What is Zero Touch Provisioning?
Zero Touch Provisioning
Zero Touch Provisioning (ZTP) is an SR OS feature that automatically configures a node by obtaining the required information from the network and provisioning the device with minimal manual intervention and configuration. When new devices that support ZTP are connected and boot up, the device is auto-provisioned.
Note: ZTP is not supported over IPv6.
For more information about ZTP and the specific devices on which it is supported, see the ZTP information in the device documentation: Nokia 7450 Ethernet Services Switch, 7750 Service Router, 7950 Extensible Routing System, and Virtualized Service Router Basic System Configuration Guide.
RESTCONF APIs are also available for ZTP; see the API documentation on the Network Developer Portal.
NSP Zero Touch Provisioning provides tools to generate ZTP files for device provisioning, and adds device information to discovery rules, reducing manual work required for device discovery.
ZTP NE details can be exported from NSP in JSON format. The exported data can facilitate the automation of the DHCP server configuration.
NSP uses the following intent types to facilitate ZTP:
-
create_http_user: creates a user identity to connect with the NSP file server
Note: creation of an HTTP user is a one time operation. Only one HTTP user is supported.
-
ztp-profile: saves a set of NE information and discovery information that can be applied to multiple devices. For example, you can create a profile for MDM managed 7250 IXR devices and one for classically managed 7250 IXR devices.
Create a ZTP profile for each set of generic parameters you need.
-
day-0-ztp: takes the parameters provided in a ZTP profile and parameters that are unique to a device and creates configuration and provisioning files for the device on the NSP file server.
Create a Day-0 intent for each device.
When the intents have been executed, the device is added to the list in the Device Management, ZTP Process list view. The device can then be powered on and discovery can be initiated.
The ZTP process list can be cleaned up using a workflow.
Important! NSP Zero Touch Provisioning has been tested with 7250 IXR-e, 7250 IXR-s and 7750 SR 14s NEs. Contact Nokia for assistance in using ZTP with any other NE type.
ZTP performed on certain releases of SR OS may fail due to an HTTP chunking issue. The affected SR OS releases are 21.2 R1-R2, 21.5 R1-R2, 21.7 R1-R2, 20.10 R3-R10 21.10 R1-R3 and 22.2 R1-R2.
NSP ZTP Prerequisites
NSP ZTP requires the following prerequisites:
-
Prerequisites for device ZTP must be in place; see the NE documentation.
-
The ZTP intents zip files must be downloaded from the Nokia NSP software download site.
-
An HTTP user must be created using the create_http_user intent type; see How do I configure Zero Touch Provisioning?.
-
A unified discovery rule for the NE must be created in NSP. The administrative state of the unified discovery rule must be Down.
-
For classic devices, a classic discovery rule for the NE must be created in NSP and associated to the unified discovery rule. The administrative state of the classic discovery rule must be Down.
-
If you plan to upgrade your device as part of the ZTP process, for example if you purchased a device with Release 20.7 software and want to use it with Release 20.10, you must import the new software image to the NSP file server before performing ZTP. If you do this, you can configure the new target software version as part of the ZTP profile intent.
-
If you plan to use an IP resource pool for IP address assignment, the IP resource pool must be created in NSP.
See the NSP System Administrator Guide for information about using IP resource pools. Also see the Resource Administration tutorial on the Network Developer Portal.
Process
Figure 6-1, Zero Touch Provisioning process shows the ZTP process with NSP.
When the ZTP Day-0 intent is created and synchronized:
-
Configuration and provisioning files are created and stored on the file server
-
Paths and filenames for the configuration and provisioning files are saved to the database
-
Device IP addresses is added to the relevant discovery rules
-
The device is added to the list of ZTP Process network elements in NSP.
If all ZTP intents are synchronized, the operator turns up the discovery rule and powers on the node. The node completes ZTP and reboots.
After rebooting, MDM managed devices are ready to manage. For classic devices, a setting must be changed in CLI to prepare the device for discovery; see How do I configure Zero Touch Provisioning?.
Figure 6-1: Zero Touch Provisioning process
