[AGENT++] Trap destinations

[michael.carr at bt.com]

Thanks Frank, you've answered those questions nicely... I've a few more
though...

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.

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?
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?

Thanks,
Mike

-----Original Message-----
From: Frank Fock [mailto:fock at agentpp.com] 
Sent: Thursday, May 10, 2007 10:18 PM
To: Carr,M,Michael,JGFTY C
Cc: agentpp at agentpp.org
Subject: Re: [AGENT++] Trap destinations

Hi Mike,

michael.carr at bt.com wrote:
> All, a few questions on this...
> 
> From what I understand the SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB 
> hold the necessary information for a master agent to send traps to a 
> management application.  The example master agent code contains a cold

> start trap with a local host address, this can be changed but means it

> is hard coded.
>
Yes, the example master agent hard codes an example destination, but
such an approach should not be used for production.

> - What is the normal way to set the destination of such a cold start 
> trap given that the two MIBs I mentioned before contain the 
> destinations for traps and, if I understand it correctly, those MIBs 
> are contained in the master and can't be set by a management 
> application until the master is up and running by which point it 
> should have already attempted to send its cold start trap (but to 
> where?).  It seems a bit like "which came first, the chicken or the 
> egg", have I misunderstood how it should be done?

The first coldStart will probably never be sent. There are generally two
approaches:

(1) Configure the target and notification MIBs and save the agents
configuration persistently. At next cold start the config will be there
when the trap is to be sent.

(2) Read a separate configuration (text) file and initialize the MIBs'
content from there.
> 
> - Along similar lines, if I know some destination addresses for 
> management applications and they could be read by the master from a 
> file and added to the previously mentioned MIBs by it.  Would that be 
> the right way to do it?

I could be. It depends on your requirements (for example this would not
allow to change the destinations at runtime).

Cheers,
Frank

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com