Latest draft questions

Joseph Zur <zur@fibhaifa.com> Wed, 21 April 1993 16:29 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09066; 21 Apr 93 12:29 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa09062; 21 Apr 93 12:29 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA29785; Wed, 21 Apr 93 11:53:32 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Wed, 21 Apr 1993 11:53:31 EDT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from spud.Hyperion.COM by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA29767; Wed, 21 Apr 93 11:53:25 -0400
Received: from imp.UUCP by spud.Hyperion.COM (4.1/SMI-4.0) id AA10927; Wed, 21 Apr 93 08:52:38 PDT
Received: by imp.HellNet.org (/\==/\ Smail3.1.21.1 #21.8) id <m0nlgmZ-00001DC@imp.HellNet.org>; Wed, 21 Apr 93 18:32 IDT
Received: from vivaldi.FibHaifa.com (vivaldi.fibronics.co.il) by FibHaifa.com (4.1/SMI-4.1) id AA00846; Wed, 21 Apr 93 17:54:24 IDT
Date: Wed, 21 Apr 93 17:54:24 IDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Joseph Zur <zur@fibhaifa.com>
Message-Id: <9304211454.AA00846@FibHaifa.com>
To: chassismib@cs.utk.edu
Subject: Latest draft questions

Hi all,

A few questions and remarks on the latest chassis MIB draft
dated April 19,1993.

1) chasType - 
   a. The OID chadTypeUnknown is not defined anywhere
      within the MIB. 
   b. Why shouldn't we try to define as many
      chasType values as possible in the MIB, and only those 
      implementors who will not find a predefined value will
      come up with their own value which will be allocated within 
      the SMI enterprisess subtree(1.3.6.1.4.1)
   c. if the SNMP agent implementing this MIB sole purpose is the 
      management of a chassis then this value should be the same
      as it's sysObjectId value, on the other hand if an entity 
      (i.e bridge card) is also the chassis manager and implements the
      chassis MIB then it may (or should) have a different chasType.
      I think some words explaining this should appear in the description
      section.
2) chasPhyLocationType - See 1.b
3) (Typo) chasPhyLocationDescr - apears in chasPhyLocationEntry sequnce as
			  chasPhyLocationName.
4) (Typo) Numbering of objects in chasPhyLocationType is wrong (number 2 apears
   twice)
5) chasModuleType - 
   a. The OID chasLocationUnknown is not defined anywhere
      within the MIB. 
   b. See 1.b
6) Is the chasModuleLocation is an index into the chasPhysLocation table,
   If yes, I think that every object which acts as an index into another
   table should have an explicitly description saying so in its description 
   section.
7) chasEntityObjectID,chasEntityDescr - why have those here? the manager 
   can get them from the entity itself. I think that the chassis manager
   should hold all the information about the chassis configuration and not any
   redundant information about entities within that chassis.
8) The config tables - I understand that those two tables are basicly
   the same table sorted by different keys. If so, why not have the tables
   look alike. meaning that if one table has an object chasPhyModuleID then the 
   other should have chasLogModuleID or both should have chasXXXConfigModule.
   The description part should also be identical for the instance of the 
   physical module within both tables. and also the description should say
   explicitly which table and index this object defines.

--- Joseph Zur

Fibronics Inc. Haifa, Israel

Voice : INTL-972-4-313679
Fax   : INTL-972-4-313342
Email : zur@FibHaifa.com