More Layer 2 VPN - EoMPLS

Have you ever wondered why we are currently using this technology on various service providers?



 


- Allows service providers to have single infrastructure for both IP and legacy services. 



 
Layer 2 VPNs are complementary to Layer 3 VPN's !!!!!

 

VPLS > MPLS Based

Ethernet Pseudo Wires (EoMPLS)  > MPLS Based

L2TP > IP Based

ATOM > MPLS Based

 

So we can call the pseudo-wire connections is a kind of tunneling mechanisim between PE and PEdevices which connectets different network circuits.

Interworking

Interworking is actually a transforming function that is required to interconnect two heterogeneous ACs, by providing the translation between the different L2 encapsulations.  
Later, I will share an example for Interworking ...


Difference between VPLS and EoMPLS is

  - VPLS is point-to-multipoint
  - EoMPLS is Point to Point


We use xconnect on EoMpls as l2tp configuration.

VPLS use different syntax that I will share an example.

Another difference is ;

The VPLS configuration creates a (integrated routing bridging) bridge in the PE router and adds the created pseudowire to the bridge

EoMPLS does not include such bridge.



So, VPLS uses a bridge to join the pseudowires and the physical interface


EoMPLS uses a xconnect to join a single pseudowire and the physical interface.


PS :

Like QinQ tunneling (802.1q tunneling of switched traffic), EoMPLS just takes the frame that comes in a port (somehow), transports it across the middle, and spits it out the paired port on the other end. There is no examination of MAC address, no learning of source MAC address, in short, no switching logic applied.










EoMPLS LAB :

R8 customer wants to communicate with R9 in same vlan domain (currently 234)

You have MPLS backbone ! and you are going to bind just 2 customer ; the secret answer is
EoMPLS indeed !!!!

EoMPLS sometimes is called like ATOM ( Any Type over MPLS = could be ethernet , FR, ATM .. )
I just like to call it as

Pseudowire Ethernet over MPLS 

 

pe1#
interface Loopback0
 ip address 2.2.2.2 255.255.255.255
 ip ospf network point-to-point
!
interface GigabitEthernet0/0
 ip address 10.0.0.7 255.255.255.252
 mpls label protocol ldp
 mpls ip
!
router ospf 1
 router-id 2.2.2.2
 network 2.2.2.2 0.0.0.0 area 0
 network 10.0.0.0 0.0.0.3 area 0
!
mpls ldp router-id Loopback0 force
!
interface GigabitEthernet0/1.234
 encapsulation dot1Q 234
 xconnect 4.4.4.4 234 encapsulation mpls

pe2#
interface Loopback0
 ip address 4.4.4.4 255.255.255.255
 ip ospf network point-to-point
!
interface GigabitEthernet0/0
 ip address 10.0.0.12 255.255.255.252
 mpls label protocol ldp
 mpls ip

router ospf 1
 router-id 4.4.4.4
 network 4.4.4.4 0.0.0.0 area 0
 network 10.0.0.0 0.0.0.3 area 0
!
mpls ldp router-id Loopback0 force
!
interface GigabitEthernet0/1.234
 encapsulation dot1Q 234
 xconnect 2.2.2.2 234 encapsulation mpls