Over the past few years I have seen many comments in the blogosphere questioning the reliability of the Catalyst 3750 platform. I believe Ethan Banks (@ecbanks) has posted on this in the past and more recently Aaron Conaway (@aconaway). I thought I’d post my experiences over the past 4-5 years managing ~40x 3750 switch stacks composed of 2-5 switches without a single stack failure in production operation (we did have one stack member die due to lightning strike and the rest of the stack continued to function).
I will qualify that all of these stacks are in a relatively static physical installations but many of them have been subjected to temperature ranges of 22C to 30C (72f – 86f for the American folk). They aren’t configured with any advanced features, only routing/switching/access-lists and weren’t running bleeding edge IOS (mostly c3750-i5-mz.122-20.SE). Most of these stacks were at the edge delivering Ethernet services in a residential environment and not in the core or data center.
I will also add that I think both Ethan and Aaron are awesome engineers that I respect greatly and I’m and avid reader of their blogs, my experience with the 3750 just hasn’t been the same as they have described. Perhaps some of my anally retentive practices in deploying these switches has minimised the occurrence of failure.
PUT THE STACK CABLES IN PROPERLY
The stack cable is heavy with quite a relatively shallow connector; you should install this in the same way you would change a tire. I seat the connector and hand screw the cable in until it is firm and then use a flat head screwdriver a few turns on each side at a time until the cable is fully screwed in.
When provisioning a new stack I always screw all the stack cables in first and then power on the switches.
SYNCHRONISE YOUR IOS
Install the same IOS on a new stack member as the rest of the stack before installing using the archive command.
Switch#archive download-sw tftp://x.x.x.x/c3750-i5-mz.122-20.SE.tar
PROVISION NEW SWITCHES BEFORE HAND
Provision new switches on the stack before installing. I also configure the new switch with the appropriate switch number.
Switch(conf)#switch x renumber y
RIG THE ELECTION
Use the switch x priority command to rig the election on all switches. Highest priority wins the stack election.
I usually want switch 1 to be the master so give it a priority of 15 descending that number with each subsequent switch
Switch(conf)#switch 1 priority 15
Manually drop the config of the switch onto new stack members before adding them too the stack. I know you don’t technically have to do this I just like removing all chances of error.
I think 3750’s are a great switch which in my experience have been rock solid performers. I would recommend them on the edge of anyone’s network, the ability to grow capacity as needed and distributed fault tolerance are big pluses. Would I use them in a data center? Probably not. I would also suggest that if you required a stack size of 4-5 switches off the bat then a 4500 would probably be a better option for cost vs features/performance.