Change History

Version	Date	Comment
Current Version (v. 22)	Jul 01, 2014 15:45	Sebastian Koch: Added known issues for plugins, see Known Issues and incompatibilities
v. 21)	Jul 01, 2014 15:31	Sebastian Koch: Added Known Issues section covering problem+solution of initial for Upgrade section regarding plugin update package

Introduction

...

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.

Plugin Name	Description	Status
check_azetiplugin_email_loop.azsp	Plugin for checking the whole e-mail delivery loop	incompatible
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.	incompatible
check_radius_adv	Advanced RADIUS check	installation issues in 5.1.1a, will be fixed shortly
check_radius	Built in radius check	execution problem, will be fixed shortly
check_azetiplugin_netapp3	SNMP based check for NetAPP storage systems	installation issues in 5.1.1a, will be fixed shortly

...

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

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:

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

...