BSC6900 GSM Commissioning Guide (V900R011C00 - 01)

BSC6900 GSM V900R011C00
Commissioning Guide
Issue Date
01 2009-07-30
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
BSC6900 GSM Commissioning Guide
Contents
Contents
About This Document.....................................................................................................................1 1 Changes in BSC6900 GSM Commissioning Guide.............................................................1-1 2 Prerequisites for Commissioning...........................................................................................2-1 3 Commissioning Process............................................................................................................3-1 4 Verifying the Equipment..........................................................................................................4-1
4.1 Checking the Operating Status of the Hardware.............................................................................................4-2 4.2 Verifying the OMU.........................................................................................................................................4-2 4.3 Logging In to the BSC6900 Through the LMT..............................................................................................4-4
5 Updating the OMU Database..................................................................................................5-1 6 Activating and Verifying the License....................................................................................6-1 7 Loading BSC6900 Board Software and Data Files...............................................................7-1
7.1 Generating the Data File for the Loading........................................................................................................7-3 7.2 Setting the Loading Mode...............................................................................................................................7-3 7.3 Resetting the BSC6900 Boards.......................................................................................................................7-4 7.4 Checking the Consistency of the Data and the Version..................................................................................7-5
8 Verifying GSM Interfaces........................................................................................................8-1

8.1 Verifying the Abis Interface............................................................................................................................8-2 8.2 Verifying the A Interface................................................................................................................................8-3 8.3 Verifying the Gb Interface..............................................................................................................................8-5 8.4 Verifying the Ater Interface............................................................................................................................8-7 8.5 Verifying the Pb Interface...............................................................................................................................8-7
9 Handling the Alarms Generated During the Commissioning..........................................9-1 10 Verifying the GSM Services................................................................................................10-1 11 Connecting the BSC6900 to the M2000...............................................................................11-1 12 Creating Scheduled Tasks....................................................................................................12-1 13 FAQ...........................................................................................................................................13-1
13.1 Checking the Transmission Link.................................................................................................................13-2 13.2 Unavailable E1/T1 Port...............................................................................................................................13-3 Issue 01 (2009-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
13.3 Unavailable FE/GE Port..............................................................................................................................13-4 13.4 IP Connection Setup Failure.......................................................................................................................13-4 13.5 Data Loading Failure on the Board.............................................................................................................13-5 13.6 Performing the Loopback Test on the E1/T1 Port......................................................................................13-7 13.7 Performing the Loopback Test on the Optical Port...................................................................................13-10
14 Appendix..................................................................................................................................14-1
14.1 Communication Ports Used by the BSC6900.............................................................................................14-2 14.2 BSC6900 Commissioning Checklist...........................................................................................................14-4
ii
Issue 01 (2009-07-30)
Figures
Figures
Figure 2-1 Typical commissioning network........................................................................................................2-2 Figure 4-1 BSC6900 log-in dialog box................................................................................................................4-5 Figure 5-1 Batch tab page....................................................................................................................................5-2 Figure 5-2 Setting the batch commands...............................................................................................................5-3
Issue 01 (2009-07-30)
iii
Tables
Tables
Table 2-1 Requirements for equipment status before commissioning.................................................................2-1 Table 2-2 Other commissioning scenarios...........................................................................................................2-2 Table 4-1 Checklist of the power supply to the cabinet components...................................................................4-2 Table 7-1 Name of the loading file.......................................................................................................................7-3 Table 7-2 Time for system resetting in different scenarios..................................................................................7-4 Table 10-1 Performing dialing tests on the basic services.................................................................................10-1 Table 10-2 Performing dialing tests on the feature services...............................................................................10-2 Table 11-1 Configuring the route from the BSC6900 to the M2000.................................................................11-2 Table 12-1 Log type and file name.....................................................................................................................12-1 Table 13-1 Methods for checking the status of transmission link in different transmission modes..................13-2 Table 13-2 Operation index................................................................................................................................13-5 Table 13-3 Procedure for performing the loopback test on the local E1/T1 port...............................................13-8 Table 13-4 Procedure for performing the loopback test on the local E1/T1 cable.............................................13-8 Table 13-5 Procedure for checking the peer equipment or the transport network.............................................13-9 Table 13-6 Procedure for performing the loopback test on the SDH port........................................................13-10 Table 13-7 Procedure for performing the loopback test on the local fiber.......................................................13-10 Table 13-8 Procedure for performing the loopback test on the peer optical port.............................................13-11 Table 14-1 Communication ports used by the services of the BSC6900...........................................................14-2
Issue 01 (2009-07-30)
About This Document
About This Document

Overview
This provides guidelines for commissioning the BSC6900. It includes the following contents: verifying the Operation and Maintenance Unit (OMU), activating and verifying the license, loading the BSC6900 board software and data files, verifying the interfaces and services, and connecting the BSC6900 to the M2000.
Product Version
The following table lists the product version related to this document. Product Name BSC6900 Product Version V900R011C00
Intended Audience
This document is intended for field engineers.
Organization
1 Changes in BSC6900 GSM Commissioning Guide This describes the changes made in the BSC6900 GSM Commissioning Guide. 2 Prerequisites for Commissioning To perform the BSC6900 commissioning, the status of the equipment and the network to be commissioned must meet the conditions described in this part, and the installation software, license, and MML command scripts required for commissioning must be ready. 3 Commissioning Process The BSC6900 commissioning involves verifying the equipment, updating the OMU database, activating and verifying the license, loading the BSC6900 board software and data files, verifying the interfaces, handling the alarms generated during commissioning, verifying the services, and connecting the BSC6900 to the M2000. 4 Verifying the Equipment The verifying of the equipment is the basis for commissioning the BSC6900. The verifying of the interfaces and services can be performed only after the equipment is verified. Equipment
Issue 01 (2009-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1
About This Document
verifying involves checking the hardware operating status, verifying the OMU and logging in to the BSC6900 through the LMT. 5 Updating the OMU Database This describes how to update the BSC6900 configuration data in the OMU database by running MML commands. 6 Activating and Verifying the License This describes how to activate the license and verify the license configuration information to enable the service checking. 7 Loading BSC6900 Board Software and Data Files This describes how to load the BSC6900 board software and data files to enable the normal operation of the BSC6900. 8 Verifying GSM Interfaces This describes how to verify the GSM interfaces on the BSC6900 side during the BSC6900 commissioning. The GSM interfaces are the Abis interface, A interface, Gb interface, Ater, and Pb interface. The Ater interface verification is mandatory only in BM/TC separated mode. The Pb interface verification is mandatory only if the BSC6900 is configured with an external PCU. 9 Handling the Alarms Generated During the Commissioning This describes how to handle the alarms generated during the commissioning, thus preventing the alarms from affecting the verification of services. 10 Verifying the GSM Services This describes how to verify that the GSM basic services and the feature services that are enabled are normal. The basic services consist of speech service and data service. The feature services consist of the inter-RAT handover, location service, and AMR service. 11 Connecting the BSC6900 to the M2000 This describes how to connect the BSC6900 to the M2000 for the centralized management. 12 Creating Scheduled Tasks This describes how to create the scheduled tasks for the automatical backup of the system data and logs after commissioning; thus, the data and logs can be used for the BSC6900 equipment fault recovery. 13 FAQ This describes how to handle the common problems during the commissioning. 14 Appendix This provides the communication ports and the commissioning checklist of the BSC6900.
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows.
2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-07-30)
About This Document
Symbol
Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3
Issue 01 (2009-07-30)
About This Document
Convention { x | y | ... }*
Description Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder .
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-07-30)
1 Changes in BSC6900 GSM Commissioning Guide
Changes in BSC6900 GSM Commissioning Guide

This describes the changes made in the BSC6900 GSM Commissioning Guide.
01 (2009-07-30)
This is the first commercial release.
Issue 01 (2009-07-30)
1-1
2 Prerequisites for Commissioning
2
Item
Prerequisites for Commissioning
To perform the BSC6900 commissioning, the status of the equipment and the network to be commissioned must meet the conditions described in this part, and the installation software, license, and MML command scripts required for commissioning must be ready.
Requirements for the Status of the Equipment

Before commissioning, ensure that the equipment meets the conditions listed in Table 2-1. Table 2-1 Requirements for equipment status before commissioning Requirement The hardware is installed and passes the hardware installation check and powering-on check. Configured before delivery. For details, see Checklist for the Factory Settings of the OMU Software. The LMT PC meets the configuration requirements. For details, see Configuration Requirements of the LMT PC.
BSC6900 hardware OMU LMT PC
Requirements for the Commissioning the Network

To ensure smooth verifying of the Abis, Ater, A, and Gb interfaces, the network equipment in the commissioning network must meet the following requirements:
l
At least one BTS is connected to the local BSC6900. The BTS should have passed the commissioning and can provide basic functions. At least one set of Core Network (CN) equipment is connected to the local BSC6900. The CN equipment should have passed the commissioning and can provide basic functions. Three single-mode MSs and one dual-mode MS for testing are functional and are registered in the HLR.
Figure 2-1 shows a typical commissioning network.
Issue 01 (2009-07-30)
2-1
Figure 2-1 Typical commissioning network
l l
The figure shows only the connection. The quantity and type of cables are not specified. Figure 2-1 illustrates the typical commissioning network. Other commissioning scenarios may be possible, as described in Table 2-2.
Table 2-2 Other commissioning scenarios Scenario In BM/TC separated mode, with the TCS configured remotely In BM/TC combined mode A over IP The external PCU The BSC6900 is connected to the MGW or BTS Alarm box configured on BSC6900 side Description The TCS is configured on the MSC side.
The BM and TC are configured in the same subrack. The TCS is not configured in the BSC6900. It communicates with the BSC6900 over the Pb interface, and provides PS service. Two NEs in the same equipment room are connected directly. The alarm box is connected to the BSC6900 LMT that serves as the alarm management system.
2-2
Issue 01 (2009-07-30)
Requirements for the Software and Data Files

l
Software installation package The installation package of the OMU application that is consistent with the local office version must be ready before commissioning.
License The license that is applicable to configuration in the local office is obtained through the Huawei technical support engineer.
MML command script file Before commissioning, complete the initial configuration according to the BSC6900 GSM Initial Configuration Guide to obtain the MML command script file. In addition, check and ensure the correctness of the data configuration according to the MML command script examples and the on-site negotiated data defined in the BSC6900 GSM Initial Configuration Guide.
Issue 01 (2009-07-30)
2-3
3 Commissioning Process
3
Procedure
1. 2. 3.
Commissioning Process
The BSC6900 commissioning involves verifying the equipment, updating the OMU database, activating and verifying the license, loading the BSC6900 board software and data files, verifying the interfaces, handling the alarms generated during commissioning, verifying the services, and connecting the BSC6900 to the M2000.
Step 1 Verify the equipment by referring to 4 Verifying the Equipment. Check the operating status of the hardware by referring to 4.1 Checking the Operating Status of the Hardware. Verify the OMU by referring to 4.2 Verifying the OMU. Logging in to the BSC6900 through the LMT by referring to 4.3 Logging In to the BSC6900 Through the LMT.
Step 2 Update the OMU data by referring to 5 Updating the OMU Database. Step 3 Activate and verify the license by referring to 6 Activating and Verifying the License. Step 4 Load the BSC6900 board software and data files by referring to 7 Loading BSC6900 Board Software and Data Files. 1. 2. 3. 4. Generate the data file for loading by referring to 7.1 Generating the Data File for the Loading. Set the loading mode by referring to 7.2 Setting the Loading Mode. Reset the BSC6900 boards by referring to 7.3 Resetting the BSC6900 Boards. Check the consistency of the version and the data by referring to 7.4 Checking the Consistency of the Data and the Version. Verify the Abis interface by referring to 8.1 Verifying the Abis Interface. Verify the A interface by referring to 8.2 Verifying the A Interface. Verify the Gb interface by referring to 8.3 Verifying the Gb Interface. Optional: Verify the Ater interface by referring to 8.4 Verifying the Ater Interface (required in BM/TC separated mode). Optional: Verify the Pb interface by referring to 8.5 Verifying the Pb Interface (required if the BSC6900 is configured with an external PCU).
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-1
Step 5 Verify GSM interfaces by referring to 8 Verifying GSM Interfaces. 1. 2. 3. 4. 5.
Issue 01 (2009-07-30)
3 Commissioning Process
Step 6 Handle the alarms generated during commissioning by referring to 9 Handling the Alarms Generated During the Commissioning. Step 7 Verify GSM services by referring to 10 Verifying the GSM Services. Step 8 Connect the BSC6900 to the M2000 by referring to 11 Connecting the BSC6900 to the M2000. ----End
Postrequisite
After the commissioning, create scheduled tasks by referring to 12 Creating Scheduled Tasks, so that the data backed up can be used for BSC6900 data restoration.
3-2
Issue 01 (2009-07-30)
4 Verifying the Equipment
4
About This Chapter
1.
Verifying the Equipment
The verifying of the equipment is the basis for commissioning the BSC6900. The verifying of the interfaces and services can be performed only after the equipment is verified. Equipment verifying involves checking the hardware operating status, verifying the OMU and logging in to the BSC6900 through the LMT. 4.1 Checking the Operating Status of the Hardware Before verifying the equipment, ensure that the cabinet is powered on and operates normally. 4.2 Verifying the OMU This describes how to verify the OMU to enable the normal communication between the LMT and the BSC6900. The OMU verifying involves installing the OMU application on site, checking the operation status of the OMU and changing the external physical IP address. 4.3 Logging In to the BSC6900 Through the LMT Log in to the BSC6900 through the LMT, and enabling the normal communication between the LMT and the BSC6900. LMT verifying ensures the BSC6900 commissioning through the LMT.
2.
3.
Issue 01 (2009-07-30)
4-1
4.1 Checking the Operating Status of the Hardware

Before verifying the equipment, ensure that the cabinet is powered on and operates normally.
Prerequisite
The BSC6900 cabinet has passed the power-on check.
Procedure
Step 1 Check whether the cabinet is powered on. If... The cabinet is not powered on, The cabinet is powered on, Step 2 Power on the cabinet by referring to Powering On the Cabinet. Step 3 Check the power supply to the cabinet components, as listed in Table 4-1. Ensure that the hardware operates normally. Table 4-1 Checklist of the power supply to the cabinet components Component Board Fan box Normal LED Status The green RUN LED on the board panel flashes every other second. The green STATUS LED on the panel of the fan box flashes every other second after the subrack and independent fan subrack are powered on. The green RUN LED on the board panel flashes every other second and the ALM LED is also OFF. Then... Go to Step 2. Go to Step 3.
Power monitoring communication board
----End
4.2 Verifying the OMU

This describes how to verify the OMU to enable the normal communication between the LMT and the BSC6900. The OMU verifying involves installing the OMU application on site, checking the operation status of the OMU and changing the external physical IP address.
Prerequisite
The software installation package of OMU application that is consistent with the version used in the local office and the Records of OMU Software Installation Information are obtained.
4-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-07-30)
Context
The external physical IP address described here refers to the physical IP address of the external Ethernet adapter team. This IP address is planned and set before the delivery of the OMU. It may be different from the IP address plan in the existing network. In this case, the external physical IP address needs to be changed according to the actual networking. Generally, the gateway IP address should be changed with the external physical IP address. The OMU application is installed in the active workspace of the OMU. If the BSC6900 works in active/standby OMU mode, then the OMU application must be installed in the active workspaces of both the active and standby OMUs. This part takes the condition that only one OMU is configured on the BSC6900 as an example.
Procedure
Step 1 Connect the PC to the ETH2 debugging port on the OMUa by using an Ethernet cable. Step 2 Set the IP address of the PC to be in the same network segment with the ETH2 port. The IP address of the ETH2 port before changing is 192.168.6.50, the subnet mask is 255.255.255.0. Step 3 Remotely log in to the Linux operating system by referring to Logging In to the OMU. Step 4 Check the OMU software environment by referring to Checking the OMU Software Environment. Step 5 Check that the OMU application is normally installed. 1. Run the /etc/rc.d/omud status command to check the running status of the OMU process. If... The returned information is running, The returned information is unused, Then... Go to Step 5.2. a. Run the /etc/rc.d/omud start command to start the omud. b. Go to Step 5.2. The returned information is neither running nor unused, Go to Step 6.
2.
Log in to the BSC6900 through the LMT by referring to 4.3 Logging In to the BSC6900 Through the LMT. Run the MML command LST VER to view the application version of the OMU. If... The OMU application version is same as that required by the customer, The OMU application version is different from that required by the customer, Then... End this task. a. Uninstall the OMU application by referring to Uninstalling the OMU Applications. b. Go to Step 6.
Issue 01 (2009-07-30)
4-3
Step 6 Install the OMU application in the active workspace by referring to Installing the OMU Applications in the Active Workspace. Step 7 Run the /etc/rc.d/omud start command to start the OMU application. Step 8 Run the ps -afx command to check the operating status of the OMU. You can infer that the OMU is in normal state if the following OMU service processes exist in the OMU active workspace directory\bin\bam\monitor: host_gate, ems_gate, authority, configure, maintain, stat, alarm, software, ftp_server, sntp, btsom, ems_agent, omu_manager, cfa and weblmt.
NOTE
You can infer that the standby OMU is in normal state if the following processes exist: software, ftp_server, sntp, and omu_manager.
Step 9 Run the ifconfig command to check whether the external physical IP address of the OMU is same as that planed in the existing network. If... The external physical IP address is same as that planed in the existing network, The external physical IP address is different from that planed in the existing network, Step 10 Run the /etc/rc.d/omud stop command to stop the omud. Step 11 Switch to the directory where the omutool program locates. You can run the ./omutool -h command to view the help information of the omutool. Step 12 Run the ./omutool extercard The external physical IP address The mask The gateway IP address command to change the external physical IP address and the gateway IP address. For example, you can run the following command and then press Enter. ./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
NOTE
Then... End this task.
Go to Step 10.
After the external physical IP address is changed, the BSC6900 can be connected to the OM network of the customer through the ETH0 or ETH1 port. In this case, the commissioning can be performed in a centralized manner.
Step 13 Run the /etc/rc.d/omud start command to start the OMU application so that the modification takes effect. Step 14 Remotely log out of the Linux operating system by referring to Logging Out of the OMU. ----End
4.3 Logging In to the BSC6900 Through the LMT

Log in to the BSC6900 through the LMT, and enabling the normal communication between the LMT and the BSC6900. LMT verifying ensures the BSC6900 commissioning through the LMT.
Prerequisite
l l
The OMU has passed the commissioning. The network connection between the LMT and the OMU is established.
Context
JRE is a standard plug-in in Java operating environment. If JRE is not installed, a message is displayed when the LMT is started. In this case, install JRE according to the prompt message on the screen. If the JRE installed in the LMT PC is not of the latest version, a message is displayed when the LMT is started, prompting you to update the JRE. In this case, it is recommended that you uninstall the old version and then install the latest version.
WARNING
When the LMT application is running, do not change the LMT PC system time. Otherwise, severe errors may occur on the system. If you have to change the system time, stop all the LMT applications first.
Procedure
Step 1 Check the configuration of the LMT PC and ensure that it meets the requirements. 1. Check the hardware configuration of the BSC6900 LMT PC to ensure that the requirements described in Configuration Requirements of the LMT PC are satisfied. 2. Check the security settings of the Internet Explorer, ensure that the Java script is supported. Step 2 Start the Internet Explorer, and then log in to the BSC6900 through the LMT. 1. Start the Internet Explorer. and then enter the external virtual IP address of the OMU of the BSC6900 on the address bar. The log-in dialog box is displayed, as shown in Figure 4-1. Figure 4-1 BSC6900 log-in dialog box
Issue 01 (2009-07-30)
4-5
NOTE
To log in to the BSC6900 by using the Domain user account, the connection between the BSC6900 and the M2000 server should be established.
2.
Enter the User Name, Password, and Verify Code, and then click Login to enter the LMT maintain interface.
----End
4-6
Issue 01 (2009-07-30)
5 Updating the OMU Database
5
Prerequisite
l l
Updating the OMU Database
This describes how to update the BSC6900 configuration data in the OMU database by running MML commands.
You have logged in to the BSC6900 through the LMT. The MML command data scripts applicable to the local office are verified and the contents are precise and complete.
Context
There are two ways to run the MML command script: through GUI or through MML commands. The MML command script can be executed through GUI only when the script is smaller than 4 MB. It is recommended that you run the MML script through MML commands, because this way is more efficient.
Procedure
l Run the MML command script through MML commands 1. 2. Run the MML command SET CFGDATAINEFFECTIVE and do not specify any parameter to set all the subracks to the ineffective mode. Run the MML command RST DATA. A dialog box is displayed. Click OK to initialize the BSC6900 configuration data in the OMU database. The Execution succeeded message is displayed. Copy the MML command script to the ftp folder in the OMU active workspace directory.
NOTE
3.
The directory of the OMU active workspace can be queried through the MML command LST OMUAREA.
4.
Run the MML command RUN BATCHFILE to run the MML command script. It is recommended that you set Finish Type to ALL_END_RETURN(Stop at end), Result Recording Type to REC_ERR(Record errors), and Result File Name to RUN_BATCHFILE_RESULT.txt.
Issue 01 (2009-07-30)
5-1

NOTE
l l
The result file RUN_BATCHFILE_RESULT.txt is saved in the ftp folder in the OMU active workspace directory. After the MML command script is executed, open the RUN_BATCHFILE_RESULT.txt file to check whether there is any command fails to be executed. If yes, extract the commands that fail to be executed to generate a new MML command script, correct the new script according to the prompts, and then go to Step 4 to run the new script.
Run the MML command script through GUI 1. 2. Run the MML command SET CFGDATAINEFFECTIVE and do not specify any parameter to set all the subracks to the ineffective mode. Run the MML command RST DATA. A dialog box is displayed. Click OK to initialize the BSC6900 configuration data in the OMU database. The Execution succeeded message is displayed.
NOTE
If an Error dialog box showing Execution failed. Do you want to continue? is displayed during the execution of the MML command script, you can infer that the MML command script is incorrect. In this case, select Yes to all to ignore the error prompt. After the script is executed, extract the commands that are fail to be executed to generate a new MML command script, correct the new script, and then go to Step 4 to run the new script.
3.
Click Batch on the LMT main page. The Batch tab page is displayed, as shown in Figure 5-1.
Figure 5-1 Batch tab page
4. 5. 6. 7.
Click Open.... The Open dialog box is displayed. Select the prepared MML command data script. Click Open. The selected script is displayed in the Batch tab page. Click Set.... The dialog box for setting batch commands is displayed. Set Sending Commands interval(s) to 0. Select Save Failed Commands, and then set the save path of the unsuccessful commands. Click OK to complete the setting of the batch commands, as shown in Figure 5-2.
5-2
Figure 5-2 Setting the batch commands
8. 9.
In the Batch tab page, set Execution Type to All. Click Go. The system runs the MML commands one by one.
NOTE
Click OK when the system prompts that the current configuration is in ineffective mode after you click Go. The execution of MML commands may take a long time. A total of 50,000 commands can be run in an hour.
10. Click OK when the message dialog box is displayed, indicating that the running of all the MML commands is complete. ----End
Issue 01 (2009-07-30)
5-3
6 Activating and Verifying the License
6
Prerequisite
l l
Activating and Verifying the License
This describes how to activate the license and verify the license configuration information to enable the service checking.
You have logged in to the BSC6900 through the LMT. The license is ready and the license check is passed.
Procedure
Step 1 Run the MML command DLD LICENSE to download the License to the OMU active workspace directory\ftp\license. Step 2 Run the MML command LST LICENSE and then set File Name to the name of the license file to be activated to query the detailed configuration information of the license file. If... Then...
The license is consistent with what you apply Go to Step 3. for, The license is inconsistent with what you apply for, Contact the Huawei Customer Service Center by referring to Contact the Huawei Customer Service Center.
Step 3 Run the MML command ACT LICENSE to activate the license file. ----End
Postrequisite
If the license activation fails, you can infer that the configuration data of the license is inconsistent with that in the OMU database. Check the configuration data of the license and the configuration data in the OMU database.
l
If the configuration data of the license is incorrect, apply for a new license.
Issue 01 (2009-07-30)
6 Activating and Verifying the License

l
If the configuration data in the OMU database is incorrect, correct the configuration data, and then activate the license again.
6-2
Issue 01 (2009-07-30)
7 Loading BSC6900 Board Software and Data Files
Loading BSC6900 Board Software and Data Files
About This Chapter

This describes how to load the BSC6900 board software and data files to enable the normal operation of the BSC6900.
Prerequisite
l l
The equipment verifying is complete. The OMU database is updated.
Context
The software of BSC6900 boards is generated automatically in the OMU active workspace directory\bin\fam when installing OMU applications. The software can be loaded directly. To make the configuration take effect, format the configuration data in the OMU database to generate a .DAT data file, and then reset the BSC6900.
Procedure
----End 1. 7.1 Generating the Data File for the Loading This describes how to generate the BSC6900 data file, which can be loaded, by using the MML command data scripts. 7.2 Setting the Loading Mode This describes how to set the loading modes of all the board subsystems before resetting BSC6900 boards. 7.3 Resetting the BSC6900 Boards This describes how to load the BSC6900 board software and data files from the OMU installation directory to the boards and make them take effect. 7.4 Checking the Consistency of the Data and the Version
2.
3.
4.
Issue 01 (2009-07-30)
This describes how to check whether the board configuration and the software version of the BSC6900 are consistent with the information in the OMU.
7-2
Issue 01 (2009-07-30)
7.1 Generating the Data File for the Loading

This describes how to generate the BSC6900 data file, which can be loaded, by using the MML command data scripts.
Prerequisite
l
You have logged in to the BSC6900 through the LMT.
Context
The generated loading file is saved in OMU active workspace directory\bin\fam. The file name is in ABCXXYYZZ.DAT format, such as XPUa000200.DAT. Table 7-1 lists the detailed information. Table 7-1 Name of the loading file Parameter ABC XX YY ZZ Indication Board name Subrack number Slot number Subsystem number
Procedure
Step 1 Run the MML command SET CFGDATAEFFECTIVE and do not specify any parameter to set all the subracks to effective mode. Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format active area) (do not specify the subrack number) to format the configuration data in the OMU database. If the Execution succeeded message is displayed, then the .DAT data files are generated and saved in OMU active workspace directory\bin\fam. ----End
7.2 Setting the Loading Mode

This describes how to set the loading modes of all the board subsystems before resetting BSC6900 boards.
Prerequisite
Context
For details about the loading modes, see Loading Management.
Issue 01 (2009-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-3
Procedure
Step 1 Run the MML command SET LODCTRL, and then set Board Start Load Control to LFB (Load from OMU and write flash). If the Execution succeeded message is displayed, the setting of the BSC6900 loading modes is complete. ----End
7.3 Resetting the BSC6900 Boards

This describes how to load the BSC6900 board software and data files from the OMU installation directory to the boards and make them take effect.
Prerequisite
l l l
The data file for the Loading is generated. You have logged in to the BSC6900 through the LMT. All the subracks are powered on.
Context
The time for system resetting is different in different scenarios, as listed in Table 7-2. Table 7-2 Time for system resetting in different scenarios Work Mode BM/TC combined, or A over IP BM/TC separate Resetting Time The resetting time is less than nine minutes in the maximum configuration. The resetting time is less than fifteen minutes in the maximum configuration. Sequence for Resetting Subracks The subracks should be reset in the following sequence: EPS -> MPS. The subracks should be reset in the following sequence: remote extension TCS-> remote main TCS -> EPS -> MPS.
You can run the MML command LST SUBRACK and then check the parameters Subrack Type and Remote TC Central to determine the resetting sequence.
Procedure
Step 1 Run the MML command RST SUBRACK, and then set Subrack No. to the number of the subrack to be reset. A dialog is displayed, asking you whether to proceed. Click OK. The boards in the subrack automatically load the BSC6900 board software and data files from the OMU. Run this command repeatedly to reset all the subracks of the BSC6900.
NOTE
You can observe the loading process at the Progress tab page on the LMT main page. If this tab page is hidden, click Progress in the toolbar on the LMT main page.
7-4
Issue 01 (2009-07-30)
Step 2 After all the subracks are reset, click the Device Maintenance on the LMT main page. The Device Maintenance tab page is displayed. Step 3 Click the BSC6900 to be queried in the Device Navigation Tree to start the device panel. If... Then...
The device panel shows that all the boards End this task. are in normal state, The device panel shows that some boards Rectify the faults according to the prompt. For are in normal state, details, see 13.5 Data Loading Failure on the Board. ----End
7.4 Checking the Consistency of the Data and the Version

This describes how to check whether the board configuration and the software version of the BSC6900 are consistent with the information in the OMU.
Prerequisite
l l
All the subracks and boards are running normally. You have logged in to the BSC6900 through the LMT.
Procedure
Step 1 Run the MML command ACT CRC and do not specify any parameter to check whether the board configuration is consistent with the data in the OMU. Expected result: The All table data consistent. message is displayed. Step 2 Run the MML command CMP BRDVER and do not specify any parameter to check whether the version run by the BSC6900 is consistent with the version information in the OMU. Expected result: The Compare consistent message is displayed. If... Then...
The board configuration or software version Run the MML command RST SUBRACK to of the BSC6900 is inconsistent with the reset the subrack with incorrect data or information in the OMU, version. The board configuration or software version The BSC6900 board software and data files of the BSC6900 is consistent with the are loaded successfully, end this task. information in the OMU, ----End
8 Verifying GSM Interfaces
8
About This Chapter
Context
Verifying GSM Interfaces
This describes how to verify the GSM interfaces on the BSC6900 side during the BSC6900 commissioning. The GSM interfaces are the Abis interface, A interface, Gb interface, Ater, and Pb interface. The Ater interface verification is mandatory only in BM/TC separated mode. The Pb interface verification is mandatory only if the BSC6900 is configured with an external PCU.
During the interface verification, you can run the LST command to query the configuration information. For example, before running the MML command DSP ADJNODE, you can run the MML command LST ADJNODE to query the parameter Adjacent Node ID. 8.1 Verifying the Abis Interface This describes how to verify the control plane and the user plane of the Abis interface. The Abis interface verification varies according to the transmission mode over the Abis interface. 8.2 Verifying the A Interface This describes how to verify the control plane and the user plane of the A interface. The A interface verification varies according to the transmission mode of the A interface. 8.3 Verifying the Gb Interface This describes how to verify the Gb interface. The Gb interface verification varies according to the transmission mode over the Gb interface. 8.4 Verifying the Ater Interface This describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode. 8.5 Verifying the Pb Interface If the BSC6900 is configured with an external PCU, Pb interface verification is needed.
Issue 01 (2009-07-30)
8-1
8.1 Verifying the Abis Interface

This describes how to verify the control plane and the user plane of the Abis interface. The Abis interface verification varies according to the transmission mode over the Abis interface.
Prerequisite
l l
The BSC6900 has passed the commissioning. The BSC6900 and the base stations are physically connected, and the hardware installation acceptance is passed. The base stations used to verify the Abis interface are commissioned and the cell configuration is complete. All the subracks of the BSC6900 are running normally. You have logged in to the BSC6900 through the LMT.
l l
Context
For the commissioning of the base station, see the commissioning guide of the base station. The following takes one base station as an example to describe the commissioning process on the Abis interface. If multiple base stations are connected, repeat the operations.
Procedure
l Verifying the Abis interface (Abis over TDM) 1. Run the MML command DSP LAPDLNK to check whether the Link Access Protocol on the D channel (LAPD) link on the Abis interface is normal. Expected result: The value of UsageStatus is Normal. 2. Run the MML command DSP ABISTS to query the timeslot status of the Abis interface. Expected result: The State of many timeslots is Idle, and there is no timeslot with the State of Failure. If the LAPD link or timeslot status on the Abis interface is abnormal, checking the transmission link by referring to 13.1 Checking the Transmission Link. 3. Run the MML command DSP BTSATTR to query the status of the carrier of the base station. Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No. l Verifying the Abis interface (Abis over IP) 1. Run the MML command DSP LAPDLNK to check whether the LAPD link on the Abis interface is normal. Expected result: The value of UsageStatus is Normal. 2. Run the MML command DSP ADJNODE to query the status of the adjacent node. Expected result: The value of Operation state is Available and the available bandwidth cannot be all 0.
3.
Run the MML command DSP IPPATH to query the status of the IP path on the Abis interface. Expected result: The value of Operation state is Available. If the value of Operation state is Unavailable, see 13.4 IP Connection Setup Failure for troubleshooting.
4.
Run the MML command DSP BTSSTAT to query the status of the cells and channels. Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No. Run the MML command DSP LAPDLNK to check whether the LAPD link on the Abis interface is normal. Expected result: The value of UsageStatus is Normal. Optional: Run the MML command LST BTSABISHDLCPATH to query the HDLC link number. Run the MML command DSP HDLCLNK to query the status of the HDLC link. Expected result: The value of operation state is Available and the value of Available Tx Bandwidth or Available Rx Bandwidth is not 0. Run the MML command DSP BTSSTAT to query the status of the cells and channels. Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No.
Verifying the Abis interface (Abis over HDLC) 1.
2. 3.
4.
----End
8.2 Verifying the A Interface

This describes how to verify the control plane and the user plane of the A interface. The A interface verification varies according to the transmission mode of the A interface.
Prerequisite
l l l l l l
The BSC6900 has passed the commissioning. The BSC6900 and the MSC are physically connected. The MSC used to verify the A interface operates normally. The Ater interface has been verified when the BSC6900 is in BM/TC separated mode. All the subracks of the BSC6900 are running normally. You have logged in to the BSC6900 through the LMT.
Procedure
l Verifying the A interface (A over TDM) 1. Run the MML command DSP MTP2LNK to query the status of the Message Transfer Part Level 2 (MTP2) signaling link. Expected result: The value of Link State is IN SERVICE. If the value of Link State is OUT OF SERVICE, check the transmission links by referring to 13.1 Checking the Transmission Link.
2.
Run the MML command DSP MTP3LNK to query the status of the Message Transfer Part Level 3 (MTP3) signaling link. Expected result: The value of Operation state is Available. Run the MML command DSP SSN to query the status of the SCCP SSN. Expected result: The value of SSN state is Allowed. Run the MML command DSP N7DPC to query the status of the SS7 destination signaling point. Expected result: The value of SCCP DSP state is Accessible.
3. 4.
5. 6.
Optional: Run the MML command LST AE1T1 to query the configuration information such as OPC Index and DPC Group Index. Run the MML command DSP ACIC to query the status of A interface circuits. Expected result: The CIC State of many CICs is Idle, and there is no CIC with the CIC State of Failure.
Verifying the A interface (A over IP) 1. Run the MML command DSP SCTPLNK to query the status of the Stream Control Transmission Protocol (SCTP) link. Expected result: The value of SCTP link Operation state is Normal. If the value of Operation state is Unavailable, check the transmission links by referring to 13.1 Checking the Transmission Link.
NOTE
Run the MML command DSP SCTPLNK for two or three times, if the value of Operation state is always Normal and the value of State Changed Time does not change, you can infer that the SCTP link is normal without intermittent disconnection.
2.
Run the MML command DSP M3LNK to query the status of the MTP3 User Adaption Layer (M3UA) signaling link. Expected result: The value of Operation state is Activated state. Run the MML command DSP SSN to query the status of the SCCP SSN. Expected result: The value of SSN state is Allowed. Run the MML command DSP N7DPC to query the status of the SS7 destination signaling point. Expected result: The value of SCCP DSP state is Accessible. Run the MML command DSP ADJNODE to query the status of the adjacent node. Expected result: The value of Operation state is Available and the available bandwidth cannot be all 0.
3. 4.
5.
6.
Run the MML command DSP IPPATH to query the status of the IP path. Expected result: The value of Operation state is Available. If the value of Operation state is Unavailable, see 13.4 IP Connection Setup Failure for troubleshooting.
----End
8-4
Issue 01 (2009-07-30)
8.3 Verifying the Gb Interface

This describes how to verify the Gb interface. The Gb interface verification varies according to the transmission mode over the Gb interface.
Prerequisite
l l
The BSC6900 has passed the commissioning. The BSC6900 and the SGSN are physically connected, and the hardware installation acceptance is passed. The SGSN equipment used to verify the Gb interface operates normally. All the subracks of the BSC6900 are running normally. You have logged in to the BSC6900 through the LMT.
l l l
Procedure
l Verifying the Gb interface links (Gb over FR) 1. Run the MML command DSP BC to query the status of the Bearer Channel (BC) to be verified. Expected result: The value of BC Service State is available.
NOTE
If the value of BC Administration State is Blocked, run the MML command UBL BC to unblock the BC, and then run the MML command DSP BC to check whether the BC status is normal. If the status remains abnormal, check the transmission links by referring to 13.1 Checking the Transmission Link.
2.
Run the MML command DSP NSVC to query the status of the Network Service Virtual Connection (NSVC) to be verified. Expected result: The value of NSVC Service State is Active Unblock. Optional: Run the MML command LST NSE to query the NSE configuration information. Run the MML command DSP SIGBVC to query the SIG BSSGP Virtual Connection (SIGBVC) status of the Network Service Entity (NSE) to be verified. Expected result: The value of SIG BVC State is Normal.
NOTE
3. 4.
If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE that has a different NSE ID.
5.
Run the MML command DSP PTPBVC to query the status of the PTP BSSGP Virtual Connection (PTPBVC) of the NSE to be verified. Expected result: The value of Service State is Normal. Optional: Run the MML command LST NSVLLOCAL or LST NSVLREMOTE to query the configuration information of the local or remote Network Service Virtual Link (NSVL). Run the MML command DSP NSVL to query the status of the Network Service Virtual Link (NSVL) to be verified. Expected result: The value of NSVL State is Normal .
Verifying the Gb interface links (Gb over IP) 1.
2.
Issue 01 (2009-07-30)
8-5
If the value of NSVL State is Fault, check the transmission links by referring to 13.1 Checking the Transmission Link. 3. Run the MML command DSP GBIPROUTE to query the status of the IP connection to be verified on the Gb interface. Expected result: The value of State is Normal . If the value of State is Faulty, run the MML command DSP IPRT to check whether the route configuration on the Gb interface is correct. 4. 5. Optional: Run the MML command LST NSE to query the NSE configuration information. Run the MML command DSP SIGBVC to query the SIGBVC status of the NSE to be verified. Expected result: The value of SIG BVC State is Normal.
NOTE
If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE that has a different NSE ID.
6.
Run the MML command DSP PTPBVC to query the PTPBVC status of the NSE to be verified. Expected result: The value of Service State is Normal.
----End
Postrequisite
Handling Suggestions to Exceptional NSVC Status
l
If the value of NSVC Manage State is Unblock and the NSVC Service State is Active Block, you can infer that the FR link that bears the NSVC is functional and that the NSVC is blocked by the SGSN. If the value of NSVC Manage State is Block and the NSVC Service State is Active Block, you can infer that the FR link that bears the NSVC is functional and that the NSVC is blocked by the BSC6900 or by both the BSC6900 and the SGSN. 1. 2. Run the MML command UBL NSVC to unblock the BSC6900. Run the MML command DSP NSVC to query the status of the NSVC. If the value of NSVC Service State is still Active Block, you can infer that the NSVC is blocked by the SGSN. The NSVC ID and NSE ID of the NSVC on the BSC6900 are inconsistent with that on the SGSN. The NSVC configured on the same BC at the SGSN is not the required one.
If the value of NSVC Service State is Deactive Block, the possible causes are as follows:
Handling Suggestions to Exceptional PTPBVC Service Status 1. If the value of PTPBVC Manage State is Block, run the MML command UBL PTPBVC to unblock the PTPBVC, and then run the MML command DSP PTPBVC to query the status of the PTPBVC. If the status remains abnormal, go to the next step. Run the MML command RST PTPBVC to reset the PTPBVC, and then run the MML command DSP PTPBVC to query the status of the PTPBVC. If the status remains abnormal, go to the next step.
2.
8-6
3.
Run the MML command RST PSCELL to reset the cell corresponding to the exceptional PTPBVC, and then run the MML command DSP PTPBVC to query the status of the PTPBVC. If the status remains abnormal, go to the next step. Run the MML command RST SIGBVC to reset the SIGBVC corresponding to the exceptional PTPBVC, and then run the MML command DSP PTPBVC to query the status of the PTPBVC. If the status remains abnormal, contact the Huawei Customer Service Center by referring to Contact the Huawei Customer Service Center.
4.
8.4 Verifying the Ater Interface

This describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode.
Prerequisite
l l l l l
The BSC6900 has passed the commissioning. The MPS/EPS and the TCS are physically connected. The data configuration on the Ater interface is complete. The TCS is loaded and started. You have logged in to the BSC6900 through the LMT.
Procedure
Step 1 Optional: Run the MML command LST ATERE1T1 to query the configuration information such as Ater connection path index and ID of BSC in TC Pool. Step 2 Run the MML command DSP ATERTS to query whether the service paths on the Ater connection channels are normal. Expected result: The State of many timeslots is Idle, and there is no timeslot with the State of Failure. If the State of a timeslot is Failure, check the transmission links by referring to 13.1 Checking the Transmission Link. Step 3 Optional: If the TCS is configured remotely, run the MML command DSP ATERSL to query whether the data configuration of the Ater signaling link is normal. Expected result: The value of UsageStatus is Normal. If the value of UsageStatus is Faulty, check the transmission links by referring to 13.1 Checking the Transmission Link. Step 4 Repeat Step 2 through Step 3 to verify whether the service channels on other Ater connection paths are normal. ----End
8.5 Verifying the Pb Interface

If the BSC6900 is configured with an external PCU, Pb interface verification is needed.
Prerequisite
l l
The PCU used to verify the Pb interface operates normally. The BSC6900 and the PCU are physically connected, and the hardware installation acceptance is passed. All the subracks of the BSC6900 are running normally. You have logged in to the BSC6900 through the LMT.
l l
Procedure
Step 1 Run the MML command DSP LAPDLNK to check whether the LAPD link on the Pb interface is normal. Expected result: The value of UsageStatus is Normal. Step 2 Optional: Run the MML command LST PBE1T1 to query the E1/T1 configuration information on the Pb interface. Step 3 Run the MML command DSP PBCIC to query the status of the circuit on the Pb interface. Expected result: The status of many circuit identity codes (CICs) is Idle, and there is no CIC with the status of Failure. ----End
8-8
Issue 01 (2009-07-30)
9 Handling the Alarms Generated During the Commissioning
Handling the Alarms Generated During the Commissioning

This describes how to handle the alarms generated during the commissioning, thus preventing the alarms from affecting the verification of services.
Prerequisite
l l
The communication between the BSC6900 and the OMU is normal. You have logged in to the BSC6900 through the LMT.
Procedure
Step 1 Click the Alarm on the LMT main page. The Alarm tab page is displayed. Step 2 Check whether any alarm is listed on the Fault tab page. If... No alarm is listed, One or more alarms are listed, Then... End this task. Go to Step 3.
Step 3 Double-click the alarm to be handled in the fault tab page. The Alarm Detailed Information dialog box is displayed. Step 4 Click Solution.... The LMT Online Help interface is displayed. Step 5 Follow the suggestions to handle the alarm.
NOTE
If the alarm persists, contact the Huawei Customer Service Center by referring to Contact the Huawei Customer Service Center.
Step 6 Repeat Step 3 to Step 5 to handle other alarms. ----End

10 Verifying the GSM Services
10
Prerequisite
l l
Verifying the GSM Services
This describes how to verify that the GSM basic services and the feature services that are enabled are normal. The basic services consist of speech service and data service. The feature services consist of the inter-RAT handover, location service, and AMR service.
The BSC6900 has passed the commissioning. The commissioning over the Abis, A, Gb, Ater and Pb interfaces is successful. The commissioning over Ater interface is mandatory only in BM/TC separated mode. The commissioning over Pb interface is mandatory only if the BSC6900 is configured with an external PCU. The MSs used for test are functional and are registered in the HLR. You have logged in to the BSC6900 through the LMT.
l l
Procedure
Step 1 Table 10-1 lists the procedure for verifying the basic services by testing the MS in the BTS cells. Table 10-1 Performing dialing tests on the basic services Basic Services Speech service Procedure for Conducting the Dialing Test Make 20 calls from an MS to a fixed-line phone and hold on each call for 60 seconds. Expected Result The connection success rate is higher than 90%. The voice is clear and without loud noise. No call drop occurs and the system resources are released normally after the call is terminated. The connection success rate is higher than 90%. The voice is clear and without loud noise. No call drop occurs and the system resources are released normally after the call is terminated.
10-1
Make 20 calls from a fixed-line phone to an MS and hold on each call for 60 seconds.
Issue 01 (2009-07-30)
10 Verifying the GSM Services
Basic Services
Procedure for Conducting the Dialing Test Make 20 calls from an MS to another MS and hold on each call for 60 seconds.
Expected Result The connection success rate is higher than 90%. The voice is clear and without loud noise. No call drop occurs and the system resources are released normally after the call is terminated. Faxes are sent and received normally. The test data rate is similar to the data rate tested in a lab.
Data service
Send a fax from an MS to an electrograph. Send a fax from an electrograph to an MS. Test the General Packet Radio Service (GPRS) or Enhanced Data Rate for GSM Evolution (EDGE) function on the MS.
NOTE
If the result of service verification cannot meet the expected results, start message tracing on the LMT over the Um, Abis, A, Gb, Pb, and Ater interfaces. Where the message tracing over the Pb interface is mandatory only when the BSC6900 is configured with an external PCU, and the message tracing over the Ater interface is mandatory only in BM/TC separated mode.
Step 2 Table 10-2 lists the procedure for verifying the feature services by testing the MS in the BTS cells. Table 10-2 Performing dialing tests on the feature services Feature Services Inter-RAT handover Procedure for Conducting the Dialing Test Hand over a dual-mode MS from the GSM to the UMTS for 20 times. Hand over a dual-mode MS from the UMTS to the GSM for 20 times. Make a call from the MS and hold on the call. Then, locate the MS. Make 50 calls from an MS to a fixed-line phone and select voice version to AMR. Expected Result The connection success rate is higher than 90%. The voice is clear and without loud noise.
Location service Adaptive Multi Rate (AMR) service
The location of the MS conforms to the precision requirements. The connection success rate is higher than 90%. The voice is clear and without loud noise.
----End
10-2
Issue 01 (2009-07-30)
11 Connecting the BSC6900 to the M2000
11
Prerequisite
l l
Connecting the BSC6900 to the M2000
This describes how to connect the BSC6900 to the M2000 for the centralized management.
The Operation and Maintenance (OM) network has passed commissioning. The M2000 is operational. The version of the M2000 is compatible with that of the BSC6900.
Context
l
If the BSC6900 and the M2000 are in the same network segment, you need not configure the IP route to the M2000. If the BSC6900 and the M2000 are not in the same network segment, you need to configure the IP route to the M2000.
Procedure
Step 1 Connect the BSC6900 to the OM network. 1. 2. Connect one end of the straight-through cable to the LAN Switch that is connected to the BSC6900. Connect the other end of the straight-through cable to the network device, for example, a hub or a router. Run the MML command LST OMUIPRT to check whether the route to the M2000 is configured on the OMU.
l
Step 2 Configure the IP route from the BSC6900 to the M2000. 1.
If the values of Destination Network Address, Destination Address Mask, and Forward Route Address in the result are consistent with the planed addresses, then you can infer that the BSC6900 already has a route to the M2000. Go to Step 2.3. If the Destination Network Address, Destination Address Mask, and Forward Route Address in the result are not consistent with the planed addresses, then you can infer that the BSC6900 does not have a route to the M2000. Go to Step 2.2.
2. 3.
Issue 01 (2009-07-30)
Run the MML command ADD OMUIPRT to configure the route from the BSC6900 to the M2000. Verify the configuration of the route from the BSC6900 to the router.
11 Connecting the BSC6900 to the M2000
Logging in to the OMU remotely, run the ping command to check whether the network between the BSC6900 and the router is operational. If the OMU can receive a response packet from the router, go to Step 2.4. Otherwise, check that the OMU and the router are properly connected. 4. Verify the configuration of the route from the BSC6900 to the M2000. Logging in to the OMU remotely, run the ping command to check whether the network between the BSC6900 and the M2000 is operational. If the BSC6900 can receive a response packet from the router, go to Step 3. Otherwise, check that the M2000 and the router are properly connected.
Step 3 Create the BSC6900 on the M2000. For details, see the NE creating-related parts in M2000 documents.
CAUTION
l
If a firewall exists between BSC6900 and M2000, ensure the communication ports connecting the BSC6900 and M2000. For details on the ports connecting the BSC6900 and M2000, see 14.1 Communication Ports Used by the BSC6900.
----End
Example
Table 11-1 describes how to configure the route between the BSC6900 and the M2000. Table 11-1 Configuring the route from the BSC6900 to the M2000 Scenar io Action The IP address of the M2000 server is 10.11.100.23. The mask is 255.255.255.0. The OMU is connected to the M2000 network segment through the router. The IP address of the router is 172.121.139.10. 1. Run the MML command ADD OMUIPRT.
l l l
Set Destination Network Address to 10.11.100.23. Set Destination Address Mask to 255.255.255.0. Set Forward Route Address to 172.121.139.10.
2. Run the Telnet client, such as PuTTY, to log in to the OMU. 3. Run the ping 172.121.139.10 command. 4. Run the ping 10.11.100.23 command.
11-2
Issue 01 (2009-07-30)
12 Creating Scheduled Tasks
12
Prerequisite
l l l
Creating Scheduled Tasks
This describes how to create the scheduled tasks for the automatical backup of the system data and logs after commissioning; thus, the data and logs can be used for the BSC6900 equipment fault recovery.
The BSC6900 has passed the commissioning. You have logged in to the BSC6900 through the LMT. To create scheduled tasks, you must be an administrator.
Context
You can set the period for the scheduled task according to the actual situation. The period for the scheduled task is of the following types: fixed time, day based scheduling, day based duration, week based scheduling, week based duration, month based scheduling, and month based duration.
l
Scheduled tasks for backing up system data After the scheduled task is executed, you can obtain the latest backup file from the backup directory on the OMU. For the backup directory and the file name, see the Help Information of the MML command BKP DB.
Scheduled tasks for backing up logs The logs are backed up in the OMU active workspace directory\ftp directory as compressed files at the specified time. Table 12-1 lists the name of the compressed files. Table 12-1 Log type and file name Type ALL OMU HOST File Name FixInfo_All.zip FixInfo_OMU.zip FixInfo_HOST.zip
Issue 01 (2009-07-30)
12-1
12 Creating Scheduled Tasks
To check the information of the logs, download the logs through the FTP client. For details, see the help information of the FTP client.
NOTE
l l
The files that are automatically backed up do not overwrite the files backed up earlier. For the directory structure of the OMU workspace, see Checking the Installation Directory of the OMU Applications.
Procedure
Step 1 Run the MML command ADD SCHTSK. Specify the Task Name and Task ID to add a scheduled task. Step 2 Run the MML command ADD SUBTSK. Set Command String to BKP DB to create a scheduled task for backing up the system data. Step 3 Run the MML command ADD SUBTSK. Set Command String to COL LOG to create a scheduled task for backing up logs.
l l
To view the created tasks, run the MML command LST SUBTSK. To change the time and period for backing up tasks, run the MML command MOD SUBTSK.
----End
Example
l
To set the system data to be backed up at 2010-4-12-12:00:00, run the following command: ADD SUBTSK: ID=1, SUBID=8, SCMD="BKP DB:", FREQ=ONTIME, SD=2010&04&12, TM=12&00;
To set the BSC6900 logs to be automatically backed up from 2010-4-10-11:01:52 to 2010-4-12-11:01:52 (log type: ALL, time mode: fixed time), run the following command: ADD SUBTSK: ID=1, SUBID=44, SCMD="COL LOG: TP=ALL, ST=2010&04&10&11&01&52, ET=2010&04&12&11&01&52", FREQ=ONTIME, SD=2010&04&13, TM=12&00;
12-2
Issue 01 (2009-07-30)
13 FAQ
13
About This Chapter
This describes how to handle the common problems during the commissioning. 13.2 Unavailable E1/T1 Port This describes how to handle the problem that the E1/T1 port is unavailable. 13.3 Unavailable FE/GE Port This describes how to handle the problem that the FE/GE port is unavailable. 13.4 IP Connection Setup Failure This describes how to handle the failures during IP connection setup.
FAQ
13.1 Checking the Transmission Link This describes how to verify that the terrestrial transmission links of the BSC6900 are functional. The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link.
13.5 Data Loading Failure on the Board This describes how to handle the failures that occur during data loading to the BSC6900 board. 13.6 Performing the Loopback Test on the E1/T1 Port This describes how to perform the loopback test to check whether the E1/T1 port is functional. 13.7 Performing the Loopback Test on the Optical Port This describes how to perform the group loopback test to check whether the optical port is functional.
Issue 01 (2009-07-30)
13-1
13 FAQ
13.1 Checking the Transmission Link

This describes how to verify that the terrestrial transmission links of the BSC6900 are functional. The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link.
Prerequisite
l l
All the subracks of the BSC6900 are running normally. You have logged in to the BSC6900 through the LMT.
Procedure
l Check the status of the transmission link based on the transmission mode. Table 13-1 Methods for checking the status of transmission link in different transmission modes If the transmission on the interface is over... IP PPP/MLPPP transmission mode Then... 1. If the channelized STM-1 transmission is used on the interface, check the status of the optical port. 2. Check the status of the E1/T1 port. 3. Check the status of the upper-layer link.
l
For the PPP transmission mode, run the MML command DSP PPPLNK to check the status of the PPP link. For the MLPPP transmission mode, run the MML command DSP MPGRP to check the status of the MLPPP group.
NOTE If the upper-layer link is not functional, run the MML command LST PPPLNK/LST MPGRP accordingly to check whether the data configuration on the interface is correct.
IP over Ethernet transmission mode TD M E1/T1 transmission mode
Check the status of the FE/GE port. Check the status of the E1/T1 port.
13-2
Issue 01 (2009-07-30)
13 FAQ
If the transmission on the interface is over... Channelized STM-1 transmission mode HDLC FR
Then... Checkg the status of the optical port. Check the status of the E1/T1 port. Check the status of the E1/T1 port.
Checking the status of the E1/T1 port 1. Run the MML command DSP E1T1 to query the status of the E1/T1 ports. Expected result: The Port running state of the associated E1/T1 port is Port available. If the value of the Port running state is Port is down, see the 13.2 Unavailable E1/ T1 Port for troubleshooting.
Checking the status of the FE/GE port 1. Run the MML command DSP ETHPORT to query the status of the Ethernet port. Expected result: The value of Link Availablility Status is Available. If either of the following cases occurs, see 13.3 Unavailable FE/GE Port for troubleshooting.

The value of Link Availablility Status is Unavailable. The value of Port state is Deactivated.
2.
Optional: Check the connectivity of the gateway (mandatory in three-layer networking). (1) Run the MML command LST IPCHK to query the configuration of the gateway connectivity check. (2) Run the MML command STR IPCHK to start the gateway connectivity check.
NOTE
If the BFD function is supported by and enabled at the peer router, set Check type to SBFD. Otherwise, set it to ARP.
(3) In the alarm tab page of the LMT, check whether the ALM-21346 IP Connectivity Check Failure alarm is reported. If yes, clear the alarm as suggested. (4) To keep the gateway connectivity check, end this task; otherwise, run the MML command STP IPCHK to stop the gateway connectivity check. l Checking the status of the optical port 1. ----End Run the MML command DSP OPT to query the status of the optical port. Expected result: The value of Optical port state is Available.
13.2 Unavailable E1/T1 Port

This describes how to handle the problem that the E1/T1 port is unavailable.
13 FAQ
Symptoms
When you run the MML command DSP E1T1 to check the status of E1/T1 ports, the Port running state on the returned result shows Port is down.
Solutions
1. If the value of Port running state is Port is down, handle the problem as follows:
l l
When electrical ports serve as the bearers, perform loopback test on the faulty E1/T1 ports. For details, see 13.6 Performing the Loopback Test on the E1/T1 Port. When optical ports serve as the bearers, perform group loopback test on the faulty optical ports. For details, see 13.7 Performing the Loopback Test on the Optical Port.
2.
Check whether the following alarms are listed in the alarm tab page of the LMT. If any of the alarms exist, handle them according to the suggestions in the online help.
l l l l
ALM-21201 E1/T1 Signal Loss ALM-21202 E1/T1 Frame out of Synchronization ALM-21203 E1/T1 Remote Alarm Indication ALM-21205 E1/T1 Multiframe out of Synchronization
NOTE
When you run the MML command DSP E1T1 to check the E1/T1 port status, the value of Is this E1/T1 occupied may be set to NO. In such a case, if the ALM-21201 E1/T1 Signal Loss exists, the link is still operational.
13.3 Unavailable FE/GE Port

This describes how to handle the problem that the FE/GE port is unavailable.
Symptoms
When you run the MML command DSP ETHPORT to check the status of the FE/GE port, any of the following situation exists:
l l
The value of Link Availablility Status is Unavailable. The value of Port state is Deactivated.
Solutions
1. If the value of Link Availablility Status is Unavailable, check the connection of the Ethernet cable and check whether the peer Ethernet port is enabled. See the online help for the handling suggestions of the alarm. If the value of Port state is Deactivated, run the MML command ACT ETHPORT to activate the FE/GE port.
2.
13.4 IP Connection Setup Failure

This describes how to handle the failures during IP connection setup.
Symptoms
During IP connection setup, the IP link fails to be established.
13 FAQ
Solutions
When the user plane is over IP transmission, handle the failure according to Table 13-2. Table 13-2 Operation index Index *1-1 Action Determine the IP path that carries the common channel. Check whether the IP path is operational. Remarks Run the MML commands LST IPPATH and LST TRMMAP to obtain the ID of the IP path that carries the common channel. 1. Run the MML command DSP IPPATH to query the status of the IP path. 2. If any transmission resource group is configured over the Iub interface, run the MML command DSP RSCGRP to query the status of the transmission resource group. 3. If all the IP paths are unavailable, go to *1-3. *1-3 Check whether the transmission link is operational. Handle the transmission link failure. 1. See 13.1 Checking the Transmission Link. 2. If the transmission link is unavailable, go to *1-4. 3. If the transmission link is available, go to *1-5. 1. If the data is transmitted over Ethernet, for example, through FE ports, see 13.3 Unavailable FE/GE Port. 2. If the data is transmitted over a private line, for example, over E1/T1 cable, see 13.2 Unavailable E1/T1 Port. Run the MML command LST IPPATH to check whether the negotiated data is consistent. If inconsistency exists, modify the negotiated data. Run the MML command DSP IPRT to check the real-time IP route information.
*1-2
*1-4
*1-5
Check the configuration of the IP path. Check the realtime IP route information.
*1-6
13.5 Data Loading Failure on the Board

This describes how to handle the failures that occur during data loading to the BSC6900 board.
Symptoms
The status of the board on the device panel is abnormal when the BSC6900 board software and data files are being loaded to the BSC6900 boards.
Solutions
1. Check the board status of other boards of the same type in this subrack.
Issue 01 (2009-07-30)
13-5
13 FAQ
If... Board status of other boards of the same type is Normal, Board status of other boards of the same type is Faulty, 2.
Then... Replace the faulty board and then reload the data to the new board. Go to 2.
Check whether the DIP switch on the subrack is set as configured. If... The DIP switch on the subrack is not set as configured, The DIP switch on the subrack is set as configured, Then... Correct the DIP switch setting and then reload the data to the board. Go to 3.
3.
Check whether the internal subnet mask of the OMUa board is 255.0.0.0 and whether the two internal IP addresses are *.168.3.50 and *.168.3.40. If... No Yes Then... Correct the internal subnet mask and internal IP address and then reload the data to the board. Go to 4.
4.
If data loading on the DPU boards in the EPS fails, check whether the SCUa boards in the MPS and that in the EPS are properly connected. If... The connection is improper, The connection is proper, Then... Correct the connection, and then reload the data to the board. Go to 5.
5.
Run the MML command LST SUBRACK to check whether the type of the faulty board is properly set. If... The type of the board is incorrectly set, The type of the board is correctly set, Then... Correct the board type and then reload the data to the board. Go to 6.
6.
If the data loading on the DPUc board in the remote TCS fails, run the MML command DSP ATEROML to check whether the OML on the Ater interface is functional, and then run the MML command DSP E1T1 to check whether the physical link between the Ater interface boards is functional.
13-6
13 FAQ
If... The OML is faulty, and the physical link is functional,
Then... 1. Check whether the configuration is consistent with the physical OML connection. If they are inconsistent, modify the configuration according to the physical OML connection. 2. Check whether the cross connection exists in the physical OML. If yes, correct the physical connection of the OML, and then reload the data to the board.
The OML is faulty, and the physical link is also faulty, The OML is functional, 7.
Correct the connection, and then reload the data to the board. Go to 7.
Check whether any alarm related to board fault is present in the Alarm tab page. If... Alarms related to board fault exist, No alarm related to board fault exists, Then... Analyze the alarm information and accordingly clear the alarm. Go to 8.
8.
Contact the Huawei Customer Service Center.
13.6 Performing the Loopback Test on the E1/T1 Port

This describes how to perform the loopback test to check whether the E1/T1 port is functional.
Prerequisite
Context
l l l
The loopback test and the Bit Error Rate (BER) test cannot be performed simultaneously. The loopback test leads to temporary interruption of services carried over this link. The loopback test can be performed when the E1/T1 port is unavailable.
Procedure
Step 1 Perform the loopback test on the local E1/T1 port.
Issue 01 (2009-07-30)
13-7
13 FAQ
Table 13-3 Procedure for performing the loopback test on the local E1/T1 port Step 1-1 1-2 1-3 1-4 Action Run the MML command SET E1T1LOP. Set Loop type to LOCAL_LOOP(Local loop). Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port. Run the MML command DSP E1T1LOP to query the result of the loopback test. Run the MML command SET E1T1LOP, and then set Loop type to NO_LOOP (No loop) to stop the loopback test on the E1/T1 port.
If... If the loopback test result is Succeeded, If the loopback test result is Not succeeded,
Then... The E1/T1 port is operational. Go to Step 2. The E1/T1 port is faulty. Replace the interface board carrying the faulty E1/T1 port.
Step 2 Perform the loopback test on the local E1/T1 cable. Table 13-4 Procedure for performing the loopback test on the local E1/T1 cable Step 2-1 2-2 2-3 2-4 Action Perform E1/T1 physical loopback at the local end, that is, connect the TX end of the E1/T1 cable to the RX end of the E1/T1 cable. Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port. Run the MML command DSP E1T1LOP to query the result of the loopback test. Stop the E1/T1 physical loopback at the local end.
If... If the loopback test result is Succeeded,
Then... The local E1/T1 cable is operational. Go to Step 3.
13-8
Issue 01 (2009-07-30)
13 FAQ
If... If the loopback test result is Not succeeded,
Then...
l
Use a multimeter to measure the connectivity between the connector pin of the E1/T1 cable and the inner conductor of the coaxial cable and that between the outer shell of the connector and the shielding layer of the coaxial cable. If a connectivity failure occurs, make a new connector and assemble the cable again. Use a multimeter to check whether the internal and external conductors of the E1/T1 cable are shortcircuited. If so, make a new connector and assemble the cable again.
If the fault persists, replace the E1/T1 cable with a new one.
Step 3 Perform the loopback test on the peer E1/T1 port. Table 13-5 Procedure for checking the peer equipment or the transport network Step 3-1 3-2 3-3 3-4 Action Run the MML command SET E1T1LOP. Set Loop type to REMOTE_LOOP (Remote loop). Run the MML command LOP E1T1 at the peer end to start the loopback test on the E1/T1 port. Run the MML command DSP E1T1LOP at the peer end to query the result of the loopback test. Run the MML command SET E1T1LOP at the peer end, and then set Loop type to NO_LOOP(No loop) to stop the loopback test on the E1/T1 port.
If... If the loopback test result is Succeeded, If the loopback test result is Not succeeded,
Then... Go to Step 4. Contact the maintenance personnel for the peer equipment to rectify faults in the peer equipment or the transport network.
Step 4 If the E1/T1 for loopback belongs to an IMA group, then run the MML command RST IMAGRP. Click OK on the displayed dialog box to reset that IMA group. ----End
Issue 01 (2009-07-30)
13-9
13 FAQ
13.7 Performing the Loopback Test on the Optical Port

This describes how to perform the group loopback test to check whether the optical port is functional.
Prerequisite
Context
The loopback test can be performed on optical port when the E1/T1 transmission link on the standard interface is unavailable.
Procedure
Step 1 Perform the loopback test on the local optical port. Table 13-6 Procedure for performing the loopback test on the SDH port Step 1-1 1-2 1-3 Action Run the MML command SET OPTLOP, and then set Loop type to LOCAL_LOOP(LOCAL_LOOP). Run the MML command DSP OPT to query the result of the loopback. Run the MML command SET E1T1LOP, and then set Loop type to NO_LOOP (NO_LOOP) to stop the loopback test on the optical port.
If... The values of Optical port state in the result are Available, The values of Optical port state in the result are Fault,
Then... The SDH port is operational. Go to Step 2. The SDH port is faulty. Replace the interface board carrying the faulty SDH port.
Step 2 Perform the loopback test on the local fiber. Table 13-7 Procedure for performing the loopback test on the local fiber Step 2-1 2-2 2-3
13-10
Action Perform fiber physical loopback at the local end, that is, connect the TX end of the fiber to the RX end of the fiber. Run the MML command DSP OPT to query the result of the loopback. Stop the fiber physical loopback at the local end.
13 FAQ
Then... The local fiber is operational. Go to Step 3. The local fiber is faulty. Replace the faulty fiber.
Step 3 Perform the loopback test on the peer optical port. Table 13-8 Procedure for performing the loopback test on the peer optical port Step 3-1 3-2 3-3 Action Run the MML command SET OPTLOP, and then set Loop type to REMOTE_LOOP(REMOTE_LOOP). Run the MML command DSP OPT at the peer end to query the result of the loopback. Run the MML command SET E1T1LOP at the peer end, and then set Loop type to NO_LOOP(NO_LOOP) to stop the loopback test on the optical port.
Then... Contact the Huawei Customer Service Center. Contact the maintenance personnel for the peer equipment to rectify faults in the peer equipment or the transport network.
----End
Issue 01 (2009-07-30)
13-11
14 Appendix
14
About This Chapter
14.1 Communication Ports Used by the BSC6900 This provides communication ports used by the BSC6900.
Appendix
This provides the communication ports and the commissioning checklist of the BSC6900.
14.2 BSC6900 Commissioning Checklist BSC6900 commissioning checklist is for recording and checking the result of BSC6900 commissioning.
Issue 01 (2009-07-30)
14-1
14 Appendix
14.1 Communication Ports Used by the BSC6900

This provides communication ports used by the BSC6900. Table 14-1 lists the number of the communication ports used by the services of the BSC6900. Table 14-1 Communication ports used by the services of the BSC6900 Protoc ol Side A Side A Ports (Liste ning) 20 Side B Side B Ports (Lau nch) 10246553 5 Service Authenti cation
TCP
OMU
BSC6900 Host, LMT, M2000 Server BSC6900 Host, LMT, M2000 Server OMU
For FTP data. FAM Load, software and log upload/ download (active mode)
username/ password
TCP
OMU
21
10246553 5
For FTP control. FAM Load, software and log upload/download
username/ password
TCP
LMT
21
10246553 5 10246553 5 10246553 5 10246553 5 10246553 5 10246553 5 80
For FTP control, this port for OMU Exchange, communication with FAM the port is used by MSTSC, to maintain OMU MML, For Maintain
username/ password IP Address
TCP
OMU
1500
BSC6900 Host Remote Desktop LMT, M2000 Server LMT, M2000 Server LMT, M2000 Server LMT computer
TCP
OMU
3389
username/ password username/ password username/ password username/ password username/ password
TCP/ SSL TCP/ SSL TCP/ SSL TCP
OMU
6000/8 000 6001/8 001 6006/8 006 80
OMU
MML, For Alarm
OMU
LMT, For Maintain
LMT
For LMT Web browsing
14-2
Issue 01 (2009-07-30)
14 Appendix
Protoc ol
Side A
Side A Ports (Liste ning) 6022/8 022 6088
Side B
Side B Ports (Lau nch) 10246553 5 10246553 5 10246553 5 10246553 5 10246553 5 10246553 5 10246553 5 10246553 5
Service
Authenti cation
TCP/ SSL TCP
OMU
Equipmen t debug console Upgrade tool Test validation M2000 Server LMT
MML, for equipment debug console For Upgrade tool
None
OMU
None
TCP/ SSL TCP/ SSL TCP/ SSL TCP/ SSL TCP
OMU
6093/8 093 6099/8 099 6100/8 100 16002/ 18002 3306
MML, Emluator operate
None
OMU
MML, data synchronization with M2000 MML, Alarm Box
None
OMU
None
OMU
M2000 Server Peer OMU
MML, notification message from performance and M2000 MySQL
None
MySQ L BTS
username/ password None
TCP
700
SMT
For local maintenance, SMT(Station Management), it will be used before GBTS connect in the network Putty terminal tool port (SSH) Samba service port
TCP
OMU
22
SSH Client Samba Client BSC6900 Host OMU
10246553 5 10246553 5 10246553 5 10246553 5
username/ password username/ password None
TCP
OMU
139/44 5 67
UDP
OMU
Load, Bootp Listen
UDP
OMU
123
NTP Server,slow time synchronization, local listening port
None
Issue 01 (2009-07-30)
14-3
14 Appendix
Protoc ol
Side A
Side A Ports (Liste ning) 1234
Side B
Side B Ports (Lau nch) 10246553 5 10246553 5 10246553 5 10246553 5 123
Service
Authenti cation
UDP
OMU
BSC6900 Host Peer OMU
NTP, time synchronization with FAM, local listening port SecurityManager, for dual OMU SecurityManager, for dual OMU SecurityManager, backup tunnel between dual OMU NTPClient, time synchronization with time's server, local listening port
None
UDP
OMU
11774
None
UDP
OMU
11775
Peer OMU
None
UDP
OMU
11776
Peer OMU
None
UDP
M200 0 Server
123
OMU
None
14.2 BSC6900 Commissioning Checklist

BSC6900 commissioning checklist is for recording and checking the result of BSC6900 commissioning. BSC6900 Commissioning Checklist.
14-4
Issue 01 (2009-07-30)

BSC6900 GSM Commissioning Guide (V900R011C00 - 01)

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

BSC6900 GSM Commissioning Guide (V900R011C00 - 01)

Uploaded by

Copyright:

Available Formats

BSC6900 GSM V900R011C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.