This object represents the number of TDM failure
events. A failure event begins when the LOPS failure
is declared, and ends when the failure is cleared. A
failure event that begins in one period and ends in
another period is counted only in the period in which
it begins.
Parsed from file CISCO-IETF-PW-TDM-MIB.mib
Module: CISCO-IETF-PW-TDM-MIB
This object represents the number of TDM failure
events. A failure event begins when the LOPS failure
is declared, and ends when the failure is cleared. A
failure event that begins in one period and ends in
another period is counted only in the period in which
it begins.
This object represents the number of TDM failure
events. A failure event begins when the LOPS failure
is declared, and ends when the failure is cleared. A
failure event that begins in one period and ends in
another period is counted only in the period in which
it begins.
Parsed from file CISCO-IETF-PW-TDM-MIB.my.txt
Company: None
Module: CISCO-IETF-PW-TDM-MIB
This object represents the number of TDM failure
events. A failure event begins when the LOPS failure
is declared, and ends when the failure is cleared. A
failure event that begins in one period and ends in
another period is counted only in the period in which
it begins.
cpwCTDMPerfIntervalFC OBJECT-TYPE SYNTAX PerfIntervalCount MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the number of TDM failure events. A failure event begins when the LOPS failure is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins." ::= { cpwCTDMPerfIntervalEntry 12 }
cpwCTDMPerfIntervalFC OBJECT-TYPE SYNTAX PerfIntervalCount ACCESS read-only STATUS mandatory DESCRIPTION "This object represents the number of TDM failure events. A failure event begins when the LOPS failure is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins." ::= { cpwCTDMPerfIntervalEntry 12 }
Vendor: Cisco
Module: CISCO-IETF-PW-TDM-MIB
[Automatically extracted from oidview.com]
cpwCTDMPerfIntervalFC OBJECT-TYPE SYNTAX PerfIntervalCount MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the number of TDM failure events. A failure event begins when the LOPS failure is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins." ::= { cpwCTDMPerfIntervalEntry 12 }
cpwCTDMPerfIntervalFC OBJECT-TYPE SYNTAX PerfIntervalCount MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the number of TDM failure events. A failure event begins when the LOPS failure is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins." ::= { cpwCTDMPerfIntervalEntry 12 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.131.1.6.1.1 | cpwCTDMPerfIntervalNumber | 0 | 0 | This object indicates a number (normally between 1 and 96 to cover a 24 hour period) which identifies the interval for which the … |
| 1.3.6.1.4.1.9.10.131.1.6.1.2 | cpwCTDMPerfIntervalValidData | 0 | 0 | This variable indicates if the data for this interval is valid. |
| 1.3.6.1.4.1.9.10.131.1.6.1.3 | cpwCTDMPerfIntervalDuration | 0 | 0 | The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock, may cause the interval to be gre… |
| 1.3.6.1.4.1.9.10.131.1.6.1.4 | cpwCTDMPerfIntervalMissingPkts | 0 | 0 | Number of missing packets (as detected via control word sequence number gaps). |
| 1.3.6.1.4.1.9.10.131.1.6.1.5 | cpwCTDMPerfIntervalPktsReOrder | 0 | 0 | Number of packets detected out of sequence (via control word sequence number), but successfully re-ordered. |
| 1.3.6.1.4.1.9.10.131.1.6.1.6 | cpwCTDMPerfIntervalJtrBfrUnderruns | 0 | 0 | Number of times a packet needed to be played out and the jitter buffer was empty. |
| 1.3.6.1.4.1.9.10.131.1.6.1.7 | cpwCTDMPerfIntervalMisOrderDropped | 0 | 0 | Number of packets detected out of order(via control word sequence numbers), and could not be re-ordered, or could not fit in the … |
| 1.3.6.1.4.1.9.10.131.1.6.1.8 | cpwCTDMPerfIntervalMalformedPkt | 0 | 0 | Number of packets detected with unexpected size, or bad headers' stack |
| 1.3.6.1.4.1.9.10.131.1.6.1.9 | cpwCTDMPerfIntervalESs | 0 | 0 | The counter associated with the number of Error Seconds encountered. |
| 1.3.6.1.4.1.9.10.131.1.6.1.10 | cpwCTDMPerfIntervalSESs | 0 | 0 | The counter associated with the number of Severely Error Seconds encountered. |
| 1.3.6.1.4.1.9.10.131.1.6.1.11 | cpwCTDMPerfIntervalUASs | 0 | 0 | The counter associated with the number of Unavailable Seconds encountered. |