bitErrorsCorrected1xUpLinkHorizontal

WHISP-APS-MIB · .1.3.6.1.4.1.161.19.3.1.2.2.47

Object

scalar deprecated SNMPv2-TCDisplayString
Number of bit errors corrected on average per fragment on up link at 1X (QPSK).
For MIMO and forward.
For MIMO this is the horizontal path.
Fragments received in MIMO-A will only be counted on vertical.
				[This variable is deprecated, please refer whispBoxLink OIDs]

Context

MIB
WHISP-APS-MIB
OID
.1.3.6.1.4.1.161.19.3.1.2.2.47
Type
scalar
Access
readonly
Status
deprecated
Parent
whispApsLinkTestResult
Groups
1

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'WHISP-APS-MIB' -M '/opt/observium/mibs/cambium:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'WHISP-APS-MIB::bitErrorsCorrected1xUpLinkHorizontal.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'WHISP-APS-MIB' -M '/opt/observium/mibs/cambium:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'WHISP-APS-MIB::bitErrorsCorrected1xUpLinkHorizontal'

Syntax

Source
SNMPv2-TCDisplayString
Base type
OctetString
Display format
255a
Type Description
Represents textual information taken from the NVT ASCII
          
character set, as defined in pages 4, 10-11 of RFC 854.
          
To summarize RFC 854, the NVT ASCII repertoire specifies:
          
  - the use of character codes 0-127 (decimal)
          
  - the graphics characters (32-126) are interpreted as
    US ASCII
          
  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
    meanings specified in RFC 854
          
  - the other 25 codes have no standard interpretation
          
  - the sequence 'CR LF' means newline
          
  - the sequence 'CR NUL' means carriage-return
          
  - an 'LF' not preceded by a 'CR' means moving to the
    same column on the next line.
          
  - the sequence 'CR x' for any x other than LF or NUL is
    illegal.  (Note that this also means that a string may
    end with either 'CR LF' or 'CR NUL', but not with CR.)
          
Any object defined using this syntax may not exceed 255
characters in length.

Values & Constraints

Type Constraints
range: 0..255

Conformance