TMS zl Module Release Notes ST.1.0.090213

Known Issues

Release ST.1.0.090213

■ PR_0000011016 — When users are being authenticated by the TMS zl Module and the user

accidently closes the logout window, the user no longer has the ability to explicitly logout.

The user must wait for the timeout to occur and then login again or must be explicitly

disconnected by the administrator of the TMS zl Module.

■ PR_0000010023 — The TMS zl Module does not log authenticated user logins and logouts.

There is no workaround for this issue at this time.

■ PR_0000011190 — When a RADIUS user attempts to login to a TMS zl Module, a log is

always generated with

Attempted to login with a wrong name despite the user being

able to successfully login.

■ PR_0000011703 — When a TMS zl Module module is moved between two switch chassis

with different configurations, references to VLANs can remain on the OSPF and Multicast

pages. For example:

1. Add several VLANs to the VLAN Associations page.

2. Enable RIP on one of the VLANs just added, for example, VLAN 40.

3. Enable OSPF on the same VLAN, for example, VLAN 40.

4. Enable Multicast on the same VLAN for example, VLAN 40.

5. Save changes.

6. Move the TMS zl Module to another chassis where the VLAN (VLAN 40) used on OSPF,

Multicast, and RIP, does not exist.

7. Verify that the information related to that particular VLAN (VLAN 40) is not displayed

anymore on the Zone and Routing pages.

8. Save changes.

9. Put the TMS zl Module back to the first chassis and verify that the information associated

with the VLAN (VLAN 40) is not displayed here either, since changes where saved on

previous chassis.

10. Again add VLAN 40 to the VLAN Association page.

Actual Result: VLAN 40 is displayed on OSPF and Multicast pages.

Expected Result: VLAN 40 should only be displayed on the VLAN Associations page.

■ PR_0000011856 — When using the Web browser interface, an error message is displayed

when a valid IP Address is trying to be set in some pages, such as RADIUS, IPsec Policies,

and so forth. For example, this may occur when an otherwise valid IP address is added with

a final space at the end. As a workaround, be sure there are no whitespace characters in the

IP address. This behavior is seen in Web browser interface fields such as the following:

• RADIUS (server address)

• IKEv1 (local and remote gateway, local and remote Id IPsec Policies (Traffic Selectors)