PCUBE-SMI

Description: Defines the Cisco P-Cube enterprise SMI structure, establishing the OID subtree hierarchy for all SCE MIB modules.

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.

PCUBE-SMI is Cisco's Structure of Management Information module for the P-Cube enterprise branch, established after Cisco's acquisition of P-Cube, whose products became the Cisco Service Control Engine (SCE) platform. This module itself contains no runtime data objects -- it purely defines the enterprise OID subtree and naming conventions under which all other SCE-related MIB modules register their object identifiers. As a pure SMI/registration module it exposes no monitorable hardware or software status data on its own; any monitoring of CPU, memory, interface, or traffic-shaping status happens in the dependent SCE MIB modules that build on this structure. Administrators typically need this PCUBE-SMI MIB file loaded first, since every MIB registered beneath pcube in this tree depends on it purely for OID namespace allocation and the dependent modules will not compile without it. It is relevant wherever Cisco SCE deep packet inspection/traffic management appliances are deployed, serving as the root of their management OID hierarchy rather than a data source itself.

This is a structural SMI module defining only the OID subtree root for Cisco P-Cube/SCE products; it has no runtime data objects of its own (sample_objects is empty), so there is no monitoring scenario to describe -- actual polling happens against the SCE-specific MIB modules registered under this tree.

Vendor-private SMI root MIB from Procera Networks (P-Cube) that defines the enterprise OID structure and common object definitions for P-Cube DPI and traffic management products.