From owner-agentx@dorothy.peer.com Mon Aug 7 14:35:30 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11108 for ; Mon, 7 Aug 2000 14:35:30 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e77IU5623933; Mon, 7 Aug 2000 13:30:05 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA22251 for agentx-list; Mon, 7 Aug 2000 11:23:30 -0700 (PDT) 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 LAA22246 for ; Mon, 7 Aug 2000 11:23:26 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e77INcA22665 for ; Mon, 7 Aug 2000 13:23:38 -0500 (CDT) Received: by ztxmail02.ztx.compaq.com (Postfix, from userid 12345) id 51A5141EE; Mon, 7 Aug 2000 13:24:02 -0500 (CDT) Received: from iota.zk3.dec.com (iota.zk3.dec.com [16.140.32.65]) by ztxmail02.ztx.compaq.com (Postfix) with ESMTP id 03AE440E1 for ; Mon, 7 Aug 2000 13:24:01 -0500 (CDT) Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM) id OAA0000016029; Mon, 7 Aug 2000 14:23:59 -0400 (EDT) Message-ID: <398EFD51.6B3A7B34@zk3.dec.com> Date: Mon, 07 Aug 2000 14:17:53 -0400 From: Mike Daniele Organization: Compaq 64-bit UNIX networking X-Mailer: Mozilla 4.74 [en] (X11; U; OSF1 V5.0 alpha) X-Accept-Language: en MIME-Version: 1.0 To: AgentX WG Subject: a test, please do not respond Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit From owner-agentx@dorothy.peer.com Tue Aug 22 16:31:14 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15202 for ; Tue, 22 Aug 2000 16:31:14 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7MKRNs29400; Tue, 22 Aug 2000 15:27:24 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA24218 for agentx-list; Tue, 22 Aug 2000 13:21:24 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA24212; Tue, 22 Aug 2000 13:21:20 -0700 (PDT) Date: Tue, 22 Aug 2000 13:21:20 -0700 (PDT) From: Randy Presuhn Message-Id: <200008222021.NAA24212@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: Fwd: Regarding Agentx Cc: ajay@pspl.co.in Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - I'm forwarding a non-susbcriber post to the agentx working group mailing list. Since this person hasn't bothered to subscribe, and due to the nature of the query, I suggest responding privately. ------------------------------------------------------- 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 XAA20501 > for ; Mon, 21 Aug 2000 23:09:53 -0700 (PDT) > Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) > by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7M6A2j03362 > for ; Tue, 22 Aug 2000 01:10:02 -0500 (CDT) > Received: from pspl.co.in (lords.intranet.pspl.co.in [192.168.1.14]) > by mail2.pspl.co.in (8.9.3/8.9.3) with ESMTP id LAA26573 > for ; Tue, 22 Aug 2000 11:43:50 +0530 > Message-ID: <39A21A61.499C604E@pspl.co.in> > Date: Tue, 22 Aug 2000 11:44:57 +0530 > From: Ajay Sakpal > X-Mailer: Mozilla 4.72 [en] (WinNT; I) > X-Accept-Language: en > MIME-Version: 1.0 > To: agentx@dorothy.bmc.com > Subject: Regarding Agentx > Content-Type: multipart/mixed; > boundary="------------0E598FECB1C0AB32D8DC2ECA" > > This is a multi-part message in MIME format. > --------------0E598FECB1C0AB32D8DC2ECA > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > Dear sir/madam, > I have visited your site and read specifications about > AgentX RFC 2741 , Can you please brief me about the > platforms on which it is portable, and what are the licence > terms. > Regards > Ajay > > > --------------0E598FECB1C0AB32D8DC2ECA > Content-Type: text/x-vcard; charset=us-ascii; > name="ajay.vcf" > Content-Transfer-Encoding: 7bit > Content-Description: Card for Ajay Sakpal > Content-Disposition: attachment; > filename="ajay.vcf" > > begin:vcard > n:Sakpal;Ajay > tel;work:Ext: 286 > x-mozilla-html:FALSE > adr:;;;;;; > version:2.1 > email;internet:ajay@pspl.co.in > fn:Ajay > end:vcard > > --------------0E598FECB1C0AB32D8DC2ECA-- > > From owner-agentx@dorothy.peer.com Wed Aug 23 10:49:00 2000 Received: from tattler.bmc.com ([198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13398 for ; Wed, 23 Aug 2000 10:48:59 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NEkSP29175; Wed, 23 Aug 2000 09:46:28 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id HAA02310 for agentx-list; Wed, 23 Aug 2000 07:44:29 -0700 (PDT) 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 HAA02304; Wed, 23 Aug 2000 07:44:25 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7NEiR628620; Wed, 23 Aug 2000 09:44:28 -0500 (CDT) Received: from snmc.com (cust-93-18.customer.jump.net [216.30.93.18]) by mail11.jump.net (8.10.2/) with ESMTP id e7NEGm706029; Wed, 23 Aug 2000 09:16:48 -0500 (CDT) Message-ID: <39A3DE79.6369289A@snmc.com> Date: Wed, 23 Aug 2000 09:23:53 -0500 From: Daris A Nevil Organization: SiSIC, Inc. X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Randy Presuhn CC: agentx@dorothy.peer.com, ajay@pspl.co.in Subject: Re: Fwd: Regarding Agentx References: <200008222021.NAA24212@dorothy.bmc.com> Content-Type: multipart/mixed; boundary="------------BD851BE3B4ADCC729CEB1C9B" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list This is a multi-part message in MIME format. --------------BD851BE3B4ADCC729CEB1C9B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Randy, et al, Since there is not very much discussion on this news list I wanted to take just a moment and describe the success we have had with the CMU AgentX implementation. We are using the CMU package under both an Intel and an embedded PowerPC platform on Linux. It works quite well. We did have to fix a bug that caused the snmpd program to crash (see patch below). We also added code that allows for disabling the automatic subagent shutdown on accumulated lost packets (our particular proxy agent protocol responds very slowly). All in all I would describe the CMU AgentX package, along with the CMU SNMP package, as a well written piece of code. We would be interested in hearing other people's success/failures with CMU or other AgentX packages. Regards, Daris Nevil BTW, the inclosed patch should be run from the agentx/snmpd subdir. Randy Presuhn wrote: > > Hi - > > I'm forwarding a non-susbcriber post to the agentx working group > mailing list. Since this person hasn't bothered to subscribe, > and due to the nature of the query, I suggest responding privately. > > > > > Dear sir/madam, > > I have visited your site and read specifications about > > AgentX RFC 2741 , Can you please brief me about the > > platforms on which it is portable, and what are the licence > > terms. > > Regards > > Ajay > > -- Daris A Nevil Simple Network Magic Corporation 401 Kentucky Lane McKinney, TX 75069 214-793-7757 dnevil@snmc.com www.snmc.com quickstack.com qslinux.org --------------BD851BE3B4ADCC729CEB1C9B Content-Type: application/x-unknown-content-type-patch_auto_file; name="snmpd_snmc.patch" Content-Disposition: inline; filename="snmpd_snmc.patch" Content-Transfer-Encoding: base64 LS0tIGVuZ2luZV9zbm1wLmMub3JpZwlXZWQgQXVnIDIzIDA4OjU5OjU3IDIwMDAKKysrIGVu Z2luZV9zbm1wLmMJV2VkIEF1ZyAyMyAwOTowMDo1NiAyMDAwCkBAIC0yMCw3ICsyMCw3IEBA CiAgKiBBUklTSU5HIE9VVCBPRiBPUiBJTiBDT05ORUNUSU9OIFdJVEggVEhFIFVTRSBPUiBQ RVJGT1JNQU5DRSBPRiBUSElTCiAgKiBTT0ZUV0FSRS4KICAqIAotICogJElkOiBlbmdpbmVf c25tcC5jLHYgMS4xIDIwMDAvMDcvMjAgMjA6MzM6NDAgZG5ldmlsIEV4cCAkCisgKiAkSWQ6 IGVuZ2luZV9zbm1wLmMsdiAxLjIgMjAwMC8wOC8xOSAxNzo0NDowNCBtcG9sYW5kIEV4cCAk CiAgKiAKICAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqLwogCkBAIC0yNDQsNyArMjQ0LDYgQEAKICAgICB3 aGlsZSAoIHZhcnMgIT0gTlVMTCApIHsKICAgICAgIHRyYW5zX3ZhcmJpbmQgPSAodHJhbnNf dmJpbmRfdCAqKW10a19tYWxsb2MoIHNpemVvZiggdHJhbnNfdmJpbmRfdCApLCAKIAkJCQkJ CSAgIGZuICk7Ci0gICAgICAKICAgICAgIGlmICggdHJhbnMtPnR5cGUgPT0gR0VUQlVMSyAp IHsKIAlpZiAoIGluZGV4IDw9IG5vbl9yZXBlYXRlcnMgKQogCSAgdHJhbnNfdmFyYmluZC0+ cmVwZXRpdGlvbnMgPSAxOwpAQCAtMjc3LDYgKzI3NiwxMyBAQAogCXRyYW5zX3ZhcmJpbmQt PnNlYXJjaF9yYW5nZS5zdGFydC5Oc3ViaWQgID0gdmFycy0+bmFtZV9sZW5ndGg7CiAJdHJh bnNfdmFyYmluZC0+c2VhcmNoX3JhbmdlLnN0YXJ0LnN1YmlkcyAgPSB2YXJzLT5uYW1lOwog CXRyYW5zX3ZhcmJpbmQtPnNlYXJjaF9yYW5nZS5zdGFydC5pbmNsdWRlID0gMDsKKworCS8v IEluaXRpYWxpemUgdGhlIGVuZCBvZiB0aGUgcmFuZ2Ugc28gdGhhdAorCS8vIHRoZSBjb2Rl IHdvbid0IGF0dGVtcHQgdG8gZW5jb2RlIGFuIG9iamVjdCBpZCB1c2luZyBpdAorCS8vIGxh dGVyIG9uLgorCXRyYW5zX3ZhcmJpbmQtPnNlYXJjaF9yYW5nZS5lbmQuTnN1YmlkICA9IDA7 CisJdHJhbnNfdmFyYmluZC0+c2VhcmNoX3JhbmdlLmVuZC5zdWJpZHMgID0gMDsKKwl0cmFu c192YXJiaW5kLT5zZWFyY2hfcmFuZ2UuZW5kLmluY2x1ZGUgPSAwOwogCiAJdmFycy0+bmFt ZSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA9IE5VTEw7CiAJdmFycy0+bmFtZV9s ZW5ndGggICAgICAgICAgICAgICAgICAgICAgICA9IDA7Ci0tLSBzdWJhZ2VudC5jLm9yaWcJ VGh1IEp1bCAyMCAxNjozMzo0MCAyMDAwCisrKyBzdWJhZ2VudC5jCVNhdCBBdWcgMTkgMTM6 NDQ6NTMgMjAwMApAQCAtMjAsNyArMjAsNyBAQAogICogQVJJU0lORyBPVVQgT0YgT1IgSU4g Q09OTkVDVElPTiBXSVRIIFRIRSBVU0UgT1IgUEVSRk9STUFOQ0UgT0YgVEhJUwogICogU09G VFdBUkUuCiAgKiAKLSAqICRJZDogc3ViYWdlbnQuYyx2IDEuMSAyMDAwLzA3LzIwIDIwOjMz OjQwIGRuZXZpbCBFeHAgJAorICogJElkOiBzdWJhZ2VudC5jLHYgMS4yIDIwMDAvMDgvMTkg MTc6NDQ6NTMgbXBvbGFuZCBFeHAgJAogICogCiAgKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi8KIApAQCAt MTQ1LDggKzE0NSw5IEBACiAgIHN1YmFnZW50ID0gKHN1YmFnZW50X3QgKiltdGtfdGFibGVf Z2V0ZW50cnkgKCBTdWJhZ2VudFRhYmxlLCBzdWJhZ2VudF9udW0gKTsKICAgaWYgKCBzdWJh Z2VudCAhPSBOVUxMICkgewogICAgIHN1YmFnZW50LT5OdGltZW91dHMrKzsKLSAgICAKLSAg ICBpZiAoIHN1YmFnZW50LT5OdGltZW91dHMgPj0gU3ViYWdlbnRNYXhUaW1lb3V0cyApIHsK KworICAgIC8vIERvbid0IGNsb3NlIHRoZSBzZXNzaW9uIG9mIFN1YmFnZW50TWF4VGltZW91 dHMgaGFzIGJlZW4gZGlzYWJsZWQKKyAgICBpZiAoIHN1YmFnZW50LT5OdGltZW91dHMgPj0g U3ViYWdlbnRNYXhUaW1lb3V0cyAmJiBTdWJhZ2VudE1heFRpbWVvdXRzKSB7CiAgICAgICBk byB7CiAJaW5kZXggPSBzZXNzaW9uX2dldG5leHRieXNhKCBzdWJhZ2VudF9udW0sIGluZGV4 ICk7CiAJaWYgKCBpbmRleCAhPSBNVEtfVEFCTEVfRU5EICkKQEAgLTE3MSw3ICsxNzIsOSBA QAogICBpZiAoIHN1YmFnZW50ICE9IE5VTEwgKSB7CiAgICAgc3ViYWdlbnQtPk5wYXJzZUVy cm9ycysrOwogICAgIAotICAgIGlmICggc3ViYWdlbnQtPk5wYXJzZUVycm9ycyA+PSBTdWJh Z2VudE1heFBhcnNlRXJyb3JzICkgeworICAgIC8vIERvbid0IGNsb3NlIHRoZSBzZXNzaW9u IG9mIFN1YmFnZW50TWF4UGFyc2VFcnJvcnMgaGFzIGJlZW4gZGlzYWJsZWQKKyAgICBpZiAo IHN1YmFnZW50LT5OcGFyc2VFcnJvcnMgPj0gU3ViYWdlbnRNYXhQYXJzZUVycm9ycyAmJgor ICAgICAgICAgU3ViYWdlbnRNYXhQYXJzZUVycm9ycykgewogICAgICAgZG8gewogCWluZGV4 ID0gc2Vzc2lvbl9nZXRuZXh0YnlzYSggc3ViYWdlbnRfbnVtLCBpbmRleCApOwogCWlmICgg aW5kZXggIT0gTVRLX1RBQkxFX0VORCApCg== --------------BD851BE3B4ADCC729CEB1C9B-- From owner-agentx@dorothy.peer.com Wed Aug 23 11:48:11 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 ESMTP id LAA15676 for ; Wed, 23 Aug 2000 11:48:10 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NFjDI13158; Wed, 23 Aug 2000 10:45:13 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA02430 for agentx-list; Wed, 23 Aug 2000 08:44:18 -0700 (PDT) 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 IAA02425 for ; Wed, 23 Aug 2000 08:44:14 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7NFiLk12885 for ; Wed, 23 Aug 2000 10:44:22 -0500 (CDT) Received: from bnatale.acecomm.com (ppp10.acec.com [38.249.211.63]) by relay1.acec.com (8.9.3/8.9.3) with ESMTP id LAA14300; Wed, 23 Aug 2000 11:47:19 -0400 (EDT) Message-Id: <4.3.2.7.2.20000823113639.00b9e090@plymouth.acec.com> X-Sender: bnatale@plymouth.acec.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 23 Aug 2000 11:47:28 -0400 To: Daris A Nevil From: Bob Natale Subject: Re: Fwd: Regarding Agentx Cc: agentx@dorothy.peer.com In-Reply-To: <39A3DE79.6369289A@snmc.com> References: <200008222021.NAA24212@dorothy.bmc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list At 8/23/2000:10:23 AM, Daris A Nevil wrote: Hi Daris, >Since there is not very much discussion on this news list I wanted to >take just a moment and describe the success we have had with the CMU AgentX >implementation. Thanks...this is exactly the kind of posting that's needed on this list at this time...i.e., those concerned with implementation and deployment issues...not to the exclusion, of course, of any technical questions about the AgentX protocol or MIB, or the two RFCs, or new work, or administration of the WG. >We are using the CMU package Can you provide a pointer to the current CMU code...I don't recall having heard anything new since Matt White left CMU some time ago. >under both an Intel and an embedded PowerPC platform on Linux. Is that Linux on both platforms (can you also let us know the particular flavor/version of Linux you are using)? >It works quite well. Excellent news. >We did have to fix a bug that caused the snmpd program to crash >(see patch below). Thanks...have you tried to get this back to the CMU folks (of course, let's hope they are also monitoring this channel!). >We also added code that allows for disabling the automatic subagent >shutdown on accumulated lost packets And that's in the patch too...? >(our particular proxy agent protocol responds very slowly). I assume you are saying that this slowness is not inherently related to AgentX itself? >All in all I would describe the CMU AgentX package, along with the >CMU SNMP package, as a well written piece of code. Excellent. >We would be interested in hearing other people's success/failures >with CMU or other AgentX packages. Do you monitor the UCD-SNMP work (an off-shoot from an older CMU-SNMP release)? Their list has had a fair amount of traffic re the UCD-SNMP AgentX implementation (developed independently of the CMU-SNMP AgentX work, AFAIK) in recent months...? >BTW, the inclosed patch should be run from the agentx/snmpd subdir. Ok...again, thanks a million for posting this info...I may ask you for a more formal (but only slightly so!) report in the near future. Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ------------- Free downloads at www.winsnmp.com ------------- From owner-agentx@dorothy.peer.com Wed Aug 23 12:18:48 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17411 for ; Wed, 23 Aug 2000 12:18:48 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NG5dd18208; Wed, 23 Aug 2000 11:05:39 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA02481 for agentx-list; Wed, 23 Aug 2000 09:04:02 -0700 (PDT) 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 JAA02476 for ; Wed, 23 Aug 2000 09:03:58 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7NG47p17764 for ; Wed, 23 Aug 2000 11:04:07 -0500 (CDT) Received: from snmc.com (cust-93-18.customer.jump.net [216.30.93.18]) by mail15.jump.net (8.10.2/) with ESMTP id e7NG4f124879; Wed, 23 Aug 2000 11:04:41 -0500 (CDT) Message-ID: <39A3F7C5.738BD16E@snmc.com> Date: Wed, 23 Aug 2000 11:11:49 -0500 From: Daris A Nevil Organization: SiSIC, Inc. X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Bob Natale CC: agentx@dorothy.peer.com Subject: Re: Fwd: Regarding Agentx References: <200008222021.NAA24212@dorothy.bmc.com> <4.3.2.7.2.20000823113639.00b9e090@plymouth.acec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi Bob, Thanks for your enthusiasm. I was beginning to think that I am the only one excited about AgentX. > Can you provide a pointer to the current CMU code...I don't > recall having heard anything new since Matt White left CMU > some time ago. The version we started with was downloaded from: http://www.net.cmu.edu/groups/netdev/agentx/ > Is that Linux on both platforms (can you also let us know > the particular flavor/version of Linux you are using)? We are using Redhad 6.2 for our Intel platform, and QSLinux for our MPC850 embedded PowerPC platform (see http://qslinux.org and ftp://qslinux.org). > >We did have to fix a bug that caused the snmpd program to crash > >(see patch below). > > Thanks...have you tried to get this back to the CMU > folks (of course, let's hope they are also monitoring > this channel!). I forwarded the bug fix to agentx-bugs@andrew.cmu.edu > > >We also added code that allows for disabling the automatic subagent > >shutdown on accumulated lost packets > > And that's in the patch too...? Yes. > > >(our particular proxy agent protocol responds very slowly). > > I assume you are saying that this slowness is not inherently > related to AgentX itself? You are correct in that it has nothing to do with AgentX. Our subagent collects data across a slow async bus, so the snmpd program sometimes times out the subagent. The original code always shuts down the subagent after 3 timed out AgentX packets (or whatever AgentxSubagmentMaxTimeouts was set to in /etc/snmpd.conf). Our modified code lets us disable this "feature" by setting AgentxSubagentMaxTimeouts and AgentxSubagentMaxParseErrors to zero. > > Do you monitor the UCD-SNMP work (an off-shoot from an older > CMU-SNMP release)? Their list has had a fair amount of traffic > re the UCD-SNMP AgentX implementation (developed independently > of the CMU-SNMP AgentX work, AFAIK) in recent months...? We were not aware of the UCD package when we started working with the CMU package. We were also drawn to the CMU package because of earlier experience with the CMU SNMP package, which we are also using. One thing that the AgentX package needs is a thoroughly cleaned and updated documentation package. There are comments in the release notes that say things like: * Set is not supported * TCP is not supported * Getbulk is not supported From what we have seen all of these features are supported by the current version of CMU AgentX. It appears to be complete. -- Daris A Nevil Simple Network Magic Corporation 401 Kentucky Lane McKinney, TX 75069 214-793-7757 dnevil@snmc.com www.snmc.com quickstack.com qslinux.org From owner-agentx@dorothy.peer.com Wed Aug 23 12:40:43 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18090 for ; Wed, 23 Aug 2000 12:40:43 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NGcNp25487; Wed, 23 Aug 2000 11:38:24 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA02563 for agentx-list; Wed, 23 Aug 2000 09:37:33 -0700 (PDT) Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA02558 for ; Wed, 23 Aug 2000 09:37:29 -0700 (PDT) Received: from ec03-hou.bmc.com (ec03-hou.bmc.com [172.20.4.32]) by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e7NGcAd11096; Wed, 23 Aug 2000 11:38:10 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Aug 2000 11:40:06 -0500 Message-ID: From: "Ayers, Mike" To: "'Daris A Nevil'" Cc: agentx@dorothy.peer.com Subject: RE: Fwd: Regarding Agentx Date: Wed, 23 Aug 2000 11:39:30 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list > From: Daris A Nevil [mailto:dnevil@snmc.com] > > > > >(our particular proxy agent protocol responds very slowly). > > > > I assume you are saying that this slowness is not inherently > > related to AgentX itself? > > You are correct in that it has nothing to do with AgentX. Our > subagent collects data across a slow async bus, so the snmpd > program sometimes times out the subagent. The original code > always shuts down the subagent after 3 timed out AgentX packets > (or whatever AgentxSubagmentMaxTimeouts was set to in > /etc/snmpd.conf). > Our modified code lets us disable this "feature" by setting > AgentxSubagentMaxTimeouts and AgentxSubagentMaxParseErrors to zero. > I feel obligated to point out that this is not the best solution to this problem. If you have a slow link to your subagent, then you should set the timeout to a correspondingly high value. The best thing to do would be to set the timeout for the region which is serviced over the slow link. However, you could, if necessary, set the master agent default timeout - it's really a question of how the CMU package supports timeouts. Telling the master agent never to disconnect means disabling connection management, which probably wouldn't be well received in the event of a real connection failure. If you set the timeout to a sufficiently high value, then the master agent will wait for the slow link but will still be able to detect a failed link. The key problem is that the patch you made violates: =====8<-----SNIP----- 7.2.5.1. Common Processing of All AgentX Response PDUs 1) If a response is not received on a session within the timeout interval for this dispatch, it is treated as if the subagent had returned `genErr' and processed as described below. A timeout may be due to a variety of reasons, and does not necessarily denote a failed or malfunctioning subagent. As such, the master agent's response to a subagent timeout is implementation-specific, but with the following constraint: A session that times out on three consecutive AgentX requests is considered unable to respond, and the master agent must close the AgentX session as described in section 7.1.8, "Processing the agentx-Close-PDU", step (2). =====8<-----SNIP----- ...and a must is a must... /|/|ike From owner-agentx@dorothy.peer.com Wed Aug 23 12:47:43 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18325 for ; Wed, 23 Aug 2000 12:47:43 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NGiqR26638; Wed, 23 Aug 2000 11:44:52 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA02586 for agentx-list; Wed, 23 Aug 2000 09:44:06 -0700 (PDT) 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 JAA02581 for ; Wed, 23 Aug 2000 09:44:02 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7NGiBw26520 for ; Wed, 23 Aug 2000 11:44:11 -0500 (CDT) Received: from snmc.com (cust-93-18.customer.jump.net [216.30.93.18]) by mail11.jump.net (8.10.2/) with ESMTP id e7NGilq11806; Wed, 23 Aug 2000 11:44:47 -0500 (CDT) Message-ID: <39A4012A.E6BEBEC1@snmc.com> Date: Wed, 23 Aug 2000 11:51:54 -0500 From: Daris A Nevil Organization: SiSIC, Inc. X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "Ayers, Mike" CC: agentx@dorothy.peer.com Subject: Re: Fwd: Regarding Agentx References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi Mike, Thanks for the feedback. Since we are running in an embedded system we never want to have our subagent disconnected. And it should never disconnect anyway, since we are using Unix domain sockets. If we were using the TCP socket protocol then I could see the importance of the connection management code. We are currently experienting with the timeout mechanism, but its not too cut-and-dry since we have variable response times from our managed cards depending on the data (sent to our subagent). Regards, Daris "Ayers, Mike" wrote: > > > From: Daris A Nevil [mailto:dnevil@snmc.com] > > > > > > > >(our particular proxy agent protocol responds very slowly). > > > > > > I assume you are saying that this slowness is not inherently > > > related to AgentX itself? > > > > You are correct in that it has nothing to do with AgentX. Our > > subagent collects data across a slow async bus, so the snmpd > > program sometimes times out the subagent. The original code > > always shuts down the subagent after 3 timed out AgentX packets > > (or whatever AgentxSubagmentMaxTimeouts was set to in > > /etc/snmpd.conf). > > Our modified code lets us disable this "feature" by setting > > AgentxSubagentMaxTimeouts and AgentxSubagentMaxParseErrors to zero. > > > > I feel obligated to point out that this is not the best solution to > this problem. If you have a slow link to your subagent, then you should set > the timeout to a correspondingly high value. The best thing to do would be > to set the timeout for the region which is serviced over the slow link. > However, you could, if necessary, set the master agent default timeout - > it's really a question of how the CMU package supports timeouts. Telling > the master agent never to disconnect means disabling connection management, > which probably wouldn't be well received in the event of a real connection > failure. If you set the timeout to a sufficiently high value, then the > master agent will wait for the slow link but will still be able to detect a > failed link. The key problem is that the patch you made violates: > > =====8<-----SNIP----- > 7.2.5.1. Common Processing of All AgentX Response PDUs > > 1) If a response is not received on a session within the timeout > interval for this dispatch, it is treated as if the subagent had > returned `genErr' and processed as described below. > > A timeout may be due to a variety of reasons, and does not > necessarily denote a failed or malfunctioning subagent. As such, > the master agent's response to a subagent timeout is > implementation-specific, but with the following constraint: > > A session that times out on three consecutive AgentX requests is > considered unable to respond, and the master agent must close the > AgentX session as described in section 7.1.8, "Processing the > agentx-Close-PDU", step (2). > =====8<-----SNIP----- > > ...and a must is a must... > > /|/|ike -- Daris A Nevil Simple Network Magic Corporation 401 Kentucky Lane McKinney, TX 75069 214-793-7757 dnevil@snmc.com www.snmc.com quickstack.com qslinux.org From owner-agentx@dorothy.peer.com Wed Aug 23 13:30:00 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19325 for ; Wed, 23 Aug 2000 13:29:59 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NHRbw02941; Wed, 23 Aug 2000 12:27:38 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA03018 for agentx-list; Wed, 23 Aug 2000 10:25:38 -0700 (PDT) Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA03013 for ; Wed, 23 Aug 2000 10:25:34 -0700 (PDT) Received: from ec03-hou.bmc.com (ec03-hou.bmc.com [172.20.4.32]) by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e7NHQFd15314; Wed, 23 Aug 2000 12:26:15 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Aug 2000 12:28:11 -0500 Message-ID: From: "Ayers, Mike" To: "'Daris A Nevil'" , "Ayers, Mike" Cc: agentx@dorothy.peer.com Subject: RE: Fwd: Regarding Agentx Date: Wed, 23 Aug 2000 12:27:36 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list > From: Daris A Nevil [mailto:dnevil@snmc.com] > > Thanks for the feedback. Since we are running in an embedded system > we never want to have our subagent disconnected. And it should never > disconnect anyway, since we are using Unix domain sockets. If we were > using the TCP socket protocol then I could see the importance of the > connection management code. I was mostly concerned about the possibility that the patch you posted would start making rounds, leaving some folks unaware that they were now using a noncompliant master agent. > We are currently experienting with the timeout mechanism, but its not > too cut-and-dry since we have variable response times from our managed > cards depending on the data (sent to our subagent). Suggestion: use a limit size of 1500 bytes, sufficient to pass the largest ethernet frame, and calculate the timeout as twice the time to move 1500 bytes (you may wish to adjust for AgentX overhead in search ranges, etc.) plus max computational time. Now double it. That should give you a workable timeout value. If the computational times vary wildly (often a problem in realtime systems), you may want to consider using MIB semaphoring or some such mechanism, since SNMP tends to tacitly assume trivial computational times for instance values. /|/|ike From owner-agentx@dorothy.peer.com Wed Aug 23 18:31:14 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 ESMTP id SAA23806 for ; Wed, 23 Aug 2000 18:31:14 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7NMS3H03585; Wed, 23 Aug 2000 17:28:04 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA05307 for agentx-list; Wed, 23 Aug 2000 15:25:19 -0700 (PDT) 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 PAA05299; Wed, 23 Aug 2000 15:25:14 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7NMPOm03208; Wed, 23 Aug 2000 17:25:24 -0500 (CDT) Received: from cisco.com (klingle-ultra.cisco.com [161.44.53.27]) by uzura.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id SAA22882; Wed, 23 Aug 2000 18:24:16 -0400 (EDT) Message-ID: <39A44F36.20698DCB@cisco.com> Date: Wed, 23 Aug 2000 18:24:54 -0400 From: Kevin Lingle X-Mailer: Mozilla 4.51C-CISCOENG [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Daris A Nevil CC: Randy Presuhn , agentx@dorothy.peer.com, ajay@pspl.co.in Subject: Re: Fwd: Regarding Agentx References: <200008222021.NAA24212@dorothy.bmc.com> <39A3DE79.6369289A@snmc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Anyone have good, bad, ugly experience using ucd-snmp agentx? kevin Daris A Nevil wrote: > > Randy, et al, > > Since there is not very much discussion on this news list I wanted to > take > just a moment and describe the success we have had with the CMU AgentX > implementation. We are using the CMU package under both an Intel and an > embedded PowerPC platform on Linux. It works quite well. We did have > to fix a bug that caused the snmpd program to crash (see patch below). > We also added code that allows for disabling the automatic subagent > shutdown on accumulated lost packets (our particular proxy agent > protocol > responds very slowly). > > All in all I would describe the CMU AgentX package, along with the > CMU SNMP package, as a well written piece of code. We would be > interested in hearing other people's success/failures with CMU > or other AgentX packages. > > Regards, > Daris Nevil > > BTW, the inclosed patch should be run from the agentx/snmpd subdir. > > Randy Presuhn wrote: > > > > Hi - > > > > I'm forwarding a non-susbcriber post to the agentx working group > > mailing list. Since this person hasn't bothered to subscribe, > > and due to the nature of the query, I suggest responding privately. > > > > > > > > Dear sir/madam, > > > I have visited your site and read specifications about > > > AgentX RFC 2741 , Can you please brief me about the > > > platforms on which it is portable, and what are the licence > > > terms. > > > Regards > > > Ajay > > > > > -- > Daris A Nevil > Simple Network Magic Corporation > 401 Kentucky Lane > McKinney, TX 75069 > 214-793-7757 > dnevil@snmc.com > www.snmc.com > quickstack.com > qslinux.org > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > Name: snmpd_snmc.patch > snmpd_snmc.patch Type: application/x-unknown-content-type-patch_auto_file > Encoding: base64 -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Kevin R. Lingle 919.392.2029 checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html Sometimes I think I understand everything, then I regain consciousness. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-agentx@dorothy.peer.com Thu Aug 24 11:53:18 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 ESMTP id LAA19545 for ; Thu, 24 Aug 2000 11:53:18 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7OFmgn23848; Thu, 24 Aug 2000 10:48:42 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA13477 for agentx-list; Thu, 24 Aug 2000 08:45:28 -0700 (PDT) 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 IAA13472 for ; Thu, 24 Aug 2000 08:45:24 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7OFjTe23081 for ; Thu, 24 Aug 2000 10:45:29 -0500 (CDT) Received: from cisco.com (klingle-ultra.cisco.com [161.44.53.27]) by uzura.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA09492; Thu, 24 Aug 2000 11:43:51 -0400 (EDT) Message-ID: <39A542DD.B1CF32F@cisco.com> Date: Thu, 24 Aug 2000 11:44:29 -0400 From: Kevin Lingle X-Mailer: Mozilla 4.51C-CISCOENG [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Daris A Nevil CC: Bob Natale , agentx@dorothy.peer.com Subject: Re: Fwd: Regarding Agentx References: <200008222021.NAA24212@dorothy.bmc.com> <4.3.2.7.2.20000823113639.00b9e090@plymouth.acec.com> <39A3F7C5.738BD16E@snmc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Daris A Nevil wrote: > > The version we started with was downloaded from: > > http://www.net.cmu.edu/groups/netdev/agentx/ So I take that to mean you downloaded ver 1.4.1 ?? I have been evaluating a few extensible agents and looked at CMU as well as UCD-SNMP. When I browsed the cmu website I notice that nothing seemed to be updated in a long time. I sent some email asking about current status and development activities. About two weeks later I got the following response: ---- email begin From: "Russell J. Yount" 07/28/00 12:30 Subject: CMU software releases To: klingle@cisco.com kevin, At the current time we have no developers working on it. We have lost a greate deal of staff over recent years to outside companies, and as such have drop development of this. -Russ Russell J. Yount Manager of Network Development Carnegie Mellon University (412) 268-8391 ** ** Initial Query From klingle@cisco.com ** Thu, 13 Jul 2000 16:55:32 -0400 ** To: dc0m@andrew.cmu.edu ** Hi, Your web page http://www.net.cmu.edu/groups/netdev/snmpd.html indicates that SET support is not available in your extensible snmp agent. It further indicates that support is planned near term. Is set support available yet? All of your pages and your release history date back to 1998. Is this project even active anymore?? Have there truely been no updates to code or web since 1998?!?!? kevin ---- email end Further if you look at the README from UCD-SNMP ver 4.1.2 you see the following: "My snmp code, based on the CMU 2.1.2.1 version with a lot of additions. It is fully extensible." Thus, I abandoned any consideration of CMU code and am opting for UCD-SNMP. While I'm glad to hear of the successes you've had, I'm wondering why you are even using the CMU code downloaded from their website as it seems to be quite behind the times? Kevin -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Kevin R. Lingle 919.392.2029 checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html Sometimes I think I understand everything, then I regain consciousness. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-agentx@dorothy.peer.com Thu Aug 24 13:09:25 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20647 for ; Thu, 24 Aug 2000 13:09:24 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7OH5dR11843; Thu, 24 Aug 2000 12:05:39 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA15391 for agentx-list; Thu, 24 Aug 2000 10:04:17 -0700 (PDT) Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA15364 for ; Thu, 24 Aug 2000 10:04:12 -0700 (PDT) Received: from ec03-hou.bmc.com (ec03-hou.bmc.com [172.20.4.32]) by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e7OH4ed10761; Thu, 24 Aug 2000 12:04:41 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21) id ; Thu, 24 Aug 2000 12:06:36 -0500 Message-ID: From: "Ayers, Mike" To: "'Kevin Lingle'" , Daris A Nevil Cc: Bob Natale , agentx@dorothy.peer.com Subject: RE: Fwd: Regarding Agentx Date: Thu, 24 Aug 2000 12:05:20 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list This issue also crossed the UCD-SNMP mailing list, where one of the CMU AgentX developers also pointed out that there is currently no new development. However, that thread had been started by someone who had used CMU AgentX successfully, and it was agreed that within certain parameters, CMU was useable. If there is interest, I can root through my archives and post the thread. /|/|ike > -----Original Message----- > From: Kevin Lingle [mailto:klingle@cisco.com] > Sent: Thursday, August 24, 2000 8:44 AM > To: Daris A Nevil > Cc: Bob Natale; agentx@dorothy.peer.com > Subject: Re: Fwd: Regarding Agentx > > > > Daris A Nevil wrote: > > > > > The version we started with was downloaded from: > > > > http://www.net.cmu.edu/groups/netdev/agentx/ > > So I take that to mean you downloaded ver 1.4.1 ?? > > I have been evaluating a few extensible agents and looked at CMU > as well as UCD-SNMP. When I browsed the cmu website I notice > that nothing seemed to be updated in a long time. I sent some > email asking about current status and development activities. > About two weeks later I got the following response: > > ---- email begin > From: "Russell J. Yount" > 07/28/00 12:30 > Subject: CMU software releases > To: klingle@cisco.com > > kevin, > At the current time we have no developers working on it. > We have lost a greate deal of staff over recent years to > outside companies, > and as such have drop development of this. > > -Russ > > Russell J. Yount > Manager of Network Development > Carnegie Mellon University > (412) 268-8391 > > ** > ** Initial Query From klingle@cisco.com > ** Thu, 13 Jul 2000 16:55:32 -0400 > ** To: dc0m@andrew.cmu.edu > ** > > Hi, > > Your web page http://www.net.cmu.edu/groups/netdev/snmpd.html > indicates that SET support is not available in your extensible > snmp agent. It further indicates that support is planned near term. > > Is set support available yet? > > All of your pages and your release history date back to 1998. > Is this project even active anymore?? Have there truely been > no updates to code or web since 1998?!?!? > > kevin > ---- email end > > Further if you look at the README from UCD-SNMP ver 4.1.2 you see > the following: > > "My snmp code, based on the CMU 2.1.2.1 version with a lot of > additions. It is fully extensible." > > Thus, I abandoned any consideration of CMU code and am opting for > UCD-SNMP. > > While I'm glad to hear of the successes you've had, I'm wondering > why you are even using the CMU code downloaded from their website > as it seems to be quite behind the times? > > Kevin > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > =-=-=-=-= > Kevin R. Lingle 919.392.2029 > checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html > Sometimes I think I understand everything, then I regain > consciousness. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > =-=-=-=-= > From owner-agentx@dorothy.peer.com Thu Aug 24 13:40:08 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 ESMTP id NAA21197 for ; Thu, 24 Aug 2000 13:40:07 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7OHaI117523; Thu, 24 Aug 2000 12:36:18 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA18865 for agentx-list; Thu, 24 Aug 2000 10:35:31 -0700 (PDT) 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 KAA18860 for ; Thu, 24 Aug 2000 10:35:23 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7OHZVF17371 for ; Thu, 24 Aug 2000 12:35:31 -0500 (CDT) Received: from cisco.com (klingle-ultra.cisco.com [161.44.53.27]) by uzura.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id NAA22241; Thu, 24 Aug 2000 13:33:52 -0400 (EDT) Message-ID: <39A55CA6.353DCE9@cisco.com> Date: Thu, 24 Aug 2000 13:34:30 -0400 From: Kevin Lingle X-Mailer: Mozilla 4.51C-CISCOENG [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Ayers, Mike" CC: Daris A Nevil , Bob Natale , agentx@dorothy.peer.com Subject: Re: Fwd: Regarding Agentx References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit i'd be interested in at least a summary of what "within certain parameters" means. kevin "Ayers, Mike" wrote: > > This issue also crossed the UCD-SNMP mailing list, where one of the > CMU AgentX developers also pointed out that there is currently no new > development. However, that thread had been started by someone who had used > CMU AgentX successfully, and it was agreed that within certain parameters, > CMU was useable. If there is interest, I can root through my archives and > post the thread. > > /|/|ike > > > -----Original Message----- > > From: Kevin Lingle [mailto:klingle@cisco.com] > > Sent: Thursday, August 24, 2000 8:44 AM > > To: Daris A Nevil > > Cc: Bob Natale; agentx@dorothy.peer.com > > Subject: Re: Fwd: Regarding Agentx > > > > > > > > Daris A Nevil wrote: > > > > > > > > The version we started with was downloaded from: > > > > > > http://www.net.cmu.edu/groups/netdev/agentx/ > > > > So I take that to mean you downloaded ver 1.4.1 ?? > > > > I have been evaluating a few extensible agents and looked at CMU > > as well as UCD-SNMP. When I browsed the cmu website I notice > > that nothing seemed to be updated in a long time. I sent some > > email asking about current status and development activities. > > About two weeks later I got the following response: > > > > ---- email begin > > From: "Russell J. Yount" > > 07/28/00 12:30 > > Subject: CMU software releases > > To: klingle@cisco.com > > > > kevin, > > At the current time we have no developers working on it. > > We have lost a greate deal of staff over recent years to > > outside companies, > > and as such have drop development of this. > > > > -Russ > > > > Russell J. Yount > > Manager of Network Development > > Carnegie Mellon University > > (412) 268-8391 > > > > ** > > ** Initial Query From klingle@cisco.com > > ** Thu, 13 Jul 2000 16:55:32 -0400 > > ** To: dc0m@andrew.cmu.edu > > ** > > > > Hi, > > > > Your web page http://www.net.cmu.edu/groups/netdev/snmpd.html > > indicates that SET support is not available in your extensible > > snmp agent. It further indicates that support is planned near term. > > > > Is set support available yet? > > > > All of your pages and your release history date back to 1998. > > Is this project even active anymore?? Have there truely been > > no updates to code or web since 1998?!?!? > > > > kevin > > ---- email end > > > > Further if you look at the README from UCD-SNMP ver 4.1.2 you see > > the following: > > > > "My snmp code, based on the CMU 2.1.2.1 version with a lot of > > additions. It is fully extensible." > > > > Thus, I abandoned any consideration of CMU code and am opting for > > UCD-SNMP. > > > > While I'm glad to hear of the successes you've had, I'm wondering > > why you are even using the CMU code downloaded from their website > > as it seems to be quite behind the times? > > > > Kevin > > -- > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > =-=-=-=-= > > Kevin R. Lingle 919.392.2029 > > checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html > > Sometimes I think I understand everything, then I regain > > consciousness. > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > =-=-=-=-= > > -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Kevin R. Lingle 919.392.2029 checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html Sometimes I think I understand everything, then I regain consciousness. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-agentx@dorothy.peer.com Tue Aug 29 11:39:12 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22763 for ; Tue, 29 Aug 2000 11:39:11 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7TFaYd11410; Tue, 29 Aug 2000 10:36:38 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA29410 for agentx-list; Tue, 29 Aug 2000 08:32:01 -0700 (PDT) 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 IAA29398 for ; Tue, 29 Aug 2000 08:31:53 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7TFVnS09643 for ; Tue, 29 Aug 2000 10:31:49 -0500 (CDT) Received: from localhost (mwhite@localhost) by bacardi.torrentnet.com (8.10.2/8.10.2) with SMTP id e7SFkha02050; Mon, 28 Aug 2000 11:46:43 -0400 (EDT) Date: Mon, 28 Aug 2000 11:46:43 -0400 (EDT) From: Matt White To: Kevin Lingle cc: "Ayers, Mike" , Daris A Nevil , Bob Natale , agentx@dorothy.peer.com Subject: Re: Fwd: Regarding Agentx In-Reply-To: <39A55CA6.353DCE9@cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list On Thu, 24 Aug 2000, Kevin Lingle wrote: > > i'd be interested in at least a summary of what "within certain parameters" means. > Off the top of my head: * Is CMU feature complete for your needs? * Do you need a support infrastructure? UCD has pretty good support lists. CMU has pretty much nothing besides what you can wheedle out of me ;). * Is size important? CMU is slimmer than UCD. * Are you building subagents from scratch or are you instrumenting already existing code? CMU was built with instrumentation of already existing code in mind. UCD also works for this purpose, but Wes keeps saying that he thinks the CMU package might be better for that and so I'm starting to believe him. -Matt > kevin > "Ayers, Mike" wrote: > > > > This issue also crossed the UCD-SNMP mailing list, where one of the > > CMU AgentX developers also pointed out that there is currently no new > > development. However, that thread had been started by someone who had used > > CMU AgentX successfully, and it was agreed that within certain parameters, > > CMU was useable. If there is interest, I can root through my archives and > > post the thread. > > > > /|/|ike > > > > > -----Original Message----- > > > From: Kevin Lingle [mailto:klingle@cisco.com] > > > Sent: Thursday, August 24, 2000 8:44 AM > > > To: Daris A Nevil > > > Cc: Bob Natale; agentx@dorothy.peer.com > > > Subject: Re: Fwd: Regarding Agentx > > > > > > > > > > > > Daris A Nevil wrote: > > > > > > > > > > > The version we started with was downloaded from: > > > > > > > > http://www.net.cmu.edu/groups/netdev/agentx/ > > > > > > So I take that to mean you downloaded ver 1.4.1 ?? > > > > > > I have been evaluating a few extensible agents and looked at CMU > > > as well as UCD-SNMP. When I browsed the cmu website I notice > > > that nothing seemed to be updated in a long time. I sent some > > > email asking about current status and development activities. > > > About two weeks later I got the following response: > > > > > > ---- email begin > > > From: "Russell J. Yount" > > > 07/28/00 12:30 > > > Subject: CMU software releases > > > To: klingle@cisco.com > > > > > > kevin, > > > At the current time we have no developers working on it. > > > We have lost a greate deal of staff over recent years to > > > outside companies, > > > and as such have drop development of this. > > > > > > -Russ > > > > > > Russell J. Yount > > > Manager of Network Development > > > Carnegie Mellon University > > > (412) 268-8391 > > > > > > ** > > > ** Initial Query From klingle@cisco.com > > > ** Thu, 13 Jul 2000 16:55:32 -0400 > > > ** To: dc0m@andrew.cmu.edu > > > ** > > > > > > Hi, > > > > > > Your web page http://www.net.cmu.edu/groups/netdev/snmpd.html > > > indicates that SET support is not available in your extensible > > > snmp agent. It further indicates that support is planned near term. > > > > > > Is set support available yet? > > > > > > All of your pages and your release history date back to 1998. > > > Is this project even active anymore?? Have there truely been > > > no updates to code or web since 1998?!?!? > > > > > > kevin > > > ---- email end > > > > > > Further if you look at the README from UCD-SNMP ver 4.1.2 you see > > > the following: > > > > > > "My snmp code, based on the CMU 2.1.2.1 version with a lot of > > > additions. It is fully extensible." > > > > > > Thus, I abandoned any consideration of CMU code and am opting for > > > UCD-SNMP. > > > > > > While I'm glad to hear of the successes you've had, I'm wondering > > > why you are even using the CMU code downloaded from their website > > > as it seems to be quite behind the times? > > > > > > Kevin > > > -- > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > =-=-=-=-= > > > Kevin R. Lingle 919.392.2029 > > > checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html > > > Sometimes I think I understand everything, then I regain > > > consciousness. > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > =-=-=-=-= > > > > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Kevin R. Lingle 919.392.2029 > checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html > Sometimes I think I understand everything, then I regain consciousness. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > From owner-agentx@dorothy.peer.com Tue Aug 29 11:39:27 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22779 for ; Tue, 29 Aug 2000 11:39:26 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7TFaXe11409; Tue, 29 Aug 2000 10:36:38 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA29409 for agentx-list; Tue, 29 Aug 2000 08:32:00 -0700 (PDT) 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 IAA29392 for ; Tue, 29 Aug 2000 08:31:51 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7TFVnQ09645 for ; Tue, 29 Aug 2000 10:31:49 -0500 (CDT) Received: from localhost (mwhite@localhost) by bacardi.torrentnet.com (8.10.2/8.10.2) with SMTP id e7SEpAJ23154 for ; Mon, 28 Aug 2000 10:51:10 -0400 (EDT) Date: Mon, 28 Aug 2000 10:51:10 -0400 (EDT) From: Matt White To: agentx@dorothy.peer.com Subject: RE: Fwd: Regarding Agentx In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list I'll pipe in and say that, even though there is no current development, that I'm relatively happy with the code I originally wrote. It's small and appears understandable by mere mortals. There are several things I would change internally, but aren't there always? Matt White Ericsson IP Infrastructure On Thu, 24 Aug 2000, Ayers, Mike wrote: > > > This issue also crossed the UCD-SNMP mailing list, where one of the > CMU AgentX developers also pointed out that there is currently no new > development. However, that thread had been started by someone who had used > CMU AgentX successfully, and it was agreed that within certain parameters, > CMU was useable. If there is interest, I can root through my archives and > post the thread. > > > /|/|ike > > > -----Original Message----- > > From: Kevin Lingle [mailto:klingle@cisco.com] > > Sent: Thursday, August 24, 2000 8:44 AM > > To: Daris A Nevil > > Cc: Bob Natale; agentx@dorothy.peer.com > > Subject: Re: Fwd: Regarding Agentx > > > > > > > > Daris A Nevil wrote: > > > > > > > > The version we started with was downloaded from: > > > > > > http://www.net.cmu.edu/groups/netdev/agentx/ > > > > So I take that to mean you downloaded ver 1.4.1 ?? > > > > I have been evaluating a few extensible agents and looked at CMU > > as well as UCD-SNMP. When I browsed the cmu website I notice > > that nothing seemed to be updated in a long time. I sent some > > email asking about current status and development activities. > > About two weeks later I got the following response: > > > > ---- email begin > > From: "Russell J. Yount" > > 07/28/00 12:30 > > Subject: CMU software releases > > To: klingle@cisco.com > > > > kevin, > > At the current time we have no developers working on it. > > We have lost a greate deal of staff over recent years to > > outside companies, > > and as such have drop development of this. > > > > -Russ > > > > Russell J. Yount > > Manager of Network Development > > Carnegie Mellon University > > (412) 268-8391 > > > > ** > > ** Initial Query From klingle@cisco.com > > ** Thu, 13 Jul 2000 16:55:32 -0400 > > ** To: dc0m@andrew.cmu.edu > > ** > > > > Hi, > > > > Your web page http://www.net.cmu.edu/groups/netdev/snmpd.html > > indicates that SET support is not available in your extensible > > snmp agent. It further indicates that support is planned near term. > > > > Is set support available yet? > > > > All of your pages and your release history date back to 1998. > > Is this project even active anymore?? Have there truely been > > no updates to code or web since 1998?!?!? > > > > kevin > > ---- email end > > > > Further if you look at the README from UCD-SNMP ver 4.1.2 you see > > the following: > > > > "My snmp code, based on the CMU 2.1.2.1 version with a lot of > > additions. It is fully extensible." > > > > Thus, I abandoned any consideration of CMU code and am opting for > > UCD-SNMP. > > > > While I'm glad to hear of the successes you've had, I'm wondering > > why you are even using the CMU code downloaded from their website > > as it seems to be quite behind the times? > > > > Kevin > > -- > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > =-=-=-=-= > > Kevin R. Lingle 919.392.2029 > > checkout: http://wwwin-eng.cisco.com/Eng/IOS/SNMP_WWW/mib-police.html > > Sometimes I think I understand everything, then I regain > > consciousness. > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > =-=-=-=-= > > > From owner-agentx@dorothy.peer.com Tue Aug 29 11:50:53 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23178 for ; Tue, 29 Aug 2000 11:50:52 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7TFaXB11407; Tue, 29 Aug 2000 10:36:38 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA29408 for agentx-list; Tue, 29 Aug 2000 08:31:59 -0700 (PDT) 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 IAA29393 for ; Tue, 29 Aug 2000 08:31:52 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7TFVn609649 for ; Tue, 29 Aug 2000 10:31:49 -0500 (CDT) Received: from localhost (mwhite@localhost) by bacardi.torrentnet.com (8.10.2/8.10.2) with SMTP id e7SEhT721422; Mon, 28 Aug 2000 10:43:30 -0400 (EDT) Date: Mon, 28 Aug 2000 10:43:29 -0400 (EDT) From: Matt White To: Daris A Nevil cc: Bob Natale , agentx@dorothy.peer.com Subject: Re: Fwd: Regarding Agentx In-Reply-To: <39A3F7C5.738BD16E@snmc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list On Wed, 23 Aug 2000, Daris A Nevil wrote: > One thing that the AgentX package needs is a thoroughly cleaned and > updated documentation package. There are comments in the release > notes that say things like: > > * Set is not supported > * TCP is not supported > * Getbulk is not supported > > >From what we have seen all of these features are supported by the > current version of CMU AgentX. It appears to be complete. Yeah, I do believe I implemented SET and GETBULK before I left. I don't think I did agent capabilities and I know TCP is not supported by the subagent library (though the master agent does have the ability to accept TCP AgentX connections). -Matt From owner-agentx@dorothy.peer.com Tue Aug 29 14:45: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 ESMTP id OAA28388 for ; Tue, 29 Aug 2000 14:45:44 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7TIbGg19271; Tue, 29 Aug 2000 13:37:16 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA02433 for agentx-list; Tue, 29 Aug 2000 11:34:47 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA02427; Tue, 29 Aug 2000 11:34:44 -0700 (PDT) Date: Tue, 29 Aug 2000 11:34:44 -0700 (PDT) From: Randy Presuhn Message-Id: <200008291834.LAA02427@dorothy.bmc.com> To: vb@lycos.com Subject: Re: Query regarding Agent-X Cc: agentx@dorothy.peer.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 8bit Hi - I'm forwarding your post to the agentx working group mailing list. I've unblocked mailcity.com here, so you should now be able to subscribe, unless it's also being blocked by our firewalls. (In the long run, you might be better off subscribing from another domain; I suspect some of the mailing list subscribers' systems will also bounce traffic from mailcity.com addresses.) ------------------------------------------------------- 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 vb@lycos.com Tue Aug 29 10:38:47 PDT 2000 > To: randy_presuhn@bmc.com > Date: Tue, 29 Aug 2000 10:34:33 -0700 > From: "Venkatesh B" > Message-ID: > X-Sent-Mail: off > Reply-To: vb@lycos.com > X-Expiredinmiddle: true > Subject: Query regarding Agent-X > X-Sender-Ip: 216.85.115.83 > Organization: Lycos Communications (http://comm.lycos.com:80) > Content-Language: en > > Hello Mr Presuhn, > I had a query regarding the use of Agent-X for one of my assignments. I tried to subscribe to AgentX mailing group, but failed in my attempt(probably because of my mailcity account). I would be very grateful if you could answer my question(please see the text below), or provide indicators to the solution. > > Thanks for your precious time, > With best regards, > Venkatesh Babu. > > I have a bunch of devices of different types. A few of these already have SNMP agent implementations. I have to provide SNMP support for the rest. Each of these devices is IP_Addressable by itself. > > I am in the process of integrating these devices into a single container. At this point I have the option of giving a integrated management view of these devices and I would like to do it. > > Since my application is a multi-component system that requires management(preferably integrated), I thought Agentx might help. Does my application warrant the use of AgentX. I ask this question because > > 1)these devices even after integration, will not be a single IP_Addressable entity but will each have one for itself. > 2)few of these already have agents written for them and it will not be possible for me to rewrite their agents. I can write sub-agents for a couple of components which do not have SNMP agents in them. > > If Agentx is a right way, how do I go about tackling the components that already have agents written for them(how do I make them subagents). > If Agentx is not the right approach, what other alternatives do I have using which I can provide this integrated management view. > > > > > Get your FrEE Email and Voicemail at Lycos Communications at ^ changed to get past spam filter > http://comm.lycos.com > From owner-agentx@dorothy.peer.com Wed Aug 30 13:41:23 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 ESMTP id NAA05562 for ; Wed, 30 Aug 2000 13:41:23 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7UHXnu21357; Wed, 30 Aug 2000 12:33:49 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA07354 for agentx-list; Wed, 30 Aug 2000 10:29:26 -0700 (PDT) Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA07349 for ; Wed, 30 Aug 2000 10:29:22 -0700 (PDT) Received: from ec03-hou.bmc.com (ec03-hou.bmc.com [172.20.4.32]) by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e7UHU0d03593; Wed, 30 Aug 2000 12:30:00 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21) id ; Wed, 30 Aug 2000 12:31:49 -0500 Message-ID: From: "Ayers, Mike" To: Kevin Lingle Cc: agentx@dorothy.peer.com Subject: RE: Fwd: Regarding Agentx Date: Wed, 30 Aug 2000 12:31:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Since Matt has stepped in (he is the authority after all), there is little more for me to say on the subject. However, I will repost one of his responses to the UCD-SNMP group, as well as Dave Shield's reply to the same query (both reposted without headers 'cause I'm stuck with Outlook). Hopefully, this (and what has been discussed here so far) will give you everything you need. /|/|ike =======8<------From Matt White 16Aug00--------------- Doesn't look like there's been a release of the CMU AgentX code since I left CMU (and stopped developing it) a year ago. My informal discussions with people at CMU indicate that they do not have the resources to continue development on this code at this time. That may change in the future, but these things are hard to judge. So, if the CMU code as it stands right now does what you want, you're in good shape, otherwise you should go with the UCD code. Or you can use both. The last I checked, there was interoperability between the two versions. Weaknesses in the CMU code: * The CMU master agent does not support SNMPv3 and won't for some time, if ever. * The CMU subagent library and master agent don't support agent capabilities or notifications. * There is no subagent MIB compiler for the CMU subagent. It's been a while since I've looked at this code, but I think those are the biggies. If it were me, I would probably use the UC Davis code. Matt White Ericsson IP Infrastructure On Thu, 10 Aug 2000, Qing Zhang wrote: > > Good Morning, > > I am currently evaluating public domain AgentX implementation. > > I got CMU AgentX compiled and I can run snmpd and the test program. > Seems the basic features are working. > > I planned to try the UCD AgentX implementation. > > Before I dive into the UCD AgentX, I would like to get some feedbacks > from people who have used it. More specifically, I would like to know > the followings regarding both CMU and UCD AgentX: > > - Features missed; > - Major bugs; > - Weakness; > - etc. > > Any comments are extremely welcome. Thanks in advance. > > -- > Senior Software Designer, Motorola Canada Ltd. > qzhang@ipsg.mot.com, Tel: (604) 241-6422 > > > =======8<-------------------------------------------- =======8<------From Dave Shield 11Aug00-------------- > I am currently evaluating public domain AgentX implementation. > > I got CMU AgentX compiled and I can run snmpd and the test program. > Seems the basic features are working. > > I planned to try the UCD AgentX implementation. > > Before I dive into the UCD AgentX, I would like to get some feedbacks > from people who have used it. OK - I'll have a go at responding. Note that it's a little while since I last looked at the CMU AgentX work, so some of my comments may be out of date. The CMU and UCD teams have been approaching this from somewhat different directions. My impression of the CMU package is that it's starting from the client side, and has developed a library for instrumenting an external application. The CMU master agent is deliberately an "empty shell" - that simply delegates requests down to subagent (i.e instrumented applications). These applications are therefore reasonably "AgentX-aware". The UCD approach has been the reverse - starting from the agent and turning an SNMP-only agent into a dual-role system. The support for an instrumented application is effectively a very stripped down version of this. This has an number of implications, not least that applications are much less "AgentX-aware" (The agent-handling code is fully contained within library routines, and the instrumentation API is protocol-independent, since it's the same as is used for the main UCD agent). Other comparisons that spring to mind: - the CMU code is probably lighter than the UCD equivalent, since this is designed for this specific requirement, rather than being an incremental development of an existing SNMP library. - the UCD master agent is "fuller" than the CMU equivalent. Particularly with regard to such things as access-control, SNMP statistics, trap notifications, etc - all of which can most sensibly be handled by the master agent itself. - the CMU code is somewhat more stable than the UCD implemention. The current UCD version (4.1.2) was the first public release of the AgentX code, and is very much "experimental". This support has developed a fair deal since then, and the current development version is notably more reliable and functional than the 4.1.2 code. - the UCD code is rather more up-to-date than the CMU offering. The last comments on the CMU web page are from 1998 (though the latest code appears to date from July 1999). I haven't looked at the 1.4 versions, but the 1.3 release was certainly built on the previous version of the AgentX protocol. The current versions is subtly different in certain respects (which may lead to some problems with interoperability). - the UCD code is rather more complete that the CMU version. Again, this is w.r.t the 1.3 CMU release, but that didn't implement certain of the AgentX protocol operations. This may have been addressed with 1.4 - I haven't looked. The UCD offering does attempt to handle the full AgentX protocol (including index allocation, ping, etc). Which isn't to claim there aren't any problems, but the basic support is there. These aren't the only two options, of course. I know that the Agent++ people have been working on AgentX support, and I believe the Advent agent also includes this facility. There may well be others. Anyway, I trust that these rambling have been both fair, and useful. Dave =======8<-------------------------------------------- From owner-agentx@dorothy.peer.com Wed Aug 30 16:04:40 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08271 for ; Wed, 30 Aug 2000 16:04:40 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7UJtLv20567; Wed, 30 Aug 2000 14:55:22 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA08335 for agentx-list; Wed, 30 Aug 2000 12:52:21 -0700 (PDT) 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 MAA08330 for ; Wed, 30 Aug 2000 12:52:17 -0700 (PDT) Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7UJqJe19525 for ; Wed, 30 Aug 2000 14:52:19 -0500 (CDT) Received: from world.std.com (ppp0c198.std.com [208.192.102.198]) by world.std.com (8.9.3/8.9.3) with ESMTP id HAA13081; Wed, 30 Aug 2000 07:47:33 -0400 (EDT) Message-ID: <39ACF241.9FEC274E@world.std.com> Date: Wed, 30 Aug 2000 07:38:42 -0400 From: Michael Daniele X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mibs@ops.ietf.org, agentx@dorothy.peer.com CC: Mike Daniele Subject: change of email address Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit hi, my new email address is as listed in the cc: above. compaq was supposed to set up an auto-reply for folks sending to my old address of daniele@zk3.dec.com, but it is not in place after almost 3 weeks. i still intend to stay active in these areas. regards, mike From owner-agentx@dorothy.peer.com Wed Aug 30 18:30:55 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10298 for ; Wed, 30 Aug 2000 18:30:54 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7UMOxH24479; Wed, 30 Aug 2000 17:24:59 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA09538 for agentx-list; Wed, 30 Aug 2000 15:23:47 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA09532 for agentx@dorothy.bmc.com; Wed, 30 Aug 2000 15:23:43 -0700 (PDT) Date: Wed, 30 Aug 2000 15:23:43 -0700 (PDT) From: Randy Presuhn Message-Id: <200008302223.PAA09532@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: Fwd: Announcement of AgentX++ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - I'm forwarding a non-subscriber post. (Frank keeps finding providers that bounce mail from this list. I hope this one is better. :-) ------------------------------------------------------- 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 PAA09423 > for ; Wed, 30 Aug 2000 15:10:24 -0700 (PDT) > Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1]) > by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e7UMATT22115 > for ; Wed, 30 Aug 2000 17:10:29 -0500 (CDT) > Received: from fwd05.sul.t-online.com > by mailout03.sul.t-online.com with smtp > id 13UG4b-0001SD-03; Thu, 31 Aug 2000 00:11:09 +0200 > Received: from fock.de (320061250925-0001@[62.224.96.23]) by fwd05.sul.t-online.com > with esmtp id 13UG4X-0Iq7l2C; Thu, 31 Aug 2000 00:11:05 +0200 > Message-ID: <39AD86C5.9508FD95@fock.de> > Date: Thu, 31 Aug 2000 00:12:21 +0200 > From: Frank.Fock@t-online.de (Frank Fock) > X-Mailer: Mozilla 4.5 [en] (WinNT; I) > X-Accept-Language: en > MIME-Version: 1.0 > To: agentx@dorothy.bmc.com > Subject: Announcement of AgentX++ > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > X-Sender: 320061250925-0001@t-dialin.net > > Hi, > > I would like to announce the final beta release of > AgentX++, the AgentX protocol implementation for > AGENT++. It can be downloaded from: > http://www.fock.de/agent++ > > AgentX++ v1.0 will be released during September. > > AgentX++ v1.0 final beta has the following features: > > * C++ API based on AGENT++/SNMP++ that > supports AgentX master and subagents. > > * Supports SNMPv1/v2c/v3 and the following > operating systems: > Solaris 7/8, Linux, Windows NT/2000 > > * Free for non-commercial use. > > * Supports all AgentX features including: > > - UNIX domain socket connections on UNIX > systems and TCP connections on UNIX and > Windows NT > - non-default contexts > - shared tables > - uses AgentX GETBULK > - AgentX request timeout handling > - AgentX MIB > - atomic SET requests > > * Existing AGENT++ agents may be migrated to > an AgentX master or subagent without changing > the management instrumentation. > > Any comments, suggestions, and bug reports are > highly appreciated. > > Regards, > Frank Fock > > From owner-agentx@dorothy.peer.com Wed Aug 30 19:00:23 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10690 for ; Wed, 30 Aug 2000 19:00:23 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e7UMo2S28325; Wed, 30 Aug 2000 17:50:03 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA09847 for agentx-list; Wed, 30 Aug 2000 15:49:03 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA09831 for agentx@dorothy.bmc.com; Wed, 30 Aug 2000 15:48:59 -0700 (PDT) Date: Wed, 30 Aug 2000 15:48:59 -0700 (PDT) From: Randy Presuhn Message-Id: <200008302248.PAA09831@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: Re: Query regarding Agent-X Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 8bit Hi - > To: randy_presuhn@bmc.com > Date: Tue, 29 Aug 2000 10:34:33 -0700 > From: "Venkatesh B" > Message-ID: > Subject: Query regarding Agent-X ... > I have a bunch of devices of different types. A few of these already have SNMP agent implementations. I have to provide SNMP support for the rest. Each of these devices is IP_Addressable by itself. > > I am in the process of integrating these devices into a single container. At this point I have the option of giving a integrated management view of these devices and I would like to do it. > > Since my application is a multi-component system that requires management(preferably integrated), I thought Agentx might help. Does my application warrant the use of AgentX. I ask this question because > > 1)these devices even after integration, will not be a single IP_Addressable entity but will each have one for itself. > 2)few of these already have agents written for them and it will not be possible for me to rewrite their agents. I can write sub-agents for a couple of components which do not have SNMP agents in them. > > If Agentx is a right way, how do I go about tackling the components that already have agents written for them(how do I make them subagents). > If Agentx is not the right approach, what other alternatives do I have using which I can provide this integrated management view. ... It really depends on the extent to which you need to manage it as though it were a single system. For example, if these IP- addressable entities are cards in a larger box, then agentx may be a very reasonable solution. The problem of integrating legacy SNMP agents in such a configuration is tricky, since all the complications of proxies can arise, and a meaningful access control policy may be precluded by security holes in those legacy agents. For more background on the motivations for AgentX, please see http://www.simple-times.org/pub/simple-times/issues/4-2.html It might be worth your while to take a look at some of the related work going on in the IETF in these working groups: http://www.ietf.org/html.charters/disman-charter.html http://www.ietf.org/html.charters/snmpconf-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. ------------------------------------------------------- From owner-agentx@dorothy.peer.com Thu Aug 31 21:39:05 2000 Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16539 for ; Thu, 31 Aug 2000 21:39:05 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e811c8X07510; Thu, 31 Aug 2000 20:38:09 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA20002 for agentx-list; Thu, 31 Aug 2000 18:32:26 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA19996 for agentx@dorothy.bmc.com; Thu, 31 Aug 2000 18:32:23 -0700 (PDT) Date: Thu, 31 Aug 2000 18:32:23 -0700 (PDT) From: Randy Presuhn Message-Id: <200009010132.SAA19996@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: agentx mailing list test, please ignore Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit please ignore