search

open-switch / opx-nas-l3

https://openswitch.net
1 stars 9 forks source link

FRR BGP or OSPF BFD not operational #28

Closed geraldmyres closed 6 years ago

geraldmyres commented 6 years ago

Installed OPX 3.0.0 and FRR 5.01. Configured eBGP leaf-spine with BFD enabled. BGP BFD is configurable, but is not operational. No BFD messages seen from either leaf or spine.

See attached configs and topology

bgp Leaf1 BGP.txt Spine1 BGP.txt

jeff-yin commented 6 years ago

This might be due to a limitation of OPX (say, a missing NETLINK handler), so will label this as an enhancement request for now. @atanu-mandal to triage -- if it turns out to be a bug we'll relabel as bug.

atanu-mandal commented 6 years ago

Hi @geraldmyres , BFD support seems to have started only from FRRouting 6.0. In 5.0.1 there was no option to enable "bfdd" in /etc/frr/daemons.

I have tried OPX 3.0.0 VM s running with FRRouting 6.0. The BFD is functional as seen in the logs captured below. I will do more verification including the hardware platforms and update accordingly.

OPX# show version FRRouting 6.0 (OPX). Copyright 1996-2005 Kunihiro Ishiguro, et al.

OPX# show bfd peers BFD Peers: peer 10.1.1.1 label: spine1-leaf1 ID: 1 Remote ID: 1 Status: up Uptime: 21 minute(s), 23 second(s) Diagnostics: ok Remote diagnostics: ok Local timers: Receive interval: 300ms Transmission interval: 300ms Echo transmission interval: disabled Remote timers: Receive interval: 300ms Transmission interval: 300ms Echo transmission interval: 50ms

root@OPX:/etc/frr# tcpdump -i e101-003-0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on e101-003-0, link-type EN10MB (Ethernet), capture size 262144 bytes 22:37:33.769211 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:33.897726 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.027228 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.167738 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.318247 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.401755 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.615264 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.686771 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.864281 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:34.917787 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:35.110299 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:35.175802 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:35.404316 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:35.436808 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:35.665335 IP 10.1.1.2.49142 > 10.1.1.1.3784: BFDv1, Control, State Up, Flags: [none], length: 24 22:37:35.697831 IP 10.1.1.1.49142 > 10.1.1.2.3784: BFDv1, Control, State Up, Flags: [none], length: 24

Thanks, -Atanu