# dsx1CurrentUASs

Number of unavailable seconds.

#### Syntax

Gauge

#### Access

Read-only

#### OID

p.7.1.5.n, where n = the index number of the DS1 interface.

#### Details

Unavailable seconds (UAS) are calculated by counting the number of seconds the interface is unavailable. The DS1 interface is unavailable from the onset of 10 contiguous SESs or the onset of the condition leading to a failure. If the condition leading to the failure was immediately preceded by one or more contiguous SESs (dsx1CurrentSESs), the DS1 interface unavailability starts from the onset of these SESs.

Once unavailable, and if... | The DS1 interface becomes available at the...
No failure is present | Onset of 10 contiguous seconds with no SESs.
A failure is present | 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.

All DS1 error counts are incremented while the DS1 interface is deemed available. While the interface is deemed unavailable, the only count that is incremented is UASs.

A special case exists when the 10 or more second period crosses the 900-second statistics window boundary, because the severely errored second and unavailable second counters must be adjusted when the unavailable signal state is entered. Successive gets of the affected get occur during the first few seconds of the window. This is an unavoidable side effect of selecting the managed objects defined by RFC 2495.