All MIBs › ACMIB › saveConfigurationReasonCode
saveConfigurationReasonCode
Module: ACMIB
OID (symbolic): ACMIB::saveConfigurationReasonCode
OID (numeric): 1.3.6.1.4.1.1751.2.18.15.10
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The result of a save configuration request. equipment-OK(1) - Save of equipment configuration completed. equipment-Fail-VersionControlInProgress(2) - Save of equipment configuration failed due to ongoing version control operation. equipment-Fail(3) - Save of equipment configuration failed. connections-OK(4) - Save of connection configuration completed. connections-Fail-VersionControlInProgress(5) - - Save of connection configuration failed due to ongoing version control operation. connections-Fail(6) - Save of connection configuration failed. routing-OK(7) - Save of routing configuration completed. routing-Fail-VersionControlInProgress(8) - - Save of routing configuration failed due to ongoing version control operation. routing-Fail(9) - Save of routing configuration failed. all-OK(10) - Saving of all configurations completed. all-Fail-VersionControlInProgress(11) - - Saving of all configurations failed due to ongoing version control operation. all-Fail(12) - Saving of all configurations failed. fileTransferFailed(13) - Saving of configurations to secondary CPU failed. fileTransferCompleted(14) - Saving of configurations to secondary CPU completed. unSupportedOption(15) - Unsupported save option received. fail-backupCpuInitializationInProgress(16) - - Save operation failed due to ongoing secondary cpu initialization. expect2ndCPURebootAfterSave(17) - - Notification to expect reboot of secondary CPU after a save operation. expect2ndCPUCardFailedOrRemoved(18) - Notification to expect trap indicating removal/failure of secondary CPU after a save operation.
What is saveConfigurationReasonCode?
This read-only integer indicates the success or failure status after a save configuration request, with separate codes for equipment configuration saves versus connection configuration saves. Engineers rely on this when they've made changes to device settings and need to know if those changes were persisted to non-volatile memory. For example, equipment-OK(1) confirms the equipment settings were saved successfully, while equipment-Fail-VersionControlInProgress(2) means a concurrent version control operation blocked the save.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.15.10 snmpwalk -v2c -c public <target> ACMIB::saveConfigurationReasonCode
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.15.10.1 snmpget -v2c -c public <target> ACMIB::saveConfigurationReasonCode.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> saveConfigurationReasonCode.1
Start monitoring Lucent/Nortel Access Concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ACMIB::saveConfigurationReasonCode OID value, configure state conditions and alerts, and monitor any Lucent/Nortel Access Concentrator (legacy) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1751 | lucent | ACMIB |
| 1.3.6.1.4.1.1751.2 | mibs | ACMIB |
| 1.3.6.1.4.1.1751.2.18 | acMIB | ACMIB |
| 1.3.6.1.4.1.1751.2.18.15 | returnCode | ACMIB |
| 1.3.6.1.4.1.1751.2.18.15.10 | saveConfigurationReasonCode | ACMIB |