Chassis MIB comments

Chris Chiotasso <> Thu, 10 June 1993 20:55 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa11316; 10 Jun 93 16:55 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa11312; 10 Jun 93 16:55 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA04398; Thu, 10 Jun 93 16:33:01 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 10 Jun 1993 16:33:00 EDT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA04390; Thu, 10 Jun 93 16:32:56 -0400
Received: from ( by (4.1/SMI-4.1[UB-1.8]) id AA08897; Thu, 10 Jun 93 13:32:55 PDT
Received: from by (4.1/SMI-4.1) id AA11249; Thu, 10 Jun 93 16:32:54 EDT
Received: by (4.1/SMI-4.1) id AA14364; Thu, 10 Jun 93 16:32:53 EDT
Date: Thu, 10 Jun 93 16:32:53 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Chris Chiotasso <>
Message-Id: <>
Subject: Chassis MIB comments

I have recently reviewed the chassis mib and have a couple of

1.  There seems to be 2 entity/module/resource mapping tables:
    chasPhyResourceTable and chasLogResourceTable.

    Should the chasPhyResourceTable provide mapping information or
    just provide a list of all resources in the chassis?  I suggest
    that the mapping should be done by the chasLogResourceTable and
    that chasPhyResourceEntry be a flat list of resources as follows:

              chasPhyResourceEntry  OBJECT-TYPE
              SYNTAX  ChasPhyResourceEntry
              ACCESS  read-only
              STATUS  mandatory
                      "Defines a particular resource."
              INDEX { chasPhyResIndex }
              ::= { chasResourceTable 1 }

          ChasPhyResourceEntry ::= SEQUENCE {
                  OBJECT IDENTIFIER

2.  If the chasLogResourceTable consisted of 4 indices:
    chasLogResourceEntityIndex, chasLogResourceModuleTypeIndex,
    chasLogResourceModuleLocation and chasLogResourceResourceIndex,
    the table would provide a many-to-many mapping for
    resource/module/entity mapping.

3.  If the access profile information was removed from the
    chasLogResourceTable into a view table, it would allow more than 1
    view to be defined for each mapping.