Re: Integral management agents in a chassis. (Dan Romascanu) Thu, 31 December 1992 13:27 UTC

Return-Path: <owner-chassismib@CS.UTK.EDU>
Received: from localhost by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA01367; Thu, 31 Dec 92 08:27:30 -0500
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 31 Dec 1992 13:27:29 GMT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from [] by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA01359; Thu, 31 Dec 92 08:27:14 -0500
Received: from ([]) by (4.1/3.1.090690-Lannet Data Communications) id AA10957; Thu, 31 Dec 92 07:50:41 IST
Received: by (4.1/SMI-4.1) id AA07924; Thu, 31 Dec 92 07:50:39 IST
Date: Thu, 31 Dec 92 07:50:39 IST
From: (Dan Romascanu)
Message-Id: <>
Subject: Re: Integral management agents in a chassis.


How would a chassis with a built-in management agent be represented in
the chasSlotTable?  It has no slot number.

Slot number '0' can't be used since a table can't be indexed by zero.
Making is slot number '1' is misleading to users since the actual slot
numbers printed on the chassis are 1-8.

Slot number 'chasNumSlots + 1' could be used.  For example, in an 8 slot
hub the management agent would be said to occupy slot 9.  This isn't very
pretty either.

Any suggestions?

One possible solution would be to leave chasEnvironIndex the only index in
the table and to define chasSensorSlot as an INTEGER which describes the slot
in which the sensor is placed. Value '0' would then be legal to use for a
built-in management agent, as in David's proposal.
Dan Romascanu, LANNET Data Communications Ltd., 972-3-6458414