Download DNP Messages Reference

Transcript
________________
Control Computer Messages
Report Alarm 1045
*
<YY-MM-DD> <hh:mm:ss> NODE=<xxx...x>
1045<B> MODADDR=<addr> MODTYPE=<type>
REPORT ALARM: stat: From bus parity error
Message Explanation
The frequency of parity errors on the indicated module has exceeded a predetermined threshold.
A parity error suggests a problem in data transmission and can be caused by a failing module,
physical removal of an enabled module, or by noise. Module removal and noise may cause
intermittent parity errors; clustering of parity errors indicates a failing module.
Recommended Action
Enter dstat < module > and check the FM NODE PARITY field to determine the number of
packets coming from the backplane that had parity errors. (This value may differ from the actual
number of alarms received, since alarms are thresholded and the FM NODE PARITY value is
not.) For the Switch module, it includes all packets transmitted by any interface module. For
individual interface modules, it includes all packets transmitted to that module. The number of
parity errors is proportional to the number of packets sent. Thus, a module with no traffic will
report no parity errors.
The following actions are listed according to the module type noted in this alarm message.
For the Switch module:
— Enter remove < module > to take an interface module out of service.
— Place the mode switch on the interface module in the Disab position.
— Check to see if the parity errors on the Switch module have stopped.
— If the errors have stopped, you have isolated the faulty module. Replace the module.
— If the errors continue, methodically repeat these steps for all interface modules.
For several interface modules:
— If modules on all shelves are reporting errors, the Switch module is failing. Replace the
Switch module.
WARNING: This disrupts all calls on the node!
For one interface module:
Replace the module.
The Installation chapter of the appropriate module reference and of the Node Reference provide
information for replacing either interface or critical modules.
Data Networking Products Messages Reference, Issue 5
2-23