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

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

N4064/N4064F/N4032/N4032F
Switches to 6.1.0.6 Firmware
Date: July 2014

Information in this document is subject to change without notice.
Copyright © 2014 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 ............................................................................................................. 1
Upgrade Overview ......................................................................................................... 2
Upgrade Procedure for Dell Networking N4064/N4064F/N4032/N4032F Switches ............................ 2
Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches............................... 3
Stacking Notes ............................................................................................................. 8
Switch Recovery Procedure .............................................................................................. 9
Switch Recovery Example ...............................................................................................10
Firmware Downgrade ....................................................................................................14
Boot Code Upgrade and Downgrade ...................................................................................14
Hardware Supported .....................................................................................................14
End of document .........................................................................................................14
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.1.0.6 or later.
IMPORTANT: Dell Networking N4000 Series switches support 6.0.0.8 or later

firmware (6.1.0.6). Both Dell Networking N4000 Series and Dell Networking 8100
series switches can share the same firmware image version (N4000v6.1.0.6.stk)
IMPORTANT: Administrators upgrading N4000 series switches from 6.x.x.x to

6.1.0.6 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.1.0.6 firmware may result in an inoperable switch!
IMPORTANT: Dell Networking N4000 Series switches require firmware version

6.0.0.8 or later (6.1.0.6) 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.1.0.6). 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

Dell Networking N4032 4G4FP
Dell Networking N4032 TAA VYN03
Dell Networking N4032F 5KGDH
Dell Networking N4032F TAA R5V1W
Dell Networking N4064 KK3D4
Dell Networking N4064 TAA JPVRH
Dell Networking N4064F FWYM4
Dell Networking N4064F TAA 8V91F
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 1
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

The upgrade procedure given below upgrades an individual switch or a stack of switches running firmware version
6.x.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.x.x.x version of firmware to the 6.1.0.6 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.1.0.6 firmware image (N4000v6.1.0.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. Activate 6.1.0.6 firmware.
5. Reload the switch.
Page 2
Switches
Upgrade Example for Dell Networking N4064/N4064F/N4032/N4032F Switches

This example shows an annotated upgrade example for a N4064F switch running 6.x.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.1.0.6 firmware image from a TFTP server.

console#copy tftp://10.10.10.200/N4000v6.1.0.6.stk backup
Transfer Mode.................................. TFTP
Server IP Address.............................. 10.10.10.200
Source File Path............................... ./
Source Filename................................ N4000v6.1.0.6.stk
Data Type...................................... Code
Destination Filename........................... backup
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...

21413073 bytes transferred...
File contents are valid. Copying file to flash...
Attempting to send the STK file to other units in the stack...
File transfer operation completed successfully.
Page 3
Switches
console#show switch
Management Standby Preconfig Plugged-in Switch Code

SW Status Status Model ID Model ID Status Version
--- ---------- --------- ------------- ------------- ------------- -----------
1 Mgmt Sw N4064F N4064F OK 6.0.0.8
console#show version
Machine Description............... Dell Networking Switch
System Model ID................... N4064F
Machine Type...................... Dell Networking N4064F
Serial Number..................... CN0VTWN8282982920006A00
Manufacturer...................... 0xbc00
Operating System.................. Linux 2.6.32.9
Burned In MAC Address............. D067.E59B.17E3
System Object ID.................. 1.3.6.1.4.1.674.10895.3046
CPU Version....................... XLP308H-A1
SOC Version....................... BCM56846_A1
HW Version........................ 3
CPLD Version...................... 17
unit active backup current-active next-active

----- ------------ ------------ ----------------- -----------------
1 6.0.0.8 6.1.0.6 6.0.0.8 6.0.0.8
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.1.0.6 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.
<183> Jun 19 05:29:26 172.25.127.212-2 UNITMGR[79911492]: unitmgr.c(6086) 1299 %% Reset
initiated on unit 1, reason: User Request
Reference platform resetting ...

starting pid 1184, tty '': '/etc/rc.d/rc.reboot'
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
Kernel restart function
Page 4
Switches
NetLogic XLP Stage 1 Loader (X-Loader) [Big-Endian] (Nov 30 2011 - 18:10:13)

MBist Pass
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 ( 0 MB ->
320 MB, size: 320 MB)
NBU0 DRAM BAR1 base: 001d0000 limit: 0088f000 xlate: 00090001 node: 00000000 ( 464 MB ->
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:17:e4
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...
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
Page 5
Switches
Created: 2013-12-13 6:09:04 UTC

Image Type: MIPS Linux Multi-File Image (gzip compressed)
Data Size: 21240245 Bytes = 20.3 MB
Load Address: ffffffff84000000
Entry Point: ffffffff84006d10
Contents:
Image 0: 2895437 Bytes = 2.8 MB
Image 1: 1719916 Bytes = 1.6 MB
Image 2: 37096 Bytes = 36.2 kB
Image 4: 16587293 Bytes = 15.8 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 0x94466d88
Uncompressing Multi-File Image ... OK
Starting kernel ...
0:<5>Linux version 2.6.32.9 (bradyr@ldt-rtp-04) (gcc version 4.4.5 20100516 (prerelease)

(GCC) ) #26 SMP PREEMPT Mon Aug 26 10:48:48 EDT 2013
0:Enabling XLP CPU (XLP308Lite+ Rev A1): pr id 0xc1101 smp id 0
0:Cached handle for FDT @ 9000000094466d88
0:FDT Cmdline: loader=uboot console=ttyS0,9600 quiet console=ttyS0,9600
initrd=1000000@02000000 root=/dev/ram mtdparts=physmap-flash.0:128k(X-Loader-RO),640k(u-
boot),128k(VPD),128k(u-boot-
env),3072k(diagnostics),61440k(jffs2),24576k(image1),24576k@98304k(image2),139264k@122880k
(unused) mem=176m@16m mem=1536m@512m
0:FDT: cpu_cells: 1 onlinemask[0]: 00000033
0:xlp_napi_vc_mask 0xb
0:fdt_cpumask: 00000000,00000000,00000000,00000033
0:ICI config not enabled
0:xlp3xx/2xx Regex (netl7) vendor_device id:0x1019184e
xlp_regex_base_pcim:0xd0180000
xlp_regex_base_pcie:0x1802d000
0:<7>node 0: Supported CPUMASK (0) -> 00000000,00000000,00000000,00000001
0:<7>node 0: Supported CPUMASK (1) -> 00000000,00000000,00000000,ffffffff
0:<7>node 0: Supported CPUMASK (2) -> 00000000,00000000,00000000,0000ffff
0:<7>node 0: Supported CPUMASK (3) -> 00000000,00000000,00000000,ffff0000
0:MSGRING_NAPI: Initializing NLM NAPI subsystem
0:<7>SETTING UP EARLY SERIAL ACCESS

0:node@0: t0_bitmap = 0x00000011, cores_bitmap = 0x00000003 threads_to_enable 0x22
0:[enable_cores] node@0, cores_bitmap = 0x00000003 cbitmap = 0x00000002
0:Enabled cpus (0x00000033) on node@0
0:<6>bootconsole [early0] enabled
0:<6>CPU revision is: 000c1101 (XLP308Lite+ Rev A1)
0:<6>FPU revision is: 00770000
0:Checking for the multiply/shift bug... 0:no.
0:Checking for the daddiu bug... 0:no.
0:<6>Determined physical RAM map:
starting pid 882, tty '': '/etc/init.d/rcS'
starting pid 1003, 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 6
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
SyncDB Running...
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
Reflashing port 53 to Firmware in OPR Code
Migrating from version 1.66 to 1.66
Step 1: Halting the system... Halted.
Step 2: Uploading the SPI loader and data into on-chip memory.
Step 3: Start copying to SPIROM... Done.
Step 4: Wait for programming phase to complete... Done.
Step 5: Restarting system.
Step 6: Verify processor is running... Started.
Step 7: Check on-chip firmware level and CRC... OK.
PHY Flashing Successful
<184> Jun 19 05:31:23 0.0.0.0-1 General[83959388]: bootos.c(179) 8 %% Event(0xaaaaaaaa)
started!
(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 6.1.0.6
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 Object ID.................. 1.3.6.1.4.1.674.10895.3046
SOC Version....................... BCM56846_A1
HW Version........................ 3
CPLD Version...................... 17

----- ------------ ------------ ----------------- -----------------
1 6.1.0.6 6.0.0.8 6.1.0.6 6.1.0.6
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 7
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 Object ID.................. 1.3.6.1.4.1.674.10895.3046
SOC Version....................... BCM56846_A1
HW Version........................ 3
CPLD Version...................... 17

---- ----------- ----------- -------------- --------------
1 6.0.0.8 6.1.0.6 6.0.0.8 6.0.0.8
2 6.0.0.8 6.1.0.6 6.0.0.8 6.0.0.8
3 6.0.0.8 6.1.0.6 6.0.0.8 6.0.0.8
console# boot system backup

Activating image backup ..
System Object ID.................. 1.3.6.1.4.1.674.10895.3046
SOC Version....................... BCM56846_A1
HW Version........................ 3
CPLD Version...................... 17

---- ----------- ----------- -------------- --------------
1 6.0.0.8 6.1.0.6 6.0.0.8 6.1.0.6
2 6.0.0.8 6.1.0.6 6.0.0.8 6.1.0.6
3 6.0.0.8 6.1.0.6 6.0.0.8 6.1.0.6
Reload the stack of switches.

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
Page 8
Switches
After the stack of switches has finished rebooting, log in and verify that the firmware has been updated to the
6.1.0.6 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 Object ID.................. 1.3.6.1.4.1.674.10895.3046
SOC Version....................... BCM56846_A1
HW Version........................ 3
CPLD Version...................... 17

---- ----------- ----------- -------------- --------------
1 6.1.0.6 6.0.0.8 6.1.0.6 6.1.0.6
2 6.1.0.6 6.0.0.8 6.1.0.6 6.1.0.6
3 6.1.0.6 6.0.0.8 6.1.0.6 6.1.0.6
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).
RJ-45 serial console port
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.1.0.6 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.1.0.6 version using the show version command.
Page 9
Switches
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
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
Page 10
Switches
Enter Gateway IP []:10.10.10.254

Enter Filename []:N4000v6.1.0.6.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
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
Kernel restart function
NetLogic XLP Stage 1 Loader (X-Loader) [Big-Endian] (Nov 30 2011 - 18:10:13)

MBist Pass
Nodes online: 1
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 ( 0 MB ->
320 MB, size: 320 MB)
NBU0 DRAM BAR1 base: 001d0000 limit: 0088f000 xlate: 00090001 node: 00000000 ( 464 MB ->
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
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:17:e4
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
Page 11
Switches
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...
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: 2013-12-13 6:09:04 UTC
Image Type: MIPS Linux Multi-File Image (gzip compressed)
Data Size: 21240245 Bytes = 20.3 MB
Load Address: ffffffff84000000
Entry Point: ffffffff84006d10
Contents:
Image 0: 2895437 Bytes = 2.8 MB
Image 1: 1719916 Bytes = 1.6 MB
Image 4: 16587293 Bytes = 15.8 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 0x94466d88
Uncompressing Multi-File Image ... OK
Starting kernel ...
0:<5>Linux version 2.6.32.9 (bradyr@ldt-rtp-04) (gcc version 4.4.5 20100516 (prerelease)

(GCC) ) #26 SMP PREEMPT Mon Aug 26 10:48:48 EDT 2013
0:Enabling XLP CPU (XLP308Lite+ Rev A1): pr id 0xc1101 smp id 0
0:Cached handle for FDT @ 9000000094466d88
0:FDT Cmdline: loader=uboot console=ttyS0,9600 quiet console=ttyS0,9600
initrd=1000000@02000000 root=/dev/ram mtdparts=physmap-flash.0:128k(X-Loader-RO),640k(u-
boot),128k(VPD),128k(u-boot-
env),3072k(diagnostics),61440k(jffs2),24576k(image1),24576k@98304k(image2),139264k@122880k
(unused) mem=176m@16m mem=1536m@512m
0:FDT: cpu_cells: 1 onlinemask[0]: 00000033
0:xlp_napi_vc_mask 0xb
0:fdt_cpumask: 00000000,00000000,00000000,00000033
0:ICI config not enabled
0:xlp3xx/2xx Regex (netl7) vendor_device id:0x1019184e
xlp_regex_base_pcim:0xd0180000
xlp_regex_base_pcie:0x1802d000
0:<7>node 0: Supported CPUMASK (2) -> 00000000,00000000,00000000,0000ffff
0:<7>node 0: Supported CPUMASK (3) -> 00000000,00000000,00000000,ffff0000
Page 12
Switches

0:MSGRING_NAPI: Initializing NLM NAPI subsystem
0:<7>SETTING UP EARLY SERIAL ACCESS

0:node@0: t0_bitmap = 0x00000011, cores_bitmap = 0x00000003 threads_to_enable 0x22
0:[enable_cores] node@0, cores_bitmap = 0x00000003 cbitmap = 0x00000002
0:Enabled cpus (0x00000033) on node@0
0:<6>bootconsole [early0] enabled
0:<6>CPU revision is: 000c1101 (XLP308Lite+ Rev A1)
0:<6>FPU revision is: 00770000
0:Checking for the multiply/shift bug... 0:no.
0:Checking for the daddiu bug... 0:no.
0:<6>Determined physical RAM map:
starting pid 882, tty '': '/etc/init.d/rcS'
starting pid 1003, 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!

============================

Select (1, 2)#
active = /dev/mtd6
Extracting Operational Code from .stk file...done.
Loading Operational Code...done.
Decompressing Operational Code...done.
Uncompressing apps.lzma
SyncDB Running...
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
Reflashing port 53 to Firmware in OPR Code
Migrating from version 1.66 to 1.66
Step 1: Halting the system... Halted.
Step 2: Uploading the SPI loader and data into on-chip memory.
Step 3: Start copying to SPIROM... Done.
Step 4: Wait for programming phase to complete... Done.
Step 5: Restarting system.
Step 6: Verify processor is running... Started.
Step 7: Check on-chip firmware level and CRC... OK.
PHY Flashing Successful
<186> Jun 19 05:40:23 0.0.0.0-1 General[83959388]: bootos.c(179) 8 %% Event(0xaaaaaaaa)
started!
(Unit 1 - Waiting to select management unit)>
Applying Global configuration, please wait ...
Applying Interface configuration, please wait
console>
5. Verify that the 6.1.0.6 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 13
Switches
Firmware Downgrade
Downgrading from 6.1.0.6 to 6.x.x.x is supported on Dell Networking N4000 Series switches. Downgrading from
6.1.0.6 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.1.0.6) 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.x.x.x to
6.1.0.6 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 14

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

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

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

Diunggah oleh

Hak Cipta:

Format Tersedia

Dell™ Networking

Upgrading Dell™ Networking

Date: July 2014

Subject to Change Without Notice

IMPORTANT: Dell Networking N4000 Series switches support 6.0.0.8 or later

IMPORTANT: Administrators upgrading N4000 series switches from 6.x.x.x to

IMPORTANT: Dell Networking N4000 Series switches require firmware version

Part Numbers for Dell Networking N4000 Series P/N

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

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

3. Download the 6.1.0.6 firmware image from a TFTP server.

Management access will be blocked for the duration of the transfer

TFTP Code transfer starting...

Management Standby Preconfig Plugged-in Switch Code

unit active backup current-active next-active

1 6.0.0.8 6.1.0.6 6.0.0.8 6.0.0.8

4. Activate the 6.1.0.6 firmware

5. Reload the switch.

Configuration Not Saved!

Reference platform resetting ...

syncing filesystems....This may take a few moments

Kernel restart function

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

U-Boot 2010.03-rc1 (Sep 04 2013 - 18:13:27)

Created: 2013-12-13 6:09:04 UTC

Starting kernel ...

0:<5>Linux version 2.6.32.9 (bradyr@ldt-rtp-04) (gcc version 4.4.5 20100516 (prerelease)

0:<7>SETTING UP EARLY SERIAL ACCESS

Dell Networking Boot Options

1 - Start Operational Code

Select (1, 2)#

unit active backup current-active next-active

Regarding steps 2, 3 and 4 above:

unit active backup current-active next-active

console# boot system backup

unit active backup current-active next-active

Reload the stack of switches.

Configuration Not Saved!

unit active backup current-active next-active

Switch Recovery Procedure

NOTE: The Switch Recovery procedure requires one to connect to each

RJ-45 serial console port

Switch Recovery Example

2. Power cycle the switch

3. When the boot menu appears, select 2 – Start Boot Menu

1 - Start Operational Code

Select (1, 2)# 2

Boot Main Menu

Boot Main Menu

Please ensure TFTP server is running to begin Transfer...

Enter Gateway IP []:10.10.10.254

The system is going down NOW!

Kernel restart function

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

U-Boot 2010.03-rc1 (Sep 04 2013 - 18:13:27)

xlp_nae_config_lane_gmac with cplx_mask=0x1 and config=0x1111

Starting kernel ...

0:<5>Linux version 2.6.32.9 (bradyr@ldt-rtp-04) (gcc version 4.4.5 20100516 (prerelease)

0:<7>node 0: Supported CPUMASK (7) -> 00000000,00000000,00000000,00000000

0:<7>SETTING UP EARLY SERIAL ACCESS

Dell Networking Boot Options

1 - Start Operational Code

Select (1, 2)#