BSC Commissioning Guide: © 2008 Motorola, Inc. All Rights Reserved

BSC Commissioning Guide
RSR10
68P02909W06-A
2008 Motorola, Inc. All Rights Reserved.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
PRELIMINARY - UNDER DEVELOPMENT
Aug 2008
Table
of
Contents
Contents

Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of Change Notices. .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
Security advice. . . . . . . . . . . . .
Warnings, cautions, and notes . . . . .
Warnings. . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . .
Safety . . . . . . . . . . . . . . . . .
General safety . . . . . . . . . . .
Electromagnetic energy . . . . . .
Caring for the environment . . . . . .
In EU countries . . . . . . . . . .
In non-EU countries . . . . . . . .
CMM labeling and disclosure table . .
Motorola document set . . . . . . . .
Ordering documents and CD-ROMs
Document banner definitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
2
3
3
3
4
5
5
5
5
6
7
7
7
7
8
8
8
9
9
9
10
11
11
11
11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-4
1-6
1-7
1-9
1-10
1-13
1-14
Chapter 1: Safety Information

Safety Information . . . . . .
Safety Precautions . . . .
Electricity Safety. . . . .
Inflammable Environment
Battery . . . . . . . . . .
Radiation . . . . . . . .
Working at Heights . . .
Mechanical Safety . . . .
Others . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W06-A
Aug 2008
Contents
Chapter 2: Introduction to BSC Commissioning

.
.
.
.
.
.
.
.
.
2-2
2-3
2-4
2-4
2-4
2-6
2-6
2-6
2-6
BSC Commissioning Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2
3-2
Introduction to BSC Commissioning . . . . . . . . . .

Definition of the BSC Commissioning . . . . . . . . .
Entry Conditions of the BSC Commissioning . . . . . .
Requirements for the BSC Equipment Status . . .
Requirements for the BSC Commissioning Network
Preparations for the BSC Commissioning . . . . . . .
Software Installation Disk or Installation Package .
License File . . . . . . . . . . . . . . . . . . . .
Data Configuration File . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 3: BSC Commissioning Process
Chapter 4: Commissioning the BSC Equipment

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-3
4-3
4-3
4-3
4-4
4-7
4-8
4-8
4-8
4-14
4-15
4-19
4-21
4-21
4-21
4-22
4-22
4-23
4-25
4-29
4-29
4-29
4-30
4-30
4-30
4-31
4-33
4-33
4-33
4-33
4-35
4-35
4-35
4-35
Verifying the Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
Commissioning the BSC Equipment . . . . . . . . . . . . . . .

Commissioning the GOMU . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Software and Hardware Settings of the GOMU
Checking the Linux Operating System Version . . . . . . . .
Installing and Configuring the OMU Software . . . . . . . .
Checking the Operating Status of the OMU Software . . . .
Commissioning the LMT . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Installing the LMT Software . . . . . . . . . . . . . . . . .
Connecting the LMT PC to the GOMU . . . . . . . . . . . .
Starting the Local Manager . . . . . . . . . . . . . . . . .
Starting the MML Command Client . . . . . . . . . . . . .
Loading the BSC Host Software . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Downloading and Decompressing the Version Software . . .
Loading the Version Software . . . . . . . . . . . . . . . .
Activating the Version Software . . . . . . . . . . . . . . .
Querying the BSC Board Information . . . . . . . . . . . .
Querying BSC Board Information . . . . . . . . . . . . . .
Configuring the BSC Clock. . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading the Data Configuration File . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Switchover of the Active and Standby Boards . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Configuration of the License File. . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
Before Commissioning
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 5: Verifying the Ater Interface
ii
68P02909W06-A
Aug 2008
Contents
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Ater Interface When the GTCS is Configured on the BSC Side . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Physical Links on the Ater Interface (Configuration on the BSC Side) . . .
Verifying the User Plane on the Ater Interface (Configuration on the BSC Side) . . . . .
Verifying the Ater Interface When the GTCS is Configured on the MSC Side . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Physical Links on the Ater Interface (Configuration on the MSC Side) . . .
Verifying the Management Plane on the Ater Interface (Configuration on the MSC Side)
Verifying the User Plane on the Ater Interface (Configuration on the MSC Side) . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-3
5-3
5-3
5-13
5-18
5-18
5-18
5-28
5-30
Chapter 6: Verifying the A Interface

Verifying the A Interface . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . .
Verifying the A Interface (A over TDM) . . . . . . . . . . . .
Verifying the Physical Links on the A Interface . . . . . .
Verifying the Control Plane on the A Interface . . . . . . .
Verifying the User Plane on the A Interface . . . . . . . .
Verifying the A Interface (A over IP) . . . . . . . . . . . . . .
Verifying the Physical Links on the A Interface (A over IP) .
Verifying the Control Plane on the A Interface (A over IP) .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-2
6-3
6-3
6-11
6-18
6-22
6-22
6-23
Chapter 7: Verifying the Abis Interface

Verifying the Abis Interface . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . .
Verifying the Physical Links on the Abis Interface . . .
Prerequisites. . . . . . . . . . . . . . . . . . . .
Verifying the E1/T1 Links on the Abis Interface . .
Verifying the STM-1 Links on the Abis Interface . .
Verifying the Management Plane on the Abis Interface
Prerequisites. . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . .
Verifying the Control Plane on the Abis Interface . . .
Prerequisites. . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . .
Verifying the User Plane on the Abis Interface . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-2
7-2
7-3
7-3
7-3
7-7
7-12
7-12
7-12
7-12
7-15
7-15
7-15
7-15
7-18
7-18
7-18
7-18
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-2
8-2
8-3
8-3
8-3
8-7
8-9
8-9
8-10
8-11
8-11
Chapter 8: Verifying the Gb Interface

Verifying the Gb Interface . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . .
Verifying the Physical Links on the Gb interface . . .
Prerequisites. . . . . . . . . . . . . . . . . . .
Verifying the E1/T1 Links on the Gb Interface . .
Verifying the FE/GE Links on the Gb interface . .
Verifying the Links on the Gb Interface (Gb over FR)
Verifying the BC . . . . . . . . . . . . . . . . .
Verifying the NSVC . . . . . . . . . . . . . . .
Verifying the SIGBVC . . . . . . . . . . . . . .
Verifying the PTPBVC . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
68P02909W06-A
Aug 2008
iii
Contents
Verifying the Links on the Gb Interface (Gb over IP) .

Verifying the NSVL. . . . . . . . . . . . . . . .
Verifying the IP Routes on the Gb Interface . . .
Verifying the SIGBVC . . . . . . . . . . . . . .
Verifying the PTPBVC . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-13
8-13
8-13
8-14
8-15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-2
9-2
9-3
9-3
9-3
9-6
9-6
9-6
9-6
9-8
9-9
9-9
9-9
9-9
9-11
9-12
9-12
9-12
9-14
9-14
9-14
9-14
9-18
9-18
9-18
9-19
9-21
9-21
9-21
9-21
Chapter 9: Loading the BTS Software (Commissioning)

Loading the BTS Software (Commissioning)
Prerequisites. . . . . . . . . . . . . .
Downloading BTS Software . . . . . . . .
Prerequisites. . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
Configuring BTS Software . . . . . . . . .
Prerequisites. . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
Postrequisites . . . . . . . . . . . . .
Loading BTS Software . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
Postrequisites . . . . . . . . . . . . .
Querying BTS Attributes . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
Activating BTS Software . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
Querying BTS Running Status . . . . . . .
Prerequisites. . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
Querying BTS Board Information . . . . .
Prerequisites. . . . . . . . . . . . . .
Context . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 10: Processing Alarms Generated in the BSC Commissioning

Processing Alarms Generated in the BSC Commissioning . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10-2
10-2
10-2
Chapter 11: Verifying the BSC Services

Verifying the BSC Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-2
11-2
11-2
Chapter 12: Connecting the BSC to the OMC-S/T

Connecting the BSC
Prerequisites. .
Context . . . .
Procedure . . .
to the OMC-S/T .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12-2
12-2
12-2
12-2
68P02909W06-A
Aug 2008
Contents
Chapter 13: Checklist for BSC Commissioning

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-2
13-2
13-2
13-3
13-3
13-4
13-5
13-5
13-6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14-2
14-3
14-3
14-3
14-4
14-4
14-4
14-6
14-6
14-7
14-8
14-8
14-8
Appendix: Changes in BSC Commissioning Guide . . . . . . . . . . . . . . . . . . . . . . . .

01 (2008-07-21) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15-2
15-2
Checklist for BSC Commissioning . . . . . . .

Installing the GOMU and the LMT Software
Loading the BSC Host Software . . . . . .
Commissioning the BSC Local Office. . . .
Verifying the Ater Interface . . . . . . . .
Verifying the A Interface . . . . . . . . . .
Verifying the Abis Interface . . . . . . . .
Loading the BTS Software . . . . . . . . .
Verifying the BSC Services. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 14: Troubleshooting: Common Problems During

the BSC Commissioning
BSC Commissioning Troubleshooting . . . . . . . . .
Failure in Connecting the LMT to the GOMU . . . . .
Fault Description. . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . .
Faults on the Abis Interface Links . . . . . . . . . . .
Failure in Starting the GOMU Board . . . . . . . . . .
Fault Description . . . . . . . . . . . . . . . . .
Troubleshooting Method . . . . . . . . . . . . .
Inconsistent Data Configurations on the Abis/Ater/A/Gb
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
Interfaces
. . . . . .
. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 15: Appendix: Changes in BSC Commissioning Guide
68P02909W06-A
Aug 2008
Contents
vi
68P02909W06-A
Aug 2008
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1-1: Wearing an ESD wrist strap . . . . . . . . . . . . . . . . . . . . . . .

1-2: Lifting a weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3: Slant angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4: One meter higher than the eave . . . . . . . . . . . . . . . . . . . . .
2-1: BSC commissioning network. . . . . . . . . . . . . . . . . . . . . . .
4-1: Select Setup Language dialog box . . . . . . . . . . . . . . . . . . . .
4-2: License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3: Selecting an installation directory . . . . . . . . . . . . . . . . . . . .
4-4: Selecting software components . . . . . . . . . . . . . . . . . . . . .
4-5: Entering CD KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6: Confirming installation information . . . . . . . . . . . . . . . . . . .
4-7: Installation completed . . . . . . . . . . . . . . . . . . . . . . . . . .
4-8: Login dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-9: BSC Management dialog box . . . . . . . . . . . . . . . . . . . . . .
4-10: Local Manager in online mode . . . . . . . . . . . . . . . . . . . . .
4-11: BSC Local Manager in offline mode . . . . . . . . . . . . . . . . . .
4-12: User Login dialog box . . . . . . . . . . . . . . . . . . . . . . . . .
4-13: Query board version information window (1) . . . . . . . . . . . . . .
4-14: Query board version information window (2) . . . . . . . . . . . . . .
4-15: Querying results of board status . . . . . . . . . . . . . . . . . . . .
4-16: Load and Restore dialog box . . . . . . . . . . . . . . . . . . . . . .
4-17: BSC Device Panel dialog box . . . . . . . . . . . . . . . . . . . . . .
5-1: BSC Attributes tab page . . . . . . . . . . . . . . . . . . . . . . . . .
5-2: View Ater Connection Path dialog box . . . . . . . . . . . . . . . . . .
5-3: Querying the port status on one end of the Ater connection path . . . .
5-4: Querying the port status on the other end of the Ater connection path .
5-5: BSC Attributes tab page . . . . . . . . . . . . . . . . . . . . . . . . .
5-6: View Ater Connection Path dialog box . . . . . . . . . . . . . . . . . .
5-7: Querying the port status on one end of the Ater connection path . . . .
5-8: Querying the port status on the other end of the Ater connection pat . .
5-9: Maintain Ater Resource dialog box . . . . . . . . . . . . . . . . . . .
5-10: Query Ater Resource tab page . . . . . . . . . . . . . . . . . . . . .
5-12: BSC Attributes tab page . . . . . . . . . . . . . . . . . . . . . . . .
5-13: View Ater Connection Path dialog box . . . . . . . . . . . . . . . . .
5-14: Querying the port status on one end of the Ater connection path. . . .
5-16: BSC Attributes tab page . . . . . . . . . . . . . . . . . . . . . . . .
5-17: View Ater Connection Path dialog box . . . . . . . . . . . . . . . . .
5-18: Querying the port status on one end of the Ater connection path. . . .
5-20: Query Ater OML State dialog box . . . . . . . . . . . . . . . . . . .
5-21: Maintain Ater Resource dialog box . . . . . . . . . . . . . . . . . . .
68P02909W06-A
Aug 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-6
1-11
1-12
1-12
2-5
4-9
4-9
4-10
4-11
4-12
4-13
4-14
4-16
4-17
4-18
4-19
4-20
4-24
4-24
4-27
4-31
4-34
5-4
5-5
5-6
5-7
5-9
5-10
5-11
5-12
5-14
5-15
5-16
5-19
5-20
5-21
5-22
5-24
5-25
5-26
5-27
5-29
5-31
5-32
5-33
vii
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
6-1: BSC Attributes tab page . . . . . . . . . . . . . . . . .

6-2: View E1/T1 dialog box . . . . . . . . . . . . . . . . . .
6-3: Query Interface Board Port Information dialog box . . .
6-8: View SS7 Signaling Link dialog box . . . . . . . . . . .
6-9: Query MTP2 Link State dialog box. . . . . . . . . . . .
6-10: Maintain MTP3 Link dialog box . . . . . . . . . . . .
6-11: Configure Subrack-OPC Mapping dialog box . . . . . .
6-12: Maintain SCCP dialog box . . . . . . . . . . . . . . .
6-13: Maintain SCCP dialog box . . . . . . . . . . . . . . .
6-14: BSC Attributes tab page . . . . . . . . . . . . . . . .
6-15: View E1/T1 dialog box . . . . . . . . . . . . . . . . .
6-16: Maintain A Interface Circuit dialog box . . . . . . . .
7-1: Attributes tab page . . . . . . . . . . . . . . . . . . .
7-7: Maintain LAPD Link (1) dialog box . . . . . . . . . . .
7-8: Viewing the OML status . . . . . . . . . . . . . . . . .
7-9: Maintain LAPD Link (1) dialog box . . . . . . . . . . .
7-10: Viewing the RSL status . . . . . . . . . . . . . . . . .
7-11: Query Abis Interface Timeslot State dialog box. . . . .
7-12: Result of querying the status of the timeslot on the Abis
8-1: Attributes tab page . . . . . . . . . . . . . . . . . . .
9-1: Downloading the BTS software . . . . . . . . . . . . .
9-2: Selecting a file . . . . . . . . . . . . . . . . . . . . . .
9-3: Configure BTS Software dialog box (1) . . . . . . . . .
9-4: Configure BTS Software dialog box (2) . . . . . . . . .
9-5: Load BTS Software dialog box . . . . . . . . . . . . . .
9-6: Loading the BTS software . . . . . . . . . . . . . . . .
9-7: Loading result . . . . . . . . . . . . . . . . . . . . . .
9-8: Querying the BTS attributes . . . . . . . . . . . . . . .
9-9: Activate BTS Software dialog box (1) . . . . . . . . . .
9-13: Activating BTS software dialog box (5) . . . . . . . . .
9-14: Query BTS running status dialog box. . . . . . . . . .
9-15: Querying BTS running status . . . . . . . . . . . . . .
9-16: Querying board information . . . . . . . . . . . . . .
10-1: Browse Alarm window . . . . . . . . . . . . . . . . .
10-2: Alarm Detail Information dialog box . . . . . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
interface
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-4
6-5
6-6
6-8
6-9
6-10
6-12
6-13
6-14
6-15
6-16
6-17
6-18
6-19
6-20
6-21
7-4
7-5
7-6
7-8
7-9
7-10
7-13
7-13
7-16
7-16
7-19
7-20
8-4
8-5
8-6
9-4
9-5
9-7
9-8
9-10
9-10
9-11
9-13
9-15
9-15
9-16
9-16
9-17
9-19
9-20
9-22
10-3
10-4
68P02909W06-A
Aug 2008
List
of
Tables
List of Tables
Table 2-1: Equipment status before commissioning the BSC . . . . .

Table 4-1: Board status . . . . . . . . . . . . . . . . . . . . . . .
Table 9-1: Description of BTS running status parameters . . . . . .
Table 9-2: Description of cell running status parameters . . . . . .
Table 11-1: Procedures for verifying the basic services . . . . . . .
Table 11-2: Procedures for verifying the feature services . . . . . .
Table 13-1: Record of installing the GOMU and the LMT software . .
Table 13-2: Record of loading the BSC host software . . . . . . . .
Table 13-3: Record of commissioning the BSC local office . . . . . .
Table 13-4: Record of verifying the Ater interface when the GTCS is
side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-5: Record of verifying the Ater interface when the GTCS is
side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-6: Record of verifying the A Interface (A over TDM) . . . .
Table 13-7: Record of verifying the A Interface (A over IP). . . . . .
Table 13-8: Record of verifying the Abis Interface (Abis over TDM) .
Table 13-9: Record of loading the BTS software . . . . . . . . . . .
Table 13-10: Record of verifying the BSC services . . . . . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
configured
. . . . . .
configured
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
68P02909W06-A
Aug 2008
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
on the BSC
. . . . . . .
on the MSC
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
2-4
4-26
9-18
9-19
11-3
11-3
13-2
13-2
13-3
13-3
.
.
.
.
.
.
13-4
13-4
13-4
13-5
13-5
13-6
ix
List of Tables
68P02909W06-A
Aug 2008
About
This
Manual
What is covered in this manual?

This manual describes the purpose of commissioning the BSC. After installing the BSC
hardware, commission the BSC equipment, BSC software loading, interfaces, and services to
ensure that the BSC operates normally as expected.
This document provides guidelines for commissioning the BSC, such as BSC commissioning
process, commissioning the BSC equipment, commissioning the BSC interfaces, commissioning
the LMT, commissioning the BSC services, and connecting the BSC to the OMC-S/T.
This document is intended for:
Project engineers
Network operators
System engineers
Related information
NOTE
For changes in the document, refer to Chapter 15 Appendix: Changes in BSC
Commissioning Guide.
68P02909W06-A
Aug 2008
Revision history
Revision history
The following sections show the revision status of this document.
Version information
The following table lists the supported versions of this manual in order of issue:
Issue
Date of issue
Remarks
Aug 2008
Initial release
Resolution of Service Requests

The following Service Requests are resolved in this document:
Service Request
CMBP Number
Remarks
N/A
N/A
N/A
Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:
CN Date
CN Number
Title
N/A
N/A
N/A
68P02909W06-A
Aug 2008
General information
General information
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02909W06-A
Aug 2008
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.
Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
Special key sequences

Special key sequences are represented as follows:
CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or
CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
68P02909W06-A
Aug 2008
Contacting Motorola
Contacting Motorola
Motorola appreciates feedback from the users of our documents.
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Questions and comments

Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
The document title, part number, and revision character
The page number with the error
A detailed description of the error and if possible the proposed solution
68P02909W06-A
Aug 2008
Security advice
Security advice
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.
The implementation of these recommendations and final responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
68P02909W06-A
Aug 2008
Warnings, cautions, and notes
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
68P02909W06-A
Aug 2008
Safety
Safety
General safety
The following general safety guidelines apply to Motorola equipment:
The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Power down or unplug the equipment before servicing.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02909W06-A
Aug 2008
Caring for the environment
Caring for the environment
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging

European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02909W06-A
Aug 2008
CMM labeling and disclosure table
CMM labeling and disclosure table
The Peoples Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identified in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10
68P02909W06-A
Aug 2008
Motorola document set
Motorola document set
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner definitions

A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02909W06-A
Aug 2008
11
Data encryption
12
68P02909W06-A
Aug 2008
Chapter
1
Safety Information
68P02909W06-A
Aug 2008
1-1
Safety Information
Safety Information
Safety Precautions
This section describes certain safety precautions. Read and follow these safety precautions
before installing, operating, and maintaining Motorola devices. This section can also help to
choose the measurement device and testing device.
Following All Safety Precautions

Before any operation, read the instructions and precautions in this document carefully to
minimize the possibility of accidents.
The Danger, Caution, and Note items in the documents do not cover all the safety precautions
that must be followed. They only provide the generic safety precautions for operations.
Symbols
WARNING
This symbol indicates that casualty or serious accident may occur if you ignore the
safety instruction.
CAUTION
This symbol indicates that serious or major injury may occur if you ignore the safety
instruction.
NOTE
This symbol indicates that the operation may be easier if you pay attention to the
safety instruction.
Complying with the Local Safety Regulations

When operating the device, comply with the local safety regulations. The safety precautions
provided in the documents are supplementary.
1-2
68P02909W06-A
Aug 2008
Safety Precautions
General Installation Requirements

Train the personnel in charge of installation and maintenance to master the correct operating
methods and safety precautions before beginning work.
The rules for installing and maintaining th e device are as follows:
Only the trained and qualified personnel can install, operate, and maintain the device.
Only the qualified specialists are allowed to remove the safety facilities, and repair the
device.
Only qualified or authorized personnel of Motorola are to perform any replacement of the
device or part of the device (including the software) or any change to the device.
Report any fault or error that might cause safety problems immediately to the personnel
in charge.
Grounding Requirements
The following requirements are applicable to the device to be grounded:
Ground the device before installation and remove the ground cable after uninstallation.
Do not operate the device in the absence of a ground conductor. Do not damage the
ground conductor.
Ensure that the unit (or system) is permanently connected to the protection ground before
operation. Check the electrical connection of the device before operation and ensure that
the device is reliably grounded.
Safety of Personnel
Ensure the following:
When lightning strikes, do not operate the device and cables.
When lightning strikes, unplug the AC power connector. Do not use the fixed terminal or
touch the terminal or antenna connector.
NOTE
The previous two requirements are suitable for the wireless fixed terminal.
To prevent electric shock, do not connect safety extra-low voltage (SELV) circuits to
telecommunication network voltage (TNV) circuits.
To prevent laser radiation from injuring your eyes, never look into the optical fiber outlet
with unprotected eyes.
To prevent electric shock and burns, wear the electrostatic discharge (ESD) clothing,
gloves and wrist strap, and remove conductors such as jewelry and watch before operation.
68P02909W06-A
1-3
Aug 2008
Electricity Safety
Device Safety
Before operation, secure the device on the floor or other fixed objects, such as the walls
and the mounting racks.
Do not block ventilation openings while the system is running.
When installing the panel, use a screwdriver to tighten the screws.
Electricity Safety
High Voltage
WARNING
The high voltage power supply provides power for running the system. Direct
contact with the high voltage power supply or contact through damp objects may
result in fatal danger.
Non-standard and improper high voltage operations may result in fire and
electric shock.
Only qualified personnel must install the AC facility that performs operations on high
voltage and AC power supply facilities.
When installing the AC power supply facility, follow the local safety regulations.
When operating the AC power supply facility, follow the local safety regulations.
When operating the high voltage and AC power supply facilities, use the specific tools
instead of common tools.
When the operation is performed in a damp environment, ensure that water is kept off the
device. If the cabinet is damp or wet, shut down the power supply immediately.
Thunderstorm
The following requirements are suitable only for the wireless base station or the device with an
antenna or GPS antenna.
WARNING
In a thunderstorm, do not perform operations on high voltage and AC power supply
facilities or on a steel tower and mast.
1-4
68P02909W06-A
Aug 2008
Electricity Safety
High Electrical Leakage
CAUTION
Ground the device before powering on the device. Otherwise, the personnel and
device are in danger.
If the "high electrical leakage" flag is stuck to the power terminal of the device, ground the
device before you power it on.
Power Cable
CAUTION
Do not install and remove the power cable with a live line. Transient contact between
the core of the power cable and the conductor may generate electric arc or spark,
which may cause fire or eye injury.
Before installing or removing the power cable, turn off the power switch.
Before connecting the power cable, ensure that the power cable and label comply with
the requirements of the actual installation.
Fuse
CAUTION
To ensure that the system runs safely, when a fuse blows, replace it with a fuse of the
same type and specifications.
Electrostatic Discharge
CAUTION
The static electricity generated by the human body may damage the electrostatic
sensitive components on the circuit board, such as the large-scale integrated circuit
(LIC).
In the following situations, the human body generates a static electromagnetic field:
Movement of body parts
Clothes friction
Friction between shoes and the ground
Holding plastic in hand
The static electromagnetic field remains within the human body for a long time.
68P02909W06-A
1-5
Aug 2008
Before handling the device, plug boards, circuit boards, and application-specific integrated
circuits (ASICs), wear a grounded ESD wrist strap. The ESD strap can prevent the sensitive
components from damage by the static electricity in the human body.
Figure 1-1 shows how to wear an ESD wrist strap.
Figure 1-1
Wearing an ESD wrist strap
NOTE
For the GSM dual density base station, you need not wear an ESD wrist strap.
WARNING
Do not place the device in the environment that has inflammable and explosive air or
fog. Do not perform any operation in this environment.
Any operation of the electrical device in the inflammable environment causes danger.
1-6
68P02909W06-A
Aug 2008
Battery
Battery
Storage Battery
WARNING
Before handling the storage battery, read the safety precautions for the handling
and connection of the storage battery.
Incorrect operation of storage batteries may cause danger. During operation, ensure the
following:
Prevent any short-circuit.
Prevent the electrolyte from overflowing and leakage.
Electrolyte overflow may damage the device. It corrodes the metal parts and the circuit boards,
and ultimately damages the device and cause short-circuit of the circuit boards.
General Operations
Before installing and maintaining the storage battery, ensure the following:
Use special insulation tools.
Use eye protection devices and operate with care.
Wear rubber gloves and an apron in case of an electrolyte overflow.
Always keep the battery upright when moving. Do not place the battery upside down
or tilt it.
Short-circuit
WARNING
Short-circuit of the battery may cause injury. Although the voltage of a battery is low,
high transient current generated by a short-circuit releases a surge of power.
Keep metal objects away from the battery to prevent short circuit. If they have to be used,
disconnect the battery in use before performing any other operation.
68P02909W06-A
1-7
Aug 2008
Battery
Harmful Gas
CAUTION
Do not use unsealed lead-acid storage batteries, because the gas emitted from it
may result in fire or device corrosion.
Lay the storage battery horizontally and fix it properly.
The lead-acid storage battery in use emits flammable gas. Therefore, store it in a place with
good ventilation and take precautions against fire.
High Temperature
CAUTION
High temperature may result in distortion, damage, and electrolyte overflow of the
battery.
When the temperature of the battery exceeds 60oC, check whether there is acid overflow. If acid
overflow occurs, handle the acid immediately.
Acid
CAUTION
If the acid overflows, absorb and neutralize the overflow immediately.
When handling a leaky battery, protect against the possible damage caused by the acid. Use
the following materials to absorb and neutralize acid spills:
Sodium bicarbonate (baking soda): NaHCO3
Sodium carbonate (soda): Na2CO3
Use antacids according to the instructions provided by the battery manufacturer.
Lithium Battery
CAUTION
There is danger of explosion if the battery is incorrectly replaced.
Replace the lithium battery with the same or equivalent type recommended by the
manufacturer.
Dispose of the used battery according to the instructions provided by the manufacturer.
Do not dispose of the lithium battery in fire.
1-8
68P02909W06-A
Aug 2008
Radiation
Radiation
Electromagnetic Field Exposure
WARNING
High-power radio-frequency signals are harmful to the human body.
Before installing or maintaining an antenna on a steel tower or mast with a large number
of transmitter antennas, the operator should coordinate with all parties to ensure that the
transmitter antennas are shut down.
The base transceiver station (BTS) has RF radiation (radiation hazard). Suggestions for the
installation and operation of BTSs are given in the following section. Operators are also required
to comply with the related local regulations on erecting BTSs.
Locate the antenna in an area that is inaccessible to the public where the RF radiation
exceeds the stipulated value.
If the areas where RF radiation exceeds the stipulated value are accessible to workers,
ensure that workers know where these areas are. They can shut down the transmitters
before entering these areas. Such areas may not exist; but if they exist, the areas must
be within a range of less than 10 m around the antennas.
Indicate each forbidden zone by a physical barrier and striking sign to warn the public or
workers.
Laser
WARNING
When handling optical fibers, do not stand close to, or look into the optical fiber outlet
with unprotected eyes.
Laser transceivers or transmitters are used in the optical transmission system and associated
test tools. The laser transmitted through the optical fiber produces a small beam of light with
a high-power density and is invisible to human eyes. If a beam of light enters the eye, it can
damage the retina.
Normally, staring into the end of an un-terminated optical fiber or broken optical fiber with
unaided eyes from a distance of more than 150 mm (6 inches) does not cause eye injury. Eyes
may, however, be damaged if an optical tool such as a microscope, magnifying glass, or eye
loupe is used to stare into the bare optical fiber end.
Read the following guidelines to prevent laser radiation:
Only the trained and authorized personnel can perform the operation.
Wear a pair of eye-protective glasses when you are handling lasers or optical fibers.
Ensure that the optical source is switched off before disconnecting optical fiber connectors.
Never look into the end of an exposed optical fiber or an open connector if you cannot
ensure that the optical source is switched off.
68P02909W06-A
1-9
Aug 2008
Working at Heights
To ensure that the optical source is switched off, use an optical power meter.
Before opening the front door of an optical transmission system, ensure that you are not
exposed to laser radiation.
Never use an optical tool such as a microscope, a magnifying glass, or an eye loupe to
look into the optical fiber connector or end.
Read the following instructions before handling optical fibers:
Only the trained personnel can cut and splice optical fibers.
Before cutting or splicing an optical fiber, ensure that the optical fiber is disconnected from
the optical source. After disconnecting the optical fiber, use protecting caps to protect
all the optical connectors.
Working at Heights
CAUTION
When working at heights, ensure that the objects do not fall.
When working at heights, ensure to meet the following requirements:
Only trained personnel work at heights .
Carry the operating machines and tools and handle them safely to prevent them from
falling.
Take safety measures, such as wearing a helmet and a safety belt.
In cold regions, wear warm clothes before working at heights.
Ensure that the lifting appliances are prepared for working at heights.
Lifting Weights
CAUTION
Do not access the areas under the arm of the crane and the goods in suspension
when lifting weights.
Ensure that the operators have been trained and qualified.
Check the weight lifting tools and ensure that they are intact.
Lift the weight only when the weight lifting tools are firmly mounted onto the
weight-bearing object or the wall.
Use a concise instruction to prevent incorrect operation.
1-10
68P02909W06-A
Aug 2008
Working at Heights
The angle between the two cables should be less than or equal to 90o in the lifting of
weights (See Figure 1-2).
Figure 1-2
Lifting a weight
Safety Guide on Ladder Use

Checking the Ladder
Check the ladder before using it. Check the maximum weight that the ladder can support.
Never overload the ladder.
Placing the Ladder
The slant angle is preferred to be 75o. The slant can be measured with the angle square or
with arms, as shown in Figure 1-3. When using a ladder, place the wider end of the ladder
on the ground and take protective measures on the base of the ladder against slippage.
Place the ladder on a stable ground.
When climbing the ladder, ensure the following:
The gravity of the body does not shift from the edge of the ladder.
Keep balance on the ladder before performing any operation.
Do not climb higher than the fourth highest step of the ladder.
If you intend to climb to the roof, the length of the ladder should be at least one meter higher
than the eave, as shown in Figure 1-4.
68P02909W06-A
1-11
Aug 2008
Working at Heights
Figure 1-3
Slant angle
Figure 1-4
One meter higher than the eave
1-12
68P02909W06-A
Aug 2008
Mechanical Safety
Mechanical Safety
Drilling
CAUTION
Do not drill on the cabinet without permission. Inappropriate drilling on the cabinet
may damage the electromagnetic shielding and internal cables. Metal shavings from
the drilling if they get into the cabinet may result in a short-circuit of the circuit board.
Before drilling a hole on the cabinet, remove the cables from the cabinet.
During the drilling, wear protective glasses to protect your eyes.
During the drilling, wear the protective gloves.
Prevent the metal shavings from getting into the cabinet. After drilling, clean the metal
shavings in time.
Handling Sharp Objects
WARNING
When carrying the device by hand, wear the protective gloves to prevent injury by
sharp objects.
Handling Fans
When replacing a component, place the component, screw, and tool at a safe place to
prevent them from falling into the running fan.
When replacing the ambient equipment around the fan, wait until the fan is switched off
and stops running. Do not place the finger or board into the running fan.
Moving Heavy Objects

Wear the protective gloves when moving heavy objects.
CAUTION
Be careful when moving heavy objects.
When moving the chassis outwards, be aware about the unfixed or heavy objects
on the chassis to prevent injury.
68P02909W06-A
1-13
Aug 2008
Others
Two persons should be available to move a chassis; one person must not move a heavy
chassis. When moving a chassis, keep the back straight and move stably to prevent
a sprain.
When moving or lifting a chassis, hold the handle or bottom of the chassis. Do not hold
the handle of the installed modules in the chassis, such as the power module, fan module,
or board.
Others
Inserting and Removing a Board
CAUTION
When inserting a board, wear the ESD wrist strap or gloves. Insert the board gently to
prevent any bent pins on the backplane.
Insert the board along the guide rail.
Avoid contact of one board with another. This prevents a short-circuit or damage to the
boards.
Do not remove the active board before powering off.
When holding a board in hand, do not touch the board circuit, components, connectors,
or connection slots.
Bundling Signal Cables
CAUTION
Bundle the signal cables separately from the strong current cables or high voltage
cables.
Cabling Requirements
At a low temperature, movement of the cable may damage the plastic skin of the cable. To
ensure the construction safety, comply with the following requirements:
When installing cables, ensure that the environment temperature is above 0oC.
If cables are stored in the place below 0oC, move the cables into a place at a room
temperature. Store the cables for more than 24 hours at this temperature before
installation.
Move the cables with care, especially at a low temperature. Do not drop the cables
directly from the vehicle.
1-14
68P02909W06-A
Aug 2008
Chapter
2
Introduction to BSC Commissioning
68P02909W06-A
Aug 2008
2-1
This section describes the definition, the entry conditions of, and the preparations for the
BSC commissioning.
2-2
68P02909W06-A
Aug 2008
Definition of the BSC Commissioning
Definition of the BSC Commissioning
This section describes the definition of the BSC commissioning. After installing the BSC
hardware, commission the BSC equipment and interfaces. Load the BSC software and services
to ensure that the BSC operates normally as expected.
68P02909W06-A
2-3
Aug 2008
Entry Conditions of the BSC Commissioning
Entry Conditions of the BSC Commissioning
This section describes the entry conditions of the BSC commissioning. Before commissioning
the BSC, ensure that the BSC equipment status and the commissioning network meet the
entry conditions.
Requirements for the BSC Equipment Status

Table 2-1 describes the required status of the BSC equipment before the commissioning of
the BSC.
Table 2-1
Equipment status before commissioning the BSC
Item
Status
BSC hardware
The BSC hardware is already installed and has passed the hardware
installation check and the power-on test.
GOMU
The GOMU is set before delivery. For details, refer to Factory Setting
Table of the GOMU Software.
LMT PC
The LMT PC is configured as required. For details, refer to Configuration

Requirements of the LMT PC section in BSC LMT User Guide.

To smoothly commission the Abis Interface, Ater interface, A Interface, and Gb interface, ensure
to meet the following conditions:
A minimum of one BTS accesses the BSC and the BTS operates normally after
commissioning.
The BSC is connected to one MSC. The commissioning of the MSC is complete and the
MSC can provide the basic functions of the CS domain.
Three single-mode MSs and one dual-mode MS for testing are functional and are registered
with the HLR.
The BSC is configured with the GOMU to enable the communication between the LMT and the
BSC. Figure 2-1 shows a typical BSC commissioning network.
2-4
68P02909W06-A
Aug 2008
Figure 2-1
BSC commissioning network
NOTE
The lines in the preceding figure indicate only the connections rather than the
quantity and types of cables.
Figure 2-1 shows the typical commissioning network. Other scenarios are
possible for different applications.
68P02909W06-A
2-5
Aug 2008
Preparations for the BSC Commissioning
Preparations for the BSC Commissioning
This section describes the preparations for commissioning the BSC. Before commissioning
the BSC, keep the software installation disk or the installation package, license file, and data
configuration file ready.
Software Installation Disk or Installation Package

Before the commissioning, keep the following software installation disk or installation package
ready:
OMU installation disk or installation package that is consistent with the version used in
the local office
LMT installation disk or installation package that is consistent with the version used in
the local office
License File
Contact the Motorola technical personnel to apply for the license file that matches the office
configuration.
Data Configuration File

Correctly configure the data required in the commissioning and the data of the board, Abis
Interface, Ater interface, A Interface, and Gb interface.
2-6
68P02909W06-A
Aug 2008
Chapter
3
BSC Commissioning Process
68P02909W06-A
Aug 2008
3-1
Chapter 3: BSC Commissioning Process
This section describes the process of commissioning the BSC. This process consists of
commissioning BSC equipment, loading the BSC host software, verifying interfaces, loading the
BTS software, verifying the BSC services, and connecting the BSC to the OMC-S/T.
Procedure
Procedure 3-1
Commission the BSC equipment by referring to Chapter 4 Commissioning the BSC

Equipment.
The GTCS can be configured on the BSC side or on the MSC side. Based on different
configurations of the GTCS, you can choose different methods to verify the A interface. For
details, refer to Chapter 5 Verifying the Ater Interface.
Verify the A interface by referring to Chapter 6 Verifying the A Interface.
Verify the Abis Interface by referring to Chapter 7 Verifying the Abis Interface.
Verify the Gb interface by referring to Chapter 8 Verifying the Gb Interface.
Load the BTS software by referring to Chapter 9 Loading the BTS Software (Commissioning).
Process alarms generated in commissioning the BSC by referring to Chapter 10 Processing

Alarms Generated in the BSC Commissioning.
Verify the BSC services by referring to Chapter 11 Verifying the BSC Services.
Connect the BSC to the OMC-S/T by referring to Chapter 12 Connecting the BSC to the
OMC-S/T.
10
Check the results of commissioning the BSC by referring to Chapter 13 Checklist for BSC
Commissioning.
3-2
68P02909W06-A
Aug 2008
Chapter
4
Commissioning the BSC Equipment
68P02909W06-A
Aug 2008
4-1
Commissioning the BSC equipment is the basis of commissioning the entire BSC. The
commissioning of the interfaces and services can be performed only after the BSC equipment
is commissioned. Commissioning the BSC equipment involves commissioning the GOMU,
commissioning the LMT, commissioning the BSC clock, loading the data configuration file,
loading the BSC host software, verifying the switchover of the BSC active/standby boards, and
verifying the license file.
4-2
68P02909W06-A
Aug 2008
Commissioning the GOMU
Commissioning the GOMU
This section describes how to commission the GOMU. Check the software and hardware settings
of the GOMU, check the Linux operating system version, install the OMU software on site, and
check the operating status of the OMU software to enable the normal communication between
the LMT and the BSC.
Prerequisites
The Tables of the GOMU Software Installation Information are obtained.
Checking the Software and Hardware Settings of the GOMU

Before Commissioning
This section describes how to check the software and hardware settings of the GOMU before
commissioning the GOMU.
Procedure
Procedure 4-1
Checking the Software and Hardware Settings of the GOMU Before Commissioning
Check the hardware settings of the GOMU. For details on the technical specifications of the
GOMU, refer to Technical Specifications of the GOMU.
Check the software settings of the GOMU. For details on the technical specifications of the
GOMU,refer to Factory Setting Table of the GOMU Software. If the software settings are not
in accordance with the specifications, install the OMU software be referring to Installing and
Configuring the OMU Software on page 4-4.
Checking the Linux Operating System Version

This section describes how to check whether the Linux operating system version on the GOMU
board is correct.
68P02909W06-A
4-3
Aug 2008
Installing and Configuring the OMU Software
Procedure
Procedure 4-2
Checking the Linux Operating System Version
Start Telnet client, such as PuTTY on the LMT computer, enter the IP address of the GOMU
and log in as a root user.
Run the uname -r command to check the kernel version of the Linux operating system.
If the message 2.6.-7.244-smp is displayed, you can infer that the version is correct.
If the message 2.6.-7.244-smp is not displayed, you can infer that the version is
wroing. Use the system disk shipped with the equipment to create installation source
files and install the Linux operating system.

This section describes how to install and configure the OMU software on the GOMU board.
This process also describes how to configure the IP address of the external network of the
GOMU board.
Prerequisites
The DIP switch of the sub-rack that holds the GOMU board is set so that the sub-rack
works as sub-rack 0.
A PC that normally communicates with the GOMU is ready.
The OMU installation files and BSC board software package are saved in the directory
/BSC6000/install.
Context
Use a Straight-Through Cable to connect the PC to the ETH2 port on the GOMU board. Then,
set the IP address of the PC so that the IP address of the PC and that of ETH2 are in the same
network segment. If the OMU software is installed for the first time, the IP address of the ETH2
port is 192.168.1.1. and the subnet mask is 255.255.255.0.
Obtain the OMU software package, including OMU installation package host software package,
upgradecfg.xml, vercfg.xml, and verpkg.xml. The OMU installation package and host software
package are used to install the OMU software, and upgradecfg.xml and vercfg.xml are used
for the OMC-S/T to upgrade the OMU software, and verpkg.xml is used to upgrade the OMU
software in online mode.
CAUTION
Verify that no OMU software is installed by logging in to the board through PuTTY and
running the rpm -qa | grep omu command. If no information is displayed, you can
infer no OMU software is installed. If the OMU software is installed, the installation
fails.
4-4
68P02909W06-A
Aug 2008
Procedure
Procedure 4-3
Install the OMU software.

1.
Run the cd/BSC6000 command to refresh the current directory.
2.
Run the ls command to check the OMU installation file and BSC board software
package.
Linux:/BSC6000/install #ls
Linux:/BSC6000/install #ls
. .. boardfile.6.0.0.0.XX.zip
vercfg.xml verpkg.xml
omu-6.0.0.0-XX.i586.rpm
upgradecfg.xml
If the installation file and software package do not exist or the versions are incorrect,
obtain the correct file and package.
3.
Run the command rpm -Uvh omu-6.0.0.0-XX.i586.rpm, to install the OMU software.
Linux:/BSC6000/install #rpm -Uvh omu-6.0.0.0-XX.i586.rpm
Preparing...
################################### [100%]
Check the version of OS................................ done
Check the free space of BSC software partition......... done
Check the free space of BSC data partion............... done
Check the space of the memory.......................... done
1:omu
################################### [100%]
Linux:/BSC6000/install #
4.
When the message 1:omu ################################### [100%] is

displayed, installing the OMU software is complete.
CAUTION
If the installation file and software package do not exist or the versions are
incorrect, obtain the correct file and package.
Continued
68P02909W06-A
4-5
Aug 2008
Procedure 4-3
3
Installing and Configuring the OMU Software (Continued)
Configure the OMU software and the IP address of the external network of the GOMU board.
1.
Enter the command omuctrl cfg to configure the network. Type the external IP
address (10.161.84.223, for example) and press Enter.
hw-omu3:/BSC6000/install # omuctrl cfg
Please input the external
IP address: ======> 10.161.84.223
2.
Type the subnet mask (for example, 255.255.255.0) of the external IP address and press
Enter, as shown in the following ouput.
Please input the netmask of external
IP address: ======> 255.255.255.0
3.
Type the gateway (10.161.84.1, for example) of the external IP address and press
Enter, as shown in the following.
Please input the default gateway of external
IP address: ======> 10.161.84.1
4.
Type the system type GOMU and press Enter.
5.
Entering the external network configurations is complete. Check whether all the
configurations are correct, as shown in the following.
Configuration is listed as following:
IP address =======> 10.161.84.223
IP netmask =======> 255.255.255.0
IP gateway =======> 10.161.84.1 System type =======> GOMU
Gomu Location =======> Back
Are you sure?(yes/no) yes
If correct, type yes and press Enter. The configurations become valid.
If incorrect, type no and press Enter. The configurations become invalid.
6.
You are prompted whether to start the OMU software. Type no and press Enter so that
running the omuctrl cfg command is complete.
2008-04-09 12:08:28 bond0 already exist
2008-04-09 12:08:28 bond1 already exist
2008-04-09 12:08:28 Configuration file ifcfg-eth-id-00:18:82:1c:c6:3d
of eth1 was created
Do you want to start omu now?(yes/no) no
Continued
4-6
68P02909W06-A
Aug 2008
Checking the Operating Status of the OMU Software
Procedure 4-3
Installing and Configuring the OMU Software (Continued)
CAUTION
When you run the omuctrl cfg command to configure the network, the
operating system fails to check the validity of the IP address. Ensure that the
IP address is correct.
The network segments 192.168.10.*, 80.*.*.*, 81.*.*.*, and 82.*.*.*

are assigned to the internal channel and backup channel of the GOMU board.
The IP addresses of the external network and the debugging Ethernet adapter
must not be located in the network segments.
The IP addresses of the external network and the debugging Ethernet adapter
must not be located in the same network segment.
NOTE
The IP address of the external network of the GOMU board is bound up with the
external network team formed by ETH0 and ETH1.
4
When the cursor is displayed, installing the OMU software is complete.

This section describes how to check that the OMU software is running normally.
Procedure
Procedure 4-4
Run the omuctrl status command to check the operating status of the OMU software. The
following message is displayed:
The process pomu_core.bin is running.
The process pomu_local.bin is running.
The process omudaemon is running.
The former message indicates that the OMU software is running normally and that the
installation is successful.
If the message No omu process is running. is displayed, you can infer that the OMU
software is not running. Start the OMU software.
If the message is not displayed, you can infer that the OMU software is not normal.
Please contact Motorola for technical support.
68P02909W06-A
4-7
Aug 2008
Commissioning the LMT
Commissioning the LMT
This section describes how to commission the LMT to enable the communication between the
LMT and the BSC. The LMT can be used to commission the BSC.
Prerequisites
The GOMU commissioning is successful.
The LMT PC meets all requirements, for details, refer to Configuration Requirements of
the LMT PC section in BSC LMT User Guide.
Installing the LMT Software

This section describes how to install the LMT software on the LMT PC.
Prerequisites
Motorola provides the setup disk and the instructions on the installation of the LMT
software.
Ensure that the PC on which the LMT software is installed meets all the requirements listed
in the Configuration Requirements of the LMT PC section of BSC LMT User Guide.
Procedure
Procedure 4-5
Use the administrator account to log in to the operating system of the LMT PC.
Insert the setup disk into the CD-ROM drive.
NOTE
The setup program runs automatically. A window is displayed, as shown in

Figure 4-1.
If the setup program fails to run automatically, double-click setup.vbs in the

directory of the setup disk. A window is displayed, as shown in Figure 4-1.
Continued
4-8
68P02909W06-A
Aug 2008
Procedure 4-5
Figure 4-1
Installing the LMT Software (Continued)
Select Setup Language dialog box
Click Next. A dialog box is displayed, as shown in Figure 4-2.
Figure 4-2
License agreement
Continued
68P02909W06-A
4-9
Aug 2008
Procedure 4-5
4
Read the license agreement carefully.

1.
If you do not accept the terms of the license agreement, select I do not accept these
terms, and then click Cancel to quit the installation.
2.
If you accept the terms of the license agreement, select I accept these terms. and
then click Next. A dialog box is displayed, as shown in Figure 4-3.
Figure 4-3
Selecting an installation directory
Click Browse to select the installation directory.
NOTE
The default installation path is C:\Program Files\Motorola\Local Manager.
If the LMT software of other versions has been installed, the installation
path is the same as the earlier installation path by default. The path cannot
be changed.
If you want to change the installation path, you must uninstall the existing
LMT software of other versions.
Continued
4-10
68P02909W06-A
Aug 2008
Procedure 4-5
6
Click Next. A dialog box is displayed, as shown in Figure 4-4.
Figure 4-4
Selecting software components
Continued
68P02909W06-A
4-11
Aug 2008
Procedure 4-5
7
Select the software components, and then click Next (selecting all the components is
recommended). A dialog box is displayed, as shown in Figure 4-5.
Figure 4-5
Entering CD KEY
Continued
4-12
68P02909W06-A
Aug 2008
Procedure 4-5
8
Enter the CD KEY: BSC, and then click Next. A window is displayed, as shown in Figure 4-6.
Figure 4-6
Confirming installation information
Ensure that the settings are correct. Click Next. Copying files starts.
Continued
68P02909W06-A
4-13
Aug 2008
Connecting the LMT PC to the GOMU
Procedure 4-5
10
After copying files is complete, a dialog box is displayed, as shown in Figure 4-7.
Figure 4-7
11
Installation completed
Click Finish. The EasyInstall software is installed.
NOTE
A dialog box is displayed to prompt you to start the MML Command Client. Click
Yes to login to the MML Command Client, see Using the MML Command Client.

This section provides an example of connecting the LMT PC to the GOMU in a LAN. It describes
how the LMT PC is connected to the OM network of the BSC. Perform this operation only when
the LMT is used for the first time.
Prerequisites
The communication between the GOMU and the BSC host is normal.
The physical connection between the LMT PC and the GOMU is established.
4-14
68P02909W06-A
Aug 2008
Starting the Local Manager
Procedure
Procedure 4-6
Set the IP address of the LMT PC. For details, refer to Setting IP Address of LMT PC section
in BSC LMT User Guide.
On the LMT PC, choose Start>Run. In the Run dialog box, type cmd, and then press Enter.
The cmd.exe window is displayed.
In the cmd.exe window, type ping external IP address of GOMU.

If the information similar to the following display is returned, you can infer that the LMT PC
and the GOMU can communicate normally. In this example, the IP address of the external
network is 10.121.71.228.
Pinging 10.121.71.228 with 32 bytes of data: Reply from 10.121.71.228: bytes=32
time=1ms TTL=253 Reply from 10.121.71.228: bytes=32 time=1ms TTL=253 Reply from
10.121.71.228: bytes=32 time=1ms TTL=253 Reply from 10.121.71.228: bytes=32
time=1ms TTL=253 Ping statistics for 110.121.71.228:Packets: Sent=4, Received=4,
Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 1ms,
Maximum = 1ms, Average = 1ms

This section describes how to log in to the Local Manager in online mode or offline mode.
Prerequisites
If you log in to the Local Manager in the online mode, ensure to meet the following requirements:
The server is functional.
The LMT and the server are connected properly.
The BSC LMT and OMU software are correctly installed and their versions match with
each other.
Context
CAUTION
When the LMT application is running, do not modify the server time. Otherwise,
severe errors may occur to the system. If you have to modify the server time, stop all
the LMT application first.
The default user name used for the first login is admin. The password is admin.
68P02909W06-A
4-15
Aug 2008
If you start both the BSC LMT only, you can start multiple BSC LMTs at the same time to log
in to one BSC as follows:
If the OMC-S/T is connected, you can start 32 BSC LMTs at the same time to log in to
one BSC.
If the OMC-S/T is not connected, you can start 33 BSC LMTs at the same time to log
in to one BSC.
Procedure
Online mode
a.
Choose Start>All Programs>Motorola Local Manager>Version Number>BSC

Local Manager. The Login dialog box is displayed, as shown in Figure 4-8.
Figure 4-8
Login dialog box
4-16
68P02909W06-A
Aug 2008
b.
Click
Figure 4-9
. A dialog box is displayed, as shown in Figure 4-9.
BSC Management dialog box
c.
Enter the corresponding information in BSC Name, BSC IP, and Remark (optional),
and then click Add.
d.
Click Close to return to the dialog box shown in Figure 4-8.
e.
Enter User Name and Password, select BSC Name, and set User Type to Local
User.
f.
Click OK. A window is displayed, as shown in Figure 4-10.
68P02909W06-A
4-17
Aug 2008
Figure 4-10
Local Manager in online mode
Offline mode
a.
Choose Start>All Programs>Motorola Local Manager>Version Number>BSC

Local Manager. The Login dialog box is displayed as shown in Figure 4-8.
b.
Click offline. A dialog box is displayed, asking you to Select the data model to
config. Choose GOMU.
c.
A dialog box is displayed, asking you whether to restore the operated data files.
Choose Yes or No according to the following instruction, a window is displayed, as
shown in Figure 4-11.
Click Yes. The configuration data of last operation is generated.
Click No. The data is the minimum configuration data.
4-18
68P02909W06-A
Aug 2008
Starting the MML Command Client
Figure 4-11
BSC Local Manager in offline mode

This section describes how to start the MML Command Client and connect it to the BSC.
Prerequisites
The LMT runs normally.
The communication between the LMT and the BSC is normal.
Context
If you start MML Command Client only, you can start multiple MML Command Clients at the
same time to log in to one BSC as follows:
If the OMC-S/T is connected, you can start 65 MML Command Clients at the same time to
log in to one BSC.
If the OMC-S/T is not connected, you can start 68 MML Command Clients at the same
time to log in to one BSC.
68P02909W06-A
4-19
Aug 2008
Procedure
Procedure 4-7
1
Use one of the following three methods to start the Local Manager.
1.
Choose Start>All Programs>Motorola Local Manager>Motorola Local Manager.

A dialog box is displayed, as shown the Figure 4-12.
2.
On Local Manager, choose System>Start MML Client.
3.
On Local Manager, click the icon
to start the MML Command Client.
NOTE
The latter two methods are not displayed on the log-in dialog box.
Figure 4-12
Click
User Login dialog box
to add office, refer to Setting the Office Information section in BSC LMT User
Guide for configuration.

3
Click Login to start the MML Command Client.
4-20
68P02909W06-A
Aug 2008
Loading the BSC Host Software
This section describes how to load the BSC host software. Loading the BSC host software
involves the following steps:
Downloading and decompressing the version software.
Loading the version software.
Activating the version software.
Querying the board version information.
Querying the board information.
Prerequisites
The BSC host software of this office is stored in the directory \HW LMT\Common\SWM\software.
Downloading and Decompressing the Version Software

This section describes how to download and decompress the software package from the FTP
server to the BSC server. When the downloading is complete, the BSC server starts the
decompression of the software package automatically.
Prerequisites
The communication between the FTP server and the BSC is normal.
Before upgrading the BSC software, download the version software to the BSC server. The
SWM on the BSC server decompresses the installation package automatically.
The file name entered in the downloading command must be the same as the file name in
the FTP server and have the correct upper and lower case.
Context
68P02909W06-A
4-21
Aug 2008
Loading the Version Software
Procedure
Procedure 4-8
1
Downloading and Decompressing the Version Software
Run DLD VERPKG on the LMT to download and decompress the version software.

This section describes how to load the version software from the BSC server to the flash memory
of the boards where the software runs.
Prerequisites
The communication within the BSC is normal.
Context
The loading of version software is an optional step before the activation of version software.
When the version software is activated without being loaded, the BSC automatically compares
the software versions of the server and the board. If the software versions of the server and the
board are different, the BSC automatically loads the software version to the board.
Procedure
Procedure 4-9
1
Run LOD SOFTWARE on the LMT to load the version software.
Activating the Version Software

This section describes how to activate the version software that is loaded on each service board.
Prerequisites
4-22
68P02909W06-A
Aug 2008
Querying the BSC Board Information
Context
If you activate the version software by resetting the system, the services may be
interrupted.
The software of all boards is activated together. You cannot activate the software of
a specified board.
Procedure
Procedure 4-10
1
Activating the Version Software
Run ACT SOFTWARE on the LMT to activate the version software.

This section describes how to query the software and hardware information, patch information,
and loading option of the BSC board.
Prerequisites
The board to be queried is running normally.
Context
The patch information includes all patch packages related to each software version in both the
active area and the standby area. For details, refer to BSC Work Areas.
There are three loading modes: AUTO, From Server and From Flash. For details, refer
to BSC Software Loading.
Procedure
Through GUI
a.
Choose BSC Maintenance>Query Software>Query Board Version Information.

The Query Board Version Information window is displayed, as shown in
Figure 4-13.
68P02909W06-A
4-23
Aug 2008
Figure 4-13
b.
Query board version information window (1)
On the Software and Hardware Information tab page, set parameters in the Query
Mode and Board Selection areas, and then click Query. The results are displayed,
as shown in Figure 4-14.
Figure 4-14
Query board version information window (2)
4-24
68P02909W06-A
Aug 2008
Querying BSC Board Information
NOTE
Click the Patch Information and Loading Option tabs in Figure 4-13 in
step a to query the patch information and loading options.
Through MML
You can run the following commands on the MML Command Client to query detailed
information of BSC boards.
Run DSP BRDVER command to query the board versions.
Run DSP PATCH to command query the information about the board patch.
Run LST BRD to command query the attributes of the board loading.

This section describes how to query the status, the manufacturing information, and the property
of the boards.
Prerequisites
The boards are in position.
The board status refers to the position information, ADMIN state, Operation state, Standby
state, and Avail state.
The manufacturing information refers to the board type, bar code, BOM number, PCB
version, production date, and production area.
The board property refers to the current temperature and voltage of a board.
The sub-board information refers to the hardware version information of the sub-board.
Only the XPU, DPU, EIU, and OIU support the query of the sub-board information.
Context
Table 4-1 describes the board status that can be queried on the LMT.
68P02909W06-A
4-25
Aug 2008
Table 4-1
Board status
Parameter
Admin state
Meaning
Indicating whether the
current board can provide
services or not
Value Range
Lock: The current board cannot

provide services.
Unlock: The current board can

provide services, but whether it
actually provides services depends on
other states, such as operation state
and standby state.
Shutdown: New services cannot

access the current board, but the
existing services on the board
continue.
NOTE
After all the services on the
board exit, the board enters
Shutdown automatically.
Operation state
Standby state
Usage state

current board can be
operated or not

current board works in
active mode or standby
mode
indicating more information

about the board usage state
Enable: The current board can be

operated.
Disable: The current board cannot be

operated.
Active: The current board works in

active mode.
Standby: The current board works in

standby mode.
Unassigned: The current board is not

in active/standby mode.
Invalid: The current board is not

ready.
Normal: The current board is running

properly.
Fault: The current board is faulty.
Uninstalled: The current board is not

in position.
Inconsistent: The status information

about the current board is
inconsistent with the configuration
information about the slot.
Continued
4-26
68P02909W06-A
Aug 2008
Table 4-1
Board status (Continued)
Parameter
Meaning
Value Range
Power off: The current board is

powered off.
Procedure
Through GUI
a.
On the LMT, choose BSC Maintenance>Maintain Device>Query BSC Board

Information.
b.
Set parameters in the Location area, and then click Query. The query result is
displayed, as shown in Figure 4-15.
Figure 4-15
Querying results of board status
68P02909W06-A
4-27
Aug 2008
NOTE
Select the Board Status, Board Information, Board Property, or
Subboard Version tab page to query detailed information of BSC boards.
Through MML
Run the DSP BRDSTAT to query board status.
Run the DSP BRDELABEL to query board information.
Run the DSP BRD to query board property.
Run the DSP SUBBRDVER command to query the board versions.
4-28
68P02909W06-A
Aug 2008
Configuring the BSC Clock
Configuring the BSC Clock
This section describes how to configure the BSC reference clock for commissioning the BSC.
The BSC reference clock is responsible for the synchronization of boards in each sub-rack.
Prerequisites
The communication between the LMT and the GOMU is normal.
All the BSC sub-racks runs normally.
Procedure
In different scenarios, the BSC clock is configured differently as follows:

For details about how to configure the BSC reference clock when the BM and the TC
are configured in different sub-racks, refer to Configuring the BSC Clock (BM/TC
Separated).
For details about how to configure the BSC reference clock when the BM and the TC
are configured in the same sub-rack, refer to Configuring the BSC Clock (BM/TC
Combined).
For details about how to configure the BSC reference clock when the A Interface
adopts the IP transmission mode, refer to Configuring the BSC Clock (IP Transmission
Mode on the A Interface).
68P02909W06-A
4-29
Aug 2008
Loading the Data Configuration File
Loading the Data Configuration File
This section describes how to load the data configuration file saved on the LMT PC or the
data configuration file backed up on the server to the server. Thus, the BSC can run the data
configuration file.
Prerequisites
The BSC is functional.
Before loading the data configuration file, download and activate the BSC license. For
details, refer to Downloading the BSC License and Activating the BSC License.
Context
When the server becomes faulty, the backup data can be restored to ensure the normal
operation of the system service.
The procedure for loading the data configuration file in GUI mode is as follows:
Restore with local file

The configuration file is loaded from the LMT PC to the GOMU. Thus, the BSC runs the
loaded configuration file.
Load file from local to GOMU

The configuration file is loaded from the LMT PC to the GOMU.
Restore with GOMU file

The BSC runs the configuration file on the GOMU.
Delete GOMU file

The configuration file is deleted from the GOMU.
Restart GOMU
The GOMU is restarted with the current configuration data.
4-30
68P02909W06-A
Aug 2008
Procedure
CAUTION
After the configuration file is loaded, the communication between the LMT and
the GOMU is interrupted temporarily. Manually connect the LMT to the GOMU.
After the connection succeeds, the consistency check is performed in the entire
system. If the data is inconsistent, reset the related GOMU LOCAL processes
or the related boards.
After performing the loading and recovery operations, use the password
corresponding to the backup files to log in to the LMT. The login password used
before the loading and recovery becomes invalid.
The loading and recovery operations may cause the loss of the GOMU data.
Therefore, Motorola recommends that you back up the GOMU data before these
operations.
Procedure
Through GUI
a.
Choose Configuration>Load and Restore. A dialog box is displayed, as shown in

Figure 4-16.
Figure 4-16
Load and Restore dialog box
68P02909W06-A
4-31
Aug 2008
Procedure
b.
Select a file and an operation type, and then click Execute.
Through MML
a.
Run the STR BATCHFILESN command on the

MML Command Client to start the batch process.
Expected result: The execution is successful.
b.
Run the DLD BATCHFILE command on the MML

Command Client to download the batch files.
c.
Run the ACT BATCHFILE command on the MML Command Client

to resolve and run the batch files obtained in the preceding step.
d.
Run the LST BATCHFILESN command on the MML Command Client to query the information on the batch process.
NOTE
To load the batch files, run the ULD BATCHFILERST on the MML
Command Client.
To abort the batch process, run the CNL BATCHFILESN command on

the MML Command Client.
To end the batch process, run the END BATCHFILESN command on

the MML Command Client.
To forcibly terminate the batch process, run the FOE BATCHFILESN

command on the MML Command Client.
4-32
68P02909W06-A
Aug 2008
Verifying the Switchover of the Active and Standby Boards
Verifying the Switchover of the Active and Standby

Boards
This section describes how to verify the switchover of the active and standby boards. The
verification is performed to check whether the boards are functional after the switchover.
Prerequisites
The active and standby boards work normally.
Context
After the switchover of the active and standby boards, a stable call is not interrupted. A new call
can be accessed 10 seconds later. The GDPUP/GDPUX works in resource pool mode. If one board
fails, calls on the board are interrupted. Subsequent calls are not assigned to the faulty board.
For details about the switchover of the active and standby boards, refer to Switching Over
BSC Active/Standby Boards.
NOTE
If the BSC board required to be switched over does not have a standby board,
the switchover cannot be performed.
A BSC interface board can be switched over only when the board is in
active/standby mode.
Procedure
Through GUI
a.
On the Local Manager, click the BSC Attributes tab. A tab page is displayed, as
68P02909W06-A
4-33
Aug 2008
Procedure
Figure 4-17
b.
BSC Device Panel dialog box
On the tab page shown in Figure 4-17, set Current Cabinet to the cabinet where
the target BSC board is located. Check the operating status of the boards after the
switchover by referring to the colors on the lower right of the tab page shown in
Figure 4-17.
Through MML
Run the SWP BRD command on the MML Command Client to switch over the active and
standby boards.
Sub-rack Number: specifies the sub-rack number of the board to be switched over.
Slot Number: specifies the slot number of the board to be switched over.
4-34
68P02909W06-A
Aug 2008
Verifying the Configuration of the License File
This section describes how to verify the configuration of the license file. The verification is
performed to check whether the feature services authorized by the license file are valid.
Prerequisites
The GXPUM in the GMPS runs normally.
Context
Configuration
Includes such items as sequence number of the software, usage time limit, maximum
number of TRXs, number of cells, and various functions.
Application
Indicates the sequence number of the current license, usage time limit, number of TRXs,
number of cells, and the functions that are used currently.
Procedure
Procedure 4-11
1
Run the DSP LICENSE command on the MML Command Client to query the information on
the BSC license file.
68P02909W06-A
Aug 2008
4-35
Procedure
4-36
68P02909W06-A
Aug 2008
Chapter
5
Verifying the Ater Interface
68P02909W06-A
Aug 2008
5-1
This section describes how to verify the Ater Interface when the BM and the TC are configured
in different sub-racks.
Prerequisites
The physical connection between the GMPS/GEPS and the GTCS is established.
5-2
68P02909W06-A
Aug 2008
Verifying the Ater Interface When the GTCS is Configured on the BSC Side
Verifying the Ater Interface When the GTCS is

Configured on the BSC Side
This section describes how to verify the Ater interface when the BM and the TC are configured
in different sub-racks and the GTCS is configured on the BSC side. Verifying the Ater interface
involves verifying the physical links and the user plane on the Ater interface.
Prerequisites
The connection between the GMPS/GEPS and the GTCS is correct.
Verifying the Physical Links on the Ater Interface (Configuration

on the BSC Side)
This section describes how to verify the physical links on the Ater interface when the BM and
the TC are configured in different sub-racks and the GTCS is configured on the BSC side. The
physical link to be verified varies with the transmission mode. When the GEIUT serves as the
Ater interface board, the E1/T1 links are verified; when the GOIUT serves as the Ater interface
board, the STM-1 links are verified.
Verifying the E1/T1 Links on the Ater Interface (Configuration on the

BSC Side)
This section describes how to verify the E1/T1 links on the Ater interface when the GEIUT serves
as the Ater interface board and the GTCS is configured on the BSC side.
Prerequisites
68P02909W06-A
5-3
Aug 2008
Verifying the Physical Links on the Ater Interface (Configuration on the BSC Side)
Procedure
Through GUI
a.
On the Local Manager, click the BSC Attributes tab. A tab page is displayed,
Figure 5-1
BSC Attributes tab page
5-4
68P02909W06-A
Aug 2008
b.
Click Ater Conn. A dialog box is displayed, as shown in Figure 5-2.
Figure 5-2
View Ater Connection Path dialog box
NOTE
The GMPS and the GEPS belong to the BM.
c.
Find the Sub-rack No., Slot No., and Port No. of the Ater connection path. Click
Quit.
68P02909W06-A
5-5
Aug 2008
d.
Choose BSC Maintenance>Maintain Transmission and Signaling>Query

Interface Board Port Information. In the displayed dialog box, set the parameters
in the Board Location area (for example, sub-rack 11, slot 14, and port 0). Click
Query. The result is displayed, as shown in Figure 5-3.
Figure 5-3
Querying the port status on one end of the Ater connection path
5-6
68P02909W06-A
Aug 2008
e.
In Board Location, set sub-rack 5, slot 16, and port 0. Then, click Query. The
result is displayed, as shown in Figure 5-4.
Figure 5-4
Querying the port status on the other end of the Ater connection path
f.
Click Cancel.
If the status of port 0 of slot 14 in sub-rack 11 and the status of port 0 of slot 16 in
sub-rack 5 are normal, you can infer that the E1/T1 link on Ater connection
path 0 is normal.
g.
Repeat step c through step f to verify whether the E1/T1 links on other Ater
connection paths are normal.
68P02909W06-A
5-7
Aug 2008
Through MML
a.
b.
Run the DSP E1T1 command on the MML Command Client to query whether the
status of the E1/T1 link on the Ater connection path is normal.
Sub-rack Number: specifies the sub-rack number of the GEIUT on which the
Ater connection path is queried.
Slot Number: specifies the slot number of the GEIUT on which the Ater
connection path is queried.
Port Number: specifies the port number of the Ater connection path to be
verified. This parameter is optional.
Repeat step a to check whether other E1/T1 links on the Ater connection path are
normal.
Verifying the STM-1 Links on the Ater Interface (Configuration on the

BSC Side)
This section describes how to verify the STM-1 links on the Ater interface when the GOIUT
serves as the Ater interface board and the GTCS is configured on the BSC side.
Prerequisites
Procedure
Through GUI
a.
5-8
68P02909W06-A
Aug 2008
Figure 5-5
b.
68P02909W06-A
5-9
Aug 2008
Figure 5-6
NOTE
c.
Find the sub-rack number, slot number, and port number that match the Ater
connection path to be verified. For example, one end of Ater connection path 0 is
port 0 of slot 17 in sub-rack 0, and the other end is port 0 of slot 19 in sub-rack
8. Click Quit.
5-10
68P02909W06-A
Aug 2008
d.

Interface Board Port Information. In the displayed dialog box, enter sub-rack 0,
slot 17, and port 0. Set Query Object to Port, and then click Query. The result is
Figure 5-7
68P02909W06-A
5-11
Aug 2008
e.
In the Figure 5-7, enter sub-rack 8, slot 19, and port 0. Then, click Query. The
result is displayed, as shown in Figure 5-8.
Figure 5-8
Querying the port status on the other end of the Ater connection pat
f.
Click Cancel. If the status of port 0 of slot 17 in sub-rack 0 and the status of port 0 of
slot 19 in sub-rack 8 are normal, the STM-1 link on Ater connection path 0 is normal.
g.
Repeat step c through step f to verify whether the STM-1 links on other Ater
Through MML
a.
Run the DSP OPT command on the MML Command Client to query whether the status
of the STM-1 link on the Ater connection path is normal.
b.
Repeat step a to check whether other STM-1 links on the Ater connection path are
normal.
5-12
68P02909W06-A
Aug 2008
Verifying the User Plane on the Ater Interface (Configuration on the BSC Side)
Verifying the User Plane on the Ater Interface (Configuration

on the BSC Side)
This section describes how to verify the user plane on the Ater interface when the GTCS is
configured on the BSC side.
Prerequisites
Context
The status of the user plane on the Ater interface refers to the status of the service channel on
the Ater connection path.
Procedure
Through GUI
a.
On the Local Manager, choose BSC Maintenance>Maintain User

Resource>Maintain Ater Resource. A dialog box is displayed, as shown in
Figure 5-9.
68P02909W06-A
5-13
Aug 2008
Figure 5-9
b.
Maintain Ater Resource dialog box
In Figure 5-9, enter sub-rack 6, slot 15, and port 0. Then, click Query. The result
is displayed, as shown in Figure 5-10.
5-14
68P02909W06-A
Aug 2008
Figure 5-10
c.
Query Ater Resource tab page
68P02909W06-A
5-15
Aug 2008
Figure 5-11
d.
Click Cancel. If the State of the timeslot between port 0 of slot 15 in sub-rack 6 and
port 0 of slot 15 in sub-rack 8 is Idle, Occupied, or Uninstalled, you can infer that
the service channel on Ater connection path 1 is normal
e.
Repeat step a through step d to verify whether the service channels on other Ater
5-16
68P02909W06-A
Aug 2008
Through MML
a.
Run the DSP ATERTS command on the MML Command Client to query whether the
status of service channel on the Ater connection path is normal.
Sub-rack Number: specifies the sub-rack number of the GEIUT/GOIUT on

which the Ater connection path is verified.
Slot Number: specifies the slot number of the GEIUT/GOIUT on which the
Ater connection path is verified.
verified.
If the State of the timeslot on the port is Idle, you can infer that the service channel
on the Ater connection path is normal.
b.
Repeat step a to verify whether the service channels on other Ater connection
paths are normal.
68P02909W06-A
5-17
Aug 2008
Verifying the Ater Interface When the GTCS is Configured on the MSC Side
Verifying the Ater Interface When the GTCS is

Configured on the MSC Side
This section describes how to verify the Ater interface when the BM and the TC are configured
in different sub-racks and the GTCS is configured on the MSC side. Verifying the Ater interface
involves verifying the physical links and the user plane on the Ater interface.
Prerequisites
Verifying the Physical Links on the Ater Interface (Configuration

on the MSC Side)
This section describes how to verify the physical links on the Ater interface when the BM and
the TC are configured in different sub-racks and the GTCS is configured on the BSC side. The
physical link to be verified varies with the transmission mode. When the GEIUT serves as the
Ater interface board, the E1/T1 links are verified; when the GOIUT serves as the Ater interface
board, the STM-1 links are verified.
Verifying the E1/T1 Links on the Ater Interface (Configuration on the

MSC Side)
This describes how to verify the E1/T1 links on the Ater interface when the GEIUT serves as the
Ater interface board and the GTCS is configured on the MSC side.
Prerequisites
5-18
68P02909W06-A
Aug 2008
Verifying the Physical Links on the Ater Interface (Configuration on the MSC Side)
Procedure
Through GUI
a.
Figure 5-12
68P02909W06-A
5-19
Aug 2008
b.
Figure 5-13
NOTE
c.
Find the Sub-rack No., Slot No., and Port No. of the Ater connection path. Click
Quit.
5-20
68P02909W06-A
Aug 2008
d.

Figure 5-14
68P02909W06-A
5-21
Aug 2008
e.
In Board Location, set sub-rack 5, slot 16, and port 0. Then, click Query. The result
Figure 5-15
path
Querying the port status on the other end of the Ater connection
f.
Click Cancel.
sub-rack 5 are normal, you can infer that the E1/T1 link on Ater connection
path 0 is normal.
g.
Repeat step c through step f to verify whether the E1/T1 links on other Ater
5-22
68P02909W06-A
Aug 2008
Through MML
a.
b.
status of the E1/T1 link on the Ater connection path is normal.
Sub-rack Number: specifies the sub-rack number of the GEIUT on which the
Ater connection path is queried.
Slot Number: specifies the slot number of the GEIUT on which the Ater
connection path is queried.
verified. This parameter is optional.
Repeat step a to check whether other E1/T1 links on the Ater connection path are
normal.
Verifying the STM-1 Links on the Ater Interface (Configuration on the

MSC Side)
This section describes how to verify the STM-1 links on the Ater interface when the GOIUT
serves as the Ater interface board and the GTCS is configured on the MSC side.
Prerequisites
Procedure
Through GUI
a.
68P02909W06-A
5-23
Aug 2008
Figure 5-16
b.
5-24
68P02909W06-A
Aug 2008
Figure 5-17
NOTE
c.
Find the sub-rack number, slot number, and port number that match the Ater
connection path to be verified. For example, one end of Ater connection path 0 is
port 0 of slot 17 in sub-rack 0, and the other end is port 0 of slot 19 in sub-rack
8. Click Quit.
d.

slot 17, and port 0. Set Query Object to Port, and then click Query. The result
68P02909W06-A
5-25
Aug 2008
Figure 5-18
e.
5-26
68P02909W06-A
Aug 2008
Figure 5-19
path
Querying the port status on the other end of the Ater connection
f.
Click Cancel.
sub-rack 8 are normal, the STM-1 link on Ater connection path 0 is normal.
g.
Repeat step c through step f to verify whether the STM-1 links on other Ater
Through MML
a.
Run the DSP OPT command on the MML Command Client to query whether the status
of the STM-1 link on the Ater connection path is normal.
b.
Repeat step a to check whether other STM-1 links on the Ater connection path are
normal.
68P02909W06-A
5-27
Aug 2008
5: Verifying the Ater Interface
Chapter
Verifying the Management Plane on the Ater Interface

(Configuration on the MSC Side)
This describes how to verify the management plane on the Ater interface when the GTCS is
configured on the MSC side.
Prerequisites
Context
The management plane link on the Ater interface refers to the Ater OML.
Procedure
Through GUI
a.
On the Local Manager, choose BSC Maintenance>Maintain

Transmission and Signaling>Query Ater OML State.
A dialog box is displayed, as shown in Figure 5-20.
If the Available status of the HDLC link is Available, you can infer that the
management plane on the Ater interface is normal.
5-28
68P02909W06-A
Aug 2008
Figure 5-20
b.
Query Ater OML State dialog box
Click Cancel
Through MML
Run the DSP ATEROML command on the MML Command Client to query the status of
the Ater OML.
Sub-rack Number: specifies the sub-rack number of the GEIUT/GOIUT on which
the Ater OML is verified.
Slot Number: specifies the slot number of the GEIUT/GOIUT on which the Ater
OML is verified.
Port Number: specifies the port number of the Ater OML to be verified. This
parameter is optional.
If the Available status of the HDLC link is Available, you can infer that the management
plane on the Ater interface is normal.
68P02909W06-A
5-29
Aug 2008
Verifying the User Plane on the Ater Interface (Configuration on the MSC Side)
Verifying the User Plane on the Ater Interface (Configuration

on the MSC Side)
This section describes how to verify the user plane on the Ater interface when the GTCS is
configured on the MSC side.
Prerequisites
Context
The status of the user plane on the Ater interface refers to the status of the service channel on
the Ater connection path.
Procedure
Through GUI
a.

Resource>Maintain Ater Resource. A dialog box is displayed, as shown in
Figure 5-21.
5-30
68P02909W06-A
Aug 2008
Figure 5-21
Maintain Ater Resource dialog box
68P02909W06-A
5-31
Aug 2008
b.
Figure 5-22
5-32
68P02909W06-A
Aug 2008
c.
Figure 5-23
d.
Click Cancel.
If the State of the timeslot between port 0 of slot 15 in sub-rack 6 and port 0 of slot
15 in sub-rack 8 is Idle, Occupied, or Uninstalled, you can infer that the service
channel on Ater connection path 1 is normal.
e.
Repeat step a through step d to verify whether the service channels on other Ater
68P02909W06-A
5-33
Aug 2008
Through MML
a.
Run the DSP ATERTS command on the MML Command Client to query whether the
status of service channel on the Ater connection path is normal.
Sub-rack Number: specifies the sub-rack number of the GEIUT/GOIUT on

which the Ater connection path is verified.
Slot Number: specifies the slot number of the GEIUT/GOIUT on which the
Ater connection path is verified.
verified.
If the State of the timeslot on the port is Idle, you can infer that the service channel
on the Ater connection path is normal.
b.
Repeat step a to verify whether the service channels on other Ater connection
paths are normal.
5-34
68P02909W06-A
Aug 2008
Chapter
6
Verifying the A Interface
68P02909W06-A
Aug 2008
6-1
This section describes how to verify the A Interface. The A Interface can adopt the E1/T1
transmission mode or the FE/GE transmission mode. When the A Interface adopts the E1/T1
transmission mode, the mapping data link layer adopts the TDM transmission mode; when the
A Interface adopts the FE/GE transmission mode, the mapping data link layer adopts the IP
transmission mode.
Prerequisites
The physical connection between the BSC and the MSC is established.
The MSC used to verify the A Interface operates normally.
6-2
68P02909W06-A
Aug 2008
Verifying the A Interface (A over TDM)
Verifying the A Interface (A over TDM)
This section describes how to verify the A Interface on the BSC side when the A Interface
adopts the TDM transmission mode.
Verifying the Physical Links on the A Interface

This section describes how to verify the physical links on the A Interface when the E1/T1
transmission mode is adopted on the A Interface. The physical link to be verified on the A
Interface varies with the transmission mode. When the GEIUA serves as the A Interface board,
the E1/T1 links are verified; when the GOIUA serves as the A Interface board, the STM-1 links
are verified.
Prerequisites
Verifying the E1/T1 Links on the A Interface

This describes how to verify the E1/T1 links on the A Interface when the GEIUA serves as
the A Interface board.
Prerequisites
68P02909W06-A
6-3
Aug 2008
Procedure
Through GUI
a.
On the Local Manager, click the BSC Attributes tab. A taadminadb page is
Figure 6-1
6-4
68P02909W06-A
Aug 2008
b.
Click Timeslot of E1/T1 Int. A dialog box is displayed, as shown in Figure 6-2.
Figure 6-2
View E1/T1 dialog box
c.
On the A Interface E1/T1 tab page, find the configuration of the E1/T1 link to be
verified, for example, port 0 of slot 24 in sub-rack 0. Click Quit.
d.

slot 24, and port 0. Click Query. The result is displayed, as shown in Figure 6-3.
68P02909W06-A
6-5
Aug 2008
Figure 6-3
Query Interface Board Port Information dialog box
e.
If Port Status is Normal, you can infer that the E1/T1 link on the A Interface is
normal.
f.
Click Cancel.
g.
Repeat step c through step e to check whether other E1/T1 links are normal.
Through MML
a.
Run the DSP E1T1 command on the Local MML Command Client to query whether
the status of the E1/T1 link on the A Interface is normal.
Sub-rack Number: specifies the sub-rack number of the GEIUA on which the
E1/T1 link is queried.
Slot Number: specifies the slot number of the GEIUA on which the E1/T1 link is
queried.
Port Number: specifies of the E1/T1 link to be queried. This parameter is

optional.
6-6
68P02909W06-A
Aug 2008
NOTE
If Available Status is Normal, you can infer that the E1/T1 link on the A
Interface is normal.
b.
Repeat step a to check whether other E1/T1 links on the A Interface are normal.
Verifying the STM-1 Links on the A Interface

This section describes how to verify the STM-1 links on the A Interface when the GOIUA serves
as the A Interface board.
Prerequisites
Procedure
Through GUI
a.
68P02909W06-A
6-7
Aug 2008
Figure 6-4
6-8
68P02909W06-A
Aug 2008
b.
Click Timeslot of E1/T1 Int, and then click the A Interface E1/T1 tab, as shown
in Figure 6-5.
Figure 6-5
c.
Find the configuration of the link to be verified, for example, sub-rack 0, slot 15,
and port 0. Click Quit.
68P02909W06-A
6-9
Aug 2008
d.

Interface Board Port Information. In the displayed dialog box, set sub-rack 0, slot
15, and port 0. Click Query. The result is displayed, as shown in Figure 6-6.
Figure 6-6
If Avail Status is Normal, you can infer that the STM-1 link on the A Interface
is normal.
e.
Click Cancel.
f.
Repeat step c through step e to check whether other STM-1 links on the A Interface
are normal.
6-10
68P02909W06-A
Aug 2008
Verifying the Control Plane on the A Interface
Through MML
a.
Run the DSP OPT command on the MML Command Client to query whether the
status of the STM-1 link on the A Interface is normal.
NOTE
If Available Status is Normal, you can infer that the STM-1 link on the A
b.
Repeat step a to check whether other STM-1 links on the A Interface are normal.

This section describes how to verify the control plane on the A Interface on the BSC side.
Prerequisites
Context
The control plane links refer to the SS7 signaling links, which consist of MTP2 links, MTP3 links,
and SCCP subsystem. The MTP2 links are configured on the GEIUA or the GOIUA in the GEPS.
The MTP3 links and the SCCP subsystem are configured on the GXPUM in the GMPS/GEPS.
Query the status of the links from the lower layer, following the sequence of the MTP2 link, the
MTP3 link, and the SCCP subsystem.
68P02909W06-A
6-11
Aug 2008
Procedure
Procedure 6-1
1
On the Local Manager, click the BSC Attributes tab. A tab page is displayed, as shown
in Figure 6-7.
Figure 6-7
Continued
6-12
68P02909W06-A
Aug 2008
Procedure 6-1
2
Verifying the Control Plane on the A Interface (Continued)
Click A Signaling Link. In the displayed dialog box, as shown in Figure 6-8, you can
view that the Link No. is 0; the mapping STPC/DPC used by signaling link is C3; the
A interface board is in slot 15 in sub-rack 0; the XPU Slot No is 0, and the XPU CPU
No is 0. Click Quit.
Figure 6-8
View SS7 Signaling Link dialog box
Continued
68P02909W06-A
6-13
Aug 2008
Procedure 6-1
3
Choose BSC Maintenance>Maintain Transmission and Signaling>Query MTP2 Link

State. Then, select sub-rack 0 and SS7 link 0. Click Query. The result is displayed, as shown
in Figure 6-9. If Link State is Service Ready, you can infer that the MTP2 link is normal.
Figure 6-9
Query MTP2 Link State dialog box
Click Cancel.
Continued
6-14
68P02909W06-A
Aug 2008
Procedure 6-1
5
Choose BSC Maintenance>Maintain Transmission and Signaling>Maintain MTP3

Link. From the Operation drop-down list box, select Query By Link No.. Then, select
sub-rack 0 and link 0. Click Query. The result is displayed, as shown in Figure 6-10.
If Fault State is False, you can infer that the MTP3 link is normal.
Figure 6-10
Maintain MTP3 Link dialog box
Click Cancel.
Right-click the BSC in the management tree.

Continued
68P02909W06-A
6-15
Aug 2008
Procedure 6-1
8
Select Configure Sub-rack-OSP Mapping from the shortcut menu. A dialog box is
displayed, as shown in Figure 6-11 The OPC of sub-rack 0 is A2. Click Cancel.
Figure 6-11
Configure Subrack-OPC Mapping dialog box
Continued
6-16
68P02909W06-A
Aug 2008
Procedure 6-1
9
Choose BSC Maintenance>Maintain Transmission and Signaling>Maintain SCCP. On

the Destination Signaling Point tab page, set DPC to the value obtained through step 2.
OPC is A2. Click Query. The result is displayed, as shown in Figure 6-12.
If Destination signaling point state is Allow, SCCP state is Allow, and Congestion
state is Normal, you can infer that the DSP status of the SCCP link is normal.
Figure 6-12
Maintain SCCP dialog box
Continued
68P02909W06-A
6-17
Aug 2008
Verifying the User Plane on the A Interface
Procedure 6-1
10
Click the Subsystem Operation tab. From the OPC drop-down list box, select A2. From
the Subsystem No. drop-down list box, select 1. Click Query. The result is displayed,
Figure 6-13
Maintain SCCP dialog box
11
Query 1 and 254 in the Subsystem No. drop-down list box in sequence. If each subsystem
is in the Allow state, you can infer that the SCCP subsystem is normal.
12
Click Cancel.
If the status of the MTP2 link, MTP3 link, and SCCP subsystem is normal, you can infer that
the control plane link on the A interface is normal.

This section describes how to verify the user plane on the A Interface on the BSC side.
6-18
68P02909W06-A
Aug 2008
Prerequisites
Context
When A Interface adopts the TDM transmission mode, the user plane links on the A Interface
refer to the circuits on the A Interface.
Procedure
Through GUI
a.
Figure 6-14
68P02909W06-A
6-19
Aug 2008
b.
Click Timeslot of E1/T1 Int, and then click the A Interface E1/T1 tab, as shown in
Figure 6-15.
Figure 6-15
c.
Find the sub-rack number and the start CIC of the A Interface board to be verified.
For example, sub-rack 0 and start CIC 0. Click Quit.
d.
Choose BSC Maintenance>Maintain User Resource>Maintain A

Interface Circuit. Then, select a sub-rack number and set the range of
CICs. Click Query. The result is displayed, as shown in Figure 6-16.
If the CIC State is Idle, Occupied, Blocked, Peer Blocked, Installed, or
Uninstalled, you can infer that the circuit on the A Interface is normal.
6-20
68P02909W06-A
Aug 2008
Figure 6-16
e.
Maintain A Interface Circuit dialog box
Click Cancel.
Through MML
Run the DSP ACIC command on the MML Command Client to query the status of circuit
on the A Interface.
DPC Group Number: specifies the DPC group number of the A Interface.
Start CIC Number: specifies the start CIC number of the A Interface.
End CIC Number: specifies the end CIC number of the A Interface.
CIC State: indicates the status of the circuit that is queried. This parameter is
optional.
If the CIC State is Idle, Occupied, Blocked, Peer Blocked, Installed, or Uninstalled,
you can infer that the circuit on the A Interface is normal.
68P02909W06-A
6-21
Aug 2008
Verifying the A Interface (A over IP)
Verifying the A Interface (A over IP)
This section describes how to verify the A Interface on the BSC side when the A Interface
adopts the IP transmission mode.
Verifying the Physical Links on the A Interface (A over IP)

This section describes how to verify the physical links on the A Interface when the
GFGUA/GOGUA serves as the A Interface board.
Prerequisites
Procedure
Procedure 6-2
Verifying the Physical Links on the A Interface (A over IP)
Run the DSP DEVIP command on the MML Command Client to query the IP address of
the GFGUA/GOGUA.
Run the DSP IPRT command on the MML Command Client to query the route and the
destination IP address of the GFGUA/GOGUA.
Run the PING IP command on the MML Command Client and enter the destination IP
address obtained in step 2.
Postrequisites
If the ping to the destination address is successful, you can infer that the physical link on the A
Interface is available. If the ping to the destination IP address fails, do as follows:
1.
Query the status of the FE/GE port.

Run the LST ETHPORTPROP command on the MML Command Client to query the
information about the Ethernet port on the A Interface. If the Ethernet port is
deactivated, run the ACT ETHPORT command to activate the Ethernet port on the
GFGUA/GOGUA.
If the fault persists, check and ensure that the Ethernet cable is securely connected.
6-22
68P02909W06-A
Aug 2008
Verifying the Control Plane on the A Interface (A over IP)
If the fault persists, check and ensure that the local setting of the Ethernet port mode
is consistent with the settings on the peer end.
2.
Query the route and ping the IP address of the next hop.
If the fault persists, the possible cause is that the FE/GE port, the router, or the
switch fails. Rectify the faults.
If the ping to the destination address is successful, you can infer that the physical link
between the BSC and the next hop router is normal. Therefore, the fault may occur
on the peer end, and you can contact the peer engineer.

This section describes how to verify the OML on the A Interface when the GFGUA/GOGUA
serves as the A Interface board.
Prerequisites
The physical links on the A Interface are available.
Procedure
Procedure 6-3
Run the LST M3LNK command on the MML Command Client to query the configuration of
the M3UA link to be verified.The configuration includes the link set index, sub-rack number,
slot number, CPU number, and SCTP link index.
Run the DSP M3LNK command on the MML Command Client and enter the sub-rack
number, slot number, and the CPU number to query the status of the M3UA link.
Run the DSP SCCPSTATUSBTSP command on the MML Command Client to query the
status of the SCCP link.
NOTE
If the status of the M3UA link and the status of the SCCP link are normal, you can
infer that the OML on the A interface is normal.
68P02909W06-A
Aug 2008
6-23
6-24
68P02909W06-A
Aug 2008
Chapter
7
Verifying the Abis Interface
68P02909W06-A
Aug 2008
7-1
This section describes how to verify the Abis Interface on the BSC side when commissioning
the BSC.
Prerequisites
The physical connection between the BSC and the BTS is established. The acceptance
of the hardware installation is complete.
The BTS used to verify that the Abis Iterface is commissioned and is ready for the cell setup.
Context
One BTS is taken as an example to describe the procedures for commissioning the Abis
Interface. If multiple BTSs access the BSC, repeat each step.
7-2
68P02909W06-A
Aug 2008
Verifying the Physical Links on the Abis Interface
Verifying the Physical Links on the Abis Interface
This section describes how to verify the physical links on the Abis Interface. The physical link
that is to be verified on the Abis Interface varies with the transmission mode. When the GEIUB
serves as the Abis Interface board, the E1/T1 links are verified. When the GOIUB serves as the
Abis Interface board, the STM-1 links are verified.
Prerequisites
Verifying the E1/T1 Links on the Abis Interface

This section describes how to verify the E1/T1 links on Abis Interface when the GEIUB serves as
the Abis Interface board. If multiple BTSs access the BSC, repeat the operation.
Prerequisites
68P02909W06-A
7-3
Aug 2008
Procedure
Through GUI
a.
Figure 7-1
Attributes tab page
7-4
68P02909W06-A
Aug 2008
b.
Click Timeslot of E1/T1 Int, and then click the Abis Interface E1/T1 tab, as shown
in Figure 7-2.
Figure 7-2
c.
Find the timeslot occupied by the E1/T1 link on the Abis Interface and the
configuration of the mapping GEIUB. Click Quit.
d.

68P02909W06-A
7-5
Aug 2008
Figure 7-3
NOTE
If Port Status is Normal, you can infer that
the E1/T1 link on the Abis Interface is normal.
If Port Status is Fault, you can infer that the E1/T1 link on the
Abis Interface fails. Rectify the faults on the E1/T1 link. For
details, refer to Troubleshooting E1/T1 Transmission Faults.
If Port Status is Loopback, infer that the E1/T1 link on the Abis Interface
is being tested.
e.
Click Cancel.
f.
Repeat step c through step e to check whether other E1/T1 links on the Abis
Interface are normal.
7-6
68P02909W06-A
Aug 2008
Verifying the STM-1 Links on the Abis Interface
Through MML
a.
Run the DSP E1T1 command on the MML Command Client to query the status of the
E1/T1 link on the Abis Interface.
Sub-rack Number: specifies the sub-rack number of the GEIUB on which the
Slot Number: specifies the slot number of the GEIUB on which the E1/T1 link
is queried.
Port Number: specifies the port number of the E1/T1 link to be queried. This
NOTE
If Available Status is Normal, you can infer that the E1/T1 link on the Abis
b.
Repeat step a to check whether other E1/T1 links on the Abis Interface are normal.

This section describes how to verify the STM-1 links on the Abis Interface board when the GOIUB
serves as the Abis Interface board. If multiple BTSs access the BSC, repeat the operation.
Prerequisites
68P02909W06-A
7-7
Aug 2008
Procedure
Through GUI
a.
Figure 7-4
7-8
68P02909W06-A
Aug 2008
b.
Click Timeslot of E1/T1 Int, and then click the Abis Interface E1/T1 tab, as shown
in Figure 7-5.
Figure 7-5
c.
Find the configuration of the link that is to be verified. Click Quit.
d.

68P02909W06-A
7-9
Aug 2008
Figure 7-6
NOTE
If Avail Status is Normal, you can infer that
the STM-1 link on the Abis Interface is normal.
If Avail Status is Fault, you can infer that the STM-1 link on
the Abis Interface fails. Rectify the faults on the STM-1 link. For
details, refer to Troubleshooting Optical Transmission Faults.
If Avail Status is Loopback, you can infer that the STM-1 link on the Abis
Interface is being tested.
e.
Click Cancel.
f.
Repeat step c through step e to check whether other STM-1 links are normal.
7-10
68P02909W06-A
Aug 2008
Through MML
a.
Run the DSP OPT command on the MML Command Client to query the status of the
STM-1 link on the Abis Interface.
NOTE
If Available Status is Normal, you can infer that the STM-1 link on the
Abis Interface is normal.
b.
Repeat step a to check whether other STM-1 links on the Abis Interface are normal.
68P02909W06-A
7-11
Aug 2008
This section describes how to verify the management plane on the Abis Interface. If multiple
BTSs access the BSC, repeat the operation.
Prerequisites
Context
The management plane link on the Abis Interface refers to the OML.
Procedure
Through GUI
a.
On the Local Manager, choose BSC Maintenance>Maintain Transmission and

Signaling>Maintain LAPD Link. A dialog box is displayed, as shown in Figure 7-7.
7-12
68P02909W06-A
Aug 2008
Procedure
Figure 7-7
b.
Maintain LAPD Link (1) dialog box
In the LAPD Link No. Scope, select OML. Select a BTS on which the OML status is
queried in the Candidate NE area, and then add the BTS to the Selected NE area.
Click Query. A dialog box is displayed, as shown in Figure 7-8.
Figure 7-8
Viewing the OML status
68P02909W06-A
7-13
Aug 2008
Procedure
NOTE
c.
If State is Normal, you can infer that the management plane on the
If State is Congestion, you can infer that the OML on the Abis
Interface is congested because of excessive traffic. Handle the
congested OML.
If State is Fault, you can infer that the management plane on the
Abis Interface fails to send or receive data. Rectify the faults on the
OML. For details, refer to Troubleshooting OML Faults.
Click Cancel.
Through MML
a.
Run the DSP LAPDLNK command on the MML Command Client to query the status of
the OML on the Abis Interface. CSE Number specifies the CSE number of the OML
that is to be verified on the Abis Interface.
b.
Repeat step a to check whether other OMLs on the Abis Interface are normal.
7-14
68P02909W06-A
Aug 2008
Verifying the Control Plane on the Abis Interface
Verifying the Control Plane on the Abis Interface
This section describes how to verify the control plane on the Abis Interface. If multiple BTSs
access the BSC, repeat the operation.
Prerequisites
Context
The control plane link on the Abis Interface refers to the RSL.
Procedure
Through GUI
a.
On the Local Manager, choose BSC Maintenance>Maintain Transmission and

Signaling>Maintain LAPD Link. A dialog box is displayed, as shown in Figure 7-9.
68P02909W06-A
7-15
Aug 2008
Procedure
Figure 7-9
b.
Maintain LAPD Link (1) dialog box
In the LAPD Link No. Scope, select RSL. Select a BTS on which the RSL status is
queried in the Candidate NE area, and then add the BTS to the Selected NE area.
Click Query. A dialog box is displayed, as shown in Figure 7-10.
Figure 7-10
Viewing the RSL status
7-16
68P02909W06-A
Aug 2008
Procedure
NOTE
c.
If State is Normal, you can infer that the control plane on the Abis
If State is Congestion, you can infer that the RSL is congested

because of excessive traffic. Handle the congested RSL. For details,
refer to Congestion Troubleshooting Methods.
If State is Fault, you can infer that the RSL fails to send or
receive data. Rectify the faults on the RSL. For details, refer to
Troubleshooting OML Faults.
Click Cancel.
Through MML
a.
Run the DSP LAPDLNK command on the MML Command Client to query the status of
the RSL on the Abis Interface.CSE No: specifies the CSE number of the RSL that
is to be verified on the Abis Interface.
b.
Repeat step a to check whether other RSLs on the Abis Interface are normal.
68P02909W06-A
7-17
Aug 2008
Verifying the User Plane on the Abis Interface
Verifying the User Plane on the Abis Interface
This section describes how to verify the user plane on the Abis Interface. If multiple BTSs
access the BSC, repeat the operation.
Prerequisites
Context
The user plane on the Abis Interface refers to the timeslots on the GEIUB/GOIUB that is
connected to the BTS.
Procedure
Through GUI
a.

Resource>Query Abis Interface Timeslots State. A dialog box is displayed, as
7-18
68P02909W06-A
Aug 2008
Procedure
Figure 7-11
b.
Query Abis Interface Timeslot State dialog box
Select Sub-rack No., Slot No., and Port No. for the GEIUB/GOIUB that is connected
to the BTS. Click Query. The result is displayed, as shown in Figure 7-12.
68P02909W06-A
7-19
Aug 2008
Procedure
Figure 7-12
Result of querying the status of the timeslot on the Abis interface
NOTE
c.
If State is Idle, you can infer that the current timeslot does not carry
any service.
If State is Occupied, you can infer that the current timeslot transmits
services.
If State is Fault, you can infer that the current timeslot is unavailable.
If State is Uninstalled, you can infer that the current timeslot is not
assigned a channel.
Click Cancel.
7-20
68P02909W06-A
Aug 2008
Procedure
Through MML
a.
Run the DSP ABISTS command on the MML Command Client to query the timeslot
status on the Abis Interface of the GEIUB/GOIUB.
Sub-rack Number: specifies the sub-rack number of the GEIUB/GOIUB that

is to be queried.
Slot Number: specifies the slot number of the GEIUB/GOIUB that is to be

queried.
Port Number: specifies the port number of the GEIUB/GOIUB that is to be

queried.
State: indicates the status of the timeslot that is to be queried. This parameter
is optional.
NOTE
b.
If State is Idle or Occupied, you can infer that the user plane on the
Repeat step a to check whether other timeslots on the Abis Interface of the
GEIUB/GOIUB are normal.
68P02909W06-A
Aug 2008
7-21
Procedure
7-22
68P02909W06-A
Aug 2008
Chapter
8
Verifying the Gb Interface
68P02909W06-A
Aug 2008
8-1
This section describes how to verify the Gb interface when the built-in PCU is configured for
the BSC.
Prerequisites
The local office commissioning is complete.
The physical connection between the BSC and the SGSN is established.
The SGSN is functional.
8-2
68P02909W06-A
Aug 2008
Verifying the Physical Links on the Gb interface
Verifying the Physical Links on the Gb interface
This section describes how to verify the physical links on the Gb interface. The physical link
that is to be verified on the Gb interface varies with the transmission mode. When the GEPUG
serves as the Gb interface board, the E1/T1 links are verified. When the GFGUG serves as the
Gb interface board, the FE/GE links are verified.
Prerequisites
Verifying the E1/T1 Links on the Gb Interface

This section describes how to verify the E1/T1 links on the Gb interface when the GEPUG
serves as the Gb interface board.
Prerequisites
Procedure
Through GUI
a.
68P02909W06-A
8-3
Aug 2008
Figure 8-1
b.
Attributes tab page
Click Timeslot of E1/T1 Int, and then click the Gb Interface E1/T1 tab, as shown
in Figure 8-2.
8-4
68P02909W06-A
Aug 2008
Figure 8-2
c.
Find the configuration of the E1/T1 link that is to be verified. Click Quit.
d.

68P02909W06-A
8-5
Aug 2008
Figure 8-3
NOTE
If Port Status is Normal, you can infer that the E1/T1 link on the Gb
interface is normal. If Port Status is Fault, you can infer that the E1/T1
link on the Gb interface fails. Rectify the faults on the E1/T1 link. For
details, refer to Troubleshooting E1/T1 Transmission Faults. If Port Status
is Loopback, you can infer that the E1/T1 link on the Gb interface is
being tested.
e.
Click Cancel.
f.
Repeat step c through step e to check whether other E1/T1 links on the Gb interface
are normal.
8-6
68P02909W06-A
Aug 2008
Verifying the FE/GE Links on the Gb interface
Through MML
a.
status of the E1/T1 link on the Gb interface is normal.
Sub-rack Number: specifies the sub-rack number of the GEPUG on which the
Slot Number: specifies the slot number of the GEPUG on which the E1/T1
link is queried.
Port Number: specifies the port number of the E1/T1 link that is to be queried.
This parameter is optional.
NOTE
If Available Status is Normal, you can infer that the E1/T1 link on the Gb
interface is normal.
b.
Repeat step a to check whether other E1/T1 links on the Gb interface are normal.

This section describes how to verify the FE/GE links on the Gb interface when the GFGUG
serves as the Gb interface board.
Prerequisites
Procedure
Procedure 8-1
1
Run the DSP ETHPORT command on the MML Command Client to query the information
about the Ethernet port on the Gb interface.
Sub-rack Number: specifies the sub-rack number of the GFGUG on which the FE/GE
link is queried.
Slot Number: specifies the slot number of the GFGUG on which the FE/GE link is
queried.
Continued
68P02909W06-A
8-7
Aug 2008
Procedure 8-1
Verifying the FE/GE Links on the Gb interface (Continued)
Port Number.: specifies the port number of the FE/GE link to be queried. This
NOTE
If Link Status is up, you can infer that the FE/GE link on the Gb interface is
normal.
2
Repeat step 1 to check whether other FE/GE links on the Gb interface are normal.
8-8
68P02909W06-A
Aug 2008
This section describes how to verify the links on the Gb interface when the Gb interface adopts
the FR transmission mode. Verifying the links on the Gb interface involves verifying the bearer
channel (BC), the network service virtual connection (NSVC), the SIG BSSGP virtual connection
(SIGBVC), and the PTP BSSGP virtual connection (PTPBVC).
Verifying the BC
This section describes how to verify the BC on the BSC side.
Prerequisites
All the BSC sub-racks run normally.
The BSC is configured with the BC.
Procedure
Procedure 8-2
Verifying the BC
Run the LST BC command on the MML Command Client to view the configuration of the
BC configured on the BSC.
Run the DSP BC command on the MML Command Client to view the status of the BC
to be verified.
If BC Administration State is Unblocked and BC Service State is Useable, you can

infer that the status of the BC is normal.
If BC Administration State is Blocked, run the UBL BC command to unblock the BC.
68P02909W06-A
8-9
Aug 2008
Verifying the NSVC
Verifying the NSVC

This section describes how to verify the NSVC on the BSC side.
Prerequisites
The BC is available.
The BSC is configured with the NSVC.
Procedure
Procedure 8-3
Verifying the NSVC
Run the LST NSVC command on the MML Command Client to view the configuration of
the NSVC configured on the BSC.
Run the DSP NSVC command on the MML Command Client to view the status of the NSVC
to be verified.If NSVC Administration State is Unblocked and NSVC Service State is
Activation unblocked, you can infer that the status of the NSVC is normal.
Postrequisites
If NSVC Administration State is Unblocked and NSVC Service State is Activation

blocked, you can infer that the FR link that bears the NSVC is established. The NSVC,
however, is blocked on the SGSN. Unblock the NSVC on the SGSN.
If NSVC Administration State is Blocked and NSVC Service State is Activation blocked,
you can infer that the FR link that bears the NSVC is established; however, the NSVC is
blocked on the BSC, or is blocked on both the BSC and the SGSN.
a.
Run the UBL NSVC command on the MML Command Client to unblock the NSVC on
the BSC.
b.
Run the DSP NSVC command on the MML Command Client to view the status of the
NSVC. If NSVC Service State is still Activation blocked, you can infer that the NSVC
is blocked on the SGSN. Unblock the NSVC on the SGSN.
If the NSVC is in the Deactivation blocked state, the possible causes are as follows:
The link on the lower layer fails. Rectify the faults by referring to Verifying the BC
on page 8-9.
The NSVC identifier set on the BSC is inconsistent with the NSVC identifier set on
the SGSN.
The SGSN is not configured with the NSVC of the same identifier on the BC.
8-10
68P02909W06-A
Aug 2008
Verifying the SIGBVC

This section describes how to verify the SIGBVC on the BSC side.
Prerequisites
The NSVC is available.
The BSC is configured with the NSE.
Context
The status of the SIGBVC is the same as the status of the NSE.
Procedure
Procedure 8-4
Run the LST NSE command on the MML Command Client to view the configuration of
the NSE configured on the BSC.
Run the DSP SIGBVC command on the MML Command Client to view the status of the
SIGBVC of the NSE to be verified.If SIG BVC State is Normal, you can infer that the
SIGBVC is available.
Postrequisites
If the status of the NSVC mapping to the NSE is normal and the SIG BVC State is Fault, you
can infer that the SGSN is not configured with the NSE of the same identifier.
Verifying the PTPBVC

This section describes how to verify the PTPBVC on the BSC side.
Prerequisites
The SIGBVC is available.
The BSC is configured with the PTPBVC.
The Um interface status of the cell is normal.
68P02909W06-A
8-11
Aug 2008
Procedure
Procedure 8-5
Run the LST PTPBVC command on the MML Command Client to view the configuration of
the PTPBVC configured on the BSC.
Run the DSP PTPBVC command on the MML Command Client to view the status of the
PTPBVC of the NSE to be verified. If PTPBVC Administration State is Unblocked and
PTPBVC Service State is Normal, you can infer that the status of the PTPBVC is normal.
Postrequisites
If the status of the SIGBVC is normal and PTPBVC Service State is Fault, take the following
measures:
1.
If the administration status of the PTPBVC is Blocked, run the UBL PTPBVC command
on the MML Command Client to unblock the PTPBVC. If the status of the PTPBVC is
still abnormal, proceed to the next step.
2.
Run the RST PTPBVC command on the MML Command Client to reset the PTPBVC. If the
status of the PTPBVC is still abnormal, proceed to the next step.
3.
Run the RST PSCELL command on the MML Command Client to reset the cell mapping to
the PTPBVC. If the status of the PTPBVC is still abnormal, proceed to the next step.
4.
Run the RST SIGBVC command on the MML Command Client to reset the SIGBVC
mapping to the PTPBVC.
8-12
68P02909W06-A
Aug 2008
Verifying the Links on the Gb Interface (Gb over IP)
Verifying the Links on the Gb Interface (Gb over IP)
This section describes how to verify the links on the Gb interface when the Gb interface adopts
the IP transmission mode. Verifying the links on the Gb interface involves verifying the NSVL,
verifying the IP routes on the Gb interface, verifying the SIGBVC, and verifying the PTPBVC.
Verifying the NSVL

This section describes how to verify the NSVL on the BSC side.
Prerequisites
The GFGUG is configured correctly.
The BSC is configured with the local NSVL and the remote NSVL.
Procedure
Procedure 8-6
Verifying the NSVL
Run the LST NSVLLOCAL command or the LST NSVLREMOTE command on the MML
Command Client to view the configuration of the NSVL configured on the BSC.
Run the DSP NSVL command on the MML Command

Client to view the status of the NSVL to be verified.
If NSVL State is Useable, you can infer that the status of the NSVL is normal.
Verifying the IP Routes on the Gb Interface

This section describes how to verify the IP routes on the Gb interface.
68P02909W06-A
8-13
Aug 2008
Prerequisites
The BSC is connected to the SGSN.
The GFGUG is configured correctly.
The local NSVL and the remote NSVL are available.
Procedure
Procedure 8-7
Verifying the IP Routes on the Gb Interface
Run the LST NSVLLOCAL command or the LST NSVLREMOTE command on the MML
Command Client to view the configuration of the NSVL configured on the BSC.
Run the DSP GBIPROUTE command on the MML Command Client to view the status of the
IP route to be verified on the Gb interface. If IP Path State is Normal, you can infer that the
IP route on the Gb interface is available.

This section describes how to verify the SIGBVC on the BSC side.
Prerequisites
The NSVC is available.
The BSC is configured with the NSE.
Context
The status of the SIGBVC is the same as the status of the NSE.
Procedure
Procedure 8-8
Run the LST NSE command on the MML Command Client to view the configuration of
the NSE configured on the BSC.
Run the DSP SIGBVC command on the MML Command Client to view the status of the
SIGBVC of the NSE to be verified.If SIG BVC State is Normal, you can infer that the
SIGBVC is available.
8-14
68P02909W06-A
Aug 2008
Postrequisites
If the SIG BVC State is Fault, you can infer that the SGSN is not configured with the NSE of
the same identifier when the status of the NSVL and the IP path is normal.

This section describes how to verify the PTPBVC on the BSC side.
Prerequisites
The SIGBVC is available.
The BSC is configured with the PTPBVC.
The Um interface status of the cell is normal.
Procedure
Procedure 8-9
Run the LST PTPBVC command on the MML Command Client to view the configuration of
the PTPBVC configured on the BSC.
Run the DSP PTPBVC command on the MML Command Client

to view the status of the PTPBVC of the NSE to be verified.
If PTPBVC Administration State is Unblocked and PTPBVC Service State is Normal, you
can infer that the status of the PTPBVC is normal.
Postrequisites
If the status of the SIGBVC is normal and PTPBVC Service State is Fault, take the following
measures:
1.
If the administration status of the PTPBVC is Blocked, run the UBL PTPBVC command
on the MML Command Client to unblock the PTPBVC. If the status of the PTPBVC is
still abnormal, proceed to the next step.
2.
Run the RST PTPBVC command on the MML Command Client to reset the PTPBVC. If the
status of the PTPBVC is still abnormal, proceed to the next step.
3.
Run the RST PSCELL command on the MML Command Client to reset the cell mapping to
the PTPBVC. If the status of the PTPBVC is still abnormal, proceed to the next step.
4.
Run the RST SIGBVC command on the MML Command Client to reset the SIGBVC
mapping to the PTPBVC.
68P02909W06-A
Aug 2008
8-15
8-16
68P02909W06-A
Aug 2008
Chapter
9
68P02909W06-A
Aug 2008
9-1
This section describes how to load the BTS software and data when commissioning the BSC.
Prerequisites
The communication between the BSC and the BTS is normal.
9-2
68P02909W06-A
Aug 2008
Downloading BTS Software
Downloading BTS Software
This section describes how to download the BTS software to the GOMU server from the LMT.
Prerequisites
The BST software exists on the LMT.
The FTP server runs normally.
Procedure
Through GUI
a.
Choose BTS Maintenance>Download BTS Software. A dialog box is displayed,

68P02909W06-A
9-3
Aug 2008
Procedure
Figure 9-1
b.
Downloading the BTS software
Click Add File. A dialog box is displayed, as shown in Figure 9-2.
NOTE
By default, the files to be downloaded are stored in the Common folder or
its lower-level folder in the LMT installation path.
9-4
68P02909W06-A
Aug 2008
Procedure
Figure 9-2
Selecting a file
c.
Double-click the file to be downloaded. The file is displayed in the Selected File
List box.
d.
Click OK. The selected file is displayed.
e.
Click Download. The BTS software is downloaded to the GOMU server.
f.
Click the Files on OMU tab page. Click Query to query the files downloaded on
the OMU.
g.
Click Cancel to close the BTS software downloading.
Through MML
Run the DLD BTSSW command on the MML Command Client to download the BTS software.
68P02909W06-A
9-5
Aug 2008
Configuring BTS Software
This section describes how to set the file type, file name, version number, and the BTS type for
the downloaded software on the server before BTS software loading.
Prerequisites
The BTS software is already downloaded on the server.
Context
Only one user can perform this operation at a time. If another user is configuring BTS
software when you perform this operation, an information box is displayed, indicating that
you cannot perform this operation.
Site Type, File Type, Version, and File Name must be correct. Otherwise, the BTS
software loading fails.
Procedure
Procedure 9-1
1
Choose BTS Maintenance>Configure BTS Software. A dialog box is displayed, as shown

in Figure 9-3.
Continued
9-6
68P02909W06-A
Aug 2008
Procedure
Procedure 9-1
Figure 9-3
Configuring BTS Software (Continued)
Configure BTS Software dialog box (1)
Set Site Type, File Type, Version, File Name, and Description.
NOTE
The Version consists of 8 hexadecimal characters, such as 09_01_1A_01.
Continued
68P02909W06-A
9-7
Aug 2008
Postrequisites
Procedure 9-1
3
Click Add. The configuration information of the software is displayed in the Software
List area, as shown in Figure 9-4.
Figure 9-4
Configuring BTS Software (Continued)
Configure BTS Software dialog box (2)
Click Commit. Configuring the BTS software is complete. The Information dialog box
displayed, indicating that the BTS software is successfully configured.
Postrequisites
If you select the configured file in the Software List shown in Figure 9-4, click Delete, and
then click Commit, the file is deleted. If you Modify, and then click Commit, the configuration
file is modified.
9-8
68P02909W06-A
Aug 2008
Loading BTS Software
Loading BTS Software
This section describes how to load the BTS software that are configured with file information to
the BTS main control board on the LMT. This section also describes how to verify whether the
file configuration is consistent with the version of BTS board software.
Prerequisites
The BTS software version is configured.
Context
The files of multiple BTSs can be loaded in one operation, thus improving the upgrade efficiency.
Load the software of the main control board first and then load the software of other boards.
Procedure
Through GUI
a.
Choose BTS Maintenance>Load BTS Software. A dialog box is displayed, as

68P02909W06-A
9-9
Aug 2008
Procedure
Figure 9-5
b.
Set Site Type and Software Type, select the software to be loaded, and click Next. A
dialog box is displayed, as shown in Figure 9-6.
Figure 9-6
c.
Load BTS Software dialog box
Loading the BTS software
Select the files to be loaded in the upper area and move them to the lower area. Click
Next. A prompt is displayed. Click Yes. The loading starts.
9-10
68P02909W06-A
Aug 2008
d.
Postrequisites
After the file is loaded, a dialog box is displayed, as shown in Figure 9-7.
Figure 9-7
e.
Loading result
Click Finish.
Through MML
Run the LOD BTSSW command on the MML Command Client to download the BTS software.
Postrequisites
During the loading, you can click View Load Progress to view the information such as loading
progress and status. Such information is displayed in the Local Manager window. When
Progress is 100%, the loading is complete.
68P02909W06-A
9-11
Aug 2008
Querying BTS Attributes
Querying BTS Attributes
This section describes how to verify BTS attributes, including attributes of site, cell, TRX, or
channel. By querying BTS attributes, you can learn the operating status and attributes of
a BTS in real time.
Prerequisites
Procedure
Through GUI
a.
Choose BTS Maintenance>Query BTS Attributes.
b.
Set Object Type to Site and set parameters in Select Objects and Select Attributes
areas. Click Query. A dialog box is displayed, as shown in Figure 9-8.
9-12
68P02909W06-A
Aug 2008
Procedure
Figure 9-8
Querying the BTS attributes
NOTE
The operation for querying the BTS attributes is the same as that for
querying the cell, TRX, or channel attributes. This takes querying the site
attributes as an example.
Through MML
You can run the DSP BTSATTR command on the MML Command Client to query BTS
attributes.
68P02909W06-A
9-13
Aug 2008
Activating BTS Software
Activating BTS Software
This section describes how to activate the software loaded to the BTS boards.
Prerequisites
The version of BTS software to be activated is different from the version of current BTS
software.
The BTS software has been loaded to the flash memory of BTS boards.
The BTS software must be activated before running.
Context
The software of multiple BTSs can be activated in one operation. When activating the
BTS software, activate the software of the main control board first and then activate the
software of other boards.
The LMT cannot activate an individual main control board. If the board to be activated
is a main control board, all main control boards in the same site will be activated. If the
board to be activated is not a main control board, a specific board can be activated based
on the actual condition.
Procedure
Through GUI
a.
Choose BTS Maintenance>Activate BTS Software. A dialog box is displayed,

9-14
68P02909W06-A
Aug 2008
Procedure
Figure 9-9
b.
Activate BTS Software dialog box (1)
Set Site Type and Software Type, and select the software to be activated. Click
Next. A dialog box is displayed, as shown in Figure 9-10.
Figure 9-10
68P02909W06-A
9-15
Aug 2008
Procedure
c.
Select sites and move them from the upper area to the lower area. Click Next. If the
Software Type is the main control board, a dialog box is displayed, as shown in
Figure 9-11.
Figure 9-11
If the Software Type is not the main control board, a dialog box is displayed, as
Figure 9-12
9-16
68P02909W06-A
Aug 2008
d.
e.
Procedure
The activation begins.
The LMT cannot activate the software of an individual main control board. Click
Next to activate the software of all main control boards.
Select a non main control board whose software can be individually activated,
and then click Next.
Click Yes. The activation begins, as shown in Figure 9-13.
Figure 9-13
f.
Activating BTS software dialog box (5)
When the Progress is 100%, click Finish.
NOTE
The activation progress of the main control board and that of the PTU
are not displayed. During the activation, you can click View Activation
Progress to view the information such as the activation progress and
status. Such information is displayed in the Local Manager window. When
the Progress is 100%, the activation is complete.
Through MML
Run the ACT BTSSW command on the MML Command Client to activate the BTS software.
68P02909W06-A
9-17
Aug 2008
Querying BTS Running Status
Querying BTS Running Status
This section describes how to query the running status of the BTSs and cells under the same
BSC to determine whether the BTSs operate normally. You can query the operating status of
multiple BTSs simultaneously.
Prerequisites
Context
You can query the running status parameters of the BTSs and cells through the LMT. Table 9-1
lists the running status parameters of the BTSs.
Table 9-1
Description of BTS running status parameters
Parameter
Description
Normal OML Link
Indicates whether the OML link between the current site and
BSC is normal.
BTS Initialized
Indicates whether the current site is initialized.
Cell Initialized
Indicates whether the cell under the current site is initialized.
Block Automatically
Indicates whether a fault occurs to the current site that is

blocked automatically.
Channel Fault
Indicates whether a channel fault occurs to the current site.
Main BCCH Mutual Aid
Indicates whether the mutual aid takes place between the

primary BCCH and other TRXs when the TRX where the BCCH
resides is exceptional.
Baseband FH Mutual Aid
Indicates that a fault occurs in the TRX that joins in baseband

FH or the BCCH mutual aid occurs in the cell.
Local Management Rights
Indicates whether the local site maintenance has got the local
management authority.
Board Fault
Indicates whether the board at the current site is running

normally.
Alarm Generated
Indicates whether alarms occur to the current site.
9-18
68P02909W06-A
Aug 2008
Procedure
Table 9-2 lists the running status parameters of the cells.
Table 9-2
Description of cell running status parameters
Parameter
Description
Cell Initialized
Indicates whether the current cell is initialized.
Block Automatically
Indicates whether the current cell is blocked automatically due

to the TRX fault.
Channel Fault
Whether channel link is faulty.
Main BCCH Mutual Aid
Indicates whether the mutual aid takes place between the

primary BCCH and other TRXs when the TRX where the BCCH
resides is exceptional.
BT Hop Mutual Aid
Indicates that a fault occurs to the TRX that joins in baseband

FH or the BCCH mutual aid occurs in the cell.
Block Manually
Indicates whether the management status of the current site is

set to Block Manually.
Procedure
Through GUI
a.
Choose BTS Maintenance>Query BTS Running Status. A dialog box is displayed,

Figure 9-14
Query BTS running status dialog box
68P02909W06-A
9-19
Aug 2008
Procedure
NOTE
The operation for querying the site running status is the same as that for
querying the cell running status. This takes querying site running status
parameters as an example.
b.
Set the Object Type to Site and set the Site Type. The sites that meet the set
conditions are displayed in Candidate sites.
c.
Select the sites to be queried and move them from Candidate sites to Selected
sites. Select parameters in the Query Status box. Click OK. A dialog box is
Figure 9-15
d.
Querying BTS running status
Click Save.
Through MML
You can run the following commands on the MML Command Client to query the running
status of the BTSs and cells under the same BSC.
Run the DSP BTSSTAT command to query the operating status of the BTS.
Run the DSP CELLSTAT command to query the operating status of a specified cell.
9-20
68P02909W06-A
Aug 2008
Querying BTS Board Information
Querying BTS Board Information
This section describes how to query the information of the BTS board on the Local Manager.
Prerequisites
Context
The BTP, TRX, MSI, and COMB support this operation.
Procedure
Through GUI
a.
On the LMT, choose BTS Maintenance>Maintain Board>Query Board

Information. A dialog box is displayed, as shown in Figure 9-16.
68P02909W06-A
9-21
Aug 2008
Procedure
Figure 9-16
b.
Querying board information
Set parameters in the Location area, and then click Query.
Through MML
Run the DSP BTSBRD command to query the BTS board information.
Run the DSP BTSBRDEX command to query the extended information of the BTS board.
9-22
68P02909W06-A
Aug 2008
Chapter
10
Processing Alarms Generated in the BSC
Commissioning
68P02909W06-A
Aug 2008
10-1
Processing Alarms Generated in the BSC Commissioning

Chapter 10:
Alarms may be generated in commissioning the BSC; thus affecting the subsequent verification
of services. This section describes how to process alarms generated in the BSC commissioning.
Prerequisites
Procedure
Procedure 10-1
1
On the Local Manager, choose Alarm Maintenance>Browse Alarm. The Browse Alarm
window is displayed, as shown in Figure 10-1.
Continued
10-2
68P02909W06-A
Aug 2008
Procedure
Procedure 10-1
Figure 10-1
Processing Alarms Generated in the BSC Commissioning (Continued)
Browse Alarm window
Continued
68P02909W06-A
10-3
Aug 2008
Procedure
Chapter 10: Processing Alarms Generated in the BSC Commissioning
Procedure 10-1
2
Processing Alarms Generated in the BSC Commissioning (Continued)
Right-click the alarm to be queried. Select Alarm Detail from the shortcut menu to view
the detailed information on the selected alarm, such as Alarm Serial No., Alarm name,
Alarm raised time, and Cleared time. You can view the detailed information on an alarm
by double-clicking the alarm. Figure 10-2 shows the detailed information on an alarm.
Figure 10-2
Alarm Detail Information dialog box
Click Alarm Detail or press F1. The BSS Help System window is displayed.
Process this alarm following the advice provided by the BSS Help System.
Repeat step 1 through step 4 to process other alarms.
10-4
68P02909W06-A
Aug 2008
Chapter
11
Verifying the BSC Services
68P02909W06-A
Aug 2008
11-1
This section describes how to verify the basic services and part of the feature services provided
by the BSC. The basic services consist of the speech service, data service, OM management; the
feature services consist of the inter-RAT handover, location service, and AMR service.
Prerequisites
The local office commissioning is complete.
The commissioning over the Abis, Ater, A, and Gb interfaces is successful.
The MS used for testing is functional and is registered with the HLR.
Procedure
Procedure 11-1
Before verifying the services, start necessary interface message tracing on the LMT.
Table 11-1 lists the procedures for verifying the basic services by testing the MS in the
BTS cells.
NOTE
The GDPUP/GDPUX works in resource pool mode. Through blocking, you can
switch the services from one board to any other GDPUP/GDPUX.
3
Table 11-2 lists the procedures for verifying the feature services by testing the MS in the
BTS cells.
11-2
68P02909W06-A
Aug 2008
Procedure
Table 11-1
Procedures for verifying the basic services
Basic Services
Speech service
Data service
OM management
Table 11-2
Procedures for Conducting

the Dialing Test
Expected Result
Make 50 calls from an MS to

a fixed-line phone. Make 50
calls from a fixed-line phone
to an MS.
The connection success rate is

greater than 90%. The voice is
clear and there is no loud noise.
Make 50 calls from an MS to

another MS.

Send a fax from an MS to

an electrograph. Send a fax
from an electrograph to an
MS.
Faxes are sent and received

normally.
Use an MS to test the GPRS

or the EDGE service.
The test data rate is similar to the

data rate tested in a library.
During the service, perform

the switchover test on the
GXPUM, GXPUC, GSCU,
GTNU, GGCU and interface
boards respectively for five
times.
The switchover success rate is

greater than 90%. The services
are not interrupted during the
switchover.
Procedures for verifying the feature services
Feature Services
Procedures for Conducting the

Dialing Test
Expected Result
Inter-RAT handover
Hand over a dual-mode MS from

the GSM to the UMTS for 50 times.
Hand over a dual-mode MS from
the UMTS to the GSM for 50 times.

Location service
Use an MS to originate a call and

hold on the call. Then, locate the
MS.
The precision of the location

conforms to the related standard.
AMR service
Make 50 calls from an MS to a

fixed-line phone. The selected
voice version is AMR.

68P02909W06-A
Aug 2008
11-3
Procedure
11-4
68P02909W06-A
Aug 2008
Chapter
12
Connecting the BSC to the OMC-S/T
68P02909W06-A
Aug 2008
12-1
This section describes how to connect the BSC to the OMC-S/T for centralized management.
Prerequisites
The commissioning of the BSC local office is successful.
The commissioning of the OM network is successful and the OMC-S/T is functional.
The OMC-S/T version matches the BSC version.
Context
If the BSC and the OMC-S/T are on the same network segment, configure the route.
If the BSC and the OMC-S/T are not on the same network segment, configure the route
before connecting the BSC to the OMC-S/T.
Procedure
Procedure 12-1
1
Connect the BSC to the OM network.

1.
Connect one end of the Ethernet cable to the GOMU.
2.
Connect the other end of the Ethernet cable to the network equipment, such as a hub
or a router, to the OM network.
Configure the route from the BSC to the OMC-S/T.
CAUTION
In this operation, do not restart the GOMU. If the GOMU must be restarted,
you need to the local process of the GOMU and the core process of the GOMU
simultaneously.
The IP address of the GOMU and that of the router are on the same network
segment.
Continued
12-2
68P02909W06-A
Aug 2008
Procedure
Procedure 12-1
Connecting the BSC to the OMC-S/T (Continued)
Take the following scenario as an example. Assume that the IP address of the
OMC-S/T server is 10.11.100.23 and the subnet mask is 255.255.255.0. The GOMU
is connected to the OMC-S/T router whose the IP address is 172.121.139.10.
Log in to the GOMU as user root. Then, perform the following steps:
1.
Open the /etc/sysconfig/network/routes file to view the routing information

configured on the GOMU.
If the information about the routing from the GOMU to the OMC-S/T is configured,
perform step 2.2.
If no information about the routing from the GOMU to the OMC-S/T is available,
add the routing information 10.11.100.23 172.121.139.10 255.255.255.0
into the file. The routing information consists of destination network (or
destination host) gateway network mask.
2.
Run the route command to view all the valid routing information on the GOMU.
If the route information from the GOMU to the OMC-S/T is validated, this task
is complete.
Otherwise, run the route add 10.11.100.23 172.121.139.10 command.
3.
Verify the route configuration.

Check whether the routing information is valid.Run the route command to view
the valid tracing information on the GOMU. Normally, you can view the routing
information from the GOMU to the OMC-S/T. If the information cannot be viewed,
perform step 2.1 again to check whether the configuration is correct.
Check the network between the GOMU and the OMC-S/T.
i.
Check whether the physical connection between the GOMU and the router
and that between the router and the OMC-S/T are proper.
ii.
Run the ping 172.121.139.10 command to check the network from the
GOMU to the router. If the GOMU receives the response packet from the
router, you can infer that the network communication between the GOMU
and the router is normal.
iii.
Run the ping 172.121.139.10 command to check the network from the
GOMU to the OMC-S/T. If GOMU receives the response packet from the
OMC-S/T, you can infer that the routing information from the GOMU to the
OMC-S/T is configured correctly and the network communication is normal.
Connect the BSC to the OMC-S/T. Create the BSC on the OMC-S/T. For details, refer to the
OMC-S/T documentation.
68P02909W06-A
Aug 2008
12-3
Procedure
12-4
68P02909W06-A
Aug 2008
Chapter
13
Checklist for BSC Commissioning
68P02909W06-A
Aug 2008
13-1
This section provides the checklist for checking the results of commissioning the BSC.
Installing the GOMU and the LMT Software

Table 13-1
Record of installing the GOMU and the LMT software
Operation
Completion
Installing the OMU

software
Y;
Installing the LMT

software
Y;
Logging in to the
GOMU through the
LMT
Y;
Record Data (Finish Time, Operator, Commissioning

Data)/Unfulfilled Description

Table 13-2
Record of loading the BSC host software
Operation
Completion
Downloading and
decompressing the
version software
Y;
Loading the BSC

version software
Y;
Activating the BSC

version software
Y;
Querying board
version information
Y;
Querying BSC board

information
Y;

13-2
68P02909W06-A
Aug 2008
Commissioning the BSC Local Office
Commissioning the BSC Local Office

Table 13-3
Record of commissioning the BSC local office
Operation
GOMU
Y;
GGCU
Y;
GSCU
Y;
GTNU
Y;
GXPUM
Y;
GXPUT
Y;
GXPUC
Y;
GEIUA/GEIUB/GEIUT
Y;
GOIUA/GOIUB/GOIUT
Y;
GFGUA/GFGUG
Y;
GFGUG
Y;
GOGUA
Y;
GDPUP
Y;
GDPUX
Y;
Querying the BSC license
Y;
Processing alarms generated

in the BSC commissioning
Y;
Switching
over the
active and
standby
boards
Record Data (Finish Time, Operator,

Commissioning Data)/Unfulfilled Description
Completion

Table 13-4 Record of verifying the Ater interface when the GTCS is configured on
the BSC side
Operation
Completion
E1/T1 links
Y;
STM-1 links
Y;
Verifying the user plane on the

Ater interface
Y;
Processing alarms generated in

verifying the Ater interface
Y;
Verifying the
physical links
on the Ater
interface

Commissioning Data)/Unfulfilled
Description
68P02909W06-A
13-3
Aug 2008
Table 13-5 Record of verifying the Ater interface when the GTCS is configured on
the MSC side
Operation
Completion
E1/T1 links
Y;
STM-1 links
Y;
Verifying the management plane

on the Ater interface
Y;

Ater interface
Y;

verifying the Ater interface
Y;
Verifying the
physical links
on the Ater
interface

Description

Table 13-6
Record of verifying the A Interface (A over TDM)

Operation
Completion
E1/T1 links
Y;
STM-1 links
Y;
Verifying the control plane on the

A interface
Y;
Verifying the user plane on the A

interface
Y;

verifying the A interface
Y;
Verifying the
physical links on
the A interface
Table 13-7

Description
Record of verifying the A Interface (A over IP)
Operation
Completion
Verifying the
physical links on
the A interface
Y;
Verifying the control

plane on the A
interface
Y;
Processing alarms
generated in
verifying the A
interface
Y;

13-4
68P02909W06-A
Aug 2008

Table 13-8
Record of verifying the Abis Interface (Abis over TDM)

Operation
Completion
E1/T1 links
Y;
STM-1 links
Y;
Verifying the management plane

on the Abis Interface
Y;
Verifying the control plane on the

Abis Interface
Y;

Abis Interface
Y;

verifying the Abis Interface
Y;
Verify the
physical links on
the Abis Interface

Description
Loading the BTS Software

Table 13-9
Record of loading the BTS software
Operation
Completion
Downloading the
BTS software to the
GOMU
Y;
Configuring the
add-ins of BTS
software
Y;
Loading the BTS

software from the
LMT
Y;
Querying BTS
attributes
Y;
Activating the BTS

software
Y;
Query BTS running

status
Y;
Querying the BTS

board information
Y;

68P02909W06-A
13-5
Aug 2008

Table 13-10
Record of verifying the BSC services

Item
Completion
Calls between
an MS and
a fixed-line
telephone
Y;
Calls between
MSs
Y;
Data service
Exchange of
faxes between
an MS and an
electrograph
Y;
OM management
Board
switchover
during services
Y;
Commissioning
of feature
services
Inter-RAT
handover
Y;
Location service
Y;
AMR service
Y;
Speech service

Description
13-6
68P02909W06-A
Aug 2008
Chapter
14
Troubleshooting: Common Problems During
the BSC Commissioning
68P02909W06-A
Aug 2008
14-1
BSC Commissioning Troubleshooting
Chapter 14: Troubleshooting: Common Problems During the BSC Commissioning
BSC Commissioning Troubleshooting
This section describes the common problems that occur in commissioning the BSC and the
solutions.
14-2
68P02909W06-A
Aug 2008
Failure in Connecting the LMT to the GOMU
Failure in Connecting the LMT to the GOMU
When the GOMU runs normally, logging in to the GOMU through the LMT may fail. This section
describes how to troubleshoot the failure.
Fault Description
The GOMU runs normally. After you enter Name and Password and click OK, you fail to
log in to the GOMU.
Troubleshooting
Procedure 14-1
Troubleshooting
Check whether the Name and Password are correct.
If the name and password are incorrect, enter the correct name and
password.
If the information is incorrect, go to step 2.
Check whether the network between the LMT PC and the GOMU is securely
connected. If the Ethernet cables are loosely connected, replace them with
new ones.
68P02909W06-A
14-3
Aug 2008
Faults on the Abis Interface Links
Faults on the Abis Interface Links
This section describes how to rectify the faults on the Abis Interface links.
Fault Description
On the LMT, the status of E1 ports of the BTS are normal, and no E1/T1 link alarm is generated.
However, the OMLs or RSLs are unavailable.
Troubleshooting
If the OMLs fail, do as follows:

a.
Find a BTS (assume BTS 1) that is running normally and is of the same type as the
BTS (assume BTS 2) whose OMLs are faulty. Connect BTS 2 to the port on the GEIUB
of BTS 1 and then reset BTS 2.
b.
If the OMLs recover after the BTS is reset, you can infer that the configuration data
of the OMLs is incorrect. Check the configuration data for correctness. If the fault
persists, you can infer that BTS 2 is faulty. Contact the BTS maintenance personnel.
NOTE
Generally, the configuration data of the OMLs refers to the port number,
timeslot number, and sub-timeslot number.
If the OMLs are normal but the RSLs fail, do as follows:

a.
View the running status of the BTS through the LMT. For details, refer to Querying
BTS Running Status.
If the initial status of the BTS is No or the initial status of the cell is No, infer
that the BTS or the cell is not initialized. Find out the reason.
If the initial status of the BTS and the initial status of the cell are Yes, check
the configuration data of the RSLs for correctness.
14-4
68P02909W06-A
Aug 2008
Troubleshooting
NOTE
Generally, the configuration data of the RSLs refers to the

port number, timeslot number, in-port number, and in-timeslot
number.
The configuration of the RSLs is delivered to the BTS through a

BTS initialization message. If the RSLs fail because the message
is incorrectly delivered, you can infer that the fault is caused
on the BSC side.
If the RSLs fail because the TRXs are not installed in the BTS,
the TRXs are in poor contact with the backplane of the BTS, or
the TRXs incur major alarms, infer that the fault is caused on
the BTS side.
If the RSLs fail when the configuration data is correct, infer that the fault is
caused on the BTS side. Contact the BTS maintenance personnel.
68P02909W06-A
14-5
Aug 2008
Failure in Starting the GOMU Board
Failure in Starting the GOMU Board
This section describes how to handle the failure in starting the GOMU.
Fault Description
The fault symptoms are as follows:
The description of LEDs on the panel is as follows:

After the GOMU is powered on, the RUN LED on the board panel is ON, and the
two LEDs that indicate the status of the read and write function of hard disks flash
simultaneously. Then, the RUN LED is still ON, but the two LEDs that indicate the
status of the read and write function of hard disks are OFF.
The ALM LED is ON or flashing.
The OFFLINE LED is flashing or ON.
The main control board generates an alarm at the frequency of 1 Hz. Three successive
sounds are produced and another three successive sounds are produced after two seconds
(an alarm related to the memory).
The possible causes are as follows:
The power cable or the network cable is loosely connected.
The memory is improperly connected or faulty.
The hard disks are improperly connected or faulty.
When shutting down the GOMU, the operator directly switches off the power instead of
powering off the GOMU normally.
The default boot sequence is changed, the device that must be started first is not started as
required. You can press F11 to view the default boot sequence: 1. Network (network port
started); 2. SCSI (hard disk started); 3. USB (USB started).
14-6
68P02909W06-A
Aug 2008
Troubleshooting Method
Troubleshooting Method
You can take the following measures to rectify the fault:
1
Check and ensure that the power cables and network cables are securely
connected.
Based on the analysis of the 1 Hz alarm, you may infer that the memory is
faulty. Therefore, the GOMU cannot be started. Remove and install the
memory. If the fault persists, proceed to the next step.
Discharge the BIOS battery, and then restart the GOMU. If the GOMU is
started and runs normally, you can infer that the fault is rectified. If the fault
persists, proceed to the next step.
If the EI tool is used to install the operationg system, check whether the
network port is first started as the default setting. If the EI tool is not used
to install the operating system, power off the GOMU, and then remove and
install the hard disk. If the fault persists, proceed to the next step.
Check whether the boot sequence of the GOMU is changed.

Restart the GOMU, and press F11 as prompted. Ensure that the GOMU is
started in the sequence of network port, hard disk, and USB.
68P02909W06-A
14-7
Aug 2008
Inconsistent Data Configurations on the Abis/Ater/A/Gb Interfaces

Troubleshooting: Common Problems During the BSC Commissioning
Chapter 14:
Inconsistent Data Configurations on the

Abis/Ater/A/Gb Interfaces
This section describes how to handle the problem of inconsistent data configurations on the Abis
Interface, the Ater interface, the A Interface, and the Gb interface.
Fault Description
After verifying the Abis, Ater, A, and Gb interfaces, the actual results do not reach the
expectation. A comparison between the data configured on the interfaces and the negotiated
data shows that the cause is data inconsistency.
Troubleshooting
Modify the inconsistent data configurations by referring to the BSC Initial Configuration Guide.
14-8
68P02909W06-A
Aug 2008
Chapter
15
Appendix: Changes in BSC Commissioning
Guide
68P02909W06-A
Aug 2008
15-1
Appendix: Changes in BSC Commissioning Guide
Chapter 15: Appendix: Changes in BSC Commissioning Guide
Appendix: Changes in BSC Commissioning Guide
This section describes the changes in the BSC Commissioning Guide.
01 (2008-07-21)
This is the initial commercial release.
15-2
68P02909W06-A
Aug 2008

BSC Commissioning Guide: © 2008 Motorola, Inc. All Rights Reserved

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC Commissioning Guide: © 2008 Motorola, Inc. All Rights Reserved

Uploaded by

Copyright:

Available Formats

BSC Commissioning Guide

2008 Motorola, Inc. All Rights Reserved.

PRELIMINARY - UNDER DEVELOPMENT