Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Supported Platforms

Understanding Zero Touch Provisioning

Note: To see which platforms support Zero Touch Provisioning, in a browser, go to Feature Explorer. In the Explore Features section of the Feature Explorer page, select All Features. In the Features Grouped by Feature Family box, select Zero Touch Provisioning. You can also type the name of the feature in the Search for Features edit box. In previous Junos OS releases on EX Series switches, Zero Touch Provisioning was called EZ Touchless Provisioning. Search for that feature name if you want to know if this feature is supported on EX Series switches.

Zero Touch Provisioning allows you to provision new Juniper Networks switches in your network automatically, without manual intervention. When you physically connect a switch to the network and boot it with a default factory configuration, it attempts to upgrade the Junos OS software automatically and autoinstall a configuration file from the network. To make sure you have the default factory configuration loaded on the switch, issue the request system zeroize command on the switch you want to provision.

The switch uses information that you configure on a Dynamic Host Configuration Protocol (DHCP) server to locate the necessary software image and configuration files on the network. If you do not configure the DHCP server to provide this information, the switch boots with the preinstalled software and default factory configuration.

The Zero Touch Provisioning process will either upgrade or downgrade the Junos OS version. During an downgrade:

  • On an EX Series switch, If you downgrade to a software version earlier than Junos OS Release 12.2, in which Zero Touch Provisioning is not supported, the configuration file autoinstall phase of the Zero Touch Provisioning process does not happen.
  • On an EX Series switch, to downgrade to a software version that does not support resilient dual-root partitions (Junos OS Release 10.4R2 or earlier), you must perform some manual work on the switch. For more information, see Understanding Resilient Dual-Root Partitions on Switches.

When you boot a switch with the default factory configuration, the following process happens:

  1. If DHCP option 43, suboption 00 (the name of the software image file on the FTP, HTTP, or TFTP server) is configured, the switch compares the version of the provided software image to the version of the software installed on the switch.

    Note: When the DHCP server cannot use suboption 00, configure the image file using suboption 04. If both suboption 00 and suboption 4 are defined, suboption 04 is ignored.

  2. If DHCP option 43, suboption 02 (a symbolic link to the software image file on the FTP, HTTP, or TFTP server), the switch compares the version of the provided software image to the version of the software installed on the switch.
    • If the Junos OS versions are different, the switch downloads the software image from the FTP, HTTP, or TFTP server, installs the Junos OS, and reboots using the default factory configuration.
    • If the software versions are the same, the switch does not upgrade the software.
  3. If DHCP option 43, suboption 01 (the name of the configuration file on the FTP, TFTP, or HTTP server is configured, the switch compares the version of the provided configuration file to the version of the configuration file on the switch.

    If DHCP option 43 suboption 01 is not specified, the switch uses the default factory configuration.

    If the configuration file version on the FTP, HTTP, or TFTP server is newer than the configuration file on the switch, the configuration file is updated on the switch.

    If both DHCP option 43 suboption 01 and suboption 2 are specified, suboption 01 is processed before suboption 02. The Junos OS is upgraded, and then the configuration file is applied.

  4. If DHCP option 43, suboption 03 (the transfer mode setting) is configured, the switch accesses the FTP, HTTP, or TFTP server using the specified transfer mode setting–for example, FTP.

    If DHCP option 43, suboption 03, is not configured, TFTP becomes the transfer mode automatically.

  5. If DHCP option 43, suboption 04 (the name of the software image file on the FTP, HTTP, or TFTP server) is configured, the switch compares the version of the provided software image to the version of the software installed on the switch.

    Note: When the DHCP server cannot use suboption 00, configure the image file using suboption 04. If both suboption 00 and suboption 4 are defined, suboption 04 is ignored.

  6. If DHCP option 150 or option 66 is specified, the IP address of the FTP, HTTP, or TFTP server is configured.

    Note: You must configure either option 150 or option 66. If you configure both option 150 and option 66, option 150 takes precedence, and option 66 is ignored. Also, make sure you specify an IP address, not a hostname, because name resolution is not supported.

  7. (Optional) If DHCP option 7 is specified, you can configure one or more syslog servers.
  8. (Optional) If DHCP option 42 is specified, you can configure one or more NTP servers.
  9. (Optional) If DHCP option 12 is specified, you can configure the hostname of the switch.

Published: 2013-11-04

Supported Platforms

Published: 2013-11-04