TMS zl Module Release Notes ST.1.2.100916
Table Of Contents
- Release Notes: Version ST.1.2.100916 Software for the HP ProCurve Threat Management Services zl Module
- Contents
- Software Management
- Download Documentation from the Web
- Software Updates
- Special Considerations Prior to Updating
- Clarifications
- Enhancements
- Enhancements in ST.1.2.100916
- ST.1.1.100430
- ST.1.1.100226
- Command Line Interface (CLI) control of VPN functionality
- RADIUS authentication for management logins
- RADIUS authentication for L2TP users
- Renaming zones
- 256 VLANs now supported, increased from 19 VLANs
- Enhanced sort and filter capabilities for displaying log files
- Improved SNMP Monitoring for network traffic and key system resources
- Software Fixes in Releases ST.1.0.090213 - ST.1.2.100916
- Known Issues
96
Known Issues
Release ST.1.0.090213
1. Open the switch management Web browser interface
2. Select the Configuration tab
3. In the Device View page in the Switch Web browser interface press the Details link on the
TMS Zl Module.
Expected Results: the link should direct the user to the management IP address.
Actual Results: the link directs the user to the High Availability IP address.
■ PR_9688 — After an HA link is restored, the TMS zl Module with higher priority does not
rejoin the cluster as a Master.
Example:
1. Configure a module in HA as Master (Active) with priority set to 1.
2. Configure a module as Participant (Standby) with priority set to 254.
3. Once both modules are in the cluster, remove the HA link (cable) that connects both
switches.
Both devices become Master independently.
4. Re-connect the HA link.
Expected Results: The module with priority set to one (original Mater) becomes Master again.
Actual Results: Device with lower priority joins the cluster as Master and the one with higher
priority joins as Participant.
At first glance, this seems to be incorrect, but it is actually done by design. It is assumed that
there is something wrong with the module that failed, for example, an intermittent problem. As
a result, once the link is rejoined, the module that was Master joins back as a participant (standby)
in an attempt to prevent any future issues.
■ PR_10844 — When a Participant joins or leaves a cluster, there is very little detail to the
log entries describing these important events and these events must be inferred.
■ PR_14506 — When an HA configuration is configured for Active/Standby and the Master
has IPS enabled and has downloaded the latest signature file, the Participant will not show
the correct version of the signature file. The actual signatures are synchronized correctly,
but the file name is not.
Example:
Precondition: Master and Participant already on a cluster
1. Download the signatures on the Master.
2. Wait until the Participant reboots and re-joins the cluster.
3. Run sh ips command on the Participant.