You are on page 1of 219

Nokia Siemens Networks WCDMA RAN, rel.

RU20, operating documentation, issue 1

RNC disturbances (1000-1999)
DN99580853 Issue 08A Approval Date 2009/09/02

RNC disturbances (1000-1999)

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 2009. 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 Spannung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen 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.

2

Id:0900d8058067c9e1

DN99580853 Issue 08A

RNC disturbances (1000-1999)

Table of Contents
This document has 219 pages. Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Default alarm indication preventions in the system . . . . . . . . . . . . . . . . . 8 List of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1001 UNIT RESTARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1002 RAM FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1003 PARITY ERROR IN RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS. . 25 1007 RESTARTED PROGRAM BLOCK . . . . . . . . . . . . . . . . . . . . . . . . 26 1008 MML PROGRAM RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . 27 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE . . . . . . . . 28 1012 EXCESSIVE RESTARTS OF UNIT . . . . . . . . . . . . . . . . . . . . . . . 29 1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED . . . . . . . 30 1016 MB INTERFACE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 1018 PROGRAM BLOCK COMMUNICATION ERROR . . . . . . . . . . . . 32 1020 PROGRAM BLOCK START UP FAILURE . . . . . . . . . . . . . . . . . . 33 1021 PROGRAM BLOCK REWARMING STARTED. . . . . . . . . . . . . . . 35 1022 PROGRAM BLOCK WARMUP FAILURE. . . . . . . . . . . . . . . . . . . 36 1023 EXCESSIVE DISTURBANCES IN SUPERVISION . . . . . . . . . . . 37 1024 HAND PROCESS ERROR IN PROGRAM BLOCK . . . . . . . . . . . 38 1029 SCCP STP MESSAGE PREVENTION. . . . . . . . . . . . . . . . . . . . . 40 1035 UPU MESSAGE RECEIVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE . . . 45 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM . . 46 1064 UNIT UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 1065 DISK UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 1070 CCS7 PROGRAM BLOCK DATA ERROR . . . . . . . . . . . . . . . . . . 50 1071 PROCESSOR TIME SHORTAGE . . . . . . . . . . . . . . . . . . . . . . . . 51 1072 SIGNALLING LINK OUT OF SERVICE . . . . . . . . . . . . . . . . . . . . 53 1076 FORCED LIGHTWEIGHT SCHEDULING . . . . . . . . . . . . . . . . . . 56 1077 FREE STACK SIZE BELOW LIMIT . . . . . . . . . . . . . . . . . . . . . . . 57 1078 PROCESS EXCEPTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

DN99580853 Issue 08A

Id:0900d8058067c9e1

3

RNC disturbances (1000-1999)

31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62

1080 PROCESS STOPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 1082 HAND USAGE LIMIT EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . 62 1083 SEMAPHORE USE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 1089 DYNAMIC LDT SLOTS EXHAUSTED . . . . . . . . . . . . . . . . . . . . . . 64 1090 BUFFER HANDLE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 1098 TOO LONG MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 1103 SIGNALLING MEASUREMENT REPORT LOST . . . . . . . . . . . . . 67 1111 RESTART DUE TO TIME OUT REQUESTED . . . . . . . . . . . . . . . 70 1113 STATISTICS MEASUREMENT OUTPUT FAILURE . . . . . . . . . . . 71 1128 EXCESSIVE DISTURBANCES IN FILE LOADING . . . . . . . . . . . . 73 1136 SIGNALLING MESSAGE DISTRIBUTION ERROR . . . . . . . . . . . 74 1140 FREE LDT SLOT COUNT BELOW LIMIT . . . . . . . . . . . . . . . . . . . 75 1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL . . . . 77 1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED. . 78 1143 AMOUNT OF FREE MEMORY REDUCED . . . . . . . . . . . . . . . . . . 80 1144 FREE BUFFER HEADERS EXHAUSTING . . . . . . . . . . . . . . . . . . 81 1147 MESSAGE QUEUE OVERFLOW . . . . . . . . . . . . . . . . . . . . . . . . . 82 1148 EXCESSIVE TRAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 1165 BUFFER ALLOCATION FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . 85 1169 FREEZING PERIOD OF SS7 REPORTING LOST . . . . . . . . . . . . 87 1183 HMS LINE CONNECTION LOST . . . . . . . . . . . . . . . . . . . . . . . . . 89 1186 NO RESPONSE TO HMN SUPERVISION . . . . . . . . . . . . . . . . . . 90 1192 SSCOP TRANSMIT BUFFER OVERFLOW . . . . . . . . . . . . . . . . . 91 1196 HMS NODE RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION . . 94 1203 SCDFLE FILE INTEGRITY ERROR . . . . . . . . . . . . . . . . . . . . . . . 95 1204 WATCHDOG CAUSES UNIT RESTART. . . . . . . . . . . . . . . . . . . . 96 1205 USER PLANE CONNECTION SETUP FAILURE . . . . . . . . . . . . . 97 1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM . 99 1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED . . 100 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED . . 102

4

Id:0900d8058067c9e1

DN99580853 Issue 08A

. . . . 151 1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 1291 SUBRACK CONNECTIVITY FAILURE. . . . . . . . . . . . . 112 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 1277 PLUG IN UNIT CONNECTION FAILURE. . . . . . . . . 110 1240 SCCP DISTURBANCE . . . . . . . . . . 161 1293 SCCP GT SCREENING APPLIED . . . . . . . . . . . . . . 148 1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE 150 1282 ASSOCIATION PARAMETER FAILURE . . . . 168 DN99580853 Issue 08A Id:0900d8058067c9e1 5 . . . . . . . . . . . . . 153 1285 AAL5 FRAME LOST . . . . . . . . . . . . . . 115 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR 120 1244 RUNNING OUT OF MESSAGE BUFFERS . . . . . . . . . . . . 108 1234 UPDATE OF PASSWORD VALIDITY TIME FAILED . . . . . . . . 104 1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART . . . . . . . . . . . . . . . . . 128 1258 ERROR IN SPARE UNIT UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 1228 UNIT SUPERVISION NOT FUNCTIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 1297 SOCKET INTERFACE FAILURE . 162 1296 SOCKET CREATION FAILURE . . . . . . 107 1232 EHAT RESTARTED . . . . . . . . . . . . . . . . 133 1273 ASP ACTIVATION FAILED. . . . . . . . . . . . . . . . . . . . . . . . . . 137 1275 NO RESPONSE FROM CRITICAL UNIT . . . . . . . . . . . . 147 1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION . . . 127 1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT . . . . . .RNC disturbances (1000-1999) 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 1222 DATA WRITING VIA VDS DEVICE FAILED. . . . . . . . . . . . . . . . . . 124 1246 RESTART OF LEAF UNIT . 126 1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 1269 AAL5 FRAME CORRUPTED . . . . . . . . . . . . 155 1286 MISMATCH IN SYSTEM CLOCK SIGNAL. . . . . . . . . . 109 1239 DSP SUPERVISION FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . 182 1432 DISTURBANCE IN COMMAND CALENDAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 1684 SPARE UNIT WARMUP FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 1598 UNIT FOUND FAULTY BY ALARM SYSTEM . . . . . . . . . . 193 1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM . . . . . 201 1683 PASSIVE UNIT FAULTY . . . . . . 215 1806 PRINTER SPOOLER DISABLED . . . . . . . 200 1682 SCDFLE UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . 210 1801 MASS MEMORY FILE BACKUP FAILURE . . . . . . . . . . . . . . . . . . . 183 1548 MTP CONFUSION MESSAGE RECEIVED. . . 198 1663 HAND RESERVATION ERROR IN DATABASE MANAGER . . . . . . . 174 1331 CDSP MEMORY CONFIGURATION FAILURE . . . . . . . . . . . . . . . . . . 177 1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT 179 1425 OVERFLOW IN ALARM BUFFERING. . . . . . . 204 1685 UNIT RESTART FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 1800 SCSI ADDRESS ILLEGAL. 217 1900 DEGRADED SLIP FREQUENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 1662 DATABASE LOADING ERROR. . . . . . . . . 211 1802 BACKUP COPY LOG FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .RNC disturbances (1000-1999) 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 1298 DSP INTERFACE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 1299 RTCP SUPERVISION FAILURE . . . . . . . . . . . . . 216 1809 IP CONFIGURATION INQUIRY SERVICE FAILED . . . . . . . . . 192 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL . . . . . . . . . . 171 1304 ACTOR EXCEPTION. . . . . . . . . . . . . . . . . 214 1804 IP ROUTING RESOURCE SHORTAGE . . . . . . . 196 1661 DATABASE MANAGER IN FATAL ERROR STATE . . . . . . . . . . . . . . . . . . . . . . . . . . 212 1803 SCSI MALFUNCTION . . . . . . . . . . . . . . . . . . . . . . . 219 6 Id:0900d8058067c9e1 DN99580853 Issue 08A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 1660 UPDATE NUMBER MISMATCH . . . . . . . 190 1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED . . . . . . . . . . . . . . . 191 1570 SECURITY LOG ALARM LIMIT REACHED . . . . . . . . . . . . . . . . . . . . . . . 205 1687 RECOVERY ACTION FAILURE . . . . . . . . . . . . . . . . . . . . . . . 181 1431 MMI SYSTEM OVERLOAD . . . . . . . . . . . . . . . 176 1336 AAL5 CHANNEL USAGE FAILED . . .

the latest document issue contains all changes made to previous issues. Note that the issue numbering system is changing. Therefore. For more information. see Guide to WCDMA RAN operating documentation. Changes made between issues 8-0 and 08A Modified alarms 1569 Changes made between issues 7-1 and 8-0 New alarms 1341 Modified alarms 1056 1076 1077 1078 1080 1083 1089 1090 1098 1140 1142 1143 1144 1147 1148 1165 1198 1220 1221 1222 1228 1240 1244 1299 1660 Changes made between issues 7-0 and 7-1 Modified alarms 1239 1269 1570 1684 DN99580853 Issue 08A Id:0900d805805de168 7 .RNC disturbances (1000-1999) Summary of Changes Summary of Changes Changes between document issues are cumulative.

Default alarm indication preventions in the system RNC disturbances (1000-1999) 1 Default alarm indication preventions in the system Alarm indication preventions for certain alarms have been set by default in RNC. This has been done to reduce the amount of alarm indications that RNC reports to NetAct. The selected alarms are seen as low-priority from network monitoring point of view but in some cases the alarms listed below are preferred to be seen also in RAN level (NetAct). See the MML command group AF (Alarm Flow handling) or Managing alarm indication preventions for details on how to remove alarm-specific indication preventions. Disturbances • • • • 1018 1192 1240 1682 PROGRAM BLOCK COMMUNICATION ERROR SSCOP TRANSMIT BUFFER OVERFLOW SCCP DISTURBANCE SCDFLE UPDATE FAILURE 8 Id:0900d805805de168 DN99580853 Issue 08A . The list of alarms below shows the affected alarms that are indication-prevented by default in RNC.

RNC disturbances (1000-1999) List of Alarms 2 List of Alarms 1001 1002 1003 1004 1007 1008 1010 1012 1014 1016 1018 1020 1021 1022 1023 1024 1029 1035 1052 1056 1064 1065 1070 1071 1072 1076 1077 1078 1080 1082 1083 1089 1090 1098 1103 1111 1113 UNIT RESTARTED RAM FAILURE PARITY ERROR IN RAM COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS RESTARTED PROGRAM BLOCK MML PROGRAM RESTARTED NO RESPONSE TO UNIT SUPERVISION MESSAGE EXCESSIVE RESTARTS OF UNIT PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED MB INTERFACE FAILURE PROGRAM BLOCK COMMUNICATION ERROR PROGRAM BLOCK START UP FAILURE PROGRAM BLOCK REWARMING STARTED PROGRAM BLOCK WARMUP FAILURE EXCESSIVE DISTURBANCES IN SUPERVISION HAND PROCESS ERROR IN PROGRAM BLOCK SCCP STP MESSAGE PREVENTION UPU MESSAGE RECEIVED REQUESTED SERVICE NOT FOUND FROM NAMETABLE MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM UNIT UPDATE FAILURE DISK UPDATE FAILURE CCS7 PROGRAM BLOCK DATA ERROR PROCESSOR TIME SHORTAGE SIGNALLING LINK OUT OF SERVICE FORCED LIGHTWEIGHT SCHEDULING FREE STACK SIZE BELOW LIMIT PROCESS EXCEPTION PROCESS STOPPED HAND USAGE LIMIT EXCEEDED SEMAPHORE USE ERROR DYNAMIC LDT SLOTS EXHAUSTED BUFFER HANDLE ERROR TOO LONG MESSAGE SIGNALLING MEASUREMENT REPORT LOST RESTART DUE TO TIME OUT REQUESTED STATISTICS MEASUREMENT OUTPUT FAILURE DN99580853 Issue 08A Id:0900d805805de168 9 .

List of Alarms RNC disturbances (1000-1999) 1128 1136 1140 1141 1142 1143 1144 1147 1148 1165 1169 1183 1186 1192 1196 1198 1200 1203 1204 1205 1207 1220 1221 1222 1227 1228 1232 1234 1239 1240 1241 1242 1244 1246 1249 1254 1258 EXCESSIVE DISTURBANCES IN FILE LOADING SIGNALLING MESSAGE DISTRIBUTION ERROR FREE LDT SLOT COUNT BELOW LIMIT DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED AMOUNT OF FREE MEMORY REDUCED FREE BUFFER HEADERS EXHAUSTING MESSAGE QUEUE OVERFLOW EXCESSIVE TRAPS BUFFER ALLOCATION FAILED FREEZING PERIOD OF SS7 REPORTING LOST HMS LINE CONNECTION LOST NO RESPONSE TO HMN SUPERVISION SSCOP TRANSMIT BUFFER OVERFLOW HMS NODE RESTARTED CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTED ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION SCDFLE FILE INTEGRITY ERROR WATCHDOG CAUSES UNIT RESTART USER PLANE CONNECTION SETUP FAILURE UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM HANDLING OF MEASUREMENT DEFINITION FILE FAILED STATISTICAL MEASUREMENT REPORT OUTPUT FAILED DATA WRITING VIA VDS DEVICE FAILED TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART UNIT SUPERVISION NOT FUNCTIONING EHAT RESTARTED UPDATE OF PASSWORD VALIDITY TIME FAILED DSP SUPERVISION FAILURE SCCP DISTURBANCE SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR RUNNING OUT OF MESSAGE BUFFERS RESTART OF LEAF UNIT DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE UNSOLICITED DATA LINK RE-ESTABLISHMENT ERROR IN SPARE UNIT UPDATE 10 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) List of Alarms 1269 1272 1273 1275 1277 1278 1281 1282 1283 1285 1286 1290 1291 1293 1296 1297 1298 1299 1304 1331 1336 1341 1425 1431 1432 1548 1569 1570 1590 1597 1598 1660 1661 1662 1663 1682 1683 1684 1685 AAL5 FRAME CORRUPTED TRIAL CONFIGURATION CANCELLED BY SYSTEM ASP ACTIVATION FAILED NO RESPONSE FROM CRITICAL UNIT PLUG IN UNIT CONNECTION FAILURE INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE ASSOCIATION PARAMETER FAILURE AUTOMATIC IP OVER ATM CHANNEL BROKEN AAL5 FRAME LOST MISMATCH IN SYSTEM CLOCK SIGNAL INTER-COMPUTER MESSAGE CONNECTIVITY LOST SUBRACK CONNECTIVITY FAILURE SCCP GT SCREENING APPLIED SOCKET CREATION FAILURE SOCKET INTERFACE FAILURE DSP INTERFACE FAILURE RTCP SUPERVISION FAILURE ACTOR EXCEPTION CDSP MEMORY CONFIGURATION FAILURE AAL5 CHANNEL USAGE FAILED MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT OVERFLOW IN ALARM BUFFERING MMI SYSTEM OVERLOAD DISTURBANCE IN COMMAND CALENDAR MTP CONFUSION MESSAGE RECEIVED CRITICAL LIMIT IN SECURITY REPORTING REACHED SECURITY LOG ALARM LIMIT REACHED ALARM SYSTEM MESSAGE SENDING BUFFER FULL I/O DEVICE FOUND FAULTY BY ALARM SYSTEM UNIT FOUND FAULTY BY ALARM SYSTEM UPDATE NUMBER MISMATCH DATABASE MANAGER IN FATAL ERROR STATE DATABASE LOADING ERROR HAND RESERVATION ERROR IN DATABASE MANAGER SCDFLE UPDATE FAILURE PASSIVE UNIT FAULTY SPARE UNIT WARMUP FAILURE UNIT RESTART FAILURE DN99580853 Issue 08A Id:0900d805805de168 11 .

The information here is for documentation purposes only. The operator can modify them with an MML command. The following listing also contains alarm event types.List of Alarms RNC disturbances (1000-1999) 1687 1800 1801 1802 1803 1804 1806 1809 1900 RECOVERY ACTION FAILURE SCSI ADDRESS ILLEGAL MASS MEMORY FILE BACKUP FAILURE BACKUP COPY LOG FAILURE SCSI MALFUNCTION IP ROUTING RESOURCE SHORTAGE PRINTER SPOOLER DISABLED IP CONFIGURATION INQUIRY SERVICE FAILED DEGRADED SLIP FREQUENCY Alarm parameters The following parameter settings are the default settings. Please note that this information is not part of the alarm parameter listing and it is not possible to change those values using MML commands. NR TEXT CLS OUT SDC SDD CDL LVT -------------------------------------------------------------------------------1001 UNIT RESTARTED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT RAM FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT PARITY ERROR IN RAM 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST 00:00:15 NONE 1002 DST 00:00:15 NONE 1003 DST 00:00:15 NONE 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS 00:00 00:00 00:00 00:01:15 EVENT TYPE: PROCESSING RESTARTED PROGRAM BLOCK 00:00 00:00 00:00 EVENT TYPE: PROCESSING MML PROGRAM RESTARTED 00:00 00:00 00:00 EVENT TYPE: PROCESSING DST NONE 1007 DST 00:02:15 NONE 1008 DST 00:00:15 NONE 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE 00:00 00:00 00:00 00:04:30 EVENT TYPE: PROCESSING DST NONE 12 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) List of Alarms 1012 EXCESSIVE RESTARTS OF UNIT 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED 00:00 00:00 00:00 00:01:15 EVENT TYPE: PROCESSING MB INTERFACE FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1014 DST NONE 1016 DST 00:00:15 NONE 1018 PROGRAM BLOCK COMMUNICATION ERROR 00:00 00:00 00:00 02:00:00 EVENT TYPE: PROCESSING PROGRAM BLOCK START UP FAILURE 00:00 00:00 00:00 00:05:00 EVENT TYPE: PROCESSING PROGRAM BLOCK REWARMING STARTED 00:00 00:00 00:00 00:05:00 EVENT TYPE: PROCESSING PROGRAM BLOCK WARMUP FAILURE 00:00 00:00 00:00 00:02:15 EVENT TYPE: PROCESSING EXCESSIVE DISTURBANCES IN SUPERVISION 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING HAND PROCESS ERROR IN PROGRAM BLOCK 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT SCCP STP MESSAGE PREVENTION 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING UPU MESSAGE RECEIVED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1020 DST NONE 1021 DST NONE 1022 DST NONE 1023 DST NONE 1024 DST NONE 1029 DST NONE 1035 DST 00:00:15 NONE 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT DST NONE 1056 DST NONE DN99580853 Issue 08A Id:0900d805805de168 13 .

List of Alarms RNC disturbances (1000-1999) 1064 UNIT UPDATE FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DISK UPDATE FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST 00:00:15 NONE 1065 DST 00:00:15 NONE 1070 CCS7 PROGRAM BLOCK DATA ERROR 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING PROCESSOR TIME SHORTAGE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1071 DST 00:01:00 NONE 1072 SIGNALLING LINK OUT OF SERVICE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT FORCED LIGHTWEIGHT SCHEDULING 00:00 00:00 00:00 00:01:00 EVENT TYPE: EQUIPMENT FREE STACK SIZE BELOW LIMIT 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT PROCESS EXCEPTION 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT PROCESS STOPPED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1076 DST NONE 1077 DST NONE 1078 DST 00:10:00 NONE 1080 DST 00:10:00 NONE 1082 HAND USAGE LIMIT EXCEEDED 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT SEMAPHORE USE ERROR 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1083 DST 00:10:00 NONE 1089 DYNAMIC LDT SLOTS EXHAUSTED 00:00 00:00 00:00 00:01:00 EVENT TYPE: EQUIPMENT BUFFER HANDLE ERROR 00:00 00:00 00:00 DST NONE 1090 DST 00:01:00 NONE 14 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) List of Alarms EVENT TYPE: EQUIPMENT 1098 TOO LONG MESSAGE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST 00:10:00 NONE 1103 SIGNALLING MEASUREMENT REPORT LOST 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT RESTART DUE TO TIME OUT REQUESTED 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT STATISTICS MEASUREMENT OUTPUT FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT EXCESSIVE DISTURBANCES IN FILE LOADING 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT SIGNALLING MESSAGE DISTRIBUTION ERROR 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING FREE LDT SLOT COUNT BELOW LIMIT 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT AMOUNT OF FREE MEMORY REDUCED 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT FREE BUFFER HEADERS EXHAUSTING 00:00 00:00 00:00 00:05:00 EVENT TYPE: EQUIPMENT MESSAGE QUEUE OVERFLOW 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT EXCESSIVE TRAPS DST NONE 1111 DST NONE 1113 DST NONE 1128 DST NONE 1136 DST NONE 1140 DST NONE 1141 DST NONE 1142 DST NONE 1143 DST NONE 1144 DST NONE 1147 DST 00:10:00 NONE 1148 DST NONE DN99580853 Issue 08A Id:0900d805805de168 15 .

List of Alarms

RNC disturbances (1000-1999)

00:00 00:00 00:00 EVENT TYPE: EQUIPMENT 1165 BUFFER ALLOCATION FAILED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

00:10:00

DST 00:10:00

NONE

1169

FREEZING PERIOD OF SS7 REPORTING LOST 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING HMS LINE CONNECTION LOST 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1183

DST 00:00:15

NONE

1186

NO RESPONSE TO HMN SUPERVISION 00:00 00:00 00:00 00:00:10 EVENT TYPE: EQUIPMENT SSCOP TRANSMIT BUFFER OVERFLOW 00:00 00:00 00:00 00:05:00 EVENT TYPE: COMMUNICATIONS HMS NODE RESTARTED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1192

DST

NONE

1196

DST 00:00:15

NONE

1198

CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTED 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION 00:00 00:00 00:00 00:01:00 EVENT TYPE: PROCESSING SCDFLE FILE INTEGRITY ERROR 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING WATCHDOG CAUSES UNIT RESTART 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING USER PLANE CONNECTION SETUP FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM 00:00 00:00 00:00 00:00:50 EVENT TYPE: PROCESSING

DST

NONE

1200

DST

NONE

1203

DST

NONE

1204

DST

NONE

1205

DST

NONE

1207

DST

NONE

16

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

List of Alarms

1220

HANDLING OF MEASUREMENT DEFINITION FILE FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING STATISTICAL MEASUREMENT REPORT OUTPUT FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING DATA WRITING VIA VDS DEVICE FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT UNIT SUPERVISION NOT FUNCTIONING 00:00 00:00 00:00 00:00:50 EVENT TYPE: PROCESSING EHAT RESTARTED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1221

DST

NONE

1222

DST

NONE

1227

DST

NONE

1228

DST

NONE

1232

DST 00:00:15

NONE

1234

UPDATE OF PASSWORD VALIDITY TIME FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING DSP SUPERVISION FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT SCCP DISTURBANCE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1239

DST 00:00:05

NONE

1240

DST 00:00:15

NONE

1241

SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT RUNNING OUT OF MESSAGE BUFFERS 00:00 00:00 00:00 00:00:15 EVENT TYPE: QUALITY OF SERVICE RESTART OF LEAF UNIT 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1242

DST

NONE

1244

DST

NONE

1246

DST 00:00:15

NONE

DN99580853 Issue 08A

Id:0900d805805de168

17

List of Alarms

RNC disturbances (1000-1999)

1249

DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING UNSOLICITED DATA LINK RE-ESTABLISHMENT 00:00 00:00 00:00 00:05:00 EVENT TYPE: COMMUNICATIONS ERROR IN SPARE UNIT UPDATE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING AAL5 FRAME CORRUPTED 00:00 00:00 00:00 02:00:00 EVENT TYPE: COMMUNICATIONS TRIAL CONFIGURATION CANCELLED BY SYSTEM 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT ASP ACTIVATION FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS NO RESPONSE FROM CRITICAL UNIT 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING PLUG IN UNIT CONNECTION FAILURE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT ASSOCIATION PARAMETER FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING AUTOMATIC IP OVER ATM CHANNEL BROKEN 00:00 00:00 00:00 00:00:15 EVENT TYPE: QUALITY OF SERVICE AAL5 FRAME LOST 00:00 00:00

DST

NONE

1254

DST

NONE

1258

DST

NONE

1269

DST

NONE

1272

DST

NONE

1273

DST

NONE

1275

DST

NONE

1277

DST

NONE

1278

DST

NONE

1281

DST

NONE

1282

DST

NONE

1283

DST

NONE

1285

DST 00:00 00:00:15

NONE

18

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

List of Alarms

EVENT TYPE: COMMUNICATIONS 1286 MISMATCH IN SYSTEM CLOCK SIGNAL 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT INTER-COMPUTER MESSAGE CONNECTIVITY LOST 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT SUBRACK CONNECTIVITY FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT SCCP GT SCREENING APPLIED 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING SOCKET CREATION FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE

1290

DST

NONE

1291

DST

NONE

1293

DST

NONE

1296

DST 00:00:15

NONE

1297

SOCKET INTERFACE FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS DSP INTERFACE FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1298

DST 00:00:15

NONE

1299

RTCP SUPERVISION FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS ACTOR EXCEPTION 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT

DST

NONE

1304

DST 00:10:00

NONE

1331

CDSP MEMORY CONFIGURATION FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT AAL5 CHANNEL USAGE FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT OVERFLOW IN ALARM BUFFERING

DST

NONE

1336

DST

NONE

1341

DST

NONE

1425

DST

NONE

DN99580853 Issue 08A

Id:0900d805805de168

19

List of Alarms RNC disturbances (1000-1999) 00:00 00:00 00:00 EVENT TYPE: PROCESSING 1431 MMI SYSTEM OVERLOAD 00:00 00:00 00:00 EVENT TYPE: PROCESSING 00:00:15 DST 00:00:15 NONE 1432 DISTURBANCE IN COMMAND CALENDAR 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING MTP CONFUSION MESSAGE RECEIVED 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT CRITICAL LIMIT IN SECURITY REPORTING REACHED 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT SECURITY LOG ALARM LIMIT REACHED 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT ALARM SYSTEM MESSAGE SENDING BUFFER FULL 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING I/O DEVICE FOUND FAULTY BY ALARM SYSTEM 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT UNIT FOUND FAULTY BY ALARM SYSTEM 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT UPDATE NUMBER MISMATCH 00:00 00:00 00:00 EVENT TYPE: PROCESSING DST NONE 1548 DST NONE 1569 DST NONE 1570 DST NONE 1590 DST NONE 1597 DST NONE 1598 DST NONE 1660 DST 00:00:15 NONE 1661 DATABASE MANAGER IN FATAL ERROR STATE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING DATABASE LOADING ERROR 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1662 DST 00:00:15 NONE 1663 HAND RESERVATION ERROR IN DATABASE MANAGER 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING DST NONE 20 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) List of Alarms 1682 SCDFLE UPDATE FAILURE 00:00 00:00 00:00 EVENT TYPE: PROCESSING PASSIVE UNIT FAULTY 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST 00:00:15 NONE 1683 DST 00:00:15 NONE 1684 SPARE UNIT WARMUP FAILURE 00:00 00:00 00:00 00:10:10 EVENT TYPE: EQUIPMENT UNIT RESTART FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT RECOVERY ACTION FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT SCSI ADDRESS ILLEGAL 00:00 00:00 00:00 EVENT TYPE: PROCESSING DST NONE 1685 DST 00:00:15 NONE 1687 DST 00:00:01 NONE 1800 DST 00:00:15 NONE 1801 MASS MEMORY FILE BACKUP FAILURE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT BACKUP COPY LOG FAILURE 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT SCSI MALFUNCTION 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1802 DST 00:00:15 NONE 1803 DST 00:00:35 NONE 1804 IP ROUTING RESOURCE SHORTAGE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING PRINTER SPOOLER DISABLED 00:00 00:00 00:00 EVENT TYPE: EQUIPMENT DST NONE 1806 DST 00:00:15 NONE 1809 IP CONFIGURATION INQUIRY SERVICE FAILED 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING DEGRADED SLIP FREQUENCY 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS DST NONE 1900 DST NONE DN99580853 Issue 08A Id:0900d805805de168 21 .

Supplementary information fields 1 2 working state of the unit before it was restarted type of unit restart indicated by the initial loading program block: 00 3 warm restart information on the unit restart: 00 01 02 spontaneous executed by the user executed or authorized by the recovery program block 4 type of restart: 00 warm restart 5 code loading mode being used: 00 01 02 optimal loading total loading total loading from disk Instructions The alarm requires no actions. Cancelling No cancelling. 22 Id:0900d805805de168 DN99580853 Issue 08A .1001 UNIT RESTARTED RNC disturbances (1000-1999) 3 1001 UNIT RESTARTED Meaning The unit has restarted.

RNC disturbances (1000-1999) 1002 RAM FAILURE 4 1002 RAM FAILURE Meaning The RAM test program of the computer has observed a malfunction in the RAM memory.FFFFFFFF Instructions If the alarm recurs.. The alarm supports the activation of the automatic recovery for the object unit. the CPU is probably faulty and needs to be replaced. You can check the supporting amount of the alarm with the MML command ARO. DN99580853 Issue 08A Id:0900d805805de168 23 . Supplementary information fields 1 address of the faulty memory location 0. Cancelling No cancelling..

the CPU is probably faulty and needs to be replaced. You can check the supporting amount of the alarm with the MML command ARO. The alarm supports the activation of the automatic recovery for the object unit. Cancelling No cancelling. 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. 24 Id:0900d805805de168 DN99580853 Issue 08A .1003 PARITY ERROR IN RAM RNC disturbances (1000-1999) 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.

or the received reply is erroneous. Cancelling No cancelling. 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 family identifier of program block setting the alarm unit message bus address of the partner program block family identifier of the partner program block identifier of the message sent to the partner program block subidentifier of the message sent to the partner program block case-specific additional information case-specific additional information Instructions The alarm requires no actions.RNC disturbances (1000-1999) 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS 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. 2 3 4 5 6 7 8 DN99580853 Issue 08A Id:0900d805805de168 25 .

26 Id:0900d805805de168 DN99580853 Issue 08A .1007 RESTARTED PROGRAM BLOCK RNC disturbances (1000-1999) 7 1007 RESTARTED PROGRAM BLOCK Meaning The program block has been restarted. or its creation failed program block has made a memory protection error program block did not answer the supervision message program block has acknowledged the supervision message with a wrong state.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 with a command of the service terminal extension MRS or in General Error Messages of System in customer documentation. Instructions The alarm requires no actions. i. Supplementary information fields 1 2 family identifier of the program block error 131d: 132d: 133d: 287d: 302d: 770d: 771d: code program block was not found another program block of the same kind already exists program block deletion error program block has been deleted. Cancelling No cancelling.

The alarm supports the activation of the automatic recovery for the object unit.RNC disturbances (1000-1999) 1008 MML PROGRAM RESTARTED 8 1008 MML PROGRAM RESTARTED Meaning The MMI Manager (MMIMAN) has restarted an MML program. family identifier of the restarted MML program DN99580853 Issue 08A Id:0900d805805de168 27 . Cancelling No cancelling. Supplementary information fields 1 Instructions The alarm requires no actions. You can check the supporting amount of the alarm with the MML command ARO.

1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE RNC disturbances (1000-1999) 9 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE Meaning The unit has not responded to a supervision message sent by the supervisory unit in the specified time. You can check the supporting amount of the alarm with the MML command ARO. it means that the defect is in the object unit of the alarm the supervision mode to detect the fault. Supplementary information fields 1 type of the unit which has failed to acknowledge the supervision. The field may have the following values: 00 01 normal supervision boot supervision Instructions The alarm requires no actions. If the object unit of the alarm is different from the unit given in this field. The alarm supports the activation of the automatic recovery for the object unit. 2 3 Cancelling No cancelling. If the object unit of the alarm is different from the unit given in this field. 28 Id:0900d805805de168 DN99580853 Issue 08A . it means that the defect is in the object unit of the alarm index of the unit which has failed to acknowledge the supervision.

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. DN99580853 Issue 08A Id:0900d805805de168 29 . Cancelling No cancelling.RNC disturbances (1000-1999) 1012 EXCESSIVE RESTARTS OF UNIT 10 1012 EXCESSIVE RESTARTS OF UNIT Meaning The maximum number of restarts set for a unit has been exceeded.

1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED RNC disturbances (1000-1999) 11 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. or find out the possible cause of overload. Cancelling No cancelling. Supplementary information fields 1 2 Instructions Check the validity of the value set for the parameter CPU LOAD SUPERVISION LIMIT of BSPARA with the MML command: ZDOT:<unit type>. processor load rate percentage interval in hundredths of a second 30 Id:0900d805805de168 DN99580853 Issue 08A . The alarm limit and the interval are defined in BSPARA file. no actions are required from the user. To change processor load supervision limit. give the MML command: ZDOM:<unit type>:PROLL=<new supervision limit>. In those cases. This alarm may be given during the system reset because reset causes load.

DN99580853 Issue 08A Id:0900d805805de168 31 . Cancelling No cancelling. In the test. The alarm supports the activation of the automatic recovery for the object unit. maintained by the operating system. You can check the supporting amount of the alarm with the MML command ARO. the unit sends a message to itself both on the active and passive bus. It also checks the error counters of the message buses.RNC disturbances (1000-1999) 1016 MB INTERFACE FAILURE 12 1016 MB INTERFACE FAILURE Meaning In the test. Supplementary information fields 1 message bus test identifier: 1 2 3 4 5 6 7 8 2 message sending does not succeed despite several attempts time supervision of message receiving has expired received test message differs from the one sent the transmission error counter of the MB has been incremented the reception error counter of the MB has been incremented time supervision of message sent with a group address has expired time supervision of message sent with a pair address has expired the supervision error counter of the MB has been incremented message bus index Instructions The alarm requires no actions. the message bus interface (MBIF) has been detected faulty.

Supplementary information fields 1 2 family identifier of program block giving the alarm number of the message sent to the partner program block or number of the received message error code 01 no reply 02 identification of reply is faulty 03 status of reply is faulty 04 sequence number of reply is faulty number of missing reply messages 3 4 Instructions The alarm requires no actions. Cancelling No cancelling. or the reply is faulty. 32 Id:0900d805805de168 DN99580853 Issue 08A .1018 PROGRAM BLOCK COMMUNICATION ERROR RNC disturbances (1000-1999) 13 1018 PROGRAM BLOCK COMMUNICATION ERROR Meaning The partner program block does not respond within the specified time to the message sent to it.

particularly if a program block creation error is in question. Supplementary information fields 1 2 family identifier of the detector of the error the error code returned by the detector of the error.The initialisation time allotted to the program block is too short. presented according to the general error code. Check the meaning of the DX error code. service terminal command ZSXP.RNC disturbances (1000-1999) 1020 PROGRAM BLOCK START UP FAILURE 14 1020 PROGRAM BLOCK START UP FAILURE Meaning When activating a program block. Service terminal command ZOQ. the message bus address of the unit where the error occurred the family identification of the error-committing program block 3 4 Instructions Additional information: Printouts of Starting Phases in customer documentation. an error has been detected which occurred either when creating or activating the program block. The fault may cause disturbances in the system. . You can check its meaning with a command of the service terminal extension MRS or in General Error Messages of System in customer documentation. Check the log with the service terminal command ZSL. Check the program block's check sum. Check the program block's version.The program block has detected an error in its initialisation. DN99580853 Issue 08A Id:0900d805805de168 33 .The program block has made a memory protection error. . Check whether the program block acknowledges USAPRO at all. service terminal command ZSS. Possible causes are: . 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).

Check the error log with the service terminal command ZGD. Possible causes are: .The program block has detected an error in its initialisation. a storage area sufficiently large and free cannot be found. if any (alarm number 1007). 771d: The program block has acknowledged negatively the activation message sent by USAPRO. 34 Id:0900d805805de168 DN99580853 Issue 08A .The program block has been activated into a wrong state with regard to the unit's operating state. a discrepancy between the parameters of the family table and the loading module. a faulty loading module. Check the error log with the service terminal command ZGD. Probable causes are: a fault in the DXPARA family table. If the program block is constantly in a wrong state.A fault in the initialisation of one of the libraries that the manager is responsible for. See the RESTARTED PROGRAM BLOCK alarms. All other error codes indicate a program block creation error. USAPRO restarts the program block.1020 PROGRAM BLOCK START UP FAILURE RNC disturbances (1000-1999) Check the error log with the service terminal command ZGD. 771d). 819d: The starting up of a library manager has failed. Check the version of the program block.In the starting up of the library manager itself. . Cancelling No cancelling. Possible causes are: . Check the versions of the manager and the library. Check the supervision messages between the program block and USAPRO (message numbers 0001 and 0002). service terminal commands ZSXP and ZSK. . Check the previous sections (770d.

Cancelling No cancelling.RNC disturbances (1000-1999) 1021 PROGRAM BLOCK REWARMING STARTED 15 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. DN99580853 Issue 08A Id:0900d805805de168 35 . or its warming failed on the previous occasion. a program block synchronization error is in question. the program block has been reactivated. 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. identifier of the family to be warmed 2 Instructions The alarm requires no actions.

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. 2 3 4 message bus address of the unit where the error occurred family identifier of the program block that made the error Instructions The alarm requires no actions. You can check its meaning in General Error Messages of System. 36 Id:0900d805805de168 DN99580853 Issue 08A . The program block has not acknowledged the warmup command sent by the unit state administration program block (USAPRO). 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 error code returned by the detector of the error.1022 PROGRAM BLOCK WARMUP FAILURE RNC disturbances (1000-1999) 16 1022 PROGRAM BLOCK WARMUP FAILURE Meaning The warming up of a program block has failed. Cancelling No cancelling. or has acknowledged it negatively.

RNC disturbances (1000-1999)

1023 EXCESSIVE DISTURBANCES IN SUPERVISION

17 1023 EXCESSIVE DISTURBANCES IN SUPERVISION
Meaning The recovery system has detected serious disturbances in the functioning of the process families or the actors of the unit. Typically, the alarm is set due to malfunction of some critical process families or actors, but it might be also set due to excessive errors related to non-critical process families or actors. The situation leads to a restart of the unit. Supplementary information fields
1 the following types of error are specified: 0 1 2 3 4 5 6 7 8 9 2 No answer to supervision Wrong unit state in supervision acknowledge Exception Synchronization failure in SP unit No answer to startup message Bad answer to startup message Error in PRB build Maximum number family recovery exceeded Maximum number warming failures exceeded Restart requested by system level recovery software

the identifier of the process family or actor which detected the error the error code returned by the detector of the error the computer unit where the error occurred the family identifier of the error-committing process family or actor

3 4 5

Instructions The alarm requires no actions. Cancelling No cancelling.

DN99580853 Issue 08A

Id:0900d805805de168

37

1024 HAND PROCESS ERROR IN PROGRAM BLOCK

RNC disturbances (1000-1999)

18 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: 1: 2: 3: 4: 5: 6: 2 creation of hands creation of additional hands reservation of hand renewal of hand reservation expiry of hand reservation restart of hand deletion of hand group

error code returned by system library service primitive. See General Error Messages of System for error code explanations type of reserved hand/hand to be reserved. 0 if not known number of reserved hand/hand to be reserved life focus of the hand computer address of the customer family ID of the customer process ID of the customer life focus of the customer

3 4 5 6 7 8 9

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

38

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

1024 HAND PROCESS ERROR IN PROGRAM BLOCK

printouts obtained with the service terminal commands ZSCFE, ZGSC, ZSL, and with the F, D, H, and G commands of the FAM family extension.

Cancelling No cancelling.

DN99580853 Issue 08A

Id:0900d805805de168

39

1029 SCCP STP MESSAGE PREVENTION

RNC disturbances (1000-1999)

19 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) the source point in question is not allowed to send signalling messages to the destination point (the message has been destroyed or sent back) the incoming link set in question should not be used to send signalling messages to the destination point (the message has been transmitted) 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) the pointer of the global title in the calling party address global title is not permitted (the message has been destroyed or sent back) no analysis can be found for the root of the calling party address global title (the message has been destroyed or sent back)

02

03

04

05

06

2

destination point signalling network, which can get the following values: 00 04 08 0C international network 0, IN0 international network 1, IN1 national network 0, NA0 national network 1, NA1

3 4

destination point code value of the processed signalling message originating point signalling network, which can get the following values:

40

Id:0900d805805de168

DN99580853 Issue 08A

E. 03 or 04. 02.numbering plan + encoding type (NP+ENC) . IN0 international network 1.RNC disturbances (1000-1999) 1029 SCCP STP MESSAGE PREVENTION 00 04 08 0C 5 international network 0. the value (5 sequential bytes) indicates the signalling point code of the signalling point and the signalling network. 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. 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.nature of address indicator (NAI) If a field has the value FF. The field is coded so that the first byte indicates the signalling network and the next four indicate the signalling point code.global title indicator (GTI) . NA0 national network 1.g. from which the signalling message was received. the value indicates the root parameter values of the calling party address global title in the following order: . NA1 originating point code value of the processed signalling message 6-10 if Supplementary information field 1 has the value 01.the standard of the global title .translation type (TT) . IN1 national network 0. Check if this restriction DN99580853 Issue 08A Id:0900d805805de168 41 . 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. 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.

if necessary. Check if the root parameters need to be analysed and remove the analysis with the MML command OCM. if necessary. if necessary. 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. In other case the operator who owns the adjacent signalling point mentioned in Supplementary information field 6 should be notified about an access right violation. 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. 42 Id:0900d805805de168 DN99580853 Issue 08A . If the root parameters need to be analysed. check if there should exist an analysis for the global title in question. Check if this restriction is justified and remove the restriction with the MML command OCM. and create it with the MML command NBC. 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.1029 SCCP STP MESSAGE PREVENTION RNC disturbances (1000-1999) 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. Cancelling No cancelling.

This message informs the sending end of a signalling message that the user part of the destination address is not available. obtained from the DN99580853 Issue 08A Id:0900d805805de168 43 .. Supplementary information fields 1 network from which the UPU message came: network code -----------00 04 08 0C network -----national network 0 national network 1 international network 0 international network 1 2 3 header code of message destination point code received in message. DPC) identifier ---------00 01 02 03 04 05 06 07 ) .RNC disturbances (1000-1999) 1035 UPU MESSAGE RECEIVED 20 1035 UPU MESSAGE RECEIVED Meaning The exchange has received a User Part Unavailable message (UPU). In the case of SCCP. ) 0F user part --------spare spare spare SCCP TUP ISUP DUP spare spare MTP test user part 4 5 reason for the unavailability of the user part (4th supplementary information). used services fail.. indicating the unavailable user part in the destination point (3rd supplementary information. Depending on the unavailable user part (TUP and ISUP) the telephone traffic and signalling traffic fail. indicating the destination point of the unavailable user part user part identifier received in the user_part_info of the message.

check from the operator of the destination point whether the user part has been created and whether it is available.1035 UPU MESSAGE RECEIVED RNC disturbances (1000-1999) user_part_info of the message code ---00 01 02 Instructions If the message traffic of the user part concerned should be possible to the destination point. or no service has been created for it user part cannot be reached in the DPC 44 Id:0900d805805de168 DN99580853 Issue 08A . Cancelling No cancelling. reason for unavailability ------------------------user part unknown in the DPC user part has not been created.

Supplementary information fields 1 the first 16 characters of the name of the requested service. Cancelling No cancelling.RNC disturbances (1000-1999) 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE 21 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE Meaning The service that was requested was not found from the nametable. DN99580853 Issue 08A Id:0900d805805de168 45 . spaces are used to make up the difference Instructions The alarm requires no actions. If the name does not contain 16 characters.

the field's value is FF originating point code 5 46 Id:0900d805805de168 DN99580853 Issue 08A .1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM RNC disturbances (1000-1999) 22 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM Meaning SCCP has received a message from the network. It can have the following values: 00 04 08 0C international network 0 international network 1 national network 0 national network 1 3 4 destination point code number of the destination subsystem unknown to SCCP. 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 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 2 CR Connection Request CC Connection Confirm CREF Connection Refused RLSD Released RLC Release Complete DT1 Data Form 1 DT2 Data Form 2 AK Data Acknowledgement UDT Unitdata UDTS Unitdata Service ED Expedited Data EA Expedited Data Acknowledgement RSR Reset Request RSC Reset Confirm ERR Protocol Data Unit Error IT Inactivity Test XUDT Extended Unitdata XUDTS Extended Unitdata Service LUDT Long Unitdata LUDTS Long Unitdata Service network indicator. If the message that is to be routed does not contain a subsystem number.

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. 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 field's value is FF reference number in the DX log. do the following: If the value of Supplementary information field 4 is something other than FF. create it with the MML commands of the previously mentioned command group. if necessary. the field's value is 0 Instructions 7 If the error occurs repeatedly. If the subsystem does not belong in the system. If the subsystem has not been created. If the reference number is not used in the log. ZGSC and ZSL in the report. The signalling point is given Supplementary information field 3 and the signalling network in Supplementary information field 2. In other cases. check if it should be created in the system and. Include the printouts of service terminal commands ZSCFE. DN99580853 Issue 08A Id:0900d805805de168 47 .RNC disturbances (1000-1999) 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM 6 number of the originating subsystem. fill in a Problem report and send it to your local Nokia Siemens Networks representative. If the message that is to be routed does not contain a subsystem number. Cancelling No cancelling. 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 log contains the incorrect message.

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 file has not been updated in the unit which received the updating input.1064 UNIT UPDATE FAILURE RNC disturbances (1000-1999) 23 1064 UNIT UPDATE FAILURE Meaning Failure in the updating of the partner unit or another unit to be updated (M. Supplementary information fields 1 family identifier of the program block that detected the failure number of the message which caused the updating unit to be updated 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 2 3 4 Instructions The alarm requires no actions. 48 Id:0900d805805de168 DN99580853 Issue 08A . SSU). Cancelling No cancelling. either.

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. Check the alarms set by the File Updating Request Manager Program Block (REQMAN).RNC disturbances (1000-1999) 1065 DISK UPDATE FAILURE 24 1065 DISK UPDATE FAILURE Meaning A file modification made in the Central Memory has not been updated onto disk. If moving the file to the disk fails. See General Error Messages of System for error code explanations 3 4 file number offset from the beginning of the file Instructions 1. Move the file shown in the additional information field 3 from the Central Memory to disk with the MML command DFC. Cancelling No cancelling. DN99580853 Issue 08A Id:0900d805805de168 49 . Supplementary information fields 1 2 number of the message that caused the updating error code returned by the file update (general error message of the system). 2. The data of the file on the disk does not correspond to the data in the Central Memory.

2 3 4 50 Id:0900d805805de168 DN99580853 Issue 08A . 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 file number record number subrecord number Instructions In N+1 protected units the warming up of the files may have already corrected the error detected. If necessary. the files of the CCS7 level 3 are likely to contain an error. If the alarm occurs repeatedly. Examine the other alarms given by the unit using the MML command AAP. If the fault situation is over. You can check the supporting amount of the alarm with the MML command ARO. Cancelling No cancelling. examine also the alarm history of the unit using the MML command AHP. The alarm supports the activation of the automatic recovery for the object unit. save the defective file on disk for later examination for errors and contact the customer support service. If the alarm still continues to occur. futher actions are not needed. Check also the log print-outs of the unit.1070 CCS7 PROGRAM BLOCK DATA ERROR RNC disturbances (1000-1999) 25 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.

Fields 5 and 6 contain the family identifier in full. the identifier is FFFF FFFF 6 7 process identifier. i. The processor has a 100 % utilization rate. the process identifier is FFFF FFFF. this process is the probable cause of the disturbance. see description in field 5 priority of the process identified in fields 5 and 6. Check if there is an overload in the network element or a local overload in some 2 3 4 5 DN99580853 Issue 08A Id:0900d805805de168 51 . If there is no such process in the queue for processes fit for running. The situation results from a computer overload or a fault in some processes. the value is 0 Instructions The disturbance may result from a computer overload. The operating system kernel has temporarily set the priority high for those processes that have not received running time for some time. Supplementary information fields 1 number of processes whose priority was set higher by the operating system during the last inspection of the queue for processes fit for running identifier of the family that preceded the process with highest priority among the processes whose priority was set higher in the queue for processes fit for running.RNC disturbances (1000-1999) 1071 PROCESSOR TIME SHORTAGE 26 1071 PROCESSOR TIME SHORTAGE Meaning There is not enough processor time for all processes fit for running.e. although it received processor time during the period. If there is no such process. If the disturbance was generated because of a looped process. Fields 2 and 3 contain the identifier of the family in full process identifier. see description in field 2 priority of the process identified in fields 2 and 3 identifier of a family that was fit for running during the whole of the inspection period.

If the fault lies elsewhere. Cancelling No cancelling.1071 PROCESSOR TIME SHORTAGE RNC disturbances (1000-1999) computer unit of the network element. it is also recommended to inform the supplier of the software package on the fault to investigate the reason for the fault. In these other fault situations. 52 Id:0900d805805de168 DN99580853 Issue 08A . the maintenance of the exchange starts actions to correct the fault situation.

In this case the signal transmission capacity is also decreased. If this signalling link is the only one in the signalling link set. If there is an alternative signalling link available in the link set. the system sets also alarm 2070. LINK SET UNAVAILABLE.RNC disturbances (1000-1999) 1072 SIGNALLING LINK OUT OF SERVICE 27 1072 SIGNALLING LINK OUT OF SERVICE Meaning A signalling link has failed and changed state from IN SERVICE to OUT OF SERVICE. the system performs a changeover. or its initial alignment attempt has failed. Supplementary information fields 1 2 signalling link number signalling link error code 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 3 4 5 6 7 stop command received erroneous BSN received repeatedly erroneous FIB received repeatedly error ratio too high acknowledgement delay too long initial alignment unsuccessful congestion too long SIO received when one is not expected SIN received when one is not expected SIE received when one is not expected SIOS received when one is not expected SIPO received when one is not expected SIB received when one is not expected number of the signalling link terminal number of the logical signalling link terminal number of the internal PCM circuit number of the external PCM circuit previous working state of signalling link terminal: 00 01 02 03 04 05 06 IDLE OUT OF SERVICE MONITORING WAIT FOR FISU NOT ALIGNED ALIGNED PROVING DN99580853 Issue 08A Id:0900d805805de168 53 .

the link typically gives error codes 04 and 0B alternatingly. If the signalling link stays unavailable for a long time and does not realign automatically. the remote signalling link terminal has for some reason detected the link faulty. If this happens repeatedly. the bit error ratio is too high for some other reason. If the exchange terminal does not indicate PCM cutoff. monitor the link with a protocol analyzer in order to solve the problem. The system automatically tries to reactivate the signalling link.1072 SIGNALLING LINK OUT OF SERVICE RNC disturbances (1000-1999) 07 08 09 0A 0B 0C 0D 0E 0F 10 11 Instructions LOOP CHECK ALIGNED/NOT READY ALIGNED/READY IN SERVICE EMPTYING UPPER LEVEL OUTAGE LOCAL PROCESSOR OUTAGE REMOTE PROCESSOR OUTAGE BOTH PROCESSORS OUTAGE INTERNAL LOOP TEST EXTERNAL LOOP TEST If the value of 7th supplementary information is 0A (IN SERVICE). 05. 03. 08. If the value of the 2nd supplementary information is 04. 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. These fault situations are not common. monitor the link with a protocol analyzer to analyze the fault situation. 3. In these cases. depending on which end first detects the error ratio. If the value of the 2nd supplementary information is 02. 2. 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). 0A. 0C or 0D. ask the remote end operator what is the reason for this. You can check the error correction method with the MML command NOI: 54 Id:0900d805805de168 DN99580853 Issue 08A . This error code is typically given when there is a PCM cutoff. 09. If the alarm is caused by a PCM circuit with a high bit error ratio. no actions are required from the user. or there are problems in synchronization. there is a problem in the operation of the remote end signalling link terminal. check data transmission. 1. If the value of the 2nd supplementary information is 0B. if these error codes are often given in this alarm.

Check that the signalling link bit rate is the same in both ends: either 64kbit/s or 56kbit/s. and it means that the signalling link has been restarted as it has been congested for the period of T111 T31. This can happen if. the CCNETM has stopped the link. and increase the capacity or rerouting should be seriously considered. In this case the value of the 7th supplementary information indicates the phase of the initial alignment procedure in which errors were detected. the link is out of service and realignment fails. DN99580853 Issue 08A Id:0900d805805de168 55 . If this happens repeatedly. You can find out the parameter set number with the MML command NCI: ZNCI:<link number>.RNC disturbances (1000-1999) 1072 SIGNALLING LINK OUT OF SERVICE ZNOI:<parameter set number>. The value 0E of the 2nd supplementary information is used only in ANSI network. 5. You can check the signalling link bit rate with the MML command NOI: ZNOI:<parameter set number>. Cancelling No cancelling. If the value of the 2nd supplementary information is 06. 4. there is serious overload in the signalling network. Usually the alignment fails because the bit error ratio is too high. You can find out the parameter set number with the MML command NCI: ZNCI:<link number>. the test procedure of the signalling link fails. for example. If the value of the 2nd supplementary information is 01. The most common reason for this is that the signalling link code (SLC) is not same in both ends. 6. Analyze the fault with a protocol analyzer.

Since the reason is usually a fault in the application. in order to investigate the reason for the fault.1076 FORCED LIGHTWEIGHT SCHEDULING RNC disturbances (1000-1999) 28 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. Supplementary information fields 1 2 3 identifier of the family where forced scheduling was executed process identifier of the hand whose running was stopped focus of the process identifier of the hand whose running was stopped length of the period. The alarm requires no other actions. Cancelling No cancelling. so as not to disturb the functioning of the other hands in the family. in seconds. The running of the hand identified in the supplementary information of the alarm is stopped and the next hand is allowed to run. The situation usually results from a fault in the functioning of a hand. that the hand was running Instructions There is a temporary disturbance in the functioning of the family. The other hands in the family have been waiting for their turn to run. it is recommended that you inform your local Nokia Siemens Networks representative about the fault. 4 56 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) 1077 FREE STACK SIZE BELOW LIMIT 29 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. see field 1 free stack size decrease in free stack size was detected because: 1 2 ESP value was below the threshold values other than zero were detected in the lowest 128 bytes of the stack 2 3 4 5 Instructions The alarm indicates a temporary disturbance in the functioning of the process. DN99580853 Issue 08A Id:0900d805805de168 57 . If it continues. the situation may disturb the functioning of the computer. 2 and 3 consist of the complete identifier of the process in question identifier of the process which set the disturbance. The disturbance may have been caused by an error in the software or the packaging. Supplementary information fields 1 family identifier of the process whose free stack size is below the limit. Fields 1. so it is recommended that you inform your local Nokia Siemens Networks representative in order to detect the possible fault. see description in field 1 focus of the process. Cancelling No cancelling.

for instance a process restart or a computer switchover. the reason for the exception is probably a fault in software. specified in the supplementary information of this alarm. 5 58 Id:0900d805805de168 DN99580853 Issue 08A . The exception may result from a software or hardware fault. The recovery from the freezing of a process may require maintenance actions. Possible values are: 00 04 05 06 07 08 09 0A 0B 0C 0D 0E 10 FF division by zero overflow segmentation fault invalid operation code parallel processor missing double fault faulty segment reference in parallel processor invalid Task State Segment segment not present stack exception general protection error page fault error in parallel processor exception not found in the log 4 selector of the exception address. as a result. If the value of field 3 is FF.1078 PROCESS EXCEPTION RNC disturbances (1000-1999) 30 1078 PROCESS EXCEPTION Meaning A process. this field has no significance Instructions If the computer has not set alarms on hardware fault. the process has been frozen. has caused an exception and. contact your local Nokia Siemens Networks representative. To correct the fault. If the value of field 3 is FF. this field has no significance offset of the exception address. Supplementary information fields 1 2 3 family identifier of the process that caused an exception process identifier of the process that caused an exception type of exception.

Cancelling No cancelling.RNC disturbances (1000-1999) 1078 PROCESS EXCEPTION The alarm requires no further actions. DN99580853 Issue 08A Id:0900d805805de168 59 .

Values set by system program library: 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 master calling for stopping FAMILY_SERVICES_IN_USE attribute missing error in buffered message reception incorrect family generation no more LDT slots saving the message failed numbers of hand types not valid hand initialization failed incorrect user for the routine lib_TNSDL_stop_r incorrect user for the routine lib_TNSDL_create_r incorrect user for the routine lib_receive_msg_r parameter error. MIN_FREE_TIME parameter error. START_PTR parameter error. The process is stopped on purpose. TRANSITION_PTR internal error in reserving data area for lightweight hand internal error in saving the stack Values set by the TNSDL translator: 80 81 82 83 84 85 86 master called for STOP statement overflow in user's encode routine overflow in system's encode routine error in user's decode routine. The fault situation is usually a result of erroneous packaging or functioning. internal INPUT internal message queue full internal message queue empty 60 Id:0900d805805de168 DN99580853 Issue 08A . a process restart. FPAR of hand error in user's decode routine. Supplementary information fields 1 2 3 family identifier of the process that was stopped process identifier of the process that was stopped the fault was noticed by: 01 02 4 LIBGEN library code produced by the TNSDL translator cause of the failure.1080 PROCESS STOPPED RNC disturbances (1000-1999) 31 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. Stopping the process may require maintenance. for example.

The field is only in use if field 4 has one of the below-mentioned values. the meaning of the field is also explained 01 89 upper word of the return address offset 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. DN99580853 Issue 08A Id:0900d805805de168 61 . the meaning of the field is also explained 01 81 82 87 88 89 lower word of the number of message number of message number of message number of message identifier of the reference is made return address offset being handled at the time of the error being handled at the time of the error being handled at the time of the error being handled at the time of the error source code file where the erroneous (internal identifier of the translator) 6 additional information on the fault.RNC disturbances (1000-1999) 1080 PROCESS STOPPED 87 88 89 5 error in user's decode routine message too short table indexed beyond the index area additional information on the fault. so it is recommended that you inform local Nokia Siemens Networks representative. The field is only in use if field 4 has one of the below-mentioned values. the meaning of the field is also explained 01 89 return address selector index used in erroneous indexing Instructions The fault usually lies in the software or the packaging. The alarm requires no further actions. Cancelling No cancelling.

Also. If there are no free hands of a certain hand type. or an insufficient number of hands in a given hand type. the supervision parameter values may be too low. and this may thus disturb the functioning of the computer. Cancelling No cancelling. If the number of free hands in a given hand type has in fact been small. 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.1082 HAND USAGE LIMIT EXCEEDED RNC disturbances (1000-1999) 32 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. increase the number of hands in the DXPARA file used in the computer. The modified number of hands will be valid after the next loading restart of the computer. that type of hands cannot be reserved. 62 Id:0900d805805de168 DN99580853 Issue 08A . Supplementary information fields 1 2 3 family identifier hand type identifier minimum percentage of free hands in a given hand type during the supervision period supervision limit percentage minimum number of free hands in a given hand type during the supervision period number of free hands in a given hand type at the end of the supervision period 4 5 6 Instructions The cause of the disturbance may be a fault or an overload situation.

Cancelling No cancelling. Supplementary information fields 1 family identifier of the process that called the routine where an error was detected process identifier of the process that called the routine where an error was detected error code describing the error detected. The possible values are: 257d 258d 259d 260d 261d 4 5 error in semaphore name attempt to use the semaphore in a way not allowed by protection illegal attempt to initialize the semaphore ENTER_REGION routine call in a critical area EXIT_REGION routine call outside a critical area 2 3 selector part of the call return address offset part of the call return address Instructions There is a fault in the software or the packaging. The alarm requires no further actions. The error may disturb the functioning of the erroneous application or the co-operation of applications.RNC disturbances (1000-1999) 1083 SEMAPHORE USE ERROR 33 1083 SEMAPHORE USE ERROR Meaning The system has detected an error in a semaphore handling routine of the operating system kernel. DN99580853 Issue 08A Id:0900d805805de168 63 . so it is recommended that you inform your local Nokia Siemens Networks representative in order to find out the reason for the fault situation.

because some operating system routines handle tables other than the process family's own local descriptor table.1089 DYNAMIC LDT SLOTS EXHAUSTED RNC disturbances (1000-1999) 34 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. 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 process identifier of the process that called the routine where an error was detected selector part of the call return address offset part of the call return address 2 3 4 Instructions 1. The error disturbs the functioning of the process family and thus possibly the functioning of the whole computer. This will help to determine the fault. that is. Useful information can also be obtained from the operating system log or the computer log. too many slots are reserved. 2. The fault may also be in software. Output the resource information of the process family indicated in the alarm by using the DOI command. an insufficient number of dynamic local descriptor table slots in comparison with the number of hand processes are reserved for a family. that is. Cancelling No cancelling. Inform your local Nokia Siemens Networks representative about the fault. The process family indicated in the supplementary information fields of this alarm is not always the one whose descriptor table is full. The fault may be in packaging. 64 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) 1090 BUFFER HANDLE ERROR 35 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. 2 3 4 DN99580853 Issue 08A Id:0900d805805de168 65 . Supplementary information fields 1 family identifier of the process that called the routine where an error was detected process identifier of the process that called the routine where an error was detected selector part of the call return address offset part of the call return address Instructions The fault is in the software. Cancelling No cancelling. it is recommended that you inform your local Nokia Siemens Networks representative. so that the buffer remains occupied by the process. therefore.

therefore. Supplementary information fields 1 family identifier of the process that received a message to an insufficient reception area process identifier of the process that received a message to an insufficient reception area message length message sender's computer message sender's family identifier message sender's process identifier message number 2 3 4 5 6 7 Instructions The fault is in software or packaging. receiving the message to the process data area was only partially successful. the process may erroneously read information in the data area outside the reception area as the end part of the message. If the process does not check whether message reception was successful. therefore. and interpret that data according to message structure. Cancelling No cancelling. in order to correct the fault situation. 66 Id:0900d805805de168 DN99580853 Issue 08A . it is recommended that you inform your local Nokia Siemens Networks representative.1098 TOO LONG MESSAGE RNC disturbances (1000-1999) 36 1098 TOO LONG MESSAGE Meaning A message to be received is longer than the area reserved for message reception. The alarm requires no further actions.

The reason may be in the definition of the logical file used in the outputting of the report. DN99580853 Issue 08A Id:0900d805805de168 67 .921 ERROR METERS TC TRANSACTION METERS SIGNALLING LINK INTERVAL LOG MTP SIGNALLING POINT INTERVAL LOG SCCP SIGNALLING POINT INTERVAL LOG SCCP SEGMENTATION AND REASSEMBLY ERRORS INTERVAL LOG TC INTERVAL LOG SCCP GT TRANSLATION ERRORS LOG the value 154d will be output in the field if RFGPRB program block gives no answer to the output request of the report. DPC AND SIO SCCP SIGNALLING POINT METERS SCCP SUBSYSTEM METERS SCCP LOCAL SUBSYSTEM AVAILABILITY SCCP SINGLE METERS TC PERFORMANCE AND UTILIZATION TRANSMITTED AND RECEIVED FRAMES AND OCTETS ON D-CHANNEL D-CHANNEL MISCELLANEOUS STATISTICAL METERS Q. You can check the meaning of error codes with a command of the service terminal extension MRS or in General Error Messages of System in customer documentation. Otherwise some other general error code will be output. Supplementary information fields 1 the lost report: 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 20 21 22 23 24 25 2 SIGNALLING LINK AVAILABILITY SIGNALLING LINK PERFORMANCE SIGNALLING LINK UTILIZATION SIGNALLING POINT STATUS SIGNALLING LINK SET AND ROUTE SET AVAILABILITY SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINT SIF AND SIO OCTETS HANDLED WITH SIO SIF AND SIO OCTETS HANDLED WITH OPC. 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. or in the switching.RNC disturbances (1000-1999) 1103 SIGNALLING MEASUREMENT REPORT LOST 37 1103 SIGNALLING MEASUREMENT REPORT LOST Meaning The forming or outputting of signalling measurement report in the defined device has failed.

........g... Command Reference Manual.1103 SIGNALLING MEASUREMENT REPORT LOST RNC disturbances (1000-1999) Instructions Make sure that the operation and maintenance unit (OMU) is in the WO-EX state..) If the logical files of binary reports are connected to the MEAFIL file........921 ERROR METERS MTP interval log reports: MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORT MTPSPLOGA SIGNALLING POINT INTERVAL LOG REPORT 68 Id:0900d805805de168 DN99580853 Issue 08A ...... 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.e... Logical file Measurement type ........... that the logical file is further connected to another logical file (e. ascii bin MTP measurement reports: MTPSLAVAIA MTPSLAVAIB MTPSLPERFA MTPSLPERFB MTPSLUTILA MTPSLUTILB MTPSPSTATA MTPSPSTATB MTPSLSAVAA MTPSLSAVAB MTPOCTHSPA MTPOCTSIOA MTPOCTMATA MTPOCTHSPB MTPOCTSIOB MTPOCTMATB SIGNALLING LINK AVAILABILITY SIGNALLING LINK PERFORMANCE SIGNALLING LINK UTILIZATION SIGNALLING POINT STATUS SIGNALLING LINK SET AND ROUTE SET AVAILABILITY SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINT SIF AND SIO OCTETS HANDLED WITH SIO SIF AND SIO OCTETS HANDLED WITH OPC.. make sure that the MEAFIL is connected to the virtual data storing device (VDS)... Make sure that the connection of the logical file of the measurement in question is in order... i.. binary report file to the MEAFIL) or to a working I/O-device (see I/O Configuration Handling....

RNC disturbances (1000-1999) 1103 SIGNALLING MEASUREMENT REPORT LOST SCCP/TC interval log reports: 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. DN99580853 Issue 08A Id:0900d805805de168 69 .

Cancelling No cancelling. and no restart has been made. but recovery has sent a negative response or has not responded at all. Supplementary information fields 1 reason for informing about disturbance: 00 recovery system has given negative response to system restart request recovery system has not responded to system restart request 01 2 error code sent by recovery system if it has sent a negative response to system restart request. You can check the meaning of the field in General Error Messages of System.1111 RESTART DUE TO TIME OUT REQUESTED RNC disturbances (1000-1999) 38 1111 RESTART DUE TO TIME OUT REQUESTED Meaning Software configuration management has asked the recovery system for system restart. Instructions The alarm requires no actions. 70 Id:0900d805805de168 DN99580853 Issue 08A .

report hand process of the program block (AMNPRB) has not responded to the report request .overload of the I/O system . reading or writing of the measurement file has failed reserving buffer for the report message failed error in copying data to the report message 2 3 02 03 04 05 4 reason for the error. Significant only if the previous field (error case) has the value 01: 0d other values more detailed reason for the error not known error code returned by the I/O system. The reason may be one of the following: . if the measurement report is output.reading or writing of the measurement file has failed The data of the measurement that has caused the alarm will disappear or. You can check its meaning in the General Error Messages of System DN99580853 Issue 08A Id:0900d805805de168 71 .RNC disturbances (1000-1999) 1113 STATISTICS MEASUREMENT OUTPUT FAILURE 39 1113 STATISTICS MEASUREMENT OUTPUT FAILURE Meaning The outputting of statistics measurement report in the defined I/O device has failed.I/O device is not functional . the data in it may be faulty. A more detailed reason for the error is given in the next supplementary information field no reply to a report request. Supplementary information fields 1 name of the statistics measurement whose report output failed version number of the measurement error case: 01 error in the I/O system.connection of the logical file used in the outputting of the report to the I/O device is not in order . The report is sent to be outputted to the report hand process of the program block (AMNPRB) or the report generation program block (RFGPRB).

1113 STATISTICS MEASUREMENT OUTPUT FAILURE RNC disturbances (1000-1999) Instructions 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 IHI) and that the logical output file STATMEAB is connected to the device in question (MML command IID). Cancelling No cancelling. 72 Id:0900d805805de168 DN99580853 Issue 08A .

identifier of the family that detected the error: RXSPRB (3AB): error detected by the System Level Restart Controller physical address of the computer where the failed loading was executed load group source: 01 memory 02 disk load group identifier of the file whose loading failed Instructions The alarm requires no actions. You can check its meaning in General Error Messages of System. Supplementary information fields 1 general error message of the system. 2 3 4 5 6 DN99580853 Issue 08A Id:0900d805805de168 73 . Cancelling No cancelling.RNC disturbances (1000-1999) 1128 EXCESSIVE DISTURBANCES IN FILE LOADING 40 1128 EXCESSIVE DISTURBANCES IN FILE LOADING Meaning File loading has been interrupted due to recurring errors. The object unit of the alarm is restarted by the recovery system to recover from the errors.

Supplementary information fields 1 error code: 01 02 03 2 PCMCON file access error COSPPC file access error CIINTA file access error value of service information octet (SIO) of received signalling message value of destination point code of received signalling message value of originating point code of received signalling message value of signalling link selection field of received signalling message the value of the circuit identification code field of such a received signalling message that contains the field. e. the signalling messages of the TUP and ISUP user parts next three bytes after the user label in the signalling message received from the signalling link 3 4 5 6 7-9 Instructions Check whether the error is caused by the files or by a faulty message. 74 Id:0900d805805de168 DN99580853 Issue 08A .g.1136 SIGNALLING MESSAGE DISTRIBUTION ERROR RNC disturbances (1000-1999) 41 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. Cancelling No cancelling.

Connect the logical file OSSTATREP to I/O terminal using the MML command IIS. too many slots are reserved or the supervision limit is set to be unnecessarily high. In case the dynamic LTD slot count falls below the supervision limit. that is. Disturbance observation 1089 is set when there are no more dynamic LDT slots. 2. The measurements are displayed to the logical file OSSTATREP. Contact your local Nokia Siemens Networks representative. Create a long-term family resource status measurement using the MML command DOF and start the measurement by giving the MML command DOG. Supplementary information fields 1 family identifier of the process whose free dynamic LDT slot count is below the limit number of family's free dynamic LDT slots supervision limit 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 3 4 DN99580853 Issue 08A Id:0900d805805de168 75 . In such case the slot count may fall below the limit even in normal operation. an insufficient number of dynamic local descriptor table slots in comparison with the number of hand processes are reserved for a family. that is.RNC disturbances (1000-1999) 1140 FREE LDT SLOT COUNT BELOW LIMIT 42 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. When the family has no more dynamic LDT slots the family is restarted. 3. which may interfere with the functioning of the computer. it is highly probable that the number of slots has been significantly reduced. The fault may be in packaging. The fault may also be in software. and the reason for this should be clarified immediately.

1140 FREE LDT SLOT COUNT BELOW LIMIT RNC disturbances (1000-1999) Displaying the resource status and providing these results speeds up the correction of the fault. Cancelling No cancelling. 76 Id:0900d805805de168 DN99580853 Issue 08A .

Appendices. Change into testing state the unit where the plug-in unit that is suspected faulty is located. Check also with the MML command AHP whether the alarm 2224. Maintenance Manual. Supplementary information fields 1 2 3 Instructions Check the amount of traffic on the channel concerned with the MML commands of statistics handling. ERROR IN MSU HANDLING. so that the signalling traffic is disturbed. You can obtain the amount of traffic on the channel. Perform a changeover for the target unit of the alarm with the MML command USC. either for the last half hour or cumulatively. If traffic is low. If it is. see Diagnostics and Testing. has been issued. See Instructions for Replacing Plug-in Units. with the MML command OLU.RNC disturbances (1000-1999) 1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL 43 1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL Meaning The delay buffer of a plug-in unit is full. act according to its instructions. Messages are deleted when the delay buffer is in use. the plug-in unit might be faulty. The alarm is issued when there is a changeover or controlled rerouting. Replace the plug-in unit. plug-in unit type plug-in unit index logical number of signalling terminal DN99580853 Issue 08A Id:0900d805805de168 77 . Run diagnostics for the unit to find out whether the plug-in unit is faulty. The overflow situation may be caused by overload or a failure in the plug-in unit. if diagnostics detects that it is faulty. Cancelling No cancelling. Maintenance Manual.

During start up. the system allocates memory areas to the family based on maximum memory use rate in normal functions. Supplementary information fields 1 2 3 4 family identifier family's memory use percentage observed by supervision supervision limit percentage memory. in kilo bytes. The failure to reserve memory disturbs the functioning of the processes and the computer. In an overload situation an increased number of reserved hands and unhandled messages for a certain process family can result in unexpected memory exhaust. If it exceeds 64 MB.1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED RNC disturbances (1000-1999) 44 1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED Meaning The family indicated in the supplementary information fields of this alarm has exceeded the supervision limit set to its memory use. in kilo bytes. at the time of the supervision. If it exceeds 64 MB. If it exceeds 64 MB. The system also supervises that this limit is not exceeded. the value is FFFF memory. Display the resource status of the process family indicated 5 6 7 78 Id:0900d805805de168 DN99580853 Issue 08A . the value is FFFF Instructions 1. Depending on the functions of the computer. in kilo bytes. in kilo bytes. the value is FFFF free memory. allocated to the family at the end of the supervision period. 2. 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. Check whether the disturbance is caused by an overload situation. the limit is exceeded. the value is FFFF free memory. allocated to the family at the time of the supervision. traffic capacity or charging may be disturbed. at the end of the supervision period. this alarm is set off. If it exceeds 64 MB.

Displaying information on memory use and providing these results speeds up the correction of the fault. This speeds up the diagnosis and correction of the fault. DN99580853 Issue 08A Id:0900d805805de168 79 . 3.RNC disturbances (1000-1999) 1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED in the additional information field of the alarm by using the MML command DOI. contact your local Nokia Siemens Networks representative to detect a possible fault in software. Cancelling No cancelling. If there is no overload.

Use the MML command DOI to investigate the computer's memory use for different purposes. memory allocation fails and may disturb the functioning of the computer.1143 AMOUNT OF FREE MEMORY REDUCED RNC disturbances (1000-1999) 45 1143 AMOUNT OF FREE MEMORY REDUCED Meaning The amount of free memory in the computer is below the alarm limit used in supervision. Cancelling No cancelling. size of the biggest free buffer alarm limit used in supervision total free memory amount total memory amount in memory administration 80 Id:0900d805805de168 DN99580853 Issue 08A . as its size is more in accordance with the available free memory amount than the total free memory amount. The alarm limit used in supervision can be modified with the MML command DOM. The size of the largest unified memory area is used as the free memory amount. parameter MEML. Supplementary information fields 1 2 3 4 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. If the computer runs out of free memory. send the information on memory use to your local Nokia Siemens Networks representative. To find out the nature and cause of the situation.

resulting in an insufficient overall number of buffer headers or one of the process families reserving too many headers. Check the current value of the parameter BUFFER HEADER SUPERVISION LIMIT by using the MMl command DOT. number of free buffer headers alarm limit used in supervision total number of buffer headers DN99580853 Issue 08A Id:0900d805805de168 81 . The fault may be in packaging or software.RNC disturbances (1000-1999) 1144 FREE BUFFER HEADERS EXHAUSTING 46 1144 FREE BUFFER HEADERS EXHAUSTING Meaning The number of free buffer headers is below the alarm limit used in supervision. It is also possible that the supervision limit has been set to be unnecessarily high. When there are no more free buffer headers the computer must be restarted. If the value of this parameter is 100 or below. in which case an alarm is set too early. Supplementary information fields 1 2 3 Instructions 1. This indicates an increased risk of running out of free buffer headers. contact your local Nokia Siemens Networks representative to detect a possible fault in packaging or software. Cancelling No cancelling. 2. If the value is unnecessarily high. decrease it by giving the MML command DOM according to the instructions of the Nokia Siemens Networks representative.

it is recommended that you inform your local Nokia Siemens Networks representative. Cancelling No cancelling. Supplementary information fields 1 2 3 4 5 6 family identifier of the process whose message queue is full process identifier of the process whose message queue is full sender computer of the deleted message sender family identifier of the deleted message sender process identifier of the deleted message deleted message number Instructions The fault lies in software or packaging. therefore.1147 MESSAGE QUEUE OVERFLOW RNC disturbances (1000-1999) 47 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. in order to detect the reason for the fault. 82 Id:0900d805805de168 DN99580853 Issue 08A . The alarm requires no further actions.

Operating system logs have been written in the OSSUPREP logical file and studying those can help you in locating the fault. that is. the system normally gives other alarms as well.RNC disturbances (1000-1999) 1148 EXCESSIVE TRAPS 48 1148 EXCESSIVE TRAPS Meaning The number of traps exceeds the alarm limit during the supervision interval. for example. The address formed by CS and EIP is an address where the program execution was when the trap was detected. contact your local Nokia Siemens Networks representative. check the equipment data with the MML commands of WT command group. software or in the data that the program uses. but they indicate a disturbance either in the hardware. allow it with the MML command ZDOM. DN99580853 Issue 08A Id:0900d805805de168 83 . Traps are produced when the program uses an insufficient or faulty memory or. If the fault is related to hardware. a faulty addtional plug-in unit. Supplementary information fields 1 2 3 4 5 6 number of traps during supervision interval alarm limit used in supervision identifier of the family that caused the latest trap identifier of the process that caused the latest trap register's CS value at the moment of the latest trap detection register's EIP value at the moment of the latest trap detection Instructions 1. If the system has not given alarms on hardware faults. If the equipment data is correct or if you do not succeed in correcting the fault. Connect the OSSUPREP logical file to the I/O terminal available with the MML command ZIIS. 2. the address describes the program's general execution area rather than a specific memory addressing execution area. Check with the MML command ZDOP whether parameter SENDING OF REPORTS is allowed. If the parameter is not allowed. Traps do not usually disturb the functioning of the program producing them.

1148 EXCESSIVE TRAPS RNC disturbances (1000-1999) 3. After the fault has been repaired. change the alarm limit back to normal and re-enable the supervision. Cancelling No cancelling. or. 84 Id:0900d805805de168 DN99580853 Issue 08A . 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. 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.

A software fault is probable. 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. the memory is fragmented. If the total amount of free memory is small.RNC disturbances (1000-1999) 1165 BUFFER ALLOCATION FAILED 49 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. 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. Buffer reservation failure may prevent the execution of a task or make it slower. If a buffer reservation fails in connection with a critical task. the maintenance system restarts the computer. the computer probably has an insufficient memory capacity and should be replaced with one that has more capacity. it is recommended to inform your local Nokia DN99580853 Issue 08A Id:0900d805805de168 85 . if the requested buffer size indicated in the supplementary information field is large in comparison with the computer memory. and usually the memory state also returns to normal. In any case. Supplementary information fields 1 family identifier of the process whose buffer reservation failed process identifier of the process whose buffer reservation failed requested buffer size largest free buffer total amount of free memory 2 3 4 5 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.

on the division of free memory and the process families that have reserved memory the most.1165 BUFFER ALLOCATION FAILED RNC disturbances (1000-1999) Siemens Networks representative on the fault. i. Include information on the memory. Cancelling No cancelling.e. 86 Id:0900d805805de168 DN99580853 Issue 08A .

the 5-minute freezing period has finished before the log events of the previous 5-minute period are reported. 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. The counters of the freezing period in question will not be included to the following reporting period. because the counters or log events in question are lost from the files. Supplementary information fields 1 type of counters or logs lost: 01 02 03 04 2 MTP counters SCCP/TC counters MTP interval logs SCCP/TC interval logs file number of the counter or log file whose counters or logs were not reported. 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 I/O System in customer documentation). If the file number is not available. and thus the counters of the first reporting period are lost. but they are available with MML commands. the log events in question are not reported. If the alarm concerns counter reporting. the following two 30-minute freezing periods have passed during the report outputting. also check that MEAFIL is connected to a virtual data storage (VDS). that is. in DN99580853 Issue 08A Id:0900d805805de168 87 . In this case. The reason for the alarm may also be the overload of reporting. If the binary reports' logical files are connected to MEAFIL file. If the alarm concerns reporting of interval logs.RNC disturbances (1000-1999) 1169 FREEZING PERIOD OF SS7 REPORTING LOST 50 1169 FREEZING PERIOD OF SS7 REPORTING LOST Meaning Some of the counters or logs of the SS7 statistics are not reported.

88 Id:0900d805805de168 DN99580853 Issue 08A . OSN OSE.1169 FREEZING PERIOD OF SS7 REPORTING LOST RNC disturbances (1000-1999) which case. signalling points and/or SCCP subsystems from the statistics with the MML commands OSL. and possibly unnecesary reporting types with the MML commands OSM and OSG. In this case. reports are not outputted fast enough. DPC AND SIO SCCP/TC counters: SCCPSPA SCCPSPB SCCPSSA SCCPSSB SCCPLSSAVA SCCPLSSAVB SCCPSINGLA SCCPSINGLB TCAPPUA TCAPPUB TCAPTRANSA TCAPTRANSB MTP interval logs: MTPSLLOGA MTPSPLOGA SCCP interval logs: SCCPSPLOGA SCCPSGLOGA TCLOGA SCCPGTLOGA SCCP SIGNALLING POINT METERS SCCP SUBSYSTEM METERS SCCP LOCAL SUBSYSTEM AVAILABILITY SCCP SINGLE METERS TCAP PERFORMANCE AND UTILIZATION TC TRANSACTION METERS SIGNALLING LINK INTERVAL LOG REPORT SIGNALLING POINT INTERVAL LOG REPORT SCCP SIGNALLING POINT INTERVAL LOG REPORT SCCP SEGMENTATION AND REASSEMBLY ERRORS INTERVAL LOG REPORT TC INTERVAL LOG REPORT SCCP GT TRANSLATION ERRORS LOG REPORT Cancelling No cancelling. Logical file Measurement type ====================================================== ascii bin MTP counters: MTPSLAVAIA MTPSLAVAIB MTPSLPERFA MTPSLPERFB MTPSLUTILA MTPSLUTILB MTPSPSTATA MTPSPSTATB MTPSLSAVAA MTPSLSAVAB MTPOCTHSPA MTPOCTHSPB MTPOCTSIOA MTPOCTMATA MTPOCTSIOB MTPOCTMATB SIGNALLING LINK AVAILABILITY SIGNALLING LINK PERFORMANCE SIGNALLING LINK UTILIZATION SIGNALLING POINT STATUS SIGNALLING LINK SET AND ROUTE SET AVAILABILITY SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINT SIF AND SIO OCTETS HANDLED WITH SIO SIF AND SIO OCTETS HANDLED WITH OPC. decrease the report load by removing unnecessary signalling channels.

do not succeed from other computers. The computer unit has possibly lost the HMS line connection to other parts of the system. the administrative actions based on the use of HMS channel. Cancelling No cancelling. DN99580853 Issue 08A Id:0900d805805de168 89 . its isolation from the system or cancelling the isolation. 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. Supplementary information fields 1 transfer line of the HMS channel (0 or 1) which the HMS node of the computer unit has last tried to listen to Instructions No specific operating instructions.RNC disturbances (1000-1999) 1183 HMS LINE CONNECTION LOST 51 1183 HMS LINE CONNECTION LOST Meaning The HMS node of the computer unit has not received supervisory messages from either transfer line of the HMS channel for some time. In that case. such as restarting the computer unit.

You can check the supporting amount of the alarm with the MML command ARO. the device driver or the communication channel between them is faulty or overloaded.1186 NO RESPONSE TO HMN SUPERVISION RNC disturbances (1000-1999) 52 1186 NO RESPONSE TO HMN SUPERVISION Meaning The HMS node of the computer unit does not respond to supervision executed by the local device driver. The HMS node. It is likely that the computer unit cannot use communication and management services related to the HMS channel. Cancelling No cancelling. 90 Id:0900d805805de168 DN99580853 Issue 08A . Supplementary information fields Instructions No specific operating instructions. The alarm supports the activation of the automatic recovery for the object unit.

DN99580853 Issue 08A Id:0900d805805de168 91 . Signalling message units.RNC disturbances (1000-1999) 1192 SSCOP TRANSMIT BUFFER OVERFLOW 53 1192 SSCOP TRANSMIT BUFFER OVERFLOW Meaning The transmit buffer of SAAL. which are sent to SAAL. has filled up. The alarm may appear in the signalling link changeover situations. The signalling message transfer of concerned signalling link is disturbed. which is maintained by the SSCOP layer. Supplementary information fields 1 2 3 4 the external interface identifier of the signalling link the virtual path identifier of the signalling link the virtual channel identifier of the signalling link number of signalling units in transmit buffer Instructions The alarm requires no actions. This situation may be caused by the congestion in the signalling data transfer or failure in the SSCOP layer of SAAL. are lost. SAAL is able to handle normally only MTP-3 management messages. Cancelling No cancellation.

master node 03. plug-in unit position address restarted node.1196 HMS NODE RESTARTED RNC disturbances (1000-1999) 54 1196 HMS NODE RESTARTED Meaning HMS node has been restarted. It no other alarm related to this fault is on and if the disturbance appears frequently. see instructions on replacing plug-in units. however set them automatically back to the defined value. The system also updates the alarm situation of the plug-in unit displayed in the additional information in the alarm to correspond the actual situation. slave node 02. bridge node in TSS3 04. The possible values: 01. Supplementary information fields 1 2 3 4 5 type of the plug-in unit detecting the fault HMS number of the cabinet in which the plug-in unit is located HMS number of the subrack in which the plug-in unit is located PPA. replace the faulty plug-in unit indicated in the additional information of the alarm. The system will. The filtering time for the alarm inputs of the plug-in unit has been reset to zero. 92 Id:0900d805805de168 DN99580853 Issue 08A . Cancelling No cancelling. bridge node in TBUF Instructions Check if any other alarm related to this fault is on and follow the instructions of that alarm.

contact your local Nokia Siemens Networks representative. If the supervision of some computer units starts to fail.if the name is PUFFIL.TXT containing information on message connections was missing or corrupted. Save the corrupted file W0-ASWDIR/PUFFILGX. and it has taken automatic recovery measures by recreating the file from the beginning. NO RESPONSE TO UNIT SUPERVISION MESSAGE.RNC disturbances (1000-1999) 1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTED 55 1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTED Meaning This is an internal error in the Message Connection Management system. Usually the system is capable of recovering by itself from the error that caused the alarm.ERR The disturbance can be ignored if it occurs when a new system is being restarted for the first time. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or in the General Error Messages of System name of the corrupted file Instructions The name of the corrupted file is given in the supplementary information field 2. The message connection network has been recreated according to the connection rules in the TRYFIL file. In this case. The Message Connection Management system creates them. It is possible that some information on message connections has been lost.ERR. . The Message Connection Management system has detected that one of its parameter files is missing or corrupted. Supplementary information fields 1 general error message of the system. the files in question do not exist on the disk. but the reasons behind the error should be looked into. the file W0-ASWDIR/PUFFILGX. Cancelling No cancelling. The corrupted file has been saved as W0-ASWDIR/PUFFILGX. 2 DN99580853 Issue 08A Id:0900d805805de168 93 . indicated by the alarm 1010. and the error code is 56d (NO SUCH FILE).

exceptions made by the actors are always noticed.e. 94 Id:0900d805805de168 DN99580853 Issue 08A . infinite loops) or the total stopping of the actor is not detected and the recovery actions are not activated. Apart from the active supervision. It is means under actor possible that the supervision data table has filled up. The problem has no effect on the supervision already activated. Cancelling No cancelling. If the actor is not supervised actively. if the actor runs without problems the lack of active supervision is not a serious problem. all actors are supervised passively. the supervision data table is full. the erroneous behaving (e. Supplementary information fields 1 the DMX family identifier of an actor that has failed to register to the supervision Instructions If the alarm occurs. This that the actor supervisor (SVATOR) cannot take more actors the active supervision. Fill in a Failure Report and send it to your local Nokia Siemens Networks representative.g. However.1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION RNC disturbances (1000-1999) 56 1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION Meaning An actor has failed to register to the active supervision. List the content of the supervision data table with service terminal command: supervise -a all and attach it to the Failure Report. i.

The supervised unit is the object unit of the alarm and the supervising unit is the unit sending of the alarm. 2 3 DN99580853 Issue 08A Id:0900d805805de168 95 . These problems are caused because there have been message transfer errors during the distribution of working state and configuration data of the system to functional units. 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 cancellation. Supplementary information fields 1 first corrupted record in the SCDFLE file contains data of this type of unit this is the index of the unit in the first corrupted record amount of corrupted records Instructions Alarm does not require user actions.RNC disturbances (1000-1999) 1203 SCDFLE FILE INTEGRITY ERROR 57 1203 SCDFLE FILE INTEGRITY ERROR Meaning The working state and configuration data of the system in the supervised unit (any other computer unit but active maintenance computer) differs from the data in the memory of the supervising unit (active maintenance computer). This divergence of data may cause malfunctioning of the system and it slows or even prevent the automatic recovery actions after a failure of a unit.

which takes care of starting other actors.1204 WATCHDOG CAUSES UNIT RESTART RNC disturbances (1000-1999) 58 1204 WATCHDOG CAUSES UNIT RESTART Meaning A critical actor for the functioning of the unit has failed. Actor Supervisor (SVATOR) stops feeding the watchdog feeder actor and this will cause a unit restart. QXFPRB. 96 Id:0900d805805de168 DN99580853 Issue 08A . This kind of actors are e. Cancelling No cancelling.g. Supplementary information fields Instructions The alarm requires no actions because the coming unit restart solves the problem. which activates the recovery functions and DAQTOR.

the alarm is set because no route has been defined to the destination indicated by the AAL2 address. The NSAP address is BCD encoded (two digits in a byte). Supplementary information fields 1 reason for the alarm possible numerical values are: 1 unknown address 2 invalid address 3 own address is invalid or missing 2 type of the address possible numerical values are: 1 E.RNC disturbances (1000-1999) 1205 USER PLANE CONNECTION SETUP FAILURE 59 1205 USER PLANE CONNECTION SETUP FAILURE Meaning The RNC (Radio Network Controller) is setting up the user plane connection for a call between the RNC and the CN (Core Network) but the AAL2 signalling address (service end point address) does not match the one specified in the local system. In the case of transit functionality. The complete address is written into the log (examine the log file with the computer log handler extension of the service terminal) Instructions If the value of the supplementary information 1 is: DN99580853 Issue 08A Id:0900d805805de168 97 .164 2 NSAP 3 total length of the address 4-16 service end point address used RNC sets up the user plane of a connection (towards CN) using the service end point address. The E. In most cases. the address fits only partially in this supplementary information field.164 address contains one number in a byte. It may also be that the address is unspecified or invalid.164 or NSAP. The address format is either E.

2 3 Cancelling No cancelling. invalid address Check the configuration in the RNC and change it if necessary.1205 USER PLANE CONNECTION SETUP FAILURE RNC disturbances (1000-1999) 1 unknown address Compare the address in the alarm to the one specified locally (in the ATM Module). own address is invalid or missing Interrogate the ATM Module default parameters by giving the MML command WEI. Add or change the address depending on the situation. You can find it out by interrogating the default parameters with the MML command WEI. The new address will be in use after a while (approximately 5 minutes). Change the local address if it is incorrect. 98 Id:0900d805805de168 DN99580853 Issue 08A .

Otherwise. This data divergence can be caused by message transfer errors during the distribution of the working states to functional units. Supplementary information fields 1 working state of the supervised unit in the memory of the system maintenance unit working state of the supervised unit in the unit's own memory Instructions If the disturbance occurs frequently. 2 DN99580853 Issue 08A Id:0900d805805de168 99 . and it slows down or may even prevent the automatic recovery actions in the system. fill in a Problem Report and send it to your local Nokia Siemens Networks representative.RNC disturbances (1000-1999) 1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM 60 1207 UNITS WORKING STATE DATA CORRUPTED 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. no action is required. The system detects this divergence by itself and begins the actions in order to correct the problem. It may cause malfunctioning of the system. Cancelling No cancelling.

00 am. which have possibly been made have not been updated to the file. but in a possible restart situation the system will continue the measurement using the old parameters. contact your local Nokia Siemens Networks representative. The measurement continues using the changed parameters. Check the I/O-system's active alarms and follow those alarm instructions.1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED RNC disturbances (1000-1999) 61 1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED Meaning Handling of measurement definition file has failed. or the schedule is also updated to the disk every night at 01. The changes. but the parameters have not been updated to disk. so these updates could correct the problem. You can check its meaning by using the MML command T2C failed task: 01 Writing of measurement definition file failed 02 Passifying of measurement definition file failed specified reason for the error case shown in the third supplementary information field. Supplementary information fields 1 measurement identifier. Send the unit's logs. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or from General Error Messages of System 2 3 4 Instructions If the third supplementary information field has the value 01. If not (the disturbance still occurs). You can try to write on the disk again when the I/O-system has recovered by modifying the measurement schedule (T2M MML command). You can check its meaning by using the MML command T2C measurements object list identifier (from 1 to 999). This is a general error message of the system. This may be due to a temporary overload in the I/O-system. There may be a temporary overload in the I/O-system. This means that the schedule of the measurement may not be correct. operating 100 Id:0900d805805de168 DN99580853 Issue 08A . the measurement is continued. The wrong parameters are shown when interrogating the measurement parameters (T2I MML command). The third and fourth supplementary information fields show the reason for the failure.

This may be due to a temporary overload in the I/O-system. and yyy refers to the OID (second supplementary information field) value in the alarm. remove the measurement definition file (T2D MML command) which could not be passified by the system. DN99580853 Issue 08A Id:0900d805805de168 101 . The active alarms can be output by using the MML command AAP. Cancelling No cancelling. The logs can be output by using the service terminal commands ZGD and ZSL. The name of the file is AMEASxxx.yyy. where xxx refers to the MID value (first supplementary information field) in the alarm. If the third supplementary information field has value 02.RNC disturbances (1000-1999) 1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED system logs and active alarms to your Nokia Siemens Networks representative.

1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED RNC disturbances (1000-1999) 62 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED Meaning Outputting the statistical measurement report has failed. This is a general error message of the system. Send the unit's logs. if the measurement report is output. If the third supplementary information field has the value 02. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or from the General Error Messages of System 2 3 4 Instructions If the third supplementary information field has the value 01. The logs can be 102 Id:0900d805805de168 DN99580853 Issue 08A . You can check its meaning by using the MML command T2C the reason for failure in outputting of the report: 01 Buffer allocation failed 02 No data writing service provider 03 Error with data writing service provider specified reason when the third supplementary information field has value 03. Contact your local Nokia Siemens Networks representative. If this is continuous. The report of the measurement. which probably cannot be corrected without a software update. The active alarms can be output by using the MML command AAP. which has caused the alarm may disappear or. the data in it may be faulty. the service may be temporarily unobtainable. there is an error situation. operating system logs and active alarms to your Nokia Siemens Networks representative. 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 third and fourth supplementary information fields show the reason for the failure. there is an error situation which probably cannot be corrected without a software update. The logs can be output by using the service terminal commands ZGD and ZSL. Supplementary information fields 1 measurement identifier of the report. You can check its meaning by using the MML command T2C measurements object list identifier (from 1 to 999).

DN99580853 Issue 08A Id:0900d805805de168 103 . The active alarms can be output by using the MML command AAP. Cancelling No cancelling. 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 IHI) 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 instructions on I/O configuration handling.RNC disturbances (1000-1999) 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED output by using the service terminal command ZGD and ZSL. If the third supplementary information field has the value 03.

This is a general error message of the system. If the alarm reoccurs. If the second supplementary information field has value 01. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or from the General Error Messages of System Instructions If the first supplementary information field has a value other than 1000. Check the active alarms of the I/O system and follow those alarm instructions. Application name is the name of the VDS-0 device and <nnnn> is the new disk file size in kilobytes. Send the unit's logs. increase the file 2 3 104 Id:0900d805805de168 DN99580853 Issue 08A . The active alarms can be output by using the MML command ZAAP. operating system logs and active alarms to your Nokia Siemens Networks representative. you can check its meaning by using the MML command T2C. The second and third supplementary information fields show the reason for the failure. The problem may be temporary and the system will correct it. The logs can be output by using service terminal commands ZGD and ZSL. The report of the measurement that has caused the alarm may disappear. Supplementary information fields 1 measurement identifier of the report 1000 RNW measurement Other other measurement id reason for the data writing failure 01 error in I/O system 02 no response from I/O system 03 memory allocation failed specified reason for the error case shown in the second supplementary information field.1222 DATA WRITING VIA VDS DEVICE FAILED RNC disturbances (1000-1999) 63 1222 DATA WRITING VIA VDS DEVICE FAILED Meaning Data writing via the VDS device has failed. the I/O system may be overloaded. If the disturbance occurs repeatedly. and thus the report output fails. If the second supplemetary information field has value 01 or 02. contact your local Nokia Siemens Networks representative. the disk file space may have run out because the measurement is so big. Increase the measurement file size with MML command ZIFF:OMU:<application name>:SIZE=<nnnn>.

The current disk file size can be checked with the MML command ZIFI:OMU:<application name>. If the second supplemetary information field has value 03. operating system logs and active alarms to your Nokia Siemens Networks representative. DN99580853 Issue 08A Id:0900d805805de168 105 . Cancelling No cancelling. Send the unit's logs.RNC disturbances (1000-1999) 1222 DATA WRITING VIA VDS DEVICE FAILED size more. there is an error situation which probably cannot be corrected without a software update. Contact your local Nokia Siemens Networks representative. The active alarms can be output by using the MML command ZAAP. The logs can be output by using service terminal commands ZGD and ZSL.

Supplementary information fields 1 index of the MXU whose restarting caused restarting of the tributary unit Instructions The alarm requires no actions. 106 Id:0900d805805de168 DN99580853 Issue 08A . System restart will take place to recover from the situation if the MXU restarted is connected to tributary unit that is classified as system critical unit. Alarm is set concerning all of the tributary units connected to the restarted multiplexer.1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART RNC disturbances (1000-1999) 64 1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART Meaning This alarm is issued when the internal ATM connection management object notices an active multiplexer restart when the spare multiplexer cannot be taken into use. Occurence of this alarm leads to restarting of the object unit of the alarm. Cancelling No cancelling.

the system starts it automatically after a while (in less than one hour). In case the supervision of all units has been stopped the value is FFFF. Cancelling No cancelling. some library function call has failed 02 Faulty supervision from RUBBER (RUBBER hasn't got any supervision messages from RUMMAN within 5 minutes) physical address of the functional unit whose supervision has been stopped. Supplementary information fields 1 failure reason: 00 User has stopped the unit supervision 01 Unit supervision has been stopped because of a technical problem e.g. Instructions If the supervision has not been stopped by the user and if the disturbance occurs frequently. no action is required. fill in a Problem Report and send it to your local Nokia Siemens Networks representative. If the supervision is stopped by the user. Otherwise. or supervision is stopped by the user for some special purpose.RNC disturbances (1000-1999) 1228 UNIT SUPERVISION NOT FUNCTIONING 65 1228 UNIT SUPERVISION NOT FUNCTIONING Meaning Supervision of functional unit(s) is not functioning due to a technical or other problem. 2 DN99580853 Issue 08A Id:0900d805805de168 107 . but it slows down or may even prevent the automatic recovery actions of the unsupervised unit. The lack of supervision does not prevent normal operation of the system.

see instructions on replacing plug-in units. 108 Id:0900d805805de168 DN99580853 Issue 08A . All the information in the EHAT has been initialized back to default value. Cancelling No cancelling. that could cause the restart of EHAT and follow the instructions of that alarm. If no such alarm is on concerning this fault and if the disturbance appears frequently. plug-in unit position address of the EHAT plug-in unit Instructions Check if any other alarm is on concerning a fault. replace the faulty EHAT plug-in unit indicated in the additional information of the alarm.1232 EHAT RESTARTED RNC disturbances (1000-1999) 66 1232 EHAT RESTARTED Meaning EHAT plug-in unit has restarted. Supplementary information fields 1 2 3 HMS number of the cabinet in which the EHAT plug-in unit is located HMS number of the subrack in which the EHAT plug-in unit is located PPA. however set them immediately back to correspond to the actual situation. The system will. The systen corrects the situation by updating the external alarm situation and the alarm outputs state to correspond to the reality.

Supplementary information fields 1 reason for failure of 01 error in writing 02 error in writing 03 creation of hand the password validity time updating of the memory file of the disk file failed Instructions The alarm requires no actions. Cancelling No cancelling. The validity times of the passwords remain unchanged.RNC disturbances (1000-1999) 1234 UPDATE OF PASSWORD VALIDITY TIME FAILED 67 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. DN99580853 Issue 08A Id:0900d805805de168 109 .

txt cat /DSP/rmd_serv.txt In addition. 110 Id:0900d805805de168 DN99580853 Issue 08A . To gather more information about the nature of the problem. You can check the supporting amount of the alarm with the MML command ARO. the operation provided by DSP in question is not available. the following service terminal commands should be executed in the TPG/DMPG where the alarm was set: clog -sa cat /DSP/rmd_log. or the operation is unreliable.1239 DSP SUPERVISION FAILURE RNC disturbances (1000-1999) 68 1239 DSP SUPERVISION FAILURE Meaning An error in the functioning of a DSP has been detected by the supervision executed by Signal Processing Resource Management. As a result of this situation. computer logs from all ISU's/ICSU's shoud be collected. Supplementary information fields 1 cause of the alarm: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 no answer from DSP to a supervision inquiry message DSP stopped responding while service was being set up DSP detected a fatal error and requested recovery DSP failed while starting up Reconfiguring DSP to new service pool failed DSP restarted spontaneously Fatal error occurred while releasing DSP resources DSP set up service failed DSP_DEVICE error notification from DSP DSP device failed while starting up Reconfigure dsp pool with forced mode DSP global buffer was empty Deleted channel failed Server service restarted failed Invalid service pool from RM3 Instructions The alarm supports the activation of the automatic recovery for the object unit.

RNC disturbances (1000-1999) 1239 DSP SUPERVISION FAILURE Cancelling No cancelling. DN99580853 Issue 08A Id:0900d805805de168 111 .

erroneous IT message abnormal release of connection. as no acknowledgement has been received abnormal release of connection.1240 SCCP DISTURBANCE RNC disturbances (1000-1999) 69 1240 SCCP DISTURBANCE Meaning Report on SCCP disturbances. depending on the value of the first supplementary information field. Possible values are: 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D releasing connection failed. as the local subsystem has not responded to the connection request subsystem does not respond to local sending local subsystem has no counterpart sending a signalling message to the subsystem fails. as the subsystem has not enrolled for the service sending message to user has failed sending message to MTP has failed SCCP management could not locate the signalling unit being distributed sending signalling message to a subsystem fails. as the standard of the TCAP message is different from the TCAP version used by the subsystem message is rejected because its priority is lower than the overload level of the MTP 0E 2 network indicator. in the following manner: 01-06 07-08 own signalling point where the error was detected own signalling point to whose subsystem the local sending was attempted 112 Id:0900d805805de168 DN99580853 Issue 08A . the time supervision of the passive receiving time (IAR) has expired abnormal release of connection. time supervision of the hand has expired establishing connection failed. Supplementary information fields 1 identifier of disturbance. The signalling point code is interpreted. the time supervision of the connection establishment (CONN_EST) has expired establishing connection failed. Possible values are: 00 04 08 0C international network 0 international network 1 national network 0 national network 1 3 local signalling point code.

whose data is being distributed subsystem which send the message remote end subsystem. depending on the value of the first supplementary information field. The log contains more DN99580853 Issue 08A Id:0900d805805de168 113 . the value in the field is FF.RNC disturbances (1000-1999) 1240 SCCP DISTURBANCE 09-0E 4 own signalling point local subsystem number. The subsystem number is interpreted. in the following manner: 01-06 07-08 09-0A 0B 0C 0D 0E signalling point of the remote end signalling connection part object signalling point of local sending. If the subsystem number is not known. If the local subsystem is not known. in the following manner: 01-06 07-08 09-0A 0B 0C 0D 0E local subsystem. in the following manner: 01-06 07-08 09-0A 0B 0C 0D 0E remote end subsystem of the signalling connection object subsystem of local sending. sending the SCCP management message to which was attempted subsystem which has send a TCAP message remote end subsystem to which sending a message was attempted 7 reference number in the DX log. The subsystem number is interpreted. depending on the value of the first supplementary information field. whose data is being distributed signalling point from which the message came local subsystem to which sending a message was attempted local subsystem to which sending an SCCP management message was attempted signalling point from which a TCAP message was received signalling point to which sending a TCAP message was attempted 6 remote subsystem number. The signalling point code is interpreted. sending the message to which was attempted SCCP management subsystem. the value in the field is FF. releasing or establishing connection to which failed local subsystem to which local sending was attempted (important subsystem) local subsystem to which local sending was attempted local subsystem from which the message was received SCCP management subsystem local subsystem to which sending a TCAP message was attempted local subsystem from which a message was received 5 remote signalling point code. depending on the value of the first supplementary information field.

114 Id:0900d805805de168 DN99580853 Issue 08A . ZGSC. Enclose the printouts output with the service terminal commands ZSCFE. Otherwise fill in a Problem report and send it to your local Nokia Siemens Networks representative. no actions are required from the user.1240 SCCP DISTURBANCE RNC disturbances (1000-1999) information on the error. Instructions If the alarm is given infrequently and the value of the error code given in the first supplementary information field is 1-6. If the reference number is not used in the log. the value of the field is 0. Cancelling No cancelling. and ZSL in the Problem report.

There is no analysis for this nature of address indicator in the GANFIL unknown numbering plan. Supplementary information fields 1 error code. A message that contains the global title in question will not get to its destination. There is no analysis for this encoding scheme in the GANFIL unknown global title indicator. Possible values are: 01 unknown nature of address indicator. There is no analysis for this global title indicator in the GANFIL GANFIL contains no analysis for the first digit of the address GANFIL contains no analysis for the second digit of the address GANFIL contains no analysis for the third digit of the address GANFIL contains no analysis for the fourth digit of the address GANFIL contains no analysis for the fifth digit of the address GANFIL contains no analysis for the sixth digit of 02 03 04 05 06 11 12 13 14 15 16 DN99580853 Issue 08A Id:0900d805805de168 115 . The global title analysis was not completed because the analysed number was not found in the analysis data.RNC disturbances (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR 70 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR Meaning Report on the analysis disturbances of the SCCP global title translation. The alarm may have some effect on the traffic capacity of the system. There is no analysis for this translation type in the GANFIL unknown encoding scheme. There is no analysis for this global title indicator in the GANFIL unknown global title standard. There is no analysis for this numbering plan in the GANFIL unknown translation type.

1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR RNC disturbances (1000-1999) the address 17 GANFIL contains no analysis for the seventh digit of the address GANFIL contains no analysis for the eighth digit of the address GANFIL contains no analysis for the ninth digit of the address GANFIL contains no analysis for the tenth digit of the address GANFIL contains no analysis for the 11th digit of the address GANFIL contains no analysis for the 12th digit of the address GANFIL contains no analysis for the 13th digit of the address GANFIL contains no analysis for the 14th digit of the address GANFIL contains no analysis for the 15th digit of the address GANFIL contains no analysis for the 16th digit of the address GANFIL contains no analysis for the 17th digit of the address GANFIL contains no analysis for the 18th digit of the address GANFIL contains no analysis for the 19th digit of the address GANFIL contains no analysis for the 20th digit of the address GANFIL contains no analysis for the 21st digit of the address GANFIL contains no analysis for the 22nd digit of the address GANFIL contains no analysis for the 23rd digit of 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 116 Id:0900d805805de168 DN99580853 Issue 08A .

the numbering plan and the encoding scheme 04 global title contains the translation type. the encoding scheme or the nature of address indicator. the encoding scheme and the nature of address indicator 05-15 global title does not contain the translation type. possible values are: 01 02 ITU-T 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 02 03 global title contains only the nature of address indicator global title contains only the translation type global title contains the translation type. the numbering plan. the numbering plan. 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.112-1992 there are values defined for the translation type with the third supplementary field value 02 (ANSI) and with the fourth DN99580853 Issue 08A Id:0900d805805de168 117 . 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 numbering plan. The translation type is interpreted in the following manner when the value in the third supplementary field is 01 (ITU-T): 00 FF translation type not in use global title does not include translation type In the national specification ANSI T1. the encoding scheme or the nature of address indicator.RNC disturbances (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR the address 28 GANFIL contains no analysis for the 24th digit of the address 2 3 record number of the GANFIL global title standard.

odd number of digits BCD..E. The encoding scheme is encoded with the least meaningful bits 1-4 in the following manner: 0000 0001 0010 0011 : 1110 1111 unknown BCD.E.211) mobile telephone network numbering plan (E.163) reserved for future use data network numbering plan (X. These values of the translation type can be analysed in the normal way.121) telex network numbering plan (F.212) ISDN/mobile telephone network numbering plan (E. Possible values are: 01 02 03 04 05 : FE FF subscriber number reserved for national use national meaningful number international number reserved for future use reserved for future use nature of address indicator not included in global title 8-15 address information from the global title of the SCCP message so that.69) ship telephone network numbering plan (E. the number 12345 is encoded 12 34 5F FF .214) reserved for future use reserved for future use numbering plan not included in global title nature of address indicator from the global title of the SCCP message.1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR RNC disturbances (1000-1999) supplementary field value 02. but they do not cause special procedures in the system 6 numbering plan and encoding scheme from the global title of the SCCP message.210. for example. 118 Id:0900d805805de168 DN99580853 Issue 08A . even number of digits reserved for future use reserved for future use encoding scheme not included in global title The numbering plan is encoded with the most meaningful bits 5-8 in the following manner: 0000 0001 0010 0011 0100 0101 0110 0111 1000 : 1110 1111 7 unknown ISDN/telephone network numbering plan (E.164..

Cancelling No cancelling. you can create it with the MML command NBC. If a suitable result record is not found. DN99580853 Issue 08A Id:0900d805805de168 119 . find out the correct analysis result to which the new analysis will be connected. If the analysis has already been created. 3. a wrong title can cause the alarm in question. it will not be set in the genuine fault situation either. You can check the analysis result records with the MML command NAI. If there is no analysis. Check whether there should be a global title analysis created for the global title indicated in the disturbance. You can check the existing analyses with the NBI command of the Global Title Analysis Handling MML (GTAHAN). fill in a Problem report and send it to your local Nokia Siemens Networks representative. this alarm can be blocked with the MML command ABB. If these actions do not help. the error may be a file error. 4. 5. if necessary. As in the short message service the subscriber gives the title. you can create it with the MML command NAC. 2. Note that if the alarm is blocked. 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.RNC disturbances (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR Instructions 1. Before creating the analysis. Note that in the MML command the given root parameters must be the same as in the alarm. If there is a disturbingly high number of alarms in a situation like this.

A message that contains the global title in question will not get to its destination. The global title indicator is interpreted in following manner when the value in the third supplementary field is 01 (ITU-T): 01 02 03 04 global title global title global title plan and the global title contains contains contains encoding contains only the nature of address indicator only the translation type the translation type. 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. 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) translation of global title contains an unknown destination point code translation of global title contains an unknown subsystem number translation of global title contains a reference to a record of the Global Title Modification File (GTMFIL). possible values are: 01 02 ITU-T ANSI 4 global title indicator in the global title of an SCCP message. the numbering 120 Id:0900d805805de168 DN99580853 Issue 08A . When modifying the global title using the values of this record. Supplementary information fields 1 error code.1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR RNC disturbances (1000-1999) 71 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR Meaning Report on the output disturbances of the SCCP global title translation.g. the result is an erroneous global title (e. the numbering scheme the translation type. The alarm may have an effect to the traffic capacity of the system. too many digits are added or removed) 02 03 04 2 3 record number of GTRFIL global title standard.

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.RNC disturbances (1000-1999) 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR plan.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. 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 encoding scheme is encoded with the least meaningful bits 1-4 in the following manner: 0000 0001 0010 0011 : 1110 1111 unknown BCD. These values of the translation type can be analysed in the normal way. even number of digits reserved for future use reserved for future use encoding scheme not included in global title The numbering plan is encoded with the most meaningful bits 5-8 in the following manner: 0000 0001 unknown ISDN/telephone network numbering plan (E. the encoding scheme and the nature of address indicator 05-15 global title does not contain the translation type. These global title indicator values have not been defined in the ANSI recommendations 5 translation type from the global title of the SCCP message.E. the encoding scheme or the nature of address indicator.163) DN99580853 Issue 08A Id:0900d805805de168 121 . the numbering plan. but they do not cause special procedures in the system 6 numbering plan and encoding scheme from the global title of the SCCP message.164. odd number of digits BCD. the numbering plan. the encoding scheme or the nature of the address indicator. The translation type is interpreted in the following manner when the value in the third supplementary field is 01 (ITU-T): 00 FF translation type not in use global title does not include translation type In the national specification ANSI T1.

Instructions 1. 122 Id:0900d805805de168 DN99580853 Issue 08A . Possible values are: 01 02 03 04 05 : FE FF subscriber number reserved for national use national meaningful number international number reserved for future use reserved for future use nature of address indicator not included in global title 8-15 address information from the global title of the SCCP message so that. 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. 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.212) ISDN/mobile telephone network numbering plan (E.1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR RNC disturbances (1000-1999) 0010 0011 0100 0101 0110 0111 1000 : 1110 1111 7 reserved for future use data network numbering plan (X. If the value of the first supplementary field is 01.121) telex network numbering plan (F.211) mobile telephone network numbering plan (E. If the alarm is set only in one computer unit.69) ship telephone network numbering plan (E.210.. the disturbance may be caused by a file error. for example. Then recreate them with the MML commands NAC and NBC. If loading the file does not correct the situation.E. a unit restart or switchover may correct the situation. Note that removing the result may cause an outage in the traffic.214) reserved for future use reserved for future use numbering plan not included in global title nature of address indicator from the global title of the SCCP message. If loading the files does not help. 2. use the NBI command of the Global Title Analysis Handling MML (GTAHAN) to check to which result the analysis in question should lead. If the value of the first supplementary field is 02. find out to which signalling point the analysis in question should lead and use the MML command NAM to correct the signalling point code. remove the analysis in question and the result with the MML commands NBD and NAD.. the number 12345 is encoded 12 34 5F FF .

find out which subsystem should be in the result and correct it with the MML command NAM. Cancelling No cancelling. the disturbance may be caused by a file error. if necessary. If the value of the first supplementary field is 04. make corrections with the NAM and NAS commands. If the value of the first supplementary field is 03. 4. use the commands NAI and NAX of the Global Title Result Handling MML (GREHAN) to check the global title information and.RNC disturbances (1000-1999) 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR 3. If loading the file does not correct the situation. 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. DN99580853 Issue 08A Id:0900d805805de168 123 .

1244 RUNNING OUT OF MESSAGE BUFFERS RNC disturbances (1000-1999) 72 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. give the service terminal commands 124 Id:0900d805805de168 DN99580853 Issue 08A . In this case. 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. 1. The latter one means a wrong dimensioning of the parameters. When there are no free message buffers. To get the information on the usage of message buffers. The alarm limit is usually set so low that the alarm indicates a critical reduction in the amount of free message buffers. or give the dmxshow command on the console of the computer. To get the message buffer usage information. please attach the printouts of the commands mentioned below. reservation of a message fails and this may disturb the functioning of the computer. If the situation recurs. because it uses messages and it could even worsen the situation. start a telnet session for the computer that is given as the object unit of the alarm. Supplementary information fields 1 size of message buffers in the message size class which is running out of message buffers number of messages allocated in the message size class number of free messages in the message size class 2 3 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. As a precautionary act it is advisable to collect some information in case the computer goes to a faulty state or gets restarted. 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. A remote session to the computer (established with the service terminal command ZRS or with the MML command ZDDS) should be avoided.

To display alarm history of the current date concerning the computer.RNC disturbances (1000-1999) 1244 RUNNING OUT OF MESSAGE BUFFERS dmxshow -s and dmxshow -m Command dmxshow -a or dmxshow -A should not be used because it heavily consumes the resources of the computer. give the MML command ZAHP:<unit_type>. DN99580853 Issue 08A Id:0900d805805de168 125 .<unit_index>. give the service terminal command clog -s -a 3. Cancelling No cancelling. To display the computer log. 2.

1246 RESTART OF LEAF UNIT RNC disturbances (1000-1999) 73 1246 RESTART OF LEAF UNIT Meaning Message connections between the system maintenance computer and a center node have gone down. Supplementary information fields 1 2 Instructions The alarm requires no actions. each leaf node of the center node will be restarted. Because of this. Cancelling No cancelling. unit type of the center computer unit index of the center computer 126 Id:0900d805805de168 DN99580853 Issue 08A .

This strategy is followed until the dumping is completed successfully. Supplementary information fields 1 database index. DN99580853 Issue 08A Id:0900d805805de168 127 .e. Cancelling No cancelling. The format of the value is hh:mm 2 3 4 Instructions The alarm requires no actions. i. The dumping is now started with an option to prevent transactions when overloading occurs. 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.RNC disturbances (1000-1999) 1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE 74 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. database name and database occurrence database name number of database occurrence how much late the disk copy is from the state in memory.

check the quality of the connection. 128 Id:0900d805805de168 DN99580853 Issue 08A . but it can also occur in data transmission connections of poor quality. and the condition of the equipment. not in use) type of the channel link set: 00 01 02 03 primary rate access channel link set subscriber module (SUB) channel link set exchange terminal (ET) channel link set functional unit channel link set 4 number of the D-channel's PCM Instructions The alarm requires no actions. The alarm usually occurs in connection with unit restarts. during which some information may have been lost.1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT RNC disturbances (1000-1999) 75 1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT Meaning A connection has been re-established on the D-channel. Supplementary information fields 1 2 number of the channel link set (D-channel) D-channel index within the channel link set: 00 01 3 primary channel backup channel (in primary rate access only. Cancelling No cancelling. If the alarm keeps recurring.

fill in a Problem Report and send it to your local Nokia Siemens Networks representative. DN99580853 Issue 08A Id:0900d805805de168 129 .RNC disturbances (1000-1999) 1258 ERROR IN SPARE UNIT UPDATE 76 1258 ERROR IN SPARE UNIT UPDATE Meaning An error has occured in a spare unit update procedure. Supplementary information fields 1 error status given by the process family that has first recognized an error in the spare unit update procedure. Data in the spare unit is not consistent with the working unit. If the problem recurs. Cancelling No cancelling. You can check the supporting amount of the alarm with the MML command ARO. You can check its meaning in General Error Messages of System family identifier of the process family that has first recognized an error in the spare unit update procedure process identifier of the process that has first recognized an error in the spare unit update procedure 2 3 Instructions The alarm supports the activation of the automatic recovery for the object unit. As a consequence of this alarm. the spare unit is restarted by the recovery system in order to recover from the data inconsistency.

The object unit of the alarm is the unit which received the corrupted frame. Supplementary information fields 1 2 3 type of the unit from which the broken frame came index of the unit from which the broken frame came virtual channel identifier of the channel from which the broken frame came the internal service category of the failed channel. if it is the spare unit of a 2N pair the index of the active MXU between the SFU and the unit which detected the broken frame. The field may have the following values: RT nRT 5 real-time non-real time 4 the type of the active MXU between the SFU and the unit which detected the broken frame. If the unit which detected the broken frame is directly connected to the SFU. e. this disturbance was set immediately after the broken frame had been received count of the broken frames with the same status received during 9 130 Id:0900d805805de168 DN99580853 Issue 08A . which handles message traffic between computers (DMX and Chorus-based computers. The possible values for the field are hardware-dependent and only for internal use 00 indicates that the sdu contains incorrect header information. respectively) has received a broken AAL5 frame. If the unit which detected the broken frame is directly connected to the SFU. if it is the spare unit of a 2N pair the status received from the AAL5 Segmentation And Reassembly sublayer (SAR). If the value is zero. this field indicates the index of the unit itself or that of its active unit.g. this field indicates the type of the unit itself or that of its active unit.1269 AAL5 FRAME CORRUPTED RNC disturbances (1000-1999) 77 1269 AAL5 FRAME CORRUPTED Meaning The post office. that the sender address differs from the target channel endpoint address 6 7 8 length of the observation period in hundredths of a second.

Replace the suspected plug-in unit. In this case the problem can be solved only by removing the source of the disturbance. If replacing the plug-in unit does not help. proceed to the next step. If the above processes do not help.RNC disturbances (1000-1999) 1269 AAL5 FRAME CORRUPTED the last observation period 10 11 total count of the broken frames on the channel number of the AAL5 errors that occurred between the previous alarm 1269 or alarm 1285 and this alarm Instructions Usually the disturbance requires no actions. 2. 3. Run the diagnosis for the suspected unit. Check the physical connections of the plug-in units. If the problem persists. Among the object units of the alarm and the units stated in the supplementary information fields 1 and 2 of the alarm. Change the unit state to 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. If the problem is not in the cabling. See Instructions for Replacing Plug-in Units. Check that the cables are correctly in place and that a correct cable type has been used. 4. Proceed in the following way to diagnose and locate the fault: 1. the object unit mentioned most often is the suspected unit. It only informs the user about temporary problems in the message transmission system. fill in a Problem Report and send it to your local Nokia Siemens Networks representative. DN99580853 Issue 08A Id:0900d805805de168 131 . Check the cabling of the suspected unit. then it is most probably due to faulty hardware. proceed to the next step. 5. The cause of the alarm can be an external disturbance conducted through the power supply.

1269 AAL5 FRAME CORRUPTED RNC disturbances (1000-1999) Cancelling No cancelling. 132 Id:0900d805805de168 DN99580853 Issue 08A .

application programs in active OMU are asked for permission to execution 02 03 04 User originated forced system restart System restart caused by failure of a system critical unit System restart caused by failure of a system critical unit. If active system maintenance unit (OMU) participates in restart. a soft switchover (no restart to new active unit) is performed. Former active unit ends up in TE state. Active OMU is included in restart User originated controlled switchover where a working unit is replaced by a hot standby unit without standby restart.RNC disturbances (1000-1999) 1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM 78 1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM Meaning Trial configuration has been cancelled by system due to some critical unit failure of the original system. The former active unit ends up in TE state 08 Caused by a fault observed in an active unit. After the canceling. Diagnostics are activated if unit can be DN99580853 Issue 08A Id:0900d805805de168 133 . If a hot standby exists. The active unit is replaced by a standby unit even if the standby is in TE or SEOU state. Supplementary information fields 1 the computer address of the functional unit from where the trial cancelling originated the identifier of the process family that originated the cancelling the recovery action. a failed critical unit of the original system will be replaced with the same type unit which located in former trial system. Active unit is replaced with hot standby unit. The action taken by recovery is one from the list below: 01 User originated controlled system restart. Application programs are asked for permission to execution 2 3 05 06 or 07 Caused by a unit found being in an inappropriate state. The former active unit ends up in SP state.

e. the standby unit is also restarted for synchronization (file and code consistency) reasons A unit is restarted in order to recover from a disturbance.1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM RNC disturbances (1000-1999) diagnosed 09 or 0A Caused by an active unit gone inoperative due to e.g. disturbed unit ends up in SP state and is restarted User originated forced switchover where active unit is replaced by a standby in SP state.g. Application programs are asked for permission to execute it User originated forced restart of unit Caused by restart of an active unit. critical process family failure. Active unit is replaced by standby in SP state.g.g. due to power failure 0C 0D 0E 0F 10 11 12 13 14 15 16 or 17 A failed unit is put to TE state. If a hot standby exists. Active unit is replaced by a hot standby. former active unit ends up in SP state Caused not by a fault but a disturbance in operation of unit. e. disturbed unit ends up in TE state 0B Caused by an active unit making a spontaneous restart. a critical application failing due to overload. Application programs are asked for permission to execution State change of unit requested by system's supervision User originated forced working state change of unit An active unit is put to TE state after it has gone inoperative. a soft switchover (no restart to new active unit) is performed. Active unit is replaced by a hot standby. a power failure. in operation User originated controlled state change of unit. Diagnostics are activated 18 N+1 replaceable unit is put to WO state by system's resource monitoring N+1 replaceable unit is is put to SP state by system's 19 134 Id:0900d805805de168 DN99580853 Issue 08A . disturbed unit ends up in state SP and is restarted User originated controlled restart of unit. e.

Unit may not belong to BASE of either side Functional unit is moved forced from system to other by user. Unit may not belong to CORE of either side. The unit has failed but remains in use due to overall situation in network element Functional unit is added or removed to/from network element configuration by user System cancels trial configuration due to critical unit failure on original System Trial configuration is created controlled by user. CORE or BASE Trial configuration is created forced by user. CORE or BASE by user. States of units participating are not restricted 1C 22 23 24 25 26 27 28 29 2A 2B 2C 4-6 the alarm numbers of the first alarms on the basis of which the cancelling was activated.RNC disturbances (1000-1999) 1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM resource monitoring 1A 1B Specific functional unit status bit is set for unit by user Specific functional unit status bit is cleared from unit by user Functional unit gets FLTY status on. Initial configuration can be defined to be OMU. Application programs may not prevent the move The units carrying traffic are moved controlled from system to system (cutover of traffic) by user The units carrying traffic are moved forced from system to system (cutover of traffic) by user. DN99580853 Issue 08A Id:0900d805805de168 135 . CORE or BASE by user The configuration on trial side made in create can be expanded or reduced to OMU. In case the trial cancelling was not caused by an alarm. Application programs may not prevent the cutover The configuration on trial side made in create can be expanded or reduced to OMU. Initial configuration can be defined to be OMU. CORE or BASE Trial configuration is cancelled by user Functional unit is moved controlled from system to other by user.

136 Id:0900d805805de168 DN99580853 Issue 08A .1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM RNC disturbances (1000-1999) the value of the field is FFFF Instructions The alarm requires no actions. Cancelling No cancelling.

So when this alarm is set by the S3CMAN (SCTP association manager) program block. Possible values are: 01 02 03 04 05 06 07 08 09 0A 0B 0C unsupported M3UA version in M3UA message header M3UA draft version used in message differs from configured the traffic handling mode in M3UA message does not match with the configured one the routing context value in M3UA message does not match with the stored one no matching configured routing key was found for the routing key found in REGREQ message an unsupported parameter was found inside the routing key parameter in REGREQ message registration status in REGRSP is not 0 the local routing key identifier in REGRSP differs from that one that was sent in REGREQ there is no space for the new ASP in SGWFIL file there is no space for the new ASP in S3WORK file a mandatory parameter is missing in M3UA message a M3UA message is received that is not in accordance with the role specified in the association set. Other reason for the alarm is the insufficient resources. The ASP/SGP is activated by the exchange of ASPSM (ASP State Maintenance). If none of the ASPs in the specified association set in the 4th supplementary information field become active. 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. such as. the receiving of ASPUP. something has probably gone wrong during that ASP message exchanging. RKM (Routing Key Management) and ASPTM (ASP Traffic Maintenance) messages between the two M3UA endpoints. ASPAC. Supplementary information fields 1 type of the ASP activation failure. shown by ZOYI MML command. it means that the whole Application Server or Signalling Gateway is not available to this network element. REGREQ at the ASP even if only the SG is prepared to receive them DN99580853 Issue 08A Id:0900d805805de168 137 . such as.RNC disturbances (1000-1999) 1273 ASP ACTIVATION FAILED 79 1273 ASP ACTIVATION FAILED Meaning The activation of the ASP (Application Server Process) or SGP (Signalling Gateway Process) has not succeeded. Otherwise the signal transmission capacity may only be somewhat decreased. an insufficient amount of records in work files which prevents a new ASP to be activated. The 2nd and 3rd supplementary information fields show the ASP message at which the ASP activation failed.

the possible values are: 01 04 ASP Up (ASPUP) ASP Up Acknowledgement (ASPUP ACK) When the 2nd supplementary information field is 04. 0FFFF if not known when an inconsistent parameter value is included in the M3UA message. Possible values are dependent on the preceding supplementary information field: When the 2nd supplementary information field is 03. for ex. Possible values are: 03 04 09 ASP State Maintenance (ASPSM) Messages ASP Traffic Maintenance (ASPTM) Messages Routing Key Management (RKM) Messages 3 message type of M3UA message.. this supplementary information field shows that inconsistent parameter value. 02 means m3ua draft version. 04 means routing context. 03 means traffic handling mode. which has the inconsistent value is deduced from the value of the 1st supplementary information field: 01 means m3ua version. for ASP the state of which is not inactive the outbound stream count in the communication up notification is less than was ordered in the associate primitive 2 message class of M3UA message. 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.1273 ASP ACTIVATION FAILED RNC disturbances (1000-1999) 0D 0E 0F 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 ASPAC (ASP Active) message was received for the ASP in wrong state. The parameter. 6 138 Id:0900d805805de168 DN99580853 Issue 08A . the possible values are: 01 03 ASP Active (ASPAC) ASP Active Acknowledgement (ASPAC ACK) When the 2nd supplementary information field is 09. Value 0FFFFFFFF means that this field is not applicable for the alarm the value of the parameter. the possible values are: 01 02 4 5 Registration Request (REG REG) Registration Response (REG RSP) association set to which the ASP belongs.

The version that the peer M3UA is using is specified by the 5th supplementary information field. Check whether it is possible to configure the peer M3UA to use the supported version. The configured M3UA draft version is also specified in the 6th supplementary information field. in which the M3UA draft version was found is specified in the 2nd and 3rd supplementary fields. 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. 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 version that is supported is specified by the 6th supplementary information field. for ex. which is different than the one configured at this network element in the association set specified in the 4th supplementary information field. If the configured M3UA draft version needs to be modified in this network element. The M3UA message. If the value of the 1st supplementary information field is 02: The peer M3UA is using M3UA draft version. The M3UA draft version that the peer M3UA is using is specified in the 5th supplementary information field. DN99580853 Issue 08A Id:0900d805805de168 139 . use ZOYM MML command and give the association set and the M3UA draft version as the parameters. the field is not applicable with the alarm 8 the identifier that unambiguously identifies the ASP. Possible values are: 06 0207 020A 020B 0200 0208 0212 0FFFF Routing Context Routing Key Local_Routing Key Identifier Destination Point Code Network Appearance Registration Result Registration Status there is no missing parameter. possible values are 07 or 09.RNC disturbances (1000-1999) 1273 ASP ACTIVATION FAILED Value 0FFFFFFFF means that this field is not applicable for the alarm 7 the parameter tag of the missing parameter..

in which the traffic handling mode was included is specified in the 2nd and 3rd supplementary fields. 2) ZDFD:CM.N. 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. If that peer M3UA is operating in the Nokia Siemens Networks network element. when handling the REGREQ message.N.0:A79. The network appearance value included in REGREQ message is specified 140 Id:0900d805805de168 DN99580853 Issue 08A . 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. Try to find out why the peer M3UA does not use the correct routing context value.. In the problem report include this alarm and the printouts of following MML commands ("CM. fill in a Problem Report and send it to your local Nokia Siemens Networks representative. The M3UA message. It is also possible that there is no routing context value stored in this network element. 3) ZDFD:CM. The value of the routing context included in the M3UA message is specified in the 5th supplementary information field. The routing key here refers to the network appearance and the destination point code (DPC). The M3UA message. in which the routing context 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.. 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.. for ex. The value of the traffic handling mode included in the M3UA message is specified by the 5th supplementary information field.1273 ASP ACTIVATION FAILED RNC disturbances (1000-1999) The configured traffic handling mode value is also specified in the 6th supplementary information field.0:AF3. use the ZOYM MML command and give the association set and the correct traffic handling mode as the parameters. The routing context value stored at this network element is specified in the 6th supplementary information field.0" in the following commands refer to active central memory): 1) ZOYI::A. If the value needs to be modified at this network element... which means that the routing key registration was not done.

check that the M3UA based link set is configured to the right signalling point at this network element. If the value needs to be modified at this network element. DN99580853 Issue 08A Id:0900d805805de168 141 . If the network appearance value is correct. 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. with ZNLC MML command. 3) Change the state of the corresponding M3UA based link to AV-EX. If the routing key registration is turned off.RNC disturbances (1000-1999) 1273 ASP ACTIVATION FAILED in the 5th supplementary information field and the DPC included in REGREQ message is specified in the 6th supplementary information field. The status value that is returned by the peer M3UA is specified by the 5th supplementary information field. and at this network element modify the registration_request parameter to value "NO" in the association set. with ZNLC MML command. 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. 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. 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. 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. 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. use ZOYM MML command and give the association set and the correct network appearance value as the parameters. If not do not use routing key registration at both ends if possible. Check whether it is possible to configure the peer M3UA to use only network appearance and DPC as a routing key. 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. 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.

3) Change the state of the corresponding M3UA based link to AV-EX. with ZNLC MML command. as follows: 1) Change the state of the corresponding M3UA based link to UA-INU. use ZOYM MML command and give the association set and the correct network appearance value as the parameters to the ZOYM MML command. If the value needs to be modified at this network element. and at this network element modify the registration_request parameter to value "NO". 2) Change the registration_request parameter giving the association set specified in the 4th supplementary 142 Id:0900d805805de168 DN99580853 Issue 08A . 08 (insufficient resources): Do not use routing key registration at both ends if possible. with ZNLC MML command. do not use routing key registration at both ends if possible. 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. with ZNLC MML command. When the 5th supplementary information field is 01 (error-unknown). If so check that the network appearance value configured in the association set specified by the 4th supplementary information field is correct. 06 (cannot support unique routing). If not. 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. 07 (routing key not currently provisioned). If the peer M3UA does not currently support network appearance and DPC as a routing key. use ZOYM MML command and give the association set and the correct network appearance value as the parameters to the ZOYM MML command. and at this network element modify the registration_request parameter to value "NO". If the value needs to be modified at this network element. check whether it is possible to configure the peer M3UA as such. 05 (permission denied). as follows: 1) Change the state of the corresponding M3UA based link to UA-INU.1273 ASP ACTIVATION FAILED RNC disturbances (1000-1999) 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.

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.RNC disturbances (1000-1999) 1273 ASP ACTIVATION FAILED information field and the new value for registration_request parameter as the parameters in ZOYM MML command. 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. as follows: 1) Change the state of the corresponding M3UA based link to UA-INU. 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. If the peer M3UA is operating in the Nokia Siemens Networks network element. 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 peer M3UA does not currently support network appearance and DPC as a routing key. 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 value needs to be modified at this network element. In the problem report include this alarm and printouts of following DN99580853 Issue 08A Id:0900d805805de168 143 . check if it is possible to configure the peer M3UA such. If not. and in this network element modify the registration_request parameter to value "NO". 3) Change the state of the corresponding M3UA based link to AV-EX. with ZNLC 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). do not use routing key registration at both ends if possible. fill in a Problem Report and send it to your local Nokia Siemens Networks representative. 3) Change the state of the corresponding M3UA based link to AV-EX. with ZNLC MML command.

. If the value of the 1st supplementary information field is 0B: A mandatory parameter is missing in a M3UA message.. 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. 6th supplementary information field shows the unit.0:A79.0:A79.N.0:AF3.N. At the same time as the alarm logs are written: first with the same log reference as in the 144 Id:0900d805805de168 DN99580853 Issue 08A .N. 3) ZDFD:CM.. you have to change the role as follows: 1) Change the state of the corresponding M3UA based link to UA-INU.N.0" in the following commands refers to active central memory): 1) ZOYI::A. 3) ZDFD:CM.N. 3) Change the state of the corresponding M3UA based link to AV-EX. with the ZNLC MML command.. In the problem report include this alarm and printouts of following MML commands ("CM.. If the value of the 1st supplementary information field is 0C: Check whether the role specified in the 4th supplementary information field is correct.. from which communication up was received.0" in the following commands refer to active central memory): 1) ZOYI::A. 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. If the value of the 1st supplementary information field is 0D: The The the two 5th supplementary information field shows the log reference. 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 not.0" in the following commands refer to active central memory): 1) ZOYI::A. In the problem report include this alarm and printouts of following MML commands ("CM.0:AF3. 2) ZDFD:CM.N. The parameter tag of the missing parameter is specified in the 7th supplementary information field.1273 ASP ACTIVATION FAILED RNC disturbances (1000-1999) MML commands ("CM. If the peer M3UA is operating in the Nokia Siemens Networks network element. 2) ZDFD:CM.. 3) ZDFD:CM. 2) ZDFD:CM..0:AF3. fill in the Problem Report from this network element and send it to your local Nokia Siemens Networks representative. with ZNLC MML command.0:A79.....

If so. In the second log the first byte shows the IP address version. The amount of configured streams is shown in the 6th supplementary information field. 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. as follows: 1) Change the state of the corresponding M3UA based link to UA-INU. add the IP address to the desired association set with ZOYA MML command. DN99580853 Issue 08A Id:0900d805805de168 145 . Use ZOYI::A. If the value of the 1st supplementary information field is 0F: SCTP could not establish the association with the configured amount of outbound streams. Check whether the IP address written to the log should be configured to some association set. The amount of SCTP streams that are returned in the communication up notification are shown in the 5th supplementary information field. Change the value of the parameter to NO. which has the role of server. 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". The amount of streams is configured in the association set basis. with the ZNLC MML command.RNC disturbances (1000-1999) 1273 ASP ACTIVATION FAILED alarm. 3) Change the state of the corresponding M3UA based link to AV-EX. 0 means IPv4 and 1 means IPv6. with the ZNLC MML command. 2) Change the registration_request parameter giving the association set specified in the 4th supplementary information field and the new value = NO for registration_request parameter as the parameters in ZOYM MML command. Cancelling No cancelling. second with the IP address that was not configured. This SCTP user adjusted to use the lower amount of outbound streams that was returned in the communication up notification.

Supplementary information fields Instructions The alarm requires no actions. This alarm occurs only if the unit is found to be totally incapable of message transmission. 146 Id:0900d805805de168 DN99580853 Issue 08A . the active unit of a 2N redundant pair is probably removed from a rack. This alarm is used to inform the recovery system that performs the necessary recovery actions. a situation when the unit has not responded to supervision via the normal message transfer mechanism and receiving the status of a unit's message transferring system by utilizing the HMS (Hardware Management System) has failed. If this alarm has occurred. The alarm supports the activation of the automatic recovery for the object unit. This means that the switchover cannot be initiated using the normal message transferring mechanism. which is always the system maintenance unit. a normal message connection from SYM unit to the removed unit's pair unit and units below in hardware topology are lost. You can check the supporting amount of the alarm with the MML command ARO.1275 NO RESPONSE FROM CRITICAL UNIT RNC disturbances (1000-1999) 80 1275 NO RESPONSE FROM CRITICAL UNIT Meaning Critical computer unit from the message transfer point of view has not responded in the allotted time to a supervision message sent by the supervisory unit. Cancelling No cancelling.

An alarm can also be issued if a unit first acknowledges the Hardware Management System (HMS) status inquiry and then does not send a request for port configuration within a certain time period. Supplementary information fields Instructions Check that the plug-in unit of the target unit is properly attached to its slot in the subrack. and the data transmission channel is out of use.RNC disturbances (1000-1999) 1277 PLUG IN UNIT CONNECTION FAILURE 81 1277 PLUG IN UNIT CONNECTION FAILURE Meaning This alarm is issued when some unit fails to acknowledge the Hardware Management System (HMS) status inquiry. the unit is restarted. contact the local Nokia Siemens Networks representative.e. and the restart of the units does not remove the problem. data cannot be sent or received. communication with the target unit might not be possible. Check that cables connected to the plug-in unit of the target unit are properly attached to their slots. If you can not find defects from the computer units. The alarm supports the activation of automatic recovery for the object unit. Because of the fault. Cancelling No cancelling. i. that is. DN99580853 Issue 08A Id:0900d805805de168 147 . Occurence of this alarm leads to restarting of the target unit of the alarm.

1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION RNC disturbances (1000-1999) 82 1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION Meaning Information about network element splitting is located in several different places. This kind of divergence is most likely to happen when the creation. it sets this alarm. by some file saving error or information distribution failure. It is being supervised that all these have the same information about the split status. Supplementary information fields 1 implicates the kind of trial information inconsistency that was observed 0 not defined 1 system variable defining split state contains inconsistent information 2 functional unit information in SCDFLE contains inconsistent information compared to information in ne_split system variable 3 system variable defining split state contains inconsistent information compared to the information received from Software Configuration Management information about trial status from Software Configuration Management point of view 01 Trial configuration has been created in the network element 00 Trial configuration has not been created in the network element 2 3 information about own unit slice identifier from Software Configuration Management point of view 0 system has not been split or slice identifier unknown 1 original 2 trial 4 value tells if network element is split. The divergence of network splitting information may be caused. This may lead to a malfunction of the whole network element. for example. If the supervisor notices that the information is not the same in every place. deletion or completion of network element splitting fails. information read from the system variable 0 system has not been split or slice identifier unknown 1 original 148 Id:0900d805805de168 DN99580853 Issue 08A .

Cancelling No cancellation.RNC disturbances (1000-1999) 1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION 2 trial 5 value tells own unit slice identifier read from the system variable 0 system has not been split or slice identifier unknown 1 original 2 trial 6 type of the unit whose integrity error was observed 7 index of the unit whose integrity error was observed 8 slice identifier of the unit whose integrity error was observed 0 system has not been split or slice identifier unknown 1 original 2 trial Instructions Alarm does not require user actions. DN99580853 Issue 08A Id:0900d805805de168 149 .

Cancelling No cancelling. this may cause alarm 1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART for the tributary units concerned. Possible reasons for the configuration failure could be. for example. Supplementary information fields 1 service or internal stage of execution where configuring the message connection failed 0: 1: 2: 3: 4: port configuration apc first phase initialisation (ingress) apc first phase initialisation (egress) internal interface creation half cross connection creation 2 general error message of the system. 150 Id:0900d805805de168 DN99580853 Issue 08A .1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE RNC disturbances (1000-1999) 83 1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE Meaning This alarm is issued when the internal ATM connection management object cannot configure a message connection to functional unit. Occurrence of this alarm leads to restarting of the object unit of the alarm. If the restarted unit is MXU. You can check its meaning with a command of the service terminal extension MRS or in the General Error Messages of System Instructions The alarm requires no actions. System restart will take place to recover from the situation if the object unit is MXU and it is connected to tributary unit that is classified as system critical unit. a synchronisation error between program blocks or problems in HMS messaging.

TALI [RFC3094] 10 .3 [Q.txt> [Ong] 11 .M2UA [RFC3331] 3 .3] 9 .2150.M2PA [RFC2960] 6 .323] 14-Q. 7 (SS7) signalling over Internet Protocol (IP). The value is between 0-31 4 identifier of the SCTP association within the computer unit 2 DN99580853 Issue 08A Id:0900d805805de168 151 .H.3] IUA: association number M3UA: association set.248 [H.1/Q. 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. Supplementary information fields 1 SCTP Payload Protocol Identifier 1 .ENRP <draft-ietf-rserpool-enrp-03.V5UA [RFC2960] 7 .2631.txt> [Ong] 13 .1902.txt> [Ong] 12 .RNC disturbances (1000-1999) 1282 ASSOCIATION PARAMETER FAILURE 84 1282 ASSOCIATION PARAMETER FAILURE Meaning Parameter setting has failed concerning Signalling System No. SCTP operates with the old value of the parameter.2150.248] 8 .M3UA [RFC3332] 4 .3 [Q.SUA [RFC2960] 5 .2150.H.IPC/Q. 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.BICC/Q. to which the association belongs 3 IUA: Not applicable M3UA: index of the association inside the association set.2150.323 [H.1/Q.ASAP <draft-ietf-rserpool-asap-03.DUA <draft-ietf-sigtran-dua-03. When the parameter setting fails.IUA [RFC3057] 2 .

Instructions Fill in a Problem Report and send it to your local Nokia Siemens Networks representative. Computer log writings can be obtained with service terminal commands ZGD and ZGS. RTO. Corresponding parameter names are RTI. Enclose the printout outputs with the MML commands ZOYI::A.MAX. The ZOYI command shows the information of the SCTP associations and ZOYO shows the SCTP association parameter values. 0020 SCTP SACK parameter setting failed.1282 ASSOCIATION PARAMETER FAILURE RNC disturbances (1000-1999) 5 6 number of the socket corresponding the association status of the socket option setting corresponding the parameters. Corresponding parameter names are HB. and ZOYO. Enclose also the log writings of the S3ZOCK program block in the computer log of the signalling unit identified in the first two fields. 0010 SCTP Bundling parameter setting failed.MAX. 0008 SCTP Checksum algorithm selection parameter setting failed. Cancelling No cancelling 152 Id:0900d805805de168 DN99580853 Issue 08A . Value of the field is one of the following values or a combination (sum) of some of the following values. 0004 SCTP Association parameter setting failed.MAX.INIT. 0001 SCTP Retransmission Timeout parameter setting failed. Corresponding parameter name is ASSOCIATION. 0002 SCTP Peer Address parameter setting failed.RETRANS.RETRANS.INTERVAL and PATH. in the failure report.MIN and RTO.

The field can have following values: 04 06 6 IPv4 IPv6 IP traffic behaviour aggregate. Check the status of the IP interface of the terminating computer unit DN99580853 Issue 08A Id:0900d805805de168 153 . which is the other end of the connection. Supplementary information fields 1 2 3 4 5 type of the terminating computer unit index of the terminating computer unit type of the network interface unit index of the network interface unit IP version.RNC disturbances (1000-1999) 1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN 85 1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN Meaning Automatic internal IP over ATM channel has broken. You can check its meaning with a command of the service terminal extension MRS or in the General Error Messages of System Instructions Take the computer logs from failed units specified in supplementary information fields 1-4. cannot be used for IP calls. give the service terminal command: clog -s -a Check the IP interface configuration of the system with the following MML command: ZQRI. The CDSP plug-in unit. The field can have following values: 01 02 03 real time traffic class non-real time traffic class generic traffic class 7 general error message of the system. The alarm indicates that the internal VCC creation has failed. and the IP connectivity from the CDSP plug-in unit is broken. To display the computer log.

Cancelling No cancelling 154 Id:0900d805805de168 DN99580853 Issue 08A .<index>:INS. ZQRS:<unit>. "AI3") The system tries to recreate the channel after a short time.<index>:INS. e.g. where <unit> is supplementary information field 1 <index> is supplementary information field 2 Check the status of the IP interface of the network interface unit with the following MML commands: ZQRS:<unit>.1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN RNC disturbances (1000-1999) with the following MML command: ZQRS:<unit>.<ip_if>. where <unit> is supplementary information field 3 <index> is supplementary information field 4 <ip_if> is the name of the IP interface (starts with letters "AI" combined with supplementary information field 2.AI0.<index>. the alarm is set again. If the alarm is shown periodically. If the creation still fails. if the computer logs indicate problems in that unit. Restarting of the CDSP plug-in unit might help. ZQMQ::::::AUTO. contact the local Nokia Siemens Networks representative.

in DMX and Chorus-based computers. if it is the spare unit of a 2N pair index of the waited sdu (00. respectively) has detected that one or more incoming AAL5 frames have been lost without any error indication from the ATM adaptation layer.RNC disturbances (1000-1999) 1285 AAL5 FRAME LOST 86 1285 AAL5 FRAME LOST Meaning The post office which handles message traffic between computers (POFFIC and GOFFIC.. if it is the spare unit of a 2N pair the index of the active MXU between the SFU and the unit which detected the lost frame.7F) index of the received sdu (00. this field indicates the index of the unit itself or that of its active unit. this field indicates the type of the unit itself or that of its active unit. If the unit which detected the lost frame is directly connected to the SFU. The field may have the following values: RT nRT 5 real-time non-real time 4 the type of the active MXU between the SFU and the unit which detected the lost frame. The object unit of the alarm is the unit where the frame loss was detected.. If the unit which detected the lost frame is directly connected to the SFU.7F) total count of the frames lost on the channel number of the AAL5 errors that occured between the previous 1269 or 1285 alarm and this alarm 6 7 8 9 10 DN99580853 Issue 08A Id:0900d805805de168 155 . Supplementary information fields 1 2 3 type of the unit that sent the lost frame(s) index of the unit that sent the lost frame(s) the virtual channel identifier of the channel from which the frame was lost the internal service category of the failed channel.

it is most probably due to faulty hardware. Cancelling No cancelling. If the problem persists. run a fault diagnosis for the object unit of the alarm and for the unit stated in the supplementary information fields 1 and 2 (with the MML command UDU) to find possible hardware defects. It only provides information about temporary problems in the message transmission system. If you cannot find defects in the plug-in unit. follow the instructions of the diagnostics report. If the unit is faulty.1285 AAL5 FRAME LOST RNC disturbances (1000-1999) Instructions Usually the disturbance requires no actions. 156 Id:0900d805805de168 DN99580853 Issue 08A . In this case. contact the local Nokia Siemens Networks representative.

Supplementary information fields 1 2 3 4 number of the rack in which the plug-in unit is located number of the subrack in which the plug-in unit is located location of the plug-in unit in the subrack (=slot number) identifies the index number of active hardware in the plug-in unit specified in the previous supplementary information fields 00: index of hw activity is 0 01: index of hw activity is 1 FF: both system clock signals on the unit are missing identifies the status of clock signals in the unit 00: both system clock signals exist 01: A signal is missing and B signal is used 10: B signal is missing and A signal is used 11: both system clock signals are missing contains coded information about system clock signal availabilities and statuses of HW activities. This problem may cause a situation where the unit will not start successfully. the alarm requires no actions. The system clock signal that will be selected for use in each plug-in unit should be the one that the active Timing and Hardware Management Bus Unit (TBU) is delivering. when both of the missing. 2. The system clock signals are the start-up phase of a plug-in unit when the the hardware activity differs from the used alarm is also issued. If the alarm was set during the switchover of TBU. This field is only for further investigations made by Nokia Siemens Networks Instructions 1.RNC disturbances (1000-1999) 1286 MISMATCH IN SYSTEM CLOCK SIGNAL 87 1286 MISMATCH IN SYSTEM CLOCK SIGNAL Meaning The system clock signal for the plug-in unit is selected from the two system clock signals that are delivered to each plug-in unit of the system. If the alarm has been set from many plug-in units of a subrack then 5 6 DN99580853 Issue 08A Id:0900d805805de168 157 . This alarm is set during system has detected that system clock signal.

the TBUF and/or TSS3 plug-in units that deliver the system clock signals to the subrack must be replaced. If there is also alarm 3017 SYSTEM CLOCK FAILURE and/or alarm 3018 CLOCK DISTRIBUTION FAILURE. EA and DP commands of HMEXTE service terminal extension program.<subrack>. The location of the faulty plug-in unit is specified in the supplementary information fields 1-3. 4. See operating instructions of the above mentioned alarms. Use the WFI MML command: ZWFI:P:. 5. 3.1 Information about the actions that were carried out in steps 1 and 2 above 5.5 Alarm history.2 Execution printouts of the CM. fill in a Problem Report and send it to your local Nokia Siemens Networks representative.<ppa>. If the replacing of the unit does not help and the alarm is set again. Use MML command ZAHP. see instructions on replacing plug-in units. 5.1286 MISMATCH IN SYSTEM CLOCK SIGNAL RNC disturbances (1000-1999) continue to the step 4 below. the second supplementary information field value stands for the subrack value and the third supplementary information field value stands for the PPA value (Note that the PPA value must be given in decimal format). 5.4 The content of the A2TSIG file (use FUTILI service terminal extension program: TN:A2TSIG) 5. Cancelling No cancelling. The following information must be included in the Problem Report: 5.:<rack>.3 The plug-in unit related information from which the alarm has been set so that the first supplementary information field value stands for the rack value. Change the accused plug-in unit. 158 Id:0900d805805de168 DN99580853 Issue 08A .

DN99580853 Issue 08A Id:0900d805805de168 159 . Supplementary information fields 1 2 3 type of the unit where the message connectivity loss was observed index of the unit where the message connectivity loss was observed type of the unit whose message connectivity loss was observed first. the operation of the system may be disturbed until the recovery system isolates the faulty unit. The alarm supports the activation of the automatic recovery.RNC disturbances (1000-1999) 1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST 88 1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST Meaning Message connectivity between the object unit of the alarm and the active OMU is lost. The field may have the following values: 01 00 path analysis used path analysis not used 4 5 6 failed computer amount in path analysis. Depending on the tasks of the unit. Check the supporting amount of the alarm with the MML command ARO. Otherwise the value is 0 Instructions The alarm requires no actions. If the object unit of the alarm is not equal to the unit given in this field. This field is significant only when the 5th supplementary information field is 01. If the object unit of the alarm is not equal to the unit given in this field. it means that analysis has decided that the defect is in the object unit of the alarm instead of this unit index of the unit whose message connectivity loss was observed first. it means that analysis has decided that the defect is in the object unit of the alarm instead of this unit used analysis type that confirmed this failure.

160 Id:0900d805805de168 DN99580853 Issue 08A .1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST RNC disturbances (1000-1999) Cancelling No cancelling.

DN99580853 Issue 08A Id:0900d805805de168 161 . alarm 3276 SUBRACK CONNECTIVITY LOST is also issued to indicate the problem. the functional units of the subrack do not work normally. If alarm 1291 is issued concerning both TBUs of the subrack (the subrack location is given in the supplementary information fields of the alarm). The alarm initiates the switchover to the Timing and Hardware Management Bus Unit (TBU). Supplementary information fields 1 2 location number of the cabinet where the subrack is located location number of the subrack Instructions The alarm requires no actions. The reason for the alarm is either that the functional units of the subrack have lost synchronisation or the subrack is without power supply.RNC disturbances (1000-1999) 1291 SUBRACK CONNECTIVITY FAILURE 89 1291 SUBRACK CONNECTIVITY FAILURE Meaning Subrack presence supervision has detected a communication failure in the domain of the subrack. Cancelling No cancelling. You can check the supporting amount of the alarm with the MML command ARO. the functional units of the subrack work normally. If alarm 3276 SUBRACK CONNECTIVITY LOST is not issued and alarm 1291 is issued only concerning one TBU unit of the subrack (the one that was the active TBU before the switchover). The alarm supports the activation of the automatic recovery for the object unit. If the reason for the failure is a subrack power failure.

also the transit of the signalling message is to be prevented. Additionally. the translation of which leads to the called GTT result in question (the message has been transmitted) the source point behind the calling GTT result is not allowed to send signalling messages with the called GT. This conclusion is based on the calling and the called global titles included in the message. the calling GTT result into which the analysis of the calling GT has led. If the transit message is destroyed. 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. the linkset from which the message was received. the translation of which leads to the called GTT result in question (the message has been destroyed or sent back) 02 2 signalling network of the adjacent point from which the processed signalling message was received. IN0 international network 1. IN1 national network 0. the called GTT result into which the analysis of the called GT has 4 5 162 Id:0900d805805de168 DN99580853 Issue 08A . This and the 2nd supplementary information field together indicate the signalling point from which the message was received. NA0 national network 1.1293 SCCP GT SCREENING APPLIED RNC disturbances (1000-1999) 90 1293 SCCP GT SCREENING APPLIED Meaning SCCP has detected at the signalling transfer point a signalling message for which this alarm must be set. Signalling network can get the following values: 00 04 08 0C international network 0. NA1 3 point code value of the adjacent point from which the processed signalling message was received. 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. that is. 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 called GTT result and the called GT analysis that lead to that result can be checked with the MML commands ZNAI and ZNBI respectively. and the nature of address indicator 05-15 global title does not contain the translation type. 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 encoding scheme. The standard is encoded with the most meaningful bits 5-8 in the following manner: 01 02 ITU-T ANSI The global title indicator is encoded with the least meaningful bits 1-4. and the encoding scheme 04 global title contains the translation type. the numbering plan. the numbering plan.RNC disturbances (1000-1999) 1293 SCCP GT SCREENING APPLIED led. 6 the global title standard and the global title indicator used in the calling global title of the SCCP message. the encoding scheme or the nature of address indicator. the numbering plan. 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. 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 02 global title contains only the translation type 03-15 global title does not contain the translation type. 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 FF translation type not in use global title does not include translation type DN99580853 Issue 08A Id:0900d805805de168 163 . the encoding scheme or the nature of address indicator.

E.212) ISDN/mobile telephone network numbering plan (E.164. the number 12345 is encoded 12 34 5F. 164 Id:0900d805805de168 DN99580853 Issue 08A . If the address information includes more than 6 digits.210.214) reserved for future use reserved for future use 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 0010 0011 0100 0101 : 1110 1111 subscriber number reserved for national use national meaningful number international number reserved for future use reserved for future use 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. 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. for example.E.112-1992.69) ship telephone network numbering plan (E.121) telex network numbering plan (F. The numbering plan is encoded with the most meaningful bits 5-8 in the following manner: 0000 0001 0010 0011 0100 0101 0110 0111 1000 : 1110 1111 unknown ISDN/telephone network numbering plan (E. there are values defined for the translation type in the national specification ANSI T1. the address information includes the first 6 digits.211) mobile telephone network numbering plan (E. These values of the translation type can be analysed in the normal way.163) reserved for future use data network numbering plan (X.1293 SCCP GT SCREENING APPLIED RNC disturbances (1000-1999) For the case the standard is ANSI and the global title indicator is 02.

Check if this restriction is justified and remove the blocking with the MML command ODN if necessary. 3.RNC disturbances (1000-1999) 1293 SCCP GT SCREENING APPLIED 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 message has been destroyed or sent back. which leads to that calling GTT result record. The analysis of the calling global title leads to the calling GTT result as mentioned in the Supplementary information field 4. For tracing the operator of the originating signalling point. 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. Cancelling No cancelling. The analysis of the called global title leads to the called GTT result as mentioned in the Supplementary information field 5. 6. The Supplementary information field 4 (calling GTT result) can also be used to find out the calling GT via calling GT analysis data. the message was transmitted. the Supplementary information fields 6. 7. If the value of the Supplementary information field 1 (cause code) was 2. 4. should be notified about an access right violation. so that the calling GT analysis is sought using the MML command ZODJ. the information supplied in the Supplementary information fields 2. 7. 8 and 9 can be used to get the calling global title from which the message was originated. If the value of the Supplementary information field 1 (cause code) was 1. 8 and 9 could be used: the Supplementary information fields 2 and 3 show the adjacent point from which the message was received. DN99580853 Issue 08A Id:0900d805805de168 165 .

One reason can be that the IP address has not been configured. the IP address of the TPG is missing). contact your local Nokia Siemens Networks representative. If the first supplementary field has the value 02. To configure the IP address for the TPG. Supplementary information fields 1 the 01 02 03 operation socket creation fails socket binding fails could not get own IP address 2 indicates used IP version 01 IPv4 02 IPv6 indicates used protocol 01 RTP 02 RTCP 03 not exist the 09 13 14 22 23 24 38 43 46 47 49 55 error codes consist of C socket errno values bad file number permission denied bad address invalid argument file table overflow too many open files socket operation on protocol not supported protocol family not supported address family not supported cannot assign requested address no buffer space available 3 4 Instructions If the first supplementary field has the value 01. then a UDP port is already reserved or the TPG is not configured correctly (for example.1296 SOCKET CREATION FAILURE RNC disturbances (1000-1999) 91 1296 SOCKET CREATION FAILURE Meaning When this alarm occurs it means that socket creation or binding of a socket has failed or the TGP's IP address has not been received. see chapter 'Creating Nb interface with IP backbone' in the 166 Id:0900d805805de168 DN99580853 Issue 08A . the limit of the file descriptions has been exceeded. If this occurs.

contact your local Nokia Siemens Networks representative. Cancelling No cancelling. If the alarm is shown periodically. DN99580853 Issue 08A Id:0900d805805de168 167 .RNC disturbances (1000-1999) 1296 SOCKET CREATION FAILURE 'MGW for MSS Integration' document.

Change the state of the TCU unit which has failed with the MML 2 3 168 Id:0900d805805de168 DN99580853 Issue 08A . RTP.1297 SOCKET INTERFACE FAILURE RNC disturbances (1000-1999) 92 1297 SOCKET INTERFACE FAILURE Meaning An error has occurred in the interface between the Real-Time Transport Protocol (RTP). use the service terminal command clog -sa If the value in the third supplementary information field is 65d. or the User Datagram Protocol (UDP) application and the IP stack. or UDP packets cannot be sent to the network or received from the network through this socket interface. the Real-Time Transport Control Protocol (RTCP).to display the computer log. there is a problem in the IP stack. Check the information on the faulty unit from the alarm and the computer logs of the failed units: . RTCP. Supplementary information fields 1 name of the protocol 01 RTP 02 RTCP 03 UDP the operation 01 packet sending 02 packet receiving the 04d 05d 09d 11d 14d 22d 27d 28d 32d 35d 49d 61d 65d error codes consist of the standard C socket errno values interrupted system I/O error bad file number no more processes bad address invalid argument file too large no space left on broken pipe operation would block can't assign requested address connection refused no route to host Instructions If this alarm occurs. check your IP configuration with the MML command ZQKB.

DN99580853 Issue 08A Id:0900d805805de168 169 . contact your local Nokia Siemens Networks representative. or replace the unit (for instructions.RNC disturbances (1000-1999) 1297 SOCKET INTERFACE FAILURE command QRN and restart it. If restarting or replacing the unit does not correct the problem and the alarm is shown periodically. Cancelling No cancelling. see the instructions on replacing plug-in units).

An interface between the RTP application and the DSP cannot be opened or data cannot be sent to the DSP or received from the DSP through this interface. 2692 INCORRECT WORKING STATE DSP has been restarted. which If the alarm is shown periodically. Cancelling No cancelling. it means that the corrects the problem. is a problem in the DSP. The supplementary field. it means that there failed operation is included in the first If alarms 1239 DSP SUPERVISION FAILURE or occur at the same time. 170 Id:0900d805805de168 DN99580853 Issue 08A .1298 DSP INTERFACE FAILURE RNC disturbances (1000-1999) 93 1298 DSP INTERFACE FAILURE Meaning If this alarm occurs. there is a fault in a Digital Signal Processor (DSP) or in the Real-time Transport Protocol application (RTP). contact your local Nokia Siemens Networks representative. Supplementary information fields 1 the 01 02 03 operation dsp opening dsp reading dsp writing 2 Instructions indicates the index of DSP If this alarm occurs.

MGC also requested MGW to send RTCP 07H RTCP supervision is requested by MGC with H. Supplementary information fields 1 2 3 connection identifier indicates the local RTCP port indicates the usage of RTCP protocol in this connection: 03H RTCP supervision is provisioned in Media Gateway (MGW) 06H RTCP supervision is requested by Media Gateway Controller (MGC) with H.RNC disturbances (1000-1999) 1299 RTCP SUPERVISION FAILURE 94 1299 RTCP SUPERVISION FAILURE Meaning Real-time Transport Control Protocol (RTCP) supervision has detected failure in a user plane Real-time Transport Protocol (RTP) connection. it means that either there is a problem in the IP network or the peer does not support the RTCP. When hexadecimal value is converted to binary value. it indicates if packet receiving succeeded(1) or failed(0) indicates how long a time (in seconds) it has been since the latest RTP packet was received indicates the ip interface type in this connection: 00H 01H 02H 03H 04H 05H 06H 7 IP-trunk IMS IP Multimedia UMA .248 for this connection.unlicensed mobile access Semipermanent Nb' IP based Iu-CS UDP 5 6 indicates call duration in seconds DN99580853 Issue 08A Id:0900d805805de168 171 . If this alarm occurs. MGC did not request MGW to send RTCP 4 indicates the transfer status of the last 32 or so rtcp packets.248 for this connection.

use the service terminal command clog -sa. it means that there are problems somewhere in the IP network. and the other MGW does not support the RTCP. To display the computer log. Check the unit information from the alarm and then check the peer's IP address from the computer logs. Check Call Control Signalling (for example. change the value of the RTCP_FOR_UP_MONITORING parameter in this MGW to 01H or 02H using the W4M MML command. If it is possible to change the peer's RTCP configuration. Check the RTCP configuration and compatibility between this MGW and the peer. Interface Specification. If the value is 06H or 07H: In this case MGC request overrides the value of the RTCP_FOR_UP_MONITORING parameter. use the service terminal command clog -sa. the calls will be released as RTCP reports were not received. you can see which profile was used in this call. Use monitoring tools such as Ethereal and Signalling Monitoring (SIMO). If both MGWs support RTCP protocol and this alarm still occurs. RTCP_FOR_UP_MONITORING parameter is described in 'RTP/RTCP in Mobile Media Gateway'. activate RTCP from peer. If the value is 03H: If the value 03H is in use in one MGW.1299 RTCP SUPERVISION FAILURE RNC disturbances (1000-1999) Instructions Operating instructions depend on the value of the supplementary information field 3. In the DSP parameter profile ID field(4). it means that there are problems somewhere in the IP network. 172 Id:0900d805805de168 DN99580853 Issue 08A . Check the unit information from the alarm and then check the peer's IP address from the computer logs.248 contents to see where RTCP supervision request originates. To display the computer log. Session Initiation Protocol (SIP) ) and H. Check the used RTCP_FOR_UP_MONITORING from the DSP parameter profile by using the W4I MML command. If this is not possible. If the peer supports RTCP protocol and this alarm occurs.

DN99580853 Issue 08A Id:0900d805805de168 173 .RNC disturbances (1000-1999) 1299 RTCP SUPERVISION FAILURE Cancelling The alarm cannot be cancelled.

traps. this field will be empty 3 4 5 174 Id:0900d805805de168 DN99580853 Issue 08A . If exception number is not 03 (DSI Exception) or 04 (ISI Exception).1304 ACTOR EXCEPTION RNC disturbances (1000-1999) 95 1304 ACTOR EXCEPTION Meaning Exceptions are generated and detected by the actor when executing instructions. These exceptions are classified as faults. Possible values are: 00 01 02 03 04 05 06 07 08 09 0C 0D 0E 2 Illegal Exception System Reset Exception Machine Check Exception DSI Exception ISI Exception External Interrupt Exception Alignment Exception Program Exception Floating Point Unavailable Exception Decrementer Exception System Call Exception Trace Exception Floating-point assist (optional) exception fault address. Thread name will be truncated if its length exceeds 12. If the target thread has no name. code offset should be 0xFFFFFFFF exception code offset which indicates the failed part. Actor name will be truncated if its length exceeds 8. When an actor exception occurs. the actor supervision system will cause this actor or whole unit to restart after making an operating system log. If PC value is not inside the code segment. and aborts. fault address should be 0 name of the actor that caused the exception. If the target actor has no name. this field will be empty name of the thread that caused the exception. Supplementary information fields 1 exception number.

the reason for the exception is probably a software fault. DN99580853 Issue 08A Id:0900d805805de168 175 . To correct the fault. Cancelling No cancelling. contact the local Nokia Siemens Networks representative.RNC disturbances (1000-1999) 1304 ACTOR EXCEPTION Instructions If the computer has not set alarms on hardware fault.

You can check the supporting amount of the alarm with the MML command ARO. Supplementary information fields 1 2 3 identifier of powerPC application error code for the CDSP memory configuration failure the operation mode that caused the alarm 0 = PowerPC application release memory 1 = PowerPC application allocate memory Instructions The alarm requires no actions. Cancelling No cancelling.1331 CDSP MEMORY CONFIGURATION FAILURE RNC disturbances (1000-1999) 96 1331 CDSP MEMORY CONFIGURATION FAILURE Meaning Configurable Digital Signal Processing (CDSP) memory configuration failed when pool-related information in DSP service pool was reconfigured. The failure was detected when all DSPs in one PowerPC were changed to another service pool and memory configuration performed by a PowerPC application failed. 176 Id:0900d805805de168 DN99580853 Issue 08A . The alarm supports the activation of the automatic recovery for the object unit.

If defects can be found in the functioning of the software. Supplementary information fields 1 2 the identifier of the channel with usage failure reason for error: 00 VCC opening failed in the local endpoint of the channel 01 sending frame failed 02 receiving frame failed Instructions If the situation persists or occurs often. Attach in the Failure Report the contents of the computer log. If defects cannot be found in the plug-in units. 2. With the service terminal command ZSLE. try the following: 1. 4. Check the cabling of the functional units reported in the alarm. and the restart of functional units did not remove the problem.RNC disturbances (1000-1999) 1336 AAL5 CHANNEL USAGE FAILED 97 1336 AAL5 CHANNEL USAGE FAILED Meaning Local virtual channels between computer units cannot be taken into use. Find the cabling instructions in Site documents. With the service terminal command ZGD. the operating system log. and the alarm history. restart (with MML command ZUSU) the object unit of the alarm. 5. If possible. The object unit of the alarm is the unit where the usage failure is noticed. check the computer log for possible faults and/or exceptional conditions detected by the software. check the error log of the operating system to make sure that no major software defects have occurred in either functional unit. DN99580853 Issue 08A Id:0900d805805de168 177 . or with command 'olog -s' in Chorus units. fill in a Failure Report and send it to the local Nokia Siemens Networks representative. 6. or 'clog -s' in Chorus units. 3.

Cancelling No cancelling.1336 AAL5 CHANNEL USAGE FAILED RNC disturbances (1000-1999) contact the local Nokia Siemens Networks representative. 178 Id:0900d805805de168 DN99580853 Issue 08A .

If the object unit of the alarm is not equal to the unit given in this field. it means that the analysis has decided that the defect is in the object unit of the alarm instead of this unit used analysis type that confirmed this failure. it means that the analysis has decided that the defect is in the object unit of the alarm instead of this unit index of the unit whose message connectivity loss was observed first. The field may have the following values: 01 00 path analysis used path analysis not used 4 5 6 failed computer amount in path analysis.). The object unit of the alarm will be restarted automatically as a recovery action. Supplementary information fields 1 2 3 type of the unit where the message connectivity loss was observed index of the unit where the message connectivity loss was observed type of the unit whose message connectivity loss was observed first. When the object unit is a non-redundant unit having non-recoverable child units (for example. If the object unit of the alarm is not equal to the unit given in this field.RNC disturbances (1000-1999) 1341 MESSAGE CONNECTIVITY FAILURE IN NONREDUNDANT UNIT 98 1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT Meaning Message connectivity between the object unit of the alarm and the active OMU is lost. NIWU. This field is significant only when the value on the 5th supplementary information field is 01. NIP1. IWS1. The alarm supports the activation of the automatic recovery. DN99580853 Issue 08A Id:0900d805805de168 179 . Otherwise. Check the supporting amount of the alarm with the MML command ARO. the value is 0 Instructions The alarm requires no actions. it cannot be put to TE state and diagnosed. etc. NPS1.

180 Id:0900d805805de168 DN99580853 Issue 08A .1341 MESSAGE CONNECTIVITY FAILURE IN NONREDUNDANT UNIT RNC disturbances (1000-1999) Cancelling No cancelling.

However. DN99580853 Issue 08A Id:0900d805805de168 181 . from which they can be output with an MML command.RNC disturbances (1000-1999) 1425 OVERFLOW IN ALARM BUFFERING 99 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 NWI3 interface. Cancelling No cancelling. the alarms that are not output or sent to the NWI3 interface are saved normally in the alarm system log file (ALHIST). Supplementary information fields 1 buffer type: 0 buffer used for buffering the alarms to be output has overflown buffer used for buffering the alarms to be formatted for sending to the NWI3 interface has overflown 1 2 number of alarms not output or sent to the NWI3 interface Instructions The alarm requires no actions. The alarm is set after all buffered alarm output tasks have been processed and sent forward from the alarm system after a buffer overflow.

Cancelling No cancelling.1431 MMI SYSTEM OVERLOAD RNC disturbances (1000-1999) 100 1431 MMI SYSTEM OVERLOAD Meaning The MMI system is overloaded. 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. 182 Id:0900d805805de168 DN99580853 Issue 08A . Supplementary information fields Instructions The alarm requires no actions.

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. is set. The blocked tasks are not executed before the fault has been corrected and the blocking is removed. 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: 12 time-out 2 identifier of the task in the command calendar. then also the alarm 2430. ERROR IN COMMAND CALENDAR.RNC disturbances (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR 101 1432 DISTURBANCE IN COMMAND CALENDAR Meaning A temporary disturbance has been detected in the command calendar operation. This identifier can be seen in the ID column of the execution printout of the MML command ICL and points DN99580853 Issue 08A Id:0900d805805de168 183 . If the fault is permanent. The command calendar interrupts the execution of the calendar task that was being executed and blocks the task.

so that a command calendar can start an MML session. see instructions on MML commands and command calendar. outputs data of all tasks. remove the blocking with the MML command ICB. 2. from command calendar queues (with the MML command ICL) or from execution printouts. If the alarm is set. Ask a user to close his/her MML session. removes the blocking from the calendar task 11. 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. MMI SYSTEM FILE ERROR. ICL. For example. act according to its instructions. If the value of the supplementary information field 1 is 01. Do the following: 1. Add the same task to the calendar again with the MML command 184 Id:0900d805805de168 DN99580853 Issue 08A . 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. Do the following: 1. For example. b) the calendar task has been created by using a username that has been deleted.CMD index of the command in command file 4 Instructions You MML the the can check which calendar task execution has failed from the session log/MML command log (with the MML command IGO). the calendar task cannot be executed. Check if the alarm 2427. 3. You can remove the blocking with the MML command ICB. because: a) all MML sessions are busy. For more information. If the calendar task is blocked.1432 DISTURBANCE IN COMMAND CALENDAR RNC disturbances (1000-1999) out the command calendar task which was been executed when the disturbance occurred 3 name of the command file been executed without the extension . is set. 2. ICB:11:UNBLOCK. Remove the task from the calendar with the MML command ICD.

Correct the command with the MML command ICM so that it conforms to the syntactic rules of the command. whether the printer is working. Note that ICD does not delete the command file from the disk. Remove the blocking from the command with the MML command ICB. the command in the calendar (including the commands of the command files in the calendar) cannot be executed. PROCESS EXCEPTION. only from the calendar: you can add the same command file to the calendar again. add paper). the command in the calendar (including the commands of the command files in the calendar) cannot be executed. because its syntactic structure is faulty. 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 it is not deleted from the disk. The following command outputs information about the printer LPT-0: ZISI::LPT. where the printout are directed to): 1. act according to its instructions. RECOMMENDATION: Direct the printouts also to the BBU-0.RNC disturbances (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR ICI. Direct the printouts through the semipermanent logical file (see the instructions given on the supplementary information value 10 at the end of the description). If the value of the supplementary information is 03. correct the fault (eg. If the value of the supplementary information is 04. If the value of the supplementary information is 05. If the value of the supplementary information is 02. Check if the alarm 1078. if you want that the command calendar is working even when the printer is not working. Check with the MML command ISI. the MML command has made a memory protection error. remove the blocking with the MML command ICB. 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. 2. is set. 3. 3. If the alarm is set. If the calendar task is blocked. If the printer does not work.0. DN99580853 Issue 08A Id:0900d805805de168 185 .

2. 2. If the calendar task is blocked. 3. c) If the calendar task is a command file: 1. If the calendar task is blocked. change the disk. The following command outputs data from the file CCALENDAR. d) If the alarm 2427. Check with the MML command IDL that the command file is not faulty. act according to its instructions. if you want that the command calendar is working even when the printer is not. If there is no space in the file. The following command outputs information about the disk: ZISI::WDU. is also set. Direct the printouts through the semipermanent logical file (see the instructions given on the supplementary information value 10 at the end of the description). If the file is faulty. whose name ends with LOG. If the disk is not damaged. 4. where the printouts are directed to): 1. remove the blocking with the MML command ICB.1432 DISTURBANCE IN COMMAND CALENDAR RNC disturbances (1000-1999) b) If the execution outputs are directed to the disk file (you can check with the command IID::COMCAL. Check eg. there has been a password check error. check with the MML command IWX. If the value of the supplementary information is 06. an error message is output. direct the printouts to another file. It is recommended that the printouts are directed to a ring file. RECOMMENDATION: Direct the printouts also to the BBU-0. If the file is faulty . if there is space in the file for the printouts. remove the blocking with the MML command ICB. ZIWX::WS::MMDIRE:CCALENDAR. MMI SYSTEM FILE ERROR.LOG. that the file structure is correct (the commands are one below the another in the right order and comments are within the comment characters). If the disk is damaged. 3. Fill in a Problem report and send 186 Id:0900d805805de168 DN99580853 Issue 08A . edit it with the MML command IEE. Check with the MML command ISI that the disk is not damaged.

1. b) you cannot execute the command from the command calendar. If the calendar task has been blocked. Do the following: 1. those commands that output questions which the user needs to answer before the command can be executed. If the value of the supplementary information field is 09. with the MML command IAA. If 2427 is set. the calendar task cannot be executed. If the value of the supplementary information is 08. there has been a data transmission error. These commands include the interactive commands. Check whether the alarm 2427 is set.RNC disturbances (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR it to your local Nokia Siemens Networks representative. If the value of the supplementary information is 07. Change the state of the OMU into WO with the MML command USC. For example. loading the MML program that executes the command to memory has failed. If the task is blocked. remove the blocking with the MML command ICB. If the calendar task has been blocked. Do the following: 1. Execute the command normally without using the command calendar. 2. that is. 2. Fill in a Problem report and send it to your local Nokia Siemens Networks representative. ICI is an interactive command. act according to its instructions. 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. If the value of the supplementary information is 0A. you can change. DN99580853 Issue 08A Id:0900d805805de168 187 . If you want to execute the task from the command calendar. You can use the command IAA only if you have the authority to use it. 2. remove the blocking with the MML command ICB. remove the blocking with the MML command ICB. 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. Those commands that require the user only to confirm the execution of the command (Y/N) can be executed from the command calendar. either the command calendar authorities or the authorities of that user who has added the task into the command calendar.

Check with the MML command IID. 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. another user is using some command that must not be used at the same time with the command in question. If the value of the supplementary information is 10. It is recommended that the printer LPT-0 and BBU-0 are connected to the COMCAL: in this case. 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. for example. the logical file COMCAL needed in the execution of the calendar tasks has not been created. the command calendar cannot at the same time execute the commands of the command group WR. 3. If.1432 DISTURBANCE IN COMMAND CALENDAR RNC disturbances (1000-1999) If the value of the supplementary information is 0B. ERROR IN COMMAND CALENDAR. If the command task has been blocked. The following command creates the file BYTEBASKET: ZIIF::BYTEBASKET. act according to the instructions of the alarm 2430. create the semipermanent logical file and connect it to BBU-0 with the MML command IIF. Find out why the logical file COMCAL has not been created.S:DEV=BBU-0. create it and connect the printer that you want to it. 0F. 188 Id:0900d805805de168 DN99580853 Issue 08A . 0E. another user is executing the command USU. remove the blocking with the MML command ICB. First. If the value of the supplementary information is 0C. 2.S:DEV=LPT-0 b) Connect the BBU-0 to the logical file COMCAL. the calendar task cannot be executed because at the same time that the command calendar is executing a specific command. If the logical file COMCAL has not been created. 1. whether the logical file COMCAL has been created: ZIID::COMCAL. Do the following: a) Create a logical file COMCAL and connect a printer LPT-0 with the MML command IIF: ZIIF::COMCAL. 0D.

RNC disturbances (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR Check whether the COMCAL is in the PLFILEG2 file. If the COMCAL is not found in the PLFILEG2 file. 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.PLFILEG2. b) Output the contents of the file with the MML command IBT: ZIBT:WDU. the software build contains the wrong version of the PLFILEG2 file.S. there has been an error.IMG. If the value of the supplementary information is 11. Wait until the other calendar task is finished or that the connections of the COMCAL have been changed. The PLFILEG2 file is in the LFILES directory. DN99580853 Issue 08A Id:0900d805805de168 189 . Contact the local Nokia Siemens Networks representative. Find out the error with the help of alarms and logs. If the COMCAL is in the PLFILEG2 file. 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. Cancelling No cancelling.

The signalling point indicated by the originating point code given in the 3rd supplementary information field has not identified the signalling network management message. a heading code that was not identified Instructions The alarm requires no actions. The heading code of the signalling network management message is given in the 6th supplementary information field.1548 MTP CONFUSION MESSAGE RECEIVED RNC disturbances (1000-1999) 102 1548 MTP CONFUSION MESSAGE RECEIVED Meaning An MTP confusion message has been received in the exchange. i. Supplementary information fields 1 2 3 4 5 6 SIO in MTP confusion message destination point code in MTP CONFUSION message originating point code in MTP CONFUSION message heading code of MTP CONFUSION message implementation level indicator in MTP CONFUSION message confusion_msg_id in MTP CONFUSION message. 190 Id:0900d805805de168 DN99580853 Issue 08A .e. Cancelling No cancelling.

RNC disturbances (1000-1999) 1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED 103 1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED Meaning The critical limit of a security reporting counter has been reached. DN99580853 Issue 08A Id:0900d805805de168 191 . Check. against the report. find out why the critical limit was exceeded. if necessary. and modify. if anything out of the ordinary has occurred. Supplementary information fields 1 the security reporting counter that has reached its critical limit: 02 04 05 07 08 10 11 12 13 14 15 16 17 18 19 counter counter counter counter counter counter counter counter counter counter counter counter counter counter counter for for for for for for for for for for for for for for for unauthorised users of service terminal unauthorised users of the network use of network: unauthorised commands unauthorised MML users unauthorised MML commands unsuccessful saves in MML log file unsuccessful MML command checks unsuccessful subscriber identifications unidentified IMSI numbers IMEI IDs on black list unidentified IMEI IDs IMEI IDs in a grey list unsuccessful saves in service terminal log file SSH sessions unauthorised SSH sessions Instructions Use the MML command IRO:<report type> to output a detailed security report. the limit value of the counter in question so that it reflects more accurately what is considered a normal situation. Cancelling No cancelling. if the counter's value was normal. However.

alarm limit of files as a percentage length of monitoring period in days starting date of monitoring period number of event records in file 192 Id:0900d805805de168 DN99580853 Issue 08A . Exact file and incoming events can be investigated using ZIRP and ZIRO report.1570 SECURITY LOG ALARM LIMIT REACHED RNC disturbances (1000-1999) 104 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. This means. that some security reporting event causes such a high load that defined file size is not as big as needed. Supplementary information fields 1 2 3 4 Instructions Predefined limit of number of events in some security reporting file is exceeded. Cancelling No cancelling.

Supplementary information fields 1 type of buffer 01 buffer for sending messages to next stage family identifier of the sender process identifier of the sender type of the receiver's computer unit See administering recovery and unit working state index of the receiver's computer unit family identifier of the receiver process identifier of the receiver time of the first lost alarm event amount of the lost alarm events 2 3 4 5 6 7 8 9 Instructions The alarm requires no actions. has overflown. It may also lead to loss of some alarms or alarm cancellations.RNC disturbances (1000-1999) 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL 105 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL Meaning A buffer used as a temporary storage for messages. which require an acknowledgement from the counterpart in the alarm system. Cancelling No cancelling. and in the communication between the centralised part of the alarm system and the network element level alarm system. DN99580853 Issue 08A Id:0900d805805de168 193 . The buffer overflow may cause temporary unbalance in the alarm situation maintained in the different parts of the alarm system. This kind of a buffer is used in the communication between the distributed part and centralised part of the alarm system.

subobject not specified index of subobject (of the I/O device) suspected faulty FFFF.1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM RNC disturbances (1000-1999) 106 1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM Meaning The alarm system has found. having received several different observations to that effect. Cancelling No cancelling. that the I/O device is defective. The I/O system has been informed of the fault in the device. subobject not specified the alarm manual numbers (in BCD format) of the observations that first supported the fault hypothesis 2 3-8 Instructions The alarm requires no actions. Supplementary information fields 1 type of subobject (of the I/O device) suspected faulty FFFF. 194 Id:0900d805805de168 DN99580853 Issue 08A .

Supplementary information fields 1 type of subobject (of a functional unit) suspected faulty FFFF. subobject not specified the alarm manual numbers (in BCD format) of the observations that first supported the fault hypothesis 2 3-8 Instructions The alarm requires no actions. having received several different observations to that effect. that a functional unit (not the I/O device) is defective.RNC disturbances (1000-1999) 1598 UNIT FOUND FAULTY BY ALARM SYSTEM 107 1598 UNIT FOUND FAULTY BY ALARM SYSTEM Meaning The alarm system has found. DN99580853 Issue 08A Id:0900d805805de168 195 . Cancelling No cancelling. subobject not specified index of subobject (of a functional unit) suspected faulty FFFF. The recovery system has been informed of the faulty unit.

and contact your local Nokia Siemens Networks representative. If the disturbance keeps recurring. Cancelling No cancelling. thus correcting the failure automatically. i. i. Supplementary information fields 1 database index (although some database applications still need this information. and the alarms. in which the number (update_seq_number) is inconsistent with the disk updating system's view of what that number should be. Either the DBMANA or the disk updating system has failed and may have lost log buffers. an update.1660 UPDATE NUMBER MISMATCH RNC disturbances (1000-1999) 108 1660 UPDATE NUMBER MISMATCH Meaning The database management system (abbr. 2 3 4 5 196 Id:0900d805805de168 DN99580853 Issue 08A . database name and database occurrence) database name number of database occurrence database location family ID of the program block handling the database Instructions The system corrects the fault automatically. DD2MAN.e. it is copied from the RAM memory to the disk. and the database will be dumped.e. The disk updating system will now no longer receive log buffers from the database in question. it is becoming more common that the database is identified by the values of the following two supplementary information fields. DBMANA) has sent the database disk updating system. save the log files of the database unit and the disk updating system unit.

save the black box of the unit after the reset for further investigation. the management system program block acknowledges supervision messages negatively. 2 3 4 DN99580853 Issue 08A Id:0900d805805de168 197 . or. i. although nowadays the database is usually identified based on the values of the following two supplementary information fields. As the program block is a critical one.e. the system resets the database unit. database name and database occurrence) database name number of database occurrence error code indicating the reason why the fatal error state was entered. and the system has been set to the "fatal error" state. In the "fatal error" state. alternatively. Cancelling No cancelling. You can check its meaning in General Error Messages of System Instructions Save the log of the database unit.RNC disturbances (1000-1999) 1661 DATABASE MANAGER IN FATAL ERROR STATE 109 1661 DATABASE MANAGER IN FATAL ERROR STATE Meaning An error occurred in the database management system. Supplementary information fields 1 database index (some database applications still need this information.

1662 DATABASE LOADING ERROR

RNC disturbances (1000-1999)

110 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) database name number of database occurrence 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 the DBMANA on the WO side does not answer when the DBMANA on the SP side asks for permission to load time supervision expires on the WO side of the database unit during the first load attempt time supervision expires on the SP side of the database unit during the first load attempt

2 3 4

02 03 04

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 database unit's WO side.

198

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

1662 DATABASE LOADING ERROR

Cancelling No cancelling.

DN99580853 Issue 08A

Id:0900d805805de168

199

1663 HAND RESERVATION ERROR IN DATABASE MANAGER

RNC disturbances (1000-1999)

111 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) database name number of database occurrence error code indicating why the hand reservation failed. You can check its meaning in General Error Messages of System 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)

2 3 4

5

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.

200

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

1682 SCDFLE UPDATE FAILURE

112 1682 SCDFLE UPDATE FAILURE
Meaning The distribution or updating of the Working State and Configuration File (SCDFLE) has failed. If alarm object is not active SYM, there will be instantenous discrepancy between SCDFLE file of active SYM and alarm object unit. SCDFLE supervision tries to correct discrepancy, if possible. Supplementary information fields 1 the reason for the failure. See The General Error Messages of System. the type of the unit, whose update failed the index of the unit updating tasks. The hexadecimal value in this field should be interpreted as a binary value, in which case the significance of the bit (0 = task not active/1 = task active) is read in following way: 000000000000000000000001 working state update 000000000000000000000010 unit status update 000000000000000000000100 logical address change 000000000000000000001000 physical address change 000000000000000000010000 2N or N+1 unit switchover 000000000000000000100000 functional unit create 000000000000000001000000 functional unit remove 000000000000000010000000 address tables update 000000000000000100000000 status data update 000000000000001000000000 restart status data update 000000000000010000000000 attribute update 000000000000100000000000 N+1 unit switchover pair create 000000000001000000000000 N+1 unit switchover pair delete 000000000010000000000000 system status update 000000000100000000000000 unit move from trial system to original system 000000001000000000000000 unit move from original system to trial system 000000010000000000000000 network element split create 000000100000000000000000 network element split delete 000001000000000000000000 logical address flush of specified unit instance 000010000000000000000000 logical addresses flush of specified unit type 000100000000000000000000 all logical addresses flush

2 3 4

DN99580853 Issue 08A

Id:0900d805805de168

201

1682 SCDFLE UPDATE FAILURE RNC disturbances (1000-1999) 001000000000000000000000 Instructions own slice update The alarm requires no actions. Cancelling No cancelling. 202 Id:0900d805805de168 DN99580853 Issue 08A .

You can check the supporting amount of the alarm with the MML command ZARO. See General Error Messages of System the numbers of the first alarms on the basis of which the unit was found faulty If the reason of recovery action was not originated by alarm system. Cancelling No cancelling. Supplementary information fields 1 2 3 4-6 the address of the unit that detected the fault the identifier of the process family that detected the fault the reason for the fault. DN99580853 Issue 08A Id:0900d805805de168 203 . The alarm supports activation of automatic recovery for the object unit.RNC disturbances (1000-1999) 1683 PASSIVE UNIT FAULTY 113 1683 PASSIVE UNIT FAULTY Meaning A spare unit of a 2N unit or of a replaceable N+1 redundant unit is faulty. the value is FFFF 7 indicates whether the alarm is set by periodical working state background checking 00 alarm is not set by background checking 01 alarm is set by background checking Instructions The alarm requires no actions.

Cancelling No cancelling. The alarm is issued from both units. The reason may be a fault in the active or in the passive unit. message bus address of the unit where the error occurred family identifier of the program block that made the error load group where the warming failed file where the warming failed 3 4 5 6 Instructions The alarm requires no actions. 204 Id:0900d805805de168 DN99580853 Issue 08A . Supplementary information fields 1 2 family identifier of the alarm detector error code returned by the alarm detector. The alarm supports the activation of the automatic recovery for the object unit.1684 SPARE UNIT WARMUP FAILURE RNC disturbances (1000-1999) 114 1684 SPARE UNIT WARMUP FAILURE Meaning The warm-up of the spare unit fails. You can check the supporting amount of the alarm with the MML command ARO. You can check its meaning in General Error Messages of System.

message bus address of the unit where the error occurred family identifier of the program block that made the error load group where the loading failed file where the loading failed 3 4 5 6 Instructions The alarm requires no actions. The alarm supports the activation of the automatic recovery for the object unit. You can check its meaning with a command of the service terminal extension MRS or in General Error Messages of System in customer documentation. You can check the supporting amount of the alarm with the MML command ARO. DN99580853 Issue 08A Id:0900d805805de168 205 . Cancelling No cancelling. Supplementary information fields 1 2 family identifier of the error detector error code returned by the error detector.RNC disturbances (1000-1999) 1685 UNIT RESTART FAILURE 115 1685 UNIT RESTART FAILURE Meaning The restarting of the computer unit fails.

The former active unit ends up in TE state 08 Caused by a fault observed in an active unit. Application programs are asked for permission to execution User originated forced switchover where active unit is replaced by a standby in SP state. Supplementary information fields 1 failed recovery action. Active OMU is included in restart User originated controlled switchover where a working unit is replaced by a hot standby unit without standby restart. If active system maintenance unit (OMU) participates in restart. If the failed recovery action was a user-originated controlled recovery action (e. the operating capacity has decreased depending on the functionality allocated to the failed functional unit. former active unit ends up in SP state 05 0C 06 or 07 Caused by a unit found being in an inappropriate state.1687 RECOVERY ACTION FAILURE RNC disturbances (1000-1999) 116 1687 RECOVERY ACTION FAILURE Meaning The recovery action of the functional unit has failed. the failed recovery action had no effect on the network element. state change or switchover). The active unit is replaced by a standby unit even if it (the standby) is in TE or SEOU state. The former active unit ends up in SP state. a soft switchover (no restart to new active unit) is performed. If the functional unit remains active. Active unit 206 Id:0900d805805de168 DN99580853 Issue 08A . If the failed recovery action was a system-originated recovery action concerning active functional unit (WO-EX). If a hot standby exists. application programs in active OMU are asked for permission to execution 02 03 04 User originated forced system restart System restart caused by failure of a system critical unit System restart caused by failure of a system critical unit.g. recovery system may try a new more powerful recovery action after this alarm. The action taken by recovery is one from the list below: 01 User originated controlled system restart.

e. a power failure. a soft switchover (no restart to new active unit) is performed.RNC disturbances (1000-1999) 1687 RECOVERY ACTION FAILURE is replaced with hot standby unit. Diagnostics are activated 15 An active unit is put to TE state after it has gone inoperative eg. disturbed unit ends up in state SP and is restarted Caused by an active unit making a spontaneous restart. Application programs are asked for permission to execute it User originated forced restart of unit A unit is restarted in order to recover from a disturbance. due to power failure N+1 replacable unit is put to WO state by system's resource monitoring N+1 replacable unit is is put to SP state by system's resource monitoring 18 19 DN99580853 Issue 08A Id:0900d805805de168 207 . disturbed unit ends up in TE state 0E User originated controlled restart of unit. in operation Caused by restart of an active unit. Active unit is replaced by a hot standby. Application programs are asked for permission to execution User originated forced working state change of unit State change of unit requested by system's supervision 0F 11 10 12 14 13 16 or 17 A failed unit is put to TE state. the standby unit is also restarted for synchronization (file and code consistency) reasons User originated controlled state change of unit. Active unit is replaced by standby in SP state. Active unit is replaced by a hot standby. critical process family failure. eg. a critical application failing due to overload. If a hot standby exists. Diagnostics are activated if unit can be diagnosed 0D Caused not by a fault but a disturbance in operation of unit.g. disturbed unit ends up in state SP and is restarted 0B 09 or 0A Caused by an active unit gone inoperative due to eg. Former active unit ends up in TE state.

1687 RECOVERY ACTION FAILURE

RNC disturbances (1000-1999)

1A 1B

Specific functional unit status bit is set for unit by user Specific functional unit status bit is cleared from unit by user Functional unit gets FLTY status on. The unit has failed but remains in use due to overall situation in network element Functional unit is added or removed to/from network element configuration by user System cancels trial configuration due to critical unit failure on original System Trial configuration is created controlled by user. Initial configuration can be defined to be OMU, CORE or BASE Trial configuration is created forced by user. Initial configuration can be defined to be OMU, CORE or BASE Trial configuration is cancelled by user Functional unit is moved controlled from system to other by user. Unit may not belong to BASE of either side Functional unit is moved forced from system to other by user. Unit may not belong to CORE of either side. Application programs may not prevent the move The units carrying traffic are moved controlled from system to system (cutover of traffic) by user The units carrying traffic are moved forced from system to system (cutover of traffic) by user. Application programs may not prevent the cutover The configuration on trial side made in create can be expanded or reduced to OMU, CORE or BASE by user The configuration on trial side made in create can be expanded or reduced to OMU, CORE or BASE by user. States of units participating are not restricted

1C

22

23

24

25

26 27

28

29

2A

2B

2C

2

computer address of the functional unit where the failed recovery action was observed family identifier which observed the failed recovery action computer address of the functional unit where the error occurred

3 4

208

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

1687 RECOVERY ACTION FAILURE

5 6

family identifier that made the error error code of the failed recovery action. You can check its meaning in general error messages of system Instructions The alarm requires no actions. Cancelling No cancelling.

DN99580853 Issue 08A

Id:0900d805805de168

209

1800 SCSI ADDRESS ILLEGAL

RNC disturbances (1000-1999)

117 1800 SCSI ADDRESS ILLEGAL
Meaning The system has detected an error in the SCSI configuration file of I/O device state handling. The device in question has an illegal bus number, SCSI ID or logical unit number or it has the same bus, ID and logical unit number as some other SCSI device. State handling of the conflicting device does not work. Supplementary information fields 1 2 3 the SCSI bus of the device in the configuration file the SCSI ID of the device in the configuration file the logical unit number of the device in the configuration file Instructions Correct the SCSI configuration file (IDWCONGX.XML). Restart the computer unit where the alarm is set with MML command USU. Cancelling No cancelling.

210

Id:0900d805805de168

DN99580853 Issue 08A

RNC disturbances (1000-1999)

1801 MASS MEMORY FILE BACKUP FAILURE

118 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 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.

2

DN99580853 Issue 08A

Id:0900d805805de168

211

because of which information could not be recorded within the defined time period. the background processing of the backup copy task has been interrupted. You can check its meaning in General Error Messages of System name identifier of the copy task whose recording in the copy log failed.1802 BACKUP COPY LOG FAILURE RNC disturbances (1000-1999) 119 1802 BACKUP COPY LOG FAILURE Meaning Saving the copy task information in the disk's copy log has failed at least partly. 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. a disturbance or a fault has been detected in the disk system and it has prevented the normal use of the copy log. 2861 NO ACCESS TO DISK. If alarm 1801. even though information on it is not available in the log. a fault in an I/O device. 2 212 Id:0900d805805de168 DN99580853 Issue 08A . MASS MEMORY FILE BACKUP FAILURE. The fault may have been caused. the copy task was successful. If alarm 1801. Otherwise. The I/O system has however failed to record some (or possibly all) information. for example. 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. is set simultaneously with this alarm. MASS MEMORY FILE BACKUP FAILURE. This alarm has no effect on the operation of the rest of the system. Supplementary information fields 1 general error message of the system. is not set simultaneously with this alarm for the same copy task. and 2862 DISK CHECKSUM ERROR. by a disturbance in the I/O system. If disk alarms are set simultaneously with this alarm. which you can interrogate with the service terminal command ZGD. 2860 DISK FAILURE. You may find more information in the system log. The following alarms are disk alarms: 0860 DISK NOTICE. or a load peak of the unit. 1860 DISK DISTURBANCE.

DN99580853 Issue 08A Id:0900d805805de168 213 . Cancelling No cancelling.RNC disturbances (1000-1999) 1802 BACKUP COPY LOG FAILURE If alarm 1801 is also set. you should start the copy task again.

If the device is diagnosed to be faulty it has to be replaced. Cancelling No cancelling 214 Id:0900d805805de168 DN99580853 Issue 08A . contact your local Nokia Siemens Networks representative. If the error is not temporary. the device may be faulty and the system will diagnose it. If the diagnostics indicate that the device is working properly and the problem still persists. The alarm supports the activation of the automatic recovery for the object unit. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or in the General Error Messages of System Instructions If the alarm appears occasionally. Supplementary information fields 1 2 3 4 the SCSI bus the device is connected to the SCSI ID of the device the logical unit number of the device general error message of the system. You can check the supporting amount of the alarm using the ARO MML command. See instructions on changing mass memory units.1803 SCSI MALFUNCTION RNC disturbances (1000-1999) 120 1803 SCSI MALFUNCTION Meaning The system has detected a temporary (not serious) error while accessing a SCSI device. The fourth additional information field indicates the cause for this disturbance. it requires no actions.

RNC disturbances (1000-1999) 1804 IP ROUTING RESOURCE SHORTAGE 121 1804 IP ROUTING RESOURCE SHORTAGE Meaning The IP Routing feature is experiencing an unexpected resource shortage. Cancelling No cancelling. DN99580853 Issue 08A Id:0900d805805de168 215 . 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.

if possible. Handling printing tasks in non-spoolered mode is more unreliable than in spoolered mode. The failure does not disable the printing system. are executed when the spooler is in use again. for example. but new printing tasks are handled in non-spoolered mode. The tasks that are in spooler when failure occurs.1806 PRINTER SPOOLER DISABLED RNC disturbances (1000-1999) 122 1806 PRINTER SPOOLER DISABLED Meaning Printing system cannot use the spooler. The system changes automatically from the non-spoolered mode to the spoolered mode when the spooler is in use again and all non-spoolered tasks are completed. when the SCSI bus or hard disks go to TEST state. Set the SCSI bus and hard disks to WO state using the IHE MML command. Supplementary information fields Instructions To find out the reason for SCSI bus's or hard disk's wrong operating state. This happens. check whether there are other alarms active using the AAP MML command. Follow the instructions given in these alarm descriptions. Cancelling No cancelling. 216 Id:0900d805805de168 DN99580853 Issue 08A .

Fill in a Problem Report and send it to your local Nokia Siemens Networks representative. IP configuration files (/etc/if. /etc/ipoa_int. the applications will get "no service" return code when calling the library routines. 5. Here are the possible problems: 1. report that too to the problem report.dat. /etc/ipoa. Under this situation. Allocate common buffer failed: Add both operating and user logs to the problem report.conf. Read/write disk files failed: Add both operating and user logs to the problem report. DN99580853 Issue 08A Id:0900d805805de168 217 ./RUNNING/LFILES/YEMIP6GX. 2.XML) are missing or corrupted: Get configuration files from the W0 disk and attach them to the problem report and if those files do not exist. 4. 3. Supplementary information fields Instructions Check the computer log to find out the possible cause of the alarm.dat. If the application has failed to receive IP configuration data. Event Forwarder problem: Add user logs to the problem report.RNC disturbances (1000-1999) 1809 IP CONFIGURATION INQUIRY SERVICE FAILED 123 1809 IP CONFIGURATION INQUIRY SERVICE FAILED Meaning The alarm is set if IP management dynamic interface library (YANLIB) cannot provide IP configuration inquiry services for applications. Name Server problem: Add user logs to the problem report. it might make the Network Element unable to provide IP calls services.

1809 IP CONFIGURATION INQUIRY SERVICE FAILED RNC disturbances (1000-1999) Cancelling No cancelling. 218 Id:0900d805805de168 DN99580853 Issue 08A .

RNC disturbances (1000-1999) 1900 DEGRADED SLIP FREQUENCY 124 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. Instructions The alarm requires no actions. Supplementary information fields 1 2 unit type E1 or T1 circuit number or ETS index. The slips are monitored for a 24 h period.. DN99580853 Issue 08A Id:0900d805805de168 219 . TCSM's internal PCM circuit number 0d. Cancelling No cancelling. when unit type is TCSM.7d. when unit type is ET.