Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • None
    • Default
    • None

    Description

      We have a Omnitron iConverter NMM2, OS - Omnitron iConverter 5.2.43

      We are currently running Observium Pro Edition 25.1.13837

      But traffic data for this Omnitron NMM2 is not collecting / populating the traffic graphs or additional information regarding light levels.

      Attached are snmp dumps created via the bot recommendation and I have also included a snmp dump using ./scripts/snmpdump.php -h <device>
      The latest available set of MIBs from Omnitron have also been attached.

      Could you let us know if new definitions / MIBs can be added to support the Onmitron NMM2?

      Kind Regards,

      GM

      Attachments

        Issue Links

          Activity

            [OBS-5041] Support for Omnitron NMM2 iConverter

            Improved in r14124.

            landy Mike Stupalov added a comment - Improved in r14124.
            gmusashi gm added a comment -

            Afternoon Mike,

            Is there any updates in regards to whether the snmp dumps were of any use and whether the MIB's we provided from the vendor could be used to pull the correct information from nmm2 transponder card?

            Kind Regards

            GM

            gmusashi gm added a comment - Afternoon Mike, Is there any updates in regards to whether the snmp dumps were of any use and whether the MIB's we provided from the vendor could be used to pull the correct information from nmm2 transponder card? Kind Regards GM
            gmusashi gm added a comment -

            Morning,

            Can we check if there is any update regarding this request? 

            If there are issues with the snmp dumps that were collected, then please let us know and we will get these re-exported.

            Kind Regards

            GM

             

            gmusashi gm added a comment - Morning, Can we check if there is any update regarding this request?  If there are issues with the snmp dumps that were collected, then please let us know and we will get these re-exported. Kind Regards GM  

            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
              gmusashi gm
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: