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.
π‘ Quick Answer: Find OVN encapsulation IP with
ovs-vsctl get Open_vSwitch . external_ids:ovn-encap-ip, map it to an interface usingip addr, then inspectbr-exports 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-ip2) Map Encapsulation IP to Interface
ip addr | grep -B2 <encap-ip>3) Check External Bridge Ports
ovs-vsctl list-ports br-ex4) Validate Routes
ip routeCorrelate default route and subnet routes with the bridge and lower devices.
Interpretation Pattern
ovn-encap-iponbr-exmeans overlay tunnel egress is tied tobr-ex.br-exlower 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.

Recommended
Kubernetes Recipes β The Complete Book100+ production-ready patterns with detailed explanations, best practices, and copy-paste YAML. Everything in one place.
Get the Book βLearn by Doing
CopyPasteLearn β Hands-on Cloud & DevOps CoursesMaster Kubernetes, Ansible, Terraform, and MLOps with interactive, copy-paste-run lessons. Start free.
Browse Courses βπ Deepen Your Skills β Hands-on Courses
Courses by CopyPasteLearn.com β Learn IT by Doing
