Distinguish Virtual WAN router recovery from a gateway reset

Source facts

Microsoft documents a case where a Virtual WAN hub router is failed and route updates are unavailable even though connectivity may continue. It directs operators to Reset router when hub status is succeeded but routing status is failed. The separate hub-reset operation can address failed hub resources, but does not reset the hub’s gateways. Microsoft Learn.

Applicability

Use this review when a hub cannot accept routing changes or reports inconsistent resource states. Identify the hub, routing and gateway states separately, together with actual traffic observations. Do not infer that a failed control operation means all traffic has stopped.

DSE recommendation

DSE recommends capturing the state and error details before selecting a recovery action. Have the network owner match the documented reset scope to the failed component and approve the operation with monitoring in place. Preserve the expected routes and application checks, and define when to seek further support instead of repeating unrelated resets.

Verification

After an authorized recovery, inspect the relevant provisioning and routing states and verify that the intended route operation succeeds. Test critical application paths and check gateway states separately. Retain before-and-after observations and any interruption. Do not promise a disruption-free reset or interpret a successful hub operation as proof that every gateway was reset or repaired.

Official references

Microsoft Learn: About virtual hub routing.