Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02480; 4 Jul 94 10:59 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02476; 4 Jul 94 10:59 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa05915; 4 Jul 94 10:59 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id KAA03924; Mon, 4 Jul 1994 10:50:12 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Mon, 4 Jul 1994 10:50:11 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from sun4nl.NL.net by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id KAA03907; Mon, 4 Jul 1994 10:50:07 -0400 Received: from vicnl by sun4nl.NL.net via EUnet id AA09809 (5.65b/CWI-3.3); Mon, 4 Jul 1994 16:50:03 +0200 Received: from vic1.victron.nl by vicnl.victron.nl id aa21808; 4 Jul 94 16:11 CEST Received: from VICTRON_ONE/TEMPQ by vic1.victron.nl (Mercury 1.11); Mon, 4 Jul 94 16:21:34 CET Received: from TEMPQ by VICTRON_ONE (Mercury 1.11); Mon, 4 Jul 94 16:21:25 CET Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jack Stiekema Organization: Victron bv, UPS and software To: ups-mib@cs.utk.edu Date: Mon, 4 Jul 1994 16:21:23 CET Subject: UPS Extensions. Reply-To: jack@victron.nl Cc: RVA@vic1.victron.nl, JVE@vic1.victron.nl, REMCO@vic1.victron.nl Priority: normal X-Mailer: Pegasus Mail v3.1 (R1a) Message-Id: <301F255274F@vic1.victron.nl> Hello SNMP fans, To whom it may concern: We started a discussion group for the next ups-mib. You can subscribe yourself if you send an email to ups-extensions@vic1.victron.nl The purpose of this group is to prepare a new draft for the ups-mib which includes the 'extra' features as environmental, advanced and receptables. After making a decent proposal we can present this to the ups-mib group. This is also the way Jeff Case preferred in the meeting i had with Jeff at Interop Berlin. The existing ups-mib mail group is to be used as platform for discussions how to implement rfc1628. Members on this moment are Best Deltec Exide Liebert Oneac Merlin Gerin NetX Victron (sri if i forgot someone, but some email addresses are very cryptic) Please join the party, and help us to make UPS an accepted part of networks. Kind regards, Jack Stiekema Product Manager Connectivity +----------------------------------------------------+ | Victron bv POB 31 9700 AA Groningen Holland | | Phone: +31 50 446222 Fax: +31 50 424107 | | Email: jack@victron.nl Internet: 193.78.242.81 | | Home: +31 5980 80498 pe0mot@pe0mot.ampr.org | +----------------------------------------------------+   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03641; 4 Jul 94 14:37 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03637; 4 Jul 94 14:37 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa08629; 4 Jul 94 14:37 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA19659; Mon, 4 Jul 1994 14:29:28 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Mon, 4 Jul 1994 14:29:27 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from arl-img-1.compuserve.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id OAA19652; Mon, 4 Jul 1994 14:29:25 -0400 Received: from localhost by arl-img-1.compuserve.com (8.6.4/5.940406sam) id OAA15326; Mon, 4 Jul 1994 14:28:53 -0400 Date: 04 Jul 94 14:26:14 EDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: "A.Stolinski-merlin gerin" <74222.1151@compuserve.com> To: UPS WRKGRP Cc: Chris Wellens-IntrwkgLab Subject: Merlin Gerin Implementation RFC 1628 Message-ID: <940704182614_74222.1151_BHT35-2@CompuServe.COM> Hi guys !! Just a note on RFC 1628 implementation progress. We have implemented RFC 1628 ( SNMPv1 version) in our UM-Link adapter. We also have our enterprise MG-MIB & MIB II implemented on the same agent. We looked at combining our MIB and RFC 1628, but decided, at least for now, to keep both MIB's in the agent. I'd like to hear any pro's and con's from anyone on how they are handling their enterprise MIB & the std. The agent can be accessed by either MIB, and we have a provision in our manager table for enabling Trap acknowledgement (included in our MG-MIB) or disabling it for RFC 1628 (no ack included) by manager. We took our agent with all three MIB's in it to the SNMP Test Summit at San Jose last week, and both the test suite & the real world interoperability with the other participants uncovered numerous, minor to medium, bugs in our implementation. I'd highly recommend anyone's participation in the next tests set for January '95. We found the experience very beneficial. By the end of the week we had corrected all bugs and gained the verification of our agent's compliance to IETF SNMP interoperability standards. A week very well spent. Well, thats about it. Any one else out there done any implementation yet?? Love to share experiences with you. Regards, Adam Stolinski Merlin Gerin   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01572; 7 Jul 94 8:34 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01568; 7 Jul 94 8:34 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa04530; 7 Jul 94 8:34 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id IAA26039; Thu, 7 Jul 1994 08:13:33 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Thu, 7 Jul 1994 08:13:31 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from sun4nl.NL.net by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id IAA26032; Thu, 7 Jul 1994 08:13:27 -0400 Received: from vicnl by sun4nl.NL.net via EUnet id AA12474 (5.65b/CWI-3.3); Thu, 7 Jul 1994 14:13:16 +0200 Received: from vic1.victron.nl by vicnl.victron.nl id aa02817; 7 Jul 94 13:50 CEST Received: from VICTRON_ONE/TEMPQ by vic1.victron.nl (Mercury 1.11); Thu, 7 Jul 94 13:50:01 CET Received: from TEMPQ by VICTRON_ONE (Mercury 1.11); Thu, 7 Jul 94 13:49:38 CET Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jack Stiekema Organization: Victron bv, UPS and software To: ups-mib@cs.utk.edu Date: Thu, 7 Jul 1994 13:49:37 CET Subject: battery current Reply-To: jack@victron.nl Cc: ERWIN@vic1.victron.nl Priority: normal X-Mailer: Pegasus Mail v3.1 (R1a) Message-Id: <3476CAC6F8C@vic1.victron.nl> Sri, but i forgot our discussion and it's not well described in the MIB. upsBatteryCurrent What is positive, and what is negative? As far as i can remember: charging is positive and discharging is negative. Agree? Kind regards, Jack Stiekema Product Manager Connectivity +----------------------------------------------------+ | Victron bv POB 31 9700 AA Groningen Holland | | Phone: +31 50 446222 Fax: +31 50 424107 | | Email: jack@victron.nl Internet: 193.78.242.81 | | Home: +31 5980 80498 pe0mot@pe0mot.ampr.org | +----------------------------------------------------+   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02392; 8 Jul 94 9:16 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02388; 8 Jul 94 9:16 EDT Received: from [128.169.94.1] by CNRI.Reston.VA.US id aa05839; 8 Jul 94 9:16 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA13047; Fri, 8 Jul 1994 09:05:17 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Fri, 8 Jul 1994 09:05:15 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from dante.exide.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA13028; Fri, 8 Jul 1994 09:05:13 -0400 Received: by dante.exide.com (5.0/1.34) id AA05759; Fri, 8 Jul 1994 09:02:11 +0500 Date: Fri, 8 Jul 1994 09:02:11 +0500 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Brennan Message-Id: <9407081302.AA05759@dante.exide.com> To: ups-mib@cs.utk.edu Subject: re: Battery current sense Exide's metering always does discharge current as positive, and charging current as negative. There was a discussion, but I too forget the conclusion. Seems to me it would have been more memorable if it had been contrary to our practice. Can't find any reference in my mail box, but then again I accidentally blew away part of my archive. Tom Brennan, Exide   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08445; 11 Jul 94 15:06 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08441; 11 Jul 94 15:06 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa19123; 11 Jul 94 15:06 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA18374; Mon, 11 Jul 1994 14:52:32 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Mon, 11 Jul 1994 14:52:29 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from nic.cerf.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id OAA18363; Mon, 11 Jul 1994 14:52:22 -0400 Received: (from rpitt@localhost) by nic.cerf.net (8.6.8/8.6.6) id LAA12882; Mon, 11 Jul 1994 11:52:17 -0700 Date: Mon, 11 Jul 1994 11:52:16 -0700 (PDT) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Ronald Pitt Subject: Battery current. To: UPS MIB Working Group Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello again, I can find no record of our discussion on the sign of the battery current measurement. It does seem more intuitive to show discharging as negative to me. However, I could live with it either way. Ron Pitt Deltec   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08455; 11 Jul 94 15:06 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08451; 11 Jul 94 15:06 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa19125; 11 Jul 94 15:06 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA18410; Mon, 11 Jul 1994 14:53:44 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Mon, 11 Jul 1994 14:53:43 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from nic.cerf.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id OAA18403; Mon, 11 Jul 1994 14:53:40 -0400 Received: (from rpitt@localhost) by nic.cerf.net (8.6.8/8.6.6) id LAA13115; Mon, 11 Jul 1994 11:53:19 -0700 Date: Mon, 11 Jul 1994 11:53:19 -0700 (PDT) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Ronald Pitt Subject: New E-Mail Address. To: UPS MIB Working Group Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please change my e-mail address in the mailing list to the following: rpitt@cerf.net Ron Pitt Deltec   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00630; 12 Jul 94 5:24 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00626; 12 Jul 94 5:24 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa01899; 12 Jul 94 5:24 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id FAA24561; Tue, 12 Jul 1994 05:11:18 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Tue, 12 Jul 1994 05:11:17 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from sun4nl.NL.net by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id FAA24537; Tue, 12 Jul 1994 05:11:10 -0400 Received: from vicnl by sun4nl.NL.net via EUnet id AA16656 (5.65b/CWI-3.3); Tue, 12 Jul 1994 11:11:05 +0200 Received: from vic1.victron.nl by vicnl.victron.nl id aa01714; 12 Jul 94 9:43 CEST Received: from VICTRON_ONE/TEMPQ by vic1.victron.nl (Mercury 1.11); Tue, 12 Jul 94 9:43:03 CET Received: from TEMPQ by VICTRON_ONE (Mercury 1.11); Tue, 12 Jul 94 9:42:35 CET Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jack Stiekema Organization: Victron bv, UPS and software To: ups-mib@cs.utk.edu Date: Tue, 12 Jul 1994 09:42:25 CET Subject: Re: Battery current. Reply-To: jack@victron.nl Priority: normal X-Mailer: Pegasus Mail v3.1 (R1a) Message-Id: <3BB51EB4696@vic1.victron.nl> >>Date sent: Mon, 11 Jul 1994 11:52:16 -0700 (PDT) >>From: Ronald Pitt >>Subject: Battery current. >>To: UPS MIB Working Group >>measurement. It does seem more intuitive to show discharging as negative >>to me. However, I could live with it either way. Agree, this the way i see it for 8 years now. In the old days we had separate chargers and developers designing these things, and charging a battery was called positive and discharging negative. In the UPS world this had to be turned around because for a customer taking energy out of a battery is a negative thing and charging positive. Kind regards, Jack Stiekema Product Manager Connectivity +----------------------------------------------------+ | Victron bv POB 31 9700 AA Groningen Holland | | Phone: +31 50 446222 Fax: +31 50 424107 | | Email: jack@victron.nl Internet: 193.78.242.81 | | Home: +31 5980 80498 pe0mot@pe0mot.ampr.org | +----------------------------------------------------+   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05013; 12 Jul 94 11:53 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05007; 12 Jul 94 11:53 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa17698; 12 Jul 94 11:53 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA01561; Tue, 12 Jul 1994 11:41:32 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Tue, 12 Jul 1994 11:41:30 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from relay3.UU.NET by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id LAA01545; Tue, 12 Jul 1994 11:41:24 -0400 Received: from uucp4.UU.NET by relay3.UU.NET with SMTP (relay) id QQwygc06597; Tue, 12 Jul 1994 11:41:18 -0400 Received: from stg.UUCP by uucp4.UU.NET with UUCP/RMAIL ; Tue, 12 Jul 1994 11:41:17 -0400 Received: by mcbain (4.1/SMI-4.1) id AA18727; Tue, 12 Jul 94 10:25:46 CDT Date: Tue, 12 Jul 94 10:25:46 CDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Chris Herzog Message-Id: <9407121525.AA18727@mcbain> To: uunet!CS.UTK.EDU!ups-mib@uunet.uu.net, uunet!victron.nl!jack@uunet.uu.net Subject: Re: Battery current. > In the old days we had separate chargers and developers designing > these things, and charging a battery was called positive and > discharging negative. > > In the UPS world this had to be turned around because for a > customer taking energy out of a battery is a negative thing and > charging positive. Don't these two statements agree or do I need more coffee?? Chris Herzog zog@stg.com   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24205; 13 Jul 94 3:17 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa24201; 13 Jul 94 3:17 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa10794; 13 Jul 94 3:17 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA12515; Wed, 13 Jul 1994 03:03:59 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Wed, 13 Jul 1994 03:03:56 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from sun4nl.NL.net by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA12500; Wed, 13 Jul 1994 03:03:51 -0400 Received: from vicnl by sun4nl.NL.net via EUnet id AA25040 (5.65b/CWI-3.3); Wed, 13 Jul 1994 09:03:47 +0200 Received: from vic1.victron.nl by vicnl.victron.nl id aa02741; 13 Jul 94 8:51 CEST Received: from VICTRON_ONE/TEMPQ by vic1.victron.nl (Mercury 1.11); Wed, 13 Jul 94 8:52:27 CET Received: from TEMPQ by VICTRON_ONE (Mercury 1.11); Wed, 13 Jul 94 8:52:17 CET Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jack Stiekema Organization: Victron bv, UPS and software To: ups-mib@cs.utk.edu Date: Wed, 13 Jul 1994 08:52:14 CET Subject: Re: Battery current. Reply-To: jack@victron.nl Priority: normal X-Mailer: Pegasus Mail v3.1 (R1a) Message-Id: <3D27BFC0283@vic1.victron.nl> >>Date sent: Tue, 12 Jul 94 10:25:46 CDT >>From: Chris Herzog >>To: ups-mib@cs.utk.edu, jack@victron.nl >>Subject: Re: Battery current. >>> In the old days we had separate chargers and developers designing >>> these things, and charging a battery was called positive and ^^^^^^^^ should be negative >>> discharging negative. ^^^^^^^^ should be positive >>> >>> In the UPS world this had to be turned around because for a >>> customer taking energy out of a battery is a negative thing and >>> charging positive. >> >>Don't these two statements agree or do I need more coffee?? Sri, i forgot to take the coffee before writing that email. Kind regards, Jack Stiekema Product Manager Connectivity +----------------------------------------------------+ | Victron bv POB 31 9700 AA Groningen Holland | | Phone: +31 50 446222 Fax: +31 50 424107 | | Email: jack@victron.nl Internet: 193.78.242.81 | | Home: +31 5980 80498 pe0mot@pe0mot.ampr.org | +----------------------------------------------------+   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00375; 14 Jul 94 3:53 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00371; 14 Jul 94 3:53 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa00901; 14 Jul 94 3:53 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA25951; Thu, 14 Jul 1994 03:41:20 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Thu, 14 Jul 1994 03:41:19 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from sun4nl.NL.net by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA25944; Thu, 14 Jul 1994 03:41:15 -0400 Received: from vicnl by sun4nl.NL.net via EUnet id AA18406 (5.65b/CWI-3.3); Thu, 14 Jul 1994 09:41:12 +0200 Received: from vic1.victron.nl by vicnl.victron.nl id aa06099; 14 Jul 94 9:28 CEST Received: from VICTRON_ONE/TEMPQ by vic1.victron.nl (Mercury 1.11); Thu, 14 Jul 94 9:29:34 CET Received: from TEMPQ by VICTRON_ONE (Mercury 1.11); Thu, 14 Jul 94 9:29:22 CET Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Jack Stiekema Organization: Victron bv, UPS and software To: ups-mib@cs.utk.edu Date: Thu, 14 Jul 1994 09:29:22 CET Subject: Re: UPS Tests Reply-To: jack@victron.nl Priority: normal X-Mailer: Pegasus Mail v3.1 (R1a) Message-Id: <3EB1AF22410@vic1.victron.nl> >>From: Sridhar Kodela >>To: Ups MIB extensions >>Subject: UPS Tests >>Date sent: Wed, 13 Jul 1994 13:16:29 -0700 (PDT) >> My question is to be compliant with Standard MIB (full) do I need >>to run the test every time i got the request or can i send the >>information i already has. Remember that the auto test duration is >>between 12 to 24 hrs, and i got no way of telling the UPS to test >>immediately. Am I out of luck ? Test result is not specified in time so it can be the result of a test 24 hours ago. The MIB does not specify anything about timing, only test in progress, initiate tests and results of tests. Anyway, it will be difficult to do the test and give back a snmp answer before the timeout of the management station. For example a deep discharge test should only be run once a month to give a customer maximum up-time and maximum battery life. You can poll the result every 10 seconds, but don't start the test. Kind regards, Jack Stiekema Product Manager Connectivity +----------------------------------------------------+ | Victron bv POB 31 9700 AA Groningen Holland | | Phone: +31 50 446222 Fax: +31 50 424107 | | Email: jack@victron.nl Internet: 193.78.242.81 | | Home: +31 5980 80498 pe0mot@pe0mot.ampr.org | +----------------------------------------------------+   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02723; 14 Jul 94 9:31 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02719; 14 Jul 94 9:31 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa06497; 14 Jul 94 9:31 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA28834; Thu, 14 Jul 1994 09:22:42 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Thu, 14 Jul 1994 09:22:39 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from dante.exide.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA28816; Thu, 14 Jul 1994 09:22:37 -0400 Received: by dante.exide.com (5.0/1.34) id AA12391; Thu, 14 Jul 1994 09:18:08 +0500 Date: Thu, 14 Jul 1994 09:18:08 +0500 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Brennan Message-Id: <9407141318.AA12391@dante.exide.com> To: ups-mib@cs.utk.edu Cc: kodela@netcom.com Subject: Re: UPS Tests Regarding sridhar's question about whether he complies if he cannot initiate a test by SNMP command, but can report the results of an automatic test: a) As I read the standard on this point, you would not be in full compliance if you cannot set upsTestId. b) However, you can still do a useful thing by filling in the fields of the upsTest group that you can fill in for read-only access. c) An even more useful thing is to send the trap, upsTrapTestCompleted. One last point: this sort of question should be addressed to this mailing list (ups-mib@cs.utk.edu), since it does not deal with extensions. Tom Brennan, Exide   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02190; 19 Jul 94 7:48 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02186; 19 Jul 94 7:48 EDT Received: from [128.169.94.1] by CNRI.Reston.VA.US id aa04102; 19 Jul 94 7:48 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id HAA25317; Tue, 19 Jul 1994 07:35:30 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Tue, 19 Jul 1994 07:35:29 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from desire.wright.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id HAA25301; Tue, 19 Jul 1994 07:35:28 -0400 Received: from dayton.wright.edu by desire.wright.edu (PMDF V4.2-10 #2485) id <01HEVSAHQQ8G8YDVYO@desire.wright.edu>; Tue, 19 Jul 1994 07:35:15 EDT Received: by dayton.wright.edu; id AA06892; Tue, 19 Jul 1994 07:35:12 -0400 Date: Tue, 19 Jul 1994 07:35:12 -0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Ray Brown Subject: SUBSCRIBE To: ups-mib@cs.utk.edu Message-id: <9407191135.AA06892@dayton.wright.edu> Content-transfer-encoding: 7BIT SUBSCRIBE RAY BROWN   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01257; 20 Jul 94 1:42 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01253; 20 Jul 94 1:42 EDT Received: from [128.169.94.1] by CNRI.Reston.VA.US id aa00131; 20 Jul 94 1:42 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id BAA27184; Wed, 20 Jul 1994 01:11:12 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Wed, 20 Jul 1994 01:11:11 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from peladon.rmit.EDU.AU by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id BAA27174; Wed, 20 Jul 1994 01:11:02 -0400 Received: from minyos.xx.rmit.EDU.AU by peladon.rmit.EDU.AU with SMTP id AA09358 (5.65c/IDA-1.4.4 for ); Wed, 20 Jul 1994 15:10:55 +1000 Received: by minyos.xx.rmit.EDU.AU Date: Wed, 20 Jul 94 15:10:50 EST Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Maria Del Carmen Nicolazzo Message-Id: <9407200510.23164@minyos.xx.rmit.EDU.AU> To: ups-mib@cs.utk.edu Subject: UPS on ethernet I work for an Australian company (THYCON Industries) who manufacture UPS (larger than 5kVA). We have been asked to provide an ethernet interface on our units by several customers, but none of us here have any experience with networks. Our units are not PC based but we use the Intel 80C196KC 16 bit micro controller and i have found source code for TCP/IP and SNMP which could possibly be converted for our use. I am after information about what a UPS should say and I understand the UPS MIB is the answer. Any help on this matter would be much appreciated. Regards Neil McCoy (via a colleagues student access)   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07551; 20 Jul 94 11:46 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07541; 20 Jul 94 11:46 EDT Received: from [128.169.94.1] by CNRI.Reston.VA.US id aa10084; 20 Jul 94 11:46 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA27249; Wed, 20 Jul 1994 11:38:45 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Wed, 20 Jul 1994 11:38:42 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from dante.exide.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA27242; Wed, 20 Jul 1994 11:38:40 -0400 Received: by dante.exide.com (5.0/1.34) id AA02247; Wed, 20 Jul 1994 09:35:14 +0500 Date: Wed, 20 Jul 1994 09:35:14 +0500 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Tom Brennan Message-Id: <9407201335.AA02247@dante.exide.com> To: s925696@minyos.xx.rmit.edu.au Cc: ups-mib@cs.utk.edu Subject: Re: UPS on ethernet To: Neil McCoy You will need to get yourself an SNMP agent; suggest commercial sources like SNMP Research or Epilogue, both here in US. Get a copy of RFC1628, which describes the UPS MIB. Request the archives of this working group, if you have a lot of time to kill reading the history of how this MIB was put together. Get Marshall Rose's "Simple Book", 2nd edition for more on SNMP in general. Good luck !! Tom Brennan, Exide Electronics.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02605; 26 Jul 94 10:29 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02601; 26 Jul 94 10:29 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa06613; 26 Jul 94 10:29 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id KAA04525; Tue, 26 Jul 1994 10:18:06 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Tue, 26 Jul 1994 10:18:05 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from dante.exide.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id KAA04518; Tue, 26 Jul 1994 10:18:04 -0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: BRENNANT@email.exide.com MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Received: from email.exide.com by dante.exide.com (5.0/1.34) id AA10099; Tue, 26 Jul 1994 10:14:57 +0500 Received: from WPDOMRAL-Message_Server by email.exide.com with WordPerfect_Office; Tue, 26 Jul 1994 10:16:34 -0400 Message-Id: X-Mailer: WordPerfect Office 4.0 Date: Tue, 26 Jul 1994 10:07:00 -0400 To: ups-mib@cs.utk.edu Subject: An Argument and Scorecard for Battery Current One reason to define Battery Current as positive on Discharge comes from Thevenin circuits: +------+ --> I +-------| Zi |-------------+ | +------+ | ^\ ------- +-+-+ \ --- | | \ ------- | Z | V --- | l| / | +-+-+ / | | / +----------------------------+ Current from a voltage source (eg, Battery) and flowing into a load is defined as Positive, as shown here. At any rate, we, and our customers, would be well served by a resolution to this question one way or the other. We haven't heard from most of you, so I'll put out this scorecard: (*=Don't Care) Discharge = + J Stiekema N T Brennan Y R Pitt * B Young G Monk R Draper L Markle D Rademacher A Stolinski ------------------------------------------------------------- Tom Brennan, Exide Electronics (919) 872-3020 x1102 Fax (919) 878-2385 brennant@email.exide.com -------------------------------------------------------------   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05284; 26 Jul 94 16:10 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05280; 26 Jul 94 16:10 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa13454; 26 Jul 94 16:10 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id PAA25486; Tue, 26 Jul 1994 15:54:53 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Tue, 26 Jul 1994 15:54:51 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from relay3.UU.NET by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id PAA25473; Tue, 26 Jul 1994 15:54:47 -0400 Received: from uucp6.UU.NET by relay3.UU.NET with SMTP id QQxagg05409; Tue, 26 Jul 1994 14:33:14 -0400 Received: from stg.UUCP by uucp6.UU.NET with UUCP/RMAIL ; Tue, 26 Jul 1994 14:33:19 -0400 Received: by mcbain (4.1/SMI-4.1) id AA26644; Tue, 26 Jul 94 12:00:51 CDT Date: Tue, 26 Jul 94 12:00:51 CDT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Chris Herzog Message-Id: <9407261700.AA26644@mcbain> To: uunet!CS.UTK.EDU!ups-mib@uunet.uu.net, uunet!email.exide.com!BRENNANT@uunet.uu.net Subject: Re: An Argument and Scorecard for Battery Current > One reason to define Battery Current as positive on Discharge > comes from Thevenin circuits: While I can agree with the technical reasoning behind a + value for discharge, for the typical administrator, the concept of a + discharge is somewhat counter intuitive for non-EE types. As a developer of agents and applications, it makes more sense to me to show a - battery current when the unit is running on battery. I feel it makes more intuitive sense to consider a discharge as - since the battery is losing potential (and losing the ability to support the output load). This means a positive current indicates charging and adding to the capacity of the UPS. zog feel: Charging "good" + Discharging "bad" - I feel this is one of the areas were I think the "principle of least astonishment" would point towards a - discharge current. Chris Herzog zog@stg.com   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05693; 26 Jul 94 17:02 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05688; 26 Jul 94 17:02 EDT Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa14614; 26 Jul 94 17:00 EDT Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA29939; Tue, 26 Jul 1994 16:48:04 -0400 X-Resent-To: ups-mib@CS.UTK.EDU ; Tue, 26 Jul 1994 16:48:02 EDT Errors-to: owner-ups-mib@CS.UTK.EDU Received: from relay1.UU.NET by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id QAA29926; Tue, 26 Jul 1994 16:48:00 -0400 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: BRENNANT@email.exide.com MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Received: from dante.exide.com by relay1.UU.NET with SMTP id QQxagp27660; Tue, 26 Jul 1994 16:47:25 -0400 Received: from email.exide.com by dante.exide.com (5.0/1.34) id AA13783; Tue, 26 Jul 1994 16:44:20 +0500 Received: from WPDOMRAL-Message_Server by email.exide.com with WordPerfect_Office; Tue, 26 Jul 1994 16:45:56 -0400 Message-Id: X-Mailer: WordPerfect Office 4.0 Date: Tue, 26 Jul 1994 15:23:52 -0400 To: zog%stg@uunet.uu.net, ups-mib%CS.UTK.EDU%uunet@uunet.uu.net Subject: Re: An Argument and Scorecard for Battery Current -Reply Chris Herzog wrote: >>>>>>>>>>>>>>> I feel it makes more intuitive sense to consider a discharge as - since the battery is losing potential (and losing the ability to support the output load). This means a positive current indicates charging and adding to the capacity of the UPS. I feel this is one of the areas were I think the "principle of least astonishment" would point towards a - discharge current. <<<<<<<<<<<<<<< This is a very good point. It may fly against established industry practice in UPS monitoring, but Network Managers have no established practice for this, so point well taken. New scorecard: (*=Don't Care) Discharge = + J Stiekema N T Brennan Y R Pitt * C Herzog N B Young G Monk R Draper L Markle D Rademacher A Stolinski ------------------------------------------------------------- Tom Brennan, Exide Electronics (919) 872-3020 x1102 Fax (919) 878-2385 brennant@email.exide.com -------------------------------------------------------------