Collect Inventory for ESXi Host Failed 9015

I have a Flex System Enterprise Chassis which have 1 FSM and 3 Compute Node running ESXi 5.5u1. I had created a virtual machine running windows 2008 R2 on one of 3 Node and already installed vCenter Server 5.5 on it. I can discover, access and inventory vCenter Server but after that I cannot see any ESXi host as well as virtual servers at all. Thus I had to run discover, access and inventory individual ESXi host but I had got an issue here that I can discover and access to these ESXi host OK as if I enable SSH service on them. However the problem I want to fix is that I cannot run inventory on these ESXi host, the error message detail is as below. Please kindly hepl me!

We are having the same issue in our lab. I think it could be due to the fact that the CMM has the older version of firmware that will hang and not allow logins after a certain amount of up time. I am currently upgrading the CMM to the latest that another MPS member so kindly referred me to this morning. After that I will try some troubleshooting and reply back.

For now I would try the following:

1. Validate FSM is at 1.3.2 with ALL patches applied2. Validate ESXi hosts are at their latest versions of firmware3. Upgrade CMM to 12PET12Q-2.5.2q4. Rerun inventory

If that doesn't work, try to remove the ESXi hosts from the FSM by right-clicking on each one individual from Chassis Manager and clicking Remove. Then inventory the chassis and after some time the ESXi hosts should reappear and you can try an inventory again.

Thanks for your support. I had updated latest firmware for all components in the chassis one week ago, so now I just need update fw for CMM if it will fix the issue. My FSM is at 1.3.2, however, how to check if it is already ALL patch applied?

It means that if I want to install patch for FSM, I should download all patches release after 20140603 or just download the latest one to use for patching??? Now I can see patch number fsmfix1.3.2.0_IT04332 is the latest one for FSM 1.3.2

Yeap! I had already updated to latest firmware for all components on chassis by manual one week ago (CMM, Node, SW). Next week I will try to up fw for CMM to 2.5.2 and FSM patch as your suggest. Hope after that everything is working fine.

USERID@FSM:~> smcli cleanupd -mva ATKUSC403I Performed cleanup on update "com.ibm.director.base.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.usmi.console.ilog.feature_6.3.2".ATKUSC403I Performed cleanup on update "com.tivoli.twg.legacylibs.feature_6.3.2".ATKUSC403I Performed cleanup on update "com.ibm.director.core.kernel.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.usmi.console.welcome.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.director.mgr.status.server.feature_6.3.5".ATKUSC403I Performed cleanup on update "org.sblim.cim.client.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.director.core.console.ui.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.director.core.console.tasks.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.director.mgr.configuration.server.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.director.core.common.feature_6.3.5".ATKUSC403I Performed cleanup on update "com.ibm.director.mgr.configuration.console.feature_6.3.5.0-20141121-IT04332".ATKUSC403I Performed cleanup on update "fsmfix_com.ibm.director.mgr.configuration.console.feature_6.3.5.0-20141121-IT04332".ATKUSC402I All update files and information for the targeted updates have been cleaned from the update library.

USERID@gvicfsm:~> ssh root@<ESXi IP>The authenticity of host '192.168.240.72 (192.168.240.72)' can't be established.RSA key fingerprint is d4:a3:7b:18:3c:7f:c3:16:2b:c0:f3:bd:4f:cb:6f:8b.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added '192.168.240.72' (RSA) to the list of known hosts.Password:The time and date of this login have been sent to the system logs.

How did you initially configure your FSM? To use separate networks for Data and Management? Or a single network? We have seen this issue before and it turned out to be a misconfiguration of the FSM where the single network was chosen. When this is chosen the FSM cannot manage the OS layer of the nodes because it has no pathway to the external management.

I initial FSM using separate networks for Data and Management, the eth0 has IPv6 enable and can be pingable to IPv6 address of CMM, they are on the same IPv6 subnet and IPv4 disable. The eth1 has Ipv6 disable and Ipv4 enable and has same subnet with OS layer of ESXi host. Could you please advice me if I have something wrong.Now whenever I perform discovery for vCenter or individual ESXi host, I always get this error message and cannot see any things I want:December 8, 2014 11:12:19 PM GMT+07:00-Level:50-MEID:0--MSG: ATKSRV640I Service Location Protocol (SLP) cannot be reached at IP address 10.32.36.116. If the resource is not fully discovered, enable SLP, ensure that Flex System Manager can reach SLP, and rerun discovery.

And now I have another confuse that this issue I am facing due to that I have installed vCenter on virtual machine of ESXi hosts, so that FSM cannot inventory vCenter to see ESXi hosts inside vCenter manage, actually FSM cannot see any Farm object that corresponding to Datacenter object contains ESXi hosts in vCenter, right??? Thus should I install vCenter on an physical machine x86-compatible system instead of installing it on virtual machine of ESXi host (the Flex Compute Node)