ePMP Release 3.4.1 is now available and can be downloaded from Cambium Networks Software Download website located at:
We had some GPS SYNC issues with the pucks after going 3.3 involving SNMP crashes? Long story short, I found a thread that had a beta release for 3.3 that appeared to resolve it but that beta file is gone. I don't see that particular issue listed in the pdf file with this release or the 3.4 pdf- was that fixed with this update as well?
Thank you!
Hi,
Could you please tell a bit more regarding issue you had with GPS sync?
Thank you.
The reboots problem was not solved. Tomorrow I will raise some pics where some SM in less than half an hour were restarted 5 times. :/ :(
best regards
chapex
Force 200 after change firmware the google browser comes to validation and does not enter. The Firefox browser enters and validates well.
1 Like
@rfcom wrote:
Force 200 after change firmware the google browser comes to validation and does not enter. The Firefox browser enters and validates well.
Hi,
Please clear cookies and cache in your Chrome browser to avoid issues with log in procedure.
Thank you.
1 Like
@chapex wrote:
The reboots problem was not solved. Tomorrow I will raise some pics where some SM in less than half an hour were restarted 5 times. :/ :(
best regards
chapex
Hi,
I can assume your issue can be not the same with issue fixed in 3.4.1 Release.
Did you check "debug crashlog" on affected devices?
Are these devices Force180/200 devices only?
Thank you.
I noticed that the neighbor discovery from our Mikrotiks now shows version 3.4.1 and device types like "5G Force 200 (FCC)" instead of 'linux' and the kernel version. Thanks! Much more useful that way.
I rolled out the update to four SMs on our network, two 180s and two 200s that had all exhibited reboot madness on V3.3. (we rolled out 3.3 network-wide back when, then reverted to 3.2.2 network-wide when the reboot problems' ties to 3.3 became apparent)
So far looks like two of them have made it 24 hrs with no reboots, but two have rebooted 5+ times in that same 24 hrs. No judgement, no complaint, just a preliminary observation. Right now looks like one of each radio type (testing on two of each) is back to frequent reboots.
j
PS - I also noticed that the IPv6 support still seems unable to utilize a gateway to reach anything outside the local subnet. But given that the release notes don't say that's fixed (though they don't even indicate it as a known problem either!) I wasn't too surprised by that.
In a large portion of the cambium network we have the symptoms of constant restarts, about 500 units in constant failure. In all cases we make a correct earthing, respecting the electrical regulations, so we can dismiss this as the source of the problem. We have updated a large portion to 3.4.1v, including subscriber modules and access points, to avoid that the origin of the reboots is some fault in the allocation of timeslots / gps, etc.
EDITED: all units are force 180(95%) and force 200 (5%) - All AP are epmp 1000 line (25%) and 2000 +SMA(75%)
@newkirk wrote:
I noticed that the neighbor discovery from our Mikrotiks now shows version 3.4.1 and device types like "5G Force 200 (FCC)" instead of 'linux' and the kernel version. Thanks! Much more useful that way.
I rolled out the update to four SMs on our network, two 180s and two 200s that had all exhibited reboot madness on V3.3. (we rolled out 3.3 network-wide back when, then reverted to 3.2.2 network-wide when the reboot problems' ties to 3.3 became apparent)
So far looks like two of them have made it 24 hrs with no reboots, but two have rebooted 5+ times in that same 24 hrs. No judgement, no complaint, just a preliminary observation. Right now looks like one of each radio type (testing on two of each) is back to frequent reboots.
j
PS - I also noticed that the IPv6 support still seems unable to utilize a gateway to reach anything outside the local subnet. But given that the release notes don't say that's fixed (though they don't even indicate it as a known problem either!) I wasn't too surprised by that.
Hi Joel,
Could you please investigate issue with SMs reboot in depth on your side?
Please check whether crashlog has been saved on affected devices with 3.4.1 Release.
Issue with IPv6 Gateway still persists in 3.4.1 Release and will be fixed in 3.5.
Sorry, we missed to add it to Known Issues, will do this asap.
Thank you.
Effectively clean cookies, clean google chrome history and I was able to login with the new firmware 3.4.1
Dear, I upgraded to 3.4.1 today and does not accept previous or standard (admin) password what can it be?
===========================================
Sorry, I was able to sign in with another browser
@edu wrote:
Dear, I upgraded to 3.4.1 today and does not accept previous or standard (admin) password what can it be?
Hi,
Please try to clear cache and cookies and try to enter password again.
Thanky ou.
2 Likes
I confirm, tried to upgrade to 3.4.1 my Force180 for testing new fw and I've got bad login... then clenaed Mozilla Firefox cache and everything worked perfectly!
Now I'm testing how it works in the next few days.
Best regards,
Paolo
2 Likes
"So far looks like two of them have made it 24 hrs with no reboots, but two have rebooted 5+ times in that same 24 hrs."
Sooo did 3.4.1 fix the reboot problem caused by 3.3 or is it just causing fewer radios to randomly reboot now?
I updated four SMs on our network from 3.2.2 to 3.4.1 last week, specifically picking four that exhibited high reboot activity on 3.3 and 3.4 firmware. Two Force180 and two Force200.
The two Force180s have since rebooted four and eight times.
The two Force200s have rebooted once for one, and 32 times for the other...
Attaching crashlog from the one that rebooted 32 times. (the other three had none)
Note that we've been under assault by lightning storms the past couple weeks, so power brownout/blackout could explain several reboots. (but not 32 times)
j
- ePMP_crashlog1.txt (15.3 KB)
@newkirk wrote:
I updated four SMs on our network from 3.2.2 to 3.4.1 last week, specifically picking four that exhibited high reboot activity on 3.3 and 3.4 firmware. Two Force180 and two Force200.
The two Force180s have since rebooted four and eight times.
The two Force200s have rebooted once for one, and 32 times for the other...
Attaching crashlog from the one that rebooted 32 times. (the other three had none)
Note that we've been under assault by lightning storms the past couple weeks, so power brownout/blackout could explain several reboots. (but not 32 times)
j
Hi Joel,
I've raised internal ticket for your reboot issue with crashlog.
I will update you as soon as we finish with investigation.
Please note that distinguishing mark for initial reboot issue in 3.3 and 3.4 Releases is reboot without crashlog. So it seems that your issue is not the same.
Thank you.
1 Like
@newkirk wrote:
I updated four SMs on our network from 3.2.2 to 3.4.1 last week, specifically picking four that exhibited high reboot activity on 3.3 and 3.4 firmware. Two Force180 and two Force200.
The two Force180s have since rebooted four and eight times.
The two Force200s have rebooted once for one, and 32 times for the other...
Attaching crashlog from the one that rebooted 32 times. (the other three had none)
Note that we've been under assault by lightning storms the past couple weeks, so power brownout/blackout could explain several reboots. (but not 32 times)
j
Hi Joel,
After Call-Trace investigation we can confirm it is HW issue with your Force 200.
Please open ticket with Cambium Support to RMA this particular unit.
Thank you.
@Fedor wrote:
Hi Joel,
After Call-Trace investigation we can confirm it is HW issue with your Force 200.
Please open ticket with Cambium Support to RMA this particular unit.
Thank you.
Unfortunately, as with most of the previous examples that we already replaced for reboot issues, (and discarded) this unit is past warranty.
j
I have upgraded to 3.4.1 on an epmp 1000 gps sync. I have set it to specturm anyalyzer and rebooted. This is all fine. I have then set it to AP mode and rebooted. It stays in spectrum anyalyzer mode. This is not fine. Has anyone else experienced this?
The notification window says the settings were saved successfully and it now requires a reboot. The save button still says applying and will stay that way. I have tried in google chrome and firefox.