From owner-agentx@dorothy.bmc.com Fri Dec 1 12:29:44 2000 Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26295 for ; Fri, 1 Dec 2000 12:29:39 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id eB1HPEQ07836; Fri, 1 Dec 2000 11:25:18 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA19021 for agentx-list; Fri, 1 Dec 2000 09:14:26 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA19015; Fri, 1 Dec 2000 09:14:22 -0800 (PST) Date: Fri, 1 Dec 2000 09:14:22 -0800 (PST) From: Randy Presuhn Message-Id: <200012011714.JAA19015@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Fwd: CMU Library documents Cc: smysore@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id eB1HPEQ07836 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA26295 Hi - I'm forwarding a non-subscriber post to the agentx working group mailing list. Subscription instructions are at http://www.ietf.org/html.charters/agentx-charter.html ------------------------------------------------------- Randy Presuhn randy_presuhn@bmc.com Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 Fax: +1 408 965-0359 2141 North First Street http://www.bmc.com/ San José, California 95131 USA ------------------------------------------------------- My opinions and BMC's are independent variables. ------------------------------------------------------- > Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) > by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA18023 > for ; Fri, 1 Dec 2000 01:18:11 -0800 (PST) > Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) > by tattler.bmc.com (8.10.2/8.10.2) with SMTP id eB19HMh21767 > for ; Fri, 1 Dec 2000 03:17:22 -0600 (CST) > Received: from cisco.com ([192.135.239.144]) > by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id OAA17882 > for ; Fri, 1 Dec 2000 14:49:00 +0530 (IST) > Message-ID: <3A276D78.A88DB0AD@cisco.com> > Date: Fri, 01 Dec 2000 14:50:56 +0530 > From: Suprabha Mysore > Reply-To: smysore@cisco.com > Organization: Cisco Systems > X-Mailer: Mozilla 4.5 [en] (WinNT; I) > X-Accept-Language: en > MIME-Version: 1.0 > To: agentx@dorothy.bmc.com > Subject: CMU Library documents > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > Hi, > > I am using the CMU library for SNMP agent > development. > > I do not sufficient documents that help me in the > development process. > > Could somebody please suggest where I can get the > appropriate documents. > > Thanks > Suprabha > From owner-agentx@dorothy.bmc.com Mon Dec 4 04:29:47 2000 Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA02409 for ; Mon, 4 Dec 2000 04:29:47 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id eB49Ql913105; Mon, 4 Dec 2000 03:26:47 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id BAA29538 for agentx-list; Mon, 4 Dec 2000 01:22:46 -0800 (PST) Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA29533 for ; Mon, 4 Dec 2000 01:22:41 -0800 (PST) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id eB49Lpt12364 for ; Mon, 4 Dec 2000 03:21:51 -0600 (CST) Received: (from fwmaster@localhost) by ns.hitt.nl (8.9.1a/8.6.12) id KAA14552 for ; Mon, 4 Dec 2000 10:23:33 +0100 (MET) Received: by ns.hitt.nl via smap (V1.3) id sma014390; Mon, 4 Dec 00 10:22:21 +0100 Received: by CHOPIN with Internet Mail Service (5.5.2448.0) id ; Mon, 4 Dec 2000 10:22:21 +0100 Message-ID: <11655D647028D311A3A20008C7BB878A1EAD87@CHOPIN> From: "Holstein, Bert" To: "'agentx@dorothy.bmc.com'" Subject: RE: CMU Library documents Date: Mon, 4 Dec 2000 10:22:20 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id BAA29534 Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id eB49Ql913105 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA02409 Hi, I presume that you're talking about the cmu agentx-library. Or do you refer to cmu's snmp library which is used by the snmpd. Both come with some doc. when downloading the packages. The snmp library with (mostly) man3 man-pages. The agentx- library with html-pages about use of both snmpd and agentx- library API. (After unzipping/untarring, have a look in directory .../doc). If that's still insufficient, then you'd better ask some specific question you're struggling with (either via this mailing-list or directory - we've done quite some programming with the CMU agentx-library in order to create subagents). Hope this helps, Kind regards, Bert Holstein HITT Holland Institute of Traffic Technology holstein@hitt.nl > -----Original Message----- > From: Randy Presuhn [SMTP:rpresuhn@dorothy.bmc.com] > Sent: Friday, December 01, 2000 6:14 PM > To: agentx@dorothy.bmc.com > Cc: smysore@cisco.com > Subject: Fwd: CMU Library documents > > > Hi - > > I'm forwarding a non-subscriber post to the agentx working > group mailing list. Subscription instructions are at > http://www.ietf.org/html.charters/agentx-charter.html > > ------------------------------------------------------- > Randy Presuhn randy_presuhn@bmc.com > Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 > Fax: +1 408 965-0359 2141 North First Street > http://www.bmc.com/ San José, California 95131 USA > ------------------------------------------------------- > My opinions and BMC's are independent variables. > ------------------------------------------------------- > > > Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) > > by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA18023 > > for ; Fri, 1 Dec 2000 01:18:11 -0800 (PST) > > Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) > > by tattler.bmc.com (8.10.2/8.10.2) with SMTP id eB19HMh21767 > > for ; Fri, 1 Dec 2000 03:17:22 -0600 (CST) > > Received: from cisco.com ([192.135.239.144]) > > by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP > id OAA17882 > > for ; Fri, 1 Dec 2000 14:49:00 +0530 (IST) > > Message-ID: <3A276D78.A88DB0AD@cisco.com> > > Date: Fri, 01 Dec 2000 14:50:56 +0530 > > From: Suprabha Mysore > > Reply-To: smysore@cisco.com > > Organization: Cisco Systems > > X-Mailer: Mozilla 4.5 [en] (WinNT; I) > > X-Accept-Language: en > > MIME-Version: 1.0 > > To: agentx@dorothy.bmc.com > > Subject: CMU Library documents > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > > > Hi, > > > > I am using the CMU library for SNMP agent > > development. > > > > I do not sufficient documents that help me in the > > development process. > > > > Could somebody please suggest where I can get the > > appropriate documents. > > > > Thanks > > Suprabha > > From owner-agentx@dorothy.bmc.com Thu Dec 28 19:05:02 2000 Received: from tattler.bmc.com ([198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA20815 for ; Thu, 28 Dec 2000 19:05:02 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id eBT00nn29726; Thu, 28 Dec 2000 18:00:49 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA07313 for agentx-list; Thu, 28 Dec 2000 15:58:55 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA07307 for agentx@dorothy.bmc.com; Thu, 28 Dec 2000 15:58:51 -0800 (PST) Date: Thu, 28 Dec 2000 15:58:51 -0800 (PST) From: Randy Presuhn Message-Id: <200012282358.PAA07307@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Re: How to detect when to report noSuchInstance error? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id eBT00nn29726 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA20815 Hi - Catching up on OLD email.... > Message-ID: <39B4232A.8080F7D6@fock.de> > Date: Tue, 05 Sep 2000 00:33:14 +0200 > From: Frank.Fock@t-online.de (Frank Fock) > To: "agentx@dorothy.bmc.com" > Subject: How to detect when to report noSuchInstance error? ... > When a subagent registers a row of a table (let's say ifEntry.1-22.1) > at the master and a SNMP request for an instance of a non registered > row (e.g., ifIndex.2) comes in, how does the master agent finds out > whether it should return noSuchInstance (which would be correct) or > noSuchObject (which would be wrong)? > > Since the master cannot know through the AgentX protocol, > that ifIndex is a multi-instance object, and since it cannot ask > any subagent about ifIndex.2 (because no subagent has registered > for that region) the master agent will have to return a noSuchObject > error. > > Has anyone solved this dilemma? ... I think noSuchObject is a reasonable answer. One could also argue for noSuchName, since subagent technologies are, at least in a historical sense, a kind of proxy (though 2573 takes pains to say that they are not). I think the noSuchName/noSuchObject/noSuchInstance distinction introduced with SNMPv2 has not proven to be useful, but eliminating it would be too painful to even contemplate. Do any management applications vary their behaviour based on which of these three error-status values shows up in a response? I suspect that most will handle them in the same way, making the question largely academic. Looking more closely at RFC 1905 (and the update's) clause 4.2.1, and then at how RFC 2573 describes when the access decision is made, it looks like the whole noSuchObject/noSuchInstance dichotomy is at not accounted for in the processing steps described in RFC 2573. Certainly RFC 2575 doesn't distinguish these two cases. Perhaps this thread should move to the snmpv3 WG list? Or maybe this is a can of worms that would be best left buried. :-) ------------------------------------------------------- Randy Presuhn randy_presuhn@bmc.com Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 Fax: +1 408 965-0359 2141 North First Street http://www.bmc.com/ San José, California 95131 USA ------------------------------------------------------- My opinions and BMC's are independent variables. ------------------------------------------------------- From owner-agentx@dorothy.bmc.com Fri Dec 29 13:13:11 2000 Received: from tattler.bmc.com ([198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11157 for ; Fri, 29 Dec 2000 13:13:11 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id eBTI9Yb25431; Fri, 29 Dec 2000 12:09:34 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09432 for agentx-list; Fri, 29 Dec 2000 10:07:49 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09426 for agentx@dorothy.bmc.com; Fri, 29 Dec 2000 10:07:46 -0800 (PST) Date: Fri, 29 Dec 2000 10:07:46 -0800 (PST) From: Randy Presuhn Message-Id: <200012291807.KAA09426@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Re: How to detect when to report noSuchInstance error? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id eBTI9Yb25431 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA11157 Hi - This morning, it occurred to me that there IS a way to get the noSuchInstance to happen in a pure AgentX environment. Just have a "fallback" subagent claim the table's entire subtree, and always respond to get requests with noSuchInstance. The only get requests dispatched to this subagent would be the ones for which no other subagent has registered the row in question. Viva le (la?) kludge! ------------------------------------------------------- Randy Presuhn randy_presuhn@bmc.com Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 Fax: +1 408 965-0359 2141 North First Street http://www.bmc.com/ San José, California 95131 USA ------------------------------------------------------- My opinions and BMC's are independent variables. ------------------------------------------------------- From owner-agentx@dorothy.bmc.com Fri Dec 29 13:13:38 2000 Received: from tattler.bmc.com ([198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11191 for ; Fri, 29 Dec 2000 13:13:33 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id eBTI9Wm25417; Fri, 29 Dec 2000 12:09:32 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09453 for agentx-list; Fri, 29 Dec 2000 10:09:49 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09447 for agentx@dorothy.bmc.com; Fri, 29 Dec 2000 10:09:45 -0800 (PST) Date: Fri, 29 Dec 2000 10:09:45 -0800 (PST) From: Randy Presuhn Message-Id: <200012291809.KAA09447@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Fwd: Re: How to detect when to report noSuchInstance error? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id eBTI9Wm25417 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA11191 Hi - I'm forwarding a post from Bob Natale from yet another address, which I have dutifully added to the agentx "posters" list. > Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) > by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id SAA08149; > Thu, 28 Dec 2000 18:35:07 -0800 (PST) > From: Bob.Natale@AppliedSNMP.com > Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) > by tattler.bmc.com (8.10.2/8.10.2) with SMTP id eBT2Y2c27288; > Thu, 28 Dec 2000 20:34:02 -0600 (CST) > Received: from bnatale.acecomm.com (dhcppm15.acec.com [38.249.211.237]) > by relay1.acec.com (8.9.3/8.9.3) with ESMTP id VAA16556; > Thu, 28 Dec 2000 21:36:02 -0500 (EST) > Message-Id: <5.0.1.4.2.20001228214140.00af5750@plymouth.acec.com> > X-Sender: bnatale@plymouth.acec.com > X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 > Date: Thu, 28 Dec 2000 21:42:53 -0500 > To: Randy Presuhn > Subject: Re: How to detect when to report noSuchInstance error? > Cc: agentx@dorothy.bmc.com > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > > At 12/28/2000:06:58 PM, Randy Presuhn wrote: > > Hi Randy, > > <...> > I think the noSuchName/noSuchObject/noSuchInstance distinction > introduced with SNMPv2 has not proven to be useful, but > eliminating it would be too painful to even contemplate. > > I agree. > > Do any management applications vary their behaviour based > on which of these three error-status values shows up in > a response? I suspect that most will handle them in the > same way, making the question largely academic. > > At least for the management apps I am familiar with, the > behavior is not materially different for any of these > error-status values relative to any of the other two. > (They leave it to the user to somehow correct the object > name in the varbind, usually via a moderately friendly > GUI front-end, with access to the relevant MIB object > definitions as an aid in most cases.) > > <...> > Perhaps this thread should move to the snmpv3 WG list? > > If it needs to be continued, but... > > Or maybe this is a can of worms that would be best > left buried. :-) > > I hope that conclusion is the consensus of the group! > > Cordially, > > BobN > > ------------------------------------------------------- Randy Presuhn randy_presuhn@bmc.com Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 Fax: +1 408 965-0359 2141 North First Street http://www.bmc.com/ San José, California 95131 USA ------------------------------------------------------- My opinions and BMC's are independent variables. ------------------------------------------------------- From owner-agentx@dorothy.bmc.com Fri Dec 29 13:35:03 2000 Received: from tattler.bmc.com ([198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11400 for ; Fri, 29 Dec 2000 13:35:02 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id eBTIVAr00100; Fri, 29 Dec 2000 12:31:10 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09614 for agentx-list; Fri, 29 Dec 2000 10:31:08 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09608 for agentx@dorothy.bmc.com; Fri, 29 Dec 2000 10:31:05 -0800 (PST) Date: Fri, 29 Dec 2000 10:31:05 -0800 (PST) From: Randy Presuhn Message-Id: <200012291831.KAA09608@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: isAccessAllowed in agentx? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list X-MIME-Autoconverted: from 8bit to quoted-printable by tattler.bmc.com id eBTIVAr00100 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA11400 Hi - In an offline discussion, I wrote: > It annoys me that the disman MIBs require mechanisms > not provided by agentx to do their job securely. > I'd be interested in a "companion" protocol providing > access to the "isAccessAllowed" abstract service. > This protocol would only have connection setup, > teardown, and isAccessAllowed query/response. Bert Wijnen replied: | Mmmm... we wanted to keep access control and such in the | master agent. So.... ??? | We do not pass any security related info (like securityName, | securityLevel, securityModel etc) to the subagent, so subagent | cannot pass it back. So the check should be made based on | an active session, transaction or packet ID or a combination | of those??? Indeed, this was deliberate, and I still think it was the right thing to do. Then along came objects like RFC 2574's authOwnKeyChange and privOwnKeyChange. These were tolerable, since they were still squarely inside the master agent. My thinking with the disman mibs was that credentials for use by scripts or expressions would be writeable attributes of those objects, allowing a manager to delegate authority to a trusted entity which would work on its behalf. This would not require any access decision functions to be invoked within the disman MIB implementation. However, what we ended up with was much more like the RMON approach, with the credentials passed "under the table", and a need for the disman MIB implementations to be able to invoke the isAccessAllowed() abstract service interface. It would be really nice to be able to do this in an interoperable way. ------------------------------------------------------- Randy Presuhn randy_presuhn@bmc.com Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 Fax: +1 408 965-0359 2141 North First Street http://www.bmc.com/ San José, California 95131 USA ------------------------------------------------------- My opinions and BMC's are independent variables. -------------------------------------------------------