ed down Administratively down auto(D) 10 Eth3/11 routed down Administratively down auto(D) 10 Eth3/12 routed down Administratively down auto(D) -- [ - - output truncated --] Chapter 7: Link Aggregation These commands are great, but they come at a price. The show etherchannel commands you may be used to from IOS are not available on NX-OS, at least as of this writing. Cross-Stack EtherChannel Sometimes you can create an EtherChannel across two physical switches. For example, when 3750s are stacked, the stack becomes a single logical entity and each physical switch acts like a blade. Configuring an EtherChannel across two physical switches in the stack is possible, and even recommended to eliminate single physical failure points. Nothing special is required to accomplish this once the stack has been configured- just configure each port to be in the same port-channel group: 3750-I0S(config)#int range g1/0/1 , g2/0/1 5750-I0S(config-if-range)#channel-group 10 mode on Creating a port-channel interface Port-channel 10 Cisco calls this cross-stack EtherChannel, and it has some interesting capabilities and limitations. For example, you can have 16 ports in a cross-stack EtherChannel, with 8 active and 8 in standby. You cannot use PAgP, though, SO your modes are confined to active, passive, and on. Multichassis EtherChannel (MEC) Multichassis EtherChannel (MEC) is very similar to cross-stack EtherChannel in prin- ciple. The difference is that the feature known as MEC is found on the Catalyst 6500 VSS switches. VSS is a clustering technology that allows multiple 6500 chassis to be configured as a single logical switch. This is similar in principle to a 3750 switch stack. For MEC to be possible, VSS must be properly configured and the switches active in the VSS cluster. See Chapter 17 for more information on VSS configuration. Once VSS is running, creating MECs is as easy as it is on 3750s. Here, I've created a 20 Gb MEC between two 6500s clustered with VSS: VSS(config)#int range ten 1/3/2 , ten 2/3/2 vsS(config-if-range)#c