Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual page 122

Permanent Errors
A permanent error is entered in the error logs when more than 50 percent of analog trunks in a
pool are maintenance-busy. When the maintenance-busy level falls below 50 percent, the system
automatically removes the permanent error.
Make sure that modules are not in a maintenance-busy state during a backup procedure.
Any module in a maintenance-busy state is recorded as such on the backup disk.
Maintenance-Busy Causes
The causes of maintenance-busy vary according to the type of trunk, as follows:
Ground-Start (GS) Trunks. The following events cause maintenance-busy on a ground-start
I
trunk:
– A seizure of the trunk is attempted that results in incomplete handshaking (or no loop
current) between the central office and the system. After four occurrences, the trunk is put
into a maintenance-busy state and a permanent error is logged.
– The CO fails to disconnect when the GS trunk is dropped by the system. After two
occurrences, the trunk is put into a maintenance-busy state and a permanent error is
logged.
Loop-Start (LS) Trunks. No loop current exists when the LS trunk is seized. The port is
I
marked maintenance-busy, and a permanent error is logged after four occurrences.
Tie Trunks. The following events cause maintenance-busy on a tie trunk:
I
– A seizure of an outgoing tie trunk fails.
– A transient error is reported. After four unsuccessful seizure attempts, the port is marked
maintenance-busy and the error becomes permanent.
– The central office fails to disconnect.
– A transient error is reported. After two occurrences, the port is marked maintenance-busy
and the error becomes permanent.
The test is not run on auto-out tie trunks.
Central Office and Private Network Problems
5
5
Trunk Errors
5-5