Nokia Base Station Alarms(1000-1999)

Published on March 2017 | Categories: Documents | Downloads: 45 | Comments: 0 | Views: 289

of 241

Content

Nokia Siemens Networks
GSM/EDGE BSS, rel.
RG10(BSS), operating
documentation, issue 05
Reference
Disturbance Printouts (1000-1999)
DN9813048
Issue 18-2
Approval Date 2009-12-17
2 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2010. All rights reserved
f Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-
nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-
zungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
DN9813048
Issue 18-2
3
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
Table of Contents
This document has 241 pages.
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 List of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Disturbance printout parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3 1001 UNIT RESTARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4 1002 RAM FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 1003 PARITY ERROR IN RAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS. . 21
7 1005 PLUG-IN UNIT RESTARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8 1007 RESTARTED PROGRAM BLOCK . . . . . . . . . . . . . . . . . . . . . . . . 23
9 1008 MML PROGRAM RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE . . . . . . . . 25
11 1012 EXCESSIVE RESTARTS OF UNIT . . . . . . . . . . . . . . . . . . . . . . . 26
12 1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED. . . . . . . 27
13 1015 OPERATING SYSTEM ERROR COUNTER INCREASED . . . . . 28
14 1016 MB INTERFACE FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
15 1018 PROGRAM BLOCK COMMUNICATION ERROR . . . . . . . . . . . . 30
16 1019 PROGRAM BLOCK ACTION FAILURE . . . . . . . . . . . . . . . . . . . . 31
17 1020 PROGRAM BLOCK START UP FAILURE. . . . . . . . . . . . . . . . . . 32
18 1021 PROGRAM BLOCK REWARMING STARTED. . . . . . . . . . . . . . . 34
19 1022 PROGRAM BLOCK WARMUP FAILURE. . . . . . . . . . . . . . . . . . . 35
20 1023 EXCESSIVE DISTURBANCES IN SUPERVISION . . . . . . . . . . . 36
21 1024 HAND PROCESS ERROR IN PROGRAM BLOCK . . . . . . . . . . . 37
22 1028 RESTARTED PROGRAM BLOCK IN PREPROCESSOR UNIT . 39
23 1029 SCCP STP MESSAGE PREVENTION. . . . . . . . . . . . . . . . . . . . . 40
24 1033 OSI CLNS CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . 43
25 1034 MAXIMUM SEQUENCE NUMBER OF OSI CLNS EXCEEDED . 44
26 1035 UPU MESSAGE RECEIVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
27 1044 ERROR IN SWITCH COMPARE TEST . . . . . . . . . . . . . . . . . . . . 47
28 1045 ERROR BETWEEN MARKER TABLES AND SWITCH CONTROL
MEMORY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
29 1047 NO RESPONSE FROM CONTROLLER OF SWITCHING NET-
WORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
30 1048 CONTROLLER OF SWITCHING NETWORK RESTARTED. . . . . 52
31 1049 SEMIPERMANENT MULTICHANNEL CONNECTION MISSING. 53
32 1055 TCAP TRANSACTION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 54
33 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM. . . 56
34 1058 ERROR IN SMUX PLUG-IN UNIT. . . . . . . . . . . . . . . . . . . . . . . . . 58
35 1061 ERROR IN SWITCH COMPARE TEST. . . . . . . . . . . . . . . . . . . . . 59
36 1062 ERROR BETWEEN MARKER TABLES AND SWITCH CONTROL
MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
37 1064 UNIT UPDATE FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
38 1065 DISK UPDATE FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
39 1070 CCS7 PROGRAM BLOCK DATA ERROR . . . . . . . . . . . . . . . . . . 63
40 1071 PROCESSOR TIME SHORTAGE . . . . . . . . . . . . . . . . . . . . . . . . . 64
41 1072 SIGNALLING LINK OUT OF SERVICE. . . . . . . . . . . . . . . . . . . . . 66
42 1076 FORCED LIGHTWEIGHT SCHEDULING. . . . . . . . . . . . . . . . . . . 69
43 1077 FREE STACK SIZE BELOW LIMIT . . . . . . . . . . . . . . . . . . . . . . . . 70
44 1078 PROCESS EXCEPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
45 1080 PROCESS STOPPED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
46 1082 HAND USAGE LIMIT EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . 75
47 1083 SEMAPHORE USE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
48 1089 DYNAMIC LDT SLOTS EXHAUSTED. . . . . . . . . . . . . . . . . . . . . . 77
49 1090 BUFFER HANDLE ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
50 1092 COMMUNICATION FAILURE IN FIELD REPORTING . . . . . . . . . 79
51 1093 OUTPUT FAILURE IN FIELD REPORTING . . . . . . . . . . . . . . . . . 80
52 1095 TRAFFIC MEASUREMENT OUTPUT FAILURE. . . . . . . . . . . . . . 82
53 1098 TOO LONG MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
54 1103 SIGNALLING MEASUREMENT REPORT LOST . . . . . . . . . . . . . 85
55 1105 LINE SIGNALLING RECEIVE OVERLOAD. . . . . . . . . . . . . . . . . . 88
56 1125 TRIAL CONFIGURATION DELETED . . . . . . . . . . . . . . . . . . . . . . 89
57 1128 EXCESSIVE DISTURBANCES IN FILE LOADING. . . . . . . . . . . . 90
58 1136 SIGNALLING MESSAGE DISTRIBUTION ERROR . . . . . . . . . . . 91
59 1137 INCORRECT SIGNALLING MESSAGE FROM SIGNALLING TER-
MINAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
60 1140 FREE LDT SLOT COUNT BELOW LIMIT . . . . . . . . . . . . . . . . . . . 94
61 1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL . . . . 96
DN9813048
Issue 18-2
5
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
62 1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED . 97
63 1143 AMOUNT OF FREE MEMORY REDUCED . . . . . . . . . . . . . . . . . 99
64 1144 FREE BUFFER HEADERS EXHAUSTING . . . . . . . . . . . . . . . . 100
65 1147 MESSAGE QUEUE OVERFLOW. . . . . . . . . . . . . . . . . . . . . . . . 101
66 1148 EXCESSIVE TRAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
67 1162 FILE SYSTEM COMMUNICATION ERROR . . . . . . . . . . . . . . . 104
68 1165 BUFFER ALLOCATION FAILED . . . . . . . . . . . . . . . . . . . . . . . . 105
69 1169 FREEZING PERIOD OF SS7 REPORTING LOST . . . . . . . . . . 107
70 1178 PREPROCESSOR UNIT DISTURBANCE . . . . . . . . . . . . . . . . . 109
71 1182 PREPROCESSOR UNIT RESTARTED . . . . . . . . . . . . . . . . . . . 110
72 1190 EXCESSIVE ERRORS IN SCP . . . . . . . . . . . . . . . . . . . . . . . . . 111
73 1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION 112
74 1204 WATCHDOG CAUSES UNIT RESTART . . . . . . . . . . . . . . . . . . 113
75 1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM.
114
76 1210 PHASE ADVANCE OF TIMING SIGNAL CHANGED. . . . . . . . . 115
77 1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED. . 117
78 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED. . 119
79 1222 DATA WRITING VIA VDS DEVICE FAILED. . . . . . . . . . . . . . . . 121
80 1228 UNIT SUPERVISION NOT FUNCTIONING . . . . . . . . . . . . . . . . 122
81 1234 UPDATE OF PASSWORD VALIDITY TIME FAILED. . . . . . . . . 123
82 1240 SCCP DISTURBANCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
83 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR .
127
84 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR 132
85 1244 RUNNING OUT OF MESSAGE BUFFERS . . . . . . . . . . . . . . . . 136
86 1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED
AGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
87 1250 DATA LINK LAYER PROTOCOL MISMATCH. . . . . . . . . . . . . . 139
88 1251 EXCESSIVE RETRANSMISSIONS ON DATA LINK CONNECTION
140
89 1252 EXCESSIVE ERROR RATE ON DATA LINK CONNECTION . . 142
90 1253 NO RESPONSE FROM PRIMARY RATE ACCESS TERMINAL 143
91 1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT. . . . . . . . . . 144
92 1255 PRIMARY RATE ACCESS MESSAGE DISTRIBUTION ERROR145
6 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
93 1256 INCORRECT PRD MESSAGE FROM PRIMARY RATE ACCESS
TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
94 1260 X.25/ETHERNET DATA TERMINAL SPONTANEOUS RESTART. .
147
95 1261 OSI CHANNEL GROUP UNREACHABLE . . . . . . . . . . . . . . . . . 148
96 1262 OSI SERVICE PROVIDER RESET . . . . . . . . . . . . . . . . . . . . . . . 149
97 1263 OSI SERVICE PROVIDER INTERFACE ERROR. . . . . . . . . . . . 150
98 1264 OSI INCOMING CALL DENIED. . . . . . . . . . . . . . . . . . . . . . . . . . 151
99 1273 ASP ACTIVATION FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
100 1280 INTERNAL COMMUNICATION CHANNEL FAILURE. . . . . . . . . 161
101 1282 ASSOCIATION PARAMETER FAILURE. . . . . . . . . . . . . . . . . . . 163
102 1293 SCCP GT SCREENING APPLIED . . . . . . . . . . . . . . . . . . . . . . . 165
103 1300 SUPERVISION CONNECTION TO UNIT LOST . . . . . . . . . . . . . 169
104 1301 PCU DIGITAL SIGNAL PROCESSOR RESTART . . . . . . . . . . . 170
105 1302 PAGING OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
106 1339 ACTIVE FRAMER UNIT FAILURE . . . . . . . . . . . . . . . . . . . . . . . 172
107 1340 HOTLINK FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
108 1347 CS PAGING COORDINATION ACTIVATION/DEACTIVATION
FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
109 1400 AFS RESTARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
110 1423 NO RESPONSE FROM MAIN CLOCK . . . . . . . . . . . . . . . . . . . . 178
111 1425 OVERFLOW IN ALARM BUFFERING. . . . . . . . . . . . . . . . . . . . . 179
112 1431 MMI SYSTEM OVERLOAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
113 1432 DISTURBANCE IN COMMAND CALENDAR . . . . . . . . . . . . . . . 181
114 1548 MTP CONFUSION MESSAGE RECEIVED. . . . . . . . . . . . . . . . . 188
115 1557 EVENT HANDLER CANNOT WORK PROPERLY DUE TO FILE
SERVICE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
116 1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED . . . . . 190
117 1570 SECURITY LOG ALARM LIMIT REACHED . . . . . . . . . . . . . . . . 191
118 1578 CONFUSION IN BSSMAP SIGNALING . . . . . . . . . . . . . . . . . . . 192
119 1580 GLOBAL RESET FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
120 1582 CONNECTION OR RELEASE ERROR. . . . . . . . . . . . . . . . . . . . 194
121 1583 LAPD MSG DISTRIBUTION PROBLEM . . . . . . . . . . . . . . . . . . . 196
122 1585 ABNORMAL A INTERFACE CIRCUIT RELEASE. . . . . . . . . . . . 197
123 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL . . . . . . 199
DN9813048
Issue 18-2
7
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
124 1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM. . . . . . . . . 200
125 1598 UNIT FOUND FAULTY BY ALARM SYSTEM . . . . . . . . . . . . . . 201
126 1623 ERROR DURING SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . 202
127 1630 RAM FAILURE IN SYNCHRONIZATION UNIT . . . . . . . . . . . . . 203
128 1660 UPDATE NUMBER MISMATCH. . . . . . . . . . . . . . . . . . . . . . . . . 204
129 1661 DATABASE MANAGER IN FATAL ERROR STATE . . . . . . . . . 205
130 1662 DATABASE LOADING ERROR . . . . . . . . . . . . . . . . . . . . . . . . . 206
131 1663 HAND RESERVATION ERROR IN DATABASE MANAGER. . . 208
132 1682 SCDFLE UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
133 1683 FAULTY UNIT SP-EX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
134 1684 SPARE UNIT WARMUP FAILURE. . . . . . . . . . . . . . . . . . . . . . . 211
135 1685 UNIT RESTART FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
136 1687 RECOVERY ACTION FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . 213
137 1688 FAILURE IN CALL CLEARING. . . . . . . . . . . . . . . . . . . . . . . . . . 214
138 1800 SCSI ADDRESS ILLEGAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
139 1801 MASS MEMORY FILE BACKUP FAILURE . . . . . . . . . . . . . . . . 216
140 1802 BACKUP COPY LOG FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . 217
141 1804 IP ROUTING RESOURCE SHORTAGE . . . . . . . . . . . . . . . . . . 219
142 1806 PRINTER SPOOLER DISABLED. . . . . . . . . . . . . . . . . . . . . . . . 220
143 1809 IP CONFIGURATION INQUIRY SERVICE FAILED. . . . . . . . . . 221
144 1850 BTS TEST REPORT PRINTOUT FAILED . . . . . . . . . . . . . . . . . 223
145 1860 DISK DISTURBANCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
146 1881 TAPI FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
147 1882 DMADI FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
148 1884 LABEL PARAMETER FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . 228
149 1885 ERROR IN WRITING DATA TO MAGNETIC TAPE. . . . . . . . . . 229
150 1886 ERROR IN TAPE OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . 230
151 1887 BLOCK COUNTER FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . 231
152 1891 AS7 RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
153 1893 O&M CHANNEL SEND OVERLOAD . . . . . . . . . . . . . . . . . . . . . 233
154 1894 NO RESPONSE TO AS7 SUPERVISION MESSAGE . . . . . . . . 234
155 1895 DISTURBANCE IN O&M CHANNEL . . . . . . . . . . . . . . . . . . . . . 235
156 1900 DEGRADED SLIP FREQUENCY. . . . . . . . . . . . . . . . . . . . . . . . 236
8 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941d
157 1901 ET RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
158 1910 COMMUNICATION FAILURE WITH TRX . . . . . . . . . . . . . . . . . . 238
159 1911 INVALID URGENCY LEVEL IN TRANSMISSION ALARM . . . . . 239
160 1915 TCSM CLOCK DISTURBANCE. . . . . . . . . . . . . . . . . . . . . . . . . . 241
DN9813048
Issue 18-2
9
Disturbance Printouts (1000-1999) Summary of Changes
Id:0900d805806a941a
Summary of Changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 18-2 and 18-1
New alarms
New alarm 1347 CS PAGING COORDINATION ACTIVATION/DEACTIVATION
FAILED has been added.
Changes made between issues 18-1 and 18-0
Modified alarms
The instructions of the alarm 1809 IP CONFIGURATION INQUIRY SERVICE FAILED
have been modified.
Changes made between issues 18-0 and 17-1
New alarms
New alarm 1339 ACTIVE FRAMER UNIT FAILURE has been added.
Modified alarms
The following alarms have been updated:
• 1071 PROCESSOR TIME SHORTAGE
• 1080 PROCESS STOPPED
• 1340 HOTLINK FAILURE
• 1583 LAPD MSG DISTRIBUTION PROBLEM
Changes made between issues 17-1and 17-0
Modified alarms
Information on the typical causes for refusing the CONFUSION message has been
updated in the Supplementary information fields of the printout 1578 CONFUSION IN
BSSMAP SIGNALING.
10 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
List of Alarms
1 List of Alarms
1001 UNIT RESTARTED
1002 RAM FAILURE
1003 PARITY ERROR IN RAM
1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS
1005 PLUG-IN UNIT RESTARTED
1007 RESTARTED PROGRAM BLOCK
1008 MML PROGRAM RESTARTED
1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE
1012 EXCESSIVE RESTARTS OF UNIT
1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED
1015 OPERATING SYSTEM ERROR COUNTER INCREASED
1016 MB INTERFACE FAILURE
1018 PROGRAM BLOCK COMMUNICATION ERROR
1019 PROGRAM BLOCK ACTION FAILURE
1020 PROGRAM BLOCK START UP FAILURE
1021 PROGRAM BLOCK REWARMING STARTED
1022 PROGRAM BLOCK WARMUP FAILURE
1023 EXCESSIVE DISTURBANCES IN SUPERVISION
1024 HAND PROCESS ERROR IN PROGRAM BLOCK
1028 RESTARTED PROGRAM BLOCK IN PREPROCESSOR UNIT
1029 SCCP STP MESSAGE PREVENTION
1033 OSI CLNS CONFIGURATION FAILED
1034 MAXIMUM SEQUENCE NUMBER OF OSI CLNS EXCEEDED
1035 UPU MESSAGE RECEIVED
1044 ERROR IN SWITCH COMPARE TEST
1045 ERROR BETWEEN MARKER TABLES AND SWITCH CONTROL
MEMORY
1047 NO RESPONSE FROM CONTROLLER OF SWITCHING NETWORK
1048 CONTROLLER OF SWITCHING NETWORK RESTARTED
1049 SEMIPERMANENT MULTICHANNEL CONNECTION MISSING
1055 TCAP TRANSACTION FAILURE
1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM
1058 ERROR IN SMUX PLUG-IN UNIT
1061 ERROR IN SWITCH COMPARE TEST
1062 ERROR BETWEEN MARKER TABLES AND SWITCH CONTROL
MEMORY
1064 UNIT UPDATE FAILURE
1065 DISK UPDATE FAILURE
DN9813048
Issue 18-2
11
Disturbance Printouts (1000-1999) List of Alarms
Id:0900d805806a941a
1070 CCS7 PROGRAM BLOCK DATA ERROR
1071 PROCESSOR TIME SHORTAGE
1072 SIGNALLING LINK OUT OF SERVICE
1076 FORCED LIGHTWEIGHT SCHEDULING
1077 FREE STACK SIZE BELOW LIMIT
1078 PROCESS EXCEPTION
1080 PROCESS STOPPED
1082 HAND USAGE LIMIT EXCEEDED
1083 SEMAPHORE USE ERROR
1089 DYNAMIC LDT SLOTS EXHAUSTED
1090 BUFFER HANDLE ERROR
1092 COMMUNICATION FAILURE IN FIELD REPORTING
1093 OUTPUT FAILURE IN FIELD REPORTING
1095 TRAFFIC MEASUREMENT OUTPUT FAILURE
1098 TOO LONG MESSAGE
1103 SIGNALLING MEASUREMENT REPORT LOST
1105 LINE SIGNALLING RECEIVE OVERLOAD
1125 TRIAL CONFIGURATION DELETED
1128 EXCESSIVE DISTURBANCES IN FILE LOADING
1136 SIGNALLING MESSAGE DISTRIBUTION ERROR
1137 INCORRECT SIGNALLING MESSAGE FROM SIGNALLING
TERMINAL
1140 FREE LDT SLOT COUNT BELOW LIMIT
1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL
1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED
1143 AMOUNT OF FREE MEMORY REDUCED
1144 FREE BUFFER HEADERS EXHAUSTING
1147 MESSAGE QUEUE OVERFLOW
1148 EXCESSIVE TRAPS
1162 FILE SYSTEM COMMUNICATION ERROR
1165 BUFFER ALLOCATION FAILED
1169 FREEZING PERIOD OF SS7 REPORTING LOST
1178 PREPROCESSOR UNIT DISTURBANCE
1182 PREPROCESSOR UNIT RESTARTED
1190 EXCESSIVE ERRORS IN SCP
1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION
1204 WATCHDOG CAUSES UNIT RESTART
1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM
1210 PHASE ADVANCE OF TIMING SIGNAL CHANGED
12 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
List of Alarms
1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED
1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED
1222 DATA WRITING VIA VDS DEVICE FAILED
1228 UNIT SUPERVISION NOT FUNCTIONING
1234 UPDATE OF PASSWORD VALIDITY TIME FAILED
1240 SCCP DISTURBANCE
1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR
1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR
1244 RUNNING OUT OF MESSAGE BUFFERS
1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED
AGE
1250 DATA LINK LAYER PROTOCOL MISMATCH
1251 EXCESSIVE RETRANSMISSIONS ON DATA LINK CONNECTION
1252 EXCESSIVE ERROR RATE ON DATA LINK CONNECTION
1253 NO RESPONSE FROM PRIMARY RATE ACCESS TERMINAL
1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT
1255 PRIMARY RATE ACCESS MESSAGE DISTRIBUTION ERROR
1256 INCORRECT PRD MESSAGE FROM PRIMARY RATE ACCESS
TERMINAL
1260 X.25/ETHERNET DATA TERMINAL SPONTANEOUS RESTART
1261 OSI CHANNEL GROUP UNREACHABLE
1262 OSI SERVICE PROVIDER RESET
1263 OSI SERVICE PROVIDER INTERFACE ERROR
1264 OSI INCOMING CALL DENIED
1273 ASP ACTIVATION FAILED
1280 INTERNAL COMMUNICATION CHANNEL FAILURE
1282 ASSOCIATION PARAMETER FAILURE
1293 SCCP GT SCREENING APPLIED
1300 SUPERVISION CONNECTION TO UNIT LOST
1301 PCU DIGITAL SIGNAL PROCESSOR RESTART
1302 PAGING OVERLOAD
1339 ACTIVE FRAMER UNIT FAILURE
1340 HOTLINK FAILURE
1347 CS PAGING COORDINATION ACTIVATION/DEACTIVATION FAILED
1400 AFS RESTARTED
1423 NO RESPONSE FROM MAIN CLOCK
1425 OVERFLOW IN ALARM BUFFERING
1431 MMI SYSTEM OVERLOAD
1432 DISTURBANCE IN COMMAND CALENDAR
DN9813048
Issue 18-2
13
Disturbance Printouts (1000-1999) List of Alarms
Id:0900d805806a941a
1548 MTP CONFUSION MESSAGE RECEIVED
1557 EVENT HANDLER CANNOT WORK PROPERLY DUE TO FILE
SERVICE FAILURE
1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED
1570 SECURITY LOG ALARM LIMIT REACHED
1578 CONFUSION IN BSSMAP SIGNALING
1580 GLOBAL RESET FAILURE
1582 CONNECTION OR RELEASE ERROR
1583 LAPD MSG DISTRIBUTION PROBLEM
1585 ABNORMAL A INTERFACE CIRCUIT RELEASE
1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL
1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM
1598 UNIT FOUND FAULTY BY ALARM SYSTEM
1623 ERROR DURING SUPERVISION
1630 RAM FAILURE IN SYNCHRONIZATION UNIT
1660 UPDATE NUMBER MISMATCH
1661 DATABASE MANAGER IN FATAL ERROR STATE
1662 DATABASE LOADING ERROR
1663 HAND RESERVATION ERROR IN DATABASE MANAGER
1682 SCDFLE UPDATE FAILURE
1683 FAULTY UNIT SP-EX
1684 SPARE UNIT WARMUP FAILURE
1685 UNIT RESTART FAILURE
1687 RECOVERY ACTION FAILURE
1688 FAILURE IN CALL CLEARING
1800 SCSI ADDRESS ILLEGAL
1801 MASS MEMORY FILE BACKUP FAILURE
1802 BACKUP COPY LOG FAILURE
1804 IP ROUTING RESOURCE SHORTAGE
1806 PRINTER SPOOLER DISABLED
1809 IP CONFIGURATION INQUIRY SERVICE FAILED
1850 BTS TEST REPORT PRINTOUT FAILED
1860 DISK DISTURBANCE
1881 TAPI FAILURE
1882 DMADI FAILURE
1884 LABEL PARAMETER FAILURE
1885 ERROR IN WRITING DATA TO MAGNETIC TAPE
1886 ERROR IN TAPE OPERATION
1887 BLOCK COUNTER FAILURE
14 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
List of Alarms
1891 AS7 RESTARTED
1893 O&M CHANNEL SEND OVERLOAD
1894 NO RESPONSE TO AS7 SUPERVISION MESSAGE
1895 DISTURBANCE IN O&M CHANNEL
1900 DEGRADED SLIP FREQUENCY
1901 ET RESTARTED
1910 COMMUNICATION FAILURE WITH TRX
1911 INVALID URGENCY LEVEL IN TRANSMISSION ALARM
1915 TCSM CLOCK DISTURBANCE
DN9813048
Issue 18-2
15
Disturbance Printouts (1000-1999) Disturbance printout parameters
Id:0900d805806a941a
2 Disturbance printout parameters
1200 DISTUR NONE 00:00 00:00 00:00 00:01:00
1204 DISTUR NONE 00:00 00:00 00:00 00:00:15
1207 DISTUR NONE 00:00 00:00 00:00 00:00:50
1210 DISTUR NONE 00:00 00:00 00:00 00:00:15
1220 DISTUR NONE 00:00 00:00 00:00 00:00:15
1221 DISTUR NONE 00:00 00:00 00:00 00:00:15
1222 DISTUR NONE 00:00 00:00 00:00 00:00:15
1228 DISTUR NONE 00:00 00:00 00:00 00:00:50
1234 DISTUR NONE 00:00 00:00 00:00 00:00:15
1240 DISTUR NONE 00:00 00:00 00:00 00:00:15
1241 DISTUR NONE 00:00 00:00 00:00 00:00:15
1242 DISTUR NONE 00:00 00:00 00:00 00:00:15
1244 DISTUR NONE 00:00 00:00 00:00 00:00:15
1249 DISTUR NONE 00:00 00:00 00:00 00:00:15
1250 DISTUR NONE 00:00 00:00 00:00 00:05:00
1251 DISTUR NONE 00:00 00:00 00:00 00:05:00
1252 DISTUR NONE 00:00 00:00 00:00 00:05:00
1253 DISTUR NONE 00:00 00:00 00:00 00:00:15
1254 DISTUR NONE 00:00 00:00 00:00 00:05:00
1255 DISTUR NONE 00:00 00:00 00:00 00:00:15
1256 DISTUR NONE 00:00 00:00 00:00 00:00:15
1260 DISTUR NONE 00:00 00:00 00:00 00:00:15
1261 DISTUR NONE 00:00 00:00 00:00 00:00:15
1262 DISTUR NONE 00:00 00:00 00:00 00:00:15
1263 DISTUR NONE 00:00 00:00 00:00 00:00:15
1264 DISTUR NONE 00:00 00:00 00:00 00:05:00
1273 DISTUR NONE 00:00 00:00 00:00 00:00:15
1280 DISTUR NONE 00:00 00:00 00:00 00:04:00
1282 DISTUR NONE 00:00 00:00 00:00 00:00:15
1293 DISTUR NONE 00:00 00:00 00:00 00:00:15
1300 DISTUR NONE 00:00 00:00 00:00 00:00:15
1301 DISTUR NONE 00:00 00:00 00:00 00:00:15
1302 DISTUR NONE 00:00 00:00 00:00 00:00:15
1339 DISTUR NONE 00:00 00:00 00:00 00:00:15
1340 DISTUR NONE 00:00 00:00 00:00 00:00:15
1347 DISTUR NONE 00:00 00:00 00:00 00:00:15
1400 DISTUR NONE 00:00 00:00 00:00 00:00:15
1423 DISTUR NONE 00:00 00:00 00:00 00:00:15
1425 DISTUR NONE 00:00 00:00 00:00 00:00:15
1431 DISTUR NONE 00:00 00:00 00:00 00:00:15
1432 DISTUR NONE 00:00 00:00 00:00 00:00:15
1548 DISTUR NONE 00:00 00:00 00:00 00:00:15
1557 DISTUR NONE 00:00 00:00 00:00 00:10:00
1569 DISTUR NONE 00:00 00:00 00:00 00:00:15
1570 DISTUR NONE 00:00 00:00 00:00 00:00:15
1578 DISTUR NONE 00:00 00:00 00:00 00:03:00
1580 DISTUR NONE 00:00 00:00 00:00 00:00:15
1582 DISTUR NONE 00:00 00:00 00:00 00:00:15
1583 DISTUR NONE 00:00 00:00 00:00 00:01:00
16 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
Disturbance printout parameters
1585 DISTUR NONE 00:00 00:00 00:00 00:05:00
1590 DISTUR NONE 00:00 00:00 00:00 00:00:15
1597 DISTUR NONE 00:00 00:00 00:00 00:00:15
1598 DISTUR NONE 00:00 00:00 00:00 00:00:15
1623 DISTUR NONE 00:00 00:00 00:00 00:02:00
1630 DISTUR NONE 00:00 00:00 00:00 00:00:15
1660 DISTUR NONE 00:00 00:00 00:00 00:00:15
1661 DISTUR NONE 00:00 00:00 00:00 00:00:15
1662 DISTUR NONE 00:00 00:00 00:00 00:00:15
1663 DISTUR NONE 00:00 00:00 00:00 00:00:15
1682 DISTUR NONE 00:00 00:00 00:00 00:00:15
1683 DISTUR NONE 00:00 00:00 00:00 00:00:15
1684 DISTUR NONE 00:00 00:00 00:00 00:10:10
1685 DISTUR NONE 00:00 00:00 00:00 00:00:15
1687 DISTUR NONE 00:00 00:00 00:00 00:01:15
1688 DISTUR NONE 00:00 00:00 00:00 00:00:15
1800 DISTUR NONE 00:00 00:00 00:00 00:00:15
1801 DISTUR NONE 00:00 00:00 00:00 00:00:15
1802 DISTUR NONE 00:00 00:00 00:00 00:00:15
1804 DISTUR NONE 00:00 00:00 00:00 00:00:15
1806 DISTUR NONE 00:00 00:00 00:00 00:00:15
1809 DISTUR NONE 00:00 00:00 00:00 00:00:15
1850 DISTUR NONE 00:00 00:00 00:00 00:05:00
1860 DISTUR NONE 00:00 00:00 00:00 00:01:15
1881 DISTUR NONE 00:00 00:00 00:00 00:01:30
1882 DISTUR NONE 00:00 00:00 00:00 00:00:15
1884 DISTUR NONE 00:00 00:00 00:00 00:00:15
1885 DISTUR NONE 00:00 00:00 00:00 00:01:05
1886 DISTUR NONE 00:00 00:00 00:00 00:00:15
1887 DISTUR NONE 00:00 00:00 00:00 00:00:15
1891 DISTUR NONE 00:00 00:00 00:00 00:00:15
1893 DISTUR NONE 00:00 00:00 00:00 00:00:15
1894 DISTUR NONE 00:00 00:00 00:00 00:03:00
1895 DISTUR NONE 00:00 00:00 00:00 00:01:30
1900 DISTUR NONE 00:00 00:00 00:00 00:00:15
1901 DISTUR NONE 00:00 00:00 00:00 00:00:15
1910 NOTICE NONE 00:00 00:00 00:00 00:00:15
1911 DISTUR NONE 00:00 00:00 00:00 00:00:15
1915 DISTUR NONE 00:00 00:00 00:00 00:00:15
DN9813048
Issue 18-2
17
Disturbance Printouts (1000-1999) 1001 UNIT RESTARTED
Id:0900d805806a941a
3 1001 UNIT RESTARTED
Meaning
The unit has restarted.
Supplementary information fields
1 working state of the unit
2 type of unit restart indicated by the initial loading program
block (e.g. BOLERO):
FF cold restart
00 warm restart
01 hot restart
02 diagnostic restart
type of unit restart indicated by the state administration:
AA not defined
3 information on the unit restart:
00 spontaneous
01 executed by the user
02 executed by the recovery program block
03 executed by the recovery program block, the package
identifier of the unit differs from that in the
active maintenance computer
04 spontaneous repeated
05 executed with the service terminal command ZAU
06 the recovery program block has restarted the unit
as a result of the alarm 1023
07 IWMANA has restarted the unit at the request of
routine testing
08 the recovery program block has restarted the unit
as a result of the alarm 1128
09 the recovery program block has restarted the unit
in connection with a state change, because virtual
loading was still in process in the unit
4 type of restart in the Working State and
Configuration File (SCDFLE) when the unit is
restarting:
00 warm restart
01 hot restart
55 mini restart
If the active maintenance computer (normally the OMU)
18 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1001 UNIT RESTARTED
was restarted with the MML command USU and R=HOT was
given as the restart type, the value of the field
is 00. The type of restart was, however, a hot
restart, if the value of supplementary information
field 2 is 01 hot restart.
5 code loading type when the unit is restarting:
00 optimal loading
01 total loading
02 total loading from disk
If the active maintenance computer (normally the OMU)
was restarted with the MML command USU and C=TOT or
C=DISK was given as the code loading type, the value
of the field is 01. Nevertheless, the loading was
performed from disk.
6 file loading type when the unit is restarting:
00 unknown/not defined
01 virtual loading
02 immediate loading
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
19
Disturbance Printouts (1000-1999) 1002 RAM FAILURE
Id:0900d805806a941a
4 1002 RAM FAILURE
Meaning
The RAM test program of the computer has observed a malfunction
in the RAM memory.
Supplementary information fields
1 address of the faulty memory location
0...FFFFFFFF
Instructions
If the alarm recurs, the CPU is probably faulty and needs to be replaced.
The alarm supports the activation of the automatic recovery for
the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
20 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1003 PARITY ERROR IN RAM
5 1003 PARITY ERROR IN RAM
Meaning
Parity error in the RAM of the computer. The parity supervision
circuit of the CPU has detected the error.
Supplementary information fields
1 address of location where the RAM test was being carried
out when the error was detected
Instructions
If the alarm recurs, the CPU is probably faulty and needs to be replaced.
The alarm supports the activation of the automatic recovery for
the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
21
Disturbance Printouts (1000-1999) 1004 COMMUNICATION ERROR BETWEEN PRO-
GRAM BLOCKS
Id:0900d805806a941a
6 1004 COMMUNICATION ERROR BETWEEN
PROGRAM BLOCKS
Meaning
The partner program block does not reply to the message sent to it
within the specified time limit, or the received reply is erroneous.
Supplementary information fields
1 error code
01 no reply
02 identification of reply is erroneous
03 status of reply is erroneous
04 sequence number of reply is erroneous
2 family identifier of program block setting the alarm
3 unit message bus address of the partner program block
4 family identifier of the partner program block
5 identifier of the message sent to the partner program block
6 subidentifier of the message sent to the partner program block
7 case-specific additional information
8 case-specific additional information
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
22 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1005 PLUG-IN UNIT RESTARTED
7 1005 PLUG-IN UNIT RESTARTED
Meaning
A plug-in unit has restarted.
Supplementary information fields
1 type of plug-in unit
See Diagnostics and Testing, Appendices
2 index of plug-in unit
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery for
the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
23
Disturbance Printouts (1000-1999) 1007 RESTARTED PROGRAM BLOCK
Id:0900d805806a941a
8 1007 RESTARTED PROGRAM BLOCK
Meaning
The program block has been restarted.
Supplementary information fields
1 family identifier of the program block
2 error code
131d: program block was not found
132d: another program block of the same kind already exists
133d: program block deletion error
287d: program block has been deleted, or its creation failed
302d: program block has made a memory protection error
770d: program block did not answer the supervision message
771d: program block has acknowledged the supervision message
with a wrong state, i.e the program block is in wrong state
in relation to the working state of the unit
781d: state transition of the program block did not succeed
You can check its meaning in General Error Messages of System
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
24 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1008 MML PROGRAM RESTARTED
9 1008 MML PROGRAM RESTARTED
Meaning
The MMI Manager (MMIMAN) has restarted an MML program.
Supplementary information fields
1 family identifier of the restarted MML program
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
25
Disturbance Printouts (1000-1999) 1010 NO RESPONSE TO UNIT SUPERVISION MES-
SAGE
Id:0900d805806a941a
10 1010 NO RESPONSE TO UNIT SUPERVISION
MESSAGE
Meaning
The unit has not responded in the allotted time to a supervision
message sent by the supervisory unit.
Supplementary information fields
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
26 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1012 EXCESSIVE RESTARTS OF UNIT
11 1012 EXCESSIVE RESTARTS OF UNIT
Meaning
The maximum number of restarts set for a unit has been exceeded.
Supplementary information fields
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
27
Disturbance Printouts (1000-1999) 1014 PROCESSOR LOAD RATE ALARM LIMIT EX-
CEEDED
Id:0900d805806a941a
12 1014 PROCESSOR LOAD RATE ALARM
LIMIT EXCEEDED
Meaning
The processor load rate exceeds the alarm limit defined for the unit at
intervals of time defined for the unit. The alarm limit and the interval
are defined in BSPARA file.
Supplementary information fields
1 processor load rate percentage
2 interval in hundredths of a second
Instructions
Check the validity of the value set for the parameter
CPU LOAD SUPERVISION LIMIT of BSPARA with the MML command:
ZDOT:<unit type>;
or find out the possible cause of overload.
This alarm may be given during the system reset because reset causes
load. In those cases, no actions are required from the user.
To change processor load supervision limit, give the MML command:
ZDOM:<unit type>:PROLL=<new supervision limit>;
Cancelling
No cancelling.
28 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1015 OPERATING SYSTEM ERROR COUNTER IN-
CREASED
13 1015 OPERATING SYSTEM ERROR
COUNTER INCREASED
Meaning
The alarm informs that the value of the error counter maintained
by the operating system has increased.
Supplementary information fields
1 error code: identifies the fault that increased the counter thus
causing the alarm. You can check its meaning in General Error
Messages of System
2 program block that increased the counter
3 value of the counter, i.e. number of errors
Instructions
Ascertain the reason for counter incrementation.
Cancelling
No cancelling.
DN9813048
Issue 18-2
29
Disturbance Printouts (1000-1999) 1016 MB INTERFACE FAILURE
Id:0900d805806a941a
14 1016 MB INTERFACE FAILURE
Meaning
In the test, the message bus interface (MBIF) has been detected
faulty. In the test, the unit sends a message to itself both on the
active and passive bus. It also checks the error counters of the
message buses, maintained by the operating system.
Supplementary information fields
1 message bus test identifier:
1 message sending does not succeed despite several attempts
2 time supervision of message receiving has expired
3 received test message differs from the one sent
4 the transmission error counter of the MB has been incremented
5 the reception error counter of the MB has been incremented
6 time supervision of message sent with a group address has
expired
7 time supervision of message sent with a pair address has
expired
8 the supervision error counter of the MB has been incremented
2 message bus index
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery for
the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
30 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1018 PROGRAM BLOCK COMMUNICATION ERROR
15 1018 PROGRAM BLOCK COMMUNICATION
ERROR
Meaning
The partner program block does not respond within the
specified time to the message sent to it, or the reply
is faulty.
Supplementary information fields
1 family identifier of program block giving the alarm
2 number of the message sent to the partner program
block or number of the received message
3 error code
01 no reply
02 identification of reply is faulty
03 status of reply is faulty
04 sequence number of reply is faulty
4 number of missing reply messages
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
31
Disturbance Printouts (1000-1999) 1019 PROGRAM BLOCK ACTION FAILURE
Id:0900d805806a941a
16 1019 PROGRAM BLOCK ACTION FAILURE
Meaning
Errors detected in the state administration procedures of a
program block.
Supplementary information fields
1 family identifier of program block
2 program block type in the family table of DXPARA
0 : normal program block
<> 0 : program block is essential for unit
functioning
3 error code of the recovery block
770d: program block did not answer the supervision message
771d: program block has acknowledged the supervision
message with a wrong state. The program block
is in wrong state in relation to the working state
of the unit
You can check the meaning of other error codes in General
Error Messages of System
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting
amount of the alarm with the MML command ARO.
Cancelling
No cancelling.
32 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1020 PROGRAM BLOCK START UP FAILURE
17 1020 PROGRAM BLOCK START UP FAILURE
Meaning
When activating a program block an error has been detected which
occurred either when creating or activating the program block.
The fault may cause disturbances in the system, particularly if a
program block creation error is in question.
Supplementary information fields
1 family identifier of the detector of the error
2 the error code returned by the detector of the error,
presented according to the general error code. You can check
its meaning with a command of the service terminal extension
MRS or in General Error Messages of System
3 the message bus address of the unit where the error occurred
4 the family identification of the error-committing program block
Instructions
Additional information: Printouts of Starting Phases.
Check the meaning of the DX error code.
If the error code is:
770d: The program block has failed to respond within the
time limit to the activation message sent by the unit
state administration program block (USAPRO).
Possible causes are:
- The program block has made a memory protection error.
Check the log with the service terminal command ZSL.
Check the program block's check sum, service terminal
command ZSS.
Check the program block's version, service terminal
command ZSXP.
- The initialisation time allotted to the program block
is too short. Check whether the program block acknowledges
USAPRO at all.
Service terminal command ZOQ.
- The program block has detected an error in its
initialisation.
Check the error log with the service terminal command ZGD.
771d: The program block has acknowledged negatively the activation
message sent by USAPRO.
Possible causes are:
- The program block has detected an error in its
DN9813048
Issue 18-2
33
Disturbance Printouts (1000-1999) 1020 PROGRAM BLOCK START UP FAILURE
Id:0900d805806a941a
initialisation.
Check the version of the program block.
Check the error log with the service terminal command ZGD.
- The program block has been activated into a wrong state
with regard to the unit's operating state. Check the
supervision messages between the program block and
USAPRO (message numbers 0001 and 0002). If the program
block is constantly in a wrong state, USAPRO restarts
the program block.
See the RESTARTED PROGRAM BLOCK alarms, if any
(alarm number 1007).
819d: The starting up of a library manager has failed.
Possible causes are:
- A fault in the initialisation of one of the libraries
that the manager is responsible for. Check the versions
of the manager and the library, service terminal commands
ZSXP and ZSK.
Check the error log with the service terminal command ZGD.
- In the starting up of the library manager itself.
Check the previous sections (770d, 771d).
All other error codes indicate a program block creation error.
Probable causes are: a fault in the DXPARA family table, a faulty
loading module, a discrepancy between the parameters of the family
table and the loading module, a storage area sufficiently large and
free cannot be found.
Cancelling
No cancelling.
34 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1021 PROGRAM BLOCK REWARMING STARTED
18 1021 PROGRAM BLOCK REWARMING
STARTED
Meaning
The warming of the program block has been restarted. The rewarming
may have been caused by one of the following: the thermometer (THERMO)
has detected synchronization errors in the program block, the program
block has been reactivated, or its warming failed on the previous
occasion.
Supplementary information fields
1 family identifier of the detector of the error
USAPRO (A0): the detector of the error is the state
supervision
THERMO (16B): the detector of the error is the thermometer
If THERMO is the detector, a program block synchronization
error is in question.
2 identifier of the family to be warmed
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
35
Disturbance Printouts (1000-1999) 1022 PROGRAM BLOCK WARMUP FAILURE
Id:0900d805806a941a
19 1022 PROGRAM BLOCK WARMUP FAILURE
Meaning
The warming up of a program block has failed. The program block has
not acknowledged the warmup command sent by the unit state
administration program block (USAPRO), or has acknowledged it
negatively. The fault can lie in either the active or the spare unit.
The warming-up manager (WUPMAN) can also be the detector of the fault.
Supplementary information fields
1 family identifier of the detector of the error
USAPRO (A0): the detector is the state administration
WUPMAN (108): the detector is the warming-up manager
2 error code returned by the detector of the error.
You can check its meaning with a command of the service
terminal extension MRS or in General Error Messages of
System
3 message bus address of the unit where the error occurred
4 family identifier of the program block that made the error
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
36 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1023 EXCESSIVE DISTURBANCES IN SUPERVI-
SION
20 1023 EXCESSIVE DISTURBANCES IN
SUPERVISION
Meaning
The unit state administration program block (USAPRO) has detected a
serious error when supervising the functioning of the program blocks
of the unit. The alarm may have been caused by one of the following:
several program blocks have been restarted; or some critical program
block does not respond to the supervision, or refuses to respond to a
state transition command.
In addition, the alarm may result from repeated rewarmings of
program blocks or from synchronisation errors. The situation
leads to a restart of the unit.
Supplementary information fields
1 type of error
00: error in program block supervision
01: error in the warmup or synchronisation
of program blocks
2 family identifier of the detector of the error.
USAPRO (A0): detector is state administration
THERMO (16B): detector is the thermometer.
If THERMO is the detector, a synchronisation fault of
a critical program block is in question
error code returned by the detector of the error,
presented according to the general error code
65535d: no significance
You can check the meaning of error codes with a
command of the service terminal extension MRS or in
General Error Messages of System
message bus address of the unit where the error occurred
FFFF: no significance
family identifier of the program block that made the
error
FFFF: no significance
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
37
Disturbance Printouts (1000-1999) 1024 HAND PROCESS ERROR IN PROGRAM
BLOCK
Id:0900d805806a941a
21 1024 HAND PROCESS ERROR IN PROGRAM
BLOCK
Meaning
The requested service could not be carried out due to the
failure of process family resource (hands) management.
Supplementary information fields
1 ID of the system library service primitive that returned
the error code. The field may have the following values:
0: creation of hands
1: creation of additional hands
2: reservation of hand
3: renewal of hand reservation
4: expiry of hand reservation
5: restart of hand
6: deletion of hand group
2 error code returned by system library service primitive.
See General Error Messages of System for error code
explanations
3 type of reserved hand/hand to be reserved. 0 if not known
4 number of reserved hand/hand to be reserved
5 life focus of the hand
6 computer address of the customer
7 family ID of the customer
8 process ID of the customer
9 life focus of the customer
Instructions
Reservation of a hand fails typically in situation where all
available hands have already been reserved (e.g. overload
situations). If the fault situation (supplementary field 1
value = 02) occurs only occasionally, the disturbance requires
no actions from the user.
In other cases, fill in a Problem Report and send it to your
local Nokia Siemens Networks representative. Enclose the
printouts obtained with the service terminal commands ZSCFE,
ZGSC, ZSL, and with the F, D, H, and G commands of the FAM family
38 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1024 HAND PROCESS ERROR IN PROGRAM
BLOCK
extension.
Cancelling
No cancelling.
DN9813048
Issue 18-2
39
Disturbance Printouts (1000-1999) 1028 RESTARTED PROGRAM BLOCK IN PREPRO-
CESSOR UNIT
Id:0900d805806a941a
22 1028 RESTARTED PROGRAM BLOCK IN
PREPROCESSOR UNIT
Meaning
A program block has been restarted.
Supplementary information fields
1 plug-in unit index:
.. : control plug-in unit
other values: line terminal plug-in unit
2 program block ID
3 error code:
770d : program block has not responded to supervision message
771d : program block has acknowledged supervision message with
wrong state, i.e. the program block is in the wrong
state in relation to the unit's working state
781d : failure in changing state of program block
287d : program block has been deleted, or its creation has
failed
302d : memory protection error by program block
131d : program block not found
132d : an identical program block already exists
133d : error in deleting program block
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
40 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1029 SCCP STP MESSAGE PREVENTION
23 1029 SCCP STP MESSAGE PREVENTION
Meaning
SCCP has detected at the signalling transfer point a signalling message
whose transit is wanted to be prevented or of which an alarm needs to be
issued.
If the transit message is destroyed, it may cause disturbance
in the function of the user parts of the signalling point that sent
the message. Usage restrictions for transit messages are usually set
on exchanges that function on another operator's interface.
Supplementary information fields
1 type of access right violation of the STP function (cause code)
01 the source point in question should not send signalling
messages to the destination point (the message has been
transmitted)
02 the source point in question is not allowed to send
signalling messages to the destination point (the message
has been destroyed or sent back)
03 the incoming link set in question should not be used to
send signalling messages to the destination point
(the message has been transmitted)
04 the incoming link set in question is not to be used to send
signalling messages to the destination point (the message
has been destroyed or sent back)
05 the pointer of the global title in the calling party address
global title is not permitted (the message has been
destroyed or sent back)
06 no analysis can be found for the root of the calling party
address global title (the message has been destroyed or
sent back)
2 destination point signalling network, which can get the
following values:
00 international network 0, IN0
04 international network 1, IN1
08 national network 0, NA0
0C national network 1, NA1
3 destination point code value of the processed signalling message
4 originating point signalling network, which can get the
following values:
00 international network 0, IN0
04 international network 1, IN1
DN9813048
Issue 18-2
41
Disturbance Printouts (1000-1999) 1029 SCCP STP MESSAGE PREVENTION
Id:0900d805806a941a
08 national network 0, NA0
0C national network 1, NA1
5 originating point code value of the processed signalling message
6-10 if Supplementary information field 1 has the value 01,
02, 03 or 04, the value (5 sequential bytes) indicates the
signalling point code of the signalling point and the
signalling network, from which the signalling message was
received. The field is coded so that the first byte
indicates the signalling network and the next four indicate
the signalling point code. E.g. the signalling point 260 of
the NA0 network would be coded as follows:
08 00 00 02 60
If Supplementary information field 1 has the value 05 or
06, the value indicates the root parameter values of the calling
party address global title in the following order:
- the standard of the global title
- global title indicator (GTI)
- translation type (TT)
- numbering plan + encoding type (NP+ENC)
- nature of address indicator (NAI)
If a field has the value FF, the root parameter in question is
not defined on the value of that global title indicator (GTI)
Instructions
Procedures on the basis of the value of Supplementary information
field 1 (cause code):
Cause codes 01 and 02:
SCCP screening information says that messages originating from the
signalling point mentioned in Supplementary information field 5
should not be transferred to the destination point. Check if this
restriction is justified and remove the blocking with the MML
command ODM if necessary. In other case the operator who owns the
signalling point mentioned in Supplementary information fields 4
and 5 should be notified about an access right violation.
Cause codes 03 and 04:
SCCP screening information says that messages originating from
the signalling network and the adjacent signalling point (channel
system) mentioned in Supplementary information field 6 should not
be transferred to the destination point. Check if this restriction
is justified and remove the blocking with the MML command ODM, if
necessary. In other case the operator who owns the adjacent
signalling point mentioned in Supplementary information field 6
42 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1029 SCCP STP MESSAGE PREVENTION
should be notified about an access right violation.
Cause code 05:
The calling party address of the received SCCP STP message uses a
global title indicator value that is prohibited in the parameter
set of the destination point mentioned in Supplementary information
fields 2 and 3. Check if this restriction is justified and remove
the restriction with the MML command OCM, if necessary. In other
case the operator who owns the signalling point mentioned in
Supplementary information fields 4 and 5 should be notified about
an access right violation.
Cause code 06:
The calling party address of the received SCCP STP message uses
a global title with root parameters that do not have a matching
analysis in the SCCP analysis information. Check if the root
parameters need to be analysed and remove the analysis with the
MML command OCM, if necessary. If the root parameters need to be
analysed, check if there should exist an analysis for the global
title in question, and create it with the MML command NBC, if
necessary. In other case the operator who owns the signalling
point mentioned in Supplementary information fields 4 and 5 should
be notified about an access right violation.
Cancelling
No cancelling.
DN9813048
Issue 18-2
43
Disturbance Printouts (1000-1999) 1033 OSI CLNS CONFIGURATION FAILED
Id:0900d805806a941a
24 1033 OSI CLNS CONFIGURATION FAILED
Meaning
The configuration of the connectionless OSI network service (CLNS)
has failed. This can be caused by either the time-out of the timer
that controls the approval of the configuration, or errors in the
configuration data. After a configuration failure, the system uses
the default value attributes for connectionless network services.
Supplementary information fields
1 the name of the CLNS used in the configuration
2 the type of the disturbance observation
0 type data is not available
1 time-out of the timer
2 an error during the configuration phase
3 an error during the attribute setting phase
3 a general error code which tells why the configuration of the
CLNS of the OSI failed. You can check its meaning in General
Error Messages of System
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
44 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1034 MAXIMUM SEQUENCE NUMBER OF OSI CLNS
EXCEEDED
25 1034 MAXIMUM SEQUENCE NUMBER OF OSI
CLNS EXCEEDED
Meaning
The number of a connectionless OSI network service (CLNS) has exceeded
the maximum value. This is probably due to a malfunction in the OSI
network IS routing equipment. Connectionless network service can not
be used for 20 minutes, during which time it is not possible to
transfer routing data or user data. This is to ensure that the
clearing of the number does not cause disturbances in other nodes,
but it is possible that there will be some interruptions in the OSI
services.
Supplementary information fields
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
45
Disturbance Printouts (1000-1999) 1035 UPU MESSAGE RECEIVED
Id:0900d805806a941a
26 1035 UPU MESSAGE RECEIVED
Meaning
The exchange has received a User Part Unavailable message (UPU).
This message informs the sending end of a signalling message that
the user part of the destination address is not available.
Depending on the unavailable user part (TUP and ISUP) the telephone
traffic and signalling traffic fail. In the case of SCCP, used
services fail.
Supplementary information fields
1 network from which the UPU message came:
network code network
------------ ------
00 national network 0
04 national network 1
08 international network 0
0C international network 1
2 header code of message
3 destination point code received in message, indicating
the destination point of the unavailable user part
4 user part identifier received in the user_part_info of
the message, indicating the unavailable user part in the
destination point (3rd supplementary information, DPC)
identifier user part
---------- ---------
00 spare
01 spare
02 spare
03 SCCP
04 TUP
05 ISUP
06 DUP
07 ) spare
... ) spare
0F MTP test user part
5 reason for the unavailability of the user part
(4th supplementary information), obtained from the
user_part_info of the message
46 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1035 UPU MESSAGE RECEIVED
code reason for unavailability
---- -------------------------
00 user part unknown in the DPC
01 user part has not been created, or
no service has been created for it
02 user part cannot be reached in the DPC
Instructions
If the message traffic of the user part concerned should be possible
to the destination point, check from the operator of the destination
point whether the user part has been created and whether it is
available.
Cancelling
No cancelling.
DN9813048
Issue 18-2
47
Disturbance Printouts (1000-1999) 1044 ERROR IN SWITCH COMPARE TEST
Id:0900d805806a941a
27 1044 ERROR IN SWITCH COMPARE TEST
Meaning
The comparison test of the switching network has observed an error.
The comparison test compares the incoming bit patterns with
the outgoing bit patterns in the connections of the switching network.
The problem can be caused by
- defective cabling
- faulty power supply of the exchange
- faulty plug-in unit of the switching network (SWSPS, SWCSM)
- faulty control processor of switching network (SWCOP)
Supplementary information fields
1 PCM line of the outgoing circuit
2 time slot of the outgoing circuit
3 PCM line of the incoming circuit
4 time slot of the incoming circuit
5 incoming bit pattern
6 outgoing bit pattern
Instructions
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of
the alarm with the MML command ARO.
To determine what has caused the alarm, proceed in
the following way:
1. Run the diagnosis for the unit that is the object unit of the alarm.
Bring the unit in the test state (TE) using the USC command and run
the diagnosis using the UDU command.
If the diagnosis cannot locate the fault, proceed to the next step.
2. Check the cabling. Check the physical connections of the SWCSM,
SWCOP, SWSPS plug-in units. Check that the cables are correctly in
place and that correct cable type has been used. If the problem
is not in the cabling, proceed to the next step.
3. Replace the SWSPS plug-in unit. See Instructions for Replacing
Plug-in Units.
If replacing the plug-in unit does not help, proceed to the next
step.
48 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1044 ERROR IN SWITCH COMPARE TEST
4. Replace the SWCOP plug-in unit. See Instructions for Replacing
Plug-in Units.
If replacing the plug-in unit does not help, proceed to the next
step.
5. The cause of the alarm can be external disturbances conducted
trough power supply. In this case the problem can be solved
only by removing the source of the disturbances.
Cancelling
No cancelling.
DN9813048
Issue 18-2
49
Disturbance Printouts (1000-1999) 1045 ERROR BETWEEN MARKER TABLES AND
SWITCH CONTROL MEMORY
Id:0900d805806a941a
28 1045 ERROR BETWEEN MARKER TABLES
AND SWITCH CONTROL MEMORY
Meaning
This alarm indicates a temporary defect in the switch control
memory. There is a difference between the data of the switch
control memory and the data of the switching file.
The problem can be caused by
- defective cabling
- faulty power supply of the exchange
- faulty plug-in unit of the switching network (SWCSM)
- faulty control processor of switching network (SWCOP)
Supplementary information fields
1 PCM line of the outgoing circuit
2 time slot of the outgoing circuit
3 PCM line of the incoming circuit in the control memory
4 time slot of the incoming circuit in the control memory
5 PCM line of the incoming circuit in the reserve table
6 time slot of the incoming circuit in the reserve table
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
To determine what has caused the alarm, proceed in
the following way:
1. Run the diagnosis for the unit that is the object unit of the alarm.
Bring the unit in the test state (TE) using the USC command and run
the diagnosis using the UDU command.
If the diagnosis cannot locate the fault, proceed to the next step.
2. Check the cabling. Check the physical connections of the SWCSM,
SWCOP plug-in units. Check that the cables are correctly in
place and that correct cable type has been used. If the problem
is not in the cabling, proceed to the next step.
3. Replace the SWCSM plug-in unit. See Instructions for Replacing
50 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1045 ERROR BETWEEN MARKER TABLES AND
SWITCH CONTROL MEMORY
Plug-in Units.
If replacing the plug-in unit does not help, proceed to the next
step.
4. Replace the SWCOP plug-in unit. See Instructions for Replacing
Plug-in Units.
If replacing the plug-in unit does not help, proceed to the next
step.
5. The cause of the alarm can be external disturbances conducted
trough power supply. In this case the problem can be solved
only by removing the source of the disturbances.
Cancelling
No cancelling.
DN9813048
Issue 18-2
51
Disturbance Printouts (1000-1999) 1047 NO RESPONSE FROM CONTROLLER OF
SWITCHING NETWORK
Id:0900d805806a941a
29 1047 NO RESPONSE FROM CONTROLLER
OF SWITCHING NETWORK
Meaning
The switch control processor (SWPRO or SWCOP) has not acknowledged the
supervision message sent by the supervising unit within the specified
time limit.
Supplementary information fields
1 type of the controller of GSW.
received.
2 index of the controller of GSW.
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
52 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1048 CONTROLLER OF SWITCHING NETWORK RE-
STARTED
30 1048 CONTROLLER OF SWITCHING
NETWORK RESTARTED
Meaning
The alarm informs of an erroneous switch control processor (SWCOP or
SWPRO) restart.
Supplementary information fields
1 type of the controller of GSW restarted
2 index of the controller of GSW
Instructions
The alarm requires no actions. The alarm supports the activation of
the automatic recovery for the object unit. You can check the supporting
amount of the alarm with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
53
Disturbance Printouts (1000-1999) 1049 SEMIPERMANENT MULTICHANNEL CONNEC-
TION MISSING
Id:0900d805806a941a
31 1049 SEMIPERMANENT MULTICHANNEL
CONNECTION MISSING
Meaning
The switching data of a semipermanent multichannel connection is
erroneous. The data in the files (SMWIBA/SMMUPO - HNCONN/LICONF) is
inconsistent.
Supplementary information fields
1 type of connection
(point-to-point connection PTP/point-to-multipoint connection PTM)
00 multichannel connection between two external PCM circuits
01 multichannel multipoint connection between external PCM
circuits
2 the connection's incoming PCM circuit, from SMWIBA/SMMUPO
3 the connection's incoming time slot, from SMWIBA/SMMUPO
4 the incorrect information, in the HNCONN/LICONF files, of
the connection's incoming PCM circuit
5 the incorrect information, in the HNCONN/LICONF files, of
the connection's incoming time slot
6 the connection's outgoing PCM circuit
7 the connection's outgoing time slot
8 error code:
01 connection is missing from HNCONN
02 connection is missing from LICONF
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
54 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1055 TCAP TRANSACTION FAILURE
32 1055 TCAP TRANSACTION FAILURE
Meaning
The Transaction Capabilities Application Part (TCAP)
of the common channel signalling system has detected an error
in the management of a transaction. The transaction has been
interrupted due to this error.
The disturbance has no effect on other transactions.
Supplementary information fields
1 type of the error. It can have the following values:
01 beginning the transaction has failed in the user's end,
TCAP has not located the SCCP computer unit
02 beginning the transaction has failed in the network
because the TCAP user has not stated the version of
TCAP to be used
03 beginning of the transaction has failed in the network
for unknown reasons
04 transaction has ended abnormally with the hand's time-out
05 transaction has ended abnormally for unknown reasons
06 sending a message to the user has failed
07 sending a message to the SCCP has failed
08 operation automatons have been used up
2 computer address of the party that requested the service
3 family identifier of the party that requested the service
4 process identifier of the party that requested the service
5 life focus of the party that requested the service
6 reference number in the DX log. The log contains additional
information on the error. If the reference number is
not used in the log, the value of the field is zero
Instructions
If the error in the first supplementary information field
is a type 4 error, and the alarm is given occasionally,
the alarm requires no actions.
In other cases, fill in a Problem Report and send it to
your local Nokia Siemens Networks representative. Include the
printouts obtained during the error situation from the message
monitoring process family 114 (TCAP), and with the service
terminal commands ZSCFE, ZGSC and ZSL as well as the FAM
DN9813048
Issue 18-2
55
Disturbance Printouts (1000-1999) 1055 TCAP TRANSACTION FAILURE
Id:0900d805806a941a
family extension commands F, D, H and G.
Cancelling
No cancelling.
56 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1056 MESSAGE FROM NETWORK TO UNKNOWN
SUBSYSTEM
33 1056 MESSAGE FROM NETWORK TO
UNKNOWN SUBSYSTEM
Meaning
SCCP has received a message from the network. The message's
destination is an unknown subsystem.
Supplementary information fields
1 type of the SCCP message that has an unknown subsystem as its
destination. It can have the following values:
01 CR Connection Request
02 CC Connection Confirm
03 CREF Connection Refused
04 RLSD Released
05 RLC Release Complete
06 DT1 Data Form 1
07 DT2 Data Form 2
08 AK Data Acknowledgement
09 UDT Unitdata
0A UDTS Unitdata Service
0B ED Expedited Data
0C EA Expedited Data Acknowledgement
0D RSR Reset Request
0E RSC Reset Confirm
0F ERR Protocol Data Unit Error
10 IT Inactivity Test
11 XUDT Extended Unitdata
12 XUDTS Extended Unitdata Service
13 LUDT Long Unitdata
14 LUDTS Long Unitdata Service
2 network indicator. It can have the following values:
00 international network 0
04 international network 1
08 national network 0
0C national network 1
3 destination point code
4 number of the destination subsystem unknown to SCCP. If the
message that is to be routed does not contain a subsystem number,
the field's value is FF
5 originating point code
6 number of the originating subsystem. If the message that is
to be routed does not contain a subsystem number, the field's
DN9813048
Issue 18-2
57
Disturbance Printouts (1000-1999) 1056 MESSAGE FROM NETWORK TO UNKNOWN
SUBSYSTEM
Id:0900d805806a941a
value is FF
7 reference number in the DX log. The log contains the incorrect
message. If the reference number is not used in the log, the
field's value is 0
Instructions
If the error occurs repeatedly, do the following:
If the value of Supplementary information field 4 is something other
than FF, check if the subsystem given in Supplementary information
field 4 has been created in the relevant signalling point of the
signalling network by using the signalling point's SCCP Data Handling
MML commands. The signalling point is given Supplementary information
field 3 and the signalling network in Supplementary information field
2.
If the subsystem has not been created, check if it should be created
in the system and, if necessary, create it with the MML commands of
the previously mentioned command group.
If the subsystem does not belong in the system, contact the network
operator of the signalling point mentioned in Supplementary information
field 5 to find out why they are trying to send messages to the
subsystem mentioned Supplementary information field 4.
If the value of Supplementary information field 4 is FF, the subsystem
number is missing from the destination data of the received message in
Supplementary information field 5 signalling point. The subsystem number
cannot be obtained through global title translation.
In other cases, fill in a Problem report and send it to your local
Nokia Siemens Networks representative. Include the printouts of
service terminal commands ZSCFE, ZGSC and ZSL in the report.
Cancelling
No cancelling.
58 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1058 ERROR IN SMUX PLUG-IN UNIT
34 1058 ERROR IN SMUX PLUG-IN UNIT
Meaning
The SMUX plug-in unit test has detected a fault in the plug-in
unit. The test is to check that the SMUX plug-in unit multiplexes
the 16 kbit/s channels correctly to the 64 kbit/s channel.
The test is carried out in the switching network by branching
time slots, coming to and leaving from the SMUX, to the SWCOP,
and by checking that the bit pattern contained in the time slots is
correct.
Supplementary information fields
1 index of SMUX plug-in unit
2 PCM circuit coming to SMUX plug-in unit
3 incoming time slot
4 PCM circuit outgoing from SMUX plug-in unit
5 outgoing time slot
6-9 four consecutive samples of bit patterns coming to
SMUX plug-in unit.
10-13four consecutive samples of bit patterns departing from
SMUX plug-in unit.
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
59
Disturbance Printouts (1000-1999) 1061 ERROR IN SWITCH COMPARE TEST
Id:0900d805806a941a
35 1061 ERROR IN SWITCH COMPARE TEST
Meaning
The comparing test of the switching network (GSWB) has detected an
error. The comparing test compares the bit pattern created in the
switching network by the switchings in the network to the
bit pattern leaving the switching network.
Supplementary information fields
1 outgoing PCM circuit (corresponds to a 4 Mbit/s circuit group)
2 outgoing PCM circuit's 8 kbit/s channel
3 incoming PCM circuit (corresponds to a 4 Mbit/s circuit group)
4 incoming PCM circuit's 8 kbit/s channel
5 incoming bit pattern
6 outgoing bit pattern
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
60 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1062 ERROR BETWEEN MARKER TABLES AND
SWITCH CONTROL MEMORY
36 1062 ERROR BETWEEN MARKER TABLES
AND SWITCH CONTROL MEMORY
Meaning
The switching data of the switching network control memory and the
incoming connections file is different.
Supplementary information fields
1 outgoing PCM circuit (corresponds to a 4 Mbit/s circuit group)
2 outgoing PCM circuit's 8 kbit/s channel
3 incoming PCM circuit in the control memory
4 incoming PCM circuit channel in the control memory
5 incoming PCM circuit in the incoming connections file
6 incoming PCM circuit channel in the incoming connections file
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
61
Disturbance Printouts (1000-1999) 1064 UNIT UPDATE FAILURE
Id:0900d805806a941a
37 1064 UNIT UPDATE FAILURE
Meaning
Failure in the updating of the partner unit or another unit to be
updated (M, SSU). The file has not been updated in the unit which
received the updating input, either.
Supplementary information fields
1 family identifier of the program block that detected
the failure
2 number of the message which caused the updating
3 unit to be updated
4 error code returned by the unit to be updated
16d REQMAN does not reply to the disk update
inquiry before time-out
106d file error
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the
alarm with the MML command ARO.
Cancelling
No cancelling.
62 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1065 DISK UPDATE FAILURE
38 1065 DISK UPDATE FAILURE
Meaning
A file modification made in the Central Memory has not been
updated onto disk. The data of the file on the disk does not
correspond to the data in the Central Memory.
Supplementary information fields
1 number of the message that caused the updating
2 error code returned by the file update (general error
message of the system). See General Error Messages of System
for error code explanations
3 file number
4 offset from the beginning of the file
Instructions
1. Check the alarms set by the File Updating Request Manager
Program Block (REQMAN).
2. Move the file shown in the additional information field 3
from the Central Memory to disk with the MML command DFC.
If moving the file to the disk fails, it is possible that
the operation of the switch suffers disturbances after the
next disk loading in so far as the operation has to do with
the file in question.
Cancelling
No cancelling.
DN9813048
Issue 18-2
63
Disturbance Printouts (1000-1999) 1070 CCS7 PROGRAM BLOCK DATA ERROR
Id:0900d805806a941a
39 1070 CCS7 PROGRAM BLOCK DATA ERROR
Meaning
A program block of the common channel signalling system has detected
an error in the working file of the MTP routing.
Supplementary information fields
1 error code
01 value of data exceeds the accepted range
02 record data are in conflict
03 value of stored data is in conflict with new value received
for that data
2 file number
3 record number
4 subrecord number
Instructions
In N+1 protected units the warming up of the files may have
already corrected the error detected. If the fault situation
is over, futher actions are not needed.
Examine the other alarms given by the unit using the MML command AHO.
If necessary, examine also the alarm history of the unit using the
MML command AHP. If the alarm occurs repeatedly, the files of the
CCS7 level 3 are likely to contain an error.
If the alarm still continues to occur, save the defective file
on disk for later examination for errors and contact the customer
support service. Check also the log print-outs of the unit.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
64 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1071 PROCESSOR TIME SHORTAGE
40 1071 PROCESSOR TIME SHORTAGE
Meaning
There is not enough processor time for all processes fit for running.
The operating system kernel has temporarily increased the priority of
those processes that have not received running time for some time.
The processor has a 100 utilization rate.
The situation results from a computer overload or a fault in some
processes.
Supplementary information fields
1 id number of the processor whose load was disturbingly high
2 number of processes whose priority was increased by the
operating system during the last inspection of the queue
for processes fit for running
3 the identifier of the family that preceded the process with
highest priority among the processes whose priority was
increased in the queue for processes fit for running. Fields
2 and 3 contain the identifier of the family in full
4 process identifier, see description in field 2
5 priority of the process identified in fields 2 and 3
6 identifier of a family that was fit for running during the whole
of the inspection period, although it received processor time
during the period. If the disturbance occurred because of
a looped process, this process is the probable cause of the
disturbance.
Fields 5 and 6 contain the family identifier in full.
If there is no such process in the queue for processes fit
for running, the identifier is FFFF FFFF
7 process identifier, see description in field 5
8 priority of the process identified in fields 5 and 6. If there
is no such process (that is the process identifier is FFFF FFFF)
the value is 0
Instructions
The disturbance may result from a computer overload. Check if there
is an overload in the network element or a local overload in some
computer unit of the network element.
DN9813048
Issue 18-2
65
Disturbance Printouts (1000-1999) 1071 PROCESSOR TIME SHORTAGE
Id:0900d805806a941a
If the fault lies elsewhere, the maintenance of the exchange starts
actions to correct the fault situation. In this case it is also
recommended to inform the supplier of the software package on
the fault so that they can investigate the reason for the fault.
Cancelling
No cancelling.
66 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1072 SIGNALLING LINK OUT OF SERVICE
41 1072 SIGNALLING LINK OUT OF SERVICE
Meaning
A signalling link has failed and changed state from IN SERVICE to
OUT OF SERVICE, or its initial alignment attempt has failed. If this
signalling link is the only one in the signalling link set, the system
sets also alarm 2070, LINK SET UNAVAILABLE. If there is an alternative
signalling link available in the link set, the system performs a
changeover. In this case the signal transmission capacity is also
decreased.
Supplementary information fields
1 signalling link number
2 signalling link error code
01 stop command received
02 erroneous BSN received repeatedly
03 erroneous FIB received repeatedly
04 error ratio too high
05 acknowledgement delay too long
06 initial alignment unsuccessful
07 congestion too long
08 SIO received when one is not expected
09 SIN received when one is not expected
0A SIE received when one is not expected
0B SIOS received when one is not expected
0C SIPO received when one is not expected
0D SIB received when one is not expected
3 number of the signalling link terminal
4 number of the logical signalling link terminal
5 number of the internal PCM circuit
6 number of the external PCM circuit
7 previous working state of signalling link terminal:
00 IDLE
01 OUT OF SERVICE
02 MONITORING
03 WAIT FOR FISU
04 NOT ALIGNED
05 ALIGNED
06 PROVING
07 LOOP CHECK
08 ALIGNED/NOT READY
DN9813048
Issue 18-2
67
Disturbance Printouts (1000-1999) 1072 SIGNALLING LINK OUT OF SERVICE
Id:0900d805806a941a
09 ALIGNED/READY
0A IN SERVICE
0B EMPTYING
0C UPPER LEVEL OUTAGE
0D LOCAL PROCESSOR OUTAGE
0E REMOTE PROCESSOR OUTAGE
0F BOTH PROCESSORS OUTAGE
10 INTERNAL LOOP TEST
11 EXTERNAL LOOP TEST
Instructions
If the value of 7th supplementary information is 0A (IN SERVICE).
it means that the signalling link given in the 1st supplementary
information has failed and its state has changed from IN SERVICE
to OUT OF SERVICE. The system automatically tries to reactivate
the signalling link.
1. If the value of the 2nd supplementary information is 04,
check data transmission. This error code is typically given
when there is a PCM cutoff. If the exchange terminal does not
indicate PCM cutoff, the bit error ratio is too high for
some other reason, or there are problems in synchronization.
If the signalling link stays unavailable for a long time
and does not realign automatically, monitor the link with
a protocol analyzer in order to solve the problem.
2. If the value of the 2nd supplementary information is 0B,
the remote signalling link terminal has for some reason
detected the link faulty. If this happens repeatedly, ask
the remote end operator what is the reason for this.
If the alarm is caused by a PCM circuit with a high bit error
ratio, the link typically gives error codes 04 and 0B
alternatingly, depending on which end first detects the error
ratio.
3. If the value of the 2nd supplementary information is 02, 03, 05,
08, 09, 0A, 0C or 0D, there is a problem in the operation of
the remote end signalling link terminal. In these cases, no
actions are required from the user. These fault situations are
not common; if these error codes are often given in this alarm,
monitor the link with a protocol analyzer to analyze the
fault situation.
Check that the level 2 error correction method is the same in
both ends of the signalling link: either the basic method or
the preventive cyclic retransmission (PCR). You can check the
error correction method with the MML command NOI:
ZNOI:<parameter set number>;
You can find out the parameter set number with the MML command NCI:
ZNCI:<link number>;
68 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1072 SIGNALLING LINK OUT OF SERVICE
4. The value 0E of the 2nd supplementary information is used only
in ANSI network, and it means that the signalling link has been
restarted as it has been congested for the period of T111 T31.
If this happens repeatedly, there is serious overload in the
signalling network, and increase the capacity or rerouting should be
seriously considered.
5. If the value of the 2nd supplementary information is 01, the
CCNETM has stopped the link. This can happen if, for example,
the test procedure of the signalling link fails. The most
common reason for this is that the signalling link code (SLC)
is not same in both ends.
If the value of the 2nd supplementary information is 06, the link
is out of service and realignment fails. In this case the value of
the 7th supplementary information indicates the phase of the
initial alignment procedure in which errors were detected. Usually
the alignment fails because the bit error ratio is too high.
Analyze the fault with a protocol analyzer.
6. Check that the signalling link bit rate is the same in both ends:
either 64kbit/s or 56kbit/s.
You can check the signalling link bit rate with the MML command NOI:
ZNOI:<parameter set number>;
You can find out the parameter set number with the MML command NCI:
ZNCI:<link number>;
Cancelling
No cancelling.
DN9813048
Issue 18-2
69
Disturbance Printouts (1000-1999) 1076 FORCED LIGHTWEIGHT SCHEDULING
Id:0900d805806a941a
42 1076 FORCED LIGHTWEIGHT SCHEDULING
Meaning
A lightweight hand within a process family has been running for
a period of time that exceeds the limit defined in the parameter
file. The other hands in the family have been waiting for their
turn to run. The running of the hand identified in the supplementary
information of the alarm is stopped and the next hand is allowed to
run, so as not to disturb the functioning of the other hands in the
family.
The situation usually results from a fault in the functioning of
a hand.
Supplementary information fields
1 identifier of the family where forced scheduling was executed
2 process identifier of the hand whose running was stopped
3 focus of the process identifier of the hand whose running
was stopped
4 length of the period, in seconds, that the hand was running
Instructions
There is a temporary disturbance in the functioning of the family.
Since the reason is usually a fault in the application, it is
recommended that you inform your local Nokia Siemens Networks
representative about the fault, in order to investigate the reason
for the fault.
The alarm requires no other actions.
Cancelling
No cancelling.
70 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1077 FREE STACK SIZE BELOW LIMIT
43 1077 FREE STACK SIZE BELOW LIMIT
Meaning
The free stack size of the process mentioned in the
supplementary information of this alarm is below the threshold
of 128 bytes. If it continues, the situation may disturb the
functioning of the computer.
Supplementary information fields
1 family identifier of the process whose free stack size is
below the limit. Fields 1, 2 and 3 consist of the complete
identifier of the process in question
2 identifier of the process which set the disturbance, see
description in field 1
3 focus of the process, see field 1
4 free stack size
5 decrease in free stack size was detected because:
1 ESP value was below the threshold
2 values other than zero were detected in the lowest
128 bytes of the stack
Instructions
The alarm indicates a temporary disturbance in the functioning
of the process. The disturbance may have been caused by an error
in the software or the packaging, so it is recommended that you
inform your local Nokia Siemens Networks representative in order
to detect the possible fault.
Cancelling
No cancelling.
DN9813048
Issue 18-2
71
Disturbance Printouts (1000-1999) 1078 PROCESS EXCEPTION
Id:0900d805806a941a
44 1078 PROCESS EXCEPTION
Meaning
A process, specified in the supplementary information of this
alarm, has caused an exception and, as a result, the process has
been frozen. The exception may result from a software or
hardware fault.
The recovery from the freezing of a process may require
maintenance actions, for instance a process restart or a
computer switchover.
Supplementary information fields
1 family identifier of the process that caused an exception
2 process identifier of the process that caused an exception
3 type of exception. Possible values are:
00 division by zero
04 overflow
05 segmentation fault
06 invalid operation code
07 parallel processor missing
08 double fault
09 faulty segment reference in parallel processor
0A invalid Task State Segment
0B segment not present
0C stack exception
0D general protection error
0E page fault
10 error in parallel processor
FF exception not found in the log
4 selector of the exception address.
If the value of field 3 is FF, this field has no significance
5 offset of the exception address.
If the value of field 3 is FF, this field has no significance
Instructions
If the computer has not set alarms on hardware fault,
the reason for the exception is probably a fault in software.
To correct the fault, contact your local Nokia Siemens Networks
representative.
72 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1078 PROCESS EXCEPTION
The alarm requires no further actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
73
Disturbance Printouts (1000-1999) 1080 PROCESS STOPPED
Id:0900d805806a941a
45 1080 PROCESS STOPPED
Meaning
A process, defined in the supplementary information fields of this
alarm, is in a situation where it is impossible to continue
execution. The process is stopped on purpose. The fault situation
is usually a result of erroneous packaging or functioning.
Stopping the process may require maintenance, for example, a
process restart.
Supplementary information fields
1 family identifier of the process that was stopped
2 process identifier of the process that was stopped
3 the fault was noticed by:
01 LIBGEN library
02 code produced by the TNSDL translator
03 Launcher (i.e. the Program starter and supervisor in Linux
computer units)
4 cause of the failure. Values set by system program library:
01 master calling for stopping
02 FAMILY_SERVICES_IN_USE attribute missing
03 error in buffered message reception
04 incorrect family generation
05 no more LDT slots
06 saving the message failed
07 numbers of hand types not valid
08 hand initialization failed
09 incorrect user for the routine lib_TNSDL_stop_r
0A incorrect user for the routine lib_TNSDL_create_r
0B incorrect user for the routine lib_receive_msg_r
0C parameter error, MIN_FREE_TIME
0D parameter error, START_PTR
0E parameter error, TRANSITION_PTR
0F internal error in reserving data area for lightweight hand
10 internal error in saving the stack
Values set by Launcher:
20 no response to supervision messages
Values set by the TNSDL translator:
80 master called for STOP statement
74 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1080 PROCESS STOPPED
81 overflow in user's encode routine
82 overflow in system's encode routine
83 error in user's decode routine, FPAR of hand
84 error in user's decode routine, internal INPUT
85 internal message queue full
86 internal message queue empty
87 error in user's decode routine
88 message too short
89 table indexed beyond the index area
5 additional information on the fault. The field is only in use
if field 4 has one of the below-mentioned values.
The meaning of the field is also explained below.
01 lower word of the return address offset
81 number of message being handled at the time of the error
82 number of message being handled at the time of the error
87 number of message being handled at the time of the error
88 number of message being handled at the time of the error
89 identifier of the source code file where the erroneous
reference is made (internal identifier of the translator)
6 additional information on the fault. The field is only in use
if field 4 has one of the below-mentioned values.
The meaning of the field is also explained below.
01 upper word of the return address offset
89 row number of the source code file where the erroneous
reference is made
7 additional information on the fault. The field is only in use
if field 4 has one of the below-mentioned values.
The meaning of the field is also explained below.
01 return address selector
89 index used in erroneous indexing
Instructions
The fault usually lies in the software or the packaging, so it is
recommended that you inform local technical support.
The alarm requires no further actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
75
Disturbance Printouts (1000-1999) 1082 HAND USAGE LIMIT EXCEEDED
Id:0900d805806a941a
46 1082 HAND USAGE LIMIT EXCEEDED
Meaning
The number of free hands of a hand type in a process family
(indicated in the supplementary information fields of this
alarm) has dropped below the supervision threshold during
the measurement period.
If there are no free hands of a certain hand type, that type
of hands cannot be reserved, and this may thus disturb the
functioning of the computer.
Supplementary information fields
1 family identifier
2 hand type identifier
3 minimum percentage of free hands in a given hand type
during the supervision period
4 supervision limit percentage
5 minimum number of free hands in a given hand type during
the supervision period
6 number of free hands in a given hand type at the end of
the supervision period
Instructions
The cause of the disturbance may be a fault or an overload
situation, or an insufficient number of hands in a given hand
type. Also, the supervision parameter values may be too low.
If the number of free hands in a given hand type has in fact
been small, increase the number of hands in the DXPARA file
used in the computer. The number of hands can be increased by
packaging a new file or by modifying the number of hands in
the file used in the exchange by means of the STYMIE service
terminal extension. The modified number of hands will be
valid after the next loading restart of the computer.
Cancelling
No cancelling.
76 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1083 SEMAPHORE USE ERROR
47 1083 SEMAPHORE USE ERROR
Meaning
The system has detected an error in a semaphore handling routine of
the operating system kernel. The error may disturb the functioning
of the erroneous application or the co-operation of applications.
Supplementary information fields
1 family identifier of the process that called the routine where an
error was detected
2 process identifier of the process that called the routine where an
error was detected
3 error code describing the error detected. The possible values are:
257d error in semaphore name
258d attempt to use the semaphore in a way not allowed by
protection
259d illegal attempt to initialize the semaphore
260d ENTER_REGION routine call in a critical area
261d EXIT_REGION routine call outside a critical area
4 selector part of the call return address
5 offset part of the call return address
Instructions
There is a fault in the software or the packaging, so it is
recommended that you inform your local Nokia Siemens Networks
representative in order to find out the reason for the fault
situation.
The alarm requires no further actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
77
Disturbance Printouts (1000-1999) 1089 DYNAMIC LDT SLOTS EXHAUSTED
Id:0900d805806a941a
48 1089 DYNAMIC LDT SLOTS EXHAUSTED
Meaning
All the local descriptor table slots for the process family's
dynamic use are reserved and the reservation of a new slot
has failed. The error disturbs the functioning of the process
family and thus possibly the functioning of the whole computer.
The fault may be in packaging, that is, an insufficient number of
dynamic local descriptor table slots in comparison with the
number of hand processes are reserved for a family. The fault
may also be in software, that is, too many slots are reserved.
The process family indicated in the supplementary information
fields of this alarm is not always the one whose descriptor
table is full, because some operating system routines handle
tables other than the process family's own local descriptor table.
This is especially the case when the family identifier is 108.
Supplementary information fields
1 family identifier of the process that called the routine
where an error was detected
2 process identifier of the process that called the routine
where an error was detected
3 selector part of the call return address
4 offset part of the call return address
Instructions
1. Output the resource information of the process family
indicated in the alarm by using the DOI command. This will
help to determine the fault. Useful information can also be
obtained from the operating system log or the computer log.
2. Inform your local Nokia Siemens Networks representative about
the fault.
Cancelling
No cancelling.
78 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1090 BUFFER HANDLE ERROR
49 1090 BUFFER HANDLE ERROR
Meaning
A process has called a buffer handling routine with an incorrect
buffer handle. A typical situation is a failure in the release of
the buffer, so that the buffer remains occupied by the process.
Supplementary information fields
1 family identifier of the process that called the routine where an
error was detected
2 process identifier of the process that called the routine where an
error was detected
3 selector part of the call return address
4 offset part of the call return address
Instructions
The fault is in the software, therefore, it is recommended that you
inform your local Nokia Siemens Networks representative.
Cancelling
No cancelling.
DN9813048
Issue 18-2
79
Disturbance Printouts (1000-1999) 1092 COMMUNICATION FAILURE IN FIELD RE-
PORTING
Id:0900d805806a941a
50 1092 COMMUNICATION FAILURE IN FIELD
REPORTING
Meaning
Reading of traffic data from the statistical unit, or back-up
copying of field reporting files, has temporarily failed due to
a fault, or overloading of statistics or the I/O system.
The next regular or intermediate report may therefore contain
information that is inexact.
Supplementary information fields
1 file number:
5C0000 = FACILI = subscriber facilities
4B0000 = SERLEV = service grade counters
5940000 = NORELC = service grade clear code counters
5930000 = DERELC = service grade counters by clear code group
6500000 = ACGAPP = service number counters
2 error code:
1d reading of traffic data failed
2d back-up copying failed
You can check the meaning of other error codes in General
Error Messages of System
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
80 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1093 OUTPUT FAILURE IN FIELD REPORTING
51 1093 OUTPUT FAILURE IN FIELD REPORT-
ING
Meaning
The output of the regular field report has failed because the I/O
system is overloaded, the I/O device is not in order, the logical
output file used to print the report is not properly connected
to the I/O device, buffer memory for making the report cannot be
reserved, or a field reporting file cannot be opened.
Supplementary information fields
1 error code given by I/O system.
General error message of the system. You can check its meaning
in the General Error Messages of System
2 observation type:
00 subscriber facilities (FAC)
01 restarts (RES)
02 all grade of service data (SER)
03 intelligent network (IN) services (ACG)
04 number of calls in the exchange (TRF)
05 clear codes of all calls (CLR)
06 clear codes of one outgoing number destination (CLS)
07 clear code groups by number destinations (DES)
08 signalling specific clear codes of specified circuits (SSC)
09 data call clear code groups by number destination (DAT)
0A data call clear codes (DCL)
0B signalling specific clear codes of all circuits (SSCA)
Instructions
Check that the I/O device used to print reports is in order and
in correct working state (MML command ISI), and that the following
logical output files have been connected to the said device:
Logical file Measurement type
=======================================================================
ascii bin xml
FIELFACA FIELFACB FIELFACX Field Reporting of facility usage
FIELRESA FIELRESB FIELRESX Field Reporting of unit restarts
FIELTRFA FIELTRFB FIELTRFX Field Reporting on trafficability
performance
FIELCLRA FIELCLRB FIELCLRX Field Reporting on clear codes
FIELCLSA FIELCLSB FIELCLSX Field Reporting on clear codes of
one destination
FIELDESA FIELDESB FIELDESX Field Reporting on destination-specific
DN9813048
Issue 18-2
81
Disturbance Printouts (1000-1999) 1093 OUTPUT FAILURE IN FIELD REPORTING
Id:0900d805806a941a
clear code groups
FIELACGA FIELACGB FIELACGX IN service gapping report
FIELASSA FIELASSB FIELASSX Signalling-specific clear code
measurement report, part 2
FIELSSCA FIELSSCB FIELSSCX Signalling-specific clear code
measurement report, part 1
FIELDATA FIELDATB FIELDATX Data call clear code group by number
destination measurement
FIELDCLA FIELDCLB FIELDCLX Data call clear code measurement
Cancelling
No cancelling.
82 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1095 TRAFFIC MEASUREMENT OUTPUT FAILURE
52 1095 TRAFFIC MEASUREMENT OUTPUT
FAILURE
Meaning
The traffic measurement report output on the I/O device used for
printing the report has failed.
Supplementary information fields
1 measurement type
CGR CIRCUIT GROUPS
DEST DESTINATIONS
CNTL CONTROL UNITS
SUBS SUBSCRIBERS
TCAT TRAFFIC CATEGORIES
BS CELLS
SMO SUBSCRIBER MODULES
ANN ANNOUNCEMENT CHANNELS
CTD CIRCUIT GROUP TO DESTINATION
DTD DESTINATION TO DESTINATION
VAN VOICE ANNOUNCEMENT
RSS REMOTE SUBSCRIBER STAGE
BCH BEARER CHANNELS
2 error code 154d is output to this field, if no reply to
the report output request is received from the RFGPRB program
block. Otherwise, any of the error codes returned by the said
program block is output. You can check their meaning in General
Error Messages of System
Instructions
Check that the operation and maintenace unit (OMU) is in state WO-EX.
Check also that the output device connected to the logical file of
the measurement in question is in order.
Logical file Measurement type
=========================================================
ascii bin xml
TRACGRA TRACGRB TRACGRX CIRCUIT GROUPS
TRADESTA TRADESTB TRADESTX DESTINATIONS
TRACNTLA TRACNTLB TRACNTLX CONTROL UNITS
TRASUBSA TRASUBSB - SUBSCRIBERS
TRATCATA TRATCATB TRATCATX TRAFFIC CATEGORIES
TRASMOA TRASMOB - SUBSCRIBER MODULES
TRABSA TRABSB TRABSX CELLS
TRAANNA TRAANNB TRAANNX ANNOUNCEMENT CHANNELS
TRACTDA TRACTDB TRACTDX CIRCUIT GROUP TO DESTINATION
DN9813048
Issue 18-2
83
Disturbance Printouts (1000-1999) 1095 TRAFFIC MEASUREMENT OUTPUT FAILURE
Id:0900d805806a941a
TRADTDA TRADTDB TRADTDX DESTINATION TO DESTINATION
TRAVANA TRAVANB TRAVANX VOICE ANNOUNCEMENT
TRARSSA TRARSSB - REMOTE SUBSCRIBER STAGE
TRABCHA TRABCHB - BEARER CHANNELS
Cancelling
No cancelling.
84 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1098 TOO LONG MESSAGE
53 1098 TOO LONG MESSAGE
Meaning
A message to be received is longer than the area reserved for
message reception, therefore, receiving the message to the
process data area was only partially successful.
If the process does not check whether message reception was
successful, the process may erroneously read information in the
data area outside the reception area as the end part of the message,
and interpret that data according to message structure.
Supplementary information fields
1 family identifier of the process that received a message to
an insufficient reception area
2 process identifier of the process that received a message to
an insufficient reception area
3 message length
4 message sender's computer
5 message sender's family identifier
6 message sender's process identifier
7 message number
Instructions
The fault is in software or packaging, therefore, it is recommended
that you inform your local Nokia Siemens Networks representative,
in order to correct the fault situation.
The alarm requires no further actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
85
Disturbance Printouts (1000-1999) 1103 SIGNALLING MEASUREMENT REPORT LOST
Id:0900d805806a941a
54 1103 SIGNALLING MEASUREMENT REPORT
LOST
Meaning
The forming or outputting of signalling measurement report
in the defined device has failed. The reason may be in the
definition of the logical file used in the outputting of the
report, or in the switching, or the reason may be the wrong
operating state or overload of one of the I/O-devices which
the logical file in question is linked with.
Supplementary information fields
1 the lost report:
01 SIGNALLING LINK AVAILABILITY
02 SIGNALLING LINK PERFORMANCE
03 SIGNALLING LINK UTILIZATION
04 SIGNALLING POINT STATUS
05 SIGNALLING LINK SET AND ROUTE SET AVAILABILITY
06 SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINT
07 SIF AND SIO OCTETS HANDLED WITH SIO
08 SIF AND SIO OCTETS HANDLED WITH OPC, DPC AND SIO
09 SCCP SIGNALLING POINT METERS
0A SCCP SUBSYSTEM METERS
0B SCCP LOCAL SUBSYSTEM AVAILABILITY
0C SCCP SINGLE METERS
0D TC PERFORMANCE AND UTILIZATION
0E TRANSMITTED AND RECEIVED FRAMES AND OCTETS ON
D-CHANNEL
0F D-CHANNEL MISCELLANEOUS STATISTICAL METERS
10 Q.921 ERROR METERS
11 TC TRANSACTION METERS
20 SIGNALLING LINK INTERVAL LOG
21 MTP SIGNALLING POINT INTERVAL LOG
22 SCCP SIGNALLING POINT INTERVAL LOG
23 SCCP SEGMENTATION AND REASSEMBLY ERRORS INTERVAL LOG
24 TC INTERVAL LOG
25 SCCP GT TRANSLATION ERRORS LOG
2 the value 154d will be output in the field if RFGPRB
program block gives no answer to the output request of
the report. Otherwise some other general error code will
be output. You can check the meaning of error codes in
General Error Messages of System.
Instructions
Make sure that the operation and maintenance unit (OMU) is in
the WO-EX state. Make sure that the connection of the logical
86 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1103 SIGNALLING MEASUREMENT REPORT LOST
file of the measurement in question is in order, i.e. that
the logical file is further connected to another logical file
(e.g. binary report file to the MEAFIL) or to a working
I/O-device.
If the logical files of binary reports are connected to the
MEAFIL file, make sure that the MEAFIL is connected to the
virtual data storing device (VDS).
Logical file Measurement type
.............................................
ascii bin
MTP measurement reports:
MTPSLAVAIA MTPSLAVAIB SIGNALLING LINK AVAILABILITY
MTPSLPERFA MTPSLPERFB SIGNALLING LINK PERFORMANCE
MTPSLUTILA MTPSLUTILB SIGNALLING LINK UTILIZATION
MTPSPSTATA MTPSPSTATB SIGNALLING POINT STATUS
MTPSLSAVAA MTPSLSAVAB SIGNALLING LINK SET AND ROUTE SET
AVAILABILITY
MTPOCTHSPA MTPOCTHSPB SIF AND SIO OCTETS HANDLED WITH
SIGNALLING POINT
MTPOCTSIOA MTPOCTSIOB SIF AND SIO OCTETS HANDLED WITH
SIO
MTPOCTMATA MTPOCTMATB SIF AND SIO OCTETS HANDLED WITH
OPC, DPC AND SIO
SCCP/TC measurement reports:
SCCPSPA SCCPSPB SCCP SIGNALLING POINT METERS
SCCPSSA SCCPSSB SCCP SUBSYSTEM METERS
SCCPLSSAVA SCCPLSSAVB SCCP LOCAL SUBSYSTEM AVAILABILITY
SCCPSINGLA SCCPSINGLB SCCP SINGLE METERS
TCAPPUA TCAPPUB TCAP PERFORMANCE AND UTILIZATION
TCAPTRANSA TCAPTRANSB TC TRANSACTION METERS
LAPD measurement reports:
LAPDFROCA LAPDFROCB TRANSMITTED AND RECEIVED FRAMES
AND OCTETS ON D-CHANNEL
LAPDMISCCA LAPDMISCCB D-CHANNEL MISCELLANEOUS STATISTICAL
METERS
LAPDQ921EA LAPDQ921EB Q.921 ERROR METERS
MTP interval log reports:
MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORT
MTPSPLOGA SIGNALLING POINT INTERVAL LOG
REPORT
SCCP/TC interval log reports:
SCCPSPLOGA SCCP SIGNALLING POINT INTERVAL LOG
REPORT
SCCPSGLOGA SCCP SEGMENTATION AND REASSEMBLY
ERRORS INTERVAL
DN9813048
Issue 18-2
87
Disturbance Printouts (1000-1999) 1103 SIGNALLING MEASUREMENT REPORT LOST
Id:0900d805806a941a
LOG REPORT
TCLOGA TC INTERVAL LOG REPORT
SCCPGTLOGA SCCP GT TRANSLATION ERRORS LOG
REPORT
Cancelling
No cancelling.
88 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1105 LINE SIGNALLING RECEIVE OVERLOAD
55 1105 LINE SIGNALLING RECEIVE
OVERLOAD
Meaning
The receiving of line signals is overloaded.
Supplementary information fields
1 plug-in unit type
2 plug-in unit index
3 error code
0 the buffer of the signal receiver in the LST plug-in unit
is full
1 the LSPPGM message buffer for received signals is full
2 the LSPPGM message buffer for supervision messages
is full
3 the message buffer between the modules
(RTC85-LSPREC) of the LSPPGM is full
4 all the filtering time counters of LSPPGM are in use
5 the message buffer for received signals in the
AS7_U plug-in unit is full
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
89
Disturbance Printouts (1000-1999) 1125 TRIAL CONFIGURATION DELETED
Id:0900d805806a941a
56 1125 TRIAL CONFIGURATION DELETED
Meaning
The recovery system has deleted the trial configuration, because
a) in connection with the latest OMU restart, automatic return
changed the software build to another because of a fault situation
or
b) a system restart occurred in a situation where the OMU (non-redundant)
was not in the trial
Supplementary information fields
1 error code which indicates the reason for deleting the trial
configuration. You can check its meaning in General Error
Messages of System.
Instructions
Check the OMU BLACKBOX for the reason why
a) the software build was changed during the latest restart
or
b) the OMU and the whole system was restarted.
Cancelling
No cancelling.
90 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1128 EXCESSIVE DISTURBANCES IN FILE LOAD-
ING
57 1128 EXCESSIVE DISTURBANCES IN FILE
LOADING
Meaning
File loading has been interrupted due to recurring errors.
The unit is restarted to recover from the errors.
Supplementary information fields
1 general error message of the system. You can check its meaning with
a command of the service terminal extension MRS or in General Error
Messages of System
2 identifier of the family that detected the error
USAPRO (A0): error detected by unit state administration
FEMSER (2A3): error detected by file server for memory files
lnx-dxfile-loader (705): error detected by Linux file loader
The error may also be detected by a database manager
3 message bus address of the computer where the failed
loading was executed
4 load group source
01 memory
02 disk
5 load type
01 virtual loading
02 immediate loading
6 load group
7 identifier of the file whose loading failed
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
91
Disturbance Printouts (1000-1999) 1136 SIGNALLING MESSAGE DISTRIBUTION ER-
ROR
Id:0900d805806a941a
58 1136 SIGNALLING MESSAGE DISTRIBUTION
ERROR
Meaning
The alarm is issued when CCRECE receives from a signalling link
a message which it cannot distribute to the user part concerned.
Supplementary information fields
1 error code:
01 PCMCON file access error
02 COSPPC file access error
03 CIINTA file access error
2 value of service information octet (SIO) of received
signalling message
3 value of destination point code of received
signalling message
4 value of originating point code of received
signalling message
5 value of signalling link selection field of received
signalling message
6 the value of the circuit identification code field of such
a received signalling message that contains the field, e.g.
the signalling messages of the TUP and ISUP user parts
7-9 next three bytes after the user label in the signalling
message received from the signalling link
Instructions
Check whether the error is caused by the files or by a faulty
message.
Cancelling
No cancelling.
92 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1137 INCORRECT SIGNALLING MESSAGE FROM
SIGNALLING TERMINAL
59 1137 INCORRECT SIGNALLING MESSAGE
FROM SIGNALLING TERMINAL
Meaning
An erroneous signalling message has been received from a plug-in unit.
There is a failure or a disturbance in the plug-in unit, or the
content of the signalling message sent by the partner exchange is
faulty. The incoming signalling message is deleted, and if the
disturbance is caused by a faulty signalling terminal, the call
setup or call termination of a single call can be affected.
Supplementary information fields
1 error detected in signalling message
01 signalling message is too long
02 service information octet is faulty
2 type of plug-in unit
3 index of plug-in unit
4 logical number of signalling terminal
5 value of service information octet (SIO) of received
signalling message
6 value of destination point code of received
signalling message
7 value of originating point code of received
signalling message
8 value of signalling link selection field of received
signalling message
Instructions
Check with the MML command AHO if the alarm 2075
(COMMUNICATION FAILURE BETWEEN SIGNALLING TERMINAL AND CCNETM)
has been issued. If it is and the alarm 1137 has been given
only once or very occasionally, act according to the instructions
of the alarm 2075.
The plug-in unit identified in supplementary information 2 and 3
may be faulty. Perform a switchover of the alarm's target unit
with the MML command USC. Change into testing state the unit
where the plug-in unit that is suspected faulty is located.
Run diagnostics for the unit to find out whether the plug-in unit
is faulty, see instructions on Diagnostics and Testing.
DN9813048
Issue 18-2
93
Disturbance Printouts (1000-1999) 1137 INCORRECT SIGNALLING MESSAGE FROM
SIGNALLING TERMINAL
Id:0900d805806a941a
Replace the plug-in unit, if diagnostics detects that it is
faulty. See Instructions for Replacing Plug-in Units.
Check also with the MML command AHP whether the alarm 2224
(ERROR IN MSU HANDLING) has been issued. If it is, act according
to its instructions.
If the cause of the disturbance was not discovered with these
actions, check out the log of the unit that issued the alarm with
the service terminal command ZGD. If the log text "INCORRECT MSG
FROM TERM TYPE x" is found, store the contents of the terminal
control mailbox identified in the message's data for later
examination. Store also the alarm history before and after
the alarm 1137 was given and, if necessary, contact your local
Nokia Siemens Networks representative.
Cancelling
No cancelling.
94 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1140 FREE LDT SLOT COUNT BELOW LIMIT
60 1140 FREE LDT SLOT COUNT BELOW LIMIT
Meaning
The free dynamic LDT slot count of a process indicated in the
supplementary information fields of this alarm is below the
supervision limit indicated by the process.
The fault may be in packaging, that is, an insufficient number of
dynamic local descriptor table slots in comparison with the
number of hand processes are reserved for a family. The fault
may also be in software, that is, too many slots are reserved or
the supervision limit is set to be unnecessarily high. In such
case the slot count may fall below the limit even in normal operation.
In case the dynamic LTD slot count falls below the supervision limit,
it is highly probable that the number of slots has been significantly
reduced, and the reason for this should be clarified
immediately.
When the family has no more dynamic LDT slots the family is restarted,
which may interfere with the functioning of the computer. Disturbance
observation 1089 is set when there are no more dynamic LDT slots.
Supplementary information fields
1 family identifier of the process whose free dynamic LDT slot count
is below the limit
2 number of family's free dynamic LDT slots
3 supervision limit
4 supervision interval in seconds
Instructions
1. Display the resource status of the process family indicated
in the additional information field of the alarm by using the
MML command DOI.
2. Create a long-term family resource status measurement using
the MML command DOF and start the measurement by giving the MML
command DOG. The measurements are displayed to the logical file
OSSTATREP. Connect the logical file OSSTATREP to I/O terminal
using the MML command IIS.
3. Contact your local Nokia Siemens Networks representative.
Displaying the resource status and providing these results
speeds up the correction of the fault.
DN9813048
Issue 18-2
95
Disturbance Printouts (1000-1999) 1140 FREE LDT SLOT COUNT BELOW LIMIT
Id:0900d805806a941a
Cancelling
No cancelling.
96 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1141 DELAY BUFFER OVERFLOW IN SIGNALLING
TERMINAL
61 1141 DELAY BUFFER OVERFLOW IN SIG-
NALLING TERMINAL
Meaning
The delay buffer of a plug-in unit is full. Messages are deleted
when the delay buffer is in use, so that the signalling traffic is
disturbed. The overflow situation may be caused by overload or a
failure in the plug-in unit. The alarm is issued when there
is a changeover or controlled rerouting.
Supplementary information fields
1 plug-in unit type
2 plug-in unit index
3 logical number of signalling terminal
Instructions
Check the amount of traffic on the channel concerned with the
MML commands of statistics handling. You can obtain the amount
of traffic on the channel, either for the last half hour or
cumulatively, with the MML command OLU. If traffic is low,
the plug-in unit might be faulty.
Perform a changeover for the target unit of the alarm with the
MML command USC. Change into testing state the unit where the
plug-in unit that is suspected faulty is located. Run diagnostics
for the unit to find out whether the plug-in unit is faulty, see
instructions on Diagnostics and Testing.
Replace the plug-in unit, if diagnostics detects that it is faulty.
See Instructions for Replacing Plug-in Units.
Check also with the MML command AHP whether the alarm 2224,
ERROR IN MSU HANDLING, has been issued. If it is, act according to its
instructions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
97
Disturbance Printouts (1000-1999) 1142 FAMILY MEMORY USAGE SUPERVISION LIM-
IT EXCEEDED
Id:0900d805806a941a
62 1142 FAMILY MEMORY USAGE SUPERVI-
SION LIMIT EXCEEDED
Meaning
The family indicated in the supplementary information fields of this
alarm has exceeded the supervision limit set to its memory use.
During start up, the system allocates memory areas to the family
based on maximum memory use rate in normal functions.
The system also supervises that this limit is not exceeded.
the limit is exceeded, this alarm is set off.
Memory use of process families is supervised because a faulty family
may reserve a lot of memory and thus prevent other
processes from reserving memory. The failure to reserve memory
disturbs the functioning of the processes and the computer.
Depending on the functions of the computer, traffic capacity or
charging may be disturbed.
Supplementary information fields
1 family identifier
2 family's memory use percentage observed by supervision
3 supervision limit percentage
4 memory, in kilo bytes, allocated to the family at the
time of the supervision. If it exceeds 64 MB, the value is FFFF
5 free memory, in kilo bytes, at the time of the supervision.
If it exceeds 64 MB, the value is FFFF
6 memory, in kilo bytes, allocated to the family at the
end of the supervision period. If it exceeds 64 MB, the value
is FFFF
7 free memory, in kilo bytes, at the end of the supervision period.
If it exceeds 64 MB, the value is FFFF
Instructions
1. Check whether the disturbance is caused by an overload situation.
In an overload situation an increased number of reserved hands
and unhandled messages for a certain process family can result
in unexpected memory exhaust.
2. Display the resource status of the process family indicated
in the additional information field of the alarm by using the
MML command DOI. This speeds up the diagnosis and correction
of the fault.
98 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1142 FAMILY MEMORY USAGE SUPERVISION LIM-
IT EXCEEDED
3. If there is no overload, contact your local Nokia Siemens
Networks representative to detect a possible fault in software.
Displaying information on memory use and providing these results
speeds up the correction of the fault.
Cancelling
No cancelling.
DN9813048
Issue 18-2
99
Disturbance Printouts (1000-1999) 1143 AMOUNT OF FREE MEMORY REDUCED
Id:0900d805806a941a
63 1143 AMOUNT OF FREE MEMORY REDUCED
Meaning
The amount of free memory in the computer is below the alarm limit
used in supervision.
If the computer runs out of free memory, memory allocation fails
and may disturb the functioning of the computer.
The size of the largest unified memory area is used as the free
memory amount, as its size is more in accordance with the available
free memory amount than the total free memory amount.
Supplementary information fields
1 size of the biggest free buffer
2 alarm limit used in supervision
3 total free memory amount
4 total memory amount in memory administration
Instructions
The reduction in free memory may result from an error in software
or from a computer whose memory is too small for the software package.
Use the MML command DOI to investigate the computer's memory use for
different purposes.
To find out the nature and cause of the situation, send the information
on memory use to your local Nokia Siemens Networks representative.
The alarm limit used in supervision can be modified with the MML command
DOM, parameter MEML.
Cancelling
No cancelling.
100 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1144 FREE BUFFER HEADERS EXHAUSTING
64 1144 FREE BUFFER HEADERS EXHAUSTING
Meaning
The number of free buffer headers is below the alarm limit used
in supervision. This indicates an increased risk of running out
of free buffer headers. When there are no more free buffer headers
the computer must be restarted.
The fault may be in packaging or software, resulting in an insufficient
overall number of buffer headers or one of the process families
reserving too many headers. It is also possible
that the supervision limit has been set to be unnecessarily high,
in which case an alarm is set too early.
Supplementary information fields
1 number of free buffer headers
2 alarm limit used in supervision
3 total number of buffer headers
Instructions
1. Check the current value of the parameter BUFFER HEADER
SUPERVISION LIMIT by using the MMl command DOT. If the value
is unnecessarily high, decrease it by giving the MML command
DOM according to the instructions of the Nokia Siemens Networks
representative.
2. If the value of this parameter is 100 or below, contact
your local Nokia Siemens Networks representative to detect a
possible fault in packaging or software.
Cancelling
No cancelling.
DN9813048
Issue 18-2
101
Disturbance Printouts (1000-1999) 1147 MESSAGE QUEUE OVERFLOW
Id:0900d805806a941a
65 1147 MESSAGE QUEUE OVERFLOW
Meaning
The message queue of the process has reached its defined maximum
length and the message sent to the process is deleted.
Supplementary information fields
1 family identifier of the process whose message queue is full
2 process identifier of the process whose message queue is full
3 sender computer of the deleted message
4 sender family identifier of the deleted message
5 sender process identifier of the deleted message
6 deleted message number
Instructions
The fault lies in software or packaging, therefore, it is recommended
that you inform your local Nokia Siemens Networks representative,
in order to detect the reason for the fault.
The alarm requires no further actions.
Cancelling
No cancelling.
102 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1148 EXCESSIVE TRAPS
66 1148 EXCESSIVE TRAPS
Meaning
The number of traps exceeds the alarm limit during
the supervision interval.
Traps are produced when the program uses an insufficient or faulty memory
or, for example, a faulty addtional plug-in unit.
Traps do not usually disturb the functioning of the program producing
them, but they indicate a disturbance either in the hardware, software or
in the data that the program uses. If the fault is related to hardware,
the system normally gives other alarms as well.
The address formed by CS and EIP is an address where the program
execution was when the trap was detected, that is, the address
describes the program's general execution area rather than a
specific memory addressing execution area.
Supplementary information fields
1 number of traps during supervision interval
2 alarm limit used in supervision
3 identifier of the family that caused the latest trap
4 identifier of the process that caused the latest trap
5 register's CS value at the moment of the latest trap detection
6 register's EIP value at the moment of the latest trap detection
Instructions
1. If the system has not given alarms on hardware faults, check the
equipment data with the MML commands of WT command group.
If the equipment data is correct or if you do not succeed in
correcting the fault, contact your local Nokia Siemens Networks
representative.
2. Operating system logs have been written in the OSSUPREP logical file
and studying those can help you in locating the fault.
Check with the MML command ZDOP whether parameter SENDING OF REPORTS
is allowed. If the parameter is not allowed, allow it with the MML
command ZDOM. Connect the OSSUPREP logical file to the I/O terminal
available with the MML command ZIIS.
3. If the fault is a hardware fault, you can temporarily prevent
the alarm from rising repeatidly by modifying the alarm limit
of the object unit with the MML command ZDOM, or,
DN9813048
Issue 18-2
103
Disturbance Printouts (1000-1999) 1148 EXCESSIVE TRAPS
Id:0900d805806a941a
you can disable the supervision in all the units that are of
the same unit type as the object unit with the MML command ZDOM.
After the fault has been repaired, change the alarm limit back
to normal and re-enable the supervision.
Cancelling
No cancelling.
104 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1162 FILE SYSTEM COMMUNICATION ERROR
67 1162 FILE SYSTEM COMMUNICATION
ERROR
Meaning
The file system program block is not responding to a message within
the allowed time limit or its answer is erroneous. If the program
block has not answered the message within the allowed time limit,
there may be discrepancies between files in the units.
Supplementary information fields
1 location unit type of the partner program block
2 location unit index of the partner program block
3 family identifier of the partner program block
4 number of the message sent to the partner program block
5 number of the file in connection to which the error was detected.
If the value is FFFFFFFF, the file number cannot be identified
6 error code returned by the partner program block.
You can check its meaning in the General Error Messages of System.
Instructions
Use the MML command AHO to check whether there are other active alarms
concerning the file system. Check also possible logs connected to
the file system in the unit identified by the first and second
supplementary fields with the S command of the service terminal
extension LOGUTI. Locate and correct the fault with the help of the
logs and the error code given in the final supplementary field of this
alarm.
Cancelling
No cancelling.
DN9813048
Issue 18-2
105
Disturbance Printouts (1000-1999) 1165 BUFFER ALLOCATION FAILED
Id:0900d805806a941a
68 1165 BUFFER ALLOCATION FAILED
Meaning
A process failed to reserve a buffer because the buffer size
requested by the process is larger than the largest free
buffer.
Buffer reservation failure may prevent the execution of a
task or make it slower.
Supplementary information fields
1 family identifier of the process whose buffer reservation
failed
2 process identifier of the process whose buffer
reservation failed
3 requested buffer size
4 largest free buffer
5 total amount of free memory
Instructions
The fault may be in software or in a computer unit whose
memory is too small for the software and functions required
of it. A software fault is probable, if the requested buffer
size indicated in the supplementary information field is
large in comparison with the computer memory.
If the total amount of free memory indicated in the
supplementary information field seems adequate but also the
largest free buffer (indicated in the supplementary
information field) is small, the memory is fragmented. Even a
hot restart of a computer would cause the rearranging of free
and reserved buffers, so that the largest free buffer would
probably become larger.
If a buffer reservation fails in connection with a critical
task, the maintenance system restarts the computer, and
usually the memory state also returns to normal.
If the total amount of free memory is small, the computer
probably has an insufficient memory capacity and should be
replaced with one that has more capacity.
In any case, it is recommended to inform your local Nokia
Siemens Networks representative on the fault. Include information on
106 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1165 BUFFER ALLOCATION FAILED
the memory, i.e. on the division of free memory and the
process families that have reserved memory the most.
Cancelling
No cancelling.
DN9813048
Issue 18-2
107
Disturbance Printouts (1000-1999) 1169 FREEZING PERIOD OF SS7 REPORTING
LOST
Id:0900d805806a941a
69 1169 FREEZING PERIOD OF SS7 REPORT-
ING LOST
Meaning
Some of the counters or logs of the SS7 statistics are not reported,
because the counters or log events in question are lost from the
files.
If the alarm concerns counter reporting, the following two 30-minute
freezing periods have passed during the report outputting, and thus
the counters of the first reporting period are lost. The counters of
the freezing period in question will not be included to the following
reporting period.
If the alarm concerns reporting of interval logs,
the 5-minute freezing period has finished before the log events of the
previous 5-minute period are reported. In this case, the log events in
question are not reported, but they are available with MML commands.
Supplementary information fields
1 type of counters or logs lost:
01 MTP counters
02 SCCP/TC counters
03 MTP interval logs
04 SCCP/TC interval logs
2 file number of the counter or log file whose counters or logs
were not reported. If the file number is not available, the
value of the field is FFFFFFFF
Instructions
Check that the operation and maintenance computer (OMU) is in working
state WO-EX with the MML command USI.
Check that the connections of the logical files of the SS7 reporting
are in order with the MML command IID, that is, that the logical files
are connected onwards to another logical file (for example binary
reports' files to MEAFIL file) or to a functioning I/O device
(for more information, see instructions on I/O System).
If the binary reports' logical files are connected to MEAFIL file,
also check that MEAFIL is connected to a virtual data storage (VDS).
The reason for the alarm may also be the overload of reporting, in
which case, reports are not outputted fast enough. In this case,
decrease the report load by removing unnecessary signalling channels,
signalling points and/or SCCP subsystems from the statistics with
108 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1169 FREEZING PERIOD OF SS7 REPORTING
LOST
the MML commands OSL, OSN OSE, and possibly unnecesary reporting
types with the MML commands OSM and OSG.
Logical file Measurement type
======================================================
ascii bin
MTP counters:
MTPSLAVAIA MTPSLAVAIB SIGNALLING LINK AVAILABILITY
MTPSLPERFA MTPSLPERFB SIGNALLING LINK PERFORMANCE
MTPSLUTILA MTPSLUTILB SIGNALLING LINK UTILIZATION
MTPSPSTATA MTPSPSTATB SIGNALLING POINT STATUS
MTPSLSAVAA MTPSLSAVAB SIGNALLING LINK SET AND ROUTE SET AVAILABILITY
MTPOCTHSPA MTPOCTHSPB SIF AND SIO OCTETS HANDLED WITH
SIGNALLING POINT
MTPOCTSIOA MTPOCTSIOB SIF AND SIO OCTETS HANDLED WITH SIO
MTPOCTMATA MTPOCTMATB SIF AND SIO OCTETS HANDLED WITH OPC, DPC
AND SIO
SCCP/TC counters:
SCCPSPA SCCPSPB SCCP SIGNALLING POINT METERS
SCCPSSA SCCPSSB SCCP SUBSYSTEM METERS
SCCPLSSAVA SCCPLSSAVB SCCP LOCAL SUBSYSTEM AVAILABILITY
SCCPSINGLA SCCPSINGLB SCCP SINGLE METERS
TCAPPUA TCAPPUB TCAP PERFORMANCE AND UTILIZATION
TCAPTRANSA TCAPTRANSB TC TRANSACTION METERS
MTP interval logs:
MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORT
MTPSPLOGA SIGNALLING POINT INTERVAL LOG REPORT
SCCP interval logs:
SCCPSPLOGA SCCP SIGNALLING POINT INTERVAL LOG REPORT
SCCPSGLOGA SCCP SEGMENTATION AND REASSEMBLY ERRORS
INTERVAL LOG REPORT
TCLOGA TC INTERVAL LOG REPORT
SCCPGTLOGA SCCP GT TRANSLATION ERRORS LOG REPORT
Cancelling
No cancelling.
DN9813048
Issue 18-2
109
Disturbance Printouts (1000-1999) 1178 PREPROCESSOR UNIT DISTURBANCE
Id:0900d805806a941a
70 1178 PREPROCESSOR UNIT DISTURBANCE
Meaning
Functioning of a program block in a preprocessor is not normal.
Either start-up of the program block has failed or the program
block does not send an answer to the supervision message.
Supplementary information fields
1 type of the preprocessor plug-in unit
2 index of the preprocessor plug-in unit
3 general error message of the system telling the reason for the
alarm. You can check its meaning in the General Error Messages
of System.
4 family identifier of the program block that the alarm concerns
Instructions
The alarm requires no immediate actions. However, if the alarm occurs
repeatedly, fill in a Problem Report and send it to your local Nokia
Siemens Networks representative.
Cancelling
No cancelling.
110 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1182 PREPROCESSOR UNIT RESTARTED
71 1182 PREPROCESSOR UNIT RESTARTED
Meaning
A preprocessor has restarted spontaneously. If the preprocessor is
equipped into a unit which working state is WO-EX, the restart causes
disturbance to the function of the unit.
Supplementary information fields
1 type of the restarted preprocessor plug-in unit
2 index of the restarted preprocessor plug-in unit
Instructions
The alarm requires no actions. It supports the activation of the
automatic recovery for the object unit. You can check the supporting
amount of the alarm with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
111
Disturbance Printouts (1000-1999) 1190 EXCESSIVE ERRORS IN SCP
Id:0900d805806a941a
72 1190 EXCESSIVE ERRORS IN SCP
Meaning
Statistics measure the ratio between failed transactions and all
transactions between the SCP and the SSP. The measurement is performed
on the global titles of the SCP with the MML command TDC.
If the ratio between failed transactions and the total number of
transactions exceeds a given limit at the end of a period, and the
total number of transactions does not exceed a given limit, then this
disturbance for the global title defined is printed.
This function has, in the class 9 of the parameter file, the parameters
observation period (15), error ratio alarm limit (14), and limit for
the total number of transactions (13).
Supplementary information fields
1-8 SCP global title:
there are two digits in each byte. If there is an odd
number of digits, the meaningless digit is FH and the
rest FFH (e.g. the global title 123 is printed
12 3F FF FF FF FF FF FF).
9 the number of all transactions in SCP
during the observation period
10 the value of the error ratio that caused the alarm
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
112 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1200 ACTOR HAS FAILED TO REGISTER TO THE
SUPERVISION
73 1200 ACTOR HAS FAILED TO REGISTER TO
THE SUPERVISION
Meaning
An actor has failed to register to the active supervision.
It is possible that the supervision data table has filled up. This
means that the actor supervisor (SVATOR) cannot take more actors
under the active supervision. The problem has no effect on the
actor supervision already activated.
Apart from the active supervision, all actors are supervised
passively, i.e. exceptions made by the actors are always noticed.
If the actor is not supervised actively, the erroneous behaving
(e.g. infinite loops) or the total stopping of the actor is not
detected and the recovery actions are not activated. However, if
the actor runs without problems the lack of active supervision is
not a serious problem.
Supplementary information fields
1 the DMX family identifier of an actor that has failed
to register to the supervision
Instructions
If the alarm occurs, the supervision data table is full.
Fill in a Failure Report and send it to your local
Nokia Siemens Networks representative.
List the content of the supervision data table with service terminal
command: supervise -a all and attach it to the Failure Report.
Cancelling
No cancelling.
DN9813048
Issue 18-2
113
Disturbance Printouts (1000-1999) 1204 WATCHDOG CAUSES UNIT RESTART
Id:0900d805806a941a
74 1204 WATCHDOG CAUSES UNIT RESTART
Meaning
A critical actor for the functioning of the unit has failed.
This kind of actors are e.g. QXFPRB, which activates the recovery
functions and DAQTOR, which takes care of starting other actors.
Actor Supervisor (SVATOR) stops feeding the watchdog feeder actor
and this will cause a unit restart.
Supplementary information fields
Instructions
The alarm requires no actions because the coming unit restart
solves the problem.
Cancelling
No cancelling.
114 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1207 UNITS WORKING STATE DATA CORRUPTED
IN THE SYSTEM
75 1207 UNITS WORKING STATE DATA COR-
RUPTED IN THE SYSTEM
Meaning
Working state data in the memory of the supervised unit is different
from the working state data of the supervised unit in the memory of
the supervising unit. The system detects this divergence by itself
and begins the actions in order to correct the problem.
This data divergence can be caused by message transfer errors during
the distribution of the working states to functional units. It may
cause malfunctioning of the system, and it slows down or may even
prevent the automatic recovery actions in the system.
Supplementary information fields
1 working state of the supervised unit in the memory of the system
maintenance unit
2 working state of the supervised unit in the unit's own memory
Instructions
If the disturbance occurs frequently, fill in a Problem Report and
send it to your local Nokia Siemens Networks representative.
Otherwise, no action is required.
Cancelling
No cancelling.
DN9813048
Issue 18-2
115
Disturbance Printouts (1000-1999) 1210 PHASE ADVANCE OF TIMING SIGNAL
CHANGED
Id:0900d805806a941a
76 1210 PHASE ADVANCE OF TIMING SIGNAL
CHANGED
Meaning
The phase advance setting of a rack has either been changed
to the default value or updated according to the phase advance
measurement result.
If the default phase advance value was taken into use, the
functional units of the rack which are located far enough
from the main clock may have synchronisation problems with
the basic timing signals.
If the phase advance value of the rack was updated when some
functional units had synchronisation problems, the
synchronisation after the updating should work better. This
is the case especially when the difference of the old and
new phase advance value is big enough. If the difference was
only a few measurement units, the updating may have no
effects on the basic timing distribution of functional units
in the rack.
Supplementary information fields
1 reason for phase update made:
00 the default phase advance was taken into use because
the phase advance setting according to the automatic phase
advance measurement is not possible due to the
measurement result changing all the time. The reason
for a measurement failure is typically the last rack
where the timing bus is terminated. If the CLAB units
of the last rack are without power supply or plug-in
units of the CLAB are removed, the automatic phase
advance measurement fails
01 the phase advance was updated. The difference between the
phase advance value used and the measurement value was
too big and updating was needed. The phase advance is
updated typically after maintenance concerning the
timing signals or when the default phase advance was in
use due to the automatic phase advance measurement
problems
2 old phase advance value
3 new phase advance value
116 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1210 PHASE ADVANCE OF TIMING SIGNAL
CHANGED
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
117
Disturbance Printouts (1000-1999) 1220 HANDLING OF MEASUREMENT DEFINITION
FILE FAILED
Id:0900d805806a941a
77 1220 HANDLING OF MEASUREMENT DEFINI-
TION FILE FAILED
Meaning
Handling of measurement definition file has failed. There may be a
temporary overload in the I/O-system. The changes, which have possibly
been made have not been updated to the file. The measurement continues
using the changed parameters, but in a possible restart situation
the system will continue the measurement using the old parameters.
This means that the schedule of the measurement may not be correct.
The third and fourth supplementary information fields show
the reason for the failure.
Supplementary information fields
1 measurement identifier. You can check its meaning by using the MML
command T2C.
2 measurements object list identifier (from 1 to 999). You can check
its meaning by using the MML command T2C.
3 failed task:
01 Writing of measurement definition file failed
02 Passifying of measurement definition file failed
4 specified reason for the error case shown in the third supplementary
information field. This is a general error message of the system.
You can check its meaning with a command of the service terminal
extension MRS (see Service Terminal Essentials, Maintenance Manual)
or from the document the General Error Messages of System,
Supplementary References
Instructions
If the third supplementary information field has the value 01, the
measurement is continued, but the parameters have not been updated to disk.
The wrong parameters are shown when interrogating the measurement
parameters (T2I MML-command). This may be due to a temporary overload
in the I/O-system. Check the I/O-system's active alarms and follow those
alarm instructions. You can try to write on the disk again when the
I/O-system has recovered by modifying the measurement schedule
(T2M MML-command), or the schedule is also updated to the disk every night at
01.00 am, so these updates could correct the problem.
If not, (the disturbance still occurs), contact your local
Nokia Siemens Networks representative. Send the unit's logs, operating
system logs and active alarms to your Nokia Siemens Networks representative.
The logs can be output by using the service terminal commands ZGD
and ZSL. The active alarms can be output by using the MML command ZAHO.
118 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1220 HANDLING OF MEASUREMENT DEFINITION
FILE FAILED
If the third supplementary information field has value 02, remove the
measurement definition file (T2D MML-command) which could not be
passified by the system. This may be due to a temporary overload
in the I/O-system. The name of the file is AMEASxxx.yyy,
where xxx refers to the MID value (first supplementary information field)
in the alarm, and yyy refers to the OID (second supplementary information
field) value in the alarm.
Cancelling
No cancelling.
DN9813048
Issue 18-2
119
Disturbance Printouts (1000-1999) 1221 STATISTICAL MEASUREMENT REPORT OUT-
PUT FAILED
Id:0900d805806a941a
78 1221 STATISTICAL MEASUREMENT
REPORT OUTPUT FAILED
Meaning
Outputting the statistical measurement report has failed. The report of
the measurement, which has caused the alarm may disappear or, if the
measurement report is output, the data in it may be faulty. The third
and fourth supplementary information fields show the reason for the
failure.
Supplementary information fields
1 measurement identifier of the report. You can check its meaning by
using the MML command T2C.
2 measurements object list identifier (from 1 to 999). You can check
its meaning by using the MML command T2C.
ERROR_CASE:
the reason for outputting of report failed:
01 Buffer allocation failed
02 No data writing service provider
03 Error with data writing service provider
3 specified reason when the third supplementary information field has
value 03. This is a general error message of the system. You can
check its meaning with a command of the service terminal extension
MRS (see Service Terminal Essentials, Maintenance Manual) or from
the document the General Error Messages of System, Supplementary
References.
Instructions
If the third supplementary information field has the value 01, there is an
error situation, which probably cannot be corrected without a software
update. Contact your local Nokia Siemens Networks representative. Send the
unit's logs, operating system logs and active alarms to your Nokia Siemens
Networks representative. The logs can be output by using the service
terminal commands ZGD and ZSL. The active alarms can be output by using
the MML command ZAHO.
If the third supplementary information field has the value 02, the service
may be temporarily unobtainable. If this is continuous, there is an error
situation which probably cannot be corrected without a software update.
Contact your local Nokia Siemens Networks representative. Send the unit's
logs, operating system logs and active alarms to your Nokia Siemens Networks
representative. The logs can be output by using the service terminal command
ZGD and ZSL. The active alarms can be output by using the MML command ZAHO.
120 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1221 STATISTICAL MEASUREMENT REPORT OUT-
PUT FAILED
If the third supplementary information field has the value 03, check that
the I/O device used in the outputting of the report is in working order and
in the correct working state (MML command ISI) and that the logical output
file is connected to the device in question (MML command IID). More
information on the administration of I/O devices can be found in I/O
Configuration Handling, Command Reference Manual.
Cancelling
No cancelling.
DN9813048
Issue 18-2
121
Disturbance Printouts (1000-1999) 1222 DATA WRITING VIA VDS DEVICE FAILED
Id:0900d805806a941a
79 1222 DATA WRITING VIA VDS DEVICE
FAILED
Meaning
Data writing via the VDS device has failed. The report of the measurement
that has caused the alarm may disappear. The second and third supplementary
information fields show the reason for the failure.
Supplementary information fields
1 measurement identifier of the report. You can check its meaning by
using the MML command T2C.
2 the reason for data writing to fail:
01 Error in I/O system.
02 No response from I/O system
03 Memory allocation failed
3 specified reason for the error case shown in the second supplementary
information field. This is a general error message of the system.
You can check its meaning with a command of the service terminal
extension MRS (see Service Terminal Essentials, Maintenance Manual)
or from the document the General Error Messages of System,
Supplementary References.
Instructions
If the second supplemetary information field has the value 01 or 02,
The I/O-system may be overloaded, and thus the report output fails.
The situation may be temporary and the system will correct it.
Check the I/O-system's active alarms and follow those alarm instructions.
If the disturbance occurs constantly, contact your local Nokia Siemens
Networks representative. Send the unit's logs, operating system logs and
active alarms to the Nokia Siemens Networks representative.
The logs can be output by using the service terminal command ZGD and ZSL.
The active alarms can be output by using the MML command ZAAP.
If the second supplemetary information field has the value 03, there is an
error situation which probably cannot be corrected without a software
update. Contact your local Nokia Siemens Networks representative.
Send the unit's logs, operating system logs and active alarms to the
Nokia Siemens Networks representative. The logs can be output by using
the service terminal command ZGD and ZSL. The active alarms can be output
by using the MML command ZAAP.
Cancelling
No cancelling.
122 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1228 UNIT SUPERVISION NOT FUNCTIONING
80 1228 UNIT SUPERVISION NOT FUNCTION-
ING
Meaning
The supervision of the functional unit(s) is not functioning because of
a technical problem, or the supervision is stopped by the user
for a special reason. If the supervision is stopped by the user,
the system starts it automatically after a while (in less than one hour).
The lack of supervision does not prevent normal operation of the system,
but it slows down or may even prevent the automatic recovery actions of
the unsupervised unit.
Supplementary information fields
1 failure reason:
01 User has stopped the unit supervision
02 Unit supervision has been stopped because of a technical problem
2 functional unit whose supervision has been stopped:
0xFFFF Supervision of all units stopped
phys_address_t Physical address of the unit whose supervision has
been stopped or technical problem prevents the
supervision to this unit.
Instructions
If the supervision has not been stopped by user and if the disturbance
occurs frequently, fill in a Problem Report and send it to your local
Nokia Siemens Networks representative. Otherwise, no action is
required.
Cancelling
No cancelling.
DN9813048
Issue 18-2
123
Disturbance Printouts (1000-1999) 1234 UPDATE OF PASSWORD VALIDITY TIME
FAILED
Id:0900d805806a941a
81 1234 UPDATE OF PASSWORD VALIDITY
TIME FAILED
Meaning
The program block of the user management (URMANA) has failed
updating the validity times of the MMI users' passwords.
The validity times of the passwords remain unchanged.
Supplementary information fields
1 reason for failure of the password validity time updating
01 error in writing of the memory file
02 error in writing of the disk file
03 creation of hand failed
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
124 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1240 SCCP DISTURBANCE
82 1240 SCCP DISTURBANCE
Meaning
Report on SCCP disturbances.
Supplementary information fields
1 identifier of disturbance. Possible values are:
01 releasing connection failed, as no acknowledgement has been
received
02 abnormal release of connection, the time supervision of the
passive receiving time (IAR) has expired
03 abnormal release of connection, erroneous IT message
04 abnormal release of connection, time supervision of the hand
has expired
05 establishing connection failed, the time supervision of the
connection establishment (CONN_EST) has expired
06 establishing connection failed, as the local subsystem has
not responded to the connection request
07 subsystem does not respond to local sending
08 local subsystem has no counterpart
09 sending a signalling message to the subsystem fails, as the
subsystem has not enrolled for the service
0A sending message to user has failed
0B sending message to MTP has failed
0C SCCP management could not locate the signalling unit being
distributed
0D sending signalling message to a subsystem fails, as the
standard of the TCAP message is different from the TCAP
version used by the subsystem
0E message is rejected because its priority is lower than the
overload level of the MTP
2 network indicator. Possible values are:
00 international network 0
04 international network 1
08 national network 0
0C national network 1
3 local signalling point code. The signalling point code is
interpreted, depending on the value of the first supplementary
information field, in the following manner:
01-06 own signalling point where the error was detected
07-08 own signalling point to whose subsystem the local sending
was attempted
09-0E own signalling point
DN9813048
Issue 18-2
125
Disturbance Printouts (1000-1999) 1240 SCCP DISTURBANCE
Id:0900d805806a941a
4 local subsystem number. If the local subsystem is not known,
the value in the field is FF. The subsystem number is
interpreted, depending on the value of the first supplementary
information field, in the following manner:
01-06 local subsystem, releasing or establishing connection
to which failed
07-08 local subsystem to which local sending was attempted
(important subsystem)
09-0A local subsystem to which local sending was attempted
0B local subsystem from which the message was received
0C SCCP management subsystem
0D local subsystem to which sending a TCAP message was
attempted
0E local subsystem from which a message was received
5 remote signalling point code. The signalling point code is
interpreted, depending on the value of the first supplementary
information field, in the following manner:
01-06 signalling point of the remote end signalling connection part
07-08 object signalling point of local sending, whose data is being
distributed
09-0A signalling point from which the message came
0B local subsystem to which sending a message was attempted
0C local subsystem to which sending an SCCP management message
was attempted
0D signalling point from which a TCAP message was received
0E signalling point to which sending a TCAP message was
attempted
6 remote subsystem number. If the subsystem number is not known,
the value in the field is FF. The subsystem number is
interpreted, depending on the value of the first supplementary
information field, in the following manner:
01-06 remote end subsystem of the signalling connection
07-08 object subsystem of local sending, whose data is being
distributed
09-0A subsystem which send the message
0B remote end subsystem, sending the message to which was
attempted
0C SCCP management subsystem, sending the SCCP management
message to which was attempted
0D subsystem which has send a TCAP message
0E remote end subsystem to which sending a message was
attempted
7 reference number in the DX log. The log contains more
information on the error. If the reference number is not
126 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1240 SCCP DISTURBANCE
used in the log, the value of the field is 0.
Instructions
If the alarm is given infrequently and the value of the error code
given in the first supplementary information field is 1-6, no
actions are required from the user.
Otherwise fill in a Problem report and send it to your local Nokia
Siemens Networks representative. Enclose the printouts output with the
service terminal commands ZSCFE, ZGSC and ZSL in the Problem report.
Cancelling
No cancelling.
DN9813048
Issue 18-2
127
Disturbance Printouts (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALY-
SIS FILE ERROR
Id:0900d805806a941a
83 1241 SCCP GLOBAL TITLE TRANSLATION
ANALYSIS FILE ERROR
Meaning
Report on the analysis disturbances of the SCCP global title
translation. The global title analysis was not completed because
the analysed number was not found in the analysis data. The alarm
may have some effect on the traffic capacity of the system.
A message that contains the global title in question will not get
to its destination.
Supplementary information fields
1 error code. Possible values are:
01 unknown nature of address indicator. There is no analysis
for this nature of address indicator in the GANFIL
02 unknown numbering plan. There is no analysis for this
numbering plan in the GANFIL
03 unknown translation type. There is no analysis for this
translation type in the GANFIL
04 unknown encoding scheme. There is no analysis for this
encoding scheme in the GANFIL
05 unknown global title indicator. There is no analysis for
this global title indicator in the GANFIL
06 unknown global title standard. There is no analysis for
this global title indicator in the GANFIL
11 GANFIL contains no analysis for the first digit of
the address
12 GANFIL contains no analysis for the second digit of
the address
13 GANFIL contains no analysis for the third digit of
the address
14 GANFIL contains no analysis for the fourth digit of
the address
15 GANFIL contains no analysis for the fifth digit of
the address
16 GANFIL contains no analysis for the sixth digit of
the address
128 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1241 SCCP GLOBAL TITLE TRANSLATION ANALY-
SIS FILE ERROR
17 GANFIL contains no analysis for the seventh digit of
the address
18 GANFIL contains no analysis for the eighth digit of
the address
19 GANFIL contains no analysis for the ninth digit of
the address
1A GANFIL contains no analysis for the tenth digit of
the address
1B GANFIL contains no analysis for the 11th digit of
the address
1C GANFIL contains no analysis for the 12th digit of
the address
1D GANFIL contains no analysis for the 13th digit of
the address
1E GANFIL contains no analysis for the 14th digit of
the address
1F GANFIL contains no analysis for the 15th digit of
the address
20 GANFIL contains no analysis for the 16th digit of
the address
21 GANFIL contains no analysis for the 17th digit of
the address
22 GANFIL contains no analysis for the 18th digit of
the address
23 GANFIL contains no analysis for the 19th digit of
the address
24 GANFIL contains no analysis for the 20th digit of
the address
25 GANFIL contains no analysis for the 21st digit of
the address
26 GANFIL contains no analysis for the 22nd digit of
the address
27 GANFIL contains no analysis for the 23rd digit of
the address
DN9813048
Issue 18-2
129
Disturbance Printouts (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALY-
SIS FILE ERROR
Id:0900d805806a941a
28 GANFIL contains no analysis for the 24th digit of
the address
2 record number of the GANFIL
3 global title standard, possible values are:
01 ITU-T
02 ANSI
4 global title indicator in the global title of an SCCP message.
The global title indicator is interpreted in following manner
when the value in the third supplementary field is 01 (ITU-T):
01 global title contains only the nature of address indicator
02 global title contains only the translation type
03 global title contains the translation type, the numbering
plan and the encoding scheme
04 global title contains the translation type, the numbering
plan, the encoding scheme and the nature of address
indicator
05-15 global title does not contain the translation type,
the numbering plan, the encoding scheme or the nature
of address indicator.
These global title indicator values have not been
defined in the ITU-T recommendations
The global title indicator is interpreted in following manner
when the value in the third supplementary field is 02 (ANSI):
01 global title contains the translation type, the numbering
plan and the encoding scheme
02 global title contains only the translation type
03-15 global title does not contain the translation type,
the numbering plan, the encoding scheme or the nature
of address indicator.
These global title indicator values have not been
defined in the ANSI recommendations
5 translation type from the global title of the SCCP message.
The translation type is interpreted in the following manner
when the value in the third supplementary field is 01 (ITU-T):
00 translation type not in use
FF global title does not include translation type
In the national specification ANSI T1.112-1992 there are
values defined for the translation type with the third
supplementary field value 02 (ANSI) and with the fourth
supplementary field value 02. These values of the translation
130 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1241 SCCP GLOBAL TITLE TRANSLATION ANALY-
SIS FILE ERROR
type can be analysed in the normal way, but they do not cause
special procedures in the system
6 numbering plan and encoding scheme from the global title
of the SCCP message. The encoding scheme is encoded with the
least meaningful bits 1-4 in the following manner:
0000 unknown
0001 BCD, odd number of digits
0010 BCD, even number of digits
0011 reserved for future use
:
1110 reserved for future use
1111 encoding scheme not included in global title
The numbering plan is encoded with the most meaningful bits
5-8 in the following manner:
0000 unknown
0001 ISDN/telephone network numbering plan (E.164,E.163)
0010 reserved for future use
0011 data network numbering plan (X.121)
0100 telex network numbering plan (F.69)
0101 ship telephone network numbering plan (E.210,E.211)
0110 mobile telephone network numbering plan (E.212)
0111 ISDN/mobile telephone network numbering plan (E.214)
1000 reserved for future use
:
1110 reserved for future use
1111 numbering plan not included in global title
7 nature of address indicator from the global title of the SCCP
message. Possible values are:
01 subscriber number
02 reserved for national use
03 national meaningful number
04 international number
05 reserved for future use
:
FE reserved for future use
FF nature of address indicator not included in global title
8-15 address information from the global title of the SCCP message
so that, for example, the number 12345 is encoded
12 34 5F FF ...
Instructions
1. Check whether there should be a global title analysis created for
the global title indicated in the disturbance. You can check the
DN9813048
Issue 18-2
131
Disturbance Printouts (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALY-
SIS FILE ERROR
Id:0900d805806a941a
existing analyses with the NBI command of the Global Title
Analysis Handling MML (GTAHAN). Note that in the MML command
the given root parameters must be the same as in the alarm.
2. If there is no analysis, you can create it with the MML command
NBC, if necessary. Before creating the analysis, find out the
correct analysis result to which the new analysis will be
connected. You can check the analysis result records with the
MML command NAI. If a suitable result record is not found, you
can create it with the MML command NAC.
3. If the analysis has already been created, the error may be
a file error. It may be possible to correct the error by loading
the GANFIL file from disk with the MML command DFM in the unit
that set the alarm.
4. As in the short message service the subscriber gives the title,
a wrong title can cause the alarm in question. If there is a
disturbingly high number of alarms in a situation like this,
this alarm can be blocked with the MML command ABB. Note that
if the alarm is blocked, it will not be set in the genuine
fault situation either.
5. If these actions do not help, fill in a Problem report and
send it to your local Nokia Siemens Networks representative.
Cancelling
No cancelling.
132 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1242 SCCP GLOBAL TITLE TRANSLATION RESULT
FILE ERROR
84 1242 SCCP GLOBAL TITLE TRANSLATION
RESULT FILE ERROR
Meaning
Report on the output disturbances of the SCCP global title
translation. The results output record of the global title translation
contains incorrect information or global title modification cannot be
done to the existing global title number. The alarm may have an effect
to the traffic capacity of the system. A message that contains the
global title in question will not get to its destination.
Supplementary information fields
1 error code. Possible values are:
01 record number formed as a result of global title
translation causes a file access error when trying to
form an address to the Global Title Translation Result
File (GTRFIL)
02 translation of global title contains an unknown
destination point code
03 translation of global title contains an unknown
subsystem number
04 translation of global title contains a reference to a
record of the Global Title Modification File (GTMFIL).
When modifying the global title using the values of this
record, the result is an erroneous global title (e.g. too
many digits are added or removed)
2 record number of GTRFIL
3 global title standard, possible values are:
01 ITU-T
02 ANSI
4 global title indicator in the global title of an SCCP message.
The global title indicator is interpreted in following manner
when the value in the third supplementary field is 01 (ITU-T):
01 global title contains only the nature of address indicator
02 global title contains only the translation type
03 global title contains the translation type, the numbering
plan and the encoding scheme
04 global title contains the translation type, the numbering
plan, the encoding scheme and the nature of address
indicator
DN9813048
Issue 18-2
133
Disturbance Printouts (1000-1999) 1242 SCCP GLOBAL TITLE TRANSLATION RESULT
FILE ERROR
Id:0900d805806a941a
05-15 global title does not contain the translation type,
the numbering plan, the encoding scheme or the nature
of address indicator.
These global title indicator values have not been
defined in the ITU-T recommendations
The global title indicator is interpreted in following manner
when the value in the third supplementary field is 02 (ANSI):
01 global title contains the translation type, the numbering
plan and the encoding scheme
02 global title contains only the translation type
03-15 global title does not contain the translation type,
the numbering plan, the encoding scheme or the nature
of the address indicator.
These global title indicator values have not been
defined in the ANSI recommendations
5 translation type from the global title of the SCCP message.
The translation type is interpreted in the following manner
when the value in the third supplementary field is 01 (ITU-T):
00 translation type not in use
FF global title does not include translation type
In the national specification ANSI T1.112-1992 there are
values defined for the translation type with the third
supplementary field value 02 (ANSI) and with the fourth
supplementary field value 02. These values of the translation
type can be analysed in the normal way, but they do not cause
special procedures in the system
6 numbering plan and encoding scheme from the global title
of the SCCP message. The encoding scheme is encoded with the
least meaningful bits 1-4 in the following manner:
0000 unknown
0001 BCD, odd number of digits
0010 BCD, even number of digits
0011 reserved for future use
:
1110 reserved for future use
1111 encoding scheme not included in global title
The numbering plan is encoded with the most meaningful bits
5-8 in the following manner:
0000 unknown
0001 ISDN/telephone network numbering plan (E.164,E.163)
0010 reserved for future use
0011 data network numbering plan (X.121)
134 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1242 SCCP GLOBAL TITLE TRANSLATION RESULT
FILE ERROR
0100 telex network numbering plan (F.69)
0101 ship telephone network numbering plan (E.210,E.211)
0110 mobile telephone network numbering plan (E.212)
0111 ISDN/mobile telephone network numbering plan (E.214)
1000 reserved for future use
:
1110 reserved for future use
1111 numbering plan not included in global title
7 nature of address indicator from the global title of the SCCP
message. Possible values are:
01 subscriber number
02 reserved for national use
03 national meaningful number
04 international number
05 reserved for future use
:
FE reserved for future use
FF nature of address indicator not included in global title
8-15 address information from the global title of the SCCP message
so that, for example, the number 12345 is encoded
12 34 5F FF ...
Instructions
1. If the value of the first supplementary field is 01, use the NBI
command of the Global Title Analysis Handling MML (GTAHAN) to
check to which result the analysis in question should lead.
You may be able to correct the error by loading the GANFIL and
GAIFIL files from disk with the MML command DFM to the unit that
set the alarm. If the alarm is set only in one computer unit, a
unit restart or switchover may correct the situation. If loading
the files does not help, remove the analysis in question and the
result with the MML commands NBD and NAD. Then recreate them with
the MML commands NAC and NBC. Note that removing the result may
cause an outage in the traffic.
2. If the value of the first supplementary field is 02,
the disturbance may be caused by a file error. It may be
possible to correct the error by loading the GTRFIL file from
disk with the MML command DFM to the unit that set the alarm.
If loading the file does not correct the situation, find out
to which signalling point the analysis in question should
lead and use the MML command NAM to correct the signalling
point code.
3. If the value of the first supplementary field is 03, the
disturbance may be caused by a file error. It may be possible
to correct the error by loading the GTRFIL file from disk with
DN9813048
Issue 18-2
135
Disturbance Printouts (1000-1999) 1242 SCCP GLOBAL TITLE TRANSLATION RESULT
FILE ERROR
Id:0900d805806a941a
the MML command DFM to the unit that set the alarm. If loading
the file does not correct the situation, find out which
subsystem should be in the result and correct it with the MML
command NAM.
4. If the value of the first supplementary field is 04, use the
commands NAI and NAX of the Global Title Result Handling MML
(GREHAN) to check the global title information and, if
necessary, make corrections with the NAM and NAS commands.
Cancelling
No cancelling.
136 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1244 RUNNING OUT OF MESSAGE BUFFERS
85 1244 RUNNING OUT OF MESSAGE BUFFERS
Meaning
The amount of free message buffer memory in one message size class in
the computer is below the alarm limit used in supervision. The alarm
limit is usually set so low that the alarm indicates a critical
reduction in the amount of free message buffers.
When there are no free message buffers, reservation of a message fails
and this may disturb the functioning of the computer.
This alarm does not necessarily mean a fault. The alarm can also be
an indication of a temporary shortage of free message buffers caused
by a high processor load.
Supplementary information fields
1 size of message buffers in the message size class which is
running out of message buffers
2 number of messages allocated in the message size class
3 number of free messages in the message size class
Instructions
The reduction in the number of free message buffers may result from a
software fault or from an insufficient number of free message buffers
in the computer as opposed to the software build.
The latter one means a wrong dimensioning of the parameters.
As a precautionary act it is advisable to collect some information in
case the computer goes to a faulty state or gets restarted.
If the situation recurs, it is recommended to inform your local Nokia
Siemens Networks representative on the message usage data in
order to find out the nature and cause of the situation. In this
case, please attach the printouts of the commands mentioned below.
To get the message buffer usage information, start a telnet session for
the computer that is given as the object unit of the alarm, or give
the dmxshow command on the console of the computer.
A remote session to the computer (established with the service terminal
command ZRS or with the MML command ZDDS) should be avoided, because it
uses messages and it could even worsen the situation.
1. To get the information on the usage of message buffers, give the
service terminal commands
dmxshow -s
and
DN9813048
Issue 18-2
137
Disturbance Printouts (1000-1999) 1244 RUNNING OUT OF MESSAGE BUFFERS
Id:0900d805806a941a
dmxshow -m
Command dmxshow -a or dmxshow -A should not be used because it
heavily consumes the resources of the computer.
2. To display the computer log, give the service terminal command
clog -s -a
3. To display alarm history of the current date concerning the computer,
give the MML command
ZAHP:<unit_type>,<unit_index>;
Cancelling
No cancelling.
138 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1249 DATABASE DISK COPY HAS EXCEEDED MAX-
IMUM ALLOWED AGE
86 1249 DATABASE DISK COPY HAS
EXCEEDED MAXIMUM ALLOWED AGE
Meaning
Database dumping has not been successful for a long time due to
a high transaction load and the age of the disk copy has reached
its maximum limit. The dumping is now started with an option to
prevent transactions when overloading occurs. This strategy is
followed until the dumping is completed successfully.
Supplementary information fields
1 database index; this is still required in some database
applications even though the current trend is that the
database is identified by the values entered in the
two following supplementary information fields, i.e.
database name and database occurrence
2 database name
3 number of database occurrence
4 how much late the disk copy is from the state in memory.
The format of the value is hh:mm
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
139
Disturbance Printouts (1000-1999) 1250 DATA LINK LAYER PROTOCOL MISMATCH
Id:0900d805806a941a
87 1250 DATA LINK LAYER PROTOCOL
MISMATCH
Meaning
The second layer protocol (LAPD) of the D-channel of the primary rate
access has detected protocol errors. The cause may be a malfunction in
the unit or the equipment functioning as the terminal equipment, or a
faulty connection (loop) in the switching network or at some other point
of the PCM connection.
Supplementary information fields
1 number of the channel link set (D-channel)
2 D-channel index within the channel link set:
00 primary channel
01 back-up channel (in primary rate access only, not in use)
3 type of the channel link set:
00 primary rate access channel link set
01 subscriber module (SUB) channel link set
02 exchange terminal (ET) channel link set
03 functional unit channel link set
4 number of the D-channel's PCM
Instructions
The alarm usually appears when the transmitting direction
in the data link connection is connected to the receiving direction
within the network element or outside it.
The network element may also have been configured so that it is
functioning as the incorrect end of the connection from the point of
view of the LAPD protocol. Also, the LAPD protocol itself may
be faulty.
The instantaneous values of the counters that set the alarm can
be examined in real time, see instructions on LAPD statistics.
The incrementing of the counter RECEIPT OF NON-IMPLEMENTED FRAME
indicates a loop or incorrect configuration in the opposing end,
RECEIPT OF UNSOLICITED UA, RECEIPT OF FRAME WITH WRONG SIZE and
N201 ERROR indicate a malfunction in the opposing end.
Cancelling
No cancelling.
140 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1251 EXCESSIVE RETRANSMISSIONS ON DATA
LINK CONNECTION
88 1251 EXCESSIVE RETRANSMISSIONS ON
DATA LINK CONNECTION
Meaning
The second layer of the primary rate access D-channel does not
receive any answers to the command frames it has sent. The missing
answers may be due to a partial or total inoperation of the remote end,
or breaks in the data link connection.
The alarm usually appears in connection with short-term or permanent
breaks in the data link connection. The alarm may also indicate problems
with protocol in the data link connection layer. In other words, the
remote end does not, in some situations, respond according to the
recommendations.
Supplementary information fields
1 number of the channel link set (D-channel)
2 D-channel index within the channel link set:
00 primary channel
01 backup channel (in primary rate access only, not in use)
3 type of the channel link set:
00 primary rate access channel link set
01 subscriber module (SUB) channel link set
02 exchange terminal (ET) channel link set
03 functional unit channel link set
4 number of the D-channel's PCM
Instructions
The fault disturbing the D-channel may lie in the hardware of the
network elements, more probably, however, in the data link connection
or the synchronization between the network elements.
The working order of the data link connection can be monitored
with an MML command, see instructions on PCM statistics.
Synchronization may be handled with MML commands, see instructions on
synchronization.
In addition to possible breaks and external disturbances, it is
especially important to check in the data link connection, that
the PCM circuit signals and the protective sheath are connected
correctly in the connection points (ET, distribution frames).
The instantaneous values of the counters UNSUCCESSFUL RETRANSMISSION OF
SABME and RR/RNR/REJ which cause the alarm may be monitored in real
DN9813048
Issue 18-2
141
Disturbance Printouts (1000-1999) 1251 EXCESSIVE RETRANSMISSIONS ON DATA
LINK CONNECTION
Id:0900d805806a941a
time, see instructions on LAPD statistics.
The RR frame's failure to answer indicates breaks of data link
layer lasting a few seconds, while the SABME frame's failure to answer
indicates a break longer than that.
Cancelling
No cancelling.
142 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1252 EXCESSIVE ERROR RATE ON DATA LINK
CONNECTION
89 1252 EXCESSIVE ERROR RATE ON DATA
LINK CONNECTION
Meaning
There are transmission errors in the data link connection of the
primary rate access D-channel. The errors manifest themselves in
check sum errors of the second layer frames, and/or in overlong
frames due to the disappearance of frame signals.
Supplementary information fields
1 number of the channel link set (D-channel)
2 D-channel index within the channel link set:
00 primary channel
01 backup channel (in primary rate access only, not in use)
3 type of the channel link set:
00 primary rate access channel link set
01 subscriber module (SUB) channel link set
02 exchange terminal (ET) channel link set
03 functional unit channel link set
4 number of the D-channel's PCM
Instructions
The fault disturbing the D-channel may lie in the hardware of the
network elements, more probably, however, in the data link connection
or the synchronization between the network elements.
The working order of the data link connection can be monitored
with an MML command, see instructions on PCM Statistics.
Synchronization may be handled with MML commands, see instructions
on Synchronization. In addition to possible breaks and external
disturbances, it is especially important to check in the data link
connection, that the PCM circuit signals and the protective sheath
are connected correctly in the connection points
(ET, distribution frames).
The instantaneous values of the counter CRC ERRORS (check sum error)
which causes the alarm may be monitored in real
time, see instructions on LAPD Statistics.
Cancelling
No cancelling.
DN9813048
Issue 18-2
143
Disturbance Printouts (1000-1999) 1253 NO RESPONSE FROM PRIMARY RATE AC-
CESS TERMINAL
Id:0900d805806a941a
90 1253 NO RESPONSE FROM PRIMARY RATE
ACCESS TERMINAL
Meaning
The primary rate access terminal has not answered to the inquiries or
requests sent to it.
Supplementary information fields
1 index of the primary rate access terminal
2 channel link set number
3 D-channel index within the channel link set
4 type of the channel link set:
00 primary rate access channel link set
01 subscriber module (SUB) channel link set
02 exchange terminal (ET) channel link set
03 functional unit channel link set
5 message that was expected or a message to which response was
expected
6 internal state of D-channel
7 identifier of D-channel time supervision
Instructions
If the situation keeps occurring, check the existence and condition
of the primary rate access terminal.
Cancelling
No cancelling.
144 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1254 UNSOLICITED DATA LINK RE-ESTABLISH-
MENT
91 1254 UNSOLICITED DATA LINK RE-ESTAB-
LISHMENT
Meaning
A connection has been re-established on the D-channel, during which
some information may have been lost. The alarm usually occurs in
connection with unit restarts, but it can also occur in data
transmission connections of poor quality.
Supplementary information fields
1 number of the channel link set (D-channel)
2 D-channel index within the channel link set:
00 primary channel
01 backup channel (in primary rate access only, not in use)
3 type of the channel link set:
00 primary rate access channel link set
01 subscriber module (SUB) channel link set
02 exchange terminal (ET) channel link set
03 functional unit channel link set
4 number of the D-channel's PCM
Instructions
The alarm requires no actions. If the alarm keeps recurring, check the
quality of the connection, and the condition of the equipment.
Cancelling
No cancelling.
DN9813048
Issue 18-2
145
Disturbance Printouts (1000-1999) 1255 PRIMARY RATE ACCESS MESSAGE DISTRI-
BUTION ERROR
Id:0900d805806a941a
92 1255 PRIMARY RATE ACCESS MESSAGE
DISTRIBUTION ERROR
Meaning
The PXRECE has received a message which it cannot distribute to
the receiver.
Supplementary information fields
1 error code
1d erroneous protocol discriminator.
You can check its meaning in General Error Messages
of System
2 number of the primary rate access terminal
3 indicates the protocol discriminator of the
message received
4-9 indicates the next six fields of the message
Instructions
There is an erroneous protocol discriminator in the message received.
The operation of the counterpart must be checked. See also the log
printouts of the PXRECE. The log contains the heading of the erroneous
message.
Cancelling
No cancelling.
146 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1256 INCORRECT PRD MESSAGE FROM PRIMARY
RATE ACCESS TERMINAL
93 1256 INCORRECT PRD MESSAGE FROM
PRIMARY RATE ACCESS TERMINAL
Meaning
An incorrect message has been received from the primary rate access
terminal. This may be due to a fault or disturbance in the terminal
itself, or to the incorrect contents of the message sent by the
remote end.
Supplementary information fields
1 an error has been detected in the message
1d the message is too long
You can check the meaning of other error codes
in General Error Messages of System
2 number of the primary rate access terminal
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
147
Disturbance Printouts (1000-1999) 1260 X.25/ETHERNET DATA TERMINAL SPONTA-
NEOUS RESTART
Id:0900d805806a941a
94 1260 X.25/ETHERNET DATA TERMINAL
SPONTANEOUS RESTART
Meaning
The AC25-S/AC25-A/AS7-U/AS7-V/AS7-A/COCEN plug-in unit has restarted.
As a result of the restart of the plug-in unit AC25-S/AS7-U, the OSI
administration releases all X.25 connections via that plug-in unit.
The plug-in unit is reinitialized after the connections have been
released.
The restart of the COCEN plug-in unit does not result in the release
of OSI or TCP/IP connections via that plug-in unit, but the level
of service is temporarily decreased.
Supplementary information fields
1 the index of the reinitialized plug-in unit
Instructions
If this alarm is preceded by a notice informing that the
computer unit hosting the plug-in unit has restarted, then
there is no error. When this alarm is received, the possible
effects of the restart on the OSI connections should be checked.
Cancelling
No cancelling.
148 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1261 OSI CHANNEL GROUP UNREACHABLE
95 1261 OSI CHANNEL GROUP UNREACHABLE
Meaning
The channel group becomes unavailable and this means that remote
applications all of whose labels use unavailable channel groups
become unreachable. The channel group becoming unavailable is caused
by the fact that the group contains no available channels.
Supplementary information fields
1 the name of the channel group that has become unavailable
Instructions
Normally, when a channel group has become unavailable it is because
plug-in units have been restarted, and no error is involved. The
availability of a channel group can be checked, when necessary, by
means of the QGI MML command and its GROUP STATE column. The value
UA means an unavailable channel group, and AV an available one.
Cancelling
No cancelling.
DN9813048
Issue 18-2
149
Disturbance Printouts (1000-1999) 1262 OSI SERVICE PROVIDER RESET
Id:0900d805806a941a
96 1262 OSI SERVICE PROVIDER RESET
Meaning
An OSI program block restart is caused by an internal fault
situation, e.g. when the memory space allocated to the program
block has been exceeded.
The disconnection of the OSI connections maintained by the
program block results in the program block being restarted.
The memory allocation situation of the program block prior
to the restart is written into the log of the unit where the
centralised part of the OSI administration is located.
Supplementary information fields
1 the family identifier indicates which program block
has been restarted. Possible values are 0000 - FFFF
2 the diagnostics field indicates the reason why the
program block is restarted. Possible values are:
01 : memory space request too large
02 : memory space exceeded
03 : erroneous interface table
04 : ASN.1 decoding error
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
150 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1263 OSI SERVICE PROVIDER INTERFACE ERROR
97 1263 OSI SERVICE PROVIDER INTERFACE
ERROR
Meaning
An OSI program block has received a message that has not been specified
in its interface. The sender of the message is written into the log of
the unit that accomodates the centralized part of the OSI administration.
Supplementary information fields
1 identifies the program block in question. Possible
values are 0000 - FFFF
2 the interface field identifies the interface where
the fault occurred. Possible values are
00 : administration interface
01 : upper interface
02 : lower interface
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
151
Disturbance Printouts (1000-1999) 1264 OSI INCOMING CALL DENIED
Id:0900d805806a941a
98 1264 OSI INCOMING CALL DENIED
Meaning
A call has been received from the network to a local application with
incoming call denial.
Supplementary information fields
1 the first part (max. 7 digits) of the address of
the calling remote end
2 the remaining part (8 digits) of the address of
the calling remote end
3 number of digits in the address of the calling
remote end. The value is between 0x00 and 0x0F
4 OADFIL file record containing the called
local address
5 plug-in unit from where the call arrived
Instructions
If several disturbance notices are received, check the files
related to the coding of the address fields of the message, at
both ends of the trunk circuit.
Cancelling
No cancelling.
152 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1273 ASP ACTIVATION FAILED
99 1273 ASP ACTIVATION FAILED
Meaning
The activation of the ASP (Application Server Process) or
SGP (Signalling Gateway Process) has not succeeded. The alarm is for
ASP if the network element is working as a Signalling Gateway or for
SGP if the network element is working as an Application Server.
The ASP/SGP is activated by the exchange of ASPSM (ASP State
Maintenance), RKM (Routing Key Management) and ASPTM (ASP Traffic
Maintenance) messages between the two M3UA endpoints. So when this alarm
is set by the S3CMAN (SCTP association manager) program block, something
has probably gone wrong during that ASP message exchanging. The 2nd and
3rd supplementary information fields show the ASP message at which the
ASP activation failed. Other reason for the alarm is the insufficient
resources, such as, an insufficient amount of records in work files
which prevents a new ASP to be activated. If none of the ASPs in the
specified association set in the 4th supplementary information field
become active, it means that the whole Application Server or Signalling
Gateway is not available to this network element. Otherwise the signal
transmission capacity may only be somewhat decreased.
Supplementary information fields
1 type of the ASP activation failure. Possible values are:
01 Unsupported M3UA version in M3UA message header
02 M3UA draft version used in message differs from configured
03 The traffic handling mode in M3UA message does not match with the
configured one
04 The routing context value in M3UA message does not match with the
stored one
05 No matching configured routing key was found for the routing
key found in REGREQ message.
06 An unsupported parameter was found inside the routing key
parameter in REGREQ message.
07 Registration status in REGRSP is not 0
08 The local routing key identifier in REGRSP differs from that
one that was sent in REGREQ
09 There is no space for the new ASP in SGWFIL file
0A There is no space for the new ASP in S3WORK file
0B A mandatory parameter is missing in M3UA message
0C A M3UA message is received that is not in accordance with the
role specified in the association set, shown by ZOYI MML command,
such as, the receiving of ASPUP, ASPAC, REGREQ at the ASP even
if only the SG is prepared to receive them.
0D A communication up notification was received at the server side
with unconfigured IP address or the unit from which the
communication up was received is not the configured unit
shown by ZOYI MML command
0E ASPAC (ASP Active) message was received for the ASP in wrong
DN9813048
Issue 18-2
153
Disturbance Printouts (1000-1999) 1273 ASP ACTIVATION FAILED
Id:0900d805806a941a
state, i.e., for ASP the state of which is not inactive.
0F The outbound stream count in the communication up notification
is less than was ordered in the associate primitive
2 message class of M3UA message. Possible values are:
03 ASP State Maintenance (ASPSM) messages
04 ASP Traffic Maintenance (ASPTM) Messages
09 Routing Key Management (RKM) Messages
3 message type of M3UA message. Possible values are dependent
on the preceding supplementary information field:
When the 2nd supplementary information field is 03, the
possible values are:
01 ASP Up (ASPUP)
04 ASP Up Acknowledgement (ASPUP ACK)
When 2nd supplementary information field is 04, the
possible values are:
01 ASP Active (ASPAC)
03 ASP Active Acknowledgement (ASPAC ACK)
When 2nd supplementary information field is 09, the
possible values are:
01 Registration Request (REG REG)
02 Registration Response (REG RSP)
4 association set to which the ASP belongs, 0FFFF if not known
5 when an inconsistent parameter value is included in the M3UA
message, this supplementary information field shows that
inconsistent parameter value. The parameter, which has the
inconsistent value is deduced from the value of the
1st supplementary information field:
01 means m3ua version, 02 means m3ua draft version,
03 means traffic handling mode, 04 means routing context.
Value 0FFFFFFFF means that this field is not applicable for
the alarm.
6 the value of the parameter, with which the preceding information
field is inconsistent. In practice this field shows the
value that is configured and shown also by the ZOYI MML command.
Value 0FFFFFFFF means that this field is not applicable for
the alarm.
7 the parameter tag of the missing parameter. Possible values are:
154 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1273 ASP ACTIVATION FAILED
06 Routing Context
0207 Routing Key
020A Local_Routing Key Identifier
020B Destination Point Code
0200 Network Appearance
0208 Registration Result
0212 Registration Status
0FFFF There is no missing parameter, i.e., the field is not
applicable with the alarm
8 the identifier that unambiguously identifies the ASP, the
value shows the SGWFIL record number.
Instructions
If the value of the 1st supplementary information field is 01:
The peer M3UA is using M3UA RFC version that is newer than supported.
Check whether it is possible to configure the peer M3UA to use
the supported version. The version that the peer M3UA is using is
specified by the 5th supplementary information field. The version
that is supported is specified by the 6th supplementary information
field.
If the value of the 1st supplementary information field is 02:
The peer M3UA is using M3UA draft version, which is different than
the one configured at this network element in the association set
specified in the 4th supplementary information field. The
configured M3UA draft version is also specified in the 6th
supplementary information field, possible values are 07 or 09. The
M3UA draft version that the peer M3UA is using is specified in the
5th supplementary information field. The M3UA message, in which the
M3UA draft version was found is specified in the 2nd and 3rd
supplementary fields. If the configured M3UA draft version needs to
be modified in this network element, use ZOYM MML command and give
the association set and the M3UA draft version as the parameters.
If the value of the 1st supplementary information field is 03:
The traffic handling mode value that is included in the M3UA message
is different from the one that is configured in the association
set specified in the 4th supplementary information field. The
configured traffic handling mode value is also specified in the
6th supplementary information field. The value of the traffic
handling mode included in the M3UA message is specified by the 5th
supplementary information field. The M3UA message, in which the
traffic handling mode was included is specified in the 2nd and 3rd
supplementary fields. Check which traffic-handling mode is correct
and change the configuration at either this network element or at
the peer M3UA. If the value needs to be modified at
DN9813048
Issue 18-2
155
Disturbance Printouts (1000-1999) 1273 ASP ACTIVATION FAILED
Id:0900d805806a941a
this network element, use the ZOYM MML command and give the
association set and the correct traffic handling mode as the
parameters.
If the value of the 1st supplementary information field is 04:
The routing context value that is included in the M3UA message
differs from the one stored at this network element and was
determined automatically by this network element during the routing
key registration, i.e., when handling the REGREQ message. It is also
possible that there is no routing context value stored in this
network element, which means that the routing key registration was
not done. The routing context value stored at this network element
is specified in the 6th supplementary information field. The value
of the routing context included in the M3UA message is specified in
the 5th supplementary information field. The M3UA message, in which
the routing context was included is specified in the 2nd and 3rd
supplementary fields. Try to find out why the peer M3UA does not
use the correct routing context value, or if the routing context
is not stored at this network element (the 6th supplementary
information field is 0FFFFFFFF)and if it is possible to configure
the peer M3UA so that the routing context parameter is not used in
the message. If that peer M3UA is operating in the Nokia Siemens
Networks network element, fill in a Problem Report and send it to
your local Nokia Siemens Networks representative.
In the problem report include this alarm And printouts of following
MML commands ("CM,0" in the following commands refer to active
central memory):
1) ZOYI::A;
2) ZDFD:CM,0:A79,,N,;
3) ZDFD:CM,0:AF3,,N,;
If the value of the 1st supplementary information field is 05:
No matching configured routing key was found for the routing
key found in REGREQ message. The routing key here refers to the
network appearance and the destination point code (DPC). The network
appearance value included in REGREQ message is specified in the
5th supplementary information field and the DPC included in REGREQ
message is specified in the 6th supplementary information field.
Check that the network appearance value is correct in the association
set where the ASP is about to be added by the routing key
registration procedure. If the value needs to be modified at this
network element, use ZOYM MML command and give the association set
and the correct network appearance value as the parameters. If the
network appearance value is correct, check that the M3UA based link
set is configured to the right signalling point at this network
element. If not you have to delete the signalling link set and route
set and then recreate them so that the signalling point code is
correct.
156 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1273 ASP ACTIVATION FAILED
If the value of the 1st supplementary information field is 06:
The peer M3UA is using an unsupported parameter inside the routing
key parameter of REGREQ message. Only network appearance and
destination point code are supported parameters inside a routing key.
The unsupported parameter tag inside the routing key parameter is
specified in the 5th supplementary information field and the
value of that unsupported parameter in the 6th supplementary
information field. Check whether it is possible to configure the
peer M3UA to use only network appearance and DPC as a routing key.
If not do not use routing key registration at both ends if possible,
and at this network element modify the registration_request parameter
to value "NO" in the association set, in which the ASP is about
to be added by the routing key registration procedure as follows:
1) Change the state of the corresponding M3UA based link to
UA-INU, with ZNLC MML command.
2) Change the registration_request parameter giving the
association set and the new value for registration_request
parameter as the parameters in ZOYM MML command.
3) Change the state of the corresponding M3UA based link to
AV-EX, with ZNLC MML command.
If the routing key registration is turned off, you have to add the
ASPs in the corresponding association set (the role of the
association set is server) by giving the destination IP addresses
of the ASPs.
If the value of the 1st supplementary information field is 07:
The peer M3UA does not answer with success status to the routing
key registration request sent by this network element. The status
value that is returned by the peer M3UA is specified by the 5th
supplementary information field.
When the 5th supplementary information field is 03 (invalid
network appearance):
Check that the network appearance value configured in the
association set specified by the 4th supplementary
information field is correct. If the value needs to be
modified at this network element, use ZOYM MML command and
give the association set and the correct network appearance
value as the parameters to the ZOYM MML command.
When the 5th supplementary information field is 02 (invalid
DPC) or 04 (invalid routing key):
Check whether the peer M3UA supports network appearance and
DPC as a routing key. If so check that the network appearance
value configured in the association set specified by the
4th supplementary information field is correct. If the value
needs to be modified at this network element, use ZOYM MML
DN9813048
Issue 18-2
157
Disturbance Printouts (1000-1999) 1273 ASP ACTIVATION FAILED
Id:0900d805806a941a
command and give the association set and the correct network
appearance value as the parameters to the ZOYM MML command.
If the peer M3UA does not currently support network
appearance and DPC as a routing key, check whether it is
possible to configure the peer M3UA as such. If not, do not
use routing key registration at both ends if possible, and
at this network element modify the registration_request
parameter to value "NO", as follows:
1) Change the state of the corresponding M3UA based link to
UA-INU, with ZNLC MML command.
2) Change the registration_request parameter giving the

association
set specified in the 4th supplementary
information field and the new value for
registration_request parameter as the parameters in ZOYM
MML command.
3) Change the state of the corresponding M3UA based link to
AV-EX, with ZNLC MML command.
When the 5th supplementary information field is
01 (error-unknown), 05 (permission denied), 06 (cannot support
unique routing), 07 (routing key not currently provisioned),
08 (insufficient resources):
Do not use routing key registration at both ends if possible,
and at this network element modify the registration_request
parameter to value "NO", as follows:
1) Change the state of the corresponding M3UA based link to
UA-INU, with ZNLC MML command.
2) Change the registration_request parameter giving the
association set specified in the 4th supplementary
information field and the new value for
registration_request parameter as the parameters in
ZOYM MML command.
3) Change the state of the corresponding M3UA based link to
AV-EX, with ZNLC MML command.
When the 5th supplementary information field is 09 (unsupported
RK parameter field):
Check whether the peer M3UA supports network appearance and
DPC as a routing key. If the peer M3UA does not currently
support network appearance and DPC as a routing key, check
if it is possible to configure the peer M3UA such.
158 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1273 ASP ACTIVATION FAILED
If not, do not use routing key registration at both ends
if possible, and in this network element modify the
registration_request parameter to value "NO", as follows:
1) Change the state of the corresponding M3UA based link to
UA-INU, with ZNLC MML command.
2) Change the registration_request parameter giving the
association set specified in the 4th supplementary
information field and the new value for
registration_request parameter as the parameters in
ZOYM MML command.
3) Change the state of the corresponding M3UA based link to
AV-EX, with ZNLC MML command.
When the 5th supplementary information field is 0A (unsupported/
invalid Traffic handling mode):
Check that the value of the traffic handling mode
configured at this network element in the association set
specified by the 4th supplementary information field is
correct. If the value needs to be modified at this network
element, use the ZOYM MML command and give the association
set and the correct traffic handling mode value as the
parameters to the ZOYM MML command.
If the value of the 1st supplementary information field is 08:
The local routing key identifier value in the received REGRSP was
not the same as it was in the REGREQ sent by this network element
(REGRSP is a response message to REGREQ message). The local
RK-identifier value that was included in the REGREQ is specified by
the 5th supplementary information field and the local RK-identifier
value that was included in the REGRSP is specified by the 6th
supplementary information field. Try to find out why the peer M3UA
does not answer with the correct local RK-identifier value in the
REGRSP. If the peer M3UA is operating in the Nokia Siemens Networks
network element, fill in a Problem Report and send it to your local
Nokia Siemens Networks representative. In the problem report include
this alarm and printouts of following MML commands ("CM,0" in the
following commands refers to active central memory):
1) ZOYI::A;
2) ZDFD:CM,0:A79,,N,;
3) ZDFD:CM,0:AF3,,N,;
If the value of the 1st supplementary information field is 09 or 0A:
Fill in a Problem Report and send it to your local Nokia Siemens
Networks representative. In the problem report include this alarm
and printouts of following MML commands ("CM,0" in the following
commands refer to active central memory):
1) ZOYI::A;
2) ZDFD:CM,0:A79,,N,;
DN9813048
Issue 18-2
159
Disturbance Printouts (1000-1999) 1273 ASP ACTIVATION FAILED
Id:0900d805806a941a
3) ZDFD:CM,0:AF3,,N,;
If the value of the 1st supplementary information field is 0B:
A mandatory parameter is missing in a M3UA message. The parameter
tag of the missing parameter is specified in the 7th supplementary
information field. Try to find out why the peer M3UA does not use
that parameter in the M3UA message specified in the 2nd and 3rd
supplementary information field. If the peer M3UA is operating in
the Nokia Siemens Networks network element, fill in the Problem
Report from this network element and send it to your local Nokia
Siemens Networks representative. In the problem report include
this alarm and printouts of following MML commands ("CM,0" in the
following commands refer to active central memory):
1) ZOYI::A;
2) ZDFD:CM,0:A79,,N,;
3) ZDFD:CM,0:AF3,,N,;
If the value of the 1st supplementary information field is 0C:
Check whether the role specified in the 4th supplementary information
field is correct. If not, you have to change the role as follows:
1) Change the state of the corresponding M3UA based link to
UA-INU, with ZNLC MML command.
2) Change the role parameter giving the association set specified in
the 4th supplementary information field and the new value for
the role parameter as the parameters in ZOYM MML command.
3) Change the state of the corresponding M3UA based link to AV-EX,
with the ZNLC MML command.
If the value of the 1st supplementary information field is 0D:
The 5th supplementary information field shows the log reference.
The 6th supplementary information field shows the unit, from which
the communication up was received. At the same time as the alarm
two logs are written: first with the same log reference as in the
alarm, second with the IP address that was not configured. In the
second log the first byte shows the IP address version, 0 means IPv4
and 1 means IPv6. Check whether the IP address written to the log
should be configured to some association set, which has the role of
server. If so, add the IP address to the desired association set
with ZOYA MML command.
If the value of the 1st supplementary information field is 0E:
The reason for the alarm may be that the "registration request"
parameter has value YES even if it should have value NO. Change the
value of the parameter to NO, as follows:
1) Change the state of the corresponding M3UA based link to UA-INU,
with the ZNLC MML command.
2) Change the registration_request parameter giving the association
160 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1273 ASP ACTIVATION FAILED
set specified in the 4th supplementary information field and the
new value = NO for registration_request parameter as the
parameters in ZOYM MML command.
3) Change the state of the corresponding M3UA based link to AV-EX,
with the ZNLC MML command.
If the value of the 1st supplementary information field is 0F:
SCTP could not establish the association with the configured amount
of outbound streams. The amount of streams is configured in the
association set basis. Use ZOYI::A; command to see the configured
amount of streams that is further specified as the sum of parameters
"first data stream number" and "data stream count". This SCTP user
adjusted to use the lower amount of outbound streams that was
returned in the communication up notification. The amount of SCTP
streams that are returned in the communication up notification are
shown in the 5th supplementary information field. The amount of
configured streams is shown in the 6th supplementary information
field.
Cancelling
No cancelling.
DN9813048
Issue 18-2
161
Disturbance Printouts (1000-1999) 1280 INTERNAL COMMUNICATION CHANNEL FAIL-
URE
Id:0900d805806a941a
100 1280 INTERNAL COMMUNICATION
CHANNEL FAILURE
Meaning
A failure has been detected in the communication between the
preprocessors of the system, or between a preprocessor unit and
its host computer. The failure hampers communication.
Supplementary information fields
1 type of the preprocessor unit generating the alarm or
suspected faulty.
See instructions on Diagnostics and Testing
2 index of the unit generating the alarm or suspected
faulty; if .. the index is not known
3 channel identifier within the unit:
SBCN: FFFF host computer
0000 RSCN (SUB 0)
VXCN: FFFF host computer
0000 RSCN (SUB 0)
RSCN: FFFF host computer
1...7 index of SBCN unit (SUB 1-7)
8 CLxTG-0 (CLSS) or CLET-0 (CLES)
9 CLxTG-1 (CLSS) or CLET-1 (CLES)
CLxTG: FFFF host computer or RSCN
0 CLxTG
CLET: FFFF RSCN
0 CLET
ATMX: FFFF host computer
TRCO: FFFF host computer
1...4 index of ET2x
HWAT 0 HWAT
4 type of the failure:
01 connection establishment failed
02 connection re-establishment
03 message queue overflow
04 CRC or some other error ratio limit of the frame level
has been exceeded
05 protocol error
06 loop test failed
07 error ratio limit of the time supervision has been
exceeded
FF other failure
162 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1280 INTERNAL COMMUNICATION CHANNEL FAIL-
URE
Instructions
If the connection establishment fails, check the wirings to the serial
communication of the unit (clock system, serial communication bus) and
the functioning of the unit of the connection's remote end.
A successful re-establishment of the connection is notified after
a temporary disturbance. Some messages of the applications may
have disappeared, in which case the operations related to the unit
should be observed.
The overflow of the unit's message queue is caused either by the
inability of the data transmission connection to transmit messages
at a speed corresponding to the speed of message requestes
(an overload situation in the remote end or disturbances in the
data transmission connection) or by an internal overload in the
unit. The consequences are the same as in the re-establishment
of the connection.
If the failure type is "protocol error", check especially the
wirings or strappings indicating the unit index of the units,
as well as the PCM cabling and possible transmission equipment,
including the ET.
If the loop test has failed, you have to check and possibly
replace the plug-in unit that caused the alarm. The clock system,
i.e. the clock units or the cabling, may also be faulty.
Cancelling
No cancelling.
DN9813048
Issue 18-2
163
Disturbance Printouts (1000-1999) 1282 ASSOCIATION PARAMETER FAILURE
Id:0900d805806a941a
101 1282 ASSOCIATION PARAMETER FAILURE
Meaning
Parameter setting has failed concerning Signalling System No. 7 (SS7)
signalling over Internet Protocol (IP).
The MTP3 User Adaptation Layer (M3UA) protocol has failed in setting at
least one of the Stream Control Transmission Protocol (SCTP) parameters
in the context of the SCTP association establishment.
This means that the value(s) of the SCTP association parameter(s)
do not change and so the value(s) of the parameter(s) are not
necessarily the values that the user has configured. When the parameter
setting fails, SCTP operates with the old value of the parameter.
Supplementary information fields
1 SCTP Payload Protocol Identifier
1 - IUA RFC3057
2 - M2UA RFC3331
3 - M3UA RFC3332
4 - SUA RFC2960
5 - M2PA RFC2960
6 - V5UA RFC2960
7 - H.248 H.248
8 - BICC/Q.2150.3 Q.1902.1/Q.2150.3
9 - TALI RFC3094
10 - DUA <draft-ietf-sigtran-dua-03.txt> Ong
11 - ASAP <draft-ietf-rserpool-asap-03.txt> Ong
12 - ENRP <draft-ietf-rserpool-enrp-03.txt> Ong
13 - H.323 H.323
14-Q.IPC/Q.2150.3 Q.2631.1/Q.2150.3
2 IUA:
association number
M3UA:
association set, to which the association belongs
3 IUA:
Not applicable
M3UA:
index of the association inside the association set.
The value is between 0-31
4 identifier of the SCTP association within the computer unit
5 number of the socket corresponding the association
164 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1282 ASSOCIATION PARAMETER FAILURE
6 status of the socket option setting corresponding the
parameters. Value of the field is one of the following values
or a combination (sum) of some of the following values.
0001 SCTP Retransmission Timeout parameter setting failed.
Corresponding parameter names are RTI.INIT, RTO.MIN and
RTO.MAX.
0002 SCTP Peer Address parameter setting failed. Corresponding
parameter names are HB.INTERVAL and PATH.MAX.RETRANS.
0004 SCTP Association parameter setting failed. Corresponding
parameter name is ASSOCIATION.MAX.RETRANS.
0008 SCTP Checksum algorithm selection parameter setting failed.
0010 SCTP Bundling parameter setting failed.
0020 SCTP SACK parameter setting failed.
Instructions
Fill in a Problem Report and send it to your local Nokia Siemens
Networks representative.
Enclose the printout outputs with the MML commands ZOYI::A; and
ZOYO; in the failure report. The ZOYI command shows the information
of the SCTP associations and ZOYO shows the SCTP association parameter
values. Enclose also the log writings of the S3ZOCK program block in the
computer log of the signalling unit identified in the first two fields.
Computer log writings can be obtained with service terminal commands
ZGD and ZGS.
Cancelling
No cancelling
DN9813048
Issue 18-2
165
Disturbance Printouts (1000-1999) 1293 SCCP GT SCREENING APPLIED
Id:0900d805806a941a
102 1293 SCCP GT SCREENING APPLIED
Meaning
SCCP has detected at the signalling transfer point a signalling message
for which this alarm must be set. Additionally, also the transit of the
signalling message is to be prevented.
This conclusion is based on the calling and the called global
titles included in the message.
If the transit message is destroyed, it may cause disturbance
in the function of the user parts of the signalling point that sent
the message. Usage restrictions for transit messages are usually set
on exchanges that function on another operator's interface.
Supplementary information fields
1 type of access right violation of the STP function (cause code)
01 the source point behind the calling GTT result should not
send signalling messages with the called GT, the translation
of which leads to the called GTT result in question
(the message has been transmitted)
02 the source point behind the calling GTT result is not allowed
to send signalling messages with the called GT, the translation
of which leads to the called GTT result in question
(the message has been destroyed or sent back)
2 signalling network of the adjacent point from which the processed
signalling message was received. Signalling network can get the
following values:
00 international network 0, IN0
04 international network 1, IN1
08 national network 0, NA0
0C national network 1, NA1
3 point code value of the adjacent point from which the processed
signalling message was received. This and the 2nd supplementary
information field together indicate the signalling point from
which the message was received, that is, the linkset from which
the message was received.
4 the calling GTT result into which the analysis of the calling GT has
led. The calling GTT result and the calling GT analysis that lead
to that result can be checked with the MML commands ZODL and ZODJ
respectively.
5 the called GTT result into which the analysis of the called GT has
led. The called GTT result and the called GT analysis that lead
to that result can be checked with the MML commands ZNAI and ZNBI
166 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1293 SCCP GT SCREENING APPLIED
respectively.
6 the global title standard and the global title indicator used in the
calling global title of the SCCP message. The standard is encoded
with the most meaningful bits 5-8 in the following manner:
01 ITU-T
02 ANSI
The global title indicator is encoded with the least meaningful bits
1-4. The global title indicator is interpreted in the following
manner when the value in the most meaningful bits 5-8 is
01 (ITU-T):
01 global title contains only the nature of address
indicator
02 global title contains only the translation type
03 global title contains the translation type, the
numbering plan, and the encoding scheme
04 global title contains the translation type, the
numbering plan, the encoding scheme, and the nature
of address indicator
05-15 global title does not contain the translation type,
the numbering plan, the encoding scheme or the
nature of address indicator. These global title
indicator values have not been defined in the
ITU-T recommendations
The global title indicator is interpreted in the following manner
when the value in the most meaningful bits 5-8 is 02 (ANSI):
01 global title contains the translation type, the
numbering plan and the encoding scheme
02 global title contains only the translation type
03-15 global title does not contain the translation type,
the numbering plan, the encoding scheme or the
nature of address indicator. These global title
indicator values have not been defined in the ANSI
recommendations
7 translation type from the global title included in the calling
party address of the processed SCCP message.
The translation type values 0 and FF are interpreted in the
following manner when the value in the least significant bits 1-4
in the sixth supplementary field is 01 (ITU-T):
00 translation type not in use
FF global title does not include translation type
For the case the standard is ANSI and the global title indicator
is 02, there are values defined for the translation type in the
DN9813048
Issue 18-2
167
Disturbance Printouts (1000-1999) 1293 SCCP GT SCREENING APPLIED
Id:0900d805806a941a
national specification ANSI T1.112-1992. These values of the
translation type can be analysed in the normal way, but they
do not cause special procedures in the system
8 numbering plan and the four least meaningful bits of the nature
of address indicator from the global title included in the calling
party address of the processed SCCP message.
The numbering plan is encoded with the most meaningful bits 5-8
in the following manner:
0000 unknown
0001 ISDN/telephone network numbering plan
(E.164,E.163)
0010 reserved for future use
0011 data network numbering plan (X.121)
0100 telex network numbering plan (F.69)
0101 ship telephone network numbering plan
(E.210,E.211)
0110 mobile telephone network numbering plan (E.212)
0111 ISDN/mobile telephone network numbering plan
(E.214)
1000 reserved for future use
:
1110 reserved for future use
1111 numbering plan not included in global title
The four least meaningful bits of the nature of address indicator is
encoded with the least meaningful bits 1-4 in the following manner:
0001 subscriber number
0010 reserved for national use
0011 national meaningful number
0100 international number
0101 reserved for future use
:
1110 reserved for future use
1111 nature of address indicator not included in global
title
9-11 address information from the global title included in the calling
party address of the processed SCCP message so that, for example,
the number 12345 is encoded
12 34 5F.
If the address information includes more than 6 digits, the address
information includes the first 6 digits.
Instructions
SCCP global title screening information says that messages with the
calling global title and the called global title combination in question
should not be transmitted. The analysis of the calling global title leads
168 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1293 SCCP GT SCREENING APPLIED
to the calling GTT result as mentioned in the Supplementary information
field 4. The analysis of the called global title leads to the called GTT
result as mentioned in the Supplementary information field 5.
If the value of the Supplementary information field 1 (cause code) was 1,
the message was transmitted. If the value of the Supplementary
information field 1 (cause code) was 2, the message has been destroyed or
sent back. Check if this restriction is justified and remove the blocking
with the MML command ODN if necessary. Otherwise the operator who
owns the signalling point from which the message has been originated,
or alternatively the operator who owns the adjacent signalling point
from which the message was received, should be notified about an access
right violation.
For tracing the operator of the originating signalling point, the
information supplied in the Supplementary information fields 2, 3, 4, 6,
7, 8 and 9 could be used: the Supplementary information fields 2 and 3
show the adjacent point from which the message was received;
the Supplementary information fields 6, 7, 8 and 9 can be used to get
the calling global title from which the message was originated. The
Supplementary information field 4 (calling GTT result) can also be used
to find out the calling GT via calling GT analysis data, so that the
calling GT analysis is sought using the MML command ZODJ, which leads to
that calling GTT result record.
Cancelling
No cancelling.
DN9813048
Issue 18-2
169
Disturbance Printouts (1000-1999) 1300 SUPERVISION CONNECTION TO UNIT LOST
Id:0900d805806a941a
103 1300 SUPERVISION CONNECTION TO UNIT
LOST
Meaning
The unit has not responded in the allotted time to a supervision
message sent by the supervisory unit. The supervisor has lost the
connection to the unit and waits if the unit has restarted or failed.
Recovery actions have been started at once and after a short period
there will be another alarm, which tells the reason for the recovery:
1001 UNIT RESTARTED or
1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE
Supplementary information fields
Instructions
The alarm requires no actions.
The alarm does not have the supporting rule because the recovery actions
have been started and activated by the supervisor.
Cancelling
No cancelling.
170 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1301 PCU DIGITAL SIGNAL PROCESSOR RESTART
104 1301 PCU DIGITAL SIGNAL PROCESSOR
RESTART
Meaning
The PCU digital signal processor (DSP) has not answered to a supervision
message sent from the PCU Power Quicc processor, or the DSP has reported
that a critical process running on it has died.
Due to the failure, the signal processor and the data channels
handled by it are temporarily out of use.
The PCU Power Quicc processor tries to reload and restart the DSP.
Supplementary information fields
1 slot position number of the plug-in unit in the cartridge.
0xFF means that the slot position number is not available
2 plug-in unit index of the plug-in unit in the cartridge
3 number of the restarted DSP (0...7)
4 01 Periodic Supervision of DSP failed.
The PQ2 does not get an answer to a periodic request sent to the
DSP for a preconfigured maximum number of times_
02 Failure reported by DSP itself.
The Component Manager of the DSP has reported that a critical
process running on the DSP has died_
Instructions
The alarm requires no actions.
Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when
the fault has been corrected.
DN9813048
Issue 18-2
171
Disturbance Printouts (1000-1999) 1302 PAGING OVERLOAD
Id:0900d805806a941a
105 1302 PAGING OVERLOAD
Meaning
The BSC sends an overload message to the MSC in overload situations
inside the BSC. At the arrival of this message, the MSC will decrease
the amount of paging by a certain percentage. This will help the BSC
to cope with the unusually high amount of paging messages.
The BSC sets the alarm when a predefined threshold of discarded
paging messages has been exceeded.
Supplementary information fields
1 the count of Overload message that BSC has been sent to MSC in
overload situations
2 the count of rejected ps-paging messages (gb-interface)
inside the BCSU
3 the count of rejected cs-paging messages (gb-interface)
inside the BCSU
4 the count of rejected paging messages (A-interface)
inside the BCSU
Instructions
The alarm requires no actions.
The alarm informs which BCSU unit has overload.
Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when
the fault has been corrected.
172 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1339 ACTIVE FRAMER UNIT FAILURE
106 1339 ACTIVE FRAMER UNIT FAILURE
Meaning
The system has detected a failure in the active framer STM-1/OC-3
interface unit. The failure was detected in the counterpart unit either
by the switchover logic circuit or because of consecutive failures in
the active framer unit supervision. The counterpart unit has taken the
role of the active framer unit and recovery actions have been started for
the failed unit.
Supplementary information fields
1 00 unknown reason
01 failure is detected by means of heartbeating
02 failure is detected by switchover logic circuit
Instructions
The alarm supports the activation of the automatic recovery for the
object unit. You can check the supporting amount of the alarm with
the MML command ARO.
The automatic recovery starts a fault diagnosis program which gives
a diagnosis report indicating the possible hardware fault. If necessary,
replace the defective plug-in unit.
If the automatic recovery and fault diagnosis was not started after the
alarm occurred, or if the automatic fault diagnosis did not find any
hardware faults, do the following:
1. Use the MML command UDU to run a fault diagnosis for the object unit
of the alarm in order to find possible hardware faults. If necessary,
replace the defective plug-in unit.
2. Use the service terminal command clog to check in the error log of the
Chorus plug-in unit that no major software defects have occurred
in the functional unit.
3. If you find defects in the functioning of the software, fill in a
Failure Report and send it to your local Nokia Siemens Networks
representative. Attach the contents of the Chorus computer log to
the Failure Report.
4. If you could not find any defects in the plug-in unit and restarting
the functional unit did not solve the problem, contact your local
Nokia Siemens Networks representative.
Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when
the fault has been corrected.
DN9813048
Issue 18-2
173
Disturbance Printouts (1000-1999) 1339 ACTIVE FRAMER UNIT FAILURE
Id:0900d805806a941a
The system supervises the object unit of the alarm and cancels the
alarm automatically also if the defective hardware block passes two
consecutive tests.
174 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1340 HOTLINK FAILURE
107 1340 HOTLINK FAILURE
Meaning
Plug-in unit HOTLink cable or transmission fault detected.
Supplementary information fields
1 type of the plug-in unit causing the alarm
FFFF means that the plug-in unit type cannot be given
2 index of the plug-in unit causing the alarm
FFFF means that the plug-in unit index cannot be given
3 index of the HOTLink interface
4 the exact error code of the HOTLink test. Possible reasons are:
0040 HOTLink sfp module unplugged
0080 HOTLink fault
0100 HOTLink CRC transmission fault
Instructions
Change the faulty HOTLink cable indicated in the additional information
of the alarm.
The traffic is automatically changed from faulty HOTLink cable to
existing redundant HOTLink by the system.
Cancelling
No cancelling
DN9813048
Issue 18-2
175
Disturbance Printouts (1000-1999) 1347 CS PAGING COORDINATION ACTIVA-
TION/DEACTIVATION FAILED
Id:0900d805806a941a
108 1347 CS PAGING COORDINATION ACTIVA-
TION/DEACTIVATION FAILED
Meaning
Activation or deactivation of the feature paging coordination in BSC has failed.
Supplementary information fields
1 error type: The reason why activation/deactivation has failed
13028 NO SYSTEM INFORMATION ACKNOWLEDGEMENT MESSAGES RECEIVED FROM LAYER 2
14269 ILLEGAL BTS CONFIGURATION
14270 NOT ALL MANDATORY SYSTEM INFORMATION MESSAGES ARE RECEIVED BY TRX
14277 ILLEGAL INITIALIZATION VALUE FOR CCCH_CONF IN SYTEM INFORMATION MESSAGE
TYPE 3
14282 ILLEGAL INITIALIZATION VALUE FOR DRX_TIMER_MAX FIELD IN SYSTEM
INFORMATION TYPE 13
14283 ILLEGAL INITIALIZATION VALUE FOR ACC_BURST_TYPE IN SYSTEM INFORMATION
TYPE 13
14284 THE VALUE OF BS_AG_BLKS_RES CANNOT BE CHANGED
14285 THE VALUE OF BS_PA_MFRMS CANNOT BE CHANGED
14286 THE VALUE OF CCCH_CONF CANNOT BE CHANGED AT RUNTIME
14287 SI13_PBCCH_LOCATION CANNOT BE CHANGED IN SYSTEM INFORMATION TYPE 3 AND
4
14288 BCCH-EXT CANNOT BE CREATED
14289 BCCH-EXT CANNOT BE RELEASED
14290 THE VALUE OF DRX_TIMER_MAX CANNOT BE CHANGED
14291 THE VALUE ACC_BURST_TYPE CANNOT BE CHANGED
14396 NO SI_END_ACK/NACK MESSAGE FROM TRX
16116 OPTIONAL FEATURE OF CONNECTSITE IS NOT ALLOWED BY BTS
Instructions
The alarm informs which BCSU unit paging coordination feature
activation/deactivation has failed. Activation/deactivation of the paging
176 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1347 CS PAGING COORDINATION ACTIVA-
TION/DEACTIVATION FAILED
coordination feature should be tried again by modifying NMO parameter or the state
of the licence.
Cancelling
Do not cancel the alarm. The alarm is cancelled automatically by the system.
DN9813048
Issue 18-2
177
Disturbance Printouts (1000-1999) 1400 AFS RESTARTED
Id:0900d805806a941a
109 1400 AFS RESTARTED
Meaning
An internal restart has occurred in the AFS plug-in unit.
Supplementary information fields
1 type of AFS plug-in unit
2 index of AFS plug-in unit
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
178 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1423 NO RESPONSE FROM MAIN CLOCK
110 1423 NO RESPONSE FROM MAIN CLOCK
Meaning
No response is obtained from the active unit maintaining the main clock.
Supplementary information fields
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
179
Disturbance Printouts (1000-1999) 1425 OVERFLOW IN ALARM BUFFERING
Id:0900d805806a941a
111 1425 OVERFLOW IN ALARM BUFFERING
Meaning
The alarm system has received more alarm output tasks than it is able
to buffer for outputting or for sending to the Q3 core system. However,
the alarms that are not output or sent to the Q3 core system are
saved normally in the alarm system log file (ALHIST), from which they can
be output with an MML command. The alarm is set after all buffered alarm
output tasks have been processed and sent forward from the alarm system
after a buffer overflow.
Supplementary information fields
1 0 buffer used for buffering the alarms to be output
has overflown
1 buffer used for buffering the alarms to be formatted
for sending to the Q3 core system has overflown
2 number of alarms not output or sent to the Q3
core system
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
180 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1431 MMI SYSTEM OVERLOAD
112 1431 MMI SYSTEM OVERLOAD
Meaning
The MMI system is overloaded.
Supplementary information fields
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
181
Disturbance Printouts (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR
Id:0900d805806a941a
113 1432 DISTURBANCE IN COMMAND
CALENDAR
Meaning
A temporary disturbance has been detected in the command
calendar operation.
The command calendar interrupts the execution of the calendar
task that was being executed and blocks the task. An exception
is made with those command files that are supposed to be executed
more than once and of which execution is not interrupted although
some of the commands in the file fail (marked as NOINT in the
CFTYPE column of the execution printout of the MML command ICL):
these calendar tasks are not blocked.
The blocked tasks are not executed before the fault has been
corrected and the blocking is removed.
If the fault is permanent, then also the alarm 2430, ERROR IN
COMMAND CALENDAR, is set.
Supplementary information fields
1 error specification
MML error:
01 creation of MML session has failed
02 interruption in session
error in execution:
03 syntax error
04 semantics error
05 command has failed
06 password check error
07 loading error
08 data transmission error
09 insufficient authority
0A OMU in working state TE or SE
0B contradictory MML program running
COFFER error:
0C command not blocked
0D command not deleted
0E either command or control parameters not available
0F command not transferred to execution queue
IOMANA error:
10 opening of logical file has failed
11 connection of logical file has failed
message exchange error:
182 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1432 DISTURBANCE IN COMMAND CALENDAR
12 time-out
2 identifier of the task in the command calendar.
This identifier can be seen in the ID column of the
execution printout of the MML command ICL and points
out the command calendar task which was been executed
when the disturbance occurred
3 name of the command file been executed without the
extension .CMD
4 index of the command in command file
Instructions
You can check which calendar task execution has failed from the
MML session log/MML command log (with the MML command IGO), from
the command calendar queues (with the MML command ICL) or from
the execution printouts.
For more information, see instructions on MML commands and
command calendar.
NOTE! If the command calendar has blocked the calendar task,
the blocking must be removed in all cases mentioned below
after the fault has been corrected: otherwise the task
cannot be executed again.
You can check whether the calendar task is blocked with the
MML command ICL: the blocked commands are marked with the
identifier BLC in the QUE column of the output.
For example, ICL; outputs data of all tasks. You can remove
the blocking with the MML command ICB.
For example, ICB:11:UNBLOCK; removes the blocking from the
calendar task 11.
If the value of the supplementary information field 1 is 01,
the calendar task cannot be executed, because:
a) all MML sessions are busy. Do the following:
1. Ask a user to close his/her MML session, so that a command
calendar can start an MML session.
2. Check if the alarm 2427, MMI SYSTEM FILE ERROR, is set.
If the alarm is set, act according to its instructions.
3. If the calendar task is blocked, remove the blocking with
the MML command ICB.
b) the calendar task has been created by using a username that
DN9813048
Issue 18-2
183
Disturbance Printouts (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR
Id:0900d805806a941a
has been deleted. Do the following:
1. Remove the task from the calendar with the MML command ICD.
2. Add the same task to the calendar again with the MML command
ICI. Note that ICD does not delete the command file from the
disk, only from the calendar: you can add the same command
file to the calendar again, if it is not deleted from the
disk.
3. If the calendar task is blocked, remove the blocking with
the MML command ICB.
If the value of the supplementary information is 02, the MML
command has made a memory protection error. Check if the alarm
1078, PROCESS EXCEPTION, is set. If the alarm is set, act
according to its instructions.
If the value of the supplementary information is 03, the command
in the calendar (including the commands of the command files in
the calendar) cannot be executed, because its syntactic structure
is faulty. Correct the command with the MML command ICM so that
it conforms to the syntactic rules of the command.
If the value of the supplementary information is 04, the command
in the calendar (including the commands of the command files in
the calendar) cannot be executed, because its semantic structure
is faulty. Correct the command with the MML command ICM so that
it conforms to the semantic rules of the command.
If the value of the supplementary information is 05, do the
following:
a) If the execution printouts of the calendar tasks are directed
to the printer (you can check with the command IID::COMCAL;
where the printout are directed to):
1. Check with the MML command ISI, whether the printer is
working.
The following command outputs information about the printer
LPT-0:
ZISI::LPT,0;
2. If the printer does not work, correct the fault
(eg. add paper).
3. Remove the blocking from the command with the MML command ICB.
RECOMMENDATION: Direct the printouts also to the BBU-0, if you
want that the command calendar is working even when the printer
184 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1432 DISTURBANCE IN COMMAND CALENDAR
is not working.
Direct the printouts through the semipermanent logical file
(see the instructions given on the supplementary information
value 10 at the end of the description).
b) If the execution outputs are directed to the disk file (you can
check with the command IID::COMCAL; where the printouts are
directed to):
1. Check with the MML command ISI that the disk is not damaged.
The following command outputs information about the disk:
ZISI::WDU;
2. If the disk is damaged, change the disk.
3. If the disk is not damaged, check with the MML command IWX,
if there is space in the file for the printouts. The following
command outputs data from the file CCALENDAR, whose name ends
with LOG.
ZIWX::WS::MMDIRE:CCALENDAR,LOG;
If there is no space in the file, direct the printouts to
another file. It is recommended that the printouts are
directed to a ring file.
4. If the calendar task is blocked, remove the blocking with
the MML command ICB.
RECOMMENDATION: Direct the printouts also to the BBU-0, if you
want that the command calendar is working even when the printer
is not.
Direct the printouts through the semipermanent logical file
(see the instructions given on the supplementary information
value 10 at the end of the description).
c) If the calendar task is a command file:
1. Check with the MML command IDL that the command file is
not faulty.
If the file is faulty, an error message is output.
2. If the file is faulty , edit it with the MML command IEE.
Check eg. that the file structure is correct (the commands
are one below the another in the right order and comments
are within the comment characters).
3. If the calendar task is blocked, remove the blocking with
the MML command ICB.
DN9813048
Issue 18-2
185
Disturbance Printouts (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR
Id:0900d805806a941a
d) If the alarm 2427, MMI SYSTEM FILE ERROR, is also set, act
according to its instructions.
If the value of the supplementary information is 06, there has
been a password check error. Fill in a Problem report and send
it to your local Nokia Siemens Networks representative.
If the value of the supplementary information is 07, loading the
MML program that executes the command to memory has failed.
Do the following:
1. Check whether the alarm 2427 is set. If 2427 is set, act
according to its instructions.
2. If the calendar task has been blocked, remove the blocking
with the MML command ICB.
If the value of the supplementary information is 08, there has
been a data transmission error. Fill in a Problem report and
send it to your local Nokia Siemens Networks representative.
If the value of the supplementary information field is 09,
the calendar task cannot be executed, because:
a) the command calendar has no authority to execute the command
or because the user who has added the command into the command
calendar has no authority to execute the command.
1. If you want to execute the task from the command calendar,
you can change, with the MML command IAA, either the
command calendar authorities or the authorities of that user
who has added the task into the command calendar. You can use
the command IAA only if you have the authority to use it.
2. If the task is blocked, remove the blocking with the
MML command ICB.
b) you cannot execute the command from the command calendar.
These commands include the interactive commands, that is, those
commands that output questions which the user needs to answer
before the command can be executed.
For example, ICI is an interactive command. Those commands that
require the user only to confirm the execution of the command
(Y/N) can be executed from the command calendar.
Execute the command normally without using the command calendar.
If the value of the supplementary information is 0A, the calendar
task cannot be executed because the OMU is at state TE or SE and
an attempt has been made to execute an MML command that must not
be executed at TE and SE states. Do the following:
186 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1432 DISTURBANCE IN COMMAND CALENDAR
1. Change the state of the OMU into WO with the MML command USC.
2. If the calendar task has been blocked, remove the blocking with
the MML command ICB.
If the value of the supplementary information is 0B, the calendar
task cannot be executed because at the same time that the command
calendar is executing a specific command, another user is using
some command that must not be used at the same time with the
command in question. If, for example, another user is executing
the
command
USU,
the
command
calendar
cannot
at
the same time
execute the commands of the command group WR.
If the command task has been blocked, remove the blocking with
the MML command ICB.
If the value of the supplementary information is 0C, 0D, 0E, 0F,
act according to the instructions of the alarm 2430, ERROR IN
COMMAND CALENDAR.
If the value of the supplementary information is 10, the logical
file COMCAL needed in the execution of the calendar tasks has not
been created.
1. Check with the MML command IID, whether the logical file COMCAL
has been created:
ZIID::COMCAL;
2. If the logical file COMCAL has not been created, create it and
connect the printer that you want to it. It is recommended that
the printer LPT-0 and BBU-0 are connected to the COMCAL: in this
case, the execution printouts of the calendar tasks are output
to the printer and the BBU-0 ensures the functioning of the
command calendar even when the printer is not functioning.
Do the following:
a) Create a logical file COMCAL and connect a printer LPT-0
with the MML command IIF:
ZIIF::COMCAL,S:DEV=LPT-0
b) Connect the BBU-0 to the logical file COMCAL.
DN9813048
Issue 18-2
187
Disturbance Printouts (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR
Id:0900d805806a941a
First, create the semipermanent logical file and connect it
to BBU-0 with the MML command IIF. The following command
creates the file BYTEBASKET:
ZIIF::BYTEBASKET,S:DEV=BBU-0;
Then add the semipermanent logical file you have created as
one of the targets of the COMCAL with the MML command IIS:
ZIIS::COMCAL::LF=BYTEBASKET;
3. Find out why the logical file COMCAL has not been created.
Check whether the COMCAL is in the PLFILEG2 file. The PLFILEG2
file is in the LFILES directory. Output the contents of the file
in the following way:
a) Define the directory where you output a file from with the
MML command IWX:
ZIWY:S:UNIT=OMU:PATH=LFILES;
b) Output the contents of the file with the MML command IBT:
ZIBT:WDU,S,PLFILEG2,IMG;
If the COMCAL is not found in the PLFILEG2 file, the software
build contains the wrong version of the PLFILEG2 file. Contact
the local Nokia Siemens Networks representative.
If the COMCAL is in the PLFILEG2 file, there has been an error.
Find out the error with the help of alarms and logs.
If the value of the supplementary information is 11, the logical
file COMCAL needed in the execution of the calendar tasks is
reserved for the execution of another calendar task or some
user is changing its connections.
Wait until the other calendar task is finished or that the
connections of the COMCAL have been changed.
Cancelling
No cancelling.
188 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1548 MTP CONFUSION MESSAGE RECEIVED
114 1548 MTP CONFUSION MESSAGE
RECEIVED
Meaning
An MTP confusion message has been received in the exchange.
The signalling point indicated by the originating point
code given in the 3rd supplementary information field has not
identified the signalling network management message. The
heading code of the signalling network management message
is given in the 6th supplementary information field.
Supplementary information fields
1 SIO in MTP confusion message
2 destination point code in MTP CONFUSION message
3 originating point code in MTP CONFUSION message
4 heading code of MTP CONFUSION message
5 implementation level indicator in MTP CONFUSION message
6 confusion_msg_id in MTP CONFUSION message, i.e. a heading
code that was not identified
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
189
Disturbance Printouts (1000-1999) 1557 EVENT HANDLER CANNOT WORK PROPER-
LY DUE TO FILE SERVICE FAILURE
Id:0900d805806a941a
115 1557 EVENT HANDLER CANNOT WORK
PROPERLY DUE TO FILE SERVICE FAILURE
Meaning
Event handler cannot save its own attributes in the disk file or
the file services for saving and reading the events have failed.
If the file services are not functioning, they prevent or disturb
the functioning of the event handler.
Supplementary information fields
1 error code
You can check its meaning in General Error Messages of System
2 disk file identifier
Disk file where attributes cannot be saved.
Value zero indicates that the file services for saving and
reading the events have failed
3 family identifier
Family which fails to provide the requested file service
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
190 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1569 CRITICAL LIMIT IN SECURITY REPORTING
REACHED
116 1569 CRITICAL LIMIT IN SECURITY REPORT-
ING REACHED
Meaning
The critical limit of a security reporting counter has been reached.
Supplementary information fields
1 the security reporting counter that has reached its critical limit:
02 - counter for unauthorised users of service terminal
04 - counter for unauthorised users of the network
05 - counter for use of network: unauthorised commands
07 - counter for unauthorised MML users
08 - counter for unauthorised MML commands
10 - counter for unsuccessful saves in MML log file
11 - counter for unsuccessful MML command checks
12 - counter for unsuccessful subscriber identifications
13 - counter for unidentified IMSI numbers
14 - counter for IMEI IDs on black list
15 - counter for unidentified IMEI IDs
Instructions
Use the MML command IRO:<report type> to output a detailed security
report. Check, against the report, if anything out of the ordinary
has occurred, and modify, if necessary, the limit value of the counter
in question so that it reflects more accurately what is considered a
normal situation. However, if the counter's value was normal, find out
why the critical limit was exceeded.
Cancelling
No cancelling.
DN9813048
Issue 18-2
191
Disturbance Printouts (1000-1999) 1570 SECURITY LOG ALARM LIMIT REACHED
Id:0900d805806a941a
117 1570 SECURITY LOG ALARM LIMIT
REACHED
Meaning
The number of events written in the Security Reporting Transaction Data
File (LETTER) during a monitoring period has reached the preset alarm
limit.
Supplementary information fields
1 alarm limit of LETTER as a percentage
2 length of monitoring period in days
3 starting date of monitoring period
4 number of records in LETTER
Instructions
A certain number (indicated by the alarm limit and given as a
percentage of all records) of events have been entered in the file
during a monitoring period. A back-up copy of the file should be made,
otherwise data will be lost as new records are written over old ones.
Cancelling
No cancelling.
192 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1578 CONFUSION IN BSSMAP SIGNALING
118 1578 CONFUSION IN BSSMAP SIGNALING
Meaning
This alarm is issued if a faulty message or a CONFUSION message is
received from the partner exchange.
Supplementary information fields
1 layer 3 BSSMAP message type
The message type values can be found in 3GPP 48.008,
chapter 3.2.2.1 Message Type
2 typical causes of refusing the message:
51H = invalid message contents
52H = information element or field missing
53H = incorrect value
54H = unknown message type
55H = unknown information element
60H = protocol error between the BSC and the MSC
If the direction is 0, that is, if the partner exchange
has sent the CONFUSION message, the cause for the refusal
can be any of the Cause values defined in 3GPP 48.008
(chapter 3.2.2.5)
3 direction of the message that caused the alarm
0 = self-sent message (the partner exchange has sent the
CONFUSION message)
1 = message sent by the partner exchange
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
193
Disturbance Printouts (1000-1999) 1580 GLOBAL RESET FAILURE
Id:0900d805806a941a
119 1580 GLOBAL RESET FAILURE
Meaning
The BSC cannot send an acknowledgment to the Global reset
message. The BSC does not transmit traffic.
Supplementary information fields
1 signalling point code of the MSC
2 program family found to be faulty.
FFFF : program family unknown
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery for
the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
194 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1582 CONNECTION OR RELEASE ERROR
120 1582 CONNECTION OR RELEASE ERROR
Meaning
The establishment or release of the connection has failed.
The call fails or a connection may be left in the marker.
Supplementary information fields
1 number of the A interface PCM circuit
This is a PCMCON record index
2 time slot of the A interface PCM circuit
3 number of the external PCM circuit
In combined BSC3i/TCSM3i
ET_PCM means Ater PCM between GSW2KB and TR3E/A
4 number of the transcoder PCM circuit
5 time slot of the transcoder PCM circuit
6 number of Abis interface PCM circuit
This is a PCMCON record index
7 time slot of Abis interface PCM circuit
8 number of external PCM circuit
9 time slot of the external PCM circuit
10 sub-time slot of the external PCM circuit
11 error code
61 : unkown message identification
62 : unused PCM
63 : unused circuit
6A : test word test error
6B : test word swtst status error
6D : connection status error
6E : connection parity error
6F : connection read error
70 : HWILIB function call fails
(virtual circuit conversions)
71 : data from HWILIB is erroneous
(virtual circuit conversions)
12 failed connection or release
02 : connection failed
DN9813048
Issue 18-2
195
Disturbance Printouts (1000-1999) 1582 CONNECTION OR RELEASE ERROR
Id:0900d805806a941a
05 : release failed
03 : marker does not answer to the connection or
release message
Instructions
Check in the alarm history if there are several alarms concerning
a certain A interface or Abis interface circuits. Solve the possible
configuration problems on these circuits. You can interrogate the circuit
group information with the MML command RCI.
The alarm supports the activation of the automatic recovery for
the object unit. You can check the supporting amount of the alarm with
the MML command ARO.
Check if there are other alarms related to this alarm. Follow the
instructions given for them.
Cancelling
Do not cancel the alarm. The system cancels the alarm
automatically when the fault has been corrected.
196 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1583 LAPD MSG DISTRIBUTION PROBLEM
121 1583 LAPD MSG DISTRIBUTION PROBLEM
Meaning
The PXRECE (Primary Rate Access Receiving Program Block) has
received messages from the D-channel, but it has not been able
to route the messages forward. The reason for this can be that
the message received from the LAPD link is erroneous. The error
situation is not a serious one, but if there are several consecutive
alarms with the same D-channel system identifier, there may be an
error in the PXRECE distribution table or a disturbance in the
LAPD link.
Supplementary information fields
1 identification of the D-channel system
(hexadecimal number)
2 identification of the D-channel system
(name)
Instructions
Use the MML command AHP to check other alarms concerning the same
unit for a period of approximately one hour before this alarm
occurred. If the other alarms do not indicate a link fault and
if there are BCF/TRX links created under the link identification
mentioned in this alarm, the fault is in the PXRECE distribution
table. To correct the situation, you can perform a switchover in
the unit that set the alarm by using the MML command USC.
The switchover updates the PXRECE distribution table.
Cancelling
No cancelling.
DN9813048
Issue 18-2
197
Disturbance Printouts (1000-1999) 1585 ABNORMAL A INTERFACE CIRCUIT RELEASE
Id:0900d805806a941a
122 1585 ABNORMAL A INTERFACE CIRCUIT
RELEASE
Meaning
The GSM speech circuit of the A interface is released in an abnormal
manner, which causes the call to be cleared from the speech
circuit in question.
Supplementary information fields
1 number of the PCM circuit
this is:
- number of the external PCM circuit, if GSW and
unsubmultiplexed A interface are used
- number of the SMUX PCM, if GSW and submultiplexed
A interface are used
- PCMCON record index, if GSWB is used
2 time slot of the PCM circuit in question
3 circuit Identification Code (CIC)
4 PCM circuit part of Circuit Identification Code.
This is 65535d , if the environment is T1 (ANSI 1.544 Mbit/s)
5 time slot part of Circuit Identification Code.
This is 255d, if the environment is T1 (ANSI 1.544 Mbit/s)
6 number of the external PCM circuit.
This is 65535d, if GSW is used in TCSM3i for
combined BSC3i/TCSM3i installation
ET_PCM means Ater PCM between GSW2KB
and TR3E/A
7 time slot of the external PCM circuit.
This is 255d, if GSW is used
8 sub-time slot of the external PCM circuit.
This is 255d, if GSW is used
9 number of the transcoder PCM circuit.
This is 0xFF, if GSW is used
10 time slot of the transcoder PCM circuit.
This is 255d, if GSW is used
11 cause of abnormal release:
198 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1585 ABNORMAL A INTERFACE CIRCUIT RELEASE
1 = abnormal release of SCCP connection
2 = "Reset circuit" message to a circuit in speech state
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
199
Disturbance Printouts (1000-1999) 1590 ALARM SYSTEM MESSAGE SENDING BUF-
FER FULL
Id:0900d805806a941a
123 1590 ALARM SYSTEM MESSAGE SENDING
BUFFER FULL
Meaning
A buffer that is used to supervise the alarm system's message
traffic requiring acknowledgements is full. Such buffers are
used for the collection of history data of both the alarm system's
distributed and centralised part, as well as for communication
between the distributed and centralised parts.
The saturation of the buffer that collects history data may
cause the loss of some such data.
The saturation of the buffer that is used for communication
between the two parts (distributed and centralised) may cause
an imbalance between the centralised part of the alarm system
and the distributed part that is sending. This may lead to the
loss of some of the set values and cancellations of the alarms.
Supplementary information fields
1 type of buffer
01 communication buffer
02 history buffer
2 family identifier of the sender
3 process identifier of the sender
4 type of the receiver's computer unit
See Recovery and Unit Working State Administration.
5 index of the receiver's computer unit
6 family identifier of the receiver
7 process identifier of the receiver
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
200 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1597 I/O DEVICE FOUND FAULTY BY ALARM SYS-
TEM
124 1597 I/O DEVICE FOUND FAULTY BY ALARM
SYSTEM
Meaning
The alarm system has found, having received several
different observations to that effect, that the I/O
device is defective.
The I/O system has been informed of the fault in the device.
Supplementary information fields
1 type of subobject (of the I/O device) suspected faulty
FFFF, subobject not specified
2 index of subobject (of the I/O device) suspected faulty
FFFF, subobject not specified
3-8 the alarm manual numbers (in BCD format) of the observations
that first supported the fault hypothesis
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
201
Disturbance Printouts (1000-1999) 1598 UNIT FOUND FAULTY BY ALARM SYSTEM
Id:0900d805806a941a
125 1598 UNIT FOUND FAULTY BY ALARM
SYSTEM
Meaning
The alarm system has found, having received several different
observations to that effect, that a functional unit
(not the I/O device) is defective.
The recovery system has been informed of the faulty unit.
Supplementary information fields
1 type of subobject (of a functional unit) suspected faulty
FFFF, subobject not specified
2 index of subobject (of a functional unit) suspected faulty
FFFF, subobject not specified
3-8 the alarm manual numbers (in BCD format) of the
observations that first supported the fault hypothesis
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
202 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1623 ERROR DURING SUPERVISION
126 1623 ERROR DURING SUPERVISION
Meaning
Unit type supervision has been interrupted because the Subscriber
Module Testing Program Block (SBTSTP) or the Time Slot Based Unit Test
Program Block (TSUPRO) is constantly reserved, or the Message Transfer
and Switching Service Program Block (MTSWIS) cannot seize the unit
to be tested, or the Test Line Management Program Block (LTMANA) is
unable to reserve the SUB-E minimeter. The supervision of the unit is
interrupted because the requested task is incorrect, or because no test
result is obtained for the requested test.
Supplementary information fields
1 program block:
0060 LTMANA_P
0064 TSUPRO_P
0065 SBTSTP_P
0067 MTSWIS_P
2 error specification:
01 unit type supervision is interrupted
02 supervision of single unit is interrupted
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
203
Disturbance Printouts (1000-1999) 1630 RAM FAILURE IN SYNCHRONIZATION UNIT
Id:0900d805806a941a
127 1630 RAM FAILURE IN SYNCHRONIZATION
UNIT
Meaning
A failure has been detected in the RAM memory of the synchronization
unit.
Supplementary information fields
Instructions
Set the unit into test state. Run the diagnostics and replace
the plug-in unit if necessary.
Cancelling
No cancelling.
204 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1660 UPDATE NUMBER MISMATCH
128 1660 UPDATE NUMBER MISMATCH
Meaning
The LOGSAV, a hand of the database management system, has sent
the DBSMAN an update, the number of which (update_seq_number) is
inconsistent with the DBSMAN's view of what that number should be.
One or the other of the processes has failed and may have lost log
buffers. The DBSMAN will now no longer receive log buffers from the
database in question, and the database will be dumped, i.e. it is
copied from RAM to the disk, thus correcting the failure automatically.
Supplementary information fields
1 database index (some database applications still need this
information, although nowadays the database is usually
identified based on the values of the following two
supplementary information fields, i.e. database name and
database occurrence)
2 database name
3 number of database occurence
4 database location
5 family ID of the program block handling the database
Instructions
The system corrects the fault automatically. If the disturbance keeps
recurring, save the log files of the database unit and the disk
updating system unit and the alarms, and contact your local Nokia
Siemens Networks representative.
Cancelling
No cancelling.
DN9813048
Issue 18-2
205
Disturbance Printouts (1000-1999) 1661 DATABASE MANAGER IN FATAL ERROR
STATE
Id:0900d805806a941a
129 1661 DATABASE MANAGER IN FATAL
ERROR STATE
Meaning
An error occurred in the database management system, and the
system has been set to the "fatal error" state. In the "fatal
error" state, the management system program block acknowledges
supervision messages negatively. As the program block is a critical
one, the system resets the database unit.
Supplementary information fields
1 database index (some database applications still need this
information, although nowadays the database is usually
identified based on the values of the following two
supplementary information fields, i.e. database name and
database occurrence)
2 database name
3 number of database occurrence
4 error code indicating the reason why the fatal error
state was entered. You can check its meaning in General Error
Messages of System
Instructions
Save the log of the database unit, or, alternatively, save the black
box of the unit after the reset for further investigation.
Cancelling
No cancelling.
206 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1662 DATABASE LOADING ERROR
130 1662 DATABASE LOADING ERROR
Meaning
Loading of the database fails. If several load attempts fail,
the management system is set to "fatal error" state. Because
of this, the system resets the database unit.
Supplementary information fields
1 database index (some database applications still need
this information, although the database is usually
identified based on the database name and
database occurrence)
2 database name
3 number of database occurrence
4 reason for load failure
01 the disk updating system (DBSMAN program block) does
not answer when the DBMANA on the WO side asks for
permission to load
02 the DBMANA on the WO side does not answer when the
DBMANA on the SP side asks for permission to load
03 time supervision expires on the WO side of the database
unit during the first load attempt
04 time supervision expires on the SP side of the database
unit during the first load attempt
Instructions
Reason = 01: Check with the DBD command the state of the disk
updating system serving the database.
Reason = 02: Check with the DBS command the state of the
management system in the database unit's WO side.
Reason = 03: Check with the DBD command the state of the disk
updating system serving the database. Check with the DBS command
the state of the management system on the database unit's WO side.
Save the log of the database unit's WO side, or,
alternatively, save the unit's black box after a reset. Save
the log of the disk update system.
Reason = 04: Check with the DBS command the state of the
management system on the database unit's WO and SP side.
Save the log of the database unit's SP side, or, alternatively,
save the unit's black box after the reset. Save the log of the
DN9813048
Issue 18-2
207
Disturbance Printouts (1000-1999) 1662 DATABASE LOADING ERROR
Id:0900d805806a941a
database unit's WO side.
Cancelling
No cancelling.
208 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1663 HAND RESERVATION ERROR IN DATABASE
MANAGER
131 1663 HAND RESERVATION ERROR IN
DATABASE MANAGER
Meaning
The reservation of a transaction or fastread hand fails in
the database management system.
Supplementary information fields
1 database index (some database applications still need this
information, although nowadays the database is usually
identified based on the values of the following two
supplementary information fields, i.e. database name and
database occurrence)
2 database name
3 number of database occurrence
4 error code indicating why the hand reservation failed.
You can check its meaning in General Error Messages of
System
5 number of the transaction or fastread hand to be reserved:
00 if on WO side
> 03 if on SP side (the number of the hand to be reserved
is known)
Instructions
Check the states of the database management system's hands by means of
the service terminal extension Family Utilities (FAMUTI).
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
209
Disturbance Printouts (1000-1999) 1682 SCDFLE UPDATE FAILURE
Id:0900d805806a941a
132 1682 SCDFLE UPDATE FAILURE
Meaning
The distribution or updating of the Working State and Configuration
File (SCDFLE) has failed.
Supplementary information fields
1 error code presented as a common error code. You can check its
meaning with a command of the service terminal extension MRS or in
the General Error Messages of System
2 consecutive number of distribution
3 recovery action
4 type of the unit whose data was changed
5 index of the unit whose data was changed
6 number of SCDFLE record
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
210 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1683 FAULTY UNIT SP-EX
133 1683 FAULTY UNIT SP-EX
Meaning
A faulty unit is spare.
Supplementary information fields
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
211
Disturbance Printouts (1000-1999) 1684 SPARE UNIT WARMUP FAILURE
Id:0900d805806a941a
134 1684 SPARE UNIT WARMUP FAILURE
Meaning
The warm-up of the spare unit fails. The reason may be a fault
in the active or in the passive unit. The alarm is issued from
both units.
Supplementary information fields
1 family identifier of the alarm detector
2 error code returned by the alarm detector.
You can check its meaning with a command of the
service terminal extension MRS or in General Error
Messages of System
3 message bus address of the unit where the error occurred
4 family identifier of the program block that made the error
5 load group where the warming failed
6 file where the warming failed
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the
alarm with the MML command ARO.
Cancelling
No cancelling.
212 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1685 UNIT RESTART FAILURE
135 1685 UNIT RESTART FAILURE
Meaning
The restarting of the computer unit fails.
Supplementary information fields
1 family identifier of the error detector
2 error code returned by the error detector.
You can check its meaning with a commands of the service terminal
extension MRS or in General Error Messages of System
3 message bus address of the unit where the error occurred
4 family identifier of the program block that made the error
5 load group where the loading failed
6 file where the loading failed
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
213
Disturbance Printouts (1000-1999) 1687 RECOVERY ACTION FAILURE
Id:0900d805806a941a
136 1687 RECOVERY ACTION FAILURE
Meaning
The recovery actions in the unit have been interrupted or a subfunction
of a recovery action has failed. The partner program block in the
object unit has not responded, or it has returned an error status.
Supplementary information fields
1 error code of recovery action.
You can check its meaning with a command of the service terminal
extension MRS or in General Error Messages of System
2 interrupted recovery action
3 family identifier of the error detector
4 error code returned by the error detector.
You can check its meaning with a command of the service terminal
extension MRS or in General Error Messages of System
5 message bus address of the unit where the error occurred
6 family identifier of the program block that made the error
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
214 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1688 FAILURE IN CALL CLEARING
137 1688 FAILURE IN CALL CLEARING
Meaning
A clear request sent to release the calls of the time-slot-based
unit such as the SUB, CNFC, ET, etc. has not been acknowledged.
Supplementary information fields
1 type of time-slot-based unit
See Recovery and Unit Working State Administration.
2 unit index
3 partner program block
Instructions
Check if the above-mentioned units have made seizures for calls.
If so, release them.
Cancelling
No cancelling.
DN9813048
Issue 18-2
215
Disturbance Printouts (1000-1999) 1800 SCSI ADDRESS ILLEGAL
Id:0900d805806a941a
138 1800 SCSI ADDRESS ILLEGAL
Meaning
There was an attempt to install an I/O device at an SCSI address
that was already reserved.
Supplementary information fields
1 number of SCSI bus
0...1
2 address of device on bus identified in field 1
0...7
3 logical unit number (= LUN)
0...7
the LUN of the master tape drive is always 0, numbers 1...7 are
slave tape drivers
Instructions
Check the SCSI bus addresses of the I/O devices on the SCSI bus.
If the alarm occurs in connection with the configuration of the tape
units, check the parameters of the ISK command.
Cancelling
No cancelling.
216 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1801 MASS MEMORY FILE BACKUP FAILURE
139 1801 MASS MEMORY FILE BACKUP
FAILURE
Meaning
A copy task has failed. The I/O system has used backgroung processing
to carry out the task but copying some of the files failed.
If alarm 1802, BACKUP COPY LOG FAILURE, is set simultaneously with
this alarm, the system has failed to save all the information on the
copy task to the copy log. The copy task execution has been interrupted.
This alarm has no effect on the operation of the rest of the system.
Supplementary information fields
1 name identification of the failed copy task.
The name is an ASCII string
2 number identification of the failed copy task.
The number is a hexadecimal number generated by the I/O system.
The name and the number of the task form an explicit identifier
Instructions
Check the backup copy log to see which copy task failed. Use
the MML commands IPI and IPP to interrogate the log of the copy
task in question. Give the copy task name and identification number
(shown in Supplementary information fields 1 and 2) as parameters.
For example, if the name of the task is COPY_1998 and the
identification number is 40020010, the following command outputs
the general copy task information:
IPI:NAME=COPY_1998,HANDLE=40020010;
The IPP command displays detailed information on the copied files
and directories. If copying a file failed, the printout shows a
general error message after the file or directory in question.
IPP:NAME=COPY_1998,HANDLE=40020010;
Cancelling
No cancelling.
DN9813048
Issue 18-2
217
Disturbance Printouts (1000-1999) 1802 BACKUP COPY LOG FAILURE
Id:0900d805806a941a
140 1802 BACKUP COPY LOG FAILURE
Meaning
Saving the copy task information in the disk's copy log has failed
at least partly.
The fault may have been caused, for example, by a disturbance in the
I/O system, a fault in an I/O device, or a load peak of the unit,
because of which information could not be recorded within the
defined time period.
If alarm 1801, MASS MEMORY FILE BACKUP FAILURE, is set simultaneously
with this alarm, the background processing of the backup copy task
has been interrupted. Otherwise, the copy task itself has succeeded
but the system was not able to record all the information connected
to the copy task to the copy log.
This alarm has no effect on the operation of the rest of the system.
If disk alarms are set simultaneously with this alarm, a disturbance
or a fault has been detected in the disk system and it has prevented
the normal use of the copy log. The following alarms are disk alarms:
0860 DISK NOTICE, 1860 DISK DISTURBANCE, 2860 DISK FAILURE,
2861 NO ACCESS TO DISK, and 2862 DISK CHECKSUM ERROR.
Supplementary information fields
1 general error message of the system. You can check its meaning
in General Error Messages of System
2 name identifier of the copy task whose recording in the copy log
failed. The name is an ASCII string
Instructions
It may be possible to interrogate information on the copy task
mentioned in Supplementary information field 2 with the MML commands
IPI and IPP. The I/O system has however failed to record some (or
possibly all) information.
You may find more information in the system log, which you can
interrogate with the service terminal command ZGD.
If alarm 1801, MASS MEMORY FILE BACKUP FAILURE, is not set
simultaneously with this alarm for the same copy task, the copy
task was successful, even though information on it is not available
in the log.
If alarm 1801 is also set, you should start the copy task again.
218 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1802 BACKUP COPY LOG FAILURE
Cancelling
No cancelling.
DN9813048
Issue 18-2
219
Disturbance Printouts (1000-1999) 1804 IP ROUTING RESOURCE SHORTAGE
Id:0900d805806a941a
141 1804 IP ROUTING RESOURCE SHORTAGE
Meaning
The IP Routing feature is experiencing an unexpected resource
shortage.
The IP routing capability of the system is temporarily reduced
until the routing database has been reconstructed from neighboring
routers.
The telephony capabilities of the switch are not affected.
Supplementary information fields
Instructions
Fill in a Problem Report and send it to your local technical
support.
Cancelling
No cancelling.
220 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1806 PRINTER SPOOLER DISABLED
142 1806 PRINTER SPOOLER DISABLED
Meaning
Printing system cannot use the spooler. This happens, for example,
when the SCSI-bus or hard disks go to TEST-state. The failure does
not disable the printing system, but new printing tasks are handled
in non-spoolered mode. Handling printing tasks in non-spoolered mode is
more unreliable than in spoolered mode.
The tasks that are in spooler when failure occurs, are executed
when the spooler is in use again. The system changes automatically from
the non-spoolered mode to the spoolered mode when the spooler is
again in use and all non-spoolered tasks are completed.
Supplementary information fields
Instructions
To find out the reason for SCSI-bus's or hard disk's wrong operating
state, check whether there are other alarms active using the AHO MML
command. Follow the instructions given in these alarm descriptions.
Set the SCSI-bus and hard disks to WO-state using the ISC MML command, if
possible.
Cancelling
No cancelling.
DN9813048
Issue 18-2
221
Disturbance Printouts (1000-1999) 1809 IP CONFIGURATION INQUIRY SERVICE
FAILED
Id:0900d805806a941a
143 1809 IP CONFIGURATION INQUIRY SERVICE
FAILED
Meaning
The alarm is set if IP management shared library (YANLIB) cannot
provide IP configuration inquiry services for applications.
Under this situation, the applications will get "no service" return
code when calling the library routines. If the application has failed
to receive IP configuration data, it might make the Network Element
unable to provide IP calls services.
Supplementary information fields
Instructions
Check the computer log to find out the possible cause of the alarm.
Fill in a Problem Report and send it to your local Nokia Siemens
Networks representative.
Here are the possible problems:
1. IP configuration files are missing or corrupted.
IPv4 configuration is stored to the /etc/if.dat file of RAM disk
of POSIX subsystem and the same information is stored to the
/LFILES/POCIFCZZ.IMG file on the hard disk of OMU unit.
IPv6 configuration is stored to the /LFILES/YEMIP6GX.XML file.
VLAN configuration is stored to the /LFILES/VLNRRRGX.XML file.
Get configuration files from the W0 disk and attach
them to the problem report and if those files do not
exist, report that in the problem report.
2. Read/write disk files failed:
Add both operating and user logs to the problem report.
3. Allocate common buffer failed:
Add both operating and user logs to the problem report.
4. Event Forwarder problem:
Add user logs to the problem report.
5. Name Server problem:
Add user logs to the problem report.
222 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1809 IP CONFIGURATION INQUIRY SERVICE
FAILED
Cancelling
No cancelling.
DN9813048
Issue 18-2
223
Disturbance Printouts (1000-1999) 1850 BTS TEST REPORT PRINTOUT FAILED
Id:0900d805806a941a
144 1850 BTS TEST REPORT PRINTOUT FAILED
Meaning
Printing the BTS test report has failed in the reporting
system of the BSC.
Supplementary information fields
1 BCF identifier
2 BTS identifier
3 TRX identifier
4 type of main test
0 = single TRX test with MML
1 = single RAX test with MML
2 = single STM test with MML
3 = single TRX test via Q3 interface
4 = single RAX test via Q3 interface
5 = single STM test via Q3 interface
6 = scheduled TRX test with MML
7 = scheduled STM test with MML
8 = scheduled TRX test via Q3 interface
9 = scheduled STM test via Q3 interface
5 type of STM test
1 = BCCH measurement
2 = originating test call
3 = BCCH carrier wave setting
4 = call information request
5 = transceiver sensitivity measurement
6 = STM test cancellation request
7 = TRX test
8 = TRX loop test
9 = antenna test
0A = antenna loop test
0B = TRX test for MetroSite and UltraSite BTSs
0C = Abis loop test
0xff = not stm test
6 reason for failure (DX error code)
224 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1850 BTS TEST REPORT PRINTOUT FAILED
DX error code: see General Error Messages of System
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
225
Disturbance Printouts (1000-1999) 1860 DISK DISTURBANCE
Id:0900d805806a941a
145 1860 DISK DISTURBANCE
Meaning
A disturbance has been detected in the Winchester or floppy disk
system. The disturbance may be caused by a DMADI, DMASI, or SCSIF
plug-in unit, the connecting cable, disk controller, disk drive,
or by a command that is incorrect, insufficient or unnecessary.
Supplementary information fields
1 general error message of the system. You can check its
meaning in General Error Messages of System
2 address of the damaged sector of the disk drive,
if 1FFFFFH, the sector address is not valid
3 first 8 characters of file name
Instructions
Check the command. Remove write protection from the floppy disk.
Check and replace, if needed, the DMADI, DMASI, or SCSIF plug-in
units, connecting cable, disk controller and disk drive or floppy
disk.
Cancelling
No cancelling.
226 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1881 TAPI FAILURE
146 1881 TAPI FAILURE
Meaning
Before giving a command concerning the magnetic tape drive,
or when making a state inquiry, TAPEDR checks the functioning
of the TAPI plug-in unit. If an error is detected, this alarm
is issued.
Supplementary information fields
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
227
Disturbance Printouts (1000-1999) 1882 DMADI FAILURE
Id:0900d805806a941a
147 1882 DMADI FAILURE
Meaning
Before read or write operations TAPEDR checks the functioning of
the address and byte counters of the DMA channel it uses. If a
failure is detected in the operation, this alarm is issued.
Supplementary information fields
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
228 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1884 LABEL PARAMETER FAILURE
148 1884 LABEL PARAMETER FAILURE
Meaning
If no label parameters have been defined for TAPEDR in connection
with the preformatting or opening command, TAPEDR tries to use the
old parameters stored in the data area. This always entails a
correctness test based on the check sum. If an error is detected,
TAPEDR fetches the constant values and uses them. At the same time,
the system issues this alarm.
Supplementary information fields
1 number of the magnetic tape unit
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
229
Disturbance Printouts (1000-1999) 1885 ERROR IN WRITING DATA TO MAGNETIC
TAPE
Id:0900d805806a941a
149 1885 ERROR IN WRITING DATA TO
MAGNETIC TAPE
Meaning
The error message is a consequence of a failure in the magnetic tape
unit, very poor condition of the tape, a serious malfunction in
the controlling plug-in units (TAPI, DMADI, SCSIF), or erroneous
task parameters sent by the application.
Supplementary information fields
1 number of the magnetic tape unit
2 general error message of the system. You can check its meaning
in General Error Messages of System
3 block number
Instructions
Determine (from the error code) whether the cause of the disturbance
is poor tape quality, equipment failure or an erroneous task parameter.
The alarm supports the activation of the automatic recovery for the
object unit. You can check the supporting amount of the alarm with
the MML command ARO.
If the magnetic tape unit has been changed into test state for recovery,
find out the cause of the failure and remove the cause before returning
the magnetic tape unit into normal working state (WO-BU). The state can
be changed with the MML command ISC.
Cancelling
No cancelling.
230 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1886 ERROR IN TAPE OPERATION
150 1886 ERROR IN TAPE OPERATION
Meaning
This is an error acknowledgement to some other command than the
write command. The fault is in the equipment or in the storage medium.
Supplementary information fields
1 number of the magnetic tape unit
2 general error code. You can check its meaning in General Error
Messages of System
Instructions
If the error code does not clearly indicate that the fault is
in the equipment, change the storage medium. If this does not
solve the problem, an inspection of the equipment is required.
Cancelling
No cancelling.
DN9813048
Issue 18-2
231
Disturbance Printouts (1000-1999) 1887 BLOCK COUNTER FAILURE
Id:0900d805806a941a
151 1887 BLOCK COUNTER FAILURE
Meaning
TAPEDR contains a duplicated block number counter for each of the
magnetic tape units. The contents of one counter are continuously
behind the other. If the test indicates that the relationship
between the two contents has changed, the block numbering is
started from the beginning, and the system issues this alarm.
Supplementary information fields
1 number of the magnetic tape unit
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
232 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1891 AS7 RESTARTED
152 1891 AS7 RESTARTED
Meaning
The processor of the AS7 plug-in unit has restarted.
Supplementary information fields
1 number of AS7 (0..n)
2 state data of AS7:
00 out of service
01 working
02 testing
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
233
Disturbance Printouts (1000-1999) 1893 O&M CHANNEL SEND OVERLOAD
Id:0900d805806a941a
153 1893 O&M CHANNEL SEND OVERLOAD
Meaning
The send buffer of the data transmission connection of the operation
and maintenance network is full, or the X.25 network layer has not
granted permission to transmit.
Supplementary information fields
1 number of OMI channel (0...n)
2 number of AS7 or AC25 plug-in unit (0...n)
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
234 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1894 NO RESPONSE TO AS7 SUPERVISION MES-
SAGE
154 1894 NO RESPONSE TO AS7 SUPERVISION
MESSAGE
Meaning
The program controlling the AS7 plug-in unit has not responded to the
supervision message within the specified time.
Supplementary information fields
1 number of the AS7 (0...n)
2 state data of the AS7:
00 out of service
01 working
02 testing
FF supervision software does not know the state of the AS7
Instructions
The alarm requires no actions.
The alarm supports the activation of the automatic recovery
for the object unit. You can check the supporting amount of the alarm
with the MML command ARO.
Cancelling
No cancelling.
DN9813048
Issue 18-2
235
Disturbance Printouts (1000-1999) 1895 DISTURBANCE IN O&M CHANNEL
Id:0900d805806a941a
155 1895 DISTURBANCE IN O&M CHANNEL
Meaning
A disturbance has been detected on the data transmission connection
of the operation and maintenance network.
Supplementary information fields
1 number of OMI channel (0...n)
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
236 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1900 DEGRADED SLIP FREQUENCY
156 1900 DEGRADED SLIP FREQUENCY
Meaning
The ET has observed that the clock frequency slips on the incoming E1
or T1 circuit exceed the alarm limit defined for the ET. The slips are
monitored for a 24-hour period.
Supplementary information fields
1 unit type
2 E1 or T1 circuit number if the unit type is ET
TCSM's internal PCM circuit number (0d..7d) if the unit type is TCSM
and the transcoder type is TCSM2
E1 or T1 circuit number on the A interface (0d..15d) or on the Ater
interface (16d..31d) if the unit type is TCSM and the transcoder type
is TCSM3i
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
DN9813048
Issue 18-2
237
Disturbance Printouts (1000-1999) 1901 ET RESTARTED
Id:0900d805806a941a
157 1901 ET RESTARTED
Meaning
An internal restart has taken place on an exchange terminal.
Supplementary information fields
1 unit type
2 index of the internal PCM circuit of TCSM, 0..7d
3 number of ET restarts
Instructions
The alarm requires no actions.
Cancelling
No cancelling.
238 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1910 COMMUNICATION FAILURE WITH TRX
158 1910 COMMUNICATION FAILURE WITH TRX
Meaning
Time supervision has elapsed, or the TRX has sent a negative
acknowledgement to the BSC, which has interrupted the ongoing message
exchange scenario.
Supplementary information fields
1 ID number of the BTS site
2 ID number of the base transceiver station
3 ID number of the transceiver
4 general error message of the system. You can check its meaning
with a command of the service terminal extension MRS or in
General Error Messages of System.
Instructions
Correct the possible transmission error in the Abis interface, or
correct the error already indicated by an alarm generated in the TRX.
Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when
the fault has been corrected.
DN9813048
Issue 18-2
239
Disturbance Printouts (1000-1999) 1911 INVALID URGENCY LEVEL IN TRANSMISSION
ALARM
Id:0900d805806a941a
159 1911 INVALID URGENCY LEVEL IN TRANS-
MISSION ALARM
Meaning
Transmission equipment has set an alarm with a different urgency level
than the one defined in the BSC alarm system. There is an erroneous alarm
urgency level definition either in the transmission equipment or in
the BSC, or there is disturbance in the Q1 service channel.
This alarm may affect the performance of the BSC transmission equipment
fault management.
Supplementary information fields
1 Q1 address of the piece of transmission equipment
2 the functional entity number specifies a physical unit of the
transmission equipment, for example a plug-in unit or a
daughter board. The number can be 0...254
3 the supervision block number specifies the faulty part of the
functional entity, for example a certain line interface or
component
4 number of the Q1 service channel in the BSC, 0...27
5 name of the piece of transmission equipment.
Not included if the name is in the alarm object field of
the alarm printout.
See Alarm Structure, Alarm Reference Manual
6 number of the piece of transmission equipment.
Not included if the index is in the alarm object field of
the alarm printout.
See Alarm Structure, Alarm Reference Manual
7 original Q1 fault code received from transmission device
Instructions
Use the MML commands Axx for alarm administration.
To clarify the reason for the fault, see the transmission equipment
operating manual to check how fault code is classified in the equipment.
If the fault code classification in the equipment is the same as in
the BSC alarm system, there is probably some kind of disturbance in
the Q1 service channel. Otherwise contact your local Nokia Siemens
Networks representative.
240 DN9813048
Issue 18-2
Disturbance Printouts (1000-1999)
Id:0900d805806a941a
1911 INVALID URGENCY LEVEL IN TRANSMISSION
ALARM
Cancelling
No cancelling.
DN9813048
Issue 18-2
241
Disturbance Printouts (1000-1999) 1915 TCSM CLOCK DISTURBANCE
Id:0900d805806a941a
160 1915 TCSM CLOCK DISTURBANCE
Meaning
One of the external synchronisation plug-in units of a TCSM3i cabinet
has detected a fault and has set an alarm to the supervising transcoder
unit.
Supplementary information fields
1 index of the external synchronisation plug-in unit
0d...1d
2 alarm number of the alarm set by the external synchronisation
plug-in unit
alarm number can be one of the following
0630
1630
3-9 alarm data related to the alarm set by the external
synchronisation plug-in unit
Instructions
This alarm encapsulates the alarm set by the external synchronisation
plug-in unit. For instructions, see the alarm description of the alarm
defined in the second field.
Cancelling
For instructions on how to cancel the alarm, see the alarm description
of the alarm defined in the second field.

Nokia Base Station Alarms(1000-1999)

Comments

Content

Sponsor Documents

Recommended