Navi WAC networking is a networking mode that uses a WLAN Access Controller (WAC) to manage

and control APs. It can provide different authentication and security policies for different user

groups, such as employees and guests. Guest data is isolated from the internal network to prevent

security threats.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100064352/9aadccc0/navi-wacnetworking

C is not a tool commonly used for WLAN network planning, acceptance, or health evaluation. eDesk

is a tool for remote fault diagnosis and rectification on WLAN networks.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/wlanplanner

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/imaster-ncecampusinsight

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/cloudcampus-app

The WPA3 transition mode applies to both WPA3-Enterprise and WPA3-Personal. In this mode, WPA3

and WPA2 can coexist for a period of time in the future to enable WPA3-incapable STAs to access a

WPA3-configured network.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/wpa3transition-mode

B and E are not parameters recorded by iMaster NCE-CampusInsight for interference analysis. The

other options are parameters recorded by iMaster NCE-CampusInsight to comprehensively record

and analyze interference.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/interference-analysis

B is false because a static VXLAN tunnel does not use any protocols on the control plane, saving

device resources.

Reference: https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/static-vxlantunnel

In a dual-link HSB scenario, after an AP sets up CAPWAP links with the active and standby WACs, the

AP periodically sends Echo packets to the WACs to detect link status. The Echo packets are sent every

30 seconds by default.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/dual-linkhsb

According to the Huawei documents and resources, the chronological order during the 802.11r fast

roaming process between WACs is as follows:

2.The STA accesses the network through API. This is the initial association process before roaming.

1.The STA initiates an 802.11 FT authentication request to AP2. This is the first step of the roaming

process when the STA moves to a new AP.

3.AP2 starts the reassociation timer, and sends an 802.11 FT authentication response to the ST

A. This is the second step of the roaming process when AP2 responds to the STA’s request and sets a

timer for reassociation.

4.The STA generates and installs a P TK based on the information contained in the response frame.

This is the third step of the roaming process when the STA derives a new pairwise key for encryption.

5.The STA sends a reassociation request to AP2. This is the fourth step of the roaming process when

the STA requests to reassociate with AP2.

6.AP2 generates and installs a PTK according to PMK-RI and information contained in the request

frame. This is the fifth step of the roaming process when AP2 derives the same pairwise key as the

STA.

7.After receiving the reassociation request, AP2 disables the reassociation timer, and then sends a

reassociation reg onse to the STA. This is the sixth step of the roaming process when AP2 confirms

the reassociation with the STA and stops the timer.

8.The STA receives the response frame of AP2. The roaming process is complete. This is the final step

of the roaming process when the STA completes the handover to AP2.

Therefore,

2,

1,

3,

4,

5,

6,

7,

8

is

the

correct

answer.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100169459/8d79210e/configuring-wirelessmesh-networking

According to the Huawei documents and resources, the troubleshooting operations for the AP

onboarding failures are as follows:

APS fail to be authenticated by the WAC: Whitelist the APS. The WAC can authenticate APs based on

their MAC addresses or SNs. If an AP is not whitelisted on the WAC, it cannot be authenticated and

onboarded.

License resources on the WAC are insufficient: Expand the license capacity. The WAC can manage a

limited number of APs based on its license. If the license resources are insufficient, some APs cannot

be onboarded.

APS fail to obtain IP addresses: Check the DHCP server. The APs need to obtain IP addresses from a

DHCP server before they can communicate with the WAC. If the DHCP server is not configured or

reachable, the APs cannot obtain IP addresses and onboard.

APS fail to ping the WAC: Check the network between the WAC and APS. The APs need to ping the

WAC to discover its IP address and establish a CAPWAP tunnel. If there is a network problem

between the WAC and APs, such as incorrect VLAN configuration or firewall blocking, the APs cannot

ping the WAC and onboard.

Therefore, APS fail to be authenticated by the WAC - c, License resources on the WAC are insufficient

- b, APS fail to obtain IP addresses - d, APS fail to ping the WAC - a is the correct answer. Reference: :

https://support.huawei.com/enterprise/en/doc/EDOC1100158948/9a0d5c37/ap-onboardingfailures

Huawei’s CloudCampus Solution supports three user access authentication modes: 802.1X

authentication, MAC address authentication, and Portal authentication.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/useraccess-authentication-modes

Huawei APs can identify non-Wi-Fi devices that operate in the 2.4 GHz frequency band, such as

Bluetooth devices, ZigBee devices, game controllers, wireless video and audio transmitters,

microwave ovens, cordless phones, and baby monitors.

Reference:

https://support.huawei.com/enterprise/en/doc/EDOC1100058940/8a8f1c9b/non-wi-fidevice-identification