What are the MIB OIDs in EventManager traps from Performance Management
Article ID: 145206
Updated On:
Products
CA Infrastructure Management
CA Performance Management - Usage and Administration
DX NetOps
Issue/Introduction
Sending EventManager traps from Performance Management.
After loading the MIB files in the trap receiver, there are still some OIDs not being mapped.
We need a full MIB covering the 4498.x tree but specifically we are missing anything past SNMPv2-SMI::enterprises.4498.7.1.9.X
Environment
All supported Performance Management releases
Resolution
EventManager traps from Performance Management are defined in the netqos-em-mib file found in (default path) /opt/CA/PerformanceCenter/PC/webapps/pc/mibs.
The EventManager trap format sends the netQoSEvent Trap Type. It contains the following OIDs and their values as defined per the netqos-em-mib file.
When the trap arrives, it will arrive with many more OIDs than those listed. The netQoSEventPropertyName and netQoSEventPropertyValue OIDs will come in pairs after the above list of defining OIDs.
They are defined in the data presented and when reviewed in alternating order it may begin to make sense. Broken out by traditional table number sequences can make it more confusing.
A small sample would be something like:
Each subsequent entry will have a Property Name followed by it's property value, with the last number in the OID incrementing for each pair of property name and value.
The EventManager trap format sends the netQoSEvent Trap Type. It contains the following OIDs and their values as defined per the netqos-em-mib file.
netQoSEvent TRAP-TYPE (1.3.6.1.4.1.4498.7.0.1)
ENTERPRISE eventManager (1.3.6.1.4.1.4498.7)
VARIABLES {
netQoSEventID: 1.3.6.1.4.1.4498.7.1.1
netQoSEventType: 1.3.6.1.4.1.4498.7.1.2
netQoSEventCategory: 1.3.6.1.4.1.4498.7.1.3
netQoSEventSeverity: 1.3.6.1.4.1.4498.7.1.4
netQoSEventDescription: 1.3.6.1.4.1.4498.7.1.5
netQoSEventState: 1.3.6.1.4.1.4498.7.1.6
netQoSEventOpenTime: 1.3.6.1.4.1.4498.7.1.7
netQoSEventMapURL: 1.3.6.1.4.1.4498.7.1.10
netQoSEventDetailsURL: 1.3.6.1.4.1.4498.7.1.11
netQoSEventAssociatedItemURL: 1.3.6.1.4.1.4498.7.1.12
netQoSEventItemName: 1.3.6.1.4.1.4498.7.1.8.1.2
netQoSEventItemType: 1.3.6.1.4.1.4498.7.1.8.1.3
netQoSEventItemSubType: 1.3.6.1.4.1.4498.7.1.8.1.4
netQoSEventItemIpAddress: 1.3.6.1.4.1.4498.7.1.8.1.5
netQoSEventPropertyName: 1.3.6.1.4.1.4498.7.1.9.1.2
netQoSEventPropertyValue: 1.3.6.1.4.1.4498.7.1.9.1.3
When the trap arrives, it will arrive with many more OIDs than those listed. The netQoSEventPropertyName and netQoSEventPropertyValue OIDs will come in pairs after the above list of defining OIDs.
- First one is the property name using OID 1.3.6.1.4.1.4498.7.1.9.1.2.x.
- Second one is property value using OID 1.3.6.1.4.1.4498.7.1.9.1.3.x.
They are defined in the data presented and when reviewed in alternating order it may begin to make sense. Broken out by traditional table number sequences can make it more confusing.
A small sample would be something like:
1.3.6.1.4.1.4498.7.1.9.1.2.1) AlarmRuleID; <== Property Name AlarmRuleID
1.3.6.1.4.1.4498.7.1.9.1.3.1) 2824660; <== AlarmRuleID propery value
1.3.6.1.4.1.4498.7.1.9.1.2.2) AlarmRuleName; <== Property Name AlarmRuleName
1.3.6.1.4.1.4498.7.1.9.1.3.2) Interface_Out_Discard_Over_1_pct; <== AlarmRuleName property value
1.3.6.1.4.1.4498.7.1.9.1.2.3) _Alarm_ID; <== Property Name AlarmID
1.3.6.1.4.1.4498.7.1.9.1.3.3) 132593798436031; <== AlarmID property value
1.3.6.1.4.1.4498.7.1.9.1.2.4) AlarmDuration; <== Property Name AlarmDuration
1.3.6.1.4.1.4498.7.1.9.1.3.4) 600; <== AlarmDuration property value
1.3.6.1.4.1.4498.7.1.9.1.2.5) AlarmWindow; <== AlarmWindow Property Name
1.3.6.1.4.1.4498.7.1.9.1.3.5) 600; <== AlarmWindow property value
Each subsequent entry will have a Property Name followed by it's property value, with the last number in the OID incrementing for each pair of property name and value.
Feedback
Yes
No
Powered by
