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.
Parsed from file rfc1516.mib.txt
Company: None
Module: SNMP-REPEATER-MIB
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.
Parsed from file SNMP-REPEATER-MIB.mib
Module: SNMP-REPEATER-MIB
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." ::= { rptrMonitor100PortEntry 4 }
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." ::= { rptrMonitor100PortEntry 4 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.3.29.2.3.2.1.1 | rptrMonitorPortIsolates | 0 | 0 | This counter is incremented by one each time that the repeater port automatically isolates as a consequence of false carrier even… |
| 1.3.6.1.3.29.2.3.2.1.2 | rptrMonitorPortSymbolErrors | 0 | 0 | This counter is incremented by one each time when valid length packet was received at the port and there was at least one occurre… |
| 1.3.6.1.3.29.2.3.2.1.3 | rptrMonitorPortUpper32Octets | 0 | 0 | This object is the number of octets contained in valid frames that have been received on this port, modulo 2**32. That is, it co… |