Table 11. HDSL Transmission and Application Interface Alarms | |
|
|
Alarm | Description |
|
|
HDSL Alarms | HDSL alarms include: |
Margin (MAR) | Margin has fallen below threshold set for the HDSL interface. |
Errored Seconds (ES) | Errored seconds count has exceeded threshold set for the HDSL interface. |
Loss of Sync Word | Loss of sync word at the HDSL interface. Remains active during restart, but not a cold start. |
(LOSW) |
|
G.703 Alarms | G.703 alarms include: |
Loss of Signal (LOS) | Loss of signal at the G.703 input. |
Loss of Frame Alignment | Loss of frame alignment at the G.703 input. |
(LFA) |
|
Receive Alarm Indication | Alarm indication signal (unframed all ones) received at the G.703 input. |
Signal (AIS) |
|
Remote Alarm Indication | Remote alarm indication signal received at the G.703 input (through |
Signal (RAI) |
|
Loss of Clock (LOC) | Applies to loss of external clock when EXT timing is used. The external clock was lost for the |
| previous second. This alarm is reset when the clock is active again. |
|
|
An HDSL system maintains several diagnostic loopback configurations, both toward and away from the local unit, which can be used to verify proper transmission of test data through the local unit, the HDSL facility, and the remote unit. Figure 8 on page 19 shows all possible loopback paths. Table 12 on page 20 lists available loopbacks.
During loopbacks the system generates an Alarm Indication Signal (AIS) past the loopback point toward the far unit. Loopbacks can be activated from the LOC (local) and REM (remote)
The system reverts to normal transmission of payload data after the specified timeout period has elapsed. If a timeout period is not specified, the loopback must be manually disengaged before normal transmission of data can resume.
Test loopbacks disrupt normal
LTU Interface |
| NTU Interface |
|
| |
HDSL | HDSL loop | HDSL |
| ||
Nx64k |
| Nx64k |
Figure 8. Loopback Operations
August 9, 2002 | 19 |