Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery, OS
    • Linux 5.10.0-23-amd64 [amd64] (Debian 11)

    Description

      Hello,

      I would like to know if it is possible do support NetApp CN1610 switches.

      They are technically already supported as they are basically Broadcom Fastpath switches, but they do report a custom-branded sysObjectID that Observium does not recognise.

      • Fastpath / EFOS switches sysObjectID: SNMPv2-SMI::enterprises.4413
      • NetApp CN1610 sysObjectID: SNMPv2-SMI::enterprises.789

      Interesting fact is, even if the sysObjectID is different, NetApp is basically only "prefixing" the standard Fastpath MIB, example:

      • CN1610 boxServicesFansTable => '.1.3.6.1.4.1.789.4413.1.1.43.1.6.1'
      • Fastpath boxServicesFansTable => '.1.3.6.1.4.1.4413.1.1.43.1.6.1',

      You would probably be able to reuse all the same logic / MIBs that are already used for fastpath switches, by only "prefixing" the OIDs with "789."

      I would gladly test a patch if necessary.

      Thank you in advance,

      Attachments

        Activity

          [OBS-4638] Support NetApp CN1610 switches

          Support added in r13105.

          landy Mike Stupalov added a comment - Support added in r13105.

          Aaaaand here you go.

          Kegeruneku Matthieu CERDA added a comment - Aaaaand here you go.

          Will do ! I'm searching for a spare unit to dump in our stock.

          Kegeruneku Matthieu CERDA added a comment - Will do ! I'm searching for a spare unit to dump in our stock.

          You must attach requested snmpdump from device (as Bot written).

          Also while this is fastpath clone, we can't add/improve support for device without look into real snmp data.

          landy Mike Stupalov added a comment - You must attach requested snmpdump from device (as Bot written). Also while this is fastpath clone, we can't add/improve support for device without look into real snmp data.

          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
            Kegeruneku Matthieu CERDA
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: