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

Juniper MIB is no longer collecting temperature for FRUs

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery

    Description

      The discovery process for Juniper devices is no longer collecting temperature information for FRUs using the JUNIPER-MIB. Doing some research on my installed based which consists of SRX, MX, EX, PTX and ACX boxes I came up to the conclusion that only the following jnxFruType values should be accounted for temperature readings:

      • powerEntryModule
      • flexiblePicConcentrator
      • routingEngine
      • controlBoard

      Also, for optimization sake, only the indexes that have jnxFruState == online and jnxOperatingTemp != 0 should be discovered.

      To solve my alerting problem I created a small patch for our internal use since we really rely on those temperature readings for health checks. I've attached the patch on this ticket.

      I've used the *_ng variant of the discover function. I'm not sure it's supposed to be used a replacement for the previous one. Visually I've noticed an issue that has probably to do with the index field that's being set to 0. See the attached image for the trailing 0 (zero) at the end of the OID index.

      Attachments

        1. Screen Shot 2019-03-29 at 12.16.42.png
          67 kB
          Luis Balbinot
        2. Screen Shot 2019-04-01 at 16.18.42.png
          24 kB
          Luis Balbinot
        3. sensors_debug_dd.txt
          201 kB
          Luis Balbinot
        4. sensors_debug.txt
          331 kB
          Luis Balbinot

        Activity

          People

            landy Mike Stupalov
            lbalbinot Luis Balbinot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: