Yes, AutoSync + FreeRun and it was stuck in FreeRun despite reporting it had Sync over Power available (from CTM2). And this is 13.2.
BTW, I have seen this previously on 5 GHz APs, but probably on an earlier FW version. From: George Skorup (Cyber Broadcasting) Sent: Sunday, March 08, 2015 2:37 PM To: [email protected] Subject: Re: [AFMUG] SM session log message dictionary? So you had AutoSync + FreeRun and it was stuck in FreeRun? I've seen that on every 3GHz AP that has it enabled (single AP sites). Ended up shutting it off on all of them. But 2.4/5GHz running 13.2/13.2.1 seems to work fine with it enabled. It's just 3GHz with weird, random timing issues. Methinks it has something to do with LBT being in the mix, because other than that, it's the same hardware/FPGA. I wanted to go back to 13.1.3, but losing MIMO-A is not an option now that I have SM links that need it occasionally, a few frequently. Variable multipath doesn't go away even in the winter. BTW, these are a mix of SyncInjectors and Parasitic pipes. No different than 2.4 and 5GHz. On 3/8/2015 9:10 AM, Ken Hohhof wrote: I think I found the cause – one of George’s favorite problems, another AP 10 miles away was on free run despite having sync over power. Problem occurred about every 8 hours. Reboot of the free running AP fixed that. It would still be nice to have a Cambium-ese to English dictionary. From: That One Guy Sent: Saturday, March 07, 2015 10:45 PM To: [email protected] Subject: Re: [AFMUG] SM session log message dictionary? I don't think cambium bought that list from moto which doesn't matter because they didn't have one anyway. I think some coder generated that component, but then died of a caffien overdose before documenting it On Mar 6, 2015 6:34 PM, "Ken Hohhof" <[email protected]> wrote: Are you doing authentication? No. But this is a 3.65 SM if that matters. -----Original Message----- From: George Skorup (Cyber Broadcasting) Sent: Friday, March 06, 2015 6:28 PM To: [email protected] Subject: Re: [AFMUG] SM session log message dictionary? To max error I think means the SM has tried to register with the AP so many times and it failed, so it gives up and starts scanning again. I don't think I've seen SMREGGNTREG before. Are you doing authentication? On 3/6/2015 5:52 PM, Ken Hohhof wrote: Is there a table of Canopy log messages and what they mean in English? I can't find one in the user guide. For example, OOSERVICE and REGISTERED are self explanatory, but what does REGREQTOMAXERR or SMREGGNTREJ mean? The first one sounds like maybe registration request and whatever TOMAXERR means. The second sounds like SM registration grant reject or something along those lines. 03/06/2015 : 21:35:55 UTC : Event: SMSESFAIL, MsgType: REGREQTOMAXERR, NewState: OOSERVICE, Flag 0 03/06/2015 : 21:36:33 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 03/06/2015 : 21:36:33 UTC : Event: SMSESFAIL, MsgType: SMREGGNTREJ, NewState: OOSERVICE, Flag 1 03/06/2015 : 21:37:19 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 03/06/2015 : 21:37:22 UTC : Event: SMSESMSG, MsgType: REGREQTO, NewState: REGISTERING, Flag 0 repeated 1 times 03/06/2015 : 21:37:27 UTC : Event: SMSESFAIL, MsgType: REGREQTOMAXERR, NewState: OOSERVICE, Flag 0 03/06/2015 : 21:38:13 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0 03/06/2015 : 21:38:13 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 21 03/06/2015 : 21:38:13 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0 repeated 2 times
