Searching...
Limitations of AirLink OS routers with AMM 2.18.1
This list provides information about the limitations in functionality that exist between the AMM 2.18.1 and AirLink OS routers.
AirLink AirLink XR80/90 LPWA Radio / OOBM Radio
Not supported on AM/AMM.
Support of AirLink OS routers via the APIs is planned for a later release.
There are no plans for asset management support for AirLink OS routers at this time.
There is no support for certificate management in AM/AMM 2.18.1. This feature is not expected until AM/AMM 2.19 or later. Certificates for MGOS devices will continue to operate.
Remote console support is not available for AirLink OS.
CSV import is not supported for AirLink OS routers
CSV import is not supported for AirLink OS routers.
AMM 2.18.1 supports the following reports for AirLink OS 6.1.x or higher routers with aos-delsadapter 2.0.x or higher :
- Network > Link Utilization (including multi-APN support)
- Network > Coverage Trail
- Network > Coverage Map
- Tracker > Gateway Trips
- Tracker > Trip Replay
- Advanced > Event Viewer
If aos-delsadapter 2.0.x is not used, then the newly added reports for 2.18.1 may appear blank or inaccurate.
Only the Event Viewer report is supported for AirLink OS 5.3 routers with aos-delsadapter 1.0.x. Other reports generated for AirLink OS 5.3 routers may appear blank or inaccurate.
Telemetry Support is planned for a later release.
Total Reach is a MGOS specific feature and there are no plans to add support for AirLink OS at this time.
Third party container management is not supported in AMM 2.18. It will be considered for future development based on customer requirements. Third party containers are still supported and managed through local AirLink OS UI.
Factory reset AirLink OS router will default back to ALMS
If the AirLink OS router is factory reset, it will report back to ALMS and will need to be reconfigured to work with the AMM.
Upload for AirLinkOS process is different
When uploading a JSON configuration to an AirLink OS router, you only need to select Configuration > Deployment > Upload for AirLinkOS, as it will automatically upload the configuration when the AirLink OS router checks in. There is no Apply needed.
AirLink OS router Re-registration requirement
If the AirLink OS router is deregistered from the AMM, then it must be factory reset before it can be registered again. This applies regardless if it is the same AMM or a different one. For more information, see Re-registering an AirLink OS router on AMM
Remote AirLink OS web UI access option
The option to remotely access the AirLink OS web UI, is found under the label Access LCI in the gateway context menu.
Only a limited set of stats is available for AirLink OS routers. See Features Supported for AirLink OS routers
Limited gateway tree context menu options for AirLink OS routers
Only a limited set of gateway tree context menu options is available for AirLink OS routers. See Features Supported for AirLink OS routers
AMM Template is not supported for AirLink OS
Building a configuration template using AMM is not supported for AirLink OS routers.
AirLink OS routers can be added even if AirLink OS Support flag is set to No
AirLink OS routers can be added even if AirLink OS Support flag is set to No. If at a later date, the AirLink OS Support flag is set to Yes, then the AirLink OS routers already added, will need to be deleted and then re-added, so that the AirLink OS Keys are created.