Minor 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
Activity
yah, nope.. impossible, need support from device firmware. Write Cisco TAC.
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>
|
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.
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.
Another thing we noticed is the IP SLA shows up in Observium as "34" instead of the name of the IP SLA. Image below
The device we are using is a Cisco ASR 920 and the IP SLA is called "path-jitter." It doesn't look like this device supports the "icmp-jitter" option. We get the same result using "path-jitter" by including the option "targetOnly." This might be why it is not showing up correctly. Also this device is not accessible from the internet as it is inside an isolated lab environment. I have attached the myagent.snmpwalk file as requested. Your second command however came back with no response from the device.
The definition for the "path-jitter" operation is "Path Discovered ICMP Jitter Operation"
Can you provide temporary snmp access to device?
If possible, please write me mike@observium.org
, my devel IP is 77.222.50.30.
If this is completely unacceptable, please make snmp dump from this device (by commands below) and also send it to the specified address.
snmpbulkwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
|
snmpbulkwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
|
Unsupported by firmware.