In NSX 6.2.2 , the VXLAN Port no is 8472.
When upgrading to 6.3.2 , the VXLAN port no supported is 4789.
Wanted to check is it mandatory to change to VXLAN port no to 4789.
What will happen if the VXLAN port no is not changed after the upgrade.
Wanted to check is it mandatory to change to VXLAN port no to 4789.
What will happen if the VXLAN port no is not changed after the upgrade.
Not mandatory.
Nothing changes, therefore No Impact.
Design Consideration: But in future if you are going to do New NSX installation, it will default go to 4789. Classic use case is when you are planning for Cross-VC. It becomes mandatory if you are planning to use Hardware VTEP.
Wish VMware make decision with zero impact to critical infrastructure piece of SDDC. I would leave it to 8472 unless benefits are more than risks.
When upgrading to 6.3.2 , the VXLAN port no supported is 4789.
Small correction, port number doesn't change when you upgrade.
Wanted to check is it mandatory to change to VXLAN port no to 4789.
What will happen if the VXLAN port no is not changed after the upgrade.
Not mandatory.
Nothing changes, therefore No Impact.
Design Consideration: But in future if you are going to do New NSX installation, it will default go to 4789. Classic use case is when you are planning for Cross-VC. It becomes mandatory if you are planning to use Hardware VTEP.
Wish VMware make decision with zero impact to critical infrastructure piece of SDDC. I would leave it to 8472 unless benefits are more than risks.
When upgrading to 6.3.2 , the VXLAN port no supported is 4789.
Small correction, port number doesn't change when you upgrade.
Agree with Techs, mandatory for Hardware VTEP, new install will use 4789 and IANA uses 4789 as per RFC 7348 - Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Lay...
VXLAN port also does not change during upgrade as per here Change VXLAN Port and changing the port from UI does not require downtime
If you upgrade from NSX 6.2.2 or earlier to NSX 6.2.3 or later, and your installation used the old default (8472), or a custom port number (for example, 8888) before the upgrade, that port will continue to be used after the upgrade unless you take steps to change it.
Changing the VXLAN port is done in a three phase process, and will not interrupt VXLAN traffic.
This also has been discussed in this thread: Is there downtime required when changing the VXLAN Port?
I would change to standardise VXLAN ports as it will not interrupt VXLAN traffic