Solved!
Go to Solution- Is there a Master Agent for ESX?
I'm trying to get our new ESX servers discovered so I
can use the friendly GUI to allocate disk to it, but
i can't find an installer for a Master Agent... any
ideas?
dernsber,
There is no agent to install on the ESX servers themselves. Instead you'll install a VMware Agent on another qualified host. Via the Assisted Discovery process you will provide the credentials for that Agent to discover the ESX server(s) via TCP/IP. Please note that the credentials you use will need to be part of the Admin Group within Virtual Center management application.
Hope that helps,
--Doug - Dane,
We are actually in a holding pattern for discovery of our ESX servers here. We are awaiting the application of updates to the 3.5 ESX environment which fixes a known Pegasus/CIM data provider issue. You will see evidence of this condition in the VMware Agent log files. Apologies that I don't have specific examples that I can share.
Also please look for VMware Agent updates on Powerlink.
--Doug - Ran the patch update, no avail.
Another question... we're using the direct IP instead of actual host-name (no DNS setup in the Test/Dev environment)... could this possible be throwing off the discovery? or the fact that no storage devices are discovered in the test ECC environemtn? seamuscoffey
472 Posts
577
1
Posted October 2nd, 2008 00:00
Hi,
Using the IP address instead of hostname should not be the cause of the issue (both should work fine).
If you're running the latest VMware Agent (6.0.0.0.343) and are still having discovery issues then it might be worth checking Knowledgebase articles emc187145 & emc189211 for possible issues with the ESX Server Pegasus service.
Regards,
Séamus Coffey
EMC Global Services- Ran the patch update, no avail.
Another question... we're using the direct IP instead
of actual host-name (no DNS setup in the Test/Dev
environment)... could this possible be throwing off
the discovery? or the fact that no storage devices
are discovered in the test ECC environemtn?
The discovery should work using an IP address and not having any storage yet shouldn't matter either.
Go to the server you installed your VMware agent on and assuming default locations go to C:\ecc\exec\EGV600 and look at your log files. Your EGV_Err.log file should be very short so take a peek at it first. If that doesn't have anything helpful go to the EGV.log file and look there. It'll be helpful to search on the IP address of the ESX server and look at the messages immediately following that. sriwithfbl
34 Posts
577
0
Posted October 2nd, 2008 09:00
A ESX 3.5 test server is being built in our environment, it will be done by today or tomorrow. I will update this thread on how it goes.- A ESX 3.5 test server is being built in our
environment, it will be done by today or tomorrow. I
will update this thread on how it goes.
We've been successfully monitoring ESX 3.5 boxes for quite some time, is there anything specific you're looking for? sriwithfbl
34 Posts
357
0
Posted October 2nd, 2008 14:00
My case is similar, but my error log is empty. In the logs it shows up as login failed.
I tried to login using my credentials on the webpage of the ESX server and it did not allow me. With Shell it works, so it must be the permissions.
Is this why login is being failed?
Does ECC use the webaccess to login on to ESX server or does it use the shell ?
tazal
59 Posts
876
0
Posted October 2nd, 2008 14:00
logs it shows up as login failed.
I tried to login using my credentials on the webpage
of the ESX server and it did not allow me. With Shell
it works, so it must be the permissions.
Is this why login is being failed?
Does ECC use the webaccess to login on to ESX server
or does it use the shell ?
Are you saying you can log in to the ESX server via ssh using the same login info you're trying to use for discovery? If so it looks like you're close, perhaps you didn't get that ID in to the proper group.
The ecc agent doesn't exactly use webaccess but it does talk directly to the pegasus server. It doesn't require shell access to the ESX box for that login but it does require the permission to "browse datastore"
I can't paste well in here but go find emc165970 and look at it, especially section 2, and I think you'll get it working.