TMS zl Module Release Notes ST.1.2.101122

46
Known Issues
Release ST.1.2.100916
When a TMS zl Module does a hardware boot, its startup time is acquired from the switch chassis via
a serial port on the blade, before the Operating System loads. At the end of the module's booting
process, the module will coordinate with the switch chassis to sync up with the switch chassis's time
with proper time zone information.
If a switch chassis is power cycled, it will cause both the switch and the TMS zl Module to be rebooted.
During the switch booting process, the switch will also first acquire the startup time from its onboard
CMOS clock, which could have some drift of a few seconds. But the time on the switch will be
corrected after SNTP synchronization with the configured SNTP servers. The corrected time will also
be relayed to the TMS zl module such that both the switch chassis and the TMS zl Module will have
the correct time.
Release ST.1.2.100916
The following problems are known issues as of release ST.1.2.100916.
General
PR_59404 — PPP interfaces are not removed after the a tunnel goes down or is removed from
configuration. The PPP interface can be seen in the Network Interfaces page. Its existence does not
cause any problems but is noticeable.
PR_58097 — The CLI command capture terminal gre will capture the GRE interface as well as others
interfaces.
PR_58514 — When IRAS is enabled, only the IPsec policy that is associated with IRAS is the effective
IPsec policy. Making changes to the IRAS configuration requires the IPsec policy be deleted and
recreated.
PR_59554 — A user with Operator Privileges can ping via Command Line Interface but not via the
web browser interface
PR_60219 — Signature Download Error status shows up when IPS is neither licensed nor configured.
The error message "Error occurred during last update. Could not resolve domain" will appear on any
new system or system where the startup-config has been erased even if it does not have an IPS
signature service license and IPS is not configured. This error should not be reported under such
conditions.
PR_60430 — An erroneous log message with mid 306569 is being generated with no source address
and shows IPsec v6.
Example:
2010-08-02 13:54:35 info SPI = N/A, Seq. No = N/A :: Handling ICMP
ErrorMessage. ICMP Message Type 3 and Code 1 are not alloweddate:
2010-08-02time: 13:54:35msg: SPI = N/A, Seq. No = N/A :: Handling