All MIBs › ENTERASYS-SNMP-PERSISTENCE-MIB › etsysSnmpPersistenceSave
etsysSnmpPersistenceSave
Module: ENTERASYS-SNMP-PERSISTENCE-MIB
OID (symbolic): ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceSave
OID (numeric): 1.3.6.1.4.1.5624.1.2.24.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Setting this object to save(2) will cause the current configuration that is stored in volatile memory to be written to persistent memory and become the start-up configuration.
This will also cause any configuration information that is part of another management interface's active configuration to become part of the start-up configuration.
Any configuration changes made through SNMP will become part of the start-up configuration if and when another management interface saves the current configuration to persistent storage.
Setting this object to save(2) while the value of the etsysSnmpPersistenceMode object is NOT pushButtonSave(2) MAY lead to an inconsistent value error.
Setting this object to save(2) while the value of the etsysSnmpPersistenceStatus object is savingChanges(3) leads to an inconsistent value error.
Setting this object to nop(1) always succeeds and has no effect.
On an SNMP get operation this object will return nop(1).
Management applications are advised to make use of the snmpSetSerialNo object defined in the SNMPv2-MIB to coordinate their use of this object.
What is etsysSnmpPersistenceSave?
This read-write value, when set to save(2), writes the current volatile configuration, including changes made through other management interfaces, to persistent storage as the new startup configuration; setting it to nop(1) always succeeds and does nothing, and reads always return nop(1). It's the explicit trigger an admin uses to commit buffered changes when etsysSnmpPersistenceMode is set to pushButtonSave, and attempting it while a save is already in progress returns an inconsistent-value error. An admin who just finished a batch of SNMP configuration changes under pushButtonSave mode would set this object to save(2) to commit them all to the startup config at once.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.24.1.2 snmpwalk -v2c -c public <target> ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceSave
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.24.1.2.1 snmpget -v2c -c public <target> ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceSave.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.5624.1.2.24.1.2.1 i <value>
Start monitoring Enterasys Networks switch (legacy, later Extreme Networks)/router (SNMP config persistence to flash) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceSave OID value, configure state conditions and alerts, and monitor any Enterasys Networks switch (legacy, later Extreme Networks)/router (SNMP config persistence to flash) 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.5624 | enterasys | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1 | etsysMibs | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1.2 | etsysModules | ENTERASYS-MIB-NAMES |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.5624.1.2.24 | etsysSnmpPersistenceMIB | ENTERASYS-SNMP-PERSISTENCE-MIB |
| 1.3.6.1.4.1.5624.1.2.24.1 | etsysSnmpPersistenceObjects | ENTERASYS-SNMP-PERSISTENCE-MIB |
| 1.3.6.1.4.1.5624.1.2.24.1.2 | etsysSnmpPersistenceSave | ENTERASYS-SNMP-PERSISTENCE-MIB |