Default OSPF Interface#

Underlay Routing → DODefault OSPF 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 in the deafult VRF are always established between DefaultOSPFInterfaces in a DefaultOSPFArea, and never operate inter-area. To connect two OSPF areas to each other, an area border router (ABR) configures both areas in the same DefaultOSPFInstance. A DefaultOSPFInstance 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 overlay, use OSPFInterface instead.

Dependencies#

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

• An interface, options are:
  • The DefaultInterface that the OSPF session will be established on
  • The SystemInterface that passively participates in the OSPF area
• The DefaultOSPFArea this interface is configured in
• The DefaultOSPFInstance this interface is configured in

Referenced resources#

DefaultInterface#

OSPF adjacencies are formed between IP addresses, and therefore require a reference to the DefaultInterface that will establish the adjacency. If the DefaultOSPFInterface 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 static routes), without actively taking part in the topology.

SystemInterface#

In a typical Fabric, overlay routes are exchanged via BGP between the SystemInterfaces on each node. To advertise the IP address of the SystemInterface to the other nodes, it must participate in the OSPF area without actively trying to establish an OSPF session. In this scenario, a DefaultOSPFInterface referencing the SystemInterface is required and must be configured as a passive OSPF interface.

DefaultOSPFInstance#

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 DefaultOSPFInterface is linked to two different DefaultOSPFInstances, two DefaultOSPFInterface resources need to be created, each referencing a different DefaultOSPFInstance.

DefaultOSPFArea#

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

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: DefaultOSPFInterface
metadata:
  name: isl-leaf-1-ethernet-1-1-ipv4
  namespace: eda
spec:
  defaultOSPFArea: fabric-ospfv3-ipv4-0.0.0.0
  defaultOSPFInstance: fabric-ospfv3-ipv4
  interface: interface-leaf-1-ethernet-1-1-vlan-1
  interfaceKind: DefaultInterface
  type: PointToPoint

cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: DefaultOSPFInterface
metadata:
  name: isl-leaf-1-ethernet-1-1-ipv4
  namespace: eda
spec:
  defaultOSPFArea: fabric-ospfv3-ipv4-0.0.0.0
  defaultOSPFInstance: fabric-ospfv3-ipv4
  interface: interface-leaf-1-ethernet-1-1-vlan-1
  interfaceKind: DefaultInterface
  type: PointToPoint
EOF

Custom Resource Definition#

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