Nortel DMS-100 Series Maintenance Manual page 375

Other problem indicators include the following:
PM128—The SMS is set to ISTb, with the active unit as ISTb from
InSv.
PM128 JUL23 23:29:16 5561 TBL ISTb SMS 0
Node: ISTb, (Inact OOS) From InSv
Unit 0 Act: IsTb (Parity errors detected) from InSv
Unit 1 Inact:
PM 189—The active unit of the SMS has a hard fault.
PM189 JUL 23 23:29:17 5561 INFO PM SW INFORMATION REPORT
SMS 0 Unit 0:
TASKID: 00370037 PARAUDT, TIME:
COMID: FF NILCID
TEXT: hard_flt 00 00 57 F6 00 00
>QUERYPM FLT
The following ISTb is present: the system detected a hard parity fault in
memory.
Action by the CM
In this example, the inactive unit is not InSv. The CM cannot take the
defective unit OOS because this action BSYs the SMS. The SMS in the
BSY state is not able to process calls. The CM sets the active unit as ISTb.
User action
Operating company personnel follow the same procedure as the first
example, but when the unit is busied, the SMS drops all call processing. To
avoid the busy unit, the user can try to force the inactive unit to and process
calls. To force the inactive unit the user returns the inactive unit to service.
PM181—Soft parity fault program store, both units INSV
The following is an example of a PM181 log:
PM181 JUL23 23:29:16 5561 INFO SMS 0 Unit 0
Node: ISTb, Unit 0 Act:
Parity audit detected soft parity fault in program store
Other problem indicators include the following:
PM128—The SMS is set ISTb, with the inactive unit OOS.
PM128 JUL23 23:29:16 5561 TBL ISTb SMS 0
Node: ISTb, (Inact OOS) From InSv
Unit 0 Inact :
Unit 1 Act: InSv
OOS
Act
InSv, Unit 1, Inact:
SysB (Parity errors detected) from InSv
DMS-100 Family SMS Maintenance Manual XPM10 and up
Trouble isolation and correction 9-11
22:29:16.68
InSv