On 2 November 2011 15:59, Alexandre James <aja...@sandvine.com> wrote:
> Is this arrangement actually compliant? ie Is it perfectly valid for different
> contexts/communities to return different values for the same oids?
It's certainly a valid use of contexts.
Indeed - this is the whole point of having contexts at all.
See RFC 3411, section 3.3.1 for details.
The situation wrt communities is a little less clear-cut,
but I can't spot anything that would forbid such an approach.
The Net-SNMP agent provides a mechanism for mapping
community strings to a non-default context. Particularly
when using proxy mapping to another agent.
> Also, does net-snmp provide this functionality or did you do the
> implementation yourself?
Most of the agent MIB modules are coded to register information
in the default context (only). So you'd need to tweak the code
to provide alternate registrations in a different context.
But you'd need to do this to report different data anyway.
If you're working with AgentX subagents, then these can probably
be tweaked to register and operate with a different context throughout.
But it's not something I've actually done myself (and it's pretty busy at
work, so I don't have much spare time at the moment). You'll probably
need to play about with things a bit to get it working.
Dave
------------------------------------------------------------------------------
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
