How to disable the CIM agent on the ESX/ESXi host

Purpose

This article provides the commands to disable the CIM agent on the ESX/ESXi host.
 
You may want to disable the CIM agent if it causes the vpxa watchdog service to restart management services by using all the available memory and by swapping the space in the service console.

Note: The CIM agent is the process providing hardware health information. Disabling this service will disable the hardware health status.

Resolution

To disable the CIM agent on an ESX host:
  1. Log in to the ESX host as root. For more information, see Connecting to an ESX host using a SSH client (1019852).
  2. Run these commands:

    service sfcbd stop
    chkconfig sfcbd-watchdog off
    chkconfig sfcbd off

    Note: Changing the chkconfig disables the sfcbd service and is persistent across reboots.

    To re-enable the CIM agent on the ESX host, run these commands:
     
service sfcbd start
chkconfig sfcbd-watchdog on
chkconfig sfcbd on

Note: To check the status of the agent on ESX, run the below command.

service sfcbd status

To disable the CIM agent on an ESXi host: 
  1. Log in to the ESXi host in the Tech Support Mode as root.
  2. Run these commands:

    chkconfig sfcbd-watchdog off
    chkconfig sfcbd off
    /etc/init.d/sfcbd-watchdog stop

    Note: Changing the chkconfig disables the sfcbd service and is persistent across reboots.

    To re-enable the CIM agent on the ESXi host, run these commands:

    chkconfig sfcbd-watchdog on
    chkconfig sfcbd on
    /etc/init.d/sfcbd-watchdog start

    Note: To check the status of the agent on ESXi, run the below command.

    /etc/init.d/sfcbd-watchdog status

    Based on VMware KB 1025757
  • 0 أعضاء وجدوا هذه المقالة مفيدة
هل كانت المقالة مفيدة ؟

مقالات مشابهة

Hardware and firmware requirements for 64-bit guest operating systems

PurposeThis article explains the host machine hardware and firmware requirements for installing...

Logging in to the vCenter Server 5.0 Web Client fails with the error: unable to connect to vCenter Inventory Service

DetailsAfter upgrading from vCenter Server 4.1 to 5.0, you experience these symptoms:Cannot log...

Multiple network entries in vCenter Server 5.0.x after migrating virtual machines from a virtual switch to a virtual distributed switch

SymptomsAfter migrating virtual machines from a virtual switch to a virtual Distributed...

Minimum requirements for the VMware vCenter Server 5.x Appliance

PurposeIf you are using the VMware vCenter Server Appliance, beginning with vSphere 5.0 you can...