Questions on hetrogenous device chassis (novice - long)
ulowell!tpdhp.teleglobe.com!michali@harvard.harvard.edu (Paul Michali) Wed, 09 December 1992 21:37 UTC
Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA22125; Wed, 9 Dec 92 16:37:16 -0500
Received: from harvard.harvard.edu by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA22120; Wed, 9 Dec 92 16:37:13 -0500
Received: by harvard.harvard.edu (5.54/a0.25) (for chassismib@cs.utk.edu) id AA16042; Wed, 9 Dec 92 16:37:06 EST
Received: by ulowell.ulowell.edu id AA06239 (5.65c+/IDA-1.4.4 for harvard!cs.utk.edu!chassismib); Wed, 9 Dec 1992 16:13:51 -0500
Received: by tpdhp.teleglobe.com (/\==/\ Smail3.1.25.1 #25.7) id <m0mzYf9-000RTzC@tpdhp.teleglobe.com>; Wed, 9 Dec 92 16:09 EST
Message-Id: <m0mzYf9-000RTzC@tpdhp.teleglobe.com>
From: ulowell!tpdhp.teleglobe.com!michali@harvard.harvard.edu
Subject: Questions on hetrogenous device chassis (novice - long)
To: chassismib@cs.utk.edu
Date: Wed, 09 Dec 1992 16:09:42 -0500
Mailer: Elm [revision: 66.25]
Hello, Myself and several associates have been tasked to develop a SNMP agent for a chassis that will contain up to 16 cards. The 16 slots can contain any one of four different board types. For example, slots 1,3,5 could have LAN cards, slots 9-15 could have X.25 cards and slot 4 could have a Frame Relay card. One entity could consume more than one slot (i.e. multiple ports over several cards), but one could never have more than one entity per slot. One could have one entity per slot, but there are cases where the user can have one X.25 controller with multiple I/O port cards in several slots. We have just received the chassis MIB that this working group is working on, and we are trying to understand the MIB better and see how it would fit our application. Granted we are all new at SNMP, MIBs, etc. so please bear with us (or yell at us if this is an inappropriate place to post this). Here is a list of questions from us (there may be some overlap of questions as I just mashed them all together, trying to eliminate redundancies). A1) Are segments internal or external connections to the chassis ? A2) Do they link two entitys, represent a port to port connection, or reflect the type of interface connected? B1) In general how is a slot related to a set of MIBs? Is chasConfigIndexType used to point to a MIB for that device? B2) What if a slot has an entity that has > 1 MIB to reflect it's functional- ity? B3) How does the chassis MIB tie together slots, entities, and ports on an entity? C1) On the ChasEntityEntry is the object id a branch or a leaf on the MIB tree ? C2) Related to that, is the ChasEntityTable used to validate requests for standard MIB variables by providing details of what variables are valid for a particular community name, or are the leafs on the table entries the actual objects themselves. To give an example, if I want to get SysDescr for a board in a slot that we identify with community name "boardX", can I send a normal get request for SysDescr in community boardX, and have the agent validate this request against the entries in the ChasEntityTable before returning the value, or should the request itself be for the ChasEntityEntry that describes the SysDescr for that community. Thanks in advance for any information, PCM, and others. --------------------------------------------+-------------------------------- Teleglobe (was Memotec (was infinet)) | michali@tpdhp.teleglobe.com 40 High Street | ulowell!tpdhp!michali N. Andover, MA 01845 | (508)-681-0600 ext. 4240
- Questions on hetrogenous device chassis (novice -… Paul Michali