NETWORK-ALCHEMY-CONFIG-MIB :: configCommit

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NETWORK-ALCHEMY-CONFIG-MIB › configCommit

configCommit

Module: NETWORK-ALCHEMY-CONFIG-MIB

OID (symbolic): NETWORK-ALCHEMY-CONFIG-MIB::configCommit

OID (numeric): 1.3.6.1.4.1.2972.2.5.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: When an SNMP management station sets (changes) a configuration parameter via an SNMP set operation, the SNMP agent code will set a dirt bit. The management station can then submit a set operation on this configCommit variable to write the configuration to flash, thereby committing the change.

Performing a read on this variable will return the value of the config dirty bit.

What is configCommit?

Setting this object to yes(1) tells the device to write its current in-memory configuration out to flash storage, permanently committing whatever changes triggered the configDirtyBit; reading it instead just returns the current dirty-bit state. An administrator uses this as the 'save config' action after making a batch of SNMP set changes, rather than having each individual change auto-persist. For example, after adjusting several parameters via SNMP, setting configCommit to yes(1) makes those edits survive a subsequent reboot.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2972.2.5.2
snmpwalk -v2c -c public <target> NETWORK-ALCHEMY-CONFIG-MIB::configCommit

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2972.2.5.2.1
snmpget -v2c -c public <target> NETWORK-ALCHEMY-CONFIG-MIB::configCommit.1

Set instance 1 (SNMPv2c):

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

Start monitoring Network Alchemy (Nokia) Crypto Cluster VPN equipment (configuration commit) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NETWORK-ALCHEMY-CONFIG-MIB::configCommit OID value, configure state conditions and alerts, and monitor any Network Alchemy (Nokia) Crypto Cluster VPN equipment (configuration commit) 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.2972networkAlchemyNETAL-SMI
1.3.6.1.4.1.2972.2netalMgmtNETAL-SMI
1.3.6.1.4.1.2972.2.5configNETAL-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2972.2.5.2configCommitNETWORK-ALCHEMY-CONFIG-MIB