- play_arrow Common Configuration for All VPNs
- play_arrow VPNs Overview
- play_arrow Assigning Routing Instances to VPNs
- play_arrow Distributing Routes in VPNs
- play_arrow Distributing VPN Routes with Target Filtering
- Configuring BGP Route Target Filtering for VPNs
- Example: BGP Route Target Filtering for VPNs
- Example: Configuring BGP Route Target Filtering for VPNs
- Configuring Static Route Target Filtering for VPNs
- Understanding Proxy BGP Route Target Filtering for VPNs
- Example: Configuring Proxy BGP Route Target Filtering for VPNs
- Example: Configuring an Export Policy for BGP Route Target Filtering for VPNs
- Reducing Network Resource Use with Static Route Target Filtering for VPNs
- play_arrow Configuring Forwarding Options for VPNs
- play_arrow Configuring Graceful Restart for VPNs
- play_arrow Configuring Class of Service for VPNs
- play_arrow Pinging VPNs
-
- play_arrow Common Configuration for Layer 2 VPNs and VPLS
- play_arrow Overview
- play_arrow Layer 2 VPNs Configuration Overview
- play_arrow Configuring Layer 2 Interfaces
- play_arrow Configuring Path Selection for Layer 2 VPNs and VPLS
- play_arrow Creating Backup Connections with Redundant Pseudowires
- play_arrow Configuring Class of Service for Layer 2 VPNs
- play_arrow Monitoring Layer 2 VPNs
- Configuring BFD for Layer 2 VPN and VPLS
- BFD Support for VCCV for Layer 2 VPNs, Layer 2 Circuits, and VPLS
- Configuring BFD for VCCV for Layer 2 VPNs, Layer 2 Circuits, and VPLS
- Connectivity Fault Management Support for EVPN and Layer 2 VPN Overview
- Configure a MEP to Generate and Respond to CFM Protocol Messages
-
- play_arrow Configuring Group VPNs
- play_arrow Configuring Public Key Infrastructure
- play_arrow Configuring Digital Certificate Validation
- play_arrow Configuring a Device for Certificate Chains
- play_arrow Managing Certificate Revocation
-
- play_arrow Configuring VPWS VPNs
- play_arrow Overview
- play_arrow Configuring VPWS VPNs
- Understanding FEC 129 BGP Autodiscovery for VPWS
- Example: Configuring FEC 129 BGP Autodiscovery for VPWS
- Example: Configuring MPLS Egress Protection Service Mirroring for BGP Signaled Layer 2 Services
- Understanding Multisegment Pseudowire for FEC 129
- Example: Configuring a Multisegment Pseudowire
- Configuring the FAT Flow Label for FEC 128 VPWS Pseudowires for Load-Balancing MPLS Traffic
- Configuring the FAT Flow Label for FEC 129 VPWS Pseudowires for Load-Balancing MPLS Traffic
-
- play_arrow Configuring VPLS
- play_arrow Overview
- play_arrow VPLS Configuration Overview
- play_arrow Configuring Signaling Protocols for VPLS
- VPLS Routing and Virtual Ports
- BGP Signaling for VPLS PE Routers Overview
- Control Word for BGP VPLS Overview
- Configuring a Control Word for BGP VPLS
- BGP Route Reflectors for VPLS
- Interoperability Between BGP Signaling and LDP Signaling in VPLS
- Configuring Interoperability Between BGP Signaling and LDP Signaling in VPLS
- Example: VPLS Configuration (BGP Signaling)
- Example: VPLS Configuration (BGP and LDP Interworking)
- play_arrow Assigning Routing Instances to VPLS
- Configuring VPLS Routing Instances
- Configuring a VPLS Routing Instance
- Support of Inner VLAN List and Inner VLAN Range for Qualified BUM Pruning on a Dual-Tagged Interface for a VPLS Routing Instance Overview
- Configuring Qualified BUM Pruning for a Dual-Tagged Interface with Inner VLAN list and InnerVLAN range for a VPLS Routing Instance
- Configuring a Layer 2 Control Protocol Routing Instance
- PE Router Mesh Groups for VPLS Routing Instances
- Configuring VPLS Fast Reroute Priority
- Specifying the VT Interfaces Used by VPLS Routing Instances
- Understanding PIM Snooping for VPLS
- Example: Configuring PIM Snooping for VPLS
- VPLS Label Blocks Operation
- Configuring the Label Block Size for VPLS
- Example: Building a VPLS From Router 1 to Router 3 to Validate Label Blocks
- play_arrow Associating Interfaces with VPLS
- play_arrow Configuring Pseudowires
- Configuring Static Pseudowires for VPLS
- VPLS Path Selection Process for PE Routers
- BGP and VPLS Path Selection for Multihomed PE Routers
- Dynamic Profiles for VPLS Pseudowires
- Use Cases for Dynamic Profiles for VPLS Pseudowires
- Example: Configuring VPLS Pseudowires with Dynamic Profiles—Basic Solutions
- Example: Configuring VPLS Pseudowires with Dynamic Profiles—Complex Solutions
- Configuring the FAT Flow Label for FEC 128 VPLS Pseudowires for Load-Balancing MPLS Traffic
- Configuring the FAT Flow Label for FEC 129 VPLS Pseudowires for Load-Balancing MPLS Traffic
- Example: Configuring H-VPLS BGP-Based and LDP-Based VPLS Interoperation
- Example: Configuring BGP-Based H-VPLS Using Different Mesh Groups for Each Spoke Router
- Example: Configuring LDP-Based H-VPLS Using a Single Mesh Group to Terminate the Layer 2 Circuits
- Example: Configuring H-VPLS With VLANs
- Example: Configuring H-VPLS Without VLANs
- Configure Hot-Standby Pseudowire Redundancy in H-VPLS
- Sample Scenario of H-VPLS on ACX Series Routers for IPTV Services
- play_arrow Configuring Multihoming
- VPLS Multihoming Overview
- Advantages of Using Autodiscovery for VPLS Multihoming
- Example: Configuring FEC 129 BGP Autodiscovery for VPWS
- Example: Configuring BGP Autodiscovery for LDP VPLS
- Example: Configuring BGP Autodiscovery for LDP VPLS with User-Defined Mesh Groups
- VPLS Multihoming Reactions to Network Failures
- Configuring VPLS Multihoming
- Example: VPLS Multihoming, Improved Convergence Time
- Example: Configuring VPLS Multihoming (FEC 129)
- Next-Generation VPLS for Multicast with Multihoming Overview
- Example: Next-Generation VPLS for Multicast with Multihoming
- play_arrow Configuring Point-to-Multipoint LSPs
- play_arrow Configuring Inter-AS VPLS and IRB VPLS
- play_arrow Configuring Load Balancing and Performance
- Configuring VPLS Load Balancing
- Configuring VPLS Load Balancing Based on IP and MPLS Information
- Configuring VPLS Load Balancing on MX Series 5G Universal Routing Platforms
- Example: Configuring Loop Prevention in VPLS Network Due to MAC Moves
- Understanding MAC Pinning
- Configuring MAC Pinning on Access Interfaces for Bridge Domains
- Configuring MAC Pinning on Trunk Interfaces for Bridge Domains
- Configuring MAC Pinning on Access Interfaces for Bridge Domains in a Virtual Switch
- Configuring MAC Pinning on Trunk Interfaces for Bridge Domains in a Virtual Switch
- Configuring MAC Pinning for All Pseudowires of the VPLS Routing Instance (LDP and BGP)
- Configuring MAC Pinning on VPLS CE Interface
- Configuring MAC Pinning for All Pseudowires of the VPLS Site in a BGP-Based VPLS Routing Instance
- Configuring MAC Pinning on All Pseudowires of a Specific Neighbor of LDP-Based VPLS Routing Instance
- Configuring MAC Pinning on Access Interfaces for Logical Systems
- Configuring MAC Pinning on Trunk Interfaces for Logical Systems
- Configuring MAC Pinning on Access Interfaces in Virtual Switches for Logical Systems
- Configuring MAC Pinning on Trunk Interfaces in Virtual Switches for Logical Systems
- Configuring MAC Pinning for All Pseudowires of the VPLS Routing Instance (LDP and BGP) for Logical Systems
- Configuring MAC Pinning on VPLS CE Interface for Logical Systems
- Configuring MAC Pinning for All Pseudowires of the VPLS Site in a BGP-Based VPLS Routing Instance for Logical Systems
- Configuring MAC Pinning on All Pseudowires of a Specific Neighbor of LDP-Based VPLS Routing Instance for Logical Systems
- Example: Prevention of Loops in Bridge Domains by Enabling the MAC Pinnning Feature on Access Interfaces
- Example: Prevention of Loops in Bridge Domains by Enabling the MAC Pinnning Feature on Trunk Interfaces
- Configuring Improved VPLS MAC Address Learning on T4000 Routers with Type 5 FPCs
- Understanding Qualified MAC Learning
- Qualified Learning VPLS Routing Instance Behavior
- Configuring Qualified MAC Learning
- play_arrow Configuring Class of Service and Firewall Filters in VPLS
- play_arrow Monitoring and Tracing VPLS
-
- play_arrow Connecting Layer 2 VPNs and Circuits to Other VPNs
- play_arrow Connecting Layer 2 VPNs to Other VPNs
- play_arrow Connecting Layer 2 Circuits to Other VPNs
- Using the Layer 2 Interworking Interface to Interconnect a Layer 2 Circuit to a Layer 2 VPN
- Applications for Interconnecting a Layer 2 Circuit with a Layer 2 Circuit
- Example: Interconnecting a Layer 2 Circuit with a Layer 2 VPN
- Example: Interconnecting a Layer 2 Circuit with a Layer 2 Circuit
- Applications for Interconnecting a Layer 2 Circuit with a Layer 3 VPN
- Example: Interconnecting a Layer 2 Circuit with a Layer 3 VPN
-
- play_arrow Configuration Statements and Operational Commands
ON THIS PAGE
Example: Configuring Layer 2 Circuit Switching Protection
Unlike Layer 2 circuit protect interfaces (see Example: Configuring Layer 2 Circuit Protect Interfaces), which provide traffic protection for paths configured between the PE routers and CE routers, Layer 2 circuit switching protection provides traffic protection for the paths configured between the PE routers. In the event the path used by a Layer 2 circuit fails, traffic can be switched to an alternate path (or protection path). Switching protection is supported for locally switched Layer 2 circuits and provides 1 to 1 protection for each Layer 2 circuit interface.
When you enable Layer 2 circuit switching protection, each Layer 2 circuit interface requires the following paths:
Working path—Used by the Layer 2 circuit when working normally.
Protection path—Used by the Layer 2 circuit when the working path fails.
Requirements
This example uses the following hardware and software components:
MX Series 5G Universal Routing Platforms
Junos OS Release 12.3
Overview
Each working path can be configured to have a either a protection path routed directly to the neighboring PE router (as shown in Figure 1) or indirectly using a pseudowire configured through an intermediate PE router (as shown in Figure 2 and Figure 3). The protection path provides failure protection for the traffic flowing between the PE routers. Ethernet OAM monitors the status of these paths. When OAM detects a failure, it reroutes the traffic from the failed working path to the protection path. You can configure OAM to revert the traffic automatically to the working path when it is restored. You can also manually switch traffic between the working path, the protection path, and back.
Non-stop routing (NSR) and graceful routing engine switchover (GRES) do not support Layer 2 circuit switching protection.
Topology
Figure 1 illustrates Layer 2 circuit local switching. There are two OAM sessions running between Router PE1 and Router PE2. One OAM session is configured over the working path and the other is configured over the protection path.
In Figure 2 and Figure 3, there are two OAM sessions running between Router PE1 and Router PE2. For Figure 2, one OAM session is configured over the working path between Router PE1 and Router PE2. The other OAM session is configured over the protection path between Router PE1 and Router PE3 to Router PE2.
For Figure 3, one OAM session is configured over the working path, the pseudowire between Router PE1 and Router PE3, then to Router PE2. The other OAM session is configured on the protect path between Router PE1 and Router PE2.
Configuration
The following sections describe how to configure each of the variations of Layer 2 circuit connection protection:
- Configuring Connection Protection Between Two PE Routers
- Verifying that OAM CFM Connections are Active
- Configuring Connection Protection Using Another PE Router for the Protection Path
- Verifying that OAM CFM Connections are Active
- Configuring Connection Protection Using an Another PE Router for the Working Path
- Verifying that OAM CFM Connections are Active
Configuring Connection Protection Between Two PE Routers
Step-by-Step Procedure
To configure Layer 2 Circuit switching protection as shown in Figure 1 on Router PE1:
Configure the Layer 2 circuit on Router PE1.
content_copy zoom_out_map[edit protocols l2circuit] user@PE1# set local-switching interface ge-2/0/2.0 connection-protection user@PE1# set local-switching interface ge-2/0/2.0 end-interface interface ge-2/0/1.0 user@PE1# set local-switching interface ge-2/0/2.0 end-interface backup-interface ge-2/0/1.1
Configure the routing policy on Router PE1.
content_copy zoom_out_map[edit policy-options] user@PE1# set policy-statement protection-policy then load-balance per-packet
Enable the routing policy on Router PE1.
content_copy zoom_out_map[edit routing-options] user@PE1# set forwarding-table export protection-policy
Configure OAM on Router PE1. OAM is used to monitor the working path between Router PE1 and Router PE2. In the event of a failure on the working path, traffic is switched automatically to the protection path. A connectivity fault management (CFM) session is configured on the working path and on the protection path. Begin by configuring the OAM maintenance domain.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md level 5
Configure OAM on Router PE1 for the working path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working continuity-check interval 100ms user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 interface ge-2/0/1.0 user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 interface working user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 direction down user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 remote-mep 103
Configure OAM on Router PE1 for the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection continuity-check interval 100ms user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 interface ge-2/0/1.1 user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 interface protect user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 direction down user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 remote-mep 104
Configure the OAM maintenance domain on Router PE2.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md level 5
Configure OAM on Router PE2 for the working path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working continuity-check interval 100ms user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 interface ge-2/0/1.0 user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 interface working user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 direction down user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 remote-mep 1000
Configure OAM on Router PE2 for the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection continuity-check interval 100ms user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 interface ge-2/0/1.1 user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 interface protect user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 direction down user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 remote-mep 1001
Results
From configuration mode on Router PE1, confirm your configuration by entering the show protocols l2circuit, show policy-options, show routing-options, and show protocols oam ethernet commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
user@host> show protocols l2circuit
local-switching {
interface ge-2/0/2.0 {
connection-protection;
end-interface {
interface ge-2/0/1.0;
backup-interface ge-2/0/1.1;
}
}
}
user@host> show policy-options
policy-statement protection-policy {
then {
load-balance per-packet;
}
}
user@host> show routing-options
forwarding-table {
export protection-policy;
}
user@host> show protocols oam ethernet
connectivity-fault-management {
maintenance-domain l2circuit-example-md {
level 5;
maintenance-association working {
continuity-check {
interval 100ms;
}
mep 1000 {
interface ge-2/0/1.0 working;
direction down;
remote-mep 103;
}
}
maintenance-association protection {
continuity-check {
interval 100ms;
}
mep 1001 {
interface ge-2/0/1.1 protect;
direction down;
remote-mep 104;
}
}
}
}
From configuration mode on Router PE2, confirm your configuration by entering the show protocols oam ethernet commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
connectivity-fault-management {
maintenance-domain l2circuit-example-md {
level 5;
maintenance-association working {
continuity-check {
interval 100ms;
}
mep 103 {
interface ge-2/0/1.0 working;
direction down;
remote-mep 1000;
}
}
maintenance-association protection {
continuity-check {
interval 100ms;
}
mep 104 {
interface ge-2/0/1.1 protect;
direction down;
remote-mep 1001;
}
}
}
}
Verifying that OAM CFM Connections are Active
Purpose
Verify that the CFM connections are active on each of the PE routers.
Action
Execute the following command on each of the PE routers.
Verify that the CFM working connection on Router PE1 is active.
content_copy zoom_out_mapuser@ PE1> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association working Interface status: Active, Link status: Up
Verify that the CFM protect connection on Router PE1 is active
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association protection Interface status: Active, Link status: Up
Verify that the CFM working connection on Router PE2 is active.
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association working Interface status: Active, Link status: Up
Verify that the CFM protect connection on Router PE2 is active.
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association protection Interface status: Active, Link status: Up
Configuring Connection Protection Using Another PE Router for the Protection Path
Step-by-Step Procedure
To configure Layer 2 Circuit switching protection as shown in Figure 2 on Router PE1:
Configure the Layer 2 circuit on Router PE1.
content_copy zoom_out_map[edit protocols l2circuit] user@PE1# set local-switching interface ge-2/0/2.0 connection-protection user@PE1# set local-switching interface ge-2/0/2.0 backup-neighbor 192.0.2.2 virtual-circuit-id 2 user@PE1# set local-switching interface ge-2/0/2.0 backup-neighbor 192.0.2.2 community example user@PE1# set local-switching interface ge-2/0/2.0 end-interface interface ge-2/0/1.0
Configure the routing policy on Router PE1.
content_copy zoom_out_map[edit policy-options] user@PE1# set policy-statement load-balance then load-balance per-packet user@PE1# set policy-statement protection-policy term protect from community example user@PE1# set policy-statement protection-policy term protect then install-nexthop lsp-regex lsp-protect-*
Configure the community.
content_copy zoom_out_map[edit policy-options] user@PE1# set community example members 65100:10
Configure the routing options on Router PE1.
content_copy zoom_out_map[edit routing-options] user@PE1# set forwarding-table export load-balance
Configure OAM on Router PE1 to setup the maintenance domain. OAM is used to monitor the working path between Router PE1 and Router PE2. In the event of a failure on the working path, traffic is switched automatically to the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md level 5
Configure OAM on Router PE1 for the working path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 interface ge-2/0/1.0 user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 direction down user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 remote-mep 103
Configure OAM on Router PE1 for the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 interface ge-2/0/0.0 user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 direction down user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 remote-mep 104
Configure OAM on Router PE2 to setup the maintenance domain.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md level 5
Configure OAM on Router PE2 for the working path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 interface ge-2/0/1.0 user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 direction down user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 remote-mep 1000
Configure OAM on Router PE2 for the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 interface ge-2/0/0.0 user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 direction down user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 remote-mep 1001
Results
From configuration mode on Router PE1, confirm your configuration by entering the show protocols l2circuit, show policy-options, show routing-options, and show protocols oam ethernet commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
user@host> show protocols l2circuit
local-switching {
interface ge-2/0/2.0 {
connection-protection;
backup-neighbor 192.0.2.2 {
virtual-circuit-id 2;
community example;
}
end-interface {
interface ge-2/0/1.0;
}
}
}
user@host> show policy-options
community example members 65100:10;
policy-statement load-balance {
then {
load-balance per-packet;
}
}
policy-statement protection-policy {
term protect {
from community example;
then {
install-nexthop lsp-regex lsp-protect-*;
}
}
}
user@host> show routing-options
forwarding-table {
export load-balance;
}
user@host> show protocols oam ethernet
connectivity-fault-management {
maintenance-domain l2circuit-example-md {
level 5;
maintenance-association working {
mep 1000 {
interface ge-2/0/1.0;
direction down;
remote-mep 103;
}
}
maintenance-association protection {
mep 1001 {
interface ge-2/0/0.0;
direction down;
remote-mep 104;
}
}
}
}
From configuration mode on Router PE2, confirm your configuration by entering the show protocols oam ethernet commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
connectivity-fault-management {
maintenance-domain l2circuit-example-md {
level 5;
maintenance-association working {
mep 103 {
interface ge-2/0/1.0;
direction down;
remote-mep 1000;
}
}
maintenance-association protection {
mep 104 {
interface ge-2/0/0.0;
direction down;
remote-mep 1001;
}
}
}
}
Verifying that OAM CFM Connections are Active
Purpose
Verify that the CFM connections are active on each of the PE routers.
Action
Execute the following command on each of the PE routers.
Verify that the CFM working connection on Router PE1 is active.
content_copy zoom_out_mapuser@ PE1> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association working Interface status: Active, Link status: Up
Verify that the CFM protect connection on Router PE1 is active
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association protection Interface status: Active, Link status: Up
Verify that the CFM working connection on Router PE2 is active.
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association working Interface status: Active, Link status: Up
Verify that the CFM protect connection on Router PE2 is active.
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association protection Interface status: Active, Link status: Up
Configuring Connection Protection Using an Another PE Router for the Working Path
Step-by-Step Procedure
To configure Layer 2 Circuit switching protection as shown in Figure 3 on Router PE1:
Configure the Layer 2 circuit on Router PE1.
content_copy zoom_out_map[edit protocols l2circuit] user@PE1# set neighbor 192.0.2.2 interface ge-2/0/2.0 virtual-circuit-id 2 user@PE1# set neighbor 192.0.2.2 interface ge-2/0/2.0 community example user@PE1# set neighbor 192.0.2.2 interface ge-2/0/2.0 connection-protection user@PE1# set neighbor 192.0.2.2 interface ge-2/0/2.0 backup-neighbor 192.0.2.3 virtual-circuit-id 3 user@PE1# set neighbor 192.0.2.2 interface ge-2/0/2.0 backup-neighbor 192.0.2.3 standby
Configure the policies on Router PE1.
content_copy zoom_out_map[edit policy-options] user@PE1# set policy-statement load-balance then load-balance per-packet user@PE1# set policy-statement protection-policy term protect from community example user@PE1# set policy-statement protection-policy term protect then install-nexthop lsp-regex lsp-primary
Configure the community.
content_copy zoom_out_map[edit policy-options] user@PE1# set community example members 65100:10
Configure the routing options on Router PE1.
content_copy zoom_out_map[edit routing-options] user@PE1# set forwarding-table export load-balance
Configure OAM on Router PE1 to setup the maintenance domain. OAM is used to monitor the working path between Router PE1 and Router PE2. In the event of a failure on the working path, traffic is switched automatically to the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md level 5
Configure OAM on Router PE1 for the working path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 interface ge-2/0/0.0 user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 direction down user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 1000 remote-mep 103
Configure OAM on Router PE1 for the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 interface ge-2/0/1.0 user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 direction down user@PE1# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 1001 remote-mep 104
Configure OAM on Router PE2 to setup the maintenance domain.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md level 5
Configure OAM on Router PE2 for the working path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 interface ge-2/0/0.0 user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 direction down user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association working mep 103 remote-mep 1000
Configure OAM on Router PE2 for the protection path.
content_copy zoom_out_map[edit protocols oam ethernet] user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 interface ge-2/0/1.0 user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 direction down user@PE2# set connectivity-fault-management maintenance-domain l2circuit-example-md maintenance-association protection mep 104 remote-mep 1001
Results
From configuration mode on Router PE1, confirm your configuration by entering the show protocols l2circuit, show policy-options, show routing-options, and show protocols oam ethernet commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
user@host> show protocols l2circuit
neighbor 192.0.2.2 {
interface ge-2/0/2.0 {
virtual-circuit-id 2;
community example;
connection-protection;
backup-neighbor 192.0.2.3 {
virtual-circuit-id 3;
standby;
}
}
}
user@host> show policy-options
community example members 65100:10;
policy-statement load-balance {
then {
load-balance per-packet;
}
}
policy-statement protection-policy {
term protect {
from community example;
then {
install-nexthop lsp-regex lsp-primary;
}
}
}
user@host> show routing-options
forwarding-table {
export load-balance;
}
user@host> show protocols oam ethernet
connectivity-fault-management {
maintenance-domain l2circuit-example-md {
level 5;
maintenance-association working {
mep 1000 {
interface ge-2/0/0.0;
direction down;
remote-mep 103;
}
}
maintenance-association protection {
mep 1001 {
interface ge-2/0/1.0;
direction down;
remote-mep 104;
}
}
}
}
From configuration mode on Router PE2, confirm your configuration by entering the show protocols oam ethernet commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
connectivity-fault-management {
maintenance-domain l2circuit-example-md {
level 5;
maintenance-association working {
mep 103 {
interface ge-2/0/0.0;
direction down;
remote-mep 1000;
}
}
maintenance-association protection {
mep 104 {
interface ge-2/0/1.0;
direction down;
remote-mep 1001;
}
}
}
}
Verifying that OAM CFM Connections are Active
Purpose
Verify that the CFM connections are active on each of the PE routers.
Action
Execute the following command on each of the PE routers.
Verify that the CFM working connection on Router PE1 is active.
content_copy zoom_out_mapuser@ PE1> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association working Interface status: Active, Link status: Up
Verify that the CFM protect connection on Router PE1 is active
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association protection Interface status: Active, Link status: Up
Verify that the CFM working connection on Router PE2 is active.
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association working Interface status: Active, Link status: Up
Verify that the CFM protect connection on Router PE2 is active.
content_copy zoom_out_mapuser@ PE2> show oam ethernet connectivity-fault-management mep-database maintenance-domain l2circuit-example-md maintenance-association protection Interface status: Active, Link status: Up
