Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Web Interface
    • QNAP ES1640DC v2 - SAN storage from QNAP supported by FreeBSD.

    Description

      Dear sirs,

      I would like your help, in order to add Observium support to the device QNAP ES1640DC v2. Attached you will find the MIB file associated with it.

      As it is a BSD Supported device, many features are automatically discovered. However, as this is a SAN (Storage Attached Network) device, information regarding LUN and individual Hard-disks status are not. I am convinced this is a "simple" fix from your part.

      In summary, I would like to see information (and create alerts) about LUNS and Health about individual hard-drives.

      Thanks for your time and help.

      Best regards.

       

      Attachments

        1. QNAP.mib
          48 kB
        2. myagent.snmpwalk
          1.26 MB
        3. myagent1.snmpwalk
          1.90 MB

        Issue Links

          Activity

            [OBS-3165] Support for QNAP ES1640DC v2

            Support added in r10199.

            landy Mike Stupalov added a comment - Support added in r10199.
            rclaro Rui Claro added a comment - - edited

            Hi.

            No problem.

            I attached a new file with the dump you requested. As getting you an outside access, I'm sorry, but the device is not accessible from the outside.

            The values I'm interested in, as I said on my first post, are the device specific ones (those beneath the ".1.3.6.1.4.1.24681" branch, particularly under ".1.3.6.1.4.1.24681.2.2", because ".1.3.6.1.4.1.24681.2.1" are essentially events logging.

            Hope to hear from you soon.

             

            rclaro Rui Claro added a comment - - edited Hi. No problem. I attached a new file with the dump you requested. As getting you an outside access, I'm sorry, but the device is not accessible from the outside. The values I'm interested in, as I said on my first post, are the device specific ones (those beneath the ".1.3.6.1.4.1.24681" branch, particularly under ".1.3.6.1.4.1.24681.2.2", because ".1.3.6.1.4.1.24681.2.1" are essentially events logging. Hope to hear from you soon.  

            rclaro or if possible, provide temporary snmp access to device from my dev ip (77.222.50.30), community you can send by mail: mike@observium.org

            Just QNAP devices more difficult for detecting by dump.

            landy Mike Stupalov added a comment - rclaro or if possible, provide temporary snmp access to device from my dev ip (77.222.50.30), community you can send by mail: mike@observium.org Just QNAP devices more difficult for detecting by dump.

            Hi, sorry for delay.
            In dump I see only enterprise Oid tree, device not support standard rfc Oids?

            Pls try to make additional dump for:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.2.1 > myagent1.snmpwalk
            

            landy Mike Stupalov added a comment - Hi, sorry for delay. In dump I see only enterprise Oid tree, device not support standard rfc Oids? Pls try to make additional dump for: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.2.1 > myagent1.snmpwalk
            rclaro Rui Claro added a comment -

            Hi!

            Can you please give an update on this issue?

            Thanks!

            rclaro Rui Claro added a comment - Hi! Can you please give an update on this issue? Thanks!
            rclaro Rui Claro added a comment - - edited

            Hi!

            Thanks for your fast reply.

            You can find, in the attached file, the results of your request.

            Kind regards,

            RC

            rclaro Rui Claro added a comment - - edited Hi! Thanks for your fast reply. You can find, in the attached file, the results of your request. Kind regards, RC

            Please attach full snmp dump from device (file myagent.snmpwalk):

            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
            

            landy Mike Stupalov added a comment - Please attach full snmp dump from device (file myagent.snmpwalk): 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

            People

              landy Mike Stupalov
              rclaro Rui Claro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: