Filter
Top Products
Chapter 5
Configuring Autoinstallation
If you are setting up many J-series Services Routers, autoinstallation can help automate
the configuration process by loading configuration files onto new or existing routers
automatically over the network. You can use either the J-Web configuration editor
or CLI configuration editor to configure a Services Router for autoinstallation. The
J-Web interface does not include Quick Configuration pages for autoinstallation.
This chapter contains the following topics:
■ Autoinstallation Terms on page 81
■ Autoinstallation Overview on page 82
■ Before You Begin on page 84
■ Configuring Autoinstallation with a Configuration Editor on page 85
■ Verifying Autoinstallation on page 86
Autoinstallation Terms
Before configuring autoinstallation, become familiar with the terms defined in
Table 40 on page 81.
Table 40: Autoinstallation Terms
DefinitionTerm
Automatic configuration of a Services Router over the network from a preexisting
configuration file that you create and store on a configuration server—typically a
Trivial File Transfer Protocol (TFTP) server. Autoinstallation takes place on a router
that is powered on without a valid configuration (boot) file or is configured specifically
for autoinstallation. Autoinstallation is useful for deploying multiple Services Routers
in a network.
autoinstallation
Configuration that takes place on a Services Router unable to locate a configuration
(boot) file. You can set up two default configuration files for autoinstallation on the
router: network.conf to specify IP address-to-hostname mappings for routers on the
network, or router.conf to provide just enough configuration for your subsequent
Telnet access.
default configuration
Host-specific configuration file for autoinstallation on a Services Router that contains
all the configuration information necessary for the router. In the filename, hostname
is replaced with the hostname you are assigning to the router.
hostname.conf
Autoinstallation Terms ■ 81