[AGENT++] using MibProxy, ProxyForwarder or AgentX ?

[Jacquemin, Jean-Philippe]

Hi,

 

I have to extend my current Snmp Agent (based on agent++)  to be able to
collect data from a second Snmp Agent located on another board (for
maintenance reasons  it is best to have a separate agent running on that
board) connected via ethernet (with static IP configurations).

 

I would like to keep the current SnmpAgent  as the main entry point for
SNMP requests, so that is it transparent for the user.

Part of the MIB should be treated by the second Snmp Agent, so there are
no conflicts.

 

I am wondering what is the best architectural solution:

-          Simply using the MibProxy class to declare a subtree, whose
OIDs would be forwarded automatically to the second agent  (but I did
not manage to compile the simple proxy example)

-          Using the ProxyForwarder, which is the currently supported
solution in the frameword (I could compile the example, but found very
limited information on how to configure the proxy forwarder)

-          Adding support for AgentX, and managing a master agent and a
slave agent.

 

The drawback of the latter solution is that the slave agent cannot be
addressed as a "normal" snmp agent, if it gets separated from the
master, without having to be reworked.

 

What solution would you advise and where to find more documentation ?

 

Thanks,

 

Best regards,

Jean-Philippe

 

 



DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.