Sliding Timer Expiry to Report Faults to Ethernet Ring Protection Mechanism

  • Karthick RajapandiyanEmail author
  • Ramakrishnan Sundaramoorthy
  • Veerakumar Palanivelayudham
Conference paper
Part of the Lecture Notes on Data Engineering and Communications Technologies book series (LNDECT, volume 36)


The G.8032 Ethernet ring protection (ERP) mechanism detects the failure in a network connected in a ring and will automatically switch traffic path to ensure that uninterrupted traffic provided even in case of a node or path failure. To avoid different race conditions and unnecessary switching operations, it uses different timers. One of such static timers configured today is the hold-off timer. After detecting a failure, ERPS will not switch immediately, and it will wait for this time; if the failure is not cleared before the timer expiry, then actual switching happens. This waiting period is added to avoid unnecessary switching due to link flaps. So even when an actual failure is detected, ERPS will wait till this timer expiry, until then traffic loss will be seen. Currently, the timer range is between 0 and 10 s which is configured by the operator. The default value of this timer is 0 s, and in this case, the timer will be disabled. It is best advised to configure and enable the timer to avoid false reporting, frequent switching, and flapping. But, if the timer is configured very less, frequent unnecessary switching will happen and if the timer is kept very high, traffic loss will be seen for that wait time. The objective of this work is to propose a sliding/adaptive timer expiry algorithm incorporated inside the ERPS module itself instead of a static hold-off timer.


Sliding timer Hold-off timer G.8032 Ethernet ring protection (ERP) Ethernet ring protection mechanism Adaptive timer 


  1. 1.
    Telecommunication standardization sector of ITU, G.8032/Y.1344 (08/2015)Google Scholar
  2. 2.
    IEEE P802.1ah (2008) IEEE standard for local and metropolitan area networks-virtual bridged local area networks-Amendment 6: Provider backbone bridgesGoogle Scholar
  3. 3.
    Ryoo J, Long H, Yang Y, Holness M, Ahmad Z, Rhee J-KK (2008) Ethernet ring protection for carrier Ethernet networks. IEEE Commun Mag 46:136–143CrossRefGoogle Scholar
  4. 4.
    Allan D, Bragg N, McGuire A, Reid A (2006) Ethernet as carrier transport infrastructure. IEEE Commun Mag 44:95–101CrossRefGoogle Scholar
  5. 5.
    Reid Andy, Willis Peter, Hawkins Ian, Bilton Chris (2008) Carrier Ethernet. Commun Mag 46:96–103CrossRefGoogle Scholar
  6. 6.
    Lee D, Rhee JKK, Lee K, Cho P (2009) Efficient ethernet multi-ring protection system. In: IEEE/2009 7th international workshop on design of reliable communication networks yearGoogle Scholar
  7. 7.
    Lee K, Rhee J-KK, Yoo S, Cho P (2011) Flush optimization in ethernet ring protection network. ICTCGoogle Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2020

Authors and Affiliations

  • Karthick Rajapandiyan
    • 1
    Email author
  • Ramakrishnan Sundaramoorthy
    • 1
  • Veerakumar Palanivelayudham
    • 1
  1. 1.Fixed Networks BroadBand Access—CopperNokia Corporation, Alcatel Lucent India LimitedChennaiIndia

Personalised recommendations