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

Integrate Optilink OL-MEN99216B switch

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller
    • None

    Description

      Hello,

      We've installed an Optilink switch in our network and observium is not discovering essential information about the device.

      It's a Optilink OL-MEN99216B switch. Attaching the MIB file provided by the vendor, along with a dump from snmpwalk.

      Attachments

        Issue Links

          Activity

            [OBS-4453] Integrate Optilink OL-MEN99216B switch

            If it not already added, this information was not in the provided snmpdump.

            Create new issue and attach snmpdump as Bot requested.

            landy Mike Stupalov added a comment - If it not already added, this information was not in the provided snmpdump. Create new issue and attach snmpdump as Bot requested.

            Hi,
            Is it possible to have also CPU/Memory utilisation, port sensors (params of the optical ports with SFP modules), device temperature and power supply information.
            Also, it would be nice if we had SLA information.

            Do you need more information in order to do such integrations?

            Kind regards,

            Plamen

            PlamenH Plamen Haralambiev added a comment - Hi, Is it possible to have also CPU/Memory utilisation, port sensors (params of the optical ports with SFP modules), device temperature and power supply information. Also, it would be nice if we had SLA information. Do you need more information in order to do such integrations? Kind regards, Plamen

            Improved vendor/version detect in r12644.

            landy Mike Stupalov added a comment - Improved vendor/version detect in r12644.

            this is weird (mibs per model) switches.
            snmpwalk now ok, but mib not related with exactly this switch (OP-MEN99216BC vs OL-MEN99216B).

            landy Mike Stupalov added a comment - this is weird (mibs per model) switches. snmpwalk now ok, but mib not related with exactly this switch (OP-MEN99216BC vs OL-MEN99216B).

            Hello, apologies for the late reply.

            Please find attached the snmpwalk data generated from the commands as per instructions.

            [^myagent.snmpwalk]

            axtroz Iskren Hadzhinedev added a comment - Hello, apologies for the late reply. Please find attached the snmpwalk data generated from the commands as per instructions. [^myagent.snmpwalk]

            Your snmpwalk not usable for testing.
            Please make snmpdump with command(s) written by Observium Bot.

            landy Mike Stupalov added a comment - Your snmpwalk not usable for testing. Please make snmpdump with command(s) written by Observium Bot.

            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
              axtroz Iskren Hadzhinedev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: