Searching...
Companion GNX
In AMM 2.17.2+, the AMM will have the TFTP server (which contains the configuration updates and firmware updates for the GNX) embedded so as to more fully manage GNX devices. Due to the TFTP protocol being insecure, when using a GNX device in companion mode, the MG companion host will be configured to route GNX TFTP traffic through the managment tunnel. This feature is only supported if the companion host is an MG90. Non-companion and GNX companion with ALEOS do not support the TFTP protocol through a management tunnel and must still use the common TFTP server.
Note: For more information on enabling routing of GNX TFTP traffic through the MG management tunnel (i.e. setting up an MG90 with a companion GNX), refer to the guide to configure MG90 with a GNX-6 companion.
When the GNX device is setup as a companion to a MG host, all stats and events generated from the GNX device will display on its MG host. This will provide a consolidated view of the GNX device and host MG90, so that only one device needs to be managed, and that a single dot will show on the map when viewing the fleet.
The Companion GNX menu allows deployment of configuration files to GNX devices using the AMM. It can also show the current status of the companion GNX devices.
Upload Configuration
The Upload Configuration tab is used to upload the configuration files for multiple GNX devices to the AMM. Both standalone GNX and companion GNX devices can be configured. This feature is normally used for first deployment of new GNX devices which are unknown to the AMM and for uploading configurations to standalone GNX devices.
Two files are required:
- a list of companion GNX serial numbers
- the GNX core config file.
An additional optional file can also be uploaded that contains a GNX custom config file.
Uploading the configuration files:
1. To add the list of GNX devices that the configuration is to be uploaded to, select 
.
For a template of the list, downloaded it from here
and edit it locally.
Note: If the template is opened in a spreadsheet, ensure that the GNX serial number is a character, not a number, so that any leading zeros are preserved. The serial number should be 12 characters in length.
2. Select 
to add the GNX core config file.
3. Optionally, select 
to add a GNX custom config file.
4. After adding the files, select 
Upload to upload the files to the AMM.
Once the files are uploaded to the AMM, when the GNX device checks in, it will download the new configuration.
Note:
- The GNX configuration on the AMM will always overwrite the configuration on the GNX.
- If a GNX device checks in and the AMM does not have a custom config file for it, then a default config file will be used. The default will instruct the GNX to send default periodic reports to AMM.
GNX Configuration Status
The GNX Configuration Status shows the current companion GNX configurations and firmware versions. This allows administrators to easily view configurations and identify differences.
Note: Standalone GNX devices will not show in the configuration status list. To upload config changes to standalone GNX devices, the Upload Configuration menu needs to be used. It is not possible to see the configuration of standalone GNX devices.
The GNX Configuration Status displays information based on the MG90 gateway. i.e. the MG90(s) must be selected in the tree view, in order to see the companion GNX attached.
Note: The default GNX check in frequency is set to 1 hour. So the Configuration Status will not change until the GNX checks in.
The list of gateways displayed can be filtered by using the following filter fields:
Filter edit box: filters the list on any part inputted into the filter edit box.
Date Range: can be used to select a date/time range for the Last Config Time column.
Selecting an option from the dropdown will display a field where the range can be input.
Note: When selecting Previous months as 1, it will show the previous month information. E.g. If it is February, then it will show companion pairs that were configured in January.
Information is provided in the following columns:
- Gateway: Name of the host MG90.
- GNX S/N: Serial number of GNX.
- GNX Version : GNX firmware version.
- Files: Shows the user the GNX config files on the AMM.
- Last Config Time: Specifies when the user last performed an upload of the configuration files to the AMM.
- Gateway Supports GNX Config: Specifies if the MG90 supports companion GNX configuration. If a GNX device is attached to the serial port of an MG90, but has not deployed the configuration to route GNX TFTP traffic through the managment tunnel, then the value will be No.
Note: Currently it is not possible to easily see if the GNX has downloaded the configuration files. Please call Sierra Wireless Support for assistance.
Upload Config
1. Select the MG90(s)
that have companion GNX devices that need a new configuration uploaded.
2. Select the Upload Config button
.
At least one file is required.
3. Select
to add a GNX core config file.
4. Select
to add a GNX custom config file.
5. Select
to upload the change to the AMM TFTP server. When the GNX companion checks in, it will download the new config file.
Upload Odometer
The Upload Odometer tab is used to set the odometer value in multiple GNX devices at one time. Only companion GNX devices using an MG host can be configured.
Note: The GNX device must have GNX9.05 firmware and be setup as a companion to an MG host device.
1. To upload odometer values to a list of gateways that have companion GNX devices, select
.
For a template of the list, downloaded it from here
and edit it locally.
2. After adding the files, select
Upload to upload the files to the AMM.
Once the file is uploaded to the AMM, when the GNX device checks in, it will set the new odometer value only once.