Professional Documents
Culture Documents
V900R019C10
Commissioning Guide
Issue 01
Date 2017-03-08
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Overview
BSC6900 commissioning is performed after hardware is installed and before services are
provided. It aims to ensure that the BSC6900 can work properly by performing verification
tasks related to equipment, board software and data file loading, interfaces, and services.
Product Versions
The following table lists the product version and solution version related to this document.
Intended Audience
This document is intended for:
l Field engineers
Organization
1 Change History
This section provides information about the changes in different document versions. There are
two types of changes, including technical changes and editorial changes. Technical changes
refer to changes in functions of a specific product version. Editorial changes refer to changes
in wording or addition of information that was not described in the earlier version.
2 Commissioning Prerequisites
Before BSC6900 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages,
licenses, and MML scripts required for commissioning must be ready.
3 Commissioning Process
The BSC6900 commissioning can be performed remotely, locally, or remotely with local
assistance.
4 Checking Operating Status of Hardware
Before commissioning the equipment, ensure that the BSC6900 cabinet is powered on and is
operating properly.
5 Commissioning the OMU
Before using the OMU for the first time, commission the OMU onsite to check the installation
of product software and the version of the product software, and configure the IP address,
mask, and computer name to ensure the normal communication between the BSC6900 and the
LMT or U2000.
6 Logging In to the BSC6900 Using the LMT
This chapter describes how to log in to the BSC6900 using the LMT and how to establish
communication between the LMT and BSC6900 to ensure successful BSC6900
commissioning using the LMT.
7 Updating the OMU Database
This chapter describes how to update configuration data in the OMU database by running
MML scripts.
8 Activating and Verifying the License
This section describes how to activate the license and verify the license configuration
information to enable service commissioning.
9 Loading BSC6900 Board Software and Data Files
This chapter describes how to load the BSC6900 board software and data files.
10 Connecting to the U2000
This section describes how to connect the BSC6900 to the U2000 for centralized
management.
11 Connecting to Operator's PKI System
This section describes how to connect the BSC6900 to operator's CA server so that the
BSC6900 can automatically manage its own digital certificates.
12 Setting the Connection Mode Between the U2000 and BSC6900 to SSL
The connection mode between the U2000 and BSC6900 must be set to Secure Socket Layer
(SSL) on the U2000 to ensure operation and maintenance (O&M) safety.
13 Verifying Interfaces
This section describes how to verify interfaces on the BSC6900 side using the LMT or
U2000. Select a verification method based on the onsite situation.
14 Handling the Alarms Generated During the Commissioning
This section describes how to handle the alarms generated during the commissioning to
prevent the alarms from affecting service verifications.
15 Verifying UMTS Services
This section describes how to verify that the basic UMTS services and the feature services are
normal. The basic UMTS services are speech services and data services. Feature services
include inter-RAT handovers, HSDPA, HSUPA, 64QAM, MIMO, CBS, and DC-HSDPA.
The network reliability can be verified by checking generated alarms and making dialing tests
after a switchover between the active/standby boards.
17 Troubleshooting
This chapter describes how to troubleshoot common problems during the commissioning.
18 Appendix
This chapter provides communication ports on and the commissioning checklist of the
BSC6900.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl
+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2 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 Description
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
18 Appendix................................................................................................................................... 113
18.1 Communication Ports on the BSC6900.................................................................................................................... 114
18.2 BSC6900 Commissioning Checklist........................................................................................................................ 114
1 Change History
This section provides information about the changes in different document versions. There are
two types of changes, including technical changes and editorial changes. Technical changes
refer to changes in functions of a specific product version. Editorial changes refer to changes
in wording or addition of information that was not described in the earlier version.
01 (2017-03-08)
Compared with Issue Draft A (2016-12-31) of V900R019C10, this issue includes the
following changes.
Change Type Change Description
Deleted None
Editorial change BSC6900 communicates with the U2000 through a default route which
does not need to be configured. For details, see 10 Connecting to the
U2000.
Draft A (2016-12-30)
Compared with Issue 01 (2016-02-29) of V900R018C10, this issue does not include any
changes.
2 Commissioning Prerequisites
Before BSC6900 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages,
licenses, and MML scripts required for commissioning must be ready.
BSC6900 hardware The hardware is installed and has passed the hardware
installation check and power-on check.
l Three single-mode UEs and one dual-mode UE are ready for test and are registered with
the home location register (HLR).
3 Commissioning Process
The BSC6900 commissioning can be performed remotely, locally, or remotely with local
assistance.
l Local commissioning is performed by a field engineer (engineer responsible for onsite
commissioning in the BSC6900 equipment room) who connects a PC to the BSC6900
and performs the commissioning on the LMT.
l Remote commissioning is remotely performed by an engineer (technical engineer
responsible for the BSC6900) and multiple BSC6900s can be commissioned
simultaneously in the central equipment room.
l Remote commissioning with local assistance is performed remotely by an engineer with
the assistance of a field engineer.
Before commissioning the equipment, ensure that the BSC6900 cabinet is powered on and is
operating properly.
Prerequisites
The BSC6900 cabinet has passed the power-on check.
Procedure
Step 1 Check whether the cabinet is powered on.
If... Then...
Step 2 Turn on the power switches that control cabinet power supply on the power distribution frame
(PDF).
Step 3 Turn on the power switches on the power distribution box after the RUN indicator on the front
panel of the power distribution box blinks 0.25s on and 0.25s off.
If... Then...
The cabinet is an MPR Set the corresponding power switches on the power
distribution box to ON.
If the cabinet is an Set the power switches that correspond to the subracks
EPR/TCR configured in the same cabinet to ON.
Step 4 Check the power supply to the cabinet components, as listed in Table 4-1. Ensure that the
hardware operates properly.
Board The RUN indicator on the board panel is neither steady on nor
steady off.
Fan box The RUN indicator on the fan box panel blinks 1s on and 1s
off in green after the subrack or independent fan subrack is
powered on.
Power distribution The RUN indicator on the board panel blinks 1s on and 1s off
monitor board in green. The ALM indicator is steady off.
NOTE
If a power failure occurs, resolve the problem following the operations provided in step 5 in section Powering
On the Cabinet in BSC6900 UMTS Site Maintenance Guide.
----End
Before using the OMU for the first time, commission the OMU onsite to check the installation
of product software and the version of the product software, and configure the IP address,
mask, and computer name to ensure the normal communication between the BSC6900 and the
LMT or U2000.
Context
The OMU can be commissioned locally or by using a USB flash drive. In new network
deployment, the OMU board has been preinstalled with the operating system and applications
before delivery. Therefore, it is recommended that the OMU board be commissioned locally.
NOTE
For the definitions of "fixed external IP address", "virtual external IP address", "fixed internal IP address",
"virtual internal IP address", "IP address of the backup channel between the active and standby OMU
boards", and "commissioning IP address", refer to OMU IP Address Plan of "Working Principles" in
BSC6900 OMU Administration Guide.
Prerequisites
l The OMU is connected to a local PC using a commissioning Ethernet port.
l The version installation package or patch installation package that you have obtained is
the same as the customer version.
l You have obtained the psftp software and the PuTTY software. For details, see Obtaining
and Using the psftp Software and Obtaining and Using the PuTTY Software.
Context
l If the product software has been installed before delivery, the active workspace of the
OMU is version_a.
l If the product software is not installed before delivery, plan items in Information Records
of OMU Software Installation before installing the product software.
l For details about the OMU software factory settings, see Checklist for the OMU
Software Factory Settings.
For details about how to commission the OMU locally, see Figure 5-1.
Procedure
Step 1 Connect a PC to the OMU board.
1. Connect the PC to the ETH2 commissioning port on the OMU board using a network
cable.
2. Set the IP addresses of the PC and ETH2 port so that they are in the same network
segment.
The initial IP address of the ETH2 port is 192.168.6.50 or 192.168.6.60, and the subnet
mask is 255.255.255.0. The initial IP address of the ETH2 port is the commissioning IP
address. For details about the commissioning IP address, see OMU IP Address Plan.
Step 2 Set the link mode of the external OMU Ethernet adapters.
1. Log in to the OMU by referring to the procedures described in Logging In to the OMU.
2. Check whether the link mode of the external OMU Ethernet adapters is consistent with
that of LAN switches.
For details about how to query the link mode of the external OMU Ethernet adapters, see
Querying the Link Mode of the External OMU Network Adapters.
If... Then...
The link mode of the external OMU Set the link mode of the external OMU
Ethernet adapters is inconsistent with that network adapters to be consistent with
of LAN switches that of LAN switch by referring to
operations in Procedure of Setting the
Link Mode for External OMU Ethernet
Adapters.
If... Then...
NOTE
Perform either of the following operations if a gateway IP address needs to be changed while
you are changing an external fixed IP address:
n Method 1: Enter ./omutool extercard The external fixed IP address The subnet mask
(The gateway IP address) to change the external fixed IP address and gateway IP address
at the same time. The following is an example:
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
n Method 2: Enter ./omutool gateway The gateway IP address to change the gateway IP
address separately. The following is an example:
./omutool gateway 10.161.10.1
After the external fixed IP address is changed, the OMU can be connected to the operation and
maintenance (OM) network of the operator over the ETH0 or ETH1 port. In this case,
subsequent commissioning tasks can be performed remotely.
3. Change the external virtual IP address and subnet mask of the active and standby OMUs
according to the plan. Ensure that the external virtual IP address is on the same network
segment as the external fixed IP address.
Enter ./omutool extervip The external virtual IP address The subnet mask to change the
external virtual IP address and subnet mask. For example, you can enter the following
command:
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
The external virtual, external fixed and gateway IP addresses must all be in the same network
segment. If you change either of the first two of these, you will be prompted to check whether the
other two addresses need to be changed to comply with this rule.
4. Check whether the internal fixed IP address, internal virtual IP address, backup channel
IP address, and commissioning IP address of active and standby OMUs are in the same
network segment as the operator's network.
If... Then...
If... Then...
The preceding IP addresses are Change the backup channel IP address of the
not in the same network standby OMU.
segment as the operator's If OMUa boards are used, enter ./omutool
network backupcard The IP address. For example, you
can enter the following command:
./omutool backupcard 192.168.3.60
Step 5 Enter ./omutool dispipinfo to check whether the modified OMU IP address and subnet mask
are correct based on the query result.
NOTE
The OMU name cannot contain control characters, spaces, or any of the following special characters: / \
[ ] ( ) ' : | < > + = ; , ?, and the length of the OMU name must range from 1 to 62 characters.
NOTE
If some of the preceding processes do not exist, enter /etc/rc.d/omud restart to restart the OMU
server, and then check whether the processes exist. If some of them still do not exist, uninstall the
product software and then reinstall it in the active workspace by referring to operations in
Procedure of Uninstalling the Product Software and Installing the Product Software in the Active
Workspace.
Step 9 Enter exit to stop the PuTTY and then remove the cable to disconnect the PC from the OMU.
----End
Prerequisites
l The preparations for installing software on site are completed. For details, see Onsite
Software Installation Preparations.
l You have obtained the planned OMU information and recorded them in Configuration
Information for Preparing the USB Flash Drive.
l The capacity of the USB flash drive is at least 4 GB. If the BSC6900 is configured with
active and standby OMUs, two USB flash drives are required.
l A USB flash drive has been inserted into an available and uncontrolled (for example,
CPM control) USB port on a portable computer
l Check whether the USB flash drive is usable by referring to the USB Flash Drive
Verification Guide under the USB Disk Tool (a tool used for preparing the USB flash
drive) directory. If the USB flash drive cannot be used, replace it with another one. The
Netac U208 (4 GB), Kingston and Sandisk USB storage devices are recommended.
Context
NOTICE
Back up the OMU data before you install the OMU operating system and product software.
This is because the OMU hard disk will be formatted during the installation of the OMU
operating system and product software using the USB flash drive, and all data will be deleted.
l This section uses the commissioning of active and standby OMUs as an example. The
commissioning operation differences between the OMU in independent mode and the
OMUs in active/standby mode are described separately.
l Commissioning an OMU using a USB flash drive involves two steps: preparing the USB
flash drive and commissioning the OMU after inserting the USB flash drive into the
OMU.
Figure 5-2 Flowchart for commissioning the OMU using a USB flash drive
Procedure
Step 1 Prepare a USB flash drive.
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system on
the USB flash drive, as shown in Figure 5-3.
2. Right-click NE List in the left pane of the window shown in Figure 5-3 and choose Add
NE from the shortcut menu. A dialog box is displayed, as shown in Figure 5-4.
3. Specify NE Name, set Operating System Type to DopraLinux, set Operate type to
Install. Then click OK. An NE is added.
NOTE
If only the operating system is to be installed on the OMU, do not select Install product software?.
If the operating system and product software are to be installed on the OMU, select Install product
software? and specify External Virtual IP Address of the NE to be added.
If only the product software is to be installed on the OMU, set Operate type to Only install
product software, and specify External Virtual IP Address of the NE to be added.
The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
The NE name and the virtual external IP address can be changed only after you delete the NE and
then add it again.
If you want to prepare multiple USB flash drives, you are advised to prepare and label the USB
flash drives one by one.
4. Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 5-5.
NOTE
The IP addresses shown in Figure 5-5 are required by the U_creator tool by default. Change the IP
addresses as required. For details about the principles of changing the IP addresses, see OMU IP
Address Plan.
Select the link mode for external Ethernet adapters listed in Figure 5-5 as required. Ensure that the
link mode for external Ethernet adapters is consistent with that for the onsite LAN switch. Table
5-1 lists the mapping between the queried link mode for external Ethernet adapters and that selected
in Figure 5-5.
In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
The new password policy is as follows:
n Passwords of admin must contain 8 to 32 characters.
n The characters must be uppercase letters, lowercase letters, digits, or special characters, or the
combination of two among these types.
n Special characters include spaces and the following characters ~!@#$^*()_+-{}|[]:./
n Modify Debug network IP and Debug network mask based on actual conditions.
On the interface described in Figure 5-5, under Please select the initial configuration data file,
import an initial configuration data file exported using a non-encryption method, and ensure that the
file data is consistent with that on Figure 5-5. The data includes the product type, version, patch
version, run mode of OMU, and language of OMU.
On the interface described in Figure 5-5, if Data encryption is selected, fill in the E-Label of the
target OMU. To obtain the E-Label of an OMU, you can manually query the OMU board bar code
label. Alternatively, you can run the DSP OMU command to view the current OMU active/standby
status and then query the value of the BarCode parameter in the DSP ELABEL command.
5. After all the information is automatically obtained, check whether the information is
correct and enter the required information.
NOTE
If a version or baseline patch is to be installed, select the V**R**C** directory of the version
installation package or the V**R**C**SPCX00 directory for the baseline patch installation
package.
If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or V**R**C**SPHXYZ
directory for the patch installation package.
6. Check that all the information is correct and click OK. In the displayed dialog box,
check the directory where the USB flash drive is located and start preparing a USB flash
drive.
7. Perform operations by following the instructions until the system displays a message that
reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB flash drive.
NOTE
If the system asks for your confirmation during preparation of the USB flash drive, insert or remove
the USB flash drive.
If an independent OMU is configured, skip the steps for preparing the standby OMU USB flash
drive.
Step 2 Commission the OMU after inserting the USB flash drive to the OMU.
1. Insert the USB flash drive into any USB port on the OMU board panel.
2. Remove and then install the OMU board to reset it. For details, see sections Removing a
Board and Installing a board in the BSC6900 UMTS Site Maintenance Guide.
3. Observe the status of the indicators on the OMU board panel and determine whether the
installation is complete.
If... Check the indicator status
NOTE
If the status of the indicators differs from this, the OMU cannot identify the USB flash device.
In this case, prepare another USB flash device. Alternatively, copy the data in the original
USB flash device to a new one, and then reinstall the OMU operating system.
After the OMU operating system and the product software are installed successfully, remove
the USB flash drive from the OMU board panel. The OMU commissioning is complete. If the
value of operation type is Only install product software, you need to remove and reinsert
the OMU to restart the OMU operating system after removing the USB flash drive.
Table 5-2 Status of the indicators on the OMUa or OMUc board panel during the OMU
operating system installation
Board Installation Successful Failed Installation
Procedure Installation
OMUc The RUN indicator The RUN indicator The RUN indicator
blinks. blinks. is off.
The ALM indicator The ALM indicator The ALM indicator
blinks. is off. blinks.
The ACT indicator The ACT indicator The ACT indicator
blinks. is off. is off.
The OFFLINE The OFFLINE The OFFLINE
indicator is off. indicator blinks. indicator blinks.
Table 5-3 Status of the indicators on the OMUa or OMUc board panel during the OMU
operating system and product software installation
Board Installation Successful Failed Installation
Procedure Installation
OMUc The RUN indicator The RUN indicator The RUN indicator
blinks. blinks. blinks.
The ALM indicator The ALM indicator The ALM indicator
blinks. is steady on or off. blinks.
The ACT indicator The ACT indicator The ACT indicator
blinks. is steady on or off. is off.
The OFFLINE The OFFLINE The OFFLINE
indicator is off. indicator is off. indicator is off.
Table 5-4 Status of the indicators on the OMUa or OMUc board panel during only the
product software installation
Board Installation Successful Failed Installation
Procedure Installation
OMUc The RUN indicator The RUN indicator The RUN indicator
blinks. blinks. blinks.
The ALM indicator The ALM indicator The ALM indicator
is off. is steady on or off. blinks.
The ACT indicator The ACT indicator The ACT indicator
is off. is steady on or off. is off.
The OFFLINE The OFFLINE The OFFLINE
indicator is off. indicator is off. indicator is off.
----End
Follow-up Procedure
Troubleshooting upon Installation Failures
Check whether the configuration files prepared in the step Prepare the USB flash drive are
correct according to the Configuration Information for Preparing the USB flash drive for
Installation recorded during the preparations.
l If the configuration files are not correct, prepare the USB flash drive again by referring
to the step Prepare the USB flash drive.
l If the configuration files are correct, contact Huawei technical support by referring to
Contact the Technical Support for Assistance.
Querying the Operating System Version Using the PuTTY
1. Double-click putty.exe. Enter the physical IP address of the OMU where an operating
system has been installed. An interface for logging in to the Linux operating system is
displayed. Enter an administrator-level user name and its password to log in to the OMU.
2. Execute /cat /etc/DL-Release to query the operating system version, as shown in Figure
5-6.
Figure 5-6 Querying the operating system version using the Putty
This chapter describes how to log in to the BSC6900 using the LMT and how to establish
communication between the LMT and BSC6900 to ensure successful BSC6900
commissioning using the LMT.
Prerequisites
l The OMU commissioning has been complete.
l The network connection between the LMT and the OMU has been established.
NOTE
In the case of the local OMU commissioning, a field engineer performs local commissioning tasks
and then Log in to the BSC6900 using the LMT to verify the connection between the OMU and
the external network. In this case, the field engineer needs to enter the IP address for OMU
commissioning in the address bar of Internet Explorer (IE) to log in to the LMT.
Context
JRE is a standard Java plug-in. If JRE is not installed, a message is displayed when you
attempt to log in to the LMT. In this case, install JRE by following the instructions in the
displayed prompt message. If the JRE installed in the PC is not of the latest version, a
message is displayed when you attempt to log in to the LMT, prompting you to update the
JRE. In this case, it is recommended that you uninstall the JRE and then install the JRE of the
latest version
CAUTION
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 met.
2. Check the security settings of the Internet Explorer and ensure that the Java script is
supported.
Step 2 Start the IE, and then log in to the BSC6900 using the LMT.
1. Start the IE and enter the external virtual IP address of the OMU of the BSC6900 on the
address bar. The login dialog box is displayed, as shown in Figure 6-1.
NOTE
To log in to the BSC6900 by using the Domain user account, establish the connection between the
BSC6900 and the U2000 server.
2. Enter User Name, Password, and Verify Code, and click Login to log in to the LMT.
----End
This chapter describes how to update configuration data in the OMU database by running
MML scripts.
Prerequisites
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l The MML command data scripts applicable to the local office are verified and the
contents are precise and complete.
Context
l There are two methods to run MML scripts: by running MML commands or using the
GUI. The MML script can be executed by using the GUI only when a script is smaller
than 4 MB. It is recommended that you run the MML script by running MML
commands, because it is more efficient.
l You can query the active workspace of the OMU through the MML command LST
OMUAREA. The following procedure assumes that the active workspace is version_a.
Procedure
l Run the MML script by running MML commands.
a. Run the MML command SET CFGDATAINEFFECTIVE to set the MPS to work
in ineffective mode.
NOTICE
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set each configured subrack to work in ineffective
mode.
b. Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize the BSC6900 configuration data in the OMU database.
c. Run the MML command UPD KEYMATERIAL to update the key material used
for local data encryption.
d. Upload the MML script to the /ftp folder in the OMU active workspace directory.
The following assumes that the MML script BATCHFILE.txt saved in disk D is
uploaded to the OMU active workspace /mbsc/bam/version_a/ftp to introduce the
two methods.
NOTE
Two methods are available: through File Manager on the LMT or through command lines.
n Through File Manager on the LMT
1) Click File Manager on the toolbar of the LMT to start the file manager.
2) In the displayed window, choose Root > bam > version_a > ftp on the
left and click Upload on the right. A dialog box is displayed. Select
BATCHFILE.txt saved in disk D, and then click Open to upload the file.
n Through command lines
1) On the local PC, choose Start > Run. Type cmd and click OK.
2) Input d: and press Enter to switch to disk D.
3) Input ftp IP address to connect to the OMU. Here, IP address is the IP
address of the OMU.
4) Input the LMT user name and password. The connection between the
OMU and the local FTP is set up after the authentication succeeds.
5) Input cd /mbsc/bam/version_a/ftp to switch to the OMU active
workspace.
6) Input put BATCHFILE.txt to upload the file.
7) After the file is uploaded successfully, input quit to disconnect the FTP.
e. Run the MML command RUN BATCHFILE to run the batch command file. It is
recommended that you set Finish Type to ANY_ERR_RETURN(Stop at Error),
Result Recording Type to REC_ERR(Record errors), Source File Name to
BATCHFILE.txt, and Result File Name to RUN_BATCHFILE_RESULT.txt.
NOTE
l The result file RUN_BATCHFILE_RESULT.txt is saved in the /ftp folder in the OMU
active workspace installation directory, that is, /mbsc/bam/version_a/ftp.
l The execution of the script takes a certain period of time. For example, 1-1.5 hours will
be needed for executing a script with 100,000 commands.
l If the MML script fails to be executed, open the RUN_BATCHFILE_RESULT.txt file
to check the commands that fail to be executed. Then, extract the commands that fail to
be executed and the commands that have not been executed to generate a new MML
script. Correct the MML script based on the displayed messages, and then go to e to run
the new script.
l Run the MML script by using the GUI.
a. Run the MML command SET CFGDATAINEFFECTIVE to set the MPS to work
in ineffective mode.
NOTICE
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set each configured subrack to work in ineffective
mode.
b. Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize the BSC6900 configuration data in the OMU database.
c. Run the MML command UPD KEYMATERIAL to update the key material used
for local data encryption.
d. On the LMT, click the Batch tab. The Batch tab page is displayed, as shown in
Figure 7-1.
e. Click Open....The Open dialog box is displayed. Select the prepared MML script,
and then click Open. The commands in the script are displayed on the Batch tab
page.
f. Click Set.... The Set dialog box is displayed. Set Sending Commands Interval(s)
to 0, select Save Failed Commands and set the path for saving the failed
commands, and then click OK, as shown in Figure 7-2.
g. On the Batch tab page, select All in the Execution Type area.
h. Click Go. The system runs the MML commands one by one.
NOTE
l Click OK when the system displays that the current configuration is in ineffective mode
after you click Go. The execution of the script will take a long time in GUI mode. For
example, 2-3 hours will be needed for executing a 4-MB script.
l If an Error dialog box showing Execution failed. Continue? is displayed during the
execution of the MML script, the MML script is incorrect. In this case, select Yes to All
to ignore the error prompt. After the MML script file is executed, extract the commands
that fail to be executed to generate a new MML script, correct the commands based on
the prompts, and then go to e to run the script again.
i. Click OK when a dialog box is displayed, indicating that the running of all the
MML commands is complete.
----End
Follow-up Procedure
After the OMU database is upgraded, perform the following operations to ensure the normal
communication between the OMU and BSC6900.
1. Run the MML command LST SUBNET to query the Subnet No. of the BSC6900.
2. Check whether the Subnet No. of the BSC6900 is consistent with the network segment
of the planned internal IP address of the OMU.
NOTE
The planned internal IP address of the OMU is recorded in Configuration Information for
Commissioning the OMU Locally.
If they are consistent, run the DSP OMU command to query the OMU internal
network segment and check whether the OMU internal network segment is
consistent with the network segment of the internal IP address of the OMU.
i. If they are consistent, perform 3.
ii. If they are inconsistent, run the RST OMU command with Reset Type set to
SOFT(Soft Reset) to reset the active and standby OMU boards.
If they are inconsistent, perform the following operations:
i. Run the MML command SET SUBNET to change the Subnet No. of the
BSC6900 so that it is consistent with the network segment of the planned
internal IP address of the OMU.
ii. Run the RST OMU command with Reset Type set to SOFT(Soft Reset) to
reset the active and standby OMU boards.
3. Run the MML command SET CFGDATAEFFECTIVE to set the MPS to work in
effective mode.
4. Locally remove the SCU board and then reinsert it into the MPS. Then, reset the MPS so
that the new IP address of the BSC6900 host takes effect.
This section describes how to activate the license and verify the license configuration
information to enable service commissioning.
Prerequisites
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l The FTP server is started. For details on how to start the FTP server, see the operations
in Startup in BSC6900 UMTS LMT User Guide for FTP Server. For the default user
name and password of the FTP server, see FTP Server in BSC6900 UMTS LMT User
Guide. Note that the user name or password may be modified.
l The license file is ready and the license check is passed.
Context
The active workspace of the OMU can be queried through the MML command LST
OMUAREA. The following operations assume that the active workspace is version_a.
Procedure
Step 1 Run the MML command DLD LICENSE to download the license to the OMU active
workspace directory /ftp/license, that is, /mbsc/bam/version_a/ftp/license/software/bam/
version_a/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 inconsistent with what you apply for Contact Huawei technical support.
Step 3 Run the MML command CHK DATA2LIC, and then set File Name to the name of the
license file to be activated to verify the license information including the equipment serial
number (ESN), version, working mode, and configuration.
If... Then...
The license information is inconsistent with the Modify the inconsistent data and then
OMU information repeat this step.
Step 4 Run the MML command ACT LICENSE to activate the license file.
Step 5 Optional: If there are the primary and secondary operators, run the MML command SET
LICENSE to reallocate the resources and functions in sequence from the primary operator to
the secondary operator. If there are multiple secondary operators, run the command for each
operator.
----End
Follow-up Procedure
If the license activation fails, 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, such as the product name, ESN, and version number of the
license is incorrect, apply for a new license.
l If the configuration data in the OMU database is incorrect, correct the configuration data,
and then reactivate the license.
NOTE
An invalid or expired license file can also lead to a license activation failure. For details, see the online
help of the MML command ACT LICENSE.
This chapter describes how to load the BSC6900 board software and data files.
Prerequisites
l The device has been commissioned.
l The OMU database has been updated.
Context
The software of the BSC6900 is generated automatically in the OMU active workspace
directory /bin/fam during the installation of the product software. For example, if the active
workspace is version_a, the software is in /mbsc/bam/version_a/bin/fam. 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 boards.
9.1 Generating Data Files for the Loading
This section describes how to generate data files, which can be loaded, using the MML data
scripts.
9.2 Setting the Board Loading Mode
This section describes how to set the loading modes of all the board subsystems before
resetting BSC6900 boards.
9.3 Resetting BSC6900 Boards
This section describes how to load the BSC6900 board software and data files from the OMU
installation directory to the boards and make them take effect.
9.4 Checking the Consistency of the Data and the Version
This section describes how to check whether the board configuration and the software version
of the BSC6900 are consistent with those on the OMU.
Prerequisites
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Run the MML command SET CFGDATAEFFECTIVE without specifying any parameter to
set the subracks configured to work in effective mode.
Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format active
area) to format the configuration data in the OMU database. Do not specify the subrack
number when running the MML command.
----End
Prerequisites
You have completed the operations provided in section 6 Logging In to the BSC6900 Using
the LMT.
Context
For details about the loading modes, see BSC6900 Loading Management.
Procedure
Step 1 Run the MML command SET LODCTRL to set the board loading mode. In this command,
set Board Start Load Control to LFB(Load from OMU and write flash).
----End
Prerequisites
l The data file for the loading has been generated.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l All the subracks have been powered on.
Context
The resetting time is less than or equal to six minutes in the maximum configuration. There is
no requirement for the sequence. All the subracks can be reset at the same time.
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 box 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.
Step 2 Repeat Step 1 to reset all the BSC6900 subracks.
NOTE
You can observe the loading process on the Progress tab page on the LMT home page. If this tab page is
hidden, click Progress in the toolbar on the LMT home page.
Step 3 Click the Device Maintenance tab on the LMT home page after all the subracks are reset.
The Device Maintenance tab page is displayed.
Step 4 Check whether all the boards on the device panel are in the normal state.
If... Then...
The device panel shows that all the boards No further action is required.
are in the normal state
The device panel shows that some boards Check the faulty boards and clear the alarms
are not in the normal state according to operations in 17.9 Data
Loading Failures on the Board.
----End
Prerequisites
l All the subracks and boards are running properly.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Run the MML command ACT CRC without specifying any parameter to check whether the
BSC6900 board configuration is consistent with the data on the OMU.
----End
Follow-up Procedure
After the consistency check, restore the loading method of the board: Run the MML
command SET LODCTRL to set Board Start Load Control to CL(Consult Load).
This section describes how to connect the BSC6900 to the U2000 for centralized
management.
Prerequisites
l The operation and maintenance (O&M) network has passed the commissioning. The
U2000 is operating properly.
l The version of the U2000 is compatible with that of the BSC6900.
l The mediation version of the U2000 is compatible with the NE version.
l If a firewall exists between the BSC6900 and U2000, enable the communication ports
connecting the BSC6900 and U2000 to ensure proper communication between the
BSC6900 and U2000.
Context
l If the BSC6900 and the U2000 are in the same network segment, you do not need to
configure an IP route to the BSC6900 to the U2000.
l If the BSC6900 and the U2000 are not in the same network segment and the BSC6900
can access the U2000 by using a default route, you do not need to configure an IP route
from the BSC6900 to the U2000. If the BSC6900 and the U2000 are not in the same
network segment and the BSC6900 cannot access the U2000 by using a default route,
you must configure an IP route from the BSC6900 to the U2000.
Procedure
Step 1 Connect the BSC6900 to the O&M network.
1. Connect one end of a straight-through cable to the ETH0 or ETH1 port on the OMU
board.
2. Connect the other end of the straight-through cable to the peer network device, such as a
hub or a router, to access the O&M network.
Step 2 Check whether the BSC6900 can access the U2000 by using a default route.
Log in to the target OMU and check whether the network connectivity between the BSC6900
and the U2000 is available running the ping command. For details about the how to log in to
the target OMU, see BSC6900 UMTS OMU Administration Guide for Logging In to the
OMU. If the OMU can receive a response packet from the U2000, go to Step 4. Otherwise, go
to Step 3.
Step 4 Create the BSC6900 on the U2000. For details, see the information about how to create an NE
in the U2000 documentation.
NOTICE
l If a firewall exists between the BSC6900 and U2000, enable the communication ports
connecting the BSC6900 and U2000 to ensure proper communication between the
BSC6900 and U2000.
l For details on the ports connecting the BSC6900 and U2000, see 18.1 Communication
Ports on the BSC6900.
l The MTU value configured for the transmission equipment between the BSC6900 and the
U2000 must be no less than that configured for the OMU board of the BSC6900.
Otherwise, the communication between the BSC6900 and the U2000 may be abnormal.
The default MTU value for the OMU board is 1500.
l You are advised to run the SET CONNTYPE command with Connection Type set to
ONLY_SSL(Only SSL Connection) to enhance network transmission security.
----End
Example
Table 10-1 describes how to configure a route between the BSC6900 and the U2000.
Follow-up Procedure
If the CME method is used to configure the data, it is necessary to complete the configuration
through the U2000.
This section describes how to connect the BSC6900 to operator's CA server so that the
BSC6900 can automatically manage its own digital certificates.
Prerequisites
l The operator has the public key infrastructure (PKI) system.
l The route from the operator's PKI system to the external IP address is available.
l You have completed the operations provided in section 10 Connecting to the U2000.
l The OMU board must be configured with an identification-capable device certificate so
that the base station controller can connect to the operator's PKI system for automatic
digital certificate management.
l Operators have purchased licenses for feature WRFD-160276 RNC Supporting PKI.
Procedure
Step 1 Configure Huawei root certificate as the trust certificate on the operator's CA server. If the
operator's CA server works in the active/standby mode, configure Huawei root certificate as
the trust certificate on both the active and standby CA servers.
Step 2 Check whether the base station controller has the identification-capable device certificate.
1. Run the MML command LST APPCERT to query information about the device
certificate of the base station controller.
If Certificate File Name is usercert.pem in the command output, the device
certificate is pre-installed by Huawei.
If Certificate File Name is hwusercert.pem in the command output, the device
certificate is pre-installed by Huawei and bound to the ESN of the OMU board. Go
to Step 4.
If Certificate File Name is any other value in the command output, go to Step 2.2.
If the command output displays no information about the device certificate, go to
Step 3.
2. Run the MML command DSP APPCERT to check whether the device certificate is
issued by the operator's CA server.
If the device certificate is issued by the operator's CA server, the device certificate
is unique. Go to Step 5.
If the device certificate is not issued by the operator's CA server, the device
certificate is issued by other CA server. Go to Step 4.
Step 3 Apply for the certificate issued by the operator's CA server on the U2000.
1. Run the following MML commands to install the certificate files required by the
BSC6900:
Run the MML command MOD CERTREQ to configure the certificate request
template.
Run the MML command CRE CERTREQFILE to generate a certificate request
file.
To apply for a digital certificate, run the MML command ULD CERTFILE to
download the local digital certificate from the CA center according to the local
certificate quest file that is sent to the CA center. You can also copy the digital
certificate from the CA center using a USB flash drive.
2. Apply for the device certificate from the operator's CA server on the U2000. In this step,
the U2000 manually submits a certificate update request file to the operator's CA server
to apply for the operator's device certificate and the operator's CA server manually sends
the operator's device certificate to the U2000.
3. Run the MML command DLD CERTFILE to download the operator-issued trust
certificate from the U2000.
4. Run the MML command ADD TRUSTCERT to add the trust certificate issued by the
operator's CA server.
5. Run the MML command DLD CERTFILE to download the device certificate from the
U2000.
6. Run the MML command ADD CERTMK to add the device certificate to the base
station controller.
7. On the U2000, choose Security > Certificate Authentication Management >
Certificate Management. On the displayed Certificate Management tab page, select
the obtained operator certificate and click Tset to check whether an SSL connection to
the U2000 can be successfully set up using the certificate.
8. Run the MML command MOD APPCERT to configure the certificate.
9. Go to Step 5.
Step 4 The base station controller applies for the device certificate from the operator's CA server.
1. Run the MML command MOD CERTREQ to configure the certificate request template.
2. Run the MML command ADD CA to add configurations of the operator's CA server. If
the operator's CA server works in the active/standby mode, add configurations of both
the active and standby CA servers to CA information to guarantee reliability in
certificate application and update.
3. Run the MML command REQ DEVCERT to apply for the certificate issued by the
operator's CA server.
4. On the U2000, choose Security > Certificate Authentication Management >
Certificate Management. On the displayed Certificate Management tab page, select
the obtained operator certificate and click Tsetto check whether an SSL connection to the
U2000 can be successfully set up using the certificate.
5. Run the MML command MOD APPCERT to configure the certificate.
6. Go to Step 5.
Step 5 Start the base station controller device certificate automatic check task to automatically
update the certificate.
1. Run the MML command SET CERTCHKTSK to set a periodic certificate validity
checking task.
2. Optional: Run the MML command DLD CERTFILE to download the operator's CRL
certificate from the certificate and CRL storage device of the operator.
3. Optional: Run the MML command ADD CRL to set CRL information.
4. Optional: Run the MML command SET CRLPOLICY to set the CRL policy.
5. Optional: Run the MML command ADD CRLTSK to set a periodic CRL downloading
task.
NOTE
The current base station controller supports only the LDAPv3 protocol. Therefore, if the CRL is
updated using the LDAP, ensure that the CRL server supports the LDAPv3 protocol.
----End
The connection mode between the U2000 and BSC6900 must be set to Secure Socket Layer
(SSL) on the U2000 to ensure operation and maintenance (O&M) safety.
Prerequisites
l The BSC6900 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l You have completed the operations provided in section 10 Connecting to the U2000.
l One of the following conditions must be met:
You have applied for an SSL safety certificate from the Certificate Authority (CA).
You have accessed the operator's PKI system.
You directly use Huawei pre-installed digital certificate.
Procedure
Step 1 If you have applied for an SSL safety certificate from the CA but do not access the operator's
PKI system or use Huawei pre-installed digital certificate, import and activate the obtained
certificate on the U2000.
1. Import a CA certificate to the BSC6900. For details about how to import a CA
certificate, see section "Importing CA Certificates" in U2000 Data Management User
Guide under U2000 Product Documentation.
2. Install a device certificate on the BSC6900. For details about how to install a device
certificate, see section "Manually Installing a Device Certificate" in U2000 Data
Management User Guide under U2000 Product Documentation.
Step 2 Set the connection mode between the U2000 and BSC6900 to SSL.
1. On the U2000 client, choose Security Management > NE Security > Certificate
Authentication Management > SSL Connection Management (application style) or
Security > Certificate Authentication Management > SSL Connection Management
(traditional style).
----End
13 Verifying Interfaces
This section describes how to verify interfaces on the BSC6900 side using the LMT or
U2000. Select a verification method based on the onsite situation.
Prerequisites
l The BSC6900 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 10 Connecting to the U2000.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Context
l An NE can work in the following engineering modes: NORMAL, INSTALL,
EXPAND, UPGRADE, and TESTING. The NE mode of the BSC6900 must be set to
TESTING in commissioning scenarios.
NOTE
For details about engineering modes, see section "Introduction to the Maintenance Mode
Management Feature" in U2000 Product Documentation.
l The NE engineering mode is valid only during the time specified by Start Time and
End Time. Before Start Time and after End Time, the NE mode changes to
NORMAL. Alarms are reported when the NE works in NORMAL mode.
l When the NE engineering mode changes to the NORMAL mode, the alarms that are not
cleared in TESTING mode are reported as common alarms to the U2000.
Procedure
l Setting the NE engineering mode by using the GUI on the U2000 client
a. On the U2000 client, choose System Settings > Task Schedule > Maintenance
Mode (application styles) or Maintenance > Maintenance Mode (traditional
styles).
l Setting the NE engineering mode by running MML commands on the U2000 or LMT
a. On the U2000 client or LMT, run the MML command SET MNTMODE. In this
command, set Maintenance Mode to TESTING(TESTING), Start Time and End
Time to values based on onsite requirements.
----End
Follow-up Procedure
After the preceding operations, all the alarms and events reported during Start Time and End
Time will not be shown in the U2000 Alarm and Event Log for the NE by default. You can
check the alarms and events reported when the NE works in TESTING mode by setting the
filtering conditions. For details, see U2000 Operator Guide.
Prerequisites
l The BSC6900 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in chapter 10 Connecting to the U2000.
Context
The internal interface must be verified by using MML commands on the LMT. For details, see
13.2.2 Verifying Internal Interfaces.
Procedure
Step 1 Specify a scenario for an NE health check.
1. On the U2000 client, choose Trace and Maintenance > Monitor > NE Health Check
(application styles) or Maintenance > Network Health Check > NE Health Check
(traditional styles).
2. Click on the displayed tab page. The Scenario Management dialog box is
displayed.
3. Click New in the displayed dialog box.
4. Enter the scenario name in the Scenario Name text box on the right of the dialog box.
NOTE
1. On the NE Health Check tab page, click the . The Create Task dialog box is
displayed.
2. Select an application scenario from the Scenario drop-down list. The application
scenario must be suitable for the newly created task. The application scenario and the
specific time (the time is accurate to the second) on which the task is created are
automatically displayed in the Task Name text box.
3. Select the NE for health check in the Select NE. area.
4. In the Time Setting area, select the task execution mode. The following table lists the
options. Click Finish to select the instant execution mode.
Option Description
Scheduled execution Set the time for executing the task in the
Scheduled spin box. Click Next. Set
Health Check Period in the displayed
dialog box, and then click Finish.
NOTE
The executed health check tasks are listed under the Finished Tasks node in the navigation tree on the
left side.
If... Then...
You select the HTML format Select the report from the report list, and then view
the report in one of the following ways:
Click the report to directly open the report in
HTML format. Click Open to open the report in
the HTML format.
Click Save As, and then select the path for
saving the report in the displayed Save dialog
box to save the report in HTML format.
You select the DOC format Click Save As, and then select the path for saving
the report in the displayed Save dialog box to save
the report in DOC format.
NOTE
The health check report is compressed to a .zip file. To view the report, double-click the .zip file,
and then double-click the report file index.html in the .zip file browser.
If some items in the health check report are in red, the corresponding interface is faulty. Rectify
the fault according to the health check report.
----End
Prerequisites
l You have completed the operations provided in section 10 Connecting to the U2000.
l You have completed the operations provided in section 13.1.1 Setting the NE
Engineering Mode to TESTING before interface verification.
l The BSC6900 has passed the commissioning.
Procedure
l Setting the NE engineering mode by using the GUI on the U2000 client
a. On the U2000 client, choose Configuration > Settings > Maintenance Mode
(application style) or Maintenance > Maintenance Mode (traditional style).
l Setting the NE engineering mode by running MML commands on the U2000 or LMT
a. On the U2000 or the LMT client, run the MML command SET MNTMODE, and
set Maintenance Mode to NORMAL(NORMAL).
----End
Context
During interface verification, you can run an LST command to view the configuration
information. For example, before running the MML command DSP ADJNODE, you can run
the MML command LST ADJNODE to query the value of the Adjacent Node ID parameter.
Prerequisites
l The optical interface board configured on the BSC6900 is operating properly and has
been connected to the transmission equipment with fiber optic cables.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Context
Working channel: board in an even-numbered slot in active/standby mode
The following operation assumes that the board in an even-numbered slot is the active board
and that the board in an odd-numbered slot is the standby board.
Procedure
Step 1 Run the MML command CHK OPTCRS to check the status of fiber optic cable connections
for an optical interface board.
Expected result: The command output shows that the value for Check Result is Correct
connection.
l If the command output shows that the value of Check Result is The check fails, check
fiber optic cable connections or the peer optical port.
l If the command output shows that the value of Check Result is Incorrect connections,
exchange the RX branches of the optic fiber cables for the local working channel and
protection channel and then exchange the TX branches in the same way.
l If the command output shows that the value of Check Result is Incorrect TX
connection, correct RX connection, exchange the TX branches of the optic fiber cables
for the local working channel and protection channel.
l If the command output shows that the value of Check Result is Correct TX
connection, incorrect RX connection, exchange the RX branches of the optic fiber
cables for the local working channel and protection channel.
l If the command output shows that the value of Check Result is not of any of the
preceding ones, the conditions for checking fiber optic cable connections are not met. In
this case, troubleshoot according to the command output and run this command again.
----End
Prerequisites
l The BSC6900 Inter-SCUa/Inter-SCUb network cables have been installed.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Run the MML command DSP PANELPORT to query the link status of the ports on the
SCUa/SCUb boards.
Expected result: The command output shows the actual status of links to the ports on the
SCUa/SCUb boards.
If the status in the command output does not meet the installation requirements, reinstall the
inter-SCUa/SCUb network cables by referring to Installing the Inter-SCUb SFP+ High-Speed
Cables Between Different Subracks and . Reinstalling Inter-SCUa/SCUb Network Cables in
the BSC6900 UMTS Installation Guide.
----End
Prerequisites
l The BSC6900 and base station are physically connected and both have passed the
hardware installation acceptance.
l The cell under the base station for the Iub interface verification has been configured.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Context
The following takes one base station as an example to describe the verification process on the
Iub interface during the commissioning of the BSC6900. If multiple base stations are
connected, repeat the operations.
Procedure
l Verifying the Iub Interface (over ATM)
a. Run the MML command DSP SAALLNK to query the status of a Signaling ATM
Adaptation Layer (SAAL) link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.1 Checking Transmission
Links for troubleshooting.
b. Run the MML command DSP UIUBCP to query the status of a link on the Iub
interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.7 Signaling Link Failure
on the Iub Interface for troubleshooting.
c. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the value of Operation state is
Available and the values of available bandwidths cannot be all 0.
If the value of Operation state is Unavailable, see ALM-21531 SAAL Link Fault
for troubleshooting. If the value of Operation state is Available and the values of
available bandwidths are all 0, see EVT-22918 Change of Transport Resource State
for Adjacent Node User Plane for troubleshooting.
d. Run the MML command DSP AAL2PATH to query the status of an AAL2 path on
the Iub interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
e. Optional: Perform Virtual Connect Link (VCL) continuity check on all the AAL2
paths on the Iub interface. For details, see 17.2 Performing a VCL Continuity
Check.
f. Optional: Perform permanent virtual channel (PVC) delay test on all the AAL2
paths on the Iub interface. For details, see 17.3 Verifying the PVC Delay
Detection Function.
g. Run the MML command DSP UCELL to query the status of a cell.
Expected result: For all the cells, the value of Operational state is Available.
If the value of Operational state is not Available, see 17.6 Cell Setup Failure for
troubleshooting.
l Verifying the Iub Interface (over IP)
a. Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links for troubleshooting.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP UIUBCP to query the status of a link on the Iub
interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.7 Signaling Link Failure
on the Iub Interface for troubleshooting.
c. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the values of available
bandwidths cannot be all 0.
If the values of available bandwidths are all 0, see EVT-22918 Change of Transport
Resource State for Adjacent Node User Plane for troubleshooting.
d. Run the MML command DSP IPPATH to query the status of the IP path on the Iub
interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
e. Run the MML command DSP UCELL to query the status of a cell.
Expected result: For all the cells, the value of Operational state is Available.
If the value of Operational state is not Available, see 17.6 Cell Setup Failure for
troubleshooting.
l Verifying the Iub Interface (over Transmission Resource Pool)
a. Optional: Run the LST UIUBCP command to query the SCTP link ID that
corresponds to the NCP and CCP to a NodeB of which the control-plane parameters
are self-planned.
b. Run the MML command DSP SCTPLNK to query the status of an SCTP link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links for troubleshooting.
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, the SCTP link does not
disconnect intermittently.
c. Run the MML command DSP UIUBCP to query the status of a link on the Iub
interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.7 Signaling Link Failure
on the Iub Interface for troubleshooting.
d. Run the MML command DSP ADJNODEDIP to query the destination address of
an adjacent node.
Expected result: The command output shows the destination IP address information
of an adjacent node.
If there is no destination IP address information, the system has not initiated a call.
The verification is complete. You can proceed to query adjacent node Ping
detection status when the cell is set up.
e. Run the MML command DSP ADJNODEPING to query adjacent node Ping
detection status.
Expected result: The command output shows that the value of Detection Status is
Normal.
If the value of Detection Status is not Normal, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
f. Run the MML command DSP UCELL to query the status of a cell.
Expected result: For all the cells, the value of Operational state is Available.
If the value of Operational state is not Available, see 17.6 Cell Setup Failure for
troubleshooting.
l Verifying the Iub interface (over ATM/IP Dual Stack)
Verify the Iub interface over ATM and over IP, respectively.
----End
Prerequisites
l For R99 networking on the Iu-CS interface: the BSC6900 and MSC are been physically
connected, and the MSC is running properly.
l For R4 networking on the Iu-CS interface: the BSC6900, MSC server, and MGW are
physically connected; the transmission links on the interface between the MSC server
and the MGW are correct; the MSC server and the MGW are running properly.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
l Verifying the Iu-CS Interface (over ATM)
a. Run the MML command DSP SAALLNK to query the status of a Signaling ATM
Adaptation Layer (SAAL) link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.1 Checking Transmission
Links for troubleshooting.
b. Run the MML command DSP MTP3LNK to query the status of a Message
Transfer Part Level 3 (MTP3) signaling link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see ALM-21506 MTP3 Signaling
Link Faulty for troubleshooting.
c. Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the value of Operation state is
Available and the values of available bandwidths cannot be all 0.
Expected result: The command output shows that the value of CN Domain ID is
CS_DOMAIN.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
h. Optional: Perform virtual channel link (VCL) continuity check on all the AAL2
paths on the Iu-CS interface. For details, see 17.2 Performing a VCL Continuity
Check.
i. Optional: Perform permanent virtual channel (PVC) delay test on all the AAL2
paths on the Iu-CS interface. For details, see 17.3 Verifying the PVC Delay
Detection Function.
l Verifying the Iu-CS Interface (over IP)
a. Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links for troubleshooting.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Expected result: The command output shows that the value of Operation state is
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of an SCCP SSN.
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
d. Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the values of available
bandwidths cannot be all 0.
If the values of available bandwidths are all 0, see EVT-22918 Change of Transport
Resource State for Adjacent Node User Plane for troubleshooting.
f. Run the MML command LST UCNNODE to check whether the CN node in the
CS domain is configured.
Expected result: The command output shows that the value of CN Domain ID is
CS_DOMAIN.
If Corresponding results not found is returned or the value of CN Domain ID is
not CS_DOMAIN, Run the MML command ADD UCNNODE to configure the
corresponding CN node.
g. Run the MML command DSP IPPATH to query the status of the IP path on the Iu-
CS interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
l Verifying the Iu-CS Interface (over Transmission Resource Pool)
a. Run the MML command DSP SCTPLNK to query the status of an SCTP link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links for troubleshooting.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an M3UA link.
Expected result: The command output shows that the value of Operation state is
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of an SCCP SSN.
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
d. Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODEDIP to query the destination IP address
information of an adjacent node.
Expected result: The command output shows the destination IP address information
of an adjacent node.
If there is no destination IP address information, the system has not initiated a call.
The verification is complete. You can proceed to query adjacent node Ping
detection status when the call is initiated.
f. Run the MML command DSP ADJNODEPING to query adjacent node Ping
detection status.
Expected result: The command output shows that the value of Detection Status is
Normal.
If the value of Detection Status is not Normal, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
g. Run the MML command LST UCNNODE to check whether the CN node in the
CS domain is configured.
Expected result: The command output shows that the value of CN Domain ID is
CS_DOMAIN.
If Corresponding results not found is returned or the value of CN Domain ID is
not CS_DOMAIN, run the MML command ADD UCNNODE to configure the
corresponding CN node.
----End
Prerequisites
l The BSC6900 and SGSN are physically connected and both have passed the hardware
installation acceptance.
l The SGSN used to verify the Iu-PS interface is operating properly.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
l Verifying the Iu-PS Interface (over ATM)
a. Run the MML command DSP SAALLNK to query the status of a Signaling ATM
Adaptation Layer (SAAL) link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.1 Checking Transmission
Links for troubleshooting.
b. Run the MML command DSP MTP3LNK to query the status of a Message
Transfer Part Level 3 (MTP3) signaling link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see ALM-21506 MTP3 Signaling
Link Faulty for troubleshooting.
c. Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
d. Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the value of Operation state is
Available and the values of available bandwidths cannot be all 0.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Expected result: The command output shows that the value of Operation state is
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
d. Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the values of available
bandwidths cannot be all 0.
If the values of available bandwidths are all 0, see EVT-22918 Change of Transport
Resource State for Adjacent Node User Plane for troubleshooting.
f. Run the MML command LST UCNNODE to check whether the CN node is
configured in the PS domain.
Expected result: The command output shows that the value of CN Domain ID is
PS_DOMAIN.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
l Verifying the Iu-PS Interface (over Transmission Resource Pool)
a. Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links for troubleshooting.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Expected result: The command output shows that the value of Operation state is
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of an SCCP SSN.
Expected result: The command output shows that the value of SSN state is
Allowed.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODEDIP to query the destination IP address
information of an adjacent node.
Expected result: The command output shows that the destination IP address
information of an adjacent node is returned.
If there is no destination IP address information, the system has not started a data
service. The verification is complete. You can proceed to query adjacent node Ping
detection status when the data service is started.
f. Run the MML command DSP ADJNODEPING to query adjacent node Ping
detection status.
Expected result: The command output shows that the value of Detection Status is
Normal.
If the value of Detection Status is not Normal, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
g. Run the MML command LST UCNNODE to check whether the CN node is
configured in the PS domain.
Expected result: The command output shows that the value of CN Domain ID is
PS_DOMAIN.
----End
Prerequisites
l The BSC6900 and RNC are physically connected and both have passed the hardware
installation acceptance.
l The RNC used to verify the Iur interface is operating properly.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Context
Before performing this task, ensure that the RNC at the other end on the Iur interface is
commissioned.
Procedure
l Verifying the Iur Interface (over ATM)
a. Run the MML command DSP SAALLNK to query the status of a Signaling ATM
Adaptation Layer (SAAL) link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 17.1 Checking Transmission
Links.
b. Run the MML command DSP MTP3LNK to query the status of a Message
Transfer Part Level 3 (MTP3) signaling link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see ALM-21506 MTP3 Signaling
Link Faulty for troubleshooting.
c. Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
d. Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the value of Operation state is
Available and the values of available bandwidths cannot be all 0.
If the value of Operation state is Unavailable, see ALM-21562 QAAL2 Adjacent
Node Inaccessible for troubleshooting. If the value of Operation state is Available
and the values of available bandwidths are all 0, see EVT-22918 Change of
Transport Resource State for Adjacent Node User Plane for troubleshooting.
f. Run the MML command DSP AAL2PATH to query the status of an AAL2 path on
the Iur interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
g. Optional: If the BSC6900 is configured with an IP path to the RNC, run the MML
command PING IP to check whether the connection to the RNC is correct.
Expected result: The IP address can be pinged.
If the IP address cannot be pinged, check whether a firewall is configured at the
peer end. If a firewall does not exist, perform virtual channel link (VCL) continuity
check on all the IP over ATM (IPoA) permanent virtual connections (PVCs) on the
Iur interface. For details, see 17.2 Performing a VCL Continuity Check and 17.3
Verifying the PVC Delay Detection Function.
l Verifying the Iur Interface (over IP)
a. Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links.
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, the Stream Control
Transmission Protocol (SCTP) link does not disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Expected result: The command output shows that the value of Operation state is
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of an SCCP SSN.
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
d. Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The command output shows that the values of available
bandwidths cannot be all 0.
If the values of available bandwidths are all 0, see EVT-22918 Change of Transport
Resource State for Adjacent Node User Plane for troubleshooting.
f. Run the MML command DSP IPPATH to query the status of the IP path on the Iur
interface.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is not Available, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
l Verifying the Iur Interface (over Transmission Resource Pool)
a. Run the MML command DSP SCTPLNK to query the status of an SCTP link.
Expected result: The command output shows that the value of Operation state is
Normal.
If the value of Operation state is not Normal, see 17.1 Checking Transmission
Links.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an M3UA link.
Expected result: The command output shows that the value of Operation state is
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of an SCCP SSN.
Expected result: The command output shows that the value of SSN state is
Allowed.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
e. Run the MML command DSP ADJNODEDIP to query the destination address of
an adjacent node.
Expected result: The command output shows the destination IP address information
of an adjacent node.
If there is no destination IP address information, the system has not started an Iur
handover. The verification is complete. You can proceed to query adjacent node
Ping detection status when the Iur handover is started.
f. Run the MML command DSP ADJNODEPING to query adjacent node Ping
detection status.
Expected result: The command output shows that the value of Detection Status is
Normal.
If the value of Detection Status is not Normal, see 17.8 AAL2/IP Connection
Setup Failure for troubleshooting.
----End
Prerequisites
l The BSC6900 and CBC have been physically connected, and both have passed the
hardware installation acceptance.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Run the PING IP command to query the connectivity between the BSC and CBC. In this
command, set Source IP Address to the IP address of the Iu-BC interface board at the local
end and set Target IP Address to the IP address of the CBC server at the peer end.
If the CBC server cannot be pinged, check whether a firewall is configured at the peer end. If
a firewall does not exist, check whether the IP addresses and route on the BSC6900 and CBC
are correctly configured.
----End
Prerequisites
l The BSC6900 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
l The RNC used to verify the Iur-g interface is operating properly.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
l Verifying the Iur-g interface (intra-RNC)
a. Run the DSP BRD command to query the status of a board.
Expected result: The command output shows that the value of CPU status is Active
normal.
If the value of CPU status is not Active normal, see ALM-20242 Board
Subsystem Unavailable for troubleshooting.
l Verifying the Iur-g interface (inter-RNC)
a. Run the MML command DSP SCTPLNK to query the status of the Stream Control
Transmission Protocol (SCTP) link.
If the value of Operation state is not Normal, see operations in 17.1 Checking
Transmission Links.
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, the SCTP link does not
disconnect intermittently.
b. Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault
for troubleshooting.
c. Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is Inaccessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
----End
Prerequisites
l The BSC6910 and BSC6900 are physically connected and both have passed the
hardware installation acceptance.
l The BSC6900 or BSC6910 used to verify the Iur-p interface is operating properly.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Run the MML command DSP IURPLKS and specify External Node Id. to query the status
of an Iur-p link set of the external node.
Expected result: Values of Number of IURP Link on Fault Subsystem, Number of IURP
Link on Invalid Subsystem, and Number of Fault IURP Link are all 0s.
If the value of Number of IURP Link on Fault Subsystem is not 0, run the MML command
RMV IURPLKS to remove the Iur-p link set of the external node and then run the MML
command ADD IURPLKS to add a new Iur-p link set to the external node.
If the value of Number of IURP Link on Invalid Subsystem is not 0, the number of Iur-p
links exceeds the RNC capability. In this case, run the MML command MOD IURPLKS to
modify the number of Iur-p links in the link set. Alternatively, run the MML command RMV
IURPLKS to remove a link set so that the number of Iur-p links can be decreased to be
within RNC capability.
NOTE
l The RNC's capability for supporting Iur-p links depends on the capabilities of configured boards on the
control plane (CP) and their numbers. When RNC in Pool is applied with two RNCs pooled, the
maximum number of Iur-p links supported in an RNC pool depends on the pooled RNC whose capability
for supporting Iur-p links is lower.
For example, in an RNC pool with two RNCs pooled, if RNC 1 supports four Iur-p links and RNC 2
supports six Iur-p links, the RNC pool can support a maximum of four Iur-p links and the excessive two
Iur-p links on RNC 2 become faulty.
l The number of Iur-p links supported by the SPU board depends on its logical function type. The SPUa
board supports three Iur-p links when its logical function type is RUCP and supports four Iur-p links
when its logical function type is UCP. The SPUb/SPUc board supports seven Iur-p links when its logical
function type is RUCP and supports eight Iur-p links when its logical function type is UCP.
If the value of Number of Fault IURP Link is not 0, see ALM-21606 IURP Link Fault for
troubleshooting.
Step 2 Run the MML command DSP ADJNODEDIP to query the destination address of an adjacent
node.
Expected result: If the command output shows the destination IP address information of an
adjacent node of the peer end.
If there is no destination IP address information, the peer end does not configure an adjacent
node, the verification is complete.
Step 3 Run the MML command DSP ADJNODEPING to query the status of the adjacent node.
Expected result: If the command output shows that the value of Detection Status is Normal.
If Detection Status is Fault, see 17.8 AAL2/IP Connection Setup Failure for
troubleshooting.
----End
Prerequisites
l The BSC6900 and eCoordinator are physically connected and both have passed the
hardware installation acceptance.
l The Sr interface has been configured.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Expected result: The value of Operation state is Normal.
If the value of Operation state is not Normal
l If the coordination service is not configured within the RNC, see operations in 17.1
Checking Transmission Links.
l If the coordination service is configured within the RNC, check whether the data
configuration on the interface is correct.
Step 2 Run the MML command DSP UECOCONN to query the status of the communication link.
Expected result: The value of Operation state is Available.
If the value of Operation state is Unavailable, check whether the data configuration on the
interface is correct.
----End
This section describes how to handle the alarms generated during the commissioning to
prevent the alarms from affecting service verifications.
Prerequisites
l The communication between the BSC6900 and OMU is normal.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Click Alarm/Event on the LMT home page. The BSC6900 Alarm/Event tab page is
displayed.
Step 2 Check whether any active alarm exists on the Normal Alarm tab page.
If... Then...
Step 3 Double-click the active alarm to be handled on the Normal Alarm tab page. The Detailed
Information dialog box is displayed.
----End
This section describes how to verify that the basic UMTS services and the feature services are
normal. The basic UMTS services are speech services and data services. Feature services
include inter-RAT handovers, HSDPA, HSUPA, 64QAM, MIMO, CBS, and DC-HSDPA.
Prerequisites
l The BSC6900 has passed the commissioning.
l The commissioning over the Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-p interfaces is
successful.
l Test UEs are functional and have registered with the HLR.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
Step 1 Verify basic UMTS services with test UEs in NodeB cells by following operations listed in
Table 15-1.
Table 15-1 Operations for verifying basic UMTS services with test UEs in NodeB cells
Service Type Operation Expected Result
Speech service Make 20 calls from a test The connection success rate
UE to a fixed-line phone is higher than 95%. The
and hold on each call for 60 voice is clear without loud
seconds. noise. No call drop occurs
and the system resources are
released properly after the
call is terminated.
Data service Activate the 384 kbit/s The activation success rate
service. Use a test UE to is higher than 95% and you
browse web pages through can browse the web page
the web browser 20 times. properly.
NOTE
If service verification results cannot meet expected results, start the following tracing tasks: Uu Interface
Trace, Iu Interface Trace, Iub Interface Trace, Iur Interface Trace, UE Trace, and Cell Trace.
Step 2 Verify feature services with the test UEs in NodeB cells by following operations listed in
Table 15-2.
Table 15-2 Operations for verifying feature services with test UEs in NodeB cells
Service Type Operation Expected Result
Inter-RAT handover Hand over a dual-mode test The handover success rate is
UE from UMTS to GSM for higher than 90%. For CS
20 times on CS and PS services, the voice is clear
services respectively. Hand without loud noise; For PS
over a dual-mode test UE service, no call drop occurs.
from GSM to UMTS for 20
times on CS and PS
services, respectively.
High Speed Downlink Activate the high-speed PS The activation success rate
Packet Access (HSDPA) service. Use a test UE to is higher than 90% and the
access the FTP server and downloading is normal.
download large files for 10
times. The assigned
downlink data rate of
services must be higher than
384 kbit/s.
High Speed Uplink Packet Activate the high-speed PS The activation success rate
Access (HSUPA) service. Use a test UE to is higher than 90% and the
access the FTP server and uploading is normal.
upload large files for 10
times. The assigned uplink
rate of services is required
to be over 384 kbit/s.
Multiple Input Multiple Activate the high-speed PS The activation success rate
Output (MIMO) service service. Use a test UE to is higher than 90% and the
access the FTP server and downloading is normal.
download large files for 10
times. The assigned
downlink data rate of
services must be higher than
384 kbit/s.
Cell broadcast service Use the cell broadcast center The UE successfully
(CBS) (CBC) to send CBS short receives correct CBS short
messages. Enable the UE to messages.
receive these messages.
Repeat this operation 10
times.
----End
The network reliability can be verified by checking generated alarms and making dialing tests
after a switchover between the active/standby boards.
Prerequisites
l The standby board to be switched over is operating properly.
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l The alarms generated before the switchover have been cleared.
Procedure
Step 1 Switch over the OMU boards. For details, see Switching Over BSC Boards in the BSC6900
UMTS LMT User Guide.
Step 2 Check and handle the alarms generated during the switchover. For details, see 14 Handling
the Alarms Generated During the Commissioning.
Step 3 Use a UE in a cell under the NodeB to perform basic services and check whether services are
going on properly. For details, see Table 16-1.
Table 16-1 Operations for verifying basic UMTS services with test UEs in NodeB cells
Service Type Operation Expected Result
Speech service Make 20 calls from a test The connection success rate
UE to a fixed-line phone is higher than 95%. The
and hold on each call for 60 voice is clear without loud
seconds. noise. No call drop occurs
and the system resources are
released properly after the
call is terminated.
Data service Activate the 384 kbit/s The activation success rate
service. Use a test UE to is higher than 95% and you
browse web pages through can browse the web page
the web browser 20 times. properly.
----End
17 Troubleshooting
This chapter describes how to troubleshoot common problems during the commissioning.
This section describes how to check whether E1/T1 ports are functional by performing
loopback tests on the E1/T1 links carried by the electrical port.
17.11 Performing a Loopback Test on an Optical Port
This section describes how to perform the group loopback test to check whether an optical
port is functional.
17.12 Checking the QCIs of the IP Transmission Link
This section describes how to perform the active test to check whether the QoS class
identifiers (QCIs) of the interface-based IP transmission meet the requirements. QoS is short
for quality of service.
Prerequisites
l All the subracks of the BSC6900 are running normally.
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
Procedure
l Check the status of physical transmission links based on the transmission scheme.
Table 17-1 Methods for checking the status of transmission links based on the
transmission scheme
If the transmission scheme on the Then...
interface is...
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 17.4 Unavailable
E1/T1 Port for troubleshooting.
l Check the status of an FE/GE port.
a. Run the MML command DSP ETHPORT to query the status of the Ethernet port.
If either of the following cases occurs, see 17.5 Unavailable FE/GE Port for
troubleshooting.
n The value of Link Availability Status is Unavailable.
n The value of Port state is Deactivated.
b. Optional: Check the connectivity of the gateway (this operation is mandatory if
three-layer networking applies).
i. Run the MML command LST IPCHK to query the configuration of the
gateway continuity check.
ii. Run the MML command STR IPCHK to start the gateway continuity 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.
iii. On the alarm tab page of the LMT, check whether ALM-21346 IP
Connectivity Check Failure is reported. If yes, clear the alarm according to the
alarm handling suggestions.
iv. Optional: To keep the gateway continuity check, end the check task;
otherwise, run the MML command STP IPCHK to stop the gateway
continuity check.
l Checking the status of an optical port
a. Run the MML command DSP OPT to query the status of an optical port.
If the value of Optical port state is not Available, check the alarms related to the
optical port and rectify the fault according to the handling suggestions in the online
alarm reference.
----End
Prerequisites
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l The peer end (NodeB, MGW, MSC, or SGSN) supports the F5 protocol.
Context
Only the VCLs that carry the SAAL link, IPoA PVC, or AAL2 path supports the continuity
check.
Procedure
l Perform a continuity check on the SAAL link.
a. Run the MML command ACT VCLCC to activate the continuity check on the
VCL. In this step, set Link type to SAALLNK, VCL act type to CC, and
Activation direction to BOTH.
b. Run the MML command DSP VCLCC, and then set Link type to SAALLNK to
query the result of the continuity check on the VCL.
Expected result: The values of LOC alarm, AIS alarm, RDI alarm, andCC
activated failure alarm are all Normal.
If the value of any of these parameters is not Normal, check whether the following
alarms are reported. If yes, rectify the fault following the alarm handling
suggestions.
n ALM-21321 VCL CC Detection Failure
n ALM-21322 VCL Alarm Indication Signal
n ALM-21323 VCL Remote Alarm Indication
n ALM-21324 VCL CC Activation Failure
c. Optional: To keep the VCL continuity check running, no action is required. To
terminate the VCL continuity check, run the MML command DEA VCLCC with
Link type set to SAALLNK.
l Perform a continuity check on the AAL2 path.
a. Run the MML command ACT VCLCC, and then set Link type to AAL2PATH,
VCL act type to CC, and Activation direction to BOTH to activate the continuity
check on the VCL.
b. Run the MML command DSP VCLCC, and then set Link type to AAL2PATH to
query the result of the continuity check on the VCL.
Expected result: The values of LOC alarm, AIS alarm, RDI alarm, andCC
activated failure alarm are all Normal.
If the value of any of these parameters is not Normal, check whether the following
alarms are reported. If yes, rectify the fault following the alarm handling
suggestions.
n ALM-21321 VCL CC Detection Failure
n ALM-21322 VCL Alarm Indication Signal
n ALM-21323 VCL Remote Alarm Indication
n ALM-21324 VCL CC Activation Failure
c. Optional: To keep the VCL continuity check running, no action is required. To
terminate the VCL continuity check, run the MML command DEA VCLCC with
Link type set to AAL2PATH.
l Perform a continuity check on the IPoA PVC.
a. Run the MML command ACT VCLCC, and then set Link type to IPOAPVC,
VCL act type to CC, and Activation direction to BOTH to activate the continuity
check on the VCL.
b. Run the MML command DSP VCLCC, and then set Link type to IPOAPVC to
query the result of the continuity check on the VCL.
Expected result: The values of LOC alarm, AIS alarm, RDI alarm, andCC
activated failure alarm are all Normal.
If the value of any of these parameters is not Normal, check whether the following
alarms are reported. If yes, rectify the fault following the alarm handling
suggestions.
n ALM-21321 VCL CC Detection Failure
n ALM-21322 VCL Alarm Indication Signal
n ALM-21323 VCL Remote Alarm Indication
n ALM-21324 VCL CC Activation Failure
----End
Prerequisites
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l The peer end (NodeB, MGW, MSC, or SGSN) supports the F5 protocol.
Context
l Only VCLs that carry the SAAL link, IPoA PVC, or AAL2 path supports the PVC delay
test.
l The PVC delay for a maximum of six links can be detected on the LMT because only six
link performance monitoring tasks can be started simultaneously.
Procedure
l Verify the PVC delay detection function on the SAAL link.
a. Run the MML command LOP VCL to perform a single PVC loopback test. In this
step, set Link type to SAALLNK.
Expected result: The delay of the link being monitored is dynamically displayed in
the Link Performance Monitoring dialog box.
e. Optional: To keep the PVC delay test running, no action is required. To terminate
the PVC delay test, run the MML command DEA VCLCC with Link type set to
SAALLNK.
l Perform the PVC delay test on the AAL2 path.
a. Run the MML command LOP VCL and then set Link type to AAL2PATH to
perform a single PVC loopback test.
Expected result: The delay of the link being monitored is dynamically displayed in
the Link Performance Monitoring dialog box.
e. Optional: To keep the PVC delay test running, no action is required. To terminate
the PVC delay test, run the MML command DEA VCLCC with Link type set to
AAL2PATH.
l Perform the PVC delay test on the IPoA PVC.
a. Run the MML command LOP VCL and then set Link type to IPOAPVC to
perform a single PVC loopback test.
Fault Description
When you run the MML command DSP E1T1 to check the status of E1/T1 ports, Port
running state in the returned result is Port is down.
Solution
1. If Port running state is Port is down for an E1/T1 port, handle the problem as follows:
When electrical ports serve as the bearers, perform the E1/T1 loopback test on all
the faulty E1/T1 ports. For details, see 17.10 Performing a Loopback Test on the
Local E1/T1 Port.
When optical ports serve as the bearers, perform the group loopback test on all the
faulty E1/T1 ports. For details, see 17.11 Performing a Loopback Test on an
Optical Port.
2. Check whether the following alarms are listed on the alarm tab page on the LMT. If any
of the alarms exists, handle them according to the suggestions in online alarm reference.
ALM-21201 E1/T1 Loss of Signal
ALM-21294 SDH/SONET TU Signal Loss
ALM-21261 SDH/SONET LP Remote Defect Indication
ALM-21202 E1/T1 Loss of Frame Alignment
ALM-21275 SDH/SONET Tributary Loss of Frame
ALM-21241 Loss of Fractional IMA Frame
ALM-21203 E1/T1 Remote Alarm Indication Signal
ALM-21286 SDH/SONET Tributary Remote Alarm Indication Signal
ALM-21205 E1/T1 Loss of Multiframe Alignment
When you run the MML command DSP E1T1 to check the E1/T1 port status, if Is this E1/T1
occupied is set to NO, the link is still available even though the ALM-21261 SDH/SONET LP
Remote Defect Indication exists.
Fault Description
When you run the MML command DSP ETHPORT to check the status of the FE/GE port,
one of the following events occurs:
l The value of Link Availability Status is Unavailable.
l The value of Port state is Deactivated.
Solution
1. If the value of Link Availability Status is Unavailable, check the connection of the
network cable and check whether the peer network interface is enabled. See the online
alarm reference for the alarm handling suggestions.
2. If the value of Port state is Deactivated, run the MML command ACT ETHPORT to
activate the FE/GE port.
Fault Description
During the verification of cell setups, the final result is not as expected. The operation state of
the cell is Unavailable and the Iub interface tracing fails to trace the complete cell setup
procedure on the Iub interface.
NOTICE
l If Iub over ATM is applied, check whether the alarms related to the DPUb/DPUe, DSP,
SAAL link, IMA, optical port, or AAL2 exist in the alarm management system when cell
setup failure occurs. If such alarms exist, handle the alarms as suggested. If the alarms
persist, handle them as follows:
l If Iub over IP is applied, check whether the alarms related to the DPUb/DPUe, DSP, or
SCTP link exist in the alarm management system when cell setup failure occurs. If such
alarms exist, handle the alarms as suggested. If the alarms persist, handle them as follows:
l If Iub over ATM/IP dual-stack is applied, check whether the alarms related to the DPUb/
DPUe, DSP, SAAL link, SCTP link, IMA, optical port, or AAL2 exist in the alarm
management system when cell setup failure occurs. If such alarms exist, handle the alarms
as suggested. If the alarms persist, handle them as follows:
To narrow down the fault location, determine whether the NodeB or the BSC6900 is faulty by
comparing the results of the Iub interface message tracing results with those expected in
normal working condition. Then, further locate the fault using other methods.
Figure 17-1 and Figure 17-2 show the procedures for locating cell setup failures.
*1-1 Check whether the Iub link See 17.1 Checking Transmission
works properly. Links.
*1-2 Handle link failures on the Iub See 17.7 Signaling Link Failure on
interface. the Iub Interface.
*1-3 Check whether the audit See Solution 1: Checking the Audit
response message is correct. Response Message.
*1-6 Check whether the DSP l Run the MML command DSP DSP
resources are available. to query the number of available
DSPs on a DPUb board. Perform
this action on all the DPU boards.
The sum of the results is the number
of available DSPs.
l The number of cells that can be set
up is 15 times the number of DSPs.
If the calculated cell number is
smaller than the number of cells that
are currently set up, the DSP
resources are insufficient.
*2-1 Check whether the PRACH See Solution 4: Checking the PRACH
setup response message is Setup Response Message.
correct.
*2-2 Check whether the Iub link See 17.1 Checking Transmission
works properly. Links.
*2-3 Handle link failures on the See 17.7 Signaling Link Failure on the
Iub interface. Iub Interface.
*2-5 Handle the AAL2/IP link See 17.8 AAL2/IP Connection Setup
setup failures. Failure.
NOTE
When the user plane is over ATM transmission, the value of the TranspLayerAddr parameter is the ATM
address. Run the MML command LST UNODEB to check whether the configured ATM address is consistent
with that in the PRACH setup response message.
When the user plane is over IP transmission, the value of the TranspLayerAddr parameter is the IP address.
Run the MML command LST IPPATH to check whether the peer IP address (that is, the IP address of the
NodeB user plane) configured is consistent with that in the PRACH setup response message.
NOTE
When the user plane is over ATM transmission, the value of the TranspLayerAddr parameter is the ATM
address. Run the MML command LST UNODEB to check whether the ATM address configured is consistent
with that in the SCCPCH setup response message.
When the user plane is over IP transmission, the value of the TranspLayerAddr parameter is the IP address.
Run the MML command LST IPPATH to check whether the peer IP address (that is, the IP address of the
NodeB user plane) configured is consistent with that in the SCCPCH setup response message.
Fault Description
During cell setup, a signaling link on the Iub interface is faulty. The NBAP_AUDIT_REQ
message cannot be traced on the Iub interface. The alarms related to the DPUb/DSP board are
not reported.
Solution
1. For Iub over ATM transmission, check whether alarms related to the E1/T1 port, FE/GE
port, SAAL link, IMA, UNI, NCP, or CCP are reported. If the alarms are reported,
handle them according to the suggestions in the online alarm reference. If the alarms
persist, handle them according to Figure 17-3.
Figure 17-3 Troubleshooting signaling link failures on the Iub interface over ATM
transmission
*1-1 Add upper-layer Run the MML commands ADD UNCP, ADD
applications to the UCCP, and ADD ADJNODE to add NCP, CCP,
SAAL link. and ALCAP, respectively.
2. For Iub over IP transmission, check whether alarms related to the E1/T1 port, FE/GE
port, SCTP link, NCP, CCP are reported. If the alarms are reported, handle them
according to the suggestions in the online alarm reference. If the alarms persist, handle
them according to Figure 17-4.
Figure 17-4 Handling of signaling link failures on the Iub interface over IP transmission
*2-1 Check whether the Run the MML command DSP SCTPLNK to
SCTP link works check whether the SCTP link works properly.
properly.
*2-2 Add upper-layer Run the MML commands ADD UNCP and ADD
applications to the UCCP to add upper-layer applications to the SCTP
SCTP link. link.
*2-5 Check the data Run the MML LST SCTPLNK command to
configuration. check the consistency of the negotiated data on the
SCTP link. If they are inconsistent, go to *2-6. If
they are consistent, go to the next step shown in
Figure 17-4.
*2-6 Modify data Modify the configuration on the SCTP link. Run
configuration. the MML command MOD SCTPLNK to modify
the configuration on the SCTP link.
Figure 17-5 Handling of signaling link failures on a NodeB for which the control-plane
parameters are self-planned in Iub over IP scenarios
*3-2 Query the upper- Run the LST UIUBCP command to check
layer applications. whether the NCP and CCP are configured for the
NodeB.
If yes, handle the signaling link failure by referring
to Figure 17-4.
Otherwise, go to *3-3.
*3-4 Modify the data The following describes the operation procedure.
configuration. 1. Check whether the NCP and CCP are
configured on the NodeB.
l If the NCP and CCP are not configured, run
the ADD UNCP command and the ADD
UCCP command to add upper-layer
configurations to the SCTP link.
l If the NCP and CCP are configured, go to
the next step.
2. Run the LST SCTPLNK command on the
NodeB side, and the LST SCTPSRV command
on the RNC side to check whether the IP
address and port number on the NodeB side is
consistent with these on the RNC side.
l If they are not consistent, run the MOD
SCTPLNK command on the NodeB side
and the MOD SCTPSRV command on the
RNC side to change the data configurations
according to the data planning.
l If they are consistent, go to the next step.
*3-5 Handle the On the Web LMT, perform SCTP trace based on
transmission link the IP address pair to check whether the NodeB
failure. can successfully send a signaling message to the
RNC.
If the NodeB cannot send a signaling message to
the RNC, the transmission link is faulty.
1. If the data is transmitted over Ethernet, for
example, through the FE port, see 17.5
Unavailable FE/GE Port.
2. If the data is transmitted over a private line, for
example, over E1/T1 links, see 17.4
Unavailable E1/T1 Port.
4. For Iub over ATM/IP dual-stack transmission, troubleshoot the failures according to the
suggestions in the ATM transmission and IP transmission as required.
Fault Description
During an AAL2 or IP connection setup or cell setup, the AAL2 or IP link fails to be
established.
Solution
l When the user plane is over ATM transmission, check whether the alarms related to the
IMA, optical ports, RSS, AAL2, or MTP3B are reported. If the alarms are reported,
handle them according to the suggestions in the online alarm reference. If the alarms
persist, handle them according to Figure 17-6.
*1-1 Check and modify the If the configuration data is inconsistent with the
local data negotiated data, modify the configuration data
configuration. based on the negotiated data as described in
Table 17-8.
*1-2 Handle link failures on See 17.7 Signaling Link Failure on the Iub
the Iub interface. Interface.
LST Whether the adjacent node Run the MML command ADD
ADJNODE is configured. ADJNODE to add an adjacent node.
LST Whether the AAL2 path to Run the MML command ADD
AAL2PATH the adjacent node is AAL2PATH to add an AAL2 path.
configured.
l When the user plane is over transmission resource pool, troubleshoot the setup failure on
the UMTS user plane according to Table 17-9.
*2-1 Determine the Run the MML command DSP ADJNODESIP to query
SIP that carries the SIP that carries the common channel.
the common
channel.
*2-2 Check whether Run the MML command DSP IPPOOL to query the SIP
the SIP is status.
normal. l If the value of SIP operation state is Normal, go to
*2-3.
l If the value of SIP operation state is Fault, go to
*2-4.
*2-5 Check the status Run the MML command DSP SRCIPRT to query the
of the route status of the route based on the source IP address.
based on the l If the value of Route Status is UP, go to *2-7.
source IP
address. l If the value of Route Status is DOWN, go to *2-6.
*2-6 Check whether Run the MML command LST SRCIPRT to query the
the configuration of the route based on the source IP
configuration of address.
the route based l If the configuration is incorrect, modify the
on the source IP configuration accordingly.
address is
correct. l If the configuration is correct, go to *2-7.
*2-7 Check the Run the MML command TRC IPADDR to check the
configuration of transmission and request transmission engineers to
the IP route handle problems.
from the local
end to the
destination end.
l When the user plane is over IP transmission, troubleshoot the setup failure on the user
plane according to Table 17-10.
*3-1 Determine the IP Run the MML commands LST IPPATH and LST
path that carries TRMMAP to obtain the ID of the IP path that carries
the common the common channel.
channel.
*3-2 Check whether 1. Run the MML command DSP IPPATH to query the
the IP path is status of the IP path.
available. 2. Optional: 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 *3-3.
*3-4 Handle the 1. If the data is transmitted over Ethernet, for example,
transmission through FE ports, see 17.5 Unavailable FE/GE Port.
link failure. 2. If the data is transmitted over a private line, for
example, over E1/T1 links, see 17.4 Unavailable
E1/T1 Port.
*3-5 Check the Run the MML command LST IPPATH to check
configuration of whether the negotiated data is consistent. If
the IP path. inconsistency exists, modify the negotiated data.
*3-6 Check the real- Run the MML command DSP IPRT to check the real-
time IP route time IP route information.
information.
Fault Description
The status of a board on the device panel is abnormal when host software and data files are
being loaded to the BSC6900 board.
Solution
1. Check the loading status of other boards in this subrack.
If... Then...
Board status of other boards is Replace the faulty board and then reload data to the
Normal new board.
The DIP switch on the subrack Correct the DIP switch setting and then power cycle
is not set as configured the subrack to reset it for reloading.
3. Check whether the internal subnet mask of the OMU board is 255.0.0.0 and whether the
two internal IP addresses are *.*.3.50 and *.*.3.60. The internal IP address is related to
the configure of the MML command LST SUBNET.
If... Then...
Yes Go to 4.
4. If data loading on all boards in the EPS fails, check whether the board in the MPS is
properly connected to that in the EPS.
If... Then...
The connection is improper Correct the connection and reload data to the board.
5. If data loading on all boards in the EPS fails, run the LST SCUPORT command to
check whether configurations of panel ports between the EPS subrack and its upper-level
subrack are correct.
If... Then...
Configurations of panel ports Correctly configure panel ports and load the
are incorrect. software to all boards in the EPS subrack.
6. Run the MML command LST SUBRACK to check whether the type of the faulty board
is properly set.
If... Then...
The type of the board is Correct the board type and then reload data to the
incorrectly set board.
If... Then...
7. If data loading on the SPUa/SPUb/SPUc board fails, run the MML command LST
URNCBASIC to check whether the BSC6900 basic data is properly set.
If... Then...
The setting is incorrect Correct the BSC6900 basic information and reload
data to the board.
8. Check whether any alarm related to board fault is present in the Alarm Browser window.
If... Then...
Alarms related to board fault Analyze the alarm information and clear the alarm.
exist
Prerequisites
You have completed the operations provided in section 6 Logging In to the BSC6900 Using
the LMT.
Context
l The loopback test and the Bit Error Rate (BER) test cannot be performed simultaneously.
l During a loopback test, services carried on the tested link will be interrupted.
l The loopback test can be performed when an E1/T1 unavailable alarm is reported on an
E1/T1 port.
Procedure
Step 1 Perform the loopback test on the local E1/T1 port.
Table 17-11 Procedure for performing the loopback test on the local E1/T1 port
Step Operation
1-1 Run the MML command SET E1T1LOP to set a loopback test on an E1/T1 port.
In this step, set Loop type to LOCAL_LOOP.
1-2 Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port.
1-3 Run the MML command DSP E1T1LOP to query the result of the loopback test.
1-4 Run the MML command SET E1T1LOP to stop the loopback test on the E1/T1
port. In this step, set Loop type to NO_LOOP.
If... Then...
The loopback test result is Not The E1/T1 port is faulty. Replace the interface board
succeeded carrying the faulty E1/T1 port.
Table 17-12 Procedure for performing a loopback test on the local E1/T1 cable
Step Operation
2-1 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.
2-2 Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port.
2-3 Run the MML command DSP E1T1LOP to query the result of the loopback test.
If... Then...
The loopback test result is The E1/T1 cable is properly connected. Go to Step 3.
Succeeded
If... Then...
The loopback test result is Not l Use a multimeter to measure the connectivity between
succeeded the connector pin of the E1/T1 cable and the inner
conductor of the coaxial cable and the connectivity
between the outer shell of the connector and the shield
layer of the coaxial cable. If a connectivity failure
occurs, make a new connector and assemble the cable
again.
l Use a multimeter to check whether the internal and
external conductors of the E1/T1 cable are short-
circuited. If so, make a new connector and assemble
the cable again.
If the fault persists, replace the E1/T1 cable with a new
E1/T1 cable.
Table 17-13 Procedure for checking the peer equipment or the transport network
Step Operation
3-1 Run the MML command SET E1T1LOP at the local end to set a loopback test on
the remote E1/T1 port. In this command, set Loop type to
REMOTE_LOOP(REMOTE LOOP).
3-2 l If the peer equipment is the BSC6900, run the MML command LOP E1T1 at
the peer end to start the loopback test on the E1/T1 port, then run the MML
command DSP E1T1LOP at the peer end to query the result of the loopback
test.
l If the peer equipment is not the BSC6900, contact the maintenance personnel
for the peer equipment to query the result of the loopback test.
3-3 Run the MML command SET E1T1LOP at the local end to stop the loopback test
on the E1/T1 link. In this step, set Loop type to NO_LOOP(No loop).
If... Then...
The loopback test result is Contact the Technical Support for Assistance.
successful
The loopback test result is Contact the maintenance personnel for the peer equipment
unsuccessful to rectify faults in the peer equipment or the transport
network.
----End
Prerequisites
You have completed the operations provided in section 6 Logging In to the BSC6900 Using
the LMT.
Context
The loopback test can be performed on an optical port when the E1/T1 transmission link on a
standard interface is unavailable.
Procedure
Step 1 Perform the loopback test on the local optical port.
Table 17-14 Procedure for performing the loopback test on the SDH port
Step Operation
1-1 Run the MML command SET OPTLOP to set a loopback test on a local optical
port. In this command, set Loop type to LOCAL_LOOP(LOCAL_LOOP).
1-2 Run the MML command DSP E1T1 to query Port State.
1-3 Run the MML command SET OPTLOP to stop the loopback test on the optical
port. In this command, set Loop type to NO_LOOP(NO_LOOP).
If... Then...
The command output shows that the The SDH port is available. Go to Step 2.
value of Port State is AVAILABLE
The command output shows that the The SDH port is faulty. Replace the interface
value of Port State is LINK_DOWN board carrying the faulty SDH port.
Step 2 Perform the loopback test on the local fiber optical cable.
Table 17-15 Procedure for performing the loopback test on the local fiber
Step Operation
2-1 Perform fiber physical loopback at the local end, that is, connect the TX end of the
fiber optic cable to the RX end of the fiber optic cable.
2-2 Run the MML command DSP E1T1 to query Port State.
Step Operation
2-3 Stop the fiber optic cable physical loopback at the local end.
If... Then...
The command output shows that the The local fiber optic cable is available. Go to
value of Port State is AVAILABLE Step 3.
The command output shows that the The local fiber optic cable is faulty. Replace
value of Port State is LINK_DOWN the faulty fiber optic cable.
Table 17-16 Procedure for performing the loopback test on the peer optical port
Step Operation
3-1 Run the MML command SET OPTLOP at the local end, set Loop type to
REMOTE_LOOP(REMOTE_LOOP).
3-2 l If the peer equipment is the BSC6900, run the MML command DSP OPT at
the peer end to query the state of the optical port.
l If the peer equipment is not the BSC6900, contact the maintenance personnel
for the peer equipment to query the state of the optical port.
3-3 Run the MML command SET OPTLOP to stop the loopback test on the optical
port. In this command, set Loop type to NO_LOOP(NO_LOOP).
If... Then...
The command output shows that the Contact Huawei technical support.
optical port state is available
The command output shows that the port Contact the maintenance personnel for the peer
state is faulty equipment to rectify faults in the peer
equipment or the transport network.
----End
Prerequisites
l You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
l The peer end (NodeB, MGW, MSC, or SGSN) supports the Two-Way Active
Measurement Protocol (TWAMP).
l You have purchased the license of the TWAMP.
Procedure
Step 1 Enable the TWAMP and start the active test.
1. Run the ADD TWAMPCLIENT command to add a client and configure the IP
addresses of the local and peer ends.
2. Run the ADD TWAMPSENDER command to set the parameters for the active test.
After the command is successfully executed, the test is started.
Step 2 Run the DSP TWAMPSENDER command to query the test results.
Table 17-17 shows QCIs recommended on interfaces. Check whether the test results meet the
QCIs recommended on interfaces.
----End
18 Appendix
This chapter provides communication ports on and the commissioning checklist of the
BSC6900.