πŸ“šBook Signing at KubeCon EU 2026Meet us at Booking.com HQ (Mon 18:30-21:00) & vCluster booth #521 (Tue 24 Mar, 12:30-1:30pm) β€” free book giveaway!RSVP Booking.com Event
Networking intermediate ⏱ 15 minutes K8s 1.28+

Verify Which Interface Carries OVN Underlay Traffic

Confirm the actual OVN underlay network path by checking ovn-encap-ip, bridge port ownership, and physical route associations on Kubernetes nodes.

By Luca Berton β€’ β€’ πŸ“– 5 min read

πŸ’‘ Quick Answer: Find OVN encapsulation IP with ovs-vsctl get Open_vSwitch . external_ids:ovn-encap-ip, map it to an interface using ip addr, then inspect br-ex ports to identify the real underlay device.

When troubleshooting SR-IOV and node networking, confirm the interface actually used for OVN underlay instead of guessing by NIC names.

1) Get OVN Encapsulation IP

ovs-vsctl get Open_vSwitch . external_ids:ovn-encap-ip

2) Map Encapsulation IP to Interface

ip addr | grep -B2 <encap-ip>

3) Check External Bridge Ports

ovs-vsctl list-ports br-ex

4) Validate Routes

ip route

Correlate default route and subnet routes with the bridge and lower devices.

Interpretation Pattern

  • ovn-encap-ip on br-ex means overlay tunnel egress is tied to br-ex.
  • br-ex lower port (for example VLAN/bond sub-interface) identifies the practical underlay path.
  • Use this mapping before concluding whether a specific PF participates in host network paths.
#ovn #underlay #openshift #networking #debugging
Luca Berton
Written by Luca Berton

Principal Solutions Architect specializing in Kubernetes, AI/GPU infrastructure, and cloud-native platforms. Author of Kubernetes Recipes and creator of CopyPasteLearn courses.

Kubernetes Recipes book cover

Want More Kubernetes Recipes?

This recipe is from Kubernetes Recipes, our 750-page practical guide with hundreds of production-ready patterns.

Luca Berton Ansible Pilot Ansible by Example Open Empower K8s Recipes Terraform Pilot CopyPasteLearn ProteinLens