TMS zl Module Release Notes ST.1.0.090213

7
Known Issues
Release ST.1.0.090213
Known Issues
Release ST.1.0.090213
The following problems are known issues as of release ST.1.0.090213.
PR_0000000665 — When an IPv4 address is entered into a field, regardless of whether the
administrator is using the Web browser interface or CLI interface, the TMS zl Module is not
doing the complete validation on the address based upon the field being used. For example,
a multicast or broadcast address can be entered into source address fields. It is up to the
user to ensure the correctness of the address for the field in question.
Related PRs:
PR_0000000665
PR_0000001794
PR_0000002068
PR_0000002252
PR_0000002253
PR_0000002254
PR_0000002424
PR_0000002613
PR_0000003824
PR_0000000906 — When the Web browser interface of the TMS zl Module is left at the login
screen without the user logging into the TMS zl Module, the inactivity timer still applies,
resulting in the user having to go back to the login screen manually. The inactivity timer
should only apply once a user has logged in, but instead applies at all times.
PR_0000000961 — The initial login banner text of the Web browser interface in the TMS
zl Module differs in size depending on whether the user is accessing it with HTTP or HTTPS.
While noticeable, this difference in size does not impair functionality.
PR_0000001044 — From the TMS zl Module CLI, when a TMS zl Module is operating in
Routing Mode using OSPF, the command show ip ospf neighbor has an output that is not the
same as a ProCurve switch that is running OSPF. Important information about OSPF
neighbors is still shown, how the information that is shown is different from the switch.
PR_0000001143 — The options for VLAN IPv4 functionality change depending on how a
command is accessed. For example, vlan <id> ip options are different than going into the
VLAN context via vlan <id> and then typing ip.