We currently have 2 x 3550 t Switches as our core and layer 3 switches.
The stacks are a mixture of 3560's and 2950's linked via sfp + fibre cables. The main core switch is the main for hsrp and the 2nd core switch is the backup. We have costed the backup ports on each stack switch and also the redundant switch so that the main route is always preferred.
My boss has said that he thinks we should have our larger stacks of 3560/2950 switches split their traffic across our 2 core switches by changing the spanning tree costs for these backup ports making them more attractive. He wants this as he says it does not utilise our other switch. Which is true.
ie have the top 2 switches send packets up to the main core switch and the bottom switches send packets to the backup switch. This would mean re-costing all the spanning tree as the backup hsrp switch has costings on each port of 5000 so that it is never the preferred option unless the primary fails.
Maybe we should be using a load balancing method instead of HSRP?
Now I don't really see any benefit in doing this only to create more work and confusion within the network.
We also have a flat network and I have started to create new vlan's for dmz's and remote sites but I would think that we should be creating vlan's for our servers etc, the servers plug into various ports on one of the stacks and I would think that our app servers should be plugged into the core but that is full with our stack connections?
Please take a look at our diagram and let me know your thoughts on our design and improvements we could make.