TMS zl Module Release Notes ST.1.1.100330

63
Known Issues
Release ST.1.0.090213
PR_14561 — An unexpected group already exists error may show up when a user
deletes a group and then adds a group with the same name again. The TMS zl Module marks
groups for deletion, but the actual deletion may take a few seconds. Simply wait a few
seconds before adding a group with the same name as a group that was previously deleted
and the error will not appear.
PR_14762 — In the Web browser interface, when the primary and secondary DNS servers’
values are cleared, no error is reported, but the secondary DNS server's value is not cleared.
PR_14783 — When moving a TMS zl Module from one switch to another, DHCP Relay may
not start if there is a mismatch in VLAN configuration between the switches. Specifically, if
a VLAN is enabled in DHCP Relay and then the TMS zl Module is moved to another switch
which doesn't have that VLAN, the DHCP Relay agent doesn't start up and DHCP Relay will
not work. When moving a TMS zl Module, if you wish to maintain the TMS zl Module
operation, be sure the VLAN information matches before moving the module to another
switch.
PR_14785 — When executing the TMS zl Module CLI command sh port-trigger
<port-trigger_name> where the port-trigger-name does not exist, an error message is displayed
Error: Operation failed rather than an error message stating that the port does not exist.
PR_14794 — There is not a one-to-one correspondence between packets processed or
dropped and the log entries that are generated - more log messages than necessary are
created. The log is correct, it just has more entries than necessary to describe what happened.
PR_14823 — When adding a VLAN to a zone, the log displays two entries with the exact
same message, but containing a different priority. The message describes the routing
interface coming up. For example, if VLAN 50 is added to a zone, the following two log
messages are created:
time="2008-12-12 13:14:24" severity=warning pri=4 fw=ProCurve-TMS-zl-Module
id=routing msg="if_rtup: UP route for interface vlan50
10.10.10.1/255.255.255"
time="2008-12-12 13:14:23" severity=warning pri=5 fw=ProCurve-TMS-zl-Module
id=routing msg="if_rtup: UP route for interface vlan50
10.10.10.1/255.255.255"
PR_15081 — When using the Web browser interface for the software update feature, the
Latest Status field is not automatically refreshed. Refreshing the browser displays the Latest
Status correctly but also clears the download form. Although no longer needed by the TMS
zl Module to perform the software update, the clearing of the download form removes some
information from view.
PR_15153When using the TMS zl Module CLI, two commands provide an insert-at
<position> extended option: access-policy and nat. There is no error checking on the position
number provided - it is assumed that a policy or rule exists at that location. For example,