Skip to main content

"Unknown" status showing in host compliance status





There were several practices where we use host profile into our environment to get the compliance among all other ESXi host into the cluster.

There are mostly 3 types of status identified to the hostprofile which is attached to the ESXi host.

1) Compliant
2) Not-compliant
3) Unknown

As you know when all the features and settings of host profile and ESXi meets perfectly then only status shows as Compliant status.
Not-compliance status shows when the hostpofile unable to meet the complete requirement on the host and some feature are missing.
Unknown status is the one which suspect even when you have ESXi host into the Compliance status or sometime could be in Not-compliant status.

There are several indentified cause for that.

Most of the time we found that all good from ESXi UI and hostprofile where all the parameters are meet successfully and even then host profile status shows as "UNKNOWN" status.

In my case i found one glitch where the dvs configuration was not sync completely in /etc/vmware/hostd/portgroup.gz under the ESXi host. Its states that the full mapping of dvportgroup to portgroupkey was missing.

To verify the correct mapping you can verify the portgroup.gz file from the ESXi host which shows host compliant status with ESXi host which shows hostprofile as "UNKNOWN" status.


Resolution:

To resolve this issue you can move all the DVS Switch/portgroup to Standard Switch and revert back all to the DVS where all the portgroup and portgroupkey mapping gets established properly into /etc/vmware/hostd/portgroup.gz of the ESXi host
which is showing unknown status. After completion, try to verify the host compliance check and you will find the host profile status moves to compliant successfully.

Second solution: If your ESXi host is running with 6.0 U1, then upgrade it to 6.0 u2 which is one of the solution.



Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl
google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0 google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0