*
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 9641

Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #15 on: December 09, 2014, 04:15:52 AM »
ESXI custom? from IBM ( Lenovo )

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 #16 on: December 09, 2014, 04:28:21 AM »
http://www-01.ibm.com/support/docview.wss?uid=nas71846c48b1342eea686257d2b0071b467

soon i installing vCenter too and post how it's work for me

but i can discover my host maunal and work properly

December 9, 2014 1:23:00 PM MSK-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 9, 2014 1:23:10 PM MSK-Level:150-MEID:113774--MSG: ATKSRV615I Discovered new system or resource


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 #17 on: December 09, 2014, 09:37:18 AM »
Hi Liks,

I use IBM ESXi Custom 5.5u1 for 3 Compute Node, then I created and install virtual machine running Win2K8 R2 and installed vCenter Window based on this virtual machine. Moreover my ESXi hosts have not yet joined AD domain. So Do your vCenter install on virtual machine inside your Compute Node or on physical machine outside???

Regards,
Bin
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #18 on: December 09, 2014, 10:18:51 AM »
The vCenter server can be a physical machine outside of the cluster or within it. From the FSM side it doesn't matter.
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #19 on: December 09, 2014, 10:41:08 AM »
Hi,

If so should I install any common agent on vCenter host in order to FSM be able to see and inventory vCenter and list out the esxi hosts?? In additional, do these esxi hosts and vcenter host need to join to AD domain???

Finally I'm trying to find out what reason leads to FSM cannot discover vCenter or ESXi host properly. What dose this message mean?: Service Location Protocol (SLP) cannot be reached at IP address x.x.x.x??? I can check and see clearly protocol: vCenter, DCOM is OK, CIM SLP on ESXi is running OK, FSM can ssh to those ESXi hosts...., so WHY?

Regards,
Bin
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

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

I have just found that the virtual machine that running Win2K8 and be installed vCenter on it do need to install Flex Common Agent for Windows. The fact that after I finished installing common agent, re-run inventory for vCenter, FSM now can see and list out the 2 Farm object in Related System that corresponding to Datacenter and Cluster object in vCenter but it only reports details of the object ESXi(ESXi host count, number of virtual machine), it could not be discovered correctly. I found this link http://www-01.ibm.com/support/docview.wss?uid=nas71846c48b1342eea686257d2b0071b467 but I still fix the new issue.

So now for me, the first issue about discovering and inventoring vCenter is fixed, but now I'm facing with new issue that I can not see the ESXi hosts and virtual machine when I click on the Farm object. Anyone can help me!

Here is the message for discovering and inventory vCenter at present:
December 10, 2014 12:30:48 AM ICT-Level:1-MEID:0--MSG: Job "Collect Inventory - December 10, 2014 12:30:42 AM ICT" activated.
December 10, 2014 12:30:48 AM ICT-Level:200-MEID:0--MSG: Subtask "Collect Inventory" activated.
December 10, 2014 12:30:48 AM ICT-Level:200-MEID:0--MSG: Starting clients
December 10, 2014 12:30:48 AM ICT-Level:100-MEID:0--MSG: Clients started for task "Collect Inventory"
December 10, 2014 12:30:48 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 10, 2014 12:30:48 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Active".
December 10, 2014 12:30:48 AM ICT-Level:150-MEID:0--MSG: ATKSRV629I Collecting inventory by using inventory profile "All Inventory".
December 10, 2014 12:30:48 AM ICT-Level:150-MEID:40424--MSG: ATKSRV628I Collecting inventory for "10.32.36.44", which has a type of "Operating System".
December 10, 2014 12:30:48 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
December 10, 2014 12:30:48 AM ICT-Level:100-MEID:40424--MSG: 10.32.36.44 client job status changed to "Active".
December 10, 2014 12:30:49 AM ICT-Level:150-MEID:40424--MSG: DNZVMK114I Getting the OS and Server objects for inventory
December 10, 2014 12:30:49 AM ICT-Level:150-MEID:40424--MSG: DNZVMK115I Updating agent information.
December 10, 2014 12:30:49 AM ICT-Level:150-MEID:40424--MSG: DNZVMK116I Updating Service Access Points.
December 10, 2014 12:30:49 AM ICT-Level:150-MEID:40424--MSG: DNZVMK110I Retrieving farms for VC system.
December 10, 2014 12:30:51 AM ICT-Level:150-MEID:40424--MSG: DNZVMK112I Farm list retrieved, updating farm information
December 10, 2014 12:30:52 AM ICT-Level:150-MEID:40424--MSG: DNZVMK113I Updating farm Relationships.

December 10, 2014 12:33:48 AM ICT-Level:100-MEID:40424--MSG: VCENTER.vpbs.com.vn client job status changed to "Complete".
December 10, 2014 12:33:48 AM ICT-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
December 10, 2014 12:33:48 AM ICT-Level:1-MEID:0--MSG: Job activation status changed to "Complete".

Regards,
Bin
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #21 on: December 09, 2014, 02:38:13 PM »
From the link you sent it looks like you are having the same issue described at the bottom of the document. Have you tried the following?

PER IBM:

This means the ESXi host could not be inventoried by the FSM. Common problems to resolve this issue include the following:

1.  ESXi firewall - by default SLP and CIM ports are NOT open on the ESXi firewall.
        VMware has documented how to alter the firewall rules rather than disabling.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008226

In Step 4, the SLP and CIM task port would be set as below (CIM port listed in red for example):

<service id="0032">
<id>DNSTCPOut</id>
<rule id='0000'>
<direction>outbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>5989 </port>
</rule>
<enabled>true</enabled>
<required>false</required>
</service>
2. SLP is not functioning on the ESXi host.

SSH must be enabled to run these commands. SSH can be disabled when complete:

o /etc/init.d/sfcbd-watchdog stop

o /etc/init.d/sfcbd-watchdog start

o /etc/init.d/slpd restart
3.   Inventory the vCenter host.

After recovery from common problems, the vCenter MEP must be inventoried again.
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #22 on: December 09, 2014, 08:43:59 PM »
Hi

Actually I had found this link before, I have also followed it but not succeed and the fact that I did turn off the firewall already on ESXi host. I think I should also install common agent on ESXi host but now flex common agent 6.3.5 just support window, linux only, it no longer supported for ESXi 5.0 and later, not as the same as flex common agent 6.2.1 can be able to support ESXi 4.0. I have tried following this link http://pelicanohintsandtips.wordpress.com/2010/03/22/installing-ibm-systems-director-6-1-1-common-on-agent-on-esx-4-0/ but no lucky because now the latest System Drirector agent 6.3.5 does not contain .sh script to install agent for ESXi 5.5. I'm feeling not well about FSM :D

P/S: One strange thing, now I can see one virtual machine running CentOS on one of ESXi host on FSM Explorer that I have just created, and FSM Explorer can show some hardware status event log such as: poweron ,off, create virtual machine. Discovering individual ESXi host still shows error message SLP can not be reached and inventorying individual ESXi host still shows error message The "systems.discovery.extended.AgentlessExtendedDiscoveryModule". Thus I'm sure ESXi host need to be install common agent to be discovered and inventoried by FSM. Maybe I should try to open ticket support with IBM for more help.

Regards,
Bin
« Last Edit: December 10, 2014, 05:24:25 AM by binhvq »
Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #23 on: December 10, 2014, 05:58:00 AM »
For Me

1. Have ipv4 configuration for FSM and other component ( but really dont metter )
2. Disable manual all ipv6 statless address where i can ( but really dont metter, if you disable ipv6 for FSM, FSM anyway configure statless address )
3. View in all modules, all modules need correctly discovering without SLP problem Switch\CMM etc
4. in EN4093R create vlan "x"
5. Place internal port to vlan "x"
6. Install ESXI
7. for VMkernel assign Ip addr in vlan "x"
8. vlan "x" and vlan ( network ) where placed FSM can be different
9. Ping from FSM ESXI host
10. ping from ESXI to FSM

now

1. i can discover single ESXI host via FSM without trouble ( in cuztomize esxi preinstalling platform agent ) i see 1 platform agent system

11. installing vCenter into ESXI Host "Guest OS"
12. Configuring vCenter and disable windows firewall
13. install agent windows
14. FSM himself FOUND vcenter on my node but "partial access"
15. i reconfigure access to my vCenter
16. in one moment i see all my ESXI host on other NODE

work properly for me

i have trouble from SLP in past, i think bad configuring network settings
« Last Edit: December 10, 2014, 06:08:34 AM by Liks »

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 #24 on: December 10, 2014, 11:05:26 AM »
Liks,

Thanks for your input hopefully this will resolve it!

Binvgh,

In regards to your common agent question, I do not believe the common agent needs to be installed on ESXi because the IBM Customized version should have all of the hooks into ESXi that the FSM should need. The vCenter agent does need to be installed I believe but its my understanding that this is done automatically once it is discovered and successfully inventoried.

If you are still have issues after you try what Liks suggested then I would definetely open a ticket with IBM and we can keep troubleshooting while they do some debugging. When they have a resolution please post their resolution if you wouldn't mind. :)

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

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #25 on: December 10, 2014, 12:11:14 PM »
Hi Liks,

Thank you for your sharing information. Please let me know what your version of ESXi is, what agent are you using for virtual machine window.

Here is mine:
1. Have ipv4 configuration for FSM and other component ( but really dont metter )----> I setup eth1 same vlan with VMkernel
2. Disable manual all ipv6 statless address where i can ( but really dont metter, if you disable ipv6 for FSM, FSM anyway configure statless address )
3. View in all modules, all modules need correctly discovering without SLP problem Switch\CMM etc -----> OK DONE
4. in EN4093R create vlan "x"----> Mine is EN2092, I created vlan 2
5. Place internal port to vlan "x" ----> Place INTA1 (port of FSM) mode access to vlan 2
6. Install ESXI--------> I use boot via SAN (External V7000)
7. for VMkernel assign Ip addr in vlan "x"-----> Place VMkernel to vlan 2
8. vlan "x" and vlan ( network ) where placed FSM can be different
9. Ping from FSM ESXI host-------> OK DONE
10. ping from ESXI to FSM------> OK DONE

11. installing vCenter into ESXI Host "Guest OS"--------> Installed guest OS into ESXi host, then install vCenter
12. Configuring vCenter and disable windows firewall-----> DONE
13. install agent windows --------> Install System Director Common Agent for Window 6.3.5, now I have protocol: CIM, CAS, DCOM, vCenter after discover vCenter
14. FSM himself FOUND vcenter on my node but "partial access"-----> FSM access vCenter OK
15. i reconfigure access to my vCenter ---->OK
16. in one moment i see all my ESXI host on other NODE-----> After inventory finished, I just see Farm object that corresponding to Datacenter and Cluster on vCenter, click on them but it loops and cannot see any ESXi hosts

Here is my EN2092 configuration, could you please review if something wrong, thanks in advance.
interface port INTA1
   switchport access vlan 2
   exit
!
interface port INTA2
   switchport mode trunk
   switchport trunk allowed vlan 1-3,10
   exit
!
interface port INTA3
   switchport mode trunk
   switchport trunk allowed vlan 1-3,10
   exit
!
interface port INTA4
   switchport mode trunk
   switchport trunk allowed vlan 1-3,10
   exit
!
interface port EXT1
   switchport mode trunk
   switchport trunk allowed vlan 1-2
   exit
!
interface port EXT2
   switchport mode trunk
   switchport trunk allowed vlan 1-2
   exit
!
interface port EXT3
   switchport mode trunk
   switchport trunk allowed vlan 1,3
   exit
!
interface port EXT4
   switchport mode trunk
   switchport trunk allowed vlan 1,3
   exit
!
vlan 2
   name "VLAN 2"
!
vlan 3
   name "VLAN 3"
!
vlan 10
   name "VLAN 10"
!
!
spanning-tree stp 2 vlan 2
!
spanning-tree stp 3 vlan 3
!
spanning-tree stp 10 vlan 10
!
!
interface port EXT1
   lacp mode active
   lacp key 14
!
interface port EXT2
   lacp mode active
   lacp key 14
!
interface port EXT3
   lacp mode active
   lacp key 15
!
interface port EXT4
   lacp mode active
   lacp key 15
!
failover enable
failover trigger 1 limit 2
failover trigger 1 mmon monitor member EXT1-EXT4
failover trigger 1 mmon control member INTA1-INTA4
failover trigger 1 enable

Regards,
Bin
« Last Edit: December 11, 2014, 06:36:27 AM by Bin »
Super Newbie Posts: 14 Karma: +0/-0 *

Bin

*
Re: Collect Inventory for ESXi Host Failed
« Reply #26 on: December 11, 2014, 03:08:54 AM »
Hi,

I have review OS supported by FSM and found that:
Standard VMware vSphere and IBM customized VMware vSphere, version 5.0, 5.1 and 5.5; all under the control of VMware vCenter.
Note: Standard VMware vSphere and IBM customized VMware vSphere are supported on agentless managed systems. IBM customized VMware vSphere offers in-band alerting of hardware events-------> So OK it no longer need flex common agent on version ESXi 5.0 and later, just need on vCenter host window based

Apply standard VMware vSphere and IBM customized VMware ESXi, version 5.0, 5.0 updates 1, 2, and 3; version 5.1, 5.1 updates 1 and 2; version 5.5, updates 1 and 2 with IBM customization patch version 1.1 or later for each compute node that is running the IBM customized image -------> I had already applied this patch for ESXi, even patching FSM and updating firmware for all components on chassis

So now for me, two considerations I think it is the cause:
1. Networking: I have just read some vlan overview for flex system and found that port INTA can be in mode vlan tagged, trunk, however, port EXT uplink should be untagged, access mode, not trunk ----> I will try re-config EXT port if possible because our system is running on production :D
2. I dont deploy ESXi by FSM, instead of that I boot it from SAN and use IMM console to install IBM custom 5.5u1, so that I think by using this method, maybe FSM is not able to load some agent or module during deployment OS for and to connect to ESXi host properly after finishing. ------> This consider can be a clue but I think the possibility is a quite bit.

Best Regards,
Bin
« Last Edit: December 12, 2014, 01:30:40 AM by Bin »
Administrator Sr. Member Posts: 309 Karma: +6/-0 *****
Re: Collect Inventory for ESXi Host Failed
« Reply #27 on: December 12, 2014, 11:29:11 AM »
Bin,

Great info! Keep us posted on your results!
Jr. Member Posts: 97 Karma: +0/-0 **
Re: Collect Inventory for ESXi Host Failed
« Reply #28 on: December 13, 2014, 07:56:35 AM »
yo yo

internal interface in default use tagged mode

only what you need configure on internal interface

switchport mode trunk
switchport trunk allowed vlan x,x,x,x
switchport trunk native vlan 1 ( default ) you can't see this in configuration



« Last Edit: December 13, 2014, 08:12:06 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 #29 on: December 13, 2014, 08:11:06 AM »
for your question for SLP this is absolutly problem with network, but when i begin configure FSM i don't know anything about IBMFlexSystem or his modules

http://mypuresupport.org/PureSystemsForum/index.php?topic=73.msg269#msg269

when i have trouble with SLP i am uninstall all system =) and start reading manuals for switch and FSM after begin install again and work properly for me now

now i know

1. configure lacp from bladenetwork and external switch, verify link aggregation work proprely
2. Create vlan on bladenetwork and external switch ( if you configure through nos, dont forget enable vlan )
3. this is critical sure vlan must be create everywhere
4. cuz i ciscoguy i use iscli
place all internal port and external port
1. in trunk
2. add all vlan ( if you have security reason, can add specify vlan, but very carefull! add native vlan 1 or create another native vlan )

for sample only
conf t
vlan 4001 - native
vlan x - for VMkernel and FSM
vlan y - vlan for DMZ
vlan z - for FileServer

interface INT1 -> ESXI
switchport mode trunk
switchport trunk allowed vlan 4001,x,y ( where x vlan for VMKernel and Y for Server )
switchport trunk native vlan 4001

you have security cuz disabled vlan 1, and place specific vlan in port for server and Vmkernel

interface INT2 -> ESXI
switchport mode trunk
switchport trunk allowed vlan 4001,x,z ( where x vlan for VMKernel and Z for Server )
switchport trunk native vlan 4001

interface INT13 -> FSM
switchport mode access
switchport access vlan x

ALL EXT interface
switchport mode trunk
switchport trunk allowed vlan 4001,x,z,y
switchport trunk native vlan 4001
+ configuration ethchannel

i think if you all done, you dont have problem with network
« Last Edit: December 22, 2014, 06:57:22 AM by Liks »

sorry for eng. not my native
From Russia With Love