TMS zl Module Release Notes ST.1.1.100330

Known Issues

Release ST.1.0.090213

■ PR_2485 — When there are a large number of firewall access policies, the Web browser

interface may take some time to load these policies to display to a user. For example, with

approximately 2,000 policies, loading them takes about 15 seconds or less. However, when

the number of firewall access policies increased, to around 15,000, the time to load the Web

page approaches three minutes.

■ PR_5580 — When adding an access policy, the administrator is always asked about a source

port, which is not applicable for all protocol selections.

■ PR_6312 — In the Web browser interface, an invalid error message is displayed when

inserting a policy at the first position when no policies exist.

Example:

1. Go to Firewall > Access Policies > Unicast page.

2. Select Add a Policy...

3. Set the following fields as specified below.

• Action = Permit Traffic

• From: = Internal (this field depends on your management zone that was set by the CLI)

• To: = Self

• Service, Source and Destination = Any

• Insert Position: = 1

4. Click the Apply button.

Expected result: The access policy should be added in the first position.

Actual Result: An error message is displayed but the policy is added.

■ PR_8074 — When a new named object (for example, an Address Object, Service Object,

and so on) is added, a log entry is generated referring to an IPDB record modified. This simply

means that the IP database that keeps track of these things was modified. See the following

example log entry:

time="2008-08-09 18:10:32" severity=info pri=6 fw=ProCurve-TMS-zl-Module

id=config_configuration ruleid=0 msg="IPDB record modified" srczone=SELF

dstzone=SELF result=0 throttledcount=0 subfamid=configurationchanges oper-

ation=0 mtype=config mid=1051 recname=b2222

■ PR_9711 — When a user authenticates by way of the firewall using RADIUS, they get the

correct policy for their group. However, if the policy is changed while the user’s session is

active, the user is not disconnected automatically to force re-authentication to provide the

updated policy. In contrast, a user that is authenticated by way of the Local database is

disconnected and must re-authenticate when the policy is updated.

Example:

1. Use username/password to RADIUS Authenticate to the TMS zl Module through the firewall.