[j-nsp] l3 vpn ping in juniper in M320

[Harry Reynolds]

Are you using any VT interface or lsi?  If not, I believe this is
normal. Meaning, when the remote PE pops the label it cannot do an IP
lookup with the vt tunnel/lsi, so its compelled to forward a packet
addressed to its local ifl out the VRF interface. In my experience the
CE, upon receiving such a packet, does the ttl - 1 thing and routes the
packet back towards the PE, who now sees an IP packet (in a vrf
context), and can generate a reply.

So, while there is an extra hop, things work. Might want to very that
pe-pe pings to core and vrf interfaces are working. Perhaps remote PE
does not have a route back to ping source and is dropping.

HTHs

 

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Dinesh Bhonsle
Sent: Wednesday, August 20, 2008 10:56 AM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] l3 vpn ping in juniper in M320

Hi,

I am not able to get a succesfull vpn ping response for    directly
connected interface inside a vpn instance in juniper.

CE1-----M320-1--------L3vpn core-----M320-2(vpn instance vpn1) (81.1.1.1
)--------------------------(81.1.1.2)CE2

when i ping from CE1 to 81.1.1.1 on M320-2, i see that M320 does not
reply , but mistreiously forwards icmp echo requests to CE2.
When i ping from CE1 to 81.1.1.2  , i see ping responses from CE2, ping
successful. So only  ping to junipers  ip-addr fails.
Regards
Dinesh
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp