I am afraid that stacking does not allow you to increase the number of ports in a single channel. According to the Configuration Guide for 3750 series, even with stacked switches, an EtherChannel may contain only up to 8 active links (with LACP, there can be at most 8 active and 8 standby links in a single group, a total of 16 ports but only 8 of them are carrying data). These are both hardware limitations and limitations of the EtherChannel management protocols (LACP and PAgP).
In my opinion, needing more than 8 links in a single EtherChannel is worth considering whether a different link layer technology may be better suited to cope with your bandwidth requirements. For example, instead of combining 9 or more GigE ports into a single EtherChannel, why not consider moving to 10GigE?
Stacking itself allows you to make several switches behave as a single, compact unit, operating over a single, shared MAC address table, sharing the control plane, and performing inter-switch communication over a dedicated, high-speed interface (the StackWise interconnect). For all purposes, the switch stack behaves as a single switch, ranging from configuration in a single please (a single configuration file controls all switches in the stack), behaving as a simple bridge in STP, EtherChannel, inter-VLAN routing and so on...
The switch stack combined with EtherChannel allows you to spread the ports among several physical switches in a single stack. Even though the ports are on different stacked switches, to the opposite party, they appear as if they were located on a single switch. In addition, if a particular switch in a stack goes down, the remaining switch will continue transporting data and the EtherChannel will still work (although in a reduced throughput until the first switch comes back up and adds the ports back to the EtherChannel).
>> I want to know why stacking is recommended as a solution.
for better resiliency and fault tolerance by taking member links of the bundle from different member switches of the stack you can ensure that no single device or single link failure event will make the bundle totally not operational.
The surviving switches have to keep using the same LACP system id even in case the failed switch had the master role. If so there is consistency and the LAG can survive to any single device or link failure.
if you put all the LAG links in a single device the bundle will be down if that device fails
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...