IETF Logo Mail Archive

Re: New overview text in Chassis MIB

Bob Stewart <rlstewart@eng.xyplex.com> Thu, 15 October 1992 17:49 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA17789; Thu, 15 Oct 92 13:49:15 -0400
Received: from xap.xyplex.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA17784; Thu, 15 Oct 92 13:49:11 -0400
Received: by xap.xyplex.com id <AA02265@xap.xyplex.com>; Thu, 15 Oct 92 13:47:06 -0500
Date: Thu, 15 Oct 1992 13:47:06 -0500
Message-Id: <9210151847.AA02265@xap.xyplex.com>
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: chassismib@cs.utk.edu
In-Reply-To: Keith McCloghrie's message of Mon, 12 Oct 92 16:26:55 PDT <9210122326.AA01186@nms.netman>
Subject: Re: New overview text in Chassis MIB 


I was one who spoke up for multiple instances of the Chassis MIB.  In our new
chassis, we'd have to go out of our way NOT to have them.  We will implement
the chassis MIB along with the agent that goes in each of our devices, and we
have no coordination among them as to who would have an only copy.  They get
their information the same way, so would have the same information.  The
benefit is independence and redundancy.  It makes no difference which one you
talk to.

	Bob

v2.30.2 | Report a Bug | By Email | System Status