Segment Routing Research Testing
Segment Routing Research Testing
LAB Diagram
RP/0/RP0/CPU0:SR-Testing-Adn-PE#
It is important to note that the BGP route for 112.123.118.23/32 can never become active on the ASBR
SR-Testing-Adn-PE because the Next-Hop is identical to the NLRI Prefix.
As a result, the IGP administrative distance of the Legacy core router's BGP-LU routes must be more
favorable than that of the BGP-LU routes from the Legacy core routers in the same environment.
Additionally, the Legacy Core routers will not operate ISIS as their routing protocol.
RP/0/RP0/CPU0:SR-Testing-Adn-PE#sh route 112.123.118.23/32
Sun Jan 22 19:08:13.089 GST
Otherwise route will be flagged as invalid and will produce recursive lookup error log events.
The requested route 144.133.128.42/32 was not found in the IS-IS test-isis IPv4
Unicast Route Table
As a result, the Next-Generation Core ASBRs in a given state must configure a specific OSPF
administrative distance for the loopback addresses of Legacy Core routers, ensuring they are not
assigned a value of "210" by the ospf 101 distance 210 command. This applies to any OSPF node
originating a BGP-LU route where the Next-Hop is the same as the advertised prefix, and the node is not
running ISIS as the routing protocol.
Singapore ASBR receives BGP-LU route for legacy Core CRS router in Singapore
The requested route 144.133.128.4/32 was not found in the IS-IS test-isis IPv4
Unicast Route Table
RP/0/RP0/CPU0:SR-Test-Core#
VIC ASBR receives reflected routes from local State RR (vm-test-12) for Singapore Legacy Core router
loopback (144.133.128.3/32)
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#sh bgp ipv4 labeled-unicast 144.133.128.3/32
Sun Jan 22 21:27:47.454 GST
BGP routing table entry for 144.133.128.3/32
Versions:
Process bRIB/RIB SendTblVer
Speaker 289135 289135
Local Label: 502036
Last Modified: Jan 22 20:45:36.230 for 00:42:11
Paths: (3 available, best #1)
Advertised IPv4 Labeled-unicast paths to update-groups (with more than one peer):
0.2
Advertised IPv4 Labeled-unicast paths to peers (in unique update groups):
112.123.118.232
Path #1: Received by speaker 0
Advertised IPv4 Labeled-unicast paths to update-groups (with more than one peer):
0.2
Advertised IPv4 Labeled-unicast paths to peers (in unique update groups):
112.123.118.232
Local, (Received from a RR-client)
144.133.128.15 (metric 51) from 144.133.128.5 (144.133.128.3)
Received Label 600005
Origin IGP, metric 0, localpref 100, aigp metric 16, valid, internal, best,
group-best, labeled-unicast
Received Path ID 1, Local Path ID 1, version 289153
Community: 65002:8669
Originator: 144.133.128.3, Cluster list: 144.133.128.5, 144.133.128.6,
144.133.128.15
Total AIGP metric 67
Label-Index: 5
Path #2: Received by speaker 0
Not advertised to any peer
Local, (Received from a RR-client)
144.133.128.16 (metric 59) from 144.133.128.5 (144.133.128.3)
Received Label 600005
Origin IGP, metric 0, localpref 100, aigp metric 16, valid, internal, labeled-
unicast
Received Path ID 2, Local Path ID 0, version 0
Community: 65002:8669
Originator: 144.133.128.3, Cluster list: 144.133.128.5, 144.133.128.6,
144.133.128.16
Total AIGP metric 75
Label-Index: 5
Path #3: Received by speaker 0
Not advertised to any peer
Local, (Received from a RR-client)
144.133.128.17 (metric 59) from 144.133.128.5 (144.133.128.3)
Received Label 600005
Origin IGP, metric 0, localpref 100, aigp metric 16, valid, internal, backup,
add-path, labeled-unicast
Received Path ID 3, Local Path ID 2, version 289153
Community: 65002:8669
Originator: 144.133.128.3, Cluster list: 144.133.128.5, 144.133.128.6,
144.133.128.17
Total AIGP metric 75
Label-Index: 5
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#sh route 144.133.128.3/32
Sun Jan 22 21:32:19.320 GST
RP/0/RP0/CPU0:SR-Test-Adn-PE-3(config)#route-policy BGP-LU_ADMINDIST
Sun Jan 22 21:32:28.663 GST
It is essential that the BGP-LU CMN OSS routes are made active in the IP Routing Information Base (RIB)
on the Next-Generation Core routers. This prevents inband management traffic from non-OSPF routers,
such as SPEs configured with BGP-LU/ISIS, from being blackholed when sent to the OSS networks.
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#sh route 141.168.206.0/24
Sun Jan 22 21:40:40.264 GST
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#sh bgp ipv4 labeled-unicast 141.168.206.0/24 neighbor
112.123.118.232 detail
Sun Jan 22 21:50:58.336 GST
BGP routing table entry for 141.168.206.0/24
Versions:
Process bRIB/RIB SendTblVer
Speaker 15793 15793
Local Label: 44621 (no rewrite);
Flags: 0x010030a2+0x20020000; backup available;
Last Modified: Feb 27 21:24:45.230 for 6d00h
Paths: (0 available)
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#sh mpls for labels 25530
Sun Jan 22 21:51:09.916 GST
Local Outgoing Prefix Outgoing Next Hop Bytes
Label Label or ID Interface Switched
------ ----------- ------------------ ------------ --------------- ------------
25530 463306 141.168.206.0/24 134.132.116.25 61200
RP/0/RP0/CPU0:SR-Test-Adn-PE-3#sh cef mpls local-label 25530 EoS
Sun Jan 22 21:51:18.284 GST
Label/EOS 25530/1, Label-type BGP, version 14617783, internal 0x5000001 0x40 (ptr
0xada29558) [1], 0x600 (0xaba2f108), 0xa08 (0xa88a1168)
Updated Sun Jan 22 :32:56.183
Prefix Len 21, traffic index 0, precedence n/a, priority 4
gateway array (0xa97f2788) reference count 234, flags 0x78, source rib (7), 0
backups
[79 type 5 flags 0x8441 (0x93a4ece8) ext 0x0 (0x0)]
LW-LDI[type=5, refc=3, ptr=0xaba2f108, sh-ldi=0x93a4ece8]
gateway array update type-time 1 Feb 26 16:18:43.333
LDI Update time Feb 26 16:18:43.333
LW-LDI-TS Feb 27 21:24:45.637
via 134.132.116.25/32, 3 dependencies, recursive [flags 0x6000]
path-idx 0 NHID 0x0 [0xa7cb8a68 0x0]
recursion-via-/32
next hop 134.132.116.25/32 via 608217/0/21
local label 25530
next hop 144.133.190.201/32 BE204 labels imposed {608217 463306}
Conclusion:
When a BGP-LU route is originated by a PE/Core router for its
own loopback address, it advertises the Segment Routing (SR)
Index and a label of Implicit-Null. The ASBR propagates the BGP-
LU route while preserving the received SR Index. It then
calculates a new label from its own SRGB based on the received
Index and sets it as the NLRI label. Additionally, the ASBR
modifies the BGP Next-Hop to itself (next-hop-self).