The gateway responds to standard SNMPv2 OIDs from the
SNMPv2-MIB and IF-MIB namespaces. The reference below shows
the values most likely to be useful when integrating an Uplevel
site into an SNMP-based monitoring system; the sample values are
representative of what a polled gateway will return.
General system
| Item | OID | Example |
|---|---|---|
| System description | .1.3.6.1.2.1.1.1.0 |
STRING: Uplevel Systems UG-101 Gateway |
| System uptime | .1.3.6.1.2.1.1.3.0 |
Timeticks: (193583855) 22 days, 9:43:58.55 |
| System name | .1.3.6.1.2.1.1.5.0 |
STRING: gateway |
| System date | .1.3.6.1.2.1.25.1.2.0 |
STRING: 2021-3-2,1:3:15.0,+0:0 |
Ethernet interfaces
The gateway exposes per-interface counters in the standard
IF-MIB table. Indexes differ per platform; the values below
were captured on a UG-101.
Internet (eth0, ifIndex 4)
| Item | OID |
|---|---|
| Name | .1.3.6.1.2.1.2.2.1.2.4 |
| Operational status | .1.3.6.1.2.1.2.2.1.7.4 |
| RX bytes | .1.3.6.1.2.1.2.2.1.10.4 |
| TX bytes | .1.3.6.1.2.1.2.2.1.16.4 |
AUX Internet (agl0, ifIndex 20)
| Item | OID |
|---|---|
| Name | .1.3.6.1.2.1.2.2.1.2.20 |
| Operational status | .1.3.6.1.2.1.2.2.1.7.20 |
| RX bytes | .1.3.6.1.2.1.2.2.1.10.20 |
| TX bytes | .1.3.6.1.2.1.2.2.1.16.20 |
LAN ports 2–8 (eth1–eth7, ifIndex 5–11)
For each LAN port n (with ifIndex = n + 3), the four entries
follow the same pattern:
Name .1.3.6.1.2.1.2.2.1.2.<ifIndex>
Operational status .1.3.6.1.2.1.2.2.1.7.<ifIndex>
RX bytes .1.3.6.1.2.1.2.2.1.10.<ifIndex>
TX bytes .1.3.6.1.2.1.2.2.1.16.<ifIndex>
So Port 2 is eth1 at ifIndex 5, Port 3 is eth2 at
ifIndex 6, and so on through Port 8 = eth7 at ifIndex 11.
Operational status returns INTEGER: up(1) or INTEGER: down(2).
RX/TX bytes return Counter32 values; for high-throughput links,
monitoring tooling should use the matching ifHC* 64-bit
counters under .1.3.6.1.2.1.31.1.1.1.* if they’re needed.
Layer-2 bridges
| Item | OID |
|---|---|
| Layer-2 forwarding table (ARP) | .1.3.6.1.2.1.3.1 |
Routing tables
| Item | OID |
|---|---|
| IP address table | .1.3.6.1.2.1.4.20 |
| IP routing table | .1.3.6.1.2.1.4.21 |
| TCP connection table | .1.3.6.1.2.1.6.13 |
Memory usage
| Item | OID |
|---|---|
| Physical memory size | .1.3.6.1.2.1.25.2.3.1.5.1 |
| Physical memory used | .1.3.6.1.2.1.25.2.3.1.6.1 |
| Virtual memory size | .1.3.6.1.2.1.25.2.3.1.5.3 |
| Virtual memory used | .1.3.6.1.2.1.25.2.3.1.6.3 |
| Memory buffers size | .1.3.6.1.2.1.25.2.3.1.5.6 |
| Memory buffers used | .1.3.6.1.2.1.25.2.3.1.6.6 |
| Cached memory size | .1.3.6.1.2.1.25.2.3.1.5.7 |
| Cached memory used | .1.3.6.1.2.1.25.2.3.1.6.7 |
All sizes and “used” values are reported as INTEGER in
kilobytes.
Processor utilization
The gateway has four cores. Each core’s instantaneous load percentage is exposed independently:
| CPU | OID |
|---|---|
| CPU 1 | .1.3.6.1.2.1.25.3.3.1.2.768 |
| CPU 2 | .1.3.6.1.2.1.25.3.3.1.2.769 |
| CPU 3 | .1.3.6.1.2.1.25.3.3.1.2.770 |
| CPU 4 | .1.3.6.1.2.1.25.3.3.1.2.771 |
Values return as INTEGER percentages 0–100.