Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ran16.0 troubleshooting guide(02)(pdf) en

564 views

Published on

Ran16.0 troubleshooting guide(02)(pdf) en

Published in: Engineering
  • Be the first to comment

Ran16.0 troubleshooting guide(02)(pdf) en

  1. 1. RAN16.0 Troubleshooting Guide Issue 02 Date 2014-05-31 HUAWEI TECHNOLOGIES CO., LTD.
  2. 2. Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd i Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: http://www.huawei.com Email: support@huawei.com
  3. 3. RAN16.0 Troubleshooting Guide Overview Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd ii Overview Document Purpose This document provides information on how to identify and repair common faults on RAN equipment that is working in a live network. Operation and maintenance (O&M) personnel should use this guide in the following scenarios:  User complaints are received  Faults are detected in the routine maintenance processes  Emergency faults are detected in the equipment  Alarm analysis Product Version The following table lists the product versions related to this document. Product Name Product Model Product Version RNC BSC6900 V900R016C00 RNC BSC6910 V100R016C00 NodeB DBS3900 Single-mode: V200R016C00 Multi-mode: BTS3900 V100R009C00 Intended Audience This guide is intended for system engineers. Symbol Conventions The symbols that may be found in this document are defined as follows.
  4. 4. RAN16.0 Troubleshooting Guide Overview Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd iii Symbol Description Alerts you to a high risk hazard that could, if not avoided, result in serious injury or death. Alerts you to a medium or low risk hazard that could, if not avoided, result in moderate or minor injury. Alerts you to a potentially hazardous situation that could, if not avoided, result in equipment damage, data loss, performance deterioration, or unanticipated results. Provides a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points in the main text. Change History Changes between document issues are cumulative. The latest document issue contains all the changes made in earlier issues. 02 (2014-05-31) This issue includes the following changes: Content Description Technical Changes Added  MBTS Emergency OM channel. For details, see 3.2 MBTS Emergency OM Channel.  Hierarchical Delimitation. For details, see 2.3 Hierarchical Delimitation. Modified N/A Deleted N/A Editorial Changes Modified the structure. The section Fault Diagnosing, Fault Information Collecting Function and Hierarchical Delimitation are moved to section FMA. 01 (2014-04-29) Compared with issue RAN15.0 01 (2013-05-04), this issue includes the following changes:
  5. 5. RAN16.0 Troubleshooting Guide Overview Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd iv Content Description Technical Changes Added  Fault Diagnosing. For details, see 2.1 Fault Diagnosing Function.  Fault Information Collecting Function. For details, see 2.2 Fault Information Collecting Function. Modified N/A Deleted N/A Editorial Changes Deleted 15 Troubleshooting RNC in Pool Faults. For the troubleshooting of RNC in Pool, please refer to RNC in Pool feature parameter description.
  6. 6. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd v Contents Overview........................................................................................................................................... ii Contents .............................................................................................................................................v 1 Troubleshooting Process and Methods ....................................................................................1 1.1 About this Chapter............................................................................................................................................1 1.2 Troubleshooting Process ..................................................................................................................................1 1.2.1 Flowchart ................................................................................................................................................1 1.2.2 Collecting and Recording Fault Information ..........................................................................................2 1.2.3 Determining Fault Scope and Type.........................................................................................................3 1.2.4 Locating the Cause of the Fault ..............................................................................................................4 1.2.5 Troubleshooting ......................................................................................................................................5 1.2.6 Ensuring that System Is Repaired ...........................................................................................................5 1.2.7 Recording the Troubleshooting Process..................................................................................................5 1.2.8 Contacting Huawei for Technical Support ..............................................................................................6 2 FMA .................................................................................................................................................7 2.1 Fault Diagnosing Function...............................................................................................................................7 2.1.1 Application Scope and Scenarios............................................................................................................8 2.1.2 Prerequisites............................................................................................................................................1 2.1.3 Starting the Fault Diagnosing Function ..................................................................................................1 2.1.4 Introduction to the Fault Diagnosing Tab Page.......................................................................................5 2.1.5 Setting Thresholds for Diagnosis Rules ..................................................................................................7 2.1.6 Viewing Analysis Results........................................................................................................................8 2.1.7 Saving the Analysis Results .................................................................................................................. 11 2.1.8 FMA Dashboard Operation Guide ........................................................................................................13 2.2 Fault Information Collecting Function...........................................................................................................17 2.2.1 Prerequisites..........................................................................................................................................17 2.2.2 Operation Guide....................................................................................................................................17 2.3 Hierarchical Delimitation...............................................................................................................................19 2.3.1 Overview...............................................................................................................................................19 2.3.2 Function Description.............................................................................................................................19 3 Common Maintenance Functions............................................................................................21 3.1 About This Chapter ........................................................................................................................................21
  7. 7. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd vi 3.2 MBTS Emergency OM Channel ....................................................................................................................21 3.2.1 Overview...............................................................................................................................................21 3.2.2 Application Scenarios ...........................................................................................................................22 3.2.3 Emergency OM Channel Establishment ...............................................................................................24 3.2.4 Function Description.............................................................................................................................29 3.2.5 Troubleshooting ....................................................................................................................................33 3.2.6 Example of Using the Proxy MML Function........................................................................................33 3.2.7 Other Operations...................................................................................................................................39 3.3 Transmission Maintenance Function..............................................................................................................39 3.3.1 Checking for Faults in Crossed Pair Connections.................................................................................39 3.3.2 Performing a Bit Error Monitoring on the E1/T1 Port..........................................................................40 3.3.3 Using VCLCC to Check for Link Faults...............................................................................................41 3.3.4 Using VCLCC to Check for Link Delays .............................................................................................42 3.3.5 Using VCLPM to Check for Abnormal Links.......................................................................................43 3.3.6 Performing VCL Link Performance Query...........................................................................................44 3.3.7 Performing the IP over ATM OMCH Continuity Check.......................................................................45 3.3.8 Using LOP VCL to Check for Link Faults or Link Delays ...................................................................46 3.3.9 Checking the Operating Status of the Ethernet Port..............................................................................47 3.3.10 Using the Ping Operation to Perform the IP Continuity Check...........................................................47 3.3.11 Using the Trace Operation to Check for Abnormal Transmission Nodes............................................49 3.3.12 Using the Ping Operation to Check the IP Path Status........................................................................50 3.3.13 Performing IP Loopback Detection to Check for Abnormal Transmission Nodes..............................51 3.3.14 Performing IP PM Detection to Check IP Path Performance on the Iub Interface..............................53 3.3.15 Performing IP PM Detection to Check IP Pool Performance on the Iub Interface .............................54 3.3.16 Performing Node Synchronization Detection to Check for Transmission Delay and Jitter on the User Plane ..............................................................................................................................................................54 3.3.17 Performing TWAMP Detection to Check for IP Link Performance....................................................56 3.4 Clock Maintenance Function..........................................................................................................................57 3.4.1 Querying the Status of the BSC Reference Clock.................................................................................57 3.4.2 Querying the Status of the BSC Board Clock .......................................................................................58 4 Troubleshooting HSPA Service Setup Failures....................................................................60 4.1 About This Chapter ........................................................................................................................................60 4.2 Definition of HSPA Service Setup Failures....................................................................................................60 4.3 Related Information........................................................................................................................................60 4.4 Possible Causes ..............................................................................................................................................61 4.5 Troubleshooting Flowchart ............................................................................................................................61 4.5.2 Troubleshooting Abnormal AAL2PATH,IPPATH or IPPOOL..............................................................61 4.5.3 Troubleshooting Failures to Admit HSUPA User Number and HSDPA User Number .........................63 4.5.4 Determining Whether the Service Rate Mismatch the Threshold of HSPA Services............................65 4.5.5 Determining Whether the Terminal Supports the HSPA Services.........................................................66 4.6 Typical Cases..................................................................................................................................................67
  8. 8. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd vii 5 Troubleshooting HSUPA Data Transmission Faults...........................................................69 5.1 About This Chapter ........................................................................................................................................69 5.2 Definition of HSUPA Data Transmission Faults ............................................................................................69 5.3 Related Information........................................................................................................................................69 5.3.1 Requisites for Reaching HSUPA Maximum Rate .................................................................................69 5.4 Troubleshooting Low or Fluctuating HSUPA Rate ........................................................................................71 5.4.1 Fault Description...................................................................................................................................71 5.4.2 Possible Causes.....................................................................................................................................71 5.4.3 Fault Handling Procedure .....................................................................................................................71 5.4.4 Typical Cases ........................................................................................................................................75 6 Troubleshooting HSDPA Service Rate Faults.......................................................................77 6.1 About This Chapter ........................................................................................................................................77 6.2 Definition of HSDPA Service Rate Faults......................................................................................................77 6.3 Related Information........................................................................................................................................77 6.4 Troubleshooting Low or Fluctuating HSDPA Service Rate ...........................................................................79 6.4.1 Fault Description...................................................................................................................................79 6.4.2 Fault Handling Flowchart .....................................................................................................................79 6.4.3 Checking Basic Elements......................................................................................................................80 6.4.4 Determining Whether the Service Can Be Set Up ................................................................................82 6.4.5 Determining Whether Radio Resources Are Limited............................................................................86 6.4.6 Check Faults Segment by Segment.......................................................................................................87 6.4.7 Typical Cases ........................................................................................................................................90 7 Troubleshooting SLC Faults .....................................................................................................92 7.1 About This Chapter ........................................................................................................................................92 7.2 Definition of SLC Faults................................................................................................................................92 7.3 SLC Problem Monitoring...............................................................................................................................92 7.4 Troubleshooting the Problem of No RRC Connection Request .....................................................................94 7.4.1 Fault Description...................................................................................................................................94 7.4.2 Possible Causes.....................................................................................................................................94 7.4.3 Fault Handling Procedure .....................................................................................................................95 7.4.4 Typical Case 1.......................................................................................................................................96 7.4.5 Typical Case 2.......................................................................................................................................96 7.5 Troubleshooting RRC Connection Setup Failures..........................................................................................97 7.5.1 Fault Description...................................................................................................................................97 7.5.2 Fault Handling Procedure .....................................................................................................................97 8 Troubleshooting RRC Connection Setup Failures...............................................................98 8.1 Definition of RRC Access Failures ................................................................................................................98 8.2 Formula for the RRC Setup Success Rate......................................................................................................98 8.3 Related Information........................................................................................................................................98 8.4 Troubleshooting the Problem of No Replies to an RRC Connection Setup Request .....................................99
  9. 9. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd viii 8.4.1 Failure Description................................................................................................................................99 8.4.2 Fault Handling Procedure .....................................................................................................................99 8.4.3 Typical Case 1.....................................................................................................................................102 8.4.4 Typical Case 2.....................................................................................................................................104 8.5 Troubleshooting Rejected RRC Connection Setup Requests .......................................................................105 8.5.1 Failure Description..............................................................................................................................105 8.5.2 Handling Procedure.............................................................................................................................105 8.6 Troubleshooting Failures in Replying to RRC Connection Setup Requests ................................................107 8.6.1 Fault Description.................................................................................................................................107 8.6.2 Handling Procedure.............................................................................................................................107 9 Troubleshooting RAB Setup Faults.......................................................................................108 9.1 About This Chapter ......................................................................................................................................108 9.2 Definition of RAB Setup Faults ...................................................................................................................108 9.2.1 RAB Setup Success Rate ....................................................................................................................108 9.2.2 RAB Setup Procedure.........................................................................................................................108 9.2.3 RAB Setup Failure Scenarios..............................................................................................................109 9.3 Possible Causes ............................................................................................................................................109 9.4 Troubleshooting RAB Setup Failure ............................................................................................................ 110 9.5 Troubleshooting the Problem of Uu No Response ....................................................................................... 112 9.5.1 Fault Description................................................................................................................................. 112 9.5.2 Fault Handling Procedure ................................................................................................................... 112 9.5.3 Typical Cases ...................................................................................................................................... 112 9.6 Troubleshooting Increased Traffic Volume .................................................................................................. 114 9.6.1 Fault Description................................................................................................................................. 114 9.6.2 Fault Handling Procedure ................................................................................................................... 114 9.6.3 Typical Cases ...................................................................................................................................... 114 9.7 Troubleshooting Iub Congestion .................................................................................................................. 115 9.7.1 Fault Description................................................................................................................................. 115 9.7.2 Fault Handling Procedure ................................................................................................................... 115 9.7.3 Typical Cases ...................................................................................................................................... 118 9.8 Troubleshooting Other Congestions............................................................................................................. 119 9.8.1 Fault Description................................................................................................................................. 119 9.8.2 Fault Handling Procedure ................................................................................................................... 119 9.8.3 Typical Case 1.....................................................................................................................................120 9.8.4 Typical Case 2.....................................................................................................................................121 9.9 Troubleshooting the Problem of RAB Setup Not Allowed by the RNC Configuration ...............................121 9.9.1 Fault Description.................................................................................................................................121 9.9.2 Fault Handling Procedure ...................................................................................................................121 9.9.3 Typical Cases ......................................................................................................................................122 9.10 Troubleshooting Transmission Network Faults..........................................................................................123 9.10.1 Fault Description...............................................................................................................................123
  10. 10. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd ix 9.10.2 Fault Handling Procedure .................................................................................................................123 9.10.3 Typical Cases ....................................................................................................................................125 9.11 Troubleshooting Physical Channel Faults ..................................................................................................126 9.11.1 Fault Description...............................................................................................................................126 9.11.2 Fault Handling Procedure..................................................................................................................126 9.11.3 Typical Cases ....................................................................................................................................127 9.12 Miscellaneous.............................................................................................................................................127 9.12.1 Fault Description...............................................................................................................................127 9.12.2 Fault Handling Procedure .................................................................................................................127 9.12.3 Typical Case 1...................................................................................................................................130 9.12.4 Typical Case 2...................................................................................................................................130 10 Troubleshooting Call Drops .................................................................................................131 10.1 Definition of CDR......................................................................................................................................131 10.1.1 CDR Formulas ..................................................................................................................................131 10.1.2 Signaling Procedure for a Call Drop.................................................................................................132 10.2 Related KPIs for Call Drops.......................................................................................................................132 10.3 Troubleshooting Procedure ........................................................................................................................134 10.4 Troubleshooting Call Drops in a Single Cell or Site ..................................................................................136 10.4.1 Fault Description...............................................................................................................................136 10.4.2 Fault Handling Procedure .................................................................................................................136 10.4.3 Typical Cases ....................................................................................................................................138 10.5 Troubleshooting Call Drops in the Entire Network....................................................................................139 10.5.1 Fault Description...............................................................................................................................139 10.5.2 Fault Handling Procedure .................................................................................................................139 10.5.3 Typical Case 1...................................................................................................................................141 10.5.4 Typical Case 2...................................................................................................................................142 10.5.5 Typical Case 3...................................................................................................................................142 11 Troubleshooting Handover Faults.......................................................................................144 11.1 About This Chapter.....................................................................................................................................144 11.2 Definitions of Handover Faults ..................................................................................................................144 11.2.1 Handover Success Ratio Formula .....................................................................................................144 11.2.2 Handover Signaling Procedure..........................................................................................................145 11.3 Handover Procedures .................................................................................................................................146 11.4 Troubleshooting Handover Faults ..............................................................................................................148 11.4.1 Fault Description...............................................................................................................................148 11.4.2 Possible Causes.................................................................................................................................148 11.4.3 Fault Handling Procedure..................................................................................................................149 11.5 Troubleshooting Faults on Related NEs .....................................................................................................150 11.5.1 Fault Description...............................................................................................................................150 11.5.2 The handover success ratio is low in most of cells, but there is no TOP cell which is quite low. Related Information .....................................................................................................................................150
  11. 11. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd x 11.5.3 Fault Handling Procedure..................................................................................................................150 11.6 Troubleshooting Inter-RNC, Inter-MSC, and Inter-RAT Handover Problems ...........................................151 11.6.1 Fault Description...............................................................................................................................151 11.6.2 Possible Causes.................................................................................................................................152 11.6.3 Fault Handling Procedure..................................................................................................................152 11.6.4 Typical Case 1 ...................................................................................................................................154 11.6.5 Typical Case 2 ...................................................................................................................................154 11.6.6 Typical Case 3 ...................................................................................................................................155 11.7 Troubleshooting the Abnormal Handover Caused by Hardware and Transmission Faults.........................155 11.7.1 Fault Description...............................................................................................................................155 11.7.2 Related Information ..........................................................................................................................155 11.7.3 Fault Handling Procedure..................................................................................................................156 11.8 Troubleshooting the Abnormal Handover Caused by Poor Quality of the Air Interface ............................156 11.8.1 Fault Description...............................................................................................................................156 11.8.2 Related Information ..........................................................................................................................156 11.8.3 Fault Handling Procedure..................................................................................................................157 11.8.4 Typical Cases ....................................................................................................................................157 11.9 Troubleshooting the Abnormal Handover Caused by Incorrect Parameter Settings...................................158 11.9.1 Fault Description...............................................................................................................................158 11.9.2 Related Information ..........................................................................................................................158 11.9.3 Fault Handling Procedure..................................................................................................................158 11.9.4 Typical Cases ....................................................................................................................................159 11.10 Troubleshooting Congestion in the Target Cell ........................................................................................160 11.10.1 Fault Description.............................................................................................................................160 11.10.2 Possible Causes...............................................................................................................................160 11.10.3 Fault Handling Procedure................................................................................................................160 11.10.4 Typical Cases...................................................................................................................................161 12 Troubleshooting Paging Faults ............................................................................................162 12.1 About This Chapter ....................................................................................................................................162 12.2 Definition of Paging Faults ........................................................................................................................162 12.3 Related Information....................................................................................................................................162 12.3.1 Paging Scenario ................................................................................................................................162 12.3.2 Paging Procedure and Performance Counters...................................................................................162 12.3.3 Difference Between Paging Success Rates on the RNC and on the CN ...........................................164 12.3.4 Related Paging Handling ..................................................................................................................165 12.4 Possible Causes ..........................................................................................................................................165 12.5 Troubleshooting Paging Faults...................................................................................................................166 12.5.1 Fault Description...............................................................................................................................166 12.5.2 Fault Handling Flowchart .................................................................................................................166 12.5.3 Fault Handling Procedure .................................................................................................................167 12.5.4 Typical Cases 1 .................................................................................................................................169
  12. 12. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd xi 12.5.5 Typical Cases 2 .................................................................................................................................169 13 Troubleshooting O&M Faults ..............................................................................................171 13.1 O&M Faults Definition ..............................................................................................................................171 13.2 Context.......................................................................................................................................................171 13.3 Troubleshooting Configuration Data Synchronization Faults ....................................................................171 13.3.1 Fault Description...............................................................................................................................171 13.3.2 Possible Causes.................................................................................................................................171 13.3.3 Troubleshooting Steps.......................................................................................................................171 13.3.4 Typical Cases ....................................................................................................................................172 13.4 Troubleshooting Counter Abnormalities ....................................................................................................172 13.4.1 Fault Description...............................................................................................................................172 13.4.2 Possible Causes.................................................................................................................................172 13.4.3 Troubleshooting Steps.......................................................................................................................172 13.4.4 Typical Cases ....................................................................................................................................173 14 Troubleshooting ATM Transmission Faults .....................................................................174 14.1 Procedure for Troubleshooting ATM Transmission Faults.........................................................................174 14.1.1 Determining ATM Transmission Fault Type .....................................................................................174 14.1.2 Measures to Troubleshoot ATM Transmission Faults .......................................................................174 14.2 Basic knowledge of ATM Transmission.....................................................................................................175 14.2.1 Characteristics of ATM Transmission Faults ....................................................................................175 14.2.2 Introduction to the ATM Layer .........................................................................................................175 14.2.3 ATM Cell Architecture......................................................................................................................176 14.2.4 VP/VC Switching..............................................................................................................................176 14.2.5 ATM VCL .........................................................................................................................................177 14.3 Troubleshooting SAAL Faults....................................................................................................................177 14.3.1 Fault Description...............................................................................................................................177 14.3.2 Possible Causes.................................................................................................................................178 14.3.3 Troubleshooting Procedure ...............................................................................................................178 14.3.4 Troubleshooting Steps.......................................................................................................................178 14.4 Troubleshooting AAL2 Path Faults............................................................................................................179 14.4.1 Fault Description...............................................................................................................................179 14.4.2 Possible Causes.................................................................................................................................180 14.4.3 Troubleshooting Procedure ...............................................................................................................180 14.4.4 Troubleshooting Steps.......................................................................................................................180 14.5 Troubleshooting Packet Loss in ATM Transmission ..................................................................................181 14.5.1 Fault Description...............................................................................................................................181 14.5.2 Possible Causes.................................................................................................................................181 14.5.3 Troubleshooting Procedure ...............................................................................................................181 14.5.4 Troubleshooting Steps.......................................................................................................................181 14.6 Troubleshooting Delay and Jitter in ATM Transmission ............................................................................183 14.6.1 Fault Description...............................................................................................................................183
  13. 13. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd xii 14.6.2 Possible Causes.................................................................................................................................183 14.6.3 Troubleshooting Procedure ...............................................................................................................183 14.6.4 Troubleshooting Steps.......................................................................................................................183 14.7 Troubleshooting Packet Error in ATM Transmission .................................................................................184 14.7.1 Fault Description...............................................................................................................................184 14.7.2 Possible Causes.................................................................................................................................184 14.7.3 Troubleshooting Procedure ...............................................................................................................185 14.7.4 Troubleshooting Steps.......................................................................................................................185 14.8 Troubleshooting Transient Interruption in ATM Transmission ..................................................................186 14.8.1 Fault Description...............................................................................................................................186 14.8.2 Possible Causes.................................................................................................................................186 14.8.3 Troubleshooting Procedure ...............................................................................................................186 14.8.4 Troubleshooting Steps.......................................................................................................................186 14.9 Troubleshooting PVC Faults (ATM layer) .................................................................................................188 14.9.1 Fault Description...............................................................................................................................188 14.9.2 Possible Causes.................................................................................................................................188 14.9.3 Troubleshooting Procedure ...............................................................................................................188 14.9.4 Troubleshooting Steps.......................................................................................................................188 14.10 Troubleshooting E1T1 Faults (physical layer) .........................................................................................189 14.10.1 Fault Description.............................................................................................................................189 14.10.2 Possible Causes...............................................................................................................................189 14.10.3 Troubleshooting Procedure .............................................................................................................189 14.10.4 Troubleshooting Steps.....................................................................................................................189 14.11 Troubleshooting IMA Faults (physical layer)...........................................................................................191 14.11.1 Fault Description.............................................................................................................................191 14.11.2 Possible Causes...............................................................................................................................191 14.11.3 Troubleshooting Steps.....................................................................................................................191 15 Troubleshooting IP Transmission Faults...........................................................................193 15.1 Procedure for Troubleshooting IP Transmission Faults..............................................................................193 15.1.1 Determining IP Transmission Fault Type..........................................................................................193 15.1.2 Measures to Troubleshoot IP Transmission Faults............................................................................193 15.2 Basic Knowledge of IP Transmission.........................................................................................................194 15.3 Troubleshooting SCTP Faults.....................................................................................................................197 15.3.1 Fault Description...............................................................................................................................197 15.3.2 Possible Causes.................................................................................................................................198 15.3.3 Troubleshooting Procedure ...............................................................................................................198 15.3.4 Troubleshooting Steps.......................................................................................................................198 15.3.5 Typical Cases ....................................................................................................................................200 15.4 Troubleshooting IP Path Faults ..................................................................................................................200 15.4.1 Fault Description...............................................................................................................................200 15.4.2 Possible Causes.................................................................................................................................201
  14. 14. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd xiii 15.4.3 Troubleshooting Procedure ...............................................................................................................201 15.4.4 Troubleshooting Steps.......................................................................................................................201 15.4.5 Typical Cases ....................................................................................................................................202 15.5 Troubleshooting IP Pool Faults ..................................................................................................................203 15.5.1 Fault Description...............................................................................................................................203 15.5.2 Possible Causes.................................................................................................................................203 15.5.3 Troubleshooting Procedure ...............................................................................................................203 15.5.4 Troubleshooting Steps.......................................................................................................................203 15.5.5 Typical Cases ....................................................................................................................................204 15.6 Troubleshooting IP over FE/GE Interface Disconnection ..........................................................................205 15.6.1 Fault Description...............................................................................................................................205 15.6.2 Possible Causes.................................................................................................................................205 15.6.3 Troubleshooting Procedure ...............................................................................................................205 15.6.4 Troubleshooting IP Layer Faults .......................................................................................................205 15.6.5 Troubleshooting Data Link Layer Faults ..........................................................................................206 15.6.6 Troubleshooting Physical Layer Faults.............................................................................................206 15.6.7 Typical Cases ....................................................................................................................................207 15.7 Troubleshooting MP/PPP Link Failure in IP over E1 Mode ......................................................................208 15.7.1 Fault Description...............................................................................................................................208 15.7.2 Possible Causes.................................................................................................................................208 15.7.3 Troubleshooting Procedure ...............................................................................................................208 15.7.4 Troubleshooting IP Layer Faults .......................................................................................................208 15.7.5 Troubleshooting E1T1 Faults (physical layer) ..................................................................................208 15.7.6 Troubleshooting Data Link Layer Faults ..........................................................................................208 15.8 Troubleshooting Packet Loss in IP Transmission.......................................................................................209 15.8.1 Fault Description...............................................................................................................................209 15.8.2 Possible Causes.................................................................................................................................209 15.8.3 Troubleshooting Steps.......................................................................................................................209 15.9 Troubleshooting Delay and Jitter in IP Transmission.................................................................................210 15.9.1 Fault Description...............................................................................................................................210 15.9.2 Possible Causes................................................................................................................................. 211 15.9.3 Troubleshooting Procedure ............................................................................................................... 211 15.9.4 Troubleshooting Steps....................................................................................................................... 211 15.10 Troubleshooting Packet Errors in IP Transmission ..................................................................................212 15.10.1 Fault Description.............................................................................................................................212 15.10.2 Possible Causes...............................................................................................................................212 15.10.3 Troubleshooting Procedure .............................................................................................................212 15.10.4 Troubleshooting Steps.....................................................................................................................212 15.11 Troubleshooting Transient Interruption in IP Transmission .....................................................................213 15.11.1 Fault Description.............................................................................................................................213 15.11.2 Possible Causes...............................................................................................................................213 15.11.3 Troubleshooting Procedure .............................................................................................................213
  15. 15. RAN16.0 Troubleshooting Guide Contents Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd xiv 15.11.4 Troubleshooting Steps.....................................................................................................................213 16 Troubleshooting Faults in SSN Configuration-Free........................................................215 16.1 About This Chapter ....................................................................................................................................215 16.2 Definition of Faults in SSN Configuration-Free ........................................................................................215 16.3 Related Information....................................................................................................................................215 16.4 Troubleshooting the Failed Execution of the ADD UNODEB Command .................................................217 16.4.1 Fault Description...............................................................................................................................217 16.4.2 Possible Causes.................................................................................................................................217 16.4.3 Troubleshooting Procedure ...............................................................................................................218 16.5 Troubleshooting the Problem that Automatic SSN Allocation Achieved by the SSN Configuration-Free Algorithm Is Inappropriate.................................................................................................................................218 16.5.1 Fault Description...............................................................................................................................218 16.5.2 Possible Causes.................................................................................................................................218 16.5.3 Troubleshooting Procedure ...............................................................................................................218 17 Troubleshooting Faults Related to the Inter-Dependence of BBU Uplink Resource Feature ..........................................................................................................................................................221 17.1 About This Chapter ....................................................................................................................................221 17.2 Definition of Faults Related to the Inter-Dependence of BBU Uplink Resource Feature..........................221 17.3 Troubleshooting Unavailable Cells ............................................................................................................221 17.3.1 Fault Description...............................................................................................................................221 17.3.2 Possible Causes.................................................................................................................................221 17.3.3 Troubleshooting Steps.......................................................................................................................221 18 Appendix: Common Methods of Collecting Fault Information....................................223
  16. 16. RAN16.0 Troubleshooting Guide 1 Troubleshooting Process and Methods Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 1 1 Troubleshooting Process and Methods 1.1 About this Chapter This chapter describes the process for troubleshooting, common methods of fault location, and how to get technical support from Huawei. 1.2 Troubleshooting Process 1.2.1 Flowchart Figure 1-1 shows the troubleshooting flowchart.
  17. 17. RAN16.0 Troubleshooting Guide 1 Troubleshooting Process and Methods Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 2 Figure 1-1 Troubleshooting flowchart 1.2.2 Collecting and Recording Fault Information Fault Information to be Collected When a fault occurs, O&M personnel must start troubleshooting by obtaining fault information, which serves as a reference. O&M personnel should collect as much fault information as possible. The following information must be collected before any operation:  Symptoms, including details and basic data  Time, location, and frequency of occurrence  Scope and impact  Equipment operating status before the fault occurred  Operations performed on the equipment before the fault occurred, and the results of these operations
  18. 18. RAN16.0 Troubleshooting Guide 1 Troubleshooting Process and Methods Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 3  Measures taken to deal with the fault, and the results  Alarms resulting from the fault  Status of board LEDs Methods of Collecting Fault Information To collect fault data, do as follows:  Consult the personnel who reported the fault about symptoms, time, location, and frequency of the fault.  Consult the O&M personnel about the equipment operating status before the fault occurred, operations performed on the equipment before the fault occurred, fault symptoms, and measures taken to deal with the fault and the results.  Observe board LEDs, the O&M subsystem, and the alarm management system to obtain information about the status of system software and hardware.  Estimate the impact of the fault by testing services, measuring performance, and tracing interface messages or signaling messages. Strategies for Collecting Fault information Strategies for collecting fault information are as follows:  Do not handle a fault hastily. Collect as much information as possible before attempting to repair the fault.  Maintain good communication with other departments and O&M personnel of other sites. Ask them for technical support if necessary. 1.2.3 Determining Fault Scope and Type After collecting all available fault information, analyze the fault symptoms, and determine the fault scope and type. This document describes 11 types of faults, as listed in Table 1-1. Table 1-1 Faults and scopes No. Category Fault Type Description 1 HSPA service HSPA service setup failure HSPA service setup failure, instead of a low rate of HSPA services 2 HSUPA rate fault Fluctuating or low HSUPA rate 3 HSDPA rate fault Fluctuating or low HSDPA rate 4 KPI SLC fault Cell access failure 5 RRC connection setup fault Low RRC connection setup success rate 6 RAB connection setup fault Low RAB access success rate 7 Call drop rate fault High call drop rate
  19. 19. RAN16.0 Troubleshooting Guide 1 Troubleshooting Process and Methods Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 4 No. Category Fault Type Description 8 Handover fault Low handover success rate 9 Paging fault Low paging success rate 10 Operation & Maintenace Operation & Maintenace fault Faults of O&M on RAN devices 11 Transmission ATM Transmission network fault ATM transmission faults 12 IP Transmission network fault IP transmission faults 13 SSN Configuration-Free SSN Configuration-Free faults The ADD UNODEB command fails to be executed when the SSN configuration-free algorithm is enabled. The automatic SSN allocation achieved by the SSN configuration-free algorithm is inappropriate. 14 Inter-Dependence of BBU Uplink Resource Feature Faults Related to the Inter-Dependence of BBU Uplink Resource Feature Faults after the Inter-Dependence of BBU Uplink Resource feature is activated 1.2.4 Locating the Cause of the Fault To locate the cause of the fault, first compare and analyze possible causes, and then eliminate causes that are unlikely or impossible. Comparison and Interchange  Description O&M personnel can compare the faulty components or symptoms with their normal equivalents to locate faults. Comparison is applied in scenarios where the scope of the fault is small. If the fault scope and area cannot be determined after the replacement of some components with spare parts, then interchange a component that is suspected of being faulty with known good components that are being used in the system. For example, replace a board or optical cable that is suspected faulted with an equivalent item that is known to be good. Then compare the status before and after the operation to determine if the fault was repaired or to further determine the scope and area of the fault. Interchange is applied in scenarios where the scope of the fault is large.  Application Scenarios Comparison and interchange are used when faults occur after NE hardware, software or a new feature is introduced that may have caused a service outage.  Instructions
  20. 20. RAN16.0 Troubleshooting Guide 1 Troubleshooting Process and Methods Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 5 Use this method to compare the performances and KPIs before and after hardware or software is changed, or a new feature is introduced. Segment-by-Segment Location  Function A fault may occur at any node in an end-to-end network. Therefore, this method helps locating the fault quickly.  Application Scenario Transmission network fault or PS data transmission fault  Usage Locate the fault segment by segment. Layer-by-Layer Location  Function As specified by the protocol, the upper layer can work properly only when its lower layers are working properly. When a fault occurs, all associated layers malfunction. In addition, the symptom of a fault may vary if different monitoring methods are used. Therefore, this method helps locating the layer where the fault is generated and facilitates the troubleshooting.  Application Scenario Transmission network fault or PS data transmission fault  Usage Locate the fault layer by layer. 1.2.5 Troubleshooting To repair faults and restore the system, troubleshoot different faults using proper measures and procedures. Troubleshooting consists of checking cables, replacing boards, modifying data configuration, switching over boards, and resetting boards. 1.2.6 Ensuring that System Is Repaired Test the system again after troubleshooting to ensure that the fault is completely repaired. Ensure the system works properly by observing the status of board LEDs and alarm information, and perform dial tests to ensure that all services are operational. 1.2.7 Recording the Troubleshooting Process It is important to record the troubleshooting process in a way that O&M personnel can use in the future. When the troubleshooting/repair action is complete, O&M personnel should:  Review the entire troubleshooting process  Note key points of the process  Summarize methods for improvement of the system which could avoid recurrence of the faults of the same type. Ensure notes are recorded in a logbook or other method that O&M personnel will have future access to.
  21. 21. RAN16.0 Troubleshooting Guide 1 Troubleshooting Process and Methods Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 6 1.2.8 Contacting Huawei for Technical Support If faults are difficult to identify or solve, then prepare the following information, and contact Huawei for technical support. Step 1 Collect general fault information. The general information required is as follows:  Full name of the office  Contact name and number  Time when the fault occurred  Detailed symptoms of the fault  Version of the host software  Measures taken to deal with the fault, and the results  Severity and expected repair time Step 2 Collect fault location information. Information to be collected is listed according to the related steps. Step 3 Use the following methods to contact Huawei for technical support:  E-mail: support@huawei.com  Website: http://support.huawei.com http://support.huawei.com contains contact information for the local office in your region.
  22. 22. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 7 2 FMA FMA(Fault Management Assistant) function helps users handle network faults. It includes the following functions: fast faultdiagnosis, fault information collection, and hierarchical delimitation. The fault diagnosis andhierarchical delimitation functions analyze faults only within eight hours from the fault rectification to the current time. The following figure shows the fault handling process using this assistant: The procedure is as follows: 1, Determine whether services are affected. 2, Use the fault diagnosis function to identify partial of the faults. 3, Use the hierarchical delimitation function to analyze faults that cannot be fast identified. 4, Use the information collection function to collect logs of faults that cannot be identified by the preceding two methods, and use the offline analysis tool to analyze these faults. 5, Rectify the faults. 6, Check that services are recovered. 2.1 Fault Diagnosing Function When a service or network fault occurs, services cannot be restored promptly by normal maintenance measures such as reset, power-off, and board replacement because the faulty NE or board cannot be located promptly. In this case, the LMT fault diagnosing function can help to find the root cause quickly based on the traffic data and logs collected onsite. Based on the
  23. 23. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 8 analysis report provided by this function, maintenance engineers can locate the faulty board or subsystem and troubleshoot the fault. The fault diagnosing function diagnoses and troubleshoots service and network faults by scenarios. Maintenance engineers can use the online diagnosis expert system to analyze traffic data, alarms, and logs collected onsite based on the diagnosis rules and locate the faulty board or subsystem. Then, they can provide the customer an analysis report for troubleshooting. Figure 2-1 illustrates the troubleshooting procedure using the fault diagnosing function. Figure 2-1 Troubleshooting procedure using the fault diagnosing function Huawei designs the diagnosis rules based on years of network maintenance experience. The diagnosis rules are released with BSC6900 V900R015C01, BSC6910 V100R015C01, and their later versions and can be updated with version upgrade. Maintenance engineers must select a fault scenario to which the problem belongs before using the fault diagnosing function. For details about fault scenarios, see Table 2-1. 2.1.1 Application Scope and Scenarios Applicable Boards This function applies only to the OMU.
  24. 24. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 9 Intended Audience R&D, maintenance, and technical support personnel involved in OM Application Scenarios and Restrictions Application Scenarios When a service or network fault occurs, the faulty NE or board cannot be located promptly. In this case, the fault diagnosing function can be used to locate and analyze the root cause. Restrictions A fault analysis task using the fault diagnosing function of the LMT is started on the OMU. This analysis task consumes the OMU physical resources but does not conflict with other tasks such as tracing and monitoring. To ensure the smooth operations of functions on the OMU and the fault diagnosing function, the following restricts are imposed:  This function cannot be started when available free space on the OMU is less than 500 MB.  When the physical OMU memory in use exceeds 95%, For the BSC6910, memory used by the fault diagnosing function exceeds 500 MB, stop this function. For the BSC6900, memory used by the fault diagnosing function exceeds 200 MB, stop this function.  When the OMU CPU usage reaches 100%, the operating systems schedules processes on the OMU by priority. The initial priority of the fault analysis task using the fault diagnosing function is set to low. When the CPU usage of this task is lower than the minimum threshold (10%), increase its priority. When the CPU usage of this task is higher than the minimum threshold (10%), set its priority to low. NOTE You can run the DSP OMUSRV command on the RNC to query the free space, memory and CPU usage on the OMU. When a fault occurs, it is recommended that you use this function to analyze the fault first and then run the COL LOG command to collect logs. After the fault diagnosing function is started, the COL LOG command is automatically executed to collect the MEMDB information. Therefore, if the user starts this function on the LMT to analyze the fault and then runs the COL LOG command, a conflict occurs. In this case, wait a few minutes and run this command again.
  25. 25. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 1 2.1.2 Prerequisites The connection is functional between the LMT and the NE. 2.1.3 Starting the Fault Diagnosing Function Step 1 Click FMA on the LMT main page. The FMA tab page is displayed. Step 2 Under FMA, double-click Fault Diagnosis. The Fault Diagnosis dialog box is displayed. Select the logical NEs requiring fault management under BSC Options. NOTE In the BSC Options area, you can select only one RNC or BSC for one fault diagnosis. Step 3 Click Next. The Scenario Options area is displayed. Select the fault scenarios. Step 4 Click Dashboard or Start. Wait for the report to be generated. ----End Table 2-1 lists all the fault scenarios. Table 2-1 Fault scenarios Scenario Options Item KPI RRC connection setup The number of RRC connection setup requests is 0 The RRC connection setup success rate is abnormal The number of RRC connection setup requests decreases significantly CS service setup The initial direct transmission flow control rate of CS services is abnormal The Iu-CS SCCP setup success rate is abnormal The CS security mode success rate is abnormal The location update success rate is abnormal The CS service rejection rate is abnormal The CS service redirection rate in an MOCN is abnormal The number of successful CS RAB setups is 0 The CS RAB setup success rate is abnormal
  26. 26. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 2 Scenario Options Item The number of CS RAB setup requests decreases significantly CS call drop The CS service drop rate is abnormal PS service setup The initial direct transmission flow control rate of PS services is abnormal The Iu-PS SCCP setup success rate is abnormal The PS security mode success rate is abnormal The RA update success rate is abnormal The PS service rejection rate is abnormal The attach success rate is abnormal The PDP context activation success rate is abnormal The PS service redirection rate in an MOCN is abnormal The number of successful PS RAB setups is 0 The PS RAB setup success rate is abnormal The number of PS RAB setup requests decreases significantly PS call drop The PS service drop rate is abnormal Paging The paging success rate is abnormal Traffic PS throughput The PS throughput decreases significantly CS Erlang The CS Erlang decreases significantly Transmission A larger number of unavailable cells A large number of cells are unavailable Others Equipment health check health check on the interface boards health check on user-plane boards and subsystems health check on control-plane boards and subsystems analysis on system configuration errors control-plan Iu-CS and Iu-PS interface status check
  27. 27. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 3 Scenario Options Item Iur-P interface status check Flow control of the board RNC in Pool Load Sharing The number of RRC connection setup requests of the overflow RNC is 0 The RRC connection setup success rate of the overflow RNC is abnormal The number of successful CS RAB setups of the overflow RNC is 0 The CS RAB setup success rate of the overflow RNC is abnormal The CS service drop rate of the overflow RNC is abnormal The number of successful PS RAB setups of the overflow RNC is 0 The PS RAB setup success rate of the overflow RNC is abnormal The PS service drop rate of the overflow RNC is abnormal The CS Erlang of the overflow RNC decreases significantly The PS throughput of the overflow RNC decreases significantly If RNC in Pool is enabled, select the fault scenarios based on Table 2-2. The system automatically determines the host status and type of load sharing and node redundancy for RNC in Pool and recommends the corresponding fault scenarios. You can also run the LST URNCBASIC and DSP UHOSTRNC commands on the RNC to query the load sharing type and host status, respectively.
  28. 28. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 4 Table 2-2 RNC in Pool fault scenarios Scenario Options RNC in Pool Load Sharing RNC in Pool Redundancy RNC in Pool Load Sharing and Redundancy Load Sharing Type= MASTE R Load Sharing Type= OVERF LOW Host Status =MAS TER Host Status =BAC KUP Load Sharing Type= MASTE R and Host Status= MASTE R Load Sharing Type= OVERF LOW and Host Status= BACK UP Load Shar ing Type =OV ERF LO W and Host Stat us= MA STE R RRC connection setup √ × √ × √ × √ CS service setup √ × √ × √ × √ CS call drop √ × √ × √ × √ PS service setup √ × √ × √ × √ PS call drop √ × √ × √ × √ CS Erlang √ × √ × √ × √ PS throughput √ × √ × √ × √ Paging √ × √ × √ × √ A large number of unavailable cells √ × √ × √ × √ Equipment health check √ √ √ √ √ √ √ RNC IN POOL Load Sharing √ × × × √ × ×
  29. 29. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 5 2.1.4 Introduction to the Fault Diagnosing Tab Page  The Scenario Options area: Multiple fault scenarios can be selected simultaneously.  The Dashboard button: After you click Dashboard, a graphical user interface (GUI) is displayed with the performance data for the last 8 hours, operation data for the last 24 hours, and active and cleared alarm for the last 24 hours is displayed.  The Start button: After you click Start, the fault analysis using the fault diagnosing function is started. A folder named by the operation date and time is generated each time this analysis is started under the /bam/version_x/ftp/fma_data directory, for example, /bam/version_x/ftp/fma_data/20111226174421. This folder contains four sub-folders which are described in the following table. Folder Description alarm_data Contains the active alarms and cleared alarms for the last 24 hours. opt_data Contains the operation data for the last 24 hours. report Contains the analysis report generated using the fault diagnosing function. stat_data Contains the performance data for the last 8 hours, the corresponding 8 hours yesterday, and the corresponding 8 hours 7 days ago. After the fault analysis is successfully started, a webpage containing the analysis results is displayed using the IE browser, as shown in Figure 2-2. The Firefox browser also supports this function. Figure 2-2 Results of a successful fault analysis task If you start the fault analysis when the COL LOG command is being executed, a webpage indicating a data export failure is displayed, as shown in Figure 2-3. This is because the fault analysis also requires to execute the COL LOG command, which leads to a conflict. In this case, run the COL LOG command a few minutes later.
  30. 30. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 6 Figure 2-3 Results of a failed fault analysis task  The Stop button: You can click Stop to stop a fault analysis task in process. The Alert dialog box is displayed. C lick OK.  The Query Result button: You can click Query Result to query the history analysis results based on the task date and time. The Query Result dialog box is displayed, as shown in Figure 2-4. Figure 2-4 Query Result dialog box Choose a date and time from the Select List drop-down list and click Submit, as shown in Figure 2-5.
  31. 31. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 7 Figure 2-5 Select List drop-down list An analysis report is displayed in a webpage form. If the report.xml file in not stored under the bam/version_x/ftp/fma_data/date and time/report directory, a dialog box indicating that the file is not found is displayed, as shown in Figure 2-6. Figure 2-6 Dialog box indicating that the file is not found Folders containing all history analysis results are stored under the bam/version_x/ftp/fma_data directory. The maximum size of these folders is 500 MB. If the size exceeds 500 MB, the system deletes the earliest folder. Therefore, you must save important history analysis results in time. For details about how to save the history analysis results, see section 2.1.7 "Saving the Analysis Results". 2.1.5 Setting Thresholds for Diagnosis Rules To query the current thresholds for diagnosis rules, run the LST FMATH command on the LMT, as show in Figure 2-7.
  32. 32. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 8 Figure 2-7 Querying the current thresholds for diagnosis rules To set and modify the thresholds for diagnosis rules, run the SET FMATH command on the LMT with specified Threshold Name and Threshold Value, as shown in Figure 2-8. Figure 2-8 Setting or modifying the thresholds for diagnosis rules 2.1.6 Viewing Analysis Results After the fault analysis task using the fault diagnosing function succeeds, a webpage is displayed, as shown in Figure 2-9. Figure 2-9 Results of a successful fault analysis task
  33. 33. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 9 This webpage consists of the following parts:  RNC Basic Information: This part is displayed only when you have selected UMTS RNC in the BSC Options area. Information about the RNC in Pool networking and basic RNC configurations is displayed. − RNC in Pool networking: Information such as RNC node ID and host status, as shown in the red circle in Figure 2-10. − Basic RNC configurations: Information such as RNC ID, RNC name, and Iub transmission mode, as shown in the black circle in Figure 2-10. Figure 2-10 RNC Basic Information  KPI and counter change trend: This part is displayed when you have selected UMTS RNC or GSM BSC in the BSC Options area. RNC KPI TREND is displayed when you have selected UMTS RNC, as shown in Figure 2-9. If you have selected GSM BSC, four KPI and counter change trend charts are displayed. If you have selected UMTS RNC, ten KPI and counter change trend charts and one table are displayed. KPI and counter change trend chart: There are three lines for each KPI or counter indicating its change trends in the last 8 hours, corresponding 8 hours yesterday, and corresponding 8 hours seven days ago. The KPIs and counters are sampled every 15 minutes. The X axis, left Y axis, and right Y axis indicate the time, number, and ratio, respectively. Figure 2-11 shows an RRC KPI and counter change trend chart. Figure 2-11 RRC KPI and counter change trend chart Alarm quantity change trend chart: Figure 2-12 shows an RNC alarm quantity change trend chart for the last 24 hours. The X axis and Y axis indicate the time and alarms quantity, respectively. The three lines indicate the quantities of reported alarms, cleared alarms, and active alarms. The alarms are collected every 15 minutes.
  34. 34. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 10 An alarm is considered an active alarm if it is not cleared within 15 minutes. You can set the alarm severity by referring to section 2.1.5 "Setting Thresholds for Diagnosis Rules". The alarm quantity displayed in Figure 2-12 uses the total number of alarms of all severity levels. Figure 2-12 RNC alarm quantity change trend chart  FMA Dashboard: Figure 2-13 shows a dashboard of integrated fault analysis results including the various KPI and counter change trend charts, operation log, and alarm log. Figure 2-13 Dashboard of integrated fault analysis results The three areas displayed in FMA Dashboard are as follows:  KPI and counter change trend chart: A line is displayed for each KPI or counter indicating its change trend in the last 8 hours. The X axis, left Y axis, and right Y axis indicate the time, number, and ratio, respectively.  Operation log: The executed MML commands are displayed from the earliest one. Information such as the executed MML commands, operating time, and execution results are displayed.  Alarm log: Alarms are displayed from the earliest one. Information such as alarm ID, alarm report time, and location information are displayed. For detailed operation and information, see section 2.1.8 "FMA Dashboard Operation Guide."  Detailed analysis of a specific cause: Figure 2-14 shows the detailed analysis of significant PS throughput drop.
  35. 35. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 11 Figure 2-14 Detailed analysis of significant PS throughput drop The analysis results are displayed in three parts, as shown in the red circles in Figure 2-14. − Description: overall fault description − Diagnose Result: related data displayed in a table or described by words − Recommend Option: recommended suggestions to troubleshoot the fault 2.1.7 Saving the Analysis Results  If the default browser is the IE browser, click Save in the displayed webpage, as shown in Figure 2-15. Figure 2-15 Saving the analysis results using the IE The Save dialog box is displayed, as shown in 2.1.8 Figure 2-16. Click Save.
  36. 36. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 12 Figure 2-16 Save dialog box To download all diagnosis information such as KPIs, operation logs, and alarm logs in one package, click Download, as shown in Figure 2-17. Figure 2-17 Downloading diagnosis information in one package  If the default browser is the Firefox browser, choose Firefox > Save Page As, as shown in Figure 2-18.
  37. 37. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 13 Figure 2-18 Saving the analysis results using the Firefox The Save As dialog box is displayed, as shown in Figure 2-19. Click Save. Figure 2-19 Save As dialog box 2.1.8 FMA Dashboard Operation Guide The dashboard function supports the associated fault analysis of KPIs and counters, alarm log, and operation log in the last 8 hours and integrated analysis result display. The dashboard function displays all KPI and counter change trends in line charts. If you click a dot on a line,
  38. 38. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 14 the alarm and operation information at the specific time when the KPI or counter value is collected is highlighted. This helps locate the fault and restore services promptly. Note the following points when you use the dashboard function:  Starting the dashboard function After the fault analysis using the fault diagnosing function is complete, the dashboard is displayed as a part in the analysis report. This eases the operation and maintenance so that you do not have to switch pages when locating the fault. You can start the dashboard function in the following ways: − After you have selected the NE to be analyzed in the Scenario Options area, you can click Dashboard to start this function, as shown in Figure 2-20. Figure 2-20 Starting the Dashboard function The dashboard is displayed in the analysis report, as shown in Figure 2-21.
  39. 39. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 15 Figure 2-21 Dashboard displayed in the analysis report (1) − After you have selected the NE to be analyzed in the Scenario Options area, you can also click Start to start this function, as shown in Figure 2-20. The dashboard is displayed in the analysis report, as shown in Figure 2-22. Figure 2-22 Dashboard displayed in the analysis report (2)  Panes on the dashboard interface The default dashboard interface consists of three parts, as shown in Figure 2-23. The area in the upper-left corner is the KPI and counter change trend chart. The area in the upper-right corner is the operation log. The area at the bottom is the alarm log. You can input a specific time and click Query to query the alarm information in this area.
  40. 40. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 16 Figure 2-23 Dashboard interface  You can click a dot in a KPI or counter line, an alarm, or an operation entry to highlight it. The highlighted alarm and operation entry are displayed in white digits and blue background. If you click a dot in a KPI or counter line, the time when the KPI or counter value is collected is displayed in an orange vertical line.  If you click a dot in a KPI or counter line, alarms and operation entries at the specific time when the KPI or counter value is collected are highlighted.  The alarm log and operation log support the filter function. Risky commands are displayed in black digits and yellow background. You can double-click an operation entry or alarm to view its detailed information, as shown in Figure 2-24. Figure 2-24 Detailed alarm information  You can click Save to save the current dashboard interface, as shown in Figure 2-25.
  41. 41. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 17 Figure 2-25 Saving the current dashboard interface 2.2 Fault Information Collecting Function When faults occur, the information need to be collected onsite. However, there is various BSC logs, and the procedure for collecting these logs is complex. It is easy to make mistakes in collecting the logs, which leads to repeated collection of logs onsite and prolongs the troubleshooting. This function is introduced to simplify the procedure for collecting logs. You can use this function to collect site information quickly and accurately, thereby facilitating the troubleshooting. 2.2.1 Prerequisites The connection is functional between the LMT and the NE. The connection is functional between the BSC and the BTS. 2.2.2 Operation Guide 1, Quickly collect information. Step 1 Click FMA on the LMT home page. The FMA window is displayed. Step 2 In the FMA tab page, double click Information Collection. The Information Collection tab page is displayed. Step 3 Set parameters on the Information Quick-Collection tab page. Specify Start Time and Path Of Results. Step 4 Click Collection to start collecting fault information. Figure 2-26 shows the GUI parameter description.
  42. 42. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 18 Figure 2-26 GUI parameter description GUI Parameter Description Start Time Time when a fault occurs. Path Of Results Path for saving the log files to be collected. Subrack Subrack number Result Information about the log files that are collected, such as the file name, path for saving the files, and file size. First Progress Second Progress Progress of collecting log file. The second batch of log files start to be collected only after the connection of the first batch completes. Log files are collected in two batches so that the first logs can be viewed while the second batch is being collected for fast troubleshooting. 2, Collect customized information. Step 1 Click Device Maintenance on the LMT home page. The Device Maintenance window is displayed. Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Collect Fault Information. The Collect Fault Information tab page is displayed. Step 3 Set parameters on the Information Self-Collection tab page. Specify Path Of Results, Start Time, End Time, and List Files of Type. If MML command outputs need to be collected, enter the MML commands in the MML Commands area. Leave this area blank if no MML command output needs to be collected. Step 4 Click Collection to start collecting fault information. Figure 2-27 shows the GUI parameter description. Figure 2-27 GUI parameter description. GUI Parameter Description Path Of Results Path for saving the log files to be collected. Start Time End Time The end time must be later than the start time. List Files of Type Types of files to be collected.
  43. 43. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 19 MML Commands This area is added to support the one-click collection of logs and command outputs. This area allows only LST and DSP commands and a maximum of 100 such commands. Export Import When you click this button, the settings for file types will be saved to a configuration file under the path for saving the logs. In this way, you can directly import this configuration file next time you need to export the same types of files. 2.3 Hierarchical Delimitation 2.3.1 Overview This function decomposes faults based on standard protocol layers from the KPIs of the faulty network, until the smallest identifiable objects are obtained. The counters, alarms, status, and operations of these objects are displayed and identified to provide a fault analysis report for users. 2.3.2 Function Description Step 1 Click FMA on the LMT home page. The FMA window is displayed. Step 2 On the FMA tab page, click Hierarchical Delimitation. The Hierarchical Delimitation tab page is displayed. Step 3 Set parameters on the Hierarchical Delimitation tab page. Step 4 Click Analyze and wait for the fault analysis report. Table 2-3 GUI parameter description Parameter Description Confirm the start time Set the start time based on the time when faults occur. Select the KPI items Set this parameter based on the abnormal KPIs by observing the KPI trend curve. History analysis In the drop-down list, select the time of saving historical analysis reports, and click Query. Result  Successful operation A new browser window is displayed with the fault analysis report presented on a web page.
  44. 44. RAN16.0 Troubleshooting Guide 2 FMA Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 20 Table 2-4 Button Functions Button Name Description Save Report When using the IE browser, click this button to save the diagnosis report as an html page. On the saved html page, the log GUI does not provide the query or filtering function. When using the FireFox browser, there will be no Save Report button and you can use the save function of the browser itself to save the diagnosis report. Download Source Data Set this parameter based on the abnormal KPIs by observing the KPI trend curve. The following table lists information in a fault analysis report. Table 2-5 Information in a fault analysis report Button Name Description Fault cells Cells that are affected by faults. Scenario selection The smallest identifiable objects obtained after faults are decomposed based on standard protocol layers.  Unsuccessful operation A dialog box is displayed with the failure cause.
  45. 45. RAN16.0 Troubleshooting Guide 3 Common Maintenance Functions Issue 02 (2014-05-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd 21 3 Common Maintenance Functions 3.1 About This Chapter This chapter describes common maintenance functions and how to perform the functions during troubleshooting. 3.2 MBTS Emergency OM Channel This chapter describes the functions, application scenarios, and usage methods of MBTS emergency OM channel. 3.2.1 Overview If the OM channel of one mode in a separate-MPT MBTS fails, the available OM channels of other modes can be used for remote troubleshooting on the LMT for the base station whose OM channel is faulty. In this way, unnecessary site visit is avoided and fault location becomes efficient and cost-effective. Step 1 Function Introduction An emergency OM channel can be established between a GBTS and an eGBTS/NodeB/eNodeB, or among the eGBTS, NodeB, and eNodeB, as shown in Figure 3-1 and Figure 3-2. A GBTS can only serve as the proxy base station instead of the target base station. A base station whose OM channel is normal can serve as the proxy base station; while a base station whose OM channel is faulty is the target base station. Figure 3-1 Emergency OM channel between a GBTS and an eGBTS/NodeB/eNodeB

×