New AR:
History | States | Assignment | Timetracking
Add Attachment
AR Text Search | More | CARES Home
Assistance Request 1-5755928
Customer Ticket N/A
Description
Outage No
Severity 1
Priority 1
Sub-Type Software
Category Software
Internal Yes
Assignment Events
Ask Alcatel-Lucent
Product
Product 9353 WMS
Version LR14.2.W
Product Location
Site Abu Dhabi AE - Alcatel-Lucent MENA JLT-
Contact
Name Karim IBRAHIM ABD EL NABY
Dates
Occurred 02-Jun-2015 14:38 Time now 29-Aug-2015 10:48
(GMT+4)
Entitlement
Agreement 242895 (OXIA 627085)
People
Owner TSCd-WLS-WCDMA-IN : achowdar
Submitter arutkows
Description
Attachments
[empty]
2. 02-Jun-2015 15:04
mohmadi
Update to Current Summary: June 2: Awaiting Receive Log Files / Technical
Info
From: owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
Cc: INDIA-WCDMA-UTRAN-BE
Hi Karim,
Wanted to know what is the impact on PS KPI at present and when it started,
how
much Is the degradation? I tried calling you but was not able to reach you.
Can you please share KPI reports and RNC logcollection and RNC health
check.
/home/wcdma/Etisalat_UAE/1-5755928
Can you please share more details on it. And if we can reduce the severity
to
Major?
As from the description :
You observed the below alarms @ the same time of degradation on both
RNC231,
RNC235 but RNC231 dont have any impact, we had an activity yesterday on
the
WMS for installation of hot fix patch related to WCE at the same time and
we need
know if any relation between them and why only one RNC impacted not both?
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
5. 03-Jun-2015 13:10
mohmadi
Hello Mohamdi,
@/home/wcdma/Etisalat_UAE/AR1-5755928
PROBLEM IMPACT:
EXPECTED RESULTS:
- RC of this issue
We observed the below alarms @ the same time of degradation on both RNC231,
RNC235
but RNC231 dont have any impact, we had an activity yesterday on the WMS
for
installation of hot fix patch related to WCE at the same time and we need
know if
any relation between them and why only one RNC impacted not both?
Thanks,
--
BR,
Karim Ibrahim
Hello Mohamdi
Any update?
Thanks,
--
BR,
Karim Ibrahim
Hi Karim,
I checked the PPC log during that time but could not see any alarm in RNC
related
userid = mdmadmin
role =
remoteTcpPort = 34619
Id: 100C113
userid = mdmadmin
role =
remoteTcpPort = 56607
Did you had a check from WMS side as both RNC were impacted during that
time.
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
From: owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
IBRAHIM
Importance: High
Hello Mohamdi,
From the logs you can see the below, the Porv file changed , which means
that the
CP/OMU did auto reset or something which the same indication of the alarms
which
appeared @ 3:09am,,
If you check the description of the alarms you will see that it related to
RNC
supervision, and if the supervision not come , OMU reset will be done auto
or
manually and we dont take any action on the RNC at this time
Please check deeply on the logs to correlate these alarms.. and find a
clear RC
Id: 100C117
Id: 100C118
Id: 100C119
Thanks,
--
BR,
Karim Ibrahim
Hi Karim,
But why both RNC impacted at same time, so do you have idea from WMS side
any
Also please upload RNC logcollection and Healthcheck for other RNC, let me
check
in it.
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
From: owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
IBRAHIM
Hello Mohamdi
From the KPIS, only RNC235 is impacted.. check below the graphs , however
both of
them have loss of supervision at the same time due to our action on the WMS
for
hot fix implementation, Please not we have also 2 WCE RNCs on the same WMS
and
not affected.
Thanks,
--
BR,
Karim Ibrahim
Hi Karim,
As informed earlier, But from present Logs no clue could be found during
that time
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
Update to Current Summary: June 4: No related info found from Logs. Shared
info
Hi Mohamdi
Thanks,
--
BR,
Karim Ibrahim
From: owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
Hi Karim,
RC could not be determined as no info was found in logs during that time.
You can observe the RNC and let us know if similar issue is observed again.
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
(Ritesh)** CTR **
Importance: High
Hello Mohamdi
Is it RF condition?, are there any relation with WMS patch?, how can we
secure
Thanks,
--
BR,
Karim Ibrahim
(Ritesh)** CTR **
Hello Mohamdi
Thanks,
--
BR,
Karim Ibrahim
(Ritesh)** CTR **
Hi Karim,
Yes, As for RC we need to wait for re-occurrence as present logs did not
gave any
much info.
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
(Ritesh)** CTR **
Importance: High
Dear Mohamdi
Please escalate this AR, we cannot wait till the issue happened again and
we will
Thanks,
--
BR,
Karim Ibrahim
(Ritesh)** CTR **
Hi Karim,
It seems that you require RC even though logs have no info and you want us
to
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
(Ritesh)** CTR **
Hello Mohamdi,
May the L3 support will required more logs to find the RC,
Thanks,
--
BR,
Karim Ibrahim
1. Detailed Description
It was observed the below alarms at the same time of degradation on both
RNC231,
RNC235. But RNC231 dont have any impact, They had an activity on same
night on
the WMS for installation of hot fix patch related to WCE at the same time
and
need know if
any relation between them and why only one RNC impacted not both?
Or Is there any relation of RF condition?, are there any relation with WMS
patch?,
how can we secure the RNC to dont have the same issue in future?!
Directory : /home/wcdma/Etisalat_UAE/AR1-5755928
As above.
3. All the steps taken before the issue observed by the engineer, who
reported the
AR
N/A
From the PPC log during that time but could not see any alarm in RNC
related to
Hardware issue or any process issue.Also Healthcheck found ok.
Id: 100C112
userid = mdmadmin
role =
remoteTcpPort = 34619
Id: 100C113
userid = mdmadmin
role =
remoteTcpPort = 56607
5. Current Status
7. Attachments
Escalation Note
Cc: INDIA-WCDMA-UTRAN-BE
Hello Paul,
Directory : /home/wcdma/Etisalat_UAE/AR1-5755928
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
TEC Update:
==========
I guess the issue here is the bad KPI for Hour3 on june 2nd 2015.
i extracted the raw counters for RNC235 and it seems the 15 min interval
counter
and even some counters are = zero and when you do the summation for the 4
quaters
ex: RAB.SuccEstab.PS.Sum
Events
RAB.SuccEstab.PS.Sum 03:00
Events
RNC235 13243
issue might be related to issue seen before in LR14.2 and issue was related
to
issue seen before in LR14.2 and issue was related to counters corrupted
files on
Cc: INDIA-WCDMA-WMS-NPO-BE
Hello Christophe,
SW Version: LR14.2.W
Customer: Emirates Telecommunications Corporation
1. Detailed Description
It was observed the below alarms at the same time of degradation on both
RNC231,
RNC235. But RNC231 don't have any impact, They had an activity on same
night on
the WMS for installation of hot fix patch related to WCE at the same time
and
need know if any relation between them and why only one RNC impacted not
both?
Or Is there any relation of RF condition?, are there any relation with WMS
patch?,
how can we secure the RNC to don't have the same issue in future?!
As above.
3. All the steps taken before the issue observed by the engineer, who
reported
the AR
N/A
N/A
5. Current Status
o Critical.
7. Attachments
N/A
I guess the issue here is the bad KPI for Hour3 on june 2nd 2015.
i extracted the raw counters for RNC235 and it seems the 15 min interval
counter
and even some counters are = zero and when you do the summation for the 4
quaters
ex: RAB.SuccEstab.PS.Sum
Events
RAB.SuccEstab.PS.Sum 03:00
Events
RNC235 13243
issue might be related to issue seen before in LR14.2 and issue was related
to
-----Original Message-----
From: owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
This AR has been escalated to OAM TEC for further investigation, we will
update
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
-----Original Message-----
Hi Karim,
TEC has checked and analyzed that the issue here is the bad KPI for Hour3
on june
2nd 2015. After extracting the raw counters for RNC235 and it seems the 15
min
interval counter of 3:15 are corrupted on wms. A lot of Cnode counters are
"counterUnfound" and even some counters are = zero and when you do the
summation
for the 4 quarters it is less than the value hourly counter ex:
RAB.SuccEstab.PS.Sum
Events
RAB.SuccEstab.PS.Sum 03:00
Events
RNC235 13243
This Issue might be related to issue seen before in LR14.2 and issue was
related
So routing AR to OAM Team to get further checks on it, and OAM person Mr.
Ajay
will keep you updated on it.
Thanks,
Mohmadi Cutlerywala,
Mobile:+91 9870327804.
About the the WMS bug traked by AR 1-5662780 / AR 1-5669684 fix tracked by
CR
01545832:
1) Signature:
in file /opt/nortel/logs/utran/FMK_PM_server-20023.tra*
2) Workaround
So far the problem has been seen only after a restart of WMS. Also the
problem
observation data for less than a minute and no loss of supervision. The
exact
commands are:
/opt/nortel/shell/sysmgt/wam_stoponeapp.sh pmgt_utran_gpo_server
/opt/nortel/shell/sysmgt/wam_startoneapp.sh pmgt_utran_gpo_server
If I read correctly the description of the issue seen on June the 2th, a
WMS
restart was performed few time before. WMS s/wrestart is both the trigger
and the
- I do not know if there are still some issue. This could be checked
looking for
- concerning the problem seen on June the 2th, it is probably too late to
find
/opt/nortel/logs/utran/FMK_PM_server-20023.tra*
-----Original Message-----
To: CHOWDARY, Ajay (Ajay)** CTR **; CUTLERYWALA, Mohmadi (Mohmadi)** CTR
**;
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Telecommunications Corporation /// Sudden PS CDR on RNC235
Hi
FYI attached the release note containing the latest hot fix applied o live
WMS for
Best Regards
-----Original Message-----
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Can you pls provide the below mentioned files for further investigation
/opt/nortel/logs/utran/FMK_PM_server-20023.tra*
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
Update to Current Summary: June 10: Logs Awaited from field team
Update to Current Summary: June 10: Logs provided to TEC, Analysis awaited
30. 10-Jun-2015 13:31 ALCATEL-LUCENT PROPRIETARY
achowdar
(Ajay)** CTR **
Subject: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Didier,
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; AMAYO, EFOSA (EFOSA);
CHOWDARY,
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; CUTLERYWALA, Mohmadi (Mohmadi)** CTR
**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Karim,
Full RCA is still not known but as per the latest TEC feedback:
1) Signature:
in file /opt/nortel/logs/utran/FMK_PM_server-20023.tra*
2) Workaround
So far the problem has been seen only after a restart of WMS. Also the
problem
observation data for less than a minute and no loss of supervision. The
exact
commands are:
/opt/nortel/shell/sysmgt/wam_stoponeapp.sh pmgt_utran_gpo_server
/opt/nortel/shell/sysmgt/wam_startoneapp.sh pmgt_utran_gpo_server
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
(Ajay)** CTR **
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; CUTLERYWALA, Mohmadi (Mohmadi)** CTR
**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Nilanjan
Ok, we will proceed, but first, Please tell us whats the issue?! Which is
known
and seen with other customer?!, do you have the RC? Can you share with us.
Thanks,
--
BR,
Karim Ibrahim
To: AMAYO, EFOSA (EFOSA); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **;
CHOWDARY,
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; CUTLERYWALA, Mohmadi (Mohmadi)** CTR
**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Karim,
The impact is no more treatment of observation data for less than a minute
and no
loss of supervision
Please go ahead with the WA. It is a known problem with this know WA to be
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; CHOWDARY, Ajay (Ajay)**
CTR **;
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; CUTLERYWALA, Mohmadi (Mohmadi)** CTR
**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Ajay
Efosa
+971507533570 - UAE
+2348058097463 - Nigeria
To: CHOWDARY, Ajay (Ajay)** CTR **; CHATTERJEE, Nilanjan (Nilanjan)** CTR
**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Ajay,
Please elaborate whats the required and excepting result from this
command,
Please note the issue appeared again on the same RNC today 8.15am.
Thanks,
--
BR,
Karim Ibrahim
hello didier,
Here, we dont habe this case, the KPIs degraded @ only one RNC, for a very
short
period then its stable, happened 2 times today and last 2 June,
How we can confirm its the same issue?!, is it from logs we have the same
errors,
- Once the service has the problem it will affect randomly Cnode obs.
There is no
identified pattern no frequence
- The problem may disappear after a restart (again a restart can be the
trigger)
In fact there are so many errors that it fills up all the FMK_PM_server-
20023.tra*
files. It means previous occurrences are generally not more visible in this
log
/opt/nortel/data/utran/observation/stats/<date>/RNCCN-<RNCname> is
generally
the obs 14h00-14:15 and also the XML file is small compared to files before
and
- If we check the size of the XML file size for the 4 RNC since the
beginning of
the year, we can see clearly that the size for RNC 231 and 235 is not
stable since
end of April. There were some restart of the gpo service at this moment.
As XML
files are zipped so the size does not always reflect the real size of the
file,
but sudden change of size is a good marker of the bug. Look at the attached
graphs
which give the size of XML file for each RNC since January.
Conclusion
- We have the signature and sudden change of XML file size. I have no
doubt we are
by CR 01545832
the same workaround several times before GPO service restart in good shape.
I
would recommend to do the stop/start, wait for one or two hours and check
in
messages the same workaround should be done again until there is no more
error for
few hours/days.
RNC321 for the obs 14h00-14:15 and also the XML file is small compared to
files
before and after (971120 bytes instead of usually about 2300000 bytes.
- If we check the size of the XML file size for the 4 RNC since
the
beginning of the year, we can see clearly that the size for RNC 231 and 235
is not
stable since end of April. There were some restart of the gpo service at
this
moment. As XML files are zipped so the size does not always reflect the
real size
of the file, but sudden change of size is a good marker of the bug. Look
at the
attached graphs which give the size of XML file for each RNC since January.
- Once the service has the problem it will affect randomly Cnode
obs.
There is no identified pattern no frequence
So yes as per the above investigation done by TEC yes it is for sure same
issue as
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
From: owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
CUTLERYWALA, Mohmadi (Mohmadi)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR
**;
(Nilanjan)** CTR **
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Karim,
We have checked and found no error in these logs. We don't have any
confirmation
on permanent fix part, will update you once we hear from TEC.
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
To: CHOWDARY, Ajay (Ajay)** CTR **; CHATTERJEE, Nilanjan (Nilanjan)** CTR
**
CUTLERYWALA, Mohmadi (Mohmadi)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR
**;
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Importance: High
Dears,
Thanks,
--
BR,
Karim Ibrahim
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; WAGDY MANSOUR, AYMAN
(AYMAN)**
CTR **
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Karim,
No error of "out of bound" observed after applying workaround. Pls keep it
under
observation.
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
CHRISTOPHE (CHRISTOPHE)
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hi Didier,
After applying the workaround we didn't found this error again, any finding
or any
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
To: CHATTERJEE, Nilanjan (Nilanjan)** CTR **; CHOWDARY, Ajay (Ajay)** CTR
**
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hello,
The RCA package will be provided by R&D guys. I expect to have it this
week.
Update to Current Summary: June 25th Design has found the root cause, and
is
Update to Current Summary: June 29th Design has found the root cause, and
is
To: CHATTERJEE, Nilanjan (Nilanjan)** CTR **; CHOWDARY, Ajay (Ajay)** CTR
**
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hello,
The RCA package will be provided by R&D guys. I expect to have it this
week.
The issue occurs with the combination of 9370 and 9771 XDR PM file
processing.
The information required for mediation is required to be separately
maintained for
9370 and WCE because the set of counters are different between them. Let us
call
In order to get the correct applicable mediation context for 9370 and WCE,
thread
A common thread specific key is used between 9370 and WCE threads. The
value which
is bound to the key is the applicable mediation context for the thread.
The issue of out of bound exception occurs while processing XDR files of
9370
because there is a bug due to which the thread processing the 9370 files
retrieves
the mediation context for WCE instead of mediation context for 9370. This
causes
the particular localization due to which the size of the processed XML
files is
Solution:
WCE threads. Thus, the relevant mediation context is retrieved for the
The hotfix built from base LR14.2 EP5 has been verified by ISS.
Update to Current Summary: June 30th RCA package delivered, Hot fix will be
available in Wk29
Update to Current Summary: 2nd July : RCA package delivered, Hot fix will
be
available in Wk29
Update to Current Summary: 6th July : RCA package delivered, Hot fix will
be
available in Wk29
available in Wk29
Update to Current Summary: 16th July : RCA package delivered, Hot fix will
be
available in Wk29
@DL_FR_PUB_MoAD-GPS-OAM-Fr
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Can any one of you please let me know if the fix is applied anywhere else?
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Telecommunications Corporation /// Sudden PS CDR on RNC235
Bonjour Didier,
Indeed there was an issue with my calendar. Now I have corrected it. Thanks
for
pointing. :
Customer has enquired whether this patch is installed somewhere else. Can
you
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
To: CHATTERJEE, Nilanjan (Nilanjan)** CTR **; CHOWDARY, Ajay (Ajay)** CTR
**
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
AR-1-5662780- LR14.2W. FMK_PM Out of bound exception for RNC CNode GPO)
Didier
Objet : RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hello Didier,
Though the delivery target was Wk29 ie next week. I see it is showing ALED.
Can I
BR
NILANJAN CHATTERJEE
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
To: CHATTERJEE, Nilanjan (Nilanjan)** CTR **; CHOWDARY, Ajay (Ajay)** CTR
**
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hello,
Yes this is the same problem, the same RCA. But the AR mentioned in the
slides is
Didier
Objet : RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
To: CHATTERJEE, Nilanjan (Nilanjan)** CTR **; CHOWDARY, Ajay (Ajay)** CTR
**
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hello,
The RCA package will be provided by R&D guys. I expect to have it this
week.
Objet : RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Hello Didier,
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
CHRISTOPHE (CHRISTOPHE)
Subject: RE: Escalated: // AR 1-5755928 /// Critical /// 9353 WMS ///
Emirates
Telecommunications Corporation /// Sudden PS CDR on RNC235
Hello,
I do not know yet when an official delivery will available for customers.
I'll let
Didier
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; CHOWDARY, Ajay (Ajay)**
CTR **
EFOSA (EFOSA)
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
This fix is delivered last week to solve the "out of bound" issues wherever
it is
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
To: CHOWDARY, Ajay (Ajay)** CTR **; CHATTERJEE, Nilanjan (Nilanjan)** CTR
**
EFOSA (EFOSA)
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Nilnjan
BR,
Karim
+971 563544568
-----Original Message-----
[nilanjan.chatterjee@alcatel-lucent.com]
[ajay.chowdary@alcatel-lucent.com]
[Mahmoud.Khedr@alcatel-lucent.com]; INDIA-WCDMA-WMS-NPO-BE
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Karim,
AR-1-5662780- LR14.2W. FMK_PM Out of bound exception for RNC CNode GPO).
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
From: owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; CHOWDARY, Ajay (Ajay)**
CTR **
EFOSA (EFOSA)
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Karim,
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Ajay,Nilanjan,
Thanks,
--
BR,
Karim Ibrahim
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Thanks, and please keep us updated once the hotfix is ready and verified,
Thanks,
--
BR,
Karim Ibrahim
To: CHOWDARY, Ajay (Ajay)** CTR **; IBRAHIM ABD EL NABY, Karim (Karim)**
CTR **
CUTLERYWALA, Mohmadi (Mohmadi)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR
**;
(Nilanjan)** CTR **
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Karim,
Pls find the RCA package and permanent fix delivery plan attached.
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
From: owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
CUTLERYWALA, Mohmadi (Mohmadi)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR
**;
(Nilanjan)** CTR **
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
We have checked and found no error in these logs. We don't have any
confirmation
on permanent fix part, will update you once we hear from TEC.
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
Update to Current Summary: 22th July : RCA package & Hot fix delivered. As
per
Update to Current Summary: 22th July : RCA package & Hot fix delivered. As
per
local team's request enquiring TEC if fix is installed anywhere else
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Ayman,
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
To: CHOWDARY, Ajay (Ajay)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Ajay
Note: ETC is already running WMS LR14.2 EP3.3 (EP3 with hit fix for wce)
thanks
Best Regards
To: MERAD, ABDESSAMAD (ABDESSAMAD); CHOWDARY, Ajay (Ajay)** CTR **; WAGDY
MANSOUR,
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Merad,
R&D did their testing in LAB & released for field installation.
BR
NILANJAN CHATTERJEE
INDIA
On-NET:2758-8716
T:+91-22-66798716
M:+91-9820820019
Nilanjan.Chatterjee@alcatel-lucent.com
Update to Current Summary: 29th July : RCA package & Hot fix delivered. As
per
Update to Current Summary: 30th July : RCA package & Hot fix delivered. As
per
To: CHATTERJEE, Nilanjan (Nilanjan)** CTR **; CHOWDARY, Ajay (Ajay)** CTR
**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
I understand from your feedback that EP5 is tested only in R&D lab and not
tested in any live network,so etislat uae will be first off customer for
this load
( LR14.2 EP5),Hence we will need to secure WMS GPS support during the
action for
We will plan for EP5 installation (intra upgrade) shortly and keep you
updated
Best Regards,
Ayman Wagdy
Alcatel-Lucent U.A.E
E-mail: Ayman.Wagdy@alcatel-lucent.com
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Ayman,
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
T:+91-40-30894009
M:+91-9000008493
Update to Current Summary: 7th Aug : RCA package & Hot fix
delivered.Feedback
awaited
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; WAGDY MANSOUR, AYMAN
(AYMAN)**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Karim,
However you can open a new AR if you face any problem while implementing.
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
On-NET:2779-4009
Update to Current Summary: 10th Aug : RCA package & Hot fix
delivered.Feedback
To: CHOWDARY, Ajay (Ajay)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hello Ajay
I already replied below that we need to wait till we apply the upgrade and
patch,
Thanks,
BR,
Karim Ibrahim
Update to Current Summary: 13th Aug : RCA package & Hot fix
delivered.Feedback
From: owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; WAGDY MANSOUR, AYMAN
(AYMAN)**
Subject: RE: // AR 1-5755928 /// Critical /// 9353 WMS /// Emirates
Hi Karim,
I understand, when is the upgrade planed?
However you can open a new AR if you face any problem while implementing.
Regards
N AJAY CHOWDARY
ALCATEL-LUCENT
INDIA
From: owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-wms-npo-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
IBRAHIM
To: CHOWDARY, Ajay (Ajay)** CTR **; WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
Hello Ajay
Thanks,
BR,
Karim Ibrahim
Add to log
Resolution
Analysis from Design:
The issue occurs with the combination of 9370 and 9771 XDR PM file
processing.
9370 and WCE because the set of counters are different between them. Let us
call
In order to get the correct applicable mediation context for 9370 and WCE,
thread
is bound to the key is the applicable mediation context for the thread.
The issue of out of bound exception occurs while processing XDR files of
9370
because there is a bug due to which the thread processing the 9370 files
retrieves
the mediation context for WCE instead of mediation context for 9370. This
causes
the particular localization due to which the size of the processed XML
files is
Solution:
WCE threads. Thus, the relevant mediation context is retrieved for the
The hotfix built from base LR14.2 EP5 has been verified by ISS.
Latest update: