Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Example: Viewing Ethernet Ring Protection Status—Ring Failure Condition

    This section assumes that Ethernet ring protection is configuring correctly, that Router 1 is the ring protection link (RPL) owner, and that there is a link failure between Router 2 and Router 3 in the configuration example.

    Router 1 Operational Commands (Ring Failure Condition)

    user@router1> show protection-group ethernet-ring aps
    Ethernet Ring Name  Request/state  No Flush  Ring Protection Link Blocked  
    pg101               SF             NO        No                           
    
    Originator  Remote Node ID
    No          00:01:02:00:00:01 
    

    Note that the ring protection link is no longer blocked and the node is no longer marked as originator.

    user@router1> show protection-group ethernet-ring interface
    Ethernet ring port parameters for protection group pg101
    
    Interface    Control Channel  Forward State  Ring Protection Link End  
    ge-1/0/1     ge-1/0/1.1       forwarding     Yes                      
    ge-1/2/4     ge-1/2/4.1       forwarding     No
                            
    Signal Failure  Admin State
    Clear           IFF ready
    Clear           IFF ready

    Note that the protection interface is now forwarding (so is the other interface).

    user@router1> show protection-group ethernet-ring node-state
    how protection-group ethernet-ring node-state   
    Ethernet ring    APS State    Event         Ring Protection Link Owner
    pg101            protected    SF            Yes                        
      
    Restore Timer  Quard Timer  Operation state
    disabled       disabled     operational  

    Note that Router 1 has recorded the span failure (SF).

    user@router1> show protection-group ethernet-ring statistics group-name pg101
    Ethernet Ring statistics for PG pg101
    RAPS sent                        : 1
    RAPS received                    : 1
    Local SF happened:               : 0
    Remote SF happened:              : 1
    NR event happened:               : 0
    NR-RB event happened:            : 1

    Note that the R-APS messages have recorded the remote failure.

    Under a failure condition, the other routers on the ring (Router 2 and Router 3) will see the following similar output:

    Router 2 and Router 3 Operational Commands (Failure Condition)

    user@router2> 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 

    Note the failure event (SF). Router 3 will see almost identical information.

    user@router2> 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

    Note that the failed interface (ge-1/0/2.1) is not forwarding. Router 3 will see almost identical information.

    user@router2> 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
    

    Note that Router 2 is not the owner. Router 3 will see almost identical information.

    user@router2> show protection-group ethernet-ring statistics group-name pg102
    Ethernet Ring statistics for PG pg102
    RAPS sent                        : 1
    RAPS received                    : 1
    Local SF happened:               : 1
    Remote SF happened:              : 0
    NR event happened:               : 0
    NR-RB event happened:            : 1

    Note that the R-APS messages have recorded the remote failure. Router 3 will see almost identical information.

    Published: 2013-02-13