V200R009C02SPC610
Installation Guide (Standalone CME for Windows)
Document
Version 01
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 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
Fax 0755-28560111
Author
Author Wang XiaoKang Date 2011-3-25
Reviewed An Xiangbin, Zhang Xiaomao, Date 2011-3-25
By Chen Huanjun, Qian Cheng, Luo
Shumin, Yan Hui, LianJie, Wu
Hao
Tested By Cao JiaWu Date 2011-3-25
Organization
It is recommended that you read the installation guide of this version before using the
V200R009C02SPC610. The following table lists the contents contained in this document
Chapter Description
History
Versio Description Release Prepared Approve
n Date By d By
Contents
1 Overview
You must familiarize yourself with the CME V200R009C02SPC610 Release Notes.
The client software of the standalone mode is also applicable to the integrated mode.
Microsoft SQL Server 2005 Microsoft SQL Server 2005 with SP3
(Microsoft SQL Server 2005 is one version of MSDE)
If the required Microsoft Office version is not provided, the following features cannot be
implemented:
2G/3G radio network planning (RNP) data import and export in .xls format
3G Iu/Iur negotiation data import and export
3G Iub negotiation data import and export
2G/3G base station reparenting
2G cell parameter import and export in .xls format
2G RNP import and export in .xls format
2G cell frequency import and export in .xls format
2G TRX device import and export in .xls format
2G BA list import and export in .xls format
2G negotiation data import
GUI data table export in .xls format
Hot cell feature
1.2.4 NE Versions
The CME supports the hot patch versions of the BSC6900, BSC6810, MBTS, NodeB and all patch
versions of BSC6000.
For example:
If CME supports BSC6900V900R011C00SPC720, BSC6900V900R011C00SPH72# is supported by default.
NE Type NE Version
BSC6800V100R012C00SPC100
TGW TGW1000V100R002C01SPC000
MBTS BTS3900V100R002C00SPC100
BTS3900V100R002C00SPC120
BTS3900 V100R002C00SPC121
BTS3900 V100R002C00SPC130
BTS3900 V100R002C00SPC150
BTS3900 V100R002C00SPC200
BTS3900 V100R002C00SPC220
BTS3900 V100R002C00SPC230
BTS3900V100R002C01
BTS3900V100R002C01SPC100
NodeB BTS3812E-12AC-12AE-BTS3812AV100R010C01SPC100
BTS3812E-12AC-12AE-BTS3812AV100R011C00SPC200
BTS3812E-12AC-12AE-BTS3812AV100R011C00SPC300
BTS3812E-12AC-12AE-BTS3812AV100R012C00
BTS3812E-12AC-12AE-BTS3812AV100R012C00SPC100
BTS3812E-12AC-12AE-BTS3812AV100R012C00SPC200
DBS3800V100R010C01SPC100
DBS3800V100R010C01SPC200
DBS3800V100R011C00SPC100
DBS3800V100R011C00SPC200
DBS3800V100R011C00SPC300
DBS3800V100R011C00SPC500
DBS3800V100R012C00
DBS3800V100R012C00SPC100
DBS3800V100R012C00SPC200
DBS3800V100R012C00SPC300
BTS3900-BTS3900A WCDMA V200R010C01SPC300
BTS3900-BTS3900A WCDMA V200R010C01SPC500
BTS3900-BTS3900A WCDMA V200R011C00SPC100
BTS3900-BTS3900A WCDMA V200R011C00SPC200
BTS3900-BTS3900A WCDMA V200R011C00SPC300
BTS3900-BTS3900A WCDMA V200R011C00SPC500
BTS3900-BTS3900A WCDMA V200R011C00SPC600
BTS3900-BTS3900A WCDMA V200R011C00SPC700
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC050
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC100
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC200
Data configuration of GBTSs is incorporated into the data configuration of BSCs, and the GBTS
versions are not displayed on the CME client. For details about the supported GBTS versions, see the
BSC6000 or BSC6900 release notes.
The CME supports the hot patch versions of the BSC6900, BSC6000, BSC6810, MBTS, and NodeB.
CMEComponent_MBSC6900V9R11SPC700.exe BSC6900V900R011C00SPC700
CMEComponent_MBSC6900V9R11SPC710.exe BSC6900V900R011C00SPC710
2 Preparations
Save the package to a local PC. This document takes the root directory of C:/ as an example.
Apply the license file for the standalone CME.
Apply license file from Huawei Technology Support Website http://support.huawei.com. The
detailed path is SUPPORT > NOTICE > Software Bulletin. Then, search for the OSS
M2000&PRS&CME&AHR&APM Product Universal License Release Bulletin.
Microsoft SQL Server 2005 Express (refer to chapter 6.8How Should I Check the
Installation of .net Framework2.0?). The .net Framework2.0 installation package is
available in the dotNet Framework 2.0 folder in the installation of MSDE_Insall
If you have installed the standalone or integrated CME client on the local PC, uninstall
the CME client first.
Installing the standalone CME client requires:
PC type Configuration
It takes about three minutes to install the SQL Server. After the installation, it takes about
eight minutes to install the standalone CME client.
----End
----End
The standalone CME can be installed only in the Windows operating system. Therefore,
do not install the standalone CME in other environments.
You must install a standalone CME or use a standalone CME as a user in the
Administrators user group.
Before installing the standalone CME, suppose that the password of the SQL server user
sa is emsems. Choose Start > Run, and then type cmd in the Run dialog box. Then, type
sqlcmd -S127.0.0.1,1433 -Usa -Pemsems in the displayed interface. If 1> is displayed, you can
infer that the database connection is normal. In such a case, type exit. If not, please check whether the sa
password or the configuration of SQLServer 2005 was right.
sqlcmd
If you change the default port to another port, you need to add the port number when run the
command to access the non-default port; otherwise, the connection to the port fails. For
example, if you change the default port to port 1434, you need to run sqlcmd
-S127.0.0.1,1434 -Usa -Pemsems to access port 1434.
Double-click Setup.exe in the folder of the Windows resource manager. Do not use tools
such as Total commander.
Step 1 Copy the installation package from the installation disk to a drive on the local PC.
Step 2 Open the installation package of the CME client, and then double-click setup.exe. A dialog is
displayed, prompting you to select the language of the program. Choose Chinese (Simplified)
or English, as shown in Figure 1.1.
Step 3 After you click Next, the dialog box is displayed, as shown in Figure 1.1, prompting you to
confirm the installation.
Step 4 Click Next. The License Agreement dialog box is displayed, as shown in Figure 1.1.
Step 5 If you do not accept the terms, click Cancel. If you accept the terms, select I accept the
terms of the license agreement and click Next. The dialog box shown in Figure 1.1 is
displayed, showing user information.
Step 6 Click Next. A dialog box shown in Figure 1.1 is displayed, prompting you to specify the
destination folder.
Step 7 Specify the destination folder and then click Next. A dialog box shown in Figure 1.1 is
displayed, prompting you to confirm the installation of the components. Select both of CME
Client and Client Assistant Daemon. Click Next.
Step 8 Enter the MSDE database user name and password and port (default value is sa,
emsems,1433) , and then click Next, as shown in Figure 1.1.
Step 9 A dialog box is displayed, indicating that the wizard is ready to begin the installation.
Step 10 Click Install to start the installation. The progress of installing the data files is displayed, as
shown in Figure 1.1. The system will install database automatically.
Step 11 Click Finish to complete the installation and restart the computer.
----End
----End
4 GU Component Installation
Files of the most GU NE versions that are supported by the CME have been contained in the
installation package of the standalone CME. You can install components corresponding to NE
versions that are not frequently used on the standalone CME. For details about NE versions
that need to install components, see section 1.2.4NE Versions . It need 35~45 minutes to
install a GU NE Component.
Step 3 After the decompression is complete, a window is displayed, as shown in the following figure.
Select a correct CME installation path, and then click Install.
Step 2 Select the CME, and then click Change or Remove and confirm the operation.
Step 4 After the uninstallation is complete, check that the CME is removed from Control Panel.
----End
6 FAQs
6.1.2 Troubleshooting
Install the NetFx20SP1_x86.exe program in the MSDE_Install\dotNet Framework 2.0
directory.
6.2.2 Troubleshooting
Copy the framedyn.dll file from C:\WINDOWS\system32\wbem\ to
C:\WINDOWS\system32\.
Note: If the root disk of Windows installation directory is in other disks, copy the file to the
system32 directory in the corresponding disk.
6.3.2 Troubleshooting
Run the Database Parameter Management.exe file in the \CME\Bin directory to modify
the configuration parameters.
6.3.4 Troubleshooting
Step 1 Check whether the port of SQL Server 2005 is static port.
1. Start the SQL Server Configuration Manager.
2. Select the used instance, as shown in Figure 1.2. Then, double-click TCP/IP.
3. On the IP Addresses tab page of the displayed TCP/IP Properties dialog box, if the
values of all TCP dynamic ports are empty or 0, it indicates that a static port is enabled for
the SQL Server 2005. Otherwise, it indicates that a dynamic port is used. In this case, use a
static port instead by referring to section 6.4"How Should I Use the Static Port Instead."
----End
the default instance is used during the installation, the static port number is 1433. If a
command instance is used during the installation, a dynamic port is required. The SQL Server
2005 sets a port number when the system is started each time.
6.4.2 Troubleshooting
Step 1 Open the TCP/IP Properties dialog box in which the instances need to be configured by
referring to 6.3.4 I. IStep 1"Check whether the port of SQL Server 2005 is static port." in
section "How Should I Check Whether the Port Used in the SQL Server 2005 is Static Port?"
Step 2 Disable all the configured TCP dynamic ports, and then change the TCP port number to the
specified number.
Step 3 After the configuration, restart the SQL Server.
6.6.2 Troubleshooting
Step 1 Click Cancel in the dialog box shown in 6.6.1 I. IStep 1Figure 1.1,
Step 2 Change the password, namely, the SAPWD value in the template.ini file in the one-click
installation package. The password must be a combination of uppercase letters, lowercase
letters, and numerals, for example, OSScme11111111.
Step 3 Perform the one-click installation again and type the correct password when required.
----End
6.7.2 Troubleshooting
Step 1 Double-click My Computer and find the path where the SQL Server is installed, for example,
in disk C.
Step 2 Right-click Local Disk (C), and then choose Properties from the shortcut menu. On the
General tab page, check whether Compress drive to save disk space is selected. If it is
selected, deselect it, and then click OK, as shown in Figure 1.1.
Step 3 In Currently installed programs, check whether a .net Framework2.0 or a later version is
available. If a .net Framework2.0 or a later version is available, it indicates that the .net
Framework2.0 is installed on the PC.
----End
Step 3 If you need to start the SQL Server service, run the net start MSSQLServer command, as
shown in Figure 1.1.
----End
Step 2 In the displayed Backup/Restore cmedb dialog box, click Backup or Restore to perform the
relevant operations.
----End
6.11.2 Troubleshooting
Run the regsvr32 vbscript.dll command for registration.
6.12.2 Troubleshooting
The installation path of Windows Installer 3.1 is
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=889482FC-
5F56-4A38-B838-DE776FD4138C
6.13.2 Troubleshooting
Uninstall the pre-installed CME and then reinstall the CME. And select the server components
while installing the CME.
6.14.2 Troubleshooting
Step 1 Enable writing caching on the disk.
1. Right-click the hard disk in which the CME client is installed, and then choose Properties
from the shortcut menu. A disk properties dialog box is displayed, as shown in Figure 1.1.
2. Click the Hardware tab, and then select the hard disk drive whose writing caching you
want to enable.
3. Right-click the hard disk drive, and then choose Properties from the shortcut menu. In the
displayed hard disk drive properties dialog box, click the Policies tab, and then select
Enable write caching on the disk.
6.15.2 Troubleshooting
Run the resgvr32 command to register the sqloledb.dll file in the C:\Program Files\Common
Files\System\Ole DB\ path, as shown in Figure 1.1.
6.16.2 Troubleshooting
Save the following information as a file named thirdtools.ini to the C:\windows\system32
path. You need to replace the contents highlighted in red with the current CME installation
path.
[CME]
AppPath=C:\Program Files\Huawei Technologies\CME\Bin\CMEMain.exe
AppParam=User,Ip,Port,Token,UserPrivileged
MenuName=CME
MenuShortcut=M
AccessKey=CMECurRead
Note: If the local PC runs on the 64-bit Windows 2008 operating system, you need to save the
thirdtools.ini file to the C:\Windows\SysWOW64 path.
6.17.2 Cause
The Microsoft SQL Server2005 is not installed by strictly following the instructions in the
upgrade guide.
6.17.3 Troubleshooting
Uninstall the Microsoft SQL Server 2005, and then re-install it by referring to section
3.2"Installing the SQL Server."
6.19.2 Cause
The Help_cme.hdx file is the material of the standalone CME, and is opened by the Hedex
software. Therefore, when you attempt to delete the Help_cme.hdx file in the installation
directory after the standalone CME is uninstalled, the system displays a message indicating
that the file cannot be deleted because it is in use.
6.19.3 Troubleshooting
Stop the Hedex services, and then delete the Help_cme.hdx file.
6.20.2 Cause
The operating system of the PC is Windows XP SP3, and the msxml6r.dll version of the
Windows XP SP3 system is later than the version to be installed. Thus, the msxml6r.dll
cannot be replaced by the previous version.
6.20.3 Troubleshooting
Click OK.
6.21.2 Cause
The default installation path of one-click installation of SQL Server is C:\Program
Files\Microsoft SQL Server\. However, the disk space of disk C is usually insufficient. Thus,
the installation of the SQL server may fail, or the later installation of the standalone CME
may fail.
6.21.3 Troubleshooting
Navigate to the installation path of the SQL Server, and then modify the INSTALLSQLDIR
parameter in the template.ini configuration file.
6.22.2 Cause
Licenses adopt A.D time, for example, 2010-01-01.
6.22.3 Troubleshooting
Change the system time in the PC to A.D. time.
6.23.2 Cause
The failure to install the SQL Server results in the failure to start the SQL server service. The
SQL server may fail to be installed because any of the following causes:
The files are not deleted completely during the uninstallation of the previous SQL Server.
Registration information cannot be deleted during the uninstallation of the previous SQL
Server.
6.23.3 Troubleshooting
Step 1 Install Windows installer clean up software. Use the Windows installer clean up program
to clear all the application related to the SQL Server and MSDE.
Step 2 Uninstall the SQL server by running uninstall.bat.
Step 3 Restart the PC and then install the SQL Server again.
6.24.2 Cause
Errors occur in the registration information because the CME fails to be installed or other
exceptions occur during the installation of the CME.
6.24.3 Troubleshooting
Clear the installation directory of the CME, and then re-install the CME.
6.25.2 Cause
The CmeServer service is not registered.
6.25.3 Troubleshooting
Run Server\Bin\RegisServer.bat to register the CmeServer service, and then restart the
CME.
6.26.2 Cause
A third-party program such as a program for remote access cannot be stopped because the
program is suspended. Therefore, the information of the CME cannot be registered through
the Setup.exe process.
6.26.3 Troubleshooting
Open the Windows task manager and stop suspended programs such as mstsc.
6.27.2 Cause
According to the explanation of the Microsoft, the SQL Server 2005 software conflicts with
the Windows XP operating system.
6.27.3 Troubleshooting
Upgrade Windows XP to Windows XP Service Pack 3.
7 Version Changes
This chapter describes the changes in features, MML scripts, alarms, and performance
counters.. The Standalone CME includes all the changes in features of Integrated CME by
default. This chapter describes the changes in features only in Standalone CME.
Improvement By FDN or NE name, the script executor can identify the NEs in the
project configuration file exported from the CME in standalone
mode.
Implementati When loading scripts, the script executor can identify the NEs by
on FDN or NE name.
Related 1. Export the script.zip, the project of the script executor, from the
Operation CME in standalone mode.
2. Replace the name marked in red in "<Script taskId="1"
neName="dss170" ...>" in the scriptcfg.xml file of the script.zip
package with the name of the actual NE to be delivered on the
M2000.
3. On the CME in integrated mode, load the project through the
script executor and activate the project.
PR Number DTS2010071601222
Feature ID None
This chapter describes the solved problems and unsolved problems. The Standalone CME
includes all the solved problems an unsolved problems of Integrated CME by default. This
chapter describes solved problems and unsolved problems only in Standalone CME.
9 Appendix