Transition Networks
S4224 Web User Guide
33558 Rev. C
Page 251 of 669
Hold Off Time
The timing value to be used to make persistent check on Signal Fail (SF) before switching. The Hold
off timer valid range is
0
to
10
seconds in steps of 100 ms. The default is
0
.
The holdoff timer is used to allow, for example, a server layer protection switch to have a chance to
fix the problem before switching at a client layer, in order to coordinate timing of protection switches
at multiple layers. When a new defect or more severe defect occurs (new SF), this event is not
reported immediately to protection switching if the provisioned holdoff timer value is non-zero.
Instead, the holdoff timer is started. When the holdoff 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 to protection
switching. The reported defect need not be the same one that started the timer.
Version
Select
v1
or
v2
as the ERPS version to be used. For fields such as Version, OpCode, Flags, and End
TLV, the values used are as defined in ITU-T Y.1731 (Version 0x01 is transmitted per the current
version of this Recommendation at the time of this publication.) G.8032v1 supported a single ring
topology and G.8032v2 supports multiple rings/ladder topology.
v1
: G.8032 v1 supported a single ring topology. The v1 protocol is robust enough to work for
unidirectional failure and multiple link failure scenarios in a ring topology. It allows mechanism to force
switch (FS) or manual switch (MS) to take care of field maintenance scenario.
v2
: G.8032 v2 supports multiple rings/ladder topology. The v2 protocol also introduced other features
such as Revertive/ Non-revertive mode after condition, that is causing the switch, is cleared,
Administrative commands - Forced Switch (FS), Manual Switch (MS) for blocking a particular ring
port, Flush FDB (Filtering database), and support of multiple ERP instances on a single ring.
Revertive
Check the checkbox for Revertive mode operation. Uncheck the checkbox for NonRevertive mode
operation. An Ethernet ring node that has one or more ring ports in an SF condition, upon detection of
clearance of the SF condition, keeps at least one of these ring ports blocked for the traffic channel
and for the R-APS channel, until the RPL is blocked as a result of Ethernet ring protection reversion,
or until there is another higher priority request (e.g., an SF condition) in the Ethernet ring.
Revertive operation: When all ring links and Ethernet ring nodes have recovered and no external
requests are active, reversion is the action to be taken.
Non-revertive operation: the Ethernet ring does not automatically revert when all ring links and
Ethernet ring nodes have recovered and no external requests are active.
Both revertive and non-revertive handling are discussed in Rec. ITU-T G.8032/Y.1344 (03/2010).
Protection switching on a manual switch request is completed when the specified actions are
performed by each Ethernet ring node. At this point, the conditions are created to allow the traffic
flows to be steered around the Ethernet ring.
VLAN config
You can click the VLAN Config hyperlink to display the ERPS VLAN Configuration for the port. See
below for description.
