All MIBs › PCUBE-CONFIG-COPY-MIB
Organization: Cisco Systems, Inc.
Last Updated: 2006-04-06
Category: DPI/Subscriber Management, Server/Systems Management
Description: Manages configuration file copy operations on Cisco P-Cube Service Control Engine devices, including source, destination, and transfer status.
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.
What Is PCUBE-CONFIG-COPY-MIB?
PCUBE-CONFIG-COPY-MIB is a vendor-specific SNMP module for Cisco Service Control Engine (SCE) devices, originally from P-Cube (acquired by Cisco), that manages copying configuration files between the running configuration, startup configuration, and other file locations on the Service Control Operating System (SCOS). It exposes a copy operation table where an administrator defines source and destination file types and triggers/monitors the copy via row status control. Its monitoring focus is software/configuration management status — tracking whether a config-copy operation (e.g., saving running config to startup config) succeeded, failed, or is in progress is essential for confirming configuration persistence before a reboot or during automated provisioning. This MIB conceptually parallels the standard CISCO-CONFIG-COPY-MIB pattern used elsewhere in Cisco's device family, adapted for the SCE/SCOS platform. It is deployed on Cisco SCE appliances used for deep packet inspection and subscriber traffic management in service provider networks. Network engineers evaluating or troubleshooting this functionality can download the PCUBE-CONFIG-COPY-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in PCUBE-CONFIG-COPY-MIB. 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) appliance
Monitoring Examples
An administrator creates a row in pcubeCopyTable/pcubeCopyEntry via pcubeCopyEntryRowStatus, setting pcubeCopySourceFileType to the running configuration and pcubeCopyDestFileType to startup configuration, then polls pcubeCopyIndex-keyed status to confirm the copy completed. If the row status transitions to an error state instead of active/completed, it indicates the config-copy operation failed, risking loss of configuration changes on next reboot. This is typically checked immediately after making manual SCE configuration changes to ensure they persist.
What Can Be Monitored
- config-copy operation status
- source/destination file type
- copy operation row status
- running-to-startup config save success
Imported Objects
From PCUBE-SMI
| pcubeMgmt | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| RowStatus | |
| TEXTUAL-CONVENTION |
OIDs
RFC description
Cisco PCube Service Control Engine (SCE) configuration copy MIB for managing running and startup configuration file operations.
Start monitoring Cisco Service Control Engine (SCE) appliance (configuration copy operations) 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.