3/4/2018 Document 434886.

Copyright (c) 2018, Oracle. All rights reserved.

Configuring SNMP Trap Notification Method in Enterprise Manager Grid Control - Steps and Troubleshooting (Doc ID 434886.1)

In this Document

Purpose
Scope
Details
SNMP Notification Method
Loading Enterprise Manager MIB Definitions into SNMP Console
Configuring SNMP Trap Notification Method
Troubleshooting Steps
References

APPLIES TO:

Enterprise Manager Base Platform - Version 10.1.0.2 to 11.1.0.1 [Release 10.1 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 26-OCT-2012***

PURPOSE

The notification methods define the method by which the notifications will be sent to the EM administrators. The available Notification methods in EM are:

Email Notification
SNMP Trap
PL/SQL Procedure
OS Command

This document describes the steps involved in configuring the SNMP Trap Notification Method available in Enterprise Manager Grid Control 10g and 11g.

Note: For enterprise Manager Cloud Control 12c, please check the Document 1532325.1 - 12c Cloud Control: Steps to Configure SNMP Trap Notification Method to
Send Traps to a Third Party SNMP Console

It is also necessary to define a Notification Rule. The Notification Rule provides an option to choose the targets and conditions under which the OMS should be sending
notifications.
The Notification Rules can be configured with the severities/violations of metrics/policies and various states of the Jobs for which the notification has to be sent for.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1695x513et_4&id=434886.1 1/5
3/4/2018 Document 434886.1

SCOPE

This document is applicable to EM administrators who want to configure Enterprise Manager to send SNMP Trap Notifications to a third party SNMP tool, whenever
critical/warning/clear alerts are raised for the targets.

DETAILS

SNMP Notification Method

Enterprise Manager supports integration with third-party management tools through the Simplified Network Management Protocol (SNMP). You can use the SNMP Trap
notification method to notify a third-party SNMP aware application that a particular metric has an alert in the EM Console.

The SNMP trap notification method must be configured by a super-administrator user before any user can choose to use this method in the notification rule.
The trap is an SNMP Version 1 trap and sent by Enterprise Manager's Management Services (OMS).
It is NOT necessary to configure the Notification Schedule for receiving SNMP Trap.
The SNMP Traps are directly sent by the OMS and the Agent is NOT involved in this operation.
The OMS does not use or need the OS level snmpd
processes to be configured / started for sending an SNMP Trap to the third party SNMP tool.
As the Agent is not involved, it is NOT necessary to start / configure the emsubagent process on the target nodes with the OS level snmpd.

Loading Enterprise Manager MIB Definitions into SNMP Console

The Enterprise Manager MIB definitions need to be loaded into the 3rd party SNMP Console, so that the Console can interpret the Trap details being sent by the OMS.
The MIB definition can be obtained using the steps in Document 389585.1: Where can I find the MIB file for Grid Control SNMP traps?

The file will be available as part of the installation from 10.2.0.5 Grid Control onwards.

Configuring SNMP Trap Notification Method

1. In the console, go to Setup -> Notification Methods.

2. Under the heading 'Scripts and SNMP Traps', choose Add 'SNMP Trap' in the drop down list and click on the go button
3. The next page will allow you to specify the details of the the SNMP aware Console.

Example:

Name: HP OpenView Console

Description: Notification method to send trap to HP openview console
SNMP Trap Host Name: abcd.oracle.com
SNMP Host Port: 162
SNMP Community: public

Mandatory fields are Name and SNMP Trap Host.

If the Port is left blank, default of 162 will be used.
If SNMP Community is left blank, default value of 'Public' will be used.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1695x513et_4&id=434886.1 2/5
3/4/2018 Document 434886.1

Note: Please verify with your Administrator who maintains the SNMP Console, for confirming the hostname, port and community details that is being used by the
tool.

4. Click on the 'Test SNMP Trap' to verify the above details. The OMS will send a test trap to the SNMP host using the details mentioned in the page. Verify that a test
Trap sent by the OMS is received in the SNMP console.

5. Click on 'Ok' to save the details.

6. The SMTP notification method is now ready for usage. You can choose this method when configuring the notification rules for the targets. Refer to the steps in Note
429422.1: How To Configure Notification Rules in EM.

7. When the metrics / violations chosen in the Notification rule are triggered, then the OMS will send an SNMP Trap to the SNMP Console.
An example SNMP Trap is shown below. All information is in one line which is sent as a variable embedded in the SNMP Trap :

Sat Jun 30 10:00:02 2007

Command: 4
Enterprise: 1.3.6.1.4.1.111.15.2
Agent: 138.1.6.200
Generic Trap: 6
Specific Trap: 1
Time Stamp: 8464:39.99
Count: 11
Name: 1.3.6.1.4.1.111.15.1.1.1.2.1
Kind: OctetString
Value: "database3"
Name: 1.3.6.1.4.1.111.15.1.1.1.3.1
Kind: OctetString
Value: "Database"
Name: 1.3.6.1.4.1.111.15.1.1.1.4.1
Kind: OctetString
Value: "emrep.us.oracle.com"
Name: 1.3.6.1.4.1.111.15.1.1.1.5.1
Kind: OctetString
Value: "Owner's Invalid Object Count"
Name: 1.3.6.1.4.1.111.15.1.1.1.6.1
Kind: OctetString
Value: "Invalid Object Owner"
Name: 1.3.6.1.4.1.111.15.1.1.1.7.1
Kind: OctetString
Value: "SYS"
Name: 1.3.6.1.4.1.111.15.1.1.1.8.1
Kind: OctetString
Value: "30-Jun-2007 08:59:10 (IST)"
Name: 1.3.6.1.4.1.111.15.1.1.1.9.1
Kind: OctetString
Value: "Warning"
Name: 1.3.6.1.4.1.111.15.1.1.1.10.1
Kind: OctetString
Value: "12 object(s) are invalid in the SYS schema."

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1695x513et_4&id=434886.1 3/5
3/4/2018 Document 434886.1
Name: 1.3.6.1.4.1.111.15.1.1.1.11.1
Kind: OctetString
Value: "Database Metrics"
Name: 1.3.6.1.4.1.111.15.1.1.1.12.1
Kind: OctetString
Value: "SYSMAN"

The SNMP Trap consists of these variables:

oraEM4AlertEntry: Information about a particular Enterprise Manager alert

oraEM4AlertIndex: Index of a particular alert, unique only at the moment an alert is generated.
oraEM4AlertTargetName: The name of the target to which this alert applies.
oraEM4AlertTargetType: The type of the target to which this alert applies.
oraEM4AlertHostName: The name of the host on which this alert originated.
oraEM4AlertMetricName: The name of the EM metric / Policy which generated this alert.
oraEM4AlertKeyValue: The value of the key-column, if present, for the EM metric which generated this alert.
oraEM4AlertTimeStamp: The time at which this alert was generated.
oraEM4AlertSeverity: Depending on the metric, this can be Critical / Warning / Clear / Up / Down/ Agent Unreachable / Agent Unreachable Clear / Blackout Start
/ Blackout End
oraEM4AlertMessage: The message generated by EM for this alert.
oraEM4AlertRuleName: The name of the notification rule that caused this notification.
oraEM4AlertRuleOwner: The owner of the notification rule that caused this notification.

Troubleshooting Steps

1. If you are using 10.1.0.x GC and find that Email Notifications are being sent but OMS is unable to send SNMP Traps, you could be hitting the following Bug : ERROR:
DELIVERING NOTIFICATIONSNMPFORMATEXCEPTION: OVERFLOW: UNSIGNED INT IS TOO

The <OMS_HOME>/sysman/log/emoms.trc will show errors:

2005-09-13 08:57:58,606 [DeliveryThread-SNMP3] ERROR em.notification deliver.185 - MetricSeveritySnmpTrap: oracle.sysman.snmp.SnmpFormatException:

Overflow: Unsigned int is too small

This is an unpublished bug, NOT viewable via My Oracle support.

The bug has been fixed in the 10.2 GC version and there is a generic one-off patch available on top of the 10.1.0.4 OMS version.

2. If you have problems receiving the SNMP Traps, check the following:

Is the 'Test SNMP Trap' working fine? If a test trap is not received by the SNMP Console, re-check the details provided in the notification methods page. The OMS
should be able to resolve the hostname of the SNMP console and the port should not be blocked by a firewall or other network entities.
Is the metric alert raised in the console? If there is no alert for the metric, no notification will be sent.
Refer to the troubleshooting steps in Document 285093.1: - How to Troubleshoot Notifications That Are Hung / Stuck and Not Being Sent from EM 10g.
Check whether Email notifications can be configured in the setup. If the Emails are sent correctly for the same metrics but there are no SNMP traps, this will help
in confirming that the issue is with only the SNMP setup and not with the Notification system in general.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1695x513et_4&id=434886.1 4/5
3/4/2018 Document 434886.1

We can also check whether the SNMP Traps sent by the OMS is received on the host where the SNMP Console is running, using this command:

# snmptrapd -p 162
By default, the UDP port 162 is used on all IPv4 interfaces. If the SNMP Console is configured on some other port, then mention the same in the
command.
Since 162 is a privileged port, snmptrapd must typically be run as root.
This command needs to be run on host machine where SNMP Console is running and listening for SNMP messages from Enterprise Manager.
This will list all the SNMP messages. There are also options available in the snmptrapd command, for filtering these messages in order to obtain only
required messages.

Reference:
Document 469884.1: How to Verify the SNMP Trap Contents Being Sent by Grid Control?
http://net-snmp.sourceforge.net/docs/man/snmptrapd.html

REFERENCES

NOTE:285093.1 - How to Troubleshoot Notifications That Are Hung / Stuck and Not Being Sent from EM 10g
NOTE:389585.1 - Where can I find the MIB file for Grid Control SNMP trap Notifications?
NOTE:429422.1 - How To Configure Notification Rules in Enterprise Manager Grid Control ?

NOTE:469884.1 - How to Verify the SNMP Trap Contents Being Sent by Grid Control?

NOTE:229627.1 - Enterprise Manager Grid Control Management Service (OMS) 10g - Locate and Manage the Log and Trace Files
NOTE:1532325.1 - 12c Cloud Control: Steps to Configure SNMP Trap Notification Method to Send Traps to a Third Party SNMP Console
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1695x513et_4&id=434886.1 5/5