Cisco Aironet Wifi "crashes" 3-5 minutes after reboot.

[bjuffinger]

Hello guys

I´m trying to setup 2 Cisco Aironet 2802e-e-K9 AP's. One is also the controller running the ME mode (master) and the other one is running the CAPWAP mode (slave). So far so good, but after booting the AP's, the wifi is up for about 3-5 minutes and suddenly it "crashes" or something. It seems to be active but i can't see the ssid on the clients anymore.

I'm searching for a solution very long time now but i can't find out anything. Maybe someone of you can help me finding a solution?

LED's blinking red, green, blue in a row

AP's in agroup and one wifi network.

Are there any MESH settings to do?

Sysinfo:

Software Version: 8.10.171.0

Model: AIR-AP2802E-E-K9

Power status
Power injector / Full Power

Max Capabilities
802.11n 2.4GHz,802.11ac 5GHz
Spatial Streams : 3 (2.4GHz), 3 (5.0GHz)
Max. Data Rate : 217 Mbps(2.4GHz), 2340 Mbps(5.0GHz)

[marce1000]

 - Could be a powering problem, reboot the AP and just after boot connect to it and issue the command show logging , or have a console attached and scrutinize the boot process,

 M.

[bjuffinger]

Hello! Thanks for the answer!

This is the log since last reset, on first sight it seems like a power issue like you said, am I right?

(Cisco Controller) >show logging last-reset

!!!Message and Trap Logs from Previous Reset

--------------------------------------------- Last Reboot MsgLog & Traplog ---------------------------------------------
Sys Name: juffinger
Model: AIR-AP2802E-E-K9
Version: 8.10.171.0
Primary Boot Image: 8.10.171.0 (default) (active)
Backup Boot Image: 0.0.0.0
LastReset Reason: Planned Reset
Timestamp: Sun Nov 6 11:43:30 2022
SystemUpTime: 0 days 0 hrs 29 mins 51 secs

-------------------------------------------------------MsgLog Dump ------------------------------------------------------------

*emWeb: Nov 06 11:43:29.097: %HREAP-3-HREAP_XML_FILE_SIZE: hreap_cfg.c:509 Hreap XML file size is: 1955 bytes.
*spamApTask0: Nov 06 11:43:19.102: %LWAPP-3-AP_DEL: spam_lrad.c:6088 00:d7:8f:b6:b8:20: Entry deleted for AP: 192.168.0.55 (5272) reason : Normal Termination.
nationpTask0: Nov 06 11:43:19.101: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7521 00:d7:8f:b6:b8:20: DTLS connection closed forAP 192:168:0:55 (5272), Controller: 192:168:0:171 (5246) Normal Term
*spamApTask0: Nov 06 11:14:21.868: %LOG-3-Q_IND: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP 00:d7:8f:b6:b8:20
*CAPWAP DATA: Nov 06 11:14:16.747: %RRM-3-RRM_LOGMSG: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP 00:d7:8f:b6:b8:20
*fp_main_task: Nov 06 11:13:46.453: %CNFGR-3-INV_COMP_ID: cnfgr.c:4326 Invalid Component Id : Unrecognized (45) in cfgConfiguratorInit.
*fp_main_task: Nov 06 11:13:46.364: %LWAPP-3-MAX_LRAD_CNT_UPDATED: spam.c:234 Max LRAD count is modified, old count:0, new count:100

--More-- or (q)uit

-----------------------------------------------------TrapLog Dump -----------------------------------------------------------

Sun Nov 6 11:43:19 2022 AP Disassociated. Base Radio MAC:00:d7:8f:b6:b8:20 ApName - AP002A-10C9-A3E6
Sun Nov 6 11:16:07 2022 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:a6:ca:ab:cd:40 Cause=AP_IF_TRAP_RADIO_LOW_POWER: Radio reset due to (117) Low in-line power Status:NA
Sun Nov 6 11:15:01 2022 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:d7:8f:b6:b8:20 Cause=AP_IF_TRAP_RADIO_LOW_POWER: Radio reset due to (117) Low in-line power Status:NA
Sun Nov 6 11:14:55 2022 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:a6:ca:ab:cd:40 Cause=RADIO_RC_CODE_UNDEF: Radio reset due to (0) Unknown Reset Status:NAne power Status:NA
Sun Nov 6 11:14:55 2022 AP's Interface:0(802.11abgn) Operation State Down: Base Radio MAC:00:a6:ca:ab:cd:40 Cause=RADIO_RC_CODE_UNDEF: Radio reset due to (0) Unknown Reset Status:NA
Sun Nov 6 11:14:51 2022 AP 'APCC16-7EF0-ACC0', MAC: 00:a6:ca:ab:cd:40 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 03 m 29 s . Reason: AP type changed to ME.
Sun Nov 6 11:14:51 2022 RF Manager updated TxPower for AP APCC16-7EF0-ACC0 Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 1 Reason: DTPC Tx Power value: 18 dbm
Sun Nov 6 11:14:51 2022 RF Manager updated TxPower for AP APCC16-7EF0-ACC0 Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 1 Reason: DTPC Tx Power value: 16 dbm
Sun Nov 6 11:14:51 2022 RF Manager updated TxPower for AP APCC16-7EF0-ACC0 Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 4 Reason: DTPC Tx Power value: 7 dbm
0 dbmv 6 11:14:49 2022 RF Manager updated TxPower for AP APCC16-7EF0-ACC0 Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11bg New Tx Power level is: 0 Reason: DTPC with Max Tx Power value
0 dbmov 6 11:14:49 2022 RF Manager updated TxPower for AP APCC16-7EF0-ACC0 Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC with Max Tx Power value:
0 dbmv 6 11:14:49 2022 RF Manager updated TxPower for AP APCC16-7EF0-ACC0 Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11bg New Tx Power level is: 0 Reason: DTPC with Max Tx Power value
Sun Nov 6 11:14:49 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:49 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:49 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:49 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:49 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:49 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:a6:ca:ab:cd:40 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:30 2022 Cold Start:

--More-- or (q)uit
Sun Nov 6 11:14:27 2022 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:d7:8f:b6:b8:20 Cause=RADIO_RC_CODE_UNDEF: Radio reset due to (0) Unknown Reset Status:NA
Sun Nov 6 11:14:27 2022 AP's Interface:0(802.11abgn) Operation State Up: Base Radio MAC:00:d7:8f:b6:b8:20 Cause=RADIO_RC_CODE_UNDEF: Radio reset due to (0) Unknown Reset Status:NA
Sun Nov 6 11:14:23 2022 AP 'AP002A-10C9-A3E6', MAC: 00:d7:8f:b6:b8:20 disassociated previously due to Link Failure. Uptime: 0 days, 11 h 31 m 42 s . Reason: Capwap Discovery Request.
Sun Nov 6 11:14:23 2022 RF Manager updated TxPower for AP AP002A-10C9-A3E6 Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 1 Reason: DTPC Tx Power value: 18 dbm
Sun Nov 6 11:14:23 2022 RF Manager updated TxPower for AP AP002A-10C9-A3E6 Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 1 Reason: DTPC Tx Power value: 16 dbm
Sun Nov 6 11:14:23 2022 RF Manager updated TxPower for AP AP002A-10C9-A3E6 Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 2 Reason: DTPC Tx Power value: 13 dbm
0 dbmv 6 11:14:21 2022 RF Manager updated TxPower for AP AP002A-10C9-A3E6 Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11bg New Tx Power level is: 0 Reason: DTPC with Max Tx Power value
0 dbmov 6 11:14:21 2022 RF Manager updated TxPower for AP AP002A-10C9-A3E6 Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC with Max Tx Power value:
0 dbmv 6 11:14:21 2022 RF Manager updated TxPower for AP AP002A-10C9-A3E6 Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11bg New Tx Power level is: 0 Reason: DTPC with Max Tx Power value
Sun Nov 6 11:14:21 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:21 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:21 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:21 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:21 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:14:21 2022 RF Manager updated TxPower for AP Base Radio MAC: 00:d7:8f:b6:b8:20 and Radio Type: 802.11a New Tx Power level is: 0 Reason: DTPC Tx Power value: 0 dbm
Sun Nov 6 11:13:52 2022 System cc:16:7e:f0:ac:c0 has Booted UP
Sun Nov 6 11:13:50 2022 A RF group member has been added on 802.11a network on controller with IP 192.168.0.171(MAC cc:16:7e:f0:ac:c0)
Sun Nov 6 11:13:50 2022 A RF group member has been added on 802.11b/g network on controller with IP 192.168.0.171(MAC cc:16:7e:f0:ac:c0)
Sun Nov 6 11:13:45 2022 Interface: virtual IP address changes from 0.0.0.0 to 192.0.2.1
Sun Nov 6 11:13:45 2022 Interface: management IP address changes from 0.0.0.0 to 192.168.0.171

[marce1000]

- Indeed, the ap does not get enough power.

M.

[Rich R]

What power injectors are you using?

[bjuffinger]

I'm using the Cisco AIR-PWRINJ6= they're recommended by Cisco for this AP model. They deliver about 30watts, should be enoigh, that's why I'm wondering why PoE should be a problem. Are there any PoE settings to do in the config?

[marce1000]

 - Try another AIR-PWRINJ6= , if available, 

 M.

[Rich R]

Yes should be enough.  Like @marce1000 could be a faulty unit - try another to be sure.
You could try upgrading to https://software.cisco.com/download/home/286304498/type/286289839/release/8.10.181.0 just in case it's a known bug although I'm sure we'd have heard about before now.