Highlighted
Absent Member.. Absent Member..
Absent Member..
902 views

NNM is not able to discover VMs on ESXi.

Jump to solution

Dear Colleagues,

NNMi is able to communicate with ESX using SNMP-V2 but cannot communicate with it using web agent.

Below are the first 3 lines of configuration polling:

12/19/16 5:51:34 PM **** Starting configuration poll of node esx-1(83d66edc-6c06-4a33-a611-863470b95cc1) ****

12/19/16 5:51:34 PM Supports SNMP V2C

12/19/16 5:51:34 PM No VMware communication. VMware Communication Configuration for esx-1 may be missing or invalid.

 

 The webagent is not added to NNMi

Below are the steps that were followed in adding the ESX.

1- add the trusted certificate to NNMi

2- add the VMware credentials to NNM

3- seed the ESX using its name and not IP

Kindly advise on how I can troubleshoot the problem and whether there is an extra configuration step that I have not done.

Thank you and Best Regards,

Rabee

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Honored Contributor.
Honored Contributor.

Re: NNM is not able to discover VMs on ESXi.

Jump to solution

Hi Rabee,

Here are something we can check more.

What are node names in NNMi inventory, are they machining names in the certificates?
I have seen issues with short FQDN node names in inventory, while a full FQDN was used in the certificate.

You might want to try command like:
nnmcommunication.ovpl listCertificates -nodeSetting <NODE full FQDN NAME>

nnmcommunication.ovpl listCertificates -nodeSetting <NODE short NAME>
Check if this could return an error with short name.

If this returns an error, try change node naming rule from shortFQDN to fullFQDN and WebAgents issue may fix.

If still failed, I advise you open a support case and include followings to get further help:
1.NNMi version and patch level.
2.Screen copy of the problematic Node details from NNMi inventory(General Tab)
3.The output of
nnmcommunication.ovpl listCertificates -nodeSetting <NODE full FQDN NAME>
nnmcommunication.ovpl listCertificates -nodeSetting <NODE short NAME>
configuration polling of that node.

Many thanks.

Chen

All the best

HP Support
Viewed the Support tips? Search for "(NNMi) Support Tips" and order by Date to get the list
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

1 Reply
Highlighted
Honored Contributor.
Honored Contributor.

Re: NNM is not able to discover VMs on ESXi.

Jump to solution

Hi Rabee,

Here are something we can check more.

What are node names in NNMi inventory, are they machining names in the certificates?
I have seen issues with short FQDN node names in inventory, while a full FQDN was used in the certificate.

You might want to try command like:
nnmcommunication.ovpl listCertificates -nodeSetting <NODE full FQDN NAME>

nnmcommunication.ovpl listCertificates -nodeSetting <NODE short NAME>
Check if this could return an error with short name.

If this returns an error, try change node naming rule from shortFQDN to fullFQDN and WebAgents issue may fix.

If still failed, I advise you open a support case and include followings to get further help:
1.NNMi version and patch level.
2.Screen copy of the problematic Node details from NNMi inventory(General Tab)
3.The output of
nnmcommunication.ovpl listCertificates -nodeSetting <NODE full FQDN NAME>
nnmcommunication.ovpl listCertificates -nodeSetting <NODE short NAME>
configuration polling of that node.

Many thanks.

Chen

All the best

HP Support
Viewed the Support tips? Search for "(NNMi) Support Tips" and order by Date to get the list
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.