classic traceroute thru MPLS VPN

open original image

Gents,

I'm running traceroute from local CE router to remote CE router thru ISP MPLS VPN in the same VPN. I assume that my ISP has 'no mpls ttl propagation'.

10.0.1.153 - ISP

Question: Why in the traceroute output the second hop is the IP address (10.0.1.153) of the outgoing interface which interconnects my remote CE to ISP (10.0.1.152/30 subnet)?

I would expect to see some interface faced towards local CE from MPLS cloud or none. What is the theory behind it that the ISP router is sourcing the ICMP ttl exceeded message with mentioned IP address? Does the ISP edge PE router some additional checking of the IP TTL after poping labels?

Here is the answer for this question. The Cisco IOS does additional check when packet is leaving egress PE for TTL 1/0 -