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

Integration of Optilink OP-MEN99810B with Observium

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Trivial
    • None
    • None
    • Graphs, OS, Ports
    • None

    Description

      Hi,

      Can we integrate Optilink OP-MEN99810B with Observium.
      Currently, it is recognised as Ruby Tech device.
      Also, if it is possible to have graphs for CPU/Memory utilisation, device temperature and performance parameters of its optical interfaces.

      I'm attaching the output of the required SNMP dumps along with MIB file.

      Attachments

        Issue Links

          Activity

            [OBS-4521] Integration of Optilink OP-MEN99810B with Observium
            landy Mike Stupalov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            Improved in r12839.

            landy Mike Stupalov added a comment - Improved in r12839.
            landy Mike Stupalov made changes -
            Status Original: In Review [ 10101 ] New: In Progress [ 3 ]
            landy Mike Stupalov made changes -
            Link New: This issue duplicates OBS-4453 [ OBS-4453 ]
            landy Mike Stupalov made changes -
            Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]

            The SNMP dumps from a device have been attached along with MIB file.

            PlamenH Plamen Haralambiev added a comment - The SNMP dumps from a device have been attached along with MIB file.
            bot Observium Bot made changes -
            Status Original: Open [ 1 ] New: Pending Response [ 10000 ]

            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.
            PlamenH Plamen Haralambiev created issue -

            People

              landy Mike Stupalov
              PlamenH Plamen Haralambiev
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: