RG10(S14)+GEMINI Case Sharing_20100827

7/27/2019 RG10(S14)+GEMINI Case Sharing_20100827

1/51

Soc Classification level

Presentation / Author / Date1 Nokia Siemens Networks

RG10(S14)+GEMINI Case Summary2010.08.27

By SSO CTM


2/51


2 Nokia Siemens Networks

RG10(S14)+GEMINI Cases List1/ pending

Pending case NA04734007--After WAU25 installed and restarted in CFBSC2, some BTS have 7725 alarm and users

NA04733900--A problem about 2770 alarm NA04736737--(BSC3i S14)BSC240 random accessrailurerate. (

NA04733083 -- (EXPO)(BSC3i S14)BSC238 low randomaccesrate)

NA04731498-- BSC242 appears high drop call rate randomly on problematic BTSs.

NA04738170 -- Several BTS site down after PCU2_Eextention NA04738708--BTS no GPRS traffic (Sleep Cell) NA04740365--some BTS+ site ever happened 7604 alarm (combiner) NA04753982--After S14 PP5.0-1 +WAU21, DL throughput decreased 50%. NA04754396GeminiBTS kept BL-RST state. NA04760146--Gemini-BTS is low AMR traffic statistic.

NA04752315TR call drop forBTSplus. NA04762385BrokenAbisPCM recovery, BTS still can not work.(new) NA04762436TRX fault cause high drop call rate.(new) NA04762449TRX fault, cause TBF establish low success.(new) NA04764016Time of GPRS progress is more 0.2s than S12.(new)

to case list2

to case list3


3/51



RG10(S14)+GEMINI Cases List2/ resolved

Resolved case

NA04731119BCSU change status to TE-EX, causing all calls drop. NA047302142770alarmappearedonPCU. NA04726915TRXbecameBL-SYSafterBCSUforcedswitchover. NA04714041BCSU CPUloadishigh. NA04694591MTCfailure. NA04709569LowUL TBFsuccessfulrate. NA04711400LowUL TBFsuccessfulrate. NA04712562sometypephonecantregisternetwork. NA04711855BSCdowngradecausedTCSMrepeatedrestarting

NA04711952TCSMlostconfigurationafterS14 upgrade. NA04704762GPRSservicelostafterBCSUexpansion. NA04730877Can not upload measurement report. NA04728403-- There is crosstalk phenomenon NA04711224--

After cutover, some Flexi BTS have no GPRS traffic, need to disable/enable GENA to solve the problem

NA04734754--Intra MSS inter BSC Handover failed from BTS with A53 to BTS with A50. NA04745368--TCH allocation rate is drop. NA04738703--Paging coordination feature problem.

NA04751771--Call connected no sound. NA04755071Flexi-BTSis without edge information in TRX with EEI command. NA04732625--Mobile F668 cannotrecieveMMS sometimes. NA04745442 --BCSUsswitch by Alarm 1178.

to case list1

to case list3


4/51



RG10(S14)+GEMINI Cases List3/GEMINI resolved

Resolved GEMINI case NA04667515some cells have TR drop.

NA04684172CU failure problem-7606 alarm.

NA04698551EDGE is unstable.

NA04626625high call drop rate. NA04720718TRXs not recovered after PCMB interruption.

NA04635141 OMC can monitor FlexiBTS, but fail to monitor BTS+.

NA04735905 EDGE enabled, BTS+ can not work.

NA04747564--Gemini BTS appeared a lot of 32835alarm. NA04738012--Carrier frequency is hang. (updated)

NA04751668--BTS TRX missing problem. (updated)

GEMINI INFO

to case list1

to case list2


5/51



NA04734007--After WAU25 installed and restarted in

CFBSC2, some BTS have 7725 alarm and users can not useGPRS

Customer: Anhui MCC

Case open date: 2010-6-29

HW: Flexi BSC

SW: S14 PP4.2

Case activities

2010-6-29 to 30: Tried to collect necessary logs but failed 2010-6-29 to 30: Tried to reproduce problem offline but failed

Current Status Waiting for problem happen again to collect valuable logs

Pending CaseBack to case list1


6/51



NA04733900--A problem about 2770 alarm

Customer: Anhui MCC

Case open date: 2010-6-29

HW: Flexi BSC

SW: S14 PP4.2Problem Description:

- one BTS had low GPRS traffic then did BCSU switchover manually, afterBCSU switchover,3 PCUs appeared 2770 alarms at the same time

Case activities

2010-6-29 to 30: Tried to collect necessary logs but failed 2010-6-29 to 30: Tried to reproduce problem offline but failed

Current Status

Waiting for problem happen again to collect valuable logs

Pending Case Back to case list1


7/51



NA04736737 --(BSC3i S14)BSC240 randomaccess failure rate.

Customer: Shanghai CUCSW Version S14+MP3.0

Problem Description:- (BSC3i S14)BSC240 random access failure rate

- same phenomenon: NA04733083 -- (EXPO)(BSC3iS14)BSC238 low random access rate

Solution: under investigation.

Workaround: no workaround.



8/51



NA04731498 -- BSC242 appears high dropcall rate randomly on problematic BTSs.


Problem Description:- BSC242 appears high drop call rate randomly on

problematic BTSs.





9/51



NA04738170 -- Several BTS site downafter PCU2_E extention

Customer: Helongjiang CUCSW Version S14+PP3.1Problem Description:

- Several BTS site down after PCU2_E extention.





10/51



NA04738708 --BTS no GPRS traffic(Sleep Cell)

Customer:ANHUI MCC

SW Version

S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1

Problem Description:- (Flexi BSC s14) BTS no GPRS traffic (Sleep Cell)/Some BTS with

with alarm 7725, some BTS without alarm 7725.


Workaround: no workaround



11/51



NA04740365--some BTS+ site ever

happened 7604 alarm (combiner)

Customer: Inner Mongolia MCCSW Version S14+PP4.2/Gemini BTS Load-0960

Problem Description:- some BTS+ site ever happened 7604 alarm (combiner problem) detected from

flexi-BSC, after replaced the combiner, the TRx remaining in blocked status (7208)from flexi-BSC side; the problem recovered till power-off/on the BTSE;

Solution: load 0971 solve this problem and the scheduled delivery date is 06/Aug/10.


Pending Case/Gemini Back to case list1


12/51



NA04753982--After S14 PP5.0-1 +WAU21, DL

throughput decreased 50%

Customer: CMCC Fujian

SW Version S14+PP5.01+WAU21

Problem Description:- BSC1822 did the S14 upgrade with PP5.0-1+WAU21 on the early morning of

5th,Aug,and after upgrade,from KPI result found that (E)GPRS throughput dropped50%. during upgrade,also upgrade BTS SW to CMX 7.1-0, EP3.3-0,CX 7.82-0





13/51



NA04754396Gemini BTS kept BL-RST state

Customer: CMCC Hubei

SW Version S14+PP4.2/Gemini BTS load0960

Problem Description:- There were 4 Gemini sites couldn't go to work state after cutover from

Ex-N BSC to FlexiBSCThe BCF ID is 72,167,256 and 259.The TRXs alwaysstay on BL-RST state, and alarm 7797 was appeared.





14/51



NA04760146Gemini-BTS is low AMR trafficstatistic

Customer: CMCC Xinjiang

SW Version S14+PP4.2/Gemini BTS load0962Problem Description:

- Gemini-BTS is low AMR traffic statistic, aftercutover from ex-siemens BSC to Flexi-BSC





15/51



NA04752315TR call drop for BTSplus.

Customer: CMCC Hubei


- TR call drop for BTSplus.





16/51



NA04762385Broken Abis PCM recovery, BTS still

can not work

Customer: CUC Shanghai

SW Version S14+PP4.2

Problem Description:- Broken Abis PCM recovery, while BTS kept BL status.





17/51



NA04762436TRX fault cause high drop call rate

Customer: CMCC Inner Mongolia


- when use SEG for EGSM & GSM ,some TRX alwaysfault cause high drop call rate.





18/51



NA04762449TRX fault, cause TBF establish low

success.

Customer: CMCC Shanghai


Problem Description:- TRX fault, cause TBF establish low success.





19/51



NA04764016Time of GPRS progress is more 0.2s

than S12.

Customer: CMCC Fujian

SW Version S14+MP5.0+PP5.01

Problem Description:- Time of GPRS progress is more 0.2s than S12.





20/51



NA04731119BCSU change status to TE-EX,

causing all calls drop.

Customer: ANHUI MCCSW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1

Problem Description:- 2770 alarms appear on one of working BCSU. The affected BCSU didn'tissue "2693 WO-EX UNIT FAULTY" alarm and didn't successfully autoswitchover to spare UNIT, instead the BCSU directly change status to TE-EX, causing all calls drop and site out of service for several minutes.

The faults can be simulated by removing 1 PCU(no GPRS resouce) ofworking BCSU.

Solution: Correction is available in MP6.0.

Workaround: S14+PP4.2+WAU29

Resolved Case Back to case list2


21/51



NA04730214 2770 alarm appeared on PCU.


Problem Description:- 2770 alarm appeared on PCU

Solution: S14 MP6.0. the root cause is that PCU2 reset occurred when thePCU2 RL process tried to access that invalid memory.

Workaround: S14+PP4.2+WAU29



22/51



NA04726915 TRX became BL-SYSafter BCSU forced switchover.Customer: ANHUI MCCSW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1Problem Description:

- TRXs stay BL-SYS after BCSU forced switchover- such problem exists when use both ECCCH and BB hopping

Solution: S14 MP6.0 or S14WAU26. fault has been localized to RNWrecovery module GUPDAT. During forced BCSU switchover GUPDAT triesto set hopping ON to BCCH TRX as well(which is illegal functionality). Afther

this BCCH TRX hopping setting fails, GUPDAT leaves other TRXs withECCCH config to blocked state as well.

Workaround: 1. Disable ECCCH or 2. Disable BB hopping



23/51



NA04714041 BCSU CPU load ishigh.Customer: Anhui MCC,SW Version S14+PP4.2

Problem Description:- The load of BCSU CPU is very high, more than 90%

Solution: S14 MP6.0. (The functionality of handling incoming mobile identity

records from PCU is optimized so that CPU load is decreased (verified inPerformance laboratory environment). Additionally, overload protection wasimplemented for paging coordination feature.). Or S14+PP4.2+WAU24

Workaround: disable the paging coordination feature



24/51



NA04694591 MTC failure.

Customer: Shanghai MCC,SW Version S14+PP4.2

Problem Description:- normally after activating ECCCH feature for 3 or 5 hours or even oneday, then can not make M.T call under the two cells

Solution: correction plan CX7 PP2.2 or CX7 MP3.0. From the debugtraces, it was found that paging command is scheduled at wrong time by the

telecom SW. The issue can happen only with sectors where CCCHparameter MFR equal 3,5,6,7 or 9. Workaround is to use 2,4 or 8.

Workaround: 1.disable ECCCH feature or 2. use MFR=2,4 or 8.



25/51



NA04709569 Low UL TBF successful

rate.

Customer: ANHUI MCCSW Version S14+PP4.2Problem Description:

- low UL TBF successful rate- segment configuration, both master and slave BTS use BB hopping

Solution: same case with BMCC case NA04711400, correction isPP5.01+WAU21.

Workaround: turn off the hopping in the slave BTS



26/51



NA04711400 Low UL TBF successful

rate.Customer: BEIJING MCC,SW Version S14+PP4.2

Problem Description:- some type mobile phone ( such as SAMSUNG E398/motoV8/SAGEM

OT498 ) couldn't GPRS attach under Segment Cell- segment configuration, both master and slave BTS use RF hopping

Solution: correction module is already ready and tested successful. This

correction S14WAU21 will be installed on top of MP5.0 or EP5.1.

Workaround: turn off the hopping in the slave BTS



27/51



NA04712562 some type phone cant

register network.Customer: Anhui MCC,

SW Version S14+PP4.2; BTS SW:EP3 MP3.0Problem Description:

- Some type mobile Phone can not register network, such as CoolPad

- Location update not successful in Flexi EDGE BTS / Flexi BSC withCoolpad phone which supports TD-SCDMA and GSM

- Location update is successful in Gemini BTS ( BTS plus) /Flexi BSC

- Ext CCCH feature is active in the network

Solution: EP3 PP3.1. The pre-released EP3 PP3.1 is already tested inAnhuiMCC, it works for this case.

Workaround: 1.no TD- SCDMA neighbors defined or 2. Disable ECCCHfeature



28/51



NA04711855BSC downgrade caused

TCSM repeated restarting

Customer: BEIJING MCC,SW Version S14+PP4.2

Problem Description:- After BSC degraded from S14 MP4.2 to S12 CD10.0,TCSM repeatedrestarting

Solution: Go to TCSM service terminal and execute ZGC command to set

default configuration, then restart the TCSM again, No correction for thiscase. This solution is already verified in live network and works successfully.



29/51



NA04711952TCSM lost configuration

after S14 upgrade.

Customer: BEIJING MCC,SW Version S14+PP4.2

Problem Description:- TCSM lost configuration (Frame Alignment Mode) after

S14 upgrade

Solution: S14 MP5.0



30/51



NA04704762GPRS service lost after

BCSU expansion.Customer: Heilongjiang CUCSW Version S14+EP3.2Problem Description:

- after BCSU4 or BCSU5 expansion, the GPRS service is lost underBCSU0

Solution: S14 MP5.0. This is due to the fact that before 19.61-0 versionRC0 did not support the activating of BCSU-unit after BSC restart. In theprevious versions (19.59-0 used here) RC0 initialized it's internal

BCSU/PCU connection table based right after the BSC restart and if a BCSUwas not found at that time, then it would not be "included" in the table indexcalculations at any point after that.

Workaround: restart BSC



31/51



NA04730877Can not upload

measurement report.Customer: Shanghai MCCSW Version S14+PP4.2

Problem Description:- Abis D-channel measurement report cannot be generated. (The

logical file ABISDCHAB connected to wrong place. It must be connected toVDS-2.) Configuration problem.

Solution: Modify the logical file ABISDCHAB to connect to VDS-2 with MMLcommand:

IIS::ABISDCHAB,PRI:DEV=WDU-SB:DEV=VDS-2;




32/51



NA04728403 -- There is crosstalkphenomenon

Customer: Helongjiang CUCSW Version S14+PP3.2Problem Description:

- There is crosstalk phenomenon in telephoneconversation after restart Flexi BSC.

Solution: S14 MP5.0 solve this fault.

Workaround: restart BSC&TCSM.



33/51



NA04711224--After cutover, some Flexi BTS have

no GPRS traffic.


Problem Description:- After cutover, some Flexi BTS have no GPRS traffic.

(The problem only happened while LAC did not change duringcutover, we will collect necessary logs if it happens again in

next cutover )

Solution: disconnect Gb link and disable&enable Flexi-BTSGENA .



34/51



NA04734754 --Intra MSS inter BSC Handover failed

from BTS with A53 to BTS with A50.

Customer: Yunnan MCCSW Version S14 SW, PP4.2Problem Description:

- Intra MSS inter BSC Handover from BTS with A53 function to BTSwith A50 function can not do successfully. (Handover from A5/3 or A5/1 to

A5/0 failed, enable A5/3, A5/1 and A5/0 in MSS, source BSC in S14, targetBSC in S12)

Solution: Missing ciphering setting mode IE in S12 in handover commandmessage from target BSC to source BSC. In S14, this IE included inhandover command message. Upgrade from S12 to S14 solve this problem.




35/51



NA04745368 --TCH allocation rate isdrop.


Problem Description:

- (BSC3i S14)TCH allocation rate is drop.

Solution: S14 MP6.0 provides correction on this issue.



36/51



NA04738703 --Paging coordinationfeature problem.

Customer:ANHUI MCCSW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1

Problem Description:- Paging coordination feature problem, MTC unsuccessful too high

under PS service.

Solution: S14+MP7.0+WAU35.




37/51



NA04751771--call connected no sound.

Customer: CUC Hebei

SW Version S14+PP4.2/Gemini BTS Load-0960Problem Description:

- call connected but no sound.

Solution: HW problem, replace defected TR3E PIUs.




38/51

Soc Classification level38 Nokia Siemens Networks

NA04755071Flexi-BTS is without edge

information in TRX with EEI command.

Customer: CMCC Beijing



- Flexi-BTS is without edge information in TRX with EEIcommand

Solution: NO fault. From S13 onwards, EDGE info is only displayed at theBCF level and not for each TRX. ZEEI: BCF=X;


R l d C


39/51


NA04732625--Mobile F668 cannot receive MMS

sometimes.

Case open date: 2010-6-29 Anhui MCC

HW: Flexi BSC

SW: S14 PP4.2


- Mobile F668 cannot receive MMS.

Solution: NO fault. We can not reproduce this problem again.


R l d C


40/51


NA04745442 --BCSUs switch by Alarm1178.

Customer:ANHUI MCCSW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1

Problem Description:- 3 FBSCs happened 1178 alarm on BCSU caused related BCSU

switch.

Solution:The correction is included in S14 MP6.0+WAU36 orCD7.0.




41/51


NA04667515some cells have TR drop.

Customer: Anhui MCC

SW Version S14+EP3.2; BTS+ SW:0947(GEMINI)

Problem Description:- Some cells have TR (transcoder failure) drop.

Solution: Gemini load 0961 was released to improve this problem.

Workaround: no workaround solution.

Case on GEMINI Back to case list3


42/51


NA04684172CU failure problem-7606

alarm.Customer: Heilongjiang CUC


Problem Description:- CU failure problem-7606 alarm- 34841-Error in downlink message

from COP/HIT

Solution: Gemini load 0962 correct this problem.

Workaround: Gemini load 0959.


C GEMINI B k li 3


43/51


NA04698551EDGE is unstable.

Customer: Anhui MCC



1.FTP with EDGE sometimes no flow control, download alwaysinterrupt.

2.FTP with GPRS is normal

3.no problem on FlexiBTS (one BTSplus was replaced by FlexiBTS,the edge problem disappeared).

4.both 0953 and 0956 have this problem, and 0947 does not have.

Solution: load 0960 provides the solution and has been verified in field.



C GEMINI B k t li t3


44/51


NA04626625high call drop rate.

Customer: Heilongjiang CUC


Problem Description:high call drop rate caused by handover access failure/ NY1*T3105

expire

Solution:

to Gemini BTS(BSC) EQM: NY1=35(default value is 5)

EHG: MIU=10s (default value is 3s)

to Gemini BTSE Set COBA:NAME=RACK:0/COBA:0,ALRMT2=3;





45/51


NA04720718TRXs not recovered after

PCMB interruption.

Customer: Telecom Italia S.p.A. (Mobile)

SW Version S14 cd 4.1 , BTS plus 9-60, flexi EP3 MP1.0

Problem Description:- the 3 trx are no more restored in their functioning unless a ZEFS of

150 and 170 are done.

Solution:

the new delivered load (09-64) solve the fault

Workaround: Lock/Unlock related BCF (ZEFS).




46/51


NA04635141OMC can monitor FlexiBTS,

but fail to monitor BTS+.

Customer: Shanghai MCC

SW Version S14 cd 3.0

Problem Description:- OMC can monitor FlexiBTS, but fail to monitor BTS+.

Solution:

to ex-N BTS, address of Q1 should be set to 4080, but BTS+ should be4001.

ZQWG:BCF=:TRE=1:4001;




47/51


NA04735905EDGE enabled, BTS+ can not

work.

Customer: Inner Mongolia MCC

SW Version S14 PP4.2/Gemini load 0960

Problem Description:- EDGE enabled, BTS+ can not work

Solution:

the max number of EDAP pools for BTSplus is not defined, only thetotal number of slave channels is specified per COBA type

COBA2P8: 48 channels => 12 TSL for all EDAP pools COBA4P12: 240 channels => 60 TSL for all EDAP pools;




48/51


NA04747564--Gemini BTS appeared alot of 32835 alarm

Customer: Hubei MCCSW Version S14+PP4.2/Gemini BTS Load-0960


- BTS appeared a lot of 32835 alarm.

Solution: HW problem, replace defective HW.





49/51


NA04738012--Carrier frequency ishang.

Customer: Inner Mongolia MCCSW Version S14+PP4.2/Gemini BTS Load-0960

Problem Description:- some TRX can not work when the EDGE is activated. TRX appeared

BL-DGN.

Solution: Gemini load 0974 solve TRX BL-DGN.





50/51


NA04751668--BTS TRX missing problem.

Customer: CUC HeilongjiangSW Version S14+EP3.2/Gemini BTS Load-0962


- Customer reported there were some TRXs missing andsame time presented 7606 alarm. After restarted BCF,The TRXrecovered.

Solution: Gemini load 0971 solve this problem.



GEMINI Notice Back to case list3


51/51

1. The number of TRX in BTSE rack is restricted from 48 to 32 in Geminifor BTSplus.

2. The max number of EDAP pools for BTSplus is not defined, only thetotal number of slave channels is specified per COBA type

COBA2P8: 48 channels => 12 TSL for all EDAP poolsCOBA4P12: 240 channels => 60 TSL for all EDAP pools

3. As BTSplus pre-handle HO and PC in Gemini as well in BR, so radiomeasurement report is not necessary in Abis uplink. While the defaultvalue of attribute IMREPS is 8 SACCH multiframe, to avoid LAPD uplinkoverload, please change value of IMREPS more than 50 SACCHmultiframe (ZEQM).

GEMINI Notice Back to case list3

Documents

RG10(S14)+GEMINI Case Sharing_20100827