Smarts NCM: Unable to query data from the msa from NCM 9.2.2a
Article ID: 331308
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Cannot access the ncm-msa details via the link :
Following installation to NCM 9.2.2a , the ncm-msa details cannot be accessed via the link :
https://<hostname FQDN >:9443/ncm-msa/msa/ncm/instances
The following error is seen in the catalina.log file:
Cannot access the ncm-msa details via the link :
https://<hostname FQDN >:9443/ncm-msa/msa/ncm/instances
Using any available browser.
Using any available browser.
Following installation to NCM 9.2.2a , the ncm-msa details cannot be accessed via the link :
https://<hostname FQDN >:9443/ncm-msa/msa/ncm/instances
The following error is seen in the catalina.log file:
Caused by: java.security.cert.CertificateException: No name matching <hostname> found
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:208)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:93)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:347)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:203)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1323)
... 154 more
25 Apr 2014 17:52:00,427-[http-9443-2] ERROR com.emc.ionix.uim.msa.domain.DataModelUtil - loadTypes caught an exception
java.lang.NullPointerException: Cannot invoke method getTableNames() on null object
at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
Environment
VMware Smart Assurance - NCM
Cause
The certification on this NCM have been created using the full FQDN for the hostname i.e.
>hostname --fqdn
As can be seen from the error in the catalina log:
Caused by: java.security.cert.CertificateException: No name matching <hostname> found
The shortname is being used for ncm-msa here, but there is no entry in the cert for the shortname, hence the error
The issue for the ncm-msa occurred because during installation, the command
>hostname --fqdn
is being used to associate the host rather than
>hostname
>hostname --fqdn
As can be seen from the error in the catalina log:
Caused by: java.security.cert.CertificateException: No name matching <hostname> found
The shortname is being used for ncm-msa here, but there is no entry in the cert for the shortname, hence the error
The issue for the ncm-msa occurred because during installation, the command
>hostname --fqdn
is being used to associate the host rather than
>hostname
Resolution
There will be a fix in a future release for NCM but in the meantime, to fix this for ncm-msa, the following files need to be edited:
Replace the hostname with the output for hostname --fqdn in the files:
1) ncm-msa/WEB-INF/classes/ncm-resources.xml
2) ncm-msa/WEB-INF/classes/ncmdatasource.properties
e.g.
>hostname
zen-machine1
>hostname --fqdn
zen-machine1.emc.com
Using the example, replace zen-machine1 with zen-machine1.emc.com in:
1) ncm-msa/WEB-INF/classes/ncm-resources.xml
2) ncm-msa/WEB-INF/classes/ncmdatasource.properties
3) restart the services
>service vcmaster restart
Replace the hostname with the output for hostname --fqdn in the files:
1) ncm-msa/WEB-INF/classes/ncm-resources.xml
2) ncm-msa/WEB-INF/classes/ncmdatasource.properties
e.g.
>hostname
zen-machine1
>hostname --fqdn
zen-machine1.emc.com
Using the example, replace zen-machine1 with zen-machine1.emc.com in:
1) ncm-msa/WEB-INF/classes/ncm-resources.xml
2) ncm-msa/WEB-INF/classes/ncmdatasource.properties
3) restart the services
>service vcmaster restart
Additional Information
The link to ncm-msa:
https://<hostname FQDN >:9443/ncm-msa/msa/ncm/instances
will not work on Chrome browsers
https://<hostname FQDN >:9443/ncm-msa/msa/ncm/instances
will not work on Chrome browsers
Feedback
Yes
No
Powered by
