By default, the auto-boot process scans all ZTP-enabled ports to find a port with an operational link. The scanned ports include:
out-of-band management port (Mgmt port)
Ethernet ports on the first two card or MDA slots (used for in-band management)
For breakout connectors, only the first breakout port in the connector can be used for ZTP.
ZTP attempts to discover the node IP through DHCP and identifies the node using DHCP client ID Option 61 (IPv4) or Option 1 (IPv6). The client ID uses the chassis serial number by default. The chassis serial number is visible on the shipping box of the chassis.
Table 1 lists the default DHCP client options for ZTP. Some client options can be manually configured in the BOF using the bof>auto-boot command.
The optional auto-boot command parameters are as follows:
[management-port]
This keyword specifies that ZTP should only be performed using the out-of-band management port (Mgmt port).
[in-band [vlan vlan-id]]
This keyword specifies that ZTP should only be performed using Ethernet ports on the first two card or MDA slots. The vlan-id parameter can be used to specify an in-band VLAN to use for the auto-boot process.
[ipv4] [ipv6]
These keywords specify that IPv4 discovery, IPv6 discovery, or both, should be performed. If both keywords are specified, the system dual-stacks.
[client-identifier {string ascii-string | hex hex-string | chassis-mac}]
These parameters identify the node to the DHCP server and find a pool for DHCP offers. This information is sent using Option 61 (IPv4) or Option 1 (IPv6). If the parameters are not configured, the chassis serial number is sent by default. This option is used for both IPv4 client ID and IPv6 DUID Type 2.
[include-user-class]
This keyword specifies that Option 77 should be included.
The auto-boot options can be modified using the bof>auto-boot command, or by interrupting the bootup process and manually modifying the bof.cfg file.
Manually modifying the bof.cfg file is not recommended. When modifying auto-boot options using CLI, all required options must be explicitly configured because the default cases are not used. When modifying the bof.cfg file manually, the format must be correct.