Advertisement
CUSTOMER RELEASE NOTES
Changes and Enhancements in 5.00.59
The command ―clear rmon stats to-defaults‖ will correctly reset rmon statistics to zero for all ports.
The SecureStack will now send Syslog messages for each of the configurable applications to a remote Syslog
server.
Modified the help displayed for the ―set radius realm any‖ command to correctly reflect all the configurable
options available for this sub-command.
Administrators have the option to disable inbound telnet and still manage the SecureStack via WebView.
The ifMauAutoNegConfig MIB will now correctly report the port status when polled.
Non-default port queuing assignments will be retained when upgrading code on the SecureStacks.
The output of "show config all vlanauthorization" now reflects the correct port settings for vlanauthorization.
When the dot1x reauth action is invoked either by CLI or MIB, the dynamic Policy ID will be cleared.
If a user authenticates with dot1x and a dynamic policy is assigned, disabling dot1x (eapol) will cause the
dynamic policy assignment to be removed.
For those customers using MAC Authentication masking, once a user is MAC authenticated using a configured
bit mask, the switch will cease sending redundant authentication requests to the server.
The SecureStack now supports the configuration of 100 rules per profile.
If a user has maclocking enabled, and the number of MAC addresses learned on a port exceeds the configured
firstarrival value, the first MAC address causing the firstarrival value to be exceeded will be displayed as a
violating MAC address in the output of ―show maclock stations‖. If the user then increases the firstarrival value
to be larger than the number of MAC address learned on the port, the violating MAC address will now be
cleared.
If maclocking is enabled both globally and per port, the etsysMACLockingLockedEntryCause OID will now
report accurate data.
The ―set port disable‖ command will now disable the port from learning entries in the forwarding database as
well as disable the physical Ethernet link.
The ―set switch description‖ command used to rename member units in the stack is now supported.
When upgrading the SecureStack C2 or C3 to the current code, all configured routing interfaces will remain
persistent.
Changes and Enhancements in 5.00.32
Support for setting static multicast IP addresses (―set igmpsnooping add-static‖) has been added.
Restored packet buffer optimization not included in earlier patch releases.
Multiple users who are sharing a computer will have the correct policy assignment and network connectivity
applied when each user uses their login into the PC.
Clients using 802.1x authentication connecting to ports configured for multiauth can be reliably authenticated
and will have the correct policy assignment applied.
When a SecureStack C2 or C3 is using a virtual IP address as its gateway and the virtual IP master fails over to
the virtual IP backup, user connectivity to the host will be maintained.
An issue whereby incorrect data was being displayed after querying the STP MIB, has been fixed.
An issue when clearing counters on a port would result in a counter discontinuity has been fixed.
rd
An issue where creating a 23
interface would cause a reset has been fixed.
An issue where ifInDiscards were counted erroneously has been fixed.
An issue whereby invalid info from dot1qVlanCurrentUntaggedPorts was being reported has been fixed.
If member ports of a LAG are spread across multiple stacked members and one of the stacked members is
reset, the LAG port members on the reset switch will rejoin the LAG once the switch becomes operational
again.
The etsysCosIrlViolationTable MIB will now return accurate data points when polled.
If an authenticated device is replaced on a port which is configured with dual user authentication, the new
device will be required to revalidate its authentication credentials.
An issue has been resolved whereby in specific configurations the switch would occasionally transmit RADIUS
Identity requests with failure frames for valid users.
Administrators can now configure PoE ports to support either pre-standard (default) or IEEE PoE mode on any
PoE port using the ―set inlinepower [auto | ieee]‖ command.
08/13/2008 P/N: 9038155-52
Subject to Change Without Notice
Page: 15 of 41
F0615-O
Advertisement
