Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
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
ii
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.
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 1
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.
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. 2. Back up your configuration. 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.
Page 2
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. Its 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 its 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.
Page 3
3.
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 its not the Master switch. 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
5.
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 4
4.
5.
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: # of free clusters: # of bad clusters: 15,312 4,023 0
Page 5
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: - free space on volume:
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 6
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 7
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. Its 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 its 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.
3.
Page 8
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 its not the Master switch. 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
5.
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.
To upgrade a switch running a 3.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. 2. Back up your configuration. 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.
Page 9
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
2.
Set an enable password and save the configuration (not required if an alternative enable authentication method is already configured).
console#configure
Page 10
3.
4.
5.
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 11
total # of clusters: # of free clusters: # of bad clusters: total free space: max contiguous free space: # of files: # of folders: total bytes in files: # of lost chains: total bytes in lost chains:
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: - free space on volume:
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 12
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 13
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
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: 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.
To upgrade a switch running a 2.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. 2. Back up your configuration. 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
Page 14
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: 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.
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.
Page 15
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
3.
4.
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 16
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 17
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
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.
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 18
b.
2.
3.
4. 5.
6. 7. 8.
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. 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 Select 5 - Display operational code vital product data from the boot menu. 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 Select 7 Update Boot Code from the boot menu. Select 9 Reset the system. Do NOT select 1 Start operational code. Verify that the firmware has been updated to the 5.0.1.3 version using the show version command.
Page 19
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.
Page 20
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.
7.
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 21
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
Page 22