You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/concepts-nexus-networking.md
+18-15Lines changed: 18 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -387,27 +387,30 @@ Additional network interfaces inside a Pod will use the Pod's route table to
387
387
route traffic to additional L3 Networks that use the `SRIOV` and `DPDK` plugin
388
388
types.
389
389
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.
0 commit comments