TMS zl Module Release Notes ST.1.1.100330

Known Issues

Release ST.1.1.100226

This will not happen for new TMS zl Modules running ST.1.1.YYYYY but will happen for any TMS

zl Module that updates from ST.1.0.XXXXXX to ST.1.1.YYYYYY. Unfortunately, the only known

workaround is to erase the startup-config for the TMS zl Module, reboot, and create a brand new

configuration.

■ PR_52365 — When adding a static route with a reachable gateway and then changing the

VLAN unique MAC address attribute, traffic is no longer routed. Workaround:

1. Delete all of the static routes associated with vlan XXXX using CLI "no ip route .... " (fastest)

or the Web browser interface (slower)

2. Add back the static routes again using CLI "ip route ..." (fastest) or the Web browser interface

(slower).

■ PR_ 52440 — Performance Related IPS issue - scheduled to be addressed in May-June 2010

release. Should not affect users with < 75% CPU utilization.

■ PR_52604 — In the Web browser interface the Dashboard has a field for Chassis Name but

never displays anything. In the TMS zl Module CLI, the command show system-information

also shows a field for Chassis Name but doesn't display any value for it.

■ PR_52698 — When the VLAN unique MAC attribute is changed, a Gratuitous ARP should

be sent so that ARP caches on the subnet can be updated.

■ PR_52743 — In the TMS zl Module Web browser interface (System->Settings->General), the

field 'Login Page Banner Text' is not checked for html and JavaScript code and a Trusted

Administrator could introduce that code into client's browsers.

Firewall

■ PR_1331 — Rate limiting is still based on rule ID. Positional (i.e., source zone, destination

zone, and position) should be added.

■ PR_4635 — The TMS zl Module should provide a packet count for packets that match access

policies.

■ PR_11018 — For TMS zl Module Authenticated Firewall feature, once a user logs on and

does not logout, the next user who logs on does not get their policy applied. Steps:

1. Setup two users: test and test2 in two different groups: test and test2

2. Setup two sets of user based access policy.

3. Login with user test

4. Login with user test2

User test2 still has access policy from user test.

■ PR_14787 — In the CLI, sh port-triggers <name> is not working when using numbers. Existing

configuration: