TMS zl Module Release Notes ST.1.1.100330

42
Known Issues
Release ST.1.1.100226
■ PR_48459 — NIMv2.1: Delete CA Certificates shows Status "Completed Successfully" but
it actually does not delete the CA Certificates due to the Script MIB introducing a extra escape
MIB.
■ PR_49913 — If a Certificate Signing Request is created, then a software update is performed,
the Certificate Signing request is not saved across a software update.
■ PR_50227 — After setting up a GRE tunnel and then rebooting the TMS zl Module, the TMS
zl Module state will be recorded as Thu Jan 1 00:00:00 1970 instead of the startup date and time
of the TMS zl Module. As a result, the tunnel state shows improper values:
Tunnel State
State : Enabled 14615 days
Changed : Thu Jan 1 00:00:00 1970
■ PR_50274 — L2TP connections can be displayed for a RADIUS user but cannot display L2TP
connections from local L2TP user.
■ PR_50586 — RADIUS server modification is not allowed after an L2TP connection. Steps
to recreate:
1. Create a global RADIUS server (the server for example.com)
2. Use an L2TP connection to login a user with the domain name that corresponds to the global
name (example.com), but without specifying the domain name.
3. Log out the user.
4. Attempt to delete/modify global RADIUS server is not allowed.
■ PR_51945 — VPN Site to Site: Traffic is not passing through when enabling or disabling the
VLAN to have a unique MAC or not to have a unique MAC. Workaround:
1. Delete all of the static routes associated with the VLAN using CLI "no ip route .... " (faster
method) or the Web browser interface (slower method)
2. Add back the static routes again using CLI "ip route ..." (faster method) or the Web browser
interface (slower method).
■ PR_52093 — The TMS zl Module cannot import certificates where the signing algorithm is
different from the key generation algorithm. For example, the signing algorithm is DSA and
the key generation algorithm is RSA.
■ PR_ 52119 — A DSA generated CA certificate does not show on the Web browser interface
or CLI after the certificate is imported, while an RSA generated CA certificate will display
okay. After importing the CA certificate on the Web browser interface ('VPN-> certificates->
certificate authorities -> import certificate'), the CA display is empty. Attempting to import
the certificate again results in a dialog that indicates "the certificate authority already exists".
The CA certificate doesn't display on CLI either. The CA certificate is actually stored and
used in communication, but isn't displayed.