Nut upsdev - Apr 2010 - Request to add new nut variable to get device part number

Hi,

To display the device part number, we need to have a nut variable. 
As it is related to the device, I would propose to have "device.part"
as
the nut variable name.

Please suggest.

Please see svn diff for docs/new-names.txt and data/cmdvartab - 

Index: docs/new-names.txt
==================================================================---
docs/new-names.txt  (revision 2445)
+++ docs/new-names.txt  (working copy)
@@ -236,6 +236,12 @@
    | output.current.nominal        | Nominal output current (A)     |
5.0   |
 
+-----------------------------------------------------------------------
-+

+device: Device identification information
+
+
+-----------------------------------------------------------------------
-+
+   | device.part               | Part Number                |
05147365-5592 |
+
+-----------------------------------------------------------------------
-+
+
 Three-phase additions:
 ----------------------

Index: data/cmdvartab
==================================================================---
data/cmdvartab      (revision 2445)
+++ data/cmdvartab      (working copy)
@@ -138,6 +138,8 @@
 VARDESC driver.version "Driver version - NUT release"
 VARDESC driver.version.internal "Internal driver version"

+VARDESC device.part "Device Part Number"
+
 # FIXME: driver.parameter and driver.flag can have many possible
members
 #
 # VARDESC driver.parameter.[[:alpha:]]+ "Driver parameter:
<name>"



Thanks & Regards,
Chetan Agarwal

Citeren ChetanAgarwal op Eaton.com:
> To display the device part number, we need to have a nut variable.
> As it is related to the device, I would propose to have
"device.part" as
> the nut variable name.
>
> Please suggest.
Have a look at the following list of variables that we already support:

     (device|ups).model
     (device|ups).mfr
     (device|ups).serial
     (device|ups).type
     (device|ups).firmware
     (device|ups).firmware.aux
     (device|ups).id

1) In what way is the suggested new variable name different from the  
ones above?
2) Why do we need to be able to access this remotely?

NUT is not an ERP system.

Best regards, Arjen
-- 
Please keep list traffic on the list

> Have a look at the following list of variables that we already
support:
> 
>      (device|ups).model
>      (device|ups).mfr
>      (device|ups).serial
>      (device|ups).type
>      (device|ups).firmware
>      (device|ups).firmware.aux
>      (device|ups).id
> 
> 1) In what way is the suggested new variable name different from the
> ones above?

Device Part number is unique for all the devices and will help in
identify the device. This is provided by the manufacturer for the
particular device. 
(device|ups).id seems to be relevant, but I guess, it is the identifier
for the device which can be r/w; and will be different for two devices
with same part number. 

device.part can be a read-only value read from the device wherever
supported / applicable.  

I was looking into BCMXCP TODO List and found part number as a value
provided in the Config Block.

As per XCP Protocol document, 
---------------------------------
5.2 Identification and Configuration
The UPS must have a way of reporting its Identification and
Configuration information, including:
* Model name (must not have Manufacturer in the text)
* VA rating
* "manufacturer"
* Serial and model or CTO numbers
* Customer-set identification string
* nominal input and output volts, amps, VA, power, and frequency
* Identification of submodules: version, name or part #
---------------------------------

device.part can be useful for identifying the ups.
> 2) Why do we need to be able to access this remotely?
> 
> NUT is not an ERP system.
> 
Part number is present for almost all the devices and can help identify
the model and other details using the part number. 

Best Regards, 
Chetan

Fellows,

2010/4/21 <ChetanAgarwal at eaton.com>
>
>
> > Have a look at the following list of variables that we already
> support:
> >
> >      (device|ups).model
> >      (device|ups).mfr
> >      (device|ups).serial
> >      (device|ups).type
> >      (device|ups).firmware
> >      (device|ups).firmware.aux
> >      (device|ups).id
> >
> > 1) In what way is the suggested new variable name different from the
> > ones above?
> (...)
>
> device.part can be useful for identifying the ups.
>
> > 2) Why do we need to be able to access this remotely?
> >
> > NUT is not an ERP system.
> >
> Part number is present for almost all the devices and can help identify
> the model and other details using the part number.
>
I second Chetan:
the part number can somehow be considered as the serial number.
that is to say, an information that:
- can be needed for support situations,
- can help managing large systems, using NUT to feed a CMDB (1) system.

Considering that some big names (like Dell) are starting to join, this is
the kind of details that will help us in rallying such companies.

cheers,
Arnaud
-- 
[1] http://en.wikipedia.org/wiki/CMDB
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100421/3882e0a5/attachment.htm>