English dropdown-ico

Nortel Networks VSN04 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Nortel Networks VSN04, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Nortel Networks VSN04 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Nortel Networks VSN04. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Nortel Networks VSN04 should contain:
- informations concerning technical data of Nortel Networks VSN04
- name of the manufacturer and a year of construction of the Nortel Networks VSN04 item
- rules of operation, control and maintenance of the Nortel Networks VSN04 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Nortel Networks VSN04 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Nortel Networks VSN04, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Nortel Networks service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Nortel Networks VSN04.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Nortel Networks VSN04 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    Network operations systems TOPS Voice service node Log and alarm messages Release: VSN04 Status: Standard Version: 03.01[...]

  • Page 2

    [...]

  • Page 3

    © 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.01 Document release: VSN04 Date: August 1995 Network operations systems TOPS Voice service node Log and alarm messages[...]

  • Page 4

    [...]

  • Page 5

    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. Common TOPS VSN log messages -0201 13 5. Common TOPS VSN log messages - 0202 19 [...]

  • Page 6

    [...]

  • Page 7

    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. These are stored temporarily on the TOPS VSN and[...]

  • Page 8

    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. The date and time are displayed in the upper[...]

  • Page 9

    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). The logs produced from these two subsystems identify logins, logouts, changes to USERID[...]

  • Page 10

    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. The following changes to the TOPS VSN application were ma[...]

  • Page 11

    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. The first six tables list[...]

  • Page 12

    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.[...]

  • Page 13

    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. If the PRU declares itself faulty then the log subsystem detects [...]

  • Page 14

    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. Action: If the PRU is in the working state, no action [...]

  • Page 15

    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. Description: The software task failed because it encountered a segment or mapp[...]

  • Page 16

    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. The PRU may declare itself faulty or recreate the task. Action: If the [...]

  • Page 17

    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. Action: If the PRU is in the working state, no action is required. If the PRU is in the[...]

  • Page 18

    [...]

  • Page 19

    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. 0002/0001 Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] but [...]

  • Page 20

    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. 0002/0004 Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] bu[...]

  • Page 21

    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. Action may b[...]

  • Page 22

    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. Action: If the PRU is in the working stat[...]

  • Page 23

    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. User action is required. Description: The sending PRU could not co[...]

  • Page 24

    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. Record all action taken, and then contact NT.[...]

  • Page 25

    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. 0003/0001 Message: [PRU_name] received an IO error (Mixed_Access) on path [file[...]

  • Page 26

    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. If it is unable to do so, then it can declare itself faulty. Action: If t[...]

  • Page 27

    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. Description: The PRU encountered an error during an IO operation [...]

  • Page 28

    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. It is the responsibility of the PRU performing the operation [...]

  • Page 29

    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. If this action doesn't correct the problem, reboot the SRU. If the[...]

  • Page 30

    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. If it is unable to do so, then it can de[...]

  • Page 31

    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. (Accessing beyond the end of file). Description: Th[...]

  • Page 32

    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. If neither reboot operations are successful, then reboot the whole system. D[...]

  • Page 33

    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. If it is unable to do so, then it c[...]

  • Page 34

    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. Description: The PRU encountered an error d[...]

  • Page 35

    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. If neither reboot operations are successful, then reboot the whole syst[...]

  • Page 36

    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. If it is unable to do so, then it can de[...]

  • Page 37

    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. The operation wa[...]

  • Page 38

    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. If this action doesn't correct the problem, reboot the SRU. If the PRU [...]

  • Page 39

    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. If this action doesn't correct the problem, reboot the SRU. If the[...]

  • Page 40

    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. If it is unable to do so, then it can de[...]

  • Page 41

    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. The operation[...]

  • Page 42

    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. If this action doesn't correct the problem, reboot the SRU. If the PRU [...]

  • Page 43

    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. If it is unable to do so, then it c[...]

  • Page 44

    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. The operation was not performed. It is t[...]

  • Page 45

    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. It is the responsibility of the PRU performing the operation to [...]

  • Page 46

    [...]

  • Page 47

    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. Action: The user should make sure that th[...]

  • Page 48

    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. The PRU does not necessarily h[...]

  • Page 49

    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.] Description: The PRU tries to set the atomic commit for a Service Data [...]

  • Page 50

    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. Action: Record all inform[...]

  • Page 51

    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]. [Two 80 character lines of optional data.] Description: The PRU tries to read a Service Data Ma[...]

  • Page 52

    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] "Diagnostic String1" "Diagnostic String2" Description: This log indicates an error in interpreting a field within the specified tup[...]

  • Page 53

    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. The maintenance notice PRU is sti[...]

  • Page 54

    [...]

  • Page 55

    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]. Description: Applications can not access the VIs because of a reference error in an SDM[...]

  • Page 56

    [...]

  • Page 57

    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>. Explanation: The ALIU has sensed remote activation of an alarm condition. The string stating the error is one of the following: FAN 1 FAILURE POWER CONVERTER 1 FAILURE POWER CO[...]

  • Page 58

    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. It must also be determined if the cabling from the DNC to the LIU is intact. 0005/0002 Message: Th[...]

  • Page 59

    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. All calls the ACPE was processing at the time the PRU died, are lost. If the [...]

  • Page 60

    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. This value is reset by the next interaction with the ACPE. Action: No action. 0000/000F Message:[...]

  • Page 61

    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. Call processing continues as usual and no effect to[...]

  • Page 62

    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. Call proce[...]

  • Page 63

    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. At initialization time this log is considered a normal occurrence. At any other time it is n[...]

  • Page 64

    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. The reason is one of the following: 1) Messa[...]

  • Page 65

    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. [Two 80 character lines of optional data.] Description: This [...]

  • Page 66

    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. Action: No acti[...]

  • Page 67

    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]. Description: This log is generated if a duplicate string is detected by the ACPE when read[...]

  • Page 68

    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. 0003/0009 Message: ACPE error. A software error has been detect[...]

  • Page 69

    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]. Debugging Information: T1RM code: [d[...]

  • Page 70

    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. This call will be handled according to the datafill of[...]

  • Page 71

    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. The reason for the error may one of many (too many to list) but is clearly identified in the bod[...]

  • Page 72

    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]. Condition = [string]. Error Level = [string]. Description: There is a link error for the T[...]

  • Page 73

    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. Action: No action. 0003/0001 Message: Voice Link Alarm Event for T[...]

  • Page 74

    [...]

  • Page 75

    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. Description: This is an information message only. Action: None. 0000/0001 Message: The LDB[...]

  • Page 76

    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. [...]

  • Page 77

    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. All MMI operations will be aborted. The first diagnostic string describes [...]

  • Page 78

    [...]

  • Page 79

    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. xxxxx are two strings [...]

  • Page 80

    [...]

  • Page 81

    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. 0100/0102 Message: User logged out <user name> Description: This message is informative on[...]

  • Page 82

    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 failure> 0200/0203 Message: Restore Failure <reason for failure> 0200/0204 Message: Bad system command <procedure name> <command> 0[...]

  • Page 83

    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>. The format for thresholded logs is <Config Number> <Report Number/Error Number> <Maximum Thres[...]

  • Page 84

    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 CLEARING ANY ALARMS 8004 00020007 COULD NOT SEND NOTIFICATION 800C 00010002 OAR, change state 800C 00010003 OAR, registration 800C 00020005 OAR, unable [...]

  • Page 85

    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 resource manager 8700 00020005 Campus resource manager 8700 00020006 Campus resource manager 8700 00020007 Campus resource manager 8700 00020008 Camp[...]

  • Page 86

    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 100 2 Link Error C302 00020017 100 2 Port Error C302 0002000F 100 2 No response from peer[...]

  • Page 87

    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. table VSNALARM on the DMS, which is datafilled by the operating company, adds severity and textu[...]

  • Page 88

    [...]

  • Page 89

    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 dictionary DMS Digital multiplex system DNC Dynamic network control DTMF Dual tone multifrequency IEEE Institute of Electrical and Electronic Engineers[...]

  • Page 90

    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.01 Standard August 1995 Printed in the United States of America[...]