Advertisement
Changes and Enhancements in 3.03.27
The OIDs for sysLocation, sysContact, and sysName now support a maximum string length of 255 characters
each.
If the stack is part of a spanning tree region and it is changed to stpcompatible (forced version 0), it will be
removed from the region since it is now considered a single spanning tree device. If, however, it is set back to
MSTP, it will now correctly re-enter the MSTP region.
Clear policy port will now correctly remove the policy assignment specified.
Support for spanning tree tctrapsuppress and protomigration have been added to the CLI.
The output of ―show port lacp port <port> counters‖ now clearly defines each port number within a stack.
The ―show spantree portadmin‖ command has been added to the CLI.
Changes have been implemented to make the move management command more resilient.
Support has been added to allow users to set the host VLAN via the dot1qPvid OID.
When an authenticated user is moved from one port to another, the etsysMultiAuthSessionStationAuthStatus
MIB entry will now change to reflect authTerminated(5), and Policy Manager will display the session in black,
which indicates an inactive (previously authenticated) session.
The ifMtu OID now correctly returns the maximum supported ifMtu size for each port.
The ipNetToMediaTable MIB now associates entries to the host port.
When a change in the selection of the stack manager occurs via the movemanagement command, the new
master will now send out a gratuitous ARP packet.
The PWA port control options have been changed to match those found on the Enterasys DFE switches.
When a SecureStack device suffers from a power system failure, the system will now send trap from the
etsysPsePowerNotification MIB, which can be correctly decoded by NetSight Console.
Changes and Enhancements in 3.02.32
When a ―verify‖ function is performed by NetSight Policy Manager on a C2 configured with VLAN-to-Role
mapping, the C2 will now return the correct result.
The C2 now has the ability to handle multiple 802.1X authentication attempts without requiring that they be
separated by a logoff frame.
Changes and Enhancements in 3.02.30
In previous versions a condition could occur in which a unit could leave and rejoin the stack, this has been
corrected.
When deleting an MSTI the fault which resulted in an error message being displayed on the CLI has been
resolved.
Deleting Multiple Spanning Tree Instances will no longer result in error messages being displayed for each
VLAN which was a member of the deleted MSTI.
If the switch has its configuration changed from MSTP to RSTP, the device will correctly remove itself from any
MST regions.
When executing the show spantree stats command with the active option, both global and port information will
be displayed.
If the switch is the root of an MSTI, the correct port role/state will now be applied when joining a region.
The SecureStack only supports a maximum of 10 locally saved configuration files. If a user tries to tftp an
eleventh configuration file onto the device, the CLI will now display an error message stating the maximum
number of saved files has been reached.
Users can now set the default value of backup root status for an MST instance using the CLI command ―clear
spantree backuproot‖.
Support for spanning tree bridgeprioritymode has been added to the device.
Support has been added for the ctEntStateOperEnabled and ctEntStateOperDisabled traps. These traps
announce if a unit has dropped from the stack due to a failure or if a unit has joined to the stack.
08/13/2008 P/N: 9038155-52
F0615-O
Subject to Change Without Notice
CUSTOMER RELEASE NOTES
Page: 20 of 41
Advertisement
