300-370 · Question #21
An AP will be deployed to an area where DHCP Option 43 is unavailable and the WLAN engineer is unable to have DNS modifications made to support this AP. Which two actions can enable the AP to join…
The correct answer is B. Pre-stage or prime the AP on the same Layer 2 VLAN as the WLC. E. Issue the capwap ap controller ip address WLC IP address command in the AP console. To enable an AP to join a WLC when DHCP Option 43 and DNS modifications are unavailable, you can either pre-stage the AP on the same Layer 2 VLAN as the WLC or manually configure the WLC's IP address on the AP.
Question
An AP will be deployed to an area where DHCP Option 43 is unavailable and the WLAN engineer is unable to have DNS modifications made to support this AP. Which two actions can enable the AP to join the WLC? (Choose two)
Options
- AIssue the clear capwap private-config command in the AP console.
- BPre-stage or prime the AP on the same Layer 2 VLAN as the WLC.
- CIssue the capwap ap ip default-gateway WLC IP address command in the AP console.
- DIssue the capwap ap ip address WLC IP address command in the AP console.
- EIssue the capwap ap controller ip address WLC IP address command in the AP console.
How the community answered
(25 responses)- A4% (1)
- B84% (21)
- C4% (1)
- D8% (2)
Why each option
To enable an AP to join a WLC when DHCP Option 43 and DNS modifications are unavailable, you can either pre-stage the AP on the same Layer 2 VLAN as the WLC or manually configure the WLC's IP address on the AP.
The 'clear capwap private-config' command resets the AP's CAPWAP configuration, which would hinder discovery rather than enable it, especially when automatic methods are already unavailable.
Pre-staging an AP on the same Layer 2 VLAN as the WLC allows it to discover the WLC via Layer 2 CAPWAP discovery, bypassing the need for Option 43 or DNS. This method ensures the AP can find the controller if they are on the same broadcast domain.
The 'capwap ap ip default-gateway' command configures the AP's default gateway, which is essential for network connectivity but does not directly inform the AP of the WLC's IP address.
The 'capwap ap ip address' command configures the AP's own IP address, which is necessary for network communication but does not specify the WLC's IP address for CAPWAP discovery.
Manually configuring the WLC's IP address on the AP using the 'capwap ap controller ip address' command directly tells the AP where its controller is located. This explicit configuration overrides automatic discovery methods and allows the AP to initiate the CAPWAP join process with the specified WLC.
Concept tested: Cisco AP WLC discovery methods
Source: https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-wlc/70308-ap-notjoin-wlc.html
Topics
Community Discussion
No community discussion yet for this question.