PCUBE-SE-MIB :: tpNumUdpActiveFlowsPeak

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PCUBE-SE-MIB › tpNumUdpActiveFlowsPeak

tpNumUdpActiveFlowsPeak

Module: PCUBE-SE-MIB

OID (symbolic): PCUBE-SE-MIB::tpNumUdpActiveFlowsPeak

OID (numeric): 1.3.6.1.4.1.5655.4.1.9.1.1.12

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: Indicates the peak value of tpNumUdpActiveFlows since the last time it was cleared or the system started.

What is tpNumUdpActiveFlowsPeak?

The highest value tpNumUdpActiveFlows has reached since the last time it was cleared or the system started. An admin uses this to see the busiest UDP-flow load this traffic processor has handled.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5655.4.1.9.1.1.12
snmpwalk -v2c -c public <target> PCUBE-SE-MIB::tpNumUdpActiveFlowsPeak

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5655.4.1.9.1.1.12.1
snmpget -v2c -c public <target> PCUBE-SE-MIB::tpNumUdpActiveFlowsPeak.1

Start monitoring Cisco SCE2000/SE100 Service Control Engine platforms with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PCUBE-SE-MIB::tpNumUdpActiveFlowsPeak OID value, configure state conditions and alerts, and monitor any Cisco SCE2000/SE100 Service Control Engine platforms from a single console.

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.5655pcubePCUBE-SMI
1.3.6.1.4.1.5655.4pcubeWorkgroupPCUBE-SMI
Numeric OIDNameModule
1.3.6.1.4.1.5655.4.1pcubeSEObjsPCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.9trafficProcessorGrpPCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.9.1tpInfoTablePCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.9.1.1tpInfoEntryPCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.9.1.1.12tpNumUdpActiveFlowsPeakPCUBE-SE-MIB