Auto-provisioning failure

Auto-provisioning fails for the following reasons:

• There is no Option 67.

• The Option 67 format is not acceptable to auto-provisioning.

• The format is a URL or DNS is not supported.There is a failure in the download provisioning file or the server is not reachable.

• There is failure in the download of the image or config file using the provisioning file information, for example, the server is not available, the wrong directory is listed, or the wrong credentials are given.

• The image or config fails to copy to the compact flash.

• The image or config fails to sync to the inactive CPM.

• The BOF does not point to the compact flash, for example, it is pointing to the network.

If the auto-provisioning procedure on this interface fails, then auto-provisioning does the following:

1. Displays information about the blocked CLI and in the log, describing the failure in detail.

2. Updates the DHCP task so the DHCP task can take the appropriate actions to release the IP address on the interface. This is done by sending a DHCP release for the DHCP ack received from the server.

3. Goes to the next interface with port up and no IP address.

   Note: If no other interface with port up is found, the auto-provisioning task stops and a failure error is displayed on the CLI and in the log.