A port channel is an aggregation of multiple physical interfaces that create a logical interface. You can bundle up to 8 individual active links into a port channel to provide increased bandwidth and redundancy. If a member port within a port channel fails, the traffic previously carried over the failed link switches to the remaining member ports within the port channel.
On the Nexus 7Ks, port channeling also load-balances traffic on the M series module and across these physical interfaces The port channel stays operational as long as at least one physical interface within the port channel is operational.
Starting with the Cisco NX-OS Release 5.1, you can bundle up to 16 active links into a port channel on the F-series module with a Nexus 7K.
NOTE: You cannot configure a shared interface to be part of a port channel.
Like many later Cisco devices, the Nexus devices do not support PAgP, and instead, offer LACP for a dynamic protocol to assist with port channel creation.
Each port can be in only one port channel. All the ports in a port channel must be compatible; they must use the same speed and duplex mode.
You can create port channels directly by creating the port-channel interface, or you can create a channel group that acts to aggregate individual ports into a bundle. When you associate an interface with a channel group, the software creates a matching port channel automatically if the port channel does not already exist. In this instance, the port channel assumes the Layer 2 or Layer 3 configuration of the first interface.
You can also create the port channel first. In this instance, the Cisco NX-OS software creates an empty channel group with the same channel number as the port channel and takes the default Layer 2 or Layer 3 configuration, as well as the compatibility configuration.
Your port channel is operationally up when at least one of the member ports is up and that port’s status is channeling. The port channel is operationally down when all member ports are operationally down.
NOTE: You can create a Layer 2 port channel by bundling compatible Layer 2 interfaces, or you can create Layer 3 port channels by bundling compatible Layer 3 interfaces. After you create a Layer 3 port channel, you can add an IP address to the port-channel interface and create subinterfaces on the Layer 3 port channel. Of course, you cannot combine Layer 2 and Layer 3 interfaces in the same port channel. You can also change the port channel from Layer 3 to Layer 2.
Also as you would expect, all ports in the port channel must be in the same virtual device context (VDC).
Any configuration changes that you apply to the port channel are applied to each member interface of that port channel. For example, if you configure Spanning Tree Protocol (STP) parameters on the port channel, the Cisco NX-OS software applies those parameters to each interface in the port channel.
After a Layer 2 port becomes part of a port channel, all switchport configurations must be done on the port channel; you can no longer apply switchport configurations to individual port-channel members. You cannot apply Layer 3 configurations to an individual port-channel member either; you must apply the configuration to the entire port channel.
You can create subinterfaces on a Layer 3 port channel, even though a subinterface is part of the logical port-channel interface.
You can configure Layer 2 port channels in either access or trunk mode. Layer 3 port-channel interfaces have routed ports as channel members and might have subinterfaces.
From Cisco NX-OS Release 4.2(1), you can configure a Layer 3 port channel with a static MAC address. If you do not configure this value, the Layer 3 port channel uses the router MAC of the first channel member to come up.
One thought on “CCIE DC Written – 1.1.a Link Aggregation – Overview”
Hi Anthony, I’m running into a situation kind of similar to what you’re explaining up top. The big difference is that I work for a small company and we pretty much have one IBM bladecenter, where I have four separate cables coming off the back that my server guys are telling me they’ve team together using Microsoft teaming and any one of their servers can use any one of those ports, with any VLAN they’ve configured for those ports. I’ve trunked all four of those ports to my double stacked 9300s, so it goes Port 1 and 2 on the back of the server go to Ports 1/1/1 & 1/1/2 on my top 9300, and ports 3 and 4 on the server go to Port 2/1/1 & 2/1/2 on the bottom 9300. The dilemma that I have, is sort of along the same lines of what you’re saying above. I want to treat all four of those interfaces as one layer 2 LACP bundle or Lag. Problem is, as soon as I create the bundle they lose connectivity to some of the NICs. I’m not sure exactly how to get those 4 interfaces teamed together in one layer 2 LACP bundle. I don’t know the Microsoft environment or the VMware environment he’s using well enough to be able to tell my server guys, “you need to set LACP on your 4 NICs that you’re using Microsoft teaming on. Is there any other way that you know of that I could possibly bundle these for connections together in order for him to have an active-active connection across all four of those with his Microsoft teaming working? And without causing A TON of Mac flapping? Thanks for any help you can provide.