IP SLA History

I am looking for information that explains the purpose of buckets and how they relate to keeping history with IP SLA's.  .  I really dont understand what they are for and how the other commands relate to them (distribution, lives kept, distribution interval, history).

I think if I explain what I am looking to do it may help in regards as to what I am looking for.  We have two core locations and 20 spokes.  Each spoke has a connection to each core location.  I want to enable ip slas from each spoke to both core locations.  I want to keep approximately 72 hours worth of data (even more if possible).  I would like to aggregate the data and potentially store the history of it.  It would be nice to have a 72 hour aggregated history and a lifetime aggregated history (or 30 day if lifetime is excessive).

Any real world examples would be greatly appreciated.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


A bucket is a logical way to preserve data collected via the ip sla monitoring process.

Each time IP SLAs starts an operation, a new bucket is created until the number of history buckets matches the specified size or the operation's lifetime expires. History buckets do not wrap (that is, the oldest information is not replaced by newer information). The operation's lifetime is defined by the ip sla monitor schedule global configuration command.

An IP SLAs operation can collect history and capture statistics. By default, the history for an IP SLAs operation is not collected. If history is collected, each history bucket contains one or more history entries from the operation. When the operation type is ICMP path echo, an entry is created for each hop along the path that the operation takes to reach its destination. The type of entry stored in the history table is controlled by the filter-for-history command. The total number of entries stored in the history table is controlled by the combination of the samples-of-history-kept, buckets-of-history-kept, and lives-of-history-kept commands

You can pull the data via SNMP MIBs from your devices using the following SNMP MIBs;

    * CISCO-RTTMON-ICMP-MIB.my (ICMP Jitter operation MIB)
    * CISCO-RTTMON-IP-EXT-MIB.my (Extension of RTTMON-MIB to support IP SLAs IPv6 operations)
    * CISCO-RTTMON-MIB.my (Base MIB, everyone needs this one)
    * CISCO-RTTMON-RTP-MIB.my (Real Time Protocol (RTP) operation support MIB)
    * CISCO-RTTMON-TC-MIB.my (IP SLA Textual Conventions MIB file)

harbor235 ;}
dlarockAuthor Commented:
I read the exact same paragraphs from the CCO doc's for IP SLA's.  So from what I can tell with IP SLA's they cant be aggregated?  But looking at the commands available I also see

#sh ip sla ?
  application       IP SLAs Application
  authentication    IP SLAs Authentication Information
  configuration     IP SLAs Configuration
  enhanced-history  IP SLAs Enhanced History
  group             IP SLAs Group Scheduling/Configuration
  history           IP SLAs History
  responder         IP SLAs Responder Information
  statistics        IP SLAs Statistics

Exactly what is the enhanced-history for?

Or when you do

#sh ip sla statistics ?
  <1-2147483647>  Entry Number
  aggregated      IP SLAs Statistics Aggregated

It shows an option for aggregated data?

Any input on those.

Enhanced history allocates additional buckets for additional retention of collected data, default bucket size is 50, with enhanced history
it is 100 buckets. The amount of additional buckets you can allocate is a function of available memory.

Performance statistics are stored in "buckets" that separate the accumulated data. Each bucket consists of data accumulated over the specified time interval.  Enhanced history allows data to be retained for a larger  time interval. However, soon or later the data will be overwritten and the data needs to be pulled via SNMP for archival.

There are also different commands available in different sub mode

harbor235 ;}

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dlarockAuthor Commented:
thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.