Hi.

We always recommend updating both, for that reason we also recommend scheduling a timeframe when you will be able to do all the necessary actions.

Updating the boot code / CPLD is possible only via CLI (SSH/Telnet but not just console), the action could also happen remotely. 

Please take extra caution while Upgrading or Downgrading CPLD as improper upgrade/downgrade might result in an unresponsive switch.

This is what I found about the CPLD/boot code versions and the corresponding FW:

CPLD version 20 is available in release 6.5.1.1 and later 

CPLD version 17 is available in release 6.3.3.9 and later 

Note:
After upgrading the switches to 6.5.1.1, the CPLD can be updated to version 20 from CLI using the command update cpld.
To update CPLD on stack members, run devshell cpldUpdate command from serial console.

Caution:

Please DO NOT power-cycle the switch when CPLD update is in progress. After CPLD update completes, the switch will reset on its own.

Another note:
Upgrading firmware requires power cycling the switch. There will be a service outage required to complete this process. Updating the boot code will power cycle the switch or stack a second time. Switches in a stack configuration cannot be updated individually. There will be an outage of this switch or stack to update the firmware.

Hope that helps a bit.

BR
Stefan

Well my question was about bootcode and how important it is, and not about CPLD.

How do I know which version is installed (without the console)? Does it actually need upgrading? But I asked that already.

Hi.

First, you have to set up SSH for management access.

https://dell.to/3b6eRog

Followed by establishing a connection and sending the command show version.

This will show you all the needed data. Here is an example output:

Machine Description............... Dell Networking Switch
System Model ID................... N4064
Machine Type...................... Dell Networking N4064
Serial Number..................... X01-64C-55
Manufacturer...................... 0xbc00
Burned In MAC Address............. D067.E5C0.D19B
System Object ID.................. 1.3.6.1.4.1.674.10895.3045
CPU Version....................... XLP308H-A1
SOC Version....................... BCM56846_A1
HW Version........................ 3
CPLD Version...................... 14
Boot Version...................... v1.0.21
Image File........................ N3000-ONv6.0.0.1
Software Capability............... Stack Limit = 12, VLAN Limit = 4093

CPLD and boot code is very identical that's why I mentioned both in my previous post. Sorry for any misunderstandings.

I'm not sure this "boot version" refers to the "bootcode" the Upgrade Guide is talking about.

The boot code version apparently looks like this:

U-Boot SPL 2012.10-00079-g20827d2 (May 22 2017 - 16:58:14)

and can only be seen on the console during boot !?

The question remains: How important is it? And how dangerous is it not to upgrade it.

That statement still doesn't answer any of my initial questions.

It is an important update. Page 17 of the upgrade guide “Boot Code upgrade is required”

The instructions don’t have an exception for switches already running the current boot code. It is recommended to run the update on every switch. It may work without it but that is at your own risk and we are not liable if it causes any issues from not updating it. There is not a list for which versions, but it looks like anything that 6.5.x has the current bootcode.

The instructions say: "Please skip next two steps if switch is already running with the latest boot-code version"

Does that mean running the update nevertheless will do harm or should we just run it anyway since we're not able to tell which version it is currently running (not being able to tell not being our fault because it only shows on the console and only during boot)

It won’t hurt it to run it again.

Why is it always this complicated to obtain that simple piece of advice: "If you're not sure, just run it again"? The docs should just say so, especially when it is very hard to obtain the currently running version.

To be on the safe side I've consulted with Support who tell me that I must not update an already up-to-date bootcode.

Great.

Hi Jammac, 

I'm in the same situation today. Did you finally get a solution to the problem ?

Thanks,

regards,

Phil.