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

90
Known Issues
Release ST.1.0.090213
■ PR_7723 — In the TMS zl Module CLI, an error message should be displayed and the entry
rejected when an invalid mask value is used for IP Address/Mask when specifying an IP
address for a VLAN. The user must carefully validate their input.
In the following example the incorrect mask value may result in the wrong subnet mask being
used:
HP Switch(tms-module-D:config)# vlan 1 ip address 192.168.11.25/2254
Success: Set VLAN 1 IP address to: 192.168.11.25 255.255.252.0
■ PR_7740 — During a UDP flood, the log incorrectly refers to it as a TCP flood by using
tcpconnectionanomaly. As a result, the administrator will not know whether a UDP flood
is occurring or a TCP flood is occurring.
■ PR_7914 — The TMS zl Module web browser interface is designed to only have one client
logged in as manager at any given time to avoid one manager's changes overwriting another
manager's changes. In most cases, this works as expected. However, multiple clients can log
in as manager by following the steps below.
1. Using the web browser interface, login as manager on the TMS zl Module.
2. Connect to the web browser interface page on a second client.
3. Login as manager. The TMS zl Module prompts to interrupt current manager, click cancel.
4. This brings up the logout prompt (Save&Logout, Do Not Save& Logout, Cancel), click Cancel.
Now, the additional client is logged into the web browser interface as manager.
■ PR_8044 — The TMS zl Module has been configured for VLAN IP addresses and HA is
enabled but not configured (that is, there is only one device in the cluster). If HA is
subsequently disabled, the VLAN IP addresses are lost. This could result in a loss of
management connectivity.
■ PR_8136 — Only 1,000 NAT Policies are supported on the TMS zl Module. The TMS zl Module
incorrectly accepts more than 1,000 NAT policies. These NAT policies work fine, but they
should not be used as a future software release may restrict the NAT policies. Please keep
the number of NAT policies used to 1,000 or fewer.
■ PR_8274 — The log entry that is logged when a new access policy is added has the wrong
zone information. Refer to the following log sample:
time="2008-08-14 10:54:36" severity=info pri=6 fw=ProCurve-TMS-zl-Module
id=config_configuration ruleid=123 msg="IAPPOL: adding new IA Policy record
" srczone=SELF dstzone=SELF result=0 throttledcount=20 subfamid=configura-
tionchanges operation=0 mtype=config mid=697
IA Policy refers to an Internet Access Policy, but both zones are indicated as "SELF" which is
incorrect.