EoMPLS P2P using VLAN rewrite

Scenario
This setup shows an incoming attachment circuit on PE1 with VLAN 10. This is translated to an internal VLAN 32 which is used on an xconnect/pseudowire to PE2 . This is then translated to VLAN 11 before being send out of the attachment circuit on PE2 (not shown). The IOS configuration is using the service instance command under the customer facing interface, whereas XR uses a sub-interface with the l2transport keyword. The pseudowire ID (123) must match on both ends. Verification can be done using the show l2vpn atom vc IOS command or the show l2vpn xconnect XR command.

IOS Config

hostname PE1
!
interface GigabitEthernet1
 no ip address
 service instance 32 ethernet
  encapsulation dot1q 32
  rewrite ingress tag translate 1-to-1 dot1q 10 symmetric
  !
 !
l2vpn xconnect context CONTEXT10
 member GigabitEthernet1 service-instance 32
 member pseudowire32 172.16.2.2 123 encapsulation mpls
!

XR Config

hostname PE1
!
interface GigabitEthernet0/0/0/1.32 l2transport
 encapsulation dot1q 32
 rewrite ingress tag translate 1-to-1 dot1q 10 symmetric
 !
!
l2vpn
 xconnect group GROUP10
  p2p P2P10
   interface GigabitEthernet0/0/0/1.32
   neighbor ipv4 172.16.2.2 pw-id 123
  !
 !
!

Back to top