Sounds like the cold might be an issue. We have several APs on 13.4 with
200+ days. A few have 264 days.
It never really gets "cold" here. Mid 30s is about the most extreme
we've seen this winter.
bp
<part15sbs{at}gmail{dot}com>
On 3/28/2016 1:02 PM, George Skorup wrote:
You'll need to reboot the AP. I'm actually really surprised that your
AP has been running on 13.4 for 200+ days. I figured you'd have seen
some watchdog resets.
Anyway.. we see this somewhat frequently. Sometimes we get SMs failing
to register due to "out of range" when clearly they are within range.
Same symptoms. They continuously try to register to the same AP. I
suspect that they're getting through the registration process cleanly,
but whatever is screwed up in memory on the AP causes the session to
fail. Or never fully establish from the AP's perspective. So the SM
never locks out the sector and attempts to register to another. Other
weird things happen too. Reboot AP, works fine again. Until it screws
up again. We had a ton more issues when it was colder outside.
Aaron posted a couple weeks ago about the FPGA memory timing problem.
As he said, you can't predict what's going to happen when your memory
controller and contents are potentially unstable.
On 3/28/2016 2:32 PM, Sean Heskett wrote:
in my opinion 13.2.1 and 14.2.1(Build 8) are the only "stable"
versions for the 450APs. 14.1.2(build 8) is still beta tho.
2 cents
-sean
On Mon, Mar 28, 2016 at 11:51 AM, Chris Wright <ch...@velociter.net
<mailto:ch...@velociter.net>> wrote:
I have a PMP450 AP on 13.4 up for 228 days. The last successful
CPE reconnect was six days ago. Now we’re noticing that CPE’s who
disconnect are unable to reconnect to that AP at all.
Furthermore, in spite of being able to see alternate APs on
secondary color codes, the CPEs seem intent on connecting to the
problem AP. Here’s what my SM Registration Failures page looks
like currently:
Registration Failures
Statisticshttp://10.10.10.246/_min.gif?mac_esn=0a003ea081e2
Number of Registration Grant Failures :
465
Most Recent Registration Failure
Listhttp://10.10.10.246/_min.gif?mac_esn=0a003ea081e2
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
10:42:45 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
10:40:10 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
10:35:09 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
10:31:26 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
10:23:52 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
10:23:14 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
10:21:49 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
10:10:46 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
10:02:56 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
10:01:38 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
09:58:21 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
09:54:27 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
09:51:02 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
09:49:30 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
09:40:01 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-a8-67 RegReq no time ref 03/28/2016 :
09:27:56 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
09:24:59 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
09:23:11 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
09:19:03 PDT : Status : 20 Flag : 0
*MAC : *0a-00-3e-a1-95-aa RegReq no time ref 03/28/2016 :
09:13:24 PDT : Status : 20 Flag : 0
I’d rather not reboot the AP as I’m fearful it could make the
problem worse for a few dozen more people. Anyone seen this before?
Chris Wright
Network Administrator
Velociter Wireless
209-838-1221 x115 <tel:209-838-1221%20x115>
