tmnxOamPingCtlTimeOut 1.3.6.1.4.1.6527.3.1.2.11.1.3.1.21

The value of tmnxOamPingCtlTimeOut specifies the time-out value, in seconds, to be used during a test run. Timers (with duration configured using the tmnxOamPingCtlTimeOut value) are used in one of two ways during a test run. 1. Per Probe: a timer is started each time a probe is sent. If the timer expires before the probe response arrives, the probe is declared failed. This is the traditional time-out method for a sequence of probes. OR 2. Per Test: a timer is started once per test run, when the last probe of the test run is sent. ANY probe which does not have a response when the timer expires is declared failed. SROS chooses 'Per Probe' or 'Per Test' based on the tmnxOamPingCtlTestMode value. The choice is not configurable. The accepted minimum, maximum, and default values for tmnxOamPingCtlTimeOut depend on tmnxOamPingCtlTestMode, as shown in the following table. The table also shows the timer usage for the test mode. tmnxOamPingCtlTestMode Min Max Def Timer Usage ---------------------- --- --- --- ----------- 'atmPing' 1 10 5 Per Probe 'dnsPing' 1 120 5 Per Probe 'ethCfmLoopback' 1 10 5 Per Probe 'ethCfmTwoWayDelay' 1 10 5 Per Test 'ethCfmTwoWaySlm' 1 10 5 Per Test 'icmpPing' 1 10 5 Per Test 'lspPing' 1 10 5 Per Probe 'macPing' 1 10 5 Per Probe 'mfibPing' 1 100 5 Per Probe 'mtuPing' 1 10 5 Per Probe 'p2mpLspPing' 1 120 10 Per Probe 'sdpPing' 1 10 5 Per Probe 'vccvPing' 1 10 5 Per Probe 'vprnPing' 1 100 5 Per Probe otherwise ......... the value of tmnxOamPingCtlTimeOut is irrelevant