Master Agent - ESX 3.5

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

Ok, that's what i was starting to think... new problem then.

We have a test environment that i did that in, with root user.. the host is not coming up... further ideas?

Thanks!
Dane
(the reply to dernsber was a little wierd)

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?

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

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.

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?

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 ?

Great help in the error log huh? That first entry for most (all?) agents seems to have an IP unknown section in it, I ignore them. :-/

The first log looks like the assisted discovery output from the ecc console and it looks like you have good communication with an agent on shqecct1.cablab.corp. On that host is there an EGV_Discovery.log.gz in the EGV600 directory? I'm guessing not yet but if so what does it say? Does the EGV.log file contain any references to 10.99.5.80, assuming that's the ESX server IP address right? Try going to c:\ecc\exec\egv600 on shqecct1.cablab.corp and searching for 10.5.99.80 in all of the files there. You could use windows explorer or try the find command something like this:
find "10.99.5.80" *

If the files have already rolled and zipped find probably can't find them but I doubt there's been much activity so they should still be there.

I'm just trying to get ECC to discover the ESX boxes with the VMWare Agent.

Ran another attempt, here's the output:
SESSION_ACTION: Discover [1] MO Type = Host
ProviderHostName=10.99.5.80 | UserName=eccadmin | Password=******
command status = finished
objects found = 0 agents responding = 1
completed in 5 seconds
action begins at: Thu Oct 02 15:07:33 MDT 2008
action ends at: Thu Oct 02 15:07:38 MDT 2008

Responding agents:
[1] {ID=32336} VMware Agent @ shqecct1.cablab.corp



The error log stated something about IP=" "...

LOG 15:04:36 L I F 992 Log.cxx:739 DATE="2008-10-02" IP=" " VERSION="600" TYPE="EGV"

Thanks again for all the input!

Tazal,

We are planning to monitor the ESX 3.5 servers, as I said, we built a test server. I tried the assisted discovery and the agents are rsponding but no objects found. Went and checked the logs and found

username eccadmin succeeded; login failed

Is anyone aware of how to proceed from here?

Check out emc165970 for full details, it's easier than pasting in here, but basically you need to set up a new user on each ESX box.

Yes, EGV_Discover.log.gq is there, it has a return of a bunch of Jiberish...

the EGV.log file has a LOT of references to 10.99.5.80.. i'm trying to parse through it now for the most recent attempt... and yes that is the IP of the ESX server.

i'll check with them on the "browse datastore" (them being the VMWare admins)