BSC6900 GU Problem Preventive Guide (20130821-V1.9) : Date Aug 21, 2013

BSC6900 GU Problem Preventive
Guide (20130821-V1.9)
Version 20130821-V1.9
Date Aug 21, 2013
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either expressed 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 the warranty of any kind, expressed or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Web site: http://www.huawei.com
Email: [email protected]
10/3/2013 Page |i
Huawei Propreitery – Restricted Distribution
10/3/2013 P a g e | ii
BSC6900 GU Problem Preventive Guide (20130821-V1.9) Security
About This Document
Change History
Date Version Description Author
Aug 21, 2013 1.9 Initial version Sugumar Rajarathinam
10/3/2013 P a g e | iii
Contents
Change History......................................................................................................................................................iii
1 Introduction.................................................................................................................................1-1
1.1 Purpose..........................................................................................................................................................1-1
1.2 Acronyms and Abbreviations ........................................................................................................................1-1
2 Misc. topics..................................................................................................................................2-2
2.1 How to check UMTS Cell Health State?.......................................................................................................2-2
2.2 How to redefine NE alarm severity from M2000? ........................................................................................2-3
2.3 How to configure NodeB Timezone/Daylight Savings Time using MML command?..................................2-5
2.4 How to enable IP Path Check on RNC? ........................................................................................................2-5
2.5 How to modify maintenance mode of NodeB/GSM BTS? ...........................................................................2-6
2.6 How to configure alarm mask rule for NodeB/GSM BTS? ..........................................................................2-8
2.7 How to synchronize NE alarms in M2000? ................................................................................................2-10

2.8 How to Ping GSM BTS from BSC?............................................................................................................ 2-11
2.9 How to Ping UMTS NodeB from BSC? .....................................................................................................2-12
2.10 How to remove WBBP Board that is not in service from NodeB?............................................................2-12
2.11 How to remove UBRI Board that is not in service from BTS? .................................................................2-13
2.12 How to swap BB resources(WBBP) in UL group for NodeB? .................................................................2-15
2.13 How to add new NTP Server IP configuration in BSC and route for it on NodeB?..................................2-19
2.14 How to install mediation software (for NEs) in M2000 via web browser? ...............................................2-20
2.15 Troubleshoot issues during addition of a new NodeB to RNC..................................................................2-21
2.16 How to resolve GSM BTS Activation error due to “No DPC match for DSP type A”?............................2-23
2.17 How to check NodeB software upgrade result and time it was performed?..............................................2-23
2.18 How to check IP configuration of Gb from BSC?.....................................................................................2-23
2.19 How to check and modify channel types of TRX on GSM BTS using MML commands?.......................2-24
2.20 How to set TCH Rate Adjust for TRX using MML commands?...............................................................2-24
2.21 How to modify Area Code information of a cell using MML commands? ...............................................2-25
2.22 How to identify (remotely) the installed MRRU type (GSM/UMTS) using MML commands?...............2-25
2.23 How to upload NodeB License to M2000 ? ..............................................................................................2-27
2.24 How to activate newly uploaded NodeB License on the M2000 Server? .................................................2-27
2.25 How to find and correct main BCCH fault during cutover/new GSM site?..............................................2-28
10/3/2013 Page |v
2.26 How to update periodic location update timer (T3212) for GSM and UMTS?.........................................2-31
2.27 How to check NodeB configuration activation status and its data integrity? ............................................2-31
2.28 How to find number of Mobile Stations (and their IMSI) attached to a specific GSM cell? ....................2-33
2.29 How to monitor packet loss at NodeB/GSM BTS/BSC Ethernet port from M2000? ...............................2-33
2.30 How to reconfigure GSM/UMTS network parameters?............................................................................2-38
2.31 How to reparent Base Stations?.................................................................................................................2-39

2.32 How to download HedEx library for a network element (NE) from Huawei support website?................2-40
2.33 How to add new library of a network element (NE) to HedEx program? .................................................2-42
2.34 How to diagnosis performance result loss of a network element in M2000?............................................2-43
10/3/2013 P a g e | vi
1 Introduction
1.1 Purpose
This document describes procedures to resolve GSM or UMTS miscellaneous issues.
1.2 Acronyms and Abbreviations
CME Configuration Management Express
GU GSM and UMTS
GUI Graphical User Interface
WBBP WCDMA Baseband Processing unit
WMPT WCDMA Main Processing and Transmission unit
UEIU Universal Environment Interface Unit
UPEU Universal Power and Environment Interface Unit
MML Man-Machine Language
LLD Low Level Design
LMT Local Maintenance Terminal
RNC Radio Network Controller
10/2/2013 错误！未知的文档属性名称 P a g e | 1-1

2 Misc. topics
2.1 How to check UMTS Cell Health State?

This section describes to run health check on a cell when you encounter UMTS cell related alarms.
Procedure
1. From RNC, run the MML command DSP UCELLCHK:CHECKSCOPE=CELLID,CELLID=nnnnn; to
query the health check of a UMTS cell.
2. Verify from the output of the command, which would be a long list, whether the cell is activated, cell is
unblocked, cell is setup, cell is available, whether cell is barred (idle or connected mode), compare
the maximum transmit power of cell configured on RNC & NodeB, HSDPA/HSUPA is configured and
supported etc.
3. If the cell is not activated or blocked or cell is not setup, the output of the command will be shorter.
Please follow appropriate procedures to activate the cell, to unblock the cell and to setup the cell.
Partial output of DSP UCELLCHK:

2.2 How to redefine NE alarm severity from M2000?

This section describes to run redefine NE alarm severity from M2000.
Procedure
1. Launch M2000 client and login to M2000.
2. Choose Monitor > Alarm Settings > NE Alarm Settings from M2000 client. The NE Alarm Settings
window is displayed.
3. Select Severity Redefinition tab; click Edit button and choose Add. The Add Severity Redefinition
window is displayed as shown below:

4. Select NE from the left pane. The right pane of the window will be populated with alarms applicable
for this NE sorted based on their default alarm severity.
5. Select the alarm for which you would like to redefine the severity and choose the desired alarm
severity from Redefined Level list box. Click OK button to apply the changes.
6. Click on the Query button from the Severity Redefinition tab. The Query Severity Redefinition
window is displayed. Select NE from the left pane and select all the alarm levels (Critical, Major, Minor
and Warning) and click OK button.
7. The query output will be displayed with list of alarms whose severity had been redefined (Redefined
Level) from their default alarm severity (Original alarm level column) as shown below:
8. When the alarm (whose severity is redefined) is reported, verify from M2000’s browse alarm window,
it displays with redefined severity instead of its default alarm severity.

2.3 How to configure NodeB Timezone/Daylight Savings

Time using MML command?
This section describes how to configure Time zone and Daylight savings time on NodeB using MML
command.
Procedure
1. From DBS39000 WCDMA (NodeB), run the MML command LST TZ; to list the current time zone and
Daylight savings time configuration.
2. If Time Zone and Daylight savings time needs to be configured, run the following MML command:
SET
TZ:ZONET=GMT-0700,DST=YES,SM=WEEK,SMONTH=MAR,SWSEQ=SECOND,SWEEK=SUN,ST=02&00&00,EM=WEEK,EMO
NTH=NOV,EWSEQ=FIRST,EWEEK=SUN,ET=02&00&00,TO=60;
Note: ZONET= GMT-0700, please choose appropriate time zone for the parameter ZONET
(command given here shows GMT-0700)
2.4 How to enable IP Path Check on RNC?

This section describes how to enable IP Path Check flag on RNC for IP PATHs to NodeBs if required.
NOTE: Please note that Path Fault Alarms will be reported to M2000 if the IP Path Check flag is enabled and
NodeBs are either disconnected or not powered-up.
Procedure
1. From RNC, run the MML command LST IPPATH:ANI=y,PATHID=x; to list the IP Path configuration.
Check the value of “IP path check flag” field.
2. If “IP path check flag” is disabled, run the following MML command to enable it:
MOD IPPATH:ANI=y,PATHID=x, ITFT=IUB,PATHCHK=ENABLED,ECHOIP=”10.x.y.x”,PERIOD=5,CHECKCOUNT=5,

ICMPPKGLEN=64,CHECKT=UDP;
Note: ECHOIP= NodeB IP address, IP Path Check Type can be either UDP or ICMP

2.5 How to modify maintenance mode of NodeB/GSM

BTS?
This section describes how to verify and modify NodeB/GSM BTS’s Maintenance mode as NORMAL to ensure
reporting of its alarms/events to M2000.
Procedure
1. Choose Maintenance > Maintenance Mode from M2000 Client. The Maintenance Mode window is
displaued.
2. Click on Query Maintenance Mode (Lens) icon from the Maintenance Mode window. The Query
Maintenance Mode window is displayed.
3. Expand the NodeB; click the check-box against the desired NodeB. Click OK button and then CLOSE
button to close the window.
4. The output of the query should show the Current NE Maintenance Mode as NORMAL as shown below:

5. If the Current NE Maintenance Mode is not NORMAL, need to execute the following steps to configure
the Maintenance Mode as NORMAL.
6. Click on Set Maintenance Mode (Pencil) icon from the Maintenance Mode window. The Set Maintenance
Mode window is displayed.
7. Expand the NodeB; click the check-box against the desired NodeB. Verify NE Mode is set to NORMAL
Click OK as shown below.

8. Click OK again to confirm that you would like to set the maintenance mode.
9. Click CLOSE to close the Set Maintenance Mode window.
10. Repeat steps 2 through 4 to verify the maintenance mode of NodeB is set to NORMAL.
NOTE: You can alternatively check and modify the maintenance mode of NodeB/BTS through MML
commands: DSP MNTMODE & SET MNTMODE (from NodeB) and LST BTSMNTMODE and SET
BTSMNTMODE (from BSC).
2.6 How to configure alarm mask rule for NodeB/GSM

BTS?
This section describes how to mask an alarm for NodeB or GSM BTS from M2000.

Procedure
2. Choose Monitor > Alarm Settings > Mask Rules from M2000 client. The Mask Rules window is
displayed.
3. Click on Add and choose Alarm Mask Rule. The Add Alarm Mask Rule window is displayed.
4. Click the check box against Alarm Name and click on the browse button as shown below. The Select
Alarm window is displayed.
5. From Select Alarm window, expand DBS3900 WCDMA from the left pane. Select the desired alarm
(e.g., Inter-System Communication Failure) and click > icon to move it to the right pane of the window.
Click OK button to close the Select Alarm window.
6. Choose Alarm Source tab from Add Alarm Mask Rule window. Click on the Custom radio button and
click Add button to choose NE.
7. Choose required UMTS NodeB from the left pane by expanding the RNC. Move it to the right pane by
clicking > icon. Once the NodeB is moved to right-pane, a check will appear on the left pane to
confirm that NodeB is selected. Click OK button from NE window and then click OK button from Filter
window.
NOTE: If you need to choose just BSC/RNC not including, type the name of the BSC/RNC in the
Name text box, select it from the left-pane to move it to right-pane.
8. Select Next button on the Add Alarm Mask Rule window. (Optional) Select Start Time, End Time if you
prefer to mask an alarm for known period of time; otherwise you leave these check boxes unchecked.
9. Verify Enable check box is selected. Enter description for the alarm mask rule in Memo field.

10. Click Finish button. The alarm mask rule will be created and will be displayed as shown below.
11. Verify in the browse current alarm window that the masked alarm is not reported.
12. If you want to add more NEs to an existing alarm rule, highlight the alarm from Mask Rules window
and click on Property button.
13. Repeat steps 6 and 7.
14. Verify in the browse current alarm window that the masked alarm is not reported for NEs for which this
alarm mask rule is applied.
15. To delete an existing alarm rule, highlight the alarm from Mask Rules window and click on Delete
button.
16. If you would prefer to leave the alarm mask rule, but don’t wish to mask the alarm anymore, uncheck
the Enable from Mask Rules window and click Apply button.
17. Verify in the browse current alarm window that the alarm is reported once the alarm mask rule is
either deleted or disabled.
2.7 How to synchronize NE alarms in M2000?

This section describes how to synchronize NE alarms in M2000. There are situations (eg., alarm mask rule
has been created for already existing alarms, due to problems such as network interruption or outage) where
the alarm data on the M2000 may be inconsistent with that on the NEs. During such scenarios, you can

manually synchronize the alarm data on the selected NEs with that on the M2000 to obtain the latest alarm
states of the NEs.
Procedure
2. Choose Monitor > Synchronize NE Alarms. The Synchronize NE Alarms window is displayed.
3. Choose required NE from the left pane by expanding the RNC. Move it to the right pane by clicking >
icon. Once the NE is moved to right-pane, a check will appear on the left pane to confirm that NE is
selected. Click OK button.
NOTE: If you need to choose just BSC/RNC not including, type the name of the BSC/RNC in the
Name text box, select it from the left-pane to move it to right-pane
4. In the Confirm dialog box, click yes button if you want to synchronize NE alarms.
2.8 How to Ping GSM BTS from BSC?

This section describes how to PING from BSC to GSM BTS when we want to verify the connectivity between
them is working properly.
Procedure
1. From RNC, run the MML command LST BTS; to query the configuration information of GSM BTS.
From the output of this command, note down the OML Out-BSC Subrack Number and OML Out-BSC
Slot Number for the required BTS by scrolling to right side.
2. From RNC, run the MML command LST BTSIP; to query the communication address of a BTS in IP
Transmission mode. From the output of this command, note down the BSC IP and BTS IP address of
BTS between which you would to verify the connectivity state.
3. From RNC, run the MML command PING IP:SRN=x,SN=yy, SIPADDR=”10.40.x.y”,

DESTIP=”10.n.m.x”, CONTPING=NO; to check the connectivity of the IP layer between BSC and
BTS.
NOTE: For SRN and SN, enter the Subrack and Slot No. values captured from step-1. The Destination IP
address (DESTIP) is the IP address of the GSM BTS – BTS IP from output captured in step-2. The Source IP
Address (SIPADDR) must be the local IP address of the PPP link or the IP Address of the Ethernet Port – BSC
IP address from output captured step-2.

2.9 How to Ping UMTS NodeB from BSC?

This section describes how to PING from BSC to UMTS NodeB when we want to verify the connectivity
between them is working properly.
Procedure
1. From RNC, run the MML command LST UNODEB:LSTFORMAT=HORIZONTAL; to query the
configuration information of UMTS NodeB. From the output of this command, note down the NodeB
name and NodeB ID for the required UMTS NodeB.
2. From RNC, run the MML command LST UNODEB:LSTTYPE=ByNodeBId, NODEBID=nn,

LSTFORMAT=HORIZONTAL; to query the information of a specified NodeB. At the very bottom of
this command output, note down the Local IP address (NodeB IP address), Logical IP address (RNC
IP address), Subrack and Slot number.
3. From RNC, run the MML command PING IP:SRN=x,SN=yy, SIPADDR=”10.40.x.y”,

DESTIP=”10.n.m.x”, CONTPING=NO; to check the connectivity of the IP layer between BSC and
NodeB.
NOTE: For SRN and SN, enter the Subrack and Slot No. values captured from step-2. The Destination IP
address (DESTIP) is the IP address of the UMTS NodeB – from the output captured in step-2. The Source IP
Address (SIPADDR) must be the local IP address of the Ethernet Port – from the output captured step-2.
2.10 How to remove WBBP Board that is not in service

from NodeB?
This section describes how to remove a WBBP board that were used once, but NOT being used currently in
the NodeB, hence reporting unnecessary alarms in M2000.
Caution:
Backup the configuration file (NodeB: BKP CFGFILE) before running the procedure to remove/modify existing
configuration. This will be used to restore the configuration if the service is impacted due to this change. Make
sure that only whose NE’s configuration requires to be updated is selected on the left-pane of the MML
navigation tree.
Procedure
1. From DBS3900 WCDMA, run the MML command DSP BRD; to query the status of the board. Verify
that the operational state of WBBP boards in slot-0 to slot-3. From the output of this command,
identify the board that needs to be removed (e.g., board that was used earlier is physically not
present in the BBU), whose operational state should NOT be enabled.

2. From DBS3900 WCDMA, run the MML command LST LOCELL; to query the configuration
information of UMTS local cells. From the output of this command, note down the UL BB Resource
Group and DL BB Resource Group numbers.
3. From DBS3900 WCDMA, run the MML command LST DLGROUP; and LST ULGROUP; commands
to query the resource of downlink and uplink BB resource groups. From the output of this command
output, note down the slot numbers of the DL and UL process unit.
NOTE: Verify that the board, you are attempting to remove is not being used; the slot number of board
listed from these commands output show that those boards are being used.
4. From DBS3900 WCDMA, run the MML command LST RRUCHAIN command to query the
configuration of RRU chain. From the output of this command output, note down the RRU Chain
numbers that correspond to the board you would like to remove. The Head Slot No. will show the slot
number of the WBBP boards.
5. From DBS3900 WCDMA, run the MML command LST RRU command to query the configuration of
RRU. From the output of this command output, note down the Cabinet/Subrack/Slot No of RRU that
correspond to the RRU CHAIN noted from the above step-4.
6. From DBS3900 WCDMA, run the MML command RMV RRU:CN=0,SRN=8x,SN=yy; to remove an
RRU. Repeat this step for the RRU that need to be removed.
NOTE: For CN, SRN and SN, enter the Cabinet No, Subrack No. and Slot No. values captured from
step-5.
7. From DBS3900 WCDMA, run the MML command RMV RRUCHAIN:RCN=x; to remove an RRU
Chain. Repeat this step for the RRU Chains that need to be removed.
NOTE: For RCN, enter the RRU Chain No. value captured from step-4.
8. From DBS3900 WCDMA, run the MML command RMV BRD:SN=x; to remove the WBBP board that
is not in service.
9. From DBS3900 WCDMA, run the MML command DSP BRD; to verify the board that is removed not
listed in the output. Verify that any alarms that are present due to this board had been cleared from
M2000 alarm reporting.
2.11 How to remove UBRI Board that is not in service from

BTS?
This section describes how to remove a UBRI board that were used once, but NOT being used currently in the
BTS, hence reporting unnecessary alarms in M2000.

Caution:
Backup the configuration file (BSC: BKP DB) before running the procedure to remove/modify existing
configuration. This will be used to restore the configuration if the service is impacted due to this change. Make
sure that BSC under which this BTS is configured is selected on the left-pane of the MML navigation tree.
Procedure
1. From BSC, run the MML command LST BTSBRD:IDTYPE=BYNAME,BTSNAME=”bts-name”; to
query BTS board information.
2. From BSC, run the MML command LST BTSRXUCHAIN:IDTYPE=BYNAME,BTSNAME=”bts-name”;

to query the configuration of BTS RXU chain. From the output of this command output, note down the
RXU Chain numbers that correspond to the board you would like to remove. The Head Slot No. will
show the slot number of the UBRI/GTMU boards.
NOTE: Verify that the UBRI board, you are attempting to remove is not being used; the slot number of
board listed from these commands output show that those boards are being used.
3. From BSC, run the MML command LST BTSRXUBRD:IDTYPE=BYNAME,BTSNAME=”bts-name”;

command to query the configuration of BTS RXU. From the output of this command output, note
down the Cabinet/Subrack/Slot No of RRU that correspond to the RXU CHAIN noted from the above
step-2.
4. From BSC, run the MML command, RMV

BTSTXUBRD:IDTYPE=BYNAME,BTSNAME=”bts-name”,RXUIDTYPE=RXUNAME,RXUNAME=”rxu
-0-6x0-name”; to remove an RXU. Repeat this step for the RXU that need to be removed.
NOTE: For RXUNAME, enter the RXUNAME value captured from step-3.
5. From BSC, run the MML command RMV

BTSTXUCHAIN:IDTYPE=BYNAME,BTSNAME=”bts-name”,RCN=x”; to remove an RXU Chain.
Repeat this step for the RRU Chains that need to be removed.
NOTE: For RCN, enter the RXU Chain No. value captured from step-3.
6. From BSC, run the MML command RMV BTSBRD:

IDTYPE=BYNAME,BTSNAME=”bts-name”,CN=0,SRN=0,SN=x; to remove the UBRI board that is
not in service.
7. From BSC, run the MML command LST BTSBRD; to verify the board that is removed not listed in the
output. Verify that any alarms that are present due to this board had been cleared from M2000 alarm
reporting.

2.12 How to swap BB resources(WBBP) in UL group for

NodeB?
This section describes sample configuration required on RNC and NodeB when there is any requirement to
swap BB resources (default WBBP Slot-3 will be used in UL group for fist carrier and Slot-2 (or 0 or 1) will be
used for UL group for secondary UMTS carriers).
Procedure
1. From RNC, execute the following MML commands to block UMTS cell (required before removing
local cell from NodeB):
BLK UCELL:CELLID=39121,PRIORITY=HIGH;
2. From NODEB, execute the following commands to remove existing configuration:
a. To remove RRU:
RMV RRU:CN=0,SRN=80,SN=0;
b. To remove RRU Chain
RMV RRUCHAIN:RCN=0;
RMV RRUCHAIN:RCN=1;

RMV RRUCHAIN:RCN=2;
RMV RRUCHAIN:RCN=3;
c. To remove DL dual group
RMV DLDUALCELLGRP:FIRSTLOCELL=39121,SECONDLOCELL=39125;
d. To remove UMTS Local cells
RMV LOCELL:LOCELL=39121;
e. To remove existing UL groups (UL BB Group 0:slot-3 & BB Group 1: slot-2)
RMV ULGROUP:ULGROUPN=0;
RMV ULGROUP:ULGROUPN=1;
3. From NODEB, execute the following commands to add new configuration:
a. To add new RRU Chain
ADD RRUCHAIN:RCN=0,TT=CHAIN,BM=COLD,HSN=2,HPN=0;

b. To add RRU
ADD
RRU:CN=0,SRN=80,SN=0,TP=TRUNK,RCN=0,PS=0,RT=MRRU,RS=UO,RN="0-80-0",RX
NUM=2,TXNUM=2;
ADD
NUM=2,TXNUM=2;
ADD
NUM=2,TXNUM=2;
ADD
NUM=2,TXNUM=2;
c. To add UL group (UL BB Group-0 with WBBP in Slot-2 and Group-1 with WBBP in Slot-3)
ADD ULGROUP:ULGROUPN=0,DEMMODE=DEM_2_CHAN,SNE1=2;
ADD ULGROUP:ULGROUPN=1,DEMMODE=DEM_2_CHAN,SNE1=3;
d. To add UMTS Local cell
ADD
LOCELL:LOCELL=39121,STN=79,SECN=0,SECT=REMOTE_SECTOR,TTW=FALSE,SRN1=8
0,ULFREQ=4162,DLFREQ=4387,MXPWR=400,HISPM=FALSE,RMTCM=FALSE,VAM=FALSE
;
ADD
;
ADD
;
ADD
;
ADD
LOCELL:LOCELL=39125,STN=79,SECN=0,SECT=REMOTE_SECTOR,ULGROUPNO=1,TTW=

FALSE,SRN1=80,ANT1N=ANT0B,ULFREQ=4141,DLFREQ=4366,MXPWR=400,HISPM=FAL
SE,RMTCM=FALSE,VAM=FALSE;
ADD
ADD
ADD
e. To add DL dual group
ADD DLDUALCELLGRP:FIRSTLOCELL=39121,SECONDLOCELL=39125;
4. From RNC, run the following commands to unblock UMTS cells:
UBL UCELL:CELLID=39121;

2.13 How to add new NTP Server IP configuration in BSC

and route for it on NodeB?
This section describes sample configuration required on RNC and NodeB to add new NTP Server IP
configuration.
Note: Please remember to add IP routes to the new NTP server when creating CME scripts for new NodeBs.
Procedure
1. To add new NTP server in RNC, run the following MML command:
ADD SNTPSRVINFO:IP=”10.100.99.x”,PT=123;
2. To add IP routes and set SNTP client information on all NodeBs that belong to this RNC, run the
following MML command from NodeB:
ADD
IPT:SN=7,SBT=BASE_BOARD,DSTIP=”10.100.99.x”,DSTMASK=”255.255.255.255”,
RTTYPE=NEXTHOP,NEXTHOP=”10.41.y.1”,DESCRI=”To NTP”;
SET SNTPCLTPARA:IP1=”10.100.99.x”,SP=10,SW=ON;
3. To PING NTP Server from NodeB, run the following MML command from NodeB:
PING:SN=7,SRCIP=”10.41.a.b”,DSTIP=”10.100.99.x”,CONTPING=DISABLE,APPTI
F=NO;
Note: Run the following command only if required to remove any old NTP server configuration.
4. To remove old NTP server (recommended during maintenance), run the following MML command
from RNC:
RMV SNTPSRVINFO:IP=”10.100.99.n”;
5. To verify RNC and NTP server synchronization is success, run the following MML command from
RNC:
LST SNTPCLTLATESTSUCCDATE;
6. To remove IP routes to old NTP server on all NodeBs, run the following MML command from RNC:
RMV
IPRT:SN=7,SBT=BASE_BOARD,DSTIP=”10.100.99.n”,DSTMASK=”255.255.255.255”,RTT
YPE=NEXTHOP,NEXTHOP=”10.41.y.1”;

2.14 How to install mediation software (for NEs) in M2000

via web browser?
This section describes how to install mediation software (for NE – NodeB, BSC, MSC etc.) using OSS
Self-Maintenance Unit (OSMU).
Caution
The following procedure is recommended to be performed during maintenance window since it would interrupt
any existing M2000 client user operations and requires the user to logout and login to M2000.
Prerequisites
• You have the network device permission to access the data.
• Required mediation software for NE has been downloaded and available on the PC.
Procedure
1. Open a web browser, type in the following address in the address bar:
https://10.100.100.4:31123 (where 10.100.100.4 is M2000 IP address)
2. Login to OSMU by entering “omcuser” as username & password and verify code as displayed.
3. Click the “General” icon from the workspace screen.
4. Click on the Mediation Package Management from the left-pane of the screen.
5. Verify by browsing through the “Installed Mediation” tab that the required mediation software is not
installed.

6. Click on the Mediation Installation tab. Click “Upload” button and choose the required mediation
software that was saved in the PC. Wait for the file to be uploaded the file integrity check to be
completed.
7. Once the uploaded mediation software shows up under “Mediation Packages to Be Installed” text box,
select it and click “Install” button.
8. Once the installation is successful, logout from OSMU by clicking Logout option available on the right
top corner of the screen.
NOTE: M2000 client users will receive a broadcast message that the mediation software is to be
installed and any modification from M2000 is not allowed. They’ll also be prompted to logout and login
to M2000.
2.15 Troubleshoot issues during addition of a new NodeB

to RNC
This section describes checklist of troubleshooting methods that can be performed when you encounter errors
while building new UMTS site.
Procedure
1. Before creating CME scripts to build configuration for physical NodeB, verify the current software
version running on the NodeB. Choose the NodeB version closer to the NodeB’s current software
version, but should be greater than current software version.
2. After adding physical NodeB to M2000 (by transferring NodeB configuration file), if the NE (NodeB) is
not connected in M2000, perform the following steps to troubleshoot:
a. From M2000 topology manager, right-click on the NodeB and verify that you don’t see
“Enable NE Connection” option. If you do see that option, it means that the connection
between NE and EMS is disabled. Choose “Enable NE Connection” to enable the connection
to verify whether the NodeB connects to M2000.
b. Open a SSH session to M2000 (10.100.100.4 Port 22), login using root/root. Run “ping
10.40.x.x” where 10.40.x.x is NodeB’s OM IP address to verify the NodeB is reachable. If it’s
still not reachable, continue to next step.
c. From NodeB configuration, check the device IP address, subnet mask of NodeB, VLANMAP
configuration for next-hop (router) address and IP route to M2000.
3. After adding physical NodeB to M2000 (by transferring NodeB configuration file), if SCTP links, IP
Paths between NodeB and RNC are not up, perform the following steps to troubleshoot:
a. From RNC MML, PING to NodeB’s service IP address to verify whether NodeB is reachable.
Refer to “How to Ping NodeB from RNC?” section in this guide for details.

b. From NodeB configuration, check the device IP address, subnet mask of NodeB, MTU
settings of NodeB’s Ethernet port, VLANMAP configuration for next-hop (router) address and
IP route to RNC.
c. From RNC MML, verify the Ethernet IP addresses and IP routes to (NodeB / Iub interface)
have been configured using LST ETHIP and LST IPRT
4. If the NodeB is not reachable from RNC and M2000 after performing step-3 and step-4, check
transport side connectivity and configuration.
5. Verify whether correct mediation software (correspond to NodeB software) had been installed in
M2000. Refer to section “How to install mediation software (for NEs) in M2000?” in this guide.
6. After adding NodeB to RNC, if one or two of the UMTS cells, keep reporting RF maintenance failure,
check the fiber connections between RRU and BBU port perform the following steps to resolve the
issue:
a. Remove and reseat the optical fiber.
b. Check the fiber connectors are not loosened.
c. Clean the fiber connectors (if they are dirty) using alcohol.
d. Replace the optical fibers.
7. If “Board Startup Abnormal Alarm” is reported (with cause=Non-Key Parameter Configuration Failure)
for MRRU, perform the following steps to resolve the issue:
a. Remove and reseat the optical fiber.
b. Check the fiber connectors are not loosened.
c. Clean the fiber connectors (if they are dirty) using alcohol.
d. Swap the fibers between UMTS and GSM RRUs.
e. Replace the optical fibers.
8. After adding NodeB, make sure the maintenance mode is configured to be NORMAL; otherwise
alarms will not be reported to M2000.
9. Remember to allocate licenses after adding new NodeB.
10. If you’ve to remove logical NodeB from RNC using CME, browse through the list of RMV (MML)
commands before executing to make sure it does not include removing any RNC specific
configuration.
11. Before going live, upgrade (if new version is available) the software of the NodeB to the recent
version.

2.16 How to resolve GSM BTS Activation error due to “No

DPC match for DSP type A”?
This section describes how to resolve the error due to “No DPC match for DSP Type A” interface when
attempting to activate GSM BTS from CM Express. This error will be reported when you have GSM Cell’s
OSP map configured with incorrect OSP code.
Procedure
1. From CM Express, note down the configured “Cell OSP Map” value for the GSM cells.
2. From BSC, run “LST N7DPC” MML command; from its output, find the DSP Type (7th column) of “A”
interface. Make a note of the OSP index (2nd column) that corresponds to “A” interface.
3. From BSC, run “LST OPC” MML command; from its output, find OSP index (1st column) whose value
matches the value noted in step-2. Make a note of the OSP Code (6th column) that corresponds to
this OSP index.
4. Make sure the value of OSP index captured in step-3 should have been entered as Cell OSP Map
value. If not, update the Cell OSP Value of GSM cells in the CME.
5. Activate GSM BTS in the CME and verify that the activation is successful.
2.17 How to check NodeB software upgrade result and

time it was performed?
In order to find when the NodeB software upgrade was performed and for the upgrade result, you can run
from DBS3900 WCDMA, the MML command “LST UPGRADEREC” which will list a maximum of 10 recent
NE upgrade result records. The output will display the upgrade time, upgrade result, version before upgrade,
version after upgrade and upgrade failure cause (if any).
2.18 How to check IP configuration of Gb from BSC?

In order to find the configured IP address configured for Gb interface run the MML command “LST
NVSLREMOTE” which will display the IP configured for the remote network service virtual link (NVSL). You
can alternatively use “LST IPRT” command to find the IP addresses correspond to Gb interface (provided
correct description has been added for each IP route)

2.19 How to check and modify channel types of TRX on

GSM BTS using MML commands?
This section describes how to check and modify channel types of TRX on GSM BTS using MML commands
from BSC.
Procedure
1. From BSC, run “LST GTRX:IDTYPE=BYID,BTSID=nnn;” MML command; from its output, find the
required cell index for whose TRX, you would like to check the assigned channel types..
2. From BSC, run “LST GTRXCHAN: :IDTYPE=BYID,CELLID=mmm;” MML command. This command
output will display the information about channels on TRXs of this cell.
3. From BSC, run “SET GTRXCHAN: :IDTYPE=BYID,TRXID=yyy;” MML command, to modify TRX and
required channel attributes. Enter the appropriate channel number and channel type.
NOTE: For Channel Type, Dynamic PDCH must not be assigned to built-in PCUs. Use LST
GCELLGPRS command from BSC, to find out whether you’ve built-in PCU or external PCU.
2.20 How to set TCH Rate Adjust for TRX using MML
commands?
This section describes how to check and modify channel types of TRX on GSM BTS using MML commands
from BSC.
Procedure
1. From BSC, run “LST GTRXDEV;” MML command to find out whether TCH Rate Adjust Allow is ‘Yes’
or ‘No’.
2. From BSC, run “SET GTRXDEV :IDTYPE=BYID,TRXID=nnn, TCHAJFLAG=Yes” MML command to

set the TCH Rate Adjust to ‘Yes’. This would allow the cell to dynamically change a channel from
full-rate to half-rate or half-rate to full-rate.
3. From BSC, run “SET GTRXDEV :IDTYPE=BYID,TRXID=nnn, TCHAJFLAG=No” MML command to

set the TCH Rate Adjust to ‘Yes’. This would prevent conversion between full rate and half rate and is
restored to the previous rate mode.

2.21 How to modify Area Code information of a cell using

MML commands?
This section describes how to modify Area Code information of any existing cells using MML commands from
RNC.
Procedure
1. From RNC, run LST UAC:LSTFORMAT=HORIZONTAL; MML command and look for the Location
Area Code, Routing Area code and Service Area Code (can be seen in the beginning of the display)
to list the configured LAC, RAC and SAC.
2. From RNC, run “LST UCELL;” (for UMTS cell) MML command to find the configured value of Service,
Location and Routing Area codes of the required cell.
3. From RNC, run MOD UCELLACINFO command to set modify the area code of a cell:
To modify RAC:
“MOD UCELLACINFO :CELLDID=yyyy,CFGRACIND=REQUIRE, RAC=nnn” MML (yyyy- cell ID and nnn- RAC).
To modify LAC:
“MOD UCELLACINFO :CELLDID=yyyy, LAC=zzzz” MML (yyyy- cell ID and zzzz- LAC).
To modify SAC:
MOD UCELLACINFO :CELLDID=yyyy, SAC=zzzz” MML (yyyy- cell ID and ssss- SAC).
4. From RNC, run “LST UCELL;” (for UMTS cell) MML command to verify that the required area code
information of cell is modified successfully.
2.22 How to identify (remotely) the installed MRRU type

(GSM/UMTS) using MML commands?
This section describes how to identify MRRU type remotely using MML command. This will be helpful during
cutover or initial turn-up of new sites.
Procedure
1. From RNC, run “DSP
BTSELABEL:IDTYPE=BYID,BTSID=NNN,QRYTYPE=BRD,CN=0,SRN=60,SN=0;” MML command
to identify the MRRU type of GSM remote radio units. The board type and its description will identify
the type of radio unit that is connected as shown in the following example:

2. From DBS3900, run DSP BRDMFRINFO:CN=0,SRN=80,SN=0; command to identify the MRRU

type of GSM remote radio units. The board type and its description will identify the type of radio unit
that is connected as shown in the following example:

3. The following table can be used as a reference to compare the output of MML commands to
distinguish MRRU types.
Board Type Description

WD5M1A2CB1 MRRU Multi-mode Multi-carriers Remote Radio Unit (TX1950-1990MHz/RX1870-1910MHz,-48VDC,1.25G)
WD5M1A2CA1 MRRU Multi-mode Multi-carriers Remote Radio Unit (TX1930-1970MHz/RX1850-1890MHz,-48VDC,1.25G)
WD5MJRUCC50 MRRU V2, Multi-mode Multi-carriers Remote Radio Unit (TX869-894MHz/RX824-849MHz,100-240VAC,2.5G)
2.23 How to upload NodeB License to M2000 ?

This section describes how to upload a NodeB common license to a server through the M2000 client. A NodeB
common license defines the resources available to the NodeBs in a RAN system.
Prerequisite
• You have logged in to the M2000 client.
• The M2000 services are running properly.
• You have obtained a valid common license file.
• You have obtained the ESN from the RAN.
Procedure
1. Choose License > NE License Management > NodeB License Management from M2000 client.
The NodeB License Management window is displayed.
2. In the navigation tree on the left of the License Management window, select an RNC (BSC6900
UMTS or BSC6900 GU). Right-click the node, and then choose Upload. The Open dialog box is
displayed.
3. Select one or multiple licenses to be uploaded, and then click Open.
4. Click the Yes button on the Confirm window after verifying the message displayed on the window.
2.24 How to activate newly uploaded NodeB License on

the M2000 Server?
This section describes how to activate newly uploaded NodeB license to a server. After uploading a NodeB
common license to the server through the M2000 client, you can send the license distribution information to the
NodeBs to grant them the license authorization.

Procedure
1. Choose License > NE License Management > NodeB License Management from M2000 client. The
NodeB License Management window is displayed.
NOTE: If there is no existing NodeB license that is active, skip the steps 2 through 9.
2. On the right side of the navigation tree, select a NodeB license file (if any available) that has been
already activated. The “Activated” column should have the value “Yes”.
3. Select all rows that are displayed under Shared/Basic frame; right-click and select Export. Save this
CSV file as “A” in your computer.
4. Now select the NodeB license file (that is recently uploaded) that has NOT been activated yet. The
“Activated” column should have the value “No”.
5. Select all rows that are displayed under Shared/Basic frame; right-click and select Export. Save this
CSV file as “B” in your computer.
6. Open both A and B files. Copy all the NodeB rows from file “A” and paste them onto file “B” (i.e.,
overwrite the rows of B) one column at a time. CAUTION: If there is any new column in file “B”, assign
the value of 0 for that column.
7. Save the updated B file as “C”.csv format.
8. Select the license file which is not yet activated in M2000 and select all the rows under Shared/Basic
frame. Right-click and choose Import. Click the Yes button on the message window.
9. Choose file “C” (CSV format) and click Open button to import the data.
10. Right-click on the license that needs to be activated and choose “Distribute”. Once the distribution of
the license is completed, verify that this new license becomes activated and the old license file
becomes inactive automatically.
11. (Optional) If specific NodeB(s) require CE license adjustment, update the UL/DL CE license value
accordingly and distribute the license again.
12. (Optional): Right-click on the previously installed NodeB license and select Invalidate.
2.25 How to find and correct main BCCH fault during

cutover/new GSM site?
This section describes how to find whether main BCCH for GSM TRX is faulty during GSM cutover or turning
up new GSM site and how to rectify it.
Please note that when the main BCCH is faulty, another normal TRX in the cell will be used as Main BCCH and
hence the service is not impacted.

Prerequisites
• You have logged in to the LMT.
• The communication between the BSC6900 and the BTS is normal.
Procedure
1. Login to BSC6900 LMT.
2. Click Device Maintenance on the LMT main page. The Device Maintenance tab page is displayed.
3. In the BTS Maintenance tab page, choose BTS Maintenance > Monitor Channel Status. The Monitor
Channel Status tab page is displayed.
4. In the displayed Monitor Channel Status tab page, click Start to monitor the channel status.
5. If you see * next to TRX No, it indicates that the main BCCH is faulty – hence main BCCH TRX mutual
aid occurs in a cell. When the main BCCH is faulty, another normal TRX in the cell will be used as the
main BCCH as shown in the snapshot below:
6. You can also check whether main BCCH is faulty, by running DSP
GCELLSTAT:IDTYPE=BYID,CELLIDLST=nnn; MML command from BSC6900. If the Main BCCH
Mutual Aid field shows ‘Yes’ (as shown below), it means the main BCCH mutual aid occurs in the
system. Please note that the cell is initialized and in the service state.

To clear main BCCH fault:
7. From BSC6900, run DEA GCELL:IDTYPE=BYID,CELLID=nnn; and ACT

GCELL:IDTYPE=BYID,CELLID=nnn; MML commands to deactivate and activate GSM cells.
8. Observe the channel status in Monitor Channel Status screen. Verify that there is no * next to TRX and
main BCCH TRX in the cell is used as main BCCH channel as shown below:
9. From BSC6900, run DSP GCELLSTAT:IDTYPE=BYID,CELLIDLST=nnn; MML command to verify that

the Main BCCH Mutual Aid field shows ‘No’ (as shown below) which means there is no main BCCH fault.
Please note that the cell is initialized and in the service state.

2.26 How to update periodic location update timer (T3212)

for GSM and UMTS?
This section describes how to modify periodic location update timer on GSM cells and UMTS.
Procedure
1. From BSC6900, run the following MML command to modify the periodic location update timer (T3212)
value (e.g., value 20 means 2 hours) of GSM cells:
SET GCELLIDLEBASIC:IDTYPE=BYID,CELLID="nnnn",T3212=yy;
2. From BSC6900, run the following MML command to modify the periodic location update timer (T3212)
value (in hours – for example value 10 means 1 hour) for UMTS (applicable only CS_DOMAIN)
MOD UCNDOMAIN: CNDOMAINID=CS_DOMAIN, T3212=xx;
2.27 How to check NodeB configuration activation status

and its data integrity?
This section describes how to check the NodeB configuration activation status after downloading and
activating NodeB configuration file.

Procedure
1. After NodeB configuration file is transferred to the NodeB, activate the downloaded configuration file,
from DBS39000, by running the following MML command:
SET CFGFILEENB:FLAG=ENABLE,RSTMODE=IMMEDIATELY;
2. After NodeB reset with new configuration file, from BSC6900 run the following MML command to verify
the configuration activation status and verify that the output of the command shows activation status as
success:
DSP CFGFILEACTSTAT;
3. If the output of the command in step-2 shows the activation status as Failure, verify data integrity of
Physical NodeB from CME. Open the planned area; select the desired NodeB and right-click. Choose
“Verify Data Integrity for Physical NodeB” as shown below:
4. Check the output of “Verify Data Integrity for Physical Node” and fix any missing or incorrect
configuration as reported in the result.

2.28 How to find number of Mobile Stations (and their

IMSI) attached to a specific GSM cell?
This section describes how to find number of Mobile Stations (MS) and their IMSI attached to a specific GSM
cell. It would be helpful command during troubleshooting.
Procedure
1. From BSC6900, run the following MML command to find out the number of MS located in a specified
GSM cell:
DSP MSNUM:IDXTYPE=BYCELL,IDTYPE=BYID,CELLID=nn,SHOWMSID=NO;
2. From BSC6900, run the following MML command to find out the number of MS located in a specified
GSM cell with their IMSI:
DSP MSNUM:IDXTYPE=BYCELL,IDTYPE=BYID,CELLID=nn,SHOWMSID=YES;
Note: TLLI – Temporary Logical Link Identifier; if IMSI is displayed as 0 denotes initial access of the MS.
2.29 How to monitor packet loss at NodeB/GSM BTS/BSC

Ethernet port from M2000?
This section describes how to monitor packet loss at NodeB, GSM BTS and BSC Ethernet port from M2000.
Procedure
1. From M2000 client’s file menu, choose Monitor > Signaling Trace > Signaling Trace management.
2. You can choose NodeB Link Monitoring (NodeB) or FE/GE monitoring (BSC) or GBTS FE/GE
monitoring (GSM) as shown in the snapshot below to monitor their Ethernet port traffic rates and packet
loss if any.

3. Once you select the desired trace type, click New button to start the trace by entering trace name,
selecting appropriate NE (NodeB, BSC) and enter the required End Time (or uncheck the End Time if
you would like to monitor continuously).
4. Enter port number of NodeB or GSM BTS or BSC’s Ethernet (as shown below) and click Finish to start
the trace. The trace will start successfully (if correct values are entered for each of the parameters) and
status will show as Running.
To monitor NodeB Ethernet Port:

To monitor GSM BTS Ethernet Port:

To monitor BSC Ethernet Port:

5. Right-Click on a running trace (or a trace that is stopped) and select Query Result to view graphical and
tabular data which shows the ports transmit/receive rate and packet loss/error if any. The following
snapshot shows a sample query result.

2.30 How to reconfigure GSM/UMTS network

parameters?
This section provides information to where to find information regarding reconfiguration of
GSM/UMTS networks parameters.
Procedure
1. Open HedEx program and select BSC6900 GU Product Documentation applicable to software
version running on your BSC.
2. Browse through the following paths to find procedures on how to reconfigure GSM or UMTS
network parameters as shown in the snapshot below:
BSC6900 GU Product Documentation > Operation and Maintenance > Configuration Management >
GBSS & RAN Reconfiguration Guide > Reconfiguring the GSM Network
• Reconfiguring a Cell
• Reconfiguring the TRX Power
• Reconfiguring the TRX Assignment
• Changing TRX frequencies

• Changing Neighboring Cell Relationships
BSC6900 GU Product Documentation > Operation and Maintenance > Configuration Management >
GBSS & RAN Reconfiguration Guide > Reconfiguring the UMTS Network
• Reconfiguring a Cell
• Reconfiguring the Channel
• Reconfiguring Neighboring Cells
2.31 How to reparent Base Stations?

This section provides information to where to find information regarding reparenting of GSM base
stations and NodeBs.
Procedure
1. Open HedEx program and select BSC6900 M2000-CME Product Documentation applicable to
software version running on your CME (eg V200R012C00).
2. Browse through the following paths to find procedures on how to reparent GBTS and NodeBs as
shown in the snapshot below:
M2000-CME Product Documentation > Reparenting Base Stations > Reparenting GBTSs

• Introduction to GBTS Reparenting
• Planned Parameters (Intra – GBSC Reparenting)
o Reparenting GBTSs in a GBSC (Static IP, Negotiated Data Files)
• Planning Parameters (Inter – GBSC Reparenting)
o Reparenting GBTSs Between GBSCs of the Same Version (Static IP, Negotiated
Data Files)
M2000-CME Product Documentation > Reparenting Base Stations > Reparenting NodeBs
• Reparenting NodeBs in an RNC
• Reparenting a NodeB between RNCs of the same version
2.32 How to download HedEx library for a network

element (NE) from Huawei support website?
This section provides steps to download HedEx library for a network element from Huawei’s support
website.

Procedure
1. Login to Huawei’s support website (http:support.huawei.com) using your credentials.
2. After you login, under product catalog, click on the required NE (eg. MBSC or GGSN or SSGN)
as shown in the snapshot below:
3. From the Product Documentation tab, click on the product version that matches your current
software version running on your NE (eg. for MBSC V900R014C00)
Note: You have to select product type (as BSC6900 GU) prior to choosing product version.
4. After clicking a specific version, browse through the list of document titles and choose the
desired documentation (eg. Product Documentation) with closer attention to the draft version
and language. Choose most recent version and EN for English.
BSC6900 GU Product Documentation (V900R014C00_05)(HDX)-EN
5. Download the desired documentation (most likely in compressed format) and save it on your
local computer.

2.33 How to add new library of a network element (NE) to

HedEx program?
This section provides steps to add recently downloaded HedEx library of a network element into HedEx
program.
Procedure
1. Extract downloaded HedEx libarary of required network element (NE) and save it (with extension .hdx)
in a known location on your computer.
2. Launch the HedEx program and click on the Admin button on the top of the screen as shown below:
3. Click on the Load HDX File button and load the saved *. Hdx library and upload the required HedEx
libarary file.
4. Once the library is loaded successfully, click on “Home” on the top of the screen.
5. Click on the HedEx file that was loaded in step 3 to verify the library can be opened successfully.

2.34 How to diagnosis performance result loss of a

network element in M2000?
This section provides steps to identify reasons for performance result loss of a network element in
M2000.
Procedure
1. From M2000 client, select Performance > Result Loss Diagnosis from the file menu. A new window
Diagnosis Condition window (as shown in the following snapshot) will open.
2. Select desired object (eg NodeB) from the left pane of the Diagnosis Condition window. Expand the
object to list the measurements available for this object and choose a required measurement (eg Traffic
Measurements per Local Cell).
3. Choose required NE(s) from Object tab under Available Objects and click > button to select that
object(s).
4. Click on the Counter tab and choose required counters; click > button to select the required counters
and choose Period as either 15 minutes or 60 minutes.
5. Enter the period for which you want to diagnosis by inputting start and end date/times. Make sure the
period doesn’t exceed 6 hours if you want to diagnosis 15-minutes or 60-minutes counter as shown in
the snapshot.

Note: Result loss diagnosis can diagnose the result loss issues within 3 days. The selected duration for
each diagnosis task cannot exceed 24 hours. The duration for 5-minute and 15-minute diagnosis tasks
cannot exceed 6 hours.
6. Click Diagnose button on the bottom of the screen. The Result diagnosis screen will open as shown in
the following snapshot.
1- Shows the result loss diagnosis process of the diagnosis tool

2- Provides solutions to result loss
3- Records information about diagnosed result loss, including NE name, period, diagnosis time
segment, result loss causes and remarks.
4- Provides frequently ask questions (FAQs) related to handling suggestions, helping solve
problems.
5- Exports diagnosis results
7. Based on the solution provided in the step above, update (eg, whether time zone, DST information of
NE needs to be updated or enable measuring of the selected counters if that is not enabled) required
configuration to resolve performance result loss.

BSC6900 GU Problem Preventive Guide (20130821-V1.9) : Date Aug 21, 2013

Uploaded by

Copyright:

Available Formats

BSC6900 GU Problem Preventive Guide (20130821-V1.9) : Date Aug 21, 2013

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 GU Problem Preventive Guide (20130821-V1.9) : Date Aug 21, 2013

Uploaded by

Copyright:

Available Formats

BSC6900 GU Problem Preventive

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

About This Document

Aug 21, 2013 1.9 Initial version Sugumar Rajarathinam

2.7 How to synchronize NE alarms in M2000? ................................................................................................2-10

2.31 How to reparent Base Stations?.................................................................................................................2-39

1.2 Acronyms and Abbreviations

CME Configuration Management Express

GU GSM and UMTS

GUI Graphical User Interface

WBBP WCDMA Baseband Processing unit

WMPT WCDMA Main Processing and Transmission unit

UEIU Universal Environment Interface Unit

UPEU Universal Power and Environment Interface Unit

MML Man-Machine Language

LLD Low Level Design

LMT Local Maintenance Terminal

RNC Radio Network Controller

10/2/2013 错误！未知的文档属性名称 P a g e | 1-1

2.1 How to check UMTS Cell Health State?

Partial output of DSP UCELLCHK:

10/2/2013 错误！未知的文档属性名称 P a g e | 2-2

2.2 How to redefine NE alarm severity from M2000?

10/2/2013 错误！未知的文档属性名称 P a g e | 2-3

10/2/2013 错误！未知的文档属性名称 P a g e | 2-4

2.3 How to configure NodeB Timezone/Daylight Savings

2.4 How to enable IP Path Check on RNC?

MOD IPPATH:ANI=y,PATHID=x, ITFT=IUB,PATHCHK=ENABLED,ECHOIP=”10.x.y.x”,PERIOD=5,CHECKCOUNT=5,

10/2/2013 错误！未知的文档属性名称 P a g e | 2-5

2.5 How to modify maintenance mode of NodeB/GSM

10/2/2013 错误！未知的文档属性名称 P a g e | 2-6

10/2/2013 错误！未知的文档属性名称 P a g e | 2-7

9. Click CLOSE to close the Set Maintenance Mode window.

2.6 How to configure alarm mask rule for NodeB/GSM

10/2/2013 错误！未知的文档属性名称 P a g e | 2-8

10/2/2013 错误！未知的文档属性名称 P a g e | 2-9

13. Repeat steps 6 and 7.

2.7 How to synchronize NE alarms in M2000?

10/2/2013 错误！未知的文档属性名称 P a g e | 2-10

2.8 How to Ping GSM BTS from BSC?

3. From RNC, run the MML command PING IP:SRN=x,SN=yy, SIPADDR=”10.40.x.y”,

10/2/2013 错误！未知的文档属性名称 P a g e | 2-11

2.9 How to Ping UMTS NodeB from BSC?

2. From RNC, run the MML command LST UNODEB:LSTTYPE=ByNodeBId, NODEBID=nn,

3. From RNC, run the MML command PING IP:SRN=x,SN=yy, SIPADDR=”10.40.x.y”,

2.10 How to remove WBBP Board that is not in service

10/2/2013 错误！未知的文档属性名称 P a g e | 2-12

2.11 How to remove UBRI Board that is not in service from

10/2/2013 错误！未知的文档属性名称 P a g e | 2-13

2. From BSC, run the MML command LST BTSRXUCHAIN:IDTYPE=BYNAME,BTSNAME=”bts-name”;

3. From BSC, run the MML command LST BTSRXUBRD:IDTYPE=BYNAME,BTSNAME=”bts-name”;

4. From BSC, run the MML command, RMV

5. From BSC, run the MML command RMV

6. From BSC, run the MML command RMV BTSBRD:

10/2/2013 错误！未知的文档属性名称 P a g e | 2-14

2.12 How to swap BB resources(WBBP) in UL group for

2. From NODEB, execute the following commands to remove existing configuration: