Configuration Examples for VPWS

Example for Configuring a Local CCC

A local Circuit Cross Connect (CCC) is a connection between two CEs connected to the same PE. The PE functions similar to a Layer 2 switch to directly transmit packets without using LSPs.

Example for Configuring Remote CCC Connections

Remote CCC connections allow a local CE and a remote CE that connect to different PEs to communicate. Static CR-LSP must be configured to transmit packets between the two PEs and be mapped to remote CCC connections.

Example for Configuring Mutual Protection Between a CCC VC and an LDP VC (Single-Homing 2PE Scenario)

This section provides an example for configuring mutual protection between a CCC VC and an LDP VC. Specifying the master/backup status of PEs allows for mutual protection between a CCC VC and an LDP VC.

Example for Configuring Mutual Protection Between a CCC VC and an LDP VC (Dual-Homing 2PE Scenario)

This section provides an example for configuring mutual protection between a CCC VC and an LDP VC. Specifying the master/backup status of PEs allows for mutual protection between a CCC VC and an LDP VC.

Example for Configuring Mutual Protection Between a CCC VC and an LDP VC (Dual-Homing 3PE Scenario)

This section provides an example for configuring mutual protection between a CCC VC and an LDP VC. Specifying the master/backup status of PEs allows for mutual protection between a CCC VC and an LDP VC.

Example for Configuring a Dynamic VPWS SS-PW Using an LSP

This section provides an example for configuring a dynamic VPWS SS-PW using an LSP.

Example for Configuring a Dynamic VPWS SS-PW Using a TE Tunnel

This section provides an example for configuring a dynamic VPWS SS-PW using a TE tunnel.

Example for Configuring a Dynamic VPWS SS-PW over an SRv6 TE Policy

This section provides an example for configuring a dynamic VPWS SS-PW over an SRv6 TE Policy.

Example for Configuring SVC VPWS

An SVC VPWS is a static VPWS, which requires no signaling protocol, but configured VC labels to transmit L2VPN information.

Example for Configuring Inter-AS LDP VPWS Option A

Inter-AS LDP VPWS Option A can be easily deployed and is recommended for scenarios where few inter-AS PWs are required.

Example for Configuring Inter-AS LDP VPWS Option C

Inter-AS LDP VPWS Option C applies to scenarios where each AS requires large numbers of inter-AS PWs. In inter-AS LDP VPWS Option C, PEs in different ASs establish single-segment PWs with each other; ASBRs do not need to create or maintain PWs and therefore will not hinder network expansion.

Example for Configuring Dynamic VPWS Switching

On both ends of a switching PW, two dynamic PWs are configured. Dynamic PWs use the extended LDP to transmit Layer 2 information and VC labels.

Example for Configuring BFD for VPWS PW

Using BFD to detect PW faults involves simple configurations and requires a few packet exchanges.

Example for Configuring a Local BGP VPWS Connection

This section provides an example for configuring a local BGP VPWS connection. If two CEs connect to the same PE, you can configure a local BGP VPWS connection for the two CEs to communicate.

Example for Configuring a Remote BGP VPWS Connection

This section provides an example for configuring a remote BGP VPWS connection. If two CEs connect to different PEs, you can configure a remote BGP VPWS connection for the two CEs to communicate.

Example for Configuring Inter-AS BGP VPWS Option A

This section provides an example for configuring inter-AS LDP VPWS Option A. Inter-AS LDP VPWS Option A can be easily deployed and is recommended for scenarios where few inter-AS PWs are required.

Example for Configuring Inter-AS BGP VPWS Option C

This section provides an example for configuring inter-AS BGP VPWS Option C. In inter-AS BGP VPWS Option C, ASBRs do not need to create or maintain VCs. This solution is recommended for scenarios where large numbers of inter-AS VPWS PWs are required.

Example for Configuring BGP VPWS FRR - Symmetric Access of CEs to PEs

In a VPWS FRR scenario where two CEs are symmetrically dual-homed to PEs, the two CEs can communicate over a pair of primary and secondary VPWS connections.

Example for Configuring BGP VPWS FRR - Asymmetric Access of CEs to PEs

If one CE is single-homed to a PE and another CE is dual-homed to two other PEs, you can configure BGP VPWS FRR for the two CEs to communicate.

Example for Configuring 3PE PW Redundancy When CEs Are Asymmetrically Connected to PEs on Mobile Bearer Networks

In PW redundancy scenarios in which CEs are asymmetrically connected to PEs, the E-Trunk determines the master/backup status of the PEs.

Example for Associating E-VRRP with 4PE PW Redundancy

In 4PE PW redundancy scenarios, the mVRRP status determines the master/backup status of PEs.

Example for Configuring Static PW FRR

In static PW FRR scenarios with static MS-PWs, configuring dynamic BFD for PW helps facilitate traffic switching between primary and secondary PWs.

Example for Configuring E-PW APS for Static SS-PWs

In an E-PW APS scenario, MPLS OAM is used to detect the status of static SS-PWs.

Example for Configuring PW APS for Static MS-PWs

In PW APS scenarios, MPLS OAM is used to detect the status of static MS-PWs.

Example for Configuring E-PW APS for Dynamic SS-PWs

In E-PW APS scenarios, MPLS OAM is used to detect the status of dynamic SS-PWs.

Example for Configuring PW APS for Dynamic MS-PWs

In PW APS scenarios, MPLS OAM is used to detect the status of dynamic MS-PWs.

Example for Configuring MS-PW Redundancy When a PE Is Single-Homed to an SPE Through PWE3

This section provides an example for configuring MS-PW redundancy when a PE is single-homed to an SPE. PW label switching is configured on the SPE to implement MS-PWs in primary/secondary mode.