Actions

Turbine Software Upgrade

From Zenitel Wiki

Revision as of 20:27, 3 June 2021 by Asle (talk | contribs) (Upgrade procedure)
AEIPS.png

This article describes how to upgrade the software of the Turbine series of intercom devices via the web interface of the station.

Note icon
  • The procedure described in this article is applicable to the following devices: TCIS-x, TCIV-x, TKIS-2, TMIS-x, TFIE-x, TKIE-x, TFIX-x, IP-LCM, ECPIR-3P, Exigo IP speakers. Exigo Network Amplifiers, and ENA-2060DC1
  • For mass upgrade of stations it is recommended to use the VS-IMT tool, see the article VS-IMT Upgrade Stations.
  • Using Turbine version 4.7.3.2 or higher, you can downgrade to VSF-Turbine version 4.2.3.17, but not to any older version.
  • There is a separate Upgrade procedure for INCA IP stations.
  • If the station is used in SIP mode, also Automatic Updates can be defined.


There are two ways of updating the software of these devices from the web interface:

Upgrade by using an external TFTP server

Prerequisites

  1. Current version must be 4.7.3.2 or higher. To upgrade from older versions, see this article.
  2. A TFTP Server must be available on your laptop. A TFTP server can be downloaded from here: http://tftpd32.jounin.net/tftpd32_download.html.
  3. Download the software package vsft-6.x.x.x.zip, and unzip the package and store the files in a folder on your PC.
  4. Check if your local firewall is not blocking incoming ping/ICMP (Turbine station is pinging TFTP Server during update process)


Upgrade procedure

  1. Start the TFTP server program and click Browse, and select the folder where the 6.x.x.x software files are located
  2. Log on to the Turbine Station web interface. Select Station Administration > Manual Upgrade
  3. Enter the IP address of the TFTP server (I.e. the IP address of your laptop)
  4. Enter Image file: vsft-6.x.x.x
  5. Save Settings
  6. Upgrade
Example: Upgrade to the latest the firmware from TFTP Server 10.9.8.187



The device will restart with the new firmware installed.

The upgrade procedure takes about 3 minutes. The process can be monitored by clicking the Log viewer tab in the TFTP server program.


Devices with Recovery OS

As from firmware version 5.1.3.0 a Recovery Operating System, Recovery OS, has been added in addition to the Main OS.

Note icon
  • "Recovery OS" is available only on Turbine devices that come from factory with software version 5.1 or higher preinstalled (approx. from March 2020)
  • When upgrading to firmware 5.1. or later in the field, "Recovery OS" will not be included


The Recovery OS supports:

  • Software upgrade in IPv6 network
  • Software upgrade when device is using 802.1X authentication
  • Software upgrade via HTTP/HTTPS protocol using .swu image

Devices with Recovery OS support both the new method for software upgrade (using .swu file), as well as the original method (using .zip file and TFTP server).

Choose between upgrading using .swu file, or using TFTP server and .zip file


In order to upgrade software using the .swu file:

  • Press the upper Start Upgrade button
  • The station will now reboot, and start in "Recovery OS" mode
Turbine device in "Recovery OS" mode


  • Now click inside the "Software Update" field and upload the image file (e.g. vsft-6.1.3.0.swu), or drag and drop the image file onto this field
  • The progress of the installation is shown. When finished installation the station will reboot, and start in regular mode.


Upgrade from versions between 3.0 and 4.2

To upgrade devices currently running a version between 3.0.x.x and 4.2.x.x, see article: Upgrading Turbine Devices running firmware between 3.0.x.x and 4.2.x.x


Upgrade in 802.1x environment

Devices with Recovery OS can be upgraded also when the station uses 801.1x authentication. For more details, see IEEE 802.1X


Troubleshooting

In the case the upgrade is not successful it may be due to a windows setting.

If the upgrade is not successful when using the default static IP, it may be due to a network setting.

  • Please check the station's subnet mask. If it is 255.255.0.0, change it to 255.255.255.0 and try again