[AGENT++] logical entity support

[Chuck Paterson]

Frank,

Unless I'm missing something, which is highly likley, that seems really
painful. Things like MibStaticTable won't really be useful unless I
create derived types. Seems much easier to do the redirect on port and
have N totally separate agents running, or to do some hack to dispatch
on the context.

The good news is I'm interested in this just to make sure
I understand. If I have to do this I can do the port thing.

Thanks for you help
Chuck

Frank Fock wrote:
 > Hi Chuck,
 >
 > Yes, the AgenPro generated code can be added to
 > a Mib instance for several contexts. Your
 > instrumentation code, however, needs to know in
 > which context it operates.
 >
 > Community names can be used for this too.
 > Just map a community to a SNMPv3 context via
 > the SNMP-COMMUNITY-MIB and use the contexts
 > internally.
 >
 > Best regards,
 > Frank
 >
 > Chuck Paterson wrote:
 >> Is there a way using code generated via agenpro
 >> to have in AGENT++ multiple logical agents based on
 >> Context Engine ID that have different names spaces. I
 >> can see how this could be done, at least I think I do,
 >> at different ports. In my case I probably need to have
 >> it based on  the communicty string since my clients look
 >> to not be v3.
 >>
 >> This is with regard to entLogicalTable in entityMib.
 >>
 >> 1.3.6.1.2.1.47.1.2.1.1
 >>
 >>
 >> Thanks
 >> Chuck
 >>
 >> _______________________________________________
 >> AGENTPP mailing list
 >> AGENTPP at agentpp.org
 >> http://lists.agentpp.org/mailman/listinfo/agentpp
 >