A little about the network first:
I have a wireless network that is tying cameras back to a central location. The RB435G has 3 mPCI cards all running NV2 with an EOIP tunnel across each wireless link. Each link is on it’s own network. The EOIP tunnel is for the cameras on the end of each link. At the end of each link is also a hotspot. There is also another link plugged into the RB435G via a Cat5e cable. The RB435G then connects to a 5 port unmanaged switch and ties back to a data room where the NVR resides.
This solution has been working for the past couple of months, but all of sudden has started to fail. The RB435G goes off into lala land and becomes unresponsive. When we unplug it’s power and plug power back in, the unit comes back up and the cameras become visible again. During the time it’s down, the discovery tool in winbox can’t see or find the RB435G and the device doesn’t respond to pings. I’ve also tried hitting it’s MAC address and IP using the winbox tool regardless of it seeing it or not (still can’t get into the board). I know when I first installed this system, I was on 5.22. I am now on 5.24, which I believe I read fixed an issue with NV2, and I’m still getting the problem. Since power cycling it always fixed the issue, I put a reboot script on the device to reboot every few days. This didn’t work either and I ended up changing the script to every 24 hours. It ran for about 5 days, cycling every 24 hours on its own, but it failed again and required a power cycle. Don’t know if it’s an NV2 issue and it’s causing the RB435G to halt or what. I know if it was a broadcast storm, I should still be able to see the device in the discovery tool, it just won’t be responsive.
Upon power cycling the device this morning, I grabbed a supout file. I will attach it to this post. Let me know if I need to provide any more information.
P.S. The RB435G is plugged into a UPS because we thought it might have been receiving dirty power.