Managing Configuration File Associations

Junos Scope can be configured to act as an automatic configuration server (ACS). This means that Junos Scope can supply configuration files to several devices simultaneously. Junos Scope enables you to associate configuration files to a set of criteria that you specify. These criteria can be a set of conditions for parameters such as hostname, model, OS version and serial number with values that you specify; a pre-configured group of devices; or a combination of both. Junos Scope can simultaneously serve up to 200 devices.

You can import configuration files into Junos Scope from an external source using the Import feature (See Importing and Deleting Configuration Files) and can store the imported configuration files in the server.

When a device requests for a configuration file, the server compares the device attributes with the criteria and returns the URL of the first configuration file whose associated criteria match the device attributes. The device uses this URL to download the associated configuration file. If no configuration file is found, Junos Scope returns an HTTP 404 error to the device.

This chapter describes how Junos Scope supplies configuration files to devices. It also describes how you can create new configuration file associations, change the order of the configuration associations, and delete configuration file associations.

In order to use Junos Scope as an ACS, you must have:

This chapter includes the following topics: