Hi
As per SMIv2 definition of the MIB , the INDEX of the table must be
'not-accessible'
unless there are no other objects than the Auxiliary object itself in the
table.
You do see, read-only objects as INDEX because original definition was in SMI
v1
and now that is converted to
On 14/12/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I have a doubt regarding table index. In MIB table sometimes the index
is not-accessible and some time the index is read-only.
My doubt is how to decide whether the table index will be read-only or
not-accessible.
As long as there is at
-Original Message-
From: Kurapati M-G19456 [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:06 AM
To: Somenath Pal (WT01 - Broadband Networks);
net-snmp-users@lists.sourceforge.net
Subject: RE: MAX-ACCESS of table index
As per SMI-v2 a MAX-ACCESS for index objects
PROTECTED]
Sent: Thursday, December 14, 2006 11:40 AM
To: Kurapati M-G19456; net-snmp-users@lists.sourceforge.net
Subject: RE: MAX-ACCESS of table index
Hi Mahesh,
Many thanks for your answer.
But what if the table has one read-create or read-write columnar
objects?
For example in case of ifTable
first of all, what Mahesh wrote is not quite clear,in my view.
Not-accessible: it means you all people cannot retrieve it's value,either
using snmpget or snmpset or anyway else.
Accessible-for-notify: it means you can access it's value only by inform
strickly.no other way you can do that .
: Thursday, December 14, 2006 11:46 AM
To: [EMAIL PROTECTED]
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: MAX-ACCESS of table index
first of all, what Mahesh wrote is not quite clear,in my view.
Not-accessible: it means you all people cannot retrieve it's
value,either using snmpget
are idices.
Not for the other columnar objects.
--
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *jiang jilin
*Sent:* Thursday, December 14, 2006 11:46 AM
*To:* [EMAIL PROTECTED]
*Cc:* net-snmp-users@lists.sourceforge.net
*Subject:* Re: MAX-ACCESS of table
