A Cisco WLC v7.0 is not seeing an AP join. Which starting prefix debug command can help determine a combination of discovery/join and DHCP process status?

`debug capwap events` on the Cisco WLC provides controller-side CAPWAP details but will not show the AP's DHCP process or its perspective of discovery if it cannot reach the controller.

`debug capwap events` on the AP shows CAPWAP-specific events, but it may not provide the granular DHCP message details needed to troubleshoot IP address acquisition issues.

`debug ip udp` on the Cisco WLC would show UDP traffic reaching the controller, but it cannot reveal the AP's DHCP process if the AP is not successfully sending or receiving DHCP traffic on its segment.

The `debug ip udp` command executed on the Access Point (AP) itself is crucial because it displays all UDP packet exchanges originating from or destined to the AP. This allows verification of DHCP traffic (UDP ports 67/68) to ensure the AP is acquiring an IP address and also shows CAPWAP discovery messages (UDP ports 5246/5247), providing comprehensive insight into initial connectivity and join process failures.