Table of Contents
Advertisement
Chapter 35: ERPS Commands
non-revertive
When non-ERPS device protection is enabled on an RPL owner node, it
•
will send non-standard health-check packets to poll the ring health
when it enters the protection state. It does not use the normal
procedure of waiting to receive an R-APS (NR - no request) message
from nodes adjacent to the recovered link. Instead, it waits to see if the
non-standard health-check packets loop back. If they do, indicating
that the fault has been resolved, the RPL will be blocked.
After blocking the RPL, the owner node will still transmit an R-APS (NR,
RB - ring blocked) message. ERPS-compliant nodes receiving this
message flush their forwarding database and unblock previously
blocked ports. The ring is now returned to Idle state.
E
XAMPLE
Console(config-erps)#non-erps-dev-protect
Console(config-erps)#
This command enables non-revertive mode, which requires the protection
state on the RPL to manually cleared. Use the no form to restore the
default revertive mode.
S
YNTAX
[no] non-revertive
D
S
EFAULT
ETTING
Disabled
C
M
OMMAND
ODE
ERPS Configuration
C
U
OMMAND
SAGE
•
Revertive behavior allows the switch to automatically return the RPL
from Protection state to Idle state through the exchange of protocol
messages.
Non-revertive behavior for Protection, Forced Switch, and Manual
Switch states are basically the same. Non-revertive behavior requires
the
erps clear
command to used to return the RPL from Protection state
to Idle state.
Recovery for Protection Switching – A ring node that has one or more
•
ring ports in an SF (Signal Fail) condition, upon detecting the SF
condition cleared, keeps at least one of its ring ports blocked for the
traffic channel and for the R-APS channel, until the RPL is blocked as a
result of ring protection reversion, or until there is another higher
priority request (e.g., an SF condition) in the ring.
A ring node that has one ring port in an SF condition and detects the SF
condition cleared, continuously transmits the R-APS (NR – no request)
message with its own Node ID as the priority information over both ring
ports, informing that no request is present at this ring node and
– 1059 –
Advertisement
Table of Contents
