[SNMP4J] AgentX with identical subagents

[Mark Gorokhov]

Frank,

Thanks for the solution:
> Then (or if you are looking for an easy migration) each
> sub-agent may use its own context. That context can be
> mapped to a SNMPv3 context and SNMPv1/v2c
> communities on the master agent.

What is your approach to solve a little bit more complex architecture:
 - subagent #1 with APP-1-MIB and generic LOG-MIB
 - subagent #2 with APP-2-MIB and generic LOG-MIB

Ideally both subagents APP-1-MIB and APP-2-MIB should be visible
simultaneously in the MIB browser, e.g. as v2/public. At the same time
they conflicts in LOG-MIB. I see the following solution:
  - subagent #1: 
       APP-1-MIB (community=public)
       LOG-MIB (community=public1)
  - subagent #2: 
       APP-1-MIB (community=public)
       LOG-MIB (community=public2)
Is this approach reasonable? 

Tnanks,
Mark G.

-----Original Message-----
From: Frank Fock [mailto:fock at agentpp.com] 
Sent: Thursday, February 28, 2008 1:38 PM
To: Mark Gorokhov
Cc: snmp4j at agentpp.org
Subject: Re: [SNMP4J] AgentX with identical subagents

Mark,

If MY-APP-MIB has been written for a subagent architecture
then it would contain few (or no) scalars and tables which
include a (sub)system sub-index.

Then each sub-agent can aquire its (sub)system index portion
from the AgentX master agent.

In most cases, the above approach fails, because the MIB
(or MIBs it depends on) do not support such an architecture.

Then (or if you are looking for an easy migration) each
sub-agent may use its own context. That context can be
mapped to a SNMPv3 context and SNMPv1/v2c
communities on the master agent.

Best regards,
Frank

Mark Gorokhov wrote:
> I have Java application with SNMP4J agent which supports MY-APP-MIB.
> This application runs as a server daemon serving some customer. Each
new
> customer requires new JVM process to be started with new copy of the
> application. Each of these copies is connected to MIB Browser using
> different ports. This architecture allows viewing in the MIB Browser
> each application instance status.
>
> Is it possible to convert this architecture to AgentX where
> application's SNMP agent is converted to SNMP AgentX subagent? It's
not
> clear for me how generic AgentX master agent could work with multiple
> customer subagents with identical MY-APP-MIB.
>  
> Thanks,
> Mark G.