Benutzeranleitung / Produktwartung VSN04 des Produzenten Nortel Networks
Zur Seite of 90
Network operations systems TOPS Voice service node Log and alarm messages Release: VSN04 Status: Standard Version: 03.01.
.
© Northern Telecom All rights reserved. TOPS is a trademark of Northern Telecom. TOPS VSN log and alarm messages Publication number: 450-1301-511 Document status: Standard Document version: 03.
.
iii 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.
.
1 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.
2 Introduction TOPS VSN Log and alarm messages 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.
Introduction 3 TOPS VSN Log and alarm messages 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).
4 Introduction TOPS VSN Log and alarm messages 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 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.
6 DNC Logs TOPS VSN Log Messages TOPS VSN Log and alarm 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 TOPS VSN Log and alarm messages 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.
8 Common TOPS VSN log messages (0200) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0200) DNC Logs 9 TOPS VSN Log and alarm messages 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.
10 Common TOPS VSN log messages (0200) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0200) DNC Logs 11 TOPS VSN Log and alarm messages 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.
.
13 TOPS VSN Log and alarm messages 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.
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.
Common Tops log messages (0201) DNC Logs 15 TOPS VSN Log and alarm messages 0002/0008 Message: [PRU_NAME] was trying to communicate with [PRU_NAME] but could not. ->TaskResult=<task_result_num> "Diagnostic String1" "Diagnostic String2" Description: This log indicates that a communication error has occurred.
16 Common TOPS VSN log messages (0201) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0201) DNC Logs 17 TOPS VSN Log and alarm messages 0002/001A 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.
18 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, then document the problem, and restart both sending and receiving PRUs. If necessary, restart the SRUs in which both PRUs reside.
19 TOPS VSN Log and alarm messages 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: No action required.
20 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0202) DNC Logs 21 TOPS VSN Log and alarm messages 0003/002A 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.
22 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0202) DNC Logs 23 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, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
24 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0202) DNC Logs 25 TOPS VSN Log and alarm messages 0003/006A 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.
26 Common TOPS VSN log messages (0202) 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, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
Common Tops log messages (0202) DNC Logs 27 TOPS VSN Log and alarm messages 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.
28 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0202) DNC Logs 29 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, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
30 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0202) DNC Logs 31 TOPS VSN Log and alarm messages 0003/0094 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.
32 Common TOPS VSN log messages (0202) 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, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
Common Tops log messages (0202) DNC Logs 33 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, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
34 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
Common Tops log messages (0202) DNC Logs 35 TOPS VSN Log and alarm messages 0003/0103 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.
36 Common TOPS VSN log messages (0202) 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, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation.
Common Tops log messages (0202) DNC Logs 37 TOPS VSN Log and alarm messages 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.
38 Common TOPS VSN log messages (0202) TOPS VSN Log and alarm messages 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.
39 TOPS VSN Log and alarm messages 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.
.
41 TOPS VSN Log and alarm messages 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.
42 Common TOPS VSN log messages (020A) TOPS VSN Log and alarm messages 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.
Common Tops log messages (020A) DNC Logs 43 TOPS VSN Log and alarm messages 0001/0021 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.
44 Common TOPS VSN log messages (020A) TOPS VSN Log and alarm messages 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.
Common Tops log messages (020A) DNC Logs 45 TOPS VSN Log and alarm messages 0001/002C 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].
46 Common TOPS VSN log messages (020A) TOPS VSN Log and alarm messages 0001/0031 Message: [PRU_NAME] could not interpret a triple read from the SDM. Table name = [table_name] Tuple ID = [tuple_name] &.
47 TOPS VSN Log and alarm messages 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.
.
49 TOPS VSN Log and alarm messages 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].
.
51 TOPS VSN Log and alarm messages 10. Alarm Subsystem - 8722 0001/0001 Message: Alarm Interface Unit has RECEIVED an external alarm. External ALIU input is: <string>.
52 Alarm Subsystem (8722) TOPS VSN Log and alarm messages 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.
53 TOPS VSN Log and alarm messages 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.
54 ACPE Resource Manager Log Messages (9440) TOPS VSN Log and alarm messages 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.
ACPE Resource Manager Log Messages (9440) 55 TOPS VSN Log and alarm messages 0000/0028 Message: <PRU_name> (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.
56 ACPE Resource Manager Log Messages (9440) TOPS VSN Log and alarm messages Action: No action. 0001/0021 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.
57 TOPS VSN Log and alarm messages 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.
58 Control Link Log Messages (9441) TOPS VSN Log and alarm messages 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.
59 TOPS VSN Log and alarm messages 13. Application call processing engine log messages - 9442 0000/0000 Message: <PRU_name>, 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.
60 Application Call Processing Engine Log Messages (9442) TOPS VSN Log and alarm messages 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.
Application Call Processing Engine Log Messages (9442) 61 TOPS VSN Log and alarm messages 0003/0001 Message: ACPE error. Unable to initialize; duplicate datafill detected during executor initialization: [duplicate_data_string] reading SDM table: [table_name].
62 Application Call Processing Engine Log Messages (9442) TOPS VSN Log and alarm messages Description: This log is generated when to many procedure variables have been added to the ACPE data structure. The ACPE will not load. Action: Record all information and report the problem to NT.
Application Call Processing Engine Log Messages (9442) 63 TOPS VSN Log and alarm messages 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].
64 Application Call Processing Engine Log Messages (9442) TOPS VSN Log and alarm messages 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.
65 TOPS VSN Log and alarm messages 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.
66 T1 Resource Manager Log Messages (9443) TOPS VSN Log and alarm messages Description: A T1 Maintenance error has been reported. Action: Exit, then re-access T1 Maintenance. 0001/0000 Message: T1 Link Error for T1 SRU in Cabinet [cabinet_id], Slot [slot_id].
T1 Resource Manager Log Messages (9443) 67 TOPS VSN Log and alarm messages 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.
.
69 TOPS VSN Log and alarm messages 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.
70 Locality Database Log Messages (944E) TOPS VSN Log and alarm messages 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.
Locality Database Log Messages (944E) 71 TOPS VSN Log and alarm messages 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.
.
73 TOPS VSN Log and alarm messages 16. ACPE Maintenance Position log messages - 9445 9945/0004 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.
.
75 TOPS VSN Log and alarm messages 17. Prompt manager log messages - 9451 0100/0101 Message: User logged in <user name> Description: This message is informative only, confirming that the user with the <user name> has logged in. Action: None.
76 Prompt Manager Log Messages (9451) TOPS VSN Log and alarm messages 0200/0201 Message: Forced Exit <procedure name> <reason for exit> 0200/0202 Message: Archive Failure <reason for fa.
77 TOPS VSN Log and alarm messages 18. Suppressed and Thresholded Logs This section lists the system logs which have been suppressed or thresholded. The format for suppressed logs is <Config Number> <Report Number/Error Number>.
78 3. Suppressed and Thresholded Logs TOPS VSN Log and alarm messages 006D 00000038 File audit status 006D 00000039 OMCA: LOCATE ERROR 006D 0000003A OMCA: LOCATE ERROR (REPORTER) 0220 00000003 VIRM CL.
Suppressed and Thresholded Logs 79 TOPS VSN Log and alarm messages 700 00020001 Campus resource manager 8700 00020002 Campus resource manager 8700 00020003 Campus resource manager 8700 00020004 Campus.
80 3. Suppressed and Thresholded Logs TOPS VSN Log and alarm messages 9442 00030013 48 2 T1 release error 9442 00030014 48 2 VI release error C302 00020018 100 2 VTP return code error C302 00020010 10.
81 TOPS VSN Log and alarm messages 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.
.
83 TOPS VSN Log and alarm messages 20. Abbreviations A list of abbreviations used in this Publication follows: ACPE Application call processing engine CLLI Common language location indicator DD Data d.
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.
Ein wichtiger Punkt beim Kauf des Geräts Nortel Networks VSN04 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie Nortel Networks VSN04 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für Nortel Networks VSN04 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von Nortel Networks VSN04 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über Nortel Networks VSN04 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon Nortel Networks VSN04 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von Nortel Networks VSN04 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit Nortel Networks VSN04. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei Nortel Networks VSN04 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
