Cradlepoint configuration

This topic is intended for Axon Evidence administrators. For user-based topics, start with Introduction.

Viewing this page requires the ALPR System Administration permission.

Cradlepoint NetCloud Manager™ (NCM) is a next-generation software and services platform that provides software-defined and cloud-delivered management, connectivity, security services, and more. Sign in at www.cradlepointecm.com.

This topic includes the standard recommended configuration for operating a Cradlepoint IBR900 series router with the Axon Fleet system. Your purchase of Cradlepoint routers from Axon generally includes NetCloud licensing and a NetCloud administrator was chosen at the time of purchase and should have received an invitation for account setup. Your administrator or designee must be available for access. Axon does not have access to your NetCloud account.

For more information about Cradlepoint devices or NetCloud Manager, see:

Note Each device should be registered and configured from NetCloud Manager. All changes should be made from the NCM interface and not the local device UI. However, the device changes outlined below may be referenced and applied via the local UI when necessary as a last resort.
Important An active, 2FF size SIM should be installed in the router's internal modem. Use SIM slot 1. For the IBR900, slot 1 is closest to the bottom of the router. For remote management of Cradlepoint routers, the router must have internet access and should have a SIM installed with no restrictions on access to Cradlepoint servers. When using an APN with your cellular provider, network administrators must ensure access as outlined in Series 3 NCM Access via a private-network.

 

Fleet 3 requirements and recommendations

Management

To help manage your pool of Cradlepoint routers:

  • Create device groups for testing and production
  • Configure device group
  • Move devices into groups

Requirements

  • Hub and computer must be connected directly to router ethernet port.
  • MDT should be connected to router ethernet port. MDT to router Wi-Fi works.
  • MDT and hub must be on the same subnet.
  • If using Wi-Fi Direct, ensure http://fleetevidenceping.com (52.247.154.57) is only reachable over a Wi-Fi interface.

Recommendations

  • Change the router local domain to "local" to enable DNS fallback.
  • Configure ignition sensing shutdown delay to match Fleet 3 to enable video upload and firmware download while vehicle is off.

Group creation

Axon recommends creating three new groups to facilitate deployment and future scalability:

Note Groups are model specific. Be sure to select the proper device model when adding groups. If you are unsure which device to select, contact your Axon sales engineer.
  1. Canary (optional in-house test) – Used to support lab environments only. It is designed to be used with a device at a workbench or otherwise installed in a non-mission critical setup. This is used for testing settings alterations and firmware updates before pushing them to the field group.
  2. Field test – Should contain limited field units. This group is the second phase of testing configuration changes, used for final validation before pushing alterations to the production group.
  3. Production – Contains the remainder of the deployed fleet. Deploy alterations to configurations here as a final phase only after testing in previous groups.

Use of a phased deployment for upgrades and alterations provides a smooth transition for the devices. In the event of any disabling changes, canary and/or test group changes can be reversed and mitigate system-wide outages.

Important Some configuration changes and all firmware upgrades will cause online devices to go offline while the updates are applied. In some cases, the units may be offline for up to 15 minutes. Please take caution when applying updates to avoid downtime during critical events. Offline devices will update as soon as they connect after the update has been executed in NCM.

Create the groups using the instructions at Set up a group to manage endpoints.

Complete the following fields when adding a new group:

  • Group Name – Choose a name as outlined above.
  • Sub-account – This defaults to your main account. Click the Change link to select one of your sub-accounts.
  • Product – Select your product name from the dropdown list (such as IBR900 or IBR1700).
  • NetCloud OS – Select a NetCloud OS version from the drop-down list. This NetCloud OS version will be pushed to devices when you add them to the group.

At any given time, the latest available NetCloud Operating System within Netcloud, for each Cradlepoint model, has been verified and approved for use with all supported generations of Axon Fleet.

Update operating system

When necessary, update the NCOS from NCM see How to upgrade router firmware via NetCloud Manager.

When updating NCOS, the preferred method is to update the groups in phases: Canary, Field Test, and then Production. As a general practice, routers should not be moved between groups for the sole purpose of updating. (such as creating a new group with an updated NCOS and then moving devices from group to group).

Group configuration

Apply device settings at a group level.

Copy group configuration

Once you have completed the initial group configuration for the Canary group, apply the configuration to the remaining groups. See How to back up router configurations in NCM.

Move devices into groups

Move all devices into a group so each receives the proper group settings. Split devices between the groups as needed. Preferably, place a workbench or IT vehicle router in the Canary group, at least two routers in Test, and the remainder in Production. These numbers will vary based on the size of your fleet. See Manage your Cradlepoint Devices.

 

Flock Safety integration Recording ï this topic ð Axon Evidence admin settings

 

Last modified - 19 February 2026