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

Half Duplex Alerting is not functional within JunOS

Details

    • Bug
    • Resolution: Won't Fix
    • Major
    • None
    • Community Edition
    • Alerting, Poller
    • Debian / as usal.

    Description

      I just experienced the problem that „Alerting“ for HDX Ports does not work with JunOS, as I suspect not the real state of an interface is monitored, but something different.

      Best documened by screenshots.

      For Bug Fixing I can grant SNMP Access to sample devices.

      Attachments

        1. Observium_HDX_1.png
          Observium_HDX_1.png
          8 kB
        2. Observium_HDX_2.png
          Observium_HDX_2.png
          26 kB
        3. Observium_HDX_3.png
          Observium_HDX_3.png
          32 kB

        Activity

          [OBS-1421] Half Duplex Alerting is not functional within JunOS
          landy Mike Stupalov made changes -
          Workflow Original: classic default workflow [ 12414 ] New: Observium workflow [ 14572 ]
          landy Mike Stupalov made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          landy Mike Stupalov added a comment -

          Vendor bug.

          landy Mike Stupalov added a comment - Vendor bug.
          adama Adam Armstrong added a comment -

          Indeed, this is 100% a JunOS bug, typical. There's no way of us knowing this data is wrong, so you'll have to exclude the devices which exhibit this from the alert definition.

          Probably easiest done with "hostname != <hostname>" lines, i guess.

          adama Adam Armstrong added a comment - Indeed, this is 100% a JunOS bug, typical. There's no way of us knowing this data is wrong, so you'll have to exclude the devices which exhibit this from the alert definition. Probably easiest done with "hostname != <hostname>" lines, i guess.
          rmueller Richard Mueller added a comment -

          The interesting part is:

          /usr/bin/snmpbulkwalk -t '5' -r '2' -v2c -c '<private>' -Pu -OQUs -m EtherLike-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'<hostname>':'161' dot3StatsEntry
          [...]
          dot3StatsDuplexStatus.508 = fullDuplex
          dot3StatsDuplexStatus.509 = fullDuplex
          dot3StatsDuplexStatus.510 = fullDuplex
          dot3StatsDuplexStatus.511 = fullDuplex
          dot3StatsDuplexStatus.513 = fullDuplex
          dot3StatsDuplexStatus.514 = fullDuplex
          dot3StatsDuplexStatus.515 = fullDuplex
          dot3StatsDuplexStatus.516 = fullDuplex
          dot3StatsDuplexStatus.517 = fullDuplex
          dot3StatsDuplexStatus.519 = fullDuplex
          dot3StatsDuplexStatus.523 = fullDuplex
          dot3StatsDuplexStatus.526 = fullDuplex
          dot3StatsDuplexStatus.528 = fullDuplex
          dot3StatsDuplexStatus.529 = fullDuplex
          [..]

          Do you see any possibility to circumvent the bug?
          (Meanwhile I will open a case @Juniper, but I assume they are as big as a giant tanker. Mostly you need a speedboat for making customers happy)

          Access to a device can be provided.

          rmueller Richard Mueller added a comment - The interesting part is: /usr/bin/snmpbulkwalk -t '5' -r '2' -v2c -c '<private>' -Pu -OQUs -m EtherLike-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'<hostname>':'161' dot3StatsEntry [...] dot3StatsDuplexStatus.508 = fullDuplex dot3StatsDuplexStatus.509 = fullDuplex dot3StatsDuplexStatus.510 = fullDuplex dot3StatsDuplexStatus.511 = fullDuplex dot3StatsDuplexStatus.513 = fullDuplex dot3StatsDuplexStatus.514 = fullDuplex dot3StatsDuplexStatus.515 = fullDuplex dot3StatsDuplexStatus.516 = fullDuplex dot3StatsDuplexStatus.517 = fullDuplex dot3StatsDuplexStatus.519 = fullDuplex dot3StatsDuplexStatus.523 = fullDuplex dot3StatsDuplexStatus.526 = fullDuplex dot3StatsDuplexStatus.528 = fullDuplex dot3StatsDuplexStatus.529 = fullDuplex [..] Do you see any possibility to circumvent the bug? (Meanwhile I will open a case @Juniper, but I assume they are as big as a giant tanker. Mostly you need a speedboat for making customers happy) Access to a device can be provided.
          adama Adam Armstrong added a comment -

          This would seem to be a JunOS bug.

          Can you get a poller debug output for this device?

          ./poller.php -h <device> -m ports -d

          adama Adam Armstrong added a comment - This would seem to be a JunOS bug. Can you get a poller debug output for this device? ./poller.php -h <device> -m ports -d
          rmueller Richard Mueller made changes -
          Attachment New: Observium_HDX_3.png [ 12623 ]
          rmueller Richard Mueller added a comment -

          Uploaded as "proof" for existance

          rmueller Richard Mueller added a comment - Uploaded as "proof" for existance
          rmueller Richard Mueller added a comment -

          Hy Kent,

          I just checked the affected port and there is a "fullDuplex" (see attachment)

          rmueller Richard Mueller added a comment - Hy Kent, I just checked the affected port and there is a "fullDuplex" (see attachment)
          kentbjoh Kent Johannessen added a comment -

          Check port data and see if there is anything in the ifDuplex value.
          Use the Data tab in single port view to find this.

          kentbjoh Kent Johannessen added a comment - Check port data and see if there is anything in the ifDuplex value. Use the Data tab in single port view to find this.

          People

            adama Adam Armstrong
            rmueller Richard Mueller
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: