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

Cannot enable virtual-machines module for ESXi server

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Minor
    • None
    • CE-22.5
    • Discovery, Web Interface
    • None

    Description

      Hi!

      First, the version is wrong but JIRA won't let me pick CE-23.9.

      I have among other systems a standalone ESXi 7.0-U3o that I monitor and for some reason the virtual-machines module - while globally enabled - is disabled for this system.

      When I run a discovery in debug mode the VMINFO MIB is there:

      sysORDescr.13 = VMWARE-SYSTEM-MIB, REVISION 201008020000Z
      sysORDescr.14 = VMWARE-VMINFO-MIB, REVISION 201006220000Z
      sysORDescr.15 = VMWARE-RESOURCES-MIB, REVISION 200810150000Z
      sysORDescr.16 = VMWARE-CIMOM-MIB, REVISION 201008200000Z
      sysORDescr.17 = VMWARE-ENV-MIB, REVISION 201706050000Z
      

      But the module is disabled:

      #####  Module Start: graphs  #####
       o Duration             0.0004s
       o Modules Disabled     lsp, virtual-machines, wifi, raid
       o Modules Enabled      os, mibs, vrf, ports, ports-stack, vlans, oids, ip-addresses, processors, mempools, inventory, printersupplies, sensors, 
                              storage,neighbours, arp-table, junose-atm-vp, bgp-peers, mac-accounting, sla, pseudowires, cisco-cbqos, ucd-diskio, 
                              p2p-radios,graphs 
      

      When I click on the "Enable" button in the module settings the screen is refreshed but nothing else happens. Doing that in debug mode shows an SQL statement that inserts "0" instead of (I assume) "1" into the table. I'll attach screenshots.

      Is this a bug in the UI? Shouldn't the module be enabled by default if the target OS is "vmware" and the VMWARE-VMINFO-MIB exists?

      Next thing I would try on my own would be to manually enable the module via SQL like so:

      DELETE FROM `entity_attribs` WHERE `entity_type` = 'device' AND `entity_id` = '23' AND `attrib_type` = 'discover_virtual-machines';
      INSERT INTO `entity_attribs` (`device_id`,`entity_type`,`entity_id`,`attrib_type`,`attrib_value`) VALUES ('23','device','23','discover_virtual-machines','1');
      

      Would that be advisable or is it prone to break other things?

      Thanks and kind regards,
      Patrick

      Attachments

        Activity

          [OBS-4718] Cannot enable virtual-machines module for ESXi server

          Can't reproduce in latest revisions. Seems as already fixed after last CE.

          landy Mike Stupalov added a comment - Can't reproduce in latest revisions. Seems as already fixed after last CE.

          and show me status of files from observium base dir as:

          svn status

          landy Mike Stupalov added a comment - and show me status of files from observium base dir as: svn status

          Complete not sure reasons for this. On all tested devices this module enabled.
          Did you changed something before for device?

          Make discovery debug and attach it (without cut parts of output):

          ./discovery.php -d -h <device>
          

          You can send this output to me in Discord (@landy).

          landy Mike Stupalov added a comment - Complete not sure reasons for this. On all tested devices this module enabled. Did you changed something before for device? Make discovery debug and attach it (without cut parts of output): ./discovery.php -d -h <device> You can send this output to me in Discord (@landy).
          Hausen Patrick M. added a comment -

          Running the two SQL statements and then a manual discovery of the host makes the VMs appear with current names, configuration (CPU cores, memory) and state (powered on/off).

          Powering off a virtual machine and subsequently running ./poller.php does not update the VM state (powered on/off). Only another run of ./discovery.php updates the state.

          Since by default discovery of existing devices is run only every 6 hours this is not very useful. I wonder if it's intentional or if I am missing anything?

          I do not intend to run any SNMP service inside the VMs and have them autodiscovered and monitored by Observium. But a list of all VMs, their configured resources and their current state would definitely be desired and I thought that's what the virtual-machines module is supposed to do?

          Kind regards,
          Patrick

          Hausen Patrick M. added a comment - Running the two SQL statements and then a manual discovery of the host makes the VMs appear with current names, configuration (CPU cores, memory) and state (powered on/off). Powering off a virtual machine and subsequently running ./poller.php does not update the VM state (powered on/off). Only another run of ./discovery.php updates the state. Since by default discovery of existing devices is run only every 6 hours this is not very useful. I wonder if it's intentional or if I am missing anything? I do not intend to run any SNMP service inside the VMs and have them autodiscovered and monitored by Observium. But a list of all VMs, their configured resources and their current state would definitely be desired and I thought that's what the virtual-machines module is supposed to do? Kind regards, Patrick
          Hausen Patrick M. added a comment -

          Attached snmpwalk output as requested.
          myagent.snmpwalk

          Hausen Patrick M. added a comment - Attached snmpwalk output as requested. myagent.snmpwalk

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            Hausen Patrick M.
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: