OSPF Interface#

Virtual Networks → OIOSPF Interfaces

Open Shortest Path First, or OSPF, is a routing protocol to exchange IP routes. There are two versions of the OSPF protocol:

• Version 2 is configured on IPv4 interfaces and only exchances IPv4 prefixes
• Version 3 is configured on IPv6 interfaces and exchanges both IPv4 and IPv6 prefixes

OSPF sessions are always established between OSPFInterfaces in an OSPFArea, and never operate inter-area. To connect two OSPF areas to each other, an area border router (ABR) configures both areas in the same OSPFInstance. An OSPFInstance is an isolated process with its own Link State Database (LSDB).

OSPF interfaces can be configured as "passive", meaning they won't actively try to establish OSPF adjacencies, nor will they respond to incoming OSPF packets. Passive OSPF interfaces are configured to advertise prefixes reachable through this interface, without participating in the OSPF topology.

To set up an OSPF interface in the default VRF, use DefaultOSPFInterface instead.

Dependencies#

To configure this resource, the following resources must exist or be created alongside the OSPFInterface

• The RoutedInterface that the OSPF session will be established on
• The OSPFArea this interface is configured in
• The OSPFInstance this interface is configured in

Referenced resources#

RoutedInterface#

OSPF adjacencies are formed between IP addresses, and therefore require a reference to the RoutedInterface that will establish the adjacency. If the OSPFInterface is configured as "passive", no adjacency will be attempted or accepted. This is useful when the prefixes reachable through this interface should be advertised to the OSPF area (for example loopback IP addresses, static routes, ...), without actively taking part in the topology.

OSPFInstance#

An OSPF instance is an isolated process that establishes OSPF adjacencies and keeps track of all prefixes that are reachable in the OSPF areas that are part of this instance. For example, if dual-stack OSPFv2 and OSPFv3 topologies are configured, each protocol version runs in its own OSPF instance, with separate Link-State Databases (LSDB).

If the same OSPFInterface is linked to two different OSPFInstances, two OSPFInterface resources need to be created, each referencing a different OSPFInstance.

OSPFArea#

Prefixes can be exchanged between OSPF areas by interconnecting them on an Area Border Router (ABR) which configures both OSPFAreas in the same OSPFInstance. One interface is always part of one OSPFArea.

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: OSPFInterface
metadata:
  name: ospf-interface-leaf1
  namespace: eda
spec:
  interface: ospf-leaf1-spine1-intf
  interfaceKind: RoutedInterface
  ospfArea: ospf-area-0
  ospfInstance: ospf-instance-v3
  type: PointToPoint

cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: OSPFInterface
metadata:
  name: ospf-interface-leaf1
  namespace: eda
spec:
  interface: ospf-leaf1-spine1-intf
  interfaceKind: RoutedInterface
  ospfArea: ospf-area-0
  ospfInstance: ospf-instance-v3
  type: PointToPoint
EOF

Custom Resource Definition#

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