TMS zl Module Planning and Implementation Guide 2009-08
Table Of Contents
- Contents
- Glossary of Acronyms and Abbreviations
- 1.0 Purpose
- 2.0 Intended Audience
- 3.0 Objectives
- 4.0 Prerequisites
- 5.0 Skills
- 6.0 The HP ProCurve Threat Management Services zl Module
- 7.0 Common TMS Security Control Points
- 8.0 Deployment Considerations
- 9.0 Installation and Preparation of the TMS zl Module
- 10.0 Configuration of the TMS zl Module
- 11.0 Using multiple HP ProCurve Threat Management Services zl Modules
- Appendix A – Additional References
- Appendix B – Sample Company Information Assets Spreadsheet
- Sample “Information Assets” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- “Server Network Details” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- “TMS Zones” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- “Firewall Rules” tab (See Embedded “Company Information Assets” Microsoft Excel 2003 spreadsheet)
- /Sample “Company Information Assets” Microsoft Excel 2003 spreadsheet
- Appendix C – Information Gathering Tools
- Appendix D - Updating Switch Software
- Appendix E – Emergency Recovery Process
Page 7
This is the show modules
In the illustrations above, Slots C and G have TMS zl Modules physically installed but the
switch is unable to recognize them properly because it is running a too early version of K.13
software. The minimum recommended version to support the TMS zl Module is K.13.51.
command run from an SSH remote management
session. Note that devices in Slot C and G show “Failed.”
If you are planning to add the TMS zl Module to an existing production chassis, it is important to
plan accordingly for the traffic outage that will result from the software update process. This, of
course, will not be an issue for an initial installation of a TMS zl Module in a dedicated chassis.
While it is possible to reduce the duration of the traffic outage that will be required by the switch
software update on a 8200zl series switch with the recommended redundant management
modules, a short duration outage will result from the switch software update. On a 5400zl series
or 8200zl series switch without redundant management modules, the outage will be
approximately 3 minutes - the length of time required to complete a reboot of the sole
management module. On an 8200zl series switch with redundant management modules, that
outage time can be reduced to approximately 45 seconds by upgrading and booting the standby
management module and then forcing a redundancy switchover once the standby management
module has completed booting up on the new switch software.
New switch software may be acquired from the HP ProCurve web site’s Software for Switches
page. The process of loading new software on to a ProCurve switch is well-documented in
Appendix A of the HP ProCurve Series 3500yl Switches, Series 5400zl Switches, 6200yl Switch,
and Series 8200zl Switches Management and Configuration Guide, but the following is an
overview of a secure method.
1. Go to the ProCurve web site at http://www.procurve.com.
2. Click the Support tab near the top of the page.
3. Click on Switches just under Download the latest software near the bottom right of
the page.