In this document, the different upgrade scenarios, and the support for each of them will be outlined.


Please read:  How do I upgrade the software?


The following scenarios go into specifics.


Version number

As a general rule, major versions may only be upgraded, never downgraded, while minor versions within the same major may be up/downgraded at will.


The version number is split into four parts; [Major].[Minor].[Type].[Revision] like 2.6.1.r145


Scenario 1: an old controller with new endpoint - not supported

A system with a controller at [Major] < endpoint [Major] is not supported. This has the consequence that in order to add additional endpoints to an existing installation, which is running at a noncurrent software version, the software version must be bumped to at least the same major version as the endpoint.


Example:

An installation with a controller and endpoints, at version 1.3.1.r66 needs to add three new endpoints. The endpoints are delivered in version 2.0.0.r66. The endpoints may be connected to the system, but will never come online nor be downgradable. The entire system must be upgraded to at least version 2.0.0.rxx.


Scenario 2: a new controller with old endpoint - supported

A system with a controller at [Major] >= endpoint [Major] is supported. This means that you can freely use any older endpoints with an updated controller.


Example:

An installation with a controller and endpoints, at version 2.0.0.r66 needs to add three new endpoints. The endpoints are running version 1.0.1.r59 because they were bought several years ago. The endpoints are automatically upgraded when they are added to the system.


Scenario 3: new controller downgrade major - not supported

A controller may never be downgraded to a previous major version.


Scenario 4: new controller downgrade minor - supported (but not encouraged)

Downgrades within between minor versions are supported, as long as they are in the same major version. It is not encouraged to do so, as the test coverage for downgrades between any two versions will inherently below.



Hardware Revision

In general, are all released software versions backwards compatible on regards of the controller and endpoint hardware revisions and models.


At the time of writing, it is not known if there will be versions that are not backwards compatible.


This means ie. that the 64/4 Controller Rev. A and 32/2 Controller Rev. A can be updated with the latest released software. Software-based features will be enabled on Rev. A controllers, hardware-based features, like port bundling/combining will of cause not be possible.



Licenses

Licenses can be installed and deleted on the controllers from sw2.7.x. A deleted license can be re-installed. The order of installation of licenses is subordinate.


When upgrading an EoC system with installed licenses, the licenses will not be altered/deleted.


This means downgrading below this version will result in licenses not being displayed. The licenses will still be active and the system will be running, provided the configuration is not utilizing features introduced in a later version than the one the controller is downgraded to.


None-WiFi controllers

Controllers bought as "none-WiFi"/MediaC controller ( 383106 & 383107) can with sw2.7.x be upgraded to fully support WiFi.