Updating or Re-imaging the SmartServer with the SmartServer Console

You can update or re-image your SmartServer software using the SmartServer console and a USB flash drive. This is one of three methods of updating your SmartServer software as described in Updating or Re-imaging the SmartServer IoT. The method described on this page is the easiest if you want to delete all of your data and re-image your SmartServer at the same time. You can only perform an update when the two versions are compatible. All SmartServer software versions prior to version 2.40.507 are not compatible with newer releases. To update releases prior to 2.40.507, re-image the software.

To update or re-image your SmartServer software with the SmartServer console and a USB flash drive, follow these steps:

SmartServer versions are hardware specific. See Determining SmartServer Software Version Compatibility before upgrading to verify compatibility for your update.
Prior to re-imaging, if you are using any custom applications or services on the SmartServer, verify you have backup copies of your custom applications and services. The re-imaging process will delete any custom applications and services.
Download the SmartServer software image to your computer. The latest update is at the following location:

https://downloads.echelon.com/support/downloads/software/smartserver/iot/SmartServer_IoT_Update.armv7l.zip
Insert a USB flash drive with at least 2GB of available space into a USB connector on your computer.

Prior to SmartServer 2.8, you cannot attach a USB flash drive and a USB network interface, such as the U60, into a SmartServer at the same time. To use both at the same time, plug a powered USB hub into one of the SmartServer USB connectors, and then plug the USB flash drive and all USB network interfaces into the external USB hub. To update the SmartServer software from a USB flash drive without using an external USB hub, first unplug all the USB network interfaces from the SmartServer, and then plug in the USB flash drive. Remove the USB flash drive once the update or re-image process is complete, and then plug in the USB network interfaces. This warning does not apply if you are using SmartServer 2.8 or newer.
If your USB flash drive is not formatted with a FAT32 file system, then reformat the drive with a FAT32 file system.
Extract the contents of the update image you downloaded in step 1 to the top-level of your USB flash drive. Do not place the files in a folder on the flash drive.
Eject the flash drive from your computer to flush any cached updates to your drive.
Write down or take a picture of the SmartServer password that is printed on the back of the SmartServer.
Remove the USB flash drive from your computer and insert it into one of the USB connectors on the SmartServer.
Connect to the SmartServer console as described in Connecting to Your SmartServer.
Verify that you have the expected firmware version USB drive image by entering the following command:
```
cat /media/usb0/versions.txt 
```
If you see a "No such file or directory" error, then enter the following command to mount the drive:
```
sudo mount -o fmask=0022,dmask=0022 /dev/sda1 /media/usb0
```
From the console widow (SSH or serial console using com[n] 115200 bps), do the following:
1. To update the SmartServer:
```
sudo /media/usb0/upgrade.sh  
```
2. To re-image the SmartServer:
```
sudo /media/usb0/re-image.sh 
```
3. Enter the [sudo] password when prompted.
If your new SmartServer image requires an active maintenance license, the update script will display the following error message: "This image requires an active maintenance license for installation. Add a new maintenance license to extend the maintenance period for this SmartServer." See Manage Licenses for more information.
The SmartServer initiates a reboot after a 1 minute delay, and then performs the upgrade or re-image. During the process, the SmartServer displays status information on your console window, and the LEDs on the SmartServer will blink intermittently. The SmartServer may display error messages during the update process. These are benign and you can ignore them if the update completes and the SmartServer software version number is updated.
The SmartServer automatically reboots when the update or re-image is completed. The SmartServer is fully up and running when you can log into the CMS. With SmartServer release 3.2 and newer, you can monitor the SmartServer Ready LED for system status.
After the reboot, unmount and remove the flash drive using the following command to unmount the drive prior to removing it:
```
sudo umount /media/usb0    
```
If you update your SmartServer, then the serial number and password do not change. If you re-image your SmartServer, then the internal flash memory is wiped clean, the SmartServer's password is reset to its default (printed on the back of your SmartServer) and the serial number is automatically reapplied to the new image. To change the password, see Managing Passwords in Securing Your SmartServer.
With SmartServer release 4.2 and higher, if you re-imaged the SmartServer and try to connect to the SmartServer using SSH or SFTP, a warning message will appear letting you know that the system with which you are trying to connect is known to your system, but that the fingerprint has changed. A new host key needs to be added to the system for SSH access. See Adding New Host Keys for SSH Access and SFTP for more information.
Clear your browser's cached data after you update or re-image the SmartServer. To clear the browser's cache, see Clearing the Browser's Cache.
Re-imaging the SmartServer may cause the MAC IDs (also referred to as neuron IDs) to change in the SmartServer for the IP-852 and U60 routers, SmartServer IoT device (used for IMM), and any internal devices that get their neuron IDs assigned by the SmartServer. Consequently, the following step is required:
1. If you are using IP-852 routing with the SmartServer, after you reset the SmartServer, delete the SmartServer device shape in the IP-852 Config Server and then add the SmartServer again.
2. If the SmartServer is used in an IzoT CT or IzoT Net Server database, after you reset the the SmartServer database, decommission the IP-852 and U60 routers (remove the neuron ID as it has changed), the SmartServer IoT device, and any SmartServer internal devices, and then commission these devices with the new neuron IDs.