VMware Networking Community
m-nara
Enthusiast
Enthusiast

L2VPN with standalone edge (NSX-V 6.1)

Hi,

I'm trying to connect VXLAN and VLAN by L2VPN with a standalone edge like following table.

Site-A (vCenter with NSX)L2VPN tunnelSite-B (vCenter only)
[NSX Edge][Standalone Edge]
VNI 2005Tunnel 2001VLAN 2001
VNI 2007Tunnel 2002VLAN 2002
VNI 2004Tunnel 2003VLAN 2003
VNI 2001Tunnel 2004VLAN 2004
VNI 2002Tunnel 2005VLAN 2005

The tunnel status between edges is up, but VMs cannot communicate across the tunnel.

Why the standalone edge does not have conversion-table ?

On the Site-A, the NSX edge is connected to vlan trunk portgroup which allows "1-4094" and configured as a L2VPN server.

The vlan trunk portgroup has 5 sub interfaces which are logical switches (vxlan) and configured as a L2VPN server.


On the Site-B,  the standalone edge is connected to vlan trunk portgroup which allows "2001-2005".

The [Sub Interface VLAN (Tunnel ID)] is configured like "2001(2001),2002(2002),2003(2003),2004(2004),2005(2005)"..

NSX Edge
L2VPN-Server-0> show service l2vpn conversion-table
TunnelId     VLAN/VNI     Type
--------------------------------------
2001          5005               VXLAN
2002          5007               VXLAN
2003          5004               VXLAN
2004          5001               VXLAN
2005          5002               VXLAN

Standalone Edge
nsx-l2vpn-edge> show service l2vpn conversion-table
TunnelId     VLAN/VNI     Type
--------------------------------------
## no entry
Tags (3)
5 Replies
admin
Immortal
Immortal

I may be going in a wrong direction here, but could you please confirm that you've set up the portgroup correctly on the remote side?

If your trunk vnic is backed by a distributed port group, you'll need to:

1) enable sink port attribute on it:

~# net-dvs --enableSink [0|1] -p dvport switch_name

2) And then, set the "forged transmit" to Enable.

If trunk vnic is backed by a standard port group, then you'll have to enable promiscuous mode, and set the forged transmit on the standard port group.

-- Dmitri

m-nara
Enthusiast
Enthusiast

It was my mistake.:smileysilly:

Physical switches did not have specified vlans.

Connection between VLAN and VXLAN over L2VPN works normally.

Only when tunnel id and VLAN id are same value, "show service l2vpn conversion-table" does not show any information.

Reply
0 Kudos
bridgegroup
Enthusiast
Enthusiast

DmitriK,

thank you very much for promiscuous mode.

Is there any link in the documentation for this option?

Reply
0 Kudos
admin
Immortal
Immortal

Doesn't look like documentation covers it sufficiently. I'll see if I can get it fixed.

Reply
0 Kudos
ignosgt
Contributor
Contributor

Hi, we have here a document with implementation, but is in spanish. It has all details.

» Requerimientos y configuración L2VPN de NSX en VMWare@ VirtualizacionVirtual @

There is a document about troubleshooting

» Diagnóstico y Troubleshooting de L2VPN de NSX con VMWAre@ VirtualizacionVirtual @

:smileysilly:

Reply
0 Kudos