Datasheet

Release Notes for 3Com X Family of Unified Security Platforms, Release 3.2 Page 10
Known Issues for Release 3.2
35030: ENABLE/DISABLE INTERFACE RESTARTS OSPF ON ALL INTERFACES
Enabling or disabling any interface restarts OSPF on all of its interfaces.
36588: FLUSHING SUMMARY AREA RANGE LSAS
OSPF and RIP do not automatically redirect routes if a physical port fails (InterfaceDown). Any existing
route using that port is still chosen and reported to neighbor routers, resulting in traffic being directed to
the failed port. Network administrators must manually reconfigure RIP and OSPF before shutting down
a port. When troubleshooting routing problems, a port link failure may well be the cause.
37257: HA IP ADDRESSES CORRUPTED WHEN STANDBY HA IP ADDRESSES MODIFIED
When using High Availability with configuration synchronization, always configure the HA Management
and Peer IP addresses on each device before enabling configuration synchronization.
37697: RADIUS AUTHORIZATION FALLS BACK TO LOCAL DATABASE
If LDAP authentication fails, local (TOS) database authentication is attempted. This fallback is also
implemented for RADIUS user authentication. LDAP authentication supersedes RADIUS authentication;
if both are configured, only LDAP is used.
39693: LSM USE WITH WEB FILTER PROFILES
Users logged in to the LSM are subject to Web filtering, under the profile associated with their TOS user
profile, if they access the Internet. Unless the user uses the login status window feature configured in
Authentication > Preferences, exiting the web browser or restarting the PC does not log out a TOS
user, and the user’s subsequent Web traffic is still filtered. Inspection of Web traffic continues until the
user logs out of the LSM or attempts to log in again.
39840: IPS RESET SECURITY POLICY DOESN'T RECREATE DEFAULT ZONE PAIR
If you click the Reset Filters button on the IPS Preferences page to reset the security policy for the IPS,
the default ANY <==> ANY zone pair is not created in the new "Default" IPS security profile.
Workaround: Edit the default security profile (IPS > Security Profiles) and add a zone pair with
Incoming and Outgoing both set to "ANY."
40085: CHANGING VLAN ID ON ZONE DISASSOCIATES ZONE FROM GRE INTERFACES
If a security zone has been added to multiple virtual interfaces, changing the zone's VLAN ID may
remove the zone from some of these interfaces.
Workaround: After such a change, review the zone assignment, and add back any zones affected to
the relevant virtual interfaces.