Nortel DMS-100 Series Maintenance Manual page 377

–The following ISTb is present: a soft parity fault was
>QUERYPM FLT
detected in program store of 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 busies the SMS. The SMS in the
BSY state cannot process calls. The CM sets the active unit as ISTb.
User action
If the inactive unit is OOS, or cannot take over call processing, the SMS
drops all call processing. The SMS drops call processing when the user
busies the unit. To get the inactive unit to process calls, the user can attempt
to return the unit to service.
PM181—Soft parity fault data 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 data store
Other problem indicators include the following:
PM128—The SMS is set ISTb, with the inactive unit set as SysB.
PM128 JUL23 23:29:16 5561 TBL ISTb SMS 0
Node: ISTb, (Inact OOS) From InSv
Unit 0 Inact:
Unit 1 Act: InSv
PM189—The inactive unit of the SMS has a fault in program store.
PM189 JUL23 23:29:17 5561 INFO PM SW INFORMATION REPORT
SMS 0 Unit 0:
TASKID: 00370037 PARAUDT, TIME:
COMID: FF NILCID
TEXT: softdat 00 00 57 F6 00 00
>
>QUERYPM FLT
store of memory.
The SysB means that either the CM takes the inactive unit OOS, or the CM
performed a SWACT on the SMS. If the CM performed a SWACT the CM
set the new inactive unit OOS.
Action by the CM
The CM sets the inactive unit as SysB. If the defective unit was the active
unit, the CM will perform a SWACT and BSY the new inactive unit. At this
point, the CM will try to recover the BSY unit without user interruption.
InSv, Unit 1, Inact:
SysB (Parity errors detected) from InSv
Inact
–SysB reason: a soft parity fault was detected in data
DMS-100 Family SMS Maintenance Manual XPM10 and up
Trouble isolation and correction 9-13
InSv
22:29:16.68