Re: Problem parsing rfc1650 with scotty-1.2.5, command mib load

Juergen Schoenwaelder (schoenw@ibr.cs.tu-bs.de)
Wed, 19 Jul 1995 10:00:36 +0200

Hi!

"Peder Chr. Norgaard" <pcn@tbit.dk> said:

Peder> But I did run into a problem with no simple solution: even though the
Peder> rfc1650.mib file is included in the scotty_mibs variable in init.tcl,
Peder> the symbol "dot3" alias { transmission 7 } was not defined.

Peder> I looked over the C implementation, and it seems to me that
Peder> the problem lies in the fact, that the functions
Peder> parse_mibfile/read_idxfile called in function MIB_Parse, file
Peder> snmp/parse.c, returns only one subtree for inclusion in the
Peder> MIB tree. But rfc1650 actually adds to the complete MIB tree
Peder> at two leaves, namely { mib-2 35 } for the compliance stuff
Peder> and { transmission 7 } for the actual data.

Your analysis is correct. The problem has been fixed in the
Tk4.0/Tcl7.4 based version of scotty. So either split your MIB
definitions into different files or upgrade to the new version
available on ftp.ibr.cs.tu-bs.de in /pub/local/tkined/devel.

Juergen