After an SD-WAN edge is elected as OSPF DR and the router-ID is changed, OSPF routes are missing.

Products

• VMware SD-WAN by VeloCloud
• VMware VeloCloud SD-WAN

Issue/Introduction

Symptoms:
When a VMware SD-WAN Edge is using OSPF and is elected as the Designated Router and the router-id is changed, the OSPF routing table may be empty, causing a service outage.

Environment

VMware SD-WAN Edge software version less than 4.5.2

Cause

The issue is being tracked under ID #83209.
The issue occurs when there is a change in the OSPF router-id and the Edge service is restarted. Only loopback interfaces and Interfaces with 'Advertise' flag enabled are considered for router-id selection. When there is a new loopback interface configured with a higher IP address, upon restarting the Edge service, the new loopback IP address is selected as the router-id and if the Edge is elected as the DR (Designated Router) and the issue is seen.

Resolution

This issue is resolved in SD-WAN Edge 4.3.1 patch R431-20220509-GA.
Fix is also available in:

• 4.5.2
• 5.0.1.0
• 5.0.0.2.

For information on how to upgrade please check the following article: VMware SD-WAN Software Upgrade FAQs

Workaround:
To work around this issue if you do not want to upgrade:

The workaround is to use the old Router ID, by enabling the Advertise option on the respective interface (an Edge service restart will occur upon saving).
This will advertise the connected network on that interface to the overlay, and allow use of that interface IP as the OSPF router ID.
Do not enable the Advertise option on a link used for WAN overlay as this may cause unexpected routing behavior.

Additional Information

Impact/Risks:
The workaround will trigger a service restart, causing a brief service interruption.