But I did run into a problem with no simple solution: even though the
rfc1650.mib file is included in the scotty_mibs variable in init.tcl,
the symbol "dot3" alias { transmission 7 } was not defined.
I looked over the C implementation, and it seems to me that the problem
lies in the fact, that the functions parse_mibfile/read_idxfile called in
function MIB_Parse, file snmp/parse.c, returns only one subtree for inclusion
in the MIB tree. But rfc1650 actually adds to the complete MIB tree at
two leaves, namely { mib-2 35 } for the compliance stuff and { transmission 7 }
for the actual data.
Truly enough, loading rfc1650.mib does indeed define the symbol etherMIB
as { mib-2 35 }. And removing the ethermib definition (and all definitions
derived from it) from rfc1650 before parsing solves the problem (as my
agents are all snmpv1 so they can't use the compliance definition anyway).
But that is not a good solution in the long run....
best regards
Peder Chr. Norgaard
Telebit Communications A/S,
Denmark