PCUBE-CONFIG-COPY-MIB: View SNMP OID List / Download MIB

VENDOR: P-CUBE LTD.


 Home MIB: PCUBE-CONFIG-COPY-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, PCUBE-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 pcubeConfigCopyMIB 1.3.6.1.4.1.5655.3.1
This 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
     pcubeConfigCopyMIBObjects 1.3.6.1.4.1.5655.3.1.1
         pcubeCopy 1.3.6.1.4.1.5655.3.1.1.1
             pcubeCopyTable 1.3.6.1.4.1.5655.3.1.1.1.1 no-access
A table of config-copy requests.
                 pcubeCopyEntry 1.3.6.1.4.1.5655.3.1.1.1.1.1 no-access
A 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)'.
                     pcubeCopyIndex 1.3.6.1.4.1.5655.3.1.1.1.1.1.1 integer32 no-access
Object 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.
                     pcubeCopyEntryRowStatus 1.3.6.1.4.1.5655.3.1.1.1.1.1.2 rowstatus read-write
This object can be used for creating/deleting entries from the table.
                     pcubeCopySourceFileType 1.3.6.1.4.1.5655.3.1.1.1.1.1.3 configfiletype read-write
Specifies the type of file to copy from. Currently only 'runningConfig(2)' is supported.
                     pcubeCopyDestFileType 1.3.6.1.4.1.5655.3.1.1.1.1.1.4 configfiletype read-write
Specifies the type of file to copy to. currently only 'startupConfig(1)' is supported.
     pcubeConfigCopyMIBConformance 1.3.6.1.4.1.5655.3.1.2
         pcubeConfigCopyMIBGroups 1.3.6.1.4.1.5655.3.1.2.1
             pcubeCopyGroup 1.3.6.1.4.1.5655.3.1.2.1.1
A collection of objects used for specifying the configuration of the copy operation.
         pcubeConfigCopyMIBCompliances 1.3.6.1.4.1.5655.3.1.2.2
             pcubeConfigCopyMIBCompliance 1.3.6.1.4.1.5655.3.1.2.2.1
A compliance statement defined in this MIB module, for SCE SNMP agents.