Conference molar::snmp

288.0. "MS SMS MIB for HP Openview??" by NEWVAX::WHITMAN (gun control = 5% gun + 95% control) Mon Apr 28 1997 21:01

     I have to write a MIB for Microsoft SMS' Event to Trap Translator which
will allow an HP Openview NMS catch the traps it generates.

     Microsoft SMS' uses an odd OID construct.
They have the normal 1.3.6.1.4.1.311 for their Enterprise, then 1.4.1 for SMS 
translated traps, then it gets wierd; the next number in the OID is the number
of characters in the name of application generating the event being translated,
followed by the ASCII value of each letter in the name of the application (i.e.
if the event was generated by "Perfmon" then the OID contains
7.80.101.114.102.109.111.110, 7 characters followed by the ASCII character
values of 'P' 'e' 'r' 'f' 'm' 'o' and 'n'). The trap id is 1073743824 so the
entire OID of the trap as sent is: 
  
1.3.6.1.4.1.311.1.4.1.7.80.101.114.102.109.111.110.1073743824

My problem, at the moment, is that HP Openview does not appear to recognize any
of the OID numbers past 1.3.6.1.4.1.311.1.4.1 except the TRAP-ID.

I have calls into Microsoft and into HP, but have not received any response
yet.

My question is - shouldn't HP Openview recognize the OID to an arbitrary length
(i.e. if my MIB specifies 18 numbers in the OID, Openview should read and accept
18 numbers)?  If not is there some MIB construct I can use to force the issue.

I'm sure my MIB still has problems with the variables, but I'll get after fixing
those once I get the OID issue straightened out.

The traps are arriving, but are being logged in the "what the heck is this trap"
log (i.e. HP Open view doesn't recognize the full trap-id)..

I'm attaching the MIB file I'm trying to load if it will help solve my problem.

Thanks,

Al Whitman

    WINDOWS-NT-PERFORMANCE DEFINITIONS ::= BEGIN
    IMPORTS
        enterprises
            FROM RFC1155-SMI
        OBJECT-TYPE
            FROM RFC-1212
        TRAP-TYPE
            FROM RFC-1215
        DisplayString
            FROM RFC-1213;

    microsoft     OBJECT IDENTIFIER ::= { enterprises 311 }
    software      OBJECT IDENTIFIER ::= { microsoft 1 }
    event         OBJECT IDENTIFIER ::= { software 4 }
    xlator        OBJECT IDENTIFIER ::= { event 1 }
        perfmon   OBJECT IDENTIFIER ::= { xlator 7.80.101.114.102.109.111.110 }

--   src_count       OBJECT IDENTIFIER ::= { xlator 7 }
--    	p    OBJECT IDENTIFIER ::= { src_count 80 }
--      e    OBJECT IDENTIFIER ::= { p 101 }
--	r    OBJECT IDENTIFIER ::= { e 114 }
--	f    OBJECT IDENTIFIER ::= { r 102 }
--	m    OBJECT IDENTIFIER ::= { f 109 }
--	o    OBJECT IDENTIFIER ::= { m 111 }
--	n    OBJECT IDENTIFIER ::= { o 110 }
----------------------------------------------------------------------------
    -- perfmon MIB

--   perfmon   OBJECT IDENTIFIER ::= { xlator 7.80.101.114.102.109.111.110 }
    PerfmonNetAddr OBJECT-TYPE
        SYNTAX INTEGER
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Network Address of the WindowsNT machine generating the trap."
        ::= { perfmon 1 }

    PerfmonGenTrapId OBJECT-TYPE
        SYNTAX INTEGER
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Always 6."
        ::= { perfmon 2 }

    PerfmonSpecTrapId OBJECT-TYPE
        SYNTAX INTEGER
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Always 1073743824"
        ::= { perfmon 3 }

    PerfmonTimestamp OBJECT-TYPE
        SYNTAX INTEGER
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Time in hundreths of seconds since SNMP agent was started."
        ::= { perfmon 4 }

    PerfmonMessage OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "An Alert condition has occurred on Computer: %1!s! ; Object:   %2!s! ;   Counter:  %3!s! ; Instance: %4!s! ; Parent:   %5!s! ; Value:    %6!s! ;   Trigger:  %7!s!  "
        ::= { perfmon 5 }

    PerfmonUserName OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "The User account which generated the SNMP trap"
        ::= { perfmon 6 }

    PerfmonComputerName OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Name of machine which generated the trap"
        ::= { perfmon 7 }

    PerfmonEventType OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Severity of the error"
        ::= { perfmon 8 }

    PerfmonEventCategory OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Category of the event which triggered the trap"
        ::= { perfmon 9 }

    PerfmonComputer OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Computer which triggered the trap"
        ::= { perfmon 10 }

    PerfmonObject OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Object which triggered the trap"
        ::= { perfmon 11 }

    PerfmonCounter OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Counter which triggered the trap"
        ::= { perfmon 12 }

    PerfmonInstance OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Instance value of counter that triggered the trap"
        ::= { perfmon 13 }

    PerfmonParent OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Parent Process"
        ::= { perfmon 14 }

    PerfmonCtrValue OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Value of the counter"
        ::= { perfmon 15 }

    PerfmonTrapTrigger OBJECT-TYPE
        SYNTAX DisplayString
        ACCESS read-only
        STATUS mandatory
        DESCRIPTION
            "Trigger Level for this event"
        ::= { perfmon 16 }

-------------------------------------------------------------------------
--  Trap definitions for SMS Event to Trap Translator
-------------------------------------------------------------------------
PerfmonTrap	      TRAP-TYPE
	ENTERPRISE    xlator
	VARIABLES    { PerfmonNetAddr, PerfmonGenTrapId,
                        PerfmonSpecTrapId, PerfmonTimestamp,
                        PerfmonMessage, PerfmonUserName,
                        PerfmonComputerName, PerfmonEventType,
                        PerfmonEventCategory, PerfmonComputer,
                        PerfmonObject, PerfmonCounter,
                        PerfmonInstance, PerfmonParent,
                        PerfmonCtrValue, PerfmonTrapTrigger }
        DESCRIPTION   "Traps generated by Winnt Perfomance Monitor."
        ::= 1073743824
	


END

>entire OID of the trap as sent is: 
  
>1.3.6.1.4.1.311.1.4.1.7.80.101.114.102.109.111.110.1073743824

How is this OID sent?  As the value of the enterprise field
in a v1 Trap-PDU?

If so, then I wouldn't expect anything to understand it.

The TRAP-TYPE macro in the mib specified the enterprise
as "xlator", not "perfmon".  So I'd expect `xlator' in the
enterprise field.

Also, the trap id value 1073743824 is sent as the specific-trap field
in the PDU, not tacked onto the end of the enterprise oid
(i don't know if that matters to the trap-catcher code in openview).

Hope this helps,
Mike

Mike

   thanks.  I'll go looking a bit closer.

Al

Mike,

   Thanks again for the tips.  I modified the MIB and it now seems to be working

I wound up having to define the "perfmon" part of the OID a piece at a time

...
...
      src_count       OBJECT IDENTIFIER ::= { xlator 7 }
    	      p    OBJECT IDENTIFIER ::= { src_count 80 }
             pe    OBJECT IDENTIFIER ::= { p 101 }
	    per    OBJECT IDENTIFIER ::= { pe 114 }
	   perf    OBJECT IDENTIFIER ::= { per 102 }
	  perfm    OBJECT IDENTIFIER ::= { perf 109 }
	 perfmo    OBJECT IDENTIFIER ::= { perfm 111 }
	perfmon    OBJECT IDENTIFIER ::= { perfmo 110 }
...
...

   but after doing that AND changing the Enterprise value in the TRAP-TYPE
definition, Openview accepted the weird OID and is recognizing the traps
Microsoft SMS Event to Trap translator is sending it...

Thanks for the help and ignore the phone message I left you earlier today.

Al