Skip to content

Host Profile Error - Found extra CIM-XML Indication Subscription

When you use Host Profiles to check the compliance of your configuration you might get the following failures against the host profile. The message persists after applying a profile and rebooting the ESXi Host:compliance-error-cim-xml

Found extra CIM-XML Indication Subscription on local system for query SELECT * FROM CIM_ProcessIndication sent to destination https://[URL]
Found extra CIM-XML Indication Subscription on local system for query SELECT * FROM CIM_AlertIndication sent to destination https://[URL]

This compliance error appears on HP Hardware when HP Systems Insight Manager (HP SIM) is in use. The URL is different for each system, so the host profile can not be applied. To get rid of the message you have to disable CIM Indication Subscriptions in the Host Profile Configuration

Read More »Host Profile Error - Found extra CIM-XML Indication Subscription

vmnic/vmhba sequence changed in ESXi 5.5

Looks like VMware has made a small but momentous change to the vmnic/vmhba numbering with the release of vSphere ESXi 5.5. In previous versions, the vmnic numbering was always determined by the the PCI ID. After adding a new ESXi Host to a Cluster that has been updated from ESXi 5.1 to ESXi 5.5 i noticed that the vmnic numbering was inconsistent although all host were identical. The newly installed host has a different vmnic to PCI ID assignment compared to the hosts that have been updated from ESXi 5.1:

esxi-vmnic-to-pciid-numbering

Read More »vmnic/vmhba sequence changed in ESXi 5.5

Howto Install VMware tools on a virtual ESXi

Running an ESXi as Virtual Machine inside VMware Worksation or on another ESXi gets more and more useful for testing purposes. That installation, also called "Nested ESXi", is not officially supported by VMware but some VMware developers are willing to help in the VMware communities Nested Virtualization forum. Up to this point is was not possible to install VMware Tools on a nested ESXi, making the management a little bit cumbersome. During VMworld 2013 in Barcelona the news about an upcoming Fling called "VMware Tools for Nested ESXi" came out. The Fling contains a small vib package that can be installed on a virtual ESXi Host.

nested-esxi-vmware-tools-0

Read More »Howto Install VMware tools on a virtual ESXi

ESXi 5.5 with PowerPath/VE 5.9 - Inaccessible Local Datastores

After upgrading an ESXi Host to version 5.5 and installing the current multipathing driver from EMC (PowerPath/VE 5.9) I encountered a problem with the local storage. EMC PowerPath claims the local storage and makes it inaccessible. The ESXi is unable to boot after it tried to claim the local devices. It boots one last time after installing the driver but can't access the local VMFS datastore. After a second reboot, an error message "No hypervisor found." is displayed in the VMware Hypervisor Recovery mode. From now on, the ESXi Host does not boot and needs to be reinstalled.

no-hypervisor-found

The main cause for that issue can be found after the first (and last) reboot next to the PowerPath/VE 5.9 installation in /var/log/vmkernel.log:

ALERT: PowerPath:Could not claim path vmhba1:C0:T0:L1. Status : Failure
WARNING: ScsiPath: 4693: Plugin 'PowerPath' had an error (Failure) while claiming path 'vmhba1:C0:T0:L1'. Skipping the path.
ScsiClaimrule: 1362: Plugin PowerPath specified by claimrule 290 was not able to claim path vmhba1:C0:T0:L1. Busy
ScsiClaimrule: 1594: Error claiming path vmhba1:C0:T0:L1. Failure.

Read More »ESXi 5.5 with PowerPath/VE 5.9 - Inaccessible Local Datastores

vCenter and the physical or virtual discussion - vSphere 5.5

Since vSphere 5.1 I have heard many advises that it is better to have a physical vCenter due to its enormous resource requirements. In the last years I had many discussions on that topics and it turned out that most people are just afraid because of this "chicken and egg" situation. Technical arguments are mostly related to dvSwitch issues or resource worries. In the following post I'll cover both sides of the argument.

p2v

Read More »vCenter and the physical or virtual discussion - vSphere 5.5

Upgrade vCenter 5.1 to 5.5 error: "The existing ssl certificate is invalid"

The upgrade from vCenter Server 5.1 to vCenter Server 5.5 (5.5.0 and 5.5.0a) fails during the SSO installation with the following error message:

The existing ssl certificate is invalid

After verifying the certificate i could confirm that it is valid and not expired. After troubleshooting the update log I figured out that the problem was caused by a wrong registry entry. The old 5.1 installation was using an IP address instead of the vCenters FQDN.

Read More »Upgrade vCenter 5.1 to 5.5 error: "The existing ssl certificate is invalid"

Warning 25000 at vCenter 5.5 Update - How to handle?

When you are updating VMware vCenter Server 5.1 to version 5.5 you always get that "Warning 25000" message. This post shows how to check that the certificate is valid, and how to replace a expired certificate

Warning 25000. Please verify that the SSL certificate for your vCenter Single Sign-On 5.1 SSL is not expired. If it did expire, please replace it with a valid certificate before upgrading to vCenter Single Sign-On 5.5.

Read More »Warning 25000 at vCenter 5.5 Update - How to handle?