BTS S2000H_S2000L_e-Cell Fault Clearing

Global System for Mobile Communications (GSM)Nortel GSM BTSS2000H/S2000L/e-cell FaultClearingRelease: V18.0 PC2Document Revision: 18.05

www.nortel.com

411-9001-104.

Global System for Mobile Communications (GSM)Release: V18.0 PC2Publication: 411-9001-104Document release date: 2 February 2010

Copyright 1999-2009 Nortel Networks. All Rights Reserved.

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OFANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Sourced in Canada, France, and the United States of America.

LEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OFANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject to change without notice.

Nortel, the Nortel logo, the Globemark, S8000 and S2000 are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

_ 17+ 18+

All other trademarks are the property of their respective owners.

.

3.

ContentsNew in this release 19Features 19

Introduction 21

Chapter 1 How to use this manual 231.1 Introduction 231.2 The types of spontaneous messages 23

1.2.1 Events detected by the BTS 231.2.2 Events detected by the BSC 24

1.3 Description of a fault number sheet 241.3.1 Header of the sheet 241.3.2 Main body of the sheet 24

Chapter 2 S2000 H/L BTS fault numbers 272.1 Fault number: 1051 (S2000 H/L BTS) 272.2 Fault number: 1052 (S2000 H/L BTS) 27

2.2.1 Source 0: No response to status request 362.2.2 Source 1: Bad hardware reference or manufacturer ID 382.2.3 Source 2: SUP stop receipt 402.2.4 Source 3: No change to one of BOOT after reset 432.2.5 Source 4: This entity is engaged in another downloadingSource 8: Wrong

software reference on a non downloadable TEI 452.2.6 Source 5: Software not compatible with hardware 472.2.7 Source 6: File access error 512.2.8 Source 7:Repetitive errors (NACK, timeout, ...) while downloading a

file 542.2.9 Source 9: No response to download message 552.2.10 Source 14: Received CSM LOAD CONTAINER NAK 572.2.11 Source 15: File to download empty 592.2.12 Source 16: File to download unavailable 622.2.13 Source 17: Buffer allocation failure 622.2.14 Source 18: Bad sending buffer size value 652.2.15 Source 19: Failure during OMU switchover 672.2.16 Source 20: Bad TEI sent by BTS in the CSM software update report

message 69

Global System for Mobile Communications (GSM)Nortel GSM BTS S2000H/S2000L/e-cell Fault Clearing

411-9001-104 18.05 2 February 2010


.

42.2.17 Source 21: CSM software update report with the cause - unknown TEI- 72

2.2.18 Source 22: CSM software update report with the cause - equipmentfailure - 74

2.2.19 Source 23: CSM software update report with the cause - downloadingfailure - 76

2.2.20 Source 24: CSM software update report with the cause - not able toperform- 79

2.2.21 Source 25: CSM software update report with the cause - wrong softwarereference - 81

2.2.22 Source 26: CSM software update report with the cause - wrongconfiguration reference - 83

2.2.23 Source 27: CSM software update report with the cause - restart request- 86

2.2.24 Source 28: CSM software update report with the cause - datainconsistency - 88

2.2.25 Source 29: CSM software update report with the cause - message out ofsequence - 90

2.2.26 Source 30: CSM software update report with the cause - background notavailable - 93

2.2.27 Source 31: CSM software update report with the cause - incompatibleRM version - 95

2.2.28 Source 32: CSM software update report with the cause - downloading inprogress - 97

2.2.29 Source 33: Bad report sent by BTS in the CSM software update reportmessage 100

2.2.30 Source 34: No BTS response on CSM software update init-controlmessage 102

2.2.31 Source 35: Nack received on the abort requested by operator 1042.2.32 Source 36: Bad report sent by BTS in the CSM software update abort

message 1072.2.33 Source 37: No BTS response on CSM software update abort

message 1092.2.34 Source 38: Flash activate nack with the cause - unknown TEI - 1112.2.35 Source 39: Flash activate nack with the cause - equipment failure

- 1132.2.36 Source 40: Flash activate nack with the cause - downloading failure

- 1162.2.37 Source 41: Flash activate nack with the cause - not able to perform

- 1182.2.38 Source 42: Flash activate nack with the cause - flash inconsistency

- 1202.2.39 Source 43: Flash activate nack with the cause - data inconsistency

- 1222.2.40 Source 44: Flash activate nack with the cause - wrong soft ref - 1252.2.41 Source 45: Flash activate nack with the cause - wrong config ref - 1272.2.42 Source 46: CSM downloading start nack with the cause - unknown TEI


411-9001-104 18.05 2 February 2010


.

5- 1292.2.43 Source 47: CSM downloading start nack with the cause - equipment

failure - 1312.2.44 Source 48: CSM downloading start nack with the cause - downloading

failure - 1342.2.45 Source 49: CSM downloading start nack with the cause - message out

of sequence - 1362.2.46 Source 50: CSM downloading start nack with the cause - wrong soft ref

- 1382.2.47 Source 51: CSM downloading start nack with the cause - wrong config

ref - 1412.2.48 Source 52: CSM downloading start nack with a bad cause 1432.2.49 Source 53: No BTS response on CSM downloading start message 1452.2.50 Source 54: CSM downloading end nack with the cause - unknown TEI

- 1472.2.51 Source 55: CSM downloading end nack with the cause - equipment

failure - 1502.2.52 Source 56: CSM downloading end nack with the cause - downloading

failure - 1522.2.53 Source 57: CSM downloading end nack with the cause - value out of

range - 1542.2.54 Source 58: CSM downloading end nack with a bad cause 1562.2.55 Source 59: No BTS response on CSM downloading end message 1592.2.56 Source 60: CSM load init nack with the cause - equipment failure - 1612.2.57 Source 61: CSM load init nack with the cause - downloading failure

- 1632.2.58 Source 62: CSM load init nack with the cause - message out of

sequence - 1652.2.59 Source 63: CSM load init nack with the cause - wrong file ref - 1682.2.60 Source 64: CSM load init nack with the cause - window size not allowed

- 1702.2.61 Source 65: CSM load init nack with the cause - data format error - 1722.2.62 Source 66: CSM load init nack with a bad cause 1752.2.63 Source 67: No BTS response on CSM load init message 1772.2.64 Source 68: CSM load data nack with the cause - equipment failure

- 1792.2.65 Source 69: CSM load data nack with the cause - downloading failure

- 1812.2.66 Source 70: CSM load data nack with the cause - message out of

sequence - 1842.2.67 Source 71: CSM load data nack with the cause - data format error

- 1862.2.68 Source 72: CSM load data nack with the cause - window overflow

- 1882.2.69 Source 73: CSM load data nack with the cause - data inconsistency

- 190


411-9001-104 18.05 2 February 2010


.

62.2.70 Source 74: CSM load data nack with the cause - block not received- 193

2.2.71 Source 75: CSM load data nack with the cause - bad block tag - 1952.2.72 Source 76: CSM load data nack with the cause - checksum error - 1972.2.73 Source 77: CSM load data nack with a bad cause 1992.2.74 Source 78: Unexpected CSM load data ack 2022.2.75 Source 79: No BTS response on CSM load data message 2042.2.76 Source 80: CSM load end nack with the cause - equipment failure

- 2062.2.77 Source 81: CSM load end nack with the cause - downloading failure

- 2082.2.78 Source 82: CSM load end nack with the cause - value out of range

- 2112.2.79 Source 83: CSM load end nack with the cause - message out of

sequence - 2132.2.80 Source 84: CSM load end nack with the cause - data format error

- 2152.2.81 Source 85: CSM load end nack with the cause - wrong file ref - 2172.2.82 Source 86: CSM load end nack with the cause - data inconsistency

- 2202.2.83 Source 87: CSM load end nack with the cause - checksum error - 2222.2.84 Source 88: CSM load end nack with a bad cause 2242.2.85 Source 89: No BTS response on CSM load end message 2262.2.86 Source 90: Bad report sent by BTS during an internal update 2292.2.87 Source 91: CSM load init nack with the cause - file already open - 2312.2.88 Source 92: CSM load init nack with the cause - invalid mode - 2332.2.89 Source 93: CSM load init nack with the cause - file cannot be unloaded

- 2352.2.90 Source 94: CSM load init nack with the cause - flash flag cannot access

- 2382.2.91 Source 95: CSM load data nack with the cause - file cannot be unloaded

- 2402.2.92 Source 96: CSM load data nack with the cause - flash flag cannot

access - 2422.2.93 Source 97: CSM load data nack with the cause - boot cannot be

unloaded - 2442.2.94 Source 98: CSM load data nack with the cause - data decode error

- 2472.2.95 Source 99: CSM load data nack with the cause - table cannot access

- 2492.2.96 Source 100: CSM load data nack with the cause - RAM mapping error

- 2512.2.97 Source 101: CSM load data nack with the cause - flash access error

- 2542.2.98 Source 102: CSM load data nack with the cause - flash RAM error

- 256


411-9001-104 18.05 2 February 2010


.

72.2.99 Source 103: CSM load data nack with the cause - flash erase error- 258

2.2.100 Source 104: CSM load data nack with the cause - internal abort - 2602.2.101 Source 105: CSM flash activate response with a bad cause 2632.2.102 Source 106: DTM error during token allocation 2652.2.103 Source 107: CSM software update report with the cause: TRX software

incompatibility 2672.2.104 Source 108: Too many different deliveries in the cell group 269

2.3 Fault number: 1053 (S2000 H/L BTS) 2722.4 Fault number: 1054 (S2000 H/L BTS) 2732.5 Fault number: 1055 (S2000 H/L BTS) 273

2.5.1 Source 1: Equipment failure 2782.5.2 Source 2: Equipment unable to perform such test 2782.5.3 Source 3: Invalid configuration 2792.5.4 Source 4: Unknown test 2812.5.5 Source 5: Cell parameters inconsistency 2812.5.6 Source 6: Data inconsistency 2822.5.7 Source 7: Value out of range 2842.5.8 Source 8: TEI not present 2852.5.9 Source 9: Unknown Abis PCM_Time_Slot 2862.5.10 Source 10: Unknown Abis PCM 2862.5.11 Source 11: Wrong software reference 2872.5.12 Source 12: Further files required 2872.5.13 Source 13: Failure during activation 2872.5.14 Source 14: Data format error 2882.5.15 Source 15: Window overflow 2882.5.16 Source 16: Normal completion 2882.5.17 Source 17: Transfer aborted 2882.5.18 Source 18: Checksum error 2882.5.19 Source 19: File incomplete 2892.5.20 Source 20: File already present and correct 2892.5.21 Source 21: File cannot be downloaded 2892.5.22 Source 22: Entity engaged in other download 2892.5.23 Source 23: Too many signaling timeslots 2892.5.24 Source 24: Too many TEI connections to physical channel 2912.5.25 Source 25: Out of sequence message 2912.5.26 Source 26: Incorrect IEI 2932.5.27 Source 27: Wrong file reference 2932.5.28 Source 28: Bad cell number 2942.5.29 Source 29: Bad related TEI 2942.5.30 Source 30: Bad timeslot 2942.5.31 Source 31: Window size not allowed 2942.5.32 Source 32: Flash boot required 2942.5.33 Source 33: Wrong config reference 295


411-9001-104 18.05 2 February 2010


.

82.5.34 Source 34: The BTS has not acknowledged the TX power consignrequest 295

2.5.35 Source 35: Downloading aborted 3002.5.36 Source 36: Files missing 3002.5.37 Source 37: Buffer overflow 3002.5.38 Source 38: Block not received 3012.5.39 Source 39: Downloading restart 3012.5.40 Source 40: Request not supported 3012.5.41 Source 41: Downloading failure 3012.5.42 Source 42: Start-up failure 3012.5.43 Source 43: Maximum number of joker TS 3022.5.44 Source 44: Bad chain type 3052.5.45 Source 45: Bad radio timeslot reference 3052.5.46 Source 46: Bad internal Link EDGE configuration 3052.5.47 Source 47: Inconsistency mapping 3052.5.48 Source 48: Inconsistency number of joker DS0 3052.5.49 Source 49: Invalid mode 3062.5.50 Source 50: File already open 3062.5.51 Source 51: File cannot be unloaded 3062.5.52 Source 52: Boot cannot be unloaded 3062.5.53 Source 53: Data decode error 3062.5.54 Source 54: Flash flag cannot access 3072.5.55 Source 55: Table cannot access 3072.5.56 Source 56: RAM mapping error 3072.5.57 Source 57: Flash access error 3072.5.58 Source 58: Flash write error 3072.5.59 Source 59: Flash erase error 3082.5.60 Source 60: Internal abort 3082.5.61 Source 61: Equipment not able to get external synchronization 3082.5.62 Source 62: Synchronization in progress 3082.5.63 Source 63: Dynamic Abis feature not supported 3082.5.64 Source 64: Inconsistent number of joker DS0 3092.5.65 Source 65: Exceeded DL joker DS0 pool number 3122.5.66 Source 255: Non-significant value 314

2.6 Fault number: 1056 (S2000 H/L BTS) 3142.6.1 Source 0: Incorrect priority on transceiver 3162.6.2 Source 1: Incorrect setting of channel on transceiver 3172.6.3 Source 2: Cell without BCCH TDM 3172.6.4 Source 3: Radio Time Slot not used 3172.6.5 Source 4: Wrong value for BSS TEI in T1 mode 3172.6.6 Source 5: Cell cfg with cavity and dual band not acceptable 3182.6.7 Source 6: Missing Site management Abis GSM function 3182.6.8 Source 7: Missing Abis Signalling management Abis GSM function 3182.6.9 Source 8: Missing Abis traffic management Abis GSM function 318


411-9001-104 18.05 2 February 2010


.

92.6.10 Source 9: Missing RfTrans management Abis GSM function 3182.6.11 Source 10: Missing cell management Abis GSM function 3192.6.12 Source 11: Missing TDMA management Abis GSM function 3192.6.13 Source 12: Missing TS management Abis GSM function 3192.6.14 Source 13: The TDMA exists in RDC but the object was not created.

3192.6.15 Source 14: Too many EDGE TDMAs (more than 16 per site) configured

3202.7 Fault number: 1058 (S2000 H/L BTS) 3202.8 Fault number: 1059 (S2000 H/L BTS) 3212.9 Fault number: 1060 (S2000 H/L BTS) 322

2.9.1 DRX (source: Frequency collision on FH bus) 3242.9.2 DRX (source: Beginning of TX isolation for maintenance) 3242.9.3 DRX (source: End of TX isolation for maintenance) 3252.9.4 DRX (source: FACCH congestion) 3252.9.5 DRX (source: Nack answer) 3262.9.6 DRX (source: DRX reset by BSC) 3272.9.7 SBCF board (source: Unknown message on Abis interface) 3272.9.8 SBCF board (source: Restart due to reset by BSC) 3272.9.9 SBCF boards (source: Restart due to reset by reset button) 3272.9.10 SBCF boards (source: Restart due to power on) 3282.9.11 SBCF boards (source: Restart due to a too long PCM scanning) 3282.9.12 SBCF boards (source: Restart requested by the active board) 3282.9.13 SBCF boards (source: Restart due to a software upgrade) 3292.9.14 SBCF boards (source: Restart due to hardware watchdog) 3292.9.15 SBCF boards (source: Restart due to double bus fault) 3292.9.16 SBCF boards (source: restart due to Man Machine Interface I and C

reset button) 3292.10 Fault number: 1061 (S2000 H/L BTS) 3302.11 Fault number: 1067 (S2000 H/L BTS) 330

2.11.1 ABIS_BTS_SYNCHRO (source: SYNO clock not locked on the network)(S2000H BTS) 344

2.11.2 ABIS_BTS_SYNCHRO (source: SYNO clock not locked on the network)(S2000L BTS) 349

2.11.3 AC power supply (source: Power fault) (S2000H BTS) 3542.11.4 AC power supply (source: Power fault) (S2000L BTS) 3572.11.5 Cabinet high temperature alarm (source: Threshold exceeded) 3602.11.6 Cabinet low temperature alarm (source: Threshold exceeded) 3632.11.7 DC power supply (source: Power fault) (S2000H BTS) 3662.11.8 DC power supply (source: Power fault) (S2000L) 3692.11.9 External alarm (source: External alarm) 3732.11.10 DRX (source: RX fault) 3732.11.11 DRX (source: Loss of PCM link) 3762.11.12 DRX (source: BBFILTER ASIC fault) 378


411-9001-104 18.05 2 February 2010


.

10

2.11.13 DRX (source: Self test failed) 3812.11.14 DRX (source: Major fault on TX) (S2000H BTS) 3832.11.15 DRX (source: Major fault on TX) (S2000L BTS) 3862.11.16 DRX (source: DRX link) (S2000H BTS) 3882.11.17 DRX (source: DRX link) (S2000L BTS) 3912.11.18 DRX (source: The TX has not acknowledged the power consign

request) 3932.11.19 DRX (source: PA DRX control loop fault) (S2000H BTS) 3972.11.20 DRX (source: PA DRX control loop fault) (S2000L BTS) 4002.11.21 DRX diversity reception chain (source: Software detection) (S2000H

BTS) 4032.11.22 DRX diversity reception chain (source: Software detection) (S2000L

BTS) 4052.11.23 DRX main reception chain (source: Software detection) (S2000H

BTS) 4082.11.24 DRX main reception chain (source: Software detection) (S2000L

BTS) 4102.11.25 LNA (source: Software detection) (S2000H BTS) 4122.11.26 LNA (source: Software detection) (S2000L BTS) 4152.11.27 PA (source: Hardware) (S2000H BTS) 4172.11.28 PA (source: Hardware) (S2000L BTS) 4192.11.29 PA (source: DRX/PA connection) (S2000H BTS) 4212.11.30 PA (source: DRX/PA connection) (S2000L BTS) 4242.11.31 PCM (source: PCM) 4262.11.32 RX splitter D (source: Over current) (S2000H BTS) 4262.11.33 RX splitter D (source: Over current) (S2000L BTS) 4292.11.34 RX splitter M (source: Over current) (S2000H BTS) 4312.11.35 RX splitter M (source: Over current) (S2000L BTS) 4342.11.36 Splitter output (source: Over current) (S2000H BTS) 4362.11.37 Splitter output (source: Over current) (S2000L BTS) 4382.11.38 Transmit antenna (source: VSWR) (S2000H BTS) 4412.11.39 Transmit antenna (source: VSWR) (S2000L BTS) 4432.11.40 VGA (source: Fault on VGA) (S2000H BTS) 446

2.12 Fault number: 1070 (S2000 H/L BTS) 4482.13 Fault number: 1073 (S2000 H/L BTS) 448

2.13.1 Source 9: No response to LOAD message 4502.13.2 Source 10: Received LOAD INIT NACK 4502.13.3 Source 11: Received message LOAD DATA NACK 4502.13.4 Source 12: Received message LOAD END NACK 4502.13.5 Source 13: Received message 450

2.14 Fault number: 1080 (S2000 H/L BTS) 451FAULT ANALYSIS 451

2.15 Fault number: 1165 (S2000H, S2000L) 4522.16 Fault number: 1258 (S2000 H/L BTS) 452


411-9001-104 18.05 2 February 2010


.

11

2.17 Fault number: 1259 (S2000 H/L BTS) 4542.18 Fault number: 1265 (S2000 H/L BTS) 4552.19 Fault number: 1266 (S2000 H/L BTS) 4562.20 Fault number: 1268 (S2000 H/L BTS) 4572.21 Fault number: 1500 (S2000 H/L BTS) 4582.22 Fault number: 1505 (S2000 H/L BTS) 4592.23 Fault number: 1508 (S2000H/L) 4602.24 Applicability of the fault numbers to the BTS type 461

Chapter 3 e-cell fault numbers 4633.1 Fault number: 1051 (e-cell) 4633.2 Fault number: 1052 (e-cell) 463

3.2.1 Source 0: No response to status request 4723.2.2 Source 1: Bad hardware reference or manufacturer ID 4743.2.3 Source 2: SUP stop receipt 4753.2.4 Source 3: No change to one BOOT after reset 4783.2.5 Source 4: This entity is engaged in another downloading Source 8:

Wrong software reference on a non downloadable TEI 4793.2.6 Source 5: Software not compatible with hardware 4803.2.7 Source 6: File access error 4833.2.8 Source 7: Repetitive errors (NACK, timeout, ...) while downloading a

file 4843.2.9 Source 9: No response to download message 4853.2.10 Source 14: Received CSM LOAD CONTAINER NAK 4873.2.11 Source 15: File to download empty 4893.2.12 Source 16: File to download unavailable 4923.2.13 Source 17: Buffer allocation failure 4923.2.14 Source 18: Bad sending buffer size value 4953.2.15 Source 19: Failure during OMU switchover 4973.2.16 Source 20: Bad TEI sent by BTS in the CSM software update report

message 4993.2.17 Source 21: CSM software update report with the cause - unknown TEI

- 5023.2.18 Source 22: CSM software update report with the cause - equipment

failure - 5043.2.19 Source 23: CSM software update report with the cause - downloading

failure - 5063.2.20 Source 24: CSM software update report with the cause - not able to

perform- 5093.2.21 Source 25: CSM software update report with the cause - wrong software

reference - 5113.2.22 Source 26: CSM software update report with the cause - wrong

configuration reference - 5133.2.23 Source 27: CSM software update report with the cause - restart request

- 5163.2.24 Source 28: CSM software update report with the cause - data


411-9001-104 18.05 2 February 2010


.

12

inconsistency - 5183.2.25 Source 29: CSM software update report with the cause - message out

of sequence - 5203.2.26 Source 30: CSM software update report with the cause - background

not available - 5233.2.27 Source 31: CSM software update report with the cause - incompatible

RM version - 5253.2.28 Source 32: CSM software update report with the cause - downloading in

progress - 5273.2.29 Source 33: Bad report sent by BTS in the CSM software update report

message 5303.2.30 Source 34: No BTS response on CSM software update init-control

message 5323.2.31 Source 35: Nack received on the abort requested by operator 5343.2.32 Source 36: Bad report sent by BTS in the CSM software update abort

message 5373.2.33 Source 37: No BTS response on CSM software update abort

message 5393.2.34 Source 38: Flash activate nack with the cause - unknown TEI - 5413.2.35 Source 39: Flash activate nack with the cause - equipment failure

- 5433.2.36 Source 40: Flash activate nack with the cause - downloading failure

- 5463.2.37 Source 41: Flash activate nack with the cause - not able to perform

- 5483.2.38 Source 42: Flash activate nack with the cause - flash inconsistency

- 5503.2.39 Source 43: Flash activate nack with the cause - data inconsistency

- 5523.2.40 Source 44: Flash activate nack with the cause - wrong soft ref - 5553.2.41 Source 45: Flash activate nack with the cause - wrong config ref - 5573.2.42 Source 46: CSM downloading start nack with the cause - unknown TEI

- 5593.2.43 Source 47: CSM downloading start nack with the cause - equipment

failure - 5613.2.44 Source 48: CSM downloading start nack with the cause - downloading

failure - 5643.2.45 Source 49: CSM downloading start nack with the cause - message out

of sequence - 5663.2.46 Source 50: CSM downloading start nack with the cause - wrong soft ref

- 5683.2.47 Source 51: CSM downloading start nack with the cause - wrong config

ref - 5713.2.48 Source 52: CSM downloading start nack with a bad cause 5733.2.49 Source 53: No BTS response on CSM downloading start message 5753.2.50 Source 54: CSM downloading end nack with the cause - unknown TEI


411-9001-104 18.05 2 February 2010


.

13

- 5773.2.51 Source 55: CSM downloading end nack with the cause - equipment

failure - 5803.2.52 Source 56: CSM downloading end nack with the cause - downloading

failure - 5823.2.53 Source 57: CSM downloading end nack with the cause - value out of

range - 5843.2.54 Source 58: CSM downloading end nack with a bad cause 5863.2.55 Source 59: No BTS response on CSM downloading end message 5893.2.56 Source 60: CSM load init nack with the cause - equipment failure - 5913.2.57 Source 61: CSM load init nack with the cause - downloading failure

- 5933.2.58 Source 62: CSM load init nack with the cause - message out of

sequence - 5953.2.59 Source 63: CSM load init nack with the cause - wrong file ref - 5983.2.60 Source 64: CSM load init nack with the cause - window size not allowed

- 6003.2.61 Source 65: CSM load init nack with the cause - data format error - 6023.2.62 Source 66: CSM load init nack with a bad cause 6053.2.63 Source 67: No BTS response on CSM load init message 6073.2.64 Source 68: CSM load data nack with the cause - equipment failure

- 6093.2.65 Source 69: CSM load data nack with the cause - downloading failure

- 6113.2.66 Source 70: CSM load data nack with the cause - message out of

sequence - 6143.2.67 Source 71: CSM load data nack with the cause - data format error

- 6163.2.68 Source 72: CSM load data nack with the cause - window overflow

- 6183.2.69 Source 73: CSM load data nack with the cause - data inconsistency

- 6203.2.70 Source 74: CSM load data nack with the cause - block not received

- 6233.2.71 Source 75: CSM load data nack with the cause - bad block tag - 6253.2.72 Source 76: CSM load data nack with the cause - checksum error - 6273.2.73 Source 77: CSM load data nack with a bad cause 6293.2.74 Source 78: Unexpected CSM load data ack 6323.2.75 Source 79: No BTS response on CSM load data message 6343.2.76 Source 80: CSM load end nack with the cause - equipment failure

- 6363.2.77 Source 81: CSM load end nack with the cause - downloading failure

- 6383.2.78 Source 82: CSM load end nack with the cause - value out of range

- 6413.2.79 Source 83: CSM load end nack with the cause - message out of


411-9001-104 18.05 2 February 2010


.

14

sequence - 6433.2.80 Source 84: CSM load end nack with the cause - data format error

- 6453.2.81 Source 85: CSM load end nack with the cause - wrong file ref - 6473.2.82 Source 86: CSM load end nack with the cause - data inconsistency

- 6503.2.83 Source 87: CSM load end nack with the cause - checksum error - 6523.2.84 Source 88: CSM load end nack with a bad cause 6543.2.85 Source 89: No BTS response on CSM load end message 6563.2.86 Source 90: Bad report sent by BTS during an internal update 6593.2.87 Source 91: CSM load init nack with the cause - file already open - 6613.2.88 Source 92: CSM load init nack with the cause - invalid mode - 6633.2.89 Source 93: CSM load init nack with the cause - file cannot be unloaded

- 6653.2.90 Source 94: CSM load init nack with the cause - flash flag cannot access

- 6683.2.91 Source 95: CSM load data nack with the cause - file cannot be unloaded

- 6703.2.92 Source 96: CSM load data nack with the cause - flash flag cannot

access - 6723.2.93 Source 97: CSM load data nack with the cause - boot cannot be

unloaded - 6743.2.94 Source 98: CSM load data nack with the cause - data decode error

- 6773.2.95 Source 99: CSM load data nack with the cause - table cannot access

- 6793.2.96 Source 100: CSM load data nack with the cause - RAM mapping error

- 6813.2.97 Source 101: CSM load data nack with the cause - flash access error

- 6843.2.98 Source 102: CSM load data nack with the cause - flash RAM error

- 6863.2.99 Source 103: CSM load data nack with the cause - flash erase error

- 6883.2.100 Source 104: CSM load data nack with the cause - internal abort - 6903.2.101 Source 105: CSM flash activate response with a bad cause 6933.2.102 Source 106: DTM error during token allocation 6953.2.103 Source 107: CSM software update report with the cause: TRX software

incompatibility 6973.2.104 Source 108: Too many different deliveries in the cell group 699

3.3 Fault number: 1053 (e-cell) 7023.4 Fault number: 1054 (e-cell) 7033.5 Fault number: 1055 (e-cell) 703

3.5.1 Source 1: Equipment failure 7073.5.2 Source 2: Equipment unable to perform such test 7083.5.3 Source 3: Equipment unable to perform such configuration 709


411-9001-104 18.05 2 February 2010


.

15

3.5.4 Source 4: Unknown test 7103.5.5 Source 5: Cell parameters inconsistency 7103.5.6 Source 6: Data inconsistency 7123.5.7 Source 7: Value out of range 7133.5.8 Source 8: TEI not present 7133.5.9 Source 9: Unknown Abis PCM_Time_Slot 7143.5.10 Source 10: Unknown Abis PCM 7143.5.11 Source 11: Wrong software reference 7153.5.12 Source 12: Further files required 7153.5.13 Source 13: Failure during activation 7163.5.14 Source 14: Data format error 7163.5.15 Source 15: Window overflow 7163.5.16 Source 16: Normal completion 7163.5.17 Source 17: Transfer aborted 7163.5.18 Source 18: Checksum error 7173.5.19 Source 19: File incomplete 7173.5.20 Source 20: File already present and correct 7173.5.21 Source 21: File cannot be downloaded 7173.5.22 Source 22: Entity engaged in other download 7183.5.23 Source 23: Too many signaling timeslots 7183.5.24 Source 24: Too many TEI connections to physical channel 7193.5.25 Source 25: Out of sequence message 7193.5.26 Source 26: Incorrect IEI 7213.5.27 Source 27: Wrong file reference 7223.5.28 Source 28: Bad cell number 7223.5.29 Source 29: Bad related TEI 7223.5.30 Source 30: Bad timeslot 7223.5.31 Source 31: Window size not allowed 7223.5.32 Source 32: Flash boot required 7233.5.33 Source 33: Wrong config reference 7233.5.34 Source 34: The BTS has not acknowledged the TX power consign

request 7233.5.35 Source 35: Downloading aborted 7283.5.36 Source 36: Files missing 7283.5.37 Source 37: Buffer overflow 7293.5.38 Source 38: Block not received 7293.5.39 Source 39: Downloading restart 7293.5.40 Source 40: Request not supported 7293.5.41 Source 41: Downloading failure 7293.5.42 Source 42: Start-up failure 7303.5.43 Source 43: Maximum number of joker TS 7303.5.44 Source 44: Bad chain type 7333.5.45 Source 45: Bad radio timeslot reference 7333.5.46 Source 46: Bad internal Link EDGE configuration 733


411-9001-104 18.05 2 February 2010


.

16

3.5.47 Source 47: Inconsistency mapping 7333.5.48 Source 48: Inconsistency number of joker DS0 7343.5.49 Source 49: Invalid mode 7343.5.50 Source 50: File already open 7343.5.51 Source 51: File cannot be unloaded 7343.5.52 Source 52: Boot cannot be unloaded 7343.5.53 Source 53: Data decode error 7353.5.54 Source 54: Flash flag cannot access 7353.5.55 Source 55: Table cannot access 7353.5.56 Source 56: RAM mapping error 7353.5.57 Source 57: Flash access error 7353.5.58 Source 58: Flash write error 7363.5.59 Source 59: Flash erase error 7363.5.60 Source 60: Internal abort 7363.5.61 Source 61: Equipment not able to get external synchronization 7363.5.62 Source 62: Synchronization in progress 7363.5.63 Source 63: Dynamic Abis feature not supported 7373.5.64 Source 64: Inconsistent number of joker DS0 7383.5.65 Source 65: Exceeded DL joker DS0 pool number 7403.5.66 Source 255: Non-significant value 742

3.6 Fault number: 1058 (e-cell) 7423.7 Fault number: 1059 (e-cell) 7433.8 Fault number: 1060 (e-cell) 744

3.8.1 PMNU (source: Message unknown) 7463.8.2 PMNU (source: Restart due to reset by BSC) 7463.8.3 PMNU (source: Restart due to reset by reset button) 7463.8.4 PMNU (source: Restart due to power on) 7463.8.5 PMNU (source: Restart due to a too long PCM scanning) 7473.8.6 PMNU (source: Restart requested by the active board) 7473.8.7 PMNU (source: restart due to a software upgrade) 7473.8.8 PMNU (source: Restart due to a hardware watchdog) 7483.8.9 PMNU (source: Restart due to loss of lock) 7483.8.10 PMOD (source: FACCH congestion) 7483.8.11 PMOD (source: PMOD reset by BCF after message non

acknowledged) 7493.8.12 PMOD (source: Restart due to the timeout on the OML link with

BSC) 7493.8.13 PMOD (source: Restart due to the timeout on the OML link with

BCF) 7503.8.14 PMOD (source: Restart due to a software upgrade) 7503.8.15 PMOD (source: BCCH config dump) 7503.8.16 PMOD (source: SACCH config dump) 7513.8.17 PMOD (source: L1M config dump) 7513.8.18 PMOD (source: RSL anomaly) 751


411-9001-104 18.05 2 February 2010


.

17

3.9 Fault number: 1061 (e-cell) 7523.10 Attribute value change: 1063 (e-cell) 7533.11 Fault number: 1067 (e-cell) 754

3.11.1 Abis BTS synchro (source: SYNO clock not locked on thenetwork) 758

3.11.2 AC power supply (source: Power fault) 7633.11.3 External alarm (source: External alarm) 7663.11.4 Internal temperature (source: Threshold exceeded) 7663.11.5 PA (source: Hardware) 7683.11.6 PA (source: PA DRX control loop fault) 7733.11.7 PCM (source: PCM) 7783.11.8 PMNU (source: Base-extension communication fault) 7783.11.9 PMNU (source: Self test failed) 7803.11.10 PMNU (source: Hardware) 7853.11.11 PMOD (source: BBFILTER ASIC fault) 7893.11.12 PMOD (source: Self test failed) 7943.11.13 PMOD (source: Major fault on TX) 7983.11.14 PMOD (source: The TX has not acknowledged the power consign

request) 8033.11.15 PMOD (source: BCCH first config failed) 8063.11.16 PMOD (source: BCCH second config failed) 8063.11.17 PMOD (source: SACCH first config failed) 8073.11.18 PMOD (source: SACCH second config failed) 8073.11.19 PMOD (source: L1M first config failed) 8083.11.20 PMOD (source: L1M second config failed) 8093.11.21 PSU (source: PSU failure) 8093.11.22 RDRX (source: RX fault) 8113.11.23 RDRX (source: Hardware) 816

3.12 Fault number: 1070 (e-cell) 8203.13 Fault number: 1073 (e-cell) 821

3.13.1 Source 9: No response to LOAD message 8253.13.2 Source 10: Received LOAD INIT NACK 8253.13.3 Source 11: Received message LOAD DATA NACK 8263.13.4 Source 12: Received message LOAD END NACK 8263.13.5 Source 13: Received message 826

3.14 Fault number: 1080 (e-cell) 826FAULT ANALYSIS 826

3.15 Fault number: 1165 (e-cell) 8273.16 Fault number: 1258 (e-cell) 8283.17 Fault number: 1259 (e-cell) 8293.18 Fault number: 1265 (e-cell) 8303.19 Fault number: 1266 (e-cell) 8313.20 Fault number: 1268 (e-cell) 8323.21 Fault number: 1500 (e-cell) 833


411-9001-104 18.05 2 February 2010


.

18

3.22 Fault number: 1505 (e-cell) 8343.23 Fault number: 1506 (e-cell) 8353.24 Fault number: 1507 (e-cell) 8363.25 Fault number: 1508 (e-cell) 836


411-9001-104 18.05 2 February 2010


.

19.

New in this releaseThe following section describe what is new in this release for Nortel GSMBTS S8006 Troubleshooting (411-9001-104) for V18.0 P&C 2 release. Features (page 19)

FeaturesThis document contains no feature updates in this release.


411-9001-104 18.05 2 February 2010


.

20 New in this release


411-9001-104 18.05 2 February 2010


.

21.

IntroductionThis document contains the fault number description and the maintenanceactions required for the S2000 H/L and e-cell Base Transceiver Station(BTS).

PrerequisitesIt is recommended that the readers also become familiar with the followingtechnical documents: Nortel GSM BSS Documentation Roadmap (411-9001-000) Nortel GSM BSS Overview (411-9001-001) Nortel GSM BSS Fundamentals - Operating Principles (411-9001-007) Nortel GSM BSS Configuration - Operating Procedures (411-9001-034) Nortel GSM BTS S2000H/S2000L Fundamentals (411-9001-035) Nortel GSM BSS Fault Management - Maintenance Principles

(411-9001-039) Nortel GSM BTS S2000H/S2000L Troubleshooting (411-9001-049) Nortel GSM BTS Commissioning - TML User Guide (411-9001-051) Nortel GSM BTS e-cell Troubleshooting (411-9001-090) Nortel GSM BSS Parameter Reference (411-9001-124) Nortel GSM OMC-R Commands Reference Objects and Fault menus

(411-9001-128)


411-9001-104 18.05 2 February 2010


.

22 Introduction

NavigationThis document consists of 3 chapters: Chapter 1 How to use this manual (page 23), describes how to use

this maintenance manual. Chapter 2 S2000 H/L BTS fault numbers (page 27), contains the

fault number description and the corrective maintenance proceduresapplicable to the S2000 H/L BTS.

Chapter 3 e-cell fault numbers (page 463), contains the fault numberdescription and the corrective maintenance procedures applicable tothe e-cell BTS.


411-9001-104 18.05 2 February 2010


.

23.

Chapter 1 How to use this manual1.1 Introduction

This manual contains the fault number description and the correctivemaintenance procedures applicable to the S2000 H/L BTS and e-cell forGSM 850, 900, 1800, and 1900.

The general principles and messages required for BSS maintenanceare described in: Nortel GSM BSS Fault Management - MaintenancePrinciples (411-9001-039)

The network maintenance is based on the graphical supervision of thenetwork at the OMC-R.

It is also based on the identification and the replacement of faulty items ofequipment, using the alarms and the notifications.

This process is divided into two steps: locating and identifying the faulty items of equipment, using information

given in this manual replacing the faulty items of equipment, using the replacement

procedures given in the manuals that describe the on-site procedures

When a faulty item of equipment sends an alarm to the OMC-R, thisalarm is identified by a fault number. This manual gives the proceduresassociated with the various fault numbers.

1.2 The types of spontaneous messages1.2.1 Events detected by the BTS

The following are types of spontaneous message: spontaneous messages indicating a hardware fault (fault number 1067) spontaneous messages indicating a hardware fault without loss of

capacity, triggering no defense actions on the part of the BSC. If thereare any defense actions, they are local and controlled by the BTS (faultnumber 1067).


411-9001-104 18.05 2 February 2010


.

24 Chapter 1 How to use this manual

spontaneous messages indicating a transient event for warning (faultnumber 1060)

spontaneous messages indicating the arrival of state changes on anequipment (fault number 1058)

1.2.2 Events detected by the BSCSpontaneous messages are sent by the BSC giving information on thestate of relationships with the BTS or part of it (1051, 1052, 1053, 1054,1055, 1059, 1073).

1.3 Description of a fault number sheetA corrective maintenance sheet contains the following information: the header the main body composed of three main paragraphs explaining the fault

number treatment

1.3.1 Header of the sheetThe header contains the following information: the fault number and possibly the source the alarm type

1.3.2 Main body of the sheetThe main body contains the following information: Fault analysis

This paragraph describes the fault. Reaction of the system

BSC defenseThis paragraph describes the defense actions taken by the BSC.

Impact on the serviceThis paragraph gives the consequences of the alarm for theservice.

TroubleshootingThis paragraph gives the procedures to be followed to repair the faultand return to the operational conditions. Preliminary checks


411-9001-104 18.05 2 February 2010


.

1.3 Description of a fault number sheet 25

These checks are used to ensure that the fault is confirmed andthat the messages identifying a faulty element are in the OMC-Rlogs before the start of repair work.

On-site maintenance (possibly using the OMC-R)This paragraph is used to start the repair work and to bring theexchanged element into correct operation.

Additional checksThis paragraph shows how to check that the fault has beencleared.


411-9001-104 18.05 2 February 2010


.

26 Chapter 1 How to use this manual


411-9001-104 18.05 2 February 2010


.

27.

Chapter 2 S2000 H/L BTS faultnumbers2.1 Fault number: 1051 (S2000 H/L BTS)

Fault number:

1051 : Loss of layer 3 with remote GSM entityType : communicationsAlarm

This problem is associated with a PCM fault. see: Nortel GSM BSS FaultClearing - Advanced Maintenance Procedures (411-9001-105)

2.2 Fault number: 1052 (S2000 H/L BTS)Fault number:1052 : GSM entity downloading failureType : communicationsAlarm/processingErrorAlarm/ equipmentAlarm

FAULT ANALYSIS

This message identifies the impacted element but not the faulty element. Itindicates a software downloading error concerning a transceiverEquipmentobject or a btsSiteManager object.

All the software downloading attempts are indicated, as well as the sourceof their failure.

Table 1 "Fault number 1052 sources" (page 28) indicates all the sourcesof the fault number 1052 for the S2000 H/L BTS. For more informationon each source, see the indicated paragraph to know the correctivemaintenance procedure associated with this source.


411-9001-104 18.05 2 February 2010


.

28 Chapter 2 S2000 H/L BTS fault numbers

Table 1Fault number 1052 sources

SourceNo. Source wording Paragraph

0 No response to statusrequest

2.2.1 Source 0: No response to statusrequest (page 36)

1 Bad hardware referenceor manufacturer ID

2.2.2 Source 1: Bad hardware referenceor manufacturer ID (page 38)

2 SUP stop receipt 2.2.3 Source 2: SUP stop receipt(page 40)

3 No change to one ofBOOT after reset

2.2.4 Source 3: No change to one ofBOOT after reset (page 43)

4 This entity is engagedin another downloading

2.2.5 Source 4: This entity is engagedin another downloadingSource 8:

Wrong software reference on a nondownloadable TEI (page 45)

5 Software not compatiblewith hardware

2.2.6 Source 5: Software not compatiblewith hardware (page 47)

6 File access error 2.2.7 Source 6: File access error(page 51)

7 Repetitive errors(NACK, timeout, ...)

while downloading a file

2.2.8 Source 7:Repetitive errors (NACK,timeout, ...) while downloading a

file (page 54)8 Wrong software

reference on a nondownloadable TEI

2.2.5 Source 4: This entity is engagedin another downloadingSource 8:

Wrong software reference on a nondownloadable TEI (page 45)

9 No response todownload message

2.2.9 Source 9: No response to downloadmessage (page 55)

14 CSM load containernegative acknowle

dgement

2.2.10 Source 14: Received CSM LOADCONTAINER NAK (page 57)

15 File to download empty 2.2.11 Source 15: File to downloadempty (page 59)

16 File to downloadunavailable

2.2.12 Source 16: File to downloadunavailable (page 62)

17 Buffer allocation failure 2.2.13 Source 17: Buffer allocationfailure (page 62)

18 Bad sending buffersize value

2.2.14 Source 18: Bad sending buffersize value (page 65)

19 Failure during OMUswitchover

2.2.15 Source 19: Failure during OMUswitchover (page 67)


411-9001-104 18.05 2 February 2010


.

2.2 Fault number: 1052 (S2000 H/L BTS) 29

Table 1Fault number 1052 sources (contd.)


20 Bad TEI sent by BTSin the CSM software

update report message

2.2.16 Source 20: Bad TEI sent byBTS in the CSM software update report

message (page 69)21 CSM software update

report with the causeunknown TEI

2.2.17 Source 21: CSM softwareupdate report with the cause - unknown

TEI - (page 72)22 CSM software update

report with the causeequipment failure

2.2.18 Source 22: CSM softwareupdate report with the cause - equipment

failure - (page 74)23 CSM software update

report with the cause"downloading failure"

2.2.19 Source 23: CSM software updatereport with the cause - downloading

failure - (page 76)24 CSM software update

report with the cause"not able to perform"

2.2.20 Source 24: CSM softwareupdate report with the cause - not able

to perform- (page 79)25 CSM software update

report with the cause"wrong soft ref"

2.2.21 Source 25: CSM software updatereport with the cause - wrong software

reference - (page 81)26 CSM software update

report with the cause"wrong config ref"

2.2.22 Source 26: CSM software updatereport with the cause - wrong configuration

reference - (page 83)27 CSM software update

report with the cause"restart request"

2.2.23 Source 27: CSM softwareupdate report with the cause - restart

request - (page 86)28 CSM software update

report with the cause"data inconsistency"

2.2.24 Source 28: CSM softwareupdate report with the cause - data

inconsistency - (page 88)

29 CSM software updatereport with the cause

"message out ofsequence"

2.2.25 Source 29: CSM software updatereport with the cause - message out

of sequence - (page 90)


"background notavailable"

2.2.26 Source 30: CSM software updatereport with the cause - background not

available - (page 93)


"incompatible RMversion"

2.2.27 Source 31: CSM software updatereport with the cause - incompatible

RM version - (page 95)


411-9001-104 18.05 2 February 2010


.





"downloading inprogress"

2.2.28 Source 32: CSM software updatereport with the cause - downloading

in progress - (page 97)

33 Bad report sent by BTSin the CSM software

update report message

2.2.29 Source 33: Bad report sent byBTS in the CSM software update report

message (page 100)34 No BTS response on

CSM software updateinit/control message

2.2.30 Source 34: No BTS responseon CSM software update init-control

message (page 102)35 Nack received on the

abort requested byoperator

2.2.31 Source 35: Nack received on theabort requested by operator (page 104)

36 Bad report sent by BTSin the CSM software

update abort message

2.2.32 Source 36: Bad report sent byBTS in the CSM software update abort

message (page 107)37 No BTS response on

CSM software updateabort message

2.2.33 Source 37: No BTS responseon CSM software update abort

message (page 109)38 Flash activate nack with

the cause "unknownTEI"

2.2.34 Source 38: Flash activatenack with the cause - unknown TEI

- (page 111)39 Flash activate nack with

the cause "equipmentfailure"

2.2.35 Source 39: Flash activatenack with the cause - equipment

failure - (page 113)40 Flash activate nack with

the cause "downloadingfailure"

2.2.36 Source 40: Flash activatenack with the cause - downloading

failure - (page 116)41 Flash activate nack

with the cause "not ableto perform"

2.2.37 Source 41: Flash activatenack with the cause - not able to

perform - (page 118)42 Flash activate nack

with the cause "flashinconsistency"

2.2.38 Source 42: Flash activate nackwith the cause - flash inconsistency

- (page 120)43 Flash activate nack

with the cause "datainconsistency"

2.2.39 Source 43: Flash activate nackwith the cause - data inconsistency

- (page 122)44 Flash activate nack

with the cause "wrongsoft ref"

2.2.40 Source 44: Flash activatenack with the cause - wrong soft ref

- (page 125)


411-9001-104 18.05 2 February 2010


.




45 Flash activate nackwith the cause "wrong

config ref"

2.2.41 Source 45: Flash activatenack with the cause - wrong config

ref - (page 127)46 CSM downloading start

nack with the cause"unknown TEI"

2.2.42 Source 46: CSM downloadingstart nack with the cause - unknown

TEI - (page 129)47 CSM downloading start

nack with the cause"equipment failure"

2.2.43 Source 47: CSM downloadingstart nack with the cause - equipment

failure - (page 131)48 CSM downloading start

nack with the cause"downloading failure"

2.2.44 Source 48: CSM downloadingstart nack with the cause - downloading

failure - (page 134)49 CSM downloading

start nack with thecause "message out

of sequence"

2.2.45 Source 49: CSM downloadingstart nack with the cause - message out

of sequence - (page 136)

50 CSM downloading startnack with the cause

"wrong soft ref"

2.2.46 Source 50: CSM downloadingstart nack with the cause - wrong soft

ref - (page 138)51 CSM downloading start

nack with the cause"wrong config ref"

2.2.47 Source 51: CSM downloadingstart nack with the cause - wrong

config ref - (page 141)52 CSM downloading start

nack with a bad cause2.2.48 Source 52: CSM downloading start

nack with a bad cause (page 143)53 No BTS response on

CSM downloading startmessage

2.2.49 Source 53: No BTS responseon CSM downloading start message

(page 145)54 CSM downloading end

nack with the cause"unknown TEI"

2.2.50 Source 54: CSM downloadingend nack with the cause - unknown

TEI - (page 147)55 CSM downloading end

nack with the cause"equipment failure"

2.2.51 Source 55: CSM downloadingend nack with the cause - equipment

failure - (page 150)56 CSM downloading end


2.2.52 Source 56: CSM downloadingend nack with the cause - downloading

failure - (page 152)57 CSM downloading end

nack with the cause"value out of range"

2.2.53 Source 57: CSM downloadingend nack with the cause - value out

of range - (page 154)


411-9001-104 18.05 2 February 2010


.




58 CSM downloading endnack with a bad cause

2.2.54 Source 58: CSM downloading endnack with a bad cause (page 156)

59 no BTS response onCSM downloading end

message

2.2.55 Source 59: No BTS responseon CSM downloading end message

(page 159)60 CSM load init nack with

the cause "equipmentfailure"

2.2.56 Source 60: CSM load init nack withthe cause - equipment failure - (page 161)

61 CSM load init nack withthe cause "downloading

failure"

2.2.57 Source 61: CSM load initnack with the cause - downloading

failure - (page 163)62 CSM load init nack with

the cause "messageout of sequence"

2.2.58 Source 62: CSM load initnack with the cause - message out of

sequence - (page 165)63 CSM load init nackwith the cause "wrong

file ref"

2.2.59 Source 63: CSM load init nack withthe cause - wrong file ref - (page 168)

64 CSM load init nackwith the cause "window

size not allow"

2.2.60 Source 64: CSM load initnack with the cause - window size not

allowed - (page 170)65 CSM load init nack

with the cause "dataformat error"

2.2.61 Source 65: CSM load init nack withthe cause - data format error - (page 172)

66 CSM load init nack witha bad cause

2.2.62 Source 66: CSM load init nackwith a bad cause (page 175)

67 No BTS response onCSM load init message

2.2.63 Source 67: No BTS response onCSM load init message (page 177)

68 CSM load datanack with the cause"equipment failure"

2.2.64 Source 68: CSM load datanack with the cause - equipment

failure - (page 179)69 CSM load data


2.2.65 Source 69: CSM load datanack with the cause - downloading

failure - (page 181)70 CSM load data

nack with the cause"message out of

sequence"

2.2.66 Source 70: CSM load datanack with the cause - message out of

sequence - (page 184)

71 CSM load data nackwith the cause "data

format error"

2.2.67 Source 71: CSM load datanack with the cause - data format

error - (page 186)


411-9001-104 18.05 2 February 2010


.




72 CSM load data nackwith the cause "window

overflow"

2.2.68 Source 72: CSM load data nackwith the cause - window overflow

- (page 188)73 CSM load data nack


2.2.69 Source 73: CSM load data nackwith the cause - data inconsistency


with the cause "blocknot received"

2.2.70 Source 74: CSM load data nackwith the cause - block not received


with the cause "badblock tag"

2.2.71 Source 75: CSM load datanack with the cause - bad block tag

- (page 195)76 CSM load data

nack with the cause"checksum error"

2.2.72 Source 76: CSM load datanack with the cause - checksum

error - (page 197)77 CSM load data nack

with a bad cause2.2.73 Source 77: CSM load data nack

with a bad cause (page 199)78 Unexpected CSM load

data ack2.2.74 Source 78: Unexpected CSM

load data ack (page 202)79 No BTS response

on CSM load datamessage

2.2.75 Source 79: No BTS response onCSM load data message (page 204)

80 CSM load end nackwith the cause

"equipment failure"

2.2.76 Source 80: CSM load endnack with the cause - equipment

failure - (page 206)81 CSM load end nack

with the cause"downloading failure"

2.2.77 Source 81: CSM load endnack with the cause - downloading

failure - (page 208)82 CSM load end nack

with the cause "valueout of range"

2.2.78 Source 82: CSM load endnack with the cause - value out of

range - (page 211)83 CSM load end nack

with the cause"message out of

sequence"

2.2.79 Source 83: CSM load endnack with the cause - message out of

sequence - (page 213)

84 CSM load end nackwith the cause "data

format error"

2.2.80 Source 84: CSM load endnack with the cause - data format

error - (page 215)


411-9001-104 18.05 2 February 2010


.




85 CSM load end nackwith the cause "wrong

file ref"

2.2.81 Source 85: CSM load endnack with the cause - wrong file ref

- (page 217)86 CSM load end nack


2.2.82 Source 86: CSM load end nackwith the cause - data inconsistency

- (page 220)87 CSM load end nack

with the cause"checksum error"

2.2.83 Source 87: CSM load endnack with the cause - checksum

error - (page 222)88 CSM load end nack

with a bad cause2.2.84 Source 88: CSM load end nack

with a bad cause (page 224)

89 No BTS response onCSM load end message

2.2.85 Source 89: No BTS response onCSM load end message (page 226)

90 Bad report sent byBTS during an internal

update

2.2.86 Source 90: Bad report sent by BTSduring an internal update (page 229)

91 CSM load init nackwith the cause "file

already open"

2.2.87 Source 91: CSM load init nack withthe cause - file already open - (page 231)

92 CSM load init nackwith the cause "invalid

mode"

2.2.88 Source 92: CSM load init nack withthe cause - invalid mode - (page 233)

93 CSM load init nack withthe cause "file cannot

be unloaded"

2.2.89 Source 93: CSM load initnack with the cause - file cannot be

unloaded - (page 235)94 CSM load init nack with

the cause "flash flagcannot access"

2.2.90 Source 94: CSM load init nackwith the cause - flash flag cannot

access - (page 238)95 CSM load data nack

with the cause "filecannot be unloaded"

2.2.91 Source 95: CSM load datanack with the cause - file cannot be

unloaded - (page 240)96 CSM load data nack

with the cause "flashflag cannot access"

2.2.92 Source 96: CSM load datanack with the cause - flash flag cannot


with the cause "bootcannot be unloaded"

2.2.93 Source 97: CSM load datanack with the cause - boot cannot be

unloaded - (page 244)


411-9001-104 18.05 2 February 2010


.




98 CSM load data nackwith the cause "data

decod error"

2.2.94 Source 98: CSM load datanack with the cause - data decode


with the cause "tablecannot access"

2.2.95 Source 99: CSM load datanack with the cause - table cannot


with the cause "rammapping error"

2.2.96 Source 100: CSM load datanack with the cause - RAM mapping


with the cause "flashaccess error"

2.2.97 Source 101: CSM load datanack with the cause - flash access


with the cause "flashram error"

2.2.98 Source 102: CSM load datanack with the cause - flash RAM


with the cause "flasherase error"

2.2.99 Source 103: CSM load datanack with the cause - flash erase


with the cause "internalabort"

2.2.100 Source 104: CSM load datanack with the cause - internal abort

- (page 260)REACTION OF THE SYSTEM

BSC defense

The BSC attempts a maximum of five software downloadings. If the fiveattempts fail, the BSC sends a fault number 1052 and a state change onthe btsSiteManager object to "disabled-failed".

Impact on the service Case of the btsSiteManager object

The site is not downloaded.CAUTIONService interruptionThe service is reduced or lost depending on theconfiguration.

Case of the transceiverEquipment objectThe TRX is not downloaded, one TDMA is not configured.


411-9001-104 18.05 2 February 2010


.


ATTENTIONThe service is reduced.

2.2.1 Source 0: No response to status requestFault number 1052 : GSM entity downloading failureSource: (0) No response to status requestBTS model: S2000H/L

FAULT ANALYSISThis source indicates that the BTS has not replied to the status request.

TROUBLESHOOTING

Step Action

Preliminary checks1 Look at the notification and identify the object concerned.

If the btsSiteManager object is concerned, go to step 2. If the transceiverEquipment object is concerned, go to step 3.

2 Check the state of the site by performing the "Display all"command on the btsSiteManager object. If the operationalState of the btsSiteManager object is

"enabled", the site is operational. Clear the alarm. The procedure is complete.

If the operationalState of the btsSiteManager object is"disabled-dependency", the site is not operational. Look foran object whose state is "disabled-failed". If a pcmCircuit object is "disabled-failed", look for a fault

number concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC .

If the operationalState of the btsSiteManager object is"disabled-failed", the site is not operational.


411-9001-104 18.05 2 February 2010


.


If the fault number 1052 is the only alarm, process thealarm.

Otherwise, if there are other alarms, set thebtsSiteManager object to "locked" and then to"unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see

above). If other fault numbers are present, such as fault

number 1054, process them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If the operationalState of the btsSiteManager object is"disabled", the site is not operational. Do not process thealarm and do not clear it. Wait for a state change of thebtsSiteManager object.

3 Check the state of the TRX by performing the "Display all"command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is

"enabled", the TRX is operational. Clear the alarm. The procedure is complete.

If the operationalState of the transceiverEquipment object is"disabled-dependency", the TRX is not operational.Look for a parent object which is not operational. If a bts object is "disabled-dependency", look for alarms

concerning cells. If the btsSiteManager object is "disabled-failed", the site

is not operational. process the alarm(s) concerning thebtsSiteManager object.

If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC.

If the operationalState of the transceiverEquipment object is"disabled-failed", the TRX is not operational.


411-9001-104 18.05 2 February 2010


.


If the fault number 1052 is the only alarm, process thealarm. Go to step 4.

Otherwise, if there are other alarms, set thetransceiverEquipment object to "locked" and thento "unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see


number 1054, process them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures)).

If the operationalState of the transceiverEquipment objectis "disabled", the TRX is not operational. Do not processthe alarm and do not clear it. Wait for a state change of thetransceiverEquipment object.

4 The procedure is complete.

--End--

2.2.2 Source 1: Bad hardware reference or manufacturer IDFault number 1052 : GSM entity downloading failureSource:BTS model:

(1) Bad hardware reference or manufacturer ID S2000 H/L

FAULT ANALYSISThis source indicates that the first downloading attempt failed.

The alarm indicates that the "hardwareRef" parameter, obtained byperforming the "Display" command on the btsSiteManager object andthe transceiverEquipment object, is not in accordance with the PROMnumbers on the boards.

TROUBLESHOOTINGPreliminary checks

Step Action

1 Look at the notification and identify the object concerned. If the btsSiteManager object is concerned, go to step 2. If the transceiverEquipment object is concerned, go to step 3.


411-9001-104 18.05 2 February 2010


.





number concerning PCMs (see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).

If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms about the BSC.

If the operationalState of the btsSiteManager object is"disabled-failed", the site is not operational. If the fault number 1052 is the only alarm, treat the alarm.

Go to step 4. Otherwise, if there are other alarms, set the

btsSiteManager object to "locked" then to "unlocked" toconfirm the problem. If the fault number 1052 is still present, treat it (see

above). If other fault numbers are present too, such as fault

number 1054, treat them (concerning fault number1054 (loss of layer 2), see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).

If the operationalState of the btsSiteManager object is"disabled", the site is not operational. Do not treat thealarm and do not clear it. Wait for a state change of thebtsSiteManager object.

3 Check the state of the DRX by performing the "Display all"command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is

"enabled", the DRX is operational. Clear the alarm. The procedure is complete.

If the operationalState of the transceiverEquipment object is"disabled-dependency", the DRX is not operational.Look for a parent object which is not operational either.


411-9001-104 18.05 2 February 2010


.


If a bts object is "disabled-dependency", look for alarmsconcerning cells.

If the btsSiteManager object is "disabled-failed", the siteis not operational. Treat the alarm(s) concerning thebtsSiteManager object.

If a pcmCicruit object is "disabled-failed", look for a faultnumber concerning PCMs (see Nortel GSM BSS FaultClearing - Advanced Maintenance (411-9001-105) ).


If the operationalState of the transceiverEquipment object is"disabled-failed", the DRX is not operational. If the fault number 1052 is the only alarm, treat the alarm.


transceiverEquipment object to "locked" and thento "unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see



If the operationalState of the transceiverEquipment objectis "disabled" the DRX is not operational. Do not treat thealarm and do not clear it. Wait for a state change of thetransceiverEquipment object.

Case of the btsSiteManager object for the S2000 H/L BTS4 Set the value of the "hardwareRef" parameter to "0".5 The procedure is complete.Case of the transceiverEquipment object for the S2000 H/L BTS6 Modify the value of the "hardwareRef" parameter: set it to "0".7 The procedure is complete.

--End--

2.2.3 Source 2: SUP stop receiptFault number 1052 : GSM entity downloading failureSource: (2) SUP stop receiptBTS model: S2000H/L


411-9001-104 18.05 2 February 2010


.


FAULT ANALYSISThis source indicates that a supervision stop has been received.

TROUBLESHOOTING

Step Action

Preliminary checks1 Look at the notification and identify the object concerned.

If the btsSiteManager object is concerned, go to step 2. If the transceiverEquipment object is concerned, go to step 3.




number concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If a lapdLink object is "disabled-failed", the BSC isconcerned. Look for alarms concerning the BSC .

If the operationalState of the btsSiteManager object is"disabled-failed", the site is not operational. If the fault number 1052 is the only alarm, process the

alarm. Otherwise, if there are other alarms, set the

btsSiteManager object to "locked" and then to"unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see


number 1054, process them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).

If the operationalState of the btsSiteManager object is"disabled", the site is not operational. Do not process the


411-9001-104 18.05 2 February 2010


.


alarm and do not clear it. Wait for a state change of thebtsSiteManager object.

3 Check the state of the TRX by performing the "Display all"command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is

"enabled", the TRX is operational. Clear the alarm. The procedure is complete.

If the operationalState of the transceiverEquipment object is"disabled-dependency", the TRX is not operational.Look for a parent object which is not operational. If a bts object is "disabled-dependency", look for alarms


is not operational. process the alarm(s) concerning thebtsSiteManager object.

If a pcmCircuit object is "disabled-failed", look for a faultnumber concerning PCMs (see 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures) ).


If the operationalState of the transceiverEquipment object is"disabled-failed", the TRX is not operational. If the fault number 1052 is the only alarm, process the

alarm. Go to step 4. Otherwise, if there are other alarms, set the

transceiverEquipment object to "locked" and thento "unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see


number 1054, process them (concerning fault number1054 (loss of layer 2), refer to 411-9001-105 (NortelGSM BSS Fault Clearing - Advanced MaintenanceProcedures)).

If the operationalState of the transceiverEquipment objectis "disabled", the TRX is not operational. Do not processthe alarm and do not clear it. Wait for a state change of thetransceiverEquipment object.


411-9001-104 18.05 2 February 2010


.



--End--

2.2.4 Source 3: No change to one of BOOT after resetFault number 1052 : GSM entity downloading failureSource:BTS model:

(3) No change to one of BOOT after resetS2000 H/L


Step Action



"enabled", the site is operational. Clear the alarm and go tostep 6.




If the operationalState of the btsSiteManager object is"disabled-failed", and if there are other alarms which couldimpact the operation of the site, lock the btsSiteManagerobject. Then unlock it. If the alarm with the fault number 1052 and the source 3

is still present, treat the alarm. Go to step 4. If other fault numbers are present too, such as fault

number 1054, treat them. Concerning fault number 1054(loss of layer 2), see Nortel GSM BSS Fault Clearing -Advanced Maintenance (411-9001-105) .

If the operationalState of the btsSiteManager object is"disabled", the site is not operational. Do not treat the


411-9001-104 18.05 2 February 2010


.


alarm and do not clear it. Wait for a state change of thebtsSiteManager object.

3 Check the state of the DRX by performing the "Display all"command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is


If the operationalState of the transceiverEquipment object is"disabled-dependency", the DRX is not operational.Look for a parent object which is not operational either. If a bts object is "disabled-dependency", look for alarms


is not operational. Treat the alarm(s) concerning thebtsSiteManager object.



If the operationalState of the transceiverEquipment object is"disabled-failed", the DRX is not operational. If the fault number 1052 is the only alarm, treat the alarm.


transceiverEquipment object to "locked" then to"unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see




On-site maintenance using the OMC-R4 Set the operationalState of the entity concerned to "locked" then

"unlocked" to restart the downloading.


411-9001-104 18.05 2 February 2010


.


If the alarm persists, check if the source 1 appears. If the source 1 appears, treat it. See Paragraph 2.2.2

Source 1: Bad hardware reference or manufacturer ID(page 38).

If the source 1 does not appear, go to step 5. If the alarm has disappeared, the downloading has restarted.

Go to step 6.

5 Replace the following items: the base or extension module of the S2000H "EP" BTS:

see Nortel GSM BTS S2000H/S2000L Troubleshooting(411-9001-049).

the main module of the S2000H "FP" BTS: see Nortel GSMBTS S2000H/S2000L Troubleshooting (411-9001-049).

the base or extension module of the S2000L "EP" BTS:see Nortel GSM BTS S2000H/S2000L Troubleshooting(411-9001-049).

the main module of the S2000L "FP" BTS: see Nortel GSMBTS S2000H/S2000L Troubleshooting (411-9001-049).

If the alarm has disappeared, go to step 6. Otherwise, call themanufacturer.


--End--

2.2.5 Source 4: This entity is engaged in another downloadingSource 8: Wrong software reference on a non downloadable TEI

Fault number 1052 : GSM entity downloading failureSource:Source:BTS model:

(4) This entity is engaged in another downloading(8) Wrong software reference on a non downloadable TEIS2000 H/L


Step Action



411-9001-104 18.05 2 February 2010


.







If the operationalState of the btsSiteManager object is"disabled-failed", and if there are other alarms which couldimpact the operation of the site, lock the btsSiteManagerobject. Then unlock it. If the alarm with the fault number 1052 and the source 4

or 8 is still present, treat the alarm. Call the manufacturer. Otherwise, if there are other alarms, such as fault number

1054, treat them (concerning fault number 1054 (loss oflayer 2), see Nortel GSM BSS Fault Clearing - AdvancedMaintenance (411-9001-105) ).


3 Check the state of the site by performing the "Display all"command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is


If the operationalState of the transceiverEquipment object is"disabled-dependency", the DRX is not operational.Look for a parent object which is not operational either. If a bts object is "disabled-dependency", look for alarms


is not operational. Treat the alarm(s) concerning thebtsSiteManager object.


411-9001-104 18.05 2 February 2010


.




If the operationalState of the transceiverEquipment object is"disabled-failed", the DRX is not operational. If the fault number 1052 is the only alarm, treat it. Call the

manufacturer. Otherwise, if there are other alarms, set the

transceiverEquipment object to "locked" then to"unlocked" to confirm the problem. If the fault number 1052 is still present, treat it (see




On-site maintenance using the OMC-R4 The procedure is complete.

--End--

2.2.6 Source 5: Software not compatible with hardwareFault number 1052 : GSM entity downloading failureSource:BTS model:

(5) Software not compatible with hardwareS2000 H/L

FAULT ANALYSISThis alarm indicates an inconsistency between the hardware items ofequipment and the software (EFT) downloaded from the OMC-R.


Step Action

1 Look at the notification and identify the object concerned.


411-9001-104 18.05 2 February 2010


.


If the btsSiteManager object is concerned, go to step 2. If the transceiverEquipment object is concerned, check

whether the "DRX automatic downloading" is activated or not: If the "DRX automatic downloading" is activated, go to

step 8. If the "DRX automatic downloading" is not activated, go

to step 3.






If the operationalState of the btsSiteManager object is"disabled-failed", and if there is an alarm with the faultnumber 1054, followed by alarms with fault numbers 1051,1052, 1053, lock the btsSiteManager object. Then unlock it. If the alarm with the fault number 1052 and the source 5

is still present, treat the alarm. Go to step 4. Otherwise, see the fault number 1054 (loss of layer

2) (see Nortel GSM BSS Fault Clearing - AdvancedMaintenance (411-9001-105) ).


3 Check the state of the site by performing the "Display all"command on the transceiverEquipment object. If the operationalState of the transceiverEquipment object is

"enabled", the DRX is operational. Clear the alarm. The procedure is complete

BTS S2000H_S2000L_e-Cell Fault Clearing

Documents

Transcript of BTS S2000H_S2000L_e-Cell Fault Clearing