BSC6900 V900R012C01 Data Relocation Guide (Only For M2000 Common Version Is V200R010)

BSC 6900 V900R012C01
Data Relocation Guide(Only for M2000

Common Version is V200R010)
Issue
03
Date
2010-07-31
Huawei Technologies Co., Ltd.
Copyright Huawei Technologies Co., Ltd. 2010. 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 commercial contract made between
Huawei and the customer. All or partial products, services, and features described in this document may
not be within the purchased scope or the usage scope. Unless otherwise agreed by 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Release 03 (2010-07-31)
Huawei confidential
iii
BSC 6900 V900R012C01

Data Relocation Guide(Only for M2000 Common Version is
V200R010)
About This Document
About This Document

Author
Prepared by
Li Xueqin, Li Yinghao, Lei Jie
Date
2010-3-23
Reviewed by
Sun Zhentao, Chen Chun, Zhu

Xiangyi, Qin Jun, Wei Lei, Jiang
Qiuxia
Date
2010-03-15
Tested by
Miao Jiongkai, Zhang Min
Date
2010-03-18
Approved by
Dong Qingyang
Date
2010-07-31
History
Issu
e
Details
Date
Author
Approved
by
03
Section 2.1.3"(Optional)
Starting the Centralized NIM
Network Monitoring" is
added.
2010-07-31
Li Yinghao, Li
Peng
Dong Qingyang
Section 2.2"Upgrading NEs"

is added.
Section 5.1"What to Do if the
Relocation Tool Is Not Started
Before NE Upgrade?" is
added.
Section 2.1.4"Starting the
Relocation Tool
upgradeServer" is modified.
Section 2.4"Stopping the
Relocation Tool" is added.
iv
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

About This Document
Issu
e
Details
Date
Author
Approved
by
02
Second issue.
2010-05-27
Lei Jie, Liu

Zhongyong
Dong Qingyang
2010-04-15
Li Xueqin, Li
Yinghao
Dong Qingyang
- Section 2.3.2Configuration
Synchronization is modified.
The operation of configure
synchronization data of
performance monitor is added.
For details, see 2.3.2 IStep 4.
01
Release 03 (2010-07-31)
First issue
Huawei confidential
Contents
1 Overview................................................................................... 1-1
2 Upgrade Procedure....................................................................2-1
2.1 Starting the Relocation Tool...........................................................................................................................2-1
2.1.1 Relocation Preparations.........................................................................................................................2-1
2.1.2 Logging In to the M2000 Server...........................................................................................................2-2
2.1.3 (Optional) Starting the Centralized NIM Network Monitoring............................................................2-2
2.1.4 Starting the Relocation Tool upgradeServer.........................................................................................2-3
2.2 Upgrading NEs...............................................................................................................................................2-3
2.3 Querying the Statuses of Upgrade Tasks........................................................................................................2-4
2.3.1 Checking Whether the Upgrade Task is Complete................................................................................2-4
2.3.2 Configuration Synchronization.............................................................................................................2-6
2.4 Stopping the Relocation Tool.........................................................................................................................2-8
3 Rollback Procedure....................................................................3-1
3.1 Overview........................................................................................................................................................3-1
3.2 Preparing for the Rollback..............................................................................................................................3-1
3.3 Starting the UpgradeServer.......................................................................................................................3-3
3.4 Rollback NE...................................................................................................................................................3-3
3.5 Selecting the Task to Be Rolled Back.............................................................................................................3-3
3.6 Starting Rollback Tasks..................................................................................................................................3-5
3.6.1 Restricted Mode....................................................................................................................................3-5
3.6.2 Checking the Running Status of the Rollback Task..............................................................................3-5
3.6.3 Configuration Synchronization.............................................................................................................3-5
3.7 Rollback Completion......................................................................................................................................3-5
3.8 Running the Script..........................................................................................................................................3-6
4 Relocation Specifications............................................................4-1
5 FAQs......................................................................................... 5-1
5.1 What to Do if the Relocation Tool Is Not Started Before NE Upgrade?........................................................5-1
Overview
In the case of upgrade from the BSC6000 or BSC6810 to the BSC6900, you must relocate the
data of the BSC6000 or BSC6810 on the M2000 to ensure that the history data such as
configuration data, alarm data, and performance data of the BSC6000 or BSC6810 can be
smoothly upgraded. This guide describes the process of relocating NE data on the M2000.
Before upgrading an NE version, you must start the relocation tool on the M2000. After the
relocation tool is started, NE data is automatically relocated. The relocation tool automatically
monitors version changes of NEs. Once the relocation condition of an NE is met, the
relocation tool starts to relocate the data of the NE.
Upgrade Procedure
This guide takes the upgrade from the BSC6000 as an example. The guide is only for
reference. The upgrade from the BSC6810 is similar to the upgrade from the BSC6000.
2.1 Starting the Relocation Tool

2.1.1 Relocation Preparations
To ensure that data relocation is successfully performed on the M2000, you must ensure that
relevant mediation is installed on the M2000 before data relocation.
Step 1 Determine the upgrade path of an NE and the target version of the NE.
Step 2 On the M2000, install the mediation of the target NE version.
Currently, you need to relocate NE data if you upgrade the BSC6000 or BSC6810 to the BSC6900. The
BSC6000 that supports data relocation is the BSC6000 V900R008C01B051 or a later release. The
BSC6810 that supports data relocation is the RAN10.0 and a later release.
Step 3 Determine whether the M2000 northbound performance file interface (NE-based) is used. If
BSC6000 or BSC6810 measurement is enabled, you need to set BSC6900 measurement.
1.
Refer to M2000 Northbound Performance File Interface Developer Guide (NE-Based),

execute Step 1 in section 2.4 Operations Related to Performance Data Export Tool
(NE-Based) to check whether BSC6000 or BSC6810 measurement is enabled.
Log in to http://support.huawei.com/. Choose Software Center > Version Software > Core Network
Product Line > Wireless-OSS > iManager M2000-II > iManager M2000 > iManager M2000
V200R010 > iManager M2000 V200R010C00SPCXXX to obtain iManager M2000
V200R010C00SPCXXX_ENG.rar. After decompressing the rar file, the M2000 Northbound
Performance File Interface Developer Guide (NE-Based) is available in the ENG\07.Northbound
File\File Interface directory.
2.
If BSC6000 or BSC6810 measurement is not enabled, skip the following operations.

Otherwise, continue to execute following operations.
3.
If BSC6000 or BSC6810 measurement is enabled, record period information.
BSC 6900 V900R012C01

5 FAQs
4.
If BSC6900 is already set to be measured, and the period is the same as period recorded
in the 3rd point, skip the following operations. Otherwise, continue to execute following
operations.
5.
Refer to M2000 Northbound Performance File Interface Developer Guide (NE-Based).

Execute step 1 through step 6 of section 2.4 Operations Related to Performance
Data Export Tool (NE-Based) to set BSC6900 measurement. The period must be the
same as the period recorded in the 3rd point.
2.1.2 Logging In to the M2000 Server
Log in to the M2000 server through the telnet or the SSH client.
You can use the telnet and SSH client software such as PuTTY and SecuCRT to log in
to the M2000 server. The methods of using these tools vary according to the on-site
parameter settings of the firewall on the server. If the IP address of the M2000 server is
10.10.10.10, you can run the following command in the command interface:
telnet 10.10.10.10
In the M2000V200R009, you must log in as user root. In the M2000V200R010, log in as user
omcuser.
Initialize the environment variables of the M2000.
@rncbam # . /opt/OMC/svc_profile.sh
In the M2000 HA system, all the operations are performed on only the active node; In
the M2000 SLS system, all the operations are performed on only the master node.
2.1.3 (Optional) Starting the Centralized NIM Network Monitoring

By default, the centralized NIM network monitoring function is disabled in the M2000
V200R010SPC200. To ensure that NIM relocation is successful, you are advised to activate
the NIM components. If the NIM components are not activated, the NIM relocation may fail.
It does not affect the entire relocation.
Run the cst_adm command to activate the centralized NIM network monitoring components.
cst_adm -cmd startcomponent NetWorkIntegrationMonitoring
The command result is as follows:

omcuser@osssvr-1 # cst_adm -cmd startcomponent NetWorkIntegrationMonitoring
StartComponent:NetWorkIntegrationMonitoring
loadProcessSvc:NIMServer*
loadProcessSvc*:NIMServer
loadProcessSvc:NIMServer*
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

Data Relocation Guide(Only for M2000 Common Version
is V200R010)
2 Upgrade Procedure
loadProcessSvc*:NIMServer
sendConvertFuncStateEvent:SvrDc_Module_Protocol_NbMml:SvrDc_Module_Protocol_NbM
ml:createModule
sendConvertFuncStateEvent:SvrModule_ComDataDriver_Impl:SvrModule_ComDataDriver_
Impl:createModule
sendConvertFuncStateEvent:SvrModule_StateDriver_Impl:SvrModule_StateDriver_Impl
:createModule
sendConvertFuncStateEvent:NIMSvr_AccMgr:NIMSvr_AccMgr:createModule
sendConvertFuncStateEvent:NIMSvr_BTSMonitor:NIMSvr_BTSMonitor:createModule
sendConvertFuncStateEvent:NIMSvr_Obt:NIMSvr_Obt:createModule
sendConvertFuncStateEvent:NIMSvr_Ogm:NIMSvr_Ogm:createModule
sendConvertFuncStateEvent:NIMSvr_Upgrade:NIMSvr_Upgrade:createModule
sendConvertFuncStateEvent::SvrFixture_Dc_NeEngine_Impl:createNeEngineStateSynch
2.1.4 Starting the Relocation Tool upgradeServer

Run the start_UpgradeServer command to start the data relocation tool.
Run the following command:
start_UpgradeServer

@osssvr-1 # start_UpgradeServer
UpgradeServer is starting ...
Checking db tables ...
creating table MBSC_UPGRADENEINFO ...
creating table MBSC_UPGRADEPROGRESS...
Upgrade Server is running ...
Broadcast Message from
(pts/4) on Galileo Sat Aug
8 09:30:36...
Upgrade server has started.
If the command result contains "Upgrade server has started." and does not contain "error" or
"fail", the UpgradeServer service is successfully started.
2.2 Upgrading NEs

Perform NE upgrade operations to upgrade NEs to the latest versions.
Release 03 (2010-07-31)
Huawei confidential
BSC 6900 V900R012C01

5 FAQs
The upgradeServer tool monitors the version changes of NEs and automatically creates
relocation tasks. Thus, start the upgradeServer tool before upgrading NE versions.
If the upgradeServer tool is not started, you need to manually create relocation tasks. For
details, see section 5.1"What to Do if the Relocation Tool Is Not Started Before NE
Upgrade?"
2.3 Querying the Statuses of Upgrade Tasks

If the NEs are connected to the M2000 client during the upgrade process, a dialog box is
displayed, indicating that the M2000 automatically switches to the multi-user mode. If this
occurs, the upgrade task is finished successfully. You need not to perform the following
operations. Then, you need to log out of the M2000 client and then log in again. If you switch
to the multi-user mode manually, you need not log in to the M2000.
If the M2000 client is not connected during the upgrade process, do the following operations
described in this section to query if the upgrade task is complete.
2.3.1 Checking Whether the Upgrade Task is

Complete
The method of checking whether the upgrade task is complete is as follows.
You can query the status of upgrade tasks one by one. Each NE maps to an upgrade task. Each
upgrade task involves multiple modules such as CM, PM, and NIM. The M2000 creates an upgrade
task for each NE meeting upgrade requirements. Each upgrade task is assigned with a unique task
ID. You can use a tool to query the execution status of each task, including the progress, running
status, and error description in each module of the upgrade task.
During the execution of an upgrade task for an NE, the M2000 synchronizes the configuration data
of the NE. If the size of the configuration data is very large, it takes a long time to synchronize the
data. Normally, it takes less than 20 minutes to synchronize data.

upgradeClient queryTasks

@Galileo # upgradeClient queryTasks
taskID:0
NE:140
GOV9R12C01ID0700
Module name
From:BSC6000V900R008C12ID0195SP11
Percent
To:BSC6900-
Operation state
Run state
UpgradeTool_CM
100
Success
UpgradeTool_FM
100
Success
UpgradeTool_FM_P
100
Success
Idle
Idle
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

is V200R010)
2 Upgrade Procedure
Idle
UpgradeTool_NIM
100
Success
UpgradeTool_PM
100
Success
UpgradeTool_PM_T
100
Success
UpgradeTool_SM_MML
Idle
100
Success
Idle
Idle
Idle
--------------------------------------------------taskID:1
NE:.3221229568.3221278720.3221287330
GOV9R12C01ID0700
To:BSC6000V900R008C12ID0195SP11
Module name
Percent
From:BSC6900-
Operation state
Run state
UpgradeTool_CM
100
Success
UpgradeTool_FM
100
Success
UpgradeTool_FM_P
100
Success
UpgradeTool_NIM
100
Success
UpgradeTool_PM
100
Success
UpgradeTool_PM_T
100
Warning
UpgradeTool_SM_MML
Idle
100
Success
Idle
Idle
Idle
Idle
Idle
Idle
Warning message:
Module name
description
UpgradeTool_PM_T
Need to stop service[PMService] firstly ,and then
execute script[mbsc_pm_backup.sh -restore .3221229568.3221278720.3221287330 SYB
sa emsems /export/home/omc/var/UpgradeTool/data >/dev/null 2>&1], finally
restart service[PMService] using this command [svc_adm -cmd restartsvc
PMService]
----------------------------------------------Total tasks:2
Release 03 (2010-07-31)
Huawei confidential
BSC 6900 V900R012C01

5 FAQs
If the progress of all the modules fails to reach 100%, it indicates that the upgrade task is
not finished. If you find that the progress of UpgradeTool_CM stops at 33% for a long
time, ignore the problem. For details, see section 2.3.2Configuration Synchronization."
Please wait until the progress reaches 100%.
If the upgrade of all the modules reaches 100% and the result does not contain "Failed",
it indicates that the upgrade is successful.
If the progresses of all the modules reach 100% but "Failed" is displayed, contact
Huawei technical support engineers for assistance.
2.3.2 Configuration Synchronization

During the synchronization of configuration data, you can run the upgradeClient
queryTasks command to view the progress. If you find that the progress of
UpgradeTool_CM stops at 33% for a long time, that is the synchronization of configuration
data is processing. And the finished time is according to the size of data.
Figure 1.1 UpgradeTool_CM stopping at 33%
If the progress of UpgradeTool_CM stops at 33% for more than 20 minutes and there is no
progress bar for synchronizing configuration data on the topology view of the M2000 client,
perform the following operations to solve this problem:
Run the following command to switch the system to the normal mode:
-bash-3.00$ svc_limitsystem off -path /opt/OMC/etc/conf

[Info]Initializing.
[Info]Succeeded in changing system restrict mode.
[Info]Changed to not restrict mode.
Operation success!
Log out from the M2000 client and then log in again. Manually synchronize the
configuration data of the relevant NE. If manual synchronization is successful, the
upgrade task on the M2000 server continues to run. After manual synchronization is
successfully performed, run the upgradeClient queryTasks command to check whether
the progress of the upgrade task exceeds 33%. If manual synchronization fails or the
progress still stops at 33%, contact Huawei technical support engineers for assistance.
To manually synchronize configuration data, do as follows:

Step 1 Log in to the M2000 client and choose Topology > Main Topology to open the M2000
topology view.
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

is V200R010)
2 Upgrade Procedure
Figure 1.1 Main Topology-1
Step 2 On the topology view, right-click an NE whose data is being relocated and then choose
Synchronize CM data from the shortcut menu.
Figure 1.1 Synchronizing CM data
Step 3 After the synchronization task starts, a progress bar is displayed on the NE icon, indicating the
synchronization progress.
Figure 1.1 Progress bar
Step 4 After the synchronization task starts, right-click tree of root node and then choose Refresh
from the shortcut menu
Release 03 (2010-07-31)
Huawei confidential
BSC 6900 V900R012C01

5 FAQs
Figure 1.1 Refreshing NE status
----End
2.4 Stopping the Relocation Tool

Step 1 Stop the UpgradeServer service.
If all the data of all NEs is successfully relocated and there is no NE to be upgraded, stop the
UpgradeServer service on the M2000. But before the next NE upgrade, you must start the
relocation tool again. For details, see section 2.1"Starting the Relocation Tool."
stop_UpgradeServer

@Galileo # stop_UpgradeServer
Upgrade Server has shutdown
upgradeServer stopping!
Broadcast Message from
(pts/7) on Galileo Thu Aug 20 11:35:44...
upgradeServer has stopped.

When the system prints the following information, the relocation tool is successfully started. You can
press Enter to return to the shell console.
upgradeServer has stopped.
Step 2 If you have performed steps in section 2.1.3"(Optional) Starting the Centralized NIM
Network Monitoring", you are advised to stop the centralized NIC network monitoring
components.
Run the cst_adm command to stop the centralized NIM network monitoring components.
cst_adm -cmd stopcomponent NetWorkIntegrationMonitoring

root@osssvr-1 # cst_adm -cmd stopcomponent NetWorkIntegrationMonitoring
Sun Microsystems Inc.
SunOS 5.10
Generic January 2005
StopComponent::NetWorkIntegrationMonitoring
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

is V200R010)
2 Upgrade Procedure
send convert component state event(stop

component[NetWorkIntegrationMonitoring])...
sendConvertFuncStateEvent:SvrDc_Module_Protocol_NbMml:SvrDc_Module_Protocol_NbM
ml:createModule
sendConvertFuncStateEvent:SvrModule_ComDataDriver_Impl:SvrModule_ComDataDriver_
Impl:createModule
sendConvertFuncStateEvent:SvrModule_StateDriver_Impl:SvrModule_StateDriver_Impl
:createModule
sendConvertFuncStateEvent:NIMSvr_AccMgr:NIMSvr_AccMgr:createModule
sendConvertFuncStateEvent:NIMSvr_BTSMonitor:NIMSvr_BTSMonitor:createModule
sendConvertFuncStateEvent:NIMSvr_Obt:NIMSvr_Obt:createModule
sendConvertFuncStateEvent:NIMSvr_Ogm:NIMSvr_Ogm:createModule
sendConvertFuncStateEvent:NIMSvr_Upgrade:NIMSvr_Upgrade:createModule
sendConvertFuncStateEvent::SvrFixture_Dc_NeEngine_Impl:createNeEngineStateSynch
disable component exec end.
writeRunInfo:/opt/OMC/etc/conf/var/NIMServer/CustomComponentDef.xml 1
<?xml version="1.0" encoding="UTF-8"?>
<response retcode="0" message="">
<Component name="NetWorkIntegrationMonitoring" desc="NetWork Integration
Monitoring" domain="WRAN;GRAN" enable="0" runningsate="0"/>
</response>
----End
Release 03 (2010-07-31)
Huawei confidential
Rollback Procedure
3.1 Overview
The rollback function of the M2000 can be used only when NE upgrade fails and the version
rollback is mandatory. Rollback operations must be manually performed.
3.2 Preparing for the Rollback

Step 1 Apply permission for restarting performance services.
The rollback requires you to restart the performance services of the M2000 (see section 3.8).
Before restarting performance services, ensure that you have applied for the relevant
permission.
Step 2 Configure the relay server.
If you roll back the BSC6900 GSM to the BSC6000, ensure that the M2000 server is already
configured as the relay server before the rollback. This operation is not involved in the
rollback of the BSC6810. The operations are as follows:
This operation is not involved in the rollback of the BSC6000V9R8C01. It is involved in the rollback of
the BSC6000V9R8C12 and later releases.
1.
Choose Software > File Server Setting.
BSC 6900 V900R012C01

5 FAQs
Figure 1.1 Setting the relay server (1)
2.
Select the BSC6900 GSM node in the left pane and specify an NE in the left pane.
Change File Server Name to OMC:
Figure 2.1 Setting the relay server (2)
There is no need to change measurement settings of performance file interface (NE-based) as it does not
affect the performance file interface.
----End
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

is V200R010)
5 FAQs
3.3 Starting the UpgradeServer

Step 1 Logging In to the M2000 Server
See section 2.1.2Logging In to the M2000 Server.
Step 2 Checking Whether upgradeServer Is Started.
Run the ps command to check whether the upgradeServer service is started. If it is not
started, manually start it.
@osssvr-1 # ps -ef |grep upgradeServer| grep -v grep
If the data relocation tool is started, the following information is displayed:

omcuser 14609
1
0 12:46:38 ?
--svcname upgradeServer --svcpara
0:17 /opt/OMC/bin/upgradeServer
If no information is displayed, you must manually start upgradeServer. For details, see section
2.1Starting the Relocation Tool
3.4 Rollback NE
Roll back the current NE version to the previous version by refering to the relevant section in
the NE upgrade guide.
The rollback of the M2000 is performed only after NE rollback is complete. Therefore, you must roll
back NEs first. After NEs are successfully rolled back, proceed with the following operations.
3.5 Selecting the Task to Be Rolled Back

Run the upgradeClient queryTasks command to query the status of all the current tasks.
Check the value of the NE field for each task. This value indicates the name of an NE created
on the M2000. Based on this value, you can identify the task of the NE to be rolled back.
upgradeClient queryTasks

@Galileo # upgradeClient queryTasks
taskID:0
NE:140
GOV9R12C01ID0700
Module name
From:BSC6000V900R008C12ID0195SP11
Percent
To:BSC6900-
Operation state
Run state
UpgradeTool_CM
100
Success
UpgradeTool_FM
100
Success
Idle
Idle
Issue 03 (2010-07-31)
Huawei confidential
BSC 6900 V900R012C01

5 FAQs
UpgradeTool_FM_P
100
Success
UpgradeTool_NIM
100
Success
UpgradeTool_PM
100
Success
UpgradeTool_PM_T
100
Success
UpgradeTool_SM_MML
Idle
100
Success
Idle
Idle
Idle
Idle
--------------------------------------------------taskID:1
NE:.3221229568.3221278720.3221287330
GOV9R12C01ID0700
To:BSC6000V900R008C12ID0195SP11
Module name
Percent
From:BSC6900-
Operation state
Run state
UpgradeTool_CM
100
Success
UpgradeTool_FM
100
Success
UpgradeTool_FM_P
100
Success
UpgradeTool_NIM
100
Success
UpgradeTool_PM
100
Success
UpgradeTool_PM_T
100
Warning
UpgradeTool_SM_MML
Idle
100
Success
Idle
Idle
Idle
Idle
Idle
Idle
Warning message:
Module name
description
UpgradeTool_PM_T
Need to stop service[PMService] firstly ,and then
execute script[mbsc_pm_backup.sh -restore .3221229568.3221278720.3221287330 SYB
sa emsems /export/home/omc/var/UpgradeTool/data >/dev/null 2>&1], finally
restart service[PMService] using this command [svc_adm -cmd restartsvc
PMService]
----------------------------------------------Total tasks:2
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

is V200R010)
5 FAQs
3.6 Starting Rollback Tasks

upgradeClient rollback --taskIds id1,id2....
For example, if the task ID of the task to be rolled back is 0, run the following command:
upgradeClient rollback --taskIds 0
If you want to roll back multiple tasks at a time, use commas (,) to separate multiple task IDs.
If a rollback task is successfully started, the system prints rollback success. The task ID of
the rollback task is the same as the task ID of the corresponding upgrade task. If a rollback
task fails to be started, the system prints the following information:
Rollback [error information]
If rollback fails, contact Huawei technical support engineers for assistance.
3.6.1 Restricted Mode

After a rollback task is started, the system is automatically switched to the restricted mode.
Before the rollback is complete, some operations cannot be performed. After the M2000 is
switched to the restricted mode, the interface of the M2000 client displays the messages.In
such a case, you must log out of the M2000 client and then log in again.
3.6.2 Checking the Running Status of the Rollback

Task
After a rollback task is started, you can run the upgradeClient queryTasks command to view
the running status of the rollback task.
The rollback process is executed in the form of tasks. The task ID of a rollback task is the
same as the task ID of the corresponding upgrade task.
3.6.3 Configuration Synchronization

Rollback takes a long time. Wait until the synchronization of configuration data is complete.
For details, see section 2.3.2Configuration Synchronization.
3.7 Rollback Completion

After the roll back is completed, the M2000 displays a dialog box shown in Figure 1.1 and
automatically switches to the multi-user mode. When this occurs, you must log out of the
M2000 client and then log in again.
Issue 03 (2010-07-31)
Huawei confidential
BSC 6900 V900R012C01

5 FAQs
Figure 1.1 Message dialog box
Run the upgradeClient queryTasks command on the M2000 server. If the progresses of all
the modules reach 100% and "Failed" is not displayed on any module, it indicates that the
rollback task is successfully executed. If "Failed" is displayed, contact Huawei technical
support engineers for assistance.
3.8 Running the Script

After the rollback is complete, run the upgradeClient queryTasks command to view the
"Warning message" of upgrade tasks and perform operations as prompted. For example, view
the following message:
Warning message:
UpgradeTool_PM
Need to stop service[PMService] firstly and execute
script[mbsc_pm_backup.sh -restore .3221229568.3221278720.3221282817 SYB sa
emsems $DBPassWord /export/home/omc/var/UpgradeTool/data >/dev/null 2>&1],
finally restart service[PMService]
Perform the following operations according to the prompt:

Step 1 Stop PMService.
# svc_adm -cmd stopsvc PMService
Step 2 Run a script to copy the character string in the brackets on the M2000 server.
# mbsc_pm_backup.sh -restore .3221229568.3221278720.3221282817 SYB sa emsems
/export/home/omc/var/UpgradeTool/data >/dev/null 2>&1
Step 3 Start PMService.

# svc_adm -cmd startsvc PMService
Huawei confidential
Issue 03 (2010-07-31)
Relocation Specifications
The previous chapters describe the process of relocating the data of a single NE. During the
process, you need to start only the relocation tool to relocate NE data. The process of
relocating the data of multiple NEs is the same. The only difference is that the M2000 server
creates multiple data relocation tasks at a time and executes these tasks concurrently.
Currently, the M2000 supports the 10 concurrent relocation tasks. The time taken for data
relocation varies according to the performance of the M2000 servers and NE upgrade plans.
FAQs
5.1 What to Do if the Relocation Tool Is Not Started Before

NE Upgrade?
If the relocation tool (upgradeServer) is not started before NE upgrade, the NE relocation
tasks on the M2000 cannot be automatically started and NEs connected to the M2000 cannot
be managed. If this occurs, manually create relocation tasks. The following operations must
be performed after NEs are upgraded and are connected to the M2000.
To create relocation tasks, perform the following steps:
Step 1 Start the NE relocation tool (upgradeServer). For details, see section 2.1"Starting the
Relocation Tool."
Step 2 Obtain the FDNs of NEs.
1.
Start the M2000 client, choose Main Topology > Main Topology.
Figure 1.1 Logging in to the main topology
2.
Right-click the NE to be upgraded, and then choose NE Property from the shortcut
menu. Record the FDN of the NE in the displayed NE Property dialog box.
BSC 6900 V900R012C01

5 FAQs
Figure 2.1 NE Property dialog box
Step 3 After an NE is relocated, its type changes and the type ID changes accordingly. Figure 1.1
lists the NE types and corresponding type IDs.
Figure 1.1 NE type and type ID
Type
ID
BSC6000
45
RNC
BSC6900 GSM
171
BSC6900 UMTS
172
BSC6900 GU
173
BSC6000(R11+)
8197
BSC6810(R11+)
8199
Step 4 Verify the version number before and after the upgrade.
The version number is recorded in the NeVersion.def file under the /etc directory of the
corresponding mediation. You can check the version number in this file.
Example
After the BSC6000 is upgraded to the BSC6900 GSM, its mediation version is changed
from iManagerM2000_BSC6000_MATCH_ENG_V200R008C12SPC023 to
iManagerM2000_BSC6900GSM_MATCH_ENG_V200R010C01B072.
Run the following command to obtain the internal version number before the upgrade:
Huawei confidential
Issue 03 (2010-07-31)
BSC 6900 V900R012C01

is V200R010)
5 FAQs
-bash-3.00$ cat
/opt/OMC/med/BSC6000NE/iManagerM2000_BSC6000_MATCH_ENG_V200R008C12SPC023/et
c/NeVersion.def |grep NeVersion
The version number in the command is only for reference. Replace it with the actual NE version.

NeVersion=BSC6000V900R008C12ID0195SP23
In the command result, BSC6000V900R008C12ID0195SP23 is the internal version

number of the BSC6000. You can also obtain the version number of upgraded NE in the
same method.
Run the following command to obtain the version number after the upgrade:
-bash-3.00$ cat
/opt/OMC/med/BSC6900GSMNE/iManagerM2000_BSC6900GSM_MATCH_ENG_V200R010C01B07
2/etc/NeVersion.def |grep NeVersion
The version number in the command is only for reference. Replace it with the actual NE version.
NeVersion=BSC6900-GOV9R12C01ID8072
Step 5 Run the following command to create NE relocation tasks:

upgradeClient createTask --neInfo
neFdn,sourceNeTypeId,targetNeTypeId,sourceInternalId,targetInternalId
--moduleInfo UpgradeTool_CM [,OtherModule]
--neInfo specifies NE information. It consists of neFdn, sourceNeTypeId, targetNeTypeId,

sourceInternalId, and targetInternalId. Each parameter is separated by commas (,). For details, see
Figure 1.1.
--moduleInfo specifies information about modules. The value of moduleInfo must be

UpgradeTool_CM,UpgradeTool_FM,UpgradeTool_FM_P,UpgradeTool_NBI,UpgradeTool_NI
M,UpgradeTool_PM,UpgradeTool_PM_T,UpgradeTool_SM_MML. The character strings in the
value of moduleInfo are separated by commas (,). Ensure that there is no space between characters.
Otherwise, running the command fails.
Figure 1.1 The description of the parameters
Issue 03 (2010-07-31)
Parameter Name
Parameter Description
neFdn
FDN of an NE. For details, see substep 2 in this section.
sourceNeTypeId
Type ID of the NE before the upgrade. For details, see Step 3.
targetNeTypeId
Type ID of the NE after the upgrade. For details, see Step 3.
sourceInternalId
Internal version number of the NE before the upgrade. For
Huawei confidential
BSC 6900 V900R012C01

5 FAQs
Parameter Name
Parameter Description
details, see Step 4 in this section.
targetInternalId
Internal version number of the NE after the upgrade. For details,

see Step 4 in this section.
Example:
-bash-3.00$ upgradeClient createTask --neInfo .
3221229568.3221278720.3221288485,45,171,BSC6000V900R008C12ID0195SP23,BSC690
0-GOV9R12C01ID8072 --moduleInfo
UpgradeTool_CM,UpgradeTool_FM,UpgradeTool_FM_P,UpgradeTool_NBI,UpgradeTool_
NIM,UpgradeTool_PM,UpgradeTool_PM_T,UpgradeTool_SM_MML
If the command is successfully executed, the system prints createTask sucess taskId=
[XX], where XX is a number. It is the ID of the newly created task.
If no command result is displayed, contact Huawei technical support engineers for
assistance.
Step 6 Querying the statuses of upgrade tasks, and then stop the relocation tool. For details, see
section 2.3Querying the Statuses of Upgrade Tasks and 2.4Stopping the Relocation Tool.
Huawei confidential
Issue 03 (2010-07-31)

BSC6900 V900R012C01 Data Relocation Guide (Only For M2000 Common Version Is V200R010)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 V900R012C01 Data Relocation Guide (Only For M2000 Common Version Is V200R010)

Uploaded by

Copyright:

Available Formats

BSC 6900 V900R012C01

Data Relocation Guide(Only for M2000

Huawei Technologies Co., Ltd.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base