[AGENT++] Problem with V3_MP Object

[kulkarni.sudhindra at wipro.com]

Hi,

This is with regard to the EngineID Used by the SNMP v3, there are 3
parts to a V3 Packet wrt to engine ID,

1. Engine ID
2. Engine Boots
3. Engine Time.

Last time we had a problem that whenever the agent restarts, the engine
ID is reset and hence all the managers fail to work until the managers
are restarted.

To fix this problem, now we ensure that the Engine ID is a constant. We
have a new problem with this implementation

Given an "Engine ID", the manager maintains  Engine Time and Engine
Boots. The Engine Time and Engine Boots will be obtained from the agent
only if the Engine ID is available with the manager.

With the above assumption, whenever a agent restarts it will reset the
Engine Time. This does not reflect to the manager hence all the queries
fail.

Any solution to this problem will be of great help.

Thanks and Regards,
Sudhindra V Kulkarni
--------------------------------



-----Original Message-----
From: agentpp-bounces at agentpp.org [mailto:agentpp-bounces at agentpp.org]
On Behalf Of kulkarni.sudhindra at wipro.com
Sent: Thursday, August 04, 2005 1:39 PM
To: fock at agentpp.com; agentpp at agentpp.org
Subject: RE: [AGENT++] Problem with V3_MP Object



Hi Fock,

Thanks a lot for your inputs. I have one query regarding the approach
(1) mentioned by you.


Having a constant Engine ID for an Agent will there be no compromise on
the security aspect of the agent.


Also is there any way to flush the Engineer Table. There is a function
in the V3_MP Class delete cache but this function is protected.


Regards,
Sudhindra V Kulkarni
--------------------




-----Original Message-----
From: fock at agentpp.com [mailto:fock at agentpp.com]

Sent: Thursday, August 04, 2005 1:48 AM
To: agentpp at agentpp.org; Sudhindra V Kulkarni (WT01 - Embedded Systems)
Subject: AW: [AGENT++] Problem with V3_MP Object


Hi,
There are at least two approaches for your problem:
1. Do not change the context engine ID on the agent side
(it is not a good idea to change the engine ID or context engine ID on
changes or reboots of an agent because this breaks SNMPv3 mechanism) 2.
If a request times out, then reset contextEngineID and engineID and
rediscover it and then retry.

Best regards,
Frank

>
>
>Hi,
>
>We have a Multi-Threaded Application which uses the SNMP++ V3.2. We are

>facing a strange problem,
>
>If we create the v3_MP Object everytime for a V3 Query, this will slow

>down our queries and also is causing crashes since multiple threads are

>using the same object.
>
>To overcome this problem, we have made V3_MP Object as static and we

>are into a altogether new problem. First time every thing works fine

>and there is no problem until there is a change on the agent, If the

>agent switches from V3 to V1 and then back to V3, then a new Context

>Engine ID is generated. Since V3_MP is static we already have a V3_MP

>object and also have a ContextEngineID so we not query to get the

>context Engine ID. this causes our queries to fail when ever there is a

>change in the agent.
>
>
>Please advice on the best approach to resolve this problem. Thanks in

>advance.
>
>Regards,
>Sudhindra V Kulkarni
>--------------------------------
>
>
>
>
>
>
>Confidentiality Notice
>
>The information contained in this electronic message and any

>attachments to
>this message are intended
>for the exclusive use of the addressee(s) and may contain confidential
or

>privileged information. If
>you are not the intended recipient, please notify the sender at Wipro
or

>Mailadmin at wipro.com immediately
>and destroy all copies of this message and any attachments.
>_______________________________________________
>AGENTPP mailing list
>AGENTPP at agentpp.org
><a

>href="http://lists.agentpp.org/mailman/listinfo/agentpp">http://lists.a
gentpp.o
>rg/mailman/listinfo/agentpp</a>



Confidentiality Notice


The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain confidential or privileged information. If you are not
the intended recipient, please notify the sender at Wipro or
Mailadmin at wipro.com immediately and destroy all copies of this message
and any attachments. _______________________________________________
AGENTPP mailing list
AGENTPP at agentpp.org http://lists.agentpp.org/mailman/listinfo/agentpp



Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.