Once the captive modem has successfully peered with the controller, the modem appears in Connection Manager with the prefix "Captive Modem."
If an issue is experienced while setting up Captive Modem, use the following to troubleshoot the issue:
Verify that the controller and adapter/captive modem are running the same version of NCOS with the following commands on the controller console. The adapter example below is running NCOS 7.22.60 release.
cat /status/remote_modem "channels": "mac": "00:30:44:00:00:00", "status": "active", captive_modem get 00:30:44:00:00:00 status/fw_info "major_version": 7, "minor_version": 22, "patch_version": 60,
Verify that the adapter was unlicensed and unregistered from NetCloud Manager in the exact steps as specified above.
Ensure that a different adapter has not already been connected to the controller and set up for Captive Modem.
From the command-line interface (CLI) of the endpoint functioning as the controller, issue the following command:
cat status/remote_modem.
In the informational section labeled Modems, verify that the Name and Type fields are both set to remote_modem.
Verify that next to the Modem line, a WAN interface ID is present and that the value is not blank.
The following commands may also be used in the CLI to troubleshoot from the controller router:
get config/discovery
Indicates if the controller code is loaded and properly running. It should return the following:
{ "enabled": true, "multicast_address": "239.0.0.12", "multicast_port": 11100 }captive_modem list
Shows the MAC addresses of all peered captive modem adapters.
captive_modem --help
Lists the help information available for the commands in this context.
log captive
Displays logs of the connected captive modems.
In the case that the above has been verified and the captive modem is not getting a cellular signal, see No Internet or Connection Issues.
When using an adapter with a controller-capable router, the adapter must be online before connecting it to the router.
Unlicensed adapter and controller capable router:
Pending adapter and controller capable router:
Online and licensed adapter and router:
Troubleshooting Multiple Captive Modem Configuration Issue
When multiple captive modems are configured on a single controller device, the system may report the following error:
RemoteModemMaster Error: Route Could Not Be Added (Object Exists)
This error indicates a routing conflict that prevents one or more captive modems from successfully establishing a connection. This issue occurs in 5G Standalone (SA) IPv6-only environments. When an IPv6-only connection is provided by the carrier, the modem uses CLAT (Customer-side translator) to enable IPv4 communication. By default, modem-based CLAT assigns the same IPv4 address (typically 192.0.0.2) to each captive modem. When multiple captive modems attempt to use this same address, duplicate routes are created in the routing table. Duplicate routes are not allowed by the system, which results in this error and preventing secondary captive modem(s) from connecting.
To resolve this issue, configure the affected Connection Manager profiles to use IPv4/IPv6 mode instead of relying on modem-based CLAT. When IPv4/IPv6 mode is enabled:
NCOS manages CLAT instead of the modem.
Each modem is assigned a unique (randomized) IPv4 subnet.
Duplicate route conflicts are eliminated.
All captive modems can establish connectivity as expected.
For more information to configure IPv4/IPv6 on the WAN profile, see Configuring IPv6.
Note
Ensure that the IP Mode for each affected Connection Manager profile is set to IPv4/IPv6.