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

IP SLA Graphs Missing Data

Details

    • Vendor Bug
    • Resolution: Won't Fix
    • Minor
    • None
    • Professional Edition
    • None

    Description

      We are looking at using Cisco IP SLA monitors and using the graphs in Observium to display the data. The issue is we have configured Cisco path-jitter IP SLA in the router which shows RTT, Jitter, and Packet Loss from the router CLI. Example output below.

       

      IPSLA operation id: 200
      Latest RTT: 274 milliseconds
      Latest operation start time: 17:19:41 MDT Thu Jul 11 2019
      Latest operation return code: OK

      ---- Path Jitter Statistics ----

      Hop IP 10.16.254.255:
      Round Trip Time milliseconds:
      Latest RTT: 274 ms
      Number of RTT: 100
      RTT Min/Avg/Max: 272/274/307 ms
      Jitter time milliseconds:
      Number of jitter: 65
      Jitter Min/Avg/Max: 1/4/32 ms
      Packet Values:
      Packet Loss (Timeouts): 0
      Out of Sequence: 0
      Discarded Samples: 0

       

      The issue we have is the graph for the IP SLA in observium only graphs the RTT value and not the jitter or packet loss value.

       

      I have attached a picture of the graph from the IP SLA page in Observium for the same IP SLA operation as the text example above.

      Attachments

        1. discovery.txt
          979 kB
        2. image-2019-07-12-16-40-24-517.png
          image-2019-07-12-16-40-24-517.png
          2 kB
        3. IP_SLA.JPG
          IP_SLA.JPG
          60 kB
        4. myagent.snmpwalk
          4.95 MB
        5. poller.txt
          1.15 MB

        Activity

          [OBS-3053] IP SLA Graphs Missing Data
          landy Mike Stupalov added a comment -

          Unsupported by firmware.

          landy Mike Stupalov added a comment - Unsupported by firmware.
          landy Mike Stupalov added a comment -

          yah, nope.. impossible, need support from device firmware. Write Cisco TAC.

          landy Mike Stupalov added a comment - yah, nope.. impossible, need support from device firmware. Write Cisco TAC.
          ajackson Andy Jackson added a comment -

          outputs attached

          ajackson Andy Jackson added a comment - outputs attached
          landy Mike Stupalov added a comment -

          Try with r9972.

          Please attach debug for discovery and polling (after update and with worked path-jitter):

          ./discovery.php -d -m sla -h <device>
          		 
          ./poller.php -d -m sla -h <device>

          landy Mike Stupalov added a comment - Try with r9972. Please attach debug for discovery and polling (after update and with worked path-jitter): ./discovery.php -d -m sla -h <device> ./poller.php -d -m sla -h <device>
          landy Mike Stupalov added a comment -

          And there exactly written https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipsla/configuration/xe-3s/asr1000/sla_path_jitter.html:

          MIB support for the Path Jitter operation is not provided.

          landy Mike Stupalov added a comment - And there exactly written https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipsla/configuration/xe-3s/asr1000/sla_path_jitter.html : MIB support for the Path Jitter operation is not provided.
          landy Mike Stupalov added a comment -

          Ok, I see this trouble and this is Vendor bug issue.
          SLA Path-jitter currently unsupported by MIBs and (probably) not exist in snmp output data.

          See this links (just shows that this feature unsupported):
          https://community.cisco.com/t5/switching/ipsla-path-jitter-monitoring/td-p/2131136
          https://community.cisco.com/t5/routing/ip-sla-path-jitter-snmp-mib/td-p/2890302

          I propose to write a request in Cisco TAC for this issue.

          But anyway, probably I can do some "local hacks" if you do snmp dump again, but with configured path-jitter and enabled target.
          Because as I see in dump there is this tagret/path-jitter disabled.

          landy Mike Stupalov added a comment - Ok, I see this trouble and this is Vendor bug issue. SLA Path-jitter currently unsupported by MIBs and (probably) not exist in snmp output data. See this links (just shows that this feature unsupported): https://community.cisco.com/t5/switching/ipsla-path-jitter-monitoring/td-p/2131136 https://community.cisco.com/t5/routing/ip-sla-path-jitter-snmp-mib/td-p/2890302 I propose to write a request in Cisco TAC for this issue. But anyway, probably I can do some "local hacks" if you do snmp dump again, but with configured path-jitter and enabled target. Because as I see in dump there is this tagret/path-jitter disabled.

          People

            landy Mike Stupalov
            ajackson Andy Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: