Delivery-Date: Mon, 01 Apr 1996 08:33:36 -0800 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id IAA20458 for X-agentx-local; Mon, 1 Apr 1996 08:33:36 -0800 (PST) Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id IAA20448 for ; Mon, 1 Apr 1996 08:33:33 -0800 (PST) Received: from flume.zk3.dec.com by mail12.digital.com (5.65v3.2/1.0/WV) id AA13136; Mon, 1 Apr 1996 11:29:26 -0500 Received: from bernie.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA17004; Mon, 1 Apr 1996 11:29:04 -0500 Received: from localhost by bernie.zk3.dec.com; (5.65v3.2/1.1.8.2/20Nov95-1250PM) id AA07259; Mon, 1 Apr 1996 11:29:39 -0500 Message-Id: <9604011629.AA07259@bernie.zk3.dec.com> To: Randy Presuhn Cc: agentx@fv.com Subject: Re: 06: Master/Component "Binding" - Transport/IPC In-Reply-To: Your message of "Thu, 28 Mar 96 15:02:23 PST." <199603282302.AA033614143@dorothy.peer.com> Date: Mon, 01 Apr 96 11:29:39 -0500 From: Mike Daniele X-Mts: smtp Hi Randy, >Depending on which version of SNMPv2 is in use, MMS is a property of > - the party to which the operation's response should be sent > - the transport over which the operation's repsonse should be sent > - a proposed MMS carried directly in the request >In all of these cases, the MMS consequently may vary from request to >request. For this reason, a MMS as part of the OPEN exchange would >be of questionable value. What I'm referring to isn't the SNMP MMS. It's an AgentX "max buffer size", for want of a better term. Sorry for the confusion. >Determination of tooBig must occur on a request-by-request basis, I agree. But I think the folks on the list are asking how to know what a master agent's overall maximum AgentX message/buffer size can be, for transports where this notion is meaningful. I'd like to avoid "negotiation" of this value, and simply have the master agent state once what it is (where applicable). Regards, Mike   Delivery-Date: Mon, 01 Apr 1996 09:40:45 -0800 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id JAA08652 for X-agentx-local; Mon, 1 Apr 1996 09:40:45 -0800 (PST) Received: from uu10.psi.com (uu10.psi.com [38.8.4.2]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id JAA08648 for ; Mon, 1 Apr 1996 09:40:44 -0800 (PST) Received: from acec.com by uu10.psi.com (5.65b/4.0.061193-PSI/PSINet) via SMTP; id AA22767 for ; Mon, 1 Apr 96 11:44:02 -0500 Received: from natale by nips.acec.com (5.65/3.2.083191-American Computer and Electronics Corp. ) id AA29625; Mon, 1 Apr 1996 12:25:55 -0500 Date: Mon, 1 Apr 1996 12:27:10 EST From: Bob Natale Subject: Simple-Times issue on agent extensibility To: agentx@fv.com Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi, I imagine most members of this list already subscribe to {The Simple Times} and will, therefore, have already seen the current issue (vol 4, no 2)... But just in case there are some on the list who have not, that issue is dedicated to agent extensibility, with five technical articles: - Intro Bob Natale - Solution Space Dale Francisco - Problem Space Randy Presuhn - eSNMP Mike Daniele - Proxy Alternative Dave Bridgham You can access this issue (and back issues) on the web via: http://www.simple-times.org/pub/simple-times/issues While all the substantive articles are very good, I am hopeful that we can use Randy's as an additional tool in helping us to reach closure and consensus on a number of the remaining issues in the coming weeks. The e-mail discussions have been very helpful thus far, but we need to hone in on more closures to enable Mike and Bert to proceed with the spec mods that Dale can turn into a consistent, readable draft spec. Cordially, BobN ------- WinSNMP DLL, SDK, and Applets for Win16 and Win32 ------ Bob Natale | ACE*COMM | 301-258-9850 [v] Dir, Net Mgmt Prod | 209 Perry Pkwy | 301-921-0434 [f] natale@acec.com | Gaithersburg MD 20877 | http://www.acec.com ------- NetPlus (r) "FCAPS" Telemanagement Applications --------   Delivery-Date: Fri, 12 Apr 1996 03:50:58 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id DAA17817 for X-agentx-local; Fri, 12 Apr 1996 03:50:58 -0700 (PDT) Received: from netra.soft.net (netra.soft.net [164.164.128.17]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id DAA17804 for ; Fri, 12 Apr 1996 03:50:52 -0700 (PDT) Received: from plutonium.bflsl.soft.net. by netra.soft.net (5.x/SMI-SVR4) id AA24540; Fri, 12 Apr 1996 16:16:22 +0500 Received: by plutonium.bflsl.soft.net. (5.x/SMI-SVR4) id AA16529; Fri, 12 Apr 1996 16:19:28 -0400 From: bflram@plutonium.bflsl.soft.net (Ramaprasad K.R.) Message-Id: <9604122019.AA16529@plutonium.bflsl.soft.net.> Subject: sub-agent development on Solaris 2.4/2.5 To: snmp@psi.com Date: Fri, 12 Apr 1996 16:19:27 -0400 (EDT) Cc: agentx@fv.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Hi, I need to know if there is any toolkit available, on Solaris, for development of sub-agents to support some enterprise specific MIBs ? More importantly, does Solaris have an extensible agent ? Awaiting replies and thanks in advance.. -- -regards rampi -----------------------------------------------------------------------   Delivery-Date: Fri, 12 Apr 1996 14:02:57 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id OAA29283 for X-agentx-local; Fri, 12 Apr 1996 14:02:57 -0700 (PDT) Received: from mail.st.rim.or.jp (mail.st.rim.or.jp [202.255.181.5]) by zloty.fv.com (8.7.4/8.7.3) with ESMTP id OAA29277 for ; Fri, 12 Apr 1996 14:02:55 -0700 (PDT) Received: from yamai (ppp448.st.rim.or.jp [202.247.132.48]) by mail.st.rim.or.jp (8.7.5/3.4W3-rim1.1) with SMTP id FAA00404; Sat, 13 Apr 1996 05:57:35 +0900 (JST) Date: Sat, 13 Apr 1996 05:57:35 +0900 (JST) Message-Id: <199604122057.FAA00404@mail.st.rim.or.jp> To: bflram@plutonium.bflsl.soft.net, snmp@psi.com Cc: agentx@fv.com Subject: Re: sub-agent development on Solaris 2.4/2.5 From: Masayuki Yamai X-Mailer: Winbiff [version 1.22 (on Trial)] References: <9604122019.AA16529@plutonium.bflsl.soft.net.> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Hello Please contact SNMP Resarch. info@snmp.com http://www.snmp.com john@int.snmp.com They have EMANATE for Solaris. The EMANATE is extenshible agent system. That include sub-agnet development KIT. Thanks /YMI In message <9604122019.AA16529@plutonium.bflsl.soft.net.> "sub-agent development on Solaris 2.4/2.5" "bflram@plutonium.bflsl.soft.net (Ramaprasad K.R.)" wrote. bflram> Hi, bflram> bflram> I need to know if there is any toolkit available, on Solaris, for bflram> development of sub-agents to support some enterprise specific bflram> MIBs ? bflram> bflram> More importantly, does Solaris have an extensible agent ? bflram> bflram> Awaiting replies and thanks in advance.. bflram> -- bflram> -regards bflram> rampi bflram> -----------------------------------------------------------------------   Delivery-Date: Fri, 12 Apr 1996 19:21:53 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id TAA01329 for X-agentx-local; Fri, 12 Apr 1996 19:21:52 -0700 (PDT) Received: from TIAMAT.DRAGON.COM (tiamat.dragon.com [155.229.20.2]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id TAA01318 for ; Fri, 12 Apr 1996 19:21:49 -0700 (PDT) From: cheryl@empiretech.com Received: by dragon.com (MX V4.1 VAX) with UUCP; Fri, 12 Apr 1996 14:01:53 EST Received: (from cheryl@localhost) by emptech.empiretech.com (8.6.12/8.6.12) id NAA09186; Fri, 12 Apr 1996 13:57:22 -0400 Message-ID: <199604121757.NAA09186@emptech.empiretech.com> Subject: Re: sub-agent development on Solaris 2.4/2.5 To: Date: Fri, 12 Apr 1996 13:57:22 -0400 (EDT) CC: snmp@psi.com, agentx@fv.com In-Reply-To: <9604122019.AA16529@plutonium.bflsl.soft.net.> from "Ramaprasad K.R." at Apr 12, 96 04:19:27 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > >Hi, > >I need to know if there is any toolkit available, on Solaris, for >development of sub-agents to support some enterprise specific >MIBs ? > >More importantly, does Solaris have an extensible agent ? Empire's "Agent Builder(tm)" provides the source code and libraries for a monolythic SNMP agent to which you can add your own enterprise specific extensions. The product also includes the source code for the MIB-II method routines for Solaris 2.x. (I can provide you additional information off-line if you'd like). > >Awaiting replies and thanks in advance.. Cheers, Cheryl >-- >-regards >rampi +--------------------------------------------------------------------+ + Check us out! http://www.empiretech.com/empiretech + +--------------------------------------------------------------------+ + Cheryl Krupczak Empire Technologies, Inc. + + cheryl@empiretech.com 541 Tenth Street NW + + PH : (770)384-0184 Suite 169 + + FAX: (770)384-0183 Atlanta, GA 30318 + +--------------------------------------------------------------------+   Delivery-Date: Mon, 15 Apr 1996 11:21:41 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id LAA29029 for X-agentx-local; Mon, 15 Apr 1996 11:21:41 -0700 (PDT) Received: from netall.netalliance.net (mercury.netalliance.net [205.242.0.2]) by zloty.fv.com (8.7.4/8.7.3) with ESMTP id LAA29021 for ; Mon, 15 Apr 1996 11:21:40 -0700 (PDT) Received: from [205.242.0.24] (saturn.netalliance.net) by netalliance.net (PMDF V5.0-4 #15221) id <01I3KLPCXKRK9D4HLP@netalliance.net> for agentx@fv.com; Mon, 15 Apr 1996 13:21:26 -0600 (CST) Date: Mon, 15 Apr 1996 13:21:26 -0600 (CST) Date-warning: Date header was inserted by netalliance.net From: kelly.breit@netalliance.net (Kelly Breit) Subject: subscribe X-Sender: kbreit@netalliance.net To: agentx@fv.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: 7BIT   Delivery-Date: Mon, 15 Apr 1996 16:44:10 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id QAA10740 for X-agentx-local; Mon, 15 Apr 1996 16:44:10 -0700 (PDT) Received: from uu10.psi.com (uu10.psi.com [38.8.4.2]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id QAA10723 for ; Mon, 15 Apr 1996 16:44:04 -0700 (PDT) Received: from acec.com by uu10.psi.com (5.65b/4.0.061193-PSI/PSINet) via SMTP; id AA12023 for ; Mon, 15 Apr 96 07:44:04 -0400 Received: from natale by nips.acec.com (5.65/3.2.083191-American Computer and Electronics Corp. ) id AA03593; Mon, 15 Apr 1996 11:02:42 -0400 Date: Mon, 15 Apr 1996 11:05:11 EDT From: Bob Natale Subject: AgentX Web Site, etc. To: agentx@fv.com Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi everyone, I would like to announce the availability of the AgentX web site: http://www.scguild.com/agentx/ On behalf of the entire wg, thanks and kudos to David Keeney (keeney@mv.mv.com) for arranging for the facilities, setting up the site, and serving as Webmaster. Check it out...especially the open issues section...while all issues are shown as open right now, we've actually closed a few sub-issues (and I will get their status colors changed), and let's try to orient some discussions toward closing even more of them. One helpful tool for doing that may be Randy's article in the April issue of {The Simple Times}...which outlined (fairly succinctly) some of the major issues, offered a consensus summary, and proposed some suggested resolutions. I am in the process of getting two AgentX meetings scheduled for the Montreal IETF (end of June). Our schedule revisions made it through review by Deirdre and the IESG and our charter (hot-linked via the web site) now reflects the new dates. This means that we have to do everything we can to make it possible for Mike and Bert to cast our decisions in terms of mods to the DPI-2 specs...not to mention enabling Dale to get the actual AgentX Protocol I-D out in time. Finally, although I was in the military in the late 60s, I failed to learn the lesson "never volunteer". I "volunteered" late last week to help the good people at Intel administer the WinSNMP e-mail list...it didn't have a lot of admin problems (just a handful of bad addresses that bounced when anyone posted a message), but Intel seemed to be running behind on fixing them and I thought another set of fingers could help. They liked that idea, but inadvertently (?...:-) signed me up as "owner" for the (much larger) WinSock and WinSock-2 e-mail lists...and I got totally overwelmed by an avalanche (7-800) garbage messages over the weekend. In my haste to avoid impacting other users at my site, I accidently deleted about a week's worth of messages I was holding for later review/response. So, if you sent me anything in the past week or so that I have not yet responded to and you still want a response to it, please re-send it to me. Thanks. Now, let's get to work on the AgentX issues, please! Cordially, BobN ------- WinSNMP DLL, SDK, and Applets for Win16 and Win32 ------ Bob Natale | ACE*COMM | 301-258-9850 [v] Dir, Net Mgmt Prod | 209 Perry Pkwy | 301-921-0434 [f] natale@acec.com | Gaithersburg MD 20877 | http://www.acec.com ------- NetPlus (r) "FCAPS" Telemanagement Applications --------   Delivery-Date: Fri, 19 Apr 1996 10:16:23 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id KAA25035 for X-agentx-local; Fri, 19 Apr 1996 10:16:23 -0700 (PDT) Received: from netra.soft.net (netra.soft.net [164.164.128.17]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id KAA25011 for ; Fri, 19 Apr 1996 10:16:17 -0700 (PDT) Received: from plutonium.bflsl.soft.net. by netra.soft.net (5.x/SMI-SVR4) id AA03291; Fri, 19 Apr 1996 22:41:52 +0500 Received: by plutonium.bflsl.soft.net. (5.x/SMI-SVR4) id AA05814; Fri, 19 Apr 1996 22:44:57 -0400 From: bflram@plutonium.bflsl.soft.net (Ramaprasad K.R.) Message-Id: <9604200244.AA05814@plutonium.bflsl.soft.net.> Subject: 22: agentX MIB To: agentx@fv.com Date: Fri, 19 Apr 1996 22:44:56 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Hi, Few doubts in the saMIB. In saMIB, the following timeout values have been defined : saDefaultTimeout OBJECT-TYPE SYNTAX INTEGER -- (1..saMaxTimeout) -- UNITS "seconds" ACCESS read-write STATUS mandatory DESCRIPTION "The default timeout (in seconds) that this agent waits for a response from a SubAgent. This value is used if a timeout value is not specified for the subtree nor for the subagent that exports the subtree." -- DEFVAL { 5 } ::= { saMIB 1 } saMaxTimeout OBJECT-TYPE SYNTAX INTEGER (1..3600) -- 3600 is 60 minutes, -- so quite big already -- UNITS "seconds" ACCESS read-write STATUS mandatory DESCRIPTION "The maximum timeout (in seconds) that this agent allows for timeout values for SubAgents. When you try to set any other timeout value it must be between 1 and this maximum value." -- DEFVAL { 60 } ::= { saMIB 2 } ....... saTimeout OBJECT-TYPE SYNTAX INTEGER -- (1..saMaxTimeout) -- UNITS "seconds" ACCESS read-write STATUS mandatory DESCRIPTION "The default timeout (seconds) for a SubAgent response. This value will be used if there is no timeout value specified for a particular subtree." -- DEFVAL { 0 } ::= { saEntry 11 } ........ saTtimeout OBJECT-TYPE SYNTAX INTEGER -- (1..saMaxTimeout) -- UNITS "seconds" ACCESS read-write STATUS mandatory DESCRIPTION "The timeout (in seconds) for objects in this subtree. A value of zero (0) means that the overall timeout value (as specified in the saTableEntry for the SubAgent) will be used." -- DEFVAL { 0 } ::= { saTreeEntry 5 } saDefaultTimeout, saTimeout and saTtimeout all depend on the variable saMaxTimeout. saMaxTimeout itself is read-write object. If this MIB is made visible to the manager, and the manager sets the value of saMaxTimeout to a value lower than the other timeout values which would have been negotiated already, then how will the master agent behave ? Should the master-agent send out information to the sub-agents that the saMaxTimeout value is being changed or should the sub-agents keep checking the value of this object maintained by master-agent ? -- -regards rampi -----------------------------------------------------------------------   Delivery-Date: Fri, 19 Apr 1996 11:26:37 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id LAA12507 for X-agentx-local; Fri, 19 Apr 1996 11:26:36 -0700 (PDT) Received: from VNET.IBM.COM (vnet.ibm.com [199.171.26.4]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id LAA12504 for ; Fri, 19 Apr 1996 11:26:35 -0700 (PDT) Message-Id: <199604191826.LAA12504@zloty.fv.com> Received: from UITVM1 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 5587; Fri, 19 Apr 96 14:25:35 EDT Date: Fri, 19 Apr 96 20:25:58 DST From: "Bert Wijnen" To: bflram@plutonium.bflsl.soft.net, agentx@fv.com Subject: 22: agentX MIB Ref: Your note of Fri, 19 Apr 1996 22:44:56 -0400 (EDT) Subject: 22: agentX MIB The question about the timeout values in relation to saMaxTimeout In my current implementation If saMaxTimeout gets changed, then I just change that value and leave the already negotiated timeouts untouched. I think that that is OK. Maybe we should add that we suggest that this value prefereably be kept on nonvolatile storage so that it is in effect with the next reboot. If a manager wants a subagent to change, he/she can set the saStatus to invalid which will break the connection to the subagent. The subagent then probably (at least I assume so) reconnect and will then be limited to the new saMaxTimeout. Bert Wijnen   Delivery-Date: Mon, 22 Apr 1996 06:56:29 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id GAA29172 for X-agentx-local; Mon, 22 Apr 1996 06:56:29 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [146.254.1.1]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id GAA28982 for ; Mon, 22 Apr 1996 06:55:48 -0700 (PDT) Received: from ztivax.zfe.siemens.de (ztivax.siemens.de) by david.siemens.de with SMTP id AA05705 (5.67a/IDA-1.5 for ); Mon, 22 Apr 1996 15:55:32 +0200 Received: from VSGWSMTP1.ZFE.SIEMENS.DE (vsgwsmtp1) by ztivax.zfe.siemens.de with SMTP id AA06467 (5.67a/IDA-1.5 for ); Mon, 22 Apr 1996 15:55:32 +0200 Received: by VSGWSMTP1.ZFE.SIEMENS.DE with Microsoft Mail id <317C0E5D@VSGWSMTP1.ZFE.SIEMENS.DE>; Mon, 22 Apr 96 15:55:25 PDT From: "Fozdar, Farhad VS extern" To: "'smtp:agentx@fv.com'" Subject: 14:sysUpTime Date: Mon, 22 Apr 96 15:55:00 PDT Message-Id: <317C0E5D@VSGWSMTP1.ZFE.SIEMENS.DE> Encoding: 24 TEXT X-Mailer: Microsoft Mail V3.0 Hi, I'm new here, so apologies if this is inappropriate or repeated... In its current form, the sysUpTime object has limited usefulness as a timestamp. Perhaps it's semantics could be re-defined with some absolute or repeating origin. For example, at midnight a 'logical' (timer) restart could be defined, with the consequence that all traps and other references to sysUpTime would appear as the actual (local) time of the occurrence (in hundredths of a sec). Provided that all agents have an appropriate real-time clock, the time they report will then have global significance. The counter would wrap every midnight at the value 8,640,000 (or a bit higher if leap-seconds were accommodated). This begs the question of clock synchronization between agents, however this can be achieved by CMOS clocks, operating system time synchronization facilities, etc. If an object is required to determine the 'real' restart time, perhaps a new timestamp should be defined for this use. Farhad Fozdar   Delivery-Date: Mon, 22 Apr 1996 11:20:20 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id LAA04864 for X-agentx-local; Mon, 22 Apr 1996 11:20:19 -0700 (PDT) Received: from ciena.com (ciena.com [204.240.57.2]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id LAA04857 for ; Mon, 22 Apr 1996 11:20:17 -0700 (PDT) Received: from opus.ciena.com ([38.254.48.12]) by ciena.com (4.1/SMI-4.1) id AA22126; Mon, 22 Apr 96 14:17:54 EDT Received: by opus.ciena.com (SMI-8.6/SMI-SVR4) id OAA13276; Mon, 22 Apr 1996 14:19:24 -0400 Date: Mon, 22 Apr 1996 14:19:24 -0400 From: jwest@ciena.com (Jim West) Message-Id: <199604221819.OAA13276@opus.ciena.com> To: Farhad.Fozdar@vs.siemens.de Subject: Re: 14:sysUpTime Cc: agentx@fv.com X-Sun-Charset: US-ASCII > From: "Fozdar, Farhad VS extern" > Subject: 14:sysUpTime > Date: Mon, 22 Apr 96 15:55:00 PDT > Hi, > > I'm new here, so apologies if this is inappropriate or repeated... > > In its current form, the sysUpTime object has limited usefulness as a > timestamp. Perhaps it's semantics could be re-defined with some absolute or > repeating origin. Can't do this. The usefulness of sysUpTime makes for an interesting debate, but considering the installed base of agents and managers, you just can go and change the semantics of this object. >For example, at midnight a 'logical' (timer) restart could > be defined, with the consequence that all traps and other references to > sysUpTime would appear as the actual (local) time of the occurrence (in > hundredths of a sec). Provided that all agents have an appropriate real-time > clock, the time they report will then have global significance. But the are a lot of agents that don't have a real time clock; maybe they don't have a clock that has a battery backup (so when the system boots, it may not know what time it is). You can't assume that all will always have access to accurate time information. Jim West CIENA Optical Communications   Delivery-Date: Tue, 23 Apr 1996 07:17:44 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id HAA26317 for X-agentx-local; Tue, 23 Apr 1996 07:17:44 -0700 (PDT) Received: from bbnplanet.com (poblano.near.net [198.114.157.116]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id HAA26313 for ; Tue, 23 Apr 1996 07:17:43 -0700 (PDT) Received: from poblano.near.net by poblano.bbnplanet.com id aa27481; 23 Apr 96 10:17 EDT To: agentx@fv.com From: David Waitzman Subject: HP OV proxy agent support? Date: Tue, 23 Apr 1996 10:17:26 -0400 Sender: djw@bbnplanet.com Message-ID: <9604231017.aa27481@poblano.bbnplanet.com> I have an manager support of agent extension question that I was hoping that someone on the list can answer. Can someone please tell me how well HP OV NNM (3.x, pre-Tornado) handles SNMP proxy agents (per the recent Simple Times article by Dave Bridgham) or point me to the right place? The HP OV documentation I have is not sufficient-- it barely mentions a "proxy" configuration option that may not be addressing this anyway. What I mean by handle is to have one icon on the map for a particular system. When you send a query using the historical query stuff, the MIB browser or other applications, it should automatically send the SNMP packets to the correct agent on the device (via the proxy) based upon the part of the MIB being queried. thanks, -david waitzman   Delivery-Date: Tue, 23 Apr 1996 11:50:54 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id LAA04820 for X-agentx-local; Tue, 23 Apr 1996 11:50:54 -0700 (PDT) Received: from uu10.psi.com (uu10.psi.com [38.8.4.2]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id LAA04813 for ; Tue, 23 Apr 1996 11:50:52 -0700 (PDT) Received: from acec.com by uu10.psi.com (5.65b/4.0.061193-PSI/PSINet) via SMTP; id AA10947 for ; Tue, 23 Apr 96 11:09:17 -0400 Date: Tue, 23 Apr 1996 14:31:04 -0400 From: natale@acec.com (Bob Natale) Received: by nips.acec.com (5.65/3.2.083191-American Computer and Electronics Corp. ) id AA05161; Tue, 23 Apr 1996 14:31:04 -0400 Message-Id: <9604231831.AA05161@nips.acec.com> To: agentx@fv.com Subject: AgentX sessions at Montreal IETF Hi everyone, I apologize for being rather inactive on this (and the WinSNMP) list lately...my task stack has been growing out of control...I am trying to work it down and/or fork some of it off to other processors, but it seems like the input port is being flooded with valid messages from high priority sources! Anyway, I wanted to give you the earliest possible notice of the AgentX session schedule for the Montreal IETF, which I just received a few minutes ago: > This is to confirm two sessions for AGENTX as follows: > > Tuesday, June 25 at 0900 (opposite atommib, pkix, rps, ipngwg) > Wednesday, June 26 at 1530 (opposite dhc, ipsec) This will be a very important IETF for AgentX, so I hope you can all attend. We need to work up an agenda and submit it to the IETF planners within the next week or so. Per our new charter schedule, the main topic of the meeting should be review of the draft of the core AgentX protocol specification. This draft will have been posted by the meeting deadline (probably around June 7). I know that Mike and Bert have been corresponding about some of the mods to the DPIv2 protocol that need to be made; and Dale has been preparing for handling the actual editing and document production tasks. Maria and I both have to get something started on the AgentX MIB and API specifications, respectively. I am hopeful that Maria will be able to follow-up with Jeff on his offer to make his reserveration MIB available as a starting point. Also, I owe it to Dave Keeney to visit the AgentX web site in detail and provide a status update on all the open issues. I will try to do this no later than the coming weekend and will, of course, post a synopsis on each one on the list...most likely with a strawman resolution of each (relying, in part, on Randy's article in the Simple-Times AgentX issue). This will, I hope, contribute to the on-list discussion of the issues for the benefit of helping Mike, Bert, and Dale to complete the core protocol draft spec. Of course, everyone is encouraged to submit their own comments to the list at any time. Cordially, BobN ------- WinSNMP DLL, SDK, and Applets for Win16 and Win32 ------ Bob Natale | ACE*COMM | 301-258-9850 [v] Dir, Net Mgmt Prod | 209 Perry Pkwy | 301-921-0434 [f] natale@acec.com | Gaithersburg MD 20877 | http://www.acec.com ------- NetPlus (r) "FCAPS" Telemanagement Applications --------   Delivery-Date: Fri, 26 Apr 1996 08:09:02 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id IAA27181 for X-agentx-local; Fri, 26 Apr 1996 08:09:01 -0700 (PDT) Received: from uu10.psi.com (uu10.psi.com [38.8.4.2]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id IAA27148 for ; Fri, 26 Apr 1996 08:09:00 -0700 (PDT) Received: from acec.com by uu10.psi.com (5.65b/4.0.061193-PSI/PSINet) via SMTP; id AA00156 for ; Fri, 26 Apr 96 10:58:56 -0400 Date: Fri, 26 Apr 1996 10:58:07 -0400 From: natale@acec.com (Bob Natale) Received: by nips.acec.com (5.65/3.2.083191-American Computer and Electronics Corp. ) id AA11966; Fri, 26 Apr 1996 10:58:07 -0400 Message-Id: <9604261458.AA11966@nips.acec.com> To: agentx@fv.com Subject: Change in meeting time (Montreal) Cc: mbeaulie@cnri.reston.va.us Hi folks, Included below is a message I just received from Marcia wrt scheduling matters: > Date: Fri, 26 Apr 1996 10:23:08 -0500 > From: Marcia Beaulieu > > I have had a lot of requests from the NM Area and have had to > do some rearranging. I had to move the Wednesday session of > AGENTX that was scheduled at 1530 to Wednesday at 1300. > It is now opposite ifmib, ospf, cat and pppext. I hope this > change is acceptable with you, please let me know. Naturally, we will want to cooperate...the only caveat being how many people might see the conflict with ifmib as a show- stopper. If you do, please let me know asap. We need to help Marcia be able to lock the agenda down asap since many attendees need to plan their travel and participation schedules. Thanks. Cordially, BobN ------- WinSNMP DLL, SDK, and Applets for Win16 and Win32 ------ Bob Natale | ACE*COMM | 301-258-9850 [v] Dir, Net Mgmt Prod | 209 Perry Pkwy | 301-921-0434 [f] natale@acec.com | Gaithersburg MD 20877 | http://www.acec.com ------- NetPlus (r) "FCAPS" Telemanagement Applications --------   Delivery-Date: Sun, 28 Apr 1996 07:38:51 -0700 Return-Path: Received: (from daemon@localhost) by zloty.fv.com (8.7.4/8.7.3) id HAA02302 for X-agentx-local; Sun, 28 Apr 1996 07:38:50 -0700 (PDT) Received: from aristo.tau.ac.il (aristo.tau.ac.il [132.66.32.10]) by zloty.fv.com (8.7.4/8.7.3) with SMTP id HAA02274 for ; Sun, 28 Apr 1996 07:38:38 -0700 (PDT) Received: from gandalf (world.lannet.com) by aristo.tau.ac.il with SMTP id AA25751 (5.67b/IDA-1.5 for ); Sun, 28 Apr 1996 17:38:07 +0300 Received: from moon.lannet.com by gandalf (4.1/SMI-4.1) id AA11687; Sun, 28 Apr 96 17:34:34 IDT Received: from smtplink.lannet.com by moon.lannet.com (4.1/SMI-4.1) id AA27225; Sun, 28 Apr 96 17:35:42 IDT Received: from Connect2 Message Router by smtplink.lannet.com via Connect2-SMTP 4.00; Sun, 28 Apr 96 17:50:25 -0500 Message-Id: <50E7833101660C40@smtplink.lannet.com> In-Reply-To: <5C59833101660C40> Date: Sun, 28 Apr 96 17:39:07 +0200 From: "Dan Romascano ESD-Tel" Sender: "Dan Romascano ESD-Tel" Organization: Lannet Ltd. To: agentx@fv.com, natale@acec.com (Bob Natale) Subject: Re: AgentX sessions at Montreal IETF X-Mailer: Connect2-SMTP 4.00 MHS to SMTP Gateway Bob, >> This is to confirm two sessions for AGENTX as follows: >> >> Tuesday, June 25 at 0900 (opposite atommib, pkix, rps, ipngwg) >> Wednesday, June 26 at 1530 (opposite dhc, ipsec) Would it be possible to avoid the conflict between atommib and agentx scheduling on June 25? I am sure that I am not the only one thinking about a future agentx based entity with ATM interfaces! Dan Romascanu, Systems Architecture Team Manager, Madge Networks (Israel) Ltd., Voice: 972-3-645-8414, e-mail: dan@madge.com ---------------------------------------------------------