From agentx-bounces@ietf.org Mon Aug 08 01:21:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E204Z-0006jN-Dz; Mon, 08 Aug 2005 01:21:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E204T-0006iN-1S
	for agentx@megatron.ietf.org; Mon, 08 Aug 2005 01:21:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16876
	for <agentx@ietf.org>; Mon, 8 Aug 2005 01:21:08 -0400 (EDT)
Received: from web30408.mail.mud.yahoo.com ([68.142.200.111])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E20c5-0003l8-Tj
	for agentx@ietf.org; Mon, 08 Aug 2005 01:55:55 -0400
Received: (qmail 10644 invoked by uid 60001); 8 Aug 2005 05:20:56 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=diWk8rMpai/bQxH8VGw+gLWQGrqkANNyAQvU8YJNk9m3pmM/qw8tSwYSoo+HC62sWBQVBc93MuU/2k0lxIw1ds4rNUhV6AKWh8taKmOnm4CIYTFlbS0MJwR9ENEzKCyYU9pyg/nsUYv6ptO1a5MjHFyXG0clj65vRAwnVqfKoaM=
	; 
Message-ID: <20050808052056.10642.qmail@web30408.mail.mud.yahoo.com>
Received: from [24.6.168.212] by web30408.mail.mud.yahoo.com via HTTP;
	Sun, 07 Aug 2005 22:20:56 PDT
Date: Sun, 7 Aug 2005 22:20:56 -0700 (PDT)
From: MEENA SELVAM <meena_selvam@yahoo.com>
To: agentx@ietf.org, MEENA SELVAM <meena_selvam@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 8bit
Cc: 
Subject: [Agentx] how to load a MIB in ireasoning browser as a non leaf node
X-BeenThere: agentx@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SNMP Agent Extensibility <agentx.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/agentx>
List-Post: <mailto:agentx@ietf.org>
List-Help: <mailto:agentx-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=subscribe>
Sender: agentx-bounces@ietf.org
Errors-To: agentx-bounces@ietf.org

Hi,
I was using ireasoning web browser, and initially it
correctly loaded as a non leaf node. But after I made
some changes to MIB, compiled and restarted the
target,
the mib browser loads it as a leaf of the RFC node.

How can I fix this problem? My target is a linux
machine
meena

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




From agentx-bounces@ietf.org Tue Aug 16 19:24:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E5Ani-0000HV-8x; Tue, 16 Aug 2005 19:24:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E5Ang-0000HN-QR
	for agentx@megatron.ietf.org; Tue, 16 Aug 2005 19:24:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20198
	for <agentx@ietf.org>; Tue, 16 Aug 2005 19:24:49 -0400 (EDT)
Received: from web30412.mail.mud.yahoo.com ([68.142.201.235])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E5BN1-00024f-Mr
	for agentx@ietf.org; Tue, 16 Aug 2005 20:01:30 -0400
Received: (qmail 13438 invoked by uid 60001); 16 Aug 2005 23:24:39 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=BFmyty21QyGdImvC/yJNwq2x8fk3Bp1gVtbif9xaVeo/p2Lo3JmAHU07vwAcuwaH+72I+go/teqaLj/Qxz0lkYpNXTgst1IOhuUkxwhCD7TAr+2aY4oHQkiJJArkJnPhs2vzd9rk73wL8UyIFc2tkpMG1WDtmK5MZ54Ppax1MZ8=
	; 
Message-ID: <20050816232439.13436.qmail@web30412.mail.mud.yahoo.com>
Received: from [47.230.0.41] by web30412.mail.mud.yahoo.com via HTTP;
	Tue, 16 Aug 2005 16:24:39 PDT
Date: Tue, 16 Aug 2005 16:24:39 -0700 (PDT)
From: MEENA SELVAM <meena_selvam@yahoo.com>
To: agentx@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: 8bit
Subject: [Agentx] getnext of empty table accesses the key of next table;
	any suggestions
X-BeenThere: agentx@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SNMP Agent Extensibility <agentx.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/agentx>
List-Post: <mailto:agentx@ietf.org>
List-Help: <mailto:agentx-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=subscribe>
Sender: agentx-bounces@ietf.org
Errors-To: agentx-bounces@ietf.org

Hi,

I have few tables in snmp module, and when I issue a
get_next using a mib browser for an empty table, since
endOfTable is returned, it continues to look for the
next available instance of the next variable/table.

This is  according to (conforming to ) the
documentation given below from
www.erlang.se/doc/doc-5.0.1/lib/snmp-3.2.1/doc/
under instrumentation functions section.

=====================================================
3.1.6 GetNext Operation 

The GetNext Operation operation should only be defined
for tables since the agent can find the next instance
of plain variables in the MIB and call the
instrumentation with the get operation. 

table_access(get_next, RowIndex, Cols [, ExtraArg1,
...])

 

Cols is a list of integers, all greater than or equal
to zero. This indicates that the instrumentation
should find the next accessible instance. This
function returns the tuple {NextOid, NextValue}, or
endOfTable. NextOid should be the lexicographically
next accessible instance of a managed object in the
table. It should be a list of integers, where the
first integer is the column, and the rest of the list
is the indices for the next row. If endOfTable is
returned, the agent continues to search for the next
instance among the other variables and tables. 

RowIndex may be an empty list, an incompletely
specified row index, or the index for an unspecified
row.
======================================================

But, in finding the next instance the program tries to
access the key ie Colno corresponding to key is part
of this search.

In my case, the get_next of the switch table works
fine
normally but in the normal case, the keys are
inaccessible, and hence getnext (even as part of walk)
specifies columns 3-7 and never 1 and 2

The error I get is:

[Note this is in erlang language]

** User error: Invalid return value {'EXIT',{{badma
tch,{aborted,{function_clause,[{oam_snmp_snas,get_switch_table,[1,{'1','1'}]},{o
am_snmp_table,nselect_cols,6},{reg,'-transaction/3-fun-0-',3},{reg,'-transaction
/3-fun-1-',1},{mnesia_tm,apply_fun,3},{mnesia_tm,execute_transaction,5},{oam_snm
p_snas,snasSwitchDetailTable,3},{snmpa_agent,get_next_values_all_rows,6}]}}},[{o
am_snmp_snas,snasSwitchDetailTable,3},{snmpa_agent,get_next_values_all_rows,6},{
snmpa_agent,get_next_table,4},{snmpa_agent,next_loop_varbinds,5},{snmpa_agent,pr
ocess_pdu,4},{snmpa_agent,handle_pdu,7},{snmpa_agent,handle_info,2},{gen_server,
handle_msg,6}]}} from
{oam_snmp_snas,snasSwitchDetailTable,[]} (get_next)

my get_switch_table is the access function which is
defined below: The first parameter is col no.

get_switch_table(?snasSwitchIp, {XId, SId}) ->
       
        {value, SwitchIp} =
reg:value_t(?SwitchIp(XId,SId)),
      
      tuple_to_list(SwitchIp);

the problem is due to the col value 1 (first parameter
of the following function call). This is confirmed
because, just typing at erlang shell as follows:

oam_snmp_snas:get_switch_table(1,{'1','1'}).

gives the following error,

=ERROR REPORT==== 16-Aug-2005::10:25:42 ===
                                           Error in
process <0.1043.0> on node '
isd@a47-80-18-92' with exit value:
{function_clause,[{oam_snmp_snas,get_switch_t
able,[1,{'1','1'}]},{erl_eval,do_apply,5},{shell,exprs,6},{shell,eval_loop,3}]}

                                                      
                        *
* exited:
{function_clause,[{oam_snmp_snas,get_switch_table,[1,{'1','1'}]},
                             {erl_eval,do_apply,5},
                             {shell,exprs,6},
                             {shell,eval_loop,3}]} **

whereas oam_snmp_snas:get_switch_table(3,{'1','1'}).
does not give error(produces proper output)


My doubt is: why does the next searched instance is
the key(col 1), instead of column 3.

Also is it possible to suppress searching beyond for
next available instance if endOfTable is encountered.


meena


		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 




From agentx-bounces@ietf.org Tue Aug 16 19:57:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E5BJJ-0007xV-Og; Tue, 16 Aug 2005 19:57:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E5BJI-0007xQ-Jr
	for agentx@megatron.ietf.org; Tue, 16 Aug 2005 19:57:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25169
	for <agentx@ietf.org>; Tue, 16 Aug 2005 19:57:34 -0400 (EDT)
Received: from pop-altamira.atl.sa.earthlink.net ([207.69.195.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E5Bsh-0003JE-QM
	for agentx@ietf.org; Tue, 16 Aug 2005 20:34:13 -0400
Received: from h-68-165-6-190.snvacaid.dynamic.covad.net ([68.165.6.190]
	helo=oemcomputer)
	by pop-altamira.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1E5BJF-0001H7-00
	for agentx@ietf.org; Tue, 16 Aug 2005 19:57:33 -0400
Message-ID: <037d01c5a2be$75b96f20$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <agentx@ietf.org>
References: <20050816232439.13436.qmail@web30412.mail.mud.yahoo.com>
Subject: Re: [Agentx] getnext of empty table accesses the key of next table;
	any suggestions
Date: Tue, 16 Aug 2005 16:58:54 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-BeenThere: agentx@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SNMP Agent Extensibility <agentx.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/agentx>
List-Post: <mailto:agentx@ietf.org>
List-Help: <mailto:agentx-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/agentx>,
	<mailto:agentx-request@ietf.org?subject=subscribe>
Sender: agentx-bounces@ietf.org
Errors-To: agentx-bounces@ietf.org

Hi -

> From: "MEENA SELVAM" <meena_selvam@yahoo.com>
> To: <agentx@ietf.org>
> Sent: Tuesday, August 16, 2005 4:24 PM
> Subject: [Agentx] getnext of empty table accesses the key of next table;any suggestions
>
> Hi,
>
> I have few tables in snmp module, and when I issue a
> get_next using a mib browser for an empty table, since
> endOfTable is returned, it continues to look for the
> next available instance of the next variable/table.

This is what it should happen at the agentx protocol level.

> This is  according to (conforming to ) the
> documentation given below from
> www.erlang.se/doc/doc-5.0.1/lib/snmp-3.2.1/doc/
> under instrumentation functions section.

We really shouldn't be discussing specific products here.

...
> My doubt is: why does the next searched instance is
> the key(col 1), instead of column 3.

This question is highly specific to that particular API,
so I'd be surprised if you got an answer here.

> Also is it possible to suppress searching beyond for
> next available instance if endOfTable is encountered.
...

That, too, is API specific, but it seems that if you wanted agentx
protocol to function correctly, it should indeed look for the next
available instance.  (Think about table rows with holes in them
to understand why.)

Randy







