On Mon, 18 Jul 2011 08:51:51 +0530 Sudheer IN BLR SISL wrote:
MSIBS>
MSIBS> Is it ok to customize netsnmp library according to my requirements ?
MSIBS>
MSIBS> Any restrictions\complince are applicable to change the source code.
See the licenses in COPYING in the top level directory of the source
PM
To: Mygapula, Sudheer IN BLR SISL
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: SNMPV3 problems.
On 9 June 2011 16:14, Mygapula, Sudheer IN BLR SISL
wrote:
> The issue can not be fixed from devices , so I am looking for work around
> from manager side.
The only workaround that
On 9 June 2011 16:14, Mygapula, Sudheer IN BLR SISL
wrote:
> The issue can not be fixed from devices , so I am looking for work around
> from manager side.
The only workaround that comes to mind would be to craft your management
application in such a way that it invokes a separate sub-process fo
> 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
:43 PM
To: Mygapula, Sudheer IN BLR SISL
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: SNMPV3 problems.
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 configur
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
, Sudheer IN BLR SISL
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: SNMPV3 problems.
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
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
er IN BLR SISL
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: SNMPV3 problems.
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 sh
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
12 matches
Mail list logo
