vCenter discovery should automate preconfiguration tasks avoiding lots of manuall effort

vCenter discovery should automate preconfiguration tasks avoiding lots of manuall effort

Currently, classical deployment NNMi handles only very limited scope of information discovered by getting in touch with vSphere web agent (quoted from device support matrix):

  • VMware ESX/ESXi
    • For ESXi 5.1 and 5.5, Virtual Machines and Virtual Switches are discovered and managed in NNMi using the ESXi Host's vSphere web-service API.
      • The NNM Communication Configuration Device Credentials (Node, Region, or Default settings) must be properly configured with the ESXi Host VSphere API credentials.
      • If the ESXi HOST is configured for VSphere API communication using HTTPS, (a) the ESXi HOST must be properly configured with a valid HTTPS certificate, and (b) that certificate must be imported into NNMi. See the Deployment Guide, Chapter 7, "Working with Certificates for NNMi" for more instruction.
      • 'VMware Tools' must be installed on the Virtual Machine's Guest OS to discover its IP Addresses in NNMi. VMware only reports IP Address information for a VM when 'VMware Tools' is installed and running on the VM's Guest OS. Windows and Linux variants are both offered and supported by VMware, but it is an administrative decision as to whether 'VMware Tools' is actually installed on a VM's Guest OS by the VMware or GuestOS system administrator.
      • VMware Virtual Switch (vSwitch) and VMware Distributed Virtual Switch (dvSwitch) are discovered and represented in NNMi as Virtual Bridges within the ESXi Host node. The ESXi Host interfaces and Virtual Machine virtual ports associated with each vSwitch/dvSwitch are reported on the "Uplinks" and "Virtual Ports" tabs of the Virtual Switch details form, respectively, as well as in the new "Wheel" and "Loom" Views of the ESXi Host. VMware DVSwitch versions 4.0, 4.1, 5.0, 5.1 and 5.5 (subject to installed ESXi Host version) are certified with NNMi.
      • The names of the Distributed Switches shown in vCenter would be different from the names shown in NNMi. This is because NNMi shows the SNMP values returned by VMware. For Example, vCenter shows vSwitch as "Distributed Switch:dvSwitch-sim1" whereas NNMi shows as "DvsPortset-0"

That were two ERs targeting to make it riched, and the Idea here also sounds similar to the topic:

https://community.microfocus.com/t5/NOM-Idea-Exchange/Add-support-for-vCenter-managed-access-to-ESXi-hosts-when/idi-p/1656362

As the best, vCenter discovery should automate adding ESX names, certificates, nodes behind.

2 Comments
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Dear Submitter, We would encourage you to vote for the original idea, which is https://community.microfocus.com/t5/NOM-Idea-Exchange/Add-support-for-vCenter-managed-access-to-ESXi-hosts-when/idi-p/1656362, instead of creating a new one, as more votes for one idea would increase the likelihood of idea moving to the next stage. Can you also specify the ER number you referred to in the Idea?
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
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.