Re: Future

Steve Horowitz <witz@chipcom.com> Thu, 09 June 1994 17:50 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07422; 9 Jun 94 13:50 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa07416; 9 Jun 94 13:49 EDT
Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA09251; Thu, 9 Jun 1994 13:29:22 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 13:29:21 EDT
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from chipcom.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA09244; Thu, 9 Jun 1994 13:29:18 -0400
Received: from teach.stealth ([151.104.20.60]) by chipcom.com (4.1/SMI-4.0) id AA13703; Thu, 9 Jun 94 13:27:36 EDT
Received: by teach.stealth (4.1/SMI-4.1) id AA01091; Thu, 9 Jun 94 13:23:35 EDT
Date: Thu, 9 Jun 94 13:23:35 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Horowitz <witz@chipcom.com>
Message-Id: <9406091723.AA01091@teach.stealth>
To: chassismib@cs.utk.edu
Subject: Re: Future


I'm curious how the chassis MIB can "fix the repeater ID problem" ?

Or better yet, I want to be able to fix the problem where I have
an agent representing 100's of repeaters, so that the user does
not have to go through configuration hell to retrieve that
information.

Same issue for bridges.

I wonder what would be the right approach to solve this.

-- Steve

> From owner-chassismib@CS.UTK.EDU Thu Jun  9 13:05:25 1994
> Return-Path: <owner-chassismib@CS.UTK.EDU>
> Received: from CS.UTK.EDU by chipcom.com (4.1/SMI-4.0)
> 	id AA12087; Thu, 9 Jun 94 13:05:20 EDT
> Errors-To: owner-chassismib@CS.UTK.EDU
> Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
> 	id MAA04609; Thu, 9 Jun 1994 12:24:48 -0400
> X-Resent-To: chassismib@CS.UTK.EDU ; Thu, 9 Jun 1994 12:24:47 EDT
> Errors-To: owner-chassismib@CS.UTK.EDU
> Received: from SynOptics.COM by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
> 	id MAA04602; Thu, 9 Jun 1994 12:24:45 -0400
> Received: from donatello (donatello.synoptics.com) by SynOptics.COM (4.1/SMI-4.1)
> 	id AA10321; Thu, 9 Jun 94 09:22:28 PDT
> Received: by donatello (4.1/2.0N)
> 	   id AA12416; Thu, 9 Jun 94 09:22:29 PDT
> Message-Id: <9406091622.AA12416@donatello>
> Date: Thu, 9 Jun 94 09:22:29 PDT
> From: Andrew Bierman <abierman@synoptics.com>
> To: chassismib@CS.UTK.EDU, arneson@ctron.com
> Subject: Re: Future
> Content-Length: 634
> X-Lines: 17
> Status: RO
> 
> > Well another IETF is comming up on us.  I guess I would like to find
> > out if there is interest in getting together to discuss where we are
> > going with the chassis MIB.
> > ...
> > /David Arneson [arneson@ctron.com] [ (603)337-5238 ]
> > 
> I'm interested in a chassis MIB that provides:
>    1) a good definition of a chassis
>    2) an inventory of physical components in a chassis
>    3) a fix for the "Repeater ID" problem
>    4) an indication of the SNMP capabilities of each component 
>       (i.e. pointers to MIBs, other agents in the chassis)
>    5) a physical sub-component hierarchy
> 
> I hope you can get a BOF scheduled soon...
> 
> --andy;
>