AR96

New AR: View AR | AR without Proprietary

History | States | Assignment | TimetrackingAdd Attachment

AR Text Search | More | CARES HomeAssistance Request 1-5542978

Customer Ticket N/A

Short KPIs degrdation after unlock the IUR link between RNC231&

Description H// RNC206

Current Fix delivered to load LR15.3

Summary

State Closed : Solution/Service Provided

Outage No

Severity 1

Priority 3

Service Request Remote Technical Support

Request Type Support

Sub-Type RCA

Category Software

Sub-Category Software Defect

Internal Yes

Assignment Events

Ask Alcatel-Lucent

Product

Product 9370 RNC

Version LR13.3.W

No Change Request is linked to this AR

Product Location

Site ETISALAT ABU DHABI

Instance 9370RNC-Etisalat : In Service

Site Company Emirates Telecommunications Corporation

City Abu Dhabi

Country United Arab Emirates

Contact

Name Karim IBRAHIM ABD EL NABY

Company Alcatel-Lucent : Open on behalf of Customer

Phone 20 127 109 0616 Email [email protected]

Request Method Email-Eng

Additional +971 56 354 4568

Contact Info

Dates

Occurred 19-Jan-2015 16:45 Time now 29-Aug-2015 13:07 (GMT+4)

Reported 19-Jan-2015 16:45 AR Created 19-Jan-2015 16:48

Service Start 19-Jan-2015 16:45

Next Customer Contact 26-Jul-2015 02:00

Responded 19-Jan-2015 16:53 Respond Target 19-Jan-2015 17:15 SA - Calculated

Restored 21-Jan-2015 18:00 Restore Target 22-Jan-2015 00:37 SA - Calculated

Resolved 30-Jun-2015 14:33 Resolve Target 23-Jul-2015 19:37 SA - Calculated

Targets for Restore & Resolve were extended by 155 days

to account for Pending time

Closed 30-Jun-2015 14:33

Last Modified 30-Jun-2015 14:33 Modified By rories

Entitlement

Agreement 242895 (OXIA 627085)

Covered Service TS 24x7 (Gold, Wireless Mobile Access)

Script This request is entitled to service.

People

Owner TSCr-MoA-WCDMA-SK : rories

Assignee TSCr-MoA-WCDMA-SK : rories

Copy To rories

Referred 1 NorP-WLS-WCDMA-vGlobal : rories

Referred 2 TEC-MoA-WCDMA_RNC-FR : lcostema

Resolve Group TEC-MoA-WCDMA_RNC-FR

Submitter lnowak

Description

Attachments

[empty]

Showing Investigation and Proprietary logs together in time order Show separately

Investigation Log and Proprietary Log

1. 19-Jan-2015 16:48 ALCATEL-LUCENT PROPRIETARY lnowak

called requestor PI provided

2. 19-Jan-2015 16:53 rjankovs

Update to Current Summary: WiP RTSC

3. 19-Jan-2015 16:55 rjankovs

Update to Current Summary: Reassigning to Assignment queue

4. 19-Jan-2015 19:00 rories

From: RIES, Robert (Robert)

Sent: Monday, January 19, 2015 3:59 PM

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **

Subject: AR 1-5542978 KPIs degrdation after unlock the IUR link between

RNC231& H RNC206

Hi Karim

Last info we have from Taher is that after extension of missing IPflows was IUR/8

unlocked today morning and link was stable and no TMU resets were observed (see at

attached mail).

So this ticket is opened following the degradation of next two counters you found

after unlocking of IUR/8 ?:

VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue #1629_0

VS.RadioLinkFailureIndication.InvalidCmSettings #18_1

Could you please confirm ?

In this case we will need also xls KPI outputs of all observed degraded counters.

Once you confirm/provide it, I route this ticket to the TPS L3. We have to ask

them, if degradation of above two counters is consequence of incorrect "QAAL2

Release Confirm" message, or not.

Thanks

Best Regards

Robert Ries

5. 21-Jan-2015 02:47 rories

From: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **


To: RIES, Robert (Robert)

Cc: OKASHA, TAHER (TAHER); BERIDY, AHMED (AHMED); REDA, RAMY (RAMY); ELHAKIM,

Mohamed (Mohamed)** CTR **; NABIL GEORGES, MARTIN (MARTIN)** CTR **; ABDEL-HALIM,

SAYED (SAYED); ZAHABI, RAMSEY (RAMSEY); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;

KHEDR, MAHMOUD (MAHMOUD)

Subject: RE: AR 1-5542978 KPIs degrdation after unlock the IUR link between

RNC231& H RNC206

Hi Ries,

I confirm , the below KPIs degrdation appeared after the IUR unlocked today morning.

As Taher said till now no TMU reset alarms appeared while we are telnet to the RNC.

Please tell me which XLS reports required so you can escalate.

Thanks to treat it as urgent as the customer requests KPIs reports on hourly based.

--

BR

Karim Ibrahim

6. 21-Jan-2015 02:47 rories


Sent: Tuesday, January 20, 2015 8:35 AM




SAYED (SAYED); ZAHABI, RAMSEY (RAMSEY); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;

KHEDR, MAHMOUD (MAHMOUD)


RNC231& H RNC206

Hi Karim

OK, thanks.

Provide please xls reports of both counters #1629 & #18 on 15 min basis at

least from the 16th Jan up to now.

And I think, there will be also useful CTG with UPOS to see which causes are as

main triggers. So provide please next:

1) run CTG + CFT + UPOS (duration=30 min; callType=select the call types, which

are impacted).

Template to be used – attached (/opt/nortel/data/utran/CTSessionTemplates):

HeavyTroubleShooting+CFT+UPOS.tpl

UPOS files to be uploaded to the RNC – attached (/sfs2/share/config):

TMU.upos.CTact8

TMU.upos.Ctdeact

Note: if there are already UPOS files present on the RNC, overwrite the old ones

with the ones I attached to this mail.

2) When CTG above is finished collect please RNCLogCollection (full mode)

immediately after that.

3) Please collect IMT log of at least one NodeB on impacted RNC.

Thank you

Best Regards

Robert Ries

7. 21-Jan-2015 02:48 rories

From: ZAHABI, RAMSEY (RAMSEY)

Sent: Tuesday, January 20, 2015 1:07 PM

To: RIES, Robert (Robert); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **



SAYED (SAYED); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; KHEDR, MAHMOUD (MAHMOUD)


RNC231& H RNC206

Hello Robert,

The trace logs have been uploaded to ftp server at

/srv/data202256/data/server/Traces/from_france/ETISALAT_UAE/TRACE_LOGS/CTG_CFT_IMT

_RNCLogCollection_20012015.rar

SFTP://172.25.80.47

user: ftraces

password: Elv24trf

Br,

Ramsey Zahabi

8. 21-Jan-2015 02:51 rories



To: ZAHABI, RAMSEY (RAMSEY); RIES, Robert (Robert)





RNC231& H RNC206

Hi Reis,

Attached also the required KPIs reports, and a detailed KPIs report for the RNC

behavior after the activity,

Waiting your feedback

Thanks,

--

BR,

Karim

Update to Current Summary: Escalated to TPS L3

9. 21-Jan-2015 02:51 ALCATEL-LUCENT PROPRIETARY rories

Dear TEC

This internal ticket is connected to already solved outage ticket AR 1-5531112

where customer ETC (UAE) found a lot of TMU resets in RNC231. Investigation found

problem on IuR towards Huawei RNC206. Customer blocked

this IuR and extend number of IPIf on Iub/8 between these both RNCs. After

unlocking of IuR there were no more TMU reset occurred. However customer found

starting degradation of few other counters. You can see his

KPI summary in the file "Etisalat UAE

-RNC231-OutageAndIurImpact_AfterUnlocking-report.pptx". This ticket he opened as

he complain for two most degraded counters:

VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue #1629_0

VS.RadioLinkFailureIndication.InvalidCmSettings #18_1

I asked customer to perform CTG + CFT + UPOS (set for pegging of 1629_0, 1629_3,

1629_4, 18_1, 18_8), but only one case of 1629_0 was captured => cause

radioNetwork = invalid-rab-parameters-value (0x13, 19)

However from 25823 calls captured by this CTG, were 10349 dropped with RANAP cause

value "Radio Connection with UE Lost" with NBAP values "Synchronization failure",

or "Transport resource unavailable".

In AR 1-5531112 Nabil Menjaoui found in the PPC alarms/debug a lot of alarms

"Failed to find the best Bwpool". Also in RNCLogCollection captured after this CTG

there are a lot of same alarms:

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:16.023 Tbm 3000 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc TbmNF::receiveEstablishRequest - Msg_traceKey: 0x80104133 Failed to find the best

Bwpool [NOCR]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:16.223 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc sendReleaseConfirm - Msg_traceKey: 0x80104133 FcHistory CID failure cause FINAL

VALUE: 19

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:16.423 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc TRM_IF_Estreq_t Message Received

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:16.623 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc Msg_traceKey[x080104133] userType[3] userId[1] IfId[42] rbType[0] cnDomainInd[1]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:16.823 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc Msg_traceKey[x080104133] qosInfo:trmTc[4] callpQos[1] thp[NONE] arpPl[1]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:17.023 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc isA2ea FALSE

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:17.223 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc Msg_traceKey[x080104133] [uplink:downlink] --maximumBitRate[8682:8288]

equivalentBitRate[4341:4172] equivalentSSSARSduSz[159:152] pcCACType[0]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:17.423 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc Msg_traceKey[x080104133] plmnId [36:244:32]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:17.623 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:07.489 tbmNFqaal2.cc CAC History: [00042:00001:00007:IP] [NOCR]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:17.823 Tbm 3000 0x00000001 202 Jan 20 2015 11:07:08.331 tbmNFqaal2.cc TbmNF::receiveEstablishRequest - Msg_traceKey: 0x80101072 Failed to find the best

Bwpool [NOCR]

DBG Lp/2 Ap/0 ; 2015-01-20 11:07:18.023 Tbm 1767 0x00000001 202 Jan 20 2015 11:07:08.331 tbmNFqaal2.cc sendReleaseConfirm - Msg_traceKey: 0x80101072 FcHistory CID failure cause FINAL

VALUE: 19

Please can you ivestigate the probem and tell us:

a) What is a root cause of the both above mentioned counters degradation ? Is it

consequence of incorrect “QAAL2 Release Confirm” message, or not ?

b) Fix delivery plan for this issue

Please note that also AR 1-5542978 is connected to this issue = TMU resets - CR

1434789 created in design.

Apropriate logs you can find on the server 172.25.80.47 in:

/srv/data202256/data/server/Traces/from_france/ETISALAT_UAE/TRACE_LOGS/

CTG_CFT_IMT_RNCLogCollection_20012015.rar

Etisalat UAE -RNC231-OutageAndIurImpact_AfterUnlocking-report.pptx

IUR_RNC231_KPIs_required_reports.rar

If you need some additional information, logs pls let us know.

Thank you and Best Regards

Robert Ries

Time Tracking Entry Added - IR01-TSA3

10. 21-Jan-2015 18:01 rories

Hello

Scope of this ticket is KPI degradation, so in this case Restore = Resolve.

As there will be Target Restore Date set to today at 9:37PM and there is still

investigation in TEC ongoing, I set Restore to avoid of run over it`s time.

Thank you

Robert Ries

11. 26-Jan-2015 12:29 ALCATEL-LUCENT PROPRIETARY lcostema

There seems to be a configuration issue in FDDCell/primary scrambling codes

between neighbor RNCs. TMU blogs CallP from 20/01/2015 12:20:16 to 20/01/2015

14:57:26 show 25324 occurrences of the following type of alarm:

20/01/2015 12:20:18.018 num:000b1846 ue_call_compCellsList_uti.cc.1920

[0x7d570000] UeCallp @ TMU_1(Lp/3,Ap/1) (PERM): UECALLP : UE_CALL :

uecall_buildTempNeighInfo_from_contribTab_cmpType1 (0x8000da00)"WARNING: Cell

{rncId,cId,primaryScramblinCode}={206,24844,412}, sponsored by contributor active

set cell {rncId,cId}={206,24836}, is ignored due to same primaryScramblingCode as

cell {rncId,cId,primaryScramblinCode}={231,24844,412} when computing neighbourhood

for primary cell {rncId,cId}={231,25136}."

The message above shows that RNC Id is not a discriminator for same FDDCell Id +

same scrambling code being added in the active set. Please plan to review primary

scrambling codes list on FDDCell from different RNC.

In attachment is the excel file for duplicate psc distribution - 146 FDDCell are

concerned in the counted period - main impacted RNC are RNC206 and RNC231, but 3

others show few occurrences (205, 215 and 216).

12. 26-Jan-2015 19:28 rories


Sent: Wednesday, January 21, 2015 2:54 AM

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; ZAHABI, RAMSEY (RAMSEY)





RNC231& H RNC206

Hi Karim

Thanks for data provided.

Ticket was escalated to the TPS L3. Once I have any output, I let you know.

Best Regards

Robert Ries

13. 26-Jan-2015 19:28 rories


Sent: Sunday, January 25, 2015 6:31 AM




SAYED (SAYED); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; KHEDR, MAHMOUD (MAHMOUD);

ZAHABI, RAMSEY (RAMSEY)


RNC231& H RNC206

Hello Robert,

Any update from TPS about this AR?

Thanks,

--

BR,

Karim

14. 26-Jan-2015 19:28 rories


Sent: Monday, January 26, 2015 12:09 AM







RNC231& H RNC206

Hello Karim

I asked TPS for update while ago. I am waiting for answer.

Best Regards

Robert Ries

15. 26-Jan-2015 19:28 rories









RNC231& H RNC206

Hello Karim

Next is TEC`s output:

There seems to be a configuration issue in FDDCell/primary scrambling codes

between neighbor RNCs. TMU blogs CallP from 20/01/2015 12:20:16 to 20/01/2015

14:57:26 show 25324 occurrences in total of the following type of alarm:

========================

20/01/2015 12:20:18.018 num:000b1846 ue_call_compCellsList_uti.cc.1920

[0x7d570000] UeCallp @ TMU_1(Lp/3,Ap/1) (PERM): UECALLP : UE_CALL :

uecall_buildTempNeighInfo_from_contribTab_cmpType1 (0x8000da00)"WARNING: Cell

{rncId,cId,primaryScramblinCode}={206,24844,412}, sponsored by contributor active

set cell {rncId,cId}={206,24836}, is ignored due to same primaryScramblingCode as

cell {rncId,cId,primaryScramblinCode}={231,24844,412} when computing neighbourhood

for primary cell {rncId,cId}={231,25136}."

========================

The above message shows that RNC Id is not a discriminator for same FDDCell Id +

same scrambling code being added in the active set.

There is an excel file attached to CARES. It shows duplicate psc distributions -

146 FDDCells are concerned in the counted period - main impacted RNCs are RNC206

and RNC231, but 3 others shows few occurrences (205, 215 and 216) as well.

AP:

Please plan to review primary scrambling codes list on FDDCell from different RNCs.

Best Regards

Robert Ries

16. 28-Jan-2015 18:35 rories

From: BERIDY, AHMED (AHMED)



Cc: OKASHA, TAHER (TAHER); REDA, RAMY (RAMY); ELHAKIM, Mohamed (Mohamed)** CTR **;

NABIL GEORGES, MARTIN (MARTIN)** CTR **; ABDEL-HALIM, SAYED (SAYED); WAGDY

MANSOUR, AYMAN (AYMAN)** CTR **; KHEDR, MAHMOUD (MAHMOUD); ZAHABI, RAMSEY (RAMSEY)


RNC231& H RNC206

HI Robert,

Thanks for the feedback we will review the PSC plan & come back to you.

Best Regards,

Ahmed BERIDY

17. 28-Jan-2015 18:35 rories








RNC231& H RNC206

Hi Robert ,

Please find the attached file including all the duplicated cells from our side

& H// side , also be informed that all cell from H// side are locked after the

swap , so the sites still created on their system but locked .

So I don't think this is the RC of the problem.

Best Regards,

Ahmed BERIDY

18. 28-Jan-2015 18:36 rories


Sent: Wednesday, January 28, 2015 12:56 PM




MANSOUR, AYMAN (AYMAN)** CTR **; KHEDR, MAHMOUD (MAHMOUD); ZAHABI, RAMSEY

(RAMSEY); BERIDY, AHMED (AHMED)


RNC231& H RNC206

Hello Karim

Yes, we agree, this is not a root cause. But TEC requested to correct this PSC

issue, because while it is present, the TMU logs are filling up very quickly,

which could lead to hiding more obvious alarms. So that's why it should be useful

to clear any alarms connected to unmatched FDDcell/psc.

Therefore if it is possible, arrange appropriate corrections, please.

Best Regards

Robert Ries

19. 28-Jan-2015 18:36 rories


Sent: Wednesday, January 28, 2015 11:29 AM






RNC231& H RNC206

Hi Robert ,

Ok , we will request from H// to clear it from there side , but please we to find

the RC.

Best Regards,

Ahmed BERIDY

20. 02-Feb-2015 13:49 rories


Sent: Sunday, February 01, 2015 9:49 AM







RNC231& H RNC206

Hello Reis,

Confirmed will delete the cells from H// side, Please update about the AP after

they delete the cells so you can continue your investigation.

Thanks,

--

BR,

Karim

21. 02-Feb-2015 13:49 rories


Sent: Monday, February 02, 2015 11:17 AM







RNC231& H RNC206

Thank you Karim

I let you know, if TEC will need another logs.

Best Regards

Robert Ries

22. 02-Feb-2015 13:49 rories


Sent: Monday, February 02, 2015 9:40 AM






RNC231& H RNC206

Dears,

Confirmed deleted from H// side.

Best Regards,

Ahmed BERIDY

23. 02-Feb-2015 13:49 rories


Sent: Monday, February 02, 2015 1:41 PM

To: BERIDY, AHMED (AHMED); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **





RNC231& H RNC206

Hi Ahmed, Karim

Could you please perform again AP, you did last time ?:

1) run CTG + CFT + UPOS (duration=30 min; callType=select the call types, which

are impacted).

Template to be used: HeavyTroubleShooting+CFT+UPOS.tpl

UPOS files to be uploaded to the RNC:

TMU.upos.CTact8

TMU.upos.Ctdeact

Note: if there are already UPOS files present on the RNC, overwrite the old ones

with the ones from last time.

2) When CTG above is finished collect please RNCLogCollection (full mode)

immediately after that.

3) Please collect IMT log of at least one NodeB on impacted RNC.

We hope the ppc_debug will be cleaner now.

Thank you

Best Regards

Robert Ries

24. 09-Feb-2015 15:51 rories


Sent: Tuesday, February 03, 2015 12:52 PM





(RAMSEY); BERIDY, AHMED (AHMED); MERAD, ABDESSAMAD (ABDESSAMAD)


RNC231& H RNC206

Hello Reis,

I applied the AP again, all traces @

/srv/data202256/data/server/Traces/from_france/ETISALAT_UAE/AR 1-5542978

Waiting your feedback,

Thanks,

--

BR,

Karim

25. 09-Feb-2015 15:51 ALCATEL-LUCENT PROPRIETARY rories


26. 09-Feb-2015 15:53 rories


Sent: Sunday, February 08, 2015 12:46 PM





(RAMSEY); BERIDY, AHMED (AHMED); MERAD, ABDESSAMAD (ABDESSAMAD); ALI, YASSER

(YASSER)** CTR **


RNC231& H RNC206

Hello Reis,

Any Update please?

Thanks,

--

BR,

Karim

27. 09-Feb-2015 15:53 rories


Sent: Monday, February 09, 2015 12:49 PM






(YASSER)** CTR **


RNC231& H RNC206

Hi Karim

TEC answered today, that they still analyze and meanwhile no updates.

Best Regards

Robert Ries

28. 10-Feb-2015 13:25 ALCATEL-LUCENT PROPRIETARY lcostema

ALU RNC does not and will not support SRB 6.8; it accepts RNSAP radio link setup

for SRB3.4 at transmission time 10msec (srb13.6) and 40msec.

In the attached file "CT_messages_parsing.xls", out of 880 tracekeys sorted per 1

or more "RNSAP Radio Link Setup Failure", almost all are due to SRB6.8

Message extract:

...

---------transportBlockSize = 0x94 (148)

---------mode

----------notApplicable = NULL (0x0, 0)

--------semi_staticPart

---------transmissionTime = msec-20 (0x1, 1)

...

CR 1440113 (IUR:IOT: RNC ALU should refuse SRB 6.8) is open for RNC to directly

reject SRB6.8 when requested.

29. 10-Feb-2015 15:57 rories


Sent: Tuesday, February 10, 2015 12:53 PM






(YASSER)** CTR **


RNC231& H RNC206

Hi Karim

KPI degradation is caused by non standard 3GPP specification from the Huawei side.

They RNC uses towards our RNC message exchange over the SRB6,8 kb/s which is not

3GPP compliant.

ALU RNC is 3GPP compliant, therefore it does not and will not support SRB6,8. It

accepts RNSAP radio link setup for SRB3,4 at transmission time 10msec (SRB13,6)

and 40msec.

You can see list of calls from CT in the attached file "CT_messages_parsing.xls".

There are filtered messages "RNSAP Radio Link Setup Failure", which almost all of

them causes call fail due to SRB6,8. In this CT sample are by SRB issue caused 880

calls out of 1698 in total.

Message extract: ...

---------transportBlockSize = 0x94 (148)

---------mode

----------notApplicable = NULL (0x0, 0)

--------semi_staticPart

---------transmissionTime = msec-20 (0x1, 1) ...

There was opened CR 1440113 in design (IUR:IOT: RNC ALU should refuse SRB6,8). It

is opened for RNC to directly reject SRB6,8 when requested.

I will inform you once fix will be implemented.

Best Regards

Robert Ries

30. 16-Feb-2015 12:10 ALCATEL-LUCENT PROPRIETARY rories


Sent: Thursday, February 12, 2015 10:10 AM

To: COSTEMALLE, LUC (LUC)

Cc: RIGAULT, LAURENT (LAURENT)


RNC231& H RNC206

Hi Luc

Just question regarding fix for this issue - do you have any info when it will be

available ? Or at least any info regarding actual progress of CR 1440113 ...

Thanks

Best Regards

Robert Ries

31. 20-Feb-2015 18:04 ALCATEL-LUCENT PROPRIETARY lcostema

Hi Robert, R&D are currently working on it, but there is no fix date/release

planned yet.

For info, disabling feature "enhanced IUR RAB configuration" (setting

isEnhancedIurRabConfigEnabled to FALSE) could be a workaround but note that it

would impact some of the HSDPA and EDCH RAB matching on IUR side; so, eventually

just for test....

BR,

32. 06-Mar-2015 22:04 rories


Sent: Thursday, February 12, 2015 8:01 AM






(YASSER)** CTR **


RNC231& H RNC206

Hello Reis.

Thanks for your feedback, any news about the fix for this issye?.

Thanks,

--

BR,

Karim

33. 06-Mar-2015 22:05 rories


Sent: Friday, March 06, 2015 7:04 PM



NABIL GEORGES, Martin (Martin); ABDEL-HALIM, SAYED (SAYED); WAGDY MANSOUR, AYMAN

(AYMAN)** CTR **; KHEDR, MAHMOUD (MAHMOUD); ZAHABI, RAMSEY (RAMSEY); BERIDY, AHMED

(AHMED); MERAD, ABDESSAMAD (ABDESSAMAD); ALI, YASSER (YASSER)** CTR **


RNC231& H RNC206

Hi Karim

Fix based on opened CR 1440113 in R&D has no date/release planned yet. R&D

is currently working on it.

One question - did you disable the feature "enhanced IUR RAB configuration" ?

(setting isEnhancedIurRabConfigEnabled to FALSE).

And if yes, is there any impact to some of the HSDPA and EDCH RAB matching on IUR

? We talked about it in another AR 1-5532074, which is connected with the same

issue as this AR.

Thanks

Best Regards

Robert Ries

34. 16-Mar-2015 14:05 rories


Sent: Monday, March 16, 2015 11:03 AM



RNC231& H RNC206

Hi Karim

Kindly did you disable the feature "enhanced IUR RAB configuration" ? (setting

isEnhancedIurRabConfigEnabled to FALSE).

And if yes, is there any impact to some of the HSDPA and EDCH RAB matching on IUR ?

Regarding CR 1440113 opened in R&D still no update.

Thanks

Best Regards

Robert Ries

35. 07-Apr-2015 10:29 ALCATEL-LUCENT PROPRIETARY rories


Sent: Tuesday, April 07, 2015 8:29 AM




RNC231& H RNC206

Hi Luc

Kindly any news regarding CR 1440113 ?

In DCT portal I can see release version LR15.3 with status - Ready to Verify.

Could you check if it is final state, please ?

Thanks

Best Regards

Robert Ries

36. 05-May-2015 11:29 rories


Sent: Tuesday, May 05, 2015 9:28 AM



RNC231& H RNC206

Hi Karim

Kindly did you disable the feature "enhanced IUR RAB configuration" ? (setting

isEnhancedIurRabConfigEnabled to FALSE).

And if yes, is there any impact to some of the HSDPA and EDCH RAB matching on IUR ?

Regarding CR 1440113 opened in R&D still no update.

Thanks

Best Regards

Robert Ries

37. 12-May-2015 15:26 rories


Sent: Tuesday, May 05, 2015 9:49 AM



RNC231& H RNC206

Hello Reis,

I'll check and back t you,

Thanks,

--

BR,

Karim

38. 12-May-2015 15:31 rories


Sent: Tuesday, May 12, 2015 1:31 PM



RNC231& H RNC206

Hello Karim

Kindly did you check ?

Friday I will go to vacation, so I`d like to know, what state is this issue now.

Or may I close the ticket ?

Thank you

Best Regards

Robert Ries

39. 15-Jun-2015 13:29 ALCATEL-LUCENT PROPRIETARY rories


Sent: Monday, June 15, 2015 11:28 AM




RNC231& H RNC206

Hi Luc

What is the status of CR 1440113, please ? May I provide to the customer info,

that fix is in LR15.3 definitely ?

I would like to close this ticket as the Target Resolve Date is already missed.

Thank you

Best Regards

Robert Ries


De : RIGAULT, LAURENT (LAURENT)

Envoyé : lundi 15 juin 2015 11:33

À : RIES, Robert (Robert); COSTEMALLE, LUC (LUC)

Objet : RE: AR 1-5542978 KPIs degrdation after unlock the IUR link between

RNC231& H RNC206

Hi Robert,

I am in CC but answer to help if Luc has not time for that.

CR delivered in LR15.3 starting with RIF30070F1352_RLF30070F1352

RCA info corresponding to that delivery

ALU RNC has to refuse SRB 6.8 configuration without allocating any resources

Regards

Laurent.


41. 25-Jun-2015 13:18 rories


Sent: Thursday, June 25, 2015 11:17 AM



RNC231& H RNC206

Hello Karim

Final statement from R&D:

Fix of this issue is delivered to load LR15.3 (starting with

RIF30070F1352_RLF30070F1352)

RCA info corresponding to that delivery:

ALU RNC has to refuse SRB 6.8 configuration without allocating any resources

As fix for this issue is known and implemented, may I close the ticket ?

Thank you

Best Regards

Robert Ries



43. 30-Jun-2015 14:31 rories


Sent: Sunday, June 28, 2015 7:51 AM



RNC231& H RNC206

Hello Reis,

Thanks, you can close the AR.

Thanks,

--

BR,

Karim Ibrahim



Sent: Sunday, June 28, 2015 7:51 AM



RNC231& H RNC206

Hello Reis,

Thanks, you can close the AR.

Thanks,

--

BR,

Karim Ibrahim

AR96

Documents

Transcript of AR96