Errored Seconds Monitor Locations |
|
|
|
|
| ||||||||||
|
|
|
|
|
|
|
|
| HRE |
| |||||
|
|
|
|
|
| ES |
|
| ES | Loop 1 | ES |
|
| ES | Loop 1 |
|
|
|
|
|
|
|
|
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
| |||||
To |
|
|
|
|
|
|
| ||||||||
|
|
|
|
|
|
|
|
|
| ||||||
|
|
|
|
|
|
|
|
|
| ||||||
Network |
|
|
|
|
|
| ES | Loop 2 | ES |
|
| ES | Loop 2 | ||
|
|
|
|
|
|
|
|
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Severely Errored Seconds Monitor Locations |
|
| ||||||||||
|
|
|
|
| HRE |
|
| |||||
|
|
|
| SES |
|
| Loop 1 |
|
|
|
| Loop 1 |
|
|
|
|
| SES | SES |
|
| SES | |||
|
|
|
|
|
|
|
|
| ||||
To |
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
| ||||
|
|
|
|
|
|
|
|
| ||||
Network |
|
|
|
|
|
|
|
|
| |||
SES | Loop 2 | SES |
|
| SES | Loop 2 | ||||||
|
|
|
|
|
|
|
| |||||
|
|
|
|
|
|
|
| |||||
|
|
|
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
ES |
|
| ES |
|
| DS1 | |
ES |
|
|
|
|
|
| |
|
|
| |
|
|
|
|
|
|
|
|
| |||
|
|
| SES |
|
|
| |
SES |
|
| DS1 |
|
|
| |
SES |
|
|
|
|
|
| |
|
|
| |
|
|
|
|
|
|
|
|
To Customer
To
Customer
Unavailable Seconds Monitor Locations
|
|
|
|
|
| HRE |
| ||
|
|
|
| ||||||
|
|
|
|
|
|
| |||
| UAS |
| UAS | Loop 1 | UAS |
|
| UAS | Loop 1 |
|
|
|
|
|
| ||||
|
|
|
|
|
| ||||
To |
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
Network |
|
| UAS | Loop 2 | UAS |
|
| UAS | Loop 2 |
|
|
|
| ||||||
|
|
|
|
|
|
| |||
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
UAS |
| UAS |
| DS1 | |
| ||
|
| |
UAS |
|
|
|
| |
|
| |
|
|
|
|
|
|
To Customer
Figure 4. ES, SES, and UAS Monitor Locations
Severely Errored Seconds (SES) Alarm
The locations shown in Figure 4 are monitored for Severely Errored Seconds and counts are maintained for each location. If any of these counts exceed the SES programmed threshold (see Tables 1 and 2) an alarm will be generated. This alarm threshold and the alarm type (minor or major) can be programmed by setting switches S1 and S2 (Figure 2) to the appropriate positions according to Tables 1 and 2. The alarm thresholds are for the
Unavailable Seconds (UAS) Alarm
The locations shown in Figure 4 are monitored for unavailable seconds. Seconds and counts are maintained for each location. If any of these counts exceed the UAS programmed threshold (see Tables 1 and 2), an alarm will be generated. This alarm threshold and the alarm type (major or critical) can be programmed by setting switches S1 or S2 (Figure 2) to the appropriate positions according to Tables 1 and 2. The alarm thresholds are for the
registers only, and the
HFAC Alarm Outputs
If an HFAC is present in the shelf, alarm outputs are available on the backplane wirewrap pins corresponding to the HFAC slot (see Figure 5). These outputs are dry contact relay connections and provide normally open, normally closed and common connection points for alarm monitoring equipment. Alarm connection points corresponding to critical major, and minor alarms (both visible and audible) are provided. These alarms are generated by the HFAC as a result of processed data collected from the
Alarm outputs presented on these pins are programmable and can be provisioned in the HFAC Options Setup screen (see Options Setup screen), or using the HFAC dip switch settings (see Tables 1, 2, and 3). Alarm severity can be provisioned for alarms
| 5 |