SOME VMS SHOWING 0 MEMORY AND 0 CPU

In these case


1.Vmotion all vms  from the affected ESXI host

2.Restart management services in Hosts





From the SSH:

putty to the esxi host

/etc/init.d/hostd restart
/etc/init.d/vpxa restart

From the Direct Console User Interface (DCUI):

1. Connect to the console of your ESXi host.
2. Press F2 to customize the system.
3. Log in as root.
4. Use the Up/Down arrows to navigate to Restart Management Agents.
   
   Note: In ESXi 4.1 and ESXi 5.0, 5.1, 5.5 and 6.0 this option is available under Troubleshooting Options.
   
5. Press Enter.
6. Press F11 to restart the services.
7. When the service restarts, press Enter.
8. Press Esc to log out of the system.

Cheers...

wait for oracle ldom

PROBLEM WITH VCENTER 5.5 WINDOWS



one of my customer faced a problem of

1.when vcenter server is logged on its showing zero inventory with the message

   "Could not connect to one or more vCenter Server Systems:https://vCenterFQDN:443/sdk"


    and some time showing the inventory

2.The Vcenter login get disconnected frequently leading to unable to connect to Vcenter server for sometime


Troubleshooting steps done

1.DNS forward and reverse lookup checked
2.When the odbc connection to sql database
3.Checked whether firewall is on in the vcenter server.
4.Restarted the vcenter server services
5.Checked the ports
6.Checked for duplicate vcenter server instance by below article

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2050273

**Make sure you are unregistering only vcenter service.In my case there was no duplicate instance

7.I saw many errors in the vpxd log as

Failed to add LDAP entry cn=d6cc6fd2-bb66-4fe9-9892-4a3a0c93b91d,ou=Instances,dc=virtualcenter,dc=vmware,dc=int: 0×68 


but before going to do the steps mentioned in the article our issue resolved.


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2044680



Solution

1.Every vcenter server have a default domain for SSO called vsphere.local.In my case customer dont know the password.so we go for  resetting administrator@vsphere.local username using below article


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2034608

after logging using administrator@vsphere.local.we are able to find inventory objects are not lost .



2. Then we checked the windows event manager where we found even though in the services.msc vcenter services are running. In the event viewer we saw many error related to vpxd service like
Fault Module Name: ntdll.dll

Then as per the article 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2076054

we added <ThreadStackSizeKb>1024</ThreadStackSizeKb> which was not there in vpxd.cfg file


After that we started the vcenter services and now the second issue of frequent Vcenter access issue resolved.


But I asked customer to keep monitoring for some days.If its works fine You guyz can follow .

note:

**Even though vcenter services seems to be running check the event viewer
**Before going to the steps to resolve error of LDAP shown in vpxd.log.Check other ways



cheers.............