Next revision
"David L. Arneson (arneson@ctron.com)" <arneson@yeti.ctron.com> Mon, 24 August 1992 17:07 UTC
Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA05453; Mon, 24 Aug 92 13:07:26 -0400
Received: from nic.near.net by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA05449; Mon, 24 Aug 92 13:07:24 -0400
Received: from ctron.com by nic.near.net id aa27359; 24 Aug 92 13:07 EDT
Received: from yeti.ctron ([134.141.40.159]) by ctron.com (4.1/SMI-4.1) id AA09574; Mon, 24 Aug 92 13:14:17 EDT
Received: by yeti.ctron (4.1/SMI-4.1) id AA15335; Mon, 24 Aug 92 13:06:56 EDT
Message-Id: <9208241706.AA15335@yeti.ctron>
To: chassismib@cs.utk.edu
Subject: Next revision
Reply-To: arneson@ctron.com
Date: Mon, 24 Aug 1992 13:06:53 -0400
From: "David L. Arneson (arneson@ctron.com)" <arneson@yeti.ctron.com>
I have started to condense the various mail message concerning the chassis MIB.
I guess rather than go blindly off and make thse changes that seem
rational to me I wll present it to everybody and see what input I get
back.
The current draft has the 4 objects chasType, chasNumSlots, chasPhysicalChanges,
chasChassisSN. Since Keith wants to push these objects down a level what
I'm thinking is why not move them else where. For example
chasNumSlots -> {chasSlot 1}
chasType -> {chasConfig 1}
chasPhysicalChanges -> {chasConfig 2}
chasChassisSN -> {chasConfig 3}
Of course the tables that are currently there would also need to be changed.
Description found in section 5 would be changed to reflect the added iformation
available.
In addition Keith mentioned forming a MIB group. If we make this change then
it appears we could go two different directions. The first would be to
from one group which is the entire MIB. The second would be multiple groups
for each of the branches defined under chassis.
What are the comments out there from everybody else. It seems to make sense to
me however there is a specific reason to leave it where it is.
/David Arneson [arneson@ctron.com] [ (603)332-9400 ]
- Next revision David L. Arneson (arneson@ctron.com)