Release Notes Threat Management Services zl Module ST.1.2.110427 06-2011

Known Issues

Release ST.1.1.100226/ST.1.1.100330

3. Add a Source NAT policy (e.g., NAT from Zone1 >External Services FTP, HTTP,SSH; Source

Any, dst 10.10.100.1-10-10.100.20 NAT value 10.10.100.111)

4. Open FTP server or any of the basic services

5. Verify IP address gets translated on the destination zone

6. Send ICMP traffic

7. Verify IP address gets translated on the destination zone when it should not be.

■ PR_51154 — Under high load with 100% CPU utilization, rebooting the TMS zl Module

causes the TMS zl Module to temporarily hang during the boot process. The TMS zl Module

will recover when the load decreases and frees up the CPU.

■ 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_52143 — In the TMS zl Module CLI, the command 'ping' would ignore the repetitions

option if the data-size parameter was specified before it. Workaround: Specify the repetitions

option before the data-size option.

■ PR_52174 — A Communications error dialog displays when attempting to change the

following settings in the TMS zl Module with PCM Device Manager:

sysName

sysContact

sysLocation

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