You can change the event report generated on the occurrence of any SNMP trap by updating the SPO Event Report box. You can specify any type of event report, provided you supply the correct syntax in the SPO Event Report box.

Log Event Report

The highlighted line in Figure 15–7 is an example that generates a log event report.

Figure 23. Example of Generating a Log Event Report

This entry causes the following log event report to be generated if the corresponding. SNMP trap is received:

TYPE=LG | CLASS=host | INSTANCE=managed-system-name 
| APPL=SPO Trap Service | APPLQUAL=trap-service-system-name 
| MSGTYPE=NO | TEXT=Disk #value1 has gone off-line.

where value1 is the value of the second variable binding. See “Trap Service Database Syntax.”

Alert Event Report

The highlighted line in Figure 15–8 is an example of an alert event report

Figure 24. Example of Generating an Alert Event Report

This entry causes the following alert event report to be generated if the corresponding SNMP trap is received:

TYPE=AL | CLASS=host | INSTANCE=managed-system-name | 
APPL=SPO Trap Service | APPLQUAL=trap-service-system-name| 
ALERTID=Disk Space | SEV=critical 
| TEXT=Disk #value1 has gone off-line.

where value1 is the value of the second variable binding. See “Trap Service Database Syntax.”

Command Event Report

The highlighted line in Figure 15–9 is an example of an attribute value for INSTANCE explicitly supplied to override the default managed-system-name value. A value for the COMMAND attribute also is supplied.

Figure 25. Example of Generating a Command Event Report

This entry causes the following command event report to be generated if the corresponding SNMP trap is received:

TYPE=CO | CLASS=host | INSTANCE=2200A | 
APPL=SPO Trap Service | APPLQUAL=trap-service-system-name |
COMMAND=@DISKDOWN value1

where value1 is the value of the second variable binding. See “Trap Service Database Syntax.”

Attribute Change Event Report

In 15–10, the event report in the highlighted line refers to a Disk component named by the second variable binding (%1). Variable bindings are described in “Trap Service Database Syntax.” Status is a site-defined attribute in the class Disk and is set to the value Off-Line.

Figure 26. Example of Generating an Attribute Change Event Report

This entry causes the following event report to be generated if the corresponding SNMP trap is received:

TYPE=AC | CLASS=Disk | INSTANCE=value1 |
APPL=SPO Trap Service | APPLQUAL=trap-service-system-name | 
HOST=managed-system-name | STATUS=Off-Line

where value1 is the value of the second variable binding. See “Trap Service Database Syntax.”

Delete Object Event Report

In 15–11, the event report in the highlighted line refers to a Disk component named by the second variable binding (%1). Setting the INSTANCE attribute overrides the default managed-system-name.

Figure 27. Example of Generating a Delete Object Event Report

This entry causes the following delete object event report to be generated if the corresponding SNMP trap is received:

TYPE=DE | CLASS=Disk | INSTANCE=value1 | 
APPL=SPO Trap Service | APPLQUAL=trap-service-system-name

where value1 is the value of the second variable binding. See “Trap Service Database Syntax.“