Any development in the epmp 3000 high ping? I have an AP with 22 subscribers and the ping is terrible…
PING 32(60) bytes of data.
40 bytes from : icmp_req=1 ttl=64 time=22.9 ms
40 bytes from : icmp_req=2 ttl=64 time=21.3 ms
40 bytes from : icmp_req=3 ttl=64 time=19.5 ms
40 bytes from : icmp_req=4 ttl=64 time=18.0 ms
40 bytes from : icmp_req=5 ttl=64 time=16.5 ms
--- ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 16.579/19.703/22.960/2.282 ms
Here is one with 4 SM…
PING 32(60) bytes of data.
40 bytes from : icmp_req=1 ttl=64 time=5.80 ms
40 bytes from : icmp_req=2 ttl=64 time=4.88 ms
40 bytes from : icmp_req=3 ttl=64 time=3.34 ms
40 bytes from : icmp_req=4 ttl=64 time=6.08 ms
40 bytes from : icmp_req=5 ttl=64 time=4.46 ms
--- ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 3.341/4.914/6.082/0.987 ms
This is also an issue for us. I had a customer switch from a force 300 on an epmp3000 sector with mixed force 300 and force 200 clients to a pmp450m and latency went from 35+ms to 8. Substantial difference.
Your first pic shows you have a ton of download and upload interference. That SM will most definitely have higher ping and latency. Locking your upload MCS rate down will help some.
PING 32(60) bytes of data.
40 bytes from : icmp_req=1 ttl=64 time=43.9 ms
40 bytes from : icmp_req=2 ttl=64 time=22.2 ms
40 bytes from : icmp_req=3 ttl=64 time=20.7 ms
40 bytes from : icmp_req=4 ttl=64 time=25.2 ms
— ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 20.754/28.043/43.972/9.337 ms
This customer is about 10km from tower… I have a SM 1.5km from tower great stats and same ping…here are the stats
PING 32(60) bytes of data.
40 bytes from 10.60.14.64: icmp_req=1 ttl=64 time=17.6 ms
40 bytes from 10.60.14.64: icmp_req=2 ttl=64 time=21.2 ms
40 bytes from 10.60.14.64: icmp_req=3 ttl=64 time=24.5 ms
40 bytes from 10.60.14.64: icmp_req=4 ttl=64 time=28.1 ms
40 bytes from 10.60.14.64: icmp_req=5 ttl=64 time=55.9 ms
— ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 17.676/29.532/55.979/13.673 ms
Hi Hu - I’m wondering why do you have a mix/match of firmware version on the SM’s?
I mean - I think we are all finding the latency too high and too inconsistent (so I’m not suggesting the firmware mix/match is the cause) but that being said – I’ve always found that having all firmware versions match is always the best chance for things to work correctly. I’m wondering why you are running a mix of firmwares?
A ping of 17-25 MS is the normal operating value for ePMP. You can only slightly improve the result by minimizing retransmission of packets for both the upstream and downstream link. This can be done by reducing the value of the maximum modulation.
!!!also, stable operation requires using the same firmware version on the AP and SM!!!
No, we have separate areas that we use ePMP or 450m depending on cost sensitivity / performance needs. Our 450 network constantly performs better, doesn’t need handholding or changing. If I did it all again we would have went 450 for all right off the bat.
@Ryan_Ray, thank you for your response! I am feeling the same way, went all epmp, ptp 550 and we are a bit disappointed in a few areas, especially the ping/latency. The budget was not compatible with the 450 lineup but definitely want to move into that arena soon. If you dont mind me asking, what do you use for your Backhaul solution?