Skip to content

Commit 7620b31

Browse files
Merge pull request #297476 from rcheeran/2025-04-01
Update BFD and BGP details
2 parents cb827db + f60319f commit 7620b31

File tree

1 file changed

+18
-15
lines changed

1 file changed

+18
-15
lines changed

articles/operator-nexus/concepts-nexus-networking.md

Lines changed: 18 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -387,27 +387,30 @@ Additional network interfaces inside a Pod will use the Pod's route table to
387387
route traffic to additional L3 Networks that use the `SRIOV` and `DPDK` plugin
388388
types.
389389

390+
391+
### CNI BFD and BGP configuration
392+
393+
## Default BFD Configuration
394+
395+
Bidirectional Forwarding Detection (BFD) parameters can be configured for each BGP peering. BFD timers are negotiated between the Operator Nexus Kubernetes clusters and the peer router. The higher timer value between the two routers is selected, which is the standard BFD behavior. The Nexus Kubernetes clusters uses the following values
396+
- **Interval**: 300ms
397+
- **Multiplier**: 3
398+
If BFD is not enabled on the peer router, a session will not be established.
399+
400+
## Default BGP Configurations
401+
402+
[Border Gateway Protocol][bgp](BGP) timers are negotiated between Operator Nexus Kubernetes clusters and the peer router. The lowest hold timer value between the two routers is selected which is the standard BGP behavior. The Nexus Kubernetes clusters uses the following values
403+
- **hold-time**: 240s hold time
404+
- **keep-alive interval**: 1/3 of hold time (80s)
405+
If a BFD session also exists, BGP will leverage BFD for detecting failed peers.
406+
390407
[linux-ns]: https://en.wikipedia.org/wiki/Linux_namespaces
391408
[podnetwork]: https://kubernetes.io/docs/concepts/cluster-administration/networking/
392409
[cni]: https://www.cni.dev/
393410
[veth]: https://www.man7.org/linux/man-pages/man4/veth.4.html
394411
[switchdev]: https://www.kernel.org/doc/html/latest/networking/switchdev.html
395412
[specify-net-anno]: https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/docs/how-to-use.md#run-pod-with-network-annotation
396413
[nad]: https://github.com/k8snetworkplumbingwg/multi-net-spec/blob/master/v1.3/%5Bv1.3%5D%20Kubernetes%20Network%20Custom%20Resource%20Definition%20De-facto%20Standard.pdf
397-
398-
<!---
399-
### Service network configuration
400-
401-
TODO(jaypipes)
402-
403-
## Default Routing and BGP Configuration
404-
405-
CNFs are typically a collection of Kubernetes Pods that are connected to one or
406-
more virtual networks. Those virtual networks are routed across the physical
407-
network infrastructure via [Border Gateway Protocol][bgp] (BGP).
408-
409-
TODO(jaypipes)
410-
411414
[bgp]: https://en.wikipedia.org/wiki/Border_Gateway_Protocol
412415

413-
-->
416+

0 commit comments

Comments
 (0)