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
69
Known Issues
Release ST.1.0.090603
■ PR_51945 — VPN Site to Site: Traffic is not passing through when enabling or disabling the
VLAN to have a unique MAC or not to have a unique MAC. Workaround:
1. Delete all of the static routes associated with the VLAN using CLI "no ip route .... " (faster
method) or the Web browser interface (slower method)
2. Add back the static routes again using CLI "ip route ..." (faster method) or the Web browser
interface (slower method).
■ PR_52093 — The TMS zl Module cannot import certificates where the signing algorithm is
different from the key generation algorithm. For example, the signing algorithm is DSA and
the key generation algorithm is RSA.
■ PR_ 52119 — A DSA generated CA certificate does not show on the Web browser interface
or CLI after the certificate is imported, while an RSA generated CA certificate will display
okay. After importing the CA certificate on the Web browser interface ('VPN> certificates>
certificate authorities > import certificate'), the CA display is empty. Attempting to import
the certificate again results in a dialog that indicates "the certificate authority already exists".
The CA certificate doesn't display on CLI either. The CA certificate is actually stored and
used in communication, but isn't displayed.
■ PR_52480 — In SCEP Settings, a user cannot clear the unique CA identifier field, either
through the Web browser interface or the CLI interface. If a user fills in all the text fields in
the SCEP settings except for the Unique CA Identifier, then presses Apply My Changes, no error
is thrown and the settings are applied successfully. When the user clicks the SCEP tab again,
the Unique CA Identifier contains the string "scep".
■ PR_53488 — TMS zl Module GRE functionality may not properly detect GRE keep-alives if
a non-TMS endpoint specifies GRE options such as Checksums or Sequencing. Normal GRE
traffic can be received with these options present, but GRE keep-alives with these options
are not handled properly. This results in the GRE tunnel being detected as down by the
non-TMS endpoint of the GRE tunnel. Please note that the TMS zl Moule does not at the
present time include the capability of specifying GRE options such as these, so they cannot
be configured for transmission of GRE traffic from the TMS zl Module. Also note, some GRE
implementations allow for a key parameter to be specified. The TMS does not allow for a
key configuration item. If a GRE implementation has the key parameter specified, normal
GRE traffic as well as keep-alive traffic will not pass.
Release ST.1.0.090603
The following problems are known issues as of release ST.1.0.090603.
Upgrading to ST.1.0.090603 from ST.1.0.090213
PR_41849/PR_41855 — After upgrading, the switch command line reports the first installed TMS
zl Module software version (ST.1.0.090213) rather than the updated version (ST.1.0.090603)