PACKETLOGIC-MIB

Description: Provides top-level SNMP management objects for Procera Networks PacketLogic DPI and traffic management appliances.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

PACKETLOGIC-MIB provides the top-level SNMP management objects for Procera Networks' PacketLogic deep packet inspection (DPI) and traffic-shaping appliances, used by carriers and enterprises for bandwidth management and traffic policy enforcement. It exposes packet-processing performance data, covering both receive and transmit paths, including current, rolling-average ("Mom"), and peak ("Max") values for traffic volume and drops. This makes it directly useful for monitoring the software/traffic-processing health of the appliance—spikes in packetprocessingRxDropsVal or packetprocessingTxDropsVal indicate congestion or overload conditions in the DPI engine, effectively a performance/fault indicator analogous to CPU load on a router. PACKETLOGIC-MIB SNMP monitoring in production deployments typically centers on exactly these throughput and drop counters rather than static configuration objects. The module also defines sub-trees like psm and pbs, suggesting policy/session management components layered under the same enterprise OID space, though it does not appear to depend heavily on external standard MIBs beyond the base SMI. It is deployed in ISP and large-enterprise network cores where PacketLogic units sit inline to shape and inspect subscriber or WAN traffic.

An admin would poll packetprocessingRxVal and packetprocessingTxVal for current throughput, alongside packetprocessingRxMax/packetprocessingTxMax to see peak load since last reset, to gauge how close the appliance is running to capacity. Rising packetprocessingRxDropsVal or packetprocessingTxDropsVal relative to packetprocessingRxVal/packetprocessingTxVal signals that the DPI engine is dropping packets under load, a strong indicator the box needs more capacity or policy tuning. The packetlogic2 subtree groups these processing counters, while psm and pbs likely hold session and policy-related objects for deeper diagnostics.