> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:net-snmp-
> [EMAIL PROTECTED] On Behalf Of Mike Ayers
> Sent: Monday, July 28, 2008 5:04 PM
> To: Furnish, Trever G; net-snmp-users@lists.sourceforge.net
> Subject: RE: control the order in which mibs are loaded?
>
>
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On
> > Behalf Of Furnish, Trever G
> > Sent: Monday, July 28, 2008 11:24 AM
>
> > Is there any way to control the order in which MIBs are loaded?
>
> None documented.
>
> > Is
> > there a way to see the order?
>
> None t5hat I know of, but if you crank the debugging all the way
> up, you'll probably see it in there somewhere.
>
> > Thoughts?
>
> If you're concerned about matching output, use -On. If you want
> to control MIB loading order for any other reason, then you're
probably
> doing something wrong.
>
>
> HTH,
>
> Mike
That does help, thanks. At least it keeps me from continuing to look
for a switch I'm missing in the manual pages.
All I'm actually trying to do is to have a trap that comes in get turned
into something more human-friendly, but when I try to translate output
using snmptranslate I'm just not getting what I'd hoped for. Any idea
what I'm doing wrong here? Is the MIB to blame, or (more likely) am I?
An example from the snmptranslate man page shows a full description of
system.sysDescr being dumped in response to snmptranslate -Td -OS
system.sysDescr. By contrast, when I try to translate what I'm
interested in:
snmptranslate -IR -Td -OS SNMPv2-SMI::mib-2.33.1.6.2.1.2.48
...I only get this:
SNMPv2-SMI::mib-2.33.1.6.2.1.2.48
mib-2 OBJECT-TYPE
-- FROM SNMPv2-SMI, RFC1213-MIB
::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) 33 1 6 2 1 2 48
}
I *think* this should translate as:
mib-2
.33 --> upsMIB (aka rfc1628)
.1 --> upsObjects
.6 --> upsAlarm
.2 --> upsAlarmTable
.1 --> upsAlarmEntry
.2 --> upsAlarmDescr
.48 --> ...I'm a little fuzzy on how to read this part...
I'd love to get that automatically turned into a description for the
alarm.
It's not just this particular trap that I can't get translated --
doesn't look like anything from mib-2.33 down gets translated. That's
where the rfc1628 mib is rooted (sorry if I'm misusing the term :-( ).
Any advice from anyone? Does anyone have the rfc1628 mib getting
translated fully? Am I just hoping for something that net-snmp doesn't
do?
--
Trever
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
