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 48
engage. Once the contacts have engaged, use the extractor handles to finish
seating the module completely and tighten the screws.
After the module is installed and powered on, the switch’s Test LED should
come on briefly while the module is undergoing self-test (if the module was
installed with the switch powered down, the Test LED will stay on for the
duration of the switch self-test, not just the TMS zl Module self-test), the
switch’s Fault LED should stay off, and the switch’s Module Status LED for
the slot in which the TMS zl Module is installed should stay on. The module’s
HDD and CF Status LEDs should come on after successful initialization and
the module’s Module Status LED should flash green after successful
initialization. This LED will stay this way as long as the module is booted to
the Service Operating System, but will be solid green when the TMS product
software is ready.
9.2 Preparing the TMS zl Module for Configuration
Now that the module has been installed, the next steps are to acquire the activation
hardware ID from the Service OS context, generate an activation license key on the My
ProCurve portal, install the activation license key on the module, and access the Product
OS context for the first `.
9.2.1 Ensure switch time is set properly
It is important to ensure that the host switch has accurate date and time as the
TMS zl Module derives its time information from the host switch.
There are many features in the TMS zl Module that are dependent on this date
and time. Inaccurate date and time can complicate access and some
configuration steps that are dependent on certificatates, which reference key
dates. Security logs require accurate date and time stamps to allow for
comparison to other devices and security events. In addition scheduled access
policies will not be properly applied if the time and date are not correct on the
switch.
For steps on how to configure your switch to communicate with a time server,
see the “TimeP Time Synchronization” section of the HP ProCurve Series
3500yl Switches, Series 5400zl Switches, 6200yl Switch, and Series 8200zl
Switches Management and Configuration Guide.
9.2.2 Service Operating System
The TMS zl Module has two operating contexts, Service OS and Product OS.
The Service OS context is used for basic setup and maintenance, and is
accessed from the switch command line via the services {TMS-zl-Module-
slot} 1 command (e.g. services c 1). After entering this command, the prompt
should change from {switch-hostname}# to {switch-
hostname}(services-module-{
TMS-zl-Module-slot
}:HD)#.