CSS GRE tunnels created by API initiated on 1 WAN link only

Products

• VMWare SD-WAN
• VMware VeloCloud SD-WAN

Issue/Introduction

When CSS GRE tunnels are created via API call, and configuration is pushed to an edge with multiple WAN links, we may find tunnels created on only WAN link and not the others and edge is not trying to initiate CSS tunnels on the WAN link.

- WAN links need to be specified for GRE tunnels to be initiated. In automated CSS GRE tunnels, VCO sends the WAN links information to API according to their status at the time of API call.

- If WAN link was down at the time of API call, the WAN link details will not be updated in the CSS configuration, and we won't be able to add the WAN link on edge or profile level.

 

Environment

All environments

Cause

- If WAN link was down at the time of API call, the WAN link details will not be updated in the CSS configuration, and we won't be able to add the WAN link on edge or profile level.

- Check deployment date/time of the edge from Monitor >> Network services > Deployment status > view

- Filter with edge name and select all output fields

- Check the WAN link status at the time of deployment, if it was down, then edge will not try to initiate CSS tunnels on this WAN interface

Resolution

- Customer needs to re-initiate the API call while all WAN links are up.

- Customer needs to delete CSS configuration from Configure >> Network services >> NSD via edge >> CSS >> delete configuration and re-configure it

- This will impact all edges that have this CSS assigned

- afterwards, edge should get the correct configuration