Alarm

Disturbance Printouts (1000-1999)

DN70600744Issue 16-0 en

# Nokia Siemens Networks 1 (332)

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia 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.

2 (332) # Nokia Siemens Networks DN70600744Issue 16-0 en


Contents

Contents 3

List of figures 10

1 Summary of changes 111.1 Changes made between issues 16-0 and 15-0 111.2 Changes made between issues 15-0 and 14-0 111.3 Changes made between issues 14-0 and 13-0 111.4 Changes made between issues 13-0 and 12-0 121.5 Changes made between issues 12-0 and 11-0 13

2 List of alarms 152.1 1000 SPEECH SAMPLE FILE LOADING FAILED 242.2 1001 UNIT RESTARTED 252.3 1002 RAM FAILURE 272.4 1003 PARITY ERROR IN RAM 272.5 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS 282.6 1005 PLUG-IN UNIT RESTARTED 292.7 1007 RESTARTED PROGRAM BLOCK 302.8 1008 MML PROGRAM RESTARTED 302.9 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE 312.10 1012 EXCESSIVE RESTARTS OF UNIT 322.11 1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED 322.12 1015 OPERATING SYSTEM ERROR COUNTER INCREASED 332.13 1016 MB INTERFACE FAILURE 342.14 1018 PROGRAM BLOCK COMMUNICATION ERROR 352.15 1019 PROGRAM BLOCK ACTION FAILURE 362.16 1020 PROGRAM BLOCK START UP FAILURE 372.17 1021 PROGRAM BLOCK REWARMING STARTED 382.18 1022 PROGRAM BLOCK WARMUP FAILURE 392.19 1023 EXCESSIVE DISTURBANCES IN SUPERVISION 402.20 1024 HAND PROCESS ERROR IN PROGRAM BLOCK 412.21 1025 REPORT LOST IN REPORTING 422.22 1026 ASM OVERLOAD 432.23 1028 RESTARTED PROGRAM BLOCK IN PREPROCESSOR UNIT 442.24 1029 SCCP STP MESSAGE PREVENTION 452.25 1032 DPNSS CIRCUIT OUT OF USE 472.26 1033 OSI CLNS CONFIGURATION FAILED 482.27 1034 MAXIMUM SEQUENCE NUMBER OF OSI CLNS EXCEEDED 492.28 1035 UPU MESSAGE RECEIVED 502.29 1036 EXCESSIVE RESTARTS OF PLUG-IN UNIT 512.30 1037 ECHO CANCELLER DAUGHTERBOARD LOADING FAILURE 522.31 1040 EVENT LOG OVERLOAD 532.32 1044 ERROR IN SWITCH COMPARE TEST 542.33 1045 ERROR BETWEEN MARKER TABLES AND SWITCH CONTROL

MEMORY 552.34 1047 NO RESPONSE FROM CONTROLLER OF SWITCHING

NETWORK 57

DN70600744Issue 16-0 en


Contents

2.35 1048 CONTROLLER OF SWITCHING NETWORK RESTARTED 572.36 1049 SEMIPERMANENT MULTICHANNEL CONNECTION MISSING 582.37 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE 592.38 1053 OVERFLOW IN GAP TABLE 602.39 1054 INCORRECT CHARGE RATE 612.40 1055 TCAP TRANSACTION FAILURE 612.41 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM 632.42 1058 ERROR IN SMUX PLUG-IN UNIT 652.43 1059 ERROR BETWEEN MARKER TABLES AND LSW CONTROL

MEMORY 662.44 1061 ERROR IN SWITCH COMPARE TEST 672.45 1062 ERROR BETWEEN MARKER TABLES AND SWITCH CONTROL

MEMORY 682.46 1064 UNIT UPDATE FAILURE 692.47 1065 DISK UPDATE FAILURE 692.48 1066 LOAD OBSERVATION REPORT OUTPUT FAILURE 702.49 1070 CCS7 PROGRAM BLOCK DATA ERROR 722.50 1071 PROCESSOR TIME SHORTAGE 732.51 1072 SIGNALLING LINK OUT OF SERVICE 742.52 1073 V5 DATA LINK LAYER PROTOCOL MISMATCH 772.53 1074 EXCESSIVE ERROR RATE ON V5 C-CHANNEL 782.54 1075 EXCESSIVE RETRANSMISSIONS ON V5 C-CHANNEL 792.55 1076 FORCED LIGHTWEIGHT SCHEDULING 802.56 1077 FREE STACK SIZE BELOW LIMIT 812.57 1078 PROCESS EXCEPTION 822.58 1079 UNSOLICITED V5 DATA LINK RE-ESTABLISHMENT 832.59 1080 PROCESS STOPPED 842.60 1082 HAND USAGE LIMIT EXCEEDED 862.61 1083 SEMAPHORE USE ERROR 872.62 1084 V5 ISDN USER PORT FAILURE 882.63 1085 V5 ISDN USER ACCESS OVERLOAD 902.64 1088 CONNECTION ERROR BETWEEN MSC AND SMSC 912.65 1089 DYNAMIC LDT SLOTS EXHAUSTED 932.66 1090 BUFFER HANDLE ERROR 942.67 1091 TOO MANY EXECUTED SUBANALYSES IN EXTENDED

PREANALYSIS 942.68 1092 COMMUNICATION FAILURE IN FIELD REPORTING 952.69 1093 OUTPUT FAILURE IN FIELD REPORTING 962.70 1095 TRAFFIC MEASUREMENT OUTPUT FAILURE 982.71 1096 TRAFFIC ANALYSIS COMMUNICATION FAILURE 992.72 1097 TRAFFIC ANALYSIS OUTPUT FAILURE 1002.73 1098 TOO LONG MESSAGE 1012.74 1099 FAILURE IN TRAFFIC SAMPLING 1022.75 1101 LSP RESTARTED 1022.76 1102 LSP RAM FAILURE 1032.77 1103 SIGNALLING MEASUREMENT REPORT LOST 1042.78 1104 NO RESPONSE TO LSP SUPERVISION MESSAGE 1062.79 1105 LINE SIGNALLING RECEIVE OVERLOAD 1072.80 1107 LINE SIGNALLING SEND OVERLOAD 1082.81 1108 LINE SIGNALLING SEND OVERLOAD 1092.82 1111 RESTART DUE TO TIME OUT REQUESTED 1092.83 1113 STATISTICS MEASUREMENT OUTPUT FAILURE 110



2.84 1116 ERROR IN CHARGING 1122.85 1117 ERROR IN LINE SIGNALLING 1122.86 1118 UNKNOWN LINE SIGNAL 1132.87 1119 ERROR IN LINE SIGNALLING INCOMING MESSAGE 1142.88 1120 ERROR IN LINE SIGNALLING PARTNER PROGRAM BLOCK 1152.89 1121 CIRCUIT CLEAR MISSING 1162.90 1122 IMPULSE NOT IN TOLERANCES 1172.91 1123 NUMBER NOT IN TOLERANCES 1182.92 1125 TRIAL CONFIGURATION DELETED 1192.93 1127 VANG POWER SUPPLY FAILURE 1192.94 1128 EXCESSIVE DISTURBANCES IN FILE LOADING 1202.95 1130 EXTERNAL CALL CLEARING 1212.96 1136 SIGNALLING MESSAGE DISTRIBUTION ERROR 1222.97 1137 INCORRECT SIGNALLING MESSAGE FROM SIGNALLING

TERMINAL 1232.98 1139 FIELD REPORT OF ROUTING COMPONENTS FAILED 1242.99 1140 FREE LDT SLOT COUNT BELOW LIMIT 1252.100 1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL 1262.101 1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED 1272.102 1143 AMOUNT OF FREE MEMORY REDUCED 1292.103 1144 FREE BUFFER HEADERS EXHAUSTING 1302.104 1145 FAILURE IN CALCULATING ACC CONGESTION LEVEL 1312.105 1147 MESSAGE QUEUE OVERFLOW 1322.106 1148 EXCESSIVE TRAPS 1332.107 1153 ERROR IN DIAL ANALYSIS DATA 1342.108 1155 CONNECTION FAILED IN GSW/SWI 1352.109 1162 FILE SYSTEM COMMUNICATION ERROR 1362.110 1164 TIME NOT RECEIVED FROM SATELLITE 1372.111 1165 BUFFER ALLOCATION FAILED 1382.112 1166 FAILURE IN ACCESSING NPDB 1392.113 1167 ERROR IN CAS REGISTER SIGNALLING 1402.114 1168 DEFAULT ROUTING CALL 1422.115 1169 FREEZING PERIOD OF SS7 REPORTING LOST 1432.116 1170 NOT ENOUGH DIGITS IN CALLED NUMBER FOR EXTENDED

PREANALYSIS 1452.117 1172 ASS PLUG-IN UNIT RAM FAILURE 1462.118 1173 SYNCHRONIZATION OF PROCESSES RESTARTED IN

COMMUNICATION LINK 1472.119 1174 NO RESPONSE TO ASS SUPERVISION MESSAGE 1482.120 1175 INTERNAL SIGNALLING SEND OVERLOAD 1482.121 1176 INTERNAL SIGNALLING RECEIVE OVERLOAD 1492.122 1177 T1 PCM REMOTE END FRAME LOST 1502.123 1178 PREPROCESSOR UNIT DISTURBANCE 1512.124 1182 PREPROCESSOR UNIT RESTARTED 1512.125 1190 EXCESSIVE ERRORS IN SCP 1522.126 1191 POSITION ESTIMATE NOT AVAILABLE FOR EMERGENCY

CALL 1532.127 1192 SSCOP TRANSMIT BUFFER OVERFLOW 1542.128 1194 DYNAMIC ROUTING SEARCH ERROR 1552.129 1195 USSD SERVICE INFORMATION NOT FOUND 1562.130 1197 INCONSISTENCY IN THE SYNCHRONIZATION OF THE NPDB

DATABASES 157

DN70600744Issue 16-0 en


Contents

2.131 1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION 1582.132 1204 WATCHDOG CAUSES UNIT RESTART 1592.133 1207 UNITS WORKING STATE DATA CORRUPTED IN THE

SYSTEM 1592.134 1209 ECHO CANCELLER SPARE CHIP FAILURE 1602.135 1210 PHASE ADVANCE OF TIMING SIGNAL CHANGED 1612.136 1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED 1622.137 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED 1632.138 1222 DATA WRITING VIA VDS DEVICE FAILED 1652.139 1224 MISSING MOLIMITER FOR SMSC LINK 1662.140 1228 UNIT SUPERVISION NOT FUNCTIONING 1662.141 1233 IP ENTITY IS NOT REACHABLE 1672.142 1234 UPDATE OF PASSWORD VALIDITY TIME FAILED 1692.143 1235 FQDN NOT PRESENT IN IEIFIL 1692.144 1236 AN SI7 FAILURE OCCURED 1712.145 1239 DSP SUPERVISION FAILURE 1722.146 1240 SCCP DISTURBANCE 1722.147 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE

ERROR 1752.148 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR 1792.149 1243 DECODING ERROR OF THE RANAP-MESSAGE 1822.150 1244 RUNNING OUT OF MESSAGE BUFFERS 1832.151 1245 RANAP ERROR INDICATION MESSAGE RECEIVED FROM

PARTNER MSC 1852.152 1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED

AGE 1852.153 1250 DATA LINK LAYER PROTOCOL MISMATCH 1862.154 1251 EXCESSIVE RETRANSMISSIONS ON DATA LINK

CONNECTION 1872.155 1252 EXCESSIVE ERROR RATE ON DATA LINK CONNECTION 1892.156 1253 NO RESPONSE FROM PRIMARY RATE ACCESS

TERMINAL 1902.157 1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT 1912.158 1255 PRIMARY RATE ACCESS MESSAGE DISTRIBUTION

ERROR 1922.159 1256 INCORRECT PRD MESSAGE FROM PRIMARY RATE ACCESS

TERMINAL 1932.160 1257 FAULTY APM INFORMATION 1932.161 1259 TOO MANY SUBANALYSES IN USER PLANE ANALYSIS 1952.162 1260 X.25/ETHERNET DATA TERMINAL SPONTANEOUS

RESTART 1962.163 1261 OSI CHANNEL GROUP UNREACHABLE 1972.164 1262 OSI SERVICE PROVIDER RESET 1982.165 1263 OSI SERVICE PROVIDER INTERFACE ERROR 1982.166 1264 OSI INCOMING CALL DENIED 1992.167 1266 NO ACKNOWLEDGEMENT TO RESET RESOURCE 2002.168 1267 RNC OUT OF SERVICE IN MSC 2012.169 1268 RANAP ERROR INDICATION MESSAGE RECEIVED FROM

RNC 2032.170 1271 THE IU-INTERFACE RANAP-LEVEL TIMER EXPIRY 2042.171 1273 ASP ACTIVATION FAILED 2052.172 1274 IU-INTERFACE RESOURCE ALLOCATION FAILURE 212



2.173 1276 INCONSISTENCY OF THE NPDB DATABASES IN THE SRRI 2142.174 1280 INTERNAL COMMUNICATION CHANNEL FAILURE 2152.175 1282 ASSOCIATION PARAMETER FAILURE 2162.176 1288 DATABASE REPLICA STATE CONFLICT 2182.177 1293 SCCP GT SCREENING APPLIED 2192.178 1294 INFINITE LOOP IN HLR GENERAL ANALYSIS 2232.179 1295 TOO MANY SUBANALYSES IN HLR GENERAL ANALYSIS 2242.180 1300 SUPERVISION CONNECTION TO UNIT LOST 2252.181 1303 DB QUERY WARNING LIMIT EXCEEDED IN SRRU 2252.182 1305 ERROR IN SUBSCRIBER SIGNALLING INCOMING

MESSAGE 2262.183 1308 PRIMARY LDAP DIRECTORY SERVER ACCESS FAILED 2272.184 1312 RAM FAILURE IN PREPROCESSOR UNIT 2282.185 1313 FAILURE IN LI2M COMMUNICATION 2292.186 1314 LI2M RESTARTED 2302.187 1320 UMA RESOURCE ALLOCATION FAILURE 2302.188 1322 NO RESPONSE TO SUB SUPERVISION MESSAGE 2312.189 1328 VLR LOAD CONTROL UPPER LIMIT REACHED 2322.190 1333 ISUP SCREENING FILE OPENING ERROR 2332.191 1337 INTERCEPTION DISTURBANCE 2342.192 1340 HOTLINK FAILURE 2352.193 1343 AOIP RESOURCE ALLOCATION FAILURE 2352.194 1400 AFS RESTARTED 2362.195 1423 NO RESPONSE FROM MAIN CLOCK 2372.196 1425 OVERFLOW IN ALARM BUFFERING 2382.197 1431 MMI SYSTEM OVERLOAD 2382.198 1432 DISTURBANCE IN COMMAND CALENDAR 2392.199 1450 NO RESPONSE TO SYSTEM SUPERVISION MESSAGE 2452.200 1453 NO RESPONSE TO TIME INQUIRY 2462.201 1455 NO RESPONSE TO TIME ADJUST MESSAGE 2472.202 1532 FAULTY COMMON CHANNEL SIGNALLING MESSAGE 2472.203 1541 PROGRAM BLOCK RESTARTED IN COCA/EC1P 2492.204 1542 DSP RESTARTED 2502.205 1543 COCA/EC1P RAM FAILURE 2512.206 1544 DM2 FAILURE 2512.207 1545 DM2 ET ALARM 2522.208 1546 ERROR IN MEMORY HANDLING OF PROGRAM BLOCK 2532.209 1547 ERROR IN COMPONENT HANDLING 2552.210 1548 MTP CONFUSION MESSAGE RECEIVED 2572.211 1549 TSLS UNTESTED IN ROUTINE TEST 2582.212 1550 FAULTY NATIONAL USER PART MESSAGE 2592.213 1551 CCS USER PART ACKNOWLEDGEMENT MESSAGE

MISSING 2602.214 1552 FAULTY ISDN USER PART MESSAGE 2612.215 1556 HLR SPECIAL ROUTING INFORMATION 2622.216 1557 EVENT HANDLER CANNOT WORK PROPERLY DUE TO FILE

SERVICE FAILURE 2632.217 1558 RADIO NETWORK CONFLICT 2642.218 1559 A-INTERFACE CIRCUIT ALLOCATION FAILURE 2652.219 1560 BSC OR BTS OUT OF SERVICE IN MSC 2662.220 1561 DPNSS ACKNOWLEDGEMENT MESSAGE MISSING 2672.221 1562 ROUTINE TEST REPORTING FAILED 268

DN70600744Issue 16-0 en


Contents

2.222 1564 UNEQUIPPED CIC 2692.223 1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED 2702.224 1570 SECURITY LOG ALARM LIMIT REACHED 2712.225 1571 CALL INDEX RESERVATION FAILED 2722.226 1572 SMS SUBMIT PRIMITIVE ENCODING FAILURE 2742.227 1573 CONFLICT WITH DEFINED DIRECTION OF CIRCUIT/CIC 2742.228 1574 DATA ERROR FOUND BY PROTOCOL 2752.229 1575 COMPONENT NOT ACCEPTED BY REMOTE END 2762.230 1576 ERROR IN TIME CHARGING INTERFACE 2782.231 1577 SMS: NO RESPONSE FROM CO PROCESS 2792.232 1579 UNRELEASED CALL BECAUSE OF DELAYED RELEASE

(DRS) 2792.233 1581 NO CIC RECEIVED FROM BSC 2802.234 1583 LAPD MSG DISTRIBUTION PROBLEM 2812.235 1584 SCCP MESSAGE ROUTING ERROR 2822.236 1586 BTA TUP RELEASE ACKNOWLEDGEMENT MISSING 2832.237 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL 2842.238 1595 NEMU ALARM BUFFER OVERFLOW OCCURRED 2852.239 1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM 2862.240 1598 UNIT FOUND FAULTY BY ALARM SYSTEM 2872.241 1621 ERROR IN FILE ACCESS 2872.242 1623 ERROR DURING SUPERVISION 2882.243 1630 RAM FAILURE IN SYNCHRONIZATION UNIT 2892.244 1642 CIRCUIT/CIC BARRED OVER 5 MIN 2902.245 1643 CIRCUIT/CIC BLOCKED OVER 5 MIN 2912.246 1644 PROTOCOL MEASUREMENT REPORT TRANSFER

UNSUCCESFUL 2922.247 1645 PROTOCOL MESSAGE QUEUE FULL 2932.248 1646 PROTOCOL INTERNAL ERROR 2932.249 1647 OPERATION TIMER EXPIRY 2952.250 1648 CONFLICT IN MESSAGE PROTOCOL 2962.251 1651 DECODING ERROR OF THE A-INTERFACE BSSMAP-

MESSAGE 2972.252 1652 DECODING ERROR OF THE MESSAGE RECEIVED FROM THE

MS 2982.253 1653 THE A-INTERFACE BSSMAP-LEVEL TIMER EXPIRY 2992.254 1654 BSSMAP MESSAGE CONFUSION RECEIVED FROM BSC 2992.255 1657 TOO MANY EXECUTED SUBANALYSES IN ATTRIBUTE

ANALYSIS 3002.256 1658 NOT ENOUGH DIGITS IN CALLED NUMBER FOR ATTRIBUTE

ANALYSIS 3022.257 1660 UPDATE NUMBER MISMATCH 3032.258 1661 DATABASE MANAGER IN FATAL ERROR STATE 3042.259 1662 DATABASE LOADING ERROR 3052.260 1663 HAND RESERVATION ERROR IN DATABASE MANAGER 3062.261 1664 ERROR IN DATABASE SYSTEM 3072.262 1667 UNHANDLED MESSAGES OVERFLOW 3082.263 1682 SCDFLE UPDATE FAILURE 3082.264 1683 FAULTY UNIT SP-EX 3092.265 1684 SPARE UNIT WARMUP FAILURE 3102.266 1685 UNIT RESTART FAILURE 3112.267 1687 RECOVERY ACTION FAILURE 312



2.268 1688 FAILURE IN CALL CLEARING 3132.269 1800 SCSI ADDRESS ILLEGAL 3132.270 1801 MASS MEMORY FILE BACKUP FAILURE 3142.271 1802 BACKUP COPY LOG FAILURE 3152.272 1804 IP ROUTING RESOURCE SHORTAGE 3162.273 1806 PRINTER SPOOLER DISABLED 3172.274 1809 IP CONFIGURATION INQUIRY SERVICE FAILED 3182.275 1810 NEMU TRIGGERED PROCESS SANITY CHECK FAILED 3192.276 1811 NEMU MANAGEMENT SERVICE START FAILURE 3202.277 1812 NEMU EMT CONNECTION COULD NOT BE OPENED 3212.278 1813 NEMU SESSION START FAILURE 3212.279 1814 NEMU FTP CONNECTION COULD NOT BE OPENED 3222.280 1815 NEMU TELNET CONNECTION COULD NOT BE OPENED 3232.281 1860 DISK DISTURBANCE 3242.282 1881 TAPI FAILURE 3242.283 1882 DMADI FAILURE 3252.284 1884 LABEL PARAMETER FAILURE 3262.285 1885 ERROR IN WRITING DATA TO MAGNETIC TAPE 3262.286 1886 ERROR IN TAPE OPERATION 3272.287 1887 BLOCK COUNTER FAILURE 3282.288 1891 AS7 RESTARTED 3292.289 1893 O&M CHANNEL SEND OVERLOAD 3292.290 1894 NO RESPONSE TO AS7 SUPERVISION MESSAGE 3302.291 1895 DISTURBANCE IN O&M CHANNEL 3312.292 1900 DEGRADED SLIP FREQUENCY 3312.293 1902 DEGRADED SLIP FREQUENCY IN 2M CONNECTION 332

DN70600744Issue 16-0 en


Contents

List of figures



1 Summary of changes

1.1 Changes made between issues 16-0 and 15-0

New alarms

1343


Modified alarms

1024 1337 1576


New alarms

1192 1244 1300 1809

1294 1303

1295 1308

1320

1328

1333

1340

DN70600744Issue 16-0 en


Summary of changes

Modified alarms

1066 1267 1571 1804

1093 1282

1095


New alarms

1166 1273 1810

1273 1276 1811

1276 1282 1812

1288 1813

1293 1814

1815

Modified alarms

1001 1194 1200 1547 1646

1005 1204 1559 1660

1016 1210 1598

1037 1220 1532

1040 1221 1547

1065 1222

1097 1228

1233

1235

1236

1252

1257




New alarms

1220 1806

1221

1222

1249

1257

1259

1266

1267

1268

1271

1274

Modified alarms

1532 1642

1551 1643

1564

1573

DN70600744Issue 16-0 en


Summary of changes

2 List of alarms

1000 SPEECH SAMPLE FILE LOADING FAILED

1001 UNIT RESTARTED

1002 RAM FAILURE

1003 PARITY ERROR IN RAM

1004 COMMUNICATION ERROR BETWEEN PROGRAMBLOCKS

1005 PLUG-IN UNIT RESTARTED

1007 RESTARTED PROGRAM BLOCK

1008 MML PROGRAM RESTARTED

1010 NO RESPONSE TO UNIT SUPERVISIONMESSAGE

1012 EXCESSIVE RESTARTS OF UNIT

1014 PROCESSOR LOAD RATE ALARM LIMITEXCEEDED

1015 OPERATING SYSTEM ERROR COUNTERINCREASED

1016 MB INTERFACE FAILURE

1018 PROGRAM BLOCK COMMUNICATION ERROR

1019 PROGRAM BLOCK ACTION FAILURE

1020 PROGRAM BLOCK START UP FAILURE

1021 PROGRAM BLOCK REWARMING STARTED

1022 PROGRAM BLOCK WARMUP FAILURE

1023 EXCESSIVE DISTURBANCES IN SUPERVISION

1024 HAND PROCESS ERROR IN PROGRAM BLOCK

1025 REPORT LOST IN REPORTING

1026 ASM OVERLOAD

1028 RESTARTED PROGRAM BLOCK INPREPROCESSOR UNIT

1029 SCCP STP MESSAGE PREVENTION

1032 DPNSS CIRCUIT OUT OF USE

DN70600744Issue 16-0 en


List of alarms

1033 OSI CLNS CONFIGURATION FAILED

1034 MAXIMUM SEQUENCE NUMBER OF OSI CLNSEXCEEDED

1035 UPU MESSAGE RECEIVED

1036 EXCESSIVE RESTARTS OF PLUG-IN UNIT

1037 ECHO CANCELLER DAUGHTERBOARDLOADING FAILURE

1040 EVENT LOG OVERLOAD

1044 ERROR IN SWITCH COMPARE TEST

1045 ERROR BETWEEN MARKER TABLES ANDSWITCH CONTROL MEMORY

1047 NO RESPONSE FROM CONTROLLER OFSWITCHING NETWORK

1048 CONTROLLER OF SWITCHING NETWORKRESTARTED

1049 SEMIPERMANENT MULTICHANNELCONNECTION MISSING

1052 REQUESTED SERVICE NOT FOUND FROMNAMETABLE

1053 OVERFLOW IN GAP TABLE

1054 INCORRECT CHARGE RATE

1055 TCAP TRANSACTION FAILURE

1056 MESSAGE FROM NETWORK TO UNKNOWNSUBSYSTEM

1058 ERROR IN SMUX PLUG-IN UNIT

1059 ERROR BETWEEN MARKER TABLES AND LSWCONTROL MEMORY

1061 ERROR IN SWITCH COMPARE TEST

1062 ERROR BETWEEN MARKER TABLES ANDSWITCH CONTROL MEMORY

1064 UNIT UPDATE FAILURE

1065 DISK UPDATE FAILURE

1066 LOAD OBSERVATION REPORT OUTPUT FAILURE

1070 CCS7 PROGRAM BLOCK DATA ERROR

1071 PROCESSOR TIME SHORTAGE

1072 SIGNALLING LINK OUT OF SERVICE

1073 V5 DATA LINK LAYER PROTOCOL MISMATCH

1074 EXCESSIVE ERROR RATE ON V5 C-CHANNEL

1075 EXCESSIVE RETRANSMISSIONS ON V5 C-CHANNEL

1076 FORCED LIGHTWEIGHT SCHEDULING



1077 FREE STACK SIZE BELOW LIMIT

1078 PROCESS EXCEPTION

1079 UNSOLICITED V5 DATA LINK RE-ESTABLISHMENT

1080 PROCESS STOPPED

1082 HAND USAGE LIMIT EXCEEDED

1083 SEMAPHORE USE ERROR

1084 V5 ISDN USER PORT FAILURE

1085 V5 ISDN USER ACCESS OVERLOAD

1088 CONNECTION ERROR BETWEEN MSC ANDSMSC

1089 DYNAMIC LDT SLOTS EXHAUSTED

1090 BUFFER HANDLE ERROR

1091 TOO MANY EXECUTED SUBANALYSES INEXTENDED PREANALYSIS

1092 COMMUNICATION FAILURE IN FIELDREPORTING

1093 OUTPUT FAILURE IN FIELD REPORTING

1095 TRAFFIC MEASUREMENT OUTPUT FAILURE

1096 TRAFFIC ANALYSIS COMMUNICATION FAILURE

1097 TRAFFIC ANALYSIS OUTPUT FAILURE

1098 TOO LONG MESSAGE

1099 FAILURE IN TRAFFIC SAMPLING

1101 LSP RESTARTED

1102 LSP RAM FAILURE

1103 SIGNALLING MEASUREMENT REPORT LOST

1104 NO RESPONSE TO LSP SUPERVISIONMESSAGE

1105 LINE SIGNALLING RECEIVE OVERLOAD

1107 LINE SIGNALLING SEND OVERLOAD

1108 LINE SIGNALLING SEND OVERLOAD

1111 RESTART DUE TO TIME OUT REQUESTED

1113 STATISTICS MEASUREMENT OUTPUT FAILURE

1116 ERROR IN CHARGING

1117 ERROR IN LINE SIGNALLING

1118 UNKNOWN LINE SIGNAL

1119 ERROR IN LINE SIGNALLING INCOMINGMESSAGE

1120 ERROR IN LINE SIGNALLING PARTNERPROGRAM BLOCK

DN70600744Issue 16-0 en


List of alarms

1121 CIRCUIT CLEAR MISSING

1122 IMPULSE NOT IN TOLERANCES

1123 NUMBER NOT IN TOLERANCES

1125 TRIAL CONFIGURATION DELETED

1127 VANG POWER SUPPLY FAILURE

1128 EXCESSIVE DISTURBANCES IN FILE LOADING

1130 EXTERNAL CALL CLEARING

1136 SIGNALLING MESSAGE DISTRIBUTION ERROR

1137 INCORRECT SIGNALLING MESSAGE FROMSIGNALLING TERMINAL

1139 FIELD REPORT OF ROUTING COMPONENTSFAILED

1140 FREE LDT SLOT COUNT BELOW LIMIT

1141 DELAY BUFFER OVERFLOW IN SIGNALLINGTERMINAL

1142 FAMILY MEMORY USAGE SUPERVISION LIMITEXCEEDED

1143 AMOUNT OF FREE MEMORY REDUCED

1144 FREE BUFFER HEADERS EXHAUSTING

1145 FAILURE IN CALCULATING ACC CONGESTIONLEVEL

1147 MESSAGE QUEUE OVERFLOW

1148 EXCESSIVE TRAPS

1153 ERROR IN DIAL ANALYSIS DATA

1155 CONNECTION FAILED IN GSW/SWI

1162 FILE SYSTEM COMMUNICATION ERROR

1164 TIME NOT RECEIVED FROM SATELLITE

1165 BUFFER ALLOCATION FAILED

1166 FAILURE IN ACCESSING NPDB

1167 ERROR IN CAS REGISTER SIGNALLING

1168 DEFAULT ROUTING CALL

1169 FREEZING PERIOD OF SS7 REPORTING LOST

1170 NOT ENOUGH DIGITS IN CALLED NUMBER FOREXTENDED PREANALYSIS

1172 ASS PLUG-IN UNIT RAM FAILURE

1173 SYNCHRONIZATION OF PROCESSESRESTARTED IN COMMUNICATION LINK

1174 NO RESPONSE TO ASS SUPERVISIONMESSAGE

1175 INTERNAL SIGNALLING SEND OVERLOAD



1176 INTERNAL SIGNALLING RECEIVE OVERLOAD

1177 T1 PCM REMOTE END FRAME LOST

1178 PREPROCESSOR UNIT DISTURBANCE

1182 PREPROCESSOR UNIT RESTARTED

1190 EXCESSIVE ERRORS IN SCP

1191 POSITION ESTIMATE NOT AVAILABLE FOREMERGENCY CALL

1192 SSCOP TRANSMIT BUFFER OVERFLOW

1194 DYNAMIC ROUTING SEARCH ERROR

1195 USSD SERVICE INFORMATION NOT FOUND

1197 INCONSISTENCY IN THE SYNCHRONIZATION OFTHE NPDB DATABASES

1200 ACTOR HAS FAILED TO REGISTER TO THESUPERVISION

1204 WATCHDOG CAUSES UNIT RESTART

1207 UNITS WORKING STATE DATA CORRUPTED INTHE SYSTEM

1209 ECHO CANCELLER SPARE CHIP FAILURE

1210 PHASE ADVANCE OF TIMING SIGNAL CHANGED

1220 HANDLING OF MEASUREMENT DEFINITION FILEFAILED

1221 STATISTICAL MEASUREMENT REPORT OUTPUTFAILED

1222 DATA WRITING VIA VDS DEVICE FAILED

1224 MISSING MOLIMITER FOR SMSC LINK

1228 UNIT SUPERVISION NOT FUNCTIONING

1233 IP ENTITY IS NOT REACHABLE

1234 UPDATE OF PASSWORD VALIDITY TIME FAILED

1235 FQDN NOT PRESENT IN IEIFIL

1236 AN SI7 FAILURE OCCURED

1239 DSP SUPERVISION FAILURE

1240 SCCP DISTURBANCE

1241 SCCP GLOBAL TITLE TRANSLATION ANALYSISFILE ERROR

1242 SCCP GLOBAL TITLE TRANSLATION RESULTFILE ERROR

1243 DECODING ERROR OF THE RANAP-MESSAGE

1244 RUNNING OUT OF MESSAGE BUFFERS

1245 RANAP ERROR INDICATION MESSAGERECEIVED FROM PARTNER MSC

DN70600744Issue 16-0 en


List of alarms

1249 DATABASE DISK COPY HAS EXCEEDEDMAXIMUM ALLOWED AGE

1250 DATA LINK LAYER PROTOCOL MISMATCH

1251 EXCESSIVE RETRANSMISSIONS ON DATA LINKCONNECTION

1252 EXCESSIVE ERROR RATE ON DATA LINKCONNECTION

1253 NO RESPONSE FROM PRIMARY RATE ACCESSTERMINAL

1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT

1255 PRIMARY RATE ACCESS MESSAGEDISTRIBUTION ERROR

1256 INCORRECT PRD MESSAGE FROM PRIMARYRATE ACCESS TERMINAL

1257 FAULTY APM INFORMATION

1259 TOO MANY SUBANALYSES IN USER PLANEANALYSIS

1260 X.25/ETHERNET DATA TERMINALSPONTANEOUS RESTART

1261 OSI CHANNEL GROUP UNREACHABLE

1262 OSI SERVICE PROVIDER RESET

1263 OSI SERVICE PROVIDER INTERFACE ERROR

1264 OSI INCOMING CALL DENIED

1266 NO ACKNOWLEDGEMENT TO RESETRESOURCE

1267 RNC OUT OF SERVICE IN MSC

1268 RANAP ERROR INDICATION MESSAGERECEIVED FROM RNC

1271 THE IU-INTERFACE RANAP-LEVEL TIMEREXPIRY

1273 ASP ACTIVATION FAILED

1274 IU-INTERFACE RESOURCE ALLOCATIONFAILURE

1276 INCONSISTENCY OF THE NPDB DATABASES INTHE SRRI

1280 INTERNAL COMMUNICATION CHANNEL FAILURE

1282 ASSOCIATION PARAMETER FAILURE

1288 DATABASE REPLICA STATE CONFLICT

1293 SCCP GT SCREENING APPLIED

1294 INFINITE LOOP IN HLR GENERAL ANALYSIS



1295 TOO MANY SUBANALYSES IN HLR GENERALANALYSIS

1300 SUPERVISION CONNECTION TO UNIT LOST

1303 DB QUERY WARNING LIMIT EXCEEDED IN SRRU

1305 ERROR IN SUBSCRIBER SIGNALLING INCOMINGMESSAGE

1308 PRIMARY LDAP DIRECTORY SERVER ACCESSFAILED

1312 RAM FAILURE IN PREPROCESSOR UNIT

1313 FAILURE IN LI2M COMMUNICATION

1314 LI2M RESTARTED

1320 UMA RESOURCE ALLOCATION FAILURE

1322 NO RESPONSE TO SUB SUPERVISIONMESSAGE

1328 VLR LOAD CONTROL UPPER LIMIT REACHED

1333 ISUP SCREENING FILE OPENING ERROR

1337 INTERCEPTION DISTURBANCE

1340 HOTLINK FAILURE

1343 AOIP RESOURCE ALLOCATION FAILURE

1400 AFS RESTARTED

1423 NO RESPONSE FROM MAIN CLOCK

1425 OVERFLOW IN ALARM BUFFERING

1431 MMI SYSTEM OVERLOAD

1432 DISTURBANCE IN COMMAND CALENDAR

1450 NO RESPONSE TO SYSTEM SUPERVISIONMESSAGE

1453 NO RESPONSE TO TIME INQUIRY

1455 NO RESPONSE TO TIME ADJUST MESSAGE

1532 FAULTY COMMON CHANNEL SIGNALLINGMESSAGE

1541 PROGRAM BLOCK RESTARTED IN COCA/EC1P

1542 DSP RESTARTED

1543 COCA/EC1P RAM FAILURE

1544 DM2 FAILURE

1545 DM2 ET ALARM

1546 ERROR IN MEMORY HANDLING OF PROGRAMBLOCK

1547 ERROR IN COMPONENT HANDLING

1548 MTP CONFUSION MESSAGE RECEIVED

1549 TSLS UNTESTED IN ROUTINE TEST

DN70600744Issue 16-0 en


List of alarms

1550 FAULTY NATIONAL USER PART MESSAGE

1551 CCS USER PART ACKNOWLEDGEMENTMESSAGE MISSING

1552 FAULTY ISDN USER PART MESSAGE

1556 HLR SPECIAL ROUTING INFORMATION

1557 EVENT HANDLER CANNOT WORK PROPERLYDUE TO FILE SERVICE FAILURE

1558 RADIO NETWORK CONFLICT

1559 A-INTERFACE CIRCUIT ALLOCATION FAILURE

1560 BSC OR BTS OUT OF SERVICE IN MSC

1561 DPNSS ACKNOWLEDGEMENT MESSAGEMISSING

1562 ROUTINE TEST REPORTING FAILED

1564 UNEQUIPPED CIC

1569 CRITICAL LIMIT IN SECURITY REPORTINGREACHED

1570 SECURITY LOG ALARM LIMIT REACHED

1571 CALL INDEX RESERVATION FAILED

1572 SMS SUBMIT PRIMITIVE ENCODING FAILURE

1573 CONFLICT WITH DEFINED DIRECTION OFCIRCUIT/CIC

1574 DATA ERROR FOUND BY PROTOCOL

1575 COMPONENT NOT ACCEPTED BY REMOTE END

1576 ERROR IN TIME CHARGING INTERFACE

1577 SMS: NO RESPONSE FROM CO PROCESS

1579 UNRELEASED CALL BECAUSE OF DELAYEDRELEASE (DRS)

1581 NO CIC RECEIVED FROM BSC

1583 LAPD MSG DISTRIBUTION PROBLEM

1584 SCCP MESSAGE ROUTING ERROR

1586 BTA TUP RELEASE ACKNOWLEDGEMENTMISSING

1590 ALARM SYSTEM MESSAGE SENDING BUFFERFULL

1595 NEMU ALARM BUFFER OVERFLOW OCCURRED

1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM

1598 UNIT FOUND FAULTY BY ALARM SYSTEM

1621 ERROR IN FILE ACCESS

1623 ERROR DURING SUPERVISION

1630 RAM FAILURE IN SYNCHRONIZATION UNIT



1642 CIRCUIT/CIC BARRED OVER 5 MIN

1643 CIRCUIT/CIC BLOCKED OVER 5 MIN

1644 PROTOCOL MEASUREMENT REPORTTRANSFER UNSUCCESFUL

1645 PROTOCOL MESSAGE QUEUE FULL

1646 PROTOCOL INTERNAL ERROR

1647 OPERATION TIMER EXPIRY

1648 CONFLICT IN MESSAGE PROTOCOL

1651 DECODING ERROR OF THE A-INTERFACEBSSMAP-MESSAGE

1652 DECODING ERROR OF THE MESSAGERECEIVED FROM THE MS

1653 THE A-INTERFACE BSSMAP-LEVEL TIMEREXPIRY

1654 BSSMAP MESSAGE CONFUSION RECEIVEDFROM BSC

1657 TOO MANY EXECUTED SUBANALYSES INATTRIBUTE ANALYSIS

1658 NOT ENOUGH DIGITS IN CALLED NUMBER FORATTRIBUTE ANALYSIS

1660 UPDATE NUMBER MISMATCH

1661 DATABASE MANAGER IN FATAL ERROR STATE

1662 DATABASE LOADING ERROR

1663 HAND RESERVATION ERROR IN DATABASEMANAGER

1664 ERROR IN DATABASE SYSTEM

1667 UNHANDLED MESSAGES OVERFLOW

1682 SCDFLE UPDATE FAILURE

1683 FAULTY UNIT SP-EX

1684 SPARE UNIT WARMUP FAILURE

1685 UNIT RESTART FAILURE

1687 RECOVERY ACTION FAILURE

1688 FAILURE IN CALL CLEARING

1800 SCSI ADDRESS ILLEGAL

1801 MASS MEMORY FILE BACKUP FAILURE

1802 BACKUP COPY LOG FAILURE

1804 IP ROUTING RESOURCE SHORTAGE

1806 PRINTER SPOOLER DISABLED

1809 IP CONFIGURATION INQUIRY SERVICE FAILED

DN70600744Issue 16-0 en


List of alarms

1810 NEMU TRIGGERED PROCESS SANITY CHECKFAILED

1811 NEMU MANAGEMENT SERVICE START FAILURE

1812 NEMU EMT CONNECTION COULD NOT BEOPENED

1813 NEMU SESSION START FAILURE

1814 NEMU FTP CONNECTION COULD NOT BEOPENED

1815 NEMU TELNET CONNECTION COULD NOT BEOPENED

1860 DISK DISTURBANCE

1881 TAPI FAILURE

1882 DMADI FAILURE

1884 LABEL PARAMETER FAILURE

1885 ERROR IN WRITING DATA TO MAGNETIC TAPE

1886 ERROR IN TAPE OPERATION

1887 BLOCK COUNTER FAILURE

1891 AS7 RESTARTED

1893 O&M CHANNEL SEND OVERLOAD

1894 NO RESPONSE TO AS7 SUPERVISIONMESSAGE

1895 DISTURBANCE IN O&M CHANNEL

1900 DEGRADED SLIP FREQUENCY

1902 DEGRADED SLIP FREQUENCY IN 2MCONNECTION

2.1 1000 SPEECH SAMPLE FILE LOADING FAILED

Meaning

When the Marker (M) is restarted, the VANSER program block loads the

necessary speech sample files into the memory of the VANG plug-in unit

if they are not there already. If the loading of one sample file fails,

the system issues the alarm. You will find information on the files

whose loading was unsuccessful in the Marker's log file. Announcements

containing such speech sample files cannot be used before the files are

properly loaded into the VANG memory.



Supplementary information fields

Instructions

If all announcements are to be used, load the files that caused

problems by using the MML command RAY.

Cancelling

No cancelling.

2.2 1001 UNIT RESTARTED

Meaning

The unit has restarted.


1 working state of the unit

2 type of unit restart indicated by the initial loading program

block (e.g. BOLERO):

FF cold restart

00 warm restart

01 hot restart

02 diagnostic restart

type of unit restart indicated by the state administration:

AA not defined

3 information on the unit restart:

00 spontaneous

01 executed by the user

02 executed by the recovery program block

03 executed by the recovery program block, the package

identifier of the unit differs from that in the

active maintenance computer

DN70600744Issue 16-0 en


List of alarms

04 spontaneous repeated

05 executed with the service terminal command ZAU

06 the recovery program block has restarted the unit

as a result of the alarm 1023

07 IWMANA has restarted the unit at the request of

routine testing


as a result of the alarm 1128


in connection with a state change, because virtual

loading was still in process in the unit

4 type of restart in the Working State and

Configuration File (SCDFLE) when the unit is

restarting:

00 warm restart

01 hot restart

55 mini restart

If the active maintenance computer (normally the OMU)

was restarted with the MML command USU and R=HOT was

given as the restart type, the value of the field

is 00. The type of restart was, however, a hot

restart, if the value of supplementary information

field 2 is 01 hot restart.

5 code loading type when the unit is restarting:

00 optimal loading

01 total loading

02 total loading from disk

If the active maintenance computer (normally the OMU)

was restarted with the MML command USU and C=TOT or

C=DISK was given as the code loading type, the value

of the field is 01. Nevertheless, the loading was

performed from disk.

6 file loading type when the unit is restarting:

00 unknown/not defined

01 virtual loading

02 immediate loading

Instructions

The alarm requires no actions.



Cancelling

No cancelling.

2.3 1002 RAM FAILURE

Meaning

The RAM test program of the computer has observed a malfunction

in the RAM memory.


1 address of the faulty memory location

0...FFFFFFFF

Instructions

If the alarm recurs, the CPU is probably faulty and needs to be replaced.

The alarm supports the activation of the automatic recovery for

the object unit. You can check the supporting amount of the alarm

with the MML command ARO.

Cancelling

No cancelling.

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

DN70600744Issue 16-0 en


List of alarms


1 address of location where the RAM test was being carried

out when the error was detected

Instructions

If the alarm recurs, the CPU is probably faulty and needs to be replaced.




Cancelling

No cancelling.

2.5 1004 COMMUNICATION ERROR BETWEENPROGRAM BLOCKS

Meaning

The partner program block does not reply to the message sent to it

within the specified time limit, or the received reply is erroneous.


1 error code

01 no reply

02 identification of reply is erroneous

03 status of reply is erroneous

04 sequence number of reply is erroneous

2 family identifier of program block setting the alarm

3 unit message bus address of the partner program block

4 family identifier of the partner program block

5 identifier of the message sent to the partner program block

6 subidentifier of the message sent to the partner program block



7 case-specific additional information

8 case-specific additional information

Instructions


Cancelling

No cancelling.

2.6 1005 PLUG-IN UNIT RESTARTED

Meaning

A plug-in unit has restarted.


1 type of plug-in unit

See Diagnostics and Testing, Appendices, Maintenance Manual

2 index of plug-in unit

Instructions





Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.7 1007 RESTARTED PROGRAM BLOCK

Meaning

The program block has been restarted.


1 family identifier of the program block

2 error code

131d: program block was not found

132d: another program block of the same kind already exists

133d: program block deletion error

287d: program block has been deleted, or its creation failed

302d: program block has made a memory protection error

770d: program block did not answer the supervision message

771d: program block has acknowledged the supervision message

with a wrong state, i.e the program block is in wrong state

in relation to the working state of the unit

781d: state transition of the program block did not succeed

You can check its meaning in General Error Messages of System.

Instructions


Cancelling

No cancelling.

2.8 1008 MML PROGRAM RESTARTED

Meaning

The MMI Manager (MMIMAN) has restarted an MML program.




1 family identifier of the restarted MML program

Instructions


The alarm supports the activation of the automatic recovery

for the object unit. You can check the supporting amount of the alarm


Cancelling

No cancelling.

2.9 1010 NO RESPONSE TO UNIT SUPERVISIONMESSAGE

Meaning

The unit has not responded in the allotted time to a supervision

message sent by the supervisory unit.


Instructions





DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.10 1012 EXCESSIVE RESTARTS OF UNIT

Meaning

The maximum number of restarts set for a unit has been exceeded.


Instructions





Cancelling

No cancelling.

2.11 1014 PROCESSOR LOAD RATE ALARM LIMITEXCEEDED

Meaning

The processor load rate exceeds the alarm limit defined for the unit at

intervals of time defined for the unit. The alarm limit and the interval

are defined in BSPARA file.




1 processor load rate percentage

2 interval in hundredths of a second

Instructions

Check the validity of the value set for the parameter

CPU LOAD SUPERVISION LIMIT of BSPARA with the MML command:

ZDOT:<unit type>;

or find out the possible cause of overload.

This alarm may be given during the system reset because reset causes

load. In those cases, no actions are required from the user.

To change processor load supervision limit, give the MML command:

ZDOM:<unit type>:PROLL=<new supervision limit>;

Cancelling

No cancelling.

2.12 1015 OPERATING SYSTEM ERROR COUNTERINCREASED

Meaning

The alarm informs that the value of the error counter maintained by the

operating system has increased.


1 error code: identifies the fault that increased the counter thus

causing the alarm. You can check its meaning in General Error

Messages of System.

2 program block that increased the counter

3 value of the counter, i.e. amount of errors

DN70600744Issue 16-0 en


List of alarms

Instructions

Ascertain the reason for counter incrementation.

Cancelling

No cancelling.

2.13 1016 MB INTERFACE FAILURE

Meaning

In the test, the message bus interface (MBIF) has been detected

faulty. In the test, the unit sends a message to itself both on the

active and passive bus. It also checks the error counters of the

message buses, maintained by the operating system.


1 message bus test identifier:

1 message sending does not succeed despite several attempts

2 time supervision of message receiving has expired

3 received test message differs from the one sent

4 the transmission error counter of the MB has been incremented

5 the reception error counter of the MB has been incremented

6 time supervision of message sent with a group address has

expired

7 time supervision of message sent with a pair address has

expired

8 the supervision error counter of the MB has been incremented

2 message bus index

Instructions







Cancelling

No cancelling.

2.14 1018 PROGRAM BLOCK COMMUNICATION ERROR

Meaning

The partner program block does not respond within the

specified time to the message sent to it, or the reply

is faulty.


1 family identifier of program block giving the alarm

2 number of the message sent to the partner program

block or number of the received message

3 error code

01 no reply

02 identification of reply is faulty

03 status of reply is faulty

04 sequence number of reply is faulty

4 number of missing reply messages

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.15 1019 PROGRAM BLOCK ACTION FAILURE

Meaning

Errors detected in the state administration procedures of a

program block.


1 family identifier of program block

2 program block type in the family table of DXPARA

0 : normal program block

<> 0 : program block is essential for unit

functioning

3 error code of the recovery block

770d: program block did not answer the supervision

message

771d: program block has acknowledged the supervision

message with a wrong state. The program block

is in wrong state in relation to the working state

of the unit

You can check the meaning of other error codes in General

Error Messages of System.

Instructions



for the object unit. You can check the supporting

amount of the alarm with the MML command ARO.

Cancelling

No cancelling.



2.16 1020 PROGRAM BLOCK START UP FAILURE

Meaning

When activating a program block an error has been detected which

occurred either when creating or activating the program block.

The fault may cause disturbances in the system, particularly if a

program block creation error is in question.


1 family identifier of the detector of the error

2 the error code returned by the detector of the error,

presented according to the general error code. You can check

its meaning with a command of the service terminal extension

MRS or in General Error Messages of System

3 the message bus address of the unit where the error occurred

4 the family identification of the error-committing program block

Instructions

Additional information: Printouts of Starting Phases.

Check the meaning of the DX error code.

If the error code is:

770d: The program block has failed to respond within the

time limit to the activation message sent by the unit

state administration program block (USAPRO).

Possible causes are:

- The program block has made a memory protection error.

Check the log with the service terminal command ZSL.

Check the program block's check sum, service terminal

command ZSS.

Check the program block's version, service terminal

command ZSXP.

- The initialisation time allotted to the program block

is too short. Check whether the program block acknowledges

USAPRO at all.

Service terminal command ZOQ.

- The program block has detected an error in its

initialisation.

Check the error log with the service terminal command ZGD.

771d: The program block has acknowledged negatively the activation

message sent by USAPRO.

DN70600744Issue 16-0 en


List of alarms


- The program block has detected an error in its

initialisation.

Check the version of the program block.


- The program block has been activated into a wrong state

with regard to the unit's operating state. Check the

supervision messages between the program block and

USAPRO (message numbers 0001 and 0002). If the program

block is constantly in a wrong state, USAPRO restarts

the program block.

See the RESTARTED PROGRAM BLOCK alarms, if any

(alarm number 1007).

819d: The starting up of a library manager has failed.


- A fault in the initialisation of one of the libraries

that the manager is responsible for. Check the versions

of the manager and the library, service terminal commands

ZSXP and ZSK.


- In the starting up of the library manager itself.

Check the previous sections (770d, 771d).

All other error codes indicate a program block creation error.

Probable causes are: a fault in the DXPARA family table, a faulty

loading module, a discrepancy between the parameters of the family

table and the loading module, a storage area sufficiently large and

free cannot be found.

Cancelling

No cancelling.

2.17 1021 PROGRAM BLOCK REWARMING STARTED

Meaning

The warming of the program block has been restarted. The rewarming

may have been caused by one of the following: the thermometer (THERMO)

has detected synchronization errors in the program block, the program

block has been reactivated, or its warming failed on the previous

occasion.





USAPRO (A0): the detector of the error is the state

supervision

THERMO (16B): the detector of the error is the thermometer

If THERMO is the detector, a program block synchronization

error is in question.

2 identifier of the family to be warmed

Instructions


Cancelling

No cancelling.

2.18 1022 PROGRAM BLOCK WARMUP FAILURE

Meaning

The warming up of a program block has failed. The program block has

not acknowledged the warmup command sent by the unit state

administration program block (USAPRO), or has acknowledged it

negatively. The fault can lie in either the active or the spare unit.

The warming-up manager (WUPMAN) can also be the detector of the fault.



USAPRO (A0): the detector is the state administration

WUPMAN (108): the detector is the warming-up manager

2 error code returned by the detector of the error.

You can check its meaning with a command of the service

terminal extension MRS or in General Error Messages of

System, Supplementary References

DN70600744Issue 16-0 en


List of alarms

3 message bus address of the unit where the error occurred

4 family identifier of the program block that made the error

Instructions


Cancelling

No cancelling.

2.19 1023 EXCESSIVE DISTURBANCES INSUPERVISION

Meaning

The unit state administration program block (USAPRO) has detected a

serious error when supervising the functioning of the program blocks

of the unit. The alarm may have been caused by one of the following:

several program blocks have been restarted; or some critical program

block does not respond to the supervision, or refuses to respond to a

state transition command. In addition the alarm may be due to repeated

rewarmings of program blocksor to synchronisation errors. The situation

leads to a restart of the unit.


1 type of error

00: error in program block supervision

01: error in the warming-up or synchronisation

of program blocks


USAPRO (A0): detector is state administration

THERMO (16B): detector is the thermometer. If THERMO

is the detector, a synchronisation fault of a critical

program block is in question.

3 error code returned by the detector of the error, presented

according to the general error code

65535d: no significance

You can check the meaning of error codes with a command of



the service terminal extension MRS or in General Error

Messages of System, Supplementary References


FFFF: no significance


FFFF: no significance

Instructions


Cancelling

No cancelling.

2.20 1024 HAND PROCESS ERROR IN PROGRAMBLOCK

Meaning

The requested service could not be carried out due to the

failure of process family resource (hands) management.


1 ID of the system library service primitive that returned

the error code. The field may have the following values:

0: creation of hands

1: creation of additional hands

2: reservation of hand

3: renewal of hand reservation

4: expiry of hand reservation

5: restart of hand

6: deletion of hand group

2 error code returned by system library service primitive. You can check

its meaning with a command of the service terminal extension MRS or

in General Error Messages of System, Supplementary References

3 type of reserved hand/hand to be reserved. 0 if not known

DN70600744Issue 16-0 en


List of alarms

4 number of reserved hand/hand to be reserved

5 life focus of the hand

6 computer address of the customer

7 family ID of the customer

8 process ID of the customer

9 life focus of the customer

Instructions

Reservation of a hand fails typically in situation where all available

hands have already been reserved (e.g. overload situations). If the fault

situation (additional information field 1 value = 02) occurs only

occasionally, the disturbance requires no actions from the user.

In other cases, fill in a Failure Report and send it to your local Nokia

Siemens Networks Customer Service Center.

Enclose the printouts obtained with the service terminal commands

ZSCFE, ZGSC, ZSL, and with the F, D, H, and G-commands of the FAM

family extension.

Cancelling

No cancelling.

2.21 1025 REPORT LOST IN REPORTING

Meaning

The outputting of a report has failed.


1 error:

01 error in I/O system, see supplementary information field 2

02 the TEXTPR program block has failed to reply to a service request

03 internal report buffer of LIZPRB program block is overflowing

04 the process has too many unhandled messages in the message queue



2 error code returned by the I/O system:

0d reason of error unknown

You can check the meaning of other error codes in General Error

Messages of System

3 type of report:

01 immediate charging report

02 subscriber counter report

03 call logging record

4 name of logical file where to outputting was attempted

Instructions

If the value of the first supplementary information field is 01, check

that the output device that is connected to the logical file is

operational.

If the value of the first supplementary information field is 04 and

in the third supplementary information field is 03, the using of

reports buffering is recommended.

Cancelling

No cancelling.

2.22 1026 ASM OVERLOAD

Meaning

An increment has been detected in the rejected cell counter

of a switching network.


1 index of the SWCOP plug-in unit that detected the fault

2 index of the ASWI plug-in unit whose counter was incremented

DN70600744Issue 16-0 en


List of alarms

3 number of higher priority level rejected cells

4 number of lower priority level rejected cells

Instructions


Cancelling

No cancelling.

2.23 1028 RESTARTED PROGRAM BLOCK INPREPROCESSOR UNIT

Meaning

A program block has been restarted.


1 plug-in unit index:

.. : control plug-in unit

other values: line terminal plug-in unit

2 program block ID

3 error code:

770d : program block has not responded to supervision message

771d : program block has acknowledged supervision message with

wrong state, i.e. the program block is in the wrong

state in relation to the unit's working state

781d : failure in changing state of program block

287d : program block has been deleted, or its creation has

failed

302d : memory protection error by program block

131d : program block not found

132d : an identical program block already exists

133d : error in deleting program block



Instructions


Cancelling

No cancelling.

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


1 type of access right violation of the STP function (cause code)

01 the source point in question should not send signalling

messages to the destination point (the message has been

transmitted)

02 the source point in question is not allowed to send

signalling messages to the destination point (the message

has been destroyed or sent back)

03 the incoming link set in question should not be used to

send signalling messages to the destination point

(the message has been transmitted)

04 the incoming link set in question is not to be used to send

signalling messages to the destination point (the message

has been destroyed or sent back)

05 the pointer of the global title in the calling party address

global title is not permitted (the message has been

destroyed or sent back)

06 no analysis can be found for the root of the calling party

address global title (the message has been destroyed or

sent back)

2 destination point signalling network, which can get the

DN70600744Issue 16-0 en


List of alarms

following values:

00 international network 0, IN0


08 national network 0, NA0

0C national network 1, NA1

3 destination point code value of the processed signalling message

4 originating point signalling network, which can get the

following values:





5 originating point code value of the processed signalling message

6-10 if Supplementary information field 1 has the value 01,

02, 03 or 04, the value (5 sequential bytes) indicates the

signalling point code of the signalling point and the

signalling network, from which the signalling message was

received. The field is coded so that the first byte

indicates the signalling network and the next four indicate

the signalling point code. E.g. the signalling point 260 of

the NA0 network would be coded as follows:

08 00 00 02 60

If Supplementary information field 1 has the value 05 or

06, the value indicates the root parameter values of the calling

party address global title in the following order:

- the standard of the global title

- global title indicator (GTI)

- translation type (TT)

- numbering plan + encoding type (NP+ENC)

- nature of address indicator (NAI)

If a field has the value FF, the root parameter in question is

not defined on the value of that global title indicator (GTI)

Instructions

Procedures on the basis of the value of Supplementary information

field 1 (cause code):

Cause codes 01 and 02:

SCCP screening information says that messages originating from the

signalling point mentioned in Supplementary information field 5

should not be transferred to the destination point. Check if this

restriction is justified and remove the blocking with the MML

command ODM if necessary. In other case the operator who owns the

signalling point mentioned in Supplementary information fields 4



and 5 should be notified about an access right violation.

Cause codes 03 and 04:

SCCP screening information says that messages originating from

the signalling network and the adjacent signalling point (channel

system) mentioned in Supplementary information field 6 should not

be transferred to the destination point. Check if this restriction

is justified and remove the blocking with the MML command ODM, if

necessary. In other case the operator who owns the adjacent

signalling point mentioned in Supplementary information field 6

should be notified about an access right violation.

Cause code 05:

The calling party address of the received SCCP STP message uses a

global title indicator value that is prohibited in the parameter

set of the destination point mentioned in Supplementary information

fields 2 and 3. Check if this restriction is justified and remove

the restriction with the MML command OCM, if necessary. In other

case the operator who owns the signalling point mentioned in

Supplementary information fields 4 and 5 should be notified about

an access right violation.

Cause code 06:

The calling party address of the received SCCP STP message uses

a global title with root parameters that do not have a matching

analysis in the SCCP analysis information. Check if the root

parameters need to be analysed and remove the analysis with the

MML command OCM, if necessary. If the root parameters need to be

analysed, check if there should exist an analysis for the global

title in question, and create it with the MML command NBC, if

necessary. In other case the operator who owns the signalling

point mentioned in Supplementary information fields 4 and 5 should

be notified about an access right violation.

Cancelling

No cancelling.

2.25 1032 DPNSS CIRCUIT OUT OF USE

Meaning

The state of one or several DLCs of the DPNSS link has changed

to 'out of service' due to a link failure. Because of this, the

speech time slots of the corresponding PCM are barred.

DN70600744Issue 16-0 en


List of alarms


1 number of the external PCM

2 number of the D-channel corresponding to the external PCM

3 the DLC or time slot in which the state transition has

taken place

Instructions

Check the condition of the D-channel. See if the failure is in the

remote end.

Cancelling

No cancelling.

2.26 1033 OSI CLNS CONFIGURATION FAILED

Meaning

The configuration of the connectionless OSI network service (CLNS)

has failed. This can be caused by either the time-out of the timer

that controls the approval of the configuration, or errors in the

configuration data. After a configuration failure, the system uses

the default value attributes for connectionless network services.


1 the name of the CLNS used in the configuration

2 the type of the disturbance observation

0 type data is not available

1 time-out of the timer

2 an error during the configuration phase

3 an error during the attribute setting phase

3 a general error code which tells why the configuration of the

CLNS of the OSI failed. You can check its meaning in General

Error Messages of System



Instructions


Cancelling

No cancelling.

2.27 1034 MAXIMUM SEQUENCE NUMBER OF OSICLNS EXCEEDED

Meaning

The number of a connectionless OSI network service (CLNS) has exceeded

the maximum value. This is probably due to a malfunction in the OSI

network IS routing equipment. Connectionless network service can not

be used for 20 minutes, during which time it is not possible to

transfer routing data or user data. This is to ensure that the

clearing of the number does not cause disturbances in other nodes,

but it is possible that there will be some interruptions in the OSI

services.


Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.28 1035 UPU MESSAGE RECEIVED

Meaning

The exchange has received a User Part Unavailable message (UPU).

This message informs the sending end of a signalling message that

the user part of the destination address is not available.

Depending on the unavailable user part (TUP and ISUP) the telephone

traffic and signalling traffic fail. In the case of SCCP, used

services fail.


1 network from which the UPU message came:

network code network

------------ ------

00 national network 0


08 international network 0

0C international network 1

2 header code of message

3 destination point code received in message, indicating

the destination point of the unavailable user part

4 user part identifier received in the user_part_info of

the message, indicating the unavailable user part in the

destination point (3rd supplementary information, DPC)

identifier user part

---------- ---------

00 spare

01 spare

02 spare

03 SCCP

04 TUP

05 ISUP

06 DUP

07 ) spare

... ) spare

0F MTP test user part

5 reason for the unavailability of the user part

(4th supplementary information), obtained from the

user_part_info of the message

code reason for unavailability



---- -------------------------

00 user part unknown in the DPC

01 user part has not been created, or

no service has been created for it

02 user part cannot be reached in the DPC

Instructions

If the message traffic of the user part concerned should be possible

to the destination point, check from the operator of the destination

point whether the user part has been created and whether it is

available.

Cancelling

No cancelling.

2.29 1036 EXCESSIVE RESTARTS OF PLUG-IN UNIT

Meaning

The number of times a subscriber interface plug-in unit has been

restarted has exceeded the preset limit.


1 type of the subscriber interface plug-in unit

2 index of the subscriber interface plug-in unit

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.30 1037 ECHO CANCELLER DAUGHTERBOARDLOADING FAILURE

Meaning

There is a disturbance in the loading of the echo cancelling software.


1 index of the echo canceller

2 reason for the loading failure

01 ECU is of the wrong type or is not equipped

02 ECU is in the wrong state

03 check sum error in a record of the file to be loaded

04 check sum error in the file to be loaded

05 equipment failure of the ECU

06 a load attempt to the unit that is loading

07 no free loading process

08 ECU does not reply

09 the version interrogation of the software failed

10 ECxN reset while loading

Instructions

Value of the supplementary information field 2:

01 : Check the type and index of the ECU, and whether it is

equipped.

02 : Set the ECU to SE-OU state before reloading.

03 : Try loading again. If the same failure is repeated, the

file to be loaded is either faulty or wrong. Contact the

supplier of the software build.

04 : Try loading again. If the same failure is repeated, the

file to be loaded is faulty. Contact the supplier of the

software build.

05 : Equipment failure in the ECU unit. Change the faulty

unit and try loading again.

06 : Wait until the previous loading is complete.

07 : Wait until the previous loading is complete.

08 : Check the D-channel connection to the ECU and the type of

the ECU.

09 : Try loading again.

10 : Try loading again.



Cancelling

No cancelling.

2.31 1040 EVENT LOG OVERLOAD

Meaning

The memory buffers of the event log or the disk file are becoming full.


1 computer unit type of event log queue

2 number of event log queue

3 object which is becoming full

01 memory buffers

02 disk file

4 filling rate in percetages

Instructions

If buffers are becoming full:

- add buffers to queue

- increase queue buffer sizes

- move applications which store data to this queue to

another queue

If disk file is becoming full:

- set queue storage to DAT

- allow overwrite

- move applications which store data to this queue to

another queue

- create a new queue with a larger file and move applications

to it

See Event Log hangling (DL), Command Reference Manual.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.32 1044 ERROR IN SWITCH COMPARE TEST

Meaning

The comparison test of the switching network has observed an error.

The comparison test compares the incoming bit patterns with

the outgoing bit patterns in the connections of the switching network.

The problem can be caused by

- defective cabling

- faulty power supply of the exchange

- faulty plug-in unit of the switching network (SWSPS, SWCSM)

- faulty control processor of switching network (SWCOP)


1 PCM line of the outgoing circuit

2 time slot of the outgoing circuit

3 PCM line of the incoming circuit

4 time slot of the incoming circuit

5 incoming bit pattern

6 outgoing bit pattern

Instructions


for the object unit. You can check the supporting amount of

the alarm with the MML command ARO.

To determine what has caused the alarm, proceed in

the following way:

1. Run the diagnosis for the unit that is the object unit of the alarm.

Bring the unit in the test state (TE) using the USC command and run

the diagnosis using the UDU command.

If the diagnosis cannot locate the fault, proceed to the next step.



2. Check the cabling. Check the physical connections of the SWCSM,

SWCOP, SWSPS plug-in units. Check that the cables are correctly in

place and that correct cable type has been used. If the problem

is not in the cabling, proceed to the next step.

3. Replace the SWSPS plug-in unit. See Instructions for Replacing

Plug-in Units.

If replacing the plug-in unit does not help, proceed to the next

step.

4. Replace the SWCOP plug-in unit. See Instructions for Replacing

Plug-in Units.


step.

5. The cause of the alarm can be external disturbances conducted

trough power supply. In this case the problem can be solved

only by removing the source of the disturbances.

Cancelling

No cancelling.

2.33 1045 ERROR BETWEEN MARKER TABLES ANDSWITCH CONTROL MEMORY

Meaning

This alarm indicates a temporary defect in the switch control

memory. There is a difference between the data of the switch

control memory and the data of the switching file.

The problem can be caused by

- defective cabling

- faulty power supply of the exchange

- faulty plug-in unit of the switching network (SWCSM)

- faulty control processor of switching network (SWCOP)


1 PCM line of the outgoing circuit

2 time slot of the outgoing circuit

3 PCM line of the incoming circuit in the control memory

DN70600744Issue 16-0 en


List of alarms

4 time slot of the incoming circuit in the control memory

5 PCM line of the incoming circuit in the reserve table

6 time slot of the incoming circuit in the reserve table

Instructions





To determine what has caused the alarm, proceed in

the following way:

1. Run the diagnosis for the unit that is the object unit of the alarm.

Bring the unit in the test state (TE) using the USC command and run

the diagnosis using the UDU command.

If the diagnosis cannot locate the fault, proceed to the next step.

2. Check the cabling. Check the physical connections of the SWCSM,

SWCOP plug-in units. Check that the cables are correctly in

place and that correct cable type has been used. If the problem

is not in the cabling, proceed to the next step.

3. Replace the SWCSM plug-in unit. See Instructions for Replacing

Plug-in Units.


step.

4. Replace the SWCOP plug-in unit. See Instructions for Replacing

Plug-in Units.


step.

5. The cause of the alarm can be external disturbances conducted

trough power supply. In this case the problem can be solved

only by removing the source of the disturbances.

Cancelling

No cancelling.



2.34 1047 NO RESPONSE FROM CONTROLLER OFSWITCHING NETWORK

Meaning

The switch control processor (SWPRO or SWCOP) has not acknowledged the

supervision message sent by the supervising unit within the specified

time limit.


1 type of the controller of GSW.

received.

2 index of the controller of GSW.

Instructions





Cancelling

No cancelling.

2.35 1048 CONTROLLER OF SWITCHING NETWORKRESTARTED

Meaning

The alarm informs of an erroneous switch control processor (SWCOP or

SWPRO) restart.

DN70600744Issue 16-0 en


List of alarms


1 type of the controller of GSW restarted

2 index of the controller of GSW

Instructions

The alarm requires no actions. The alarm supports the activation of

the automatic recovery for the object unit. You can check the supporting


Cancelling

No cancelling.

2.36 1049 SEMIPERMANENT MULTICHANNELCONNECTION MISSING

Meaning

The switching data of a semipermanent multichannel connection is

erroneous. The data in the files (SMWIBA/SMMUPO - HNCONN/LICONF) is

inconsistent.


1 type of connection

(point-to-point connection PTP/point-to-multipoint connection PTM)

00 multichannel connection between two external PCM circuits

01 multichannel multipoint connection between external PCM

circuits

2 the connection's incoming PCM circuit, from SMWIBA/SMMUPO

3 the connection's incoming time slot, from SMWIBA/SMMUPO

4 the incorrect information, in the HNCONN/LICONF files, of

the connection's incoming PCM circuit

5 the incorrect information, in the HNCONN/LICONF files, of



the connection's incoming time slot

6 the connection's outgoing PCM circuit

7 the connection's outgoing time slot

8 error code:

01 connection is missing from HNCONN

02 connection is missing from LICONF

Instructions


Cancelling

No cancelling.

2.37 1052 REQUESTED SERVICE NOT FOUND FROMNAMETABLE

Meaning

The service that was requested was not found from the

nametable.


1 the first 16 characters of the name of the requested

service. If the name does not contain 16 characters,

spaces are used to make up the difference

Instructions


DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.38 1053 OVERFLOW IN GAP TABLE

Meaning

SCP requests the creation of a new traffic gap gate, but the traffic gap

table is already full. A module is removed from the table and a new gate

is created in its place.


1 the number of records in the traffic gap table

2 identifier of the gapping criterion that was deleted because of

the new gate:

0 service key

1 B number

2 A number

3 service key and B number

4 service key and A number

3-16 more information on the deleted criterion

Instructions

Notify your software supplier and ask them to enlarge the gap table.

Cancelling

No cancelling.



2.39 1054 INCORRECT CHARGE RATE

Meaning

The charging zone has had incorrect charge rate. This can be a result

of a failed charge rate update during the previous change of the charge

rate, or the charge rate has been changed when the unit has just been

getting up, so that the old charge rate is left for the charging zone.

In this situation, the correct charge rate has been updated to the

charging zone.


1 the charging zone that has had a wrong charge rate

Instructions


Cancelling

No cancelling.

2.40 1055 TCAP TRANSACTION FAILURE

Meaning

The Transaction Capabilities Application Part (TCAP)

of the common channel signalling system has detected an error

in the management of a transaction. The transaction has been

interrupted due to this error.

The disturbance has no effect on other transactions.


1 type of the error. It can have the following values:

01 beginning the transaction has failed in the user's end,

TCAP has not located the SCCP computer unit

DN70600744Issue 16-0 en


List of alarms

02 beginning the transaction has failed in the network

because the TCAP user has not stated the version of

TCAP to be used

03 beginning of the transaction has failed in the network

for unknown reasons

04 transaction has ended abnormally with the hand's time-out

05 transaction has ended abnormally for unknown reasons

06 sending a message to the user has failed

07 sending a message to the SCCP has failed

08 operation automatons have been used up

2 computer address of the party that requested the service

3 family identifier of the party that requested the service

4 process identifier of the party that requested the service

5 life focus of the party that requested the service

6 reference number in the DX log. The log contains additional

information on the error. If the reference number is

not used in the log, the value of the field is zero

Instructions

If the error in the first supplementary information field

is a type 4 error, and the alarm is given occasionally,

the alarm requires no actions.

In other cases, fill in a Problem Report and send it to

your local Nokia Customer Service Center. Include the printouts

obtained during the error situation from the message monitoring

process family 114 (TCAP), and with the service terminal commands

ZSCFE, ZGSC and ZSL as well as the FAM family extension commands

F, D, H and G.

Cancelling

No cancelling.



2.41 1056 MESSAGE FROM NETWORK TO UNKNOWNSUBSYSTEM

Meaning

SCCP has received a message from the network. The message's

destination is an unknown subsystem.


1 type of the SCCP message that has an unknown subsystem as its

destination. It can have the following values:

01 CR Connection Request

02 CC Connection Confirm

03 CREF Connection Refused

04 RLSD Released

05 RLC Release Complete

06 DT1 Data Form 1

07 DT2 Data Form 2

08 AK Data Acknowledgement

09 UDT Unitdata

0A UDTS Unitdata Service

0B ED Expedited Data

0C EA Expedited Data Acknowledgement

0D RSR Reset Request

0E RSC Reset Confirm

0F ERR Protocol Data Unit Error

10 IT Inactivity Test

11 XUDT Extended Unitdata

12 XUDTS Extended Unitdata Service

13 LUDT Long Unitdata

14 LUDTS Long Unitdata Service

2 network indicator. It can have the following values:




0C national network 1

3 destination point code

4 number of the destination subsystem unknown to SCCP. If the

message that is to be routed does not contain a subsystem number,

the field's value is FF

5 originating point code

6 number of the originating subsystem. If the message that is

to be routed does not contain a subsystem number, the field's

DN70600744Issue 16-0 en


List of alarms

value is FF

7 reference number in the DX log. The log contains the incorrect

message. If the reference number is not used in the log, the

field's value is 0

Instructions

If the error occurs repeatedly, do the following:

If the value of Supplementary information field 4 is something other

than FF, check if the subsystem given in Supplementary information

field 4 has been created in the relevant signalling point of the

signalling network by using the signalling point's SCCP Data Handling

MML commands. The signalling point is given Supplementary information

field 3 and the signalling network in Supplementary information field

2.

If the subsystem has not been created, check if it should be created

in the system and, if necessary, create it with the MML commands of

the previously mentioned command group.

If the subsystem does not belong in the system, contact the network

operator of the signalling point mentioned in Supplementary information

field 5 to find out why they are trying to send messages to the

subsystem mentioned Supplementary information field 4.

If the value of Supplementary information field 4 is FF, the subsystem

number is missing from the destination data of the received message in

Supplementary information field 5 signalling point. The subsystem number

cannot be obtained through global title translation.

In other cases, fill in a Problem report and send it to your local Nokia

Customer Service Center. Include the printouts of service terminal

commands ZSCFE, ZGSC and ZSL in the report.

Cancelling

No cancelling.



2.42 1058 ERROR IN SMUX PLUG-IN UNIT

Meaning

The SMUX plug-in unit test has detected a fault in the plug-in

unit. The test is to check that the SMUX plug-in unit multiplexes

the 16 kbit/s channels correctly to the 64 kbit/s channel.

The test is carried out in the switching network by branching

time slots, coming to and leaving from the SMUX, to the SWCOP,

and by checking that the bit pattern contained in the time slots is

correct.


1 index of SMUX plug-in unit

2 PCM circuit coming to SMUX plug-in unit

3 incoming time slot

4 PCM circuit outgoing from SMUX plug-in unit

5 outgoing time slot

6-9 four consecutive samples of bit patterns coming to

SMUX plug-in unit.

10-13four consecutive samples of bit patterns departing from

SMUX plug-in unit.

Instructions





Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.43 1059 ERROR BETWEEN MARKER TABLES ANDLSW CONTROL MEMORY

Meaning

The connection data in the Line Signalling Switch (LSW) and the LICONF

file of the control memory are inconsistent.


1 the number of the external PCM corresponding to the LSW output

2 the number of the external PCM's time slot corresponding to

the LSW output

3 the index (0..2047) of the LSW input in the control memory

of LSCSM

4 the number of the external PCM corresponding to the LSW input,

defined on the basis of field 3

5 the number, in the LSCSM control memory, of the external PCM's

time slot corresponding to the LSW input

6 the mask bits of the standard signal to be sent and the bit

pattern of the standard signal in the control memory of LSCSM

7 index (0..2047) of the LSW input in the LSWCON table

8 the number of the external PCM corresponding to the LSW input,

defined on the basis of field 7

9 the number, in the LSWCON table, of the external PCM's

time slot corresponding to the LSW input

10 the mask bits of the standard signal to be sent and the bit

pattern of the standard signal in the LSWCON table

Instructions


The alarm support the activation of the automatic recovery





Cancelling

No cancelling.

2.44 1061 ERROR IN SWITCH COMPARE TEST

Meaning

The comparing test of the switching network (GSWB) has detected an

error. The comparing test compares the bit pattern created in the

switching network by the switchings in the network to the

bit pattern leaving the switching network.


1 outgoing PCM circuit (corresponds to a 4 Mbit/s circuit group)

2 outgoing PCM circuit's 8 kbit/s channel

3 incoming PCM circuit (corresponds to a 4 Mbit/s circuit group)

4 incoming PCM circuit's 8 kbit/s channel

5 incoming bit pattern

6 outgoing bit pattern

Instructions





Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.45 1062 ERROR BETWEEN MARKER TABLES ANDSWITCH CONTROL MEMORY

Meaning

The switching data of the switching network control memory and the

incoming connections file is different.


1 outgoing PCM circuit (corresponds to a 4 Mbit/s circuit group)

2 outgoing PCM circuit's 8 kbit/s channel

3 incoming PCM circuit in the control memory

4 incoming PCM circuit channel in the control memory

5 incoming PCM circuit in the incoming connections file

6 incoming PCM circuit channel in the incoming connections file

Instructions





Cancelling

No cancelling.



2.46 1064 UNIT UPDATE FAILURE

Meaning

Failure in the updating of the partner unit or another unit to be

updated (M, SSU). The file has not been updated in the unit which

received the updating input, either.


1 family identifier of the program block that detected

the failure

2 number of the message which caused the updating

3 unit to be updated

4 error code returned by the unit to be updated

16d REQMAN does not reply to the disk update

inquiry before time-out

106d file error

Instructions



for the object unit. You can check the supporting amount of the

alarm with the MML command ARO.

Cancelling

No cancelling.

2.47 1065 DISK UPDATE FAILURE

Meaning

A file modification made in the Central Memory has not been

updated onto disk. The data of the file on the disk does not

correspond to the data in the Central Memory.

DN70600744Issue 16-0 en


List of alarms


1 number of the message that caused the updating

2 error code returned by the file update (general error

message of the system). See General Error Messages of System for error

code explanations.

3 file number

4 offset from the beginning of the file

Instructions

1. Check the alarms set by the File Updating Request Manager

Program Block (REQMAN).

2. Move the file shown in the additional information field 3

from the Central Memory to disk with the MML command DFC.

If moving the file to the disk fails, it is possible that

the operation of the switch suffers disturbances after the

next disk loading in so far as the operation has to do with

the file in question.

Cancelling

No cancelling.

2.48 1066 LOAD OBSERVATION REPORT OUTPUTFAILURE

Meaning

The output of a load observation report to a specific I/O device has

failed. The failure can be caused by an overload in the I/O system or

in the statistical unit. It can also be caused by a situation, where

there are several items under observation, and it is not possible to

produce output of all items during the monitoring period.




1 load observation report type

CGR circuit group observation report

CNTL control unit observation report

COMP computer unit observation report

MBUS message bus observation report

REJ rejected calls report

DEST destination observation report

SUBD subdestination observation report

TOT total load observation report

2 reason for the failure in reporting:

00 an error in the output of a report, the reason for the error

is explained in the third supplementary information field

01 there is not enough time to produce output of all items

during the monitoring period, there are too many items for

a monitoring period or the units' load has caused delay in

the traffic data search

03 the program block forming the report does not respond to an

output request, the load of the I/O system

3 the reason for the failure of report output:

00 error with the making of the report, the reason for the error

is in the second supplementary information field

other values: an error code returned by the I/O system.

You can check its meaning in General Error Messages

of System

Instructions

If the value of the second supplementary information field is 01, use MML

command TLI to check the number of items and the length of the

observation period. If there are several items, extend the observation

period by stopping the observation with the MML command TLE and

restarting it in a new observation period with the MML command TLS.

Check that the operation and maintenance computer (OMU) is in state

WO-EX.

Check that the output device that is connected to the load observation

logical file is operational. The logical files for the ascii, binary

and xml reports of the load observation are as follows:

DN70600744Issue 16-0 en


List of alarms

Logical file Measurement type

=====================================================================

ascii bin xml

LOACGRA LOACGRB LOACGRX circuit group observation

LOACNTLA LOACNTLB LOACNTLX control unit observation

LOACOMPA LOACOMPB LOACOMPX computer unit observation

LOAMBUSA LOAMBUSB LOAMBUSX message bus observation

LOATOTA - - total load observation

LOADESTA LOADESTB - destination observation

LOASUBDA LOASUBDB - subdestination observation

LOAREJEA LOAREJEB LOAREJEX load Observation of rejected calls

Cancelling

No cancelling.

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


1 error code

01 value of data exceeds the accepted range

02 record data are in conflict

03 value of stored data is in conflict with new value received

for that data

2 file number

3 record number

4 subrecord number

Instructions

In N+1 protected units the warming up of the files may have

already corrected the error detected. If the fault situation

is over, futher actions are not needed.

Examine the other alarms given by the unit using the MML command AHO.



If necessary, examine also the alarm history of the unit using the

MML command AHP. If the alarm occurs repeatedly, the files of the

CCS7 level 3 are likely to contain an error.

If the alarm still continues to occur, save the defective file

on disk for later examination for errors and contact the customer

support service. Check also the log print-outs of the unit.




Cancelling

No cancelling.

2.50 1071 PROCESSOR TIME SHORTAGE

Meaning

There is not enough processor time for all processes fit for running.

The operating system kernel has temporarily set the priority high for

those processes that have not received running time for some time.

The processor has a 100 % utilization rate.

The situation results from a computer overload or a fault in some

processes.


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

2 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. Fields 2 and 3 contain

the identifier of the family in full

3 process identifier, see description in field 2

4 priority of the process identified in fields 2 and 3

5 identifier of a family that was fit for running during the whole

of the inspection period, although it received processor time

during the period. If the disturbance was generated because of

DN70600744Issue 16-0 en


List of alarms

a looped process, this process is the probable cause of the

disturbance.

Fields 5 and 6 contain the family identifier in full.

If there is no such process in the queue for processes fit

for running, the identifier is FFFF FFFF

6 process identifier, see description in field 5

7 priority of the process identified in fields 5 and 6. If there

is no such process, i.e. the process identifier is FFFF FFFF,

the value is 0

Instructions

The disturbance may result from a computer overload. Check if there

is an overload in the network element or a local overload in some

computer unit of the network element.

If the fault lies elsewhere, the maintenance of the exchange starts

actions to correct the fault situation. In these other fault

situations, it is also recommended to inform the supplier of

the software package on the fault to investigate the reason for

the fault.

Cancelling

No cancelling.

2.51 1072 SIGNALLING LINK OUT OF SERVICE

Meaning

A signalling link has failed and changed state from IN SERVICE to

OUT OF SERVICE, or its initial alignment attempt has failed. If this

signalling link is the only one in the signalling link set, the system

sets also alarm 2070, LINK SET UNAVAILABLE. If there is an alternative

signalling link available in the link set, the system performs a

changeover. In this case the signal transmission capacity is also

decreased.




1 signalling link number

2 signalling link error code

01 stop command received

02 erroneous BSN received repeatedly

03 erroneous FIB received repeatedly

04 error ratio too high

05 acknowledgement delay too long

06 initial alignment unsuccessful

07 congestion too long

08 SIO received when one is not expected

09 SIN received when one is not expected

0A SIE received when one is not expected

0B SIOS received when one is not expected

0C SIPO received when one is not expected

0D SIB received when one is not expected

0E signalling link congested for the time t111 t31

3 number of the signalling link terminal

4 number of the logical signalling link terminal

5 number of the internal PCM circuit

6 number of the external PCM circuit

7 previous working state of signalling link terminal:

00 IDLE

01 OUT OF SERVICE

02 MONITORING

03 WAIT FOR FISU

04 NOT ALIGNED

05 ALIGNED

06 PROVING

07 LOOP CHECK

08 ALIGNED/NOT READY

09 ALIGNED/READY

0A IN SERVICE

0B EMPTYING

0C UPPER LEVEL OUTAGE

0D LOCAL PROCESSOR OUTAGE

0E REMOTE PROCESSOR OUTAGE

0F BOTH PROCESSORS OUTAGE

10 INTERNAL LOOP TEST

11 EXTERNAL LOOP TEST

DN70600744Issue 16-0 en


List of alarms

Instructions

If the value of 7th supplementary information is 0A (IN SERVICE).

it means that the signalling link given in the 1st supplementary

information has failed and its state has changed from IN SERVICE

to OUT OF SERVICE. The system automatically tries to reactivate

the signalling link.

1. If the value of the 2nd supplementary information is 04,

check data transmission. This error code is typically given

when there is a PCM cutoff. If the exchange terminal does not

indicate PCM cutoff, the bit error ratio is too high for

some other reason, or there are problems in synchronization.

If the signalling link stays unavailable for a long time

and does not realign automatically, monitor the link with

a protocol analyzer in order to solve the problem.

2. If the value of the 2nd supplementary information is 0B,

the remote signalling link terminal has for some reason

detected the link faulty. If this happens repeatedly, ask

the remote end operator what is the reason for this.

If the alarm is caused by a PCM circuit with a high bit error

ratio, the link typically gives error codes 04 and 0B

alternatingly, depending on which end first detects the error

ratio.

3. If the value of the 2nd supplementary information is 02, 03, 05,

08, 09, 0A, 0C or 0D, there is a problem in the operation of

the remote end signalling link terminal. In these cases, no

actions are required from the user. These fault situations are

not common; if these error codes are often given in this alarm,

monitor the link with a protocol analyzer to analyze the

fault situation.

Check that the level 2 error correction method is the same in

both ends of the signalling link: either the basic method or

the preventive cyclic retransmission (PCR). You can check the

error correction method with the MML command NOI:

ZNOI:<parameter set number>;

You can find out the parameter set number with the MML command NCI:

ZNCI:<link number>;

4. The value 0E of the 2nd supplementary information is used only

in ANSI network, and it means that the signalling link has been

restarted as it has been congested for the period of T111 T31.

If this happens repeatedly, there is serious overload in the

signalling network, and increase the capacity or rerouting should be

seriously considered.

5. If the value of the 2nd supplementary information is 01, the

CCNETM has stopped the link. This can happen if, for example,

the test procedure of the signalling link fails. The most

common reason for this is that the signalling link code (SLC)

is not same in both ends.



If the value of the 2nd supplementary information is 06, the link

is out of service and realignment fails. In this case the value of

the 7th supplementary information indicates the phase of the

initial alignment procedure in which errors were detected. Usually

the alignment fails because the bit error ratio is too high.

Analyze the fault with a protocol analyzer.

6. Check that the signalling link bit rate is the same in both ends:

either 64kbit/s or 56kbit/s.

You can check the signalling link bit rate with the MML command NOI:

ZNOI:<parameter set number>;

You can find out the parameter set number with the MML command NCI:

ZNCI:<link number>;

Cancelling

No cancelling.

2.52 1073 V5 DATA LINK LAYER PROTOCOL MISMATCH

Meaning

The protocol (LAPV5) of a V5 interface C-channel's layer 2 has

detected protocol errors. They may be caused either by errors in

the counterpart network element, or an incorrect connection (loop)

in the switching network or somewhere else on the PCM connection.


1 identifier of V5 interface

2 C-channel within V5 interface

3 PCM circuit used by C-channel of V5 interface

4 time slot used by C-channel of V5 interface

Instructions

The alarm appears usually when the transmitting direction of a

data link connection is connected to the receiving direction

inside or outside of the network element. Also, it is possible that

the network element has been configured so that it functions as the

wrong end (AN/LE) of the interface, from the point of view of the

DN70600744Issue 16-0 en


List of alarms

LAPV5 protocol. The LAPV5 protocol itself can be at fault.

It is possible to examine in real time the running values of the

counters that cause the alarm, see instructions on LAPD statistics.

An incremented RECEIPT OF NON-IMPLEMENTED

FRAME counter suggests a loop or an incorrectly configured counterpart,

while the counters RECEIPT OF UNSOLICITED UA, RECEIPT OF FRAME WITH

WRONG SIZE, and N201 ERROR point to an incorrectly functioning

counterpart.

Cancelling

No cancelling.

2.53 1074 EXCESSIVE ERROR RATE ON V5 C-CHANNEL

Meaning

Transmission errors occur on the data link connection of the C-channel

of a V5 interface. The errors appear as checksum errors of the

layer 2 frames.






Instructions

The fault affecting the C-channel of the V5 interface can reside in

in the hardware of the network elements, but it is more likely that

the trouble lies in the data link connections between them, or

in their synchronisations with each other.

The state of the 2 Mbit/s connections can be monitored with an

MML command, see instructions on PCM Statistics.



The synchronisation can be controlled with MML commands, see

instructions on synchronization

In addition to possible breaks and external disturbances, you should

especially check on the data link connection the switching nodes

(ET, distribution frames) and see that the signals of the PCM circuit

and the protective sheath are correctly connected.

The running values of the CRC ERRORS counter (check sum error) which

caused the alarm can be examined in real time, see instructions on

LAPD Statistics.

Cancelling

No cancelling.

2.54 1075 EXCESSIVE RETRANSMISSIONS ON V5 C-CHANNEL

Meaning

Layer 2 of a V5 interface's C-channel is not receiving replies to

the command frames it is sending, due to a partially or completely

malfunctioning counterpart, or breaks on the data link connection.

The alarm generally occurs in connection with temporary or permanent

breaks on the data link connection. The alarm can also indicate

protocol trouble on the data link layer, i.e. the partner program

does not respond in all situations in the recommended way.






Instructions

The fault affecting the C-channel of the V5 interface can reside in

in the hardware of the network elements, but it is more likely that

the trouble lies in the data link connections between them, or

DN70600744Issue 16-0 en


List of alarms

in their synchronisations with each other.

The state of the 2 Mbit/s connections can be monitored with an

MML command, see instructions on PCM Statistics.

The synchronisation can be controlled with MML commands, see

instructions on synchronization.

In addition to possible breaks and external disturbances special

attention on the data link connection should be paid to the

switching nodes (ET, distribution frames) and see that the signals

of the PCM circuit and the protective sheath are correctly connected.

The running values of the UNSUCCESSFUL RETRANSMISSION OF SABME and

RR/RNR/REJ counters, which caused the alarm, can be examined in real

time, see instructions on LAPD statistics.

If it is only the RR frames that receive no reply, the breaks last only

a few seconds, but if the SABME frame goes unanswered, this means that

the link layer connection is out for longer than seconds.

Cancelling

No cancelling.

2.55 1076 FORCED LIGHTWEIGHT SCHEDULING

Meaning

A lightweight hand within a process family has been running for

a period of time that exceeds the limit defined in the parameter

file. The other hands in the family have been waiting for their

turn to run. The running of the hand identified in the supplementary

information of the alarm is stopped and the next hand is allowed to

run, so as not to disturb the functioning of the other hands in the

family.

The situation usually results from a fault in the functioning of

a hand.


1 identifier of the family where forced scheduling was executed

2 process identifier of the hand whose running was stopped

3 focus of the process identifier of the hand whose running



was stopped

4 length of the period, in seconds, that the hand was running

Instructions

There is a temporary disturbance in the functioning of the family.

Since the reason is usually a fault in the application, it is

recommended to inform the local Nokia Customer Service Center on

the fault to investigate the reason for the fault.

The alarm requires no other actions.

Cancelling

No cancelling.

2.56 1077 FREE STACK SIZE BELOW LIMIT

Meaning

The free stack size of the process mentioned in the

supplementary information of this alarm is below the threshold

of 128 bytes. If it continues, the situation may disturb the

functioning of the computer.


1 family identifier of the process whose free stack size is

below the limit. Fields 1, 2 and 3 consist of the complete

identifier of the process in question

2 identifier of the process which set the disturbance, see

description in field 1

3 focus of the process, see field 1

4 free stack size

5 decrease in free stack size was detected because:

DN70600744Issue 16-0 en


List of alarms

1 ESP value was below the threshold

2 values other than zero were detected in the lowest

128 bytes of the stack

Instructions

The alarm indicates a temporary disturbance in the functioning

of the process. The disturbance may have been caused by an error

in the software or packaging, so it is recommended to inform the

local Nokia Customer Service Center in order to detect the

possible fault.

Cancelling

No cancelling.

2.57 1078 PROCESS EXCEPTION

Meaning

A process, specified in the supplementary information of this

alarm, has caused an exception and, as a result, the process has

been frozen. The exception may result from a software or

hardware fault.

The recovery from the freezing of a process may require

maintenance actions, for instance a process restart or a

computer switchover.


1 family identifier of the process that caused an exception

2 process identifier of the process that caused an exception

3 type of exception. Possible values are:

00 division by zero

04 overflow

05 segmentation fault

06 invalid operation code

07 parallel processor missing

08 double fault

09 faulty segment reference in parallel processor



0A invalid Task State Segment

0B segment not present

0C stack exception

0D general protection error

0E page fault

10 error in parallel processor

FF exception not found in the log

4 selector of the exception address.

If the value of field 3 is FF, this field has no significance

5 offset of the exception address.

If the value of field 3 is FF, this field has no significance

Instructions

If the computer has not set alarms on hardware fault,

the reason for the exception is probably a fault in software.

To correct the fault, contact the local Nokia Customer Service

Center.

The alarm requires no further actions.

Cancelling

No cancelling.

2.58 1079 UNSOLICITED V5 DATA LINK RE-ESTABLISHMENT

Meaning

A data link has been re-established on the C-channel of a V5 interface

and it is possible that data was lost in the process.





DN70600744Issue 16-0 en


List of alarms


5 V5 protocol:

00 = PSTN

01 = Control

02 = Link Control

03 = BCC

04 = Protection

Instructions

If the alarm occurs regularly the quality of the link connection

and the condition of the hardware need to be checked. A re-established

connection may be due to an error in the LAPV5 protocol, as perceived

by either the home end or the far end, or to a short break.

The running values of the counters causing the alarm can be examined

in real time, see instructions on LAPD statistics.

The protocol errors detected by the local exchange

are gathered in counters Q.921 ERROR COUNTERS (B,E,J,L,N,O). The

re-established connections caused by short breaks are registered in

counter I.

Cancelling

No cancelling.

2.59 1080 PROCESS STOPPED

Meaning

A process defined in the supplementary information fields of this

alarm is in a situation where it is impossible to continue

execution. The process is stopped on purpose. The fault situation

is usually a result of erroneous packaging or functioning.

Stopping the process may require maintenance, for instance, a

process restart or a computer switchover.




1 family identifier of the process that was stopped

2 process identifier of the process that was stopped

3 the fault was noticed by:

01 LIBGEN library

02 code produced by the TNSDL translator

4 cause of the failure. Values set by system program library:

01 master calling for stopping

02 FAMILY_SERVICES_IN_USE attribute missing

03 error in buffered message reception

04 incorrect family generation

05 no more LDT slots

06 saving the message failed

07 numbers of hand types not valid

08 hand initialization failed

09 incorrect user for the routine lib_TNSDL_stop_r

0A incorrect user for the routine lib_TNSDL_create_r

0B incorrect user for the routine lib_receive_msg_r

0C parameter error, MIN_FREE_TIME

0D parameter error, START_PTR

0E parameter error, TRANSITION_PTR

0F internal error in reserving data area for lightweight hand

10 internal error in saving the stack

Values set by the TNSDL translator:

80 master called for STOP statement

81 overflow in user's encode routine

82 overflow in system's encode routine

83 error in user's decode routine, FPAR of hand

84 error in user's decode routine, internal INPUT

85 internal message queue full

86 internal message queue empty

87 error in user's decode routine

88 message too short

89 table indexed beyond the index area

5 additional information on the fault. The field is only in use

if field 4 has one of the below-mentioned values,

the meaning of the field is also explained

01 lower word of the return address offset

81 number of message being handled at the time of the error




89 identifier of the source code file where the erroneous

reference is made (internal identifier of the translator)

DN70600744Issue 16-0 en


List of alarms




01 upper word of the return address offset

89 row number of the source code file where the erroneous

reference is made




01 return address selector

89 index used in erroneous indexing

Instructions

The fault usually lies in the software or the packaging, therefore,

it is recommended to inform the local Nokia Customer Service Center.


Cancelling

No cancelling.

2.60 1082 HAND USAGE LIMIT EXCEEDED

Meaning

The number of free hands of a hand type in a process family

(indicated in the supplementary information fields of this

alarm) has dropped below the supervision threshold during

the measurement period.

If there are no free hands of a certain hand type, that type

of hands cannot be reserved, and this may thus disturb the

functioning of the computer.


1 family identifier

2 hand type identifier



3 minimum percentage of free hands in a given hand type

during the supervision period

4 supervision limit percentage

5 minimum number of free hands in a given hand type during

the supervision period

6 number of free hands in a given hand type at the end of

the supervision period

Instructions

The cause of the disturbance may be a fault or an overload

situation, or an insufficient number of hands in a given hand

type. Also, the supervision parameter values may be too low.

If the number of free hands in a given hand type has in fact

been small, increase the number of hands in the DXPARA file

used in the computer. The number of hands can be increased by

packaging a new file or by modifying the number of hands in

the file used in the exchange by means of the STYMIE service

terminal extension. The modified number of hands will be

valid after the next loading restart of the computer.

Cancelling

No cancelling.

2.61 1083 SEMAPHORE USE ERROR

Meaning

The system has detected an error in a semaphore handling routine of

the operating system kernel. The error may disturb the functioning

of the erroneous application or the co-operation of applications.


1 family identifier of the process that called the routine where an

error was detected

2 process identifier of the process that called the routine where an

DN70600744Issue 16-0 en


List of alarms

error was detected

3 error code describing the error detected. The possible values are:

257d error in semaphore name

258d attempt to use the semaphore in a way not allowed by

protection

259d illegal attempt to initialize the semaphore

260d ENTER_REGION routine call in a critical area

261d EXIT_REGION routine call outside a critical area

4 selector part of the call return address

5 offset part of the call return address

Instructions

There is a fault in software or packaging, therefore, it is

recommended to inform the local Nokia Customer Service Center in order

to find out the reason for the fault situation.


Cancelling

No cancelling.

2.62 1084 V5 ISDN USER PORT FAILURE

Meaning

A momentary failure has occured in the operation or control of

a V5 ISDN user port. Frames or commands received were not

identified, or LAPD protocol errors were found in them.



2 number of C-channel

3 identifier of V5 user port (EFaddr, L3addr)

4 SAPI value used by D-channel:



0 signalling of ISDN line

FF incorrect address field structure, or SAPI value

not recognisable

5 TEI value used by D-channel:

0...7E terminal ID identifier (TEI)

FF incorrect address field structure, or TEI value

not recognisable

6 type of fault:

01 EFaddr of received ISDN frame unknown

02 ISDN user port ID of received control message

unknown

03 D-channel protocol error (retransmissions, frame errors)

Instructions

If the ISDN user port ID of the received frame is unknown, check

that the corresponding subscriber has been created and defined in

the V5 interface and C-channel in question. If the subscriber is not

supposed to be created, corrective measures need to be taken at the

other end of the interface (AN).

If the ISDN user port ID of a control message received from a higher

level is unknown, an error has occured when the subscriber data was

updated. The system will endeavour to correct the error automatically.

If the fault persists, recovery should be attempted by means of a

switchover and/or restart. If protocol errors occur repeatedly,

check if other ISDN subscribers using the same channel have the same

fault, and if they do, check especially the condition of the data

link connection in the V5 interface in question. It is possible that

the interface between the ISDN subscriber and the network needs to be

checked, as well as the condition of the D-channel throughout the

network (AN). These have to be checked also when protocol errors

happen to individual subscribers.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.63 1085 V5 ISDN USER ACCESS OVERLOAD

Meaning

The D-channel of a V5 interface has an overload situation on layer 2.

The overload can be caused if the C-channel containing the D-channel

in question is incorrectly dimensioned, if the entire switch becomes

overloaded, or if the PCM circuit or subscriber line interface has

a bad error ratio.



2 identifier of V5 user port (EFaddr, L3addr)

3 service access point identifier (SAPI) value used by

overloaded D-channel:

0 signalling of ISDN interface

FF SAPI value not recognisable

4 terminal endpoint identifier (TEI) value used by overloaded

D-channel:

0...7E terminal identifier (TEI)

FF TEI value not recognisable

5 cause of overload:

01 an abundance of faulty layer 2 frames received

02 too many layer 2 frames received

03 layer 3 signalling messages received cannot be

delivered to host computer

Instructions

The alarm may be a random network disturbance, in which case no

immediate action need be taken. If, however, the alarm appears

regularly, or together with other alarms, and if based on these

alarms it can be assumed the service level of ISDN subscribers is

likely to suffer, the following checks can be carried out:

If a lot of faulty layer 2 frames are received, check the condition

of the PCM circuit used by the C-channel of the V5 interface in

question.

The condition of the data link connection can be monitored with

an MML command, see instructions on PCM Statistics.

The check sum errors of the frames (CRC ERRORS)



can be examined in real time on the C-channel, see instructions on

LAPD Statistics.

If a lot of layer 2 frames are received, check the dimensioning

of the C-channel in question with reference to ISDN signalling.

Subscribers may have to be moved to other C-channels. It is also

possible that an ISDN terminal is malfunctioning, or that there

is an unsatisfactory error ratio on the D-channel connecting the

terminal and AN, and this manifests itself in the exchange (LE)

as retransmissions.

If the received signalling messages cannot be delivered to the host

computer, check the dimensioning of the C-channel, the signalling

terminal, and the host computer unit in question.

Cancelling

No cancelling.

2.64 1088 CONNECTION ERROR BETWEEN MSC ANDSMSC

Meaning

The SMSC's request for establishing a connection to the MSC has been

rejected, or the connection between them has failed. Short message

traffic for that SMSC has been interrupted.


1 reason for the alarm

the possible numeric values are:

0 reason unknown

1 time supervision for establishing the connection

2 SMSC undefined

3 SMSC's IP address undefined

4 password incorrect

5 system error

6 time supervision for the connection

7 local connection problem

8 connection problem in the SMSC

2-10 ISDN address of the short message service centre

It is used when the mobile-originated short messages are routed

DN70600744Issue 16-0 en


List of alarms

to the SMSC. The SMSC's ISDN addresss is connected with an IP

address and a password in an analysis that the user creates

in the MSC. The ISDN address is in the international E.164 format.

The address has been coded in the table so that two numbers are

placed in one byte. The rest of the free half-bytes in the table

have been filled with 0xF

Instructions

1. Check whether the SMSC should really be able to establish the

connection. If not, take action to prevent unauthorized use

and move to step 8. If the SMSC should be able to establish

the connection, move to the next step.

2. Analyse the log files of the system to check the details of

the alarm (the SMSC's IP address). Establish a service terminal

connection to the unit that issued the alarm and give the ZGD

command. It shows you the log file lists where you can check the

details of the alarm. Move to the next step.

3. Give the MML command CFI (MSC Digit Analysis) to check that the

necessary analysis exists. If the analysis is missing, create a

new analysis with the MML command CFS. Move to the next step.

4. Check that the SMSC uses the password and IP address defined in

the analysis. Move to the next step.

5. Check the state of the SMSC. If the connection exists, wait a

while for the missing connection to become active. If the

situation does not go back to normal, move to the next step.

6. Check that the connection between the MSC and the SMSC is in

order (especially if the error code of the alarm is 6, 7 or 8).

7. Activate the SMSC so that it tries to re-establish the connection.

If the connection is established, move to the next step. If the

connection is not established, move to step 2 again.

8. Ready.

Cancelling

No cancelling.



2.65 1089 DYNAMIC LDT SLOTS EXHAUSTED

Meaning

All the local descriptor table slots for the process family's

dynamic use are reserved and the reservation of a new slot

has failed. The error disturbs the functioning of the process

family and thus possibly the functioning of the whole computer.

The fault may be in packaging, that is, an insufficient number of

dynamic local descriptor table slots in comparison with the

number of hand processes are reserved for a family. The fault

may also be in software, that is, too many slots are reserved.

The process family indicated in the supplementary information

fields of this alarm is not always the one whose descriptor

table is full, because some operating system routines handle

tables other than the process family's own local descriptor table.

This is especially the case when the family identifier is 108.


1 family identifier of the process that called the routine

where an error was detected

2 process identifier of the process that called the routine

where an error was detected



Instructions

1. Output the resource information of the process family

indicated in the alarm by using the DOI command. This will

help to determine the fault. Useful information can also be

obtained from the operating system log or the computer log.

2. Inform the local Nokia Customer Service Center of the fault

detected.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.66 1090 BUFFER HANDLE ERROR

Meaning

A process has called a buffer handling routine with an incorrect

buffer handle. A typical situation is a failure in the release of

the buffer, so that the buffer remains occupied by the process.


1 family identifier of the process that called the routine where an

error was detected

2 process identifier of the process that called the routine where an

error was detected



Instructions

The fault is in the software, therefore, it is recommended to inform

the local Nokia Customer Service Center.

Cancelling

No cancelling.

2.67 1091 TOO MANY EXECUTED SUBANALYSES INEXTENDED PREANALYSIS

Meaning

More than the allowed number of subanalyses of the extended preanalysis have

been executed. Too many consecutive subanalyses may weaken the performance of

the exchange. The call set-up continues normally.




1 the name in text format of the subanalysis which contains too many

subanalyses in an extended preanalysis chain.

2 of the two sides of the subanalysis, the one whose execution caused

the alarm to be set

0 = normal side of the subanalysis

1 = test side of the subanalysis

Instructions

Find out if the operation in question can be succesfully executed with a

smaller amount of subanalyses. The number of subanalyses to be executed

should be less than the value of the parameter MAX_EXP_SUBANA_NBR (identifier:

80) to be output with the MML command WOI:7;

The value of parameter MAX_EXP_SUBANA_NBR shows the maximum amount of

subanalyses to be executed in an extended preanalysis. This maximum

number should not yet weaken the performance of the exchange too much.

You can check the attribute analysis chain starting from the subanalysis

whose execution caused the disturbance. For more instructions, see the

Feature Description for feature 929: Extended Preanalysis.

You can make the decision about modifying the attribute analysis.

Cancelling

No cancelling.

2.68 1092 COMMUNICATION FAILURE IN FIELDREPORTING

Meaning

Reading of traffic data from the statistical unit, or back-up

copying of field reporting files, has temporarily failed due to

a fault, or overloading of statistics or the I/O system.

The next regular or intermediate report may therefore contain

information that is inexact.

DN70600744Issue 16-0 en


List of alarms


1 file number:

5C0000 = FACILI = subscriber facilities

4B0000 = SERLEV = service grade counters

5940000 = NORELC = service grade clear code counters

5930000 = DERELC = service grade counters by clear code group

6500000 = ACGAPP = service number counters

2 error code:

1d reading of traffic data failed

2d back-up copying failed

You can check the meaning of other error codes in General


Instructions


Cancelling

No cancelling.

2.69 1093 OUTPUT FAILURE IN FIELD REPORTING

Meaning

The output of the regular field report has failed because the I/O

system is overloaded, the I/O device is not in order, the logical

output file used to print the report is not properly connected

to the I/O device, buffer memory for making the report cannot be

reserved, or a field reporting file cannot be opened.


1 error code given by I/O system.

General error message of the system. You can check its meaning

in the General Error Messages of System



2 observation type:

00 subscriber facilities (FAC)

01 restarts (RES)

02 all grade of service data (SER)

03 intelligent network (IN) services (ACG)

04 number of calls in the exchange (TRF)

05 clear codes of all calls (CLR)

06 clear codes of one outgoing number destination (CLS)

07 clear code groups by number destinations (DES)

08 signalling specific clear codes of specified circuits (SSC)

09 data call clear code groups by number destination (DAT)

0A data call clear codes (DCL)

0B signalling specific clear codes of all circuits (SSCA)

Instructions

Check that the I/O device used to print reports is in order and

in correct working state (MML command ISI), and that the following

logical output files have been connected to the said device:


=======================================================================

ascii bin xml

FIELFACA FIELFACB FIELFACX Field Reporting of facility usage

FIELRESA FIELRESB FIELRESX Field Reporting of unit restarts

FIELTRFA FIELTRFB FIELTRFX Field Reporting on trafficability

performance

FIELCLRA FIELCLRB FIELCLRX Field Reporting on clear codes

FIELCLSA FIELCLSB FIELCLSX Field Reporting on clear codes of

one destination

FIELDESA FIELDESB FIELDESX Field Reporting on destination-specific

clear code groups

FIELACGA FIELACGB FIELACGX IN service gapping report

FIELASSA FIELASSB FIELASSX Signalling-specific clear code

measurement report, part 2

FIELSSCA FIELSSCB FIELSSCX Signalling-specific clear code

measurement report, part 1

FIELDATA FIELDATB FIELDATX Data call clear code group by number

destination measurement

FIELDCLA FIELDCLB FIELDCLX Data call clear code measurement

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.70 1095 TRAFFIC MEASUREMENT OUTPUT FAILURE

Meaning

The traffic measurement report output on the I/O device used for

printing the report has failed.


1 measurement type

CGR CIRCUIT GROUPS

DEST DESTINATIONS

CNTL CONTROL UNITS

SUBS SUBSCRIBERS

TCAT TRAFFIC CATEGORIES

BS CELLS

SMO SUBSCRIBER MODULES

ANN ANNOUNCEMENT CHANNELS

CTD CIRCUIT GROUP TO DESTINATION

DTD DESTINATION TO DESTINATION

VAN VOICE ANNOUNCEMENT

RSS REMOTE SUBSCRIBER STAGE

BCH BEARER CHANNELS

2 error code 154d is output to this field, if no reply to

the report output request is received from the RFGPRB program

block. Otherwise, any of the error codes returned by the said

program block is output. You can check their meaning in General


Instructions

Check that the operation and maintenace unit (OMU) is in state WO-EX.

Check also that the output device connected to the logical file of

the measurement in question is in order.


=========================================================

ascii bin xml

TRACGRA TRACGRB TRACGRX CIRCUIT GROUPS

TRADESTA TRADESTB TRADESTX DESTINATIONS

TRACNTLA TRACNTLB TRACNTLX CONTROL UNITS

TRASUBSA TRASUBSB - SUBSCRIBERS

TRATCATA TRATCATB TRATCATX TRAFFIC CATEGORIES

TRASMOA TRASMOB - SUBSCRIBER MODULES

TRABSA TRABSB TRABSX CELLS

TRAANNA TRAANNB TRAANNX ANNOUNCEMENT CHANNELS



TRACTDA TRACTDB TRACTDX CIRCUIT GROUP TO DESTINATION

TRADTDA TRADTDB TRADTDX DESTINATION TO DESTINATION

TRAVANA TRAVANB TRAVANX VOICE ANNOUNCEMENT

TRARSSA TRARSSB - REMOTE SUBSCRIBER STAGE

TRABCHA TRABCHB - BEARER CHANNELS

Cancelling

No cancelling.

2.71 1096 TRAFFIC ANALYSIS COMMUNICATIONFAILURE

Meaning

The message exchange with the Traffic Analysis Program Block (TRCANA) and

the Statistical File Services Program Block (TFIPRB) has failed. Temporary

inaccuracies may occur in the measurement results.


Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.72 1097 TRAFFIC ANALYSIS OUTPUT FAILURE

Meaning

The output of a peak hour method report (see Peak Hour Traffic

Measurement, Operating Manual) onto magnetic tape or onto

the I/O device used to print reports has failed.


1 failed output

01 output of daily peak hour traffic sample record onto tape

recorder

02 output of circuit group specific or growth alarm report onto

I/O device used to print reports

03 output of end-of-day report onto I/O device used to

print reports

04 output of end-of-day report onto magnetic tape

05 output of intermediate report onto I/O device used to

print reports

2 154d, if the program block RFGPRB does not respond to

the printing request.

In other cases, an error code returned by the program block

RFGPRB. You can check its meaning in General Error Messages

of System

Instructions

Check that the output device is in order, and that the logical

output file MTTRAN is connected to the correct magnetic tape and

correspondingly TRAMES2 file to the correct I/O device by II-MML

commands.

Cancelling

No cancelling.



2.73 1098 TOO LONG MESSAGE

Meaning

A message to be received is longer than the area reserved for

message reception, therefore, receiving the message to the

process data area was only partially successful.

If the process does not check whether message reception was

successful, the process may erroneously read information in the

data area outside the reception area as the end part of the message,

and interpret that data according to message structure.


1 family identifier of the process that received a message to

an insufficient reception area

2 process identifier of the process that received a message to

an insufficient reception area

3 message length

4 message sender's computer

5 message sender's family identifier

6 message sender's process identifier

7 message number

Instructions

The fault is in software or packaging, therefore, it is recommended

to inform the local Nokia Customer Service Center in order to

correct the fault situation.


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.74 1099 FAILURE IN TRAFFIC SAMPLING

Meaning

Due to a fault or to overloading of statistics or of the Central

Memory, the calibration of circuit group file of statistics as

regards circuits that are in use has failed. For this reason, the

traffic measurement report and the load supervision report related

to the circuit groups (as well as the circuit group report of the

peak hour traffic measurement) may contain faulty information on

the number of circuits in the circuit group.


1 circuit group number in hexadecimals

Instructions

Check that the central memory is operational. Output the data

on the circuit group mentioned in the alarm with the MML command RCI.

Outputting should be performed without error and the data should not

contain errors.

Cancelling

No cancelling.

2.75 1101 LSP RESTARTED

Meaning

The processor of the LSP plug-in unit has restarted.

The CASSIG initializes the control data of the LSP,

and releases the calls controlled by the LSP.




1 plug-in unit type

2 plug-in unit index

Instructions





Cancelling

No cancelling.

2.76 1102 LSP RAM FAILURE

Meaning

An error has been detected in the RAM memory of an LSP plug-in unit.


1 plug-in unit type


Instructions





DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.77 1103 SIGNALLING MEASUREMENT REPORT LOST

Meaning

The forming or outputting of signalling measurement report

in the defined device has failed. The reason may be in the

definition of the logical file used in the outputting of the

report, or in the switching, or the reason may be the wrong

operating state or overload of one of the I/O-devices which

the logical file in question is linked with.


1 the lost report:

01 SIGNALLING LINK AVAILABILITY

02 SIGNALLING LINK PERFORMANCE

03 SIGNALLING LINK UTILIZATION

04 SIGNALLING POINT STATUS

05 SIGNALLING LINK SET AND ROUTE SET AVAILABILITY

06 SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINT

07 SIF AND SIO OCTETS HANDLED WITH SIO

08 SIF AND SIO OCTETS HANDLED WITH OPC, DPC AND SIO

09 SCCP SIGNALLING POINT METERS

0A SCCP SUBSYSTEM METERS

0B SCCP LOCAL SUBSYSTEM AVAILABILITY

0C SCCP SINGLE METERS

0D TC PERFORMANCE AND UTILIZATION

0E TRANSMITTED AND RECEIVED FRAMES AND OCTETS ON

D-CHANNEL

0F D-CHANNEL MISCELLANEOUS STATISTICAL METERS

10 Q.921 ERROR METERS

11 TC TRANSACTION METERS

20 SIGNALLING LINK INTERVAL LOG

21 MTP SIGNALLING POINT INTERVAL LOG

22 SCCP SIGNALLING POINT INTERVAL LOG

23 SCCP SEGMENTATION AND REASSEMBLY ERRORS INTERVAL LOG

24 TC INTERVAL LOG

25 SCCP GT TRANSLATION ERRORS LOG

2 the value 154d will be output in the field if RFGPRB

program block gives no answer to the output request of



the report. Otherwise some other general error code will

be output. You can check the meaning of error codes in

General Error Messages of System.

Instructions

Make sure that the operation and maintenance unit (OMU) is in

the WO-EX state. Make sure that the connection of the logical

file of the measurement in question is in order, i.e. that

the logical file is further connected to another logical file

(e.g. binary report file to the MEAFIL) or to a working

I/O-device.

If the logical files of binary reports are connected to the

MEAFIL file, make sure that the MEAFIL is connected to the

virtual data storing device (VDS).


.............................................

ascii bin

MTP measurement reports:

MTPSLAVAIA MTPSLAVAIB SIGNALLING LINK AVAILABILITY

MTPSLPERFA MTPSLPERFB SIGNALLING LINK PERFORMANCE

MTPSLUTILA MTPSLUTILB SIGNALLING LINK UTILIZATION

MTPSPSTATA MTPSPSTATB SIGNALLING POINT STATUS

MTPSLSAVAA MTPSLSAVAB SIGNALLING LINK SET AND ROUTE SET

AVAILABILITY

MTPOCTHSPA MTPOCTHSPB SIF AND SIO OCTETS HANDLED WITH

SIGNALLING POINT

MTPOCTSIOA MTPOCTSIOB SIF AND SIO OCTETS HANDLED WITH

SIO

MTPOCTMATA MTPOCTMATB SIF AND SIO OCTETS HANDLED WITH

OPC, DPC AND SIO

SCCP/TC measurement reports:

SCCPSPA SCCPSPB SCCP SIGNALLING POINT METERS

SCCPSSA SCCPSSB SCCP SUBSYSTEM METERS

SCCPLSSAVA SCCPLSSAVB SCCP LOCAL SUBSYSTEM AVAILABILITY

SCCPSINGLA SCCPSINGLB SCCP SINGLE METERS

TCAPPUA TCAPPUB TCAP PERFORMANCE AND UTILIZATION

TCAPTRANSA TCAPTRANSB TC TRANSACTION METERS

LAPD measurement reports:

LAPDFROCA LAPDFROCB TRANSMITTED AND RECEIVED FRAMES

AND OCTETS ON D-CHANNEL

LAPDMISCCA LAPDMISCCB D-CHANNEL MISCELLANEOUS STATISTICAL

METERS

LAPDQ921EA LAPDQ921EB Q.921 ERROR METERS

MTP interval log reports:

MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORT

MTPSPLOGA SIGNALLING POINT INTERVAL LOG

REPORT

DN70600744Issue 16-0 en


List of alarms

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.

2.78 1104 NO RESPONSE TO LSP SUPERVISIONMESSAGE

Meaning

The LSP program block (LSPPGM) has not responded in the specified

time to the supervision message sent by the USAPRO program block

of the CAC or the LSU.


1 plug-in unit type


Instructions





Cancelling

No cancelling.



2.79 1105 LINE SIGNALLING RECEIVE OVERLOAD

Meaning

The receiving of line signals is overloaded.


1 plug-in unit type


3 error code

0 the buffer of the signal receiver in the LST plug-in unit

is full

1 the LSPPGM message buffer for received signals is full

2 the LSPPGM message buffer for supervision messages

is full

3 the message buffer between the modules

(RTC85-LSPREC) of the LSPPGM is full

4 all the filtering time counters of LSPPGM are in use

5 the message buffer for received signals in the

AS7_U plug-in unit is full

Instructions





Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.80 1107 LINE SIGNALLING SEND OVERLOAD

Meaning

The sending of line signals is overloaded. The situation may be caused

by overloading or by a defect in the plug-in unit. If the alarm is

repeatedly directed to the same plug-in unit, the plug-in unit is

probably defective.


1 plug-in unit type


3 error code

0 the signal message buffer (used for message sending) between

the LISEND program block and the LSP plug-in unit is full

1 the supervision message buffer (used for message sending)

between the LISEND program block and the LSP plug-in unit

is full

2 the signal message buffer (used for message sending)

between the LISEND program block and the AS7-U plug-in unit

is full

3 the command message buffer between the LISEND program block

and the AS7-U plug-in unit is full

4 the message buffer between the modules of the LSPPGM

(RTC85-LSPSND) is full

5 all transmission counters of the LSPPGM are in use

Instructions





Cancelling

No cancelling.



2.81 1108 LINE SIGNALLING SEND OVERLOAD

Meaning

The sending of line signals is overloaded.


1 FF not in use

2 LSP number

3 FF the message buffer between the modules of LSPPGM

(RTC85-LSPSND) is full

4 FF all sending counters of LSPPGM are in use

Instructions





Cancelling

No cancelling.

2.82 1111 RESTART DUE TO TIME OUT REQUESTED

Meaning

Software configuration management has asked the recovery system

for system restart, but recovery has sent a negative response or

has not responded at all, and no restart has been made.

DN70600744Issue 16-0 en


List of alarms


1 reason for informing about disturbance:

00 recovery system has given negative response

to system restart request

01 recovery system has not responded to system

restart request

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.

Instructions


Cancelling

No cancelling.

2.83 1113 STATISTICS MEASUREMENT OUTPUTFAILURE

Meaning

The outputting of statistics measurement report in the

defined I/O device has failed.

The reason may be one of the following:

- overload of the I/O system

- I/O device is not functional

- connection of the logical file used in the outputting of

the report to the I/O device is not in order

- report hand process of the program block (AMNPRB) has not

responded to the report request

- reading or writing of the measurement file has failed

The data of the measurement that has caused the alarm will

disappear or, if the measurement report is outputted, the

data in it may be faulty.




1 name of the statistics measurement whose report

output failed

2 version number of the measurement

3 error case:

01 error in the I/O system. A more detailed reason for

the error is given in the next supplementary

information field

02 no reply to a report request. The report is sent to

be outputted to the report hand process of the

program block (AMNPRB) or the report generation

program block (RFGPRB).

03 reading or writing of the measurement file has failed

04 reserving buffer for the report message failed

05 error in copying data to the report message

4 reason for the error. Significant only if the previous

field (error case) has the value 01:

0d more detailed reason for the error not

other values known error code returned by the I/O

system. You can check its meaning in the

General Error Messages of System

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 ISI) and that the logical output file STATMEAB

is connected to the device in question (MML command IID).

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.84 1116 ERROR IN CHARGING

Meaning

Error in charging. The charging program block responds to the

charging message with an error code, or does not respond within

the limits of time control.


1 error code

0000$0001B error detected with automaton_0

0000$0010B error detected with automaton_1

0000$0100B message erroneous

0000$1000B all automata reserved

0001$0000B charging automaton reserved

FFH charging program block has not responded within

the time limit the error code is a combination

of the codes given above

2 number of the message where the error occurred

Instructions


Cancelling

No cancelling.

2.85 1117 ERROR IN LINE SIGNALLING

Meaning

The incoming line signal is not within permitted limits. The

length of the line signal is in a range where interpretation

is uncertain.




1 PCM circuit of the connection

2 timeslot of the connection

3 state of the connection

4 unit of the partner connection

5 PCM circuit of the partner connection

6 timeslot of the partner connection

7 message sender

8 message identifier

Instructions


Cancelling

No cancelling.

2.86 1118 UNKNOWN LINE SIGNAL

Meaning

There is a conflict between the state information in the circuit of the

channel-associated signalling program block (CASSIG) and a new

incoming input signal.





DN70600744Issue 16-0 en


List of alarms




7 message sender


Instructions


Cancelling

No cancelling.

2.87 1119 ERROR IN LINE SIGNALLING INCOMINGMESSAGE

Meaning

There is a conflict between the message coming to the channel-associated

signalling program block (CASSIG) and the files of the program block.










7 message sender


Instructions


Cancelling

No cancelling.

2.88 1120 ERROR IN LINE SIGNALLING PARTNERPROGRAM BLOCK

Meaning

CASSIG failed to communicate with another program block.

CASSIG received an erroneous answer or no answer at all.






FF no significance


0d no significance


0d no significance

7 message sender


DN70600744Issue 16-0 en


List of alarms

Instructions


Cancelling

No cancelling.

2.89 1121 CIRCUIT CLEAR MISSING

Meaning

The releasing of the circuit failed. The circuit remains seized.








7 message sender


Instructions


Cancelling

No cancelling.



2.90 1122 IMPULSE NOT IN TOLERANCES

Meaning

The CASSIG program block has detected that the received dialling

impulse is not within tolerances.


1 PCM of the connection

2 time slot of the connection

3 state information of the connection

4 partner unit

FF no significance

5 PCM of the partner connection

00 no significance

6 time slot of the partner connection

00 no significance

7 message sender


Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.91 1123 NUMBER NOT IN TOLERANCES

Meaning

The CASSIG program block has detected that the received

number is not within tolerances.


1 PCM of the connection


3 state information of the connection

4 partner unit

FF no significance

5 PCM of the partner connection

00 no significance

6 time slot of the partner connection

00 no significance

7 message sender


Instructions


Cancelling

No cancelling.



2.92 1125 TRIAL CONFIGURATION DELETED

Meaning

The recovery system has deleted the trial configuration, because

a) in connection with the latest OMU restart, automatic return

changed the software build to another because of a fault situation

or

b) a system restart occurred in a situation where the OMU (non-redundant)

was not in the trial


1 error code which indicates the reason for deleting the trial

configuration. You can check its meaning in General Error

Messages of System.

Instructions

Check the OMU BLACKBOX for the reason why

a) the software build was changed during the latest restart

or

b) the OMU and the whole system was restarted.

Cancelling

No cancelling.

2.93 1127 VANG POWER SUPPLY FAILURE

Meaning

The VANG plug-in units equipped in the target unit did not have any

power supply.


DN70600744Issue 16-0 en


List of alarms

Instructions

The alarm requires no actions. The system recovers from the situation

by loading speech sample files to the VANG plug-in units equipped in

the target unit.

Cancelling

No cancelling.

2.94 1128 EXCESSIVE DISTURBANCES IN FILELOADING

Meaning

File loading has been interrupted due to recurring errors.

The unit is restarted to recover from the errors.


1 general error message of the system. You can check its meaning with

a command of the service terminal extension MRS or in General Error

Messages of System

2 identifier of the family that detected the error

USAPRO (A0): error detected by unit state administration

FEMSER (2A3): error detected by file server for memory files

The error may also be detected by a database manager

3 message bus address of the computer where the failed

loading was executed

4 load group source

01 memory

02 disk

5 load type

01 virtual loading

02 immediate loading

6 load group

7 identifier of the file whose loading failed



Instructions


Cancelling

No cancelling.

2.95 1130 EXTERNAL CALL CLEARING

Meaning

A trunk circuit which is either in the call phase or in the call

set-up phase has become idle because of signalling information

received from the trunk circuit.


1 error code

01 inconsistent signalling message from message transfer part

02 reset-circuit message

03 metering pulse message in which number of pulses is zero

FF not enough data for determining other error code

2 PCM circuit

3 timeslot

4 heading codes of the signalling message

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.96 1136 SIGNALLING MESSAGE DISTRIBUTIONERROR

Meaning

The alarm is issued when CCRECE receives from a signalling link

a message which it cannot distribute to the user part concerned.


1 error code:

01 PCMCON file access error

02 COSPPC file access error

03 CIINTA file access error

2 value of service information octet (SIO) of received

signalling message

3 value of destination point code of received

signalling message

4 value of originating point code of received

signalling message

5 value of signalling link selection field of received

signalling message

6 the value of the circuit identification code field of such

a received signalling message that contains the field, e.g.

the signalling messages of the TUP and ISUP user parts

7-9 next three bytes after the user label in the signalling

message received from the signalling link

Instructions

Check whether the error is caused by the files or by a faulty

message.

Cancelling

No cancelling.



2.97 1137 INCORRECT SIGNALLING MESSAGE FROMSIGNALLING TERMINAL

Meaning

An erroneous signalling message has been received from a plug-in unit.

There is a failure or a disturbance in the plug-in unit, or the

content of the signalling message sent by the partner exchange is

faulty. The incoming signalling message is deleted, and if the

disturbance is caused by a faulty signalling terminal, the call

setup or call termination of a single call can be affected.


1 error detected in signalling message

01 signalling message is too long

02 service information octet is faulty

2 type of plug-in unit

3 index of plug-in unit

4 logical number of signalling terminal

5 value of service information octet (SIO) of received

signalling message

6 value of destination point code of received

signalling message

7 value of originating point code of received

signalling message

8 value of signalling link selection field of received

signalling message

Instructions

Check with the MML command AHO if the alarm 2075

(COMMUNICATION FAILURE BETWEEN SIGNALLING TERMINAL AND CCNETM)

has been issued. If it is and the alarm 1137 has been given

only once or very occasionally, act according to the instructions

of the alarm 2075.

The plug-in unit identified in supplementary information 2 and 3

may be faulty. Perform a switchover of the alarm's target unit

with the MML command USC. Change into testing state the unit

where the plug-in unit that is suspected faulty is located.

DN70600744Issue 16-0 en


List of alarms

Run diagnostics for the unit to find out whether the plug-in unit

is faulty, see instructions on Diagnostics and Testing.

Replace the plug-in unit, if diagnostics detects that it is

faulty. See Instructions for Replacing Plug-in Units.

Check also with the MML command AHP whether the alarm 2224

(ERROR IN MSU HANDLING) has been issued. If it is, act according

to its instructions.

If the cause of the disturbance was not discovered with these

actions, check out the log of the unit that issued the alarm with

the service terminal command ZGD. If the log text "INCORRECT MSG

FROM TERM TYPE x" is found, store the contents of the terminal

control mailbox identified in the message's data for later

examination. Store also the alarm history before and after

the alarm 1137 was given and, if necessary, contact the local

Nokia Customer Service Center.

Cancelling

No cancelling.

2.98 1139 FIELD REPORT OF ROUTING COMPONENTSFAILED

Meaning

Outputting to the desired I/O device the "ATTRIBUTE DIRECTED ROUTING

REPORT" related to field reporting has failed.

The failure can be caused by overloading of the I/O system, or because

either the I/O device or the connections of the I/O device are out of

order.


1 error:

01 error in the I/O system, reason of error in supplementary

information field 2

02 TEXTPR has not responded to service request

03 CMREAD has not responded to report request

04 creating a hand has failed



2 error code

00 : reason for error not known

other values : error code returned by the I/O system. You can

check its meaning in General Error Messages

of System

Instructions

Check that the I/O device used for outputting the report is functional,

and that the logical output files ADRROUTA and ADRROUTB are directed

to that device.

Cancelling

No cancelling.

2.99 1140 FREE LDT SLOT COUNT BELOW LIMIT

Meaning

The free dynamic LDT slot count of a process indicated in the

supplementary information fields of this alarm is below the

supervision limit indicated by the process.

The fault may be in packaging, that is, an insufficient number of

dynamic local descriptor table slots in comparison with the

number of hand processes are reserved for a family. The fault

may also be in software, that is, too many slots are reserved or

the supervision limit is set to be unnecessarily high. In such

case the slot count may fall below the limit even in normal operation.

In case the dynamic LTD slot count falls below the supervision limit,

it is highly probable that the number of slots has been significantly

reduced, and the reason for this should be clarified

immediately.

When the family has no more dynamic LDT slots the family is restarted,

which may interfere with the functioning of the computer. Disturbance

observation 1089 is set when there are no more dynamic LDT slots.

DN70600744Issue 16-0 en


List of alarms


1 family identifier of the process whose free dynamic LDT slot count

is below the limit

2 number of family's free dynamic LDT slots

3 supervision limit

4 supervision interval in seconds

Instructions

1. Display the resource status of the process family indicated

in the additional information field of the alarm by using the

MML command DOI.

2. Create a long-term family resource status measurement using

the MML command DOF and start the measurement by giving the MML

command DOG. The measurements are displayed to the logical file

OSSTATREP. Connect the logical file OSSTATREP to I/O terminal

using the MML command IIS.

3. Contact the local Nokia Customer Service Center. Displaying

the resource status and providing these results speeds

up the correction of the fault.

Cancelling

No cancelling.

2.100 1141 DELAY BUFFER OVERFLOW IN SIGNALLINGTERMINAL

Meaning

The delay buffer of a plug-in unit is full. Messages are deleted

when the delay buffer is in use, so that the signalling traffic is

disturbed. The overflow situation may be caused by overload or a

failure in the plug-in unit. The alarm is issued when there

is a changeover or controlled rerouting.




1 plug-in unit type


3 logical number of signalling terminal

Instructions

Check the amount of traffic on the channel concerned with the

MML commands of statistics handling. You can obtain the amount

of traffic on the channel, either for the last half hour or

cumulatively, with the MML command OLU. If traffic is low,

the plug-in unit might be faulty.

Perform a changeover for the target unit of the alarm with the

MML command USC. Change into testing state the unit where the

plug-in unit that is suspected faulty is located. Run diagnostics

for the unit to find out whether the plug-in unit is faulty, see

instructions on Diagnostics and Testing.

Replace the plug-in unit, if diagnostics detects that it is faulty.

See Instructions for Replacing Plug-in Units.

Check also with the MML command AHP whether the alarm 2224,

ERROR IN MSU HANDLING, has been issued. If it is, act according to its

instructions.

Cancelling

No cancelling.

2.101 1142 FAMILY MEMORY USAGE SUPERVISIONLIMIT EXCEEDED

Meaning

The family indicated in the supplementary information fields of this

alarm has exceeded the supervision limit set to its memory use.

During start up, the system allocates memory areas to the family

based on maximum memory use rate in normal functions.

The system also supervises that this limit is not exceeded.

the limit is exceeded, this alarm is set off.

DN70600744Issue 16-0 en


List of alarms

Memory use of process families is supervised because a faulty family

may reserve a lot of memory and thus prevent other

processes from reserving memory. The failure to reserve memory

disturbs the functioning of the processes and the computer.

Depending on the functions of the computer, traffic capacity or

charging may be disturbed.


1 family identifier

2 family's memory use percentage observed by supervision

3 supervision limit percentage

4 memory, in kilo bytes, allocated to the family at the

time of the supervision. If it exceeds 64 MB, the value is FFFF

5 free memory, in kilo bytes, at the time of the supervision.

If it exceeds 64 MB, the value is FFFF

6 memory, in kilo bytes, allocated to the family at the

end of the supervision period. If it exceeds 64 MB, the value

is FFFF

7 free memory, in kilo bytes, at the end of the supervision period.

If it exceeds 64 MB, the value is FFFF

Instructions

1. Check whether the disturbance is caused by an overload situation.

In an overload situation an increased number of reserved hands

and unhandled messages for a certain process family can result

in unexpected memory exhaust.

2. Display the resource status of the process family indicated

in the additional information field of the alarm by using the

MML command DOI. This speeds up the diagnosis and correction

of the fault.

3. If there is no overload, contact the local Nokia Customer Service

Centre to detect a possible fault in software. Displaying

information on memory use and providing these results speeds

up the correction of the fault.



Cancelling

No cancelling.

2.102 1143 AMOUNT OF FREE MEMORY REDUCED

Meaning

The amount of free memory in the computer is below the alarm limit

used in supervision.

If the computer runs out of free memory, memory allocation fails

and may disturb the functioning of the computer.

The size of the largest unified memory area is used as the free

memory amount, as its size is more in accordance with the available

free memory amount than the total free memory amount.


1 size of the biggest free buffer

2 alarm limit used in supervision

3 total free memory amount

4 total memory amount in memory administration

Instructions

The reduction in free memory may result from an error in software

or from a computer whose memory is too small for the software package.

Use the MML command DOI to investigate the computer's memory use for

different purposes.

To find out the nature and cause of the situation, send the information

on memory use to the local Nokia Customer Service Center.

The alarm limit used in supervision can be modified with the MML command

DOM, parameter MEML.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.103 1144 FREE BUFFER HEADERS EXHAUSTING

Meaning

The number of free buffer headers is below the alarm limit used

in supervision. This indicates an increased risk of running out

of free buffer headers. When there are no more free buffer headers

the computer must be restarted.

The fault may be in packaging or software, resulting in an insufficient

overall number of buffer headers or one of the process families

reserving too many headers. It is also possible

that the supervision limit has been set to be unnecessarily high,

in which case an alarm is set too early.


1 number of free buffer headers


3 total number of buffer headers

Instructions

1. Check the current value of the parameter BUFFER HEADER

SUPERVISION LIMIT by using the MMl command DOT. If the value

is unnecessarily high, decrease it by giving the MML command

DOM according to the instructions of the Nokia Customer Service

Centre.

2. If the value of this parameter is 100 or below, contact the

local Nokia Customer Service Centre to detect a possible fault

in packaging or software.



Cancelling

No cancelling.

2.104 1145 FAILURE IN CALCULATING ACCCONGESTION LEVEL

Meaning

The congestion level calculation of the Automatic Congestion

Control function has consecutively failed three times.


1 reason for congestion level calculation failure

01 interrogation of values needed for congestion level

calculation from the unit has failed

02 interrogation of data needed for congestion level

calculation from the ticket office has failed

2 01 interrogation from one unit has failed

02 interrogation from several units has failed

3 type of the unit which failed to respond

4 index of the unit which failed to respond

Instructions

If several disturbances occur in a short time, telling that

the interrogation from one unit has failed, study the alarms

which are on in that unit with the MML command AHO. Clarify

the reason for the failure to respond on the basis of this

information.

If disturbances occur continuously and the congestion level

cannot be calculated and changed, some congestion level may

stay on for a long time. If necessary, the congestion level

calculation can be turned off by stopping the ACC function

with the MML command TLA.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

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


1 family identifier of the process whose message queue is full

2 process identifier of the process whose message queue is full

3 sender computer of the deleted message

4 sender family identifier of the deleted message

5 sender process identifier of the deleted message

6 deleted message number

Instructions

The fault lies in software or packaging, therefore, it is recommended

to inform the local Nokia Customer Service Center in order to detect

the reason for the fault.


Cancelling

No cancelling.



2.106 1148 EXCESSIVE TRAPS

Meaning

The number of traps exceeds the alarm limit during

the supervision interval.

Traps are produced when the program uses an insufficient or faulty memory

or, for example, a faulty addtional plug-in unit.

Traps do not usually disturb the functioning of the program producing

them, but they indicate a disturbance either in the hardware, software or

in the data that the program uses. If the fault is related to hardware,

the system normally gives other alarms as well.

The address formed by CS and EIP is an address where the program

execution was when the trap was detected, that is, the address

describes the program's general execution area rather than a

specific memory addressing execution area.


1 number of traps during supervision interval


3 identifier of the family that caused the latest trap

4 identifier of the process that caused the latest trap

5 register's CS value at the moment of the latest trap detection

6 register's EIP value at the moment of the latest trap detection

Instructions

1. If the system has not given alarms on hardware faults, check the

equipment data with the MML commands of WT command group.

If the equipment data is correct or if you do not succeed in

correcting the fault, contact the nearest Nokia Customer

Service Center.

2. Operating system logs have been written in the OSSUPREP logical file

and studying those can help you in locating the fault.

Check with the MML command ZDOP whether parameter SENDING OF REPORTS

is allowed. If the parameter is not allowed, allow it with the MML

command ZDOM. Connect the OSSUPREP logical file to the I/O terminal

available with the MML command ZIIS.

3. If the fault is a hardware fault, you can temporarily prevent

DN70600744Issue 16-0 en


List of alarms

the alarm from rising repeatidly by modifying the alarm limit

of the object unit with the MML command ZDOM, or,

you can disable the supervision in all the units that are of

the same unit type as the object unit with the MML command ZDOM.

After the fault has been repaired, change the alarm limit back

to normal and re-enable the supervision.

Cancelling

No cancelling.

2.107 1153 ERROR IN DIAL ANALYSIS DATA

Meaning

The register has received a digit analysis result from the

CMREAD program block which makes the continuation of digit

analysis unreasonable.

There has been an attempt to analyse a number for which no

digit analysis has been created; or there has been an attempt

to analyse a number in a wrong analysis tree.


1 analysis field of B-subscriber number

2-13 B-subscriber number

Instructions

Check with the MML command RII that there is a digit analysis

for the B subscriber number in the analysis tree indicated

in the analysis field of the B subscriber number.

If there is no analysis, create it with the MML command RDC.

Cancelling

No cancelling.



2.108 1155 CONNECTION FAILED IN GSW/SWI

Meaning

A connection necessary for the call set-up has not been successfully

established in the GSW switching network of the DX 220 or in the SWI

switching network of the DX 210. The program block requesting the

connection has not been able to communicate with the marker, or the

SWICOP program block has not sent a message informing about the failure

of the connection.


1 01 INREGI: incoming MFC service request rejected

02 OUREGI: outgoing MFC service request rejected

03 OUREGI: hunting for outgoing circuit has failed

04 INREGI: no audible tone

05 INREGI: audible tone not cleared

06 INREGI: speech path not connected

07 OUREGI: speech path not connected

08 INREGI: no connection to SWICOP

09 OUREGI: no connection to SWICOP

0A INREGI: time limit for clearing of through-connection exceeded

0B OUREGI: time limit for clearing of through-connection exceeded

2 call handling register instance

3 PCM of incoming or outgoing circuit

4 time slot of incoming or outgoing circuit

5 circuit group of incoming or outgoing circuit

6 index for incoming or outgoing signalling of register

7 marker unit used by register

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.109 1162 FILE SYSTEM COMMUNICATION ERROR

Meaning

The file system program block is not responding to a message within

the allowed time limit or its answer is erroneous. If the program

block has not answered the message within the allowed time limit,

there may be discrepancies between files in the units.


1 location unit type of the partner program block

2 location unit index of the partner program block

3 family identifier of the partner program block

4 number of the message sent to the partner program block

5 number of the file in connection to which the error was detected.

If the value is FFFFFFFF, the file number cannot be identified

6 error code returned by the partner program block.

You can check its meaning in the General Error Messages of System.

Instructions

Use the MML command AHO to check whether there are other active alarms

concerning the file system. Check also possible logs connected to

the file system in the unit identified by the first and second

supplementary fields with the S command of the service terminal

extension LOGUTI. Locate and correct the fault with the help of the

logs and the error code given in the final supplementary field of this

alarm.

Cancelling

No cancelling.



2.110 1164 TIME NOT RECEIVED FROM SATELLITE

Meaning

Time cannot be received from the satellite receiver in order to check

the correctness of network element time. This does not mean that

network element time would be incorrect. If time cannot be received

within an hour despite repeated attempts, a more serious alarm

2443 RECEIVING TIME FROM SATELLITE FAILS will be issued.


1 information about the reason for the alarm

11 I/O system does not respond to the request for satellite time

12 I/O system does not receive time from the satellite receiver

13 check sum of the satellite time is incorrect

14 satellite receiver does not receive time from the satellite

15 time or date received from the satellite receiver is not

sensible

Instructions

This alarm may be caused by a temporary disturbance (for example,

a climatic radio disturbance) and thus the alarm requires no actions.

When the supplementary information value is between 12 to 15, the user

may perform the checks mentioned in the instructions of the alarm 2443

while this alarm is active, so that the possible fault may be corrected

sooner.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.111 1165 BUFFER ALLOCATION FAILED

Meaning

A process failed to reserve a buffer because the buffer size

requested by the process is larger than the largest free

buffer.

Buffer reservation failure may prevent the execution of a

task or make it slower.


1 family identifier of the process whose buffer reservation

failed

2 process identifier of the process whose buffer

reservation failed

3 requested buffer size

4 largest free buffer

5 total amount of free memory

Instructions

The fault may be in software or in a computer unit whose

memory is too small for the software and functions required

of it. A software fault is probable, if the requested buffer

size indicated in the supplementary information field is

large in comparison with the computer memory.

If the total amount of free memory indicated in the

supplementary information field seems adequate but also the

largest free buffer (indicated in the supplementary

information field) is small, the memory is fragmented. Even a

hot restart of a computer would cause the rearranging of free

and reserved buffers, so that the largest free buffer would

probably become larger.

If a buffer reservation fails in connection with a critical

task, the maintenance system restarts the computer, and

usually the memory state also returns to normal.

If the total amount of free memory is small, the computer

probably has an insufficient memory capacity and should be

replaced with one that has more capacity.



In any case, it is recommended to inform the local Nokia

Customer Service Center on the fault. Include information on

the memory, i.e. on the division of free memory and the

process families that have reserved memory the most.

Cancelling

No cancelling.

2.112 1166 FAILURE IN ACCESSING NPDB

Meaning

*************************

While the MSC (AI1PRB) tries to interrogate the Number Portability

Database for routing information on a portable number, one of the

following errors occurs:

a. The guard timer expired before a response was received for the

interrogation.

b. The information in the interrogation response is invalid.

c. The response to the interrogation is not the expected one.

Any of the above errors will cause the call to be routed by default

routing.


1 cause of the alarm

Values:

0x01 = Guard timer for NPDB interrogation expired

0x02 = NPDB responded with incorrectly formatted data

(LRN with format other than NPA-NXX-XXXX)

0x03 = NPDB responded with an unexpected result. The result

is not equal to the expected response.

2 incorrectly formatted data, if the value of the field 1 = 0x02.

Values: digits received from NPDB with BCD format

DN70600744Issue 16-0 en


List of alarms

Instructions

When the system issues this alarm, check the NPDB to make sure that a

valid reponse is sent back to the MSC.

Cancelling

No cancelling.

2.113 1167 ERROR IN CAS REGISTER SIGNALLING

Meaning

An error has occured in the register signalling of channel-associated

signalling.


1 external PCM circuit of the connection

2 speech timeslot of the connection's external and internal PCM

circuits

3 type of the alarm:

01 = Received MF signal is against the protocol

02 = Received MF signal has unexpectedly changed into another

MF signal

03 = Received MF signal does not end (R2)

04 = Received MF signal has ended unexpectedly

05 = Received MF signal is too long (R1)

06 = Received MF signal is too short (R1)

07 = Reception time for the MF signal has been exceeded

08 = Time supervision of the signalling's forced control period

has been exceeded (Rus. R1)

09 = the total signalling time of MF signalling has been exceeded

(R1)

4-7 type of the alarm:

01: call direction byte

reception group byte

raw signal byte

sdl state byte



02:call direction byte


raw signal byte

sdl state byte



time supervision

duration (s) byte

sdl state byte



** spare ** byte

sdl state byte



time supervision

duration (s) byte

sdl state byte



time supervision

duration (s) byte

sdl state byte



time supervision

duration (s) byte

sdl state byte



time supervision

duration (s) byte

sdl state byte



time supervision

duration (s) byte

sdl state byte

8-15 the last eight register signals

Instructions

Monitor the PCM circuit more closely in order to find other errors which

may have occurred. Does e.g. the ET unit or the CASU unit issue other

alarms? If the fault situation occurs either repeatedly or also in other

timeslots, contact the maintenance staff of the partner exchange

DN70600744Issue 16-0 en


List of alarms

immediately in order to correct the fault.

You can conclude the scope and concentration of the error situation by

examining PCM and timeslot data concerning the alarms. Determining the

scope of the error situation helps you to locate the faulty device.

Possible reasons for the alarm:

1. If also the alarms 2624 and/or 2625 are issued from the CASU unit,

the MFST device has become faulty. Read the instructions given in

these alarm descriptions.

(Alarm types: 1-9)

2. The MSC and the partner exchange use different signallings. Check

that the signalling used in the MSC and the partner exchange has been

defined correctly.

(Alarm types: 1,3,7)

3. The signalling time supervisions of the MSC and the response time of

the partner exchange are incompatible.

(Alarm types: 3,4,5,6,7,8,9)

4. There are disturbances on the PCM circuit between the MSC and the

partner exchange.

(Alarm types: 1-9)

5. There is an overload situation in the MSC or in the partner exchange.

(Alarm types: 1-9)

6. The partner exchange is defective/incompatible.

(Alarm types: 1-9)

Cancelling

No cancelling.

2.114 1168 DEFAULT ROUTING CALL

Meaning

The MSC has queried the Number Portability Database (NPDB)

to obtain routing information on the portable directory number

but has not received a valid response. The call will be default

routed if reanalysis has been defined for the cause code indicated

by the alarm, and if reanalysis is allowed by the call control.




1 cause code that is analysed in the EOS analysis and EOS

attribute analysis

2-6 directory number that was sent to the NPDB

Instructions

When the system gives this alarm, check the NPDB to ensure that

a valid response is sent to the MSC.

Cancelling

No cancelling.

2.115 1169 FREEZING PERIOD OF SS7 REPORTINGLOST

Meaning

Some of the counters or logs of the SS7 statistics are not reported,

because the counters or log events in question are lost from the

files.

If the alarm concerns counter reporting, the following two 30-minute

freezing periods have passed during the report outputting, and thus

the counters of the first reporting period are lost. The counters of

the freezing period in question will not be included to the following

reporting period.

If the alarm concerns reporting of interval logs,

the 5-minute freezing period has finished before the log events of the

previous 5-minute period are reported. In this case, the log events in

question are not reported, but they are available with MML commands.


1 type of counters or logs lost:

01 MTP counters

02 SCCP/TC counters

DN70600744Issue 16-0 en


List of alarms

03 MTP interval logs

04 SCCP/TC interval logs

2 file number of the counter or log file whose counters or logs

were not reported. If the file number is not available, the

value of the field is FFFFFFFF

Instructions

Check that the operation and maintenance computer (OMU) is in working

state WO-EX with the MML command USI.

Check that the connections of the logical files of the SS7 reporting

are in order with the MML command IID, that is, that the logical files

are connected onwards to another logical file (for example binary

reports' files to MEAFIL file) or to a functioning I/O device

(for more information, see instructions on I/O System).

If the binary reports' logical files are connected to MEAFIL file,

also check that MEAFIL is connected to a virtual data storage (VDS).

The reason for the alarm may also be the overload of reporting, in

which case, reports are not outputted fast enough. In this case,

decrease the report load by removing unnecessary signalling channels,

signalling points and/or SCCP subsystems from the statistics with

the MML commands OSL, OSN OSE, and possibly unnecesary reporting

types with the MML commands OSM and OSG.


======================================================

ascii bin

MTP counters:

MTPSLAVAIA MTPSLAVAIB SIGNALLING LINK AVAILABILITY

MTPSLPERFA MTPSLPERFB SIGNALLING LINK PERFORMANCE

MTPSLUTILA MTPSLUTILB SIGNALLING LINK UTILIZATION

MTPSPSTATA MTPSPSTATB SIGNALLING POINT STATUS

MTPSLSAVAA MTPSLSAVAB SIGNALLING LINK SET AND ROUTE SET AVAILABILITY

MTPOCTHSPA MTPOCTHSPB SIF AND SIO OCTETS HANDLED WITH

SIGNALLING POINT

MTPOCTSIOA MTPOCTSIOB SIF AND SIO OCTETS HANDLED WITH SIO

MTPOCTMATA MTPOCTMATB SIF AND SIO OCTETS HANDLED WITH OPC, DPC

AND SIO

SCCP/TC counters:

SCCPSPA SCCPSPB SCCP SIGNALLING POINT METERS

SCCPSSA SCCPSSB SCCP SUBSYSTEM METERS

SCCPLSSAVA SCCPLSSAVB SCCP LOCAL SUBSYSTEM AVAILABILITY

SCCPSINGLA SCCPSINGLB SCCP SINGLE METERS

TCAPPUA TCAPPUB TCAP PERFORMANCE AND UTILIZATION

TCAPTRANSA TCAPTRANSB TC TRANSACTION METERS

MTP interval logs:

MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORT



MTPSPLOGA SIGNALLING POINT INTERVAL LOG REPORT

SCCP interval logs:

SCCPSPLOGA SCCP SIGNALLING POINT INTERVAL LOG REPORT

SCCPSGLOGA SCCP SEGMENTATION AND REASSEMBLY ERRORS

INTERVAL LOG REPORT

TCLOGA TC INTERVAL LOG REPORT

SCCPGTLOGA SCCP GT TRANSLATION ERRORS LOG REPORT

Cancelling

No cancelling.

2.116 1170 NOT ENOUGH DIGITS IN CALLED NUMBERFOR EXTENDED PREANALYSIS

Meaning

There are not enough digits in the called subscriber number for

the execution of the extended preanalysis. If the called subscriber

number is shorter than the number which the user has defined in the

subanalysis in question, the call will be cleared.


1 in text format, the name of the subanalysis in which

the user has defined more digits than what can be analysed

when searching for the attribute that corresponds to the

number of the subscriber

2 of the two sides of the subanalysis, the one whose execution

caused the alarm



3 type of number

4-9 the first 12 digits of the called subscriber number

DN70600744Issue 16-0 en


List of alarms

Instructions

Check if the extended preanalysis subanalysis that was output

in the alarm requires any actions. For more information, see

the feature description of feature 929, Extended Preanalysis.

Cancelling

No cancelling.

2.117 1172 ASS PLUG-IN UNIT RAM FAILURE

Meaning

A fault has been detected in the RAM memory of an ASS plug-in unit.


1 number of the ASS plug-in unit

Instructions





Cancelling

No cancelling.



2.118 1173 SYNCHRONIZATION OF PROCESSESRESTARTED IN COMMUNICATION LINK

Meaning

The ASS data transmission connection has been resynchronized because of

a failure detected by the program block. The alarm is set only once

during a monitoring period. Repeated failures increase the value of the

channel-specific error ratio counter.


1 maintenance type of unit

2 unit index

3 ASS channel of data transmission connection

4 PCM circuit of data transmission connection

5 time slot of data transmission connection

6 failure detected by the ASSPGM program block

01 CRC sum error in received message

02 synchronization of connection lost

03 remote end does no acknowledge the message sent to it

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.119 1174 NO RESPONSE TO ASS SUPERVISIONMESSAGE

Meaning

The ASS program block (ASSPGM) has not responded within the specified

time to the supervision message sent by the USAPRO program block of

the computer controlling the program block.


1 additional information

FF = no additional information

01 = ASS unit has not started

02 = ASS unit has stopped responding to

supervision messages

2 index of the ASS plug-in unit

Instructions





Cancelling

No cancelling.

2.120 1175 INTERNAL SIGNALLING SEND OVERLOAD

Meaning

The outgoing message buffer of the IPSEND program block is full.




1 channel number of the ASS plug-in unit

Instructions





Cancelling

No cancelling.

2.121 1176 INTERNAL SIGNALLING RECEIVEOVERLOAD

Meaning

The incoming message buffer of the IPRECE program block is full.


1 channel number of the ASS plug-in unit

Instructions





DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.122 1177 T1 PCM REMOTE END FRAME LOST

Meaning

The remote end of the PCM circuit issues a disturbance on T1 PCM.

The system cannot use the PCM circuit for calls before the fault

has been corrected.

The error situation has no direct effect on charging or announcements.




3 internal alarm setting position

Instructions

Check the condition of the PCM transmission system.

Cancelling

Do not cancel the alarm.



2.123 1178 PREPROCESSOR UNIT DISTURBANCE

Meaning

Functioning of a program block in a preprocessor is not normal.

Either start-up of the program block has failed or the program

block does not send an answer to the supervision message.


1 type of the preprocessor plug-in unit

2 index of the preprocessor plug-in unit

3 general error message of the system telling the reason for the

alarm. You can check its meaning in the General Error Messages

of System.

4 family identifier of the program block that the alarm concerns

Instructions

The alarm requires no immediate actions. However, if the alarm occurs

repeatedly, fill in a Problem Report and send it to your local Nokia

Customer Service Center.

Cancelling

No cancelling.

2.124 1182 PREPROCESSOR UNIT RESTARTED

Meaning

A preprocessor has restarted spontaneously. If the preprocessor is

equipped into a unit which working state is WO-EX, the restart causes

disturbance to the function of the unit.

DN70600744Issue 16-0 en


List of alarms


1 type of the restarted preprocessor plug-in unit

2 index of the restarted preprocessor plug-in unit

Instructions

The alarm requires no actions. It supports the activation of the

automatic recovery for the object unit. You can check the supporting


Cancelling

No cancelling.

2.125 1190 EXCESSIVE ERRORS IN SCP

Meaning

Statistics measure the ratio between failed transactions and all

transactions between the SCP and the SSP. The measurement is performed

on the global titles of the SCP with the MML command TDC.

If the ratio between failed transactions and the total number of

transactions exceeds a given limit at the end of a period, and the

total number of transactions does not exceed a given limit, then this

disturbance for the global title defined is printed.

This function has, in the class 9 of the parameter file, the parameters

observation period (15), error ratio alarm limit (14), and limit for

the total number of transactions (13).


1-8 SCP global title:

there are two digits in each byte. If there is an odd

number of digits, the meaningless digit is FH and the

rest FFH (e.g. the global title 123 is printed

12 3F FF FF FF FF FF FF).

9 the number of all transactions in SCP



during the observation period

10 the value of the error ratio that caused the alarm

Instructions


Cancelling

No cancelling.

2.126 1191 POSITION ESTIMATE NOT AVAILABLE FOREMERGENCY CALL

Meaning

The obtaining or delivering of the position estimate of a mobile station

(MS) has failed. When a MS makes an emergency call, the call will be

setup to an appropriate Public Safety Answering Point (PSAP), and the

position estimate of the MS will be sent to the PSAP. The position

estimate is the estimate of the geographical location of the MS.

The estimate is obtained from the LCF (Location Control Function).

The alarm is set when the positioning has completely failed or the

POST timer expires. In both cases the position estimate is not delivered

to the PSAP.


1 location area code

2 cell identity

3-11 location number digits (Maximum 18 numbers)

Unsignificant number have value 0.

12 position signalling

1 = Non-Call Associated Signalling in use

2 = Call Associated Signalling in use

3 = Non-Call Associated Signalling and

Call Associated Signalling in use

DN70600744Issue 16-0 en


List of alarms

13 additonal information

0 = positioning has completely failed

1 = POST timer has expired

Instructions

The PRFILE parameter ES_LCS_QOS_ACC defines the accuracy required

for position measurement. If the accuracy is set too high, the position

measurement within the range of the accuracy may not be obtainable.

In case of timer expiration, the post_timer value in CDAFIL may

be set too small. The timer value is set through the MML command (EPC).

The value is given in the units of 10 ms. If the value of the timer is

too small, the timer may expire, and if the value is too high, it may

hold up too long.

Cancelling

No cancelling.

2.127 1192 SSCOP TRANSMIT BUFFER OVERFLOW

Meaning

The transmit buffer of SAAL, which is maintained by the SSCOP layer,

has filled up. Signalling message units, which are sent to SAAL, are

lost. SAAL is able to handle normally only MTP-3 management messages.

The signalling message transfer of concerned signalling link is

disturbed. This situation may be caused by the congestion in the

signalling data transfer or failure in the SSCOP layer of SAAL.

The alarm may appear in the signalling link changeover situations.


1 the external interface identifier of the signalling link

2 the virtual path identifier of the signalling link

3 the virtual channel identifier of the signalling link

4 number of signalling units in transmit buffer



Instructions


Cancelling

No cancellation.

2.128 1194 DYNAMIC ROUTING SEARCH ERROR

Meaning

Distribution of traffic load cannot be carried out in a

certain order, and thus routing cannot be performed using the

principle of dynamic routing. Alternative routing is taken

into use to find the appropriate route. Traffic is thus

directed through the primary routing alternative, using the

primary subdestination, if possible. If traffic cannot be

directed using the primary subdestination, the system

automatically selects the first alternative subdestination

etc.


1 record number of the DNSFIL file, leading to the

circuit group in question

2 number of the route whose load cannot be determined

3 general error message. Check the meaning of the

message using the service terminal extension command

MRS (see Service Terminal Essentials, Maintenance

Manual) or refer to the document General Error

Messages of System, Supplementary references.

Instructions

If the value shown in field 3 of the additional information

is 43079d, the routing alternative the system tried to use

does nor exist (see field 2 in the additional information to

find out the routing alternative).

DN70600744Issue 16-0 en


List of alarms

Use the MML command RMJ to modify the alternative destination

data.

If another error code is shown in field 3 of the additional

information, fill in a problem report and send it to the

local Nokia Customer Service Center. Include active main

memory and marker logs in the report, as well as analysis

component data. The logs can be output using the service

terminal command ZGD, and the analysis components can be

displayed using the MML command RIL.

Cancelling

No cancelling.

2.129 1195 USSD SERVICE INFORMATION NOT FOUND

Meaning

Default routing information for Unstructured Supplementary

Service Data (USSD) messages is not defined. Default will be

used when there is no analysis for received USSD string.


1 profile identifier. The analysis of the USSD service

information is started with the help of the profile

identifier. The analysis is started from the UAPFIL

and the result is stored in the UARFIL

2-12 mobile subscriber international ISDN number

Instructions

Store default routing (SCP) address to the USSD control files

with MML command CUC (CREATE USSD PROFILE WITH ANALYSIS):

CUC:RES=DEFROUT:GT=<SCP address>,SSN=<subsystem number of USSDC>;



Cancelling

No cancelling

2.130 1197 INCONSISTENCY IN THE SYNCHRONIZATIONOF THE NPDB DATABASES

Meaning

An inconsistency in the synchronization of the Number Portability

Databases (NPDB) has been detected. The alarm is set when the MSC

has received information that the NPDB query for the call

has been performed and the subsequent NPDB query is not allowed

and the routing enquiry for the call has resulted number portability

specific routing information.

The call is released.


1 B subscriber's number (used in SRI).

It contains the length field, indicator field and actual

digits used in the address. The indicator field contains the

address type and the numbering plan. The number of digits

indicates the length of the address

2 PCM line number

3 timeslot

Instructions

Take the appropriate actions to identify NPDB(s) containing inconsistent

routing data associated with the B subscriber's number and to restore

consistency between the NPDBs.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.131 1200 ACTOR HAS FAILED TO REGISTER TO THESUPERVISION

Meaning

An actor has failed to register to the active supervision.

It is possible that the supervision data table has filled up. This

means that the actor supervisor (SVATOR) can not take more actors

under the the active supervision. The problem has no effect on the

actor supervision already activated.

Apart from the active supervision, all actors are supervised

passively, i.e. exceptions made by the actors are always noticed.

If the actor is not supervised actively, the erroneous behaving

(e.g. infinite loops) or the totally stopping of the actor is not

detected and the recovery actions are not activated. However, if

the actor runs without problems the lack of active supervision is

not a serious problem.


1 the DMX family identifier of an actor that has failed

to register to the supervision

Instructions

If the alarm occurs, the supervision data table is full.

Fill in a Failure Report and send it to your local

Nokia Customer Service Center.

List the content of the supervision data table with service terminal

command: supervise -a all and attach it to the Failure Report.

Cancelling

No cancelling.



2.132 1204 WATCHDOG CAUSES UNIT RESTART

Meaning

A critical actor for the functioning of the unit has failed.

This kind of actors are e.g. QXFPRB, which activates the recovery

functions and DAQTOR, which takes care of starting other actors.

Actor Supervisor (SVATOR) stops to feed the watchdog feeder actor

and this will cause a unit restart.


Instructions

The alarm requires no actions because the coming unit restart

solves the problem.

Cancelling

No cancelling.

2.133 1207 UNITS WORKING STATE DATA CORRUPTEDIN THE SYSTEM

Meaning

Working state data in the memory of the supervised unit is different

from the working state data of the supervised unit in the memory of

the supervising unit. The system detects this divergence by itself

and begins the actions in order to correct the problem.

This data divergence can be caused by message transfer errors during

the distribution of the working states to functional units. It may

cause malfunctioning of the system, and it slows down or may even

prevent the automatic recovery actions in the system.

DN70600744Issue 16-0 en


List of alarms


1 working state of the supervised unit in the memory of the system

maintenance unit

2 working state of the supervised unit in the unit's own memory

Instructions

If the disturbance occurs frequently, fill in a Problem Report and

send it to your local Nokia Customer Service Center.

Otherwise, no action is required.

Cancelling

No cancelling.

2.134 1209 ECHO CANCELLER SPARE CHIP FAILURE

Meaning

The system has detected that the spare chip on the echo canceller

daughter board is faulty. This does not affect the traffic going

through the unit.


Instructions


Cancelling

No cancelling.



2.135 1210 PHASE ADVANCE OF TIMING SIGNALCHANGED

Meaning

The phase advance setting of a rack has either been changed

to default value or updated according to the phase advance

measurement result.

If the default phase advance value was taken into use, the

functional units of the rack which are located far enough

from the main clock may have synchronization problems with

the basic timing signals.

If the phase advance value of the rack was updated when some

functional units had synchronization problems, the

synchronization after the updating should work better. This

is the case especially when the difference of the old and

new phase advance value is big enough. If the difference was

only a few measurement units, the updating may have no

effects on the basic timing distribution of functional units

in the rack.


1 reason for phase update made:

00 default phase advance was taken into use because

phase advance setting according to automatic phase

advance measurement is not possible due to

measurement result changing all the time. The reason

of measurement failure is typically the last rack

where the timing bus is terminated. If the CLAB units

of the last rack are without power supply or plug-in

units of CLAB are removed, the automatic phase

advance measurement fails

01 phase advance was updated. The difference between the

phase advance value used and measurement value was

too big and updating was needed. The phase advance is

updated typically after maintenance concerning the

timing signals or when default phase advance was in

use due to automatic phase advance measurement

problems

2 old phase advance value

3 new phase advance value

DN70600744Issue 16-0 en


List of alarms

Instructions


Cancelling

No cancelling.

2.136 1220 HANDLING OF MEASUREMENT DEFINITIONFILE FAILED

Meaning

Handling of measurement definition file has failed. There may be a

temporary overload in the I/O-system. The changes, which have possibly

been made have not been updated to the file. The measurement continues

using the changed parameters, but in a possible restart situation

the system will continue the measurement using the old parameters.

This means that the schedule of the measurement may not be correct.

The third and fourth supplementary information fields show

the reason for the failure.


1 measurement identifier. You can check its meaning by using the MML

command T2C.

2 measurements object list identifier (from 1 to 999). You can check

its meaning by using the MML command T2C.

3 failed task:

01 Writing of measurement definition file failed

02 Passifying of measurement definition file failed

4 specified reason for the error case shown in the third supplementary

information field. This is a general error message of the system.

You can check its meaning with a command of the service terminal

extension MRS (see Service Terminal Essentials, Maintenance Manual)

or from the document the General Error Messages of System,

Supplementary References



Instructions

If the third supplementary information field has the value 01, the

measurement is continued, but the parameters have not been updated to disk.

The wrong parameters are shown when interrogating the measurement

parameters (T2I MML-command). This may be due to a temporary overload

in the I/O-system. Check the I/O-system's active alarms and follow those

alarm instructions. You can try to write on the disk again when the

I/O-system has recovered by modifying the measurement schedule

(T2M MML-command), or the schedule is also updated to the disk every night at

01.00 am, so these updates could correct the problem.

If not, (the disturbance still occurs), contact the local

Nokia Customer Service Center. Send the unit's logs, operating system

logs and active alarms to the Nokia Customer Service Center.

The logs can be output by using the service terminal commands ZGD

and ZSL. The active alarms can be output by using the MML command ZAAP.

If the third supplementary information field has value 02, remove the

measurement definition file (T2D MML-command) which could not be

passified by the system. This may be due to a temporary overload

in the I/O-system. The name of the file is AMEASxxx.yyy,

where xxx refers to the MID value (first supplementary information field)

in the alarm, and yyy refers to the OID (second supplementary information

field) value in the alarm.

Cancelling

No cancelling.

2.137 1221 STATISTICAL MEASUREMENT REPORTOUTPUT FAILED

Meaning

Outputting the statistical measurement report has failed. The report of

the measurement, which has caused the alarm may disappear or, if the

measurement report is output, the data in it may be faulty. The third

and fourth supplementary information fields show the reason for the

failure.

DN70600744Issue 16-0 en


List of alarms


1 measurement identifier of the report. You can check its meaning by

using the MML command T2C.

2 measurements object list identifier (from 1 to 999). You can check

its meaning by using the MML command T2C.

ERROR_CASE:

the reason for outputting of report failed:

01 Buffer allocation failed

02 No data writing service provider

03 Error with data writing service provider

3 specified reason when the third supplementary information field has

value 03. This is a general error message of the system. You can

check its meaning with a command of the service terminal extension

MRS (see Service Terminal Essentials, Maintenance Manual) or from

the document the General Error Messages of System, Supplementary

References.

Instructions

If the third supplementary information field has the value 01, there is an

error situation, which probably cannot be corrected without a software

update. Contact the local Nokia Customer Service Center. Send the unit's

logs, operating system logs and active alarms to the Nokia Customer Service

Center. The logs can be output by using the service terminal commands

ZGD and ZSL. The active alarms can be output by using the MML command ZAAP.

If the third supplementary information field has the value 02, the service

may be temporarily unobtainable. If this is continuous, there is an error

situation which probably cannot be corrected without a software update.

Contact the local Nokia Customer Service Center. Send the unit's logs,

operating system logs and active alarms to Nokia Customer Service Center.

The logs can be output by using the service terminal command ZGD and ZSL.

The active alarms can be output by using the MML command ZAAP.

If the third supplementary information field has the value 03, check that

the I/O device used in the outputting of the report is in working order and

in the correct working state (MML command ISI) and that the logical output

file is connected to the device in question (MML command IID). More

information on the administration of I/O devices can be found in I/O

Configuration Handling, Command Reference Manual.

Cancelling

No cancelling.



2.138 1222 DATA WRITING VIA VDS DEVICE FAILED

Meaning

Data writing via the VDS device has failed. The report of the measurement

that has caused the alarm may disappear. The second and third supplementary

information fields show the reason for the failure.


1 measurement identifier of the report. You can check its meaning by

using the MML command T2C.

2 the reason for data writing to fail:

01 Error in I/O system.

02 No response from I/O system

03 Memory allocation failed

3 specified reason for the error case shown in the second supplementary

information field. This is a general error message of the system.


extension MRS (see Service Terminal Essentials, Maintenance Manual)

or from the document the General Error Messages of System,

Supplementary References.

Instructions

If the second supplemetary information field has the value 01 or 02,

The I/O-system may be overloaded, and thus the report output fails.

The situation may be temporary and the system will correct it.

Check the I/O-system's active alarms and follow those alarm instructions.

If the disturbance occurs constantly, contact the local Nokia Customer

Service Center. Send the unit's logs, operating system logs and active

alarms to Nokia Customer Service Center. The logs can be output by using

the service terminal command ZGD and ZSL. The active alarms can be output

by using the MML command ZAAP.

If the second supplemetary information field has the value 03, there is an

error situation which probably cannot be corrected without a software

update. Contact the local Nokia Customer Service Center. Send the unit's

logs, operating system logs and active alarms to Nokia Customer Service

Center. The logs can be output by using the service terminal command ZGD

and ZSL. The active alarms can be output by using the MML command ZAAP.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.139 1224 MISSING MOLIMITER FOR SMSC LINK

Meaning

During the connection establishment between the MSC and SMSC there is no

MO Limiter value in the SMR-BIND request for the given TCP/IP link.

Additionally the SMS_ENHANCEMENT and the DYN_TCPIP_LOADSHARING PRFILE

parameters are turned on.

The disturbance will be cleared by the operator.


1-16 the address of the TCP/IP link, which hasn't got MO Limiter value

Instructions

The reason of the disturbance is that there is no MO Limiter value for

one or more links of the given IP address. The operator has to check

these link settings in the SMSC and add a value for the link without

MO Limiter. The new MO Limiter value will be visible in the MSC after

SMR-UNBIND and SMR-BIND operations.

Cancelling

The disturbance will be cleared by the operator.

2.140 1228 UNIT SUPERVISION NOT FUNCTIONING

Meaning

Supervision of functional unit(s) is not functioning due to

a technical problem, or supervision is stopped by the user

for some special purpose. If the supervision is stopped by the user,



the system starts it automatically after a while (in less than one hour).

The lack of supervision does not prevent normal operation of the system,

but it slows down or may even prevent the automatic recovery actions of

the unsupervised unit.


1 failure reason:

01 User has stopped the unit supervision

02 Unit supervision has been stopped because of a technical problem

2 functional unit whose supervision has been stopped:

0xFFFF Supervision of all units stopped

phys_address_t Physical address of the unit whose supervision has

been stopped or technical problem prevents the

supervision to this unit.

Instructions

If the supervision has not been stopped by user and if the disturbance

occurs frequently, fill in a Problem Report and send it to your local

Nokia Customer Service Center. Otherwise, no action is required.

Cancelling

No cancelling.

2.141 1233 IP ENTITY IS NOT REACHABLE

Meaning

The signalling unit of the other exchange is unreachable: this alarm is

set when the packet sent to the IP address coming from the DNS query

does not reach the destination.

DN70600744Issue 16-0 en


List of alarms


1-16 the remote IP address which is unreachable.

If the IP addess is IPv4 type then only the first four bytes

contain the IP address, the other bytes are filled with zeros.

Eg. in case of ipv4 172.24.175.139 the alarm looks similar

to the following alarm:

BOREAS_MSCi TGSU-0 SWITCH 2003-01-16 11:52:50.97

DISTUR TGSU-0 1C002-00 ZSSPRB


AC 18 AF 8B 00 00 00 00 00 00 00 00 00 00 00 00

Eg. in case of ipv6 1122:3344:5566:7788:9900:AABB:CCDD:EEFF

the alarm looks similar to the following alarm:




11 22 33 44 55 66 77 88 99 00 AA BB CC DD EE FF

Instructions

Check in the log file the error log to obtain information about the

unreachable FQDN and IP address.

The error log looks simillar to the following log:

CALLER : 058F 0000 00 RETURN ADDRESS: 0940 (G0296).00000219

WRITE TIME: 2003-01-16 11:52:50.97

PARAMETERS: E-08 0938.00000033 00000072 0938.00000004

USER TEXT : DISTUR 1233 IP ENTITY IS NOT REACHABLE is SET!!

USER DATA : remote end which could not be reached:

remote fqdn: boreasip1in.nokia.com

remote ip address: 172.24.175.139

Try to ping with ZQRX -MML manually from originating TGSU to terminating

TGSU.

- If this does not succeed, IP backbone failure is the most likely reason. By

using the same ping process you can manually check the connections from

each switch and router between both ends.

- If the ping is going through and the alarm is still on, take the TGSU logs

from the both end and contact the local Nokia Customer Service Center.



Cancelling

Do not cancel the alarm. The system cancels the alarm automatically when

the fault has been corrected

2.142 1234 UPDATE OF PASSWORD VALIDITY TIMEFAILED

Meaning

The program block of the user management (URMANA) has failed

updating the validity times of the MMI users' passwords.

The validity times of the passwords remain unchanged.


1 reason for failure of the password validity time updating

01 error in writing of the memory file

02 error in writing of the disk file

03 creation of hand failed

Instructions


Cancelling

No cancelling.

2.143 1235 FQDN NOT PRESENT IN IEIFIL

Meaning

This alarm occurs when the network is not configured properly.

The alarm indicates the remote IP address that corresponds to the FQDN

that is missing from the configuration file (IEIFIL).

DN70600744Issue 16-0 en


List of alarms

ZSS and ZSC processes write to the log the

FQDN (Fully Qualified Domain Name) that caused the error together with the

IP address.


1-16 the remote IP address that corresponds to the FQDN that is missing

from the configuration file (IEIFIL).

If the IP addess is IPv4 type then only the first four bytes contain

the IP address, the other bytes are filled with zeros.

Eg. in case of ipv4 172.24.175.139 the alarm looks similar to the

following alarm:




AC 18 AF 8B 00 00 00 00 00 00 00 00 00 00 00 00

Eg. in case of ipv6 1122:3344:5566:7788:9900:AABB:CCDD:EEFF

the alarm looks similar to the following alarm:




11 22 33 44 55 66 77 88 99 00 AA BB CC DD EE FF

Instructions

Actions to be taken:

Check the error log to see which FQDN is missing from the IEIFIL.

The error log looks simillar to the following log:

CALLER : 058F 0000 00 RETURN ADDRESS: 0940 (G0296).00000219

WRITE TIME: 2003-01-16 12:14:50.28

PARAMETERS: E-08 0938.00000033 0000006B 0938.00000004

USER TEXT : DISTUR 1235 FQDN NOT PRESENT IN IEIFIL is set!!

USER DATA : this FQDN is missing from ieifil: boreasip1out.nokia.com

its corresponding ip address: 172.24.175.139

There can be two situation which generates this alarm:

-The DNS is misconfigured: the FQDN of the originating side is

obtained incorrectly during reverse DNS query, so this incorrect FQDN

is not found on the terminating side in the IEIFIL configuration file

(more details in IP Trunk O&M Manual).

-The IEIFIL configuration file is misconfigured: the FQDN is missing



from the IEIFIL.

The incorrectly configured circuit group can be

modified with the RCN command. (More details in IP Trunk O&M Manual).

Cancelling



2.144 1236 AN SI7 FAILURE OCCURED

Meaning

This alarm is set when SI7 does not respond in a given time.


1 the computer id from the PID structure of the ZSSPRB slave

that finds the failure caused by SI7

2 the family id from the PID structure of the ZSSPRB slave that

finds the failure caused by SI7

3 the process id from the PID structure of the ZSSPRB slave that


4 the focus from the PID structure of the ZSSPRB slave that


Instructions

Contact the local Nokia Customer Service Center

Cancelling



DN70600744Issue 16-0 en


List of alarms

2.145 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, the operation provided by DSP in question

is not available, or the operation is unreliable.


1 cause of the alarm:

01 no answer from DSP to a supervision inquiry message

Instructions

The alarm supports the activation of the automatic recovery for the

object unit. You can check the supporting amount of the alarm with

the MML command ARO.

Cancelling

No cancelling.

2.146 1240 SCCP DISTURBANCE

Meaning

Report on SCCP disturbances.


1 identifier of disturbance. Possible values are:

01 releasing connection failed, as no acknowledgement has been

received

02 abnormal release of connection, the time supervision of the

passive receiving time (IAR) has expired



03 abnormal release of connection, erroneous IT message

04 abnormal release of connection, time supervision of the hand

has expired

05 establishing connection failed, the time supervision of the

connection establishment (CONN_EST) has expired

06 establishing connection failed, as the local subsystem has

not responded to the connection request

07 subsystem does not respond to local sending

08 local subsystem has no counterpart

09 sending a signalling message to the subsystem fails, as the

subsystem has not enrolled for the service

0A sending message to user has failed

0B sending message to MTP has failed

0C SCCP management could not locate the signalling unit being

distributed

0D sending signalling message to a subsystem fails, as the

standard of the TCAP message is different from the TCAP

version used by the subsystem

0E message is rejected because its priority is lower than the

overload level of the MTP

2 network indicator. Possible values are:




0C national network 1

3 local signalling point code. The signalling point code is

interpreted, depending on the value of the first supplementary

information field, in the following manner:

01-06 own signalling point where the error was detected

07-08 own signalling point to whose subsystem the local sending

was attempted

09-0E own signalling point

4 local subsystem number. If the local subsystem is not known,

the value in the field is FF. The subsystem number is



01-06 local subsystem, releasing or establishing connection

to which failed

07-08 local subsystem to which local sending was attempted

(important subsystem)

09-0A local subsystem to which local sending was attempted

0B local subsystem from which the message was received

0C SCCP management subsystem

0D local subsystem to which sending a TCAP message was

attempted

0E local subsystem from which a message was received

5 remote signalling point code. The signalling point code is



DN70600744Issue 16-0 en


List of alarms

01-06 signalling point of the remote end signalling connection part

07-08 object signalling point of local sending, whose data is being

distributed

09-0A signalling point from which the message came

0B local subsystem to which sending a message was attempted

0C local subsystem to which sending an SCCP management message

was attempted

0D signalling point from which a TCAP message was received

0E signalling point to which sending a TCAP message was

attempted

6 remote subsystem number. If the subsystem number is not known,

the value in the field is FF. The subsystem number is



01-06 remote end subsystem of the signalling connection

07-08 object subsystem of local sending, whose data is being

distributed

09-0A subsystem which send the message

0B remote end subsystem, sending the message to which was

attempted

0C SCCP management subsystem, sending the SCCP management

message to which was attempted

0D subsystem which has send a TCAP message

0E remote end subsystem to which sending a message was

attempted

7 reference number in the DX log. The log contains more

information on the error. If the reference number is not

used in the log, the value of the field is 0.

Instructions

If the alarm is given infrequently and the value of the error code

given in the first supplementary information field is 1-6, no

actions are required from the user.

Otherwise fill in a Problem report and send it to your local Nokia

Customer Service Center. Enclose the printouts output with the

service terminal commands ZSCFE, ZGSC and ZSL in the Problem report.

Cancelling

No cancelling.



2.147 1241 SCCP GLOBAL TITLE TRANSLATIONANALYSIS FILE ERROR

Meaning

Report on the analysis disturbances of the SCCP global title

translation. The global title analysis was not completed because

the analysed number was not found in the analysis data. The alarm

may have some effect on the traffic capacity of the system.

A message that contains the global title in question will not get

to its destination.


1 error code. Possible values are:

01 unknown nature of address indicator. There is no analysis

for this nature of address indicator in the GANFIL

02 unknown numbering plan. There is no analysis for this

numbering plan in the GANFIL

03 unknown translation type. There is no analysis for this

translation type in the GANFIL

04 unknown encoding scheme. There is no analysis for this

encoding scheme in the GANFIL

05 unknown global title indicator. There is no analysis for

this global title indicator in the GANFIL

06 unknown global title standard. There is no analysis for

this global title indicator in the GANFIL

11 GANFIL contains no analysis for the first digit of

the address

12 GANFIL contains no analysis for the second digit of

the address

13 GANFIL contains no analysis for the third digit of

the address

14 GANFIL contains no analysis for the fourth digit of

the address

15 GANFIL contains no analysis for the fifth digit of

the address

16 GANFIL contains no analysis for the sixth digit of

the address

DN70600744Issue 16-0 en


List of alarms

17 GANFIL contains no analysis for the seventh digit of

the address

18 GANFIL contains no analysis for the eighth digit of

the address

19 GANFIL contains no analysis for the ninth digit of

the address

1A GANFIL contains no analysis for the tenth digit of

the address

1B GANFIL contains no analysis for the 11th digit of

the address

1C GANFIL contains no analysis for the 12th digit of

the address

1D GANFIL contains no analysis for the 13th digit of

the address

1E GANFIL contains no analysis for the 14th digit of

the address

1F GANFIL contains no analysis for the 15th digit of

the address

20 GANFIL contains no analysis for the 16th digit of

the address


the address


the address


the address


the address

25 GANFIL contains no analysis for the 21st digit of

the address

26 GANFIL contains no analysis for the 22nd digit of

the address

27 GANFIL contains no analysis for the 23rd digit of

the address


the address

2 record number of the GANFIL



3 global title standard, possible values are:

01 ITU-T

02 ANSI

4 global title indicator in the global title of an SCCP message.

The global title indicator is interpreted in following manner

when the value in the third supplementary field is 01 (ITU-T):

01 global title contains only the nature of address indicator

02 global title contains only the translation type

03 global title contains the translation type, the numbering

plan and the encoding scheme


plan, the encoding scheme and the nature of address

indicator

05-15 global title does not contain the translation type,

the numbering plan, the encoding scheme or the nature

of address indicator.

These global title indicator values have not been

defined in the ITU-T recommendations


when the value in the third supplementary field is 02 (ANSI):








defined in the ANSI recommendations

5 translation type from the global title of the SCCP message.

The translation type is interpreted in the following manner


00 translation type not in use

FF global title does not include translation type

In the national specification ANSI T1.112-1992 there are

values defined for the translation type with the third

supplementary field value 02 (ANSI) and with the fourth

supplementary field value 02. These values of the translation

type can be analysed in the normal way, but they do not cause

special procedures in the system

6 numbering plan and encoding scheme from the global title

of the SCCP message. The encoding scheme is encoded with the

least meaningful bits 1-4 in the following manner:

0000 unknown

0001 BCD, odd number of digits

0010 BCD, even number of digits

DN70600744Issue 16-0 en


List of alarms

0011 reserved for future use

:


1111 encoding scheme not included in global title

The numbering plan is encoded with the most meaningful bits

5-8 in the following manner:

0000 unknown

0001 ISDN/telephone network numbering plan (E.164,E.163)


0011 data network numbering plan (X.121)

0100 telex network numbering plan (F.69)

0101 ship telephone network numbering plan (E.210,E.211)

0110 mobile telephone network numbering plan (E.212)

0111 ISDN/mobile telephone network numbering plan (E.214)


:


1111 numbering plan not included in global title

7 nature of address indicator from the global title of the SCCP

message. Possible values are:

01 subscriber number

02 reserved for national use

03 national meaningful number

04 international number


:

FE reserved for future use

FF nature of address indicator not included in global title

8-15 address information from the global title of the SCCP message

so that, for example, the number 12345 is encoded

12 34 5F FF ...

Instructions

1. Check whether there should be a global title analysis created for

the global title indicated in the disturbance. You can check the

existing analyses with the NBI command of the Global Title

Analysis Handling MML (GTAHAN). Note that in the MML command

the given root parameters must be the same as in the alarm.

2. If there is no analysis, you can create it with the MML command

NBC, if necessary. Before creating the analysis, find out the

correct analysis result to which the new analysis will be

connected. You can check the analysis result records with the

MML command NAI. If a suitable result record is not found, you

can create it with the MML command NAC.

3. If the analysis has already been created, the error may be

a file error. It may be possible to correct the error by loading



the GANFIL file from disk with the MML command DFM in the unit

that set the alarm.

4. As in the short message service the subscriber gives the title,

a wrong title can cause the alarm in question. If there is a

disturbingly high number of alarms in a situation like this,

this alarm can be blocked with the MML command ABB. Note that

if the alarm is blocked, it will not be set in the genuine

fault situation either.

5. If these actions do not help, fill in a Problem report and


Cancelling

No cancelling.

2.148 1242 SCCP GLOBALTITLE TRANSLATION RESULTFILE ERROR

Meaning

Report on the output disturbances of the SCCP global title

translation. The results output record of the global title translation

contains incorrect information or global title modification cannot be

done to the existing global title number. The alarm may have an effect

to the traffic capacity of the system. A message that contains the

global title in question will not get to its destination.


1 error code. Possible values are:

01 record number formed as a result of global title

translation causes a file access error when trying to

form an address to the Global Title Translation Result

File (GTRFIL)

02 translation of global title contains an unknown

destination point code

03 translation of global title contains an unknown

subsystem number

04 translation of global title contains a reference to a

record of the Global Title Modification File (GTMFIL).

DN70600744Issue 16-0 en


List of alarms

When modifying the global title using the values of this

record, the result is an erroneous global title (e.g. too

many digits are added or removed)

2 record number of GTRFIL

3 global title standard, possible values are:

01 ITU-T

02 ANSI

4 global title indicator in the global title of an SCCP message.



01 global title contains only the nature of address indicator





plan, the encoding scheme and the nature of address

indicator





defined in the ITU-T recommendations


when the value in the third supplementary field is 02 (ANSI):






of the address indicator.


defined in the ANSI recommendations

5 translation type from the global title of the SCCP message.

The translation type is interpreted in the following manner




In the national specification ANSI T1.112-1992 there are

values defined for the translation type with the third

supplementary field value 02 (ANSI) and with the fourth

supplementary field value 02. These values of the translation

type can be analysed in the normal way, but they do not cause

special procedures in the system

6 numbering plan and encoding scheme from the global title

of the SCCP message. The encoding scheme is encoded with the



least meaningful bits 1-4 in the following manner:

0000 unknown

0001 BCD, odd number of digits

0010 BCD, even number of digits


:


1111 encoding scheme not included in global title

The numbering plan is encoded with the most meaningful bits

5-8 in the following manner:

0000 unknown

0001 ISDN/telephone network numbering plan (E.164,E.163)




0101 ship telephone network numbering plan (E.210,E.211)


0111 ISDN/mobile telephone network numbering plan (E.214)


:



7 nature of address indicator from the global title of the SCCP

message. Possible values are:






:

FE reserved for future use

FF nature of address indicator not included in global title

8-15 address information from the global title of the SCCP message

so that, for example, the number 12345 is encoded

12 34 5F FF ...

Instructions

1. If the value of the first supplementary field is 01, use the NBI

command of the Global Title Analysis Handling MML (GTAHAN) to

check to which result the analysis in question should lead.

You may be able to correct the error by loading the GANFIL and

GAIFIL files from disk with the MML command DFM to the unit that

set the alarm. If the alarm is set only in one computer unit, a

unit restart or switchover may correct the situation. If loading

the files does not help, remove the analysis in question and the

result with the MML commands NBD and NAD. Then recreate them with

the MML commands NAC and NBC. Note that removing the result may

DN70600744Issue 16-0 en


List of alarms

cause an outage in the traffic.

2. If the value of the first supplementary field is 02,

the disturbance may be caused by a file error. It may be

possible to correct the error by loading the GTRFIL file from

disk with the MML command DFM to the unit that set the alarm.

If loading the file does not correct the situation, find out

to which signalling point the analysis in question should

lead and use the MML command NAM to correct the signalling

point code.

3. If the value of the first supplementary field is 03, the

disturbance may be caused by a file error. It may be possible

to correct the error by loading the GTRFIL file from disk with

the MML command DFM to the unit that set the alarm. If loading

the file does not correct the situation, find out which

subsystem should be in the result and correct it with the MML

command NAM.

4. If the value of the first supplementary field is 04, use the

commands NAI and NAX of the Global Title Result Handling MML

(GREHAN) to check the global title information and, if

necessary, make corrections with the NAM and NAS commands.

Cancelling

No cancelling.

2.149 1243 DECODING ERROR OF THE RANAP-MESSAGE

Meaning

RANAP-message cannot be decoded.


1 message type of the erroneous decoded message,

specification UMTS 25413

2 message length of the erroneous decoded message

3 reason for the alarm

possible numerical values are:



0 unknown

1 mandatory parameter missing

2 corrupted message

Instructions


Cancelling

No cancelling.

2.150 1244 RUNNING OUT OF MESSAGE BUFFERS

Meaning

The amount of free message buffer memory in one message size class in

the computer is below the alarm limit used in supervision. The alarm

limit is usually set so low that the alarm indicates a critical

reduction in the amount of free message buffers.

When there are no free message buffers, reservation of a message fails

and this may disturb the functioning of the computer.

This alarm does not necessarily mean a fault. The alarm can also be

an indication of a temporary shortage of free message buffers caused

by a high processor load.


1 size of message buffers in the message size class which is

running out of message buffers

2 number of messages allocated in the message size class

3 number of free messages in the message size class

DN70600744Issue 16-0 en


List of alarms

Instructions

The reduction in the number of free message buffers may result from a

software fault or from an insufficient number of free message buffers

in the computer as opposed to the software build.

The latter one means a wrong dimensioning of the parameters.

As a precautionary act it is advisable to collect some information in case

the computer goes to a faulty state or gets restarted.

If the situation recurs, it is recommended to inform the local Nokia

Customer Service Center on the message usage data in order to find out

the nature and cause of the situation. In this case, please attach the

printouts of the commands mentioned below.

To get the message buffer usage information start a telnet session for

the computer that is given as the object unit of the alarm, or give

the dmxshow command on the console of the computer.

A remote session to the computer (established with the service terminal

command ZRS or with the MML command ZDDS) should be avoided because it

uses messages and it could even worsen the situation.

1. To get the information on the usage of message buffers, give the

service terminal commands

dmxshow -s

and

dmxshow -m

Command dmxshow -a or dmxshow -A should not be used because it

Heavily consumes the resources of the computer.

2. To display the computer log, give the service terminal command

clog -s -a

3. To display alarm history of the current date concerning the computer,

give the MML command

ZAHP:<unit_type>,<unit_index>;

Cancelling

No cancelling.



2.151 1245 RANAP ERROR INDICATION MESSAGERECEIVED FROM PARTNER MSC

Meaning

An ERROR INDICATION has been received from the partner MSC in inter MSC

handover.


1 specification UMTS 25413

Instructions


Cancelling

No cancelling.

2.152 1249 DATABASE DISK COPY HAS EXCEEDEDMAXIMUM ALLOWED AGE

Meaning

Database dumping has not been successful for a long time due to

a high transaction load and the age of the disk copy has reached

its maximum limit. The dumping is now started with an option to

prevent transactions when overloading occurs. This strategy is

followed until the dumping is completed successfully.


1 database index; this is still required in some database

applications even though the current trend is that the

database is identified by the values entered in the

two following supplementary information fields, i.e.

database name and database occurrence

DN70600744Issue 16-0 en


List of alarms

2 database name

3 number of database occurrence

4 how much late the disk copy is from the state in memory.

The format of the value is hh:mm

Instructions


Cancelling

No cancelling.

2.153 1250 DATA LINK LAYER PROTOCOL MISMATCH

Meaning

The second layer protocol (LAPD) of the D-channel of the primary rate

access has detected protocol errors. The cause may be a malfunction in

the unit or the equipment functioning as the terminal equipment, or a

faulty connection (loop) in the switching network or at some other point

of the PCM connection.


1 number of the channel link set (D-channel)

2 D-channel index within the channel link set:

00 primary channel

01 back-up channel (in primary rate access only, not in use)

3 type of the channel link set:

00 primary rate access channel link set

01 subscriber module (SUB) channel link set

02 exchange terminal (ET) channel link set

03 functional unit channel link set

4 number of the D-channel's PCM



Instructions

The alarm usually appears when the transmitting direction

in the data link connection is connected to the receiving direction

within the network element or outside it.

The network element may also have been configured so that it is

functioning as the incorrect end of the connection from the point of

view of the LAPD protocol. Also, the LAPD protocol itself may

be faulty.

The instantaneous values of the counters that set the alarm can

be examined in real time, see instructions on LAPD statistics.

The incrementing of the counter RECEIPT OF NON-IMPLEMENTED FRAME

indicates a loop or incorrect configuration in the opposing end,

RECEIPT OF UNSOLICITED UA, RECEIPT OF FRAME WITH WRONG SIZE and

N201 ERROR indicate a malfunction in the opposing end.

Cancelling

No cancelling.

2.154 1251 EXCESSIVE RETRANSMISSIONS ON DATALINK CONNECTION

Meaning

The second layer of the primary rate access D-channel does not

receive any answers to the command frames it has sent. The missing

answers may be due to a partial or total inoperation of the remote end,

or breaks in the data link connection.

The alarm usually appears in connection with short-term or permanent

breaks in the data link connection. The alarm may also indicate problems

with protocol in the data link connection layer. In other words, the

remote end does not, in some situations, respond according to the

recommendations.




DN70600744Issue 16-0 en


List of alarms

00 primary channel

01 backup channel (in primary rate access only, not in use)







Instructions

The fault disturbing the D-channel may lie in the hardware of the

network elements, more probably, however, in the data link connection

or the synchronization between the network elements.

The working order of the data link connection can be monitored

with an MML command, see instructions on PCM statistics.

Synchronization may be handled with MML commands, see instructions on

synchronization.

In addition to possible breaks and external disturbances, it is

especially important to check in the data link connection, that

the PCM circuit signals and the protective sheath are connected

correctly in the connection points (ET, distribution frames).

The instantaneous values of the counters UNSUCCESSFUL RETRANSMISSION OF

SABME and RR/RNR/REJ which cause the alarm may be monitored in real

time, see instructions on LAPD statistics.

The RR frame's failure to answer indicates breaks of data link

layer lasting a few seconds, while the SABME frame's failure to answer

indicates a break longer than that.

Cancelling

No cancelling.



2.155 1252 EXCESSIVE ERROR RATE ON DATA LINKCONNECTION

Meaning

There are transmission errors in the data link connection of the

primary rate access D-channel. The errors manifest themselves in check

sum errors of the second layer frames, and/or in overlong

frames due to the disappearance of frame signals.




00 primary channel








Instructions

The fault disturbing the D-channel may lie in the hardware of the

network elements, more probably, however, in the data link connection

or the synchronization between the network elements.

The working order of the data link connection can be monitored

with an MML command, see instructions on PCM Statistics.

Synchronization may be handled with MML commands, see instructions on

Synchronization. In addition to possible breaks and external

disturbances, it is especially important to check in the data link

connection, that the PCM circuit signals and the protective sheath

are connected correctly in the connection points (ET, distribution frames).

The instantaneous values of the counter CRC ERRORS (check sum error)

which causes the alarm may be monitored in real

time, see instructions on LAPD Statistics.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.156 1253 NO RESPONSE FROM PRIMARY RATEACCESS TERMINAL

Meaning

The primary rate access terminal has not answered to the inquiries or

requests sent to it.


1 index of the primary rate access terminal

2 channel link set number

3 D-channel index within the channel link set






5 message that was expected or a message to which response was

expected

6 internal state of D-channel

7 identifier of D-channel time supervision

Instructions

If the situation keeps occurring, check the existence and condition

of the primary rate access terminal.



Cancelling

No cancelling.

2.157 1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT

Meaning

A connection has been re-established on the D-channel, during which

some information may have been lost. The alarm usually occurs in

connection with unit restarts, but it can also occur in data

transmission connections of poor quality.




00 primary channel








Instructions

The alarm requires no actions. If the alarm keeps recurring, check the

quality of the connection, and the condition of the equipment.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.158 1255 PRIMARY RATE ACCESS MESSAGEDISTRIBUTION ERROR

Meaning

The PXRECE has received a message which it cannot distribute to

the receiver.


1 error code

1d erroneous protocol discriminator.


of System

2 number of the primary rate access terminal

3 indicates the protocol discriminator of the

message received

4-9 indicates the next six fields of the message

Instructions

There is an erroneous protocol discriminator in the message received.

The operation of the counterpart must be checked. See also the log

printouts of the PXRECE. The log contains the heading of the erroneous

message.

Cancelling

No cancelling.



2.159 1256 INCORRECT PRD MESSAGE FROM PRIMARYRATE ACCESS TERMINAL

Meaning

An incorrect message has been received from the primary rate access

terminal. This may be due to a fault or disturbance in the terminal

itself, or to the incorrect contents of the message sent by the

remote end.


1 an error has been detected in the message

1d the message is too long

You can check the meaning of other error codes

in General Error Messages of System

2 number of the primary rate access terminal

Instructions


Cancelling

No cancelling.

2.160 1257 FAULTY APM INFORMATION

Meaning

This disturbance is issued if an APP parameter contains faulty

information, like incorrect addressing, or unknown context identifier.

It is also used when application information is too long to be

segmented, or a message contains erroneous segmentation data.

DN70600744Issue 16-0 en


List of alarms


1 error code

01 segmented APM data has been sent, but no acknowledge is

received before ACM,CPG or CON

02 APM received with error notification (reassembly error), or

segmented data is sent, but receiving node indicates

error in reassembly

03 APM received with EH-ASE notification and application is in

the node

04 reassembly or addressing error and ATII has been "release call"

05 EH notification received with ACI = no information

06 EH notification received with unrecognized release reason

07 application information is too long to be segmented ( >2048

bytes)

08 APM terminating node, node could not transit APM data not

belonging to this node

2 service information octet

3 destination point code of the partner exchange

4 identifier of the received APM user in hexadecimal format

00 UCEH-ASE

01 PSS1-ASE (VPN)

03 Charging ASE

04 GAT-ASE

05 BAT-ASE

06 EUCEH-ASE

5 call instance code

Instructions

If disturbances are issued, you can use the commands of the MML command

group AP for changing the filtering time from 20 minutes to one second.

The new shorter filtering time becomes effective only after the

original time (20 minutes) has passed. Short filtering time makes it

possible to monitor different commissioning situations, for example,

to find out if the same disturbance occurs repeatedly, or if there are

other error codes which have the value presented in the 1st

supplementary information.

The original filtering time (20 minutes) reports only the first one of

the periodically repeated disturbances. If all calls cause

disturbances, the alarm system repeats the disturbance whenever the

time between two calls is longer than the filtering time.



When a disturbance occurs, use the specifications of the APM

(ITU-T Q.765).

Cancelling

No cancelling.

2.161 1259 TOO MANY SUBANALYSES IN USER PLANEANALYSIS

Meaning

Analysis chain (in normal side) includes so many subanalyses that

it may weaken the capacity of the switch. The limit for the number

of subanalyses to be executed in one chain is defined with PRFILE

parameter.

This disturbance occurs if the number of executed subanalyses

exceeds the value of corresponding PRFILE parameter value.


1 the phase of User Plane Analysis, which contains too many

subanalyses

0 Not in use

1 Preceding UPD determination phase

2 Succeeding BNC Characteristics determination phase

3 CMN determination phase

4 Succeeding UPD determination phase

5 Succeeding Action Indicator determination phase

6 Inter-Connecting BNC Characteristics determination phase

2 the name in text format of the first subanalysis of the analysis

chain. Consequently this chain contains too many subanalyses

3 this field indicates the execution side of the subanalysis

0 Normal side

1 Test side

DN70600744Issue 16-0 en


List of alarms

Instructions

Find out if the operation in question can be succesfully executed

with a smaller amount of subanalyses. The number of subanalyses to

be executed should be less than the value of the parameter

MAX_UPA_SUBANA_NBR that can be obtained with the MML command WOI.

The value of the parameter shows the maximum amount of subanalyses to

be executed in user plane analysis. This maximum number should not yet

weaken the performance of the exchange too much.

You can check the analysis chain starting from the subanalysis

whose execution caused the disturbance.


Cancelling

No cancelling

2.162 1260 X.25/ETHERNET DATA TERMINALSPONTANEOUS RESTART

Meaning

The AC25-S/AC25-A/AS7-U/AS7-V/AS7-A/COCEN plug-in unit has restarted.

As a result of the restart of the plug-in unit AC25-S/AS7-U, the OSI

administration releases all X.25 connections via that plug-in unit.

The plug-in unit is reinitialized after the connections have been

released.

The restart of the COCEN plug-in unit does not result in the release

of OSI or TCP/IP connections via that plug-in unit, but the level

of service is temporarily decreased.


1 the index of the reinitialized plug-in unit



Instructions

If this alarm is preceded by a notice informing that the

computer unit hosting the plug-in unit has restarted, then

there is no error. When this alarm is received, the possible

effects of the restart on the OSI connections should be checked.

Cancelling

No cancelling.

2.163 1261 OSI CHANNEL GROUP UNREACHABLE

Meaning

The channel group becomes unavailable and this means that remote

applications all of whose labels use unavailable channel groups

become unreachable. The channel group becoming unavailable is caused

by the fact that the group contains no available channels.


1 the name of the channel group that has become unavailable

Instructions

Normally, when a channel group has become unavailable it is because

plug-in units have been restarted, and no error is involved. The

availability of a channel group can be checked, when necessary, by

means of the QGI MML command and its GROUP STATE column. The value

UA means an unavailable channel group, and AV an available one.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.164 1262 OSI SERVICE PROVIDER RESET

Meaning

An OSI program block restart is caused by an internal fault

situation, e.g. when the memory space allocated to the program

block has been exceeded.

The disconnection of the OSI connections maintained by the

program block results in the program block being restarted.

The memory allocation situation of the program block prior

to the restart is written into the log of the unit where the

centralised part of the OSI administration is located.


1 the family identifier indicates which program block

has been restarted. Possible values are 0000 - FFFF

2 the diagnostics field indicates the reason why the

program block is restarted. Possible values are:

01 : memory space request too large

02 : memory space exceeded

03 : erroneous interface table

04 : ASN.1 decoding error

Instructions


Cancelling

No cancelling.

2.165 1263 OSI SERVICE PROVIDER INTERFACE ERROR

Meaning

An OSI program block has received a message that has not been specified

in its interface. The sender of the message is written into the log of

the unit that accomodates the centralized part of the OSI administration.




1 identifies the program block in question. Possible

values are 0000 - FFFF

2 the interface field identifies the interface where

the fault occurred. Possible values are

00 : administration interface

01 : upper interface

02 : lower interface

Instructions


Cancelling

No cancelling.

2.166 1264 OSI INCOMING CALL DENIED

Meaning

A call has been received from the network to a local application with

incoming call denial.


1 the first part (max. 7 digits) of the address of

the calling remote end

2 the remaining part (8 digits) of the address of

the calling remote end

3 number of digits in the address of the calling

remote end. The value is between 0x00 and 0x0F

4 OADFIL file record containing the called

DN70600744Issue 16-0 en


List of alarms

local address

5 plug-in unit from where the call arrived

Instructions

If several disturbance notices are received, check the files

related to the coding of the address fields of the message, at

both ends of the trunk circuit.

Cancelling

No cancelling.

2.167 1266 NO ACKNOWLEDGEMENT TO RESETRESOURCE

Meaning

The Radio Network Controller (RNC) does not answer

the RESET_RESOURCE message. Releasing of resources related to

signalling connection identifiers indicated in RESET_RESOURCE

message may not be released in RNC.


1 mobile country code

001-0999

FFFFH, if unknown

2 mobile network code

001-0999

FFFFH, if unknown

3 RNC identification

1-FFFH

FFFFH, if unknown

4 indicates the repeat count of reset_resource message before

this disturbance is set.



Instructions

Check that the signalling link between MSC and RNC is working.

Check that the RNC network element is working correctly.

Cancelling

No cancelling.

2.168 1267 RNC OUT OF SERVICE IN MSC

Meaning

The state of the radio network controller (RNC)

in the MSC prevents relaying of the traffic.


Fields MCC, MNC, and RNC_ID form global RNC_id.

1 1-999

mobile country code

FFFFH if unknown

2 1-999

mobile network code

FFFFH if unknown


1-FFFH

FFFFH if unknown

4 state of the RNC:

restarting_by_RNC = 0

restarting_by_MSC = 1

subsystem prohibited (if spc used) = 2

rnc_out_of_service = 3

available = A

init (used if RNC changed to locked) = FF

DN70600744Issue 16-0 en


List of alarms

Instructions

The disturbance occurs when a reset message is sent to or received from

the RNC or when the RANAP subsystem of the RNC is not reachable.

Check the functional state of the RNC with the MML command E2I

(if RNC belongs to the operator's network) or E2G (if RNC belongs

to a parallel network). Depending on the result, take the suitable

recovery steps:

State of RNC Action

RESTARTING BY RNC

A reset message has been received, but not yet

acknowledged, from RNC. The state should be

temporary. If RNC remains in this state, change

it manually to LOCKED and then back to

UNLOCKED.

RESTARTING BY MSC

RNC has not acknowledged the reset message

sent by the MSC. Check that the

RNC network element is functioning as defined in

the MSC.

SUBSYSTEM PROHIBITED

The RANAP subsystem of the RNC is not reachable.

Check the functional

state of the SCCP and the MTP

with the MML commands NHI and NEL.

The state of the RANAP subsystem should

be AV and that of the link should

be AV-EX. If necessary, change the state of the

subsystem with the MML command NHC and that of

the link with the MML command NLC.

Cancelling

No cancelling.



2.169 1268 RANAP ERROR INDICATION MESSAGERECEIVED FROM RNC

Meaning

An ERROR INDICATION was received from the RNC indicating that

a faulty message was sent by the MSC server.


Fields MCC, MNC and RNC_ID form global RNC_id.

1 1-999

mobile country code

FFFFH, if unknown

2 1-999

mobile network code

FFFFH, if unknown


1 - FFFH

FFFFH, if unknown

4 RANAP cause code

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.170 1271 THE IU-INTERFACE RANAP-LEVEL TIMEREXPIRY

Meaning

The purpose of this alarm is to notify the user about the RANAP

timer expiry in the MSC Server.


Fields MCC, MNC and RNC_ID form the global RNC_id.

1 1-999

mobile country code

FFFFH, if unknown

2 1-999

mobile network code

FFFFH, if unknown


1 - FFFH

FFFFH, if unknown

4 RANAP cause code

5 index of the expired timer in the BPAFIL file

6 duration of the timer

Instructions

Check the state of the RNC in question and the RNC version (E2I).

Check the value of the timer in question according

to the RNC version (E2J).

Cancelling

No cancelling.



2.171 1273 ASP ACTIVATION FAILED

Meaning

The activation of the ASP (Application Server Process) or

SGP (Signalling Gateway Process) has not succeeded. The alarm is for

ASP if the network element is working as a Signalling Gateway or for

SGP if the network element is working as an Application Server.

The ASP/SGP is activated by the exchange of ASPSM (ASP State

Maintenance), RKM (Routing Key Management) and ASPTM (ASP Traffic

Maintenance) messages between the two M3UA endpoints. So when this alarm

is set by the S3CMAN (SCTP association manager) program block, something

has probably gone wrong during that ASP message exchanging. The 2nd and

3rd supplementary information fields show the ASP message at which the

ASP activation failed. Other reason for the alarm is the insufficient

resources, such as, an insufficient amount of records in work files

which prevents a new ASP to be activated. If none of the ASPs in the

specified association set in the 4th supplementary information field

become active, it means that the whole Application Server or Signalling

Gateway is not available to this network element. Otherwise the signal

transmission capacity may only be somewhat decreased.


1 type of the ASP activation failure. Possible values are:

01 Unsupported M3UA version in M3UA message header

02 M3UA draft version used in message differs from configured

03 The traffic handling mode in M3UA message does not match with the

configured one

04 The routing context value in M3UA message does not match with the

stored one

05 No matching configured routing key was found for the routing

key found in REGREQ message.

06 An unsupported parameter was found inside the routing key

parameter in REGREQ message.

07 Registration status in REGRSP is not 0

08 The local routing key identifier in REGRSP differs from that

one that was sent in REGREQ

09 There is no space for the new ASP in SGWFIL file

0A There is no space for the new ASP in S3WORK file

0B A mandatory parameter is missing in M3UA message

0C A M3UA message is received that is not in accordance with the

role specified in the association set, shown by ZOYI MML command,

such as, the receiving of ASPUP, ASPAC, REGREQ at the ASP even

if only the SG is prepared to receive them.

0D A communication up notification was received at the server side

with unconfigured IP address or the unit from which the

communication up was received is not the configured unit

shown by ZOYI MML command

0E ASPAC (ASP Active) message was received for the ASP in wrong

state, i.e., for ASP the state of which is not inactive.

DN70600744Issue 16-0 en


List of alarms

0F The outbound stream count in the communication up notification

is less than was ordered in the associate primitive

2 message class of M3UA message. Possible values are:

03 ASP State Maintenance (ASPSM) messages

04 ASP Traffic Maintenance (ASPTM) Messages

09 Routing Key Management (RKM) Messages

3 message type of M3UA message. Possible values are dependent

on the preceding supplementary information field:

When the 2nd supplementary information field is 03, the

possible values are:

01 ASP Up (ASPUP)

04 ASP Up Acknowledgement (ASPUP ACK)

When 2nd supplementary information field is 04, the


01 ASP Active (ASPAC)

03 ASP Active Acknowledgement (ASPAC ACK)

When 2nd supplementary information field is 09, the


01 Registration Request (REG REG)

02 Registration Response (REG RSP)

4 association set to which the ASP belongs, 0FFFF if not known

5 when an inconsistent parameter value is included in the M3UA

message, this supplementary information field shows that

inconsistent parameter value. The parameter, which has the

inconsistent value is deduced from the value of the

1st supplementary information field:

01 means m3ua version, 02 means m3ua draft version,

03 means traffic handling mode, 04 means routing context.

Value 0FFFFFFFF means that this field is not applicable for

the alarm.

6 the value of the parameter, with which the preceding information

field is inconsistent. In practice this field shows the

value that is configured and shown also by the ZOYI MML command.

Value 0FFFFFFFF means that this field is not applicable for

the alarm.

7 the parameter tag of the missing parameter. Possible values are:

06 Routing Context

0207 Routing Key

020A Local_Routing Key Identifier

020B Destination Point Code

0200 Network Appearance

0208 Registration Result



0212 Registration Status

0FFFF There is no missing parameter, i.e., the field is not

applicable with the alarm

8 the identifier that unambiguously identifies the ASP, the

value shows the SGWFIL record number.

Instructions

If the value of the 1st supplementary information field is 01:

The peer M3UA is using M3UA RFC version that is newer than supported.

Check whether it is possible to configure the peer M3UA to use

the supported version. The version that the peer M3UA is using is

specified by the 5th supplementary information field. The version

that is supported is specified by the 6th supplementary information

field.


The peer M3UA is using M3UA draft version, which is different than

the one configured at this network element in the association set

specified in the 4th supplementary information field. The

configured M3UA draft version is also specified in the 6th

supplementary information field, possible values are 07 or 09. The

M3UA draft version that the peer M3UA is using is specified in the

5th supplementary information field. The M3UA message, in which the

M3UA draft version was found is specified in the 2nd and 3rd

supplementary fields. If the configured M3UA draft version needs to

be modified in this network element, use ZOYM MML command and give

the association set and the M3UA draft version as the parameters.


The traffic handling mode value that is included in the M3UA message

is different from the one that is configured in the association

set specified in the 4th supplementary information field. The

configured traffic handling mode value is also specified in the

6th supplementary information field. The value of the traffic

handling mode included in the M3UA message is specified by the 5th

supplementary information field. The M3UA message, in which the

traffic handling mode was included is specified in the 2nd and 3rd

supplementary fields. Check which traffic-handling mode is correct

and change the configuration at either this network element or at

the peer M3UA. If the value needs to be modified at

this network element, use the ZOYM MML command and give the

association set and the correct traffic handling mode as the

parameters.


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

DN70600744Issue 16-0 en


List of alarms

key registration, i.e., when handling the REGREQ message. It is also

possible that there is no routing context value stored in this

network element, which means that the routing key registration was

not done. The routing context value stored at this network element

is specified in the 6th supplementary information field. The value

of the routing context included in the M3UA message is specified in

the 5th supplementary information field. The M3UA message, in which

the routing context was included is specified in the 2nd and 3rd

supplementary fields. Try to find out why the peer M3UA does not

use the correct routing context value, or if the routing context

is not stored at this network element (the 6th supplementary

information field is 0FFFFFFFF)and if it is possible to configure

the peer M3UA so that the routing context parameter is not used in

the message. If that peer M3UA is operating in the Nokia network

element, fill in a Problem Report and send it to your local Nokia

Customer Service Center. In the problem report include this alarm

And printouts of following MML commands ("CM,0" in the following

commands refer to active central memory):

1) ZOYI::A;

2) ZDFD:CM,0:A79,,N,;

3) ZDFD:CM,0:AF3,,N,;


No matching configured routing key was found for the routing

key found in REGREQ message. The routing key here refers to the

network appearance and the destination point code (DPC). The network

appearance value included in REGREQ message is specified in the

5th supplementary information field and the DPC included in REGREQ

message is specified in the 6th supplementary information field.

Check that the network appearance value is correct in the association

set where the ASP is about to be added by the routing key

registration procedure. If the value needs to be modified at this

network element, use ZOYM MML command and give the association set

and the correct network appearance value as the parameters. If the

network appearance value is correct, check that the M3UA based link

set is configured to the right signalling point at this network

element. If not you have to delete the signalling link set and route

set and then recreate them so that the signalling point code is

correct.


The peer M3UA is using an unsupported parameter inside the routing

key parameter of REGREQ message. Only network appearance and

destination point code are supported parameters inside a routing key.

The unsupported parameter tag inside the routing key parameter is

specified in the 5th supplementary information field and the

value of that unsupported parameter in the 6th supplementary

information field. Check whether it is possible to configure the

peer M3UA to use only network appearance and DPC as a routing key.

If not do not use routing key registration at both ends if possible,

and at this network element modify the registration_request parameter

to value "NO" in the association set, in which the ASP is about

to be added by the routing key registration procedure as follows:

1) Change the state of the corresponding M3UA based link to



UA-INU, with ZNLC MML command.

2) Change the registration_request parameter giving the

association set and the new value for registration_request

parameter as the parameters in ZOYM MML command.


AV-EX, with ZNLC MML command.

If the routing key registration is turned off, you have to add the

ASPs in the corresponding association set (the role of the

association set is server) by giving the destination IP addresses

of the ASPs.


The peer M3UA does not answer with success status to the routing

key registration request sent by this network element. The status

value that is returned by the peer M3UA is specified by the 5th

supplementary information field.

When the 5th supplementary information field is 03 (invalid

network appearance):

Check that the network appearance value configured in the

association set specified by the 4th supplementary

information field is correct. If the value needs to be

modified at this network element, use ZOYM MML command and

give the association set and the correct network appearance

value as the parameters to the ZOYM MML command.

When the 5th supplementary information field is 02 (invalid

DPC) or 04 (invalid routing key):

Check whether the peer M3UA supports network appearance and

DPC as a routing key. If so check that the network appearance

value configured in the association set specified by the

4th supplementary information field is correct. If the value

needs to be modified at this network element, use ZOYM MML

command and give the association set and the correct network

appearance value as the parameters to the ZOYM MML command.

If the peer M3UA does not currently support network

appearance and DPC as a routing key, check whether it is

possible to configure the peer M3UA as such. If not, do not

use routing key registration at both ends if possible, and

at this network element modify the registration_request

parameter to value "NO", as follows:




association set specified in the 4th supplementary

information field and the new value for

registration_request parameter as the parameters in ZOYM

MML command.



When the 5th supplementary information field is

01 (error-unknown), 05 (permission denied), 06 (cannot support

DN70600744Issue 16-0 en


List of alarms

unique routing), 07 (routing key not currently provisioned),

08 (insufficient resources):

Do not use routing key registration at both ends if possible,

and at this network element modify the registration_request

parameter to value "NO", as follows:






registration_request parameter as the parameters in

ZOYM MML command.



When the 5th supplementary information field is 09 (unsupported

RK parameter field):

Check whether the peer M3UA supports network appearance and

DPC as a routing key. If the peer M3UA does not currently

support network appearance and DPC as a routing key, check

if it is possible to configure the peer M3UA such.

If not, do not use routing key registration at both ends

if possible, and in this network element modify the

registration_request parameter to value "NO", as follows:






registration_request parameter as the parameters in

ZOYM MML command.



When the 5th supplementary information field is 0A (unsupported/

invalid Traffic handling mode):

Check that the value of the traffic handling mode

configured at this network element in the association set

specified by the 4th supplementary information field is

correct. If the value needs to be modified at this network

element, use the ZOYM MML command and give the association

set and the correct traffic handling mode value as the

parameters to the ZOYM MML command.


The local routing key identifier value in the received REGRSP was

not the same as it was in the REGREQ sent by this network element

(REGRSP is a response message to REGREQ message). The local

RK-identifier value that was included in the REGREQ is specified by

the 5th supplementary information field and the local RK-identifier

value that was included in the REGRSP is specified by the 6th

supplementary information field. Try to find out why the peer M3UA



does not answer with the correct local RK-identifier value in the

REGRSP. If the peer M3UA is operating in the Nokia network element,

fill in a Problem Report and send it to your local Nokia Customer

Service Center. In the problem report include this alarm and

printouts of following MML commands ("CM,0" in the following

commands refers to active central memory):

1) ZOYI::A;

2) ZDFD:CM,0:A79,,N,;


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 Customer

Service Center. In the problem report include this alarm and

printouts of following MML commands ("CM,0" in the following

commands refer to active central memory):

1) ZOYI::A;

2) ZDFD:CM,0:A79,,N,;


If the value of the 1st supplementary information field is 0B:

A mandatory parameter is missing in a M3UA message. The parameter

tag of the missing parameter is specified in the 7th supplementary

information field. Try to find out why the peer M3UA does not use

that parameter in the M3UA message specified in the 2nd and 3rd

supplementary information field. If the peer M3UA is operating in

the Nokia network element, fill in the Problem Report from this

network element and send it to your local Nokia Customer Service

Center. In the problem report include this alarm and printouts of

following MML commands ("CM,0" in the following commands refer

to active central memory):

1) ZOYI::A;

2) ZDFD:CM,0:A79,,N,;


If the value of the 1st supplementary information field is 0C:

Check whether the role specified in the 4th supplementary information

field is correct. If not, you have to change the role as follows:



2) Change the role parameter giving the association set specified in

the 4th supplementary information field and the new value for

the role parameter as the parameters in ZOYM MML command.

3) Change the state of the corresponding M3UA based link to AV-EX,

with the ZNLC MML command.

If the value of the 1st supplementary information field is 0D:

The 5th supplementary information field shows the log reference.

The 6th supplementary information field shows the unit, from which

the communication up was received. At the same time as the alarm

two logs are written: first with the same log reference as in the

alarm, second with the IP address that was not configured. In the

second log the first byte shows the IP address version, 0 means IPv4

DN70600744Issue 16-0 en


List of alarms

and 1 means IPv6. Check whether the IP address written to the log

should be configured to some association set, which has the role of

server. If so, add the IP address to the desired association set

with ZOYA MML command.

If the value of the 1st supplementary information field is 0E:

The reason for the alarm may be that the "registration request"

parameter has value YES even if it should have value NO. Change the

value of the parameter to NO, as follows:

1) Change the state of the corresponding M3UA based link to UA-INU,


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.

3) Change the state of the corresponding M3UA based link to AV-EX,


If the value of the 1st supplementary information field is 0F:

SCTP could not establish the association with the configured amount

of outbound streams. The amount of streams is configured in the

association set basis. Use ZOYI::A; command to see the configured

amount of streams that is further specified as the sum of parameters

"first data stream number" and "data stream count". This SCTP user

adjusted to use the lower amount of outbound streams that was

returned in the communication up notification. The amount of SCTP

streams that are returned in the communication up notification are

shown in the 5th supplementary information field. The amount of

configured streams is shown in the 6th supplementary information

field.

Cancelling

No cancelling.

2.172 1274 IU-INTERFACE RESOURCE ALLOCATIONFAILURE

Meaning

Reserving a resource on the Iu-interface fails.




Fields MCC, MNC and RNC_ID form global RNC_id.

1 1-999

mobile country code

FFFFH, if unknown

2 1-999

mobile network code

FFFFH, if unknown


1 - FFFH

FFFFH, if unknown

4 user plane destination identification is the

Iu-resource that is being allocated

5 error code

405 the request message contained erroneous parameters or

was sent in the wrong call phase, that is, the route,

switch type or the circuit type is invalid

406 the connection failed in the switch

603 no answer received from the SWICOP or the RMAPRB

509 radio network file reading error

70E configuration error

872 unknown user plane destination

Instructions

If the alarm is repeated:

Check in MSC if the user plane destination id in question has been

defined correctly for the RNC.

The alarm may also be caused by a temporary congestion (error code

804), in which case you do not need to take any action.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.173 1276 INCONSISTENCY OF THE NPDB DATABASESIN THE SRRI

Meaning

An inconsistency in the synchronization of the Number Portability

Databases (NPDB) is detected. The alarm is set when the SRRi

receives information that the NPDB query for the message

has been performed and the message should be forwarded to other

network, but it is not allowed. The received message is rejected to

avoid looping of messages between PLMNs. If the received message

is a call-related message, the call is released.


1 B subscriber's number.

It contains the number of digits field, the number info field

and actual digits used in the address. The number info field

contains the numbering plan and the nature of address indicator.

The number of digits indicates the length of the address

2 SRR operation code.

The parameter defines the used operation in the SRRi which causes

the loop prevention

3 resulting action.

The parameter defines the resulting action how the loop is

prevented

Instructions

Take the appropriate actions to identify NPDB(s) containing inconsistent

routing data associated with the B subscriber's number and to restore

consistency between the NPDBs.

Cancelling

No cancelling.



2.174 1280 INTERNAL COMMUNICATION CHANNELFAILURE

Meaning

A failure has been detected in the communication between the

preprocessors of the system, or between a preprocessor unit and

its host computer. The failure hampers communication.


1 type of the preprocessor unit generating the alarm or

suspected faulty.

See instructions on Diagnostics and Testing

2 index of the unit generating the alarm or suspected

faulty; if .. the index is not known

3 channel identifier within the unit:

SBCN: FFFF host computer

0000 RSCN (SUB 0)

VXCN: FFFF host computer

0000 RSCN (SUB 0)

RSCN: FFFF host computer

1...7 index of SBCN unit (SUB 1-7)

8 CLxTG-0 (CLSS) or CLET-0 (CLES)

9 CLxTG-1 (CLSS) or CLET-1 (CLES)

CLxTG: FFFF host computer or RSCN

0 CLxTG

CLET: FFFF RSCN

0 CLET

ATMX: FFFF host computer

TRCO: FFFF host computer

1...4 index of ET2x

HWAT 0 HWAT

4 type of the failure:

01 connection establishment failed

02 connection re-establishment

03 message queue overflow

04 CRC or some other error ratio limit of the frame level

has been exceeded

05 protocol error

06 loop test failed

07 error ratio limit of the time supervision has been

exceeded

FF other failure

DN70600744Issue 16-0 en


List of alarms

Instructions

If the connection establishment fails, check the wirings to the serial

communication of the unit (clock system, serial communication bus) and

the functioning of the unit of the connection's remote end.

A successful re-establishment of the connection is notified after

a temporary disturbance. Some messages of the applications may

have disappeared, in which case the operations related to the unit

should be observed.

The overflow of the unit's message queue is caused either by the

inability of the data transmission connection to transmit messages

at a speed corresponding to the speed of message requestes

(an overload situation in the remote end or disturbances in the

data transmission connection) or by an internal overload in the

unit. The consequences are the same as in the re-establishment

of the connection.

If the failure type is "protocol error", check especially the

wirings or strappings indicating the unit index of the units,

as well as the PCM cabling and possible transmission equipment,

including the ET.

If the loop test has failed, you have to check and possibly

replace the plug-in unit that caused the alarm. The clock system,

i.e. the clock units or the cabling, may also be faulty.

Cancelling

No cancelling.

2.175 1282 ASSOCIATION PARAMETER FAILURE

Meaning

Parameter setting has failed concerning Signalling System No. 7 (SS7)

signalling over Internet Protocol (IP).

The MTP3 User Adaptation Layer (M3UA) protocol has failed in setting at

least one of the Stream Control Transmission Protocol (SCTP) parameters

in the context of the SCTP association establishment.

This means that the value(s) of the SCTP association parameter(s)



do not change and so the value(s) of the parameter(s) are not

necessarily the values that the user has configured. When the parameter

setting fails, SCTP operates with the old value of the parameter.


1 SCTP Payload Protocol Identifier

1 - IUA [RFC3057]

2 - M2UA [RFC3331]

3 - M3UA [RFC3332]

4 - SUA [RFC2960]

5 - M2PA [RFC2960]

6 - V5UA [RFC2960]

7 - H.248 [H.248]

8 - BICC/Q.2150.3 [Q.1902.1/Q.2150.3]

9 - TALI [RFC3094]

10 - DUA <draft-ietf-sigtran-dua-03.txt> [Ong]

11 - ASAP <draft-ietf-rserpool-asap-03.txt> [Ong]

12 - ENRP <draft-ietf-rserpool-enrp-03.txt> [Ong]

13 - H.323 [H.323]

14-Q.IPC/Q.2150.3 [Q.2631.1/Q.2150.3]

2 IUA:

association number

M3UA:

association set, to which the association belongs

3 IUA:

Not applicable

M3UA:

index of the association inside the association set.

The value is between 0-31

4 identifier of the SCTP association within the computer unit

5 number of the socket corresponding the association

6 status of the socket option setting corresponding the

parameters. Value of the field is one of the following values

or a combination (sum) of some of the following values.

0001 SCTP Retransmission Timeout parameter setting failed.

Corresponding parameter names are RTI.INIT, RTO.MIN and

RTO.MAX.

0002 SCTP Peer Address parameter setting failed. Corresponding

parameter names are HB.INTERVAL and PATH.MAX.RETRANS.

0004 SCTP Association parameter setting failed. Corresponding

parameter name is ASSOCIATION.MAX.RETRANS.

0008 SCTP Checksum algorithm selection parameter setting failed.

DN70600744Issue 16-0 en


List of alarms

0010 SCTP Bundling parameter setting failed.

0020 SCTP SACK parameter setting failed.

Instructions


Service Center.

Enclose the printout outputs with the MML commands ZOYI::A; and

ZOYO; in the failure report. The ZOYI command shows the information

of the SCTP associations and ZOYO shows the SCTP association parameter

values. Enclose also the log writings of the S3ZOCK program block in the

computer log of the signalling unit identified in the first two fields.

Computer log writings can be obtained with service terminal commands

ZGD and ZGS.

Cancelling

No cancelling

2.176 1288 DATABASE REPLICA STATE CONFLICT

Meaning

There has been an attempt to use database replica state and database

remote copies in Network Element Management Unit (NEMU) in a

conflicting way.

The attempt was prevented and database continues operating normally.

However, the alarm can be an indication of configuration problem or

improper use of database replication via Network Element Management

Unit (NEMU).


1 database index (some database applications still need this

information, although nowadays the database is usually

identified based on the values of the following two

supplementary information fields, i.e. database name and

database occurrence)

2 database name



3 number of database occurence

4 01 Locked remote copy connection from NEMU attempted when

database is in replica state.

02 Replica state attempted when remote copy

connection to NEMU is active.

Instructions

Check the connection settings of all Network Element Management Units,

so that they correspond to the current Redundant HLR system

configuration.

Cancelling

No cancelling.

2.177 1293 SCCP GT SCREENING APPLIED

Meaning

SCCP has detected at the signalling transfer point a signalling message

for which this alarm must be set. Additionally, also the transit of the

signalling message is to be prevented.

This conclusion is based on the calling and the called global

titles included in the message.

If the transit message is destroyed, it may cause disturbance

in the function of the user parts of the signalling point that sent

the message. Usage restrictions for transit messages are usually set

on exchanges that function on another operator's interface.


1 type of access right violation of the STP function (cause code)

01 the source point behind the calling GTT result should not

send signalling messages with the called GT, the translation

of which leads to the called GTT result in question

(the message has been transmitted)

02 the source point behind the calling GTT result is not allowed

to send signalling messages with the called GT, the translation

of which leads to the called GTT result in question

DN70600744Issue 16-0 en


List of alarms

(the message has been destroyed or sent back)

2 signalling network of the adjacent point from which the processed

signalling message was received. Signalling network can get the

following values:





3 point code value of the adjacent point from which the processed

signalling message was received. This and the 2nd supplementary

information field together indicate the signalling point from

which the message was received, that is, the linkset from which

the message was received.

4 the calling GTT result into which the analysis of the calling GT has

led. The calling GTT result and the calling GT analysis that lead

to that result can be checked with the MML commands ZODL and ZODJ

respectively.

5 the called GTT result into which the analysis of the called GT has

led. The called GTT result and the called GT analysis that lead

to that result can be checked with the MML commands ZNAI and ZNBI

respectively.

6 the global title standard and the global title indicator used in the

calling global title of the SCCP message. The standard is encoded

with the most meaningful bits 5-8 in the following manner:

01 ITU-T

02 ANSI

The global title indicator is encoded with the least meaningful bits

1-4. The global title indicator is interpreted in the following

manner when the value in the most meaningful bits 5-8 is

01 (ITU-T):

01 global title contains only the nature of address

indicator


03 global title contains the translation type, the

numbering plan, and the encoding scheme


numbering plan, the encoding scheme, and the nature

of address indicator


the numbering plan, the encoding scheme or the

nature of address indicator. These global title

indicator values have not been defined in the

ITU-T recommendations

The global title indicator is interpreted in the following manner

when the value in the most meaningful bits 5-8 is 02 (ANSI):




numbering plan and the encoding scheme



the numbering plan, the encoding scheme or the

nature of address indicator. These global title

indicator values have not been defined in the ANSI

recommendations

7 translation type from the global title included in the calling

party address of the processed SCCP message.

The translation type values 0 and FF are interpreted in the

following manner when the value in the least significant bits 1-4

in the sixth supplementary field is 01 (ITU-T):



For the case the standard is ANSI and the global title indicator

is 02, there are values defined for the translation type in the

national specification ANSI T1.112-1992. These values of the

translation type can be analysed in the normal way, but they

do not cause special procedures in the system

8 numbering plan and the four least meaningful bits of the nature

of address indicator from the global title included in the calling

party address of the processed SCCP message.

The numbering plan is encoded with the most meaningful bits 5-8

in the following manner:

0000 unknown

0001 ISDN/telephone network numbering plan

(E.164,E.163)




0101 ship telephone network numbering plan

(E.210,E.211)


0111 ISDN/mobile telephone network numbering plan

(E.214)


:



The four least meaningful bits of the nature of address indicator is

encoded with the least meaningful bits 1-4 in the following manner:






:


DN70600744Issue 16-0 en


List of alarms

1111 nature of address indicator not included in global

title

9-11 address information from the global title included in the calling

party address of the processed SCCP message so that, for example,

the number 12345 is encoded

12 34 5F.

If the address information includes more than 6 digits, the address

information includes the first 6 digits.

Instructions

SCCP global title screening information says that messages with the

calling global title and the called global title combination in question

should not be transmitted. The analysis of the calling global title leads

to the calling GTT result as mentioned in the Supplementary information

field 4. The analysis of the called global title leads to the called GTT

result as mentioned in the Supplementary information field 5.

If the value of the Supplementary information field 1 (cause code) was 1,

the message was transmitted. If the value of the Supplementary

information field 1 (cause code) was 2, the message has been destroyed or

sent back. Check if this restriction is justified and remove the blocking

with the MML command ODN if necessary. Otherwise the operator who

owns the signalling point from which the message has been originated,

or alternatively the operator who owns the adjacent signalling point

from which the message was received, should be notified about an access

right violation.

For tracing the operator of the originating signalling point, the

information supplied in the Supplementary information fields 2, 3, 4, 6,

7, 8 and 9 could be used: the Supplementary information fields 2 and 3

show the adjacent point from which the message was received;

the Supplementary information fields 6, 7, 8 and 9 can be used to get

the calling global title from which the message was originated. The

Supplementary information field 4 (calling GTT result) can also be used

to find out the calling GT via calling GT analysis data, so that the

calling GT analysis is sought using the MML command ZODJ, which leads to

that calling GTT result record.

Cancelling

No cancelling.



2.178 1294 INFINITE LOOP IN HLR GENERAL ANALYSIS

Meaning

Execution of analysis has gone through too many subanalyses. It is

treated as an analysis loop. The limit for the number of subanalyses

to be executed in one CF registration case is defined

with PRFILE parameter

(in this case limit is (2*parameter value) + 10).

If this alarm occurs, CF registrations will not succeed.


1 the phase of HLR General Analysis

Analysis has not been defined for this phase

0 Not in use

1 Routing Category for CF phase


chain. Consequently this chain contains too many subanalyses

Instructions

Remove the faulty analysis, and correct the HLR General Analysis

before bringing it into use again.

The HLR General Analysis is considered to be in an infinite loop

when the amount of subanalyses to be executed > (2 * n) + 10,

where n is obtained with the MML command WOI, with the parameter

MAX_HGA_SUBANA_NBR.

You can check the HGA chain starting from the subanalysis whose

execution caused the alarm.

Correct the chain with the CY MML command group.

When the fault in the analysis has been corrected, the analysis

can be brought into use again.

Cancelling

Cancel the alarm with an MML command after correcting the fault as

presented in INSTRUCTIONS. See instructions on Alarm Administration.

DN70600744Issue 16-0 en


List of alarms

2.179 1295 TOO MANY SUBANALYSES IN HLR GENERALANALYSIS

Meaning

Analysis chain includes so many subanalyses that it can weaken

the capacity of the switch. The limit for the number of

subanalyses to be executed in one chain is defined with PRFILE

parameter.

This disturbance occurs if the number of executed subanalyses

exceeds the value of corresponding PRFILE parameter value.


1 the phase of HLR General Analysis

Analysis has not been defined for this phase

0 Not in use

1 Routing Category for CF phase


chain. Consequently the chain contains too many subanalyses

Instructions


with a smaller number of subanalyses. The number of subanalyses to


MAX_HGA_SUBANA_NBR that can be obtained with the MML command WOI.

The value of the parameter shows the maximum number of subanalyses to

be executed in user plane analysis. This maximum number should not yet

weaken the performance of the exchange too much.

You can check the analysis chain starting from the subanalysis

whose execution caused the disturbance.


Cancelling

Cancel the alarm with an MML command after correcting the fault as

presented in INSTRUCTIONS. See instructions on Alarm Administration.



2.180 1300 SUPERVISION CONNECTION TO UNIT LOST

Meaning

The unit has not responded in the allotted time to a supervision

message sent by the supervisory unit. The supervisor has lost the

connection to the unit and waits if the unit has restarted or failed.

Recovery actions have been started at once and after a short period

there will be another alarm, which tells the reason for the recovery:

1001 UNIT RESTARTED or

1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE


Instructions


The alarm does not have the supporting rule because the recovery actions

have been started and activated by the supervisor.

Cancelling

No cancelling.

2.181 1303 DB QUERY WARNING LIMIT EXCEEDED INSRRU

Meaning

This alarm gives database query information to the customer before

the paid limit is exceeded. The customer sets db query warning limit

value as percentage of the paid limit (25% - 150%) to the PRFILE.

Warning is set if the customer definable limit is exceeded.

DN70600744Issue 16-0 en


List of alarms


1 number of database query in SRRU pair

2 amount of SRRU pairs

Instructions

This alarm gives database query information from one SRRU pair. Total

number of database queries (SRRi) can be calculated in two ways:

1) (PEAK_VALUE) * (amount of SRRU pairs)

2) add together peak_values of all SRRU pairs alarms

If this alarm occurs the following will be checked:

1) If 2 SRRi's work in loadsharing mode, check that both SRRi network

elements are working properly.

2) Value of DB_QUERY_WARNING_LIMIT PRFILE parameter value is correctly

defined.

3) Is there need for more software lisences? To get more database query

capacity contact your local Nokia Customer Service Center.

Cancelling

No cancelling.

2.182 1305 ERROR IN SUBSCRIBER SIGNALLINGINCOMING MESSAGE

Meaning

The subscriber signalling program block (SUBSIG) monitors the format

of the messages it has received. An alarm is given of

each message with a format error.


1 error code

01 invalid sender

02 invalid module circuit

03 invalid ASS channel



04 invalid group switch circuit

2 family identifier of the alarm sender

3 process identifier of the alarm sender

4 message number

5 first info byte in the received message

6 second info byte in the received message

7 third info byte in the received message

8 fourth info byte in the received message

If the message number is 6006, this is a message of the

subscriber module. In this case supplementary information fields

5 (lsb) and 6 (msb) contain the stage number and supplementary

information fields 7 (lsb) and 8 (msb) the module number.

Instructions





Cancelling

No cancelling.

2.183 1308 PRIMARY LDAP DIRECTORY SERVERACCESS FAILED

Meaning

This alarm indicates that the primary LDAP directory server cannot

be used for subscriber data fetching.

Because of this, registering or call initiation of subscribers using

SIP-URI (Session Initiation Protocol - Uniform Resource Identifier)

through SIP access side signalling will be possible only through a

secondary server (if one exists and has been configured).

The SIP Subscriber Database functionality is not redundant anymore.

DN70600744Issue 16-0 en


List of alarms


1 reason of the connection failure:

03 - the ldap server cannot be reached

04 - the server is reached but the bind operation

to it didn't succeed

Instructions

1. Check if there is a physical connection between the unit and the

directory server.

In case of physical connection failure, fix the cabling fault and

then restart the object unit of this alarm with the MML command

USU.

2. Check whether the ZF1FIL file exists in the object unit of this

alarm with the MML command DFL.

If typing the DFL command for the file yields the response "NO

SUCH FILE", contact your local Nokia Customer Service Centre.

If the response shows the file parameters (indicating that the file

exists) but the record number in the returned output is zero, the

directory server needs to be reconfigured with the MML command JDM.

3. Check the values of the configuration parameters necessary for

establishing a connection to the primary directory server.

The values of the parameters can be checked with the MML command JDI.

The parameters listed in the output of this command need to correspond

to the attributes of the directory server.

If any configuration failure has been found, the directory server

needs to be reconfigured with the MML command JDM.

Cancelling

No cancelling.

2.184 1312 RAM FAILURE IN PREPROCESSOR UNIT

Meaning

An error has been detected in the RAM of the preprocessor

unit's processor.




1 faulty plug-in unit:

FF control plug-in unit

Instructions

Replace the faulty control plug-in unit.




Cancelling

No cancelling.

2.185 1313 FAILURE IN LI2M COMMUNICATION

Meaning

The LI2M plug-in unit is unable to establish a maintenance connection

to the SSU or the CAC when transferring alarms.


1 index of the LI2M plug-in unit (0...1)

Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.186 1314 LI2M RESTARTED

Meaning

An internal restart occurred in the LI2M plug-in unit.


1 index of the LI2M plug-in unit (0...1)

Instructions


Cancelling

No cancelling.

2.187 1320 UMA RESOURCE ALLOCATION FAILURE

Meaning

Reserving a terrestrial resource for UMA access fails.


1 administrative number of the UNC to which the

user plane destination id was specified

1 - FFF UNC


resource that is being allocated

3 route



FFFF unknown

4 error code


was sent in the wrong call phase, that is, the route,

switch type, or circuit type is invalid






Instructions


Check in MSS if the user plane destination id in question has been

defined correctly for the UNC.



Cancelling

No cancelling.

2.188 1322 NO RESPONSE TO SUB SUPERVISIONMESSAGE

Meaning

The subscriber module (SUB/SUB-D) has not responded to the supervision

message sent by the USAPRO program block of the control computer,

or a critical number of DLIs in the digital subscriber module

do not respond to the supervision message.

DN70600744Issue 16-0 en


List of alarms


1 error status

00 subscriber module does not respond to supervision

01 number of DLIs exceeding the defined limit do not

respond to supervision (in digital subscriber module)

Instructions





Cancelling

No cancelling.

2.189 1328 VLR LOAD CONTROL UPPER LIMITREACHED

Meaning

The CPU load of the VLRU has reached 98%. The VLRU will reject all

MOC, MTC, SMS, and LU transactions during the following 10 seconds

and will limit the traffic until the load drops below 98%. Below 98%

some traffic limitation may take place as defined in the VLR

parameters.


Instructions

If the alarm is raised during the cleaning or other similar batch works,

no actions need to be taken.

If the alarm is raised during normal operation, the configuration should

be reconsidered. For example, more HW units could be added to the VLR or



the CPUs could be upgraded; or the number of subscribers in the VLR could

be limited with a licence or with PRFILE parameters

11:19 VLR_CAPACITY_FUSE.

It is also possible to set the VLR parameter PRIMO to a lower value so

that the CPU load is stabilised at an earlier CPU load point and 98%

CPU load will never be reached.

Cancelling

The alarm does not need to be cancelled.

2.190 1333 ISUP SCREENING FILE OPENING ERROR

Meaning

This disturbance indicates that the ISUP signalling program block did not

succeed in opening the ISUP screening file

AND

the ISUP screening file (IS7FIL) has been corrupted or does not exist in

the unit's memory. The ISUP signalling part (SI7PRB) cannot use support

or compatibility information values created with the FN1735 ISUP

screening mask.

The original values are used instead.


Instructions

FN1735 ISUP screening mask feature deactivation has been automatically

initiated by the system. If the automatic deactivation fails, the feature

should be deactivated manually. This can be done with the MML command

WOA (parameter class 002, parameter number 1271).

After the deactivation has been completed, contact the local Nokia

Customer Service Center. Do not reactivate the feature until the problem

has been solved.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.191 1337 INTERCEPTION DISTURBANCE

Meaning

This alarm indicates OLCM specific alarms and notifications as

disturbance in the dx alarm system.


1 this field indicates the olcm notification number. Refer to the list

of alarms in MSC On-Line Call Monitoring Interface Speficiation

2 used trace reference number related to intercepted user

3 law enforcement agency id

4 additional field used at olcm notification

5 additional field used at olcm notification

Instructions

For operating instructions please refer to the OLCM specific instructions

to handle OLCM originated alarms and notification. OLCM specific alarms

and notification can be identified based on the alarm_id field of this

alarm.

Cancelling

No cancelling.



2.192 1340 HOTLINK FAILURE

Meaning

Plug-in unit HOTLink cable or transmission fault detected.


1 type of the plug-in unit causing the alarm

FFFF means that the plug-in unit type cannot be given

2 index of the plug-in unit causing the alarm

FFFF means that the plug-in unit index cannot be given

3 index of the HOTLink interface

4 the exact error code of the HOTLink test. Possible reasons are:

0040 HOTLink sfp module unplugged

0080 HOTLink fault

0100 HOTLink CRC transmission fault

Instructions

Change the faulty HOTLink cable indicated in the additional information

of the alarm.

The traffic is automatically changed from faulty HOTLink cable to

existing redundant HOTLink by the system.

Cancelling

No cancelling

2.193 1343 AOIP RESOURCE ALLOCATION FAILURE

Meaning

The reservation of IP resource on the A-interface failed.

DN70600744Issue 16-0 en


List of alarms


1 administrative number of the BSC where the resource reservation was

unsuccessful

1 - FFF BSC

2 error code

Typical error codes:

405 the request message contained erroneous parameters or was

sent in the wrong call phase, that is, the route, the switch

type or the circuit type is invalid





719 no RMA-hand resource available for the call



Iu-resource that is being allocated

Instructions


Check in MSS if the user plane destination id in question has been

defined correctly for the BSC.

Cancelling

No cancelling

2.194 1400 AFS RESTARTED

Meaning

An internal restart has occurred in the AFS plug-in unit.




1 type of AFS plug-in unit

2 index of AFS plug-in unit

Instructions


Cancelling

No cancelling.

2.195 1423 NO RESPONSE FROM MAIN CLOCK

Meaning

No response is obtained from the active unit maintaining the main clock.


Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.196 1425 OVERFLOW IN ALARM BUFFERING

Meaning

The alarm system has received more alarm output tasks than it is able

to buffer for outputting or for sending to the Q3 core system. However,

the alarms that are not output or sent to the Q3 core system are

saved normally in the alarm system log file (ALHIST), from which they can

be output with an MML command. The alarm is set after all buffered alarm

output tasks have been processed and sent forward from the alarm system

after a buffer overflow.


1 0 buffer used for buffering the alarms to be output

has overflown

1 buffer used for buffering the alarms to be formatted

for sending to the Q3 core system has overflown

2 number of alarms not output or sent to the Q3

core system

Instructions


Cancelling

No cancelling.

2.197 1431 MMI SYSTEM OVERLOAD

Meaning

The MMI system is overloaded.




Instructions





Cancelling

No cancelling.

2.198 1432 DISTURBANCE IN COMMAND CALENDAR

Meaning

A temporary disturbance has been detected in the command

calendar operation.

The command calendar interrupts the execution of the calendar

task that was being executed and blocks the task. An exception

is made with those command files that are supposed to be executed

more than once and of which execution is not interrupted although

some of the commands in the file fail (marked as NOINT in the

CFTYPE column of the execution printout of the MML command ICL):

these calendar tasks are not blocked.

The blocked tasks are not executed before the fault has been

corrected and the blocking is removed.

If the fault is permanent, then also the alarm 2430, ERROR IN

COMMAND CALENDAR, is set.


1 error specification

MML error:

01 creation of MML session has failed

02 interruption in session

DN70600744Issue 16-0 en


List of alarms

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.

This identifier can be seen in the ID column of the

execution printout of the MML command ICL and points

out the command calendar task which was been executed

when the disturbance occurred

3 name of the command file been executed without the

extension .CMD

4 index of the command in command file

Instructions

You can check which calendar task execution has failed from the

MML session log/MML command log (with the MML command IGO), from

the command calendar queues (with the MML command ICL) or from

the execution printouts.

For more information, see instructions on MML commands and

command calendar.

NOTE! If the command calendar has blocked the calendar task,

the blocking must be removed in all cases mentioned below

after the fault has been corrected: otherwise the task

cannot be executed again.

You can check whether the calendar task is blocked with the

MML command ICL: the blocked commands are marked with the

identifier BLC in the QUE column of the output.



For example, ICL; outputs data of all tasks. You can remove

the blocking with the MML command ICB.

For example, ICB:11:UNBLOCK; removes the blocking from the

calendar task 11.

If the value of the supplementary information field 1 is 01,

the calendar task cannot be executed, because:

a) all MML sessions are busy. Do the following:

1. Ask a user to close his/her MML session, so that a command

calendar can start an MML session.

2. Check if the alarm 2427, MMI SYSTEM FILE ERROR, is set.

If the alarm is set, act according to its instructions.

3. If the calendar task is blocked, remove the blocking with

the MML command ICB.

b) the calendar task has been created by using a username that

has been deleted. Do the following:

1. Remove the task from the calendar with the MML command ICD.

2. Add the same task to the calendar again with the MML command

ICI. Note that ICD does not delete the command file from the

disk, only from the calendar: you can add the same command

file to the calendar again, if it is not deleted from the

disk.



If the value of the supplementary information is 02, the MML

command has made a memory protection error. Check if the alarm

1078, PROCESS EXCEPTION, is set. If the alarm is set, act

according to its instructions.

If the value of the supplementary information is 03, the command

in the calendar (including the commands of the command files in

the calendar) cannot be executed, because its syntactic structure

is faulty. Correct the command with the MML command ICM so that

it conforms to the syntactic rules of the command.

If the value of the supplementary information is 04, the command

in the calendar (including the commands of the command files in

the calendar) cannot be executed, because its semantic structure

is faulty. Correct the command with the MML command ICM so that

it conforms to the semantic rules of the command.

If the value of the supplementary information is 05, do the

following:

a) If the execution printouts of the calendar tasks are directed

to the printer (you can check with the command IID::COMCAL;

where the printout are directed to):

DN70600744Issue 16-0 en


List of alarms

1. Check with the MML command ISI, whether the printer is

working.

The following command outputs information about the printer

LPT-0:

ZISI::LPT,0;

2. If the printer does not work, correct the fault

(eg. add paper).

3. Remove the blocking from the command with the MML command ICB.

RECOMMENDATION: Direct the printouts also to the BBU-0, if you

want that the command calendar is working even when the printer

is not working.

Direct the printouts through the semipermanent logical file

(see the instructions given on the supplementary information

value 10 at the end of the description).

b) If the execution outputs are directed to the disk file (you can

check with the command IID::COMCAL; where the printouts are

directed to):

1. Check with the MML command ISI that the disk is not damaged.

The following command outputs information about the disk:

ZISI::WDU;

2. If the disk is damaged, change the disk.

3. If the disk is not damaged, check with the MML command IWX,

if there is space in the file for the printouts. The following

command outputs data from the file CCALENDAR, whose name ends

with LOG.

ZIWX::WS::MMDIRE:CCALENDAR,LOG;

If there is no space in the file, direct the printouts to

another file. It is recommended that the printouts are

directed to a ring file.



RECOMMENDATION: Direct the printouts also to the BBU-0, if you

want that the command calendar is working even when the printer

is not.

Direct the printouts through the semipermanent logical file

(see the instructions given on the supplementary information

value 10 at the end of the description).

c) If the calendar task is a command file:

1. Check with the MML command IDL that the command file is

not faulty.



If the file is faulty, an error message is output.

2. If the file is faulty , edit it with the MML command IEE.

Check eg. that the file structure is correct (the commands

are one below the another in the right order and comments

are within the comment characters).



d) If the alarm 2427, MMI SYSTEM FILE ERROR, is also set, act


If the value of the supplementary information is 06, there has

been a password check error. Fill in a Problem report and send

it to your local Nokia Customer Service Center.

If the value of the supplementary information is 07, loading the

MML program that executes the command to memory has failed.

Do the following:

1. Check whether the alarm 2427 is set. If 2427 is set, act


2. If the calendar task has been blocked, remove the blocking

with the MML command ICB.

If the value of the supplementary information is 08, there has

been a data transmission error. Fill in a Problem report and


If the value of the supplementary information field is 09,

the calendar task cannot be executed, because:

a) the command calendar has no authority to execute the command

or because the user who has added the command into the command

calendar has no authority to execute the command.

1. If you want to execute the task from the command calendar,

you can change, with the MML command IAA, either the

command calendar authorities or the authorities of that user

who has added the task into the command calendar. You can use

the command IAA only if you have the authority to use it.

2. If the task is blocked, remove the blocking with the

MML command ICB.

b) you cannot execute the command from the command calendar.

These commands include the interactive commands, that is, those

commands that output questions which the user needs to answer

before the command can be executed.

For example, ICI is an interactive command. Those commands that

require the user only to confirm the execution of the command

(Y/N) can be executed from the command calendar.

Execute the command normally without using the command calendar.

DN70600744Issue 16-0 en


List of alarms

If the value of the supplementary information is 0A, the calendar

task cannot be executed because the OMU is at state TE or SE and

an attempt has been made to execute an MML command that must not

be executed at TE and SE states. Do the following:

1. Change the state of the OMU into WO with the MML command USC.

2. If the calendar task has been blocked, remove the blocking with


If the value of the supplementary information is 0B, the calendar

task cannot be executed because at the same time that the command

calendar is executing a specific command, another user is using

some command that must not be used at the same time with the

command in question. If, for example, another user is executing

the command USU, the command calendar cannot at the same time

execute the commands of the command group WR.

If the command task has been blocked, remove the blocking with


If the value of the supplementary information is 0C, 0D, 0E, 0F,

act according to the instructions of the alarm 2430, ERROR IN

COMMAND CALENDAR.

If the value of the supplementary information is 10, the logical

file COMCAL needed in the execution of the calendar tasks has not

been created.

1. Check with the MML command IID, whether the logical file COMCAL

has been created:

ZIID::COMCAL;

2. If the logical file COMCAL has not been created, create it and

connect the printer that you want to it. It is recommended that

the printer LPT-0 and BBU-0 are connected to the COMCAL: in this

case, the execution printouts of the calendar tasks are output

to the printer and the BBU-0 ensures the functioning of the

command calendar even when the printer is not functioning.

Do the following:

a) Create a logical file COMCAL and connect a printer LPT-0

with the MML command IIF:

ZIIF::COMCAL,S:DEV=LPT-0

b) Connect the BBU-0 to the logical file COMCAL.

First, create the semipermanent logical file and connect it

to BBU-0 with the MML command IIF. The following command

creates the file BYTEBASKET:

ZIIF::BYTEBASKET,S:DEV=BBU-0;

Then add the semipermanent logical file you have created as



one of the targets of the COMCAL with the MML command IIS:

ZIIS::COMCAL::LF=BYTEBASKET;

3. Find out why the logical file COMCAL has not been created.

Check whether the COMCAL is in the PLFILEG2 file. The PLFILEG2

file is in the LFILES directory. Output the contents of the file

in the following way:

a) Define the directory where you output a file from with the

MML command IWX:

ZIWY:S:UNIT=OMU:PATH=LFILES;

b) Output the contents of the file with the MML command IBT:

ZIBT:WDU,S,PLFILEG2,IMG;

If the COMCAL is not found in the PLFILEG2 file, the software

build contains the wrong version of the PLFILEG2 file. Contact

the local Nokia Customer Service Center.

If the COMCAL is in the PLFILEG2 file, there has been an error.

Find out the error with the help of alarms and logs.

If the value of the supplementary information is 11, the logical

file COMCAL needed in the execution of the calendar tasks is

reserved for the execution of another calendar task or some

user is changing its connections.

Wait until the other calendar task is finished or that the

connections of the COMCAL have been changed.

Cancelling

No cancelling.

2.199 1450 NO RESPONSE TO SYSTEM SUPERVISIONMESSAGE

Meaning

The system of the operation and maintenance network has not

responded within the specified time to the supervision message.

DN70600744Issue 16-0 en


List of alarms


1 system identifier

Instructions


Cancelling

No cancelling.

2.200 1453 NO RESPONSE TO TIME INQUIRY

Meaning

The system supervised by the MSW or the OMC does not respond to the time

inquiry.


1 system identifier

Instructions


Cancelling

No cancelling.



2.201 1455 NO RESPONSE TO TIME ADJUST MESSAGE

Meaning

The system supervised by the MSW or the OMC does not respond to the time

adjust command.


1 system identifier

Instructions


Cancelling

No cancelling.

2.202 1532 FAULTY COMMON CHANNEL SIGNALLINGMESSAGE

Meaning

The system issues this disturbance if the program family that

controls the circuit has received from the message transfer

part (MTP) a message that is faulty, or unknown to the

telephone user part. The disturbance is also issued if the

information part of the message contains conflicting

information. The message received has not caused any

erroneous action; it has either been rejected or the faulty

information has not been processed.


1 error code

01 signalling message is not in use

DN70600744Issue 16-0 en


List of alarms

02 signalling message is too short or its release

failed

03 number of circuits in a circuit group message

exceeds the maximum limit or is less than the

minimum limit

04 acknowledgement of a circuit group message does

not contain all the requested circuits

05 circuit group message contains circuits that do

not belong in the signalling

06 blocking message has been acknowledged, but the

acknowledgement contains additional circuits

which should not be blocked

07 unblocking message has been acknowledged, but the

acknowledgement contains additional circuits

which should be blocked

08 unexpected blocking acknowledgement has been

received. It contains circuits which should not

be blocked

09 unexpected unblocking acknowledgement has been

received. It contains circuits which should be

blocked

10 received message contains incorrect parameters

compared to the other parameters or call phase.

FF there is not enough data for setting this or any

other error code



4 type of the received message in ascii format

as follows:

ISUP : e.g. iam, cgb, cgba, blo, bla ...

If the message is unknown, or the program block does

not have an ascii name list, it is presented in

hexadecimal form

5 PCM circuit

6 first faulty timeslot or the first circuit group

timeslot under error conditions

7 the range of faulty timeslots in hexadecimal form

if the value of the 6th supplementary information is

22, and the value of the 7th supplementary

information is 6, this means timeslots 22 - 27 so

that e.g. 23 and 24 can be missing from between

FF = the range cannot be specified

the value of the 7th supplementary information



actually means the range of the circuit

identification code (CIC) beginning from the variable

PCM/TSL, if Free CIC Allocation is in use

Instructions

If disturbances are issued, you can use the commands of the

MML command group AP for changing the filtering time from 20

minutes to one second. The new and shorter filtering time

becomes effective only after the original time (20 minutes)

has passed. Short filtering time makes it possible to monitor

different commissioning situations, for example, to find out

if the same disturbance occurs repeatedly, or if there are

other error codes which have the value shown in the 1st

supplementary information.

The original filtering time (20 minutes) reports only the

first one of the periodically repeated disturbances. If every

call causes disturbances, the alarm system repeats the

disturbance whenever the time between two calls is longer

than the filtering time.

The disturbance is PCM-specific, so only one disturbance per

PCM is reported.

When a disturbance occurs, use the specifications of the SS7

signalling user part and the following MML commands:

WIP

CEL

RCI

Cancelling

No cancelling.

2.203 1541 PROGRAM BLOCK RESTARTED IN COCA/EC1P

Meaning

A program block located in the COCA or EC1P plug-in unit has

been restarted.

DN70600744Issue 16-0 en


List of alarms


1 family identifier of the restarted program block

Instructions


Cancelling

No cancelling.

2.204 1542 DSP RESTARTED

Meaning

USAPRO has loaded a new program for the signal processor and has

restarted it.


1 number of a signal processor in the unit

0-31

2 internal PCM handled by the signal processor

0-1

3 first timeslot handled by the signal processor

0-31

4 last timeslot handled by the signal processor

0-31

Instructions




Cancelling

No cancelling.

2.205 1543 COCA/EC1P RAM FAILURE

Meaning

A failure has been detected in the RAM memory of the COCA or EC1P

plug-in unit.


Instructions


The alarm supports the activation of automatic recovery measures for

the target unit. The amount of support, i.e. the alarm gravity level,

can be checked with the MML command ARO.

Cancelling

No cancelling.

2.206 1544 DM2 FAILURE

Meaning

A failure has been detected in the DM2 digital multiplexer of the modem

pool controller (MPC) or of the digital interface controller (DIC), or

the DM2 is in abnormal state. It is possible that several of the

failures (FAIL_CODE1,,,FAIL_CODE8) detected by the DM2 multiplexer are

set at the same time.

DN70600744Issue 16-0 en


List of alarms


1-8 error code

0 error in the power supply

15 DM2 is looped back to the interface

16 DM2 is looped back to the device

32 incoming 2MHz signal is missing

51 loss of frame alignment

52 loss of multiframe alignment

7A synchronization failure

7C clock synchronization failure

82 memory failure

8E installation error

FF no significance

Instructions

Check the error code. If the DM2 is looped back (error code 16), connect

the service terminal TC21700 to the DM2 and remove the loop-back.

The command given at the service terminal is as follows:

mode,1,ret,5,ret,9,ret,2,ret,2,ret.

Otherwise change the DM2. See Instructions for Replacing Plug-in Units.

The alarm supports the activation of automatic recovery measures for the

target unit. The amount of support, i.e. the alarm gravity level, can be

checked with the MML command ARO.

Cancelling

No cancelling.

2.207 1545 DM2 ET ALARM

Meaning

The DM2 digital multiplexer in the modem pool controller

(MPC) or in the digital interface controller (DIC) has

received the AIS signal or a remote end alarm from the

exchange terminal (ET), or it has detected that the data

received is erroneous. It is possible that several faults

detected by the DM2 multiplexer are set at the same time

(supplementary information fields 1-8).




1 error code

42 AIS received

4A AIS received in timeslot 16

56 CRC missing

63 bit error ratio > 1 E-3

B2 multiframe alarm received from the remote end

B3 alarm received from the remote end

FF no significance

2 error code (see above)







Instructions


Cancelling

No cancelling.

2.208 1546 ERROR IN MEMORY HANDLING OFPROGRAM BLOCK

Meaning

An error has occurred in the memory handling of the MTAPRB

program block. Usually this indicates that MTAPRB is running

out of memory. Since the amount of memory is sufficient to

handle all situations which conform to protocol

recommendations, this error situation results from some other

error.

DN70600744Issue 16-0 en


List of alarms

The error situation may be temporary, it does not have a

direct effect on other dialogues. However, the ongoing

dialogue is usually interrupted.

The error situation has no direct effect on charging or

announcements.


1 error code

7E overflow or underflow in encoding buffer

8C dynamic memory overflow

97 operational activations overflow

2 operation code indicating to what operation the situation

causing the alarm is related to.

3 number of the remote end's subsystem. If the number is

unknown or unnecessary, the subsystem number is set at

zero (0).

4-15 remote end's address. The type of address is indicated

first:

00 Global title

01 Network indicator and the signalling point code

address

After the address type comes either the global title, or

the network indicator and the signalling point code

address. If the address is unknown or unnecessary, the

fields are filled with zeros (0)

Instructions

Fill in a failure report. Attach the following information to

it:

In case of a MAP protocol alarm set by MTA_IX:

- MAP statistics (operation counters to all directions, a

detailed report, MML command group ZOX)

- log files of the CCSU computer units,

- contents of the MAP cyclic buffer (MML command OPO), and

- alarms and disturbances set by the MTAPRB program block.

In case of an INAP protocol alarm set by ITA_IX:



- INAP statistics (operation counters to all directions, a

detailed report, MML command group ZOA)

- log files of the CCSU computer units,

- contents of the INAP cyclic buffer (MML command OEO), and

- alarms and disturbances set by the ITAPRB program block.

Send the failure report to the local Nokia Customer Service

Center.

Cancelling

No cancelling.

2.209 1547 ERROR IN COMPONENT HANDLING

Meaning

An error has occurred in the handling of an operation or its

acknowledgement. The most common error situations are:

1. the system cannot convert data from the format used

internally in the DX-system into the format used in the

signalling network (ASN.1), or

2. the system cannot convert data from the format used in the

signalling network (ASN.1) into the format used internally

in the DX-system.

Case 1 usually indicates an error situation in the DX-system.

Case 2 usually indicates incompatibility between network elements.

The error situation may be temporary, it has no direct effect

on other dialogues. The error situation usually interrupts the

ongoing dialogue.


announcements.


1 error code. The following values are possible:

78 erroneous type identifier

79 missing end-of-coding character

7A coded value outside value range

7B primitive type identifier combined with

DN70600744Issue 16-0 en


List of alarms

undefined length coding

7C incorrect length field

7D encoding violating syntax

7F component coded several times

80 compulsory component missing

81 list overflow

82 ENUMERATED type has an invalid value

8D too many nested levels in the ASN. 1 variable

98 unidentified invoke id

99 unidentified operation code

9A unidentified reject type

9B unidentified error code

9C unidentified rejection cause

9D component heading violating syntax

9E unsuitable length field value

9F unsuitable error code

A2 unsuitable service category

A3 unsuitable checking type

A4 unidentified component type

A5 unidentified invoke id of connected operation

A6 unexpected response from succeeded operation

A7 unexpected response from failed operation

A8 erroneous operation code

A9 erroneous primitive type

AA unexpected selection field

CA unidentified ISDN address type

CB ISDN address too long

CD wrong address type


causing the alarm is related to

3 number of remote end's subsystem. If the number is

unknown or unnecessary, the subsystem number is set at

zero (0)

4-15 remote end's address. The type of the address is indicated

first:

00 Global title

01 Network identicator and the signalling point code

After the address type comes either the global title,

or the network identity and the signalling point code address.

If the address is unknown or unnecessary, the fields are filled

with zeroes (0).

The structure of the global title :

1. byte : address length (amount of numbers)

2. byte : numbering plan of the address and type of the

number.

This data has been coded according to GSM 09.02

recommendation. The most common values are

91 (E.164/INT), A1 (E.164/NAT) and



97 (E.214/INT).

3..12 : numbers of the address in compressed form, two

numbers per byte

Instructions

Collect the following data:

- MAP statistics (operation counters to all directions,

a detailed report, MML command group ZOX),

- log files of the SMMU computer units,

- contents of the MAP cyclic buffer (MML command OPO), and

- alarms and disturbances set by the MTAPRB program block.

and contact the local Nokia Customer Service Center.

Cancelling

No cancelling.

2.210 1548 MTP CONFUSION MESSAGE RECEIVED

Meaning

An MTP confusion message has been received in the exchange.

The signalling point indicated by the originating point

code given in the 3rd supplementary information field has not

identified the signalling network management message. The

heading code of the signalling network management message

is given in the 6th supplementary information field.


1 SIO in MTP confusion message

2 destination point code in MTP CONFUSION message

3 originating point code in MTP CONFUSION message

4 heading code of MTP CONFUSION message

DN70600744Issue 16-0 en


List of alarms

5 implementation level indicator in MTP CONFUSION message

6 confusion_msg_id in MTP CONFUSION message, i.e. a heading

code that was not identified

Instructions


Cancelling

No cancelling.

2.211 1549 TSLS UNTESTED IN ROUTINE TEST

Meaning

The IRUTIN program block has completed a test period. The number of

untested timeslots exceeds the maximum number specified in the

parameter file.


1 type of test:

0 ECU loop test

2 the upper limit of untested timeslots as

a percentage of all timeslots to be tested

3 the number of tested timeslots

4 the number of untested timeslots

5 the number of the timeslots that the system did not

even try to test

6 the number of the timeslots that were reserved when

the system tried to test for the last time

7 the number of the timeslots whose last test attempt

failed due to an error in the unit to be tested



8 the number of the timeslots whose last test attempt

failed due to an error elsewhere than in the unit

to be tested

Instructions

Check that the test period is long enough in relation to the number of

timeslots to be tested. If necessary, lengthen the test period in the

parameter file, or increase the number of tests run simultaneously.

Cancelling

No cancelling.

2.212 1550 FAULTY NATIONAL USER PART MESSAGE

Meaning

The disturbance is given if the program block supervising the

circuit has received from the message transfer part a faulty

message, or one that is unknown to the telephone user part. The

message was rejected, and the fact that it was received did not

cause a fault situation.


1 error code:

01 the signalling message is not in use

02 the value of the service information octet

is not in use

FF there is insufficient information for any

other error code to be set




5 circuit identification code

6 first heading code of the signalling message

DN70600744Issue 16-0 en


List of alarms

7 second heading code of the signalling message

8 PCM circuit

9 time slot

Instructions

If several disturbances are given, check the files related

to the coding of the label fields of the message, at both

ends of the trunk circuit.

Cancelling

No cancelling.

2.213 1551 CCS USER PART ACKNOWLEDGEMENTMESSAGE MISSING

Meaning

The disturbance is given when the partner exchange has failed to

acknowledge the implementation of a requested function. If repeated

attempts fail to produce an acknowledgement, steps are taken as

required by the user part.

In case of BICC Call Instance Code is used instead of circuits.


1 type of the sent message (word)

(The lower byte tells the heading code of the network message

(in the TUP/ISUP) or the message (in the NUP). The upper byte

is empty (in the TUP/ISUP), or contains the message group ID

(in the NUP).)



4 PCM circuit, not used in BICC



5 timeslot, not used in BICC

6 number of circuits in circuit group

7 Call Instance Code

Instructions

If several disturbances are given, check the availability of the message

transfer part and the traffic capacity state of the partner exchange with

the MML command NET.

Cancelling

No cancelling.

2.214 1552 FAULTY ISDN USER PART MESSAGE

Meaning

The disturbance is given if a circuit-supervising program block has

received an erroneous message from the message transfer part, or one

that is unknown to the telephone user part. The message has been

rejected, or the misinformation it contains is not handled. The

reception of the message has not caused operational errors.


1 error code:

01 signalling message is not in use

02 SIO value is not in use

03 too many circuits in circuit group message

04 acknowledgement of circuit group message deficient

FF insufficient data to set other error code




DN70600744Issue 16-0 en


List of alarms

5 circuit identification code

6 message type

7 PCM circuit

8 timeslot

Instructions

If several disturbances are given, check the files connected with

encoding the label fields of messages at both ends of the trunk

circuit.

Cancelling

No cancelling.

2.215 1556 HLR SPECIAL ROUTING INFORMATION

Meaning

An inquiry from the HLR about routing information was directed to the

operator's service number, or the routing request originated from a

prohibited address. The address used was a global address or a signalling

point.


1 situation where routing information was requested:

0 = operator service number

1 = blocking of optimised routing

2-12 global address used when requesting routing data

13 signalling point used when requesting routing data

14 network ID used when requesting routing data



Instructions

You can read the subscriber number that caused the alarm from the log

outputs of the CCSU.

Cancelling

No cancelling.

2.216 1557 EVENT HANDLER CANNOT WORKPROPERLY DUE TO FILE SERVICE FAILURE

Meaning

Event handler cannot save its own attributes in the disk file or

the file services for saving and reading the events have failed.

If the file services are not functioning, they prevent or disturb

the functioning of the event handler.


1 error code

You can check its meaning in General Error Messages of System

2 disk file identifier

Disk file where attributes cannot be saved.

Value zero indicates that the file services for saving and

reading the events have failed

3 family identifier

Family which fails to provide the requested file service

Instructions


DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.217 1558 RADIO NETWORK CONFLICT

Meaning

A network approaches the MSC with an unknown ID (CI, LAC, SPC).


1 ID in question:

03: Cell Identity (CI)

04: Location Area Code (LAC)

05: Location Area Code and Cell Identity (LAC + CI)

06: Service Information Octet and Signalling Point Code

(SIO + SPC)

07: ISDN number

2 ID number:

1 - FFFF : CI, LAC

83, C3, 03, 43 : SIO

3 ID number:

1 - FFFF : CI

1 - 3FFF : SPC

4 transaction type:

01: supplementary service

02: mobile-originated call

03: IMSI detach

04: location update

05: mobile-originated short message

06: mobile-terminated short message

07: mobile-terminated call

08: emergency call

09: handover

0A: re-establishment

0B: SCCP subsystem state change

0C: SDCCH handover

0D: handover in MSC-B



0E: resource indication

0F: handover canditate

10: load indication

Instructions

Check the radio network configuration and add, if necessary, the missing

entity to the configuration.

Cancelling

No cancelling.

2.218 1559 A-INTERFACE CIRCUIT ALLOCATIONFAILURE

Meaning

The reservation of a circuit on the A-interface failed.


1 route

FFFF unknown

2 administrative number of the BSC/MGW(Rel99) to whom the

route was specified

1 - FFF BSC/MGW(Rel99)

3 error code


was sent in the wrong call phase, that is, the route, switch

type or the circuit type is invalid


601 no free module circuits available on the requested route


60D no free stage circuits available on the requested route

804 no free outgoing circuits available on the requested

route


DN70600744Issue 16-0 en


List of alarms


719 no RMA-hand resource available for the call

80D outgoing circuit is faulty

80E incoming circuit is faulty

B14 handover failure, for example the target BSC may be out of

service

4 PCM circuit

FFFF unknown PCM

5 timeslot

FF unknown timeslot

Instructions


Check in MSC if the route in question has been defined for the

BSC/MGW(Rel99), and what is its state. To do this, use the Base

Station Controller Handling MML, command ZEDO. If necessary, activate

the route by means of the Circuit Group Handling MML.



Cancelling

No cancelling.

2.219 1560 BSC OR BTS OUT OF SERVICE IN MSC

Meaning

In the MSC, a base station controller (BSC) or a base transceiver

station (BTS) is in a state where traffic cannot be transmitted.


1 the base station system element concerned:

01: BTS

02: BSC



2 administrative number of the BTS or BSC:

1 - FFFF: BTS

1 - FFF : BSC

3 state of BTS or BSC:

02 : administrative state "LOCKED"

0B : global reset started by BSS not finished

0C : global reset started by MSC not finished

0D : release of MSC internal resources not finished

0E : SCCP subsystem unavailable

FF : SCCP subsystem in unknown state

Instructions

Change the administrative state of the BSC or BTS to "UNLOCKED" and

activate the BSSAP subsystem of the signalling point defined for the

BSC concerned.

Cancelling

No cancelling.

2.220 1561 DPNSS ACKNOWLEDGEMENT MESSAGEMISSING

Meaning

This disturbance is given when a partner PBX has failed

to send a message acknowledging execution of a function.

If repeated attempts do not produce an acknowledgement, BTNR 188

is observed.


1 error code:

01 clearing acknowledgement missing

FF insufficient information to set other

error code

DN70600744Issue 16-0 en


List of alarms

2 number of external PCM circuit

3 number of DLC used (= time slot, channel type REAL)

4 type of DLC used: REAL (0) / VIRTUAL (1)

5 number of D-channel system

Instructions

If there are several of these alarms, check the availability

of DPNSS level 2 (DLC states), and the traffic capacity of the

partner exchange.

Cancelling

No cancelling.

2.221 1562 ROUTINE TEST REPORTING FAILED

Meaning

The reporting on a routine test failed.


1 test type:

0 loop test of ECU

2 type of failed report

3 error code

Instructions

Try to output the report again by using the MML command UEO.



Cancelling

No cancelling.

2.222 1564 UNEQUIPPED CIC

Meaning

This disturbance is given when a UCIC message is received (the

destination point had not identified the CIC), or a message is

received, whose CIC the local destination point does not identify.

In case of ISUP CIC is Circuit Identification Code

In case of BICC Call Instance Code (CIC) is used instead of circuits.


1 CIC number between the signalling points

in question

2 circuit-external PCM

When a message is received whose CIC was not identified by the

local destination point, the value is FFFF

not used in BICC

3 circuit-external timeslot

When a message is received whose CIC was not identified by the

local destination point, the value is FF

not used in BICC



6 direction of the message that generated this alarm:

00 = a UCIC message is received (the destination point has

not identified the CIC)

01 = a message is received, whose CIC the local destination

point has not identified

DN70600744Issue 16-0 en


List of alarms

Instructions

If the system issues several disturbances, check that the circuit

concerned has been created at both ends.

Cancelling

No cancelling.

2.223 1569 CRITICAL LIMIT IN SECURITY REPORTINGREACHED

Meaning

The critical limit of a security reporting counter has been reached.


1 the security reporting counter that has reached its critical limit:

02 - counter for unauthorised users of service terminal

04 - counter for unauthorised users of the network

05 - counter for use of network: unauthorised commands

07 - counter for unauthorised MML users

08 - counter for unauthorised MML commands

10 - counter for unsuccessful saves in MML log file

11 - counter for unsuccessful MML command checks

12 - counter for unsuccessful subscriber identifications

13 - counter for unidentified IMSI numbers

14 - counter for IMEI IDs on black list

15 - counter for unidentified IMEI IDs

Instructions

Use the MML command IRO:<report type> to output a detailed security

report. Check, against the report, if anything out of the ordinary

has occurred, and modify, if necessary, the limit value of the counter

in question so that it reflects more accurately what is considered a

normal situation. However, if the counter's value was normal, find out

why the critical limit was exceeded.



Cancelling

No cancelling.

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


1 alarm limit of LETTER as a percentage

2 length of monitoring period in days

3 starting date of monitoring period

4 number of records in LETTER

Instructions

A certain number (indicated by the alarm limit and given as a

percentage of all records) of events have been entered in the file

during a monitoring period. A back-up copy of the file should be made,

otherwise data will be lost as new records are written over old ones.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.225 1571 CALL INDEX RESERVATION FAILED

Meaning

The call index reservation failed. If this event recurs, alarm number

2740 EXCESSIVE DISTURBANCES IN CALL INDEX RESERVATION, which contains

instructions on how to proceed if the call index reservation fails

repeatedly, is activated.


1 phase in which the call index reservation failed. The most

significant digit is always 0. The second most significant digit

refers to Diameter, the third most significant digit refers to

statistics, and the least significant digit refers to charging.

Value 0000 is not possible.

0z0y call index was received from statistics

0z1y statistics did not find a suitable index

0z2y RMAPRB or XORPRB did not receive acknowledgement from

statistics

0zx0 call index was received from charging

0zx1 charging did not find a suitable index

0zx2 RMAPRB or XORPRB did not receive acknowledgement from

charging

00xy call index was received from Diameter

01xy Diameter did not find a suitable index

02xy RMAPRB or XORPRB did not receive acknowledgement

from Diameter

0zx3 XORPRB was unable to create a hand

0zx4 RMAPRB did not receive acknowledgement from XORPRB

2 value of PRFILE parameter PERMIT_NON_CHARG_CALLS

(class 1 parameter 37)

0 calls without charging or statistics not allowed,

without Diameter allowed

1 calls without charging not allowed, without statistics

and Diameter allowed

2 calls without statistics not allowed, without charging

and Diameter allowed

3 calls allowed without statistics, charging and Diameter

4 calls without statistics allowed, without charging or

Diameter not allowed

5 calls without charging allowed, without statistics or




6 calls without charging or statistics allowed, without


7 calls without charging, statistics or Diameter not allowed

Instructions

If the PRFILE parameter 1:37 PERMIT_NON_CHARG_CALLS allows the call

setup without the call index, the call will be connected, but either

charging, statistics or Diameter will be lost for the call in

question.

If no call index is received from any of them, charging and

statistics will be lost for the call in question.

If the parameter 1:37 does not allow calls, the call setup has failed

because the call index reservation failed.

Based on additonal information you can verify whether the call was

connected or interrupted. The value of parameter PERMIT_NON_CHARG_CALLS

is read every time the call index reservation fails. Instant change

of parameter affects the situation.

Phase 111, for example, describes that the statistics and charging

have not found a free call index, and phase 002 tells that a call index

was received from the charging, but the acknowledgement for charging

has not been received on time.

Emergency calls are always connected regardless of the value of

parameter PERMIT_NON_CHARG_CALLS.

For MSC application only:

All connected calls can be seen in the functional reporting (TUF).

Following additional services are included:

CWC calls without charging

CWS calls without statistics

CWCS calls without charging and statistics

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.226 1572 SMS SUBMIT PRIMITIVE ENCODING FAILURE

Meaning

Due to use of the PNP service in the short message service, an error

occurred in the encoding of the Transfer layer Protocol Data Unit

(TPDU). The data in the TPDU contains erroneous values.


1-11 MSISDN number of subscriber A

12-15PNP index

Instructions

In connection with this alarm, the system writes an entry containing

the TDPU to the logfile.


Cancelling

No cancelling.

2.227 1573 CONFLICT WITH DEFINED DIRECTION OFCIRCUIT/CIC

Meaning

The system issues this disturbance if the partner exchange handles the

circuit to the wrong direction.

In case of BICC Call Instance Code (CIC) is used instead of circuits.




1 error code

01 received initial address message

02 received blocking/unblocking message


(if the SIO is not CCS, the value is FF)



5 number of circuits in the circuit group


Instructions

Check the direction data of the circuit with the MML command RCI.

Cancelling

No cancelling.

2.228 1574 DATA ERROR FOUND BY PROTOCOL

Meaning

A network element has received an operation or an acknowledgement for

it from another network element, and a parameter required in this

situation is missing, or the parameter received contains an erroneous

value.

The error situation has no direct effect on charging or announcements.


1 error code. It can have the following values:

MAP protocol:

DN70600744Issue 16-0 en


List of alarms

23 Data Missing

24 Unexpected Data Value

INAP protocol:

07 Missing parameter

0F Unexpected Data Value

2 operation code. It indicates the operation in which the error

situation occurred.

3 remote end's subsystem number. If the number is unknown or

unnecessary, the number of the subsystem is set at zero (0).

4-15 remote end's address. The type of the address is indicated first:

00 Global title

01 Network indicator and signalling point code address

After the address type comes either the global title, or network

indicator and the signalling point code address. If the

address is unknown or unnecessary, the fields are filled with

zeros (0)

Instructions

Using the log files received by the CCSU computer unit, and the data

contained in the cyclic buffer of the protocol (MML command OPO/OEO),

find out the reason for the rejection of the data.

Cancelling

No cancelling.

2.229 1575 COMPONENT NOT ACCEPTED BY REMOTEEND

Meaning

Two network elements are incompatible with each other.

This disturbance is used in a situation where a network element

has sent an operation to another network element, but the latter

does not accept the operation because:

- a mandatory parameter is missing in the operation, or



- one of the operation parameters has an erroneous value.


announcements.


1 error code. It can have the following values:

MAP protocol:

23 Data Missing

24 Unexpected Data Value

INAP protocol:

07 Missing Parameter

0F Unexpected Data Value

2 operation code. It indicates the operation in which the error

situation occurred

3 remote end's subsystem number. If the number is unknown or

unnecessary, the subsystem number is set at zero (0)

4-15 remote end's address. The type of the address is indicated first:

00 Global title



network indicator and the signalling point code address.

If the address is unknown or unnecessary, the fields are

filled with zeroes (0)

Instructions

The remote end has not accepted the operation sent to it.

Find out the reason for this in the network element which failed

to accept the operation.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.230 1576 ERROR IN TIME CHARGING INTERFACE

Meaning

Call control sends TIMCHA a request, asking it to start call-specific

time charging, but for some reason TIMCHA answers with an error code or

does not answer at all. Call control is unable to start, interrupt or

stop the charging.


1 activity that caused the failure:

0 = start of charging

1 = end of charging

2 = interruption of charging

3 = continuation of charging

4 = intermediate charging

5 = transmission of pulses received from the circuit

6 = reception of charging data

2 type of the error:

1 = TIMCHA does not reply; the time supervision has expired

2 = TIMCHA replies with an error code

Instructions

Check the log of the unit and contact the local Nokia Siemens Networks


Cancelling

No cancelling.



2.231 1577 SMS: NO RESPONSE FROM CO PROCESS

Meaning

In connection with the short message service, no acknowledgement is

received to the start-up message sent by the SMHPRB, or the SMHPRB

received the process identifier and sent a message to the process

corresponding to the identifier, but received no acknowledgement to it.


1 short message type and exchange type specified in the short

message service:

mobile-terminating, VMSC = 01

mobile-terminating, GMSC = 02

mobile-originating, VMSC = 03

mobile-originating, IWMSC = 04

2 process identification to the process which does not send an

acknowledgement

Instructions


Cancelling

No cancelling.

2.232 1579 UNRELEASED CALL BECAUSE OF DELAYEDRELEASE (DRS)

Meaning

The system issues this disturbance when the call is being held according

to the 'delayed release' signalling procedure. In this case, the

release of the outgoing circuit is the task of the address switch.

DN70600744Issue 16-0 en


List of alarms


1 reason for using the delayed release message

01 delayed release was requested

02 DRS message was received from the incoming side

03 CCS system is not in use in all sections of the

connection <option>

04 malicious call tracing was requested <option>

2 statistical identification of the call identifier

3 charging identification of the call identifier

4 computer identification of the call identifier

5 process identification of the call identifier

6 focus of the call identifier

7 unreleased PCM circuit

8 unreleased timeslot

Instructions


Cancelling

No cancelling.

2.233 1581 NO CIC RECEIVED FROM BSC

Meaning

No circuit identification code (CIC) has been received from the BSC

while reverse hunting is used.




1 the signalling point code of the Base Station Controller in

question

2 the SCCP service information octet of the Base Station

Controller

3 message type:

4FH: change_circuit_ack_c

12H: handover_request_ack_c

02H: assignment_complete_c

Instructions

The support of the reverse hunting needs to be checked for both network

elements (MSC and BSC). For the MSC the MML command ZEDO can be used.

Correct the inconsistent specifications.

Cancelling

No cancelling.

2.234 1583 LAPD MSG DISTRIBUTION PROBLEM

Meaning

The PXRECE (Primary Rate Access Receiving Program Block) has

received messages from the D-channel, but it has not been able

to route the messages forward. The reason for this can be that

the message received from the LAPD link is erroneous. The error

situation is not a serious one, but if there are several consecutive

alarms with the same D-channel system identifier, there may be an

error in the PXRECE distribution table or a disturbance in the

LAPD link.

DN70600744Issue 16-0 en


List of alarms


1 identification of the D-channel system

(hexadecimal number)

2 identification of the D-channel system

(name)

Instructions

Use the MML command AHP to check other alarms concerning the same

unit for a period of approximately one hour before this alarm

occurred. If the other alarms do not indicate a link fault and

if there are BCF/TRX links created under the link identification

mentioned in this alarm, the fault is in the PXRECE distribution

table. To correct the situation, you can perform a switchover in

the unit that set the alarm by using the MML command USC.

The switchover updates the PXRECE distribution table.

Cancelling

No cancelling.

2.235 1584 SCCP MESSAGE ROUTING ERROR

Meaning

Sending connectionless SCCP messages failed.


1 identifier of the network where the signalling point is located

00: IN0, international network 0

04: IN1, international network 1

08: NA0, national network 0

0C: NA1, national network 1

2 signalling point

3 number of the subsystem

05: MAP



06: MAP-HLR

07: MAP-VLR

08: MAP-MSC

09: MAP-EIR

0A: MAP-reserve

FE: BSSAP

4 diagnosis

00: no translation for the nature of address in question

01: no translation for the address in question

02: subsystem is in congestion state

03: failure in the subsystem

04: unequipped user

05: network failure

06: network is in congestion state

07: unspecified

08 - FF spare

Instructions

Check the local distribution specifications of the SCCP with the MML

command NBO. If necessary, add them with the MML command NBC.

Cancelling

No cancelling.

2.236 1586 BTA TUP RELEASE ACKNOWLEDGEMENTMISSING

Meaning

The system issues this disturbance if, in spite of renewed attempts,

no acknowledgement has been received for a release message from the

partner exchange. After this disturbance, the circuit in question is

barred from hunting.


1 title code of the missing release acknowledgement

17 RLG (release-guard signal)

46 CLF (clear-forward signal)

DN70600744Issue 16-0 en


List of alarms


84 (TUP, national toll network)

C4 (TUP, national local network)


4 PCM circuit in which the fault was noticed

5 timeslot in which the fault was noticed

0-31

Instructions

Move the faulty circuit into down state (NU-US) by giving the MML

command CEC. You can reactivate the circuit by moving it through

SE-US state into WO-EX state.

Cancelling

No cancelling.

2.237 1590 ALARM SYSTEM MESSAGE SENDINGBUFFER FULL

Meaning

A buffer that is used to supervise the alarm system's message

traffic requiring acknowledgements is full. Such buffers are

used for the collection of history data of both the alarm system's

distributed and centralised part, as well as for communication

between the distributed and centralised parts.

The saturation of the buffer that collects history data may

cause the loss of some such data.

The saturation of the buffer that is used for communication

between the two parts (distributed and centralised) may cause

an imbalance between the centralised part of the alarm system

and the distributed part that is sending. This may lead to the

loss of some of the set values and cancellations of the alarms.




1 type of buffer

01 communication buffer

02 history buffer

2 family identifier of the sender

3 process identifier of the sender

4 type of the receiver's computer unit

See Recovery and Unit Working State Administration.

5 index of the receiver's computer unit

6 family identifier of the receiver

7 process identifier of the receiver

Instructions


Cancelling

No cancelling.

2.238 1595 NEMU ALARM BUFFER OVERFLOWOCCURRED

Meaning

A buffer that is used to collect NEMU unit alarms is full.

Due to the saturation of this NEMU alarm buffer the buffer

has reinitialised. Some NEMU alarms may have been lost.


DN70600744Issue 16-0 en


List of alarms

Instructions


Cancelling

No cancelling.

2.239 1597 I/O DEVICE FOUND FAULTY BY ALARMSYSTEM

Meaning

The alarm system has found, having received several

different observations to that effect, that the I/O

device is defective.

The I/O system has been informed of the fault in the device.


1 type of subobject (of the I/O device) suspected faulty

FFFF, subobject not specified

2 index of subobject (of the I/O device) suspected faulty


3-8 the alarm manual numbers (in BCD format) of the observations

that first supported the fault hypothesis

Instructions


Cancelling

No cancelling.



2.240 1598 UNIT FOUND FAULTY BY ALARM SYSTEM

Meaning

The alarm system has found, having received several different

observations to that effect, that a functional unit

(not the I/O device) is defective.

The recovery system has been informed of the faulty unit.


1 type of subobject (of a functional unit) suspected faulty


2 index of subobject (of a functional unit) suspected faulty


3-8 the alarm manual numbers (in BCD format) of the

observations that first supported the fault hypothesis

Instructions


Cancelling

No cancelling.

2.241 1621 ERROR IN FILE ACCESS

Meaning

The file reading or writing has failed: no PCM circuit is found in

the PCM configuration file (PCMCON) for the unit to be tested. No

signalling mode with which the test could be performed can be found

in the signal control file (CNTROL).

DN70600744Issue 16-0 en


List of alarms


1 file specification

01 unit identifier file error

02 signal control file error

Instructions


Cancelling

No cancelling.

2.242 1623 ERROR DURING SUPERVISION

Meaning

Unit type supervision has been interrupted because the Subscriber

Module Testing Program Block (SBTSTP) or the Time Slot Based Unit Test

Program Block (TSUPRO) is constantly reserved, or the Message Transfer

and Switching Service Program Block (MTSWIS) cannot seize the unit

to be tested, or the Test Line Management Program Block (LTMANA) is

unable to reserve the SUB-E minimeter. The supervision of the unit is

interrupted because the requested task is incorrect, or because no test

result is obtained for the requested test.


1 program block:

0060 LTMANA_P

0064 TSUPRO_P

0065 SBTSTP_P

0067 MTSWIS_P

2 error specification:

01 unit type supervision is interrupted

02 supervision of single unit is interrupted



Instructions


Cancelling

No cancelling.

2.243 1630 RAM FAILURE IN SYNCHRONIZATION UNIT

Meaning

A failure has been detected in the RAM memory of the synchronization

unit.


Instructions

Set the unit into test state. Run the diagnostics and replace

the plug-in unit if necessary.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.244 1642 CIRCUIT/CIC BARRED OVER 5 MIN

Meaning

The barring state of one or more PCM trunk circuits has lasted more

than 5 minutes.

In case of BICC Call Instance Code is used instead of circuits


1 error code

01 barring by management command of a single trunk circuit

has lasted more than 5 minutes

02 barring by management command of several trunk circuits


FF not enough information for setting other error code




5 the amount of circuits in a circuit group


Instructions

Move the PCM circuit into down state. You can interrogate the state

of the circuits with the MML command RCI, and change their state

with the MML command CEC.

Cancelling

No cancelling.



2.245 1643 CIRCUIT/CIC BLOCKED OVER 5 MIN

Meaning

One or more PCM trunk circuits have been blocked for more than 5 minutes.

In case of BICC Call Instance Code is used instead of circuits.


1 error code

01 blocking by management command of a single trunk circuit


02 blocking by management command of several trunk circuits


FF not enough information for setting other error code




5 the amount of circuits in a circuit group


Instructions

Move the PCM circuit into down state. You can interrogate the state of

the circuits with the MML command RCI, and change their state with the

MML command CEC.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.246 1644 PROTOCOL MEASUREMENT REPORTTRANSFER UNSUCCESFUL

Meaning

The MAP statistics, INAP statistics, CAP statistics,

SSAP statistics or SRR statistics has failed to transfer

all the measurement records to RFGPRB.


1 type of the protocol that was not able to transfer the data

to the report forming program block (INAP, CAP, MAP, SSAP,

GYUJTO)

2 the total amount of measurement records included in short

term counters

3 the amount of records, which were not transferred when the safety

time reserved for the transfer was exceeded

MAP statistic transfers the rest of the records after twenty-four

hours. The time stamps of delayed records are, correspondingly,

twenty-four hours longer

This field is relevant only in the MAP statistics. In case of

INAP, SSAP or CAP statistics, the value is always 0

4 the amount of records whose transfer succeeded partly, e.g. transfer

to OMC succeeded but the binary format failed. These records will

not be retransferred

Instructions

MAP statistics:

If you wish to interrupt the transfer of delayed records, or any

transfer, you can stop the short term measurement by giving the MML

command

ZOXE:S...

You can increase the time used for sending with the MML command

ZOXS:S::TEXT=Y,DUR=<time in hours>;

INAP statistics:

If you wish to interrupt the transfer of records, you can stop the

short term measurement by giving the MML command

ZOAE:S...



Cancelling

No cancelling.

2.247 1645 PROTOCOL MESSAGE QUEUE FULL

Meaning

A protocol has rejected a service request because of an overload

situation in the unit.


1 00 event activated in the network was rejected

01 event activated by an own network element was rejected

Instructions


Cancelling

No cancelling.

2.248 1646 PROTOCOL INTERNAL ERROR

Meaning

A protocol has rejected a service request sent by the user because of

the user's erroneous action, or the protocol software has detected an

internal error.

DN70600744Issue 16-0 en


List of alarms


1 cause of error:

00 TCAP has given a notice about running out of its

operation automatons

01 TCAP has not accepted the message sent by the protocol

02 the protocol notices an error in the message sent by the user

03 error in overload control initialization

04 error in overload control use

05 error in the protocol version control

06 error in signing in for SCCP distribution

07 error in SCCP address handling

2-16 this field is used if the first field has the value 01.

The first two bytes give the reason why TCAP did not accept

the message sent by the protocol. The cause is coded so that the

least significant byte of the code is at the beginning

25 unidentified primitive

27 rejection in the wrong operating state

28 user requests the sending of End message

although the remote end has not sent messages

29 Invoke ID of Cancel primitive is not in use

2B incorrect length of the element

2C SCCP address is too long

2E TCAP message is too long

32 TCAP use is not allowed

34 error in missing impulses

3A application context error

3B parameter error in tc2 message

A6 hand and transaction freed

1A6 hand freed

Instructions


Cancelling

No cancelling.



2.249 1647 OPERATION TIMER EXPIRY

Meaning

An operation has been sent to the network, but an

acknowledgement to it has not been received fast enough.

As a result of this error situation, the ongoing dialogue is

interrupted. The effect on the functioning of the system and

on the service received by the subscriber depends on the

operation in question.

This disturbance can indicate a routing problem, or

congestion in the network element to which the operation

was sent.


announcements.



causing the alarm is related to

2 remote end's subsystem number

3-14 remote end's address where the message was being sent to

the type of the address is indicated first:

00 Global title



the network indicator and signalling point code address.

The structure of the global title :

1. byte : address length (amount of numbers)

2. byte : numbering plan of the address and type of the

number. This data has been coded according to

GSM 09.02 recommendation. The most common

values are 91 (E.164/INT), A1 (E.164/NAT) and

97 (E.214/INT).

3..12 : numbers of the address in compressed form, two

numbers per byte

DN70600744Issue 16-0 en


List of alarms

Instructions

If the address in the third field is in the form of a global

address, find out the global address translation for the

address in question and for the network element's own address

(MML commands ZNA and ZNB).

If the address in the third field is in the form of a network

indicator and signalling point code address, find out the

state of the signalling network (MML commands ZNH and ZNL).

Find out if the point code in question is known, if there is

a signalling connection with the remote end, and if

signalling links and subsystems are active.

Cancelling

No cancelling.

2.250 1648 CONFLICT IN MESSAGE PROTOCOL

Meaning

The hand of the program block has received a message, which is identified

and usable, in the wrong phase of the call.


1 the type of the received message in ascii characters as shown

below:

ISUP : eg. iam, cgb, cgba, blo, bla ...

In case the message in unknown, or the program block does not

have an ascii name list, it is presented as a hexadecimal number

2 signalling point code of the partner exchange


4 PCM circuit

5 timeslot



Instructions


Cancelling

No cancelling.

2.251 1651 DECODING ERROR OF THE A-INTERFACEBSSMAP-MESSAGE

Meaning

The purpose of this alarm is to notify the user about a BSSMAP-message

which was received from the BSC and could not be decoded.


1 signalling point code of the base station controller

2 SCCP service information octet of the base station controller

3 BSSMAP cause code

4 type of the faulty message

5 internal automaton reference

6 internal state reference

7 reference to the work file into which the faulty message

is written

8 index of the work file into which the faulty message has

been written

Instructions


DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.252 1652 DECODING ERROR OF THE MESSAGERECEIVED FROM THE MS

Meaning

The purpose of this alarm is to notify the user about a message which

was received from the MS and could not be decoded.


1 protocol discriminator field showing the transaction type

(MM, CC, SS, SMS)

2 IMEI (International Mobile station Equipment Identity) of the

mobile which had sent the faulty message

3 message type of the faulty message

4 internal automaton reference

5 internal state reference

6 reference to the workfile into which the faulty message

is written

7 index of the workfile into which the faulty message has

been written

Instructions


Cancelling

No cancelling.



2.253 1653 THE A-INTERFACE BSSMAP-LEVEL TIMEREXPIRY

Meaning

The purpose of this alarm is to notify the user of the BSSMAP

timer expiry in the MSC.




3 BSSMAP cause code

4 index of the expired timer in the BPAFIL file

5 duration of the timer

Instructions

Check the state of the BSC in question and the BSSAP version (ZEDO).

Check the value of the timer in question in the BPAFIL file from a

record that corresponds to the BSSAP version (ZED).

Cancelling

No cancelling.

2.254 1654 BSSMAP MESSAGE CONFUSION RECEIVEDFROM BSC

Meaning

The purpose of this alarm is to notify the user of a CONFUSION message

which was received from the BSC and which is an indication of a faulty

message sent by the MSC.

DN70600744Issue 16-0 en


List of alarms




3 BSSMAP cause code

4 type of the message mentioned in the CONFUSION message

5 reference to the work file into which the faulty message

is written

6 index of the work file into which the faulty message was

written

Instructions


Cancelling

No cancelling.

2.255 1657 TOO MANY EXECUTED SUBANALYSES INATTRIBUTE ANALYSIS

Meaning

More than the allowed number of subanalyses of the attribute analysis

have been executed. Too many consecutive subanalyses may weaken the

performance of the exchange. The call set-up continues normally.


1 type of the attribute analysis:

1 = charging attribute analysis

2 = EOS attribute analysis

3 = routing attribute analysis

4 = A-interface attribute analysis for mobile-originating

(MO) calls



5 = A-interface attribute analysis for mobile-terminating

(MT) calls

2 in attribute analysis, the name in text format of the subanalysis

whose execution caused the counter showing the number of subanalyses

to be executed to overflow

3 of the two sides of the subanalysis, the one whose execution

caused the counter showing the number of subanalyses to be

executed to overflow


1 = testside of the subanalysis

Instructions


with a smaller amount of subanalyses. The number of subanalyses to


"MAX_ATB_SUBANA_NBR" (identifier: 047) to be output with the MML

command WOI:7; shows.

The value of parameter MAX_ATB_SUBANA_NBR shows the maximum amount

of subanalyses to be executed in the attribute analysis. This maximum

number should not yet weaken the performance of the exchange too much.

The operator can check the attribute analysis chain starting from the

subanalysis whose execution caused the disturbance. For more

information, see the feature activation instructions of the

Feature 597: Routing Based on Origin Attributes and Feature 519:

A-interface Priority Information Control.

The operator can make the decision about modifying the attribute

analysis.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.256 1658 NOT ENOUGH DIGITS IN CALLED NUMBERFOR ATTRIBUTE ANALYSIS

Meaning

There are not enough digits in the called number for the execution

of the attribute analysis. If the called number is shorter than the

number which the user had defined in the subanalysis in question,

the call will be cleared in all other attribute analyses except

the following:

- A-interface attribute analysis for mobile originating (MO) calls

- A-interface attribute analysis for mobile terminating (MT) calls.

In these cases the call set-up continues in the normal way, and the

analysis result does not affect the call.


1 type of attribute analysis:

1 = charging attribute analysis

2 = EOS attribute analysis

3 = routing attribute analysis

4 = A-interface attribute analysis for MO calls

5 = A-interface attribute analysis for MT calls

2 in attribute analysis, the name in text format of the subanalysis

in which the operator has defined more digits than can be analysed

for the attribute corresponding to the number of the subscriber

3 of the two sides of the subanalysis, the one whose execution caused

the alarm to be set



Instructions

Check if the action is desired in the attribute analysis subanalysis

which was output in the alarm.

For more information, see the feature activation instructions of the

Feature 597: Routing Based on Origin Attributes and Feature 519:

A-interface Priority Information Control.



Cancelling

No cancelling.

2.257 1660 UPDATE NUMBER MISMATCH

Meaning

The LOGSAV, a hand of the database management system, has sent

the DBSMAN an update, the number of which (update_seq_number) is

inconsistent with the DBSMAN's view of what that number should be.

One or the other of the processes has failed and may have lost log

buffers. The DBSMAN will now no longer receive log buffers from the

database in question, and the database will be dumped, i.e. it is

copied from RAM to the disk, thus correcting the failure automatically.







2 database name

3 number of database occurence

4 database location

5 family ID of the program block handling the database

Instructions

The system corrects the fault automatically. If the disturbance keeps

recurring, save the log files of the database unit and the disk

updating system unit and the alarms, and contact your local Nokia


DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.258 1661 DATABASE MANAGER IN FATAL ERRORSTATE

Meaning

An error occurred in the database management system, and the

system has been set to the "fatal error" state. In the "fatal

error" state, the management system program block acknowledges

supervision messages negatively. As the program block is a critical

one, the system resets the database unit.







2 database name


4 error code indicating the reason why the fatal error

state was entered. You can check its meaning in General Error

Messages of System

Instructions

Save the log of the database unit, or, alternatively, save the black

box of the unit after the reset for further investigation.

Cancelling

No cancelling.



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


1 database index (some database applications still need

this information, although the database is usually

identified based on the database name and


2 database name


4 reason for load failure

01 the disk updating system (DBSMAN program block) does

not answer when the DBMANA on the WO side asks for

permission to load

02 the DBMANA on the WO side does not answer when the

DBMANA on the SP side asks for permission to load

03 time supervision expires on the WO side of the database

unit during the first load attempt

04 time supervision expires on the SP side of the database

unit during the first load attempt

Instructions

Reason = 01: Check with the DBD command the state of the disk

updating system serving the database.

Reason = 02: Check with the DBS command the state of the

management system in the database unit's WO side.

Reason = 03: Check with the DBD command the state of the disk

updating system serving the database. Check with the DBS command

the state of the management system on the database unit's WO side.

Save the log of the database unit's WO side, or,

alternatively, save the unit's black box after a reset. Save

the log of the disk update system.

Reason = 04: Check with the DBS command the state of the

management system on the database unit's WO and SP side.

DN70600744Issue 16-0 en


List of alarms

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.

Cancelling

No cancelling.

2.260 1663 HAND RESERVATION ERROR IN DATABASEMANAGER

Meaning

The reservation of a transaction or fastread hand fails in

the database management system.







2 database name


4 error code indicating why the hand reservation failed.

You can check its meaning in General Error Messages of

System

5 number of the transaction or fastread hand to be reserved:

00 if on WO side

> 03 if on SP side (the number of the hand to be reserved

is known)

Instructions

Check the states of the database management system's hands by means of

the service terminal extension Family Utilities (FAMUTI).






Cancelling

No cancelling.

2.261 1664 ERROR IN DATABASE SYSTEM

Meaning

An error has occurred in the database management system during the

operation of a database procedure.


1 identifier of the database family

2 computer unit in which the database is located

3 error code indicating the reason of the disturbance.


of System.

Instructions

Save the log of the database unit.

Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.262 1667 UNHANDLED MESSAGES OVERFLOW

Meaning

A service request has been rejected due to the overflow of unhandled

messages.


1 number of the rejected service request

Instructions


Cancelling

No cancelling.

2.263 1682 SCDFLE UPDATE FAILURE

Meaning

The distribution or updating of the Working State and Configuration

File (SCDFLE) has failed.


1 error code presented as a common error code. You can check its

meaning with a command of the service terminal extension MRS or in

the General Error Messages of System

2 consecutive number of distribution

3 recovery action

4 type of the unit whose data was changed



5 index of the unit whose data was changed

6 number of SCDFLE record

Instructions


Cancelling

No cancelling.

2.264 1683 FAULTY UNIT SP-EX

Meaning

A faulty unit is spare.


Instructions





Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.265 1684 SPARE UNIT WARMUP FAILURE

Meaning

The warm-up of the spare unit fails. The reason may be a fault

in the active or in the passive unit. The alarm is issued from

both units.


1 family identifier of the alarm detector

2 error code returned by the alarm detector.

You can check its meaning with a command of the

service terminal extension MRS or in General Error

Messages of System, Supplementary References

3 message bus address of the unit where the error

occurred

4 family identifier of the program block that made the

error

5 load group where the warming failed

6 file where the warming failed

Instructions





Cancelling

No cancelling.



2.266 1685 UNIT RESTART FAILURE

Meaning

The restarting of the computer unit fails.


1 family identifier of the error detector

2 error code returned by the error detector.

You can check its meaning with a commands of the service terminal

extension MRS or in General Error Messages of System, Supplementary

References



5 load group where the loading failed

6 file where the loading failed

Instructions





Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.267 1687 RECOVERY ACTION FAILURE

Meaning

The recovery actions in the unit have been interrupted or a subfunction

of a recovery action has failed. The partner program block in the

object unit has not responded, or it has returned an error status.


1 error code of recovery action.


extension MRS or in General Error Messages of System,

Supplementary References

2 interrupted recovery action

3 family identifier of the error detector

4 error code returned by the error detector.


extension MRS or in General Error Messages of System, Supplementary

References



Instructions


Cancelling

No cancelling.



2.268 1688 FAILURE IN CALL CLEARING

Meaning

A clear request sent to release the calls of the time-slot-based

unit such as the SUB, CNFC, ET, etc. has not been acknowledged.


1 type of time-slot-based unit

See Recovery and Unit Working State Administration.

2 unit index

3 partner program block

Instructions

Check if the above-mentioned units have made seizures for calls.

If so, release them.

Cancelling

No cancelling.

2.269 1800 SCSI ADDRESS ILLEGAL

Meaning

There was an attempt to install an I/O device at an SCSI address

that was already reserved.


1 number of SCSI bus

0...1

2 address of device on bus identified in field 1

DN70600744Issue 16-0 en


List of alarms

0...7

3 logical unit number (= LUN)

0...7

the LUN of the master tape drive is always 0, numbers 1...7 are

slave tape drivers

Instructions

Check the SCSI bus addresses of the I/O devices on the SCSI bus.

If the alarm occurs in connection with the configuration of the tape

units, check the parameters of the ISK command.

Cancelling

No cancelling.

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


1 name identification of the failed copy task.

The name is an ASCII string

2 number identification of the failed copy task.

The number is a hexadecimal number generated by the I/O system.

The name and the number of the task form an explicit identifier



Instructions

Check the backup copy log to see which copy task failed. Use

the MML commands IPI and IPP to interrogate the log of the copy

task in question. Give the copy task name and identification number

(shown in Supplementary information fields 1 and 2) as parameters.

For example, if the name of the task is COPY_1998 and the

identification number is 40020010, the following command outputs

the general copy task information:

IPI:NAME=COPY_1998,HANDLE=40020010;

The IPP command displays detailed information on the copied files

and directories. If copying a file failed, the printout shows a

general error message after the file or directory in question.

IPP:NAME=COPY_1998,HANDLE=40020010;

Cancelling

No cancelling.

2.271 1802 BACKUP COPY LOG FAILURE

Meaning

Saving the copy task information in the disk's copy log has failed

at least partly.

The fault may have been caused, for example, by a disturbance in the

I/O system, a fault in an I/O device, or a load peak of the unit,

because of which information could not be recorded within the

defined time period.

If alarm 1801, MASS MEMORY FILE BACKUP FAILURE, is set simultaneously

with this alarm, the background processing of the backup copy task

has been interrupted. Otherwise, the copy task itself has succeeded

but the system was not able to record all the information connected

to the copy task to the copy log.

This alarm has no effect on the operation of the rest of the system.

If disk alarms are set simultaneously with this alarm, a disturbance

or a fault has been detected in the disk system and it has prevented

DN70600744Issue 16-0 en


List of alarms

the normal use of the copy log. The following alarms are disk alarms:

0860 DISK NOTICE, 1860 DISK DISTURBANCE, 2860 DISK FAILURE,

2861 NO ACCESS TO DISK, and 2862 DISK CHECKSUM ERROR.


1 general error message of the system. You can check its meaning


2 name identifier of the copy task whose recording in the copy log

failed. The name is an ASCII string

Instructions

It may be possible to interrogate information on the copy task

mentioned in Supplementary information field 2 with the MML commands

IPI and IPP. The I/O system has however failed to record some (or

possibly all) information.

You may find more information in the system log, which you can

interrogate with the service terminal command ZGD.

If alarm 1801, MASS MEMORY FILE BACKUP FAILURE, is not set

simultaneously with this alarm for the same copy task, the copy

task was successful, even though information on it is not available

in the log.

If alarm 1801 is also set, you should start the copy task again.

Cancelling

No cancelling.

2.272 1804 IP ROUTING RESOURCE SHORTAGE

Meaning

The IP Routing feature is experiencing an unexpected resource

shortage.

The IP routing capability of the system is temporarily reduced

until the routing database has been reconstructed from neighboring



routers.

The telephony capabilities of the switch are not affected.


Instructions


Center.

Cancelling

No cancelling.

2.273 1806 PRINTER SPOOLER DISABLED

Meaning

Printing system cannot use the spooler. This happens, for example,

when the SCSI-bus or hard disks go to TEST-state. The failure does

not disable the printing system, but new printing tasks are handled

in non-spoolered mode. Handling printing tasks in non-spoolered mode is

more unreliable than in spoolered mode.

The tasks that are in spooler when failure occurs, are executed

when the spooler is in use again. The system changes automatically from

the non-spoolered mode to the spoolered mode when the spooler is

again in use and all non-spoolered tasks are completed.


Instructions

To find out the reason for SCSI-bus's or hard disk's wrong operating

state, check whether there are other alarms active using the AHO MML

command. Follow the instructions given in these alarm descriptions.

DN70600744Issue 16-0 en


List of alarms

Set the SCSI-bus and hard disks to WO-state using the ISC MML command, if

possible.

Cancelling

No cancelling.

2.274 1809 IP CONFIGURATION INQUIRY SERVICEFAILED

Meaning

The alarm is set if IP management shared library (YANLIB) cannot

provide IP configuration inquiry services for applications.

Under this situation, the applications will get "no service" return

code when calling the library routines. If the application has failed

to receive IP configuration data, it might make the Network Element

unable to provide IP calls services.


Instructions

Check the computer log to find out the possible cause of the alarm.


Service Center.

Here are the possible problems:

1. IP configuration files (etc/if.dat or /LFILES/YEMIP6GX.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, report that too to the problem report.

2. Read/write disk files failed:

Add both operating and user logs to the problem report.

3. Allocate common buffer failed:



Add both operating and user logs to the problem report.

4. Event Forwarder problem:

Add user logs to the problem report.

5. Name Server problem:

Add user logs to the problem report.

Cancelling

No cancelling.

2.275 1810 NEMU TRIGGERED PROCESS SANITYCHECK FAILED

Meaning

All NEMU processes are monitored continuously whether they are

functioning properly or not. The state of each process is checked

periodically. The purpose of this disturbance type alarm is to notify

that a triggered process has failed the sanity check and is therefore not

working as expected. The process will be shut down.


1 name of the malfunctioning process

Instructions

The alarm requires no actions. Process recovery is done automatically.

If the process persists in failing, see document 'Network Element

Management Unit (NEMU)' for how to fix the problem and if that does not

provide a solution, contact the local Nokia Customer Service Center.

DN70600744Issue 16-0 en


List of alarms

Cancelling

No cancelling.

2.276 1811 NEMU MANAGEMENT SERVICE STARTFAILURE

Meaning

Starting of a new management service in NEMU has failed.


1 the number of the session in format:

Nwi3ManagementSessionSrv-<session_id>

(example: Nwi3ManagementSessionSrv-23)

Instructions

The error can be caused by many different reasons (out of memory, load is

too high, and so on).

Try to find out the reason for the error:

1. Log in to Nemu as a local user (use Netop or local terminal).

2. Start Windows Event Viewer with Start - Run - eventvwr.

3. Check 'Nemu Error' events in Application Log and system events in

System Log.

If the problem persists, see document 'Network Element Management Unit

(NEMU)' for how to fix the problem and if that does not provide a

solution, contact the local Nokia Customer Service Center.

Cancelling

No cancelling.



2.277 1812 NEMU EMT CONNECTION COULD NOT BEOPENED

Meaning

New EMT connection could not be opened from NEMU to the network element.


1 IP address of the network element, which could not be connected

Instructions

The error can be caused by many different reasons (Network failure,

configuration error, for example a faulty IP address, out of memory, load

is too high, Network element reset or any network related failure in the

network element and so on).

See document 'Network Element Management Unit (NEMU)' for how to fix the

problem and if that does not provide a solution, contact the local Nokia


Cancelling

No cancelling.

2.278 1813 NEMU SESSION START FAILURE

Meaning

Starting a new session in NEMU has failed when executing login operation.


1 the IP address of the client requesting a new session

DN70600744Issue 16-0 en


List of alarms

Instructions

The error can be caused by many different reasons (out of memory, load is

too high, and so on).


1. Log in to NEMU as a local user (use Netop or local terminal).

2. Start Windows Event Viewer with Start - Run - eventvwr.

3. Check 'Nemu Error' events in Application Log and system events in

System Log.




Cancelling

No cancelling.

2.279 1814 NEMU FTP CONNECTION COULD NOT BEOPENED

Meaning

Starting a new FTP connection has failed.


1 the remote IP address of the failed FTP connection attempt

Instructions

The error can be caused by many different reasons (configuration error,

for example a faulty IP address, out of memory, load is too high, and

so on).


1. Log in to NEMU with Nokia Application Launcher.

2. Start EM Action Log Viewer.

3. Check 'Nemu Error' and 'Nemu Security' events.






Cancelling

No cancelling.

2.280 1815 NEMU TELNET CONNECTION COULD NOTBE OPENED

Meaning

Starting a new Telnet connection has failed.


1 the remote IP address of the failed Telnet connection attempt

Instructions

The error can be caused by many different reasons (configuration error,

for example a faulty IP address, out of memory, load is too high, and so

on).


1. Log in to NEMU with Nokia Application Launcher.

2. Start EM Action Log Viewer.

3. Check 'Nemu Error' and 'Nemu Security' events.




Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.281 1860 DISK DISTURBANCE

Meaning

A disturbance has been detected in the Winchester or floppy disk

system. The disturbance may be caused by a DMADI, DMASI, or SCSIF

plug-in unit, the connecting cable, disk controller, disk drive,

or by a command that is incorrect, insufficient or unnecessary.


1 general error message of the system. You can check its

meaning in General Error Messages of System

2 address of the damaged sector of the disk drive,

if 1FFFFFH, the sector address is not valid

3 first 8 characters of file name

Instructions

Check the command. Remove write protection from the floppy disk.

Check and replace, if needed, the DMADI, DMASI, or SCSIF plug-in

units, connecting cable, disk controller and disk drive or floppy

disk.

Cancelling

No cancelling.

2.282 1881 TAPI FAILURE

Meaning

Before giving a command concerning the magnetic tape drive,

or when making a state inquiry, TAPEDR checks the functioning

of the TAPI plug-in unit. If an error is detected, this alarm

is issued.




Instructions


Cancelling

No cancelling.

2.283 1882 DMADI FAILURE

Meaning

Before read or write operations TAPEDR checks the functioning of

the address and byte counters of the DMA channel it uses. If a

failure is detected in the operation, this alarm is issued.


Instructions


Cancelling

No cancelling.

DN70600744Issue 16-0 en


List of alarms

2.284 1884 LABEL PARAMETER FAILURE

Meaning

If no label parameters have been defined for TAPEDR in connection

with the preformatting or opening command, TAPEDR tries to use the

old parameters stored in the data area. This always entails a

correctness test based on the check sum. If an error is detected,

TAPEDR fetches the constant values and uses them. At the same time,

the system issues this alarm.


1 number of the magnetic tape unit

Instructions


Cancelling

No cancelling.

2.285 1885 ERROR IN WRITING DATA TO MAGNETICTAPE

Meaning

The error message is a consequence of a failure in the magnetic tape

unit, very poor condition of the tape, a serious malfunction in

the controlling plug-in units (TAPI, DMADI, SCSIF), or erroneous

task parameters sent by the application.



2 general error message of the system. You can check its meaning




3 block number

Instructions

Determine (from the error code) whether the cause of the disturbance

is poor tape quality, equipment failure or an erroneous task parameter.

The alarm supports the activation of the automatic recovery for the

object unit. You can check the supporting amount of the alarm with

the MML command ARO.

If the magnetic tape unit has been changed into test state for recovery,

find out the cause of the failure and remove the cause before returning

the magnetic tape unit into normal working state (WO-BU). The state can

be changed with the MML command ISC.

Cancelling

No cancelling.

2.286 1886 ERROR IN TAPE OPERATION

Meaning

This is an error acknowledgement to some other command than the

write command. The fault is in the equipment or in the storage medium.



2 general error code. You can check its meaning in General Error

Messages of System

DN70600744Issue 16-0 en


List of alarms

Instructions

If the error code does not clearly indicate that the fault is

in the equipment, change the storage medium. If this does not

solve the problem, an inspection of the equipment is required.

Cancelling

No cancelling.

2.287 1887 BLOCK COUNTER FAILURE

Meaning

TAPEDR contains a duplicated block number counter for each of the

magnetic tape units. The contents of one counter are continuously

behind the other. If the test indicates that the relationship

between the two contents has changed, the block numbering is

started from the beginning, and the system issues this alarm.



Instructions


Cancelling

No cancelling.



2.288 1891 AS7 RESTARTED

Meaning

The processor of the AS7 plug-in unit has restarted.


1 number of AS7 (0..n)

2 state data of AS7:

00 out of service

01 working

02 testing

Instructions


Cancelling

No cancelling.

2.289 1893 O&M CHANNEL SEND OVERLOAD

Meaning

The send buffer of the data transmission connection of the operation

and maintenance network is full, or the X.25 network layer has not

granted permission to transmit.


1 number of OMI channel (0...n)

2 number of AS7 or AC25 plug-in unit (0...n)

DN70600744Issue 16-0 en


List of alarms

Instructions


Cancelling

No cancelling.

2.290 1894 NO RESPONSE TO AS7 SUPERVISIONMESSAGE

Meaning

The program controlling the AS7 plug-in unit has not responded to the

supervision message within the specified time.


1 number of the AS7 (0...n)

2 state data of the AS7:

00 out of service

01 working

02 testing

FF supervision software does not know the state of the AS7

Instructions





Cancelling

No cancelling.



2.291 1895 DISTURBANCE IN O&M CHANNEL

Meaning

A disturbance has been detected on the data transmission connection

of the operation and maintenance network.


1 number of OMI channel (0...n)

Instructions


Cancelling

No cancelling.

2.292 1900 DEGRADED SLIP FREQUENCY

Meaning

The ET has observed that the clock frequency slips on the

incoming E1 or T1 circuit exceed the alarm limit defined for

the ET. The slips are monitored for a 24 h period.


1 unit type

2 E1 or T1 circuit number or ETS index,

when unit type is ET.

TCSM's internal PCM circuit number 0d..7d, when unit

type is TCSM.

DN70600744Issue 16-0 en


List of alarms

Instructions


Cancelling

No cancelling.

2.293 1902 DEGRADED SLIP FREQUENCY IN 2MCONNECTION

Meaning

The exchange terminal of the VXCN plug-in unit has detected that

the number of clock frequency slips on the incoming PCM circuit

exceeds the notification limit defined for the ET. The slips are

monitored in 24h periods.


1 index of the V2 interface 0...1

Instructions


Cancelling

No cancelling.



Alarm

Documents

Transcript of Alarm