Receive Email Notifications When Pa Services Fail - HPE XP7 User Manual

Storage, performance advisor software 7.1
Hide thumbs Also See for XP7:
Table of Contents

Advertisement

Ensure that the above-mentioned steps are performed before you initiate a real-time performance data
collection for the arrays.
IMPORTANT:
Ideally, if an array is connected to two host agents, configure separate real-time data collection
through each of the host agents.
At a time, ensure that only one instance of PA collects the real-time performance data from an
array through the respective host agent.
If there have been configuration changes on the XP/XP7 disk array for which you want to collect
the real-time performance data, the following informational message appears when you select
components and start plotting the real-time graphs:
The <XP or XP7 disk array> configuration data available in the Real
Time Server is not in sync with the configuration data available on
Performance Advisor. This could occur due to the following reasons:
Command device is invalid, <XP or XP7 disk array> is no longer
connected, or selected components are not available on the selected <XP
or XP7 disk array>.

Receive email notifications when PA services fail

The PA service periodically monitors the statuses of the following services and accordingly notifies the
intended email recipients:
PA Tomcat service
PA Database service
PA Database Listener service
To receive email notifications, you must configure certain SMTP parameters.
IMPORTANT:
The PA Monitor service does not monitor the PA Security service.
Notification for PA Tomcat service failure
During the course of monitoring, if the PA service identifies that the PA Tomcat service has abruptly
stopped or failed to start, it does the following:
1. Attempts to restart the PA Tomcat service 'n' number of times, where 'n' indicates the retry count that is
specified.
By default, the retry count is set to five, which means that five attempts are made to restart the PA
Tomcat service before a notification is dispatched. For more information on specifying the retry count,
see Configure retry count.
2. Intimates the intended recipients on the success or failure of the restart attempts, such as the
following:
Tomcat Server was not running on management station, Restart of the service was successful after
'n' attempt.
Tomcat Server was not running on management station, Restart of the service was not successful
after 'n' attempt.
Receive email notifications when PA services fail
121

Advertisement

Table of Contents
loading

Table of Contents