NETWORK-ALCHEMY-CONFIG-MIB :: configDirtyBit

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

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

configDirtyBit

Module: NETWORK-ALCHEMY-CONFIG-MIB

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

OID (numeric): 1.3.6.1.4.1.2972.2.5.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Says whether the configuration has been changed via a set on any of the writable SNMP variables.

What is configDirtyBit?

This object reports whether the device's running configuration has been changed via an SNMP set operation since it was last saved to permanent storage, returning yes(1) if there are unsaved changes. An administrator polls this to know whether a reboot would lose recent configuration edits before they're committed to flash. For example, seeing configDirtyBit return yes(1) after adjusting several SNMP-writable parameters is a reminder to commit those changes before power-cycling the unit.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2972.2.5.1
snmpwalk -v2c -c public <target> NETWORK-ALCHEMY-CONFIG-MIB::configDirtyBit

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2972.2.5.1.1
snmpget -v2c -c public <target> NETWORK-ALCHEMY-CONFIG-MIB::configDirtyBit.1

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::configDirtyBit OID value, configure state conditions and alerts, and monitor any Network Alchemy (Nokia) Crypto Cluster VPN equipment (configuration commit) from a single console.

How to Use in IPNetwork Monitor

Select a Network Alchemy (Nokia) Crypto Cluster VPN equipment (configuration commit) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type configDirtyBit into the Find box to locate it in the OID tree, then select it and click OK. Says whether the configuration has been changed via a set on any of the writable SNMP variables. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'no', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

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.1configDirtyBitNETWORK-ALCHEMY-CONFIG-MIB