On Thu, Jun 09, 2011 at 05:27:26AM -0700, Wes Hardaker wrote:
> It's time to wrap up the 'pre' series (bug-fixing) for 5.7 and try and
> get it out the door. I'd like to do an rc1 release either today or
> tomorrow if no one has reasons we should wait longer.
Just a quick note that Fedora15 has a
On Thu, 9 Jun 2011 12:04:32 +0530 Sukhdeep wrote:
SS> Also while searching on netsnmp bug-trackers, I found some-one reported
leak in netsnmp:
SS>
SS>
http://sourceforge.net/tracker/index.php?func=detail&aid=3151845&group_id=12694&atid=112694
SS>
SS> Do you think reported issue is somewhat rela
> On Thu, 9 Jun 2011 16:46:05 +0100, Dave Shield
> said:
>> I am looking for work around from manager side.
DS> I'm not sure what to suggest.
Dave's right... It's theoretically possible to mess with the code in
the engineID cache, but that will only help your application. Other
netwo
On 9 June 2011 16:14, Mygapula, Sudheer IN BLR SISL
wrote:
> The devices are not running netsnmp.
>
> The issue can not be fixed from devices
In which case, all I can suggest is that you complain
to the vendor who provided this broken kit.
> I am looking for work around from manager side.
I'm
The devices are not running netsnmp.
The issue can not be fixed from devices , so I am looking for work around from
manager side.
Thanks.
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf
Of Dave Shield
Sent: Thursday, June 09, 2011 8:43
On 9 June 2011 15:50, Mygapula, Sudheer IN BLR SISL
wrote:
> Is there any work around to resolve this issue.
The "workaround" is to find out what is broken in the configuration
and set up of your devices. They should not have been given identical
engine IDs in the first place.
If you can wor
Hello,
Is there any work around to resolve this issue.
Can engine ID can be appended with mac address of device.
Thanks.
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf
Of Dave Shield
Sent: Thursday, June 09, 2011 5:31 PM
To: Mygapula,
It's time to wrap up the 'pre' series (bug-fixing) for 5.7 and try and
get it out the door. I'd like to do an rc1 release either today or
tomorrow if no one has reasons we should wait longer.
--
Wes Hardaker
Please mail all replies to [email protected]
-
On 9 June 2011 11:31, Mygapula, Sudheer IN BLR SISL
wrote:
> for the second device which is having same engID as previous
That's the basic problem.
The second device should *not* have the same engineID.
Each device needs to have a different engineID,
otherwise SNMPv3 doesn't work.
Dave
I don't have code to set the engine ID explicitly, what my observation was
during SNMP V3 communication, the cache maintained with engine ID and engine
boot time etc... for the first device the communication work fine but for the
second device which is having same engID as previous it always re
On 9 June 2011 10:32, Mygapula, Sudheer IN BLR SISL
wrote:
> I have problem with SNMP V3 Communication.
> The devices in network are having same engine ID.
Yes - that would be a problem.
Each device should have a unique engine ID.
> How this problems can be resolved.
How are the engineIDs bein
Hello,
I have problem with SNMP V3 Communication. The devices in network are having
same engine ID.
One device engine time is different from another engine time causing one of the
devices explores and another device never gets explored (USM stats not in time
window).
How this problems can be
Yeah I tried valgrind and Rational Purify Plus. There it didn't report any
leak-trace. But in process manager (our own proprietary tool) and Task-manager,
it shows memory keep on increasing. I'm just doing nothing except, session
initiation and then simple snmp walk in a continuous loop.
Also w
13 matches
Mail list logo
