So I am puzzled by the latency between the Force 300 25 SM and the epmp 3000. I have an epmp 3000, running 4.5 firmware, with 19 SMs and the ping between the closest SM, 1 mile away, and the sector is
8 packets transmitted, 8 received, 0% packet loss, time 7012ms
rtt min/avg/max/mdev = 15.672/19.462/28.618/4.487 ms
And another SM that is 6 mles away and the ping to the sector is this
8 packets transmitted, 8 received, 0% packet loss, time 7008ms
rtt min/avg/max/mdev = 15.603/18.866/23.531/2.597 ms
The first SM is a 19 and its downlink is modulating at 95% at DS MCS9 and its uplink is 99% at DS MCS8
The second SM is a 25 and its downlink is modulating at 92% at DS MCS9 and its uplink is 97% at DS MCS7
I have another epmp 3000 running 4.5 with 4 SM and I have a force 25 sm that is 7 miles from the sector and it is not modulating as well as the aove mentioned SM and ping is
8 packets transmitted, 8 received, 0% packet loss, time 7010ms rtt min/avg/max/mdev = 3.249/4.903/6.685/1.210 ms
Less SM means less delays, it appears that around 12-16 SM delays are low. With more SM, they stabilize around 25ms. Jitter is great so where's the problem ???
So I am puzzled by the latency between the Force 300 25 SM and the epmp 3000. I have an epmp 3000, running 4.5 firmware, with 19 SMs and the ping between the closest SM, 1 mile away, and the sector is
8 packets transmitted, 8 received, 0% packet loss, time 7012ms
rtt min/avg/max/mdev = 15.672/19.462/28.618/4.487 ms
And another SM that is 6 mles away and the ping to the sector is this
8 packets transmitted, 8 received, 0% packet loss, time 7008ms
rtt min/avg/max/mdev = 15.603/18.866/23.531/2.597 ms
The first SM is a 19 and its downlink is modulating at 95% at DS MCS9 and its uplink is 99% at DS MCS8
The second SM is a 25 and its downlink is modulating at 92% at DS MCS9 and its uplink is 97% at DS MCS7
I have another epmp 3000 running 4.5 with 4 SM and I have a force 25 sm that is 7 miles from the sector and it is not modulating as well as the aove mentioned SM and ping is
8 packets transmitted, 8 received, 0% packet loss, time 7010ms rtt min/avg/max/mdev = 3.249/4.903/6.685/1.210 ms
Any help would be great!
Could you please attach a screenshot of Monitor -> Performance page for both SMs with high latency? You have to take into consideration not only DM MCS, but UL as well since ping is doing a round trip.
8 packets transmitted, 8 received, 0% packet loss, time 6996ms
rtt min/avg/max/mdev = 0.098/0.162/0.381/0.098 ms
pinging the AP from the SM I get this result.....
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 15.623/21.529/41.623/7.873 ms
The results are not consistent.
For the case when you are pinging SM from AP, latency is too low.
And for the case when you are pinging AP from SM, it's too high.
Since ping is measuring RTT.
You can also do the simple test, just leave 1 SM connected and see the latency.
Thank you.
Thank you for the reply, Im not sure what you want me to do, I have 20 SMs on this sector and they are all in the field installed at customers location... having all but one connected isnt an option...by info I supplied what are we looking at here?
@DigitalMan2020 wrote:2/0.381/0.098 ms having all but one connected isnt an option..
I think what he's suggesting is to temporarily change something, to leave just one SM connected - just for a quick test. For example, change the SSID on one SM and on the AP, and do an 'Test/Try Changes' on the SM and on the AP... and then 'revert' when you're done testing. That way, you'll have a couple minutes to do a ping test both directions and see what results you get, with just 1 SM connected. I think that's what he's suggesting?
I know, it's tricky to do that when that'll take 19 client out of service for a few minutes, but at least that way it'll be a test of the exact same AP / SM / Freq / Distance / Environment, and he will be able to see if it's just a factor of the higher user count, or if the problem persists with just 1 SM.
I think the ping attempt from SM to AP may be a mistake. You may have accidentally pinged the AP from the AP. Not sure how else you could have gotten sub millisecond RTT.
My pings to SMs are pretty consistent with yours. I have 24 clients on this AP.
8 packets transmitted, 8 received, 0% packet loss, time 7011ms
rtt min/avg/max/mdev = 5.931/21.936/36.561/9.574 ms
I think the ping attempt from SM to AP may be a mistake. You may have accidentally pinged the AP from the AP. Not sure how else you could have gotten sub millisecond RTT.
My pings to SMs are pretty consistent with yours. I have 24 clients on this AP.
8 packets transmitted, 8 received, 0% packet loss, time 7011ms
rtt min/avg/max/mdev = 5.931/21.936/36.561/9.574 ms
dkeltgen, thanks ya I must of messed up... my ping from ap to sm and sm to ap are consistent now, I cant believe how bad the ping is...
