Configuring Autoinstallation with a Configuration Editor

No configuration is required on a device on which you are performing autoinstallation, because it is an automated process. However, to simplify the process, you can specify one or more interfaces, protocols, and configuration servers to be used for autoinstallation.

To configure autoinstallation:

Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
Perform the configuration tasks described in Table 46.
If you are using the &j-web;, click Commit to view a summary of your changes, then click OK to commit the configuration. If you are using the CLI, commit the configuration by entering the commit command.
To check the configuration, see Verifying Autoinstallation.

Table 46: Configuring Autoinstallation

Task	J-Web Configuration Editor	CLI Configuration Editor
Navigate to the System level in the configuration hierarchy.	In the J-Web interface, select CLI Tools>Point and Click CLI. Next to System, click Configure or Edit.	From the [edit] hierarchy level, enter edit system
Enable autoinstallation.	Select Autoinstallation, and then click Configure.	Enter set autoinstallation configuration-servers url
Specify the URL address of one or more servers from which to obtain configuration files. For example: tftp://tftpconfig.sp.com ftp://user:password @sftpconfig.sp.com	Next to Configuration servers, click Add new entry. Type the location of the configuration server in the Url box. If a password is required for server access, type it into the Password box. Click OK to return to the Autoinstallation page.	Enter set autoinstallation configuration-servers url
Configure one or more Ethernet or serial interfaces to perform autoinstallation.	Next to Interfaces, click Add new entry. Type the name of the interface into the Interface name box—for example, ge-0/0/0. Click OK.	To set BOOTP and RARP on an Ethernet interface, enter set autoinstallation interfaces ge-0/0/0 bootp rarp
Configure one or two procurement protocols for each interface. The device uses the protocols to send a request for an IP address for the interface. BOOTP—Sends requests over all interfaces. RARP—Sends requests over Ethernet interfaces. SLARP—Sends requests over serial interfaces.	Next to the interface name, click Edit. Select one or two protocols to be used by autoinstallation over the interface—for example, Bootp and Rarp. Click OK.

Note: When there is a user-specified configuration for a particular interface, the factory default for that interface should be deleted. Having two configurations for the same device might lead to errors. For example, if PPP encapsulation is set on a T1 interface via user configuration while the factory default configuration configures CISCO HLDC on the same interface, then the interface might not come up and the following error will be logged in the message file: “DCD_CONFIG_WRITE_FAILED failed.”