NSX

How To Change VXLAN MTU Size and Teaming Policy in NSX Data Center For vSphere 6.4

In this article, I will share the steps to change the MTU settings, Teaming Policy of exiting VXLAN configuration. The VXLAN teaming policy and MTU settings can be changed on prepared hosts and clusters, but the changes apply only when preparing new hosts and clusters for VXLAN. Existing virtual port groups for VTEP vmkernel can be changed only by manually preparing the hosts and clusters again. You can change the teaming policy and MTU settings using API.

This step you can follow when you have chosen the incorrect MTU setting is chosen for the VTEPs. You need an API development software for performing this operation, in this procedure we use POSTMAN.

  • First, retrieve the information about all the VXLAN prepared switches using the below command
  • Open the API development platform and Click on New -> Request

  • And use GET and below syntax note that Authentication should be Basic Authentication and use vCNS/NSX Manager credentials

GET https://<NSX-Manager-IP-Address>/api/2.0/vdn/switches

Here our distributed switch name is “dvs-679”

  • Now you have to query with the specific vSphere Distributed Switch (dvs-679) that you noted earlier and you can identify the variables MTU, Teaming Policy you need to modify the setting.
  • Now copy the Response from Body
GET https://<NSX-Manager-IPAddress>/api/2.0/vdn/switches/dvs-679

Here we modify MTU from 1600 to 9000 of using the API call, you can change the Teaming policy also from there

  • Open a new tab and paste it into the Request Body box and perform below

Note:- Make sure you in the header add a new header: Content-Type: application/xml

PUT  https://<NSX-Manager-IP-Address>/api/2.0/vdn/switches 

  • Send the request and if everything went successfully you will get Status Code: 200 OK response.

  • Now you can verify that MTU is modified by running syntax the
GET https://<NSX-Manager-IP-Address>/api/2.0/vdn/switches/dvs-679

  • Now you can log in to vSphere Web Client and confirm verify the configuration changes are reflected

Reference

Conclusion 

We have successfully changed the MTU of our configuration using the above steps and we followed it from VMwareDocs . In NSX Data Center For vSphere, many operations can be performed using API calling option, we are exploring more in NSX will share more posts in the future.

Rajesh Radhakrishnan

Recent Posts

NAKIVO Backup & Replication v10.8 Released With New Features

Nakivo has released its new Backup and Replication solution Nakivo v10.8, which includes support for…

2 years ago

Oracle Cloud VMware Solution and Features

Oracle Cloud VMware Solution (OCVS) provides a customer-managed, native VMware-based cloud environment hosted in Oracle…

2 years ago

Vinchin Backup and Recovery Review

Vinchin is a professional provider of data protection solutions for enterprises. It provides a series…

2 years ago

VMware Cloud Disaster Recovery (VCDR) Solution Deployment And Configuration Part 2

In my previous blog post, I have explained about VMware Cloud Disaster Recovery (VCDR) Onboarding and…

2 years ago

How to Deploy vRNI Cloud With VMC on AWS

vRealize Network Insight helps you build an optimized, highly available, and secure network infrastructure across…

2 years ago

This SysAdmin Day, WIN with Hornetsecurity!

Can you believe it's here again? SysAdmin Day is back, and with it comes endless gratitude…

2 years ago