01-20-2012 08:42 AM - edited 07-03-2021 09:25 PM
After a solid year of running great one of my Aironet 1142N access points started acting up on me. Yesterday, both radio interfaces changed to 'reset/down' state for some reason. The only way I could get them back to 'up/up' was to reload the access point. If I shutdown the interface and brought it back up, it would then display 'up/down'.
I thought it was fixed but today the wireless was weak again, so I checked and now just one of the radio interfaces is back to 'reset/down'. Reloaded the access point and we are back to 'up/up' and great coverage again. Think it could be a hardware issue, or am I overlooking something maybe?
DFW-WAP-2#sh int
BVI1 is up, line protocol is up
Hardware is BVI, address is e8b7.48d6.e51c (bia 5835.d93b.24e0)
Internet address is 172.19.1.12/24
MTU 1500 bytes, BW 54000 Kbit, DLY 5000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
5 minute input rate 2000 bits/sec, 3 packets/sec
5 minute output rate 0 bits/sec, 1 packets/sec
147584 packets input, 10169501 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
25464 packets output, 2703331 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
267 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
Dot11Radio0 is reset, line protocol is down
Hardware is 802.11N 2.4GHz Radio, address is 5835.d93b.24e0 (bia 5835.d93b.24e0)
MTU 1500 bytes, BW 54000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 07:27:05, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/1677/0/0 (size/max/drops/flushes); Total output drops: 445
Queueing strategy: fifo
Output queue: 0/30 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
191878 packets input, 72311574 bytes, 0 no buffer
Received 7212 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
286017 packets output, 153414519 bytes, 0 underruns
82 output errors, 0 collisions, 4 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Dot11Radio0.1 is reset, line protocol is down
Hardware is 802.11N 2.4GHz Radio, address is 5835.d93b.24e0 (bia 5835.d93b.24e0)
MTU 1500 bytes, BW 54000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1.
ARP type: ARPA, ARP Timeout 04:00:00
Last clearing of "show interface" counters never
Dot11Radio0.100 is reset, line protocol is down
Hardware is 802.11N 2.4GHz Radio, address is 5835.d93b.24e0 (bia 5835.d93b.24e0)
MTU 1500 bytes, BW 54000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 100.
ARP type: ARPA, ARP Timeout 04:00:00
Last clearing of "show interface" counters never
Dot11Radio1 is up, line protocol is up
01-20-2012 10:52 AM
Try a:
>show controllers dot11Radio 0/1
... the last chunk of output should give you some feedback on what's causing the radio resets.
Last radio reset code: 62
Radio resets - total:23 retries:0 failed:0
Reset Stats: Start Cnt: 19, Recovery: Cnt 0, Last Ret: 0, Fails: 0, Recvry Status: Stalled NO, In Prog NO
Code/Count: 37/00008 54/00001 62/00013 67/00001
Log Buffer:
I don't *believe* Cisco makes these codes public, but a little Google-Fu usually yields results ;-)
Best of luck!
05-01-2014 10:36 AM
I also was unable to find a sheet on cisco or google to find the Aironet reset codes. I ended up power cycling the Aironet 1142N and the interface and line protocol came back up.
05-01-2014 06:49 PM
Console into the AP and reboot the AP. Post the entire boot-up process.
02-18-2016 01:14 PM
I know this is an old thread but unanswered.
This happened to me and I resolve it by adding SSID under the dot11radio interface.
Thanks,
Mulu
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide