Ericsson Cradlepoint Cellular Field Commissioning
Cellular equipment can show a connected modem while delivering unstable throughput, selecting the wrong carrier profile or failing when the primary circuit drops. TechRunz validates NetCloud ownership, SIM and subscription readiness, antenna and RF conditions, routing mode, policies and operational failover as one field workflow.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
NetCloud, carrier and configuration staging
Confirm the exact router or adapter model, modem and region, NetCloud account and license, carrier, active SIM or eSIM and data plan. Record APN, static-address option, data limits and the authorized carrier escalation contact without exposing full account details.
Stage the endpoint name, group, LAN or adapter mode, WAN priority, health rules, VPN, firewall, Wi-Fi and software policy. Determine whether the device will route traffic, provide IP passthrough, serve as out-of-band access or attach to an existing firewall; these roles need different cable and acceptance plans.
Get the router role, the endpoint license status and the expected carrier activation confirmed in writing ahead of dispatch. A technician who arrives to an unactivated SIM or an unclaimed device cannot finish the commissioning, and that is a far cheaper call to make from the office than from the parking lot.
- Model, modem and region
- NetCloud group and license
- SIM, APN and data plan
- Routing or adapter role
Router, adapter and antenna installation
Install the device within its environmental and power ratings and label power, Ethernet, SIM and antenna connections. Use the supported antenna family and cable, keep runs practical and protect outdoor penetrations and grounding as required. Avoid hiding antennas inside a rack or metal enclosure unless the design has been validated.
Confirm the endpoint appears in the correct NetCloud account and group, receives the intended configuration and registers on the expected carrier. Capture modem technology, band, signal-strength and signal-quality metrics at candidate antenna locations before final mounting.
Note the candidate antenna positions you rejected and the readings that led you to the one you kept. When service degrades after building changes, that short list gives the next visit somewhere to start instead of a fresh survey, and it explains why the coax takes the route it does.
- Power and environmental limits
- Supported antenna and cable
- Carrier registration and bands
- Measured placement comparison
| Layer | Acceptance check | Evidence |
|---|---|---|
| Cloud and carrier | NetCloud, license, SIM, APN and registration | Account and endpoint state |
| RF system | Antenna, cable, band and signal quality | Measurements and photos |
| Network service | Addressing, routing, VPN and applications | Client tests |
| Resilience | Failure, failover and restoration | Timestamped event record |
Cellular performance and failover validation
Test addressing, DNS, required applications, VPN and inbound reachability if the plan includes it. Measure performance at representative times and distinguish RF, plan throttling, carrier congestion, antenna loss and local-network limits. A single peak speed test does not establish reliability.
For backup service, intentionally remove or fail the primary path through the approved method and record detection time, route change, session impact and restoration. Confirm that return-to-primary behavior matches policy and does not flap between links. Test out-of-band access without depending on the failed primary network.
Repeat the failover exercise after the first pass, since a link that recovered cleanly once can behave differently when the modem has already re-registered. Record the time of day beside each measurement, because a carrier sector that reads well midmorning can look different when the surrounding area fills up in the evening.
- Application and VPN tests
- Signal and performance evidence
- Primary-path failure timing
- Stable restoration behavior
Monitoring, records and operational handoff
Reconcile serial, modem identifier, SIM reference, antenna model and location, cable path, power source, Ethernet port, software and NetCloud group. Store sensitive identifiers and carrier account records only in the protected client system.
Deliver RF measurements, application and failover tests, photographs, data-plan and alert ownership, accepted limitations and support links. Operations should know who monitors consumption, renews licenses, approves software and opens carrier or manufacturer cases.
Whoever inherits this site will want the antenna photograph with the cable path visible, the band and signal readings taken at acceptance, and the NetCloud group the endpoint sits in. Together those let someone judge whether a later complaint points to a moved antenna, a carrier-side change or configuration drift.
- Serial, SIM and antenna record
- Consumption and alert ownership
- Software and license lifecycle
- Protected carrier information
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Confirm subscriptions
Verify NetCloud group ownership, SIM activation and carrier profiles before the router leaves staging for the site.
Mount and cable
Install the router, antennas and any adapter, then route cabling so RF paths and power stay clear.
Survey signal
Compare readings at more than one antenna position and record throughput, not only the signal indicator.
Force failover
Drop the primary path under controlled conditions, confirm recovery, then hand the site to monitoring with records attached.
Information to gather before design
Cellular results depend on account, carrier and RF details that are hard to recover once a technician is already standing at the site.
- NetCloud account and group structure
- Carrier accounts and SIM activation status
- Candidate antenna locations and mounting surfaces
- Primary circuit details for failover testing
- Site contact and roof or ceiling access
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Is a strong signal-strength value enough?
No. Signal quality, band, congestion, antenna system, plan and real application behavior also matter.
Why test at more than one antenna location?
Building materials and nearby obstructions can materially change usable signal and quality, even across a short distance.
Does a connected backup modem prove failover works?
No. Trigger the approved primary-path failure and measure routing, applications and restoration.
Should SIM and modem identifiers appear on the public site?
No. Keep sensitive identifiers and account data in the protected client closeout repository.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Deploy Cradlepoint cellular across your site list
Carrier readiness and antenna placement decide how these dispatches go. Send your site list, the NetCloud account and group layout, carrier and SIM status, and what each location uses cellular for, whether that is primary access or backup.