Nortel DMS 100 Series Maintenance Manual page 66

2-50 Maintenance overview
company personnel can check for associated logs, like the PM128, to
understand what actions the CM takes. This section provides examples of the
messages that associate with the PM181 and PM128 logs.
The RSC-M unit can be set ISTB with multiple reasons together. When a
QUERYPM FLT occurs at the MAP level, all of the ISTb reasons appear.
These reasons occurred on the unit and were not cleared.
Hard parity fault
parity fault to the CM, the system generates a PM181 log. This log notifies
operating company personnel:
•
•
To clear the ISTb and the parity fault, the user can perform a manual SWACT
and reload.
An example of a PM181 log report follows:
PM181 JUL23 23:29:16 7700 INFO RSC-M 0 Unit 0
Node: Istb, Unit0 Inact: ISTb, Unit1 Act: ISTb
Parity audit has detected a hard parity fault.
The system will autoload the unit during the next
XPM REX test window.
Monitor the system for maintenance and recovery.
Site Flr
RAL1 00
When a unit changes state to ISTb of UP RAM parity fault, the system
generates a PM128 log report. This log informs operating company personnel
the unit changed state.
An example of a PM128 log follows:
*PM128 MAY09 09:49:56 9000 TBL ISTB SMA2 1
Node: ISTb (Unit ISTb)
Unit0 Inact: InSv
Unit1
The system uses a command string QUERYPM FLT to display the faults on a
posted RSC-M. The following example MAP response shows a hard parity
fault is present in unit 1 of the posted XPM:
297-8223-550 Standard 04.02 November 2000
When the active unit of the RSC-M reports a hard
a parity fault occurred on the active unit and the unit was set ISTb
the CM reloads the unit during the next XPM REX test window
RPos Bay_id
C05 RSCM 00
Act: ISTb (UP RAM Parity)
Shf Description Slot
18 RSC-M : 000
EqPEC
3 MX77