IP SLA - History empty

k.desrosiers · ‎09-03-2010

Hello,

We have a MAN network with two ASR 1002-F as core devices and C1812 routers (with IOS c181x-advipservicesk9-mz.151-1.T.bin) at remote devices.

How can I see the history (results) for the probes in CLI (without a IP SLA Analyser)?

I enabled the ip sla responder on one of the ASR.

I configured 2 probes (101 and 102) on one of the C1812 for testing.

Here is the conf for one of them:

snmp-server community public RO
snmp-server host x.x.x.x version 2c public
snmp-server host x.x.x.x version 2c public syslog
ip sla logging traps
snmp-server enable traps syslog
!
ip sla 101
icmp-echo 172.25.1.129 source-ip 172.25.1.131
tag ICMP-ECHO
frequency 180
exit
ip sla schedule 101 start-time now life forever
!
! Configure thresholds and reactions.
ip sla reaction-configuration 101 react rtt threshold-type immediate threshold-value 10 5 action-type trapOnly

With a debug, the probes seem to work as well as the proactive threshold....

C1812#
Sep 3 16:11:42.878 PARIS_E: IPSLA-OPER_TRACE:OPER:101 slaSchedulerEventWakeup

Sep 3 16:11:42.878 PARIS_E: IPSLA-OPER_TRACE:OPER:101 Starting an operation

Sep 3 16:11:42.878 PARIS_E: IPSLA-OPER_TRACE:OPER:101 Starting icmpecho operation - destAddr=172.25.1.129, sAddr=172.2                   5.1.131

Sep 3 16:11:42.878 PARIS_E: IPSLA-OPER_TRACE:OPER:101 Sending ID: 17

Sep 3 16:11:42.882 PARIS_E: IPSLA-OPER_TRACE:OPER:101 ID:17, RTT=4

Sep 3 16:11:42.882 PARIS_E: IPSLA-OPER_TRACE:OPER:101 Updating result

AND:

Sep 3 16:21:36.046 PARIS_E: IPSLA-OPER_TRACE:OPER:102 slaSchedulerEventWakeup

Sep 3 16:21:36.046 PARIS_E: IPSLA-OPER_TRACE:OPER:102 Starting an operation

Sep 3 16:21:36.046 PARIS_E: IPSLA-OPER_TRACE:OPER:102 VRF: CG58     lookup table id: 1

Sep 3 16:21:36.046 PARIS_E: IPSLA-OPER_TRACE:OPER:102 Starting icmpecho operation - destAddr=10.40.1.145, sAddr=10.40.1.146

Sep 3 16:21:36.046 PARIS_E: IPSLA-OPER_TRACE:OPER:102 Sending ID: 18

Sep 3 16:21:36.058 PARIS_E: IPSLA-OPER_TRACE:OPER:102 ID:18, RTT=12

Sep 3 16:21:36.058 PARIS_E: IPSLA-OPER_TRACE:OPER:102 Updating result

Sep 3 16:21:36.062 PARIS_E: %RTT-3-IPSLATHRESHOLD: IP SLAs(102): Threshold exceeded for rtt

But I can't see nothing in here:

C1812#sh ip sla history 101
        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

C1812#

ccarring · ‎09-03-2010

Hi KEvin,

Almost there... just two small commands to add!

With IP SLA, once you schedule an operation, you'll have to delete the operation to make changes to it (a small inconvenience).

I verified this in my lab just now, here's what you need to do:

!
ip sla 101
icmp-echo 172.25.1.129 source-ip 172.25.1.131
tag ICMP-ECHO
frequency 180

history lives 1

history filter all

exit
ip sla schedule 101 start-time now life forever

!

History lives tells it to keep one lifetime of the history (1 or 2 are the only options), and the filter command tells it what to keep... by default, that's nuttin'.

That should do it, then you can see the history in the CLI output.

Let me know if that helps?

k.desrosiers · ‎09-03-2010

Hello,

Thanks for your help!

It's working!

Now that I have my basis, I'll try to configure some other probes like udp-jitter... and see what Centreon (Nagios) can do with that!

BRGs,

Katy

C1812#sh 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
101   1          1          1          2530102164 120        1          172.25.1.129
102   1          1          1          2530192212 12         1          10.40.1.145