Egress PE router (target node) behavior

The data path in the ingress network port in the destination router that owns the target SID extracts the packet to CPM.

A traceroute packet is extracted based on the hop-limit field value of 1 before the route lookup.

A ping packet is extracted after the route lookup matches a FIB entry of a local locator, End, or End.X SID.

The CPM checks that the target locator or SID address matches a local entry. This means that the locator or SID has either been configured manually by the user or it has been auto-allocated by the locator module for use by IS-IS or BGP.

A match on the locator requires an exact match on the locator field and that both the function and argument fields be zero.

A match on a SID requires both the locator and function fields to match. The argument field is not checked.

When a match on a local locator or SID exists, the CPM replies with the following:

The responder node copies into the payload of the reply message the leading bytes (up to 128 bytes) in the received packet encapsulation, and including the outer IPv6 header and the SRH, if any.

When the traceroute is carried over a TCP transport and the destination is not an interface address, there is no indication whether the TCP port is open or closed.

Figure: End-to-end packet encapsulation for ping or traceroute of a remote locator or SID (1) and Figure: End-to-end packet encapsulation for ping or traceroute of a remote locator or SID (2) illustrate the packet encapsulation from ingress PE to egress PE for both the primary path and the backup path. For the backup path, both the PSP and USP types of the LFA SRH are shown.

Figure: End-to-end packet encapsulation for ping or traceroute of a remote locator or SID (1)
Figure: End-to-end packet encapsulation for ping or traceroute of a remote locator or SID (2)