Why is an AP joining a different WLC than the one specified through option 43?
A. The AP is joining a primed WLC
B. The APs broadcast traffic is unable to reach the WLC through Layer 2
C. The AP multicast traffic is unable to reach the WLC through Layer 3
D. The WLC is running a different software version
350-401: Implementing Cisco Enterprise Network Core Technologies (ENCOR)Free dumps for 350-401 in PDF format.High quality 350-401 PDF and software. VALID exam to help you pass. |
 |
Answer – “A” on a 101%
Answer is A:
Priming is joining a previously joined WLC.
If priming and DHCP are not working for the AP, it will do an L3 broadcast.
Source:
https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html#:~:text=on%20document%20conventions.-,Overview%20of%20the%20Wireless%20LAN%20Controller%20(WLC)%20Discovery%20and%20Join%20Process,-In%20a%20Cisco
Why could not be true the “B”?
for what i recall, if it’s a new AP the discovery process starts from L2 broadcast domain, and if no controller are discovered locally the next step is to use DHCP Opt 43 if configured…
If the ap is not new, than the last joined controller win the election
The correct answer is A
…The LAP remembers the management IP address of any controller it joins across reboots. Therefore, if you put the LAP first on the local subnet of the management interface, it will find the controller’s management interface and remember the address.
I think
Answer: A