VMware Networking Community
KWKirchner
Enthusiast
Enthusiast

Migrating NSX-V to NSX-T is failing at Edge Migration - API Call fail api/2.0/vdn/controller

Hello all,

We are trying to get our lab migrated from V (6.4) to T (3.2) and are running into an issue where the migration seems to stall on the Edge Migration. The CM.log file just has the same log entries repeating:

 

 

2022-04-26 17:50:55,225 4049 CM.plugins.overlay_plugin DEBUG  Waiting for CCP to get CDO mode VNI-VTEPS...
2022-04-26 17:50:55,225 4049 CM.clients.base_client DEBUG  API tracker: REQUEST method=POST, url=https://10.128.30.14/api/2.0/vdn/controller?action=execute&cmd-module=vxlan, non-session-headers=None, params=None, data={"cliCommandKey": "getVtepTableFromController", "cliParams": {"cliParamList": [{"name": "vni", "value": "4999"}]}}
2022-04-26 17:50:56,909 4049 CM.clients.base_client ERROR  Failed to POST https://10.128.30.14/api/2.0/vdn/controller?action=execute&cmd-module=vxlan with status: 404 and reason: {"errorCode":202,"details":"The requested object : Controller [] could not be found. Object identifiers are case sensitive.","rootCauseString":null,"moduleName":"core-services","errorData":null}
2022-04-26 17:50:56,909 4049 CM.plugins.overlay_plugin DEBUG  {"errorCode":202,"details":"The requested object : Controller [] could not be found. Object identifiers are case sensitive.","rootCauseString":null,"moduleName":"core-services","errorData":null}

 

 

 We're not exactly sure what it's attempting to do as we cant find any mention of this API function in the 6.4 API reference. We do have 3 functioning NSX-V controllers, so we are not sure which one its looking for.  Our VXLAN Segment ID range is also 5000-5999 so not sure where the 4999 is coming from. Super frustrating.

 

Reply
0 Kudos
1 Reply
KWKirchner
Enthusiast
Enthusiast

Have not got past this issue yet, but it appears to involve CDO mode being enabled and it creating the 4999 VNI.  CDO is off by default, so not sure if there was an issue with NSX-T turning it on or if we should have done that in advance.

Reply
0 Kudos