Searching...

Matching results

    Release Notes for AM/AMM 2.18

    AirLink Manager (AM) / AirLink Mobility Manager (AMM) 2.18 is a major release of the AirLink Manager platform. This release introduces foundational support for AirLink OS (AOS) devices, enabling customers to begin managing their AOS fleets through AMM.

    While AOS support on AMM will continue to expand in subsequent releases, AMM 2.18 delivers the basic AOS device management features needed to start customer trials and prepare for broader adoption.

    AMM 2.18 marks the first phase of AOS device support, delivering the essential building blocks of management: registration, configuration, monitoring, and upgrades. These features create the foundation for deeper AOS integration in upcoming releases, where functionality will be continuously enhanced.

    This release also includes general security patches and bug fixes.

    1 Release Information

    1.1 Officially Released Versions

    AM/AMM 2.18 was officially released to General Availability on Oct 30th, 2025.

    1.2 Platform Support

    AM/AMM 2.18 has been tested on Dell R250 and R650 servers and on VMWare ESXi 7 and later.

    1.3 Browser Support

    AMM 2.18 has been tested on Google Chrome, Firefox and Microsoft Edge. Users that attempt to use a browser that is not supported will get a warning and may experience some issues.

    1.4 Semtech Gateway Support

    The following table shows the minimum software version needed on the gateways to be used with AMM 2.18.

    		AOS 5.3 MGOS 4.4.2.1 ALEOS 4.16
    XR90 ✔

    XR80 ✔

    XR60 ✔

    RX55 Wi-Fi Plus ✔

    MG90

    		✔

    RV50X/RV55

    		✔
    MP (All)

    		✔
    LX (All)

    		✔

    2 Key Features and Enhancements

    2.1 Unified Dashboard

    AirLink OS routers now appear on the AM/AMM Dashboard alongside ALEOS and MGOS devices, giving administrators a single consolidated view of their complete fleet.

    As part of the initial AirLink OS integration, this release introduces remote UI access for AirLink OS routers. From within AM/AMM, administrators can securely open the AirLink OS web interface of a router to:

    • Configure and manage AirLink OS device settings remotely
    • Monitor live device status and performance
    • Download troubleshooting logs and perform diagnostics
    This capability enables full remote configuration, monitoring, and maintenance, eliminating the need for physical site visits and improving operational efficiency.

    2.3 Monitoring & Troubleshooting

    Events generated by AirLink OS routers are displayed on the Events tab.

    Note: Limited event types are supported for AirLink OS devices in this initial release.

    AirLink OS devices that provide GPS data are displayed on the Map and Tracker tabs. Regular updates and customizable vehicle icons provide a familiar fleet-management experience consistent with existing device families.

    Key operational statistics from AirLink OS devices are now available in the Stats tab.

    Note: A limited set of metrics are supported in this release; additional telemetry support will be introduced in future versions.

    2.4 Configuration Templates

    Administrators can upload and distribute AirLink OS JSON configuration templates directly from AM/AMM. This feature enables centralized and scalable configuration management across the fleet.

    2.5 Software Repository and Distribution

    AirLink OS firmware packages and applications have been added to the public software repository. Users can download firmware images, upload them into AM/AMM, and distribute updates using the same workflow established for ALEOS and MGOS routers.

    AirLink OS routers must be registered using the “Add Gateway” workflow before connecting to AM/AMM. A new AirLink OS Key Management feature enables administrators to generate secure registration keys for device onboarding.

    2.7 System – Log Retention

    AMM now includes an automated gateway-log cleanup job. Set GatewayLogRetentionDays in Admin > System > Configuration to automatically purge old logs and reduce disk full risks. (Upgrades import your prior retention setting; new installs require setting a value to enable the job.)

    2.8 Report Retention Period

    AMM now automatically purges generated reports older than a configurable retention period (default 365 days) to reduce storage use. You can change the retention in Admin > System > Configuration. Files and their entries are cleaned up automatically during the daily maintenance run.

    3 Customer Addressed Issues
    Reference Description
    2672, 2829 Change default page size on AMM dashboard
    7483, 7614, 8271, 8606 Recurring reports relative time frames not properly expanded on individual runs
    8127 Incorporate support scripts in future AMM releases.
    8452 Current MSCI self-signed certificates expiring soon
    8613 User unable to login to secondary AMM.
    8752 MG90 Template fails to update UpTime Extension After Ignition

    4 Security Vulnerabilities

    All relevant security fixes have been implemented in this release to ensure the system remains protected against known vulnerabilities. The update strengthens overall platform security and maintains compliance with current best practices.

    5 Outstanding Issues

    There are a number of known issues discovered that will be addressed in a future AM/AMM release.
    Reference Description Notes
    15762 Shutdown reason shows 0 when AirLink OS gateway rebooted from AMM When an AirLink OS gateway is rebooted from AMM, the ShutdownReason stat shows as 0.
    15743 Events can be lost on reboot If the gateway loses connectivity for some time before a reboot, events collected during this time will be lost
    15659 Callup Link Timer did not reset when gateway powered off After complete power removal, gateways may boot with a stale clock and send early events with older timestamps, impacting AMM/ALMS reports. XR60/XR80/XR90 are not affected in proper installs with continuous battery power; RX55 can show this issue after power-off.
    14252 Unable to see Cellular WAN dels events on AMM when APN mode is set to Multi Currently dependent on AirLink OS software support
    12863 After a fresh install, API stops working after enabling Admin > System > Configuration After AMM GUI is running, and installer uses Admin > System > Configuration to complete configuring the AMM, the AMM must be rebooted so that all configuration settings are fully implemented before using API.
    12832 Callup Timer not accurate Callup timer can show less than expected due to an addition error.
    12789 User List shows empty data after clicked on “Cancel” button. Refresh will re-populate the list.
    12755 When editing a threshold, the Stats for Gateway Type field doesn’t show AirLink OS option This field is used for filtering stats. Filtering AirLink OS stats can be done by changing the gateway selection on the gateway tree.
    12752 Default Threshold values for AirLink OS gateway are outside normal range. Define a threshold with the same name, so that it overwrites the default.
    12588 Download AirLink OS keys limited to 100 on a page To download more than 100, use Download Batch. If the keys are spread out over a page, use the search filter to narrow the range displayed, so that the relevant keys are on one page.
    12491 AirLink OS Opevn VPN flag should not be enabled when certificates are not uploaded to AMM Ensure certificates are uploaded to AMM.
    3028 AirLink OS 5.3.66 does not support AMM HA

    HA support is planned for an upcoming future AMM release. After a failover, AirLink OS gateways should be rebooted from the AMM. The exception is the RX55 gateway, where the LWM2M channel does not recover after an HA failover and requires a local reboot. It is recommended to NOT deploy AMM HA with AirLink OS 5.3.66.

    TOP