suggestion for rmonEtherMib-II
Gary Ellis <garye@hpspdla.spd.hp.com> Wed, 15 January 1992 02:27 UTC
Received: from nri.reston.va.us by NRI.NRI.Reston.VA.US id aa20316; 14 Jan 92 21:27 EST
Received: from mtigate.mti.com by NRI.NRI.Reston.VA.US id aa20312; 14 Jan 92 21:27 EST
Received: by mtigate.mti.com id AA12674 (5.65+/IDA-1.3.5); Tue, 14 Jan 92 17:38:57 -0800
Received: from telford.iag.hp.com by mtigate.mti.com with SMTP id AA12670 (5.65+/IDA-1.3.5); Tue, 14 Jan 92 17:38:54 -0800
Received: from hpspd.spd.hp.com by telford.iag.hp.com with SMTP (16.6/IAG42.42) id AA11095; Tue, 14 Jan 92 17:38:45 -0800
Received: from hpspdla.spd.hp.com by hpspd.spd.hp.com with SMTP (15.11/15.5+IOS 3.12) id AA06580; Tue, 14 Jan 92 17:39:05 pst
Received: by hpspdla.spd.hp.com (16.6/15.5+IOS 3.12) id AA16280; Tue, 14 Jan 92 17:37:25 -0800
From: Gary Ellis <garye@hpspdla.spd.hp.com>
Message-Id: <9201150137.AA16280@hpspdla.spd.hp.com>
Subject: suggestion for rmonEtherMib-II
To: RMONMIB mailing list <rmonmib@lexcel.com>
Date: Tue, 14 Jan 1992 17:37:24 -0800
X-Mailer: ELM [version 2.3 PL11]
The owner objects in each table are currently writable at any time. It seems to me that they are good candidates for the not_writable_when_status_is_valid restriction. Allowing owner strings to be changed during data collection seems sort of counter to the accountability features we wanted to achieve for multiple manager support don't you think? [note that this is a suggestion for the next version of the mib] --------------------------------------------------------- Gary Ellis (garye@hpspd.spd.hp.com) Hewlett-Packard Company -- Intelligent Networks Operation
- suggestion for rmonEtherMib-II Gary Ellis