Escolar Documentos
Profissional Documentos
Cultura Documentos
Troubleshooting Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright 2010 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
and
are registered trademarks of ZTE CORPORATION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyones access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided as is and as available. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATIONs
products and technologies.
ZTE CORPORATION
Address:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website:
Email:
doc@zte.com.cn
Revision History
Product Version
V8.20.04 or higher versions
Document Version
1.0
Serial Number
-
Author
Date
2010-05-19
Document Version
1.0
Prepared by
Xiang Yijie
Reviewed by
-
Approved by
-
II
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ
Reference material
-
Follow-up document: After reading this document, you may need the following information
SEQ
1
Reference material
-
Information
-
III
Description
1 Overview
IV
TABLE OF CONTENTS
1
1.1
1.2
1.3
Overview ........................................................................................................... 1
About This Guide ............................................................................................... 1
Acronyms and Abbreviations ............................................................................. 1
Product Versions................................................................................................ 2
2
2.1
2.2
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
3
3.1
3.2
3.3
3.3.1
3.3.2
FIGURES
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 3-1
Figure 3-2
Failure Information.............................................................................................. 11
TABLES
Table 1-1
Table 1-2
VI
Overview
1.1
The first part introduces the organizational structure, acronyms and abbreviations,
and applicable scope of this guide.
The second part describes how to troubleshoot an undetected CHM board alarm.
The third part describes how to troubleshoot a CSM6800 bit test failure alarm.
It can serve as a reference for quick problem location and failure information feedback.
This guide is intended for the following audience:
1.2
Full Name
Functions
CHM
Channel
Handling
Module
Forward modulation
Backward demodulation
CCM
Communication
Control Module
Signaling control
Resource management
Data Service
Module
Signaling control
Data transfer
Trunk function
DSM
Acronyms
and
Abbreviations
PP2S and
16CHIP
1.3
Full Name
Functions
The PP2S and 16CHIP are CDMA BSS system
clocks, which are generated by the way of
receiving satellite signals from the GPS of the
BSC or BTS, and using 1PPS as a reference
phase lock as well.
Product Versions
Table 1-2 lists the product versions that are applicable to this guide.
Product Versions
V8.20.04 or higher versions
2.1
Symptom Description
The ALL-IP CCM board reports an undetected CHM board alarm.
2.2
Troubleshooting Procedure
Take BTSB I4 for example. You can troubleshoot CBTS I2 in a similar way.
To troubleshoot an undetected CHM board alarm, perform the following steps:
1.
Check whether the CCM and DSM boards run normally, as shown in Figure 2-1.
2.
3.
If the BTS reports any 32-chip, 16-chip, or PP2S clock alarm, check whether the
GCM board is normal, as shown in Figure 2-2.
4.
Check whether the CHM version is consistent with the released version, as shown
in Figure 2-3.
5.
Check whether the physically inserted CHM boards are consistent with those
configured in the OMC, as shown in Figure 2-4.
6.
Power off the CHM board, and then restart/reset it. Check whether the CHM board
is running normally, as shown in Figure 2-5.
7.
If this problem still persists, power off the BTS, and then replace the CHM board or
insert the CHM board in a different slot.
8.
Return the CHM board to the R&D Dept for performing the following cause analysis
and fault location:
Rack configuration
2.3
Cause Analysis
2.3.1
CCM/DSM Problem
If the CCM/DSM board is problematic, the OMC reports a link disconnection alarm. In this
case, the OMC cannot detect the CHM board. Therefore, you should verify that the CCM
board, DSM board, and E1 links are normal.
2.3.2
Clock Problem
The CHM board cannot start running until the CSM6800 bit test is passed. The CSM6800
bit test can be passed only when the 32-chip, 16-chip, and PP2S clock are normal. If a
32-chip, 16-chip, or PP2S clock is problematic, the BTS reports either an undetected
CHM board alarm or a CSM6800 bit test failure alarm. When reaching the preset time
interval, the CHM board gets automatically reset. In this case, the CSM6800 bit test
failure alarm disappears; however, the BTS reports the undetected CHM board alarm.
The BTS repeats the test-failure-alarm cycle. If the BTS reports a 32-chip, 16-chip, or
PP2S clock alarm, you need to check whether the GCM board is problematic or the OMC
can detect the CHM board.
2.3.3
Configuration Problem
The CHM board varies from type to type, from version to version. The physically inserted
boards may be incorrectly configured in the OMC. To avoid an undetected CHM board
problem, ensure that the physically inserted boards are consistent with those configured
in the OMC.
2.3.4
Board Problem
After having been running for a long time, the CHM board may experience one of the
following component failures:
BGA failure
In this case, the CHM board cannot be started, the field engineer cannot identify any
potential cause, and the OMC can neither detect the CHM board nor report any alarm.
Therefore, you need to replace the CHM board with a new one, and then return the
replaced CHM board for repair.
2.3.5
2.3.6
Engineering Problem
If an engineering problem occurs, you need to check whether the cabinet is correctly
grounded or the power supply is reliable.
3.1
Symptom Description
The ALL-IP CCM board reports a CSM6800 bit test failure alarm.
3.2
Troubleshooting Procedure
Take BTSB I4 for example. You can troubleshoot CBTS I2 in a similar way.
To troubleshoot a CSM6800 bit test failure alarm, perform the following steps:
1.
2.
If the BTS reports a 32-chip, 16-chip, or PP2S clock alarm, check whether the GCM
board is normal, as shown in Figure 3-1.
10
3.
11
4.
Report the failure information to the R&D Dept. for cause analysis.
5.
Check whether the clocks are normal. If yes, replace the CHM board or insert the
CHM board in a different slot, and then return the replaced CHM board for repair.
3.3
Cause Analysis
3.3.1
Clock Problem
The CHM board cannot start running until the CSM6800 bit test is passed. The CSM6800
bit test can be passed only when the 32-chip, 16-chip, and PP2S clock are normal. If a
32-chip, 16-chip, or PP2S clock is problematic, the BTS reports either an undetected
CHM board alarm or a CSM6800 bit test failure alarm. When reaching the preset time
interval, the CHM board gets automatically reset. In this case, the CSM6800 bit test
failure alarm disappears; however, the BTS reports the undetected CHM board alarm.
The BTS repeats the test-failure-alarm cycle. If the BTS reports a 32-chip, 16-chip, or
PP2S clock alarm, you need to check whether the GCM board is problematic or the OMC
can detect the CHM board.
3.3.2
Board Problem
After having been running for a long time, the CHM board may experience one of the
following failures:
In this case, the CHM board cannot be started, the field engineer cannot identify any
potential cause, and the OMC reports the undetected CHM alarm and CSM6800 bit test
failure alarm. Therefore, you need to replace the CHM board with a new one, and then
return the replaced CHM board for repair.
12