Deploying the NSX Advanced Load Balancer from the NSX GUI fails with the error "The Controller VM failed to register itself within the allotted wait time."
Article ID: 389697
Updated On:
Products
Issue/Introduction
NSX Advance Load Balancer (ALB) nodes no longer show in NSX UI or fail to deploy. When trying to deploy or redeploy the Advance Load Balancer nodes, the error "The Controller VM failed to register itself within the allotted wait time." is given.
ALB /var/lib/avi/log/log_core_manager.log showing registration timeout:
[####-##-## ##:##:##,###] ERROR [log_core_manager.generate_event:####] ESC[##mregister_to_nsxt.py on node (###-###-###-###) crash -- Pls investigate further. ESC[0m[####-##-## ##:##:##,###] ERROR [log_core_manager.generate_event:####] ESC[##mcore_archive.########_####.tar.gz not collected due to similar stack-trace seen=register_to_nsxt.py.########_######.stack_traceESC[0m[####-##-## ##:##:##,###] INFO [log_core_manager.log_monitor:###] event close_write on b'/var/lib/avi/archive/lcm_events.json'[####-##-## ##:##:##,###] INFO [log_core_manager.log_monitor:###] event close_write on b'/var/lib/avi/python_crash/stack_trace-!opt!avi!scripts!register_to_nsxt.py-####-########_######'[####-##-## ##:##:##,###] INFO [log_core_manager.get_process_path_from_core:###] Extracting process-path for Corefile:(stack_trace-!opt!avi!scripts!register_to_nsxt.py-####-########_######)[####-##-## ##:##:##,###] INFO [log_core_manager.get_process_path_from_core:###] Corefile: process-path: Time: (stack_trace-!opt!avi!scripts!register_to_nsxt.py-####-########_######:/opt/avi/scripts/register_to_nsxt.py:0.######)[####-##-## ##:##:##,###] INFO [log_core_manager.get_process_details:####] Corefile(/var/lib/avi/python_crash/stack_trace-!opt!avi!scripts!register_to_nsxt.py-####-########_######), process_name(register_to_nsxt.py), stack_trace(/var/lib/avi/tmp/archive/20250211_193122/crash/stack_trace-!opt!avi!scripts!register_to_nsxt.py-####-########_######), time(0.#####)
Environment
VMware NSX
VMware NSX-T Data Center
Cause
An incorrectly formatted certificate can prevent registration of the Advanced Load Balancer (ALB) with NSX.
Resolution
The below API is used to collect all certificate data from NSX. This can be used to check for certificate issues such as bad formatting, extra spaces, or incomplete certificate chain. https://<nsx_vip>/policy/api/v1/trust-management/certificates
Note: replace <nsx_vip> with the NSX Virtual IP address.
Replace any invalid certificates that are not correctly formatted. If this resolves the issue, the ALB can be deployed successfully.
If unable to identify invalid certificates, contact Support and provide NSX manager log bundles.
If you're unsure if any certificates have issues, or if NSX reports expiring or expired certificates, use the script attached to KB369034 to automatically update and replace all self-signed certificates on NSX Manager nodes.
Additional Information
For more information about NSX supported certificate formats:
NSX Manager upgrade pre-checks failed due to certificate parsing error
NSX error Certificate chain of compute manager <FQDN> is invalid (Error code: 90204)
VMware NSX-T Advanced Load Balancer Controller showing as not reachable in NSX-T UI
If you are contacting Broadcom support about this issue, please provide the following:
- Ensure log date range covers the full date of the event(s) being investigated. When in doubt, retrieve logs for all time.
- NSX Manager log bundles
- Text of any error messages seen in NSX GUI or command lines pertinent to the investigation
Handling Log Bundles for offline review with Broadcom support
Feedback
