I don't think you're going to see any website with direct step-by-step instructions on how to do this. There maybe a few blogs which speak to a blogger's personal experience....however, this is how I would approach it.
I'm going to assume that your current 3560Gs have L3 links to the core and an L2 link (or portchannel) between the two switches. I will also assume that you're using interface tracking to help swap HSRP states and pre-emption and etc...
While you are adding the 3750X to the original 3560G switches. All you would require is to extend the L2 link to the 3750X stack. You can pre-provision the 2nd 3750X and even have it running and connected when you do this entire process.
Then move the L3 uplinks from the standby 3560G to the first 3750X and ensure that HSRP is configured in order to facilitate the failover.
Once that is done...begin migrating your cabling/device cable to the 3750X stack.
Then move the final 3560G L3 link to the 2nd 3750X switch. You should now also be able to remove the L2 link between the 3750'ss and 2560's and power them off.
Since you're using HSRP - the 3750X's should become active under your control (via a priority change)
Finally, after you are left with just the 3750X in a stack-formation. You will no longer require HSRP to run between the two switches since the 3750X will really be seen as one switch all together.
Ultimately, the end solution should have 2x L3 uplinks to your core or router, and the VLAN interface existing solely on the 3750X stack. I would also have the each of the L3 links attached to the separate 3750X switches as well.
This final solution should give you a more robust design from preventing spanning tree and HSRP timers from delaying your network re-convergence and allowing the routing protocol to do the upstream path selection instead of HSRP.
We have been using 2 Cisco 2960-S 48 Port switches which were connected together using a regular Cat5e cable and everything was working fine, however we have purchased a 3rd switch of the same model and need to connect it to the other switches.
What would be the best way to connect all 3 switches?
Generally, you connect all three switches in a "triangle". There is no problem with this configuration as long as you have some version of spanning-tree running.
I'm not sure what state your network is in right now, so I'm assuming you might not have spanning-tree running, and you have not connected the third switch. Generic steps to introduce the new switch:
- Make sure the third switch is disconnected. Configure
spanning-tree mode rapid-pvst
on all switches.
- Configure
spanning-tree vlan 1-4094 priority 4096
on the switch closest to your Internet / WAN connection
- Configure
spanning-tree vlan 1-4094 priority 8192
on the other (running) switch
- Configure
spanning-tree portfast disable
on all ports connecting to the other switches.
I gave you a very basic recipe to make this work... depending on the bandwidth needs of the clients, you might want to bundle multiple links between these switches with LACP or EtherChannel.
Best Answer
Look at this link and scroll about half way down.
http://forums.networkinfrastructure.info/nortel-ethernet-switching/ers-8300-and-lacp-with-hp-blade-servers/
UPDATE: Fixed - Here's how you get LACP to work with the 8300.
The configuration is simple, for a base line.
Configure your ports and vlans as you would normally (for multiple vlans enable tagging on the port level)