06-12-2024 04:18 AM
I was working on a maintenance window. moving some customers to our new MPLS network PE router NCS540 SOFTWARE 7.6.2.
When I move 192.168.70.0/24 to the new mpls network I was able to ping it from everywhere. however a static routed network I was not able to reach even though I could see the route advertized everywhere in the network
int bvi 100
vrf CORE_14288
ipv4 address 192.168.70.1 255.255.255.0
!
router bgp 11749
vrf CORE_14288
rd auto
address-family ipv4 unicast
redistribute connected
redistribute static
!
!
router static
vrf CORE_14288
address-family ipv4 unicast
192.168.10.0/27 192.168.70.2
After doing some digging I found that the redistribute static was not allowing the traffic to pass thru even though I could see it advertized from every PE in the network.
If I hardcode it like shown below, it works.
router bgp xxxx
vrf CORE_14288
address-family ipv4 unicast
192.168.10.0/27 192.168.70.2
!
!
I opened a ticket with cisco just to make sure this is not a bug, but I'm curious to see if anybody has experience the same behaviour.
Solved! Go to Solution.
06-12-2024 01:13 PM
Hi @DanielGutierrez615 ,
The first label (26065) is a per vrf label and is allocated by the network statement. The second one (26085) is a per prefix/per CE label and is generated by the redistribute static statement.
It looks like there might be an issue when the per prefix/per CE is used, possibly because of the BVI interface. You could validate that by changing the label mode under the VRF and verify that it works with the redistribute static as well.
router bgp xxx
vrf CORE_14288
address-family ipv4 unicast
label mode per-vrf
This will cause the label to be allocated per-vrf regardless if you use the network statement or redistribute static statement.
Regards,
06-12-2024 04:36 AM
Did you use rpl abd allow all prefix includes static route
MHM
06-12-2024 05:18 AM - edited 06-12-2024 05:19 AM
Hi @DanielGutierrez615 ,
I am not sure I understand what you did to fix the issue, as the following command is invalid under BGP:
router bgp xxx
vrf CORE_14288
address-family ipv4 unicast
192.168.10.0/27 192.168.70.2
Can you please give us more specific information.
Regards,
06-12-2024 05:40 AM
06-12-2024 05:47 AM
Hi @DanielGutierrez615 ,
Both the "redistribute static" and the network statement should work.
You say that when you use the "redistribute static" the route was learned on the remote sites, but that you could not ping addresses within that subnet, right?
Regards,
06-12-2024 05:50 AM
That is correct Harold. I'm beginning to think that this might be a bug missed on the NCS540-iosxr-k9-7.6.2 software release. I open a ticket with cisco to confirm my theory.
06-12-2024 05:53 AM
Hi @DanielGutierrez615 ,
That definitely sounds like a bug. Please keep up posted on what TAC says.
Regards,
06-12-2024 06:03 AM
when you redistrubte you can not ping
when you use prefix without redistribute you can ping
if above correct
show bgp
check the next hop
it next-hop issue
specially if you use ibgp
MHM
06-12-2024 07:37 AM
you see the route where you use redistribute static or using the network command.
Here is THE OUTPUT wheN is not working with redistribute static
RP/0/RP0/CPU0:SCTLAB-NCS540-02#show bgp vpnv4 unicast vrf CORE_14288
Route Distinguisher: 10.0.24.203:1 (default for vrf CORE_14288)
*>i0.0.0.0/0 10.0.24.2 100 0 14288 174 i
* i 10.0.24.4 100 0 14288 3356 i
*>i66.90.3.108/30 10.0.24.4 0 100 0 ?
*>i66.90.3.144/30 10.0.24.2 0 100 0 ?
*>i207.190.12.96/27 10.0.24.35 0 100 0 ?
*>i216.53.129.228/30 10.0.24.35 0 100 0 ?
*>i216.53.129.236/30 10.0.24.37 0 100 0 ?
*>i216.53.178.168/29 10.0.24.35 0 100 0 ?
*> 216.97.200.64/29 0.0.0.0 0 32768 ?
*>i216.97.200.88/29 10.0.24.34 0 100 0 ?
*> 216.97.207.0/27 216.97.200.66 0 32768 ?
Processed 10 prefixes, 11 paths
Here is THE OUTPUT wheN is working with the network statement.
RP/0/RP0/CPU0:SCTLAB-NCS540-02#show bgp vpnv4 unicast vrf CORE_14288
Route Distinguisher: 10.0.24.203:1 (default for vrf CORE_14288)
*>i0.0.0.0/0 10.0.24.2 100 0 14288 174 i
* i 10.0.24.4 100 0 14288 3356 i
*>i66.90.3.108/30 10.0.24.4 0 100 0 ?
*>i66.90.3.144/30 10.0.24.2 0 100 0 ?
*>i207.190.12.96/27 10.0.24.35 0 100 0 ?
*>i216.53.129.228/30 10.0.24.35 0 100 0 ?
*>i216.53.129.236/30 10.0.24.37 0 100 0 ?
*>i216.53.178.168/29 10.0.24.35 0 100 0 ?
*> 216.97.200.64/29 0.0.0.0 0 32768 ?
*>i216.97.200.88/29 10.0.24.34 0 100 0 ?
*> 216.97.207.0/27 216.97.200.66 0 32768 i
Processed 10 prefixes, 11 paths
06-12-2024 07:40 AM
Sorry I forgot to mention the network I'm trying to reach is 216.97.207.0/27
06-12-2024 07:52 AM - edited 06-12-2024 08:06 AM
Hi @DanielGutierrez615 ,
Could you please provide the following command from SCTLAB-NCS540-02 when it works and when it doesn't.
show bgp vpnv4 unicast vrf CORE_14288 labels
It would be good to check if the label received on remote PE is properly installed on the PE originating it.
Regards,
06-12-2024 09:43 AM
here
This is when it works
RP/0/RP0/CPU0:SCTLAB-NCS540-02#show bgp vpnv4 unicast vrf CORE_14288 labels
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 10.0.24.203:1 (default for vrf CORE_14288)
*>i0.0.0.0/0 10.0.24.2 24009 nolabel
* i 10.0.24.4 26063 nolabel
*>i66.90.3.108/30 10.0.24.4 26061 nolabel
*>i66.90.3.144/30 10.0.24.2 24008 nolabel
*>i207.190.12.96/27 10.0.24.35 26080 nolabel
*>i216.53.129.228/30 10.0.24.35 26080 nolabel
*>i216.53.129.236/30 10.0.24.37 26058 nolabel
*>i216.53.178.168/29 10.0.24.35 26080 nolabel
*> 216.97.200.64/29 0.0.0.0 nolabel 26065
*>i216.97.200.88/29 10.0.24.34 26106 nolabel
*> 216.97.207.0/27 216.97.200.66 nolabel 26065
Processed 10 prefixes, 11 paths
RP/0/RP0/CPU0:SCTLAB-NCS540-02#
here is the output where it does not works
show bgp vpnv4 unicast vrf CORE_14288 labels
RP/0/RP0/CPU0:SCTLAB-NCS540-02#show bgp vpnv4 unicast vrf CORE_14288 labels
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 10.0.24.203:1 (default for vrf CORE_14288)
*>i0.0.0.0/0 10.0.24.2 24009 nolabel
* i 10.0.24.4 26063 nolabel
*>i66.90.3.108/30 10.0.24.4 26061 nolabel
*>i66.90.3.144/30 10.0.24.2 24008 nolabel
*>i207.190.12.96/27 10.0.24.35 26080 nolabel
*>i216.53.129.228/30 10.0.24.35 26080 nolabel
*>i216.53.129.236/30 10.0.24.37 26058 nolabel
*>i216.53.178.168/29 10.0.24.35 26080 nolabel
*> 216.97.200.64/29 0.0.0.0 nolabel 26065
*>i216.97.200.88/29 10.0.24.34 26106 nolabel
*> 216.97.207.0/27 216.97.200.66 nolabel 26066
Processed 10 prefixes, 11 paths
06-12-2024 08:31 AM
RP/0/0/CPU0:XR1# show mpls forwarding <<- share this for both case
thanks
MHM
06-12-2024 09:47 AM
06-12-2024 09:59 AM
Also from the peering route pespective
it works
RP/0/RP0/CPU0:MTD-RTR-PE1-01#show bgp vpnv4 unicast vrf CORE_14288 labels
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 10.0.24.4:4 (default for vrf CORE_14288)
*> 0.0.0.0/0 66.90.3.109 nolabel 26063
*> 66.90.3.108/30 0.0.0.0 nolabel 26061
*>i66.90.3.144/30 10.0.24.2 24008 nolabel
*>i207.190.12.96/27 10.0.24.35 26080 nolabel
*>i216.53.129.228/30 10.0.24.35 26080 nolabel
*>i216.53.129.236/30 10.0.24.37 26058 nolabel
*>i216.53.178.168/29 10.0.24.35 26080 nolabel
*>i216.97.200.64/29 10.0.24.203 26065 nolabel
*>i216.97.200.88/29 10.0.24.34 26106 nolabel
*>i216.97.207.0/27 10.0.24.203 26065 nolabel <<<<<
does not work
RP/0/RP0/CPU0:MTD-RTR-PE1-01#show bgp vpnv4 unicast vrf CORE_14288 labels
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 10.0.24.4:4 (default for vrf CORE_14288)
*> 0.0.0.0/0 66.90.3.109 nolabel 26063
*> 66.90.3.108/30 0.0.0.0 nolabel 26061
*>i66.90.3.144/30 10.0.24.2 24008 nolabel
*>i207.190.12.96/27 10.0.24.35 26080 nolabel
*>i216.53.129.228/30 10.0.24.35 26080 nolabel
*>i216.53.129.236/30 10.0.24.37 26058 nolabel
*>i216.53.178.168/29 10.0.24.35 26080 nolabel
*>i216.97.200.64/29 10.0.24.203 26065 nolabel
*>i216.97.200.88/29 10.0.24.34 26106 nolabel
*>i216.97.207.0/27 10.0.24.203 26085 nolabel
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