PEAKFLOW-SP-MIB :: deviceTotalFlows

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PEAKFLOW-SP-MIB › deviceTotalFlows

deviceTotalFlows

Module: PEAKFLOW-SP-MIB

OID (symbolic): PEAKFLOW-SP-MIB::deviceTotalFlows

OID (numeric): 1.3.6.1.4.1.9694.1.4.2.1.11

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Accumulative flow count per SP device.

What is deviceTotalFlows?

A running total of the flow records this Peakflow SP device has processed since it started (or since the counter last wrapped). Admins can poll it periodically to derive a flow processing rate and confirm the device is still actively receiving flow data from monitored routers.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9694.1.4.2.1.11
snmpwalk -v2c -c public <target> PEAKFLOW-SP-MIB::deviceTotalFlows

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9694.1.4.2.1.11.1
snmpget -v2c -c public <target> PEAKFLOW-SP-MIB::deviceTotalFlows.1

Start monitoring Arbor Networks traffic analysis/DDoS detection appliances with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PEAKFLOW-SP-MIB::deviceTotalFlows OID value, configure state conditions and alerts, and monitor any Arbor Networks traffic analysis/DDoS detection appliances from a single console.

How to Use in IPNetwork Monitor

Select an Arbor Networks traffic analysis/DDoS detection 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 deviceTotalFlows into the Find box to locate it in the OID tree, then select it and click OK. It reports the accumulative flow count per SP device. 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.9694arbornetworksARBOR-SMI
1.3.6.1.4.1.9694.1arbornetworksProductsARBOR-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9694.1.4peakflowSPMIBPEAKFLOW-SP-MIB
1.3.6.1.4.1.9694.1.4.2peakflowSPMgrPEAKFLOW-SP-MIB
1.3.6.1.4.1.9694.1.4.2.1deviceHealthPEAKFLOW-SP-MIB
1.3.6.1.4.1.9694.1.4.2.1.11deviceTotalFlowsPEAKFLOW-SP-MIB