In our PTMP networks the access point is one of below
NetMetal (RB921UAGS-5SHPacT-NM) with wireless radio QCA9882
MantBox19s (RB921GS-5HPacD-19S) with wireless radio QCA9892
RouterBoard RB922UAGS-5HPacD with wireless radio QCA9882
And the CPEs are a typically a mix of these
50% LHG XL HP 5 (mipsbe)
30% LHG XL AC
20% SXT5HPND
Can anyone who has a similar access point share their experience when switching from NV2 to 802.11 protocol when there is a mixed variety of CPE such as above?
I’ve read that performance of 802.11AC is good for new ARM hardware, but what about the rest of the equipment (mipsbe)?
Would really like to know as well because having 20 CPE’s on a sector in very noise environment and only able to get max 20mbps from the sector is a bit low in today’s market.
Only running nv2 on our network
Mostly lhg lite 5 cpe’s and trying to keep signal below -60
Any one getting better performance from any other setup in a noise environment please share your experience.
Im using 922UAGS-5HPacD (Netmetal) and RF elements Symmetrical Horn 30 deg
I don’t think it is frequency because i did test it with a very clean one that is obviously not one of the default frequency and i got the same result.
20 clients on the sector running ROS 6.46.4
band=5ghz-onlyn
NV2
nv2-cell-radius=22
nv2-downlink-ratio=80
If you say low what are you getting out of your setup?
I have read here on the forum a while ago, that there are indeed performance problems with the combination of: NV2, AC hardware and older N type hardware clients. It’s been suggested, that one can use pure 802.11 with RTS/CTS configured instead, and get higher aggregated throughput (at the cost of higher latency), but this really depends also on how far away the client’s are, from the sector/AP.
I think that you will get the best results, by creating a new sector on a different channel (80 MHz wide) and the AP set to AC only. The gradually move over the clients, to the new AC sector, so that you avoid mixing old and new clients. Why 80 MHz wide, you may ask?, well when you run AC, the AP and client can fallback in increments of 20 MHz, if interference is detected on one of the subs.
Until today, mikrotik developers have not made a driver that allows for asymmetrical (set maximum MCS matching on the UPLOAD side). Which results in an unstable high JITTER in almost every urban environment. And the lack of valid TCP transfers, of course, UDP works beautifully.
Change base stations for OLD mikrotik BaseBOX 5 802.11N use NV2 & NOISE FLOOR parameter try: 100, 95, 90, 85 force low MCS from UPLOAD SIDE.
ANY mikrotik 802.11AC gear cant set NOISE FLOOR properly.