nv-l
[Top] [All Lists]

RE: [nv-l] Error when using mib2trap

To: "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Error when using mib2trap
From: "Bursik, Scott {PBSG}" <Scott.Bursik@pbsg.com>
Date: Tue, 23 Mar 2004 15:10:48 -0600
Delivery-date: Tue, 23 Mar 2004 21:24:55 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

Great. Thanks for the explanation! That makes perfect sense.

 

 

Scott Bursik

Enterprise Systems Management

PepsiCo Business Solutions Group

(972) 963-1400

scott.bursik@pbsg.com

 

 


From: James Shanks [mailto:jshanks@us.ibm.com]
Sent: Tuesday, March 23, 2004 2:55 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Error when using mib2trap

 


Remember that mib2trap works on the MIB file itself and not on the MIB database (/usr/OV/conf/snmpmib and snmpmib.bin or snmpv2mib and snmpv2mib.bin).  He only considered what's the file.  So he's telling you that he cannot resolve the textual convention DisplayString.


The IMPORTS tell you that this is defined in RFC1213-MIB.  So you can get that file and concatenate this Dell MIB to it to create a  big new MIB file, and run mib2trap on that, or you can just go look in that MIB file to where DisplayString is defined and copy that def into the Dell MIB before it used, before line 59, and all should be well

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group


"Bursik, Scott {PBSG}" <Scott.Bursik@pbsg.com>
Sent by: owner-nv-l@lists.us.ibm.com

03/23/2004 03:23 PM

Please respond to
nv-l

To

"'Nv-L (nv-l@lists.us.ibm.com)'" <nv-l@lists.us.ibm.com>

cc

 

Subject

[nv-l] Error when using mib2trap

 

 

 




AIX 4.3.3 NetView 7.1.3

I am getting errors when loading a MIB for Dell but I am not sure what the
error means. Anyone out there have an idea what this error is telling me?

Thank You!



/usr/OV/bin/mib2trap  DELL_10892.mib DELL_10892.mib.sh
        Errors - no script generated.
Textual convention doesn't map to real type.(DisplayString): On or around
line 59
Bad parse of ASN type definition(::=).: On or around line 59


Here is the MIB just a little past line 59
----------------------------------------------------------------------------
---
--
-- Server Administrator MIB : 10892.mib
--
-- Copyright (c) 2000-2002 Dell Computer Corporation.
-- All Rights Reserved.
--
-- The information and functionality described by this MIB file,
-- like many MIB files, is subject to change without notice. Please
-- examine the version number of this MIB and compare it to the version
-- number you are expecting.
--
-- MIB Version 1.55                     06 March 2002
--
----------------------------------------------------------------------------
---

MIB-Dell-10892 DEFINITIONS ::= BEGIN

IMPORTS
   enterprises, IpAddress
       FROM RFC1155-SMI
   OBJECT-TYPE
       FROM RFC-1212
   TRAP-TYPE
       FROM RFC-1215
   DisplayString
       FROM RFC1213-MIB;

-- Dell enterprises ID
dell                          OBJECT IDENTIFIER ::= { enterprises    674   }
-- Server Administrator
server3                       OBJECT IDENTIFIER ::= { dell           10892 }
-- Server Administrator Groups
baseboardGroup                OBJECT IDENTIFIER ::= { server3        1     }
drsOutOfBandGroup             OBJECT IDENTIFIER ::= { server3        2     }
mIBVersionGroup               OBJECT IDENTIFIER ::= { baseboardGroup 1     }
systemManagementSoftwareGroup OBJECT IDENTIFIER ::= { baseboardGroup 100   }
systemStateGroup              OBJECT IDENTIFIER ::= { baseboardGroup 200   }
chassisInformationGroup       OBJECT IDENTIFIER ::= { baseboardGroup 300   }
operatingSystemGroup          OBJECT IDENTIFIER ::= { baseboardGroup 400   }
systemResourceGroup           OBJECT IDENTIFIER ::= { baseboardGroup 500   }
powerGroup                    OBJECT IDENTIFIER ::= { baseboardGroup 600   }
thermalGroup                  OBJECT IDENTIFIER ::= { baseboardGroup 700   }
userSecurityGroup             OBJECT IDENTIFIER ::= { baseboardGroup 800   }
remoteFlashBIOSGroup          OBJECT IDENTIFIER ::= { baseboardGroup 900   }
portGroup                     OBJECT IDENTIFIER ::= { baseboardGroup 1000  }
deviceGroup                   OBJECT IDENTIFIER ::= { baseboardGroup 1100  }
slotGroup                     OBJECT IDENTIFIER ::= { baseboardGroup 1200  }
memoryGroup                   OBJECT IDENTIFIER ::= { baseboardGroup 1300  }
biosSetUpControlGroup         OBJECT IDENTIFIER ::= { baseboardGroup 1400  }
lraGroup                      OBJECT IDENTIFIER ::= { baseboardGroup 1500  }
cooGroup                      OBJECT IDENTIFIER ::= { baseboardGroup 1600  }
remoteAccessGroup             OBJECT IDENTIFIER ::= { baseboardGroup 1700  }
alertGroup                    OBJECT IDENTIFIER ::= { baseboardGroup 5000  }

--
-- Textual Conventions
--
DellString                  ::= DisplayString (SIZE (0..64))
DellSecurityString          ::= DisplayString (SIZE (0..255))
DellCostofOwnershipString   ::= DisplayString (SIZE (0..64))
DellObjectRange             ::= INTEGER (1..128)
DellUnsigned8BitRange       ::= INTEGER (0..255)
DellUnsigned16BitRange      ::= INTEGER (0..65535)
DellUnsigned32BitRange      ::= INTEGER (0..4294967295)
DellSigned32BitRange        ::= INTEGER (-2147483647..2147483647)
DellBoolean                 ::= INTEGER (0..1) -- FALSE = 0, TRUE = 1

-- Please Note:
-- Variables with definitions of xxxCapabilities or xxxCapabilitiesUnique
-- are integers representing a series of bit definitions. They are NOT
enumerations
-- and should be treated as bit fields. The value is passed as a decimal
value;
-- it should be converted to hex, and the appropriate bits should be parsed
from
-- that. Some of the more common bit combinations are defined in some
variables,
-- but not all combinations are or will be defined.
 
 
 


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web