nv-l

RE: [nv-l] Mib2trap alcatel AOS devices

2004-01-13 14:19:06
Subject: RE: [nv-l] Mib2trap alcatel AOS devices
From: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
To: <nv-l AT lists.us.ibm DOT com>
Date: Tue, 13 Jan 2004 13:13:01 -0600
Sorry about that! Misdirected the reply!
-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]On Behalf Of Barr, Scott
Sent: Tuesday, January 13, 2004 12:52 PM
To: nv-l AT lists.us.ibm DOT com
Subject: RE: [nv-l] Mib2trap alcatel AOS devices

 
8888 is:
 
8888
  WEBGSM
    Ludovic Smadja
      lsmadja AT webgsm DOT com
 
-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]On Behalf Of Christopher J Petrina
Sent: Tuesday, January 13, 2004 12:43 PM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] Mib2trap alcatel AOS devices


using the AlcatelIND1Chassis.mib When doing a mib2trap I receive the following error

CMD:   mib2trap AlcatelIND1Chassis.mib A_Chassis.trap

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

I checked spelling and every portion of the MIb I could think of the section directly above that line parses out fine and is almost I dentical in nature.  

I guess my confusion lies in that I did not think that trapd could understand snmpV2 traps?  Maybe I misunderstood.  I thought that is where the trouble of when I use a xnmloadmib2 and then try to run mib2trap it does nto add anything to the xnmtrap configuration.

Thanks
Chris Petrina