Ethernet Automatic Protection Switching
Steady State
In steady state when the common link is up, both the controller and partner are said to be in the
"ready" state. After EAPS has converged and the EAPS master node has blocked its own secondary
ports, the controller puts all its ports into "forwarding," and goes back to "ready" state.
Figure 24: Multiple EAPS domain steady state
S4
Figure 24
shows a multiple EAPS domain steady state, where:
EAPS1 is the EAPS domain for ring S1, S3, S4, S5, and S2
●
EAPS2 is the EAPS domain for ring S1, S6, S7, S8, and S2
●
EAPS3 is the EAPS domain for ring S1, S9, S10, S11, and S2
●
P1, P2, P3, and P4 are the ports on switch S1
●
P5, P6, P7, and P8 are the ports on switch S2
●
S5, S8, and S11 are the master nodes of their respective EAPS domains
●
S3, S4, S6, S7, S9, and S10 are the transit nodes of their respective EAPS domains
●
S1 and S2 are running EAPSv2
●
S1 is the controller
●
S2 is the partner
●
P1 is the EAPS shared port on switch S1
●
P5 is the EAPS shared port on switch S2
●
Link ID 10 is the unique identifier for the common link
●
Common Link Failures
If a single common link fails, the configured controller (S1) and partner (S2) take steps to prevent a
superloop.
Assuming there is a single data VLAN configured on all three EAPS domains, the controller (S1) keeps
one port open (called "Active-Open"). The remaining segment ports are "blocked" to prevent a
superloop.
In
Figure
25, P2 is the "Active-Open" port on S1. Ports P3 and P4 are "blocked." The master nodes (S5,
S8, and S11) open their secondary ports.
412
S3
P2
S1
Controller
EAPS1
P1
link ID=10
P5
S2
Partner
P6
S5
Master
P3
P4
S6
Common
EAPS2
link
S8
P8
Master
P7
Master
S9
EAPS3
S10
S7
S11
EX_104
ExtremeWare XOS 11.3 Concepts Guide
Need help?
Do you have a question about the ExtremeWare XOS Guide and is the answer not in the manual?