cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4880
Views
25
Helpful
19
Replies

AP Unexpected reboot

tanner.zaitt
Level 3
Level 3

Hello All

Please could you confirm that the reason for restarting of the access point is related with Poe issue?
Last reset from power-on

I didn't find logs for Poe issue...



Logs from the switch:
016229: Jun 17 10:32:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/30, changed state to down

016230: 000091: Jun 17 10:32:42: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi2/0/30: PD removed (access_sw)

016231: Jun 17 10:32:43: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/30, changed state to down

016232: Jun 17 10:33:14: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/30, changed state to up

016233: Jun 17 10:33:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/30, changed state to up

016234: Jun 17 10:37:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/30, changed state to down

016235: Jun 17 10:37:21: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/30, changed state to down

016236: 000092: Jun 17 10:37:23: %ILPOWER-7-DETECT: Interface Gi2/0/30: Power Device detected: IEEE PD (access_sw)

016237: 000093: Jun 17 10:37:25: %ILPOWER-5-POWER_GRANTED: Interface Gi2/0/30: Power granted (access_sw)

016238: Jun 17 10:37:44: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/30, changed state to up

016239: Jun 17 10:37:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/30, changed state to up


Logs from the AP:
*Jun 17 08:39:57.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.152.177.3 peer_port: 5246
*Jun 17 08:39:57.211: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.152.177.3 peer_port: 5246
*Jun 17 08:39:57.211: %CAPWAP-5-SENDJOIN: sending Join Request to 10.152.177.3
*Jun 17 08:40:02.211: %CAPWAP-5-SENDJOIN: sending Join Request to 10.152.177.3
*Jun 17 08:40:02.355: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 56
*Jun 17 08:40:02.359: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 17 08:40:02.367: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 17 08:40:02.987: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 56
*Jun 17 08:40:02.987: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10
*Jun 17 08:40:02.995: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WLC01
*Jun 17 08:40:03.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 17 08:40:03.007: [m102x_set_lanport_config] Cannot enable AUX port while POE, connect AC or Inj source
*Jun 17 08:40:03.223: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
*Jun 17 08:40:03.359: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 17 08:40:03.403: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jun 17 08:40:03.411: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jun 17 08:40:04.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jun 17 08:40:04.255: %LINEPROTO-5-UPDOWN: Line protocol on Interface NVI0, changed state to up
*Jun 17 08:40:04.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 17 08:40:04.443: %DOT11-6-DFS_SCAN_START: DFS: Scanning frequency 5320 MHz for 60 seconds.
*Jun 17 08:40:04.447: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 17 08:40:04.455: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 17 08:40:04.463: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 17 08:40:05.447: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jun 17 08:40:05.455: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 17 08:40:05.487: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 17 08:40:06.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 17 08:40:26.543: %CLEANAIR-6-STATE: Slot 0 enabled
*Jun 17 08:40:28.311: %CLEANAIR-6-STATE: Slot 1 enabled
*Jun 17 08:40:42.267: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10
*Jun 17 08:40:42.267: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 10
*Jun 17 08:40:42.267: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Jun 17 08:40:42.271: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 17 08:40:42.279: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 17 08:40:43.271: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 17 08:40:43.311: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 17 08:40:43.319: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jun 17 08:40:43.327: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jun 17 08:40:44.311: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 17 08:40:44.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jun 17 08:40:44.367: %DOT11-6-DFS_SCAN_START: DFS: Scanning frequency 5320 MHz for 60 seconds.
*Jun 17 08:40:44.371: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 17 08:40:45.371: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed

Show version of the AP:

Cisco IOS Software, C2700 Software (AP3G2-K9W8-M), Version 15.3(3)JK3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2020 by Cisco Systems, Inc.
Compiled Wed 29-Jul-20 04:24 by prod_rel_team

ROM: Bootstrap program is C2700 boot loader
BOOTLDR: C2700 Boot Loader (AP3G2-BOOT-M) LoaderVersion 15.2(4)JB5m, RELEASE SOFTWARE (fc2)

AP01 uptime is 1 hour, 12 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g2-k9w8-mx.153-3.JK3/ap3g2-k9w8-xx.153-3.JK3"
Last reload reason: Image upgrade.

 

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco AIR-CAP2702E-E-K9 (PowerPC) processor (revision A0) with 376814K/134656K bytes of memory.
Processor board ID FCZ2201J0XG
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.10.130.0
1 Gigabit Ethernet interface
2 802.11 Radios

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: xxxxxxxxxxxxx
Part Number : xxxxxxxxxxxx
PCB Serial Number : xxxxxxxxxxxxxxx
Top Assembly Part Number : xxxxxxxxxxxxxxxx
Top Assembly Serial Number : xxxxxxxxxxxxxxxxxx
Top Revision Number : xx
Product/Model Number : AIR-CAP2702E-E-K9

 

Configuration register is 0xF


Gi2/0/30 auto on 16.8 AIR-CAP2702E-E-K9 4 30.0

19 Replies 19

Hello Scot,

No, the WLC controllers are two in HA, one is waiting on standby and one is with an active role.
A few months ago we upgraded them to the same version.
Differences regarding the image don't exist.

Okay so maybe the message isn’t telling you exactly what happens. Logs from the switch and staking would be the same if you disconnected the ap, reset the ap and or the ap crashed. Radio resets and other items that forces the ap to reboot can happen and will happen. Like I mentioned, open a TAC case and see what the tac engineer provides you. It might help with understanding what might of happened and also explain what you are seeing.
-Scott
*** Please rate helpful posts ***

tanner.zaitt
Level 3
Level 3

Thank you I will move the AP to another port.
If it's required I will open a case to Cisco TAC.

Please could you share your experience with TAC?
I try to solve my issues alone or with your help from the community here.

I am not satisfied from TAC support maybe TAC performance in EAST Europe and Asia is low.
When you open a case to them from where comes the TAC support?

I always open a tac case when I run into things I don’t have a clue about. I always tell folks that it’s fine to try to solve things yourself, but you shouldn’t take day’s to figure it out. While you try figuring it out, open a tac case. I have not had any issue with TAC, any help is great. Just like in the forums, you might get an answer you may not like, it’s understanding what happened or not, see if it happens again with the same ap or not and coming up with your theory. AP’s will bounce, it just what happens, not all the time, but it does happen.
-Scott
*** Please rate helpful posts ***


@tanner.zaitt wrote:

I am not satisfied from TAC support maybe TAC performance in EAST Europe and Asia is low.


When this happens, get the Case re-queued to LATAM or RTP.

Review Cisco Networking for a $25 gift card