Where are we supposed to purchase the Smart QOS license. I cannot find it anywhere
I think it should be available from the usual Cambium distributors, although Google doesn’t seem to be showing many results. Here’s one though:
https://www.wavonline.com/products/cambium-networks-qe-e3000-01a-ww/p-171259/
1 Like
Is there a video showing the Smart QoS in action?
2 Likes
We put 4.7 RELEASE on all our ePMP 1000 (2.4 Ghz) / 2000 / 3000 series, and all seems well.
The only issue we see is the known cosmetic issue of certain SM’s showing up with blank ‘device names’ in the AP’s list – which has been tracked down to their device name being a certain length or containing a certain string of characters.
So far, so good… working well on all 1000 / 2000 / 3000 series gear.
3 Likes
We installed 4.7 on a 2.4 ePTP link in a high noise environment feeding a a small mini
pop through some trees a couple of miles distant. The link had been problematic and we were on the verge of swapping it to an AF2X but since we moved to 4.7 it has been stable so KUDOs for the ePTP tweaks…
5 Likes
We’ve deployed 4.7 on our entire network and the one thing that really stands out is the reduced latency. Great work!
4 Likes
Are you sure? We didn’t notice such thing…
4.7 has been out for a few weeks now, how is this running for everyone who has upgraded? Anybody tried the STA release yet?
Yep, we’re running 4.7 on everything and have the STA release deployed on all 5GHz radios. Everything is working great!
1 Like
I’ve seen performance improvements with 4.7 mentioned in the forums. But it’s not clear to me whether those improvements are applicable to 2000 APs with F200 SMs.
Hi @3-dBnetworks,
yes, you should observe improvements on N-radios too. There was a bunch of changes in scheduler algorithm and stability improvements. In other words fixes covering corner cases from our customers’ networks related to latency and tput.
What is wrong with the traceroute from the CLI?
AP_TEST>traceroute --help
BusyBox v1.25.1 (2022-11-23 17:36:19 UTC) multi-call binary.
Usage: traceroute [-FIlnrv] [-f 1ST_TTL] [-m MAXTTL] [-q PROBES] [-p PORT]
[-t TOS] [-w WAIT_SEC] [-s SRC_IP] [-i IFACE]
[-z PAUSE_MSEC] HOST [BYTES]
Trace the route to HOST
-F Set don't fragment bit
-l Display TTL value of the returned packet
-n Print numeric addresses
-r Bypass routing tables, send directly to HOST
-v Verbose
-f N First number of hops (default 1)
-m N Max number of hops
-q N Number of probes per hop (default 3)
-p N Base UDP port number used in probes
(default 33434)
-s IP Source address
-i IFACE Source interface
-t N Type-of-service in probe packets (default 0)
-w SEC Time to wait for a response (default 3)
-g IP Loose source route gateway (8 max)
AP_TEST>traceroute -n 192.168.101.1
Syntax error: Illegal command line
Hi @Willi_Gruber,
arguments should be in quotes.
e3k_cs>traceroute “-n 8.8.8.8”
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.1.11.71 1.958 ms 2.207 ms 1.049 ms
2 172.22.123.1 2.227 ms 1.037 ms 2.246 ms
3 172.17.62.9 2.219 ms 2.221 ms 2.242 ms
4 195.238.92.68 2.249 ms 2.281 ms 2.184 ms
5 95.67.4.121 3.330 ms 2.233 ms 2.241 ms
6 95.67.1.28 10.577 ms 10.547 ms 11.765 ms
7 * * *
8 108.170.248.155 3.381 ms 3.467 ms 3.478 ms
9 142.251.242.39 29.804 ms 142.251.224.82 30.785 ms 72.14.239.111 3.388 ms
10 216.239.35.133 29.696 ms 29.670 ms 108.170.250.209 30.854 ms
11 108.170.250.209 31.021 ms 216.239.40.43 31.928 ms 142.250.238.1 30.787 ms
12 142.250.224.89 32.037 ms 8.8.8.8 29.660 ms 142.251.65.223 30.863 ms
I will create an engineering ticket to add this note to help output. It is the same for all Linux tools in our CLI. Thank you!
1 Like
I’m not able to upgrade an ePMP 3k on version 4.6.2 to 4.7 from cnMaestro, this is the third time I try, and I have to (once again) go the the site to uplug/plug it again. Is there any recommended upgrade path I should be aware of?
3rd time I’ve tried on that particular AP worked from the Web UI, now, I’ve tried the upgrade again with other two APs using the Web UI, and isn’t working, I will have to go on-site again (ugly experience :), restart, and try again. It’s very inconsistent, but 90% of the time the upgrade for AP doesn’t work. Cambium team, any feedback on this?
We upgrade hundreds to 4.7 without any much issues. The only time we’ve had inability to upgrade in the past, is when memory is low. This might not be your situation, but that’s bit us a couple times before. So, we’ll turn off all things that don’t need to be on (certainly the Spectrum Analyzer if it happens to be on, will likely screw things up) but any other services which don’t need to be running during the upgrade, that seems to help.
We also have ethernet equipped smart power bars on AP’s, so we can power cycle them from the shop. 
That helps a keep 2 AM drives to a minimum. 
2 Likes
I would appreciate it if you could drop Tech Support File collected from AP when it’s running 4.6.1 or any other firmware you can’t upgrade to 4.7 from.
We didn’t notice the described behavior in the scope of the internal testing cycle.
Thank you.
I’ve 4 ePMP 3000 radios on that state, working (passing traffic), but not responding, thus, I’m not able to download the tech file, ssh, telnet or interact with them using SNMP. I will have to do a power cycle and try again. It has been an inconsistent behavior, both from Web UI or using cnMaestro. Last night I upgrade ~300 F300-13L SMs with cnMaestro, ~90% were success upgrades, the rest either timed out (but upgraded successfuly) or failed downloading and I had to retry.
The first three e3K APs I tried upgrading from 4.6.2 to 4.7 had the same lockup behavior (could only ping, and connected SMs continued to work just fine) The next few APs I power-cycled before upgrading and they upgraded fine. I’ll try to reproduce the issue on the next couple APs I upgrade and will grab support files beforehand.