Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2380
Views
0
Helpful
4
Replies

WAP 321 Random Reboot

dell.brinson
Level 1
Level 1

‎11-04-2013 10:05 AM

Hello, I have 3 WAP 321 all at firmware 1.0.4.2.  One of the access points continues to randomly reboot.  When I check the error log, there isn't any distinct errors, but I do notice the time stamps from when the access point starts backup have an unusual date like 1969 or something until it corrects the time.  I have tried reinstalling the firmware and reset it to the default/factory setup with no success.  Two of the wap's are connected via POE and one is connected via the cisco power supply.  I have taken one of the properly working waps and switch locations to make sure it wasn't related to the cisco power supply.  It worked fine via the power supply.  I have only had them since March.  Any suggestions?  Since its rebooting, it's dropping the connections and therefore is no providing benefit.  I have disconnected it from the network and I am running on 2 WAPs.  Any suggestions would be beneficial.

Here are the latest crash dumps:

crashdumps:

crashdump1:

Software Version: 1.0.4.2

Crash Log:

Uptime of the AP: 0 Days, 0 Hours, 30 Minutes and 37 Seconds

CPU Unable to handle kernel paging request for process = swapper and pid = 0

epc == 202a, ra == c05c3520

Stack Trace:

PC is not a kernel space address. Exiting

crashdump2:

Software Version: 1.0.4.2

Crash Log:

Uptime of the AP: 0 Days, 0 Hours, 45 Minutes and 31 Seconds

CPU Unable to handle kernel paging request for process = swapper and pid = 0

epc == c061d8e0, ra == c061d8d8

Stack Trace:

[<00000000c05fe9cc>] - wlc_phy_aci_scan_nphy+0xae4/0x1178 [wl]

[<00000000c06003dc>] - wlc_phy_acimode_upd_nphy+0x4c/0x760 [wl]

[<00000000c05d2e8c>] - wlc_phy_watchdog+0xd14/0xd88 [wl]

[<00000000c053724c>] - wlc_watchdog+0x140/0x1198 [wl]

[<00000000c0538464>] - wlc_watchdog_timer+0x1c/0x90 [wl]

[<00000000c05654f8>] - wl_timer+0x184/0x1bc [wl]

[<0000000080033500>] - run_timer_softirq+0x170/0x1f8

[<000000008002ea20>] - __do_softirq+0x80/0x110

[<000000008002eb18>] - do_softirq+0x68/0x70

crashdump3:

Software Version: 1.0.4.2

Crash Log:

Uptime of the AP: 0 Days, 3 Hours, 32 Minutes and 14 Seconds

CPU Unable to handle kernel paging request for process = swapper and pid = 0

epc == c061d8e0, ra == c061d8d8

Stack Trace:

[<00000000c05fe9cc>] - wlc_phy_aci_scan_nphy+0xae4/0x1178 [wl]

[<00000000c06003dc>] - wlc_phy_acimode_upd_nphy+0x4c/0x760 [wl]

[<00000000c05d2e8c>] - wlc_phy_watchdog+0xd14/0xd88 [wl]

[<00000000c053724c>] - wlc_watchdog+0x140/0x1198 [wl]

[<00000000c0538464>] - wlc_watchdog_timer+0x1c/0x90 [wl]

[<00000000c05654f8>] - wl_timer+0x184/0x1bc [wl]

[<0000000080033500>] - run_timer_softirq+0x170/0x1f8

[<000000008002ea20>] - __do_softirq+0x80/0x110

[<000000008002eb18>] - do_softirq+0x68/0x70


Labels:
0 Helpful
4 Replies 4

Eric Moyers
Level 7
Level 7

‎11-06-2013 06:52 AM

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Thank you for using the Cisco Community Post Forums.

I am sorry to hear about the issue that you are having. I would like to ask a couple of questions to help determine the next course of action.

You mentioned that you took one of the WAP that is currently working and plugged it into the power supply and it continued working. Did you then take the one that was not working and try it with PoE?

Is the non working one hardwired to a switch or is it bridged or repeating another WAP?

Thanks

Eric Moyers    .:|:.:|:.

Cisco Small Business US STAC Advanced Support Engineer

CCNA, CCNA-Wireless

866-606-1866

Mon - Fri 09:00 - 18:00 (UTC - 05:00)

*Please rate the Post so other will know when an answer has been found.

0 Helpful

dell.brinson
Level 1
Level 1
In response to Eric Moyers

‎11-06-2013 10:39 AM

HI Eric, thanks for responding.  I tried the problem WAP both on POE and with the cisco power supply.  The power source didn't make a different, it would still randomly crash.  As an update I did the following and it has been running for

System Uptime:1 days, 5 hours, 13 minutes

So far this is the longest that it has been running without a crash.

  • Removed it from the Single Point Setup Cluster
  • While at v 1.0.4.2, I did a hard factory reset by holding the reset button for 30 secs
  • Once it restarted I logged in and downgraded the firmware to 1.0.1.10
  • While at v 1.0.1.10, I did a hard factory reset by holding the reset button for 30 secs
  • Once it restarted I logged in and upgraded the firmware back to 1.0.4.2
  • While at 1.0.4.2, I did a hard factory reset by holding the reset button for 30 secs
  • Once it restarted, I added it back to the Single Point Setup Cluster and it has been up and running every since for the time period listed above.
0 Helpful

Eric Moyers
Level 7
Level 7
In response to dell.brinson

‎11-06-2013 12:54 PM

Ok, please keep us posted.

Eric Moyers

0 Helpful

dell.brinson
Level 1
Level 1

‎11-13-2013 05:04 AM

I think my last steps have resolved the issue.  The system has been up for

System Uptime:7 days, 23 hours, 41 minutes

without random rebooting.

To recap:

  • Removed it from the Single Point Setup Cluster
  • While at v 1.0.4.2, I did a hard factory reset by holding the reset button for 30 secs
  • Once it restarted I logged in and downgraded the firmware to 1.0.1.10
  • While at v 1.0.1.10, I did a hard factory reset by holding the reset button for 30 secs
  • Once it restarted I logged in and upgraded the firmware back to 1.0.4.2
  • While at 1.0.4.2, I did a hard factory reset by holding the reset button for 30 secs
  • Once it restarted, I added it back to the Single Point Setup Cluster and it has been up and running every since for the time period listed above.

    • 0 Helpful
    Customers Also Viewed These Support Documents