Scribd
Upload
441 views10 pages

CQT Troubleshoooting V1.0

This document provides guidelines for troubleshooting issues that may impact CQT throughput. It describes factors that can affect CQT, including testing devices, radio quality, hardware alarms, transmission issues, and core network problems. It then outlines the requirements for testing devices and CQT. Steps are provided for troubleshooting radio quality, hardware alarms, transmission problems, and includes monitoring criteria for analyzing transmission bandwidth restrictions and packet loss. Finally, a case study example is described where low CQT throughput was due to a configuration issue that was resolved through on-site testing and troubleshooting.

Uploaded by

KhangTran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
441 views10 pages

CQT Troubleshoooting V1.0

This document provides guidelines for troubleshooting issues that may impact CQT throughput. It describes factors that can affect CQT, including testing devices, radio quality, hardware alarms, transmission issues, and core network problems. It then outlines the requirements for testing devices and CQT. Steps are provided for troubleshooting radio quality, hardware alarms, transmission problems, and includes monitoring criteria for analyzing transmission bandwidth restrictions and packet loss. Finally, a case study example is described where low CQT throughput was due to a configuration issue that was resolved through on-site testing and troubleshooting.

Uploaded by

KhangTran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

CQT Troubleshooting GuideLines

CQT Troubleshooting Process


 Factors effect to CQT Throughput:
 1. Testing device and Testing
Computer
 2. Radio Quality( RSRP, SINR)
 3. Hardware alarms, License
eNodeB capacity or Parameter
settings…
 4. Transmission issues: Long
delay, Jitter, packet loss,
bandwidth limit, wrong
configuration setting,...
 5. Core network issues …

HUAWEI TECHNOLOGIES CO., LTD. Page 2


CQT Troubleshooting Process – Device requirements
Test Device Requirements
 Test mobile must support MIMO 4x4, 256 QAM for DL, 64 QAM for UL.
 Test laptop is recommended Intel Core i5 chipset and RAM at least 4GB, PC Performance should set to best performance

CQT Requirements
 FTP Server Bandwidth should greater than or equal
1Gbps
 Ensure that registered AMBR complies with the
UE Testing
requirement for UL and DL
 You are advised to conduct a DT during off-peak
hour to reduce background user’s impact on DT
users.

HUAWEI TECHNOLOGIES CO., LTD. Page 3


CQT Troubleshooting Process – Radio Quality
 Troubleshooting Steps:
 1. Number of Radio Bear(RB), SINR(Signal to interference and Noise Ratio) in PS domain( Request SINR( RS CINR) of test
point > =20)
 2. Implement Uu test( Test from eNodeB to UE) to verify Radio Enroviroment( DSP ALLUEBASICINFO, STR UUDATATST)
 3. Re-DT after get confirmation from TXN teams or OMC KPIs.

MBF LTE1187HHuo´ng dâ~n kiê?m tra troubleshooting trong qua´ tri`nh CQTSSV.msg

HUAWEI TECHNOLOGIES CO., LTD. Page 4


CQT Troubleshooting Process – Hardware Alarms
 Troubleshooting Steps:
 Check whether there are active alarms or faults that effect the service rate. For alarm that have significal impact on
the service rate, clear them first. For alarms whose impact is unknow, you are advised to further analyze whether they
are the root case of service rate exceptions. Then, determine whether to clear the alarms.
 Analyze whether the alarm reporting time and scope match those of the service rate exception. For example, analyze
whether the service rate are abnormal in all the sectors under the eNodeB experiencing an alarm that affects the
whole eNodeB, analyze whether the rate is abnormal in other sections under the eNodeB experiencing an alarm that
affects one of the sectors under the eNodeB.
 For rate deterioration in top N eNodeBs, check whether the new alarms reported on surrounding eNodeBs during the
deterioration period. The number of CEU in the surrounding eNodeBs increase due to site faults.
Common Alarm Lisst
 Solution BBU CPRI Interface Error
BBU CPRI Optical Module Fault
 Clear alarm in sequence based on their impact on the service rate and confirm BBU CPRI Optical Module or Electrical Port Not Ready
BBU Fan Stalled
whether the problem is solved. BBU Optical Module Transmit/Receive Fault
 If alarm could not cleared, report the reason and impact analysis. Cell Unavailable
eNodeB S1 Control Plane Transmission Interruption
Ethernet Link Fault
RF Unit VSWR Threshold Crossed
S1 Interface Fault
System Dynamic Traffic Exceeding Licensed Limit
Transmission Optical Interface Error
Transmission Optical Module Not In Position

HUAWEI TECHNOLOGIES CO., LTD. Page 5


CQT Troubleshooting Process – Transmission Troubleshooting
 Troubleshooting Steps:
 1. Check current hardware alarm( related license, TXN Atenuation,…)
 2. Verify TXN KPIs(FEGE KPIs) from OMC to Restrict transmission
bandwidth, check transmission configurations( cascade, config,..)
 3. Re-DT after get confirmation from TXN teams or OMC KPIs.

 FEGE MAX Speed KPIs: These counters provide the receive rate or transmit rate of
the FEGE Ethernet port at the Link layer in the measurement period. The rates
measured here include the spending of the MAC header and the MAC payload of
the MAC data.

HUAWEI TECHNOLOGIES CO., LTD. Page 6


CQT Troubleshooting Process – Transmission Troubleshooting(Cont.)
 Check whether packet loss or packet disorder occurs. Check the location of the lost packet if packet loss rate
exceeds 0.5%, multi-spot packet capture is recommended.

Scenario Analysis Principle Monitoring criteria


Check the rate over S1 interface and determine whether the problems occur above the eNodeB by running the
UDP Service must be enabled for firewall in operator network
DSP IPPATH command

Restrict transmission bandwidth Check whether the transmission bandwidth is restricted by the command SET UDPLOOP Command Huawei EPC must configured accordingly

user the average value( FEGE.TxMeanSpeed, FEGE.RxMeanSpeed) and Peak value( FEGE.TxMaxSpeed, the eNodeB traffic statistic need to be activated. Operators must provide correct
FEGE.RxMaxSpeed) to check whether the transmission bandwidth is sufficient. information about bandwidth
IP Packet in RX/TX channels on the user plan suddenly increase but the average size of these packet suddenly
the corresponding eNodeB counter must be activated
decreases
the counter Gtpu.RxDropBytes suddenly increase the corresponding eNodeB counter must be activated
Transmission Packet loss The eNodeB must be of eRAN 6.0 or a later version. Huawei EPC must be of PS 9.2 or a
the counter VS.IPPM.Forword.DropMeans suddenly increase
later version
The eNodeB must be of eRAN 6.1 or a later version. EPC(including an EPC of the vendors)
the counter VS.BSTWAMP.Forward.DropMeans/VS.BSTWAMP.Backward.DropMean suddenly increase
must support TWAMP
The eNodeB must be of eRAN 6.0 or a later version. Huawei EPC must be of PS 9.2 or a
Other The counter VS.IPPM.Forword.DropMeans suddenly increase exceeds 20 ms
later version

HUAWEI TECHNOLOGIES CO., LTD. Page 7


CQT Troubleshooting Process – Case
 HGCT07 – Low throughput cause configuration issue
1. Description: from CQT first result, CQT of this site do not reach contract CQT Target but Uu test result is very
good.

2. Description: HW contact with MBF HGG province and NOC Can Tho to get support for TXN and Co-operate
with subcontractor and to on-site test & Troubleshooting

3. Result: The CQT of this site was improved and reach


the target.

SSV and CQT


Low throughput
tracker
Troubleshooting
HUAWEI TECHNOLOGIES CO., LTD. Page 8
CQT Troubleshooting Process – Case 2 Low throughput cause TXN Bandwidh Limit
First CQT result of AGTT24 had low throughput both DL and UL

Actions: Checking TXN Configuration and FEGE KPIs, we found that KPI is not good then we asked support from AGG province team for TXN configuration checking

Result: After AGG team informed that TXN fix, we monitored and found FEGE KPIs become better and do re-test. The CQT pass contract target.

HUAWEI TECHNOLOGIES CO., LTD. Page 9


THANK YOU

HUAWEI TECHNOLOGIES CO., LTD. Page 10

You might also like