Appendix F - Alarms Troubleshooting HSL Alarms Troubleshooting
HSL Alarms Troubleshooting
Table 106: HSL alarms troubleshooting table
Recommended Troubleshooting Procedure
Copper mismatch connection;
There is no Ethernet service and in-
band management traffic.
Applicable on HSL configured in -O
(Office) mode.
The ML device with HSL in -O (Office) mode can
detect and report that this HSL is terminated on
multiple -R (Customer) destinations.
The table in the Modem Ports pane provides unique
identification (Serial Number) of each copper line
termination. The table column - "Linked NE"
provides Serial Number (s) of the discovered linked
by HSL ML device system(s).
To resolve the problem:
Re-connect each copper line with different
Serial Number discovered on distant end. MLP
provides Serial Number discovery immediately
after synchronization.
To work around the problem:
Reconfigure HSL on local side to exclude
incorrectly terminated copper lines from HSL.
De-calibrate (Cancel Calibration) the HSL; then
delete MLPs from HSL, re-calibrate HSL once
more.
High Speed Link is Up, but not
calibrated yet.
Up, not calibrated status can appear
when the system is powered for the
first time or when you click the
Cancel Calibration button in HSL
pane.
Applicable on HSL configured in -O
(Office) mode.
In High Speed Link pane, click the Calibrate
button to calibrate the HSL (allow a few minutes to
complete the process).
HSL is down;
Temporary alarm resulting from HSL
initialization or recovery process
(secondary state is HUNT, CALIB or
RCVRY).
Applicable on HSL configured in -O
(Office) mode.
There is a temporary alarm. Verify in the HSL pane,
Details section, that after a few minutes the HSL
status is changed to one of the following:
UP with the appropriate alarm or no alarms;
HSLDIAG with the appropriate alarm;
HSLFLT with the appropriate alarm.
If problem is not resolved, check if linked by HSL
ML device is powered up, correctly installed (copper
loop connections), not alarmed and MLP and HSL
are configured properly.
To Next Page