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.