Adding a 'chasEnvironSlotIndex' to the chasEnvironTable.

gallagher@quiver.enet.dec.com Wed, 30 December 1992 15:34 UTC

Return-Path: <owner-chassismib@CS.UTK.EDU>
Received: from localhost by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA11542; Wed, 30 Dec 92 10:34:07 -0500
X-Resent-To: chassismib@CS.UTK.EDU ; Wed, 30 Dec 1992 15:34:06 GMT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from inet-gw-2.pa.dec.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA11534; Wed, 30 Dec 92 10:34:04 -0500
Received: by inet-gw-2.pa.dec.com; id AA20232; Wed, 30 Dec 92 07:34:00 -0800
Received: by us1rmc.bb.dec.com; id AA02489; Wed, 30 Dec 92 10:28:29 -0500
From: gallagher@quiver.enet.dec.com
Message-Id: <9212301528.AA02489@us1rmc.bb.dec.com>
Received: from quiver.enet; by us1rmc.enet; Wed, 30 Dec 92 10:31:34 EST
Date: Wed, 30 Dec 1992 10:31:34 -0500
To: chassismib@cs.utk.edu
Cc: gallagher@quiver.enet.dec.com
Apparently-To: chassismib@cs.utk.edu
Subject: Adding a 'chasEnvironSlotIndex' to the chasEnvironTable.


Hi,

The chassis environment group contains the following objects:

               ChasEnvironEntry ::=
                   SEQUENCE {
                       chasEnvironIndex
                           INTEGER,
                       chasEnvironSensor
                           AutonomousType,
                       chasEnvironStatus
                           INTEGER,
                       chasEnvironWarnings
                           Counter,
                       chasEnvironFailures
                           Counter
                   }

These objects are fine for 'chassis wide' sensors, like a sensor which 
represents the temperature of the chassis.  But what of cases where there 
are sensors within each module occupying a slot?  For example, what if 
there were a temperature sensor on each module?  What each module had 
built-in fans which were monitored using a 'sensorFans'?

A new object could be added to this table to solve this problem.
'chasEnvironSlotIndex' could be added to represent the slot in which the 
sensor resides.  The ChasEnvironTable would then be indexed using both 
chasEnvironIndex and chasEnvironSlotIndex.  chasEnvironSlotIndex could be 
zero for 'chassis wide' sensors.

Thoughts?
						-Shawn