cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1467
Views
0
Helpful
4
Replies

Unable to ping across MPLS vpn

PacketSpartan
Level 1
Level 1

Hi guys i have set up a layer 3 vpn across the mpls and have Customer A connecting to Customer A across the MPLS core, I have just set up another PE router on the core and paired them up using MBGP and pairing works and able to ping the loopback address MBGP pairing.

Under sh ip route the routes are coming across but i am unable to ping from customer CE1A to CE3A, same fromt the other end, for the love of  god i cant seem to figure it out why they are not pinging

Please ignore the bottom right hand corner of the image, that is part of my next bit

1. I can get routes from CE1A to CE2A and ping across

2.I can get routes from CE3A on CE1A vice a versa (#sh ip route)

3. ping suceesful from PE1 to PE3 (loopback addresses)

4. RD: 1:111 Same across the one customer

5. RT : 1:100 (export and import)

Please help

CCNA R&S
4 Replies 4

Hi TTboy,
Which protocol are u using as CE-PE routing one? Did you verify the redistribution? Make sure your PE find the correct next-hop because some IOS have this kind of bug. If you shared more info about the config itself (PE to CE ) it would be easier to help

Regards,
Alessio

Sent from Cisco Technical Support iPad App

Hi Thanks you for the reply, I am using Eigrp between the PE and CE, I am not aware of this bug as it was working between PE1 and PE2 (pingable).

PE3

Current configuration : 1875 bytes

!

version 12.4

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname PE3

!

boot-start-marker

boot-end-marker

!

!

no aaa new-model

memory-size iomem 5

!

!

ip cef

no ip domain lookup

ip domain name lab.local

!

!

ip vrf Cust-A

rd 1:111

route-target export 1:100

route-target import 1:100

!

interface Loopback0

ip address 192.168.33.1 255.255.255.255

!

interface FastEthernet0/0

ip vrf forwarding Cust-A

ip address 10.10.30.2 255.255.255.252

speed 100

full-duplex

!

interface FastEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

interface Ethernet1/0

ip address 10.10.30.30 255.255.255.252

full-duplex

mpls ip

!

interface Ethernet1/1

no ip address

shutdown

half-duplex

!

interface Ethernet1/2

no ip address

shutdown

half-duplex

!

interface Ethernet1/3

no ip address

shutdown

half-duplex

!

!

router eigrp 200

network 10.10.30.28 0.0.0.3

network 192.168.33.1 0.0.0.0

no auto-summary

!

router eigrp 65001

auto-summary

!

address-family ipv4 vrf Cust-A

redistribute bgp 65001 metric 10000 1000 255 1 1500

network 10.10.30.2 0.0.0.0

no auto-summary

autonomous-system 1

exit-address-family

!

router bgp 65001

no synchronization

bgp log-neighbor-changes

neighbor 192.168.5.1 remote-as 65001

neighbor 192.168.5.1 update-source Loopback0

no auto-summary

!

address-family vpnv4

neighbor 192.168.5.1 activate

neighbor 192.168.5.1 send-community both

exit-address-family

!

address-family ipv4 vrf Cust-A

redistribute eigrp 1

no synchronization

exit-address-family

!

no ip http server

no ip http secure-server

!

control-plane

!

line con 0

exec-timeout 0 0

privilege level 15

logging synchronous

line aux 0

exec-timeout 0 0

privilege level 15

logging synchronous

line vty 0 4

login

!

!

end

CCNA R&S

Hello,

Please try to rediestribute connected.

for BGP

address-family ipv4 vrf Cust-A

redistribute eigrp 1

redistribute connected.

router eigrp 65001

auto-summary

!

address-family ipv4 vrf Cust-A

redistribute bgp 65001 metric 10000 1000 255 1 1500

redistribute connected.

Regards
Thanveer
"Everybody is genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is a stupid."

I was a bit skeptic in tryingthe Redistribute connected command as it was not need other MBGP pairings, after doing i did try it and it did not make a difference. I did further trouble shooting and since gns3 played up a littel bit i had to do further re code all the commands. re establish the pairing.

Well its fixed as they are able to ping across, can it be due to the duplex being set on auto ? (went through all the P routers to ensure that they were not on auto

Thanks guys for the help

CCNA R&S

CCNA R&S