New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Absent Member.. Absent Member..
Absent Member..
228 views

CPU Performance Alert Not Right In OMi

We have NNMi integrated with OMi using HPOM agent integration.  This is working fine with an issue being worked by HP support.  However, we have an issue that makes little sense.  In NNMi we have configured performance alerting on CPU performance.  An instance occurred where the alert triggered resulting in the CpuOutOfRangeOrMalfunctioning management trap being sent.  For some reason, however, the title inserted in the event was not the message text we configured in NNMi.  Instead, the title was populated with the same contents found in the Source Info tab.  This makes no sense as the title has, for all other events from NNMi, shown the configured message content as defined in NNMi.

 

Is it possible there could be some bug in NNMi a patch for which might want to be installed?  I can write OMi EPI code to modify the title but I would prefer not doing so if not needed.

 

Generic: 6; Specific: 1000; Community: public; Enterprise: .1.3.6.1.4.1.11.2.17.19.2;
Variables:

[1] .1.3.6.1.4.1.11.2.17.19.2.2.1 (OctetString): NNMi
[2] .1.3.6.1.4.1.11.2.17.19.2.2.2 (OctetString): https://nnmisrv1.mitre.org:443/nnm
[3] .1.3.6.1.4.1.11.2.17.19.2.2.3 (Integer): 225613
[4] .1.3.6.1.4.1.11.2.17.19.2.2.4 (Null): NULL
[5] .1.3.6.1.4.1.11.2.17.19.2.2.5 (OctetString): CpuOutOfRangeOrMalfunctioning
[6] .1.3.6.1.4.1.11.2.17.19.2.2.6 (OctetString): 97da1534-3a5b-4124-b118-f8a9ed938dcc
[7] .1.3.6.1.4.1.11.2.17.19.2.2.7 (OctetString): com.hp.nms.incident.category.Fault
[8] .1.3.6.1.4.1.11.2.17.19.2.2.8 (OctetString): com.hp.nms.incident.family.ComponentHealth
[9] .1.3.6.1.4.1.11.2.17.19.2.2.9 (OctetString): MANAGEMENTSOFTWARE
[10] .1.3.6.1.4.1.11.2.17.19.2.2.10 (Integer): 1
[11] .1.3.6.1.4.1.11.2.17.19.2.2.11 (OctetString): mwwlgw CPU utilization high
[12] .1.3.6.1.4.1.11.2.17.19.2.2.12 (Integer): 5
[13] .1.3.6.1.4.1.11.2.17.19.2.2.13 (Integer): 5
[14] .1.3.6.1.4.1.11.2.17.19.2.2.14 (Integer): 4
[15] .1.3.6.1.4.1.11.2.17.19.2.2.15 (OctetString): 20150304125917523-0500
[16] .1.3.6.1.4.1.11.2.17.19.2.2.16 (OctetString): 20150304125923232-0500
[17] .1.3.6.1.4.1.11.2.17.19.2.2.17 (OctetString): 20150304131158739-0500
[18] .1.3.6.1.4.1.11.2.17.19.2.2.18 (Integer): 0
[19] .1.3.6.1.4.1.11.2.17.19.2.2.19 (Null): NULL
[20] .1.3.6.1.4.1.11.2.17.19.2.2.20 (OctetString): com.hp.ov.nms.apa.symptom=NsCpuChanged,cia.thresholdParameter.cpu5min=com.hp.nms.statepoller.device.sensor.cpu5min,cia.thresholdPreviousValue.cpu5min=NORMAL,cia.thresholdMeasurementTime.cpu5min=2015-03-04T12:57:57.644-0500,cia.thresholdCurrentValue.cpu5min=HIGH,cia.thresholdUpperBound.cpu5min=100,cia.thresholdMeasuredValue.cpu5min=92,cia.thresholdLowerBound.cpu5min=90,cia.snmpoid=.1.3.6.1.4.1.11.2.17.19.2.0.9,,cia.reasonClosed=CpuInRangeAndFunctioning,cia.timeIncidentDetectedMs=1425491957523,cia.timeIncidentResolvedMs=1425492718728,cia.incidentDurationMs=761205
[21] .1.3.6.1.4.1.11.2.17.19.2.2.21 (OctetString): mwwlgw.mitre.org
[22] .1.3.6.1.4.1.11.2.17.19.2.2.22 (OctetString): d167eae5-b859-4e66-877b-dbcf16068f22
[23] .1.3.6.1.4.1.11.2.17.19.2.2.23 (OctetString): 345fcea394ff616bb43986bad4c8ec2d
[24] .1.3.6.1.4.1.11.2.17.19.2.2.24 (OctetString): 128.29.210.13
[25] .1.3.6.1.4.1.11.2.17.19.2.2.25 (OctetString): CPU  
[26] .1.3.6.1.4.1.11.2.17.19.2.2.26 (OctetString): com.hp.ov.nms.model.core.NodeSensor
[27] .1.3.6.1.4.1.11.2.17.19.2.2.27 (OctetString): 797336f2-fbd4-4e85-bf07-c11d75306ce6
[28] .1.3.6.1.4.1.11.2.17.19.2.2.28 (OctetString): 345fcea394ff616bb43986bad4c8ec2d
[29] .1.3.6.1.4.1.11.2.17.19.2.2.43 (OctetString): CpuInRangeAndFunctioning
[30] .1.3.6.1.4.1.11.2.17.19.2.2.44 (OctetString): CiHint:CPU @@mwwlgw.mitre.org

0 Likes
3 Replies
Highlighted
Fleet Admiral Fleet Admiral
Fleet Admiral

Hello Edward,

 

is $11 ([11] .1.3.6.1.4.1.11.2.17.19.2.2.11 (OctetString): mwwlgw CPU utilization high) what you expect in OM? Then the rule inside the policy should have $11 as the title. Is this really specific id 1000?

 

Kind regards

 

Allessandro

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

I looked at the policy and the title is set to <$11>.  That is what we expect for message.

 

I am not sure what you mean by "Is this really specific id 1000".

 

0 Likes
Highlighted
Fleet Admiral Fleet Admiral
Fleet Admiral

Hello Edward,

 

I have done a nnmopcexport.ovpl on my NNMi system here and the SNMP Trap specific OID of 1000 is this one:

 

# from EVENT EventLifecycleStateClosed .1.3.6.1.4.1.11.2.17.19.2.0.1000 "LOGONLY" Normal

 

So I am confused that "your" id is also the 1000:

 

Generic: 6; Specific: 1000; Community: public; Enterprise: .1.3.6.1.4.1.11.2.17.19.2;

 

Perhaps this has something to do with your issues.

 

Can you please describe exactly what you get and what you expect?

 

Kind regards

 

Allessandro

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.