Using DHCP Automatic Deployment
DHCP Automatic Deployment (DAD) is a method used to bring up the switch with new firmware or a preset configuration automatically.
In Network OS 4.1.0 and later, you can automatically bring up a switch with new firmware, with a preset or default configuration, omitting the need for logging in to the switch console to configure the switch. You must be using DHCP to use DAD. The DHCP process helps retrieve certain parameters (for example, the firmware path, VCS ID, VCS mode, RBridge ID, and preset configuration file) needed by the DAD process to perform the firmware and configuration downloads. If the switch is in fabric cluster mode, you can apply either the default configuration or a preset configuration. For node replacement in the logical chassis cluster mode, the switch is set to the default configuration.
You must enable DAD from the CLI, after which the switch is rebooted automatically. After the DAD process is triggered and completed, DAD is automatically disabled. If you attempt to download new firmware that is already installed on the switch, the DAD process skips the firmware download step and continues configuring the switch.
Beginning with Network OS 6.0.1, you can bring up a cluster of switches using a Python script (dad.py) for DAD. Zero Touch Provisioning (ZTP) deployment is also supported beginning with this release. When the switch is in a factory default configuration and the DHCP server for auto deployment is reachable, auto deployment is enabled automatically when the switch powers up. You can also enable DAD from the CLI, after which the switch is rebooted automatically.
Supported DAD use cases
DAD supports the following typical use cases:
- Invoking a firmware upgrade (and optional configuration download) on many switches at the same time in fabric cluster mode.
- Replacing a switch in a cluster by upgrading the firmware and setting up the switch to a preset configuration. In this instance, DAD must be completed on the new switch hardware (to update the firmware) before the new switch can be incorporated into the cluster.
- Logical chassis mode support for default or preset configuration. Logical chassis mode node replacement is integrated into the logical chassis mode support.
- Configuring the whole cluster using a Python script for fabric cluster mode and logical chassis mode.
- Zero Touch Provisioning (ZTP) support on a two-node cluster.