Configuring Autoinstallation of Configuration Files (CLI Procedure)
Autoinstallation is the automatic configuration of a device over the network from a
pre-existing configuration file that you create and store on a configuration server—typically
a Trivial File Transfer Protocol (TFTP) server. You can use autoinstallation to automatically
configure new devices and to deploy multiple devices from a central location in the
network.
No configuration is required on a new switch (a switch that has the factory default
configuration file), because it is an automated process. However, to specify
autoinstallation to run when you power on a switch already installed in your network,
you can enable it by specifying one or more interfaces, protocols, and configuration
servers to be used for autoinstallation.
Before you explicitly enable and configure autoinstallation on the switch, perform these
tasks as needed for your network’s configuration:
•
Have a service available—typically Dynamic Host Configuration Protocol (DHCP)—to
assign an IP address to the switch
•
Configure a DHCP server on your network to meet your network requirements. You can
configure an EX Series switch to operate as a DHCP server. For more information, see
“Configuring DHCP Services (J-Web Procedure)” on page 549.
•
Create one of the following configuration files, and store it on a TFTP server (or HTTP
server or FTP server) in the network:
•
A host-specific file with the name
hostname.conf
for each switch undergoing
autoinstallation. Replace
hostname
with the name of a switch. The
hostname.conf
file typically contains all the configuration information necessary for the switch with
this hostname.
•
A default configuration file named
switch.conf
with the minimum configuration
necessary to enable you to telnet into the new switch for further configuration.
•
Physically attach the switch to the network using a Gigabit Ethernet port.
•
If you configure the DHCP server to provide only the TFTP server hostname, add an IP
address-to-hostname mapping entry for the TFTP server to the DNS database file on
the Domain Name System (DNS) server in the network.
•
If the new switch is not on the same network segment as the DHCP server (or other
device providing IP address resolution), configure an existing device as an intermediate
device to receive TFTP and DNS requests and forward them to the TFTP server and
the DNS server. You must configure the LAN or serial interface on the intermediate
device with the IP addresses of the hosts providing TFTP and DNS services. Connect
this interface to the new switch.
•
If you are using
hostname.conf
files for autoinstallation, you must also complete the
following tasks:
•
Configure the DHCP server to provide a
hostname.conf
filename to each new switch.
Each switch uses its
hostname.conf
filename to request a configuration file from
Copyright © 2010, Juniper Networks, Inc.
432
Complete Software Guide for Junos
®
OS for EX Series Ethernet Switches, Release 10.3
Summary of Contents for JUNOS OS 10.3 - SOFTWARE
Page 325: ...CHAPTER 17 Operational Mode Commands for System Setup 229 Copyright 2010 Juniper Networks Inc ...
Page 1323: ...CHAPTER 56 Operational Mode Commands for Interfaces 1227 Copyright 2010 Juniper Networks Inc ...
Page 2841: ...CHAPTER 86 Operational Commands for 802 1X 2745 Copyright 2010 Juniper Networks Inc ...
Page 3367: ...CHAPTER 113 Operational Mode Commands for CoS 3271 Copyright 2010 Juniper Networks Inc ...
Page 3435: ...CHAPTER 120 Operational Mode Commands for PoE 3339 Copyright 2010 Juniper Networks Inc ...
Page 3529: ...CHAPTER 126 Operational Mode Commands for MPLS 3433 Copyright 2010 Juniper Networks Inc ...