ZTE-AN-SYS-MGMT-MIB :: zxAnSysConfigSaveFailedReason

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ZTE-AN-SYS-MGMT-MIB › zxAnSysConfigSaveFailedReason

zxAnSysConfigSaveFailedReason

Module: ZTE-AN-SYS-MGMT-MIB

OID (symbolic): ZTE-AN-SYS-MGMT-MIB::zxAnSysConfigSaveFailedReason

OID (numeric): 1.3.6.1.4.1.3902.1082.20.1.2.10.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The reason of saving flash operation failed. Possible values are: - noError(1): No error, saving flash successfully or no saving flash operation is excuted. - flashMediaFull(2): The save flash operation is failed because flash media is full. - createConfigFilesFailed(3): The save flash operation is failed because configuration file is created unsuccessfully. - openConfigFilesFailed(4): The save flash operation is failed because configuration file can't be opened successfully. - standbyCardCopyConfigFilesFailed(5) : The save flash operation is failed because configuration file can't be copied to the standby board. - unknown(99): The save flash operation is failed for some unknown error.

What is zxAnSysConfigSaveFailedReason?

This field reports the specific reason the most recent flash-save operation failed, such as full flash media or an inability to create the configuration file. Admins use this detailed reason code to diagnose exactly why a save failed rather than just knowing that it did, guiding the fix, such as clearing flash space. For example, a value of flashMediaFull(2) tells the admin to free up flash storage before the configuration can be saved successfully.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.1082.20.1.2.10.1.5
snmpwalk -v2c -c public <target> ZTE-AN-SYS-MGMT-MIB::zxAnSysConfigSaveFailedReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.1082.20.1.2.10.1.5.1
snmpget -v2c -c public <target> ZTE-AN-SYS-MGMT-MIB::zxAnSysConfigSaveFailedReason.1

Start monitoring ZTE Access Node (DSLAM/OLT broadband access device) (NTP-sync/syslog-destination config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZTE-AN-SYS-MGMT-MIB::zxAnSysConfigSaveFailedReason OID value, configure state conditions and alerts, and monitor any ZTE Access Node (DSLAM/OLT broadband access device) (NTP-sync/syslog-destination config status) from a single console.

OID Breakdown

Upper-level ancestors (9 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.3902zteDPI-MIB
1.3.6.1.4.1.3902.1082zxAccessNodeZTE-AN-SMI
1.3.6.1.4.1.3902.1082.20zxAnSystemZTE-AN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3902.1082.20.1zxAnSysMgmtMibZTE-AN-SYS-MGMT-MIB
1.3.6.1.4.1.3902.1082.20.1.2zxAnSysMgmtObjectsZTE-AN-SYS-MGMT-MIB
1.3.6.1.4.1.3902.1082.20.1.2.10zxAnSysConfigSaveObjectsZTE-AN-SYS-MGMT-MIB
1.3.6.1.4.1.3902.1082.20.1.2.10.1zxAnSysConfigSaveGlobalObjectsZTE-AN-SYS-MGMT-MIB
1.3.6.1.4.1.3902.1082.20.1.2.10.1.5zxAnSysConfigSaveFailedReasonZTE-AN-SYS-MGMT-MIB