Configuration Notes and Feature Limitations for DHCP Auto-Provisioning

• Although the DHCP server may provide multiple addresses, only one IP address is installed at a time.
• DHCP auto-provisioning is not supported together with DHCP snooping.
• POE firmware is bundled with the ICX image file. If the ICX software is upgraded, the POE firmware is automatically updated after the upgrade completes.
• The DHCP client does not initiate auto-provisioning after a stack switchover. You must disable and re-enable the DHCP client after a stack switchover for auto-provisioning to start.
• When the Layer 2 switch acts as a DHCP client, the show ip command does not display the image file name if the bootfile on the DHCP server is configured as manifest.txt.
• During the DHCP auto-provisioning process, the client accepts either the TFTP server name or the TFTP server IP address. If the server name is configured, the client ignores the server IP address.
• During auto-provisioning using the manifest.txt file, the boot image download is skipped if the flash images are the same.
• The DHCP server accepts more than one default router in the address pool. However, the DHCP client configures the first router-ip as the default route when the options are received.
• The DHCP client contacts the TFTP server to obtain the hostnameMAC-config.cfg file only five times if the TFTP server is busy or not reachable. If the TFTP server is reachable, the DHCP client contacts the TFTP server only once.
• In a stacking configuration, the DHCP client flash image download waits five minutes for all member units to join and update. After five minutes, the DHCP client downloads the new image from the TFTP server using the TFTP server IP address (option 150), if it is available. If the TFTP server IP address is not available, the DHCP client requests the TFTP file from the DHCP server.

The following configuration rules apply to DHCP auto-provisioning:

• To enable flash image update (ip dhcp-client auto-update enable command), you must also enable the auto-configuration (ip dhcp-client enable command).
• The image file name to be updated must have the extension .bin or .txt.
• The DHCP option 067 bootfile name is used for an image update if it has the extension .bin or .txt.
• The DHCP option 067 bootfile name is used for the configuration download if it does not have the extension .bin or .txt.
• If the DHCP option 067 bootfile name is not configured or does not have the extension .bin or .txt, then auto-provisioning does not occur.
• The option 67 (boot file name) is available for DHCP Offer and ACK packets only under Option 67 and not under the “Boot file name” header.

The following configuration rules apply to DHCP auto-provisioning enhancements:

• Only “router” can be used for specifying an image type. If any other value is entered, the DHCP client accepts and stores the values specified in the string. However, these values cannot be used and the DHCP client behavior will not change based on the option 67 configurations.
• Only “primary” or “secondary” can be used for specifying the flash image. If any other value is entered, the DHCP client accepts and stores the values specified in the string. However, these values cannot be used and the DHCP client behavior will not change based on the option 67 configurations.
• The received option 67 value for the boot image name is not saved in the DHCP client configuration.
• DHCP auto-provisioning enhancements are only supported beginning with FastIron 08.0.80. If the DHCP client image is downgraded to that of a prior release, and option 67 is received by the DHCP client with the image type and flash location specified, DHCP auto-provisioning does not work because the DHCP client expects only a specified file type. Option 67 must be reconfigured on the DHCP server for the format supported for the particular release.