Re: Chassis MIB comments
Mike MacFaden <mike@premisys.com> Mon, 21 June 1993 20:33 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11649; 21 Jun 93 16:33 EDT
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa11645; 21 Jun 93 16:33 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA27298; Mon, 21 Jun 93 15:58:18 -0400
X-Resent-To: chassismib@CS.UTK.EDU ; Mon, 21 Jun 1993 15:58:17 EDT
Errors-To: owner-chassismib@CS.UTK.EDU
Received: from fernwood.mpk.ca.us by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA27253; Mon, 21 Jun 93 15:58:14 -0400
Received: by fernwood.mpk.ca.us; id AA04364; Mon, 21 Jun 93 13:01:00 -0700
Received: by premisys (4.1/SMI-4.1m) id AA02143; Mon, 21 Jun 93 12:41:15 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mike MacFaden <mike@premisys.com>
Message-Id: <9306211941.AA02143@premisys>
Subject: Re: Chassis MIB comments
To: chassismib@cs.utk.edu
Date: Mon, 21 Jun 1993 12:41:14 -0700
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Length: 1566
Ok, one lurker speaks up: Bob Stewart writes: >It would be good to get this work finished, but we don't seem to be settling >very well. People seem apathetic or confused, or just too busy to think about >it. It would be helpful if people would at least express that level of input. >We need a sense of: > > 1) Like it as it is > > 2) It needs a little more work > > 3) It needs a lot more work > > 4) Don't care > > 5) Care, but don't have time to assess work needed > > 6) Care, but don't understand > > 7) Let's wait for OSI to define it > > 8) We don't need to finish this I joined this group late, and would have to vote for 6 as I am still learning to program snmp and do mib development. Our product needs this mib. It matches our product layout (slot/card/unit). For instance, A generic mib browser should be able to ask our product "What's installed?" and the response should be something like: Slot 2 is a Dual Port T1. The first t1 is CSU, second slot is CEPT. Slot 3 is a Dual Port T1. The first t1 is CSU, second slot is CEPT redundant Slot 4 is a Primary Rate ISDN 8 ports Slot 5 is a Inverse Mux Slot 6 is a RS-530 High Speed Data Slot 7 is a V.35 High Speed Data Slot 8 is a 8 Port E&M.... Then to answer the question: "How is it configured?" the response should be the standard internet mib that corresponds to the logical/physical interface (T1/E1, ISDN,...). This is possible with any existing standard mib? I think not. Regards, Mike MacFaden Premisys Communications, Inc Palo Alto, CA USA
- Chassis MIB comments Niels Ole Brunsgaard
- Re: Chassis MIB comments arneson
- Re: Chassis MIB comments Kiho Yum
- Chassis MIB comments Keith McCloghrie
- Re: Chassis MIB comments David L. Arneson (arneson@ctron.com)
- Chassis MIB comments Dan Romascanu
- Re: Chassis MIB comments Keith McCloghrie
- Re: Chassis MIB comments Keith McCloghrie
- Re: Chassis MIB comments Dan Romascanu
- Chassis MIB comments David Perkins
- Re: Chassis MIB comments David L. Arneson (arneson@ctron.com)
- Re: Chassis MIB comments Bob Stewart
- Re: Chassis MIB comments Kiho Yum
- Chassis MIB comments Chris Chiotasso
- Re: Chassis MIB comments Manu Kaycee
- Re: Chassis MIB comments Chris Chiotasso
- RE: Chassis MIB comments {3COM/PDD/PeteW}
- Chassis MIB comments Chris Chiotasso
- RE: Chassis MIB comments Manu Kaycee
- Re: Chassis MIB comments David L. Arneson
- Re: Chassis MIB comments David L. Arneson
- Re: Chassis MIB comments Manu Kaycee
- Re: Chassis MIB comments Bob Stewart
- Re: Chassis MIB comments Mahendra J. Kaycee
- Re: Chassis MIB comments Mike MacFaden
- Chassis MIB comments Dan Romascanu
- Re: Chassis MIB comments Joseph Zur