cancel
Showing results for 
Search instead for 
Did you mean: 

3.3 to 3.5 kills radios?

Contributor

3.3 to 3.5 kills radios?

What's the  deal with this?  I've killed 4 modules now and we're going to need to remove  them from the tower to find out what went wrong.

 

Cambium is a frustrating company to root for.

16 REPLIES
Valued Contributor

Re: 3.3 to 3.5 kills radios?

Does your switch have a watch dog pinging them ? They don't respond for a while updating and that certainly will cause a problem.

We upgraded about 200 aps to 3.5 without an issue, mix of 3.3 and 2.6.2.1


Contributor

Re: 3.3 to 3.5 kills radios?

These are epmp 2000 radios with smart antennas if that makes a difference.  The updates were done via gui since I can't seem to make  cnut work with these.

 

I also tried upgrading the force 200 at my house which is currently on 3.4, but I get a message telling me to reboot first.  If I reboot first and try again it repeats the same message telling me to reboot.

 

 

Any ideas?  I'm scared to death to upgrade anything else on this network and may be stuck with old firmware forever.  The ubiquitis are looking pretty good again.  I'm not even gonna try that elevate crap, I'll just keep both AP's up until one beats the other.  So far it's a tie I guess and when compared to UBNT that is not a good thing.

Contributor

Re: 3.3 to 3.5 kills radios?

Watchdog was turned off.  They complete the update and ask for a reboot, they never return after the reboot.  The switch is still showing power being drawn, but it's not pingable by it's IP or the default IP.

 

The first 3 happened the other day after a tower got destroyed by lightning.  We installed 3 new radios which came with 3.3 out of the box.  I ran an update on all 3 and killed them.  We then took 3 other new ones out there and left them on 3.3.  Today I decided to try one that had no customers on it and same thing.

 

IDK.  Too close to Friday to deal with this nonsense.  This should be basic stuff that just works.

Contributor

Re: 3.3 to 3.5 kills radios?

More info in case it helps Cambium.  I can arp ping it and it's responding on 169.254.1.1, along with every other ap nearby.  So it's kinda alive.  Tomorrow I'll have someone go defualt the thing and see what happens.  I'll try the same on the first 3 that went down as well.  Fun stuff.

Contributor

Re: 3.3 to 3.5 kills radios?

I'm also noticing in my neighbors list from an MT device that the modules with 3.3 are showing version  2.6.32.27 whereas the devices that upgraded successfully are showing 3.5.0.  Is it possible these modules are lying to me about which version is actually installed?  Again these came right out of the box this way.  Maybe I'm jumping to many versions on these?

Super Contributor

Re: 3.3 to 3.5 kills radios?

Are those radios connected to a Netonix switch?  If so, is STP enabled on the AP?  I'll explain if your answers are yes.

Contributor

Re: 3.3 to 3.5 kills radios?

Yes and yes.

Highlighted
Super Contributor

Re: 3.3 to 3.5 kills radios?

Take a read through this if you have not already:

 

http://community.cambiumnetworks.com/t5/ePMP-2000-and-1000/Lost-access-to-2000-AP-during-upgrade-to-...

 

I am getting convinced there is an issue with the 2000 AP hardware, firmware 3.5, Netonix switches when the AP has STP turned on. I have three 2000 APs and all three of them I lost control of on the Ethernet side when I tried to upgrade to 3.5.  All three are in Netonix switches and all three use STP.  As a result, I have not upgraded those APs.

Contributor

Re: 3.3 to 3.5 kills radios?

Interesting.  

 

I havnt read through the entire thing yet, but decided to turn off STP in the netonix and then update the radios.  I stepped them first to 3.4.1 and then to 3.5 and all updated fine.  I then turned STP back on in the netonix and lost contact with all of them until turning STP off again in the netonix.  I then turned STP off in the radios and on in the netonix and all is well.

 

Weird, I can live without stp in the radios if thats the fix.

 

Thanks for the info!