After upgrading NCM the web console page is not accessible by hostname
search cancel

After upgrading NCM the web console page is not accessible by hostname

book

Article ID: 451833

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

After upgrading NCM users are no longer able to log into the Web Console by hostname however they can log in by IP.  Unfortunately this is a violation of security policy.

Cause

At the time of install there is a check for hostname resolution.  If that fails then webswing will use the IPAddress.  The changes are not preserved on upgrade.  The file are rebuilt so even if the hostname was there previously, it may not be there after upgrading.

Resolution

Update the https and wss entries for the webswing to use the FQDN of the host in the following files:

$NCM/webtomcat/bin/webswing.properties
$NCM/webtomcat/bin/webswing-admin.properties
$NCM/webtomcat/webswing/webswing.config

Restart NCM services

Additional Information

If you are using a CA certificate, verify the SAN of the cert has the FQDN entered.