gbksphere
asked on
Help on adding a 3rd Cisco Switch
I'm certainly not a savy Cisco network guy. My objective is to add a third Cisco switch to my current setup. I would appreciate it if I can get some directions on how to connect and configure the new switch and make all three working dandy. :). If connected correctly, the third switch can join the stack with minimal configurations, correct? After it's joined, does the new switch inherits all the VLAN stuff too?
SWC1: C3560G
SWC2: C2960S
SWC3: C2960S
Currently SWC1 and SWC2 connection:
SWC1 port 5 <---> SWC2 port 1
Please shed some light on what's the best approach I should take. Thank you in advance.
SWC1: C3560G
SWC2: C2960S
SWC3: C2960S
Currently SWC1 and SWC2 connection:
SWC1 port 5 <---> SWC2 port 1
Please shed some light on what's the best approach I should take. Thank you in advance.
ASKER
Thanks for reply. You are correct though, I'm very limited on networking knowledge. LOL. In this case, there's no specialized stack or via stack cables at all. Sry for using the term incorrectly. I only have 2 switches connected to each other and I'm trying to add 1 more switch for more devices.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Awesome. Thanks for the assistance.
In the Cisco world, a stack is a group of switches connected by a specialized stack cable on the backside of the switches. From there the switches act as if they were one large switch with a single configuration, spanning-tree instance, etc.
Other manufacturers define a stack as a group of switches that have a single point of configuration even if they are all operating independently and physically separated.
A less technical definition of a stack is just the logical idea of 2 or more switches connected together, usually physically stacked on top of one another.
Once we know how you are planning to connect the new switch, we can tell you how it's done.
I do apologize if it sounds like I'm trying to point out a possible lack of networking knowledge, but the configuration and considerations vary greatly depending on how it's really being connected, and we don't like pointing people in the wrong direction if we can avoid it.