IP SLA History

Posted on 2008-11-14
Last Modified: 2012-06-27
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.

Question by:dlarock
    LVL 32

    Expert Comment


    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;

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

    harbor235 ;}

    Author Comment

    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.
    LVL 32

    Accepted Solution


    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 ;}

    Author Closing Comment

    thank you.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    In the world of WAN, QoS is a pretty important topic for most, if not all, networks. Some WAN technologies have QoS mechanisms built in, but others, such as some L2 WAN's, don't have QoS control in the provider cloud.
    I recently attended Cisco Live! in Las Vegas, a conference that boasted over 28,000 techies in attendance, and a week of hands-on learning hosted by a solid partner with which Concerto goes to market.  Every year, Cisco displays cutting-edge technol…
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

    730 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now