Amer Networks E5Web GUI User Manual
Page 113
These have bug fixes only with no feature additions. They are freely available to all customers
who are licensed to run the base version involved in the upgrade. The last two digits in the
version number will change for this type of upgrade. For example, version 10.30.00 might
become version 10.30.01.
•
Feature Releases
These have minor feature additions and bug fixes. They are freely available to all customers
who are licensed to run the base version involved in the upgrade. The middle two digits in
the version number will change for this type of upgrade. For example, version 10.30.nn might
become version 10.31.nn.
•
Major Releases
These involve the addition of major new functionality to cOS Core as well as bug fixes. They
are available to customers who have a valid software subscription service contract. The first
two digits of the version number will change for this type of upgrade. For example, version
10.30.nn might become version 10.40.nn.
•
CorePlus 9.nn to cOS Core 10.nn Upgrades
The upgrade from a CorePlus 9.nn to a 10.nn cOS Core version does not require any special
steps. After the 10.nn version is loaded and started for the first time, the existing CorePlus
configuration will be automatically converted by into the required cOS Core internal format.
•
CorePlus 8.nn to cOS Core 10.nn Upgrades
Upgrading a CorePlus 8.nn version to a cOS Core 10.nn version is done using the Migration
Wizard which is available as a separate Windows executable. It is done in the same way as
upgrading from CorePlus 8.nn to CorePlus 9.nn except the upgrade file chosen in the wizard
should be for the target 10.nn version. This wizard is fully described in the separate Migration
Guide document which is included with cOS Core distributions and is available from the
Clavister website.
An alternative to running the Migration Wizard software is to perform the upgrade from
within the InControl client. This is recommended if InControl is the principle management
interface used by the administrator.
The Upgrade Procedure
Upgrading to a new version of cOS Core is a simple procedure. A cOS Core upgrade is packaged
as a single file with filetype .upg and this can be downloaded from the Clavister website. This file
is then uploaded to the Clavister Security Gateway by using either of the following two methods:
•
Go to: Status > Maintenance > Upgrade in the Web Interface. Then choose the option
Upgrade Unit's Firmware to select and upload the correct .upg file.
•
Upload the file using Secure Copy (SCP). When cOS Core receives the file, it recognizes what
the purpose of the file is.
When the upload of a .upg file is complete, the Clavister Security Gateway will initiate a full
system restart. Any live traffic will therefore be interrupted and connections lost while this takes
place.
Chapter 2: Management and Maintenance
113