Floating Static Routes are preferred to OSPF Dynamic Routes
Article ID: 328608
Updated On: 11-13-2024
Products
VMware NSX
Issue/Introduction
A backup Floating Static Route is incorrectly entered into an Edges routing table when Route Redistribution is enabled even though an OSPF Route is available.
Cause
Static routes by default have an Administrative Distance of 1. NSX 6.2.x added the functionality to configure Administrative Distance for static routes.
A floating static route is a backup route which has an Administrative Distance greater than the Administrative Distance of the primary route.
These floating routes is only selected for the routing table when the primary route is unavailable. It is found that when route redistribution is enabled for static routes on an Edge, backup floating static routes are incorrectly preferred to OSPF dynamic routes. The floating routes enters the routing table.
A floating static route is a backup route which has an Administrative Distance greater than the Administrative Distance of the primary route.
These floating routes is only selected for the routing table when the primary route is unavailable. It is found that when route redistribution is enabled for static routes on an Edge, backup floating static routes are incorrectly preferred to OSPF dynamic routes. The floating routes enters the routing table.
Resolution
This issue is resolved in VMware NSX for vSphere 6.3.0.
Workaround:
Disable the route redistribution of Static into OSPF.
Note: This issue does not impact the data path.
Feedback
Was this article helpful?
Yes
No
Powered by
