CUSTOMER RELEASE NOTES
08/13/2008 P/N: 9038155-52
Subject to Change Without Notice
Page: 28
of 41
F0615-O
Changes and Enhancements in Previous Releases
Default gateway and default route information is now available via CLI, but was not in previous releases.
A problem with the switch displaying improper information using the ―show inline power‖ command has been
corrected. The command now returns the proper amount of total power for the device.
A problem with edge port STP topology change counters incrementing incorrectly has been corrected.
A problem with the password reset not operating properly has been corrected.
A problem with disabling port mirroring causing a port to be inoperable has been corrected.
A problem displaying SNMP targetparams correctly has been corrected.
A problem preventing the user from creating a static VLAN after a dynamic VLAN had been created has been
corrected.
A problem where auto negotiation was disabled for the four MGBIC ports has been corrected.
The event log will now time stamp error messages with the current time/date.
A problem where
logging in as ―rw‖ allowed the user to change the ―admin‖ password has been corrected.
Viewing the ARP cache for the switch via CLI is now supported.
A problem with the output of the ―show igmpsnooping mfdb‖ has been corrected.
An issue requiring the user to configure LAGs in the non-default VLAN first has been corrected.
The ―flowlimit‖ commands are now named ―flowcontrol‖.
KNOWN RESTRICTIONS AND LIMITATIONS:
Known Issues in 5.01.06.0007
There are no new known restrictions or limitations associated with this release.
Known Issues in Previous Releases
When using macauthentication, if the multiauth session-timeout is set through the CLI, users are not able to re-
authenticate once the session timeout expires.
Workaround: Use the Radius server to configure the session timeout instead of the CLI on the switch. The
session-timeout works correctly when returned by the Radius server, allowing users to re-authenticate.
Setting of port advertised capability on Combo ports is not persistent.
When a VLAN tunnel is applied,
t
raffic is egressed untagged as expected.
―Show vlanauthorization‖ will display
the correct VLAN and MAC address;
however ―show vlan‖ and ―show port egress‖ will not display tunnel ports.
When configuring a login banner ensure that the banner message is properly configured with a beginning double
quote and ending double quote. The message itself cannot contain any additional double quotation marks.
RIP auto-summarization affects both RIPv1 and RIPv2 routes by default.
If the host IP address or the router IP interface used for management is in a zero subnet (i.e. 10.0.x.x/16), ARPs
will resolve, and the host will be unable to ping devices within the subnet.
PIM-SM commands are not displayed in the device configuration.
ICMP packets containing the record route or timestamp options will not be forwarded by the device.
If a secondary address is added to an interface advertising RIPv2 via the ―redistribute connect‖ command, the
router will send an initial RIP response packet which includes the secondary address, but in the subsequent
updates the route is not advertised.
The SecureStack does not send router Syslog messages.
Policy assignments for authenticated users will be dropped if the multiauth precedence of their ports is modified.
A locally configured DCHP server will not respond to a DHCP request for an IP address if the MAC address of the
client is statically configured on the server and the DHCP request uses option-61, client identifier.
The SecureStack will not add a host route to its routing table for a subnet it already knows about.
When CoS based rate limiting is enabled, port based rate limiting is not supported.
MAC Addresses listed in a ―Violating‖ state according to Port MAC Locking can still dot1x authenticate on the port
but the user will not have access on the network.
If you set a port to lacp passive using the command ―clear port lacp port ge.1.1 aadminstate lacpactive‖ the
command ―clear port lacp port ge.1.1 aadminstate lacptimeout‖ will also be added to the configuration. If you
unset the command it will remove the second command automatically from the configuration file.
