Versions Compared

Old Version 35

changes.mady.by.user Sebastian Koch

Saved on

compared with

New Version 36

changes.mady.by.user Sebastian Koch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Change History

Change History

...

Version
Date
Comment
Current Version (v. 34)Jul 10, 2014 16:09Sebastian Koch:
Added note about fixed check_azetiplugin_netapp3, Added end of life for check_azetiplugin_kyocera_toner. Added not about check_radius_adv fix. Added Known Issues Table
v. 32Jul 09, 2014 10:25Sebastian Koch: 
Enhanced backup creation instructions
v. 29Jul 08, 2014 18:15Sebastian Koch: 
Added extra steps to disable notifications, flushing the mail queue and fixed minor typos
v. 25Jul 08, 2014 12:11Sebastian Koch: 
Extended list of incompatible plugins and known issues for EOL packages
v. 21Jul 01, 2014 15:31Sebastian Koch: 
Added Known Issues for Upgrade section regarding plugin update package
v. 18Jun 26, 2014 16:01Sebastian Koch: 
Fixed minor typos in portal paths, Added section about Plugin Download for azeti NG

...

 

After the SONARPLEX Upgrade

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

Updating the LOAD Configuration

The following step assures that the global LOAD Configuration is properly updated and is mandatory.

  1. Open Admin GUI > Configuration > System > Load Configuration
  2. Choose  to save the current configuration and apply it with the following 

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

Flush the Mail Queue

It is possible that during the upgrade system messages are created and stored in the email queue. Those would be sent out whenever you enable the SMTP configuration and you can flush those if you don't want to receive such mails from the upgrade.

Flushing queued e-mails:

  1. Open the Admin GUI > System > Email Queue
  2. Choose  Delete all messages in queue and press OK

Re-Enable the Notifications

When all upgrade steps are done and the system behaves properly, it is save to enable the notifications again. Check that not too many service and host checks are in Non-OK states to avoid notification floods.

Enable notifications globally:

  1. Open the Web GUI > Status > Processes
  2. Choose  Enable notifications and press Commit in the next screen

 

...