PCUBE-CONFIG-COPY-MIB
Imported Objects
Objects
14 total| Object Name |
|---|
pcubeConfigCopyMIBThis MIB facilitates writing of running configuration of the SCOS to startup configuration. A config-copy operation is a request to copy a configuration file of a running SCOS. The term 'agent-config' will be used in this MIB to refer to either the running config or the startup config. The term SCE refers to Service Control Engine MODULE-IDENTITY .1.3.6.1.4.1.5655.3.1 |
pcubeConfigCopyMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.5655.3.1.1 |
pcubeCopy OBJECT IDENTIFIER .1.3.6.1.4.1.5655.3.1.1.1 |
pcubeCopyTableA table of config-copy requests. SEQUENCE OF PcubeCopyEntry .1.3.6.1.4.1.5655.3.1.1.1.1 |
pcubeCopyEntryA config-copy request. A management station wishing to save the running config may use any number to be used as an index. The station should then create the associated instance of the row status and row index objects. It should be noted however that currently 'pcubeCopySourceFileType' must be of 'runningConfig' type and 'pcubeCopyDestFileType' must be of 'startupConfig' type (that are the default values). After setting pcubeCopySourceFileType and pcubeCopyDestFileType objects by explicit SNMP request or or by default, the row status should be set to createAndGo to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of 'createAndGo(4)'. PcubeCopyEntry .1.3.6.1.4.1.5655.3.1.1.1.1.1 |
pcubeCopyIndexObject which specifies a unique entry in the pcubeCopyTable. A management station wishing to initiate a config-copy operation should use a random value for this object when creating or modifying an instance of a 'pcubeCopyEntry'. The RowStatus semantics of the 'pcubeCopyEntryRowStatus' object will prevent access conflicts. Integer32 .1.3.6.1.4.1.5655.3.1.1.1.1.1.1 |
pcubeCopyEntryRowStatusThis object can be used for creating/deleting entries from the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.5655.3.1.1.1.1.1.2 |
pcubeCopySourceFileTypeSpecifies the type of file to copy from. Currently only 'runningConfig(2)' is supported.rw ConfigFileType .1.3.6.1.4.1.5655.3.1.1.1.1.1.3 |
pcubeCopyDestFileTypeSpecifies the type of file to copy to. currently only 'startupConfig(1)' is supported.rw ConfigFileType .1.3.6.1.4.1.5655.3.1.1.1.1.1.4 |
pcubeConfigCopyMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.5655.3.1.2 |
pcubeConfigCopyMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.5655.3.1.2.1 |
pcubeCopyGroupA collection of objects used for specifying the configuration of the copy operation. Unknown .1.3.6.1.4.1.5655.3.1.2.1.1 |
pcubeConfigCopyMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.5655.3.1.2.2 |
pcubeConfigCopyMIBComplianceA compliance statement defined in this MIB module, for SCE SNMP agents. Unknown .1.3.6.1.4.1.5655.3.1.2.2.1 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.