As to what caused it could be a number of things. the command "show switch stack-port diag" is often my first goto and see if there are any errors counters. if there are then it can be cable or stack-port itself. There is also a chance that the "keep alive" from that switch was just not heard from the master switch so the member switch stepped forward in order to take over the role of master which kicked it out the stack. This can be caused by large CPU directed traffic hitting the "brain"CPU of the Master switch or just over saturation on the stack-port going to that member switch.
Sadly the list can gon on and on. If it continues to cause an issue I'd say update the code as they do make corrections that affect stacking.
No changes were made. Yes, I must bring the firmware up-to-date. I have been postponing it for a long time but I have to do it now. I was just wondering whether anyone else has experienced a similar behaviour.
Sounds like one or more of the stack members have left the stack. Use a console cable to connect to each switch in the stack. Use command "show switch" and you'll most likely see that there are switches that think they are the sole remaining member of the stack.
On the switch that needs to re-join the existing stack: Disconnect power cable reseat stacking cable ate both ends re-connect power cable
- Muzz -
1 Rookie
•
19 Posts
0
April 12th, 2023 09:00
igano,
As to what caused it could be a number of things. the command "show switch stack-port diag" is often my first goto and see if there are any errors counters.
if there are then it can be cable or stack-port itself.
There is also a chance that the "keep alive" from that switch was just not heard from the master switch so the member switch stepped forward in order to take over the role of master which kicked it out the stack. This can be caused by large CPU directed traffic hitting the "brain"CPU of the Master switch or just over saturation on the stack-port going to that member switch.
Sadly the list can gon on and on. If it continues to cause an issue I'd say update the code as they do make corrections that affect stacking.
I hope that helped
DELL-Charles R
Moderator
•
4.7K Posts
0
April 3rd, 2023 12:00
Hello igano,
Was any work or changes being made on the network around the time this started?
It is a little behind on firmware. Could you bring the firmware up to date and test results?
Firmware update: https://dell.to/3m47FBu
igano
1 Rookie
•
35 Posts
0
April 6th, 2023 09:00
Hi
No changes were made. Yes, I must bring the firmware up-to-date. I have been postponing it for a long time but I have to do it now. I was just wondering whether anyone else has experienced a similar behaviour.
Thank you
- Muzz -
1 Rookie
•
19 Posts
0
April 10th, 2023 15:00
igano,
Sounds like one or more of the stack members have left the stack.
Use a console cable to connect to each switch in the stack. Use command "show switch" and you'll most likely see that there are switches that think they are the sole remaining member of the stack.
On the switch that needs to re-join the existing stack:
Disconnect power cable
reseat stacking cable ate both ends
re-connect power cable
it should rejoin stack
igano
1 Rookie
•
35 Posts
0
April 12th, 2023 03:00
Hi Muzz
Thanks for your reply. I rebooted the switch and is back in the stack now. I was just wondering what caused this behaviour.
Thank you
igano
1 Rookie
•
35 Posts
0
April 13th, 2023 03:00
Thank you for your time Muzz.