[an error occurred while processing this directive] [an error occurred while processing this directive]

Typical Autoinstallation Process on the SRX650 Services Gateway

When a services gateway is powered on for the first time, it performs the following autoinstallation tasks:

  1. The new services gateway sends out DHCP, BOOTP, RARP, or SLARP requests on each connected interface simultaneously to obtain an IP address.

    If a DHCP server responds, it provides the device with some or all of the following information:

    • An IP address and subnet mask for the autoinstallation interface.
    • The location of the TFTP (typically), Hypertext Transfer Protocol (HTTP), or FTP server on which the configuration file is stored.
    • The name of the configuration file to be requested from the TFTP server.
    • The IP address or hostname of the TFTP server.

      If the DHCP server provides only the hostname, a DNS server must be available on the network to resolve the name to an IP address.

    • The IP address of an intermediate device if the configuration server is on a different LAN segment from the new device.
  2. After the new services gateway acquires an IP address, the autoinstallation process on the device attempts to download a configuration file in the following ways:
    1. If the DHCP server specifies the host-specific configuration file (boot file) hostname.conf, the device uses that filename in the TFTP server request. (In the filename, hostname is the hostname of the new device.) The autoinstallation process on the new device makes three unicast TFTP requests for hostname.conf. If these attempts fail, the device broadcasts three requests to any available TFTP server for the file.
    2. If the new device cannot locate hostname.conf, the autoinstallation process unicasts or broadcasts TFTP requests for a default device configuration file called network.conf, which contains hostname-to-IP address mapping information, to attempt to find its hostname.
    3. If network.conf contains no hostname entry for the new services gateway, the autoinstallation process sends out a DNS request and attempts to resolve the new device's IP address to a hostname.
    4. If the new services gateway can determine its hostname, it sends a TFTP request for the hostname.conf file.
    5. If the new services gateway is unable to map its IP address to a hostname, it sends TFTP requests for the default configuration file router.conf.
  3. After the new services gateway locates a configuration file on a TFTP server, autoinstallation downloads the file, installs the file on the device, and commits the configuration.

To configure a network for services gateway autoinstallation, complete the following tasks:

  • Configure a DHCP server on your network to meet your network requirements.

    You can configure a services gateway to operate as a DHCP server. For more information, see the JUNOS Software Administration Guide.

  • Create one of the following configuration files, and store it on a TFTP server in the network:
    • A host-specific file with the name hostname.conf for each services gateway undergoing autoinstallation. Replace hostname with the name of a services gateway. The hostname.conf file typically contains all the configuration information necessary for the device with this hostname.
    • A default configuration file named router.conf with the minimum configuration necessary to enable you to telnet into the new services gateway for further configuration.
  • Physically attach the services gateway to the network using the Gigabit Ethernet interface.
  • 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 DNS server in the network.
  • If the new device 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 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 service. Connect this interface to the new device.
  • If you are using hostname.conf files for autoinstallation of host-specific configuration files, you must also complete the following tasks:
    • Configure the DHCP server to provide a hostname.conf filename to each new services gateway. Each device uses its hostname.conf filename to request a configuration file from the TFTP server. Copy the necessary hostname.conf configuration files to the TFTP server.
    • Create a default configuration file named network.conf, and copy it to the TFTP server. This file contains IP address-to-hostname mapping entries. If the DHCP server does not send a hostname.conf filename to a new device, the services gateway uses network.conf to resolve its hostname based on its IP address.

      Alternatively, you can add the IP address-to-hostname mapping entry for the new services gateway to a DNS database file.

      The device uses the hostname to request a hostname.conf file from the TFTP server.

Updated: 2009-04-23

[an error occurred while processing this directive]