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

FreeNAS 11.3 discovered as FreeBSD

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • CE-17.9, Professional Edition
    • Discovery
    • None

    Description

      It looks like ixSystems changed the reported sysObjectId again in 11.3.    They now report the following:

      For FreeNas boxes - .1.3.6.1.4.1.50536.3.1

      For TrueNas boxes - .1.3.6.1.4.1.50536.3.2

       

      I have attached a patch file to detect both of these cases and this has been tested again actual ixSystems FreeNAS and TrueNAS hardware as well as a home built system running FreeNAS.

      Attachments

        Activity

          [OBS-3350] FreeNAS 11.3 discovered as FreeBSD
          bot Observium Bot made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          landy Mike Stupalov added a comment -

          Tnx, added in r10445.

          I merged both discovery definitions to single.

          landy Mike Stupalov added a comment - Tnx, added in r10445. I merged both discovery definitions to single.
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: In Progress [ 3 ]
          cdebruin Chris DeBruin added a comment -

          SNMP walk attached

          cdebruin Chris DeBruin added a comment - SNMP walk attached
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          cdebruin Chris DeBruin made changes -
          Attachment New: freenas.snmpwalk [ 17491 ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          cdebruin Chris DeBruin created issue -
          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.

          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
            cdebruin Chris DeBruin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: