Skip to content

Routed Interface#

Virtual Networks → RIRouted Interfaces

A RoutedInterface associates an Interface with a Router, usually with an IP address that is used as the source IP of originated traffic.

It is very similar to the IRBInterface, which connects a Router to a BridgeDomain. The RoutedInterface does not have to be associated with a physical interface: it can also be used with loopback1 interfaces.

The most common use cases of routed interfaces are:

  • Setting up a BGP connection to a locally connected device (a firewall, a datacenter gateway)
  • Establishing an OSPF neighborship between a host and the virtualized Router
  • Providing a next-hop for static routes toward an internet gateway router

Dependencies#

Interface#

A RoutedInterface is always associated with a particular Interface. This interface can be virtual (a loopback1), or linked to a (set of) physical port(s).

The same physical interface can be connected to multiple virtualized Router services. A VLAN tag is used to determine which service will be used to process the packet.

Router#

The RoutedInterface enables reachability towards a particular subnet. This route may be a host route (/32) for a loopback1 interface, a point-to-point route (/31 or /30), or a bigger subnet route.

This route is installed in the routing table of the Router that the RoutedInterface is connected to. If the Interface should be connected to the default VRF, check out the DefaultInterface instead.

Referenced resources#

IndexAllocationPool#

If the RoutedInterface is connected to a physical interface, a VLAN tag should be specified to determine which packets will be processed by the Router associated with this RoutedInterface.

The VLAN tag can be manually specified (including special values null and any), or can automatically be drawn from an index allocation pool.

Filter#

Traffic that is received by or sent from the RoutedInterface can optionally be filtered by specifying one or more Filter resources in the ingress (respectively egress) container.

IngressPolicy#

Traffic that is received by the RoutedInterface can optionally be processed by one or more QoS IngressPolicies by specifying them in the ingress container.

EgressPolicy#

Traffic that is sent by the RoutedInterface can optionally be processed by one or more QoS EgressPolicies by specifying them in the egress container.

Examples#

apiVersion: services.eda.nokia.com/v2
kind: RoutedInterface
metadata:
  name: internet-gateway
  namespace: scale-across
spec:
  interface: dc1-leaf-1-ethernet-1-8
  ipMTU: 1500
  router: compute-vrf
  vlanID: '909'
  vlanPool: vlan-pool

cat << 'EOF' | kubectl apply -f -
apiVersion: services.eda.nokia.com/v2
kind: RoutedInterface
metadata:
  name: internet-gateway
  namespace: scale-across
spec:
  interface: dc1-leaf-1-ethernet-1-8
  ipMTU: 1500
  router: compute-vrf
  vlanID: '909'
  vlanPool: vlan-pool

EOF

Custom Resource Definition#

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

RoutedInterface

services.eda.nokia.com / v2

SPEC

The RoutedInterface enables the configuration and management of Layer 3 interfaces for routing traffic between different networks. This resource allows for specifying an underlying Interface and Router, configuring VLAN IDs, and setting the IP MTU. It also supports the learning of unsolicited ARPs, defining both IPv4 and IPv6 addresses, and enabling unnumbered interfaces. Advanced features such as BFD configuration, Proxy ARP/ND, and ARP timeout settings are included to ensure robust and efficient routing.

  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #

STATUS

RoutedInterfaceStatus defines the observed state of RoutedInterface

  • #
  • #
  • #
  • #
  • #

  1. Loopback interfaces are logical interfaces used to enable a switch to send or receive traffic. The system interface is an example of a loopback interface. ↩↩↩