Path Configuration Table
ricci@mtunm.att.com Mon, 27 July 1992 21:18 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa14867; 27 Jul 92 17:18 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa14863; 27 Jul 92 17:18 EDT
Received: from CS.UTK.EDU by NRI.Reston.VA.US id aa22188; 27 Jul 92 17:19 EDT
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA09420; Mon, 27 Jul 92 16:36:14 -0400
Received: from att-out.att.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA09416; Mon, 27 Jul 92 16:36:06 -0400
Message-Id: <9207272036.AA09416@CS.UTK.EDU>
Date: Mon, 27 Jul 1992 16:32:00 -0400
From: ricci@mtunm.att.com
To: fddi-mib@cs.utk.edu
Cc: anil@levers.enet.dec.com, mtunm!ricci@gatech.edu
Subject: Path Configuration Table
Fddi MIB group, After reviewing the Path Configuration Table proposal put out on the list I became suspicious that it wasn't consistent with the definition of the table given in the SMT document (either that or it broke the lexicographical ordering imposed by SNMP). A brief description of the problem - the token ordering of the resources inserted on the path could not be preserved (if you'd like a better explanation send me some mail and I'll go into more detail). I've conferred with Anil on this matter and he agrees that the Table is inconsistent with the SMT document. I sent him a version of the table that I used in our implementation and, after a tweek to a object definition, we have agreed to mutually present this table to the group (see below). One other question for the working group: was a consensus reached on resource indexes? More to the point, are the indexes used for PORTs and MACs in SNMP the same or different as the indexes used for the same resource in SMT (i.e. if a PORT has a resource index of 5 in SMT must its resource index be 5 in SNMP or can they be different) ? Note that in the definitions given below, it is assumed that the indexes are the same. Sal Ricci ------------------------------------------- snmpFddiPATHConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF SnmpFddiPATHConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "" -- I didn't feel like typing - pull the definition from the SMT document. REFERENCE "ANSI SMT Draft Rev. 7.2 { fddiPATH 18 }" ::= { snmpFddiPATH X } -- X to be filled in as appropriate. snmpFddiPATHConfigEntry OBJECT-TYPE SYNTAX SnmpFddiPATHConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A collection of objects containing information for a given PATH Configuration entry." INDEX { snmpFddiPATHConfigSMTIndex, snmpFddiPATHConfigPATHIndex, snmpFddiPATHConfigTokenOrder } ::= { snmpFddiPATHConfigTable 1 } SnmpFddiPATHConfigEntry ::= SEQUENCE { snmpFddiPATHConfigSMTIndex INTEGER, snmpFddiPATHConfigPATHIndex INTEGER, snmpFddiPATHConfigTokenOrder INTEGER, snmpFddiPATHConfigResourceType INTEGER, snmpFddiPATHConfigResourceIndex INTEGER, snmpFddiPATHConfigCurrentPath INTEGER } snmpFddiPATHConfigSMTIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The value of the SNMP SMT index associated with this configuration entry." ::= { snmpFddiPATHConfigEntry 1 } snmpFddiPATHConfigPATHIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The value of the PATH index associated with this configuration entry." ::= { snmpFddiPATHConfigEntry 2 } snmpFddiPATHConfigTokenOrder OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "An object associated with Token order for this entry. Thus if the token passes resources a,b,c and d, in that order, then the value of this object for these resources would be 1,2,3 and 4 respectively." ::= { snmpFddiPATHConfigEntry 3 } snmpFddiPATHConfigResourceType OBJECT-TYPE SYNTAX INTEGER { MAC(2), PORT(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The type of resource associated with this configuration entry." ::= { snmpFddiPATHConfigEntry 4 } snmpFddiPATHConfigResourceIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The value of the SNMP index used to refer to the instance of this resource." -- This resource index is currently the same in SNMP as it is in SMT. ::= { snmpFddiPATHConfigEntry 5 } snmpFddiPATHConfigCurrentPath OBJECT-TYPE SYNTAX INTEGER { isolated(1), local(2), secondary(3), primary(4), concatenated(5), thru(6) } ACCESS read-only STATUS mandatory DESCRIPTION "The current insertion status for this resource on this PATH." ::= { snmpFddiPATHConfigEntry 1 }
- Path Configuration Table ricci