Well I would like to go into our hardware box environment an execute a few SNMP
commands to test that the master agent and subagent are working before I turn
off all MIB loading in the configure command. I have all the MIB text files
(even the ones which are reportedly not being found) located in the
"/usr/local/share/snmp/mibs" directory on our hardware box. Now, I believe
these MIB text files are just used when I perform a SNMP request in the
hardware box environment so the query results can be dislpayed in text rather
than OID only. I do not think these files are the files which "Can Not be
Found".
Actually, if I issue any SNMP request (snmptranslate, snmpget, etc..) which
should be processed by the master agent (ie: lets forget about the subagent for
now), I receive these errors as well.
Anyway, it would be nice to understand why these errors are being produced?
Where does the master agent try to "find" these MIB files?
Again, all of this code (if compiled for the PC environment) works fine with no
errors at all when the master agent and subagent start up and process queries.
So the only difference is that I am cross-compiling now and copying files to
our hardware box to run the master agent and subagent there. I would assume I
am simply not copying everything I need to copy over to get this working.
I do not want to simply turn off mib loading right now to stop seeing the
errors, but would rather like to understand why they are produced in the first
place.
Also, is there any ideas why my subagent can not find the master agent? Is
there any tests which I can perform to see if the master agent is indeed
listening for subagent register requests or whether the subagent is registering
incorrectly? Must the master agent and subagent use the same port to register
on? Currently I am not setting any ports at all, which I thought means that
the master agent would be listening to all ports for SNMP queries and subagent
registration requests .... is this correct?
Wes Hardaker <[EMAIL PROTECTED]> wrote: >>>>> "NH" == Need Help writes:
NH> Cannot find module (IP-MIB): At line 0 in (none)
These you can ignore. You can also set your MIBS environment variable
to "NONE" before you start, and they should go away. Or there is a
configure flag to turn off mib loading entirely. Generally, running
agents shouldn't need the MIBs.
NH> Warning: Failed to connect to the agentx master agent ([NIL]):
NH> ocStbHostMib_subagent is up and running.
That's a bigger problem. It means the subagent couldn't connect to the
master agent, which is what would really cause you a problem.
--
Wes Hardaker
Sparta, Inc.
---------------------------------
Shape Yahoo! in your own image. Join our Network Research Panel today!-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
