ned

Nokia Siemens Networks WCDMA RAN, rel. RU20, operating documentation, issue 1

RNC disturbances (1000-1999)

DN99580853

Issue 08AApproval Date 2009/09/02

2 DN99580853Issue 08A


Id:0900d8058067c9e1

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

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN99580853Issue 08A

3


Id:0900d8058067c9e1

Table of ContentsThis document has 219 pages.

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Default alarm indication preventions in the system . . . . . . . . . . . . . . . . . 8

2 List of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 1001 UNIT RESTARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 1002 RAM FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 1003 PARITY ERROR IN RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS. . 25

7 1007 RESTARTED PROGRAM BLOCK . . . . . . . . . . . . . . . . . . . . . . . . 26

8 1008 MML PROGRAM RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE . . . . . . . . 28

10 1012 EXCESSIVE RESTARTS OF UNIT . . . . . . . . . . . . . . . . . . . . . . . 29

11 1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED . . . . . . . 30

12 1016 MB INTERFACE FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

13 1018 PROGRAM BLOCK COMMUNICATION ERROR . . . . . . . . . . . . 32

14 1020 PROGRAM BLOCK START UP FAILURE . . . . . . . . . . . . . . . . . . 33

15 1021 PROGRAM BLOCK REWARMING STARTED. . . . . . . . . . . . . . . 35

16 1022 PROGRAM BLOCK WARMUP FAILURE. . . . . . . . . . . . . . . . . . . 36

17 1023 EXCESSIVE DISTURBANCES IN SUPERVISION . . . . . . . . . . . 37

18 1024 HAND PROCESS ERROR IN PROGRAM BLOCK . . . . . . . . . . . 38

19 1029 SCCP STP MESSAGE PREVENTION. . . . . . . . . . . . . . . . . . . . . 40

20 1035 UPU MESSAGE RECEIVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

21 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE . . . 45

22 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM . . 46

23 1064 UNIT UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

24 1065 DISK UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

25 1070 CCS7 PROGRAM BLOCK DATA ERROR. . . . . . . . . . . . . . . . . . 50

26 1071 PROCESSOR TIME SHORTAGE . . . . . . . . . . . . . . . . . . . . . . . . 51

27 1072 SIGNALLING LINK OUT OF SERVICE . . . . . . . . . . . . . . . . . . . . 53

28 1076 FORCED LIGHTWEIGHT SCHEDULING . . . . . . . . . . . . . . . . . . 56

29 1077 FREE STACK SIZE BELOW LIMIT . . . . . . . . . . . . . . . . . . . . . . . 57

30 1078 PROCESS EXCEPTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4 DN99580853Issue 08A


Id:0900d8058067c9e1

31 1080 PROCESS STOPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

32 1082 HAND USAGE LIMIT EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . 62

33 1083 SEMAPHORE USE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

34 1089 DYNAMIC LDT SLOTS EXHAUSTED. . . . . . . . . . . . . . . . . . . . . . 64

35 1090 BUFFER HANDLE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

36 1098 TOO LONG MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

37 1103 SIGNALLING MEASUREMENT REPORT LOST . . . . . . . . . . . . . 67

38 1111 RESTART DUE TO TIME OUT REQUESTED . . . . . . . . . . . . . . . 70

39 1113 STATISTICS MEASUREMENT OUTPUT FAILURE . . . . . . . . . . . 71

40 1128 EXCESSIVE DISTURBANCES IN FILE LOADING . . . . . . . . . . . . 73

41 1136 SIGNALLING MESSAGE DISTRIBUTION ERROR . . . . . . . . . . . 74

42 1140 FREE LDT SLOT COUNT BELOW LIMIT . . . . . . . . . . . . . . . . . . . 75

43 1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL . . . . 77

44 1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED. . 78

45 1143 AMOUNT OF FREE MEMORY REDUCED. . . . . . . . . . . . . . . . . . 80

46 1144 FREE BUFFER HEADERS EXHAUSTING . . . . . . . . . . . . . . . . . . 81

47 1147 MESSAGE QUEUE OVERFLOW . . . . . . . . . . . . . . . . . . . . . . . . . 82

48 1148 EXCESSIVE TRAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

49 1165 BUFFER ALLOCATION FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . 85

50 1169 FREEZING PERIOD OF SS7 REPORTING LOST . . . . . . . . . . . . 87

51 1183 HMS LINE CONNECTION LOST . . . . . . . . . . . . . . . . . . . . . . . . . 89

52 1186 NO RESPONSE TO HMN SUPERVISION . . . . . . . . . . . . . . . . . . 90

53 1192 SSCOP TRANSMIT BUFFER OVERFLOW . . . . . . . . . . . . . . . . . 91

54 1196 HMS NODE RESTARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

55 1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE COR-RUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

56 1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION . . 94

57 1203 SCDFLE FILE INTEGRITY ERROR . . . . . . . . . . . . . . . . . . . . . . . 95

58 1204 WATCHDOG CAUSES UNIT RESTART. . . . . . . . . . . . . . . . . . . . 96

59 1205 USER PLANE CONNECTION SETUP FAILURE . . . . . . . . . . . . . 97

60 1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM .99

61 1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED . . 100

62 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED . . 102

DN99580853Issue 08A

5


Id:0900d8058067c9e1

63 1222 DATA WRITING VIA VDS DEVICE FAILED. . . . . . . . . . . . . . . . 104

64 1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

65 1228 UNIT SUPERVISION NOT FUNCTIONING . . . . . . . . . . . . . . . . 107

66 1232 EHAT RESTARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

67 1234 UPDATE OF PASSWORD VALIDITY TIME FAILED . . . . . . . . . 109

68 1239 DSP SUPERVISION FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . 110

69 1240 SCCP DISTURBANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

70 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR . 115

71 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR 120

72 1244 RUNNING OUT OF MESSAGE BUFFERS . . . . . . . . . . . . . . . . 124

73 1246 RESTART OF LEAF UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

74 1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

75 1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT. . . . . . . . . . 128

76 1258 ERROR IN SPARE UNIT UPDATE . . . . . . . . . . . . . . . . . . . . . . 129

77 1269 AAL5 FRAME CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

78 1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM . . . . . . . 133

79 1273 ASP ACTIVATION FAILED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

80 1275 NO RESPONSE FROM CRITICAL UNIT . . . . . . . . . . . . . . . . . . 146

81 1277 PLUG IN UNIT CONNECTION FAILURE. . . . . . . . . . . . . . . . . . 147

82 1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMA-TION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

83 1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE150

84 1282 ASSOCIATION PARAMETER FAILURE . . . . . . . . . . . . . . . . . . 151

85 1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN . . . . . . . . . . 153

86 1285 AAL5 FRAME LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

87 1286 MISMATCH IN SYSTEM CLOCK SIGNAL. . . . . . . . . . . . . . . . . 157

88 1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST . . . . . 159

89 1291 SUBRACK CONNECTIVITY FAILURE. . . . . . . . . . . . . . . . . . . . 161

90 1293 SCCP GT SCREENING APPLIED . . . . . . . . . . . . . . . . . . . . . . . 162

91 1296 SOCKET CREATION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 166

92 1297 SOCKET INTERFACE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . 168

6 DN99580853Issue 08A


Id:0900d8058067c9e1

93 1298 DSP INTERFACE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

94 1299 RTCP SUPERVISION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 171

95 1304 ACTOR EXCEPTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

96 1331 CDSP MEMORY CONFIGURATION FAILURE . . . . . . . . . . . . . 176

97 1336 AAL5 CHANNEL USAGE FAILED. . . . . . . . . . . . . . . . . . . . . . . . 177

98 1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT179

99 1425 OVERFLOW IN ALARM BUFFERING. . . . . . . . . . . . . . . . . . . . . 181

100 1431 MMI SYSTEM OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

101 1432 DISTURBANCE IN COMMAND CALENDAR . . . . . . . . . . . . . . . 183

102 1548 MTP CONFUSION MESSAGE RECEIVED. . . . . . . . . . . . . . . . . 190

103 1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED . . . . . 191

104 1570 SECURITY LOG ALARM LIMIT REACHED . . . . . . . . . . . . . . . . 192

105 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL . . . . . . 193

106 1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM . . . . . . . . . 194

107 1598 UNIT FOUND FAULTY BY ALARM SYSTEM . . . . . . . . . . . . . . . 195

108 1660 UPDATE NUMBER MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . 196

109 1661 DATABASE MANAGER IN FATAL ERROR STATE . . . . . . . . . . 197

110 1662 DATABASE LOADING ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . 198

111 1663 HAND RESERVATION ERROR IN DATABASE MANAGER . . . 200

112 1682 SCDFLE UPDATE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

113 1683 PASSIVE UNIT FAULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

114 1684 SPARE UNIT WARMUP FAILURE . . . . . . . . . . . . . . . . . . . . . . . 204

115 1685 UNIT RESTART FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

116 1687 RECOVERY ACTION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 206

117 1800 SCSI ADDRESS ILLEGAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

118 1801 MASS MEMORY FILE BACKUP FAILURE . . . . . . . . . . . . . . . . . 211

119 1802 BACKUP COPY LOG FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 212

120 1803 SCSI MALFUNCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

121 1804 IP ROUTING RESOURCE SHORTAGE . . . . . . . . . . . . . . . . . . . 215

122 1806 PRINTER SPOOLER DISABLED . . . . . . . . . . . . . . . . . . . . . . . . 216

123 1809 IP CONFIGURATION INQUIRY SERVICE FAILED . . . . . . . . . . 217

124 1900 DEGRADED SLIP FREQUENCY . . . . . . . . . . . . . . . . . . . . . . . . 219

DN99580853Issue 08A

7

RNC disturbances (1000-1999) Summary of Changes

Id:0900d805805de168

Summary of ChangesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Note that the issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation.

Changes made between issues 8-0 and 08A

Modified alarms

Changes made between issues 7-1 and 8-0

New alarms

Modified alarms

Changes made between issues 7-0 and 7-1

Modified alarms

1569

1341

1056 1090 1148 1240

1076 1098 1165 1244

1077 1140 1198 1299

1078 1142 1220 1660

1080 1143 1221

1083 1144 1222

1089 1147 1228

1239 1269 1570 1684

8 DN99580853Issue 08A


Id:0900d805805de168

Default alarm indication preventions in the system

1 Default alarm indication preventions in the systemAlarm indication preventions for certain alarms have been set by default in RNC. This has been done to reduce the amount of alarm indications that RNC reports to NetAct. The list of alarms below shows the affected alarms that are indication-prevented by default in RNC.

The selected alarms are seen as low-priority from network monitoring point of view but in some cases the alarms listed below are preferred to be seen also in RAN level (NetAct). See the MML command group AF (Alarm Flow handling) or Managing alarm indication preventions for details on how to remove alarm-specific indication preven-tions.

Disturbances

• 1018 PROGRAM BLOCK COMMUNICATION ERROR • 1192 SSCOP TRANSMIT BUFFER OVERFLOW • 1240 SCCP DISTURBANCE • 1682 SCDFLE UPDATE FAILURE

DN99580853Issue 08A

9

RNC disturbances (1000-1999) List of Alarms

Id:0900d805805de168

2 List of Alarms1001 UNIT RESTARTED

1002 RAM FAILURE

1003 PARITY ERROR IN RAM

1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS

1007 RESTARTED PROGRAM BLOCK

1008 MML PROGRAM RESTARTED

1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE

1012 EXCESSIVE RESTARTS OF UNIT

1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED

1016 MB INTERFACE FAILURE

1018 PROGRAM BLOCK COMMUNICATION ERROR

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

1029 SCCP STP MESSAGE PREVENTION

1035 UPU MESSAGE RECEIVED

1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE

1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM

1064 UNIT UPDATE FAILURE

1065 DISK UPDATE FAILURE

1070 CCS7 PROGRAM BLOCK DATA ERROR

1071 PROCESSOR TIME SHORTAGE

1072 SIGNALLING LINK OUT OF SERVICE

1076 FORCED LIGHTWEIGHT SCHEDULING

1077 FREE STACK SIZE BELOW LIMIT

1078 PROCESS EXCEPTION

1080 PROCESS STOPPED

1082 HAND USAGE LIMIT EXCEEDED

1083 SEMAPHORE USE ERROR

1089 DYNAMIC LDT SLOTS EXHAUSTED

1090 BUFFER HANDLE ERROR

1098 TOO LONG MESSAGE

1103 SIGNALLING MEASUREMENT REPORT LOST

1111 RESTART DUE TO TIME OUT REQUESTED

1113 STATISTICS MEASUREMENT OUTPUT FAILURE

10 DN99580853Issue 08A


Id:0900d805805de168

List of Alarms

1128 EXCESSIVE DISTURBANCES IN FILE LOADING

1136 SIGNALLING MESSAGE DISTRIBUTION ERROR

1140 FREE LDT SLOT COUNT BELOW LIMIT

1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL

1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED

1143 AMOUNT OF FREE MEMORY REDUCED

1144 FREE BUFFER HEADERS EXHAUSTING

1147 MESSAGE QUEUE OVERFLOW

1148 EXCESSIVE TRAPS

1165 BUFFER ALLOCATION FAILED

1169 FREEZING PERIOD OF SS7 REPORTING LOST

1183 HMS LINE CONNECTION LOST

1186 NO RESPONSE TO HMN SUPERVISION

1192 SSCOP TRANSMIT BUFFER OVERFLOW

1196 HMS NODE RESTARTED

1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE COR-RUPTED

1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION

1203 SCDFLE FILE INTEGRITY ERROR

1204 WATCHDOG CAUSES UNIT RESTART

1205 USER PLANE CONNECTION SETUP FAILURE

1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM

1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED

1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED

1222 DATA WRITING VIA VDS DEVICE FAILED

1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART

1228 UNIT SUPERVISION NOT FUNCTIONING

1232 EHAT RESTARTED

1234 UPDATE OF PASSWORD VALIDITY TIME FAILED

1239 DSP SUPERVISION FAILURE

1240 SCCP DISTURBANCE

1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR

1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR

1244 RUNNING OUT OF MESSAGE BUFFERS

1246 RESTART OF LEAF UNIT

1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE

1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT

1258 ERROR IN SPARE UNIT UPDATE

DN99580853Issue 08A

11


Id:0900d805805de168

1269 AAL5 FRAME CORRUPTED

1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM

1273 ASP ACTIVATION FAILED

1275 NO RESPONSE FROM CRITICAL UNIT

1277 PLUG IN UNIT CONNECTION FAILURE

1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION

1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE

1282 ASSOCIATION PARAMETER FAILURE

1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN

1285 AAL5 FRAME LOST

1286 MISMATCH IN SYSTEM CLOCK SIGNAL

1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST

1291 SUBRACK CONNECTIVITY FAILURE

1293 SCCP GT SCREENING APPLIED

1296 SOCKET CREATION FAILURE

1297 SOCKET INTERFACE FAILURE

1298 DSP INTERFACE FAILURE

1299 RTCP SUPERVISION FAILURE

1304 ACTOR EXCEPTION

1331 CDSP MEMORY CONFIGURATION FAILURE

1336 AAL5 CHANNEL USAGE FAILED

1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT

1425 OVERFLOW IN ALARM BUFFERING

1431 MMI SYSTEM OVERLOAD

1432 DISTURBANCE IN COMMAND CALENDAR

1548 MTP CONFUSION MESSAGE RECEIVED

1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED

1570 SECURITY LOG ALARM LIMIT REACHED

1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL

1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM

1598 UNIT FOUND FAULTY BY ALARM SYSTEM

1660 UPDATE NUMBER MISMATCH

1661 DATABASE MANAGER IN FATAL ERROR STATE

1662 DATABASE LOADING ERROR

1663 HAND RESERVATION ERROR IN DATABASE MANAGER

1682 SCDFLE UPDATE FAILURE

1683 PASSIVE UNIT FAULTY

1684 SPARE UNIT WARMUP FAILURE

1685 UNIT RESTART FAILURE

12 DN99580853Issue 08A


Id:0900d805805de168

List of Alarms

1687 RECOVERY ACTION FAILURE

1800 SCSI ADDRESS ILLEGAL

1801 MASS MEMORY FILE BACKUP FAILURE

1802 BACKUP COPY LOG FAILURE

1803 SCSI MALFUNCTION

1804 IP ROUTING RESOURCE SHORTAGE

1806 PRINTER SPOOLER DISABLED

1809 IP CONFIGURATION INQUIRY SERVICE FAILED

1900 DEGRADED SLIP FREQUENCY

Alarm parametersThe following parameter settings are the default settings. The operator can modify them with an MML command.

The following listing also contains alarm event types. Please note that this information is not part of the alarm parameter listing and it is not possible to change those values using MML commands. The information here is for documentation purposes only.

NR TEXT CLS OUT SDC SDD CDL LVT--------------------------------------------------------------------------------

1001 UNIT RESTARTED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1002 RAM FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1003 PARITY ERROR IN RAM DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKS DST NONE 00:00 00:00 00:00 00:01:15 EVENT TYPE: PROCESSING

1007 RESTARTED PROGRAM BLOCK DST NONE 00:00 00:00 00:00 00:02:15 EVENT TYPE: PROCESSING

1008 MML PROGRAM RESTARTED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1010 NO RESPONSE TO UNIT SUPERVISION MESSAGE DST NONE 00:00 00:00 00:00 00:04:30 EVENT TYPE: PROCESSING

DN99580853Issue 08A

13


Id:0900d805805de168

1012 EXCESSIVE RESTARTS OF UNIT DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDED DST NONE 00:00 00:00 00:00 00:01:15 EVENT TYPE: PROCESSING

1016 MB INTERFACE FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1018 PROGRAM BLOCK COMMUNICATION ERROR DST NONE 00:00 00:00 00:00 02:00:00 EVENT TYPE: PROCESSING

1020 PROGRAM BLOCK START UP FAILURE DST NONE 00:00 00:00 00:00 00:05:00 EVENT TYPE: PROCESSING

1021 PROGRAM BLOCK REWARMING STARTED DST NONE 00:00 00:00 00:00 00:05:00 EVENT TYPE: PROCESSING

1022 PROGRAM BLOCK WARMUP FAILURE DST NONE 00:00 00:00 00:00 00:02:15 EVENT TYPE: PROCESSING

1023 EXCESSIVE DISTURBANCES IN SUPERVISION DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1024 HAND PROCESS ERROR IN PROGRAM BLOCK DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1029 SCCP STP MESSAGE PREVENTION DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1035 UPU MESSAGE RECEIVED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

14 DN99580853Issue 08A


Id:0900d805805de168

List of Alarms

1064 UNIT UPDATE FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1065 DISK UPDATE FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1070 CCS7 PROGRAM BLOCK DATA ERROR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1071 PROCESSOR TIME SHORTAGE DST NONE 00:00 00:00 00:00 00:01:00 EVENT TYPE: EQUIPMENT

1072 SIGNALLING LINK OUT OF SERVICE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1076 FORCED LIGHTWEIGHT SCHEDULING DST NONE 00:00 00:00 00:00 00:01:00 EVENT TYPE: EQUIPMENT

1077 FREE STACK SIZE BELOW LIMIT DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1078 PROCESS EXCEPTION DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1080 PROCESS STOPPED DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1082 HAND USAGE LIMIT EXCEEDED DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1083 SEMAPHORE USE ERROR DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1089 DYNAMIC LDT SLOTS EXHAUSTED DST NONE 00:00 00:00 00:00 00:01:00 EVENT TYPE: EQUIPMENT

1090 BUFFER HANDLE ERROR DST NONE 00:00 00:00 00:00 00:01:00

DN99580853Issue 08A

15


Id:0900d805805de168

EVENT TYPE: EQUIPMENT

1098 TOO LONG MESSAGE DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1103 SIGNALLING MEASUREMENT REPORT LOST DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1111 RESTART DUE TO TIME OUT REQUESTED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1113 STATISTICS MEASUREMENT OUTPUT FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1128 EXCESSIVE DISTURBANCES IN FILE LOADING DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1136 SIGNALLING MESSAGE DISTRIBUTION ERROR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1140 FREE LDT SLOT COUNT BELOW LIMIT DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1141 DELAY BUFFER OVERFLOW IN SIGNALLING TERMINAL DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1142 FAMILY MEMORY USAGE SUPERVISION LIMIT EXCEEDED DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1143 AMOUNT OF FREE MEMORY REDUCED DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1144 FREE BUFFER HEADERS EXHAUSTING DST NONE 00:00 00:00 00:00 00:05:00 EVENT TYPE: EQUIPMENT

1147 MESSAGE QUEUE OVERFLOW DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1148 EXCESSIVE TRAPS DST NONE

16 DN99580853Issue 08A


Id:0900d805805de168

List of Alarms

00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1165 BUFFER ALLOCATION FAILED DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1169 FREEZING PERIOD OF SS7 REPORTING LOST DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1183 HMS LINE CONNECTION LOST DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1186 NO RESPONSE TO HMN SUPERVISION DST NONE 00:00 00:00 00:00 00:00:10 EVENT TYPE: EQUIPMENT

1192 SSCOP TRANSMIT BUFFER OVERFLOW DST NONE 00:00 00:00 00:00 00:05:00 EVENT TYPE: COMMUNICATIONS

1196 HMS NODE RESTARTED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION DST NONE 00:00 00:00 00:00 00:01:00 EVENT TYPE: PROCESSING

1203 SCDFLE FILE INTEGRITY ERROR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1204 WATCHDOG CAUSES UNIT RESTART DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1205 USER PLANE CONNECTION SETUP FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS

1207 UNITS WORKING STATE DATA CORRUPTED IN THE SYSTEM DST NONE 00:00 00:00 00:00 00:00:50 EVENT TYPE: PROCESSING

DN99580853Issue 08A

17


Id:0900d805805de168

1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1222 DATA WRITING VIA VDS DEVICE FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART DST NONE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT

1228 UNIT SUPERVISION NOT FUNCTIONING DST NONE 00:00 00:00 00:00 00:00:50 EVENT TYPE: PROCESSING

1232 EHAT RESTARTED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1234 UPDATE OF PASSWORD VALIDITY TIME FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1239 DSP SUPERVISION FAILURE DST NONE 00:00 00:00 00:00 00:00:05 EVENT TYPE: EQUIPMENT

1240 SCCP DISTURBANCE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERROR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERROR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1244 RUNNING OUT OF MESSAGE BUFFERS DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: QUALITY OF SERVICE

1246 RESTART OF LEAF UNIT DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

18 DN99580853Issue 08A


Id:0900d805805de168

List of Alarms

1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT DST NONE 00:00 00:00 00:00 00:05:00 EVENT TYPE: COMMUNICATIONS

1258 ERROR IN SPARE UNIT UPDATE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1269 AAL5 FRAME CORRUPTED DST NONE 00:00 00:00 00:00 02:00:00 EVENT TYPE: COMMUNICATIONS

1272 TRIAL CONFIGURATION CANCELLED BY SYSTEM DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1273 ASP ACTIVATION FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS

1275 NO RESPONSE FROM CRITICAL UNIT DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1277 PLUG IN UNIT CONNECTION FAILURE DST NONE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT

1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILURE DST NONE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT

1282 ASSOCIATION PARAMETER FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1283 AUTOMATIC IP OVER ATM CHANNEL BROKEN DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: QUALITY OF SERVICE

1285 AAL5 FRAME LOST DST NONE 00:00 00:00 00:00 00:00:15

DN99580853Issue 08A

19


Id:0900d805805de168

EVENT TYPE: COMMUNICATIONS

1286 MISMATCH IN SYSTEM CLOCK SIGNAL DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1290 INTER-COMPUTER MESSAGE CONNECTIVITY LOST DST NONE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT

1291 SUBRACK CONNECTIVITY FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1293 SCCP GT SCREENING APPLIED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1296 SOCKET CREATION FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1297 SOCKET INTERFACE FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS

1298 DSP INTERFACE FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1299 RTCP SUPERVISION FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS

1304 ACTOR EXCEPTION DST NONE 00:00 00:00 00:00 00:10:00 EVENT TYPE: EQUIPMENT

1331 CDSP MEMORY CONFIGURATION FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1336 AAL5 CHANNEL USAGE FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS

1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT DST NONE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT

1425 OVERFLOW IN ALARM BUFFERING DST NONE

20 DN99580853Issue 08A


Id:0900d805805de168

List of Alarms

00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1431 MMI SYSTEM OVERLOAD DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1432 DISTURBANCE IN COMMAND CALENDAR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1548 MTP CONFUSION MESSAGE RECEIVED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1570 SECURITY LOG ALARM LIMIT REACHED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULL DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEM DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1598 UNIT FOUND FAULTY BY ALARM SYSTEM DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1660 UPDATE NUMBER MISMATCH DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1661 DATABASE MANAGER IN FATAL ERROR STATE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1662 DATABASE LOADING ERROR DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1663 HAND RESERVATION ERROR IN DATABASE MANAGER DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

DN99580853Issue 08A

21


Id:0900d805805de168

1682 SCDFLE UPDATE FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1683 PASSIVE UNIT FAULTY DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1684 SPARE UNIT WARMUP FAILURE DST NONE 00:00 00:00 00:00 00:10:10 EVENT TYPE: EQUIPMENT

1685 UNIT RESTART FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1687 RECOVERY ACTION FAILURE DST NONE 00:00 00:00 00:00 00:00:01 EVENT TYPE: EQUIPMENT

1800 SCSI ADDRESS ILLEGAL DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1801 MASS MEMORY FILE BACKUP FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1802 BACKUP COPY LOG FAILURE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1803 SCSI MALFUNCTION DST NONE 00:00 00:00 00:00 00:00:35 EVENT TYPE: EQUIPMENT

1804 IP ROUTING RESOURCE SHORTAGE DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1806 PRINTER SPOOLER DISABLED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: EQUIPMENT

1809 IP CONFIGURATION INQUIRY SERVICE FAILED DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: PROCESSING

1900 DEGRADED SLIP FREQUENCY DST NONE 00:00 00:00 00:00 00:00:15 EVENT TYPE: COMMUNICATIONS

22 DN99580853Issue 08A


Id:0900d805805de168

1001 UNIT RESTARTED

3 1001 UNIT RESTARTEDMeaning

The unit has restarted.

Supplementary information fields

1 working state of the unit before it was restarted

2 type of unit restart indicated by the initial loading program block:

00 warm restart

3 information on the unit restart:

00 spontaneous 01 executed by the user 02 executed or authorized by the recovery program block

4 type of restart:

00 warm restart

5 code loading mode being used:

00 optimal loading 01 total loading 02 total loading from disk

Instructions

The alarm requires no actions.

Cancelling

No cancelling.

DN99580853Issue 08A

23

RNC disturbances (1000-1999) 1002 RAM FAILURE

Id:0900d805805de168

4 1002 RAM FAILUREMeaning

The RAM test program of the computer has observed a malfunctionin 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 forthe object unit. You can check the supporting amount of the alarmwith the MML command ARO.

Cancelling

No cancelling.

24 DN99580853Issue 08A


Id:0900d805805de168

1003 PARITY ERROR IN RAM

5 1003 PARITY ERROR IN RAMMeaning

Parity error in the RAM of the computer. The parity supervisioncircuit of the CPU has detected the error.


1 address of location where the RAM test was being carried out when the error was detected

Instructions

If the alarm recurs, the CPU is probably faulty and needs to be replaced.The alarm supports the activation of the automatic recovery forthe object unit. You can check the supporting amount of the alarmwith the MML command ARO.

Cancelling

No cancelling.

DN99580853Issue 08A

25

RNC disturbances (1000-1999) 1004 COMMUNICATION ERROR BETWEEN PRO-GRAM BLOCKS

Id:0900d805805de168

6 1004 COMMUNICATION ERROR BETWEEN PROGRAM BLOCKSMeaning

The partner program block does not reply to the message sent to itwithin 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.

26 DN99580853Issue 08A


Id:0900d805805de168

1007 RESTARTED PROGRAM BLOCK

7 1007 RESTARTED PROGRAM BLOCKMeaning

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 with a command of the service terminal extension MRS or in General Error Messages of System in customer documentation.

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

27

RNC disturbances (1000-1999) 1008 MML PROGRAM RESTARTED

Id:0900d805805de168

8 1008 MML PROGRAM RESTARTEDMeaning

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


1 family identifier of the restarted MML program

Instructions

The alarm requires no actions.The alarm supports the activation of the automatic recoveryfor the object unit. You can check the supporting amount of the alarmwith the MML command ARO.

Cancelling

No cancelling.

28 DN99580853Issue 08A


Id:0900d805805de168

1010 NO RESPONSE TO UNIT SUPERVISION MES-SAGE

9 1010 NO RESPONSE TO UNIT SUPERVISION MESSAGEMeaning

The unit has not responded to a supervision message sent bythe supervisory unit in the specified time.


1 type of the unit which has failed to acknowledge the supervision. If the object unit of the alarm is different from the unit given in this field, it means that the defect is in the object unit of the alarm

2 index of the unit which has failed to acknowledge the supervision. If the object unit of the alarm is different from the unit given in this field, it means that the defect is in the object unit of the alarm

3 the supervision mode to detect the fault. The field may have the following values:

00 normal supervision 01 boot supervision

Instructions


The alarm supports the activation of the automatic recovery forthe object unit. You can check the supporting amount of the alarmwith the MML command ARO.

Cancelling

No cancelling.

DN99580853Issue 08A

29

RNC disturbances (1000-1999) 1012 EXCESSIVE RESTARTS OF UNIT

Id:0900d805805de168

10 1012 EXCESSIVE RESTARTS OF UNITMeaning

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


Instructions


The alarm supports the activation of the automatic recoveryfor the object unit. You can check the supporting amount of the alarmwith the MML command ARO.

Cancelling

No cancelling.

30 DN99580853Issue 08A


Id:0900d805805de168

1014 PROCESSOR LOAD RATE ALARM LIMIT EX-CEEDED

11 1014 PROCESSOR LOAD RATE ALARM LIMIT EXCEEDEDMeaning

The processor load rate exceeds the alarm limit defined for the unit atintervals of time defined for the unit. The alarm limit and the intervalare 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 parameterCPU 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 causesload. 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.

DN99580853Issue 08A

31

RNC disturbances (1000-1999) 1016 MB INTERFACE FAILURE

Id:0900d805805de168

12 1016 MB INTERFACE FAILUREMeaning

In the test, the message bus interface (MBIF) has been detectedfaulty. In the test, the unit sends a message to itself both on theactive and passive bus. It also checks the error counters of themessage 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.

32 DN99580853Issue 08A


Id:0900d805805de168

1018 PROGRAM BLOCK COMMUNICATION ERROR

13 1018 PROGRAM BLOCK COMMUNICATION ERRORMeaning

The partner program block does not respond within thespecified time to the message sent to it, or the replyis 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.

DN99580853Issue 08A

33

RNC disturbances (1000-1999) 1020 PROGRAM BLOCK START UP FAILURE

Id:0900d805805de168

14 1020 PROGRAM BLOCK START UP FAILUREMeaning

When activating a program block, an error has been detected whichoccurred either when creating or activating the program block. Thefault may cause disturbances in the system, particularly if aprogram 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 in customer documentation.

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 in customerdocumentation.

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.

34 DN99580853Issue 08A


Id:0900d805805de168

1020 PROGRAM BLOCK START UP FAILURE

Check the error log with the service terminal command ZGD.

771d: The program block has acknowledged negatively the activation message sent by USAPRO. Possible causes are: - The program block has detected an error in its initialisation. Check the version of the program block. Check the error log with the service terminal command ZGD. - The program block has been activated into a wrong state with regard to the unit's operating state. Check the supervision messages between the program block and USAPRO (message numbers 0001 and 0002). If the program block is constantly in a wrong state, USAPRO restarts the program block. See the RESTARTED PROGRAM BLOCK alarms, if any (alarm number 1007).

819d: The starting up of a library manager has failed. Possible causes are: - A fault in the initialisation of one of the libraries that the manager is responsible for. Check the versions of the manager and the library, service terminal commands ZSXP and ZSK. Check the error log with the service terminal command ZGD. - In the starting up of the library manager itself. Check the previous sections (770d, 771d).

All other error codes indicate a program block creation error.Probable causes are: a fault in the DXPARA family table, a faultyloading module, a discrepancy between the parameters of the familytable and the loading module, a storage area sufficiently large andfree cannot be found.

Cancelling

No cancelling.

DN99580853Issue 08A

35

RNC disturbances (1000-1999) 1021 PROGRAM BLOCK REWARMING STARTED

Id:0900d805805de168

15 1021 PROGRAM BLOCK REWARMING STARTEDMeaning

The warming of the program block has been restarted. The rewarmingmay have been caused by one of the following: the thermometer (THERMO)has detected synchronization errors in the program block, the programblock has been reactivated, or its warming failed on the previousoccasion.


1 family identifier of the detector of the error USAPRO (A0): the detector of the error is the state supervision THERMO (16B): the detector of the error is the thermometer If THERMO is the detector, a program block synchronization error is in question.

2 identifier of the family to be warmed

Instructions


Cancelling

No cancelling.

36 DN99580853Issue 08A


Id:0900d805805de168

1022 PROGRAM BLOCK WARMUP FAILURE

16 1022 PROGRAM BLOCK WARMUP FAILUREMeaning

The warming up of a program block has failed. The program block has notacknowledged the warmup command sent by the unit state administrationprogram block (USAPRO), or has acknowledged it negatively. The fault canlie in either the active or the spare unit. The warming-up manager(WUPMAN) can also be the detector of the fault.


1 family identifier of the detector of the error USAPRO (A0): the detector is the state administration WUPMAN (108): the detector is the warming-up manager

2 error code returned by the detector of the error. You can check its meaning in General Error Messages of System.

3 message bus address of the unit where the error occurred

4 family identifier of the program block that made the error

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

37

RNC disturbances (1000-1999) 1023 EXCESSIVE DISTURBANCES IN SUPERVI-SION

Id:0900d805805de168

17 1023 EXCESSIVE DISTURBANCES IN SUPERVISIONMeaning

The recovery system has detected serious disturbances in the functioningof the process families or the actors of the unit. Typically, the alarmis set due to malfunction of some critical process families or actors,but it might be also set due to excessive errors related to non-criticalprocess families or actors. The situation leads to a restart of the unit.


1 the following types of error are specified:

0 No answer to supervision 1 Wrong unit state in supervision acknowledge 2 Exception 3 Synchronization failure in SP unit 4 No answer to startup message 5 Bad answer to startup message 6 Error in PRB build 7 Maximum number family recovery exceeded 8 Maximum number warming failures exceeded 9 Restart requested by system level recovery software

2 the identifier of the process family or actor which detected the error

3 the error code returned by the detector of the error

4 the computer unit where the error occurred

5 the family identifier of the error-committing process family or actor

Instructions


Cancelling

No cancelling.

38 DN99580853Issue 08A


Id:0900d805805de168

1024 HAND PROCESS ERROR IN PROGRAM BLOCK

18 1024 HAND PROCESS ERROR IN PROGRAM BLOCKMeaning

The requested service could not be carried out due to thefailure 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. See General Error Messages of System for error code explanations

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

4 number of reserved hand/hand to be reserved

5 life focus of the hand

6 computer address of the customer

7 family ID of the customer

8 process ID of the customer

9 life focus of the customer

Instructions

Reservation of a hand fails typically in situation where allavailable hands have already been reserved (e.g. overloadsituations). If the fault situation (supplementary field 1value = 02) occurs only occasionally, the disturbance requiresno actions from the user.

In other cases, fill in a Problem Report and send it to yourlocal Nokia Siemens Networks representative. Enclose the

DN99580853Issue 08A

39

RNC disturbances (1000-1999) 1024 HAND PROCESS ERROR IN PROGRAMBLOCK

Id:0900d805805de168

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

Cancelling

No cancelling.

40 DN99580853Issue 08A


Id:0900d805805de168


19 1029 SCCP STP MESSAGE PREVENTIONMeaning

SCCP has detected at the signalling transfer point a signalling messagewhose transit is wanted to be prevented or of which an alarm needs to beissued.

If the transit message is destroyed, it may cause disturbancein the function of the user parts of the signalling point that sentthe message. Usage restrictions for transit messages are usually seton 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 following values:

00 international network 0, IN0 04 international network 1, IN1 08 national network 0, NA0 0C national network 1, NA1

3 destination point code value of the processed signalling message

4 originating point signalling network, which can get the following values:

DN99580853Issue 08A

41

RNC disturbances (1000-1999) 1029 SCCP STP MESSAGE PREVENTION

Id:0900d805805de168


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 informationfield 1 (cause code):

Cause codes 01 and 02:

SCCP screening information says that messages originating from thesignalling point mentioned in Supplementary information field 5should not be transferred to the destination point. Check if thisrestriction is justified and remove the blocking with the MMLcommand ODM if necessary. In other case the operator who owns thesignalling point mentioned in Supplementary information fields 4and 5 should be notified about an access right violation.

Cause codes 03 and 04:

SCCP screening information says that messages originating fromthe signalling network and the adjacent signalling point (channelsystem) mentioned in Supplementary information field 6 should notbe transferred to the destination point. Check if this restriction

42 DN99580853Issue 08A


Id:0900d805805de168


is justified and remove the blocking with the MML command ODM, ifnecessary. In other case the operator who owns the adjacentsignalling point mentioned in Supplementary information field 6should be notified about an access right violation.

Cause code 05:

The calling party address of the received SCCP STP message uses aglobal title indicator value that is prohibited in the parameterset of the destination point mentioned in Supplementary informationfields 2 and 3. Check if this restriction is justified and removethe restriction with the MML command OCM, if necessary. In othercase the operator who owns the signalling point mentioned inSupplementary information fields 4 and 5 should be notified aboutan access right violation.

Cause code 06:

The calling party address of the received SCCP STP message usesa global title with root parameters that do not have a matchinganalysis in the SCCP analysis information. Check if the rootparameters need to be analysed and remove the analysis with theMML command OCM, if necessary. If the root parameters need to beanalysed, check if there should exist an analysis for the globaltitle in question, and create it with the MML command NBC, ifnecessary. In other case the operator who owns the signallingpoint mentioned in Supplementary information fields 4 and 5 shouldbe notified about an access right violation.

Cancelling

No cancelling.

DN99580853Issue 08A

43

RNC disturbances (1000-1999) 1035 UPU MESSAGE RECEIVED

Id:0900d805805de168

20 1035 UPU MESSAGE RECEIVEDMeaning

The exchange has received a User Part Unavailable message (UPU).This message informs the sending end of a signalling message thatthe user part of the destination address is not available.Depending on the unavailable user part (TUP and ISUP) the telephonetraffic and signalling traffic fail. In the case of SCCP, usedservices fail.


1 network from which the UPU message came:

network code network ------------ ------ 00 national network 0 04 national network 1 08 international network 0 0C international network 1

2 header code of message

3 destination point code received in message, indicating the destination point of the unavailable user part

4 user part identifier received in the user_part_info of the message, indicating the unavailable user part in the destination point (3rd supplementary information, DPC)

identifier user part ---------- --------- 00 spare 01 spare 02 spare 03 SCCP 04 TUP 05 ISUP 06 DUP 07 ) spare ... ) spare 0F MTP test user part

5 reason for the unavailability of the user part (4th supplementary information), obtained from the

44 DN99580853Issue 08A


Id:0900d805805de168

1035 UPU MESSAGE RECEIVED

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 possibleto the destination point, check from the operator of the destinationpoint whether the user part has been created and whether it isavailable.

Cancelling

No cancelling.

DN99580853Issue 08A

45

RNC disturbances (1000-1999) 1052 REQUESTED SERVICE NOT FOUND FROMNAMETABLE

Id:0900d805805de168

21 1052 REQUESTED SERVICE NOT FOUND FROM NAMETABLEMeaning

The service that was requested was not found from thenametable.


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


Cancelling

No cancelling.

46 DN99580853Issue 08A


Id:0900d805805de168

1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEM

22 1056 MESSAGE FROM NETWORK TO UNKNOWN SUBSYSTEMMeaning

SCCP has received a message from the network. The message'sdestination 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:

00 international network 0 04 international network 1 08 national network 0 0C national network 1

3 destination point code

4 number of the destination subsystem unknown to SCCP. If the message that is to be routed does not contain a subsystem number, the field's value is FF

5 originating point code

DN99580853Issue 08A

47

RNC disturbances (1000-1999) 1056 MESSAGE FROM NETWORK TO UNKNOWNSUBSYSTEM

Id:0900d805805de168

6 number of the originating subsystem. If the message that is to be routed does not contain a subsystem number, the field's 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 otherthan FF, check if the subsystem given in Supplementary informationfield 4 has been created in the relevant signalling point of thesignalling network by using the signalling point's SCCP Data HandlingMML commands. The signalling point is given Supplementary informationfield 3 and the signalling network in Supplementary information field2.

If the subsystem has not been created, check if it should be createdin the system and, if necessary, create it with the MML commands ofthe previously mentioned command group.

If the subsystem does not belong in the system, contact the networkoperator of the signalling point mentioned in Supplementary informationfield 5 to find out why they are trying to send messages to thesubsystem mentioned Supplementary information field 4.

If the value of Supplementary information field 4 is FF, the subsystemnumber is missing from the destination data of the received message inSupplementary information field 5 signalling point. The subsystem numbercannot be obtained through global title translation.

In other cases, fill in a Problem report and send it to your localNokia Siemens Networks representative. Include the printouts ofservice terminal commands ZSCFE, ZGSC and ZSL in the report.

Cancelling

No cancelling.

48 DN99580853Issue 08A


Id:0900d805805de168

1064 UNIT UPDATE FAILURE

23 1064 UNIT UPDATE FAILUREMeaning

Failure in the updating of the partner unit or another unit to beupdated (M, SSU). The file has not been updated in the unit whichreceived 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


The alarm supports the activation of the automatic recoveryfor the object unit. You can check the supporting amount of thealarm with the MML command ARO.

Cancelling

No cancelling.

DN99580853Issue 08A

49

RNC disturbances (1000-1999) 1065 DISK UPDATE FAILURE

Id:0900d805805de168

24 1065 DISK UPDATE FAILUREMeaning

A file modification made in the Central Memory has not beenupdated onto disk. The data of the file on the disk does notcorrespond to the data in the Central Memory.


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 thatthe operation of the switch suffers disturbances after thenext disk loading in so far as the operation has to do withthe file in question.

Cancelling

No cancelling.

50 DN99580853Issue 08A


Id:0900d805805de168

1070 CCS7 PROGRAM BLOCK DATA ERROR

25 1070 CCS7 PROGRAM BLOCK DATA ERRORMeaning

A program block of the common channel signalling system has detectedan 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 havealready corrected the error detected. If the fault situationis over, futher actions are not needed.

Examine the other alarms given by the unit using the MML command AAP.If necessary, examine also the alarm history of the unit using theMML command AHP. If the alarm occurs repeatedly, the files of theCCS7 level 3 are likely to contain an error.

If the alarm still continues to occur, save the defective fileon disk for later examination for errors and contact the customersupport service. Check also the log print-outs of the unit.

The alarm supports the activation of the automatic recoveryfor the object unit. You can check the supporting amount of thealarm with the MML command ARO.

Cancelling

No cancelling.

DN99580853Issue 08A

51

RNC disturbances (1000-1999) 1071 PROCESSOR TIME SHORTAGE

Id:0900d805805de168

26 1071 PROCESSOR TIME SHORTAGEMeaning

There is not enough processor time for all processes fit for running.The operating system kernel has temporarily set the priority high forthose 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 someprocesses.


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 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 thereis an overload in the network element or a local overload in some

52 DN99580853Issue 08A


Id:0900d805805de168

1071 PROCESSOR TIME SHORTAGE

computer unit of the network element.

If the fault lies elsewhere, the maintenance of the exchange startsactions to correct the fault situation. In these other faultsituations, it is also recommended to inform the supplier ofthe software package on the fault to investigate the reason forthe fault.

Cancelling

No cancelling.

DN99580853Issue 08A

53

RNC disturbances (1000-1999) 1072 SIGNALLING LINK OUT OF SERVICE

Id:0900d805805de168

27 1072 SIGNALLING LINK OUT OF SERVICEMeaning

A signalling link has failed and changed state from IN SERVICE toOUT OF SERVICE, or its initial alignment attempt has failed. If thissignalling link is the only one in the signalling link set, the systemsets also alarm 2070, LINK SET UNAVAILABLE. If there is an alternativesignalling link available in the link set, the system performs achangeover. In this case the signal transmission capacity is alsodecreased.


1 signalling link number

2 signalling link error code

01 stop command received 02 erroneous BSN received repeatedly 03 erroneous FIB received repeatedly 04 error ratio too high 05 acknowledgement delay too long 06 initial alignment unsuccessful 07 congestion too long 08 SIO received when one is not expected 09 SIN received when one is not expected 0A SIE received when one is not expected 0B SIOS received when one is not expected 0C SIPO received when one is not expected 0D SIB received when one is not expected

3 number of the signalling link terminal

4 number of the logical signalling link terminal

5 number of the internal PCM circuit

6 number of the external PCM circuit

7 previous working state of signalling link terminal:

00 IDLE 01 OUT OF SERVICE 02 MONITORING 03 WAIT FOR FISU 04 NOT ALIGNED 05 ALIGNED 06 PROVING

54 DN99580853Issue 08A


Id:0900d805805de168

1072 SIGNALLING LINK OUT OF SERVICE

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

Instructions

If the value of 7th supplementary information is 0A (IN SERVICE).it means that the signalling link given in the 1st supplementaryinformation has failed and its state has changed from IN SERVICEto OUT OF SERVICE. The system automatically tries to reactivatethe 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:

DN99580853Issue 08A

55

RNC disturbances (1000-1999) 1072 SIGNALLING LINK OUT OF SERVICE

Id:0900d805805de168

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.

56 DN99580853Issue 08A


Id:0900d805805de168

1076 FORCED LIGHTWEIGHT SCHEDULING

28 1076 FORCED LIGHTWEIGHT SCHEDULINGMeaning

A lightweight hand within a process family has been running fora period of time that exceeds the limit defined in the parameterfile. The other hands in the family have been waiting for theirturn to run. The running of the hand identified in the supplementaryinformation of the alarm is stopped and the next hand is allowed torun, so as not to disturb the functioning of the other hands in thefamily.

The situation usually results from a fault in the functioning ofa 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 isrecommended that you inform your local Nokia Siemens Networksrepresentative about the fault, in order to investigate the reasonfor the fault.

The alarm requires no other actions.

Cancelling

No cancelling.

DN99580853Issue 08A

57

RNC disturbances (1000-1999) 1077 FREE STACK SIZE BELOW LIMIT

Id:0900d805805de168

29 1077 FREE STACK SIZE BELOW LIMITMeaning

The free stack size of the process mentioned in thesupplementary information of this alarm is below the thresholdof 128 bytes. If it continues, the situation may disturb thefunctioning 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:

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 functioningof the process. The disturbance may have been caused by an errorin the software or the packaging, so it is recommended that youinform your local Nokia Siemens Networks representative in orderto detect the possible fault.

Cancelling

No cancelling.

58 DN99580853Issue 08A


Id:0900d805805de168

1078 PROCESS EXCEPTION

30 1078 PROCESS EXCEPTIONMeaning

A process, specified in the supplementary information of thisalarm, has caused an exception and, as a result, the process hasbeen frozen. The exception may result from a software orhardware fault.

The recovery from the freezing of a process may requiremaintenance actions, for instance a process restart or acomputer 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 your local Nokia Siemens Networksrepresentative.

DN99580853Issue 08A

59

RNC disturbances (1000-1999) 1078 PROCESS EXCEPTION

Id:0900d805805de168

The alarm requires no further actions.

Cancelling

No cancelling.

60 DN99580853Issue 08A


Id:0900d805805de168

1080 PROCESS STOPPED

31 1080 PROCESS STOPPEDMeaning

A process defined in the supplementary information fields of thisalarm is in a situation where it is impossible to continueexecution. The process is stopped on purpose. The fault situationis usually a result of erroneous packaging or functioning.

Stopping the process may require maintenance, for example, aprocess restart.


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

DN99580853Issue 08A

61

RNC disturbances (1000-1999) 1080 PROCESS STOPPED

Id:0900d805805de168

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 82 number of message being handled at the time of the error 87 number of message being handled at the time of the error 88 number of message being handled at the time of the error 89 identifier of the source code file where the erroneous reference is made (internal identifier of the translator)


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, so it isrecommended that you inform local Nokia Siemens Networksrepresentative.


Cancelling

No cancelling.

62 DN99580853Issue 08A


Id:0900d805805de168

1082 HAND USAGE LIMIT EXCEEDED

32 1082 HAND USAGE LIMIT EXCEEDEDMeaning

The number of free hands of a hand type in a process family(indicated in the supplementary information fields of thisalarm) has dropped below the supervision threshold duringthe measurement period.

If there are no free hands of a certain hand type, that typeof hands cannot be reserved, and this may thus disturb thefunctioning 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 overloadsituation, or an insufficient number of hands in a given handtype. Also, the supervision parameter values may be too low.

If the number of free hands in a given hand type has in factbeen small, increase the number of hands in the DXPARA fileused in the computer. The number of hands can be increased bypackaging a new file or by modifying the number of hands inthe file used in the exchange by means of the STYMIE serviceterminal extension. The modified number of hands will bevalid after the next loading restart of the computer.

Cancelling

No cancelling.

DN99580853Issue 08A

63

RNC disturbances (1000-1999) 1083 SEMAPHORE USE ERROR

Id:0900d805805de168

33 1083 SEMAPHORE USE ERRORMeaning

The system has detected an error in a semaphore handling routine ofthe operating system kernel. The error may disturb the functioningof 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 error was detected

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

257d error in semaphore name 258d attempt to use the semaphore in a way not allowed by protection 259d illegal attempt to initialize the semaphore 260d ENTER_REGION routine call in a critical area 261d EXIT_REGION routine call outside a critical area

4 selector part of the call return address

5 offset part of the call return address

Instructions

There is a fault in the software or the packaging, so it isrecommended that you inform your local Nokia Siemens Networksrepresentative in order to find out the reason for the faultsituation.


Cancelling

No cancelling.

64 DN99580853Issue 08A


Id:0900d805805de168

1089 DYNAMIC LDT SLOTS EXHAUSTED

34 1089 DYNAMIC LDT SLOTS EXHAUSTEDMeaning

All the local descriptor table slots for the process family'sdynamic use are reserved and the reservation of a new slothas failed. The error disturbs the functioning of the processfamily and thus possibly the functioning of the whole computer.

The fault may be in packaging, that is, an insufficient number ofdynamic local descriptor table slots in comparison with thenumber of hand processes are reserved for a family. The faultmay also be in software, that is, too many slots are reserved.

The process family indicated in the supplementary informationfields of this alarm is not always the one whose descriptortable is full, because some operating system routines handletables other than the process family's own local descriptor table.This is especially the case when the family identifier is 108.






Instructions

1. Output the resource information of the process family indicated in the alarm by using the DOI command. This will help to determine the fault. Useful information can also be obtained from the operating system log or the computer log.

2. Inform your local Nokia Siemens Networks representative about the fault.

Cancelling

No cancelling.

DN99580853Issue 08A

65

RNC disturbances (1000-1999) 1090 BUFFER HANDLE ERROR

Id:0900d805805de168

35 1090 BUFFER HANDLE ERRORMeaning

A process has called a buffer handling routine with an incorrectbuffer handle. A typical situation is a failure in the release ofthe buffer, so that the buffer remains occupied by the process.






Instructions

The fault is in the software, therefore, it is recommended that youinform your local Nokia Siemens Networks representative.

Cancelling

No cancelling.

66 DN99580853Issue 08A


Id:0900d805805de168

1098 TOO LONG MESSAGE

36 1098 TOO LONG MESSAGEMeaning

A message to be received is longer than the area reserved formessage reception, therefore, receiving the message to theprocess data area was only partially successful.

If the process does not check whether message reception wassuccessful, the process may erroneously read information in thedata 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 recommendedthat you inform your local Nokia Siemens Networks representative,in order to correct the fault situation.


Cancelling

No cancelling.

DN99580853Issue 08A

67

RNC disturbances (1000-1999) 1103 SIGNALLING MEASUREMENT REPORT LOST

Id:0900d805805de168

37 1103 SIGNALLING MEASUREMENT REPORT LOSTMeaning

The forming or outputting of signalling measurement reportin the defined device has failed. The reason may be in thedefinition of the logical file used in the outputting of thereport, or in the switching, or the reason may be the wrongoperating state or overload of one of the I/O-devices whichthe 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 with a command of the service terminal extension MRS or in General Error Messages of System in customer documentation.

68 DN99580853Issue 08A


Id:0900d805805de168

1103 SIGNALLING MEASUREMENT REPORT LOST

Instructions

Make sure that the operation and maintenance unit (OMU) is inthe WO-EX state. Make sure that the connection of the logicalfile of the measurement in question is in order, i.e. thatthe logical file is further connected to another logical file(e.g. binary report file to the MEAFIL) or to a workingI/O-device (see I/O Configuration Handling, Command ReferenceManual.)If the logical files of binary reports are connected to theMEAFIL file, make sure that the MEAFIL is connected to thevirtual data storing device (VDS).

Logical file Measurement type.............................................ascii bin

MTP measurement reports:MTPSLAVAIA MTPSLAVAIB SIGNALLING LINK AVAILABILITYMTPSLPERFA MTPSLPERFB SIGNALLING LINK PERFORMANCEMTPSLUTILA MTPSLUTILB SIGNALLING LINK UTILIZATIONMTPSPSTATA MTPSPSTATB SIGNALLING POINT STATUSMTPSLSAVAA MTPSLSAVAB SIGNALLING LINK SET AND ROUTE SET AVAILABILITYMTPOCTHSPA MTPOCTHSPB SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINTMTPOCTSIOA MTPOCTSIOB SIF AND SIO OCTETS HANDLED WITH SIOMTPOCTMATA MTPOCTMATB SIF AND SIO OCTETS HANDLED WITH OPC, DPC AND SIO

SCCP/TC measurement reports:SCCPSPA SCCPSPB SCCP SIGNALLING POINT METERSSCCPSSA SCCPSSB SCCP SUBSYSTEM METERSSCCPLSSAVA SCCPLSSAVB SCCP LOCAL SUBSYSTEM AVAILABILITYSCCPSINGLA SCCPSINGLB SCCP SINGLE METERSTCAPPUA TCAPPUB TCAP PERFORMANCE AND UTILIZATIONTCAPTRANSA TCAPTRANSB TC TRANSACTION METERS

LAPD measurement reports:LAPDFROCA LAPDFROCB TRANSMITTED AND RECEIVED FRAMES AND OCTETS ON D-CHANNELLAPDMISCCA LAPDMISCCB D-CHANNEL MISCELLANEOUS STATISTICAL METERSLAPDQ921EA LAPDQ921EB Q.921 ERROR METERS

MTP interval log reports:MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORTMTPSPLOGA SIGNALLING POINT INTERVAL LOG REPORT

DN99580853Issue 08A

69

RNC disturbances (1000-1999) 1103 SIGNALLING MEASUREMENT REPORT LOST

Id:0900d805805de168

SCCP/TC interval log reports:SCCPSPLOGA SCCP SIGNALLING POINT INTERVAL LOG REPORTSCCPSGLOGA SCCP SEGMENTATION AND REASSEMBLY ERRORS INTERVAL LOG REPORTTCLOGA TC INTERVAL LOG REPORTSCCPGTLOGA SCCP GT TRANSLATION ERRORS LOG REPORT

Cancelling

No cancelling.

70 DN99580853Issue 08A


Id:0900d805805de168

1111 RESTART DUE TO TIME OUT REQUESTED

38 1111 RESTART DUE TO TIME OUT REQUESTEDMeaning

Software configuration management has asked the recovery systemfor system restart, but recovery has sent a negative response orhas not responded at all, and no restart has been made.


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.

DN99580853Issue 08A

71

RNC disturbances (1000-1999) 1113 STATISTICS MEASUREMENT OUTPUT FAIL-URE

Id:0900d805805de168

39 1113 STATISTICS MEASUREMENT OUTPUT FAILUREMeaning

The outputting of statistics measurement report in thedefined 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 willdisappear or, if the measurement report is output, thedata 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

72 DN99580853Issue 08A


Id:0900d805805de168

1113 STATISTICS MEASUREMENT OUTPUT FAIL-URE

Instructions

Check that the I/O device used in the outputting of thereport is in working order and in the correct working state(MML command IHI) and that the logical output file STATMEABis connected to the device in question (MML command IID).

Cancelling

No cancelling.

DN99580853Issue 08A

73

RNC disturbances (1000-1999) 1128 EXCESSIVE DISTURBANCES IN FILE LOAD-ING

Id:0900d805805de168

40 1128 EXCESSIVE DISTURBANCES IN FILE LOADINGMeaning

File loading has been interrupted due to recurring errors. The objectunit of the alarm is restarted by the recovery system to recover fromthe errors.


1 general error message of the system. You can check its meaning in General Error Messages of System.

2 identifier of the family that detected the error: RXSPRB (3AB): error detected by the System Level Restart Controller

3 physical address of the computer where the failed loading was executed

4 load group source: 01 memory 02 disk

5 load group

6 identifier of the file whose loading failed

Instructions


Cancelling

No cancelling.

74 DN99580853Issue 08A


Id:0900d805805de168

1136 SIGNALLING MESSAGE DISTRIBUTION ER-ROR

41 1136 SIGNALLING MESSAGE DISTRIBUTION ERRORMeaning

The alarm is issued when CCRECE receives from a signalling linka 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 faultymessage.

Cancelling

No cancelling.

DN99580853Issue 08A

75

RNC disturbances (1000-1999) 1140 FREE LDT SLOT COUNT BELOW LIMIT

Id:0900d805805de168

42 1140 FREE LDT SLOT COUNT BELOW LIMITMeaning

The free dynamic LDT slot count of a process indicated in thesupplementary information fields of this alarm is below thesupervision limit indicated by the process.

The fault may be in packaging, that is, an insufficient number ofdynamic local descriptor table slots in comparison with thenumber of hand processes are reserved for a family. The faultmay also be in software, that is, too many slots are reserved orthe supervision limit is set to be unnecessarily high. In suchcase 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 significantlyreduced, and the reason for this should be clarifiedimmediately.

When the family has no more dynamic LDT slots the family is restarted,which may interfere with the functioning of the computer. Disturbanceobservation 1089 is set when there are no more dynamic LDT slots.


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

2 number of family's free dynamic LDT slots

3 supervision limit

4 supervision interval in seconds

Instructions

1. Display the resource status of the process family indicated in the additional information field of the alarm by using the MML command DOI.

2. Create a long-term family resource status measurement using the MML command DOF and start the measurement by giving the MML command DOG. The measurements are displayed to the logical file OSSTATREP. Connect the logical file OSSTATREP to I/O terminal using the MML command IIS.

3. Contact your local Nokia Siemens Networks representative.

76 DN99580853Issue 08A


Id:0900d805805de168

1140 FREE LDT SLOT COUNT BELOW LIMIT

Displaying the resource status and providing these results speeds up the correction of the fault.

Cancelling

No cancelling.

DN99580853Issue 08A

77

RNC disturbances (1000-1999) 1141 DELAY BUFFER OVERFLOW IN SIGNALLINGTERMINAL

Id:0900d805805de168

43 1141 DELAY BUFFER OVERFLOW IN SIG-NALLING TERMINALMeaning

The delay buffer of a plug-in unit is full. Messages are deletedwhen the delay buffer is in use, so that the signalling traffic isdisturbed. The overflow situation may be caused by overload or afailure in the plug-in unit. The alarm is issued when thereis a changeover or controlled rerouting.


1 plug-in unit type

2 plug-in unit index

3 logical number of signalling terminal

Instructions

Check the amount of traffic on the channel concerned with theMML commands of statistics handling. You can obtain the amountof traffic on the channel, either for the last half hour orcumulatively, 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 theMML command USC. Change into testing state the unit where theplug-in unit that is suspected faulty is located. Run diagnosticsfor the unit to find out whether the plug-in unit is faulty, seeDiagnostics and Testing, Appendices, Maintenance Manual.

Replace the plug-in unit, if diagnostics detects that it is faulty.See Instructions for Replacing Plug-in Units, Maintenance Manual.

Check also with the MML command AHP whether the alarm 2224,ERROR IN MSU HANDLING, has been issued. If it is, act according to itsinstructions.

Cancelling

No cancelling.

78 DN99580853Issue 08A


Id:0900d805805de168

1142 FAMILY MEMORY USAGE SUPERVISION LIM-IT EXCEEDED

44 1142 FAMILY MEMORY USAGE SUPERVI-SION LIMIT EXCEEDEDMeaning

The family indicated in the supplementary information fields of thisalarm has exceeded the supervision limit set to its memory use.During start up, the system allocates memory areas to the familybased on maximum memory use rate in normal functions.The system also supervises that this limit is not exceeded.the limit is exceeded, this alarm is set off.

Memory use of process families is supervised because a faulty familymay reserve a lot of memory and thus prevent otherprocesses from reserving memory. The failure to reserve memorydisturbs the functioning of the processes and the computer.Depending on the functions of the computer, traffic capacity orcharging 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

DN99580853Issue 08A

79

RNC disturbances (1000-1999) 1142 FAMILY MEMORY USAGE SUPERVISION LIM-IT EXCEEDED

Id:0900d805805de168

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 your local Nokia Siemens Networks representative to detect a possible fault in software. Displaying information on memory use and providing these results speeds up the correction of the fault.

Cancelling

No cancelling.

80 DN99580853Issue 08A


Id:0900d805805de168

1143 AMOUNT OF FREE MEMORY REDUCED

45 1143 AMOUNT OF FREE MEMORY REDUCEDMeaning

The amount of free memory in the computer is below the alarm limitused in supervision.

If the computer runs out of free memory, memory allocation failsand may disturb the functioning of the computer.

The size of the largest unified memory area is used as the freememory amount, as its size is more in accordance with the availablefree 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 softwareor from a computer whose memory is too small for the software package.Use the MML command DOI to investigate the computer's memory use fordifferent purposes.

To find out the nature and cause of the situation, send the informationon memory use to your local Nokia Siemens Networks representative.

The alarm limit used in supervision can be modified with the MML commandDOM, parameter MEML.

Cancelling

No cancelling.

DN99580853Issue 08A

81

RNC disturbances (1000-1999) 1144 FREE BUFFER HEADERS EXHAUSTING

Id:0900d805805de168

46 1144 FREE BUFFER HEADERS EXHAUSTINGMeaning

The number of free buffer headers is below the alarm limit usedin supervision. This indicates an increased risk of running outof free buffer headers. When there are no more free buffer headersthe computer must be restarted.

The fault may be in packaging or software, resulting in an insufficientoverall number of buffer headers or one of the process familiesreserving too many headers. It is also possiblethat 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 Siemens Networks representative.

2. If the value of this parameter is 100 or below, contact your local Nokia Siemens Networks representative to detect a possible fault in packaging or software.

Cancelling

No cancelling.

82 DN99580853Issue 08A


Id:0900d805805de168

1147 MESSAGE QUEUE OVERFLOW

47 1147 MESSAGE QUEUE OVERFLOWMeaning

The message queue of the process has reached its defined maximumlength 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 recommendedthat you inform your local Nokia Siemens Networks representative,in order to detect the reason for the fault.


Cancelling

No cancelling.

DN99580853Issue 08A

83

RNC disturbances (1000-1999) 1148 EXCESSIVE TRAPS

Id:0900d805805de168

48 1148 EXCESSIVE TRAPSMeaning

The number of traps exceeds the alarm limit duringthe supervision interval.

Traps are produced when the program uses an insufficient or faulty memoryor, for example, a faulty addtional plug-in unit.Traps do not usually disturb the functioning of the program producingthem, but they indicate a disturbance either in the hardware, software orin 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 programexecution was when the trap was detected, that is, the addressdescribes the program's general execution area rather than aspecific 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 your local Nokia Siemens Networks representative.

2. Operating system logs have been written in the OSSUPREP logical file and studying those can help you in locating the fault. Check with the MML command ZDOP whether parameter SENDING OF REPORTS is allowed. If the parameter is not allowed, allow it with the MML command ZDOM. Connect the OSSUPREP logical file to the I/O terminal available with the MML command ZIIS.

84 DN99580853Issue 08A


Id:0900d805805de168

1148 EXCESSIVE TRAPS

3. If the fault is a hardware fault, you can temporarily prevent the alarm from rising repeatidly by modifying the alarm limit of the object unit with the MML command ZDOM, or, 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.

DN99580853Issue 08A

85

RNC disturbances (1000-1999) 1165 BUFFER ALLOCATION FAILED

Id:0900d805805de168

49 1165 BUFFER ALLOCATION FAILEDMeaning

A process failed to reserve a buffer because the buffer sizerequested by the process is larger than the largest freebuffer.

Buffer reservation failure may prevent the execution of atask 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 whosememory is too small for the software and functions requiredof it. A software fault is probable, if the requested buffersize indicated in the supplementary information field islarge in comparison with the computer memory.

If the total amount of free memory indicated in thesupplementary information field seems adequate but also thelargest free buffer (indicated in the supplementaryinformation field) is small, the memory is fragmented. Even ahot restart of a computer would cause the rearranging of freeand reserved buffers, so that the largest free buffer wouldprobably become larger.

If a buffer reservation fails in connection with a criticaltask, the maintenance system restarts the computer, andusually the memory state also returns to normal.

If the total amount of free memory is small, the computerprobably has an insufficient memory capacity and should bereplaced with one that has more capacity.

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

86 DN99580853Issue 08A


Id:0900d805805de168

1165 BUFFER ALLOCATION FAILED

Siemens Networks representative on the fault. Include information onthe memory, i.e. on the division of free memory and theprocess families that have reserved memory the most.

Cancelling

No cancelling.

DN99580853Issue 08A

87

RNC disturbances (1000-1999) 1169 FREEZING PERIOD OF SS7 REPORTINGLOST

Id:0900d805805de168

50 1169 FREEZING PERIOD OF SS7 REPORT-ING LOSTMeaning

Some of the counters or logs of the SS7 statistics are not reported,because the counters or log events in question are lost from thefiles.

If the alarm concerns counter reporting, the following two 30-minutefreezing periods have passed during the report outputting, and thusthe counters of the first reporting period are lost. The counters ofthe freezing period in question will not be included to the followingreporting period.

If the alarm concerns reporting of interval logs,the 5-minute freezing period has finished before the log events of theprevious 5-minute period are reported. In this case, the log events inquestion are not reported, but they are available with MML commands.


1 type of counters or logs lost:

01 MTP counters 02 SCCP/TC counters 03 MTP interval logs 04 SCCP/TC interval logs

2 file number of the counter or log file whose counters or logs were not reported. If the file number is not available, the value of the field is FFFFFFFF

Instructions

Check that the operation and maintenance computer (OMU) is in workingstate WO-EX with the MML command USI.

Check that the connections of the logical files of the SS7 reportingare in order with the MML command IID, that is, that the logical filesare connected onwards to another logical file (for example binaryreports' files to MEAFIL file) or to a functioning I/O device(for more information, see I/O System in customer documentation).

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

88 DN99580853Issue 08A


Id:0900d805805de168

1169 FREEZING PERIOD OF SS7 REPORTING LOST

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 withthe MML commands OSL, OSN OSE, and possibly unnecesary reportingtypes with the MML commands OSM and OSG.

Logical file Measurement type======================================================ascii bin

MTP counters:MTPSLAVAIA MTPSLAVAIB SIGNALLING LINK AVAILABILITYMTPSLPERFA MTPSLPERFB SIGNALLING LINK PERFORMANCEMTPSLUTILA MTPSLUTILB SIGNALLING LINK UTILIZATIONMTPSPSTATA MTPSPSTATB SIGNALLING POINT STATUSMTPSLSAVAA MTPSLSAVAB SIGNALLING LINK SET AND ROUTE SET AVAILABILITYMTPOCTHSPA MTPOCTHSPB SIF AND SIO OCTETS HANDLED WITH SIGNALLING POINTMTPOCTSIOA MTPOCTSIOB SIF AND SIO OCTETS HANDLED WITH SIOMTPOCTMATA MTPOCTMATB SIF AND SIO OCTETS HANDLED WITH OPC, DPC AND SIO

SCCP/TC counters:SCCPSPA SCCPSPB SCCP SIGNALLING POINT METERSSCCPSSA SCCPSSB SCCP SUBSYSTEM METERSSCCPLSSAVA SCCPLSSAVB SCCP LOCAL SUBSYSTEM AVAILABILITYSCCPSINGLA SCCPSINGLB SCCP SINGLE METERSTCAPPUA TCAPPUB TCAP PERFORMANCE AND UTILIZATIONTCAPTRANSA TCAPTRANSB TC TRANSACTION METERS

MTP interval logs:MTPSLLOGA SIGNALLING LINK INTERVAL LOG REPORTMTPSPLOGA SIGNALLING POINT INTERVAL LOG REPORT

SCCP interval logs:SCCPSPLOGA SCCP SIGNALLING POINT INTERVAL LOG REPORTSCCPSGLOGA SCCP SEGMENTATION AND REASSEMBLY ERRORS INTERVAL LOG REPORTTCLOGA TC INTERVAL LOG REPORTSCCPGTLOGA SCCP GT TRANSLATION ERRORS LOG REPORT

Cancelling

No cancelling.

DN99580853Issue 08A

89

RNC disturbances (1000-1999) 1183 HMS LINE CONNECTION LOST

Id:0900d805805de168

51 1183 HMS LINE CONNECTION LOSTMeaning

The HMS node of the computer unit has not received supervisorymessages from either transfer line of the HMS channel for sometime. The computer unit has possibly lost the HMS line connectionto other parts of the system. In that case, the administrativeactions based on the use of HMS channel, such as restarting thecomputer unit, its isolation from the system or cancelling theisolation, do not succeed from other computers.


1 transfer line of the HMS channel (0 or 1) which the HMS node of the computer unit has last tried to listen to

Instructions

No specific operating instructions.


Cancelling

No cancelling.

90 DN99580853Issue 08A


Id:0900d805805de168

1186 NO RESPONSE TO HMN SUPERVISION

52 1186 NO RESPONSE TO HMN SUPERVISIONMeaning

The HMS node of the computer unit does not respond to supervisionexecuted by the local device driver. The HMS node, the device driveror the communication channel between them is faulty or overloaded.It is likely that the computer unit cannot use communication andmanagement services related to the HMS channel.


Instructions

No specific operating instructions.

The alarm supports the activation of the automatic recoveryfor the object unit. You can check the supporting amount ofthe alarm with the MML command ARO.

Cancelling

No cancelling.

DN99580853Issue 08A

91

RNC disturbances (1000-1999) 1192 SSCOP TRANSMIT BUFFER OVERFLOW

Id:0900d805805de168

53 1192 SSCOP TRANSMIT BUFFER OVERFLOWMeaning

The transmit buffer of SAAL, which is maintained by the SSCOP layer,has filled up. Signalling message units, which are sent to SAAL, arelost. SAAL is able to handle normally only MTP-3 management messages.The signalling message transfer of concerned signalling link isdisturbed. This situation may be caused by the congestion in thesignalling 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.

92 DN99580853Issue 08A


Id:0900d805805de168

1196 HMS NODE RESTARTED

54 1196 HMS NODE RESTARTEDMeaning

HMS node has been restarted. The filtering time for the alarm inputsof the plug-in unit has been reset to zero. The system will, howeverset them automatically back to the defined value. The system alsoupdates the alarm situation of the plug-in unit displayed in theadditional information in the alarm to correspond the actual situation.


1 type of the plug-in unit detecting the fault

2 HMS number of the cabinet in which the plug-in unit is located

3 HMS number of the subrack in which the plug-in unit is located

4 PPA, plug-in unit position address

5 restarted node. The possible values: 01, slave node 02, master node 03, bridge node in TSS3 04, bridge node in TBUF

Instructions

Check if any other alarm related to this fault is on and follow theinstructions of that alarm. It no other alarm related to this faultis on and if the disturbance appears frequently, replace the faultyplug-in unit indicated in the additional information of the alarm,see instructions on replacing plug-in units.

Cancelling

No cancelling.

DN99580853Issue 08A

93

RNC disturbances (1000-1999) 1198 CRITICAL MESSAGE CONNECTION MANAGE-MENT FILE CORRUPTED

Id:0900d805805de168

55 1198 CRITICAL MESSAGE CONNECTION MANAGEMENT FILE CORRUPTEDMeaning

This is an internal error in the Message Connection Management system.

The Message Connection Management system has detected that one of itsparameter files is missing or corrupted, and it has taken automaticrecovery measures by recreating the file from the beginning. It ispossible that some information on message connections has been lost.


1 general error message of the system. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or in the General Error Messages of System

2 name of the corrupted file

Instructions

The name of the corrupted file is given in the supplementary informationfield 2.

- if the name is PUFFIL, the file W0-ASWDIR/PUFFILGX.TXT containing information on message connections was missing or corrupted. The message connection network has been recreated according to the connection rules in the TRYFIL file. The corrupted file has been saved as W0-ASWDIR/PUFFILGX.ERR

The disturbance can be ignored if it occurs when a new system is beingrestarted for the first time, and the error code is 56d (NO SUCH FILE).In this case, the files in question do not exist on the disk. TheMessage Connection Management system creates them.

Usually the system is capable of recovering by itself from the errorthat caused the alarm, but the reasons behind the error should be lookedinto. Save the corrupted file W0-ASWDIR/PUFFILGX.ERR. If the supervisionof some computer units starts to fail, indicated by the alarm 1010, NORESPONSE TO UNIT SUPERVISION MESSAGE, contact your local NokiaSiemens Networks representative.

Cancelling

No cancelling.

94 DN99580853Issue 08A


Id:0900d805805de168

1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISION

56 1200 ACTOR HAS FAILED TO REGISTER TO THE SUPERVISIONMeaning

An actor has failed to register to the active supervision.

It is possible that the supervision data table has filled up. Thismeans that the actor supervisor (SVATOR) cannot take more actorsunder the active supervision. The problem has no effect on theactor supervision already activated.

Apart from the active supervision, all actors are supervisedpassively, i.e. exceptions made by the actors are always noticed.

If the actor is not supervised actively, the erroneous behaving(e.g. infinite loops) or the total stopping of the actor is notdetected and the recovery actions are not activated. However, ifthe actor runs without problems the lack of active supervision isnot 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 localNokia Siemens Networks representative.

List the content of the supervision data table with service terminalcommand: supervise -a all and attach it to the Failure Report.

Cancelling

No cancelling.

DN99580853Issue 08A

95

RNC disturbances (1000-1999) 1203 SCDFLE FILE INTEGRITY ERROR

Id:0900d805805de168

57 1203 SCDFLE FILE INTEGRITY ERRORMeaning

The working state and configuration data of the system in the supervisedunit (any other computer unit but active maintenance computer) differsfrom the data in the memory of the supervising unit (active maintenancecomputer). The supervised unit is the object unit of the alarm andthe supervising unit is the unit sending of the alarm.

These problems are caused because there have been message transfererrors during the distribution of working state and configuration dataof the system to functional units.

This divergence of data may cause malfunctioning of the system and itslows or even prevent the automatic recovery actions after a failureof a unit.


1 first corrupted record in the SCDFLE file contains data of this type of unit

2 this is the index of the unit in the first corrupted record

3 amount of corrupted records

Instructions

Alarm does not require user actions.

The alarm supports the activation of the automatic recovery for theobject unit. You can check the supporting amount of the alarm withthe MML command ARO.

Cancelling

No cancellation.

96 DN99580853Issue 08A


Id:0900d805805de168

1204 WATCHDOG CAUSES UNIT RESTART

58 1204 WATCHDOG CAUSES UNIT RESTARTMeaning

A critical actor for the functioning of the unit has failed.This kind of actors are e.g. QXFPRB, which activates the recoveryfunctions and DAQTOR, which takes care of starting other actors.

Actor Supervisor (SVATOR) stops feeding the watchdog feeder actorand this will cause a unit restart.


Instructions

The alarm requires no actions because the coming unit restartsolves the problem.

Cancelling

No cancelling.

DN99580853Issue 08A

97

RNC disturbances (1000-1999) 1205 USER PLANE CONNECTION SETUP FAILURE

Id:0900d805805de168

59 1205 USER PLANE CONNECTION SETUP FAILUREMeaning

The RNC (Radio Network Controller) is setting up the userplane connection for a call between the RNC and the CN (CoreNetwork) but the AAL2 signalling address (service end pointaddress) does not match the one specified in the local system.

It may also be that the address is unspecified or invalid.

In the case of transit functionality, the alarm is set becauseno route has been defined to the destination indicated by theAAL2 address.


1 reason for the alarm

possible numerical values are: 1 unknown address 2 invalid address 3 own address is invalid or missing

2 type of the address

possible numerical values are: 1 E.164 2 NSAP

3 total length of the address

4-16 service end point address used

RNC sets up the user plane of a connection (towards CN) using the service end point address. The address format is either E.164 or NSAP. The E.164 address contains one number in a byte. The NSAP address is BCD encoded (two digits in a byte). In most cases, the address fits only partially in this supplementary information field. The complete address is written into the log (examine the log file with the computer log handler extension of the service terminal)

Instructions

If the value of the supplementary information 1 is:

98 DN99580853Issue 08A


Id:0900d805805de168

1205 USER PLANE CONNECTION SETUP FAILURE

1 unknown address Compare the address in the alarm to the one specified locally (in the ATM Module). You can find it out by interrogating the default parameters with the MML command WEI. Change the local address if it is incorrect. The new address will be in use after a while (approximately 5 minutes).

2 invalid address Check the configuration in the RNC and change it if necessary.

3 own address is invalid or missing Interrogate the ATM Module default parameters by giving the MML command WEI. Add or change the address depending on the situation.

Cancelling

No cancelling.

DN99580853Issue 08A

99

RNC disturbances (1000-1999) 1207 UNITS WORKING STATE DATA CORRUPTEDIN THE SYSTEM

Id:0900d805805de168

60 1207 UNITS WORKING STATE DATA COR-RUPTED IN THE SYSTEMMeaning

Working state data in the memory of the supervised unit is differentfrom the working state data of the supervised unit in the memory ofthe supervising unit. The system detects this divergence by itselfand begins the actions in order to correct the problem.

This data divergence can be caused by message transfer errors duringthe distribution of the working states to functional units. It maycause malfunctioning of the system, and it slows down or may evenprevent the automatic recovery actions in the system.


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 andsend it to your local Nokia Siemens Networks representative.Otherwise, no action is required.

Cancelling

No cancelling.

100 DN99580853Issue 08A


Id:0900d805805de168

1220 HANDLING OF MEASUREMENT DEFINITION FILE FAILED

61 1220 HANDLING OF MEASUREMENT DEFINI-TION FILE FAILEDMeaning

Handling of measurement definition file has failed. There maybe a temporary overload in the I/O-system. The changes, whichhave possibly been made have not been updated to the file.The measurement continues using the changed parameters, but ina possible restart situation the system will continue the measurementusing the old parameters. This means that the schedule of themeasurement may not be correct.

The third and fourth supplementary information fields showthe 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 instructions on the service terminal) or from General Error Messages of System

Instructions

If the third supplementary information field has the value 01, themeasurement is continued, but the parameters have not been updatedto disk. The wrong parameters are shown when interrogating themeasurement parameters (T2I MML command). This may be due to atemporary overload in the I/O-system. Check the I/O-system's activealarms and follow those alarm instructions. You can try to write onthe disk again when the I/O-system has recovered by modifying themeasurement schedule (T2M MML command), or the schedule is also updatedto the disk every night at 01.00 am, so these updates could correctthe problem. If not (the disturbance still occurs), contact your localNokia Siemens Networks representative. Send the unit's logs, operating

DN99580853Issue 08A

101

RNC disturbances (1000-1999) 1220 HANDLING OF MEASUREMENT DEFINITIONFILE FAILED

Id:0900d805805de168

system logs and active alarms to your Nokia Siemens Networksrepresentative. The logs can be output by using the service terminalcommands ZGD and ZSL. The active alarms can be output by usingthe MML command AAP.

If the third supplementary information field has value 02, remove themeasurement definition file (T2D MML command) which could not bepassified by the system. This may be due to a temporary overloadin the I/O-system. The name of the file is AMEASxxx.yyy,where xxx refers to the MID value (first supplementary informationfield) in the alarm, and yyy refers to the OID (second supplementaryinformation field) value in the alarm.

Cancelling

No cancelling.

102 DN99580853Issue 08A


Id:0900d805805de168

1221 STATISTICAL MEASUREMENT REPORT OUT-PUT FAILED

62 1221 STATISTICAL MEASUREMENT REPORT OUTPUT FAILEDMeaning

Outputting the statistical measurement report has failed.The report of the measurement, which has caused the alarmmay disappear or, if the measurement report is output, thedata in it may be faulty. The third and fourth supplementaryinformation 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 measurements object list identifier (from 1 to 999). You can check its meaning by using the MML command T2C

3 the reason for failure in outputting of the report: 01 Buffer allocation failed 02 No data writing service provider 03 Error with data writing service provider

4 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 instructions on the service terminal) or from the General Error Messages of System

Instructions

If the third supplementary information field has the value 01, thereis an error situation, which probably cannot be corrected without asoftware update. Contact your local Nokia Siemens Networksrepresentative. Send the unit's logs, operating system logs andactive alarms to your Nokia Siemens Networks representative.The logs can be output by using the service terminal commandsZGD and ZSL. The active alarms can be output by using the MMLcommand AAP.

If the third supplementary information field has the value 02, theservice may be temporarily unobtainable. If this is continuous,there is an error situation which probably cannot be correctedwithout a software update. Contact yourlocal Nokia Siemens Networksrepresentative. Send the unit's logs, operating system logs and activealarms to your Nokia Siemens Networks representative. The logs can be

DN99580853Issue 08A

103

RNC disturbances (1000-1999) 1221 STATISTICAL MEASUREMENT REPORT OUT-PUT FAILED

Id:0900d805805de168

output by using the service terminal command ZGD and ZSL. Theactive alarms can be output by using the MML command AAP.

If the third supplementary information field has the value 03, checkthat the I/O device used in the outputting of the report is in workingorder and in the correct working state (MML command IHI) and that thelogical output file is connected to the device in question (MML commandIID). More information on the administration of I/O devices can befound in instructions on I/O configuration handling.

Cancelling

No cancelling.

104 DN99580853Issue 08A


Id:0900d805805de168

1222 DATA WRITING VIA VDS DEVICE FAILED

63 1222 DATA WRITING VIA VDS DEVICE FAILEDMeaning

Data writing via the VDS device has failed. The report of themeasurement that has caused the alarm may disappear. The second andthird supplementary information fields show the reason for the failure.


1 measurement identifier of the report 1000 RNW measurement Other other measurement id

2 reason for the data writing failure 01 error in I/O system 02 no response from I/O system 03 memory allocation failed

3 specified reason for the error case shown in the second supplementary information field. This is a general error message of the system. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or from the General Error Messages of System

Instructions

If the first supplementary information field has a value other than1000, you can check its meaning by using the MML command T2C.

If the second supplemetary information field has value 01 or 02,the I/O system may be overloaded, and thus the report output fails.The problem may be temporary and the system will correct it.Check the active alarms of the I/O system and follow those alarminstructions. If the disturbance occurs repeatedly, contact yourlocal Nokia Siemens Networks representative. Send the unit's logs,operating system logs and active alarms to your Nokia SiemensNetworks representative. The logs can be output by using serviceterminal commands ZGD and ZSL. The active alarms can beoutput by using the MML command ZAAP.

If the second supplementary information field has value 01, the diskfile space may have run out because the measurement is so big. Increasethe measurement file size with MML command ZIFF:OMU:<applicationname>:SIZE=<nnnn>;Application name is the name of the VDS-0 device and <nnnn> is the newdisk file size in kilobytes. If the alarm reoccurs, increase the file

DN99580853Issue 08A

105

RNC disturbances (1000-1999) 1222 DATA WRITING VIA VDS DEVICE FAILED

Id:0900d805805de168

size more. The current disk file size can be checked with the MMLcommand ZIFI:OMU:<application name>;

If the second supplemetary information field has value 03, there is anerror situation which probably cannot be corrected without a softwareupdate. Contact your local Nokia Siemens Networks representative.Send the unit's logs, operating system logs and active alarms to yourNokia Siemens Networks representative. The logs can be output byusing service terminal commands ZGD and ZSL. The active alarmscan be output by using the MML command ZAAP.

Cancelling

No cancelling.

106 DN99580853Issue 08A


Id:0900d805805de168

1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART

64 1227 TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTARTMeaning

This alarm is issued when the internal ATM connection management objectnotices an active multiplexer restart when the spare multiplexer cannotbe taken into use.

Occurence of this alarm leads to restarting of the object unit of thealarm. Alarm is set concerning all of the tributary units connected tothe restarted multiplexer.

System restart will take place to recover from the situation if the MXUrestarted is connected to tributary unit that is classified as systemcritical unit.


1 index of the MXU whose restarting caused restarting of the tributary unit

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

107

RNC disturbances (1000-1999) 1228 UNIT SUPERVISION NOT FUNCTIONING

Id:0900d805805de168

65 1228 UNIT SUPERVISION NOT FUNCTION-INGMeaning

Supervision of functional unit(s) is not functioning due toa technical or other problem, or supervision is stopped by the userfor 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 ofthe unsupervised unit.


1 failure reason: 00 User has stopped the unit supervision 01 Unit supervision has been stopped because of a technical problem e.g. some library function call has failed 02 Faulty supervision from RUBBER (RUBBER hasn't got any supervision messages from RUMMAN within 5 minutes)

2 physical address of the functional unit whose supervision has been stopped. In case the supervision of all units has been stopped the value is FFFF.

Instructions

If the supervision has not been stopped by the user and if thedisturbance occurs frequently, fill in a Problem Report and send it toyour local Nokia Siemens Networks representative. Otherwise, noaction is required.

Cancelling

No cancelling.

108 DN99580853Issue 08A


Id:0900d805805de168

1232 EHAT RESTARTED

66 1232 EHAT RESTARTEDMeaning

EHAT plug-in unit has restarted. All the information in the EHAT hasbeen initialized back to default value. The system will, however setthem immediately back to correspond to the actual situation. The systencorrects the situation by updating the external alarm situation and thealarm outputs state to correspond to the reality.


1 HMS number of the cabinet in which the EHAT plug-in unit is located

2 HMS number of the subrack in which the EHAT plug-in unit is located

3 PPA, plug-in unit position address of the EHAT plug-in unit

Instructions

Check if any other alarm is on concerning a fault, that could causethe restart of EHAT and follow the instructions of that alarm. If nosuch alarm is on concerning this fault and if the disturbance appearsfrequently, replace the faulty EHAT plug-in unit indicated in theadditional information of the alarm, see instructions on replacingplug-in units.

Cancelling

No cancelling.

DN99580853Issue 08A

109

RNC disturbances (1000-1999) 1234 UPDATE OF PASSWORD VALIDITY TIMEFAILED

Id:0900d805805de168

67 1234 UPDATE OF PASSWORD VALIDITY TIME FAILEDMeaning

The program block of the user management (URMANA) has failedupdating 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.

110 DN99580853Issue 08A


Id:0900d805805de168

1239 DSP SUPERVISION FAILURE

68 1239 DSP SUPERVISION FAILUREMeaning

An error in the functioning of a DSP has been detected by the supervisionexecuted by Signal Processing Resource Management.As a result of this situation, the operation provided by DSP in questionis not available, or the operation is unreliable.


1 cause of the alarm:

01 no answer from DSP to a supervision inquiry message 02 DSP stopped responding while service was being set up 03 DSP detected a fatal error and requested recovery 04 DSP failed while starting up 05 Reconfiguring DSP to new service pool failed 06 DSP restarted spontaneously 07 Fatal error occurred while releasing DSP resources 08 DSP set up service failed 09 DSP_DEVICE error notification from DSP 10 DSP device failed while starting up 11 Reconfigure dsp pool with forced mode 12 DSP global buffer was empty 13 Deleted channel failed 14 Server service restarted failed 15 Invalid service pool from RM3

Instructions


To gather more information about the nature of the problem, the followingservice terminal commands should be executed in the TPG/DMPG where thealarm was set: clog -sa cat /DSP/rmd_log.txt cat /DSP/rmd_serv.txt

In addition, computer logs from all ISU's/ICSU's shoud be collected.

DN99580853Issue 08A

111

RNC disturbances (1000-1999) 1239 DSP SUPERVISION FAILURE

Id:0900d805805de168

Cancelling

No cancelling.

112 DN99580853Issue 08A


Id:0900d805805de168


69 1240 SCCP DISTURBANCEMeaning

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:

00 international network 0 04 international network 1 08 national network 0 0C national network 1

3 local signalling point code. The signalling point code is interpreted, depending on the value of the first supplementary information field, in the following manner:

01-06 own signalling point where the error was detected 07-08 own signalling point to whose subsystem the local sending was attempted

DN99580853Issue 08A

113

RNC disturbances (1000-1999) 1240 SCCP DISTURBANCE

Id:0900d805805de168

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 interpreted, depending on the value of the first supplementary information field, in the following manner:

01-06 local subsystem, releasing or establishing connection to which failed 07-08 local subsystem to which local sending was attempted (important subsystem) 09-0A local subsystem to which local sending was attempted 0B local subsystem from which the message was received 0C SCCP management subsystem 0D local subsystem to which sending a TCAP message was attempted 0E local subsystem from which a message was received

5 remote signalling point code. The signalling point code is interpreted, depending on the value of the first supplementary information field, in the following manner:

01-06 signalling point of the remote end signalling connection part 07-08 object signalling point of local sending, whose data is being distributed 09-0A signalling point from which the message came 0B local subsystem to which sending a message was attempted 0C local subsystem to which sending an SCCP management message was attempted 0D signalling point from which a TCAP message was received 0E signalling point to which sending a TCAP message was attempted

6 remote subsystem number. If the subsystem number is not known, the value in the field is FF. The subsystem number is interpreted, depending on the value of the first supplementary information field, in the following manner:

01-06 remote end subsystem of the signalling connection 07-08 object subsystem of local sending, whose data is being distributed 09-0A subsystem which send the message 0B remote end subsystem, sending the message to which was attempted 0C SCCP management subsystem, sending the SCCP management message to which was attempted 0D subsystem which has send a TCAP message 0E remote end subsystem to which sending a message was attempted

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

114 DN99580853Issue 08A


Id:0900d805805de168


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 codegiven in the first supplementary information field is 1-6, noactions are required from the user.

Otherwise fill in a Problem report and send it to your localNokia Siemens Networks representative. Enclose the printoutsoutput with the service terminal commands ZSCFE, ZGSC, andZSL in the Problem report.

Cancelling

No cancelling.

DN99580853Issue 08A

115

RNC disturbances (1000-1999) 1241 SCCP GLOBAL TITLE TRANSLATION ANALY-SIS FILE ERROR

Id:0900d805805de168

70 1241 SCCP GLOBAL TITLE TRANSLATION ANALYSIS FILE ERRORMeaning

Report on the analysis disturbances of the SCCP global titletranslation. The global title analysis was not completed becausethe analysed number was not found in the analysis data. The alarmmay have some effect on the traffic capacity of the system.A message that contains the global title in question will not getto 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

116 DN99580853Issue 08A


Id:0900d805805de168

1241 SCCP GLOBAL TITLE TRANSLATION ANALY-SIS FILE ERROR

the address

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





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

DN99580853Issue 08A

117


Id:0900d805805de168

the address


2 record number of the GANFIL

3 global title standard, possible values are:

01 ITU-T 02 ANSI

4 global title indicator in the global title of an SCCP message. The global title indicator is interpreted in following manner when the value in the third supplementary field is 01 (ITU-T):

01 global title contains only the nature of address indicator 02 global title contains only the translation type 03 global title contains the translation type, the numbering plan and the encoding scheme 04 global title contains the translation type, the numbering plan, the encoding scheme and the nature of address indicator 05-15 global title does not contain the translation type, the numbering plan, the encoding scheme or the nature of address indicator. These global title indicator values have not been defined in the ITU-T recommendations

The global title indicator is interpreted in following manner when the value in the third supplementary field is 02 (ANSI):

01 global title contains the translation type, the numbering plan and the encoding scheme 02 global title contains only the translation type 03-15 global title does not contain the translation type, the numbering plan, the encoding scheme or the nature of address indicator. These global title indicator values have not been defined in the ANSI recommendations

5 translation type from the global title of the SCCP message. The translation type is interpreted in the following manner when the value in the third supplementary field is 01 (ITU-T):

00 translation type not in use FF global title does not include translation type

In the national specification ANSI T1.112-1992 there are values defined for the translation type with the third supplementary field value 02 (ANSI) and with the fourth

118 DN99580853Issue 08A


Id:0900d805805de168

1241 SCCP GLOBAL TITLE TRANSLATION ANALY-SIS FILE ERROR

supplementary field value 02. These values of the translation type can be analysed in the normal way, but they do not cause special procedures in the system

6 numbering plan and encoding scheme from the global title of the SCCP message. The encoding scheme is encoded with the least meaningful bits 1-4 in the following manner:

0000 unknown 0001 BCD, odd number of digits 0010 BCD, even number of digits 0011 reserved for future use : 1110 reserved for future use 1111 encoding scheme not included in global title

The numbering plan is encoded with the most meaningful bits 5-8 in the following manner:

0000 unknown 0001 ISDN/telephone network numbering plan (E.164,E.163) 0010 reserved for future use 0011 data network numbering plan (X.121) 0100 telex network numbering plan (F.69) 0101 ship telephone network numbering plan (E.210,E.211) 0110 mobile telephone network numbering plan (E.212) 0111 ISDN/mobile telephone network numbering plan (E.214) 1000 reserved for future use : 1110 reserved for future use 1111 numbering plan not included in global title

7 nature of address indicator from the global title of the SCCP message. Possible values are:

01 subscriber number 02 reserved for national use 03 national meaningful number 04 international number 05 reserved for future use : FE reserved for future use FF nature of address indicator not included in global title

8-15 address information from the global title of the SCCP message so that, for example, the number 12345 is encoded 12 34 5F FF ...

DN99580853Issue 08A

119


Id:0900d805805de168

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 send it to your local Nokia Siemens Networks representative.

Cancelling

No cancelling.

120 DN99580853Issue 08A


Id:0900d805805de168


71 1242 SCCP GLOBAL TITLE TRANSLATION RESULT FILE ERRORMeaning

Report on the output disturbances of the SCCP global titletranslation. The results output record of the global title translationcontains incorrect information or global title modification cannot bedone to the existing global title number. The alarm may have an effectto the traffic capacity of the system. A message that contains theglobal 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). When modifying the global title using the values of this record, the result is an erroneous global title (e.g. too many digits are added or removed)

2 record number of GTRFIL

3 global title standard, possible values are:

01 ITU-T 02 ANSI

4 global title indicator in the global title of an SCCP message. The global title indicator is interpreted in following manner when the value in the third supplementary field is 01 (ITU-T):

01 global title contains only the nature of address indicator 02 global title contains only the translation type 03 global title contains the translation type, the numbering plan and the encoding scheme 04 global title contains the translation type, the numbering

DN99580853Issue 08A

121

RNC disturbances (1000-1999) 1242 SCCP GLOBAL TITLE TRANSLATION RESULTFILE ERROR

Id:0900d805805de168

plan, the encoding scheme and the nature of address indicator 05-15 global title does not contain the translation type, the numbering plan, the encoding scheme or the nature of address indicator. These global title indicator values have not been defined in the ITU-T recommendations

The global title indicator is interpreted in following manner when the value in the third supplementary field is 02 (ANSI):

01 global title contains the translation type, the numbering plan and the encoding scheme 02 global title contains only the translation type 03-15 global title does not contain the translation type, the numbering plan, the encoding scheme or the nature of the address indicator. These global title indicator values have not been defined in the ANSI recommendations

5 translation type from the global title of the SCCP message. The translation type is interpreted in the following manner when the value in the third supplementary field is 01 (ITU-T):


In the national specification ANSI T1.112-1992 there are values defined for the translation type with the third supplementary field value 02 (ANSI) and with the fourth supplementary field value 02. These values of the translation type can be analysed in the normal way, but they do not cause special procedures in the system

6 numbering plan and encoding scheme from the global title of the SCCP message. The encoding scheme is encoded with the least meaningful bits 1-4 in the following manner:

0000 unknown 0001 BCD, odd number of digits 0010 BCD, even number of digits 0011 reserved for future use : 1110 reserved for future use 1111 encoding scheme not included in global title

The numbering plan is encoded with the most meaningful bits 5-8 in the following manner:

0000 unknown 0001 ISDN/telephone network numbering plan (E.164,E.163)

122 DN99580853Issue 08A


Id:0900d805805de168


0010 reserved for future use 0011 data network numbering plan (X.121) 0100 telex network numbering plan (F.69) 0101 ship telephone network numbering plan (E.210,E.211) 0110 mobile telephone network numbering plan (E.212) 0111 ISDN/mobile telephone network numbering plan (E.214) 1000 reserved for future use : 1110 reserved for future use 1111 numbering plan not included in global title

7 nature of address indicator from the global title of the SCCP message. Possible values are:

01 subscriber number 02 reserved for national use 03 national meaningful number 04 international number 05 reserved for future use : FE reserved for future use FF nature of address indicator not included in global title

8-15 address information from the global title of the SCCP message so that, for example, the number 12345 is encoded 12 34 5F FF ...

Instructions

1. If the value of the first supplementary field is 01, use the NBI command of the Global Title Analysis Handling MML (GTAHAN) to check to which result the analysis in question should lead. You may be able to correct the error by loading the GANFIL and GAIFIL files from disk with the MML command DFM to the unit that set the alarm. If the alarm is set only in one computer unit, a unit restart or switchover may correct the situation. If loading the files does not help, remove the analysis in question and the result with the MML commands NBD and NAD. Then recreate them with the MML commands NAC and NBC. Note that removing the result may cause an outage in the traffic.

2. If the value of the first supplementary field is 02, the disturbance may be caused by a file error. It may be possible to correct the error by loading the GTRFIL file from disk with the MML command DFM to the unit that set the alarm. If loading the file does not correct the situation, find out to which signalling point the analysis in question should lead and use the MML command NAM to correct the signalling point code.

DN99580853Issue 08A

123

RNC disturbances (1000-1999) 1242 SCCP GLOBAL TITLE TRANSLATION RESULTFILE ERROR

Id:0900d805805de168

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.

124 DN99580853Issue 08A


Id:0900d805805de168

1244 RUNNING OUT OF MESSAGE BUFFERS

72 1244 RUNNING OUT OF MESSAGE BUFFERSMeaning

The amount of free message buffer memory in one message size class inthe computer is below the alarm limit used in supervision. The alarmlimit is usually set so low that the alarm indicates a criticalreduction in the amount of free message buffers.

When there are no free message buffers, reservation of a message failsand this may disturb the functioning of the computer.

This alarm does not necessarily mean a fault. The alarm can also bean indication of a temporary shortage of free message buffers causedby 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

Instructions

The reduction in the number of free message buffers may result from asoftware fault or from an insufficient number of free message buffersin 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 incase the computer goes to a faulty state or gets restarted.If the situation recurs, it is recommended to inform your local NokiaSiemens Networks representative on the message usage data inorder to find out the nature and cause of the situation. In thiscase, please attach the printouts of the commands mentioned below.

To get the message buffer usage information, start a telnet session forthe computer that is given as the object unit of the alarm, or givethe dmxshow command on the console of the computer.A remote session to the computer (established with the service terminalcommand ZRS or with the MML command ZDDS) should be avoided, because ituses messages and it could even worsen the situation.

1. To get the information on the usage of message buffers, give the service terminal commands

DN99580853Issue 08A

125

RNC disturbances (1000-1999) 1244 RUNNING OUT OF MESSAGE BUFFERS

Id:0900d805805de168

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.

126 DN99580853Issue 08A


Id:0900d805805de168

1246 RESTART OF LEAF UNIT

73 1246 RESTART OF LEAF UNITMeaning

Message connections between the system maintenance computer anda center node have gone down. Because of this, each leaf nodeof the center node will be restarted.


1 unit type of the center computer

2 unit index of the center computer

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

127

RNC disturbances (1000-1999) 1249 DATABASE DISK COPY HAS EXCEEDED MAX-IMUM ALLOWED AGE

Id:0900d805805de168

74 1249 DATABASE DISK COPY HAS EXCEEDED MAXIMUM ALLOWED AGEMeaning

Database dumping has not been successful for a long time due toa high transaction load and the age of the disk copy has reachedits maximum limit. The dumping is now started with an option toprevent transactions when overloading occurs. This strategy isfollowed 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

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.

128 DN99580853Issue 08A


Id:0900d805805de168

1254 UNSOLICITED DATA LINK RE-ESTABLISH-MENT

75 1254 UNSOLICITED DATA LINK RE-ESTAB-LISHMENTMeaning

A connection has been re-established on the D-channel, during whichsome information may have been lost. The alarm usually occurs inconnection with unit restarts, but it can also occur in datatransmission connections of poor quality.


1 number of the channel link set (D-channel)

2 D-channel index within the channel link set:

00 primary channel 01 backup channel (in primary rate access only, not in use)

3 type of the channel link set:

00 primary rate access channel link set 01 subscriber module (SUB) channel link set 02 exchange terminal (ET) channel link set 03 functional unit channel link set

4 number of the D-channel's PCM

Instructions

The alarm requires no actions. If the alarm keeps recurring, check thequality of the connection, and the condition of the equipment.

Cancelling

No cancelling.

DN99580853Issue 08A

129

RNC disturbances (1000-1999) 1258 ERROR IN SPARE UNIT UPDATE

Id:0900d805805de168

76 1258 ERROR IN SPARE UNIT UPDATEMeaning

An error has occured in a spare unit update procedure. Data in thespare unit is not consistent with the working unit. As a consequenceof this alarm, the spare unit is restarted by the recovery system inorder to recover from the data inconsistency.


1 error status given by the process family that has first recognized an error in the spare unit update procedure. You can check its meaning in General Error Messages of System

2 family identifier of the process family that has first recognized an error in the spare unit update procedure

3 process identifier of the process that has first recognized an error in the spare unit update procedure

Instructions


If the problem recurs, fill in a Problem Report and send it to yourlocal Nokia Siemens Networks representative.

Cancelling

No cancelling.

130 DN99580853Issue 08A


Id:0900d805805de168


77 1269 AAL5 FRAME CORRUPTEDMeaning

The post office, which handles message traffic between computers(DMX and Chorus-based computers, respectively) has received abroken AAL5 frame. The object unit of the alarm is the unit whichreceived the corrupted frame.


1 type of the unit from which the broken frame came

2 index of the unit from which the broken frame came

3 virtual channel identifier of the channel from which the broken frame came

4 the internal service category of the failed channel. The field may have the following values:

RT real-time nRT non-real time

5 the type of the active MXU between the SFU and the unit which detected the broken frame. If the unit which detected the broken frame is directly connected to the SFU, this field indicates the type of the unit itself or that of its active unit, if it is the spare unit of a 2N pair

6 the index of the active MXU between the SFU and the unit which detected the broken frame. If the unit which detected the broken frame is directly connected to the SFU, this field indicates the index of the unit itself or that of its active unit, if it is the spare unit of a 2N pair

7 the status received from the AAL5 Segmentation And Reassembly sublayer (SAR). The possible values for the field are hardware-dependent and only for internal use

00 indicates that the sdu contains incorrect header information, e.g. that the sender address differs from the target channel endpoint address

8 length of the observation period in hundredths of a second. If the value is zero, this disturbance was set immediately after the broken frame had been received

9 count of the broken frames with the same status received during

DN99580853Issue 08A

131

RNC disturbances (1000-1999) 1269 AAL5 FRAME CORRUPTED

Id:0900d805805de168

the last observation period

10 total count of the broken frames on the channel

11 number of the AAL5 errors that occurred between the previous alarm 1269 or alarm 1285 and this alarm

Instructions

Usually the disturbance requires no actions. It only informs the userabout temporary problems in the message transmission system.

If the problem persists, then it is most probably due to faultyhardware. Among the object units of the alarm and the units stated inthe supplementary information fields 1 and 2 of the alarm, the objectunit mentioned most often is the suspected unit.

Proceed in the following way to diagnose and locate the fault:

1. Run the diagnosis for the suspected unit.

Change the unit state to TE using the USC command and run the diagnosis using the UDU command.

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

2. Check the cabling of the suspected unit.

Check the physical connections of the plug-in units. Check that the cables are correctly in place and that a correct cable type has been used. If the problem is not in the cabling, proceed to the next step.

3. Replace the suspected 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. The cause of the alarm can be an external disturbance conducted through the power supply. In this case the problem can be solved only by removing the source of the disturbance.

5. If the above processes do not help, fill in a Problem Report and send it to your local Nokia Siemens Networks representative.

132 DN99580853Issue 08A


Id:0900d805805de168


Cancelling

No cancelling.

DN99580853Issue 08A

133

RNC disturbances (1000-1999) 1272 TRIAL CONFIGURATION CANCELLED BYSYSTEM

Id:0900d805805de168

78 1272 TRIAL CONFIGURATION CANCELLED BY SYSTEMMeaning

Trial configuration has been cancelled by system due to some criticalunit failure of the original system. After the canceling, a failedcritical unit of the original system will be replaced with the sametype unit which located in former trial system.


1 the computer address of the functional unit from where the trial cancelling originated

2 the identifier of the process family that originated the cancelling

3 the recovery action. The action taken by recovery is one from the list below:

01 User originated controlled system restart. If active system maintenance unit (OMU) participates in restart, application programs in active OMU are asked for permission to execution

02 User originated forced system restart

03 System restart caused by failure of a system critical unit

04 System restart caused by failure of a system critical unit. Active OMU is included in restart

05 User originated controlled switchover where a working unit is replaced by a hot standby unit without standby restart. The former active unit ends up in SP state. Application programs are asked for permission to execution

06 or 07 Caused by a unit found being in an inappropriate state. The active unit is replaced by a standby unit even if the standby is in TE or SEOU state. If a hot standby exists, a soft switchover (no restart to new active unit) is performed. The former active unit ends up in TE state

08 Caused by a fault observed in an active unit. Active unit is replaced with hot standby unit. Former active unit ends up in TE state. Diagnostics are activated if unit can be

134 DN99580853Issue 08A


Id:0900d805805de168


diagnosed

09 or 0A Caused by an active unit gone inoperative due to e.g. a power failure. Active unit is replaced by standby in SP state. If a hot standby exists, a soft switchover (no restart to new active unit) is performed, disturbed unit ends up in TE state

0B Caused by an active unit making a spontaneous restart. Active unit is replaced by a hot standby, disturbed unit ends up in SP state and is restarted

0C User originated forced switchover where active unit is replaced by a standby in SP state, former active unit ends up in SP state

0D Caused not by a fault but a disturbance in operation of unit, e.g. a critical application failing due to overload. Active unit is replaced by a hot standby, disturbed unit ends up in state SP and is restarted

0E User originated controlled restart of unit. Application programs are asked for permission to execute it

0F User originated forced restart of unit

10 Caused by restart of an active unit, the standby unit is also restarted for synchronization (file and code consistency) reasons

11 A unit is restarted in order to recover from a disturbance, e.g. critical process family failure, in operation

12 User originated controlled state change of unit. Application programs are asked for permission to execution

13 State change of unit requested by system's supervision

14 User originated forced working state change of unit

15 An active unit is put to TE state after it has gone inoperative, e.g. due to power failure

16 or 17 A failed unit is put to TE state. Diagnostics are activated

18 N+1 replaceable unit is put to WO state by system's resource monitoring

19 N+1 replaceable unit is is put to SP state by system's

DN99580853Issue 08A

135

RNC disturbances (1000-1999) 1272 TRIAL CONFIGURATION CANCELLED BYSYSTEM

Id:0900d805805de168

resource monitoring

1A Specific functional unit status bit is set for unit by user

1B Specific functional unit status bit is cleared from unit by user

1C Functional unit gets FLTY status on. The unit has failed but remains in use due to overall situation in network element

22 Functional unit is added or removed to/from network element configuration by user

23 System cancels trial configuration due to critical unit failure on original System

24 Trial configuration is created controlled by user. Initial configuration can be defined to be OMU, CORE or BASE

25 Trial configuration is created forced by user. Initial configuration can be defined to be OMU, CORE or BASE

26 Trial configuration is cancelled by user

27 Functional unit is moved controlled from system to other by user. Unit may not belong to BASE of either side

28 Functional unit is moved forced from system to other by user. Unit may not belong to CORE of either side. Application programs may not prevent the move

29 The units carrying traffic are moved controlled from system to system (cutover of traffic) by user

2A The units carrying traffic are moved forced from system to system (cutover of traffic) by user. Application programs may not prevent the cutover

2B The configuration on trial side made in create can be expanded or reduced to OMU, CORE or BASE by user

2C The configuration on trial side made in create can be expanded or reduced to OMU, CORE or BASE by user. States of units participating are not restricted

4-6 the alarm numbers of the first alarms on the basis of which the cancelling was activated.

In case the trial cancelling was not caused by an alarm,

136 DN99580853Issue 08A


Id:0900d805805de168


the value of the field is FFFF

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

137

RNC disturbances (1000-1999) 1273 ASP ACTIVATION FAILED

Id:0900d805805de168

79 1273 ASP ACTIVATION FAILEDMeaning

The activation of the ASP (Application Server Process) orSGP (Signalling Gateway Process) has not succeeded. The alarmis for ASP if the network element is working as a Signalling Gatewayor for SGP if the network element is working as an Application Server.

The ASP/SGP is activated by the exchange of ASPSM (ASP StateMaintenance), RKM (Routing Key Management) and ASPTM (ASP TrafficMaintenance) messages between the two M3UA endpoints. So when thisalarm 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 messageat which the ASP activation failed. Other reason for the alarm is theinsufficient resources, such as, an insufficient amount of records inwork files which prevents a new ASP to be activated. If none of theASPs in the specified association set in the 4th supplementaryinformation field become active, it means that the whole ApplicationServer or Signalling Gateway is not available to this network element.Otherwise the signal transmission capacity may only be somewhatdecreased.


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

138 DN99580853Issue 08A


Id:0900d805805de168


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, for ex., for ASP the state of which is not inactive 0F the outbound stream count in the communication up notification is less than was ordered in the associate primitive

2 message class of M3UA message. Possible values are:

03 ASP State Maintenance (ASPSM) Messages 04 ASP Traffic Maintenance (ASPTM) Messages 09 Routing Key Management (RKM) Messages

3 message type of M3UA message. Possible values are dependent on the preceding supplementary information field:

When the 2nd supplementary information field is 03, the possible values are:

01 ASP Up (ASPUP) 04 ASP Up Acknowledgement (ASPUP ACK)


01 ASP Active (ASPAC) 03 ASP Active Acknowledgement (ASPAC ACK)


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.

DN99580853Issue 08A

139


Id:0900d805805de168

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, for ex., 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.

140 DN99580853Issue 08A


Id:0900d805805de168


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 key registration, for ex., when handling the REGREQ message. It is also possible that there is no routing context value stored in this network element, which means that the routing key registration was not done. The routing context value stored at this network element is specified in the 6th supplementary information field. The value of the routing context included in the M3UA message is specified in the 5th supplementary information field. The M3UA message, in which the routing context was included is specified in the 2nd and 3rd supplementary fields.

Try to find out why the peer M3UA does not use the correct routing context value, or if the routing context is not stored at this network element (the 6th supplementary information field is 0FFFFFFFF) and if it is possible to configure the peer M3UA so that the routing context parameter is not used in the message.

If that peer M3UA is operating in the Nokia Siemens Networks network element, fill in a Problem Report and send it to your local Nokia Siemens Networks representative. In the problem report include this alarm and the 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

DN99580853Issue 08A

141


Id:0900d805805de168

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. 3) Change the state of the corresponding M3UA based link to AV-EX, with ZNLC MML command. If the routing key registration is turned off, you have to add the ASPs in the corresponding association set (the role of the association set is server) by giving the destination IP addresses of the ASPs.


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.

142 DN99580853Issue 08A


Id:0900d805805de168


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: 1) Change the state of the corresponding M3UA based link to UA-INU, with ZNLC MML command. 2) Change the registration_request parameter giving the association set specified in the 4th supplementary information field and the new value for registration_request parameter as the parameters in ZOYM MML command. 3) Change the state of the corresponding M3UA based link to AV-EX, with ZNLC MML command.

When the 5th supplementary information field is 01 (error-unknown), 05 (permission denied), 06 (cannot support unique routing), 07 (routing key not currently provisioned), 08 (insufficient resources):

Do not use routing key registration at both ends if possible, and at this network element modify the registration_request parameter to value "NO", as follows: 1) Change the state of the corresponding M3UA based link to UA-INU, with ZNLC MML command. 2) Change the registration_request parameter giving the association set specified in the 4th supplementary

DN99580853Issue 08A

143


Id:0900d805805de168

information field and the new value for registration_request parameter as the parameters in ZOYM MML command. 3) Change the state of the corresponding M3UA based link to AV-EX, with ZNLC MML command.

When the 5th supplementary information field is 09 (unsupported RK parameter field):

Check whether the peer M3UA supports network appearance and DPC as a routing key. If the peer M3UA does not currently support network appearance and DPC as a routing key, check if it is possible to configure the peer M3UA such. If not, do not use routing key registration at both ends if possible, and in this network element modify the registration_request parameter to value "NO", as follows: 1) Change the state of the corresponding M3UA based link to UA-INU, with ZNLC MML command. 2) Change the registration_request parameter giving the association set specified in the 4th supplementary information field and the new value for registration_request parameter as the parameters in ZOYM MML command. 3) Change the state of the corresponding M3UA based link to AV-EX, with ZNLC MML command.

When the 5th supplementary information field is 0A (unsupported/ invalid Traffic handling mode):

Check that the value of the traffic handling mode configured at this network element in the association set specified by the 4th supplementary information field is correct. If the value needs to be modified at this network element, use the ZOYM MML command and give the association set and the correct traffic handling mode value as the parameters to the ZOYM MML command.


The local routing key identifier value in the received REGRSP was not the same as it was in the REGREQ sent by this network element (REGRSP is a response message to REGREQ message). The local RK-identifier value that was included in the REGREQ is specified by the 5th supplementary information field and the local RK-identifier value that was included in the REGRSP is specified by the 6th supplementary information field. Try to find out why the peer M3UA does not answer with the correct local RK-identifier value in the REGRSP. If the peer M3UA is operating in the Nokia Siemens Networks network element, fill in a Problem Report and send it to your local Nokia Siemens Networks representative. In the problem report include this alarm and printouts of following

144 DN99580853Issue 08A


Id:0900d805805de168


MML commands ("CM,0" in the following commands refers to active central memory): 1) ZOYI::A; 2) ZDFD:CM,0:A79,,N,; 3) ZDFD:CM,0:AF3,,N,;

If the value of the 1st supplementary information field is 09 or 0A:

Fill in a Problem Report and send it to your local Nokia Siemens Networks representative. In the problem report include this alarm and printouts of following MML commands ("CM,0" in the following commands refer to active central memory): 1) ZOYI::A; 2) ZDFD:CM,0:A79,,N,; 3) ZDFD:CM,0:AF3,,N,;

If the value of the 1st supplementary information field is 0B:

A mandatory parameter is missing in a M3UA message. The parameter tag of the missing parameter is specified in the 7th supplementary information field. Try to find out why the peer M3UA does not use that parameter in the M3UA message specified in the 2nd and 3rd supplementary information field. If the peer M3UA is operating in the Nokia Siemens Networks network element, fill in the Problem Report from this network element and send it to your local Nokia Siemens Networks representative. In the problem report include this alarm and printouts of following MML commands ("CM,0" in the following commands refer to active central memory): 1) ZOYI::A; 2) ZDFD:CM,0:A79,,N,; 3) ZDFD:CM,0:AF3,,N,;

If the value of the 1st supplementary information field is 0C:

Check whether the role specified in the 4th supplementary information field is correct. If not, you have to change the role as follows: 1) Change the state of the corresponding M3UA based link to UA-INU, with ZNLC MML command. 2) Change the role parameter giving the association set specified in the 4th supplementary information field and the new value for the role parameter as the parameters in ZOYM MML command. 3) Change the state of the corresponding M3UA based link to AV-EX, with the ZNLC MML command.

If the value of the 1st supplementary information field is 0D:

The 5th supplementary information field shows the log reference. The 6th supplementary information field shows the unit, from which the communication up was received. At the same time as the alarm two logs are written: first with the same log reference as in the

DN99580853Issue 08A

145


Id:0900d805805de168

alarm, second with the IP address that was not configured. In the second log the first byte shows the IP address version, 0 means IPv4 and 1 means IPv6. Check whether the IP address written to the log should be configured to some association set, which has the role of server. If so, add the IP address to the desired association set with ZOYA MML command.

If the value of the 1st supplementary information field is 0E:

The reason for the alarm may be that the "registration request" parameter has value YES even if it should have value NO. Change the value of the parameter to NO, as follows: 1) Change the state of the corresponding M3UA based link to UA-INU, with the ZNLC MML command. 2) Change the registration_request parameter giving the association set specified in the 4th supplementary information field and the new value = NO for registration_request parameter as the parameters in ZOYM MML command. 3) Change the state of the corresponding M3UA based link to AV-EX, with the ZNLC MML command.

If the value of the 1st supplementary information field is 0F:

SCTP could not establish the association with the configured amount of outbound streams. The amount of streams is configured in the association set basis. Use ZOYI::A; command to see the configured amount of streams that is further specified as the sum of parameters "first data stream number" and "data stream count". This SCTP user adjusted to use the lower amount of outbound streams that was returned in the communication up notification. The amount of SCTP streams that are returned in the communication up notification are shown in the 5th supplementary information field. The amount of configured streams is shown in the 6th supplementary information field.

Cancelling

No cancelling.

146 DN99580853Issue 08A


Id:0900d805805de168

1275 NO RESPONSE FROM CRITICAL UNIT

80 1275 NO RESPONSE FROM CRITICAL UNITMeaning

Critical computer unit from the message transfer point of view has notresponded in the allotted time to a supervision message sent by thesupervisory unit, which is always the system maintenance unit.

This alarm occurs only if the unit is found to be totally incapable ofmessage transmission, a situation when the unit has not responded tosupervision via the normal message transfer mechanism and receiving thestatus of a unit's message transferring system by utilizing theHMS (Hardware Management System) has failed.

If this alarm has occurred, the active unit of a 2N redundant pair isprobably removed from a rack, a normal message connection from SYM unitto the removed unit's pair unit and units below in hardware topology arelost. This means that the switchover cannot be initiated using the normalmessage transferring mechanism. This alarm is used to inform the recoverysystem that performs the necessary recovery actions.


Instructions



Cancelling

No cancelling.

DN99580853Issue 08A

147

RNC disturbances (1000-1999) 1277 PLUG IN UNIT CONNECTION FAILURE

Id:0900d805805de168

81 1277 PLUG IN UNIT CONNECTION FAILUREMeaning

This alarm is issued when some unit fails to acknowledge theHardware Management System (HMS) status inquiry.

An alarm can also be issued if a unit first acknowledges the HardwareManagement System (HMS) status inquiry and then does not send a requestfor port configuration within a certain time period.

Occurence of this alarm leads to restarting of the target unit of thealarm.

Because of the fault, communication with the target unit might not bepossible, and the data transmission channel is out of use, that is,data cannot be sent or received.


Instructions

Check that the plug-in unit of the target unit is properly attachedto its slot in the subrack.

Check that cables connected to the plug-in unit of the target unitare properly attached to their slots.

The alarm supports the activation of automatic recovery for theobject unit, i.e. the unit is restarted.

If you can not find defects from the computer units, and the restartof the units does not remove the problem, contact the local NokiaSiemens Networks representative.

Cancelling

No cancelling.

148 DN99580853Issue 08A


Id:0900d805805de168

1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATION

82 1278 INTEGRITY ERROR IN NETWORK ELEMENT SPLIT INFORMATIONMeaning

Information about network element splitting is located in severaldifferent places. It is being supervised that all these have thesame information about the split status. If the supervisor noticesthat the information is not the same in every place, it sets thisalarm.

The divergence of network splitting information may be caused, forexample, by some file saving error or information distributionfailure. This kind of divergence is most likely to happen when thecreation, deletion or completion of network element splitting fails.This may lead to a malfunction of the whole network element.


1 implicates the kind of trial information inconsistency that was observed 0 not defined 1 system variable defining split state contains inconsistent information 2 functional unit information in SCDFLE contains inconsistent information compared to information in ne_split system variable 3 system variable defining split state contains inconsistent information compared to the information received from Software Configuration Management

2 information about trial status from Software Configuration Management point of view 01 Trial configuration has been created in the network element 00 Trial configuration has not been created in the network element

3 information about own unit slice identifier from Software Configuration Management point of view 0 system has not been split or slice identifier unknown 1 original 2 trial

4 value tells if network element is split, information read from the system variable 0 system has not been split or slice identifier unknown 1 original

DN99580853Issue 08A

149

RNC disturbances (1000-1999) 1278 INTEGRITY ERROR IN NETWORK ELEMENTSPLIT INFORMATION

Id:0900d805805de168

2 trial

5 value tells own unit slice identifier read from the system variable 0 system has not been split or slice identifier unknown 1 original 2 trial

6 type of the unit whose integrity error was observed

7 index of the unit whose integrity error was observed

8 slice identifier of the unit whose integrity error was observed 0 system has not been split or slice identifier unknown 1 original 2 trial

Instructions

Alarm does not require user actions.

Cancelling

No cancellation.

150 DN99580853Issue 08A


Id:0900d805805de168

1281 UNIT IS RESTARTED BECAUSE OF CONFIGU-RATION FAILURE

83 1281 UNIT IS RESTARTED BECAUSE OF CONFIGURATION FAILUREMeaning

This alarm is issued when the internal ATM connection management objectcannot configure a message connection to functional unit.

Possible reasons for the configuration failure could be, for example,a synchronisation error between program blocks or problems in HMSmessaging.

Occurrence of this alarm leads to restarting of the object unit of thealarm. If the restarted unit is MXU, this may cause alarm 1227TRIBUTARY UNIT IS RESTARTED BECAUSE OF ACTIVE MXU RESTART forthe tributary units concerned.

System restart will take place to recover from the situation if theobject unit is MXU and it is connected to tributary unit thatis classified as system critical unit.


1 service or internal stage of execution where configuring the message connection failed

0: port configuration 1: apc first phase initialisation (ingress) 2: apc first phase initialisation (egress) 3: internal interface creation 4: half cross connection creation

2 general error message of the system. You can check its meaning with a command of the service terminal extension MRS or in the General Error Messages of System

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

151

RNC disturbances (1000-1999) 1282 ASSOCIATION PARAMETER FAILURE

Id:0900d805805de168

84 1282 ASSOCIATION PARAMETER FAILUREMeaning

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 atleast one of the Stream Control Transmission Protocol (SCTP) parametersin 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 notnecessarily the values that the user has configured. When the parametersetting 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

152 DN99580853Issue 08A


Id:0900d805805de168

1282 ASSOCIATION PARAMETER FAILURE

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.

0010 SCTP Bundling parameter setting failed.

0020 SCTP SACK parameter setting failed.

Instructions

Fill in a Problem Report and send it to your local Nokia SiemensNetworks representative.

Enclose the printout outputs with the MML commands ZOYI::A; andZOYO; in the failure report. The ZOYI command shows the informationof the SCTP associations and ZOYO shows the SCTP association parametervalues. Enclose also the log writings of the S3ZOCK program block in thecomputer log of the signalling unit identified in the first two fields.Computer log writings can be obtained with service terminal commandsZGD and ZGS.

Cancelling

No cancelling

DN99580853Issue 08A

153

RNC disturbances (1000-1999) 1283 AUTOMATIC IP OVER ATM CHANNEL BRO-KEN

Id:0900d805805de168

85 1283 AUTOMATIC IP OVER ATM CHANNEL BROKENMeaning

Automatic internal IP over ATM channel has broken. The alarmindicates that the internal VCC creation has failed, and theIP connectivity from the CDSP plug-in unit is broken.

The CDSP plug-in unit, which is the other end of the connection,cannot be used for IP calls.


1 type of the terminating computer unit

2 index of the terminating computer unit

3 type of the network interface unit

4 index of the network interface unit

5 IP version. The field can have following values:

04 IPv4 06 IPv6

6 IP traffic behaviour aggregate. The field can have following values:

01 real time traffic class 02 non-real time traffic class 03 generic traffic class

7 general error message of the system. You can check its meaning with a command of the service terminal extension MRS or in the General Error Messages of System

Instructions

Take the computer logs from failed units specified in supplementaryinformation fields 1-4. To display the computer log, give theservice terminal command: clog -s -a

Check the IP interface configuration of the systemwith the following MML command: ZQRI;

Check the status of the IP interface of the terminating computer unit

154 DN99580853Issue 08A


Id:0900d805805de168

1283 AUTOMATIC IP OVER ATM CHANNEL BRO-KEN

with the following MML command: ZQRS:<unit>,<index>:INS,AI0; where <unit> is supplementary information field 1 <index> is supplementary information field 2

Check the status of the IP interface of the network interface unitwith the following MML commands: ZQRS:<unit>,<index>:INS,<ip_if>; ZQMQ::::::AUTO; ZQRS:<unit>,<index>; where <unit> is supplementary information field 3 <index> is supplementary information field 4 <ip_if> is the name of the IP interface (starts with letters "AI" combined with supplementary information field 2, e.g. "AI3")

The system tries to recreate the channel after a short time. If thecreation still fails, the alarm is set again. Restarting of the CDSPplug-in unit might help, if the computer logs indicate problemsin that unit.

If the alarm is shown periodically, contact the local NokiaSiemens Networks representative.

Cancelling

No cancelling

DN99580853Issue 08A

155

RNC disturbances (1000-1999) 1285 AAL5 FRAME LOST

Id:0900d805805de168

86 1285 AAL5 FRAME LOSTMeaning

The post office which handles message traffic between computers(POFFIC and GOFFIC, in DMX and Chorus-based computers, respectively)has detected that one or more incoming AAL5 frames have been lostwithout any error indication from the ATM adaptation layer. Theobject unit of the alarm is the unit where the frame loss wasdetected.


1 type of the unit that sent the lost frame(s)

2 index of the unit that sent the lost frame(s)

3 the virtual channel identifier of the channel from which the frame was lost

4 the internal service category of the failed channel. The field may have the following values:

RT real-time nRT non-real time

5 the type of the active MXU between the SFU and the unit which detected the lost frame. If the unit which detected the lost frame is directly connected to the SFU, this field indicates the type of the unit itself or that of its active unit, if it is the spare unit of a 2N pair

6 the index of the active MXU between the SFU and the unit which detected the lost frame. If the unit which detected the lost frame is directly connected to the SFU, this field indicates the index of the unit itself or that of its active unit, if it is the spare unit of a 2N pair

7 index of the waited sdu (00..7F)

8 index of the received sdu (00..7F)

9 total count of the frames lost on the channel

10 number of the AAL5 errors that occured between the previous 1269 or 1285 alarm and this alarm

156 DN99580853Issue 08A


Id:0900d805805de168

1285 AAL5 FRAME LOST

Instructions

Usually the disturbance requires no actions. It only providesinformation about temporary problems in the message transmissionsystem.

If the problem persists, it is most probably due to faultyhardware. In this case, run a fault diagnosis for the object unitof the alarm and for the unit stated in the supplementaryinformation fields 1 and 2 (with the MML command UDU) to findpossible hardware defects. If the unit is faulty, follow theinstructions of the diagnostics report. If you cannot find defectsin the plug-in unit, contact the local Nokia Siemens Networksrepresentative.

Cancelling

No cancelling.

DN99580853Issue 08A

157

RNC disturbances (1000-1999) 1286 MISMATCH IN SYSTEM CLOCK SIGNAL

Id:0900d805805de168

87 1286 MISMATCH IN SYSTEM CLOCK SIGNALMeaning

The system clock signal for the plug-in unit is selected from the twosystem clock signals that are delivered to each plug-in unit of thesystem. The system clock signal that will be selected for use in eachplug-in unit should be the one that the active Timing and HardwareManagement Bus Unit (TBU) is delivering.

This alarm is set during the start-up phase of a plug-in unit when thesystem has detected that the hardware activity differs from the usedsystem clock signal. The alarm is also issued, when both of thesystem clock signals are missing.

This problem may cause a situation where the unit will not startsuccessfully.


1 number of the rack in which the plug-in unit is located

2 number of the subrack in which the plug-in unit is located

3 location of the plug-in unit in the subrack (=slot number)

4 identifies the index number of active hardware in the plug-in unit specified in the previous supplementary information fields 00: index of hw activity is 0 01: index of hw activity is 1 FF: both system clock signals on the unit are missing

5 identifies the status of clock signals in the unit 00: both system clock signals exist 01: A signal is missing and B signal is used 10: B signal is missing and A signal is used 11: both system clock signals are missing

6 contains coded information about system clock signal availabilities and statuses of HW activities. This field is only for further investigations made by Nokia Siemens Networks

Instructions

1. If the alarm was set during the switchover of TBU, the alarm requires no actions.

2. If the alarm has been set from many plug-in units of a subrack then

158 DN99580853Issue 08A


Id:0900d805805de168

1286 MISMATCH IN SYSTEM CLOCK SIGNAL

continue to the step 4 below.

3. Change the accused plug-in unit, see instructions on replacing plug-in units. The location of the faulty plug-in unit is specified in the supplementary information fields 1-3.

4. If there is also alarm 3017 SYSTEM CLOCK FAILURE and/or alarm 3018 CLOCK DISTRIBUTION FAILURE, the TBUF and/or TSS3 plug-in units that deliver the system clock signals to the subrack must be replaced. See operating instructions of the above mentioned alarms.

5. If the replacing of the unit does not help and the alarm is set again, fill in a Problem Report and send it to your local Nokia Siemens Networks representative. The following information must be included in the Problem Report:5.1 Information about the actions that were carried out in steps 1 and 2 above5.2 Execution printouts of the CM, EA and DP commands of HMEXTE service terminal extension program.5.3 The plug-in unit related information from which the alarm has been set so that the first supplementary information field value stands for the rack value, the second supplementary information field value stands for the subrack value and the third supplementary information field value stands for the PPA value (Note that the PPA value must be given in decimal format). Use the WFI MML command: ZWFI:P:,:<rack>,<subrack>,<ppa>;5.4 The content of the A2TSIG file (use FUTILI service terminal extension program: TN:A2TSIG)5.5 Alarm history. Use MML command ZAHP;

Cancelling

No cancelling.

DN99580853Issue 08A

159

RNC disturbances (1000-1999) 1290 INTER-COMPUTER MESSAGE CONNECTIVI-TY LOST

Id:0900d805805de168

88 1290 INTER-COMPUTER MESSAGE CON-NECTIVITY LOSTMeaning

Message connectivity between the object unit of the alarm and the activeOMU is lost. Depending on the tasks of the unit, the operation of thesystem may be disturbed until the recovery system isolates the faultyunit.


1 type of the unit where the message connectivity loss was observed

2 index of the unit where the message connectivity loss was observed

3 type of the unit whose message connectivity loss was observed first. If the object unit of the alarm is not equal to the unit given in this field, it means that analysis has decided that the defect is in the object unit of the alarm instead of this unit

4 index of the unit whose message connectivity loss was observed first. If the object unit of the alarm is not equal to the unit given in this field, it means that analysis has decided that the defect is in the object unit of the alarm instead of this unit

5 used analysis type that confirmed this failure. The field may have the following values:

01 path analysis used 00 path analysis not used

6 failed computer amount in path analysis. This field is significant only when the 5th supplementary information field is 01. Otherwise the value is 0

Instructions


The alarm supports the activation of the automatic recovery.Check the supporting amount of the alarm with the MML command ARO.

160 DN99580853Issue 08A


Id:0900d805805de168

1290 INTER-COMPUTER MESSAGE CONNECTIVI-TY LOST

Cancelling

No cancelling.

DN99580853Issue 08A

161

RNC disturbances (1000-1999) 1291 SUBRACK CONNECTIVITY FAILURE

Id:0900d805805de168

89 1291 SUBRACK CONNECTIVITY FAILUREMeaning

Subrack presence supervision has detected a communication failure in thedomain of the subrack. The reason for the alarm is either that thefunctional units of the subrack have lost synchronisation or the subrackis without power supply.

The alarm initiates the switchover to the Timing and Hardware ManagementBus Unit (TBU).

If the reason for the failure is a subrack power failure, alarm 3276SUBRACK CONNECTIVITY LOST is also issued to indicate the problem.

If alarm 3276 SUBRACK CONNECTIVITY LOST is not issued and alarm 1291 isissued only concerning one TBU unit of the subrack (the one that was theactive TBU before the switchover), the functional units of the subrackwork normally.

If alarm 1291 is issued concerning both TBUs of the subrack (the subracklocation is given in the supplementary information fields of the alarm),the functional units of the subrack do not work normally.


1 location number of the cabinet where the subrack is located

2 location number of the subrack

Instructions



Cancelling

No cancelling.

162 DN99580853Issue 08A


Id:0900d805805de168


90 1293 SCCP GT SCREENING APPLIEDMeaning

SCCP has detected at the signalling transfer point a signalling messagefor which this alarm must be set. Additionally, also the transit of thesignalling message is to be prevented.This conclusion is based on the calling and the called globaltitles included in the message.

If the transit message is destroyed, it may cause disturbancein the function of the user parts of the signalling point that sentthe message. Usage restrictions for transit messages are usually seton 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 (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

DN99580853Issue 08A

163

RNC disturbances (1000-1999) 1293 SCCP GT SCREENING APPLIED

Id:0900d805805de168

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 02 global title contains only the translation type 03 global title contains the translation type, the numbering plan, and the encoding scheme 04 global title contains the translation type, the numbering plan, the encoding scheme, and the nature of address indicator 05-15 global title does not contain the translation type, the numbering plan, the encoding scheme or the nature of address indicator. These global title indicator values have not been defined in the ITU-T recommendations

The global title indicator is interpreted in the following manner when the value in the most meaningful bits 5-8 is 02 (ANSI):

01 global title contains the translation type, the numbering plan and the encoding scheme 02 global title contains only the translation type 03-15 global title does not contain the translation type, the numbering plan, the encoding scheme or the nature of address indicator. These global title indicator values have not been defined in the ANSI recommendations

7 translation type from the global title included in the calling party address of the processed SCCP message. The translation type values 0 and FF are interpreted in the following manner when the value in the least significant bits 1-4 in the sixth supplementary field is 01 (ITU-T):


164 DN99580853Issue 08A


Id:0900d805805de168


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) 0010 reserved for future use 0011 data network numbering plan (X.121) 0100 telex network numbering plan (F.69) 0101 ship telephone network numbering plan (E.210,E.211) 0110 mobile telephone network numbering plan (E.212) 0111 ISDN/mobile telephone network numbering plan (E.214) 1000 reserved for future use : 1110 reserved for future use 1111 numbering plan not included in global title

The four least meaningful bits of the nature of address indicator is encoded with the least meaningful bits 1-4 in the following manner:

0001 subscriber number 0010 reserved for national use 0011 national meaningful number 0100 international number 0101 reserved for future use : 1110 reserved for future use 1111 nature of address indicator not included in global title

9-11 address information from the global title included in the calling party address of the processed SCCP message so that, for example, the number 12345 is encoded 12 34 5F. If the address information includes more than 6 digits, the address information includes the first 6 digits.

DN99580853Issue 08A

165

RNC disturbances (1000-1999) 1293 SCCP GT SCREENING APPLIED

Id:0900d805805de168

Instructions

SCCP global title screening information says that messages with thecalling global title and the called global title combination in questionshould not be transmitted. The analysis of the calling global title leadsto the calling GTT result as mentioned in the Supplementary informationfield 4. The analysis of the called global title leads to the called GTTresult 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 Supplementaryinformation field 1 (cause code) was 2, the message has been destroyed orsent back. Check if this restriction is justified and remove the blockingwith the MML command ODN if necessary. Otherwise the operator whoowns the signalling point from which the message has been originated,or alternatively the operator who owns the adjacent signalling pointfrom which the message was received, should be notified about an accessright violation.For tracing the operator of the originating signalling point, theinformation supplied in the Supplementary information fields 2, 3, 4, 6,7, 8 and 9 could be used: the Supplementary information fields 2 and 3show the adjacent point from which the message was received;the Supplementary information fields 6, 7, 8 and 9 can be used to getthe calling global title from which the message was originated. TheSupplementary information field 4 (calling GTT result) can also be usedto find out the calling GT via calling GT analysis data, so that thecalling GT analysis is sought using the MML command ZODJ, which leads tothat calling GTT result record.

Cancelling

No cancelling.

166 DN99580853Issue 08A


Id:0900d805805de168

1296 SOCKET CREATION FAILURE

91 1296 SOCKET CREATION FAILUREMeaning

When this alarm occurs it means that socket creation or binding of asocket has failed or the TGP's IP address has not been received. Onereason can be that the IP address has not been configured.


1 the operation 01 socket creation fails 02 socket binding fails 03 could not get own IP address

2 indicates used IP version 01 IPv4 02 IPv6

3 indicates used protocol 01 RTP 02 RTCP 03 not exist

4 the error codes consist of C socket errno values 09 bad file number 13 permission denied 14 bad address 22 invalid argument 23 file table overflow 24 too many open files 38 socket operation on 43 protocol not supported 46 protocol family not supported 47 address family not supported 49 cannot assign requested address 55 no buffer space available

Instructions

If the first supplementary field has the value 01, the limit of the filedescriptions has been exceeded. If this occurs, contact your local NokiaSiemens Networks representative.

If the first supplementary field has the value 02, then a UDP port isalready reserved or the TPG is not configured correctly (for example,the IP address of the TPG is missing). To configure the IP address forthe TPG, see chapter 'Creating Nb interface with IP backbone' in the

DN99580853Issue 08A

167

RNC disturbances (1000-1999) 1296 SOCKET CREATION FAILURE

Id:0900d805805de168

'MGW for MSS Integration' document.

If the alarm is shown periodically, contact your local Nokia SiemensNetworks representative.

Cancelling

No cancelling.

168 DN99580853Issue 08A


Id:0900d805805de168

1297 SOCKET INTERFACE FAILURE

92 1297 SOCKET INTERFACE FAILUREMeaning

An error has occurred in the interface between the Real-Time TransportProtocol (RTP), the Real-Time Transport Control Protocol (RTCP), orthe User Datagram Protocol (UDP) application and the IP stack. RTP,RTCP, or UDP packets cannot be sent to the network or received fromthe network through this socket interface.


1 name of the protocol 01 RTP 02 RTCP 03 UDP

2 the operation 01 packet sending 02 packet receiving

3 the error codes consist of the standard C socket errno values 04d interrupted system 05d I/O error 09d bad file number 11d no more processes 14d bad address 22d invalid argument 27d file too large 28d no space left on 32d broken pipe 35d operation would block 49d can't assign requested address 61d connection refused 65d no route to host

Instructions

If this alarm occurs, there is a problem in the IP stack. Check theinformation on the faulty unit from the alarm and the computer logsof the failed units: - to display the computer log, use the service terminal command clog -sa

If the value in the third supplementary information field is 65d,check your IP configuration with the MML command ZQKB.

Change the state of the TCU unit which has failed with the MML

DN99580853Issue 08A

169

RNC disturbances (1000-1999) 1297 SOCKET INTERFACE FAILURE

Id:0900d805805de168

command QRN and restart it, or replace the unit (for instructions,see the instructions on replacing plug-in units).

If restarting or replacing the unit does not correct the problemand the alarm is shown periodically, contact your local NokiaSiemens Networks representative.

Cancelling

No cancelling.

170 DN99580853Issue 08A


Id:0900d805805de168

1298 DSP INTERFACE FAILURE

93 1298 DSP INTERFACE FAILUREMeaning

If this alarm occurs, there is a fault in a Digital Signal Processor(DSP) or in the Real-time Transport Protocol application (RTP). Aninterface between the RTP application and the DSP cannot be opened ordata cannot be sent to the DSP or received from the DSP through thisinterface.


1 the operation 01 dsp opening 02 dsp reading 03 dsp writing

2 indicates the index of DSP

Instructions

If this alarm occurs, it means that there is a problem in the DSP. Thefailed operation is included in the first supplementary field.If alarms 1239 DSP SUPERVISION FAILURE or 2692 INCORRECT WORKING STATEoccur at the same time, it means that the DSP has been restarted, whichcorrects the problem.

If the alarm is shown periodically, contact your local Nokia SiemensNetworks representative.

Cancelling

No cancelling.

DN99580853Issue 08A

171

RNC disturbances (1000-1999) 1299 RTCP SUPERVISION FAILURE

Id:0900d805805de168

94 1299 RTCP SUPERVISION FAILUREMeaning

Real-time Transport Control Protocol (RTCP) supervision has detectedfailure in a user plane Real-time Transport Protocol (RTP) connection.If this alarm occurs, it means that either there is a problem in theIP network or the peer does not support the RTCP.


1 connection identifier

2 indicates the local RTCP port

3 indicates the usage of RTCP protocol in this connection:

03H RTCP supervision is provisioned in Media Gateway (MGW)

06H RTCP supervision is requested by Media Gateway Controller (MGC) with H.248 for this connection. MGC also requested MGW to send RTCP

07H RTCP supervision is requested by MGC with H.248 for this connection. MGC did not request MGW to send RTCP

4 indicates the transfer status of the last 32 or so rtcp packets. When hexadecimal value is converted to binary value, it indicates if packet receiving succeeded(1) or failed(0)

5 indicates how long a time (in seconds) it has been since the latest RTP packet was received

6 indicates the ip interface type in this connection:

00H IP-trunk 01H IMS IP Multimedia 02H UMA - unlicensed mobile access 03H Semipermanent 04H Nb' 05H IP based Iu-CS 06H UDP

7 indicates call duration in seconds

172 DN99580853Issue 08A


Id:0900d805805de168

1299 RTCP SUPERVISION FAILURE

Instructions

Operating instructions depend on the value of the supplementaryinformation field 3.

If the value is 03H:

If the value 03H is in use in one MGW, and the other MGW does not support the RTCP, the calls will be released as RTCP reports were not received.

Check the used RTCP_FOR_UP_MONITORING from the DSP parameter profile by using the W4I MML command.

In the DSP parameter profile ID field(4), you can see which profile was used in this call.

Check the unit information from the alarm and then check the peer's IP address from the computer logs. To display the computer log, use the service terminal command clog -sa.

If it is possible to change the peer's RTCP configuration, activate RTCP from peer. If this is not possible, change the value of the RTCP_FOR_UP_MONITORING parameter in this MGW to 01H or 02H using the W4M MML command.

If both MGWs support RTCP protocol and this alarm still occurs, it means that there are problems somewhere in the IP network.

RTCP_FOR_UP_MONITORING parameter is described in 'RTP/RTCP in Mobile Media Gateway', Interface Specification.

If the value is 06H or 07H:

In this case MGC request overrides the value of the RTCP_FOR_UP_MONITORING parameter.

Check the unit information from the alarm and then check the peer's IP address from the computer logs. To display the computer log, use the service terminal command clog -sa.

Check the RTCP configuration and compatibility between this MGW and the peer. Check Call Control Signalling (for example, Session Initiation Protocol (SIP) ) and H.248 contents to see where RTCP supervision request originates. Use monitoring tools such as Ethereal and Signalling Monitoring (SIMO).

If the peer supports RTCP protocol and this alarm occurs, it means that there are problems somewhere in the IP network.

DN99580853Issue 08A

173

RNC disturbances (1000-1999) 1299 RTCP SUPERVISION FAILURE

Id:0900d805805de168

Cancelling

The alarm cannot be cancelled.

174 DN99580853Issue 08A


Id:0900d805805de168

1304 ACTOR EXCEPTION

95 1304 ACTOR EXCEPTIONMeaning

Exceptions are generated and detected by the actor when executinginstructions. These exceptions are classified as faults, traps, andaborts.

When an actor exception occurs, the actor supervision system willcause this actor or whole unit to restart after making an operatingsystem log.


1 exception number. Possible values are:

00 Illegal Exception 01 System Reset Exception 02 Machine Check Exception 03 DSI Exception 04 ISI Exception 05 External Interrupt Exception 06 Alignment Exception 07 Program Exception 08 Floating Point Unavailable Exception 09 Decrementer Exception 0C System Call Exception 0D Trace Exception 0E Floating-point assist (optional)

2 exception fault address. If PC value is not inside the code segment, code offset should be 0xFFFFFFFF

3 exception code offset which indicates the failed part. If exception number is not 03 (DSI Exception) or 04 (ISI Exception), fault address should be 0

4 name of the actor that caused the exception. Actor name will be truncated if its length exceeds 8. If the target actor has no name, this field will be empty

5 name of the thread that caused the exception. Thread name will be truncated if its length exceeds 12. If the target thread has no name, this field will be empty

DN99580853Issue 08A

175

RNC disturbances (1000-1999) 1304 ACTOR EXCEPTION

Id:0900d805805de168

Instructions

If the computer has not set alarms on hardware fault,the reason for the exception is probably a software fault.To correct the fault, contact the local Nokia Siemens Networksrepresentative.

Cancelling

No cancelling.

176 DN99580853Issue 08A


Id:0900d805805de168

1331 CDSP MEMORY CONFIGURATION FAILURE

96 1331 CDSP MEMORY CONFIGURATION FAILUREMeaning

Configurable Digital Signal Processing (CDSP) memory configurationfailed when pool-related information in DSP service pool wasreconfigured. The failure was detected when all DSPs in one PowerPCwere changed to another service pool and memory configurationperformed by a PowerPC application failed.


1 identifier of powerPC application

2 error code for the CDSP memory configuration failure

3 the operation mode that caused the alarm

0 = PowerPC application release memory 1 = PowerPC application allocate memory

Instructions



Cancelling

No cancelling.

DN99580853Issue 08A

177

RNC disturbances (1000-1999) 1336 AAL5 CHANNEL USAGE FAILED

Id:0900d805805de168

97 1336 AAL5 CHANNEL USAGE FAILEDMeaning

Local virtual channels between computer units cannot betaken into use.

The object unit of the alarm is the unit where the usagefailure is noticed.


1 the identifier of the channel with usage failure

2 reason for error:

00 VCC opening failed in the local endpoint of the channel 01 sending frame failed 02 receiving frame failed

Instructions

If the situation persists or occurs often, try the following:

1. Check the cabling of the functional units reported in the alarm. Find the cabling instructions in Site documents.

2. With the service terminal command ZSLE, or with command 'olog -s' in Chorus units, check the error log of the operating system to make sure that no major software defects have occurred in either functional unit.

3. With the service terminal command ZGD, or 'clog -s' in Chorus units, check the computer log for possible faults and/or exceptional conditions detected by the software.

4. If defects can be found in the functioning of the software, fill in a Failure Report and send it to the local Nokia Siemens Networks representative. Attach in the Failure Report the contents of the computer log, the operating system log, and the alarm history.

5. If possible, restart (with MML command ZUSU) the object unit of the alarm.

6. If defects cannot be found in the plug-in units, and the restart of functional units did not remove the problem,

178 DN99580853Issue 08A


Id:0900d805805de168

1336 AAL5 CHANNEL USAGE FAILED

contact the local Nokia Siemens Networks representative.

Cancelling

No cancelling.

DN99580853Issue 08A

179

RNC disturbances (1000-1999) 1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT

Id:0900d805805de168

98 1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNITMeaning

Message connectivity between the object unit of the alarm and the activeOMU is lost. When the object unit is a non-redundant unit havingnon-recoverable child units (for example, NIP1, NPS1, NIWU, IWS1, etc.),it cannot be put to TE state and diagnosed. The object unit of the alarmwill be restarted automatically as a recovery action.


1 type of the unit where the message connectivity loss was observed

2 index of the unit where the message connectivity loss was observed

3 type of the unit whose message connectivity loss was observed first. If the object unit of the alarm is not equal to the unit given in this field, it means that the analysis has decided that the defect is in the object unit of the alarm instead of this unit

4 index of the unit whose message connectivity loss was observed first. If the object unit of the alarm is not equal to the unit given in this field, it means that the analysis has decided that the defect is in the object unit of the alarm instead of this unit

5 used analysis type that confirmed this failure. The field may have the following values:

01 path analysis used 00 path analysis not used

6 failed computer amount in path analysis. This field is significant only when the value on the 5th supplementary information field is 01. Otherwise, the value is 0

Instructions


The alarm supports the activation of the automatic recovery.Check the supporting amount of the alarm with the MML command ARO.

180 DN99580853Issue 08A


Id:0900d805805de168

1341 MESSAGE CONNECTIVITY FAILURE IN NON-REDUNDANT UNIT

Cancelling

No cancelling.

DN99580853Issue 08A

181

RNC disturbances (1000-1999) 1425 OVERFLOW IN ALARM BUFFERING

Id:0900d805805de168

99 1425 OVERFLOW IN ALARM BUFFERINGMeaning

The alarm system has received more alarm output tasks thanit is able to buffer for outputting or for sending to theNWI3 interface. However, the alarms that are not output orsent to the NWI3 interface are saved normally in the alarmsystem log file (ALHIST), from which they can be output withan MML command. The alarm is set after all buffered alarmoutput tasks have been processed and sent forward from thealarm system after a buffer overflow.


1 buffer type:

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 NWI3 interface has overflown

2 number of alarms not output or sent to the NWI3 interface

Instructions


Cancelling

No cancelling.

182 DN99580853Issue 08A


Id:0900d805805de168

1431 MMI SYSTEM OVERLOAD

100 1431 MMI SYSTEM OVERLOADMeaning

The MMI system is overloaded.


Instructions



Cancelling

No cancelling.

DN99580853Issue 08A

183

RNC disturbances (1000-1999) 1432 DISTURBANCE IN COMMAND CALENDAR

Id:0900d805805de168

101 1432 DISTURBANCE IN COMMAND CALENDARMeaning

A temporary disturbance has been detected in the commandcalendar operation.

The command calendar interrupts the execution of the calendartask that was being executed and blocks the task. An exceptionis made with those command files that are supposed to be executedmore than once and of which execution is not interrupted althoughsome of the commands in the file fail (marked as NOINT in theCFTYPE 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 beencorrected and the blocking is removed.

If the fault is permanent, then also the alarm 2430, ERROR INCOMMAND CALENDAR, is set.


1 error specification

MML error: 01 creation of MML session has failed 02 interruption in session

error in execution: 03 syntax error 04 semantics error 05 command has failed 06 password check error 07 loading error 08 data transmission error 09 insufficient authority 0A OMU in working state TE or SE 0B contradictory MML program running

COFFER error: 0C command not blocked 0D command not deleted 0E either command or control parameters not available 0F command not transferred to execution queue

IOMANA error: 10 opening of logical file has failed 11 connection of logical file has failed

message exchange error: 12 time-out

2 identifier of the task in the command calendar. This identifier can be seen in the ID column of the execution printout of the MML command ICL and points

184 DN99580853Issue 08A


Id:0900d805805de168


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 theMML session log/MML command log (with the MML command IGO), fromthe command calendar queues (with the MML command ICL) or fromthe execution printouts.

For more information, see instructions on MML commands andcommand 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

DN99580853Issue 08A

185


Id:0900d805805de168

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 MMLcommand has made a memory protection error. Check if the alarm1078, PROCESS EXCEPTION, is set. If the alarm is set, actaccording to its instructions.

If the value of the supplementary information is 03, the commandin the calendar (including the commands of the command files inthe calendar) cannot be executed, because its syntactic structureis faulty. Correct the command with the MML command ICM so thatit conforms to the syntactic rules of the command.

If the value of the supplementary information is 04, the commandin the calendar (including the commands of the command files inthe calendar) cannot be executed, because its semantic structureis faulty. Correct the command with the MML command ICM so thatit conforms to the semantic rules of the command.

If the value of the supplementary information is 05, do thefollowing:

a) If the execution printouts of the calendar tasks are directed to the printer (you can check with the command IID::COMCAL; where the printout are directed to):

1. Check with the MML command ISI, whether the printer is working. The following command outputs information about the printer LPT-0:

ZISI::LPT,0;

2. If the printer does not work, correct the fault (eg. add paper).

3. Remove the blocking from the command with the MML command ICB.

RECOMMENDATION: Direct the printouts also to the BBU-0, if you want that the command calendar is working even when the printer 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).

186 DN99580853Issue 08A


Id:0900d805805de168


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 according to its instructions.

If the value of the supplementary information is 06, there hasbeen a password check error. Fill in a Problem report and send

DN99580853Issue 08A

187


Id:0900d805805de168

it to your local Nokia Siemens Networks representative.

If the value of the supplementary information is 07, loading theMML program that executes the command to memory has failed.Do the following:

1. Check whether the alarm 2427 is set. If 2427 is set, act according to its instructions.

2. If the calendar task has been blocked, remove the blocking with the MML command ICB.

If the value of the supplementary information is 08, there hasbeen a data transmission error. Fill in a Problem report andsend it to your local Nokia Siemens Networks representative.

If the value of the supplementary information field is 09,the calendar task cannot be executed, because:

a) the command calendar has no authority to execute the command or because the user who has added the command into the command calendar has no authority to execute the command.

1. If you want to execute the task from the command calendar, you can change, with the MML command IAA, either the command calendar authorities or the authorities of that user who has added the task into the command calendar. You can use the command IAA only if you have the authority to use it.

2. If the task is blocked, remove the blocking with the MML command ICB.

b) you cannot execute the command from the command calendar. These commands include the interactive commands, that is, those commands that output questions which the user needs to answer before the command can be executed. For example, ICI is an interactive command. Those commands that require the user only to confirm the execution of the command (Y/N) can be executed from the command calendar.

Execute the command normally without using the command calendar.

If the value of the supplementary information is 0A, the calendartask cannot be executed because the OMU is at state TE or SE andan attempt has been made to execute an MML command that must notbe 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 the MML command ICB.

188 DN99580853Issue 08A


Id:0900d805805de168


If the value of the supplementary information is 0B, the calendartask cannot be executed because at the same time that the commandcalendar is executing a specific command, another user is usingsome command that must not be used at the same time with thecommand in question. If, for example, another useris executing the command USU, the command calendar cannot at the same timeexecute the commands of the command group WR.If the command task has been blocked, remove the blocking withthe MML command ICB.

If the value of the supplementary information is 0C, 0D, 0E, 0F,act according to the instructions of the alarm 2430, ERROR INCOMMAND CALENDAR.

If the value of the supplementary information is 10, the logicalfile COMCAL needed in the execution of the calendar tasks has notbeen 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.

DN99580853Issue 08A

189


Id:0900d805805de168

Check whether the COMCAL is in the PLFILEG2 file. The PLFILEG2 file is in the LFILES directory. Output the contents of the file in the following way:

a) Define the directory where you output a file from with the MML command IWX:

ZIWY:S:UNIT=OMU:PATH=LFILES;

b) Output the contents of the file with the MML command IBT:

ZIBT:WDU,S,PLFILEG2,IMG;

If the COMCAL is not found in the PLFILEG2 file, the software build contains the wrong version of the PLFILEG2 file. Contact the local Nokia Siemens Networks representative.

If the COMCAL is in the PLFILEG2 file, there has been an error. Find out the error with the help of alarms and logs.

If the value of the supplementary information is 11, the logical file COMCAL needed in the execution of the calendar tasks is reserved for the execution of another calendar task or some user is changing its connections.

Wait until the other calendar task is finished or that the connections of the COMCAL have been changed.

Cancelling

No cancelling.

190 DN99580853Issue 08A


Id:0900d805805de168

1548 MTP CONFUSION MESSAGE RECEIVED

102 1548 MTP CONFUSION MESSAGE RECEIVEDMeaning

An MTP confusion message has been received in the exchange.The signalling point indicated by the originating pointcode given in the 3rd supplementary information field has notidentified the signalling network management message. Theheading code of the signalling network management messageis 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

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.

DN99580853Issue 08A

191

RNC disturbances (1000-1999) 1569 CRITICAL LIMIT IN SECURITY REPORTINGREACHED

Id:0900d805805de168

103 1569 CRITICAL LIMIT IN SECURITY REPORT-ING REACHEDMeaning

The critical limit of a security reporting counter has been reached.

Supplementary information fields1 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 16 - counter for IMEI IDs in a grey list 17 - counter for unsuccessful saves in service terminal log file 18 - counter for SSH sessions 19 - counter for unauthorised SSH sessions

InstructionsUse the MML command IRO:<report type> to output a detailed securityreport. Check, against the report, if anything out of the ordinaryhas occurred, and modify, if necessary, the limit value of the counterin question so that it reflects more accurately what is considered anormal situation. However, if the counter's value was normal, find outwhy the critical limit was exceeded.

CancellingNo cancelling.

192 DN99580853Issue 08A


Id:0900d805805de168

1570 SECURITY LOG ALARM LIMIT REACHED

104 1570 SECURITY LOG ALARM LIMIT REACHEDMeaning

The number of events written in the Security Reporting Transaction DataFile (LETTER) during a monitoring period has reached the preset alarmlimit.


1 alarm limit of files as a percentage

2 length of monitoring period in days

3 starting date of monitoring period

4 number of event records in file

Instructions

Predefined limit of number of events in some security reporting fileis exceeded. This means, that some security reporting event causessuch a high load that defined file size is not as big as needed.Exact file and incoming events can be investigated using ZIRP andZIRO report.

Cancelling

No cancelling.

DN99580853Issue 08A

193

RNC disturbances (1000-1999) 1590 ALARM SYSTEM MESSAGE SENDING BUF-FER FULL

Id:0900d805805de168

105 1590 ALARM SYSTEM MESSAGE SENDING BUFFER FULLMeaning

A buffer used as a temporary storage for messages, which requirean acknowledgement from the counterpart in the alarm system, hasoverflown. This kind of a buffer is used in the communicationbetween the distributed part and centralised part of the alarmsystem, and in the communication between the centralised part ofthe alarm system and the network element level alarm system.

The buffer overflow may cause temporary unbalance in the alarmsituation maintained in the different parts of the alarm system.It may also lead to loss of some alarms or alarm cancellations.


1 type of buffer 01 buffer for sending messages to next stage

2 family identifier of the sender

3 process identifier of the sender

4 type of the receiver's computer unit See administering recovery and unit working state

5 index of the receiver's computer unit

6 family identifier of the receiver

7 process identifier of the receiver

8 time of the first lost alarm event

9 amount of the lost alarm events

Instructions


Cancelling

No cancelling.

194 DN99580853Issue 08A


Id:0900d805805de168

1597 I/O DEVICE FOUND FAULTY BY ALARM SYS-TEM

106 1597 I/O DEVICE FOUND FAULTY BY ALARM SYSTEMMeaning

The alarm system has found, having received severaldifferent observations to that effect, that the I/Odevice 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 FFFF, subobject not specified

3-8 the alarm manual numbers (in BCD format) of the observations that first supported the fault hypothesis

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

195

RNC disturbances (1000-1999) 1598 UNIT FOUND FAULTY BY ALARM SYSTEM

Id:0900d805805de168

107 1598 UNIT FOUND FAULTY BY ALARM SYSTEMMeaning

The alarm system has found, having received several differentobservations 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 FFFF, subobject not specified

2 index of subobject (of a functional unit) suspected faulty FFFF, subobject not specified

3-8 the alarm manual numbers (in BCD format) of the observations that first supported the fault hypothesis

Instructions


Cancelling

No cancelling.

196 DN99580853Issue 08A


Id:0900d805805de168

1660 UPDATE NUMBER MISMATCH

108 1660 UPDATE NUMBER MISMATCHMeaning

The database management system (abbr. DBMANA) has sentthe database disk updating system, DD2MAN, an update,in which the number (update_seq_number) is inconsistent with thedisk updating system's view of what that number should be. Eitherthe DBMANA or the disk updating system has failed and may have lostlog buffers. The disk updating system will now no longer receive logbuffers from the database in question, and the database will be dumped,i.e. it is copied from the RAM memory to the disk, thus correcting thefailure automatically.


1 database index (although some database applications still need this information, it is becoming more common that the database is identified by the values of the following two supplementary information fields, i.e. database name and database occurrence)

2 database name


4 database location

5 family ID of the program block handling the database

Instructions

The system corrects the fault automatically. If the disturbance keepsrecurring, save the log files of the database unit and the diskupdating system unit, and the alarms, and contact your localNokia Siemens Networks representative.

Cancelling

No cancelling.

DN99580853Issue 08A

197

RNC disturbances (1000-1999) 1661 DATABASE MANAGER IN FATAL ERRORSTATE

Id:0900d805805de168

109 1661 DATABASE MANAGER IN FATAL ERROR STATEMeaning

An error occurred in the database management system, and thesystem has been set to the "fatal error" state. In the "fatalerror" state, the management system program block acknowledgessupervision messages negatively. As the program block is a criticalone, the system resets the database unit.


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


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 blackbox of the unit after the reset for further investigation.

Cancelling

No cancelling.

198 DN99580853Issue 08A


Id:0900d805805de168

1662 DATABASE LOADING ERROR

110 1662 DATABASE LOADING ERRORMeaning

Loading of the database fails. If several load attempts fail,the management system is set to "fatal error" state. Becauseof 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 database occurrence)

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 diskupdating system serving the database.

Reason = 02: Check with the DBS command the state of themanagement system in the database unit's WO side.

Reason = 03: Check with the DBD command the state of the diskupdating system serving the database. Check with the DBS commandthe 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. Savethe log of the disk update system.

Reason = 04: Check with the DBS command the state of themanagement system on the database unit's WO and SP side.Save the log of the database unit's SP side, or, alternatively,save the unit's black box after the reset. Save the log of thedatabase unit's WO side.

DN99580853Issue 08A

199

RNC disturbances (1000-1999) 1662 DATABASE LOADING ERROR

Id:0900d805805de168

Cancelling

No cancelling.

200 DN99580853Issue 08A


Id:0900d805805de168

1663 HAND RESERVATION ERROR IN DATABASE MANAGER

111 1663 HAND RESERVATION ERROR IN DATABASE MANAGERMeaning

The reservation of a transaction or fastread hand fails inthe database management system.


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


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 ofthe service terminal extension Family Utilities (FAMUTI).


Cancelling

No cancelling.

DN99580853Issue 08A

201

RNC disturbances (1000-1999) 1682 SCDFLE UPDATE FAILURE

Id:0900d805805de168

112 1682 SCDFLE UPDATE FAILUREMeaning

The distribution or updating of the Working State and ConfigurationFile (SCDFLE) has failed. If alarm object is not active SYM, therewill be instantenous discrepancy between SCDFLE file of active SYM andalarm object unit.SCDFLE supervision tries to correct discrepancy, if possible.


1 the reason for the failure. See The General Error Messages of System.

2 the type of the unit, whose update failed

3 the index of the unit

4 updating tasks. The hexadecimal value in this field should be interpreted as a binary value, in which case the significance of the bit (0 = task not active/1 = task active) is read in following way: 000000000000000000000001 working state update 000000000000000000000010 unit status update 000000000000000000000100 logical address change 000000000000000000001000 physical address change 000000000000000000010000 2N or N+1 unit switchover 000000000000000000100000 functional unit create 000000000000000001000000 functional unit remove 000000000000000010000000 address tables update 000000000000000100000000 status data update 000000000000001000000000 restart status data update 000000000000010000000000 attribute update 000000000000100000000000 N+1 unit switchover pair create 000000000001000000000000 N+1 unit switchover pair delete 000000000010000000000000 system status update 000000000100000000000000 unit move from trial system to original system 000000001000000000000000 unit move from original system to trial system 000000010000000000000000 network element split create 000000100000000000000000 network element split delete 000001000000000000000000 logical address flush of specified unit instance 000010000000000000000000 logical addresses flush of specified unit type 000100000000000000000000 all logical addresses flush

202 DN99580853Issue 08A


Id:0900d805805de168

1682 SCDFLE UPDATE FAILURE

001000000000000000000000 own slice update

Instructions


Cancelling

No cancelling.

DN99580853Issue 08A

203

RNC disturbances (1000-1999) 1683 PASSIVE UNIT FAULTY

Id:0900d805805de168

113 1683 PASSIVE UNIT FAULTYMeaning

A spare unit of a 2N unit or of a replaceable N+1 redundant unitis faulty.


1 the address of the unit that detected the fault

2 the identifier of the process family that detected the fault

3 the reason for the fault. See General Error Messages of System

4-6 the numbers of the first alarms on the basis of which the unit was found faulty

If the reason of recovery action was not originated by alarm system, the value is FFFF

7 indicates whether the alarm is set by periodical working state background checking 00 alarm is not set by background checking 01 alarm is set by background checking

Instructions


The alarm supports activation of automatic recoveryfor the object unit. You can check the supporting amount of the alarmwith the MML command ZARO.

Cancelling

No cancelling.

204 DN99580853Issue 08A


Id:0900d805805de168

1684 SPARE UNIT WARMUP FAILURE

114 1684 SPARE UNIT WARMUP FAILUREMeaning

The warm-up of the spare unit fails. The reason may be a fault inthe 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 in General Error Messages of System.



5 load group where the warming failed

6 file where the warming failed

Instructions



Cancelling

No cancelling.

DN99580853Issue 08A

205

RNC disturbances (1000-1999) 1685 UNIT RESTART FAILURE

Id:0900d805805de168

115 1685 UNIT RESTART FAILUREMeaning

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 command of the service terminal extension MRS or in General Error Messages of System in customer documentation.



5 load group where the loading failed

6 file where the loading failed

Instructions



Cancelling

No cancelling.

206 DN99580853Issue 08A


Id:0900d805805de168


116 1687 RECOVERY ACTION FAILUREMeaning

The recovery action of the functional unit has failed. If thefailed recovery action was a user-originated controlled recoveryaction (e.g. state change or switchover), the failed recoveryaction had no effect on the network element.If the failed recovery action was a system-originated recovery actionconcerning active functional unit (WO-EX), recovery system may trya new more powerful recovery action after this alarm. If the functionalunit remains active, the operating capacity has decreased dependingon the functionality allocated to the failed functional unit.


1 failed recovery action. The action taken by recovery is one from the list below:

01 User originated controlled system restart. If active system maintenance unit (OMU) participates in restart, application programs in active OMU are asked for permission to execution

02 User originated forced system restart

03 System restart caused by failure of a system critical unit

04 System restart caused by failure of a system critical unit. Active OMU is included in restart

05 User originated controlled switchover where a working unit is replaced by a hot standby unit without standby restart. The former active unit ends up in SP state. Application programs are asked for permission to execution

0C User originated forced switchover where active unit is replaced by a standby in SP state, former active unit ends up in SP state

06 or 07 Caused by a unit found being in an inappropriate state. The active unit is replaced by a standby unit even if it (the standby) is in TE or SEOU state. If a hot standby exists, a soft switchover (no restart to new active unit) is performed. The former active unit ends up in TE state

08 Caused by a fault observed in an active unit. Active unit

DN99580853Issue 08A

207

RNC disturbances (1000-1999) 1687 RECOVERY ACTION FAILURE

Id:0900d805805de168

is replaced with hot standby unit. Former active unit ends up in TE state. Diagnostics are activated if unit can be diagnosed

0D Caused not by a fault but a disturbance in operation of unit, eg. a critical application failing due to overload. Active unit is replaced by a hot standby, disturbed unit ends up in state SP and is restarted

0B Caused by an active unit making a spontaneous restart. Active unit is replaced by a hot standby, disturbed unit ends up in state SP and is restarted

09 or 0A Caused by an active unit gone inoperative due to eg. a power failure. Active unit is replaced by standby in SP state. If a hot standby exists, a soft switchover (no restart to new active unit) is performed, disturbed unit ends up in TE state

0E User originated controlled restart of unit. Application programs are asked for permission to execute it

0F User originated forced restart of unit

11 A unit is restarted in order to recover from a disturbance, e.g. critical process family failure, in operation

10 Caused by restart of an active unit, the standby unit is also restarted for synchronization (file and code consistency) reasons

12 User originated controlled state change of unit. Application programs are asked for permission to execution

14 User originated forced working state change of unit

13 State change of unit requested by system's supervision

16 or 17 A failed unit is put to TE state. Diagnostics are activated

15 An active unit is put to TE state after it has gone inoperative eg. due to power failure

18 N+1 replacable unit is put to WO state by system's resource monitoring

19 N+1 replacable unit is is put to SP state by system's resource monitoring

208 DN99580853Issue 08A


Id:0900d805805de168


1A Specific functional unit status bit is set for unit by user

1B Specific functional unit status bit is cleared from unit by user

1C Functional unit gets FLTY status on. The unit has failed but remains in use due to overall situation in network element

22 Functional unit is added or removed to/from network element configuration by user

23 System cancels trial configuration due to critical unit failure on original System

24 Trial configuration is created controlled by user. Initial configuration can be defined to be OMU, CORE or BASE

25 Trial configuration is created forced by user. Initial configuration can be defined to be OMU, CORE or BASE

26 Trial configuration is cancelled by user

27 Functional unit is moved controlled from system to other by user. Unit may not belong to BASE of either side

28 Functional unit is moved forced from system to other by user. Unit may not belong to CORE of either side. Application programs may not prevent the move

29 The units carrying traffic are moved controlled from system to system (cutover of traffic) by user

2A The units carrying traffic are moved forced from system to system (cutover of traffic) by user. Application programs may not prevent the cutover

2B The configuration on trial side made in create can be expanded or reduced to OMU, CORE or BASE by user

2C The configuration on trial side made in create can be expanded or reduced to OMU, CORE or BASE by user. States of units participating are not restricted

2 computer address of the functional unit where the failed recovery action was observed

3 family identifier which observed the failed recovery action

4 computer address of the functional unit where the error occurred

DN99580853Issue 08A

209

RNC disturbances (1000-1999) 1687 RECOVERY ACTION FAILURE

Id:0900d805805de168

5 family identifier that made the error

6 error code of the failed recovery action. You can check its meaning in general error messages of system

Instructions


Cancelling

No cancelling.

210 DN99580853Issue 08A


Id:0900d805805de168

1800 SCSI ADDRESS ILLEGAL

117 1800 SCSI ADDRESS ILLEGALMeaning

The system has detected an error in the SCSI configuration fileof I/O device state handling. The device in question has anillegal bus number, SCSI ID or logical unit number or it hasthe same bus, ID and logical unit number as some other SCSI device.

State handling of the conflicting device does not work.


1 the SCSI bus of the device in the configuration file

2 the SCSI ID of the device in the configuration file

3 the logical unit number of the device in the configuration file

Instructions

Correct the SCSI configuration file (IDWCONGX.XML). Restart thecomputer unit where the alarm is set with MML command USU.

Cancelling

No cancelling.

DN99580853Issue 08A

211

RNC disturbances (1000-1999) 1801 MASS MEMORY FILE BACKUP FAILURE

Id:0900d805805de168

118 1801 MASS MEMORY FILE BACKUP FAILUREMeaning

A copy task has failed. The I/O system has used backgroung processingto carry out the task but copying some of the files failed.

If alarm 1802, BACKUP COPY LOG FAILURE, is set simultaneously withthis alarm, the system has failed to save all the information on thecopy 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. Usethe MML commands IPI and IPP to interrogate the log of the copytask 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 theidentification number is 40020010, the following command outputsthe general copy task information:

IPI:NAME=COPY_1998,HANDLE=40020010;

The IPP command displays detailed information on the copied filesand directories. If copying a file failed, the printout shows ageneral error message after the file or directory in question.

IPP:NAME=COPY_1998,HANDLE=40020010;

Cancelling

No cancelling.

212 DN99580853Issue 08A


Id:0900d805805de168

1802 BACKUP COPY LOG FAILURE

119 1802 BACKUP COPY LOG FAILUREMeaning

Saving the copy task information in the disk's copy log has failedat least partly.

The fault may have been caused, for example, by a disturbance in theI/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 thedefined time period.

If alarm 1801, MASS MEMORY FILE BACKUP FAILURE, is set simultaneouslywith this alarm, the background processing of the backup copy taskhas been interrupted. Otherwise, the copy task itself has succeededbut the system was not able to record all the information connectedto 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 disturbanceor a fault has been detected in the disk system and it has preventedthe 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 in General Error Messages of System

2 name identifier of the copy task whose recording in the copy log failed. The name is an ASCII string

Instructions

It may be possible to interrogate information on the copy taskmentioned in Supplementary information field 2 with the MML commandsIPI and IPP. The I/O system has however failed to record some (orpossibly all) information.

You may find more information in the system log, which you caninterrogate with the service terminal command ZGD.

If alarm 1801, MASS MEMORY FILE BACKUP FAILURE, is not setsimultaneously with this alarm for the same copy task, the copytask was successful, even though information on it is not availablein the log.

DN99580853Issue 08A

213

RNC disturbances (1000-1999) 1802 BACKUP COPY LOG FAILURE

Id:0900d805805de168

If alarm 1801 is also set, you should start the copy task again.

Cancelling

No cancelling.

214 DN99580853Issue 08A


Id:0900d805805de168

1803 SCSI MALFUNCTION

120 1803 SCSI MALFUNCTIONMeaning

The system has detected a temporary (not serious) error while accessinga SCSI device. If the error is not temporary, the device may be faultyand the system will diagnose it.

The fourth additional information field indicates the cause forthis disturbance.


1 the SCSI bus the device is connected to

2 the SCSI ID of the device

3 the logical unit number of the device

4 general error message of the system. You can check its meaning with a command of the service terminal extension MRS (see instructions on the service terminal) or in the General Error Messages of System

Instructions

If the alarm appears occasionally, it requires no actions.

The alarm supports the activation of the automatic recovery for theobject unit. You can check the supporting amount of the alarm usingthe ARO MML command.

If the device is diagnosed to be faulty it has to be replaced. Seeinstructions on changing mass memory units.

If the diagnostics indicate that the device is working properly and theproblem still persists, contact your local Nokia Siemens Networksrepresentative.

Cancelling

No cancelling

DN99580853Issue 08A

215

RNC disturbances (1000-1999) 1804 IP ROUTING RESOURCE SHORTAGE

Id:0900d805805de168

121 1804 IP ROUTING RESOURCE SHORTAGEMeaning

The IP Routing feature is experiencing an unexpected resourceshortage.

The IP routing capability of the system is temporarily reduceduntil the routing database has been reconstructed from neighboringrouters.

The telephony capabilities of the switch are not affected.


Instructions

Fill in a Problem Report and send it to your local technicalsupport.

Cancelling

No cancelling.

216 DN99580853Issue 08A


Id:0900d805805de168

1806 PRINTER SPOOLER DISABLED

122 1806 PRINTER SPOOLER DISABLEDMeaning

Printing system cannot use the spooler. This happens, for example,when the SCSI bus or hard disks go to TEST state. The failure doesnot disable the printing system, but new printing tasks are handledin non-spoolered mode. Handling printing tasks in non-spoolered mode ismore unreliable than in spoolered mode.

The tasks that are in spooler when failure occurs, are executedwhen the spooler is in use again. The system changes automatically fromthe non-spoolered mode to the spoolered mode when the spooler isin use again and all non-spoolered tasks are completed.


Instructions

To find out the reason for SCSI bus's or hard disk's wrong operatingstate, check whether there are other alarms active using the AAP MMLcommand. Follow the instructions given in these alarm descriptions.

Set the SCSI bus and hard disks to WO state using the IHE MML command,if possible.

Cancelling

No cancelling.

DN99580853Issue 08A

217

RNC disturbances (1000-1999) 1809 IP CONFIGURATION INQUIRY SERVICEFAILED

Id:0900d805805de168

123 1809 IP CONFIGURATION INQUIRY SERVICE FAILEDMeaning

The alarm is set if IP management dynamic interface library (YANLIB)cannot provide IP configuration inquiry services for applications.Under this situation, the applications will get "no service" returncode when calling the library routines. If the application has failedto receive IP configuration data, it might make the Network Elementunable to provide IP calls services.


Instructions

Check the computer log to find out the possible cause of the alarm.Fill in a Problem Report and send it to your local Nokia SiemensNetworks representative.

Here are the possible problems:

1. IP configuration files (/etc/if.dat, /etc/ipoa.conf, /etc/ipoa_int.dat,/RUNNING/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.

218 DN99580853Issue 08A


Id:0900d805805de168

1809 IP CONFIGURATION INQUIRY SERVICE FAILED

Cancelling

No cancelling.

DN99580853Issue 08A

219

RNC disturbances (1000-1999) 1900 DEGRADED SLIP FREQUENCY

Id:0900d805805de168

124 1900 DEGRADED SLIP FREQUENCYMeaning

The ET has observed that the clock frequency slips on the incomingE1 or T1 circuit exceed the alarm limit defined for the ET. The slipsare 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.

Instructions


Cancelling

No cancelling.