This post is more than 5 years old
105 Posts
0
853
January 21st, 2010 13:00
Controlcenter 6.0 and assisted discovery for ESX 4 hosts
We are used to doing assisted discovery on ESX hosts to add them to ECC. We cannot seem to get the ESX 4 hosts to discover but al lthe 3.5 hosts worked fine. Maybe because the VMWARE agent is the latest .568 but that is from OCt 2008 and we see no newer one on Powerlink. It seems to find the host with discovered one and agent responding one but it never appears in the ESX host drop down tree under Hosts.
Any ideas? We realize we need to get to 6.1 this year at some point but need work around for this now.
Scott
No Events found!
ConorLawlor
2 Intern
•
233 Posts
0
January 22nd, 2010 07:00
Hi Scott,
ControlCenter 6.0 does not support the Discovery of ESX 4.0 Servers.
There is no plan to support Discovery of ESX 4.0 at 6.0
ControlCenter 6.1 with the Hotfix 4674 or later versions include support for the discovery of ESX 4.0 (VMWare Agent version 6.1.0.5.223 and above)
Regards
Conor
Allen Ward
4 Operator
•
2.1K Posts
0
March 5th, 2010 12:00
I was just about to start a new thread on this but I thought it would make more sense to just add on the question here for consistency...
With ESX 4.0 (once the VMWare agent is up to 6.1.0.5.223) has anything changed in the setup on the ESX host for discovery? We have a few that have recently been upgraded to ESX 4 and when we try to discover them it's like they aren't there. We have confirmed that the account/password is right and that the permissions/role for the read only account is set correctly (as per the old instructions). I can't find anything quickly in the documentation that shows a change.
Unless you can tell me that something has changed I'll be opening a case with support early next week to investigate.
ConorLawlor
2 Intern
•
233 Posts
0
March 8th, 2010 03:00
H Allen,
With ESX 4.0 (once the VMWare agent is up to 6.1.0.5.223) has anything changed in the setup on the ESX host for discovery? No.
Before opening an SR with support increase the Initial Discovery DCP from the default value of 5 minutes to 45 minutes.
I have seeing similar issues in environments where a large number (such as 25 or more) of VMware ESX Servers are managed by only one ControlCenter VMware Agent. Increasing the Initial Discovery_00 DCP to 45 minutes have resolved these issue and it will have no impact on the environment. This policy will run the initial discovery for any ESX server that ControlCenter knows about but which a full discovery is not completed and will then sends it information to the store which updates the ControlCenter repository.
Try the following procedure:
1) Stop the VMware agents
2) For the ControlCenter VMware Agents, Increase the Initial Discovery DCP from 5 minutes to 45 minutes
3) Inspect the Review Progress tab (Discover > Review Progress > ESX Server) as it contains entries for both Virtual Center and also ESX for the problem server and delete any references.
4) Restart the VMware Agents. Start an Assisted Discovery using the ESX Server tab to discover the previously undiscovered server.
5) See if the Server appears in the Console
If the Initial Discovery DCP is already set to 45 minutes or if the issue remains after following the above steps open an SR and attach the ESX agent logs "%ECC_INSTALL_ROOT%\exec\EGV610\" and Store logs to the SR.
Regards
Conor
Allen Ward
4 Operator
•
2.1K Posts
0
March 8th, 2010 12:00
Thanks Connor, I'll look at increasing the DCP setting to help for the future. We have two agents deployed, but well over 100 ESX servers in our environment. I'm actually looking at deploying a 3rd agent if need be.
This one issue was resolved by harassing the ESX admins to check again to make sure the discovery account was set up properly. They reapplied the settings and suddenly we were able to discover that one.