Versions Compared

Old Version 21

changes.mady.by.user Sebastian Koch

Saved on

compared with

New Version 22

changes.mady.by.user Sebastian Koch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added known issues for plugins, see

...

...

...

...

Change History

Version
Date
Comment
Current Version 

...

(v. 21)Jul 01, 2014 15:31Sebastian Koch:
Added Known Issues section covering problem+solution of initial plugin update package

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. 

...

Warning
titleProblems with plugin-updates-001_v4.2.0b_to_v5.1.1a.tar

There is the possibility, in seldom circumstances, that plugin installation errors appear in combination with the plugin update package plugin-updates-001_v4.2.0b_to_v5.1.1a.tar.

This was released in the time of 25th june 2014 until 1st july 2014.

Tip
titleSolution

The problems are fixed by the latest upgrade plugin-updates-002_v4.2.0b_to_v5.1.1a.tar. It is important that you install the latter, see Upgrade Patch

...

Package

Status Update

The system configuration, performance data and event-log will be upgraded to the new version. Due to the major software change the status file will not take over to the new version. This means it will take a while until the status will be updated.

...

Info

You can get specific ARM builds of plugins which run on the azeti NG in the azeti Portal > Downloads > SONARPLEX Generation 5 > Plugins > ARM.

...

Known Issues and incompatibilities

Plugin NameDescriptionStatus
check_azetiplugin_email_loop.azspPlugin for checking the whole e-mail delivery loopincompatible
HTTP-XML-Interface.azse

HTTP POST XML Interface for integration of external data and systems Accepts HTTP POST Requests and receives a XML file and parameters.
It will then try to match the content of the XML file to the mandatory sonarplex variables like service name, hostname, freshness and plugin output.

Several variables can be conducted out of mutliple xml fields, e.g. the service name.

Compatible Plugins

Following plugins are compatible and will be automatically upgraded through the upgrade patch. You can download all of these plugin in azeti Portal > Download > SONARPLEX Generation 5 > Plugins as well. 

...

incompatible

check_radius_adv

Advanced RADIUS checkinstallation issues in 5.1.1a, will be fixed shortly
check_radiusBuilt in radius checkexecution problem, will be fixed shortly

check_azetiplugin_netapp3

SNMP based check for NetAPP storage systemsinstallation issues in 5.1.1a, will be fixed shortly

Compatible Plugins

Following plugins are compatible and will be automatically upgraded through the upgrade patch. You can download all of these plugin in azeti Portal > Download > SONARPLEX Generation 5 > Plugins as well. 

Info

The Service Check Plugin check_snmp.pl is not listed as it is installed by default and will be automatically updated.

Version 0.0.617Version 1.0.676checks the login on RADIUS servers
Plugin NameDescriptionVersion
camera.azsp receives HTTP alerts form AXIS Cameras upon motion detectionVersion 1.0.1273
check_arm_state.azsp
  • used for site surveillance
  • based on the state other alarm are triggered
Version 1.0.714
check_axis_storage.plsimple script for checking the storage state (OK or NON-OK) for Axis Mxxxx and Pxxxx cameras(No version information available)
check_azetiplugin_akcpairflow.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_akcphumidity.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_akcpmotion.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_akcpsecurity.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_akcpsmoke.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_akcptemperature.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_akcpwater.tar.gzSNMP based plugin to query specific sensor from AKCP sensorprobe deviceVersion 0.0.613
check_azetiplugin_ncp_sevpn.azspSpecial remote check. The plugin checks data within a remote MYSQL database.Version 1.0.663
check_azetiplugin_esx_perf.azspsRemote Check Plugin for checking performance counter on ESX hosts via the VMware Perl SDK. Requires the azeti Virtual Remote Host (azeti-VRH). Version 1.0.675
check_azetiplugin_exchange.tar.gzcollection of performance counters for exchange servers, based on check_ azeti_perf Version 0.0.763
check_azetiplugin_kyocera_toner.tar.gzSNMP query for toner status of Kyocera printers. Version 1.0.675
check_azetiplugin_netapp3exchange.tar.gzchecks various system parameters like CPULOAD or FAILEDDISKS on NetApp Storage systems via SNMPVersion '3.0'.613check_oracle_ix.azsp (formerly check_azetiplugin_oracle)remote check plugin which allows the user to execute custom sql queries via a remote oracle clientcollection of performance counters for exchange servers, based on check_ azeti_perf Version 0.0.763
check_azetiplugin_kyocera_toner.tar.gzSNMP query for toner status of Kyocera printersVersion 0.0.617
check_azetiplugin_remoteping.azspremote check plugin which allows the user to ping a host from a remote hostVersion 1.0.613
check_azetiplugin_vcenter_inv.azspschecks VMware vCenter inventory and creats a csv for import within the SONARMANAGERVersion 1.0.683
check_azetiplugin_vcenter_perf.azspscheck the performance counters of configured hosts and cluster in a VMware vCenterVersion 1.0.684
check_azetiplugin_vcenter_status.azspscheck the status of configured hosts and cluster in a VMware vCenterVersion 1.0.686
check_cisco_ipsla.azspchecks the network latency through the proprietary CISCO IPSLA protocol. Data is received from cisco routers via SNMPVersion 1.0.613
check_icmp_adv2.azspenhanced ICMP check with Host Property support (e.g. loading ip addresses of different network interfaces)Version 1.0.618
check_icmp2.azspenhanced check_icmp with TOS support and further advanced optionsVersion 1.0.613
check_modbus_access_m2m-wtsc.azspMODBUS based check plugin for M2m-WTSC converters used within access control (via PIN-Pad or proximity reader) installationsVersion 1.6.780
check_modbus_fast_drycontact3.azspMODBUS based check for drycontactsVersion 1.7.777
check_modbus_fast_read3.azspMODBUS based check to read single registersVersion 1.4.735
check_modbus_fast_write4.azspMODBUS based check to write to single registers, also used by action_modbus_write.azspVersion 1.4.738
check_performance_trend.azsp

checks the latest value of an already monitored service against a historic value and compares the resulting difference against thresholds.

This is especially useful to check for the growth or loss over a certain amount of time, e.g. for detecting abnormal fuel level drops.

Version 0.1.613check_radius_adv.azsp
Version 1.0.623check_remote_snmp_ifbandwidth.azspremote check to execute a check_snmp_ifbandwidth from another host. E.g. when the destination is not in the same network segment as the SONARPLEX device or if SNMP is only enabled within a special network segmentVersion 1.0.678
check_snmp_ifbandwidth_pct.azspchecks the percentual network interface usage in regards to either a fixed interface speed or an automatically detected interface speed, like it is the case for DSL RoutersVersion 1.0.613
data_exporter.azseColetcs event and performance data into archives as CSV and/or XML. These exports are regularly uploaded to a destination FTP server.Version 1.0.506
modbus-fastd.azseMODBUS Fast Daemon

Version 1.7.1

MODBUS-Setup.azsetool to send manual request to a connected MODBUS for configuration and setup purposes, requires the modbus_fastd.azseVersion 1.3.563
send_sms_to_gatewayconnects the Messaging gateway for SMS sending(No version information available)
snmpd.azseNet-SNMP based daemon to access status information via SNMP GET from the SONARPLEXVersion 1.0.533
sonargate.azseprovided the connection and configuration interface for the azeti SONARGATEVersion 1.2.28.1245
sonartcpd.azseTCP based Zigbee daemon for importing data from external sensorsVersion 1.0.434
Video.azse-Harvester.azseDaemon to harvest recorded videos from connected Axis cameras and uploading these to an external FTP server later onVersion 1.0.570

...

PackageFilenameDescriptionDownload

SONARPLEX 4.2 patch level 7

update-4.2.0b-base-7.tarenables upgrade from SONARPLEX 4.2.0b to 5.1.xazeti Portal > Downloads > SONARPLEX Generation 4 > Updates
SONARPLEX 5.1.1a image<SysID>-daaz1en-5.1.1a.aup (e.g. 2m002421121f36-daaz1en-5.1.1a.aup)Full Operating System image version 5.1.1aazeti Portal > My Appliances > <SONARPLEX SysId>
SONARPLEX 5.1.1a plugin updates

plugin-updates-001_v4.2.0b_to_v5.1.1a.tar (see Known Issues for Upgrade)

plugin-updates-002_v4.2.0b_to_v5.1.1a.tar

Package containing all necessary plugin updates for automatic installationazeti Portal > Downloads > SONARPLEX Generation 5 > Updates
SONARMANAGER 2.7.3.24SonarManager_2.7.3.24.zipSONARMANAGER compatible to SONARPLEX 5.x.xazeti Portal > Downloads > SONARPLEX Generation 5 > SONARMANAGER

...

 

After the SONARPLEX Upgrade

SONARPLEX 5 is a major release and thus some minor system configuration changes must be done right after the upgrade. 

Configure the global Log Level

A whole new logging framework was introduced with the upgrade. See Admin GUI > Configuration > System > Logging Configuration.

 By default the Debug log level is set to OFF. We recommend turning it to INFO for all hardware types except the azeti NG.

Note

The azeti NG runs on SD flash storage and debug log levels can lead to decreased lifetime of the storage due to large amounts of write operations through logging. Therefore leave the Debug log level set to OFF.

Flush the Retention File

To warrant a consistent status among the old and new plugins, delete the retention file. 

Info

Deleting the retention file leads to a flush of all status information, this will set every host and service object into state PENDING. This is expected and the objects will be checked during the normal check intervals and return into a non-PENDING state.

Deleting the retention file:

  1. Open Admin GUI > Status > Monitor
  2. Choose Delete state retention file (read online help before using), the Monitor process will be restarted automatically

 

...