RE: Re: Addtrap problem.

[James_Shanks@tivoli.com]

Two way to go about this.

(A) First way -- analysis
(1) Find the TRAP-TYPE macro and see what is in the ENTERPRISES field.
     for example
          entityWatchdogTimeout  TRAP-TYPE
               ENTERPRISES  usr
               VARIABLES  {               etc
(2) Find where what is in the ENTERPRISES field is defined as an OBJECT
     for example
          usr   OBJECT IDENTIFIER  : :=  {  xxxx   1 }
(3) Keep going back until you get to one which  ties back to  "enterprises"
     for example
          xxxx OBJECT IDENTIFIER  : :=  {  enterprises 429 }
(4)  Since "enterprises" refers to ".iso.org.
dod.internet.private.enterprises" or ".1.3.6.1.4.1",
       you build the enterprise id by  reading backward what you have
found.
     for example
          1.3.6.1.4.1.429.1

(B) Second way - construction
(1)  Read the IMPORTS section of the MIB you just ran mib2trap on and
determine what other MIBs by this vendor it depends on.
     They should be listed there.
(2)  Find that imported MIB file and concatenate the one you just used,
which contains the TRAP-TYPE construct, to it to create one big file of
     two MIBs.
(3) Repeat this process until there are no more files to concatenate (it is
usually just two or three).
(3) Run mib2trap on the new combined file and it should resolve the
enterprise id correctly.



Hope this helps.  You can call Support for assistance.

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT



Stephen Elliott <selliott@epicrealm.com> on 10/25/2000 02:32:16 PM

Please respond to IBM NetView Discussion <nv-l@tkg.com>

To:   "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  RE: [NV-L] Re: Addtrap problem.




Ray,

I am experiencing similar problems with Altiga traps as you did with the
8272 system noted in your email below. The addtrap script generated by
mib2trap also lacks the -i option specifying the enterprise ID. Looking at
the MIB file, tho, I am at a loss how to proceed tracking it back to it's
root. Could you please pass on how you tracked down the e-ID for the 8272?

Thank You & Regards,

Steve Elliott
Sr. Network Mgmt. Engineer
epicRealm, Inc.
214-570-4560


-----Original Message-----
From: Ray Westphal [mailto:rwestphal@erac.com]
Sent: Monday, October 09, 2000 7:15 AM
To: NV List (E-mail)
Subject: [NV-L] Re: Addtrap problem.


Thanks James & Mythili .....

You were both correct. Here's the format that finally worked.

/usr/OV/bin/addtrap -n ibm8272TsSys -l ibm8272TsTempThreshold \
   -i 1.3.6.1.4.1.2.6.66 -g 6 -s 1 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "This trap is generated when the system temperature
either exceeds 50 C or when it returns to normal(45 C)
after exceeding the temperature. The variable
ibm8272Ts2SysTemperature indicates the temperature
condition at the time of the event."  \
   -e ibm8272TsTempThreshold  \
   -F '$E $G $S $# args: $*'

Ray Westphal



_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l