TRANGO-APEX-RF-MIB :: rfInDataOctets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TRANGO-APEX-RF-MIB › rfInDataOctets

rfInDataOctets

Module: TRANGO-APEX-RF-MIB

OID (symbolic): TRANGO-APEX-RF-MIB::rfInDataOctets

OID (numeric): 1.3.6.1.4.1.5454.1.60.3.11.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Display total number of incoming Octets in FPGA

What is rfInDataOctets?

A running count of the total octets received into the radio's FPGA from the RF side, a baseline throughput counter for the receive direction of this microwave link.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5454.1.60.3.11.1
snmpwalk -v2c -c public <target> TRANGO-APEX-RF-MIB::rfInDataOctets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5454.1.60.3.11.1.1
snmpget -v2c -c public <target> TRANGO-APEX-RF-MIB::rfInDataOctets.1

Start monitoring Trango Apex point-to-point wireless backhaul radio, ODU (RF power/frequency/modulation status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TRANGO-APEX-RF-MIB::rfInDataOctets OID value, configure state conditions and alerts, and monitor any Trango Apex point-to-point wireless backhaul radio, ODU (RF power/frequency/modulation status) from a single console.

How to Use in IPNetwork Monitor

Select a Trango Apex point-to-point wireless backhaul radio, ODU (RF power/frequency/modulation status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type rfInDataOctets into the Find box to locate it in the OID tree, then select it and click OK. It reports the display total number of incoming Octets in FPGA. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.5454trangoTRANGO-APEX-MIB
1.3.6.1.4.1.5454.1tbwTRANGO-APEX-MIB
1.3.6.1.4.1.5454.1.60apexTRANGO-APEX-MIB
Numeric OIDNameModule
1.3.6.1.4.1.5454.1.60.3rfTRANGO-APEX-RF-MIB
1.3.6.1.4.1.5454.1.60.3.11rfInTRANGO-APEX-RF-MIB
1.3.6.1.4.1.5454.1.60.3.11.1rfInDataOctetsTRANGO-APEX-RF-MIB