Network operations systems TOPS Voice service node Log and alarm messages Release: VSN04 Status: Standard Version: 03.
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.
iii Contents 1. Introduction 1 Collection and printing log and alarm messages TOPS VSN log message format 1 Change history 4 BCS30 4 BCS31 4 BCS32 4 VSN03 4 VSN04 4 1 2. TOPS VSN log messages 3. Common TOPS VSN log messages - 0200 4. Common TOPS VSN log messages -0201 5. Common TOPS VSN log messages - 0202 6. Common TOPS VSN log messages - 0203 7. Common TOPS VSN log messages - 020A 8. Common TOPS VSN log messages - 0020 9. Voice interface resource manager log messages 0220 10.
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.
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 reporting.
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.
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.
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.
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.
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.
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 condition.
Common Tops log messages (0200) 0001/000A DNC Logs 9 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.
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.
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.
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.
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.
Common Tops log messages (0201) 0002/0008 DNC Logs 15 Message: [PRU_NAME] was trying to communicate with [PRU_NAME] but could not. ->TaskResult= "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.
16 Common TOPS VSN log messages (0201) 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. 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.
Common Tops log messages (0201) 0002/001A DNC Logs 17 Message: [Sending_PRU_name] was trying to communicate with [Receiving_ 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: The sending PRU could not communicate with the receiving PRU because the software version in each were not the same. Action: The user must reinstall both PRUs from the load tape. If the problem persists, then contact NT.
18 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, 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.
19 5. Common TOPS VSN log messages - 0202 0003/0000 Message: [PRU_name] successfully performed an IO operation on pathname [file/directory_pathname]. Description: The PRU successfully completed an IO operation. Action: 0003/0001 No action required. Message: [PRU_name] received an IO error (Mixed_Access) on path [file/directory_path name]. The "localized SRU" error was the result of mixing IO types, for example (Readln and blockreads).
20 Common TOPS VSN log messages (0202) Description: The PRU encountered an error during an IO operation on the 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: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
Common Tops log messages (0202) 0003/002A DNC Logs 21 Message: [PRU_name] received an IO error on path [file/directory_path name]. The error was the result of trying to save the file to disk, but the file was not opened for "writable" access. Description: The PRU encountered an error during an IO operation such as, 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.
22 Common TOPS VSN log messages (0202) Description: The PRU encountered an error during an IO operation on the 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: If the PRU is in the working state, no action is required.
Common Tops log messages (0202) DNC Logs 23 Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
24 Common TOPS VSN log messages (0202) Description: The PRU encountered an error during an IO operation on the 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: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU.
Common Tops log messages (0202) 0003/006A DNC Logs 25 Message: [PRU_name] received an IO error (Outside_File_Boundaries) on path [file/directory_path name]. The "server" error was the result of attempting an IO operation outside the boundaries of the file. (Accessing beyond the end of file). Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed.
26 Common TOPS VSN log messages (0202) Action: If the PRU is in the working state, no action is required. If the PRU is 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. 0003/006E Message: [PRU_name] received an IO error (Invalid_Password) on path [file/directory_path name].
Common Tops log messages (0202) DNC Logs 27 Description: The PRU encountered an error during an IO operation on the 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: Close all files that do not need to be open. If the PRU is in the working state, no action is required.
28 Common TOPS VSN log messages (0202) 0003/0075 Message: [PRU_name] received an IO error (Object_Not_Writable) on path [file/directory_path name]. The "server" error was the result of performing a write operation on an object (or file) that can not be written to. Description: The PRU encountered an error during an IO (write) operation on the file or object. 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.
Common Tops log messages (0202) DNC Logs 29 Action: If the PRU is in the working state, no action is required. If the PRU is 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. 0003/0079 Message: [PRU_name] received an IO error (Date_Noset) on path [file/directory_path name].
30 Common TOPS VSN log messages (0202) Description: The PRU encountered an error during an IO operation on the 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: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU.
Common Tops log messages (0202) 0003/0094 DNC Logs 31 Message: [PRU_name] received an IO error (Bad_Comm_Addr) on path [file/directory_path name]. The error was the result of specifying an invalid site address. Description: The PRU encountered an error during an IO operation on the 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.
32 Common TOPS VSN log messages (0202) Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
Common Tops log messages (0202) DNC Logs 33 Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
34 Common TOPS VSN log messages (0202) Description: The PRU encountered an error during an IO operation on the 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: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU.
Common Tops log messages (0202) 0003/0103 DNC Logs 35 Message: [PRU_name] received an IO error (Bad_Parameter) on path [file/directory_path name]. The error was the result of specifying an invalid input parameter. Description: The PRU encountered an error during an IO operation on the 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.
36 Common TOPS VSN log messages (0202) Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
Common Tops log messages (0202) DNC Logs 37 Description: The PRU encountered an error during an IO operation on the 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: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU.
38 Common TOPS VSN log messages (0202) 0003/010E Message: [PRU_name] received an IO error (PERM_Denied) on path [file/directory_path name]. The error was the result of permission denied. Description: The PRU encountered an error during an IO operation on the 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.
39 6. Common TOPS VSN log messages - 0203 0001/0000 Message: [PRU_name] encountered a VTP error [decimal]. [Two 80 character lines of optional data.] Description: The PRU encountered an communication error. The communication 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: If the PRU is in the working state, no action is required.
41 7. Common TOPS VSN log messages - 020A 0001/0000 Message: [PRU_name] could not obtain sufficient memory to operate. User action is required. [Two 80 character lines of optional data.] Description: The PRU could not find enough memory to perform a function or to initialize. Action: The user should make sure that there are no PRUs defined in the application processor that do not need to be there. Document the problem, record all action taken, and then contact NT.
42 Common TOPS VSN log messages (020A) 0001/0004 Message: [PRU_name] tried to locate [name] with the name server but failed. [Two 80 character lines of optional data.] Description: The PRU could not find the name of the PRU or task it was trying to locate using the name server facility. The PRU does not necessarily have to declare itself faulty; it can communicate using other means. This log indicates one of two problems: trouble with the name server, or that the PRU or task does not exist.
Common Tops log messages (020A) 0001/0021 DNC Logs 43 Message: [PRU_name] was attempting to perform an SDM "Set Atomic Commit" and failed. Error Type = [Helix_IO_result], Error Class = [1,2,3]. [Two 80 character lines of optional data.] Description: The PRU tries to set the atomic commit for a Service Data Manager operation and fails. Class error codes are: 1) run error, 2) task error, and 3) IO error. Action: This log should never occur. If it does, contact NT immediately.
44 Common TOPS VSN log messages (020A) Description: The PRU tries to start a transaction with the Service Data Manager and fails. Class error codes are: 1) run error, 2) task error, and 3) IO error. This log indicates that another user has already opened some of the required files or tables. Action: Record all information for NT. 0001/0027 Message: [PRU_name] was attempting to perform an SDM "End Transaction" and failed. Error Type = [Helix_IO_result], Error Class = [1,2,3].
Common Tops log messages (020A) 0001/002C DNC Logs 45 Message: [PRU_name] was attempting to perform an SDM "Read table" and failed. table Name = [SDM_table]. Error Type = [Helix_IO_result], Error Class = [1,2,3]. [Two 80 character lines of optional data.] Description: The PRU tries to read a Service Data Manager table and fails. Class error codes are: 1) run error, 2) task error, and 3) IO error. This log is generated when the table does not exist. Action: Record all information for NT.
46 Common TOPS VSN log messages (020A) 0001/0031 Message: [PRU_NAME] could not interpret a triple read from the SDM. Table name = [table_name] Tuple ID = [tuple_name] "Diagnostic String1" "Diagnostic String2" Description: This log indicates an error in interpreting a field within the specified tuple. Action: Re-edit the tuple and verify that the fields are all of the correct type. 0001/0032 Message: [PRU_NAME] was attempting to perform an SDM "notification Registration" and failed.
47 8. Common TOPS VSN log messages - 0020 0001/0000 Message: [PRU_name] could not insert Control Link PRU in data structure. It is full. Maximum number of control links supported = [max_number] Description: The maximum number of controls links the system can support has been reached. The maintenance notice PRU is still working but will only send notices to the first [max_number] control links up. Action: No action 0001/0001 Message: [PRU_name] could not insert a maintenance notice in data structure.
49 9. Voice interface resource manager log messages - 0220 0000/0000 Message: Error encountered attempting to load DTMF patterns. The symbol [symbol] is referenced in the table [table_name] but not found in the table [table_name]. Description: Applications can not access the VIs because of a reference error in an SDM table. This table can not be accessed by the user. Action: Contact NT to correct the problem. 0000/0001 Message: Error encountered attempting to load DTMF patterns.
51 10. Alarm Subsystem - 8722 0001/0001 0001/0002 0005/0001 Message: Alarm Interface Unit has RECEIVED an external alarm. External ALIU input is: . Explanation: The ALIU has sensed remote activation of an alarm condition.
52 Alarm Subsystem (8722) 0005/0002 0020/0000 0020/0001 0020/0002 0020/0003 0020/0004 Action: The system administrator must check the status of the APTIO port according to NTP 450-1011-301. If the fault has not been detected at the port, the operation of the LIU must be checked. It must also be determined if the cabling from the DNC to the LIU is intact. Message: The alarm subsystem has recovered communication with the APTIO port. APTIO port .
53 11. ACPE resource manager log messages - 9440 0000/0000 Message: [PRU_name] has detected the termination of an ACPE identified as [dead_PRU_name] [dead_PRU_number]. [Number_of_calls] will be terminated. Description: An ACPE PRU has died. All calls the ACPE was processing at the time the PRU died, are lost. If the ACPE died because of a fault, an alarm is sounded. If the ACPE died because it was courtesied down, then no alarm is generated. Action: Verify in SAS that the ACPEs go into service.
54 ACPE Resource Manager Log Messages (9440) Action: No action. 0000/000C Message: SET entry invoked - Changing the load on an ACPE. The ACPE was: [PRU_name] [PRU_number]. Description: The ACPE load has been set manually. This value is reset by the next interaction with the ACPE. Action: No action. 0000/000F Message: SET entry invoked - The ObjectID passed is not supported. Object Type was: [object_type]. Object Index was: [object_index]. Description: The object is not curently supported.
ACPE Resource Manager Log Messages (9440) 55 0000/0028 Message: (Tokenizer) Disk status is now lower than threshold. Will start collection. Description: Sample data collected is now written to disk. The daily audit has made room for new sample data. Call processing continues as usual and no effect to service is seen. Action: 0000/002A No action. Message: Tokenizer logged into server. Collection will start. Server name = . Description: Sample data is collected via server.
56 ACPE Resource Manager Log Messages (9440) Action: 0001/0021 No action. Message: [PRU_name] Non success return from tokenizer task, from INIT entry. No tokens will be issued. [Two 80 character lines of optional data.] Description: Unable to issue tokens because of unsuccessful return code from tokenizer. Call processing continues as usual and no effect to service is seen. Action: 0001/0022 No action. Message: [PRU_name] Exception entry invoked. All tokens will be turned off.
57 12. Control link log messages - 9441 0000/0000 Message: Data Link [link_identifier] to DMS [common_language_location _identifier] is in service. Description: This log is generated when the X.25 Control Link has been reset. At initialization time this log is considered a normal occurrence. At any other time it is not. Data may have been lost depending on the activity in progress at the time of the reset. Action: No action is required. The condition indicates that a link is now available.
58 Control Link Log Messages (9441) 0000/0003 Message: A Datalink message was discarded. Destination = [DMS_or_VSN]. Reason = [reason]. Message Type = [message_type]. Description: This log is generated when the X.25 Datalink software encounters a problem sending a message. The reason is one of the following: 1) Message type received from application is not supported, 2) Message type received on link is not supported, 3) problem relaying message to X.25 (outgoing message could not be sent to X.
59 13. Application call processing engine log messages - 9442 0000/0000 Message: , has just become operational. Call processing capacity of this ACPE is now 24 out of 24 calls. All pending minor alarms against this ACPE PRU will be cleared. [Two 80 character lines of optional data.] Description: This log is generated each time the ACPE is rebooted. If there were alarms pending against the PRU they are cleared. Action: 0000/0001 No action. Message:, Initialization sequence aborted.
60 Application Call Processing Engine Log Messages (9442) Description: The ACPE is beginning automatic recovery. The failure has only affected one subscriber call. If this log is generated many times in a short period of time, the ACPE has encountered a serious error and can not recover automatically. Action: No action is required if this event occurs periodically. If this log occurs often over a short period of time, take the ACPE PRU out of service, and then return it to service.
Application Call Processing Engine Log Messages (9442) 61 0003/0001 Message: ACPE error. Unable to initialize; duplicate datafill detected during executor initialization: [duplicate_data_string] reading SDM table: [table_name]. Description: This log is generated if a duplicate string is detected by the ACPE when reading an SDM table. This means there is ambiguous reference in the datafill. The ACPE can not go into a working state. Action: Change the datafill for one of the entries.
62 Application Call Processing Engine Log Messages (9442) Description: This log is generated when to many procedure variables have been added to the ACPE data structure. The ACPE will not load. Action: 0003/0009 Record all information and report the problem to NT. Message: ACPE error. A software error has been detected. See the debug information for details. Debugging Information: [parameter/value]. Description: This log is generated when there is an error in the code.
Application Call Processing Engine Log Messages (9442) 63 0003/000F Message: ACPE error. Unable to allocate T1 channel for call. Call was rejected. The CLLI of the DMS from which the call originated was [DMS_CLLI]. The voice channel on which the call was received was [channel_id]. Debugging Information: T1RM code: [decimal]. Description: This log is generated by the T1 Resource Manager when it is unable to allocate T1 resources for the call. The T1RM return code is given.
64 Application Call Processing Engine Log Messages (9442) Description: The ACPE could not determine the locality treatment for the current call because the Locality Database is either a new set of locality prompts, or a new set of locality prompts is being saved. This call will be handled according to the datafill of parameters Locality_Check and Loc_Default_Prompt in table User Interaction. Action: No immediate action is required because the ACPE continues to process calls,(at a diminished capacity).
65 14. T1 resource manager log messages - 9443 0000/0000 Message: [PRU_name] reports internal software error. [Two 80 character lines of optional data.] Description: The identified PRU is reporting a fatal internal error. The reason for the error may one of many (too many to list) but is clearly identified in the body of the message. Action: Document the error and message precisely, and then contact NT. The PRU must be reloaded. 0000/0001 Message: [PRU_name] reports administration error.
66 T1 Resource Manager Log Messages (9443) Description: A T1 Maintenance error has been reported. Action: 0001/0000 Exit, then re-access T1 Maintenance. Message: T1 Link Error for T1 SRU in Cabinet [cabinet_id], Slot [slot_id]. Condition = [string]. Error Level = [string]. Description: There is a link error for the T1 SRU at the specified location.
T1 Resource Manager Log Messages (9443) 67 0003/0000 Message: [PRU_name] has cleared any outstanding T1 Voice Link Alarms. Description: This log is generated each time the PRU is rebooted. If there were alarms pending against the PRU they are cleared. Action: 0003/0001 Major No action. Message: Voice Link Alarm Event for T1 SRU. Event = Major alarm set for failed Standby InService link. Description: A Major Alarm has been set for failed (SysBusy) T1 link.
69 15. Locality database log messages 944E 0000/0000 Message: The Locality Database has just become operational. Locality queries can now be processed. Any pending minor alarms against the Locality Database have been cleared. Description: This is an information message only. Action: None. 0000/0001 Message: The LDB has detected a serious problem which prevents it from initializing.
70 Locality Database Log Messages (944E) Description: The diagnostic strings, which are filled by the LDB PRU, describe the nature of the problem. The problem reported may be with the custom branding information found in the Custom Brands and Carrier Brands SDM tables, or in the Locality Database brand index fields. These problems may be the result ofi references to non-existent branding segment prompts in the Locality Database, references to non-existent brand indexes, and lack of data store memory.
Locality Database Log Messages (944E) 71 Description: A serious error was received from a system operation. If the error is a fatal error and the LDB is unable to continue processing, all queries being processed by the LDB PRU will be aborted. All MMI operations will be aborted. The first diagnostic string describes the nature of the problem, the second string gives additional information on the problem. Action: All information on this error should be recorded and reported to NT service personnel.
73 16. ACPE Maintenance Position log messages - 9445 9945/0004 0445/0005 Message: @1 Initialization sequence aborted. Error or inconsistency encountered while loading the ACPE Maintenance Position initialization data. xxxxx xxxxx Description: @1 is the reporting PRU, namely the ACPE Maintenance Position. xxxxx are two strings that describe the error that was encountered. Action: An error has occurred during the ACPE Maintenance Position initialization.
75 17. Prompt manager log messages 9451 0100/0101 Message: User logged in Description: This message is informative only, confirming that the user with the has logged in. Action: None. 0100/0102 Message: User logged out Description: This message is informative only, confirming that the user with the has logged out. Action: None.
76 Prompt Manager Log Messages (9451) 0200/0201 Message: Forced Exit 0200/0202 Message: Archive Failure 0200/0203 Message: Restore Failure 0200/0204 Message: Bad system command 0200/0205 Message: Install unsuccessful 0300/0301 Message: Cannot open file 0300/0302 Message: Cannot create file 0300/0303 Message: Read failure 0300/0304 Message: Write failure
77 18. Suppressed and Thresholded Logs This section lists the system logs which have been suppressed or thresholded. The format for suppressed logs is . The format for thresholded logs is Suppressed Logs 0000 00010002 KERNEL INNER CI 0002 41010001 0002 41010011 0002 41020037 0002 41050003 0002 4106003B VTP: ERROR 1 VTP: PHYSICAL DEST IS NON-EXISTENT.
78 3.
Suppressed and Thresholded Logs 79 700 00020001 8700 00020002 8700 00020003 8700 00020004 8700 00020005 8700 00020006 8700 00020007 8700 00020008 8700 00020009 8700 00020010 8700 00020011 8700 00024104 8700 00030001 8700 00030002 8700 00030005 8700 00030007 8700 00040001 8700 00040003 8700 00040004 Campus resource manager Campus resource manager Campus resource manager Campus resource manager Campus resource manager Campus resource manager Campus resource manager Campus resource manager Campus resource ma
80 3.
81 19. DMS notices Some events which occur in the TOPS VSN must be reported to the DMS switch. The report takes the form of a notification message. The list which follows identifies the log/alarm messages sent to the DMS. table VSNALARM on the DMS, which is datafilled by the operating company, adds severity and textual information to the notification message before it is output on the DMS side. The event ID given here corresponds directly to the alarm code in table VSNALARM.
83 20.
Network operations systems TOPS Voice service node Log and alarm messages Copyright © 1995 Northern Telecom All rights reserved. TOPS and DMS are trademarks of Northern Telecom. NTP 450-1301-511 Release: VSN04 Version: 03.
