Creating NSX-T Transport Node Fails: RPC request timed out
Article ID: 322567
Updated On:
Products
VMware NSX
Issue/Introduction
Symptoms:
- You have NSX-T 3.2.0 deployed.
- When trying to create a transport node, it fails with the following error:
"App Init configuration: Caught MessagingException during app init config stage. [TN=TransportNode/714bf77d-ff4c-490c-8830-b04af975f61a]. Reason: RPC request timed out."
Environment
VMware NSX-T Data Center
VMware NSX-T Data Center 3.x
VMware NSX-T Data Center 3.x
Cause
If the host retrieves its IP address from a DHCP server and it takes longer than 30 seconds, the alarm is triggered.
This happens as DHCP client retrieving an IP from the DHCP server takes about 1 minute and the app init rpc timeout value is 30 seconds.
This happens as DHCP client retrieving an IP from the DHCP server takes about 1 minute and the app init rpc timeout value is 30 seconds.
Resolution
This is a known issue impacting NSX-T 3.2.0.
Workaround:
No workaround is required. The failure will be recovered automatically, the transport node configuration will be pushed down again after a period of time, at which point the server should have received its IP address from the DHCP server.
Workaround:
No workaround is required. The failure will be recovered automatically, the transport node configuration will be pushed down again after a period of time, at which point the server should have received its IP address from the DHCP server.
Feedback
Yes
No
Powered by
