Transitioning AOS Gateways to the AMM

This section describes how to transition AOS gateway(s) to an AMM.

Overview

To use the AOS gateways with the AMM, ensure that both the AMM and the AOS gateways meet the required software versions:

• The AMM must be running version 2.18 or later.
• Each gateway must be upgraded to version 5.3 or later.

To transition an AOS gateway from ALMS to AMM, the following steps should be done:

1. Upgrade the gateway (if required). If the AOS gateway is running an older AOS release, upgrade it to 5.3 or higher. This must be done using ALMS or by upgrading the gateway locally using the AOS web UI.

Note : The AOS gateway will need to be factory reset if it is transitioning from one AMM server to another.

2. Add the gateway to the AMM.
3. Unique keys will be automatically created for each AOS gateway when they are added to the AMM.
4. Ensure the WAN connection on the AOS gateway is up.
5. Configure the AOS gateway with its unique keys for communication with the AMM.
6. Once the AOS gateway is communicating with the AMM, reboot the gateway.

Note :

• An AOS gateway can only report to one management server.
• Once the AOS gateway is managed by AMM, future upgrades will be done from the AMM.

Adding an AOS gateway to the AMM

Adding an AOS gateway to the AMM:

1. Login to the AMM as a user with access to Admin > Devices > Gateways.

2. Click on the Add button to display the “Add or Edit Gateway” screen where configuration settings can be changed, as shown in the figure below:

   

3. Enter the ID of the AOS gateway. This is the electronic serial number.

4. Enter the Name that is used to identify the gateway.

5. Optionally add Group, Location, Contact and Notes.

6. Click Save. A CSV file titled _sierrawireless_bootstrap_keys will be created. Save it to a local location where you can easily find it.

Adding multiple AirLink OS gateways to AMM

To transition multiple AirLink OS gateways to the AMM, use the following procedure

1. Login to the AMM as a user with access to Admin > Devices > Gateways.

2. Click on up arrow to import the Gateway List. If need be, the template can be downloaded from this screen.

   

3. Select the file with the multiple AOS devices in it. The file can have a mix of different types of gateways.

4. Optionally enter a Batch Name. The Batch Name is a tag that can be used to categorize when an AOS gateway was added. It is used in Admin > Devices > AirLink OS Keys. The Batch Name should be limited to 100 characters.

   

5. Click on Start

6. The AMM will process the entries and show a report. A CSV file, titled _sierrawireless_bootstrap_keys, will be created containing all the AOS devices added. Save this file to a location where it can be easily found.

Configuring an AOS gateway for AMM

1. Open the _sierrawireless_bootstrap_keys file using an editor or spreadsheet application.

2. Login to the AOS gateway as user admin

3. Navigate to System > Device Management > Device Manager

4. You will see that the Device Manager is set to ALMS. Change it to AMM

   

5. Navigate to System > Device Management > AMM LwM2M. From the _sierrawireless_bootstrap_keys file, copy the BOOTSTRAP URI for that particular AOS gateway and paste into the AMM LwM2M field BOOTSTRAP URI .

6. From the _sierrawireless_bootstrap_keys file, copy the Bootstrap Identity for that particular AOS gateway and paste into the AMM LwM2M field BOOTSTRAP IDENTITY

7. From the _sierrawireless_bootstrap_keys file, copy the Bootstrap Secret Key for that particular AOS gateway and paste into the AMM LwM2M field BOOTSTRAP SECRET KEY

   

8. Save the changes on the gateway. The AOS LwM2M process will start and the STATUS will change to Starting and if there are no errors, change to Connected.

   

   Warning : Ensure that the WAN connectivity is not interrupted until the LwM2M process, the AOS-AMM-Dels-Tunnel and the aos-delsadapter is running.

9. Once the LwM2M is connected, the OpenVPN tunnel process will automatically start. To check the process, go to Networking > VPN > OpenVPN Tunnels and view the SYSTEM TUNNELS.
   

   

10. To check if the container is being pulled, navigate to Apps > Container Applications (Early Adopter) > Images. Under SYSTEM IMAGES, the DelsAdapter status should start and transition to show as ready.

    

    

11. Once the aos-delsadapter status is ready, the AOS-AMM-DelsAdapter should have a status of running.

    

12. The gateway should begin reporting all its stats to the AMM dashboard.

    

13. Reboot the gateway.