Specifications

Clarifications and Known Behaviors
ExtremeWare 7.0 Release Notes 55
RADIUS and Telnet
If one of the following two situations occurs:
1 You have a single RADIUS server configured with a RADIUS timeout value of 10 seconds or more
2 Both primary and secondary RADIUS servers lose their connections and the configured RADIUS
timeout value is 5 seconds or more
The switch might not be able to fail over to the local user authentication for telnet sessions. If this
happens, the switch cannot be accessed via telnet. This does not occur with the default RADIUS timeout
configuration of 3 seconds, or when using alternate session types such as console, SSH, or Vista
management (PD2-109828821).
TACACS+ and RADIUS
If TACACS or RADIUS is enabled, but access to the TACACS/RADIUS primary and secondary server
fails, the switch uses its local database for authentication.
Network Login and Saving the Configuration
If you save the configuration on a switch while there are open authenticated Network Login sessions,
all those sessions will become unauthenticated. This occurs to prevent the authenticated ports from
being permanently saved in the authenticated VLAN (1-981ML).
The show netlogin Command Output
If you remove a module with configured Network Login ports and reboot the switch, the output of the
show netlogin command incorrectly omits the configured ports. Network Login remains enabled on
the configured ports and operates correctly if you reinstall the module (PD2-92593101).
Flow Redirection
Enumeration Mode Redirects ICMP Packets
When you create a flow redirection rule for source address based on a subnet mask of /24, enumeration
mode is selected, and all ICMP packets are redirected to the next hop. To work around this, use a
subnet mask of /16 (PD2-118471863).
Cache Servers Set To “Down” Under Sustained High Traffic Loads
Under very high sustained loads flow redirection might fail and set a cache server to the “down” state
and then bring it back up. This only occurs during high loads for a duration of more than 2 minutes.
The server will come back up immediately; however, during that time connections that were established
might be dropped due to a flushing of the associated IP forwarding database entries. A “down” state is
depicted in the log with the following message:
09/01/2000 10:51.56 <INFO:IPRT> redirect next hop test <ip_addr> changed to down
Health Checking Cannot be Disabled
Flow redirection health checking of the next hop address is turned on by default and cannot be
disabled.