Ericsson Cradlepoint Routers, Adapters and NetCloud
Ericsson Cradlepoint offers router/firewalls, cellular adapters, vehicle and IoT endpoints, antennas and NetCloud services. The architecture should reflect whether cellular is primary, failover, out-of-band or simply a modem path for an existing firewall.
Treat components, installation and evidence as one system
Choose a supported architecture from application, capacity, environment, pathway, lifecycle and acceptance requirements—not a single part number.
Choose the cellular architecture
Define primary, backup, out-of-band, temporary or mobile use. Decide which platform owns routing, firewall, VPN, SD-WAN, DHCP and monitoring. An adapter can preserve an existing security edge; a router may consolidate functions. Confirm throughput under the required security services.
Start with applications, speeds, distances, endpoint power, density, resilience, environment and growth. Reconcile the proposed platform with the client standard and installed base. A complete bill of materials must include connectivity, patching, pathways, grounding, management and service parts.
- Primary/failover/OOB use
- Router versus adapter ownership
- Security-service throughput
- Site or vehicle environment
Select endpoint, modem and antenna
Match endpoint and modem generation to carrier, bands, SIM strategy, location and lifecycle. Engineer antennas from cable loss, MIMO ports, mounting, separation, grounding and indoor/outdoor environment. Avoid assuming signal bars alone predict stable application performance.
Physical design should account for rack space, bend radius, fill, heat, power, UPS runtime, optics, polarity, labeling and maintenance access. Validate substitutions before procurement because an apparently equivalent component can alter performance, testing limits, warranty or serviceability.
- Carrier bands and modem
- SIM/APN/data plan
- MIMO antenna and cable loss
- Mounting and grounding
| Component | Use when | Confirm |
|---|---|---|
| Router/firewall | Cellular edge owns routing/security | Throughput, licenses and LAN |
| Adapter | Existing edge retains control | Handoff and management path |
| Vehicle/IoT | Mobility or rugged use | Power, antenna and environment |
| NetCloud | Central operations and lifecycle | Tenant, subscription and roles |
Integrate LAN, WAN and security
Document handoff, VLAN, addressing, NAT, firewall, DNS, NTP, VPN and health-check behavior. For dual-WAN, define route priority, session impact, inbound dependencies and restoration. Coordinate carrier account, APN, static IP and data-plan ownership before dispatch.
Define the manufacturer-supported test method, instrument configuration, reference procedure and pass/fail limits before work begins. Preserve native test files as well as summaries. Marginal results, skipped links and inaccessible areas need an owner and a documented retest or exception path.
- Ethernet/VLAN handoff
- Routing, NAT and VPN
- Health check and failback
- Inbound/public-IP dependencies
Commission NetCloud and failover
Claim the device into the client-owned NetCloud account and assign licenses, groups, roles and configuration. Record RSRP/RSRQ/SINR or model-supported metrics, throughput, latency and loss. Test forced failover and restoration, then deliver SIM, antenna, subscription and support records securely.
Closeout should reconcile drawings, labels, ports, serials, licenses, software, warranties and test results. Link to the current manufacturer support and download portal. Store sensitive floor plans and configurations appropriately while keeping public guidance free of credentials and private network details.
- Client-owned NetCloud tenant
- Subscription and roles
- Signal/performance evidence
- Failover and recovery test
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Assess
Confirm applications, site conditions, standards and existing assets.
Engineer
Develop the architecture, bill of materials and acceptance plan.
Build and test
Install with controlled workmanship and manufacturer-supported tests.
Handoff
Reconcile records, warranties, support and lifecycle 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.
- Applications, scale and growth
- Platform and component compatibility
- Pathway, power and environment
- Testing, warranty and substitutions
- Closeout and lifecycle ownership
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
When is an adapter preferable to a router?
When an existing firewall or SD-WAN edge should continue owning routing and security.
Are signal bars enough for acceptance?
No. Record radio metrics and representative performance at the installed antenna location.
Does failover testing require disconnecting the primary WAN?
Use an approved scenario that proves detection, routing and restoration behavior.
Where are software updates obtained?
Through the official NetCloud and Ericsson support workflow.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Plan a testable network-infrastructure project
Share available drawings, site counts, pathways, distances, applications and turnover requirements. We will help identify the surveys, materials, testing and documentation the project needs.