All MIBs › TMS-COMMON-MIB › tmsCommonMiscSaveToNvm
tmsCommonMiscSaveToNvm
Module: TMS-COMMON-MIB
OID (symbolic): TMS-COMMON-MIB::tmsCommonMiscSaveToNvm
OID (numeric): 1.3.6.1.4.1.731.2.2.1.6.1
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
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.
What is tmsCommonMiscSaveToNvm?
Set this to save(2) to write all pending nonvolatile configuration changes to flash; because the save can be slow, batch multiple configuration changes before triggering it, and poll for saveInProgress(3) to change back to noop(1) before assuming it finished.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.731.2.2.1.6.1 snmpwalk -v2c -c public <target> TMS-COMMON-MIB::tmsCommonMiscSaveToNvm
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.731.2.2.1.6.1.1 snmpget -v2c -c public <target> TMS-COMMON-MIB::tmsCommonMiscSaveToNvm.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.731.2.2.1.6.1.1 i <value>
Start monitoring Wind River TMS-managed platform devices (shared textual conventions, no data objects) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TMS-COMMON-MIB::tmsCommonMiscSaveToNvm OID value, configure state conditions and alerts, and monitor any Wind River TMS-managed platform devices (shared textual conventions, no data objects) from a single console.
OID Breakdown
Upper-level ancestors (9 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.731 | wrs | WRS-MASTER-MIB |
| 1.3.6.1.4.1.731.2 | tms | WRS-MASTER-MIB |
| 1.3.6.1.4.1.731.2.2 | tmsGeneric | WRS-MASTER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.731.2.2.1 | tmsCommonMib | TMS-COMMON-MIB |
| 1.3.6.1.4.1.731.2.2.1.6 | tmsCommonMisc | TMS-COMMON-MIB |
| 1.3.6.1.4.1.731.2.2.1.6.1 | tmsCommonMiscSaveToNvm | TMS-COMMON-MIB |