Upgrading Dell Networking N4000 Series Switches From Version 6.x.x.x To 6.3.0.18

Dell Networking N4064/N4064F/N4032/N4032F
Upgrading Dell Networking

N4000 Series Switches to
6.3.0.18 Firmware
Date: August 2016
Information in this document is subject to change without notice.

Copyright 2016 Dell Inc. All rights reserved.
This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are
trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be
trademarks of their respective companies.
Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Information in this document is subject to change without notice.

Copyright 2016 Dell Inc. All rights reserved.
This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are
trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be
trademarks of their respective companies.
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 ............................................................................................................2
Upgrade Overview .......................................................................................................3
Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches from firmware version
6.2.x.x to 6.3.0.18 .......................................................................................................3
Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches from firmware version
6.2.x.x to 6.3.0.18 .......................................................................................................4
Stacking Notes ............................................................................................................9
Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches from firmware version
6.0.x.x or 6.1.x.x to 6.3.0.18 ........................................................................................ 10
Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches from firmware version
6.0.x.x or 6.1.x.x to 6.3.0.18 ........................................................................................ 11
Stacking Notes .......................................................................................................... 17
Switch Recovery Procedure........................................................................................... 19
Switch Recovery Example ............................................................................................. 19
Firmware Downgrade .................................................................................................. 24
Boot Code Upgrade and Downgrade ................................................................................. 24
Hardware Supported ................................................................................................... 24
End of document ....................................................................................................... 24
Subject to Change Without Notice
ii
Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Switches
Introduction
This document provides specific procedures for upgrading the Dell Networking N4064/N4064F/N4032/N4032F
switches to firmware version 6.3.0.18 or later.
IMPORTANT: Dell Networking N4000 Series switches support 6.0.0.8 or later

firmware (6.3.0.18). Both Dell Networking N4000 Series and Dell Networking 8100
series switches can share the same firmware image version (N4000v6.3.0.18.stk)
IMPORTANT: Administrators upgrading N4000 series switches from 6.x.x.x to
6.3.0.18 of firmware MUST follow the instructions documented in this procedure.
Failure to follow the procedures described in that document when upgrading from
6.x.x.x to 6.3.0.18 firmware may result in an inoperable switch!
IMPORTANT: Administrators upgrading N4000 series switches from 6.0.x.x/6.1.x.x
to 6.3.0.18 of firmware MUST follow the step upgrade (from 6.0/6.1 to 6.2 first and
then upgrade to 6.3) instructions documented in this procedure. Failure to follow
the procedures described in that document when upgrading from 6.0.x.x/6.1.x.x to
6.3.0.18 firmware may result in an inoperable switch!
IMPORTANT: Dell Networking N4000 Series switches require firmware version
6.0.0.8 or later (6.3.0.18) and cannot be downgraded to earlier 5.x releases. Dell
Networking N4000 series switches can be stacked with Dell Networking 8100 series
switches. If N4000 unit is to be deployed as a member within a stack of Dell
Networking 8100 Series switches of A1 and/or B1 CPU HW, the entire stack will be
required to run 6.0.0.8 or later firmware (6.3.0.18). The show version CLI
command will help to identify the CPU version of the switch. The improved CPU
version XLP308H-B2 version in N4000 series is not compatible with firmware
version 5.x.x.x.
Part Numbers for Dell Networking N4000 Series
P/N
4G4FP
VYN03
5KGDH
R5V1W
KK3D4
JPVRH
FWYM4
8V91F
Dell Networking N4032

Dell Networking N4032 TAA
Dell Networking N4032F
Dell Networking N4032F TAA
Page 1

Switches
IMPORTANT: Below Dell Networking N4000 Series switches with HW revision 4
require firmware version 6.2.6.6 or later and cannot be downgraded to earlier
5.x.x.x/6.0.x.x/6.1.x.x/6.2.x.x releases. Dell Networking N4000 series switches with
HW revision of 4 can be stacked with N4000/PC8100 series switches with HW
revision 3 or older. If N4000 unit with HW Revision 4 is to be deployed as a member
within a stack of N4000/PC8100 Series switches with HW revision 3 or older, the
entire stack will be required to run 6.2.6.6 or later. The show version CLI
command will help to identify the Switch Hardware version of the switch.
Part Numbers for Dell Networking N4000
Series
P/N
M0P6C
2DM31
JH9TW
9FPR2
4DP8H
M40JD
G4H0V
J7YMY
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.
Page 2

Switches
Upgrade Overview
Administrators must have access to the CLI via telnet, SSH or the serial port to perform the upgrade procedure.
Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches from

firmware version 6.2.x.x to 6.3.0.18
The upgrade procedure given below upgrades an individual switch or a stack of switches running firmware version
6.2.x.x. This is a normal operation of the upgrade procedure. Please 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 6.2.x.x version of firmware to the 6.3.0.18 version of firmware or later, uses 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 <password>
console(config)#exit
console#copy running-config startup-config
3.
Download the 6.3.0.18 firmware image (N4000v6.3.0.18.stk) to the switch or stack master.
NOTE: Activate the image to use as the boot (active) image after the switch
resets. Images on the N4064/N4064F/N4032/N4032F are named active and backup.
4.
Activate 6.3.0.18 firmware.
5.
Reload the switch.
Page 3

Switches
Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches from
firmware version 6.2.x.x to 6.3.0.18
This example shows an annotated upgrade example for a N4064F switch running 6.2.x.x firmware. This example
presumes the administrator is logged in to the switch or stack via Serial console. You can also follow this upgrade
procedure via telnet or SSH after setting enable password if it is not set so.
NOTE: How to access serial console of the switch? Use a supplied RJ45 Yost to DB9 serial cable to
access the serial console. Connect the RJ45 end of the cable to the RJ45 serial console port and the DB9
connector to your PC. Download and Install the terminal emulation software on your PC (for example.,
PuTTY) to access the serial console with the correct settings (default setting 9600 baud, 8 data bits, no
parity bit, 1 stop bit, and no flow control).
RJ-45 serial console port
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 <password>
console(config)# exit
console# copy running-config startup-config
3.
Download the 6.3.0.18 firmware image from a TFTP server.

console#copy tftp://10.10.10.200/N4000v6.3.0.18.stk backup
Transfer Mode.................................. TFTP
Server IP Address.............................. 10.10.10.200
Source File Path............................... ./
Source Filename................................ N4000v6.3.0.18.stk
Data Type...................................... Code
Destination Filename........................... backup
TFTP Code transfer starting...
31522816 bytes transferred...
File contents are valid. Copying file to flash...
Attempting to send the STK file to other units in the stack...
Page 4

Switches
console#show switch
Management Standby
SW Status
Status
--- ---------- --------1
Mgmt Sw
Preconfig
Plugged-in
Switch
Code
Model ID
Model ID
Status
Version
------------- ------------- ------------- ----------N4064F
N4064F
Ok
6.2.7.6
console#show version
Machine Description...............
System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
Burned In MAC Address.............
System Object ID..................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
Dell Networking Switch

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
unit active
backup
current-active
next-active
----- ------------ ------------ ----------------- ----------------1
6.2.7.6
6.3.0.18
6.2.7.6
6.2.7.6
NOTE: Set the image to use as the boot (active) image after the switch
resets. Images on the N4064/N4064F/N4032/N4032F are named active and
backup.
4.
Activate the 6.3.0.18 firmware

console#boot system backup
Activating image backup ..
5.
Reload the switch.

console#reload
Management switch has unsaved changes.
Are you sure you want to continue? (y/n) y
Configuration Not Saved!
Are you sure you want to reload the stack? (y/n) y
NOTE: 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 more than once during the upgrade procedure.
<184> Jul 27 00:04:42 172.25.137.218-1 UNITMGR[emWeb]: unitmgr.c(6451) 1327 %% Reset
initiated on unit 1, reason: User Request
<186> Jul 27 00:04:42 172.25.137.218-1 General[emWeb]: unitmgr.c(6476) 1328 %% Event(0x0)
Reference platform resetting ...
syncing filesystems....This may take a few moments
Rebooting system!
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
NetLogic XLP Stage 1 Loader (X-Loader) [Big-Endian] (Nov 30 2011 - 18:10:13)

MBist Pass
Page 5

Switches
Nodes online: 1
Initialized I2C0 Controller.
DDR SPD: Node 0 Channel 0 Mem size = 2048 MB
DDR SPD: Node 0 DRAM frequency 666 MHz
DDR SPD: Node 0 CPU frequency 1200 MHz
RTT Norm:44
NBU0 DRAM BAR0 base: 00000000 limit: 0013f000 xlate: 00000001 node: 00000000 (
320 MB, size:
320 MB)
NBU0 DRAM BAR1 base: 001d0000 limit: 0088f000 xlate: 00090001 node: 00000000 (
2192 MB, size: 1728 MB)
Hit any key to stop autoboot: 0
## Starting application at 0x8C100000 ...
U-Boot 2010.03-rc1 (Sep 04 2013 - 18:13:27)
DRAM:
2 GB
Initialized CPLD on CS3
Initializing I2C0: speed = 48 KHz -- done.
Now running in RAM - U-Boot [N64 ABI, Big-Endian] at: ffffffff8c100000
Flash: 256 MB
PCIE (B0:D01:F0) : Link up.
PCIE (B0:D01:F1) : No Link.
In:
serial
Out:
serial
Err:
serial
OOB MAC addr = d0:67:e5:9b:18:50
XLP3XX FMN configuration
POE ext msg storage:
POE Free Buffer Pool config ...
Net:
Successfully zapped free in fifo!
Configuring ucore...
Loading ucores (mask = 0x00ff)
Configuring NAE...
NAE Frequency set to 249MHz (2X frequency 499MHz)
num-ports = 1, start-port-id = 0
Scanning MDIO external BUS0---Found port with 0th bus and phy_addr =0x1 phy-idfer=0x3625d12
Total PHYs found = 1
xlp_nae_config_lane_gmac with cplx_mask=0x1 and config=0x1111
Net:
Completed PCS Configuration
fdt missing num-lanes, default 4
nlm_hal_ilk_pcs_init ilk_cplx_mask 0x0
parse_fdt_nae_config Completed NETIOR soft reset
Warning: Len is 0 while copying /soc/nae-cfg/port@0/intf-regs
Configuring per-port interface registers for port@0
Configuring per-port NAE registers for port@0
nlm_hal_open_if: 0CLEARING speed bit =0x2
Initializing OOB Ethernet PHY:
Starting auto-negotiation on port 0, external mdio bus 0, phy address 1
Configured with Speed 1000Mb FDX
Link is up
Storm:Initialized port@0
Configuring CPU-NAE...
Configuring PoE...
Page 6
0 MB ->
464 MB ->

Switches
Configuring POE in bypass mode
NAE configuration done!
Digest of FDT based NAE config:
nae-0: PHY is Broadcom BCM54616S (3625d12)
nae-0
boot in 5 s
Booting image at /dev/mtd6....
## Booting kernel from Legacy Image at 9000000094000074 ...
Image Name:
System for pct
Created:
2016-02-20
1:29:06 UTC
Image Type:
MIPS Linux Multi-File Image (gzip compressed)
Data Size:
31561316 Bytes = 30.1 MB
Load Address: ffffffff80100000
Entry Point: ffffffff8057a440
Contents:
Image 0: 3064420 Bytes = 2.9 MB
Image 1: 2641929 Bytes = 2.5 MB
Image 2: 21687 Bytes = 21.2 kB
Image 4: 25832776 Bytes = 24.6 MB
Verifying Checksum ... OK
## Loading init Ramdisk from multi component Legacy Image at 9000000094000074 ...
Copying the root file system to 0xffffffff81000000... OK
## Flattened Device Tree from multi component Image at 9000000094000074
Booting using the fdt at 0x9457133c
Uncompressing Multi-File Image ... OK
Starting kernel ...
[
0.000000] Initializing cgroup subsys cpuset
[
0.000000] Initializing cgroup subsys cpu
[
0.000000] Linux version 3.7.10-9939e68c (lvl7build@lc-rtp-009) (gcc version 4.6.3
(GCC) ) #1 SMP Thu Jan 14 14:29:22 EST 2016
[
0.000000] bootconsole [early0] enabled
[
0.000000] CPU revision is: 000c1101 (Netlogic XLP)
[
0.000000] FPU revision is: 00770000
[
0.000000] Checking for the multiply/shift bug... no.
[
0.000000] Checking for the daddiu bug... no.
[
0.000000] Node 0 - SYS/FUSE coremask 3
[
0.000000] Determined physical RAM map:
[
0.000000] memory: 000000000afffe00 @ 0000000000000000 (usable)
[
0.000000] memory: 000000005ffffe00 @ 0000000020000000 (usable)
[
0.424000] physmap-flash.0: failed to claim resource 0
starting pid 570, tty '': '/etc/init.d/rcS'
starting pid 708, tty '/dev/ttyS0': '/etc/rc.d/rc.fastpath'
Mounting /dev/mtdblock5 at /mnt/fastpath...done.
Mounting tmpfs at /mnt/application...done.
Checking for USB Device... done.
No USB Device found!
Dell Networking Boot Options

============================
Select a menu option within 5 seconds or the Operational Code will start automatically...
Page 7

Switches
1 - Start Operational Code

2 - Display Boot Menu
Select (1, 2)#
active = /dev/mtd6
Extracting Operational Code from .stk file...done.
Loading Operational Code...done.
Decompressing Operational Code...done.
Uncompressing apps.lzma
Uncompressing python.lzma
Installing Python
<185> Jul 27 11:06:02 0.0.0.0-0 General[fp_main_task]: unitmgr.c(6477) 1 %% Reboot 1 (0x1)
DMA pool size: 16777216
PCI unit 0: Dev 0xb846, Rev 0x02, Chip BCM56846_A1, Driver BCM56840_B0
SOC unit 0 attached to PCI device BCM56846_A1
<186> Jul 27 11:06:12 0.0.0.0-1 General[fp_main_task]: bootos.c(188) 11 %%
Event(0xaaaaaaaa)
started!
<185> Jul 27 11:06:12 0.0.0.0-1 SIM[Cnfgr_Thread ]: sim_util.c(3868) 13 %% Switch was
reset due to operator intervention.
(Unit 1 - Waiting to select management unit)>
<188> Jul 27 11:07:05 0.0.0.0-1 UNITMGR[umCfgUpdateTask]: unitmgr.c(7605) 981 %% Error
retrieving user applications information from unit 2. Failed to download user
applications.
(Unit 1 - CLI unavailable - please connect to master on Unit 2)>
<185> Jul 27 11:20:35 0.0.0.0-1 UNITMGR[unitMgrTask]: unitmgr.c(3029) 985 %% Standby
taking over as Manager of the Stack, reason: Heartbeat Timeout
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
6.3.0.18 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 Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
unit active
backup
current-active
next-active
----- ------------ ------------ ----------------- ----------------1
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
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.
Page 8

Switches
Stacking Notes
Regarding steps 2, 3 and 4 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 all the switches as backup image
System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
Operating System..................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
unit
---1
2
3
active
----------6.2.7.6
6.2.7.6
6.2.7.6

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
Linux 2.6.32.9
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
backup
current-active next-active
----------- -------------- -------------6.3.0.18
6.2.7.6
6.2.7.6
6.3.0.18
6.2.7.6
6.2.7.6
6.3.0.18
6.2.7.6
6.2.7.6
console# boot system backup

System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
unit
---1
2
3
active
----------6.2.7.6
6.2.7.6
6.2.7.6

N4064F
CN0VTWN8282982920006A00
0xbc00
Linux 2.6.32.9
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
backup
----------- -------------- -------------6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
Reload the stack of switches.

console#reload
Page 9

Switches
After the stack of switches has finished rebooting, log in and verify that the firmware has been updated to the
6.3.0.18 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 Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
unit
---1
2
3

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
active
backup
----------- ----------- -------------- -------------6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches from

firmware version 6.0.x.x or 6.1.x.x to 6.3.0.18
The upgrade procedure given below upgrades an individual switch or a stack of switches running firmware version
6.0.x.x. or 6.1.x.x. This is a normal operation of the upgrade procedure.
This procedure requires step upgrade from 5.0/6.0/6.1 to 6.2 first and then upgrade to 6.3. This is a normal
operation of the upgrade procedure.
Please 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/stack running a 6.0.x.x or 6.1.x.x version of firmware to the 6.3.0.18 version of firmware or
later, need to upgrade the switch/stack to 6.2.x.x first and then upgrade to 6.3.0.18 uses the procedure below. An
annotated upgrade example is shown following this section.
Page 10

Switches
1.
Back up your configuration before upgrading the switch/stack to 6.3.0.18.
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 <password>
console(config)#exit
console#copy running-config startup-config
3.
It requires step upgrade from 5.0/6.0/6.1 to 6.2 first and then upgrade to 6.3. So download the 6.2.7.6
firmware to the switch or stack master first. Download the 6.2.7.6 firmware image (N4000v6.2.7.6.stk) to
the switch or stack master.
NOTE: Activate the image to use as the boot (active) image after the switch
resets. Images on the N4064/N4064F/N4032/N4032F are named active and backup.
4.
5.
Reload the switch.
6.
Download the 6.3.0.18 firmware image (N4000v6.3.0.18.stk) to the switch or stack master.
7.
8.
Reload the switch.
Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches from

firmware version 6.0.x.x or 6.1.x.x to 6.3.0.18
This example shows an annotated upgrade example for a N4064F switch running 6.0.x.x or 6.1.x.x firmware. The
below example shows the step upgrade from 6.0.x.x/6.1.x.x to 6.2 and then upgrade to 6.3.0.18 image. This example
presumes the administrator is logged in to the switch or stack via Serial console. You can also follow this upgrade
procedure via telnet or SSH after setting enable password if it is not set so.
NOTE: How to access serial console of the switch? Use a supplied RJ45 Yost to DB9 serial cable to
access the serial console. Connect the RJ45 end of the cable to the RJ45 serial console port and the DB9
connector to your PC. Download and Install the terminal emulation software on your PC (for example.,
PuTTY) to access the serial console with the correct settings (default setting 9600 baud, 8 data bits, no
parity bit, 1 stop bit, and no flow control).
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
11062 bytes transferred
Page 11

Switches
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 <password>
console(config)# exit
console# copy running-config startup-config
3.
Download the 6.2.7.6 firmware image from a TFTP server.

Source File Path............................... ./
Data Type...................................... Code
console#show switch
Management Standby
SW Status
Status
--- ---------- --------1
Mgmt Sw
Preconfig
Plugged-in
Switch
Code
Model ID
Model ID
Status
Version
------------- ------------- ------------- ----------N4064F
N4064F
Ok
6.2.7.6
System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
unit active
backup
current-active
next-active
----- ------------ ------------ ----------------- ----------------1
6.0.0.8
6.2.7.6
6.0.0.8
6.0.0.8
backup.
4.

5.
Reload the switch.

console#reload
Page 12

Switches
6.
After switch upgraded to 6.2 image, download the 6.3.0.18 firmware image from a TFTP server.
Source File Path............................... ./
Data Type...................................... Code
console#show switch
Management Standby
SW Status
Status
--- ---------- --------1
Mgmt Sw
Preconfig
Plugged-in
Switch
Code
Model ID
Model ID
Status
Version
------------- ------------- ------------- ----------N4064F
N4064F
Ok
6.2.7.6
System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
unit active
backup
current-active
next-active
----- ------------ ------------ ----------------- ----------------1
6.2.7.6
6.3.0.18
6.2.7.6
6.2.7.6
backup.
7.

8.
Reload the switch.

console#reload
Page 13

Switches
NOTE: 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 more than once during the upgrade procedure.
<184> Jul 27 00:04:42 172.25.137.218-1 UNITMGR[emWeb]: unitmgr.c(6451) 1327 %% Reset
initiated on unit 1, reason: User Request
<186> Jul 27 00:04:42 172.25.137.218-1 General[emWeb]: unitmgr.c(6476) 1328 %% Event(0x0)
Reference platform resetting ...
Rebooting system!

MBist Pass
Nodes online: 1
RTT Norm:44
320 MB, size:
320 MB)
2192 MB, size: 1728 MB)
U-Boot 2010.03-rc1 (Sep 04 2013 - 18:13:27)
DRAM:
2 GB
Flash: 256 MB
In:
serial
Out:
serial
Err:
serial
Net:
Configuring NAE...
Page 14
0 MB ->
464 MB ->

Switches
Net:
Link is up
Configuring PoE...
nae-0
boot in 5 s
Image Name:
System for pct
Created:
2016-02-20
1:29:06 UTC
Image Type:
Data Size:
31561316 Bytes = 30.1 MB
Contents:
Image 0: 3064420 Bytes = 2.9 MB
Image 1: 2641929 Bytes = 2.5 MB
Image 4: 25832776 Bytes = 24.6 MB
Booting using the fdt at 0x9457133c
Starting kernel ...
[
0.000000]
[
0.000000]
[
0.000000]
(GCC) ) #1 SMP
[
0.000000]
[
0.000000]
Initializing cgroup subsys cpuset

Initializing cgroup subsys cpu
Linux version 3.7.10-9939e68c (lvl7build@lc-rtp-009) (gcc version 4.6.3
Thu Jan 14 14:29:22 EST 2016
bootconsole [early0] enabled
CPU revision is: 000c1101 (Netlogic XLP)
Page 15

Switches
[
0.000000] FPU revision is: 00770000
[
[
[
[
[
[
[
Checking for USB Device... done.
============================
Select (1, 2)#
active = /dev/mtd6
Uncompressing python.lzma
Installing Python
Event(0xaaaaaaaa)
started!
<188> Jul 27 11:07:05 0.0.0.0-1 UNITMGR[umCfgUpdateTask]: unitmgr.c(7605) 981 %% Error
retrieving user applications information from unit 2. Failed to download user
applications.
<185> Jul 27 11:20:35 0.0.0.0-1 UNITMGR[unitMgrTask]: unitmgr.c(3029) 985 %% Standby
taking over as Manager of the Stack, reason: Heartbeat Timeout
Console>
Page 16

Switches
9.
After the switch has finished rebooting, log in and verify that the firmware has been updated to the
6.3.0.18 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 Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
unit active
backup
current-active
next-active
----- ------------ ------------ ----------------- ----------------1
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
10. 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.
Stacking Notes
Regarding steps 2 to 6 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 all the switches as backup image
System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
unit
---1
2
3
active
----------6.2.7.6
6.2.7.6
6.2.7.6

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
Linux 2.6.32.9
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
backup
----------- -------------- -------------6.3.0.18
6.2.7.6
6.2.7.6
6.3.0.18
6.2.7.6
6.2.7.6
6.3.0.18
6.2.7.6
6.2.7.6
console# boot system backup

Page 17

Switches
System Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
unit
---1
2
3
active
----------6.2.7.6
6.2.7.6
6.2.7.6

N4064F
CN0VTWN8282982920006A00
0xbc00
Linux 2.6.32.9
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
backup
----------- -------------- -------------6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
Reload the stack of switches.

console#reload
After the stack of switches has finished rebooting, log in and verify that the firmware has been updated to the
6.3.0.18 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 Model ID...................
Machine Type......................
Serial Number.....................
Manufacturer......................
CPU Version.......................
SOC Version.......................
HW Version........................
CPLD Version......................
unit
---1
2
3

N4064F
CN0VTWN8282982920006A00
0xbc00
D067.E59B.17E3
1.3.6.1.4.1.674.10895.3046
XLP308H-A1
BCM56846_A1
3
17
active
backup
----------- ----------- -------------- -------------6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
6.3.0.18
6.2.7.6
6.3.0.18
6.3.0.18
Page 18

Switches
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. 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 console port on the switch (8-No Parity-1-9600-No Flow Control).
a. Use the supplied RJ45 Yost to DB9 serial cable. Connect the RJ45 end to the switch console port
and the DB9 connector to your PC. Set the terminal emulation software (for example., PuTTY) to
the correct settings (default setting 9600 baud, 8 data bits, no parity bit, 1 stop bit, and no flow
control).
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.
Download 6.3.0.18 firmware to the switch using TFTP by selecting option 4 - Load new operational code
from the boot menu.
4.
Verify that the firmware has been updated to the 6.3.0.18 version using the show version command.
Switch Recovery Example

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

============================
Select (1, 2)# 2
Page 19

Switches
Boot Main Menu
==============
2 - Select Baud Rate
3 - Retrieve Logs
4 - Load New Operational Code
5 - Display Operational Code Details
9 - Reboot
10 - Restore Configuration to Factory Defaults
11 - Activate Backup Image
12 - Start Password Recovery
4.
If not already loaded, download the firmware to the switch using TFTP (Select option 4 - Load new
operational code)
Boot Main Menu
==============
2 - Select Baud Rate
3 - Retrieve Logs
4 - Load New Operational Code
5 - Display Operational Code Details
9 - Reboot
10 - Restore Configuration to Factory Defaults
11 - Activate Backup Image
12 - Start Password Recovery
Enter Choice# 4
Creating tmpfs filesystem on /mnt/download for download...done.
Current Active Image# /dev/mtd7
Which Image to Update Active (/dev/mtd7) OR Back-Up (/dev/mtd6)? Select (A/B): A
You selected to update Active Image /dev/mtd7...
Select Mode of Transfer (Press T/X/Y/Z for TFTP/XMODEM/YMODEM/ZMODEM) []:T
Please ensure TFTP server is running to begin Transfer...
Enter Server IP []:10.10.10.200
Enter Host IP []:10.10.10.224
Enter Host Subnet Mask [255.255.255.0]:255.255.0.0
Enter Gateway IP []:10.10.10.254
Enter Filename []:N4000v6.3.0.18.stk
Do you want to continue? Press(Y/N): y
Bringing up eth0 interface...done.
Adding default gateway 10.10.10.254 to the Routing Table...done.
Erasing /dev/mtd7!!!
Erasing 128 Kibyte @ 17e0000 -- 99 % complete.
Updating code file...done.
Code Update Instructions Found!
Critical components modified on Active Partition -- System Reboot Recommended!
Reboot? (Y/N): y
Rebooting...
starting pid 11
Rebooting system!
Page 20

Switches
MBist Pass
Nodes online: 1
RTT Norm:44
320 MB, size:
320 MB)
2192 MB, size: 1728 MB)
U-Boot 2010.03-rc1 (Sep 04 2013 - 18:13:27)

DRAM:
2 GB
Flash: 256 MB
In:
serial
Out:
serial
Err:
serial
Net:
Configuring NAE...
Net:
Page 21
0 MB ->
464 MB ->

Switches
Link is up
Configuring PoE...
nae-0
boot in 5 s
Image Name:
System for pct
Created:
2015-02-12 21:07:58 UTC
Image Type:
Data Size:
24381532 Bytes = 23.3 MB
Contents:
Image 0: 3063073 Bytes = 2.9 MB
Image 1: 2330239 Bytes = 2.2 MB
Image 4: 18966028 Bytes = 18.1 MB
Booting using the fdt at 0x94524c70
Starting kernel ...
[
0.000000] Initializing cgroup subsys cpuset
[
0.000000] Initializing cgroup subsys cpu
[
0.000000] Linux version 3.7.10-4134a969 (lvl7build@lc-rtp-020) (gcc version 4.6.3
(GCC) ) #1 SMP Wed Dec 10 20:24:48 EST 2014
[
0.000000] bootconsole [early0] enabled
[
0.000000] CPU revision is: 000c1101 (Netlogic XLP)
[
0.000000] FPU revision is: 00770000
[
[
[
[
[
[
[
Checking for USB Device... mount: mounting /dev/sda1 on /media/sda1 failed: Invalid
argument
done.
Page 22

Switches

============================
Select (1, 2)#
active = /dev/mtd6
SyncDB Running...
Event(0xaaaaaaaa)started!
console>
5.
Verify that the 6.3.0.18 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.
Page 23

Switches
Firmware Downgrade
Downgrading from 6.3.0.18 to 6.2.x.x is supported on Dell Networking N4000 Series switches. Downgrading from
6.3.0.18 to an earlier 5.x.x.x release is NOT supported on Dell Networking N4000 Series switches with B2 CPU.
IMPORTANT: Dell Networking N4000 Series switches (XLP30H-B2 CPU) require

firmware version 6.0.0.8 or later (6.3.0.18) and cannot be downgraded to earlier
releases.
Also, 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 by
configuring the switch using CLI command boot auto-copy-sw allow-downgrade before loading new firmware
onto the stack master.
Boot Code Upgrade and Downgrade

No Boot Code upgrade is required for N4064/N4064F/N4032/N4032F switches after upgrading from 6.2.x.x to
6.3.0.18 firmware.
No Boot Code downgrade is required for N4064/N4064F/N4032/N4032F switches
Hardware Supported
Dell Networking N4032 Ethernet Switch

Dell Networking N4032F Ethernet Switch
Dell Networking N4064 Ethernet Switch
Dell Networking N4064F Ethernet Switch
End of document
Page 24

Upgrading Dell Networking N4000 Series Switches From Version 6.x.x.x To 6.3.0.18

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Upgrading Dell Networking N4000 Series Switches From Version 6.x.x.x To 6.3.0.18

Uploaded by

Copyright:

Available Formats

Dell Networking N4064/N4064F/N4032/N4032F

Upgrading Dell Networking

Date: August 2016

Information in this document is subject to change without notice.

Information in this document is subject to change without notice.

Subject to Change Without Notice

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

IMPORTANT: Dell Networking N4000 Series switches support 6.0.0.8 or later

Dell Networking N4032

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches from

Back up your configuration.

Activate 6.3.0.18 firmware.

Reload the switch.

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Download the 6.3.0.18 firmware image from a TFTP server.

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Switch

Activate the 6.3.0.18 firmware

Reload the switch.

NetLogic XLP Stage 1 Loader (X-Loader) [Big-Endian] (Nov 30 2011 - 18:10:13)

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Boot Options

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

1 - Start Operational Code

Dell Networking Switch

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Switch

console# boot system backup

Dell Networking Switch

Reload the stack of switches.

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Switch

Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches from

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Back up your configuration before upgrading the switch/stack to 6.3.0.18.

Activate 6.2.7.6 firmware.

Reload the switch.

Activate 6.3.0.18 firmware.

Reload the switch.

Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches from

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Download the 6.2.7.6 firmware image from a TFTP server.

Dell Networking Switch

Activate the 6.2.7.6 firmware

Reload the switch.

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Switch

Activate the 6.3.0.18 firmware

Reload the switch.

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

NetLogic XLP Stage 1 Loader (X-Loader) [Big-Endian] (Nov 30 2011 - 18:10:13)

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Initializing cgroup subsys cpuset

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Switch

Dell Networking Switch

console# boot system backup

Upgrade Procedure Dell Networking N4064/N4064F/N4032/N4032F

Dell Networking Switch