I am going to reboot this discussion since it is once again driving me insane.
Every single B5 or B5 Lite (we don’t have any B5c) we put on our network stops responding to our monitor machine 24 hours after it was installed and it stops for exactly 1 hour - every day. You install it at 3:00pm and the next day at 3:00pm, it stops responding to pings and SNMP for exactly 60 minutes - and every single day after that. You reboot the Mimosa at 11:30am and the next day, instead of 3:00pm, it stops responding at 11:30am for exactly 60 minutes. It is 100% related to the Mimosa uptime.
Our monitor machine is a Windows 7 machine running PRTG. We use both SNMP and Ping to monitor our radios.
When the radio stops responding to PRTG, if I log into the Windows machine and try to ping a Mimosa radio from command line, it does not respond. If I try to ping that radio from our switches or another random device on the management VLAN, it works. So, the Windows 7 machine can’t see every single B5 and B5 Lite for exactly 1 hour every day at the same time.
Thinking this was a Windows issue, we built a Windows 10 PRTG server on a different piece of hardware and on a different IP address. Guess what? Same exact thing happens to that server - it can’t see the Mimosa radios for exactly 1 hour nor can the computer ping them during that hour.
If I reboot the Windows PRTG server during this “outage”, it still can’t access them until that hour is up. So, this really has me believing this is a Mimosa thing, not a PRTG or Windows issue. We monitor over 200 devices with this server. The only devices that have an issue are the Mimosa B5’s and B5-Lites (A5 and C5’s are fine).
I am not able to confidently monitor these radios since we get alarms every day for every radio. We end up turning off alerting so if it really does go down, we won’t know until devices behind it start squawking.
Would love some help from Mimosa on this… We are running the latest release firmware as of 5/2017. It has been happening on at least the previous firmware as well.