I'm working on a high speed networking project where we have a lot of computers running an application that we'd like to be able to re-configure and also monitor their performance.
The question is, does it make sense for the application to act as a manager to get and set the MIB variables while at the same time have another external manager acting as the "real" manager. So, basically any status we'd want to report would get set by the application and the external SNMP manager would get them when it wanted them. Values set by the external manager could be read using some embedded SNMP get function in the application upon initialization or, if there are MIB variables set by the external manager that would require immediate action by the application, the agent would have routines registered with it that would send simple UDP messages to the application notifying it that it needed to act upon new information. Is this a sensible approach? I think it's pretty simple and workable but I caught a bit of flack from someone who thought I was proposing something not very standard. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
