The RttMonOperStatus object is used to manage the 'state' of the probe that is implementing this conceptual RTT control row. This status object has six defined values: reset(1) - Reset this entry; transition to 'pending'. orderlyStop(2) - Shutdown this entry at the end of the next RTT operation attempt; transition to 'inactive'. immediateStop(3) - Shutdown this entry immediately (if possible); transition to 'inactive'. pending(4) - This value is not settable and this conceptual RTT control row is waiting for further control via the teldatNsmScheduleAdminTable. This object can transition to this value via two mechanisms: first by reseting this object, and second by creating a conceptual RTT control row with the teldatNsmScheduleAdminRttStartTime object with its special value. inactive(5) - This value is not settable and this conceptual RTT control row is waiting for further control via the teldatNsmScheduleAdminTable. This object can transition to this value via two mechanisms: first by setting this object to 'orderlyStop' or 'immediateStop', second by the teldatNsmCtrlOperRttLife object reaching zero. active(6) - This value is not settable and this conceptual RTT control row is currently active. restart(7) - This value is only settable when the state is active. It clears the data of this entry and remain on active state. The probes action when this object is set to 'reset': - All rows in teldatNsmStatsCaptureTable that relate to this conceptual RTT control row (only 1 in current implementation) are destroyed. - A single new teldatNsmStatsCaptureTable row is created. - teldatNsmCtrlOperRttLife is set to teldatNsmScheduleAdminRttLife. - teldatNsmCtrlOperNumRtts is set to zero. - teldatNsmCtrlOperTimeoutOccurred, teldatNsmCtrlOperOverThresholdOccurred, and teldatNsmCtrlOperConnectionLostOccurred are set to false. - The next RTT operation is controlled by the objects in the teldatNsmScheduleAdminTable. - All open connections must be maintained. This can be used to synchronize various RTT definitions, so that the RTT requests occur simultaneously, or as simultaneously as possible. The probes action when this object transitions to 'inactive' (via setting this object to 'orderlyStop' or 'immediateStop' or by teldatNsmCtrlOperRttLife reaching zero): - All statistics and collection information table entries will be closed and kept. - teldatNsmCtrlOperTimeoutOccurred, teldatNsmCtrlOperOverThresholdOccurred, and teldatNsmCtrlOperConnectionLostOccurred are set to false. - The next RTT request is controlled by the objects in the teldatNsmScheduleAdminTable. - All open connections are to be closed and cleanup. teldatNsmCtrlOperState STATE + | A | B | C | ACTION | 'pending' | 'inactive' | 'active' | + | OperState set | noError |inconsistent- | noError | | to 'reset' | | Value | | | | -> A | | -> A | + | OperState set | noError | noError | noError | |to 'orderlyStop'| -> B | -> B | -> B | | or to | | | | |'immediateStop' | | | | + | AdminStatus | -> C | -> C | see (1) | | transitions to | | | | | 'active' & | | | | | RttStartTime is| | | | | special value | | | | | of one. | | | | + | AdminStatus | -> A | -> A | see (1) | | transitions to | | | | | 'active' & | | | | | RttStartTime is| | | | | special value | | | | | of less than | | | | | current time, | | | | | excluding one. | | | | + | AdminStatus | -> A | -> B | see (2) | | transitions to | | | | | 'notInService' | | | | + | AdminStatus | -> B | -> B | -> B | | transitions to | | | | | 'delete' | | | | + | AdminStatus is | -> C | -> C | -> C | | 'active' & the | | | see (3) | | RttStartTime | | | | | arrives | | | | + | RowAgeout | -> B | -> B | -> B | | expires | | | | + | OperRttLife | N/A | N/A | -> B | | counts down to | | | | | zero | | | | + (1) - teldatNsmCtrlOperState must have transitioned to 'inactive' or 'pending' before the teldatNsmCtrlAdminStatus can transition to 'active'. See (2). (2) - teldatNsmCtrlAdminStatus cannot transition to 'notInService' unless teldatNsmCtrlOperState has been previously forced to 'inactive' or 'pending'. (3) - When this happens the teldatNsmCtrlOperRttLife will not be updated with the teldatNsmScheduleAdminRttLife. NOTE: In order for all objects in a PDU to be set at the same time, this object can not be part of a multi-bound PDU.