Table Of Contents

Scheduling CLI Commands

Examples

Scheduling CLI Commands

---

Last Updated: August 5, 2011

Beginning in Cisco UMG Release 8.0, you can schedule the execution of a block of CLI commands. Blocks of commands are entered interactively, using a symbol delimiter character to start and stop the execution. The execution of the block of commands begins in EXEC mode, but mode-changing commands are allowed in the command block.

The following limitations apply in Cisco UMG Release 8.6:

•The maximum size of the block of commands is 1024 characters ,including new lines.

•Commands in the block cannot use the comma "," character or the delimiter character. For example, if the delimiter character is configured to be "#", then that character cannot be used in the command blocks.

•Only system administrators can schedule the execution of blocks of commands.

•CLI commands are executed under system super-user privileges.

•Notification for the execution of these command blocks is not available. Error messages and results are available in log files only.

---

Caution Use caution when scheduling CLI commands. Interactive commands will cause the execution to hang. Some commands might cause system instability.

---

SUMMARY STEPS

1. kron schedule [name]

2. description

3. repeat every {number days at time |number weeks on day | number months on day date | number years on month month} at time

---

Note Instead of the repeat every command, you can optionally use one of the following commands:

•repeat once at time

•repeat daily at time

•repeat monthly on day date at time

•repeat weekly on day at time

•repeat yearly on month month at time

---

4. start-date date

5. stop-date date

6. commands delimiter

7. exit

8. show kron schedules

9. show kron schedule detail job

DETAILED STEPS

	Command or Action	Purpose
Step 1	kron schedule [name] Example: umg-1# kron schedule kron1011	Enters kron schedule configuration mode.
Step 2	description description Example: umg-1(kron-schedule)# description backup	(Optional) Enters a description for the scheduled kron job.
Step 3	repeat every {number days |number weeks on day | number months on day date | number years on month month} at time time Example: umg-1(kron-schedule)# repeat every 2 days at time 10:00	Specifies how often a recurring scheduled kron job occurs. To configure a one-time kron job, use the repeat once command. You can also optionally use one of the other repeat commands listed in the previous note.
Step 4	start-date date Example: umg-1(kron-schedule)# start-date 05/30/2009	Specifies the start date for the recurring scheduled kron job to occur.
Step 5	stop-date date Example: umg-1(kron-schedule)# stop-date 10/20/2009	Specifies the stop date for the recurring scheduled kron job to occur.
Step 6	commands delimiter Example: umg-1(kron-schedule)# commands % Enter CLI commands to be executed. End with the character `%'. Maximum size is 1024 characters, it may not contain symbol %. %show version show running-config config t hostname aaa % umg-1(kron-schedule)#	Enters an interactive mode where commands in the the command block can be entered for the scheduled kron job. Use the delimiter character to delimit the command block. Note Any symbol can be a delimiter. The "%" symbol is shown for example purposes only.
Step 7	exit	Exits kron schedule configuration mode.
Step 8	show kron schedules Example: umg-1# show kron schedule	Displays a list of scheduled kron jobs.
Step 9	show kron schedule detail job name Example: umg-1# show kron schedule detail job kron1011	Displays information about a specific scheduled kron job.

Examples

The following is sample output from the show kron schedules command:

umg-1# show kron schedules

Name          Schedule                            Commands

krj1          Every 1 days at 12:34               show ver,sh run,conf t,host...

Total: 1

The following is sample output from the show kron schedule detail job command:

umg-1# show kron schedule detail job krj1

Job Name        krj1

Description

Schedule        NOT SET

Last Run        NEVER

Last Result

Next Run        NEVER

Active          from Feb 15, 2010 until INDEFINITE

Disabled

CLI Commands

                show ver

                sh run

                conf t

                hostname aaa

umg-1#