ENTERASYS-SNMP-PERSISTENCE-MIB :: etsysSnmpPersistenceMode

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › ENTERASYS-SNMP-PERSISTENCE-MIB › etsysSnmpPersistenceMode

etsysSnmpPersistenceMode

Module: ENTERASYS-SNMP-PERSISTENCE-MIB

OID (symbolic): ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceMode

OID (numeric): 1.3.6.1.4.1.5624.1.2.24.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Setting this object to snmpNormalSave(1) will cause this device to exhibit what could be considered normal SNMP behavior, that is each SNMP set of a persistent object will be saved to persistent storage as part of the set operation.

Setting this object to pushButtonSave(2) will cause SNMP sets of persistent objects to be buffered in volatile memory until the configuration is explicitly saved to persistent memory, either through the CLI or by setting the etsysSnmpPersistenceWrite object to save(2).

Setting this object to timeDelayedSave(3) will cause SNMP sets of persistent objects to be buffered in volatile memory until certain implementation dependent time conditions are met. Once these conditions are met the configuration is saved to persistent memory.

Setting this object to a mode that is not supported on that particular implementation leads to an inconsistent value error.

On an SNMP get operation this object will return the current persistent storage mode of operation.

What is etsysSnmpPersistenceMode?

This read-write value selects how SNMP configuration changes get committed to persistent storage: snmpNormalSave(1) saves each SNMP set immediately, pushButtonSave(2) buffers changes in volatile memory until an explicit save via CLI or the companion save object, and timeDelayedSave(3) buffers changes until an implementation-defined time condition triggers a save. It lets an admin control the risk/performance trade-off between immediate persistence and batched, deliberate saves. An admin making a series of related SNMP configuration changes who wants them all committed together, or rolled back together if something goes wrong, would set this to pushButtonSave(2) rather than the default immediate-save behavior.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.24.1.1
snmpwalk -v2c -c public <target> ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.24.1.1.1
snmpget -v2c -c public <target> ENTERASYS-SNMP-PERSISTENCE-MIB::etsysSnmpPersistenceMode.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.5624.1.2.24.1.1.1 i <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> etsysSnmpPersistenceMode.1

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::etsysSnmpPersistenceMode 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.5624enterasysENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1etsysMibsENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1.2etsysModulesENTERASYS-MIB-NAMES
Numeric OIDNameModule
1.3.6.1.4.1.5624.1.2.24etsysSnmpPersistenceMIBENTERASYS-SNMP-PERSISTENCE-MIB
1.3.6.1.4.1.5624.1.2.24.1etsysSnmpPersistenceObjectsENTERASYS-SNMP-PERSISTENCE-MIB
1.3.6.1.4.1.5624.1.2.24.1.1etsysSnmpPersistenceModeENTERASYS-SNMP-PERSISTENCE-MIB