Adam
-Original Message-
From: Bell, Adam [mailto:[email protected]]
Sent: Wednesday, February 25, 2009 12:26 PM
To: Dave Shield
Cc: [email protected]
Subject: RE: Question on SNMP version
Thanks for the pointer,
will try it.
-Original Message-
From: dave
Thanks for the pointer,
will try it.
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf
Of Dave Shield
Sent: Wednesday, February 25, 2009 5:56 AM
To: Bell, Adam
Cc: [email protected]
Subject: Re: Question on SNMP version
2009/2/24 Bell, Adam :
> The table in question is using a Textual Convention definition for an
> octet string that is fixed 18 bytes in length.
> Therefore when encoding the index I expect
>
> table.entry.firstrow.18bytesOfOID
> rather than
> table.entry.18.18bytesOfOID.
That sounds
Hi all,
I have a very specific question about the encoding of a multi-oid table
index.
The table in question is using a Textual Convention definition for an
octet string that is fixed 18 bytes in length.
Therefore when encoding the index I expect
table.entry.firstrow.18bytesOfOID
rath
2009/2/24 Sathyanarayana Murthy, Harish Kolar :
> My question here is this version is of the agent or the SNMP manager who is
> running this code?
Neither.
The version is of the protocol that is used between them.
The agent and the manager must agree how they will communicate.
Either they both u
Hi all,
I understood that the SNMP message format is different from SNMP version 1.0
and version 3.0. And net-snmp supports both.
While creating a SNMP session using
snmp_sess_init( &session );
We mention the SNMP version like
session.peername = strdup("16.138.37.21"); //give the agent IP
ses
