Upgrading PowerConnect Switches From Version 2.x.x.x or 3.x.x.x or 4.x.x.x to 5.0.1.3 Firmware

Dell™ PowerConnect™

8024/8024F/M6220/M6348/M8024/M8024-k

7024/7048/7024P/7048P/7024F/7048R/7048R-RA

Upgrading PowerConnect Switches from 2.x.x.x or 3.x.x.x or 4.x.x.x to 5.0.1.3 Firmware

Date: November 2012

Information in this document is subject to change without notice.

© 2003 – 2012 Dell Inc. All rights reserved.

Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell, the DELL logo and PowerConnect are trademarks of Dell Inc; Intel and Pentium are registered

trademarks and Celeron is a trademark of Intel Corporation; Microsoft and Windows are registered trademarks of Microsoft

Corporation.

Other trademarks and trade names may be used in this document to refer to either the entity claiming the marks and names or their products. Dell Inc disclaims any proprietary interest in trademarks and trade names other than its own. All rights reserved. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without the prior written consent of Dell. Dell reserves the right to make changes without further notice to any products or specifications referred to herein to improve reliability, functionality or design.

Reproduction, adaptation or translation without prior written permission is prohibited, except as allowed under the copyright laws.

Subject to Change Without Notice ii

Table of Contents

Introduction ................................................................................................................ 1

Global Support ............................................................................................................. 1

Firmware Upgrade Procedures .......................................................................................... 1

Upgrade Overview ......................................................................................................... 2

Upgrade Procedure for Switches Running 4.x.x.x Firmware ....................................................... 9

Upgrade Example for Switches Running 4.x.x.x Firmware ........................................................10

Upgrade Procedure for Switches Running 3.x.x.x Firmware ....................................................... 7

Upgrade Example for Switches Running 3.x.x.x Firmware ......................................................... 8

Upgrade Procedure for Switches Running 2.x.x.x Firmware ......................................................12

Upgrade Example for Switches Running 2.x.x.x Firmware ........................................................13

Switch Recovery Procedure .............................................................................................18

Switch Recovery Example ...............................................................................................19

Firmware Downgrade ....................................................................................................21

Boot Code Downgrade ...................................................................................................22

Hardware Supported .....................................................................................................22

End of document .........................................................................................................22

Upgrading PowerConnect Switches Running 2.x.x.x or 3.x.x.x or 4.x.x.x Firmware

Page 1

Introduction This document provides specific procedures for upgrading the Dell™ PowerConnect™ 8024/8024F/M6220/M6348/M8024/ M8024-k/7024/7048/7024P/7048P/7024F/7048R/7048R-RA switches with firmware versions 2.x.x.x or 3.x.x.x or 4.x.x.x to firmware version 5.0.1.3 or later.

WARNING: Failure to follow the procedures in this document may cause a switch to become inoperable! If a switch is rendered inoperable, obtain a serial cable compatible with the switch and follow the switch recovery procedure located in this document.

It is recommended that this document be thoroughly reviewed prior to installing or upgrading of this product.

Global Support For information regarding the latest available firmware, release note revisions, or additional assistance, please visit support.dell.com.

Firmware Upgrade Procedures There are three procedures specified in this paper. The first is an upgrade procedure for systems running 4.x.x.x firmware. The second is an upgrade procedure for systems running 3.x.x.x firmware. The third is an upgrade procedure for systems running 2.x.x.x firmware. The fourth is a procedure to recover switches that failed an earlier upgrade attempt.

NOTE: Switches running 3.x.x.x or 4.x.x.x firmware in a stacking configuration automatically upgrade stack members with the firmware version installed on the master switch (including the boot code). Use this procedure to update the firmware on a single switch or stack of switches running 3.x.x.x or 4.x.x.x firmware.

NOTE: This procedure updates the boot code on the switch. Power cycling the switch during this procedure is likely to cause the switch to become inoperable and require factory re-installation of the firmware. Do NOT manually power cycle the switch during this procedure unless specifically directed to do so in the instructions!


Page 2

NOTE: This procedure involves multiple reboots of the switch or stack. In order to avoid affecting network operations, it is recommended that the switch or stack being upgraded be disconnected or isolated from the operational network.

Upgrade Overview The upgrade procedure is comprised of a two-step process. Administrators must have access to the CLI via telnet, SSH or the serial port to perform the upgrade procedure.

Upgrade Procedure for Switches Running 4.x.x.x Firmware The upgrade procedure given below upgrades an individual switch or a stack of switches running firmware version 4.x.x.x. This procedure can be used to update modular switches via the CMC as well. During this process, the switch may autonomously reboot itself such that it appears the switch rebooted twice. This is a normal operation of the upgrade procedure. Do not interrupt switch operation during the upgrade process as this may result in corruption of flash memory. Do not power off a switch undergoing the upgrade process unless specifically directed to do so by the instructions.

To upgrade a switch running a 4.x.x.x version of firmware to the 5.0.1.3 version of firmware, use the procedure below. An annotated upgrade example is shown following this section.

1. Back up your configuration.

2. If using telnet or ssh to perform the upgrade procedure and if the current configuration does not contain a non-default enable authentication method or enable password, configure an enable password and save the configuration. Example steps to configure an enable password are shown below: console# configure console(config)# enable password <XXXXXX> console(config)# exit console# copy running-config startup-config

NOTE: It is required that either a non-default privileged exec (enable) access method or an enable password be saved in the startup config in order to access privileged exec (enable) mode after the firmware upgrade.

The 5.0.1.3 firmware emulates industry standard behavior for privileged exec mode authentication over SSH and telnet. In 5.0.1.3, the default authentication list for telnet and SSH is enableNetList, which requires an enable password. If the startup configuration being upgraded does not have a non-default enable authentication method defined (e.g. TACACS), setting an enable password allows one to access privileged exec (enable) mode after the firmware upgrade.

NOTE: A TFTP server must be on the network and the switch software must be accessible to the TFTP server before attempting to download the switch software by TFTP.


Page 3

3. Download the 5.0.1.3 firmware to the switch or stack master. The following versions are available: - PCM6220v5.0.1.3.stk - PC7000_M6348v5.0.1.3.stk - PC8024v5.0.1.3.stk - PCM8024v5.0.1.3.stk

4. Activate 5.0.1.3 firmware.

5. Update the boot code from the CLI after performing steps 1 through 4 above. If the update bootcode command does not boot the switch automatically, reload the switch. The upgrade procedure will take several minutes to complete for an individual switch and longer for a stack of switches.

NOTE: After upgrading to the 5.0.1.3 firmware, one can emulate the earlier firmware default behavior for privileged exec (enable) mode access by setting the enable authentication method to enableList.

console(config)# line telnet console(config)# enable authentication enableList console(config)# exit

NOTE: After upgrading the switch firmware version to 5.0.1.3, the CPLD update is required for M8024-k switches if switch is running with CPLD version 4 or older. Follow these instructions below to verify the CPLD version and Upgrade CPLD code to version 5 from Serial console or from CMC console. Do not run this procedure via Telnet or SSH session. It’s also required to follow these instructions on each unit in the stack of M8024-k switches. The below CPLD update instructions are allowed to run on all members of the stack even if it’s not the Master switch.

1. Verify CPLD version from console. console#dev cpldTest CPLD REVISION: 4 HW Version : 6 SFP_TX_POWERCONTROL register = f SFP STATUS_1 register = cf SFP STATUS_2 register = cf SYS_SLOTB_PG : 0 SYS_SLOTA_PG : 1 SYS_MODULEB_PRESENT: 0 SYS_MODULEA_PRESENT: 1 SYS_SLOTB_POWER_CTRL: 0 SYS_SLOTA_POWER_CTRL: 1 Slot 1 status: Slot 2 status: SFP+ MODULE INSTALLED value = 22 = 0x16

2. Upgrade CPLD from console. console#dev cpldUpdate Device #1 Silicon ID is ALTERA04(00) erasing MAXII device(s)... erasing MAXII UFM block... erasing MAXII CFM block... programming CFM block... programming UFM block... verifying CFM block... verifying UFM block...


Page 4

DONE CPLD update exited with a return code of 0 error_address 38684560, exit_code 0, format_version 2 value = -1 = 0xffffffff

3. Reset M8024-k switch from CMC console. $ racadm chassisaction -m switch-1 reset Module power operation successful

4. Repeat Steps 1 through 3 on each member unit in the Stack of M8024-k switches. The above CPLD update instructions are allowed to run from serial console prompt (for example., (Unit 2 - CLI unavailable - please connect to master on Unit 1)>devshell cpldTest) of all members in the stack even if it’s not the Master switch.

5. Verify the updated CPLD version after switch reset. console#dev cpldTest CPLD REVISION: 5 HW Version : 6 SFP_TX_POWERCONTROL register = f SFP STATUS_1 register = cf SFP STATUS_2 register = cf SYS_SLOTB_PG : 0 SYS_SLOTA_PG : 1 SYS_MODULEB_PRESENT: 0 SYS_MODULEA_PRESENT: 1 SYS_SLOTB_POWER_CTRL: 0 SYS_SLOTA_POWER_CTRL: 1 Slot 1 status: Slot 2 status: SFP+ MODULE INSTALLED value = 22 = 0x16

Upgrade Example for Switches Running 4.x.x.x Firmware This example shows an annotated upgrade example for a PC8024 switch running 4.2.2.3 firmware. It is NOT necessary to use the serial port to upgrade from 4.x.x.x firmware to 5.0.1.3 firmware. This example presumes the administrator is logged in to the switch or stack via telnet or SSH. If following this example, be sure to use the firmware appropriate to the switch being upgraded.

1. Back up your configuration. The following commands copy the running-config to a TFTP server:

console#copy running-config tftp://10.10.10.200/myconfig.txt Mode........................................... TFTP Set TFTP Server IP............................. 10.10.10.200 TFTP Path...................................... ./ TFTP Filename.................................. myconfig.txt Data Type...................................... Config Script Source Filename................................ running-config Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y 11062 bytes transferred File transfer operation completed successfully. console#

2. Set an enable password and save the configuration (not required if an alternative enable authentication method is already configured). console#configure console(config)# enable password XXXXXX console(config)# exit console# copy running-config startup-config


Page 5

3. Download the 5.0.1.3 firmware from a TFTP server. console#copy tftp://10.27.9.99/PC8024v5.0.1.3.stk image Transfer Mode.................................. TFTP Server IP Address.............................. 10.27.9.99 Source File Path............................... / Source Filename................................ PC8024v5.0.1.3.stk Data Type...................................... Code Destination Filename........................... image Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y TFTP code transfer starting 13409372 bytes transferred Verifying CRC of file in Flash File System Distributing the code to the members of the stack! File transfer operation completed successfully. console#show version Image Descriptions

image1 : default image

image2 : Images currently available on Flash

-------------------------------------------------------------------- unit image1 image2 current-active next-active --------------------------------------------------------------------

1 5.0.1.3 4.2.2.3 image2 image2

4. Activate the 5.0.1.3 firmware console#boot system image1 Activating image image1 ..

5. Update the boot code and reboot the switch. console#update bootcode Update bootcode and reset (Y/N)?y Management switch has unsaved changes. Are you sure you want to continue? (Y/N) y Issuing boot code update command... Validating boot code from image...CRC Valid.

a. If using the serial port to update the firmware, the following output will be observed. If logged in

via telnet or SSH, rebooting the switch will close the connection. Rebooting may take several minutes to complete and the switch may reboot itself autonomously during the upgrade procedure.

Boot Menu 4.2.2.3 CPU Card ID: 0x10508548 CFI Probe: Found x16 device in x16 mode /DskVol// - disk check in progress ... /DskVol// - Volume is OK total # of clusters: 15,312 # of free clusters: 4,023 # of bad clusters: 0


Page 6

total free space: 8,046 Kb max contiguous free space: 5,165,056 bytes # of files: 25 # of folders: 1 total bytes in files: 22,548 Kb # of lost chains: 0 total bytes in lost chains: 0 volume descriptor ptr (pVolDesc): 0x3c2adc0 XBD device block I/O handle: 0x10001 auto disk check on mount: DOS_CHK_REPAIR |DOS_CHK_VERB_2 volume write mode: copyback (DOS_WRITE) max # of simultaneously open files: 52 file descriptors in use: 0 # of different files in use: 0 # of descriptors for deleted files: 0 # of obsolete descriptors: 0 current volume configuration: - volume label: NO LABEL ; (in boot sector: ) - volume Id: 0xf6 - total number of sectors: 61,376 - bytes per sector: 512 - # of sectors per cluster: 4 - # of reserved sectors: 1 - FAT entry size: FAT16 - # of sectors per FAT copy: 60 - # of FAT table copies: 2 - # of hidden sectors: 4 - first cluster is in sector # 136 - Update last access date for open-read-close = FALSE - directory structure: VFAT - file name format: 8-bit (extended-ASCII) - root dir start sector: 121 - # of sectors per root: 15 - max # of entries in root: 240 FAT handler information: ------------------------ - allocation group size: 2 clusters - free space on volume: 8,239,104 bytes Boot Menu 4.2.2.3 Select an option. If no selection in 10 seconds then boot code will be updated. 1 - Update boot code. 2 - Start Boot Menu. Select (1, 2): Validating image1....OK Extracting boot code from image...CRC valid Erasing Boot Flash.....Done. Wrote 0x10000 bytes. Wrote 0x20000 bytes. Wrote 0x30000 bytes. Wrote 0x40000 bytes. Wrote 0x50000 bytes. Wrote 0x60000 bytes. Wrote 0x70000 bytes. Wrote 0x80000 bytes. Wrote 0x90000 bytes. Wrote 0xa0000 bytes. Wrote 0xb0000 bytes. Wrote 0xc0000 bytes. Wrote 0xd0000 bytes. Wrote 0xe0000 bytes. Wrote 0xf0000 bytes.


Page 7

Wrote 0x100000 bytes. Validating Flash.....Passed Flash update completed. Operational Code Date: Wed Oct 10 20:17:11 2012 Uncompressing..... Adding 0 symbols for standalone. /DskVol// - disk check in progress ... /DskVol// - Volume is OK volume descriptor ptr (pVolDesc): 0x50b0ef0 XBD device block I/O handle: 0x10001 auto disk check on mount: DOS_CHK_REPAIR |DOS_CHK_VERB_2 volume write mode: copyback (DOS_WRITE) volume options: max # of simultaneously open files: 52 file descriptors in use: 0 # of different files in use: 0 # of descriptors for deleted files: 0 # of obsolete descriptors: 0 current volume configuration: - volume label: NO LABEL ; (in boot sector: ) - volume Id: 0xf6 - total number of sectors: 61,376 - bytes per sector: 512 - # of sectors per cluster: 4 - # of reserved sectors: 1 - FAT entry size: FAT16 - # of sectors per FAT copy: 60 - # of FAT table copies: 2 - # of hidden sectors: 4 - first cluster is in sector # 136 - Update last access date for open-read-close = FALSE PCI unit 0: Dev 0xb820, Rev 0x11, Chip BCM56820_B0, Driver BCM56820_A0 SOC unit 0 attached to PCI device BCM56820_B0 Adding BCM transport pointers Configuring CPUTRANS TX Configuring CPUTRANS RX Instantiating /download as rawFs, device = 0x20001 Formatting /download for DOSFS Instantiating /download as rawFs, device = 0x20001 Formatting.../download: file system is marked clean, skipping check OK. <186> OCT 31 07:50:23 0.0.0.0-1 General[1073741072]: bootos.c(225) 1 %% Event(0xaaaaaaaa) Instantiating RamCP: as rawFs, device = 0x30001 Formatting RamCP: for DOSFS Instantiating RamCP: as rawFs, device = 0x30001 RamCP:/ - disk check in progress ... RamCP:/ - Volume is OK OK. (Unit 1 - Waiting to select management unit)> Applying Global configuration, please wait ... Applying Interface configuration, please wait ... console>

6. After the switch has finished rebooting, log in and verify that the firmware has been updated to the 5.0.1.3 version using the show version command. A single switch will typically reboot in around two minutes. A stack may take significantly longer to complete the upgrade process. console#show version


Page 8

Image Descriptions image1 : default image image2 : Images currently available on Flash unit image1 image2 current-active next-active ----- ------------ ------------ ----------------- ----------------- 1 5.0.1.3 4.2.2.3 image1 image1

7. The switch or stack is now ready for normal operation. Verify the configuration and make any changes needed prior to connecting the switch to the operational network.

NOTE: After upgrading the switch firmware version to 5.0.1.3, the CPLD update is required for M8024-k switches if switch is running with CPLD version 4 or older. Follow these instructions below to verify the CPLD version and Upgrade CPLD code to version 5 from Serial console or from CMC console. Do not run this procedure via Telnet or SSH session. It’s also required to follow these instructions on each unit in the stack of M8024-k switches. The below CPLD update instructions are allowed to run on all members of the stack even if it’s not the Master switch.

1. Verify CPLD version from console. console#dev cpldTest CPLD REVISION: 4 HW Version : 6 SFP_TX_POWERCONTROL register = f SFP STATUS_1 register = cf SFP STATUS_2 register = cf SYS_SLOTB_PG : 0 SYS_SLOTA_PG : 1 SYS_MODULEB_PRESENT: 0 SYS_MODULEA_PRESENT: 1 SYS_SLOTB_POWER_CTRL: 0 SYS_SLOTA_POWER_CTRL: 1 Slot 1 status: Slot 2 status: SFP+ MODULE INSTALLED value = 22 = 0x16

2. Upgrade CPLD from console. console#dev cpldUpdate Device #1 Silicon ID is ALTERA04(00) erasing MAXII device(s)... erasing MAXII UFM block... erasing MAXII CFM block... programming CFM block... programming UFM block... verifying CFM block... verifying UFM block... DONE CPLD update exited with a return code of 0 error_address 38684560, exit_code 0, format_version 2 value = -1 = 0xffffffff

3. Reset M8024-k switch from CMC console. $ racadm chassisaction -m switch-1 reset Module power operation successful


Page 9

4. Repeat Steps 1 through 3 on each member unit in the Stack of M8024-k switches. The above CPLD update

instructions are allowed to run from serial console prompt (for example., (Unit 2 - CLI unavailable - please connect to master on Unit 1)>devshell cpldTest) of all members in the stack even if it’s not the Master switch.

5. Verify the updated CPLD version after switch reset. console#dev cpldTest CPLD REVISION: 5 HW Version : 6 SFP_TX_POWERCONTROL register = f SFP STATUS_1 register = cf SFP STATUS_2 register = cf SYS_SLOTB_PG : 0 SYS_SLOTA_PG : 1 SYS_MODULEB_PRESENT: 0 SYS_MODULEA_PRESENT: 1 SYS_SLOTB_POWER_CTRL: 0 SYS_SLOTA_POWER_CTRL: 1 Slot 1 status: Slot 2 status: SFP+ MODULE INSTALLED value = 22 = 0x16








Page 10

The 5.0.1.3 firmware emulates industry standard behavior for privileged exec mode authentication over SSH and telnet. In 5.0.1.3, the default authentication list for telnet and SSH is enableNetList, which requires an enable password. If the startup configuration being upgraded does not have a non-default enable authentication method defined (e.g. TACACS), setting an enable password allows one to access privileged exec (enable) mode after the firmware upgrade.






Upgrade Example for Switches Running 3.x.x.x Firmware This example shows an annotated upgrade example for a PC8024 switch running 3.1.4.16 firmware. It is NOT necessary to use the serial port to upgrade from 3.x.x.x firmware to 5.0.1.3 firmware. This example presumes the administrator is logged in to the switch or stack via telnet or SSH. If following this example, be sure to use the firmware appropriate to the switch being upgraded.

1. Back up your configuration. The following commands copy the running-config to a TFTP server:

console#copy running-config tftp://10.10.10.200/myconfig.txt Mode........................................... TFTP Set TFTP Server IP............................. 10.10.10.200 TFTP Path...................................... ./ TFTP Filename.................................. myconfig.txt Data Type...................................... Config Script Source Filename................................ running-config Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y 11062 bytes transferred File transfer operation completed successfully. console#

2. Set an enable password and save the configuration (not required if an alternative enable authentication method is already configured). console#configure


Page 11

console(config)# enable password XXXXXX console(config)# exit console# copy running-config startup-config

3. Download the 5.0.1.3 firmware from a TFTP server. console#copy tftp://10.27.9.99/PC8024v5.0.1.3.stk image Transfer Mode.................................. TFTP Server IP Address.............................. 10.27.9.99 Source File Path............................... / Source Filename................................ PC8024v5.0.1.3.stk Data Type...................................... Code Destination Filename........................... image Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y TFTP code transfer starting 13409372 bytes transferred Verifying CRC of file in Flash File System Distributing the code to the members of the stack! File transfer operation completed successfully. console#show version Image Descriptions

image1 : default image

image2 : Images currently available on Flash

-------------------------------------------------------------------- unit image1 image2 current-active next-active --------------------------------------------------------------------

1 5.0.1.3 3.1.4.16 image2 image2


5. Update the boot code and reboot the switch. console#update bootcode Update bootcode and reset (Y/N)?y Management switch has unsaved changes. Are you sure you want to continue? (Y/N) y Issuing boot code update command... Validating boot code from image...CRC Valid.

b. If using the serial port to update the firmware, the following output will be observed. If logged in

via telnet or SSH, rebooting the switch will close the connection. Rebooting may take several minutes to complete and the switch may reboot itself autonomously during the upgrade procedure.

Boot Menu 3.1.4.16 CPU Card ID: 0x10508548 CFI Probe: Found x16 device in x16 mode /DskVol// - disk check in progress ...


Page 12

/DskVol// - Volume is OK total # of clusters: 15,312 # of free clusters: 4,023 # of bad clusters: 0 total free space: 8,046 Kb max contiguous free space: 5,165,056 bytes # of files: 25 # of folders: 1 total bytes in files: 22,548 Kb # of lost chains: 0 total bytes in lost chains: 0 volume descriptor ptr (pVolDesc): 0x3c2adc0 XBD device block I/O handle: 0x10001 auto disk check on mount: DOS_CHK_REPAIR |DOS_CHK_VERB_2 volume write mode: copyback (DOS_WRITE) max # of simultaneously open files: 52 file descriptors in use: 0 # of different files in use: 0 # of descriptors for deleted files: 0 # of obsolete descriptors: 0 current volume configuration: - volume label: NO LABEL ; (in boot sector: ) - volume Id: 0xf6 - total number of sectors: 61,376 - bytes per sector: 512 - # of sectors per cluster: 4 - # of reserved sectors: 1 - FAT entry size: FAT16 - # of sectors per FAT copy: 60 - # of FAT table copies: 2 - # of hidden sectors: 4 - first cluster is in sector # 136 - Update last access date for open-read-close = FALSE - directory structure: VFAT - file name format: 8-bit (extended-ASCII) - root dir start sector: 121 - # of sectors per root: 15 - max # of entries in root: 240 FAT handler information: ------------------------ - allocation group size: 2 clusters - free space on volume: 8,239,104 bytes Boot Menu 3.1.4.16 Select an option. If no selection in 10 seconds then boot code will be updated. 1 - Update boot code. 2 - Start Boot Menu. Select (1, 2): Validating image1....OK Extracting boot code from image...CRC valid Erasing Boot Flash.....Done. Wrote 0x10000 bytes. Wrote 0x20000 bytes. Wrote 0x30000 bytes. Wrote 0x40000 bytes. Wrote 0x50000 bytes. Wrote 0x60000 bytes. Wrote 0x70000 bytes. Wrote 0x80000 bytes. Wrote 0x90000 bytes.


Page 13

Wrote 0xa0000 bytes. Wrote 0xb0000 bytes. Wrote 0xc0000 bytes. Wrote 0xd0000 bytes. Wrote 0xe0000 bytes. Wrote 0xf0000 bytes. Wrote 0x100000 bytes. Validating Flash.....Passed Flash update completed. Operational Code Date: Wed Oct 10 20:17:11 2012 Uncompressing..... Adding 0 symbols for standalone. /DskVol// - disk check in progress ... /DskVol// - Volume is OK volume descriptor ptr (pVolDesc): 0x50b0ef0 XBD device block I/O handle: 0x10001 auto disk check on mount: DOS_CHK_REPAIR |DOS_CHK_VERB_2 volume write mode: copyback (DOS_WRITE) volume options: max # of simultaneously open files: 52 file descriptors in use: 0 # of different files in use: 0 # of descriptors for deleted files: 0 # of obsolete descriptors: 0 current volume configuration: - volume label: NO LABEL ; (in boot sector: ) - volume Id: 0xf6 - total number of sectors: 61,376 - bytes per sector: 512 - # of sectors per cluster: 4 - # of reserved sectors: 1 - FAT entry size: FAT16 - # of sectors per FAT copy: 60 - # of FAT table copies: 2 - # of hidden sectors: 4 - first cluster is in sector # 136 - Update last access date for open-read-close = FALSE PCI unit 0: Dev 0xb820, Rev 0x11, Chip BCM56820_B0, Driver BCM56820_A0 SOC unit 0 attached to PCI device BCM56820_B0 Adding BCM transport pointers Configuring CPUTRANS TX Configuring CPUTRANS RX Instantiating /download as rawFs, device = 0x20001 Formatting /download for DOSFS Instantiating /download as rawFs, device = 0x20001 Formatting.../download: file system is marked clean, skipping check OK. <186> OCT 31 09:50:23 0.0.0.0-1 General[1073741072]: bootos.c(225) 1 %% Event(0xaaaaaaaa) Instantiating RamCP: as rawFs, device = 0x30001 Formatting RamCP: for DOSFS Instantiating RamCP: as rawFs, device = 0x30001 RamCP:/ - disk check in progress ... RamCP:/ - Volume is OK OK. (Unit 1 - Waiting to select management unit)> Applying Global configuration, please wait ... Applying Interface configuration, please wait ... console>


Page 14

6. After the switch has finished rebooting, log in and verify that the firmware has been updated to the 5.0.1.3 version using the show version command. A single switch will typically reboot in around two minutes. A stack may take significantly longer to complete the upgrade process. console#show version Image Descriptions image1 : default image image2 : Images currently available on Flash unit image1 image2 current-active next-active ----- ------------ ------------ ----------------- ----------------- 1 5.0.1.3 3.1.4.16 image1 image1







The 5.0.1.3 firmware emulates industry standard behavior for privileged exec mode authentication over SSH and telnet. In 5.0.1.3, the default authentication list for telnet and SSH is enableNetList, which requires an



Page 15

enable password. If the startup configuration being upgraded does not have a non-default enable authentication method defined (e.g. TACACS), setting an enable password allows one to access privileged exec (enable) mode after the firmware upgrade.






Upgrade Example for Switches Running 2.x.x.x Firmware This example shows an annotated upgrade example for a PCM6220 switch running 2.2.0.3 firmware. It is NOT necessary to use the serial port to upgrade from 2.x.x.x firmware to 5.0.1.3 firmware. This example presumes the administrator is logged in to the switch or stack via telnet or SSH. If following this example, be sure to use the firmware appropriate to the switch being upgraded.

1. Back up your configuration. console#copy running-config tftp://10.10.10.200/myconfig.txt Mode........................................... TFTP Set TFTP Server IP............................. 10.10.10.200 TFTP Path...................................... ./ TFTP Filename.................................. myconfig.txt Data Type...................................... Config Script Source Filename................................ running-config Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y 11062 bytes transferred File transfer operation completed successfully. console#

2. Download the 5.0.1.3 firmware from a TFTP server. console#copy tftp://10.27.9.99/PCM6220v5.0.1.3.stk image

NOTE: A TFTP server must be on the network and the switch software must be accessible by the TFTP server before attempting to download the switch software by TFTP.


Page 16

Transfer Mode.................................. TFTP Server IP Address.............................. 10.27.9.99 Source File Path............................... / Source Filename................................ PCM6220v5.0.1.3.stk Data Type...................................... Code Destination Filename........................... image Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y TFTP code transfer starting 11536336 bytes transferred Verifying CRC of file in Flash File System Unpacking the image file. Distributing the code to the members of the stack! File transfer operation completed successfully. console#show version Image Descriptions image1 : default image image2 : Images currently available on Flash -------------------------------------------------------------------- unit image1 image2 current-active next-active -------------------------------------------------------------------- 1 5.0.1.3 2.2.0.3 image2 image2


4. Update the boot code and reboot the switch. console#update bootcode Update bootcode and reset (Y/N)?y

Updating boot code ...

BootCode from image1 ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................BCM56314 DEV REV ID = 0001b314

a. If using the serial port to update the firmware, the following output will be observed. If logged in via telnet or SSH, rebooting the switch will close the connection. Rebooting may take several minutes to complete and the switch may reboot itself autonomously during the upgrade procedure.


Page 17

Boot Menu 5.0.1.3 CPU Card ID: 0x10508541 /DskVol// - disk check in progress ... /DskVol// - Volume is OK volume descriptor ptr (pVolDesc): 0x81234b0 XBD device block I/O handle: 0x10001 auto disk check on mount: DOS_CHK_REPAIR |DOS_CHK_VERB_2 volume write mode: copyback (DOS_WRITE) volume options: max # of simultaneously open files: 52 file descriptors in use: 0 # of different files in use: 0 # of descriptors for deleted files: 0 # of obsolete descriptors: 0 current volume configuration: - volume label: NO LABEL ; (in boot sector: ) - volume Id: 0x167 - total number of sectors: 61,376 - bytes per sector: 512 - # of sectors per cluster: 4 - # of reserved sectors: 1 - FAT entry size: FAT16 - # of sectors per FAT copy: 60 - # of FAT table copies: 2 - # of hidden sectors: 4 - first cluster is in sector # 136 - Update last access date for open-read-close = FALSE Boot Menu 5.0.1.3 Select an option. If no selection in 10 seconds then operational code will start. 1 - Start operational code. 2 - Start Boot Menu. Select (1, 2): Operational Code Date: Wed Oct 10 21:35:16 2012 Uncompressing..... Adding 0 symbols for standalone. /DskVol// - disk check in progress ... dosChkLib : CLOCK_REALTIME is being reset to WED JUL 13 17:52:26 2005 Value obtained from file system volume descriptor pointer: 0x3d5e7d0 The old setting was THU JAN 01 00:00:03 1970 Accepted system dates are greater than THU DEC 27 00:00:00 1990 /DskVol// - Volume is OK volume descriptor ptr (pVolDesc): 0x3d5e7d0 XBD device block I/O handle: 0x10001 auto disk check on mount: DOS_CHK_REPAIR |DOS_CHK_VERB_2 volume write mode: copyback (DOS_WRITE) volume options: max # of simultaneously open files: 52 file descriptors in use: 0 # of different files in use: 0 # of descriptors for deleted files: 0 # of obsolete descriptors: 0 current volume configuration: - volume label: NO LABEL ; (in boot sector: ) - volume Id: 0x167 - total number of sectors: 61,376 - bytes per sector: 512 - # of sectors per cluster: 4


Page 18

- # of reserved sectors: 1 - FAT entry size: FAT16 - # of sectors per FAT copy: 60 - # of FAT table copies: 2 - # of hidden sectors: 4 - first cluster is in sector # 136 - Update last access date for open-read-close = FALSE Timebase: 66.666666 MHz, MEM: 266.666664 MHz, PCI: 66.666666 MHz, CPU: 533.333328 MHz PCI unit 0: Dev 0xb314, Rev 0x01, Chip BCM56314_A0, Driver BCM56314_A0 SOC unit 0 attached to PCI device BCM56314_A0 Adding BCM transport pointers Configuring CPUTRANS TX Configuring CPUTRANS RX hpc - No stack ports. Starting in stand-alone mode. Instantiating /download as rawFs, device = 0x20001 Formatting /download for DOSFS Instantiating /download as rawFs, device = 0x20001 Formatting.../download: file system is marked clean, skipping check OK. <186> Oct 31 17:52:49 0.0.0.0-1 General[268434704]: bootos.c(225) 1 %% Event(0xaaaaaaaa) (Unit 1 - Waiting to select management unit)> Applying Global configuration, please wait ... Applying Interface configuration, please wait ... console>

5. After the switch has finished rebooting, log in and verify that the firmware has been updated to the 5.0.1.3 version using the show version command. A single switch will typically reboot in around two minutes. A stack may take significantly longer to complete the upgrade process. console#show version Image Descriptions image1 : default image image2 : Images currently available on Flash unit image1 image2 current-active next-active ----- ------------ ------------ ----------------- ----------------- 1 5.0.1.3 2.2.0.3 image1 image1


Switch Recovery Procedure

NOTE: The Switch Recovery procedure requires one to connect to each switch individually via the serial port. It will not upgrade stack members other than the switch directly connected via the serial port. For modular switches, connect via the serial port on the front panel, not via the CMC. If the switches are connected via stacking cables, disconnect the stacking cables to perform the recovery procedure.

1. Connect a serial cable to the serial port (8-No Parity-1-9600-No Flow Control).


Page 19

a. For Top-Of-Rack Switches, use the supplied RJ45 Yost to DB9 serial cable. Connect the RJ45 end to the switch and the DB9 connector to your PC. Set the terminal emulation software to the correct settings (default setting 9600 baud, 8 data bits, no parity bit, 1 stop bit, and no flow control).

b. For M-Series switches, use the supplied USB Type-A to DB9 serial cable. Plug the USB Type A connector into the switch and connect the DB9 connector to your PC. Set the terminal emulation software to correct settings (default setting 9600 baud, 8 data bits, no parity bit, 1 stop bit, and no flow control). Power cycle the switch by powering it off for at least 10 seconds and then powering it on.

2. When the boot menu appears, select 2 – Start Boot Menu within 10 seconds of the prompt appearing. If the boot menu does not appear after power cycling the switch, check the serial port settings and the serial cable connections. Make sure that RTS/CTS (HW flow control) and XON/XOFF (SW flow control) are disabled on the terminal. It is preferred to use the serial cable supplied with the switch. If you do not have the original serial cable, it may be necessary to use a NULL modem device to access the switch via the serial cable. Check the serial cable setup with an operational switch to verify that it works properly.

3. If 5.0.1.3 firmware has not already been downloaded to the switch, download the firmware to the switch (Select option 4 - Load new operational code using XMODEM) from the boot menu using Xmodem. Download the firmware using a 1K block size. HyperTerminal supports Xmodem-1K and is distributed with Microsoft Windows®. Information on how to operate HyperTerminal can be obtained from Microsoft at http://technet.microsoft.com/en-us/library/cc784492%28WS.10%29.aspx

4. Select 5 - Display operational code vital product data from the boot menu. 5. Examine the name of the firmware image file listed on the last line of the output and tagged with the

keyword “File.” The firmware version is embedded in the name beginning with the lower case letter ‘r’ following the switch model number. If the output indicates a 2.x.x.x. or 3.x.x.x version of firmware is active, select 11 – Activate Backup Image. If the File line at the end of the output indicates a 5.0.1.3 version of firmware, skip to step 7 without changing the active image.

a. Example image versions as displayed on the boot menu: i. “File - PC8024r3v1m4b5.opr” - Version 3.1.4.5

ii. “File – PC6348r2v1m0b7.opr” – Version 2.1.0.7 iii. “File – PC8024r5v0m1b3.opr” – Version 5.0.1.3 iv. “File – PC8024r4v2m2b3.opr” – Version 4.2.2.3

6. Select 7 – Update Boot Code from the boot menu. 7. Select 9 – Reset the system. Do NOT select 1 – Start operational code. 8. Verify that the firmware has been updated to the 5.0.1.3 version using the show version command.

Switch Recovery Example 1. Connect a serial cable to the serial port (8-No Parity-1-9600-No Flow Control) 2. Power cycle the switch 3. When the boot menu appears, select 2 – Start Boot Menu

Boot Menu 3.1.4.5 Select an option. If no selection in 10 seconds then operational code will start. 1 - Start operational code. 2 - Start Boot Menu. Select (1, 2):2 Boot Menu 3.1.4.5 Options available


Page 20

1 - Start operational code 2 - Change baud rate 3 - Retrieve event log using XMODEM 4 - Load new operational code using XMODEM 5 - Display operational code vital product data 6 - Abort boot code update 7 - Update boot code 8 - Delete backup image 9 - Reset the system 10 - Restore configuration to factory defaults (delete config files) 11 - Activate Backup Image 12 - Password Recovery Procedure 13 - Reformat and restore file system

4. If not already loaded, download the firmware to the switch using Xmodem 1K block size (Select option 4 -

Load new operational code using XMODEM). HyperTerminal supports Xmodem-1K and is distributed with Microsoft Windows®. Information on how to operate HyperTerminal can be obtained here: http://technet.microsoft.com/en-us/library/cc784492%28WS.10%29.aspx Boot Menu 3.1.4.5 Options available 1 - Start operational code 2 - Change baud rate 3 - Retrieve event log using XMODEM 4 - Load new operational code using XMODEM 5 - Display operational code vital product data 6 - Abort boot code update 7 - Update boot code 8 - Delete backup image 9 - Reset the system 10 - Restore configuration to factory defaults (delete config files) 11 - Activate Backup Image 12 - Password Recovery Procedure 13 - Reformat and restore file system [Boot Menu] 4 Ready to receive the file with XMODEM/CRC.... Ready to RECEIVE File xcode.bin in binary mode Send several Control-X characters to cancel before transfer starts. CKCKCK

5. Select 5 - Display operational code vital product data

[Boot Menu] 5 The following image is in the Flash File System: File Name......................................image1 CRC............................................0x7289 (29321) Target Device..................................0x00508548 Size...........................................0xc176cc (12678860) Number of Components...........................3 Operational Code Size..........................0xa739ac (10959276) Operational Code Offset........................0x74 (116) Operational Code FLASH flag....................1 Operational Code CRC...........................0xF71A Operational Compression flag...................2 (lzma) Boot Code Version..............................1


Page 21

Boot Code Size.................................0x100000 (1048576) Boot Code Offset...............................0xa73a20 (10959392) Boot Code FLASH flag...........................0 Boot Code CRC..................................0x4128 VPD - rel A ver 1 maint_lvl 0 build_num 15 Timestamp - Thu May 19 15:25:41 2011

File - PC7000_M6348v5.0.1.3.opr

6. Select 7 – Update Boot Code from the menu [Boot Menu] 7 Do you wish to update Boot Code(y/n)y

Validating image1....OK Extracting boot code from image...CRC valid Erasing Boot Flash.....Done. Wrote 0x10000 bytes. Wrote 0x20000 bytes. Wrote 0x30000 bytes. Wrote 0x40000 bytes. Wrote 0x50000 bytes. Wrote 0x60000 bytes. Wrote 0x70000 bytes. Wrote 0x80000 bytes. Wrote 0x90000 bytes. Wrote 0xa0000 bytes. Wrote 0xb0000 bytes. Wrote 0xc0000 bytes. Wrote 0xd0000 bytes. Wrote 0xe0000 bytes. Wrote 0xf0000 bytes. Wrote 0x100000 bytes. Validating Flash.....Passed Flash update completed.

7. Select 9 – Reset the System

[Boot Menu] 9

8. Verify that the 5.0.1.3 version of firmware is loaded on the switch. The switch or stack is now ready for

normal operation. Verify the configuration and make any changes needed prior to connecting the switch to the operational network.

Firmware Downgrade Downgrading from 5.0.1.3 to an earlier release is supported on PowerConnect series switches; however, migration of configuration information from a later release to an earlier release is not supported. The existing configuration may or may not work with downgraded firmware, therefore, it is best to be physically present at the switch site and to be prepared to access the switch over the serial port if necessary when downgrading firmware. Auto-downgrade of a stack is not enabled by default. If downgrading a stack, be sure to enable auto-downgrade before loading new firmware onto the stack master.


Page 22

Boot Code Downgrade Never downgrade the boot code! The 5.0.1.3 boot code supports all earlier versions of firmware and never needs downgrading.

Hardware Supported

• Dell PowerConnect M6220 Ethernet Switch • Dell PowerConnect M6348 Ethernet Switch • Dell PowerConnect 8024 Ethernet Switch • Dell PowerConnect 8024F Ethernet Switch • Dell PowerConnect M8024 Ethernet Switch • Dell PowerConnect M8024-K Ethernet Switch • Dell PowerConnect 7024 Ethernet Switch • Dell PowerConnect 7048 Ethernet Switch • Dell PowerConnect 7024P Ethernet Switch • Dell PowerConnect 7048P Ethernet Switch • Dell PowerConnect 7024F Ethernet Switch • Dell PowerConnect 7048R Ethernet Switch • Dell PowerConnect 7048R-RA Ethernet Switch

End of document

Documents

Upgrading PowerConnect Switches From Version 2.x.x.x or 3.x.x.x or 4.x.x.x to 5.0.1.3 Firmware