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

OLT V1600G1B - Check MIB compatibility

Details

    Description

      ood morning community,

      I was trying to monitor:

      Vendor/Hardware V-Solution V1600G1B
      Operating system V-SOL OLT

      (so a different version, but I believe it uses the same OS), and indeed, it fails to poll all the information, performing only a partial discovery of the interfaces and stopping there. I see from this link that nothing has been populated on the MIB side yet, is that possible? https://mibs.observium.org/mib/V1600G/

      I also noticed a resolved request here: https://jira.observium.org/browse/OBS-4801, where it seems that MIB compatibility for these OLT devices has been added. Could anyone confirm this?

      I also imagine that the current version 24.3.13371 (stable) needs to be updated to the latest version.

      Thank you for your valuable support!
      M.

      Attachments

        Issue Links

          Activity

            [OBS-4879] OLT V1600G1B - Check MIB compatibility

            Pls do not clone issues.

            landy Mike Stupalov added a comment - Pls do not clone issues.

            Is it also possible to add the logo, as per the attachment? Currently, we see the Observium mouse; it’s a generic logo.

            antonini.mlk Massimo Antonini added a comment - Is it also possible to add the logo, as per the attachment? Currently, we see the Observium mouse; it’s a generic logo.

            Is it also possible to add the logo, as per the attachment? Currently, we see the Observium mouse; it’s a generic logo

            antonini.mlk Massimo Antonini added a comment - Is it also possible to add the logo, as per the attachment? Currently, we see the Observium mouse; it’s a generic logo

            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
              antonini.mlk Massimo Antonini
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: