All MIBs › OPS-MIB › iOpsIADSaveConfiguration
iOpsIADSaveConfiguration
Module: OPS-MIB
OID (symbolic): OPS-MIB::iOpsIADSaveConfiguration
OID (numeric): 1.3.6.1.3.1.1.1.1.19
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Save the downloaded configuration file, but continue to use the currently running configuration file or start using the newly downloaded configuration file.
For IADs that can contain multiple configuration files, either option can be used.
For IADs that can only contain one configuration file, only the 'saveAndReconfigure' option can be used.
1) When the 'none' option is specified.
2) When the 'save' option is specified, the IAD will continue to use the currently running configuration file. In order for the IAD to use the newly downloaded configuration file, the network manager should set the 'iOpsIADConfigFileName' object-type with the newly downloaded configuration file name, and then set the 'iOpsIADReConfigIAD' object-type to the value 'reConfig(2)'.
3) When 'saveAndReconfigure' is specified, the IAD will immediately start using the new configuration file if:
- The file transfer successfully completed, AND - The file is not corrupt
The SNMP Agent must update the 'iOpsIADConfigFileName' object-type with the 'iOpsIADConfigUpgradeFileName' object-type before using the newly downloaded configuration file.
When initiating a download, the attributes of this object and the attributes of the 'iOpsIADUpDownloadConfiguration'
object-type must be included in the same SNMP SET PDU message.
This is an action attribute and it is meaningless to attempt to read this value.
What is iOpsIADSaveConfiguration?
This chooses what happens after a configuration file transfer completes: none(1), save(2) which keeps the currently running config and requires a later iOpsIADReConfigIAD to switch over, or saveAndReconfigure(3) which switches immediately if the file transferred cleanly and isn't corrupt. It must be set together with iOpsIADUpDownloadConfiguration, and reading it back is meaningless since it is an action attribute.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.3.1.1.1.1.19 snmpwalk -v2c -c public <target> OPS-MIB::iOpsIADSaveConfiguration
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.3.1.1.1.1.19.1 snmpget -v2c -c public <target> OPS-MIB::iOpsIADSaveConfiguration.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.3.1.1.1.1.19.1 i <value>
Start monitoring ANDA Networks next-generation customer premises equipment (NG-CPE) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the OPS-MIB::iOpsIADSaveConfiguration OID value, configure state conditions and alerts, and monitor any ANDA Networks next-generation customer premises equipment (NG-CPE) from a single console.
OID Breakdown
Upper-level ancestors (8 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.3 | experimental | APERTUS-NPG-MIB |
| 1.3.6.1.3.1 | clns | CLNS-MIB |
| 1.3.6.1.3.1.1 | clnp | CLNS-MIB |
| 1.3.6.1.3.1.1.1 | clnpForwarding | CLNS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.3.1.1.1.1 | iOpsIADConfig | OPS-MIB |
| 1.3.6.1.3.1.1.1.1.19 | iOpsIADSaveConfiguration | OPS-MIB |