Summary of the content on the page No. 1
Network operations systems
TOPS
Voice service node
Log and alarm messages
Release: VSN04 Status: Standard Version: 03.01
Summary of the content on the page No. 2
Summary of the content on the page No. 3
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 is a trademark of Northern Telecom. TOPS VSN log and alarm messages
Summary of the content on the page No. 4
Summary of the content on the page No. 5
iii 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
Summary of the content on the page No. 6
Summary of the content on the page No. 7
1 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
Summary of the content on the page No. 8
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. (b) Severity. Each log message specifies the severity of the event it is reportin
Summary of the content on the page No. 9
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 numbe
Summary of the content on the page No. 10
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
Summary of the content on the page No. 11
5 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 corresp
Summary of the content on the page No. 12
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
Summary of the content on the page No. 13
7 3. Common TOPS VSN log messages - 0200 0001/0000 Message: [PRU_name] has encountered a bus error. This is an unrecoverable error and the SRU where this PRU resides should be rebooted. Description: The software task failed because of a hardware error. 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. Record all action taken. 0001/0001 Message: [PRU_n
Summary of the content on the page No. 14
8 Common TOPS VSN log messages (0200) Description: The software task failed due to a software 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: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, document the problem, restart the PRU, and then contact NT. 0001/0005 Message: [PRU_name] has encountered a stack overflow con
Summary of the content on the page No. 15
Common Tops log messages (0200) DNC Logs 9 0001/000A Message: [PRU_name] encountered a segment or mapper error. This is an unrecoverable error and the PRU should be rebooted. If rebooting the PRU does not solve the problem, reboot the SRU. Description: The software task failed because it encountered a segment or 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.
Summary of the content on the page No. 16
10 Common TOPS VSN log messages (0200) 0001/000F Message: [PRU_name] has encountered a nil pointer reference run error. This is an unrecoverable error and the PRU should be rebooted. Description: The software task failed due to a reference error. The PRU may declare itself faulty or recreate the task. 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 the PRU, and then contact NT. 0001/0010 Message: [PRU_name
Summary of the content on the page No. 17
Common Tops log messages (0200) DNC Logs 11 Description: The software task failed because it tried to perform an exit command from a procedure it was not currently executing. The PRU may declare itself faulty or recreate the task. 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 the PRU, and then contact NT. 0001/0015 Message: [PRU_name] encountered a mini-task error. This is an unrecoverable error and the
Summary of the content on the page No. 18
Summary of the content on the page No. 19
13 4. Common TOPS VSN log messages -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 t
Summary of the content on the page No. 20
14 Common TOPS VSN log messages (0201) 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/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. Description: The sending PRU could not communicate with the receiving PRU. The l
