10-36
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 10 Editing and Deploying Configurations Using Config Editor
Configuring Job Policies for Config Editor
Step 2 Select any of the following:
• Back to return to the Select Configs dialog box.
• Next to proceed to the Job Summary dialog box.
• Cancel to stop creating a Download job.
Configuring Job Policies for Config Editor
You can configure a default policy for job properties that applies to all future jobs.
You can also specify if the property can be modified when the job is created.
View Permission Report (Common Services > Server > Reports) to check if you have the required
privileges to perform this task.
To do this:
Step 1 Select RME > Admin > Config Mgmt > Config Job Policies.
The Config Job Policies dialog box appears.
Step 2 Select Config Editor from the application drop-down list.
Push Config to The method in which
the Configuration is
pushed. The two
methods are Running
and Startup
Do either of the following:
Select the Running option, if you want to replace the existing running
configuration on the device, with the selected configuration file. This is also
referred to as Write2Run.
Or
Select the Startup option, if you want to erase the contents of the device's
startup configuration and write the contents of the given file as the device's new
startup configuration. This is also referred to as Write2Start.
Configurations edited from Raw mode (.RAW) can be downloaded to both
Startup or Running configuration of the device.
Configurations edited from Processed mode (.PROC) can only be downloaded
to the Running configuration of the device.
Update RME
credentials after
deploy
Update the
credentials in DCR
after deployment, if
the deployed
commands include
any credentials
commands.
Choose this option if you want to update the DCR with the deployed credentials
commands such as SNMP community strings, Telnet username/password etc.
Write2Start does not support changing the RME credentials after deployment.
Field Description/Action Usage Notes