[Cambium-users] 15.0.2.1 - a bad bug still exists

2017-01-31 Thread George Skorup
Remember back around 14.1.2 betas where an SM wouldn't see a primary AP and instead would register to the secondary? I saw hints that this was still a problem in 14.1.2 official and 14.2.1. It would pop up infrequently and rebooting the SM would fix it. Here we are today on 15.0.2/15.0.2.1 and

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread George Skorup
Just FYI, I took a couple APs running in DFS land from 2.6.2.1 to 3.2.2. Most of them have never seen a radar hit. One saw radar less than 10 minutes after the upgrade. I moved the primary frequency 5MHz and it has been fine since. Another sees radar every few hours since this morning no matter

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Matt Reeser
Yea, that's part of the SNMP bug that was introduced into 3.2.1. I had to power cycle a few that were not responding. Matt Reeser Network Technician Verso Networks 720.329.0614 On Jan 31, 2017 8:54 AM, "Chadwick Wachs" wrote: > I tried rebooting a few times. Couldn't. Had to power cycle the AP

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Josh Luthman
You can't actually reboot from the GUI/SSH when the snmpd bug happens. It sort of looks like it, but it doesn't actually do it. You can reboot via cnMaestro...and obviously a power cycle. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Jan

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Chadwick Wachs
I tried rebooting a few times. Couldn't. Had to power cycle the AP to get it to upgrade. Didn't try to power cycle the SM. On Jan 31, 2017 8:04 AM, "Sakid Ahmed via Cambium-users" < cambium-users@wispa.org> wrote: > Hi guys, > > > > It seems that this might be an artifact of the SNMPd issue from

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Matt Reeser
I upgraded using the CNS server since we have not fully moved over to cnMaestro. It was fine. Matt Reeser Network Technician Verso Networks On Jan 31, 2017 8:04 AM, "Sakid Ahmed via Cambium-users" < cambium-users@wispa.org> wrote: Hi guys, It seems that this might be an artifact of the SNMP

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Sakid Ahmed via Cambium-users
Hi guys, It seems that this might be an artifact of the SNMPd issue from the earlier release. Once you get to this release, the issue goes away. Now, for the upgrade challenge we are recommending a reboot of the radio after the first attempt has failed and then doing a second attempt. Apologie

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Darin Steffl
Also tried last night to upgrade 15 SM's on one sector and they also fail immediately in cnMaestro. Not a good sign. Hope they get this fixed and more solid. On Tue, Jan 31, 2017 at 7:56 AM, Chadwick Wachs wrote: > Unable to upgrade any SMs or APs from 3.2.1 to 3.2.2 via cnMaestro. Fails > immed

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread Chadwick Wachs
Unable to upgrade any SMs or APs from 3.2.1 to 3.2.2 via cnMaestro. Fails immediately. We did about 20 if ours manually as a test. On Jan 31, 2017 6:07 AM, "CBB - Jay Fuller" wrote: > > hm, nothing in the release notes about db readings from remote subs. in > our 3.2 they were waaay off (6-7 db

Re: [Cambium-users] ePMP 3.2.2

2017-01-31 Thread CBB - Jay Fuller
hm, nothing in the release notes about db readings from remote subs. in our 3.2 they were waaay off (6-7 db) we never did 3.2.1, may try this - happy to hear the snmp (and reboot and lots of other things) bug is fixed curious to read other reports... - Original Message - From: G