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 18
While not immediately relevant to the emergency recovery there are items worth noting in the
first green highlighted section, “[boot]”. We see in the yellow highlighted line immediately
following the section header that the default is to boot the monitor, then the primary, and, failing
that, the secondary. In the next three yellow highlighted lines, we see that the switch was last
booted from the secondary, is currently configured to boot from primary, and the option to
choose differently during the boot process will expire in 5 seconds (proceeding to then boot from
the switch software image in the primary flash).
In the second green highlighted section, “[primary],” we see in the yellow highlighted line
immediately following it that the file “btm.swi” contains the K.13.25 switch software currently