The stacked switches act as one logical switch, meaning that you can use any port on any switch in the stack as a LAG member. The N-series support aggregating up to 8 ports. With a stack you will typically spread the LAG across multiple switches. This creates a scenario where you have some switch redundancy and link redundancy.  Example of the config would look similar to this: console(config)# interface gigabitethernet 1/0/1 console(config-if)# channel-group 1 mode active console(config-if)# exit console(config)# interface gigabitethernet 2/0/1 console(config-if)# channel-group 1 mode active console(config-if)# exit console(config)# interface port-channel 1 console(config-if)# switchport mode trunk
Hello All, We are replacing our Powerconnect switches with N2048 for the Access Layer and (2)  N4032 at the core.  I have never used stacking in the past and was hope to manage the members as one.  Would it be possible to  stack the Access switches and also LAG them to the core for redundancy?  The core could be stacked as well, but I'm reading that MLAG is faster for failover. Should I have a problem with this config?    Thanks for any advice. Charles
MLAG CORE + ACCESS STACK