AVIAT-SWMANAGEMENT-MIB :: aviatSmLoadControl

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › AVIAT-SWMANAGEMENT-MIB › aviatSmLoadControl

aviatSmLoadControl

Module: AVIAT-SWMANAGEMENT-MIB

OID (symbolic): AVIAT-SWMANAGEMENT-MIB::aviatSmLoadControl

OID (numeric): 1.3.6.1.4.1.2509.9.11.2.2.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The software loading process may be controlled using this object.

Setting the value load(1) will begin transfer of the specified file from the external URI to the unit. If the file is a manifest, this will initiate transfer of all referenced files. When this procedure has completed, aviatSmLoadStatus will indicate loadOk(6) for success, or loadError(10) for failure.

An unresolvable incompatibility error is indicated by compatibilityError(13) and should be followed by an abort(0).

A successful software (loadOk) load may be activated by setting the value to activate(2). If the delayed/timed activation objects are disabled this will have an immediate effect, otherwise the activation will take place as scheduled. A successful activation will result in an aviatSmLoadStatus value of activateOk(7). An error will be indicated by the value activateError(11).

If the value is idle(7) and no software load process has been initiated since the last successful activation, the inactive software can be re-activated by setting the value to rollback(4). Success is indicated in aviatSmLoadStatus by rollbackOk(8) and failure by rollbackError(12).

Setting the value to loadAndActivate(3) will begin software transfer. A successful transfer will be followed by software activation which is controlled by the delayed/timed activation objects. Success will be indicated in aviatSmLoadStatus by activateOk(7). A pending scheduled activation is indicated by waitingToActivate(13).

What is aviatSmLoadControl?

This is a writable control that drives the software loading workflow: load(1) transfers the specified file (or all files referenced by a manifest) from the configured URI, activate(2) activates a successfully loaded image, loadAndActivate(3) does both in sequence, rollback(4) reactivates the previous inactive image, and abort(0)/forceLoad(5) handle cancellation and forced loads. Progress and outcome of each step are reflected in aviatSmLoadStatus.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2509.9.11.2.2.1
snmpwalk -v2c -c public <target> AVIAT-SWMANAGEMENT-MIB::aviatSmLoadControl

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2509.9.11.2.2.1.1
snmpget -v2c -c public <target> AVIAT-SWMANAGEMENT-MIB::aviatSmLoadControl.1

Set instance 1 (SNMPv2c):

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

Start monitoring Aviat Networks microwave radio links (point-to-point backhaul) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVIAT-SWMANAGEMENT-MIB::aviatSmLoadControl OID value, configure state conditions and alerts, and monitor any Aviat Networks microwave radio links (point-to-point backhaul) from a single console.

OID Breakdown

Upper-level ancestors (8 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.2509dmcSTXN-GLOBALREGISTER-MIB
1.3.6.1.4.1.2509.9aviatModulesSTXN-GLOBALREGISTER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2509.9.11aviatSwManagementModuleAVIAT-SWMANAGEMENT-MIB
1.3.6.1.4.1.2509.9.11.2aviatSwManagementMIBObjectsAVIAT-SWMANAGEMENT-MIB
1.3.6.1.4.1.2509.9.11.2.2aviatSwLoadObjectsAVIAT-SWMANAGEMENT-MIB
1.3.6.1.4.1.2509.9.11.2.2.1aviatSmLoadControlAVIAT-SWMANAGEMENT-MIB