Due to hostname mismatch between the certificate (*-versa-director) and the configured hostname (Director-DC1 and Director-DC2), configured data is not displayed after a vnms restart.
To resolve this, you must make changes to the Versa Director and to the Versa Analytics.
Follow these steps to edit the CN and use the wild card Versa Director name (Director-DC* ) in /opt/versa/vnms/scripts/vnms-certgen.sh.
1. Go to directory /var/versa/vnms/data/certs.
2. Run the keytool --printcert -v -file versa_director_client.cer | grep CN sudo command.
The output displays the CN.
Follow these steps to resolve the hostname mismatch on active Director:
#CN=`hostname -f`
Change the CN name with the
CN="*-versa-director"
admin@Director1:/var/versa/vnms/data/certs$ sudo keytool --printcert -v -file versa_director_client.cer | grep C Owner: CN=*-versa-director, OU=VersaDirector, O=versa-networks, ST=California, C=US Issuer: L=Santa Clara, ST=California, C=US, OU=VersaDirector, O=versa-networks, CN=*-versa-director
Follow these steps to resolve the hostname mismatch on backup Director:
Follow these steps to resolve the hostname mismatch on Versa Analytics:
versa@versa-analytics:/opt/versa/var/van-app/certificates$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 versa-analytics 10.40.171.3 master-versa-director 10.40.171.4 slave-versa-director