08-30-2012 03:01 AM
Hi all,
I want to do something with IP SLA and started by estabilishing a baseline.
I'm trying to check history on an ASR. I tested same config on a 3845 and was forgetting the "history filter all". After this I could see history table on 3845 but still history is empty on the ASR1006. The operation started because I can see information with "show ip sla statistics".
Anyone can help me to know if i missed something or maybe this is not supported in ASR1006?
Thank you
re-ld-tcc-02_ASR1006#show vers
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-ADVIPSERVICESK9-M), Version 15.2(1)S2, RELEASE SOFTWARE (fc1)
...
System image file is "bootflash:asr1000rp2-advipservicesk9.03.05.02.S.152-1.S2.bin"
...
re-ld-tcc-02_ASR1006#show ip sla statistics
IPSLAs Latest Operation Statistics
IPSLA operation id: 3
Latest RTT: 138 milliseconds
Latest operation start time: 10:56:41 GMT+1 Thu Aug 30 2012
Latest operation return code: OK
Number of successes: 3
Number of failures: 0
Operation time to live: 271 sec
re-ld-tcc-02_ASR1006#show ip sla history
Point by point History
Entry = Entry number
LifeI = Life index
BucketI = Bucket index
SampleI = Sample index
SampleT = Sample start time (milliseconds)
CompT = RTT (milliseconds)
Sense = Response return code
Entry LifeI BucketI SampleI SampleT CompT Sense TargetAddr
08-30-2012 01:49 PM
I am not too familiar with the ASR but have you set up history collection within your SLA's?
history distributions-of-statistics-kept size
history enhanced [interval seconds] [buckets number-of-buckets]
history hours-of-statistics-kept hours
history statistics-distribution-interval milliseconds
IP SLAs maintains the following three types of history statistics:
Note
* The IP SLAs UDP jitter operation does not support the IP SLAs History feature (statistics history
buckets) because of the large data volume involved with UDP jitter operations. This means that the
following commands are not supported for UDP jitter operations: history buckets-kept, history filter,
history lives-kept, samples-of-history-kept, and show ip sla history.
* The MIB used by IP SLAs (CISCO-RTTMON-MIB) limits the hours-of-statistics kept for the UDP
jitter operation to two hours. Configuring a larger value using the history hours-of-statisticshours
global configuration change will not increase the value beyond two hours. However, the Data
Collection MIB can be used to collect historical data for the operation.
Hope this is helpful to you.
09-06-2012 09:56 AM
Thanks ngoldwat,
I tryed the line you suggested and saw the text you provided before (please post original document link). I believe my intention is getting the operation snapshot history which is coming empty. however I do get something with "show ip sla enhanced-history collection-statistics" but still all values 0 (all error counters) and no ping values.
The configuration
ip sla 3
icmp-echo 8.8.8.8 source-ip 41.72.61.70
threshold 1000
timeout 1000
frequency 10
history distributions-of-statistics-kept 2
history enhanced interval 10 buckets 10
ip sla schedule 3 life 300 start-time now ageout 3600
Outputs:
show ip sla statistics
IPSLA operation id: 3
Latest RTT: 139 milliseconds
Latest operation start time: 17:48:44 GMT+1 Thu Sep 6 2012
Latest operation return code: OK
Number of successes: 30
Number of failures: 0
Operation time to live: 0
re-ld-tcc-02_ASR1006#show ip sla history
Point by point History
Entry = Entry number
LifeI = Life index
BucketI = Bucket index
SampleI = Sample index
SampleT = Sample start time (milliseconds)
CompT = RTT (milliseconds)
Sense = Response return code
Entry LifeI BucketI SampleI SampleT CompT Sense TargetAddr
re-ld-tcc-02_ASR1006#show ip sla enhanced-history distribution-statistics
Point by point Enhanced History
Entry = Entry Number
Int = Aggregation Interval
BucI = Bucket Index
StartT = Aggregation Start Time
Pth = Path index
Hop = Hop in path index
Comps = Operations completed
OvrTh = Operations completed over thresholds
SumCmp = Sum of RTT (milliseconds)
SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)
SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)
TMax = RTT maximum (milliseconds)
TMin = RTT minimum (milliseconds)
Entry Int BucI StartT Pth Hop Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin
3 10 1 9128394636 1 1 1 0 138 19044 0 138 138
3 10 2 9128404636 1 1 1 0 139 19321 0 139 139
3 10 3 9128414636 1 1 1 0 139 19321 0 139 139
3 10 4 9128424636 1 1 1 0 139 19321 0 139 139
3 10 5 9128434636 1 1 1 0 139 19321 0 139 139
3 10 6 9128444636 1 1 1 0 139 19321 0 139 139
3 10 7 9128454636 1 1 1 0 138 19044 0 138 138
3 10 8 9128464636 1 1 1 0 139 19321 0 139 139
3 10 9 9128474636 1 1 1 0 138 19044 0 138 138
3 10 10 9128484636 1 1 1 0 139 19321 0 139 139
re-ld-tcc-02_ASR1006#show ip sla enhanced-history collection-statistics
Entry number: 3
Aggregation Interval: 10
Bucket Index: 1
Aggregation start time 17:47:14.104 GMT+1 Thu Sep 6 2012
Target Address: 8.8.8.8
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
Bucket Index: 2
Aggregation start time 17:47:24.104 GMT+1 Thu Sep 6 2012
Target Address: 8.8.8.8
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
Bucket Index: 3
Aggregation start time 17:47:34.104 GMT+1 Thu Sep 6 2012
Target Address: 8.8.8.8
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
And goes on to bucket 10 every 10 seconds.
09-06-2012 12:10 PM
Hey,
The full command is show ip sla history [operation-number] [tabular | full]
Here is a general link for IOS & NX-OS IP SLA along with one to History Statistics.
The Feature Navigator site is helpful as well.
If you still find yourself running into issues send the output of
- sh mem
- sh ip sla app
- sh ip sla statistics aggregated
- sh ip sla configuration
To debug:
- debug ip sla error
- debug ip sla trace
09-07-2012 09:24 AM
Hi ngoldwat,
The command without parameter is the same as tabular. But full I get output below:
re-ld-tcc-02_ASR1006#show ip sla history 3 full
Entry number: 3
History is not configured
But, I managed to find the problem. The configuration was missing "history lives-kept 1" which defaults to (zero)
re-ld-tcc-02_ASR1006(config-ip-sla-echo)#history ?
...
lives-kept Maximum number of history lives to collect
...
re-ld-tcc-02_ASR1006(config-ip-sla-echo)#history lives-kept ?
<0-2> Life size value (default 0)
According to this:
...
lives: Number of lives maintained in the history table for the operation. If you specify 0 lives, history is not collected for the operation.
...
The default value of 0 lives means that history is not collected for the operation.
...
The command history filter all must also be configured (to get successes)
Thank you for your time ngoldwat and I hope this may be of help.
Regards
Mario
09-12-2012 08:26 AM
A related post
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide