Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

wsimps01

1 Message

727

January 11th, 2011 11:00

ESX Discovery Issues

I have installed the VMagent and then I select DISCOVER | ASSISTED | ESX SERER in the ControlCenter GUI (v. 6.1.0.8.470-GA).

When I use the VirtualCenter Server option and run the discovery it seems to find all of my ESX Servers without any issues but it will not discover all the the hosts on the servers but it did on only one ESX Server.

I created the same creditenals on a ESX Server re-ran the discovery and it will not discover the host associated with it.

Any suggestions?

I have been told that I must have the same User & ID for the Virtual Center and all of the ESX Servers, is this correct? Do I use one or the other or is both required?

Thanks,

Bill

ConorLawlor

2 Intern

 • 

233 Posts

January 12th, 2011 06:00

Hi Bill,

If the preferred discovery mechanism is via VirtualCenter, then in addition to creating the user at the ESX level, the same user needs to be created in VirtualCenter

Review attached document (ESX_discovery.doc) and the Primus Solution emc165970  "ControlCenter 6.x: How do I set up a user account on my VMware ESX server for use by ControlCenter assisted discovery?"

Pages 1 - 10 shows steps in creating non-root users for ESX Server Discovery

See page 11 of the attached document for the steps required for setting up a user for the VirtualCenter Discovery option to discovery all the ESXS

A)

Ensure that the permissions & user roles are correct for a discovery of the ESXs in ControlCenter per the attached document and emc165970 .

B)

From the VMWare agent host doing the discovery confirm you can connect to the below address's using the fully qualified domain or short hostname of the ESXs in question

http://< >> or < >/mob
https://< >> or < >/mob
http://< >> or < >/sdk
https://< >> or < >/sdk

C)

1. Stop the VMware agents
2. Delete any partially discovered ESX server for the ESXs in question from under the host folder in the left hand tree pane of the ControlCenter console.
3. Remove all VMware related entries for the ESXs or VirtualCenter in question from the Review Progress window under the Discover tab .
4. Restart the VMware agents
5. Kick off a discovery of the ESXs or VirtualCenter depending on the method you use.

D)

If the discovery issue remains open an SR with Support and attach the VMware agent and store.trc files (covering the timeframe of discovery)


From the Vmware agent doing the discovery
 
Log Collection Wizard -- Category: 'All Log Types' -- Subcategory: 'Agents And Related Software' -- Log Type: 'EGV -VMWARE'
%ECC_INSTALL_ROOT%\exec\EGV610\EGV.log
%ECC_INSTALL_ROOT%\exec\EGV610\EGV_Bx.log.gz
%ECC_INSTALL_ROOT%\exec\EGV610\EGV.ini
%ECC_INSTALL_ROOT%\exec\EGV610\EGV_Err.log
%ECC_INSTALL_ROOT%\exec\EGV610\EGV_Bx_Err.log
%ECC_INSTALL_ROOT%\exec\EGV610\EGV_Discovery.log.gz
 
From all the hosts where the ControlCenter Store service is installed:
 
%ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\data\store.trc
%ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\data\store.trc.*.gz
%ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\data\ecc_store.ini

Regards

Conor Lawlor

See the link below for emc165970 - "How do I set up a user account on my VMware ESX server for use by Controlcenter assisted discovery?"

http://knowledgebase.emc.com/emcice/documentDisplay.do?docType=1006&clusterName=DefaultCluster&resultType=5002&groupId=1&page=&docProp=$solution_id&docPropValue=emc165970&passedTitle=null

1 Attachment

Was this post helpful?

View All

No Events found!

Top