Removing notification destinations

[Peter Loveman]

I could really see the use of having the additional add/remove methods.
Especially in a commercial app where the agent may be just one of many
north-bound interfaces, there may be a need to be able to add/remove
destinations without using SNMP from one of the other interfaces.
-peter

-----Original Message-----
From: Frank Fock [mailto:Frank.Fock____t-online.de]
Sent: Wednesday, May 23, 2001 12:41 AM
To: David S. Brown
Cc: agentpp-dl____agentpp.com
Subject: Re: Removing notification destinations


David,

The add_v1_trap_destination() method is meant as an example only.
You can remove destinations by removing the corresponding rows
of the SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB.
For adding v2 or v3 destinations you should directly add the appropriate
entries in these MIBs.

Regards,
Frank

"David S. Brown" wrote:

> I am using NotificationOriginator::add_v1_trap_destination() to add
entries
> in the target and notification tables.  I do not see a method to later
> remove these entries.  Once a destination is added is it expected to
stay
> for the life of the agent?
>
> Also, if I am implementing a v2 agent, should I even be using
> add_v1_trap_destination(), or should I be adding destination addresses
by
> some other means?
>
> Thank you,
> David Brown
> Anatel Communications

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.agentpp.org/pipermail/agentpp/attachments/20010523/1b779b5f/attachment.htm