Closed EasyNetDev closed 1 year ago
In the broken state can we see the output of show ip route 89.238.245.113
?
Sure. Give some time to re-enable NHRP daemon. Without NHRP daemon looks everything fine.
I couldn't replicate the bug on the same system, but I think a similar issue I found it in FRR 8.4.2 on a RPi device.
router bgp 43474
bgp router-id 10.100.12.1
!
address-family ipv4 unicast
label vpn export auto
rd vpn export 43474:11012
rt vpn import 43474:11910
rt vpn export 43474:11012
export vpn
import vpn
exit-address-family
!
address-family ipv6 unicast
rd vpn export 43474:11012
rt vpn export 43474:11012
exit-address-family
exit
router bgp 65512 vrf VPN1
neighbor 10.101.1.37 remote-as 43474
neighbor 10.101.1.37 description R01_VPN
neighbor 10.102.1.37 remote-as 43474
neighbor 10.102.1.37 description R02_VPN
!
address-family ipv4 unicast
redistribute connected route-map VPN-export-VPN1-connected
neighbor 10.101.1.37 next-hop-self
neighbor 10.101.1.37 soft-reconfiguration inbound
neighbor 10.101.1.37 route-map VPN-VPN1-received in
neighbor 10.101.1.37 route-map VPN-export-VPN1-advertised out
neighbor 10.102.1.37 soft-reconfiguration inbound
neighbor 10.102.1.37 route-map VPN-VPN1-received in
neighbor 10.102.1.37 route-map VPN-export-VPN1-advertised out
label vpn export auto
rd vpn export 43474:13012
rt vpn import 43474:13000 43474:13990
rt vpn export 43474:13000
export vpn
import vpn
exit-address-family
exit
The the output:
# do sh bgp vrf VPN1 summary
IPv4 Unicast Summary (VRF VPN1):
BGP router identifier 192.168.144.12, local AS number 65512 vrf-id 5
BGP table version 49
RIB entries 13, using 2496 bytes of memory
Peers 2, using 1448 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt Desc
10.101.1.37 4 43474 874 887 0 0 0 00:08:59 5 4 R01_VPN
10.102.1.37 4 43474 242 256 0 0 0 00:00:10 Idle (Admin) 0 R02_VPN
Total number of neighbors 2
R12(config-router)# do sh bgp vrf VPN1 ipv4
BGP table version is 49, local router ID is 192.168.144.12, vrf id 5
Default local pref 100, local AS 65512
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
0.0.0.0/0 10.101.1.37 0 0 43474 i
10.100.1.10/32 10.101.1.37 0 0 43474 ?
10.101.1.32/30 10.101.1.37 0 0 43474 ?
10.101.1.36/30 10.101.1.37 0 0 43474 ?
*> 0.0.0.0 0 32768 ?
10.102.1.32/30 10.101.1.37 0 43474 ?
*> 10.102.1.36/30 0.0.0.0 0 32768 ?
*> 192.168.143.0/24 0.0.0.0 0 32768 ?
*> 192.168.144.12/32
0.0.0.0 0 32768 ?
Displayed 8 routes and 9 total paths
R12(config-router)# do sh bgp vrf VPN1 ipv4 0.0.0.0/0
BGP routing table entry for 0.0.0.0/0, version 45
Paths: (1 available, no best path)
Not advertised to any peer
43474
10.101.1.37 (inaccessible) from 10.101.1.37 (10.100.1.10)
Origin IGP, metric 0, invalid, external
Last update: Thu Mar 30 14:31:11 2023
R12(config-router)# do sh ip route vrf VPN1
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
VRF VPN1:
S>* 0.0.0.0/0 [250/0] unreachable (blackhole), weight 1, 00:15:03
C>* 10.101.1.36/30 is directly connected, wg120102, 13:52:13
C>* 10.102.1.36/30 is directly connected, wg120202, 03:44:56
C>* 169.254.0.0/16 is directly connected, VPN1, 13:52:06
C>* 192.168.143.0/24 is directly connected, wlan0, 13:26:38
C>* 192.168.144.12/32 is directly connected, VPN1, 13:50:51
R12(config-router)# do sh ip route vrf VPN1 10.101.1.37
Routing entry for 10.101.1.36/30
Known via "connected", distance 0, metric 0, vrf VPN1, best
Last update 13:52:54 ago
* directly connected, wg120102
I don't know if the bugs are correlated, but I will try to compile latest version of FRR on RPi.
This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose
label in order to avoid having this issue closed.
This issue will be automatically closed in the specified period unless there is further activity.
Describe the bug BGP LDP MPLS keeps static route over MPLS.
To Reproduce
Expected behavior
The static route should stay static.
Screenshots
MPLS config:
Internet VRF:
VRF Internet:
As you can see 193.230.200.47 is configured over 89.238.245.113 as a static route.
Output:
If I delete the static route from VRF internet:
Readd static route:
Checking local connection for po1.650:
After a shut/no shut over po1.650 interface then line protocol is going up.
And also I'm noticing a lot of "Route install failed" like this message:
This error I'm not sure if is related to the same issue.
Versions
Additional context