charPortHardware question
Jim Barnes <barnes@xylogics.com> Wed, 19 August 1992 21:20 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id ab07160;
19 Aug 92 17:20 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa07156;
19 Aug 92 17:20 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa20282;
19 Aug 92 17:21 EDT
Received: by inet-gw-2.pa.dec.com; id AA01217; Wed, 19 Aug 92 14:20:50 -0700
Received: by nsl.pa.dec.com; id AA27006; Wed, 19 Aug 92 14:20:33 -0700
Received: by inet-gw-1.pa.dec.com; id AA18473; Wed, 19 Aug 92 14:20:30 -0700
Received: from spock.xylogics.com by atlas.xylogics.com with SMTP id AA17861
(5.65c/UK-2.1-920813); Wed, 19 Aug 1992 17:20:49 -0400
Received: by spock.xylogics.com id AA04116 (4.1/UK-2.1-920729);
Wed, 19 Aug 92 17:19:01 EDT
Message-Id: <4116.9208192119@spock.xylogics.com>
From: Jim Barnes <barnes@xylogics.com>
Date: Wed, 19 Aug 1992 17:19:00 EDT
X-Mailer: Mail User's Shell (7.1.0 4/25/90)
To: char-mib@pa.dec.com
Subject: charPortHardware question
In rfc1316, the charPortHardware object is defined as follows:
> charPortHardware OBJECT-TYPE
> SYNTAX AutonomousType
> ACCESS read-only
> STATUS mandatory
> DESCRIPTION
> "A reference to hardware MIB definitions specific to
> a physical port's external connector. For example,
> if the connector is RS-232, then the value of this
> object refers to a MIB sub-tree defining objects
> specific to RS-232. If an agent is not configured
> to have such values, the agent returns the object
> identifier:
>
> nullHardware OBJECT IDENTIFIER ::= { 0 0 }
> "
> ::= { charPortEntry 4 }
My question is, what is the accepted value that should be returned
for this object if the connector is RS-232? Should the complete
OID for the RS-232 subtree (1.3.6.1.2.1.10.33) be returned here?
Something else?
Jim Barnes (barnes@xylogics.com)
- charPortHardware question Jim Barnes
- Re: charPortHardware question Bob Stewart