RE: Problem/Issue importing MIB net-snmp

Dave Shield <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
On Wed, 2006-02-01 at 12:41 -0500, Brazell, Nate (CTR) wrote:
> > 1.  Is net-snmp able to use the FIBRE-CHANNEL-FE-MIB
> >     or the FCMGMT-MIB?
> 
> What do you mean by "use" ?
> **  I guess what I mean is can it query the objects
> in the MIB without writing custom code.

That's still too vague.
The client tools can query the objects in this MIB without
writing custom code.   The agent can *NOT* supply values
from this MIB without custom code.


>     Since this is a popular MIB it seems someone would
> have done the code writing already.

Well if anyone has, they haven't supplied that code to us.



> If you've got an agent that you know implements these
> MIBs, then the Net-SNMP tools should be able to recognise
> the MIB object names, and retrieve the appropriate values
> with no real changes.
> **  Isn't snmpd the agent?

But you didn't say "the Net-SNMP agent".
You said "Net-SNMP" - that includes client-side tools as well.

To repeat - "snmpget", "snmpwalk" and the rest of the client
tool *WILL* understand this MIB without needing further code.

The only application that won't handle this "automatically"
is the agent - snmpd.


>             Could it be as easy as compiling snmpd with
> a --with-module=xxx.

Yes, and no.
Yes - in principle it is as simple as compiling snmpd with
a suitable --with-mib-module=XXX.   But you need to *have*
the necessary code files in order to do this.   That is
*NOT* simple - it requires both a general understanding of
SNMP (various mib2c templates notwithstanding) *and* a
knowledge of how to retrieve the necessary information.

The SNMP agent is not a magic black box - *somebody* must
work out how to retrieve the necessary information, in
order for the agent to report it.


>   How do I know what MIB's snmpd implements?

    $ ls agent/mibgroup/*

or browse the documentation.



> If you want the Net-SNMP agent to *report* these values,
> then this involves a significant amount of work.
> **  Could you explain this a little more?

The agent is basically just an intermediary between a
Network Management application, and the underlying system.
It needs to understand both SNMP (in order to talk to the
management app), and the particular subsytem concerned
(in order to retrieve the necessary values).
   The Net-SNMP toolkit can provide a flexible framework
to handle the SNMP side, reasonably automatically.  It can
*not* take care of the agent<->subsystem interface.  That
may well be completely different for each MIB (and often
for each O/S).   Writing that code is where the skill
really lies.



Dave


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.