The Overlay Flow Control page displays a summarized view of all the routes in your network.

For the 4.3 release, a new NSD bucket has been introduced for the classification of NSD Routes. The new NSD bucket preference logic will be applicable only when the Use NSD policy is enabled along with the Distributed Cost Calculation. The Use NSD policy can only be enabled after you enable the Distributed Cost Calculation.

You can view and edit the global routing preferences and the advertise actions for the Edges, Hubs, Partner Gateways, and Non SD-WAN Destinations via Edge and Gateway.

In the Enterprise portal, click Configure > Overlay Flow Control.

The Overlay Flow Control page displays the following details:

Option Description
Preferred VPN Exits Displays the priority of the destinations to where the traffic should be routed.
Global Advertise Flags Displays the advertise actions of static, connected, internal, external, and uplink routes.
  • Edit – Click to update the priorities and the advertise actions. See Configure Global Routing Preferences.
  • Refresh Routes – This option is available only when the Distributed Cost Calculation feature is enabled by the Operator. By default, the Orchestrator is actively involved in learning the dynamic routes. Edges and Gateways rely on the Orchestrator to calculate initial route preferences and return them to the Edge and Gateway. The Distributed Cost Calculation feature enables to distribute the route cost calculation to the Edges and Gateways.

    For more information on Distributed Cost Calculation, refer to the Configure Distributed Cost Calculation section in the VMware SD-WAN Operator Guide available at:

    Note: To enable the Distributed Cost Calculation feature, check with your supporting partner. If you are directly supported by VMware, contact the support team.

    Click Refresh Routes which makes the Edges and Gateways to recalculate learned route costs and send them to the Orchestrator. In addition, the changes in the Overlay Flow Control are applied immediately on the new and existing learned routes.

    When you refresh the routes, the Customer Enterprise has the following impact on the network:

    • All the local dynamic routes are refreshed, and the preference and advertise action of these routes are updated. This updated information is advertised to the Gateway, Orchestrator, and eventually across the Enterprise. As this leads to an update in the routing table, there is a brief impact on the traffic for all the sites.
    • Any existing flow using these routes can potentially be affected due to the change in the routing entries.
    Note: It is recommended to use Refresh Routes in a maintenance window to minimize the impact on the Customer Enterprise.

The bottom panel of the Overlay Flow Control window displays the subnets. You can prioritize the preferred destinations for the subnets and pin or unpin learned route preferences. For more information, see Configure Subnets.

You can configure global routing preferences and subnets for both IPv4 and IPv6 addresses using the new Orchestrator UI. For more information, see Overlay Flow Control.