Release Notes Threat Management Services zl Module ST.1.2.110909 11-2011

Known Issues

Release ST.1.0.090213

• Invalidly fragmented UDP packets

The TMS zl Module only detects invalidly fragmented UDP packets and generates a log with

mid=1001 with msg="Jolt attack detected". This log message should identify jolt2.

The TMS zl Module does not detect the following:

• Jolt- which sends very large fragmented ICMP packets to a target machine.

• Jolt2- Invalidly fragmented ICMP ECHOs (pings)

■ PR_10767 — When using RADIUS authentication, the field NAS-Identifier is sent for CHAP

and MS-CHAP authentication requests, but not for PAP requests. If any network

infrastructure requires the NAS-Identifier field, a user needs to use to CHAP or MS-CHAP at

this time.

■ PR_11016 — 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_10023 — The TMS zl Module does not log authenticated user logins and logouts. There

is no workaround for this issue at this time.

■ PR_11190 — 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_11703 — When a TMS zl Module is moved between two switch chassis with different

configurations, references to VLANs can remain on the OSPF and Multicast pages.

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.