I have a large number of 2024p/2048p switches that we deployed last summer with 6.3.0.15,16 or 18 and CPLD 13. I was looking over the notes for the upgrade to 6.3.2.7 and trying to figure out the impact of the CPLD update from 13 to 15. The language of the patch notes is not worded as strongly as most of the other content, they mention you can upgrade it where for other components they tell you that you must upgrade it (like boot code), but that you MUST downgrade it to go backwards.
In addition, they requirement to visit every switch and connect directly to it/power cycle it locally is a gigantic burden.
Its it required to update to CPLD 15 at the same time as upgrading to 6.3.2.7? Is is possible to go to 6.3.2.7 and stay on CPLD 13 until someone can go to each switch and do the CPLD update (weeks or months), or should we stop at some lower release, like 6.3.2.6 that did not yet have the CPLD update until we can schedule the visits?
It is recommended for everything to be at the latest version. It may work with the older CPLD and the newer firmware, but it would be better to have them all updated at the same time. Just updating the firmware to a version that doesn’t need the newest CPLD is the best option.
We have three Dell Networking N2048 units in a stack. I upgraded from 6.3.2.3 --> 6.3.3.8 today. Going by the included PDF upgrading guide, I attempted to telnet into the stack and issue the command 'update cpld' to get from CPLD 13 --> CPLD 15.
The console line showed that it was issuing the CPLD update command and after about a minute it printed a new line saying that it successfully issued the update command and returned me to my enable prompt.
However, when I go back into the console and issue 'show version' my CPLD version is still 13. I can't seem to get it to update the CPLD version to 15 from the stack master. Any help is appreciated.
Your solution is good, but it will not work on stack with only 2 members. I can't demote the current Mgmt switch to standby. Example:
SWCORE_01_MRT02#show switch
Management Standby Preconfig Plugged-in Switch Code
SW Status Status Model ID Model ID Status Version
--- ---------- --------- ------------- ------------- ------------- -----------
1 Stack Mbr Cfg Stby N3048 N3048 OK 6.1.0.6
2 Mgmt Sw N3048 N3048 OK 6.1.0.6
Whenever i try to put switch2 as standby i get this message
SWCORE_01_MRT02#configure
SWCORE_01_MRT02(config)#stack
SWCORE_01_MRT02(config-stack)#standby 2
Error: Management unit cannot be set as Standby
Maybe i'll have to deal with uploading the startup-config to a tftpd server, edit the "standby" line and download it again to startup-config.
Hi Guys, hope you can help me, a have a situation with my stack , it's was running well, but i figurated that the cpdl was diferents in the 3 switches.. the master was in 20 .. the other was 13 and 15 ... then a ran the command to updates the other 2 .. and my stack come down....
my firmware running its 6.5.2.15 , on N2048P...
just have one switch alive... the others two says Unassigned on the part of managenet status ... and not present on the switch status...
MXTIJCORSW05>show switch
Management Standby Preconfig Plugged-in Switch Code SW Status Status Model ID Model ID Status Version --- ---------- --------- ------------- ------------- ------------- ----------- 1 Mgmt Sw N2048P N2048P OK 6.5.2.15 2 Unassigned N2048P Not Present 0.0.0.0 3 Unassigned N2048P Not Present 0.0.0.0
Can you confirm that all 3 switches are running the same firmware and CPLD? Are the other 2 switches, console serial are able to access? Can you also confirm with the stack cables, are seated properly? Have you also tried rebooting the switch? In your situation, reboot switch 2 and wait for it to be fully loaded then move on with switch 3.
DELL-Joey C
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’ if I did.
ordovice
11 Posts
12606
1
Posted December 19th, 2017 18:00
Wanted to chime in with how we've done it (completely remotely)