*
News: SMF - Just Installed!


Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

Collect Inventory for ESXi Host Failed 10328

Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Collect Inventory for ESXi Host Failed
« on: December 04, 2014, 02:44:14 AM »
Hi,

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!


December 4, 2014 2:33:10 AM ICT-Level:1-MEID:0--MSG: Job "Collect Inventory - December 4, 2014 2:33:08 AM ICT" activated.
December 4, 2014 2:33:10 AM ICT-Level:200-MEID:0--MSG: Subtask "Collect Inventory" activated.
December 4, 2014 2:33:10 AM ICT-Level:200-MEID:0--MSG: Starting clients
December 4, 2014 2:33:10 AM ICT-Level:100-MEID:0--MSG: Clients started for task "Collect Inventory"
December 4, 2014 2:33:10 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 4, 2014 2:33:10 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 4, 2014 2:33:10 AM ICT-Level:150-MEID:0--MSG: ATKSRV629I Collecting inventory by using inventory profile "All Inventory".
December 4, 2014 2:33:10 AM ICT-Level:150-MEID:163604--MSG: ATKSRV628I Collecting inventory for "10.32.36.114", which has a type of "Operating System".
December 4, 2014 2:33:10 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 4, 2014 2:33:10 AM ICT-Level:100-MEID:163604--MSG: 10.32.36.114 client job status changed to "Active".
December 4, 2014 2:33:14 AM ICT-Level:150-MEID:163604--MSG: ATKSRV642E The "systems.discovery.extended.AgentlessExtendedDiscoveryModule" inventory extension failed for "10.32.36.114", which has a type of "Operating System". Search above for previous related errors, fix each error, and then collect the inventory again.
December 4, 2014 2:33:14 AM ICT-Level:100-MEID:163604--MSG: 10.32.36.114 client job status changed to "Error".
December 4, 2014 2:33:14 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete with errors".
December 4, 2014 2:33:14 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active with errors".


Best Regards,
Bin
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #1 on: December 04, 2014, 03:47:05 PM »
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 applied
2. Validate ESXi hosts are at their latest versions of firmware
3. Upgrade CMM to 12PET12Q-2.5.2q
4. 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.
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #2 on: December 04, 2014, 09:20:24 PM »
Hi,

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?

I'm looking for your reply back with solution offer for this issue.


Best Regards,
Bin
« Last Edit: December 04, 2014, 09:54:20 PM by binhvq »
Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #3 on: December 05, 2014, 01:36:19 AM »
you can use

Liks@FSManager2:~> lsconfig -V
"version= Version: 1
Release: 3
Service Pack: 2
FSM Build level 20140603-0113 2014_154.Tue Jun 3 01:06:845 CDT 2014
 
","base_version=V1R3
"

if you install latest patch

    
fsmfix1.3.2.0_IT04332  for example


feature_6.3.5.0-20141121-IT04332

FSM Build level 20140603-0113 2014_154.Tue Jun 3 01:06:845 CDT 2014

this numerals and date will same how in patch ( Readme.txt )

« Last Edit: December 05, 2014, 01:38:03 AM by Liks »

sorry for eng. not my native
From Russia With Love
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #4 on: December 05, 2014, 02:16:16 AM »
Version of my FSM is the same:
"version= Version: 1
Release: 3
Service Pack: 2
FSM Build level 20140603-0113 2014_154.Tue Jun 3 01:06:845 CDT 2014
 
","base_version=V1R3
"

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

Regards,
Bin
Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #5 on: December 05, 2014, 04:51:09 AM »
read readme this is important

and section Prerequisites and corequisites

for you now step this

Download:

FSMAppliancefixPackage-1-3-2-1.zip
fsmfix_1.3.2.0_IT04332.zip

1. install fsmfix_1.3.2.0_IT04332.zip
2. install FSMAppliancefixPackage-1-3-2-1.zip

For step 2.
The fix, 'fsmfix1.3.2.0_IT04332' should be installed with this fix package.  It can be installed before or after
this fix package.


PS dont forget

12PET12Q-2.5.2q for CMM

i think when big update FSM or CMM need update all modules Chassis node\switch etc. ( up to date )

you can this via FSM or manual

i like this do manual =)
« Last Edit: December 05, 2014, 04:56:01 AM by Liks »

sorry for eng. not my native
From Russia With Love
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #6 on: December 05, 2014, 09:26:54 AM »
Hi Liks,

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.

Regards,
Bin
Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #7 on: December 05, 2014, 09:57:48 AM »
Fix
USERID@FSM:~> smcli cleanupd -mva
ATKUSC402I All update files and information for the targeted updates have been cleaned from the update library.
USERID@FSM:~> smcli cleanupd -mFv -P "Platform='Director' OR Platform='DirectorAppliance'"
ATKUSC261W Warning: no updates found that match the target options.
ATKUSC402I All update files and information for the targeted updates have been cleaned from the update library.
USERID@FSM:~> smcli collectinv -p "All Inventory" -i 10.3.0.1,10.3.0.2 -t OperatingSystem
Inventory collection percentage 0%
Inventory collection percentage 19%
Inventory collection percentage 74%
Inventory collection percentage 82%
Inventory collection percentage 88%
Inventory collection percentage 90%
Inventory collection completed:
100%
USERID@FSM:~> smcli installneeded -v -F /home/USERID/fsmfix_1.3.2.0_IT04332.zip
ATKUPD727I The update install task has finished successfully.
ATKUPD288I The install needed updates task has completed successfully.

FixPack

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@FSM:~> smcli collectinv -p "All Inventory" -i 10.3.0.1,10.3.0.2 -t OperatingSystem
Inventory collection percentage 0%
Inventory collection percentage 66%
Inventory collection percentage 82%
Inventory collection percentage 90%
Inventory collection completed:
100%
Inventory collection percentage 66%
Inventory collection percentage 82%
Inventory collection percentage 90%
Inventory collection completed:
100%

USERID@FSM:~> smcli installneeded -v -F /home/USERID/FSMApplianceFixPackage-1-3-2-1.zip
ATKUPD489I Collecting inventory for one or more systems.
ATKUSC216I Extracting file "/home/USERID/FSMApplianceFixPackage-1-3-2-1.zip" for import.
...
ATKUPD727I The update install task has finished successfully.
ATKUPD288I The install needed updates task has completed successfully.

smshutdown -r -t now

in fix pack, latest update for dsa imm and other

USERID@FSM:~> lsconfig -V
"version= Version: 1
Release: 3
Service Pack: 2.1
FSM Build level 20141115-1310.Sat Nov 15 13:10:02 CST 2014
« Last Edit: December 05, 2014, 10:11:59 AM by Liks »

sorry for eng. not my native
From Russia With Love
Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #8 on: December 05, 2014, 09:58:09 AM »
now you can upgrade u1 -> u2 too if needed ( customized ESXI )

but need reboot ESXI


sorry for eng. not my native
From Russia With Love
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #9 on: December 05, 2014, 01:24:06 PM »
Binhvq,

I was able to successfully inventory my esxi hosts and my vCenter server after the CMM update. Now I am seeing my ESXi hosts as virtual servers.

Let us know what you find out after your upgrades.

thanks!
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #10 on: December 08, 2014, 02:27:57 AM »
Hi,

Today I have applied your suggestion that:
1. Validate FSM is at 1.3.2 with ALL patches applied----------> DONE
2. Validate ESXi hosts are at their latest versions of firmware ----------> DONE
3. Upgrade CMM to 12PET12Q-2.5.2q--------->DONE
4. Rerun inventory------->DONE

But I am still having this issue. I can discover, access and inventory vCenter Server but after that I cannot see any ESXi host as well as virtual servers inside at all.

I have also tried to remove the ESXi hosts from the FSM then inventory the chassis and after that the issue still exists.


Here is some error messages:
1. Discover vCenter
December 9, 2014 3:20:55 AM ICT-Level:1-MEID:0--MSG: Job "System Discovery - 10.32.36.44 - December 9, 2014 3:20:55 AM GMT+07:00" activated.
December 9, 2014 3:20:55 AM ICT-Level:200-MEID:0--MSG: Subtask "System Discovery" activated.
December 9, 2014 3:20:55 AM ICT-Level:200-MEID:0--MSG: No clients to start.
December 9, 2014 3:20:55 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 3:20:55 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 9, 2014 3:20:55 AM ICT-Level:150-MEID:330228--MSG: ATKSRV617I System or resource "10.32.36.44" of type "Operating System" was discovered previously at the specified location or locations.
December 9, 2014 3:20:55 AM ICT-Level:150-MEID:330244--MSG: ATKSRV617I System or resource "Vcenter 10.32.36.44" of type "Virtual Server" was discovered previously at the specified location or locations.
December 9, 2014 3:20:55 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Starting".
December 9, 2014 3:20:55 AM ICT-Level:150-MEID:0--MSG: ATKSRV623I Starting the discovery process for all resource types for IP address or range "10.32.36.44".
December 9, 2014 3:20:55 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 3:21:26 AM ICT-Level:50-MEID:0--MSG: ATKSRV640I Service Location Protocol (SLP) cannot be reached at IP address 10.32.36.44. If the resource is not fully discovered, enable SLP, ensure that Flex System Manager can reach SLP, and rerun discovery.
December 9, 2014 3:21:31 AM ICT-Level:150-MEID:0--MSG: ATKSRV616I Discovered 0 new systems.
December 9, 2014 3:21:31 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
December 9, 2014 3:21:31 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Complete".



2. Collect inventory for vCenter log:
December 9, 2014 2:16:51 AM ICT-Level:1-MEID:0--MSG: Job "Collect Inventory - December 9, 2014 2:16:48 AM ICT" activated.
December 9, 2014 2:16:51 AM ICT-Level:200-MEID:0--MSG: Subtask "Collect Inventory" activated.
December 9, 2014 2:16:51 AM ICT-Level:200-MEID:0--MSG: Starting clients
December 9, 2014 2:16:51 AM ICT-Level:100-MEID:0--MSG: Clients started for task "Collect Inventory"
December 9, 2014 2:16:51 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 2:16:51 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 9, 2014 2:16:51 AM ICT-Level:150-MEID:0--MSG: ATKSRV629I Collecting inventory by using inventory profile "All Inventory".
December 9, 2014 2:16:51 AM ICT-Level:150-MEID:330228--MSG: ATKSRV628I Collecting inventory for "10.32.36.44", which has a type of "Operating System".
December 9, 2014 2:16:51 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 2:16:51 AM ICT-Level:100-MEID:330228--MSG: 10.32.36.44 client job status changed to "Active".
December 9, 2014 2:17:22 AM ICT-Level:100-MEID:330228--MSG: 10.32.36.44 client job status changed to "Complete".
December 9, 2014 2:17:22 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
December 9, 2014 2:17:22 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Complete".


3. Discover each individual ESXi host
December 9, 2014 2:39:46 AM ICT-Level:1-MEID:0--MSG: Job "System Discovery - 10.32.36.115 - December 9, 2014 2:39:46 AM GMT+07:00" activated.
December 9, 2014 2:39:46 AM ICT-Level:200-MEID:0--MSG: Subtask "System Discovery" activated.
December 9, 2014 2:39:46 AM ICT-Level:200-MEID:0--MSG: No clients to start.
December 9, 2014 2:39:46 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 2:39:46 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 9, 2014 2:39:46 AM ICT-Level:150-MEID:220750--MSG: ATKSRV617I System or resource "10.32.36.115" of type "Operating System" was discovered previously at the specified location or locations.
December 9, 2014 2:39:46 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Starting".
December 9, 2014 2:39:46 AM ICT-Level:150-MEID:0--MSG: ATKSRV623I Starting the discovery process for all resource types for IP address or range "10.32.36.115".
December 9, 2014 2:39:46 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 2:40:22 AM ICT-Level:50-MEID:0--MSG: ATKSRV640I Service Location Protocol (SLP) cannot be reached at IP address 10.32.36.115. If the resource is not fully discovered, enable SLP, ensure that Flex System Manager can reach SLP, and rerun discovery.
December 9, 2014 2:40:27 AM ICT-Level:150-MEID:0--MSG: ATKSRV616I Discovered 0 new systems.
December 9, 2014 2:40:27 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
December 9, 2014 2:40:27 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Complete".


4. Collect inventory for  each individual ESXi host if SSH on ESXi host is disable
December 9, 2014 1:34:20 AM ICT-Level:200-MEID:0--MSG: Starting clients
December 9, 2014 1:34:20 AM ICT-Level:100-MEID:0--MSG: Clients started for task "Collect Inventory"
December 9, 2014 1:34:20 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 1:34:20 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 9, 2014 1:34:20 AM ICT-Level:150-MEID:0--MSG: ATKSRV629I Collecting inventory by using inventory profile "All Inventory".
December 9, 2014 1:34:20 AM ICT-Level:150-MEID:163604--MSG: ATKSRV628I Collecting inventory for "10.32.36.114", which has a type of "Operating System".
December 9, 2014 1:34:20 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 1:34:20 AM ICT-Level:100-MEID:163604--MSG: 10.32.36.114 client job status changed to "Active".
December 9, 2014 1:34:20 AM ICT-Level:150-MEID:163604--MSG: ATKSRV631E The secure shell (SSH) connection for managed resource "10.32.36.114" was not initialized. The reported inventory data might be incomplete. Verify the SSH connection between the management server and the managed resource. Next, collect the inventory again.
December 9, 2014 1:34:20 AM ICT-Level:150-MEID:163604--MSG: ATKSRV642E The "systems.discovery.extended.AgentlessExtendedDiscoveryModule" inventory extension failed for "10.32.36.114", which has a type of "Operating System". Search above for previous related errors, fix each error, and then collect the inventory again.
December 9, 2014 1:34:20 AM ICT-Level:100-MEID:163604--MSG: 10.32.36.114 client job status changed to "Error".
December 9, 2014 1:34:20 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete with errors".
December 9, 2014 1:34:20 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active with errors".
December 9, 2014 1:34:21 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Complete with errors".


5. Collect inventory for each individual ESXi host if SSH on ESXi host is enable
December 9, 2014 2:25:27 AM ICT-Level:1-MEID:0--MSG: Job "Collect Inventory - December 9, 2014 2:25:25 AM ICT" activated.
December 9, 2014 2:25:27 AM ICT-Level:200-MEID:0--MSG: Subtask "Collect Inventory" activated.
December 9, 2014 2:25:27 AM ICT-Level:200-MEID:0--MSG: Starting clients
December 9, 2014 2:25:27 AM ICT-Level:100-MEID:0--MSG: Clients started for task "Collect Inventory"
December 9, 2014 2:25:27 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 2:25:27 AM ICT-Level:150-MEID:0--MSG: ATKSRV629I Collecting inventory by using inventory profile "All Inventory".
December 9, 2014 2:25:27 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 9, 2014 2:25:27 AM ICT-Level:150-MEID:163604--MSG: ATKSRV628I Collecting inventory for "10.32.36.114", which has a type of "Operating System".
December 9, 2014 2:25:27 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 2:25:27 AM ICT-Level:100-MEID:163604--MSG: 10.32.36.114 client job status changed to "Active".
December 9, 2014 2:25:30 AM ICT-Level:150-MEID:163604--MSG: ATKSRV642E The "systems.discovery.extended.AgentlessExtendedDiscoveryModule" inventory extension failed for "10.32.36.114", which has a type of "Operating System". Search above for previous related errors, fix each error, and then collect the inventory again.
December 9, 2014 2:25:30 AM ICT-Level:100-MEID:163604--MSG: 10.32.36.114 client job status changed to "Error".
December 9, 2014 2:25:30 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete with errors".
December 9, 2014 2:25:30 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active with errors".
December 9, 2014 2:25:30 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Complete with errors".
« Last Edit: December 08, 2014, 05:48:46 AM by binhvq »
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #11 on: December 08, 2014, 09:58:39 AM »
Binhvg,

Try to login to the FSM via SSH and SSH to your ESXi hosts.

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)? yes
Warning: 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.

VMware offers supported, powerful system administration tools.  Please
see www.vmware.com/go/sysadmintools for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ #
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #12 on: December 08, 2014, 11:47:13 AM »
Hi,

I have tried to login to the FSM via SSH and SSH to your ESXi hosts but the issue still persist.

1. Discover ESXi host
December 8, 2014 11:11:47 PM GMT+07:00-Level:1-MEID:0--MSG: Job "System Discovery - 10.32.36.116 - December 8, 2014 11:11:47 PM GMT+07:00" activated.
December 8, 2014 11:11:47 PM GMT+07:00-Level:200-MEID:0--MSG: Subtask "System Discovery" activated.
December 8, 2014 11:11:47 PM GMT+07:00-Level:200-MEID:0--MSG: No clients to start.
December 8, 2014 11:11:47 PM GMT+07:00-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 8, 2014 11:11:47 PM GMT+07:00-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 8, 2014 11:11:47 PM GMT+07:00-Level:150-MEID:255806--MSG: ATKSRV617I System or resource "10.32.36.116" of type "Operating System" was discovered previously at the specified location or locations.
December 8, 2014 11:11:47 PM GMT+07:00-Level:200-MEID:0--MSG: Subtask activation status changed to "Starting".
December 8, 2014 11:11:47 PM GMT+07:00-Level:150-MEID:0--MSG: ATKSRV623I Starting the discovery process for all resource types for IP address or range "10.32.36.116".
December 8, 2014 11:11:47 PM GMT+07:00-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
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.
December 8, 2014 11:12:24 PM GMT+07:00-Level:150-MEID:0--MSG: ATKSRV616I Discovered 0 new systems.
December 8, 2014 11:12:24 PM GMT+07:00-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
December 8, 2014 11:12:24 PM GMT+07:00-Level:1-MEID:0--MSG: Job activation status changed to "Complete".
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #13 on: December 08, 2014, 02:22:47 PM »
Binhvg,

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.
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #14 on: December 08, 2014, 07:27:18 PM »
Hi,

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)???


Thanks,
Bin
« Last Edit: December 09, 2014, 05:56:25 AM by binhvq »