WANSTATS-MIB: View SNMP OID List / Download MIB

The MIB containing RMON media statistics for WAN links.

T1/E1 signaling statistics.

Statistics for a T1/E1 interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanT1E1StatsTable entry.

This object identifies the source of the data that this wanT1E1StatsEntry analyzes. This source can be any DS1 or E1 interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be ds1(18).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen originating from the far end of the link including errored frames.

The total number of frames seen originating from the near end of the link including errored frames.

The sum of octets from all frames seen originating from the far end of the link including errored frames.

The sum of octets from all frames seen originating from the near end of the link including errored frames.

For ESF and E1-CRC links an Errored Second is a second with one or more Path Code Violations OR one or more Out of Frame defects OR one or more Controlled Slip events OR a detected AIS defect. For D4 and E1-noCRC links, the presence of Bipolar Violations also triggers an Errored Second. This is not incremented during an Unavailable Second.

A Severely Errored Second for ESF signals is a second with 320 or more Path Code Violation Error Events OR one or more Out of Frame defects OR a detected AIS defect. For E1-CRC signals, a Severely Errored Second is a second with 832 or more Path Code Violation error events OR one or more Out of Frame defects. For E1-noCRC signals, a Severely Errored Second is a 2048 LCVs or more. For D4 signals, a Severely Errored Second is a count of one-second intervals with Framing Error events, or an OOF defect, or 1544 LCVs or more. Controlled slips are not included in this parameter. This is not incremented during an Unavailable Second.

An Severely Errored Framing Second is a second with one or more Out of Frame defects OR a detected AIS defect.

An OOF defect is the occurrence of a particular density of Framing Error events. For T1 links, an Out of Frame defect is declared when the receiver detects two or more framing errors within a 3 msec period for ESF signals and 0.75 msec for D4 signals, or two or more errors out of five or fewer consecutive framing-bits. For E1 links, an Out Of Frame defect is declared when three consecutive frame alignment signals have been received with an error (see G.706 Section 4.1 [17]). Once an Out Of Frame Defect is declared, the framer starts searching for a correct framing pattern. The Out of Frame defect ends when the signal is in frame. In-frame occurs when there are fewer than two frame bit errors within 3 msec period for ESF signals and 0.75 msec for D4 signals. For E1 links, in-frame occurs when a) in frame N the frame alignment signal is correct and b) in frame N+1 the frame alignment signal is absent (i.e., bit 2 in TS0 is a one) and c) in frame N+2 the frame alignment signal is present and correct.

Unavailable Seconds (UAS) are calculated by counting the number of seconds that the interface is unavailable. The DS1 interface is said to be unavailable from the onset of 10 contiguous SESs, or the onset of the condition leading to a failure (see Failure States). If the condition leading to the failure was immediately preceded by one or more contiguous SESs, then the DS1 interface unavailability starts from the onset of these SESs. Once unavailable, and if no failure is present, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs. Once unavailable, and if a failure is present, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs, if the failure clearing time is less than or equal to 10 seconds. If the failure clearing time is more than 10 seconds, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs, or the onset period leading to the successful clearing condition, whichever occurs later. With respect to the DS1 error counts, all counters are incremented while the DS1 interface is deemed available. While the interface is deemed unavailable, the only count that is incremented is UASs.

A Controlled Slip Second is a one-second interval containing one or more controlled slips.

A Path Coding Violation error event is a frame synchronization bit error in the D4 and E1-noCRC formats, or a CRC error in the ESF and E1-CRC formats.

A Line Errored Second, according to T1M1.3, is a second in which one or more Line Code Violation error events were detected. While many implementations are currently unable to detect the zero strings, it is expected that interface manufacturers will add this capability in deference to ANSI; therefore, it will become available in time. In the T1M1.3 specification, near end Line Code Violations and far end Line Errored Seconds are counted. For consistency, we count Line Errored Seconds at both ends.

A Bursty Errored Second (also known as Errored Second type B) is a second with fewer than 320 and more than 1 Path Coding Violation error events, no Severely Errored Frame defects and no detected incoming AIS defects. Controlled slips are not included in this parameter. This is not incremented during an Unavailable Second.

A Degraded Minute is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3 (see G.821 [15]). Degraded Minutes are determined by collecting all of the Available Seconds, removing any Severely Errored Seconds grouping the result in 60-second long groups and counting a 60-second long group (a.k.a., minute) as degraded if the cumulative errors during the seconds present in the group exceed 1E-6. Available seconds are merely those seconds which are not Unavailable as described below.

A Line Coding Violation (LCV) is the occurrence of either a Bipolar Violation (BPV) or Excessive Zeroes (EXZ) Error Event.

For T1 links, the Loss Of Frame failure is declared when an OOF or LOS defect has persisted for T seconds, where 2 <= T <= 10. The Loss Of Frame failure is cleared when there have been no OOF or LOS defects during a period T where 0 <= T <= 20. Many systems will perform 'hit integration' within the period T before declaring or clearing the failure e.g., see TR 62411 [16]. For E1 links, the Loss Of Frame Failure is declared when an OOF defect is detected.

For T1, the Loss Of Signal failure is declared upon observing 175 +/- 75 contiguous pulse positions with no pulses of either positive or negative polarity. The LOS failure is cleared upon observing an average pulse density of at least 12.5% over a period of 175 +/- 75 contiguous pulse positions starting with the receipt of a pulse. For E1 links, the Loss Of Signal failure is declared when greater than 10 consecutive zeroes are detected (see O.162 Section 3.4.4).

The Far End Alarm failure is also known as 'Yellow Alarm' in the T1 case and 'Distant Alarm' in the E1 case. For D4 links, the Far End Alarm failure is declared when bit 6 of all channels has been zero for at least 335 ms and is cleared when bit 6 of at least one channel is non-zero for a period T, where T is usually less than one second and always less than 5 seconds. The Far End Alarm failure is not declared for D4 links when a Loss of Signal is detected. For ESF links, the Far End Alarm failure is declared if the Yellow Alarm signal pattern occurs in at least seven out of ten contiguous 16-bit pattern intervals and is cleared if the Yellow Alarm signal pattern does not occur in ten contiguous 16-bit signal pattern intervals. For E1 links, the Far End Alarm failure is declared when bit 3 of time-slot zero is received set to one on two consecutive occasions. The Far End Alarm failure is cleared when bit 3 of time-slot zero is received set to zero.

The Alarm Indication Signal failure is declared when an AIS defect is detected at the input and the AIS defect still exists after the Loss Of Frame failure (which is caused by the unframed nature of the 'all-ones' signal) is declared. The AIS failure is cleared when the Loss Of Frame failure is cleared.

For E1 links, the TS16 Alarm Indication Signal failure is declared when time-slot 16 is received as all ones for all frames of two consecutive multiframes (see G.732 Section 4.2.6). This condition is never declared for T1.

The Loss Of MultiFrame failure is declared when two consecutive multiframe alignment signals (bits 4 through 7 of TS16 of frame 0) have been received with an error. The Loss Of Multiframe failure is cleared when the first correct multiframe alignment signal is received. The Loss Of Multiframe failure can only be declared for E1 links operating with G.732 [18] framing (sometimes called 'Channel Associated Signalling' mode).

The Far End Loss Of Multiframe failure is declared when bit 2 of TS16 of frame 0 is received set to one on two consecutive occasions. The Far End Loss Of Multiframe failure is cleared when bit 2 of TS16 of frame 0 is received set to zero. The Far End Loss Of Multiframe failure can only be declared for E1 links operating in 'Channel Associated Signalling' mode.

The entity that configured this entry.

The status of this wanT1E1StatsTable entry.

V-series interface statistics.

The statistics for a V-series interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanVSeriesStatsTable entry.

This object identifies the source of the data that this wanVSeriesStatsEntry analyzes. This source can be and V-series interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be rs232(33) , v35(45), v11(64), or v36(65).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen originating from the far end of the link including errored.

The total number of frames seen originating from the near end of the link including errored frames.

The sum of octets from all frames seen originating from the far end of the link including errored frames.

The sum of octets from all frames seen originating from the near end of the link including errored frames.

Total number of frames with an invalid frame check from the far end of the link.

Total number of frames with an invalid frame check from the near end of the link.

Total number of frames from the far end of the link that failed to be received because the receiver did not accept the data in time.

Total number of frames from the near end of the link that failed to be received because the receiver did not accept the data in time.

Total number of frames that failed to be received or transmitted on the port due to loss of modem signals.

Number of frames from the far end of the link aborted on the port due to receiving an abort sequence.

Number of frames from the near end of the link aborted on the port due to receiving an abort sequence.

The entity that configured this entry.

The status of this wanVSeriesStatsTable entry.

HSSI interface statistics.

The statistics for a HSSI interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanHssiStatsTable entry.

This object identifies the source of the data that this wanT1E1StatsEntry analyzes. This source can be any HSSI interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be hssi(46).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen originating from the far end of the link including errored frames.

The total number of frames seen originating from the near end of the link including errored frames.

The sum of octets from all frames seen originating from the far end of the link including errored frames.

The sum of octets from all frames seen originating from the near end of the link including errored frames.

Number of long frames from the far end of the link.

Number of frames from far end of link with CRC errors.

Number of frames from far end of link with FIFO overrun errors.

Number of frames from far end of link with abort status.

Number of frames from near end of link with internal abort errors.

Number of frames from near end of link aborted with underrun errors.

Number of receive ring error events.

Number of receive ring overrun events.

Number of transmit ring error events.

Number of port operation error events.

Number of transmit complete processings (TINT).

The entity that configured this entry.

The status of this wanHssiStatsTable entry.

T3/E3 signaling statistics

Statistics for a T3/E3 interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanT3E3StatsTable entry.

This object identifies the source of the data that this wanT3E3StatsEntry analyzes. This source can be any DS3 or E3 interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value of the associated ifIndex can only be ds3(30).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen originating from the far end of the link including errored frames.

The total number of frames seen originating from the near end of the link including errored frames.

The sum of octets from all frames seen originating from the far end of the link including errored frames.

The sum of octets from all frames seen originating from the near end of the link including errored frames.

A PES is a second with one or more PCVs OR one or more Out of Frame defects OR a detected incoming AIS. This gauge is not incremented when UASs are counted.

A PSES is a second with 44 or more PCVs OR one or more Out of Frame defects OR a detected incoming AIS. This gauge is not incremented when UASs are counted.

A DS3 OOF defect is detected when any three or more errors in sixteen or fewer consecutive F-bits occur within a DS3 M-frame. An OOF defect may also be called a Severely Errored Frame (SEF) defect. An OOF defect is cleared when reframe occurs. A DS3 Loss of Frame (LOF) failure is declared when the DS3 OOF defect is consistent for 2 to 10 seconds. The DS3 OOF defect ends when reframe occurs. The DS3 LOF failure is cleared when the DS3 OOF defect is absent for 10 to 20 seconds. An E3 OOF defect is detected when four consecutive frame alignment signals have been incorrectly received in there predicted positions in an E3 signal. E3 frame alignment occurs when the presence of three consecutive frame alignment signals have been detected.

A SEFS is a second with one or more Out of Frame defects OR a detected incoming AIS.

UAS are calculated by counting the number of seconds that the interface is unavailable. The DS3 interface is said to be unavailable from the onset of 10 contiguous PSESs, or the onset of the condition leading to a failure (see Failure States). If the condition leading to the failure was immediately preceded by one or more contiguous PSESs, then the DS3 interface unavailability starts from the onset of these PSESs. Once unavailable, and if no failure is present, the DS3 interface becomes available at the onset of 10 contiguous seconds with no PSESs. Once unavailable, and if a failure is present, the DS3 interface becomes available at the onset of 10 contiguous seconds with no PSESs, if the failure clearing time is less than or equal to 10 seconds. If the failure clearing time is more than 10 seconds, the DS3 interface becomes available at the onset of 10 contiguous seconds with no PSESs, or the onset period leading to the successful clearing condition, whichever occurs later. With respect to the DS3 error counts, all counters are incremented while the DS3 interface is deemed available. While the interface is deemed unavailable, the only count that is incremented is UASs.

This parameter is a count of both BPVs and EXZs occurring over the accumulation period. An EXZ increments the LCV by one regardless of the length of the zero string.

For all DS3 applications, a coding violation error event is a P-bit Parity Error event. A P-bit Parity Error event is the occurrence of a received P-bit code on the DS3 M-frame that is not identical to the corresponding locally- calculated code.

A Line Errored Second is a second in which one or more CVs occurred OR one or more LOS defects.

For C-bit Parity and SYNTRAN DS3 applications, this is the count of coding violations reported via the C-bits. For C-bit Parity, it is a count of CP-bit parity errors occurring in the accumulation interval. For SYNTRAN, it is a count of CRC-9 errors occurring in the accumulation interval.

An CES is a second with one or more CCVs OR one or more Out of Frame defects OR a detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3 applications. This gauge is not incremented when UASs are counted.

A CSES is a second with 44 or more CCVs OR one or more Out of Frame defects OR a detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3 applications. This gauge is not incremented when UASs are counted.

The Remote Alarm Indication (RAI) failure, in SYNTRAN applications, is declared after detecting the Yellow Alarm Signal on the alarm channel. See ANSI T1.107a-1990 [10]. The Remote Alarm Indication failure, in C-bit Parity DS3 applications, is declared as soon as the preqsence of either one or two alarm signals are detected on then Far End Alarm Channel. See [10]. The Remote Alarm Indication failure may also be declared after detecting the far-end SEF/AIS defect (aka yellow). The Remote Alarm Indication failure is cleared as soon as the presence of the any of the above alarms are removed. Also, the incoming failure state is declared when a defect persists for at least 2-10 seconds. The defects are the following: Loss of Signal (LOS), an Out of Frame (OOF) or an incoming Alarm Indication Signal (AIS). The Failure State is cleared when the defect is absent for less than or equal to 20 seconds.

The DS3 AIS is framed with 'stuck stuffing.' This implies that it has a valid M-subframe alignments bits, M-frame alignment bits, and P bits. The information bits are set to a 1010... sequence, starting with a one (1) after each M-subframe alignment bit, M-frame alignment bit, X bit, P bit, and C bit. The C bits are all set to zero giving what is called 'stuck stuffing.' The X bits are set to one. The DS3 AIS defect is declared after DS3 AIS is present in contiguous M-frames for a time equal to or greater than T, where 0.2 ms <= T <= 100 ms. The DS3 AIS defect is terminated after AIS is absent in contiguous M-frames for a time equal to or greater than T. The E3 binary content of the AIS is nominally a continuous stream of ones. AIS detection and the application of consequent actions, should be completed within a time limit of 1 ms.

A DS3 Loss of Frame (LOF) failure is declared when the DS3 OOF defect is consistent for 2 to 10 seconds. The DS3 OOF defect ends when reframe occurs. The DS3 LOF failure is cleared when the DS3 OOF defect is absent for 10 to 20 seconds. (See T1.231 section 7.1.2.2.1)

The DS3 LOS defect is declared upon observing 175 +/- 75 contiguous pulse positions with no pulses of either positive or negative polarity. The DS3 LOS defect is terminated upon observing an average pulse density of at least 33% over a period of 175 +/- 75 contiguous pulse positions starting with the receipt of a pulse.

The entity that configured this entry.

The status of this wanT3E3StatsTable entry.

ATM signaling statistics.

The statistics for an ATM interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In an ATM network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The value of this object uniquely identifies this wanAtmStatsTable entry.

This object identifies the source of the data that this wanAtmStatsEntry analyzes. This source can be any interface on this device. in order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be atm(37).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of cells seen coming from the far end of the link including errored cells.

The total number of cells seen coming from the near end of the link including errored cells.

The total number of cells with the CLP bit set seen coming from the far end of the link.

The total number of cells with the CLP bit set seen coming from the near end of the link.

This counter counts the sum of the following errors: 1) SSCOP Connection Disconnect Counter The abnormal occurrence of this event is characterized by the expiry of Timer_NO_RESPONSE. (This event is communicated to the layer management with MAA-ERROR code P. See ITU-T Q.2110.) 2) SSCOP Connection Initiation Failure This condition indicates the inability to establish an SSCOP connection. This event occurs whenever the number of expiries of the connection control timer (Timer_CC) exceeds the MaxCC or upon receipt of a connection reject message BGREJ PDU. (This event is communicated to layer management with MAA-ERROR code O. See ITU-T Q.2110.) 3) SSCOP Connection Re-Establ/Resynch This event occurs upon receipt of a BGN PDU or RESYNC PDU.

This counter counts the sum of the following errors: 1) Invalid PDUs. These are defined in SSCOP and consist of PDUs with incorrect length (MAA-ERROR code U), undefined PDU type code or not 32-bit aligned. 2) PDUs that result in MAA error codes and are discarded See Errors A-M and Q-T defined in ITU-T Q.2110.

This counter counts the number of call setup attempts (both successful and unsuccessful) detected on this interface.

This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant(for counting purposes) and should not be counted.

This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line id restriction 27 destination out of order 31 normal, unspecified 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure.

This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line id restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant(for counting purposes) and should not be counted. Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure.

The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: ? RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted or received, that contain any of the Cause values listed below. ? Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: Message with invalid protocol discriminator Message with errors in the call reference I.E. ? Bits 5-8 of the first octet not equal to '0000' ? Bits 1-4 of the first octet indicating a length other than 3 octets ? RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress ? SETUP message received with call reference flag incorrectly set to 1 ? SETUP message received with a call reference for a call that is already active or in progress. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated) Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: ? RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted or received, that contain any of the Cause values listed below. ? Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: Message with invalid protocol discriminator Message with errors in the call reference I.E. ? Bits 5-8 of the first octet not equal to '0000' ? Bits 1-4 of the first octet indicating a length other than 3 octets ? RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress ? SETUP message received with call reference flag incorrectly set to 1 ? SETUP message received with a call reference for a call that is already active or in progress. Message too short The following cause values are monitored by this counter Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated) Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 78 AAL parameters cannot be supported (UNI3.1 only) 91 invalid transit network selection 93 AAL parameters cannot be supported (UNI3.0 only) NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant(for counting purposes) and should not be counted.

This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 78 AAL parameters cannot be supported (UNI3.1 only) 91 invalid transit network selection 93 AAL parameters cannot be supported (UNI3.0 only) NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The conditions for incrementing this counter are: ? Expiry of any network timer ? Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The conditions for incrementing this counter are: ? Expiry of any network timer ? Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when receiving a RESTART message.

The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when transmitting a RESTART message.

SVC VCCs established at this signaling entity for incoming connections.

SVC VCCs established at this signaling entity for outgoing connections.

An out of cell delineation from far end of the link.

An out of cell delineation from near end of the link.

A loss of cell delineation error from far end of the link. This is a persistent OCD condition.

A loss of cell delineation error from near end of link. This is a persistent OCD condition.

A loss of frame error from far end of link.

A loss of frame error from near end of link.

A loss of pointer error from far end of link.

A loss of pointer error from near end of link.

A loss of signal error from far end of link.

A loss of signal error from near end of link.

The entity that configured this entry.

The status of this wanAtmStatsTable entry.

X.25 Packet layer statistics.

The statistics for an X.25 interface across all LCIs. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In an X.25 network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The value of this object uniquely identifies this wanX25StatsTable entry.

This object identifies the source of the data that this wanX25StatsEntry analyzes. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be rfc887-x25(5).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen coming from the far end of the link including error packets.

The total number of frames seen coming from the near end of the link including error packets.

The sum of octets from all frames seen originating from the far end of the link including errored frames.

The sum of octets from all frames seen originating from the near end of the link including errored frames.

The number of REJ or SREJ frames see coming from the far end of the link.

The number of REJ or SREJ frames see coming from the near end of the link.

The number of call setup attempts initiated from the far end of the link.

The number of call setup attempts initiated from the near end of the link.

The number call setup attempt failures seen coming from the far end of the link.

The number call setup attempt failures seen coming from the near end of the link.

The number of clear request seen with a cause code other than DTE initiated.

The number of reset requests seen from the far end of the link with cause code DTE initiated.

The number of reset requests seen from the near end of the link with cause code DTE initiated.

The number of reset requests seen with cause code other than DTE initiated.

The numbers of packets seen from the far end of the link containing a procedure error cause code. These include clear, reset, restart, or diagnostic packets.

The numbers of packets seen from the near end of the link containing a procedure error cause code. These include clear, reset, restart, or diagnostic packets.

The number of interrupts packets seen coming from the far end of the link over all VCs.

The number of interrupts packets seen coming from the near end of the link over all VCs.

The entity that configured this entry.

The status of this wanX25StatsTable entry.

Frame Relay statistics.

The statistics for a frame relay interface across all DLCIs. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In a frame relay network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The value of this object uniquely identifies this wanFrStatsTable entry.

This object identifies the source of the data that this wanFrStatsEntry analyzes. This source can be any frame relay interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be frameRelay(32).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen coming from the far end of the link including error packets.

The total number of frames seen coming from the near end of the link including error packets.

The sum of octets from all frames seen originating from the far end of the link including errored frames.

The sum of octets from all frames seen originating from the near end of the link including errored frames.

The number of frames see coming form the far end of the link with the FECN bit set.

The number of frames see coming form the near end of the link with the FECN bit set.

The number of frames seen coming from the far end of the link with the BECN bit set.

The number of frames seen coming from the near end of the link with the BECN bit set.

The number of frames seen coming from the far end of the link with the DE bit set.

The number of frames seen coming from the near end of the link with the DE bit set.

The entity that configured this entry.

The status of this wanFrStatsTable entry.

AAL/5 statistics.

The statistics for a AAL/5 interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In an ATM network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The value of this object uniquely identifies this wanAal5StatsTable entry.

This object identifies the source of the data that this wanAal5StatsEntry analyzes. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be aal5(49).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of cells for any AAL-5 connection seen coming from the far end of the link.

The total number of cells for any AAL-5 connection seen coming from the near end of the link.

The total number of AAL-5 PDUs seen coming from the far end of the link including error PDUs.

The total number of AAL-5 PDUs seen coming from the near end of the link including error PDUs.

The sum of octets from all AAL-5 PDUs seen originating from the far end of the link including errored PDUs.

The sum of octets from all AAL-5 PDUs seen originating from the near end of the link including errored PDUs.

The total number of cells for any AAL-5 connection with the CLP bit set seen coming from the far end of the link.

The total number of cells for any AAL-5 connection with the CLP bit set seen coming from the near end of the link.

The total number of AAL-5 PDUs with CRC errors from the far end of the link.

The total number of AAL-5 PDUs with CRC errors from the near end of the link.

The total number of AAL-5 SDUs from the far end of the link that were too large.

The total number of AAL-5 SDUs from the near end of the link that were too large.

The total number of AAL/5 connections seen initiated from the far end of the link.

The total number of AAL-5 connections seen initiated from the near end of the link.

The entity that configured this entry.

The status of this wanAal5StatsTable entry.

PPP in HDLC service statistics.

The statistics for a PPP in HDLC service. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanPppStatsTable entry.

This object identifies the source of the data that this wanPppStatsEntry analyzes. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [RFC 1573] for the desired interface. The ifType value associated with the ifIndex can only be ppp(22).

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen coming from the far end of the link including error frames.

The total number of frames seen coming from the near end of the link including error frames.

The sum of octets from all frames seen coming from the far end of the link including errored frames.

The sum of octets from all frames seen coming from the near end of the link including errored frames.

The number of frames seen from the far end of the link with an incorrect address field.

The number of frames seen from the near end of the link with an incorrect address field

The number of frames seen from the far end of the link with an incorrect control field.

The number of frames seen from the near end of the link with an incorrect control field.

The number of frames seen from the far end of the link that exceed the MRU.

The number of frames seen from the near end of the link that exceed the MRU.

The number of packets seen from the far end of the link with incorrect FCSs.

The number of packets seen from the near end of the link with incorrect FCSs.

The entity that configured this entry.

The status of this wanPppStatsTable entry.

X.25 per-LCI statistics for a PVC.

The statistics for a X.25 PVC. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the sides the probe is not on.

The value of this object uniquely identifies this wanX25PvcStatsTable entry.

This object identifies the source of the data that this wanX25PvcStatsEntry analyzes. This source can be any pvcEntry associated with an X.25 interface. In order to identify a particular LCI to monitor, this object shall identify the instance of the pvcIndex object that corresponds to a X.25 PVC, defined above for the desired interface.

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen coming from the far end of the link on this LCI.

The total number of frames seen coming from the near end of the link on this LCI.

The sum of octets from all frames seen originating from the far end of the link on this LCI.

The sum of octets from all frames seen originating from the near end of the link on this LCI.

The number of reset requests seen from the far end of the link with cause code DTE initiated for this LCI.

The number of reset requests seen from the far end of the link with cause code DTE initiated for this LCI.

The number of reset requests seen with cause code other than DTE initiated for this LCI.

The numbers of frames seen from the far end of the link containing a procedure error cause code on this LCI. These include clear, reset, restart, or diagnostic packets.

The numbers of frames seen from the near end of the link containing a procedure error cause code on this LCI. These include clear, reset, restart, or diagnostic packets.

The number of interrupts frames seen coming from the far end of the link on this LCI.

The number of interrupts frames seen coming from the far end of the link on this LCI.

The total amount of time in one-hundreds of a second that the probe is sure this LCI was active, i.e., the total time the value of wanX25PvcStatsState was equal to up(1). A value of less than the age of this entry does not necessarily mean that this LCI was down. It only means the probe was not certain it was up. Note: the sum of wanX25PvcStatsUpTime and wanX25PvcStatsDownTime may be less than the age of this entry. In this case, the unaccounted for time is the time the probe was uncertain of the state of this LCI, i.e., the total time the value of wanX25PvcStatsState was unknown(3).

The total amount of time in one-hundreds of a second that the probe is sure this LCI was down, i.e., the total time the value of wanX25PvcStatsState was equal to down(3). A value of less than the age of this entry does not necessarily mean that this LCI was up at some point. It only means the probe was not certain it was down. Note: the sum of wanX25PvcStatsUpTime and wanX25PvcStatsDownTime may be less than the age of this entry. In this case, the unaccounted for time is the time the probe was uncertain of the state of this LCI, i.e., the total time the value of wanX25PvcStatsState was unknown(3).

The current state of this LCI as inferred by the probe. A value of up(2) means the LCI is active. A value of down(2) means the LCI is inactive. And a value of unknown(3) means the probe cannot currently infer the state. Enumeration: 'down': 2, 'unknown': 3, 'up': 1.

The count of the number of times the wanX25PvcStatsState has gone from up(1) to down(2) or vice versa. The number of times wanX25PvcStatsState goes to unknown(3) is not counted. However, if the value goes from up(1) to unknown(3) and then to down(2) should be counted as 1. Likewise going from down(2) to unknown(3) and then to up(3) should be counted as 1.

The entity that configured this entry.

The status of this wanX25PvcStatsTable entry.

Frame Relay per-DLCI statistics.

The statistics for a frame relay DLCI. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanFrPvcStatsTable entry.

This object identifies the source of the data that this wanFrPvcStatsEntry analyzes. This source can be any pvcEntry associated with a frame relay interface on this device. In order to identify a particular DLCI, this object shall identify the instance of the frame relay pvcIndex object, defined in the PVCCONFIG-MIB.

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of frames seen coming from the far end of the link on this DLCI.

The total number of frames seen coming from the near end of the link on this DLCI.

The sum of octets from all frames seen originating from the far end of the link on this DLCI.

The sum of octets from all frames seen originating from the near end of the link on this DLCI.

The number of frames see coming form the far end of the link with the FECN bit set on this DLCI.

The number of frames seen coming from the far end of the link with the BECN bit set on this DLCI.

The number of frames see coming form the near end of the link with the FECN bit set.

The number of frames seen coming from the near end of the link with the BECN bit set on this DLCI.

The number of frames seen coming from the far end of the link with the DE bit set on this DCLI.

The number of frames seen coming from the near end of the link with the DE bit set on this DLCI.

The total amount of time in one-hundreds of a second that the probe is sure this LCI was active, i.e., the total time the value of wanFrPvcStatsState was equal to up(1). A value of less than the age of this entry does not necessarily mean that this LCI was down. It only means the probe was not certain it was up. Note: the sum of wanFrPvcStatsUpTime and wanFrPvcStatsDownTime may be less than the age of this entry. In this case, the unaccounted for time is the time the probe was uncertain of the state of this DLCI, i.e., the total time the value of wanFrPvcStatsState was unknown(3).

The total amount of time in one-hundreds of a second that the probe is sure this LCI was down, i.e., the total time the value of wanFrPvcStatsState was equal to down(3). A value of less than the age of this entry does not necessarily mean that this LCI was up at some point. It only means the probe was not certain it was down. Note: the sum of wanX25PvcStatsUpTime and wanFrPvcStatsDownTime may be less than the age of this entry. In this case, the unaccounted for time is the time the probe was uncertain of the state of this DLCI, i.e., the total time the value of wanFrPvcStatsState was unknown(3).

The current state of this DLCI as inferred by the probe. A value of up(2) means the DLCI is active. A value of down(2) means the DLCI is inactive. And a value of unknown(3) means the probe cannot currently infer the state. Enumeration: 'down': 2, 'unknown': 3, 'up': 1.

The count of the number of times the wanFrPvcStatsState has gone from up(1) to down(2) or vice versa. The number of times wanFrPvcStatsState goes to unknown(3) is not counted. However, if the value goes from up(1) to unknown(3) and then to down(2) should be counted as 1. Likewise going from down(2) to unknown(3) and then to up(3) should be counted as 1.

The entity that configured this entry.

The status of this wanFrPvcStatsTable entry.

AAL/5 per-VPI/VCI statistics.

The statistics for a AAL-5 VCI/VPI. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The value of this object uniquely identifies this wanAal5PvcStatsTable entry.

This object identifies the source of the data that this wanAal5StatsEntry analyzes. This source can be any pvcEntry that is associated with an ATM interface on this device. In order to identify a particular VPI/VCI, this object shall identify the instance of the pvcIndex object, defined in the PVCCONFIG-MIB.

The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of frames dropped; it is just the number of times this condition has been detected.

The total number of cells for seen coming from the far end of the link on this VPI/VCI.

The total number of cells seen coming from the near end of the link on this VPI/VCI.

The total number of AAL-5 PDUs seen coming from the far end of the link on this VPI/VCI.

The total number of AAL-5 PDUs seen coming from the near end of the link on this VPI/VCI.

The sum of octets from all AAL-5 PDUs seen originating from the far end of the link on this VCI/VPI.

The sum of octets from all AAL-5 PDUs seen originating from the near end of the link on this VPI/VCI.

The total number of cells with the CLP bit set seen coming from the far end of the link on this VCI/VPI.

The total number of cells with the CLP bit set seen coming from the near end of the link on this VCI/VPI.

The total number of AAL-5 PDUs with CRC errors seen coming from the far end of the link on this VCI/VPI.

The total number of AAL-5 PDUs with CRC errors seen coming from the near end of the link on this VPI/VCI.

The number of AAL5 SDUs from the far end of the link that were too large on this VPI/VCI.

The number of AAL5 SDUs from the near end of the link that were too large on this VPI/VCI.

The total amount of time in one-hundreds of a second that the probe is sure this LCI was active, i.e., the total time the value of wanAal5PvcStatsState was equal to up(1). A value of less than the age of this entry does not necessarily mean that this VPI/VCI was down. It only means the probe was not certain it was up. Note: the sum of wanAal5PvcStatsUpTime and wanAal5PvcStatsDownTime may be less than the age of this entry. In this case, the unaccounted for time is the time the probe was uncertain of the state of this VPI/VCI, i.e., the total time the value of wanAal5PvcStatsState was unknown(3).

The total amount of time in one-hundreds of a second that the probe is sure this LCI was down, i.e., the total time the value of wanAal5PvcStatsState was equal to down(3). A value of less than the age of this entry does not necessarily mean that this VPI/VCI was up at some point. It only means the probe was not certain it was down. Note: the sum of wanAal5PvcStatsUpTime and wanAal5PvcStatsDownTime may be less than the age of this entry. In this case, the unaccounted for time is the time the probe was uncertain of the state of this VPI/VCI, i.e., the total time the value of wanAal5PvcStatsState was unknown(3).

The current state of this VPI/VCI as inferred by the probe. A value of up(2) means the LCI is active. A value of down(2) means the VPI/VCI is inactive. And a value of unknown(3) means the probe cannot currently infer the state. Enumeration: 'down': 2, 'unknown': 3, 'up': 1.

The count of the number of times the wanAal5PvcStatsState has gone from up(1) to down(2) or vice versa. The number of times wanAal5PvcStatsState goes to unknown(3) is not counted. However, if the value goes from up(1) to unknown(3) and then to down(2) should be counted as 1. Likewise going from down(2) to unknown(3) and then to up(3) should be counted as 1.

The entity that configured this entry.

The status of this wanAal5PvcStatsTable entry.

T1/E1 signaling statistics.

Statistics for a particular T1/E1 interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanT1E1StatsDropEvents during the interval.

The change in value of wanT1E1StatsInFrames during the interval.

The change in value of wanT1E1StatsOutFrames during the interval.

The change in value of wanT1E1StatsInOctets during the interval.

The change in value of wanT1E1StatsOutOctets during the interval.

The change in value of wanT1E1StatsESs during the interval.

The change in value of wanT1E1StatsSESs during the interval.

The change in value of wanT1E1StatsSEFSs during the interval.

The change in value of wanT1E1StatsOOFs during the interval.

The change in value of wanT1E1StatsUASs during the interval.

The change in value of wanT1E1StatsCSSs during the interval.

The change in value of wanT1E1StatsPCVs during the interval.

The change in value of wanT1E1StatsLESs during the interval.

The change in value of wanT1E1StatsBESs during the interval.

The change in value of wanT1E1StatsDMs during the interval.

The change in value of wanT1E1StatsLCVs during the interval.

The change in value of wanT1E1StatsLOFSs during the interval.

The change in value of wanT1E1StatsLOSs during the interval.

The change in value of wanT1E1StatsRAIs during the interval.

The change in value of wanT1E1StatsAISs during the interval.

The change in value of wanT1E1StatsTS16AISs during the interval.

The change in value of wanT1E1StatsLOMFs during the interval.

The change in value of wanT1E1StatsFarLOMFs during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

The statistics for a V-series interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanVSeriesStatsDropEvents during the interval.

The change in value of wanVSeriesStatsInFrames during the interval.

The change in value of wanVSeriesStatsOutFrames during the interval.

The change in value of wanVSeriesStatsInOctets during the interval.

The change in value of wanVSeriesStatsOutOctets during the interval.

The change in value of wanVSeriesStatsInFCSs during the interval.

The change in value of wanVSeriesStatsOutFCSs during the interval.

The change in value of wanVSeriesStatsInOverruns during the interval.

The change in value of wanVSeriesStatsOutOverruns during the interval.

The change in value of wanVSeriesStatsInterruptedFrames during the interval.

The change in value of wanVSeriesStatsInAbortedFrames during the interval.

The change in value of wanVSeriesStatsOutAbortedFrames during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

HSSI interface statistics.

The statistics for a HSSI interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanHssiStatsDropEvents during the interval.

The change in value of wanHssiStatsInFrames during the interval.

The change in value of wanHssiStatsOutFrames during the interval.

The change in value of wanHssiStatsInOctets during the interval.

The change in value of wanHssiStatsOutOctets during the interval.

The change in value of wanHssiStatsRxLongFrames during the interval.

The change in value of wanHssiStatsRxCrcErrors during the interval.

The change in value of wanHssiStatsRxOverruns during the interval.

The change in value of wanHssiStatsRxAborts during the interval.

The change in value of wanHssiStatsTxAborts during the interval.

The change in value of wanHssiStatsTxUnderruns during the interval.

The change in value of wanHssiStatsTxRingErrors during the interval.

The change in value of wanHssiStatsRxRingOverruns during the interval.

The change in value of wanHssiStatsTxRingErrors during the interval.

The change in value of wanHssiStatsPortOpErrors during the interval.

The change in value of wanHssiStatsTxCmplProcessings during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

T3/E3 signaling statistics

Statistics for a T3/E3 interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanT3E3StatsDropEvents during the interval.

The change in value of wanT3E3StatsInFrames during the interval.

The change in value of wanT3E3StatsOutFrames during the interval.

The change in value of wanT3E3StatsInOctets during the interval.

The change in value of wanT3E3StatsOutOctets during the interval.

The change in value of wanT3E3StatsPESs during the interval.

The change in value of wanT3E3StatsPSESs during the interval.

The change in value of wanT3E3StatsOOFs during the interval.

The change in value of wanT3E3StatsSEFs during the interval.

The change in value of wanT3E3StatsUASs during the interval.

The change in value of wanT3E3StatsLCVs during the interval.

The change in value of wanT3E3StatsPCVs during the interval.

The change in value of wanT3E3StatsLESs during the interval.

The change in value of wanT3E3StatsCCVs during the interval.

The change in value of wanT3E3StatsCESs during the interval.

The change in value of wanT3E3StatsCSESs during the interval.

The change in value of wanT3E3StatsRAIs during the interval.

The change in value of wanT3E3StatsAISs during the interval.

The change in value of wanT3E3StatsLOFs during the interval.

The change in value of wanT3E3StatsLOSs during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

ATM signaling statistics.

The statistics for an ATM interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In an ATM network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanAtmStatsDropEvents during the interval.

The change in value of wanAtmStatsInCells during the interval.

The change in value of wanAtmStatsOutCells during the interval.

The change in value of wanAtmStatsInCLP1 during the interval.

The change in value of wanAtmStatsOutCLP1 during the interval.

The change in value of wanAtmStatsConnectionEvents during the interval.

The change in value of wanAtmStatsErroredPDUs during the interval.

The change in value of wanAtmStatsSetupAttempts during the interval.

The change in value of wanAtmStatsInRoutesUnavailable during the interval.

The change in value of wanAtmStatsOutRoutesUnavailable during the interval.

The change in value of wanAtmStatsInResourcesUnavailable during the interval.

The change in value of wanAtmStatsOutResourcesUnavailable during the interval.

The change in value of wanAtmStatsInUnsuccessfulCalls during the interval.

The change in value of wanAtmStatsOutUnsuccessfulCalls during the interval.

The change in value of wanAtmStatsInIncorrectMsgs during the interval.

The change in value of wanAtmStatsOutIncorrectMsgs during the interval.

The change in value of wanAtmStatsInPartyEvents during the interval.

The change in value of wanAtmStatsOutPartyEvents during the interval.

The change in value of wanAtmStatsInExpiries during the interval.

The change in value of wanAtmStatsOutExpiries during the interval.

The change in value of wanAtmStatsInRestartErrors during the interval.

The change in value of wanAtmStatsOutRestartErrors during the interval.

The change in value of wanAtmStatsInSVCs during the interval.

The change in value of wanAtmStatsOutSVCs during the interval.

The change in value of wanAtmStatsInOCDs during the interval.

The change in value of wanAtmStatsOutOCDs during the interval.

The change in value of wanAtmStatsInLOCs during the interval.

The change in value of wanAtmStatsOutLOCs during the interval.

The change in value of wanAtmStatsInLOFs during the interval.

The change in value of wanAtmStatsOutLOFs during the interval.

The change in value of wanAtmStatsInLOPs during the interval.

The change in value of wanAtmStatsOutLOPs during the interval.

The change in value of wanAtmStatsInLOSs during the interval.

The change in value of wanAtmStatsOutLOSs during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

X.25 Packet layer statistics.

The statistics for an X.25 interface across all LCIs. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In a X.25 network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanX25StatsDropEvents during the interval.

The change in value of wanX25StatsInFrames during the interval.

The change in value of wanX25StatsOutFrames during the interval.

The change in value of wanX25StatsInOctets during the interval.

The change in value of wanX25StatsOutOctets during the interval.

The change in value of wanX25StatsInRejects during the interval.

The change in value of wanX25StatsOutRejects during the interval.

The change in value of wanX25StatsInAttempts during the interval.

The change in value of wanX25StatsOutAttempts during the interval.

The change in value of wanX25StatsInFailures during the interval.

The change in value of wanX25StatsOutFailures during the interval.

The change in value of wanX25StatsProviderClears during the interval.

The change in value of wanX25StatsInResets during the interval.

The change in value of wanX25StatsOutResets during the interval.

The change in value of wanX25StatsProviderResets during the interval.

The change in value of wanX25StatsInAccusedErrors during the interval.

The change in value of wanX25StatsOutAccusedErrors during the interval.

The change in value of wanX25StatsInInterrupts during the interval.

The change in value of wanX25StatsOutInterrupts during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

Frame Relay statistics.

The statistics for a frame relay interface across all DLCIs. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In a frame relay network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanFrStatsDropEvents during the interval.

The change in value of wanFrStatsInFrames during the interval.

The change in value of wanFrStatsOutFrames during the interval.

The change in value of wanFrStatsInOctets during the interval.

The change in value of wanFrStatsOutOctets during the interval.

The change in value of wanFrStatsInFECSs during the interval.

The change in value of wanFrStatsOutFECNs during the interval.

The change in value of wanFrStatsInBECNs during the interval.

The change in value of wanFrStatsOutBECNs during the interval.

The change in value of wanFrStatsInDEs during the interval.

The change in value of wanFrStatsDOutDEs during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

AAL/5 statistics.

The statistics for a AAL/5 interface. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on. In an ATM network, there are many far ends of the link, but they shall be logically grouped into one end in this table.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanAal5StatsDropEvents during the interval.

The change in value of wanAal5StatsInCells during the interval.

The change in value of wanAal5StatsOutCells during the interval.

The change in value of wanAal5StatsInPDUs during the interval.

The change in value of wanAal5StatsOutPDUs during the interval.

The change in value of wanAal5StatsInOctets during the interval.

The change in value of wanAal5StatsOutOctets during the interval.

The change in value of wanAal5StatsInCLP1 the interval.

The change in value of wanAal5StatsOutCLP1 during the interval.

The change in value of wanAal5StatsInCRCs during the interval.

The change in value of wanAal5StatsOutCRCs during the interval.

The change in value of wanAal5StatsInOversizedSDUs during the interval.

The change in value of wanAal5StatsOutOversizedSDUs during the interval.

The change in value of wanAal5StatsInSVCs during the interval.

The change in value of wanAal5StatsOutSVCs during the interval.

The best estimated of the mean AAL-5 layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean AAL-5 layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

PPP in HDLC service statistics.

The statistics for a PPP in HDLC service. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanPppStatsDropEvents during the interval.

The change in value of wanPppStatsInFrames during the interval.

The change in value of wanPppStatsOutFrames during the interval.

The change in value of wanPppStatsInOctets during the interval.

The change in value of wanPppStatsOutOctets during the interval.

The change in value of wanPppStatsInBadAddresses during the interval.

The change in value of wanPppStatsOutBadAddresses during the interval.

The change in value of wanPppStatsInBadControls during the interval.

The change in value of wanPppStatsOutBadControls during the interval.

The change in value of wanPppStatsInLongFrames during the interval.

The change in value of wanPppStatsOutLongFrames during the interval.

The change in value of wanPppStatsInBadFCSs during the interval.

The change in value of wanPppStatsOutBadFCSs during the interval.

The best estimated of the mean physical layer network utilization of traffic coming from the far end of the link in hundreds of a percent.

The best estimated of the mean physical layer network utilization of traffic coming from the near end of the link in hundreds of a percent.

X.25 per LCI statistics.

The statistics for a X.25 LCI. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanX25PvcStatsDropEvents during the interval.

The change in value of wanX25PvcStatsInFrames during the interval.

The change in value of wanX25PvcStatsOutFrames during the interval.

The change in value of wanX25PvcStatsInOctets during the interval.

The change in value of wanX25PvcStatsOutOctets during the interval.

The change in value of wanX25PvcStatsInResets during the interval.

The change in value of wanX25PvcStatsOutResets during the interval.

The change in value of wanX25PvcStatsProviderResets during the interval.

The change in value of wanX25PvcStatsInAccusedErrors during the interval.

The change in value of wanX25PvcStatsOutAccusedErrors during the interval.

The change in value of wanX25PvcStatsInInterrupts during the interval.

The change in value of wanX25PvcStatsOutInterrupts during the interval.

The change in value of wanX25PvcStatsUpTime during the interval.

The change in value of wanX25PvcStatsDownTime during the interval.

The change in value of wanX25PvcStatsStateChanges during the interval.

The best estimated of the mean utilization of traffic on this LCI coming from the far end of the link in hundreds of percent of the CIR.

The best estimated of the mean utilization of traffic on this LCI coming from the near end of the link in hundreds of percent of CIR.

Frame Relay per-DCLI statistics.

The statistics for a frame relay DLCI. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanFrPvcStatsDropEvents during the interval.

The change in value of wanFrPvcStatsInFrames during the interval.

The change in value of wanFrPvcStatsOutFrames during the interval.

The change in value of wanFrPvcStatsInOctets during the interval.

The change in value of wanFrPvcStatsOutOctets during the interval.

The change in value of wanFrPvcStatsInFECNs during the interval.

The change in value of wanFrPvcStatsOutFECNs during the interval.

The change in value of wanFrPvcStatsInBECNs during the interval.

The change in value of wanFrPvcStatsOutBECNs during the interval.

The change in value of wanFrPvcStatsInDEs during the interval.

The change in value of wanFrPvcStatsOutDEs during the interval.

The change in value of wanFrPvcStatsUpTime during the interval.

The change in value of wanFrPvcStatsDownTime during the interval.

The change in value of wanFrPvcStatsStateChanges during the interval.

The best estimated of the mean utilization of traffic on this DLCI coming from the far end of the link in hundreds of percent of the CIR.

The best estimated of the mean utilization of traffic on this DLCI coming from the near end of the link in hundreds of percent of CIR.

AAL-5 per-VPI/VCI statistics.

The statistics for a AAL-5 VCI/VPI. The near end of the link refers to the side of the link that the probe is monitoring. The far end is the side the probe is not on.

The history of which this entry is a port. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collection the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.

The change in value of wanAal5PvcStatsDropEvents during the interval.

The change in value of wanAal5PvcStatsInCells during the interval.

The change in value of wanAal5PvcStatsOutCells during the interval.

The change in value of wanAal5PvcStatsInPDUs during the interval.

The change in value of wanAal5PvcStatsOutPDUs during the interval.

The change in value of wanAal5PvcStatsInOctets during the interval.

The change in value of wanAal5PvcStatsOutOctets during the interval.

The change in value of wanAal5PvcStatsInCLP1 during the interval.

The change in value of wanAal5PvcStatsOutCLP1 during the interval.

The change in value of wanAal5PvcStatsInCRCs during the interval.

The change in value of wanAal5PvcStatsOutCRCs during the interval.

The change in value of wanAal5PvcStatsInOversizedSDUs during the interval.

The change in value of wanAal5PvcStatsOutOversizedSDUs during the interval.

The change in value of wanAal5PvcStatsUpTime during the interval.

The change in value of wanAal5PvcStatsDownTime during the interval.

The change in value of wanAal5PvcStatsStateChanges during the interval.

The best estimated of the mean utilization of traffic on this VPI/VCI coming from the far end of the link in hundreds of percent of the CIR.

The best estimated of the mean utilization of traffic on this VPI/VCI coming from the near end of the link in hundreds of percent of CIR.