IETF Logo Mail Archive

Re: Problem with RFC1658 Character MIB object - charPortInFlowTypes

Bob Stewart <bstewart@cisco.com> Fri, 07 February 1997 02:37 UTC

Received: from cnri by ietf.org id aa20872; 6 Feb 97 21:37 EST
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa02438; 6 Feb 97 21:37 EST
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id VAA15799 for snmpv2-outgoing; Thu, 6 Feb 1997 21:28:22 -0500 (EST)
X-Sender: bstewart@puli.cisco.com
Message-Id: <v0302090faf2043d1a0a8@[171.69.128.42]>
In-Reply-To: <199702062208.OAA00180@eng_serv.simpact.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-pression: awestruck amazement
Date: Thu, 06 Feb 1997 21:29:27 -0500
To: Ron Tabor <rtabor@simpact.com>
From: Bob Stewart <bstewart@cisco.com>
Subject: Re: Problem with RFC1658 Character MIB object - charPortInFlowTypes
Cc: SNMPv2 Mailing List <snmp2@tis.com>
Sender: owner-snmpv2@ex.tis.com
Precedence: bulk

Circa 2:10 PM -0800 2/6/97, Ron Tabor bitwhacked:
>I am returning a value of 96 in my agent to indicate enqHost and
>enqTerm. The problem is, every manager that I have used to view
>this information displays the value as a backward single quote "`".
>Apparently this is the ascii representation of 96.  Unfortunately,
>this isn't very useful for anyone trying to read the MIB values.
>
>I considered that maybe I should be sending a string "96", but the
>OCTET STRING size of 1 prohibits that.
>
>I am wondering if anyone else has run across this, or if anyone
>can give me a clue what I am missing.

You're doing it right.  The management station is brain dead.  Without
information to the contrary an OCTET STRING should be display as hex, not
ASCII.

	Bob

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