On 2014-09-05 15:41, Aaron wrote:
123.123.144.1 is one of my l3vpn customer subnets and I can trace to it and see all my mpls p hops along the way... (mpls p boxes are 172.20.x.x) (not sure why the penultimate hop times out.... but perhaps that's another topic)
(1) You are sure that 124.173.255.221 is not dropping your 172.20.x.x addresses and (b) you are also not filtering 172.20.x.x on your PE-CE link? (2) You could set label-allocation-mode to VRF on the PE peering with the CE, for this VRF only (downside: you would lose some features like eiBGP load-sharing and such). That way your PE would route the ICMPs back to the source. I don't think there are other solutions. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
