Check Default Bgp Peers#

Workflows → CDCheck Default Bgp Peers

The CheckDefaultBGPPeers workflow can be used to query the status of all BGP sessions in the default VRF, across a selection of nodes. More specifically, for a list of nodes, it loops over all DefaultBGPPeers configured on those nodes and looks up whether the session is established on the relevant node.

Workflow definition#

The selection of the nodes can be done in one of two ways:

1. via the node selector, by selecting individual nodes
2. via the label selector, which selects all nodes that have the label assigned to them

If both the node selector and the label selector are left empty, no nodes will be selected.

Workflow execution#

The result of the workflow, upon completion, is the number of BGP sessions that were operational compared to the number of BGP sessions that have an associated DefaultBGPPeer resource. For example:

...
status:
  result: default BGP peer check successful, 8/8 up
...

Dependencies#

This workflow has no dependencies. If no nodes were selected by the node selector or no nodes matched the label selector, the workflow will complete successfully.

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: CheckDefaultBgpPeers
metadata:
  name: checkdefaultbgppeers-workflow
  namespace: eda
spec:
  nodeSelectors:
    - eda.nokia.com/role = leaf

cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: CheckDefaultBgpPeers
metadata:
  name: checkdefaultbgppeers-workflow
  namespace: eda
spec:
  nodeSelectors:
    - eda.nokia.com/role = leaf

EOF

Custom Resource Definition#

To browse the Custom Resource Definition go to crd.eda.dev.