[AGENT++] logical entity support

[Frank Fock]

Hi Chuck,

As long as you do not use the "instance" pointer,
everything will work fine. The instance pointer
is there for easy instance access for those agents
that only have a default context. This pointer is
*not* used by AGENT++ and you can modify the
code generation templates to not create that
"instance" member.

Best regards,
Frank

Chuck Paterson wrote:
> I see all the statics will make anything simple port based in the
> same executable not work.
> 
>    MibTable(oidEntPhySensorEntry, indEntPhySensorEntry, 1)
> {
>         // This table object is a singleton. In order to access it use
>         // the static pointer 
> entity_sensor_mib_entPhySensorEntry::instance.
>         instance = this;
> 
> 
> chuck
> 
>  > 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
>  >  >
>  >
>  > _______________________________________________
>  > AGENTPP mailing list
>  > AGENTPP at agentpp.org
>  > http://lists.agentpp.org/mailman/listinfo/agentpp
> 
> 

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com