Plans for this year?

Dan Romascanu <> Wed, 12 January 1994 15:18 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa07148; 12 Jan 94 10:18 EST
Received: from CS.UTK.EDU by IETF.CNRI.Reston.VA.US id aa07144; 12 Jan 94 10:18 EST
Received: from localhost by CS.UTK.EDU with SMTP (8.6.4/2.8s-UTK) id JAA19808; Wed, 12 Jan 1994 09:58:52 -0500
X-Resent-To: chassismib@CS.UTK.EDU ; Wed, 12 Jan 1994 09:58:48 EST
Errors-to: owner-chassismib@CS.UTK.EDU
Received: from by CS.UTK.EDU with SMTP (8.6.4/2.8s-UTK) id JAA19735; Wed, 12 Jan 1994 09:58:43 -0500
Received: from by (5.65b/4.0.071791-PSI/PSINet) via SMTP; id AA25082 for; Wed, 12 Jan 94 09:58:34 -0500
Received: from by (4.1/SMI-4.1) id AA22336; Wed, 12 Jan 94 16:57:19 IST
Received: by (4.1/SMI-4.1) id AA23036; Wed, 12 Jan 94 16:57:19 IST
Date: Wed, 12 Jan 94 16:57:19 IST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dan Romascanu <>
Message-Id: <>
Subject: Plans for this year?

>1. Did anybody implement the chassis mib? 
>   If so, I'd like to hear from you if you care to share your experiences.

We have implemented part of the initial Chassis MIB proposal in our
LET-18/36/10 agents by means of variables in our private space. We
do support mapping of resources relative to modules and connectivity
of modules and ports to networks on the backplane.
I think the initial model does not present any implementability 
problems if the managed box provides the means of conveying the
information to the box agent. We also implemenented management of 
hardware resources. However, we did not yet implement any of the
later refinements brought around the last meeting of the Chassis MIB
in Columbus.

Dan Romascanu, LANNET Data Communications Ltd., Voice: 972-3-6458-414