VMware NSX for vSphere 6.0.x
VMware NSX for vSphere 6.1.x
VMware NSX for vSphere 6.2.x
VMware NSX for vSphere 6.3.x
VMware NSX for vSphere 6.4.x
To change the VXLAN teaming policy and MTU settings, unprepare the cluster for VXLAN and reprepare the cluster to apply the new settings from the client.
Note: This does not change MTU or teaming policy of pre-existing port groups. You still have to manually update the teaming policy and/or MTU of VXLAN port groups which have already been deployed (vmkernel and virtual wire/logical switch port groups).
To change the VXLAN teaming policy or MTU in vShield/NSX manager, use API calls to update the settings without redeploying the cluster:
Caution: This procedure modifies the database. Ensure to take a backup of the configuration files before proceeding.
For the Body, copy the output of step 4’s API call and use that as the body of your next call.
Modify the parameters that are to be changed such as teaming policy and/or MTU.
For example:
To change to 9000 MTU and a Load Balancing Source MAC teaming policy:
<vdsContext>
<switch>
<objectId>dvs-35</objectId>
<objectTypeName>VmwareDistributedVirtualSwitch</objectTypeName>
<vsmUuid>423A993F-####-####-####-54E48D508D90</vsmUuid>
<nodeId>916287b3-####-####-####-83878dfe3e7f</nodeId>
<revision>6</revision>
<type>
<typeName>VmwareDistributedVirtualSwitch</typeName>
</type>
<name>vds-####-a</name>
<scope>
<id>datacenter-21</id>
<objectTypeName>Datacenter</objectTypeName>
<name>Datacenter #### A</name>
</scope>
<clientHandle/>
<extendedAttributes/>
<isUniversal>false</isUniversal>
<universalRevision>0</universalRevision>
</switch>
<mtu>9000</mtu>
<teaming>LOADBALANCE_SRCMAC</teaming>
<uplinkPortName>Uplink 4</uplinkPortName>
<promiscuousMode>false</promiscuousMode>
</vdsContext>
Following is a list of valid teaming policy entries in the <teaming>Teaming_policy</teaming> line:
For more information on querying NSX vDS configurations using vSphere APIs, see:
Best practices for using snapshots in the vSphere environment
Impact/Risks:
Incorrect modification of switch related database entries using PUT API calls can lead to an outage. It is recommended to take a snapshot of NSX/VCNS manager before making any changes.