Hi Ken - Has this happened a lot on this device? This error is a result of setting the Tx frequency not "taking", and the reboot is taken to let it try again with a re-iniatialization of the ADI chip. So I'm not sure this is the JV version of that issue, but maybe intramurals or parks and rec league of the same sport. I see the MAC from the log, we'll take a look at that timeline and see if it's from the batch.
If this happens once, I'd ignore it as the radio did the reboot to recover. If it is in the log numerous times, then I would worry. I would suggest opening a ticket with support just so it can be tracked and add to the historical data. I can let them know something like this is coming and get them started in the meantime. And George, I really don't have a filter, but people are always watching, so I do get paged if I'm not paying attention. :) -Aaron -----Original Message----- From: Af [mailto:[email protected]] On Behalf Of Ken Hohhof Sent: Wednesday, April 13, 2016 3:58 PM To: [email protected] Subject: Re: [AFMUG] 450 "silent watchdog reset" question I hope this isn't the junior varsity version of the ADI Communication Failure problem. No log entries for that error, but the SM is from the time we saw those. -----Original Message----- From: George Skorup Sent: Wednesday, April 13, 2016 3:52 PM To: [email protected] Subject: Re: [AFMUG] 450 "silent watchdog reset" question Assuming the scanning caused it, then it wouldn't be a re-reg since that doesn't trigger a full scan. You could look at the session log for that SM and see if that shows any out-of-service (OOS) and/or reg attempts. Maybe Aaron can tell you exactly what that means. Bad frequency offset at that temperature or something. Lets see if a "paging Aaron Schneider" triggers his filter........ On 4/13/2016 2:08 PM, Ken Hohhof wrote: > Yes, I normally turn off 5 MHz and the 2.5 MHz raster (otherwise it > would take forever to register), but I leave both 5.4 and 5.7 > frequencies checked just in case. > > Your scenario assumes it had to rereg, correct? Not sure what caused > that. > > > -----Original Message----- From: George Skorup > Sent: Wednesday, April 13, 2016 2:02 PM > To: [email protected] > Subject: Re: [AFMUG] 450 "silent watchdog reset" question > > Could be it pooped while scanning that frequency. Do you have the 5.4 > band scanning enabled on that SM? > > On 4/13/2016 1:53 PM, Ken Hohhof wrote: >> 04/13/2016 : 11:09:46 UTC : :Reset due to error setting transmit >> frequency 5540 at temperature 24 C >> 04/13/2016 : 11:10:46 UTC : :Forced reset; >> 04/13/2016 : 11:10:46 UTC : >> ******System Startup****** >> System Reset Exception -- Watchdog Reset Cur ExtInt 0 Max ExtInt 0 >> Cur DecInt 0 Max DecInt 0 Cur Sync 0 Max Sync 0 Cur LED 2 Max LED 1 >> Cur WDOG >> 0 Max WDOG 1 Cur EthXcvr 0 Max EthXcvr 1 Cur FEC 0 Max FEC 0 Cur FPGA >> 0 Max FPGA 2572 Cur FrmLoc 0 Max FrmLoc 0 Cur WatchDog 33 Max >> WatchDog 33 RTMLogStats 0 AAState 0 Software Version : CANOPY 13.2 >> SM-DES Board Type : P11 Device Setting : 5.4/5.7GHz MIMO OFDM - >> Subscriber Module - 0a-00-3e-b2-04-4e FPGA Version : 081514 FPGA >> Features : DES, Sched; >> >> >> Note that the AP is on 5835 MHz, so I don't know why it says 5540. >> >> >> >> -----Original Message----- From: George Skorup >> Sent: Wednesday, April 13, 2016 1:08 PM >> To: [email protected] >> Subject: Re: [AFMUG] 450 "silent watchdog reset" question >> >> It's not the same problem. The 450 AP and SM are different FPGAs. I >> do see stack dumps and watchdog resets on SMs sometimes. I suspect >> that's radios on crappy power/no UPS. Although, I have seen stuck VCs >> followed by a dump and reset a few times. >> >> Also, Aaron did say that the 450 hardware doesn't have a reboot >> mechanism. So when you "reboot" a radio, they kill off stuff and let >> the watchdog timer expire which then resets the board. So that's why >> you see watchdog reset - user initiated reset, reboot from webpage or >> whatever. >> >> On 4/13/2016 12:01 PM, Ken Hohhof wrote: >>> Is this just on APs, or also on SMs? >>> >> >> > >
