04-16-2013 09:10 AM - edited 03-04-2019 07:36 PM
topology:
interface g3/13--6509A---->4506---->6509B-->interface g2/29
6509A and 6509B configure EoMPLS over GRE, VC is up, but can't ping.
6509A config :
mpls ldp neighbor 10.154.129.244 targeted
mpls label protocol ldp
!
interface Tunnel0
ip address 172.16.1.1 255.255.255.0
mpls label protocol ldp
mpls ip
tunnel source 10.154.129.10
tunnel destination 10.154.129.42
tunnel path-mtu-discovery
!
interface Loopback0
ip address 10.154.129.252 255.255.255.255
!
interface GigabitEthernet3/13
description link-to-Gi3/14
switchport
switchport access vlan 172
switchport mode access
!
interface GigabitEthernet3/14
description link-to-Gi3/13
no ip address
xconnect 10.154.129.244 100 encapsulation mpls
!
interface Vlan172
mtu 1526
ip address 172.16.16.253 255.255.255.0
mpls ip
standby 172 ip 172.16.16.254
standby 172 priority 150
standby 172 preempt
!
interface Vlan298
mtu 9216
ip address 10.154.129.10 255.255.255.248
mpls label protocol ldp
mpls ip
!
ip route 10.154.129.244 255.255.255.255 Tunnel0
mpls ldp router-id Loopback0 force
6509B config :
mpls ldp neighbor 10.154.129.252 targeted
mpls label protocol ldp
!
interface Tunnel0
ip address 172.16.1.2 255.255.255.0
mpls label protocol ldp
mpls ip
tunnel source 10.154.129.42
tunnel destination 10.154.129.10
tunnel path-mtu-discovery
!
interface Loopback0
ip address 10.154.129.244 255.255.255.255
!
interface GigabitEthernet2/29
no ip address
xconnect 10.154.129.252 100 encapsulation mpls
!
interface GigabitEthernet2/30
description link-to-Gi2/29
switchport
switchport access vlan 172
switchport mode access
!
interface Vlan172
mtu 1526
ip address 172.16.16.251 255.255.255.0
mpls ip
standby 172 ip 172.16.16.254
!
interface Vlan302
mtu 9216
ip address 10.154.129.42 255.255.255.248
mpls label protocol ldp
mpls ip
!
ip route 10.154.129.252 255.255.255.255 Tunnel0
mpls ldp router-id Loopback0 force
VC status:
C6509A#show mpls l2transport vc 100 detail
Local interface: Gi3/14 up, line protocol up, Ethernet up
Destination address: 10.154.129.244, VC ID: 100, VC status: up
Output interface: Tu0, imposed label stack {326}
Preferred path: not configured
Default path: active
Next hop: point2point
Create time: 06:53:52, last status change time: 06:52:52
Signaling protocol: LDP, peer 10.154.129.244:0 up
MPLS VC labels: local 333, remote 326
Group ID: local 0, remote 0
MTU: local 9216, remote 9216
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 0, send 27841
byte totals: receive 0, send 2076523
packet drops: receive 0, send 0 C5-C6509-25-A#show mpls l2transport vc 100 detail
Local interface: Gi3/14 up, line protocol up, Ethernet up
Destination address: 10.154.129.244, VC ID: 100, VC status: up
Output interface: Tu0, imposed label stack {326}
Preferred path: not configured
Default path: active
Next hop: point2point
Create time: 06:53:52, last status change time: 06:52:52
Signaling protocol: LDP, peer 10.154.129.244:0 up
MPLS VC labels: local 333, remote 326
Group ID: local 0, remote 0
MTU: local 9216, remote 9216
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 0, send 27841
byte totals: receive 0, send 2076523
packet drops: receive 0, send 0
04-16-2013 09:30 AM
Hi Wilson,
Try configuring "mls mpls tunnel-recir" on both devices. I would also reduce the MTU on the attachment circuit on both devices.
Hope this helps
04-16-2013 01:39 PM
Can you provide your ping results/traceroutes, also the output of:
sh ip route
sh mpls forwarding-table
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide