Auto-Provisioning Download and Update

During auto-provisioning, the device requests the configuration files from the TFTP server in the following order.
  1. bootfile name provided by the DHCP server (if configured).
  2. hostnameMAC-config.cfg (for example: ICX001p-Switch0000.005e.4d00-config.cfg).
  3. hostnameMAC.cfg (for example: ICX002p-Switch0000.005e.4d00.cfg).
  4. A new file format has been introduced based on the host name as part of DHCP option 12 support. For example fi_router.cfg.
  5. When the DHCP client switch looks for the configuration file in the TFTP server, a configuration file in the format such as <icx>-<switch | router>.cfg will be ignored. Instead the following file format is expected.
    Old format: ICX7650-router.cfg New format: ICX7650.cfg

    < ICX7650>.cfg appends the existing configuration.

  6. ruckus.cfg (applies to all devices), (for example: ruckus.cfg appends the existing configuration).

If the device successfully contacts the TFTP server and the server has the configuration file, the files are merged. If there is a conflict, the server file takes precedence. If the device is unable to contact the TFTP server, or if the files are not found on the server, the TFTP part of the configuration download process ends.

Parent topic: Configuration Notes and Feature Limitations for DHCP Auto-Provisioning