New AP's rebooting

Fresh install
2 AP’s running into a CMM4.
Both running SW version 2.1.1
Both AP’s appear to be rebooting at the same time, intermittently
CMM4 not re-booting
Nothing else re-booting at site

Thoughts?
Thanks

By any chance do you have a cable atteched to the RJ 11 jack on the AP? If so this will cause the AP to reboot

I work for cmack, and no the reset cable is not plugged in.

Update.
It appears the AP’s are not re-booting simultaneously as previously posted, they did once on the weekend, the rest of the time they do it independently.

upgrade the switch of the CMM4.

I’m not sure what you mean by upgrade the switch of the CMM4? and is there a reason?
Thanks

older firmware for etherwan siwtch in cmm4 caused 3.65 ap’s to reboot randomly. as well as disable flow control on all ports connected to 3.65 ap.

Here is the link to the firware for the switch
http://www.etherwan.com/support-mo.php
Make sure flow control is turned off on the switch

The cmm4 we have does not have a switch included.

Where did you get your CMM4 without thr etherwan switch. We were told we couldnt purchase onw without.


Also are you guys still seeign the AP reboot or was it the swithch firmware like you posted?

version 2.2 ap randomly rebooting itself coupe times a day, when it happens some customers do not link back.

here is crash report, and yes switch is 1.91 with no flow control’

also i have two ap connected in this set up and ap 1 has no issues its only ap 2


Subject: Reset cnt 54 DAN PM - Host name localhost, BSID 00.01.02.03.04.05 BUILD_ID: 352101005


2011/05/27 22:27:50

HW type: HW_rev_DSM_TOYOTA_G2



UP time: 0 days 00 hours 46 minutes 17 seconds



Core 0 post mortem data :


==============OSA=================


Core traceback 0x0014430C 0x0027F624 0x0027F6B0 0x00128EC0 0x0000146C 0x0037AC10 0x00001610 0x002D9860


Thread statistics


THREAD State Th_id Priority St size Unused Run cnt Preemtion thresh Time slice Resumptions Suspensions Solicited preemps Interrupt preemps Priority invers Time slices Relinquishes Timeouts Wait aborts DTCM alloc DTCM free HEAP alloc HEAP free Shared alloc Shared free


IPCTASK semaphore_susp 1 1 8188 7084 875175 1 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002F14 0x0012B820 0x00164EC0

LOGGER suspended 2 18 8188 8112 0 18 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

CFGMGR queue_susp 3 16 8188 7908 85 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x0001188C 0x0012B454 0x00001EC0 0x00273DE0 0x00164EC0

PM suspended 4 29 8188 8112 0 29 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

Dbs Task suspended 5 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

RTT suspended 6 16 8188 8112 0 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

FM queue_susp 7 8 8188 7372 2205740 8 10 0 0 0 0 0 0 0 0 0 0 0 2618576 0 0 0 Traceback 0x0001188C 0x0012B454 0x00001EC0 0x00228990 0x00164EC0

FM_HISR semaphore_susp 8 5 8188 7904 545581 5 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

MAC suspended 9 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

CDMA suspended 10 10 8188 8112 0 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

RFS suspended 11 8 8188 8112 0 8 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

RFS_HISR suspended 12 5 8188 8112 0 5 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

WLD ready 13 16 8188 7684 751290 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x0014430C 0x0027F624 0x0027F6B0 0x00128EC0 0x0000146C 0x0037AC10 0x00001610 0x002D9860

WLD_PHY queue_susp 14 10 8188 6452 1465273 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x0001188C 0x0012B454 0x00001EC0 0x001CFCA8 0x00164EC0

WLD_URG queue_susp 15 1 8188 7204 1784644 1 10 0 0 0 0 0 0 0 0 0 2088 0 2409480 0 0 0 Traceback 0x0001188C 0x0012B454 0x00001EC0 0x001D047C 0x00164EC0

DSP_HISR semaphore_susp 16 8 8188 7876 549689 8 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

WLD_HISR semaphore_susp 17 13 8188 7904 574694 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

PHY_HISR semaphore_susp 18 8 8188 7904 545444 8 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

FS_HISR semaphore_susp 19 1 8188 7904 550432 1 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

RXP_HISR semaphore_susp 20 1 8188 7908 411188 1 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

WLD_HISR_fch_map semaphore_susp 21 1 8188 8068 1 1 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x000034E8 0x00002C30 0x00164EC0

RF_SA queue_susp 22 24 8188 7776 1 24 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x0001188C 0x0012B454 0x00001EC0 0x002A8398 0x00164EC0

ETH suspended 23 10 8188 8112 0 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

ETH_HISR suspended 24 8 8188 8112 0 8 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

MNG suspended 25 10 8188 8112 0 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

TEN suspended 26 8 8188 8112 0 8 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

Scheduler Task suspended 27 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

SCH_URG suspended 28 5 8188 8112 0 5 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

SCH_TUP suspended 29 2 8188 8112 0 2 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

SCH_TMR suspended 30 2 8188 8112 0 2 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

Beam Former suspended 31 16 8188 8112 0 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

RA Task suspended 32 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

LPT ready 33 31 8188 7948 280806 31 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x0036080C 0x00164EC0

SCRIPT suspended 34 21 8188 8112 0 21 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

CLI suspended 35 21 8188 8112 0 21 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

CLI_MCOR queue_susp 36 21 8188 7924 6 21 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x0001188C 0x0012B454 0x00001EC0 0x0020F928 0x00164EC0

BH suspended 37 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

R6 suspended 38 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

BHD1 suspended 39 13 8188 8112 0 13 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

LUT suspended 40 16 8188 8112 0 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

DAN suspended 41 16 8188 8112 0 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

R6Proxy suspended 42 10 8188 8112 0 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

PARSE suspended 43 16 8188 8112 0 16 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

IP 0 0 0 Trac a 0 0 0 0 0 0 0 0 1SM0 _ 0 4EA4

IP 0 0 0 Trac a D08 0 271 0 0 0 0 0 0 0 0 0 0 Traceback 0x00164EA4

DAN suspended 41 16 8188 8112 0 65a_70 9 0 47 0 0 T94

DAN suspended 0 0 0 0 0 0 0 0 46

IP 0 0 986u2 ue_susp 0 8188 8112 0 5 0 0 3

working with support right now,

they have requested a cnut capture of cmm.

will keep the forum posted…

Do you Open case in Moto. I look for me Ap’s and see One base station i have 4 ap’s and one reset

Wanted to follow up with everyone about this case,

after repeated e-mails to them with my crash reports, sometime 3 a day, moto techs
informed me that my AP had an old style circuit board and I need to swap ap.

Put a new ap in and is working so far with no problems,…
Its been over a month and I have not received my RMA’ed AP yet.

Starting to have this exact problem on another AP on a different tower, I’ll be submitting this again to Moto shortly

To recap: The AP’s are crashing several times a day, they come back on their own in 30 seconds, however,
users are experiencing intermittent connectivity, dropping out loosing game sessions, netflix sessions, etc.
Sometimes the users have to give their cpe a physical reboot to get it working again after connection loss…

To set up a crash report on your ap, just enter you e-mail address along with your mail server, no user/pass required,
It will send you the report. Just hit send now to test it.

Good luck reading it. It consists of specialize coding like above post…

Hi cmackay!

Can I ask how long ago you bought these AP’s. Buy chance did you buy them used?

Just fishing :slight_smile:

Jay

jaystewart@giantcomm.net

They where bought “new” about 14 months ago.

They have been through every fw upgrade since before layer2 addition.

currently using e2.2 and cpe 7.13.

I know there is a e2.2.1, but release notes say nothing that pertains to my issue.
It just fixes the setting bug for the center frequency in the ap gui.

I also want to iterate that I did shut off the extended range feature before I upgraded to
e2.2 per release notes.

I wonder if there is still some underlying bug pertaining to that…

But still getting crash reports at random times, 4 since yesterday, some two hours apart, some 8 hours apart…