everything has been stable on our link as well since we replaced the SM side of the link. we are still running in TDD and on 4.5.6.
2 Likes
2 days now on 4.5.6 in ePTP with no issues on the one link, everything performing well. If it stays stable we’ll go to 4.5.6 on another this weekend. As some people had earlier surmised, it appears there were some flakey units out there. What we saw in ePTP with 4.6 RC35 was different with pretty much a complete collapse in ePTP mode so hopefully the official release will resolve that. The new F400 series looks pretty awesome, so will get all the F300 BH’s working good just in time to replace them, LOL.
1st incident on 4.5.6 ePTP. mode. Been running well for several days but link dropped for about 15 seconds this afternoon. Master SYSLOG reporting aid=1 disassociated. Reason: 53 (AP KEEP ALIVE RX STUCK)
I would appreciate if you could send Tech support files from both ends please.
Thank you.
When we tried RC35 in ePTP last time on the F300-25 as BH’s, it basically melted down and throughput dropped to like a meg, though TDD mode seemed fine. Been waiting for the official 4.6 before trying it again.
Fedor,
Sent both. Appreciate it! …and take some time off! LOL
1 Like
Still having issues with a F300 TDD BH running 4.5.6. Symptom is different with the last 2 occurrences. On 1/31 and today the wireless link drops. Per the slave side it shows deregistered but the master still shows the link up and active, though it is not.
It required a reboot of the master to restore the link. The watchdog from our switch on the slave side did not reboot the slave which indicates the ethernet link was up, which was the previous problem attributed to hardware.
Captures were already sent. Should we try going to 4.6?
2 Likes
We have the same problem with 4.6-RC35, waiting for 4.6.x.
Yes, it makes sense to go to 4.6.
Please send Tech Support File next time of the issue will occur again.
Any additional information would be highly appreciated.
Thank you.
Issue happened again on 4.5.6 and just happened again after running on 4.6 for a couple of days. I was able to capture the engineering download which has been sent to you.
This is actually a different issue than this thread originally started with. The LAN isse was resolved by a hardware replacement on the slave side that was experiencing the issue. This issue is on the master wireless side dropping its registration and incorrectly thinking it is still registered with the slame. Issue occurs on 4.5.6 and 4.6 and the engineering logs nor the internal logs show any reason. The slave shows the registration drop and the master shows nothing but the reset. .It appears to be load related as the last 3 days it has occurred during peak usage periods but still well below the links capability. Frequency is clean and still have the issue after changing to a different frequency… We were rebooting the master to restore the link but on the last occurrence a couple of hours ago, I logged into the master under the wireless tab, which still showed an active session with the slave, hit DEREGISTER and it immediately re-registered and restored the link. We will be changing the master F300 once the weather clears. The current radio was a replacement for a previous “INTERNAL ERROR” radio failure and it worked fine for a couple of months until this. This will be the 3rd radio replaced on the link. We have been fighting this link for over a year and have decided to replace the link completely with an Air Fiber solution once we get some decent weather in March
2 Likes