Troubleshooting On-prem DR VCO heartbeat issue
search cancel

Troubleshooting On-prem DR VCO heartbeat issue

book

Article ID: 379374

calendar_today

Updated On:

Products

VMware VeloCloud SD-WAN

Issue/Introduction

Scenarios where Edges are not heart beating to the standby VCO

Environment

All SDWAN Software versions 

Cause

Below are the possible causes where edges cannot heartbeat to the DR VCO.

- Management updates are not pushed properly from the Active VCO.
- Routing issue for DR VCO IP address.
- Firewall blocking DR VCO IP address

Resolution

- Management updates are not pushed properly from the Active VCO - We can make some temporary changes which are non-intrusive on the VCO system properties (example: VCO heartbeat seconds) and revert them will push the management updates to all the edges in the Enterprise

- Routing issue for DR VCO IP address: Check the flows on the edge, it could be possible that the traffic for DR VCO is exiting via LAN because peer BGP is advertising more specific routes. We can create a deny filter towards that BGP neighbor on the VCO to resolve this issue.

- Firewall blocking DR VCO IP address: Allow the DR VCO IP in the firewall