Re: NNMi and Trap (418 Views)
Reply
Frequent Advisor
Le_savoyard
Posts: 46
Registered: ‎06-14-2001
Message 1 of 3 (421 Views)
Accepted Solution

NNMi and Trap

Hello every NNMi User

 

I would to know if there is a method to load trap in NNMi,

As after NNMi replace a numeric value in a trap by the value configured in the mib file

 

Here the custom attribute attach to the trap

.1.3.6.1.4.1.7779.3.1.1.1.2.2.0 asn_integ 4


and here the definition  of the varbind in the mib

ibTrapSeverity OBJECT-TYPE
	SYNTAX          INTEGER {
                         critical (5),   -- service impact problem
                         major    (4),   -- problem requiring user intervension
                         minor    (3),   -- problem not requiring user interv.
                         info     (2),   -- informational only
                         indetermined (1)
                        }
	MAX-ACCESS      accessible-for-notify
	STATUS          current
	DESCRIPTION     "It contains the serverity of the trap."
	::= { ibNotificationVarBind 2}


So I would like that NNMi directly tell that " ibTrapSeverity is major" and not .1.3.6.1.4.1.7779.3.1.1.1.2.2.0 asn_integ 4

thank you for your help

Honored Contributor
dieter boschung
Posts: 236
Registered: ‎12-18-2008
Message 2 of 3 (418 Views)

Re: NNMi and Trap

Hello Le_savoyard

 

If the mib has been correctly loaded then you can use the $text($<CIA_oid>) construct to replace the CIA_oid value with the corresponding text.

 

Your Incident message would look like:

 

ibTrapSeverity is $text($.1.3.6.1.4.1.7779.3.1.1.1.2.2.0)

 

See also the online help, search for "Functions to Generate Values Within the Incident Message"

And: http://support.openview.hp.com/selfsolve/document/KM964053

 

Kind regards

Dieter

 

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Frequent Advisor
Le_savoyard
Posts: 46
Registered: ‎06-14-2001
Message 3 of 3 (409 Views)

Re: NNMi and Trap

Thank for the response

 

 

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.