I completely misreported this. What is happening is every four or five days I have a PowerBeam M5 620 that locks up. This radio is a couple hundred miles away and 130ft up on a tower, so I can't easily be certain that there are no lights on on the feedhorn, but can confirm it is inaccessible. The port indicator on the Netonix stays lit up - it doesn't show the port as being down, however I'm unable to ping it from the switch. This is on a PtP link that's been up without issue for going on two years. I also noticed that on this radio, the LAN side is only 100MF. (On the radio I have it set to 10-100-1000 Auto. On the Netonix if I lock it to 1G, the radio loses connection with the switch. If I set the Netonix to Auto, it negotiates at 100MF.) To recover, I log into the Netonix switch and bounce the PoE port, and it's good for another four or five days. I was running 5.6.5 XW on it. I just upgraded it to 5.6.9 XW this morning. I don't know if that will resolve the issue or not (there's nothing in the release notes to lead me to believe this is something that was fixed between 5.6.5 and 5.6.9). While I wait to see if it helps I thought I'd see if anyone else has seen anything like this. Given that it won't negotiate to 1G, could the cable be causing this? Seems like it would be easy to blame the cable for the inability of the radio to negotiate at 1G, however I wouldn't think a bad cable would allow the radio to stay up for five days, then lock up hard, only to run again for five days after being power cycled, lock up hard, etc. After upgrading the firmware, the radio still still only negotiates to 100MF. I tried putting it on a different Netonix but that changed nothing.
(I have to remember to stop asking for help before I've had coffee. I do have another radio where the WLAN port was going to sleep but I think I have that figured out.) Thanks, Sam On 11/2/2016 9:16 AM, Sam Morris wrote: > Yes...you have to listen to what I mean and not what I write. :) > > > On 11/2/2016 7:50 AM, Josh Luthman wrote: >> You mean WLAN port? >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> >> On Nov 2, 2016 8:47 AM, "Sam Morris" <[email protected] >> <mailto:[email protected]>> wrote: >> >> Have any of you seen the WAN port going to sleep every four or five days >> or so on a PowerBeam M5? I've started seeing that on a PtP link that's >> been up without issue for going on two years. When this happens, I log >> into the Netonix switch and bounce the PoE port, and it's good for >> another four or five days. I was running 5.6.5 XW on it. I just upgraded >> it to 5.6.9 XW this morning. I don't know if that will resolve the issue >> or not (there's nothing in the release notes to lead me to believe this >> is something that was fixed between 5.6.5 and 5.6.9). While I wait to >> see if it helps I thought I'd see if anyone else has seen anything like >> this. >> >> Thanks >> Sam >> _______________________________________________ >> Ubnt_users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> <http://lists.wispa.org/mailman/listinfo/ubnt_users> >> >> >> >> _______________________________________________ >> Ubnt_users mailing list >> [email protected] >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> > > _______________________________________________ > Ubnt_users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/ubnt_users > _______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
