[c-nsp] SR-TE

[dip]

Aaron, not surprised here. In case of SR-TE, all the labels are imposed at
the headend (R20) and headend does the validation to make sure the explicit
path is still valid (If you would have specified the adjacency label for
the link R24->R23 then the path would have become invalid after the link
down). In your case, since you have the loopbacks defined which will
translate to Node-Sid's for the routers, So after the link between R24-R23
got removed from the topology, R24 LFIB is pointing towards R20 to reach
R23 which is the next-label imposed on your label stack.

On Sat, Sep 19, 2020 at 11:06 PM <aaron1 at gvtc.com> wrote:

> Trying again...formatting the router hops in a different way as the email
> is
> getting messed up
>
> r10                  r30
> |                        |
> |                        |
> r20-----r21-----r22
> |                        |
> |                        |
> r24------X------r23
>
>
> i put an X where I accidentally brought down the connection
>
> traceroute started on r10 and destined for r30...
>
> r10--->
>
> r20--->
>
> r24--->
>
> r20(again)--->
>
> r21--->
>
> r22--->
>
> r23--->
>
> r22(again)--->
>
> r30
>
>
> here was the segment list configured in the srte policy...
>
>   segment-list my-srte-sidlist-2
>    index 1 address ipv4 10.20.0.24
>    index 2 address ipv4 10.20.0.23
>    index 3 address ipv4 10.20.0.22
>
>
> -Aaron
>
>
>
>