ZXWR RNC (V3.09.30) Radio Network Controller Operation and Maintenance Module Software Installation Guide

ZXWR RNCRadio Network Controller

Operation and MaintenanceModule Software Installation Guide

Version 3.09.30

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 20100705 First Edition (V3.09.30.03)

R1.1 20100906 Add:

1. Add a topic "Database Configuration in SBCXActive/Standby Environment".

2. Add a topic "Installing OMMB Server Side Soft-ware".

3. Add a topic "Installing OMMB Client Side Soft-ware".

4. Add a topic "Modification of OmmProc-Config.conf File" under "Configurations Relatedto OMM in M/S SBCX Mode" .

Update:

1. In the chapter "M/S Configuration Mode ofSBCX", modify a screen-shot and add ascreen-shot related to log service.

2. In the chapter "Configurations Related to OMMin M/S SBCX Mode", modify the descriptions.

3. In the chapter "Installation Flow", modify thescreen-shot.

4. In the chapter "Installing Oracle 10gDatabaase", modify the descriptions.

5. In the chapter "Overview to OMM NM ServerSoftware", modify the descriptions.

6. In the chapter "Installing OMMRB NM ServerSoftware", modify the screen-shots.

7. In the chapter "Overview to OMM NM ClientSoftware", modify the descriptions.

Revision No. Revision Date Revision Reason

8. In the chapter "Installing OMMRB NM ClientSoftware", modify the screen-shots and theJVM configuration.

9. In the chapter "Overview to OMM NM Serverand NM Client Software Upgrade", modify thedescriptions.

10. In the chapter " Upgrading OMM NM Server andNM Client in Linux", modify the descriptionsrelated to commands.

11. In the chapter " Upgrading OMM NM Serverand NM Client in Windows", modify the screen-shots.

12. In the chapter "One-Click Upgrade of OMM NMServer and NM Client", add the windows-re-lated descriptions.

13. In the chapter "Overview to OMM NM SoftwareUnload", modify the descriptions.

14. In the chapter "Uninstalling NM Server Pro-grams", modify the screen-shots.

15. In the chapter "Uninstalling Oracle Database",modify the descriptions of backup command.

16. In the chapter " Inconsistent File Format withContents", add a command line to create andclose the database.

R2.0 20100917 Second Edition (V3.09.30.06)

1. In chapter Steps to install OMMRB NM ServerSoftware, add new images of make_profile,modify the recommended installation directoryof the software.

2. In chapter Steps to Install OMMRB NM ClientSoftware, modify the recommended installa-tion directory of the software.

Serial Number: SJ-20100603155704-015

This page is intentionally blank.

Contents

Preface.............................................................. I

System Overview ..............................................1Network Management System .......................................... 1

Location of OMM in the System..................................... 1

Basic Concepts of OMM Installation ............................... 2

System Structure ........................................................... 2

Hardware Structure .................................................... 2

OMM Software Structure.............................................. 3

Networking Mode........................................................ 3

M/S Configuration Mode of SBCX .................................. 3

Database Configuration in SBCX Active/Standby

Environment ...................................................... 5

Configurations Related to OMM in M/S SBCX Mode .........11

Modification of system.conf File...........................12

Modification of OmmProcConfig.conf File ..............12

Modification of NetIf.conf File..............................14

Connection Method of Backplane Network

Interface ..............................................17

Installation Flow............................................................17

Configuration Requirements ............................................19

OMM Server Hardware Configurations...........................19

OMM Server Software Configurations............................19

OMM Client Hardware Configurations............................19

OMM Client Software Configurations.............................20

Installing Operating System............................21Overview......................................................................21

Installing SBCX Server Operating System .........................21

Preparations .............................................................21

Steps to install SBCX Server Operating System..............22

After the Installation ..................................................26

Configuring Telnet Access...................................26

Confidential and Proprietary Information of ZTE CORPORATION I

ZXWR RNC Operation and Maintenance Module Software Installation Guide

Configuring Remote Graphics Access ...................26

Configuring FTP Server ......................................27

Setting samba ..................................................28

Installing System Database.............................31Overview......................................................................31

Installing Oracle 10g Database ........................................32

Preparations for Oracle 10g Database Installation ..........32

Checking Installation Surroundings......................32

Checking System Kernel Parameters ....................32

Modifying shell limits .........................................33

Creating User and User Group ............................34

Creating User Directory and Modifying

Rights ..................................................34

Setting Environment Variables ............................35

Steps to install Oracle 10g Database ............................36

Installing Oracle 10g 10.2.0.1.0 ..........................36

Installing Oracle Patches ....................................47

Configuring Listener ..........................................53

Creating Database ............................................58

Checks after Oracle 10g Database Installation ...............71

Checking whether Oracle Database

can be Connected/Started/Shut

Successfully ..........................................71

Checking Whether Oracle Listener can be

Started/Stopped Successfully ..................72

Viewing Character Set of Database......................74

Configuring Auto Startup/Closeup of Oracle ..........76

Installing NM Server Software ........................79Overview......................................................................79

Installing OMMRB NM Server Software..............................80

Preparations for OMM NM Server Software

Installation .......................................................80

Setting Environment Variables for root Users .........80

Copying and Decompressing...............................81

Viewing and Modifying Rights .............................81

Checking Whether Oracle Database and Listener

is Enabled .............................................82

Steps to install OMMRB Server Software .......................83

Checks after OMMRB NM Server Software

Installation ..................................................... 104

II Confidential and Proprietary Information of ZTE CORPORATION

Checking Installation Files ................................ 104

Checking the /etc/hosts File ............................. 104

Starting NM Server.......................................... 105

Checking Running State ................................... 106

Shutting Down NM Server ................................ 107

Installing OMMB Server Side Software............................ 107

Installing NM Client Software........................125Overview.................................................................... 125

Installing OMMRB Client Software .................................. 125

Preparations ........................................................... 125

Steps to Install OMMRB NM Client Software................. 126

Checks after Installation........................................... 133

Checking Installation Files ................................ 133

Running OMMRB NM Client ............................... 133

Exiting OMMRB NM Client ................................. 134

Installing OMMB Client Side Software ............................. 134

Upgrading NM Server and NM Client

Software .......................................................143Overview.................................................................... 143

Upgrading OMM NM Server and NM Client in Linux ........... 144

Preparations ........................................................... 144

Upgrading Steps in Linux .......................................... 144

Upgrading OMM Client in Windows ................................. 151

Preparations ........................................................... 151

Upgrading Steps in Windows ..................................... 151

Checks................................................................... 160

One-Click Upgrade of OMMRB NM Server and Client ......... 160

Uninstalling OMM NM Software .....................163Overview.................................................................... 163

Uninstalling OMMRB NM Client Programs......................... 163

Uninstalling OMMRB NM Server Programs ....................... 164

Uninstalling Oracle Database......................................... 165

Backing Up Database .............................................. 165

Stopping Oracle Services .......................................... 167

Deleting Oracle Instances ......................................... 168

Uninstalling Oracle Database..................................... 172

FAQ ...............................................................177Database.................................................................... 177

Confidential and Proprietary Information of ZTE CORPORATION III


Import/Export Failure and Illegible Characters in

Records Inserted to Databases .......................... 177

Illegible Characters Displayed in Creating Diagnosis

and Test Tasks................................................. 178

Database Connection Failure Due to Power Off............. 178

OMM NMS................................................................... 179

Connection Failure between Client and Server (1) ......... 179

Connection Failure between Client and Server (2) ......... 179

Inconsistent File Format with Contents ....................... 180

Server Login ............................................................... 180

Checking Link Setup between Server and OMP ................ 181

Logs .......................................................................... 182

Common Commands of Linux........................................ 182

Common Commands of Oracle ...................................... 187

Starting Oracle Service............................................. 187

Closing Oracle Service.............................................. 187

Starting/Stopping Oracle Listener .............................. 188

Figures ..........................................................189

Tables ...........................................................197

Glossary ........................................................199

IV Confidential and Proprietary Information of ZTE CORPORATION

Preface

Purpose Thank you very much for choosing the UMTS wireless access sys-tem of ZTE Corporation!

The UMTS wireless access system of ZTE is a 3G mobile commu-nication system developed on a basis of the UMTS technology. Itfeatures strong capability in CS and PS service processing and pro-vides diversified services. Compared with GSM, UMTS delivers awider range of telecommunication services, including such multi-media services as voice, data, and image transmission, with higherrate and resource utilization ratio.

ZXWR RNC, a new generation radio network controller in the ZTEUMTS V3 family, delivers functions of system access control, secu-rity mode control, mobility management, and radio resource man-agement and control, etc.

ZXWR RNC provides all the functions defined in the 3GPPR99/R4/R5/R6/R7 protocol, and offers Iu, Iub, and Iur seriesstandard interfaces, which enable it to connect with CNs, RNCs,and Node Bs from different manufacturers.

Developed on a basis of ZTE all IP unified hardware platform,ZXWR RNC features a distributed design, separating control planeand user plane as well as interface and application. It supportsATM/IP dual protocol stack and can smoothly evolve to full IPUTRAN.

IntendedAudience

This manual is intended for engineers and technicians who performoperations on the ZXWR RNC.

Prerequisite Skilland Knowledge

To use this manual effectively, users should have a general under-standing of wireless telecommunications technology.

Familiar with the following is helpful:

� ZXWR RNC system and its various components

� Local operating procedures

What is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1 System Overview Introduces the basicsoftware/hardware systemstructure of the unifiedNM, installation flow, andsoftware/hardware environmentrequirements during theinstallation.

Chapter 2 Installing OperatingSystem

Introduces the process to installRed Hat AS 4 for x86 operatingsystem on the SBCX board. Forhow to install on the Windowoperating system, contact theMicrosoft Corporation or directlycontact ZTE engineers.

Confidential and Proprietary Information of ZTE CORPORATION I


Chapter Summary

Chapter 3 Installing SystemDatabase

Introduces the installationprocess of Oracle 10g for RedHat AS database, including thepreparations, steps and checks.

Chapter 4 Installing NM ServerSoftware

Introduces the installation processof the NM Server.

Chapter 5 Installing NM ClientSoftware

Introduces the installation processof the NM Client.

Chapter 6 Upgrading NM Serverand Client Software

Introduces the upgrading processof the NM Server and Clientsoftware.

Chapter 7 Uninstalling OMM NMSoftware

Introduces the uninstall processof the NM software.

Appendix A FAQ Introduces the solutions of FAQ.

II Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

System Overview

Table of ContentsNetwork Management System.............................................. 1System Structure ............................................................... 2Installation Flow................................................................17Configuration Requirements ................................................19

Network ManagementSystemLocation of OMM in the System

ZXWR RNC NMS includes NetNumen M31 (Mobile NE Managementsystem) and OMM.

� NetNumen M31 is the common wireless NE management sys-tem, realizing the global management and maintenance, asshown in Figure 1.

FIGURE 1 CONNECTION OF CENTRALIZED NM AND NE

� OMM is installed inside the ZXWR RNC rack, used for ZXWRRNC operation and maintenance. ZXWR RNC connects the NMSNetNumen M31 through OMM.

Confidential and Proprietary Information of ZTE CORPORATION 1


� In the ZXWR RNC system, the hardware platform of OMMadopts SBCX. SBCX is configured in M/S mode, which in-creases the reliability of the operation and maintenancemodule.

Basic Concepts of OMM Installation

Before the NMS installation, this manual will give describe commonconcepts.

1. Client/Server structure

Client/Server structure refers to that several clients andservers interconnect with each other through the LAN or theWAN. Users can log on at the Client, that is, they can operateon the resources saved on the Server. The Server feeds backthe operation results according to the users' requests.

2. Server

ZXWR RNC NMS adopts the Client/Server structure. The serverin the Client/Server structure includes the hardware at theServer and the software at the Server. The software at theServer refers to the Server programs of NMS. The hardwareat the server includes the computers or workstations that runthese programs.

3. Client

The Client in the client/server structure refers to the client pro-grams of the software. Users can install and run the Clientprograms on the computer where the Server software runs oron a separate computer.

System StructurePrior to NM software installation and application, you should getfamiliar to the software/hardware structure and networking modeof the system.

Hardware Structure

The selection of OMM hardware networking structure depends onthe actual network size and system load of the NM.

For detailed hardware networking structure, refer to ZXWR RNC(V3.07.310) radio Network Controller System Description.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 System Overview

OMM Software Structure

The structure of OMM NM software is as shown in Figure 2, whichincludes OMM Server programs and OMM Client programs.

FIGURE 2 OMM SOFTWARE STRUCTURE

As shown in Figure 2, OMM NM Server program supports the Linuxoperating system and it supports the Oracle database. OMM NMClient program supports the Windows operating system. In actualapplication, both the Client and the Server must be supported bya Java virtual machine. Both NM Server and NM Client support theWindows operating system and the Linux operating system.

Networking Mode

For the detailed networking mode, refer to ZXWR RNC (V3.07.310)Radio network Controller System Description.

M/S Configuration Mode of SBCX

The hardware platform of OMM adopts the M/S SBCX configurationmode, as shown in Figure 3.



FIGURE 3 M/S SBCX CONFIGURATION MODE

1. The network interface used byOMC1 is eth3. The left boardIP: 128.0.30.1; the right boardIP: 128.0.30.9 The left and rightboard MacAddr: 255.255.255.0

2. The network interface used byOMC2 is eth4, whose IP addressis set as needed. It is floating inthe same network segment withMINOS/OMM. The settings on the

left board are consistent with thaton the right board.

3. The network interface used byOMP1 is eth6, whose IP address isset as needed. It is floating in thesame network segment with ROMPexternal interface. The settings onthe left board are consistent withthat on the right board.

The master SBCX and the slave SBCX interconnects with thecrossover cable through the specified network interface. If themaster SBCX gets faulty and fails to work normally, the slaveSBCX will replace the master SBCX automatically.

The master SBCX connects another external SBCX which is usedas the log service through the switch. Besides, the master SBCX isembedded with the OMM Host process, as shown in Figure 4. TheOMM Host is an A/S monitoring process. When the external logservice SBCX starts, the SBCX started by the OMM Host processat first will serve as the active board; while the SBCX started bythe OMM Host process later will serve as the standby board. Ifthe active board doesn’t work normally, the OMM Host will triggeran active/standby changeover, which enables the standby boardto work as the active board.



FIGURE 4 LOG SERVICE CONFIGURATION

Database Configuration in SBCXActive/Standby Environment

When OMM is installed on SBCX board, you need to configure thedatabase. The modification to the database configuration files willimpact the machine name of SBCX board. Therefore, the machinename of the board should be unique in LAN. Meanwhile be sure tomake the database instances for active/standby board consistent.When OMM is installed on SBCX board, the following database con-figuration should be done to SBCX board.

Perform the following operations to the database configurationfiles:

1. Modify the configuration file /etc/rc.d/rc.local

2. Check the file configuration /etc/hosts

3. Check the file /etc/host.conf

4. Check database NET service name configuration

Modify theconfiguration file/etc/rc.d/rc.local

rc.local should be modified before Omm Host installation. Be-fore OmmHost installation, add the following information to theconfiguration file:

. /etc/profile

The screen output of the configuration file is shown as follows:#!/bin/sh # # This script will be executed *after* all the other init scripts.# You can put your own initialization stuff in here if you don't # want to dothe full Sys V style init stuff. touch /var/lock/subsys/local . /etc/profile

Check the fileconfiguration/etc/hosts

The file is used to map the machine name and IP address. Runthe following command:

#cat /etc/hosts. The output is as follows:



192.168.63.1 wsbcx11 10.62.102.71 wsbcx11 10.62.102.73wsbcx11 127.0.0.1 localhost

Tip:

The output in the previous description contains the example. Theactual output varies with the configuration.

127.0.0.1 localhost must be put at the last line.

192.168.63.1 is a virtual IP address for the network port not yetassigned by SBCX board. It must be put at the first line in the fileand be globally unique.

The virtual IP must be unique in active/standby SBCX board withinthe range of EMS managed OMM. Virtual IP should be assigned ina reasonable method.

For example: If the floating IP for OMM is 10.62.102.61/255.255.255.010.62.102.80/255.255.255.0, the fourth segment of thefloating IP can match the third segment of the virtual IP. Rules:

Left board IP range is 192.168.61.1/255.255.255.0192.168.80.1/255.255.255.0

Right board IP range is 192.168.61.2/255.255.255.0192.168.80.2/255.255.255.0

Tip:

10.62.102.71/73 is the channel IP bound with OMMRB and OMMB.

If the output is not consistent with the previous description, usegedit or vi command to modify the file.

#gedit /etc/hosts

Configure eth2 network port with the IP address 192.168.63.1,255.255.255.0

#cd /etc/sysconfig/network-scripts

#gedit ifcfg-eth2DEVICE=eth2 IPADDR=192.168.63.1 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet

If the system configuration file exists, only three options need tobe set: IPADDR, NETMASK and ONBOOT.

Check the file/etc/host.conf

Check whether the configuration file has a line containing multion. If not, run the following command to add this line into theright and left board configuration file.

#gedit /etc/host.conf. After modification, you can find:order hosts, bind multi on

Check databaseNET service name

configuration

After the installation of OMMRB and OMMB server side application,run the following command to check the left and right boards.

#cd /oracleapp/oracle/product/10.2.0/network/admin/

# cat tnsnames.ora

Make sure the following output is obtained:



womc_128.0.30.9 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.30.9)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womc)))womc_128.0.30.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.30.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womc)))womc_127.0.0.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womc)))womcb_128.0.29.9 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.29.9)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womcb)))womcb_128.0.29.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.29.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womcb)))womcb_127.0.0.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womcb)))

If the output is not complete, log in the system as the root ororacle user. Use netca tool to add the network service name foractive/standby IP on the right and left boards. Connect the net-work service name of 127.0.0.1 loopback address. The format isthe same as that for other network service name configuration.The procedures is as follows:

Note:

The tool needs to be run under GUI, such as VNC client side.

1. Right-click on the Linux desktop, choose to open the terminalfrom the menu.

2. Enter the following commands:

#xhost +

#su – oracle

$netca

The Welcome window shows up. Choose Local Net ServiceName configuration, as shown in Figure 5.

FIGURE 5 WELCOME

3. Click Next. In Net Service Name Configuration window,choose add, as shown in Figure 6.



FIGURE 6 NET SERVICE NAME CONFIGURATION

4. Click Next. Net Service Name Configuration, ServiceName window shows up, as shown in Figure 7.

FIGURE 7 NET SERVICE NAME CONFIGURATION, SERVICE NAME

Enter Service Name. Enter oracle instance name. The defaultnames are womc and womcb.

5. Click Next. In Net Service Name Configuration, SelectProtocol window. Select TCP protocol, as shown in Figure 8.



FIGURE 8 NET SERVICE NAME CONFIGURATION, SELECT PROTOCOL

6. Click Next. In Net Service Name Configuration, TCP/IPProtocol window, enter database host IP in Host Name. Keepthe other settings default, as shown in Figure 9.

FIGURE 9 NET SERVICE NAME CONFIGURATION, TCP/IP PROTOCOL

Note:

The I addresses in Figure 9 are examples.

7. Click Next. In Net Service Name Configuration, Test win-dow, choose to perform or not to perform the test, as shownin Figure 10.



FIGURE 10 NET SERVICE NAME CONFIGURATION, TEST

8. Click Next. In Net Service Name Configuration, Net Ser-vice Name window, enter the net service name, as shown inFigure 11.

FIGURE 11 NET SERVICE NAME CONFIGURATION, NET SERVICE NAME

Note:

Net Service Name follows the format of <SID>_<Host IP>.Figure 11 gives an example: zxomc_128.0.30.1.

9. Click Next. Net Service Name Configuration, AnotherNets Service Name window shows up, as shown in Figure12.



FIGURE 12 NET SERVICE NAME CONFIGURATION, ANOTHER NETSSERVICE NAME

After you have completed the above steps, the local service nameconfiguration is done with the host IP 128.0.30.1.

Make the similar configuration to the host IP 127.0.0.1,128.0.30.9, 128.0.29.1, 128.0.29.9.

Check the service name configuration of the left and right boardsto make sure the output is complete with the six items.womc_128.0.30.9 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.30.9)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womc)))womc_128.0.30.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.30.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womc)))womc_127.0.0.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womc)))womcb_128.0.29.9 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.29.9)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womcb)))womcb_128.0.29.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.29.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womcb)))womcb_127.0.0.1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = womcb)))

Caution:

The above configuration is based on the database instances of theleft and right boards. The data with left and right boards in ac-tive/standby environment is recommended to be consistent.

Configurations Related to OMM inM/S SBCX Mode

When OMM is installed on SBCX, the configuration files and con-figuration items of the NE M/S monitoring software are required tobe modified.



Note:

Except for the configuration items mentioned in this manual, it isrecommended not to modify other items.

All configuration files are saved under /home/zte/OmmHost/bin/conf, where OMM Host is installed. The configuration files to bemodified include:

1. system.conf

2. OmmProcConfig.conf

3. NetIf.conf

Modification of system.conf File

The system.conf file is located under /home/zte/OmmHost/bin/conf, where OMM Host is installed.

1. The ShareBoardWithOMM on system columnThis configu-ration item enables Omm Host to initialize with OMM. 0 for NOand 1 for YEW. For example:

ShareBoardWithOMM = 1

This example indicates Omm Host initializes with OMM

2. The BackupMode on system column: This configuration itemis enables the backup function 0 for no backup and 1 for 1+1backup. For example

BackupMode = 1

This example indicates 1+1 backup is applied.

3. The BoardPosition on system column: This configurationitem indicates whether SBCX is the left board or the rightboard. 0 indicates the left board and 1 indicates the rightboard. For example:

BoardPosition = 0

It indicates that the local SBCX is the left board.

Modification of OmmProcConfig.conf File

This configuration file is user for OMM process management.OMMR and OMMB are separated in V3.09.30 and you need toinstall two NM softwares: OMC-RB combined version and OMCB.Therefore, two OMM process are necessary.



Caution:

The start sequence of multi—software NM mode is: OmmProc1— OmmProcN; for single—software NM mode, only the processconfigured in OmmProc1 is initialized.

The following are the versions that separated OMMR and OMMB.

1. OmmProcNum item: This item decides the number of NMprocesses. For single mode, enter 1; for multiple mode, enterthe number as needed. For example:

OmmProcNum = 2

This example indicates 2 processes will be initialized.

2. ProcType item in OmmProc1 column:

� For single mode, make sure ProcType in OmmProc1 is4100.

� For the version with OMMR and OMMB, pay attention tothe corresponding relationships between process name andtype ID.

_OMMR_PROC = 4100, _OMMB_PROC = 4101 [The thirdprocess name] = 4102

3. ExePath item in OmmProc1 column: This configuration itemis used to set the running path for the OMMRB script. Forexample:

ExePath = /home/womc/ZXWR-RB/WOMC/ums-svr/bin/

This example indicate the installation path for the script startand exit is /home/womc/ZXWR-RB/WOMC/ums-svr/bin/

4. ExePath item in OmmProc2 column: This configuration itemis used to set the running path for the OMMB script. For ex-ample:

ExePath = /home/zxomcb/ZXOMCB/ums-svr/bin/

This example indicate the installation path for the script startand exit is /home/womc/ZXWR-RB/WOMC/ums-svr/bin/

Note:

In this chapter:

1. The file path for Oracle installation package:data1/10201_database_linux32.zip

2. The installation directory for Oracle: /home/oracle

3. The file path for OMM server installation package: data1/zx-womc

4. OMMRB server installation directory: /home/womc/ZXWR-RB/WOMC/

5. OMMB server installation directory: /home/zxomcb/ZXOMCB/

6. Omm Host installation directory: /home/zte/OmmHost/



You can change the file paths as needed. Make sure the change isconsistent with the paths in the related configuration.

Modification of NetIf.conf File

The NetIf.conf file is located under /home/zte/OmmHost/bin/c-onf, where OMM Host is installed.

1. The parameter Count in CommChannel column:

This parameter indicates the number of network interfaces en-abled, which is equal to the number of network interfaces con-figured. These interfaces are enabled in turn from Channel1to ChannelX. This order has nothing to do with user input se-quence.

2. The parameter IP under Channel3:

This parameter indicates the IP address of the NM M/S path.By default, 128.0.30.1 is configured for the left board and128.0.30.9 for the right board. The IP address is generatedby the slot.

3. Channel4 column indicates the OMCR channel (for OMM) andMINOS connection channel.

� ChannelName= OMM_OMCR_OMC2NetIfName = eth4

This item indicates the ID of a channel.

� IP item and NETMAS item

IP address and subnet mask.

� MacAddr item:

MacAddr of the left board and right board must be identical.Refer to the MAC address of the left SBCX board or theaddress generated according to the foreground RNC. TheMAC information is just written in NetIf.conf file. Do notwrite it into the network interface configuration file.

� GateWay item is set to be the gateway address to theexternal network.

� NeedSetDefaultGateWay: 1 for default gateway.

4. Channel5 column: This interface should be configured withmain network IP bound with OMCB. The following settings arerecommended to share the network segment with eth4.

� ChannelName= OMM_OMCR_OMC2NetIfName = eth4:1


� IP item and NETMAS item:

IP address and subnet mask.

� MacAddr item:

You cannot set MAC address

� GateWay item is set to be the gateway address to the ex-ternal network. If the IP address is in the same network



segment with eth4, this item does not need to be config-ured.

� NeedSetDefaultGateWay item must be 0.

5. Channel6 column: The interface is for OMP OMM (For OMMfunction).

� ChannelName= OMCR_OMP_OMCBNetIfName = eth6


� IP item and NETMAS item:

IP address and subnet mask. The IP must in the samenetwork segment with OMP. The configuration with activeboard and standby board must be consistent.

� MacAddr item:

The configuration with active board and standby boardmust be consistent. MacAddr for the left board and theright board must be identical. Refer to the MAC address ofthe left SBCX board or the address generated according tothe foreground RNC. The MAC information is just written inNetIf.conf file. Do not write it into the network interfaceconfiguration file.


6. Channel7 column: The interface is for OMCB channel (forOMM-RB function).

Note:

� One end is connected with Node B and share eth6 withOMP-OMM channel.

� One end is connected with GIPI board through which thedata is transported to OMCB.

� ChannelName=OMCB_eth6_1, NetIfName = eth6:1


� IP item and NETMASitem:

IP address and subnet mask for OMCB channel

The IP must be in the same network segment with GIPIgateway IP.

� MacAddr must be blank.

� GateWay is for OMCB channel. Enter GIPI gateway IP.

� NextSkipIP is for OMCB channel. Enter IPOA destinationsubnet.

� NextSkipNetMask is for OMCB channel. Enter IPOA des-tination network segment.

� NeedSetDefaultGateWay must be 0.

7. Channel8 column: The interface is for OMCB channel (forOMMB function).



Note:

� One end is connected with Node B and share eth6 withOMP-OMM channel.

� One end is connected with GIPI board through which thedata is transported to OMCB.

� ChannelName=OMCB_eth6_1NetIfName = eth6:2


� IP item and NETMAS item

IP address and subnet mask for OMCB channel

IP must be in the same network segment with GIPI gate-way IP. The NETMAS must be in the same network seg-ment with OMP. The configuration with active board andstandby board must be consistent.

� MacAddr item must be blank.

� GateWay item is for OMCB channel. Enter the GIPI gate-way IP.

� NextSkipIP item is for OMCB channel. Enter IPOA desti-nation subnetwork.

� NextSkipNetMask item is for OMCB channel. Enter IPOAdestination network segment.


Note:

i. Network interface floating means the interface only workson the active board. It is not effective on the standbyboard.

ii. GateWay, NextSkipIP, NextSkipNetMask are config-ured only when the gateway is used to connect to the ex-ternal network.

iii. When the gateway on the network adapter needs to be setas default, NeedSetDefaultGateWay should be 1.

If NeedSetDefaultGateWay is 0, it is a default gateway.When there are several network adpaters, NeedSetDefault-GateWay should be 1. The last loaded gateway is regardedas default by OMM Host.

iv. When the IP on the interface needs floating, MAC addressmust be set.

v. MAC address: 00:D0:D0:FA:12:01. Any value can be ap-plied if with no conflict. to avoid conflict, use the methodof RNC foreground MAC address calculation, as shown inTable 1



TABLE 1 MAC ADDRESS CALCULATION

byte 0 byte 1 byte 2 byte 3 byte 4 byte 5

0x00 0xd0 0xd0 1AAAB-BBB

0CCG-FFF

EEEDD-DDD

– byte0 to byte5 indicates the six digits for MAC Address– AAA: Office ID (0–7)– BBBB: Rack ID (0–15)– CC: Shelf ID (0–3)– DDDDD: Slot ID (1–17)– EEE: CPU ID (0–7)– FFF: Network Interface ID (0–7)– I: For control plane IP and MAC, I=0; for OSS virtual IP and MAC,

I=1.– G: 0 or 1– The A-G are all in binary, that is, AAA means three binary digits, for

example, 11 indicates 3.

vi. When MacAddr, GateWay, NextSkipIP and NextSkipNet-Mask do not need to be configured, just set as blank.

Connection Method of Backplane NetworkInterface

1. OMC1: The master SBCX and the slave SBCX interconnectthrough the crossover cable.

2. OMC2: The network section where OMCB path is accessed.

3. OMP: The 129 network section where OMP is accessed.

Note:

The network section where OMP accesses is the network sec-tion of the on-site environment LAN. 129 mentions here is justan example. Access according to the actual situations.

4. RS232: The network section where NM client is accessed.

5. Currently, Heart1 and Heart2 are disabled.

Installation FlowThe installation flow of NM software is as shown in Figure 13.



FIGURE 13 INSTALLATION FLOW OF NM SOFTWARE

As shown in Figure 13, the installation of NM software falls intoServer and Client.

At the server, the software installation includes the operating sys-tem installation, database installation and OMM server software.

At the client, the software installation includes the operating sys-tem installation and OMM client software.

The NM Server and NM Client can be installed at the same time.Generally, the Server is installed in the Linux operating systemwhile the Client is installed in the Linux operating system. There-fore, the Server and the Client are installed separately in the in-stallation flow.



Configuration RequirementsOMM Server HardwareConfigurations

The hardware configurations of SBCX Server are as shown in Table2.

TABLE 2 SBCX SERVER HARDWARE CONFIGURATIONS

Managed Object Configurations

CPU Intel(R) Xeon 2G*2

Memory 8 G

Harddisk SAS sda=146G(RAID1)

Network card Inter Corporation 8255xER/82551T Fast EthernetController * 3

Intel Corporation 82571EB Gigabit EthernetController * 4

OMM Server Software Configurations

The software configurations of SBCX Server are as shown in Table3.

TABLE 3 SERVER SOFTWARE CONFIGURATIONS


Operating system Linux platform: Red Hat AS 4

Database Oracle10g Release 2 EnterpriseEdition for Linux

OMM Server OMM Server software

OMM Client Hardware Configurations

OMM Client adopts the PC as the workstation, and its minimumconfiguration requirements are as shown in Table 4.



TABLE 4 CLIENT HARDWARE CONFIGURATIONS


CPU Intel P4 or above, Intel Core2

Memory 1 G or above

Embedded harddisk 80 GB or above

OMM Client Software Configurations

The software configurations of OMM Client are as shown in Table5.

TABLE 5 CLIENT SOFTWARE CONFIGURATIONS


Operating System MS Windows 2000 Professional

Windows XP

Windows 2003

Browser Netscape

IE6.0

File browsing tool MS Office 2000

Anti-virus software McafeeVirusScan8.0 or Norton

OMM Client OMM Client Software

Note:

1. SBCX is pre-installed with some system software before de-livery, such as, operating system software and database soft-ware, so it is not required to be installed on the site. Ins omespecial cases (such as, on-site software/hardware upgrading),it may be necessary to re-install the SBCX. This manual willgive descriptions below for reference.

2. in the command lines in this manual, # indicates the currentusers is the root.


C h a p t e r 2

Installing OperatingSystem

Table of ContentsOverview..........................................................................21Installing SBCX Server Operating System .............................21

OverviewThe flow to install the Red Hat AS 4 for x86 operating system onSBCX Server is as below:

1. Preparations

2. Steps

3. After the installation

After the installation, the operations include:

1. Configure Telnet access

2. Configure remote graphic access

3. Configure FTP server

4. Set samba

For the installation of Windows operating system, log on the web-site of Microsoft Corporation for support or directly contact engi-neers of ZTE Corporation.

Installing SBCX ServerOperating SystemPreparations

1. Prepared the installation disk of Red Hat AS 4.

2. Prepare the hardware configuration surroundings of SBCX.



3. Make sure the following information before the installation.Make plans according to the network surroundings and actualapplications.

i. IP address and sub-network mask.

ii. Host machine name

The host machine name must be unique in the domain.Otherwise, the network may go faulty after Linux is in-stalled.

iii. Hard disk partition

4. Set the BIOS for the machine and start from the driver.

5. Prepare one display, one 220 V multi function power adapter,a set of PS/2 keyboard and mouse. Usually, the mouse usesthe jade-green interface and the keyboard uses the purple in-terface.

Steps to install SBCX ServerOperating System

Steps 1. If the machine is OFF, turn on the machine first. Insert the firstdisk into the driver and restart the machine. When the DOSprompt of boot: pops up, press Enter.

2. Welcome to Red Hat Enterprise Linux interface pops up,where the disk is checked.

3. Click Skip and Welcome to Red Hat Enterprise Linux ASinterface pops up.

4. Click Next and Language Selection interface pops up. SelectU.S. English.

5. Click Next and Keyboard Configuration interface pops up.Select U.S. English.

6. Click Next and Disk Partition interface pops up. Selectman-ually Partition with Disk Druid andWarning interface popsup.

7. Click Yes and Disk Setup interface pops up.

Partition the disk. The system type of swap partition file isswap and of other partition files is ext3, as shown in Table 6.

TABLE 6 DISK PARTITION

Disk MountingPoint

SystemType

Size

/boot ext3 200 M (obliged to be themaster partition and theappointed space size)

swap swap 8 G (obliged to be the masterpartition and the appointedspace size)

SAS(s-da)


Chapter 2 Installing Operating System

Disk MountingPoint

SystemType

Size

/ ext3 10 G (obliged to be themaster partition and theappointed space size)

/oracleapp ext3 6 G (the appointed spacesize)

/home ext3 40 G

/backup ext3 6 G (the appointed spacesize)

/oracle-data

ext3 Remaining

8. Click Next and Booting Load Program Configuration inter-face pops up.

Keep the default value of Take GRUB as booting load pro-gram.

Select Red Hat Enterprise Linux AS as the default bootingsystem.

Select Configure senior booting load program options.

9. Click Next and Senior booting load program configurationinterface pops up.

Select /dev/sdbMaster Booting Record (MBR) for Installationlocation of booting load program records.

Note:

If it is /dev/sdb Master Booting Record (MBR), change thebooting sequence. Select the SATA harddisk menu and putit to the first option, click Confirm and then install.

10.Click Next and Network Configuration interface pops up.Set the hardware and configurations of the network devices.

� Select eth3 and click Edit.

Uncheck Configure with DHCP.

Check Enable when Booting.

Enter the IP address, such as, 129.0.31.100.

Enter the network mask, such as, 255.255.252.0.

Note:

The IP address and network mask mentioned in this manualare just examples. Fill int he values according to the actualnetwork surroundings.

� Select Manual setting in Host machine name.



Enter the host machine name according to the host ma-chine naming rules, such as, sbcx01.wcdma.

� Keep default values for Other settings.

11.Click Next and Warning interface pops up.

12.Click Continue and Firewall configuration interface pops up,where the configurations related to the firewall are configured.

Check No firewall.

Check Disable before Enable SELinux or not.

13.Click Next and Warning-No firewall interface pops up.

14.Click Continue and Additional language support interfacepops up.

Select English (USA).

15.Click Next and Time Zone Configuration interface pops up,where the time zone is selected according to the actual cases.

Make sure Use UTC is unchecked.

16.Click Next and Set root user password interface pops up.Enter the same passwords twice and then the password takeseffect.

17.Click Next and Select software packet interface pops up.Select Customize the software packet to install.

The software packets to install include (by default, there areno software packets are required to be installed under level-2menu):

X window system

GNOME desktop surroundings

Editor

Server configuration tools

Windows file Server

FTP Server

Network Server

Extra software packer

vnc-server - VNC Server

dhcp - DHCP Server and forwarding agent

Remaining network Server

Extra software packet

tftp-server - TFTP Server

telnet-server - the Server program for telnet remote login pro-tocol

Development tool

Original software development

Management tool

System tool

Extra software packet



ethereal - Network transport analyzer

nmap - Network searching tool and security scanner

sysstat - sar and iostat system monitoring command

18.Click Next and Install interface pops up.

19.ClickNext and Required installationmedium interface popsup. Insert the installation disk.

20.Click Continue and insert disks according to the prompts. Thisstep may take about half and hour to one hour, which dependson the quantity of the software packets and the speed of themachine.

21.When the installation completes, take out the disk and clickRestart the computer.

22.Set BIOS for the machine and cancel to start from the driver.

23.Restart the computer and Welcome interface pops up.

24.Click Next and License Agreement interface pops up. SelectI agree.

25.Click Next and Data and Time interface pops up. Set thedata and time for the Server.

26.Click Next and Display interface pops up. Keep the defaultvalues.

27.Click Next and Red Hat Access Login interface pops up. Se-lect Tell me why i need to register and provide one RedHat login accountant.

28.Click Next and Why to register interface pops up. Select ican not register now, and please remind me later.

29.Click Next and Initialization interface pops up. And thenLicence interface pops up. Select Accept.

30.Click Next and System user interface pops up. Create thewomc user.

User name: womc

Full name: womc

Password: womc123

Verify: womc123

31.Click Next and Audio car interface pops up. Keep the defaultvalues.

32.ClickNext and Extra disks interface pops up. Keep the defaultvalues.

33.Click Next and End of Settings interface pops up.

34.Click Next and the system enters the graphic access interface.

END OF STEPS



After the Installation

After the Red Hat AS 4 is installed, to run the OM programs, thefollowing system settings are required.

Configuring Telnet Access

Steps 1. Edit /etc/xinetd.d/krb5-telnet as the root user with thefollowing command:

#vi /etc/xinetd.d/krb5-telnet

Change disable ＝ yes into disable = no.

2. Restart the xinet service with the following command:

# service xinetd restartStop xinetd: [OK]

Start xinetd: [OK]

END OF STEPS

Configuring Remote Graphics Access

Context The remote graphics have two modes:

� vnc: Access through the tool of vncviewer/ultravnc.

� xdmcp: Access through the tool of exceed/Xmanager.

Steps 1. Configuring xdmcp access

i. Edit the /etc/X11/gdm/gdm.conf file as the root userwith the following command:

#vi /etc/X11/gdm/gdm.conf

Find the command line next to xdmcp and change En-able=fasle into Enable=true.

ii. Restart the gdm with the following command:

#/usr/sbin/gdm-restart

iii. Access through the tool of exceed/Xmanager that sup-ports the Xdmcp mode, that is, control at the remote.

2. Configuring VNC access

i. Log on the Server in the telnet mode as the user who needsto be configured with VNC remote graphic access and startthe vncserver.

Take the access as the womc user as an example:

Enter the command of $ vncserverYou will require a password to access your desktops.

Password:womc123

Verify:womc123



New 'sbcx01.wcdma:1 (womc)' desktop is localhost.localdomain:1

Creating default startup script /home/womc/.vnc/xstartup

Starting applications specified in /home/womc/.vnc/xstartup

Log file is /home/womc/.vnc/sbcx01.wcdma:1.log

ii. Modify the graphic window manager of the vnc access andthen restart the vncserver.

Enter the command of $ vi .vnc/xstartup

Change twm & into gnome-session &.

Enter the command of $ vncserver -kill :1.

Enter the command of $ vncserver.New 'sbcx01.wcdma:1 (womc)' desktop is sbcx01.wcdma:1

Starting applications specified in /home/womc/.vnc/xstartup

Log file is /home/womc/.vnc/sbcx01.wcdma.log

iii. Access such VNC tool as utltravnc, run the vncviewer.exeon the PC at the client, and then connect to the SBCX Serverthrough LAN.

Enter 129.0.31.100 (IP address of the host machine) forthe VNC Server. The login password is womc123. The re-mote access succeeds.

Note:

The IP address of the VNC Server is the IP address of theSBCX Server.

END OF STEPS

Configuring FTP Server

Context users need to set the ftp server for the operating system, so thatthey can send files from the Client.

Steps 1. Modify the /etc/vsftpd/vsftpd.conf as the root user withthe following command:

# vi /etc/vsftpd/vsftpd.conf

The line of listen_port=10021 is added.

2. Start the vsftpd with the following command:

# /etc/init.d/vsftpd startStarting vsftpd for vsftpd: [OK］

3. Modify the service configurations to make them run automati-cally when the system starts with the following commands:

#chkconfig --level 345 vsftpd on

#chkconfig --list vsftpd

vsftpd 0:OFF 1:OFF 2:OFF 3:ON 4:ON 5:ON 6:OFF

4. Set the FTP tool for the Client to send files.



Note:

The FTP port at the Client is configured when the operation andmaintenance software is installed at the Server.

END OF STEPS

Setting samba

Context Samba service is a file sharing service through multi operating sys-tems. Through the Samba service, users can access the sharingfolder of Linux and perform related operations through Windows,such as, uploading the version files and downloading the files.

Steps 1. Set the user name for the samba service as the root user withthe following command:

# smbpasswd -a womcNew SMB password: womc123

Retype new SMB password: womc123startsmbfilepwent_internal: file /etc/samba/smbpasswd did not exist.File successfully created.Added user womc.

2. Start the samba service with the following command:

# /etc/init.d/smb startStart SMB service: [OK]

Start NMB service: [OK]

3. Modify the service configurations to make them run automati-cally when the system starts with the following commands:

#chkconfig --level 345 smb on

#chkconfig --list smb

smb 0:OFF 1:OFF 2:OFF 3:ON 4:ON 5:ON 6:OFF

the operation example is as shown in Figure 14.



FIGURE 14 ADDING SAMBA USER

Set the path of the shared folder by modifying the/etc/samba/smb.conf file and set the writable rights, asshown in Figure 15.

FIGURE 15 SETTING SHARED FOLDER

END OF STEPS





C h a p t e r 3

Installing SystemDatabase

Table of ContentsOverview..........................................................................31Installing Oracle 10g Database ............................................32

OverviewOMM NMS supports the Oracle database.

The steps to install the Oracle 10g database under Linux operatingsystem are as below:

1. Preparations

i. Check the installation surroundings.

ii. Check the system kernel parameters.

iii. Modify shell limits.

iv. Create the user and user group.

v. Create the user directory and modifying the rights.

vi. Set the environment variables.

2. Steps

i. Install the Oracle 10g 10.2.0.1.0.

ii. Install the Oracle patches.

iii. Configure the listener program.

iv. Create the database.

3. Checks

� Check whether the Oracle database program can be con-nected/started/stopped.

� Check whether the Oracle listener program can bestarted/stopped.

� View the database character set.

� Configure the auto startup/closeup of the Oracle.



Note:

Oracle database can be installed on the same machine wherethe OMM Server is installed or on different machine. If the datathroughput of the Oracle is large, it is suggested to install theOracle database and the OMM Server on different machines.

Installing Oracle 10gDatabasePreparations for Oracle 10g DatabaseInstallation

Checking Installation Surroundings

Context Before installing the Oracle 10g database, make sure that the fol-lowing surroundings are ready.

Steps 1. SBCX is powered on normally, the operating system of Red HatAS4 is running normally, and the cable connecting the ETH3is normal.

2. Get the Oracle10g installation disks or installation pack-ets ready. This manual takes the installation packet(10201_database_linux32.zip) as an example.

3. Make sure that no Oracle database of any version exists in theoperating system. If there is any, delete the database beforeinstalling the new version.

Note:

When uninstalling the database, delete the default installationdirectory of the Oracle.

END OF STEPS

Checking System Kernel Parameters

Steps 1. Right-click on the desktop of the Linux system and select OpenTerminal.

2. Log in as the root user.


Chapter 3 Installing System Database

3. Enter the /etc and open the sysctl.conf file with the followingcommand:

#vi /etc/sysctl.conf

4. Add the following contents at the end of the /etc/sysctl.conffile:

kernel.shmall=2097152

kernel.shmmax=2147483648

kernel.shmmni=4096

kernel.sem=250 32000 100 128

fs.file-max=65536

net.ipv4.ip_local_port_range=1024 65000

net.core.rmem_default=1048576

net.core.rmem_max=1048576

net.core.wmem_default=1048576

net.core.wmem_max=1048576

5. Execute the kernel parameter with the following command:

#/sbin/sysctl -p /etc/sysctl.conf

END OF STEPS

Modifying shell limits



3. Enter the /etc/security and open the limits.conf file withthe following command:

#vi /etc/security/limits.conf

4. Modify the contents into the following at the end of the lim-its.conf file.

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 1024

oracle hard nofile 65536

5. Execute the following command:

#vi /etc/pam.d/login

6. Add the following line:

session required pam_limits.so


#vi /etc/profile

8. Add the following lines:



if [ $USER = “oracle” ]; then

if [ $SHELL = “/bin/ksh” ]; then

ulimit -p 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

fi

fi

END OF STEPS

Creating User and User Group

Context Log in the system as the root user and create the dba group andoracle user.

Steps 1. Execute the following command:

#groupadd dba


#groupadd oinstall


#useradd -d /home/oracle -m -g oinstall -G dba oracle


#passwd oracle

Note:

/home/oracle is the path of the oracle user.

END OF STEPS

Creating User Directory and Modifying Rights

Steps 1. Execute the following command:

#mkdir -p /oracleapp/oracle


#chown -R oracle:oinstall /oracleapp


#chmod -R 755 /oracleapp


#mkdir -p /oracledata/womc




#chown -R oracle:oinstall /oracledata


#chmod -R 755 /oracledata

Note:

oracleapp is the installation point of the Oracle software andoracledata is the installation point of the Oracle database.

END OF STEPS

Setting Environment Variables



3. Open the /etc/profile file with the following command:

#vi /etc/profile

4. Add the following lines:

ORACLE_BASE=/oracleapp/oracle

ORACLE_HOME=$ORACLE_BASE/product/10.2.0

ORACLE_SID=womc

NLS_LANG=AMERICAN_AMERICA.ZHS16GBK

PATH=$PATH:$ORACLE_HOME/bin:/bin:/usr/bin:/sbin:/us-r/sbin

export ORACLE_BASE ORACLE_HOME ORACLE_SID NLS_LANGPATH

umask 022

Note:

i. Save the settings, log out the root user, and then log inas the root user. As a result, the /etc/profile file takeseffect.

ii. When installing the application software at the Server, domodify the /etc/profile file.

END OF STEPS



Steps to install Oracle 10g Database

Installing Oracle 10g 10.2.0.1.0

Steps 1. Right-click the desktop of the Linux system and select OpenTerminal, as shown in Figure 16.

FIGURE 16 SELECTING OPEN TERMINAL

2. Open the target folder to view whether all software installationprograms exist, as shown in Figure 17.

FIGURE 17 VIEWING FOLDER



3. Copy the software program file of 10201_data-base_linux32.zip to the /home/oracle, as shown in Figure18.

FIGURE 18 COPYING 10201_DATABASE_LINUX32.ZIP FILE

4. Log in the system as the oracle user from the root user, asshown in Figure 19.

FIGURE 19 LOGGING IN AS ORACLE USER

5. View the files under the oracle user and enter the installtmpfolder (If there is no installtmp folder, create it.), as shown inFigure 20.



FIGURE 20 ENTERING INSTALLTMP FOLDER

6. Move the 10201_database_linux32.zip file in the installtmpfolder and decompress it, as shown in Figure 21.

FIGURE 21 DECOMPRESSING 10201_DATABASE_LINUX32.ZIP FILE

7. After decompressing the file, enter the database folder, asshown in Figure 22.



FIGURE 22 ENTERING DATABASE FOLDER

8. View the contents in the database folder and run the runIn-staller file, as shown in Figure 23.

FIGURE 23 RUNNING RUNINSTALLER FILE

9. The Select Installation Method interface pops up, as shownin Figure 24. Select Advanced Installation.



FIGURE 24 SELECT INSTALLATION METHOD INTERFACE

10.Click Next and Select Installation Type interface pops up,as shown in Figure 25. Select Custom.

FIGURE 25 SELECT INSTALLATION TYPE INTERFACE

11.Click Next and the Specify Home Details interface pops up,as shown in Figure 26.



FIGURE 26 SPECIFY HOME DETAILS INTERFACE

Click Browse and enter/select the name and full installationpath of the product to install as required.

Note:

It is not required to modify the source path. It is not rec-ommended to install the Oracle under the computer operatingsystem directory because the installation directory needs largespace.

The full path of the Oracle application installation should meetthe disk space requirement mentioned in the preparation.

The maximum length of the Oracle main directory is 16 char-acters, which consist of letters, numbers and underlines. NoChinese characters or spaces are allowed. If there is an Ora-cle10g in the system, delete it first.

12.Click Next and Available Product Components interfacepops up, as shown in Figure 27.



FIGURE 27 AVAILABLE PRODUCT COMPONENTS INTERFACE

Select the product components as below:

i. Oracle10g 10.2.0.1.0

ii. In Enterprise Edition Option 10.2.0.1.0

– Oracle Advanced Security 10.2.0.1.0

– Oracle Partitioning 10.2.0.1.0

– Oracle Spatial 10.2.0.1.0

– Oracle OLAP 10.2.0.1.0

iii. In Oracle Net Services 10.2.0.1.0

– Oracle Net Listener 10.2.0.1.0

– Oracle Connection Manager 10.2.0.1.0

iv. Oracle Enterprise Manager Console DB 10.2.0.1.0

v. OracleCall InterfaceOCI10.2.0.1.0

vi. OracleProgrammer 10.2.0.1.0

vii. OracleXML Development Kit 10.2.0.1.0

viii. OracleODBC Driver 10.2.0.1.0

13.Click Next and Product-Specific Prerequisite Checks inter-face pops up, as shown in Figure 28.



FIGURE 28 PRODUCT-SPECIFIC PREREQUISITE CHECKS INTERFACE

If any value in the Status column is Warning, click the item toview the details. Handle it and then click Retry until all valuesbecome Succeeded.

14.After all values in the Status column become Succeeded,Privileged Operating System Groups interface pops up, asshown in Figure 29.

FIGURE 29 PRIVILEGED OPERATING SYSTEM GROUPS INTERFACE

Fill in dba for both Database Administrator (OSDBA) Groupand Database Operator (OSOPER) Group.



15.Click Next and the Create Database interface pops up, asshown in Figure 30.

FIGURE 30 CREATE DATABASE INTERFACE

16.Click Next and the Summary interface pops up, containingall components summary of the Oracle10g to be installed, asshown in Figure 31.

FIGURE 31 SUMMARY INTERFACE

17.Click Install and the Install interface pops up, as shown inFigure 32.



FIGURE 32 INSTALL INTERFACE

Note:

The installation may take about ten minutes, which dependson the configurations of the machine.

18.When the progress bar reaches 100%, Execute Configura-tion Scripts interface pops up, as shown in Figure 33.

FIGURE 33 EXECUTE CONFIGURATION SCRIPTS

19.Click OK and the system returns to the command window.Enter the /oracleapp/oracle/product/10.2.0/ and run theroot.sh file, as shown in Figure 34.



FIGURE 34 RUNNING ROOT.SH FILE

20.End of Installation interface pops up, as shown in Figure 35.

FIGURE 35 END OF INSTALLATION INTERFACE

21.Click Exit and Exit interface pops up, as shown in Figure 36.



FIGURE 36 EXIT INTERFACE

22.Click Yes and the Oracle 10g 10.2.0.1.0 installation completes.

END OF STEPS

Installing Oracle Patches

Steps 1. Enter the installtmp folder in the Linux command window anduncompress the p6810189_10204_Linux-x86.zip file, asshown in Figure 37.

FIGURE 37 UNCOMPRESSING P6810189_10204_LINUX-X86.ZIP FILE

2. After the uncompressing completes, enter theDisk1 folder andrun the runInstaller file, as shown in Figure 38.




3. Welcome interface pops up, as shown in Figure 39.

FIGURE 39 WELCOME INTERFACE

4. Click Next and Specify Home Details interface pops up, asshown in Figure 40.



FIGURE 40 SPECIFY HOME DETAILS INTERFACE

]

Click Browse and enter the installation path of the Oracleproduct.

5. Click Next and Product-Specify Prerequisite Checks inter-face pops up, as shown in Figure 41.

FIGURE 41 PRODUCT-SPECIFY PREREQUISITE CHECKS INTERFACE

If any value in the Status column is Warning, click the item toview the details. Handle it and then click Retry until all valuesbecome Succeeded.



6. After all values in the Status column become Succeeded, OracleConfiguration Manager Registration interface pops up, asshown in Figure 42.

FIGURE 42 ORACLE CONFIGURATION MANAGER REGISTRATIONINTERFACE

7. Click Next and Summary interface pops up, as shown inFigure 43.

FIGURE 43 SUMMARY INTERFACE

8. Click Install and Install interface pops up, as shown in Figure44.



FIGURE 44 INSTALL INTERFACE

9. When the progress bar reaches 100%, Execute Configura-tion Scripts interface pops up, as shown in Figure 45.

FIGURE 45 EXECUTE CONFIGURATION SCRIPTS

10.Open the command window of the Linux system, enter the/oracleapp/oracle/product/10.2.0/root.sh to run theroot.sh file, as shown in Figure 46.



FIGURE 46 RUNNING ROOT.SH FILE

When the system queries whether to cover the current folderon the command window, select y.

11.Click OK and End of Installation interface pops up, as shownin Figure 47.

FIGURE 47 END OF INSTALLATION INTERFACE

12.Click Exit and Exit interface pops up, as shown in Figure 48.



FIGURE 48 EXIT INTERFACE

13.Click Yes and the Oracle 10g patch installation completes.

END OF STEPS

Configuring Listener

Steps 1. Right-click on the desktop of the Linux system and select OpenTerminal, as shown in Figure 49.


2. Enter the command, as shown in Figure 50.



FIGURE 50 ENTERING LISTENER CONFIGURATION COMMAND

3. Welcome interface pops up, as shown in Figure 51.

FIGURE 51 ORACLE NET CONFIGURATION ASSISTANT: WELCOMEINTERFACE

4. Select Listener configuration and then click Next, and theinterface as shown in Figure 52 pops up.



FIGURE 52 ORACLE NET CONFIGURATION ASSISTANT: LISTENERINTERFACE

5. Click Next and Listener name interface pops up, as shown inFigure 53.

FIGURE 53 ORACLE NET CONFIGURATION ASSISTANT: LISTENER NAMEINTERFACE

6. Fill in Listener name and then click Next, and Select Protocolinterface pops up, as shown in Figure 54.



FIGURE 54 ORACLE NET CONFIGURATION ASSISTANT: SELECTPROTOCOL INTERFACE

TCP is in Selected Protocols column by default.

Click as needed and put the target protocol from theAvailable Protocols column to the Selected Protocolscolumn.

7. Click Next and TCP/IP Protocol interface pops up, as shownin Figure 55.

FIGURE 55 ORACLE NET CONFIGURATION ASSISTANT: TCP/IPPROTOCOL INTERFACE

8. Select Use the standard port number of 1521 or Use an-other port number a required, and click Next, and MoreListeners interface pops up, as shown in Figure 56.



FIGURE 56 ORACLE NET CONFIGURATION ASSISTANT: MORE LISTENERSINTERFACE

� Click Yes to configure another listener.

� Click No to complete the configuration.

9. Click Next and Listener Configuration Done interface popsup, as shown in Figure 57.

FIGURE 57 ORACLE NET CONFIGURATION ASSISTANT: LISTENERCONFIGURATION DONE INTERFACE

10.Click Next and the interface shown in Figure 58 pops up.



FIGURE 58 LISTENER CONFIGURATION COMPLETE INTERFACE

11.Click Finish to exit from the listener configuration interface.The related information is displayed on the Linux commandwindow, as shown in Figure 59.

FIGURE 59 DISPLAYING LISTENER CONFIGURATION INFORMATION

END OF STEPS

Creating Database






FIGURE 61 ENTERING DATABASE CREATION COMMAND

3. The Welcome interface pops up, as shown in Figure 62.



FIGURE 62 DATABASE CONFIGURATION ASSISTANT: WELCOMEINTERFACE

4. Select Listener configuration and then click Next, and theDatabase Configuration assistant, Step 1 of 12: Opera-tions interface pops up, as shown in Figure 63.

FIGURE 63 DATABASE CONFIGURATION ASSISTANT, STEP 1 OF 12:OPERATIONS INTERFACE

5. Click Next and the Database Configuration assistant, Step2 of 12: Database Template interface pops up, as shown inFigure 64. Select General Purpose.



FIGURE 64 DATABASE CONFIGURATION ASSISTANT, STEP 2 OF 12:DATABASE TEMPLATE INTERFACE

6. Click Next and the Database Configuration Assistant,Step 3 of 12: Database Identification interface pops up, asshown in Figure 65. Fill in womc for both Global databaseName and SID.

FIGURE 65 DATABASE CONFIGURATION ASSISTANT, STEP 3 OF 12:DATABASE IDENTIFICATION INTERFACE

7. Click Next and the Database Configuration Assistant, Step4 of 12: Management Options interface pops up, as shownin Figure 66. Keep the default values.



FIGURE 66 DATABASE CONFIGURATION ASSISTANT, STEP 4 OF 12:MANAGEMENT OPTIONS INTERFACE

8. Click Next and the Database Configuration Assistant, Step5 of 12: Database Credentials interface pops up, as shownin Figure 67. Enter the password. It is recommended to useoracle as the password.

FIGURE 67 DATABASE CONFIGURATION ASSISTANT, STEP 5 OF 12:DATABASE CREDENTIALS INTERFACE

9. Click Next and the Database Configuration Assistant, Step6 of 12: Storage Options interface pops up, as shown inFigure 68. Keep the default values.



FIGURE 68 DATABASE CONFIGURATION ASSISTANT, STEP 6 OF 12:STORAGE OPTIONS INTERFACE

10.Click Next and the Database Configuration Assistant, Step7 of 12: Database File Locations interface pops up, asshown in Figure 69. Select Use Common Location for AllDatabase Files.

FIGURE 69 DATABASE CONFIGURATION ASSISTANT, STEP 7 OF 12:DATABASE FILE LOCATIONS INTERFACE

Click and select the folder path in the DirectoryBrowse dialog box that pops up.

Click OK and the system returns to the Database Configu-ration Assistant, Step 7 of 12: Database File Locationsinterface, as shown in Figure 70.



FIGURE 70 DATABASE FILES LOCATION

11.Click Next and the Database Configuration Assistant,Step 8 of 12: Recovery Configuration interface pops up, asshown in Figure 71. Uncheck Specify Flash Recovery Area.

FIGURE 71 DATABASE CONFIGURATION ASSISTANT, STEP 8 OF 12:RECOVERY CONFIGURATION INTERFACE

12.Click Next and the Database Configuration Assistant, Step9 of 12: Database Content interface pops up, as shown inFigure 72. On the Sample Schemas tab, uncheck SampleSchemas.



FIGURE 72 DATABASE CONFIGURATION ASSISTANT, STEP 9 OF 12:DATABASE CONTENT INTERFACE

13.Click Next and the Database Configuration Assistant, Step10 of 12: Initialization Parameters interface pops up, asshown in Figure 73. On the Memory tab, keep the defaultsettings.

If the memory is 2 G, enter 40 in the Percentage column.



FIGURE 73 DATABASE CONFIGURATION ASSISTANT, STEP 10 OF 12:INITIALIZATION PARAMETERS

� Keep the default value for Typical - Allocate memoryas a percentage of the total physical memory. Or-acle database can automatically allocate to optimize thedatabase according to the hardware configurations of themachine.



� Select the Sizing tab and keep the default settings, asshown in Figure 74.

FIGURE 74 DATABASE CONFIGURATION ASSISTANT, STEP 10 OF 12INITIALIZATION PARAMETERS INTERFACE — SIZING TAB

� Select the Character Sets tab, as shown in Figure 75 Se-lect Choose from the list of character sets. Make surethat Database Character Set is ZHS16GBK and NationalCharacter Set is AL16UTF16.

FIGURE 75 DATABASE CONFIGURATION ASSISTANT, STEP 10 OF 12INITIALIZATION PARAMETERS INTERFACE — CHARACTER SETS TAB



Note:

It is recommended to select American in Default Lan-guage and select United States in Default Data Formatduring the installation.

Click and the All Initializa-tion Parameters interface pops up, as shown in Figure

76. Click to display all initializa-tion parameters. Modify value of NLS_DATE_FORMAT to‘YYYY-MM-DD HH24:MI:SS’, enter √ in Override column,and set the Value of optimizer_mode as rule.

FIGURE 76 ALL INITIALIZATION PARAMETERS INTERFACE

Note:

When setting value of NLS_DATE_FORMAT to ‘YYYY-MM-DD HH24:MI:SS’, do not omit the single quotes.

After the modification, click and the system returnsto the interface shown in Figure 76.

� Select the Connection Mode tab and keep the default set-tings, as shown in Figure 77.



FIGURE 77 DATABASE CONFIGURATION ASSISTANT, STEP 10 OF 12INITIALIZATION PARAMETERS INTERFACE — CONNECTION MODETAB

14.Click Next and the Database Configuration Assistant, Step11 of 12: Database Storage interface pops up, as shown inFigure 78. Click Storage > Controlfile on the left topologytree. On the Option tab, set Maximum Datafiles to 254,Maximum Redo Log Files to 32, Maximum Log Membersto 2, and Redo Log Groups to 200M.

FIGURE 78 DATABASE CONFIGURATION ASSISTANT, STEP 11 OF 12:DATABASE STORAGE INTERFACE

15.Click Next and the Database Configuration Assistant, Step12 of 12: Creation Options interface pops up, as shown inFigure 79. Keep the default values.



FIGURE 79 DATABASE CONFIGURATION ASSISTANT, STEP 11 OF 12:CREATION OPTIONS INTERFACE

16.Click Finish and the Confirmation interface pops up, asshown in Figure 80. Make sure that all parameters are correctand then click OK.

FIGURE 80 CONFIRMATION INTERFACE

17. The Database Configuration Assistant interface pops up, asshown in Figure 81. The system starts to copy database files,create and start Oracle instances, and create the database.



FIGURE 81 DATABASE CONFIGURATION ASSISTANT CREATIONINTERFACE

18.After the creation completes, the information is displayed onDatabase Configuration Assistant interface, as shown inFigure 82. At present, the database instance name are all zx-omc before delivery.

FIGURE 82 DATABASE CONFIGURATION ASSISTANT INFORMATIONINTERFACE

19.Click Exit and the installation completes.

END OF STEPS



Checks after Oracle 10g DatabaseInstallation

After Oracle 10g database installation completes, check the fol-lowing items to make sure that it runs normally.

Checking whether Oracle Database can beConnected/Started/Shut Successfully

Steps 1. Start the command line as the oracle user and executethe following command. If the Oracle service can be con-nected/started/shut normally, the check is successful.

FIGURE 83 CONNECTING ORACLE SERVICE

2. After one minute, enter the following commands:

$sqlplus sys/oracle@womc as sysdba

SQL>shutdown immediate

SQL>startup



FIGURE 84 STARTING UP/SHUTTING ORACLE SERVICE

END OF STEPS

Checking Whether Oracle Listener can beStarted/Stopped Successfully

Steps 1. Log in as the oracle user and execute the following checks:

2. $lsnrctl stop

The instance to stop the listener is as shown in Figure 85.



FIGURE 85 STOPPING LISTENER

3. $lsnrctl start

The instance to start the listener is as shown in Figure 86.

FIGURE 86 STARTING LISTENER



END OF STEPS

Viewing Character Set of Database

Steps 1. View the character sets of the database Server

Log in the database as the sys user and query the charactersets at the database Server with the sql sentence, as shownin Figure 87.

FIGURE 87 QUERYING CHARACTER SET AT DATABASE SERVER

2. Query the character set at the database Client with the com-mand as shown in Figure 88.



FIGURE 88 QUERYING CHARACTER SET AT DATABASE CLIENT

3. Check the data format with the command as shown in Figure89.

FIGURE 89 CHECKING DATA FORMAT

If the data format is error, recover with the following command:

$ sqlplus /nolog

SQL>connect sys/PWD@SID as dba #Log in Oracle as DBAuser#

SQL>ALTER SYSTEM SET nls_data_format='YYYY-MM-DD HH24:MI:SS' SCOP=SPFILE

SQL>shutdown#close the database#



SQL>startup#Restart the database#

SQL>exit

END OF STEPS

Configuring Auto Startup/Closeup of Oracle

Steps 1. Create the /etc/init.d/dbora file as the root user and set theexecutable rights with the following command:

#vi /etc/init.d/dbora

Add the following sentences:

#!/bin/bash

ORA_HOME=/oracleapp/oracle/product/10.2.0

ORA_OWNER=oracle

if [ ! -d $ORA_HOME/bin ]; then

echo "ORACLE STARTUP:can not start"

exit

fi

case "$1" in

start)

su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start"

su - $ORA_OWNER -c "$ORA_HOME/bin/sqlplus /nolog <<EOF

connect sys/oracle as sysdba;

startup;

exit;

EOF"

;;

stop)

su - $ORA_OWNER -c "$ORA_HOME/bin/sqlplus /nolog <<EOF

connect sys/oracle as sysdba;

shutdown immediate;

exit;

EOF"

su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl stop"

;;

esac

# chown root /etc/init.d/dbora

# chgrp root /etc/init.d/dbora

# chmod u+x /etc/init.d/dbora



2. Create the connection of two characters as the root user.

# ln -s /etc/init.d/dbora /etc/rc0.d/K10dbora

# ln -s /etc/init.d/dbora /etc/rc6.d/K10dbora

# ln -s /etc/init.d/dbora /etc/rc5.d/S99dbora

3. Modify the /etc/oratab file as the oracle user.

$vi /etc/oratab

Change womc:/oracleapp/oracle/product/10.2.0:N to womc:/ora-cleapp/oracle/product/10.2.0:Y.

4. Verify whether the auto startup takes effect as the root user.# cd /etc/init.d

# ./dbora start

Starting /oracleapp/oracle/product/10.2.0/bin/tnslsnr: please wait

Services Summary

Service “PLSExtProc” has 1 instance(s)

Instance “PLSExtProc”， status UNKNOWN, has 1 handler(s) for this service

The command completed successfully

SQL>ORACLE instance started

Database mounted

Database opened

SQL> Disconnected from Oracle Database 10g Enterprise EditionRelease 10.2.0.1.0

Production With the Partitioning, OLAP and Data Mining options

# ./dbora stop

SQL> Database closed

Database dismounted

ORACLE instance shut down

LSNRCTL for Linux. Version 10.2.0.1.0 - Production on 31-MAR-2008 15:37:43

The command completed successfully

END OF STEPS





C h a p t e r 4

Installing NM ServerSoftware

Table of ContentsOverview..........................................................................79Installing OMMRB NM Server Software..................................80Installing OMMB Server Side Software................................ 107

OverviewIn V3.09.30, OMM is separated into OMMR and OMMB. OMM-RBand OMMB are installed separately.

OMM NM application software consists of the OMM Client softwareand OMM Server software.

The installation flow of the OMM NM Server application softwareunder the Linux int is as below:

1. Preparations

i. Set the environment variables for the root user.

ii. Copy and uncompress.

iii. View and modify the rights.

iv. Check whether the Oracle database and listener have beenstarted.

2. Steps to install OMM-RB

3. Checks after the installation

i. Check the installation files.

ii. Check the etc/hosts file.

iii. Start the NM Server.

iv. Close the NM Server.

4. Steps to install OMMB



Installing OMMRB NMServer SoftwareThe installation of NM Server on Linux operating system falls intothree steps:

1. Preparations

2. Installation


Preparations for OMM NM ServerSoftware Installation

Setting Environment Variables for root Users

Steps 1. Log in the Linux command terminal as the root user.

2. Enter the command of $ vi . /etc/profile.

3. Check the settings of the three environment variables, asshown in Figure 90.

� ORACLE_BASE

� ORACLE_SIDc

� ORACLE_HOME


Chapter 4 Installing NM Server Software

FIGURE 90 CHECKING SETTINGS OF ENVIRONMENT VARIABLES

4. After the environment variables are modified, restart the SBCXand check whether the modification takes effect with the fol-lowing commands:

$su – root

$echo $ORACLE_HOME

$echo $ORACLE_BASE

$echo $ORACLE_SID

END OF STEPS

Copying and Decompressing

Steps 1. Send the version file packet of the SBCX applications,zxwomc.zip, to the temp installation directory (/home/in-stalltmp) through FTP. The installation directory of the NMserver is /data1/zxwomc.

2. Log in the Linux operating system as the root user to run thefollowing command:

# unzip zxwomc.zip

END OF STEPS

Viewing and Modifying Rights

Steps 1. View whether the install-liunx.sh file is executable, as shownin Figure 91.



FIGURE 91 VIEWING RIGHTS

2. The install-linux.sh file shown in Figure 91 is executable. Ifthe file is not executable, modify the rights of the script byrunning the following command:

[root@sbcx zxwomc]# chmod 755 install-linux.sh

END OF STEPS

Checking Whether Oracle Database and Listeneris Enabled

Steps 1. Log in as the oracle user with the following command:

[zte@sbcx ~]$ su – oracle

Password:********

[oracle@sbcx ~]$ lsnrctl status

The result is displayed as follows:LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 31-OCT-2008 14:20:41

Copyright (c) 1991, 2005, Oracle. All rights reserved.Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Linux: Version 10.2.0.1.0 - ProductionStart Date 31-OCT-2008 10:28:21Uptime 0 days 3 hr. 52 min. 19 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Log File /home/data1/oracle/product/10.2.0/db_1/network/log/listener.logListening Endpoints Summary...(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sbcx)(PORT=1521)))Services Summary...Service "womc" has 1 instance(s).Instance "womc", status READY, has 1 handler(s) for this service...Service "womcXDB" has 1 instance(s).



Instance "womc", status READY, has 1 handler(s) for this service...Service "womc_XPT" has 1 instance(s).Instance "womc", status READY, has 1 handler(s) for this service...The command completed successfully

2. If the instances and the listener are not started, start as theoracle user with the following commands.

i. Start the listener

[zte@sbcx ~]$ su - oracle

Password:********

[oracle@sbcx ~]$ lsnrctl start

ii. Start the Oracle database

[oracle@sbcx ~]$ sqlplus /nologSQL*Plus: Release 10.2.0.1.0 - Production on Fri Oct 31 14:24:11 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

SQL> conn sys/oracle as sysdbaConnected.

SQL>startup

END OF STEPS

Steps to install OMMRB ServerSoftware






3. Open the target folder to view whether all software installationprograms exist, as shown in Figure 93.

FIGURE 93 CHECKING INSTALLATION FOLDER

4. Run the install-linux.sh file, as shown in Figure 94.



FIGURE 94 RUNNING INSTALL-LINUX.SH FILE

5. The Please Select language interface pops up, as shown inFigure 95. Select the language according to the installationenvironment. Select English from the drop-down menu.

FIGURE 95 PLEASE SELECT LANGUAGE INTERFACE

The language selected on this interface is the language dis-played during the NM software installation.

6. Click NEXT and the You should accept the agreement tocontinue installing interface pops up, as shown in Figure 96.Read the ZTE Corporation Agreement and then click Accept.



FIGURE 96 YOU SHOULD ACCEPT THE AGREEMENT TO CONTINUEINSTALLING INTERFACE

7. Click NEXT and the Please Select Product interface popsup, as shown in Figure 97. Select English Edition from thedrop-down menu.

FIGURE 97 PLEASE SELECT PRODUCT INTERFACE

The language selected on this interface is the language dis-played when the NM software is running after the installation.



Note:

The software version number shown in the figure above is forinstance only. It may be different from the actual version re-leased.

8. Click NEXT and the Please Select Product Module interfacepops up, as shown in Figure 98.

FIGURE 98 PLEASE SELECT PRODUCT MODULE INTERFACE

9. Click NEXT and the Please Set Installation Path interfacepops up, as shown in Figure 99.



FIGURE 99 PLEASE SET INSTALLATION PATH INTERFACE

Click to select the path to install the application program.Alternatively, select the recommended installation directory:/home/ZXWR-RB/WOMC/.

Note:

You can either set setup path manually or select one of the ex-isting paths in the local computer. The system supports pathsof not more than eighty characters, English letters and num-bers only. It is not recommended to use special characters.

The disk space required for the applications installation andthe remaining disk space of the selected installation directoryare displayed on the current interface. Make sure that theremaining disk space is larger than the required disk space.

10.Click NEXT and the Set of Application Database interfacepops up, as shown in Figure 100.



FIGURE 100 SET OF APPLICATION DATABASE INTERFACE

Note:

If you select Initial data in Figure 98 and the correspond-ing database SID has existed in the database, the system willoverwrite the NM data that has the same SID during the in-stallation. If there is no database that has the same SID in thedatabase, you cannot continue the installation.

� Select ORACLE from the drop-down menu of Pleasechoose Database Type.

� If the database and NM server are on the same machine,select Database and Server on the Same Machine.Otherwise, do not select it.

� IP address: The address of Oracle Server.

If Database and Server on the Same Machine is se-lected, the IP address of this machine will appear in thedrop-down menu of IP Address.

If Database and Server on the Same Machine is notselected, input the IP address manually.

� SID: The database instance ID that is set during Oracleinstallation.

� System user password: The password of System user inOracle.



Note:

On the Please Select Product Module interface, if you haveselected to install the database, the UMS server configurationinterface is as shown in Figure 100. If not, it indicates that thedatabase has existed and there is no need to install it again.In this case, you can only set the IP address and the SID onthe interface, which respectively correspond to the IP addressand the SID of the database.

11.Click NEXT and the Drop Initial Data interface pops up, asshown in Figure 101.

FIGURE 101 DROP INITIAL DATA INTERFACE

Tick Drop related data of the product in the database.

12.Click NEXT and the Drop Initial Data process interface popsup, as shown in Figure 102.



FIGURE 102 DROP INITIAL DATA PROCESS INTERFACE

13.Click NEXT and Database Module Set interface pops up.

The database installation mode falls into five types:

� Big Module

This mode is applicable to a network size of 2000 to 4000cells. Therefore, 15 G disk space is required.

� Medium Module

This mode is applicable to a network size of 1000 to 2000cells. Therefore, 10 G disk space is required. The diskpartition requirements are the same as Big Module.

� Small Module

This mode is applicable to a network size of 1000 or lessthan 1000 cells. Therefore, 7 G disk space is required. Thedisk partition requirements are the same as Big Module.

� Test Module

In Test Module, disk partition requirements are the sameas Big Module.

� Self Defined Module

In Self Defined Module, you can set database setup pathsand the disk size manually.

The installation methods of Big Module, Medium Module, SmallModule, and Test Module are almost the same. They are differ-ent only in terms of required space. The following will take theinstallation method of Test Module and Self Defined Module asexamples.

i. Small Module

Select Small Module from the drop-down menu of Data-base Module Set, as shown in Figure 103.



FIGURE 103 DATABASE MODULE SET INTERFACE — SMALL MODULE

Click NEXT and the Database Parameter Set interfacepops up. Select Fixed Path or Disk Partition.

– Fixed Path

Select Fixed Path from the drop-down menu of Data-base Parameter Set and select the number from thedrop-down menu of Path Number, as shown in Figure104.

FIGURE 104 DATABASE PARAMETER SET DIALOG BOX — FIXEDPATH

Click to select the path.

Make sure that the remaining space where the selectedpath exists is larger than the space required for thedatabase installation.



Note:

The remaining space is the available disk space minusthe required space. If the remaining space is a negativevalue, it indicates that the space is not enough and youmust release the disk space or select another path.

– Disk Partition

Select Disk Partition from the drop-down menu ofDatabase Parameter Set and select the number fromthe drop-down menu of Partition Number, as shownin Figure 105.

FIGURE 105 DATABASE PARAMETER SET DIALOG BOX — DISKPARTITION

ii. Self Defined Module

Select Self Defined Module from the drop-down menu ofDatabase Module Set, as shown in Figure 106.

Note:

Small Module is recommended.



FIGURE 106 DATABASE MODULE SET INTERFACE — SELF-DEFINEDMODULE

ClickNEXT and Set Database File Path interface pops up,as shown in Figure 107, where the path of the database filecan be input. Input the installation path as required.

FIGURE 107 SET DATABASE FILE PATH INTERFACE

– Data installation path

You can set the path where the configuration, alarm,measurement task, and test management tablespacefiles locate. The default path is the path where SIDlocates. If the server and the client are on the samemachine, you can set this path as inexistent path. Thesystem will create the path automatically. Otherwise,you should fill in one existing path



– Path number of PM (Performance Management) parti-tion table space

Select number i (i=1-6) in the drop-down list of PM sec-tion tablespace path, indicates to create i set of datafile of PM section tablespace (including original data ta-blespace, middle data tablespace and corresponding in-dex table space). These data files are saved in the pathdisplayed from the first to the ith edit box respectively.If more than one tablespace paths are selected, and thesame path is set up in edit box, the data file of PM sec-tion tablespace with the same number of paths can becreated under the same path.

Setting path number can create big tablespace, dis-tribute files under different path, and improve the effi-ciency.

– Performance database path

After selecting the path number of PM, fill in path in thefollowing TEXT box. If the server and the client are onthe same machine, you can set this path as inexistentpath. The system will create the path automatically.Otherwise, you should fill in one existing path.

Click Next and Set Size of Database interface popsup, as shown in Figure 108. You can input values ac-cording to the actual cases.

FIGURE 108 SET SIZE OF DATABASE INTERFACE

Note:

When setting the database table space, it is recom-mended to use the default value.

14.Click NEXT and Please View Install Information interfacepops up, as shown in Figure 109.



FIGURE 109 PLEASE VIEW INSTALL INFORMATION INTERFACE

15.Click NEXT and the Install Application Database Serverinterface pops up, as shown in Figure 110.

FIGURE 110 INSTALL APPLICATION DATABASE SERVER INTERFACE

16.When the installation is completed, click Next and the In-stall the application program interface pops up, as shownin Figure 111.



FIGURE 111 INSTALL THE APPLICATION PROGRAM INTERFACE

17.When the application program installation is completed, clickNext and the Node B FTP Configure interface pops up, asshown in Figure 112.

FIGURE 112 NODE B FTP CONFIGURE INTERFACE



Note:

If the OMMR NM is used and the OMMB NM is not used, thisstep can be skipped. The ipoaV3Node B-ftpIP item in thisversion means that IP address of 3G Node B IPOA supportsmultiple IP settings. When setting IP address, separate severalIP addresses with semicolons. For example, 10.61.56.145;10.61.56.145. At most five IP addresses can be set.

18.Click NEXT and the RNC FTP SERVER IP Configure inter-face pops up, as shown in Figure 113. Enter the FTP server IPaddress and click Next. The Minos FTP SERVER IP Config-ure interface pops up, as shown in Figure 114. Enter the IPaddress of the FTP server.

FIGURE 113 RNC FTP SERVER IP CONFIGURE INTERFACE

Note:

The IP address in this step should be in the same networksegment with RNC foreground and can be accessed by RNC.



FIGURE 114 MINOS FTP SERVER IP CONFIGURE INTERFACE

19.Click NEXT and the Master Clock Sync Server Configureinterface pops up, as shown in Figure 115. Enter the IP addressof the master clock Server.

FIGURE 115 MASTER CLOCK SYNC SERVER CONFIGURE INTERFACE

This step is to synchronize the time of the Server and the Client.

When the Client is installed independently or the Server andthe Client are installed at the same time, this interface popsup. When only the Server is installed, this interface does notpop up.

Set the IP address to the IP address of the network where theServer is located.

20.Click NEXT and the SBCX Board Configure interface pops up.



Select the check box according to the SBCX configurations.

� When there is only one SBCX on the rack, select BackupMode none for Backup Mode and keep null for BoardSetup, as shown in Figure 116.

FIGURE 116 SBCX BOARD CONFIGURE INTERFACE — BACKUPMODE NONE

� When there are two SBCX on the rack in the M/S modeand the NMS is installed on the left board, select BackupMode Master-Slave for Backup Mode and Left Boardfor Board Setup, as shown in Figure 117.

FIGURE 117 SBCX BOARD CONFIGURE INTERFACE - BACKUP MODEMASTER-SLAVE (LEFT)

� When there are two SBCX on the rack in the M/S modeand the NMS is installed on the right board, select Backup



Mode Master-Slave for Backup Mode and Right Boardfor Board Setup, as shown in Figure 118.

FIGURE 118 SBCX BOARD CONFIGURE INTERFACE - BACKUP MODEMASTER-SLAVE (RIGHT)

21.Click NEXT and make_profile interface pops up, an shown inFigure 119.

FIGURE 119 MAKE_PROFILE

Note:

Set is_split and is_backup according to the on-site condi-tions.



22.Click NEXT and Set JVM Memory interface pops up, as shownin Figure 120.

FIGURE 120 SET JVM MEMORY INTERFACE

The default JVM memory is 512 M. You can modify this valueas required, The recommended value is 512M.

Note:

In the case of Small Mode, this step is not required.

23.Click NEXT and the Config Environment interface pops up,as shown in Figure 121.



FIGURE 121 CONFIG ENVIRONMENT INTERFACE

24.Click NEXT and Setup Finished interface pops up, as shownin Figure 122.

FIGURE 122 SETUP FINISHED INTERFACE

Select VIEW README and click Finish to view READ ME mes-sages.

25.Click NEXT and the VIEW README interface pops up, asshown in Figure 123.



FIGURE 123 VIEW README INTERFACE

Click Finish and the installation completes.

END OF STEPS

Checks after OMMRB NM ServerSoftware Installation

After OMMRB NM Server software installation completes, check thefollowing items to make sure that the software can run normally.

Checking Installation Files

Context After the installation completes, check whether the sub-directoriesexist under the following installation directories:

Steps 1. docs directory: Description document, details of directorystructure and FAQ document

2. jdk-windows directory: Java running environment underLinux operating system

3. ums-svr directory: Server application program

4. ums-clnt directory: Client application program

END OF STEPS

Checking the /etc/hosts File

Steps 1. Before starting the NM Server, check /etc/hosts by runningthis command: $more /tec/hosts.



2. Check whether the first line is 127.0.0.1. If so, add the IPaddress of the external network.

3. Start the NMS normally by running the following commands:

Where, 10.61.100.202 is the IP address of the external net-work and sbcx is the hostname.

END OF STEPS

Starting NM Server

Context This procedure describes how to start the NM Server through com-mand.

Steps 1. After installing the NMS successfully, enter the installation di-rectory of /ums-svr/ on the terminal command window, asshown in Figure 124.

FIGURE 124 ENTERING INSTALLATION DIRECTORY

2. Enter the bin file under the installation directory, as shown inFigure 125.

FIGURE 125 ENTERING BIN FILE



3. Give the execution authority by running the following com-mand:

chmod 775 run-linux.sh

chmod +x run-linux.sh

4. Run the run-linux.sh file, as shown in Figure 126.

FIGURE 126 RUNNING RUN-LINUX.SH FILE

END OF STEPS

Checking Running State

Context

Note:

Make sure that the console is running before checking the runningstate. If the console is not started, enter the ums-svr/bin direc-tory and run the console-linux.sh file.

Steps 1. Enter ums-svr/bin/consolemml to run the status-linux.shfile, as shown in Figure 127. The system feeds back the currentprocess.

FIGURE 127 CHECKING RUNNING STATE

END OF STEPS



Shutting Down NM Server

Context This procedure describes how to shut down the NM Server throughcommand.

Steps 1. Enter the bin file under the installation directory on the ter-minal command window and run the close-console-linux.shfile, as shown in Figure 128.

FIGURE 128 SHUTTING DOWN SERVER

END OF STEPS

Installing OMMB Server SideSoftware

Prerequisites 1. OMMRB server is running properly.

2. Create a new oracle database instance.

3. Copy and decompress.

i. Use FTP tool to transport version file package zxwomcb.zipfor SBCX application server to the temporary installationdirectory (The temp directory is: /home/installtmp). Theserver installation directory in this chapter is /data1/zx-womcb.

ii. Log in the Linux operation system as root user and run thefollowing command.

Run the unzip command under the directory /home/in-stalltmp.

# unzip zxwomcb.zip

4. View the modification authority

i. Check whether you have execution authority for the fileinstall-liunx.sh

For example, if the directory path generated after decom-press is /home/data1/zxwomcb, you can run the followingcommand to check the file modification authority.



[root@sbcx zxwomcb]# ls -l

ii. If you do not have execution authority, you can run thecommand:

[root@sbcx zxwomcb]# chmod 755 install-linux.sh

5. Check whether the Oracle database and the interception func-tion.

i. Log in with the Oracle user name.

[zte@sbcx ~]$ su – oracle

Password:********

[oracle@sbcx ~]$ lsnrctl status

The result is as follows:LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 23-JUL-2010 17:47:53Copyright (c) 1991, 2007, Oracle. All rights reserved.Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))STATUS of the LISTENER ------------------------ Alias LISTENER VersionTNSLSNR for Linux: Version 10.2.0.4.0 - Production Start Date23-JUL-2010 15:48:58 Uptime0 days 1 hr. 58 min. 55 sec Trace Level off SecurityON: Local OS Authentication SNMPOFF Listener Parameter File/home/data1/oracle/product/10.2.0/network/admin/listener.oraListener Log File/home/data1/oracle/product/10.2.0/db_1/network/log/listener.logListening Endpoints Summary...(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sbcx)(PORT=1521)))Services Summary... Service "womc" has 1 instance(s).Instance "womc", status READY, has 1 handler(s) for this service...Service "womcXDB" has 1 instance(s).Instance "womc", status READY, has 1 handler(s) for this service...Service "womc_XPT" has 1 instance(s).Instance "womc", status READY, has 1 handler(s) for this service...Service "womcb" has 1 instance(s).Instance "womcb", status READY, has 1 handler(s) for this service...Service "womcbXDB" has 1 instance(s).Instance "womcb", status READY, has 1 handler(s) for this service...Service "womcb_XPT" has 1 instance(s).Instance "womcb", status READY, has 1 handler(s) for this service...The command completed successfully

If the above screen output appears, the database instanceand the interception are initiated.

Caution:

V3.09.30 has two database instances, therefore you cansee two instances under interception.

ii. If the instance and interception are not started, run thefollowing commands:

a) Start Interception.

[zte@sbcx ~]$ su - oracle

Password:********

[oracle@sbcx ~]$ lsnrctl start

b) Start Oracle



[oracle@sbcx ~]$ sqlplus /nologSQL*Plus: Release 10.2.0.1.0 - Production on Fri Oct 31 14:24:11 2008Copyright (c) 1982, 2005, Oracle. All rights reserved.

SQL> conn sys/oracle as sysdbaConnected.

SQL>startup

Steps 1. Right-click on the Linux desktop,


3. Open the target file folder, check the installation software, asshown in Figure 129.

FIGURE 129 VIEW INSTALLATION FOLDER

4. Run install-linux.sh, as shown in Figure 130.

FIGURE 130 RUN INSTALL-LINUX.SH

5. In Please Select Language window, select English in thedrop-down list, as shown in Figure 131.



FIGURE 131 WELCOME

The language selected is also applied throughout the installa-tion process.

6. Click NEXT. In the window, view the ZTE corporation agree-ment, select Accept to proceed, as shown in Figure 132.

FIGURE 132 VIEW THE ZTE CORPORATION AGREEMENT

7. ClickNEXT. In Please Select Productwindow, select EnglishEdition, as shown in Figure 133.



FIGURE 133 SELECT PRODUCT

The language is applied when the software started after instal-lation.

Note:

The version shown in the figure is an example. It may bedifferent with the current version.

8. Click NEXT to enter the Please Select Product Module win-dow, as shown inFigure 134.

FIGURE 134 SELECT PRODUCT MODULE

9. Click NEXT to enter the Please set the installation pathwindow, as shown in Figure 135.



FIGURE 135 SET THE INSTALLATION PATH

Click to select the installation path. The recommendedpath is /zxomcb.

Note:

You can self-define the installation path, or select from those inthe system. The system supports the path that has not morethan 80 characters. Only English letters and the numeral digitsare accepted. Do not include special characters in the path.

The interface shows the disk space required for the software in-stallation and the available space of the installation disk. Makesure the available disk space is larger than that required by thesoftware installation.

10.Click Next. Set of Application Database window shows up,as shown in Figure 136.



FIGURE 136 SET OF APPLICATION DATABASE

Note:

If the same instance ID (SID) exists in the database, the NMdata with the SID will be overwritten during the installation.If there is not a duplicate SID in the database, the installationcannot proceed.

� In Please choose database type drop-down list, selectORACLE.

� If the database and the NM server are installed on the sameserver, select Database and Server on the Same Ma-chine.

� IP address: Oracle server address.

If you choose Database and Server on the Same Ma-chine, the IP Address drop down list will give the IP ad-dress of this machine.

If this option is not selected, you need to input the IP ad-dress manually.

� SID is the ID set at the installation of Oracle.

� System user password is under the Oracle environment.

Note:

If you have chosen to install database in the previous step, theserver configuration interface is as shown in Figure 136; if youhave not chosen to install database, which means the databaseis already there, you can only set the IP address and the SID,which are corresponding to both in the database.



11.Click Next. Drop initial data window shows up, as shown inFigure 137.

FIGURE 137 DROP INITIAL DATA

Select Drop related data of the product in the database.

12.Click Next. Drop initial data window shows up with the dropstatus, as shown in Figure 138.

FIGURE 138 DROP INITIAL DATA

13.After data drop, click Next. Database Module Set windowshows up.

The database has 5 installation modes.

� Big module

Big module is applied in a cell with 2000 to 4000 users. 15G disk space is needed.



� Medium module

Medium module is applied in a cell with 1000 to 2000 users.10 G disk space is needed. The disk partition is the samewith big module.

� Small module

Small module is applied in a cell with 1000 or less than1000 users. 7 G disk space is needed. The disk partition isthe same with big module.

� Test module

Test module is added for test. The disk partition is the samewith big module.

� Self-Defined module

In this module, you need to set the database installationpath and the space for each table.

The installation method for each module is similar, so the fol-lowing contents take the small module and self-defined moduleas examples to describe the installation procedures.

i. Small module

In Database Module Set, select Small Module, as shownin Figure 139.

FIGURE 139 SMALL MODULE

Click NEXT. Database Parameter Set window shows up.You can choose to install into a fixed path or disk partition.

– Install with fixed path

In Database Parameter Set drop-down list, selectFixed Path. In Path Number drop-down list, selectthe number as shown in Figure 140.



FIGURE 140 FIXED PATH

Click to select path.

Make sure the rest space with the selected path mustbe larger than the space required for the database in-stallation.

Caution:

If the rest space value is negative, free the disk spaceor choose another path.

– Install with disk partition

In Database Parameter Set drop-down list, selectDisk Partition. In Partition Number drop-down list,select the number as shown in Figure 141.



FIGURE 141 DISK PARTITION

ii. Self-Defined module

In Database Module Set, select Self Defined Module,as shown in the figure.

FIGURE 142 SELF DEFINED MODULE

Click NEXT. Set Database File Path window shows up.You can set the file path for the database file, as shown inFigure 143.



FIGURE 143 SET DATABASE FILE PATH

– The data installation path

Set the paths for files of configuration, alarm, perfor-mance and diagnosis and test. The default path is thesame as that of SID. If the NM server and the databaseserver are the same machine, you can set a path notexisted and the system will create this path.

– Division number of Performance Management (PM)

Select the number i in the drop-down list (i=1-6), whichmeans to create i set of files for PM division table spaceincluding source data table space, middle data tablespace and the corresponding index table space.If youselect multiple table space paths and set the same pathin the edit area, several data files for the PM partitiontable space will be created under this path. The numberof files is the same as that of the paths.

Path number setting enables you to create bigger tablespace and makes files distribute under different pathsto improve efficiency.

– Performance database path

After you have chosen the path number of performancedatabase, you can fill in the following TEXT field with apath. If the NM server and database server are installedon one machine, the path can be the one that does notexist. The system will create the path. Otherwise youmust fill in an existed path.

Click Next. Set Size of Database window shows up,as shown in Figure 144.



FIGURE 144 SET SIZE OF DATABASE

Caution:

When setting the size of the database table space, youare recommended to adopt the default value.

14.Click NEXT. Please View Install Information window showsup, as shown in Figure 145.

FIGURE 145 VIEW INSTALL INFORMATION

15.Click NEXT. Install Application Database Server windowshows up, as shown in Figure 146.



FIGURE 146 INSTALL APPLICATION DATABASE SERVER

16.Wait until the database server installation completes. ClickNEXT. Install the application program window shows up,as shown in the figure.

FIGURE 147 INSTALL THE APPLICATION PROGRAM

17.Wait until the program installation completes. Click NEXT.Node B FTP Configure window shows up, as shown in Figure148.



FIGURE 148 NODE B FTP CONFIGURE

Note:

The IP address is in the network connecting OMMB server toNode B.

18.Click NEXT. Master Clock Sync Server Configure windowshows up, as shown in Figure 149. Fill in the IP address of themaster clock server.

FIGURE 149 MASTER CLOCK SYNC SERVER CONFIGURE

The purpose of IP address setting is to synchronize the timeon server and client side.

The interface appears when you install the client side only orinstall both the server side and the client side.



The IP address is in the server network.

19.Click NEXT. make_profile window shows up.

FIGURE 150 MAKE PROFILE

Note:

Set is_split and is_backup, according to the on-site condi-tions.

For V3.09, the two options are both Yes.

20.Click NEXT. Pease choose functions window shows up withAdd the Program Group or Add the shortcut Link, asshown in Figure 151.

FIGURE 151



21.ClickNEXT. Config Environment window shows up, as shownin Figure 152.

FIGURE 152 CONFIGURE ENVIRONMENT

22.Click Next. Setup Finished window shows up, as shown inFigure 153.

FIGURE 153 SETUP FINISHED

Select VIEW README. Click Finish to view readme informa-tion.

23.Click Finish. VIEW README window shows up, as shown inFigure 154.



FIGURE 154 VIEW README

Click Finish to complete the installation.

END OF STEPS


C h a p t e r 5

Installing NM ClientSoftware

Table of ContentsOverview........................................................................ 125Installing OMMRB Client Software ...................................... 125Installing OMMB Client Side Software ................................. 134

OverviewIn V3.09.30, OMM is separated into OMMR and OMMB. OMM-RBand OMMB are installed separately.

OMM NM applications include Client and Server. Usually, OMMClient is installed under Windows. This chapter introduces the in-stallation of OMM NM Client applications under Windows 2003.

NM client can run independently of the NM Server and can be in-stalled on multiple PCs.

Installing OMMRB ClientSoftwareThe installation of NM Client under Windows 2003 operating sys-tem falls into three steps:

1. Preparations

2. Steps


Preparations

Before installing OMMRB NM Client applications, check the follow-ing items and make preparations.



1. Make sure that the operating system is installed properly andis running normally.

2. Check whether the hardware configurations and performanceof the computer fulfill the requirements.

3. Obtain the installation disk for OMM NM application software.

Note:

During the installation, make sure that all other programs areclosed and the user to install the software belongs to the admin-istrator group who have right to write the installation disk and thesystem disk.

Steps to Install OMMRB NM ClientSoftware

Steps 1. Open the NM installation program directory and double-clickthe $\zxwomc\install.bat file. The system starts to installthe Client software.

2. The Please Select Language interface pops up, as shown inFigure 155. Select English.

FIGURE 155 PLEASE SELECT LANGUAGE INTERFACE

The language selected on this interface is the language dis-played during the NM software installation.

3. Click NEXT and the You should accept the agreement tocontinue installing interface pops up, as shown in Figure156. View ZTE Corporation Agreement and then click Accept.


Chapter 5 Installing NM Client Software

FIGURE 156 YOU SHOULD ACCEPT THE AGREEMENT TO CONTINUEINSTALLING INTERFACE

4. Click NEXT and the Please Select Product interface pops up,as shown in Figure 157 Select English Edition.

FIGURE 157 PLEASE SELECT PRODUCT INTERFACE

Note:




5. Click NEXT and the Please Select Product Module interfacepops up, as shown in Figure 158. Select Client.

FIGURE 158 PLEASE SELECT PRODUCT MODULE INTERFACE

6. Click NEXT and the Please set installation path interface

pops up, as shown in Figure 159. Click to set the instal-lation path.

FIGURE 159 PLEASE SET INSTALLATION PATH INTERFACE

7. Click NEXT and the Please View Install Information inter-face pops up, as shown in Figure 160.



FIGURE 160 PLEASE VIEW INSTALL INFORMATION INTERFACE

Note:


8. Click NEXT and the Install the application program inter-face pops up, as shown in Figure 161.

FIGURE 161 INSTALL THE APPLICATION PROGRAM INTERFACE

9. Click NEXT and the Master Clock Sync Server Configureinterface pops up, as shown in Figure 162.



FIGURE 162 MASTER CLOCK SYNC SERVER CONFIGURE INTERFACE

Usually, the IP address of the master clock Server is the IPaddress of the NM Server and it is used to synchronize thetime of the Client.

10.Click NEXT and Set JVM Memory interface pops up, as shownin Figure 163.

FIGURE 163 SET JVM MEMORY INTERFACE

The default JVM memory is 256 M. You can modify this valueas required, The recommended value is 512M.

11.Click NEXT and the Please Choose Functions interface popsup, as shown in Figure 164. Select Add the Program Groupand/or Add the ShortCut Link as required.



FIGURE 164 PLEASE CHOOSE FUNCTIONS INTERFACE

� Add the Program Group

Choose Start > Programs and add the ZXWR-OMCRBprogram group.

� Add the ShortCut Link

Add the startup shortcut for the NM Client on the desktop.

12.Click NEXT and the Config Environment interface pops up,as shown in Figure 165.

FIGURE 165 CONFIG ENVIRONMENT INTERFACE

13.Click NEXT and the Setup Finished interface pops up, asshown in Figure 166.




Select VIEW README and click Finish to view READ ME mes-sages.

14.Click NEXT and VIEW README interface pops up, as shownin Figure 167.

FIGURE 167 VIEW README INTERFACE

Click Finish and the installation completes.

END OF STEPS



Checks after Installation

After the OMMRB NM Client installation completes, check the fol-lowing items to make sure that the installation is correct.

Checking Installation Files

Context After the installation completes, check whether the sub-directoriesexist in the following installation directories:

Steps 1. docs directory: Description document, details of directorystructure and FAQ document

2. jdk-windows directory: Java running environment underWindows 2003 operating system

3. ums-clnt directory: Client application program

END OF STEPS

Running OMMRB NM Client

Context There are two methods to start the NM Client:

Steps 1. From the menu

After the NMS installation completes, the system automaticallyadds the system Client startup menu on Start > Programs.Select this menu to start the NM Client program, as shown inFigure 168.

FIGURE 168 NM CLIENT STARTUP MENU

2. With the shortcut icon

If the user has selected Add the Shortcut Link, the systemautomatically adds the shortcut icon of running Client on thedesktop, as shown in Figure 169.

FIGURE 169 RUN CLIENT SHORTCUT ICON

Double-click the shortcut icon to run the NM Client

END OF STEPS



Exiting OMMRB NM Client

Context There are two methods to exit from the NM Client.

Steps 1. Choose System > Exit on the NM startup interface.

2. Click .

END OF STEPS

Installing OMMB Client SideSoftware

Prerequisites Do the following preparations before installing OMMB client sidesoftware.

1. The operating system has been installed and is running prop-erly.

2. The hardware configuration of the workstation meets the in-stallation requirements of server software. And the worksta-tion has good performance.

3. The installation CD of the application software is prepared.

Caution:

Exit other programs before installation and make sure the personconducting the installation is a member of administrators group.

Steps 1. Open the installation program folder. Double-click the file$\zxwomcb\install.bat to start installation.

2. In Please Select Language window, select English in thedrop-down list, as shown in Figure 170.



FIGURE 170 SELECT LANGUAGE

The language selected is also applied throughout the installa-tion process.

3. Click NEXT. In the window, view the ZTE corporation agree-ment, select Accept to proceed, as shown in Figure 171.

FIGURE 171 ZTE CORPORATION AGREEMENT

4. ClickNEXT. In Please Select Productwindow, select EnglishEdition, as shown in Figure 172.



FIGURE 172 SELECT PRODUCT

The language selected is also applied when the softwarestarted after installation.

5. Click NEXT. Please Select Product Module window showsup, as shown in Figure 173.

FIGURE 173 SELECT PRODUCT MODULE

6. Choose the module and click NEXT. Please set installation

path window shows up. Click to select installation path,as shown in Figure 174.



FIGURE 174 SET INSTALLATION PATH

7. Click NEXT. Please View Installation Information windowshows up, as shown in Figure 175.

FIGURE 175 VIEW INSTALLATION INFORMATION

8. Click NEXT Install the application program window showsup, as shown in Figure 176.



FIGURE 176 INSTALL THE APPLICATION PROGRAM

9. Click NEXT. Master Clock Sync Server Configure windowshows up, as shown in Figure 177.

FIGURE 177 MASTER CLOCK SYNC SERVER CONFIGURATION

The IP address of the master clock server is the same as thatof the NM server. It synchronizes the client side time.

10.Click Next. Set JVM Memory window shows up, as shown inFigure 178.



FIGURE 178 SET JVM MEMORY

The NM client side JVM (Java virtual machine) memory is 256Mby default. You can modify the JVM value as needed. Therecommended value is 512M.

11.Click NEXT. Pease choose functions window shows up withAdd the Program Group or Add the shortcut Link, asshown in Figure 179.

FIGURE 179 CHOOSE FUNCTIONS

You can select Add the Program Group or Add the shortcutLink as needed.

� Add program group menu

In Start > Program, add ZXOMCB Program group.

� Add shortcut



Add shortcut access for the client side software.

12.ClickNEXT. Config Environment window shows up, as shownin Figure 180.

FIGURE 180 CONFIGURE ENVIRONMENT

13.Click Next. Setup Finished window shows up, as shown inFigure 181.


Select VIEW README. Click Finish to view readme informa-tion.

14.Click Finish. VIEW README window shows up, as shown inFigure 182.



FIGURE 182 VIEW README

Click Finish to complete the installation.

END OF STEPS

Postrequisite Installation check is necessary to ensure that the OMMB client soft-ware has been correctly installed.

1. Checking Installation Directories

Check whether the following subdirectories are available in theinstallation directory of the OMMB client software:

i. docs directory: description documents, directory structurespecification, and FAQ documents

ii. jdk-windows directory: Java running environment in Win-dows 2003 operating system

iii. ums-clnt directory: client program

2. Starting the OMMB Client.

There are several methods to start OMMB client:

i. Menu Start

After installation, the system will add a program group inStart > Program.

ii. Shortcut Access

If you choose to add a shortcut menu during installation,the system will add a shortcut icon on the desktop.



FIGURE 183 SHORTCUT ICON

Double-click the shortcut icon to start the OMMB client.

3. Shut down the Client

You can exit the OMMB client from the System menu or click.


C h a p t e r 6

Upgrading NM Serverand NM Client Software

Table of ContentsOverview........................................................................ 143Upgrading OMM NM Server and NM Client in Linux ............... 144Upgrading OMM Client in Windows ..................................... 151One-Click Upgrade of OMMRB NM Server and Client ............. 160

OverviewNM Server software and Client software can be upgraded sepa-rately or simultaneously.

This chapter mainly introduces the upgrade process of OMM NMServer software and Client software under the Linux operating sys-tem and that of the OMM NM Client software in the Windows 2003operating system.

The upgrade can be made by using graphical interfaces. Alterna-tively, you can also use one-click upgrade.

The upgrading procedures of OMMRB is the same as that of OMMB.The following chapters take the OMMRB server and Client upgrad-ing as examples.

Note:

Do not save the installation directory under a deep path. Other-wise, the upgrade will fail.

The installation directory should be three levels at most for theWindows operating system and five levels at most for the Linuxoperating system.

For example, if the software is saved under C:\softwar\ommsoft-ware\ZXWR-OMCRB\WOMC in the Windows operating system, the up-date fails.



Upgrading OMM NM Serverand NM Client in LinuxPreparations

Exit the Server and Client application programs before the update.Exit from the Client on the interface and exit from the Server withthe close-console-linux.sh command under the /ums-svr/bin.

Upgrading Steps in Linux

Steps 1. Log in as the root user.

2. The system automatically decompresses the jdk-linux.tar fileunder /update/container/jre/jre-linux

3. Grant the executable rights by running the following command:

chmod –R 755 jre-linux

4. Run the /update/container/run-linux.sh file. The Up-grade Software interface pops up, as shown in Figure 184.

FIGURE 184 UPGRADE SOFTWARE INTERFACE

5. Select English and click OK. The Welcome to use the up-grade program interface pops up, as shown in Figure 185.


Chapter 6 Upgrading NM Server and NM Client Software

FIGURE 185 WELCOME TO USE THE UPGRADE PROGRAM INTERFACE

6. Click Next and the System Path interface pops up, as shownin Figure 186.

FIGURE 186 SYSTEM PATH INTERFACE

Click Choose and select the NM software root directory of theversion to be upgraded. This root directory is the father direc-tory of ums-clnt and ums-svr.

7. Click Next and the upgrade mode interface pops up, as shownin Figure 187.



FIGURE 187 UPGRADE MODE INTERFACE

The system selects the software to be upgraded according tothe information of the upgrade software.

8. Click Next and the upgrading progress interface pops up, asshown in Figure 188.

FIGURE 188 UPGRADING PROGRESS INTERFACE

9. When the progress bar reaches its end, the Preview of up-grade information interface pops up, as shown in Figure 189.



FIGURE 189 PREVIEW OF UPGRADE INFORMATION INTERFACE

The interface displays the current NM system version and theversion to be upgraded. Please check the user information.If there is any discrepancy, click cancel to exit the currentupgrading program.

Note:


10.Confirm the version information and then click Next. The sys-tem starts to create the Client upgrade packages, as shown inFigure 190.

FIGURE 190 CREATING CLIENT UPGRADE PACKAGE



11.After the upgrade completes, the database settings interfacepops up, as shown in Figure 191.

FIGURE 191 DATABASE SETTINGS INTERFACE

In the Super username and Super password , set up thesystem user name and password of the Oracle database.

Note:

The Super password field can not be null. Otherwise, thedatabase can not be connected.

12.Click next and the macro parameter settings interface popsup, as shown in Figure 192.

FIGURE 192 MACRO PARAMETER SETTINGS INTERFACE



13. Fill in related parameters and click Next. The Confirm dia-log box pops up, prompting the user to back up the databasemanually, as shown in Figure 193.

FIGURE 193 CONFIRM DIALOG BOX

Note:

If the database is not backed up, back it up manually. For howto back up the database, refer to Uninstalling Oracle Database.

14. If the database is backed up, click OK and the system displaysthe upgrading progress, as shown in Figure 194.

FIGURE 194 UPGRADING PROGRESS BAR

The system automatically upgrade the software and the data-base.

15.After the upgrade completes, the Please Choice interfacepops up, as shown in Figure 195.



FIGURE 195 PLEASE CHOICE INTERFACE

16.Click all yes and the Upgrade succeeded interface pops up,as shown in Figure 196.

FIGURE 196 UPGRADE SUCCEEDED INTERFACE

17.After the upgrade completes, the files in the upgraded softwareare not executable and you should grant the right manually byusing the following command:

#chmod -R 755 /home/zxwomc

END OF STEPS



Upgrading OMM Client inWindowsPreparations

Before upgrading the OMMRB NM Server software and Client soft-ware, check the following items and make preparations:

1. Shut down the OMMRB NM Client software.

2. Shut down the OMMRB NM Server software.

3. Obtain one OMMRB application software installation CD.

Note:

OMMRB NM Server software must be shut down through the shut-down under $\ums-svr\bin. It can not be shut down just throughthe click on the close button on the cmd window.

Upgrading Steps in Windows

Steps 1. Open the NM installation program directory: \update\con-tainer\ and double-click the run.bat file to start the upgrade.

2. The UMS Update window pops up, as shown in Figure 197.

FIGURE 197 UMS UPDATE WINDOW

3. After a moment, the Upgrade Software interface pops up,as shown in Figure 198. Select English from the drop-downmenu.



FIGURE 198 UPGRADE SOFTWARE INTERFACE

4. Click OK and the Welcome to use the upgrade programinterface pops up, as shown in Figure 199.

FIGURE 199 WELCOME TO USE THE UPGRADE PROGRAM INTERFACE

5. Click Next and the System path interface pops up, as shownin Figure 200.



FIGURE 200 SYSTEM PATH INTERFACE

6. Click Choose and select the NM software root directory of theversion to be upgraded. This root directory is the father direc-tory of ums-clnt and ums-svr, as shown in Figure 201.

FIGURE 201 CHOOSE SYSTEM PATH DIALOG BOX

7. Click Open and the system returns to the System Path dialogbox, as shown in Figure 202.



FIGURE 202 CHOOSING DIRECTORY FOR UPGRADING

8. Click Next and a dialog box pops up, as shown in Figure 203.

FIGURE 203 UPGRADING BOTH

Select Client only if you have only installed the NM Client inyour local computer, as shown in Figure 204.



FIGURE 204 UPGRADING CLIENT ONLY

No manual operation is required in this step. The upgradingsoftware will make automatic selections according to the NMsoftware information to be upgraded.

9. Click Next and the upgrading progress interface pops up, asshown in Figure 205.


10.When the progress bar reaches its end, the Preview of up-grade information interface pops up, as shown in Figure 206.



FIGURE 206 PREVIEW OF UPGRADE INFORMATION INTERFACE

The interface displays the current NM system version and theversion to be upgraded. Please check the user information.If there is any discrepancy, click cancel to exit the currentupgrading program.

Note:


11.Click Next and the upgrading progress interface appears, asshown in Figure 207.




12.When the upgrading progress bar reaches its end, an interfacepops up, as shown in Figure 208.

FIGURE 208 SETTING DATABASE USERNAME AND PASSWORD

In the Super username and Super password , set up thesystem user name and password of the Oracle database.

Caution:

The Super password field can not be null.

13.Click Next and an interface pops up, as shown in Figure 209.



FIGURE 209 SETTING MACRO PARAMETERS

Fill in User of network management common databaseand PM Tablespace Name.

14.Click Next and a dialog box pops up, as shown in Figure 210.


15.Click OK and a dialog box pops up, as shown in Figure 211.



FIGURE 211 UPGRADING PROGRESS BAR

16.When the progress bar reaches its end, an dialog box pops up,as shown in Figure 212.

FIGURE 212 UPGRADE SUCCEEDED DIALOG BOX

17. The upgrade completes. Click End to exit from the currentupgrading program.

END OF STEPS



Checks

Log on the Server and open the NM Client. Choose Help > Abouton the main menu, and About interface pops up, where the ver-sion No. of the current NMS is displayed.

FIGURE 213 ABOUT INTERFACE

One-Click Upgrade ofOMMRB NM Server andClient

Prerequisites Exit OMMRB NM server and client before upgrading. It is recom-mended to exit the sever and the client by running the close-con-sole-linux.sh file under \ums-svr\bin.

Make sure that the language and character set used in the Linuxsystem is “zh_CN.GBK” or “zh_CN.GB18030”.

Context This procedure describes how to use one-click upgrade on theLinux platform and can also be applied on the windows platform.

Steps 1. Use applicable software to open and modify configuration itemsas required in the auto_run_param. properties file under/data1/zxwomc/update/container/, and then save the mod-ifications.

Two configurations items needs to be modified.



� One is the path of the NM system to be upgraded: . Change“C:\\ZXWR-OMCRB\\WOMC” to the installation path of theversion to be upgraded; for example, .

Note:

The path must be the complete father directory of the di-rectory where the ums-svr or ums-clnt folder is located.

� The other is the super user password of the default datasource in the NM system to be upgraded: . Change “oracle”to the super user password of the default data source in theactual installation environment.

2. Open the terminal command window and access the/data1/zxwomc/update/container/ directory. Run the./auto-linux.sh command to execute the one-click upgradingprogram. The system feeds back the upgrading result, asshown in Figure 214.

FIGURE 214 UPGRADE SUCCEED

END OF STEPS





C h a p t e r 7

Uninstalling OMM NMSoftware

Table of ContentsOverview........................................................................ 163Uninstalling OMMRB NM Client Programs............................. 163Uninstalling OMMRB NM Server Programs ........................... 164Uninstalling Oracle Database............................................. 165

OverviewThis chapter introduces installation the methods to uninstalling theNM Server, Client, and Oracle database.

Under the Windows 2003 operating system, OMM NM Client sup-ports the graphics installation methods.

Before uninstalling the OMM NM software, make sure that the NMprogram is closed normally.

The method of OMMRB uninstalling is the same as that of OMMBuninstalling. Therefore the upcoming chapter takes the OMMRBuninstalling as an example.

Uninstalling OMMRB NMClient Programs

Steps 1. Under the Windows 2003 operating system, choose Start >Programs > ZXWR-OMCRB > Uninstall ZXWROMRB, asshown in Figure 215.

FIGURE 215 SELECTING UNINSTALL NM PROGRAM



2. Confirm dialog box pops up, as shown in Figure 216.


3. Click Yes and the system starts to uninstall. After the installcompletes, Information dialog box pops up, which indicatesthe uninstall success, as shown in Figure 217.

FIGURE 217 INFORMATION DIALOG BOX

4. Click Yes and the uninstall completes.

END OF STEPS

Uninstalling OMMRB NMServer Programs

Steps 1. Log on the Linux terminal command window as the root userand enter the NM Server installation directory, as shown inFigure 218.


Chapter 7 Uninstalling OMM NM Software

FIGURE 218 ENTERING NM SERVER INSTALLATION DIRECTORY

2. Enter the rm -rf docs/ jdk-linux/ ums-svr/ ums-clnt/update/ command to start the uninstallation, as shown inFigure 219. The uninstallation completes.

FIGURE 219 DELETING NM SERVER INSTALLATION DIRECTORY

END OF STEPS

Uninstalling OracleDatabaseBacking Up Database

Steps 1. Log on the Linux terminal command window as the Oracle user.

2. On the machine where the Oracle Server is installed, executethe backup command in the following format:

$exp username/password@servicename file = /home/bakdir/bakfilename log = /home/bakdir/bakfilename.log

Note:

username/password is the user name and password formaintaining the database. servicename is the service namecorresponding to the database instance. /home/bakdir/bak-filename is an example of the path and path name of thebackup files. The suffix of the backup files is .dmp while thatof the log files is .log.



Under the surrounding shown in this chapter, enter the $expuep/u_tywg_2008@womcr file = expdat.dmp log=expdat.log command, as shown in Figure 220.

FIGURE 220 BACKUP COMMAND

3. When the backup succeeds, Export terminated successfully with-out warnings appears, as shown in Figure 221. The backup datacan be used to recover the original data of the database.

FIGURE 221 BACKUP SUCCESS

END OF STEPS



Stopping Oracle Services

Steps 1. Log in the Linux terminal command window as the oracle userand enter the following command, as shown in Figure 222.

FIGURE 222 ENTERING ORACLE PROCESS

2. Enter the command to make sure that the current Oracle is inthe normal connection, as shown in Figure 223.

FIGURE 223 CONFIRMING ORACLE CONNECTION NORMAL

3. Stop the Oracle service process, as shown in Figure 224.



FIGURE 224 STOPPING ORACLE SERVICE

END OF STEPS

Deleting Oracle Instances

Steps 1. Right-click on the Linux desktop and select Open Terminal,as shown in Figure 225.





FIGURE 226 CREATING DATABASE

3. Database Configuration Assistant: Welcome interfacepops up, as shown in Figure 227.

FIGURE 227 DATABASE CONFIGURATION ASSISTANT: WELCOMEINTERFACE

4. Click Next and Database Configuration Assistant, Step 1of 2: Operations interface pops up, as shown in Figure 228.Select Delete a Database.



FIGURE 228 DATABASE CONFIGURATION ASSISTANT, STEP 1 OF 2:OPERATIONS INTERFACE

5. Database Configuration Assistant, Step 2 of 2: Databaseinterface pops up, as shown in Figure 229.

FIGURE 229 DATABASE CONFIGURATION ASSISTANT, STEP 2 OF 2:DATABASE INTERFACE

6. Select the database to delete and click Finish. The interfacefor confirming the deletion pops up, as shown in Figure 230.



FIGURE 230 CONFIRMING DELETION

7. Click Yes and the system starts to delete, as shown in Figure231.

FIGURE 231 DATABASE DELETION IN PROGRESS INSTANCE

8. When the process bar reaches 100%, the system displays thatthe deletion completes, as shown in Figure 232.

FIGURE 232 DELETION COMPLETED INTERFACE

9. Click Yes to continue with other operations.



Click No to complete the deletion.

END OF STEPS

Uninstalling Oracle Database

Steps 1. Right-click on the Linux desktop and select Open Terminal,as shown in Figure 233.


2. Under the root user, log on as the oracle user, as shown inFigure 234.



FIGURE 234 LOGGING ON AS ORACLE USER

3. Run the runInstaller file, as shown in Figure 235.


4. Oracle Universal Installer: Welcome interface pops up, asshown in Figure 236.



FIGURE 236 ORACLE UNIVERSAL INSTALLER: WELCOME INTERFACE

5. Click Deinstall Products and Inventory interface pops up,as shown in Figure 237.

FIGURE 237 INVENTORY INTERFACE

6. Check the Oracle products to be deleted and click Delete.Confirmation interface pops up, as shown in Figure 238.



FIGURE 238 CONFIRMATION INTERFACE

7. Click Yes and Remove interface pops up, as shown in Figure239.

FIGURE 239 REMOVE INTERFACE

8. When the process bar reaches 100%, the system returns tothe interface shown in Figure 238.

9. Click Close and the Oracle database programs is uninstalled.

END OF STEPS





A p p e n d i x A

FAQ

Table of ContentsDatabase........................................................................ 177OMM NMS ...................................................................... 179Server Login ................................................................... 180Checking Link Setup between Server and OMP .................... 181Logs .............................................................................. 182Common Commands of Linux............................................ 182Common Commands of Oracle .......................................... 187

DatabaseImport/Export Failure and IllegibleCharacters in Records Inserted toDatabases

Problem Import/Export fails and illegible characters occur to recorddatabases.

Cause analysis The character set installed at NM database server is inconsistentwith that installed in NM Client.

Solution Identify how to set character sets in the database server and client.

1. Database Server

In general, specify the character set of the database serverwhen creating the database. After being created, the databasecannot be modified.

The character set of the database server should be AMERI-CAN_AMERICA.ZHS16GBK.

If the character set in the database server does not fulfill theabove requirements, delete the current database and createdatabase again.

2. Database Client

The character set of the database client is saved in the systemregistry. The location and value of the character set are dis-played as follows:



LOCALE_MACHINE\SOFTWARE\ORACLE\HOME0\NLS_LANG= AMERICAN_AMERICA.ZHS16GBKORACLE

Herein, SIMPLIFIED AMERICAN_AMERICA.ZHS16GBK is the correct char-acter set.

If an exception occurs at the client, check the setting of thecharacter set and modify character set. For details, refer toCheck the character set.

Illegible Characters Displayed inCreating Diagnosis and Test Tasks

Problem Illegible characters are displayed during creating diagnosis andtest tasks.

Cause analysis The national character set is not correctly set during the installa-tion of the database.

When the database is created, set the national character set toAL16UTF16.

Solution Log on to Oracle database as a sys user.

c:>sqlplus/nologSQL>connect sys/PWD as sysdbaSQL>select value$ from props$ where name='NLS_NCHAR_CHARACTERSET';

Check whether the value is AL16UTF16. If not, delete the currentdatabase and create database again.

Database Connection Failure Due toPower Off

Problem Due to sudden power off, databases are not connected afterpower-on.

Cause analysis There are several causes for failure in starting databases after ab-normal power off.

The general cause lies in the data repairs done by databases. Ina normal case, databases will start to repair data after the poweron.

Solution Log in to the Oracle database as a sys user or a sysdba user.

c:>sqlplus /nologSQL>connect sys/PWD as sysdbaSQL>alter database open

If commands are executed successfully, databases is restored nor-mally. If the system returns errors and prompts to repair data,execute the following command:


Appendix A FAQ

SQL>recover database

After command execution databases is running normally, showsthat the databases have been saved normally.

OMM NMSConnection Failure between Clientand Server (1)

Problem The host Server locates is prepared with several network adapters,so several IP addresses are configured to the host. The problemoccurs when Client fails to connect to the server.

Cause analysis Suppose the host Server locates is prepared with two networkadapters. Two IP addresses, IP1 and IP2, are configured to it.Herein, IP1 is the main IP address.

NM Server releases UMSS services by the main IP address of thehost. Thus, the IP address of Client and main IP address (IP1)of Server must belong to a same subnet or can ping each othersuccessfully.

If Client IP address and IP2 of Server host are in a same subnetwhile IP1 and IP2 cannot ping each other successfully, the connec-tion between Client and Server fails.

Solution Make sure that Client IP address and the main IP address of Servercan ping each other successfully.

Use the following command to display the main IP address of theworkstation:

# ipconfig -all

The most important is IP address of the workstation.

Connection Failure between Clientand Server (2)

Problem The host of Client is prepared with several network adapters, soseveral IP addresses are configured to the client. The problemoccurs; Client fails to connect to Server.

Cause analysis Suppose two IP addresses, IP1 and IP2, are configured to Client.Herein, IP1 is the main IP address.

When NM Client starts, it uses main IP address for login. Thus,main IP address of Client and Server must belong to the samesubnet or can ping each other successfully.



If Client IP2 address and main IP address of Server host are in thesame subnet while IP1 and IP2 can not ping each other success-fully, the connection between Client and Server fails.

Solution Make sure that the main IP address of Client and that of Servercan ping each other successfully.

Inconsistent File Format withContents

Problem When NM Server starts, it reports the error of the file format in-consistent with the contents.

Cause analysis The time format of Oracle database is not set, so NMS shows errorswhen entering time to Oracle database.

Since the default time format in the Oracle database is not YYYY-MM_DD HH24:MI:SS required by NM software, modify the timeformat as required.

Solution There are two methods to make modification: With Oracle graphictool, Enterprise Manager Console, or directly with command line.

1. Oracle graphic tool, Enterprise Manager Console

i. Log on the graphic webpage interface.

ii. Log on as the dba user with the sys.

iii. Choose Management > Entering initialization param-eter > spfile and search nls_date_format.

iv. Modify the nls_data_format into ‘YYYY-MM-DD HH24:MI:SS'.

v. Click Aplly.

vi. The system prompts whether to restart the database. ClickYes.

2. Command line

$ sqlplus /nolog

SQL>connect sys/PWD@SID as dba

SQL>ALTER SYSTEM SET nls_data_format='YYYY-MM-DD HH24:MI:SS' SCOP=SPFILE

SQL>shutdown# Close the database #

SQL>startup# Restart the database #

SQL>exit

Server Login1. When logging on through the Server, enter the correct user

name and password according to the prompts and then en-ter the Server system. Usually, operations on the Linux arethrough shell and all Linux commands are entered and exe-


Appendix A FAQ

cuted through shell. To start the shell, right-click on the desk-top and select Open Terminal.

2. When logging on through the network, use any standard Tel-net Client program. For example, through the Telnet Client at-tached to the Windows, users can enter the telnet 138.1.1.1(supposing it is the IP address of the Server) in the dos promptor Run column, enter the correct user name and password ac-cording to the prompts, and then log on the Server.

If the Client fails to connect the Server, such error promptsas inconsistent language and inconsistent products may pop up.The problem is that the configuration files are inconsistent atthe Server and at the Client. The configuration files is deploy-020womcr.properties and deploy-010muep.properties.

� Inconsistent language indicates that the ums.locale inthe deploy-030womcb.properties files are configuredinconsistently.

� Inconsistent products or versions indicates that theums.version.main and ums.product are configuredinconsistently.

Checking Link Setupbetween Server and OMP

Steps 1. Log on the SBCX Server through the Client and open the Con-figuration Management interface.

2. Check the topology tree on the left, as shown in Figure 240.

indicates that the link between the Server and the OMP isdisconnected. indicates the link between the Server andthe OMP is normal.

FIGURE 240 CHECKING LINK CONNECTION (DISCONNECTED)

END OF STEPS



LogsThe path to save the logs is \ums-svr\log\.

Configurable parameters of the deploy-010muep.propertiesunder the \ums-svr\deploy\ include:

userdefined-uep-psl-debugprn.file-size=8192KB

userdefined-uep-psl-debugprn.backup-index=20

userdefined-uep-psl-debugprn.buffer-io=false

userdefined-uep-psl-debugprn.buffer-size=8192

Common Commands ofLinux1. ls: List files and directories

For example: $ls

To list the contents of the current directory.

2. cp: Copy files and directories

For example: $cp src dest

To copy the src file into the dsc file.

3. rm: Delete files

For example: $rm abc

To delete the abc file.

4. mv: Change the file name or move the file

For example: $mv abc ../bcd

To move the abc file from the current directory to the high-leveldirectory and change the name into bcd.

5. man: Display the help information

For example: $man ls

To display the help information of the ls file.

6. who: Show who is in the system

For example: $who

To show who has logged into the system.

7. mkdir: Create directories

For example: $mkdir newdir

To create the newdir directory under the current directory.

8. rmdir: Delete directories

For example: $rmdir dir1


Appendix A FAQ

To delete the dir1 directory from the current directory. Thedir1 directory must be null. IF not, use the rm -fr dir1 todelete constrainedly.

9. chmod: Change the file mode

Foe example: $chmod 700 abc

To change the attributes of the abc file into 700 mode, that is,only the owner can rear/write/operate on the file whle otherusers can not.

10.chown: Change the owner of the file

For example: $chown omc abc

To change the owner of the abc file into omc.

11.chgrp: Modify the user group of the file

For example: $chgrp omc abc

To change the user group of the abc file into omc.

12.pwd: Display the current directory

For example: $pwd

To display the current directory.

13. tail: Display the last lines of the file

For example: $tail -f abc

To display the last lines of the abc file and to monitor thechanges of the file. If the file is added, display the added con-tents.

For example: $tail -100 abc

To display the last 100 lines of the abc file.

14.ps: Display the system process

For example: $ps -U omc

To display all processes of the omc user. -U indicates users.

15.cat: Display the contents of one file

For example: $cat abc

To display the contents of the abc on the screen.

16.date: Display or modify the system time

For example: $date

To display the current time in the following format:

Dec. 10th, 2003, Wednesday, 14:02:41, CST

$date 091812002001

To set the current time to Sep. 18th, 2001, 12:00

17.df: Display the usage of the partition

For example: $df -k

To display the usage of the partition in the unit of kbyte.

18.du: To display the number of bytes occupied by the direc-tory/file



For example: $du -ks dir1

To display the number of the bytes occupid by the dir1 direc-tory in the unit of kbyte.

19. tar: Pack/Unpack the file. The suffix of the tar file is .tar.

For example: $tar -cvf a.tar dir1 dir2 file1

Pack the dir1 directory, dir2 directory, and file1 file into onepackage, a.tar. The tar command is only used to pack not tocompress.

For example: $tar -xvf a.tar

Unpack the a.tar file under the current directory and form thedir1, dir2, and file1.

20.gzip/gunzip: Compress/Uncompress the file. The suffix ofthe gzip file is .gz.

For example: $gzip a.tar

Uncomptess the a.tar file and the uncompressed file is nameas a.tar.gz. After the uncompress, the original file, a.tar, isdeleted automatically.

For example: $gunzip a.tar.gz

Uncompress the file and the new file is named as a.tar. Afterthe uncompress, the original file, a.tar.gz, is deleted automat-ically.

21.compress/uncompress: Compress/Uncompress the file.The suffix of the compress file is .z

For example: $compress a.tar

Uncomptess the a.tar file and the uncompressed file is nameas a.tar.Z. After the uncompress, the original file, a.tar, isdeleted automatically.

For example: $uncompress a.tar.Z

Uncompress the file and the new file is named as a.tar. Afterthe uncompress, the original file, a.tar.Z, is deleted automat-ically.

22.su: To change the user itself into another user

For example: $su oracle

To change the user itself into the oracle user. It is required toenter the password. If the su is not followed by user name, itbecomes the root user.

23.kill: Kill the process

For example: $kill -9 1033

To kill the process whose No. is 1033. The process No. can befound with the ps command. -9 indicates to kill the processconstrainedly.

24.shutdown: To reboot the system

For example: $/usr/sbin/shutdown -y -g 0 -i 6

To reboot the system.

25. reoot: To reboot the system


Appendix A FAQ

For example: $reboot

To reboot the system. Compared with the shutdown com-mand, the reboot command is a forcible reboot, which mayresult in that some processes do not save the data. It is sug-gested to use the shutdown command to reboot the system.

26.stop+a: Disconnect the system operation

For example: Okstop+a

In any cases, enter the stop+a command, and the Linux op-erating system stops its operation and OK prompt pops up.

27.boot: Boot the system

For example: OKboot cdrom

Under the OK prompt, enter the boot cdrom command, andthe Server boots the system from the disk.

28. id: Display the user id and user name

For example: $id

uid=1005(omc) gid=10(staff)

The system displays the user id and user name.

29.passwd: Modify the user password

For example: $passwd omc

To modify the password of the omc user. Enter the originalpassword if the omc user and enter the new password of theuser twice.

30. ln: Create the link of the file or the directory

For example: $ln –s /net/138.1.1.1$OMCHOME/tmp/ftp$OMCHOME /tmp/ftp

To link the $OMCHOME/tmp/ftp directory of the host machine,138.1.1.1, to the $OMCHOME/tmp/ftp of the local machine.

31. touch: To modify the file access and modification time

For example: $touch test

If the test file has existed, the touch command changes thefile mollification time to the current time. If the test file doesnot exist, the touch command creates the test file.

32.groupadd: Create user group

For example: $groupadd –g 1000 staff

To create the staff user group and its id is 1000.

33.useradd: Create the user

For example: $useradd –d /home/oracle –m –g oinstalloracle

To create the oracle user and it belongs to the oinstall usergroup and to set the /home/oracle as the main directory ofthe oracle user.

34. ldd: List the dynamic relationship of the executable files

For example: $ldd amp

To list all files that the amp file belongs to.



35. format: Disk partition and maintenance tool

For example: $format

The system displays the format menu and the user operatesaccording to the menu.

36.prtvtoc and fmthard: Mirror disk partition

For example: $ prtvtoc –h /dev/rdsk/c0t0d0s2 | fmthard-s - /dev/rdsk/c0t1d0s2

To copy the partition table of the system booting disk,c0t0d0s2 to the mirror disk, c0t1d0s2.

37.metainit: Create a mirror of a file system

For example: $ metainit -f d10 1 1 c0t0d0s0

$metainit -f d20 1 1 c0t1d0s0

$metainit d30 -m d10

To create one-to-one cascading for the c0t0d0s0 partition andthe c0t1d0s0 partition. dxx is the device No. xx can beany value. Create the metadevice mirror and add the mirrordevice, d10, to d30.

38.metaroot: Update the /etc/vfstab file and the /etc/sys-tem file

For example: $ metaroot d30

After executing the metainit command, use the metarootcommand to update the file. Do not manually edit these twofiles.

39. lockfs: Reboot and allow the system to re-mount the mirror

For example: $lockfs –fa

$init 6

To reboot and allow the system to re-mount the mirror.

40.metattach: Attach the mirror device to the mirror

For example: $metattach d30 d20

To attach the second mirror device to the mirror. The data onthe disk will synchronize with the mirrored disk through thebooting disk.

41.metadb: Create the duplicate of the state database

For example: $metadb -a -f -c2 /dev/dsk/c0t0d0s3 /dev/dsk/c0t1d0s3

To create the duplicate of the state database.

42.newfs: Create a new UFS file system

For example: $newfs -i 8192 -c 256 /dev/md/rdsk/d7

To create a new UFS file system.

43. free: View the usage of the memory

For example: #free

The display result is as shown in Figure 241. The method tocalculate the memory size is : [8312744K/1024/1024]= 8G(take integer)


Appendix A FAQ

FIGURE 241 QUERYING MEMORY SIZE

Common Commands ofOracleStarting Oracle Service

Steps 1. Log on the Server as the Oracle user.


$ sqlplus /nolog

3. Execute the following command and connect to the databaseas the sys user.

sql>connect sys/oracle as sysdba

4. Execute the following command to start the database:

sql>startup

5. Execute the following command to exit:

sql>exit

END OF STEPS

Closing Oracle Service





$ sqlplus /nolog

3. Execute the following command and connect the database asthe sys user:

sql>connect sys/oracle as sysdba

4. Close the database with the following three methods:

sql>shutdown normal

sql>shutdown immediate

sql>shutdown abort

When the database is shut down with the normal option, thesystem cancels all users to visit the database and waits until allusers complete the requests and disconnects with the Server.When closing the database is shut down with the immediateoption, the system shuts down the database immediately, thecurrent SQL sentence that the data is processing is terminatedimmediately, and all unsubmitted transactions are rolled back.The abort option is used in emergency when the above twomethods do not take effect. When the database is shut downwith the immediate option, the SQL sentence is terminatedand unsubmitted transaction is not rolled back. The databaseautomatically recovers the conflict when starting next time. itis recommended to shut down the database with the immediatemethod on the site.

5. Execute the following command and exit the Oracle Servermanager:

SVRMGR>exit

END OF STEPS

Starting/Stopping Oracle Listener


2. Execute the following command to start the Oracle Listenerservice:

$lsnrctl start

3. Execute the following command to stop the Oracle Listener ser-vice:

$lsnrctl stop

END OF STEPS


Figures

Figure 1 Connection of Centralized NM and NE........................ 1

Figure 2 OMM Software Structure ......................................... 3

Figure 3 M/S SBCX Configuration Mode ................................. 4

Figure 4 Log Service Configuration........................................ 5

Figure 5 Welcome............................................................... 7

Figure 6 Net Service Name Configuration ............................... 8

Figure 7 Net Service Name Configuration, Service Name.......... 8

Figure 8 Net Service Name Configuration, Select Protocol ........ 9

Figure 9 Net Service Name Configuration, TCP/IP Protocol........ 9

Figure 10 Net Service Name Configuration, Test.....................10

Figure 11 Net Service Name Configuration, Net Service Name...10

Figure 12 Net Service Name Configuration, Another Nets

Service Name ...................................................11

Figure 13 Installation Flow of NM Software............................18

Figure 14 Adding samba User..............................................29

Figure 15 Setting Shared Folder ..........................................29

Figure 16 Selecting Open Terminal .......................................36

Figure 17 Viewing Folder ....................................................36

Figure 18 Copying 10201_database_linux32.zip File ...............37

Figure 19 Logging in As Oracle User .....................................37

Figure 20 Entering installtmp Folder .....................................38

Figure 21 Decompressing 10201_database_linux32.zip File .....38

Figure 22 Entering database Folder ......................................39

Figure 23 Running runInstaller File ......................................39

Figure 24 Select Installation Method Interface .......................40

Figure 25 Select Installation Type Interface...........................40

Figure 26 Specify Home Details Interface..............................41

Figure 27 Available Product Components Interface .................42

Figure 28 Product-Specific Prerequisite Checks Interface.........43

Figure 29 Privileged Operating System Groups Interface .........43

Figure 30 Create Database Interface ....................................44

Figure 31 Summary Interface..............................................44

Figure 32 Install Interface ..................................................45

Figure 33 Execute Configuration Scripts................................45



Figure 34 Running root.sh File.............................................46

Figure 35 End of Installation Interface..................................46

Figure 36 Exit Interface......................................................47

Figure 37 Uncompressing p6810189_10204_Linux-x86.zip

File ..................................................................47

Figure 38 Running runInstaller File ......................................48

Figure 39 Welcome Interface...............................................48

Figure 40 Specify Home Details Interface..............................49

Figure 41 Product-Specify Prerequisite Checks Interface .........49

Figure 42 Oracle Configuration Manager Registration

Interface ..........................................................50

Figure 43 Summary Interface..............................................50

Figure 44 Install Interface ..................................................51

Figure 45 Execute Configuration Scripts................................51

Figure 46 Running root.sh File.............................................52

Figure 47 End of Installation Interface..................................52

Figure 48 Exit Interface......................................................53


Figure 50 Entering Listener Configuration Command ..............54

Figure 51 Oracle Net Configuration Assistant: Welcome

Interface ..........................................................54

Figure 52 Oracle Net Configuration Assistant: Listener

Interface ..........................................................55

Figure 53 Oracle Net Configuration Assistant: Listener Name

Interface ..........................................................55

Figure 54 Oracle Net Configuration Assistant: Select Protocol

Interface ..........................................................56

Figure 55 Oracle Net Configuration Assistant: TCP/IP

Protocol Interface ..............................................56

Figure 56 Oracle Net Configuration Assistant: More Listeners

Interface ..........................................................57

Figure 57 Oracle Net Configuration Assistant: Listener

Configuration Done Interface...............................57

Figure 58 Listener Configuration Complete Interface...............58

Figure 59 Displaying Listener Configuration Information..........58


Figure 61 Entering Database Creation Command ...................59

Figure 62 Database Configuration Assistant: Welcome

Interface ..........................................................60


Figures

Figure 63 Database Configuration assistant, Step 1 of 12:

Operations Interface ..........................................60

Figure 64 Database Configuration assistant, Step 2 of 12:

Database Template Interface...............................61

Figure 65 Database Configuration Assistant, Step 3 of 12:

Database Identification Interface .........................61


Management Options Interface............................62


Database Credentials Interface............................62


Storage Options Interface ...................................63


Database File Locations Interface.........................63

Figure 70 Database Files Location ........................................64


Recovery Configuration Interface .........................64


Database Content Interface ................................65


Initialization Parameters .....................................65

Figure 74 Database Configuration Assistant, Step 10 of 12

Initialization Parameters Interface — Sizing Tab .....66


Initialization Parameters Interface — Character

Sets Tab...........................................................66

Figure 76 All Initialization Parameters Interface .....................67


Initialization Parameters Interface — Connection

Mode Tab..........................................................68


Database Storage Interface.................................68


Creation Options Interface ..................................69

Figure 80 Confirmation Interface .........................................69

Figure 81 Database Configuration Assistant Creation

Interface ..........................................................70

Figure 82 Database Configuration Assistant Information

Interface ..........................................................70

Figure 83 Connecting Oracle Service ....................................71



Figure 84 Starting up/Shutting Oracle Service .......................72

Figure 85 Stopping Listener ................................................73

Figure 86 Starting Listener .................................................73

Figure 87 Querying Character Set at Database Server ............74

Figure 88 Querying Character Set at Database Client..............75

Figure 89 Checking Data Format..........................................75

Figure 90 Checking Settings of Environment Variables ............81

Figure 91 Viewing Rights ....................................................82


Figure 93 Checking Installation Folder ..................................84

Figure 94 Running install-linux.sh File ..................................85

Figure 95 Please Select Language Interface...........................85

Figure 96 You should accept the agreement to continue

installing Interface.............................................86

Figure 97 Please Select Product Interface .............................86

Figure 98 Please Select Product Module Interface...................87

Figure 99 Please Set Installation Path Interface .....................88

Figure 100 Set of Application Database Interface ...................89

Figure 101 Drop Initial Data Interface ..................................90

Figure 102 Drop Initial Data Process Interface .......................91

Figure 103 Database Module Set Interface — Small Module.....92

Figure 104 Database Parameter Set Dialog Box — Fixed Path...92

Figure 105 Database Parameter Set Dialog Box — Disk

Partition ...........................................................93

Figure 106 Database Module Set Interface — Self-defined

Module.............................................................94

Figure 107 Set Database File Path Interface ..........................94

Figure 108 Set Size of Database Interface.............................95

Figure 109 Please View Install Information Interface ..............96

Figure 110 Install Application Database Server Interface.........96

Figure 111 Install the application program Interface...............97

Figure 112 Node B FTP Configure Interface ...........................97

Figure 113 RNC FTP SERVER IP Configure Interface ...............98

Figure 114 Minos FTP SERVER IP Configure Interface .............99

Figure 115 Master Clock Sync Server Configure Interface........99

Figure 116 SBCX Board Configure Interface — Backup Mode

None.............................................................. 100

Figure 117 SBCX Board Configure Interface - Backup Mode

Master-Slave (Left) .......................................... 100


Figures

Figure 118 SBCX Board Configure Interface - Backup Mode

Master-Slave (Right) ........................................ 101

Figure 119 make_profile................................................... 101

Figure 120 Set JVM Memory Interface ................................ 102

Figure 121 Config Environment Interface ............................ 103

Figure 122 Setup Finished Interface ................................... 103

Figure 123 VIEW README Interface ................................... 104

Figure 124 Entering Installation Directory ........................... 105

Figure 125 Entering bin File .............................................. 105

Figure 126 Running run-linux.sh File .................................. 106

Figure 127 Checking Running State.................................... 106

Figure 128 Shutting Down Server ...................................... 107

Figure 129 View Installation Folder .................................... 109

Figure 130 Run install-linux.sh .......................................... 109

Figure 131 Welcome ........................................................ 110

Figure 132 View the ZTE Corporation Agreement ................. 110

Figure 133 Select Product ................................................. 111

Figure 134 Select Product Module ...................................... 111

Figure 135 Set the Installation Path ................................... 112

Figure 136 Set of Application Database............................... 113

Figure 137 Drop Initial Data.............................................. 114

Figure 138 Drop Initial Data.............................................. 114

Figure 139 Small Module .................................................. 115

Figure 140 Fixed Path ...................................................... 116

Figure 141 Disk Partition .................................................. 117

Figure 142 Self Defined Module ......................................... 117

Figure 143 Set Database File Path...................................... 118

Figure 144 Set Size of Database ........................................ 119

Figure 145 View Install Information ................................... 119

Figure 146 Install Application Database Server .................... 120

Figure 147 Install the application program .......................... 120

Figure 148 Node B FTP Configure....................................... 121

Figure 149 Master Clock Sync Server Configure ................... 121

Figure 150 Make Profile .................................................... 122

Figure 151 ..................................................................... 122

Figure 152 Configure Environment ..................................... 123

Figure 153 Setup Finished ................................................ 123

Figure 154 VIEW README................................................. 124

Figure 155 Please Select Language Interface....................... 126



Figure 156 You should accept the agreement to continue

installing Interface........................................... 127

Figure 157 Please Select Product Interface.......................... 127

Figure 158 Please Select Product Module Interface ............... 128

Figure 159 Please Set Installation Path Interface ................. 128

Figure 160 Please View Install Information Interface ............ 129

Figure 161 Install the Application Program Interface............. 129

Figure 162 Master Clock Sync Server Configure Interface...... 130

Figure 163 Set JVM Memory Interface ................................ 130

Figure 164 Please Choose Functions Interface ..................... 131

Figure 165 Config Environment Interface ............................ 131


Figure 167 VIEW README Interface ................................... 132

Figure 168 NM Client Startup Menu.................................... 133

Figure 169 Run Client Shortcut Icon................................... 133

Figure 170 Select Language .............................................. 135

Figure 171 ZTE Corporation Agreement .............................. 135

Figure 172 Select Product ................................................. 136

Figure 173 Select Product Module ...................................... 136

Figure 174 Set Installation Path......................................... 137

Figure 175 View Installation Information............................. 137

Figure 176 Install the Application Program .......................... 138

Figure 177 Master Clock Sync Server Configuration .............. 138

Figure 178 Set JVM Memory.............................................. 139

Figure 179 Choose Functions............................................. 139

Figure 180 Configure Environment ..................................... 140


Figure 182 VIEW README................................................. 141

Figure 183 Shortcut Icon .................................................. 142

Figure 184 Upgrade Software Interface .............................. 144

Figure 185 Welcome to use the upgrade program Interface ... 145

Figure 186 System Path Interface ...................................... 145

Figure 187 Upgrade Mode Interface ................................... 146

Figure 188 Upgrading Progress Interface ............................ 146

Figure 189 Preview of upgrade information Interface............ 147

Figure 190 Creating Client Upgrade Package ....................... 147

Figure 191 Database Settings Interface .............................. 148

Figure 192 Macro Parameter Settings Interface.................... 148

Figure 193 Confirm Dialog Box .......................................... 149

Figure 194 Upgrading Progress Bar .................................... 149


Figures

Figure 195 Please Choice Interface .................................... 150

Figure 196 Upgrade Succeeded Interface ............................ 150

Figure 197 UMS Update Window ........................................ 151

Figure 198 Upgrade Software Interface .............................. 152

Figure 199 Welcome to use the upgrade program Interface ... 152

Figure 200 System Path Interface ...................................... 153

Figure 201 Choose System Path Dialog Box......................... 153

Figure 202 Choosing Directory for Upgrading....................... 154

Figure 203 Upgrading Both ............................................... 154

Figure 204 Upgrading Client Only....................................... 155


Figure 206 Preview of Upgrade Information Interface ........... 156


Figure 208 Setting Database Username and Password .......... 157

Figure 209 Setting Macro Parameters ................................. 158


Figure 211 Upgrading Progress Bar .................................... 159

Figure 212 Upgrade Succeeded Dialog Box.......................... 159

Figure 213 About Interface ............................................... 160

Figure 214 Upgrade Succeed............................................. 161

Figure 215 Selecting Uninstall NM Program ......................... 163


Figure 217 Information Dialog Box..................................... 164

Figure 218 Entering NM Server Installation Directory............ 165

Figure 219 Deleting NM Server Installation Directory............ 165

Figure 220 backup Command............................................ 166

Figure 221 backup Success ............................................... 166

Figure 222 Entering Oracle Process .................................... 167

Figure 223 Confirming Oracle Connection Normal................. 167

Figure 224 Stopping Oracle Service.................................... 168

Figure 225 Selecting Open Terminal ................................... 168

Figure 226 Creating Database ........................................... 169

Figure 227 Database Configuration Assistant: Welcome

Interface ........................................................ 169


Operations Interface ........................................ 170


Database Interface .......................................... 170

Figure 230 Confirming Deletion ......................................... 171

Figure 231 Database Deletion In Progress Instance .............. 171



Figure 232 Deletion Completed Interface ............................ 171

Figure 233 Selecting Open Terminal ................................... 172

Figure 234 Logging On as Oracle User ................................ 173

Figure 235 Running runInstaller File................................... 173

Figure 236 Oracle Universal Installer: Welcome Interface...... 174

Figure 237 Inventory Interface .......................................... 174

Figure 238 Confirmation Interface...................................... 175

Figure 239 Remove Interface ............................................ 175

Figure 240 Checking Link Connection (Disconnected) ........... 181

Figure 241 Querying Memory Size ..................................... 187


Tables

Table 1 MAC Address Calculation..........................................17

Table 2 SBCX Server Hardware Configurations .......................19

Table 3 Server Software Configurations ................................19

Table 4 Client Hardware Configurations.................................20

Table 5 Client Software Configurations..................................20

Table 6 Disk Partition .........................................................22





Glossary

JVM- Java Virtual Machine

LAN- Local Area Network

NM- Network Management

NMS- Network Management System

OMM- Operation & Maintenance Module

OMMB- Operation & Maintenance Moudle (Node B)

OMMR- Operation & Maintenance Module (RNC)

OMP- Operation & Maintenance Processor

PM- Performance Management

SBCX- X86 Single Board Computer

WAN- Wide Access Network


Documents

ZXWR RNC (V3.09.30) Radio Network Controller Operation and Maintenance Module Software Installation Guide