How it Works
Nortel Networks
Loading...
VSN04
User Manual
90 pgs224.77 Kb0
Table of contents
Loading...

Nortel Networks VSN04 User Manual

Network operations systems
TOPS Voice service node
Log and alarm messages
Release: VSN04 Status: Standard Version: 03.01
Network operations systems
TOPS Voice service node
Log and alarm messages
Publication number: 450-1301-511 Document status: Standard Document version: 03.01 Document release: VSN04 Date: August 1995
© Northern Telecom All rights reserved.
TOPS VSN log and alarm messages

Contents

1. Introduction 1
Collection and printing log and alarm messages 1 TOPS VSN log message format 1 Change history 4
BCS30 4 BCS31 4 BCS32 4 VSN03 4 VSN04 4
2. TOPS VSN log messages 5
3. Common TOPS VSN log messages - 0200 7
4. Common TOPS VSN log messages -0201 13
5. Common TOPS VSN log messages - 0202 19
6. Common TOPS VSN log messages - 0203 39
7. Common TOPS VSN log messages - 020A 41
8. Common TOPS VSN log messages - 0020 47
9. Voice interface resource manager log messages ­0220 49
10. Alarm Subsystem - 8722 51
11. ACPE resource manager log messages - 9440 53
12. Control link log messages - 9441 57
13. Application call processing engine log messages
- 9442 59
14. T1 resource manager log messages - 9443 65
15. Locality database log messages - 944E 69
16. ACPE Maintenance Position log messages ­9445 73
17. Prompt manager log messages - 9451 75
18. Suppressed and Thresholded Logs 77
Suppressed Logs 77 Thresholding Logs 79
19. DMS notices 81
20. Abbreviations 83
iii
TOPS VSN Log and alarm messages

1. Introduction

Collection and printing log and alarm messages

Logs and Alarms are collected for TOPS Voice Service Node (VSN) using the log and alarm subsystem installed in base TOPS VSN software. The same subsystem is responsible for creating log and alarm reports. These are stored temporarily on the TOPS VSN and can be sent to a printer or to a terminal for continuous display. TOPS VSN uses a dedicated printer to report its log messages.
Predefined log and alarm configuration datafill is delivered to the operating company as part of the TOPS VSN installation tapes.

TOPS VSN log message format

A typical TOPS VSN log or alarm message is shown below in figure 1-1. Its identifying information is printed on one or two lines, and is followed by the message.
Figure 1-1 Sample TOPS VSN log/alarm message
1
Severity of Occurrance
LAN_NAME
PRU state Change: Cabinet 1 Slot 14 Unit#85BC Configuration #0000 FAULTY Reporting PRU is Logger Other PRU is Unspecified RU.
dwg 1301-511-1
Subsystem Number
Report Number
Log Message Number
Date and Time of Generation Locally
88 03 22 13:36Subsystem=8720, Report no=0003, Error no=0002,*Minor
TOPS VSN Log and alarm messages
2 Introduction
Header Information For TOPS VSN Log Messages.
Identifying information, also known as header information, uniquely identifies each log and alarm message. The header of every log or alarm message generated by TOPS VSN contains the following:
(a)
Date and Time. The date and time are displayed in the upper left of the
message. The format of the date is yymmdd, and the format of the time is hh:mm.
Severity. Each log message specifies the severity of the event it is
(b)
reporting. The following terms or values are used to indicate severity:
*C Critical Severity 1 Logs with this severity generate critical
alarms. These logs and alarms are the result of catastrophic failures such as power failures.
** Major Severity 2 Logs with this severity generate major
alarms. These logs and alarms are the result serious failures such as PRUs being unable to initialize.
* Minor Severity 3 Logs with this severity generate minor
alarms. These alarms are used to flag problems that need either a visual or audible display at the TOPS VSN site. An example of a problem that would cause a minor alarm is an incorrect table entry.
GEvent GError LEvent LError
Warning/ Trouble
Status Severity 9 This log severity reports the status of a
Progress Severity 10 Log reports the progress of an event.
Severity 4 Severity 5 Severity 6 Severity 7
Severity 8 This log severity indicates a warning.
Severity 11-13 These severity ratings are not defined for
These are intermediate severity ratings. An event is a happening that does not effect service. The event is simply logged for the record. An error is also considered non­service affecting. It is an isolated error condition caused by the system, for example, a single lost call.
particular software or hardware unit. The percentage of disk space used is an example of a log with status severity.
TOPS VSN.
TOPS VSN Log and alarm messages
Introduction 3
Status 14 Status 14 Used for login/logout security related
events. This status is now used by all logs generated from two DVS subsystems (8029 System Administration (Report #1 only, and 8039 Security Agent Sub-PRU). The logs produced from these two subsystems identify logins, logouts, changes to USERIDs and Admin objects.
Information Status 15 This log severity is used for informational
purposes only.
(c) Subsystem Number. The subsystem number is a four-digit hexadecimal
number that identifies a message subsystem. For example, the subsystem number for TOPS VSN common logs is 0200 to 020A. Each program resource unit (PRU) that generates logs has its own subsystem; the common logs are shared by all TOPS VSN PRUs.
The following list identifies the number associated with each PRU:
0200 - Common Logs - Run Errors 0201 - Common Logs - Tasking Errors 0202 - Common Logs - I/O Errors 0203 - Common Logs - VTP Errors 020A - TOPS VSN Common Logs 0220 - VI Resource Manager Logs 8722 - Alarms PRU 9440 - ACPE Resource Manager Logs 9441 - Control Link Logs 9442 - ACPE Logs + ACPE Executor 9443 - T1 Resource Manager Logs 9445 - ACPE Maintenance Position
Report Number. Report numbers are hexadecimal numbers. They identify
(d)
the group or category within the subsystem file the message belongs to. For TOPS VSN common log messages, the following numbering convention applies:
Number Type
0000 Nonspecified error types 0001 Run errors 0002 Tasking errors 0003 IO errors
(e) Error Number. Error numbers are hexadecimal numbers. They identify the
specific error condition within each report number grouping.
TOPS VSN Log and alarm messages
4 Introduction

Change history

This section summarizes the important changes that affect this publication. They are arranged under the heading of the appropriate Batch Change Supplement (BCS) release.

BCS30

The presentation of this publication has been changed.
The following changes to the TOPS VSN application were made by BCS30:
• introduction of log messages for the locality database
• introduction of log messages for the prompt manager
• addition of an abbreviations list
• introduction of log messages for the support of locality call processing

BCS31

This Document has been reissued as part of the BCS31 release.

BCS32

This document has been revised to include several new alarms in the 8722 subsystem and to include a list of suppressed and thresholded logs.
VSN03 - Version 02.01
This document has been revised to include several new alarm and log messages.
VSN04 - Version 03.01
This document has been revised to include a new log message.
TOPS VSN Log and alarm messages

2. TOPS VSN log messages

TOPS VSN log messages are separated into two groups: common logs, and PRU-specific logs. Each group generates logs from a single subsystem (in most cases a subsystem is defined by a PRU). This Publication uses separate tables for each subsystem that generates logs.
The first six tables list logs that are common to TOPS VSN as a whole. These logs are generated from base software but have specific application to TOPS VSN. With these logs there is no one-to-one correspondence between subsystem and PRU. The remaining tables list logs by software (PRU) subsystem. A complete list of logs generated from base software is given in Publication 450-1301-511.
Accompanying each log entry is a definition and a description of the action the user must take to respond to the log. This Publication contains the following log sections:
• 3. lists messages for base run errors.
• 4. lists messages for base tasking errors.
• 5. lists messages for base IO errors.
• 6. lists messages for base VTP errors.
• 7. lists messages for TOPS VSN common logs.
• 8. lists base maintenance notices.
• 9. lists messages for VI resource manager errors.
• 10. lists messages for the Alars PRU.
• 11. lists messages for ACPE resource manager errors.
• 12. lists messages for datalink errors.
• 13. lists messages for ACPE errors.
• 14. lists messages for T1 resource manager errors.
• 15. lists messages for the Locality Database.
• 16. lists messages for the Prompt Manager.
5
TOPS VSN Log and alarm messages
6 DNC Logs TOPS VSN Log Messages
The following messages are the complete, or raw messages. The log service may select only certain items from the lists shown for each message, depending on the nature of the event.
TOPS VSN Log and alarm messages

3. Common TOPS VSN log messages - 0200

7
0001/0000
0001/0001
0001/0002
0001/0003
0001/0004
Message:
unrecoverable error and the SRU where this PRU resides should be rebooted.
Description:
PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
the SRU. Record all action taken.
Message:
an unrecoverable error and the PRU should be rebooted.
Description:
zero operation. The PRU may declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
run error. This is an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
a faulty state, document the problem, restart the PRU, and then contact NT.
Message:
This is an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
unrecoverable error and the PRU should be rebooted.
[PRU_name] has encountered a bus error. This is an
The software task failed because of a hardware error. If the
Reboot the SRU. If the error occurs more than once a week replace
[PRU_name] has encountered a divided by zero run error. This is
The software task failed because it encountered a divide by
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered a dereferencing of an odd address
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is in
[PRU_name] has encountered an illegal user instruction run error.
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is in
[PRU_name] has encountered a value range error. This is an
TOPS VSN Log and alarm messages
8 Common TOPS VSN log messages (0200)
0001/0005
0001/0006
0001/0007
0001/0008
0001/0009
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
Errordefs.
Description:
Action: Retain all information regarding the problem, and then contact NT.
Message:
an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
unrecoverable error and the PRU should be rebooted. If rebooting the PRU does not solve the problem, reboot the SRU.
Description:
blocks. Control blocks are required for communication between PRUs. The PRU may declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
reboot the SRU. If the error occurs more than once a week replace the SRU. Document the problem and record all action taken.
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered a stack overflow condition. This is
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is in
[PRU_name] has encountered a privilege violation error. This is an
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name], Filler log. This log should not occur as defined in
The software task failed due to a software error.
[PRU_name] has no buffer pools associated with the task. This is
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] can not allocate control blocks. This is an
The software task failed because it could not allocate control
Reboot the PRU. If this action does not correct the problem, then
TOPS VSN Log and alarm messages
Common Tops log messages (0200) DNC Logs 9
0001/000A
0001/000B
0001/000C
0001/000D
0001/000E
Message:
unrecoverable error and the PRU should be rebooted. If rebooting the PRU does not solve the problem, reboot the SRU.
Description:
mapping error. The PRU may declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
reboot the SRU. If the error occurs more than once a week replace the SRU. Document the problem and record all action taken.
Message:
unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
unrecoverable error and the SRU should have diagnostics run.
Description:
declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
other PRUs out of service first. If diagnostics fail, replace the SRU. If diagnostics do not detect an error but the problem persists, replace the SRU. Document the problem and record all action taken.
Message:
error and the SRU should be rebooted.
Description:
the PRU is operating has encountered an unexpected state. The PRU may declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
the SRU. Document the problem and record all action taken.
Message:
an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
[PRU_name] encountered a segment or mapper error. This is an
The software task failed because it encountered a segment or
Reboot the PRU. If this action does not correct the problem, then
[PRU_name] has been in a critical region too long. This is an
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered a parity error. This is an
The software task failed because of a parity error. The PRU may
Run diagnostics on the SRU containing the PRU. To do this take all
[PRU_name] encountered a kernel error. This is an unrecoverable
The software task failed because the kernel of the SRU in which
Reboot the SRU. If the error occurs more than once a week replace
[PRU_name] has encountered a floating point math error. This is
The software task failed due to a reference error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
TOPS VSN Log and alarm messages
10 Common TOPS VSN log messages (0200)
0001/000F
0001/0010
0001/0011
0001/0012
0001/0013
0001/0014
Message:
This is an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
operation. This is an unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
operation. Specifically, the error occurred when performing a conversion of a long integer to a short integer. This is an unrecoverable error and the PRU should be rebooted.
Description:
converted to a short integer. The PRU may declare itself faulty or recreate the task. If the PRU declares itself faulty then the log subsystem detects the faulty condition and raises an alarm.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
unrecoverable error.
Description:
operation. The PRU may declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
performing multiplication. This is an unrecoverable error and the PRU should be rebooted.
Description:
too large and overflowed. The PRU may declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
This is an unrecoverable error and the PRU should be rebooted.
[PRU_name] has encountered a nil pointer reference run error.
The software task failed due to a reference error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered a run error when performing a set
The software task failed during a set operation. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered a run error while performing a math
The software task failed because the integer was to large to be
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered a divide by zero run error. This is an
The software task failed because of a long divide by zero
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has encountered an overflow run error when
The software task failed because a multiplication operation was
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] has attempted to exit a procedure not directly called.
TOPS VSN Log and alarm messages
Common Tops log messages (0200) DNC Logs 11
0001/0015
0001/0016
0001/0017
Description:
command from a procedure it was not currently executing. The PRU may declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
unrecoverable error and the PRU should be rebooted.
Description:
declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
was negative. This is an unrecoverable error and the PRU should be rebooted.
Description:
a transcendental function. Transcendental function values must be positive. The PRU may declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
Message:
numbers. This is an unrecoverable error and the PRU should be rebooted.
Description:
operation. The PRU may declare itself faulty or recreate the task.
Action:
in the faulty state, document the problem, restart the PRU, and then contact NT.
The software task failed because it tried to perform an exit
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] encountered a mini-task error. This is an
The software task failed due to a software error. The PRU may
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] was passed input to a transcendental function that
The software task failed because a negative value was used for
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] encountered an error associated with IEEE real
The software task failed because of an illegal IEEE real number
If the PRU is in the working state, no action is required. If the PRU is
TOPS VSN Log and alarm messages

4. Common TOPS VSN log messages -0201

13
0002/0000
0002/0001
0002/0002
0002/0003
Message:
PRU_name]. (No error detected.)
Description: Action: Message:
PRU_name] but could not. This means the message was not accepted after a timeout value.
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. This means the message was not accepted after a timeout value.
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. This means the message was not accepted after a timeout value.
Description:
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_name] has successfully communicated with [Other
The named PRUs are communicating.
No action is required.
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
TOPS VSN Log and alarm messages
14 Common TOPS VSN log messages (0201)
0002/0004
0002/0005
0002/0006
0002/0007
Action:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. Either a bad control block handler or a bad taskID could cause such an error.
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. The receiver of the message [Receiving_PRU_ name] is probable cause of error.
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. This means the message was not accepted after a timeout value.
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. The sender encountered an invalid wait time.
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
TOPS VSN Log and alarm messages
Common Tops log messages (0201) DNC Logs 15
0002/0008
0002/0009
0002/000F
0002/0011
0002/0015
Message:
could not.
->TaskResult=<task_result_num> "Diagnostic String1" "Diagnostic String2"
Description:
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:
problem and contact your NT representative.
Message: Description:
of this PRU to recover from the error by resending the message or to declare itself faulty.
Action:
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.
Message:
PRU_name] but could not. The sender [Sending_PRU_name] did not have a communication pool available OR there was an invalid "MakePool".
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. The sender [Sending_PRU_name] encountered an illegal operation in its mini task.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
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.
[PRU_NAME] was trying to communicate with [PRU_NAME] but
This log indicates that a communication error has occurred.
If the problem persists, retain all of the information regarding the
[Sending_PRU_name] was trying to initiate a task but could not.
The sending PRU could not initiate a task. It is the responsibility
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
TOPS VSN Log and alarm messages
16 Common TOPS VSN log messages (0201)
0002/0016
0002/0017
0002/0018
0002/0019
Description:
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:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. The sender [Sending_PRU_ name] could not transmit to the network.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, restart the sending PRU. If the problem persists, then reboot the entire machine. Document the problem, record all action taken, and then contact NT.
Message:
PRU_name] but could not. The sender [Sending_PRU_ name] encountered a stack overflow.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, then restart the sending PRU. If the problem persists, then reboot the SRU in which the PRU resides. Document the problem, record all action taken, and then contact NT.
Message:
PRU_name] but could not. The information being passed within the communication packet is invalid.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. The entry definition in [Receiving_PRU_name] does not match what [Sending_PRU_ name] expects. User action is required.
Description:
PRU because the software version in each were not the same.
Action:
persists, then contact NT.
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
The user must reinstall both PRUs from the load tape. If the problem
TOPS VSN Log and alarm messages
Common Tops log messages (0201) DNC Logs 17
0002/001A
0002/001B
0002/001C
0002/001D
0002/001E
Message:
PRU_name] but could not. The entry definition in [Sending_PRU_name] was not found, OR push/pull was invoked when not in entry. User action is required.
Description:
PRU because the software version in each were not the same.
Action:
persists, then contact NT.
Message:
PRU_name] but could not. The result was a communication failure.
Description:
because the receiving PRU is not there. It is the responsibility of the sending PRU to recover from the error or to declare itself faulty.
Action:
in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
Message:
PRU_name] but could not. The result was that the location address of the receiver was invalid.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, then document the problem, and restart both sending and receiving PRUs. If necessary, restart the SRUs in which both PRUs reside. Record all action taken, and then contact NT.
Message:
PRU_name] but could not. The result was an interval timer error.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action:
in the faulty state, then document the problem, and restart both sending and receiving PRUs. If necessary, restart the SRUs in which both PRUs reside. Record all action taken, and then contact NT.
Message:
PRU_name] but could not. The problem is the sender [Sending_PRU_name] could not obtain control blocks. User action is required.
Description:
PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
The user must reinstall both PRUs from the load tape. If the problem
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU can not communicate with the receiving PRU
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
If the PRU is in the working state, no action is required. If the PRU is
[Sending_PRU_name] was trying to communicate with [Receiving_
The sending PRU could not communicate with the receiving
TOPS VSN Log and alarm messages
18 Common TOPS VSN log messages (0201)
Action:
in the faulty state, then document the problem, and restart both sending and receiving PRUs. If necessary, restart the SRUs in which both PRUs reside. Record all action taken, and then contact NT.
If the PRU is in the working state, no action is required. If the PRU is
TOPS VSN Log and alarm messages

5. Common TOPS VSN log messages - 0202

19
0003/0000
0003/0001
0003/0002
0003/0014
Message:
[file/directory_pathname].
Description: Action: Message:
[file/directory_path name]. The "localized SRU" error was the result of mixing IO types, for example (Readln and blockreads).
Description:
file or directory. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, the corrective action taken, and then contact NT.
Message:
name]. The error was the result of reaching a resource limit.
Description:
file or directory. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If the PRU is still faulty, then reboot the SRU in which the PRU resides. If all reboot operations are unsuccessful, then reboot the whole system. Document the problem, the corrective action taken, and then contact NT.
Message:
name]. The error was the result of trying to write an illegal character.
[PRU_name] successfully performed an IO operation on pathname
The PRU successfully completed an IO operation.
No action required.
[PRU_name] received an IO error (Mixed_Access) on path
The PRU encountered an error during an IO operation on the
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO operation on the
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
TOPS VSN Log and alarm messages
20 Common TOPS VSN log messages (0202)
0003/001E
0003/0028
0003/0029
Description:
file or directory. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, the corrective action taken, and then contact NT.
Message:
name]. The error was the result of an out of bounds operation.
Description:
file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, the corrective action taken, and then contact NT.
Message:
name]. The error was the result of performing an I/O operation on a file that was not opened.
Description:
file or directory. The operation was not performed because it did not make its way to the server. This error is in the SRU where the PRU resides. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, or if the problem persists, then reboot the PRU. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the entire system. Document the problem, record all action taken, and then contact NT.
Message:
name]. The error was the result of performing an open operation on a file that was already opened.
Description:
on the file or directory. The operation was not performed because it did not make its way to the server. The error is in the SRU where the PRU resides. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, the corrective action taken, and then contact NT.
The PRU encountered an error during an IO operation on the
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO operation on the
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO operation on the
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO (open) operation
If the PRU is in the working state, no action is required. If the PRU is
TOPS VSN Log and alarm messages
Common Tops log messages (0202) DNC Logs 21
0003/002A
0003/002B
0003/002C
0003/002D
Message:
name]. The error was the result of trying to save the file to disk, but the file was not opened for "writable" access.
Description:
open, read, or write, on the file or directory. The operation was not performed because it did not make its way to the server. The error is in the SRU where the PRU resides. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, the corrective action taken, and then contact NT.
Message:
name]. The error was the result of performing an illegal seek operation.
Description:
open, read or write, on the file or directory. The operation was not performed because it did not make its way to the server. The error is in the SRU where the PRU resides. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
Message:
name]. The error was the result of performing an operation on a file set using a bad identifier for the file set.
Description:
file or directory. The operation was not performed because it did not make its way to the server. This error is in the SRU where the PRU resides. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action:
in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
Message:
name]. The error was the result of performing an I/O operation, but the server that was referenced [first_component_of_pathname], was not found.
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO operation such as,
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO operation such as,
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
The PRU encountered an error during an IO operation on the
If the PRU is in the working state, no action is required. If the PRU is
[PRU_name] received an IO error on path [file/directory_path
TOPS VSN Log and alarm messages
Loading...
+ 63 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use