---
oid: "1.3.6.1.4.1.2338.4.2.4.2.1.1"
short-description: "vrptrMonUpper32TotalOctets OBJECT-TYPE"
last-modified: "2022-02-25"
parent-oid: "1.3.6.1.4.1.2338.4.2.4.2.1"
---

## OID: `1.3.6.1.4.1.2338.4.2.4.2.1.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2338 vsnmpDot3RptrMgt(4) vrptrMonitorPackage(2) vrptrMonitorAllRptrInfo(4) vrptrMon100Table(2) vrptrMon100Entry(1) vrptrMonUpper32TotalOctets(1)}
```

### Description

```asn1
vrptrMonUpper32TotalOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of octets contained in the valid frames that have been received on the ports in this repeater, modulo 2**32. That is, it contains the upper 32 bits of a 64-bit counter, of which the lower 32 bits are contained in the rptrMonTotalOctets object. If an implementation can not obtain a count of octets as seen by the repeater itself, the 64-bit value may be the summation of the values of the rptrMonitorPortReadableOctets counters combined with the corresponding rptrMonitorPortUpper32Octets counters for all of the ports in the repeater.
This statistic provides an indicator of the total data transferred within the repeater.
This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMP V1) and are used to manage a repeater type of 100Mb/s.
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."
```

**Classification:** MIB object for network management

### 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.