Reference v4.1.0 Instruction Manual

Network OS Command Reference 217

53-1003115-01

dhcp auto-deployment enable

Enables DHCP auto-deployment on the switch.

Synopsis dhcp auto-deployment enable

Operands None

Defaults Disabled

Command Modes Privileged EXEC mode

Description Use this command to enable DHCP auto-deployment on the switch.

Usage Guidelines This command will cause a cold/disruptive reboot and will require that Telnet, secure Telnet, or

SSH sessions be restarted.

Scenario 1: When you enable DHCP auto-deployment and the system starts to reboot, the DAD

process is triggered after configuration replay is complete.

In the case of dual Management Moddule (MM) chassis, the DAD process waits for the dual MMs

to be in sync before starting the requested firmware download. However, if you manually issue

firmwaredownload –sb during this period (after DAD is triggered and before the MM is in sync),

DHCP auto-deployment will fail because the previous firmware download takes precedence. If you

manually issue firmwaredownload –sb before DAD is triggered, DHCP auto-deployment will fail for

the same reason.

Scenario 2: You issue the command to enable DAD (answer “Yes” when prompted), but before the

system reboot, there is an HA failover. DAD will be cancelled. You must enable DHCP

auto-deployment from the new active switch.

Scenario 3: You issue the command to enable DAD, but after the system reboot is invoked,

takeover occurs (the previous standby switch becomes the new active switch), DHCP

auto-deployment will proceed.

Scenario 4: You manually issue the firmwaredownload command, but before the firmware

download is completed, you enable DAD from the CLI and answer “Yes” when prompted to reboot

the switch. When the switch boots up, even if the DAD process detects that the firmware download

is needed, it will fail during the sanity check because the previous incomplete firmware download

takes precedence. DHCP auto-deployment will fail.

Examples None