|
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
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
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>
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._______________________________________________________________ |
