[c-nsp] SR-TE

[Phil Bedard]

This is likely the key.  Apart from defining the SR-TE Policy, you have to map traffic to them, it doesn't happen automatically.  

Today it's done through 
1) static routes 
2) autoroute announce as mentioned, 
3) For traffic using BGP routes using a color BGP community to automatically map traffic to a destination BGP next-hop to a specific SR Policy (used for global routing table, L3VPN, and EVPN) 
4) For P2P L2VPN you can define a specific SR Policy to use.    

Thanks, 
Phil 

On 9/17/20, 4:44 PM, "cisco-nsp on behalf of dip" <cisco-nsp-bounces at puck.nether.net on behalf of diptanshu.singh at gmail.com> wrote:

    It's been almost 4 yrs since I looked at SR-TE. How are you mapping traffic
    to your SR-TE tunnels? Like "auto-route announce"?

    On Thu, Sep 17, 2020 at 1:34 PM <aaron1 at gvtc.com> wrote:

    > Anyone have ideas why I can't seem to get traffic to flow via this SR-TE
    > path?  I have configs if you would like to see them.
    >
    >
    >
    > Seems that the BSID (100) is in the LFIB but I'm not seeing traffic through
    > it.  Also the traceroute on the r10 ce still shows flowing via the dynamic
    > vanilla SR path via r21.  I'd like to have the SR-TE path carry the
    > customer
    > traffic via r24----r23
    >
    >
    >
    >
    >
    > RP/0/0/CPU0:r20#sh mpls for
    >
    > Thu Sep 17 15:14:28.224 CST
    >
    > Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes
    >
    >
    > Label  Label       or ID              Interface                    Switched
    >
    >
    > ------ ----------- ------------------ ------------ ---------------
    > ------------
    >
    > 100    Pop         No ID              my-srte-poli point2point     0
    >
    >
    > 16022  16022       SR Pfx (idx 22)    Gi0/0/0/0    10.20.1.2       3864764
    >
    >
    > 16024  Pop         SR Pfx (idx 24)    Gi0/0/0/1    10.20.1.21      0
    >
    >
    > 24000  Pop         SR Adj (idx 0)     Gi0/0/0/0    10.20.1.2       0
    >
    >
    > 24001  Pop         SR Adj (idx 0)     Gi0/0/0/1    10.20.1.21      0
    >
    >
    > 24002  Aggregate   one: Per-VRF Aggr[V]   \
    >
    >
    >
    >                                       one
    > 2895172236
    >
    >
    >
    > RP/0/0/CPU0:r20#sh segment-routing traffic-eng policy
    >
    > Thu Sep 17 15:14:33.523 CST
    >
    >
    >
    > SR-TE policy database
    >
    > ---------------------
    >
    >
    >
    > Name: my-srte-policy (Color: 1, End-point: 10.20.0.22)
    >
    >   Status:
    >
    >     Admin: up  Operational: up for 00:00:16 (since Sep 17 15:14:17.095)
    >
    >   Candidate-paths:
    >
    >     Preference 1:
    >
    >       Explicit: segment-list my-srte-sidlist-1 (active)
    >
    >         Weight: 0
    >
    >           16024
    >
    >           24002
    >
    >           16022
    >
    >   Attributes:
    >
    >     Binding SID: 100
    >
    >       Allocation mode: explicit
    >
    >       State: programmed
    >
    >       Policy selected: yes
    >
    >     Forward Class: 0
    >
    >
    >
    >
    >
    > r10               r30
    >
    > |                 |
    >
    > |                 |
    >
    > r20-----r21-----r22
    >
    > |                 |
    >
    > |                 |
    >
    > r24-------------r23
    >
    >
    >
    > r10 and r30 are ce's
    >
    >
    >
    >
    >
    >
    >
    >
    >
    > Aaron
    >
    > aaron1 at gvtc.com
    >
    >
    >
    > _______________________________________________
    > cisco-nsp mailing list  cisco-nsp at puck.nether.net
    > https://puck.nether.net/mailman/listinfo/cisco-nsp
    > archive at http://puck.nether.net/pipermail/cisco-nsp/
    >
    _______________________________________________
    cisco-nsp mailing list  cisco-nsp at puck.nether.net
    https://puck.nether.net/mailman/listinfo/cisco-nsp
    archive at http://puck.nether.net/pipermail/cisco-nsp/