TRANGO-APEX-SYS-MIB :: sysUnitType

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TRANGO-APEX-SYS-MIB › sysUnitType

sysUnitType

Module: TRANGO-APEX-SYS-MIB

OID (symbolic): TRANGO-APEX-SYS-MIB::sysUnitType

OID (numeric): 1.3.6.1.4.1.5454.1.60.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Unit Type

What is sysUnitType?

This OID sets or reports the role of this Trango Apex radio unit: notype(0), active(1), or standby(2). It's used to identify which unit in a protected (active/standby) radio link pair this device currently represents.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5454.1.60.1.1
snmpwalk -v2c -c public <target> TRANGO-APEX-SYS-MIB::sysUnitType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5454.1.60.1.1.1
snmpget -v2c -c public <target> TRANGO-APEX-SYS-MIB::sysUnitType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.5454.1.60.1.1.1 i <value>

Start monitoring Trango Systems Apex wireless backhaul radio (firmware/FPGA/OS version status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TRANGO-APEX-SYS-MIB::sysUnitType OID value, configure state conditions and alerts, and monitor any Trango Systems Apex wireless backhaul radio (firmware/FPGA/OS version status) from a single console.

How to Use in IPNetwork Monitor

Select a Trango Systems Apex wireless backhaul radio (firmware/FPGA/OS version 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 sysUnitType into the Find box to locate it in the OID tree, then select it and click OK. It reports the unit Type. 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 an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value changes unexpectedly, since which type is correct for this unit depends on your redundancy setup and an unplanned change often indicates a failover or misconfiguration. 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.1sysTRANGO-APEX-SYS-MIB
1.3.6.1.4.1.5454.1.60.1.1sysUnitTypeTRANGO-APEX-SYS-MIB