TMS zl Module Release Notes ST.1.2.101122

Software Fixes in Releases ST.1.0.090213 - ST.1.2.101122

Release ST.1.1.100430

■ PR_49894 — TMS zl Module web browser interface performance Related HA + IPS issue -

scheduled to be addressed in May-June 2010 release. Should not affect users with < 75% CPU

utilization.

■ PR_50615 — Unable to monitor RAM and CPU performance via SNMP.

■ PR_50102 — Incorrect values for the SNMP objects ifSpeed and ifHighSpeed

■ PR_3743/PR_11770/PR_2838 — Cannot change sysName, sysContact, or sysLocation

objects via SNMP

■ PR_50035 — Performance Related Maximum Configured Access Policies issue - scheduled

to be addressed in May-June 2010 release. Should not affect users with < 75% CPU utilization.

■ PR_50252 — Performance Related HA + 256 VLAN configured issue - scheduled to be

addressed in May-June 2010 release.

■ PR_50465 — Performance Related - excessive logging during times of high packet

throughput - scheduled to be addressed in May-June 2010 release.

■ PR_51091 — IP Addresses may get translated for ICMP traffic when they shouldn't be.

■ PR_51159 — When restoring a TMS configuration via the web browser interface, the http

daemon could halt and prevent the configuration from being loaded. The http daemon would

restart, but the configuration file would not have been loaded.

■ PR_51303 — If a RIP interface is disabled, deleted, then added back with the same IP

configuration, re-enabled again, it will not send out RIP updates any more. Workaround:

disable the RIP interface again and then re-enable it.

■ PR_51502 — In the CLI, the command capture file any ether ? does not list choices available.

■ PR_52023 — Performance Related IPS issue - Scheduled to be addressed in May-June 2010

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

■ 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.

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

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

Firewall

■ 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_15293 — A lot of firewall logs are generated for normal management activities. Showing

this log will lead a user to thinking the firewall is blocking legitimate traffic.