Re: Mib questions
kzm@hls.com (Keith McCloghrie) Tue, 15 September 1992 05:55 UTC
Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA13029; Tue, 15 Sep 92 01:55:45 -0400
Received: from LANSLIDE.HLS.COM by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA13025; Tue, 15 Sep 92 01:55:40 -0400
Received: from nms.netman (nms.hls.com) by lanslide.hls.com (4.1/SMI-4.0) id AA19039; Mon, 14 Sep 92 22:55:58 PDT
Received: by nms.netman (4.1/SMI-4.1) id AA10413; Mon, 14 Sep 92 22:53:47 PDT
From: kzm@hls.com
Message-Id: <9209150553.AA10413@nms.netman>
Subject: Re: Mib questions
To: dan@lannet.com
Date: Mon, 14 Sep 1992 22:53:46 -0700
Cc: chassismib@cs.utk.edu
In-Reply-To: <9209100835.AA29439@moon.lannet.com>; from "Dan Romascanu" at Sep 10, 92 10:35 am
Organization: Hughes LAN Systems
X-Mailer: ELM [version 2.2 PL0]
Dan, > I would like to answer these > questions, not in order to give an authoritive answer but rather to > present how we understand what has been proposed untill now and how we > try to implement it. Good idea. I agree with most of your answers. Here's where we differ: > > 1) What is the scope of the chassis MIB? Is it limited > > the the devices covered in the Overview (section 5)? > Yes, I think we should limit the scope to 'networking devices' > as defined in the Overview. It is very tempting to extend the > scope ('The sky is the limit') but in order to be effective we > should limit now the scope and maybe later, when we will have > some implementation experience try to solve other problems of > mankind. If extending the scope were to require more or different MIB objects, then I'd agree, but if someone wants to apply the same MIB to a more general case, then I don't see any need to prohibit it. I think this can be handled by appropriate text to this effect in the Overview. > > 2) Do the terms "functional module" and "logical device" > > mean the same and are they things like routers, bridges, > > terminal servers, etc? > Yes, I think so. As Bob said, a "module" is a physical entity in the Chassis, whereas a logical device is something which has an agent. These can be the same but are not necesarily. > > A fundamentation question is just how is an agent that implements > > the chassis MIB suppose to get all the information about the other > > "logical devices" - 1) through SNMP requests to the other "logical > > devices", 2) through a private network protocol, 3) through a backplane > > bus using shared memory or messages between CPUs, or 4) through some > > "static" configuration file that is loaded at agent boot time (and > > maybe refreshed during running)? > > I really do not think that the Chassis MIB standard must address this > question which is a matter of implementation. Anyway, in my opinion: > 1) does not work in the SNMP framework, as all "logical devices" are > agents. > 2) could work > 3) the best > 4) could work, but it is the least efficient. I agree with all but your answer to 1), in that some (but not all) of the information could be obtained through SNMP. (Not that I recommend that.) Keith.
- Mib questions David Perkins
- Re: Mib questions Bob Stewart
- Re: Mib questions David Perkins
- Re: Mib questions Bob Stewart
- Re: Mib questions Kiho Yum
- Re: Mib questions Yosef Zur
- Mib questions Dan Romascanu
- Re: Mib questions Keith McCloghrie
- Re: Mib questions Keith McCloghrie
- Re: Mib questions Bob Stewart
- Re: Mib questions Bob Stewart
- Re: Mib questions Keith McCloghrie
- Re: Mib questions CASE
- Re: Mib questions David L. Arneson (arneson@ctron.com)