Job Management Partner 1/Integrated Management - Manager Quick Reference
To handle multiple events as a single error, you use correlation events. You set correlation events in the correlation event generation definition file.
- Prerequisite condition:
- The correlation event generation function is enabled.
Let's specify settings to generate the following events when a correlation either succeeds or fails.
- When the correlation succeeds:
- Condition for a successful correlation:
Events of severity level Error are issued from hosts A, B, and C within 60 seconds of one another.
- Event that is generated:
An event of severity level Warning is generated with the message Errors occurred on hosts A, B, and C in the sales department, which are hindering operations.
- When the correlation fails:
- Condition for a failed correlation:
Error-level events issued from host A, B, and/or C do not satisfy the condition set for a successful correlation.
- Event that is generated:
An event with severity level Information is generated with the message Operations are continuing, but one or more errors may have occurred on host A, B, and/or C.
Using a text editor, open a correlation event generation definition file (example: def1.conf) which is in the following location:
- Windows: any-folder
- UNIX: any-directory
Use .conf as the correlation event generation definition file extension. In the file name, you can use alphanumeric characters and the underscore (_).
Enter the following specifications:
VERSION=2 [error_gradation] CON=E.SEVERITY==Error,B.SOURCESERVER==hostA CON=E.SEVERITY==Error,B.SOURCESERVER==hostB CON=E.SEVERITY==Error,B.SOURCESERVER==hostC TYPE=combination SUCCESS_EVENT=E.SEVERITY:Warning,B.MESSAGE:"Errors occurred on hosts A, B, and C in the sales department, which are hindering operations." FAIL_EVENT=E.SEVERITY:Information,B.MESSAGE:"Operations are continuing, but one or more errors may have occurred on host A, B, and/or C."The following table explains these specifications:
Specification Explanation CON=E.SEVERITY==Error,B.SOURCESERVER==hostA
CON=E.SEVERITY==Error,B.SOURCESERVER==hostB
CON=E.SEVERITY==Error,B.SOURCESERVER==hostCSpecifies the event conditions used in specifying a correlation event generation condition.
Specify as follows to set error-level events issued by hostA as a condition.
In a similar fashion, specify error-level events issued by host B and host C as conditions.
- Set the severity level to match Error:
E.SEVERITY==Error
- Set the event-issuing host to match host A:
E.SOURCESERVER==hostA
TYPE=combination Specifies the type of the correlation event generation condition that is defined. Specify as follows to set the combination of host A, host B, and host C as a condition.
- TYPE=combination
SUCCESS_EVENT=E.SEVERITY:Warning,B.MESSAGE:
"Errors occurred on hosts A, B, and C in the sales department, which are hindering operations."Specifies the correlation event that is generated if the correlation event generation condition succeeds.
Specify as follows to generate an event of severity level Warning with the message Errors occurred on hosts A, B, and C in the sales department, which are hindering operations.
- Specify an event of severity level Warning:
E.SEVERITY:Warning
- Specify the message to display:
B.MESSAGE:"Errors occurred on hosts A, B, and C in the sales department, which are hindering operations."
FAIL_EVENT=E.SEVERITY:Information,B.MESSAGE:
"Operations are continuing, but one or more errors may have occurred on host A, B, and/or C."Specifies the correlation event that is generated if the correlation event generation condition fails.
Specify as follows to generate an event of severity level Information with the message Operations are continuing, but one or more errors may have occurred on host A, B, and/or C.
- Specify an event of severity level Information:
E.SEVERITY:Information
- Specify the message to display:
B.MESSAGE:"Operations are continuing, but one or more errors may have occurred on host A, B, and/or C."
You can store def1.conf anywhere you like (Example: C:\jp1im).
Execute the jcoegschange command on the manager as follows to register the definitions:
jcoegschange -f C:\jp1im\def1.conf
References:
- See 3.3 Issue of correlation events in the Overview and System Design Guide.
- See 4.4 Setting correlation event generation in the Configuration Guide.
- See 5.1.7 Displaying and handling correlation events in the Administration Guide.
- See jcoegschange in Chapter 1 of the manual Command and Definition File Reference.
- See Correlation event generation definition file in Chapter 2 of the manual Command and Definition File Reference.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.