Exception Alerts

Exception alerts (xAlerts) notify you of system failures in the database, communication network problems, and application errors and failures. The Exception Alerts displays information about each alert, such as the alert ID, severity of the alert, and the message that was generated by the alert.

Managing Exception Alerts

Begin

Sending Alerts and xAlerts to an Event Management System

This procedure describes how to send alerts and xAlerts to your organization's event management system via SNMP.

For a detailed list of trap variables, see SNMP Trap Format.

Begin

  1. Copy the Control-M/EM MIB file (SNMP2) from the following location to your SNMP server:

    <emHome>\Data\BMC-CONTROLMEM-MIB.txt

  2. Define the following system parameters, as described in Configuring Control-M/EM System Parameters:

    • SNMPHost: Define the hostname of the SNMP server where the alerts are sent.

    • SNMPSendActive: Change the value to 1 to generate SNMP messages for Active Alerts.

    • SendSNMP: Change the value to 0 to send alerts to SNMP server only.

    • SendAlertNotesSnmp: Change the value to 1 if you want to send the NOTES field to the SNMP server.

    • XAlertsEnableSending: Change the value to 1 to enable xAlert sending.

    • XAlertsSnmpHosts: Define the hostname of the SNMP server where the xAlerts are sent.

    • XalertsSendSnmp: Change the value to 1 to send xAlerts to SNMP server only.

  3. Recycle the Gateway, as described in Recycling a Control-M/EM Component.

  4. To test an alert, order a job that sends a notification to the Alerts window.

SNMP Trap Format

The following table describes SNMP variables that Control-M/EM uses to send alerts to an event management system via SNMP, as described in Sending Alerts and xAlerts to an Event Management System.

Number

Field

Description

1

UPDATE TYPE

Determines the type of event that triggered the alert, as follows:

  • I: A new alert was issued.

  • U: An existing alert was updated

2

ALERT ID

Defines the numeric value used as a key (index) to identify the alert.

3

CONTROLM

Defines the name of the data center to which the job belongs.

4

MEMNAME

Defines the File Name of the job (previously known as Mem Name).

5

ORDERID

Defines the Order ID of the job.

6

SEVERITY

Determines the severity of the alert:

  • V: Very urgent

  • U: Urgent

  • R: Regular

7

STATUS

Determines the status of the alert:

  • Not noticed

  • Noticed

  • Handled

8

TIME

Determines the time and date that the alert was issued.

Format: yyyymmddhhmmss

9

USER

Defines the name of the user who last modified the status or text of the alert.

10

UPDATE TIME

Determines the time and date that the alert was last modified by the user.

11

MESSAGE

Presents the full text of the alert.

12

OWNER

Defines the Run As user set as owner of the job.

13

GROUP

Defines the job sub-application (previously known as group).

14

APPLICATION

Defines the job application.

15

JOB NAME

Defines the name of the job.

16

NODE ID

Defines the node or host where the job is run.

17

TYPE

Determines the Alert type:

  • R: Regular (Can also be empty).

  • B: BIM

Default: R

18

CLOSED FROM EM

Determines whether the Remedy ticket was closed from Control-M/EM:

  • Y: Yes

  • N: No

Default: N

The initial value is empty.

19

TICKET NUMBER

Determines the Remedy ticket number.

20

RUN COUNTER

When a job is executed more than once within a scheduling day, this counter uniquely identifies each execution of that job.

This way you know exactly in what instance of the job’s execution the remedy ticket was opened.

21

NOTES

Displays the text that can be edited and saved in the Control-M/EM Alerts window.

To enable this field, set the SendAlertNotesSnmp parameter to 1.

Sending Alerts and xAlerts to a Script

This procedure describes how to send alerts and xAlerts to a script.

Begin

  1. Define the following system parameters, as described in Configuring Control-M/EM System Parameters:

    • SendAlarmToScript: Define the pathname of the script that is activated when an alert is generated.

    • SendSNMP: Change the value to 1 to send alerts to a script only.

    • SendAlertNotesSnmp: Change the value to 1 if you want to send the NOTES field to a script.

    • SNMPSendActive: Change the value to 1 to generate SNMP messages to a script.

    • XAlertsEnableSending: Change the value to 1 to enable xAlert sending.

    • XAlertsSend2Script: Define the pathname of the script that is activated when an xAlert is generated.

    • XalertsSendSnmp: Change the value to 2 to send xAlerts to a script only.

  2. Recycle the Gateway, as described in Recycling a Control-M/EM Component.