DECnet MIB question
"John A. Shriver" <jas@proteon.com> Tue, 11 August 1992 15:19 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id ab03258; 11 Aug 92 11:19 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa03254; 11 Aug 92 11:19 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa18007; 11 Aug 92 11:19 EDT
Received: by inet-gw-2.pa.dec.com; id AA03542; Tue, 11 Aug 92 08:03:03 -0700
Received: by nsl.pa.dec.com; id AA06261; Tue, 11 Aug 92 07:14:11 -0700
Received: by nsl.pa.dec.com; id AA06257; Tue, 11 Aug 92 07:13:40 -0700
Received: by inet-gw-2.pa.dec.com; id AA01794; Tue, 11 Aug 92 07:12:58 -0700
Received: from sonny.proteon.com by monk.proteon.com (5.65/1.8)id AA14922; Tue, 11 Aug 92 10:18:15 -0400
Received: by sonny.proteon.com (3.2/SMI-3.2)id AA10123; Tue, 11 Aug 92 10:11:45 EDT
Date: Tue, 11 Aug 1992 10:11:45 -0400
From: "John A. Shriver" <jas@proteon.com>
Message-Id: <9208111411.AA10123@sonny.proteon.com>
To: deb@tci.bell-atl.com
Cc: phiv-mib@pa.dec.com
In-Reply-To: Debasis Dalapati's message of Mon, 10 Aug 92 18:57:49 EDT <9208102257.AA19615@tci.bell-atl.com>
Subject: DECnet MIB question
Date: Mon, 10 Aug 92 18:57:49 EDT From: deb@tci.bell-atl.com (Debasis Dalapati) Hi, I am looking at the document "DECnet Digital Network Architecture Phase IV, Routing layer Functional Specification, December 1983" and not sure how the following management information is modeled in the Phase IV mib specification. 1) page 38-39, adjacency database. Adjacencies are for broadcast circuits, neighbors on non-broadcast circuits, all router adjacencies on the ethernets and endnodes in the home-area. In the RFC1289, page 50 for Adjacency group, PhivAdjEntry is INDEXed by phivAdjCircuitIndex. The DESCRIPTION for phivAdjCircuitIndex is "A unique index value for each known circuit". I suspect that the wording is a little off here. I suspect that the index is unique for each adjacency. Each adjacency on a line can be viewed as a circuit. The wording of the RFC probably needs to be fixed here. This is fine if only the broadcast circuit adjacencies are of management interest. Are the broadcast router adjacencies and endnode adjacencies are of no management interest? Why? Is it because they are of transient nature based on the hello timer? If all kind of adjacencies at a given point of time are of management interest, should not the INDEXing be through phivAdjNodeAddr with some way of identifying the multiple broadcast circuit adjacencies? You don't want to use the node address because you'd need to double index, because you can have multiple adjacencies with the same node. Double indexed tables are a bitch. 2) In the RFC1289, page 53-59 talks about line table and non-broadcast line table. In the UNIX environment, these tables may be initialized from the kernel. In the non-UNIX environment, at least for my target environment, it is other way; the drivers ( at least the non-broadcast ones) start by reading these table. In other words, these tables are populated at initialization. Would it be appropriate to define a new ACCESS type that brings out the fact that some objects are writable at initialization only and then they are read-only? SNMP has never given a clear mapping of what an SNMP write does. Eg., is an SNMP write the same as an NCP SET or qan NCP DEFINE? To the best of my knowledge, the typical mapping is "SET", eg. only affect volatile database. 3) IfIndex is so specific to UNIX environment and it is used to describe few objects in the MIB spec! A non-UNIX person just asked me the question after looking at the MIB spec? Huh? IfIndex was derived in the router environment, which was, after all, the first SNMP target. It corresponds quite closely with the interface numbers in our router.
- DECnet MIB question Debasis Dalapati
- DECnet MIB question John A. Shriver
- Re: DECnet MIB question Art Berggreen