AR53

New AR:
View AR | AR without Proprietary

History | States | Assignment | Timetracking
Add Attachment
AR Text Search | More | CARES Home
Assistance Request 1-5692664

Customer Ticket N/A
Short
High rate of VSWR alarms that can be fixed only by MC-RRH
Description
replacement
Current
Aug 27: Provided all details, script, and explaination
Summary
awaiting customer feedback
State
Pending : Awaiting Receive Log Files / Technical Info
Outage
No
Severity
Priority
Service Request Remote Technical Support

Request Type
Support
Sub-Type
Configuration Assistance
Internal
Yes
Assignment Events
Ask Alcatel-Lucent
Product
Product
9926 DBS-WCDMA
Version
LR13.3.W
No Change Request is linked to this AR

Product Location
Site
ETISALAT ABU DHABI
Instance
9926DBS WCDMA-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
971 56 354 4568
Karim.Ibrahim@alcatel-lucent.com
Request Method
Email
Email-Eng
Dates
Occurred
(GMT+4)
22-Apr-2015 18:43
Time now
29-Aug-2015 11:19
Reported
22-Apr-2015 18:43
AR Created
22-Apr-2015 18:45
Service Start
22-Apr-2015 18:43
Next Customer Contact
10-Sep-2015 13:15
Responded
22-Apr-2015 18:45
SA - Calculated
Respond Target
22-Apr-2015 19:43
Restored
22-Apr-2015 20:30
SA - Calculated
Restore Target
26-Apr-2015 17:16
Resolved
-- --- ---SA - Calculated
Resolve Target
31-Aug-2015 16:08
Targets for Restore & Resolve have been extended by 46 hours

to account for Pending time
Closed
-- --- ----
Last Modified
27-Aug-2015 13:15
Modified By
shelends
Entitlement
Agreement
242895 (OXIA 627085)
Covered Service TS 24x7 (Gold, Wireless Mobile Access)

Script
This request is entitled to service.
People
Owner
TSCd-WLS-WCDMA-IN : shelends
Assignee
TSCd-WLS-WCDMA-IN : shelends
Referred 1
NorP-WLS-WCDMA-vGlobal : shelends
Referred 2
TEC-WLS-WCDMA-BTS : dpasha
Resolve Group
TEC-WLS-WCDMA-BTS
Submitter
mbednarz
Description
From: "IBRAHIM ABD EL NABY, Karim (Karim)** CTR **"
<karim.ibrahim@alcatel-lucent.com>
Sent: 2015-04-22 16:43:18
To: ALU Support <support@alcatel-lucent.com>
Cc: "KHEDR, MAHMOUD (MAHMOUD)" <Mahmoud.Khedr@alcatel-lucent.com>;"REDA,
RAMY (RAMY)" <ramy.reda@alcatel-lucent.com>;"ABDEL-HALIM, SAYED (SAYED)"
<Sayed.Abdel-Halim@alcatel-lucent.com>;3G_ALU_Integ_UAE
<3g_Alu_Integ_Uae@alcatel-lucent.com>;"MERAD, ABDESSAMAD (ABDESSAMAD)"
<abdessamad.merad@alcatel-lucent.com>;"BERIDY, AHMED (AHMED)"
<Ahmed.Beridy@alcatel-lucent.com>;"EL-MIDANY, AHMED (AHMED)"
<Ahmed.El-Midany@alcatel-lucent.com>
Subject: Etisalat UAE//High rate of VSWR alarms that can be fixed only by
MC-RRH
replacement
Hello,
PROBLEM DESCRIPTION:
High rate of VSWR alarms that can be fixed only by MC-RRH replacement
PROBLEM IMPACT:
Lot of RRH are replaced to solve this issue, lot of KPIS degradation and
outage,
EXPECTED RESULTS:
We suspect RRH calibration is not appropriate, We want confirmation of this

or RCA asap
We want to know how to update/perform RRH calibration on site? Is it

possible without the need of FW change
ARs CORRELATION:
Contact Surname
Contact Given Name
Contact Phone
Contact Company
Company
Karim
: Ibrahim
:+971 56 354 4568
: Alcatel-Lucent
Emirates Telecommunications Corporation
Contract Number
: OXIA 627085
Region
: EMEA
Country
: United Arab Emirates
City
: Abu Dhabi
Site
: ETISALAT ABU DHABI
Product Instance
Severity
: 9926 DBS-WCDMA
: 2
Priority
Product Version
Outage
Internal/External:
: 2
: L13.3.1
: No
:Internal
-Best Regards,
Karim Ibrahim
LTE/WCDMA Integration Professional
META WLS Access Network (GNE EMEA)

M(UAE): +
<https://mail.eu.alcatel-lucent.com/owa/redir.aspx?
C=30449991f54743fd85063b63258fd6f2&URL=https%3a%2f%2fmail.eu.alcatellucent.com%2fowa%2fUrlBlockedError.aspx>
971-56-354-4568
M(Egy): +
<https://mail.eu.alcatel-lucent.com/owa/redir.aspx?
C=30449991f54743fd85063b63258fd6f2&URL=https%3a%2f%2fmail.eu.alcatellucent.com%2fowa%2fUrlBlockedError.aspx>
2010-668-44-810
ONNET:
2205 5534
Showing Investigation and Proprietary logs together in time order

separately
Show
Investigation Log and Proprietary Log

1. 22-Apr-2015 18:47
mbednarz
ALCATEL-LUCENT PROPRIETARY
Outgoing E-mail to Karim (Karim)** CTR ** IBRAHIM ABD EL NABY

Workflow Status: Queued
Subject: Re: Etisalat UAE//High rate of VSWR alarms that can be fixed only
by
MC-RRH replacement/1-5692664
Contact: Karim (Karim)** CTR ** IBRAHIM ABD EL NABY
Agent: mbednarz
From: support@alcatel-lucent.com
To: "IBRAHIM ABD EL NABY, Karim (Karim)** CTR **"

<karim.ibrahim@alcatel-lucent.com>
Cc: "KHEDR, MAHMOUD (MAHMOUD)" <Mahmoud.Khedr@alcatel-lucent.com>, "REDA,
RAMY
(RAMY)" <ramy.reda@alcatel-lucent.com>, "ABDEL-HALIM, SAYED (SAYED)"
<Sayed.Abdel-Halim@alcatel-lucent.com>, 3G_ALU_Integ_UAE
<3g_Alu_Integ_Uae@alcatel-lucent.com>, "MERAD, ABDESSAMAD (ABDESSAMAD)"
<abdessamad.merad@alcatel-lucent.com>, "BERIDY, AHMED (AHMED)"
<Ahmed.Beridy@alcatel-lucent.com>, "EL-MIDANY, AHMED (AHMED)"
<Ahmed.El-Midany@alcatel-lucent.com>
Bcc:
Sent on:
Dear Karim,
Thank you for contacting the Alcatel-Lucent Welcome Center.

Your request has been processed and the ticket number for your reference is
AR
1-5692664
Please reference that number when contacting Alcatel-Lucent for follow-up.
An Alcatel-Lucent representative will contact you regarding your request.
Kind Regards,
Malwina Bednarz
ALCATEL-LUCENT
GLOBAL WELCOME CENTER
Visit OnLine Customer Support for Contact details
2. 22-Apr-2015 18:53
mbednarz
Outgoing E-mail to SHELENDRA (SHELENDRA) SHARMA

Workflow Status: Routing
Subject: Regarding 1-5692664
Contact: SHELENDRA (SHELENDRA) SHARMA
Agent: mbednarz
From: support@alcatel-lucent.com
To: Shelendra.Sharma@alcatel-lucent.com
Cc:
Bcc:
Sent on:
Dear Sir,
As I couldn't reach you over the phone, I called Secondar from Schedule
engineer
Sudhakar Babu and he advised to assigned the ticket for Emirates
Telecommunications Corporation to your handle.
Kind regards,
Malwina Bednarz
ALCATEL-LUCENT
GLOBAL WELCOME CENTER
Visit OnLine Customer Support for Contact details
3. 22-Apr-2015 19:01
shelends
Update to Current Summary: April 22: VSWR alarm on MC RRH
4. 22-Apr-2015 19:01
shelends
April 22: VSWR alarm on MC RRH
5. 22-Apr-2015 19:06
shelends
Update to Current Summary: April 22: VSWR alarm on MC RRH, awaiting logs
6. 22-Apr-2015 19:06
shelends
April 22: VSWR alarm on MC RRH, awaiting logs
7. 23-Apr-2015 08:13
shelends
Update to Current Summary: April 23: VSWR alarm on MC RRH, awaiting logs
8. 23-Apr-2015 08:13
shelends
April 23: VSWR alarm on MC RRH, awaiting logs
9. 24-Apr-2015 18:00
shelends
From: SHARMA, Shelendra (Shelendra)** CTR **

Sent: Friday, April 24, 2015 7:29 PM
To: DAS, Sunil (Sunil)** CTR **
Cc: AGRAWAL, Ritesh (Ritesh)** CTR **; INDIA-WCDMA-UTRAN-BE; ARORA, Gaurav
(Gaurav)** CTR **
Subject: RE: 1-5692664/MAJOR/9926 DBS/LR 13.3/Etisalat_UAE/High rate of VSWR
alarms that can be fixed only by MC-RRH
Hi Sunil
I have escalated this AR to your work group,.Please help us to assign this

AR to
your team (9926 DB NODEB ) to get the RC of this issue.
Below I have pasted complete expectation & details about this issue.
1 ? DESCRIPTION TEMPLATE
SUMMARY;
Concerned Node B and
RNC: 9926 DBS WCDMA
Concerned component : MC RRH
Type of alarm:
RRH VSWR DIV/31 VSWR LEVEL 2 & RRH VSWR DIV/31 (ANTENNA
ACCESS/31)
RAISED
2015-04-24
01:57:50 VSWR LEVEL 2
Time of the issue:

MC-RRH
As per log 24th April, but generally it is coming with
and can be fixed on replace MC-RRH
Product release: LR13.3
NODE-B V13D3.0 EBC.01" & "NODE-B V13D3.0 EC2.03"
Patch release: N/A
Reproducible: Yes its happening in 3G+MC-RRH sites after deployment
PROBLEM DETAILS:
1. Action performed (feature activation, upgrade, work?order
application...):
Customer receives high rate of VSWR alarms on the MC-RRHs after deployment.
2. System behavior (high?level + detailed description if relevant):

Customer
receives high rate of VSWR alarms on the MC-RRHs after deployment.
3. TSC/TIS analysis:
but
We have got VSWR LEVEL 2 ALARM ONLY ON 3RD sector,
customer saying but the issue that the VSWR alarms are bouncing over the
time, so
now we have only on Sec1 may after some time we have on all sectors like the
cases
I mentioned below, this issue so critical because the only way to clear this
alarms is to replace the MC-RRHs (I mean after applying all troubleshooting
methods)
2812565
NW:UTRAN BTSEquipment:ET_AR_U_2198_MohawagaWest
AntennaAccess:antennaConnection_31 NW/UTRAN
BTSEquipment/ET_AR_U_2198_MohawagaWest
AntennaAccess/antennaConnection_31
Active
FALSE
RRH VSWR DIV/31 VSWR LEVEL 2
2015-04-23T18:36:53 +0400
minor
Specific Problem:RRH VSWR DIV/31 VSWR LEVEL 2,
AdditionalInformationFromNE:additionalInformation = { manufacturerInfoAscii
= Tx2
VSWR Alarm }
2812512
Cleared
2015-04-23T18:33:02 +0400
Specific
2015-04-23T18:29:31 +0400
FALSE
minor
Problem:RRH VSWR DIV/31 VSWR LEVEL 2,

= Tx2
VSWR Alarm }
2812411
Cleared
2015-04-23T18:23:38 +0400
Specific
2015-04-23T18:16:24 +0400
FALSE
minor
= Tx2
VSWR Alarm }
2812340
Cleared
2015-04-23T18:10:15 +0400
Specific
2015-04-23T18:09:27 +0400
FALSE
minor

= Tx2
VSWR Alarm }
From IMT:-
2015-04-24 01:57:51:243:D7CE8715
VSWR DIV/31 (ANTENNA ACCESS/31)
2015-04-24 01:57:50 VSWR LEVEL 2
4481.3620636437 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 02:08:14:040:E7E836E3
2015-04-24 02:08:13 VSWR LEVEL 2
4490.3890755299 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 02:09:56:453:656D7F4A
2015-04-24 02:09:55 VSWR LEVEL
4492.1701674826 [MsgSeq/37b394b0] RRH

RAISED
4. Reason for priority/severity choice:

Here
Customer want RCA for this issue,
you can see customer points.
Customer receives high rate of VSWR alarms on the MC-RRHs after

deployment.
Customer performed all troubleshooting methods to clear it but the
issue still
the same and the only one solution to recover is to replace the MC-RRH.
-
Note: we are using the MC-RRH for 3G ONLY mode.
Note:
Alarm
customer activated the feature "FN 159393 Configurable VSWR
Threshold"?" on all the network as per customer request from about 2 months,
may
it have any relation.
the
Customer taken the NodeB "ET_AR_U_2198_MohawagaWest" as an example and
running SW
is "NODE-B V13D3.0 EC2.03"
5. Contact information: N/A
CONFIGURATION:
1. Hardware configuration: 9926 DBS WCDMA NODE B----MC-RRH
2. Software configuration: LR13.3
IMPACT:
1. Frequency of the problem (once, x times, sporadic, systematic...):
Customer
receives high rate of VSWR alarms on the MC-RRHs after deployment
2. Features impacted (iMCTA, CAC, Rate Adaptation, HSxPA over IUR,

other...):
Customer receives high rate of VSWR alarms on the MC-RRHs after deployment
6 ? LOGS AND TRACES------------------------------Sever IP; 135.240.25.160

wftp/wftp
/home/wcdma/Etisalat_UAE/AR1-5692664 ,China FTP server.
Expectations from the TEC ----------------------------------Need RCA
RC of this issue.
Another recovery action in case we received the VSWR again till you
find the RC.
and
Any relation of this alarms with the feature I mentioned?!.(Attached
uploaded at server with description of it)

-
Any relation of this alarms with the SW running on the MC-RRH?!.
Below a history of the sites solved by MC-RRH replacement and the

actions taken,
Site ID
Site name
Alarm date
RRH location
RRH SN Faulty
Techno Alarm
Taken action
report
2531 WR_SUROOR_FARM 16-Mar-15
replacement
U900
VSWR on all sectors
Only RRH
resolved the issue - Dummy load on RRH port after 4 to 5 min. VSWR alarm
appeared
CEVA for DOA SH1434G02LH
Submitted

replacement
U900
VSWR on all sectors
Only RRH
appeared
CEVA for DOA SH1434G02JT
Submitted

replacement
U900
VSWR on all sectors
Only RRH
appeared
CEVA for DOA SH1435G05CB
Submitted
2842 WR_OSAN_CAMP_HAMIM
replacement resolved
21-Apr-15
U900
VSWR sector 3
Only RRH
the issue - Dummy load on RRH port after 4 to 5 min. VSWR alarm appeared
CEVA for
DOA
SH1435G05FB
Submitted
2614 WR_Gayathi_Industrial
replacement
resolved the issue
submitted
19-Mar U900
Repeated VSWR sec 1
SC warehouse to try in another site
2289 WR_GHAGHA_COAST_GAURD
20-Apr U900
VSWR on Sec-5
Only RRH
Not
Only RRH
SC
warehouse
SH1449G0060
243
ET_AR_U_243_ShamsU900
RRH port after 4 to
Not submitted
20-Apr U900
VSWR-SEC1
Dummy load on
5 min. VSWR alarm appeared + RRH cannot be replaced as site is CNIA and need
permission to take extra material to site
SH1434G02FB
on site could be seen from WMS
Not submitted
2115 ET_AR_U_2115_Mzd1U900
RRH port after 4 to
20-Apr U900
VSWR-SEC1
Dummy load on
Not submitted
2118 ET_AR_U_2118_AbuAwanaU900
fluctuating - health
SC warehouse
SH1424G0338
20-Apr U900
VSWR-SEC1
20-Apr U900
VSWR-SEC1&3
VSWR
check only
2130 ET_AR_U_2130_BidaAridU900
2787 EM_AR_U_2787_Habshan5GascoMainGate
Jumpers
tightened
20-Apr U900
RRH OK
Regds
Shelendra Sharma
10. 24-Apr-2015 18:02

shelends
VSWR-U900 SEC1
From: owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM
[mailto:owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
SHARMA,
Shelendra (Shelendra)** CTR **
Cc: AGRAWAL, Ritesh (Ritesh)** CTR **; INDIA-WCDMA-UTRAN-BE; ARORA, Gaurav
(Gaurav)** CTR **
Subject: RE: 1-5692664/MAJOR/9926 DBS/LR 13.3/Etisalat_UAE/High rate of VSWR
alarms that can be fixed only by MC-RRH
Hi Sunil
I have escalated this AR to your work group,.Please help us to assign this

AR to
your team (9926 DB NODEB ) to get the RC of this issue.
Below I have pasted complete expectation & details about this issue.
1 ? DESCRIPTION TEMPLATE
SUMMARY;
Concerned Node B and
RNC: 9926 DBS WCDMA
Concerned component : MC RRH
Type of alarm:
RRH VSWR DIV/31 VSWR LEVEL 2 & RRH VSWR DIV/31 (ANTENNA
ACCESS/31)
RAISED
2015-04-24
01:57:50 VSWR LEVEL 2
Time of the issue:

MC-RRH
As per log 24th April, but generally it is coming with
and can be fixed on replace MC-RRH
Product release: LR13.3
NODE-B V13D3.0 EBC.01" & "NODE-B V13D3.0 EC2.03"
Patch release: N/A
Reproducible: Yes its happening in 3G+MC-RRH sites after deployment
PROBLEM DETAILS:
1. Action performed (feature activation, upgrade, work?order
application...):
Customer receives high rate of VSWR alarms on the MC-RRHs after deployment.
2. System behavior (high?level + detailed description if relevant):

Customer
receives high rate of VSWR alarms on the MC-RRHs after deployment.
3. TSC/TIS analysis:
but
We have got VSWR LEVEL 2 ALARM ONLY ON 3RD sector,
customer saying but the issue that the VSWR alarms are bouncing over the
time, so
now we have only on Sec1 may after some time we have on all sectors like the
cases
I mentioned below, this issue so critical because the only way to clear this
alarms is to replace the MC-RRHs (I mean after applying all troubleshooting
methods)
2812565
Active
FALSE
2015-04-23T18:36:53 +0400
minor
= Tx2
VSWR Alarm }
2812512
Cleared
2015-04-23T18:33:02 +0400
Specific
2015-04-23T18:29:31 +0400
FALSE
minor

= Tx2
VSWR Alarm }
2812411
Cleared
2015-04-23T18:23:38 +0400
Specific
2015-04-23T18:16:24 +0400
FALSE
minor

= Tx2
VSWR Alarm }
2812340
Cleared
2015-04-23T18:10:15 +0400
Specific
2015-04-23T18:09:27 +0400
FALSE
minor

= Tx2
VSWR Alarm }
From IMT:-
2015-04-24 01:57:51:243:D7CE8715
2015-04-24 01:57:50 VSWR LEVEL 2
4481.3620636437 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 02:08:14:040:E7E836E3
2015-04-24 02:08:13 VSWR LEVEL 2
4490.3890755299 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 02:09:56:453:656D7F4A
2015-04-24 02:09:55 VSWR LEVEL
4492.1701674826 [MsgSeq/37b394b0] RRH

RAISED
4. Reason for priority/severity choice:

Here
Customer want RCA for this issue,
you can see customer points.
Customer receives high rate of VSWR alarms on the MC-RRHs after

deployment.
Customer performed all troubleshooting methods to clear it but the
issue still
the same and the only one solution to recover is to replace the MC-RRH.
-
Note:
Alarm
customer activated the feature "FN 159393 Configurable VSWR
may
the
Customer taken the NodeB "ET_AR_U_2198_MohawagaWest" as an example and
running SW
5. Contact information: N/A
CONFIGURATION:
1. Hardware configuration: 9926 DBS WCDMA NODE B----MC-RRH
2. Software configuration: LR13.3
IMPACT:
1. Frequency of the problem (once, x times, sporadic, systematic...):
Customer
receives high rate of VSWR alarms on the MC-RRHs after deployment
2. Features impacted (iMCTA, CAC, Rate Adaptation, HSxPA over IUR,

other...):
Customer receives high rate of VSWR alarms on the MC-RRHs after deployment
6 ? LOGS AND TRACES------------------------------Sever IP; 135.240.25.160

wftp/wftp
/home/wcdma/Etisalat_UAE/AR1-5692664 ,China FTP server.
Expectations from the TEC ----------------------------------Need RCA
RC of this issue.
find the RC.
and
uploaded at server with description of it)

-

actions taken,
Site ID
Site name
Alarm date
RRH location
RRH SN Faulty
Techno Alarm
Taken action
report
replacement
U900
VSWR on all sectors
Only RRH
appeared
CEVA for DOA SH1434G02LH
Submitted

replacement
U900
VSWR on all sectors
Only RRH
appeared
CEVA for DOA SH1434G02JT
Submitted

replacement
U900
VSWR on all sectors
Only RRH
appeared
CEVA for DOA SH1435G05CB
Submitted
2842 WR_OSAN_CAMP_HAMIM
21-Apr-15
U900
VSWR sector 3
Only RRH
CEVA for
DOA
SH1435G05FB
Submitted
2614 WR_Gayathi_Industrial
replacement
resolved the issue
submitted
19-Mar U900
Repeated VSWR sec 1
Only RRH
Not
2289 WR_GHAGHA_COAST_GAURD
20-Apr U900
VSWR on Sec-5
Only RRH
SC
warehouse
SH1449G0060
243
RRH port after 4 to
Not submitted
20-Apr U900
VSWR-SEC1
Dummy load on
SH1434G02FB
Not submitted
2115 ET_AR_U_2115_Mzd1U900
RRH port after 4 to
20-Apr U900
VSWR-SEC1
Dummy load on
Not submitted
2118 ET_AR_U_2118_AbuAwanaU900
fluctuating - health
SC warehouse
SH1424G0338
20-Apr U900
VSWR-SEC1
20-Apr U900
VSWR-SEC1&3
VSWR
check only
2130 ET_AR_U_2130_BidaAridU900
2787 EM_AR_U_2787_Habshan5GascoMainGate
Jumpers
tightened
20-Apr U900
VSWR-U900 SEC1
RRH OK
Regds
Shelendra Sharma
11. 24-Apr-2015 18:03

shelends
Update to Current Summary: April 24: AR Escalated to GPS BTS for RCA, with
escalation Note
12. 24-Apr-2015 18:03

shelends
April 24: AR Escalated to GPS BTS for RCA, with escalation Note
13. 02-May-2015 05:39

shelends
Update to Current Summary: May 2: AR Escalated to GPS BTS for RCA, with
escalation
Note
14. 02-May-2015 05:39

shelends
May 2: AR Escalated to GPS BTS for RCA, with escalation Not
15. 02-May-2015 06:00

shelends
Time Tracking Entry Added - IR01-TSA1
16. 02-May-2015 06:17

shelends
17. 02-May-2015 06:21

shelends
18. 02-May-2015 06:25

shelends
19. 04-May-2015 13:03

gauravarora
20. 06-May-2015 08:18

shelends

Sent: Thursday, April 23, 2015 3:09 PM
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **
Cc: INDIA-WCDMA-UTRAN-BE; ARORA, Gaurav (Gaurav)** CTR **
Subject: 1-5692664/MAJOR/9926/UAE-ETC/WCDMA/High rate of VSWR alarms that
can be
fixed only by MC-RRH replacement
Hi
Please provide following logs.
1.
IMT Log
2.
HFB Log
Regds
Shelendra Sharma
+91 9930969351
**********************************************************************
21. 06-May-2015 08:19

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

To: SHARMA, Shelendra (Shelendra)** CTR **
Cc: INDIA-WCDMA-UTRAN-BE; ARORA, Gaurav (Gaurav)** CTR **; MERAD, ABDESSAMAD
(ABDESSAMAD); REDA, RAMY (RAMY); ABDEL-HALIM, SAYED (SAYED);
3G_ALU_Integ_UAE;
AHMED, NADER (NADER); BERIDY, AHMED (AHMED); KHEDR, MAHMOUD (MAHMOUD)
Subject: RE: 1-5692664/MAJOR/9926/UAE-ETC/WCDMA/High rate of VSWR alarms
that can
be fixed only by MC-RRH replacement
Hello Sharma,
Kindly find below more details about the issue,
We receive high rate of VSWR alarms on the MC-RRHs after deployment.
We perform all troubleshooting methods to clear it but the issue

still the
same and the only one soln to recover is to replace the MC-RRH.
You can refer to these ARs, for more details about the MC-RRH
history of
deployment on our network,
Note:
we activated the feature "FN 159393 Configurable VSWR Alarm
may
The NodeBs are running on "NODE-B V13D3.0 EBC.01" & "NODE-B V13D3.0
EC2.03"
I take the NodeB "ET_AR_U_2198_MohawagaWest" as an example and the

running
SW
IMT&HFB&NW Snapshot uploaded @
/home/wcdma/Etisalat_UAE/AR1-5692664 ,China FTP server,
Requirements:
RC of this issue.
find
the RC.
the
description of it)

actions
taken,
Site ID
Site name
Alarm date
Techno
Alarm
Taken action
RRH location
RRH SN
Faulty report
2531
WR_SUROOR_FARM
16-Mar-15
U900
VSWR on all sectors
Only RRH replacement resolved the issue - Dummy load on RRH port after 4 to
5 min.
VSWR alarm appeared
CEVA for DOA
SH1434G02LH
Submitted
2531
WR_SUROOR_FARM
16-Mar-15
U900
VSWR on all sectors
5 min.
VSWR alarm appeared
CEVA for DOA
SH1434G02JT
Submitted
2531
WR_SUROOR_FARM
16-Mar-15
U900
VSWR on all sectors
5 min.
VSWR alarm appeared
CEVA for DOA
SH1435G05CB
Submitted
2842
WR_OSAN_CAMP_HAMIM
21-Apr-15
U900
VSWR sector 3
5 min.
VSWR alarm appeared
CEVA for DOA
SH1435G05FB
Submitted
2614
WR_Gayathi_Industrial
19-Mar
U900
Repeated VSWR sec 1
Only RRH replacement resolved the issue
Not submitted
2289
WR_GHAGHA_COAST_GAURD
20-Apr
U900
VSWR on Sec-5
5 min.
VSWR alarm appeared
SC warehouse
SH1449G0060
Not submitted
243
20-Apr
U900
VSWR-SEC1
Dummy load on RRH port after 4 to 5 min. VSWR alarm appeared + RRH cannot be
replaced as site is CNIA and need permission to take extra material to site
SH1434G02FB
Not submitted
2115
ET_AR_U_2115_Mzd1U900
20-Apr
U900
VSWR-SEC1
Dummy load on RRH port after 4 to 5 min. VSWR alarm appeared + RRH cannot be
replaced as site is CNIA and need permission to take extra material to site
SC warehouse
SH1424G0338
Not submitted
2118
ET_AR_U_2118_AbuAwanaU900
20-Apr
U900
VSWR-SEC1
VSWR fluctuating - health check only
2130
ET_AR_U_2130_BidaAridU900
20-Apr
U900
VSWR-SEC1&3
2787
EM_AR_U_2787_Habshan5GascoMainGate
20-Apr
U900
VSWR-U900 SEC1
Jumpers tightened
RRH OK
Thanks,
-BR,
Karim
M: +971 (0)56-354-4568
22. 06-May-2015 08:19

shelends

3G_ALU_Integ_UAE;
that can
Hi Karim
From HFB log:- We have got VSWR Level 2 alarm only on

query is
Sector 31, so my
rest of all cells are working fine with Same MC-RRH code and same software,
please
confirm.
2812565
AntennaAccess:antennaConnection_31
NW/UTRAN BTSEquipment/ET_AR_U_2198_MohawagaWest
2015-04-23T18:36:53 +0400
minor
Active
FALSE
= Tx2
VSWR Alarm }
2812512
2015-04-23T18:29:31 +0400
minor
Cleared
2015-04-23T18:33:02 +0400
FALSE
= Tx2
VSWR Alarm }
2812411
2015-04-23T18:16:24 +0400
minor
Cleared
2015-04-23T18:23:38 +0400
FALSE
= Tx2
VSWR Alarm }
2812340
2015-04-23T18:09:27 +0400
minor
Cleared
2015-04-23T18:10:15 +0400
FALSE
= Tx2
VSWR Alarm }
From IMT:-
2015-04-24 01:57:51:243:D7CE8715
2015-04-24 01:57:50 VSWR LEVEL 2
4481.3620636437 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 02:08:14:040:E7E836E3
2015-04-24 02:08:13 VSWR LEVEL 2
4490.3890755299 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 02:09:56:453:656D7F4A
2015-04-24 02:09:55 VSWR LEVEL 2
4492.1701674826 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 02:35:58:034:1EC4B481
DIV/31 (ANTENNA ACCESS/31)
2015-04-24 02:35:57 VSWR LEVEL 2
4515.516207745 [MsgSeq/37b394b0]
CLEARED
2015-04-24 02:42:08:098:815CF657
2015-04-24 02:42:07 VSWR LEVEL 2
4520.2170353239 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 05:51:17:264:A84D1533
2015-04-24 05:51:16 VSWR LEVEL 2
4685.2823623987 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 05:56:28:252:2ED24426
2015-04-24 05:56:27 VSWR LEVEL 2
4690.785531942 [MsgSeq/37b394b0]
RAISED
2015-04-24 06:39:41:010:E999224B
2015-04-24 06:39:40 VSWR LEVEL 2
4727.3919127115 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 06:45:29:199:FAB47270
2015-04-24 06:45:28 VSWR LEVEL 2
4732.4206129776 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 07:12:22:123:735099B5
2015-04-24 07:12:21 VSWR LEVEL 2
4756.1934662069 [MsgSeq/37b394b0] RRH

CLEARED
RRH VSWR
RRH VSWR
2015-04-24 07:14:09:317:2A50BB7 4758.44370871 [MsgSeq/37b394b0] RRH VSWR

RAISED
2015-04-24 07:14:08 VSWR LEVEL 2
2015-04-24 07:28:24:134:7315E15B
2015-04-24 07:28:23 VSWR LEVEL 2
4770.1930813787 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 07:33:25:268:D4E573B9
2015-04-24 07:33:24 VSWR LEVEL 2
4774.3571807161 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 07:57:33:945:E9A385D4
2015-04-24 07:57:33 VSWR LEVEL 2
4795.3919807956 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 07:59:21:374:79D78609
2015-04-24 07:59:20 VSWR LEVEL 2
4797.2044167689 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 08:03:42:041:44E6D643
2015-04-24 08:03:41 VSWR LEVEL 2
4801.1155978819 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 08:08:48:561:BAC701CC
2015-04-24 08:08:48 VSWR LEVEL 2
4805.3133604300 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 08:14:05:272:569E67DF
2015-04-24 08:14:04 VSWR LEVEL 2
4810.1453221855 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 08:18:24:489:1C4720F5
2015-04-24 08:18:24 VSWR LEVEL 2
4814.474423541 [MsgSeq/37b394b0]
RAISED
RRH VSWR
2015-04-24 08:21:55:920:2FEB713B
2015-04-24 08:21:55 VSWR LEVEL 2
4817.803959099 [MsgSeq/37b394b0]
CLEARED
RRH VSWR
2015-04-24 08:26:59:860:9C2F0BD9
2015-04-24 08:26:59 VSWR LEVEL 2
4821.2620328921 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 08:27:55:115:6A063DAE
2015-04-24 08:27:54 VSWR LEVEL 2
4822.1778793902 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 08:40:06:074:D0FBA5F 4833.219134559 [MsgSeq/37b394b0]

RAISED
2015-04-24 08:40:05 VSWR LEVEL 2
RRH VSWR
2015-04-24 08:41:00:285:D703642D
2015-04-24 08:40:59 VSWR LEVEL 2
4833.3607323693 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 08:42:50:157:70512A1B
2015-04-24 08:42:49 VSWR LEVEL 2
4835.1884367387 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 08:55:57:784:E6744E0A
2015-04-24 08:55:57 VSWR LEVEL 2
4846.3866381834 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 08:58:27:157:12EA5970
2015-04-24 08:58:26 VSWR LEVEL 2
4849.317348208 [MsgSeq/37b394b0]
RAISED
2015-04-24 09:21:00:448:C4508447
2015-04-24 09:20:59 VSWR LEVEL 2
4868.3293611079 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 09:22:47:929:54B66EC6
2015-04-24 09:22:47 VSWR LEVEL 2
4870.1421242054 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 09:27:48:674:B5137266
2015-04-24 09:27:48 VSWR LEVEL 2
4874.3037950566 [MsgSeq/37b394b0] RRH

CLEARED
RRH VSWR
2015-04-24 09:32:11:482:881CCA08
2015-04-24 09:32:10 VSWR LEVEL 2
4878.2283588104 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 09:37:38:346:49C6BB7A
2015-04-24 09:37:37 VSWR LEVEL 2
4883.1237760890 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 09:44:31:705:4DA86410
2015-04-24 09:44:31 VSWR LEVEL 2
4889.1302881296 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 10:31:09:223:339D373 4930.54121331 [MsgSeq/37b394b0] RRH VSWR

CLEARED
2015-04-24 10:31:09 VSWR LEVEL 2
2015-04-24 10:34:19:923:C9A2D43E
2015-04-24 10:34:19 VSWR LEVEL 2
4932.3382891582 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 10:46:29:349:66F66279
2015-04-24 10:46:29 VSWR LEVEL 2
4943.1727423097 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 10:48:13:272:EA1AF6F8
2015-04-24 10:48:13 VSWR LEVEL 2
4944.3927635704 [MsgSeq/37b394b0] RRH

RAISED
2015-04-24 10:53:29:806:85497313
2015-04-24 10:53:29 VSWR LEVEL 2
4949.2236183315 [MsgSeq/37b394b0] RRH

CLEARED
2015-04-24 10:55:18:169:18F7D7F0
2015-04-24 10:55:18 VSWR LEVEL 2
4951.418895856 [MsgSeq/37b394b0]
RAISED
2015-04-24 11:08:27:323:94CBC7A9
4962.2496382889
Regds
Shelendra Sharma
+91 9930969351
23. 06-May-2015 08:20

shelends

RRH VSWR

3G_ALU_Integ_UAE;
that can
Hello Sharma,
I can confirm that we are using the same MC-RRH during the deployment, but
the
issue that the VSWR alarms are bouncing over the time, so now we have only
on Sec1
may after some time we have on all sectors like the cases I mentioned below,
this
issue so critical because the only way to clear this alarms is to replace
the
MC-RRHs (I mean after applying all troubleshooting methods)
Please as mentioned with MR.Abdelsammad on another mail, thanks to check the

below
2 issue also,
[A.M]
This issue is seriously killing as most of the solution today require HW
change.
Either we have a product issue
Either I&C issue
We are also suspecting RRH calibration issue, can you please also explore
this
direction, any methodlogy to adjust calibration on site to consider
environmental
effect ?
Thanks,
-BR,
Karim
M: +971 (0)56-354-4568
24. 06-May-2015 08:20

shelends
From:
owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM<mailto:owner-india-wcdmautr
an-be@LIST.ALCATEL-LUCENT.COM>
[mailto:owner-india-wcdma-utran-be@LIST.ALCATEL-LUCENT.COM] On Behalf Of
SHARMA,
Shelendra (Shelendra)** CTR **
Sent: Monday, April 27, 2015 10:22 PM
3G_ALU_Integ_UAE;
AHMED, NADER (NADER); BERIDY, AHMED (AHMED); KHEDR, MAHMOUD (MAHMOUD); ELMIDANY,
AHMED (AHMED)
that can
Hi Karim
GPS-BTS Team is working on this issue, Will back to you soon.
Regds
Shelendra
25. 06-May-2015 08:21

shelends

Sent: Wednesday, April 29, 2015 11:17 AM
3G_ALU_Integ_UAE;
AHMED (AHMED); OKASHA, TAHER (TAHER)
that can
Importance: High
Hello Sharma,
Kindly find my comments highlighted below,
Please treat this issue urgent as the we received customer escalation on the
VSWR
alarms and it's a blocking point for our swap progress.
Thanks,
[Description: Description: Description: Description: alu]
-BR,
Karim
LTE/3G Integration Professional
M: +971 (0)56-354-4568

Sent: Tuesday, April 28, 2015 4:12 PM
3G_ALU_Integ_UAE;
AHMED (AHMED)
that can
Hi Karim
After the MC-RRHs deployment VSWR alarm is raised, it is clearly showing

that
there is impedance mismatch between load and the source impedance.
Probable Causes:
*
*
1.Inappropriate data configuration

A VSWR alarm threshold is set inappropriately
--> As I mentioned before we activate the VSWR threshold feature "FN

--> 159393"(Attached) with the levels "Threshold1 to RL14 ; VSWR 1.5 ,
--> Threshold2 to RL12 ; VSWR 1.67", Please check and confirm that no
--> relation between it and MC-RRH load
2.Hardware fault
*
the
The frequency band type of the TRX is inconsistent with that of
antenna components.
The actual VSWR of the antenna components increases, leading to an
abnormal antenna VSWR. The reason may be

An antenna component is damaged:
1.
A connector on an antenna component is not well prepared.
2.
A connector on an antenna component is not tightened or is wet.
3.
An antenna cable is bent or deformed.
*
highly
The two input ports on the 3 dB combiner or hybrider are not
isolated. Therefore, the detected VSWR is higher than the actual VSWR, which
leads
to false VSWR alarms. This situation occurs when a combiner is used by
multiple
carriers working on the same frequency band.
==> Is the HW fault you mentioned is investigation or what?, is it a HW

issue?
Just check
the
for the above causes, may be any one of the causes may impact
VSWR.
1. whether the VSWR alarm is raised immediately after the MC-RRH

installation? -->
Not at all times, lot of MC-RRH running from deployment ill now normally, 2.
Have
you checked whether the RRH which is removed is working on the other site?-> New
Brand 3. kindly send the NodeB snapshot.--> Attached.
Regds
Shelendra Sharma
26. 06-May-2015 08:21

shelends

Sent: Wednesday, April 29, 2015 7:29 PM

3G_ALU_Integ_UAE;
that can
Hi Karim
For analysis we need the following logs.
1.
Need the IMT for the Faulty MC-RRH.
2.
Need the software dumps collected with Faulty MC-RRH and New RRH.
Command to collect the Dumps:
1)
Set_Print_Error_Level 1
2)
Trace_Turnon_Terminal
Keep the trace collecting for 3 minutes.

After that, you can use Trace_Turnoff_Terminal to close the trace printing.
And besides the trace, please execute below commands to collect more
information.
1)
SWStatus_Show
2)
TxConfig_Show
3)
RunningSWName_Show
Also we said the probable causes for VSWR alarm, I didn't mean exactly it's
a
hardware issue.
Regds
Shelendra Sharma
27. 06-May-2015 08:21

shelends

Sent: Friday, May 01, 2015 5:45 PM
3G_ALU_Integ_UAE;
that can
Importance: High
Hello Sharma,
Kindly attached the required logs, Please add the GPS to the loop as we
already
have another
as an
AR 1-5682573 related to the MC-RRH, here we take the site 2032
example, RRH Sec6 U900,
All types of troubleshooting done on the site till we change the Antenna,
and the
issue still the same.
Please treat this AR very urgent as we have quick rollout progress due the
swap
and this issue blocking our swap progress,
Thanks,
[Description: Description: Description: Description: alu]
-BR,
Karim
28. 06-May-2015 08:22

shelends

Sent: Monday, May 04, 2015 9:15 AM
3G_ALU_Integ_UAE;
that can
Hi Karim
Kindly check, If you deactivate FN 159393,

please
alarm disappears
or not
confirm.
Regds
Shelendra Sharma
+91 9930969351
29. 06-May-2015 08:22

shelends

Sent: Monday, May 04, 2015 12:23 PM
3G_ALU_Integ_UAE;
that can

Importance: High
Hello Sharma
NO, I did the reverse for the site 2302 but the alarms still exist.
Thanks,
-BR,
Karim
30. 06-May-2015 08:22

shelends

Sent: Tuesday, May 05, 2015 11:15 AM
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; ARORA, Gaurav (Gaurav)**
CTR **;
AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;
AHMED (AHMED); OKASHA, TAHER (TAHER); DAS, Sunil (Sunil)** CTR **; PASHA, D
Hussain (D Hussain)** CTR **
that can
Adding GPS team
Hi Karim
1.
Please
The IMT which you have shared does not have all the MC-RRH logs.
Collect the full log (IMT) and share with us. Please find the attached
reference
RRH logs (software dumps).
2.
below
Command to collect the Dumps: Please login into RRH and Execute
commands and capture the console output.
1)
Set_Print_Error_Level 1
2)
Trace_Turnon_Terminal
Keep the trace collecting for 3 minutes.

After that, you can use Trace_Turnoff_Terminal to close the trace printing.
1.
more
And besides the trace, please execute below commands to collect
information.
1)
SWStatus_Show
2)
TxConfig_Show
3)
RunningSWName_Show
Regds
Shelendra Sharma
31. 06-May-2015 08:23

shelends
From: IBRAHIM ABD EL NABY KARIM

Sent: 2015?5?5? 15:37
To: SHARMA SHELENDRA; ARORA Gaurav; AGRAWAL RITESH; LU Wei I; DAS SUNIL
Cc: INDIA-WCDMA-UTRAN-BE; ARORA Gaurav; MERAD ABDESSAMAD; REDA RAMY; ABDELHALIM
SAYED; 3G ALU INTEG UAE; AHMED NADER; BERIDY AHMED; KHEDR MAHMOUD; EL-MIDANY
AHMED; OKASHA TAHER; DAS SUNIL; PASHA D Hussain
that can
Importance: High
Hello Sharma,
The required logs attached.. can you elaborate why the IMT don't cover the
MC-RRH
logs?!. What to do to have this logs included on the IMT?
Please note this logs after the deactivate of the VSWR threshold feature.
Thanks,
-BR,
Karim

M: +971 (0)56-354-4568
32. 06-May-2015 08:23

shelends
From: LU Wei I [mailto:Wei.i.Lu@alcatel-sbell.com.cn]

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; SHARMA, Shelendra
(Shelendra)**
CTR **; ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **;
DAS,
Sunil (Sunil)** CTR **
3G_ALU_Integ_UAE;
that can
Hi, Karim
The RRH is running in incorrect load, the same issue as we discussed in

another
mail loop.
============================================================================
====
Hardware and FPGA Versions

CPLD Version
: 2.3
FPGA Version
: 72247
Build 00000
============================================================================
====
BRs
LuWei
33. 06-May-2015 08:23

shelends

Sent: Tuesday, May 05, 2015 1:22 PM
To: LU, Wei I (Wei); SHARMA, Shelendra (Shelendra)** CTR **; ARORA, Gaurav
(Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **; DAS, Sunil (Sunil)**
CTR **
3G_ALU_Integ_UAE;
that can
Hello Lu,
But we have also other sites have the VSWR alarms and the FPGA version is
OK...
Thanks,
-BR,
Karim
34. 06-May-2015 08:24

shelends
From: DAS, Sunil (Sunil)** CTR **

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; LU, Wei I (Wei); SHARMA,
Shelendra (Shelendra)** CTR **; ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL,
Ritesh
(Ritesh)** CTR **
3G_ALU_Integ_UAE;
AHMED (AHMED); OKASHA, TAHER (TAHER); PASHA, D Hussain (D Hussain)** CTR **
that can
Karim,
If VSWR alarm present, cell will be down. can you please confirm cell
status?
Regards,
Sunil
35. 06-May-2015 08:24

shelends

To: DAS, Sunil (Sunil)** CTR **; LU, Wei I (Wei); SHARMA, Shelendra
(Shelendra)**
CTR **; ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;
that can
Sunil,
Yes the cell down,
Sunil,Lu,
How can we do audit on all installed MC-RRHs to know the running FGPA
version, I
need to make sure that all network aligned with the correct FGPA verison, ?!
Do you confirm if we apply the WA now for this MC-RRH the VSWR will be
cleared?!
Thanks,
-BR,
Karim
M: +971 (0)56-354-4568
36. 06-May-2015 08:25

shelends
From: DAS SUNIL

Sent: 2015?5?5? 16:07
To: IBRAHIM ABD EL NABY KARIM; LU Wei I; SHARMA SHELENDRA; ARORA Gaurav;
AGRAWAL
RITESH
AHMED; OKASHA TAHER; PASHA D Hussain
that can
Karim,
1.
If you want to audit, a script is needed. The script will login each
nodeb/RRH
and collect FPGA version from running software. The script will compare with
correct version. If not okay, it will login the nodeB and RRH number.
2.
VSWR alarm can be for number of reasons.
a.
Path loss is more.
b.
Bug in firmware
c.
Antenna is not correctly positioned.
d.
Many more.
Let us go step by step to determined VSWR alarm. Please apply work-around

and let
us remove software component from investigation.
LU Wei,
Is there any command to see return loss in RF cable?
Regards,
Sunil
37. 06-May-2015 08:25

shelends

To: DAS, Sunil (Sunil)** CTR **; IBRAHIM ABD EL NABY, Karim (Karim)** CTR
**;
SHARMA, Shelendra (Shelendra)** CTR **; ARORA, Gaurav (Gaurav)** CTR **;
AGRAWAL,
Ritesh (Ritesh)** CTR **

3G_ALU_Integ_UAE;
that can
Sunil, Karim
As I said, if RRH load is fine we can use below command to show measured
VSWR.
L1DPDCTRLStatus_Show
Be aware, if there is no cell the measured VSWR will be 0.
BRs
LuWei
38. 06-May-2015 08:25

shelends

Sent: 2015?5?5? 16:33
To: LU Wei I; DAS SUNIL; SHARMA SHELENDRA; ARORA Gaurav; AGRAWAL RITESH

that can
Importance: High
Hello Sunil,Lu
Yes we need a script to audit the network and provide below
FPGA version.
Active and running SW version of each MC-RRH.
Please start to prepare it.
Attached the output of the command,
I'm still no apply the WA.
Thanks,
-BR,
Karim
M: +971 (0)56-354-4568
39. 06-May-2015 08:26

shelends

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; DAS, Sunil (Sunil)** CTR
**;
AGRAWAL,
3G_ALU_Integ_UAE;
that can
Karim
You should make the running load correct first, otherwise the TX path 1
won't work.
The TX path 2 is normal in the trace.
Measured VSWR
---- measured VSWR is under threshold
17
(Unit: 1/10)
Urgent VSWR Threshold

---- two thresholds for VSWR report
30
(Unit: 1/10)
21
(Unit: 1/10)
Warnning VSWR
@ Sunil, do you know if anyone in GPS team can help on the script?
BRs
LuWei
40. 06-May-2015 08:26

shelends

Sent: 2015?5?5? 18:02
To: LU Wei I; DAS SUNIL; SHARMA SHELENDRA; ARORA Gaurav; AGRAWAL RITESH
that can
Hello Lu,
The WA applied, attached the output after the action. Please note no VSWR
till now,
Let me know your comments please,
Sunil,Lu
I think we can correlate the 2 ARs here the one for F5,F6 Zero traffic,
You can see below that we have lot of cell have zero RRC, Please treat the
issue
very urgent, we should find the RC and recovery action for all network, the
number
of cells increasing every day due to the swap and these issue affecting our
swap
progress and acceptance,
@Sunil , Im waiting your confirmation about the date to provide the script.
Cell Name
RF Comment
BO Comment
AR_2532_53251_F5_A
ZERO RRC
AR_2532_53252_F5_B
Very low RRC
AR_2532_53253_F5_D
ZERO RRC
AR_2532_53254_F5_C
ZERO RRC
AR_2032_13331_F5_A
ZERO RRC
AR_2032_13332_F5_B
ZERO RRC
AR_2032_13333_F5_C
ZERO RRC
AR_2118_00814_F5_D
ZERO RRC
AR_2118_00818_F6_D
ZERO RRC
AR_2126_06221_F5_A
ZERO RRC
AR_2135_21351_F5_A
ZERO RRC
AR_2135_21352_F5_B
ZERO RRC
AR_2153_21534_F5_D
ZERO RRC (VSWR alarm as per BO)
AR_2153_21538_F6_D
ZERO RRC (VSWR alarm as per BO)
AR_2376_15451_F5_A
ZERO RRC
AR_2527_16411_F5_A
ZERO RRC
AR_2527_16412_F5_B
ZERO RRC
AR_2527_16413_F5_C
ZERO RRC
AR_2842_18332_F5_B
Very low RRC
AR_2842_18335_F6_B
Very low RRC
AR_2843_28436_F6_A
ZERO RRC
Thanks,
-BR,
Karim
41. 06-May-2015 08:27

shelends

**;
AGRAWAL,
3G_ALU_Integ_UAE;
that can
Karim
Your trace is normal, measured VSWR is under threshold.

In case you found the VSWR exist with correct load, please send to me.
For the zero RRC issues, I think they are properly caused by incorrect load.
Have we stopped the original load upgrade via SUM?

There should be some BAD operation steps when site team perform it.
BRs
LuWei
42. 06-May-2015 08:27

shelends

To: LU, Wei I (Wei); DAS, Sunil (Sunil)** CTR **; SHARMA, Shelendra
(Shelendra)**
3G_ALU_Integ_UAE;
that can
Importance: High
Hello Lu,
Yes we stopped using SUMX, but the old sites done with SUMX still running on
the
network , that's why we should audit all the netowork.
For the VSWR, I'll activate again the VSWR threshold feature and check if
the VSWR
will come back or not , attached feature details.
And this is the threshold we are using on the network, please check if any
problem
with it.
Threshold1 to RL14 ; VSWR 1.5 , Threshold2 to RL12 ; VSWR 1.67
Thanks,
-BR,
Karim
43. 06-May-2015 08:27

shelends

Ritesh
(Ritesh)** CTR **
3G_ALU_Integ_UAE;

that can
Karim,
It is good news that VSWR is not there after applying WA.

Do you want another script which will apply WA and reset RRH? This will help
you
to clean up the network with correct software?
Regards,
Sunil
44. 06-May-2015 08:28

shelends

(Shelendra)**
3G_ALU_Integ_UAE;
that can

Importance: High
Sunil,Lu
Unfortunately the VSWR come back now after activating the threshold feature!
But
this time as minor alarm not major as before (applying the WA and VSWR
feature_
To summarize:
1-
Major alarm was exist
2-
We deactivate the VSWR threshold feature , ' major alarms still exist
3-
We applied WA ' the Major VSWR cleared.
4-
We activated the VSWR threshold feature, ' Minor VSWR alarms back
Please check below and attached,
/pltf_587$ emo/alarm/GlobalAlarms
+------------------------------------------------------------------+---------------------+------------------+------------------------------------------------+
Equipment (Object)
Time
Status
Specific Cause
+------------------------------------------------------------------+--------------------+------------------+------------------------------------------------+
Faults for Ecem256.01 1

Faults for RRH 32
RRH VSWR MAIN/61 (ANTENNA ACCESS/61)
2015-05-05 14:16:27 VSWR LEVEL 2
RAISED
+-> Manuf Info ASCII =

+-> Manuf Info BIN
= 00
RRH VSWR DIV/61 (ANTENNA ACCESS/61)

2015-05-05 14:16:54 VSWR LEVEL 2
+-> Manuf Info ASCII =
RAISED
+-> Manuf Info BIN
= 00
Faults for RRH 33

Faults for RRH 34
Faults for RRH 35
Faults for RRH 36
Faults for RRH 37
Faults for IP IuB
+------------------------------------------------------------------+---------------------+------------------+------------------------------------------------+
/pltf_587$
Thanks,
-BR,
Karim
45. 06-May-2015 08:28

shelends
From: DAS SUNIL

Sent: 2015?5?5? 22:46
To: IBRAHIM ABD EL NABY KARIM; LU Wei I; SHARMA SHELENDRA; ARORA Gaurav;
AGRAWAL
RITESH
that can
Karim,
1.
Generally RF cable influence return path Loss.
length
of RF cable and make?
loss per
Can you please tell us
Quality depends vendor to vendor. Vendor specifies
mtr.
Path 1 >>
Measured VSWR
16
(Unit: 1/10)
Path 2 >>
------------------------------------------------------------------------Measured VSWR
2.
15
(Unit: 1/10)
Threshold define is
Should we increase
Warnning VSWR
18
:
(Unit: 1/10)
17
(Unit: 1/10)
Can you please define above threshold in one RRH and let us monitor KPI.
Lei Wei,
You opinion please.
Regards,
Sunil
46. 06-May-2015 08:29

shelends
Sent: Wednesday, May 06, 2015 7:56 AM

**;
AGRAWAL,
3G_ALU_Integ_UAE;
AHMED (AHMED); OKASHA, TAHER (TAHER); PASHA, D Hussain (D Hussain)** CTR **;
CHEN,
Wenwen (Wenwen); YI, Dongchao (Dongchao); CHEN, Eric (Eric)

that can
Hi, Karim, Sunil
First, the VSWR is not related to calibration I think.
Second, for the VSWR threshold.

Why did you choose 1.5 and 1.67 ?
It will be more sensitive than default value 2.1 and 3.0.
As I can see in some other sites, they just use the default value.
Third, for the measured VSWR.

From my personal view, they should be okay.
We checked in our lab, we can see measured VSWR 1.6 with RRH terminated by
50 ohms
load.
BRs
LuWei
47. 06-May-2015 08:29

shelends
From: DAS SUNIL

Sent: 2015?5?6? 10:32
To: LU Wei I; IBRAHIM ABD EL NABY KARIM; SHARMA SHELENDRA; ARORA Gaurav;
AGRAWAL
RITESH

AHMED; OKASHA TAHER; PASHA D Hussain; CHEN Wenwen; YI Dongchao; CHEN Eric
that can
So, you suggest default threshold should be as below.
Regards,
Sunil
48. 06-May-2015 08:29

shelends

**;
AGRAWAL,
3G_ALU_Integ_UAE;
CHEN,

that can
Sunil
I am not familiar with the threshold setting on site.
Maybe you can check with other site deploy team for our normal setting.
At least 2.1 and 3.0 are acceptable in some customer site.
BRs
LuWei
49. 06-May-2015 08:30

shelends

To: LU, Wei I (Wei); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; SHARMA,
Ritesh
(Ritesh)** CTR **
3G_ALU_Integ_UAE;
CHEN,

that can
Current setting at site is as below based on feature recommendation.
If increasing threshold does not bring KPI degradation, we will surely

suggest to
modify.
KPI.
As I suggested last night, let us apply it to a nodeB and observe
Regards,
Sunil
50. 06-May-2015 09:37

shelends
51. 06-May-2015 09:37

shelends
52. 08-May-2015 15:46

shelends
Update to Current Summary: May 8: After changed VSWR threshold value, KPI is
good
, under observation
53. 08-May-2015 15:46

shelends
May 8: After changed VSWR threshold value, KPI is good , under observation
54. 15-May-2015 14:11

shelends
Update to Current Summary: May 16: After changed VSWR threshold value, KPI
is good
, under observation
55. 15-May-2015 14:11

shelends
May 16: After changed VSWR threshold value, KPI is good , under observation
56. 20-May-2015 14:45

shelends
Update to Current Summary: May 20: After changed VSWR threshold value, KPI
is good
, awaiting customer feedback
57. 20-May-2015 14:45

shelends
May 20: After changed VSWR threshold value, KPI is good , awaiting customer
feedback
58. 20-May-2015 14:56

shelends

Sent: Wednesday, May 06, 2015 3:11 PM
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; PASHA, D Hussain (D
Hussain)**
CTR **; DAS, Sunil (Sunil)** CTR **; SHARMA, Shelendra (Shelendra)** CTR **;
ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;
AHMED (AHMED); OKASHA, TAHER (TAHER); CHEN, Wenwen (Wenwen); YI, Dongchao
(Dongchao); CHEN, Eric (Eric)
that can
Hi, Sunil
As you said 50 ohms is a theoretical value for all RF devices.

Due to product deviation, some RRH's output impedance may not equal to
50ohms
strictly. In this case, it's impossible to reduce VSWR by changing the RF
jumper.
Can we check some other country's site for the measured VSWR?
Then we can know if it's the first time we have such issue or it's normal
for our
HW products.
In our lab, we will also test the RRH's output impedance.

I think if our HW really have such deviation, we can increase the threshold
if it
doesn't impact KPI.
What's your view on this?
BRs
LuWei
59. 20-May-2015 14:58

shelends

Sent: Thursday, May 07, 2015 3:17 PM
Ritesh
(Ritesh)** CTR **; PASHA, D Hussain (D Hussain)** CTR **
3G_ALU_Integ_UAE;

that can
I could see data with Pasha. There is no KPI degradation. You can apply to
all
nodeBs.
Could you please send me dump of
after
L1DPDCTRLStatus_Show
from few nodeBs
modifying threshold value.
Regards,
Sunil
60. 20-May-2015 14:59

shelends

Ritesh
(Ritesh)** CTR **; PASHA, D Hussain (D Hussain)** CTR **
3G_ALU_Integ_UAE;
that can
Karim,
As feature document says, we can adopt
this threshold according to network
requirement. Maximum threshold can go up to 2.1 for RL9

You
and 3.0 for RL6.
can refer to the customer to convince them.
2nd, Lu Wei had also measured in his lab which is supposed to be ideal
condition
with small length of antenna cable and with proper termination. He found
loss is
16. RL is generally depends on terminating impedance and RF cable.
If your
network is not properly terminated , this loss would be there. some cases
more and
some cases less.
3rd, since we have experimented in one nodeb with threshold 2.1 and 3.0 and
found
no KPI degradation, what would be problem to increase threshold.? If
customer
insists with RL12 and RL9, there would be logic and measurement from their
network
designer. Can you please pass their document to us if any? Let us study and
recommend.
4th, to remove VSWR alarm, we need to play with impedance at antenna side.
Is the
customer using attenuator or impedance matching element in antenna?
Regards,
Sunil
61. 20-May-2015 15:01

shelends

(Shelendra)**
PASHA,
D Hussain (D Hussain)** CTR **
3G_ALU_Integ_UAE;
that can
Hello Sunil,
Thanks for usual detailed feedback,
I checked with the customer and they apply this threshold on all vendors to
be
aligned, and already applied on our 2G/LTE systems with 1.5 and 1.7,
Are there any news about the script?
Thanks,
<image001.gif>
-BR,
Karim
M: +971 (0)56-354-4568
62. 20-May-2015 15:02

shelends
From: PASHA, D Hussain (D Hussain)** CTR **

Ritesh
(Ritesh)** CTR **; DAS, Sunil (Sunil)** CTR **
3G_ALU_Integ_UAE;
(Dongchao); CHEN, Eric (Eric); Kumar, Kanipakam Vijaya K (Vijay)** CTR **
that can
Hi All,
Please find
script
the attached script. Steps to be followed before running the
Steps:
=========
1. copy this script to WMS server.
This should be copied only to /home/oamops/ directory.
2. untar the tar file
command: tar -xvf rrh_version.tar
3. once 2nd step is successful then go inside rrh_version
directory
command: cd rrh_version
4. Please run get_iplist.sh script 1st.
command: ./get_iplist.sh
5. Once 4th step is completed successful, then please run
nodeB_rrh_version-match.pl script.
command: ./nodeB_rrh_version-match.pl
Step 5 will take time to complete (depending on the list of NodeB in WMS
server).
Once nodeB_rrh_version-match.pl completed, it will create "logs" directory

in the
current directory
(ie. /home/oamops/rrh_version/) and this will contain 2 files inside.
1. perl_script_logs.log : This contains information related to script.
2. rrh_logs.log
Nodeb, RRH,
: This contains information related to
current Running s/w version and FPGA version's.
If you are sending any logs related to this script then please send both log
files
(perl_script_logs.log & rrh_logs.log).
BR,
Pasha
63. 20-May-2015 15:03

shelends

To: PASHA, D Hussain (D Hussain)** CTR **; IBRAHIM ABD EL NABY, Karim
(Karim)**
CTR **; LU, Wei I (Wei); SHARMA, Shelendra (Shelendra)** CTR **; ARORA,
Gaurav
(Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;
that can
Thanks Pasha.
Karim,
Please apply workaround and run the script again. Please look at list of
nodeBs
that created by the script. We want to make sure that all nodeBs are
covered.
Regards,
Sunil
64. 20-May-2015 15:04

shelends

Hussain)**
CTR **; LU, Wei I (Wei); SHARMA, Shelendra (Shelendra)** CTR **; ARORA,
Gaurav
(Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;
that can
Addition of VSWR may need some time. it is equal work as it was done for RRH
software version check. We will deliver in next installment.
Mean time, let us correct running software in the nodeB.
Regards,
Sunil
65. 20-May-2015 15:05

shelends
From: EL-MIDANY, AHMED (AHMED)

**;
PASHA, D Hussain (D Hussain)** CTR **; LU, Wei I (Wei); SHARMA, Shelendra
(Shelendra)** CTR **; ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh
(Ritesh)**
CTR **
3G_ALU_Integ_UAE;
AHMED, NADER (NADER); BERIDY, AHMED (AHMED); KHEDR, MAHMOUD (MAHMOUD);
OKASHA,
TAHER (TAHER); CHEN, Wenwen (Wenwen); YI, Dongchao (Dongchao); CHEN, Eric
(Eric);
Kumar, Kanipakam Vijaya K (Vijay)** CTR **
that can
Importance: High
Hello Sunil,
Thanks for your efforts, we will wait for the modified script.
Few comments from our side, when you mentioned "we need to extend threshold
as
appropriate" so what is the appropriate threshold that should be set? Can
you
share ALU official document highlighting the recommended VSWR thresholds?
And what
is the benefit from feature if we have to stick to default values (2.0 and
3.0)?
the default value is not accepted by the customer.
BR,
Ahmed El-Midany
66. 20-May-2015 15:06

shelends

**;
EL-MIDANY, AHMED (AHMED); LU, Wei I (Wei); SHARMA, Shelendra (Shelendra)**
CTR **;
ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;

OKASHA,
(Eric);
that can
Hi Karim,
From the data provided we can see that there is a minimum VSWR value of RL10
(1.92).so we suggest that kindly configure VSWR minimum threshold to 2.10.
find
the attached file for your reference.
From the file we can see that one site is not running on correct FPGA
version.
EP_AR_U_2309_Geasa/10.235.189.68
x0w_alw5.bin
MC RRH(10)/192.168.132.1
/NECI_72247_00000_1R3X09.fh2/NECI_73245_00000_2R3X09.fh2
BR,
Pasha
67. 20-May-2015 15:07

shelends

/0/11
Hussain)**
CTR **; EL-MIDANY, AHMED (AHMED); LU, Wei I (Wei); SHARMA, Shelendra
(Shelendra)**
3G_ALU_Integ_UAE;
OKASHA,
(Eric);
that can
Which equation are you referring to?
Generally VSWR =
(Zin -Zout)/(Zin+Zout)
Typically Zin =50 ohms and Zout=50 Ohms.

power
So in ideal condition delivered
should be absorbed by receiver if impedance is matched. it is called maximum

delivery condition.
VSWR as minimum as possible is good.
However in practical condition, Zin can't be equal to Zout, we would see

some
VSWR. How much we should allow, it depends on quality of KPI. As I
mentioned, if
no KPI degradation or no RSSI degradation or no impact on RTWP, we can go
till 2.1
and 3.0 as per default specification of the product.

could
In your network, we
see maximum 1.98. so, you can go easily 2.0 without impacting KPI.
Regards,
Sunil
68. 20-May-2015 15:08

shelends

Hussain)**
(Shelendra)**
3G_ALU_Integ_UAE;
OKASHA,
(Eric);
that can
Table is output of script. No formula is involved.
P1 = RL of path 1
and its value is in right side.
P2 = RL of path 2 and its value is in right side.
VSWR P1/P2*
Value
/11/11
1.78/1.78
/12/12
/1.67/1.67
/11/11
/1.78/1.78
/11/14
/1.78/1.5
Regards,
Sunil
69. 20-May-2015 15:08

shelends

To: DAS, Sunil (Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **; ELMIDANY,
AHMED (AHMED); LU, Wei I (Wei); SHARMA, Shelendra (Shelendra)** CTR **;
ARORA,
Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **
3G_ALU_Integ_UAE;
OKASHA,
(Eric);

that can
: we are inline,
and
RL in dB and it's the output of the PA, script only got it
the VSWR value calculated manually, so I need to confirm with you the
formula used
is as below,
Script Output:
NODEB/IP Address
RUNNING S/W
RRH NAME/IPADDRESS
FPGA VERSION
VSWR P1/P2*
****************************************************************************
******
**********************************************************
ET_AR_U_2136_BuhasaWell/10.235.157.78
MC RRH(10)/192.168.129.1
x3w_al38.bin
/NECI_60220_00100_1R3G09.fh2/NECI_612
20_00100_2R3G09.fh2 /11/11
the formula is
: VSWR = (1+ (10^(RL/20))) / ((10^(RL/20))-1);
Waiting your feedback for the jsutifcation to be submited to customer to

close
this issue,
Thanks,
<image001.gif>
--
BR,
Karim
M: +971 (0)56-354-4568
ONNET:2205 5534
70. 20-May-2015 15:09

shelends
From: DAS SUNIL

Sent: 2015?5?12? 19:50
To: IBRAHIM ABD EL NABY KARIM; PASHA D Hussain; EL-MIDANY AHMED; LU Wei I;
SHARMA
SHELENDRA; ARORA Gaurav; AGRAWAL RITESH
SAYED; 3G ALU INTEG UAE; AHMED NADER; BERIDY AHMED; KHEDR MAHMOUD; OKASHA
TAHER;
CHEN Wenwen; YI Dongchao; CHEN Eric; KUMAR VIJAY K
that can
Lu Wei,
Can you please copy architect? Let us get his view as well.
VSWR = (1+ (10^(RL/20))) / ((10^(RL/20))-1);
Regards,
Sunil
71. 20-May-2015 15:10

shelends
From: CHEN Eric [mailto:Eric.Chen@alcatel-sbell.com.cn]

**;
PASHA, D Hussain (D Hussain)** CTR **; EL-MIDANY, AHMED (AHMED); LU, Wei I
(Wei);
AGRAWAL,
Ritesh (Ritesh)** CTR **; WANG, JUNQIANG (JUNQIANG); MAO, YONGFENG
(YONGFENG);
SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert)
3G_ALU_Integ_UAE;
OKASHA,
TAHER (TAHER); CHEN, Wenwen (Wenwen); YI, Dongchao (Dongchao); Kumar,
Kanipakam
Vijaya K (Vijay)** CTR **; CHEN, Eric (Eric)
that can
Hello all
With architecture, Wang Junqiang's help,

RRH900 3G
we dug out FSD document of MC-
only(F103774), includes compliant matrix. VSWR item as :
R10
RRH2X40-09 supports Tx VSWR Antenna Test with a minimum sensitivity of
1.5:1
Partially Compliant
HW can only support 2:1
Sensitivity close to the antenna connector of the RRH is limited, while the
sensitivity in a few meter distance (i.e. usual feeder length) is quite high
(See
Alf's slides).
Accepted BY PLM
Due to HW limitation, MC-RRH900 can only support 2:1 sensitivity. This is

R&D
commitment, which is accepted by PLM.
I also consultant China NPI expert, Mai Yongfeng and TIS leader: Shan
Chaoyi(in to
list).
Get below information:
1)
sites.
VSWR setting uses default setting: 2.1 and 3 in China MCRRH900 3G
2)
Not see AR complains KPI due to VSWR
3)
and
Vendor also requests VSWR less than some value . It's for antenna
feeder, not for RRH. They use instrument to measure VSWR of antenna and
feeder,
ensure less than the
Not
target as acceptance criterial of install engineering.
reasonable to use RRH to replace instrument to do so sensitive VSWR

measurement.
MC customer document owner: Weber Hubert is OOO. I suppose hard to get

response
recently.
Regards
Eric Chen
72. 20-May-2015 15:11

shelends

To: CHEN, Eric (Eric); DAS, Sunil (Sunil)** CTR **; PASHA, D Hussain (D
Hussain)**
(Shelendra)**
WANG,
JUNQIANG (JUNQIANG); MAO, YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER,
Hubert (Hubert)
3G_ALU_Integ_UAE;
OKASHA,
Kanipakam
that can
Importance: High
Hello Sunil,Pasha,All,
Kindly your support I highly appreciated, we have the below sites cleared
from
VSWR yesterday and no alarms exist, and from the script the VSWR values are
existed the limit?!!, and no alarm exit?!
Site Site Name

VSWR1
VSWR2
Issue
Clearance date To follow
Status @18 May
227
WR_UM_AL_ASTHAN 3G Unavailability (Cell Fail) 17-May VSWR Sec U900
(U900 RRH
replaced)
Clear Since action only Sync alarm
1.6709 1.49852
2008 WR_CCC_ACCOMM_SHAH GAS 3G Unavailability (Cell Fail) 17-May IUB Fail

alarms
& VSWR Sec2 U900 (RRH U900 Replacement)
1.576895
Clear since action 17-05
1.6709
2532 WR_WADI_AL_GHAZALAN
Sec3,4
Clear of
3G Unavailability (Cell Fail) 17-May VSWR
VSWR but down @ 18-05 and clear after recovery

2225 WR_Liwa_Industrial
2100
replaced)
1.6709
1.576895
Clear
1.576895
VSWR Sec3
action only Sync alarm
1.6709 1.6709
2622 DUM_WR_BAINONAH_MZD_ROAD
Since 16-05 1.784888
Thanks,
1.6709
VSWR Sec2 U900 17-May RRH U900 Replaced
2513 WR_Marriage_Hall_MZD
Clear Since
1.784888
1.576895
VSWR Sec2 U2100 & RRH missing 16-May VSWR (RRH
Clear Since action
2138 WR_Ghumaisia
since action
1.784888
17-May VSWR (jumpers changed)
VSWR Sec3
15-May VSWR
clear
<image001.gif>
-BR,
Karim Ibrahim
73. 20-May-2015 15:12

shelends

**;
CHEN, Eric (Eric); PASHA, D Hussain (D Hussain)** CTR **; EL-MIDANY, AHMED
(AHMED); SHARMA, Shelendra (Shelendra)** CTR **; ARORA, Gaurav (Gaurav)**
CTR **;
AGRAWAL, Ritesh (Ritesh)** CTR **; WANG, JUNQIANG (JUNQIANG); MAO, YONGFENG
(YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert)
3G_ALU_Integ_UAE;
OKASHA,
Kanipakam
that can
Hi, Karim
In the IMT (imt_2015-05-19T09h19m58)

VSWR of
trace of logs_VSWR_227, the measured
MC_RRH41/51/61 are normal.
MCRRH_41
Path 1 >>
Measured VSWR
12
(Unit: 1/10)
14
(Unit: 1/10)
11
(Unit: 1/10)
11
(Unit: 1/10)
12
(Unit: 1/10)
11
(Unit: 1/10)
17 (Unit: 1/10)
Path 2 >>
Measured VSWR
MCRRH_51
Path 1 >>
Measured VSWR
Path 2 >>
Measured VSWR
MCRRH_61
Path 1 >>
Measured VSWR
Path 2 >>
Measured VSWR
Threshold is 1.5 and 1.7 as you said.

Warnning VSWR
But I have a question:
15 (Unit: 1/10)
As I know the measured VSWR will only be in unit of 0.1

Why the output VSWR of script is so accurate? How does the script get the
value?
BRs
LuWei
74. 20-May-2015 15:15

shelends

**;
CHEN, Eric (Eric); PASHA, D Hussain (D Hussain)** CTR **; EL-MIDANY, AHMED
CTR **;
(YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert)
3G_ALU_Integ_UAE;
OKASHA,
Kanipakam
that can
Hi, Karim
You don't need to do calculation for VSWR.

The output "measured VSWR" is already VSWR value in unit 0.1
Maybe we need to update the script.
BRs
LuWei
75. 20-May-2015 15:16

shelends
Hi, Karim and all
This is on behalf of Lu Wei because his laptop doesn't work.
First, the script output is misleading.

The second last column is already the actual VSWR, there is no need to do
any
calculation.
It means the last column is not correct and should be removed..
@ Sunil, could you help to request the update of script?
Second, about the threshold setting.

We can have measured VSWR less than 1.5 for most MCRRHs, but we can't
guarantee
the sensitivity for all modules.
Especially for some modules Karim mentioned, even if we check the
connection, VSWR
is still around 1.6.
So from my view, we should use default value RL 6 and 9 as other customers.
BTW as a note:
In IMT, there is a statusdump.txt in MCRRH sub-directory. You can search
"Measured
VSWR" in it then you can see the runtime VSWR and also current threshold
below it
Best Regards,
Yi Dongchao ???
76. 20-May-2015 15:17

shelends

To: LU, Wei I (Wei); KHEDR, MAHMOUD (MAHMOUD); YI, Dongchao (Dongchao)
Cc: PASHA, D Hussain (D Hussain)** CTR **; DAS, Sunil (Sunil)** CTR **;
CHEN, Eric
(Eric); EL-MIDANY, AHMED (AHMED); SHARMA, Shelendra (Shelendra)** CTR **;
ARORA,
Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **; WANG, JUNQIANG
(JUNQIANG); MAO, YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert
(Hubert); INDIA-WCDMA-UTRAN-BE; MERAD, ABDESSAMAD (ABDESSAMAD); REDA, RAMY
(RAMY);
ABDEL-HALIM, SAYED (SAYED); 3G_ALU_Integ_UAE; AHMED, NADER (NADER); BERIDY,
AHMED
(AHMED); OKASHA, TAHER (TAHER); CHEN, Wenwen (Wenwen); Kumar, Kanipakam
Vijaya K
(Vijay)** CTR **

that can
Hello Sunil,
Also please we need to update the script to get the VSWR values from U2100
RRH as
well.
Thanks,
-BR,
Karim Ibrahim
Alcatel-Lucent, Dubai, Etisalat Program
M: +971 (0)56-354-456 || ONNET:2205 5534

To: KHEDR, MAHMOUD (MAHMOUD); YI, Dongchao (Dongchao)
Cc: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; PASHA, D Hussain (D
Hussain)**
CTR **; DAS, Sunil (Sunil)** CTR **; CHEN, Eric (Eric); EL-MIDANY, AHMED
(AHMED);
AGRAWAL,
Ritesh (Ritesh)** CTR **; WANG, JUNQIANG (JUNQIANG); MAO, YONGFENG
(YONGFENG);
SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert); INDIA-WCDMA-UTRAN-BE; MERAD,
ABDESSAMAD (ABDESSAMAD); REDA, RAMY (RAMY); ABDEL-HALIM, SAYED (SAYED);

3G_ALU_Integ_UAE; AHMED, NADER (NADER); BERIDY, AHMED (AHMED); OKASHA, TAHER
(TAHER); CHEN, Wenwen (Wenwen); Kumar, Kanipakam Vijaya K (Vijay)** CTR **
that can
Hi, Mahmoud
The second last column should already be the correct value of current VSWR
measure.
Eg, for below output, the measured VSWR of AbuHasaCampU900 MCRRH(10) is 1.0
(PA1)
and 1.2 (PA2).
You should ignore the 1.92 and 1.67
ET_AR_U_2446_AbuHasaCampU900/10.235.154.184 MC RRH(10)
/192.168.132.1
x3w_al3d.bin
/NECI_60222_00100_1R3G09.fh2/NECI_61222_00100_2R3G09.fh2
/10/12 /
1.92/1.67
@ Sunil, could you ask the script writer to double confirm this?
BRs
LuWei
77. 20-May-2015 15:18

shelends

Sent: 2015?5?20? 16:57
To: LU Wei I; YI Dongchao; DAS SUNIL; PASHA D Hussain; KUMAR VIJAY K

Cc: PASHA D Hussain; CHEN Eric; EL-MIDANY AHMED; SHARMA SHELENDRA; ARORA
Gaurav;
AGRAWAL RITESH; WANG JUNQIANG; MAO Yongfeng; SHAN Chaoyi; Weber Hubert;
INDIA-WCDMA-UTRAN-BE; REDA RAMY; ABDEL-HALIM SAYED; 3G ALU INTEG UAE; AHMED
NADER;
BERIDY AHMED; OKASHA TAHER; CHEN Wenwen; MERAD ABDESSAMAD; WAGDY MANSOUR
AYMAN;
AMAYO EFOSA; KHEDR MAHMOUD
that can
Importance: High
Hi Sunil,Pasha,Lu,
Please we need to confirm and answer the below question so we can close this
topic
and deliver a clear message to our customer:
Is the script not correct and the VSWR value is only 0.1 from the
script output
from PA1,PA2? , you will update it to include the U2100 or not?!.
-
Why the problem of the VSWR solved only by replacing the RRH?
Should we align all the network with the default threshold?
Why limitation is on U900 but not U2100 RRH?
Why we don't see same issue with 2G RRH900? It is the same HW
From where this limitation is coming? We already have several RRHs

running
normally with the new thresholds!
-
What is the benefits of the feature if we have to use default values?
Please find below the count of minor and major alarms for last month ,
Waiting your detailed feedback to close this issue.
Row Labels
Count of Alarm Code
BTS_0206_00052(Minor)
5768
BTS_0207_00051(Major)
73
(blank)
Grand Total
5841
Thanks,
--
78. 20-May-2015 15:19

shelends

To: LU, Wei I (Wei); YI, Dongchao (Dongchao); DAS, Sunil (Sunil)** CTR **;
PASHA,
D Hussain (D Hussain)** CTR **; Kumar, Kanipakam Vijaya K (Vijay)** CTR **
Cc: PASHA, D Hussain (D Hussain)** CTR **; CHEN, Eric (Eric); EL-MIDANY,
AHMED
CTR **;
(YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert); INDIA-WCDMAUTRAN-BE;
REDA, RAMY (RAMY); ABDEL-HALIM, SAYED (SAYED); 3G_ALU_Integ_UAE; AHMED,

NADER
(NADER); BERIDY, AHMED (AHMED); OKASHA, TAHER (TAHER); CHEN, Wenwen
(Wenwen);
MERAD, ABDESSAMAD (ABDESSAMAD); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
AMAYO,
EFOSA (EFOSA); KHEDR, MAHMOUD (MAHMOUD)
that can
Importance: High
Hello Lu,
These is not a BTS names, it's alarm code names,
1-
BTS_0206_00052' VSWR Minor alarm
2-
BTS_0207_00051
' VSWR Major alarms,
The count below for the number of alarms during the last month,
The output from the script is for one day, and the alarms are bouncing and
repeated as per attached HFB,
Row Labels
Count of Alarm Code
BTS_0206_00052(Minor)
5768
BTS_0207_00051(Major)
73
(blank)
Grand Total
5841
Thanks,
-BR,
Karim Ibrahim
79. 20-May-2015 15:20

shelends
From: KHEDR, MAHMOUD (MAHMOUD)

Cc: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; LU, Wei I (Wei); YI,
Dongchao
(Dongchao); PASHA, D Hussain (D Hussain)** CTR **; Kumar, Kanipakam Vijaya K
(Vijay)** CTR **; CHEN, Eric (Eric); EL-MIDANY, AHMED (AHMED); SHARMA,
Shelendra
(Shelendra)** CTR **; ARORA, Gaurav (Gaurav)** CTR **; AGRAWAL, Ritesh
(Ritesh)**
CTR **; WANG, JUNQIANG (JUNQIANG); MAO, YONGFENG (YONGFENG); SHAN, Chaoyi
(Chaoyi); WEBER, Hubert (Hubert); INDIA-WCDMA-UTRAN-BE; REDA, RAMY (RAMY);
AHMED
(AHMED); OKASHA, TAHER (TAHER); CHEN, Wenwen (Wenwen); MERAD, ABDESSAMAD
(ABDESSAMAD); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; AMAYO, EFOSA (EFOSA)
Subject: Re: 1-5692664/MAJOR/9926/UAE-ETC/WCDMA/High rate of VSWR alarms
that can
Hello Sunil,
I'm totally lost!
Do we have issue with HW?

Customer want to put threshold from major 1.5 to critical 1.7... But it
seems "if
I understand well" that most of U900 are above this threshold which is for
me a
quality RED flag on our modules unless if we can prove that it's not from
our HW
Please note that almost all modules are far maximum 5m from Antenna where
short
antenna jumper is used
so I appreciate your support to evaluate our position and give next step
Best regards,
Mahmoud Khedr
Sent from my iPhone
80. 21-May-2015 14:17

shelends
Update to Current Summary: May 21: After changed VSWR threshold value with
correct
load, KPI is good , awaiting customer feedback
81. 21-May-2015 14:17

shelends
May 21: After changed VSWR threshold value with correct load, KPI is good ,
82. 25-May-2015 11:25

shelends
correct
83. 25-May-2015 11:25

shelends
84. 28-May-2015 15:13

shelends
correct
85. 28-May-2015 15:13

shelends
86. 02-Jun-2015 14:29

shelends
Update to Current Summary: June 2: After changed VSWR threshold value with
correct
87. 02-Jun-2015 14:29

shelends
June 2: After changed VSWR threshold value with correct load, KPI is good ,
88. 04-Jun-2015 11:19

shelends

Sent: 2015?5?20? 16:57
To: LU Wei I; YI Dongchao; DAS SUNIL; PASHA D Hussain; KUMAR VIJAY K
Cc: PASHA D Hussain; CHEN Eric; EL-MIDANY AHMED; SHARMA SHELENDRA; ARORA
Gaurav;
AGRAWAL RITESH; WANG JUNQIANG; MAO Yongfeng; SHAN Chaoyi; Weber Hubert;
INDIA-WCDMA-UTRAN-BE; REDA RAMY; ABDEL-HALIM SAYED; 3G ALU INTEG UAE; AHMED
NADER;
BERIDY AHMED; OKASHA TAHER; CHEN Wenwen; MERAD ABDESSAMAD; WAGDY MANSOUR
AYMAN;
AMAYO EFOSA; KHEDR MAHMOUD
that can
Importance: High
Hi Sunil,Pasha,Lu,
Please we need to confirm and answer the below question so we can close this
topic
and deliver a clear message to our customer:
script output from PA1,PA2? , you will update it to include the U2100 or
not?!.
-
RRHs
From where this limitation is coming? We already have several
running normally with the new thresholds!

values?
What is the benefits of the feature if we have to use default
Please find below the count of minor and major alarms for last month ,
Waiting your detailed feedback to close this issue.
Row Labels
Count of Alarm Code
BTS_0206_00052(Minor)
5768
BTS_0207_00051(Major)
73
(blank)
Grand Total
5841
89. 04-Jun-2015 11:20

shelends

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; YI, Dongchao (Dongchao);
DAS,
Sunil (Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **; Kumar,
Kanipakam
Vijaya K (Vijay)** CTR **
AHMED
CTR **;
NADER
(Wenwen);
AMAYO,
that can
Hi, Karim
Could you give us below information before answering your question?
In attached excel, it seems many sites info included.
Inside it, I saw only 3 MCRRH U900 with VSWR exceeding threshold.
And you only highlight that BTS_0206_00052 and BTS_0207_00051 have many VSWR
alarms.
We want to know, what percentage of MCRRH U900 module have such VSWR issue?
Have you done connection check for all these MCRRH with VSWR alarms?
BRs
LuWei
90. 04-Jun-2015 11:20

shelends

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; YI, Dongchao (Dongchao);
DAS,
Sunil (Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **; Kumar,
Kanipakam
Vijaya K (Vijay)** CTR **
AHMED
CTR **;
NADER
(Wenwen);
AMAYO,

that can
Hi, Karim
Please see some inline answer for my part.
script output from PA1,PA2? , you will update it to include the U2100 or
not?!.
[Lu Wei] Where did you see 0.1? The unit of output is 0.1 and so all the
VSWR
values are bigger than 10.
[Lu Wei] We can have measured VSWR less than 1.5 for some MCRRHs, but we
can't
guarantee the sensitivity for all modules.
According to compliance summary, the only guaranteed sensitivity is 2 which
means
the VSWR below 2 is not accurate enough.
[Lu Wei] I hope so.
[Lu Wei] They have totally different HW and SW, of course the VSWR detection
mechanism is different.
[Lu Wei] First, the VSWR detection method for 2G and 3G are different.
Second, do
you know the threshold used for 2G world?
RRHs
From where this limitation is coming? We already have several
running normally with the new thresholds!

[Lu Wei] According to the compliance summary, the limitation is from HW. And
I
think detection mechanism also.
Do you mean 1.5 and 1.7 for "new threshold"?
If yes, I have to say there is no 100% the same HW of course, that should be
the
reason for different behavior for different module.
values?
What is the benefits of the feature if we have to use default
[Lu Wei] The feature will allow you to adjust the threshold, but for the
threshold
value it depends on different module.
BRs
LuWei
91. 04-Jun-2015 11:21

shelends

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; LU, Wei I (Wei); YI,
Dongchao
(Dongchao); PASHA, D Hussain (D Hussain)** CTR **; Kumar, Kanipakam Vijaya K
(Vijay)** CTR **
AHMED
CTR **;
NADER
(Wenwen);
AMAYO,
that can
Karim,
No, 0.1* is not coming out of script. Let us not confuse.

Pasha's
script and share the file. you will see no 0.1* value.
Anyway, I will ask Pasha to send you script again.
Regards,
Sunil
Please run
92. 04-Jun-2015 11:21

shelends

Sent: 20 May 2015 18:37
To: DAS, Sunil (Sunil)** CTR **; LU, Wei I (Wei); YI, Dongchao (Dongchao);
PASHA,
D Hussain (D Hussain)** CTR **; Kumar, Kanipakam Vijaya K (Vijay)** CTR **
AHMED
CTR **;
NADER
(Wenwen);
AMAYO,
that can
Hello Sunil.
I don't mean that the script 0.1*, I mean we should apply 0.1* on the value
come
from the script to get the VSWR..
Attached the output of the script today and the calculated VSWR values,
please
check and confirm.,
Thanks,
-BR,
Karim Ibrahim
M: +971 (0)56-354-456 || ONNET:2205 5534
93. 04-Jun-2015 11:22

shelends

Sent: Thursday, May 21, 2015 5:25 AM
To: KHEDR, MAHMOUD (MAHMOUD); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **;
PASHA,
D Hussain (D Hussain)** CTR **; DAS, Sunil (Sunil)** CTR **; YI, Dongchao
(Dongchao); Kumar, Kanipakam Vijaya K (Vijay)** CTR **
Cc: CHEN, Eric (Eric); EL-MIDANY, AHMED (AHMED); SHARMA, Shelendra
(Shelendra)**
WANG,
Hubert (Hubert); INDIA-WCDMA-UTRAN-BE; REDA, RAMY (RAMY); ABDEL-HALIM, SAYED
(SAYED); 3G_ALU_Integ_UAE; AHMED, NADER (NADER); BERIDY, AHMED (AHMED);
OKASHA,
TAHER (TAHER); CHEN, Wenwen (Wenwen); MERAD, ABDESSAMAD (ABDESSAMAD); WAGDY
MANSOUR, AYMAN (AYMAN)** CTR **; AMAYO, EFOSA (EFOSA)

that can
Hi, Pasha, Sunil
For the VSWR, could you tell me which value from MCRRH in the script?
Is it from the "measured VSWR" in command "L1DPDCTRLStatus_Show"?

If yes, as I said it should be already VSWR value, not RL.
BRs
LuWei
94. 04-Jun-2015 11:22

shelends

Sent: 21 May 2015 12:15
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; LU, Wei I (Wei); KHEDR,
MAHMOUD
(MAHMOUD); PASHA, D Hussain (D Hussain)** CTR **; YI, Dongchao (Dongchao);
Kumar,
Kanipakam Vijaya K (Vijay)** CTR **
(Shelendra)**
WANG,

OKASHA,
that can
Script is using L1DPDCTRLStatus_Show. As Lu Wei said, it should be then

measured
VSWR.
Currently is it 1.5 for Level2 and 1.7 for L3.
I looked at script output today. if we go with 1.5 and 1.7 VSWR value, only
4 RRH
are showing such issue. However, few nodeBs were not reachable.
like
I would
pasha to send list nodeBs that do not have correct IP.
Karim,
Please fill up IP send us. we will make complete nodeB list and send you.
Let us
get one more level of script output.
seeing
the script data.
Regards,
Sunil
I will suggest the solution after
95. 04-Jun-2015 11:22

shelends

To: PASHA, D Hussain (D Hussain)** CTR **; DAS, Sunil (Sunil)** CTR **; LU,
Wei I
(Wei); KHEDR, MAHMOUD (MAHMOUD); YI, Dongchao (Dongchao); Kumar, Kanipakam
Vijaya
K (Vijay)** CTR **
(Shelendra)**
WANG,
OKASHA,
that can
Dears,
I informed you 2 times before that not all the created sites on the network
are
integrated and have OAM IPs, that's why you have blank IPs on the script
output,
NOW to highlight the last finds,
To highlight again as confirmed from LUwi, the script output is OK, and give
*0.1
of the VSWR values,
To close this issue, please answer this questions:
Can you deliver a document/presenation to be shared with the

customer to
approve that we should change the threshold value to the default.
-
Can you confirm why the VSWR alarms are bouncing?!.
after
As we mentioned in the beginning the VSWR is cleared on some sites
replacing the
MC-RRH, are there a clear RC for this?!.
Please find below audit
Created site ' 486
Integrated ' 287 , which is the same number of IP,
96. 04-Jun-2015 11:23

shelends
From: DAS SUNIL

Sent: 2015?5?21? 16:25
To: IBRAHIM ABD EL NABY KARIM; PASHA D Hussain; LU Wei I; KHEDR MAHMOUD; YI
Dongchao; KUMAR VIJAY K
Cc: CHEN Eric; EL-MIDANY AHMED; SHARMA SHELENDRA; ARORA Gaurav; AGRAWAL
RITESH;
WANG JUNQIANG; MAO Yongfeng; SHAN Chaoyi; Weber Hubert; INDIA-WCDMA-UTRANBE; REDA
RAMY; ABDEL-HALIM SAYED; 3G ALU INTEG UAE; AHMED NADER; BERIDY AHMED; OKASHA
TAHER; CHEN Wenwen; MERAD ABDESSAMAD; WAGDY MANSOUR AYMAN; AMAYO EFOSA
that can
Thanks Karim. We are clear on IP address.
1.
We will make PPT.
we will also check customer document; what was
recommended.
2.
Replacing RRH is NOT RC and is NOT recommended.
3.
As I understood, VSWR alarm did not bounce once it comes. Please
confirm.
Regards,
Sunil
97. 04-Jun-2015 11:23

shelends

Sent: jeudi 21 mai 2015 10:49
**;
PASHA, D Hussain (D Hussain)** CTR **; KHEDR, MAHMOUD (MAHMOUD); YI,
Dongchao
(Dongchao); Kumar, Kanipakam Vijaya K (Vijay)** CTR **; IRVING, David
(David);
ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei)

(Shelendra)**
WANG,
OKASHA,
that can
Karim
First, I agreed with Sunil that replacing RRH is not RC.

Each time you replace RRH, the connection is changed and there will be
difference
between HW.
Second for the bouncing, the VSWR may be impacted by output power,
temperature and
frequency.
So from my view, if the measured VSWR happened to be around the threshold
you will
see bouncing.
Third for the VSWR sensitivity, I involve MCRRH 900 PLM David to confirm.
@ David
We have some MCRRH 900 on ETC site.

The customer set a low alarm threshold 1.5, then they found for some module
the
VSWR alarms can't be cleared no matter how to check the connection.
We found in our compliance summary of MCRRH 900, it says "HW can only
support 2:1
sensitivity".
R10
RRH2X40-09 supports Tx VSWR Antenna Test with a minimum sensitivity of
1.5:1
Partially Compliant
HW can only support 2:1
Sensitivity close to the antenna connector of the RRH is limited, while the
sensitivity in a few meter distance (i.e. usual feeder length) is quite high
(See
Alf's slides).
Accepted BY PLM
Does it mean for MCRRH we should not use threshold lower than 2.0?
BRs
LuWei
98. 04-Jun-2015 11:24

shelends

Sent: 21 May 2015 19:11
To: PASHA, D Hussain (D Hussain)** CTR **; MERAD, ABDESSAMAD (ABDESSAMAD);
LU, Wei
I (Wei); DAS, Sunil (Sunil)** CTR **; KHEDR, MAHMOUD (MAHMOUD); YI, Dongchao

(David);
ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei)
(Shelendra)**
WANG,
OKASHA,
TAHER (TAHER); CHEN, Wenwen (Wenwen); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
AMAYO, EFOSA (EFOSA)
that can
Thanks pasha, Please provide it in XML format so I can import to NPO, Please
also
send me the indicator to check traffic with VSWR as discussed,
Hello all,
Kindly find a detailed audit done on the VSWR alarms from 15 May till today,
as
discussed I take the highest 3 sites and I changed the threshold as per
below and
will monitor the alarms and will send you the KPIS, HFB and script output
next
Sunday morning,
BTS name
BTS_0206_00052 (VSWR Minor)
Configuration
BTS_0207_00052 (VSWR Major)
EM BTSEquipmentEO_AR_U_2338_EasternAlMariah 285
EM BTSEquipmentET_AR_U_243_ShamsU900349
U900
EM BTSEquipmentET_AR_U_2767_Ghumaisia1
605
U900+U2100
U900
New threshold:
RL(dB)
8
2.32
10
1.92
VSWR
Thanks,
-BR,
Karim Ibrahim
99. 04-Jun-2015 11:24

shelends

To: PASHA, D Hussain (D Hussain)** CTR **; DAS, Sunil (Sunil)** CTR **
(Shelendra)**
WANG,
OKASHA,
MERAD, ABDESSAMAD (ABDESSAMAD); LU, Wei I (Wei); DAS, Sunil (Sunil)** CTR
**;
KHEDR, MAHMOUD (MAHMOUD); YI, Dongchao (Dongchao); Kumar, Kanipakam Vijaya K
(Vijay)** CTR **; IRVING, David (David); ZHANG, Xu B (Xu); QIAN, Pengfei
(Pengfei); AMAYO, EFOSA (EFOSA)
that can
Hello Pasha,Sunil,
Kindly note that the 3 sites are stable of minor VSWR alarms since the
modification of the threshold,
Attached the required KPIs to check,
Please update about your investigation regarding the temperature values

affecting
the VSWR , and if the traffic trend is variable of VSWR value or not.
Also please as we mentioned before we need to update the script to get the
VSWR
values of U2100, when can we receive the updated one?!.
Thanks,
-BR,
Karim Ibrahim
100. 04-Jun-2015 11:24

shelends
From: ARORA, Gaurav (Gaurav)** CTR **

Hussain)**
CTR **
(Shelendra)**
CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **; WANG, JUNQIANG (JUNQIANG); MAO,
YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert);
INDIA-WCDMA-UTRAN-BE; REDA, RAMY (RAMY); ABDEL-HALIM, SAYED (SAYED);
3G_ALU_Integ_UAE; AHMED, NADER (NADER); BERIDY, AHMED (AHMED); DAS, Sunil
(Sunil)** CTR **; OKASHA, TAHER (TAHER); CHEN, Wenwen (Wenwen); WAGDY
MANSOUR,
AYMAN (AYMAN)** CTR **; MERAD, ABDESSAMAD (ABDESSAMAD); LU, Wei I (Wei);
DAS,
Sunil (Sunil)** CTR **; KHEDR, MAHMOUD (MAHMOUD); YI, Dongchao (Dongchao);
Kumar,
Kanipakam Vijaya K (Vijay)** CTR **; IRVING, David (David); ZHANG, Xu B
(Xu);
QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA)
that can
Hi Karim ,
As the
purpose of the AR
has been solved , I will
request
requirement of the script for U2100 please open a new AR .
that for the
Thanks and regards

Gaurav Arora
+91 9503055691
101. 04-Jun-2015 11:25

shelends

Sent: Monday, May 25, 2015 11:29 AM
To: ARORA, Gaurav (Gaurav)** CTR **; IBRAHIM ABD EL NABY, Karim (Karim)**
CTR **;
PASHA, D Hussain (D Hussain)** CTR **
(Shelendra)**
CTR **; AGRAWAL, Ritesh (Ritesh)** CTR **; WANG, JUNQIANG (JUNQIANG); MAO,
YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert);
(TAHER); CHEN, Wenwen (Wenwen); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
MERAD,
ABDESSAMAD (ABDESSAMAD); LU, Wei I (Wei); KHEDR, MAHMOUD (MAHMOUD); YI,
Dongchao
(David);
ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA)
that can
Karim,
We will check KPI and come back.
As Gaurav said, we can't club 2100 RRH to U900 AR because we have made
advanced
with our investigation on U900. We are almost in closer
I
would request you to raise new AR for U2100.
investigate
stage.
Therefore,
We will support you to
in U2100 through new AR.
Regards,
Sunil
102. 04-Jun-2015 11:25

shelends
From: DAS SUNIL

Sent: 2015?5?26? 13:08
To: LU Wei I; KHEDR MAHMOUD; AGRAWAL RITESH; IBRAHIM ABD EL NABY KARIM
Cc: CHEN Eric; EL-MIDANY AHMED; SHARMA SHELENDRA; WANG JUNQIANG; MAO
Yongfeng;
SHAN Chaoyi; Weber Hubert; INDIA-WCDMA-UTRAN-BE; REDA RAMY; ABDEL-HALIM
SAYED; 3G
ALU INTEG UAE; AHMED NADER; BERIDY AHMED; OKASHA TAHER; CHEN Wenwen; WAGDY
MANSOUR
AYMAN; MERAD ABDESSAMAD; YI Dongchao; KUMAR VIJAY K; IRVING David; ZHANG Xu
B;
QIAN Pengfei; AMAYO EFOSA; ARORA Gaurav; PASHA D Hussain; XU Haili
that can
Lu Wei
and Dave,
If there is tolerance of +/- 0.5, we may have to consider upper threshold

very
carefully.
For example:
1.
Actual VSWR measurement is 2.5 but showing 3.0 in RRH, it is okay.
2.
Actual is 3.0 but showing 2.5, it is wrong and dangerous for PA.
Since network shows 1.92 is higher VSWR, I would suggested to define

threshold 2.1
for minor alarm and 2.5 for major alarm. This
in
will give room for PA to work
healthy condition.
Let me know your advice.
Regards,
Sunil
103. 04-Jun-2015 11:26

shelends

**; LU,
Wei I (Wei); KHEDR, MAHMOUD (MAHMOUD); AGRAWAL, Ritesh (Ritesh)** CTR **

(Shelendra)**
AHMED
(AHMED); OKASHA, TAHER (TAHER); CHEN, Wenwen (Wenwen); WAGDY MANSOUR, AYMAN
(AYMAN)** CTR **; MERAD, ABDESSAMAD (ABDESSAMAD); YI, Dongchao (Dongchao);
Kumar,
(Xu);
QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA); ARORA, Gaurav (Gaurav)** CTR
**;
XU, HAILI (HAILI)
that can
Hi All,
Please find the attached script. Steps to be followed before running the
script.
Note: first delete the existing script from WMS server

command:
cd /home/oamops/
command: rm -rf rrh_version*
Steps:
=========

directory

4. Please run get_iplist.sh script 1st.
command: ./scripts/get_iplist.sh
5. Once 4th step is completed successful, then please run

nodeB_rrh_version-match.pl script.
command: ./scripts/nodeB_rrh_versionmatch.pl
Step 5 will take time to complete (depending on the list of NodeB in WMS
server).
Once nodeB_rrh_version-match.pl completed, it will create "logs" directory

in the
current directory
(i.e. /home/oamops/rrh_version/).
If you are sending any logs related to this script then please send "logs"
directory.
BR,
Pasha
104. 04-Jun-2015 11:27

shelends

To: PASHA, D Hussain (D Hussain)** CTR **; DAS, Sunil (Sunil)** CTR **; LU,
Wei I
(Wei); KHEDR, MAHMOUD (MAHMOUD); AGRAWAL, Ritesh (Ritesh)** CTR **
(Shelendra)**
AHMED
Kumar,
(Xu);
**;
XU, HAILI (HAILI)
that can
Hello Pasha,
Many thanks for your usual support, but our request is also including that
the
script to be added to the crotab to be runned automatically every day
morning
about 4am,
Can you please modify the steps to add the script to the crontab?
Action taken and progress:

U900
On the AR-1-5692664 we already received from the TSO the script for
MC-RRH , we need modify it to add the U2100 RRHs, and to know how to add it
to the
crontab of the WMS to be generated automatically on daily based every
morning,
Thanks,
-BR,
Karim Ibrahim
105. 04-Jun-2015 11:27

shelends

Sent: 01 June 2015 12:07
To: PASHA, D Hussain (D Hussain)** CTR **; LU, Wei I (Wei); KHEDR, MAHMOUD
(MAHMOUD); AGRAWAL, Ritesh (Ritesh)** CTR **; DAS, Sunil (Sunil)** CTR **
(Shelendra)**
AHMED

Kumar,
(Xu);
**;
XU, HAILI (HAILI)
that can
Hello Pasha,all.
The script is working fine as attached and generated automatically today,
For the VSWR of U2100 , we will take it directly from the script as
attached, no
need for any modification yes?!.
Please Pasha, as I told you

also to
before we need to add the get_Iplist script
the crontab to run before the main script, so please send me the modified
script.
Karim.
106. 04-Jun-2015 11:28

shelends
From: Kumar, Kanipakam Vijaya K (Vijay)** CTR **

Sent: Monday, June 1, 2015 11:13 AM
Hussain)**
CTR **; LU, Wei I (Wei); KHEDR, MAHMOUD (MAHMOUD); AGRAWAL, Ritesh
(Ritesh)** CTR
**; DAS, Sunil (Sunil)** CTR **
(Shelendra)**
AHMED
IRVING,
David (David); ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA
(EFOSA);
ARORA, Gaurav (Gaurav)** CTR **; XU, HAILI (HAILI)
that can
Hi Karim,
Here is the updated script. Both "get_iplist.sh" and "nodeB_rrh_versionmatch.pl"
are added to crontab.
Note: first delete the existing script from WMS server

command:
cd /home/oamops/rrh_version
command:
./scripts/stop.sh
command:
cd /home/oamops/
command: rm -rf rrh_version*
Steps:
=========
directory
4. Please run "start.sh" script
command: ./scripts/start.sh
start script will add the entry in crontab and it will run every day morning
4 o
clock and it generates corresponding logs in ' logs' directory.
5.
command.
If you want to stop the script please run the below

command: ./scripts/stop.sh
If you are sending any logs related to this script then please send "logs"
directory.
Thanks & Regards

-Vijay
107. 04-Jun-2015 11:28

shelends
Sent: Monday, June 01, 2015 3:07 PM

To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; Kumar, Kanipakam Vijaya K
(Vijay)** CTR **; PASHA, D Hussain (D Hussain)** CTR **; LU, Wei I (Wei);
KHEDR,
MAHMOUD (MAHMOUD); AGRAWAL, Ritesh (Ritesh)** CTR **
(Shelendra)**
AHMED
IRVING,
David (David); ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA
(EFOSA);
ARORA, Gaurav (Gaurav)** CTR **; XU, HAILI (HAILI)
that can
Karim,
We will prepare PPT.
I am not sure about customer document.

Is
customer usage doc or UPUG doc?
Regards,
Sunil
What type of doc are you expecting?
108. 04-Jun-2015 11:28

shelends

Sent: Wednesday, June 03, 2015 6:02 PM
To: IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; Kumar, Kanipakam Vijaya K
(Vijay)** CTR **; LU, Wei I (Wei); KHEDR, MAHMOUD (MAHMOUD); AGRAWAL, Ritesh
(Ritesh)** CTR **
(Shelendra)**
(Chaoyi); WEBER, Hubert (Hubert); DAS, Sunil (Sunil)** CTR **;
(TAHER); CHEN, Wenwen (Wenwen); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **;
MERAD,
ABDESSAMAD (ABDESSAMAD); YI, Dongchao (Dongchao); IRVING, David (David);
ZHANG, Xu
B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA); ARORA, Gaurav
(Gaurav)**
CTR **; XU, HAILI (HAILI)
that can
Hi Karim,
Please find the
BR,
attached PPT for your reference.
Pasha
109. 04-Jun-2015 11:29

shelends

Sent: Thursday, June 04, 2015 11:04 AM
To: PASHA, D Hussain (D Hussain)** CTR **
(Shelendra)**
(Chaoyi); WEBER, Hubert (Hubert); IBRAHIM ABD EL NABY, Karim (Karim)** CTR
**;
Kumar, Kanipakam Vijaya K (Vijay)** CTR **; LU, Wei I (Wei); AGRAWAL, Ritesh
(Ritesh)** CTR **; DAS, Sunil (Sunil)** CTR **; INDIA-WCDMA-UTRAN-BE; REDA,
RAMY
(RAMY); ABDEL-HALIM, SAYED (SAYED); 3G_ALU_Integ_UAE; AHMED, NADER (NADER);
BERIDY, AHMED (AHMED); OKASHA, TAHER (TAHER); CHEN, Wenwen (Wenwen); WAGDY
MANSOUR, AYMAN (AYMAN)** CTR **; MERAD, ABDESSAMAD (ABDESSAMAD); YI,
Dongchao
(Dongchao); IRVING, David (David); ZHANG, Xu B (Xu); QIAN, Pengfei
(Pengfei);
AMAYO, EFOSA (EFOSA); ARORA, Gaurav (Gaurav)** CTR **; XU, HAILI (HAILI)
that can
Importance: High
Thanks Pasha for the update..
From the slides "4. U900 have deviation

means
of +/-0.5 for VSWR measurement. It
if the physical VSWR is 1.2, U900 may report measured VSWR 1.7 and raise
alarms in
case threshold less than 1.7 "
Actually, this is very critical for us as the Etisalat want to have the
threshold
@1.5.
This means we will have bouncing U900 on hourly basis which is highly
impacting
the network stability and will not be controlled
Our request here is to improve the U900 RRH sensitivity or the way of alarm
reporting like G900 for example
Please let me know how can we move further for that!
Best regards,
Mahmoud Khedr
110. 04-Jun-2015 11:29

shelends

To: KHEDR, MAHMOUD (MAHMOUD); PASHA, D Hussain (D Hussain)** CTR **
(Shelendra)**
**;
(Ritesh)** CTR **; INDIA-WCDMA-UTRAN-BE; REDA, RAMY (RAMY); ABDEL-HALIM,
SAYED
OKASHA,
MERAD, ABDESSAMAD (ABDESSAMAD); YI, Dongchao (Dongchao); IRVING, David
(David);
ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA); ARORA,
Gaurav
(Gaurav)** CTR **; XU, HAILI (HAILI); SCHWAB, PAUL (PAUL)
that can
Hi Mahmoud,
While product was designed, PLM agreed to have sensitive in the range till
2.1(max) for lower and 3.0 for higher. Since current VSWR 1.92 at max is
within
range, I would say, it is not a product issue.
We have discussed this issue
several weeks and provided explanation and suggestion.
2nd, if customer insists for VSWR value 1.5,

PLM
and sales team.
I believe, we need to involve
I copied Paul Schwab for his comment.
Paul,
Your comment is valuable here. We need to draw a conclusion somewhere.
Regards,
Sunil
111. 04-Jun-2015 11:35

shelends
Update to Current Summary: June 4: Provided all details, script, and

explaination
112. 04-Jun-2015 11:35

shelends
June 4: Provided all details, script, and explaination

feedback
, awaiting customer
113. 11-Jun-2015 12:24

shelends
explaination
114. 11-Jun-2015 12:24

shelends
, awaiting customer
feedback
115. 12-Jun-2015 11:54

shelends

Sent: Friday, June 05, 2015 6:30 PM
To: DAS, Sunil (Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **;
SCHWAB,
PAUL (PAUL)
(Shelendra)**
**;
SAYED
OKASHA,
(David);
Gaurav
(Gaurav)** CTR **; XU, HAILI (HAILI)
that can
Importance: High
Hello Paul,
Appreciate your update as having such big variance +/-0.5 in VSWR is not
acceptable and lead to bouncing VSWR alarm and outage all over the network
Best regards,
Mahmoud Khedr
116. 12-Jun-2015 11:54

shelends
From: SCHWAB, PAUL (PAUL)

Sent: Monday, June 08, 2015 8:32 PM
To: KHEDR, MAHMOUD (MAHMOUD); DAS, Sunil (Sunil)** CTR **; PASHA, D Hussain
(D
Hussain)** CTR **; IRVING, David (David); EDER, Thomas (Thomas)
(Shelendra)**
**;
SAYED
OKASHA,
(David);
Gaurav
that can
Mahmoud,
If you want to request a product evolution, you need to address it to the

PLM
prime: Dave Irving ,with the help of Thomas Eder. Unfortunately Dave is not
available this week. Anyway product evolution will take a lot of time.
I think the first thinks is to explain why you are not happy with the
product, and
why it is specific to this customer, and there is no issue with other
customers.
BR
Paul
117. 12-Jun-2015 11:55

shelends

Sent: Tuesday, June 09, 2015 11:36 AM
To: SCHWAB, PAUL (PAUL); DAS, Sunil (Sunil)** CTR **; PASHA, D Hussain (D
Hussain)** CTR **; IRVING, David (David); EDER, Thomas (Thomas)
(Shelendra)**
**;
SAYED
OKASHA,

(David);
Gaurav
that can
Dear Paul,
As explained before, the customer is not happy because of bouncing VSWR on

the
U900 sites
The customer is putting the VSWR threshold @ 1.5 for major and 1,7 for
critical
And we come to know that the MCRRH VSWR accuracy is +/-0.5
This means if We have actual VSWR @ 1.2. the MCRRH can report 1.2+0.5 ' 1.7
In this case the module comes down as it reached the critical threshold
this is simply the issue
and why no complains from other customer, I don't know, but may be they are
using
different VSWR threshold
Hope this clarify our issue here
Best regards,
Mahmoud Khedr
118. 12-Jun-2015 11:55

shelends
From: EDER, Thomas (Thomas)

Sent: Friday, June 12, 2015 1:16 PM
To: KHEDR, MAHMOUD (MAHMOUD); SCHWAB, PAUL (PAUL); DAS, Sunil (Sunil)** CTR
**;
PASHA, D Hussain (D Hussain)** CTR **; IRVING, David (David)
(Shelendra)**
**;
SAYED
OKASHA,
(David);
Gaurav
that can
Mahmoud,
I'll take the point together with Dave and get back to you in the course of
next
week.
We'll very likely need guidance from R&D here.
Best Regards,
Thomas
119. 17-Jun-2015 12:57

shelends
explaination
120. 17-Jun-2015 12:57

shelends
, awaiting customer
feedback
121. 19-Jun-2015 12:46

shelends

To: EDER, Thomas (Thomas); SCHWAB, PAUL (PAUL); DAS, Sunil (Sunil)** CTR **;
PASHA, D Hussain (D Hussain)** CTR **; IRVING, David (David)

(Shelendra)**
**;
SAYED
(SAYED); 3G_ALU_Integ_UAE; CHARBONNIER, DOMINIQUE (DOMINIQUE); AHMED, NADER
(Wenwen);
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; MERAD, ABDESSAMAD (ABDESSAMAD); YI,
Dongchao (Dongchao); IRVING, David (David); ZHANG, Xu B (Xu); QIAN, Pengfei
(Pengfei); AMAYO, EFOSA (EFOSA); ARORA, Gaurav (Gaurav)** CTR **; XU, HAILI
(HAILI)
that can
Importance: High
Dear Thomas,
Appreciate your update please
Best regards,
Mahmoud Khedr
122. 25-Jun-2015 20:04

shelends
From: <KHEDR>, "MAHMOUD (MAHMOUD)" <Mahmoud.Khedr@alcatel-lucent.com>
Date: Monday 22 June 2015 22:43

To: Thomas Eder <thomas.eder@alcatel-lucent.com>, "SCHWAB, PAUL (PAUL)"
<paul.schwab@alcatel-lucent.com>, "DAS, Sunil (Sunil)** CTR **"
<sunil.das@alcatel-lucent.com>, "PASHA, D Hussain (D Hussain)** CTR **"
<d_hussain.pasha@alcatel-lucent.com>, David Irving
<david.irving@alcatel-lucent.com>, "CHARBONNIER, DOMINIQUE (DOMINIQUE)"
<dominique.charbonnier@alcatel-lucent.com>
Cc: "CHEN, Eric (Eric)" <eric.chen@alcatel-sbell.com.cn>, "EL-MIDANY, AHMED
(AHMED)" <Ahmed.El-Midany@alcatel-lucent.com>, "SHARMA, Shelendra
(Shelendra)**
CTR **" <shelendra.sharma@alcatel-lucent.com>, "WANG, JUNQIANG (JUNQIANG)"
<junqiang.wang@alcatel-sbell.com.cn>, "MAO, YONGFENG (YONGFENG)"
<yongfeng.mao@alcatel-sbell.com.cn>, "SHAN, Chaoyi (Chaoyi)"
<chaoyi.shan@alcatel-sbell.com.cn>, Hubert WEBER
<hubert.weber@alcatel-lucent.com>, "IBRAHIM ABD EL NABY, Karim (Karim)** CTR
**" <karim.ibrahim@alcatel-lucent.com>, "Kumar, Kanipakam Vijaya K (Vijay)**
CTR **" <vijay.k.kumar@alcatel-lucent.com>, "LU, Wei I (Wei)"
<wei.i.lu@alcatel-sbell.com.cn>, "AGRAWAL, Ritesh (Ritesh)** CTR **"
<ritesh.agrawal@alcatel-lucent.com>, INDIA-WCDMA-UTRAN-BE
<india-wcdma-utran-be@alcatel-lucent.com>, "REDA, RAMY (RAMY)"
<ramy.reda@alcatel-lucent.com>, "ABDEL-HALIM, SAYED (SAYED)"
<Sayed.Abdel-Halim@alcatel-lucent.com>, 3G_ALU_Integ_UAE
<3g_Alu_Integ_Uae@alcatel-lucent.com>, "CHARBONNIER, DOMINIQUE (DOMINIQUE)"
<dominique.charbonnier@alcatel-lucent.com>, "AHMED, NADER (NADER)"
<Nader.Ahmed@alcatel-lucent.com>, "BERIDY, AHMED (AHMED)"
<Ahmed.Beridy@alcatel-lucent.com>, "OKASHA, TAHER (TAHER)"
<Taher.Okasha@alcatel-lucent.com>, "CHEN, Wenwen (Wenwen)"
<wenwen.chen@alcatel-sbell.com.cn>, "WAGDY MANSOUR, AYMAN (AYMAN)** CTR **"
<Ayman.Wagdy@alcatel-lucent.com>, "MERAD, ABDESSAMAD (ABDESSAMAD)"

<abdessamad.merad@alcatel-lucent.com>, "YI, Dongchao (Dongchao)"
<dongchao.yi@alcatel-sbell.com.cn>, David Irving
<david.irving@alcatel-lucent.com>, "ZHANG, Xu B (Xu)"
<xu.b.zhang@alcatel-sbell.com.cn>, "QIAN, Pengfei (Pengfei)"
<pengfei.qian@alcatel-sbell.com.cn>, "AMAYO, EFOSA (EFOSA)"
<efosa.amayo@alcatel-lucent.com>, "ARORA, Gaurav (Gaurav)** CTR **"
<g.arora@alcatel-lucent.com>, XU Haili <haili.xu@alcatel-sbell.com.cn>,
"HUSSEIN, HANY (HANY)" <Hany.Hussein@alcatel-lucent.com>
that can
Dear Support and PLM team,
Situation is beyond critical with such weak VSWR accuracy
We got customer escalation as we are not able to control the VSWR in the
network
On daily basis we have several outages on the network due to VSWR which is
highly
bouncing as explained below with +/- 0.5 accuracy
Customer is blocking our RFS which is ~4 MEUR + risk of project blocking as

well
AR is open since more than two months without acceptable solution and we
need to
go with critical CCI
Thanks Dominique to support to go with a CCI

In Summary, Our customer put the threshold @ 1.5 as minor and 1.7 as Major
"outage"
With MCRRH in U900, the accuracy is +/- 0.5 where we have bouncing VSWR
alarms and
outages as it can jump from 1.2 to 1.7 because of this accuracy
Looking for team support to have a solution for the critical situation we
have
Best regards,
Mahmoud Khedr
123. 25-Jun-2015 20:05

shelends
From: EDER, Thomas (Thomas)

Sent: mardi 23 juin 2015 11:46
To: KHEDR, MAHMOUD (MAHMOUD); SCHWAB, PAUL (PAUL); DAS, Sunil (Sunil)** CTR
**;
PASHA, D Hussain (D Hussain)** CTR **; IRVING, David (David); CHARBONNIER,
DOMINIQUE (DOMINIQUE)
(Shelendra)**
**;
SAYED

(Wenwen);
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; MERAD, ABDESSAMAD (ABDESSAMAD); YI,
(HAILI); HUSSEIN, HANY (HANY)
that can
Importance: High
Mahmoud,
we discussed this item internally. As per R&D feedback there seems to be no

space for improvement with this Hardware: "MC 900M HW is designed to only
allow
around 2:1 sensitivity"
All I got is the ppt file in the attachment.
In addition, I'd like to ask whether it's considerable that we take an
adjustment
of the Alarm Level Threshold into account, given the fact that we talk about
HW
restrictions?
Xu Haili, Zhang Yong: Feel free to comment further here, in case it is

required.
Best Regards,
Thomas
124. 25-Jun-2015 20:06

shelends
From: MERAD, ABDESSAMAD (ABDESSAMAD)

Sent: mardi 23 juin 2015 12:26
To: EDER, Thomas (Thomas); KHEDR, MAHMOUD (MAHMOUD); SCHWAB, PAUL (PAUL);
DAS,
Sunil (Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **; IRVING, David
(David); CHARBONNIER, DOMINIQUE (DOMINIQUE)
(Shelendra)**
**;
SAYED
(Wenwen);
WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; YI, Dongchao (Dongchao); IRVING,
David
(David); ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA);
ARORA,
Gaurav (Gaurav)** CTR **; XU, HAILI (HAILI); HUSSEIN, HANY (HANY)
that can
HI Thomas / all,
We cannot comeback to customer without solution and need to propose

something
following their escalation: SW or HW changes? HW roadmap? Other immediate

solution? Other ALU product that will guaranty the threshold ? I'm not
mentioning
the threshold levels changes as they are part of Etisalat "standard" and
applicable to all other vendors.
Mahmoud is mentioning below direct impact on RFS, I think we need to

highlight the
risk of even more damageable impacts since customer will perceive ALU u900
mcrrh
as not complying with their requirement and standard!
thanks
Best Regards
125. 25-Jun-2015 20:06

shelends
From: CHARBONNIER, DOMINIQUE (DOMINIQUE)

Sent: 23 June 2015 12:41
To: MERAD, ABDESSAMAD (ABDESSAMAD); EDER, Thomas (Thomas); KHEDR, MAHMOUD
(MAHMOUD); SCHWAB, PAUL (PAUL); DAS, Sunil (Sunil)** CTR **; PASHA, D
Hussain (D
Hussain)** CTR **; IRVING, David (David)
(Shelendra)**
**;

SAYED
OKASHA,
YI,
(HAILI); HUSSEIN, HANY (HANY); EUVE, FRANCIS (FRANCIS); DONG, Qing
(Christine)
that can
Adding Christine Dong + Francis Euve (BL Quality)
Dominique Charbonnier
Wireless EMEA RBC - RPMO
Post-Sales Transformation
Customer Issues Predictive Mgmt
M:
T:
+33 6 15 73 84 25
+33 1 60 40 47 98
France - Villarceaux
dominique.charbonnier@alcatel-lucent.com
126. 25-Jun-2015 20:06

shelends
From: IRVING, David (David)

Sent: 24 June 2015 13:32
To: CHARBONNIER, DOMINIQUE (DOMINIQUE); MERAD, ABDESSAMAD (ABDESSAMAD);

EDER,
Thomas (Thomas); KHEDR, MAHMOUD (MAHMOUD); SCHWAB, PAUL (PAUL); DAS, Sunil
(Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **
(Shelendra)**
**;
SAYED
OKASHA,
YI,
Dongchao (Dongchao); ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA
(EFOSA); ARORA, Gaurav (Gaurav)** CTR **; XU, HAILI (HAILI); HUSSEIN, HANY
(HANY);
EUVE, FRANCIS (FRANCIS); DONG, Qing (Christine)
that can
All,
As promised, here are my notes from our meeting today:
First, for clarity: MC-RRH is not intended to be a precision measurement

tool for
VSWR. It's intended to be an RRH which includes a tool which provides an
indication to the operator that there may be issues with their antenna
system, and
a tool to protect itself when it sees conditions that could cause damage.
The first tool is the level 2, warning alarm. It should be set up after the
site
has been installed and good antenna and feeder connections and performance
have
been proven. It should be set at a level which provides no alarms with this
known
good site. It's intended that if the site degrades, it will trigger an alarm
for
the operator to investigate and correct any issues found. ALU recommendation
is
that it is left at the default value of 9dB.
The second tool is the level 3, critical alarm. It is intended to prevent

damage
to the RRH should excessive return power be received. There is no point in
setting
this at a more sensitive level than needed, as this will simply result in
excessive down-time. ALU recommendation is that it is left at the default
value of
6dB.
It should be noted that measurements of VSWR/ return loss are more difficult
when
the problem is close to the measurement point (the RRH), and measurements
are
easier when the problem is further away from the measurement point. We
should
expect more 'false alarms' when sensitive settings are used with short
cables (by
which I means less than ~5 metres or so). I understand the problem sites
have
short cable lengths around 2-3 metres.
We understand settings more sensitive than default are being used by

Etisalat on
some sites:
Our customer put the threshold @ 1.5 as minor and 1.7 as Major
"outage"
These are equivalent to Return Loss of 14dB (level 2 = warning) and ~11.5dB
(level
3 = critical & PA shutdown). MC-RRH is not designed to support this level of
accuracy with short feeder lengths. It may be able to support it with longer
feeder lengths (I will need some technical help to be more precise).
The original design specification for MC-RRH was to support the two default
thresholds (6dB=3.01 VSWR & 9dB=2.10 VSWR). We do not see these alarms with
sensitive settings and short cables as indicative of a problem with the
product in
general or with individual RRHs. The additional flexibility provided by
feature
159393 'Configurable VSWR Alarm Threshold' is intended to allow increased
sensitivity in appropriate conditions - typically when monitoring of
difficult to
access sites with long feeder lengths. When changed from default, the
settings
chosen should always take into account the product capabilities (VSWR
measurement
tolerance +/-0.5) and site conditions. Those chosen by Etisalat appear too
sensitive.
Actions proposed (I'll need help from development on those assigned to me):
1
Check for differences and gap closure options between 2G and 3G VSWR
measurement
techniques (Dave)
2
Identify the 'functional envelope' of settings and cable lengths that
can be
supported (Dave)
3
We should review the feature and product documentation, and consider
adding
guidance and clarifications (? + Dave).
4
Start to socialise this position with the customer (CT)
I'll send separate mails (reduced address lists) regarding my actions above.
Comments and questions welcomed.
Best regards
Dave
127. 25-Jun-2015 20:07

shelends

Sent: Thursday, June 25, 2015 12:10 PM
To: CHARBONNIER, DOMINIQUE (DOMINIQUE); MERAD, ABDESSAMAD (ABDESSAMAD);
EDER,
Thomas (Thomas); KHEDR, MAHMOUD (MAHMOUD); SCHWAB, PAUL (PAUL); DAS, Sunil
(Sunil)** CTR **; PASHA, D Hussain (D Hussain)** CTR **
(Shelendra)**
**;

SAYED
OKASHA,
YI,
(HANY);
that can
All,
I have a first response from 2G development:

DSP hasn't enabled 2G VSWR for MC-RRH.DSP only enabled 2G VSWR for MC-TRDU.
Please could you explain in more detail what 2Go VSWR monitoring has been
attempted?
Best regards
Dave
128. 25-Jun-2015 20:08

shelends

Sent: Thursday, June 25, 2015 4:46 PM
To: IRVING, David (David); CHARBONNIER, DOMINIQUE (DOMINIQUE); MERAD,
ABDESSAMAD
(ABDESSAMAD); EDER, Thomas (Thomas); SCHWAB, PAUL (PAUL); DAS, Sunil

(Sunil)** CTR
**; PASHA, D Hussain (D Hussain)** CTR **
(Shelendra)**
**;
SAYED
OKASHA,
YI,
(HANY);
that can
Importance: High
Hello David,
Can you please elaborate more about the below statement?
What do you mean by DSP hasn't enabled VSWR for MC-RRH 2G?
For the 2G, we are getting VSWR alarms also, but very few, not bouncing, and
it
was cleared by proper installation not like MC-RRH 900 3G
Best regards,
Mahmoud Khedr
129. 25-Jun-2015 20:09

shelends
, awaiting customer
feedback
130. 25-Jun-2015 20:09

shelends
explaination
131. 29-Jun-2015 09:42

sunilkd
All information and recommendation was sent to local team. Nothing is

pending from
our side.
132. 29-Jun-2015 12:05

ritesh
133. 30-Jun-2015 15:42

gauravarora
134. 02-Jul-2015 18:33

shelends
Update to Current Summary: July 2: Provided all details, script, and

explaination
135. 02-Jul-2015 18:33

shelends
July 2: Provided all details, script, and explaination

feedback
136. 02-Jul-2015 18:36

shelends
, awaiting customer

Sent: 29 June 2015 14:20
To: KHEDR, MAHMOUD (MAHMOUD); IRVING, David (David); CHARBONNIER, DOMINIQUE
(DOMINIQUE); PASHA, D Hussain (D Hussain)** CTR **; EUVE, FRANCIS (FRANCIS);
MOHAMED, GEHAD (GEHAD)
(Shelendra)**
CTR **; WANG, JUNQIANG (JUNQIANG); DAS, Sunil (Sunil)** CTR **; EDER, Thomas
(Thomas); MAO, YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert
(Hubert);
IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; Kumar, Kanipakam Vijaya K
(Vijay)**
CTR **; LU, Wei I (Wei); AGRAWAL, Ritesh (Ritesh)** CTR **; INDIA-WCDMAUTRAN-BE;
NADER
(NADER); BERIDY, AHMED (AHMED); SCHWAB, PAUL (PAUL); CHEN, Wenwen (Wenwen);
WAGDY
MANSOUR, AYMAN (AYMAN)** CTR **; YI, Dongchao (Dongchao); ZHANG, Xu B (Xu);
QIAN,
Pengfei (Pengfei); AMAYO, EFOSA (EFOSA); ARORA, Gaurav (Gaurav)** CTR **;
XU,
HAILI (HAILI); HUSSEIN, HANY (HANY); EUVE, FRANCIS (FRANCIS); DONG, Qing
(Christine)
that can
Dears,
This is the update following today meeting:
Attendees: TO list (David and Thomas excused)

Minutes:
-
Detailed feedback on 3G provided by David already
Last mile is missed with a clear explanation on why 2G modules are not
behaving
the same and having no issue
Slide pack need to be build now for an internal
customer
Actions:
review and com to
Pasha, please to confirm slide pack will be produced by support / when?

David, please to explain more below Mahmoud concern
Abdessamad, new meeting to be arranged tomorrow especially to close above
points
Thanks
Best Regards
137. 02-Jul-2015 18:37

shelends

Sent: mercredi 1 juillet 2015 09:46
To: MERAD, ABDESSAMAD (ABDESSAMAD); KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER,
DOMINIQUE (DOMINIQUE); PASHA, D Hussain (D Hussain)** CTR **; EUVE, FRANCIS
(FRANCIS); MOHAMED, GEHAD (GEHAD)
(Shelendra)**
(Hubert);
(Vijay)**
NADER
WAGDY
QIAN,
XU,
(Christine); Engmann, Frank (Frank)
that can
Abdessamad
While you respond to the customer, we continue our discussion with R&D about
possible future VSWR evolution.
They ask if it is possible to ship some of the replaced RRHs to them for
analysis.
Please could you say how many replaced units there are, and whether this
shipment
could be supported? I propose analysis of 2 units in each of 2 locations total 4
RRHs. Is this possible?
We are working to add some more information to the slide pack, which may
help in
your communication with the customer. I will try to provide this additional
information later today or tomorrow.
With thanks,
Dave
138. 02-Jul-2015 18:38

shelends

Sent: Wednesday, July 01, 2015 1:59 PM
To: IRVING, David (David); KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE
(Shelendra)**
(Hubert);
(Vijay)**
NADER
WAGDY
QIAN,
XU,
that can
Thanks David,
I will double conform below with the team and see how we can manage
thanks
Best Regards
139. 02-Jul-2015 18:38

shelends

Sent: 01 July 2015 13:37
To: MERAD, ABDESSAMAD (ABDESSAMAD); IRVING, David (David); CHARBONNIER,
DOMINIQUE
(Shelendra)**
(Hubert);
(Vijay)**
NADER
WAGDY
QIAN,
XU,

that can
Dear David,
I appreciate if we can include answers for the following example of

questions
which I'm expecting to be raised by customer:
What's different between MC-RRH 900 in 3G mode than 2G mode?
Which design is better MCRRH 900 is 2G or 3G?
is MC-RRH 2100 have same design of MC-RRH 900 3G?
Why no issues for U2100?
Why ALU decided to have unique design for MC-RRH 900 in 3G mode only?
Any benefits of this design?
I'm expecting a lot of such comparison questions between different modules

and
different vendors even... so I prefer to be ready with answers
Best regards,
Mahmoud Khedr
140. 02-Jul-2015 18:38

shelends

To: KHEDR, MAHMOUD (MAHMOUD); MERAD, ABDESSAMAD (ABDESSAMAD); CHARBONNIER,
(FRANCIS); MOHAMED, GEHAD (GEHAD)

(Shelendra)**
(Hubert);
(Vijay)**
NADER
WAGDY
QIAN,
XU,
that can
Mahmoud,
I'll try .... :
Abdessamad:
Another question for you:
The AR text says

High rate of VSWR alarms that can be fixed only by MC-RRH replacement
And alarms are "cleared only by replacing the MC-RRH".
Does this mean:

"
the RRH worked OK, then (with unchanged VSWR settings) later started
to generate
alarms
"
the RRH worked OK, then (at the time the VSWR settings were adjusted
to 1.5-1.7)
started to generate alarms
Do you interpret this to imply:

"
the RRH degrades in operation?
"
the new RRH has a better accuracy than the replaced RRH
Thanks,
Dave
141. 03-Jul-2015 14:05

gauravarora
142. 09-Jul-2015 17:45

shelends

explaination
143. 09-Jul-2015 17:45

shelends

feedback
144. 09-Jul-2015 18:08

shelends
, awaiting customer

Sent: Sonntag, 5. Juli 2015 12:25
To: IRVING, David (David); KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE
(Shelendra)**
(Hubert);
(Vijay)**
NADER
WAGDY
QIAN,
XU,

that can
Irvin,
Both cases were faced but most of them are: MC_RRH VSWR issue appear upon
integration (does not work) and fixed only after MC_RRH replacement.
Kindly note that in all cases the "faulty" and the "replacement" Units have
exactly same reference so expected to be identical, I do not know if it can
be
interpreted as better accuracy or higher sensitivity ?
Best Regards
145. 09-Jul-2015 18:08

shelends
From: Engmann, Frank (Frank)

Sent: lundi 6 juillet 2015 08:16
To: MERAD, ABDESSAMAD (ABDESSAMAD); IRVING, David (David); KHEDR, MAHMOUD
(MAHMOUD); CHARBONNIER, DOMINIQUE (DOMINIQUE); PASHA, D Hussain (D
Hussain)** CTR
**; EUVE, FRANCIS (FRANCIS); MOHAMED, GEHAD (GEHAD)
(Shelendra)**
(Hubert);
(Vijay)**
NADER
WAGDY
QIAN,
XU,
(Christine)
that can
Please can I have the information about the HW variants (3BK number + Serial
number) of the MC-RRH of the one we replace and the one we install. I think
we
should identify whether there are HW differences, e.g. in the isolator.
Frank
146. 09-Jul-2015 18:09

shelends
From: MERAD ABDESSAMAD

Sent: 2015?7?8? 4:06
To: ENGMANN Frank; IRVING David; KHEDR MAHMOUD; CHARBONNIER DOMINIQUE; PASHA
D
Hussain; EUVE FRANCIS; MOHAMED GEHAD
Cc: CHEN Eric; EL-MIDANY AHMED; SHARMA SHELENDRA; WANG JUNQIANG; DAS SUNIL;
Eder
Thomas; MAO Yongfeng; SHAN Chaoyi; Weber Hubert; IBRAHIM ABD EL NABY KARIM;
KUMAR
VIJAY K; LU Wei I; AGRAWAL RITESH; INDIA-WCDMA-UTRAN-BE; REDA RAMY; ABDELHALIM
SAYED; 3G ALU INTEG UAE; AHMED NADER; BERIDY AHMED; SCHWAB PAUL; CHEN
Wenwen;
WAGDY MANSOUR AYMAN; YI Dongchao; ZHANG Xu B; QIAN Pengfei; AMAYO EFOSA;
ARORA
Gaurav; XU Haili; HUSSEIN HANY; EUVE FRANCIS; DONG Christine
that can
Importance: High
Frank,
We are collecting the informations with RO teams and will share them asap,
as well
as engaging the shipment of the units.
Can you please summarize the contact and @ where we have to send the units.
Also,
We still did not receive complentary informations requested by mahmoud, this
is
needed to complete the slide pack and communication/readiness to customer
thanks
Best Regards
147. 09-Jul-2015 18:09

shelends
From: CHEN Eric [mailto:Eric.Chen@alcatel-sbell.com.cn]

Sent: Mittwoch, 8. Juli 2015 05:43
To: MERAD, ABDESSAMAD (ABDESSAMAD); Engmann, Frank (Frank); IRVING, David
(David);
KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE (DOMINIQUE); PASHA, D
Hussain (D
Hussain)** CTR **; EUVE, FRANCIS (FRANCIS); MOHAMED, GEHAD (GEHAD)
Cc: EL-MIDANY, AHMED (AHMED); SHARMA, Shelendra (Shelendra)** CTR **; WANG,
JUNQIANG (JUNQIANG); DAS, Sunil (Sunil)** CTR **; EDER, Thomas (Thomas);
MAO,
YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi); WEBER, Hubert (Hubert); IBRAHIM
ABD EL
NABY, Karim (Karim)** CTR **; Kumar, Kanipakam Vijaya K (Vijay)** CTR **;
LU, Wei
I (Wei); AGRAWAL, Ritesh (Ritesh)** CTR **; INDIA-WCDMA-UTRAN-BE; REDA, RAMY
BERIDY, AHMED (AHMED); SCHWAB, PAUL (PAUL); CHEN, Wenwen (Wenwen); WAGDY
MANSOUR,
AYMAN (AYMAN)** CTR **; YI, Dongchao (Dongchao); ZHANG, Xu B (Xu); QIAN,
Pengfei
(Christine);
CHEN, Eric (Eric)
that can
Hello Abdessamad
China contact and shipping info was sent by Yi Dongchao.
Frank
Do you need module shipping?
Regards
Eric
148. 09-Jul-2015 18:10

shelends
From: Engmann, Frank (Frank)

Sent: mercredi 8 juillet 2015 07:53
To: CHEN, Eric (Eric); MERAD, ABDESSAMAD (ABDESSAMAD); IRVING, David
(David);
KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE (DOMINIQUE); PASHA, D
Hussain (D
MAO,
ABD EL
LU, Wei
MANSOUR,
Pengfei
(Christine);
CHEN, Eric (Eric)
that can
Hi Abdessamad and Eric,
As far as I understood up to now we don't expect a HW problem causing the

VSWR
alarms. Thus we don't start any HW root cause analysis. Please tell me when
I'm
wrong.
I was only asking for the HW variants of the replaced modules and
serial
their
numbers for a production check.
If the modules are sent to Nanjing and a HW RCA is necessary later on by us,
then
we can take them over.
Frank
149. 09-Jul-2015 18:11

shelends

To: Engmann, Frank (Frank); CHEN, Eric (Eric); IRVING, David (David); KHEDR,
MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE (DOMINIQUE); PASHA, D Hussain (D

MAO,
ABD EL
LU, Wei
MANSOUR,
Pengfei
(Christine);
CHEN, Eric (Eric)
that can
Importance: High
Thanks,
What about remaining needed feedback, especially for 2G vs. 3G
thanks
Best Regards
150. 10-Jul-2015 10:29

gauravarora
151. 10-Jul-2015 11:12

gauravarora
152. 17-Jul-2015 10:30

shelends
explaination
153. 17-Jul-2015 10:30

shelends
, awaiting customer
feedback
154. 17-Jul-2015 10:32

shelends

Sent: Monday, July 13, 2015 5:22 PM
To: CHEN, Eric (Eric); YI, Dongchao (Dongchao); IRVING, David (David);
KHEDR,
MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE (DOMINIQUE); PASHA, D Hussain (D
Hussain)** CTR **; EUVE, FRANCIS (FRANCIS); MOHAMED, GEHAD (GEHAD); HUA,
JIANNAN
(JIANNAN); JACKYRA, GREGORY (GREGORY)
MAO,
ABD EL
LU, Wei
MANSOUR,
AYMAN (AYMAN)** CTR **; ZHANG, Xu B (Xu); QIAN, Pengfei (Pengfei); AMAYO,
EFOSA
(HANY);
EUVE, FRANCIS (FRANCIS); DONG, Qing (Christine); Engmann, Frank (Frank);
CHEN,
Eric (Eric)
that can
Eric,
Kindly find attached details of first 2 Units under shipment, I will share
delivery details as soon as received
thanks
Best Regards
155. 20-Jul-2015 08:59

gauravarora
156. 23-Jul-2015 10:51

shelends
explaination
157. 23-Jul-2015 10:51

shelends
, awaiting customer
feedback
158. 27-Jul-2015 09:55

shelends
explaination
159. 27-Jul-2015 09:55

shelends

feedback
, awaiting customer
160. 30-Jul-2015 11:40

shelends
explaination
161. 30-Jul-2015 11:40

shelends
, awaiting customer
feedback
162. 06-Aug-2015 13:18

shelends

Sent: Thursday, August 06, 2015 2:48 PM
To: MERAD, ABDESSAMAD (ABDESSAMAD); CHEN, Eric (Eric); YI, Dongchao
(Dongchao);
IRVING, David (David); KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER, DOMINIQUE
MOHAMED, GEHAD (GEHAD); HUA, JIANNAN (JIANNAN); JACKYRA, GREGORY (GREGORY)
Cc: EL-MIDANY, AHMED (AHMED); WANG, JUNQIANG (JUNQIANG); DAS, Sunil
(Sunil)** CTR
**; EDER, Thomas (Thomas); MAO, YONGFENG (YONGFENG); SHAN, Chaoyi (Chaoyi);
WEBER,
Hubert (Hubert); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **; Kumar,
Kanipakam
Vijaya K (Vijay)** CTR **; LU, Wei I (Wei); AGRAWAL, Ritesh (Ritesh)** CTR
**;

3G_ALU_Integ_UAE; AHMED, NADER (NADER); BERIDY, AHMED (AHMED); SCHWAB, PAUL
(PAUL); CHEN, Wenwen (Wenwen); WAGDY MANSOUR, AYMAN (AYMAN)** CTR **; ZHANG,
Xu B
(Xu); QIAN, Pengfei (Pengfei); AMAYO, EFOSA (EFOSA); ARORA, Gaurav
(Gaurav)** CTR
**; XU, HAILI (HAILI); HUSSEIN, HANY (HANY); EUVE, FRANCIS (FRANCIS); DONG,
Qing
(Christine); Engmann, Frank (Frank); CHEN, Eric (Eric)
that can
Hi Eric
Kindly update on this AR.
Regds
Shelendra Sharma
163. 06-Aug-2015 13:18

shelends
Update to Current Summary: Aug 6: Provided all details, script, and

explaination
164. 06-Aug-2015 13:18

shelends

feedback
, awaiting customer
165. 11-Aug-2015 12:38

shelends

Sent: mardi 11 aot 2015 08:45
(Dongchao);
MOHAMED, GEHAD (GEHAD); HUA, JIANNAN (JIANNAN); JACKYRA, GREGORY (GREGORY);
IBRAHIM ABD EL NABY, Karim (Karim)** CTR **
(Sunil)** CTR
WEBER,
Kanipakam
**;
Xu B
(Gaurav)** CTR
Qing
that can
Hi Merad/Karim
Can we close this AR?
Regds
Shelendra Sharma
166. 11-Aug-2015 12:38

shelends

Sent: Tuesday, August 11, 2015 12:58 PM
To: SHARMA, Shelendra (Shelendra)** CTR **; CHEN, Eric (Eric); YI, Dongchao
(Dongchao); IRVING, David (David); KHEDR, MAHMOUD (MAHMOUD); CHARBONNIER,
(FRANCIS); MOHAMED, GEHAD (GEHAD); HUA, JIANNAN (JIANNAN); JACKYRA, GREGORY
(GREGORY); IBRAHIM ABD EL NABY, Karim (Karim)** CTR **
(Sunil)** CTR
WEBER,
Kanipakam
**;
Xu B
(Gaurav)** CTR
Qing
that can
Hi
We are waiting customer feedback on that before closure, WLI is also openso
will
be closed same time according to customer feedback
thanks
Best Regards
167. 13-Aug-2015 14:56

shelends
explaination
168. 13-Aug-2015 14:56

shelends

feedback
169. 20-Aug-2015 15:02

shelends
, awaiting customer
explaination
170. 20-Aug-2015 15:02

shelends

feedback
, awaiting customer
171. 27-Aug-2015 13:15

shelends
explaination
172. 27-Aug-2015 13:15

shelends

Sent: Thursday, August 27, 2015 2:45 PM
(Dongchao);
MOHAMED, GEHAD (GEHAD); HUA, JIANNAN (JIANNAN); JACKYRA, GREGORY (GREGORY);
IBRAHIM ABD EL NABY, Karim (Karim)** CTR **
(Sunil)** CTR
WEBER,
Kanipakam
**;
Xu B
(Gaurav)** CTR
Qing
that can
Hi Merad
Any Update?
Did you get any feedback from customer?
Can we close this long pending AR?
Regds
Shelendra Sharma
-------------------------------------------------------Aug 27: Provided all details, script, and explaination
feedback
Add to log
Resolution
[empty]
End of Assistance Request 1-5692664
, awaiting customer
New AR:
View AR | AR without Proprietary | OLCS

History | States | Assignment | Timetracking
View Attachments | Add Attachment
AR Text Search | More | CARES Home

AR53

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AR53

Uploaded by

Copyright:

Available Formats

New AR:

View AR | AR without Proprietary

Assistance Request 1-5692664

High rate of VSWR alarms that can be fixed only by MC-RRH

Aug 27: Provided all details, script, and explaination

awaiting customer feedback

Pending : Awaiting Receive Log Files / Technical Info

Service Request Remote Technical Support

No Change Request is linked to this AR

ETISALAT ABU DHABI

9926DBS WCDMA-Etisalat : In Service

Emirates Telecommunications Corporation

United Arab Emirates

Karim IBRAHIM ABD EL NABY

Alcatel-Lucent : Open on behalf of Customer

Targets for Restore & Resolve have been extended by 46 hours

242895 (OXIA 627085)

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

This request is entitled to service.

We suspect RRH calibration is not appropriate, We want confirmation of this

We want to know how to update/perform RRH calibration on site? Is it

Contact Given Name

:+971 56 354 4568

Emirates Telecommunications Corporation

: United Arab Emirates

: ETISALAT ABU DHABI

META WLS Access Network (GNE EMEA)

Showing Investigation and Proprietary logs together in time order

Investigation Log and Proprietary Log

Outgoing E-mail to Karim (Karim)** CTR ** IBRAHIM ABD EL NABY

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

Thank you for contacting the Alcatel-Lucent Welcome Center.

GLOBAL WELCOME CENTER

Visit OnLine Customer Support for Contact details

Outgoing E-mail to SHELENDRA (SHELENDRA) SHARMA

GLOBAL WELCOME CENTER

Visit OnLine Customer Support for Contact details

Update to Current Summary: April 22: VSWR alarm on MC RRH

April 22: VSWR alarm on MC RRH

April 22: VSWR alarm on MC RRH, awaiting logs

April 23: VSWR alarm on MC RRH, awaiting logs

From: SHARMA, Shelendra (Shelendra)** CTR **

I have escalated this AR to your work group,.Please help us to assign this

High rate of VSWR alarms that can be fixed only by MC-RRH

Concerned Node B and

RNC: 9926 DBS WCDMA

Concerned component : MC RRH

Time of the issue:

As per log 24th April, but generally it is coming with

and can be fixed on replace MC-RRH

Product release: LR13.3

NODE-B V13D3.0 EBC.01" & "NODE-B V13D3.0 EC2.03"

Patch release: N/A

Reproducible: Yes its happening in 3G+MC-RRH sites after deployment

2. System behavior (high?level + detailed description if relevant):

We have got VSWR LEVEL 2 ALARM ONLY ON 3RD sector,

Specific Problem:RRH VSWR DIV/31 VSWR LEVEL 2,

RRH VSWR DIV/31 VSWR LEVEL 2

Problem:RRH VSWR DIV/31 VSWR LEVEL 2,

Problem:RRH VSWR DIV/31 VSWR LEVEL 2,

RRH VSWR DIV/31 VSWR LEVEL 2

RRH VSWR DIV/31 VSWR LEVEL 2

Problem:RRH VSWR DIV/31 VSWR LEVEL 2,

4481.3620636437 [MsgSeq/37b394b0] RRH

Outgoing E-mail to Karim (Karim) CTR IBRAHIM ABD EL NABY

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

From: SHARMA, Shelendra (Shelendra) CTR