If you can enable icmp-tunneling on the P-routers and do a traceroute instead of ping, you may be able to see the path it takes. It also tells you the MPLS label it uses, so you can find out the entry in the routing-table it is using.
Thanks. Raymond Richmond, Jeff wrote: >I would really need some more info to really help, but are you pinging via the >routing instance from PE2 to PE1 and that is working (as opposed to pinging >via inet.0)? When you say PE1 has no routes, are you saying at all, or just >the VRF, inet.0, or both? > >-Jeff > > >-----Original Message----- >From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] >Sent: Thu 10/11/2007 6:11 PM >To: [email protected] >Cc: >Subject: [j-nsp] PE to PE ping > > > > >i am not able to ping b/w pe1 and pe2, but pe2 can ping pe1 vrf interface? PE1 >does not have any routes > >in VPNA VRF to other PE's VRF, but it can still answer a ping? i dont think >this is a right behavior? > >I may be wrong but do like to see if you guys have seen this.. > > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
