Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Virtualization Manager (VMAN) > VMware ESX 6.5 unknown status and polling fails in VMAN

VMware ESX 6.5 unknown status and polling fails in VMAN

Updated: 5-11-2017

Overview

For VMAN, VMware ESX 6.5 Hardware health may appear as Unknown and does not display the accurate status in the Orion Web Console. The VM node displays as Green with a Grey child status. If using Network Atlas, the map shows the server as green with a yellow status.

Note: Network Atlas does not use Orion Core statuses, other than up/down, or thresholds for color coding.

The reported error is: Hardware Health Unknown. "Polling of chassis (CIM_Chassis class) failed. Unable to connect to the remote server."

To resolve, you need to access the ESX server via SSH and enter a series of commands to restart the sfcbd-watchdog service. See the resolution steps for a walkthrough of SSH commands.

 

Environment

  • VMAN
  • VMware ESX 6.5

 

Cause 

The hardware health for VMware ESX 6.5 may display inaccurately as Unknown when polling fails. There is a work-around to reset and poll a correct status.

Resolution

The following instructions include SSH commands. Use a preferred CLI for entering these commands via SSH, for example putty. For assistance, contact Support.

If you do not have SSH enabled for the VMware ESX 6.5 system, enable it:

  1. Access the VMware C Client for the server.
  2. Select Configuration > Security Profile, and select Properties.
  3. Select SSH.
  4. Click to enable the SSH Service.

With SSH enabled, complete the following commands:

  1. Login to the server via SSH using a CLI. For our examples, putty was used.
  2. Enter and run: esxcli system wbem get

    The following messages display:

    Authorization Model: password
    Enabled: false
    Loglevel: warning
    Port: 5989
    WSManagement Service: true
    
  3. Enter and run: esxcli system wbem set -e 1
  4. Perform another get command: esxcli system wbem get

    The following messages display:

    Authorization Model: password
    Enabled: false
    Loglevel: warning
    Port: 5989
    WSManagement Service: true
    
  5. Verify the service is running with this command: /etc/init.d/sfcbd-watchdog status

    The following message displays:

    sfcbd is running
  6. Run a test of the service: /etc/init.d/sfcbd-watchdog test

    The following messages display:

    sfcbd-init: Checking core components of sfcbd are running...
    sfcbd-init: Component sfcb-ProviderMa is running.
    sfcbd-init: Component sfcb-HTTP-Daemo is running.
    sfcbd-init: Component sfcb-HTTPS-Daem is running.
    sfcbd-init: All components are running.
    
  7. Stop the service: /etc/init.d/sfcbd-watchdog stop

    The following messages display:

    sfcbd-init: Getting Exclusive access, please wait...
    sfcbd-init: Exclusive access granted.
    sfcbd-init: Request to stop sfcbd-watchdog, pid 84360
    sfcbd-init: Invoked kill 84014
    sfcbd-init: stop sfcbd process completed.
    
  8. Start the service: /etc/init.d/sfcbd-watchdog start

    The following messages display:

    sfcbd-init: Getting Exclusive access, please wait...
    sfcbd-init: Exclusive access granted.
    sfcbd-init: Request to start sfcbd-watchdog, pid 84401
    sfcbd-config[84411]: No third party cim providers installed
    sfcbd-init: Start to create indication subscription for hostd SNMPSVC
    sfcbd-init: starting sfcbd
    sfcbd-init: Waiting for sfcb to start up.
    sfcbd-init: Program started normally.
    
  9. Check the service status: /etc/init.d/sfcbd-watchdog status

    The following message displays:

    sfcbd is running
  10. Finally test the service: /etc/init.d/sfcbd-watchdog test

    The following messages display:

    sfcbd-init: Checking core components of sfcbd are running...
    sfcbd-init: Component sfcb-ProviderMa is running.
    sfcbd-init: Component sfcb-HTTP-Daemo is running.
    sfcbd-init: Component sfcb-HTTPS-Daem is running.
    sfcbd-init: All components are running.
    
  11. Exit the SSH.
  12. Wait for polling to continue and verify the status in the Orion Web Console. The process may take 15 minutes. A restart should not be required.

 

 

Last modified
09:59, 11 May 2017

Tags

Classifications

Public