HCIA-WLAN common mistakes
HCIA-WLAN · Understand the traps and how to avoid them.
Confusing the roles of CAPWAP control and data tunnels, and assuming that all client data traffic must pass through the AC.
Candidates memorize that CAPWAP has two tunnels but do not learn that in direct forwarding mode the data tunnel carries only management traffic, while service data is bridged locally at the AP; they also mix up UDP ports 5246 and 5247.
What to do instead
Draw the CAPWAP encapsulation: control tunnel UDP 5246 (DTLS optional), data tunnel UDP 5247. For each forwarding mode (tunnel/集中转发 vs direct/本地转发), write which tunnel carries user traffic and where the AP management VLAN terminates. Practice identifying the mode from a described topology.
Mixing up 802.11 frame subtypes and their ACK/coordination rules, for example expecting an ACK for every data frame or treating RTS/CTS as mandatory.
Study focuses on frame names without linking them to the access method: broadcast/multicast frames and frames with the No-ACK policy are not acknowledged, and RTS/CTS is optional and used mainly to mitigate hidden nodes.
What to do instead
Build a table of management, control, and data subtypes with their purpose and whether they are acknowledged. For each, note the coordination function (DCF/EDCA) and the conditions that trigger RTS/CTS. Answer practice items by first naming the frame class, then the rule.
Treating WPA2-PSK and WPA2-802.1X (enterprise) as interchangeable and selecting the wrong authentication method for a described scenario.
Candidates learn the four-way handshake but not the difference in key hierarchy: PSK derives the PMK from the passphrase, while 802.1X derives it from EAP exchange with a RADIUS server. They also forget that WPA3-SAE replaces PSK's offline dictionary exposure.
What to do instead
Map each security mode to its credential source, PMK origin, and handshake. For scenario questions, extract the clue (pre-shared key vs RADIUS/EAP, personal vs enterprise, SAE vs PSK) before choosing. Review 802.11i/RSN terminology and the role of the 4-way handshake in both modes.
Misidentifying Huawei AP/AC model families and their capacity or role, such as assuming any Huawei AP can run in leader/standalone mode or that an AC6005 supports the same AP count as an AC6605.
Model numbers are memorized without the product-line logic: AP series differ by Wi-Fi generation, radio count, and indoor/outdoor use; AC models differ by managed AP capacity, port count, and whether they are fixed or modular. Candidates also confuse fat AP, fit AP, and cloud-managed modes.
What to do instead
Create a comparison sheet for the AP series and AC models you are likely to see, listing Wi-Fi standard, number of radios, maximum managed APs, and typical deployment. For each model, note supported working modes. Practice matching a described site (AP count, throughput, indoor/outdoor) to a model.
Ignoring PoE power budget and power-sourcing standards when selecting APs and switches, leading to answers that pair an AP with a switch that cannot power it.
Candidates focus on wireless throughput and forget that AP power draw depends on radio count and features, and that 802.3af/at/bt supply different wattages. They also overlook that some APs need an external power adapter or a higher-class PSE.
What to do instead
For each AP model, record its typical and maximum power consumption and required PoE class. Compare with the PSE budget per port and total switch budget. In scenario questions, calculate total AP load against the switch PoE budget before choosing hardware.
Assuming an AP will automatically become fit and register with the AC without configuring the AC's IP address or the correct discovery method.
Candidates learn that APs are plug-and-play but skip the discovery sequence (DHCP Option 43, DNS, broadcast, static AC address). They also forget that the AP and AC must have IP reachability and that NAT between them breaks CAPWAP.
What to do instead
Memorize the AP discovery order and the configuration points: DHCP server Option 43 carrying the AC IP, AC source interface, and CAPWAP reachability. Practice writing the minimal configuration for a new AP to register, then verify with display commands.
Configuring a VAP/profile but forgetting to bind it to the AP group or radio, then wondering why the SSID does not appear.
Huawei WLAN configuration is profile-based: regulatory domain, AP group, VAP profile, SSID profile, and security profile must all be linked in the right order. Candidates omit the ap-group binding or the vap-profile reference inside the AP group.
What to do instead
Use a checklist for every SSID deployment: create SSID profile, security profile, VAP profile; reference VAP profile in the AP group; bind AP to the group; set the regulatory domain and radio. After each step, name the command that verifies the binding.
Choosing tunnel forwarding versus direct forwarding without considering the AC's location and the service VLAN design, resulting in a topology that cannot work as described.
Candidates memorize the two modes but not the consequences: tunnel mode requires the AC to handle user traffic and the AP-AC path to carry service VLANs, while direct mode requires the service VLAN on the access switch and the AP to tag frames.
What to do instead
For each mode, draw the VLAN path and the device that terminates the service VLAN. Note where DHCP runs and where the gateway sits. In scenario questions, decide the mode from the AC's position (central vs branch) and the requirement for local breakout.
Reading display station output but not knowing which field proves the failure stage, such as jumping to RF conclusions when the station never completed association or authentication.
Troubleshooting questions present a symptom (client cannot connect) and candidates skip the layered sequence: AP registration, SSID advertisement, association, authentication, DHCP, and data forwarding. They also ignore CAPWAP tunnel state and AC-AP reachability.
What to do instead
Follow a fixed order: check AP registration on the AC, then VAP/SSID state, then station association and authentication state, then DHCP address assignment, then forwarding. For each stage, name the display command and the field that confirms success or failure.
Blaming the wireless network for all poor performance instead of checking co-channel interference, channel width, and non-Wi-Fi interference using the available tools.
Candidates treat low throughput as an AP fault and skip RF analysis: overlapping channels, 40/80 MHz width in dense areas, and interference sources explain many cases. They also forget that airtime is shared and that legacy clients slow the cell.
What to do instead
Practice a structured RF check: survey the channel plan for 2.4 GHz (1/6/11) and 5 GHz, verify width and power settings, and use spectrum/air interface statistics to distinguish co-channel from non-Wi-Fi interference. Match each finding to a configuration change.