Re: Chassis MIB Proposal Sun, 16 August 1992 09:28 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA24425; Sun, 16 Aug 92 05:28:45 -0400
Received: from [] by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA24289; Sun, 16 Aug 92 05:28:14 -0400
Received: from ([]) by (4.1/3.1.090690-Lannet Data Communications) id AA10116; Thu, 13 Aug 92 08:16:24 IDT
Received: by (4.1/SMI-4.1) id AA00303; Thu, 13 Aug 92 08:16:22 IDT
Date: Thu, 13 Aug 92 08:16:22 IDT
Message-Id: <>
To:, (Pablo Brenner)
Subject: Re: Chassis MIB Proposal

Shalom Pablo,

> (Dan Romascanu) writes:
>> b. In the previous proposal repeater and concentrator were separated.
>> I think it is more correct. I hardly can see why an FDDI concentrator
>> should be described as a repeater.

> The correction was made because dividing into repeater and concentrator
> would be very confusing, the FDDI case is obvious but where would you
> put a Token Ring MAU, it is of course a concentrator, but I guess it will
> be hard to explain your customers that what they thought it was 
> a multiport Token Ring Repeater is not a repeater any more but a 
> concentrator.
I had in mind exactly the same example. Token Ring MAU is a concentrator 
but not necessarely a repeater. If you have passive (non-regenerative)
ports on your cards, you only have a concentrator and not a repeater.
> Now how would you define an Ethernet HUB?, it is in fact a repeater,
> but it's much like a MAU than a regular repeater, etc, etc....

Both. So chasEntityFunction will be 130 (2^1 + 2^7) - 1 for repeater, 7
for MAU.

> I asked Keith to do one of the following:
> 1. To explain what is a repeater and what's a concentrator or
> 2. To join them

> He choosed 2 for the sake of simplicity, if the wg doesn't like this
> solution so we must explain in the MIB what do we mean.

At the time you asked for the change, 'mau' was not inside, but 
'concentrator' was. Now we have 'mau' but 'concentrator' was left out.
On my opinion we should have either all three options defined,
or one single option like physicalLayerDevice to unify everything.
> --Pablo

Dan Romascanu
Systems Group Manager

LANNET Data Communications
Tel Aviv, Israel

Voice: 972-3-6458414
Fax:   972-3-5447146