Using Zero Touch Provisioning
Using Zero Touch Provisioning
Using Zero Touch Provisioning
The router provides you the option of having the router auto configure. Field technicians need only mount
the router, connect to the power and attach cables in easily-accessible ports, and initiate zero touch provisioning.
This feature helps operators to reduce total cost of ownership (TCO) by simplifying the network deployment.
Note ZTP is supported only on the RSP3 module on the NCS 4206-16 Series routers.
ZTP is supported on the NCS 4201-4202 routers.
Note Routers running ZTP must be able to connect to a DHCP server and a TFTP server, download the configuration
template, and begin operation.
Note ZTP must be initiated only from the R0 that has the active RSP module in a dual RSP scenario.
Note If you type yes at the prompt, the system configuration is saved in the nvRAM and the ZTP process terminates.
Note The operations center can initiate any of the above packets over the network to establish a
connection to the DHCP server.
2. When the first packet on any VLAN is detected, the router initiates a DHCP session to a DHCP server
over that VLAN.
3. After a DHCP session is established, the router uses the DHCP option 150 and initiates to download a
configuration file from the TFTP server. The configuration file in the TFTP server should have anyone
of the following naming format:
a. PID-chassis-mac-address
The PID specifies NCS and chassis-mac-address specifies the unique chassis MAC address printed
on the chassis. For example, if the chassis mac-address is 00-01-02-03-04-06, then the config file
would be NCS-00-01-02-03-04-05.
b. network-confg
c. router-confg
d. ciscortr.cfg
e. cisconet.cfg
When the ZTP process initiates, the router creates an Ethernet flow point (EFP) and associates a bridge domain
interface (BDI) on the detected management VLAN.
The router creates the following configuration to establish a connection with the DHCP server and the TFTP
server. The BDI created for this purpose has description ZTP_BDI configured under the BDI interface.
Note Once the configuration file is downloaded successfully, you must save the configuration file (write memory)
and reload the router.
Caution You may choose to remove the ZTP_BDI configuration before reloading the router.
Building configuration...
Current configuration : 216 bytes
!
interface GigabitEthernet0/0/1
no ip address
media-type auto-select
no negotiation auto
service instance 12 ethernet
encapsulation dot1q 1000
rewrite ingress tag pop 1 symmetric
bridge-domain 12
!
end
!
interface BDI12
description ZTP_BDI
ip address dhcp
end
Effective Cisco IOS XE Amsterdam 17.3.2a, the router tries to learn the reachability to multiple DHCP servers
during ZTP. Hence multiple DHCP discovery messages are sent out during this phase. The router goes through
all the DHCP offer messages received and selects an appropriate DHCP server based on the priority decided
based on below rules:
1. The DHCP server reachable via untagged interface have higher priority than the one via tagged. In case
of tagged, the one reachable via an interface learned using VRRP packets has higher priority.
2. If multiple DHCP servers are reachable via similar interfaces mentioned in previous rule, the one reachable
via higher physical port number has higher priority.
DHCP Server
The following is a sample configuration to set up a Cisco router as a DHCP server:
This configuration creates a DHCP pool of 30.30.1.x addresses with 30.30.1.0 as the subnet start. The IP
address of the DHCP server is 30.30.1.6. Option 150 specifies the TFTP server address. In this case, the DHCP
and TFTP server are the same.
The DHCP pool can allocate from 30.30.1.1 to 30.30.1.19 with the exception of 30.30.1.6, which is the DHCP
server itself.
TFTP Server
The TFTP server stores the bootstrap configuration file.
The following is a sample configuration (network– confg file):
hostname test-router
!
{ncs router-specifc configuration content}
!
end