Cisco Catalyst 2960 Series, Configuration Manual

Page: 2033 / 2288

Example 2: "15 16 1 * *" would trigger an event at
4:15 p.m. on the first day of each month.
Example 3: "0 12 * * 1-5" would trigger an event at
noon on Monday through Friday of each week.
Example 4: "@weekly" would trigger an event at
midnight once a week on Sunday.
(Optional) Must be specified if a timer type other than
CRON is specified. Must not be specified if the
CRON timer type is specified. For watchdog and
countdown timers, the number of seconds and
milliseconds until the timer expires; for the absolute
timer, the calendar time of the expiration time. Time
is specified in SSSSSSSSSS[.MMM] format, where
SSSSSSSSSS must be an integer representing seconds
between 0 and 4294967295, inclusive, and where
MMM must be an integer representing milliseconds
between 0 and 999. An absolute expiration date is the
number of seconds and milliseconds since January 1,
1970. If the date specified has already passed, the
timer expires immediately. time
(Optional) Priority level at which the script will be
queued:
• queue_priority low--Specifies that the script is
to be queued at the lowest of the three priority
levels.
• queue_priority normal--Specifies that the script
is to be queued at a priority level greater than
low priority but less than high priority.
• queue_priority high--Specifies that the script is
to be queued at the highest of the three priority
levels.
• queue_priority last--Specifies that the script is
to be queued at the lowest priority level.
If more than one script is registered with the
"queue_priority_last" argument set, these scripts will
execute in the order in which the events are published.
The queue_priority argument specifies the
queuing priority, but not the execution
priority, of the script being registered. Note
If this argument is not specified, the default queuing
priority is normal.
queue_priority
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1951
event_register_timer