rttMonCtrlOperState - Round Trip Time Monitor Control Operational State - CISCO-RTTMON-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

rttMonCtrlOperState

Round Trip Time Monitor Control Operational State
1.3.6.1.4.1.9.9.42.1.2.9.1.10

The RttMonOperStatus object is used to manage the 'state' of the probe that is implementing 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 either via the rttMonScheduleAdminTable or the rttMonReactAdminTable/ rttMonReactTriggerAdminTable; 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 rttMonScheduleAdminRttStartTime object with the its special value inactive(5) - this value is not settable and this conceptual RTT control row is waiting for further control via the rttMonScheduleAdminTable; This object can transition to this value via two mechanisms, first by setting this object to 'orderlyStop' or 'immediateStop', second by the rttMonCtrlOperRttLife 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 rttMonStatsCaptureTable that relate to this conceptual RTT control row are destroyed and the indices are set to 1 - if rttMonStatisticsAdminNumHourGroups is not zero, a single new rttMonStatsCaptureTable row is created - all rows in rttMonHistoryCaptureTable that relate to this RTT definition are destroyed and the indices are set to 1 - implied history used for timeout or threshold notification (see rttMonReactAdminThresholdType or rttMonReactThresholdType) is purged - rttMonCtrlOperRttLife is set to rttMonScheduleAdminRttLife - rttMonCtrlOperNumRtts is set to zero - rttMonCtrlOperTimeoutOccurred, rttMonCtrlOperOverThresholdOccurred, and rttMonCtrlOperConnectionLostOccurred are set to false; if this causes a change in the value of either of these objects, resolution notifications will not occur - the next RTT operation is controlled by the objects in the rttMonScheduleAdminTable or the rttMonReactAdminTable/rttMonReactTriggerAdminTable - if the rttMonReactTriggerOperState is 'active', it will transition to 'pending' - all rttMonReactTriggerAdminEntries pointing to this conceptual entry with their rttMonReactTriggerOperState object 'active', will transition their OperState to 'pending' - 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 rttMonCtrlOperRttLife reaching zero): - all statistics and history collection information table entries will be closed and kept - implied history used for timeout or threshold notification (see rttMonReactAdminThresholdType or rttMonReactThresholdType) is purged - rttMonCtrlOperTimeoutOccurred, rttMonCtrlOperOverThresholdOccurred, and rttMonCtrlOperConnectionLostOccurred are set to false; if this causes a change in the value of either of these objects, resolution notifications will not occur. - the next RTT request is controlled by the objects in the rttMonScheduleAdminTable - if the rttMonReactTriggerOperState is 'active', it will transition to 'pending' (this denotes that the Trigger will be ready the next time this object goes active) - all rttMonReactTriggerAdminEntries pointing to this conceptual entry with their rttMonReactTriggerOperState object 'active', will transition their OperState to 'pending' - all open connections are to be closed and cleanup. rttMonCtrlOperState 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' | | | | +----------------+--------------+--------------+-------------+ | Event causes | -> C | -> B | -> C | | Trigger State | | | see (3) | | to transition | | | | | to 'active' | | | | +----------------+--------------+--------------+-------------+ | 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) - rttMonCtrlOperState must have transitioned to 'inactive' or 'pending' before the rttMonCtrlAdminStatus can transition to 'active'. See (2). (2) - rttMonCtrlAdminStatus cannot transition to 'notInService' unless rttMonCtrlOperState has been previously forced to 'inactive' or 'pending'. (3) - when this happens the rttMonCtrlOperRttLife will not be updated with the rttMonCtrlAdminRttLife. 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.

Back to CISCO-RTTMON-MIB MIB page.

IPHost Network monitor allows you to monitor rttMonCtrlOperState on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco firewalls right now.

Easy monitoring of rttMonCtrlOperState with IPHost tools

MIBs list