I find it works consistently by adding the mibs to the smi_modules
file ( there maybe more than 1 on your system ) such as
C:\Documents and Settings\<USER>\Application Data\Wireshark
C:\Program Files\Wireshark
I also add mibs to C:\usr\mibs and put that path into
smi_paths
"C:\Program Files\Wireshark\snmp\mibs;C:\usr\mibs"
That way the mibs I add don't get deleted by an install of wireshark.
Glenn
On Sat, Jul 25, 2009 at 6:11 AM, Tony Barratt<tbarratt@xxxxxxxxxxx> wrote:
> Ah! No. The mib did not.
> But now it does.
> And it loads just fine.
>
> Thanx!!
>> From: Glenn Andrews <gjandrews35@xxxxxxxxx>
>> Subject: Re: [Wireshark-users] enterprises.9
>> To: Community support list for Wireshark
>> <wireshark-users@xxxxxxxxxxxxx>
>> Message-ID:
>> <ff9475b60907231250l31ebcf72v9e6261305d712ead@xxxxxxxxxxxxxx>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Does this mib appear in the smi_modules file ?
>> Also the smi_paths file should contain the paths to your mib files.
>>
>> Glenn
>>
>> On Thu, Jul 23, 2009 at 1:37 PM, Tony Barratt<tbarratt@xxxxxxxxxxx> wrote:
>>
>>> Hello,
>>>
>>> Flushed with success with filters I now want to load the mibs so I can
>>> easily view traps for
>>> CISCO-ISDNU-IF-MIB
>>>
>>> I was getting all traps from cisco not being resolved like so:
>>> enterprise: 1.3.6.1.4.1.9.9.26.2 (SNMPv2-SMI::enterprises.9.9.26.2)
>>> So I added the ?mib CISCO-ISDNU-IF-MIB and its pre-reqs and restarted
>>> wireshark.
>>>
>>> And <sigh> no difference.
>>>
>>> At this point where should I look to troubleshoot the problem?
>>>
>>> TIA
>>>
>>> Tony
>>>
>>>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>
