The SNMP reset lines result from a script which sends a reboot to radios under certain conditions, but this script does not correlate to the resetting (that is, it happened before the script was deployed, and on APs where the script is deployed, it has happened on just a tiny handful of radios which hadn't been rebooted by that script in over a week). The reboot command is just an snmpset to the .1.3.6.1.4.1.161.19.3.3.3.2.0 OID aimed at the SM through the AP. If that is triggering the resets, then there is a bigger problem than we realized!
-----Original Message----- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Larry Smith Sent: Thursday, September 07, 2017 12:49 PM To: af@afmug.com Subject: Re: [AFMUG] PMP450 SMs resetting to Factory Defaults? Anyone? Interesting, do not see any of these sort of errors on our 450's. Also interesting are the SNMP lines: > 09/07/2017 : 01:26:25 CST : :SNMP user; user=snmp; Reboot from SNMP; > 09/07/2017 : 01:26:27 CST : :SNMP user; user=snmp; Reboot from SNMP; > 09/07/2017 : 01:26:27 CST : :Forced reset; almost appears that some monitoring equipment is rebooting the SM -- Larry Smith lesm...@ecsis.net On Thu September 7 2017 11:17, Darren Shea wrote: > Just wondering, if this is a problem which only bedevils me, or if > other people are seeing it: > > > > PMP450 SMs, running 15.0 or later f/w (it's a question right now > whether the AP f/w is related to this, but it seems that the APs are > usually running 13.2 f/w) > > > > The symptom is the SM throws a bunch of "Deleting a timer since it was > active" errors, then some other errors, then it resets to factory > defaults and reboots (see below for typical Event log snippet). > Sometimes, the radio loses calibration data. Because we run our > configurations as close as possible to default in the first place, we > can typically access the radio via ICC and reconfigure it > appropriately without a truck. However, and this is a huge deal, some > of these radios that had 10M keys are now reverting to 4M keys! This is going > to cause us major headaches. > > > > I have opened lines of communication with Cambium about this, but they > are giving me their standard "we haven't heard about this" response > which is always their default up until they admit it's a problem and > start to resolve it. Have any of you encountered these issues? > > > > Typical Event Log snippet: > > > 09/07/2017 : 01:26:19 CST : :Deleting a timer since it was active (T), > TimerId=0x5fa0c0 (0xac325c), TimerEvent=0x8, TimerTaskId=48, > CurrentTask=48 > > > 09/07/2017 : 01:26:21 CST : :Deleting a timer since it was active (T), > TimerId=0x5fa0c0 (0xac325c), TimerEvent=0x8, TimerTaskId=48, > CurrentTask=48 > > > 09/07/2017 : 01:26:23 CST : :Deleting a timer since it was active (T), > TimerId=0x5fa0c0 (0xac325c), TimerEvent=0x8, TimerTaskId=48, > CurrentTask=48 > > > 09/07/2017 : 01:26:25 CST : :SNMP user; user=snmp; Reboot from SNMP; > > > 09/07/2017 : 01:26:25 CST : :Deleting a timer since it was active (T), > TimerId=0x5fa0c0 (0xac325c), TimerEvent=0x8, TimerTaskId=48, > CurrentTask=48 > > > 09/07/2017 : 01:26:27 CST : :SNMP user; user=snmp; Reboot from SNMP; > > > 09/07/2017 : 01:26:27 CST : :Forced reset; > > > 09/07/2017 : 01:26:27 CST : :Deleting a timer since it was active (T), > TimerId=0x5fa0c0 (0xac325c), TimerEvent=0x8, TimerTaskId=48, > CurrentTask=48 > > > 01/01/2016 : 00:00:00 UTC : : > > > 01/01/1970 : 00:00:00 UTC : :CalParams[46], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[47], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[58], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[59], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[60], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[61], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[62], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : :CalParams[63], updating FPM, CalParams > and FPM mismatch! > > > 01/01/1970 : 00:00:00 UTC : File src/cal_params.c : Li > > > 01/01/2016 : 00:00:00 UTC : > > ******SYSTEM STARTUP****** > > > System Reset Exception -- Watchdog Reset > > > Software Version : CANOPY 15.0.2 SM-DES > > > Board Type : P11 > > > Boot Bank : 0 > > > Board Temperature : 38 C / 101 F > > > Device Setting : 5.4/5.7GHz MIMO OFDM - Subscriber Module - > 0a-00-3e-bx-yy-zz No valid accounts configured. Using default user > account > > > FPGA Version : 061716 > > > FPGA Features : DES, Sched; > > 01/01/2016 : 00:00:00 UTC : > :CalParams[46,47,58,59,60,61,62,63,64,65,66,67,68,72,76,77], updated > FPM, > > CalParams and FPM mismatch! > > > FeatureKey mismatch for FKey[1] > > > 12/31/2015 : 18:03:37 CST : :Timezone set to CST; > > > 09/07/2017 : 01:30:24 CST : :Time Set
