Hey Folks, I think I may have discovered an issue today, or perhaps I've discovered how a feature works... perhaps you can tell me.
Upon logging into an active 2.4 Ghz PMP450 AP of ours, I attempted to generate an XML file on the Session Status tab... the webpage kind've just stalled, and nothing really happened. I refreshed the webpage, and was greeted with a login, only to realize the AP had rebooted. Yikes!
So, I tested it on our test-bench AP, and I am successfully able to replicate this every time I try.
Can anyone tell me if this is supposed to happen? If it's not, then, I think I've caught a little glitch in the matrix.
Please send engineering.cgi file to my email chitrang dot srivastava at cambiumnetworks
Is there an update on when the Radius issue (CPY-15643) fix will be released? If there is a link to the original post/issue would it be possible to provide that too?
We upgraded an AP from 15.1.5 to 16.0.1 last week. Around noon today we "uncapped" two SMs in our radius server and rebooted the SMs via cnMaestro API. On the new firmware, the SMs hang on the loading page after reboot (see attached image). I tried this test on an SM on firmware version 15.1.5 on a different AP (also on 15.1.5) and it worked flawlessly. I can see all three SMs authenticate in the radius server (and no changes have been made there other than removing the rate cap.
After about 2 hours, one of the SMs finally attached after 16 reauths. The event log shows nothing unusual. The other SM is still hanging after 25 reauths. I'm going to see if that customer can manually power cycle the SM tonight.
Initially, this appears to be related to the 16.0.1 firmware because it is working in 15.1.5. Has anyone in the community or at Cambium seen anything like this? If so, is a fix expected anytime soon? We were hoping to upgrade our APs to the 16.0.1 code rev so we can prepare for the upcoming 16.1, but at the moment this is a show stopper for AP firmware upgrades.
We upgraded an AP from 15.1.5 to 16.0.1 last week. Around noon today we "uncapped" two SMs in our radius server and rebooted the SMs via cnMaestro API. On the new firmware, the SMs hang on the loading page after reboot (see attached image). I tried this test on an SM on firmware version 15.1.5 on a different AP (also on 15.1.5) and it worked flawlessly. I can see all three SMs authenticate in the radius server (and no changes have been made there other than removing the rate cap.
After about 2 hours, one of the SMs finally attached after 16 reauths. The event log shows nothing unusual. The other SM is still hanging after 25 reauths. I'm going to see if that customer can manually power cycle the SM tonight.
Initially, this appears to be related to the 16.0.1 firmware because it is working in 15.1.5. Has anyone in the community or at Cambium seen anything like this? If so, is a fix expected anytime soon? We were hoping to upgrade our APs to the 16.0.1 code rev so we can prepare for the upcoming 16.1, but at the moment this is a show stopper for AP firmware upgrades.
Please email me the engineering.cgi from the AP to balaji.grandhi@cambiumnetworks.com. We can take a look. Also, from the radius server logs, do you know why the autentication is failing?
Hi Balagi, the radius auth is a success in the radius server. The SM itself loses connection to AP.
Yesterday afternoon we put a cap back on the SM and rebooted. That remedied the problem. So the SM has an issue if there is no rate limit assigned.
Would you like me to send in the engineering files from the AP and 2 SMs now that I can reach the SM?
Also, we might be willing to try the new Beta release if Cambium thinks it could fix the above issue. Below is the thread where Matt talks about needing Beta customers for a Radius fix:
Hi Balagi, the radius auth is a success in the radius server. The SM itself loses connection to AP.
Yesterday afternoon we put a cap back on the SM and rebooted. That remedied the problem. So the SM has an issue if there is no rate limit assigned.
Would you like me to send in the engineering files from the AP and 2 SMs now that I can reach the SM?
Also, we might be willing to try the new Beta release if Cambium thinks it could fix the above issue. Below is the thread where Matt talks about needing Beta customers for a Radius fix: