Cisco Catalyst 9800-L-F Wireless controller

[gopi-potteti]

Hello All,

Can any help  for my issue mentioned below.

I have a WLC - 9800-L-F and  three Access Point -C9130AXI-A  and both are running on Ver 17.9.4

my issue , i have given a static IP for Access point and i am able to ping Controller and same time getting ping from controller to access point.

however, the access point is not appearing on wireless access points list.

i hope you all understand my issue.

Thank you for your support and solutions.

[MHM Cisco World]

If you manually assign IP to AP then AP can not use dhcp/dns to discover wlc mgmt IP

Here you need to also manually add wlc mgmt IP to AP 

MHM

[marce1000]

     (edited) : Following other posters remarks you may need : capwap ap controller ip address <ip>
                   (on the access point)
                          Standard methodology however is always to have APs use DHCP with dhcp option 43 to find the
                         controller 

   -  Have an overall checkup of the  WLC - 9800-L-F controller's configuration with the CLI command
       show tech wireless and feed the output from that into Wireless Config Analyzer
      use the full command as denoted in green , do not use a simple show tech as input for this procedure

   + Post the full boot sequence of the AP
   + Look into https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin
   + Checkout https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/217738-monitor-catalyst-9800-kpis-key-performa.html#anc4  when you make corrections, 

 M.

[gopi-potteti]

after executing this command in on controller - "wireless management interface vlan ID" and "capwap-discovery public" , the controller starts discovering APs

[Rich R]

Note that the controller does not discover the APs.  It is always the APs which discover the controller.

Missing wireless management interface config would have been highlighted by the Config Analyzer which @marce1000 suggested and which should always be your first point of call for detecting simple config errors.

capwap-discovery public should only be needed in very specific scenarios where you are using NAT with a public IP and want the APs to join the private IP.  Are you sure you needed this?

Refer to the TAC Recommended link below for the latest TAC recommended code versions which you should be using.