We have a 6 switch stack that is split between two cabinets, switches 1-3 in the left cabinet, 4-6 in the right. We need to add a new switch to each cabinet. I am confident adding a switch to the bottom of a stack and know the do's and dont's but adding a switch in the middle I am unsure. Would this work?
The above shouldn't cause any downtime and can be done in preparation. Then
Is this the correct way of doing it? If it is do I have to wait for each new switch to load fully before adding the next one?
The current stack looks like this
* 1 56 WS-C3850-48P 03.06.05E cat3k_caa-universalk9 INSTALL
2 56 WS-C3850-48P 03.06.05E cat3k_caa-universalk9 INSTALL
3 56 WS-C3850-48P 03.06.05E cat3k_caa-universalk9 INSTALL
4 56 WS-C3850-48P 03.06.05E cat3k_caa-universalk9 INSTALL
5 56 WS-C3850-48P 03.06.05E cat3k_caa-universalk9 INSTALL
6 56 WS-C3850-48P 03.06.05E cat3k_caa-universalk9 INSTALL
We will be updating the software to 03.07.05E
Got to ask why not just add it to the bottom of the stack?
Must be missing something - the switches are connected via stackwise cables correct?
Sorry I still dont understand why you cannot just add the switch to the bottom of the current stack, Surely it wouldn't matter if the switch was in the middle or on the end as far for any cable run would it?
What we want to avoid having is network cables start being strung across between cabinets. There are just over 600 ports in the comms room, so each cab has slightly more than 300 ports in its patch panels. As much as we can we want to have a port patch from one cab going to a switch in the same cabinet, running up to 96 cables between the two cabinets soon becomes a mess.
make sure the new switch has the same software version running as the existing stack members and clear the config
the process is very simple, the stack with stackwise cables forms a ring, you can split the ring anywhere as long as the other path remains available. and so, you can add a new stack member anywhere in the ring
and if you add two new members you need to do the physical connection one-by-one to keep one path of the ring available
When the new members config is empty it wil automatically get the next free member-number on power-on
so the stack numbering may end up as 1-2-3-7-4-5-6-8,
until you use the "switch <x> renumber <y>" command (for all members) and do a reload !!!
your procedure would change a little