nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

interfaces, where any given flow always hashes to the same physical interface. A common
misconception about port-channels is that the logical interface is a 20/40/80-Gbps link. For
10-Gbps member links, however, no single flow would exceed the transmission speed of the
physical links that are members. An analogy here would be that port-channels add new lanes
to the highway but do not increase the speed limit. A port-channel can be configured as
either a Layer 2 or Layer 3 link depending on the requirements.
The hashing used to load balance traffic across the links is user-configurable, and the
following options are available on the Nexus 7000:
• Source IP
• Destination IP
• Source MAC
• Destination MAC
• Source port
• Destination port
• Source and destination IP
• Source and destination MAC
• Source and destination port
You can configure these options globally or, because of the distributed nature of the Nexus
7000, on a linecard-by-linecard basis. If VDCs are used, these parameters are defined in the
default VDC.
Example 2-62 shows how to configure and verify the load-balancing algorithm.
Example 2-62. Port-Channel Load-Balancing Algorithm
Click here to view code image
Congo(config)# port-channel load-balance ethernet sourcedest-ip-vlan
Congo(config)# show port-channel load-balance
Port Channel Load-Balancing Configuration:
System: source-dest-ip-vlan
Port Channel Load-Balancing Addresses Used Per-Protocol:
Non-IP: source-dest-mac
IP: source-dest-ip-vlan
Assigning Physical Ports to a Port-Channel
Two options exist for assigning members to the logical interface:
• Configure member links to run the industry-standard 802.3ad Link Aggregation
Control Protocol (LACP).
• Statically configure the port as a member of the port-channel. This mode is on, and no