- play_arrow Working With Network Director
- play_arrow About Network Director
- play_arrow Installing Network Director
- play_arrow Accessing Network Director
- play_arrow Understanding Network Director System Administration and Preferences
- play_arrow Getting Started with Network Director
-
- play_arrow Working with the Dashboard
- play_arrow About the Dashboard
- play_arrow Using the Dashboard
- play_arrow Dashboard Widget Reference
-
- play_arrow Working in Build Mode
- play_arrow About Build Mode
- play_arrow Discovering Devices
- play_arrow Setting Up Sites and Locations Using the Location View
- Understanding the Location View
- Setting Up the Location View
- Creating a Site
- Configuring Buildings
- Configuring Floors
- Setting Up Closets
- Assigning and Unassigning Devices to a Location
- Changing the Location of a Device
- Deleting Sites, Buildings, Floors, Wiring Closets, and Devices
- Configuring Outdoor Areas
- play_arrow Building a Topology View of the Network
- play_arrow Creating Custom Device Groups
- play_arrow Configuring Quick Templates
- play_arrow Configuring Device Settings
- play_arrow Configuring Authentication, Authorization, and Access for Your Network
- play_arrow Configuring Interfaces and VLANs
- Understanding Port Profiles
- Creating and Managing Port Profiles
- Assigning and Unassigning Port Profiles from Interfaces
- Managing Auto Assignment Policies
- Creating Auto Assignments
- Configuring Easy Config Setup
- Understanding Port Groups
- Creating and Managing Port Groups
- Understanding VLAN Profiles
- Creating and Managing VLAN Profiles
- Assigning a VLAN Profile to Devices or Ports
- play_arrow Configuring Firewall Filters (ACLs)
- play_arrow Configuring Class of Service (CoS)
- play_arrow Configuring Media Access Control Security (MACsec)
- play_arrow Configuring Link Aggregation Groups (LAGs)
- play_arrow Creating and Managing Fabrics
- Understanding Junos Fusion
- Understanding Junos Fusion Enterprise
- Software Requirements for Junos Fusion
- Creating and Managing Fusion Configuration Templates
- Managing Fusion Fabrics
- Creating and Managing Satellite Software Upgrade Groups
- Understanding Layer 3 Fabrics
- User Privileges Required for the DHCP and File Server While Using Zero Touch Provisioning
- Managing Layer 3 Fabrics
- Creating Layer 3 Fabrics
- Editing Layer 3 Fabrics
- Viewing Layer 3 Fabric Connectivity
- Performing Layer 3 Fabric Connectivity Checks
- play_arrow Configuring VRRP Profiles
- play_arrow Managing Network Devices
- Viewing the Device Inventory Page
- Physical Topology
- Viewing Profiles Assigned to a Device
- Viewing the Physical Inventory of Devices
- Viewing Licenses With Network Director
- Viewing a Device's Current Configuration from Network Director
- Assigning Devices to Logical Category
- Accessing a Device’s CLI from Network Director
- Accessing a Device’s Web-Based Interface from Network Director
- Deleting Devices
- Rebooting Devices
- Viewing Virtual Machines
-
- play_arrow Monitoring Devices and Traffic
- play_arrow About Monitor Mode
- play_arrow Monitoring Traffic
- play_arrow Monitoring Client Sessions
- play_arrow Monitoring Devices
- play_arrow Monitoring and Analyzing Fabrics
- play_arrow Monitoring Virtual Networks
- play_arrow General Monitoring
- play_arrow Monitor Reference
- 802.11 Packet Errors Monitor
- Access vs. Uplink Port Utilization Trend Monitor
- Current Sessions Monitor
- Current Sessions by Type Monitor
- Error Trend Monitor
- Equipment Summary By Type Monitor
- Node Device Summary Monitor
- Port Status Monitor
- Port Status for IP Fabric Monitor
- Port Utilization Monitor
- Power Supply and Fan Status Monitor
- Resource Utilization Monitor for Switches, Routers, and Virtual Chassis
- Status Monitor for Junos Fusion Systems
- Status Monitor for Layer 3 Fabrics
- Status Monitor for Switches and Routers
- Status Monitor for Virtual Chassis
- Status Monitor for Virtual Chassis Members
- Top Talker - Wired Devices Monitor
- Traffic Trend Monitor
- Unicast vs Broadcast/Multicast Monitor
- Unicast vs Broadcast/Multicast Trend Monitor
- User Session Details Window
- Virtual Chassis Topology Monitor
- VC Equipment Summary By Type Monitor
-
- play_arrow Using Fault Mode
- play_arrow About Fault Mode
- play_arrow Using Fault Mode
- play_arrow Fault Reference
-
- play_arrow Working in Report Mode
- play_arrow About Report Mode
- play_arrow Creating and Managing Reports
- play_arrow Report Reference
-
- play_arrow Working with Network Director Mobile
- play_arrow About Network Director Mobile
- play_arrow Getting Started with Network Director Mobile
- play_arrow Working in the Network Director Mobile Dashboard Mode
- play_arrow Working in the Network Director Mobile Devices Mode
-
ON THIS PAGE
Configuring and Monitoring Zero Touch Provisioning
Zero touch provisioning (ZTP) allows you to provision new switches in your network automatically—without manual intervention. When you physically connect a switch to a network and boot it with the factory-default configuration, the switch attempts to upgrade the Junos OS software automatically and autoinstall a configuration file from the network.
The switch uses information that you configure on a Dynamic Host Control Protocol (DHCP) server to determine whether to perform these actions and to locate the necessary software image and configuration files on the network. You can configure the DHCP server by using a zero touch provisioning profile. If you do not configure a DHCP server, the switch boots with the preinstalled software and the default configuration.
The type of DHCP server that you want to use determines whether Network Director configures the DHCP server for you or whether you must manually configure the DHCP server. If you select CentOS or Ubuntu DHCP servers, Network Director configures the DHCP server by using the details that you specified in the zero touch provisioning profile. If you use any other DHCP server, you must manually configure the DHCP server. For such DHCP servers, you can use Network Director only to monitor the switches once they are provisioned. For details on configuring a DHCP server manually, see the DHCP server documentation.
For more information on zero touch provisioning for switches, see Understanding Zero Touch Provisioning.
Before you begin, ensure that you have the necessary privileges on the FTP and the file server that Network Director uses for zero touch provisioning..
For detailed information about DHCP and DHCP options, see RFC2131 (http://www.ietf.org/rfc/rfc2131.txt ) and RFC2132 (http://www.ietf.org/rfc/rfc2132.txt). These documents refers to Internet Systems Consortium (ISC) DHCP version 4.2. For more information about this version, see http://www.isc.org/software/dhcp/documentation.
Configuring Zero Touch Provisioning
Before you begin:
Ensure that the switch has access to the following network resources:
The DHCP server that provides the location of the software image and configuration files on the network
See your DHCP server documentation for configuration instructions.
The File Transfer Protocol (anonymous FTP), the Hypertext Transfer Protocol (HTTP) server, or the Trivial File Transfer Protocol (TFTP) server on which the software image and configuration files are stored. If you are using an FTP server, ensure that the FTP server is configured to enable anonymous access. Refer to your FTP server documentation to know more about this.
Note:Although TFTP is supported, we recommend that you use FTP or HTTP instead, because these transport protocols are more reliable.
(Optional) A Network Time Protocol (NTP) server to perform time synchronization on the network
(Optional) A system log (syslog) server to manage system log messages and alerts
Identify the type of DHCP server that you will be using for zero touch provisioning:
CentOS DHCP Server—If your DHCP server uses the following command to restart the server, then select CentOS as the DHCP server type:
content_copy zoom_out_mapservice dhcpd restart
Ubuntu DHCP Server—If your DHCP server uses the following command to restart the server, then select Ubuntu as the DHCP server type:
content_copy zoom_out_mapservice isc-dhcp-server restart
Other—If your server is not an ISC DHCP server running on Linux operating system, then you must select Other and configure the DHCP server manually.
CentOS 6.10 is the supported or qualified version of CentOS for the DHCP server in Network Director 4.1 release.
For information about the CentOS and Ubuntu versions supported by Network Director Release 4.1, see the Supported Platforms section of the Network Director Release Notes.
To configure zero touch provisioning:
Specifying the Software Image and Configuration Details
To specify the software image, configuration file, and the IP address range to be configured on the DHCP server:
Reviewing and Modifying Zero Touch Provisioning Settings
From this page, you can save or make changes to a zero touch provisioning profile:
To make changes to the profile, click the Edit button associated with the configuration you want to change.
Alternatively, you can click the appropriate buttons in the zero touch provisioning workflow at the top of the page that corresponds to the configuration you want to change.
When you are finished with your modifications, click Review to return to this page.
To save a zero touch provisioning profile or to save modifications to the settings of an existing profile, click Finish.
What To Do Next
For manual configuration, use the DHCP configuration file to manually configure the DHCP server. If you selected the DHCP server as CentOS or Ubuntu, Network Director uploads the software image to the file server that you specified. If you selected any other DHCP server, you must manually upload the software image to the file server and specify the path when you configure the DHCP server.
(Only for the CentOS or Ubuntu DHCP servers) For automatic configuration, Network Director configures the DHCP server with the details that you specified in the zero touch provisioning profile and uploads the software image to the file server that you specified.
Configuration Statements for Custom Configuration of DHCP Server
Insert the following configuration statements to the configuration file, if you want to upload a custom configuration file to the DHCP server:
system {
root-authentication {
encrypted-password "PASSWORD"; ## SECRET-DATA
}
}
event-options {
policy target_add_test {
events snmpd_trap_target_add_notice;
then {
raise-trap;
}
}
}
trap-group networkdirector_trap_group {
version all;
destination-port NDPORT;
categories {
link;
services;
authentication;
}
targets{
NDIP;
}
}
