- Upgrade was recently completed to NSX-T version 3.2.x.
- The Transport node profile (TNP) was changed.
- The Transport nodes (TN) go into an NSX install failed state after changing the TNP.
- The TN status shows as Partial Success.
- On the NSX-T manager log /var/log/proton/nsxapi.log we see the following entries:
INFO L2HostConfigTaskExecutor4 TransportNodeStateServiceImpl 4665 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Incoming Revision: [11058] Obj: [TnStateInternal [id=<TN UUID>, retryCount=0, vmkMigrationFailures=0, revision=11058, stageToStatusMap={HostConfig=TnStageStatus [stageName=HostConfig, status=PARTIAL_SUCCESS, errorCode=8700, errorParams=[9a5faf0b-####-####-####-########2f1, NSXA Vim not ready;
- In the manager log /var/log/proxy/reverse-proxy.log we see the following entries:
INFO https-jsse-nio-10.218.34.91-443-exec-4 RegistrationTokenAuthenticationProvider 9298 AAA [nsx@6876 comp="nsx-manager" level="INFO" subcomp="http"] Successful login for reg-token <token UUID>, delegated user, roles (none)
- On the TN log /var/run/log/nsxcli.log we see the following entries:
31412205 cli.utils.apiclient ERROR POST /api/v1/fabric/nodes/<TN UUID>?action=register_node returned status: 403
...
2137855 cli.audit INFO CMD: join management-plane 10.34.45.14 thumbprint <thumb print> token <token-obfuscated> node-uuid <TN UUID> (duration: 8.769s), Operation status: CMD_EXECUTED_WITH_ERROR_RESULT
5987505 cli.descriptors.cli_command_service INFO {0} CMD: join management-plane <manager IP address> thumbprint <thumb print> token <token-obfuscated> node-uuid <TN UUID>
...
3041798 cli.utils.apiclient ERROR POST /api/v1/fabric/nodes/<TN UUID>?action=register_node returned status: 403
b'{\n "module_name" : "common-services",\n "error_message" : "The credentials were incorrect, or the account specified has been locked.",\n "error_code" : 403\n}\n'
3041798 cli.commands.host_shared.register INFO Node registration failed, rc=403: None
3041798 cli.commands.host_shared.register INFO Error from MP API: The credentials were incorrect, or the account specified has been locked.