IBM Support

Flex System Manager (FSM) 1.3.2: Discovery and Inventory of ESXi 5.5 Host May Not Complete Correctly on Discovery of vCenter

 Technote

You should ensure you have followed IBM requirements to manage ESXi 5.5. on Flex System Manager (FSM):



When FSM discover System task is performed against a VMware vCenter 5.5, the FSM will immediately perform an inventory of the vCenter.
The vCenter MEP should report access OK status and have both DCOM and vCenter protocols:

Properties of a vcenter server showing OK.

If DCOM and vCenter protocols do not report or are not unlocking, some of the common problems are as follows:

1. Windows Server firewall
By default DCOM is allowed; however, vCenter is not. Check the rules to allow vCenter.
Review VMware document for required ports
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2051575

2. vCenter is in lockdown mode
If vCenter is in lockdown mode, it cannot be discovered for remote control (disable vCenter lockdown mode).
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008077

Once the vCenter is correctly discovered and unlocked as shown above, it will create a MEP for each
vCenter DataCenter with the same name as defined in vCenter.

From the vCenter MEP, select inventory:

Inventory tab from the mep properties view.

At the bottom of the inventory page, you will see the FARM MEP which represents the vCenter Datacenter:

Inventory data showing the farm mep details.

The Farm (in the example, WaltDC) should open the ESXi host MEP, if ESXi was discovered through the vCenter.
If, however, when the Farm is opened and it only reports details of the object ESXi, it could not be discovered correctly.

Print of a failed ESXi discovery:
General details for the farm MEP

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.
When the FARM is correctly inventoried, clicking on the WaltDC farm will show the ESXi host (x node system name).
It will create a MEP for each ESXi host with the name of the ESXi host (the resolvable name):

Related systems view for the farm mep.

It will create a MEP for each Virtual Server defined on each ESXi host discovered. Selecting the ESXi host will show the inventory of all virtual servers:

Related systems view for all computer systems.

vCenter discovery and inventory may complete without any error reported. Only by reviewing the inventory results will you know if the inventory was complete and valid.

If all Virtual servers have been discovered, you are ready to work with your servers in VMControl.




Product:
Flex System Manager
Release:
1.3.2
Function Area:
Base Director
Subfunctional Area:
General



IBM Systems Management Support Page

    IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.

Document information

More support for: Flex System Manager Node

Version: 1.3.2

Reference #: 714998573

Modified date: 18 December 2017