13
TOPS VSN Log and alarm messages
4. Common TOPS VSN logmessages -0201
0002/0000
Message:
[PRU_name] has successfully communicated with [Other
PRU_name]. (No error detected.)
Description:
The named PRUs are communicating.
Action:
No action is required.
0002/0001
Message:
[Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. This means the message was not accepted after a
timeout value.
Description:
The sending PRU could not communicate with the receiving
PRU. The latter did not accept the message after a specified time interval. 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/0002
Message:
[Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. This means the message was not accepted after a
timeout value.
Description:
The sending PRU could not communicate with the receiving
PRU. The latter did not accept the message after a specified time interval. 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/0003
Message:
[Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. This means the message was not accepted after a
timeout value.
Description:
The sending PRU could not communicate with the receiving
PRU. The latter did not accept the message after a specified time interval. It is
the responsibility of the sending PRU to recover from the error by resending
the message or to declare itself faulty.