Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Implementing and Operating Cisco Enterprise Network Core Technologies (ENCOR) · Cisco
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
1st: You resolve the DNS hostname CISCO-CAPWAP-CONTROLLER.localdomain. 2nd: You build the controller list from the resolved IPs, send unicast discovery requests for each controller, and wait for the discovery responses. 3rd: If you receive discovery responses from the controllers, you will send a join request to the primary controller if previously configured. If not, you will resort to the secondary and tertiary if they were previously configured on the AP. If none, you will join the controller that advertised itself as primary in its discovery response https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html#backinfo:~:text=Send%20a%20discovery,number%20of%20APs.
Wireless LAN Controller Election Once the AP has received a Discovery Response from any WLC using any of the WLC discovery methods, it selects one controller to join with this criteria: 1. Primary Controller (Configured with the capwap ap primary-base <wlc-hostname> <wlc-IP-address> command) 2. Secondary Controller (Configured with the capwap ap secondary-base <wlc-hostname> <wlc-IP-address> command) 3. Tertiary Controller (Configured with the capwap ap tertiary-base <wlc-hostname> <wlc-IP-address> command) 4. If no Primary, Secondary or Tertiary WLC were previously configured, then the AP attempts to join the first WLC that responded to the Discovery Request with its own Discovery Response that has the maximum capacity of available APs (that is, the WLC that can support the most APs at a given time). https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axe-access-point/221056-understand-the-ap-join-process-with-the.html#toc-hId--1764447379
It's D. Step 1. The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list.(This includes defaut DNS name of WLC) Step 2. Send a discovery request to every controller on the list and wait for the controller discovery reply Step 3 . send a join request to a controller in this order (only if the AP received a discovery reply from it): Primary Controller system name (previously configured on LAP). Secondary Controller system name (previously configured on LAP). Tertiary Controller system name (previously configured on LAP). Source : https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html#backinfo