RAPS received : 1
Local SF happened: : 0
Remote SF happened: : 1
NR event happened: : 0
NR-RB event happened: : 1
Failure Situation—Other Nodes
For Node 2 and Node 3, the outputs should be the same:
user@node2> show protection-group ethernet-ring aps
Ethernet Ring Name Request/state No Flush Ring Protection Link Blocked
pg102 SF No No
Originator Remote Node ID
Yes 00:00:00:00:00:00
user@node2> show protection-group ethernet-ring interface
Ethernet ring port parameters for protection group pg102
Interface Control Channel Forward State Ring Protection Link End
ge-1/2/1 ge-1/2/1.1 forwarding No
ge-1/0/2 ge-1/0/2.1 discarding No
Signal Failure Admin State
Clear IFF ready
set IFF ready
user@node2> show protection-group ethernet-ring node-state
Ethernet ring APS State Event Ring Protection Link Owner
pg102 idle NR-RB No
Restore Timer Quard Timer Operation state
disabled disabled operational
user@node2> show protection-group ethernet-ring statistics group-name pg102
Ethernet Ring statistics for PG pg101
RAPS sent : 1
RAPS received : 1
Local SF happened: : 1
Remote SF happened: : 0
NR event happened: : 0
NR-RB event happened: : 1
Related
Documentation
Ethernet Ring Protection Switching Overview on page 111•
• Understanding Ethernet Ring Protection Switching Functionality on page 112
• Configuring Ethernet Ring Protection Switching on page 118
• Ethernet Interfaces Feature Guide for Routing Devices
Example: Viewing Ethernet Ring Protection Status—Normal Ring Operation
Under normal operating conditions, when Ethernet ring protection is configured correctly,
the ring protection link (RPL) owner (Router 1 in the configuration example) will see the
following:
127Copyright © 2017, Juniper Networks, Inc.
Chapter 4: Configuring Interfaces and Chassis
To Next Page
Loading...
Need help?
General
