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

Synology SA3400 and SA3600 models are detected as generic linux

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • OS

    Description

      Hi Observium support,

       

      The Synology SA3400 and SA3600 devices are not obtaining correct OS matching when they are discovered. I was get this to work by modifying the modelName.0 string match found in the following file:

      includes/definitions/os/synology.inc.php file.

      Please review the diff below and hopefully apply this permanently. I think it will make life easier for users in the future.

      -Rick

       

      1. diff ~/synology.inc.php /opt/observium/includes/definitions/os/synology.inc.php 
        27c27
        <   'SYNOLOGY-SYSTEM-MIB::modelName.0'        => '/^(DS|RS|FS|RC)/',
        —
        >   'SYNOLOGY-SYSTEM-MIB::modelName.0'        => '/^(DS|RS|FS|RC|SA)/',

      Attachments

        Activity

          [OBS-4021] Synology SA3400 and SA3600 models are detected as generic linux
          bot Observium Bot made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          landy Mike Stupalov made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          landy Mike Stupalov added a comment -

          Improved in r11879.

          landy Mike Stupalov added a comment - Improved in r11879.
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          barzilli Rick Barzilli created issue -
          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 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --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

          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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

          People

            landy Mike Stupalov
            barzilli Rick Barzilli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: