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.
Parsed from file agilent-wanstats.mib.txt
Company: None
Module: WANSTATS-MIB
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.
Parsed from file WANSTATS-MIB.mib
Module: WANSTATS-MIB
Vendor: Hewlett-Packard
Module: WANSTATS-MIB
[Automatically extracted from oidview.com]
wanT1E1StatsUASs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { wanT1E1StatsEntry 12 }
wanT1E1StatsUASs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { wanT1E1StatsEntry 12 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.1 | wanT1E1StatsIndex | 0 | 0 | The value of this object uniquely identifies this wanT1E1StatsTable entry. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.2 | wanT1E1StatsDataSource | 0 | 0 | This object identifies the source of the data that this wanT1E1StatsEntry analyzes. This source can be any DS1 or E1 interface o… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.3 | wanT1E1StatsDropEvents | 0 | 0 | The total number of events in which frames were dropped by the probe due to lack of resources. Note that this number is not nece… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.4 | wanT1E1StatsInFrames | 0 | 0 | The total number of frames seen originating from the far end of the link including errored frames. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.5 | wanT1E1StatsOutFrames | 0 | 0 | The total number of frames seen originating from the near end of the link including errored frames. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.6 | wanT1E1StatsInOctets | 0 | 0 | The sum of octets from all frames seen originating from the far end of the link including errored frames. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.7 | wanT1E1StatsOutOctets | 0 | 0 | The sum of octets from all frames seen originating from the near end of the link including errored frames. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.8 | wanT1E1StatsESs | 0 | 0 | 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 … |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.9 | wanT1E1StatsSESs | 0 | 0 | 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 Fra… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.10 | wanT1E1StatsSEFSs | 0 | 0 | An Severely Errored Framing Second is a second with one or more Out of Frame defects OR a detected AIS defect. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.11 | wanT1E1StatsOOFs | 0 | 0 | An OOF defect is the occurrence of a particular density of Framing Error events. For T1 links, an Out of Frame defect is declared… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.13 | wanT1E1StatsCSSs | 0 | 0 | A Controlled Slip Second is a one-second interval containing one or more controlled slips. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.14 | wanT1E1StatsPCVs | 0 | 0 | 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 ES… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.15 | wanT1E1StatsLESs | 0 | 0 | A Line Errored Second, according to T1M1.3, is a second in which one or more Line Code Violation error events were detected. While… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.16 | wanT1E1StatsBESs | 0 | 0 | A Bursty Errored Second (also known as Errored Second type B) is a second with fewer than 320 and more than 1 Path Coding Violati… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.17 | wanT1E1StatsDMs | 0 | 0 | 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 Minute… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.18 | wanT1E1StatsLCVs | 0 | 0 | A Line Coding Violation (LCV) is the occurrence of either a Bipolar Violation (BPV) or Excessive Zeroes (EXZ) Error Event. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.19 | wanT1E1StatsLOFs | 0 | 0 | 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 be… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.20 | wanT1E1StatsLOSs | 0 | 0 | For T1, the Loss Of Signal failure is declared upon observing 175 +/- 75 contiguous pulse positions with no pulses of either posi… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.21 | wanT1E1StatsRAIs | 0 | 0 | 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 Fa… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.22 | wanT1E1StatsAISs | 0 | 0 | The Alarm Indication Signal failure is declared when an AIS defect is detected at the input and the AIS defect still exists afte… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.23 | wanT1E1StatsTS16AISs | 0 | 0 | For E1 links, the TS16 Alarm Indication Signal failure is declared when time-slot 16 is received as all ones for all frames of tw… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.24 | wanT1E1StatsLOMFs | 0 | 0 | The Loss Of MultiFrame failure is declared when two consecutive multiframe alignment signals (bits 4 through 7 of TS16 of frame 0… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.25 | wanT1E1StatsFarLOMFs | 0 | 0 | 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 occasi… |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.26 | wanT1E1StatsOwner | 0 | 0 | The entity that configured this entry. |
| 1.3.6.1.4.1.11.2.3.7.6.1.5.1.8.1.1.1.1.27 | wanT1E1StatsStatus | 0 | 0 | The status of this wanT1E1StatsTable entry. |