Yes, 14.1.1 will talk to 13.2.1. 14.1.1 should hit the website with official release by tomorrow. Will take a look at that forum post and answer over there.
Thanks! -Aaron From: Af <[email protected]<mailto:[email protected]>> on behalf of George Skorup <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Sunday, November 22, 2015 at 8:51 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [AFMUG] 450 SM corrupt flash? Cool. So not a hardware issue. In regards to 14.1.1, please see my post here: http://community.cambiumnetworks.com/t5/PMP-Beta/Beta-System-Software-14-1-1-Build-8-is-now-available/m-p/46592#U46592 Looks like build 8 isn't adding 3652.5 and 3697.5 default frequencies on 3.6 radios. And no, I haven't moved beyond 13.2.1 on the 450 network. So if I upgrade this SM to 14.1.1, will it register to a 13.2.1 AP? And the other way around, how about 13.2.1 SMs on 14.1.1 APs? There's always that handful of customers that power off their radios when they're not using it. On 11/22/2015 1:45 AM, Aaron Schneider wrote: Hi George - This is a bug where the event log gets corrupt and kind of locks itself in place. If you load the latest 14.1.1 open beta, it will recover the event log and also has a fix so that any future crash logs won’t be able to lead to this problem. Unfortunately there is no way for you to get this back without loading the new SW. You can load the 14.1.1 image to recover it and then downgrade it if you aren’t ready to try 14.1.1 yet, but then you’ll be exposed to seeing this crash log issue again until you upgrade. We are planning for 14.1.1 to be fully released on Tuesday, but the open beta load up there now will get you past this problem. Regards, -Aaron From: Af <<mailto:[email protected]>[email protected]<mailto:[email protected]>> on behalf of George Skorup <[email protected]<mailto:[email protected]>> Reply-To: "<mailto:[email protected]>[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Saturday, November 21, 2015 at 10:38 PM To: "<mailto:[email protected]>[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [AFMUG] 450 SM corrupt flash? I should add that the license key info and all of the config is intact. On 11/21/2015 10:36 PM, George Skorup wrote: Had to go out and power-cycle a 450 SM at a micro-POP tonight. I've seen this once before, but a reboot fixed it. This one is a bit different though. It appeared to be crashed and multiple power-cycles didn't clear this garbage out of the event log and if I try to clear it, I get "Unsaved changes and reboot required" in red at the top of the pages. Any other config changes causes the same thing to happen. I had to go to unit settings and click undo unit-wide saved changes. At least it's working for now. Anyone else seen this? Is there any way to fix it? K������� 16 ( 0%) 0 0 0 0 (12284/ 6%/29%) Suspend 0x8001bd4 COMM������� 17 ( 0%) 0 0 0 0 (12284/ 2%/31%) Ready 0x8001bd4 EAPP������� 19 ( 0%) 0 0 0 0 (12284/ 2%/15%) Ready 0x8001bd4 VLAN������� 20 ( 0%) 0 0 0 0 (12284/ 2%/12%) PendEvFlgGrp 0x8001bd4 ARPT������� 21 ( 0%) 0 0 0 0 (12284/ 2%/14%) PendEvFlgGrp 0x8001bd4 APPT������� 22 ( 0%) 0 0 0 0 (12284/ 2%/ 9%) PendEvFlgGrp 0x8001bd4 ctic������� 23 ( 0%) 0 0 0 0 (12284/ 2%/14%) Ready 0x8001bd4 Inet������� 24 ( 0%) 0 0 0 0 (12284/ 2%/24%) Suspend 0x8001bd4 BDMT������� 27 ( 0%) 0 0 0 0 (12284/ 2%/12%) Ready 0x8001bd4 BDQT������� 28 ( 0%) 0 0 0 0 (12284/ 2%/15%) Ready 0x8001bd4 FECT������� 29 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) Suspend 0x8001bd4 AUTH������� 31 ( 0%) 0 0 0 0 (12284/ 3%/27%) PendEvFlgGrp 0x8001bd4 SNMP������� 32 ( 0%) 0 0 0 0 (12284/ 3%/40%) Suspend 0x8001bd4 teln������� 34 ( 0%) 0 0 0 0 (12284/ 6%/29%) Suspend 0x8001bd4 TEL1������� 35 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) Suspend 0x8001bd4 TEL2������� 36 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) Suspend 0x8001bd4 TEL3������� 37 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) Suspend 0x8001bd4 TEL4������� 38 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) Suspend 0x8001bd4 FTPs������� 39 ( 0%) 0 0 0 0 (12284/ 7%/31%) Suspend 0x8001bd4 ROOT������� 46 ( 0%) 0 0 0 0 (12284/ 2%/40%) Suspend 0x8001bd4 UPDM������� 47 ( 0%) 0 0 0 0 (12284/ 2%/11%) PendEvFlgGrp 0x8001bd4 UPDT������� 48 ( 0%) 0 0 0 0 (12284/ 2%/ 9%) PendEvFlgGrp 0x8001bd4 HTTP������� 50 ( 0%) 0 0 0 0 (12284/ 7%/45%) Suspend 0x8001bd4 PROX������� 51 ( 0%) 0 0 0 0 (12284/ 7%/31%) Suspend 0x8001bd4 TFT0������� 53 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) PendQ 0x8001bd4 nvrm������� 55 ( 0%) 0 0 0 0 (12284/ 2%/ 9%) PendEvFlgGrp 0x8001bd4 PING������� 56 ( 0%) 0 0 0 0 (12284/ 2%/ 8%) Suspend 0x8001bd4 LLDT������� 57 ( 0%) 0 0 0 0 (12284/ 2%/18%) Ready 0x8001bd4 STAT������� 60 ( 0%) 0 0 0 0 ( 8192/ 3%/17%) Ready 0x8001bd4 IDLE������� 61 ( 0%) 0 0 0 0 ( 8192/ 3%/20%) Ready 0x80019b4 <more stuff> Task DIAG������� - Priority 10 <more stuff.. DIAG output?>
