NETSCREEN-INTERFACE-MIB :: nsIfFlowInByte

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NETSCREEN-INTERFACE-MIB › nsIfFlowInByte

nsIfFlowInByte

Module: NETSCREEN-INTERFACE-MIB

OID (symbolic): NETSCREEN-INTERFACE-MIB::nsIfFlowInByte

OID (numeric): 1.3.6.1.4.1.3224.9.3.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Incoming byte number arriving at the this interface

What is nsIfFlowInByte?

Read-only Counter32 total of bytes received on this interface, one of the core throughput counters an admin graphs to track inbound bandwidth usage.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3224.9.3.1.3
snmpwalk -v2c -c public <target> NETSCREEN-INTERFACE-MIB::nsIfFlowInByte

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3224.9.3.1.3.1
snmpget -v2c -c public <target> NETSCREEN-INTERFACE-MIB::nsIfFlowInByte.1

Start monitoring Juniper NetScreen firewalls with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NETSCREEN-INTERFACE-MIB::nsIfFlowInByte OID value, configure state conditions and alerts, and monitor any Juniper NetScreen firewalls from a single console.

How to Use in IPNetwork Monitor

Select a Juniper NetScreen firewall 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 nsIfFlowInByte into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the incoming byte number arriving at the this interface. 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 (8 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.3224netscreenNETSCREEN-SMI
1.3.6.1.4.1.3224.9netscreenInterfaceNETSCREEN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3224.9.3nsIfFlowTableNETSCREEN-INTERFACE-MIB
1.3.6.1.4.1.3224.9.3.1nsIfFlowEntryNETSCREEN-INTERFACE-MIB
1.3.6.1.4.1.3224.9.3.1.3nsIfFlowInByteNETSCREEN-INTERFACE-MIB