| Table of Contents |
|---|
Version
...
Introduction
This guide is intended to help you through the migration process from SONARPLEX Version 4.1.x and 4.2.x to SONARPLEX release 5.1. SONARPLEX Generation 5 is a major release, and contains essential changes of the software especially for the plugins. This requires from the user additional steps in the upgrade procedure.
...
Due to the caching of your Web Browser it might be necessary to manual reload of the SONARPLEX Web page; most browsers support CTLR-F5 to reload.
SONARPLEX 4
SONARPLEX 5
Plugin Migration
Preparation
Most of the plugins you are using in your appliance are not compatible with the SONARPLEX generation 5 and need to be updated. Therefore after the upgrade, you will find most of the plugins in red (See image below.). This means they have to be upgraded. The new version of the plugins can be found in the azeti portal.
To migrate all installed plugins you can choose three different ways:
- Plugin upgrade patch (recommended)
- the SONARMANAGER
- the SONARPLEX Administration GUI
Different types of plugins require different handling. With both the SONARPLEX Administration GUI and the SONARMANAGER you are able to migrate and both guides describe all necessary steps.
- Perl plugins (plugins with extension *.pl)
OK, nothing to do. Normally this type of plugins should run under the new version without any migration activities. - *.tar.gz plugins
These type of plugins is not supported anymore. To migrate it to new version the corresponding *.azsp successor need to be installed. The new *.azsp version automatically takes over the configuration from the old version. The obsolete tar.gz should be deinstalled. - *.azse plugins (addons)
These type of plugins need to be replaced by the new version. The new version automatically takes over the configuration from the old version. - *.azsp plugins (checks)
These type of plugins need to be replaced by the new version. The new version automatically takes over the configuration from the old version. - modbus daemon and modbus plugins; see section modbus migration
Migration of MODBUS daemon if you choose not to use the patch:
- Deinstall both plugins modbus_fastd-COM1.azse and modbus_fastd-COM2.azse
- Install modbus_fastd_<version>_INTEL.azse. (version stands for the plugin version number. Please choose the most recent.)
- Installation of the new versions of MODBUS check plugins (if check_modbus_fast_write3 was installed please install the new version of it check_modbus_fast_write4)
- Migration of MODBUS configuration: simply install modbus_active_to_passive_converter-<version>.azse. Once installed the migration is done and the plugin can be deinstalled.
- Adapt configuration to the new plugins (see below).
- If check_modbus_fast_write3 was installed please deinstall it.
...