Highlighted
Pinion Honored Contributor.
Honored Contributor.
245 views

Alarm messages incorrect ?

Jump to solution

Hi All,

 

I have a question with the alarm message.

 

Alarm messages of trap ID '.1.3.6.1.4.1.2636.4.12.0.5' are incorrectly interpreted as messages of ID '.1.3.6.1.4.1.2636.0.5' in OVO.  Similarly, messages of ID '.1.3.6.1.4.1.2636.4.12.0.6' are interpreted as '.1.3.6.1.4.1.2636.0.6'.

 

the alarm was displayed as '.1.3.6.1.4.1.2636.0.5' in OVO message browser, while its trap ID is actually '.1.3.6.1.4.1.2636.4.12.0.5'. 

 

OVO matched the message to the template condition '.1.3.6.1.4.1.2636.0.5' instead of the condition '.1.3.6.1.4.1.2636.4.12.0.5'.

 

this is a normal expected ?Any idea ?

 

Thank you,

-/\-
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: Alarm messages incorrect ?

Jump to solution

Could it be that the condition that is matching is defined with:

 

Enterprise OID: .1.3.6.1.4.1.2636

Generic trap: any

Specific trap: any

 

Such a condition would match .1.3.6.1.4.1.2636.4.12.0.5 indeed and could show up as .1.3.6.1.4.1.2636.0.5 in the message browser depending on how your policy is defined.

 

In that case, you want to ensure that the more restrictive conditions are listed before the more generic conditions in your policy. So move your condition that should match .1.3.6.1.4.1.2636.4.12.0.5 higher up the list before the condition that is currently matching.

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: Alarm messages incorrect ?

Jump to solution

Could it be that the condition that is matching is defined with:

 

Enterprise OID: .1.3.6.1.4.1.2636

Generic trap: any

Specific trap: any

 

Such a condition would match .1.3.6.1.4.1.2636.4.12.0.5 indeed and could show up as .1.3.6.1.4.1.2636.0.5 in the message browser depending on how your policy is defined.

 

In that case, you want to ensure that the more restrictive conditions are listed before the more generic conditions in your policy. So move your condition that should match .1.3.6.1.4.1.2636.4.12.0.5 higher up the list before the condition that is currently matching.

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
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.