ping time degrades for zf7731

Question

when the Ruckus wireless bridge is restarted, everything works perfectly: the response time of the remote terminal are 1ms and remote applications work perfectly

In time (of the order of the week, see ten days) ping time degrades (up from packet loss) and the application becomes non-functional (frames IP is not received).

ping school to Parking

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 293 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 911 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 1190 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 511 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 453 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 309 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 448 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 607 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 1449 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 662 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 815 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 258 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 792 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 351 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 1911 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 24 DC TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 1393 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 393 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 511 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 472 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 273 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 271 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 990 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 669 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 269 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 548 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 993 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 1192 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 833 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 954 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 1219 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 1457 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 1761 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 754 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 774 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 233 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 674 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 1308 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 864 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 742 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 450 ms TTL = 63

Reply from 192.168.121.242: bytes = 32 time = 548 ms TTL = 63

Timeout of the request.

Reply from 192.168.121.242: bytes = 32 time = 1329 ms TTL = 63

The request timeout

unknown · Answer

Hello Camara,

With Limited info, Link performance degradation over a period of time if there is no visible source of interference near the Zf7731 devices then it is possible case of Fresnel zone encroachment. In my experience - these are NOT seen immediate and takes time to rear its ugly head.

Take a look at Point-Point Bridge Best Practices doc just in case you missed out during planning stage.

http://alturl.com/pud8p

Best of luck.