Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 568)

538 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
ERP commands
15
This WTR timer is activated on the RPL Owner Node. When the relevant delay timer expires, the RPL
owner initiates the reversion process by transmitting an R-APS (NR, RB) message. The WTR timer is
deactivated when any higher priority request preempts this timer. The WTR timers may be started
and stopped. A request to start running the WTR timer does not restart the WTR timer. A request to
stop the WTR timer stops the WTR timer and resets its value. The Clear command can be used to
stop the WTR timer. While WTR timer is running, the WTR running signal is continuously generated.
After the WTR timer expires, the WTR running signal is stopped, and the WTR Expires signal is
generated. When the WTR timer is stopped by the clear command, the WTR Expires signal is not
generated.
When configured, the RPL owner waits until the timer expires before transmitting the R-APS(NR,RB)
message to initiate the reversion process. While the timer is in effect, the WTR running signal is
continuously generated. You can configure the WTR timer in 1 minute increments from 1 to 12
minutes; the default value is 5 minutes.
This timer can be stopped by issuing the clear erp erp_id wtr-timer command.
Syntax: wtr-time time-value>
Testing the WTR timer
You can enter the fast-wtr-time command to test your configuration. Instead of having to wait 5
minutes for the timer to expire, you wait 5 seconds. This command changes the timer’s unit of
measure from minutes to seconds.
Syntax: [no] fast-wtr-time
Use the no command to return the unit of measure to minutes.
Configuring and clearing the WTB timer
The WTB timer ensures that clearing of a single FS command does not trigger the reblocking of the
RPL when multiple FS situations co-exist in an Ethernet Ring. When recovering from an MS or FS
command, the delay timer must be long enough to receive any latent remote FS or MS.
While it is running, the WTB running signal is continuously generated. The WTB timer is 5000ms (5
seconds) longer than the guard timer. You can configure this timer in 100 ms increments from
5100ms to 7000ms (7 seconds); the default value is 5500ms.
The WTB timer can be stopped through the CLI by entering the clear erp erp_id> wtb-timer
command.
Syntax: wtb-time time-value>
Configuring a hold-off timer
The hold-off timer is used in each ERN to prevent unnecessary Signal Fail events due to port
flapping. If you configure a non-zero hold-off timer value, when a link error occurs, the event will not
be reported immediately. When the hold-off timer expires, ERP checks if the error still exists.
The hold-off timer is used in every ERN. When a new defect occurs (new SF), this event will not be
reported immediately to trigger protection switching if the provisioned hold-off timer value is
non-zero. Instead, the hold-off timer is started. When the hold-off timer expires, the trail that
started the timer is checked as to whether a defect still exists. If one does exist, that defect is
reported and protection switching is triggered.