Maipu and Cisco - MPLS L2VPN and AToM

As discussed in last post about MPLS L2VPN. In this post we will see the configuration for Cisco and Maipu Router both.First of all this technology is known as AToM (Any Traffic over MPLS).

            In this example I tested Maipu 3840 and Cisco 1841. I only taken two routers, simulating that these are acting as PE. Here I shown computers , Both are in same subnet. That means over MPLS cloud we are creating a L2 tunnel.

So that these two laptops can communicate, which are in same subnet.

            In real time this laptops are replaced with Routers and these IP address are assigned to Routers and they can ping each other, It may be /24 or /32. It totally depends on Customer requirement.

For testing and understanding, I feel this is good example. Here you can know how your L2circut is formed from your site to another site.

            In last post, I shown Full setup, This is just for compatibility with Cisco and Maipu. In Cisco little bit more configuration to setup MPLS L2VPN.

Topology :

Configuration -

Cisco 1841 configuration:

pseudowire-class a
 encapsulation mpls

interface Loopback0
 ip address 18.18.18.18 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
 mpls ip 
mpls label protocol ldp
 xconnect 37.37.37.37 100 pw-class a
!
interface FastEthernet0/1
 ip address 9.0.10.18 255.255.255.0
 duplex auto
 speed auto
 mpls ip
mpls label protocol ldp
!

!
router ospf 1
 log-adjacency-changes
  network 9.0.10.0 0.0.0.255 area 0
 network 18.18.18.18 0.0.0.0 area 0

mpls ldp router-id Loopback0

MP3840 configuration:

ip mef

ip load-sharing per-destination

mpls ip

interface loopback0

 ip address 37.37.37.37 255.255.255.255

 exit

interface gigaethernet0

 ip address 9.0.10.19 255.255.255.0

 mpls ip

 mpls ldp

 exit

interface gigaethernet1

 mpls ip

 xconnect 18.18.18.18 100 encapsulation mpls

 mpls ldp

 exit

                                    

router ospf 1

 router-id 37.37.37.37

 network 9.0.10.0 area 0

 network 37.37.37.37 0.0.0.0 area 0

 exit

mpls ldp

 router-id 37.37.37.37

 transport-address 37.37.37.37

 targeted-peer 18.18.18.18

 exit

-- you are done, yes but many of you thinking its very simple. yes its simple the important is reachability with peer ip address (loopback IP). That means if you face any issue in xconnect, First you have to check IGP status and routing. It use IGP routing to reach peer router. 

Here same example with Maipu to Maipu for better understanding.

MAIPU TO MAIPU

Configurations

MP3780 configuration :

ip mef

ip load-sharing per-destination

mpls ip

           

interface loopback0

 ip address 37.37.37.37 255.255.255.255

 exit

interface gigaethernet0

 ip address 1.1.1.2 255.255.255.0

 mpls ip

 mpls ldp

 exit

interface gigaethernet1

 mpls ip

 xconnect 18.18.18.18 100 encapsulation mpls

 mpls ldp

 exit

                                   

router ospf 1

 router-id 37.37.37.37

 network 1.1.1.0 0.0.0.255 area 0

 network 37.37.37.37 0.0.0.0 area 0

 exit

mpls ldp

 router-id 37.37.37.37

 transport-address 37.37.37.37

 targeted-peer 18.18.18.18

 exit

MP3840 configuration :

ip mef

ip load-sharing per-destination

mpls ip

interface loopback0

 ip address 18.18.18.18 255.255.255.255

 exit

interface gigaethernet0

 ip address 1.1.1.1 255.255.255.0

 mpls ip

 mpls ldp

 exit

interface gigaethernet1

 mpls ip

 xconnect 37.37.37.37 100 encapsulation mpls

 mpls ldp

 exit

                                    

router ospf 1

 router-id 18.18.18.18

 network 1.1.1.0 0.0.0.255 area 0

 network 18.18.18.18 0.0.0.0 area 0

 exit

mpls ldp

 router-id 18.18.18.18

 transport-address 18.18.18.18

 targeted-peer 37.37.37.37

 exit

Hope this information will help you for better understanding about Cisco AToM and Maipu MPLS L2VPN.

For more information about AToM - Click here 

For any feedback and queries, Plz put comment with your Name and Mail id..