Knowledge Hub · Connectivity

Do we need Peplink InControl 2 for a FirstNet managed Peplink service?

Bonded Connectivity with Peplink · Answered by FirstNet Technology Services

Short answer

For a managed service, yes. Peplink devices can run locally without it, but InControl 2 provides the single-pane operations, alerting, firmware control and per-link visibility that FirstNet's day-2 service relies on.

In detail

InControl 2 is Peplink's cloud management platform. In a FirstNet deployment it is run by FirstNet on your behalf, and it underpins:

  • Alerting: InControl 2 alerts feed the FirstNet NOC, so faults are ticketed and managed through one support desk.
  • Per-link visibility: you can see when failover was active and for how long, for example during load-shedding.
  • Firmware control: device firmware is managed consistently across the estate.
  • Single-pane operations: one view across all sites and devices.
  • Pilot reviews: InControl 2 data is used at the 30-day review of a pilot to show how often the bonded edge prevented an outage.

Onboarding to InControl 2 is a standard step in FirstNet's Peplink rollout. It follows the site survey, link selection and hardware sizing, and comes before tunnel termination design and the shipping of pre-staged kit for installation and acceptance testing.

Source: FirstNet Bonded Connectivity with Peplink service page →

Didn’t answer your question?

Call