In short - when you need more ports than a single switch then you need to add more switches to the stack to add more capacity. If you are new i would recommond to google it and learn more on switch stacking. Do you wanted to be a network tech/engineer ?
All stack members store a copy of the configuration settings. If a stack master becomes unavailable, any stack member assuming the role of stack master will operate from the saved configuration files. Say if you have 2 switches in stack, issue the command - sh flash2: and see - you will have the same config file there too.
Here did you say if I had two switches for example 9200 and I would like to put hem in stack I just need to connect the stack cable and the swtiches automatically formed the stacking? Don't I need to make a previous configuration?
if you are adding a second switch to the existing 9200 switch, the second switch will get the config from the already running 9200. Look at this video and you will understand well. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-hms445UHeOM.html Hope this helps.
Thanks for your great contents. I have a question. Say we add a third switch to our two members switch stack which its mode is "Bundle" and we want to make it as "Install" mode so it can join our "Install" mode stack. Do we have to change its mode individually and before putting the stack cables on and then connect it to the stack or we can add it as is and make a V-mismatch and then console to the new member and change its mode and reload it ? This area is kinda vague to me. Could you please explain? And sorry I have to pose my second question that just sparked in my mind. How about the license mismatch? How do we match them? And why the license has to be the same? Thanks beforehand.
Another question? Are all the files in all the stack members' flashes autogrnarated once the stack is forming? So if we format all switches flashes and only having the .bin Image file, we shouldnt run into any problems right?
hi, yes, u can delete all file but do not delete the (.bin) or (.tar) because it is the OP of it. one suggestion, before to delete all try to backup all file in case of lose. you can do it with TFTP-Server software.
if you are adding a new switch - you don't have to reboot the stack. for example if you are adding a second switch to the stack - set the second switch priority to 14 (assuming your first switch is @ priority 15) and just add it to the stack. no reboot needed. let me know if this is what you are asking?
Hello Network Tutor Nice video.. i'm new on networking, i'm planning to add a new cisco 2960x on existing stacks. The switch i will add is not new. Do i need to reset it to factory default before it to the stack?thanks..
it is better if you reset it to factory default. You need to erase the vlan.dat and write erase. This will make all the old vlans goes away. See this video - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-0W_sOZiMn4o.html
you use #sh run to see the running config of the entire stack and with regards to console access you can console into any switch in the stack. Running config will be copied to all the switch in the stack
If you have a new switch, just power off the stack and add it using the stacking cable. Before add the switch, make sure to set the slot priority. Also when you power up the stack, turn on the master first. But if you have each switch priority set correct, master election happen automatically.** Main think - don't turn on the blank switch first. it will blank all the stack config. by becoming the master switch.Sorry for the late response.
