Closed Madhu-api closed 10 months ago
Please show the output of show ip route
, show ip nht
.
madhuVM3# show ip route
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, t - Table-Direct,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
K>* 0.0.0.0/0 [0/0] via 10.0.2.2, enp0s3, 00:29:26
C>* 10.0.2.0/24 is directly connected, enp0s3, 02:51:46
K>* 10.0.2.2/32 [0/100] is directly connected, enp0s3, 02:51:46
S>* 22.22.22.1/32 [1/0] via 192.168.62.220, enp0s8, weight 1, 00:53:10
C>* 192.168.62.0/24 is directly connected, enp0s8, 02:51:46
C>* 192.168.131.0/24 is directly connected, enp0s9, 02:51:46
madhuVM3#
madhuVM3#
madhuVM3# show ip nht
VRF default:
Resolve via default: on
22.22.22.1
resolved via static
via 192.168.62.220, enp0s8 (vrf default), weight 1
Client list: bgp(fd 17)
192.168.62.220
resolved via connected
is directly connected, enp0s8 (vrf default)
Client list: static(fd 43)
madhuVM3#
VM2
madhuVM4# show ip route
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, t - Table-Direct,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
K>* 0.0.0.0/0 [0/0] via 10.0.2.2, enp0s3, 00:30:26
C>* 10.0.2.0/24 is directly connected, enp0s3, 02:52:51
K>* 10.0.2.2/32 [0/100] is directly connected, enp0s3, 02:52:51
S>* 11.11.11.1/32 [1/0] via 192.168.62.222, enp0s8, weight 1, 00:54:41
C>* 192.168.62.0/24 is directly connected, enp0s8, 02:52:51
C>* 192.168.131.0/24 is directly connected, enp0s9, 02:52:51
madhuVM4#
madhuVM4#
madhuVM4# show ip nht
VRF default:
Resolve via default: on
11.11.11.1
resolved via static
via 192.168.62.222, enp0s8 (vrf default), weight 1
Client list: bgp(fd 17)
192.168.62.222
resolved via connected
is directly connected, enp0s8 (vrf default)
Client list: static(fd 43)
madhuVM4#
Also show the output of show bgp neighbors
.
VM1
madhuVM3# show ip bgp neighbors
BGP neighbor is 22.22.22.1, remote AS 100, local AS 100, internal link
Local Role: undefined
Remote Role: undefined
BGP version 4, remote router ID 0.0.0.0, local router ID 11.11.11.1
BGP state = Active
Last read 00:17:36, Last write never
Hold time is 180 seconds, keepalive interval is 60 seconds
Configured hold time is 180 seconds, keepalive interval is 60 seconds
Configured tcp-mss is 0, synced tcp-mss is 0
Configured conditional advertisements interval is 60 seconds
Graceful restart information:
Local GR Mode: Helper*
Remote GR Mode: NotApplicable
R bit: False
N bit: False
Timers:
Configured Restart Time(sec): 120
Received Restart Time(sec): 0
Configured LLGR Stale Path Time(sec): 0
Message statistics:
Inq depth is 0
Outq depth is 0
Sent Rcvd
Opens: 0 0
Notifications: 0 0
Updates: 0 0
Keepalives: 0 0
Route Refresh: 0 0
Capability: 0 0
Total: 0 0
Minimum time between advertisement runs is 0 seconds
Update source is lo:11
For address family: IPv4 Unicast
Not part of any update group
Inbound soft reconfiguration allowed
Community attribute sent to this neighbor(all)
0 accepted prefixes
Connections established 0; dropped 0
Last reset 00:17:36, Socket Error (n/a)
Internal BGP neighbor may be up to 255 hops away.
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 24 seconds
Read thread: off Write thread: off FD used: -1
madhuVM3#
VM2
madhuVM4# show ip bgp neighbors
BGP neighbor is 11.11.11.1, remote AS 100, local AS 100, internal link
Local Role: undefined
Remote Role: undefined
BGP version 4, remote router ID 0.0.0.0, local router ID 22.22.22.1
BGP state = Active
Last read 00:18:31, Last write never
Hold time is 180 seconds, keepalive interval is 60 seconds
Configured hold time is 180 seconds, keepalive interval is 60 seconds
Configured tcp-mss is 0, synced tcp-mss is 0
Configured conditional advertisements interval is 60 seconds
Graceful restart information:
Local GR Mode: Helper*
Remote GR Mode: NotApplicable
R bit: False
N bit: False
Timers:
Configured Restart Time(sec): 120
Received Restart Time(sec): 0
Configured LLGR Stale Path Time(sec): 0
Message statistics:
Inq depth is 0
Outq depth is 0
Sent Rcvd
Opens: 0 0
Notifications: 0 0
Updates: 0 0
Keepalives: 0 0
Route Refresh: 0 0
Capability: 0 0
Total: 0 0
Minimum time between advertisement runs is 0 seconds
Update source is lo:22
For address family: IPv4 Unicast
Not part of any update group
Inbound soft reconfiguration allowed
Community attribute sent to this neighbor(all)
0 accepted prefixes
Connections established 0; dropped 0
Last reset 00:18:31, Socket Error (n/a)
Internal BGP neighbor may be up to 255 hops away.
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 89 seconds
Read thread: off Write thread: off FD used: -1
madhuVM4#
Socket errors means most likely you specified the wrong update source in neighbor 22.22.22.1 update-source lo:11
. Try using an explicit IP address.
FRRouting 9.2-dev-MyOwnFRRVersion-gf6d708bc8 on Linux(5.4.0-166-generic).
lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal
Two FRR routers (VMs) are connected in IBGP mode
lo:11 VM1 =(enp0s8)=================(enp0s8)=VM2 lo:22 11.11.11.11/32 192.168.62.222 192.168.62.220 22.22.22.1/32
VM1 and VM2 are in AS 100
VM1 is having BGP neighbor ip as VM2's loopback ip (i.e.,22.22.22.1) VM2 is having BGP neighbor ip as VM1's loopback ip (i.e.,11.11.11.1) VM2 is having a static route to reach VM2's loopback ip VM2 is having a static route to reach VM1's loopback ip
neighbor ip's are reachable and pingable from each VM's
Problem is that iBGP neighborship is NOT forming (stays in 'Active' mode)
running-config from each router is attached below. Please let me know if any config. is missing out and why iBGP neighborship is not establishing.
VM1
VM2
Ping from VM1
Ping from VM2
neighbor status in VM1:
neighbor status in VM2:
Events
show interface brief
FRR version
Note: same config. with eBGP and disable connected-check is also not working. depending on this issue's triage, I will raise a new issue if required.