mscApsTestCauseOftermination
View at oid-info.com
This attribute indicates either the status of the test or the cause of
the test's termination:
neverStarted indicates that the test has not yet been started.
testRunning indicates that the test has been started.
stoppedByOperator indicates that the operator issued a stop
command on a test that was running.
testTimeExpired indicates that the test ran for the time specified by
the test's duration.
loopCodeSyncFailed indicates that the local end failed to
synchronize to the loopCode pattern. The local end transmits the
loopCode pattern to cause the remote end to apply a loopback, after
which the local end should receive the loopCode pattern. The exact
pattern used to request loopCode depends on the test type. This
failure indicates a high rate of transmission errors, or that the
remote end has failed to apply the loopback.
patternSyncFailed indicates that the local end failed to synchronize
to the frmPatternType test pattern, that should have been looped
back at the remote end. This failure indicates a high rate of
transmission errors or the absence of a loopback.
patternSyncLost indicates that the local end gained and then lost
synchronization to the returned frmPatternType test pattern. This
failure indicates a sudden increase in transmission errors, frame
slippage, or the removal of an existing loopback.
unknown is set when a reason to terminate other than those listed
here is encountered.
Note: Only MSA cards support recognition of the failures
loopCodeSyncFailed, patternSyncFailed and patternSyncLost.
Other cards will not terminate the test under the conditions
described by these values.
Parsed from file nortelPC-apsV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-ApsMIB
This attribute indicates either the status of the test or the cause of
the test's termination:
neverStarted indicates that the test has not yet been started.
testRunning indicates that the test has been started.
stoppedByOperator indicates that the operator issued a stop
command on a test that was running.
testTimeExpired indicates that the test ran for the time specified by
the test's duration.
loopCodeSyncFailed indicates that the local end failed to
synchronize to the loopCode pattern. The local end transmits the
loopCode pattern to cause the remote end to apply a loopback, after
which the local end should receive the loopCode pattern. The exact
pattern used to request loopCode depends on the test type. This
failure indicates a high rate of transmission errors, or that the
remote end has failed to apply the loopback.
patternSyncFailed indicates that the local end failed to synchronize
to the frmPatternType test pattern, that should have been looped
back at the remote end. This failure indicates a high rate of
transmission errors or the absence of a loopback.
patternSyncLost indicates that the local end gained and then lost
synchronization to the returned frmPatternType test pattern. This
failure indicates a sudden increase in transmission errors, frame
slippage, or the removal of an existing loopback.
unknown is set when a reason to terminate other than those listed
here is encountered.
Note: Only MSA cards support recognition of the failures
loopCodeSyncFailed, patternSyncFailed and patternSyncLost.
Other cards will not terminate the test under the conditions
described by these values.
Parsed from file Nortel-MsCarrier-MscPassport-ApsMIB.mib
Module: Nortel-MsCarrier-MscPassport-ApsMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-ApsMIB
[Automatically extracted from oidview.com]
mscApsTestCauseOfTermination OBJECT-TYPE SYNTAX INTEGER { testTimeExpired(0), stoppedByOperator(1), unknown(2), neverStarted(3), testRunning(4), hardwareReconfigured(5), loopCodeSyncFailed(6), patternSyncFailed(7), patternSyncLost(8) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values." DEFVAL { neverStarted } ::= { mscApsTestResultsEntry 3 }
mscApsTestCauseOfTermination OBJECT-TYPE SYNTAX INTEGER { testTimeExpired(0), stoppedByOperator(1), unknown(2), neverStarted(3), testRunning(4), hardwareReconfigured(5), loopCodeSyncFailed(6), patternSyncFailed(7), patternSyncLost(8) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values." DEFVAL { neverStarted } ::= { mscApsTestResultsEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.1 | mscApsTestElapsedTime | 0 | 0 | This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the ti… |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.2 | mscApsTestTimeRemaining | 0 | 0 | This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute. |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.4 | mscApsTestBitsTx | 0 | 0 | This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is l… |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.5 | mscApsTestBytesTx | 0 | 0 | This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value. |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.6 | mscApsTestFrmTx | 0 | 0 | This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum valu… |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.7 | mscApsTestBitsRx | 0 | 0 | This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum va… |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.8 | mscApsTestBytesRx | 0 | 0 | This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum v… |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.9 | mscApsTestFrmRx | 0 | 0 | This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum … |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.10 | mscApsTestErroredFrmRx | 0 | 0 | This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. F… |
| 1.3.6.1.4.1.562.36.2.1.134.2.12.1.11 | mscApsTestBitErrorRate | 0 | 0 | This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. F… |