From the error, you might be facing an issue with firmware communication between switches. The switches seems are not at the same firmware level. Usually when the switches are stacked, the firmware will propagate. But from that error, there is a communication issue. It did not indicate which switch though. Can you update the firmware to the latest.
the system's firmware is important being up to date newer version may include bug fixes for similar issues. You can also check SFP+ optics are properly seated and connected. You can check port configuration and set to correct mode.
So, after 270 days with latest 6.5.4.23, the stack restarted again. I believe that it is still a bug in N3/4K series. Any one got other ideas ?
Thanks
core-stack#show switch
Management Standby Preconfig Plugged-in Switch Code
SW Status Status Model ID Model ID Status Version
--- ---------- --------- ------------- ------------- ------------- -----------
1 Mgmt Sw N4032F N4032F OK 6.5.4.23
2 Stack Mbr Oper Stby N4032F N4032F OK 6.5.4.23
Switch............................ 1
Management Status................. Management Switch
Switch Type....................... 0xd8420002
Preconfigured Model Identifier.... N4032F
Plugged-in Model Identifier....... N4032F
Switch Status..................... OK
Switch Description................ Dell Networking N4032F
Unit Description.................. sw01
Detected Code Version............. 6.5.4.23
Detected Code in Flash............ 6.5.4.23
SFS Last Attempt Status........... None
Serial Number..................... redacted
Up Time........................... 266 days 14 hrs 7 mins 9 secs
core-stack#show switch 2
Switch............................ 2
Management Status................. Stack Member
Switch Type....................... 0xd8420002
Preconfigured Model Identifier.... N4032F
Plugged-in Model Identifier....... N4032F
Switch Status..................... OK
Switch Description................ Dell Networking N4032F
Unit Description.................. sw02
Detected Code Version............. 6.5.4.23
Detected Code in Flash............ 6.5.4.23
SFS Last Attempt Status........... None
Serial Number..................... redacted
Up Time........................... 0 days 14 hrs 55 mins 40 secs
core-stack#show log
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1757 %% WARN Reconciliation error: Unit/Port 0/23: CmdId 40 does not have a valid value, operValid 1 shadowValid 0
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1756 %% WARN Reconciliation error: Unit/Port 0/23: CmdId 15 does not have a valid value, operValid 128 shadowValid 0
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1755 %% WARN Reconciliation error: Unit/Port 0/23: CmdId 13 does not have a valid value, operValid 32 shadowValid 0
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1754 %% WARN Reconciliation error: Unit/Port 0/6: CmdId 40 does not have a valid value, operValid 1 shadowValid 0
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1753 %% WARN Reconciliation error: Unit/Port 0/6: CmdId 15 does not have a valid value, operValid 128 shadowValid 0
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1752 %% WARN Reconciliation error: Unit/Port 0/5: CmdId 40 does not have a valid value, operValid 1 shadowValid 0
<188> Oct 16 02:18:12 core-stack-1 DRIVER[USL Control Tas]: l7_usl_port_db.c(9515) 1751 %% WARN Reconciliation error: Unit/Port 0/5: CmdId 15 does not have a valid value, operValid 128 shadowValid 0
<189> Oct 16 02:18:10 core-stack-1 SIM[emWeb]: sim_svc_port.c(337) 1636 %% NOTE Service port IPv4 address has been set to 10.11.19.10.
<189> Oct 16 02:18:10 core-stack-1 SIM[emWeb]: sim_svc_port.c(337) 1635 %% NOTE Service port IPv4 address has been set to 0.0.0.0.
<189> Oct 16 02:18:10 core-stack-1 SIM[emWeb]: sim_svc_port.c(337) 1634 %% NOTE Service port IPv4 address has been set to 0.0.0.0.
<189> Oct 15 23:18:08 0.0.0.0-1 TRAPMGR[trapTask]: traputil.c(721) 1399 %% NOTE Link on Vl1 is failed
<189> Oct 15 23:18:08 0.0.0.0-1 TRAPMGR[trapTask]: traputil.c(721) 1398 %% NOTE Link Down: Vl1
<189> Oct 15 23:18:08 0.0.0.0-1 TRAPMGR[trapTask]: traputil.c(721) 1397 %% NOTE Unit 2 is added to the stack
<189> Oct 15 23:18:08 0.0.0.0-1 TRAPMGR[trapTask]: traputil.c(721) 1396 %% NOTE Stack master unit 2 is failed
<185> Oct 15 23:18:06 0.0.0.0-1 UNITMGR[unitMgrTask]: unitmgr.c(3057) 1337 %% ALRT Standby taking over as Manager of the Stack, reason: Heartbeat Timeout
<190> Oct 15 23:18:06 0.0.0.0-1 SIM[unitMgrTask]: sysapi.c(667) 1336 %% INFO Failed to separate component config from fastpathRun.cfg
DELL-Joey C
Moderator
•
4.1K Posts
0
January 20th, 2025 08:13
Hi,
From the error, you might be facing an issue with firmware communication between switches. The switches seems are not at the same firmware level. Usually when the switches are stacked, the firmware will propagate. But from that error, there is a communication issue. It did not indicate which switch though. Can you update the firmware to the latest.
What was the issue that it recovered by itself?
(edited)
dooh
1 Rookie
•
3 Posts
0
January 20th, 2025 10:39
Hi Joey,
Thank you.
It seems that unit 1 experienced the issue, both switches are at the same level and the stack recovered itself in about 3 minutes.
1 6.5.4.20 6.3.0.18 6.5.4.20 6.5.4.20
2 6.5.4.20 6.3.0.18 6.5.4.20 6.5.4.20
I could schedule a maintenance window to update to 6.5.4.23, but I do not see any related changes in the changelog.
DELL-Erman O
Moderator
•
3K Posts
0
January 20th, 2025 11:28
Hi,
the system's firmware is important being up to date newer version may include bug fixes for similar issues. You can also check SFP+ optics are properly seated and connected. You can check port configuration and set to correct mode.
dooh
1 Rookie
•
3 Posts
0
October 16th, 2025 14:16
Hi,
So, after 270 days with latest 6.5.4.23, the stack restarted again. I believe that it is still a bug in N3/4K series. Any one got other ideas ?
Thanks
(edited)