Description

Ethernet Ring Protection (ERP) prevents fatal loops in ring network topologies while providing fast protection switching to maintain network stability. Unlike traditional spanning-tree protocols, ERP is specifically optimized for ring architectures, offering more efficient convergence and better resource utilization. ERP works by designating a specific link (Ring Protection Link - RPL) to protect the entire ring, which remains blocked during normal operation and becomes active only when a failure occurs in the ring. This approach ensures no loops form while maintaining network redundancy.

Symptoms

Before deploying ERP, it's essential to understand the requirements, limitations, and key components:

1. Basic Requirements:

  • Minimum of three switches to form a ring topology
  • One designated RPL (Ring Protection Link) owner node in the ring
  • One control VLAN for ERP control traffic
  • Optional data VLANs for user traffic
  • All ERP interfaces must be configured as trunk ports
  • Spanning tree protocols must be disabled on ERP interfaces

2. Platform-Specific Limitations:

  • EX2300/EX3400:
    • Wait to Restore (WTR) timer must be 5-12 minutes
    • Wait to Block (WTB) timer is always disabled (ERPv1 limitation)
    • Maximum combined instances with MSTP: 50 for EX2300, 100 for EX3400
    • Cannot mix ERP interfaces with STP/RSTP/MSTP
    • ERP control VLAN and data VLAN cannot be part of the MST instance
  • Legacy EX Series:
    • ERPS reacts to logical interface status changes
  • EX4300 and QFX Series:
    • ERPS reacts only to physical interface status changes

3. Key Components and States:

  • Node States:
    • init: Node is not participating in the ring
    • idle: Normal operation, no failures (RPL owner blocks RPL, other ports forward)
    • protection: Failure detected, the ring is broken (RPL owner unblocks RPL)
    • pending: Node recovering from failure or manual command (WTR/WTB timer running)
    • force switch: Manual intervention forcing specific link blocking
    • manual switch: Manual traffic path modification

4. Incompatibilities:

  • Cannot configure redundant trunk groups on ERP interfaces
  • VSTP can coexist only if using different VLANs than ERP control/data VLANs
  • Total ERPS and VSTP/MSTP instances are limited to 253 (platform-specific limits apply)

Solution

1. Pre-Configuration Considerations:

  • RPL Owner Selection:
    • Choose a switch with high-availability features when possible
    • Consider the physical location in the ring for optimal traffic flow
    • Ensure the selected switch has stable power and environment
    • Avoid switches that frequently require maintenance/updates
  • Ring Port Selection:
    • Use dedicated interfaces for ring connections
    • Avoid interfaces that share bandwidth with other critical services
    • Consider interface speed and capability matching between nodes

 

2. NON-ELS Configuration Steps:

# A. Disable xSTP on ERP interfaces (required)
[edit protocols]
set rstp interface ge-0/0/0 disable
set rstp interface ge-0/0/1 disable

# B. Configure VLANs (control and data)
set vlans erp-control-vlan vlan-id 100
set vlans erp-data-vlan-1 vlan-id 101

#C. Configure the EAST and WEST interfaces on RPL Owner Node & Regular Nodes

set interfaces ge-0/0/3 flexible-vlan-tagging
set interfaces ge-0/0/3 unit 0 family ethernet-switching port-mode trunk
set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members 100-101
set interfaces ge-0/0/4 flexible-vlan-tagging
set interfaces ge-0/0/4 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/4 unit 0 family ethernet-switching vlan members 100-101

# D. Configure RPL Owner Node
set protocols protection-group ethernet-ring erp1
set protocols protection-group ethernet-ring erp1 ring-protection-link-owner
set protocols protection-group ethernet-ring erp1 control-vlan erp-control-vlan
set protocols protection-group ethernet-ring erp1 data-channel vlan erp-data-vlan-1
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/0.0
set protocols protection-group ethernet-ring erp1 east-interface ring-protection-link-end
set protocols protection-group ethernet-ring erp1 west-interface control-channel ge-0/0/1.0

# E. Configure Regular Nodes
set protocols protection-group ethernet-ring erp1
set protocols protection-group ethernet-ring erp1 control-vlan erp-control-vlan
set protocols protection-group ethernet-ring erp1 data-channel vlan erp-data-vlan-1
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/0.0
set protocols protection-group ethernet-ring erp1 west-interface control-channel ge-0/0/1.0

 

3. ELS Configuration Steps: 

# A. Disable xSTP on ERP interfaces (version dependent)
## For Junos 15.1 or later:
set protocols rstp interface ge-0/0/0 disable
set protocols rstp interface ge-0/0/1 disable
## For Junos prior to 15.1:
delete rstp interface ge-0/0/0
delete rstp interface ge-0/0/1

# B. Configure VLANs (control and data)
set vlans erp-control-vlan vlan-id 100
set vlans erp-data-vlan-1 vlan-id 101

#C. Configure the EAST and WEST interfaces on RPL Owner Node & Regular Nodes

set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members 100-101
set interfaces ge-0/0/1 flexible-vlan-tagging
set interfaces ge-0/0/1 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members 100-101

# D. Configure RPL Owner Node
set protocols protection-group ethernet-ring erp1
set protocols protection-group ethernet-ring erp1 ring-protection-link-owner
set protocols protection-group ethernet-ring erp1 control-vlan 100
set protocols protection-group ethernet-ring erp1 data-channel vlan 101
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/0.0
set protocols protection-group ethernet-ring erp1 east-interface ring-protection-link-end
set protocols protection-group ethernet-ring erp1 east-interface control-channel vlan 100
set protocols protection-group ethernet-ring erp1 west-interface control-channel ge-0/0/1.0
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100

# E. Configure Regular Nodes
set protocols protection-group ethernet-ring erp1
set protocols protection-group ethernet-ring erp1 control-vlan 100
set protocols protection-group ethernet-ring erp1 data-channel vlan 101
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/0.0
set protocols protection-group ethernet-ring erp1 east-interface control-channel vlan 100
set protocols protection-group ethernet-ring erp1 west-interface control-channel ge-0/0/1.0
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100

 

4. Troubleshooting Steps: 

  • Verify Basic Configuration:
    • Check ERP configuration: show configuration protocols protection-group
    • Verify interface status: show interfaces terse
    • Review ring status: show protection-group ethernet-ring interface brief
  • Monitor Ring State:
    • Check node state: show protection-group ethernet-ring node-state
    • Review statistics: show protection-group ethernet-ring statistics
    • Verify detailed interface status: show protection-group ethernet-ring interface detail
  • Enable Debug Logging:

set protocols protection-group traceoptions file ERP.tr
set protocols protection-group traceoptions file size 5m
set protocols protection-group traceoptions file files 5
set protocols protection-group traceoptions flag all

 

Common Issues to Check:

  1. Verify that RSTP is properly disabled on all ERP interfaces
  2. Ensure the control VLAN is properly configured and consistent across all nodes
  3. Check that the RPL owner and RPL end are correctly configured on the appropriate nodes
  4. Verify interface status is operationally up on all ring ports
  5. Confirm VLAN configuration matches on all nodes in the ring
  6. Check for any physical connectivity issues or interface errors

Modification History

02-02-2025 - KB created