Solution 1:

See here: https://web.archive.org/web/20090323043038/http://www.sifizm.com/2009/02/19/using-snmpget-or-snmpwalk-and-a-vendor-mib-file/

First, copy your .mib file into the directory where your script is located.

Then use snmpget in the following format:

snmpget [address] -c [community string] -v 1 -m [mib name] [object to scan]

Then use snmpwalk in the following format:

snmpwalk [address] -c [community string] -v 1 -m [mib name] [object to scan]

On most Linux systems, the MIB files should go to /usr/share/snmp/mibs or probably /usr/local/share/snmp/mibs.

Solution 2:

Put STRANGE-NEW-MIB.txt in the directory where all your other MIBs are stored (possibly /usr/share/snmp/mibs , but it may vary with distro, mine is Fedora 14), then do

snmpwalk -v 1 -c public -m +STRANGE-NEW-MIB 1.2.3.4

where you replace public with the real RO community strong, STRANGE-NEW-MIB is the name of your new MIB without the .txt suffix (if memory serves), and 1.2.3.4 is the IP address of your switch.