Handling An Imc Link Fault; Handling A Parity Error Fault - Nortel DMS-100 Series Maintenance Manual

9-8 Trouble isolation and correction

Handling an IMC link fault

When the intermodule communication (IMC) link audit detects data loss or
damage to the messages over IMC links, the SMS becomes ISTb. The
system generates a PM128 log. Enter the command string
the response includes the following statement:
NON-CRITICAL HARDWARE FAULT
Operating company personnel must perform the following steps:
1 Test both units to confirm the audit result.
2 BSY and offline the inactive unit and replace the defective cards on the
3 RTS inactive unit.
The fault is in the active unit if:
If the RTS of the inactive unit is successful, perform the following steps:
1 SWACT of the units.
2 BSY the new inactive unit.
3 Test the inactive unit.
4 Offline (OFFL) the unit with the defective cards. Replace the defective
5 RTS inactive unit.
The problem is in the backplane if card replacement does not remove the
fault.

Handling a parity error fault

The parity audit was introduced in BCS28. If the parity audit detects a
parity fault, the system places the defective unit OOS. Operating company
personnel manually test and RTS the unit. In BCS31, the SMS reports a
parity fault to the CM and the CM decides the action to take. This decision
depends on the type of parity error and the state of the SMS units. In most
occurrences, user can correct the fault without a loss of service.
The following sections provide background on types of parity faults and a
summary of types of actions that the CM takes. The last sections highlight
297-8231-550 Standard 09.01 August 1998
reset the SMS
load the SMS again
list, NT6X69 or MX77.
the node remains ISTb for more than 5 min
the response to the
>QUERYPM FLT
cards with good cards.
>QUERYPM FLT
command does not change
,