Académique Documents
Professionnel Documents
Culture Documents
VE
ZMLER
1
NDEKLER
Appendix
Alarm and Event List Alarms ..............................................................................................33
Alarm and Event List Events .............................................................................................40
.
3
Alarm zebilmek iin;nce bize verilen bilginin-Alarmn deerlendirilmesi ,
Normal - olamas gereken deer ile karlatrlmas, varsa bal olduu dier
Alarm , bal olduu Hardware ve Software Seviyesine gre deerlendirilmesi
gerekir.
4
Bu kapsamda
SW ad Seviyesi
SW seviyesine bal olarak ekran grnleri ve Men deki yerleri baz farkllklar
gsterebilir.
5
2 Hardware Kontrol
Node B Integration Basicsdeki kurallara uygun ekilde configure edilmi kabinetteki ekipman
grnleri
2.1 Equipment
Kapal hali
6
2.2 RBS 3418 RRU RET
7
2.3 CBU ve ETMFX kartlar
8
2.4 RAX ve TX kartlar
9
2.5 TX ve OBIF
10
11
3 RADIO Network
12
3.2 Sektor Carrier Sinyalizasyon
13
4 IP Transport
14
5 Alarm Event ve Loglar
15
5.2 Alarm Log
16
5.3 Event Log
17
5.4 OSS Alarm List Viever
18
6 Alarm zm
Node B zerinde oluabilecek alarmlar ve zmleri Ericcson Customer Product Information
dosyalarnda (ALEX) ayrntlar ile belirtmektedir.
Alarmlar OSS zerinden Alarm List Viever veya Temip Maximo Optima gibi Raporlama
programlar ile ekilir.
rnek :
Youn RNC ve RBS mdahalesinden sonra sadece 3 gn sonra alnm bir baka rapor:
Temip_070609_1910
Alarm zmnde :
Kabinet iinde ve dnda hangi ekipmanlarn hangi ekipmanlar ile balantili alt dikkate
alnarak zm yoluna gidilmelidir.
19
6.1 Alarm inceleme ve zm
Aadaki resimde MBW02R1 RNC ye bal olarak alan HALBA 3G Node B ile ilgili alarmlar
grlmektedir.
Sahada birden fazla alarm olmas halinde en yksek ncelikli alarm dan balayarak tm alarmlar
giderilmelidir.
Baz durumlarda Alarm Event liste gre dk ncelik verilmi baz alarmlarn Node Bye ve
Network etkisi beklenenden daha yksek olabilmekte ve iemri ncelii ykseltilebilmektedir.
20
6.1.2 RNC de AMOS Grn
Alm iemrinde sahaya gitmeden mmknse operasyon merkezi ile irtibata geilerek sahada
mevcut olan TM alarmlar hakknda bilgi alnr.
Bu ilem OSS RNC zerinden AMOS denilen bir program ile yaplabilir.
Yukardaki resimde HALBA sahasna RNC ile balanmasndan sonra Node B zerinde grnen
alarmlar ve olas nedenleri sralanmaktadr.
Nr of active alarms are: 7
================================================================================================
Sever Specific Problem Cause Mo-Reference
================================================================================================
Maj AntennaBranch_AntennaSystemProblemInBranchB equipment_malfunction SectorAntenna=1,AntennaBranch=B
Maj AntennaBranch_AntennaSystemProblemInBranchB equipment_malfunction SectorAntenna=3,AntennaBranch=B
Maj AntennaBranch_FeederCurrentTooLowInBranchA equipment_malfunction SectorAntenna=1,AntennaBranch=A
Maj AntennaBranch_FeederCurrentTooLowInBranchA equipment_malfunction SectorAntenna=3,AntennaBranch=A
Maj AuxPlugInUnit_CommunicationLostWithRet equipment_malfunction SectorAntenna=1,AuxPlugInUnit=2
Maj AuxPlugInUnit_CommunicationLostWithRet equipment_malfunction SectorAntenna=3,AuxPlugInUnit=2
Maj OpticalInterfaceLink_OpticalInterfaceLinkFailure equipment_malfunction OpticalInterfaceLink=2-UL
>>> Total: 7 Alarms (0 Critical, 7 Major)
Okunan alarm tanmlar , olas nedenleri ,ekipmanlar ve bazende kabinetin SW seviyelerine bal
olarak alarm zme yollar izlenir.
22
6.2 CPI Alex dokmanlar ile Alarm zm
Ericsson Node B iin ngrd btn alarmlar ve olas zm yontemlerini kabinet tiplerine gre
ayrm ve Herbir kabinet tipi iin Urn , Montaj, Yedekparca, Bakm Arza bilgilerini ieren Alex
dosyalar hazrlamtr.
23
Hemen her alarm iin, ilgili alarmlar, Alarm loglarda neler grlecei, Bu alarmn dzeltilmesi iin
neler yaplmas gerektii ayrntlar ile anlatlmtr.
24
6.3 En ok Karlalan 10 Alarm
Aada Hazirann ilk haftasnda NodeB kaynakl alarmlardan enok karlalanlar sralanmtr.
4 nolu port:
Bilgisayar EMAS ile Lokalden Node Bye balantnn yapld porttur. Bu porttan alarm
gelmesi, lokal fiziksel balantnn yaplmad anlamna gelir. Operasyonel anlamda bir sorun
tekil etmemektedir ve bu alarm iin i emri retilmemektedir. Alarmn giderilmesi iin 4 nolu
port EMAS ile yada RNC den bloklanabilir ve sonrasnda. Bu bloklama herhangi bir soruna
neden olmayacaktr.
5 nolu port:
Genellikle 3418 kabinetler iin kullanlan 4,5,6 sektrlerin yerald 2. RBS 3418 iin gerekli
olan transmisyon k - kaskat balantnn yapld porttur. Sahaya gelen transmisyon
balants 6 nolu porta girmektedir ve 5. Porttan alnan kaskat, 2. Kabinete 6 nolu porttan
girmektedir. Bu alarm, kaskat balantnn henz yaplmad anlamna gelebilir. Bu alarmn
giderilmesi iin 2. Kabinetin ilavesi beklenmelidir. Eer bu port bloklanrsa 2. Kabinet almaz.
6 nolu port:
Sahaya gelen transmisyon balantsnn girildii porttur.
Bu porttan gelen alarmn bilinen 2 nedeni vardr. Birincisi, normalde 100Mbit Full Duplex
olarak ayarlanm olmas gereken balantnn Transmisyon ekipmanlarnda (TAN-Router)
10Mbit olarak tanmlanmasdr veya Half Duplex- Full Duplex tanmlamasndaki bir hatadr. Bu
durumda TAN tarafndaki tanmlamalar kontrol edilmelidir ( aksiyon TN). kinci durum ise
Sahadaki Transmisyon ekipman (ML TN-NPU3-ETU2) ile kabinet arasnda yanl kablo tipinin
kullanlmasdr. TAN tarafndaki tanmlar doru ise sahada transmisyon kablo kontrol
gerekmektedir.
25
6.3.2 AuxPlugInUnit_CommunicationLostWithRet
Bu alarm Anten siteminde sk olarak kullanlan RET ekipman ile balant sorunlar yaanmas
halinde ortaya kar. Hem Makro kabinetler (RBS 3206-3106-3216-3116) hem de Main Remote
kabinetler (RBS 3418- 3518) karlalan bir alarmdr.
Makro kabinetlerde
RBS 3206-3106-3216-3116 gibi Makro NodeB kabinetlerde RET gerekli olan enerjiyi cabinet
ierisindeki RU FU kartlarndan Coaksiyel Feeder kablolar zerinden alr. RET in beslenmesi
ve kontrol edilmesi iin Feeder zerinde ASC yada RUI montaj yaplm olmaldr.
Arzann zm iin ;nce ASC RUI ile ilgili bir alarm olup olmad control edilir. Varsa bu
alarm zlr. Daha sonra RET ile ASC-RUI arasndaki data enerji kablosu kontrol edilir.
Gevek ise sklr, Arzal ise deitirilir.
Main Remote kabinetler
RBS 3418- 3518 gibi Main Remote kabinetlerde RRU zerindeki AUX EXT k ile RET
arasndaki data enerji kablosu kontrol edilir. Gevek ise sklr, Arzal ise deitirilir.
6.3.3 AntennaBranch_FeederCurrentTooLowInBranchA
Bu alarm NodeBye Site Equipment Script ile tanmlamas yaplan Feeder kabloya ait zayflama
(Attenuation) ve gecikme (Delay) deerlerinin Node B tarafndan (ASC-RU-RRU) llen
deerlerle karlatrmas ve farkl kmas durumunda retilen bir alarmdr.
Bu alarmn zm Kabinet tipine gore farkllk gsterir
Makro kabinetlerde
RBS 3206-3106-3216-3116 gibi Makro NodeB kabinetlerde ve tm SW seviyelerinde (P6.1.0,
P7.01, P7.02 gibi) RU dan balayarak Antene kadar olan kablolarn fiziksel kontrolu, DTF,
SWR, Insertion Loss testlerinin tekrarlanmas , varsa ASC alarmlar ile birlikte incelenirvarsa
arzalar dzeltilir.Testler sonunda hesaplanan gecikme ve zayflama deerleri ile Kabinet
zerinde tanmlanan deerler karlatrlr gerekiyorsa llen deerlere gre gncellenir.
Bunun yannda Antenna Supervision deerlerinin Site Equipmentte doru girildii kontrol edilir
Antenna Supervision deerleri aadaki tabloya gre dzenlenmi olmaldr
BRANCHA Indoororsharedfeeder 0
Others 10
BranchB IndoororsharedfeederorASCexisting 0
Others 80
Main Remote kabinetler
RBS 3418 -3518 kabinetlerde P7.0.2 seviyesine kadar bu alarm SWden kaynaklanan bir hata -
FAKE bir alarmdr. Eer sahada sadece bu alarm varsa mdahale etmeye gerek yoktur.
6.3.4 AuxPlugInUnit_CommunicationLostWithAsc
Bu alarm Anten siteminde sk olarak kullanlan ASC ekipman ile balant sorunlar yaanmas
halinde ortaya kar. Hemen tum Makro kabinetler (RBS 3206-3106-3216-3116) ile baz Main
Remote kabinet (RBS 3418- 3518) kullanlan anten sistemlerinde karlalan bir alarmdr.
26
zerinden alr. FU zerindeki ANT A k ASC iin gerekli olan enerji ve control sinyallerinin
alnd konnektordur.
Arzann zm iin ;nce kabinet ierisinde RU FU ile ilgili bir alarm olup olmad kontrol
edilir. Varsa bu alarm zlr. FU - ASC arasndaki Jumper ve Feeder kablolar kotrol edilir. A ve B
kollarnn doru ulara balandii kontrol edilir. Konnektrler control edilerek Gevek ise sklr,
Arzal ise deitirilir.
Site Equipmentde girilen Antenna Supervision deerleri aadaki tabloya gre dzenlenmi
olmaldr
BRANCHA Indoororsharedfeeder 0
Others 10
BranchB IndoororsharedfeederorASCexisting 0
Others 80
6.3.5 OpticalInterfaceLink_OpticalInterfaceLinkFailure
Sadece Main Remote kabinetlerde karlalabilecek bir alarmdr.
Remote unite RRU tayaca data ve Kabinet ii haberleme bilgilerini Main Uniteye Fiber optic
kablolar ile tar.
Optical Interface Link Failure alarm ncelikle ok hassas ve krlgan olan Fiberoptik kablo olmak
zere ; OBIFB kart kart zerinde yeralan SFP konnektor , Optik kablo, ve RRU zerinde yeralan
SFP konnektor ekipmanlarndan bir yada birkann hasarl krk yada kullanlamaz halde olduu
anlamna gelir.
Montaj esnasnda Fiberoptik kablo konnektorlerine dokunarak kirletmekte sk karlalan sorun
kaynaklarndandr
Eer sahadaki tm sektrlerden bu alarm geliyorsa OBIF kartnda problem olabilir. Bu durumda
ncelikli olarak bu karta restart atlmas denenmelidir. Bu restart sorunu zmezse OBIF kart arzal
olabilir yada RRU montaj yaplp yaplmad , OPTK kablolarda krk olup olmad tekrar
control edilmelidir.
6.3.6 UpLinkBaseBandPool_ULHWLessThanULCapacity ve
DownLinkBaseBandPool_DLHWLessThanDLCapacity
Yukardaki iki alarm da kapasite ile ilgili alarmlardr ve RAX-TX kartlarndaki problemler
nedeniyle tetiklenen alarmlardr. Sahann devreye alnmas esnasnda Site Equipment yklenmemi
kabinette grlebilirler. Ayn zamanda RU ve RRU ile ilgili problemlerde de bu alarm gelebilir.
Arzann gideriminde nce kabinete monte edilmi olan RAX ve TX kartlar detayl olarak incelenir.
Sorunlu olduu belirlenen ekipmana restarttan sonu alnamazsa sahaya genel restart denenebilir.
Lisans eksiklii, Uplink iin gerekli EUL Resource ve Downlink iin gerekli HS Resource
deerleri kullanlan kart tiplerine gre RNC ile karlkl kontrol edilir. Dzelmemesi durumunda bu
saha Ericssona iletilmelidir.
6.3.7 AntennaBranch_AntennaSystemProblemInBranchB
FU zerindeki ANT B kna bal olan kablodaki bir feeder kablo hatas durumunda karlalr.
27
Bunun yannda InBuildig sistemlerinde sadece ANT A k kullanldndan yanllkla B k
iinde Antenna Supervision deeri girilmesi durmunda bu hata ile karlaslr.
Arzann gideriminde nce Antenna Spervision parametreleri kontrol edilir. Daha sonra FU ile
Anten arasndaki feeder sistemi gzle control edilir. DTF VSWR testleri tekrarlanarak arzal
ksmlar deitirilir.
6.3.8 AuxPlugInUnit_NewAuxiliaryUnitDetectedNotCorrespondingToTheDefin
edConfiguration
zellikle sahadan, Montaj Arza personeli tarafndan SW upgradei yaplm kabinetlere daha
sonra SW yklemesine ihtiya duyan (hemen tm kartlar) yeni bir kart veya ekipman ilave
edilmesinden sonra grlr. En ok Montaj ve Upgrade ilemi bitmi sahalara daha sonra ASC -
RET montaj yapldktan sonra grlr.
Arzann gideriminde; RNC OSS te kullanlmakta olan bir FTP server zerine gerekli SW
Upgrade paketleri bulundurularak zmlenebilir.
Yada ;sahaya gidilerek Active durumdaki SWUpgrade paketi zelliklerine properties ile girilir.
Arza personelinin bilgisayarnda FTP server program alarak SW Upgrade paketibi barndran
folder ve File part bilgileri gncellenir. Daha sonra Install PIU Type seceneginden Kartn product
kodu secilerek gerekli SW yklenir. Backup alnarak Restart verilir. SWnin yeni taklan karta
yklenerek Kartn aktif hale gelmesi 15-20dak bulabilir.
6.3.9 RbsLocalCell_MaxNumHsPdschCodesExceedsLicensedLimit
Node B zerine montaj yaplm tm HWin uygun O&M, Site Equipmet ve Iub ile dzenlenmesi
gereklidir. Bu HWin alabilmesi iin NodeBye uygun zelliklere sahip lisansnda yklenmesi
gerekir.
Bu alarmn giderilmesinde RNC ile konuarak gerekli Lisansdosyalarnn yuklenip yuklenmedii.
RAX ve TX kartlarnda , Uplink iin gerekli EUL Resource ve Downlink iin gerekli HS
Resource deerleri kullanlan kart tiplerine gre uygun deerlerde ve lisans deeriniamayacak
ekilde ayarland kontrol edilir.
6.3.10 NbapCommon_Layer3SetupFailure
pmNoiseFloor adndaki bir countern dolmas sonucu reyen bir alarmdr. Gncel duruma gre bu
counter, NodeB tarafndaki tanmlamalardan karlmtr. Buna ramen daha once tanmlanp
tranmisyonu zun srekesik kalan sahalardan gelebilecek bir alarmdr.
Bu alarmn giderilmesinde; RNC ile konusarak ilgili Counterin RBS ten silinmesi ve backup alp
restart atarak alarm kaldrmas istenir.
Aadaki alarmlar ounlukla Node B alarmlardr. lerinde RNC tarafndan da grlen alarmlar
vardr.
Aklamalar RNCde alsan kiiler iin yazlmtr.
28
6.4.1 Heartbeat failure
Bu alarm 2Mbit balants ile ilgilidir ve bu alarma santral tarafnda alnabilecek bir aksiyon
bulunmamaktadr. Aksiyon TN
6.4.3 AuxPlugInUnit_PiuConnectionLost
lgili HW iin ncelikle santral tarafndan genel bir kontrol gereklidir. Genel bir alarmdr. Uygun
olmayan SW ieren veya Uygun olmayan ekilde sklm bir kartn slotundan bu alarm gelebilir.
Ulalan bulgulara gre BOya aksiyon verilebilir.
Carrier_RxDiveristyLost
lgili sektrn anten ekipmanlarna restart atmak denenmelidir. Sonu alnamazsa sahaya genel
restart atlabilir.
6.4.4 DbccDevice_GammaDownLinkFailure
Tx kaynakl bir problem olmas muhtemeldir. lk mdahale olarak sorunlu grnen TX kartna
restart atlmaldr. Bu mdahale sorunu zmezse RUIF e restart atlmaldr. Restartlar ile bir
sonu alamyorsak nce TX, sonra da RUIF(3206)/OBIF(3418) iin HW test balatmak
gerekmektedir. Sorun yine tekrarlarsa sahaya backup alp test ieren genel restart (cold restart with
test) atlmaldr. Eer problem yine devam ediyorsa bu durum Ericssona bildirilip kart deiimi
istenmelidir. Kart deiimi de sorunu gidermezse CSR aarak Ericssondan zm beklenmelidir.
6.4.5 Carrier_NumberOfCarriersExceedsLicensedLimit
Bu alarm, lisans ykl olmayan sahaya P7.0.2 SW seviyesine upgradeden kaynaklanmaktadr.
Upgrade yaplan sahaya upgradee uygun lisans yklenerek bu alarm giderilebilir. Eer gerekli
lisans OSSte mevcut deilse Ericssondan talep edilmelidir.
6.4.6 Carrier_RejectSignalFromHardware
Alarm aklamasnda belirtilen sektrn anten ekipmanndan (RRU, RU-FU vs.) kaynaklanan
problemdir. Aklamada belirtilen ekipmana restart atlmaldr. lk restart ie yaramazsa 2. Ve 3.
Restartlar denenebilir. Ekipman restartlar ie yaramazsa sahaya genel restart atlmaldr. Problem
devam ediyorsa SW paketi ile lisans uyumsuzluundan kaynaklanma ihtimali vardr. Bu durum
Ericssona yneltilmelidir.
6.4.7 Eul_NbapMessageFailure
RNCde reyen bir alarmdr. lgili sahann EUL kanallarnn almamas nedeniyle oluur.
ncelikli olarak NodeB tarafnda lisans kontrol yaplmaldr. EUL ieren bir lisans ykl olmaldr.
29
Eer lisans olup da almama durumu varsa HS ve EUL kaynaklar kontrol edilmelidir ve kabinet
tipine gre olmas gereken deerlere ayarlanmaldr. Bu dzeltmeye ramen EUL almazsa, RNC
tarafnda Iub datas ierisinde olmas gereken Edch MOsu tanmlanmam olabilir. Bu MO da
tantlp halen sorun devam ediyorsa NodeBde HW kontrol yaplmaldr.
6.4.8 Hsdsch_NbapMessageFailure
lgili sahann HS kanal tanmlar kontrol edilmelidir. Tanmlarda sorun yoksa RAX-TX kartlarnda
problem olabilir. Bu kartlar iin genel kontrol gereklidir.
6.4.9 ObifDeviceGroup_GammaLinkFailure
OBIF kartna restart atmak denenmelidir. Sonu alnamazsa sahaya genel restart denenebilir. Tekrar
sonu alnamazsa OBIF deiimi gerekebilir.
6.4.12 Rach_NbapMessageFailure
RNCde reyen bir alarmdr. lgili sahann Rach kanallarnn almamasna iaret eder. Bu durum,
NodeB tarafnda RAX kartndaki arzadan kaynaklanabilir. Kabinetteki kartlar kontrol edilmelidir.
RaxDeviceGroup_GeneralSWError
NodeBde reyen bir alarmdr. RAX kartndan kaynaklanmaktadr. lk mdahale olarak bu alarmn
geldii slottaki RAX kartna restart atlmaldr. Sorun devam ederse fcleanff yntemi
uygulanabilir ve ardndan sahaya restart atlmaldr. Halen problem devam ediyorsa aadaki
alarmlardan herhangi birinin daha olup olmad kontrol edilmelidir. Eer bunlardan biri varsa,
alarmlarn fake olma ihtimali vardr ve bu sorun SW upgrade ile zlecektir. Bu durumdaki sahay
Ericssona bildiriniz.
6.4.13 RetDevice_RetFailure
lgili sektrn RET ekipmannda sorun bulunmaktadr. ncelikle bu ekipmana restart denenmelidir.
Sonu alnamazsa RETin bal olduu RU-RRU ekipmanna restart denenebilir. RETi force
calibration ile yeniden kalibre etmek ie yarayan zmlerdendir.Yine de sonu alnamazsa RET
deiimi gerekebilir.
30
6.4.14 TrDeviceSet_GeneralHWError
TX kartnda veya RRU ekipmannda HW bir problem olumutur. Alarm ierii incelenerek
problemin olutuu kart,ekipman vs. deiimi iin sahaya ekip ynlendirilmelidir.
6.4.15 UbchDeviceSet_GeneralSWError
RAX kartnda oluan bir problemdir. Bu karta restart atarak sonu alnamazsa sahaya genel restart
denenebilir. Eer sorun halen devam ediyorsa yukarda bahsedilen fake alarm trnde bir alarm
olma ihtimali yksektir. P7.0.2 SW upgrade ile pekok sahada giderilebilmektedir .
6.4.16 Utrancell_ExternalResourceUnavailable
NodeBdeki NbapCommon_Layer3SetupFailure alarmnn RNCde tetikledii bir alarmdr.
NodeB tarafndaki alarm giderildikten sonra bu alarm da kalkmaktadr.
6.4.17 Utrancell_NbapMessageFailure
RNCde reyen bir alarmdr. lgili sahada kesik olan sektr/sektrlerden gelmektedir. Saha
incelenerek NodeB zerindeki alarma gre gerekli aksiyonlar alnmaldr.
6.4.18 Utrancell_RBSLocalCellNotAdded
RBS ve RNCdeki sektr tanmlamalar arasndaki uyumazlktan kaynaklanmaktadr. Saha 4 sektr
olmas gerekirken NodeB tarafnda 3418 tipinde 2. Kabinetin bulunmamas bu duruma bir rnektir.
Bu alarma neden olabilecek baka bir durum ise, Cell ID bilgilerinin RNC ve RBSte farkl
olmasdr. Bu bilgi iki tarafta da ayn olmaldr. RNC ve NodeB tarafinda control edilmelidir.
NodeB tarafnda ancak Site equipmentin silinip tekrar yklenmesi ile giderilebilir..
6.4.19 Utrancell_ServiceUnavailable
Bu alarm RNCde remektedir ve ilgili sahann tamamnn kesik olduunu belirtmektedir. Bu
durumda ncelikle RNCden sahann Iubsinin alp almad kontrol edilmelidir. Eer Iub
DISABLED durumdaysa 2 ihtimal szkonusudur. Ya RBS tarafnda Iub ykl deildir, ya da
transmisyon kaynakl bir kesinti vardr. Iub ykl deilse yklenerek bu alarmn kalkmas
beklenmektedir. Eer transmisyon kaynakl bir kesinti sz konusuysa bu durumdaki saha ilgili
transmisyon ekibine bildirilmelidir. emri Transmisyon ekibine iletilir.
Sahada HW kaynakl bir probleme rastlanrsa olumu soruna gre aksiyon alnr.
6.4.20 RruDeviceGroup_GammaLinkFailure
Belirtilen sektrn RRU ekipmannda sorun bulunmaktadr. ncelikle bu RRUya restart
denenmelidir. RRUya mdahale sonu vermezse srayla OBIF ve TX kartlarna restart atmak
denenebilir. Eer ana MO ENABLED durumda olup da alt MOlar DISABLED olarak
grnyorsa RRU toplayacak demektir. Ksa bir sre ierisinde tm MOlarn ENABLED
duruma gelmesi beklenmektedir. Tm mdahalelere ramen hibir MO ENABLED olarak
grnmyorsa RRU deiimi gerekmektedir.
31
6.4.21 Emergency Unlock of Software Licensing
Emergency lisans aktif edilmi bir sahadan gelen alarmdr. Bu lisans her bir saha iin 2 kere 1
haftalk olmak zere aktif edilebilir ve bu 1 haftalk sre iinde tm featurelar kullanlabilir. Bu
sre bitiminde saha trafiinin tamam ya da nemli bir ksm kapanabilir. Bu durumdaki bir saha
Ericssona bildirilmelidir ve i emri Ericssona ynlendirilmelidir.
6.4.22 Utrancell_NbapReconfigurationFailure
lgili sahann performans dklnden dolay oluan bir uyardr. RNC tarafndaki parametre
deiiklikleri ile dzeltilebilir.
Bu problemin nedeni, RNC tarafnda ilgili hcre iin tanmlanm transmisyon g deerinin RBS
tarafnda girilen feeder uzunluklar, delay ve attenuation deerlerine gre hesaplanm transmisyon
gc bilgisinin maksimum ve minimum snrlar dnda kalmasdr.
Bu sorunu zerken RBS tarafndaki bilgi referans alnp, RNC tarafna bu deerin girilmesi
gerekmektedir.
32
APPENDIX: Alarm and Event List - Alarms
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
AscDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is AscDeviceGroup
complete.
The event is issued if reconfigurations were required and have been performed.
AuxPlugInUnit_NewAuxiliaryUnitDetectedNoPredefinedConfigAn Auxiliary Plug-in Unit is replaced by an older or newer version and an attempt to unlock AuxPlugInUnit
the unit is made.
The Auxiliary Unit or Non-processing Unit can be connected to two Device Boards. If the link
between the Main Processor and Auxiliary Unit or Non-processing Unit goes down, the Main
Processor can set up a communication path through the other Device Board.
AuxPlugInUnit_SuccessfulRecoveryActionPerformedSwitched AuxPlugInUnit
A switching of communication path to Auxiliary Unit or Non-processing Unit has been
performed.
The Auxiliary Unit or Non-processing Unit can be connected to two Device Boards. If the link
between the Main Processor and Auxiliary Unit or Non-processing Unit goes down, the Main
Processor can set up a communication path through the other Device Board.
BbifBoard_SuccessfulRecoveryActionPerformedReestablishe BbifBoard
A switching of communication path to Auxiliary Unit or Non-processing Unit has been
performed.
The Auxiliary Unit or Non-processing Unit can be connected to two Device Boards. If the link
between the Main Processor and Auxiliary Unit or Non-processing Unit goes down, the Main
Processor can set up a communication path through the other Device Board.
BfuDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is BfuDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
CluDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is CluDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
CuDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is CuDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
DeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is DeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
E1PhysPathTerm_NoCRC4Mfa In CRC-4 mode, AUTOMATIC, the frame alignment algorithm has entered the state: Assume E1PhysPathTerm
CRC-4-to-non-CRC-4 interworking.
PHY_E1Ppt_MI_AUTOLOCK_IND A port is locked. E1PhysPathTerm
E1Ttp_NOCRC4MFA In CRC-4 mode, AUTOMATIC, the frame alignment algorithm has entered the state: Assume E1Ttp
CRC-4-to-non-CRC-4 interworking.
PHY_E3Ppt_MI_AUTOLOCK_IND A port is locked. E3PhysPathTerm
A Non-Local MAU Has Been Chosen as the Active Client Split Ethernet Server is not executing on the same MP as the Split Ethernet Client. EthernetLink
Fan_New Fan detected, matches the defined configuration The new hardware can be used. No reconfiguration was needed, or the node reconfigured Fan
itself automatically.
Fan_New Fan detected, no predefined configuration exist This fan cannot be used. There is no software allocation for the fan. Fan
FanDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is FanDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
FcuDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is FcuDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
FuDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is FuDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
Link switched Traffic has moved from one link to the other link. GigaBitEthernet
One of two links outage One Ethernet link has failed. (One link is still in operation.) GigaBitEthernet
One of two links outage ceased One failed Ethernet link has recovered. (Two links are now in operation.) GigaBitEthernet
InterSubTimingCable_SuccessfulRecoveryActionPerformedS A switching of BB Clock source has been performed. InterSubTimingCable
All RAX and TX boards always get their BB clock from either the BBIF1 or BBIF2. The clock
source can be switched between these two boards.
IntraCabTimingCable_SuccessfulRecoveryActionPerformedS A switching of BB Clock source has been performed. IntraCabTimingCable
All RAX and TX boards always get their BB clock from either the BBIF1 or BBIF2. The clock
source can be switched between these two boards.
Ip over ATM Link Supervision Failed The operational state of the MO has become DISABLED. IpAtmLink
Ip over ATM Link Supervision Recovered The operational state of the MO has become ENABLED. IpAtmLink
Default router switch The default router for traffic has changed. IpInterface
PHY_J1Ppt_MI_AUTOLOCK_IND A port is locked. J1PhysPathTerm
Licensing_CapacityChange A license-controlled capacity has changed value. Licensing
Licensing_FaultyFormatVersion The format version is faulty in the license key file. Licensing
Licensing_FaultyLicenseKey A license key is faulty in the license key file. Licensing
Licensing_FaultySeqNum The sequence number is faulty in the license key file. Licensing
Licensing_FaultySignature The signature is faulty in the license key file. Licensing
Licensing_FeatureChange A license-controlled feature has changed state. Licensing
Licensing_FingerPrintMismatch The fingerprint on the node does not match the fingerprint in the license key file. Licensing
Licensing_MultipleLicenses Multiple license keys are found in the license key file. Licensing
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
Mspg_ProtectionSwitch A switch to the standby board or port has been made. This board or port is now handling Mspg
traffic.
Mspg_ProtectionSwitchFailure An attempt to switch to the standby board or port has failed. Mspg
PHY_MSPGMI_K2MISMATCH_IND The K2 MISMATCH protocol state is entered. Mspg
NodeBFunction_DlHwUsageLimitedToLicensedLevel UL and DL BB capacity is not immediately limited by levels specified in BB capacity LKs. NodeBFunction
When the grace period is over, the capacity is restricted to the licensed level and the event is
issued.
NodeBFunction_MainProcessorRestarted The main processor is restarted for one of the following reasons: NodeBFunction
Power on
Reset button
SW initiated
Watch dog
Undefined
NodeBFunction_MpTrafficApplicationRestarted NodeBFunction
The Main Processor Traffic Application is restarted.
The event is issued whenever the restart of an active Main Processor Traffic Application is
performed by the application itself, or triggered by a restart of the Main Processor in the RBS.
NodeBFunction_NodeRestarted The node is restarted for one of the NodeBFunction
following reasons:
Power on
Reset button
SW initiated
Watch dog
Undefined
NodeBFunction_OaMApplicationRestarted This event is issued any time the restart of an active O&M Application is performed by the NodeBFunction
application itself, that is not triggered by a processor restart.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
ObifDeviceGroup_SuccessfulRecoveryActionPerformedReestThis event is sent when there is a short period of gamma link failure. ObifDeviceGroup
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
Pccpch_DownLinkChannelResourceRedundancySwitchOver New hardware has been allocated. The channels BCH and PCCPCH have been set up on thePccpch
new hardware, and have started sending system information.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
PowerSupplySystem_BatteryTestResult A battery test has been performed. PowerSupplySystem
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
RaxDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is RaxDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
RbsSynchronization_NodeSynchronizationRedundancySwitchThis event is issued at successful automatic switch over of distributing Timing Unit to stand- RbsSynchronization
by unit.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
RfifDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is RfifDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
RfifDeviceGroup_SuccessfulRecoveryActionPerformedReestaThis event is sent when there is a short period of gamma link failure. RfifDeviceGroup
All RAX and TX boards always get their BB clock from either the BBIF1 or BBIF2. The clock
source can be switched between these two boards.
RruDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is RruDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
RuDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is RuDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
RuifDeviceGroup_ SuccessfulRecoveryActionPerformedReesThis event is sent when there is a short period of gamma link failure. RuifDeviceGroup
RuifDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is RuifDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
SaiuDeviceGroup_SuccessfulRecoveryActionPerformedBoardA restart of the whole Device Board or Auxiliary Unit has been performed. SaiuDeviceGroup
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
Download of Local AA Database completed The reqested local AA database was successfully installed Security
Download of Local AA Database failed The requested local AA database was not installed Security
Download of Trusted Certificates completed The requested certificate(s) was(were) successfully installed Security
Download of Trusted Certificates failed The requested certificate(s) was(were) not installed. Security
Node Credentials expiring Node Credentials will expire. See attribute, certExpirWarnTime. Security
Node Credentials installed Node Credentials are installed. Security
Node Credentials rolled back The enrollment action has been rolled back, the new credentials have been discarded and theSecurity
credentials used before enrollment started, if any, have been reinstated.
SlotNew PIU detected, matches the defined configuration The new hardware can be used. No reconfiguration was needed, or the node reconfigured Slot
itself automatically.
SlotNew PIU detected, no predefined configuration exist This slot cannot be used. There is no software allocation for the slot. Slot
StrxDeviceGroup_ SuccessfulRecoveryActionPerformedReesThis event is sent when there is a short period of gamma link failure. StrxDeviceGroup
StrxDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is StrxDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
BPDU Guard, Port Blocked Bridge Port Data Unit Guard blocks an Edge Port. SwitchPortStp
BPDU Guard, Port Unblocked Bridge Port Data Unit Guard unblocks an Edge Port. SwitchPortStp
Edge Port Mode transition to EDGE_OFF A port with attribute, edgePortMode set to AUTO_EDGE or ADMIN_EDGE_ON, transits to SwitchPortStp
EDGE_OFF.
Edge Port Mode transition to EDGE_ON A port with attribute, edgePortMode set to AUTO_EDGE or ADMIN_EDGE_ON, transits to SwitchPortStp
EDGE_ON.
STP Role transition to ALTERNATE Spanning Tree Protocol role transits from ROOT to ALTERNATE. SwitchPortStp
STP Role transition to ROOT Spanning Tree Protocol role transits from ALTERNATE to ROOT. SwitchPortStp
NssSynchronization_SynchRefChanged A new reference has been selected as the active reference. Synchronization
NssSynchronization_SystemClockStatusChanged The state of the system clock has changed. Synchronization
PHY_T1Ppt_MI_AUTOLOCK_IND A port is locked. T1PhysPathTerm
PHY_T3Ppt_MI_AUTOLOCK_IND A port is locked. T3PhysPathTerm
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
TuDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is TuDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
TxDeviceGroup_HardwareTestEndIndication When a hardware test is manually initiated, an event notification is sent when the test is TxDeviceGroup
complete.
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.
Creating a Configuration Version Creation of a configuration version has been requested. UpgradePackage
Entering normal mode The upgrade phase is finished and the state of the node is set to normal mode, that is, fault- UpgradePackage
tolerant mode, and the upgrade supervision timer is stopped.
Entering upgrade mode UpgradePackage
The upgrade phase is initiated and the system state is set to upgrade mode: the rollback CV
is created, fault-tolerant mode is set, and the upgrade supervision timer is set.
Executing an application unique trigger An undefined application-specific action is executing. UpgradePackage
Executing trigger Confirmed Confirmation that the node is in a normal state (normally after manual confirmation of the UpgradePackage
upgrade).
Executing trigger Convert Configuration data is converted. UpgradePackage
Executing trigger Execute The switch to new software is to be executed. UpgradePackage
Executing trigger Finish Old loader information and old persistent data are cleaned up. Old programs are also UpgradePackage
removed.
Executing trigger Initiate UpgradePackage
New programs are created, and old programs are prepared for being taken out of operation.
Executing trigger Preload Software that is preloadable is preloaded on device boards. UpgradePackage
Execution of upgrade failed The execution of upgrade failed for some reason. A rollback may occur and the node may UpgradePackage
restart.
Java Virtual Machine (JVM) restart requested A restart of the JVM has been requested. UpgradePackage
Node restart requested A node restart has been requested. UpgradePackage
Node upgrade requested A reboot node upgrade has been requested. A CV is created and is set as startable before UpgradePackage
the node is restarted.
Reboot PIU upgrade requested A reboot PIU upgrade has been requested, that is, one or more PIUs will be restarted. UpgradePackage
Reconfiguring MOs MOs, as defined in the upgrade control file, are reconfigured, for example: PiuType, UpgradePackage
Repertoire, ReliableProgramUniter, PlugInUnit, and SwAllocation.
Soft PIU upgrade requested A soft PIU upgrade has been requested, that is, a number of programs are started, stopped UpgradePackage
or upgraded.
Start or stop of program(s) requested One or more programs are to be started or stopped. UpgradePackage
Upgrade executed The execution of upgrade is finished. UpgradePackage
Upgrade requested An upgrade action has been requested, for example, rebootNodeUpgrade. UpgradePackage
UpgradePackage AUE confirmed with warning An Application Upgrade Engine has confirmed with a warning. UpgradePackage
UpgradePackage AUE failure An Application Upgrade Engine has reported a failure or has not answered within the UpgradePackage
expected time.
UpgradePackage AUE progress Progress indication from an Application Upgrade Engine that is part of the upgrade. UpgradePackage
UpgradePackage Creating a Configuration Version Creation of a configuration version has been requested. UpgradePackage
UpgradePackage Entering normal mode The upgrade phase is finished and the state of the node is set to normal mode, that is, fault- UpgradePackage
tolerant mode, and the upgrade supervision timer is stopped.
UpgradePackage Entering upgrade mode The upgrade phase is initiated and the system state is set to upgrade mode: the rollback CV UpgradePackage
is created, fault-tolerant mode is set, and the upgrade supervision timer is set.
UpgradePackage Executing an application unique trigger An undefined application-specific action is executing. UpgradePackage
UpgradePackage Executing trigger Confirmed Confirmation that the node is in a normal state (normally after manual confirmation of the UpgradePackage
upgrade).
UpgradePackage Executing trigger Convert Configuration data is converted. UpgradePackage
UpgradePackage Executing trigger Execute The switch to new software is to be executed. UpgradePackage
UpgradePackage Executing trigger Finish Old loader information and old persistent data are cleaned up. Old programs are also UpgradePackage
removed.
UpgradePackage Executing trigger Initiate New programs are created, and old programs are prepared for being taken out of operation. UpgradePackage
UpgradePackage Executing trigger Preload Software that is preloadable is preloaded on device boards. UpgradePackage
The purpose is to restore the unit's HW and SW. A limited HW test is performed as a part of
the restart.