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

Values wrong for transceivers on Cisco ASR

Details

    Description

      Wrong values for Cisco ASR on transceivers. Seems they are *10 what they should be..
      I guess this could be vendor bug aswell.. ? See attached

      Attachments

        1. iosxesensors.PNG
          iosxesensors.PNG
          102 kB
        2. rtrdebugdis.txt
          441 kB
        3. rtrdebugpoll.txt
          24 kB

        Issue Links

          relates to

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-3026 Wrong values for transceivers in Cisco 9500

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Activity

            [OBS-3707] Values wrong for transceivers on Cisco ASR
            landy Mike Stupalov added a comment -

            Yah, ok.. Should be fixed in r11200.

            landy Mike Stupalov added a comment - Yah, ok.. Should be fixed in r11200.
            kentbjoh Kent Johannessen added a comment -

            I saw that linked issue. I reverted that workaround and the values are now as expected

            We currently on 16.12.4 on the ASR. We have a few of these, all on the same versions.
            So it seems it was maybe fixed in the 16.12.x releases then.

            kentbjoh Kent Johannessen added a comment - I saw that linked issue. I reverted that workaround and the values are now as expected We currently on 16.12.4 on the ASR. We have a few of these, all on the same versions. So it seems it was maybe fixed in the 16.12.x releases then.
            landy Mike Stupalov added a comment -

            Yes, this is vendor bug which was in older ios-xe version(s) (see linked issue).
            It's seems as fixed now, and need to understand in which version it was fixed.

            This is only one device which you have with "issue"?
            (if no, specify the minimum version of ios-xe).

            landy Mike Stupalov added a comment - Yes, this is vendor bug which was in older ios-xe version(s) (see linked issue). It's seems as fixed now, and need to understand in which version it was fixed. This is only one device which you have with "issue"? (if no, specify the minimum version of ios-xe).

            People

              landy Mike Stupalov
              kentbjoh Kent Johannessen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: