Maintenance and Troubleshooting
Flowchart
From 3
Use loopbacks to isolate alarm condition
Alarm Internal?
No
Contact distant end - have them start troubleshooting
Alarm Clears?
No
3A
|
|
| Check following most likely |
|
|
|
|
|
|
|
|
| causes/correct as necessary: |
|
|
|
|
|
|
|
|
|
|
| Alarm Clears? | ||||
Yes |
|
|
| ||||||
|
|
|
| ||||||
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
| No |
| |
|
|
|
|
| |||||
|
|
|
| ||||||
|
|
|
| LOF/LOP/LOCD check Sync | |||||
|
|
|
|
|
|
|
|
|
|
Alarm Clears ?
Yes 3B
No
3A
Yes
Yes
Review Alarm Summary and
System log- call Customer
Service with pertinent information
3B
Return to | 3 |
Figure 8-5: NIM Major Alarm Troubleshooting Flowchart
Broadmore 1750 - Release 4.6 |