PW-TDM-MIB

All MIBs › PW-TDM-MIB

Organization: Pseudo-Wire Emulation Edge-to-Edge (PWE3) Working Group

Last Updated: 2009-06-15

Category: Network Interfaces, Pseudowire

Description: Defines managed objects for managing pseudowire encapsulation of TDM circuits (T1, E1, T3, E3, NxDS0) over packet-switched networks.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring PW-TDM-MIB with a free 30-day trial of IPNetwork Monitor.

What Is PW-TDM-MIB?

PW-TDM-MIB is an IETF PWE3 MIB (RFC 5601 family) for managing pseudo-wire emulation of TDM circuits -- T1, E1, T3, E3, and NxDS0 -- carried over a packet-switched network. It belongs to the MPLS/PWE3 circuit-emulation standards area and exposes per-pseudo-wire TDM-specific configuration (data rate) alongside performance-monitoring data organized into current and historical 15-minute/24-hour interval buckets. Its primary monitoring value is tracking the operational health of emulated TDM circuits, including configuration error conditions (pwTDMConfigError), elapsed time in the current statistics interval, and error-seconds counts, which together indicate signal quality and service-affecting faults on the emulated leased line. It explicitly supplements the PW-STD-MIB, which supplies the generic pseudo-wire structures, associations, and cross-references that this TDM-specific module extends with rate and error-interval detail. It is typically deployed on edge routers or TDM circuit-emulation gateways that convert legacy T1/E1/T3/E3 leased-line traffic into packets for transport over an MPLS or IP core. Engineers can download the PW-TDM-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PW-TDM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

MPLS/PSN provider-edge router
TDM circuit-emulation gateway
vendor-neutral IETF standards-based MIB, not tied to a specific manufacturer

Monitoring Examples

An administrator would poll pwTDMTable/pwTDMEntry, keyed by pwTDMIfIndex, to read pwTDMRate and confirm the pseudo-wire is emulating the expected T1/E1/T3 line rate, and check pwTDMConfigError for mismatches between the configured PW parameters and the underlying TDM interface. Watching pwTDMValidIntervals together with pwTDMLastEsTimeStamp reveals whether errored-seconds history is being collected correctly across the rolling performance-monitoring windows, while a rising error-seconds count during pwTDMTimeElapsed would flag jitter buffer underruns or packet loss degrading the emulated circuit. pwTDMNotifications would be used to receive traps when these error conditions cross configured thresholds.

What Can Be Monitored

TDM pseudo-wire emulated line rate
pseudo-wire configuration errors
errored seconds / performance interval statistics
valid 15-min and 24-hour interval counts
last errored-second timestamp

Imported Objects

From IF-MIB

InterfaceIndexOrZero

From PerfHist-TC-MIB

PerfCurrentCount
PerfIntervalCount

From PW-STD-MIB

pwIndex

OBJECT-TYPE

From PW-TC-STD-MIB

PwCfgIndexOrzero

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

RowStatus
StorageType
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using pwTDMPerf1DayIntervalMissingPkts OID:

Select an MPLS/PSN provider-edge router, TDM circuit-emulation gateway, vendor-neutral IETF MIB (RFC 5604) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type pwTDMPerf1DayIntervalMissingPkts into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the number of missing packets (as detected via control word sequence number gaps). On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
PWC pwGenTDMCfgIndex	1.3.6.1.2.1.186.1.1.1.3	PwCfgIndexOrzero	read-write	Index to the generic parameters in the TDM configuration table that appears in this MIB module. It is likely that multiple TDM PWs of the same characteristic will share a single TDM Cfg entry.
PWC pwRelTDMCfgIndex	1.3.6.1.2.1.186.1.1.1.4	PwCfgIndexOrzero	read-write	Index to the relevant TDM configuration table entry that appears in one of the related MIB modules such as TDMoIP or CESoPSN. It is likely that multiple TDM PWs of the same characteristic will share a single configuration entry of the relevant type. The value 0 implies no entry in other related MIBs.
U32 pwTDMCfgAlarmThreshold	1.3.6.1.2.1.186.1.3.1.15	Unsigned32	read-create	Alarms are only reported when the defect state persists for the length of time specified by this object. Object MAY be changed only when the related PW is defined as not active.
I32 pwTDMCfgAvePktLossTimeWindow	1.3.6.1.2.1.186.1.3.1.13	Integer32	read-create	The length of time over which the average packet loss rate should be computed to detect excessive packet loss rate. Object MAY be changed only when the related PW is defined as not active.
U32 pwTDMCfgClearAlarmThreshold	1.3.6.1.2.1.186.1.3.1.16	Unsigned32	read-create	Alarm MUST be cleared after the corresponding defect is undetected for the amount of time specified by this object. Object MAY be changed only when the related PW is defined as not active.
U32 pwTDMCfgConsecMissPktsOutSynch	1.3.6.1.2.1.186.1.3.1.10	Unsigned32	read-create	The number of consecutive missing packets that are required to enter the LOPS. Object MAY be changed only when the related PW is defined as not active.
U32 pwTDMCfgConsecPktsInSynch	1.3.6.1.2.1.186.1.3.1.9	Unsigned32	read-create	The number of consecutive packets with sequential sequence numbers that are required to exit the LOPS. Object MAY be changed only when the related PW is defined as not active.
pwTDMCfgEntry	1.3.6.1.2.1.186.1.3.1		not-accessible	These parameters define the characteristics of a TDM PW. They are grouped here to ease NMS burden. Once an entry is created here it may be re-used by many PWs. Unless otherwise specified, all objects in this table MUST NOT be changed after row activation (see [PWMIB]).
U32 pwTDMCfgExcessivePktLossThreshold	1.3.6.1.2.1.186.1.3.1.14	Unsigned32	read-create	Excessive packet loss rate is detected by computing the average packet-loss rate over a pwTDMCfgAvePktLossTimeWindow amount of time and comparing it with this threshold value. The rate is expressed in percentage. Object MAY be changed only when the related PW is defined as not active.
PWT pwTDMCfgIndex	1.3.6.1.2.1.186.1.3.1.1	PwTDMCfgIndex	not-accessible	Index to an entry in this table. When an NMS creates a new entry/row in this table, it best makes use of the value of the pwTDMCfgIndexNext object in order to find a free or available index value.
U32 pwTDMCfgIndexNext	1.3.6.1.2.1.186.1.2	Unsigned32	read-only	This object contains the value to be used for pwTDMCfgIndex when creating entries in the pwTDMCfgTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwTDMCfgIndexNext for a new entry in the pwTDMCfgTable, the manager issues a management protocol retrieval operation. The agent will determine through its local policy when this index value will be made available for reuse.
U32 pwTDMCfgJtrBfrDepth	1.3.6.1.2.1.186.1.3.1.7	Unsigned32	read-create	The size of this buffer SHOULD be locally configured to allow accommodation to the PSN-specific packet delay variation. If configured to a value not supported by the implementation, the agent MUST return an error code 'jtrBfrDepth' in 'pwTDMConfigError'. NOTE: jitter buffers are a limited resource to be managed. The actual size should be at least twice as big as the value of pwTDMCfgJtrBfrDepth.
U32 pwTDMCfgMissingPktsToSes	1.3.6.1.2.1.186.1.3.1.17	Unsigned32	read-create	Percent of missing packets detected (consecutive or not) within a 1-second window to cause a Severely Error Second (SES) to be counted. Object MAY be changed only when the related PW is defined as not active.
STR pwTDMCfgName	1.3.6.1.2.1.186.1.3.1.21	SnmpAdminString	read-create	A descriptive string, preferably a unique name, to an entry in this table. Object MAY be changed at any time.
U32 pwTDMCfgPayloadSize	1.3.6.1.2.1.186.1.3.1.4	Unsigned32	read-create	The value of this object indicates the PayLoad Size (in bytes) to be defined during the PW setUp. Upon TX, implementation must be capable of carrying that amount of bytes. Upon RX, when the Low Entry Networking (LEN) field is set to 0, the payload of packet MUST assume this size, and if the actual packet size is inconsistent with this length, the packet MUST be considered to be malformed.
INT pwTDMCfgPayloadSuppression	1.3.6.1.2.1.186.1.3.1.8	INTEGER	read-create	Selecting 'enable' means: Payload suppression is allowed. Payload MAY be omitted in order to conserve bandwidth. Selecting 'disable' means: No suppression under any condition. Object MAY be changed at any time.
U32 pwTDMCfgPktFiller	1.3.6.1.2.1.186.1.3.1.20	Unsigned32	read-create	Filler byte pattern played out on the TDM interface if pwTDMCfgPktReplacePolicy was set to filler(3). Object MAY be changed only when the related PW is defined as not active.
T/F pwTDMCfgPktReorder	1.3.6.1.2.1.186.1.3.1.5	TruthValue	read-create	If set to True: as CE-bound packets are queued in the jitter buffer, out of order packets are re-ordered. The maximum sequence number differential (i.e., the range in which re-sequencing can occur) is dependant on the depth of the jitter buffer. See pwTDMCfgJtrBfrDepth. NOTE: Some implementations may not support this feature. The agent should then reject a SET request for true.
INT pwTDMCfgPktReplacePolicy	1.3.6.1.2.1.186.1.3.1.12	INTEGER	read-create	This parameter determines the value to be played when CE bound packets over/underflow the jitter buffer, or are missing for any reason. This byte pattern is sent (played) on the TDM line. Selecting implementationSpecific(2) implies an agent-specific algorithm. Selecting filler(3) requires the setting of pwTDMCfgPktFiller. Object MAY be changed only when the related PW is defined as not active.
ROW pwTDMCfgRowStatus	1.3.6.1.2.1.186.1.3.1.2	RowStatus	read-create	Object used for creating, modifying, and deleting a row from this table. The following objects cannot be modified if the entry is in use and the status is active: pwTDMCfgPayloadSize, pwTDMCfgRtpHdrUsed, pwTDMCfgJtrBfrDepth, and pwTDMCfgPayloadSuppression. The row cannot be deleted if the entry is in use.
T/F pwTDMCfgRtpHdrUsed	1.3.6.1.2.1.186.1.3.1.6	TruthValue	read-create	If set to False: an RTP header is not pre-pended to the TDM packet.
U32 pwTDMCfgSetUp2SynchTimeOut	1.3.6.1.2.1.186.1.3.1.11	Unsigned32	read-create	The amount of time the host should wait before declaring the pseudowire in a down state, if the number of consecutive TDM packets that have been received after changing the administrative status to up and after finalization of signaling (if supported) between the two PEs is smaller than pwTDMCfgConsecPktsInSynch. Once the PW has OperStatus of 'up', this parameter is no longer valid. This parameter is defined to ensure that the host does not prematurely inform failure of the PW. In particular, PW 'down' notifications should not be sent before expiration of this timer. This parameter is valid only after administrative changes of the status of the PW. If the PW fails due to network impairments, a 'down' notification should be sent. Object MAY be changed only when the related PW is defined as not active.
STO pwTDMCfgStorageType	1.3.6.1.2.1.186.1.3.1.19	StorageType	read-create	This variable indicates the storage type for this row. Conceptual rows having the value permanent(4) must allow write-access to all columnar objects.
pwTDMCfgTable	1.3.6.1.2.1.186.1.3		not-accessible	This table contains a set of parameters that may be referenced by one or more TDM PWs in pwTDMTable.
INT pwTDMCfgTimestampMode	1.3.6.1.2.1.186.1.3.1.18	INTEGER	read-create	Timestamp generation MAY be used in one of the following modes: 1. Absolute mode: The PSN-bound IWF sets timestamps using the clock recovered from the incoming TDM attachment circuit. As a consequence, the timestamps are closely correlated with the sequence numbers. All TDM implementations that support usage of the RTP header MUST support this mode. 2. Differential mode: Both IWFs have access to a common high- quality timing source, and this source is used for timestamp generation. Support of this mode is OPTIONAL. Object MAY be changed only when the related PW is defined as not active.
pwTDMCompliances	1.3.6.1.2.1.186.2.1
BIT pwTDMConfigError	1.3.6.1.2.1.186.1.1.1.5	Bits	read-only	Any of the bits are set if the local configuration is not compatible with the peer configuration as available from the various parameters options. Setting is done based on signaling, or else value (0) will be set. -tdmTypeIncompatible bit is set if the local configuration is not carrying the same TDM type as the peer configuration. -peerRtpIncompatible bit is set if the local configuration is configured to send RTP packets for this PW, and the remote is not capable of accepting RTP packets. -peerPayloadSizeIncompatible bit is set if the local configuration is not carrying the same Payload Size as the peer configuration.
pwTDMConformance	1.3.6.1.2.1.186.2
pwTDMEntry	1.3.6.1.2.1.186.1.1.1		not-accessible	This table is indexed by the same index that was created for the associated entry in the PW Table (in the PW-STD-MIB). - The PwIndex. An entry is created in this table by the agent for every entry in the pwTable with a pwType equal to one of the following: e1Satop(17), t1Satop(18), e3Satop(19), t3Satop(20), basicCesPsn(21), basicTdmIp(22), tdmCasCesPsn(23), or tdmCasTdmIp(24). Unless otherwise specified, all writeable objects in this table MUST NOT be changed after row activation in the generic pwTable (see [PWMIB]) and values must persist after reboot.
pwTDMGroup	1.3.6.1.2.1.186.2.2.1			Collection of objects for basic TDM PW config and status.
pwTDMGroups	1.3.6.1.2.1.186.2.2
NUM pwTDMIfIndex	1.3.6.1.2.1.186.1.1.1.2	InterfaceIndexOrZero	read-write	This is a unique index within the ifTable. It represents the interface index of the full link or the interface index for the bundle holding the group of time slots to be transmitted via this PW connection. A value of zero indicates an interface index that has yet to be determined. Once set, if the TDM ifIndex is (for some reason) later removed, the agent SHOULD delete the associated PW rows (e.g., this pwTDMTable entry). If the agent does not delete the rows, the agent MUST set this object to zero.
TIM pwTDMLastEsTimeStamp	1.3.6.1.2.1.186.1.1.1.11	TimeStamp	read-only	The value of sysUpTime at the most recent occasion at which the TDM PW entered the ES or SES state.
pwTDMMIB	1.3.6.1.2.1.186			This MIB contains managed object definitions for encapsulating TDM (T1,E1, T3, E3, NxDS0) as pseudo-wires over packet-switching networks (PSN). This MIB supplements the PW-STD-MIB as in: Zelig, D., Nadeau, T. 'Pseudowire (PW) Management Information Base'. The PW-STD-MIB contains structures and MIB associations generic to pseudowire (PW) emulation. PW-specific MIBs (such as this) contain config and stats for specific PW types. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5604; see the RFC itself for full legal notices.
pwTDMModuleCompliance	1.3.6.1.2.1.186.2.1.1			The compliance statement for agent that support TDM PW over PSN operation.
pwTDMNotifications	1.3.6.1.2.1.186.0
pwTDMObjects	1.3.6.1.2.1.186.1
U32 pwTDMPerf1DayIntervalDuration	1.3.6.1.2.1.186.1.7.1.3	Unsigned32	read-only	The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
pwTDMPerf1DayIntervalEntry	1.3.6.1.2.1.186.1.7.1		not-accessible	An entry is created in this table by the agent for every entry in the pwTDMTable table.
C32 pwTDMPerf1DayIntervalESs	1.3.6.1.2.1.186.1.7.1.9	Counter32	read-only	The counter associated with the number of Error Seconds encountered.
C32 pwTDMPerf1DayIntervalFC	1.3.6.1.2.1.186.1.7.1.12	Counter32	read-only	TDM Failure Counts (FC-TDM). The number of TDM failure events. A failure event begins when the LOPS failure is declared, and it ends when the failure is cleared.
pwTDMPerf1DayIntervalGroup	1.3.6.1.2.1.186.2.2.4			Collection of Daily statistics objects for TDM PWs.
C32 pwTDMPerf1DayIntervalJtrBfrUnderruns	1.3.6.1.2.1.186.1.7.1.6	Counter32	read-only	Number of times a packet needed to be played out and the jitter buffer was empty.
C32 pwTDMPerf1DayIntervalMalformedPkt	1.3.6.1.2.1.186.1.7.1.8	Counter32	read-only	Number of packets detected with unexpected size or bad headers' stack.
C32 pwTDMPerf1DayIntervalMisOrderDropped	1.3.6.1.2.1.186.1.7.1.7	Counter32	read-only	Number of packets detected out of order (via control word sequence numbers) that could not be re-ordered or could not fit in the jitter buffer.
C32 pwTDMPerf1DayIntervalMissingPktsEx	1.3.6.1.2.1.186.1.7.1.4	Counter32	read-only	Number of missing packets (as detected via control word sequence number gaps).
U32 pwTDMPerf1DayIntervalNumber	1.3.6.1.2.1.186.1.7.1.1	Unsigned32	not-accessible	The number of intervals where 1 indicates the current day measured period and 2 and above indicate previous days, respectively.
C32 pwTDMPerf1DayIntervalPktsReOrder	1.3.6.1.2.1.186.1.7.1.5	Counter32	read-only	Number of packets detected out of sequence (via control word sequence number) but successfully re-ordered. Note: some implementations may not support this feature.
C32 pwTDMPerf1DayIntervalSESs	1.3.6.1.2.1.186.1.7.1.10	Counter32	read-only	The counter associated with the number of Severely Error Seconds.
pwTDMPerf1DayIntervalTable	1.3.6.1.2.1.186.1.7		not-accessible	This table provides performance information per TDM PW similar to the pwTDMPerfIntervalTable above. However, these counters represent historical one-day intervals up to one full month. The table consists of real-time data, as such it is not persistence across re-boot.
C32 pwTDMPerf1DayIntervalUASs	1.3.6.1.2.1.186.1.7.1.11	Counter32	read-only	The counter associated with the number of UnAvailable Seconds. NOTE: When first entering the UAS state, the number of SES to UAS is added to this object, then as each additional UAS occurs, this object increments by one.
T/F pwTDMPerf1DayIntervalValidData	1.3.6.1.2.1.186.1.7.1.2	TruthValue	read-only	This variable indicates if the data for this interval is valid.
pwTDMPerfCurrentEntry	1.3.6.1.2.1.186.1.5.1		not-accessible	An entry in this table is created by the agent for every pwTDMTable entry. After 15 minutes, the contents of this table entry are copied to a new entry in the pwTDMPerfInterval table, and the counts in this entry are reset to zero.
PER pwTDMPerfCurrentESs	1.3.6.1.2.1.186.1.5.1.6	PerfCurrentCount	read-only	The counter associated with the number of Error Seconds encountered. Any malformed packet, sequence error, LOPS, and the like are considered as Error Seconds.
PER pwTDMPerfCurrentFC	1.3.6.1.2.1.186.1.5.1.9	PerfCurrentCount	read-only	TDM Failure Counts (FC-TDM). The number of TDM failure events. A failure event begins when the LOPS failure is declared, and it 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.
pwTDMPerfCurrentGroup	1.3.6.1.2.1.186.2.2.2			Collection of current statistics objects for TDM PWs.
PER pwTDMPerfCurrentJtrBfrUnderruns	1.3.6.1.2.1.186.1.5.1.3	PerfCurrentCount	read-only	Number of times a packet needed to be played out and the jitter buffer was empty.
PER pwTDMPerfCurrentMalformedPkt	1.3.6.1.2.1.186.1.5.1.5	PerfCurrentCount	read-only	Number of packets detected with unexpected size or bad headers' stack.
PER pwTDMPerfCurrentMisOrderDropped	1.3.6.1.2.1.186.1.5.1.4	PerfCurrentCount	read-only	Number of packets detected out of order (via control word sequence numbers) that could not be re-ordered or could not fit in the jitter buffer.
PER pwTDMPerfCurrentMissingPkts	1.3.6.1.2.1.186.1.5.1.1	PerfCurrentCount	read-only	Number of missing packets (as detected via control word sequence number gaps).
PER pwTDMPerfCurrentPktsReOrder	1.3.6.1.2.1.186.1.5.1.2	PerfCurrentCount	read-only	Number of packets detected out of sequence (via control word sequence number) but successfully re-ordered. Note: some implementations may not support this feature.
PER pwTDMPerfCurrentSESs	1.3.6.1.2.1.186.1.5.1.7	PerfCurrentCount	read-only	The counter associated with the number of Severely Error Seconds encountered.
pwTDMPerfCurrentTable	1.3.6.1.2.1.186.1.5		not-accessible	The current 15-minute interval counts are in this table. This table provides per TDM PW performance information.
PER pwTDMPerfCurrentUASs	1.3.6.1.2.1.186.1.5.1.8	PerfCurrentCount	read-only	The counter associated with the number of Unavailable Seconds encountered. Any consecutive ten seconds of SES are counted as one Unavailable Seconds (UAS).
U32 pwTDMPerfIntervalDuration	1.3.6.1.2.1.186.1.6.1.3	Unsigned32	read-only	The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
pwTDMPerfIntervalEntry	1.3.6.1.2.1.186.1.6.1		not-accessible	An entry in this table is created by the agent for every pwTDMPerfCurrentEntry that is 15 minutes old. The contents of the Current entry are copied to the new entry here. The Current entry then resets its counts to zero for the next current 15-minute interval.
NUM pwTDMPerfIntervalESs	1.3.6.1.2.1.186.1.6.1.9	PerfIntervalCount	read-only	The counter associated with the number of Error Seconds encountered.
NUM pwTDMPerfIntervalFC	1.3.6.1.2.1.186.1.6.1.12	PerfIntervalCount	read-only	TDM Failure Counts (FC-TDM). The number of TDM failure events. A failure event begins when the LOPS failure is declared, and it 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.
pwTDMPerfIntervalGroup	1.3.6.1.2.1.186.2.2.3			Collection of Interval statistics objects for TDM PWs.
NUM pwTDMPerfIntervalJtrBfrUnderruns	1.3.6.1.2.1.186.1.6.1.6	PerfIntervalCount	read-only	Number of times a packet needed to be played out and the jitter buffer was empty.
NUM pwTDMPerfIntervalMalformedPkt	1.3.6.1.2.1.186.1.6.1.8	PerfIntervalCount	read-only	Number of packets detected with unexpected size, or bad headers' stack
NUM pwTDMPerfIntervalMisOrderDropped	1.3.6.1.2.1.186.1.6.1.7	PerfIntervalCount	read-only	Number of packets detected out of order (via control word sequence numbers) that could not be re-ordered or could not fit in the jitter buffer.
NUM pwTDMPerfIntervalMissingPkts	1.3.6.1.2.1.186.1.6.1.4	PerfIntervalCount	read-only	Number of missing packets (as detected via control word sequence number gaps).
U32 pwTDMPerfIntervalNumber	1.3.6.1.2.1.186.1.6.1.1	Unsigned32	not-accessible	A number (normally between 1 and 96 to cover a 24 hour period) that identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15-minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1. The minimum range of N is 1 through 4. The default range is 1 through 32. The maximum value of N is 1 through 96.
NUM pwTDMPerfIntervalPktsReOrder	1.3.6.1.2.1.186.1.6.1.5	PerfIntervalCount	read-only	Number of packets detected out of sequence (via control word sequence number) but successfully re-ordered. Note: some implementations may not support this feature.
NUM pwTDMPerfIntervalSESs	1.3.6.1.2.1.186.1.6.1.10	PerfIntervalCount	read-only	The counter associated with the number of Severely Error Seconds encountered.
pwTDMPerfIntervalTable	1.3.6.1.2.1.186.1.6		not-accessible	This table provides performance information per TDM PW similar to the pwTDMPerfCurrentTable above. However, these counts represent historical 15-minute intervals. Typically, this table will have a maximum of 96 entries for a 24 hour period, but is not limited to this.
NUM pwTDMPerfIntervalUASs	1.3.6.1.2.1.186.1.6.1.11	PerfIntervalCount	read-only	The counter associated with the number of Unavailable Seconds encountered.
T/F pwTDMPerfIntervalValidData	1.3.6.1.2.1.186.1.6.1.2	TruthValue	read-only	This variable indicates if the data for this interval is valid.
I32 pwTDMRate	1.3.6.1.2.1.186.1.1.1.1	Integer32	read-write	The parameter represents the bit-rate of the TDM service in multiples of the 'basic' 64 Kbit/s rate [TDMCP-EXT]. It complements the definition of pwType used in PW-STD-MIB. For structure-agnostic mode, the following should be used: a) (Structure-Agnostic TDM over Packet) Satop E1 - 32 b) Satop T1 emulation: i) MUST be set to 24 in the basic emulation mode ii) MUST be set to 25 for the 'Octet-aligned T1' emulation mode c) Satop E3 - 535 d) Satop T3 - 699 For all kinds of structure-aware emulation, this parameter MUST be set to N where N is the number of DS0 channels in the corresponding attachment circuit.
pwTDMTable	1.3.6.1.2.1.186.1.1		not-accessible	This table contains basic information including the ifIndex and pointers to entries in the relevant TDM config tables for this TDM PW.
I32 pwTDMTimeElapsed	1.3.6.1.2.1.186.1.1.1.6	Integer32	read-only	The number of seconds, including partial seconds, that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
I32 pwTDMValidDayIntervals	1.3.6.1.2.1.186.1.1.1.8	Integer32	read-only	The number of previous days for which data was collected. An agent with TDM capability must be capable of supporting at least n intervals. The minimum value of n is 1. The default of n is 1 and the maximum value of n is 30.
I32 pwTDMValidIntervals	1.3.6.1.2.1.186.1.1.1.7	Integer32	read-only	The number of previous 15-minute intervals for which data was collected. An agent with TDM capability must be capable of supporting at least n intervals. The minimum value of n is 4. The default of n is 32 and the maximum value of n is 96. The value will be n unless the measurement was (re-) started within the last (n*15) minutes, in which case, the value will be the number of complete 15-minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.

RFC description

Encapsulates TDM circuits (T1, E1, T3, E3, NxDS0) as pseudo-wires over packet-switching networks with configuration and statistics.

Start monitoring MPLS/PSN provider-edge router, TDM circuit-emulation gateway, vendor-neutral IETF MIB (RFC 5604) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download PW-TDM-MIB