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.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- 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.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- 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.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- 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.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- 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.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
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.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.