DISMAN-SCRIPT-MIB :: smScriptOperStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DISMAN-SCRIPT-MIB › smScriptOperStatus

smScriptOperStatus

Module: DISMAN-SCRIPT-MIB

OID (symbolic): DISMAN-SCRIPT-MIB::smScriptOperStatus

OID (numeric): 1.3.6.1.2.1.64.1.3.1.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The actual status of the script in the runtime system. The value of this object is only meaningful when the value of the smScriptRowStatus object is `active'.

The smScriptOperStatus object may have the following values:

- `enabled' indicates that the script is available and can be started by a launch table entry.

- `disabled' indicates that the script can not be used.

- `editing' indicates that the script can be modified in the smCodeTable.

- `retrieving' indicates that the script is currently being loaded from non-volatile storage or a remote system.

- `compiling' indicates that the script is currently being compiled by the runtime system.

- `noSuchScript' indicates that the script does not exist at the smScriptSource.

- `accessDenied' indicates that the script can not be loaded from the smScriptSource due to a lack of permissions.

- `wrongLanguage' indicates that the script can not be loaded from the smScriptSource because of a language mismatch.

- `wrongVersion' indicates that the script can not be loaded from the smScriptSource because of a language version mismatch.

- `compilationFailed' indicates that the compilation failed.

- `noResourcesLeft' indicates that the runtime system does not have enough resources to load the script.

- `unknownProtocol' indicates that the script could not be loaded from the smScriptSource because the requested protocol is not supported.

- `protocolFailure' indicates that the script could not be loaded from the smScriptSource because of a protocol failure.

- `genericError' indicates that the script could not be

loaded due to an error condition not listed above.

The `retrieving' and `compiling' states are transient states which will either lead to one of the error states or the `enabled' state. The `disabled' and `editing' states are administrative states which are only reached by explicit management operations.

All launch table entries that refer to this script table entry shall have an smLaunchOperStatus value of `disabled' when the value of this object is not `enabled'.

What is smScriptOperStatus?

Reports the script's real runtime state, such as enabled (ready to run), compiling, or one of several specific error states like wrongLanguage, accessDenied, or compilationFailed; an admin checks this after enabling a script to confirm it actually loaded rather than getting stuck in an error condition.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.64.1.3.1.1.7
snmpwalk -v2c -c public <target> DISMAN-SCRIPT-MIB::smScriptOperStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.64.1.3.1.1.7.1
snmpget -v2c -c public <target> DISMAN-SCRIPT-MIB::smScriptOperStatus.1

Start monitoring SNMP agent supporting DISMAN script delegation (vendor-neutral) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DISMAN-SCRIPT-MIB::smScriptOperStatus OID value, configure state conditions and alerts, and monitor any SNMP agent supporting DISMAN script delegation (vendor-neutral) from a single console.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.64scriptMIBDISMAN-SCRIPT-MIB
1.3.6.1.2.1.64.1smObjectsDISMAN-SCRIPT-MIB
1.3.6.1.2.1.64.1.3smScriptObjectsDISMAN-SCRIPT-MIB
1.3.6.1.2.1.64.1.3.1smScriptTableDISMAN-SCRIPT-MIB
1.3.6.1.2.1.64.1.3.1.1smScriptEntryDISMAN-SCRIPT-MIB
1.3.6.1.2.1.64.1.3.1.1.7smScriptOperStatusDISMAN-SCRIPT-MIB