All MIBs › GBNPlatformOAM-MIB › writeConfig
writeConfig
Module: GBNPlatformOAM-MIB
OID (symbolic): GBNPlatformOAM-MIB::writeConfig
OID (numeric): 1.3.6.1.4.1.13464.1.2.1.1.2.17
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: When set to 'save(2)', config file is saved to NVM (Nonvolatile Memory). NVM save operations may be slow (e.g., erasing/writing Flash device).
Consequently, all or many updates should be made before saving to NVM. Note that the SNMP set to 'save(2)' returns immediately to the caller. Gets on this object then return 'saveInProgress(3)' until the save operation completes, at which time 'noop(1)' is returned if the save operation is succeeded, otherwise 'saveFailed(4)' is returned. Consequently, a get operation always returns 'noop(1)', 'saveInProgress(3)' or 'saveFailed(4) depending on the current state and the result of the save operation.
The agent returns 'badValue' for SNMPv1 or 'inconsistentValue' for SNMPv2c/v3 for a set to 'Save(2)' while the current get state is 'saveInProgress(3)'.
Attempts to set this object to 'saveInProgress(3)' or 'saveFailed(4)' returns 'badValue' for SNMPv1 or 'wrongValue' for SNMPv2c/v3.
What is writeConfig?
This read-write object triggers saving the running configuration to NVM: setting it to save(2) starts the save (which can be slow due to flash erase/write), after which GETs return saveInProgress(3) until it completes, then noop(1) on success or saveFailed(4) on failure. An admin batches multiple configuration changes together and sets this once at the end, since the NVM write itself is comparatively slow.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13464.1.2.1.1.2.17 snmpwalk -v2c -c public <target> GBNPlatformOAM-MIB::writeConfig
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.13464.1.2.1.1.2.17.1 snmpget -v2c -c public <target> GBNPlatformOAM-MIB::writeConfig.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.13464.1.2.1.1.2.17.1 i <value>
Start monitoring Unidentified device (Greentech/GBN common OAM framework) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the GBNPlatformOAM-MIB::writeConfig OID value, configure state conditions and alerts, and monitor any Unidentified device (Greentech/GBN common OAM framework) from a single console.
OID Breakdown
Upper-level ancestors (10 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 |
| 1.3.6.1.4.1.13464 | admin | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1 | dataCom | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1.2 | gbn | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1.2.1 | gbnPlatform | ADMIN-MASTER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.13464.1.2.1.1 | gbnPlatformOAM | GBNPlatformOAM-MIB |
| 1.3.6.1.4.1.13464.1.2.1.1.2 | gbnPlatformOAMSystem | GBNPlatformOAM-MIB |
| 1.3.6.1.4.1.13464.1.2.1.1.2.17 | writeConfig | GBNPlatformOAM-MIB |