Prerequisites for Routed Pseudowire and VPLS
-
MTU must be manually configured for MPLS enabled interfaces.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Routed Pseudowire and VPLS feature routes Layer 3 traffic and Layer 2 frames for pseudowire connections between provider edge (PE) devices using Virtual Private LAN Services (VPLS) multipoint PE.
MTU must be manually configured for MPLS enabled interfaces.
MPLS is not supported over routed VPLS in releases prior to Cisco IOS XE 16.6.1
Maximum number of routed VPLS supported per system is 128.
Maximum number of pseudowires supported per bridge domain is 62.
Layer 2 and Layer 3 multicast are not supported.
ACL on the core network is not supported.
PBR is not supported.
MTU check is not supported. MTU must be manually configured for MPLS enabled interfaces.
Routed Pseudowire and VPLS configuration can route Layer 3 traffic as well as Layer 2 frames for pseudowire connections between provider edge (PE) devices using Virtual Private LAN Services (VPLS) multipoint PE. The ability to route frames to and from these interfaces supports termination of pseudowires into the Layer 3 network (VPN or global) on the same switch, or to the tunnel Layer 3 frames over a Layer 2 tunnel (VPLS).
To configure routing support for a pseudowire, configure the IP address and other Layer 3 features for the Layer 3 domain in interface configuration mode.
Note |
BFD over BDI is supported with routed VPLS configuration. |
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
interface bdi bdi-number Example:
|
Configures the bridge domain interface. |
Step 4 |
ip address ip address subnet mask Example:
|
Specifies the IP address for the bridge domain. |
Step 5 |
no shut Example:
|
Enables the bridge domain interface. |
Step 6 |
end Example:
|
Exits interface configuration mode. |
The virtual forwarding interface (VFI) specifies the VPN ID of a Virtual Private LAN Services (VPLS) domain, the addresses of other provider edge (PE) devices in the domain, and the type of tunnel signaling and encapsulation mechanism for each peer. Perform this task to configure a VFI:
Note |
Only Multiprotocol Label Switching (MPLS) encapsulation is supported. |
Note |
You must configure BDI on the bridge domain that has the association with the VFI. |
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
||
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
||
Step 3 |
l2 vfi name manual Example:
|
Establishes a Layer 2 VPN (L2VPN) virtual forwarding interface (VFI) between two or more separate networks and enters VFI configuration mode. |
||
Step 4 |
vpn id vpn-id Example:
|
Configures a VPN ID for a VPLS domain.
|
||
Step 5 |
neighbor remote-router-id vc-id {encapsulation encapsulation-type | pw-class pw-name } [no-split-horizon ] Example:
|
Specifies the type of tunnel signaling and encapsulation mechanism for each VPLS peer.
|
||
Step 6 |
bridge-domain bd-id Example:
|
Specifies a bridge domain. |
||
Step 7 |
end Example:
|
Exits VFI configuration mode and returns to privileged EXEC mode. |
The example configures the IP address on a BDI interface and associates the interface to a VFI.
!
interface GigabitEthernet0/0/0
service instance 3 ethernet
encapsulation dot1q 3000
rewrite ingress tag pop 1 symmetric
bridge-domain 100
!
interface BDI100
ip address 24.24.24.24 255.255.255.0
no shut
!
l2 vfi TEST manual
vpn id 100
bridge-domain 100
neighbor 9.9.9.9 encapsulation mpls
!