(Page 30 of 39 in this chapter) Version
dsx1CurrentUASs
Syntax
- Gauge
Access
- Read-only
OID
- p.7.1.5.n, where n = the index number of the DS1 interface.
Description
- Number of Unavailable Seconds.
- 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. If the condition leading to the failure was immediately preceded by one or more contiguous SESs (dsx1CurrentSESs), then the DS1 interface unavailability starts from the onset of these 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.
- 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 dsx1IntervalSESs and dsx1IntervalUASs objects will return differing values if the first get occurs during the first few seconds of the window. This is an unavoidable side-effect of selecting the managed objects defined by RFC 2495.
Configuration
- Not applicable.
(Page 30 of 39 in this chapter) Version
Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com
Copyright © 2000, Natural MicroSystems, Inc. All rights
reserved.