From owner-agentx@dorothy.bmc.com Sat May 5 11:26:46 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16006 for ; Sat, 5 May 2001 11:26:46 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f45FKop18647; Sat, 5 May 2001 10:20:50 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA11388 for agentx-list; Sat, 5 May 2001 08:11:13 -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 IAA11383 for ; Sat, 5 May 2001 08:11:09 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f45FC7X24774 for ; Sat, 5 May 2001 10:12:07 -0500 (CDT) Received: from hoemail1.lucent.com ([192.11.226.161]) by fw-us-hou-9.bmc.com; Sat, 05 May 2001 10:12:12 +0000 (CST) Received: from hoemail1.firewall.lucent.com (localhost [127.0.0.1]) by hoemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f45FCBU14076 for ; Sat, 5 May 2001 11:12:11 -0400 (EDT) Received: from md6370exch001p.wins.lucent.com (h135-114-206-50.lucent.com [135.114.206.50]) by hoemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f45FCB714072 for ; Sat, 5 May 2001 11:12:11 -0400 (EDT) Received: by md6370exch001p.nse.lucent.com with Internet Mail Service (5.5.2650.21) id ; Sat, 5 May 2001 11:12:10 -0400 Message-ID: From: "Natale, Robert C (Bob)" To: AgentX@dorothy.bmc.com Subject: AgentX charter page updated Date: Sat, 5 May 2001 11:12:03 -0400 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.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Hi, I just wanted to let you all know that the WG's web page at http://www.ietf.org/html.charters/agentx-charter.html as been officially updated to reflect the new set of milestones we discussed several weeks ago and to show current progress. We have so far received three implementation reports -- two posted to the list and one to me privately. I am hereby reminding all implementers who have not yet reported to not let this slide too far. Our goal is to finish collecting, summarizing, and assessing the implementation and interoperability results by the end of this month, with the bulk of next spent in making any (hopefully minor) mods to the specs and deciding on the next-step recommendations to the IESG. I will be distributing the interoperability report solicitation over the weekend. This is targeted mainly toward people who have used AgentX components but who did not necessarily implement them. Of course, implementers may fall into both categories. Thanks, BobN From owner-agentx@dorothy.bmc.com Tue May 8 11:31:29 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27498 for ; Tue, 8 May 2001 11:31:28 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f48FL7L27930; Tue, 8 May 2001 10:21:07 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA14442 for agentx-list; Tue, 8 May 2001 08:13:04 -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 IAA14435 for ; Tue, 8 May 2001 08:12:59 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f48FDt726622 for ; Tue, 8 May 2001 10:13:55 -0500 (CDT) Received: from fe5.southeast.rr.com ([24.93.67.52]) by fw-us-hou-9.bmc.com; Tue, 08 May 2001 10:13:56 +0000 (CST) Received: from fink03 ([66.61.39.181]) by mail5.mgfairfax.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Tue, 8 May 2001 11:12:51 -0400 From: "Nancy Fink" To: Cc: Subject: AgentX Implementation Report Date: Tue, 8 May 2001 11:12:14 -0400 Message-ID: <000201c0d7d1$44ca9e00$0201a8c0@fink03> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit AgentX Implementation Report Report date: ___May 8, 2001____________________________________ Submitted by: ____Nancy Fink____________________________________ Organization: ___COMTEK Services, Inc.__________________________ E-mail address: __Nancy.Fink@comtekservices.com___________________ Implementation name: __NMServer for OpenVMS____________________________ Implementation type: ___ Master and/or _x_ Sub-Agent and/or ___ Toolkit Runtime platform(s): __OpenVMS VAX or Alpha____________________________ Reported version id: __3.4_____________________________________________ If Master Agent, did you implement: SNMPv1 support in master agent: ___ Yes ___ No Comments: SNMPv2c support in master agent: ___ Yes ___ No Comments: SNMPv3 support in master agent: ___ Yes ___ No Comments: If Sub-Agent, what MIB(s) did you implement: COMTEK-DEFINITIONS-MIB COMTEK-SUBAGENT-MIB COMTEK-VMS-NM-SYSMGR-MIB COMTEK-VMS-NM-SYSMGR-TRAP-MIB COMTEK-VMS-NM-TRPMGR-MIB COMTEK-VMS-NM-TRPMGR-TRAP-MIB COMTEK-VMS-NM-CONSOLE-MIB COMTEK-VMS-NM-CONSOLE-TRAP-MIB COMTEK-VMS-NM-VMS-MONITOR-MIB COMTEK-VMS-MONITOR-SUBAGENT-MIB COMTEK-VMS-NM-OPCOM-MIB Comments: NMServer is a set of system management subagents for OpenVMS. Electronic copies of implemented MIBs are available at http://www.comtekservices.com/vms_downloadintro.htm. All MIBs implemented are private MIBs, no standard MIBs were implemented. There were a total of 5 subagents implemented, with each subagent registering more than one MIB. (Please identify each specific MIB.) If Toolkit, please identify: Development languages supported: Comments: Development platforms supported: Comments: Runtime platforms supported: OpenVMS v5.5+ VAX or Alpha Comments: For all implementations: Did you implement the following PDU types: Note: Subagents were developed using the subagent toolkit from a TCP/IP vendor, therefore the actual PDUs are not visible to the subagents. agentx-Open-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: agentx-Close-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: agentx-Register-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: agentx-Unregister-PDU: ___ Yes _x__ No, but plan to within ___ months Comments: agentx-Get-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: agentx-GetNext-PDU: _x__ Yes ___ No, but plan to within ___ months Comments: agentx-GetBulk-PDU: ___ Yes _x__ No, but plan to within ___ months Comments: agentx-TestSet-PDU: _x__ Yes ___ No, but plan to within ___ months Comments: agentx-Commit-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: agentx-Set-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-UndoSet-PDU: _x__ Yes ___ No, but plan to within ___ months Comments: agentx-CleanupSet-PDU: _x__ Yes ___ No, but plan to within ___ months Comments: agentx-Notify-PDU: _x__ Yes ___ No, but plan to within ___ months Comments: agentx-Ping-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: agentx-IndexAllocate-PDU: ___ Yes _x_ No, but plan to within ___ months Comments: agentx-IndexDeallocate-PDU: ___ Yes _x_ No, but plan to within ___ months Comments: agentx-AddAgentCaps-PDU: ___ Yes _x_ No, but plan to within ___ months Comments: agentx-RemoveAgentCaps-PDU: ___ Yes _x_ No, but plan to within ___ months Comments: agentx-Response-PDU: _x_ Yes ___ No, but plan to within ___ months Comments: Does this implementation have interoperability experience with at least one other independent implementation with respect to: Registration operations: _x_ Yes ___ No, but plan to within ___ months Comments: Registration priorities: ___ Yes _x_ No, but plan to within ___ months Comments: Index allocation operations: ___ Yes _x_ No, but plan to within ___ months Comments: Index deallocation operations: ___ Yes _x_ No, but plan to within ___ months Comments: Multiple sub-agent connections: ___ Yes ___ No, but plan to within ___ months Comments: Connecting sub-agent(s) to multiple master agents: ___ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection of sub-agent(s): ___ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection with master agent(s): _x_ Yes ___ No, but plan to within ___ months Comments: What transport mappings did you implement: TCP/IP on port 705: _x_ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on "/var/agentx/master": ___ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on other endpoints: ___ Yes ___ No, but plan to within ___ months Comments: Other(s): ___ Yes ___ No, but plan to within ___ months Comments: (Please indicate at least type(s) and connection specifics.) Did you implement the AgentX MIB (RFC2742): ___ Yes _x_ No, but plan to within ___ months Comments: Did you satisfy the agentxMIBCompliance MODULE-COMPLIANCE requirements:: ___ Yes ___ No, but plan to within ___ months Comments: Did you implement the MIB as an integral part of the master agent: ___ Yes ___ No Comments: Did you implement the MIB in an AgentX sub-agent: ___ Yes ___ No Comments: Please record any other comments or notes you deem useful for the record: Comments: This may not be a true AgentX subagent implementation because the subagents use a subagent toolkit that insulates them from the particulars of the protocol. The subagent toolkit that was used to build these subagents comes with Compaq's TCP/IP Services v5.1 for OpenVMS. These subagents operate with the following AgentX master agents: TCP/IP Services v5.1 (Compaq), MultiNet v4.3 (Process Software) and TCPware v5.5 (Process Software). These subagents also coexist with Compaq's Insight Management Agents and other subagents provided with the various TCP products. Because of their long history, these subagents may also be used with eSNMP and DPI master agents (a DPI master agent is provided with the product). From owner-agentx@dorothy.bmc.com Tue May 8 11:34:00 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27636 for ; Tue, 8 May 2001 11:33:59 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f48FX4m29206; Tue, 8 May 2001 10:33:04 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA14493 for agentx-list; Tue, 8 May 2001 08:30: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 IAA14488 for ; Tue, 8 May 2001 08:30:24 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f48FVK608355 for ; Tue, 8 May 2001 10:31:20 -0500 (CDT) Received: from zcamail04.zca.compaq.com ([161.114.32.104]) by fw-us-hou-9.bmc.com; Tue, 08 May 2001 10:31:21 +0000 (CST) Received: by zcamail04.zca.compaq.com (Postfix, from userid 12345) id 83F171B8; Tue, 8 May 2001 08:30:49 -0700 (PDT) Received: from mailrelay01.cce.cpqcorp.net (mailrelay01.cce.cpqcorp.net [16.47.68.171]) by zcamail04.zca.compaq.com (Postfix) with ESMTP id 46AB6495; Tue, 8 May 2001 08:30:45 -0700 (PDT) Received: by mailrelay01.cce.cpqcorp.net (Postfix, from userid 12345) id 3C4E866A; Tue, 8 May 2001 10:29:01 -0500 (CDT) Received: from kitche.zk3.dec.com (kitche2.zk3.dec.com [16.140.160.162]) by mailrelay01.cce.cpqcorp.net (Postfix) with ESMTP id C8A102A2; Tue, 8 May 2001 10:29:00 -0500 (CDT) Received: from zk3.dec.com by kitche.zk3.dec.com (8.9.3/1.1.27.5/27Oct00-1235PM) id LAA0001572471; Tue, 8 May 2001 11:28:56 -0400 (EDT) Message-ID: <3AF810CE.D2472D53@zk3.dec.com> Date: Tue, 08 May 2001 11:29:18 -0400 From: Michael Daniele X-Mailer: Mozilla 4.72 [en] (X11; I; OSF1 V5.1 alpha) X-Accept-Language: en MIME-Version: 1.0 To: Bob.Natale@AppliedSNMP.com Cc: agentx@dorothy.bmc.com Subject: AgentX implementation report: Compaq Tru64 UNIX Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Report date: 05/08/01 Submitted by: Michael Daniele Organization: Compaq Computer Corporation E-mail address: daniele@zk3.dec.com, md@world.std.com Implementation name: Compaq Tru64 UNIX Implementation type: _X__ Master and/or _X__ Sub-Agent and/or _X__ Toolkit Runtime platform(s): Tru64 UNIX V5.0 and later Reported version id: If Master Agent, did you implement: SNMPv1 support in master agent: _X__ Yes ___ No Comments: SNMPv2c support in master agent: _X__ Yes ___ No Comments: SNMPv3 support in master agent: ___ Yes _X__ No Comments: If Sub-Agent, what MIB(s) did you implement: RFCs 1213, 1231, 1285, 1514, 2011, 2012, 2013, 2358, 1907, 2742, and many enterprise-specific MIBs Comments: These of course were existing implementations (except for 2742, the AgentX MIB). (Please identify each specific MIB.) If Toolkit, please identify: Development languages supported: C Comments: Development platforms supported: Tru64 UNIX Comments: Runtime platforms supported: Tru64 UNIX Comments: For all implementations: Did you implement the following PDU types: agentx-Open-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Close-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Register-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Unregister-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Get-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-GetNext-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-GetBulk-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-TestSet-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Commit-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Set-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-UndoSet-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-CleanupSet-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Notify-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Ping-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-IndexAllocate-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-IndexDeallocate-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-AddAgentCaps-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-RemoveAgentCaps-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: agentx-Response-PDU: _X__ Yes ___ No, but plan to within ___ months Comments: Does this implementation have interoperability experience with at least one other independent implementation with respect to: Registration operations: _X__ Yes ___ No, but plan to within ___ months Comments: Registration priorities: _X__ Yes ___ No, but plan to within ___ months Comments: Index allocation operations: ___ Yes _X__ No, but plan to within ___ months Comments: Index deallocation operations: ___ Yes _X__ No, but plan to within ___ months Comments: Multiple sub-agent connections: _X__ Yes ___ No, but plan to within ___ months Comments: Connecting sub-agent(s) to multiple master agents: ___ Yes _X__ No, but plan to within ___ months Comments: If you mean connecting a subagent, concurrently, to multiple master agents, then "no". But how is that germane to AgentX? Detecting loss of connection of sub-agent(s): _X__ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection with master agent(s): _X__ Yes ___ No, but plan to within ___ months Comments: What transport mappings did you implement: TCP/IP on port 705: _X__ Yes ___ No, but plan to within ___ months Comments: Only when built for testing, not enabled in shipping product. UNIX Domain Sockets on "/var/agentx/master": _X__ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on other endpoints: ___ Yes _X__ No, but plan to within ___ months Comments: Other(s): ___ Yes ___ No, but plan to within ___ months Comments: (Please indicate at least type(s) and connection specifics.) Did you implement the AgentX MIB (RFC2742): _X__ Yes ___ No, but plan to within ___ months Comments: Did you satisfy the agentxMIBCompliance MODULE-COMPLIANCE requirements:: _X__ Yes ___ No, but plan to within ___ months Comments: Did you implement the MIB as an integral part of the master agent: _X__ Yes ___ No Comments: Did you implement the MIB in an AgentX sub-agent: _X__ Yes ___ No Comments: This question and the one above are too loosely worded. Please record any other comments or notes you deem useful for the record: Comments: This implementation has interoperated at various times and with varying degrees of success with CMU/AgentX Peer/BMC Epilogue/ISI SNMP Research Based on our Tru64 UNIX experience alone, I do not feel we accomplished the breadth of testing needed to warrant advancing the RFC to draft status. I do not feel there are any issues in the specification itself to prevent advancement. I am only saying that I personally have not done sufficiently complete testing to make the assertion that it should advance. This is a result of scheduling issues, and of the various implementations being incomplete at the time of testing. From owner-agentx@dorothy.bmc.com Tue May 8 13:05:00 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01765 for ; Tue, 8 May 2001 13:05:00 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f48H4Ha07824; Tue, 8 May 2001 12:04:17 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA17289 for agentx-list; Tue, 8 May 2001 10:01: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 KAA17280 for ; Tue, 8 May 2001 10:01:24 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f48H2Kr23757 for ; Tue, 8 May 2001 12:02:20 -0500 (CDT) Received: from mumm.ibr.cs.tu-bs.de ([134.169.34.190]) by fw-us-hou-9.bmc.com; Tue, 08 May 2001 12:02:31 +0000 (CST) Received: from hansa.ibr.cs.tu-bs.de (IDENT:root@hansa [134.169.34.137]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id TAA28105; Tue, 8 May 2001 19:02:29 +0200 (MET DST) Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.9.3/8.9.3) id TAA24774; Tue, 8 May 2001 19:02:29 +0200 X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: strauss set sender to strauss@ibr.cs.tu-bs.de using -f From: Frank Strauss Subject: AgentX implementation report: JAX toolkit To: Bob.Natale@AppliedSNMP.com Cc: agentx@dorothy.bmc.com Date: 08 May 2001 19:02:29 +0200 Message-ID: Lines: 104 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 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 Hi! Here's a tight implementation report on the open source JAX toolkit. I've removed those fields, that would be left empty otherwise. The order and format of all remaining fields is unchanged. -frank Report date: 08-May-2001 Submitted by: Frank Strauss Organization: TU Braunschweig E-mail address: strauss@ibr.cs.tu-bs.de Implementation name: JAX Implementation type: ___ Master and/or ___ Sub-Agent and/or _X_ Toolkit Runtime platform(s): Java (plus a MIB compiler driver in C (UNIX, W32, ...)) Reported version id: 0.0.10 If Toolkit, please identify: Development languages supported: Java Comments: Stub classes and implementation class templates can be generated by a MIB compiler. This MIB compiler is not part of the JAX distribution itself, but of the libsmi distribution. Libsmi is not written in Java, but C with GNU configure stuff, so that it is also very portable. Development platforms supported: any JDK Runtime platforms supported: any JRE For all implementations: Did you implement the following PDU types: agentx-Open-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Close-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Register-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Unregister-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Get-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-GetNext-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-GetBulk-PDU: ___ Yes _X_ No, but plan to within ___ months agentx-TestSet-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Commit-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Set-PDU: ___ Yes ___ No, but plan to within ___ months agentx-UndoSet-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-CleanupSet-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Notify-PDU: _X_ Yes ___ No, but plan to within ___ months agentx-Ping-PDU: ___ Yes _X_ No, but plan to within ___ months Comments: To be precise, a sub-agent implementor can instantiate and emit a Ping PDU, but the receiption of the response would not be handled accordingly. agentx-IndexAllocate-PDU: ___ Yes _X_ No, but plan to within ___ months agentx-IndexDeallocate-PDU: ___ Yes _X_ No, but plan to within ___ months agentx-AddAgentCaps-PDU: ___ Yes _X_ No, but plan to within ___ months agentx-RemoveAgentCaps-PDU: ___ Yes _X_ No, but plan to within ___ months agentx-Response-PDU: _X_ Yes ___ No, but plan to within ___ months Does this implementation have interoperability experience with at least one other independent implementation with respect to: Registration operations: _X_ Yes ___ No, but plan to within ___ months Comments: We used (only) the NET-SNMP master agent. We had problems registering sub-id ranges with the master. We tried to use it to allow multiple sub-agents to register separate rows within a common table. Registration priorities: ___ Yes _X_ No, but plan to within ___ months Index allocation operations: ___ Yes _X_ No, but plan to within ___ months Index deallocation operations: ___ Yes _X_ No, but plan to within ___ months Connecting sub-agent(s) to multiple master agents: ___ Yes _X_ No, but plan to within ___ months Detecting loss of connection with master agent(s): ___ Yes _X_ No, but plan to within ___ months What transport mappings did you implement: TCP/IP on port 705: _X_ Yes ___ No, but plan to within ___ months UNIX Domain Sockets on "/var/agentx/master": ___ Yes _X_ No, but plan to within ___ months Comments: Java does not support UNIX domain sockets. UNIX Domain Sockets on other endpoints: ___ Yes _X_ No, but plan to within ___ months Comments: Java does not support UNIX domain sockets. Other(s): ___ Yes _X_ No, but plan to within ___ months Did you implement the AgentX MIB (RFC2742): ___ Yes _X_ No, but plan to within ___ months Please record any other comments or notes you deem useful for the record: Comments: Our overall experience with JAX is quite limited, since its more or less a by-product of another Open Source project. However, we had 350+ JAX downloads so far without too many complains on our mailinglist. ;-) From owner-agentx@dorothy.bmc.com Fri May 11 10:48:26 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11813 for ; Fri, 11 May 2001 10:48:25 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f4BElr419118; Fri, 11 May 2001 09:47:53 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id HAA04994 for agentx-list; Fri, 11 May 2001 07:43:14 -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 HAA04989 for ; Fri, 11 May 2001 07:43:05 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f4BEi1c27704 for ; Fri, 11 May 2001 09:44:01 -0500 (CDT) Received: from mailhub2.liv.ac.uk ([138.253.100.95]) by fw-us-hou-9.bmc.com; Fri, 11 May 2001 09:44:13 +0000 (CST) Received: from ribble.server.csc.liv.ac.uk ([138.253.124.242]) by mailhub2.liv.ac.uk with esmtp (Exim 3.22 #1) id 14yE6U-0002Dy-00; Fri, 11 May 2001 15:41:14 +0100 Received: from daves.staff.csc.liv.ac.uk (IDENT:root@daves.staff.csc.liv.ac.uk [138.253.124.36]) by ribble.server.csc.liv.ac.uk (8.9.3 (PHNE_22672)/LUCS-DTS-3.0M10) with ESMTP id PAA27729; Fri, 11 May 2001 15:41:10 +0100 (BST) Received: from daves.staff.csc.liv.ac.uk (daves@localhost [127.0.0.1]) by daves.staff.csc.liv.ac.uk (8.8.7/LUCS-DTS-3.0D9) with ESMTP id PAA20622; Fri, 11 May 2001 15:39:28 +0100 Message-Id: <200105111439.PAA20622@daves.staff.csc.liv.ac.uk> X-Mailer: exmh version 2.0.2 To: Bob.Natale@AppliedSNMP.com cc: agentx@dorothy.bmc.com Subject: AgentX implementation report: {UCD,Net}-SNMP Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 May 2001 15:39:27 +0100 From: Dave Shield Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Just squeezing in before the "Desired due date". Sorry for cutting it so fine! Dave AgentX Implementation Report Report date: 10th May 2001 __________________________________ Submitted by: Dave Shield ___________________________________ Organization: Net-SNMP project ______________________________ E-mail address: _______ Implementation name: ucd-snmp (also known as net-snmp) ____________ Implementation type: X Master and/or X Sub-Agent and/or (X) Toolkit Runtime platform(s): Linux, *BSD, Solaris, HP-UX, etc ______________ Reported version id: 4.2.1 _______________________________________ If Master Agent, did you implement: SNMPv1 support in master agent: X Yes ___ No SNMPv2c support in master agent: X Yes ___ No SNMPv3 support in master agent: X Yes ___ No If Sub-Agent, what MIB(s) did you implement: MIB-2, Host Resources, UCD-specifics Comments: The AgentX support was added to an existing agent, so all prior MIBs were immediately available as AgentX subagent(s). If Toolkit, please identify: Development languages supported: C Comments: It is possible to use the libraries as an AgentX toolkit, to instrument external applications, but the API is not currently as cleanly defined as we would like. Development platforms supported: Linux, *BSD, Solaris, HP-UX, etc Comments: Should work on most Unix-style platforms Also reported to work on Windows Runtime platforms supported: Linux, *BSD, Solaris, HP-UX, etc Comments: Should work on most Unix-style platforms Also reported to work on Windows For all implementations: Did you implement the following PDU types: agentx-Open-PDU: X Yes ___ No, but plan to within ___ months Comments: Contexts not supported by master or subagent framework agentx-Close-PDU: X Yes ___ No, but plan to within ___ months agentx-Register-PDU: X Yes ___ No, but plan to within ___ months Comments: Range registrations currently not handled correctly. It is intended to correct this - hopefully for the next release agentx-Unregister-PDU: X Yes ___ No, but plan to within ___ months agentx-Get-PDU: X Yes ___ No, but plan to within ___ months agentx-GetNext-PDU: X Yes ___ No, but plan to within ___ months agentx-GetBulk-PDU: X Yes ___ No, but plan to within ___ months Comments: Master agent never generates GetBulk requests, but uses GetNext instead. Subagent handles GetBulk OK. agentx-TestSet-PDU: X Yes ___ No, but plan to within ___ months agentx-CommitSet-PDU: X Yes ___ No, but plan to within ___ months agentx-UndoSet-PDU: X Yes ___ No, but plan to within ___ months agentx-CleanupSet-PDU: X Yes ___ No, but plan to within ___ months agentx-Notify-PDU: X Yes ___ No, but plan to within ___ months agentx-Ping-PDU: X Yes ___ No, but plan to within ___ months Comments: Implemented, but not used by the current release, though the development version does now make use of this. agentx-IndexAllocate-PDU: X Yes ___ No, but plan to within ___ months Comments: Not used by subagent MIB implementations agentx-IndexDeallocate-PDU: X Yes ___ No, but plan to within ___ months Comments: Not used by subagent MIB implementations agentx-AddAgentCaps-PDU: X Yes ___ No, but plan to within ___ months Comments: Not used by subagent MIB implementations agentx-RemoveAgentCaps-PDU: X Yes ___ No, but plan to within ___ months Comments: Not used by subagent MIB implementations agentx-Response-PDU: X Yes ___ No, but plan to within ___ months Does this implementation have interoperability experience with at least one other independent implementation with respect to: Registration operations: X Yes ___ No, but plan to within ___ months Registration priorities: ___ Yes X No, but plan to within ___ months Comments: Priorities have been implemented and are believed to be working, but have not been tested against an independent implementation. Index allocation operations: ___ Yes X No, but plan to within ___ months Comments: Implemented, but not tested against an independent implementation, or currently used by MIB modules. Index deallocation operations: ___ Yes X No, but plan to within ___ months Comments: Implemented, but not tested against an independent implementation, or currently used by MIB modules. Multiple sub-agent connections: X Yes ___ No, but plan to within ___ months Connecting sub-agent(s) to multiple master agents: ___ Yes X No, but plan to within ___ months Detecting loss of connection of sub-agent(s): X Yes ___ No, but plan to within ___ months Detecting loss of connection with master agent(s): ___ Yes X No, but plan to within 6 months Comments: This functionality is present within the current development code. What transport mappings did you implement: TCP/IP on port 705: X Yes ___ No, but plan to within ___ months Comments: Also TCP/IP on other ports UNIX Domain Sockets on "/var/agentx/master": X Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on other endpoints: X Yes ___ No, but plan to within ___ months Comments: Other(s): X Yes ___ No, but plan to within ___ months Comments: Transport mapping is implemented independently from AgentX support, so the suite will support AgentX over any implemented transport (e.g. definitely UDP/IP - possibly {TCP/UDP}/IPv6, etc) Did you implement the AgentX MIB (RFC2742): ___ Yes X No, but plan to within 6 months Did you satisfy the agentxMIBCompliance MODULE-COMPLIANCE requirements:: ___ Yes ___ No, but plan to within ___ months Did you implement the MIB as an integral part of the master agent: ___ Yes X No Comments: Since we haven't implemented the MIB, strictly speaking the answer is No. But the intention is certainly to implement this within the master agent (only) Did you implement the MIB in an AgentX sub-agent: ___ Yes X No Comments: The necessary information does not appear to be available to the subagent (at least not without a private communication channel to the master agent, which rather defeats the point!) Please record any other comments or notes you deem useful for the record: Comments: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From owner-agentx@dorothy.bmc.com Mon May 14 12:31:17 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17156 for ; Mon, 14 May 2001 12:31:17 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f4EGUbc16402; Mon, 14 May 2001 11:30:37 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA03184 for agentx-list; Mon, 14 May 2001 09:25:25 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA03178 for agentx@dorothy.bmc.com; Mon, 14 May 2001 09:25:18 -0700 (PDT) Date: Mon, 14 May 2001 09:25:18 -0700 (PDT) From: Randy Presuhn Message-Id: <200105141625.JAA03178@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Fwd: Re: AgentX implementation reports requested 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 creeper.bmc.com id f4EGUbc16402 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA17156 Hi - I'm forwarding a non-subscriber post to the agentx list. I've added pereira@wit-software.com to the "posters" list. ------------------------------------------------------- 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 MAA06067 > for ; Fri, 11 May 2001 12:40:53 -0700 (PDT) > Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) > by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f4BJfnZ03000 > for ; Fri, 11 May 2001 14:41:49 -0500 (CDT) > Received: from milu.ipn.pt ([194.79.82.125]) by fw-us-hou-9.bmc.com; Fri, 11 May 2001 14:42:01 +0000 (CST) > Received: from ipn.pt ([195.23.8.89]) > by milu.ipn.pt (8.9.3/8.9.3) with ESMTP id UAA17324; > Fri, 11 May 2001 20:49:13 +0100 (PST) > Message-ID: <3AFC42C2.50044A52@ipn.pt> > Date: Fri, 11 May 2001 20:51:30 +0100 > From: Pedro Pereira > Organization: WIT-Software > X-Mailer: Mozilla 4.5 [en] (WinNT; I) > X-Accept-Language: en > MIME-Version: 1.0 > To: Bob.Natale@AppliedSNMP.com > CC: agentx@dorothy.bmc.com > Subject: Re: AgentX implementation reports requested > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > AgentX Implementation Report > > Report date: May 11, > 2001_______________________________________ > > Submitted by: Pedro Pereira_____________________________________ > > Organization: University of Coimbra_____________________________ > > E-mail address: agentx@dei.uc.pt _________________________________ > > Implementation name: J.AgentX _________________________________________ > > Implementation type: _X_ Master and/or _X_ Sub-Agent and/or _X_ Toolkit > > Runtime platform(s): Any platform supporting Java 1.2 or later ________ > > Reported version id: 1.0 ______________________________________________ > > If Master Agent, did you implement: > > SNMPv1 support in master agent: _X_ Yes ___ No > Comments: > > SNMPv2c support in master agent: ___ Yes _X_ No > Comments: > > SNMPv3 support in master agent: ___ Yes _X_ No > Comments: > > If Sub-Agent, what MIB(s) did you implement: JamesMIB > Comments: The Master Agent also supports MIB-II.system, MIB-II.snmp > and MIB-II.agentx > (Please identify each specific MIB.) > > If Toolkit, please identify: > > Development languages supported: Java 1.2 or later > Comments: > > Development platforms supported: Any platform supporting Java 1.2 or > later > Comments: > > Runtime platforms supported: Any platform supporting Java 1.2 or later > Comments: Functional tests were performed in Linux ReadHat 6.0 > (i386), > Win9x, WinNT, Win2000 and Sun Solaris 2.6 (sparc) > > For all implementations: Did you implement the following PDU types: > > agentx-Open-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Close-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Register-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Unregister-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Get-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-GetNext-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-GetBulk-PDU: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > agentx-TestSet-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Commit-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Set-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-UndoSet-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-CleanupSet-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Notify-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-Ping-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > agentx-IndexAllocate-PDU: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > agentx-IndexDeallocate-PDU: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > agentx-AddAgentCaps-PDU: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > agentx-RemoveAgentCaps-PDU: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > agentx-Response-PDU: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > Does this implementation have interoperability experience with at least > one > other independent implementation with respect to: > > Registration operations: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > Registration priorities: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > Index allocation operations: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > Index deallocation operations: ___ Yes _X_ No, but plan to within ___ > months > Comments: > > Multiple sub-agent connections: _X_ Yes ___ No, but plan to within ___ > months > Comments: > > Connecting sub-agent(s) to multiple master agents: ___ Yes _X_ No, but > plan to within ___ months > Comments: > > Detecting loss of connection of sub-agent(s): ___ Yes _X_ No, but > plan to within ___ months > Comments: > > Detecting loss of connection with master agent(s): ___ Yes _X_ No, but > plan to within ___ months > Comments: > > What transport mappings did you implement: > > TCP/IP on port 705: _X_ Yes ___ No, but plan > to within ___ months > Comments: > > UNIX Domain Sockets on "/var/agentx/master": ___ Yes _X_ No, but plan > to within ___ months > Comments: > > UNIX Domain Sockets on other endpoints: ___ Yes _X_ No, but plan > to within ___ months > Comments: > > Other(s): UPD, JavaSpaces _X_ Yes ___ No, but plan > to within ___ months > Comments: We support UDP, although a connectionless protocol, because > we find it usefull in > situations where using TCP can be awkward. JavaSpaces is also supported > for integration with Mobile Agents. Notice that our Master Agent can > support simultaneas SubAgents using different communication protocols. > > Did you implement the AgentX MIB (RFC2742): _X_ Yes ___ No, but plan > to within ___ months > Comments: > > Did you satisfy the agentxMIBCompliance > MODULE-COMPLIANCE requirements:: _X_ Yes ___ No, but plan > to within ___ months > Comments: > > Did you implement the MIB as an integral part of the master agent: _X_ > Yes ___ No > Comments: Considering "the MIB" as the "AgentX MIB" > > Did you implement the MIB in an AgentX sub-agent: ___ > Yes _X_ No > Comments: I don't think it makes much sense implementing the AgentX > MIB in a SubAgent. > > Please record any other comments or notes you deem useful for the > record: > Comments: The J.AgentX project is a public Java based implementation > of the AgentX protocol. > It's a rather simple and powerful implementation, comprising a Master > Agent and Subagent API. > Source code and documentation are available at the J.AgentX home page: > http://www.dei.uc.pt/agentx > Any questions please submit to agentx@dei.uc.pt > From owner-agentx@dorothy.bmc.com Thu May 24 13:25:48 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17677 for ; Thu, 24 May 2001 13:25:47 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f4OHP2V27242; Thu, 24 May 2001 12:25:02 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA10348 for agentx-list; Thu, 24 May 2001 10:19:37 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA10334; Thu, 24 May 2001 10:19:32 -0700 (PDT) Date: Thu, 24 May 2001 10:19:32 -0700 (PDT) From: Randy Presuhn Message-Id: <200105241719.KAA10334@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Fwd: Info Required Cc: rama.prasad@wipro.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 creeper.bmc.com id f4OHP2V27242 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA17677 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 XAA28875 for ; Wed, 23 May 2001 23:29:37 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f4O6UPM25952 for ; Thu, 24 May 2001 01:30:25 -0500 (CDT) Received: from wiproecmx1.wipro.com ([164.164.31.5]) by fw-us-hou-9.bmc.com; Wed, 24 May 2000 01:30:45 +0000 (CST) Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [192.168.181.23]) by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id f4OGof129285 for ; Thu, 24 May 2001 11:50:42 -0500 (GMT) Received: from wintws04 ([192.168.178.229]) by ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with SMTP id GDTU0W00.3SJ for ; Thu, 24 May 2001 11:59:20 +0530 Message-ID: <003301c0e41c$8f15c640$e5b2a8c0@wipro.com> >From: "Rama Prasad Nadig" To: Subject: Info Required Date: Thu, 24 May 2001 12:11:27 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Hi, Can you please give me the following information : 1. Where can I get good tutorials on AgentX ? 2. Complete details of net-snmp AgentX 4.2.1 (cmu->ucd->net) support on WindowsNT & the steps to build them ? Thanks & Regards, Ram. Rama Prasad N Systems Manager, Wipro Technologies, Bangalore India. From owner-agentx@dorothy.bmc.com Wed May 30 13:25:05 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18792 for ; Wed, 30 May 2001 13:25:04 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f4UHOYf19641; Wed, 30 May 2001 12:24:34 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA26645 for agentx-list; Wed, 30 May 2001 10:19:12 -0700 (PDT) Received: from babbler.bmc.com (babbler.bmc.com [172.17.0.116]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA26640 for ; Wed, 30 May 2001 10:19:08 -0700 (PDT) Received: from ec03-hou.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id f4UHKfZ01201; Wed, 30 May 2001 12:20:42 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19) id <2KPSGXYY>; Wed, 30 May 2001 12:16:34 -0500 Message-ID: From: "Ayers, Mike" To: "'Bob.Natale@AppliedSNMP.com'" , agentx@dorothy.bmc.com Subject: RE: AgentX implementation reports requested Date: Wed, 30 May 2001 12:19:37 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list With apologies for lateness... Report date: ____25May01_______________________________________ Submitted by: ____Mike_Ayers____________________________________ Organization: ____BMC_Software__________________________________ E-mail address: ____mayers@bmc.com________________________________ Implementation name: ____SNMP_Library__________________________________ Implementation type: _X_ Master and/or _X_ Sub-Agent and/or _X_ Toolkit Runtime platform(s): ____Windows_NT/2K,_HPUX,_AIX,_Solaris,____________ ________Compaq_TRU-64_Unix(formerly_OSF/1)________ Reported version id: ____3.3___________________________________________ If Master Agent, did you implement: SNMPv1 support in master agent: _X_ Yes ___ No Comments: SNMPv2c support in master agent: ___ Yes _X_ No Comments: SNMPv3 support in master agent: ___ Yes _X_ No Comments: Will be supported in next release If Sub-Agent, what MIB(s) did you implement: only sample MIBs were implemented as separate subagents. Master agent is implemented with a monolithic subagent which Comments: (Please identify each specific MIB.) If Toolkit, please identify: Development languages supported: C, C++ Comments: Development platforms supported: Windows NT/2K, HPUX, AIX, Solaris, TRU-64 Comments: Runtime platforms supported: Windows NT/2K, HPUX, AIX, Solaris, TRU-64 Comments: For all implementations: Did you implement the following PDU types: agentx-Open-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Close-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Register-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Unregister-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Get-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-GetNext-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-GetBulk-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: Not tested agentx-TestSet-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Commit-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Set-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-UndoSet-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-CleanupSet-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Notify-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: agentx-Ping-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: Not tested agentx-IndexAllocate-PDU: ___ Yes _X_ No, but plan to within _?_ months Comments: agentx-IndexDeallocate-PDU: ___ Yes _X_ No, but plan to within _?_ months Comments: agentx-AddAgentCaps-PDU: ___ Yes _X_ No, but plan to within _?_ months Comments: agentx-RemoveAgentCaps-PDU: ___ Yes _X_ No, but plan to within _?_ months Comments: agentx-Response-PDU: _X_ Yes ___ No, but plan to within ___ months Comments: Does this implementation have interoperability experience with at least one other independent implementation with respect to: Registration operations: _X_ Yes ___ No, but plan to within ___ months Comments: Registration priorities: _X_ Yes ___ No, but plan to within ___ months Comments: Index allocation operations: ___ Yes _X_ No, but plan to within _?_ months Comments: Index deallocation operations: ___ Yes _X_ No, but plan to within _?_ months Comments: Multiple sub-agent connections: _X_ Yes ___ No, but plan to within ___ months Comments: Connecting sub-agent(s) to multiple master agents: _X_ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection of sub-agent(s): _X_ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection with master agent(s): ___ Yes _X_ No, but plan to within _3_ months Comments: What transport mappings did you implement: TCP/IP on port 705: _X_ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on "/var/agentx/master": _X_ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on other endpoints: _X_ Yes ___ No, but plan to within ___ months Comments: Other(s): _X_ Yes ___ No, but plan to within ___ months Comments: TCP connections on any port (Please indicate at least type(s) and connection specifics.) Did you implement the AgentX MIB (RFC2742): ___ Yes _X_ No, but plan to within ___ months Comments: Did you satisfy the agentxMIBCompliance MODULE-COMPLIANCE requirements:: ___ Yes _X_ No, but plan to within ___ months Comments: No MIB Did you implement the MIB as an integral part of the master agent: _X_ Yes ___ No Comments: No MIB Did you implement the MIB in an AgentX sub-agent: _X_ Yes ___ No Comments: No MIB Please record any other comments or notes you deem useful for the record: Comments: From owner-agentx@dorothy.bmc.com Thu May 31 08:53:14 2001 Received: from creeper.bmc.com ([198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA22882 for ; Thu, 31 May 2001 08:53:13 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f4VCqmQ11945; Thu, 31 May 2001 07:52:48 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA16417 for agentx-list; Thu, 31 May 2001 05:49:25 -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 FAA16412 for ; Thu, 31 May 2001 05:49:21 -0700 (PDT) Received: from fw-us-hou-9.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with SMTP id f4VCo5q26881 for ; Thu, 31 May 2001 07:50:05 -0500 (CDT) Received: from ihemail2.lucent.com ([192.11.222.163]) by fw-us-hou-9.bmc.com; Wed, 31 May 2000 07:50:16 +0000 (CST) Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1]) by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f4VCoIH00490 for ; Thu, 31 May 2001 08:50:18 -0400 (EDT) Received: from md6370exch001p.wins.lucent.com (h135-114-206-50.lucent.com [135.114.206.50]) by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f4VCoIe00480 for ; Thu, 31 May 2001 08:50:18 -0400 (EDT) Received: by md6370exch001p.nse.lucent.com with Internet Mail Service (5.5.2650.21) id ; Thu, 31 May 2001 08:50:17 -0400 Message-ID: From: "Natale, Robert C (Bob)" To: "Ayers, Mike" Cc: agentx@dorothy.bmc.com Subject: RE: AgentX implementation reports requested Date: Thu, 31 May 2001 08:50:06 -0400 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.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Hi Mike, > With apologies for lateness... Thanks for the report. For the record, after receiving the main batch of implementation reports (including several off-list), there were two known implementations who had not reported. I contacted both orgs directly to ask whether they intended to submit a report because I did not want to proceed w/o them only to receive them after the summary was produced. One of the orgs informed me that they did not intend to submit an implementation report...with that, Mike's report wraps up the set of implementations I am aware of, so I will proceed with the next step(s) now and will publish the draft summary implementation report to the WG for review over the coming weekend. Thanks, BobN