Changing VXLAN UDP port from 8472 to 4789 fails on NSX
search cancel

Changing VXLAN UDP port from 8472 to 4789 fails on NSX

book

Article ID: 330261

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • While changing Port for VXLAN you might observe this logs:

    2016-06-12 14:23:18.692 GMT INFO http-nio-127.0.0.1-7441-exec-2 VdnIdManagerImpl:655 - Changing the default VXLAN udp port to the port 4789.
    2016-06-12 14:23:20.136 GMT INFO http-nio-127.0.0.1-7441-exec-2 NetworkPrepFacadeImpl:332 - Found all given hosts are at NetworkFabric version >= [6.2.0]
    2016-06-12 14:23:20.136 GMT INFO http-nio-127.0.0.1-7441-exec-2 NetworkPrepFacadeImpl:350 - Determined that cluster [domain-c59494] has been upgraded to minimum required NetworkFabric[6.2.0] ? [true]
    2016-06-12 14:23:23.547 GMT INFO http-nio-127.0.0.1-7441-exec-2 NetworkPrepFacadeImpl:332 - Found all given hosts are at NetworkFabric version >= [6.2.0]
    2016-06-12 14:23:23.547 GMT INFO http-nio-127.0.0.1-7441-exec-2 NetworkPrepFacadeImpl:350 - Determined that cluster [domain-c7] has been upgraded to minimum required NetworkFabric[6.2.0] ? [true]
    2016-06-12 14:23:23.617 GMT INFO http-nio-127.0.0.1-7441-exec-2 TaskServiceImpl:101 - TF:Created Job with ID jobdata-79379
    2016-06-12 14:23:23.622 GMT INFO DCNPool-5 SchedulerService:193 - Received job creation DCN for job id jobdata-79379
    2016-06-12 14:23:23.630 GMT INFO http-nio-127.0.0.1-7441-exec-2 TaskServiceImpl:399 - TF:Scheduling Job jobdata-79379
    2016-06-12 14:23:23.645 GMT INFO http-nio-127.0.0.1-7441-exec-2 SchedulerService:198 - Job jobdata-79379 is scheduled and put data in to scheduleInfoTable
    2016-06-12 14:23:23.646 GMT INFO http-nio-127.0.0.1-7441-exec-2 VdnIdManagerImpl:739 - Update the VXLAN udp port on

    Note: It is possible to not see these log entries though the change hangs.
     
  • Running the REST API call GET https://nsxmgr-01a/api/2.0/vdn/config/vxlan/udp/port/taskStatus returns:

    <taskPhase>PHASE_TWO</taskPhase>
    <taskStatus>PAUSED</taskStatus>

    The expected response is:

    <taskPhase>FINISHED</taskPhase>
    <taskStatus>SUCCEED</taskStatus>



Environment

VMware NSX Data Center for vSphere 6.x

Resolution

To resolve this issue run API call to NSX manager to resume task.

Be aware that task can be paused on different stages, there 3 PHASES.

with this API GET https://<nsx mgr IP>/api/2.0/vdn/config/vxlan/udp/port/taskStatus

you find on which PHASE is paused

the run a API to resume task for changing

REST API POST https://<nsx mgr IP>/api/2.0/vdn/config/vxlan/udp/port/resume

you need to run this API call few times it depends on which stage is paused

if it on stage two then you need to run this for verify status

https://<nsx mgr IP>/api/2.0/vdn/config/vxlan/udp/port/taskStatus

and then https://<nsx mgr IP>/api/2.0/vdn/config/vxlan/udp/port/resume

to resume phase two .

then again

https://<nsx mgr IP>/api/2.0/vdn/config/vxlan/udp/port/taskStatus if it paused again then run again resume API call

Powered by Wolken Software