Frr: FFR bgpd is run but no send bgp packet ?
[FRR run info ]
-bash-4.2# systemctl status frr
โ frr.service - FRRouting (FRR)
Loaded: loaded (/usr/lib/systemd/system/frr.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 2018-12-13 10:47:39 CST; 3h 0min ago
Process: 10449 ExecStop=/usr/lib/frr/frr stop (code=exited, status=0/SUCCESS)
Process: 10656 ExecStart=/usr/lib/frr/frr start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/frr.service
โโ10679 /usr/lib/frr/zebra -d -s 90000000 --daemon -A 127.0.0.1
โโ10686 /usr/lib/frr/bgpd -d --daemon -A 127.0.0.1
โโ10696 /usr/lib/frr/ripd -d --daemon -A 127.0.0.1
โโ10704 /usr/lib/frr/ripngd -d --daemon -A ::1
โโ10712 /usr/lib/frr/ospfd -d --daemon -A 127.0.0.1
โโ10720 /usr/lib/frr/ospf6d -d --daemon -A ::1
โโ10728 /usr/lib/frr/isisd -d --daemon -A 127.0.0.1
โโ10736 /usr/lib/frr/ldpd -L
โโ10737 /usr/lib/frr/ldpd -E
โโ10738 /usr/lib/frr/ldpd -d --daemon -A 127.0.0.1
โโ10747 /usr/lib/frr/babeld -d --daemon -A 127.0.0.1
โโ10755 /usr/lib/frr/staticd -d --daemon -A 127.0.0.1
โโ10765 /usr/lib/frr/watchfrr -d -b_ -r/usr/lib/frr/frr_restart_%s -s/usr/lib/frr/frr_start_%s -k/usr/lib/frr/frr_stop_%s zebra bgpd ripd ripn...
Dec 13 10:47:39 KVM-2 watchfrr[10765]: ospf6d state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: bgpd state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: ripd state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: staticd state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: ripngd state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: ldpd state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: ospfd state -> up : connect succeeded
Dec 13 10:47:39 KVM-2 watchfrr[10765]: Watchfrr: Notifying Systemd we are up and running
Dec 13 10:47:39 KVM-2 frr[10656]: watchfrr[ OK ]
Dec 13 10:47:39 KVM-2 systemd[1]: Started FRRouting (FRR).
[FRR BGPD ]
tcp 0 0 127.0.0.1:2605 0.0.0.0:* LISTEN 10686/bgpd
[configure]
frr-route# show running-config
Building configuration...
Current configuration:
!
frr version 6.0
frr defaults traditional
hostname Router
no ipv6 forwarding
hostname KVM-2
log file router
hostname frr-route
username root nopassword
!
debug bgp keepalives
debug bgp neighbor-events
debug bgp update-groups
debug bgp updates in
debug bgp updates out
debug bgp zebra
!
password alinux123
enable password alinux123
!
router bgp 300
bgp router-id 100.118.127.248
neighbor 100.118.126.78 remote-as 300
neighbor 100.118.126.78 update-source 100.118.127.248
!
line vty
!
end
[BGPD status]
end
frr-route# show ip bgp neighbors
BGP neighbor is 100.118.126.78, remote AS 300, local AS 300, internal link
BGP version 4, remote router ID 0.0.0.0, local router ID 100.118.127.248
BGP state = Active
Last read 02:39:19, Last write never
Hold time is 180, keepalive interval is 60 seconds
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 100.118.127.248
For address family: IPv4 Unicast
Not part of any update group
Community attribute sent to this neighbor(all)
0 accepted prefixes
Connections established 0; dropped 0
Last reset never
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 43 seconds
Read thread: off Write thread: off
[question]
I watched BGPD for several minutes without sending a message. What's the reason?
BGP neighbor is 100.118.126.78, remote AS 300, local AS 300, internal link
BGP version 4, remote router ID 0.0.0.0, local router ID 100.118.127.248
BGP state = Active
Last read 02:39:19, Last write never
Hold time is 180, keepalive interval is 60 seconds
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
[system env]
Linux 4.9.13-1.el7.centos.x86_64 #1 SMP Mon Feb 27 17:01:27 CST 2017 x86_64 x86_64 x86_64 GNU/Linux
net.ipv4.ip_forward = 1
zhangyigui
All 11 comments
I use frr-5.0.1-2018070501.el7.centos.x86_64.rpm version is OK
[ run info ]
BGP neighbor is 100.118.126.78, remote AS 300, local AS 300, internal link
Hostname: centos7-K8s-M-etcd1
BGP version 4, remote router ID 100.118.126.78
BGP state = Established, up for 00:00:48
Last read 00:00:47, Last write 00:00:47
Hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
4 Byte AS: advertised and received
AddPath:
IPv4 Unicast: RX advertised IPv4 Unicast and received
Route refresh: advertised and received(old & new)
Address Family IPv4 Unicast: advertised and received
Hostname Capability: advertised (name: KVM-2,domain name: n/a) received (name: centos7-K8s-M-etcd1,domain name: n/a)
Graceful Restart Capabilty: advertised and received
Remote Restart timer is 120 seconds
Address families by peer:
none
Graceful restart informations:
End-of-RIB send: IPv4 Unicast
End-of-RIB received: IPv4 Unicast
Message statistics:
Inq depth is 0
Outq depth is 0
Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 1 1
Keepalives: 1 1
Route Refresh: 0 0
Capability: 0 0
Total: 3 3
Minimum time between advertisement runs is 0 seconds
Update source is 100.118.127.248
For address family: IPv4 Unicast
Update group 1, subgroup 1
Packet Queue length 0
Community attribute sent to this neighbor(all)
0 accepted prefixes
Connections established 1; dropped 0
Last reset never
Local host: 100.118.127.248, Local port: 44549
Foreign host: 100.118.126.78, Foreign port: 179
Nexthop: 100.118.127.248
Nexthop global: fe80::a423:21ff:fe47:7245
Nexthop local: fe80::a423:21ff:fe47:7245
BGP connection: non shared network
BGP Connect Retry Timer in Seconds: 120
Read thread: on Write thread: on
frr-route# show bgp neighbors
BGP neighbor is 100.118.126.78, remote AS 300, local AS 300, internal link
Hostname: centos7-K8s-M-etcd1
BGP version 4, remote router ID 100.118.126.78
BGP state = Established, up for 00:04:22
Last read 00:00:22, Last write 00:00:22
Hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
4 Byte AS: advertised and received
AddPath:
IPv4 Unicast: RX advertised IPv4 Unicast and received
Route refresh: advertised and received(old & new)
Address Family IPv4 Unicast: advertised and received
Hostname Capability: advertised (name: KVM-2,domain name: n/a) received (name: centos7-K8s-M-etcd1,domain name: n/a)
Graceful Restart Capabilty: advertised and received
Remote Restart timer is 120 seconds
Address families by peer:
none
Graceful restart informations:
End-of-RIB send: IPv4 Unicast
End-of-RIB received: IPv4 Unicast
Message statistics:
Inq depth is 0
Outq depth is 0
Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 1 1
Keepalives: 5 5
Route Refresh: 0 0
Capability: 0 0
Total: 7 7
Minimum time between advertisement runs is 0 seconds
Update source is 100.118.127.248
centos7-K8s-M-etcd1 version is [ frr-6.0-001.el7.centos.x86_64.rpm ] but it [centos7-K8s-M-etcd1] no send bgp packet.
centos7-K8s-M-etcd1# show ip bgp summary
IPv4 Unicast Summary:
BGP router identifier 100.118.126.78, local AS number 300 vrf-id 0
BGP table version 0
RIB entries 0, using 0 bytes of memory
Peers 1, using 21 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
100.118.127.248 4 300 8 8 0 0 0 00:05:19 0
zhangyigui
on 13 Dec 2018
What's the output of show ip bgp nexthop
donaldsharp
on 13 Dec 2018
@zhangyigui Please turn on debug bgp neighbor-events, bring up bgpd, and dump any log messages from bgpd here. When you do, please use the code block syntax, it is difficult to read logs, config files, and output originally aligned with a monospace font if you do not.
qlyoung
on 13 Dec 2018
I same config in frr-5.0 is runing ok ,but this [frr-6.0-001.el7.centos.x86_64.rpm] version isn't working correctly.
{show ip bgp nexthop}
FFR version is [ frr-6.0-001.el7.centos.x86_64.rpm ]
show ip bgp nexthop
frr-route# show ip bgp nexthop
Current BGP nexthop cache:
100.118.126.78 invalid
Last update: Fri Dec 14 09:53:14 2018
frr-route# 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, D - SHARP,
F - PBR,
> - selected route, * - FIB route
K>* 0.0.0.0/0 [0/0] via 100.118.127.1, br0, 00:06:34
C * 100.118.127.0/24 is directly connected, br0, 00:06:34
C>* 100.118.127.0/24 is directly connected, br0, 00:06:34
K * 169.254.0.0/16 [0/1012] is directly connected, br0, 00:06:34
K>* 169.254.0.0/16 [0/1002] is directly connected, enp4s0, 00:06:34
frr-route# ping 100.118.126.78
PING 100.118.126.78 (100.118.126.78) 56(84) bytes of data.
64 bytes from 100.118.126.78: icmp_seq=1 ttl=63 time=0.518 ms
64 bytes from 100.118.126.78: icmp_seq=2 ttl=63 time=0.429 ms
64 bytes from 100.118.126.78: icmp_seq=3 ttl=63 time=0.461 ms
[debug bgp neighbor-events]
2018/12/14 09:59:14 BGP: 100.118.126.78 [FSM] Waiting for NHT
2018/12/14 09:59:14 BGP: 100.118.126.78 went from Active to Connect
2018/12/14 09:59:14 BGP: 100.118.126.78 [FSM] TCP_connection_open_failed (Connect->Active), fd -1
2018/12/14 09:59:14 BGP: 100.118.126.78 went from Connect to Active
2018/12/14 10:01:14 BGP: 100.118.126.78 [FSM] Timer (connect timer expire)
2018/12/14 10:01:14 BGP: 100.118.126.78 [FSM] ConnectRetry_timer_expired (Active->Connect), fd -1
2018/12/14 10:01:14 BGP: 100.118.126.78 [FSM] Waiting for NHT
2018/12/14 10:01:14 BGP: 100.118.126.78 went from Active to Connect
2018/12/14 10:01:14 BGP: 100.118.126.78 [FSM] TCP_connection_open_failed (Connect->Active), fd -1
2018/12/14 10:01:14 BGP: 100.118.126.78 went from Connect to Active
[show ip bgp neighbors]
frr-route# show ip bgp neighbors
BGP neighbor is 100.118.126.78, remote AS 300, local AS 300, internal link
BGP version 4, remote router ID 0.0.0.0, local router ID 100.118.127.248
BGP state = Active
Last read 00:11:16, Last write never
Hold time is 180, keepalive interval is 60 seconds
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 100.118.127.248
For address family: IPv4 Unicast
Not part of any update group
Community attribute sent to this neighbor(all)
0 accepted prefixes
Connections established 0; dropped 0
Last reset never
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 45 seconds
Read thread: off Write thread: off
[iptables info ]
[-bash-4.2# iptables -nL
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
-bash-4.2# ]
ใFRR config ใ
frr-route(config)# do show running-config
Building configuration...
Current configuration:
!
frr version 6.0
frr defaults traditional
hostname Router
log file router
no ipv6 forwarding
hostname KVM-2
hostname frr-route
username root nopassword
!
debug bgp keepalives
debug bgp neighbor-events
debug bgp update-groups
debug bgp updates in
debug bgp updates out
debug bgp zebra
!
password alinux123
enable password alinux123
!
router bgp 300
bgp router-id 100.118.127.248
neighbor 100.118.126.78 remote-as 300
neighbor 100.118.126.78 update-source 100.118.127.248
!
address-family ipv4 unicast
network 1.1.1.0/24
redistribute connected metric 1000
exit-address-family
!
line vty
!
centos7-K8s-M-etcd1# show running-config
Building configuration...
Current configuration:
!
frr version 6.0
frr defaults traditional
hostname Router
no ipv6 forwarding
hostname centos7-K8s-M-etcd1
log file router
!
debug bgp keepalives
debug bgp neighbor-events
debug bgp update-groups
debug bgp updates in
debug bgp updates out
debug bgp zebra
!
password zebra
enable password zebra
!
router bgp 300
bgp router-id 100.118.126.78
neighbor 100.118.127.248 remote-as 300
neighbor 100.118.127.248 update-source 100.118.126.78
!
line vty
!
bfd
!
end
🎉1
I added a routing manually and the BGP peer was normal.
1:ใno add static route show ip bgp nexthop ใ
[show ip bgp nexthop ]
frr-route# show ip bgp nexthop
Current BGP nexthop cache:
100.118.126.78 invalid
Last update: Fri Dec 14 09:53:14 2018
2:ใadd static route show ip bgp nexthop ใ
ip route 100.118.126.78/32 100.118.127.1
frr-route# show ip bgp nexthop
Current BGP nexthop cache:
100.118.126.78 valid [IGP metric 0], #paths 0
3:[BGPD runing OK ]
frr-route# show bgp summary
IPv4 Unicast Summary:
BGP router identifier 100.118.127.248, local AS number 300 vrf-id 0
BGP table version 2
RIB entries 3, using 480 bytes of memory
Peers 1, using 21 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
100.118.126.78 4 300 10 12 0 0 0 00:07:07 0
Total number of neighbors 1
frr-route# show ip bgp neighbors
BGP neighbor is 100.118.126.78, remote AS 300, local AS 300, internal link
Hostname: centos7-K8s-M-etcd1
BGP version 4, remote router ID 100.118.126.78, local router ID 100.118.127.248
BGP state = <h2>Established</h2>, up for 00:08:05
Last read 00:00:05, Last write 00:00:05
Hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
4 Byte AS: advertised and received
[route info]
frr-route# 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, D - SHARP,
F - PBR,
> - selected route, * - FIB route
K>* 0.0.0.0/0 [0/0] via 100.118.127.1, br0, 02:07:09
S>* 100.118.126.78/32 [1/0] via 100.118.127.1, br0, 00:09:42
C>* 100.118.127.0/24 is directly connected, br0, 02:07:09
K * 169.254.0.0/16 [0/1012] is directly connected, br0, 02:07:09
K>* 169.254.0.0/16 [0/1002] is directly connected, enp4s0, 02:07:09
@zhangyigui Again, please use Github Flavored Markdown when posting logs and configs. Specifically please wrap that text in three backticks (` x 3).
I have had to reformat every post you have made thus far in order to read it. With the amount of information here please help us help you and use the proper formatting.
qlyoung
on 17 Dec 2018
TKS๏ผ
zhangyigui
on 18 Dec 2018
If you want to resolve the nexthop using the default route instead of adding a static route, you can try configuring this knob:
ip nht resolve-via-default
This should allow the capability
dslicenc
on 18 Dec 2018
👍1
ip nht resolve-via-default needs to be documented
qlyoung
on 19 Dec 2018
Was this page helpful?
0 / 5 - 0 ratings
Related issues
Chen0Yang
ยท
3Comments
464d41
ยท
8Comments
Try75
ยท
8Comments
mshuttle76
ยท
6Comments
SandroRaV
ยท
5Comments