From owner-agentx@dorothy.peer.com Fri Dec 3 20:42:26 1999 Received: from tangelo.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26699 for ; Fri, 3 Dec 1999 20:42:03 -0500 (EST) Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id TAA19017; Fri, 3 Dec 1999 19:37:26 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA08497 for agentx-list; Fri, 3 Dec 1999 17:18:48 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA08491; Fri, 3 Dec 1999 17:18:44 -0800 (PST) Date: Fri, 3 Dec 1999 17:18:44 -0800 (PST) From: Randy Presuhn Message-Id: <199912040118.RAA08491@dorothy.bmc.com> To: agentx@dorothy.peer.com, disman@dorothy.peer.com Subject: agentx & disman mailing list problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - Due to persistant NIS problems outside my control, you may see bounces for addresses associated with the agentx and disman mailing lists. I do not know when then problem is expected to be repaired. Since email for me is also bouncing erraticly, please contact me by telephone or fax for urgent list administration requests. -------------------------N-E-W---A-D-D-R-E-S-S-------------------------- Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ From owner-agentx@dorothy.peer.com Mon Dec 6 19:21:00 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28306 for ; Mon, 6 Dec 1999 19:20:56 -0500 (EST) Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id SAA15442; Mon, 6 Dec 1999 18:16:09 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA02238 for agentx-list; Mon, 6 Dec 1999 16:06:53 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id QAA02226 for ; Mon, 6 Dec 1999 16:05:26 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id SAA12928 for ; Mon, 6 Dec 1999 18:05:42 -0600 (CST) Received: from [38.249.211.2] (helo=relay1.acecomm.com) by relay10.smtp.psi.net with smtp (Exim 1.90 #1) for agentx@peer.com id 11v88N-0001r0-00; Mon, 6 Dec 1999 19:05:35 -0500 Received: from bnatale by relay1.acecomm.com (SMI-8.6/SMI-SVR4) id TAA18871; Mon, 6 Dec 1999 19:17:36 -0500 Message-Id: <4.2.2.19991206190512.00b09b50@nips.acec.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 06 Dec 1999 19:07:30 -0500 To: agentx@peer.com From: Bob Natale Subject: AgentX RFCs...? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Hi, I just wanted everyone to know that the AgentX RFCs are "in process" in the RFC editor's queue. You can check status at: > http://www.rfc-editor.org/queue.html I check this from time to time, but otherwise cannot do anything to hasten the process. Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ------------- Free downloads at www.winsnmp.com ------------- From owner-agentx@dorothy.peer.com Mon Dec 6 20:47:09 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06790 for ; Mon, 6 Dec 1999 20:47:08 -0500 (EST) Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id TAA29957; Mon, 6 Dec 1999 19:43:30 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA04618 for agentx-list; Mon, 6 Dec 1999 17:41:31 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA04612; Mon, 6 Dec 1999 17:41:26 -0800 (PST) Date: Mon, 6 Dec 1999 17:41:26 -0800 (PST) From: Randy Presuhn Message-Id: <199912070141.RAA04612@dorothy.bmc.com> To: agentx@dorothy.peer.com, disman@dorothy.peer.com Subject: Agentx & disman list woes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - Our IS folk assure my that the NIS nightmare is over for now. This means that the agentx@dorothy.bmc.com and disman@dorothy.bmc.com mailing lists should be working normally again. I have no reliable way of knowing how many adminstrative requests went into the bit bucket. If in the last two weeks you've made an administrative request for either of these lists and nothing has happened, please retransmit. I apologize for the inconvenience. -------------------------N-E-W---A-D-D-R-E-S-S-------------------------- Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ From owner-agentx@dorothy.peer.com Wed Dec 15 03:15:25 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27478 for ; Wed, 15 Dec 1999 03:15:20 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id CAA28774; Wed, 15 Dec 1999 02:12:00 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id AAA17198 for agentx-list; Wed, 15 Dec 1999 00:04:34 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id AAA17193 for ; Wed, 15 Dec 1999 00:04:28 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id CAA27428 for ; Wed, 15 Dec 1999 02:04:45 -0600 (CST) Received: from cisco.com ([192.135.245.163]) by cbinmail.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id NAA09919 for ; Wed, 15 Dec 1999 13:34:35 +0530 (IST) Message-ID: <38574AB4.A8673FDD@cisco.com> Date: Wed, 15 Dec 1999 13:30:52 +0530 From: Nalinaksh Pai Reply-To: npai@cisco.com Organization: Cisco Systems X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: agentx@dorothy.peer.com Subject: TimeStamp issues Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi, Consider the scenario where I need to give a unified view to a set of independant systems, each running its own OS and hardware. One such system runs the master agent and the others run the sub agent. Each subagent maintains its MIBs local to that box. The question I have here is, how do I handle sysUpTime and all the other objects related to sysUpTime. One way to do it would be, sysUpTime would be retrieved from the master agent MIB storage. But there are objects that have a particular sysUpTime timestamp as their value. Objects like ifTableLastChange store a timestamp when the ifTable was last changed. The ifTable needs to be represented as a common seamless table across all systems. The problem here is sysUpTime is not the same across all the systems, hence it is not right to assume that the maximum value of ifTableLastChange across all systems is 'the value' to be returned back to the management station. Does anybody have any suggestions as to how such objects that store timestamps can be correctly supported in the agentx framework? Regards, Nalin From owner-agentx@dorothy.peer.com Wed Dec 15 04:18:48 1999 Received: from tangelo.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27995 for ; Wed, 15 Dec 1999 04:18:47 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id DAA08142; Wed, 15 Dec 1999 03:16:12 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id BAA17354 for agentx-list; Wed, 15 Dec 1999 01:13:49 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA17349 for ; Wed, 15 Dec 1999 01:13:44 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id DAA07760 for ; Wed, 15 Dec 1999 03:14:02 -0600 (CST) Received: from ribble.server.csc.liv.ac.uk ([138.253.124.242]) by mailhub1.liv.ac.uk with esmtp (Exim 2.12 #1) id 11yAVR-0003cb-00; Wed, 15 Dec 1999 09:13:57 +0000 Received: from daves.staff.csc.liv.ac.uk (root@daves.staff.csc.liv.ac.uk [138.253.124.36]) by ribble.server.csc.liv.ac.uk (8.8.8/LUCS-DTS-3.0M10) with ESMTP id JAA26243; Wed, 15 Dec 1999 09:13:57 GMT 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 JAA02970; Wed, 15 Dec 1999 09:13:43 GMT Message-Id: <199912150913.JAA02970@daves.staff.csc.liv.ac.uk> X-Mailer: exmh version 2.0.2 To: npai@cisco.com Cc: agentx@dorothy.peer.com Subject: Re: TimeStamp issues In-Reply-To: Your message of "Wed, 15 Dec 1999 13:30:52 +0530." <38574AB4.A8673FDD@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 09:13:43 +0000 From: Dave Shield Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list > The question I have here is, how do I handle sysUpTime and all the other > objects related to sysUpTime. > > The problem here is sysUpTime is not the same across all the systems, > hence it is not right to assume that the maximum value of > ifTableLastChange across all systems is 'the value' to be returned back > to the management station. The way that I approached this for the UCD implementation, was to use the value of sysUpTime returned in the responses to administrative requests, and synchronise the subagent with the master. In particular, the subagent will re-set its idea of "when I started" whenever it receives a response PDU. Something like (slightly simplified): if (op == RECEIVED_MESSAGE) { if (pdu->command == AGENTX_MSG_RESPONSE) { /* * Synchronise sysUpTime with the master agent */ gettimeofday( &now, NULL ); diff.tv_sec = pdu->time/100; diff.tv_usec = (pdu->time - (diff.tv_sec * 100)) * 10000; starttime.tv_sec = now.tv_sec - diff.tv_sec; starttime.tv_usec = now.tv_usec - diff.tv_usec; } } Everything else can then use 'starttime' quite happily - nothing else realises that this refers to the master rather than the subagent. Hope this helps. Dave From owner-agentx@dorothy.peer.com Wed Dec 15 07:57:00 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00956 for ; Wed, 15 Dec 1999 07:56:59 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id GAA10478; Wed, 15 Dec 1999 06:53:31 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA18065 for agentx-list; Wed, 15 Dec 1999 04:51:18 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id EAA18060 for ; Wed, 15 Dec 1999 04:51:12 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id GAA10128 for ; Wed, 15 Dec 1999 06:51:30 -0600 (CST) Received: from cisco.com ([192.135.245.163]) by cbinmail.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id SAA18543; Wed, 15 Dec 1999 18:21:20 +0530 (IST) Message-ID: <38578DE8.29D5C2AB@cisco.com> Date: Wed, 15 Dec 1999 18:17:36 +0530 From: Nalinaksh Pai Reply-To: npai@cisco.com Organization: Cisco Systems X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Dave Shield CC: agentx@dorothy.peer.com Subject: Re: TimeStamp issues References: <199912150913.JAA02970@daves.staff.csc.liv.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi David, Thanks for your quickfire response. I totally agree with you that synchronizing the timestamps across the master agent and the subagent solves the basic problem. But there are some scenarios where this could lead to inconsistency in the sysUpTime values referenced by other objects. If the master agent goes down and comes up again, the value of the sysUpTime would be reset back in time. The subagent now would extract this sysUpTime from the agentx response PDU and reset its own sysUpTime reference base. But what about the MIB objects on the subagent who have stored values w.r.to the previous time scale of the sysUpTime before the master agent went down? I understand that one way to tackle this problem is to actually live with it !!!!! I wanted to know whether such issues were taken care of in the UCD implementation and if yes then how. Comments welcome. Nalin Dave Shield wrote: > > The question I have here is, how do I handle sysUpTime and all the other > > objects related to sysUpTime. > > > > The problem here is sysUpTime is not the same across all the systems, > > hence it is not right to assume that the maximum value of > > ifTableLastChange across all systems is 'the value' to be returned back > > to the management station. > > The way that I approached this for the UCD implementation, was to use > the value of sysUpTime returned in the responses to administrative > requests, and synchronise the subagent with the master. > In particular, the subagent will re-set its idea of "when I started" > whenever it receives a response PDU. Something like (slightly simplified): > > if (op == RECEIVED_MESSAGE) { > if (pdu->command == AGENTX_MSG_RESPONSE) { > > /* > * Synchronise sysUpTime with the master agent > */ > gettimeofday( &now, NULL ); > diff.tv_sec = pdu->time/100; > diff.tv_usec = (pdu->time - (diff.tv_sec * 100)) * 10000; > starttime.tv_sec = now.tv_sec - diff.tv_sec; > starttime.tv_usec = now.tv_usec - diff.tv_usec; > } > } > > Everything else can then use 'starttime' quite happily - nothing else > realises that this refers to the master rather than the subagent. > > Hope this helps. > > Dave -- Nalinaksh Pai Software Engineer Cisco Systems Phone: 91-022-2289931 Ext: 5007 Email: npai@cisco.com Epage: nalpai@cbinpage.cisco.com From owner-agentx@dorothy.peer.com Wed Dec 15 15:39:54 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27747 for ; Wed, 15 Dec 1999 13:08:20 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id MAA16258; Wed, 15 Dec 1999 12:03:18 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA18962 for agentx-list; Wed, 15 Dec 1999 09:59:19 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA18956 for agentx@dorothy.bmc.com; Wed, 15 Dec 1999 09:59:16 -0800 (PST) Date: Wed, 15 Dec 1999 09:59:16 -0800 (PST) From: Randy Presuhn Message-Id: <199912151759.JAA18956@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: Re: TimeStamp issues Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - > Date: Wed, 15 Dec 1999 18:17:36 +0530 > From: Nalinaksh Pai > To: Dave Shield > CC: agentx@dorothy.peer.com > Subject: Re: TimeStamp issues > References: <199912150913.JAA02970@daves.staff.csc.liv.ac.uk> > List-Id: IETF Agentx Working Group mailing list ... > If the master agent goes down and comes up again, the value of the sysUpTime > would be reset back in time. The subagent now would extract this sysUpTime > from the agentx response PDU and reset its own sysUpTime reference base. But > what about the MIB objects on the subagent who have stored values w.r.to the > previous time scale of the sysUpTime before the master agent went down? ... TimeStamps are misnamed. They have lots of problems, discussed on this list as far back as 1996, and in greater depth on the SNMPv3 list in the thread entitled "Epochal discontinuity" starting in June of 1998. This resulted in clarification of the TimeStamp definition in RFC 2579, which requires the stale TimeStamps to be reset to zero in the scenario you described. ------------------------------------------------------------------------ Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ From owner-agentx@dorothy.bmc.com Thu Dec 23 13:55:50 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01370 for ; Thu, 23 Dec 1999 13:55:49 -0500 (EST) Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id MAA13248; Thu, 23 Dec 1999 12:53:11 -0600 (CST) Received: (from root@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id KAA00167 for agentx-list; Thu, 23 Dec 1999 10:47:13 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA00161 for agentx@dorothy.bmc.com; Thu, 23 Dec 1999 10:47:09 -0800 (PST) Date: Thu, 23 Dec 1999 10:47:09 -0800 (PST) From: Randy Presuhn Message-Id: <199912231847.KAA00161@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: AgentX in Java Mime-Version: 1.0 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 Hi - Last summary a query was posted to this list regarding Java implementations of AgentX. I haven't seen any responses, and was wondering if anyone has done anything in this area. ------------------------------------------------------------------------ Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ From owner-agentx@dorothy.bmc.com Tue Dec 28 10:44:50 1999 Received: from tangelo.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01146 for ; Tue, 28 Dec 1999 10:44:49 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id JAA25586; Tue, 28 Dec 1999 09:41:03 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id HAA10977 for agentx-list; Tue, 28 Dec 1999 07:31:29 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA10972 for ; Tue, 28 Dec 1999 07:31:24 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id JAA22935 for ; Tue, 28 Dec 1999 09:31:44 -0600 (CST) Message-ID: <19991228153130.135.qmail@web3107.mail.yahoo.com> Received: from [136.182.2.221] by web3107.mail.yahoo.com; Tue, 28 Dec 1999 07:31:30 PST Date: Tue, 28 Dec 1999 07:31:30 -0800 (PST) From: gopal krishna Subject: snmp traps in agentx To: agentx@dorothy.peer.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 hi, i need some clarification regarding traps. suppose subagents are required to send traps to snmp managers (by either the ipaddress or host name of managers). the subagents are required to 1a) Send traps to a particular manager for some of the events. 1b) Same trap to more than one managers for other events 2) also Is it possible for the individual subagents to specify even the version of traps (i.e, snmp v1 or v2 trap) that should be sent to snmp managers in the case 1)a & 1)b is there any scope for this kind of operation in AgentX. if this is considered as implementation specific, what would be the ideal solution . regards, gopal __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com From owner-agentx@dorothy.bmc.com Tue Dec 28 11:08:21 1999 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01428 for ; Tue, 28 Dec 1999 11:08:20 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id KAA02579; Tue, 28 Dec 1999 10:04:44 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA11039 for agentx-list; Tue, 28 Dec 1999 08:02:50 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA11034 for ; Tue, 28 Dec 1999 08:02:45 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id KAA02080 for ; Tue, 28 Dec 1999 10:03:06 -0600 (CST) Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345) id C0DB11F4; Tue, 28 Dec 1999 11:03:05 -0500 (EST) Received: from iota.zk3.dec.com (iota.zk3.dec.com [16.140.32.65]) by zmamail02.zma.compaq.com (Postfix) with ESMTP id AC9C63C0; Tue, 28 Dec 1999 11:03:05 -0500 (EST) Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM) id LAA0000002442; Tue, 28 Dec 1999 11:03:04 -0500 (EST) Message-ID: <3868DE97.A83D8DBE@zk3.dec.com> Date: Tue, 28 Dec 1999 11:00:23 -0500 From: Mike Daniele Organization: Compaq 64-bit UNIX networking X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V5.0 alpha) X-Accept-Language: en MIME-Version: 1.0 To: gopal krishna Cc: agentx@dorothy.peer.com Subject: Re: snmp traps in agentx References: <19991228153130.135.qmail@web3107.mail.yahoo.com> 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 Hi Gopal, See section 7.1.10 of the latest draft, http://www.ietf.org/internet-drafts/draft-ietf-agentx-rfc-update-03.txt AgentX subagents pass notification information to master agents in SNMPv2 format (must include snmpTrapOID.0). From there the master agent decides which targets (managers) may or may not receive it, and in which SNMP version to encode the information. This has typically been done via implementation-specific configuration files. RFC 2573 defines MIB objects for targets (manager addresses) and notification generation. Regards, Mike gopal krishna wrote: > hi, > > i need some clarification regarding traps. > > suppose subagents are required to send traps to > snmp managers (by either > the ipaddress or host name of managers). > > the subagents are required to > > 1a) Send traps to a particular manager for some of > the events. > > 1b) Same trap to more than one managers for other > events > > 2) also Is it possible for the individual subagents to > specify even the version of traps > (i.e, snmp v1 or v2 trap) that should be sent to > snmp managers in the case 1)a & 1)b > > is there any scope for this kind of operation in > AgentX. > > if this is considered as implementation specific, > what would be the ideal solution . > > regards, > gopal > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://messenger.yahoo.com