CommScope RUCKUS Community Forums

william_marion · ‎05-25-2021

Hello,

We often see code 328 pop-up for latency health crossing the threshold, then later a code 332 when latency drops back below the threshold. What I am trying to understand is where this latency warning is coming from. Is this latency from the AP to the device caused by interference or range issues or does it indicate a problem with the AP itself?

Any insight is greatly appreciated.

Thank you

syamantakomer · ‎05-25-2021

Hi William,

Latency could be due to many reasons.

First of all, controller monitors the stats of RF from all the APs and depending upon the threshold value, it raised the flags.

It shows you the environment of those AP and AP stats at present. By default flags are set to medium sensitivity with medium threshold. This may not be appropriate for all the deployment like if its a big network with multiple AP and high density setup.

Change the sensitivity of flags (set to low) and threshold as well (to high), depending upon how tightly your APs are deployed.

And no, its not a problem on the AP.

View solution in original post

cambiatihealths · ‎11-25-2024

The latency warnings you're seeing code 328 for crossing the threshold and 332 when it drops back—likely indicate issues with communication between the access point (AP) and the device. This latency can stem from several factors, such as interference from nearby networks or devices, signal obstruction, or the distance between the AP and the client. While these issues are commonly external, it’s also worth checking the AP’s load and firmware for any performance anomalies. Running a site survey or spectrum analysis can help pinpoint interference, while ensuring the AP's placement and settings are optimal for your environment might improve overall latency performance.

p-5-p supplement designs for health

CommScope RUCKUS Community Forums

AP Health High Latency Flag