500 Internal Server Error during launch of thin client

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

After performing a CA-signed certificate update in NCM, the system throws an "HTTP Status 500 – Internal Server Error."

Environment

NCM 25.4.11 and above 

Cause

Server name and NCM launch name are different hence HostNameVerification fails. 

Resolution

For environments where the server name differs from the load-balanced NCM launch name, you can use the update-ncm-for-loadbalancer.sh script provided by NCM. This script is located in the $VOYENCE_HOME/tools directory.

Run script to add LB (Load balancer) name, example : 

update-ncm-for-loadbalancer.sh --third-party <Loadbalancer name> <IP>

This command would update webswing.config file to accept response from LB name and thin client would work.