TMS zl Module Release Notes ST.1.1.100330

65
Known Issues
Release ST.1.0.090213
■ PR_16231 — Some log entries for warning logs and information logs have messages that
are truncated in the log viewer. The most log messages are not truncated and those that are
contain enough information that a user can tell what they are about. However, the messages
have more information in them than can be displayed.
■ PR_16539 — When using the TMS zl Module CLI, the radius-server help command gives
options that are not available.
■ PR_16546 — A TMS zl Module that incorrectly has duplicate IP addresses for its VLANs
may cause the TMS zl Module SNMP daemon to restart, which may hide the actual problem
from a user. While it is incorrect to have duplicate IP addresses, this may occur, and the
SNMP daemon restart may send the administrator down the wrong troubleshooting path.
■ PR_16812 — When a user incorrectly logs into a TMS zl Module resulting in an
authentication failure, if the TMS zl Module is setup to send traps, it will send an
authentication failure trap. However, the trap does not contain the user's IP address or the
username.
■ PR_16892 — When the local log contains more than 10,000 entries, the oldest entries (after
the 1,000th entry) are displayed in a wrong position.
Steps to reproduce:
1. Get more than 10,000 entries in the local log
2. Either export the local log or, in the Web browser interface, set the number of entries per
page to 500 and go to page 6.
■ PR_18145 — In the Web browser interface, if a VLAN is added with an invalid IP address
in the range 224.0.0.0 - 254.255.255.255, an error is returned stating:
VLAN could not be
added. Failed to add VLAN IP address
, but the VLAN is actually added, but not
associated to any zone. In the CLI, the error message only states:
Error: Failed to set
VLAN IP address:
■ PR_18197 — The Web browser interface Help incorrectly states the number of VLAN
associations supported as 21. It should be 19.
■ PR_999 — In the Web browser interface, Firewall > Access Policies, if a user deletes all the
rules in an access policy, the Web browser interface doesn't remove the empty policy until
a screen refresh is done. This is a visual issue only, the policy has actually been removed.
■ PR_2379 — In the Web browser interface, when adding a Service Object, if the Service
Object already exists, an error message is displayed. The error message refers to an Address
Object instead of a Service Object.
■ PR_2387 — In the TMS zl Module CLI, when creating a Service Object, the value of zero
cannot be set as a protocol number although zero is a valid protocol number.