Re: Dense?
kzm@hls.com (Keith McCloghrie) Wed, 16 September 1992 05:56 UTC
Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA18039; Wed, 16 Sep 92 01:56:28 -0400
Received: from LANSLIDE.HLS.COM by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA18035; Wed, 16 Sep 92 01:56:24 -0400
Received: from nms.netman (nms.hls.com) by lanslide.hls.com (4.1/SMI-4.0) id AA04198; Tue, 15 Sep 92 22:56:39 PDT
Received: by nms.netman (4.1/SMI-4.1) id AA07306; Tue, 15 Sep 92 22:54:23 PDT
From: kzm@hls.com
Message-Id: <9209160554.AA07306@nms.netman>
Subject: Re: Dense?
To: chassismib@cs.utk.edu
Date: Tue, 15 Sep 1992 22:54:22 -0700
Organization: Hughes LAN Systems
X-Mailer: ELM [version 2.2 PL0]
> >Finally, is this simple example a "good" one to > >use for further discussion? What other additional > >information needs to be added (maybe information > >about backplane(s))? > > Sounds pretty good to me. It should probably have a couple of segments to > play with. If you'd like to try provoking some discussion, let it have a > repeater card and let that repeater card be able to hook to two different > segments at the same time and not repeat them. At the risk of another "tweeet" from Jeff, I wonder if people think it would be useful to have an additional explanatory section (i.e., not in the MIB section) in the document give an example of how a sample configuration of modules in a chassis would be represented in the MIB e.g., a cross-mixture of Dave's example and the one which indirectly led to the formation of this WG (extract from last November's Repeater MIB WG meeting minutes reproduced below). Keith. ------------ EXAMPLE Slot Device Backplane 1 1 1 2 1 1 3 2 1 3 2 2 4 3 2 5 3 2 devices 1,3 are repeaters; device 2 is a bridge.
- Dense? David Perkins
- Re: Dense? David L. Arneson (arneson@ctron.com)
- Re: Dense? Bob Stewart
- Re: Dense? CASE
- Re: Dense? Keith McCloghrie
- Re: Dense? Bob Stewart