Access Points on WLC 2504

Wireless
1

Hello,

I am trying to connect the Cisco Access Point AIR-CAP 1602I-E-K9 to the Cisco WLC 2504.
However, I do not see it in the GUI under “Access Points.”
Is there anything else that needs to be done? Does the access point require a license, or can it be operated without one?

Thank you.

2

Hello Mar.Jaeger

Thanks for reaching out! This is a very common situation when setting up Cisco AireOS controllers like the WLC 2504, and I’m happy to walk you through both the licensing question and the AP discovery issue.

First, the good news is that the AIR-CAP1602I-E-K9 itself does not require a separate license, but understanding how WLC 2504 licensing works is key. On Cisco AireOS controllers, licensing is controller-based, not AP-model-based. The license lives on the controller, not on the access point. Your WLC 2504 shipped with a built-in AP-count license, typically 5, 15, 25, or 50 APs, depending on your specific part number. When you deploy the 1602i on your WLC 2504, it will join using the CAPWAP protocol and simply consume one of your controller’s available AP-license slots.

Now, about the AP not showing up in the GUI, this is almost always a configuration or discovery problem that’s fixable once we identify the root cause. The access point won’t appear in the Monitor > Access Points section until it completes the CAPWAP discovery and join process with the WLC. If it’s missing entirely, the join is failing silently.

I can suggest a troubleshooting process that may help you resolve the issue.

Start with these diagnostic commands on your WLC:

  • show ap join stats summary all
  • show time
  • show sysinfo | include Country

The show ap join stats command is your quickest diagnostic: it will tell you whether the WLC has even seen a discovery request from your AP’s MAC address and the specific failure reason.

Most common causes to your problem include:

  • Clock/Certificate mismatch — If your WLC’s system clock is outside the AP’s certificate validity window, the join fails silently. Verify show time and sync via NTP if needed.
  • Country code not set — The WLC and AP must have matching regulatory domains. Check config country on the WLC and confirm it matches the AP’s domain sticker.
  • AP not reachable at Layer 3 — The AP must be on the same VLAN as the WLC’s management interface and able to obtain an IP via DHCP. Verify the trunk port and DHCP scope include the AP’s VLAN.
  • AP authorization/certificate policy — Check Security > AP Policies: if “AP Authorization List” is enabled, add your AP’s MAC. If your AP has a self-signed certificate (not a manufacturer certificate), enable “Accept Self-Signed Certificate (SSC).”
  • AP-count license limit — If your WLC 2504 base license supports only 5 APs and you’re at that limit, new APs will be refused.

Run those commands and share the output, along with a screenshot of your Security > AP Policies settings. That will pinpoint exactly which of these is blocking your AP, and we can fix it together.

For a deeper walkthrough, I’d also recommend reviewing our lesson on Cisco WLC Basic Configuration. It walks through the VLAN, country code, and AP join process step by step, which should help you understand the full picture.

Let me know how you get along and if we can help further.

I hope this has been helpful!

Laz