[c-nsp] Mpls Troubleshooting Question

[schilling]

check no ip unreachable on the PE interface? I got bite once.

verify the LSP?

Ivan's blog for rescue :-)

http://wiki.nil.com/PE-to-PE_troubleshooting_in_MPLS_VPN_networks


Schilling

On Mon, Feb 23, 2009 at 4:51 PM, Rocker Feller <
rocker.rockerfeller at gmail.com> wrote:

> Hi,
>
> I work in an ISP environment and in it I found developed MPLS delivering ip
> vpns.
>
> There is one client with 5 branches.
>
> All work fine except for 1.
>
> This is the scenario.
>
> The default route is derived from the corporate office (HQ). Its network
> range is 172.16.0.0/16
>
> Say branch with problem is branch Z ip range is 172.16.7.0/24
>
> >From Z Lan I can ping HQ Lan ok
>
> ping 172.16.1.1 source 172.16.7.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
> Packet sent with a source address of 172.16.7.1
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 24/29/36 ms
>
> >From HQ I cannot ping Z apart from reaching the Z router.the lan
>
> ping 172.16.7.1
> PING 172.16.7.1 (172.16.7.1) 56(84) bytes of data.
> 64 bytes from 172.16.7.1: icmp_seq=0 ttl=253 time=19.8 ms
>
> Any other connections are dropped from branch Z router
>
> A trace reveals packets are dropped from the main MPLS PE router.
>
> The PE router can reach the CE router but not any pc behind it.
>
>
> Your input appreciated
>
>
> Regards
> Rocker
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>