Routes installed on SD-WAN Edge do not follow correct Hub order
Article ID: 333935
Updated On:
Products
Issue/Introduction
Traffic in a SD-WAN Route expected to follow HUB order in a spoke device is not routing to the expected HUB, and instead following the order configured in Overlay Flow Control (OFC)
Environment
VMware SD-WAN by VeloCloud
Cause
Scenario-1
From a SD-WAN Edge Spoke perspective, when DCC is enabled and a route is learnt from multiple HUBs with same preferences/ metrics, then the best route path will be selected based on the HUB order.
However, if one of said subnets is modified on the OFC, the route will be automatically pinned, and the best exit point will be based on OFC and not HUB order.
Scenario-2
If the spoke edge learns the same route from two hubs—one via OSPF from HUB1 and the other via BGP from HUB2—the spoke edge will choose the route based on its preference, not the order of the hubs.
Resolution
By default, the spoke edge will select the best route based on the preferences. The HUB order will take effect only if the preferences/ metrics are same.
If the user wants to override the default behavior, then they can modify the route order from the OFC page. To navigate click on configure >> Overlay flow control >> Route list >> filter the route >> change the order as per the requirement. To revert, click on reset and save the changes.
Feedback
