Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3038

VMWare ESXi / HPE Server - Status Indicators "unknown"

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery, OS, Poller
    • None

    Description

      Hi there,

      Since the last update, my VMWare ESXi hosts have the status indicators shown in the picture.

      Is there a way to hide this or to correct the output? Status 1 = OK

       

      Best regards

      Richard

       

      Observium 19.6.9952 (19th June 2019)
      OS Linux 4.4.0-146-generic [amd64] (Ubuntu 16.04)
      Apache 2.4.18 (Ubuntu)
      PHP 7.0.33-0ubuntu0.16.04.4 (OPcache: ENABLED)
      Python 2.7.12
      MySQL 5.7.26-0ubuntu0.16.04.1 (extension: mysqli 5.0.12-dev)
      SNMP NET-SNMP 5.7.3
      RRDtool 1.5.5
      Fping 3.13 (IPv4 and IPv6)

      Attachments

        Activity

          [OBS-3038] VMWare ESXi / HPE Server - Status Indicators "unknown"

          Fixed in r9953.

          landy Mike Stupalov added a comment - Fixed in r9953.
          kuhner Richard Kucera added a comment - - edited

          Hi Mike,

          i think excluding the unknown status would be a good solution for me.
          It's interesting, in the vSphere these points are displayed as OK.

          Many thanks for your response.

          kuhner Richard Kucera added a comment - - edited Hi Mike, i think excluding the unknown status would be a good solution for me. It's interesting, in the vSphere these points are displayed as OK. Many thanks for your response.

          This status correct, as described in VMWARE-RESOURCES-MIB::vmwHbaStatus:

          SYNTAX  INTEGER { unknown(1), normal(2), marginal(3), critical(4), failed(5) }
          

          unknown definitely is not ok state, we can just exclude statuses with such state.

          landy Mike Stupalov added a comment - This status correct, as described in VMWARE-RESOURCES-MIB::vmwHbaStatus : SYNTAX INTEGER { unknown(1), normal(2), marginal(3), critical(4), failed(5) } unknown definitely is not ok state, we can just exclude statuses with such state.

          People

            landy Mike Stupalov
            kuhner Richard Kucera
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: