CONFIG-COPY-MIB :: copyFailCause

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CONFIG-COPY-MIB › copyFailCause

copyFailCause

Module: CONFIG-COPY-MIB

OID (symbolic): CONFIG-COPY-MIB::copyFailCause

OID (numeric): 1.3.6.1.2.1.1.1.1.1.14

Node type: OBJECT-TYPE

Type: ConfigCopyFailCause

Access: read-only

Description: The reason why the config-copy operation failed. This object is instantiated only when the copyState for this entry is in the failed state.

What is copyFailCause?

This read-only object reports the specific reason a config-copy operation failed, and is only populated once copyState for that entry has reached the failed state. Admins check it to diagnose why an automated backup or restore didn't complete, such as an authentication or network error. For example, if a nightly config backup shows copyState as failed, an admin would read copyFailCause to see whether it was a connectivity issue or a bad file name before retrying.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.1.1.1.1.14
snmpwalk -v2c -c public <target> CONFIG-COPY-MIB::copyFailCause

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.1.1.1.1.14.1
snmpget -v2c -c public <target> CONFIG-COPY-MIB::copyFailCause.1

Start monitoring ZTE ZXR10 router (ZTE ROS) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CONFIG-COPY-MIB::copyFailCause OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 router (ZTE ROS) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.1systemAIMOS
1.3.6.1.2.1.1.1sysDescrAIMOS
Numeric OIDNameModule
1.3.6.1.2.1.1.1.1copyTableCONFIG-COPY-MIB
1.3.6.1.2.1.1.1.1.1copyEntryCONFIG-COPY-MIB
1.3.6.1.2.1.1.1.1.1.14copyFailCauseCONFIG-COPY-MIB