A DHCP relay agent is a host that forwards DHCP packets between clients and servers that do not reside on a shared physical subnet. Relay agent forwarding is distinct from the normal forwarding of an IP router where IP datagrams are switched between networks transparently.

DHCP clients use User Datagram Protocol (UDP) broadcasts to send DHCPDISCOVER messages when they lack information about the network to which they belong.

If a client is on a network segment that does not include a server, a relay agent is needed on that network segment to ensure that DHCP packets reach the servers on another network segment. UDP broadcast packets are not forwarded, because most routers are not configured to forward broadcast traffic. You can configure a DHCP relay agent to forward DHCP packets to a remote server by configuring a DHCP relay profile and configure one or more helper addresses in it. You can assign the profile to an interface or a VRF.

The figure below demonstrates the process. The DHCP client broadcasts a request for an IP address and additional configuration parameters on its local LAN. Acting as a DHCP relay agent, Router B picks up the broadcast, changes the destination address to the DHCP server's address and sends the message out on another interface. The relay agent inserts the IP address of the interface, on which the DHCP client’s packets are received into the gateway address (giaddr) field of the DHCP packet, which enables the DHCP server to determine which subnet should receive the offer and identify the appropriate IP address range. The relay agent unicasts the messages to the server address, in this case 172.16.1.2 (which is specified by the helper address in the relay profile).

These are the limitations for implementing DHCP relay feature:

• The multicast addresses are not supported. The helper-address command in DHCP relay profile submode supports valid unicast IP address as the helper address.

  Note	Configuring the helper-address command directly (not using profile) under a interface (such as BVI interface) is not supported.

• Only interface-id and remote-id DHCP option code are added by a relay agent while forwarding the packet to a DHCP server.

  Note	Configuring DHCP option code is not supported in DHCP relay profile submode.

The Dynamic Host Configuration Protocol (DHCP) client functionality enables the router interfaces to dynamically acquire the IPv4 or DHCPv4 or DHCPv6 server, and forwards the responses back to the correct Layer 2 address so that the correct device gets the correct configuration information.

DHCP has the ability to allocate IP addresses only for a configurable period of time, called the lease period. If the client is required to retain this IP address for a longer period beyond the lease period, the lease period must be renewed before the IP address expires. The client renews the lease based on configuration that was sent from the server. The client unicasts a REQUEST message using the IP address of the server. When a server receives the REQUEST message and responds with an ACK message. The lease period of the client is extended by the lease time configured in the ACK message.

RP/0/RP0/CPU0:ios# configure
Tue Aug 29 09:26:12.468 UTC
RP/0/RP0/CPU0:ios(config)# int mgmtEth 0/RP0/CPU0/0
RP/0/RP0/CPU0:ios(config-if)# ipv4 address dhcp
RP/0/RP0/CPU0:ios(config-if)# commit
Tue Aug 29 09:26:21.715 UTC
RP/0/RP0/CPU0:ios(config-if)# exit
RP/0/RP0/CPU0:ios(config)# int mgmtEth 0/RP0/CPU0/0
RP/0/RP0/CPU0:ios(config-if)# ipv6 address dhcp
dhcp  dhcp-client-options
RP/0/RP0/CPU0:ios(config-if)# ipv6 address dhcp
RP/0/RP0/CPU0:ios(config-if)# commit
Tue Aug 29 09:26:50.159 UTC

A DHCP server must be configured for IPv4, IPv6, or both communication protocols.

Note

For DHCPv6, a routing advertisement (RA) message must be sent to all nodes in the network that indicates which method is to be used to obtain the IPv6 address. Configure Router-advertise-daemon (radvd, install using yum install radvd) to allow the client to send the DHCP request. For example: interface eth3 { AdvSendAdvert on; MinRtrAdvInterval 60; MaxRtrAdvInterval 180; AdvManagedFlag on; AdvOtherConfigFlag on; prefix 2001:1851:c622:1::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; };

To setup a DHCP server:

1. Create the dhcpd.conf file (for IPv4, IPv6 or both communication protocols), dhcpv6.conf file (for IPv6) or both in the /etc/ directory. This configuration file stores the network information such as the path to the script, location of the ISO install file, location of the provisioning configuration file, serial number, MAC address of the chassis.

2. Test the server once the DHCP server is running:

   For example, for ipv4:

   1. Use MAC address of the chassis:

      host ncs1020 
      {
      hardware ethernet ab:cd:ef:01:23:45;
      fixed-address <ip address>;
      filename "http://<httpserver-address>/<path-to-image>/ncs1020-mini-x.iso";
      }

      Ensure that the above configuration is successful.
   2. Use serial number of the chassis:

      host demo {
      option dhcp-client-identifier "<chassis-serial-number>";
        filename "http://<IP-address>/<hardware-platform>-mini-x.iso";
        fixed-address <IP-address>;
      }

      The serial number of the chassis is derived from the BIOS and is used as an identifier.

      Example

      
      host 10.89.205.202 {
             hardware ethernet 40:55:39:56:0c:e8;
              option dhcp-client-identifier "<FCB2437B066>";
                if exists user-class and option user-class = "iPXE" {
                filename "http://10.89.205.127/box1/ncs1020-x64.iso";
             } else {
                 filename "http://10.89.205.127/box1/StartupConfig.cfg";
             }
             fixed-address 10.89.205.202;
          }
      

Before you use the iPXE boot, ensure that:

• DHCP server is set and is running.

• Management port of the NCS 1020 chassis is in UP state.

Use anyone of the following methods to invoke the iPXE boot process:

• via CLI terminal:

  Run the following command to invoke the iPXE boot process to reimage the chassis:

  reload bootmedia network location all

  Example:

  RP/0/RP0/CPU0:ios# reload bootmedia network location all
  Wed Jul  6 15:11:33.791 UTC
  Reload hardware module ? [confirm]

  The following example shows the output of the command:

  Preparing system for backup. This may take a few minutes especially for large configurations.
          Status report: node0_RP0_CPU0: BACKUP INPROGRESS 
  RP/0/RP0/CPU0:P1D_DT#   Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY 
  [Done]
  [FAILED] Failed unmounting /mnt/fuse/parser_server.
  [  OK  ] Unmounted /mnt/fuse/ftp.
  [  OK  ] Unmounted /mnt/fuse/nvgen_server.
  [  OK  ] Unmounted /boot/efi.
  [  OK  ] Unmounted /selinux.
  .
  .
  Output Snipped
  .
  .
  ..         *** Sirius ***
  System Initializing..
  ..
  
  ERROR: Class:0; Subclass:10000; Operation: 1004
  
  Shelf Assembly Reset
  Shelf Assembly Reset for P1
  
  
  ..         *** Sirius ***
  System Initializing..
  ..
  
  ERROR: Class:0; Subclass:10000; Operation: 1004
  .
  .
  Output Snipped
  .
  .
  
  NCS1010, Initializing Devices
  
  Booting from Primary Flash
  Aldrin: Programmed MI 10 
  .
  .
  Output Snipped
  .
  .
  Version 2.19.1266. Copyright (C) 2022 American Megatrends, Inc.                 
  BIOS Date: 05/20/2022 10:47:39 Ver: 0ACHI0410                                   
  Press <DEL> or <ESC> to enter setup.                                            
  TAM Chipguard Validate Observed DB Error: 0x48                                  
                                                                                  
  WARNING!!! TAM: Empty Chip DB                                                   
                                                                                  
                                                                                  
  Software Boot OK, Validated                                                     
                                                                                  
  iPXE initialising devices...ok                                                  
                                                                                  
                                                                                  
  iPXE 1.0.0+ (c2215) -- Open Source Network Boot Firmware -- http://ipxe.org     
  Features: DNS HTTP TFTP VLAN EFI ISO9660 ISO9660_grub Menu                      
  Trying net0-2051,net0-2052 and net0-2053...                                     
  net0-2051: 68:9e:0b:b8:71:1e using NII on NII-PCI06:00.0 (open)                 
    [Link:down, TX:0 TXE:0 RX:0 RXE:0]                                            
    [Link status: Unknown (http://ipxe.org/1a086194)]                             
  Configuring (net0-2051 68:9e:0b:b8:71:1e).................. Error 0x040ee186 (http://ipxe.org/040ee186)
  net0-2052: 68:9e:0b:b8:71:1f using NII on NII-PCI06:00.0 (open)                 
    [Link:up, TX:0 TXE:0 RX:18 RXE:14]                                            
    [RXE: 8 x "Operation not supported (http://ipxe.org/3c086083)"]               
    [RXE: 3 x "Error 0x440e6083 (http://ipxe.org/440e6083)"]                     
    [RXE: 3 x "The socket is not connected (http://ipxe.org/380f6093)"]
  Configuring (net0-2052 68:9e:0b:b8:71:1f).................. ok
  net0: fe80::6a9e:bff:feb8:711e/64
  net1: fe80::6a9e:bff:feb8:7121/64 (inaccessible)
  net2: fe80::6a9e:bff:feb8:7122/64 (inaccessible)
  net3: fe80::6a9e:bff:feb8:7123/64 (inaccessible)
  net0-2051: fe80::6a9e:bff:feb8:711e/64
  net0-2051: 2001:420:5446:2014::281:0/119 gw fe80::676:b0ff:fed8:c100 (no address)
  net0-2051: 2002:420:54ff:93:6a9e:bff:feb8:711e/64 gw fe80::fa4f:57ff:fe72:a640
  net0-2052: 10.4.33.44/255.255.0.0 gw 10.4.33.1
  net0-2052: fe80::6a9e:bff:feb8:711e/64
  net0-2053: fe80::6a9e:bff:feb8:711e/64
  Filename: http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso
  http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso... ok
  .
  .
  Output Snipped
  .
  .
  User Access Verification
  
  Username: cisco
  Password: 
  

• via BIOS interface:

  1. Reboot NCS 1020 using power cycle or console.

  2. Press Esc to enter BIOS.

  3. Select the Save & Exit tab of BIOS.

  4. Choose UEFI: iPXE Network Boot.

     The following example shows the output of the command:

     Preparing system for backup. This may take a few minutes especially for large configurations.
             Status report: node0_RP0_CPU0: BACKUP INPROGRESS 
     RP/0/RP0/CPU0:P1D_DT#   Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY 
     [Done]
     [FAILED] Failed unmounting /mnt/fuse/parser_server.
     [  OK  ] Unmounted /mnt/fuse/ftp.
     [  OK  ] Unmounted /mnt/fuse/nvgen_server.
     [  OK  ] Unmounted /boot/efi.
     [  OK  ] Unmounted /selinux.
     .
     .
     Output Snipped
     .
     .
     ..         *** Sirius ***
     System Initializing..
     ..
     
     ERROR: Class:0; Subclass:10000; Operation: 1004
     
     Shelf Assembly Reset
     Shelf Assembly Reset for P1
     
     
     ..         *** Sirius ***
     System Initializing..
     ..
     
     ERROR: Class:0; Subclass:10000; Operation: 1004
     .
     .
     Output Snipped
     .
     .
     
     NCS1010, Initializing Devices
     
     Booting from Primary Flash
     Aldrin: Programmed MI 10 
     .
     .
     Output Snipped
     .
     .
     Version 2.19.1266. Copyright (C) 2022 American Megatrends, Inc.                 
     BIOS Date: 05/20/2022 10:47:39 Ver: 0ACHI0410                                   
     Press <DEL> or <ESC> to enter setup.                                            
     TAM Chipguard Validate Observed DB Error: 0x48                                  
                                                                                     
     WARNING!!! TAM: Empty Chip DB                                                   
                                                                                     
                                                                                     
     Software Boot OK, Validated                                                     
                                                                                     
     iPXE initialising devices...ok                                                  
                                                                                     
                                                                                     
     iPXE 1.0.0+ (c2215) -- Open Source Network Boot Firmware -- http://ipxe.org     
     Features: DNS HTTP TFTP VLAN EFI ISO9660 ISO9660_grub Menu                      
     Trying net0-2051,net0-2052 and net0-2053...                                     
     net0-2051: 68:9e:0b:b8:71:1e using NII on NII-PCI06:00.0 (open)                 
       [Link:down, TX:0 TXE:0 RX:0 RXE:0]                                            
       [Link status: Unknown (http://ipxe.org/1a086194)]                             
     Configuring (net0-2051 68:9e:0b:b8:71:1e).................. Error 0x040ee186 (http://ipxe.org/040ee186)
     net0-2052: 68:9e:0b:b8:71:1f using NII on NII-PCI06:00.0 (open)                 
       [Link:up, TX:0 TXE:0 RX:18 RXE:14]                                            
       [RXE: 8 x "Operation not supported (http://ipxe.org/3c086083)"]               
       [RXE: 3 x "Error 0x440e6083 (http://ipxe.org/440e6083)"]                     
       [RXE: 3 x "The socket is not connected (http://ipxe.org/380f6093)"]
     Configuring (net0-2052 68:9e:0b:b8:71:1f).................. ok
     net0: fe80::6a9e:bff:feb8:711e/64
     net1: fe80::6a9e:bff:feb8:7121/64 (inaccessible)
     net2: fe80::6a9e:bff:feb8:7122/64 (inaccessible)
     net3: fe80::6a9e:bff:feb8:7123/64 (inaccessible)
     net0-2051: fe80::6a9e:bff:feb8:711e/64
     net0-2051: 2001:420:5446:2014::281:0/119 gw fe80::676:b0ff:fed8:c100 (no address)
     net0-2051: 2002:420:54ff:93:6a9e:bff:feb8:711e/64 gw fe80::fa4f:57ff:fe72:a640
     net0-2052: 10.4.33.44/255.255.0.0 gw 10.4.33.1
     net0-2052: fe80::6a9e:bff:feb8:711e/64
     net0-2053: fe80::6a9e:bff:feb8:711e/64
     Filename: http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso
     http://10.4.33.51/P1D_DT_05/ncs1010-x64.iso... ok
     .
     .
     Output Snipped
     .
     .
     User Access Verification
     
     Username: cisco
     Password: 
     

The ZTP process initiates when you boot the network-device with an IOS-XR image. The process starts only on the device that doesn't have a prior configuration.

This image depicts the high-level work flow of the ZTP process:

1. ZTP sends DHCP request to fetch the ZTP configuration file or user script. To help the Bootstrap server uniquely identify the device, ZTP sends below DHCP option.

   • DHCP(v4/v6) client-id=Serial Number

   • DHCPv4 option 124: Vendor, Platform, Serial-Number

   • DHCPv6 option 16: Vendor, Platform, Serial-Number

   The following is the default sequential flow of the ZTP process:

   • ZTP sends IPv4 DHCP request first on all the management port. In case there is a failure, then ZTP sends IPv6 DHCP request on all the management port.

   • ZTP sends IPv4 DHCP request first on all the data port. In case there is a failure, then ZTP sends IPv6 DHCP request on all the data port.

     The default sequential flow is defined in configuration file and you can modify the sequence using the configuration file.

2. DHCP server identifies the device and responds with DHCP response using one of the following options:

   DHCP server should be configured to respond with the DHCP options.

   • DHCPv4 using BOOTP filename to supply script/config location.

   • DHCPv4 using Option 67 (bootfile-name) to supply script/config location.

   • DHCPv6 using Option 59 (OPT_BOOTFILE_URL) to supply script/config location

3. The network device downloads the file from the web server using the URL location that is provided in the DHCP response.

4. The device receives a configuration file or script file from the HTTP server.

   Note	If the downloaded file content starts with !! IOS XR it is considered as a configuration file. If the downloaded file content starts with #! /bin/bash, #! /bin/sh or #!/usr/bin/python it is considered as a script file.

5. The device applies the configuration file or executes the script or binary in the default bash shell.

6. The Network device is now up and running.

Based on the business need, you can use a configuration or script file to initiate the ZTP process.

The configuration file content starts with !! IOS XR.

The following is the sample configuration file. You can automate all the configurations. For more information on creating ZTP configuration file, refer ZTP Configuration Files Creation.

Tue May 4 18:08:59.544 UTC
Building configuration...
!! IOS XR Configuration 7.7.1.22I
!! Last configuration change at Tue May 4 17:12:47 2021 by cisco
!
line console
exec-timeout 0 0
!
line default
exec-timeout 0 0
session-timeout 0
!
vty-pool default 0 20
alias alarms show alarms brief system active
interface MgmtEth0/RP0/CPU0/0
ipv4 address dhcp
no shut
!
interface MgmtEth0/RP0/CPU0/1
description noshut-interface-ztp
ipv4 address 10.127.60.160 255.255.255.0
no shut
!
interface MgmtEth0/RP0/CPU0/2
description noshut-interface-ztp
no shut
!
interface PTP0/RP0/CPU0/0
description noshut-interface-ztp
no shut
Cisco NCS 1020 System Setup and Software Installation Guide, IOS XR Release 7.7.x
19
Bring-up Cisco NCS 1020
Build your Configuration File
!
telnet vrf default ipv4 server max-servers 100a
ssh server v2
ssh server netconf vrf default
netconf-yang agent
ssh
!
netconf agent tty
grpc
router static
address-family ipv4 unicast
0.0.0.0/0 10.127.60.1
end

ZTP downloads and executes the script files. These script files include a programmatic approach to complete a task. For example, scripts created using IOS XR commands to perform patch upgrades. The first line of the file must contain #! /bin/bash or #! /bin/sh for ZTP to process the file as script. You can either use the ZTP bash script or the ZTP configuration file.

You can either use the ZTP bash script or the ZTP configuration file.

If you want to hardcode a script to be executed every boot, configure the following.

Router#configure 
Router(config)#ztp bootscript /disk0:/myscript
Router(config)#commit

The above configuration waits for the first data-plane interface to be configured and then wait an extra minute for the management interface to be configured with an IP address, to ensure that we have connectivity in the third-party namespace for applications to use. If the delay is not desired, use:

Router#configure
Router(config)#ztp bootscript preip /disk0:/myscript
Router(config)#commit

Note	When the above command is first configured, you will be prompted if you wish to invoke it now. The prompt helps with testing.

This is the example content of /disk0:/myscript:

host ncs1020_P1B_DT_08_ETH0 {
#hardware ethernet 68:9e:0b:b8:6f:5c ;
option dhcp-client-identifier "FCB2437B05N" ;
if exists user-class and option user-class = "iPXE" {
filename "http://10.33.0.51/P1B_DT_08/ncs1020-x64.iso";
} else {
filename "http://10.33.0.51/P1B_DT_08/startup.cfg";
}
fixed-address 10.33.0.19;
}

The following is the sample content of the ZTP bash script.

#! /bin/bash
#
# NCS1020 Demo Sample
# ZTP installation of config and day-0 SMU's
#
source ztp_helper

wget http://downloads.sourceforge.net/project/yourcode/application.tgz
#install the downloaded application.tgz

#Run XR CLI’s from the script
`xrcmd “show version”`

The following is the sample content of the ZTP configuration file.

Tue May 4 18:08:59.544 UTC
Building configuration...
!! IOS XR Configuration 7.7.1.22I
!! Last configuration change at Tue May 4 17:12:47 2021 by cisco
!
line console
exec-timeout 0 0
!
line default
exec-timeout 0 0
session-timeout 0
!
vty-pool default 0 20
alias alarms show alarms brief system active
interface MgmtEth0/RP0/CPU0/0
ipv4 address dhcp
no shut
!
interface MgmtEth0/RP0/CPU0/1
description noshut-interface-ztp
ipv4 address 10.127.60.160 255.255.255.0
no shut
!
interface MgmtEth0/RP0/CPU0/2
description noshut-interface-ztp
no shut
!
interface PTP0/RP0/CPU0/0
description noshut-interface-ztp
no shut
!
interface PTP0/RP0/CPU0/1
description noshut-interface-ztp
no shut
end

ZTP logs its operation on the flash file system in the directory /disk0:/ztp/. ZTP logs all the transaction with the DHCP server and all the state transition.

The following example displays the execution of a simple configuration script downloaded from a data interface using the command ztp initiate interface Ten 0/0/0/0 verbose, this script unshuts all the interfaces of the system and configure a load interval of 30 seconds on all of them.

2022-06-17 11:52:34,682  19292 [Xr           ] INF: Downloading the file to /tmp/ztp.script
2022-06-17 11:52:35,329  19292 [Report       ] INF: User script downloaded successfully. Provisioning in progress.
2022-06-17 11:52:35,330  19292 [Engine       ] DEB: ZAdmin, current state:active. Processing work: Config device work for ZAdmin. done = False
2022-06-17 11:52:35,330  19292 [ZAdmin       ] DEB: Proceeding to provision the router
2022-06-17 11:52:35,331  19292 [Engine       ] DEB: ZAdmin, current state:active. Processing work: ZAdmin: Apply configuration. done = False
2022-06-17 11:52:35,331  19292 [Engine       ] INF: ZAdmin, current state:active: state tag changed to provision
RP/0/RP0/CPU0:Jun 17 11:52:35.341 UTC: pyztp2[140]: %INFRA-ZTP-4-CONFIG_INITIATED : ZTP has initiated config load and commit operations
2022-06-17 11:52:35,339  19292 [Env          ] DEB: No MTU configs detected
2022-06-17 11:52:35,340  19292 [Engine       ] DEB: ZAdmin, current state:active. Processing work: ZAdmin: Apply configuration. done = False
2022-06-17 11:52:35,354  19292 [Xr           ] DEB: Will apply the following config: /disk0:/ztp/customer/config.candidate
2022-06-17 11:52:35,354  19292 [Xr           ] INF: Applying user configurations
2022-06-17 11:52:35,355  19292 [Configuration] INF: Provisioning via config replace
2022-06-17 11:52:54,656  19292 [Configuration] INF: Configuration has been applied
2022-06-17 11:52:54,656  19292 [Engine       ] DEB: ZAdmin, current state:active. Processing work: Sending standby sync message. done = False
2022-06-17 11:52:54,663  19292 [Engine       ] DEB: ZAdmin, current state:active. Processing work: [privileged] getting engine status. done = False
2022-06-17 11:52:54,664  19292 [Engine       ] DEB: ZAdmin, current state:active. Processing work: ZAdmin: Execute post-configuration script. done = False
2022-06-17 11:52:55,212  19292 [Env          ] INF: Env::cleanup, success:True, exiting:False
2022-06-17 11:52:55,213  19292 [ZtpHelpers   ] DEB: Executing: source /pkg/bin/ztp_helper.sh && echo -ne  | xrcmd "show running-config"
2022-06-17 11:52:55,825  19292 [Env          ] INF: Executing command ip netns exec vrf-default /sbin/dhclient -4 -cf /etc/dhcp/dhclient.conf.ztp -lf /var/lib/dhcp/dhclient.leases.ztp -sf /etc/dhcp/dhclient-script.ztp2 -r Mg0_RP0_CPU0_0 to release IP
2022-06-17 11:52:56,968  19292 [Xr           ] INF: Removing linux route with ip 10.33.0.63
2022-06-17 11:52:57,023  19292 [Engine       ] INF: ZAdmin, current state:active, exit code:success
2022-06-17 11:52:57,023  19292 [Engine       ] INF: ZAdmin, current state:final, exit code:success: state changed to final
2022-06-17 11:52:59,737  19292 [Engine       ] DEB: ZAdmin, current state:final, exit code:success. Processing work: Sending standby sync message. done = False
2022-06-17 11:52:59,738  19292 [Engine       ] WAR: ZAdmin, current state:final, exit code:success: work is ignored: work=<desc='Sending standby sync message' done=False priv=False>
2022-06-17 11:52:59,738  19292 [Engine       ] DEB: ZAdmin, current state:final, exit code:success. Processing work: [privileged] getting engine status. done = False
2022-06-17 11:53:04,744  19292 [main     ] DEB: Moved to final state
2022-06-17 11:53:04,745  19292 [main     ] DEB: ZTP completed successfully
2022-06-17 11:53:04,745  19292 [main     ] INF: Exiting SUCCESSFULLY
2022-06-17 11:53:04,746  19292 [main     ] DEB: Exiting. Will not retry now.
2022-06-17 11:53:04,746  19292 [main     ] DEB: Shutting down adaptor. Cleanup False. Exiting False
2022-06-17 11:53:04,748  19292 [Engine       ] DEB: ZAdmin, current state:final, exit code:success. Processing work: [privileged] prepare engine shutdown. done = False
2022-06-17 11:53:04,849  19292 [Engine       ] DEB: ZAdmin, current state:final, exit code:success. Processing work: [privileged] shutting down ZAdmin engine. done = False
2022-06-17 11:53:04,849  19292 [Engine       ] INF: ZAdmin, current state:final, exit code:shutdown
2022-06-17 11:53:04,849  19292 [Engine       ] INF: ZAdmin, exit code:shutdown: state changed to None
2022-06-17 11:53:04,849  19292 [Engine       ] DEB: ZAdmin, exit code:shutdown: breaking engine loop after shutdown
2022-06-17 11:53:04,850  19292 [Engine       ] DEB: ZAdmin, exit code:shutdown: end of event loop
2022-06-17 11:53:04,850  19292 [Adaptor      ] DEB: Adaptor : Cleanup for admin context on Terminate
2022-06-17 11:53:06,119  19292 [main     ] INF: Exiting SUCCESSFULLY
2022-06-17 11:53:06,119  19292 [main     ] INF: ZTP Exited
RP/0/RP0/CPU0:Jun 17 11:53:06.119 UTC: pyztp2[140]: %INFRA-ZTP-4-EXITED : ZTP exited

When you have a problem in the ztp process that you cannot resolve, the resource of last resort is your Cisco Systems technical support representative. To analyze a problem, your technical support representative needs certain information about the situation and the symptoms that you are experiencing. To speed up the problem isolation and resolution process, collect the necessary data before you contact your representative.

Use the show tech-support ztp command to collect all debugging information of ztp process.

Example:

RP/0/RP0/CPU0:R1#show tech-support ztp
Thu Jul 28 08:33:27.531 UTC
++ Show tech start time: 2022-Jul-28.083327.UTC ++
Thu Jul 28 08:33:28 UTC 2022 Waiting for gathering to complete
..
Thu Jul 28 08:33:34 UTC 2022 Compressing show tech output
Show tech output available at 0/RP0/CPU0 : /harddisk:/showtech/showtech-R1-ZTP-2022-Jul-28.083327.UTC.tgz
++ Show tech end time: 2022-Jul-28.083334.UTC ++
RP/0/RP0/CPU0:R1#

In the above example, the tech support information is saved as .tgz file in the specified location. This information can be shared with the Cisco Technical Support representatives for troubleshooting the ztp process.