Re: Adjacency index
saperia@tcpjon.ogo.dec.com Fri, 28 August 1992 21:36 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa06712;
28 Aug 92 17:36 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa06708;
28 Aug 92 17:36 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa17313;
28 Aug 92 17:38 EDT
Received: by inet-gw-2.pa.dec.com; id AA24676; Fri, 28 Aug 92 14:37:18 -0700
Received: by nsl.pa.dec.com; id AA13219; Fri, 28 Aug 92 14:13:46 -0700
Received: by nsl.pa.dec.com; id AA13215; Fri, 28 Aug 92 14:13:43 -0700
Received: by inet-gw-2.pa.dec.com; id AA23147; Fri, 28 Aug 92 14:13:39 -0700
Received: by tcpjon.ogo.dec.com (5.57/ULTRIX-fma-071891); id AA11490;
Fri, 28 Aug 92 17:16:12 -0400
Message-Id: <9208282116.AA11490@tcpjon.ogo.dec.com>
To: Debasis Dalapati <deb@tci.bell-atl.com>
Cc: saperia@tcpjon.ogo.dec.com, phiv-mib@pa.dec.com
Subject: Re: Adjacency index
In-Reply-To: Your message of "Fri,
28 Aug 92 14:38:38 EDT." <9208281838.AA24207@tci.bell-atl.com>
Date: Fri, 28 Aug 92 17:16:12 -0400
From: saperia@tcpjon.ogo.dec.com
X-Mts: smtp
Debasis, >>Could you repeat once more what the "INDEX" specification would look like for >>phivAdjEntry object ? Sure here is the entire table: Here is how the new table would look with new names etc. Rather than tacking an N on at the end of each name, I just added node to the name in most cases which makes the meaning of the objects clear (I hope). phivAdjNodeTable OBJECT-TYPE SYNTAX SEQUENCE OF PhivAdjNodeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The Adjacent Node Table." ::= { adjacency 1 } phivAdjNodeEntry OBJECT-TYPE SYNTAX PhivAdjNodeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "There is one entry in the table for each adjacency." INDEX { phivAdjNodeCircuitIndex, phivAdjAddr } ::= { phivAdjNodeTable 1 } PhivAdjNodeEntry ::= SEQUENCE { phivAdjNodeCircuitIndex INTEGER, phivAdjAddr PhivAddr, phivAdjNodeBlockSize INTEGER, phivAdjNodeListenTimer INTEGER (1..65535), phivAdjNodeCircuitEtherServPhysAddr OCTET STRING, phivAdjNodeType INTEGER, phivAdjNodeState INTEGER, phivAdjNodePriority INTEGER, phivAdjNodeExecListenTimer INTEGER (1..65535) } phivAdjNodeCircuitIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A unique index value for each known circuit. This value is the same as phivCircuitIndex and identifies the circuit over which the adjacency is realized." ::= { phivAdjNodeEntry 1 } phivAdjAddr OBJECT-TYPE SYNTAX PhivAddr -- OCTET STRING (SIZE (2)) ACCESS read-only STATUS mandatory DESCRIPTION "The address of the adjacent node." ::= { phivAdjNodeEntry 2 } phivAdjNodeBlockSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This read-only parameter is the block size that was negotiated with the adjacent Routing layer during Routing initialization over a particular circuit. It includes the routing header, but excludes the data link header. This parameter is qualified by ADJACENT NODE." ::= { phivAdjNodeEntry 3 } phivAdjNodeListenTimer OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "This value determines the maximum number of seconds allowed to elapse before Routing receives some message (either a Hello message or a user message) from the adjacent node on the circuit. It was agreed during Routing initialization with the adjacent Routing layer. This parameter is qualified by ADJACENT NODE." ::= { phivAdjNodeEntry 4 } phivAdjNodeCircuitEtherServPhysAddr OBJECT-TYPE SYNTAX OCTET STRING ( SIZE (6) ) ACCESS read-only STATUS mandatory DESCRIPTION "This parameter indicates the Ethernet physical address of an adjacent node that is being serviced on this circuit. This parameter is a qualifier for SERVICE SUBSTATE." ::= { phivAdjNodeEntry 5 } phivAdjNodeType OBJECT-TYPE SYNTAX INTEGER { routing-III (1), nonrouting-III (2), area (3), routing-IV (4), nonrouting-IV (5) } ACCESS read-only STATUS mandatory DESCRIPTION "This parameter indicates the type of adjacency. For adjacent nodes, this is a read-only parameter that indicates the type of the reachable adjacent node. NOTE: The routing-III and nonrouting-III values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155)" ::= { phivAdjNodeEntry 6 } phivAdjNodeState OBJECT-TYPE SYNTAX INTEGER { initializing (1), -- Ethernet one-way up (2), -- Ethernet two-way run (3), -- The eight DDCMP/X.25 states circuit-rejected (4), data-link-start (5), routing-layer-initialize (6), routing-layer-verify (7), routing-layer-complete (8), off (9), halt (10) } ACCESS read-only STATUS mandatory DESCRIPTION "This value indicates the state of a router adjacency. On adjacencies over a circuit of type (phivCircuitCommonType) Ethernet, CI, or FDDI, with an adjacent node of type (phivAdjNodeType) ROUTING IV or AREA, this variable is the state of the Ethernet Initialization Layer for this adjacency, and can have values INITIALIZING or UP. (See Section 9.1.1 of DECnet Phase IV Routing Layer Functional Specification.) On adjacencies over a circuit of type (phivCircuitCommonType) Ethernet, CI, or FDDI, with an adjacent node of type (phivAdjNodeType) NONROUTING IV, this variable will always take on the value UP. On adjacencies over a circuit of type (phivCircuitCommonType) DDCMP POINT, DDCMP CONTROL, DDCMP TRIBUTARY, DDCMP DMC, or X.25, this variable is the state of the Routing Layer Initialization Circuit State. (See section 7.3, ibid.) It can have values between RUN and HALT. On adjacencies over a circuit of type (phivCircuitCommonType) OTHER, this variable may be used in a manner consistent with the Initialization Layer used on that circuit." ::= { phivAdjNodeEntry 7 } phivAdjNodePriority OBJECT-TYPE SYNTAX INTEGER (0..255) ACCESS read-only STATUS mandatory DESCRIPTION "Priority assigned by the adjacent node for this circuit." ::= { phivAdjNodeEntry 8 } phivAdjNodeExecListenTimer OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "This read-only value determines the maximum number of seconds allowed to elapse before Routing receives some message (either a Hello message or a user message) from the adjacent node on the circuit. It was agreed during Routing initialization with the adjacent Routing layer." ::= { phivAdjNodeEntry 9 }
- Adjacency index saperia
- Adjacency index John A. Shriver
- Adjacency index John A. Shriver
- Re: Adjacency index Bob Stewart
- Re: Adjacency index saperia
- Adjacency index John A. Shriver
- Re: Adjacency index Bob Stewart
- Re: Adjacency index saperia
- Re: Adjacency index Art Berggreen
- Re: Adjacency index saperia
- Re: Adjacency index Bob Stewart
- Re: Adjacency index saperia
- Re: Adjacency index saperia
- Re: Adjacency index Debasis Dalapati
- Re: Adjacency index Debasis Dalapati
- Re: Adjacency index saperia
- Re: Adjacency index Art Berggreen
- Re: Adjacency index Debasis Dalapati
- Re: Adjacency index saperia
- Re: Adjacency index saperia