VXLAN segments are built between VXLAN tunnel end points (VTEPs). A hypervisor host is an example of a typical VTEP. Each VXLAN tunnel has a segment ID. You must specify a segment ID pool for each NSX Manager to isolate your network traffic. If an NSX controller is not deployed in your environment, you must also add a multicast address range to spread traffic across your network and avoid overloading a single multicast address.
When determining the size of each segment ID pool, consider that the segment ID range controls the number of logical switches that can be created. Choose a small subset of the 16 million potential VNIs. Do not configure more than 10,000 VNIs in a single vCenter because vCenter limits the number of dvPortgroups to 10,000.
If VXLAN is in place in another NSX Data Center for vSphere deployment, consider which VNIs are already in use and avoid overlapping VNIs. Non-overlapping VNIs is automatically enforced within a single NSX Manager and vCenter environment. Local VNI ranges cannot be overlapping. However, it is important for you make sure that VNIs do not overlap in your separate NSX Data Center for vSphere deployments. Non-overlapping VNIs is useful for tracking purposes and helps to ensure that your deployments are ready for a cross-vCenter environment.
If any of your transport zones use multicast or hybrid replication mode, you must add a multicast address or a range of multicast addresses.
Having a range of multicast addresses spreads traffic across your network, prevents the overloading of a single multicast address, and better contains BUM replication.
Do not use 188.8.131.52/24 or 184.108.40.206/24 as the multicast address range, because these networks are used for local subnet control, meaning that the physical switches flood all traffic that uses these addresses. For more information about unusable multicast addresses, see https://tools.ietf.org/html/draft-ietf-mboned-ipv4-mcast-unusable-01.
When VXLAN multicast and hybrid replication modes are configured and working correctly, a copy of multicast traffic is delivered only to hosts that have sent IGMP join messages. Otherwise, the physical network floods all multicast traffic to all hosts within the same broadcast domain. To avoid such flooding, you must do the following:
Make sure that the underlying physical switch is configured with an MTU larger than or equal to 1600.
Make sure that the underlying physical switch is correctly configured with IGMP snooping and an IGMP querier in network segments that carry VTEP traffic.
Make sure that the transport zone is configured with the recommended multicast address range. The recommended multicast address range starts at 220.127.116.11/24 and excludes 18.104.22.168/24.
You can configure a single segment ID range and a single multicast address or multicast address range from the vSphere Web Client . If you want to configure multiple segment ID ranges or multiple multicast address values, you can do this using the API. See the NSX API Guide for details.
- Log in to the vSphere Web Client.
- Navigate to logical network settings.
In NSX 6.4.1 and later, navigate to .
In NSX 6.4.0, navigate to .
- Navigate to segment ID pool settings.
In NSX 6.4.1 and later, click VXLAN Settings, then click Edit next to Segment IDs.
In NSX 6.4.0, click .
- Enter a range for segment IDs, such as 5000-5999.
- (Optional) If any of your transport zones use multicast or hybrid replication mode, you must add a multicast address or a range of multicast addresses.
- Select or turn on the Enable Multicast addressing feature.
- Enter a multicast address or multicast address range, such as 22.214.171.124-126.96.36.199.
When you configure logical switches, each logical switch receives a segment ID from the pool.