Usage Guidelines

Use the ztp breakout command to perform a 10x10 breakout detection on all 100 Gigabit ports. On the 100G ports which are not able to bring up, the ztp breakout command will no shut all the 100G interfaces which support breakout configuration. If the interface is able to bring up, the ztp breakout script will keep the interface no change. Otherwise, the ztp breakout script will apply breakout configuration on the down interfaces.

The nosignal-stay-in-breakout-mode argument will force the port in breakout mode when all breakout interfaces from the same physical port have no signal locked, and place the ten 10Gigabitinterfaces in shutdown mode. The nosignal-stay-in-state-noshut argument will leave the port in breakout mode and place the ten 10Gigabit interfaces in no shutdown mode.

No progress logs are shown by default, although there will be XR syslogs for important events. If you wish to see more logs, add verbose after the ztp terminate command. If these logs are not enough, add debug before verbose .

Logs can be found in disk0:/ztp/ztp.log.

Usage Guidelines

If you wish to run ZTP as if from a clean boot, use the ztp clean command to remove all ZTP logs and settings. Use commit replace to reload, and then ZTP will run again as if from first boot.

No progress logs are shown by default, although there will be XR syslogs for important events. If you wish to see more logs, add verbose after the ztp clean command. If these logs are not enough, add debug before verbose .

Logs can be found in disk0:/ztp/ztp.log.

Usage Guidelines

Use ztp disable command to disable ZTP. When you execute the ztp disable command, the start value in the ztp.ini file is set to False.

The following example shows the sample of the ztp.ini file:

[Startup]
start: False
retry_forever: True

[Fetcher Priority]
Mgmt4: 0
Mgmt6: 1
DPort4: 2
DPort6: 3

Usage Guidelines

By default, ZTP is enabled. When you execute the ztp enable command the start value in the ztp.ini file is set to True.

The following example shows the sample of the ztp.ini file:

[Startup]
start: True
retry_forever: True

[Fetcher Priority]
Mgmt4: 0
Mgmt6: 1
DPort4: 2
DPort6: 3

Usage Guidelines

Use the ztp initiate command to forceably inititate the ZTP, ignoring username configuration. ztp initiate allows the execution of a script even when the system has already been configured. This command is useful for testing ZTP without forcing a reload. This command is particularly useful to test scripts or if some manual operations are required before provisioning the box. ztp initiate can specify any data interfaces and management interface on the system to be used for the whole ZTP process. If you don't specify an interface, ztp will be invoked on management interface only.

No progress logs are shown by default, although there will be XR syslogs for important events. If you wish to see more logs, add verbose after the ztp initiate command. For more details, add debug before verbose .

Logs can be found in disk0:/ztp/ztp.log.

Usage Guidelines

If you want to terminate an already running ZTP process, use the ztp terminate command. Be careful to use the ztp terminate command because unproperly usage of this command may leave your system in a partially configured state.

No progress logs are shown by default, although there will be XR syslogs for important events. If you wish to see more logs, add verbose after the ztp terminate command. If these logs are not enough, add debug before verbose .

Logs can be found in disk0:/ztp/ztp.log.

Note	Unproperly cleanup of the interface IP configuration in Linux in the XR namespace may cause the same IP present in the global Virtual Routing and Forwarding (VRF) and XR namespace at the same time.