 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
The JUNOScope software configuration management module lets users manage device configurations that are currently running on connected devices and configurations that have been archived or imported in the JUNOScope CVS repository.
The configuration management module lets you view and edit current device configurations using the Configuration Browser and the Configuration Editor.
(Configuration > Current >View) Provides a GUI for viewing the setup of the currently committed configuration that is running on a selected device. Use the Configuration Browser to view the configuration statement hierarchy in brief or detailed mode, including viewing statement inheritance. For more information, see Using the Configuration Browser.
(Configuration > Current > Edit) Provides a GUI for editing a configuration on a selected device. Use the Configuration Editor to modify the existing configuration. You can also use the Configuration Editor to commit the modified configuration, as well as discard any unwanted configuration changes. If a device has redundant Routing Engines, committed changes will be synchronized on both the master and backup. For more information, see Using the Configuration Editor.
The configuration management module lets you archive and import devices configurations into the JUNOScope CVS repository. The repository holds version of device configurations. Each device can have many different versions of a configuration in the repository. Once a device configuration version is stored in the JUNOScope repository, you can manipulate it, including tag, audit, compare, display, or restore.
(Configuration > Repository > Archive) Lets you download the active configuration file from a device or group of devices. The downloaded version of the configuration file is archived in the JUNOScope software CVS repository. You can save configuration archive operations and combine them with other operations, such as restore and inventory scan, to be run concurrently or sequentially in real time or at a scheduled interval. For more information, see Archiving and Manipulating Device Configurations.
(Configuration > Repository > Archive Tags) Lets you associate tags with a configuration version so you can compare it with another version. The comparison can be made with the active or current configuration or with a version from the JUNOScope CVS repository. For more information about tagging device configurations, see Setting Up Archived Configuration Tags and Auditing Configurations and Partial Configurations.
(Configuration > Repository > Audit Configurations) Lets you check for differences between device configuration versions in the JUNOScope CVS repository for one or more devices. For more information about auditing differences in device configurations, see Setting Up Archived Configuration Tags and Auditing Configurations and Partial Configurations.
(Configuration > Repository > Compare) Lets you compare the differences between the contents of two revisions of a configuration file that you select in JUNOScope. By default, the JUNOScope software compares the newer revision of a configuration file to an older one. You can also select to compare an older revision of a configuration file with a newer one. For more information, see Comparing Configuration Files.
(Configuration > Repository > Display) Displays the contents of a configuration file revision that you select in JUNOScope. For more information, see Displaying a Configuration File.
(Configuration > Repository > Transfer on Commit) Lets you configure devices to transfer its currently active configuration to JUNOScope each time a candidate configuration is committed. For more information, see Configuring the JUNOScope Server for Transfer on Commit.
(Configuration > Repository > Import) Lets you import into JUNOScope a portion or all of a device configuration that you have saved in ASCII file format to a file on the local file system. The imported configuration is stored in the CVS repository. You can then compare, display, or restore the imported configuration. For more information about importing configuration files, see Importing and Deleting Configuration Files.
(Configuration > Repository > Restore) Uploads an archived configuration file to the device from which it was archived or uploads an imported configuration to a selected device. JUNOScope locks the device configuration and loads the new configuration on the device, overriding or merging (discarding) the old configuration. JUNOscope issues a commit confirmed command and a commit-configuration JUNOScript XML tag command. If the target device has installed and configured dual Routing Engines, JUNOScope issues a commit synchronize command. JUNOScope then unlocks the configuration. If an error occurs, JUNOScope issues a rollback command, causing the configuration to revert to the last saved configuration.
You can save configuration restore operations and combine them with other operations, such as archive and inventory scan, to be run concurrently or sequentially in real time or at a scheduled interval.
For more information, see Restoring a Configuration File.
(Configuration > Repository > Delete) Lets you delete user imported configuration files from the JUNOScope CVS repository. For more information see Importing and Deleting Configuration Files.
(Configuration > Repository > Save) Lets you save archived configurations to a local file system. For more information see Archiving and Manipulating Device Configurations.
(Configuration > Repository > Edit) Lets you edit an archived configuration file. For more information see Archiving and Manipulating Device Configurations.
(Configuration > Repository > Scripts) Lets you Lets you manage JUNOS-based scripts. JUNOS-based scripts such as commit scripts, operation (op) scripts, and event scripts can be imported into the JUNOScope CVS repository from the local file system and deployed to a group of routers.You can also view, edit, compare, and disable these scripts. For more information see Managing JUNOS Scripts.
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |