Cisco Systems 4.1 Dust Collector User Manual


 
5-7
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 5 Understanding RME Device State Transition
States in RME 4.x
c. Provide the job policies and scheduling information.
d. Click on Submit button to submit the job.
At the scheduled time, the job is executed. For Job Execution there is no mandatory requirement for
the existence of any inventory or Config Archive data.
Configuration Changes Using NetConfig
To make configuration changes using NetConfig:
Step 1 Select a set of devices from the device selector that contains all of Pending, Normal and Pre-deployed
devices.
Step 2 Select a set of task types to be executed on these devices (Banner change, SNMP Credentials change
etc.).
For each device type and task type selected, you must enter the relevant parameters.
If a particular task requires inventory data (for example, Cable templates that require Interface details)
and if the required inventory data is not available, you will be prompted with a warning that the job
cannot include that particular task.
Step 3 Select any of these options to continue creating a job:
Different Configuration Versions Considered Failure—Requires at least one configuration version
to be archived.
Rollback failure policies—At job creation time, all the rollback policies for failure apply to devices
in Pending, Pre-Deployed and Normal states.
Sync Archive before Job execution—Applicable to devices in any of Pending, Pre-deployed and
Normal states. Failure to get the Config at job execution time fails the job.
Write running to startup configuration—Applicable to devices in any of Pending, Pre-Deployed and
Normal States.
Step 4 Submit the job after selecting the job policies and entering the job scheduling information.
At the job execution time, before deploying the Config changes:
If sync archive policy is selected, and if archival fails (at the time of execution) the job fails. (Current
behavior).
If rollback policy is selected, and no configuration has been collected for this device, the job
execution will proceed with a warning in the job results.
Job Options Description
Different Configuration Versions Considered
Failure
This requires at least one configuration version to
be archived.
Sync Archive before Job execution Applicable to devices in all of pending,
Pre-deployed and Normal states. Failure to get the
configuration at job execution time fails the job.
Write running to startup configuration Applicable to devices in all Pending,
Pre-Deployed and Normal States.