Laird Sentrius RG191+LTE User Manual Download Page 37

Page: 37 / 56

http://www.lairdconnect.com

Americas

: +1-800-492-2320

Europe

: +44-1628-858-940

Hong Kong

: +852 2923 0610

This works much like it does with the web User Interface (UI). When the system administrator has a new firmware release to
load, they will update the

InternetGatewayDevice.Laird.GatewayManagement.Versions.FirmwareUpdateURL

. The value

is the link to download the firmware. This link always points to a fw.txt file. Once that is done, the gateway will respond with
success, and download the firmware in the background. A remote user would then poll for

InternetGatewayDevice.Laird.GatewayManagement.Versions.FirmwareUpdateStatus

to be set to “1” indicating that the

firmware was successfully downloaded and is ready to reboot to switch to the new firmware. The system administrator would
then issue the TR-

069 “Reboot” command to reboot the device. After the reboot, the gateway will check in again and be

running the new version. Note that settings (including remote management) are preserved across a firmware update.

Configuration files and certificates can be uploaded to the device. These configuration files are called

‘vendor configuration

files

’ in TR-069 terminology. An ACS can be commanded to push these to a device or group of devices. The vendor

configuration file can change several settings in bulk. It is useful to (re)configure a batch of new devices in the field. These
settings include, LAN, WiFi, and LoRa radio settings (including the channel plan and other radio settings).
A strategy to deploy configurations to the field is to modify a unit locally to the way you want it. Download the configuration file
via TR-069 from a locally configured gateway, then upload that generated configuration file to be pushed to all the units once
the system administrator is satisfied that all the settings are correct on the

‘golden unit’. A download is initiated by the ACS

with the type “3 Vendor Configuration File”, and an upload is also initiated by the ACS with the type “3 Vendor Configuration
File”. The ACS will not put a file extension on the downloaded file. It is a compressed tarball (.tar.gz) file.
See the documentation for your ACS to determine how to initiate the

‘3 Vendor Configuration File” upload command.

Initiate a download by the ACS with type

2 Vendor Log File

. This returns the log data. The same log data that can be obtained

by the web interface. It is viewable with a text editor.

The device configuration can be downloaded by the ACS with type

3 Vendor Configuration File

. This allows a user to configure

a device locally to their specification, then save the settings for distribution to a larger group of deployed units. This file will
include LoRa settings, Wi-Fi settings, and IP settings. This includes the channel plan used by the Semtech UDP packet
forwarder. This file can be uploaded to deployed gateways to update their configuration to match the device that was updated
locally. It is always good practice to locally test any configuration changes you make, so that you know it works the way you
want it to before deploying the changes to more units deployed in the field. See the documentation for your ACS to determine
how to initiate the

3 Vendor Configuration File

download command.

The following tables show all of the parameters supported by the gateway along with a description of each. Each entry in the
table is designated as read (R), write (W), or object (O). The items designated as objects are nodes in the data model. All
parameters are designated with an R, W, or both.

The root of the data model is InternetGatewayDevice.