For the best and most secure experience, Lantronix Local Managers should always run the latest version of LMS. Lantronix generally releases two new versions of software each year, but may also release patches if important bugfixes or security updates are required.
To ensure proper operation of the Local Manager with the Control Center, both need to be running the same minor revision of software. That is, the first two numbers of the version need to be the same.
For example, a 6.3.0 Local Manager will work fine with a 6.3.1 Control Center. A 6.2 Local Manager, however, will not synchronize with a 6.3.x Control Center.
Here's what happens when you upgrade a Local Manager:
The Local Manager will be available until Step 4. During the upgrade, the operating system will be up and responding to pings, but SSH will be unavailable until the upgrade is complete.
Lantronix provides multiple software bin files to best match your deployment.
Most customers will want to download the bin file tagged with -all.bin. This file contains software for both the 500/5000, LM80/LM83X, and Virtual platforms.
FIPS-compliant versions of LMS are tagged with the g letter. Most customers will want to download the bin file tagged with -allg.bin. This file contains FIPS-compliant software for both the 500/5000 and LM80/LM83X platforms.
For environments where bandwidth is a concern, Lantronix provides smaller platform-specific bin files for updating Local Managers.
Use the g version as needed for FIPS environments.
Previous EOL platforms are no longer supported and cannot be upgraded.
Visit your Lantronix Support Site account page at uplogix.com/support/account.An active maintenance contract is required to access the Lantronix Support Site account page and/or download software. If your maintenance contract has expired, please contact Lantronix Support.
Find the green button marked Download Software.
Click the folder link for your desired software version.
Click the link to download the bin file to your desktop.
Customers with Local Managers on older versions (6.1.0 or older) will need to upgrade in steps to get to 6.2. Please contact Lantronix Support for information on your upgrade path and what files are needed prior to the upgrade.
SCP, FTP, and HTTP require the lms.bin file to be staged on an appropriate server. Push the file to an SCP, FTP, or HTTP server.
The Control Center can be used as an SCP target because of its Linux operation system. Use a program like WinSCP or pscp to transfer the bin file to /home/emsadmin.
Log into your Local Manager and use the config update command to initiate the upgrade. You will need to specify the IP address or hostname of the target and the path to the file.
config update scp email@example.com:LantronixOS-126.96.36.199768-all.bin
config update ftp firstname.lastname@example.org:LantronixOS-188.8.131.52768-all.bin
config update http https://198.51.100.172/LantronixOS-184.108.40.206768-all.bin
To upgrade Local Managers from the Control Center, please refer to Control Center User Guide, Upgrading Local Managers.
Flash drives are a useful alternative if the Local Manager isn't on the network or is in a remote location.
The flash drive should be formatted with the FAT16 filesystem. If the drive is formatted with FAT32, it must be removed from the Local Manager after it reboots to complete the upgrade.
Download the upgrade.mnf file from the Lantronix Software Directory of the version you wish to upgrade to and copy it to the root directory of the USB drive.
Use a free USB slot on the front of the Local Manager. Allow a few seconds for the system to recognize the new drive.
Press the center button on the keypad to enter the Local Manager menu.
Scroll down and select Update.
Verify that Update to [version]? message matches intended version.
Scroll left and select Yes.
The upgrade will now continue on its own. While the software is transferred to the Local Manager, the LCD will begin displaying status information again. Allow several minutes for the software to be copied over and for the upgrade to begin.
Log into the Local Manager.
Run config update usb upgrade_filename.bin. If the filename is not specified, the appliance will attempt to discover this information via the MNF file.
The Local Manager will then copy the file over, verify it, and begin the upgrade.