|
|
|
|
Description:
|
tmsCommonMiscSaveToNvm OBJECT-TYPE
SYNTAX INTEGER {
noop(1), -- no operation
save(2), -- save all configuration parameters to NVM
saveInProgress(3) -- read-only: NVM save in progress
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When set to 'save(2)', all nonvolatile configuration
parameters are 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. Consequently, a get
operation always returns 'noop(1)' or 'saveInProgress(3)'
depending on the current state.
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)' returns
'badValue' for SNMPv1 or 'wrongValue' for SNMPv2c/v3."
|
|
Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2024 |
iso(1)
