Bingo! VPXA appears to be the issue. Thanks very much guys
2008/10/3 NTSysAdmin <[EMAIL PROTECTED]> > Try: > > 1. Log in to the ESX Server service console as root. > 2. Type service vmware-vpxa stop and press Enter. > 3. Type /opt/vmware/vpxa/vpx/init_vpxa.sh and press Enter > > S > > > > *From:* James Rankin [mailto:[EMAIL PROTECTED] > *Sent:* Friday, October 03, 2008 8:16 AM > *To:* NT System Admin Issues > *Subject:* Re: Virtual Center query > > > > ESX 3.5. Tried *service mgmt-vmware restart* and made no difference. > > 2008/10/3 NTSysAdmin <[EMAIL PROTECTED]> > > What version of ESX.. > > > > Quick fix is to restart the management service on the esx server. > > > > S > > > > *From:* James Rankin [mailto:[EMAIL PROTECTED] > *Sent:* Friday, October 03, 2008 6:39 AM > *To:* NT System Admin Issues > *Subject:* Virtual Center query > > > > Does anybody have any idea why sometimes some of my ESX servers show as not > responding in VirtualCenter, and the guests running on it show as > disconnected? The guests themselves are still up and running fine, but they > won't respond to VirtualCenter commands (all the options are greyed out). > The only way to get around this seems to be shut down all the guests on the > affected server, and then restart the ESX server - not really an option when > my Exchange, Excalibur and SQL servers are running on this particular ESX > box. If ESX was Windows, I guess I'd be looking for a failed service or > something, but being a bit of a Unix/ESX amateur I'm not sure where to start > troubleshooting.... > > TIA, > > > > JRR > > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
