JUNIPER-PW-TDM-MIB
Updated Apr 3, 2007This 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.
note
Main OID:
jnxPWTdmMIB.1.3.6.1.4.1.2636.3.54.1
79
Objects
Active
Status
8
Dependencies
Imported Objects
Objects
79 total| Object Name |
|---|
jnxPWTdmMIBThis 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.
note MODULE-IDENTITY .1.3.6.1.4.1.2636.3.54.1 |
jnxpwTDMObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.54.1.1 |
jnxpwTDMTableThis table contains basic information including ifIndex,
and pointers to entries in the relevant TDM config
tables for this TDM PW. SEQUENCE OF JnxPwTDMEntry .1.3.6.1.4.1.2636.3.54.1.1.1 |
jnxpwTDMEntryThis 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. JnxPwTDMEntry .1.3.6.1.4.1.2636.3.54.1.1.1.1 |
jnxpwTDMRateThe 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.ro Integer32 -- .1.3.6.1.4.1.2636.3.54.1.1.1.1.1 |
jnxpwTDMIfIndexThis 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.ro InterfaceIndexOrZero -- .1.3.6.1.4.1.2636.3.54.1.1.1.1.2 |
jnxpwGenTDMCfgIndexIndex 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.ro JnxPwCfgIndexOrzero -- .1.3.6.1.4.1.2636.3.54.1.1.1.1.3 |
jnxpwRelTDMCfgIndexIndex 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 MIBro JnxPwCfgIndexOrzero -- .1.3.6.1.4.1.2636.3.54.1.1.1.1.4 |
jnxpwTDMConfigErrorAny 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.ro Bits .1.3.6.1.4.1.2636.3.54.1.1.1.1.5 |
jnxpwTDMTimeElapsedThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.54.1.1.1.1.6 |
jnxpwTDMValidIntervalsThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.54.1.1.1.1.7 |
jnxpwTDMValidDayIntervalsThe 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.ro Integer32 .1.3.6.1.4.1.2636.3.54.1.1.1.1.8 |
jnxpwTDMLastEsTimeStampThe value of sysUpTime at the most recent occasion at
which the TDM PW entered the ES or SES state.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.2636.3.54.1.1.1.1.11 |
jnxpwTDMCfgIndexNextThis 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.ro Unsigned32 .1.3.6.1.4.1.2636.3.54.1.1.2 |
jnxpwTDMCfgTableThis table contains a set of parameters that may be
referenced by one or more TDM PWs in pwTDMTable. SEQUENCE OF JnxPwTDMCfgEntry .1.3.6.1.4.1.2636.3.54.1.1.3 |
jnxpwTDMCfgEntryThese 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. JnxPwTDMCfgEntry .1.3.6.1.4.1.2636.3.54.1.1.3.1 |
jnxpwTDMCfgIndexIndex to an entry in this table. The value is a copy of the
assigned pwTDMCfgIndexNext JnxPwTDMCfgIndex .1.3.6.1.4.1.2636.3.54.1.1.3.1.1 |
jnxpwTDMCfgRowStatusObject 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 usedro RowStatus -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.2 |
jnxpwTDMCfgPayloadSizeThe 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.ro Unsigned32 -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.4 |
jnxpwTDMCfgPktReorderIf 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.ro TruthValue -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.5 |
jnxpwTDMCfgRtpHdrUsedIf set to False: an RTP header is not pre-pended to the
TDM packet.ro TruthValue -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.6 |
jnxpwTDMCfgJtrBfrDepthThe 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 pwTDMCfgJtrBfrDepthro Unsigned32 UNITS "microsecond" -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.7 |
jnxpwTDMCfgPayloadSuppressionSelecting '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.ro Enumeration .1.3.6.1.4.1.2636.3.54.1.1.3.1.8 |
jnxpwTDMCfgConsecPktsInSynchThe 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.ro Unsigned32 -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.9 |
jnxpwTDMCfgConsecMissPktsOutSynchThe 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.ro Unsigned32 -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.10 |
jnxpwTDMCfgSetUp2SynchTimeOutThe 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.ro Unsigned32 UNITS "millisecond" -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.11 |
jnxpwTDMCfgPktReplacePolicyThis 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.ro Enumeration .1.3.6.1.4.1.2636.3.54.1.1.3.1.12 |
jnxpwTDMCfgAvePktLossTimeWindowThe 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.ro Integer32 UNITS "millisecond" -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.13 |
jnxpwTDMCfgExcessivePktLossThresholdExcessive 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.ro Unsigned32 UNITS "Percent" -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.14 |
jnxpwTDMCfgAlarmThresholdAlarms 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.ro Unsigned32 -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.15 |
jnxpwTDMCfgClearAlarmThresholdAlarm 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.ro Unsigned32 -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.16 |
jnxpwTDMCfgMissingPktsToSesPercent 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.ro Unsigned32 UNITS "Percent" -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.17 |
jnxpwTDMCfgTimestampModeTimestamp 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.ro Enumeration .1.3.6.1.4.1.2636.3.54.1.1.3.1.18 |
jnxpwTDMCfgStorageTypeThis variable indicates the storage type for this
row.ro StorageType -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.19 |
jnxpwTDMCfgPktFillerFiller 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.ro Unsigned32 .1.3.6.1.4.1.2636.3.54.1.1.3.1.20 |
jnxpwTDMCfgNameA descriptive string, prefereably unique name, to an entry
in this table.
Object MAY be changed at any time.ro SnmpAdminString -- .1.3.6.1.4.1.2636.3.54.1.1.3.1.21 |
jnxpwTDMPerfCurrentTableThe current 15 minute interval counts are in
this table.
This table provides per TDM PW performance information. SEQUENCE OF JnxPwTDMPerfCurrentEntry .1.3.6.1.4.1.2636.3.54.1.1.5 |
jnxpwTDMPerfCurrentEntryAn 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. JnxPwTDMPerfCurrentEntry .1.3.6.1.4.1.2636.3.54.1.1.5.1 |
jnxpwTDMPerfCurrentMissingPktsNumber of missing packets (as detected via control word
sequence number gaps).ro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.1 |
jnxpwTDMPerfCurrentPktsReOrderNumber of packets detected out of sequence (via control
word sequence number), but successfully re-ordered.
Note: some implementations may not support this Feature.ro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.2 |
jnxpwTDMPerfCurrentJtrBfrUnderrunsNumber of times a packet needed to be played
out and the jitter buffer was empty.ro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.3 |
jnxpwTDMPerfCurrentMisOrderDroppedNumber 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.ro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.4 |
jnxpwTDMPerfCurrentMalformedPktNumber of packets detected with unexpected size, or
bad headers' stackro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.5 |
jnxpwTDMPerfCurrentESsThe counter associated with the number of Error
Seconds encountered. Any malformed packet, seq. error, LOPS
and similar are considered as error secondro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.6 |
jnxpwTDMPerfCurrentSESsThe counter associated with the number of
Severely Error Seconds encountered.ro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.7 |
jnxpwTDMPerfCurrentUASsThe counter associated with the number of
Unavailable Seconds encountered. Any consequtive
ten seconds of SES are counted as one UASro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.8 |
jnxpwTDMPerfCurrentFCTDM 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.ro PerfCurrentCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.5.1.9 |
jnxpwTDMPerfIntervalTableThis 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. SEQUENCE OF JnxPwTDMPerfIntervalEntry .1.3.6.1.4.1.2636.3.54.1.1.6 |
jnxpwTDMPerfIntervalEntryAn 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. JnxPwTDMPerfIntervalEntry .1.3.6.1.4.1.2636.3.54.1.1.6.1 |
jnxpwTDMPerfIntervalNumberA 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. Unsigned32 .1.3.6.1.4.1.2636.3.54.1.1.6.1.1 |
jnxpwTDMPerfIntervalValidDataThis variable indicates if the data for this interval
is valid.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2636.3.54.1.1.6.1.2 |
jnxpwTDMPerfIntervalDurationThe 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.ro Unsigned32 .1.3.6.1.4.1.2636.3.54.1.1.6.1.3 |
jnxpwTDMPerfIntervalMissingPktsNumber of missing packets (as detected via control
word sequence number gaps).ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.4 |
jnxpwTDMPerfIntervalPktsReOrderNumber of packets detected out of sequence (via control
word sequence number), but successfully re-ordered.
Note: some implementations may not support this
Feature.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.5 |
jnxpwTDMPerfIntervalJtrBfrUnderrunsNumber of times a packet needed to be played
out and the jitter buffer was empty.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.6 |
jnxpwTDMPerfIntervalMisOrderDroppedNumber 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.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.7 |
jnxpwTDMPerfIntervalMalformedPktNumber of packets detected with unexpected size, or
bad headers' stackro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.8 |
jnxpwTDMPerfIntervalESsThe counter associated with the number of Error
Seconds encountered.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.9 |
jnxpwTDMPerfIntervalSESsThe counter associated with the number of
Severely Error Seconds encountered.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.10 |
jnxpwTDMPerfIntervalUASsThe counter associated with the number of
Unavailable Seconds encountered.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.11 |
jnxpwTDMPerfIntervalFCTDM 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.ro PerfIntervalCount (PerfHist-TC-MIB) .1.3.6.1.4.1.2636.3.54.1.1.6.1.12 |
jnxpwTDMPerf1DayIntervalTableThis 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. SEQUENCE OF JnxPwTDMPerf1DayIntervalEntry .1.3.6.1.4.1.2636.3.54.1.1.7 |
jnxpwTDMPerf1DayIntervalEntryAn entry is created in this table by the agent
for every entry in the pwTDMTable table. JnxPwTDMPerf1DayIntervalEntry .1.3.6.1.4.1.2636.3.54.1.1.7.1 |
jnxpwTDMPerf1DayIntervalNumberThe number of interval, where 1 indicates current day
measured period and 2 and above indicate previous days
respectively Unsigned32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.1 |
jnxpwTDMPerf1DayIntervalValidDataThis variable indicates if the data for this interval
is valid.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2636.3.54.1.1.7.1.2 |
jnxpwTDMPerf1DayIntervalDurationThe 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.ro Unsigned32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.3 |
jnxpwTDMPerf1DayIntervalMissingPktsNumber of missing packets (as detected via control word
sequence number gaps).ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.4 |
jnxpwTDMPerf1DayIntervalPktsReOrderNumber of packets detected out of sequence (via control
word sequence number), but successfully re-ordered.
Note: some implementations may not support this
feature.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.5 |
jnxpwTDMPerf1DayIntervalJtrBfrUnderrunsNumber of times a packet needed to be played
out and the jitter buffer was empty.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.6 |
jnxpwTDMPerf1DayIntervalMisOrderDroppedNumber 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.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.7 |
jnxpwTDMPerf1DayIntervalMalformedPktNumber of packets detected with unexpected size, or
bad headers' stack.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.8 |
jnxpwTDMPerf1DayIntervalESsThe counter associated with the number of Error
Seconds encountered.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.9 |
jnxpwTDMPerf1DayIntervalSESsThe counter associated with the number of Severely
Error Seconds.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.10 |
jnxpwTDMPerf1DayIntervalUASsThe 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.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.11 |
jnxpwTDMPerf1DayIntervalFCTDM 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.ro Counter32 .1.3.6.1.4.1.2636.3.54.1.1.7.1.12 |
jnxpwTDMNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.54.1.2 |
jnxpwTDMConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.54.1.3 |
jnxpwTDMGroups OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.54.1.3.1 |
jnxpwTDMCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.54.1.3.2 |