Thanks for you patienc Mike,
I see your example
iii. (symbolic absolute)
.iso.org.dod.internet.mgmt.mib-2.system.sysDescr
iv. (symbolic absolute implied)
iso.org.dod.internet.mgmt.mib-2.system.sysDescr
Acually what we have is that we have six nodes where the trap is printed out as
something.org.dod.mgmt.mib-2.system.sysDescr
or
x.3.6.2.1.1.1 (with the .1 missing )
And when snooping between different nodes we also get this in the snoop
Whereas we run identical commands on 18 other servers installed in an identical
way
Wher the trap is printed
something.org.dod.internet.mgmt.mib-2.system.sysDescr
The only difference is that the six servers have an additional application with
it's own traps
In the snoops we see a trap which is numeric.
In the tools on the server there is both numeric and symbolic, but anyway the
internet part IN THE MIDDLE,
is missing so we must imagine then if there is some incoherency between the
additional application and
our basic application.
Anyway I take you hint that we should look for any snmp command with the
switches you have described.
Ragnar
-----Original Message-----
From: Mike Ayers [mailto:[EMAIL PROTECTED]
Sent: mardi 2 décembre 2008 20:53
To: Ragnar Moller
Cc: [email protected]
Subject: RE: MIB Wizardry to Workaround for a trap problem
Please always reply to the list, thanks.
> From: Ragnar Moller [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 02, 2008 9:46 AM
> Thanks for your response to my, perhaps vague response.
>
> I have yet to understand much about SNMP and MIB's it seems.
>
> You are saying "One of the tools may be using the "-Ou" flag."
>
> Are you saying I have to search for a startup script where something
> snmp related is called with the flag -Ou ?
> In /etc/ or elsewhere.
> Would you have an idea of the how such a command would look ?
>
> That's what I understood from your comment.
What I am saying is that there are many different ways to print out
OIDs. Here are a few samples:
i. (numeric absolute) .1.3.6.1.2.1.1.1
ii. (numeric absolute implied) 1.3.6.1.2.1.1.1
iii. (symbolic absolute)
.iso.org.dod.internet.mgmt.mib-2.system.sysDescr
iv. (symbolic absolute implied)
iso.org.dod.internet.mgmt.mib-2.system.sysDescr
v. (simple symbolic) sysDescr
vi. (MIB::symbol) SNMPv2-MIB::sysDescr
vii. (symbolic relative) system.sysDescr
There are other ways as well. The net-snmp command line tools which
print output can be forced to use some of these modes: "-On" for (i), "-Of" for
(iii), "-Os" for (v), "-OS" for (vi), and "-Ou" for (vii). See the "OUTPUT
OPTIONS" section of the snmpcmd man page for details. Of note is (vii), which
can vary greatly, as the choice of where to specify relative to is highly
subjective and varies (not for the "-Ou" flag, which should be consistent for
given OIDs, while not necessarily across OIDs) from tool to tool.
So if one of your tools prints out sysDescr as "system.sysDescr" and
another expects to read it as "internet.mgmt.mib-2.system.sysDescr", nothing
has disappeared - the tools just aren't using the same notation. The easy way
to avoid this problem is to force all your tools (except probably the final
display tools) to use absolute numeric mode for OIDs. One way to force this is
to not tell them where the MIBs are.
Specific corrective strategies are left as an exercise for the student.
HTH,
Mike
-------------------------------------------------------------------------
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
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
