Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM 6.4 Administrator Guide > High Availability in SRM > Configure High Availability settings

Configure High Availability settings

Table of contents
No headers
Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 7 Votes: 0 Revisions: 1

Click Settings > All Settings > High Availability Settings to access these options.

By default, High Availability is enabled and an email is sent when a failover occurs. You can change the default interval and modify your default email settings.

Default interval to consider a member as down in a pool

Define how long the active pool member can be down before a failover occurs. Provide the interval in seconds.

Email me when server status is changed

Choose to receive email messages when a failover occurs. This is enabled by default and uses the default email settings to send notifications. High Availability notifications do not depend on the SolarWinds alerting service or the Orion database so you receive High Availability alerts when the service or database is down.

Email me when facility status is changed

Receive email messages when the status of a low-level component changes, such as the percent used of the CPU or RAM. Facilities are used to gauge the health of the system and may trigger a failover condition. For example, the computer may restart and failover if the CPU stays over 100% for a significant amount of time.

SolarWinds recommends disabling this setting due to a potentially large message volume.

Email me when resource status is changed

Receive email messages when a SolarWinds Orion component changes, such as the polling or job engines. Resources are generally SolarWinds specific processes or services that are monitored by the High Availability software that can trigger a failover condition. For example, if the job engine is down and does not restart successfully, the active server fails over to the standby server.

SolarWinds recommends disabling this setting due to a potentially large message volume.

 
Last modified
08:56, 14 Mar 2017

Tags

Classifications

Public