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

Extreme 100G Transceiver Sensor Metrics

Details

    Description

      Current version of Observium is not able to handle the outputs from 100G transceivers in Extreme devices i.e. for TX/RX values for each wavelength. Attached a discovery debug log from a device which has 4x 100G transceivers plugged in at port 1:57, 1:61, 1:65 and 1:69.

      If you need more debug information, let me know.

      Attachments

        Activity

          [OBS-2840] Extreme 100G Transceiver Sensor Metrics
          dklimek Denis Klimek added a comment -

          Extreme forgot to implement SFP TX Power Channel 1-4 Sensors ...

          ¯_(ツ)_/¯

          dklimek Denis Klimek added a comment - Extreme forgot to implement SFP TX Power Channel 1-4 Sensors ... ¯_(ツ)_/¯
          dklimek Denis Klimek added a comment -

          Extreme released new firmware which contains a bug fix.

          ExtremeXOS 22.7.1.2

          dklimek Denis Klimek added a comment - Extreme released new firmware which contains a bug fix. ExtremeXOS 22.7.1.2
          landy Mike Stupalov added a comment -

          Extreme is next major vendor after Cisco and Juniper, who like make bugs

          landy Mike Stupalov added a comment - Extreme is next major vendor after Cisco and Juniper, who like make bugs
          dklimek Denis Klimek added a comment -

          Extreme Networks created Bug xos0074073 for this. Issue will be fixed in next release EXOS 22.7.1.

           

          dklimek Denis Klimek added a comment - Extreme Networks created Bug xos0074073 for this. Issue will be fixed in next release EXOS 22.7.1.  
          dklimek Denis Klimek added a comment -

          Damn... you're right Adam. Looks like a issue at Extreme again. Time to contact their GTAC again :/

           

          dklimek Denis Klimek added a comment - Damn... you're right Adam. Looks like a issue at Extreme again. Time to contact their GTAC again :/  
          adama Adam Armstrong added a comment -

          The device is reporting these sensors as unavailable. This probably needs to be directed to Extreme.

          ENTITY-MIB is a very standard MIB, any issues are almost certainly related to vendor bugs.

          entPhySensorOperStatus.812 = unavailable
          entPhySensorOperStatus.813 = unavailable
          entPhySensorOperStatus.814 = unavailable
          entPhySensorOperStatus.815 = unavailable
          entPhySensorOperStatus.816 = unavailable
          entPhySensorOperStatus.817 = unavailable
          entPhySensorOperStatus.818 = unavailable
          entPhySensorOperStatus.819 = unavailable
          entPhySensorOperStatus.820 = unavailable
          entPhySensorOperStatus.821 = unavailable

          adama Adam Armstrong added a comment - The device is reporting these sensors as unavailable. This probably needs to be directed to Extreme. ENTITY-MIB is a very standard MIB, any issues are almost certainly related to vendor bugs. entPhySensorOperStatus.812 = unavailable entPhySensorOperStatus.813 = unavailable entPhySensorOperStatus.814 = unavailable entPhySensorOperStatus.815 = unavailable entPhySensorOperStatus.816 = unavailable entPhySensorOperStatus.817 = unavailable entPhySensorOperStatus.818 = unavailable entPhySensorOperStatus.819 = unavailable entPhySensorOperStatus.820 = unavailable entPhySensorOperStatus.821 = unavailable

          People

            adama Adam Armstrong
            dklimek Denis Klimek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: