entry

Use this command to schedule an IP SLA entry to execute now or at a specific time. You can also set how often a test cycle occurs, the number of tests in a test cycle, the duration of the tests, and the delay between tests.

Syntax

entry ip-sla-entry {{[start {[time <yyyy-mm-dd:hh.mm.ss>] | [now] | [after <5-300>]}]} [duration <30-3600>] [frequency <30-3600>] [recurrence <120-7776000>] [repetitions <1-10>] {[reset] | [stop]}

Parameters

ip-sla-entry The IP SLA entry to schedule.
start time <yyyy-mm-dd:hh.mm.ss> | now | after <5-300> Specify the start time.
  • time—Schedule the entry to begin at a specific time in the following format

    yyyy-mm-dd:hh.mm.ss

  • now—Schedule the entry to begin immediately.
  • after—Schedule the entry to begin after the specified number of seconds.
duration <30-3600> The length, in seconds, of each test in the test cycle. The default value is 30 seconds.
frequency <30-3600> The interval, in seconds, between each test in the test cycle. The default value is 30 seconds
recurrence 
<0, 120-7776000> The time, in seconds, between the end of one test cycle and the start of the next test cycle.

A value of zero indicates that the test cycle will run only once for the IP SLA entry. A value other than zero means that test cycles will continue until you stop them with either the reset or stop parameters.

The maximum value, 7776000, is 90 days. One day is 86400.

See the “Usage” section below for information on how to set the recurrence parameter to avoid overlapping test cycles.

repetitions <1-10> The number of tests to run in each test cycle. The default value is 1.
reset Stop the test cycle and clear the IP SLA entry‘s schedule attributes.
stop Stop the test cycle but do not clear the IP SLA entry‘s schedule attributes.

Defaults

Any parameter not specified remains at its current value.

Mode

IP SLA Entry Schedule Configuration.

Usage

If you change the value of recurrence from the default, you may inadvertently schedule the new test cycle to begin while the current test cycle is still running. Overlapping test cycles are skipped.

To avoid this from happening, ensure that the recurrence value is greater than the run time of a test cycle (repetitions * (duration + frequency)).

For example, if an IP SLA entry is scheduled for two repetitions with a duration of 60 seconds and a frequency of 30 seconds, the run time of the test cycle 180 seconds. To avoid overlapping test cycles, you must set the value of recurrence to greater than 180 seconds.

If the specify the start time using the now or after options, the running config will display the start time in the yyyy-mm-dd:hh.mm.ss format.

Example

This example shows how that the test cycles of the IP SLA entry 2 are scheduled to begin 60 seconds after the command is entered. Each test cycle will include five tests that are each 60 seconds long. The interval between the tests in the test cycle is set to 60 seconds. The next test cycle will begin one second after the current test cycle ends.

System(su-config)->sla schedule
System(su-config-sla-sched)->entry 2 start after 60 recurrence 601 duration 60 repetitions 5 frequency 60