ePMP3000 with 72 F300-25 SMs results

For me, for an AP with 50 users, is about 20-25ms.

Curious to see the same on this 72 users AP

I expected less latency much less 20-25 ms and approximate latency of an epmp 2000 with this amount of SM with old 802.11n hardware, I sincerely expected something between 5-8 ms because it is new hardware, with its report of 20- 25ms I was really disappointed with epmp 3000.

Alex,

Its a TDD system which means you are able to synchronize SMs and get a lot of SMs connected with very good tput. Part of that story is that you have to allocate time to the different SMs as they request bandwidth or have data to send. You cannot show me any system where 50+ users being served at any given time gives you 5~8 ms latency while supporting 5ms frame and a synchronized system. 

Sakid

1 Like

Alex - this is from one of our ePMP3000's to a Force300-25 client 8.99km away.

PING 10.123.1.193 (10.123.1.193) 32(60) bytes of data.
40 bytes from 10.123.1.193: icmp_req=1 ttl=64 time=3.58 ms
40 bytes from 10.123.1.193: icmp_req=2 ttl=64 time=2.03 ms
40 bytes from 10.123.1.193: icmp_req=3 ttl=64 time=5.48 ms
40 bytes from 10.123.1.193: icmp_req=4 ttl=64 time=4.00 ms
40 bytes from 10.123.1.193: icmp_req=5 ttl=64 time=2.56 ms
40 bytes from 10.123.1.193: icmp_req=6 ttl=64 time=4.61 ms
40 bytes from 10.123.1.193: icmp_req=7 ttl=64 time=4.71 ms
40 bytes from 10.123.1.193: icmp_req=8 ttl=64 time=2.95 ms
40 bytes from 10.123.1.193: icmp_req=9 ttl=64 time=5.93 ms
40 bytes from 10.123.1.193: icmp_req=10 ttl=64 time=4.80 ms

— 10.123.1.193 ping statistics —
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 2.031/4.068/5.931/1.211 ms

I don’t have ePMP3000 AP’s with 72 clients I can test with - but I just wanted to chime in and say that the latency is a lot less than ePMP2000 802.11n was.

2 Likes

Thanks Todd for showing your results. Looking forward to you talking about yoru dual horn experience too :)

Alex, the latency I've reported is for a big number of users, for less users you have less latency like ninedd reported.

Ninedd, how many users you have?

ninedd

How many users and is that ePMP or TDD mode and frame size ?

Here is what latency looks like on one of my sectors with 35 active subscribers.  Not bad but not great either.  This is typical of what I'm seeing on 3k with 25~35 subscribers and moderate traffic (~50Mbps out to subs at this time).

This is pinging from the tower router to the router at one subscriber's location, so this is just OTA/TDD latency. Latency is obviously higher from the sub to anywhere on the internet.

 SEQ HOST                                     SIZE TTL TIME  STATUS             
   40 100.64.104.134                             56  64 26ms 
   41 100.64.104.134                             56  64 56ms 
   42 100.64.104.134                             56  64 22ms 
   43 100.64.104.134                             56  64 21ms 
   44 100.64.104.134                             56  64 61ms 
   45 100.64.104.134                             56  64 22ms 
   46 100.64.104.134                             56  64 53ms 
   47 100.64.104.134                             56  64 31ms 
   48 100.64.104.134                             56  64 26ms 
   49 100.64.104.134                             56  64 32ms 
   50 100.64.104.134                             56  64 46ms 
   51 100.64.104.134                             56  64 22ms 
   52 100.64.104.134                             56  64 22ms 
   53 100.64.104.134                             56  64 22ms 
   54 100.64.104.134                             56  64 32ms 
   55 100.64.104.134                             56  64 22ms 
   56 100.64.104.134                             56  64 28ms 
   57 100.64.104.134                             56  64 26ms 
   58 100.64.104.134                             56  64 32ms 
   59 100.64.104.134                             56  64 21ms 
    sent=60 received=60 packet-loss=0% min-rtt=12ms avg-rtt=30ms max-rtt=77ms 
1 Like

For comparison to the 3k results above - Here is ePMP 1k AP and 1k sub.  This AP also has 35 subscribers and at the time of this test was between 75 and 97% DL frame utilization.  Totally slammed.  Again, the pings are from tower router to subscriber router, through the radios.  This is OTA/TDD latency.

It has been my experience thusfar that ePMP 1000 jitter is MUCH lower overall than 3k.  I've actually almost lost subscribers that rely on VOIP once moving them to a 3k AP and have had to move them back.

SEQ HOST                                     SIZE TTL TIME  STATUS             
   40 100.64.103.65                              56  64 32ms 
   41 100.64.103.65                              56  64 29ms 
   42 100.64.103.65                              56  64 26ms 
   43 100.64.103.65                              56  64 31ms 
   44 100.64.103.65                              56  64 32ms 
   45 100.64.103.65                              56  64 28ms 
   46 100.64.103.65                              56  64 26ms 
   47 100.64.103.65                              56  64 29ms 
   48 100.64.103.65                              56  64 29ms 
   49 100.64.103.65                              56  64 25ms 
   50 100.64.103.65                              56  64 27ms 
   51 100.64.103.65                              56  64 26ms 
   52 100.64.103.65                              56  64 27ms 
   53 100.64.103.65                              56  64 27ms 
   54 100.64.103.65                              56  64 31ms 
   55 100.64.103.65                              56  64 29ms 
   56 100.64.103.65                              56  64 29ms 
   57 100.64.103.65                              56  64 29ms 
   58 100.64.103.65                              56  64 32ms 
   59 100.64.103.65                              56  64 28ms 
    sent=60 received=60 packet-loss=0% min-rtt=25ms avg-rtt=29ms max-rtt=57ms 
1 Like

@ninedd wrote:

Alex - this is from one of our ePMP3000's to a Force300-25 client 8.99km away.

PING 10.123.1.193 (10.123.1.193) 32(60) bytes of data.
40 bytes from 10.123.1.193: icmp_req=1 ttl=64 time=3.58 ms
40 bytes from 10.123.1.193: icmp_req=2 ttl=64 time=2.03 ms
40 bytes from 10.123.1.193: icmp_req=3 ttl=64 time=5.48 ms
40 bytes from 10.123.1.193: icmp_req=4 ttl=64 time=4.00 ms
40 bytes from 10.123.1.193: icmp_req=5 ttl=64 time=2.56 ms
40 bytes from 10.123.1.193: icmp_req=6 ttl=64 time=4.61 ms
40 bytes from 10.123.1.193: icmp_req=7 ttl=64 time=4.71 ms
40 bytes from 10.123.1.193: icmp_req=8 ttl=64 time=2.95 ms
40 bytes from 10.123.1.193: icmp_req=9 ttl=64 time=5.93 ms
40 bytes from 10.123.1.193: icmp_req=10 ttl=64 time=4.80 ms

— 10.123.1.193 ping statistics —
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 2.031/4.068/5.931/1.211 ms

I don’t have ePMP3000 AP’s with 72 clients I can test with - but I just wanted to chime in and say that the latency is a lot less than ePMP2000 802.11n was.


ninedd, I have about 15 active subscribers on one of my epmp 3000 sectors and this is my ping from a customer around 8km…

PING 10.60.14.173 (10.60.14.173) 32(60) bytes of data. 
40 bytes from 10.60.14.173: icmp_req=1 ttl=64 time=21.6 ms 
40 bytes from 10.60.14.173: icmp_req=2 ttl=64 time=27.5 ms 
40 bytes from 10.60.14.173: icmp_req=3 ttl=64 time=25.3 ms 
40 bytes from 10.60.14.173: icmp_req=4 ttl=64 time=18.6 ms 
40 bytes from 10.60.14.173: icmp_req=5 ttl=64 time=25.8 ms 

--- 10.60.14.173 ping statistics --- 
5 packets transmitted, 5 received, 0% packet loss, time 4005ms 
rtt min/avg/max/mdev = 18.609/23.803/27.595/3.248 ms 

How are you getting such great ping?  

17 SC

tarifs 25/5 and 50/10

50% have IPTV

Hi Chris_2;

That's very good.  I noticed that some of your SMs are running different firmware versions.  Would that make a difference?  Also, you're not using MIR Profile based on the screenshot.  Would that make a difference?  Also, what are you using to do put customers to their various packages?

That is some good SNR.   Are you using the Beamforming antenna?  Are you using the ePMP 3000 AP stock antenna (Cambium's version) or another 3rd party, like a horn or something?

Very good results.

i want to share my results too.

64 clients

2 Likes

Hi, 

These are good results with e3K running backwards compatibility mode. I noticed that most of our SMs are still 11n. As you change out the SMs, I think you will see considerable improvement in AP tput and DL MUMIMO results. You should also make sure all the SMs are on the same software version.

If you don't mind me asking, what is preventing you from upgrading the SMs?

Thx

Sakid

I will tell you that the force 300 is crap, you will not find anyone to tell you that the equipment works well and without any error.

1 Like

@Tewsbehappy  wrote:

I will tell you that the force 300 is crap, you will not find anyone to tell you that the equipment works well and without any error.


We use F300's all over the place and we have very few, if any problems... at least no show stoppers that prevent us from offering the same level of service as any other client equipment.

2 Likes

I think someone from Cambium already reached out but we want to change your mind. Please let me know and we can make this right. You can DM me in the community or email me at sakid.ahmed@cambiumnetworks.com

1 Like

Hi Tewsbehappy;


Wow. Would you mind sharing your experience and/or in which way these specific SM types are bad compared to the other ePMP SM units?


Your comments are serious and I even see where Cambium support (in this thread) is even reaching out to you to help you through any difficulties being experienced. Lots of persons research here to see how to upgrade and pick a solution. Or, to resolve a problem. This one is quite alarming.


Thanks.

1 Like

great!
I see that all your sm are force 180 and with distances above 1.5 km, which model of ap do you use? what kind of antenna do you put on it?
Another thing that I see and I create that data in case 100% improvements are not achieved are downlink capacity
thanks for showing us your network
regards! 

this antennas with 4.4.3 are comming from other ap working on this version. cnmaestro update this versions one time a week. :D