08-22-2025 07:01 PM
Hi There
I'm trying to do a lab about L3vpn inter AS option C on cisco CML, I'm using the topology below. This option consists of making a BGP-LU ipv4 adjacency between the PEs router and propagating the route-reflectors and PEs loop-backs between AS, and after that, making a VPNv4 adjacency between route-reflectors . I'm configuring one AS with Mpls-LDP a the other with segment routing.
First, I use IOS Xe on both PE and it work .... after I change the PE on the segment routing side for one XR, it did not work anymore, and i think I have the correct label distribution, but the XR is blocking the packets for some reason.
If I check the labels on the RR of the segmen-routing side, It will use the 16101-24004 labels to get on 5.5.5.5 the RR on the MPLS-LDP side.
hear you can see the packet capture , on RR to p1(ping) the MPLS stack is as it was expected 16101-24004
hear you can see the packet capture , on p1 to XR-PE
and finally the packet arrive to XR-PE with the expected label, but this no make any out-put on the packet capture, the packet its just drooped.
and the PE3 on the side mpls-ldp is waiting for the label 3016 as the XR-PE is expected to swap the label
if I do the same from MPLS-LDP side is the same history the lsp is break on XR-PE.
I can't see where is the fail, Can some one help me to find the problem?
here are the configurations.
XR_PE Segment routing side interface Loopback1 ipv4 address 130.130.130.130 255.255.255.255 ! interface MgmtEth0/RP0/CPU0/0 shutdown ! interface GigabitEthernet0/0/0/0 shutdown ! interface GigabitEthernet0/0/0/1 ipv4 address 10.11.101.101 255.255.255.0 ! interface GigabitEthernet0/0/0/2 shutdown ! interface GigabitEthernet0/0/0/3 ipv4 address 10.100.200.2 255.255.255.252 ! route-policy default pass end-policy ! router isis 1 is-type level-2-only net 49.0001.0000.0000.0101.00 address-family ipv4 unicast metric-style wide router-id Loopback1 segment-routing mpls ! interface Loopback1 address-family ipv4 unicast prefix-sid index 101 ! ! interface GigabitEthernet0/0/0/1 point-to-point address-family ipv4 unicast ! ! interface GigabitEthernet0/0/0/3 passive address-family ipv4 unicast ! ! ! router bgp 3000 bgp router-id 130.130.130.130 address-family ipv4 unicast allocate-label all ! neighbor 55.55.55.55 remote-as 3000 update-source Loopback1 address-family ipv4 labeled-unicast next-hop-self ! ! neighbor 10.100.200.1 remote-as 1000 update-source GigabitEthernet0/0/0/3 address-family ipv4 labeled-unicast next-hop-self route-policy default in route-policy default out ! ! ! segment-routing ! end
RR-55 SR SIDE hostname p55 ! ! ! ip cef login on-success log ipv6 unicast-routing ipv6 cef ! ! spanning-tree mode rapid-pvst ! ! interface Loopback1 ip address 55.55.55.55 255.255.255.255 ip router isis ipv6 address 2001:55:55:55::55/128 ipv6 router isis ! interface Ethernet0/0 ip address 10.11.55.55 255.255.255.0 ip router isis ipv6 address 2001:10:100:1155::55/64 ipv6 router isis isis network point-to-point isis adjacency-sid index 551 ! interface Ethernet0/1 ip address 10.22.55.55 255.255.255.0 ip router isis ipv6 address 2001:10:100:2255::55/64 ipv6 router isis isis network point-to-point ! interface Ethernet0/2 ip address 10.44.55.55 255.255.255.0 ip router isis ipv6 address 2001:10:100:4455::55/64 ipv6 router isis isis network point-to-point ! interface Ethernet0/3 ip address 10.33.55.55 255.255.255.0 ip router isis ipv6 address 2001:10:100:3355::55/64 ipv6 router isis isis network point-to-point isis adjacency-sid index 552 ! ! segment-routing mpls ! connected-prefix-sid-map address-family ipv4 55.55.55.55/32 index 55 range 1 exit-address-family ! ! router isis net 49.0001.0000.0000.0055.00 is-type level-2-only router-id Loopback1 metric-style wide log-adjacency-changes segment-routing mpls ! router bgp 3000 bgp router-id 55.55.55.55 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor 5.5.5.5 remote-as 1000 neighbor 5.5.5.5 ebgp-multihop 10 neighbor 5.5.5.5 update-source Loopback1 neighbor 102.102.102.102 remote-as 3000 neighbor 102.102.102.102 update-source Loopback1 neighbor 130.130.130.130 remote-as 3000 neighbor 130.130.130.130 update-source Loopback1 ! address-family ipv4 network 55.55.55.55 mask 255.255.255.255 neighbor 102.102.102.102 activate neighbor 102.102.102.102 route-reflector-client neighbor 102.102.102.102 send-label neighbor 130.130.130.130 activate neighbor 130.130.130.130 route-reflector-client neighbor 130.130.130.130 send-label exit-address-family ! address-family vpnv4 neighbor 5.5.5.5 activate neighbor 5.5.5.5 send-community extended neighbor 102.102.102.102 activate neighbor 102.102.102.102 send-community extended neighbor 102.102.102.102 route-reflector-client neighbor 130.130.130.130 activate neighbor 130.130.130.130 send-community extended neighbor 130.130.130.130 route-reflector-client exit-address-family ! ip forward-protocol nd ! ! ip http server ip http secure-server ip ssh bulk-mode 131072 no logging btrace ip access-list standard 55 10 permit 5.5.5.5 route-map gw permit 10 match ip next-hop 55 set ip next-hop 130.130.130.130 ! ! ! ! control-plane ! ! ! line con 0 exec-timeout 0 0 logging synchronous line aux 0 line vty 0 4 exec-timeout 0 0 login transport input ssh ! ! ! ! end
PE-3 mpls-ldp version 17.3 service timestamps debug datetime msec service timestamps log datetime msec service call-home platform qfp utilization monitor load 80 platform punt-keepalive disable-kernel-core platform console serial ! hostname PE3 ! boot-start-marker boot-end-marker ! ! vrf definition 1000:101 rd 1000:101 ! address-family ipv4 route-target export 1000:101 route-target import 1000:101 exit-address-family ! ! mpls label range 3000 3999 mpls traffic-eng tunnels multilink bundle-name authenticated ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! diagnostic bootup level minimal archive path bootflash: memory free low-watermark processor 71464 ! ! spanning-tree extend system-id ! ! redundancy ! bridge-domain 20 member BD-VIF 20 ! ! ! ! ! ! ! l2 vfi vpls1 manual vpn id 101 bridge-domain 15 neighbor 11.11.11.11 1133 encapsulation mpls ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface Loopback1 ip address 33.33.33.33 255.255.255.255 ip ospf 1 area 0 ! interface GigabitEthernet1 ip address 10.100.33.33 255.255.255.0 ip ospf network point-to-point negotiation auto no mop enabled no mop sysid ! interface GigabitEthernet2 ip address 10.100.43.33 255.255.255.0 ip ospf network point-to-point negotiation auto no mop enabled no mop sysid ! interface GigabitEthernet3 ip address 10.100.200.1 255.255.255.252 ip ospf network point-to-point ip ospf 1 area 0 negotiation auto mpls bgp forwarding no mop enabled no mop sysid ! interface GigabitEthernet4 no ip address negotiation auto no mop enabled no mop sysid service instance 10 ethernet description l2 vpn client 1 encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric xconnect 11.11.11.11 1001 encapsulation mpls ! service instance 15 ethernet description manual vpls client 1 encapsulation dot1q 15 rewrite ingress tag pop 1 symmetric bridge-domain 15 ! service instance 20 ethernet description L3 vpn client 1 encapsulation dot1q 20 rewrite ingress tag pop 1 symmetric bridge-domain 20 ! ! interface GigabitEthernet5 no ip address shutdown negotiation auto no mop enabled no mop sysid ! interface GigabitEthernet6 no ip address shutdown negotiation auto no mop enabled no mop sysid ! interface GigabitEthernet7 no ip address shutdown negotiation auto no mop enabled no mop sysid ! interface GigabitEthernet8 no ip address shutdown negotiation auto no mop enabled no mop sysid ! interface BD-VIF20 vrf forwarding 1000:101 ip address 192.168.3.1 255.255.255.248 ip ospf network point-to-point ip ospf 1000 area 0 no mop enabled no mop sysid ! router ospf 1000 vrf 1000:101 router-id 192.168.3.1 area 0 sham-link 10.200.33.33 10.200.11.11 ! router ospf 1 router-id 33.33.33.33 network 10.100.0.0 0.0.0.0 area 0 network 10.100.0.0 0.0.255.255 area 0 mpls ldp sync mpls ldp autoconfig mpls traffic-eng router-id Loopback1 mpls traffic-eng area 0 ! router bgp 1000 bgp router-id interface Loopback1 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor 5.5.5.5 remote-as 1000 neighbor 5.5.5.5 update-source Loopback1 neighbor 10.100.200.2 remote-as 3000 neighbor 10.100.200.2 update-source GigabitEthernet3 ! address-family ipv4 network 33.33.33.33 mask 255.255.255.255 neighbor 5.5.5.5 activate neighbor 5.5.5.5 next-hop-self neighbor 5.5.5.5 send-label neighbor 10.100.200.2 activate neighbor 10.100.200.2 next-hop-self neighbor 10.100.200.2 send-label exit-address-family ! address-family vpnv4 neighbor 5.5.5.5 activate neighbor 5.5.5.5 send-community both exit-address-family ! address-family ipv4 vrf 1000:101 redistribute connected redistribute ospf 1000 exit-address-family ! ip forward-protocol nd no ip http server ip http secure-server ! ! ! ip access-list standard 1 10 deny 10.200.11.11 20 deny 10.200.33.33 30 permit any ip access-list standard 2 10 permit 5.5.5.5 ! ! route-map shamlink-client1 permit 10 match ip address 1 ! route-map inter-as permit 10 match ip address 2 ! route-map inter-as deny 25 ! mpls ldp router-id Loopback1 force ! ! ! control-plane ! ! ! ! ! ! line con 0 exec-timeout 0 0 stopbits 1 line vty 0 exec-timeout 0 0 login transport input ssh line vty 1 exec-timeout 0 0 login length 0 transport input ssh line vty 2 4 exec-timeout 0 0 login transport input ssh ! call-home ! If contact email address in call-home is configured as sch-smart-licensing@cisco.com ! the email address configured in Cisco Smart License Portal will be used as contact email address to send SCH notifications. contact-email-addr sch-smart-licensing@cisco.com profile "CiscoTAC-1" active destination transport-method http ! ! ! ! ! end
RR 5 - MPLS-LDP Building configuration... Current configuration : 5578 bytes ! ! Last configuration change at 01:24:11 UTC Sat Aug 23 2025 ! version 17.15 service timestamps debug datetime msec service timestamps log datetime msec ! hostname P5 ! boot-start-marker boot-end-marker ! ! no logging console no aaa new-model ! ! ! ! ! ip cef login on-success log ipv6 unicast-routing ipv6 cef ! ! ! ! ! ! ! ! mpls label range 500 599 mpls traffic-eng tunnels ! ! crypto pki trustpoint TP-self-signed-131184642 enrollment selfsigned subject-name cn=IOS-Self-Signed-Certificate-131184642 revocation-check none rsakeypair TP-self-signed-131184642 hash sha512 ! ! ! memory free low-watermark processor 80093 ! ! spanning-tree mode rapid-pvst ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface Loopback1 ip address 5.5.5.5 255.255.255.255 ip ospf 1 area 0 ! interface Tunnel11 ip unnumbered Loopback1 tunnel mode mpls traffic-eng tunnel destination 2.2.2.2 tunnel mpls traffic-eng path-option 1 explicit identifier 11 ! interface Ethernet0/0 ip address 10.100.15.5 255.255.255.0 ip ospf network point-to-point mpls traffic-eng tunnels ip rsvp bandwidth ! interface Ethernet0/1 ip address 10.100.25.5 255.255.255.0 ip ospf network point-to-point mpls traffic-eng tunnels mpls traffic-eng backup-path Tunnel11 ip rsvp bandwidth ! interface Ethernet0/2 ip address 10.100.35.5 255.255.255.0 ip ospf network point-to-point mpls traffic-eng tunnels ip rsvp bandwidth ! interface Ethernet0/3 ip address 10.100.45.5 255.255.255.0 ip ospf network point-to-point mpls traffic-eng tunnels ip rsvp bandwidth ! router ospf 1 network 10.100.0.0 0.0.255.255 area 0 mpls ldp sync mpls ldp autoconfig mpls traffic-eng router-id Loopback1 mpls traffic-eng area 0 ! router bgp 1000 bgp router-id interface Loopback1 bgp log-neighbor-changes bgp listen range 33.33.33.33/32 peer-group pe-group bgp listen range 22.22.22.22/32 peer-group pe-group bgp listen range 11.11.11.11/32 peer-group pe-group no bgp default ipv4-unicast neighbor pe-group peer-group neighbor pe-group remote-as 1000 neighbor pe-group update-source Loopback1 neighbor 55.55.55.55 remote-as 3000 neighbor 55.55.55.55 ebgp-multihop 10 neighbor 55.55.55.55 update-source Loopback1 ! address-family ipv4 network 5.5.5.5 mask 255.255.255.255 neighbor pe-group activate neighbor pe-group route-reflector-client neighbor pe-group send-label exit-address-family ! address-family vpnv4 neighbor pe-group activate neighbor pe-group send-community both neighbor pe-group route-reflector-client neighbor 55.55.55.55 activate neighbor 55.55.55.55 send-community extended exit-address-family ! address-family vpnv6 exit-address-family ! address-family l2vpn vpls neighbor pe-group activate neighbor pe-group send-community both neighbor pe-group route-reflector-client neighbor pe-group suppress-signaling-protocol ldp exit-address-family ! ip forward-protocol nd ! ! ip http server ip http secure-server ip ssh bulk-mode 131072 ! ip explicit-path identifier 11 enable index 1 next-address 1.1.1.1 index 2 next-address 2.2.2.2 no logging btrace ip access-list standard 55 10 permit 55.55.55.55 ip access-list standard 1300 10 permit 130.130.130.130 20 permit 102.102.102.102 30 deny any route-map gw permit 10 match ip next-hop 55 set ip next-hop 33.33.33.33 ! route-map ext-bgp permit 10 match ip address 1300 ! mpls ldp router-id Loopback1 ! ! ! control-plane ! ! ! line con 0 exec-timeout 0 0 logging synchronous line aux 0 line vty 0 4 exec-timeout 0 0 login transport input ssh ! ! ! ! end
Solved! Go to Solution.
08-24-2025 12:08 PM - edited 08-24-2025 12:10 PM
Thanks for the additional info @heiliger-eliet .
> What level of code do you run on the XR side?
I meant the IOS-XR version, but I see in the last provided output that you run IOS-XR 24.3.1.
I quickly tried to reproduce the issue and I see what triggers this issue.
Can you add the following command to your XR configuration and reload IOS-XR.
segment-routing
global-block 16000 23999
Then reload XR. It should fix it.
08-22-2025 08:05 PM
Hi @heiliger-eliet ,
For InterAS to work on XR you need to configure a static route towards the neighbor IP address on the interface between the two ASes as follow
router static
address-family ipv4 unicast
10.100.200.1/32 GigabitEthernet0/0/0/3
This document gives an InterAS option C example.
08-22-2025 10:35 PM
Thanks @Harold Ritter for the answer.
I added the static route and now I can get traffic between PE3 and XR-PE, but the lsp is still broken toward inside the AS 3000
here a packte capture on PE3 XR-PE link (RR-AS3000 pingin to RR as 1000).
the link P1-PE55 the answer from p5-RR does not pass through XR-PE.
08-23-2025 08:36 AM
Hi @heiliger-eliet ,
I overlooked the fact that you are using SR in the domain where the XR router is located. This brings in another XR particularity. If you look in the XR router logs, you will see the following error message:
%ROUTING-RIB-3-LABEL_ERR_ADD
This is because BGP-LU tries to allocate a label and there is already one allocated by SR. The solution is to use a BGP prefix SID instead of letting BGP-LU allocate its own label.
Here's the configuration you need on the XR side to use the BGP prefix SID for prefix 55.55.55.55/32.
route-policy setPrefixSID55
set label-index 55
end-policy
!
router bgp 3000
address-family ipv4 unicast
network 55.55.55.55/32 route-policy setPrefixSID55.
You can remove the network 55.55.55.55 statement from p55, as XR-PE is the one originating the prefix in BGP-LU. The reason you originate the prefix on the XR router rather than on the p55 is that setting the BGP prefix SID is not supported on IOS-XE yet.
After committing this change, you will need to restart the bgp process with the following command:
process restart bgp
You will need to do the same thing for PE-e2 and any other devices that you want to be reachable from the other domain.
Do not hesitate to let me know if you have any further questions.
08-23-2025 12:04 PM
Hi @heiliger-eliet ,
Correction. the BGP prefix SID setting is now supported in the IOS-XE 17 train.
08-23-2025 08:27 PM
Hi @Harold Ritter , thanks for the answers .. has been helpfully.
yes, the log about the route 55.55.55.55 was there.
RP/0/RP0/CPU0:Aug 23 05:56:25.900 UTC: rib_mgr[1256]: %ROUTING-RIB-3-LABEL_ERR_ADD : Add local-label 24002 (2) for table 0xe0000000, prefix 55.55.55.55/128, by proto bgp client 54 bgp node0_RP0_CPU0 - existing label 16055 added by proto-id 6 client 49
first I added the fallowing configuration to the Xr-Pe
route-policy SID($SID)
set label-index $SID
end-policy
!
address-family ipv4 unicast
network 55.55.55.55/32 route-policy SID(55)
after restart BGP process the log error appear again so I delete the prefix-sid configuration, and whala! the RR make the VPNV4 adjacency and of course PE-e2 get the routes of VRF 1000:101, but I can not ping from tha VRF on PE-e2 to the vrf on Pe3 or Pe1.
I fallows the label from PE-e2.
the three label are out as is expected form PE-e2.
link(Pe3 - PEXR) the information get where is expected and the remote vrf respond but the packet are dropped on PE-XR routers
the packet are coming with 24004 that output unlabelled.
I try some thing to fix it, i use the command next-host-unchaged on RR55 and advertised the PE-e2 loopback like the loopback of RR55 but when eliminate the prexi-id on PE-e2 the reachability to RR55 is lost. also use the comas segment-routing mpls on XE router but that does not change anything
some thing more is need to synchronized the labels?
08-23-2025 08:58 PM - edited 08-23-2025 09:02 PM
Hi @heiliger-eliet ,
> after restart BGP process the log error appear again so I delete the prefix-sid configuration
The end to end connectivity between the two domains will not work without the prefix-sid configuration, as it is required on the XR side for the label to be properly programmed in the LFIB. We can see in the output you provided that the LFIB entry for 55.55.55.55/32 is incorrect. It should use the SR SID for 55.55.55.55/32 (16055), not 24004.
Can you please put the prefix SID configuration I suggested back in place, restart the BGP process and then provide a "show mpls forwarding" from PE3 and XR-PE?
08-23-2025 09:42 PM
Can you please put the prefix SID configuration I suggested back in place, restart the BGP process and then provide a "show mpls forwarding" from PE3 and XR-PE? yes!!!!
logs after reset
RP/0/RP0/CPU0:ios#process restart bgp
Sun Aug 24 04:14:35.429 UTC
RP/0/RP0/CPU0:Aug 24 04:13:02.784 UTC: bgp[1090]: %ROUTING-BGP-3-RIB_FAIL : [27299] : Failed to Redist since prefix sid is out of SRGB inside calculate origin for TBL:default (1/1) while calling the RIB instance 0: Success
RP/0/RP0/CPU0:Aug 24 04:14:35.466 UTC: sysmgr_control[68661]: %OS-SYSMGR-4-PROC_RESTART_NAME : User cisco (con0_RP0_CPU0) requested a restart of process bgp at 0/RP0/CPU0
RP/0/RP0/CPU0:Aug 24 04:14:37.547 UTC: bgp[1090]: %ROUTING-BGP-3-RIB_FAIL : [11347] : Failed to Redist since prefix sid is out of SRGB inside calculate origin for TBL:default (1/1) while calling the RIB instance 0: Success
RP/0/RP0/CPU0:Aug 24 04:14:37.678 UTC: bgp[1090]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : default, process instance 1:(A)inst-id 0, Connection Establised
RP/0/RP0/CPU0:Aug 24 04:14:38.472 UTC: bgp[1090]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : default:(A)inst-id 0, Initial Config Done
RP/0/RP0/CPU0:Aug 24 04:14:41.155 UTC: bgp[1090]: %ROUTING-BGP-5-ADJCHANGE : neighbor 10.100.200.1 Up (VRF: default) (AS: 1000)
RP/0/RP0/CPU0:Aug 24 04:14:41.159 UTC: bgp[1090]: %ROUTING-BGP-5-NSR_STATE_CHANGE : Changed state to Not NSR-Ready
RP/0/RP0/CPU0:Aug 24 04:14:42.186 UTC: bgp[1090]: %ROUTING-BGP-5-ADJCHANGE : neighbor 55.55.55.55 Up (VRF: default) (AS: 3000)
RP/0/RP0/CPU0:Aug 24 04:14:42.220 UTC: rib_mgr[1256]: %ROUTING-RIB-3-LABEL_ERR_ADD : Add local-label 24004 (2) for table 0xe0000000, prefix 55.55.55.55/128, by proto bgp client 52 bgp node0_RP0_CPU0 - existing label 16055 added by proto-id 7 client 54
show mpls forwarding
08-23-2025 10:03 PM
Thanks for the output @heiliger-eliet
The issue is fixed on the XR-PE side.
We still see an issue on PE3, which should have an entry with the local and remote label set to 16055 for 55.55.55.55/32.
Could you please configure the following on PE3 and provide another "show mpls forwarding" from PE3:
router bgp 1000
address-family ipv4
segment-routing mpls
08-23-2025 10:17 PM
here
segment-routing mpls (I had to active SR before be alower to use on bgp)
router bgp 1000
address-family ipv4
segment-routing mpls
08-23-2025 10:47 PM - edited 08-24-2025 10:34 AM
Thanks for the additional information @heiliger-eliet .
The BGP prefix-sid configuration and the BGP process restart should definitely have fixed it. If it didn't it is because there something wrong.
You can actually remove this last configuration on PE3.
What level of code do you run on the XR side?
Can you provide the output for the command "show route 55.55.55.55/32 detail private"?
As a quick test, could you just reboot the XR side to see if it will clean things up?
08-24-2025 10:55 AM
What level of code do you run on the XR side?
privilege level you mean? is a emulation on cisco CML, i don't know if it has a limitation
Can you provide the output for the command "show route 55.55.55.55/32 detail private"?
RP/0/RP0/CPU0:ios#show route 55.55.55.55/32 detail private
Sun Aug 24 05:08:30.466 UTC
Routing entry for 55.55.55.55/32
Known via "isis 1", distance 115, metric 30, labeled SR, type level-2
Installed Aug 24 05:03:31.639 for 00:04:59
Routing Descriptor Blocks
10.11.101.11, from 55.55.55.55, via GigabitEthernet0/0/0/1
Route metric is 30
Label: 0x3eb7 (16055)
Tunnel ID: None
Binding Label: None
Extended communities count: 0
Path id:1 Path ref count:0
NHID: 0x2 (Ref: 17)
Path flags: 0x0 ()
Private flags: 0xa (has_vpn_data, label_stack)
Route version is 0x17 (23)
Local Label: 0x3eb7 (16055)
IP Precedence: Not Set
QoS Group ID: Not Set
Flow-tag: Not Set
Fwd-class: Not Set
Route Priority: RIB_PRIORITY_NON_RECURSIVE_MEDIUM (7) SVD Type RIB_SVD_TYPE_LOCAL
Download Priority 1, Download Version 174
Client-id: 54
Route flags: 0x8800000 (ldp_sr_merge_request, label_sr)
Route Extended flags: 0x8 (ldp_sr_merge_request)
Route private flags: 0x20 (priority_promotion)
Route private flags2: 0x0 ()
Route head pointer: 0x7fa3e9fcf920
Local Label List
i 16055 (Client ID: 54, Distance: 115, Metric: 30)
B 24004 (Client ID: 52, Distance: 255, Metric: 4294967295)
No advertising protos.
BGP LOGs after reset
Sun Aug 24 17:37:42.657 UTC
RP/0/RP0/CPU0:Aug 24 17:31:26.081 UTC: bpm[1105]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-active:(bgp-bpm-active)inst-id 0, Service Published
RP/0/RP0/CPU0:Aug 24 17:31:28.912 UTC: bgp[1090]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : default, process instance 1:(A)inst-id 0, Connection Establised
RP/0/RP0/CPU0:Aug 24 17:31:29.694 UTC: bgp[1090]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : default:(A)inst-id 0, Initial Config Done
RP/0/RP0/CPU0:Aug 24 17:32:08.039 UTC: bgp[1090]: %ROUTING-BGP-5-ADJCHANGE : neighbor 10.100.200.1 Up (VRF: default) (AS: 1000)
RP/0/RP0/CPU0:Aug 24 17:32:08.040 UTC: bgp[1090]: %ROUTING-BGP-5-NSR_STATE_CHANGE : Changed state to Not NSR-Ready
RP/0/RP0/CPU0:Aug 24 17:32:08.707 UTC: bgp[1090]: %ROUTING-BGP-3-RIB_FAIL : [9149] : Failed to Redist since prefix sid is out of SRGB inside calculate origin for TBL:default (1/1) while calling the RIB instance 0: Success
RP/0/RP0/CPU0:Aug 24 17:32:11.945 UTC: bgp[1090]: %ROUTING-BGP-5-ADJCHANGE : neighbor 55.55.55.55 Up (VRF: default) (AS: 3000)
RP/0/RP0/CPU0:Aug 24 17:32:11.964 UTC: rib_mgr[1256]: %ROUTING-RIB-3-LABEL_ERR_ADD : Add local-label 24007 (2) for table 0xe0000000, prefix 55.55.55.55/128, by proto bgp client 51 bgp node0_RP0_CPU0 - existing label 16055 added by proto-id 7 client 54
the actual configuration on XR-pe and Pe3
RP/0/RP0/CPU0:ios#sh running-config
Sun Aug 24 17:48:30.085 UTC
!! Building configuration...
!! IOS XR Configuration 24.3.1
!! Last configuration change at Sun Aug 24 02:41:57 2025 by cisco
!
logging console disable
username cisco
group root-lr
group cisco-support
secret 10 $6$9PYu7/4dSGeb27/.$5YWzSZXYv6xvXsaNp4GCXlIzLi9za0pWmqIr.4Tq6ZEfGHFDCDLDsT.q2lX8PZBKTs39gc5NXWTv01xFSIHM91
!
line console
exec-timeout 0 0
absolute-timeout 0
session-timeout 0
!
line default
exec-timeout 0 0
absolute-timeout 0
session-timeout 0
!
interface Loopback1
ipv4 address 130.130.130.130 255.255.255.255
!
interface MgmtEth0/RP0/CPU0/0
shutdown
!
interface GigabitEthernet0/0/0/0
shutdown
!
interface GigabitEthernet0/0/0/1
ipv4 address 10.11.101.101 255.255.255.0
!
interface GigabitEthernet0/0/0/2
shutdown
!
interface GigabitEthernet0/0/0/3
ipv4 address 10.100.200.2 255.255.255.252
!
route-policy SID($SID)
set label-index $SID
end-policy
!
route-policy default
pass
end-policy
!
router static
address-family ipv4 unicast
10.100.200.1/32 GigabitEthernet0/0/0/3
!
!
router isis 1
is-type level-2-only
net 49.0001.0000.0000.0101.00
address-family ipv4 unicast
metric-style wide
router-id Loopback1
segment-routing mpls
!
interface Loopback1
address-family ipv4 unicast
prefix-sid index 101
!
!
interface GigabitEthernet0/0/0/1
point-to-point
address-family ipv4 unicast
!
!
interface GigabitEthernet0/0/0/3
passive
address-family ipv4 unicast
!
!
!
router bgp 3000
bgp router-id 130.130.130.130
address-family ipv4 unicast
network 55.55.55.55/32 route-policy SID(55)
allocate-label all
!
neighbor 55.55.55.55
remote-as 3000
update-source Loopback1
address-family ipv4 labeled-unicast
next-hop-self
!
!
neighbor 10.100.200.1
remote-as 1000
egress-engineering
update-source GigabitEthernet0/0/0/3
address-family ipv4 labeled-unicast
route-policy default in
route-policy default out
!
!
!
segment-routing
!
end
Building configuration...
Current configuration : 9174 bytes
!
! Last configuration change at 05:56:05 UTC Sun Aug 24 2025
!
version 17.3
service timestamps debug datetime msec
service timestamps log datetime msec
service call-home
platform qfp utilization monitor load 80
platform punt-keepalive disable-kernel-core
platform console serial
!
hostname PE3
!
boot-start-marker
boot-end-marker
!
!
vrf definition 1000:101
rd 1000:101
!
address-family ipv4
route-target export 1000:101
route-target import 1000:101
exit-address-family
!
no logging console
!
no aaa new-model
!
!
!
!
!
!
!
!
!
!
login on-success log
!
!
!
!
!
!
!
subscriber templating
!
!
!
!
!
!
mpls label range 3000 3999
mpls traffic-eng tunnels
multilink bundle-name authenticated
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
crypto pki trustpoint SLA-TrustPoint
enrollment pkcs12
revocation-check crl
!
crypto pki trustpoint TP-self-signed-3888238503
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3888238503
revocation-check none
rsakeypair TP-self-signed-3888238503
!
!
crypto pki certificate chain SLA-TrustPoint
certificate ca 01
30820321 30820209 A0030201 02020101 300D0609 2A864886 F70D0101 0B050030
32310E30 0C060355 040A1305 43697363 6F312030 1E060355 04031317 43697363
6F204C69 63656E73 696E6720 526F6F74 20434130 1E170D31 33303533 30313934
3834375A 170D3338 30353330 31393438 34375A30 32310E30 0C060355 040A1305
43697363 6F312030 1E060355 04031317 43697363 6F204C69 63656E73 696E6720
526F6F74 20434130 82012230 0D06092A 864886F7 0D010101 05000382 010F0030
82010A02 82010100 A6BCBD96 131E05F7 145EA72C 2CD686E6 17222EA1 F1EFF64D
CBB4C798 212AA147 C655D8D7 9471380D 8711441E 1AAF071A 9CAE6388 8A38E520
1C394D78 462EF239 C659F715 B98C0A59 5BBB5CBD 0CFEBEA3 700A8BF7 D8F256EE
4AA4E80D DB6FD1C9 60B1FD18 FFC69C96 6FA68957 A2617DE7 104FDC5F EA2956AC
7390A3EB 2B5436AD C847A2C5 DAB553EB 69A9A535 58E9F3E3 C0BD23CF 58BD7188
68E69491 20F320E7 948E71D7 AE3BCC84 F10684C7 4BC8E00F 539BA42B 42C68BB7
C7479096 B4CB2D62 EA2F505D C7B062A4 6811D95B E8250FC4 5D5D5FB8 8F27D191
C55F0D76 61F9A4CD 3D992327 A8BB03BD 4E6D7069 7CBADF8B DF5F4368 95135E44
DFC7C6CF 04DD7FD1 02030100 01A34230 40300E06 03551D0F 0101FF04 04030201
06300F06 03551D13 0101FF04 05300301 01FF301D 0603551D 0E041604 1449DC85
4B3D31E5 1B3E6A17 606AF333 3D3B4C73 E8300D06 092A8648 86F70D01 010B0500
03820101 00507F24 D3932A66 86025D9F E838AE5C 6D4DF6B0 49631C78 240DA905
604EDCDE FF4FED2B 77FC460E CD636FDB DD44681E 3A5673AB 9093D3B1 6C9E3D8B
D98987BF E40CBD9E 1AECA0C2 2189BB5C 8FA85686 CD98B646 5575B146 8DFC66A8
467A3DF4 4D565700 6ADF0F0D CF835015 3C04FF7C 21E878AC 11BA9CD2 55A9232C
7CA7B7E6 C1AF74F6 152E99B7 B1FCF9BB E973DE7F 5BDDEB86 C71E3B49 1765308B
5FB0DA06 B92AFE7F 494E8A9E 07B85737 F3A58BE1 1A48A229 C37C1E69 39F08678
80DDCD16 D6BACECA EEBC7CF9 8428787B 35202CDC 60E4616A B623CDBD 230E3AFB
418616A9 4093E049 4D10AB75 27E86F73 932E35B5 8862FDAE 0275156F 719BB2F0
D697DF7F 28
quit
crypto pki certificate chain TP-self-signed-3888238503
certificate self-signed 01
30820330 30820218 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 33383838 32333835 3033301E 170D3235 30383131 32313237
32345A17 0D333530 38313132 31323732 345A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D33 38383832
33383530 33308201 22300D06 092A8648 86F70D01 01010500 0382010F 00308201
0A028201 0100B569 9B7DC137 CCFF1BBB 84558DB6 8BE9E513 627BB54E C34084F4
7998FFC3 9E468727 DE83F652 FC7B95ED 220913E6 267D6AE5 9E207102 D4691242
0E066CC2 307339AB FD2E01D1 C5D4F195 6E075AE8 5B69BCBB FA97AA61 164F88C4
7BA29A92 45D888F5 471B54E4 9105466E 24C713D8 24A5A6F6 DC70AD84 48014838
86DBBADB CE07965A 8431B91D 630BF8B2 1A49E892 AE475BE2 4E34B2A4 162E29B6
0ABEE062 72219FC4 C6F2231C B20E0BE0 EFA164EE 4E917506 57AA01B2 2F930D4B
42E9281C 81D3823D 845F78B8 11A1D089 13772F5A B05282CE F6B878CB 0A988EA2
7C021116 321327F5 DAFE36C8 AD185422 0CA1B03B CEF01A50 BB8AD138 3AF02AA1
C8B81741 BA6B0203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF
301F0603 551D2304 18301680 146B6810 F1D8F459 C82CE2DE D00F3CF0 E0077788
0A301D06 03551D0E 04160414 6B6810F1 D8F459C8 2CE2DED0 0F3CF0E0 0777880A
300D0609 2A864886 F70D0101 05050003 82010100 7CAED39C 87E58089 B57EB0FF
D366C63D EC17ACE4 88893C44 F316307C 89DD7F71 8FD3CFBF E13112D4 74E2C8E2
54778F3B 4544D256 7977E6A5 3BD628A7 91063694 AA041142 B05ED933 15B0B2EC
970FDF33 877ADEBD F20E4416 DF497F33 E3BC01BE EF703926 00397D28 F007A5A5
E20DF966 E23B72D2 921913AB CEAA248E ADFBF32B 07AD420E 991F6AD7 140EFFB6
7D258966 A1C38127 8BB3835F B09E9C43 73F2819B EDE72C92 A27E576A 3FC82B64
C42B7C1E 2E112ADF 045E36AA 2FA6FFD8 CA1C6169 0BDA02D6 D644CB14 007D40F2
26001891 81C20AD0 3EE9C872 214510D3 E5B057D1 C0509B59 3A1BCCED BC67100C
65E0626C 27AA3A9F B28791C7 2A6322AE 3E331682
quit
!
license udi pid CSR1000V sn 9EE6Q20PF5C
diagnostic bootup level minimal
archive
path bootflash:
memory free low-watermark processor 71464
!
!
spanning-tree extend system-id
!
!
redundancy
!
bridge-domain 20
member BD-VIF 20
!
!
!
!
!
!
!
l2 vfi vpls1 manual
vpn id 101
bridge-domain 15
neighbor 11.11.11.11 1133 encapsulation mpls
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
ip address 33.33.33.33 255.255.255.255
ip ospf 1 area 0
!
interface GigabitEthernet1
ip address 10.100.33.33 255.255.255.0
ip ospf network point-to-point
negotiation auto
no mop enabled
no mop sysid
!
interface GigabitEthernet2
ip address 10.100.43.33 255.255.255.0
ip ospf network point-to-point
negotiation auto
no mop enabled
no mop sysid
!
interface GigabitEthernet3
ip address 10.100.200.1 255.255.255.252
ip ospf network point-to-point
ip ospf 1 area 0
negotiation auto
mpls bgp forwarding
no mop enabled
no mop sysid
!
interface GigabitEthernet4
no ip address
negotiation auto
no mop enabled
no mop sysid
service instance 10 ethernet
description l2 vpn client 1
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
xconnect 11.11.11.11 1001 encapsulation mpls
!
service instance 15 ethernet
description manual vpls client 1
encapsulation dot1q 15
rewrite ingress tag pop 1 symmetric
bridge-domain 15
!
service instance 20 ethernet
description L3 vpn client 1
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
!
!
interface GigabitEthernet5
no ip address
shutdown
negotiation auto
no mop enabled
no mop sysid
!
interface GigabitEthernet6
no ip address
shutdown
negotiation auto
no mop enabled
no mop sysid
!
interface GigabitEthernet7
no ip address
shutdown
negotiation auto
no mop enabled
no mop sysid
!
interface GigabitEthernet8
no ip address
shutdown
negotiation auto
no mop enabled
no mop sysid
!
interface BD-VIF20
vrf forwarding 1000:101
ip address 192.168.3.1 255.255.255.248
ip ospf network point-to-point
ip ospf 1000 area 0
no mop enabled
no mop sysid
!
!
segment-routing mpls
!
router ospf 1000 vrf 1000:101
router-id 192.168.3.1
area 0 sham-link 10.200.33.33 10.200.11.11
!
router ospf 1
router-id 33.33.33.33
network 10.100.0.0 0.0.0.0 area 0
network 10.100.0.0 0.0.255.255 area 0
mpls ldp sync
mpls ldp autoconfig
mpls traffic-eng router-id Loopback1
mpls traffic-eng area 0
!
router bgp 1000
bgp router-id interface Loopback1
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 5.5.5.5 remote-as 1000
neighbor 5.5.5.5 update-source Loopback1
neighbor 10.100.200.2 remote-as 3000
neighbor 10.100.200.2 update-source GigabitEthernet3
!
address-family ipv4
network 33.33.33.33 mask 255.255.255.255
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 next-hop-self
neighbor 5.5.5.5 send-label
neighbor 10.100.200.2 activate
neighbor 10.100.200.2 next-hop-self
neighbor 10.100.200.2 send-label
exit-address-family
!
address-family vpnv4
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 send-community both
exit-address-family
!
address-family ipv4 vrf 1000:101
redistribute connected
redistribute ospf 1000
exit-address-family
!
ip forward-protocol nd
no ip http server
ip http secure-server
!
!
!
ip access-list standard 1
10 deny 10.200.11.11
20 deny 10.200.33.33
30 permit any
ip access-list standard 2
10 permit 5.5.5.5
!
!
route-map shamlink-client1 permit 10
match ip address 1
!
route-map inter-as permit 10
match ip address 2
!
route-map inter-as deny 25
!
mpls ldp router-id Loopback1 force
!
!
!
control-plane
!
!
!
!
!
!
line con 0
exec-timeout 0 0
stopbits 1
line vty 0
exec-timeout 0 0
login
transport input ssh
line vty 1
exec-timeout 0 0
login
length 0
transport input ssh
line vty 2 4
exec-timeout 0 0
login
transport input ssh
!
call-home
! If contact email address in call-home is configured as sch-smart-licensing@cisco.com
! the email address configured in Cisco Smart License Portal will be used as contact email address to send SCH notifications.
contact-email-addr sch-smart-licensing@cisco.com
profile "CiscoTAC-1"
active
destination transport-method http
!
!
!
!
!
end
08-24-2025 12:08 PM - edited 08-24-2025 12:10 PM
Thanks for the additional info @heiliger-eliet .
> What level of code do you run on the XR side?
I meant the IOS-XR version, but I see in the last provided output that you run IOS-XR 24.3.1.
I quickly tried to reproduce the issue and I see what triggers this issue.
Can you add the following command to your XR configuration and reload IOS-XR.
segment-routing
global-block 16000 23999
Then reload XR. It should fix it.
08-24-2025 12:54 PM
Woo now it works !! The label 24004 now have a label for transport on the side of SR
also the the communication end to end on VRF work
@Harold Ritter thank a lot for your time , I was reading the documentation of SR on BGP in IOs XR, but I by pass para that explain the global mus be explicit configure.
Thanks a lot
08-24-2025 01:00 PM - edited 08-24-2025 01:08 PM
You are very welcome @heiliger-eliet .
Yes, I have seen many issues in the past when the global block was not explicitly configured. It is better to find out in the lab, like you did than in a production network.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide