TMS zl Module Release Notes ST.1.0.090213

18
Known Issues
Release ST.1.0.090213
PR_0000000999 — In the Web browser interface, Firewall > Access Policies, if a user deletes
all the rules in an access policy, the Web browser interface doesn't remove the empty policy
until a screen refresh is done. This is a visual issue only, the policy has actually been removed.
PR_0000002379 — In the Web browser interface, when adding a Service Object, if the
Service Object already exists, an error message is displayed. The error message refers to an
Address Object instead of a Service Object.
PR_0000002387 — In the TMS zl Module CLI, when creating a Service Object, the value of
zero cannot be set as a protocol number although zero is a valid protocol number.
PR_0000002485 — 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_0000005580 — When adding an access policy, the administrator is always asked about
a source port, which is not applicable for all protocol selections.
PR_0000006312 — 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_0000008074 — 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: