Number of times a packet needed to be played
out and the jitter buffer was empty.
Parsed from file CISCO-IETF-PW-TDM-MIB.mib
Module: CISCO-IETF-PW-TDM-MIB
Number of times a packet needed to be played
out and the jitter buffer was empty.
Number of times a packet needed to be played
out and the jitter buffer was empty.
Parsed from file CISCO-IETF-PW-TDM-MIB.my.txt
Company: None
Module: CISCO-IETF-PW-TDM-MIB
Number of times a packet needed to be played
out and the jitter buffer was empty.
cpwCTDMPerf1DayIntervalJtrBfrUnderruns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times a packet needed to be played out and the jitter buffer was empty." ::= { cpwCTDMPerf1DayIntervalEntry 6 }
cpwCTDMPerf1DayIntervalJtrBfrUnderruns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of times a packet needed to be played out and the jitter buffer was empty." ::= { cpwCTDMPerf1DayIntervalEntry 6 }
Vendor: Cisco
Module: CISCO-IETF-PW-TDM-MIB
[Automatically extracted from oidview.com]
cpwCTDMPerf1DayIntervalJtrBfrUnderruns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times a packet needed to be played out and the jitter buffer was empty." ::= { cpwCTDMPerf1DayIntervalEntry 6 }
cpwCTDMPerf1DayIntervalJtrBfrUnderruns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times a packet needed to be played out and the jitter buffer was empty." ::= { cpwCTDMPerf1DayIntervalEntry 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.131.1.7.1.1 | cpwCTDMPerf1DayIntervalNumber | 0 | 0 | The number of interval, where 1 indicates current day measured period and 2 and above indicate previous days respectively |
| 1.3.6.1.4.1.9.10.131.1.7.1.2 | cpwCTDMPerf1DayIntervalValidData | 0 | 0 | This variable indicates if the data for this interval is valid. |
| 1.3.6.1.4.1.9.10.131.1.7.1.3 | cpwCTDMPerf1DayIntervalDuration | 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.7.1.4 | cpwCTDMPerf1DayIntervalMissingPkts | 0 | 0 | Number of missing packets (as detected via control word sequence number gaps). |
| 1.3.6.1.4.1.9.10.131.1.7.1.5 | cpwCTDMPerf1DayIntervalPktsReOrder | 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.7.1.7 | cpwCTDMPerf1DayIntervalMisOrderDropped | 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.7.1.8 | cpwCTDMPerf1DayIntervalMalformedPkt | 0 | 0 | Number of packets detected with unexpected size, or bad headers' stack. |
| 1.3.6.1.4.1.9.10.131.1.7.1.9 | cpwCTDMPerf1DayIntervalESs | 0 | 0 | The counter associated with the number of Error Seconds encountered. |
| 1.3.6.1.4.1.9.10.131.1.7.1.10 | cpwCTDMPerf1DayIntervalSESs | 0 | 0 | The counter associated with the number of Severely Error Seconds. |
| 1.3.6.1.4.1.9.10.131.1.7.1.11 | cpwCTDMPerf1DayIntervalUASs | 0 | 0 | The counter associated with the number of UnAvailable Seconds. When first entering the UAS state, the number of SES To UAS is adde… |
| 1.3.6.1.4.1.9.10.131.1.7.1.12 | cpwCTDMPerf1DayIntervalFC | 0 | 0 | This object represents the number of TDM failure events. A failure event begins when the LOPS failure is declared, and ends when … |