Searching...

Matching results

    Basic Reporting for ALEOS Devices

    All ALEOS devices are configured from the factory to report to AirLink Management Service (ALMS) which is a hosted, secure cloud-based application. However in order for devices to send basic report information to a hosted or on-premise AMM server, each device requires a few specific configuration changes. Setting up basic device reporting to an AMM server will enable the ability to monitor the device, run detailed reports, push software updates, configuration changes and password changes.

    Additional Information:

    • Device Limitations and Server Requirements for Basic Device Reporting
      • ALEOS devices must be running ALEOS 4.4.x or higher in order to communicate with an AMM server. Some reporting and other features require a minimum 4.8.0 and AAF application support.
      • AMM servers must be running version 2.15 or later for ALEOS device compatibility. Several features and reports are only available in later versions. For TLS peer verification, the server must have a valid TLS certificate.
      • AMM 2.16.2 supports TLS v1.0, v1.1 and v1.2.
      • AMM 2.17+ will only support TLS v1.2. ALEOS devices must be running the following versions in order to be compatible with AMM 2.17+.
        • ALEOS 4.4.9 or later (LS300, GX440, GX400)
        • ALEOS 4.9.4 or later (GX450, ES450)
        • ALEOS 4.11.1 or later (RV50, RV55, MP70, LX60, LX40)
    • Configuration Steps for Basic Device Reporting

      For the device to report in to the AMM server, the following settings need to be configured in the template, either through an ALMS-created template or locally using ACEmanager:

      1. Navigate to AirLink Management Service > Services/ALMS and set the ALMS protocol to MSCI. Note that in some older ALEOS versions, there may not be a protocol option, since LWM2M wasn’t deployed yet.
      2. Configure the Device initiated interval (minutes) to a low number to facilitate initial communication and configuration. It can be increased remotely once communication is established and validated.
      3. Navigate to Services/ALMS > MSCI section, and enter the server URL in the following manner: https://[server_address_or_FQDN]:8083/msci Note that the protocol must be https using port 8083, and “msci” is case-sensitive as it is a Linux path configured on the server. Not setting these precisely will result in communication failure.1
        Also note that for connecting to hosted servers, the server name (FQDN) must be used and never the IP address. Hosted AMM servers in AWS do not have fixed addresses.
      4. TLS Verify Peer Certificate must be disabled, unless:
        • The device is reporting in to a hosted Sierra Wireless AMM server with a valid TLS certificate; or
        • The device is reporting in to a private AMM server that has been deployed with a valid TLS certificate.
          Note that if the TLS Verify setting is not set correctly for the environment, this will result in a communication failure. This valid certificate is a pre-requisite for the AMM Management Tunnel.
      5. If you will be using any of the additional features of Sierra Wireless-provided AAF applications, then the ALEOS Application Framework must also be enabled. While you can do this remotely after the fact, it is more convenient and efficient to do it at the time of building the basic template.
        • To enable AAF, navigate in ACEmanager to the Applications > ALEOS Application Framework tab.
        • In the General section, set the ALEOS Application Framework to Enable.
          The device must be rebooted for the settings to take effect before it can successfully connect to the server. After rebooting, you can check the connection using the Connect button in ACEmanager, or adjust the reporting interval.

      1. The device-to-server communication can use http on port 8082, however this will send data to the server in cleartext. Since it is cleartext, the system limits the data being sent to exclude any passwords, so remote password management will not be possible. Password management is only supported over encrypted https via port 8083. [return]
    • For a list of related ports and protocols for this functionality see: ALEOS TCP/UDP Port Summary.
    TOP