VMs on a remote L2VPN segment can not ping their DGW but can ping other hosts on the far end of the tunnel
search cancel

VMs on a remote L2VPN segment can not ping their DGW but can ping other hosts on the far end of the tunnel

book

Article ID: 377472

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

An L2VPN service has been created between two NSX environments within two separate software-defined data centers.  While the VM's on the Client side of the tunnel will likely be able to communicate with VM's on the Server side, connectivity to the DGW on the server side may be down or intermittent.  This particular problem may be the result of the L2VPN Client NSX version being later than the Server version. 

While the Client and Server NSX versions may be different in certain scenarios, in all cases, the NSX L2VPN Server must be either the same version as the Client or the higher version.  Please see the below document to understand which Server versions are compatible with which Client versions:



Understanding Layer 2 VPN (vmware.com)

Environment

NSX

Cause

Even though certain version differences between NSX L2VPN client and server are permitted, in no case is it supported for the Client side to be at the newer version.

Resolution

Recreate the tunnel with the newer version of NSX as the server