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 9
14. Issue the command put {new switch software file path}/{new switch software file
name} os/[primary|secondary]. For example, if you stored the new switch software
file in “/usr/home/janequser”, saved it as “K_13_65.swi”, and would like to load that
image into the secondary of the switch you would issue the command put
/usr/home/janequser/K_13_65.swi os/secondary.
Note: It takes a few minutes after the completion of the file transfer for the
switch to decompress the file to the new location before the new software
version information is reflected in the show flash switch CLI command
output.
show flash
15. Use the command boot system flash [primary | secondary], depending on where
you stored the new switch software image in the previous step. For example, boot
system flash secondary.
shows our expected versions of software on each image.
Note: It is this command that will cause the switch to reboot. If the switch
is already in production there will be an outage of approximately 3 minutes.
The next section covers how to reduce this time to around 45 seconds on an
8212 zl equipped with redundant management modules.
show version
boot from the secondary boot image.
shows that the switch will now