Defunct cimservera processes freeze VMware ESX 3.5

Earlier today Virtual IEF posted a blog about not being able to access an ESX host, not by ssh, not by VIC and not even through vCenter.  Evidently this is caused by the hardware monitoring agents (HP, Dell, etc) auto-detecting the management server and failing authentication.  This causes cimservera to be spawned hundreds if not thousands of times thus causing so much CPU and Network traffic locally that it cannot respond within the thresholds for SSH, or VPX agents.

Read More…


Created on January 6, 2009 by Rick Scherer

Posted under ESX 3.5 Tips, ESXi 3.5 Tips, Monitoring.

This blog has 5,411 views and one response.

Tags: , , ,

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

Access the ESXi Service Console

Here is a brief write-up on how to access the Service Console of VMware ESXi. As a disclaimer, this should only be done under the direct supervision of a VMware Support Engineer.

Read More…


Created on October 20, 2008 by Rick Scherer

Posted under ESXi 3.5 Tips, VMware.

This blog has 61,939 views and 12 responses.

Tags: , , ,

1 Star2 Stars3 Stars4 Stars5 Stars (8 votes, average: 4.88 out of 5)
Loading...

Changing Service Console IP Address in ESX 3.5

Actually this is not that difficult, but remember you will require console access to the server. Be sure to put the machine in Maintenance Mode then Disconnect it from Virtual Center. Then connect to the console of the ESX host;

Read More…


Created on September 12, 2008 by Rick Scherer

Posted under ESX 3.5 Tips, ESXi 3.5 Tips, Networking, VMware.

This blog has 109,599 views and 10 responses.

Tags: , , , , ,

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)
Loading...