Re: Chassis MIB comments

Kiho Yum <kxy@NSD.3Com.COM> Mon, 17 August 1992 23:20 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA17878; Mon, 17 Aug 92 19:20:53 -0400
Received: from bridge2.NSD.3Com.COM by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA17874; Mon, 17 Aug 92 19:20:50 -0400
Received: from rainier.NSD.3Com.COM by bridge2.NSD.3Com.COM with SMTP id AA18042 (5.65c/IDA-1.4.4nsd for <>); Mon, 17 Aug 1992 16:20:43 -0700
Received: by rainier.NSD.3Com.COM id AA00358 (5.65c/IDA-1.4.4-910725); Mon, 17 Aug 1992 16:20:40 -0700
From: Kiho Yum <kxy@NSD.3Com.COM>
Message-Id: <199208172320.AA00358@rainier.NSD.3Com.COM>
Subject: Re: Chassis MIB comments
Date: Mon, 17 Aug 92 16:20:39 PDT
In-Reply-To: <9208172140.AA11832@yeti.ctron>; from "" at Aug 17, 92 5:40 pm
X-Mailer: ELM [version 2.3 PL11]

> >5) I like chasConfigIfIndex. For a device with 2 interfaces there
> >is currently no way of knowing which physical interface they map onto.
> However how much use is it if we have multiple instances of the interface
> group of MIB II?

What about a router with 3 interfaces, 2 connected to different internal 
segments and one connected to an external Ethernet.  I can imagine the 
interface group for that entity would contain three "rows".  Through
ifType, I could tell the external interface from the internal interfaces
(that reminds me, what value of ifType do we give the internal interfaces?
other(1) ?), but I don't know how to distinguish which interface is connected 
to which segment.

It seems chasConfigIfIndex solves this problem.  Or have I missed something?