Segment Routing Tunnel down

[dodgerfan78]

I have basic scenario R1-R2-R3-R4 in a full mesh

I built a tunnel from R1 to R4 that traverse R2 and R3: R1->R2->R3->R4:

These are loopbacks:

explicit-path name R1234
 index 10 next-address strict ipv4 unicast 100.1.1.2
 index 20 next-address strict ipv4 unicast 100.1.1.3
 index 30 next-address strict ipv4 unicast 100.1.1.4
!
interface Loopback0
 ipv4 address 100.1.1.1 255.255.255.255
!
interface tunnel-te14
 ipv4 unnumbered Loopback0
 destination 100.1.1.4
 path-selection
 segment-routing adjacency protected
 !
 path-option 1 explicit name R1234 segment-routing

Each router has a config that looks like this:

router ospf 1
 segment-routing mpls
 segment-routing forwarding mpls
 area 0
 mpls traffic-eng
 segment-routing mpls
 interface Loopback0
 prefix-sid index 101 !! (102,103,104 for the others)
 !
 interface GigabitEthernet0/0/0/0
 network point-to-point
 segment-routing forwarding mpls
 !
 interface GigabitEthernet0/0/0/1
 network point-to-point
 segment-routing forwarding mpls
 !
 interface GigabitEthernet0/0/0/2
 network point-to-point
 segment-routing forwarding mpls

RP/0/0/CPU0:R1#show mpls traffic-eng tunnels 
Thu Sep 1 15:12:52.750 UTC
Name: tunnel-te14 Destination: 100.1.1.4 Ifhandle:0x580 
 Signalled-Name: R1_t14
 Status:
 Admin: up Oper: down Path: not valid Signalling: Down
path option 1, (Segment-Routing) type explicit R1234
 Protected-by PO index: none
 Last PCALC Error: Wed Aug 31 15:17:02 2016
 Info: No topology
 G-PID: 0x0800 (derived from egress interface properties)
 Bandwidth Requested: 0 kbps CT0
 Creation Time: Wed Aug 31 15:16:33 2016 (23:56:20 ago)

RP/0/0/CPU0:R1#show mpls forwarding 
Thu Sep 1 15:13:51.386 UTC
Local Outgoing Prefix Outgoing Next Hop Bytes 
Label Label or ID Interface Switched 
------ ----------- ------------------ ------------ --------------- ------------
16102 Pop SR Pfx (idx 102) Gi0/0/0/0 10.1.2.2 520 
16103 Pop SR Pfx (idx 103) Gi0/0/0/2 10.1.3.3 520 
16104 Pop SR Pfx (idx 104) Gi0/0/0/1 10.1.4.4 51480 

Can you tell me what else I am missing?

Thanks,

Bryan

[Anoop Kalikot Veetil]

Hi Bryan,

Can you add " mpls traffic-eng router-id <router-id>" under OSPF and retry ?  

Hope you added interfaces under  "mpls traffic-eng". Looks like  TE  topology doesn't have any info, please check  "show mpls traffic-eng   topology  model-type rdm"  output for the prefixes

thanks/Anoop

[smailmilak]

Hi,

I do not want to open a new discussion.

Do we have support for segment routing on Trident Line Cards (1st Gen ethernet linecard) on ASR9K?

[Anoop Kalikot Veetil]

No, SR is not supported on trident based cards

thanks/Anoop

[smailmilak]

Ok, thanks for that info.

So we can say that SR is supported on any Typhoon and Tomahawk based line card?

[Adam Vitkovsky]

It begs a question why?

I mean SR was around since in 5.2.x, so it’s not the 5.3.4 limit.

Is it then the microcode on Trident that has some limitations with regards to label stack?

adam

[Aleksandar Vidakovic]

it's because of the instruction memory size on Trident NP. There was no space to add more features.

[Adam Vitkovsky]

Aah I see, thank you very much.

[smailmilak]

Hi,

I am testing a few SR scenarios. We have a large RSVP TE domain and we need to create TE tunnels from SR to RSVP. I was looking into some slides and all I could find is this

This example is working for me (using binding-sid on edge router) but this is more complicated than RSVP TE. 

Is it really not possible to create a tunnel with dynamic path or explicit path with next address Loopback?

I think that the LSP path is broken between SR and RSVP and that is the reason why we need to use binding sid.