nominal environmental values in the chassis mib

fardy@minotaur.ctron.com Thu, 03 December 1992 20:48 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA27899; Thu, 3 Dec 92 15:48:42 -0500
Received: from nic.near.net by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA27848; Thu, 3 Dec 92 15:48:26 -0500
Received: from ctron.com by nic.near.net id aa21608; 3 Dec 92 15:48 EST
Received: from minotaur.ctron ([134.141.40.109]) by ctron.com (4.1/SMI-4.1) id AA01487; Thu, 3 Dec 92 15:48:49 EST
Received: by minotaur.ctron (4.1/SMI-4.1) id AA00384; Thu, 3 Dec 92 15:47:50 EST
Message-Id: <9212032047.AA00384@minotaur.ctron>
To: chassismib@cs.utk.edu
Cc: arneson@minotaur.ctron.com, craig@minotaur.ctron.com, grimard@minotaur.ctron.com, zielinsk@minotaur.ctron.com, jra@minotaur.ctron.com
Subject: nominal environmental values in the chassis mib
Date: Thu, 03 Dec 92 15:47:47 -0500
From: fardy@minotaur.ctron.com



 The latest rev of the chassis mib (nov 30) lists four well-known sensor types,
 Other, temperature, Fans and Humidity.

 These have associated status values (chasEnvironStatus).
 This status can be unknown, bad, warning or good.
  
  I would find it useful to have both nominal and actual values associated with 
  these sensors (especially temperature and humidity).  

  I assume that the reason they are sensors instead of integers is to avoid
requiring that users instrument these things in every chassis.  Could we propose a
means of allowing nominal and actual values  (an environmental entry table?) to
optionally be available in the chassis mib?