Recommended EtherChannel Load-Balancing Mode for Cisco WLCs?

200-301 By islever Editorial Last updated

Configure and verify (Layer 2/Layer 3) EtherChannel (LACP) Describe physical infrastructure connections of WLAN components (AP, WLC, access/trunk ports, and LAG)

Short answer

A Configure the switch EtherChannel load-balancing mode as source-destination IP for links serving Cisco WLCs.

Question

What is the recommended switch load-balancing mode for Cisco WLCs?
  1. source-destination IP address Correct Answer
  2. destination IP address
  3. destination MAC address
  4. source-destination MAC address

Key Takeaways

The question tests which EtherChannel load-balancing hash the switch should use on WLC-facing ports, and the trap is assuming Layer 2 devices must hash only MAC addresses instead of recognizing that modern switches routinely hash Layer 3 fields.

When a Cisco Wireless LAN Controller connects to a switch through an EtherChannel/LAG, the switch must choose a hash mode to spread frames across the bundled links. Cisco's WLC configuration best-practices guidance identifies source-destination IP address as the typically recommended load-balancing option, making A the correct choice.

Common mistake: Option D (source-destination MAC address) is the most common wrong pick, because learners reason that a switch 'only works at Layer 2' and therefore cannot inspect IP headers — but Catalyst switches do support and commonly recommend src-dst-ip hashing on controller links.

Expert Analysis

Why the Answer Is Correct

Cisco's Wireless LAN Controller Configuration Best Practices note lists "source-destination IP" as the typically recommended option for switch-side EtherChannel load balancing toward WLCs. Hashing on both source and destination IP spreads the many distinct client-to-controller flows across all bundle members, because each client typically has its own IP while the controller keeps a stable IP, producing a well-distributed hash. This keeps all frames of a given flow on one link, preserving order for tunneled controller traffic while still balancing aggregate load. Options such as source-destination IP are supported precisely because Catalyst switches can parse Layer 3 headers in hardware, so the premise that a switch cannot read IP addresses is incorrect.

Why the Other Options Are Wrong

Option D (source-destination MAC address) hashes on client and controller MAC addresses; since a WLC is typically reached through one or a small number of MAC identities, the resulting hash distribution is far less even than IP-based hashing across many clients, which is why it is not the recommended default. Option B (destination IP only) and option C (destination MAC only) each look at a single field, so all traffic headed to the controller's one address funnels into a subset of links, defeating the purpose of the bundle. Neither single-field mode accounts for the many client-side sources, so utilization stays uneven. Option C also ignores Layer 3 diversity entirely.

Community Comment Notes

Commenters were split, but the strongest evidence points to A: dropspablo quoted the official best-practices text naming "source-destination IP" as "the typically recommended option," and Tompoo concurred that "Cisco recommends source-destination IP (src-dst-ip)" because the switch makes the hashing decision. shaney67 and JulesAZ argued for D or a situational answer, and matass_md admitted getting "them mixed" before switching positions, illustrating the classic Layer 2 hashing misconception. mageknight's top-voted comment also confirms source-destination IP, noting it keeps all traffic for a specific client-WLC pair on the same physical link.

Official Reference

https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-6/b_Cisco_Wireless_LAN_Controller_Configuration_Best_Practices.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

On CCNA EtherChannel questions, remember that Catalyst switches offer src-dst-ip, src-ip, dst-ip, src-dst-mac and similar modes, and that Cisco recommends src-dst-ip for WLC and server-facing bundles. If an option offers both source and destination of a richer header field, it usually beats a single-field or MAC-only mode.

Frequently Asked Questions

Why isn't source-destination MAC the right choice if switches work at Layer 2?

Catalyst switches can hash Layer 3 fields in hardware, and Cisco's WLC best-practices note recommends source-destination IP for more even distribution across many clients.

Does load-balancing mode affect traffic order on a WLC EtherChannel?

Hashing on source-destination IP keeps each client-to-controller flow on one link, preserving frame order while balancing aggregate traffic across the bundle.

More 200-301 FAQ →

Discussion 10 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 10

  1. mageknight 👍 20
    When using EtherChannel with Cisco WLCs, the recommended load-balancing mode is the source-destination IP address mode. This mode distributes traffic based on the source and destination IP addresses, which ensures that all traffic between a specific client and the WLC is sent over the same physical link. This is important for maintaining client connectivity and optimizing network performance, as it helps to minimize latency, packet loss, and other network issues.
  2. dropspablo 👍 6
    Answer correct : https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-6/b_Cisco_Wireless_LAN_Controller_Configuration_Best_Practices.html#:~:text=%E2%80%9Csource%2Ddestination%20IP%E2%80%9D%20as%20the%20typically%20recommended%20option
  3. shaney67 👍 5
    D. source-destination MAC address Explanation: For Cisco Wireless LAN Controllers (WLCs), the recommended switch load-balancing mode is typically the "source-destination MAC address" mode. This mode considers both the source MAC address (the client device) and the destination MAC address (the access point) to make load-balancing decisions. This helps distribute client traffic across access points while maintaining session continuity for individual client devices.
  4. matass_md 👍 2
    sorry D , D source-destionation MAC , got them mixed
  5. Fakecon 👍 2 Answered D
    Other choices don't make sense
Show 5 more comments
  1. matass_md 👍 1
    Switches act at Layer 2 , there is a hashing algorithm that can read IP addresses but that's way to complex. Stick with the basics SW = Layer 2 Router = Layer 3 . Right answer is A , I know this because what you wrote chatGPT gave me the exact same answer , and after asking about layer 2 and layer 3 chatGPT rectified the answer and told that source and destination MAC address is right , it got confused . VOTE for A , think for yourself !
  2. Tompoo 👍 1 Answered A
    Cisco recommends source-destination IP (src-dst-ip) as the switch EtherChannel load-balancing method for WLC connections. The WLC relies on the connected switch to make the load-balancing decision for traffic entering the controller
  3. JulesAZ 👍 1 Answered D
    from my research could be A or D dependent on specific network requirements. would welcome any well referenced answer to the contrary
  4. 7a136f6 👍 1 Answered D
    d. if machines shared a ip for any reason, then we would get the opposite of load balancing (not a)
  5. g0dofnub 👍 1 Answered A
    A IS CORRECT

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Rapid PVST+ Port State That Neither Receives BPDUs nor Learns MAC

S-grade

Computing the EUI-64 Interface ID for a Given MAC Address

S-grade

Electing the Root Bridge in PVST+ by Priority and MAC

S-grade

How a Switch Handles an ARP Request for an Unknown Destination

S-grade

Practice All 200-301 Questions

Access 220 questions with complete answers and detailed explanations.

View Full 200-301 Practice Test →

← Back to 200-301 Study Guide