Important Cambium Upgrade by July 1, 2021

UPDATE: Cambium has extended this to January, 31 2022.

Updated Bulletin
https://www.cambiumnetworks.com/support/field-service-bulletins/fsb9083/?fbclid=IwAR0rhizW7jkovSvBFQnUTWyqEKL41nMEceEyfGaeFMAIOIiWNGZTVU0HmTE

On July 1, 2021 Cambium will update the certificate for https://cloud.cambiumnetworks.com 14 to use a new Certificate Authority. All cnMaestro managed devices without the updated Root CA certificate will fail to connect to the cnMaestro Cloud service. Please see the following Field Service Bulletin (FSB) for ePMP upgrade instructions.
https://www.cambiumnetworks.com/support/field-service-bulletins/fsb9083/

https://community.cambiumnetworks.com/t/notice-need-for-epmp-upgrade/74457

As of the bulletin the minimum softwar versions to support the new certificate are:

Family Model Version
cnMatrix cnMatrix EX2K 2.1-r5

cnPilot
cnPilot R200, R200P 4.6-R16
cnPilot R201, R201P 4.6-R16
cnPilot R190V, R190W 4.6-R16
cnPilot e400/e500 3.11.4.1-r3
cnPilot e410/e430w/e600 3.11.4.1-r3
cnPilot R195P 4.7-R6
cnPilot R195W 4.6-R16
cnPilot e501S/e502S 3.11.4.1-r3
cnPilot e700 3.11.4.1-r3
cnPilot e425/e505 4.1-r3
cnPilot e510 3.11.4.1-r3

cnRanger
Sierra 800 1.1-r3
Tyndall 101 1.1-r3

cnReach N500 5.2.18h

Enterprise WiFi 6
XV3-8 6.1-r5
XV2-2 6.1-r5

ePMP 1000
Hotspot ePMP 1000 Hotspot 3.3.1.2-r1

ePMP
ePMP 1000, Force 180/200 4.5.0
ePMP 2000 4.5.0
ePMP Elevate XM/XW 4.5.0
ePMP Force 190 4.5.0
ePMP Force 300 4.5.0
ePMP PTP 550 4.5.0
ePMP MP 3000 4.5.0
ePMP PTP 550 E 4.5.0
ePMP Elevate SXGLITE5 4.5.0
ePMP Elevate LHG5 4.5.0
ePMP 3000 4.5.0

PMP
PMP 450i, PMP 450, PMP
450m, PMP 430 SM 20.0 Beta-6
PTP 450, PTP 450i, PMP 450
Retro 20.0 Beta-6
Micro-pop Omni/Sector 20.0 Beta-6

PTP
PTP 650 650-01-50
PTP 670 (650 Emulation) 670-01-50,
670-03-12
PTP 670, PTP 700 700-03-11

My first wireless enclosure

This “enclosure” was my first attempt at being a Wireless ISP with no budget. The problem I was trying to solve was putting a waverider Subscriber module on top of a 150 grain leg. The Waverider unit was designed for indoor use. You would mount the unit indoors and then run hardline out to your antenna. In our use case, the 160 foot run of hardline would have caused too much loss.

So before you is the solution. We put an APC battery backup, netgear dumb switch, and a few POEs inside a cooler. A hole was then drilled in the side to pass ethernet and power cables through. This hole was then foamed and further sealed with silicone. This lasted for many years.

Full LTE Architecture explanation

This content is for Patreon subscribers of the j2 blog. Please consider becoming a Patreon subscriber for as little as $1 a month. This helps to provide higher quality content, more podcasts, and other goodies on this blog.
To view this content, you must be a member of Justin Wilson's Patreon
Already a qualifying Patreon member? Refresh to access this content.

Common ISP outage causes

Over the years I have been able to narrow the most common reasons a service provider goes down or has an outage. This is, by no means, an extensive list.   Let’s jump in.

Layer1 outages
Physical layer outages are the easiest and where you should always start. If you have had any kind of formal training you have ran across the OSI model.  Fiber cuts, equipment failure, and power are all physical layer issues.  I have seen too many engineers spend time looking at configs when they should see if the port is up or the device is on.

DNS related
DNS is what makes the transition from the man world to the machine world (queue matrix movie music). Without DNS we would not be able to translate www.j2sw.com into an IP address the we-servers and routers understand. DNS resolution problems are what you are checking when you do something like:

PING j2sw.com (199.168.131.29): 56 data bytes
64 bytes from 199.168.131.29: icmp_seq=0 ttl=52 time=33.243 ms
64 bytes from 199.168.131.29: icmp_seq=1 ttl=52 time=32.445 ms
--- j2sw.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 32.445/32.844/33.243/0.399 ms

Software bugs
Software bugs typically are always a reproducible thing.  The ability to reproduce these bugs is the challenge.  Sometimes a memory leak happens on a certain day.  Sometimes five different criteria have to be met for the bug to happen.

Version mismatches
When two or more routers talk to each other they talk best when they are on the same software version. A later version may fix an earlier bug.  Code may change enough between version numbers that certain calls and processes are speaking slightly differently.  This can cause incompatibilities between software versions.

Human mistakes
“Fat fingering” is what we typically call this. A 3 was typed instead of a 2. This is why good version control and backups with differential are a good thing. Things such as cables getting bumped because they were not secured properly are also an issue.

What can we do to mitigate these issues?
1.Have good documentation.  Know what is plugged in where what it looks like and as much detail as possible.  You want your documentation to stand on its own. A person should be able to pick it up and follow it without calling someone.
2.Proactive monitoring.  Knowing problems before customers call is a huge deal. Also, being able to identify trends over time is a good way to troubleshoot issues.  Monitoring systems also allow you to narrow down the problem right away.
3.When it comes to networking know the OSI model and start from the bottom and work your way up.

Books can and are written about troubleshooting,  This has just been a few of the common things I have seen.