Cisco IPICS Server Administration Guide, Release 4.6
Configuring System Event E-Mail Notifications
Downloads: This chapterpdf (PDF - 93.0KB) The complete bookPDF (PDF - 13.51MB) | Feedback

Configuring System Event E-Mail Notifications

Table Of Contents

Configuring System Event E-Mail Notifications

Understanding System Event E-Mail Notifications

Enabling System Event E-Mail Notifications

Disabling System Event E-Mail Notifications

Changing System Event Trigger Values


Configuring System Event E-Mail Notifications


This appendix describes system event e-mail notifications and how to enable or disable them, and includes the following sections:

Understanding System Event E-Mail Notifications

Enabling System Event E-Mail Notifications

Disabling System Event E-Mail Notifications

Changing System Event Trigger Values

Understanding System Event E-Mail Notifications

The system administrator can log in to the Administration Console to access major system event information. However, the system administrator should be notified when major system events occur, even when not logged in to the Administration Console. You can configure the IPICS server to send system event notifications to the system administrator when any of the following major system events occur:

The 1 minute load average exceeds 5

The 5 minute load average exceeds 3

Memory usage exceeds 75%

User CPU usage exceeds 70%

System CPU usage exceeds 40%

I/O wait exceeds 40%

The node manager process starts or stops

The server HA state changes (active/standby)

Any partition is more than 90% full, except for the /documents partition which sends notifications after it is 75% full.

Enabling System Event E-Mail Notifications

By default, the IPICS server does not send system event e-mail notifications to the system administrator. To enable system event e-mail notifications, perform the following procedure.

Before You Begin

Collect the following information that you must supply when configuring system event e-mail notifications:

The hostname or IP address of the Simple Mail Transfer Protocol (SMTP) server that is to be used for sending the notifications.

The e-mail address or mailing-list alias of the system administrators who are to receive the notifications,

Procedure


Step 1 Log in to the IPICS server bash shell using the root account.

Step 2 At the root prompt, run the /opt/cisco/ipics/bin/setup_monit_alerts script.

Step 3 Enter the the IP address or hostname of the SMTP e-mail server.

Step 4 Enter the e-mail address for the system administrator.

The system applies the configuration settings and reinitializes the monit daemon.


The following example configures the IPICS server to send system event e-mail notifications to the SysAdmin@cisco.com e-mail account using the email.cisco.com STMP server.

[root]# /opt/cisco/ipics/bin/setup_monit_alerts 
Enter the SMTP e-mail server host name: email.cisco.com 
Enter the e-mail address to send system alerts to: SysAdmin@cisco.com 
Reinitializing monit daemon
 
   
Applying changes to HA partner...
Welcome to Cisco IPICS 4.5(1)
building file list ... done
 
   
sent 78 bytes received 20 bytes 196.00 bytes/sec
total size is 11131 speedup is 113.58
Welcome to Cisco IPICS 4.5(1)
Reinitializing monit daemon

Disabling System Event E-Mail Notifications

To disable the IPICS server from sending system event e-mail notifications, perform the following procedure.

Procedure


Step 1 Log in to the IPICS server bash shell using the root account.

Step 2 Enter the rm -f /etc/monit.d/email.monitrc /etc/monit.d/alerts.monitrc command to delete the email.monitrc and alerts.monitrc files.

Step 3 Enter the monit reload command to reinitialize the monit daemon.


The following example disables the IPICS server from sending system event e-mail notifications:

[root]# rm -f /etc/monit.d/email.monitrc /etc/monit.d/alerts.monitrc
[root]# monit reload
 
   

What to do Next

If you want to re-enable system event e-mail notifications, run the /opt/cisco/ipics/bin/setup_monit_alerts script to regenerate the deleted files (email.monitrc and alerts.monitrc). For more information, see the "Enabling System Event E-Mail Notifications" section.

Changing System Event Trigger Values

You can change the values at which system events are triggered. This allows you to adjust the sensitivity for system events and, therefore, adjust the number of system event notifications that you will receive. For example, if your system is configured to trigger an event when CPU usage is greater than 75%, you can do either of the following:

Decrease the CPU usage value (for example, 65%) to make the system event more sensitive, which will result in more system event notifications being generated and sent.

Increase the CPU usage value (for example, 85%) to make the system event less sensitive, which will result in fewer system event notifications being generated and sent.

Perform the following procedure to change system event trigger values:

Before you begin

You need the following information to complete the procedure:

Hostname or IP address of the IPICS server

IPICS server bash shell root credentials

Procedure


Step 1 Log in to the IPICS server bash shell using the root account.

Step 2 Enter the vi /etc/monit.d/alerts.monitrc command to open the alerts.monitrc file:

The VI editor opens and displays the contents of the alerts.monitrc file in command mode. The alerts.monitrc file contains a list of the system events and trigger values. For example, the list might look something like this:

check system localhost
    if loadavg (1min)     >   5 then alert
    if loadavg (5min)     >   3 then alert
    if memory usage       > 75% then alert
    if cpu usage (user)   > 90% then alert
    if cpu usage (system) > 40% then alert
    if cpu usage (wait)   > 40% then alert
 
   

Step 3 Enter insert mode and change one or more of the system event trigger values.

Step 4 Press the ESC key to exit insert mode.

The VI editor enters command mode.

Step 5 Enter :q to save the updated alerts.monitrc file and exit the VI editor.

Step 6 Enter the monit reload command to reinitialize the monit daemon.

Step 7 Enter the monit status command to verify your changes.