All MIBs › JUNIPER-PW-TDM-MIB
Organization: Pseudo-Wire Emulation Edge-to-Edge (PWE3) Working Group
Last Updated: 2007-04-03
Category: Pseudowire, Vendor: Juniper
Description: Juniper Networks MIB for managing TDM (Time Division Multiplexing) pseudowire emulation circuits on Juniper router platforms.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.
What Is JUNIPER-PW-TDM-MIB?
JUNIPER-PW-TDM-MIB is a Juniper Networks MIB (built on the IETF PW-STD-MIB framework) for managing TDM (T1, E1, T3, E3, NxDS0) pseudowire emulation circuits that carry time-division-multiplexed traffic over a packet-switched network on Juniper routers. Although no sample objects were retrievable for this batch, based on its stated purpose it would expose configuration objects for TDM pseudowire circuit parameters (e.g., framing, clocking mode, payload size) alongside status/statistics objects layered on top of the generic pseudowire state machine defined in PW-STD-MIB. Its monitoring value would center on circuit/software status -- pseudowire up/down state, clocking synchronization, and TDM-specific error counters -- which reveal whether a TDM circuit emulation is correctly carrying legacy voice/data traffic across the packet network, rather than physical chassis hardware sensors. It explicitly supplements the IETF PW-STD-MIB, relying on that MIB's generic pseudowire structures and adding TDM-type-specific configuration and statistics. It is deployed on Juniper routers acting as PE (provider edge) devices in carrier networks offering TDM circuit emulation services over MPLS or IP backbones. Engineers can download the JUNIPER-PW-TDM-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-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
- Juniper Networks router (PE device) providing TDM pseudowire/circuit emulation
Monitoring Examples
No sample objects were available for this MIB in the provided data, so a concrete polling scenario naming actual table/object names cannot be responsibly constructed; in general terms, a carrier would be expected to poll the TDM pseudowire's operational state (extending the underlying PW-STD-MIB's status objects) and TDM-specific error/underrun counters to detect clock slips or framing errors on a T1/E1 emulated circuit.
This MIB depends on
Related MIBs
Imported Objects
From IF-MIB
| InterfaceIndexOrZero |
From JUNIPER-SMI
| jnxMibs | OBJECT-IDENTITY |
| jnxPwTdmMibRoot | OBJECT-IDENTITY |
From JUNIPER-VPN-MIB
| jnxVpnPwIndex | OBJECT-TYPE |
| jnxVpnPwVpnName | OBJECT-TYPE |
| jnxVpnPwVpnType | OBJECT-TYPE |
From PerfHist-TC-MIB
| PerfCurrentCount | |
| PerfIntervalCount |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 | |
| transmission |
From SNMPv2-TC
| RowStatus | |
| StorageType | |
| TEXTUAL-CONVENTION | |
| TimeStamp | |
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| JNX jnxpwGenTDMCfgIndex | 1.3.6.1.4.1.2636.3.54.1.1.1.1.3 | JnxPwCfgIndexOrzero | read-only | 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. |
| JNX jnxpwRelTDMCfgIndex | 1.3.6.1.4.1.2636.3.54.1.1.1.1.4 | JnxPwCfgIndexOrzero | read-only | 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 MIB |
| U32 jnxpwTDMCfgAlarmThreshold | 1.3.6.1.4.1.2636.3.54.1.1.3.1.15 | Unsigned32 | read-only | Alarms are only reported when the defect state persists for the length of time specified by this object. The object's unit is millisec. Object MAY be changed when the related PW is defined as not active. |
| I32 jnxpwTDMCfgAvePktLossTimeWindow | 1.3.6.1.4.1.2636.3.54.1.1.3.1.13 | Integer32 | read-only | The length of time over which the average packet loss rate should be computed to detect Excessive packet loss rate. Object MAY be changed when the related PW is defined as not active. |
| U32 jnxpwTDMCfgClearAlarmThreshold | 1.3.6.1.4.1.2636.3.54.1.1.3.1.16 | Unsigned32 | read-only | Alarm MUST be cleared after the corresponding defect is undetected for the amount of time specified by this object. The object's unit is millisec. Object MAY be changed when the related PW is defined as not active. |
| U32 jnxpwTDMCfgConsecMissPktsOutSynch | 1.3.6.1.4.1.2636.3.54.1.1.3.1.10 | Unsigned32 | read-only | The number of consecutive missing packets that are required to enter the LOPS state. Object MAY be changed when the related PW is defined as not active. |
| U32 jnxpwTDMCfgConsecPktsInSynch | 1.3.6.1.4.1.2636.3.54.1.1.3.1.9 | Unsigned32 | read-only | The number of consecutive packets with sequential sequence numbers that are required to exit the LOPS state. Object MAY be changed when the related PW is defined as not active. |
| jnxpwTDMCfgEntry | 1.3.6.1.4.1.2636.3.54.1.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]) if the row index is in used by an entry in pwTDMTable. Rows should remain unchanged after reboot. | |
| U32 jnxpwTDMCfgExcessivePktLossThreshold | 1.3.6.1.4.1.2636.3.54.1.1.3.1.14 | Unsigned32 | read-only | Excessive packet loss rate is detected by computing the average packetloss rate over a pwTDMCfgAvePktLossTimeWindow amount of time and comparing it with this threshold value. The rate is expressed in precentage. Object MAY be changed when the related PW is defined as not active. |
| JNX jnxpwTDMCfgIndex | 1.3.6.1.4.1.2636.3.54.1.1.3.1.1 | JnxPwTDMCfgIndex | not-accessible | Index to an entry in this table. The value is a copy of the assigned pwTDMCfgIndexNext |
| U32 jnxpwTDMCfgIndexNext | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMCfgJtrBfrDepth | 1.3.6.1.4.1.2636.3.54.1.1.3.1.7 | Unsigned32 | read-only | 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 jnxpwTDMCfgMissingPktsToSes | 1.3.6.1.4.1.2636.3.54.1.1.3.1.17 | Unsigned32 | read-only | 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 when the related PW is defined as not active. |
| STR jnxpwTDMCfgName | 1.3.6.1.4.1.2636.3.54.1.1.3.1.21 | SnmpAdminString | read-only | A descriptive string, prefereably unique name, to an entry in this table. Object MAY be changed at any time. |
| U32 jnxpwTDMCfgPayloadSize | 1.3.6.1.4.1.2636.3.54.1.1.3.1.4 | Unsigned32 | read-only | 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 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 jnxpwTDMCfgPayloadSuppression | 1.3.6.1.4.1.2636.3.54.1.1.3.1.8 | INTEGER | read-only | Selecting 'enable' means: Payload suppression is allowed. Payload MAY be omitted in order to conserve bandwidth. Selecting 'disable' means: no suppresion under any condition. Object MAY be changed at any time. |
| U32 jnxpwTDMCfgPktFiller | 1.3.6.1.4.1.2636.3.54.1.1.3.1.20 | Unsigned32 | read-only | Filler byte pattern played out on the TDM interface if pwTDMCfgPktReplacePolicy was set to filler(3). Object MAY be changed when the related PW is defined as not active. |
| T/F jnxpwTDMCfgPktReorder | 1.3.6.1.4.1.2636.3.54.1.1.3.1.5 | TruthValue | read-only | If set 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 is then required to set this to False. |
| INT jnxpwTDMCfgPktReplacePolicy | 1.3.6.1.4.1.2636.3.54.1.1.3.1.12 | INTEGER | read-only | This parameter determines the value to be played when CE bound packets have 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 agent specific algorithm. Selecting filler(3) requires setting of pwTDMCfgPktFiller. Object MAY be changed when the related PW is defined as not active. |
| ROW jnxpwTDMCfgRowStatus | 1.3.6.1.4.1.2636.3.54.1.1.3.1.2 | RowStatus | read-only | Object used for creating, modifying, and deleting a row from this table. The following objects should not be modified if the entry is in used and the status is active: pwTDMCfgPayloadSize, pwTDMCfgRtpHdrUsed, pwTDMCfgJtrBfrDepth, and pwTDMCfgPayloadSuppression. The row should not be deleted if the entry is in used |
| T/F jnxpwTDMCfgRtpHdrUsed | 1.3.6.1.4.1.2636.3.54.1.1.3.1.6 | TruthValue | read-only | If set to False: an RTP header is not pre-pended to the TDM packet. |
| U32 jnxpwTDMCfgSetUp2SynchTimeOut | 1.3.6.1.4.1.2636.3.54.1.1.3.1.11 | Unsigned32 | read-only | The amount of time the host should wait before declaring the pseudo wire in down state, if the number of consecutive TDM packets that have been received after changing the adminstrative status to up and after finalization of signaling (if supported) between the two PEs is smaller than pwTDMCfgConsecPktsInSynch. Once the 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 adminisrative 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 when the related PW is defined as not active. |
| STO jnxpwTDMCfgStorageType | 1.3.6.1.4.1.2636.3.54.1.1.3.1.19 | StorageType | read-only | This variable indicates the storage type for this row. |
| jnxpwTDMCfgTable | 1.3.6.1.4.1.2636.3.54.1.1.3 | not-accessible | This table contains a set of parameters that may be referenced by one or more TDM PWs in pwTDMTable. | |
| INT jnxpwTDMCfgTimestampMode | 1.3.6.1.4.1.2636.3.54.1.1.3.1.18 | INTEGER | read-only | 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 when the related PW is defined as not active. |
| jnxpwTDMCompliances | 1.3.6.1.4.1.2636.3.54.1.3.2 | |||
| BIT jnxpwTDMConfigError | 1.3.6.1.4.1.2636.3.54.1.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. |
| jnxpwTDMConformance | 1.3.6.1.4.1.2636.3.54.1.3 | |||
| jnxpwTDMEntry | 1.3.6.1.4.1.2636.3.54.1.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), tdmCasTdmIp(24). Unless otherwise specified, all RW objects in this table MUST NOT be changed after row activation (see [PWMIB]) and should remain unchanged after reboot. | |
| jnxpwTDMGroup | 1.3.6.1.4.1.2636.3.54.1.3.1.1 | Collection of objects for basic TDM PW config and status. | ||
| jnxpwTDMGroups | 1.3.6.1.4.1.2636.3.54.1.3.1 | |||
| NUM jnxpwTDMIfIndex | 1.3.6.1.4.1.2636.3.54.1.1.1.1.2 | InterfaceIndexOrZero | read-only | 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 jnxpwTDMLastEsTimeStamp | 1.3.6.1.4.1.2636.3.54.1.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. |
| jnxPWTdmMIB | 1.3.6.1.4.1.2636.3.54.1 | 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. 'Pseudo Wire (PW) Management Information Base'. The PW-STD-MIB contains structures and MIB associations generic to Pseudo-Wire (PW) emulation. PW-specific MIBs (such as this) contain config and stats for specific PW types. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices. -- RFC Ed.: replace yyyy with actual RFC number & remove this note | ||
| jnxpwTDMModuleCompliance | 1.3.6.1.4.1.2636.3.54.1.3.2.1 | The compliance statement for agent that support TDM PW over PSN operation. | ||
| jnxpwTDMNotifications | 1.3.6.1.4.1.2636.3.54.1.2 | |||
| jnxpwTDMObjects | 1.3.6.1.4.1.2636.3.54.1.1 | |||
| U32 jnxpwTDMPerf1DayIntervalDuration | 1.3.6.1.4.1.2636.3.54.1.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. |
| jnxpwTDMPerf1DayIntervalEntry | 1.3.6.1.4.1.2636.3.54.1.1.7.1 | not-accessible | An entry is created in this table by the agent for every entry in the pwTDMTable table. | |
| C32 jnxpwTDMPerf1DayIntervalESs | 1.3.6.1.4.1.2636.3.54.1.1.7.1.9 | Counter32 | read-only | The counter associated with the number of Error Seconds encountered. |
| C32 jnxpwTDMPerf1DayIntervalFC | 1.3.6.1.4.1.2636.3.54.1.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 ends when the failure is cleared. |
| jnxpwTDMPerf1DayIntervalGroup | 1.3.6.1.4.1.2636.3.54.1.3.1.4 | Collection of Daily statistics objects for TDM PWs. | ||
| C32 jnxpwTDMPerf1DayIntervalJtrBfrUnderruns | 1.3.6.1.4.1.2636.3.54.1.1.7.1.6 | Counter32 | read-only | Number of times a packet needed to be played out and the jitter buffer was empty. |
| C32 jnxpwTDMPerf1DayIntervalMalformedPkt | 1.3.6.1.4.1.2636.3.54.1.1.7.1.8 | Counter32 | read-only | Number of packets detected with unexpected size, or bad headers' stack. |
| C32 jnxpwTDMPerf1DayIntervalMisOrderDropped | 1.3.6.1.4.1.2636.3.54.1.1.7.1.7 | Counter32 | read-only | Number of packets detected out of order(via control word sequence numbers), and could not be re-ordered, or could not fit in the jitter buffer. |
| C32 jnxpwTDMPerf1DayIntervalMissingPkts | 1.3.6.1.4.1.2636.3.54.1.1.7.1.4 | Counter32 | read-only | Number of missing packets (as detected via control word sequence number gaps). |
| U32 jnxpwTDMPerf1DayIntervalNumber | 1.3.6.1.4.1.2636.3.54.1.1.7.1.1 | Unsigned32 | not-accessible | The number of interval, where 1 indicates current day measured period and 2 and above indicate previous days respectively |
| C32 jnxpwTDMPerf1DayIntervalPktsReOrder | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerf1DayIntervalSESs | 1.3.6.1.4.1.2636.3.54.1.1.7.1.10 | Counter32 | read-only | The counter associated with the number of Severely Error Seconds. |
| jnxpwTDMPerf1DayIntervalTable | 1.3.6.1.4.1.2636.3.54.1.1.7 | not-accessible | This table provides performance information per TDM PW similar to the pwTDMPerfIntervalTable above. However, these counters represent historical 1 day intervals up to one full month. The table consists of real time data, as such it is not persistence across re-boot. | |
| C32 jnxpwTDMPerf1DayIntervalUASs | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerf1DayIntervalValidData | 1.3.6.1.4.1.2636.3.54.1.1.7.1.2 | TruthValue | read-only | This variable indicates if the data for this interval is valid. |
| jnxpwTDMPerfCurrentEntry | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerfCurrentESs | 1.3.6.1.4.1.2636.3.54.1.1.5.1.6 | PerfCurrentCount | read-only | The counter associated with the number of Error Seconds encountered. Any malformed packet, seq. error, LOPS and similar are considered as error second |
| PER jnxpwTDMPerfCurrentFC | 1.3.6.1.4.1.2636.3.54.1.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 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. |
| jnxpwTDMPerfCurrentGroup | 1.3.6.1.4.1.2636.3.54.1.3.1.2 | Collection of current statistics objects for TDM PWs. | ||
| PER jnxpwTDMPerfCurrentJtrBfrUnderruns | 1.3.6.1.4.1.2636.3.54.1.1.5.1.3 | PerfCurrentCount | read-only | Number of times a packet needed to be played out and the jitter buffer was empty. |
| PER jnxpwTDMPerfCurrentMalformedPkt | 1.3.6.1.4.1.2636.3.54.1.1.5.1.5 | PerfCurrentCount | read-only | Number of packets detected with unexpected size, or bad headers' stack |
| PER jnxpwTDMPerfCurrentMisOrderDropped | 1.3.6.1.4.1.2636.3.54.1.1.5.1.4 | PerfCurrentCount | read-only | Number of packets detected out of order(via control word sequence numbers), and could not be re-ordered, or could not fit in the jitter buffer. |
| PER jnxpwTDMPerfCurrentMissingPkts | 1.3.6.1.4.1.2636.3.54.1.1.5.1.1 | PerfCurrentCount | read-only | Number of missing packets (as detected via control word sequence number gaps). |
| PER jnxpwTDMPerfCurrentPktsReOrder | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerfCurrentSESs | 1.3.6.1.4.1.2636.3.54.1.1.5.1.7 | PerfCurrentCount | read-only | The counter associated with the number of Severely Error Seconds encountered. |
| jnxpwTDMPerfCurrentTable | 1.3.6.1.4.1.2636.3.54.1.1.5 | not-accessible | The current 15 minute interval counts are in this table. This table provides per TDM PW performance information. | |
| PER jnxpwTDMPerfCurrentUASs | 1.3.6.1.4.1.2636.3.54.1.1.5.1.8 | PerfCurrentCount | read-only | The counter associated with the number of Unavailable Seconds encountered. Any consequtive ten seconds of SES are counted as one UAS |
| U32 jnxpwTDMPerfIntervalDuration | 1.3.6.1.4.1.2636.3.54.1.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. |
| jnxpwTDMPerfIntervalEntry | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerfIntervalESs | 1.3.6.1.4.1.2636.3.54.1.1.6.1.9 | PerfIntervalCount | read-only | The counter associated with the number of Error Seconds encountered. |
| NUM jnxpwTDMPerfIntervalFC | 1.3.6.1.4.1.2636.3.54.1.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 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. |
| jnxpwTDMPerfIntervalGroup | 1.3.6.1.4.1.2636.3.54.1.3.1.3 | Collection of Interval statistics objects for TDM PWs. | ||
| NUM jnxpwTDMPerfIntervalJtrBfrUnderruns | 1.3.6.1.4.1.2636.3.54.1.1.6.1.6 | PerfIntervalCount | read-only | Number of times a packet needed to be played out and the jitter buffer was empty. |
| NUM jnxpwTDMPerfIntervalMalformedPkt | 1.3.6.1.4.1.2636.3.54.1.1.6.1.8 | PerfIntervalCount | read-only | Number of packets detected with unexpected size, or bad headers' stack |
| NUM jnxpwTDMPerfIntervalMisOrderDropped | 1.3.6.1.4.1.2636.3.54.1.1.6.1.7 | PerfIntervalCount | read-only | Number of packets detected out of order(via control word sequence numbers), and could not be re-ordered, or could not fit in the jitter buffer. |
| NUM jnxpwTDMPerfIntervalMissingPkts | 1.3.6.1.4.1.2636.3.54.1.1.6.1.4 | PerfIntervalCount | read-only | Number of missing packets (as detected via control word sequence number gaps). |
| U32 jnxpwTDMPerfIntervalNumber | 1.3.6.1.4.1.2636.3.54.1.1.6.1.1 | Unsigned32 | not-accessible | A number (normally between 1 and 96 to cover a 24 hour period) which 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 jnxpwTDMPerfIntervalPktsReOrder | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerfIntervalSESs | 1.3.6.1.4.1.2636.3.54.1.1.6.1.10 | PerfIntervalCount | read-only | The counter associated with the number of Severely Error Seconds encountered. |
| jnxpwTDMPerfIntervalTable | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMPerfIntervalUASs | 1.3.6.1.4.1.2636.3.54.1.1.6.1.11 | PerfIntervalCount | read-only | The counter associated with the number of Unavailable Seconds encountered. |
| T/F jnxpwTDMPerfIntervalValidData | 1.3.6.1.4.1.2636.3.54.1.1.6.1.2 | TruthValue | read-only | This variable indicates if the data for this interval is valid. |
| I32 jnxpwTDMRate | 1.3.6.1.4.1.2636.3.54.1.1.1.1.1 | Integer32 | read-only | 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 the following should be used: a) 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. |
| jnxpwTDMTable | 1.3.6.1.4.1.2636.3.54.1.1.1 | not-accessible | This table contains basic information including ifIndex, and pointers to entries in the relevant TDM config tables for this TDM PW. | |
| I32 jnxpwTDMTimeElapsed | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMValidDayIntervals | 1.3.6.1.4.1.2636.3.54.1.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 jnxpwTDMValidIntervals | 1.3.6.1.4.1.2636.3.54.1.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
Juniper pseudo-wire TDM encapsulation management for T1/E1/T3/E3 circuit emulation over packet networks.
Start monitoring Vendor-neutral IETF PWE3 draft standard (TDM pseudowire, RAD Data Communications editor) 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.