The CA User Activity Reporting Module MIB file, CA-ELM.MIB, is on the installation DVD. The CA User Activity Reporting Module MIB is generated from the CEG source document, which contains the OIDs for each CEG field (elmAlertVariables).
The CA-ELM.MIB file begins with imports as follows:
CAELM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP,NOTIFICATION-GROUP
FROM SNMPv2-CONF DisplayString
FROM SNMPv2-TC;
The following representation is designed to show the structure of the CA User Activity Reporting Module MIB tree, where the top-level nodes include iso(1) org(3) dod(6) internet(1) private(4) enterprises(1). The actual CA-ELM.MIB is not formatted like this representation.
ca OBJECT IDENTIFIER::= { enterprises 791 }
elm MODULE-IDENTITY...::= { ca 9845 }
elmAlertVariables ::= { elm 2 }
source-username ::= { elmAlertVariables 1 }
source-domainname ::= { elmAlertVariables 2 }
source-groupname ::= { elmAlertVariables 3 }
...
result-severity ::= { elmAlertVariables 88 }
raw-event ::= { elmAlertVariables 89 }
snippet ::= { elmAlertVariables 90 }
elmAlertTrapGroup ::= { elm 3 }
elmTrap ::= { elmAlertTrapGroup 1 }
elmDynamicVariables ::= { elm 4 }
calmAPIURL ::= { elmDynamicVariables 1 }
dynamicData ::= { elmDynamicVariables 2 }
elmConformance ::= { elm 5 }
elmGroups ::= { elmConformance 1 }
elmDataGroup ::= { elmGroups 1 }
elmCompliances ::= { elmConformance 2 }
elmCompliance ::= { elmCompliances 3 }
The CA-ELM.MIB file defines one trap. That trap is defined as follows:
elmTrap NOTIFICATION-TYPE
OBJECTS { source-username,source-domainname,source-groupname,source-uid,source-gid,source-hostname,source-hostdomainname,source-address,source-mac-address,source-port,source-processname,source-objectname,source-objectattr,source-objectid,source-objectclass,source-objectvalue,dest-username,dest-domainname,dest-groupname,dest-uid,dest-gid,dest-hostname,dest-hostdomainname,dest-address,dest-mac-address,dest-port,dest-objectname,dest-objectattr,dest-objectid,dest-objectclass,dest-objectvalue,agent-name,agent-address,agent-hostname,agent-hostdomainname,agent-version,agent-id,agent-connector-name,agent-group,event-source-hostname,event-source-hostdomainname,event-source-address,event-source-processname,receiver-name,receiver-hostname,receiver-hostaddress,receiver-hostdomainname,receiver-port,receiver-time-gmt,receiver-timezone,receiver-version,event-protocol,event-logname,event-euuid,event-count,event-summarized,event-duration,event-time-year,event-time-month,event-time-monthday,event-time-weekday,event-time-hour,event-time-minute,event-time-gmt,event-datetime,event-year-datetime,event-month-datetime,event-day-datetime,event-hour-datetime,event-quarterhour-datetime,event-minute-datetime,event-timezone,event-sequence,event-trend,event-action,event-id,event-category,event-class,ideal-model,event-severity,event-result,result-string,result-signature,result-code,result-version,result-priority,result-scope,result-severity,raw-event,snippet }
STATUS current
DESCRIPTION
"The ELM SNMP Trap."
::= { elmAlertTrapGroup 1 }
The elmAlertTrapGroup is 1.3.6.1.4.1.791.9845.3 and the elmTrap is defined by the next node. The default elmTrap ID is 1.3.6.1.4.1.791.9845.3.1. User-defined Custom Trap IDs have the range 1.3.6.1.4.1.791.9845.3.2 to 1.3.6.1.4.1.791.9845.3.999.
Important! The best practice for sending traps to CA Spectrum is to use the default elmTrap ID. The best practice for sending traps to CA NSM is to specify a Custom Trap ID that references an elmTrap ID in a custom MIB.
|
Copyright © 2013 CA.
All rights reserved.
|
|