vailable on Fast Ethernet at the time. The technology is also called Gigabit EtherChannel (GEC), or more generically, just Port Channel. The non-Cisco term used for link aggregation is generally Link Aggre- gation, or LAG for short. With EtherChannel, the single logical link's speed is equal to the aggregate of the speeds of all the physical links used. For example, if you were to create an EtherChannel out of four 100 Mbps Ethernet links, the EtherChannel would have a speed of 400 Mbps. This sounds great, and it is, but the idea is not without problems. For one thing, the increased capacity is not truly the aggregate of the physical link speeds in all situations. For example, on an EtherChannel composed of four 1 Gbps links, each conversation will still be limited to 1 Gbps by default. The default behavior is to assign one of the physical links to each packet that traverses the EtherChannel, based on the packet's destination MAC address. This means that if one workstation talks to one server over an EtherChannel, only one of the physical links will be used. In fact, all of the traffic destined for that server will traverse a single physical link in the EtherChannel. This means that a single user will only ever get 1 Gbps from the EtherChannel at a time. This behavior can be changed to send each packet over a different physical link, but as you'll see, there are limits to how well this works for applications like VoIP. The benefit arises when there are multiple destinations, which can each use a different path. EtherChannels are referenced by different names in NX-OS, IOS, and CatOS. As Fig- ure 7-1 shows, on a switch running CatOS, an EtherChannel is called a channel, while on a switch running IOS or NX-OS, an EtherChannel is called a port channel inter- face. The command to configure an EtherChannel on CatOS is set port channel, and the commands to view channels include show port channel and show channel. IOS switch Cat0S switch Port channel interface EtherChannel Channel Po0, Po1, etc. Figure 7-1. EtherChannel