Cisco Vlan-Mode EoMPLS Configuration

Cisco Vlan-Mode EoMPLS Configuration

In this example, we will configure vlan-mode EoMPLS (Ethernet over Mpls) between Cisco IOS PE routers.

EoMPLS provides a mpls labeled tunneling mechanism for Ethernet traffic through an MPLS enabled network.Ingress PE routers encapsulates Ethernet protocol data units inside MPLS labeled packets and forwards to the remote PE router through the Mpls enabled network.Remote PE router removes the mpls labels and forwards the Ethernet protocol data units to the CE device.

Here is the topology for this example:

 Configurations of Routers:

Configuration of PE-1:
interface Loopback0

 ip address 1.1.1.1 255.255.255.255

 ip ospf 1 area 0

!

interface FastEthernet1/0

 ip address 192.168.13.1 255.255.255.0

 ip ospf 1 area 0

mpls ip 

!        

interface FastEthernet1/1

 no ip address

 !        

interface FastEthernet1/1.10

 encapsulation dot1Q 10

 xconnect 2.2.2.2 100 encapsulation mpls

!        

Configuration of PE-2:

interface Loopback0
 ip address 2.2.2.2 255.255.255.255
 ip ospf 1 area 0
!
!
interface FastEthernet1/0
 ip address 192.168.23.2 255.255.255.0
 ip ospf 1 area 0
 mpls ip
!        
interface FastEthernet1/1

no ip address

!

interface FastEthernet1/1.10

 encapsulation dot1Q 10

 xconnect 1.1.1.1 100 encapsulation mpls

Configuration of CE-1:

interface FastEthernet1/0.10

encapsulation dot1q 10

ip address 12.12.12.1 255.255.255.0

!
router ospf 12
 log-adjacency-changes
 network 12.12.12.0 0.0.0.255 area 0

Configuration of CE-2:

interface FastEthernet1/0.10

encapsulation dot1q 10

ip address 12.12.12.1 255.255.255.0

!

router ospf 12
 log-adjacency-changes
 network 12.12.12.0 0.0.0.255 area 0

Lets test the vlan-mode EoMPLS configurations:

PE-1#show mpls l2transport vc 100 detail

Local interface: Fa1/1.10 up, line protocol up, Eth VLAN 10 up

  Destination address: 2.2.2.2, VC ID: 100, VC status: up

    Output interface: Fa1/0, imposed label stack {17 16}

    Preferred path: not configured 

    Default path: active

    Next hop: 192.168.13.3

  Create time: 00:10:30, last status change time: 00:07:28

  Signaling protocol: LDP, peer 2.2.2.2:0 up

    MPLS VC labels: local 16, remote 16

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  VC statistics:

    packet totals: receive 57, send 61

    byte totals:   receive 5644, send 7542

    packet drops:  receive 0, seq error 0, send 0

We see that targeted ldp session is established between PE-1 and PE-2 routers:

PE-1#show mpls ldp neighbor             

    Peer LDP Ident: 3.3.3.3:0; Local LDP Ident 1.1.1.1:0

        TCP connection: 3.3.3.3.62473 - 1.1.1.1.646

        State: Oper; Msgs sent/rcvd: 19/19; Downstream

        Up time: 00:10:31

        LDP discovery sources:

          FastEthernet1/0, Src IP addr: 192.168.13.3

        Addresses bound to peer LDP Ident:

          192.168.13.3    3.3.3.3         192.168.23.3   

    Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0

        TCP connection: 2.2.2.2.13188 - 1.1.1.1.646

        State: Oper; Msgs sent/rcvd: 19/19; Downstream

        Up time: 00:09:34

        LDP discovery sources:

          Targeted Hello 1.1.1.1 -> 2.2.2.2, active, passive

        Addresses bound to peer LDP Ident:

          2.2.2.2         192.168.23.2 

Reachability between CE routers:

CE-1#ping 12.12.12.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 12.12.12.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 52/68/100 ms


Ospf neighborship between CE routers is established:

CE-1#show ip ospf neighbor
Neighbor ID     Pri   State           Dead Time   Address         Interface
12.12.12.2        1   FULL/DR         00:00:35    12.12.12.2      FastEthernet1/0

We see that vlan-mode EoMPLS configurations on PE routers are working without any problem.