iQExplore only showing 298 VMWare ESXi hosts

Owned by Conor McCann
Last updated: Jun 24, 2020 by Daniel Stuart-KellyVersion comment

iQExplore only showing 298 VMWare ESXi hosts when scan database has 600+
ESX hosts aren't showing as VM Hosts in iQExplore. There are now around 300+ hosts in the scan database and about 100+ VM Hosts showing in iQExplore. I managed to find the same number in iQDatahub by looking at a distinct count of physical hostnames from hub.devicevirtual.

 

Step-by-step guide

The iQExplore problem is based on the premise that almost all the model is based on the premise that calculations for hosts are generated off the requirement that hosts are identified and counted based on the presence of the VM guests. The absence of VMs (either becuase they don't exist or they have not been associated with the host for some reason). This required a modification to the model to ensure that ALL VM hosts have a dummy VM associated with them. This is accomplished in the initial script load (that is kicked off as part of initial data load) and this creates a dummy VM called 'NoVM' against all HOSTs identified in the iqExplore_v2. VMHostProcessor. It is essential that the new version of the view attached to this OnTime item is patched into datahub prior to the load. The bulk of the work required to this modification was to ensure that the dummy VMs are not dipslayed or counted.

 

Backup database before any changes to the database.

  1. Execute the attached Stored Procedure Explore_ VMHostProcessor against the iQDataHub-EDW

  2. Execute the SQL Patch 9229
  3. Open the following location C:\Users\conor.mccann\Documents\iQuate\iQExplore.
    Rename the files iQExplore.ini and iQExplore.qvw to .old
  4. Import new .qvw file and .ini file
  5. And reload the IQExplore and test.

 

Backout Plan : Remove files from step 4 .qvw file and .ini file and rename the original files from step 3. Restore the Database and reload iQExplore.