AIR-AP4800-A-K9 is not broadcasting SSID

[rizwanr74]

Hi guy I have got APs one is: AIR-AP4800-A-K9  and other is AIR-AP3802-i-K9, neither of them broadcasting SSID.

I am able to login to web-console and wlan is enabled.

I powered them via Cisco DC injector and through none-cisco PoE switch (i.e. netgear switch).

Version I am running is: 8.7.106.0

I don't know what to do here.

Any help is appreciated and will be rated.

Thanks

RR

[marce1000]

 - Check the status of the radios.

 M.

[rizwanr74]

Hi Marce,

Check status of radio on the web-console?  How?

Or on the CLI ?

Thx

[rizwanr74]

Hi Marce,

I was trying to setup WAP2 simple wlan and default vlan id as 1.

Thx

[Arshad Safrulla]

Hi Rizwan,

How are these AP's managed? Are they running ME WLC or capwap?

[rizwanr74]

Hi Arshad,

ME WLC is running on AIR-AP4800-A-K9.

I didn't add any additional APs yet, I believe WLC itself should broadcast wlan once it is configured.

Thx

[Arshad Safrulla]

Can you login to the AP shell and check whether it is having an IP address

[rizwanr74]

Hi Arshad,

It has got an ip-address, I am able to open the web-console on the ME App itself.

Thx

RR

[Arshad Safrulla]

use the command apciscoshell to connect to the AP console

use username Cisco and password Cisco

now check whether the AP has an IP.

Also note that the upstream switchport must be configured as below.

Interface X/X/X

switchport mode trunk

switchport trunk native vlan <Management VLAN>

switch trunk allowed vlan <management VLAN  + Wireless VLAN's)

[rizwanr74]

Hi Arshad,

Issue is, no SSID is being broadcasted.

Switch-port configuration has no bearing to SSID is not being broadcast.

Thx

RR

[rizwanr74]

I upgraded both APs capwap and ME AP to latest version and yet I don't see SSID is being broadcast.

Capwap AP has joined ME and I see both radios 2.4Ghz and 5Ghz radios are enabled state.

I don't know what is happening here.

Anyone else can help me?

Thx

RR

[marce1000]

 - Reboot the AP , then immediately after reboot  issue the command show logging , check if you can find any anomalies.

 M.

[rizwanr74]

Here is the output from "show logging".

(Cisco Controller) >show logging

Logging to Logger Queue :
- Logging of system messages to Logger Queue :
- Effective Logging Queue filter level.......... errors
- Number of Messages recieved for logging :
- Emergency severity............................ 0
- Alert Severity................................ 0
- Critical Severity............................. 0
- Error Severity................................ 11
- Warning Severity.............................. 6
- Notice Severity............................... 18
- Information Severity.......................... 95
- Debug Severity................................ 6
- Total messages recieved....................... 136
- Total messages enqueued....................... 10
- Total messages dropped........................ 126
Logging to buffer :
- Logging of system messages to buffer :
- Logging filter level.......................... errors
- Number of system messages logged.............. 11
- Number of system messages dropped.............
- Number of Messages dropped due to Facility .... 0127
- Logging of debug messages to buffer ........... Disabled

--More-- or (q)uit
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Cache of logging ............................. Disabled
- Cache of logging time(mins) ................... 10080
- Number of over cache time log dropped ........ 0
Logging to console :
- Logging of system messages to console :
- Logging filter level.......................... disabled
- Number of system messages logged.............. 0
- Number of system messages dropped............. 138
- Number of system messages throttled........... 0
- Logging of debug messages to console .......... Enabled
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Number of debug messages throttled............ 0
Logging to syslog :
- Syslog facility................................ local0
- Logging of system messages to syslog :
- Logging filter level.......................... errors
- Number of system messages logged.............. 11
- Number of system messages dropped............. 127
- Logging of debug messages to syslog ........... Disabled
- Number of debug messages logged............... 0

--More-- or (q)uit
- Number of debug messages dropped.............. 0
- Number of remote syslog hosts.................. 0
- syslog over tls................................ Disabled
- syslog over ipsec.............................. Disabled
- ipsec profile inuse for syslog................. none
- Host 0.......................................
- Host 1.......................................
- Host 2.......................................
Logging of Debug messages to file :
- Logging of Debug messages to file.............. Disabled
- Number of debug messages logged................ 0
- Number of debug messages dropped............... 0
Logging of traceback............................. Enabled
- Traceback logging level........................ errors
Logging of source file informational............. Enabled
Timestamping of messages.........................
- Timestamping of system messages................ Enabled
- Timestamp format.............................. Date and Time
- Timestamping of debug messages................. Enabled
- Timestamp format.............................. Date and Time

Logging buffer (11 logged, 127 dropped)

--More-- or (q)uit
*sntpReceiveTask: Jul 30 09:32:32.481: %DNS-3-GETADDRINFO_ERR: dns_query.c:256 Internal Error: getaddrinfo failed for 2.ciscome.pool.ntp.org
*sntpReceiveTask: Jul 30 09:32:22.476: %DNS-3-GETADDRINFO_ERR: dns_query.c:256 Internal Error: getaddrinfo failed for 1.ciscome.pool.ntp.org
*sntpReceiveTask: Jul 30 09:32:12.470: %DNS-3-GETADDRINFO_ERR: dns_query.c:256 Internal Error: getaddrinfo failed for 0.ciscome.pool.ntp.org
*sntpReceiveTask: Jul 30 09:31:52.482: %DNS-3-GETADDRINFO_ERR: dns_query.c:256 Internal Error: getaddrinfo failed for 2.ciscome.pool.ntp.org
*spamApTask0: Jul 30 09:31:46.235: %LWAPP-3-STATIC_IP_ERR: spam_lrad.c:61163 Configured static IP Address is not valid for AP a0:b4:39:7e:2b:40
*sntpReceiveTask: Jul 30 09:31:42.476: %DNS-3-GETADDRINFO_ERR: dns_query.c:256 Internal Error: getaddrinfo failed for 1.ciscome.pool.ntp.org
*sntpReceiveTask: Jul 30 09:31:32.470: %DNS-3-GETADDRINFO_ERR: dns_query.c:256 Internal Error: getaddrinfo failed for 0.ciscome.pool.ntp.org
*osapiReaper: Jul 30 09:31:19.607: %LOG-3-Q_IND: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP a0:b4:39:7e:2b:40
*CAPWAP DATA: Jul 30 09:31:10.466: %RRM-3-RRM_LOGMSG: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP a0:b4:39:7e:2b:40
*fp_main_task: Jul 30 09:31:03.467: %CNFGR-3-INV_COMP_ID: cnfgr.c:4326 Invalid Component Id : Unrecognized (45) in cfgConfiguratorInit.

(Cisco Controller) >

[rizwanr74]

What I think the issue was, I configured the ME AP without providing a valid DNS server ip-address that is routable. When I connected the ME AP to my home home-network, the AP was able to resolve DNS names, then the radio came online, I mean radio becomes active.

So I believe, no DNS resolution means, no Radio or no Radio becomes active.

[Arshad Safrulla]

Not the case. Probably had something to do with NTP. As per your logs you had a dns record configured as NTP server. As soon as it resolved the NTP IP AP's registered and came up.