Error: "IPSec VPN Tunnel with id ########-####-####-####-############ not found on Gateway <edge name>." when updating IPSec tunnel on an edge.

Products

• VMware Cloud Director

Issue/Introduction

• Updating one of the IPSec VPN tunnels on a tenant edge from the VMware Cloud Director(VCD) provider portal fails with the error: 
  
  [########-####-####-####-############] IPSec VPN Tunnel with id ########-####-####-####-############ not found on Gateway <edge name>.
  
  
• The tunnel can be seen present on the edge as expected.
• The edge has more than 128 IPSec VPN tunnels on it. 
• Tunnels created initially can be edited successfully. 
• Tunnels from 129th position onwards fails to update.

Environment

VMware Cloud Director 10.6.x

Cause

The issue happens only during the UPDATE of ipsec tunnel with index > 128. This happens when VMware Cloud Director(VCD) fetches all IPSec VPN Sessions for an edge gateway from the NSXT before creating the information on the VCD side. While doing so, the pageSize parameter to be sent to the NSXT's API of fetching the IPSec VPN Sessions is not included. This in turn causes few of the entries to be ignored and VCD then complains of the missing IPSec Tunnel.

Resolution

The issue will be resolved in a future release of VMware Cloud Director. Subscribe to this knowledge article to get updates on this issue Subscribe to a Broadcom knowledge article by article or product 

To workaround the issue:

1. Update the IPSec VPN tunnel directly in NSXT 
2. Delete and recreate the tunnel with the updated information.
3. Rename one of the tunnels in the initial pages to move it to last and then edit the tunnel required.

Additional Information

Adding VPN Services

IPsec VPN for NSX Edge Gateways in the VMware Cloud Director Service Provider Admin Portal