TMS zl Module Release Notes ST.1.2.101122

Known Issues

Release ST.1.2.101122

Known Issues

Known issues fixed in a later software release are indicated using the following format:

■ PR_xxxxxxxxxx —

To confirm what release fixed the issue, use the issue number to search the PDF file.

Known issues that are open as of the latest software release appear as follows:

■ PR_xxxxxxxxxx —

Release ST.1.2.101122

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

Firewall

■ PR_65612 — Create a scenario where five hosts are getting NATted by a TMS zl Module

from Internal zone to External zone (source NAT). Three of five hosts can ping hosts on the

External zone.

Clear the connections using the no connections command on the TMS zl Module CLI.

After clearing connections, all hosts were able to ping for 2 seconds, then two of them (not always

the same as before) stopped pinging.

Captures on the External interface just show packets flowing from the External VLAN IP to the

target host.

Replace the TMS zl Module with an HP ProCurve 7203 router and enable NAT.

With Router, all hosts can ping the external host without interruptions.

High Availability

PR_ 65978 — HA configuration does not detect an invalid IP/mask combination.

To recreate, configure on the TMS console:

1. (tms-module-C:config)# high-availability active-standby cluster 6 device 1

priority 55 multicast-ip 224.5.5.5

2. (tms-module-C:config)# high-availability ip 192.168.1.1 255.255.255.255

Although an invalid mask has been specified, no error is observed. The mask should allow

for a maximum of 30 subnet bits and at least 2 host bits so that the active and standby modules

can have a unique IP address.