Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Changing segment or multicast range in NSX Data Center for vSphere (57844)

Last Updated: 6/23/2020Categories: How toTotal Views: 3248Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides information on how to change segment range and multicast range in NSX Data Center for vSphere.
You might need a change in segment or multicast range when two single sites with overlapping segment or multicast range need to be brought into a cross-vCenter NSX setup.

Important: If you have NSX Data Center for vSphere 6.4.3 or earlier installed, and you have distributed logical routers deployed, you must contact VMware Customer Support for assistance with this task.

If you have NSX Data Center for vSphere 6.4.4 or later installed, you can follow the instructions in this article.

Notes:

The introduction of multiple VNI pools as described in this article should only be a temporary solution. In addition, VMware does not support an upgrade in this state.

When determining the size of each segment ID pool, keep in mind 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. You should not configure more than 10,000 VNIs in a single vCenter Server because vCenter limits the number of dvPortgroups to 10,000.

If VXLAN is in place in another NSX deployment, consider which VNIs are already in use and avoid overlapping VNIs. Non-overlapping VNIs are automatically enforced within a single NSX Manager and vCenter Server environment. Local VNI ranges cannot be overlapping. However, it's important for you make sure that VNIs do not overlap in your separate NSX deployments. Non-overlapping VNIs are useful for tracking purposes and helps to ensure that your deployments are ready for a cross-vCenter environment.

Resolution

Resolving overlapping segment ranges and move logical switches:

Create a new non overlapping Segment Range:

For example:

POST https://<NSXMGR_IP>/api/2.0/vdn/config/segments
<segmentRange>
<name>Segment ID Pool 2</name>
<begin>7000</begin>
<end>7999</end>
</segmentRange>

# Note the segment range “id” (lets call it newRangeId) returned in response payload.

# GET segments will also return segment range "id",
GET https://<nsxmgr-ip>/api/2.0/vdn/config/segments
<segmentRanges>
<segmentRange>
<id>4</id>
<name> Segment ID Pool 2</name>
<begin>7000</begin>
<end>7999</end>
<isUniversal>false</isUniversal>
<universalRevision>0</universalRevision>
</segmentRange>
<segmentRanges>

Shutdown or disconnect VNIC from the dvpg (LogicalSwitch).

Move each logical switch from the old segment range to new segment range. This API needs virtualwire-id and rangeId as inputs. API payload is empty:

For example:

PUT https://<NSXMGR_IP>/api/2.0/vdn/virtualwires/<virtualwire-id>/segmentreconfig/<newRangeId>

To resolve overlapping multicast ranges and move logical switches:

Create a new non overlapping multicast Range:

For example:

POST https://<NSXMGR_IP>/api/2.0/vdn/config/multicasts
<multicastRange>

<name>Range 2</name>

<begin>237.0.0.0</begin>

<end>237.255.255.255</end>

</multicastRange>

# Note the multicast range “id” (lets call it newRangeId) returned in response payload.

# GET multicasts will also return multicast range id,
GET https://<nsxmgr-ip>/api/2.0/vdn/config/multicasts

<multicastRanges>

<multicastRange>

<id>3</id>

<name>Range 2</name>

<begin>237.0.0.0</begin>

<end>237.255.255.255</end>

<isUniversal>false</isUniversal>

<universalRevision>0</universalRevision>

</multicastRange>

</multicastRanges>

Shutdown or disconnect VNIC from the dvpg (LogicalSwitch).

Move each logical switch from the old multicast range to new multicast range. This API needs virtualwire-id and newRangeId as inputs. API payload is empty:

For example:

PUT https://<NSXMGR_IP>/api/2.0/vdn/virtualwires/<virtualwire-id>/multicastreconfig/<newRangeId>

Move each distributed logical router to the new segment or multicast range.

If you are using segments, use the following API:

POST https://<NSXMGR_IP>/api/4.0/edges/{edge-id}?action=vdridreconfig&vdnRangeId=<newRangeId>

To delete the old segment range:

For example:

DELETE https://<NSXMGR_IP>/api/2.0/vdn/config/segments/<oldRangeId>

For more information on overlapping segment ranges, see the Cross vCenter NSX Installation Guide.

If you are using multicast, use the following API:

POST https://<NSXMGR_IP>//api/4.0/edges/{edge-id}?action=vdridreconfig&multicastRangeId=<newRangeId>

To delete the old multicast range:

For example:

DELETE https://<NSXMGR_IP>/api/2.0/vdn/config/multicasts/<oldRangeId>

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant