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

Issue with ONU Monitoring on BDCOM GPON OLT

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • CE-22.5
    • OS, Ports

    Description

      We are using Observium to monitor BDCOM OLTs (EPON and GPON). While ONU information is displayed correctly for EPON, it is missing for GPON OLTs.

      We've attached the relevant MIB files and SNMP walk outputs for the GPON OLTs to assist in troubleshooting. Could you please confirm if ONU monitoring is supported for GPON OLT, or if further steps are needed to enable it?

      I am using -> Observium CE 24.12.13800

      Attachments

        1. epon-1.jpg
          epon-1.jpg
          45 kB
        2. gpon-1.jpg
          gpon-1.jpg
          21 kB

        Activity

          [OBS-5035] Issue with ONU Monitoring on BDCOM GPON OLT

          Improved support in r14044.
          If you use CE edition, this will added in next CE update.

          landy Mike Stupalov added a comment - Improved support in r14044. If you use CE edition, this will added in next CE update.

          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
            noman Noman Abdullah
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: