Also sprach Mark Thornton
I got a bit farther. I can now get the 3Com to return the system info, but when I specify a directory containing all the 3Com mibs I get the following:
Unlinked OID in RFC1213-MIB (lots of these) system: Bad sub-id in object identifier (system)
Hrmm...try this: grep "RFC1213-MIB DEFINITIONS" * If it doesn't return anything, you need to get that MIB.
It doesn't seem to like the mibs that come with the 3Com distro.
The mibs themselves are pretty much fine...just the mibs identify at the top where they link in to the MIB tree, and the references that they are using are unknown, meaning your mib parser is building up the mib tree, but it doesn't see where this mib that its reading connects in. For example, near the top of the file nmc-mib.txt you'll see something like: usr OBJECT IDENTIFIER ::= { enterprises 429 } Basically this is telling the mib parser that the node "usr" is the 429th child of the enterprises node. If your mib tree doesn't have the enterprises node, then it doesn't know where to link in the NMC-MIB that its reading. What your error sounds like is that its not finding the node "system" (as a guess), which is the 1st child of mib-ii. So, you *should* be able to find a place with a line like: system OBJECT IDENTIFIER ::= { mib-ii 1 } this line would usually be found in the RFC1213-MIB that I referenced above. -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.