TMS zl Module Release Notes ST.1.1.100430

Known Issues

Release ST.1.1.100226/ST.1.1.100330

Monitor Mode

■ PR_42670 — Firewall Logs are shown for broadcast packets in monitor mode.

time="2009-07-08 19:36:37" severity=warning pri=5

fw=ProCurve-TMS-zl-Module id=fw_access_control ruleid=0 msg="FW: no

access policy found, packets dropped" srczone=ZONE6 src=10.255.134.37

srcport=137 dstzone=ZONE6 dst=10.255.135.255 dstport=137 proto=UDP

rcvd=0 rcvdsc=0 sent=0 sentsc=0 srcnatport=0 destnatport=0 destnati-

paddr=0.0.0.0 subfamid=accessdeny mtype=access_control mid=629 srcna-

tipaddr=0.0.0.0

■ PR_44127 — An invalid log message (mid=339) may appear in monitor mode with invalid

contents.

time="2009-08-18 15:15:07" severity=critical pri=1

fw=ProCurve-TMS-zl-Module id=l2br_bridge portname=" dropping packet"

destination_macaddress="urce mac is broadcast, dropping packet" subf-

amid=l2brprotoerror mtype=l2bridge mid=339 source_macaddress=""

■ PR_45379 — In monitor mode, there is an inconsistency between CLI and the Web browser

interface: there is not a view routes page in the Web browser interface. You have to use the

CLI to view routes.

■ PR_50226 — TCP connection anomaly logs should be removed in monitor mode.

date: 2010-01-06

time: 18:49:12

msg: TCP: invalid ACK packet, packets dropped

severity: info

id: fw_l2l3_attack

srczone: INTERNAL

src: 10.234.58.12

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