Connectivity Guide

● Hybrid ports are not supported in VXLAN (hybrid port means an interface tagged to one VLAN and untagged to another
VLAN).
● The show vxlan vxlan-instance statistics remote-vtep-ip and the show vxlan vxlan-instance
statistics instance commands are not supported in a NSX environment.
● VXLAN is not supported in a stacking setup.
● Routing over VXLAN is not supported in a controller-based VXLAN setup.
● SNMP and REST API are not supported for VXLAN configurations.
● Multicast over VXLAN is not supported.
● In multicast and broadcast traffic, even though the remote VTEP is reachable through the ECMP path, load balancing is not
supported.
● Supports only 4 remote vteps through a single interface in a broadcast domain.
○ When a fifth remote VTEP configured is reachable via the same network port, traffic destined to the fifth remote VTEP
flows to the first remote VTEP configured via the same network port. If any of the first four remote VTEPS configured
via the same network port is removed, traffic flow to the fifth remote VTEP is not restored. You need to do one of the
following to restore traffic flow to fifth remote VTEP correctly :
￭ Remove and add the fifth remote VTEP again
￭ Flap the next hop reachability to the fifth remote VTEP
● Single VNI can be mapped to Single VLAN in both static and NSX controller-based VXLAN. Hence, only 4000 VNIs are
supported while configuring static VXLAN.
● You can map multiple VNIs with multiple VLANs in an NSX-based VXLAN.
● You can configure only one Nuage controller in a VXLAN setup. Nuage controller datapath-learning is not supported.
● In a Nuage controller-based VXLAN deployment, station moves of non-virtualized entities may not work as expected due to a
possible issue in the Nuage contoller.
NOTE:
When more than 15000 learned MAC addresses are synchronized from the Nuage controller to one of the VTEPs,
the SSL connection between the controller and the VTEP flaps continuously.
Configuring and Controlling VXLAN from the NSX
Controller GUI
You can configure and control VXLAN from the NSX controller GUI, by adding a hardware device to NSX and authenticating the
device.
1. Generate a certificate in your system and add it to the NSX before adding a hardware device for authentication.
To generate a certificate, use the following command:
● crypto cert generate self-signed cert-file flash://vtep-cert.pem key-file flash://
vtep-privkey.pem
To view the certificate, use the following command:
● show file flash://vtep-cert.pem
The output appears similar to the following example:
-----BEGIN CERTIFICATE-----
MIID3jCCAsagAwIBAgIBATANBgkqhkiG9w0BAQUFADCBmTELMAkGA1UEBhMCVVMxFTATBgNVBAMMDHd3dy5kZW
xsLmNvbTENMAsGA1UECgwERGVsbDEYMBYGA1UECwwPRGVsbCBOZXR3b3JraW5nMREwDwYDVQQHDAhTQU4gSm9z
ZTETMBEGA1UECAwKQ2FsaWZvcm5pYTEiMCAGCSqGSIb3DQEJARYTc29tZW9uZUBleGFtcGxlLmNvbTAeFw0xNT
ExMjAwMzA0NTNaFw0yNTExMTcwMzA0NTNaMIGZMQswCQYDVQQGEwJVUzEVMBMGA1UEAwwMd3d3LmRlbGwuY29t
MQ0wCwYDVQQKDAREZWxsMRgwFgYDVQQLDA9EZWxsIE5ldHdvcmtpbmcxETAPBgNVBAcMCFNBTiBKb3NlMRMwEQ
YDVQQIDApDYWxpZm9ybmlhMSIwIAYJKoZIhvcNAQkBFhNzb21lb25lQGV4YW1wbGUuY29tMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqGaGq3Cv4/RpuoiuePrnayORRhzEW/
H2Ypv8OKEcew1gySmFz24LQttzSHo4AO+qF3LkILvFW2RaHZ1mxbmm95d3PnZ8fXg2wgPz+
+T6coHGYH0o0+LkHVBb3IIXd/CSp+TBRzAwWMPS7tnaRv1UqiJtm6/RjcJghbf6zcQWUcg2CTtKe5ej/
rS2tIU9EBGCzL3xs6DRB3lvScgmuckc5L18qWqNHRWMdKFgKwHKUOOvHakPFs9RNJNy5Sxwfe/kgkVmqA/
KWiRIecLIgmgYjKu2E0uC3URpuydoN7UwPSeigXWeR3JyhzfFVEr5LtyXVpo9zS2JGyygKtzZBpke1wIDAQABo
y8wLTAMBgNVHRMEBTADAQH/MB0GA1UdDgQWBBTaOaPuXmtLDTJVv+
+VYBiQr9gHCTANBgkqhkiG9w0BAQUFAAOCAQEAn5E/w3BLQrX3e3Jv3EUFftGV0NABXOQxb/ODH4doA/
68nQcvW7GZgpwoxe77YQH+C/
uBNFwSBFxsu9ZkXhKu2q8wrCd+cnuaNu7Kq2V0DGSdR7eIkDTHkflttHbMmRfStHLetk3bA0HgXTW5c+vFn79E
X/
nJqxIvkl5ADT7k5JZR+j6i9eskgUlvBuV5OOZKzh29Gy4sjXvdYL5GirZFon8iZNY5FON+WlpcLJ9GjMvVfwvJ
x7exVs9cqXvm6UZ4Bf262STKbm+Q4qz30tyjDdF1xDBcBjL83UcEvSW65V/
Virtual Extensible LAN (VXLAN)
1037