Expansion Modules For Dell Networking Switches v2.3

Dell™ PowerConnect™
8024/8024F/M6220/M6348/M8024/M8024-k
7024/7048/7024P/7048P/7024F/7048R/7048R-RA
Upgrading PowerConnect
Switches from Version 2.x.x.x or
3.x.x.x or 4.x.x.x or 5.x.x.x to
5.1.13.1 Firmware
Date: June 2018

Information in this document is subject to change without notice.
© 2003 – 2018 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.
Table of Contents
Introduction ...............................................................................................................1
Global Support ............................................................................................................1
Firmware Upgrade Procedures .........................................................................................1
Upgrade Overview .......................................................................................................2
Upgrade Switches Running Firmware v3.x.x.x or v4.x.x.x or v5.x.x.x to v5.1.13.1 Firmware ..............2
Upgrade Example for Switches Running v3.x.x.x or v4.x.x.x or v5.x.x.x Firmware ...........................3
Stacking Notes ............................................................................................................8
CPLD Update Procedure Example for PC8024/PC8024F switch ................................................. 10
CPLD Update Procedure Example for M8024-k switch ............................................................ 12
Upgrade Switches Running Firmware v2.x.x.x to v5.1.13.1 Firmware ........................................ 13
Upgrade Example for Switches Running v2.x.x.x Firmware ..................................................... 14
Switch Recovery Procedure........................................................................................... 18
Switch Recovery Example ............................................................................................. 19
Firmware Downgrade .................................................................................................. 21
Boot Code Downgrade ................................................................................................. 21
Hardware Supported ................................................................................................... 21
End of document ....................................................................................................... 21
Subject to Change Without Notice

ii
Upgrading PowerConnect Switches from Version 2.x.x.x or 3.x.x.x or
4.x.x.x or 5.x.x.x to 5.1.13.1 Firmware
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 or 5.x.x.x to firmware version 5.1.13.1 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 upgrade procedures specified in this document. The first is an upgrade procedure for systems
running 3.x.x.x or 4.x.x.x or 5.x.x.x firmware. The second is an upgrade procedure for systems running 2.x.x.x
firmware. The third is a procedure to recover switches that failed an earlier upgrade attempt.
NOTE: Switches running 3.x.x.x or 4.x.x.x or 5.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 or 5.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!
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.
Page 1
Upgrade Overview
Administrators must have access to the switch CLI via telnet, SSH or the serial port to perform the upgrade
procedure. This upgrade procedure can be followed to update modular switches (M8024k, M8024, M6220, and
M6348) via the CMC (Chassis Management Controller) interface as well.
Upgrade Switches Running Firmware v3.x.x.x or v4.x.x.x or v5.x.x.x to v5.1.13.1 Firmware

The upgrade procedure given below upgrades an individual switch or a stack of switches running firmware version
3.x.x.x or 4.x.x.x or 5.x.x.x. 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.
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.
NOTE: The following TFTP server may be used if you do not have one:
http://tftpd32.jounin.net/tftpd32_download.html
To upgrade a switch running a 3.x.x.x or 4.x.x.x or 5.x.x.x version of firmware to the 5.1.13.1 version of firmware,
use the procedure below. An annotated upgrade example is shown following this section.
1. Back up your running 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.1.13.1 firmware emulates industry standard behavior for privileged

exec mode authentication over SSH and telnet. In 5.1.13.1, 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.
Page 2
3. Download the 5.1.13.1 firmware to the switch or stack master. The following versions are available:
- PC7000_M6348v5.1.13.1.stk
- PC8024v5.1.13.1.stk
- PCM6220v5.1.13.1.stk
- PCM8024kv5.1.13.1.stk
4. Activate 5.1.13.1 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.1.13.1 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
NOTE: After upgrading the switch firmware version to 5.1.13.1, the CPLD
(Complex Programmable Logic Device) code update is required on M8024-k
and PC8024/PC8024F switches if switch is running with the older CPLD
version. CPLD update can be done only via switch serial console (not
through SSH or Telnet).
You can verify the running CPLD code version by executing the command
“console#dev cpldTest” from console. The latest CPLD version available for
M8024k and PC8024/PC8024F switch is Version 6.
Upgrade Example for Switches Running v3.x.x.x or v4.x.x.x or v5.x.x.x Firmware

This example shows an annotated upgrade example for a PC8024 switch running 4.2.1.3 firmware. Administrators
can also follow the same procedure to upgrade switches running 3.x.x.x or 5.x.x.x to 5.1.13.1 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 and TFTP server is accessible from the switch.
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.
Page 3
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
3. Download the 5.1.13.1 firmware from a TFTP server.

console#copy tftp://10.10.10.200/PC8024v5.1.13.1.stk image
Transfer Mode.................................. TFTP
Server IP Address.............................. 10.10.10.200
Source File Path............................... /
Source Filename................................ PC8024v5.1.13.1.stk
Data Type...................................... Code
Destination Filename........................... image

TFTP code transfer starting

Verifying CRC of file in Flash File System
Distributing the code to the members of the stack!
console#show version
Image Descriptions
image1 : default image
image2 :
Images currently available on Flash
--------------------------------------------------------------------
unit image1 image2 current-active next-active
--------------------------------------------------------------------
1 4.2.1.3 5.1.13.1 image1 image1
4. Activate the 5.1.13.1 firmware

console#boot system image2
Activating image 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.
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 4
Boot Menu 4.2.1.3

CPU Card ID: 0x10508548
CFI Probe: Found x16 device in x16 mode
/DskVol// - disk check in progress ...
/DskVol// - Volume is OK
volume descriptor ptr (pVolDesc): 0x813a4d0

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
Boot Menu 4.2.1.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 0xa0000 bytes.
Wrote 0xb0000 bytes.
Wrote 0xc0000 bytes.
Wrote 0xd0000 bytes.
Wrote 0xe0000 bytes.
Wrote 0xf0000 bytes.
Validating Flash.....Passed
Page 5
Boot Menu 5.1.13.1

volume descriptor ptr (pVolDesc): 0x813acf0

volume options:

- volume Id: 0xf6
Boot Menu 5.1.13.1

operational code will start.
1 - Start operational code.

Select (1, 2):
Operational Code Date: Wed Apr 1 16:01:49 2015
Uncompressing.....
Adding 0 symbols for standalone.

volume descriptor ptr (pVolDesc): 0x4ad4290

volume options:

- volume Id: 0xf6
Page 6

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
Formatting.../download: file system is marked clean, skipping check
OK.
<186> Jun 27 03:09:42 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.1.13.1 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.
System Description................ Dell Ethernet Switch
System Up Time.................... 0 days, 00h:02m:36s
System Contact.................... Babuji
System Name....................... DNSE
System Location................... Austin
Burned In MAC Address............. 5C26.0AB2.4327
System Object ID.................. 1.3.6.1.4.1.674.10895.3023
System Model ID................... PC8024
Machine Type...................... Powerconnect 8024

---- ----------- ----------- -------------- --------------
1 4.2.1.3 5.1.13.1 image2 image2
7. The switch is now ready for normal operation. Verify the configuration and make any changes needed prior
to connecting the switch to the operational network.
Page 7
Stacking Notes
Regarding steps 3, 4 and 5 above:
 The “copy” command will take longer to complete with a stack of switches. This is due to the master
switch copying the software to the member switches. The master switch will display the line “Distributing
the code to the members of the stack!” for several minutes until the copy is done.
 The “copy” command will copy the software to the non-active image on all the switches.
Examples:
 If all switches in the stack have image1 as active, then the downloaded software will go to image2 on all
switches and a single “boot system image2” command will select image2 for the next active image on all
switches in the stack.
Image Descriptions
image2 :
--------------------------------------------------------------------
--------------------------------------------------------------------
1 4.2.1.3 5.1.13.1 image1 image1
2 4.2.1.3 5.1.13.1 image1 image1
console# boot system image2
Image Descriptions
image2 :
--------------------------------------------------------------------
--------------------------------------------------------------------
1 4.2.1.3 5.1.13.1 image1 image2
2 4.2.1.3 5.1.13.1 image1 image2


 If the switches in the stack have some image1 active and some image2 active members, then the
downloaded software will go to the non-active image on each switch and multiple “boot system <unit>
imageX” commands will be required to select the next active image on each switch in the stack.
Page 8
Image Descriptions
image2 :
--------------------------------------------------------------------
--------------------------------------------------------------------
1 4.2.1.3 5.1.13.1 image1 image1
2 5.1.13.1 4.2.1.3 image2 image2
console#boot system 1 image2

console#boot system 2 image1

Image Descriptions
image2 :
--------------------------------------------------------------------
--------------------------------------------------------------------
1 4.2.1.3 5.1.13.1 image1 image2
2 5.1.13.1 4.2.1.3 image2 image1


NOTE: After upgrading the switch firmware version to 5.1.13.1, the CPLD
(Complex Programmable Logic Device) code update is required on M8024-k
and PC8024/PC8024F switches if switch is running with the older CPLD
version. CPLD update can be done only via switch serial console (not
through SSH or Telnet). The latest CPLD version available for M8024k and
PC8024/PC8024F switch is Version 6.
NOTE: Administrators upgrading PowerConnect 8024/8024F/M8024k

switches MUST use the CPLD update instructions documented in detail
below.
Page 9
CPLD Update Procedure Example for PC8024/PC8024F switch
NOTE: After upgrading the PC8024/PC8024F switch firmware version to

5.1.13.1, the CPLD update is required for PC8024/PC8024F switches if
switch is running with CPLD version 5 or older. You can verify the current
version of CPLD by running the command “console#devshell cpldTest”
from console.
Follow these instructions below to verify the CPLD version and Upgrade
CPLD code to version 6 on PC8024/PC8024F switch from Serial 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 PC8024/PC8024F switches.
1. Verify CPLD version from console.
console#dev cpldTest
Board Type : Campbell 24F
Board Version : 2
CPLD Revision : 3 (0x3)
RPS2 Present
RPS2 Status : Working
RPS2 Temperature : Normal
RPS2 Fan Status : Working
RPS1 Present
Port SFP Status Link Status Tx Power
---- ---------- ----------- --------
1 Present Up Enabled
3 Not Present Down Disabled
17 Not Present Down Enabled
Fan control IC has failed
Fan1 Status : Working
value = 36 = 0x24
Page 10
2. Upgrade CPLD from console.

console#dev cpldUpdate
Device #1 Silicon ID is ALTERA04(01)
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 180300310, exit_code 0, format_version 2
value = -1 = 0xffffffff
3. Power cycle the switch - Hard reboot required. Power disconnected for 10 seconds. Each unit of the
stack will require a hard reboot.
4. Repeat Steps 1 through 3 on each member unit in the Stack of PC8024/PC8024F 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 power cycle.
Board Type : Campbell 24F
Board Version : 2
CPLD Revision : 6 (0x6)
RPS2 Present
RPS1 Present
Port SFP Status Link Status Tx Power
---- ---------- ----------- --------
value = 36 = 0x24
Page 11
CPLD Update Procedure Example for M8024-k switch
NOTE: After upgrading the M8024-k switch firmware version to 5.1.13.1, the
CPLD update is required for M8024-k switches if switch is running with
CPLD version 5 or older. You can verify the running version of CPLD by
executing the command “console#dev cpldTest” from console.
Follow these instructions below to verify the CPLD version and Upgrade
CPLD code to version 6 on M8024-k switch 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.
CPLD REVISION: 4
HW Version : 6
SFP_TX_POWERCONTROL register = f
SFP STATUS_1 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
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.
Page 12
5. Verify the updated CPLD version after switch reset.

CPLD REVISION: 6
HW Version : 6
SFP_TX_POWERCONTROL register = f
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 Switches Running Firmware v2.x.x.x to v5.1.13.1 Firmware

The upgrade procedure given below upgrades an individual switch or a stack of switches running firmware version
2.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.
must be accessible to the TFTP server before attempting to download
To upgrade a switch running a 2.x.x.x version of firmware to the 5.1.13.1 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>
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.1.13.1 firmware emulates industry standard behavior for privileged

exec mode authentication over SSH and telnet. In 5.1.13.1, the default
authentication list for telnet and SSH is enableNetList, which requires an
enable password. If the startup configuration being upgraded does not
Page 13
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.
3. Download the 5.1.13.1 firmware to the switch or stack master. The following versions are available:
- PCM6220v5.1.13.1.stk
- PC7000_M6348v5.1.13.1.stk
- PC8024v5.1.13.1.stk
- PCM8024v5.1.13.1.stk
4. Activate 5.1.13.1 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.
Upgrade Example for Switches Running v2.x.x.x Firmware

This example shows an annotated upgrade example for a PCM6220 switch running 2.2.0.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.
must be accessible by the TFTP server before attempting to download
NOTE: The following TFTP server may be used if you do not have one:
http://tftpd32.jounin.net/tftpd32_download.html
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
console#
Page 14
2. Download the 5.1.13.1 firmware from a TFTP server.

console#copy tftp://10.10.10.200/PCM6220v5.1.13.1.stk image
Transfer Mode.................................. TFTP
Server IP Address.............................. 10.10.10.200
Source File Path............................... /
Source Filename................................ PCM6220v5.1.13.1.stk
Data Type...................................... Code
Destination Filename........................... image

TFTP code transfer starting

Verifying CRC of file in Flash File System
Unpacking the image file.
Distributing the code to the members of the stack!
Image Descriptions

image2 :

--------------------------------------------------------------------
--------------------------------------------------------------------
1 5.1.13.1 2.2.0.3 image2 image2
3. Activate the 5.1.13.1 firmware

console#boot system image1
4. Update the boot code and reboot the switch.

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 15
Boot Menu 5.1.13.1

volume descriptor ptr (pVolDesc): 0x81239b0

volume options:

- volume Id: 0x167
Boot Menu 5.1.13.1


Select (1, 2):
Operational Code Date: Wed Apr 1 16:01:49 2015
Uncompressing.....
Adding 0 symbols for standalone.

dosChkLib : CLOCK_REALTIME is being reset to THU AUG 03 20:31:48 2006
Value obtained from file system volume descriptor pointer: 0x3d4a9f0
The old setting was THU JAN 01 00:00:03 1970
Accepted system dates are greater than THU DEC 27 00:00:00 1990
volume descriptor ptr (pVolDesc): 0x3d4a9f0

volume options:

- volume Id: 0x167
Page 16

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.
Formatting /download for DOSFS
Formatting.../download: file system is marked clean, skipping check
OK.
<186> Jun 27 03:32:10 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.1.13.1 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.
System Description................ Dell Ethernet Switch
System Up Time.................... 0 days, 00h:05m:23s
System Contact....................
System Name.......................
System Location...................
Burned In MAC Address............. 5C26.0ACE.D9C7
System Object ID.................. 1.3.6.1.4.1.674.10895.3015
System Model ID................... PCM6220
Machine Type...................... PowerConnect M6220

---- ----------- ----------- -------------- --------------
1 5.1.13.1 2.2.0.3 image1 image1
6. 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.
Page 17
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).
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.1.13.1 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.1.13.1
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 – PC8024r5v1m13b1.opr” – Version 5.1.13.1
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.1.13.1 version using the show version command.
Page 18
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 (1, 2):2
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
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.
Page 19
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

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.1.13.1.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 0xa0000 bytes.
Wrote 0xb0000 bytes.
Wrote 0xc0000 bytes.
Wrote 0xd0000 bytes.
Wrote 0xe0000 bytes.
Wrote 0xf0000 bytes.
Validating Flash.....Passed
Flash update completed.
7. Select 9 – Reset the System

[Boot Menu] 9
Page 20
8. Verify that the 5.1.13.1 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.1.13.1 to an earlier release is supported on all PowerConnect series switches. But 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 enabled by default. To avoid accidentally downgrading a stack, be sure to disable
auto-downgrade (CLI command: no boot auto-copy-sw allow-downgrade).
Boot Code Downgrade

Never downgrade the boot code! The 5.1.13.1 boot code supports all earlier versions of firmware and never needs
downgrading.
Hardware Supported
 Dell PowerConnect M6220 Ethernet Switch
 Dell PowerConnect 8024 Ethernet Switch
 Dell PowerConnect 8024F Ethernet Switch
 Dell PowerConnect M8024-K 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
Page 21

Expansion Modules For Dell Networking Switches v2.3

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Expansion Modules For Dell Networking Switches v2.3

Încărcat de

Drepturi de autor:

Formate disponibile

Dell™ PowerConnect™

Date: June 2018

Subject to Change Without Notice

WARNING: Failure to follow the procedures in this document may cause a

Firmware Upgrade Procedures

NOTE: Switches running 3.x.x.x or 4.x.x.x or 5.x.x.x firmware in a

NOTE: This procedure involves multiple reboots of the switch or

Upgrade Switches Running Firmware v3.x.x.x or v4.x.x.x or v5.x.x.x to v5.1.13.1 Firmware

NOTE: It is required that either a non-default privileged exec (enable)

The 5.1.13.1 firmware emulates industry standard behavior for privileged

Upgrade Example for Switches Running v3.x.x.x or v4.x.x.x or v5.x.x.x Firmware

console#copy running-config tftp://10.10.10.200/myconfig.txt

11062 bytes transferred

File transfer operation completed successfully.

3. Download the 5.1.13.1 firmware from a TFTP server.

Management access will be blocked for the duration of the transfer

TFTP code transfer starting

12333844 bytes transferred

Images currently available on Flash

1 4.2.1.3 5.1.13.1 image1 image1

4. Activate the 5.1.13.1 firmware

5. Update the boot code and reboot the switch.

Management switch has unsaved changes.

Issuing boot code update command...

Boot Menu 4.2.1.3

volume descriptor ptr (pVolDesc): 0x813a4d0

current volume configuration:

Boot Menu 4.2.1.3

1 - Update boot code.

Boot Menu 5.1.13.1

volume descriptor ptr (pVolDesc): 0x813acf0

current volume configuration:

Boot Menu 5.1.13.1

1 - Start operational code.

Operational Code Date: Wed Apr 1 16:01:49 2015

Adding 0 symbols for standalone.

volume descriptor ptr (pVolDesc): 0x4ad4290

current volume configuration:

- # of sectors per FAT copy: 60

<186> Jun 27 03:09:42 0.0.0.0-1 General[1073741072]: bootos.c(225) 1 %% Event(0xaaaaaaaa)

(Unit 1 - Waiting to select management unit)>

Applying Interface configuration, please wait ...

unit image1 image2 current-active next-active

Regarding steps 3, 4 and 5 above:

console# boot system image2

Activating image image2 ..

Management switch has unsaved changes.

Issuing boot code update command...

console#boot system 1 image2

console#boot system 2 image1

Management switch has unsaved changes.

Issuing boot code update command...

NOTE: Administrators upgrading PowerConnect 8024/8024F/M8024k

CPLD Update Procedure Example for PC8024/PC8024F switch

NOTE: After upgrading the PC8024/PC8024F switch firmware version to

2. Upgrade CPLD from console.

CPLD Update Procedure Example for M8024-k switch

2. Upgrade CPLD from console.

3. Reset M8024-k switch from CMC console.

5. Verify the updated CPLD version after switch reset.

Upgrade Switches Running Firmware v2.x.x.x to v5.1.13.1 Firmware

NOTE: It is required that either a non-default privileged exec (enable)

The 5.1.13.1 firmware emulates industry standard behavior for privileged