04 mn1782eu11mn 0001 bsc maintenance

8/12/2019 04 Mn1782eu11mn 0001 Bsc Maintenance

1/66

BSC maintenance Siemens

MN1782EU11MN_0001 2002 Siemens AG

1

Contents

1 BSC maintenance 3

1.1 Maintenance concept 4

1.2 Identification of suspected modules 6

1.3 Replacing modules 8

1.4 Cold plug 10

2 LEDs 13

2.1 BSC Fuse and Alarm Panel (FAP) 14

2.2 Global alarm section of the FAP and lamp panel 14

2.3 System alarm section 16

2.4 Equipment alarm and communication section 182.5 S/W RUN section (old and new) 18

2.6 Minor alarm section (SAI-PAI and ENV) 19

3 BSC maintenance entity graph 21

4 Switching network failure 27

4.1 Alarm message 28

4.2 Fault identification 30

4.3 Perform test on NTW 33

4.4 Module replacement 36

4.5 Verify that the alarm has been removed 385 Maintenance objects 39

6 BSC hardware 41

6.1 BSC high capacity step 1 42

6.2 BSC high capacity step 2 43

7 Exercises 45

8 Solutions 53

BSC maintenance


2/66

Siemens BSC maintenance

MN1782EU11MN_0001

2002 Siemens AG

2


3/66



3

1 BSC maintenance


4/66


MN1782EU11MN_0001

2002 Siemens AG

4

1.1 Maintenance concept

The modular design of the BSC allows you to clear a large percentage of faults in thesystem by replacing a defective module. In the BSC the modules divide into thegroup of hot plugged modules and the group of cold plugged modules.

In addition for some modules special care is required. This applies to the MPCC andTDPC modules that have cabling on the front side of the module.

In case of faults do not result from defective modules, but from interface problems ingeneral (for example interrupted PCM lines) special trouble shooting procedures forinterfaces are provided.

The detailed information for the fault clearance procedures can be found in theMaintenance Manual MMN:BSC.

TIPThe BSC is the central alarm collection point for all connected Network elements andfor all logical objects. Many failures that are visible in the message browser in case ofconnection to BSC are not directly relayed to the Hardware of the BSC itself.


5/66



5

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Replacing Modules

Finding Faults

Checking Connections

Customer Documentation

LMT

Fig. 1 Fault clearance principle


6/66


MN1782EU11MN_0001

2002 Siemens AG

6

1.2 Identification of suspected modules

In the Operation and Maintenance Center the Network is centrally supervised. Inmany cases Information from OMC is valuable for finding the suspected module.

Characteristics of faulty modules

In this course the local maintenance actions are discussed. Information about faultymodules may be obtained from LMT alone. Keywords for identifying defectivemodules are

operational state:Disabled,

availability status:Failed.

Locating the fault

Failure message from RC

Interpretation of the LEDs (details later)

Connect LMT, open the Graphical user interface: Faulty units are marked withred/orange/yellow colors

Connect LMT, execute GET commands

Verify the fault

Lock the module

Perform a test on the module

Check if the Test outcome is failed


7/66



7

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

FAILURE EVENT REPORT:

NAME = NTW:1

Event Type = Equipment Failure Event

Event Time = 01/Sep/2005 11:12:26

Probable Cause = Equipment Failure

Specific Problems = 342 - SNAP Permanent Failure

Severity = Major

Trend Indication = More Severe

Notification Identifier = 8602

Correlated Notification

Identifier = 8597

Related MO = BSCE:0

Proposed Repair Actions = 4 - Test the addressed card(s)

Originator = 4207Additional Words =

Octets 01 to 16: H'0056 H'0001 H'0006 H'106a H'020e H'0000 H'0400

H'ffff

Octets 17 to 30: H'ffff H'ffff H'ffff H'ffff H'ffff H'ffff H'00ff

Software Vers ion = 02-08-01-01-00-64_05-07-06

END OF OUTPUT FOR JOB 720

Failure ReportLMT evolution

LED status Fuse and

Alarm panel

Test Result: outcome = failed

GLOBALALARM

SYSTEM ALARM EQUIPMENT

ALARM

S/WRUN

CRT MPCCTDPC PPXX

QOS COM EQP

NEW

OLD

MJR

LINE NTWCLOCK

MINOR

ALARM

SAIPAI

COMMUNICATION

O MC HWI DIS K B TS T RA U ENVMIN

Fig. 2 Faulty module


8/66


MN1782EU11MN_0001

2002 Siemens AG

8

1.3 Replacing modules

WARNINGMany system modules are equipped with electrostatically sensitivecomponents (marked by an ESD symbol). Therefore, ESD precautions must betaken when removing and inserting modules. During module replacement,personnel must wear a conductive wrist strap to discharge electrostaticcharging. Before modules, lines or components are touched, this wrist strapmust be connected to the ground potential of the rack by means of a flexible

lead integrating a 1 M resistor.

All information required for this purpose is found in the Maintenance ManualMMN:BSC.

Hardware replacement in the BSC requires the (locking and) switching off for therespective power supply module before the module itself is replaced (coldplug-in).The only modules, which can be hot plugged, i.e. while power is still on, are

QTLP, STLP

PPXX


9/66



9

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Take ESD PrecautionsInterpret LED status

Use the Customer Documentation:

Consult the Maintenace Manual!

Many modules are cold plugged!

MPCC

SNAP

CPEX

IXLT

TDPC

MEMT

UBEX

PLLH

Fig. 3 Module Replacement


10/66


MN1782EU11MN_0001

2002 Siemens AG

10

1.4 Cold plug

In case of modules are cold plug, the following steps have to be executed. If thefaulty module is identified:

Connect LMT

LOCK corresponding PWRS module of the module that has to be replaced

Pull down the "Request Power off" lever

pull the faulty module

Insert the new module

Pull up the "Request Power off" lever Unlock PWRS module

Perform Test on the replaced module


11/66



11

Cold plug modules

Power Supply modulePWRS:0

Power Supply modulePWRS:1

BSC base rack area

Fig. 4 Cold plug modules

Request Power off

Power Off anyway

PWRS module

Fig. 5 Power Supply module


12/66


MN1782EU11MN_0001

2002 Siemens AG

12


13/66



13

2 LEDs

Lamp Panel

BSC Fuse and

Alarm Panel

Fig. 6 BSC high capacity rack with fuse and alarm panel and lamp panel


14/66


MN1782EU11MN_0001

2002 Siemens AG

14

2.1 BSC Fuse and Alarm Panel (FAP)

The LED located on the fuse and alarm panel signal (from left to right):

Global Alarms

System Alarms

Equipment Alarms and Communication

S/W Run

Minor Alarms.

LED with three different colors are used: Green LED for equipment and communication alarms.

Amber LED for minor severity alarms.

Red LED for major or critical alarms.

2.2 Global alarm section of the FAP and lamp panel

Three summary LED display whether a critical, major or minor alarm is present (all

BSC alarms OR-ed). There is one LED each for

CRITICAL alarms (red),

MAJOR alarms (red),

MINOR alarms (amber in Global Alarm Section, red in Lamp Panel).

The alarms from the global alarm section are mirrored on the lamp panel. With theBSC door closed, the LED on the lamp panel are still visible.

FUSECRITICAL

ALARM

MAJOR

ALARM

MINOR

ALARM

Fig. 7 Lamp panel


15/66



15

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

GLOBAL

ALARM


ALARM

S/W

RUN

CRT MPCC TDPC PPXX

QOS COM EQP

NEW

OLD

MJR

LINE NTW CLOCK

MINOR

ALARM

SAI

PAICOMMUNICATION

OMC HWI DISK BTS TRAU ENVMIN

Fig. 8 BSC fuse and alarm panel, part with alarm LED


16/66


MN1782EU11MN_0001

2002 Siemens AG

16

2.3 System alarm section

In the system alarm section the following alarm types are displayed:

Quality of Service alarms arerelated to service downgrading. By default, MINOR,MAJOR or CRITICAL alarms are reported for the attention thresholds 30%, 60% or90%.

Communication .alarms reports problems in communication exchange between thesubsystem elements

Equipmentalarmsare related to BSC hardware failures. Both generating functionand alarm severity are reported. The BSC automatically switches over to theredundant modules if hardware failures occur.

The LED indicate the severity of the alarm reported:

a flashing red LED indicates a CRITICAL alarm,

a permanently lit red LED indicates a MAJOR alarm,

an amber LED indicates minor alarms.


17/66



17

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

GLOBAL

ALARM


ALARM

S/W

RUN

CRT MPCC TDPC PPXX

QOS COM EQP

NEW

OLD

MJR

LINE NTW CLOCK

MINOR

ALARM

SAI

PAICOMMUNICATION


Fig. 9 BSC fuse and alarm panel, system alarm section


18/66


MN1782EU11MN_0001

2002 Siemens AG

18

2.4 Equipment alarm and communication section

The equipment alarm and communication section features green LED only:

green LED permanently lit indicates good working condition,

green LED flashing signals alarm.

The following table gives the correspondence between the LED designation and therelated modules/objects.

LED - Equipment Alarm/Communication Alarm

Corresponding modules/objects

MPCC MPCC, PWRD

TDPC TDPC, MEMT

PPXX PPCC, PPCU, PPLD, PPXU, PPXL, PPXP, PPXT

LINE PCMA, PCMB, PCMS, PCMG

NTW SN16, SNAP, UBEX, PLLH

CLOCK PLLH, SYNC

OMC OMAL

HWI IXLT, LICD, LICDS, EPWR

DISK MPCC hard diskBTS BTS

TRAU TRAU

LED - hardware correspondence

2.5 S/W RUN section (old and new)

S/W RUN LED are normally switched off. The green S/W RUN LED lights up onlyduring the change version procedure. When a LED lights up, it indicates which SWversion is currently running. The LED switches off when the operator enters the endof change version command; see OMN:BSC, "BSS SW Version Change".


19/66



19

2.6 Minor alarm section (SAI-PAI and ENV)

This section features two amber LED. The SAI-PAI LED reports alarms onPCMS/PCMB lines (Service Alarm Indication - PCM Alarm Indication). The ENV LEDindicates an environmental alarm such as smoke, intrusion, fire, or temperature.

On and not flashing means MINOR alarm.

Slow flashing means MAJOR alarm.

Fast flashing means CRITICAL alarm.

GLOBAL

ALARM


ALARM

CRT MPCC TDPC PPXX

QOS COM EQP

MJR

LINE NTW CLOCK

COMMUNICATION

OMC HWI DISK BTS TRAUMIN

S/W

RUN

NEW

OLD

MINOR

ALARM

SAI

PAI

ENV

Fig. 10 BSC fuse and alarm panel, part with alarm LED


20/66


MN1782EU11MN_0001

2002 Siemens AG

20


21/66



21

3 BSC maintenance entity graph


22/66


MN1782EU11MN_0001

2002 Siemens AG

22

The hierarchy of the BSC logical and physical objects and their mutual dependency isshown in the Maintenance Entity Graph. In the picture you see the hardware (green)and the logical objects (red, blue, yellow).

Sub-ordinate objects (on branches) are dependent from super-ordinate objects (onthe trunk). For example, the RAMT of the TDPC telephony processor depends on theMEMT module on which it is installed and the PWRD object representing the powersupply.

The effect of a failure in the system is affected by the dependency shown in the MEGand the redundancy mechanism of the object.

TIPThe auto diagnostic procedures of the BSC system are able to identify the defectivemodule and the possible malfunctioning objects. The same procedures can place theobjects into the operational DISABLE state. As a consequence of this action, thesubordinate objects are also placed in the DISABLE state. This allows for theillumination of the appropriate LED on the alarm panel. The operator must payattention to this and look at the MEG in order to identify the source of the error.


23/66



23

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MPCC MEMT UBEX CPEX IXLT NTW

TDPC LICD LICDS

PPXL PPXU

PCMS PCMB PCMG

LPDLS PCU

FRL

NVSC

BTSM

BTS

TRX

CHAN

PWRD

SS7L

TRAU

PCMA

TSLA

NUC

SYNC

LPDLRLPDLM

PTPPKF

Fig. 11 BSC MEG overview


24/66


MN1782EU11MN_0001

2002 Siemens AG

24

Power Supply Impact

All modules in the lowest base shelf and PLLH are subordinate to the PWRS with the

same number (0 or 1). If the Power supply PWRS:0 is switched off, the modulesMPCC:0, TDPC:0, MEMT:0 . are changing their OST to disabled because ofdependency.

The other modules in the BSC (STLP, STLPS, PPXX) have double power supply orpower supply from the backplane. In case of one PWRS module is switched off,these modules are not affected.

Redundancy Impact

An example to show the impact of redundancy is TDPC failure. Consider the case ofTDPC:0 module is failed and TDPC:1 is providing service. The PPXX modules aresubordinate to TDPC modules. But in this case of one TDPC module is failed, thesubordinate objects stay enabled and can provide service. TDPC is protected by 1+1hot standby redundancy.

Another example is the 2 PPXL boards working in balanced load sharing mode. Thismeans if one module is failed, the other board is taking over the complete traffic.

Only in the case that both boards fail, all subordinate objects change their OST todisabled because of dependency.


25/66



25

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MPCC:0MEMT:0

PPXU

PWRD:0

UBEX:0CPEX:0 IXLT:0 NTW:0

TDPC:0

PPXL

PCMB

LICD:0...2 LICDS:0

PCMS PCMG

Double PowerSupply

Single

Power

Supply

TDPC:1

Fig. 12 MEG hardware BSC base rack (simplified)


26/66


MN1782EU11MN_0001

2002 Siemens AG

26


27/66



27

4 Switching network failure

GLOBAL

ALARM


ALARM

S/W

RUN

CRT MPCC TDPC PPXX

QOS COM EQP

NEW

OLD

MJR

LINE NTW CLOCK

MINOR

ALARM

SAIPAICOMMUNICATION


Fig. 13 Alarm panel displaying a minor equipment alarm


28/66


MN1782EU11MN_0001

2002 Siemens AG

28

4.1 Alarm message

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


NAME = NTW:1


Event Time = 01/Sep/2005 11:12:26

Probable Cause = Equipment Failure

Specific Problems = 342 - SNAP Permanent Failure

Severity = Major




Identifier = 8597

Related MO = BSCE:0


Originator = 4207

Additional Words =

Octets 01 to 16: H'0056 H'0001 H'0006 H'106a H'020e H'0000H'0400 H'ffff

Octets 17 to 30: H'ffff H'ffff H'ffff H'ffff H'ffff H'ffffH'00ff

Software Version = 02-08-01-01-00-64_05-07-06



29/66



29

S

T

L

P

8

18

S

T

L

P

7

29

S

T

L

P

6

27 42 48 50 54 58 82

ST

L

P

5

18

ST

L

P

4

29

ST

L

P

3

27

ST

L

P

2

31

ST

L

P

S

1

35

PP

X

U

5

42

PP

X

U

4

48

PP

X

U

3

50

PP

X

U

2

54

PP

X

U

1

58

PP

X

U

0

82

S

T

L

P

1

25

S

T

L

P

0

29

S

T

L

P

S

0

39

P

P

X

L

1

38

P

P

X

L

0

48 59 58

P

L

L

H

1

69

P

W

R

S

0

9

P

W

R

S

1

71

C

PE

X

0

2

C

P

E

X

1

78

P

L

L

H

0

18

I

XL

T

0

18

U

BE

X

0

17

S

NA

P

0

20

T

DP

C

0

23

M

EM

T

0

30

M

E2

M

0

34

M

PC

C

0

36

M

PC

C

1

44

U

BE

X

1

68

I

XL

T

1

71

M

E2

M

1

48

M

EM

T

1

54

T

DP

C

1

58

Fig. 14 BSC with faulty NTW-1


30/66


MN1782EU11MN_0001

2002 Siemens AG

30

4.2 Fault identification

Finding the faulty module

Open Graphical view and look for faulty objects, here you see that the NTW objectis disabled

Set up the Command " Get active Alarms" (BSCE), here you get in the messagebrowser the failure report of NTW

You know now the suspected object, execute a "GET NTW status", in the answeryou will find the OST = disabled

SUMMARYNow you know the something is wrong with the object NTW. This object isrepresenting the modules SNAP, UBEX and PLLH. So one of these cards can be thesource of the fault.

TIPUse the maintenance manual and follow the procedure steps!

1. Open the Maintenance Manual and search for the fault number

a link to the corresponding procedure is given

2. Open the NTW procedure and follow all the steps

The result of the test is including the information which module is the source of thefault. In this example it should be SNAP.


31/66



31

Fig. 15 GET ACTIVE ALARMS BSCE

Fig. 16 GET NTW STAT


32/66


MN1782EU11MN_0001

2002 Siemens AG

32

Response message from commandGet NTW STAT:

JOB: 774

PC Time&Date: 11:18:54 09/01/2005

NE Time&Date: 11:16:15 09/01/2005

USER NAME: SAG

COMMAND: Get NTW STAT:NAME=NTW:1;

SW RELEASE: 02-08-01-01-00-64_05-07-06

COMMAND RESULT: Operation successful

stateValue =

AdministrativeState = UNLOCKED

OperationalState = DISABLED

alarmStatus = MAJOR

proceduralStatus = NULLavailabilityStatus = failed

controlStatus = NULL

unknownStatus = FALSE

standbyStatus = NOTAPPLICABLE



33/66



33

4.3 Perform test on NTW

To find out which card has to be replaced a test is performed on the NTW:1 object.

Fig. 17 LOCK NTW

Fig. 18 Perform test NTW


34/66


MN1782EU11MN_0001

2002 Siemens AG

34

Response of command PERFTEST NTW(before replacing module) gives hintswhich module to replace:

Result TEST:

name = BSCETEST:1

testOutcome = FAILED

MOT = NTW:1

testTermination = Normal

executedPhases =

PhaseId = ACCESSIBILITY

PhaseId = UBEX_FORCE_ALARM

PhaseId = PLLH_FORCE_ALARM

PhaseId = PLLH_FW_SELF

PhaseId = SN_FORCE_ALARM

PhaseId = END

failedPhases =

phaseId = ACCESSIBILITY

additionalWords =

addWords = H`106F

addWords = H`0056

addWords = H`0601

addWords = H`0000

addWords = H`0000

addWords = H`FFFF

addWords = H`FFFFaddWords = H`FFFF

phaseId = SN_FORCE_ALARM

additionalWords =

addWords = H`106F

addWords = H`0056

addWords = H`0601

addWords = H`FFFF

addWords = H`FFFF


35/66



35

addWords = H`FFFF

addWords = H`FFFF

addWords = H`FFFFskippedPhases =

phaseId = SN_SPEECH_RAM_ADDRESS_PARITY_TEST

phaseId = SN_SPEECH_RAM_DATA_PARITY_TEST

phaseId = SN_CONTROL_RAM_DATA_PARITY_TEST

phaseId = SN_CHANNEL_LOOP_TEST

proposedRepairAction =

action = REPLACE_SN

action = REPLACE_UBEX

action = REPLACE_PLLH



36/66


MN1782EU11MN_0001

2002 Siemens AG

36

4.4 Module replacement

WARNINGThis module requires cold plug

Before replacing one of the NTW modules the corresponding power supply PRWDhas to be LOCKED and switched off.

Fig. 19 Lock PWRD


37/66



37

WARNINGTake ESD precautions when extracting the SNAP card!

Pull the faulty SNAP module

Compare the jumper settings (new module - faulty module)

Insert the new SNAP module

After the replacement of the (faulty) module the PRWD has to be unlocked again.

Perform a test on the NTW to verify that the modules are ok

Unlock NTW object

Fig. 20 Unlock NTW


38/66


MN1782EU11MN_0001

2002 Siemens AG

38

4.5 Verify that the alarm has been removed

Open GLT

Set up the Command " Get active Alarms" (BSCE),

Execute a "GET NTW status"

Fig. 21 GET ACTIVE ALARMS BSCE


39/66



39

5 Maintenance objects

The maintenance objects on BSC/120 for diagnostic tests are shown in the table.Specially in the case of NTW there is one object in the LMT input handler that isrepresenting three different modules.

MaintenanceObject

Description

MPCC Microprocessor Control Circuit

TDPC Telephony and Distribution Circuit

MEMT Memory between MPCC and TDPC, contains RAMT (memory ofTDPC) and DPMT (memory of data exchange to/from MPCC)

LICD Line Interface Card

LICDS Line Interface Card Spare

NTW Network (composed of SN16/SNAP, PLLH, UBEX)

PPXL Peripheral Processor for CCSS7 and LAPD

PPXU Peripheral Processor for GPRS/EGPRS Protocols

IXLT Interface X.25 and local maintenance terminal

CPEX Control Panel and External Alarm card

PWRS Power Supply

PPCC Peripheral Processor for CCSS7

PPLD Peripheral Processor for LAPD

PPCU Peripheral Processor for GPRS Protocols

DK40 Hard disk and Alarm panel supervision


40/66


MN1782EU11MN_0001

2002 Siemens AG

40


41/66



41

6 BSC hardware


42/66


MN1782EU11MN_0001

2002 Siemens AG

42

6.1 BSC high capacity step 1

Lamp Panel

Q

T

L

P

8

Q

T

L

P

7

Q

T

L

P

6

P

P

X

X

7

P

P

X

X

6

P

P

X

X

5

Q

T

L

P

5

Q

T

L

P

4

Q

T

L

P

3

P

P

X

X

4

P

P

X

X

3

P

P

X

X

2

Q

T

L

P

2

Q

T

L

P

S

1

P

W

R

S

1

P

W

R

S

0

P

L

L

H

0

Q

T

L

P

1

P

P

X

X

0

P

L

L

H

1

Q

T

L

P

0

P

W

R

S

1

P

W

R

S

0

Q

T

L

P

S

0

P

P

X

X

1

D

K

40

0

I

X

L

T

0

U

B

E

X

0

S

N

A

P

0

T

D

P

C

0

M

E

M

T

0

M

P

C

C

0

M

P

C

C

1

M

E

M

T

1

T

D

P

C

1

S

N

A

P

1

U

B

E

X

1

I

X

L

T

1

Expansion

Fuse and Alarm

Panel

Base

Fig. 22 BSC Rack Layout (High Capacity 1st step, BR6.0 Hardware)


43/66



43

6.2 BSC high capacity step 2

E

S

A

M

0

I

X

L

T

0

U

B

E

X

0

S

N

A

P

0

T

D

P

C

0

M

E

M

T

0

M

P

C

C

0

E

S

A

M

1

I

X

L

T

1

U

B

E

X

1

S

N

A

P

1

T

D

P

C

1

M

E

M

T

1

M

P

C

C

1

P

W

R

S

1

P

L

L

H

1

P

W

R

S

0

P

L

L

H

0

S

T

L

P

1

S

T

L

P

0

S

T

L

P

S

0

S

T

L

P

2

P

P

X

X

1

P

P

X

X

0

S

T

L

P

5

S

T

L

P

4

S

T

L

P

3

S

T

L

P

S

1

S

T

L

P

9

S

T

L

P

8

S

T

L

P

7

S

T

L

P

6

P

P

X

X

7

P

P

X

X

6

P

P

X

X

5

P

P

X

X

4

P

P

X

X

3

P

P

X

X

2

P

P

X

X

13

P

P

X

X

12

P

P

X

X

11

P

P

X

X

10

P

P

X

X

9

P

P

X

X

8

Expansion Subrack

Base Subrack

Fuseand Alarm Panel

Fig. 23 BSC Rack (BSC High Capacity 2nd Step)


44/66


MN1782EU11MN_0001

2002 Siemens AG

44


45/66



45

7 Exercises


46/66


MN1782EU11MN_0001

2002 Siemens AG

46


47/66



47

Exercise 1

Title: LICD failuresObjectives: Understand the switching concept of LICD and LICDS boards

Pre-requisite: none

Task

1. Use a command for getting subordinate objects to check which LICD boards arehandling PCM lines.

2. Get the state and status attributes to check which LICD boards are providing

service and which are standby.3. Provoke a hardware failure by removing the LICDS-0 board. Can this board be

hot-plugged, i.e. pulled out while power is on?

4. Check again which LICD boards are providing service and which are standby.

5. Start fault clearance for this fault. Check the jumper settings of the removedLICDS-0 board before "module replacement.

6. After fault clearance, provoke another hardware failure by removing one of theLICD boards providing service.

7. Interpret the alarm status.

8. Use again the command for getting subordinate objects to look for thedependencies between LICD boards and PCM links.

9. Get again the state and status attributes to look which LICD boards are providingservice and which are standby.

10. Create an additional hardware failure by removing a second LICD board.

11. Interpret the alarm status and interrogate again the dependencies between LICDboards and PCM links.

12. Perform fault clearance for the faults.

Query

Which LMT commands are relevant for fault clearance?

Explain the switching concept of LICD and LICDS boards!


48/66


MN1782EU11MN_0001

2002 Siemens AG

48


49/66



49

Exercise 2

Title: PPXX failuresObjectives: Understand the switching concept of PPXX boards

Pre-requisite: none

Task

1. Use a command for getting the subordinate objects to checkwhich PPXXboards are handling signaling links.

2. Get the state and status attributes

3. Provoke a hardware failure by removing a PPXX board. Can this board be hot-plugged?

4. Check again the PPXX boards . Which boards have overtaken the traffic of theextracted module?

5. Interrogate the dependencies between PPXL boards and signaling links.

6. Start the fault clearance for this fault. Check the jumper settings of the PPXXboard before "module replacement.

7. After fault clearance use again the command for getting subordinate objects tolook for the dependencies between PPXX boards and signaling links.

8. Get again the state and status attributes

Query

Which settings in the LMT command tree do you have to perform?

How does the switching concept of PPXX boards work?


50/66


MN1782EU11MN_0001

2002 Siemens AG

50


51/66



51

Exercise 3

Title: SN failureObjectives: Understand the maintenance concept

Pre-requisite: none

Task

1. Get the state and status attributes to find out which SNAP or SN16 module isproviding service and which one is standby.

2. Create a hardware failure by pulling out the standby SNAP or SN16 module. Canthis module be hot-plugged?

3. Interpret the failure event report.

4. Perform fault clearance according to the General Maintenance Procedure.

Query


How does the maintenance concept generally work?


52/66


MN1782EU11MN_0001

2002 Siemens AG

52


53/66



53

8 Solutions


54/66


MN1782EU11MN_0001

2002 Siemens AG

54


55/66



55

Solution 1

Title: LICD failuresObjectives: Understand the switching concept of LICD and LICDS boards

Pre-requisite: none

Task

1. Use a command for getting subordinate objects to check which LICD boards arehandling PCM lines.

Fig. 24 GET SUBO LICD


56/66


MN1782EU11MN_0001

2002 Siemens AG

56

Get the state and status attributes to check which LICD boards are providing serviceand which are standby.

The LICD modules are not supported with a standby status, because they areworking in a pool with only one fixed standby module LICDS. The standby LICDS hasusually, that means when no error persists, the standby status "HOT STANDBY".

2. Provoke a hardware failure by removing the LICDS-0 board. Can this board behot-plugged, i.e. pulled out while power is on?

The LICD and LICDS boards can be hot plugged, because they are powered by bothPWRS and therefore for maintenance purposes it must be possible to plug the boardwhile power is on.

3. Check again which LICD boards are providing service and which are standby.For appropriate commands see above.

The faulty LICDS has the operational state "DISABLED" and the availability status"FAILED". The state and status attributes of the other LICD boards are notinfluenced, they don't change.

4. Start fault clearance for this fault. Check the jumper settings of the removedLICDS-0 board before module replacement.

Refer to MMN:BSC, the General Maintenance Procedure.

For correct jumper settings refer to MMN:BSC ("Jumper settings DTLP/QTLP")

depending on the used LICD type.

After successful fault clearance the LICDS board get the standby status "HOTSTANDBY".

5. After fault clearance, provoke another hardware failure by removing one of theLICD boards supporting PCM lines.

Pull out one LICD board, which supports subordinate objects (PCM lines).

Interpret the alarm status.

You get a FAILURE EVENT REPORT for this board with SEVERITY: MINOR.

The appropriate LICDS board overtakes the service (PCM lines) of the faulty moduleand its standby status changes to "PROVIDING SERVICE".

6. Use again the command for getting subordinate objects to look for thedependencies between LICD/LICDS boards and PCM links.

For appropriate commands see above.

The LICDS board now carries the PCM lines of the faulty module.

7. Get again the state and status attributes to look which LICD boards are providing

service and which are standby.


57/66



57


The new standby status of the LICDS board is "PROVIDING SERVICE".

8. Create an additional hardware failure by removing a second LICD board.

Pull out another LICD board, which supports subordinate objects (PCM lines).

9. Interpret the alarm status and interrogate again the dependencies between LICDboards and PCM links.


This action in the previous step leads to a loss of PCM lines. Therefore you get acritical alarm, because one or more NEs are unavailable. The concerned PCM linesget the operational state "DISABLED" and the availability status "DEPENDENCY".This failure will be automatically cleared when the hardware fault is cleared.

10. Perform fault clearance for the faults.


After successful fault clearance of the first LICD board the supported PCM linesbecome available.

After successful fault clearance of the second LICD board the PCM lines supportedtemporarily by the appropriate LICDS board will be switched back to the original LICDboard and the LICDS board gets the standby status "HOT STANDBY".

Query


For commands and attribute settings see above.

How does the switching concept of LICD and LICDS boards work?

If one LICD board fails the associated LICDS board overtakes service of the failedboard. The standby status of the LICDS changes from "HOT STANDBY" to

"PROVIDING SERVICE".

A failure of a second LICD board in the same sub rack leads to loss of PCM linesonly if this board supports PCM lines.

Switching of LICD boards between the sub racks is not possible. Therefore every subrack contains its own LICDS board.

If all failures of LICD boards are cleared the original LICD boards overtakes theservice for the associated PCM lines and the LICDS board becomes "HOTSTANDBY".


58/66


MN1782EU11MN_0001

2002 Siemens AG

58


59/66



59

Solution 2

Title: PPXX failuresObjectives: Understand the switching concept of PPXX boards

Pre-requisite: none

Task

1. Use a command for getting the subordinate objects to checkwhich PPXXboards are handling signaling links.

Fig. 25 GETSUBO PPXX


60/66


MN1782EU11MN_0001

2002 Siemens AG

60

2. Get the state and status attributes to look which PPXX boards are providingservice and which is standby.

Fig. 26 GET PPXU/PPXL STAT


61/66



61

The PPXL modules in the base subrack are carrying LAPD links. They work in loadsharing mode, that means both cards have the standby status "PROVIDINGSERVICE

3. Provoke a hardware failure by removing a PPXL board. Can this board be hot-plugged?

The PPXL boards can be hot plugged, because they are powered by both PWRS andtherefore for maintenance purposes it must be possible to plug the board while poweris on.

4. Check again which PPXL boards carry the signaling links


The faulty PPXL board is out of service. The left PPXL is now overtaking thecomplete traffic

5. Interrogate the dependencies between PPXL boards and signaling links.

The LAPD links from the faulty PPXL board are overtaken by the left PPXL

6. Start the fault clearance for this fault. Check the jumper settings of the PPXLboard before module replacement.


For correct jumper settings refer to MMN:BSC ("Jumper settings PPXL").

7. After fault clearance use again the command for getting subordinate objects tolook for the dependencies between PPXL boards and signaling links.

8. Get again the state and status attributes


62/66


MN1782EU11MN_0001

2002 Siemens AG

62

Query



How does the switching concept of PPXL boards work?

Both PPXL boards are providing service. They are sharing the load, that means, bothboards carry similar amount of links. In case of one module fails, the other module isovertaking the complete traffic.


63/66



63

Solution 3

Title: SN failureObjectives: Understand the maintenance concept

Pre-requisite: none

Task

1. Get the state and status attributes to find out which SNAP or SN16 module isproviding service and which one is standby.

Fig. 27 GET NTW STAT


64/66


MN1782EU11MN_0001

2002 Siemens AG

64

2. Create a hardware failure by pulling out the standby SNAP or SN16 module. Canthis module be hot-plugged?

The NTW board must not be hot plugged, because each NTW copy is powered by itsown PWRS and therefore for maintenance purposes the board has to be pluggedwhile power is off.

3. Interpret the failure event report.

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

JOB: 62

PC Time&Date: 16:07:24 08/20/2003

NE Time&date: 6:35:22 01/01/1995

USER NAME: SAG

SW RELEASE: 02-07-01-01-00-65_03-07-10

COMMAND RESULT: OPERATION COMPLETED


NAME = NTW:1


Event Time = 01/Jan/1995 06:34:56

Probable Cause = Equipment FailureSpecific Problems = 155 - SNAP Permanent Failure

Severity = Major




Identifier = 532

Related MO = BSCE:0


Originator = 4207

Additional Words =

H'0056 H'0001 H'0004 H'106a H'01d9

H'0000 H'0400 H'ffff H'ffff H'00ff

H'ffff H'00ff H'00ff H'ffff H'00ff

Software Version = 02-07-01-01-00-65_03-07-10



65/66



65

The most important information is:

4. Probable Cause = Equipment failure Event

5. Event Type = Equipment Failure Event

6. Perform fault clearance according to the General Maintenance Procedure.


Query



How does the maintenance concept generally work?

1. If the faulty module is a central module lock PWRS (PWRD)

2. Lock the faulty module

3. Start the test on the faulty module4. Replace the faulty module

5. Start the test on the replaced module

6. Unlock the replaced module

7. Unlock PWRS (PWRD) if previously locked


66/66


04 mn1782eu11mn 0001 bsc maintenance

Documents