On 15 April 2011 05:38, Priya Raghavendra <[email protected]> wrote: > So now my next issue is that both the applications have subagents, scalar and > tabular running.
Do these subagents implement the same set of MIB objects? If the two subagents provide different information (with no overlap), then you don't actually need two SNMP agents. The two subagents could both connect to the same main SNMP agent > So how do I configure the subagents so that the subagents on application A > talk to the first instance of snmpd and the subagents on application B talk > to the second instance of snmpd running on port 171. If the two subagents provide the same set of OIDs, then the simplest approach is indeed to run two master SNMP agents. You will need two configuration files - one for each master agent. These should each specify an AgentX socket to listen on using the directive 'AgentXSocket' with a different port number You can then use these port numbers when configuring the two subagents. Dave ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
