An enterprise uses WAC+FITAP networking, and users find that the AP fails to go online. The cause of this failure may be that the AP and WAC software versions do not match.

Question

Options

• ATrue
• BFalse

• A
  78% (42)
• B
  22% (12)

Explanation

Option A is correct because in WAC+FITAP (Wireless Access Controller + Fit AP) architecture, the Fit AP is a "thin" device that relies entirely on the WAC for configuration and management via the CAPWAP protocol. If the AP's firmware version is incompatible with the WAC's software version, the CAPWAP tunnel negotiation can fail, preventing the AP from registering and going online. Version mismatches are one of the standard troubleshooting checkpoints when APs fail to associate with a controller in enterprise WLAN deployments.

Option B is incorrect because it dismisses a well-documented compatibility requirement - Huawei (and similar vendors) explicitly require matching or compatible software versions between the WAC and its managed APs for successful operation.

Memory tip: Think of WAC+FITAP like a manager and employee who must "speak the same language" - if the AP and controller run different software versions, they literally cannot communicate properly to establish the management tunnel. Always verify version compatibility first when an AP won't come online.

No community discussion yet for this question.