Update Configuration

Lantronix Provisioning Manager allows you to update device configuration files using a batch process or on a per device basis.

Batch Configuration vs. Per Device Configuration

The batch configuration update process allows you to apply a single configuration file to multiple devices, while the per device configuration update process allows you to apply a configuration file to a specific device. The per device configuration update may be applied to one device or to multiple devices, as long as there are configuration files for each of the devices selected.

You may generate configuration files in different ways; your options include using Percepxion or the device itself, such as the web interface. For information on how to generate a configuration file, refer to the Percepxion online help or to the user guide for your device, depending on the method you choose. If you generate the configuration file from Percepxion, the output file name from Percepxion will include the device ID. If you generate the configuration file from the device, the output file name may include the device's serial number or some other name.

You will need to make sure that the configuration file name matches the requirements for LPM as described in Per Device Configuration Update. When executing the configuration update procedure, LPM searches for devices either by serial number or device ID so you need to specify which method it should follow according to the configuration file name.

Batch Configuration Update Preparation

Configure LPM settings:

• Configure SFTP/FTP Server Settings if you are updating OOB devices.

Prepare the configuration file:

1. Ensure you have the correct and valid configuration file.
2. Ensure that the configuration file name ends in one of the following formats:
   • -slccfg.tgz for SLC and SLB devices
   • -emgcfg.tgz for EMG devices
   • .xml or .xcr for IoT devices
   • .rec for CoBos-based devices
3. If using an external SFTP/FTP server, store the configuration file on the server in the folder specified in Path in Server Settings.

Batch Configuration Update Procedure

To apply a single configuration file to multiple devices:

1. Click Provision on the side menu.
2. Select one or more devices to apply the configuration to. They must all be the same type of device (for example, all SLB devices).
3. Click Update > Configuration.
4. The radio button next to Batch Configuration Update is already selected.
5. If using the built-in SFTP server or working with IoT devices, click Upload Configuration File and select the configuration file. If using an external SFTP/FTP server, type or paste the name of the configuration file in the Select File field.
6. Choose whether to reboot the device after the update using the checkbox. This option is not available on all devices.
7. Click Update or press Enter to begin the update. While the device is rebooting, connectivity is disrupted.

Check the Operation Status and Progress columns to see the progress of the configuration update.

Per Device Configuration Preparation

Configure LPM settings:

• Configure SFTP/FTP Server Settings if you are updating OOB devices.

Prepare the configuration files:

1. Ensure you have the correct and valid configuration files.
2. Ensure that the configuration file name adheres to one of the following formats:
   • Update using Serial Number (base name + serial number + device type file extension)
     • <base name><last four characters of the device's serial number>-slccfg.tgz for SLC/SLB devices
     • <base name><last four characters of the device's serial number>-emgcfg.tgz for EMG devices
     • <base name><last four characters of the device's serial number>.rec for CoBos-based devices
     • <base name><last four characters of the device's serial number>.xml or <base name><last four characters of the device's serial number>.xcr for all other devices
   • Update using Device ID (base name + device ID + device type file extension)
     • <base name><32 character device ID>-slccfg.tgz for SLC/SLB devices
     • <base name><32 character device ID>-emgcfg.tgz for EMG devices
     • <base name><32 character device ID>.xml or <base name><32 character device ID>.xcr for all other devices
3. If using an external SFTP/FTP server, store the configuration file on the server in the folder specified as Path in Settings.

Examples of Configuration File Name

For update using Serial Number in the file name:

test1024-slccfg.tgz

where "test" is the base name, "1024" is the last four characters of the serial number, and "slccfg.tgz" is the device type-specific file extension. The base name must be the same for all devices.

For update using Device ID in the file name:

test00204AH7YER5D9YDZRS5HAZW5QRXCQWX-slccfg.tgz

where "test" is the base name, "00204AH7YER5D9YDZRS5HAZW5QRXCQWX" is the 32 character Device ID, and "slccfg.tgz" is the device type-specific file extension. The base name must be the same for all devices.

Per Device Configuration Update Procedure

To apply a unique configuration file to each device:

1. Click Provision on the side menu.
2. Select one or more devices to apply configuration. They must all be the same type of device.
3. Choose the appropriate update option Per Device Configuration Update (Using Serial Number) or Per Device Configuration Update (Using Device ID) according to your requirement.
4. In the Base Name field, provide the base name of the configuration files. The base name must be the same for all files.
5. If using the built in SFTP server or working with IoT devices, click Browse next to the Path field and select the folder that contains the configuration files. Ignore this step if using an external SFTP server because LPM will use the path that was specified in Server Settings.
6. Choose whether to reboot the device after the update using the checkbox. This option is not available on all devices.
7. Click Update or press Enter to begin the update. While the devices are rebooting, connectivity is disrupted.

Check the Operation Status and Progress columns to see the progress of the configuration update.