[c-nsp] Mpls Troubleshooting Question

[Ibrahim Abo Zaid]

sorry as both sites have different networks so you can't use this technology




On Tue, Feb 24, 2009 at 9:54 AM, Ibrahim Abo Zaid <ibrahim.abozaid at gmail.com
> wrote:

> Hi Rocker
>
> that doesn't seem to me as MPLS VPN topology as both PE1 interfaces to CE1
> and CEZ are non-MPLS interfaces , it is much like
> local-switching scenario
>
> try using CONNECT command
>
>
>
> best regards
> --Ibrahim
>
> On Tue, Feb 24, 2009 at 2:11 AM, Rocker Feller <
> rocker.rockerfeller at gmail.com> wrote:
>
>> Hi,
>>
>> My full scenario
>>
>> CE1 -------> PE1 -----------> PE2 -------------> CEZ
>>
>> On the PE1 interface I have a tunnel to CEZ .
>>
>> nb: PE2 is not mpls enabled.
>>
>> CEZ has a ptp link to PE2
>>
>> LSP - tunnel is up from  PE1---> CEZ and I can reach the CEZ router via
>> the
>> tunnel ptp.
>>
>>        - from the CEZ lan CE1 lan is reacheable.
>>
>> It is only from the CE1 router  and from the PE1 that I cannot reach CEZ
>> lan.
>>
>> Please note this customer has 6 other branches which are working well.
>>
>> Thanks
>>
>>
>>
>> On Tue, Feb 24, 2009 at 1:11 AM, schilling <schilling2006 at gmail.com>
>> wrote:
>>
>> > 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/
>> >>
>> >
>> >
>> _______________________________________________
>> 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/
>>
>
>