1130AG Radio will not enable.

Answered Question
Jun 14th, 2010

Hey folks,


Something happend over the weekend at a remote site with my 1130AG WAP.  The ethernet is up but the Radio will not come up.  Here are some logs, etc:


000010: *Jun 14 10:46:43.010 CDT: %SSH-5-ENABLED: SSH 1.99 has been enabled
000011: *Jun 14 10:46:43.013 CDT: Writing radio coredump to 'flash:/r0.rcore'
000012: *Jun 14 10:46:43.811 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down
000013: *Jun 14 10:46:44.210 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
000014: *Jun 14 10:46:51.388 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
000015: Jun 14 10:48:25.109 CDT: Writing radio coredump to 'flash:/r0.rcore'
000016: Jun 14 10:48:26.306 CDT: Interface Dot11Radio0: not starting because stop-on-failure set
000017: Jun 14 10:48:31.081 CDT: %PKI-6-AUTOSAVE: Running configuration saved to NVRAM
000018: Jun 14 10:49:15.904 CDT: %CDP_PD-4-POWER_OK: Full power - NON_CISCO-NO_CDP_RECEIVED inline power source
000019: Jun 14 10:49:15.904 CDT: Interface Dot11Radio0: not starting because stop-on-failure set


Just so not to rabbit trail, line item 18 above is because I am using a POE injector (non Cisco) which IS 802.3af compliant. (http://www.engeniustech.com/resources/NPE-4818_PoE.pdf).  It's cheaper than purchasing a POE switch (Cisco or otherwise) for only one POE device in this remote office of two users. ($21)


Hereis the #show interfaces Dot11Radio0


Dot11Radio0 is initializing, line protocol is down
  Hardware is 802.11G Radio, address is 0000.0000.0000 (bia 0000.0000.0000)
  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 never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/1127/0/0 (size/max/drops/flushes); Total output drops: 0
  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
     0 packets input, 0 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 input packets with dribble condition detected
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out


I see the Stop-On-Failure log line 19, but not having much luck determining how to trouble-shoot this.

The unit connects back to a 3com switch (after going through the POE Injector).


  TAC tells me the warranty ran out last month (May), and I could either do one-time suppport @ $400/hr, or probably better off purchasing a new one.




Before I purchase a new one, what might I be missing that could resolve this?


Thanks,


James

Correct Answer by Rob Huffman about 6 years 8 months ago

Hi James,


I think this line from your original post;


000019: Jun 14 10:49:15.904 CDT: Interface Dot11Radio0: not starting because stop-on-failure set


And this from the last post;


-Traceback= 0x2E6F68 0x2E2158 0x4F7C08 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000028: Jun 15 08:43:52.120 CDT: %SYS-3-CPUYLD: Task ran for (6984)msecs, more than (2000)msecs (0/0),process = Dot11 driver


And this description of the problem;


stop-on-failure Configures the access point to not restart when the radio driver fails



Tell us the sad story of this AP I guess it's off to the great wireless infrastructure

beyond.



Cheers!

Rob

Correct Answer by Leo Laohoo about 6 years 8 months ago

Use CLI:


arch download-sw /noset tftp:///c1130-k9w7-tar.124-10b.JDA3.tar


Hope this helps.


Please don't forget to rate useful posts.  Thanks.

Correct Answer by dancampb about 6 years 8 months ago

You have some issue with the radio firmware.  You can see this with the rcore files being generated and that the radio's mac address is showing as all zeros.  You could try loading a different version of code to the AP.  This would put a new radio firmware file onto the AP.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Correct Answer
dancampb Mon, 06/14/2010 - 12:15

You have some issue with the radio firmware.  You can see this with the rcore files being generated and that the radio's mac address is showing as all zeros.  You could try loading a different version of code to the AP.  This would put a new radio firmware file onto the AP.

jmhunter Mon, 06/14/2010 - 13:51

Thanks DanCampB.  I've downloaded a current image from Cisco "c1130-k9w7-tar.124-10b.JDA3.tar", dropped it into my C:\ Drive.  (On the root, atually).  I then used the WEB interface to try to do the upgrade/reimage.  I get two popups.  THe first one is this:


And the second one is this:

That's all I get.  I've waited a great while, but nothing seems to be happening.


Am I missing something here?  I do have a TFTP server available to upload the image with, again, the Cisco DOCs are not clear on this procedure.


Thanks,


James

Correct Answer
Leo Laohoo Mon, 06/14/2010 - 15:35

Use CLI:


arch download-sw /noset tftp:///c1130-k9w7-tar.124-10b.JDA3.tar


Hope this helps.


Please don't forget to rate useful posts.  Thanks.

jmhunter Tue, 06/15/2010 - 06:10

Well, thanks for all the assistance.  The answers were correct so far.  I have awarded

points for them.  The problem still seems to persist.  Here is the latest log files:


000010: *Feb 28 19:00:23.250 EST: %SNMP-5-COLDSTART: SNMP agent on host ATL-AP-01 is undergoing a cold start
000011: *Jun 15 08:33:26.008 CDT: %SSH-5-ENABLED: SSH 1.99 has been enabled
000012: *Jun 15 08:33:26.504 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down
000013: *Jun 15 08:33:26.747 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
000014: *Jun 15 08:33:26.837 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
000015: *Jun 15 08:33:28.714 CDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
000016: Jun 15 08:36:11.745 CDT: %CDP_PD-4-POWER_OK: Full power - NON_CISCO-NO_CDP_RECEIVED inline power source
000017: Jun 15 08:36:32.830 CDT: %DOT11-2-RESET_RADIO: Restarting Radio interface Dot11Radio0 due to won't start
000018: Jun 15 08:36:34.825 CDT: %SYS-3-CPUHOG: Task is running for (1995)msecs, more than (2000)msecs (0/0),process = Dot11 driver.
-Traceback= 0x2E6F68 0x2E2158 0x4F7BEC 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000019: Jun 15 08:36:36.820 CDT: %SYS-3-CPUHOG: Task is running for (3990)msecs, more than (2000)msecs (0/0),process = Dot11 driver.
-Traceback= 0x2EB6E8 0x2E6F6C 0x2E2158 0x4F7C08 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000020: Jun 15 08:36:38.816 CDT: %SYS-3-CPUHOG: Task is running for (5985)msecs, more than (2000)msecs (0/0),process = Dot11 driver.
-Traceback= 0x2E6FA8 0x2E6F7C 0x4F7C08 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000021: Jun 15 08:36:39.815 CDT: %SYS-3-CPUYLD: Task ran for (6984)msecs, more than (2000)msecs (0/0),process = Dot11 driver
000022: Jun 15 08:43:20.284 CDT: %SYS-5-CONFIG_I: Configured from http by admin on 172.16.1.205
000023: Jun 15 08:43:20.474 CDT: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
000024: Jun 15 08:43:45.135 CDT: %DOT11-2-RESET_RADIO: Restarting Radio interface Dot11Radio0 due to won't start
000025: Jun 15 08:43:47.129 CDT: %SYS-3-CPUHOG: Task is running for (1994)msecs, more than (2000)msecs (0/0),process = Dot11 driver.
-Traceback= 0x2E6F68 0x2E2158 0x4F7BEC 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000026: Jun 15 08:43:49.124 CDT: %SYS-3-CPUHOG: Task is running for (3989)msecs, more than (2000)msecs (0/0),process = Dot11 driver.
-Traceback= 0x2EB6E8 0x2E6F6C 0x2E2158 0x4F7C08 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000027: Jun 15 08:43:51.120 CDT: %SYS-3-CPUHOG: Task is running for (5985)msecs, more than (2000)msecs (0/0),process = Dot11 driver.
-Traceback= 0x2E6F68 0x2E2158 0x4F7C08 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000028: Jun 15 08:43:52.120 CDT: %SYS-3-CPUYLD: Task ran for (6984)msecs, more than (2000)msecs (0/0),process = Dot11 driver

Any other ideas or, the radio probably dead?


THanks,


James

Correct Answer
Rob Huffman Tue, 06/15/2010 - 06:50

Hi James,


I think this line from your original post;


000019: Jun 14 10:49:15.904 CDT: Interface Dot11Radio0: not starting because stop-on-failure set


And this from the last post;


-Traceback= 0x2E6F68 0x2E2158 0x4F7C08 0x7D2070 0x7D4D8C 0x5034E0 0x50CA74 0x1A3B30
000028: Jun 15 08:43:52.120 CDT: %SYS-3-CPUYLD: Task ran for (6984)msecs, more than (2000)msecs (0/0),process = Dot11 driver


And this description of the problem;


stop-on-failure Configures the access point to not restart when the radio driver fails



Tell us the sad story of this AP I guess it's off to the great wireless infrastructure

beyond.



Cheers!

Rob

Leo Laohoo Tue, 06/15/2010 - 15:31

Hi James,


I agree.  The AP could be dead.  During the bootup process the AP will undergo a Power On Self-Test (POST) with the FIPS.  Can you post the result?

jmhunter Wed, 06/16/2010 - 06:32

I configured and sent out the replacement unit.  The unit being in a remote site, I do not have it set up with the console cable to capture the bootup info.  When I get the defective unit back, I'll do that and post the results.  The information none the less might be helpful for others searching this forum.


It'll be a few days before I get the old unit back.


Thanks for the help!


James

jmhunter Mon, 06/21/2010 - 06:13

Well, I finally received the radio back.  Plugged it in, and all seems to be working.  There are no trace back lines.  I can only guess something got knocked around in shipping (unlikely) or gremlins

Thanks for the assistance folks...

Actions

This Discussion

Related Content