Gateways

The Gateways panel is used to add, modify, delete and reboot gateways.

Adding a new gateway

Click on Add to open the Add or Edit Gateway panel.

Enter the following fields:

• ID^*: electronic serial number (used to uniquely identify the gateway).

  Note: For issues setting serial numbers for GX440 devices, see Adding GX440 Devices with Long Serial Numbers to an AMM .

• Name: enter the name or alias for the gateway. Note that as of AMM 2.17, angled brackets “<” and “>” are no longer allowed in the names of gateways. AMM 2.17 will erase the angled brackets in existing names when upgrading from an older version of the AMM.

  Note: in AMM 2.16.2+, the Name field for an ALEOS device will be automatically populated with the value of MSCIID 5023 if no name has been assigned to the device during gateway creation or import into the AMM. For more information see Commonly Used MSCIIDs .

• Vehicle Type: specifies the type of vehicle in which the gateway is installed. For more information Vehicles . Note that a vehicle type defined by a different user group than that associated with the current gateway, cannot be assigned to the gateway.
• Group: use the drop-down menu to select the group to which the gateway will belong.
• Update DNS Servers (applicable only for MG devices): use the drop-down menu to select the DNS server to which updates will be sent. Note: before a DNS server can be assigned to a gateway, it must first be created. See DNS Servers . Click on + to add additional DNS servers and - to remove them.
• Customer: enter the customer information for the gateway.
• Location: allows you to set the location of ALEOS and MG devices manually, so that they appear on the map even if the device does not have GPS, or does not have the ability to receive a GPS signal. If the Internet is available, a popup will appear when clicking on this field, allowing you to enter an address or geo coordinates, see the location on a map, and set that as the device’s location. For more information about this feature see Setting Device Locations .

  Note: A manually set location is displayed when the map is viewed with the default time range of “Today” or “All”. A manually-set location will be overridden by a GPS location if available within the user-selected time range. Manually set locations are supported in AMM 2.16.2+.

• Contact: enter the contact information for the gateway.
• Notes: enter additional information regarding the gateway. This can be used to segment a fleet. For example, when using search filters, entering “Laptop equipped” or “Winter Tires” will only display vehicles equipped with laptops or winter tires.
• Icon URLs: leave empty - reserved for future use.

^* denotes a required field

Click Save to create the new gateway.

For additional methods of adding gateways see:

• Adding Multiple Gateways to an AMM
• Transitioning AirLink Gateways from ALMS to the AMM

Deleting a Gateway

Gateways can be deleted by clicking in the checkbox next to the gateway label and then on Delete. Deleting a gateway removes it from the AMM’s Gateway Tree. After deletion, the gateway will no longer report to the AMM and existing information about the gateway will no longer be available.

Editing a Gateway

To edit an existing gateway, click on its gateway link in the ID column to open the Editing panel (or click on Edit).

Gateways can be moved from one group to another from this panel.

If when moving a gateway, there are linked configuration templates found on the gateway(s)’s parent group(s), then a popup will show, allowing the user to unlink the configuration template(s).

E.g. if “template A” and “template B” are linked to the gateway, but only “template A” is also linked to the gateway’s parent group, then when the gateway is moved to a new group, only linked “template A” has the option to be removed from gateway. “template B” remains unchanged.

If there are linked configuration templates found on the group and/or parent group where the gateway(s) is moving to, then a popup will appear requesting confirmation to deploy the linked configuration template(s) to the gateway.

A Summary popup will display allowing the confirmation of the deployment of the template(s), with the option to link the template(s) to the gateway(s).

The changes will be logged in the User Activity screen.

Note: administrators can add gateways before they go online. When a gateway boots up, the AMM matches it based on the ESN. This enables administrators to pre-assign gateways to a fleet and to configure additional properties.

Note: The AMM server has a mechanism called authunits lookup which will reject any incoming tunnel connection requests if the requesting device serial number is not in the authunits lookup list.

• This is not enabled on Sierra Wireless-hosted AMMs, but is enabled on customer hosted AMMs.
• Prior to AMM 2.17, the authunits lookup file required command-line updating whenever new devices were added to the fleet.
• As of AMM 2.17, devices that are added via the Gateways tab are automatically added to the authunits file.
• Best Practice : Gateways should be added to the AMM as soon as the serial number is known either via the Gateway tab, or through importing a CSV list. If the gateways connect to the AMM without a tunnel, then problems could occur when downloading software or configuring. If this situation occurs, the authunits file will need to be manually updated. Please contact Sierra Wireless support for assistance.

Rebooting a Gateway

To reboot a gateway(s), click in the checkbox(es) next to the gateway label and then on the Reboot button. A popup screen will appear showing which gateways will be affected and which will be unaffected. Click on the Unaffected Gateway(s) tab to see the reason why the gateway(s) will not be rebooted.

Note:

• MG90(5G) must have MGOS version 4.4.1 or higher to reboot using this workflow. MG90(4G,5G) must have MGOS version 4.4.2 or higher. If the MGOS version is lower, refer to Request Reboot via Gateway Tree.

• all ALEOS platforms and versions are supported.

When ready, click on the Submit button and a reboot operation will be created for each affected gateway. If none of the selected gateways can be rebooted, then the Submit button will be disabled.

Note: the reboot operation will expire at midnight in 10 days from the date of creation of the operation.

If any operations are created, then a notification banner will appear at the bottom of the screen. There will be a link to take you directly to the Operations page.