In this example, we will configure port-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:
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.12.1 255.255.255.0
ip ospf 1 area 0
mpls ip
!
interface FastEthernet1/1
no ip address
xconnect 2.2.2.2 100 encapsulation mpls
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.12.2 255.255.255.0
ip ospf 1 area 0
mpls ip
!
interface FastEthernet1/1
no ip address
xconnect 1.1.1.1 100 encapsulation mpls
CE-1
interface FastEthernet1/0
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
CE-2
interface FastEthernet1/0
ip address 12.12.12.2 255.255.255.0
router ospf 12
log-adjacency-changes
network 12.12.12.0 0.0.0.255 area 0
Lets test the EoMPLS configurations:
PE-2#show mpls l2transport vc det
Local interface: Fa1/1 up, line protocol up, Ethernet up
Destination address: 1.1.1.1, VC ID: 100, VC status: up
Output interface: Fa1/0, imposed label stack {17}
Preferred path: not configured
Default path: active
Next hop: 192.168.12.1
Create time: 00:47:35, last status change time: 00:47:14
Signaling protocol: LDP, peer 1.1.1.1:0 up
MPLS VC labels: local 17, remote 17
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 363, send 638
byte totals: receive 36265, send 75764
packet drops: receive 0, seq error 0, send 0
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 = 92/109/132 ms
CE Routers learn the mac-addresses of each other:
CE-1#show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 12.12.12.1 - ca02.0fdc.001c ARPA FastEthernet1/0
Internet 12.12.12.2 49 ca03.0fdc.001c ARPA FastEthernet1/0
CE-2#show interface f1/0 | inc bia
Hardware is i82543 (Livengood), address is ca03.0fdc.001c (bia ca03.0fdc.001c)
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:36 12.12.12.2 FastEthernet1/0
We see that port-mode EoMPLS configurations on PE routers are working without any problem.
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:
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.12.1 255.255.255.0
ip ospf 1 area 0
mpls ip
!
interface FastEthernet1/1
no ip address
xconnect 2.2.2.2 100 encapsulation mpls
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.12.2 255.255.255.0
ip ospf 1 area 0
mpls ip
!
interface FastEthernet1/1
no ip address
xconnect 1.1.1.1 100 encapsulation mpls
CE-1
interface FastEthernet1/0
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
CE-2
interface FastEthernet1/0
ip address 12.12.12.2 255.255.255.0
router ospf 12
log-adjacency-changes
network 12.12.12.0 0.0.0.255 area 0
Lets test the EoMPLS configurations:
PE-2#show mpls l2transport vc det
Local interface: Fa1/1 up, line protocol up, Ethernet up
Destination address: 1.1.1.1, VC ID: 100, VC status: up
Output interface: Fa1/0, imposed label stack {17}
Preferred path: not configured
Default path: active
Next hop: 192.168.12.1
Create time: 00:47:35, last status change time: 00:47:14
Signaling protocol: LDP, peer 1.1.1.1:0 up
MPLS VC labels: local 17, remote 17
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 363, send 638
byte totals: receive 36265, send 75764
packet drops: receive 0, seq error 0, send 0
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 = 92/109/132 ms
CE Routers learn the mac-addresses of each other:
CE-1#show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 12.12.12.1 - ca02.0fdc.001c ARPA FastEthernet1/0
Internet 12.12.12.2 49 ca03.0fdc.001c ARPA FastEthernet1/0
CE-2#show interface f1/0 | inc bia
Hardware is i82543 (Livengood), address is ca03.0fdc.001c (bia ca03.0fdc.001c)
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:36 12.12.12.2 FastEthernet1/0
We see that port-mode EoMPLS configurations on PE routers are working without any problem.
No comments:
Post a Comment