We see it on both tpes of radios. We have not confirmed it yet on the older force 110 radios? but for sure on both 180 and 200 units.
has anyone been able to "unbrick" a force 200 radio that possibly failed to load firmware and rebooted during the downgrade. Would a TFTP client possibly work? I have one here at my desk I am going to play around with and see what it is doing. Wish it had a monitor output heheheh..
HI,
TFTP recovery works properly starting 2.6.2 Release.
Thats great but it talks abotu extracting the BIN file. When I use my "extraction software" to find the .bin file in the tar.gz file all it finds is another .tar file? where do we locate the .bin file???? or are you simply renaming the .tar file to .bin?
Thats great but it talks abotu extracting the BIN file. When I use my "extraction software" to find the .bin file in the tar.gz file all it finds is another .tar file? where do we locate the .bin file???? or are you simply renaming the .tar file to .bin?
Hi,
You have to untar the .tar file which will then list all the files. One of the files will be the firmware.bin file.
Anyone else seeing issues on 3.3? We have been running a few force 200 and force 180 on it and so far no reboots but I dont want to keep putting it out in the wild if its going to cause customers issues.
Right now the installers are still getting SM's with it on them.
Anyone else seeing issues on 3.3? We have been running a few force 200 and force 180 on it and so far no reboots but I dont want to keep putting it out in the wild if its going to cause customers issues.
Right now the installers are still getting SM's with it on them.
Cambium should we role back to 3.2?
Hi Brandon,
For now we didn't observe reboot issue with 3.3 Release.
Several cases were solved with hardware replacement and hardware issue has been confirmed.
We saw probably 15-20 clients impacted by this. (out of about 500 using ePMP) The first several we rolled trucks and replaced the radios, but for the remainder their troubles were solved by downgrading to 3.2.2.
So you're saying those are all hardware problems that were exposed by 3.3?
We saw probably 15-20 clients impacted by this. (out of about 500 using ePMP) The first several we rolled trucks and replaced the radios, but for the remainder their troubles were solved by downgrading to 3.2.2.
So you're saying those are all hardware problems that were exposed by 3.3?
j
Hi Joel,
We need to investigate your perticular case to make any conclusions.
When I first read about this issue we stopped depoloying 3.3. I have been waiting for Cambium to release more details about it before we put it into production. Right now the last truely stable firmware was 2.6.2.1 which is what we are still running. I really would like to run something in the 3.x firmware to take advantage of the faster GUI and a few other fetures.