411-9001-131(BSC TCU Fault Clearing)

Global System for Mobile Communications (GSM)Nortel GSM BSC 3000/TCU3000 Fault ClearingRelease: 18.0Document Revision: 18.07

www.nortel.com

411-9001-131.

Global System for Mobile Communications (GSM)Release: 18.0Publication: 411-9001-131Document release date: 12 March 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.

All other trademarks are the property of their respective owners.

.

3.

ContentsNew in this release 7Features 7Other Changes 7

Introduction 9Chapter 1 How to use this manual 111.1 Introduction 111.2 Description of a fault number sheet 12

Chapter 2 BSC 3000 fault numbers 152.1 Fault number: 47 152.2 Fault number: 1074 162.3 Fault number 1310 172.4 Fault number: 1315 192.5 Fault number: 1502 222.6 Fault number: 1503 242.7 Fault number: 1525 252.8 Fault number: 2000 (BSC 3000) 252.9 Fault number: 2001 (BSC 3000) 312.10 Fault number: 2004 372.11 Fault number: 2005 412.12 Fault number: 2006 422.13 Fault number: 2007 432.14 Fault number: 2008 (BSC 3000) 442.15 Fault number: 2009 (BSC 3000) 512.16 Fault number: 2010 (BSC 3000) 622.17 Fault number: 2011 (BSC 3000) 632.18 Fault number: 2012 642.19 Fault number: 2013 652.20 Fault number: 2014 (BSC 3000) 652.21 Fault number: 2015 662.22 Fault number: 2017 682.23 Fault number: 2018 692.24 Fault number: 2019 (BSC 3000) 70

Global System for Mobile Communications (GSM)Nortel GSM BSC 3000/TCU 3000 Fault Clearing

411-9001-131 18.07 12 March 2010


.

42.25 Fault number: 2020 722.26 Fault number: 2021 732.27 Fault number: 2022 752.28 Fault number: 2023 762.29 Fault number: 2024 (BSC 3000) 772.30 Fault number: 2026 802.31 Fault number: 2027 (BSC 3000) 812.32 Fault number: 2028 (BSC 3000) 832.33 Fault number: 2030 (BSC 3000) 842.34 Fault number: 2031 (BSC 3000) 842.35 Fault number: 2032 (BSC 3000) 852.36 Fault number: 2033 962.37 Fault number: 2034 (BSC 3000) 972.38 Fault number: 2035 992.39 Fault number: 2037 1002.40 Fault number: 2039 1022.41 Fault number: 2040 1032.42 Fault number: 2041 1032.43 Fault number: 2043 1042.44 Fault number: 2045 1042.45 Fault number: 2046 (BSC 3000) 1062.46 Fault number: 2047 (BSC 3000) 1082.47 Fault number: 2048 1102.48 Fault number: 2049 1112.49 Fault number: 2050 1122.50 Fault number: 2053 1122.51 Fault number: 2060 1152.52 Fault number: 2061 1162.53 Fault number: 2062 1172.54 Fault number: 2063 1192.55 Fault number: 2064 1202.56 Fault number: 2065 1212.57 Fault number: 2066 1222.58 Fault number: 2067 1242.59 Fault number: 2068 (BSC 3000) 1252.60 Fault number: 2069 (BSC 3000) 127Chapter 3 TCU 3000 fault numbers 1313.1 Fault number: 2000 (TCU 3000) 1313.2 Fault number: 2001 (TCU 3000) 1333.3 Fault number: 2008 (TCU 3000) 1353.4 Fault number: 2009 (TCU 3000) 1373.5 Fault number: 2010 (TCU 3000) 1453.6 Fault number: 2011 (TCU 3000) 146


411-9001-131 18.07 12 March 2010


.

53.7 Fault number: 2014 (TCU 3000) 1473.8 Fault number: 2019 (TCU 3000) 1483.9 Fault number: 2024 (TCU 3000) 1503.10 Fault number: 2025 1543.11 Fault number: 2027 (TCU 3000) 1553.12 Fault number: 2028 (TCU 3000) 1563.13 Fault number: 2030 (TCU 3000) 1573.14 Fault number: 2031 (TCU 3000) 1573.15 Fault number: 2032 (TCU 3000) 1583.16 Fault number: 2034 (TCU 3000) 1683.17 Fault number: 2036 1693.18 Fault number: 2042 1703.19 Fault number: 2046 (TCU 3000) 1723.20 Fault number: 2047 (TCU 3000) 1743.21 Fault number: 2051 1763.22 Fault number: 2068 (TCU 3000) 1773.23 Fault number: 2069 (TCU 3000) 179Chapter 4 Informational messages 183


411-9001-131 18.07 12 March 2010


.

6Global System for Mobile Communications (GSM)Nortel GSM BSC 3000/TCU 3000 Fault Clearing

411-9001-131 18.07 12 March 2010


.

7.

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

FeaturesThis document contains no feature updates in this release.

Other ChangesSee the following section for information about changes that are notfeature-related: added 2.3 Fault number 1310 (page 17)


411-9001-131 18.07 12 March 2010


.

8 New in this release


411-9001-131 18.07 12 March 2010


.

9.

IntroductionThis document explains how to clear a BSC 3000 or TCU 3000 fault on theOMC-R. It contains all the fault numbers of the BSC 3000 and TCU 3000.

PrerequisitesThe readers must be familiar with the following technical documents:

Nortel GSM BSS Documentation Roadmap (411-9001-000)

Nortel GSM BSS Fault Management Maintenance Principles(411-9001-039)

Nortel GSM BSS Fault Clearing Advanced Maintenance Procedures(411-9001-105)

Nortel GSM BSC 3000/TCU 3000 Fundamentals (411-9001-126)

Nortel GSM BSC 3000/TCU 3000 Troubleshooting (411-9001-132)

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

this maintenance manual. Chapter 2 BSC 3000 fault numbers (page 15), contains the fault

number description and the corrective maintenance proceduresapplicable to the BSC 3000.

Chapter 3 TCU 3000 fault numbers (page 131), contains the faultnumber description and the corrective maintenance proceduresapplicable to the TCU 3000.


411-9001-131 18.07 12 March 2010


.

10 Introduction


411-9001-131 18.07 12 March 2010


.

11.

Chapter 1 How to use this manual1.1 Introduction

This manual contains the fault number description and correctivemaintenance procedures that are only applicable to the BSC 3000 and theTCU 3000.

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

Network maintenance is based on graphical supervision of the network.

It is also based on the identification and replacement of faulty items ofequipment, using the alarms and 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 manual that describe on-site procedures (referto Nortel GSM BSC 3000/TCU 3000 Troubleshooting (411-9001-132))

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.

Description of the representation n+p: n : shows the minimum number of TMU so that all core processes are

at least in simplex mode. n+p : shows the necessary number of TMU so that all core processes

are in duplex mode.


411-9001-131 18.07 12 March 2010


.

12 Chapter 1 How to use this manual

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

number treatment

1.2.1 Header of the sheetThe header contains the following information: the fault number and possibly the cause the alarm type

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

This paragraph describes the fault and gives the alarm severity,indicated by the system state. MINOR: when an unbalanced distribution is detected by the Load

Balancing application with no resource missing MAJOR: when the system is in "exposure"

all the active core groups are running some of the passive core groups are not present

CRITICAL: when some of the active core groups are not present CLEARED: when Load Balancing considers that the applications

are well balanced on the Control NodeAlways : Warning/Cleared for every elements.Only Control Node, Interface Node and TCU object can be associatedwith Minor, Major or Critical level.

If fault number leads to the replacement of modules or boards, NortelGSM BSC 3000/TCU 3000 Troubleshooting (411-9001-131) indicateslocalization of these elements for each rack from BSC 3000 and TCU3000. Reaction of the system

Equipment units defense:This paragraph describes the defense actions taken by theequipment units.

Impact on service


411-9001-131 18.07 12 March 2010


.

1.2 Description of a fault number sheet 13

This paragraph gives the consequences of the alarm for service. Troubleshooting:

This paragraph gives the procedures or the flow charts to be followedto repair the fault and return the equipment to operational conditions.

Two conditions indicate failure: Maintenance task is necessary each time a fault has critical level

(Major or Critical) If it lasts more than 10 minutes (Disable failed)

Each procedure or flow chart is composed of three parts: preliminary checks that are used to ensure that the fault is confirmed

and that 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) that is used to startthe repair work and to ensure that the exchanged component willoperate correctly

additional checks, showing how to check that the fault has beencleared

If the fault number is still present after modules or boards replacement,move to the next highest level of support.


411-9001-131 18.07 12 March 2010


.

14 Chapter 1 How to use this manual


411-9001-131 18.07 12 March 2010


.

15.

Chapter 2 BSC 3000 fault numbers2.1 Fault number: 47

Fault number:47 : Cessation of active alarmsType : communicationsAlarm, environmentalAlarm, equipmentAlarm,

processingErrorAlarm, qualityOfServiceAlarm

FAULT ANALYSISThis notification can be sent in response to the following conditions: after a BSC, TCU, PCUSN, or BTS restart (probable cause number 64) when the OMC-R performs a purge of alarms as defined in the OMC-R

static configuration. The purge type can be purgeOnSaturation(Probable Cause 65) or dailyPurge (Probable Cause 66).

If the anomaly that triggered these alarms is still present after the BSC,TCU, or BTS restart, new alarms will be sent to the OMC-R. Thus, noinformation is lost.

If the anomaly that triggered these alarms is still present after purgeon saturation or daily purge, no new alarm is sent to the OMC-R andinformation is lost.

The notification concerns one alarm type (see the list given above in thetitle box).

The notification concerns one of the following objects: bsc,btsSiteManager, transcoder, pcu.

The type of alarm clearing is displayed in the probableCause field of thenotification.


411-9001-131 18.07 12 March 2010


.

16 Chapter 2 BSC 3000 fault numbers

probableCause No.

probableCausewording Type of alarm clearing

64 bscRequest notification sent by the BSC Purge performed by the BSC: consists

in sending a list of alarms which may becleared by the OMC-R if they are stillactive

65 purgeOnSaturation notification sent by the MD The defense purge consists in clearing

the oldest alarms. The threshold is fixedby the static configuration.

66 dailyPurge notification sent by the MD The daily purge consists in clearing

the alarms that are older than N days,every day. N is fixed by the staticconfiguration.

REACTION OF THE SYSTEMBSC defenseNone.

Impact on the serviceNone.

TROUBLESHOOTINGNo maintenance is required.

2.2 Fault number: 1074Fault number:1074 : Indication of non activated features on specific instancesType : equipmentAlarm

FAULT ANALYSIS

After a "Display all" command, the BSC sends a global notification thatlists all the TDMA where one (or more) feature is not activated. This faultalso gives the number of non activated features and the feature identifier.

Values of features_id field : Cell tiering (0) New L1m (1) GPRS service (2)


411-9001-131 18.07 12 March 2010


.

2.3 Fault number 1310 17

AMR (3) Call drop analysis (4) Distribution (5) GSM to UMTS handover (6) EMR-Enhanced Measurement report (7) AMR-HR on pre-empted PDTCH (8) A5/3 encryption algorithm (9) Not used (10) DTM support (11) Not used (12-31)

TROUBLESHOOTING

The notification shows the incompatibilities between the featuresconfigured by the operator and the hardware possibilities. Despitehardware compatibility, "GPRS service" is shown as disabled if: GPRS service is not activated on this cell there is at least one PDTCH missing in the TDMA configuration

2.3 Fault number 1310Fault number:1310 : An interface protocol error indicationType : communicationsAlarm

FAULT ANALYSIS

This warning notification is caused by a software anomaly on the Ainterface and the MSC. The BSC receives an unknown message from theMSC. Most often there is an incompatibility between what the MSC sendsand what the BSC knows. The "Source" field of the notification can containthe following values: 10 -Unknown CIC (in this case, data length (lg_data) = 2, and

the received CIC which is incorrect is dumped. This dump is inhexadecimal representation and appears in a form similar to 0x0799).

26 - Unknown IEI 27 - Bad length of element 51 - Unknown message in this way 52 - Too short reserved length - imperative reserved area


411-9001-131 18.07 12 March 2010


.


53 - Minimum length not respected 54 - Unknown message type 55 - Unknown message group 65 - Essential element missing 66 - Wrong mandatory element

The MSC version is incompatible with the BSC. The "Circuit IdentityCode" field contains the CIC coded number declared at the MSC level butunknown to the BSC. This is true for all of the 1310 fault.

REACTION OF THE SYSTEM

BSC defense

None. The TMG does not use these channels.

Impact on the service

The communication cannot be established on the considered channels.

TROUBLESHOOTING

Maintenance using the OMC-R

Step Action

1 Look at the source given in the "Source" field of the notification. If the source is "10 Unknown CIC", go to step 2. If the source is "26", "27", 1"51", "52", 1"53", "54", "55", "65",

or "66", it is a transient problem. If this notification is oftenemitted, call the manufacturer.

2 Search for the reason why there is such an inconsistentconfiguration. If it was configured this way on purpose, to prepare a network

extension for instance, this fault number emission is normal,and no maintenance is required. Go to step 4.

If it was not configured this way on purpose, then there is anerror in the configuration. Go to step 3.


411-9001-131 18.07 12 March 2010


.

2.4 Fault number: 1315 19

3 Correct the inconsistent configuration in one of the followingways: At the OMC-S, delete the CIC indicated in the notification, OR At the OMC-R, create the equivalent CIC for the BSC, and

the xtp objects as well.Additional Checks4 Check the notification state in the "Current alarm list" window.

If the notification has disappeared, go to step 7. If the notification persists, go to step 5.

5 Check the state of the TCU, by performing a "Display all"command on the object concerned. If the operationalState of the object is "enabled", the fault is

not confirmed. Go to step 6. If the operationalState of the object is "disabled", and the

availabilityStatus is "failed", call the manufacturer.

6 Clear the notification.7 The procedure is complete.

--End--

2.4 Fault number: 1315Fault number:1315 : Path information for calls released by TCU or BTSType : communicationsProtocolError

FAULT ANALYSIS

Perceived severity: WARNING

In cases where there is a loss of communication between the TCU andthe BTS, the user would hear only silence and would eventually terminatethe call. The system now detects these types of failures and releases thecall automatically.

This warning notification is sent to indicate the path associated with thedropped call to facilitate troubleshooting the problem.

This notification indicates that either the BTS or the TCU has detecteda loss of frame synchronization. The call is released and the followingcounters are incremented:


411-9001-131 18.07 12 March 2010


.


C1164/32 if the BTS detects the fault C1164/28 if the TCU detects the fault

The warning is subject to a threshold: 100 occurrences (of call releasedper cellGroup) affecting the same path will result in 1 warning at theOMC-R.

The fault could be indicative of Transmission Line failure, TransmissionEquipment failure (i.e. DACS) or a failure within the BSC 3000 or TCU3000 or BTS.


BSC defense

None.


Calls have been dropped.

TROUBLESHOOTING

Preliminary checks

Step Action

1 Monitor counter C1164 to determine the frequency of occurrenceand which transmission direction is affected: C1164/28: Indicates a failure in the path from BTS to TCU. C1164/32: Indicates a failure in the path from TCU to BTS.

ATTENTIONEither one may be caused by a failure of either ABIS or ATER PCM.

2 Check for any notifications relating to the BSC, TCU orTransmission links (PCM), treat these symptoms first then verifyif counters are still incremented. If the counters are no longer incremented, the fault is not

confirmed, go to step 8. If the counters are still incremented, go to step 3.

3 Use the information provided in the notification 1315 to know thefailing path:


411-9001-131 18.07 12 March 2010


.


date: date of the drop call cic: identifies the BSC/MSC CIC trm: the TRM board number in the TCU 3000 archipel: archipelago of the used TRM architecture: (4) TCU 3000 pcm_ater: ATER PCM number ts_ater: timeslot on ATER PCM tcu_circ: internal Ater TCU circuit (16K channel) number pcm_abis: ABIS PCM number ts_abis: timeslot on ABIS PCM pcm_circ: internal Abis pcm circuit (16K channel) number cell_group: cell group number cell: BSC internal cell Id TDMA: TDMA number channel: channel number on TDMA

Then go to step 4.On-site maintenance using the OMC-R

4 Using the decoded path information provided in the notification1315, look for reoccurring instances of the same object (i.e.TRM, PCM, Timeslot). If the most commonly failing object is a PCM or Timeslot,

determine if it is an ATER or ABIS PCM. Go to step 5. If failure is associated with the same TRM, replace the TRM.

Refer to Nortel GSM BSC 3000/TCU 3000 Troubleshooting(411-9001-132).

5 Confirm the failing path: Try to physically swap PCMs, or lock one PCM at a time. Try to lock impacted Radio Channels. Verify if counter C1164 is still incremented.

If counters are no longer incremented, fault on Abis orAter PCM is confirmed, go to step 6.

If counters are still incremented, the fault on Timeslots isconfirmed, go to step 7.

6 If either the ATER or ABIS PCM pass through intermediateequipment such as a DACS:


411-9001-131 18.07 12 March 2010


.


Check the DACS board that manages the PCM and theDACS configuration.

The DACS (and many other types of transmission equipment)will often have counters indicating errors, errored seconds,BPVs, slips, or Frame errors. Use these to localize thesource of the problem.

ATTENTIONDepending on the type of DACS, it may re-frame the signal, whichwould tend to mask alarms and some types of errors (slips, notably).

All transmission facilities should be configured to useappropriate zero-code suppression (i.e., B8ZS for DS1facilities).

7 Using suitable test equipment, perform end-to-end quality test offailing PCM, ensuring that all Timeslots are checked. If the failing PCMs are associated with the same LSA,

perform a SWACT of the associated IEM. If problem is not identified, call the manufacturer.

8 The procedure is complete.

--End--

2.5 Fault number: 1502Fault number:1502 : Access attempt to a non operational cellType : qualityOfServiceAlarm

FAULT ANALYSIS

This message warns the operator that an access attempt to a nonoperational cell has been made. This can be due to: an access attempt to a non-created cell paging attempted on a cell in which paging is not authorized paging on a cell in which all System Information messages have been

acknowledged

This notification indicates a configuration problem.

When Cell is created, but not operational then the fault number 1502 issent to the OMC-R. This could happen when:


411-9001-131 18.07 12 March 2010


.


1. Cell has been created, attributed and then de-attributed.After the creation of the cell, a cell in Operational state is attributed afterreceiving Sys Info Acknowledgments from BTS.A Cell in Operational state is de-attributed, when the cell is out of servicein BSC.

Fault number 1502 is sent to OMC-R, after one of the following call flowsoccurs:Call Flow 1A Channel Required message is sent to the BSC (Traffic Management).Traffic management issues fault number 1502.Call Flow 2An inter-cell handover is requested for a call setup on its destination cell(inter or intra BSC).An Access Request message is sent to the BSC (Traffic Management).Traffic management issues fault number 1502.

Fault number 1502 is issued for the following reason:If the CCCH downlink channel is not initialized and if the BSC is in theactive mode, fault number 1502 is triggered. The warning is issued, ifthis scenario is executed more than 100 times. The limitation of 100times exists because of a warning threshold present in RADCEL warningmanagement.

2. Cell has been created but not attributed.The cell has not been attributed by SPR (Radio supervision), i.e., Sys InfoExchange has not happened between BSC and BTS for this cell.

FIELD DESCRIPTION

Target CGI:

Examplecell parameters: mcc, LAC, mnc, and ci

Cell Admin State:

Example0: not created205: created

Cell Paging State:

Example0: not significant1: not allowed because BCCH information not acknowledged2: paging request allowed


411-9001-131 18.07 12 March 2010


.


Radio Data Consistency for TMG point of view:

Example0: consistent1: inconsistent

TS Carrying Common Channel:

ExampleTS carrying common channel


BSC defense

None.


None.

ATTENTIONService is reduced.

TROUBLESHOOTING

Check the configuration against the information given in the notification.

2.6 Fault number: 1503Fault number:1503 : Access Attempt to an unknown BCCH or BSICType : communicationsAlarm

FAULT ANALYSIS

This anomaly is sent when a handover is required towards a (bsic,bcch)not belonging to the neighboring cells of the originated cell.

This alarm indicates that a mobile sent measurement reports withmeasures reported from an unknown neighbor cell identified by the couple(BCCH, BSIC) which is not declared in the adjacent handover cell list atthe OMC-R.


BSC defense


411-9001-131 18.07 12 March 2010


.

2.8 Fault number: 2000 (BSC 3000) 25

None


None.

TROUBLESHOOTING

To solve this problem, check the frequency plan and the frequency bands.For the cells found in the Session Log, verify the accuracy of the datafill(BSIC/BCCH) for the impacted cell (on the bts object) and its neighboringcells.

2.7 Fault number: 1525Fault number:1525 : Modification of Agprs configurationType : warning

FAULT ANALYSIS

After running Agprs cell allocation online and offline algorithms, if thereis a change in Agprs configuration, this warning "Modification of Agprsconfiguration" is sent by SPP to the OMC-R. This warning describesexhaustively the Agprs interface configuration. The OMC-R treats thenotification and stores the information in a configuration file on SDO.

This warning indicates the new mapping of cells on Agprs interface,allowing monitoring tools to perform Agprs statistics per PCM.

TROUBLESHOOTING

No maintenance is required.

The configuration of the Agprs being automatically reported to the OMC-R,the operator has access to new configuration data that can be processedby PrOptima. Agprs metrics per PCM can then be computed allowingimproving monitoring and optimization processes.

2.8 Fault number: 2000 (BSC 3000)Fault number:2000 : Power failureType : EquipmentAlarm

FAULT ANALYSIS


411-9001-131 18.07 12 March 2010


.


ATTENTIONThis fault number also applies to TCU 3000. See 3.1 Fault number: 2000 (TCU3000) (page 131).

Perceived severity: MAJOR/CLEARED

This notification can appear for the Control Node or the Interface Node intwo different cases: after a period of normal operating (only after reset of the module) on board insertion and incorrect MIM reading

Fault number 2000 can come either from the Interface Node or from theTranscoder Node.

The managed objects (MOs) are: atmRm, cc, cem, cem3, controlNode,hsaRc, , iem, interfaceNode, iom, lsaRcBsc, mms, omu, sw8kRm, tmu.

The managed objects (MOs) are: atmRm, cc, cem, cem3, controlNode,hsaRc, , iem, igm, interfaceNode, iom, ipgRc, lsaRcBsc, mms, omu,sw8kRm, tmu.

The type, position and slot number of the module are given in thenotification.

The modules are involved in the Control Node can be one of the following: OMU MMS TMU TMU3 ATM-SW (CC1)

The modules involved in the Interface Node can be one of the following CEM CEM3 ATM-RM LSA-RC HSA-RC 8K-RM IGM IPG


411-9001-131 18.07 12 March 2010


.

2.8 Fault number: 2000 (BSC 3000) 27


The modules are redundant.

If the first module is involved, there is no impact on the service.

Case of the shared MMS module and notification after a period ofnormal operating

CAUTIONService interruptionWhen the second module is involved, service is lost.

Case of the TMU module (with configuration)ATTENTIONThere is a potential service degradation if less than "n" boards are available.Otherwise, there is no impact on service.

A 2004 fault number may appear.

Case of OMU module or its private MMS

In the case of a fault on the active OMU module, restart is automatic onthe other OMU module.

In the case of a fault on the passive OMU module, redundancy is lost.

Case of ATM-SW module


CAUTIONService interruptionIf one ATM-SW module is faulty, as soon as the other ATM-SWmodule is faulty, service is lost.

TROUBLESHOOTING

Fault 2000 can occur either at the control node or the interface node.

If the fault originates in the control node, refer to the following flow chart.

If the fault originates in the interface node, perform a "display all"command to confirm the status of the modules and replace the moduleidentified in the notification. (The red LED on the failed module will be lit).


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.8 Fault number: 2000 (BSC 3000) 29


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.9 Fault number: 2001 (BSC 3000) 31

2.9 Fault number: 2001 (BSC 3000)Fault number:2001 : Hardware not supportedType : EquipmentAlarm

FAULT ANALYSIS



This diagnosis event is mapped Control Node object and is sent as Major(for BSC 3000) to OMC-R in the following cases: At module insertion when the module "PEC code" is not supported by

the Control Node software (not referenced in MIB) At module insertion when the synchronization with the module software

cannot be done (time-out) After an upgrade procedure, for modules with a "PEC code" that is no

longer supported (no more referenced in MIB) After a replacement procedure, for modules that are not compatible

with the existing configuration (for example when the disk size doesntmatch, because a MMS2 can only be replaced by a MMS2, and notby a MMS1)

If a TML user attempts to set the parameter BscSharedDiskCapacity toHigh for an MMS that does not support it (for example, an MMS1 or anMMS2 serving as a spare for a MMS1)

After reset or restart, if the synchronization with the module softwarecannot be done (time-out)

This diagnosis event is cleared when, after an upgrade, a not supported"PEC code" becomes supported (referenced in the new MIB).

It must be purged when a purge event including this codano is sent on theobject this diagnosis event is mapped on.

In this diagnosis event, the concerned module is given in the hardwareslot position field.

The type, position, and slot number of the module are given in thenotification.


411-9001-131 18.07 12 March 2010


.


The managed Object is: controlNode, transcoder, inode

For the interfaceNode, this fault is not sent.

The modules are involved in the controlNode. They can be one of thefollowing: OMU module MMS module TMU module ATM-SW module


BSC 3000 defense

None.

TROUBLESHOOTING

For the troubleshooting of the 2001 fault number, refer to the following flowchart.


411-9001-131 18.07 12 March 2010


.

2.9 Fault number: 2001 (BSC 3000) 33


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.9 Fault number: 2001 (BSC 3000) 35


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.


2.10 Fault number: 2004Fault number:2004 : Load balancing performedType : QualityOfServiceAlarm

FAULT ANALYSIS

Perceived severity: MINOR/MAJOR/CRITICAL/CLEARED

The notification 2004 warns the operator that the current Core Processdistribution is not satisfactory. It is automatically cleared by the BSC whenthe Core Process distribution becomes satisfactory.

This notification can appear in two cases: Capacity increase problem: btsSiteManager or transceiverEquipment

objects are created and the system cannot support them. A loadbalancing operation is performed. Supplementary TMU modules arerequired. Refer to the "Number of TMU" field of the notification todetermine the number of TMU modules inserted in the cabinet.

Hardware problem. Two different cases are possible: some TMU modules are faulty: the load balancing operation allows

allocation of resources on the remaining TMU modules some TMU are added: the load balancing operation allows

allocation of resources on all the TMU modules

The Managed Object is: controlNode.

The three additional problems which could occur in notification are: Addobjects, Add/Remove modules from TMU, Software failure.

Reminder:

A core process is duplex when TMUs, in term of load, can manage boththe active and passive processes.

A core process is simplex when TMUs, in term of load, can manage onlythe active process ("Error type" field: simplex).

A core process is nullex when TMUs, if any, can manage neither the activeprocess nor the passive process ("Error type" field: nullex).

Here is the list of the core group types:


411-9001-131 18.07 12 March 2010


.


Current core group type: SS7 Current core group type: PCU Current core group type: TCUe3 Current core group type: CellGroup

"Number of present TMU" field: indicates the number of TMU currentlyinstalled in the BSC.

"Number of missing TMU" field: indicates the number of potentially missingTMU. This number is defined as follows:1. If the current Core Process distribution is such that all Core Groups are

duplex, then the number of potentially missing TMU is equal to 0.2. Otherwise, the number of potentially missing TMU is defined as

the smallest number of TMU required such that the Core Processdistribution is full duplex after an online load reconfiguration or a BSCrestart. Refer to the Troubleshooting section when this number is notequal to 0, and in all cases when the notification is "Major" or Critical".

"Reconfiguration recommendation" field: quantifies the benefit of applyingan online load reconfiguration (0 : negative, 1 : null, 2 : low, 3 : strong,4 : mandatory).

This notification is declared: "MINOR" when an unbalanced distribution is detected by the Load

Balancing application with no resource missing. In that case, the"Number of TMU missing" field is equal to 0 for the current distribution.

"MAJOR" when the system is likely to be impacted: All the active Core Groups are running Some of the passive Core Groups are not present:

the "Number of bad core groups" field of the current distributionis not equal to 0

the "Error type" field is equal to SIMPLEX for all the CoreGroups in error.

"CRITICAL" when the system capacity is reduced: some of the active Core Groups are not present


411-9001-131 18.07 12 March 2010


.


the "Number of bad core groups" field of the current distributionis not equal to 0

at least one of the "Error type" fields is equal to MISSING forthe Core Groups in error

"CLEARED" automatically when Load Balancing considers thatapplications are well balanced on the Control Node. In that case, the"Number of bad core groups" field of the current distribution is 0.


When this alarm 2004 is raised, the state of the ControlNode ManagedObject is changed to Enabled / { degraded }.

When some Core Groups are NULLEX, the state of the correspondingGSM objects (btsSiteManager, bts, transceiverEquipment, etc..) ischanged to "Disabled/Dependency".

When this alarm 2004 is cleared, the state of the ControlNode ManagedObject is changed to "Enabled".

TROUBLESHOOTING

For the troubleshooting of the "MAJOR" or "CRITICAL" 2004 fault number,refer to Figure 1 "Flowchart for the major or critical 2004 fault number"(page 40).


411-9001-131 18.07 12 March 2010


.


Figure 1Flowchart for the major or critical 2004 fault number

For the troubleshooting of the "MINOR" 2004 fault number, refer to Figure2 "Flowchart for the minor 2004 fault number" (page 41).


411-9001-131 18.07 12 March 2010


.


Figure 2Flowchart for the minor 2004 fault number

2.11 Fault number: 2005Fault number:2005 : Load balancing resultType : QualityOfServiceAlarm

FAULT ANALYSIS


This notification gives the result after each load balancing operation.It gives the current process distribution over the available TMUs. Thisnotification gives the following information: the call processing load (given in Erlangs) of the TMU after execution

of load balancing the number of used active and passive internal LAPD ports the list of active and passive of the CellGroup present on this TMU


Reminder:


411-9001-131 18.07 12 March 2010


.


A core process is duplex when TMUs, in term of load, can manage boththe active and passive processes.

A core process is simplex when TMUs, in term of load, can manage onlythe active process (Error type: simplex).

A core process is nullex when TMUs, if any, can manage neither the activeprocess nor the passive process (Error type: nullex).

Here is the list of the core group types: Current core group type : SS7 Current core group type : PCU Current core group type : TCUe3 Current core group type : TCU2g Current core group type : Cell Current core group type : PLG (PCU LAPD Group)

TROUBLESHOOTING

Maintenance action is not applicable.

2.12 Fault number: 2006Fault number:2006 : End of load reconfigurationType : EquipmentAlarm

FAULT ANALYSIS

The warning 2006 notifies the operator that a load reconfiguration hasbeen either completed or aborted, as indicated in the "Status" field: 0 : "completed" 1 : "aborted on board event" if the reconfiguration was aborted due to a

TMU event: Failure or recovery of a TMU: in this case, the TMU event is

processed normally and, as a consequence, as much as isreasonably possible of the active or passive Core Processes whichmight still be interrupted are recreated.

Failure of a Core Process termination, service-preserving migrationor creation during the reconfiguration (note that such a failureresults in a TMU reset).


411-9001-131 18.07 12 March 2010


.





BSC defense

None.


None.

TROUBLESHOOTING

No maintenance action is required.

2.13 Fault number: 2007Fault number:2007 : Overload threshold crossedType : QualityOfServiceAlarm

FAULT ANALYSIS


This is a software capacity problem on the OMU or TMU modules.

The software capacity of the modules is involved. There are three overloadthresholds: Overload level 1 and level 2:

These are the predefined overload thresholds which carry out ofdifferent defenses in the GSM applications. They damage the service,but this damage is not perceived by the OMC-R operator.

Overload level 3:This is a predefined overload threshold. It is sent when a predefinedoverload threshold is crossed. In this case an alarm appears. Thealarm is cleared when the overload value return to less than thethreshold (which can be seen on a hysteresis). This overload levelcauses a loss of some service.



411-9001-131 18.07 12 March 2010


.


Overload threshold notifications are sent or cleared under the followingcircumstances: Notification is sent with severity Major when Overload level 3 is

crossed. Notification is cleared when Overload returns to a level lower than 3. No notification is sent when level 1 or level 2 are crossed.

Notification contains the following data: list of modules which have crossed level 3 resource in overload level 3 for each module in overload.


The overload levels 1 and 2 cause a damage of service (for examplereduction of service: paging).

The overload level 3 causes a loss some of service (for example, only onecell is managed).

TROUBLESHOOTING

Maintenance action is not applicable.

2.14 Fault number: 2008 (BSC 3000)Fault number:2008 : Hardware failureType : EquipmentAlarm

FAULT ANALYSIS


Perceived severity: MINOR/MAJOR/CLEARED

This diagnosis event (ANO_HARDWARE_FAILURE ON HARDWAREOBJECTS) is sent in the following cases: After module insertion, if the "flash" of the module cannot be

downloaded At module insertion, when the "BIST" of the module are failed


411-9001-131 18.07 12 March 2010


.

2.14 Fault number: 2008 (BSC 3000) 45

After a reset or a restart, when the "BIST" of the module are failed When an "OC3 fiber" is detected as failed (in fact that may be a

disconnection done by the craft person or a real "OC3 fiber" failure)

This diagnosis event is mapped on the hardware object associated to thefaulty module or supporting the faulty "OC3 fiber".

This diagnosis event is sent as Warning (for BSC 3000) or Major toOMC-R.

This diagnosis event is cleared when the concerned object is no more infault and must be purged when a purge event including this codano is senton the object this diagnosis event is mapped on.

In this diagnosis event, the concerned module is given in the hardwareslot position field.

In this diagnosis event, the cause of the failure ("flashing", "BIST" or "OC3fiber" problem) is given in the MANUF information field.

This diagnosis event (ANO_HARDWARE_FAILURE ON CONTROL NODEOBJECT) is sent as Major (for BSC 3000 and to OMC-R in the followingcases:

When a "Power connection and Interface Unit (PCIU)" failure isdetected for a BSC 3000

When an "Ethernet-Ethernet link" failure is detected (time-out)

This diagnosis event is mapped on Control Node object and is clearedwhen the cause of this diagnostic event is no more applicable and mustbe purged when a purge event including this codano is sent on the objectthis diagnosis event is mapped on.

In this diagnosis event, the passive concerned equipment (notdescribed as an object managed by the OMC-R) is given in theAdditional_Info_On_Faulty_Equipment field.

This notification appears each time the Hardware Management detects ahardware failure.

This notification provides the following information for the Control Node: it specifies if the event is sent immediately after a restart or not it contains the shelf number (0 or 1) and the slot number (from 1 to 15)

of the faulty module. it contains the following data if it is available:


411-9001-131 18.07 12 March 2010


.


serial number PEC number of the IEM board hardware release

ATTENTIONIf the software application is not able to determine which component is faulty,one or two modules which might be impacted by the failure can also appear inthe notification.

For the Interface Node, this failure information is transmitted by the faultnumber 2032: Miscellaneous SPM alarm.

The managed objects (MOs) (MO) are: atmRm, cc, cem, cem3,controlNode, hsaRc, iem, interfaceNode, iom, lsaRcBsc, mms, omu,sw8kRm, tmu.

The managed objects (MOs) (MO) are: atmRm, cc, cem, cem3,controlNode, hsaRc, iem, igm, igprc, interfaceNode, iom, lsaRcBsc, mms,omu, sw8kRm, tmu.

The elements involved can be any of the following: in the frame assembly:

PCIU assembly inter control card link

in the Control Node: OMU module MMS module TMU module ATM-SW (called CC1) module



If the first module is involved, there is no impact on the service.

Case of the shared MMS module and notification after a period ofnormal operating


411-9001-131 18.07 12 March 2010


.

2.14 Fault number: 2008 (BSC 3000) 47

CAUTIONService interruptionWhen the second module is involved, service is lost.

Case of the TMU module (with n+p configuration)

Reminder: - n : shows the minimum number of TMU so that all the core processes

should be at least simplex. - n+p : shows the number of necessary TMU so that all the core

processes should be duplex.

ATTENTIONThere is a potential service degradation if less than "n" boards are available.Otherwise, there is no impact on service.

A 2004 fault number may appear.

Case of the OMU module or its private MMS

In the case of a fault on the active OMU module, restart is automatic onthe other OMU module.

In case of a fault on the passive OMU module, redundancy is lost.

Case of the ATM-SW module

These modules are redundant.

CAUTIONService interruptionIf one ATM-SW module is faulty, as soon as the other ATM-SWmodule is faulty, the service is lost.

TROUBLESHOOTING

The troubleshooting depends on the module implication in the hardwarefailure. The action associated with the fault may differ. Most of the time,the action to be carried out is the replacement of the impacted module.

If fault 2008 occurs in the control node, use the following flow chart.


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.14 Fault number: 2008 (BSC 3000) 49


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.15 Fault number: 2009 (BSC 3000) 51

2.15 Fault number: 2009 (BSC 3000)Fault number:2009 : PCM failureType : CommunicationsAlarm

FAULT ANALYSIS



A PCM link is faulty if any of the following alarms are triggered for FBT(Fault Begin Time) consecutive seconds: LOS, AIS, LFA, FE, CRC, RAI,E-Bits.

The alarms are listed by priority, from the highest (LOS) to the lowest(E-Bits).

An alarm is cleared when no alarm threshold (LOS, AIS, LFA, FE, CRC,RAI, E-bits) is detected for at least FET (Fault End Time) consecutiveseconds.

The Managed Object (MO) is pcmCircuit.

This notification provides the following information: it specifies whether the event is sent right after a restart or not it contains the shelf number (from 0 to 1) hosting the LSA-RC

connecting the PCM and its position within the shelf (from 1 to 15) it contains the type of PCM: E1 or T1 it contains the Threshold value:

FBT value if alarm severity is major FET value if alarm severity is cleared

the time elapsed in faulty state:this information is significant when the severity is cleared

the length of time the alarms are triggered (in seconds): the length of time the LOS alarm is triggered (nd_sec_LOS) the length of time the AIS alarm is triggered (nd_sec_AIS) the length of time the LFA alarm is triggered (nd_sec_LFA)


411-9001-131 18.07 12 March 2010


.


the length of time the FE alarm is triggered (nd_sec_FE)this number is not significant for T1

the length of time the CRC alarm is triggered (nd_sec_CRC) the length of time the RAI alarm is triggered (nd_sec_RAI) the length of time the E-Bits alarm is triggered (nd_sec_E-Bits)

At the given time, if multiple alarms are detected, only the alarm with thehighest priority is logged.

In this case for example, the alarm is raised with the following values forthe different errors: nd_sec_LOS=3 seconds nd_sec_AIS=1 second nd_sec_LAF=2 seconds nd_sec_FE=1 second nd_sec_CRC=1 second nd_sec_RAI=0 second nd_sec_E-Bits=1 second


The reaction of the system depends on the type of PCM links (Ater,Abis...).

TROUBLESHOOTING



411-9001-131 18.07 12 March 2010


.

2.15 Fault number: 2009 (BSC 3000) 53


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.15 Fault number: 2009 (BSC 3000) 55


411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.15 Fault number: 2009 (BSC 3000) 57


411-9001-131 18.07 12 March 2010


.


The following tables give the relation between PCM links andLSA-RC/CTU modules (or HSA-RC modules). For more informationon logical slot numbering inside BSC 3000 cabinet (whether electricalor optical), see Nortel GSM BSC 3000/TCU 3000 Troubleshooting(411-9001-132).

Table 1Relation between the PCM E1 link number and the LSA-RC/CTU module in use located in theBSC 3000

Logical PCM numberLSA 0 LSA 1 LSA 2 LSA 3 LSA 4 LSA 5Port numberdisplayed at

the OMC-R

Physical portnumber ona LSA-RCmodule CTU 4 CTU 0 CTU 1 CTU 2 CTU 5 CTU 3

0 0 0 21 42 63 84 105


411-9001-131 18.07 12 March 2010


.

2.15 Fault number: 2009 (BSC 3000) 59

Table 1Relation between the PCM E1 link number and the LSA-RC/CTU module in use located inthe BSC 3000 (contd.)


the OMC-R


1 1 1 22 43 64 85 106

2 2 2 23 44 65 86 107

|||

|||

|||

|||

|||

|||

|||

|||

19 19 19 40 61 82 103 124

20 20 20 41 62 83 104 125

Table 2Relation between the PCM T1 link number and the LSA-RC/CTU module in use located in theBSC 3000


the OMC-R


0 0 0 28 56 84 112 1401 1 1 29 57 85 113 1412 2 2 30 58 86 114 142|||

|||

|||

|||

|||

|||

|||

|||

26 26 26 54 82 110 138 16627 27 27 55 83 111 139 167

Table 3Relation between the STM1 virtual PCM number and the HSA-RC module in use located in theBSC 3000

Logical PCM numberPort number displayedat the OMC-R

Virtual port number ona HSA-RC module HSA 0 HSA 1

0 0 147 210


411-9001-131 18.07 12 March 2010


.


Table 3Relation between the STM1 virtual PCM number and the HSA-RC module in use located inthe BSC 3000 (contd.)



1 1 148 2112 2 149 212|||

|||

|||

|||

61 61 208 27162 62 209 272

Table 4Relation between the OC3 virtual PCM number and the HSA-RC module in use located in theBSC 3000



0 0 196 2801 1 197 2812 2 198 282|||

|||

|||

|||

82 82 278 36283 83 279 363

Table 5HSA-RC and STM1 port mapping

Location in the hierarchy Standards equivalentsVirtual portnumber on a

HSA-RCK (See Note

1)L (SeeNote 2)

M (SeeNote 3) KLM number ITU-T Number

0 21 42 1 2 3 1 1 1 22 43 1 2 31 22 43 1 2 3 2 1 4 25 46 4 5 62 23 44 1 2 3 3 1 7 28 49 7 8 93 24 45 1 2 3 4 1 10 31 52 10 11 124 25 46 1 2 3 5 1 13 34 55 13 14 155 26 47 1 2 3 6 1 16 37 58 16 17 18


411-9001-131 18.07 12 March 2010


.

2.15 Fault number: 2009 (BSC 3000) 61

Table 5HSA-RC and STM1 port mapping (contd.)

Location in the hierarchy Standards equivalentsVirtual portnumber on a

HSA-RCK (See Note

1)L (SeeNote 2)

M (SeeNote 3) KLM number ITU-T Number

6 27 48 1 2 3 7 1 19 40 61 19 20 217 28 49 1 2 3 1 2 2 23 44 22 23 248 29 50 1 2 3 2 2 5 26 47 25 26 279 30 51 1 2 3 3 2 8 29 50 28 29 3010 31 52 1 2 3 4 2 11 32 53 31 32 3311 32 53 1 2 3 5 2 14 35 56 34 35 3612 33 54 1 2 3 6 2 17 38 59 37 38 3913 34 55 1 2 3 7 2 20 41 62 40 41 4214 35 56 1 2 3 1 3 3 24 45 43 44 4515 36 57 1 2 3 2 3 6 27 48 46 47 4816 37 58 1 2 3 3 3 9 30 51 49 50 5117 38 59 1 2 3 4 3 12 33 54 52 53 5418 39 60 1 2 3 5 3 15 36 57 55 56 5719 40 61 1 2 3 6 3 18 39 60 58 59 6020 41 62 1 2 3 7 3 21 42 63 61 62 63

Note 1: Tributary Unit Group 3Note 2: Tributary Unit Group 2Note 3: Virtual Tributary

Table 6HSA-RC and OC3 VT1.5 port mapping

Location in the hierarchyVirtual port number on a HSA-RC STS Group VT

0 28 56 1 2 3 1 11 29 57 1 2 3 2 12 30 58 1 2 3 3 13 31 59 1 2 3 4 14 32 60 1 2 3 5 15 33 61 1 2 3 6 16 34 62 1 2 3 7 17 35 63 1 2 3 1 28 36 64 1 2 3 2 2


411-9001-131 18.07 12 March 2010


.


Table 6HSA-RC and OC3 VT1.5 port mapping (contd.)

Location in the hierarchyVirtual port number on a HSA-RC STS Group VT

9 37 65 1 2 3 3 210 38 66 1 2 3 4 211 39 67 1 2 3 5 212 40 68 1 2 3 6 213 41 69 1 2 3 7 214 42 70 1 2 3 1 315 43 71 1 2 3 2 316 44 72 1 2 3 3 317 45 73 1 2 3 4 318 46 74 1 2 3 5 319 47 75 1 2 3 6 320 48 76 1 2 3 7 321 49 77 1 2 3 1 422 50 78 1 2 3 2 423 51 79 1 2 3 3 424 52 80 1 2 3 4 425 53 81 1 2 3 5 426 54 82 1 2 3 6 427 55 83 1 2 3 7 4

2.16 Fault number: 2010 (BSC 3000)Fault number:2010 : ISIMA failureType : Equipment alarm

FAULT ANALYSIS




411-9001-131 18.07 12 March 2010


.

2.17 Fault number: 2011 (BSC 3000) 63

Diagnostic event ANO_ALIMA_FAILURE is sent as Major (for BSC 3000)to the OMC-R, when the Control Node [shelf0/slot15] or Interface Node[shelf0/slot15] "ALIM" module is either not present, or extracted, or faulty(the Control Node and Interface Node software can not distinguish thesecases).

This diagnostic event is mapped on the Control Node or Interface Nodeobject and is cleared when its cause is removed. This diagnostic event ispurged when a purge event including its fault number is sent to the objectwhich is mapped with the diagnostic event.

The managed objects (MOs) are: controlNode, interfaceNode


A state change on the interfaceNode object occurs when the alarm 2010is raised at the OMC-R : the operationalState is still "enabled", but theavailabilityStatus becomes "degraded".

TROUBLESHOOTING

The following maintenance is required: If the power module is extracted, insert it and turn it on. If the power module is turn off, turn it on. In other cases, replace the SIM module. Refer to its procedure in

Nortel GSM BSC 3000/TCU 3000 Troubleshooting (411-9001-132).

2.17 Fault number: 2011 (BSC 3000)Fault number:2011 : ISIMB failureType : Equipment alarm

FAULT ANALYSIS




411-9001-131 18.07 12 March 2010


.


Diagnostic event ANO_ALIMB_FAILURE is sent as Major (for BSC 3000)to the OMC-R, when the Control Node [shelf1/slot15] or Interface Node[shelf1/slot15] "ALIM" module is either not present, or extracted, or faulty(the Control Node and Interface Node software can not distinguish thesecases).


The managed objects (MOs) are: controlNode, interfaceNode



TROUBLESHOOTING

The following maintenance is required: If the power module is extracted, insert it and turn it on. If the power module is turn off, turn it on. In other cases, replace the SIM module. Refer to its procedure in

Nortel GSM BSC 3000/TCU 3000 Troubleshooting (411-9001-132).

2.18 Fault number: 2012Fault number:2012 : Loss of A interface (or no establishment) with MSCType : CommunicationsAlarm

FAULT ANALYSIS

Perceived severity: CRITICAL

This fault is sent to indicate that SCCP configuration is not valid (especiallywhen "SCCP routing indicator" is not set correctly).

This fault is effectively sent if SCCP layer cannot be connected betweenthe BSC 3000 and the MSC.


411-9001-131 18.07 12 March 2010


.

2.20 Fault number: 2014 (BSC 3000) 65

This fault can be sent after a Control node startUp, after an IN restart orafter two TCU restarts. It can also be raised if all SS7 links are lost to anoperating BSC.

The Managed Object is: signallingLinkSet


SS7 service is not present (loss of service).

TROUBLESHOOTING

The following maintenance is required: Check the SCCP configuration on the BSC side and on the MSC side. This fault could also occur if all of the SS7 links are out of service. In

this case, a 2012 potential fault is transmitted.

2.19 Fault number: 2013Fault number:2013 : SS7 SSN LCSType : QualityOfServiceAlarm

FAULT ANALYSIS


This notification is sent when a client of the SS7 protocol becomesavailable or becomes unavailable (at each state change of the SSN LCS).

The Managed Object (MO) is: signalingLinkSet.

TROUBLESHOOTING


2.20 Fault number: 2014 (BSC 3000)Fault number:2014 : IFan failureType : Equipment alarm

FAULT ANALYSIS


411-9001-131 18.07 12 March 2010


.




Diagnostic event ANO_FAN_FAILURE is sent as Major (for BSC 3000) tothe OMC-R, when a "Cooling Unit" failure is detected on the Control Nodeor Interface Node.


The managed objects (MOs) are: controlNode are interfaceNode.



The state change does not occur on the controlNode object.

TROUBLESHOOTING

The following maintenance is required: If a FAN is extracted, insert it. In other cases, check each FAN and replace the faulty one(s). Refer

to its procedure in Nortel GSM BSC 3000/TCU 3000 Troubleshooting(411-9001-132).

2.21 Fault number: 2015Fault number:2015 : ATM path failure plan 0Type : CommunicationsAlarm

FAULT ANALYSIS


This notification indicates a problem on an ATM path (using AAL-1 orAAL-5 plane 0). The ATM path can be one of the following:


411-9001-131 18.07 12 March 2010


.


inter-TMU link OMU and TMU link inter ATM-SW link OMU and ATM-SW link TMU and ATM-SW link

A state changed notification appears simultaneously.

The managed objects (MOs) (MO) are: omu, tmu and cc.

This notification gives the following information: It specifies if the event is sent right after a restart or not. The only one cause of error for this release of BSC 3000 is loopBack

test.

It indicates the shelf/slot of the ATM-SW module from which the faultis sent.

It contains the serial number of the module, the PEC number andhardware release.


Generally, loss of capacity and, in certain cases (in particular when testsdone for the plane used by SS7 stack are failed due to CC1-7 failure),loss of service.

TROUBLESHOOTING

The maintenance action required is to check the ATM path.

The first level of maintenance is to verify if backplane and modules arecorrectly placed in the shelf (and screwed to the shelf).

The second level of maintenance (if the fault is always effective) iseffectively to change either the faulty module (i.e. OMU, TMU or ATM-SWmodule) or if the problem goes on, the ATM-SW module that has emittedthe alarm.

Fault could occur in two cases : fault is local : Suspect in fault finding a faulty TMU fault is global, applying to one or all modules from TMU : Replace

CC1-7 faulty board


411-9001-131 18.07 12 March 2010


.


2.22 Fault number: 2017Fault number:2017 : ATM path failure plan 1Type : CommunicationsAlarm

FAULT ANALYSIS


This notification indicates a problem on an ATM path (using AAL-1 orAAL-5 plane 1). The ATM path can be one of the following: inter-TMU link OMU and TMU link inter ATM-SW link OMU and ATM-SW link TMU and ATM-SW link

A state changed notification appears simultaneously.

The managed objects (MOs) (MO) are: omu, tmu and cc.

This notification gives the following information: It specifies if the event is sent right after a restart or not. The only one cause of error for this release of BSC 3000 is loopBack

test.

It indicates the shelf/slot of the ATM-SW module from which the faultis sent.

It contains the serial number of the module, the PEC number andhardware release.


Generally, loss of capacity and, in certain cases (in particular when testsdone for the plane used by SS7 stack are failed due to CC1-8 failure),loss of service.

TROUBLESHOOTING

The maintenance action required is to check the ATM path.

The first level of maintenance is to verify if backplane and modules arecorrectly placed in the shelf (and screwed to the shelf).


411-9001-131 18.07 12 March 2010


.


The second level of maintenance (if the fault is always effective) iseffectively to change either the faulty module (that is, OMU, TMU orATM-SW module) or if the problem goes on, the ATM-SW module that hasemitted the alarm.

Fault could occur in two cases : fault is local : Suspect in fault finding the faulty TMU fault is global, applying to one or all modules from TMU : Replace

CC1-8 faulty board

2.23 Fault number: 2018Fault number:2018 : Loss of Lb interface (or no establishment) with SMLCType : CommunicationsAlarm

FAULT ANALYSIS


This fault is sent to indicate that SCCP configuration has failed.

This fault is effectively sent if SCCP layer cannot be connected or is lostbetween the BSC 3000 and the SMLC.

This fault can also be raised if all SS7 links are lost to an operating BSC.

The Managed Object is: signallingLinkSet


BSC defense

None.


SS7 service is not present (loss of service).

TROUBLESHOOTING Check the SCCP configuration on the BSC side and on the SMLC side. This fault could also occur if all of the SS7 links are out of service.

In this case, a 2018 potential fault is transmitted. Depending on the


411-9001-131 18.07 12 March 2010


.


configuration, check all the PCMA_Lb links or the PCM_Lb links (lookfor alarms on PCM links).

2.24 Fault number: 2019 (BSC 3000)Fault number:2019 : Synchronizing PCM indicationType : Communications alarm

FAULT ANALYSIS


Perceived severity: CRITICAL/CLEARED/WARNING

Reminder: An Interface Node can be synchronized on: a PCM port (among the six synchronizer PCM ports of LSA 0) a local clock (internal to the node)

The Interface Node selects the best synchronization source among thepossible PCM synchronizer ports (6 first ports of LSA 0) and optical ports.The Interface Node will preferably synchronize on optical ports. If it detectsa clock instability, it selects one of the PCM synchronizer port among thesix possible PCM ports. If none of the optical ports and of the six possiblesynchronizer ports are suitable, the Interface Node selects the local clockas a synchronization source (the local clock is provided by the active CEMmodule).

For the BSC 3000 cabinet, the Managed Object is: interfaceNode and"hardware transcoder 3G"

This notification (ANO_SYNCHRONIZING_PCM_INDICATION) canappear in two different cases: after the restart of the relevant equipment (no maintenance action is

required) on a change of the PCM synchronization source (possible sources are

all the possible synchronizer PCM ports and the local clock)

This notification gives the following information on the event and itscauses:

due to restart or not synchronization type (on a PCM port, on the local clock)


411-9001-131 18.07 12 March 2010


.

2.24 Fault number: 2019 (BSC 3000) 71

synchronizer PCM port number (if any) hsaRc number: the "HsaRC number" is given if the fault number 2019

was emitted by the interfaceNode. Otherwise, "0XFFFF" is indicated ifa hsaRC is not used as the clock reference.

The perceived severity depends on the previous clock and newly selectedclock: Severity is set to CRITICAL when the local clock is selected. In this

case, the IN node or TCU node switch to DEGRADED status. Severity is set to CLEARED when the system was synchronized to its

local clock and selects an optical or PCM clock. Severity is set to WARNING when the clock is selected from another

PCM.

ATTENTIONA CLEARED notification can occur before a new clock notification on the firstclock change after an OMU restart.


None (due to a smooth clock-switching device).

TROUBLESHOOTING


Perform the troubleshooting associated with the 2009 fault number forthe CTU 4 - LSA 0 module. Refer to procedure 2.15 Fault number: 2009(BSC 3000) (page 51)


411-9001-131 18.07 12 March 2010


.


2.25 Fault number: 2020Fault number:2020 : Supervision failureType : equipmentAlarm

FAULT ANALYSIS



411-9001-131 18.07 12 March 2010


.


A "Supervision failure" notification is sent whenever the operator pressesthe push button located on the OMU or MMS front panel. This button ispressed to prepare the OMU or MMS module for an extraction from itsshelf.

If the faulty module is not removed, the OMU is reinserted in the hardwareconfiguration after the maintenance period (about 15 minutes). The redLED stops to blink.

The type, position and slot number of the module are given in thenotification.

For the BSC 3000 cabinet, the Managed Object is controlNode,"hardwaretranscoder 3G".

The modules involved in the Control Node can be one of the following: OMU module shared MMS module private MMS module


There is a restart of the faulty module.

2.26 Fault number: 2021Fault number:2021 : IN Access failureType : EquipmentAlarm

FAULT ANALYSIS


This notification appears when the link between the Interface Node and theControl Node is lost.

The Managed Object is: interfaceNode.

There are two fiber-optic links between the Control Node and the InterfaceNode. Each link is made of an ATM-SW module, a Tx fiber cable, a Rxfiber cable, and an ATM-RM module. When both links are faulty (forexample, if the ATM-SW faulty on one link and the ATM-RM faulty on theother link, the service is lost and the "IN Access Failure" notification isdisplayed at the OMC-R.


411-9001-131 18.07 12 March 2010


.



CAUTIONService interruptionThe service is lost.

TROUBLESHOOTING



411-9001-131 18.07 12 March 2010


.


Service_interruptionPerform the troubleshooting associated with this fault. Refer toprocedure in 2.14 Fault number: 2008 (BSC 3000) (page 44)

2.27 Fault number: 2022Fault number:2022 : Clock failureType : Equipment Alarm

FAULT ANALYSIS


Identifier/Number set by the local Fault Management

Causes: incorrect time (for example, hour = 25) (0) failure to read time (1) time value not advancing (2)


411-9001-131 18.07 12 March 2010


.


Post mortem: Specify if the event is sent after a restart or not. The postmortem values are fmNormal (0) fmEventSentAfterRestart (1)

Alarm on the clock chip of the active OMU

The Managed Object is: omu.

TROUBLESHOOTING

Replace the faulty chip.

This alarm can only be purged by an ANO_PURGE_PREVIOUS_EVENTSemitted after an OMU swact.

2.28 Fault number: 2023Fault number:2023 : Signalling faultType : communicationsAlarm

FAULT ANALYSIS


Unused LAPD or SS7 channels of each TMU module are periodicallytested. The "Signalling fault" notification appears when the result of thistest is wrong.


The PcmId, position, and slot number of the faulty TMU module are givenin the notification.

The PmcId (Identifier of the PMC board on the TMU) can be 0 or 1 for aTMU1 and will always be 0 for a TMU2.


ATTENTIONThere is a potential service degradation if less than "n" boards are available (n +p configuration). Otherwise, there is no impact on service.

TROUBLESHOOTING

On-site maintenance


411-9001-131 18.07 12 March 2010


.

2.29 Fault number: 2024 (BSC 3000) 77

Replace the TMU module mentioned in the notification. Refer to the replacement procedure given in Nortel GSM BSC

3000/TCU 3000 Troubleshooting (411-9001-132). The alarm is automatically cleared.

2.29 Fault number: 2024 (BSC 3000)Fault number:2024 : SPM Download failureType : EquipmentAlarm

FAULT ANALYSIS



Reminder: Control Node, Interface Node and Transcoder Node softwarecan be upgraded using the OMC-R. The files are downloaded from theOMC-R to the shared MMS module. Then the Control Node is upgraded.Then the Interface Node. Then the Transcoder Nodes.

"SPM Download failure" means "SPectruM Download failure". It appearson Interface Node downloading operation failure. This notification gives: the type, position, and slot number of the module the name of the file the downloading has failed

For the BSC 3000 cabinet, the Managed Object (MO) is: interfaceNode,and "hardware transcoder 3G"


None. The service is not lost.

ATTENTIONThe module which is pointed out in the notification is not upgraded.

TROUBLESHOOTING



411-9001-131 18.07 12 March 2010


.



411-9001-131 18.07 12 March 2010


.

2.29 Fault number: 2024 (BSC 3000) 79


411-9001-131 18.07 12 March 2010


.


2.30 Fault number: 2026Fault number:2026 : Observation FTAM: Disk failType : QualityOfService

FAULT ANALYSIS


This notification appears when it is impossible to store a generalpermanent observation message on the disk of the BSC 3000.



None. The traffic is not lost.

This alarm will appear on each failed storage attempt of the message.

TROUBLESHOOTING


411-9001-131 18.07 12 March 2010


.

2.31 Fault number: 2027 (BSC 3000) 81


2.31 Fault number: 2027 (BSC 3000)Fault number:2027 : Restart CauseType : qualityOfServiceAlarm

FAULT ANALYSIS

ATTENTIONThis fault number also applies to TCU 3000. See 3.11 Fault number: 2027(TCU 3000) (page 155).

Hardware slot position is not significant if the notification is related to acode. Otherwise, contains the shelf number (0 or 1) and the slot number (1to 15) of the module the notification is related to.


Indication of the cause of a node or module restart due to an OMC/TMLrequest or an internal malfunction.

List of cause values:


411-9001-131 18.07 12 March 2010


.


Power on (0) Reset command from OMC (1) Reset command from TML (2) RAZ build (3) Upgrade (4) Swact when passive supervision module not yet synchronized (5) Build error (6) Simultaneous restarting of the supervision modules (7) Module reset at end of maintenance period (8) Critical processing error alarm signal received (9) Processing error alarm threshold exceeded (10) Module supervision signal lost (11) Module application signal lost (12) Simultaneous lost of CC1 modules (13) Active supervision module flashed (14) Module flashed (15) Bad module restarting (16) OMC-Link failure (17) OMU swact due to loss of active one (18) Passive OMU reset after IP@ update (19) New bscArchitecture (electrical/optical) is taken into account (20) NS (Not Significant) (255)

The type, position, and slot number of the module are given in thenotification.

For the BSC 3000 cabinet, the managed objects (MOs) are: atmRm, cem,cem3, cc, controlNode, iem, interfaceNode, iom, lsaRc, mmu, omu, tmu,sw8kRm.

For the BSC 3000 cabinet, the managed objects (MOs) are: atmRm, cem,cem3, cc, controlNode, iem, igm, interfaceNode, iom, ipgRc, lsaRc, mmu,omu, tmu, sw8kRm.


No service interruption.


411-9001-131 18.07 12 March 2010


.

2.32 Fault number: 2028 (BSC 3000) 83

TROUBLESHOOTING


2.32 Fault number: 2028 (BSC 3000)Fault number:2028 : Restart contextType : qualityOfServiceAlarm

FAULT ANALYSIS

ATTENTIONThis fault number also applies to TCU 3000. See 3.12 Fault number: 2028(TCU 3000) (page 156).


This notification appears each time that a board starts correctly after aninsertion, a reset or a restart.

For the BSC 3000 cabinet, the managed objects (MOs) are: controlNode,interfaceNode, and transcoder, omu, "mmu", tmu, cc cem "srt" "iem, atm".

The board type (see below), position, and slot number of the module aregiven in the notification. Board type:

SBC (0) for TMU1 or TMU2 PMC (1) for TMU1 TM (2) for TMU1 (255) not significant



No service interruption.

TROUBLESHOOTING



411-9001-131 18.07 12 March 2010


.


2.33 Fault number: 2030 (BSC 3000)Fault number:2030 : SPM message errorType : CommunicationsAlarm

FAULT ANALYSIS

ATTENTIONThis fault number also applies to TCU 3000. See 3.13 Fault number: 2030(TCU 300

411-9001-131(BSC TCU Fault Clearing)

Documents

Transcript of 411-9001-131(BSC TCU Fault Clearing)