All MIBs › PCUBE-SMI
Organization: Cisco Systems, Inc.
Last Updated: 2002-01-14
Category: DPI/Subscriber Management, Products/Registration
Description:
Defines the Cisco P-Cube enterprise SMI structure, establishing the OID subtree hierarchy for all SCE MIB modules.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| enterprises |
What Is PCUBE-SMI?
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.
IPNetwork Monitor allows you to monitor SNMP objects defined in PCUBE-SMI. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Cisco Service Control Engine (SCE) platform
Monitoring Examples
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.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| pcube | 1.3.6.1.4.1.5655 | The Structure of Management Information for the Pcube enterprise. | ||
| pcubeProducts | 1.3.6.1.4.1.5655.1 | pcubeProducts is the root OBJECT IDENTIFIER from which sysObjectID values are assigned. Actual values are defined in PCUBE-PRODUCTS-MIB. | ||
| pcubeModules | 1.3.6.1.4.1.5655.2 | pcubeModules provides a root object identifier from which MODULE-IDENTITY values may be assigned. | ||
| pcubeMgmt | 1.3.6.1.4.1.5655.3 | pcubeMgmt is the main subtree for new MIB development. | ||
| pcubeWorkgroup | 1.3.6.1.4.1.5655.4 | pcubeWorkgroup is the main subtree for objects and events of P-Cube's products. |
RFC description
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.
Start monitoring Cisco Service Control Engine (SCE) platform, ex-P-Cube (shared OID registration) 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.