Filter
Top Products
Common Tops log messages (0201) DNC Logs 15
TOPS VSN Log and alarm messages
0002/0008
Message:
[PRU_NAME] was trying to communicate with [PRU_NAME] but
could not.
->TaskResult=<task_result_num>
"Diagnostic String1"
"Diagnostic String2"
Description:
This log indicates that a communication error has occurred.
Action may be required, depending on the state of the PRU(s). If the PRU(s) are
in a "working" state, it can be assumed that the software recovered from the
error and no further action is required. If one or both of the PRUs are "faulty" or if
the problem persists, reboot the "faulty" PRU(s).
Action:
If the problem persists, retain all of the information regarding the
problem and contact your NT representative.
0002/0009
Message:
[Sending_PRU_name] was trying to initiate a task but could not.
Description:
The sending PRU could not initiate a task. It is the responsibility
of this PRU to recover from the error by resending the message or to declare
itself faulty.
Action:
If the PRU is in the working state, no action is required. If the PRU is
in the faulty state, document the problem and reboot the PRU. If the problem
persists reboot the SRU in which the PRU resides. Document the problem,
record all action taken , and then call NT.
0002/000F
Message:
[Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. The sender [Sending_PRU_name] did not have a
communication pool available OR there was an invalid "MakePool".
Description:
The sending PRU could not communicate with the receiving
PRU. It is the responsibility of the sending PRU to recover from the error by
resending the message or to declare itself faulty.
Action:
If the PRU is in the working state, no action is required. If the PRU is
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.
0002/0011
Message:
[Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. The sender [Sending_PRU_name] encountered
an illegal operation in its mini task.
Description:
The sending PRU could not communicate with the receiving
PRU. It is the responsibility of the sending PRU to recover from the error by
resending the message or to declare itself faulty.
Action:
If the PRU is in the working state, no action is required. If the PRU is
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.
0002/0015
Message:
[Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. Depending on the type of communication method
used either [Receiving_PRU_ name] or [Sending_PRU_name] does not have
enough communication buffers available.