Troubleshooting OpenStack Neutron with ML2/OVN backend driver
summary
OVN replaces ML2/OVS by handling L3, DHCP and DVR natively and requires different debugging steps: use ovn-nbctl and ovn-sbctl to map Neutron IDs to OVN logical switches/routers and to inspect port, NAT and port-group objects; fix a non‑distributed floating IP by writing external_mac and logical_port into the NAT row; remove a poisoned mac_binding row to restore AR learning; repair missing dhcpv4_options on a logical_switch_port or run neutron-ovn-db-sync to repopulate OVN DB; these fixes restore traffic in the demo.
AI-written summary · about
chapters (6)
- 0:00OVN and Neutron concepts
- 29:29Troubleshooting DVR issues
- 44:02Resolving ARP cache poisoning
- 52:47Fixing external connectivity
- 59:44Debugging DHCP failures
- 1:10:37Agent connectivity issues
related talks
36mMigrating the Neutron backend to OVN in production
21mHassle-free migration from OVS to OVN
28mPerformance optimization of Neutron server and Agent for large-scale scenario
58mTelco; Networking; Architecture; How to debug; Tips and Tricks
19mAdvanced Network management with oVirt and OVN
18mSmartNIC DPU Enablement in OpenStack with OVN
30mHow we integrated L3 services into one of the biggest OpenStack Public Clouds - OVHcloud case study
36mOVN-Kubernetes The new default CNI of OpenShift