Sei sulla pagina 1di 51

RG10(S14)+GEMINI Case Summary

2010.08.27 By SSO CTM

Soc Classification level 1 Nokia Siemens Networks

Presentation / Author / Date

RG10(S14)+GEMINI Cases List1/ pending


to case list2 to case list3
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 access railure rate. ( NA04733083 -- (EXPO)(BSC3i S14)BSC238 low random acces rate ) NA04731498 -- BSC242 appears high drop call rate randomly on problematic BTSs . NA04738170 -- Several BTS site down after PCU2_E extention 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%. NA04754396Gemini BTS kept BL-RST state. NA04760146--Gemini-BTS is low AMR traffic statistic. NA04752315TR call drop for BTSplus. NA04762385Broken Abis PCM 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)

Soc Classification level 2 Nokia Siemens Networks

RG10(S14)+GEMINI Cases List2/ resolved


Resolved case

to case list1 to case list3

NA04731119BCSU change status to TE-EX, causing all calls drop. NA04730214 2770 alarm appeared on PCU. NA04726915 TRX became BL-SYS after BCSU forced switchover. NA04714041 BCSU CPU load is high. NA04694591 MTC failure. NA04709569 Low UL TBF successful rate. NA04711400 Low UL TBF successful rate. NA04712562 some type phone cant register network. NA04711855BSC downgrade caused TCSM repeated restarting NA04711952TCSM lost configuration after S14 upgrade. NA04704762GPRS service lost after BCSU expansion. 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-BTS is without edge information in TRX with EEI command . NA04732625--Mobile F668 cannot recieve MMS sometimes. NA04745442 --BCSUs switch by Alarm 1178.

Soc Classification level 3 Nokia Siemens Networks

RG10(S14)+GEMINI Cases List3/GEMINI resolved


Resolved GEMINI case

to case list1 to case list2

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 32835 alarm.

NA04738012--Carrier frequency is hang. (updated) NA04751668--BTS TRX missing problem. (updated) GEMINI INFO
Soc Classification level 4 Nokia Siemens Networks

Pending Case

Back to case list1

NA04734007--After WAU25 installed and restarted in CFBSC2, some BTS have 7725 alarm and users can not use GPRS

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
Soc Classification level 5 Nokia Siemens Networks

Pending Case NA04733900--A problem about 2770 alarm


Customer: Anhui MCC Case open date: 2010-6-29 HW: Flexi BSC SW: S14 PP4.2 Problem Description:

Back to case list1

- one BTS had low GPRS traffic then did BCSU switchover manually, after BCSU 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
Soc Classification level 6 Nokia Siemens Networks

Pending Case

Back to case list1

NA04736737 --(BSC3i S14)BSC240 random access failure rate.


Customer: Shanghai CUC SW Version S14+MP3.0 Problem Description: - (BSC3i S14)BSC240 random access failure rate - same phenomenon: NA04733083 -- (EXPO)(BSC3i S14)BSC238 low random access rate Solution: under investigation. Workaround: no workaround.
Soc Classification level 7 Nokia Siemens Networks

Pending Case

Back to case list1

NA04731498 -- BSC242 appears high drop call rate randomly on problematic BTSs.
Customer: Shanghai CUC SW Version S14+MP3.0 Problem Description: - BSC242 appears high drop call rate randomly on problematic BTSs. Solution: under investigation. Workaround: no workaround.
Soc Classification level 8 Nokia Siemens Networks

Pending Case

Back to case list1

NA04738170 -- Several BTS site down after PCU2_E extention


Customer: Helongjiang CUC SW Version S14+PP3.1 Problem Description: - Several BTS site down after PCU2_E extention. Solution: under investigation. Workaround: no workaround.
Soc Classification level 9 Nokia Siemens Networks

Pending Case

Back to case list1

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. Solution: under investigation. Workaround: no workaround
Soc Classification level 10 Nokia Siemens Networks

Pending Case/Gemini

Back to case list1

NA04740365--some BTS+ site ever happened 7604 alarm (combiner)


Customer: Inner Mongolia MCC SW 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.

Workaround: no workaround.

Soc Classification level 11 Nokia Siemens Networks

Pending Case

Back to case list1

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 dropped 50%. during upgrade,also upgrade BTS SW to CMX 7.1-0, EP3.3-0,CX 7.82-0 Solution: under investigation. Workaround: no workaround.

Soc Classification level 12 Nokia Siemens Networks

Pending Case/Gemini

Back to case list1

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 always stay on BL-RST state, and alarm 7797 was appeared. Solution: under investigation. Workaround: no workaround.
Soc Classification level 13 Nokia Siemens Networks

Pending Case/Gemini

Back to case list1

NA04760146Gemini-BTS is low AMR traffic statistic


Customer: CMCC Xinjiang SW Version S14+PP4.2/Gemini BTS load0962 Problem Description: - Gemini-BTS is low AMR traffic statistic, after

cutover from ex-siemens BSC to Flexi-BSC


Solution: under investigation. Workaround: no workaround.
Soc Classification level 14 Nokia Siemens Networks

Pending Case/Gemini

Back to case list1

NA04752315TR call drop for BTSplus.


Customer: CMCC Hubei SW Version S14+PP4.2/Gemini BTS load0960 Problem Description: - TR call drop for BTSplus. Solution: under investigation. Workaround: no workaround.
Soc Classification level 15 Nokia Siemens Networks

Pending Case

Back to case list1

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. Solution: under investigation. Workaround: no workaround.
Soc Classification level 16 Nokia Siemens Networks

Pending Case/Gemini

Back to case list1

NA04762436TRX fault cause high drop call rate


Customer: CMCC Inner Mongolia SW Version S14+PP4.2/Gemini BTS load0960 Problem Description: - when use SEG for EGSM & GSM ,some TRX always fault cause high drop call rate. Solution: under investigation. Workaround: no workaround.
Soc Classification level 17 Nokia Siemens Networks

Pending Case

Back to case list1

NA04762449TRX fault, cause TBF establish low success.


Customer: CMCC Shanghai SW Version S14+PP4.2 Problem Description: - TRX fault, cause TBF establish low success. Solution: under investigation. Workaround: no workaround.
Soc Classification level 18 Nokia Siemens Networks

Pending Case

Back to case list1

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. Solution: under investigation. Workaround: no workaround.
Soc Classification level 19 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04731119BCSU change status to TE-EX, causing all calls drop.


Customer: ANHUI MCC SW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1 Problem Description: - 2770 alarms appear on one of working BCSU. The affected BCSU didn't issue "2693 WO-EX UNIT FAULTY" alarm and didn't successfully auto switchover to spare UNIT, instead the BCSU directly change status to TEEX, causing all calls drop and site out of service for several minutes. The faults can be simulated by removing 1 PCU(no GPRS resouce) of working BCSU. Solution: Correction is available in MP6.0. Workaround: S14+PP4.2+WAU29
Soc Classification level 20 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04730214 2770 alarm appeared on PCU.


Customer: ANHUI MCC SW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1 Problem Description: - 2770 alarm appeared on PCU Solution: S14 MP6.0. the root cause is that PCU2 reset occurred when the PCU2 RL process tried to access that invalid memory. Workaround: S14+PP4.2+WAU29

Soc Classification level 21 Nokia Siemens Networks

Resolved Case

Back to case list2

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

NA04726915 TRX became BL-SYS after BCSU forced switchover.

Problem 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 RNW recovery module GUPDAT. During forced BCSU switchover GUPDAT tries to set hopping ON to BCCH TRX as well(which is illegal functionality). Afther this BCCH TRX hopping setting fails, GUPDAT leaves other TRXs with ECCCH config to blocked state as well. Workaround: 1. Disable ECCCH or 2. Disable BB hopping

Soc Classification level 22 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04714041 BCSU CPU load is high.


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 in Performance laboratory environment). Additionally, overload protection was implemented for paging coordination feature.). Or S14+PP4.2+WAU24 Workaround: disable the paging coordination feature
Soc Classification level 23 Nokia Siemens Networks

Resolved Case

Back to case list2

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 one day, then can not make M.T call under the two cells Solution: correction plan CX7 PP2.2 or CX7 MP3.0. From the debug traces, it was found that paging command is scheduled at wrong time by the telecom SW. The issue can happen only with sectors where CCCH parameter 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.
Soc Classification level 24 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04709569 Low UL TBF successful rate.


Customer: ANHUI MCC SW Version S14+PP4.2 Problem Description: - low UL TBF successful rate - segment configuration, both master and slave BTS use BB hopping Solution: same case with BMCC case NA04711400, correction is PP5.01+WAU21. Workaround: turn off the hopping in the slave BTS

Soc Classification level 25 Nokia Siemens Networks

Resolved Case

Back to case list2

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

Soc Classification level 26 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04712562 some type phone cant register network.


Customer: Anhui MCC, SW Version S14+PP4.2; BTS SW:EP3 MP3.0 Problem Description: - Some type mobile Phone can not register network, such as CoolPad - Location update not successful in Flexi EDGE BTS / Flexi BSC with Coolpad 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 in AnhuiMCC, it works for this case. Workaround: 1.no TD- SCDMA neighbors defined or 2. Disable ECCCH feature
Soc Classification level 27 Nokia Siemens Networks

Resolved Case

Back to case list2

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 repeated restarting Solution: Go to TCSM service terminal and execute ZGC command to set default configuration, then restart the TCSM again, No correction for this case. This solution is already verified in live network and works successfully.

Soc Classification level 28 Nokia Siemens Networks

Resolved Case

Back to case list2

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

Soc Classification level 29 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04704762GPRS service lost after BCSU expansion.


Customer: Heilongjiang CUC SW Version S14+EP3.2 Problem Description: - after BCSU4 or BCSU5 expansion, the GPRS service is lost under BCSU0 Solution: S14 MP5.0. This is due to the fact that before 19.61-0 version RC0 did not support the activating of BCSU-unit after BSC restart. In the previous versions (19.59-0 used here) RC0 initialized it's internal BCSU/PCU connection table based right after the BSC restart and if a BCSU was not found at that time, then it would not be "included" in the table index calculations at any point after that. Workaround: restart BSC
Soc Classification level 30 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04730877Can not upload measurement report.


Customer: Shanghai MCC SW 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 to VDS-2.) Configuration problem. Solution: Modify the logical file ABISDCHAB to connect to VDS-2 with MML command: IIS::ABISDCHAB,PRI:DEV=WDU-SB:DEV=VDS-2; Workaround: no workaround
Soc Classification level 31 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04728403 -- There is crosstalk phenomenon


Customer: Helongjiang CUC SW Version S14+PP3.2 Problem Description: - There is crosstalk phenomenon in telephone conversation after restart Flexi BSC. Solution: S14 MP5.0 solve this fault. Workaround: restart BSC&TCSM.
Soc Classification level 32 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04711224--After cutover, some Flexi BTS have no GPRS traffic.


Customer: ANHUI MCC SW Version S14+PP4.2 BTS SW:FlexiBTS :EP3+PP3.1 Problem Description: - After cutover, some Flexi BTS have no GPRS traffic. (The problem only happened while LAC did not change during cutover, we will collect necessary logs if it happens again in next cutover ) Solution: disconnect Gb link and disable&enable Flexi-BTS GENA .
Soc Classification level 33 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04734754 --Intra MSS inter BSC Handover failed from BTS with A53 to BTS with A50.
Customer: Yunnan MCC SW Version S14 SW, PP4.2 Problem Description: - Intra MSS inter BSC Handover from BTS with A53 function to BTS with 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, target BSC in S12) Solution: Missing ciphering setting mode IE in S12 in handover command message from target BSC to source BSC. In S14, this IE included in handover command message. Upgrade from S12 to S14 solve this problem. Workaround: no workaround
Soc Classification level 34 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04745368 --TCH allocation rate is drop.


Customer: Shanghai CUC SW Version S14+MP3.0 Problem Description: - (BSC3i S14)TCH

allocation rate is drop.

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

Soc Classification level 35 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04738703 --Paging coordination feature problem.


Customer: ANHUI MCC SW 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. Workaround: no workaround.
Soc Classification level 36 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04751771--call connected no sound.


Customer: CUC Hebei SW Version S14+PP4.2/Gemini BTS Load-0960 Problem Description: - call connected

but no sound.

Solution: HW problem, replace defected TR3E PIUs. Workaround: no workaround.

Soc Classification level 37 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04755071Flexi-BTS is without edge information in TRX with EEI command.


Customer: CMCC Beijing SW Version S14+PP5.01 Problem Description: - Flexi-BTS is without

command

edge information in TRX with EEI

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

Soc Classification level 38 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04732625--Mobile F668 cannot receive MMS sometimes.


Case open date: 2010-6-29 HW: Flexi BSC SW: S14 PP4.2
Problem Description: - Mobile F668 cannot Anhui MCC

receive MMS.

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

Soc Classification level 39 Nokia Siemens Networks

Resolved Case

Back to case list2

NA04745442 --BCSUs switch by Alarm 1178.


Customer: ANHUI MCC SW 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 CD7.0.

correction is included in S14 MP6.0+WAU36 or

Workaround: no workaround.
Soc Classification level 40 Nokia Siemens Networks

Case on GEMINI

Back to case list3

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.

Soc Classification level 41 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04684172CU failure problem-7606 alarm.


Customer: Heilongjiang CUC SW Version S14+EP3.2; BTS+ SW:0953(GEMINI) 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.

Soc Classification level 42 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04698551EDGE is unstable.
Customer: Anhui MCC SW Version S14+EP3.2; BTS+ SW:0953(GEMINI) Problem Description: 1.FTP with EDGE sometimes no flow control, download always interrupt. 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. Workaround: no workaround solution.
Soc Classification level 43 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04626625high call drop rate.


Customer: Heilongjiang CUC SW Version S14+EP3.2; BTS+ SW:0947(GEMINI) 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; Workaround: no workaround solution.
Soc Classification level 44 Nokia Siemens Networks

Case on GEMINI

Back to case list3

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).
Soc Classification level 45 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04635141 OMC 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 be 4001. ZQWG:BCF=<bcf_id>:TRE=1:4001;

Soc Classification level 46 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04735905 EDGE 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 the total 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;
Soc Classification level 47 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04747564--Gemini BTS appeared a lot of 32835 alarm


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

a lot of 32835 alarm.

Solution: HW problem, replace defective HW. Workaround: no workaround.

Soc Classification level 48 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04738012--Carrier frequency is hang.


Customer: Inner Mongolia MCC SW 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. Workaround: no workaround.

Soc Classification level 49 Nokia Siemens Networks

Case on GEMINI

Back to case list3

NA04751668--BTS TRX missing problem.


Customer: CUC Heilongjiang SW Version S14+EP3.2/Gemini BTS Load-0962 Problem Description: - Customer reported

there were some TRXs missing and same time presented 7606 alarm. After restarted BCF,The TRX recovered.
Solution: Gemini load 0971 solve this problem. Workaround: no workaround.
Soc Classification level 50 Nokia Siemens Networks

GEMINI Notice

Back to case list3

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


for BTSplus.

2. The max number of EDAP pools for BTSplus is not defined, only the
total 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

3. As BTSplus pre-handle HO and PC in Gemini as well in BR, so radio

measurement report is not necessary in Abis uplink. While the default value of attribute IMREPS is 8 SACCH multiframe, to avoid LAPD uplink overload, please change value of IMREPS more than 50 SACCH multiframe (ZEQM).

Soc Classification level 51 Nokia Siemens Networks

Potrebbero piacerti anche