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 <[email protected]> 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 Statistics[image: > http://10.10.10.246/_min.gif?mac_esn=0a003ea081e2] > > Number of Registration Grant Failures : > > 465 > > Most Recent Registration Failure List[image: > http://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 > > >
