Re: question re: charPortAdminStatus
Bob Stewart <rlstewart@eng.xyplex.com> Mon, 14 September 1992 18:42 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa18253;
14 Sep 92 14:42 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa18249;
14 Sep 92 14:42 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa20125;
14 Sep 92 14:46 EDT
Received: by inet-gw-2.pa.dec.com; id AA18244; Mon, 14 Sep 92 11:46:13 -0700
Received: by nsl.pa.dec.com; id AA08750; Mon, 14 Sep 92 11:29:52 -0700
Received: by nsl.pa.dec.com; id AA08746; Mon, 14 Sep 92 11:29:52 -0700
Received: by inet-gw-2.pa.dec.com; id AA17274; Mon, 14 Sep 92 11:29:46 -0700
Received: by xap.xyplex.com id <AA00223@xap.xyplex.com>;
Mon, 14 Sep 92 14:28:26 -0500
Date: Mon, 14 Sep 92 14:28:26 -0500
Message-Id: <9209141928.AA00223@xap.xyplex.com>
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: char-mib@pa.dec.com
In-Reply-To: Jim Barnes's message of Fri,
11 Sep 1992 13:39:26 EDT <20388.9209111739@spock.xylogics.com>
Subject: Re: question re: charPortAdminStatus
First the easy one: the only archive I know of is the GNU emacs file I've kept, which stands at a bit over 2 megabytes. Regarding the statuses, charPortAdminStatus is advisory and charPortOperStatus is reality. Timing for charPortOperStatus to follow charPortAdminStatus is somewhat implementation dependent, but I'd expect setting charPortAdminStatus to 'off' to be very shortly followed by charPortOperStatus going to 'down', with all active connections abruptly terminated. Setting charPortAdminStatus to 'disabled' is the kind and gentle way to shut off a port. When all connections for the port have gone away on their own, charPortOperStatus should go to 'down'. Bob
- question re: charPortAdminStatus Jim Barnes
- Re: question re: charPortAdminStatus Bob Stewart