Should I be seeing more than 1 Historical Traceroutes listed on the ICMP Path Echo Operation Details web page?
If so, what settings do I need to make in the router CLI to make the additional traceroutes appear?
In general, I do not find an adequate explanation of the idea of history either in the VNQM Administrators guide, or in the Cisco documentation - or the relation between the two.
After using the wizard a bunch of times, and getting only the 1st hop, I found in the current Administrators Guide, (VoIP and Network Quality Manager Version 4.2.2, revised 10/9/2015) near the bottom of p54 there's an important warning:
Configuring devices for ICMP echo path operations
Devices where you want to monitor ICMP echo path operations must be manually configured.(italics mine) VNQM reads hop results from history data. Therefore, the operation needs to be configured to save data to the history table. To enable history data support, configure the following items:
- History filter (all)
- Number of buckets kept (min value: 1)
- Number of samples kept (max value: 30)
- Lives of history kept (min value: 1) [BTW the max is 2]
To configure history data support, follow the directions based on your IOS version on the following Cisco links:
That last link has this import detail:
Router(config-rtr)# buckets-of-history-kept size
For a pathEcho probe, sets the number of paths to store (italics mine). For all other probes, sets the number (size) of data points to be kept. Applies to the following operations: IP/ICMP Echo, IP/ICMP Path Echo, UDP Echo, TcpConnect, DNS, DLSw, and SNA Echo.
But it's not clear if "paths" here are historical paths or what. So I'm experimenting with it. Also note that these are IOS 12.2 command syntax - it changed at some point (12.4?) to history buckets-kept (different word order ... each parson's son parses parts differently). It's clear that path echo is a horse of a different color, as far as IP SLA goes.
If ICMP Path Echo must be manually configured to work with VNQM, it should be removed from the wizard, I think. But I bet it has to do with router model and IOS version and typically poor Cisco documentation. That's not SolarWinds fault, and they do provide babelfish for some of this.
So my latest failure is:
no ip sla schedule 201510233 life forever start-time now
no ip sla 201510233
ip sla 201510233
path-echo x.x.x.x
threshold 1000
frequency 300
history lives-kept 1
samples-of-history-kept 30
history buckets-kept 4
paths-of-statistics-kept 12
history filter all
ip sla schedule 201510233 life forever start-time now
First I delete the operation from VNQM, then I do the CLI commands, then I discover the operations on the router in VNQM.
I only see the most recent occurrence under Historical Traceroutes. I can see the samples from 4 buckets via show ip sla history full. I've tried varying the numbers on lives, samples, buckets, and paths.
Anyone see anything I missed?