Release Notes Threat Management Services zl Module ST.1.2.110301
95
Known Issues
Release ST.1.0.090213
■ PR_13560 — When a user is in a TMS zl Module CLI session and they copy the startup-config
file to an FTP server when the ALG for FTP is disabled, the copy command appears to hang.
After about 60 seconds, the copy command will timeout and the user session can be
recovered.
Example:
1. Open a TMS zl Module CLI session.
2. Disable alg ftpv4
HP Switch (tms-module-D:config)# no alg ftpv4
3. Save the startup-config
HP Switch (tms-module-D:config)#copy startup-config ftp 192.168.1.1 backup.cfg
user administrator
4. If prompted, enter the password for the FTP account.
CLI hangs for sixty seconds.
■ PR_14561 — An unexpected group already exists error may show up when a user
deletes a group and then adds a group with the same name again. The TMS zl Module marks
groups for deletion, but the actual deletion may take a few seconds. Simply wait a few
seconds before adding a group with the same name as a group that was previously deleted
and the error will not appear.
■ PR_14762 — In the web browser interface, when the primary and secondary DNS servers’
values are cleared, no error is reported, but the secondary DNS server's value is not cleared.
■ PR_14783 — When moving a TMS zl Module from one switch to another, DHCP Relay may
not start if there is a mismatch in VLAN configuration between the switches. Specifically, if
a VLAN is enabled in DHCP Relay and then the TMS zl Module is moved to another switch
which doesn't have that VLAN, the DHCP Relay agent doesn't start up and DHCP Relay will
not work. When moving a TMS zl Module, if you wish to maintain the TMS zl Module
operation, be sure the VLAN information matches before moving the module to another
switch.
■ PR_14785 — When executing the TMS zl Module CLI command sh port-trigger
<port-trigger_name> where the port-trigger-name does not exist, an error message is displayed
Error: Operation failed rather than an error message stating that the port does not exist.
■ PR_14794 — There is not a one-to-one correspondence between packets processed or
dropped and the log entries that are generated - more log messages than necessary are
created. The log is correct, it just has more entries than necessary to describe what happened.