Welcome to the fun of explaining SNMP version support for various
pieces of netview.
D T <dtmitre@yahoo.com> writes:
> Netview 7.1.2 on Solaris8 :: So I loaded a MIB into the v2 loader.
> Worked fine and I didn't get any errors, also had previously loaded
> the dependencies. When I log into the web console and attempt to
> walk the MIB, I can't see it. When I use snmpwalk on the agent
> machine, it outputs the first few MIBs with the actual name, and the
> rest with the number. The weird thing is I can walk the MIB using
> MGSoft. Did I miss a step or something?
You're seeing the impact of loading a MIB into the v1/v2 mib database
that isn't seen/used by another portion of netview.
/usr/OV/bin/snmpwalk uses the v1 MIB database in netview. To populate
this database, you would have had to load with /usr/OV/bin/xnmloadmib
(available via the X gui option "load mib SNMP", which in turn
populates the v1 mib database /usr/OV/conf/snmpmib.bin and its text
buddy /usr/OV/conf/snmpmib. To browse this database, you use the v1
mib browser /usr/OV/bin/xnmbrowser.
If you do not have mib files that are in v1 to load into this
database, you can't successfully load em, and hence you will not see
text descriptions with a /usr/OV/bin/snmpwalk. It's kinda a drag.
There is a second separate mib database that can take in v1 or v2
mibs.
To load it: /usr/OV/bin/xnmloadmib2
To browse it: /usr/OV/bin/xnmbrowser2 (gui option "browse mib snmpv1/v2")
I don't think that database gets used by anything but the xnmbrowser2
program.
--
Todd H.
http://www.toddh.net/
|