AVAYA-LOAD-MIB :: avGenOpRunningState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAVAYA-LOAD-MIBavGenOpRunningState

avGenOpRunningState

Module: AVAYA-LOAD-MIB

OID (symbolic): AVAYA-LOAD-MIB::avGenOpRunningState

OID (numeric): 1.3.6.1.4.1.6889.2.6.5.1.2.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Identifies the operation to perform and the state of that operation. This field acts as both the trigger to initiate the operation (via the beginOperation) and the status field of the operation itself (i.e. waiting-ip, running-ip, etc.). It is expected that all dependent MIB objects will be set before the trigger is set to beginOperation. The operations completion is triggered by the return to the idle state.

idle(1), - Operation not in progress beginOperation(2), - Trigger by NMS to start the operation waitingIp(3), - Communication phase; waiting for response runningIp(4), - Communication phase; transferring data copyingLocal(5), - Local operation readingConfiguration(6), - Parsing / Executing configuration file executing(7) - Executing Command (such as erasing a file or reporting) blocked(8) - to be used when the Load MIB agent is unable to perform a requested operation, this could happen in CM if a firmware download job was submitted directly from the SAT. Since CM only accepts one job at a time, the Load MIB agent will be blocked until that job completes. reset(9) - to be used to request a reset only of a TN board, this capability is a existing capability in Software Update Manager that we want to support directly in the Load MIB.

What is avGenOpRunningState?

Acts as both the trigger and the status indicator for a file operation: a management system sets it to beginOperation to start the transfer, and the agent then updates it through states like waitingIp, runningIp, copyingLocal, or executing as the operation progresses, returning to idle when done. An admin polls this field to know whether an upload, download, or backup job it started is still running, blocked, or finished.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.5.1.2.1.3
snmpwalk -v2c -c public <target> AVAYA-LOAD-MIB::avGenOpRunningState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.5.1.2.1.3.1
snmpget -v2c -c public <target> AVAYA-LOAD-MIB::avGenOpRunningState.1

Set instance 1 (SNMPv2c):

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

Start monitoring Avaya communication servers and network equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVAYA-LOAD-MIB::avGenOpRunningState OID value, configure state conditions and alerts, and monitor any Avaya communication servers and network equipment 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.6889avayaAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2mibsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.6avGatewayMibsAVAYAGEN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6889.2.6.5avLoadAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1avGenOperationsAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1.2avGenOpTableAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1.2.1avGenOpEntryAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1.2.1.3avGenOpRunningStateAVAYA-LOAD-MIB