If your switches support any of the various STPs, then yes you can implement your second design.
If your switches offer a STP faster than the original, use if for faster convergence.
When setting up STP for your design, you'll normally want one core switch as the primary root and the other as the secondary root. You'll also want to insure one of the each edge switch's uplinks blocks, not the link between the two core switches.
I think it's better for future use, for scalability and for performance you use a layer 3 switch at the network core.
Sure, with 2970 you may use Spanning Tree Protocol, which provides layer 2 redundancy...if you have multiple VLAN you may use also load balancing on links that are running spanning tree (for example tuning the port priorities and so on..).
If you use a layer 3 switch you can configure interVLAN routing and HSRP (redundancy at Layer 3) and you may use Spanning Tree (layer 2 redundancy) too and achieve the redundancy at Layer 3 and Layer 2...example of switch Layer 3 is Catalyst 3560.
It sounds like the way to go is to upgrade the core switches to 3560's perhaps as the 2970 is no longer in production.
STP sounds like the way to go though in our fairly small implementation. At present we have about 15 Edge switches. Would stacking work in my proposed solution? I've never done it and I get the feeling that stacking might complicate things no?
I was just told that manegement wants whatever gives us the most flexibility and uptime regardless of cost.
What would suggest without going over the top? The facility consists of multiple buildings connected via 1 gigabit fiber. The most important is the data center which looks very much like my example above (1.jpg) at present ie. a fairly small room with 1 serverack with 2 switches,a patchrack with 6 edge switches and 1 core swith. Redundancy to the outer edge of the network (other buildings) is not a requirement. All in all there's around 300 connected devices. Not a major site.
What I would suggest is a stack of 3750s, containing two 3750G-12S, for termination of the gig fiber links, and two or more 3750G (10/100/1000) copper switches, either 24 or 48 port, POE or not.
This new stack becomes both your core switch and your server edge. You want to insure there's at least one extra switch of both fiber and copper such that loss of individual switch does not leave you short of ports.
The stack itself will continue to operate if an individual member stack fails.
Insure any dual connected switches, or servers, are not connected to the same physical switch.
For the dual connected edge switches, I believe you can channel two links to the stack. This doubles the available bandwidth and negates the need for STP (although should still be enabled). Again, the channel connections on the 3750s should not attach to the same individual stack member.
You can continue to remain pure L2, or activate L3 within the 3750 stack.
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...