JETNEXUS-MIB :: jetnexusOverallInputBytes

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JETNEXUS-MIB › jetnexusOverallInputBytes

jetnexusOverallInputBytes

Module: JETNEXUS-MIB

OID (symbolic): JETNEXUS-MIB::jetnexusOverallInputBytes

OID (numeric): 1.3.6.1.4.1.38370.1.1.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: from jetnexus shared memory

What is jetnexusOverallInputBytes?

A running counter of total bytes received by the JetNexus ALB-X load balancer across all traffic, pulled straight from the appliance's shared-memory stats; admins graph it to see overall inbound throughput trends.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.38370.1.1.1
snmpwalk -v2c -c public <target> JETNEXUS-MIB::jetnexusOverallInputBytes

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.38370.1.1.1.1
snmpget -v2c -c public <target> JETNEXUS-MIB::jetnexusOverallInputBytes.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> jetnexusOverallInputBytes.1

Start monitoring jetNEXUS application delivery controller / load balancer appliance with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JETNEXUS-MIB::jetnexusOverallInputBytes OID value, configure state conditions and alerts, and monitor any jetNEXUS application delivery controller / load balancer appliance from a single console.

How to Use in IPNetwork Monitor

Select a jetNEXUS application delivery controller / load balancer appliance 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 jetnexusOverallInputBytes into the Find box to locate it in the OID tree, then select it and click OK. It reports from jetnexus shared memory. 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 Counter64-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 (6 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
Numeric OIDNameModule
1.3.6.1.4.1.38370jetnexusMIBJETNEXUS-MIB
1.3.6.1.4.1.38370.1jetnexusDataJETNEXUS-MIB
1.3.6.1.4.1.38370.1.1jetnexusGlobalJETNEXUS-MIB
1.3.6.1.4.1.38370.1.1.1jetnexusOverallInputBytesJETNEXUS-MIB