Creating Transport Node Fails with RPC Request Timed Out - VMware NSX-T

Products

• VMware NSX

Issue/Introduction

This article addresses an issue where transport node creation fails due to a hardcoded RPC timeout during DHCP IP address retrieval.

Symptoms:

• NSX-T 3.2.0 is deployed.
• Transport node creation fails with the following error:

App Init configuration: Caught MessagingException during app init config stage. [TN=TransportNode/####]. Reason: RPC request timed out.

Environment

• VMware NSX-T Data Center 3.x
• VMware NSX-T Data Center 3.2.0

Cause

The failure occurs when the host retrieves its IP address from a DHCP server and the process exceeds 30 seconds. The app init rpc timeout value is 30 seconds, leading to a timeout before the DHCP client completes retrieval (which may take up to 60 seconds).

Resolution

Fixed in release 3.2.4.0 and higher. See Download Broadcom products and software for steps to download this release.

Workaround:

1. No manual intervention is required for immediate recovery.
2. The failure will recover automatically as the transport node configuration is pushed down again after a period of time.
3. Ensure the DHCP server is reachable and responding within standard timeframes.

Additional Information

For updates on similar issues, subscribe to this article: https://knowledge.broadcom.com/external/article/275360.