The examples in this
section provide the new configurations that are introduced by the MPLS L2VPN
Protocol-Based CLIs feature that replace the existing (legacy) MPLS L2VPN CLIs.
MPLS L2VPN VPWS Configuration Using Replacement (or New)
Commands
The following example
shows the configuration for Virtual Private Wired Service (VPWS)—Ethernet over
Multiprotocol Label Switching (EoMPLS). In this example, L2VPN members point to
peer ID or virtual circuit (VC) ID. This configuration is used in most cases
except when features like quality of service (QoS), need to be applied at the
pseudowire level.
l2vpn xconnect context foo
member GigabitEthernet2/1/1 service-instance 300
member 10.0.0.1 888 encapsulation mpls
!
interface GigabitEthernet2/1/1
service instance 300 Ethernet
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
!
service instance 400 Ethernet
encapsulation dot1q 40
rewrite ingress tag pop 1 symmetric
l2vpn xconnect context faa
member GigabitEthernet2/1/1 service-instance 400
member 10.0.0.1 999 encapsulation mpls
!
MPLS L2VPN Pseudowire Configuration Using Replacement (or New)
Commands
In the following
example, L2VPN members point to a pseudowire interface. The pseudowire
interface is manually configured and includes peer ID and VC ID. This
configuration is used in most cases except when features like quality of
service (QoS), need to be applied at the pseudowire level.
l2vpn xconnect context foo
member GigabitEthernet2/1/1 service-instance 300
member Pseudowire888
!
interface Pseudowire 888
encapsulation mpls
neighbor 10.0.0.1 888
!
interface Pseudowire 999
encapsulation mpls
neighbor 10.0.0.1 999
!
interface GigabitEthernet2/1/1
service instance 300 Ethernet
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
!
service instance 400 Ethernet
encapsulation dot1q 40
rewrite ingress tag pop 1 symmetric
l2vpn xconnect context faa
member GigabitEthernet2/1/1 service-instance 400
member Pseudowire 999
!
MPLS L2VPN Pseudowire
Redundancy Configuration Using Replacement (or New) Commands
The following example
shows the configuration for pseudowire redundancy. The new configuration shows
concise pseudowire redundancy with no submodes or separate groups. This
configuration allows the addition of redundant members to a service without
service disruption. This configuration also allows modifying or deleting
redundant service configurations without service disruption.
l2vpn xconnect context sample-pw-redundancy
member GigabitEthernet2/1/1 service-instance 200
member 1.1.1.1 180 encap mpls group Denver
member 2.2.2.2 180180 encap mpls group Denver priority 1
member 3.3.3.3 180181 encap mpls group Denver priority 2
redundancy delay 1 20 group Denver
!
interface GigabitEthernet2/1/1
service instance 200 Ethernet
encapsulation dot1q 100
rewrite ingress tag pop 1 symmetric
MPLS L2VPN Static Pseudowire Configuration Using Replacement
(or New) Commands
Note |
The following
configuration is shown for the Provider Edge (PE) 1 router in a network scheme
where Customer Edge (CE) 1 and PE 1 and PE 2 and CE 2 traverse through a
Provider core (P) router (CE 1—PE 1—P—PE 2—CE 2).
|
interface g2/1/1
service instance 300 ethernet
encapsulation dot1q 300
no shutdown
!
interface pseudowire 100
neighbor 10.4.4.4 121
encapsulation mpls
label 200 300
signaling protocol none
no shutdown
!
l2vpn xconnect context foo
member GigabitEthernet2/1/1 service-instance 300
member pseudowire 100
MPLS L2VPN Static Pseudowire Template Configuration Using
Replacement (or New) Commands
Note |
The following
configuration is shown for the Provider Edge (PE) 1 router in a network scheme
where Customer Edge (CE) 1 and PE 1 and PE 2 and CE 2 traverse through a
Provider core (P) router (CE 1—PE 1—P—PE 2—CE 2).
|
template type pseudowire test
encapsulation mpls
signaling protocol none
!
interface g2/1/1
service instance 300 ethernet
encapsulation dot1q 300
no shutdown
!
interface pseudowire 100
neighbor 10.4.4.4 121
source template type pseudowire test
label 200 300
no shutdown
!
l2vpn xconnect context foo
member GigabitEthernet2/1/1 service-instance 300
member pseudowire 100
MPLS L2VPN Dynamic Pseudowire
Template Configuration Using Replacement (or New) Commands
Note |
The following
configuration is shown for the Provider Edge (PE) 1 router in a network scheme
where Customer Edge (CE) 1 and PE 1 and PE 2 and CE 2 traverse through a
Provider core (P) router (CE 1—PE 1—P—PE 2—CE 2).
|
template type pseudowire test
encapsulation mpls
signaling protocol ldp
!
!
interface g2/1/1
service instance 300 ethernet
encapsulation dot1q 300
no shutdown
!
interface pseudowire 100
neighbor 10.4.4.4 121
source template type pseudowire test
no shutdown
!
l2vpn xconnect context foo
member GigabitEthernet2/1/1 service-instance 300
member pseudowire 100
MPLS L2VPN Multi-segment
Static-Dynamic Pseudowire Template Configuration Using Replacement (or New)
Commands
The following PE
router configuration is for a multi-segment static-dynamic pseudowire:
l2vpn pseudowire tlv template TLV
tlv mtu 1 4 dec 1500
!
interface pseudowire401
source template type pseudowire staticTempl
encapsulation mpls
neighbor 10.4.4.4 101
signaling protocol none
label 4401 4301
pseudowire type 4
tlv template TLV
tlv 1 4 dec 1500
tlv vccv-flags C 4 hexstr 0110
!
interface pseudowire501
source template type pseudowire dynTempl
encapsulation mpls
neighbor 10.2.2.2 101
signaling protocol ldp
Displaying MPLS L2VPN
Pseudowire Template Configuration Using Replacement (or New)
Commands
The following example
displays output from the
show interface
pseudowire command:
PE1#show interface pseudowire 100
pseudowire100 is up
Description: Pseudowire Interface
MTU 1500 bytes, BW 10000000 Kbit
Encapsulation mpls
Peer IP 10.4.4.4, VC ID 121
RX
21 packets 2623 bytes 0 drops
TX
20 packets 2746 bytes 0 drops
The following example
displays output from the
show template
command:
PE1#show template
Template class/type Component(s)
ABC owner interface pseudowire
BOUND: pw1
Sourcing a Template Under an Interface Pseudowire Using
Replacement (or New) Commands
The following example
configures the interface pseudowire to inherit all attributes defined from a
template on the PE 2 router.
PE2(config-subif)#interface pseudowire 100
PE2(config-if)#source template type pseudowire test
PE2(config-if)#neighbor 10.4.4.4 121
PE2(config-if)#no shutdown
Feedback