I don’t think we have seen much difference between CTM, CTM2, SyncInjector, or CMM sites with regard to the reboots, but I can’t say I have tried to correlate it either.
The suggestion from tech support to turn off sync on the towers was stupid enough that we gave up on that conversation. It was obvious we were not going to get anywhere. Mark > On Aug 29, 2015, at 12:34 AM, Ken Hohhof <[email protected]> wrote: > > So I checked some APs on 13.2 and found one with 177 days uptime. Strangely, > it says it is using the internal GPS even though it has power port sync > (CTM-2). Maybe there's something to the idea that it depends on sync method. > > > -----Original Message----- From: George Skorup > Sent: Friday, August 28, 2015 11:00 PM > To: [email protected] > Subject: Re: [AFMUG] Canopy 13.4 Watchdog Reset > > What does FreeRun have to do with it? > > I have a couple 450 test sites on 13.4 and haven't seen any watchdog > resets. Granted, that's only two APs. Definitely still see it on 13.2.1. > It's not a daily thing, but yeah, annoying. > > One thing I'm seeing on the 3.6 450 with 13.2.1 is the APs getting into > a state where they say there's no sync pulse. Then it says receiving > sync, no sync... over and over every few seconds until they are > rebooted. All the while the SyncInjector says nothing is wrong. Tracking > 8+ sats. No increment for the 1PPS Active counter. I understand this had > something to do with the FreeRun stuck issue, which was apparently > resolved with 13.4, but I'm waiting on 13.4.1 so some other issues get > fixed before I can update the entire network. > > Anyway, if I leave the APs alone for a while (say it happens in the > middle of the night while I'm sleeping), they mysteriously return to > normal after anywhere from 3 to 20 minutes. Then if any SM loses > registration (or if I force an SM to rescan), it fails to register for > no reason at all. Reboot the AP, everything works again. I have no > freakin idea what this is about. > > On 8/28/2015 9:54 PM, Mark Radabaugh wrote: >> We have been seeing this across 200+ AP's >> >> It's getting truly annoying. Cambium tech support has helpful suggestions >> like'just put them in free run'. Um.... Thanks for the help, but no. >> >> Mark Radabaugh >> Amplex >> 27800 Lemoyne, Ste F >> Millbury, OH 43447 >> 419-261-5996 >> >>> On Aug 28, 2015, at 4:56 PM, Brian Sullivan <[email protected]> >>> wrote: >>> >>> Last week we rolled out 13.4 to 450 AP's after testing in-house for a >>> while. While running 13.2 we would see an AP here or there reboot on >>> occasion by itself. The only message in the Event Log mentions Watchdog >>> Reset. This is one of the bugs that Cambium noted was fixed in the 13.4 >>> release notes. >>> >>> Since we upgraded the network to 13.4 we are now seeing at least 4 AP's out >>> there rebooting several times per day. On one of these AP's we are also >>> seeing SM's (all 17 registered) reboot along with the AP. The site has UPS >>> backup so I know it's not a power grid problem. I am planning to roll the >>> affected AP's back to 13.2 this evening. >>> >>> Anyone else having Watchdog issues with the 13.4 release? >>> >>> ******System Startup****** >>> System Reset Exception -- Watchdog Reset >>> Software Version : CANOPY 13.4 AP-DES >>> Board Type : P12 >>> Device Setting : 5.7GHz MIMO OFDM - Access Point - 0a-00-3e-a0-08-e5 - >>> 5760.0 MHz - 20.0 MHz - 1/16 - CC 85 - 2.5 ms >>> FPGA Version : 040715 >>> FPGA Features : DES, Sched, US/ETSI; >>> 08/28/2015 : 14:11:42 CST : :Time Set >>> 08/28/2015 : 14:11:58 CST : Acquired sync pulse from Power Port. >>> >>> > >
