writeConfig

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.

MIB

QTECH-GBNPlatformOAM-MIB

OID

.1.3.6.1.4.1.27514.1.2.1.1.2.17

Type

scalar

Access

readwrite

Status

current

Parent

gbnPlatformOAMSystem