LevelOne GEL-5261, User Manual

Page: 418 / 570

Chapter 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
– 418 –
■
Recovery with Non-revertive Mode – In non-revertive operation, the
ring does not automatically revert when all ring links and ring nodes
have recovered and no external requests are active. Non-revertive
operation is handled in the following way:
a.
The RPL Owner Node does not generate a response on reception of
an R-APS (NR) messages.
b.
When other healthy ring nodes receive the NR (Node ID) message,
no action is taken in response to the message.
c.
When the operator issues the Clear command (Configure
Operation page) for non-revertive mode at the RPL Owner Node,
the non-revertive operation is cleared, the RPL Owner Node blocks
its RPL port, and transmits an R-APS (NR, RB) message in both
directions, repeatedly.
d.
Upon receiving an R-APS (NR, RB) message, any blocking node
should unblock its non-failed ring port. If it is an R-APS (NR, RB)
message without a DNF indication, all ring nodes flush the FDB.
■
Recovery for Forced Switching – A Forced Switch command is removed
by issuing the Clear command (Configure Operation page) to the same
ring node where Forced Switch mode is in effect. The clear command
removes any existing local operator commands, and triggers reversion
if the ring is in revertive behavior mode.
The ring node where the Forced Switch was cleared continuously
transmits the R-APS (NR) message on both ring ports, informing other
nodes that no request is present at this ring node. The ring nodes stop
transmitting R-APS (NR) messages when they accept an RAPS (NR, RB)
message, or when another higher priority request is received.
If the ring node where the Forced Switch was cleared receives an R-APS
(NR) message with a Node ID higher than its own Node ID, it unblocks
any ring port which does not have an SF condition and stops
transmitting R-APS (NR) message over both ring ports.
■
Recovery with revertive mode is handled as follows:
a.
The reception of an R-APS (NR) message causes the RPL Owner
Node to start the WTB timer.
b.
The WTB timer is cancelled if during the WTB period a higher
priority request than NR is accepted by the RPL Owner Node or
is declared locally at the RPL Owner Node.
c.
When the WTB timer expires, in the absence of any other higher
priority request, the RPL Owner Node initiates reversion by
blocking the traffic channel over the RPL, transmitting an R-APS
(NR, RB) message over both ring ports, informing the ring that
the RPL is blocked, and flushes the FDB.