I have (4) separate 3750 switches, (3) are 24 port and a single 48 port. I was thinking of consolidating them into a single stack. I have read some of the white papers so I understand the process, but other than getting the IOS on the same version, is there any special considerations I need to make? Is there a problem with having one with 48 ports and the rest 24? Any reason I wouldn't want to stack them?
Cat3750s no matter their port density are meant to be stacked. You are right as the most common problems come from IOS or feature set mismatches but as long as having a single management unit with no severe performance issues, having a stack is a real relief when configuring.
I am sure you read this doc but it basically tells all you need to know about stacking 3750s
"Is there a problem with having one with 48 ports and the rest 24?"
Any 3750 series can be stacked together (you can also mix 3750 series with 3750-E series in same stack).
There are SDM templates (additions) that are unique to just one model, the 12 port SFP 3750 (as also noted by another poster).
"Any reason I wouldn't want to stack them?"
Biggest issue with stack, when you want to upgrade you need to bounce the stack. If you have separate units, with redundant paths, you might cause less network interruption. This isn't usually an issue if you can schedule network maintenance down time.
Another issue, stack ring can be a bottleneck. More of an issue with 3750 stackwise (vs. 3750-E stackwise+) and as stack size increases (max 9 units). If this is a concern, you're probably need to consider the 3750-E series and/or a chassis that provides a true fabric between blades (e.g. 4500, 6500).
You do want to use the same IOS version on all stack members (as noted in another post), however they will work with different feature sets.
"And lastly, when I create the stack, will the orginal configuration on teh ports remain intact? For example my vlan configuration and port setting?"
There are special considerations merging existing configured 3750s since the stack becomes one virtual switch (runs one config). I.e., believe some member switch configuration information could be lost, and pre-existing configurations might impede stack merge (as also noted by another poster).
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...