Carrier Problems - Lucent Technologies MERLIN LEGEND Release 5.0 Maintenance And Troubleshooting Manual

MERLIN LEGEND Communications System Release 5.0
Maintenance and Troubleshooting 555-650-140
Control Unit Problems

Carrier Problems

For a link shutdown, do the following:
Suspend MERLIN LEGEND alarming for the CTI link.

If Step 1 of the link shutdown is not performed, then the MERLIN
LEGEND may generate alarms about the CTI link while under
maintenance. See the MERLIN LEGEND Network Manager's Guide for
detailed instructions on this procedure.
Prevent new CTI link traffic.

If Step 2 is not performed before working on the CTI link, an application
may get confused. For example, if an application sent a service request
(such as Make Call) but the CTI link is taken down for maintenance
before the MERLIN LEGEND sends a reply, the application will think the
request failed even if it succeeded. In contrast, if this step is performed,
the application will immediately receive a failure reply. See the MERLIN
LEGEND Network Manager's Guide for detailed instructions on the
Block, Offline, and mloam commands.
Wait for CTI link traffic to subside.

If the Offline or mloam command was used in Step 2, skip to Step 4.This
step applies only if the Block command was used in Step 2.
Determine when traffic has stopped. On the NetWare server, start the
mloam or wmloam tool, then go to the Link Status screen. View the line
CTI Link Msg. Rate. If the value there is 0, then traffic on the link has
stopped. Refer to the Network Manager's Guide for details.
Unplug the CTI link, or perform appropriate maintenance.

Carrier Problems
Typical carrier problems include power supply failure, sudden failure of one or
more modules, or system problems that cannot be isolated to a specific module.
If you find a problem with the carrier, it must be replaced; carriers cannot be
repaired in the field.
Issue 1
June 1997
Page 4-132