Re: [nv-l] SNMPv2

["Christopher J Petrina" <cjp8@meadwestvaco.com>]

Here are the imports of the MIB

ALCATEL-IND1-CHASSIS-MIB DEFINITIONS ::= BEGIN

IMPORTS
         OBJECT-TYPE,
         OBJECT-IDENTITY,
         MODULE-IDENTITY,
         NOTIFICATION-TYPE,
         Unsigned32,
         Counter32              FROM SNMPv2-SMI
         PhysicalIndex,
         entPhysicalIndex       FROM ENTITY-MIB
         hardentIND1Physical,
         chassisTraps,
         hardentIND1Chassis     FROM ALCATEL-IND1-BASE
         SnmpAdminString               FROM SNMP-FRAMEWORK-MIB
         TEXTUAL-CONVENTION     FROM SNMPv2-TC
         MODULE-COMPLIANCE,
         OBJECT-GROUP,
         NOTIFICATION-GROUP     FROM SNMPv2-CONF;



ChassisTrapsStrfileName  ::= TEXTUAL-CONVENTION
     STATUS        current
   DESCRIPTION
        "Name of the source file where the fault
        was detected. This is given by the C ANSI
        macro __FILE__. The path shouldn't appear."
        SYNTAX        SnmpAdminString(SIZE (0..19))              <------------------------   This is the Line they are referring to.

-Chris Petrina

James Shanks <jshanks@us.ibm.com> Sent by: owner-nv-l@lists.us.ibm.com 01/30/2004 03:42 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Subject:        Re: [nv-l] SNMPv2

OK, so what's on or around line 1252 of the MIB? 

My guess is that they have defined one textual convention in terms of another, which is really a no-no.  It should map to a base type as the message implies. 
But perhaps it does so in some other imported MIB which mib2trap doesn't know about. 

But a quick look at the IMPORTS section at the beginning , along with what's on 1252 ought to tell us whether that makes sense. 
Cut and paste 'em both.   Then we'll see whether we can make sense of it.

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

"Christopher J Petrina" <cjp8@meadwestvaco.com> Sent by: owner-nv-l@lists.us.ibm.com 01/30/2004 02:59 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com        cc:                Subject:        Re: [nv-l] SNMPv2

OK here is the error message I am receiving when I attempt to use mib2trap on the AlcatelIND1Chassis.mib 

# mib2trap chassis.mib chassis_trap 
        Errors - no script generated. 
Textual convention doesn't map to real type.(SnmpAdminString): On or around line 1252 
Bad parse of ASN type definition(::=).: On or around line 1252

James Shanks <jshanks@us.ibm.com> Sent by: owner-nv-l@lists.us.ibm.com 01/29/2004 03:49 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com       cc:               Subject:        Re: [nv-l] SNMPv2

If you want help on the list, then you have to post your error messages. My guess is that something else is wrong.

But yes, Level 2 Support would be happy to help you in just that way.

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

"Christopher J Petrina" <cjp8@meadwestvaco.com>

"Christopher J Petrina" <cjp8@meadwestvaco.com> Sent by: owner-nv-l@lists.us.ibm.com 01/29/04 11:29 AM Please respond to nv-l

To: nv-l@lists.us.ibm.com cc: Subject: Re: [nv-l] SNMPv2

I guess my question now then is would popening a PMR with Netview and sending them the MIBs and let them try to run mib2trap on it be the next choice? I have run mib2trap on the notification-types and it errors out each time. It could be that Alcatel's MIBs simply are not created properly. And they do not have a SNMPv1 version of the MIBs. 

-Chris Petrina 
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________