I have another concern. Is there a risk for the other switch that still operates that this switch could have issues ? For exemple, could this active switch reboot or close connection to production servers during the time the other unassigned switch is rebooting? If the unassigned switch reboots and becomes again a stack member, do the stack will close connections to servers ?
In my understanding of the stack concept, the remaining active switch would not cause any problem to the production server. And if we want the other switch which has problem to be part again of the stack, no server would have connectivity problem, it's the concept of redundancy of stack....
If the stack was already working at some point and one member goes down, then comes back up at a later time, then it should not impact the other member and it's attached devices. There is a detailed guide on stacking the N4000 series here: https://www.dell.com/learn/us/en/04/shared-content~data-sheets~en/documents~stacking_dell_networking_n4000.pdf. One nice feature offered with stacking is the ability to split your teamed NIC ports across multiple stack members. This way if one stack member goes down the other remains active. Hope this helps!
Yes my 2 switches are already configured this way so the remaining switche is still available for the management. Tonight is the night I will reboot my "not present" switche. Hope it will return in it's "stack" state. Otherwise, I will have to reconfigure it to be again in the stack.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
October 24th, 2018 11:00
Hi,
If it is working right now I would wait until you can schedule downtime. Rebooting the unassigned one should allow it to get assigned a stack number.
851d229
1 Rookie
•
8 Posts
0
October 24th, 2018 12:00
ok I will try this at next downtime.
thank you !
851d229
1 Rookie
•
8 Posts
0
October 26th, 2018 05:00
I have another concern. Is there a risk for the other switch that still operates that this switch could have issues ? For exemple, could this active switch reboot or close connection to production servers during the time the other unassigned switch is rebooting? If the unassigned switch reboots and becomes again a stack member, do the stack will close connections to servers ?
In my understanding of the stack concept, the remaining active switch would not cause any problem to the production server. And if we want the other switch which has problem to be part again of the stack, no server would have connectivity problem, it's the concept of redundancy of stack....
vt1012
212 Posts
0
October 26th, 2018 08:00
851d229
1 Rookie
•
8 Posts
0
October 30th, 2018 14:00
Yes my 2 switches are already configured this way so the remaining switche is still available for the management. Tonight is the night I will reboot my "not present" switche. Hope it will return in it's "stack" state. Otherwise, I will have to reconfigure it to be again in the stack.