As I already mentioned: the SNMP4J-Agent code cannot cause this
misbehavior.
You will have to debug your code to find the problem source...
Frank
Am 27.08.2013 06:34, schrieb Hanish Bansal:
Thats the problem i am facing. I debugged the code and everything is
looking fine. I am able to
Any Suggestion ??
On Wed, Aug 14, 2013 at 9:20 AM, Hanish Bansal
hanish.bansal.agar...@gmail.com wrote:
I am using rowid term for row index. I have agent configured for snmp
table with two row indexes 111,222.
I am publishing info using OIDs .1.3.6.1.4.1.1.102.1.1.1.111 to
I believe you will have to provide a code example before anyone can provide
meaningful suggestions.
Hanish Bansal hanish.bansal.agar...@gmail.com wrote:
Any Suggestion ??
On Wed, Aug 14, 2013 at 9:20 AM, Hanish Bansal
hanish.bansal.agar...@gmail.com wrote:
I am using rowid term for row
Hi,
I think the error is located in your code. I cannot see
from the SNMP4J-Agent code in DefaultMOTable
how it would be able to modify cells from other
columns or rows than specified if the specified OID
is a valid instance OID for that table.
Best regards,
Frank
Am 26.08.2013 10:38, schrieb
Hi All,
We are using SNMPv3 for publishing snmp parameters. We are publishing data
as snmp tables.
I am facing an issue in below case:
Multiple rowIDs for same component : When we are publishing parameters of
one component using different rowIds from same jvm process, every-time we
send a
I am using rowid term for row index. I have agent configured for snmp
table with two row indexes 111,222.
I am publishing info using OIDs .1.3.6.1.4.1.1.102.1.1.1.111 to
.1.3.6.1.4.1.1.102.1.1.2.111 where last digit(111) is row index. Then it
sets values for both rowindexes 111 and 222.
On Tue,
