Best Switch Configuration Recommendations
Posted on 2008-10-10
It's time to upgrade our switches at our main site and rethink the layout. We are currently on a 255.255.252.000 subnet and everything is on the single default VLAN. There are about 375 computers/printers on this subnet which includes a site that is connected to us via a 100mb metroE type connection, the number of devices are pretty much equal at each site. We will eventually be splitting the connected site onto it's own subnet.
Currently we primarly use 3com layer 2 switches (3com 3870 and 2948 all Gigabit - have had alot of lockup problems with the 2948's for some reason tried with STP enable and dissabled don't know if the 2948's are just problematic for this type of setup or not, the 3870's seem to always work good) and were looking at the 3com 5500's and the Cisco 3750's as possibilities since they seem to be similar except for the price.
All our servers (about 50 servers) and internet connection are located at our main site which is where we are wanting to upgrade the switches.
What would your recommendations be to reconfigure the backbone as nice as possible/best practice? For example, just throw in enough 5500's/3750's to cover the ports or should there be a different core switch and hang a different type of switches off the core, and what is the best practice way to connect the switches, if direct daisy chaining is ok or if everything should be run through an external fiber patch panel etc.
Maybe "We have this setup" kind of examples. Looking for something that will be very stable and ready to growth, if you would choose Cisco over 3com, 3com over Cisco etc.
Those 2948's are going to give me ulcers :) We have about 10 of them around the company, even at different sites, and over half had have the lockup problem needing a power cycle to get them going again. No pinging the switch from outside, no pinging hosts when plugged in on the same switch etc. The only thing we could do is get an RMA from 3com. This happened with the default base firmware and the current firmware.
We will also need to start getting VLan's setup to split out the servers, IP phones and a wireless network which is not implemented yet.