About a VMware ESXi host, the warning “Sfcbd not started, administratively disabled” usually refers to the sfcbd service. As part of our Server Management Service, Bobcares provides answers to all of your questions.

More on “Sfcbd not started, administratively disabled”

“Small Footprint CIM Broker Daemon,” or sfcbd, is the service that answers to requests for CIMs. It also gives management software hardware-related details and monitoring data. This message shows the admin action has temporarily disabled the sfcbd service. This may be done on purpose by a system admin or as part of troubleshooting to solve a particular problem.

We can enable the sfcbd service using the vSphere Client or the ESXi Shell.

Enabling SFCBD Using VSphere Client

1. Firstly, access the vSphere Client.

2. Then, chooose the ESXi host in the inventory.

3. Now, go to the “Configure” tab.

4. Also, select “Advanced System Settings” under “System.”

5. In the “Filter” box, now enter “sfcbd.”

6. Find the “UserVars.CIMvmw_sfcbs.disabled” option.

7. Change the value of “UserVars.CIMvmw_sfcbs.disabled” from 1 to 0.

8. Lastly, select “OK” to save the changes.

Enabling SFCBD Using ESXi Shell

1. Use an SSH client such as PuTTY to log in to the ESXi host.

2. To make the sfcbd service available, execute the following command:

esxcli system settings advanced set -o /UserVars/CIMvmw_sfcbs.disabled -i 0

3. To carryout the changes, restart the sfcbd service:

/etc/init.d/sfcbd-watchdog restart

[Need to know more? We’re available 24/7.]

Conclusion

It’s important to approach cautiously when changing advanced settings and to be aware of the effects of turning on or off specific services.