Hi,
Thanks for your answer !
I have merge the 2 mib
file and now it’s working!
Thanks for your time !
Julien
From:
nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of James Shanks
Sent: lundi 3 septembre 2007 23:44
To: Tivoli NetView Discussions
Subject: Re: [NV-L] VMWARE-TRAPS-MIB
mib2trap works on files, not on the loaded database per
se.
mib2trap <MIB file name> <output file>
<baroc file prefix>
so
it does not matter whether you have loaded the precursor MIBs or not.
In
this case, the error messages mean that the definitions in the VMWARE-TRAPS-MIB
are not sufficient to define all that you need. My guess is that you
require what is in the VMWARE-ROOT-MIB as well. So what you have to do is
to combine those MIBs into one big file and run mib2trap on that.
So
I would edit the VMWARE-ROOT-MIB and after it says END, copy into it the
VMWARE-TRAPS-MIB. Then run
mib2trap VMWARE-ROOT-MIB VMWARE.addtrap VMWARE
This
is the UNIX syntax. The Windows version requires that your output file
name end in ".bat" so I would change "VMWARE.addtrap"
to "VMWARE.bat"
Using
the baroc file syntax will be very helpful if you plan on sending the trap to
TEC. In 7.1.5 mib2trap was altered to create much more elaborate trap
definitions and for Windows, to build OID and CDS files for use with the tecad
adapter.
Hope
this helps,
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
|
"Mongin Julien"
<julien.mongin@volvo.com>
Sent
by: nv-l-bounces@lists.ca.ibm.com
09/03/2007 11:51 AM
|
Please
respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
|
|
|
To
|
<nv-l@lists.ca.ibm.com>
|
|
cc
|
|
|
Subject
|
[NV-L] VMWARE-TRAPS-MIB
|
|
Hi all,
I
have some troubles to add the VMWARE-TRAPS-MIB in Netview.
I
have successfully loaded in Netview:
VMWARE-ROOT-MIB.mib
VMWARE-TRAPS-MIB.mib
When
I tried to execute mib2trap am Error message :
./mib2trap
/usr/OV/snmp_mibs/VMWARE-TRAPS-MIB.mib /tmp/VMWARE-TRAPS-MIB.trap
Warning:
The mib description doesn't seem to be consistent.
Some
nodes couldn't be linked under the "iso" tree.
These
nodes are left:
Left-over
node vpxdObjValue ::= { vmwTraps 306 } (1)
Left-over
node vpxdNewStatus ::= { vmwTraps 305 } (1)
Left-over
node vpxdOldStatus ::= { vmwTraps 304 } (1)
Left-over
node vpxdVMName ::= { vmwTraps 303 } (1)
Left-over
node vpxdHostName ::= { vmwTraps 302 } (1)
Left-over
node vpxdTrapType ::= { vmwTraps 301 } (1)
Left-over
node vmConfigFile ::= { vmwTraps 102 } (1)
Left-over
node vmID ::= { vmwTraps 101 } (134)
Enterprise
object id not found for trap vmPoweredOn, (6,1).Enterprise object id not found
for trap vmPoweredOff, (6,2).Enterprise object id not found for trap vmHBLost,
(6,3).Enterprise object id not found for trap vmHBDetected, (6,4).Enterprise
object id not found for trap vmSuspended, (6,5).Enterprise object id not found
for trap vpxdTrap, (6,201).
Do
you have some Ideas to help ?
Thanks
Julien_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l
(Browser access limited to internal IBM'ers only)