Receiving SNMP Traps in OracleEnterprise ManagerAn Oracle White PaperJune 2009

Receiving SNMP Traps in Oracle Enterprise ManagerIntroduction. 3Common Usage Scenarios. 4Receiving SNMP Traps. 4Design the Management Plug-in. 5Map the SNMP Traps to OEM alerts. 5Develop the metadata files that make up a Management Plug-in.7Validate the metadata files. 16Create the Management Plug-in archive. 16Deploy the Management Plug-in. 16Add a new target in OEM. 17Update the trap destination. 17Optional: add a monitoring rule for new target type.18Conclusion. 19Receiving SNMP traps in Oracle Enterprise Manager Page 2

Receiving SNMP Traps in Oracle Enterprise ManagerIntroductionOracle Enterprise Manager (OEM) provides top-down applicationmanagement for Oracle technologies including Oracle packagedapplications, Oracle Fusion Middleware, Oracle Database and Oracle VM.However, it is often critical for an administrator to receive alerts fromapplications that are not managed by OEM. Many of these applications canbe configured to trigger SNMP traps when an alert condition takes place.You can receive these traps within OEM and start monitoring thoseapplications from OEM. Since OEM is optimized for analyzing historicalalerts, having the capability to receive and analyze SNMP traps raised bysuch applications allows you extend OEM’s monitoring and alertingcapabilities to these applications and reduce monitoring complexity in your ITenvironments.This paper provides a step-by-step guide for receiving SNMP traps in OracleEnterprise Manager.Note: The example used in this paper is based on the SNMP frameworkprovided by the Oracle Contact Center Anywhere (CCA) application. Youmay use the general guidelines specified here to build a plug-in to receiveSNMP traps from any application. If you want to send SNMP traps from OEMout to a trap receiver, refer to the SNMP support reference guide.1This document complements the official OEM configuration2 and the OfficialEM Extensibility guide3.1SNMP Support Reference Guide 01/doc/em.102/b16244/toc.htm2Advanced Configuration Guide: 01/doc/em.102/e10954/toc.htm3Extensibility Guide: 01/doc/em.102/b40007/toc.htmReceiving SNMP traps in Oracle Enterprise Manager Page 3

Common Usage ScenariosSNMP traps can be received in OEM from any application in your IT environment.Examples of scenarios when one would want to configure OEM to receive SNMPtraps include:Steps to receive SNMP traps:1.Design a management plug-in2.Deploy the management plug-in3.Add a target to OEM4.Update the trap destination5.Optional: Create notification rules Application server fronted by a load balancer: The middleware administrator may wantto be alerted when the load-balancer that fronts his application server is facingperformance problems. OEM can be configured to listen for load balancer traps. Oracle packaged application using a critical network switch: OEM can be configured tolisten for SNMP traps raised by critical network switches or routers. OEM as the central monitoring console: OEM can be configured to receive SNMPtraps from all SNMP enabled applications in the IT environment. Therebymaking it the central console of event monitoring in the datacenter.Receiving SNMP TrapsWe want to configure OEM to receive the SNMP traps raised by an application(figure 1) and display the traps as alerts in the OEM console.Figure 1: Showing the SNMP traps raised by CCA applicationIn order to receive these traps, we will develop a SNMP Receivelet basedManagement Plug-in. At a high level, you need to: Design the Management Plug-in Deploy the Management Plug-in Add a target to OEM Update the trap destinationReceiving SNMP traps in Oracle Enterprise Manager Page 4

Optional: Create notification rule and subscribe administrators to notificationrulesThe first step involves designing a management plug-in. The plug-in makes OEMagent capable of receiving SNMP traps. The plug-in also tells OEM how the trapsshould be displayed on its console.Design the Management Plug-inIn order to design a management plug-in, you need to: Map the SNMP traps to OEM alerts. Develop metadata files that make up a Management Plug-in. Validate the metadata files. Create the Management Plug-in Archive.Map the SNMP Traps to OEM alertsAs the first step, we need to understand how the SNMP traps map to OEM metricalerts. For that, you need to obtain the traps from the CCA MIB. Find below anextract of a few of the traps from the CCA MIB4.SNMPAgentShutdown TRAP-TYPEENTERPRISE telephonyatworkVARIABLES { trapInfo }DESCRIPTION "SNMPAgent is shutting down":: 1.SNMPAgentRunning TRAP-TYPEENTERPRISE telephonyatworkVARIABLES { trapInfo }DESCRIPTION "SNMPAgent is up and running":: 1001.companyDeleted TRAP-TYPEENTERPRISE telephonyatworkVARIABLES { trapInfo }DESCRIPTION "Company has been deleted": 5Notice that all traps use a single variable, trapInfo, shown in the Table 1.An individual SNMP trap maps to one and only one OEM metric while a singleOEM metric can map to one, two or three SNMP traps. For example, a singleOEM metric can be created to process trap ID 1 and 1001 above. We will map trapID 1 to an OEM alert with severity Critical and clear that alert on receipt of trap id1001. Traps 5, 6, and 27 on the other hand, map to one and only one critical OEMTo learn more about SNMP V1 Trap structure, go to SNMPVersion1SNMPv1MessageFormat-3.htm4Receiving SNMP traps in Oracle Enterprise Manager Page 5

alert metric since there is no corresponding Clear event trap ID defined. Table 1shows the mapping of some of the CCA Traps to OEM alert metrics.Matching OEM AlertMetricSNMP TrapTrap e 1.Mapping of sample CCA Traps to OEM alert metricsConstruct OIDs from CCA MIBProcess the CCA MIB either by reading the file or with the help of any availableMIB browser tool (there are several freeware versions available on the Internet).The table below lists some of the OIDs constructed from the CCA Trap Attribute (Product)Attributes of Company TableReceiving SNMP traps in Oracle Enterprise Manager Page 6

. 2.CommentScalar Trap AttributeCCA OIDsThe OIDs for Telephonyatwork and TrapInfo (Table 2) are OIDs needed fortraps while the rest of the OIDs in Table 2 are accessible and can be queried asneeded by the SNMP fetchlet.For the purpose of this paper, our focus will be on traps. Nonetheless, referencewill be made to these other accessible objects simply to illustrate that not all OIDsare necessarily SNMP trap related.Identify TrapsTable 3 shows the alert traps and the clearing traps.Alert Trap (Critical)Clearing TrapTrap IDNameTrap MaliciousCalltraceN/ATable 3.Sample CCA TrapsOnce we have identified the SNMP trap components, we can map them to EMalerts using the Management Plug-in metadata files. Table 4 summarizes themetadata files that constitute a Management Plug-in.NameDescriptionComment target type ttd.xmlTarget Type Metadata DefinitionDeployed to OH/sysman/admin/metadataTarget Default CollectionDeployed toDefinition OH/sysman/admin/default collection target type dc.xmlTable 4.Plug-in Metadata FilesDevelop the Metadata Files that Make Up a Management Plug-inThe first metadata file, the target type metadata definition (or ttd) XML file, definesthe target type, the metrics and the methods the OEM agent will be using to collectthose metrics. It contains the following required components: Document Type Definition (DTD) locationReceiving SNMP traps in Oracle Enterprise Manager Page 7

The DTD referenced here is the document that describes the content of the XMLfile and set constraints and restrictions on its structure. e.g. !DOCTYPE TargetMetadata SYSTEM "./dtds/TargetMetadata.dtd" META VERThis is the version of the metadata. Each time a plug-in is released with changes,the META VER should be bumped up. TYPEThe type uniquely identifies the kind of target instance this metadata file is for. Thetype must be unique within all target types of OEM. DisplayThe Display value is used in the OEM UI for the particular target type. TargetMetadata META VER "1.0" TYPE "oracle cca" Display Label NLSID "oracle cca" Oracle CCA Application /Label /Display MetricsA fetchlet is a parameterizeddata access mechanism thattakes arguments (For example,a script, a SQL statement, atarget instance's properties) asinput and returns formatteddata. A fetchlet ‘fetches’ orretrieves information byquerying at certain intervals.Each fetchlet handles aspecific type of data access.They are the dominant part of the metadata file and define all metrics to bemonitored for the target type. Display strings, data columns and the method usedto obtain the data values are all part of a metric definition.Note: In order for a target type to be considered valid, it must have a metric called Response containing ametric column named Status. This metric is used to monitor the state of the target (UP/DOWN). QueryDescriptorIn the example shown below, the Response metric is obtained by using the OEMagent’s SNMP fetchlet, which is specified in the QueryDescriptor. TheQueryDescriptor also contains properties that are needed by a fetchlet. There aremany different types of fetchlets supported by the OEM agent and SNMP fetchletis a special type of fetchlet. The SNMP fetchlet queries accessible SNMP objects asdefined in the target type’s MIB. The TableDescriptor contains definitions of all ofthe metric columns (in this case, there is just the single Status column). Similarmetric definitions could be defined with the metadata file so that the OEM agentcould collect other information about the target instance that is exposed throughthe SNMP MIB.If you are interested in creating metrics that have SNMP datapoints (vs. SNMPtraps), refer to the OEM Extensibility Guide on OTN.Receiving SNMP traps in Oracle Enterprise Manager Page 8

Metric NAME "Response" TYPE "TABLE" Display Label NLSID "oracle cca resp" Response /Label /Display TableDescriptor ColumnDescriptor NAME "Status" TYPE "NUMBER" Display Label NLSID "cca SNMP resp status" CCA SNMP SubAgentStatus /Label /Display /ColumnDescriptor /TableDescriptor QueryDescriptor FETCHLET ID "Snmp" Property NAME "NAME" SCOPE "INSTANCE" NAME /Property Property NAME "hostname" SCOPE "INSTANCE" AgentHost /Property Property NAME "PINGMODE" SCOPE "GLOBAL" TRUE /Property Property NAME "OIDS"SCOPE "GLOBAL" /Property Property NAME "COMMUNITY" SCOPE "INSTANCE"OPTIONAL "TRUE" CommunityString /Property Property NAME "TIMEOUT" SCOPE "INSTANCE"OPTIONAL "TRUE" Timeout /Property /QueryDescriptor /Metric The ‘NAME’ property contains the name of the CCA target instance.The ‘hostname’ property contains the location of the SNMP agent.The ‘PINGMODE’ property is typically used with the SNMP fetchlet within aResponse metric. When it is set to TURE, this property tells the fetchlet to returnthe SNMP target’s availability status to a column defined in the Response metric.The ‘OIDS’ property can contain a list OIDs that are defined in the target type’sMIB that correspond to properties that can be obtained. In this case, corresponds to the releaseVersion property in the MIB. Thefinal 0 in the OID signifies that a scalar object (single value) will be returned. Ifthere isn’t a trailing 0, then a table column (multiple values) will be returned. In theexample with the Response metric above, the OID specified is actuallyinconsequential since PINGMODE is set to TRUE.The ‘COMMUNITY’ property is the SNMP community value. If not specified thedefault value is public.The ‘TIMEOUT’ property corresponds to the SNMP timeout value, which defaultsto 5 seconds.Receiving SNMP traps in Oracle Enterprise Manager Page 9

PushDescriptorAn OEM agent can also listen for data through the use of a receivelet. The OEMagent supports different types of receivelets. The SNMP receivelet can be used bythe OEM agent to listen for SNMP traps as defined in the target type’s MIB. APushDescriptor is part of the metric definition of a receivelet.A Receivelet is a library thatallows Enterprise Manager toreceive notifications sent bythird-party network elements.A receivelet listens at aparticular port for thenotifications. These arenotifications that areasynchronously sent andwithout any requests fromOracle Management Agent.TELEPHONYATWORK-MIB DEFINITIONS :: BEGINIMPORTSenterprises, gaugeFROM RFC1155-SMIOBJECT-TYPEFROM RFC-1212DisplayStringFROM RFC-1213;.telephonyatwork OBJECT IDENTIFIER :: { enterprises 10477 }serverPart OBJECT IDENTIFIER :: { telephonyatwork 1 } trapInfo OBJECT-TYPESYNTAX DisplayStringACCESS read-onlySTATUS mandatoryDESCRIPTION "Trap Description":: { serverPart 6 } companyDeleted TRAP-TYPEENTERPRISE telephonyatworkVARIABLES { trapInfo }DESCRIPTION "Company has been deleted":: 5:: 5The type of receivelet is identified by the properties that the receivelet needs inorder to listen for a particular SNMP trap. Find below a portion of CCA’s MIBused in this example:generic-trap – generic trap typeINTEGER iseSpecific(6)}In addition, there are standard SNMP MIB definitions that will be referenced aswell. Below is the definition for generic-trap (RFC1157): The example belowdefines a metric, companyDeleted, which will listen for SNMP trap of the samename:Receiving SNMP traps in Oracle Enterprise Manager Page 10

Metric NAME "companyDeleted" TYPE "TABLE" Display Label NLSID "companyDeleted" Company Deleted /Label /Display TableDescriptor ColumnDescriptor NAME "trapInfoCompDel" STATELESS ALERTS "TRUE"TYPE "STRING" IS KEY "TRUE" Display Label NLSID "TrapInfo5" Company Deleted Trap(Stateless) /Label /Display /ColumnDescriptor /TableDescriptor PushDescriptor RECVLET ID "SNMPTrap" Property NAME "MatchEnterprise"SCOPE "GLOBAL" /Property Property NAME "MatchGenericTrap" SCOPE "GLOBAL" 6 /Property Property NAME "MatchSpecificTrap" SCOPE "GLOBAL" 5 /Property Property NAME "MatchAgentAddr"SCOPE "INSTANCE" AgentAddr /Property Property NAME "EventtrapInfoCompDelOID"SCOPE "GLOBAL" /Property Property NAME "SeverityCode"SCOPE "GLOBAL" CRITICAL /Property /PushDescriptor /Metric Since the companyDeleted SNMP trap does not have a corresponding clearingSNMP trap, STATELESS ALERTS is set to TRUE. In the case, the OEM UIallows the user to manually clear the alert. When an SNMP trap has acorresponding clearing SNMP trap (i.e. systemOverflow and systemLicenseOKfrom Table 1), STATELESS ALERTS is set to FALSE.The properties that can be used by the SNMP receivelet are defined in thefollowing ringOID used to define the trap being sent.RequiredMatchGenericTrapStringCode for a generic SNMP StringEvent metric-column StringTrap defined in a MIB (not one of the generictraps), the ID assigned to that MIB.IP address of the generating SNMP agent, assent in the trap.RequiredRequiredSpecifies that, on receiving this trap, theRequired, if eventsreceivelet should generate a severity on thishave to be generated.metric column. The value of the metricHowever, ifcolumn should be the value of this parameter.Event metric-(This case is useful where the expectedcolumn OID isReceiving SNMP traps in Oracle Enterprise Manager Page 11

ParameterTypeDescriptionUsevalues of the EM metric are not the same asprovided, then this isthe triggering SNMP variable.)not required.Specifies that, on receiving this trap, thereceivelet should generate a severity on thisEvent metriccolumn OIDStringmetric column. The value of the metriccolumn should be taken from the varbind inthe trap with OID equal to the value of thisparameter.SeverityCodeStringRequired, if eventshave to be generated.However, ifEvent metriccolumn is provided,then this is notrequired.Specifies the level at which the severityRequired. However, ifshould be generated. The value of thisSeverityCodeOID isparameter should be one of ‘CRITICAL’,provided, then this is‘WARNING’ or ‘CLEAR’.not required.Specifies the level at which the severityshould be generated. If the varbind in thetrap with OID equal to the value of thisparameter is one of the strings ‘CRITICAL’,‘WARNING’ or ‘CLEAR’, the severity shouldSeverityCodeOIDStringbe generated at that level; otherwise, noseverity should be generated. (Thisparameter would only be used if theRequired. However, ifSeverityCode isprovided, then this isnot required.integrator were designing a trap exclusivelyfor use with EM, but may be useful in thiscase.Specifies that, on receiving this trap, thereceivelet should generate a datapoint on themetric, for which the value of this metriccolumn should be taken from the varbind inthe trap with OID equal to the value of thisData metriccolumn OIDparameter. (An SNMP PushDescriptor mayStringhave many Data* parameters, in which casea single row will be returned, with all specifiedRequired, if datapointshave to be generated.columns populated from the appropriatevarbind in the trap. An SNMPPushDescriptor may not have both a Data*parameter and a Severity* parameter, normay it have multiple Severity* parameters.)Severity or datapoint generated by thisPushDescriptor should contain a key valuefor this metric column. The key value shouldKey metriccolumn OIDStringbe taken from the varbind in the trap with OIDequal to the value of this parameter. ForOptionalevery key column in the metric definition,there must be a Key* parameter in thePushDescriptor.Context metriccolumn OIDStringIf the PushDescriptor generates a severity,Optional. This can bethe severity should contain a value for thisused only formetric column in its event context. The valueseverities.should be taken from the varbind in the trapwith OID equal to the value of this parameter.Receiving SNMP traps in Oracle Enterprise Manager Page 12

ParameterTypeDescriptionUseIf the PushDescriptor generated a datapoint,this parameter is ignored.Table 5.SNMP Receivelet PropertiesIn the companyDeleted metric example above, MatchEnterprise is set totelephonyatwork (, which is the highest-level object identifierbased off of the standard enterprises value ( is set to 6, which is the enterpriseSpecific value for generic-trapfound in RFC1157. This implies that a specific trap value will also be supplied.MatchSpecificTrap is set to 5, which is the value of the companyDeleted TRAPTYPE in the MIB.MatchAgentAddr is set to the AgentAddr instance property value for the targetinstance.Event metric-column OID turns into EventrapInfoCompDelOID and has thevalue, which is the OID of trapInfo. The alert generated willbe for the trapInfoCompDel metric column.Finally, SeverityCode is set to ‘CRITICAL’ so when this SNMP trap is caught, thena critical level alert will be generated.NOTE: In the current 8.1.2 CCA build, the trapInfo variable is not sent with thegenerated traps. Instead, the trap contains a single variable with the OID set to1. In addition, the Trap Enterprise value from the trap is1. This value does not exist in the CCA MIB.This means for 8.1.2 CCA, the definition of the companyDeleted metric as shownabove should be modified so that both MatchEnterprise andEventtrapInfoCompDelOID properties have the value Instance PropertiesThese properties are those that uniquely identify a particular instance of a targettype. The oracle cca target type will have four target instance properties asillustrated below. The Labels that are specified are used in the EM UI on the pagewhere a target instance can be manually added. InstanceProperties InstanceProperty NAME "AgentHost" CREDENTIAL "FALSE"OPTIONAL "FALSE" Display Label NLSID "oracle cca SNMP agent host" Hostname (SNMP Agent ) /Label /Display /InstanceProperty InstanceProperty NAME "AgentAddr" CREDENTIAL "FALSE"OPTIONAL "FALSE" Display Label NLSID "oracle cca SNMP agent addr" IP Address (SNMP Agent) /Label /Display Receiving SNMP traps in Oracle Enterprise Manager Page 13

/InstanceProperty InstanceProperty NAME "CommunityString" CREDENTIAL "TRUE"OPTIONAL "TRUE" Display Label NLSID "oracle cca SNMP community string" SNMP ReadCommunity String (Default: public) /Label /Display public /InstanceProperty InstanceProperty NAME "Timeout" CREDENTIAL "FALSE"OPTIONAL "TRUE" Display Label NLSID "oracle cca SNMP timeout" SNMP Timeout (Default: 30seconds) /Label /Display 30 /InstanceProperty /InstanceProperties Setting CREDENTIAL to TRUE results in the instance property gettingobfuscated while you type it in OEM’s Add Target page.When an instance property is set to be OPTIONAL, you need not specify it on theAdd Target page. A default value can be specified as can be seen for the instanceproperties CommunityString and Timeout above.The second metadata file, the target default collection (or dc) XML file, defines theschedule and collection interval for each metric added to the metadata typedefinition. It’s made up of the following Document Type Definition (DTD) locationThe DTD referenced here is the document describing the content of the XML fileand setting constraints and restrictions on its structure. e.g. !DOCTYPE TargetMetadata SYSTEM "./dtds/TargetCollection.dtd" Target Type referenceThe Target Type reference matches the TYPE set in the target type metadata file. TargetCollection TYPE "oracle cca" Collection ItemA collection for each metric that is defined in the target type metadata file. This caneither be obtained on a given schedule with a specific interval or simply bylistening. When dealing with SNMP, the collection definition largely depends onwhether the metrics are obtained through a fetchlet or a receivelet.Note: A collection item must be defined for the Response metric so that theavailability of the target instance is known to OEM.Receiving SNMP traps in Oracle Enterprise Manager Page 14

In the example below, a CollectionItem is set up for the Response metric. TheOEM agent collects it every 5 minutes. A Condition is defined for theStatus metric column so that when the value is 0, a critical alert will begenerated. For the Response metric there is no need to define awarning level alert. However, for other metric columns, it is likely thatwhen a critical alert threshold is set, a warning level threshold would beset as well. In addition, messages can be defined for display when thealert occurs or is cleared. CollectionItem NAME "Response" Schedule IntervalSchedule INTERVAL "5" TIME UNIT "Min"/ /Schedule Condition COLUMN NAME "Status"CRITICAL "0"WARNING "NotDefined"OPERATOR "EQ"OCCURRENCES "1"MESSAGE "%target% is unreachable or is down."MESSAGE NLSID "oracle cca response status"CLEAR MESSAGE "%target% is up."CLEAR MESSAGE NLSID "oracle cca response status clear"/ /CollectionItem Unlike the CollectionItem for a metric that is obtained by a fetchlet, no schedule orinterval is needed for a metric that gets its data from a receivelet. However, thePUSH property for the Condition must be set to “TRUE”. This indicates that theSNMP traps are being pushed by the SNMP agent rather than being pulled by theOEM agent on a given schedule. See the example shown below: CollectionItem NAME "companyDeleted" Condition PUSH "TRUE"COLUMN ”trapInfoCompDel”COLUMN NAME "trapInfo1"CRITICAL "1"MESSAGE " companyDeleted trap received for target %target%: %value%"MESSAGE NLSID "oracle cca tranInfoCompDel” /CollectionItem Messages can contain placeholders, which will be filled in when the alert message iscreated. Some of these placeholders include: %value% - value of the metric (or column of metric) %target% - name of the target %column name% - can include value columns as well as key columns%critical threshold%: the critical threshold of the conditionReceiving SNMP traps in Oracle Enterprise Manager Page 15

The next two sections cover detailed steps for building and deploying theManagement Plug-in.Validate the metadata files Download the EM PDK (empdk.jar)5 to validate the XML files to a workstationthat has a 10.1.x or 10.2.x OEM agent installed on it. Set the ORACLE HOME environment variable to the OEM agent’sORACLE HOME. Set the JAVA HOME environment variable to the proper location. Add JAVA HOME/bin to your PATH environment variable. Install the PDK as follows:java –jar emPDK.jar client -install dir pdk installation directory Add pdk installation directory /pdk/bin to your PATH environmentvariable and then run the following for command usage and summary:emcli help check mp Check the syntax of the metric metadata and the default collection files:emcli check mp –metadata file oracle cca ttd.xml –collection file .oracle cca dc.xml –err level errorIf the files are well constructed, the program will return with no error message.Next you need to package all the metadata files into a portable management plug-inarchive.Create the Management Plug-in Archive Assuming that you have the same environment set up as when the metadata fileswere validated, use EMCLI to package the plug-in:emcli add mp to mpa -mpa "oracle cca.jar" -mp version "1.0"-ttd "oracle cca ttd.xml" -dc "oracle cca dc.xml" -func desc "CCA ManagementPlug-in to receive SNMP Traps" Tip: Deploy the plug-in toseveral agents in one go toreduce plug-in roll out time inyour datacenter.Copy the generated JAR to your local desktop.Deploy the Management Plug-inOracle Enterprise Manager 10g Grid Control Management Plug-in Development xtensions/management plugin sdk.html5.Receiving SNMP traps in Oracle Enterprise Manager Page 16

Import the Archive into OEM Go to: Setup Management Plug-ins. Click the Import button. Browse to the JAR location and select the file. Click the List Archive button. Select the listed CCA plug-in. Click the OK button to import.Push the plug-in to Agent(s) Identify the row for the Management Plug-in you just imported. Click the Deploy icon for the CCA Management Plug-in. Click the Add Agents button. In the Search and Select popup window, set Target Type to Agent in the LOV. Select the agent(s) where you would like the plug-in deployed. Click the Select button to dismiss the popup window. Hit the Next button and then the Finish button.Add a New Target in OEMEven though the CCA Management Plug-in has been deployed in OEM, it is notyet ready to accept and display the SNMP traps. You have to create a targetinstance within OEM that can display alerts.Follow the steps below to add the target: Go to Setup Agents. Select the agent the Management Plug-in has been deployed to by clicking on itslink. Select the target type (Oracle CCA Application) from the Add dropdown andclick Go. On the target configuration page, fill in the target instance name (a suggestedformat could be target-type hostname ).e.g. oracle cca myhost Fill in the Hostname, which is the location of where the SNMP daemon for CCAis running.e.g. Fill in the AgentAddr as the IP address of Hostname. Optionally fill in CommunityString, which defaults to public. Optionally fill in Timeout as the value for the SNMP timeout, which defaults to30 seconds. Click the OK button to add the target.Receiving SNMP traps in Oracle Enterprise Manager Page 17

Now that OEM is ready to receive the SNMP alerts, you must point the SNMPtrap originator to the OEM agent where the Management Plug-in is deployed.Update the Trap DestinationIn order to successfully receive traps from CCA, the trap d

Construct OIDs from CCA MIB Process the CCA MIB either by reading the file or with the help of any available MIB browser tool (there are several freeware versions available on the Internet). The table below lists some of the OIDs constructed from the CCA MIB. Name OID