[AGENT++] Trap destinations

[Frank Fock]

Hi Mike,

michael.carr at bt.com wrote:
> 
> If I disabled v3 support (in order to reduce the footprint size - see my
> other thread/email) are SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB still
> used to set the trap destinations?  I was under the impression these
> MIBs were added as part of v3 but going on the example master code
> they're not excluded from a build when v3 is disabled.
>
Both MIB modules can be used for SNMPv1/v2c too and they
provide a standardized way to configure trap targets. That's
why those modules are not excluded when _SNMPv3 is not defined.

> If indeed SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB were introduced by
> v3, what mechanism for trap destinations did v1 & v2 use prior to v3?

Before those MIB modules have been specified, each vendor
used its own proprietary mechanisms.

> This is probably a really basic question but I'm still learning about
> SNMP etc. so you'll have to bare with me :)
> 
> Also, what is the purpose of the call to
> "allow_agentx_tcp_from_localhost();"?  The comment before the call has
> me puzzled since it gets disabled when v3 is disabled - unless the
> comment is referring to the VACM entries?
> 
Mmmh, it seems the enclosing #ifdef is a relict. Some time
ago, the SNMP-COMMUNITY-MIB where only supported when _SNMPv3
was defined. This is no longer the case and thus the #ifdef
can be removed.

Best regards,
Frank