TMS zl Module Release Notes ST.1.1.100330

Known Issues

Release ST.1.1.100226

srcport: 135

dstzone: INTERNAL

dst: 10.255.133.182

dstport: 58319

proto: TCP

subfamid: tcpconnectionanomaly

mtype: attack

"mid: 675

High Availability

■ PR_14222 — NIMv2 does not display the HA Configuration already set on a device and the

log shows Driver Operation Fails with Exception. A user has directly used CLI

to setup a High-Availability Active-Standby cluster using two TMS zl Modules successfully.

After this cluster is successfully formed, the user tries to synchronize TMS properties of both

those devices with NIMv2. In such a condition, NIMv2 reports only the presence of a single

Master device in the cluster. This happens because the participant device is not reachable

from NIMv2 and the Master device show high-availability does not show in its output the real

identity of the Participant.

■ PR_14506 — Last Signature Download field is not synchronized on HA.

■ PR_18230 — Members for Cluster Id dialog showing Chassis IP No Switch Manag.

■ PR_38021 — TMS zl Module allows the same HA IP Address to be configured on two

modules residing in the same subnet.

■ PR_46778 — High Availability cannot be disabled without serious service disruption and

loss of connectivity. When high availability is disabled, the following message is displayed:

ProCurve Switch 5406zl(tms-module-C:config)# no high-availability

Shutting down HA will remove the IP addresses of the TMS VLANs, and any remote

connections to the TMS zl Module will be lost. You must then access the TMS zl Module's

CLI through the host switch to save the configuration and re-configure the VLANs.

Do you want to continue [y/n]?

■ PR_46898 — In High Availability mode when RIP is enabled, the TMS zl Module attempts

to send RIP via the High Availability network interface. The following log is generated as a

result:

■ time="2009-10-25 15:06:07" severity=critical pri=1

fw=ProCurve-TMS-zl-Module id=fw_l2l3_attack msg="IPROUTE: unable to

determine destination network for the packet, packets dropped"

srczone=SELF src=192.168.0.1 srcport=520 dst=192.168.0.255

dstport=520 proto=UDP subfamid=routeanomaly mtype=attack

duplicatecount=2 mid=656PR_49472 — In certain High Availability situations, the

Participant fails to receive any sessions from the Master.