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

Known Issues

Release ST.1.1.100226/ST.1.1.100330

The following problems are known issues as of release ST.1.1.100226.

General

■ PR_9285 / PR_9286 — For RIP, there are some minor issues when interoperating between

RIP version 1 and RIP version 2 on the switch. As a general recommendation when using a

TMS zl Module, always standardize on RIP version 1 or RIP version 2, with RIP version 2

preferred.

■ PR_12609 — The web browser interface consistency and text clarification edits.

■ PR_16221 — In the web browser interface after a successful software update, the success

Log message is lost after rebooting the blade. Steps:

1. Make software update using any server (for example, tftp).

2. After the image has been installed, go to logging>view log page.

3. Use the filter to see the log message (for example, Severity Major).

4. See the logging message Image completed successfully for host .... is

displayed.

5. Reboot the blade.

The Image completed successfully for host .... log is deleted after rebooting the

blade.

■ PR_17703 — In the web browser interface, the logs may pick up the wrong time zone from

the chassis.

■ PR_18482 — Inconsistent treatment of password fields in web browser interface.

■ PR_ 39670 — LLDP protocol sends localhost as the name of the system instead of configured

hostname in monitor mode.

■ PR_41166 — In the routing CLI, ip rip send should work as enabling sending updates.

■ PR_41291 — In the CLI, show logging local filter date-time accepts invalid time values.

■ PR_42142 — When using the Firefox browser, when on the Update Software page and

refreshing or going to a different tab, the following message is displayed Can't establish

connection with the device. The message is displayed only for a few moments. In

IE7, this message is not displayed.

■ PR_42607 — In the web browser interface, duplicate IP addresses are allowed under DNS

configuration. The web browser interface allows you to put the same IP address twice, under

Primary DNS server and Secondary DNS server.