This article provides the necessary steps to update firmware on the N1500, N2000, N3000, N4000 series switches through the Dell OpenManage Switch Administrator web interface. This procedure is applicable to stand-alone and stacked switches.
Updating the firmware using the web interface requires access to the OpenManage Switch Administrator web interface and the firmware to be uploaded. Updating the boot code requires a command-line interface access using serial, telnet, or SSH.
File type: Firmware
Transfer mode: HTTP
Image to Download: Backup
Use the Active Images page to set the firmware image to use when the switch boots. If you change the boot image, it does not become the active image until you reset the switch.
The firmware version should be verified following the power cycle. Under the Active Images page, click System > File Management > Active Images in the navigation panel check for the active firmware version.
Boot code, CPLD, and XLOADER are done only using CLI (SSH, Telnet, or Console). See the upgrade guide before proceeding with Boot code, CPLD, and XLOADER updating. The upgrade guide is in the .zip file. For more information about CPLD, Bootcode, and Xloader updates, refer to the Upgrade Guide and release notes for your relevant hardware and operating system version on the Dell Support Site.
update bootcode [unit ]
Default Configuration
By default, all units in the stack are updated.
Command Mode
Privileged Exec mode
User Guidelines
This command applies to the N1100, N1500, N2000, N2100-ON, N2200-ON, N3000, N3100-ON, and N3200-ON Series switches only.
It is not required to update the boot code unless directed to do so in the release notes. Dell Networking switches use a universal boot loader and do not contain version-specific dependencies in the boot loader. If a unit is not specified, all units in the stack are updated. This command does not reboot the stack members after the update completes. Do not reload or power off stack members during the update process as it may cause a switch to fail on a subsequent boot.
It is recommended that the stack be rebooted after a bootcode update to ensure that all stack members are properly updated.
Example
The following example updates the bootcode on stack unit 2.
console#update bootcode 2