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
47
Known Issues
Release ST.1.1.100430
■ PR_55506 — When an invalid protocol number is specified for an access policy, the error
message gives a valid range as 0 to 255 when the correct range is 1 to 255.
■ PR_55698 — In the command line interface, the command show connections will truncate
the word "Other".
■ PR_54075 — When Firewall policies are moved in order (priority), current active sessions
are re-evaluated against the new priority. However, some data associated with the policy is
not updated. This old state is reflected in the show connections command by incorrectly
associating the active session with a policy that no longer applies to the session (due to the
policy move). This error is visual only and the actual session not associated with that policy
and was re-evaluated.
■ PR_54194 — Login with the same user on two different host and then logout from both, the
local log only generates a log entry from the first logout.
■ PR_56192 — Upgrading the TMS from an ST.1.0.XXXXXX version to a ST.1.1.YYYYYY
version, the IPS Protocol Anomalies Settings are not being migrated, but instead are restored
to default values.
Steps to reproduce:
1. Running an image of ST.1.0.XXXXXX
2. Change the IPS Protocol Anomalies settings.
3. Upgrade via the Web User Interface
4. Reboot the TMS to complete the upgrade process.
5. After rebooting login to the Web User Interface and go to the IPS Protocol Anomalies
settings.
Expected Result: Protocol anomalies settings should be the same as the ones set before the
upgrade.
Actual Result: Protocol anomalies settings are not migrated after the upgrade and they are reset
to default values.
■ PR_55989 — When running tracert from a device in an internal zone to a device in the
external zone, the results do not show the correct host names (IPs) in each reply. Instead,
every reply shows the host name of the destination host. This problem appears when source
NAT is configured on the TMS and a host in the local network issues a tracert command for
a destination on a remote network.
Workaround: When using this configuration, use tracert to validate connectivity to the TMS. To
validate connectivity to an external destination in this configuration, use trace route from the
TMS.