Ahh .... I understand now .....
I was only using the standalone specialized agent which comes with the MfD
stuff for testing purposes only. I always intended to use the main "snmpd"
master agent for my true execution of NetSNMP, so I guess I have no worries
then. Thanks for clarifying this for me.
Dave Shield <[EMAIL PROTECTED]> wrote: On 24/05/07, Need Help wrote:
> I am using "mib2c.mfd.conf" configuration files to generate code. Will I
> be able to incorporate SNMPv3 functionality in the code if I want to?
Yes.
The "mib2c" tool is primarily used to generate the code for a particular
MIB module. This is completely independent of the access control
mechanisms used by the agent.
You should be able to use MIB modules generated by mib2c
(using *any* of the mib2c frameworks), together with *any* version
of SNMP.
> I was told that the VACM might not be incorporated into the MFD
> packages so it might not be able to be used easily.
MIB modules and the overall agent framework are two completely
separate things.
A MIB module (MfD or otherwise) can be compiled into the main
Net-SNMP agent code, with no problems whatsoever.
A MIB module (MfD or otherwise) can be compiled as an AgentX
subagent, and used with the main Net-SNMP master agent, with
no problems whatsoever.
The MfD framework (and this framework *only*) also has the concept
of running the MIB module as a standalone agent, wrapped within a
minimal SNMP agent driver. It is unclear to me how much this
particular mode of operation reflects the "normal" agent behaviour,
and I'd rather not comment on this. I don't always trust myself to give
an objective view of the MfD framework - and it's probably safer to let
Robert offer his thoughts on that.
(He's no more objective than I am, but his bias is rather more positive
than mine!)
> There is a good chance I am going to require SNMPv3 settings in the future
> so I would like to confirm I am not going to run into any problems in the
> future as a result of me using the mibs-for-dummies (MfD) configruation
> files now.
No - you should not have any probloems whatsoever - certainly if you
include your MIB module within the main Net-SNMP agent, or run it
as an AgentX subagent.
I make no guarantees about running this using the MfD-specific
standalone agent approach.
> I guess I am wondering whether I should be using any other
> configuration file type to generate my code (using mib2c) to allow me to use
> SNMPv3 functionality.
>
> Please let me know if using the MfD configuration files are fine or not.
They're fine.
I don't like them, but they're fine.
Dave
---------------------------------
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games. -------------------------------------------------------------------------
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
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
