Nortel Networks Recording Equipment VSN04 User Manual
14 Common TOPS VSN log messages (0201)
TOPS VSN Log and alarm messages
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.
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.
0002/0004
Message: [Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. Either a bad control block handler or a bad taskID
could cause such an error.
PRU_name] but could not. Either a bad control block handler or a bad taskID
could cause such an error.
Description: The sending PRU could not communicate with the receiving
PRU. The latter did not accept the message. It is the responsibility of the
sending PRU to recover from the error by resending the message or to declare
itself faulty.
PRU. The latter did not accept the message. 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.
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.
0002/0005
Message: [Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. The receiver of the message [Receiving_PRU_
name] is probable cause of error.
PRU_name] but could not. The receiver of the message [Receiving_PRU_
name] is probable cause of error.
Description: The sending PRU could not communicate with the receiving
PRU. The latter did not accept the message. It is the responsibility of the
sending PRU to recover from the error by resending the message or to declare
itself faulty.
PRU. The latter did not accept the message. 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.
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.
0002/0006
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.
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.
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.
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.
0002/0007
Message: [Sending_PRU_name] was trying to communicate with [Receiving_
PRU_name] but could not. The sender encountered an invalid wait time.
PRU_name] but could not. The sender encountered an invalid wait time.
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.
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.
in the faulty state, document the problem, restart both sending and receiving
PRUs, and then contact NT.