155
Configuration guidelines
•
To have a job successfully run a command, check that the specified view and command are valid.
The system does not verify their validity.
•
The configuration interface, view, and user status that you have before job execution restores even
if the job has run a command that changes the user interface (for example,
telnet
,
ftp
, and
ssh2
),
the view (for example,
system-view
and
quit
), or the user status (for example,
super)
.
•
The jobs run in the background without displaying any messages except log, trap and debugging
messages.
•
In the modular approach:
{
Every job can have only one view and up to 10 commands. If you specify multiple views, the
one specified the last takes effect.
{
Input a view name in its complete form. Most commonly used view names include
monitor
for
user view,
system
for system view,
GigabitEthernet
x/x/x, or
Ten-GigabitEthernet
x/x/x for
Ethernet interface view, and
Vlan-interfacex
for VLAN interface view.
{
The time ID (
time-id
) must be unique in a job. If two time and command bindings have the same
time ID, the one configured last takes effect.
Scheduling a job in the non-modular approach
Perform one of the following commands in user view to schedule a job:
To do…
Use the command…
Remarks
Schedule a job to run a command
at a specific time
schedule job at
time
[
date
]
view
view
command
Schedule a job to run a command
after a delay
schedule job delay
time
view
view
command
Required
Use either command
NOTE:
•
If you execute the
schedule job
at
command or the
schedule
job delay
command
repeatedly, the last
configuration takes effect.
•
If you change the system time
by using the
clock datetime
,
clock summer-time
, or
clock
timezone
command after you
configure a scheduled job, the
job configuration becomes
invalid automatically.
Scheduling a job in the modular approach
Follow these steps to configure a scheduled job:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a job and enter job view
job
job-name
Required
