Release Notes Threat Management Services zl Module ST.1.2.110427 06-2011

Known Issues

Release ST.1.0.090603

3. Go to the logging section.

4. Select the View Log tab.

5. Search for the log entry generated when logging in as Local user previously created.

6. The following log entry is displayed:

time="2009-03-24 17:00:02" severity=warning pri=4 fw=ProCurve-TMS-zl-Module

id=user_statistics msg="Radius authentication failed" srczone=SELF

dstzone=SELF logintime=0 logouttime=0 useripaddr=0.0.0.0 pktstransfered=0

usersessionid=0 subfamid=useraccounting mtype=userlogin mid=4579

■ PR_38247 — Unknown log message generated when a local user failed to authenticate

mid=4507.

time="2009-03-25 16:11:54" severity=info pri=6 fw=ProCurve-TMS-zl-Module

id=fw_access_control ruleid=0 msg="Authentication failed for TIM user"

srczone=UNKNOWN_ZONE src=0.0.0.0 srcport=0 dstzone=UNKNOWN_ZONE dst=0.0.0.0

dstport=0 proto=0 rcvd=0 rcvdsc=0 sent=0 sentsc=0 srcnatport=0 destnatport=0

destnatipaddr=0.0.0.0 subfamid=accessdeny mtype=access_control mid=4507

srcnatipaddr=0.0.0.0

■ PR_38705 — RIP: Connected VLANs are not sent correctly when Ripv1-v2 is set. The TMS

zl Module does not send the connected VLANs to another router (R1), when RIP version has

been set as v1-v2.

In the following example the TMS zl Module is using Ripv1-v2 and router R1 has RIP version 2 set.

Routes in TMS zl Module

Destination Gateway Metric Distance VLAN Type

10.10.30.0/24 10.10.30.254 1 0 lan30 connected

10.10.40.0/24 10.10.40.254 1 0 vlan40 connected

192.168.1.0/24 192.168.1.254 1 0 vlan100 connected

192.168.2.0/24 192.168.3.250 3 100 vlan300 rip

192.168.3.0/24 192.168.3.254 1 0 vlan300 connected

192.168.5.0/24 192.168.1.253 2 110 vlan100 ospf

192.168.11.0/24 192.168.11.96 1 0 vlan1 connected