Re: [nv-l] Mib2trap

[Gareth Holl <gholl@us.ibm.com>]

Unsigned32 is being used somewhere around
line 47 but has not been previously defined. You may need to find a MIB
that defines it and then concatenate it with your MIB, as you would for
all MIBs defined in the IMPORT statements of the AVAYA MIB.

If you are trying to build a MIB database
file that will later be used with mib2trap (the technique James Shanks
re-published on the listserv recently), then you will need to load all
the MIBs (using xnmloadmib/xnmloadmib2) in the correct order, including
a MIB you are sure defines Unsigned32....do not assume the MIB defines
it just because you see it in the IMPORT statement of the AVAYA MIB.

Good luck.

Gareth

reamd@Nationwide.com
Sent by: owner-nv-l@lists.us.ibm.com

04/14/2006 03:37 PM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	[nv-l] Mib2trap

Hi all,
          I am attempted to run mib2trap on an
Avaya mib and received the
following:

mib2trap AVAYA-VMON-MIB.asn   job1.sh
         Errors - no script generated.
Textual convention doesn't map to real type.(Unsigned32): On or around
line
47
Bad parse of ASN type definition(::=).: On or around line 47

Can anyone help....

Thanks, Dave

AIX 5.1.5
7.1.4  FixPack3