Chassis MIB Proposal
{3COM/PDD/PeteW}@pdd.3mail.3com.com Tue, 04 January 1994 10:09 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01783; 4 Jan 94 5:09 EST
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa01779; 4 Jan 94 5:09 EST
Received: from localhost by CS.UTK.EDU with SMTP (8.6.4/2.8s-UTK) id EAA12256; Tue, 4 Jan 1994 04:50:31 -0500
X-Resent-To: chassismib@CS.UTK.EDU ; Tue, 4 Jan 1994 04:50:30 EST
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from relay2.UU.NET by CS.UTK.EDU with SMTP (8.6.4/2.8s-UTK) id EAA12237; Tue, 4 Jan 1994 04:50:27 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: {3COM/PDD/PeteW}@pdd.3mail.3com.com
MMDF-Warning: Parse error in original version of preceding line at IETF.CNRI.Reston.VA.US
Received: from cixgate.3com.com (via [192.156.136.10]) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA07942; Tue, 4 Jan 94 04:50:26 -0500
Received: from gw.3Com.COM by cixgate.3com.com (4.1/SMI-4.1/3com-cixgate-GCA-931027-01) id AA14346; Tue, 4 Jan 94 01:50:08 PST
Received: by gw.3Com.COM id AA18670 (5.65c/IDA-1.4.4 for chassismib@cs.utk.edu); Tue, 4 Jan 1994 01:50:23 -0800
Date: Tue, 04 Jan 1994 09:44:00 -0800
Subject: Chassis MIB Proposal
To: chassismib@cs.utk.edu
Message-Id: <940104.015138@3Mail.3Com.COM>
Msg-Date: 1994-01-04
Msg-Time: 09:41
FROM: Wilson, Peter TO: {chassismib@cs.utk.edu}:ugate:3com DATE: 01-04-94 TIME: 09:39 CC: SUBJECT: Chassis MIB Proposal PRIORITY: ATTACHMENTS: ------------------------------------------------------------------------------ zero. Note that some implementations of this MIB may make this object writable. The effect of doing this is to allow standard management operations to dynamically reconfigure the resource of the chassis. Note that even if a specific implementation allows this object to be written, such operations may still fail if an illegal assignment is attempted. Illegal assignment includes assignment to a non-existent row, assignment to an inappropriate entity, eg an 802.3 repeater port to a token ring! Successfully changing the value of this object may have the side effect of changing the value of chasPhyResEntitySubIndex. The change will also be reflected in the chasLogResourceTable." ::= { chasPhyResourceEntry 6 } chasPhyResEntitySubIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A value that allows correlation with the cahsLogResourceTable. For each resource in this table which is assigned to an entity, there will be a corresponding row in the chasLogResourceTable. The row in the logical table is identified by indexing that table on the values of chasPhyResAssignment and chasPhyResEntitySubIndex. If a resource is not currently assigned to an entity, the value of this object for that resource will be zero and there will be no corresponding entry in chasLogResourceTable." ::= { chasPhyResourceEntry 7 } -- Logical configuration/resource table chasLogResourceTable OBJECT-TYPE SYNTAX SEQUENCE OF ChasLogResourceEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains a row for each resource in the system that is currently assigned to a particular entity. This table allows a direct mapping from entity to resource via the indices. The resource itself is identified by its location within the chassis. Note that no changes can be made to this table directly. The table will change when the physical configuration of the chassis changes or when the resource assignment is changed by access to chasPhyResourceTable." ::= { chasResource 2 } chasLogResourceEntry OBJECT-TYPE SYNTAX ChasLogResourceEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Defines a single logical relationship." INDEX { chasLogResourceEntity, chasLogResourceEntitySubIndex } ::= { chasLogResourceTable 1 } ChasLogResourceEntry SEQUENCE { chasLogResEntity INTEGER, chasLogResEntitySubIndex INTEGER, chasLogResLocationType INTEGER, chasLogResLocation INTEGER, chasLogResID INTEGER } chasLogResEntity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The entity ID for which this logical configuration relationship exists." ::= { chasLogResourceEntry 1 } chasLogResEntitySubIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This object is used simply to provide for multiple resources assigned to a single entity." ::= { chasLogResourceEntry 2 } chasLogResLocationType OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This object, in conjuntion with the value of chaLogResLocation identifies the module on which the resource refered to by this table row resides." ::= { chasLogResourceEntry 3 } chasLogResLocation OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This object, in conjuntion with the value of chaLogResLocationType identifies the module on which the resource refered to by this table row resides." ::= { chasLogResourceEntry 4 } chasLogResID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A module potentially contains many resources. The value of this object identifies the specific resource instance on this module to which this table row defines an entity mapping." ::= { chasLogResourceEntry 5 } -- The chasInterconnect group. -- This group is OPTIONAL and is provided for those chassis that are -- prepared to or are capable of reporting internal resource interconnection -- information. The basic idea of this table is that it contains -- 'link descriptions'. Each such description documents a known connection -- between two resources in the chassis. There is no requirement to -- itemise all traffic links between resources in the chassis. For example -- if this were required then a link from every repeater port to every other -- repeater port in a repeater would be required. -- -- Useful interconnections that could be documented in this table are -- mappings from bridge and router ports to repeater ports. eg a -- bridge/router card contains a seperate bridge and router, but both share -- the same logical repeater ports to the backplane. eg: -- +-----------+ +----------------+ +-----------+ -- +<--]Bdge Port 1]<--] Bridge Relay ]-->]Bdge Port 2]-->+ -- ] +-----------+ +----------------+ +-----------+ ] -- ] ] -- V +-----------+ +----------------+ +-----------+ V -- +<--]Rter Port 1]<--] Relay Relay ]-->]Rter Port 2]-->+ -- ] +-----------+ +----------------+ +-----------+ ] -- ] ] -- +-------------+ +-------------+ -- ]Repeater Pt 1] ]Repeater Pt 2] -- +-------------+ +-------------+ -- Now in this case it is useful to know which bridge ports map to which -- repeater ports, given that both are in different entities. chasLinkTable OBJECT-TYPE SYNTAX SEQUENCE OF ChasLinkEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains entity/resource interconnection information. Note that this information in this table is read-only." ::= { chasInterconnect 1 } chasLinkEntry OBJECT-TYPE SYNTAX ChasLinkEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Each entry in this table describes a link between two resources." INDEX { chasLinkIndex } ::= { chasLinkTable 1 } ChasLogResourceEntry SEQUENCE { chasLinkIndex INTEGER, chasLinkFromLocType INTEGER, chasLinkFromLoc INTEGER, chasLinkFromResourceId INTEGER, chasLinkFromIf INTEGER, chasLinkToLocType INTEGER, chasLinkToLoc INTEGER, chasLinkToResourceId INTEGER, chasLinkToIf INTEGER } chasLinkIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This object is used to identify one of the link specifications in this table." ::= { chasLinkEntry 1 } chasLinkFromLocType OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A link is defined to be between one resource and another. This object identifies is a partial definition of one end of the link. This object in conjuntion with chasLinkFromLoc and chasLinkFromResourceId identfiy the start of the link." ::= { chasLinkEntry 2 } chasLinkFromLoc OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A link is defined to be between one resource and another. This object identifies is a partial definition of one end of the link. This object in conjuntion with chasLinkFromLocType and chasLinkFromResourceId identfiy the start of the link." ::= { chasLinkEntry 3 } chasLinkFromResourceId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A link is defined to be between one resource and another. This object identifies is a partial definition of one end of the link. This object in conjuntion with chasLinkFromLocType and chasLinkFromLoc identfiy the start of the link." ::= { chasLinkEntry 4 } chasLinkFromIfNumber OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This object can be used to correlate the resource to an entry in an ifTable visible through the entity to which this resource belongs. Without this object there is no correlation between a resource and
- Chassis MIB Proposal Dan Romascanu
- Re: Chassis MIB Proposal Pablo Brenner
- Re: Chassis MIB Proposal dan
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}
- Chassis MIB Proposal {3COM/PDD/PeteW}