Specifications

48 ExtremeWare 7.0 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
1 The EAPS ring fails, due to a Hello timeout or a link failure.
2 The EAPS master node secondary port fails or is disabled.
3 The EAPS master node secondary port recovers or is re-enabled. The port incorrectly blocks
incoming traffic even though it is enabled.
ESRP and EAPS Secondary Port
Configuring ESRP Host Attach on an EAPS secondary port causes a broadcast storm (1-B1O4L).
Incorrect show vlan Output
The show vlan output incorrectly lists the EAPS secondary port as active with an asterisk (*). The
number of active ports is correctly displayed (PD2-59142420).
ESRP
Configure a Neighbor Timeout Less than 6 Times Hello Timer
If you configure the neighbor timeout to greater than six times the hello timer, and the link between the
master and the slave goes down, the slave might not immediately flush the FDB table. To avoid this,
configure a neighbor timeout less than six times the hello timer. To correct this situation, manually clear
the FDB (PD2-124371801).
Transition Incorrectly Logged
If you change the priority of the ESRP master to 255, in rare situations it might change to slave,
transition back to master, then finally transition to slave (PD2-129379243).
Dual Master Recovery Not Logged
When two switches recover from a dual-master situation, in rare situations the new master might not
log the state change (PD2-111406501).
A Flapping Redundant Link Might Cause ESRP to Fail Over
A flapping redundant link might cause the port counter to increase its count on the neigbor’s side,
increasing the neighbor's port count. This could cause an ESRP state transition. To avoid this, disable
smart redundancy (PD2-111264407).
ESRP and Ingress Rate Shaping
Do not use ingress rate shaping on an ESRP-enabled port (PD2-107800933).
ESRP and Protocol-Based VLANs
ESRP-aware switches cannot connect to an ESRP switch through a port configured for a
protocol-sensitive VLAN using untagged traffic (PD2-99007701).