gsm-bss fault information feedback training

7/26/2019 GSM-BSS Fault Information Feedback Training

1/58

GSM

BSS


2/58

GSM-BSS Fault Report

Training

Technical Support Center, Mobile DivisionJan 200


3/58

Contents

Preface

Foreground BSC Fault Report

Background OMCR Fault Report

GPRS Fault Report

BTS Fault Report

Network Management Fault Report


4/58

Preface


5/58

Purpose Report Right ata Report Complete ata Reduce Fault Recurrence

!ocate Fault Timel"

Report #lements Fault Start and #nd Time

Fault Phenomenon escription Fault $andling Procedure S"stem ata


6/58

Case %nal"sis

Case &' !ook for a needle in a ha"stackThere were a lot of one(wa" audio and call drop faults

somewhere) #ngineers made dial test under the fault" BTS*

and returned the signalings recorded at %(interface and %+is(

interface* re,uesting anal"sis assistance from the researchinstitute)

Test MSinformatio

n?

Test siteinformatio

n?

Call starttime?

Comment: Ifyou are askedto analyze

this case, how

will you findusefulinformation

from numerousdata?


7/58

Case -' Blank information

%fter capacit" e.pansion* the downtown BTS kept restartingand could not work normall") The maintainers on site asked

for help from the research institute* and sent the O%M

messages recorded at %+is(interface first hand)

Ah, thesignaling filecomes, letsanalyze itnow Alas,

the

file is!lank

Comment:"lease askyourself: #doI know how to

ac$uire theright data?%#&id I checkthe ac$uireddata?% #&id Iconfirm the

com'leteness%


8/58

The on-site engineers should determine the specific fault

category and the required data according to the actual

conditions. If you are not sure, please consult the chief

engineers.

The file is a guide to fault information report instead of afault handling procedure. If you meet any major or urgent

fault, please handle it by following the major fault handling

procedure of the Technical upport !enter.

The on-site engineers should report fault information as

listed in theFault Ticketattached below.

Microsoft Word


9/58

!hapter "

Foreground BSC Fault Report


10/58

/hat 0s Foreground Fault1

(oardfaultwithin(SC

frame

(SCfaultwhen

addingor

deletinghardware

s

(TScommunication e)ce'tion

caused !y(SC

A*interface

e)ce'tion incommunication with MSC


11/58

Case %nal"sis

22 regional office recei3ed complaint from theoperator that the su+scri+ers in the south district could

not make or recei3e calls) The engineers went to thee,uipment room and found that MP R4N indicator

light of peripheral module 5 of BSC- was solid on 6all

the BTSs in the south district are connected with that

module7) %fter resetting the MP* the BTS was restored)

uppose you were on site, what data will

you return to help find out the fault cause#


12/58

oC mplaint: many

BTSs n!t s"pp #t

$all s%#&i$%'

oT(% s")s$#i)%#s

a#% &%#y an*#y an

t(% $ ns%+"%n$% is

&%#y s%#i "s'

oT(% p#int% ,-l * . t(% .a"lty

m "l% (as )%%n

s%nt t y "/ pl%as%

analy0% #i*(t n 1

an (an in t(%

.a"lt #%p #t'

+ault starttime?

+ault 'henomenon,historical alarms?

n*site reco-erymeasures?

Centralmodule M"'rinting?

.//012for

foregroundM"?


13/58

Common ata for Foreground BSC Faults

First learn a+out all the data* and then

report those useful for fault handling)


14/58

BSC faults

2%+"i#% in. #mati n 3n. #mati n "sa*% 3n. #mati n s "#$%

4a"lt sta#t tim%/ "#ati n/

an %n tim%

T (%lp t .in "t .a"lt

in. #mati n .# m a l t .

ata'

C ns"lt n5sit% sta..

6%tail% .a"lt p(%n m%n n/

in$l"in* ala#ms 7$"##%nt

ala#ms an #%$ &%#%

(ist #i$al ala#ms8/

n ti$%s/ ) a# ini$at #

li*(ts/ .a"lty m "l%/

%t$'

B a# ini$at # li*(ts/ syst%m

ala#ms/ an n ti$%s $ ntain

t(% m st )asi$ in. #mati n

a) "t t(% .a"lt'


4a"lt p(%n m%n n s( "l in$l"%

.a"lt in.l"%n$% t t(% %nti#%

n%t1 #9 an t s")s$#i)%#

$ mm"ni$ati n

la#m an n ti$% in. #mati n/

in$l"in* .a"lt p%#i / $an )%

. "n in 8$istor" ,uer"9 in thealarm interface

6%s$#ipti n a) "t m%as"#%s

ta9%n t %al 1it( t(%

.a"lt

T (%lp t s%pa#at% man"al

p%#ati n in. #mati n


-#intin* . . #%*# "n MP

.il%' C nsi%#in*

a$ti&%;stan)y $ n&%#si n/

) t( a$ti&% an stan)yMP 7!*R8 p#intin* .il%sa#% n%%%/ in$l"in*

.a"lt p%#i

Printed MP .il% $ ntains syst%m

.a"lt in. #mati n

Ba$9*# "n: :;OMC$OM#:tmp:mplog

-#int% in. #mati n .

. #%*# "n MP* including#RROR)!OG*

PO/#RON)!OG* and

0NT&5/ %t$'

T #%$ # MP hardware e.ception

information

3n t(% i#%$t #y . ;t#a$% .

. #%*# "n

,-' < " $an *%t t(% ata )

y $ nn%$tin* t t(% . #%*#

"n ,- 1it(

m$.tp'


15/58

=pp%#5l%&%l MSC information*MSC manufacturer* andlat%st ata "pat%'

3mp #tant . # >"*in* %(interfacefaults)

C ns"lt n5sit% sta..'

%(interface slot status* and NO)uer" OMCR +ackground 3ersion with command

amp ?3 in the OMCR ser3er=

A"%#y . #%*# "n MP an ) a# &%#si nin t(% s .t1a#% in t(% OMCR client*an +"%#y $"##%nt #"nnin* &%#si n )y

#i*(t $li$9in* t(% ) a# in t(%

p(ysi$al &i%1 int%#.a$%'

4nplug T0C +oard to check the hardware 3ersion)

GB(interface signaling tracing message

record

T analy0% JB5int%#.a$%

si*nalin* .l 1'

$+"i#% si*nalin* in. #mati n

Printed GPRS +oard file T $ n.i#m ) a# #"nnin*stat"s'

$+"i#% p#int% J-2S .il%

Connection mode of the network ca+le+etween the MP to GPRS e,uipment

rack' using the $MS or sharing one$4B with other e,uipments

To check whether $4B sharinginfluences GPRS'

Dn5sit% $(%$9

B file in the foreground* and BSCconfiguration +ackup file generated+" +ackground OMCR ser3er)

T $(%$9 n5sit%

$ n.i*"#ati n'

$+"i#% ata .# m . #%*# "n ,- 1it(

m$.tp

p #t $ n.i*"#ati n .il% .# m

;OMC$OM#:tools:d++ak in the +ackgroundser3er with cme.p)


31/58

!hapter 1

BTS Fault Report


32/58

/hat 0s BTS Fault1

.-ery!ody knows

BTS .alls'

BTS ) a# %$%pti n'

Call %$%pti n a# "n

BTS'

BTS $ n.i*"#ati n

m i.i$ati n .a"ltK


33/58

$ow to Report BTS Fault ata /ell1

+T faults inole four %ey points2 transmission, board,

cable, and 3IP switch. If all these four parts hae been chec%ed,

the +T has no problem.

ince the +T faults inole a lot of factors, the on-siteinformation need be reported as detailed as possible.

% good technical support engineer should

report the following data)


34/58

Basi$ BTS in. #mati n is &%#y

imp #tant:

BTS $ n.i*"#ati n in. #mati n@ 63-

s1it$(@ BTS &%#si n@ $ nn%$ti n m %

)%t1%%n BTS an BSC'

BTS .a"lt p(%n m%n n %s$#ipti n

is &%#y m"$( imp #tant:

B a# ini$at # li*(t@

$ mm"ni$ati n %$%pti n %s$#ipti n'

Syst%m in. #mati n . t(% .a"lty

BTS is . &ital imp #tan$%:

la#ms@ n ti$%s@ p%#. #man$%

#%p #ts'

ll 9ins . p#int% syst%m

m%ssa*%s a#% 9%y t t(% .inal

&i$t #y in .a"lt %liminati n:

)is5int%#.a$% si*nalin* m%ssa*%@

,- p#intin* m%ssa*%@ BTS

$ n.i*"#ati n )a$9"p .il%'

7ey7ey6atch6atchitit


35/58

Common ata for BTS Faults

First learn a+out all the data* and then

report those useful for fault handling)


36/58

+T.a"lts


4a"lt sta#t tim%/ "#ati n/ an %n

tim%

E%lp t .in "t .a"lt

in. #mati n .# m a l t .

ata'


6%tail% .a"lt p(%n m%n n/ in$l"in*

ala#ms 7$"##%nt ala#ms an

#%$ &%#% (ist #i$al ala#ms8/

n ti$%s/ ) a# ini$at # li*(ts'

BTS $(ann%l stat"s in ynami$

mana*%m%nt'

B a# ini$at # li*(ts/ syst%m

ala#ms/ an n ti$%s $ ntain

t(% m st )asi$ in. #mati n

a) "t t(% .a"lt'


C mm"ni$ati n .a"lt %tails .# m

m )il% p( n% s")s$#i)%#s'

6%s$#ipti n . "s%# $ mplaint is

&%#y imp #tant'

la#m an n ti$% in. #mati n/

in$l"in* .a"lt p%#i / $an )%

. "n in 8$istor" ,uer"9 in the alarminterface)

Dn5sit% t%st #%s"lt'

6%s$#ipti n a) "t m%as"#%s ta9%n t

%al 1it( t(% .a"lt

E%lp t s%pa#at% man"al p%#ati n

in. #mati n


BTS (a#1a#% typ% an $ n.i*"#ati n@ Basi$ BTS in. #mati n A"%#y .# m s .t1a#% l ain* int%#.a$%

. t(% OMCR$li%nt@

BTS &%#si n@ C ns"lt maint%nan$% sta..@

BTS an BSC $ nn%$ti n m % 7i#%$t

# $as$a% $ nn%$ti n8/ an

t#ansmissi n m % 7

#&/ pti$al

.i)%#/ mi$# 1a&%/ sat%llit%8@

Dn5sit% BTS $(%$9'

BTS5#%lat% 63- s1it$('


37/58

Foreground and +ackground BSC

#RT hardware t"pe* an

SP 3ersion)

T $ n.i#m 1(%t(%# t(%#% is

$ m)inati n .

#RTD-SP&)A-* which causes

3oice discontinuit"

A"%#y &%#si n t(# "*( t(% OMCR client=-l"* an "npl"* t(% #RT1(%n t(%

t#a..i$ is l 1' C n.i#m t(% $(ips

"s% )y t(% #RT +oard)

Si*nalin* t#a$in* m%ssa*%s

. O%MG RS! la"er at%B0S(interface of rele3antcells

T analy0% %B0S(interface signaling $+"i#% si*nalin* m%ssa*%

Fifteen(minute granularit" reportfor +asic measure inperformance management

-# )l%ms $$"##% a.t%# %na)lin*

. .#%+"%n$y ( ppin* an $Rfunctions should +e anal"@ed +"comparing +asic measurements

made +efore and after the faultoccurrence)

Cli$9 LA"%#y (ist #i$al ataM .# m

L,%as"#% tas9M in t(%

L-%#. #man$% mana*%m%ntM

int%#.a$% . t(% OMCR $li%nt'

C( s% L)asi$ m%as"#%M as t(%

m%as"#% typ%' S%l%$t #%l%&ant

$%lls/ in$l"in* all t(% $ "nt%#s'

-#intin* . a$ti&% ,- .

#%lat% m "l%s in t(%

. #%*# "n/ in$l"in*

t(% .a"lt p%#i

Printed MP .il% $ ntains syst%m.a"lt in. #mati n

-#int% . #%*# "n MP .il% is in t(%i#%$t #y . :;OMC$OM#:tmp:mplogin t(% )a$9*# "n

B file in the foreground* andBSC configuration +ackup filegenerated +" +ackground

OMCR ser3er)

T $(%$9 n5sit% $ n.i*"#ati n $+"i#% ata .# m . #%*# "n ,- 1it(

m$.tp@

p #t $ n.i*"#ati n .il% .# m

;OMC$OM#:tools:d++ak in the+ackground ser3er with cme.p)


38/58

!hapter 4

Network Management Fault Report


39/58

/hat 0s Network Management Fault1

5etworkmanagement

system cannot

ac$uire data0

&ata fromnetwork

managementsystem and local

data are not

consistent 1ink !etweennetwork

managementsystem andMC/ ser-er

aredisconnected0


40/58

Case %nal"sis

ome customer complained that the proincialnetwor% management system could not acquiredata from the cities it superised.

/sually the networ% management system is notproided by )T*. If you are sure that the localdata is normal, and the lin% with the networ%management system is normal too, you shouldconsider whether it is the problem of networ%management system.


41/58

ll

ll

n #malN#malN

3t m"st )%

t m"st )%

t(% p# )l%m

(% p# )l%m

. t(%

. t(%

n%t1 #9

%t1 #9

mana*%m%ntana*%m%nt

syst%m'

yst%m'

Are local'erformance and

alarm data

normal?

Is the linkwith networkmanagement

system ok?

Are there data inthe data sheetssent to the

networkmanagementsystem?

&oes our ser-ersend data to the

networkmanagementsystem?

Is theconfiguration filerelatedwith

networkmanagement

systemnormal?


42/58

Common ata for Network Management

Faults

First learn a+out all the data* and thenreport those useful for fault handling)


43/58

H%t1 #9 ,ana*%m%nt 4a"lts


4a"lt sta#t tim%/ "#ati n/ an

%n tim%

E%lp t .in "t .a"lt in. #mati n

.# m a l t . ata'


6%tail% .a"lt p(%n m%n n@

#%s"lt . $ mm"ni$ati n 1it(

n%t1 #9 mana*%m%nt syst%m

p# &i%#s

3t is imp #tant . # $ mm"ni$ati n

1it( n%t1 #9 mana*%m%nt syst%m

p# &i%#s'


6%s$#ipti n a) "t m%as"#%s ta9%n

t %al 1it( t(% .a"lt'

E%lp t s%pa#at% man"al p%#ati n

in. #mati n


Oin9 stat"s )%t1%%n n%t1 #9

mana*%m%nt syst%m an OMCR

s%#&%# 7$an t(%y P0NG eachother18' 3. p%#. #man$% an#%al5tim% ala#ms (a&%

i..%#%nt s%#&%#s/ $(%$9

t(%m #%sp%$ti&%ly'

T $(%$9 n%t1 #9 (a#1a#%' Ping communications +etween nodes

P(%t(%#

OMCR ser3er sends data tonetwork management port

T $(%$9 $ mm"ni$ati n )%t1%%n

s%#&%# p #ts'

C(%$9 1(%t(%# t(%

imf log file hasLRc3 CommOk MsgM

H%t1 #9 mana*%m%nt syst%m

p%#at #

6i..%#%nt p%#at #s #%+"i#%

i..%#%nt #%al5tim% ala#m

int%#.a$%s . # n%t1 #9

mana*%m%nt syst%m/ s"$( as

, )il% -(as% - and 5)

C ns"lt t(% $"st m%#/ an $(%$9

.il% :;OMC$OM#:conf:fmmgr)ini


44/58

!hec% in the database withusername teomcwhether there are data inm5measure5c" andm5tchperfm

To confirm whether localperformance data reportfunction is normal.

!onnect to the database withsqlplus teomc6teomc. 7uerym5measure5c" with select789 7uery m5tchperfmfor networ% management of:obile Phase &.

!onfiguration file;::'(.I0I andP:!;'.I0I in the

directory of=:*6conf

To chec% configuration file. 3ownload from =:!( sererwith ;TP.


45/58

!hapter ?

ata %c,uisition Guide


46/58

Signaling information ac,uisition&) 0n order to trace all signaling links at the same time* this function

need +e ena+led) Open s"scfg)ini in the director" of client:conf in theOMCR client* and find the following parameters 6in the end of thefile7

8S0GTRCCFG9

M%2C#!!N4M H 5

M%2N

-) Modif" the 3alue of +oth these two parameters to &J 6ma.imum to +etraced at the same time7)

5) Restart the client* and se3eral signalings can +e traced at the same

time)

K) %fter successful user log on* select 8PerformancemanagementLsignaling tracing9 from the main interface of OMC(R*and enter the signaling tracing main interface* as shown in the

following figure)


47/58


48/58

D) #nter the tracing setting window* choose the o+ect to

+e traced) Choose 8Signaling tracingLStart9 from

the main tracing interface* and enter the signaling

tracing configuration window) Choose the BSC and

N< link to +e traced* click Q okR * and the su+(window for %(interface tracing will pop up) From

now on* the tracing for the selected %(interface

signaling is started)


49/58


50/58

J) Select the file name and the director" to +e sa3ed* to

sa3ed the traced signalings) /hile the signaling is+eing traced* click the Sa3e +utton* and thedialogue +o. as shown in the following figure will popup) Select the file name and the director" to +e sa3ed*the traced signaling will +e sa3ed in the disk) Pa"

attention that onl" after this step* the conse,uentsignaling messages will +e sa3ed in the disk)Otherwise* e3en if the signalings are displa"ed in thewindow* the" will not +e sa3ed in the disk) Fordifferent signaling displa" su+(windows* each su+(window need +e selected and confirmed respecti3el"*otherwise* the signalings cannot +e sa3ed)


51/58


52/58


53/58

Below we will take the MP printing error as an e.ample to

introduce the usage of the tool of omcftp)

&) Connect to the foreground with command omcftp at the+ackground)

-) Connect corresponding MPs with command connect x.y.z6.stands for the BSC 0* " stands for the correspondingmodule num+er* and @ usuall" takes - or 5* where - standsfor the acti3e MP* and 5 stands for the stand+" MP7)

5) Get the log file for a certain period of time in the director"of :TR%C#) First enter that director" with command cd

/trace, then download0NT&5* #RROR)!OG* PR0NT)!OG*PO/#RON)!OG* and 2G&A)CFG with commandget

filename.


54/58

K) /hen the files ha3e +een downloaded to the ser3er* use

ftp tools such as C4T#FTP to transmit the file to theclient)

#.amples'

cd $OMCHOME

omcftp

connect 1.1.2

cd trace

prompt

get error.log (For a lot of file, !e "."#

ye


55/58

Get printed GPRS files)Printed GPRS file can +e ac,uired +" e.ecuting

PrtTool)e.e in the director" of :client:tools in the

OMCR client)

&) #dit prtToolCfg)ini in the director" of :client:conf:*and add the path of the printed file to +e sa3ed at the

end of FilePath H)

-) Open PrtTool)e.e* click S !ocation information

comparisonT * and configure the GPRS +oard to +eprinted as shown in the following figure)


56/58


57/58

5) %fter configuration is completed* choose the +oard to +e

+urned as shown in the following figure* and click

S StartT

K) Check the printed files in the sa3ed director")


58/58

PS'

For our common future* the on(site emplo"ees should

report fault information with full responsi+ilit" to

help to remo3e the faults as soon as possi+le)

gsm-bss fault information feedback training

Documents