Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • None
    • Poller
    • None

    Description

      Just updated from 11075 to 11104 and noticed a new device type 'Hypervisor' was added.

      Greatly appreciate that Proxmox hypervisors now showing up with their own logo but now the OpenVZ/LXC containers are also listed with the same Proxmox logo and under device type hypervisors which looks like now there a hundreds of Proxmox hypervisors out there which isn't the case.

      As Observium is already aware that the guests systems are containers or KVM and correctly identified as OpenVZ/LXC/KVM maybe you can also use their own logos and put them into device type virtual machine (new)?

      Physical Hardware running Debian/Proxmox:

              1. Module Start: os #####

      o OS Poller Group
      o Type Hypervisors
      o Vendor Supermicro
      o Hardware X9DRW-3LN4F+/X9DRW-3TF+
      o Version 6.3
      o Features Virtual Environment
      o Serial <empty>
      o Asset <empty>

      Virtual guest system (OpenVZ container):

              1. Module Start: os #####

      o OS Poller Group
      o Type Hypervisors
      o Vendor <empty>
      o Hardware OpenVZ Container x86 [32bit]
      o Version <empty>
      o Features Debian
      o Serial <empty>
      o Asset <empty>

      Virtual guest system (LXC container):

              1. Module Start: os #####

      o OS Poller Group
      o Type Hypervisors
      o Vendor <empty>
      o Hardware LXC Container x86 [64bit]
      o Version <empty>
      o Features Debian 10
      o Serial <empty>
      o Asset <empty>

      Virtual guest system (KVM):

              1. Module Start: os #####

      o OS Poller Group
      o Type Servers
      o Vendor <empty>
      o Hardware KVM Virtual Machine x86 [64bit]
      o Version 5.8.0-0.bpo.2-amd64
      o Features Debian 10
      o Serial <empty>
      o Asset <empty>

      Thank You,
      Alex

      Attachments

        1. debug.log
          11 kB
        2. devices-containers.png
          devices-containers.png
          40 kB
        3. device-osdetail-lxc.png
          device-osdetail-lxc.png
          36 kB
        4. device-osdetail-openvz.png
          device-osdetail-openvz.png
          36 kB

        Activity

          [OBS-3683] New device type Hypervisor

          Yes, fixed - thanks

          ajoelly.magna Alexander Joelly added a comment - Yes, fixed - thanks

          Currently we not have plans for add specific type for vm containers.
          But exactly this issue fixed in r11110.

          All KVM/OpenVZ containers should back to linux os and server type.
          (need rediscovery this devices after update).

          Probably later we add tags with some common types like vm, container, switch, router.

          landy Mike Stupalov added a comment - Currently we not have plans for add specific type for vm containers. But exactly this issue fixed in r11110. All KVM/OpenVZ containers should back to linux os and server type. (need rediscovery this devices after update). Probably later we add tags with some common types like vm , container , switch , router .
          ajoelly.magna Alexander Joelly added a comment - - edited

          attached the debug and two images from one of the LXC containers - all LXC & OpenVZ containers are like this one.

          Thanks,
          Alex

          ajoelly.magna Alexander Joelly added a comment - - edited attached the debug and two images from one of the LXC containers - all LXC & OpenVZ containers are like this one. Thanks, Alex
          adama Adam Armstrong added a comment - - edited

          Are your containers being identified as proxmox? Can you show output of :

          ./discovery.php -h <device_id> -m os -dd

          For these devices? The clients are not proxmox.

          adama Adam Armstrong added a comment - - edited Are your containers being identified as proxmox? Can you show output of : ./discovery.php -h <device_id> -m os -dd For these devices? The clients are not proxmox.

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            ajoelly.magna Alexander Joelly
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: