From ashishkh@wipinfo.soft.net Wed Jul 1 04:10:31 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id EAA01220 for ; Wed, 1 Jul 1998 04:10:31 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id EAA01178 for ; Wed, 1 Jul 1998 04:10:21 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma000449; Wed, 1 Jul 98 04:08:05 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id EAA04149 for ; Wed, 1 Jul 1998 04:07:29 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma003212; Wed, 1 Jul 98 04:06:32 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id EAA08740; Wed, 1 Jul 1998 04:06:58 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA17702 for ; Wed, 1 Jul 1998 02:02:39 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id EAA29692 for ; Wed, 1 Jul 1998 04:02:27 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma029655; Wed, 1 Jul 98 04:02:10 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id OAA00601; Wed, 1 Jul 1998 14:26:07 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id OAA07687; Wed, 1 Jul 1998 14:32:22 +0530 Reply-To: From: "Ashish K Hanwadikar" To: "Bob Natale" Cc: "Agentx" Subject: RE: Updated goals and milestones Date: Wed, 1 Jul 1998 14:31:07 +0530 Keywords: Mailing Lists Message-ID: <000501bda4ce$c904dfc0$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Reply-By: Mon, 6 Jul 1998 18:00:00 +0530 In-Reply-To: <9806301545.AA06228@acecomm.com> X-Message-Flag: Follow up Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by tangelo.bmc.com id EAA08740 Hi, Is the AgentX API I-D going to be an information RFC or a standard RF= C? Where can I get more information about the efforts on AgentX API (mailing lists, working groups etc.)? Also, one more thing, the AgentX-Close-PDU when sent by Sub Agent to Master Agent does not require master agent to respond until there is an error in closing the session. This is unnecessarily making the implementation complicated. Why can't master agent send response to all agentx-close-PDUs irrespective of the outcome? Otherwise, the sub agent h= as to keep on waiting for the response to agentx-close-PDU, when he don't ev= en know whether there will be any response or not. The same is true for agentx-notify-PDU. The implementation becomes very complicated when we ha= ve to design a generic sub agent API. What should be the semantics of the ca= ll agent-close-session(sessionID), blocking or non-blocking? If it is non-blocking what happens when there is error in closing the session and response is received from the master agent? If it is made blocking and th= ere is no resonse because the session was closed successfuly then how long should the call block? This waiting on the sub agent side is a general problem. What should = be the timeout values from the sub agent side, i.e. for how long should the = sub agent wait for responses from the master agent for various PDU's like registration etc. Thanks in advance. > -----Original Message----- > From: Bob Natale [mailto:bnatale@acecomm.com] > Sent: Tuesday, June 30, 1998 9:15 PM > To: agentx@peer.com > Subject: Updated goals and milestones > > > Hi, > > The AgentX page at www.ietf.org has been > updated with the > following: > > Goals and Milestones: > > Done Publication of AgentX protocol specification > Done Submit working draft version of AgentX MIB I-D. > Jun 98 Collect and evaluate implementation reports > (through bake-off). > Jul 98 Conduct AgentX interoperability testing > (July 23-24, Sunnyvale). > Aug 98 Meet at 42nd IETF-Chicago (refine or revise > RFC 2257). > Sep 98 Petition IESG to advance RFC 2257 to Draft > or recycle at Proposed > Oct 98 Submit final version of AgentX MIB I-D to > IESG for consideration as Proposed. > Nov 98 Submit initial draft version of AgentX API I-D > Dec 98 Submit interim draft version of AgentX API I-D. > Jan 99 Submit final version of AgentX API I-D to IESG > for consideration as an Informational RFC. > Feb 99 Evaluate necessary revisions to RFC 2257. > Feb 99 Evaluate necessary revisions to AgentX MIB RFC. > Mar 99 Meet at 44th IETF to > Assess status of AgentX deployment > Determine need for AgentX v2 (Protocol, MIB, or API) > Plan future work items accordingly. > Apr 99 Submit new charter proposal to IESG or retire WG. > > I have submitted a request for a single 2hr meeting slot in > Chicago...I have not yet received notification of the scheduled > time and place. The basic agenda will include: > > - the usual preliminaries > - review implementation status reports > - review bake-off results, findings > - review list of open issues > - review status of AgentX MIB > - review need/desire for a standard AgentX API > - review status of SNMPv3 and DISMAN wrt AgentX > - recommend working plan wrt any of the above items > - the usual summaries > > Comments on any of the above are welcomed...as are proposed > mods (additions/deletions/changes) to the agenda outline. > > Cordially, > > BobN > ------------ ISO 9001 Registered Quality Supplier ----------- > Bob Natale=A0=A0=A0=A0=A0=A0=A0=A0 | ACE*COMM=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 | 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.co= m > ------------- > > From ksainc@magicsolution.com Sat Jul 4 22:33:42 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id WAA00533 for ; Sat, 4 Jul 1998 22:33:41 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id WAA05085 for ; Sat, 4 Jul 1998 22:33:25 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma005056; Sat, 4 Jul 98 22:33:18 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id WAA24557 for ; Sat, 4 Jul 1998 22:32:44 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma024470; Sat, 4 Jul 98 22:32:17 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id WAA23923; Sat, 4 Jul 1998 22:32:43 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id UAA00230 for ; Sat, 4 Jul 1998 20:22:37 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id WAA20571 for ; Sat, 4 Jul 1998 22:22:36 -0500 (CDT) Received: from unknown(12.14.24.4) by cashew.bmc.com via smap (V2.0) id xma020568; Sat, 4 Jul 98 22:22:16 -0500 Received: from virtual.magicsolution.com ([12.14.24.5]) by candra.online-systems.net (8.9.1/8.9.0) with SMTP id XAA16108; Sat, 4 Jul 1998 23:21:42 -0400 (EDT) Date: Sat, 4 Jul 1998 23:21:42 -0400 (EDT) Message-Id: <199807050321.XAA16108@candra.online-systems.net> X-Sender: ksainc@magicsolution.com X-Mailer: Windows Eudora Light Version 3.0.1 (32) From: Kalman.Saffran.Associates@candra.online-systems.net, "Inc." Reply-To: ksainc@magicsolution.com To: (Dear Friend) Subject: ADV: SONET Newsletter Volume 6-98 Kalman Saffran Associates Inc. (KSA) announces the availability of SONET/SDH technology licenses. Already the telecommunications standard, SONET/SDH has now been adopted by ISP's and the cable TV industry. Equipment manufacturers are required by customers to deliver SONET/SDH compatible products. KSA began developing SONET/SDH products 12 years ago for telephone equipment manufacturers. Now the entire communications industry needs to plug into the public switched telephone network using SONET/SDH. By capitalizing on KSA's vast expertise with SONET/SDH products, companies can serve new customers without having to invest years in development of this very complex technology. KSA licenses include proprietary circuitry and firmware. KSA also offers associated custom product development and system engineering services. KSA has a staff of more than 100, including engineers specializing in today's "building block" technologies such as SONET/SDH, ATM, xDSL, fiber optics, MPEG and PCI. In addition to SONET/SDH, KSA has ATM, MPEG-2, PCI and CompactPCI hot swap solutions available for license. KSA's clients include industry leaders such as AT&T, Lucent, Nortel, Alcatel, Cisco Systems, Bay Networks, 3COM, Scientific-Atlanta, PictureTel, Hewlett-Packard, Compaq and Motorola. Contact: Kalman Saffran Associates, Inc., 1841 Commonwealth Ave., Newton, MA 02166 - (617)527-2000 - www.ksaweb.com --------------- We are currently consolidating our many mailing lists and need to update our databases. Our records indicate that you may have inquired in the past. If this is not the case, please reply with "REMOVE" in the subject field to never receive email offers from this vendor. From bnatale@acecomm.com Mon Jul 6 10:30:11 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id KAA01291 for ; Mon, 6 Jul 1998 10:30:11 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA23598 for ; Mon, 6 Jul 1998 10:29:50 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma023390; Mon, 6 Jul 98 10:28:59 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id KAA16037 for ; Mon, 6 Jul 1998 10:28:26 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma015642; Mon, 6 Jul 98 10:28:03 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA14975; Mon, 6 Jul 1998 10:28:32 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA29874 for ; Mon, 6 Jul 1998 08:18:41 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA22297 for ; Mon, 6 Jul 1998 10:18:38 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by almond.bmc.com via smap (V2.0) id xma022295; Mon, 6 Jul 98 10:18:27 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) for agentx@peer.com id 0ytD24-0001tf-00; Mon, 6 Jul 1998 11:18:21 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA00601; Mon, 6 Jul 1998 11:20:39 -0400 Message-Id: <9807061520.AA00601@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 06 Jul 1998 11:20:25 -0400 To: agentx@peer.com From: Bob Natale Subject: Fwd: 42nd IETF-CHICAGO, IL: AGENTX Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >Date: Mon, 06 Jul 1998 10:54:59 -0400 >From: Marcia Beaulieu >This is to confirm one session for AGENTX as follows: > > Wednesday, August 26 at 1530-1730 > > Other groups scheduled at that time: ip1394, > Routing Area Meeting, avt We must submit a formal agenda by Aug 19. I have already posted (on Jun 30) the outline candidate agenda included below. Please post any suggested changes to the list (or to me directly if you prefer). Thanks. The basic agenda will include: - the usual preliminaries - review implementation status reports - review bake-off results, findings - review list of open issues - review status of AgentX MIB - review need/desire for a standard AgentX API - review status of SNMPv3 and DISMAN wrt AgentX - recommend working plan wrt any of the above items - the usual summaries 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 uglyware@berkscountypa.com Thu Jul 16 01:53:00 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id BAA16485 for ; Thu, 16 Jul 1998 01:52:59 -0500 (CDT) From: uglyware@berkscountypa.com Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id BAA05598 for ; Thu, 16 Jul 1998 01:52:20 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma005206; Thu, 16 Jul 98 01:50:56 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id BAA26256 for ; Thu, 16 Jul 1998 01:50:22 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma026133; Thu, 16 Jul 98 01:49:54 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id BAA20891; Thu, 16 Jul 1998 01:50:24 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id XAA07395 for ; Wed, 15 Jul 1998 23:41:12 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id BAA04079 for ; Thu, 16 Jul 1998 01:41:11 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma004065; Thu, 16 Jul 98 01:40:45 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id BAA23228 for ; Thu, 16 Jul 1998 01:40:12 -0500 (CDT) Date: Thu, 16 Jul 1998 01:40:12 -0500 (CDT) Message-Id: <199807160640.BAA23228@dresden.bmc.com> Received: from unknown(205.148.246.213) by dresden.bmc.com via smap (3.2) id xma023215; Thu, 16 Jul 98 01:40:05 -0500 To: agentx@peer.com Subject: Public Service - S.M.A.R.T. Sensor As a public service, Higher Ground Diagnostics, Inc. is offering a free download of the Hard Drive Mechanics S.M.A.R.T. sensor. This program will check your PC for the presence of *Predictive* technology installed into most hard drives built after 1996. This technology is capable of determining when hard drive failures will occur. If your hard drive has the S.M.A.R.T. technology, then your PC already has the ability to detect hard drive crashes, weeks even months before they actually occur. To take advantage of the S.M.A.R.T. technology, you simply need to access it. As a free public service, the S.M.A.R.T. tester can be downloaded from http://www.uglyware.com/deluxe/ The S.M.A.R.T. tester has been checked for viruses and may be downloaded safely from that website. Zandy Carter International Marketing Manager From agentx-bugs@andrew.cmu.edu Fri Jul 17 12:47:58 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id MAA03037 for ; Fri, 17 Jul 1998 12:47:58 -0500 (CDT) From: agentx-bugs@andrew.cmu.edu Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA08336 for ; Fri, 17 Jul 1998 12:47:15 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma007941; Fri, 17 Jul 98 12:45:56 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA27954 for ; Fri, 17 Jul 1998 12:45:21 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma026246; Fri, 17 Jul 98 12:44:03 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA22729; Fri, 17 Jul 1998 12:44:33 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA26493 for ; Fri, 17 Jul 1998 09:27:31 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id LAA05633 for ; Fri, 17 Jul 1998 11:27:25 -0500 (CDT) Received: from gauntlet.fv.com(207.67.199.118) by cashew.bmc.com via smap (V2.0) id xma005619; Fri, 17 Jul 98 11:27:02 -0500 Received: from shekel.fv.com (shekel.fv.com [207.67.199.130]) by gauntlet.fv.com (8.9.1/8.9.0) with ESMTP id JAA26845 for ; Fri, 17 Jul 1998 09:25:53 -0700 (PDT) Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.9.1/8.9.1) with ESMTP id JAA04153 for ; Fri, 17 Jul 1998 09:26:45 -0700 (PDT) Received: from mail1.andrew.cmu.edu (MAIL1.ANDREW.CMU.EDU [128.2.10.131]) by gauntlet.fv.com (8.9.1/8.9.0) with ESMTP id JAA26831 for ; Fri, 17 Jul 1998 09:25:42 -0700 (PDT) Received: from po4.andrew.cmu.edu (PO4.ANDREW.CMU.EDU [128.2.10.104]) by mail1.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id MAA11804 for ; Fri, 17 Jul 1998 12:26:41 -0400 (EDT) Received: (from daemon@localhost) by po4.andrew.cmu.edu (8.8.5/8.8.2) id MAA23553 for post+internet.computing.agentx@MAIL1.ANDREW.CMU.EDU; Fri, 17 Jul 1998 12:26:38 -0400 (EDT) Received: via switchmail for post+internet.computing.agentx@andrew.cmu.edu; Fri, 17 Jul 1998 12:26:36 -0400 (EDT) Received: from cmu1.acs.cmu.edu (CMU1.ACS.CMU.EDU [128.2.35.186]) by po4.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id MAA23530; Fri, 17 Jul 1998 12:26:26 -0400 (EDT) Received: from FRAUGHT.NET.CMU.EDU (FRAUGHT.NET.CMU.EDU [128.2.6.66]) by cmu1.acs.cmu.edu (8.8.5/8.8.5) with SMTP id MAA24850; Fri, 17 Jul 1998 12:26:22 -0400 (EDT) Date: Fri, 17 Jul 1998 12:28:33 -0400 To: post+internet.computing.agentx@andrew.cmu.edu Subject: CMU AgentX v0.1.1 available Message-ID: <3030348966.900678513@FRAUGHT.NET.CMU.EDU> X-Mailer: Mulberry (Win32) [1.3.3, s/n S-100002] X-Authenticated: mwhite by cyrus.andrew.cmu.edu X-Licensed-To: site license MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have made a second alpha quality release of our AgentX subagent library and snmpd available for FTP. While there are still several protocol features that need to be implemented, we have verified that we interoperate with Digital's implementation of the AgentX protocol. The web site for the CMU AgentX project is located at; http://www.net.cmu.edu/projects/agentx/ Commnets or questions should be addressed to: agentx-bug@andrew.cmu.edu Thanks to all who have shown interest in our work. Matt White ---------- Matt White Maintainer, AgentX Implementation Carnegie Mellon Computing Services From ashishkh@wipinfo.soft.net Fri Jul 31 10:32:01 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id KAA12640 for ; Fri, 31 Jul 1998 10:32:00 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA18663 for ; Fri, 31 Jul 1998 10:30:49 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma017821; Fri, 31 Jul 98 10:28:05 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id KAA20345 for ; Fri, 31 Jul 1998 10:27:29 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma019085; Fri, 31 Jul 98 10:26:31 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA19047; Fri, 31 Jul 1998 10:27:02 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id GAA11429 for ; Fri, 31 Jul 1998 06:59:40 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id IAA11006 for ; Fri, 31 Jul 1998 08:59:38 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma010837; Fri, 31 Jul 98 08:59:03 -0500 Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id TAA09690; Fri, 31 Jul 1998 19:23:51 -0500 From: "Ashish Hanwadikar" To: "Agentx" Cc: "RAMAKUMARA K" Subject: Sub Agent Processing of AgentX GetNext Response Date: Fri, 31 Jul 1998 19:29:15 +0530 Message-ID: <005301bdbc8b$67266f10$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0054_01BDBCB9.80DEAB10" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 This is a multi-part message in MIME format. ------=_NextPart_000_0054_01BDBCB9.80DEAB10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi all, While going through the AgentX RFC we noticed one ambiguity: "Section 7.2.2.2. Subagent Processing of the agentx-GetNext-PDU Upon the subagent's receipt of an agentx-GetNext-PDU, each SearchRange in the request is processed as follows: (1) The subagent searches for a variable within the lexicographically ordered list of variable names for all variables it instantiates (without regard to registration of regions) within the indicated context and session, for which the following are all true:" Suppose master agent sends AgentX GetNext request to a subagent (Sub Agent #1) with a SearchRange (falling under a target MIB Region #1). The sub agent responds with a oid and its value falling under a different MIB Region (lexicographically after MIB Region #1). Lets call these region as MIB Region #2. Now suppose another sub agent had registered an MIB Region #3. The lexicographical relationship is MIB Region #1 < #3 < #2 That means, if the SearchRange doesn't fall within MIB Region #1, then ideally target sub agent should return endOfMIBView. The Master Agent will find lexicographically next region, i.e. MIB Region #3 (by subagent #2) and resend the request to sub agent #2. If first sub agent returns the oid and value from MIB Region #2 (as he has to search through a list of lexicographically ordered list of instantiated variables without regard to registration of region), then the SNMP Response for SNMP GetNext will be wrong. Either this is a error or it is not clear what is meant by "without regard to registration of MIB region". Please clarify. Also, in the section "7.2.4.3. Processing of Responses to agentx-GetNext-PDU and agentx-GetBulk-PDU ", the Master Agent never checks whether for each oid in the VarBind the response returned by a sub agent is valid or not. I think the master agent should check whether, for the oid in the varbind, the response returned by the sub agent is falling within the target MIB Region (which he determined while preparing the AgentX GetNext PDU for that particular sub agent). Thanks. With regards, Ashish K Hanwadikar Senior Software Engineer, Wipro Infotech, Technology Solutions, Bangalore INDIA ------=_NextPart_000_0054_01BDBCB9.80DEAB10 Content-Type: text/x-vcard; name="Ashish K Hanwadikar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Ashish K Hanwadikar.vcf" BEGIN:VCARD VERSION:2.1 N:Hanwadikar;Ashish;K;; FN:Ashish K Hanwadikar ORG:Wipro Infotech, Technology Solutions;Technology Solutions TITLE:Senior Software Engineer TEL;WORK;VOICE:+91-80-2241730 Ext. 3315 TEL;HOME;VOICE:+91-80-2241730 Ext. 3315 ADR;WORK:;Mission Road LABEL;WORK:Mission Road ADR;HOME;ENCODING=3DQUOTED-PRINTABLE:;;Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar;Bangalo=3D re;Karnataka;560 027;INDIA LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar=3D0D=3D0ABang=3D alore, Karnataka 560 027=3D0D=3D0AINDIA URL:http://www.geocities.com/SiliconValley/Bay/5393/ URL:http://www.geocities.com/SiliconValley/Bay/5393 EMAIL;PREF;INTERNET:ashishkh@wipinfo.soft.net REV:19980630T133122Z END:VCARD ------=_NextPart_000_0054_01BDBCB9.80DEAB10-- From daniele@zk3.dec.com Fri Jul 31 12:18:12 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id MAA13470 for ; Fri, 31 Jul 1998 12:18:11 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA27561 for ; Fri, 31 Jul 1998 12:16:59 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma026923; Fri, 31 Jul 98 12:14:46 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA08684 for ; Fri, 31 Jul 1998 12:14:07 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma007003; Fri, 31 Jul 98 12:12:52 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA21885; Fri, 31 Jul 1998 12:13:21 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA12460 for ; Fri, 31 Jul 1998 09:58:58 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id LAA25297 for ; Fri, 31 Jul 1998 11:58:56 -0500 (CDT) Received: from mail11.digital.com(192.208.46.10) by almond.bmc.com via smap (V2.0) id xma025290; Fri, 31 Jul 98 11:58:49 -0500 Received: from quarry.zk3.dec.com (fquarry.zk3.dec.com [16.140.160.9]) by mail11.digital.com (8.8.8/8.8.8/WV1.0f) with SMTP id MAA15672; Fri, 31 Jul 1998 12:57:52 -0400 (EDT) Received: from bernie.zk3.dec.com by quarry.zk3.dec.com; (5.65v4.0/1.1.8.2/16Jan95-0946AM) id AA06644; Fri, 31 Jul 1998 12:57:51 -0400 Received: from localhost by bernie.zk3.dec.com; (5.65/1.1.8.2/22Aug96-1117AM) id AA20179; Fri, 31 Jul 1998 12:58:03 -0400 Message-Id: <9807311658.AA20179@bernie.zk3.dec.com> To: "Ashish Hanwadikar" Cc: agentx@peer.com Subject: Re: Sub Agent Processing of AgentX GetNext Response In-Reply-To: Your message of "Fri, 31 Jul 98 19:29:15 +0530." <005301bdbc8b$67266f10$163409c0@opel.wipinfo.soft.net> Date: Fri, 31 Jul 98 12:58:03 -0400 From: Mike Daniele X-Mts: smtp Hi Ashish, > If first sub agent returns the oid and value from MIB Region #2 (as he has >to search through a list of lexicographically ordered list of instantiated >variables without regard to registration of region), then the SNMP Response >for SNMP GetNext will be wrong. > Either this is a error or it is not clear what is meant by "without regard >to registration of MIB region". Please clarify. > Also, in the section "7.2.4.3. Processing of Responses to >agentx-GetNext-PDU and agentx-GetBulk-PDU ", the Master Agent never checks >whether for each oid in the VarBind the response returned by a sub agent is >valid or not. I think the master agent should check whether, for the oid in >the varbind, the response returned by the sub agent is falling within the >target MIB Region (which he determined while preparing the AgentX GetNext >PDU for that particular sub agent). 7.2.1 states 1) Honoring the registry Because AgentX supports overlapping registrations, it is possible for the master agent to obtain a value for a requested varbind from within multiple registered MIB regions. The master agent must ensure that the value (or exception) actually returned in the SNMP response PDU is taken from the authoritative region (as defined in section 7.1.5.1). I think this "blanket rule" covers your concerns. Note that the master agent may use the ending oid of the searchrange to "scope" the instances the subagent may return, as described in 2) of section 7.2.1, and 7.2.2.2. Does this make it clear? Regards, Mike From sgudur@hotmail.com Fri Jul 31 12:42:54 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id MAA13658 for ; Fri, 31 Jul 1998 12:42:53 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA00248 for ; Fri, 31 Jul 1998 12:41:42 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma029540; Fri, 31 Jul 98 12:39:35 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA02570 for ; Fri, 31 Jul 1998 12:38:58 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma001573; Fri, 31 Jul 98 12:38:15 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA29130; Fri, 31 Jul 1998 12:38:47 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA12551 for ; Fri, 31 Jul 1998 10:33:03 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id MAA07662 for ; Fri, 31 Jul 1998 12:33:01 -0500 (CDT) Received: from f220.hotmail.com(207.82.251.111) by cashew.bmc.com via smap (V2.0) id xma007630; Fri, 31 Jul 98 12:32:35 -0500 Received: (qmail 29030 invoked by uid 0); 31 Jul 1998 17:32:29 -0000 Message-ID: <19980731173229.29029.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Fri, 31 Jul 1998 10:32:29 PDT X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: agentx@peer.com Subject: open issues in agentX MIB Content-Type: text/plain Date: Fri, 31 Jul 1998 10:32:29 PDT Hi, Some of the open issues that needs to be addressed for agentx MIB include: 1. Relevance of agentxConnNumber, and agentxSessionNumber. This gives the number of entries in each respective table. Do we need these in the tables? 2. Add agentXLastChange to RegistrationTable to be consistent with the other tables. If there are any other open items that need to be addressed in the MIB, I urge everyone on the mailing list to send them as early as possible. These need to be resolved before the Chicago IETF meeting in August. Please send all email to agentx mailing list. thanks smitha ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From fenner@parc.xerox.com Fri Jul 31 14:11:08 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id OAA14343 for ; Fri, 31 Jul 1998 14:11:08 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id OAA07219 for ; Fri, 31 Jul 1998 14:09:56 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma006700; Fri, 31 Jul 98 14:08:13 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id OAA00708 for ; Fri, 31 Jul 1998 14:07:35 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma029088; Fri, 31 Jul 98 14:06:33 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA26547; Fri, 31 Jul 1998 14:07:02 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA13234 for ; Fri, 31 Jul 1998 11:51:47 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id NAA04931 for ; Fri, 31 Jul 1998 13:51:46 -0500 (CDT) Received: from omega.xerox.com(13.1.64.95) by almond.bmc.com via smap (V2.0) id xma004880; Fri, 31 Jul 98 13:51:16 -0500 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40677(2)>; Fri, 31 Jul 1998 11:51:05 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 31 Jul 1998 11:50:55 -0700 From: Bill Fenner To: agentx@peer.com Subject: Can an AgnetX sub-agent send an AgentX-GET PDU to the AgentX master? Cc: fenner@parc.xerox.com Message-Id: <98Jul31.115055pdt.177515@crevenia.parc.xerox.com> Date: Fri, 31 Jul 1998 11:50:52 PDT Hi, Let's say I have a routing daemon which wants to present a MIB which happens to include ifindex values. However, the local interface to ifindex value mapping happens in a different subagent; the routing daemon doesn't know what this mapping is. It has to walk the iftable and try to match that up with its view of the interfaces. Can this routing daemon send AgentX-GET PDU's up to the master agent and expect it to dispatch them to the right sub-agent and dispatch the reply back to me all via AgentX, or do I have to use SNMP for this part? I ask because it seems like a shame that an application that only wants to be an AgentX sub-agent also has to be able to be an SNMP client. Thanks, Bill From fenner@parc.xerox.com Fri Jul 31 14:23:27 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id OAA14446 for ; Fri, 31 Jul 1998 14:23:27 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id OAA09391 for ; Fri, 31 Jul 1998 14:22:15 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma008729; Fri, 31 Jul 98 14:20:30 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id OAA12463 for ; Fri, 31 Jul 1998 14:19:54 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma010063; Fri, 31 Jul 98 14:18:11 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA00285; Fri, 31 Jul 1998 14:18:43 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA13406 for ; Fri, 31 Jul 1998 12:13:11 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id OAA14055 for ; Fri, 31 Jul 1998 14:13:09 -0500 (CDT) Received: from omega.xerox.com(13.1.64.95) by cashew.bmc.com via smap (V2.0) id xma013944; Fri, 31 Jul 98 14:12:46 -0500 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40652(2)>; Fri, 31 Jul 1998 12:11:20 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 31 Jul 1998 12:11:13 -0700 From: Bill Fenner To: agentx@peer.com Subject: Misleading wording in section 8.1.2: AgentX over TCP operation Cc: fenner@parc.xerox.com Message-Id: <98Jul31.121113pdt.177515@crevenia.parc.xerox.com> Date: Fri, 31 Jul 1998 12:11:00 PDT Section 8.1.2 says: All AgentX PDUs are presented individually to the TCP, to be sent as the data portion of a TCP PDU. Applications can't control TCP PDU's; e.g. if you do 3 small TCP writes in a row, most TCP's will coalesce the 2nd and 3rd write into a single TCP PDU. And, of course, large writes will be fragmented into multiple TCP PDU's. I'd suggest removing this sentence in the next version of the document, since how you present data to TCP has very little to do with how TCP puts the data into PDU's. Bill From schoenw@ibr.cs.tu-bs.de Fri Jul 31 15:28:35 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id PAA14973 for ; Fri, 31 Jul 1998 15:28:34 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA14994 for ; Fri, 31 Jul 1998 15:27:22 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma014412; Fri, 31 Jul 98 15:26:00 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id PAA15361 for ; Fri, 31 Jul 1998 15:25:24 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma014188; Fri, 31 Jul 98 15:24:26 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA19463; Fri, 31 Jul 1998 15:24:58 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA13775 for ; Fri, 31 Jul 1998 13:12:35 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id PAA17695 for ; Fri, 31 Jul 1998 15:12:33 -0500 (CDT) Received: from mumm.ibr.cs.tu-bs.de(134.169.34.190) by cashew.bmc.com via smap (V2.0) id xma017637; Fri, 31 Jul 98 15:11:53 -0500 Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.1/8.9.0) with ESMTP id WAA17833; Fri, 31 Jul 1998 22:11:51 +0200 (MET DST) Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id WAA01760; Fri, 31 Jul 1998 22:11:50 +0200 Date: Fri, 31 Jul 1998 22:11:50 +0200 Message-Id: <199807312011.WAA01760@henkell.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: agentx@peer.com Subject: Extensions for AgentX Version 1 Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII AgentX verion 1 does not allow a subagent to do the following: 1) check whether access is allowed to variables that exist in other subagents 2) read variables that exist in other subagents (with appropriate access control applied) 3) write variables that exist in other subagents (with appropriate access control applied) Some of the DISMAN MIBs that are currently on their way to proposed standard require to do the operations listed above. This means that it is impossible to implement and ship these DISMAN MIBs as separate products that you can plug into your native AgentX master agent. It might be possible to extend AgentX to provide this capability. The hardest part of the problem is how you maintain the required input for the access control function. Shipping this information to the subagent is probably not a good idea (it would make it pretty easy to mount guessing attacks from a subagent). However, it might be possible to find a solution where the master maintains a cache for security related information and passes only a handle to a subagent, probably only on a special request from the subagent while processing a read or write SNMP request. Anyway, I would like to know if there is interest in extending AgentX in this direction so that DISMAN MIBs can be implemented based on AgentX. (Bob, please consider this a request to discuss this during the AgentX meeting in Chicago. ;-) Juergen Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289) From mithatch@cisco.com Fri Jul 31 15:34:00 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id PAA15019 for ; Fri, 31 Jul 1998 15:34:00 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA16366 for ; Fri, 31 Jul 1998 15:32:48 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xmaa15902; Fri, 31 Jul 98 15:31:44 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id PAA21465 for ; Fri, 31 Jul 1998 15:31:09 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma020599; Fri, 31 Jul 98 15:30:23 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA21091; Fri, 31 Jul 1998 15:30:55 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA13847 for ; Fri, 31 Jul 1998 13:27:05 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA14881 for ; Fri, 31 Jul 1998 15:27:02 -0500 (CDT) Received: from brownale.cisco.com(171.69.95.89) by almond.bmc.com via smap (V2.0) id xma014359; Fri, 31 Jul 98 15:25:50 -0500 Received: from mithatch-ultra.cisco.com (mithatch-ultra.cisco.com [171.69.50.33]) by brownale.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id NAA08617; Fri, 31 Jul 1998 13:24:36 -0700 (PDT) Received: from cisco.com (localhost [127.0.0.1]) by mithatch-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id NAA12501; Fri, 31 Jul 1998 13:24:35 -0700 (PDT) Sender: mithatch@cisco.com Message-ID: <35C22803.C5940BEE@cisco.com> Date: Fri, 31 Jul 1998 13:24:35 -0700 From: Mike Thatcher X-Mailer: Mozilla 4.03C-CISCOENG [en] (X11; U; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: Smitha Gudur CC: agentx@peer.com Subject: Re: open issues in agentX MIB References: <19980731173229.29029.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit If there is a relationship between sessionID as defined in RFC2257and agentxSessionIndex then the relationship needs to be clarified and the description of agentxSessionIndex made consistent with the definition in the RFC. (See sections 6.1, 6.2.16, 7.1.1(3)) MikeT From rpresuhn@dorothy.bmc.com Fri Jul 31 16:44:14 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id QAA15576 for ; Fri, 31 Jul 1998 16:44:14 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA22638 for ; Fri, 31 Jul 1998 16:43:01 -0500 (CDT) Received: from dresden.bmc.com(198.64.253.250) by almond.bmc.com via smap (V2.0) id xma021688; Fri, 31 Jul 98 16:40:03 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA20192 for ; Fri, 31 Jul 1998 16:39:21 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma018950; Fri, 31 Jul 98 16:38:34 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA09761; Fri, 31 Jul 1998 16:39:06 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA14938 for agentx@peer.com; Fri, 31 Jul 1998 14:24:42 -0700 (PDT) Date: Fri, 31 Jul 1998 14:24:42 -0700 (PDT) From: Randy Presuhn Message-Id: <199807312124.OAA14938@dorothy.bmc.com> To: agentx@peer.com Subject: Re: Extensions for AgentX Version 1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Fri, 31 Jul 1998 22:11:50 +0200 > From: Juergen Schoenwaelder > To: agentx@peer.com > Subject: Extensions for AgentX Version 1 ... > Anyway, I would like to know if there is interest in extending AgentX > in this direction so that DISMAN MIBs can be implemented based on > AgentX. (Bob, please consider this a request to discuss this during > the AgentX meeting in Chicago. ;-) ... Discussion of whatever the AgentX WG has to say on this topic is already on the proposed disman agenda. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." ----------------------------------------------------------------------- From sgudur@hotmail.com Fri Jul 31 16:54:02 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id QAA15658 for ; Fri, 31 Jul 1998 16:54:01 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA24660 for ; Fri, 31 Jul 1998 16:52:49 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma024107; Fri, 31 Jul 98 16:50:58 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA01706 for ; Fri, 31 Jul 1998 16:50:22 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma029842; Fri, 31 Jul 98 16:49:02 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA12543; Fri, 31 Jul 1998 16:49:34 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA15711 for ; Fri, 31 Jul 1998 14:45:37 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA23291 for ; Fri, 31 Jul 1998 16:45:35 -0500 (CDT) Received: from f185.hotmail.com(207.82.251.74) by almond.bmc.com via smap (V2.0) id xma023283; Fri, 31 Jul 98 16:45:29 -0500 Received: (qmail 29356 invoked by uid 0); 31 Jul 1998 21:45:24 -0000 Message-ID: <19980731214524.29355.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Fri, 31 Jul 1998 14:45:24 PDT X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: mithatch@cisco.com Cc: agentx@peer.com Subject: Re: open issues in agentX MIB Content-Type: text/plain Date: Fri, 31 Jul 1998 14:45:24 PDT Hi, Mike, There is relationship between sessionID defined in RFC2257 and the agentxSessionIndex. Current description for agentxSessionIndex includes: "Index values assigned for a given registration are constant for the lifetime of this table." is inappropriate and needs to be removed. The other part of the description is consistent with the RFC. "A unique index for the subagent session. Note that if a subagent's session with the master agent is closed for any reason its index should not be re-used, therefore, the values of agentxSessionIndex may not be contiguous and will generally not be the same for the same subagent across multiple sessions." thanks for the inputs. regards smitha >From mithatch@cisco.com Fri Jul 31 13:25:54 1998 >Received: from mithatch-ultra.cisco.com (mithatch-ultra.cisco.com [171.69.50.33]) by brownale.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id NAA08617; Fri, 31 Jul 1998 13:24:36 -0700 (PDT) >Received: from cisco.com (localhost [127.0.0.1]) by mithatch-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id NAA12501; Fri, 31 Jul 1998 13:24:35 -0700 (PDT) >Sender: mithatch@cisco.com >Message-ID: <35C22803.C5940BEE@cisco.com> >Date: Fri, 31 Jul 1998 13:24:35 -0700 >From: Mike Thatcher >X-Mailer: Mozilla 4.03C-CISCOENG [en] (X11; U; SunOS 5.5.1 sun4u) >MIME-Version: 1.0 >To: Smitha Gudur >CC: agentx@peer.com >Subject: Re: open issues in agentX MIB >References: <19980731173229.29029.qmail@hotmail.com> >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >If there is a relationship between sessionID as defined in RFC2257and >agentxSessionIndex then the relationship needs to be clarified and the >description of agentxSessionIndex made consistent with the definition in >the RFC. (See sections 6.1, 6.2.16, 7.1.1(3)) > >MikeT > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From martin@exmandato.se Fri Jul 31 17:07:26 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id RAA15768 for ; Fri, 31 Jul 1998 17:07:26 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA26635 for ; Fri, 31 Jul 1998 17:06:14 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma025882; Fri, 31 Jul 98 17:03:53 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id RAA12728 for ; Fri, 31 Jul 1998 17:03:15 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma011260; Fri, 31 Jul 98 17:02:02 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA15776; Fri, 31 Jul 1998 17:02:29 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA16380 for ; Fri, 31 Jul 1998 14:57:17 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA25126 for ; Fri, 31 Jul 1998 16:57:14 -0500 (CDT) Received: from oden.exmandato.se(192.71.33.1) by almond.bmc.com via smap (V2.0) id xma025120; Fri, 31 Jul 98 16:56:53 -0500 Received: from localhost (martin@localhost) by oden.exmandato.se (8.8.8/8.8.5) with SMTP id XAA00477; Fri, 31 Jul 1998 23:56:59 +0200 (MET DST) Date: Fri, 31 Jul 1998 23:56:59 +0200 (CEST) From: Martin Jacobsson Reply-To: Martin Jacobsson To: Smitha Gudur cc: agentx@peer.com Subject: Re: open issues in agentX MIB In-Reply-To: <19980731173229.29029.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 31 Jul 1998, Smitha Gudur wrote: > If there are any other open items that need to be addressed in the MIB, > I urge everyone on the mailing list to send them as early as possible. Section 2, goal 4 says: - Provide statistics about the protocol operation such as the number of packets to and from each subagent This information is not available through the mib as defined. One option is to add agentxSessionInPackets and agentxSessionOutPackets to the session table. And another is to add agentxConnInPackets, agentxConnOutPackets, agentxConnProtocolErrors and agentxConnParseErrors to the connection table. All as Counter32's. Then a port table would be nice, so that it is possible to see what ports the master agent accepts connections from and if it listens on any nondefault ports. A typical unix master agent will listen on both tcp port 705 and unix-domain socket "/var/agentx/master". /Martin Jacobsson --- .signature: No such file or directory From sgudur@hotmail.com Fri Jul 31 17:51:35 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id RAA16113 for ; Fri, 31 Jul 1998 17:51:35 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA01138 for ; Fri, 31 Jul 1998 17:50:22 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma029883; Fri, 31 Jul 98 17:46:39 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id RAA12121 for ; Fri, 31 Jul 1998 17:45:26 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma009261; Fri, 31 Jul 98 17:43:16 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA26848; Fri, 31 Jul 1998 17:43:47 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA25398 for ; Fri, 31 Jul 1998 15:30:07 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA27889 for ; Fri, 31 Jul 1998 17:30:06 -0500 (CDT) Received: from f139.hotmail.com(207.82.251.18) by almond.bmc.com via smap (V2.0) id xma027878; Fri, 31 Jul 98 17:29:43 -0500 Received: (qmail 1049 invoked by uid 0); 31 Jul 1998 22:29:42 -0000 Message-ID: <19980731222942.1048.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Fri, 31 Jul 1998 15:29:41 PDT X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: mithatch@cisco.com Cc: agentx@peer.com Subject: Re: open issues in agentX MIB Content-Type: text/plain Date: Fri, 31 Jul 1998 15:29:41 PDT >From mithatch@cisco.com Fri Jul 31 15:03:58 1998 >Received: from mithatch-ultra.cisco.com (mithatch-ultra.cisco.com [171.69.50.33]) by pleco.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id PAA29758; Fri, 31 Jul 1998 15:02:54 -0700 (PDT) >Received: from cisco.com (localhost [127.0.0.1]) by mithatch-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id PAA12637; Fri, 31 Jul 1998 15:02:54 -0700 (PDT) >Sender: mithatch@cisco.com >Message-ID: <35C23F0D.44E2CE36@cisco.com> >Date: Fri, 31 Jul 1998 15:02:53 -0700 >From: Mike Thatcher >X-Mailer: Mozilla 4.03C-CISCOENG [en] (X11; U; SunOS 5.5.1 sun4u) >MIME-Version: 1.0 >To: Smitha Gudur >Subject: Re: open issues in agentX MIB >References: <19980731214524.29355.qmail@hotmail.com> >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Smitha Gudur wrote: > >> Hi, Mike, >> >> There is relationship between sessionID defined in RFC2257 and >> the agentxSessionIndex. >> >> Current description for agentxSessionIndex includes: >> >> "Index values assigned for a given registration are constant for the >> lifetime of this table." >> >> is inappropriate and needs to be removed. >> >> The other part of the description is consistent with the RFC. >> >> "A unique index for the subagent session. Note that if a >> subagent's session with the master agent is closed for >> any reason its index should not be re-used, therefore, >> > >However the RFC does not restrict the reuse of sessionID. I agree, it does not restrict the usage but says that it should be globally unique over all its sessions if master agent supports multiple transports. The description has to be changed to make it unique across all the sessions that the master agent supports instead of saying it cannot be reused. smitha > >MikeT > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From bnatale@acecomm.com Fri Jul 31 17:51:38 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id RAA16117 for ; Fri, 31 Jul 1998 17:51:37 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA01156 for ; Fri, 31 Jul 1998 17:50:24 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma029915; Fri, 31 Jul 98 17:46:43 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id RAA12080 for ; Fri, 31 Jul 1998 17:45:24 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma009249; Fri, 31 Jul 98 17:43:15 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA26840; Fri, 31 Jul 1998 17:43:46 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA25406 for ; Fri, 31 Jul 1998 15:30:08 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA27891 for ; Fri, 31 Jul 1998 17:30:06 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by almond.bmc.com via smap (V2.0) id xma027887; Fri, 31 Jul 98 17:29:56 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) id 0z2NgO-0005N2-00; Fri, 31 Jul 1998 18:29:53 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA17422; Fri, 31 Jul 1998 18:32:10 -0400 Message-Id: <9807312232.AA17422@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 31 Jul 1998 18:32:19 -0400 To: "Smitha Gudur" From: Bob Natale Subject: Re: open issues in agentX MIB Cc: mithatch@cisco.com, agentx@peer.com In-Reply-To: <19980731214524.29355.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 7/31/98 02:45 PM, Smitha Gudur wrote: Hi Smitha, >There is relationship between sessionID defined in RFC2257 and >the agentxSessionIndex. Logically, that's true. The value used for agentxSessionIndex to identify the session should be the same as that used for the SessionID as given by the master agent to the subagent. The problem Mike alludes to here derives from the "should not be re-used" semantics used for agentxSessionIndex in the MIB but which are missing from the RFC references to SessionID. I would argue that the RFC text should be tightened in this respect, to stipulate non-reuse; but it is clear that a reasonable argument can be made for not stipulating it and leaving it up to the implementation. In my view, however, management apps will be able to use the MIB better to monitor the overall AgentX system if the non-reuse semantics of agentxSessionIndex are carried over to SessionID. This value, via agentxSessionIndex, is critical to all three of the tables currently defined in the MIB [btw, we should all be reading from the -02.txt version of the MIB document, dated April 14, 1998, at this point]: agentxConnectionTable agentxSessionTable agentxRegistrationTable In thinking through the relationships, it seems that we need to add agentxConnIndex to the AgentxSessionEntry and agentxSessionIndex to the AgentxRegistrationEntry. In this way, each registration entry can point to the session in which it lives and each session can point to the connection in which it lives. [Note to Smitha and Lauren here in particular:] The rationale and the consequent OBJECT-TYPE macros should be obvious (I think), but if not let me know. >Current description for agentxSessionIndex includes: > >"Index values assigned for a given registration are constant >for the lifetime of this table." > >is inappropriate and needs to be removed. Right. >The other part of the description is consistent with the RFC. That's the debatable part. >thanks for the inputs. Likewise. 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 bnatale@acecomm.com Fri Jul 31 18:09:46 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id SAA16276 for ; Fri, 31 Jul 1998 18:09:46 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id SAA03053 for ; Fri, 31 Jul 1998 18:08:33 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma002423; Fri, 31 Jul 98 18:06:27 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id SAA21465 for ; Fri, 31 Jul 1998 18:05:51 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma020384; Fri, 31 Jul 98 18:04:47 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA02097; Fri, 31 Jul 1998 18:05:20 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA10570 for ; Fri, 31 Jul 1998 15:56:45 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id RAA26038 for ; Fri, 31 Jul 1998 17:56:43 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by cashew.bmc.com via smap (V2.0) id xma026033; Fri, 31 Jul 98 17:56:17 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) id 0z2O5t-0000Op-00; Fri, 31 Jul 1998 18:56:14 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA17629; Fri, 31 Jul 1998 18:58:27 -0400 Message-Id: <9807312258.AA17629@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 31 Jul 1998 18:58:35 -0400 To: Martin Jacobsson From: Bob Natale Subject: Re: open issues in agentX MIB Cc: Smitha Gudur , agentx@peer.com In-Reply-To: References: <19980731173229.29029.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 7/31/98 11:56 PM, Martin Jacobsson wrote: Hi Martin, >Section 2, goal 4 says: > >- Provide statistics about the protocol operation such >as the number of packets to and from each subagent > >This information is not available through the mib as defined. >One option is to add agentxSessionInPackets and >agentxSessionOutPackets to the session table. And another is >to add agentxConnInPackets, agentxConnOutPackets, >agentxConnProtocolErrors and agentxConnParseErrors >to the connection table. All as Counter32's. First, let me note that there is considerable sentiment to keep this MIB relatively minimal. Second, you are right, if state such purposes (and the one you quote seems like a sound one to me). The approach that I would like to propose for this purpose is to add an agentxResponseTable. This would be indexed by agentxSessionID and consist of a set of objects (with syntax of GAUGE32, I suggest), one for each of the possible AgentX-Response-PDU res.error codes (including no_error). Such a table would handle overall (by simple summing), connection-specific (by mapping back to agentxConnectionTable via the agentxConnIndex in the corresponding agentxSessionTable row, and session-specific traffic and error counts for all active sessions. >Then a port table would be nice, so that it is possible to see >what ports the master agent accepts connections from I think this can be had now, via the agentxConnTransportDomain and agentxConnTransportAddress objects in the agentxConnectionTable. No...? >and if it listens on any nondefault ports. I'll pass on that one (I don't really see the need for it). >A typical unix master agent will listen on both tcp port >705 and unix-domain socket "/var/agentx/master". True...and the two objects mentioned above would, I think, tend to reveal that, given at least one active connection from each domain. 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 rpresuhn@dorothy.bmc.com Fri Jul 31 19:01:10 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA16677 for ; Fri, 31 Jul 1998 19:01:10 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id SAA06112 for ; Fri, 31 Jul 1998 18:59:58 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma005479; Fri, 31 Jul 98 18:57:55 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id SAA07221 for ; Fri, 31 Jul 1998 18:57:18 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma006045; Fri, 31 Jul 98 18:56:11 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA11777; Fri, 31 Jul 1998 18:56:43 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA24395 for agentx@peer.com; Fri, 31 Jul 1998 16:43:08 -0700 (PDT) Date: Fri, 31 Jul 1998 16:43:08 -0700 (PDT) From: Randy Presuhn Message-Id: <199807312343.QAA24395@dorothy.bmc.com> To: agentx@peer.com Subject: Re: open issues in agentX MIB Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Fri, 31 Jul 1998 18:58:35 -0400 > To: Martin Jacobsson > From: Bob Natale > Subject: Re: open issues in agentX MIB > Cc: Smitha Gudur , agentx@peer.com > References: <19980731173229.29029.qmail@hotmail.com> > > >At 7/31/98 11:56 PM, Martin Jacobsson wrote: > > Hi Martin, > > >Section 2, goal 4 says: > > > >- Provide statistics about the protocol operation such > >as the number of packets to and from each subagent ... > First, let me note that there is considerable sentiment to > keep this MIB relatively minimal. ... A counter-proposal to consider: delete goal 4 in section 2. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." -----------------------------------------------------------------------