Re: draft MIB
Jim Barnes <barnes@xylogics.com> Tue, 01 June 1993 18:53 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11525; 1 Jun 93 14:53 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa11521; 1 Jun 93 14:53 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA13260; Tue, 1 Jun 93 14:22:58 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Tue, 1 Jun 1993 14:22:57 EDT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from atlas.xylogics.com by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA13252; Tue, 1 Jun 93 14:22:53 -0400
Received: from spock.xylogics.com by atlas.xylogics.com with SMTP id AA15450 (5.65c/UK-2.1-930202); Tue, 1 Jun 1993 14:22:45 -0400
Received: by spock.xylogics.com id AA10399 (4.1/UK-2.1-921215); Tue, 1 Jun 93 14:22:57 EDT
Message-Id: <10399.9306011822@spock.xylogics.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jim Barnes <barnes@xylogics.com>
Date: Tue, 01 Jun 1993 14:22:56 -0400
X-Mailer: Mail User's Shell (7.1.0 4/25/90)
To: chassismib@cs.utk.edu
Subject: Re: draft MIB
Here are a few comments on the draft posted last week. chasPowerSupply is defined twice: } chasPowerSupply OBJECT IDENTIFIER ::= { chassis 5 } } chasPowerSupply OBJECT IDENTIFIER ::= { chasChassisTypes 1 } ----------------------------------------------------- } } chasChassisEntities OBJECT IDENTIFIER ::= { chasEntityTypes 1 } } } chasPowerSupply OBJECT IDENTIFIER ::= { chasChassisTypes 1 } } chasChassis OBJECT IDENTIFIER ::= { chasChassisTypes 2 } } chasMonitors OBJECT IDENTIFIER ::= { chasChassisTypes 3 } ^^^^^^^^^^^^^^^^ Should that be chasChassisEntities? ----------------------------------------------------- } chasModuleType OBJECT-TYPE } SYNTAX OBJECT IDENTIFIER } ACCESS read-only } STATUS mandatory } DESCRIPTION } "An authoritative identification of the type of } physcial module in this physical location. A } value of chasLocationUnknown indicates that the ^^^^^^^^^^^^^^^^^^^ Should that be chasModuleUnknown?? } type of physical module is unknown." } :== { chasModuleEntry 3 } ----------------------------------------------------- The description of } chasModuleOperStatus refers to phyAdminStatus and phyOperStatus. Should those be chasModuleAdminStatus and chasModuleOperStatus, respectively? ----------------------------------------------------- I still have a problem with the descriptions for } chasEntityParty } DESCRIPTION } "The SNMP Party which provides access to the } detailed management information for this entity. and } chasEntityCommunity } DESCRIPTION } "The SNMP Community which executes at the address } chasEntityIpAddress, and provides access to the } detailed management information for this entity. I would like to see some guidance as to what "access to the detailed management information" means. Is read permission for the MIB-II system group sufficient to satisfy this requirement? Is it required that the agent for the entity allow read and write permissions to all implemented MIBs? Something in between? -------------------------------------------------- } chasLogResourceID } SYNTAX INTEGER } ACCESS read-only } STATUS mandatory } DESCRIPTION } "The value of this object refers to a particular } instance of a resource, as defined by } chasResourceIndex, for which this relationship is ^^^^^^^^^^^^^^^^^ What is this supposed to be? } defined. This together with } chasLogResourceLocationType and } chasLogResourceLocation completes the mapping of } the logical configuration on to the physical } module and resource combination." } ::= { chasLogResourceEntry 2 } } ------------------------------------------------- } chasPowerSupplyIndex OBJECT-TYPE } SYNTAX INTEGER } ACCESS read-only } STATUS mandatory } DESCRIPTION } "An index value that uniquely identifies a power } supply. This may correspond to a hardware power } supply slot, which may or may not be the same as a } network device slot (chasSlotIndex)." ^^^^^^^^^^^^^^ What should this be? } ::= { chasPowerSupplyEntry 1 } ------------------------------------------------ Jim Barnes (barnes@xylogics.com)
- Re: draft MIB Jim Barnes