---
oid: "1.3.6.1.2.1.22.2.3.2.1.4"
short-description: "rptrMonitorPortHCReadableOctets OBJECT-TYPE"
last-modified: "2020-06-23"
parent-oid: "1.3.6.1.2.1.22.2.3.2.1"
---

## OID: `1.3.6.1.2.1.22.2.3.2.1.4`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snmpDot3RptrMgt(22) rptrMonitorPackage(2) rptrMonitorPortInfo(3) rptrMonitor100PortTable(2) rptrMonitor100PortEntry(1) rptrMonitorPortHCReadableOctets(4)}
```

### Description

```asn1
rptrMonitorPortHCReadableOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the number of octets contained in
valid frames that have been received on this port.
This counter is incremented by OctetCount for each
frame received on this port which has been
determined to be a readable frame (i.e., including
FCS octets but excluding framing bits and dribble
bits).
This statistic provides an indicator of the total
data transferred.
This counter is a 64-bit version of rptrMonitor-
PortReadableOctets. It should be used by network
management protocols which suppport 64-bit counters
(e.g. SNMPv2).
Conformance clauses for this MIB are defined such
that implementation of this object is not required
in a system which does not support 100Mb/s.
However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 2108](https://www.rfc-editor.org/rfc/rfc2108.html)

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.