CUSTOMER RELEASE NOTES
08/13/2008 P/N: 9038155-52
Subject to Change Without Notice
Page: 29
of 41
F0615-O
Known Issues in Previous Releases
In certain specific Policy configurations, if a user is authenticated and assigned a VLAN via Policy and then
moves to another port, the
user will be able to reauthenticate but won‘t receive a VLAN assignment via Policy.
When SNTP is enabled on a B3 that is routing but does not have a switch IP address configured, the
SecureStack will fail to synchronize its local time with the SNTP server.
An rmon alarm will not be triggered for a rising threshold when the startup parameter is configured for ―either‖.
When the rmon alarm value has incremented higher than the Rising Threshold, the rmon event for a rising
threshold will not be triggered. When the rmon alarm value drops below the Falling Threshold, the rmon event for
a falling threshold will be triggered.
When the SecureStack is configured as a DHCP server, it does not respond to DHCP Discover packets sent by
Avaya IP Phones (model 96xx) if option 242 is configured. The DHCP server will respond correctly if option 176 is
set instead.
The SecureStack will sometimes give erroneous error messages when setting RADIUS Accounting retries or
timeouts, though the commands will correctly be applied to the device configuration.
The command ―clear nodealias config <port>‖ will not clear non-default maxentries values. The nodealias
maxentries value can be set back to its default of 32 by executing the command ―set nodealias maxentries 32
<port>‖.
By default, dot1x on the stacks has maximum requests set to 2, but after only one failed login request the stacks
go to a quiet period.
When a port mirror is created the mirror destination port is removed from vlan 1 egress list after a reboot.
If an admin user has been locked out of the device CLI, pressing the password reset button will remove the
password configuration, but it does not re-enable the admin super-user account.
The ―show spantree ports active‖ command may erroneously display some ports as active. If a port was once
active and later goes down, the system will still show the port on the ―active‖ list.
The RMON Falling Alarm event will trigger at each interval, even if traffic rates do not exceed the threshold.
Additionally the RMON Alarm appears to be using the Falling Threshold as the interval instead of using the actual
interval of 15 seconds.
The MIB dot1dTpFdbTable does not return any values.
If a policy rule is created for ipsource/ipdest socket with 48 bit mask, and socket is 0 (x.x.x.x:0), the rule will
instead act on all traffic matching the 32 bit mask IP address regardless of socket value.
When policy is applied to a port, admin rules are created for the port. If a policy is removed from a port (clear
policy port / clear policy all-rules) or if user became unauthenticated removing policy from the port, the admin rule
for the port remains.
Tagged network traffic which is sent through a port mirror exits the destination port of the port mirror displaying
the packet‘s 802.1Q tag.
The order of configuration of masked rules causes different forwarding behavior
—even though the end
configuration is the same.
If the dot1dStpPortDesignatedRoot MIB is queried, the designated bridge will be returned and not the root bridge.
If a cos s
ettings‘ ToS value is configured to use the last two bits of the ToS field, these two bits will not get
marked. For example ToS value 3, will result to 0x00. TOS value 255 will result to 0xFC.
When configuring routing on a mixed stack of C2 and C3 units, OSPF is only supported on the C3 units. OSPF
adjacencies will not form on C2 slave units. OSPF adjacencies will correctly form on pure C2 stacks.
If the user sets the CLI length value to a value other than zero and enters the command ―show mac port‖ the
device will fail to display the MAC address information associated with the port specified and instead will display a
message stating ―there is no MAC addresses matching your criteria.‖
The SecureStack will remove all dynamic MAC addresses learned on a LAG port from the forwarding database
when only an individual port on the LAG bounces. These MAC addresses will then need to be relearned by the
device.
If you have a LAG between a SecureStack device and an Enterasys DFE device on which you disable lacp (set
port lacp port) on LAG member ports on the DFE and then re-enable them, the LAG will not properly reform on
the SecureStack.
The C2/C3 mixed stack does not support L2 rules, however they show as an option, this option should not be
used as it is not supported.
