I have 2 Rocket M5s and a Rocket M2. For some reason they occasionally "forget" their settings or firmware and become unusable, requiring me to re-flash the AREDN firmware.
- One M5 (XW) is on a remote site and I can't keep making half day trips to fix it. The one on-site is currently borked again. I can remotely access a Linux SBC on-site, so maybe there's a chance to fix it that way.
- The other M5 and M2 are now on my workbench.
- The M5 (XM) is flashed again with current AREDN firmware and seems good to go, for now. I'm reluctant to deploy it if it is going to forget again.
- The M2 started taking AREDN firmware but now seems stuck. The LEDs fit the AREDN pattern (Pwr, Network, #4), but I can't connect to it in any way over network. No DHCP, not at IP 192.168.1.1 nor 192.168.1.20. Network scanner doesn't find it on the 192.168.1.x subnet. Can get into TFTP flash mode (alternating LEDs), but I can't put firmware at the 192.168.1.20 address.
- any ideas on why they are "going bad" on me?
- how can I get the M2 working again?
- Depending on their age, it's possible that the flash memory in those devices is wearing out (it happens).
- In the Ubiquiti products there's a remote reset circuit that functions by shorting certain wires or pairs. If moisture gets into the Ethernet cable, it mimics a remote reset (ask me how I know...). Depending on how it shorts, it will at a minimum reset the AREDN software config back to "just loaded" state.
If you confirm 2. isn't happening, then it's probably 1. and you're going to have to replace the devices. On the bright side, you can replace the Rocket m5s with the way-better Rocket 5 ac lites. :-)Hope this helps.
Orv W6BI
Another problem with the Ubiquity is the RJ-45 framework is a bit flaky and can pull out and bend very easily if pulled on or stressed and render the Ethernet cable useless. I place a cable tie to the Ethernet cable inside the unit as a stress relief.
Denis KD1HA