We had great comms 1ms at the beginning and not a lot of data traffic. But after a few hours, its like the comm ports loaded up and acted like a loop was in place. But it was just a bridge to an endpoint cabinet. It was like all our traffic was trying to route down the fiber from the ES48, to the ERX, instead of to the WatchGuard Router. This is just my explanation, and just meant to explain what we experienced. Once we power cycled the ERX, ping times went back to 1ms, and traffic was good. This has happened twice in 24 hours. The issue does not exist with a Power Beam connection back to AP, connected to ES48. Why would the fiber link act differently?
I will try a few of the connections that are non-critical to the ERX. One reason for our current setup with dumb hub at the end for scada, is to make sure the local devices can communcate locally if comm issue. Honest, there have been issues with certain lightly managed devices (will not mention names, mulitple manufacturers) causing problems in the past.
Our goal, is to deploy more edge point routers because of the heat rating for West Texas, the SFP, and POE manageability. We are very happy with the setup of the edge point/routerX. Just have some worries now after the issues we saw previously.