You are on page 1of 92

M2000 V200R012C00

Administrator Guide (x3850, SUSE10)


Issue Date Draft A 2012-02-27

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions


and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.


Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com

Website: Email:

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

About This Document

About This Document


Overview
This document is intended for the M2000 administrator. It is applicable to the IBM x3850 X5 server and based on the SUSE Linux operating system and the Oracle database. In addition, it provides the concepts related to system management tasks, the detailed operation procedures, and the guide to routine maintenance, and the processes and services, and describes the usage of frequently used commands and tools.

Product Version
Product versions corresponding to this document are as follows: Product Name M2000 Product Version V200R012

Intended Audience
This document is intended for system administrators.

Change History
Draft A (2012-02-27)
This issue is a draft. It is a new document, and only applies to the Core Network IMS field.

Organization
1 Routine Maintenance Items This section describes the recommended maintenance items of the M2000. 2 Powering On/Off the System
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ii

M2000 Administrator Guide (x3850, SUSE10)

About This Document

This describes the procedures for powering on and off the M2000 system when IBM x3850 X5 acts as the M2000 server. 3 Configuring the Parameters of the M2000 Server This describes how to set the parameters of the M2000 server. 4 Configuring the NTP Service This section describes how to set the M2000 server as an NTP client or an intermediate-layer NTP server. 5 Managing M2000 Users This describes how to manage OS users and DB users of the M2000 system. 6 Managing the M2000 Processes and Services This describes how to manage the M2000 processes so that the processes and services on the M2000 server can function properly. 7 Managing M2000 Database This chapter describes how to manage the M2000 database. This chapter also describes the concepts of the M2000 database and procedures on how to view the database status, start or stop the database, and check the database space. 8 Managing Disk Array and Hardware This describes how to manage the disks and hardwares on the M2000 server. 9 Managing License This describes how to query and replace the license file on the M2000 server through the M2000 client.

Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii

M2000 Administrator Guide (x3850, SUSE10)

About This Document

Symbol

Description Provides additional information to emphasize or supplement important points of the main text.

General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.

Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

[ x | y | ... ]*

GUI Conventions The GUI conventions that may be found in this document are defined as follows.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

iv

M2000 Administrator Guide (x3850, SUSE10)

About This Document

Convention Boldface >

Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

Contents

Contents
About This Document.....................................................................................................................ii 1 Routine Maintenance Items........................................................................................................1 2 Powering On/Off the System......................................................................................................2
2.1 Powering on the System Securely......................................................................................................................3 2.2 Powering off the System Securely......................................................................................................................5

3 Configuring the Parameters of the M2000 Server...................................................................8


3.1 Changing the IP Address of the M2000 Server..................................................................................................9

4 Configuring the NTP Service....................................................................................................12


4.1 Methods for Configuring the NTP Service on the M2000 Server....................................................................13 4.2 Setting the M2000 Server as the NTP Client...................................................................................................14 4.3 Setting the M2000 Server as an Intermediate-Layer NTP Server....................................................................16 4.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE)...........................................18

5 Managing M2000 Users..............................................................................................................20


5.1 User Type.........................................................................................................................................................21 5.2 Changing the Password of User root................................................................................................................25 5.3 Changing the Password of User ossuser...........................................................................................................26 5.4 Changing the Password of User ftpuser...........................................................................................................27 5.5 Changing the Password of User oracle.............................................................................................................28 5.6 Changing the Password of User DB.................................................................................................................29

6 Managing the M2000 Processes and Services........................................................................31


6.1 Introduction to M2000 Processes and Services................................................................................................32 6.1.1 3rdTool_agent Process............................................................................................................................32 6.1.2 adn_agent Process....................................................................................................................................32 6.1.3 adss_agent Process..................................................................................................................................32 6.1.4 antenna_agent Process.............................................................................................................................32 6.1.5 ce_agent Process......................................................................................................................................33 6.1.6 cmdc_agent Process.................................................................................................................................33 6.1.7 cmengine_agent Process..........................................................................................................................33 6.1.8 cmeserver_agent Process.........................................................................................................................33 6.1.9 cmexp_agent Process...............................................................................................................................34 6.1.10 cmserver_agent Process.........................................................................................................................34 Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vi

M2000 Administrator Guide (x3850, SUSE10)

Contents

6.1.11 corba_agent Process..............................................................................................................................34 6.1.12 cpm_agent Process................................................................................................................................34 6.1.13 dam Process...........................................................................................................................................35 6.1.14 datacollectorsvr Process........................................................................................................................35 6.1.15 DCServer Process..................................................................................................................................35 6.1.16 devdoc_agent Process............................................................................................................................35 6.1.17 dsXXXX agent Process...........................................................................................................................35 6.1.18 eam_agent Process.................................................................................................................................36 6.1.19 Eml_PerfSvr Process.............................................................................................................................36 6.1.20 Eml_PubSvr Process..............................................................................................................................36 6.1.21 fars_agent Process.................................................................................................................................36 6.1.22 fmmedXXXX_agent Process..................................................................................................................37 6.1.23 fmnotify_agent Process.........................................................................................................................37 6.1.24 FMPreServiceXXXX_agent Process......................................................................................................37 6.1.25 fnlicense_agent Process.........................................................................................................................38 6.1.26 gem_agent Process................................................................................................................................38 6.1.27 glmssyn_agent Process..........................................................................................................................38 6.1.28 ifms_agent Process................................................................................................................................38 6.1.29 InventoryDM Process............................................................................................................................39 6.1.30 ipm_agent Process.................................................................................................................................39 6.1.31 irp_agent Process...................................................................................................................................39 6.1.32 itm_agent Process..................................................................................................................................40 6.1.33 lic_agent Process...................................................................................................................................40 6.1.34 log_agent Process..................................................................................................................................40 6.1.35 maintain_agent Process.........................................................................................................................41 6.1.36 manager_agent Process..........................................................................................................................41 6.1.37 mc Process.............................................................................................................................................41 6.1.38 medXXXX_agent Process.......................................................................................................................41 6.1.39 ncc0X01_agent Process.........................................................................................................................42 6.1.40 necomm_agent Process..........................................................................................................................42 6.1.41 nelicense_agent Process........................................................................................................................42 6.1.42 nemgr_ptn Process.................................................................................................................................43 6.1.43 nemgr_rtn Process.................................................................................................................................43 6.1.44 neproxy Process.....................................................................................................................................43 6.1.45 neuser_agent Process.............................................................................................................................43 6.1.46 ngnffs_agent Process.............................................................................................................................43 6.1.47 ngnni112_agent Process........................................................................................................................43 6.1.48 ngnnis_agent Process.............................................................................................................................44 6.1.49 ngntestmanage_agent Process...............................................................................................................44 6.1.50 nhcservice_agent Process......................................................................................................................44 6.1.51 nicservice_agent Process.......................................................................................................................44 6.1.52 nimserver_agent Process.......................................................................................................................44 Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii

M2000 Administrator Guide (x3850, SUSE10)

Contents

6.1.53 nms_mml_agent Process.......................................................................................................................45 6.1.54 partition_agent Process..........................................................................................................................45 6.1.55 pm_agent Process..................................................................................................................................45 6.1.56 PMDataSynchronizer Process...............................................................................................................45 6.1.57 pmengine0X01_agent Process...............................................................................................................45 6.1.58 pmexp_agent Process............................................................................................................................46 6.1.59 pmmon_agent Process...........................................................................................................................46 6.1.60 PMSDm Process....................................................................................................................................46 6.1.61 porttrunk_agent Process........................................................................................................................46 6.1.62 PQMDm Process...................................................................................................................................47 6.1.63 proxy_agent Process..............................................................................................................................47 6.1.64 PRSAssistantService_agent Process......................................................................................................47 6.1.65 prsdc_agent Process...............................................................................................................................47 6.1.66 prsfs_agent Process................................................................................................................................47 6.1.67 prsreport_agent Process.........................................................................................................................48 6.1.68 prssum_agent Process............................................................................................................................48 6.1.69 rn_agent Process....................................................................................................................................48 6.1.70 RouterMgrDm Process..........................................................................................................................48 6.1.71 ScriptModuleService_agent Process.....................................................................................................49 6.1.72 scriptserver_agent Process.....................................................................................................................49 6.1.73 SecurityMgrDm Process........................................................................................................................49 6.1.74 sm_agent Process...................................................................................................................................49 6.1.75 snm_agent Process.................................................................................................................................49 6.1.76 snmp_agent Process...............................................................................................................................49 6.1.77 son_agent Process..................................................................................................................................50 6.1.78 sso_agent Process..................................................................................................................................50 6.1.79 swm_agent Process................................................................................................................................50 6.1.80 threshold_agent Process........................................................................................................................50 6.1.81 toolkit Process........................................................................................................................................51 6.1.82 trapdispatcher Process...........................................................................................................................51 6.1.83 TXTNBIDm Process.............................................................................................................................51 6.1.84 uap_agent Process..................................................................................................................................51 6.1.85 uflight_dispatcher Process.....................................................................................................................51 6.1.86 umgupdsvr_agent Process.....................................................................................................................52 6.1.87 UniteUitlDM Process............................................................................................................................52 6.1.88 xftpXX01_agent Process........................................................................................................................52 6.1.89 Trace Server Services and Processes.....................................................................................................52 6.1.90 Processes and Services Related to Each Northbound Interface.............................................................54 6.1.91 Checking the Status of the M2000 Processes........................................................................................54 6.2 Viewing the Running Status of M2000 Services (SUSE)................................................................................55 6.3 Starting the M2000 Server (SUSE)..................................................................................................................57 6.4 Stopping the M2000 Services (SUSE).............................................................................................................58 Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. viii

M2000 Administrator Guide (x3850, SUSE10)

Contents

7 Managing M2000 Database........................................................................................................59


7.1 Introduction to the M2000 Database (Oracle, ATAE).....................................................................................60 7.1.1 omcdb......................................................................................................................................................60 7.1.2 logdb........................................................................................................................................................62 7.1.3 smdb.........................................................................................................................................................62 7.1.4 topodb......................................................................................................................................................63 7.1.5 fmdb.........................................................................................................................................................64 7.1.6 pmdb........................................................................................................................................................64 7.1.7 swmdb......................................................................................................................................................65 7.1.8 pmcomdb.................................................................................................................................................66 7.1.9 itfndb........................................................................................................................................................67 7.1.10 farsdb.....................................................................................................................................................68 7.1.11 osstempdb..............................................................................................................................................69 7.1.12 eamdb.....................................................................................................................................................69 7.2 Checking Oracle Services.................................................................................................................................70 7.3 Starting Oracle Service.....................................................................................................................................72 7.4 Stopping Oracle Service...................................................................................................................................73 7.5 Checking Database Space.................................................................................................................................74

8 Managing Disk Array and Hardware......................................................................................76


8.1 Viewing the CPU and Memory Usage of the M2000 Server (SUSE)..............................................................77 8.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands...............................................78 8.3 Clearing the Disk Space of the M2000 Server (SUSE)....................................................................................78

9 Managing License........................................................................................................................81
9.1 Querying the M2000 License...........................................................................................................................82 9.2 Updating the M2000 License...........................................................................................................................82

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

ix

M2000 Administrator Guide (x3850, SUSE10)

1 Routine Maintenance Items

1
No. 1 2 3 4 5 Item

Routine Maintenance Items

This section describes the recommended maintenance items of the M2000. Table 1-1 lists the recommended maintenance items of the M2000. You can add or delete maintenance items according to your requirements. Table 1-1 Maintenance item list Frequency Daily Daily Monthly Daily Weekly

6.2 Viewing the Running Status of M2000 Services (SUSE) 7.2 Checking Oracle Services 7.5 Checking Database Space 8.1 Viewing the CPU and Memory Usage of the M2000 Server (SUSE) 8.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands 9.1 Querying the M2000 License

Monthly

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

2 Powering On/Off the System

2
About This Chapter

Powering On/Off the System

This describes the procedures for powering on and off the M2000 system when IBM x3850 X5 acts as the M2000 server. 2.1 Powering on the System Securely This section describes how to power on the M2000 server and related cautions. 2.2 Powering off the System Securely This section describes the procedure for powering off the M2000 hardware devices and related notes when the IBM x3850 X5 functions as the M2000 server.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

2 Powering On/Off the System

2.1 Powering on the System Securely


This section describes how to power on the M2000 server and related cautions.

Prerequisites
l The components of the M2000 system are installed in the cabinet. Before you power on the cabinet, ensure that the power switch of the cabinet power distribution box (PDB) must be disabled. After the cabinet is powered on, the device power switch is connected to the cabinet power control panel.

Context
The system can be powered on using either one of the following methods: l l Power on the system using the power switch of the server. Power on the system using the Integrated Management Module (IMM). For IP address, initial user name and password of the IMM network port, see Planning Device Host Name and IP Address and Planning Users.

Procedure
l Power on the system using the power switch of the server. 1. Turn on the power switch of the server to start the server. Figure 2-1 shows the operation information pane. Figure 2-1 Operation Information pane

Power switch/ Power indicator

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

2 Powering On/Off the System

2. l

Check the power indicator status of the server after power on, and steady green indicates the server is running properly. Connect the PC and the M2000 server through the local area network (LAN) switch. a. b. c. Connect the system management network port on the M2000 server to the network interface on the LAN switch using straight-through cables. Connect the PC to the network interface on the LAN Switch using straightthrough cables. Set the IP address of the PC on the same network segment (192.168.70.xx for example) as the IP address of the system management network port on the M2000 server. For example, configure the network card of the PC as follows: Set IP address to 192.168.70.35. Set Subnet mask to 255.255.255.0. Leave Default gateway, Preferred DNS server and Alternate DNS server.

Power on the system using IMM. 1.

2.

Open Internet Explorer, type http://192.168.70.125 in the URL of your Internet Explorer and then press Enter to access the IMM login page.
NOTE

http://192.168.70.125 is an example and must be replaced by the actual IP address of the IMM.

3. 4. 5. 6. 7. 8.

Type the initial user name USERID and password PASSW0RD. 0 in PASSW0RD is the digit 0, not the letter O. Click Login to access the Welcome page. Click Continue to access the IMM home page. In the navigation tree, choose System > Tasks > Remote Control. In the displayed window, select the Use the ActiveX Client with Microsoft Internet Explorer, and then click Start Remote Control in Multi-User Mode. In the displayed window, choose Tools > Power > On. In the displayed window, click Yes. After the system is powered on, a power-on page is displayed, as shown in Figure 2-2.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

2 Powering On/Off the System

Figure 2-2 Startup page

----End

2.2 Powering off the System Securely


This section describes the procedure for powering off the M2000 hardware devices and related notes when the IBM x3850 X5 functions as the M2000 server.

Prerequisites
Log in to the server as user root through Security Shell Protocol (SSH).

Context
To securely power off the system, disable the M2000 service, the database interception and database services, and then the server in order.

Procedure
Step 1 Stop the M2000 service. Check whether the M2000 is started by referring to 6.2 Viewing the Running Status of M2000 Services (SUSE). Stop the M2000 services if they are running. For how to stop the M2000 services, see 6.4 Stopping the M2000 Services (SUSE). If M2000 service is stopped, run the following command to switch to user root:
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5

M2000 Administrator Guide (x3850, SUSE10)

2 Powering On/Off the System

> su - root Step 2 Disable the database interception and database services. 1. Run the following commands to check the status of the database interception. $ su - oracle > lsnrctl status When the following information is displayed, the database interception is in running status:
Service "+ASM" has 1 instance(s). Instance "+ASM", status READY, has 1 handler(s) for this service... Service "+ASM_XPT" has 1 instance(s). Instance "+ASM", status READY, has 1 handler(s) for this service... Service "ossdb" has 1 instance(s). Instance "ossdb", status READY, has 1 handler(s) for this service... Service "ossdbXDB" has 1 instance(s). Instance "ossdb", status READY, has 1 handler(s) for this service... Service "ossdb_XPT" has 1 instance(s). Instance "ossdb", status READY, has 1 handler(s) for this service... The command completed successfully

2.

Run the following commands to disable the database interception. > lsnrctl stop If the following information has been displayed, the database interception is disabled successfully. Otherwise, the database interception is not disabled. In this case, contact Huawei technical support.
The command completed successfully

3.

Run the following command to disable the Oracle database services. a. Run the following command to stop the ORACLE instance. > sqlplus / as SYSDBA SQL> shutdown immediate If the following information is displayed, the ORACLE instance has been disabled. Otherwise, the ORACLE instance is not stopped. In this case, contact Huawei technical support.
Database closed. Database dismounted. ORACLE instance shut down.

SQL> exit b. Run the following command to stop the ASM instance. > ORACLE_SID=+ASM > sqlplus / as SYSDBA SQL> shutdown immediate If the following information is displayed, the ASM instance has been disabled. Otherwise, the ASM instance is not stopped. In this case, contact Huawei technical support.
ASM diskgroups dismounted ASM instance shutdown

SQL> exit 4. Run the following command to exit user oracle.


Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6

Issue Draft A (2012-02-27)

M2000 Administrator Guide (x3850, SUSE10)

2 Powering On/Off the System

> exit Step 3 Run the following commands to disable the server: $ sync; sync; sync; sync; sync; sync $ shutdown -h now It takes about 5 minutes to disable the server. If the power indicator on the operator information pane turns from steady green to blinking green, the system is disabled. Then, go to Step 4. Figure 2-3 Operator information pane

Step 4 Power off other devices and the cabinet. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

3 Configuring the Parameters of the M2000 Server

Configuring the Parameters of the M2000 Server

About This Chapter


This describes how to set the parameters of the M2000 server. 3.1 Changing the IP Address of the M2000 Server This section describes how to change the IP addresses of the M2000 servers to ensure that the IP addresses of the servers meet the requirements.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

M2000 Administrator Guide (x3850, SUSE10)

3 Configuring the Parameters of the M2000 Server

3.1 Changing the IP Address of the M2000 Server


This section describes how to change the IP addresses of the M2000 servers to ensure that the IP addresses of the servers meet the requirements.

Prerequisites
l l The M2000 server application is installed. You have logged in to the server as user root.

Context
l l l When you are changing the IP addresses of the M2000 servers, the performance data and alarm data of the managed NEs cannot be processed. After you change the IP addresses of the servers, the M2000 collects performance data and alarm data again through automatic synchronization and then processes the data. If the IP addresses of the M2000 servers are recorded in the NE database, changing the IP address of an M2000 server leads to the disconnection between the M2000 server and the NEs. When changing the IP addresses of the M2000 servers, you need to notify the NE maintenance engineers and ask them to modify relevant plans and update the IP addresses of the M2000 servers recorded in the NE database.

Procedure
Step 1 Check the IP address of the server. $ ifconfig -a If the IP address of the server is incorrect, perform the following steps: Step 2 Check whether the new IP address is already used. This part takes change the old IP address 10.10.10.10 to the new IP address 192.168.8.12 as an example. $ ping 192.168.8.12 l If the new IP address can be pinged, you can infer that the new IP address are occupied and you need to use other new IP address. l If the new IP address cannot be pinged, you can infer that the new IP address is idle and you can use the new IP address. Step 3 Check whether the M2000 is started by referring to Viewing the Running Status of M2000 Services. Stop the M2000 services if they are running. For details on how to stop the M2000, see 6.4 Stopping the M2000 Services (SUSE). Step 4 Check whether the Oracle is started by referring to 7.2 Checking Oracle Services. If the Oracle is not started, start it by referring to 7.3 Starting Oracle Service. Step 5 Perform the following operations to change the IP addresses of the M2000 servers. 1. Run the modify.sh script. $ . /opt/oss/server/svc_profile.sh $ cd /opt/oss/server/rancn/tools/modifytool
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9

M2000 Administrator Guide (x3850, SUSE10)

3 Configuring the Parameters of the M2000 Server

$ ./modify.sh 2. When the main menu is displayed, choose 1--IP.


-----------------------------------------------------------------Welcome to use Modify tool Modify Tool (2.0.0) ----------------------------------------------------------------------------------------------------------------------------------Please select a(n) operator type 1--IP 2--Database password 3--Password of ftpuser R--Return Q--Quit -----------------------------------------------------------------Please make a choice[1-3]:

3.

Change the IP address, subnet mask, and default route according to system outputs.
-----------------------------------------------------------------Note: -- Enter key f/F to finish ip input old-new ip pairs -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the old ip[default 10.121.71.138]: Please input the new ip[default 10.121.71.138]: 10.121.71.181 Please input the old ip[default 10.121.71.182]: -----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the database superuser's password: Please input the old mask number[default 255.255.255.0]: Please input the new mask number[default 255.255.255.0]: Please input the old router ip address[default 10.121.71.1]: Please input the new router ip address[default 10.121.71.1]:
NOTE

l If you need to change multiple IP addresses by running the modify.sh script, type all previous addresses to be changed and their new values here. l You can press Enter to use the default value in the system output. l The script displays the IP addresses that are already configured in the system. If you need not change a certain IP address, press Enter to proceed with the next step. l You can type p/P to return to the function menu of the modify.sh script. Then, you are prompted to perform operations such as changing the IP address and changing user password. l You can type q/Q to exit the modify.sh script. l When the system prompts you to type the previous IP addresses, type f/F to finish typing IP addresses and proceed with the next step.

4.

When the system displays the following prompt, type Y, and then press Enter:
Are you sure to continue? Y--Yes. Q--Quit. R--Re-input P--Return pre-step Please make a choice[Y/Q/R/P]: Y
NOTE

l You can type Q to exit the script without performing any operations. l You can type R to return to the previous step to reconfigure relevant parameters. l You can type P to return to the function menu of the modify.sh script. Then, you are prompted to perform operations such as changing the IP address and user password. l Running the modify.sh script to change the server IP addresses takes about three minutes. Please wait.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10

M2000 Administrator Guide (x3850, SUSE10)

3 Configuring the Parameters of the M2000 Server

5.

When the system displays the following information, you can infer that the change is successful.
-----------------------------------------------------------------Operator compelete!

If the system output contains failed, you can infer that the change fails. Contact Huawei technical support engineers for assistance. 6. When the system displays the function menu again, type q to exit. Step 6 Run the following commands to restart the server: $ sync; sync; sync; sync; sync; sync $ shutdown -y -g0 -i6 After the server is restarted, both the Oracle and M2000 services are automatically restarted. Step 7 Log in to the server by using the new IP address as user root, and then check the status of the Oracle and M2000 services.
NOTE

If the login fails or the Oracle and M2000 services are abnormal after the server is restarted, contact Huawei for technical support.

l For details about how to view the Oracle service, see 7.2 Checking Oracle Services. l For details about how to check the status of the M2000 services, see Viewing the Running Status of M2000 Services. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

11

M2000 Administrator Guide (x3850, SUSE10)

4 Configuring the NTP Service

4
About This Chapter
Context
CAUTION

Configuring the NTP Service

This section describes how to set the M2000 server as an NTP client or an intermediate-layer NTP server.

l If you do not need to configure the NTP service on the M2000 server at the site, ignore this section and proceed to the follow-up sections. l If you need to configure the NTP service on the M2000 server at the site, but the IP address of the upper-layer NTP server has not been obtained at the commissioning stage, ignore this section and proceed to the follow-up sections. 4.1 Methods for Configuring the NTP Service on the M2000 Server This section describes the methods for configuring the Network Time Protocol (NTP) service on the M2000 server. 4.2 Setting the M2000 Server as the NTP Client This section describes how to set the M2000 server as an NTP client to synchronize time with an NTP server. 4.3 Setting the M2000 Server as an Intermediate-Layer NTP Server This section describes how to set the M2000 server as an intermediate-layer NTP server. An intermediate-layer NTP server synchronizes time with the upper-layer NTP server, and provides time reference for NTP clients. 4.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE) This describes how to check the running status of the NTP service on the M2000 server.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

12

M2000 Administrator Guide (x3850, SUSE10)

4 Configuring the NTP Service

4.1 Methods for Configuring the NTP Service on the M2000 Server
This section describes the methods for configuring the Network Time Protocol (NTP) service on the M2000 server. You can configure the M2000 server as an NTP client or an intermediate-layer NTP server. Table 4-2 describes the advantages and disadvantages of each method. Table 4-1 Methods for configuring the NTP service Method Set the M2000 server as an NTP client. Set the M2000 server as an intermediatelayer NTP server. Reference 4.2 Setting the M2000 Server as the NTP Client 4.3 Setting the M2000 Server as an Intermediate-Layer NTP Server

Table 4-2 Advantages and disadvantages of each method Metho d Set the M2000 server as an NTP client. Reliability Higher reliability because an independent intermediatelayer NTP server is deployed independently Security Higher security of the time synchronization network because the M2000 server serves as an NTP client and synchronizes time with the intermediatelayer NTP server Time synchronization failed when the M2000 server becomes faulty System Resource Usage Less system resources required because the M2000 server synchronizes time with the upperlayer NTP server but does not provide time reference for NTP clients More system resources required because the M2000 server synchronizes time with the upperlayer NTP server and provides time reference for NTP clients Cost Expensive because you have to deploy an independent intermediatelayer NTP server

Set the M2000 server as an interme diatelayer NTP server.

Weaker reliability because the M2000 server also performs maintenance, upgrade, and backup operations frequently

Cost effective because the M2000 server also serves as an intermediatelayer NTP server

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13

M2000 Administrator Guide (x3850, SUSE10)

4 Configuring the NTP Service

4.2 Setting the M2000 Server as the NTP Client


This section describes how to set the M2000 server as an NTP client to synchronize time with an NTP server.

Prerequisites
l l l l The time zone of the M2000 server are set correct. You have obtained the IP address of the NTP server. The network between the M2000 server and the NTP server is running properly. You have logged in to the server as user root in Secure Shell (SSH) mode.

Procedure
Step 1 Run the following command to check the time zone of the server: # date - R If the time zone of the M2000 server and the NTP server is different, correct it by referring to Changing the Time Zone and Time of the M2000 Server (SUSE). Step 2 If the M2000 services are running, stop them. 1. 2. Check the status of the M2000 services. For details, see How Do I Check the Status of the M2000 Services?. Stop M2000 services. For details, see How to Stop M2000 Services. Step 3 If the Oracle services are running, stop them. 1. 2. Check the status of the Oracle services. For details, see 7.2 Checking Oracle Services. Stop Oracle services. For details, see How Do I Stop the Oracle Services. Step 4 If M2000 or Oracle service is stopped, run the following command to switch to user root > su - root Step 5 Run the following command to synchronize the clock time with the upper-level server. # /usr/sbin/ntpdate IP address of the NTP server Step 6 Run the following command to open the yast interface: # yast Step 7 On the YaST Control Center interface, use and to select Network Services. Step 8 On the YaST Control Center interface, use Tab, , and to select NTP Configuration, and then press Enter. Step 9 Use Tab, , and to select During Boot on Automatically Start NTP Daemon. Press Enter for confirmation.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14

M2000 Administrator Guide (x3850, SUSE10)


NOTE

4 Configuring the NTP Service

When the Warning dialog box is displayed, use the Tab key to select Continue and then press Enter. This warning does not affect the setting of NTP server.

Step 10 On the NTP Server Configuration interface, use Tab to enter the IP address of the NTP server in Address. Use the Tab key to select Test to check whether the input IP address is valid, as shown in Figure 4-1. l If the message Server is unreachable or does not respond properly. is displayed, the input IP address is invalid. Check whether the IP address of the top-layer NTP server is correct and the network connections. Perform this step again after the problem is solved. l If the message Server is reachable and responds properly. is displayed, the input IP address is valid. Figure 4-1 Configuring the NTP client

Step 11 Use Tab to select Finish for completing the configuration of the NTP server. Step 12 Use Tab to select Quit to exit the system. Step 13 Run the following command to check the status of the NTP service on the M2000 server: # /usr/sbin/ntpq -p
remote refid st t when poll reach delay offset jitter ============================================================================== *192.168.8.12 .LCL. 1 u 29 64 177 0.240 0.093 1.222 LOCAL(0) .LOCL. 5 l 26 64 177 0.000 0.000 0.001

l The value of remote indicates the IP address and status of an NTP server. In the preceding output, 192.168.8.12 indicates the IP address of the top-layer NTP server, and * indicates that the top-layer NTP server is in normal state. After the following information is displayed, wait 5 minutes and * is displayed. l The value of st indicates the layer of an NTP server in the time synchronization network. In the preceding output, the IP address 192.168.8.12 is on layer 1. Step 14 Run the following command to check the system date and time. # date - R If the system date and time are incorrect, contact Huawei technical support engineers for assistance. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15

M2000 Administrator Guide (x3850, SUSE10)

4 Configuring the NTP Service

4.3 Setting the M2000 Server as an Intermediate-Layer NTP Server


This section describes how to set the M2000 server as an intermediate-layer NTP server. An intermediate-layer NTP server synchronizes time with the upper-layer NTP server, and provides time reference for NTP clients.

Prerequisites
l l l l The top-layer NTP server has been configured, and the IP address of the top-layer NTP server has been obtained. The network between the M2000 server and the NTP server is running properly. The time zone of the M2000 server are correct. You have logged in to the server as user root in Secure Shell (SSH) mode.

Context
The NTP server for the M2000 server uses the NTP. A server running on the Windows operating system uses the SNTP. Therefore, it cannot serve as the NTP server for the M2000 server.

Procedure
Step 1 Run the following command to check the time zone of the server: # date - R If the time zone of the M2000 server and the NTP server is different, correct it by referring to Changing the Time Zone and Time of the M2000 Server (SUSE). Step 2 If the M2000 services are running, stop them. 1. 2. Check the status of the M2000 services. For details, see How Do I Check the Status of the M2000 Services?. Stop M2000 services. For details, see How to Stop M2000 Services. Step 3 If the Oracle services are running, stop them. 1. 2. Check the status of the Oracle services. For details, see 7.2 Checking Oracle Services. Stop Oracle services. For details, see How Do I Stop the Oracle Services. Step 4 If M2000 or Oracle service is stopped, run the following command to switch to user root > su - root Step 5 Run the following commands to back up the ntp.conf file: # rcntp stop If the following information is displayed, ignore it and continue to run the following command:
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16

M2000 Administrator Guide (x3850, SUSE10)


Shutting down network time protocol daemon (NTPD) umount: /var/lib/ntp/proc: not mounted

4 Configuring the NTP Service


done

# cd /etc # cp -p ntp.conf bak.ntp.conf Step 6 Run the following command to synchronize the clock time with the upper-level server. # /usr/sbin/ntpdate IP address of the NTP server Step 7 Switch to the YaST Control Center window, and then configure the M2000 server as an intermediate-layer NTP server. 1. Run the following command to switch to the YaST Control Center window: # yast 2. 3. 4. In the YaST Control Center window, use or to choose Network Services. In the YaST Control Center window, use Tab and or to choose NTP Configuration, and then press Enter. Use Tab and or to choose During Boot under Automatically Start NTP Daemon, and then press Enter.
NOTE

If the Warning dialog box is displayed, press Tab to choose Continue, and then press Enter. This warning does not affect the settings of the intermediate-layer NTP server.

5. 6. 7. 8. 9.

Use the Tab key to select Advanced Configuration, and then press Enter. Use the Tab key to select Undisciplined Local Clock (LOCAL), and use the Tab to select Delete, and then press Enter. In the displayed prompt dialog box, use the Tab key to select Yes, and then press Enter. Use the Tab key to select Add, and then press Enter. Use the Tab key to select Server, and then press Enter. If Server is selected, skip this step.

10. Use the Tab key to select Next, and then press Enter. 11. Use the Tab key to select Address, and then enter the IP address of the highest-level NTP server in Address. 12. Use the Tab key to select Test to check whether the entered IP address is available. l If the system displays "Server is unreachable or does not respond properly. ", it indicates that the entered IP address is unavailable. In such a case, you need to check whether the IP address of the NTP server is correct and whether network communication is normal. After troubleshooting, perform this step again. l If the system displays "Server is reachable and responds properly. ", it indicates that the entered IP address is available. 13. Use the Tab key to select Use for Initial Synchronization, and then press Enter. 14. Use the Tab key to enter prefer in Options.
NOTE

prefer indicates that the time of the NTP server is synchronized preferentially. If there are multiple NTP servers, you can set only one of them to prefer.

15. Use the Tab key to select OK, and then press Enter.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 17

M2000 Administrator Guide (x3850, SUSE10)


NOTE

4 Configuring the NTP Service

If there are multiple NTP servers, repeat Step 7.8 through Step 7.15 to set the IP addresses of other NTP servers.

16. Press Tab to choose Finish, and then press Enter. 17. Press Tab to choose Quit, and then press Enter. Step 8 Run the following command to check the status of the NTP service on the M2000 server: # /usr/sbin/ntpq -p
remote refid st t when poll reach delay offset jitter ============================================================================== *192.168.8.12 .LCL. 1 u 29 64 177 0.240 0.093 1.222 LOCAL(0) .LOCL. 5 l 26 64 177 0.000 0.000 0.001

l The value of remote indicates the IP address and status of an NTP server. In the preceding output, 192.168.8.12 indicates the IP address of the top-layer NTP server, and * indicates that the top-layer NTP server is in normal state. After the following information is displayed, wait 5 minutes and * is displayed. l The value of st indicates the layer of an NTP server in the time synchronization network. In the preceding output, the IP address 192.168.8.12 is on layer 1. Step 9 Run the following command to check the time synchronization path from the M2000 server to the top-layer NTP server: # /usr/sbin/ntptrace
localhost: stratum 6, offset 0.000000, synch distance 0.950193 192.168.8.12: stratum 1, offset 0.000000, synch distance 0.010010, refid 'LCL

The localhost line and the next line indicate the path from the M2000 server (intermediate-layer NTP server) to the top-layer NTP server. The system can track the entire NTP synchronization path from the M2000 server (intermediate-layer NTP server) to the top-layer NTP server. For example, localhost: stratum 6 in the preceding output indicates that the M2000 server is on layer 6, and 192.168.8.12: stratum 1 indicates that 192.168.8.12 is on layer 1. Step 10 Run the following command to check the system date and time. # date - R If the system date and time are incorrect, contact Huawei technical support engineers for assistance. ----End

Follow-up Procedure
After the server is set as an intermediate NTP server, set the NEs as NTP clients. For details about how set an NE as an NTP client, see the user guide of the corresponding NE type.

4.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE)
This describes how to check the running status of the NTP service on the M2000 server.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18

M2000 Administrator Guide (x3850, SUSE10)

4 Configuring the NTP Service

Prerequisites
You have logged in to the server as user root.

Procedure
Step 1 Run the following command to check the status of NTP: # ps -ef|grep ntp|grep -v grep
ntp 32038 1 0 21:34 ? 00:00:00 /usr/sbin/ntpd -p /var/lib/ntp/var/run/ntp/ntpd.pid -u ntp -i /var/lib/ntp

If the command output contains ntpd, you can infer that the NTP service is running on the M2000 server. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

5
About This Chapter

Managing M2000 Users

This describes how to manage OS users and DB users of the M2000 system. 5.1 User Type This section describes information about user OS and user DB involved in the operation of the M2000. User OS include user root, ossuser, ftpuser, and oracle. User DB includes user system and sys. 5.2 Changing the Password of User root This describes how to change the password of user root. In the M2000 HA system, the password of user root on the two nodes must be consistent. Thus, you must change the password of user root on the active and standby nodes separately to ensure the password consistency. 5.3 Changing the Password of User ossuser This describes how to change the password of user ossuser when you log in to the system as user root. In the M2000 HA system, the password of user ossuser on the two nodes must be consistent. Thus, you must change the password of user ossuser on the active and standby nodes separately to ensure the password consistency. 5.4 Changing the Password of User ftpuser This section describes how to change the password of user ftpuser. 5.5 Changing the Password of User oracle This describes how to change the password of user oracle when you log in to the M2000 database as user root. For an HA system, the password of user oracle on the two nodes must be consistent. Therefore, you need to change the password of user oracle on the active and standby nodes respectively to ensure the password consistency. 5.6 Changing the Password of User DB This section describes how to change the passwords of user DB.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

5.1 User Type


This section describes information about user OS and user DB involved in the operation of the M2000. User OS include user root, ossuser, ftpuser, and oracle. User DB includes user system and sys. Table 5-1 and Table 5-2 describe user OS and user DB for the M2000.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

Table 5-1 User OS User Name Default Password Usag e Authorit y Us er Gr ou p Sh ell Re sol uti on Pro gra m / bin/ bas h Di rec tor y

User OS

root

root

User root is the super user of the syste m. User root is autho rized to contr ol all resou rces, create other user accou nts, assig n autho rity to other users, and perfor m all syste m opera tions.

User root has the highest authority of the system. User root is authorize d to install and uninstall M2000 server applicatio ns and to start and stop M2000 services.

oth er, bin , sys , ad m, uuc p, mai l, tty, lp, nuu cp, dae mo n, and use r.ro ot

/ roo t

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

22

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

User Name

Default Password

Usag e

Authorit y

Us er Gr ou p

Sh ell Re sol uti on Pro gra m / bin/ bas h

Di rec tor y

ossuser

Changeme_123

User ossus er is respo nsible for the opera tion and maint enanc e of the M200 0.

User ossuser is authorize d to access the database and perform operation and maintena nce. User ossuser is not allowed to install or uninstall M2000 server applicatio ns.

roo t, sys , oss gro up, dba , and oin stal l

/ exp ort/ ho me/ oss use r

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

23

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

User Name

Default Password

Usag e

Authorit y

Us er Gr ou p

Sh ell Re sol uti on Pro gra m / bin/ bas h

Di rec tor y

oracle

Changeme_123

User oracl e is used to install the Oracl e datab ase. User oracl e is create d befor e the datab ase is install ed. ftpus er is a user to uploa d files to the server and down load files from the server .

User oracle is authorize d to access the database and perform operation s over the Oracle database.

oin stal l, dba , and oss gro up

/ opt / ora cle

ftpuser

Changeme_123

User ftpuser is authorize d to perform software managem ent and file transfer for NEs.

oss gro up, dial out , vid eo

/ bin/ bas h

/ exp ort/ ho me/ sys m

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

Table 5-2 User DB User Name Default Passwor d Changeme _123 Usage Authority

system

User system is the administrator of the Oracle database. User system is responsible for the management, upgrade, and maintenance of the Oracle database, and is used to install the M2000 server applications. User sys is the super user of the Oracle database. User sys is responsible for the management and operation of the Oracle system, and is used to restore the Oracle database applications.

User system has the highest authority of the database.

sys

Changeme _123

User sys is the super user of the database.

5.2 Changing the Password of User root


This describes how to change the password of user root. In the M2000 HA system, the password of user root on the two nodes must be consistent. Thus, you must change the password of user root on the active and standby nodes separately to ensure the password consistency.

Prerequisites
l l The old password of user root is available. The new password of user root is available.

Context
The password can contain 8 to 30 characters, including digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and special characters @%-=_.]{}. To improve password security, you are advised to use the following password policies: l l l l l The password contains at least one uppercase letter. The password contains at least one lowercase letter. The password contains at least one digit. The password contains at least one special character. The password does not contain the user name.
NOTE

The password must also meet the requirements of the operating system. For details about the password policies of the operating system, see the DVD-ROM delivered with the operating system.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

Procedure
Step 1 Log in as user root, and then enter the old password of user root. Step 2 Change the password. # passwd root
Changing password for root.

New password:new password Reenter New Password:new password


Password changed.

----End

5.3 Changing the Password of User ossuser


This describes how to change the password of user ossuser when you log in to the system as user root. In the M2000 HA system, the password of user ossuser on the two nodes must be consistent. Thus, you must change the password of user ossuser on the active and standby nodes separately to ensure the password consistency.

Prerequisites
l l The new password for ossuser is available. You have logged in to the UNIX as user root.

Context
The password can contain 8 to 30 characters, including digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and special characters @%-=_.]{}. To improve password security, you are advised to use the following password policies: l l l l l The password contains at least one uppercase letter. The password contains at least one lowercase letter. The password contains at least one digit. The password contains at least one special character. The password does not contain the user name.
NOTE

The password must also meet the requirements of the operating system. For details about the password policies of the operating system, see the DVD-ROM delivered with the operating system.

Procedure
Step 1 Run the following command to change the password: # passwd ossuser
Changing password for ossuser.

New password:new password Reenter New Password:new password


Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 26

M2000 Administrator Guide (x3850, SUSE10)


Password changed.

5 Managing M2000 Users

----End

5.4 Changing the Password of User ftpuser


This section describes how to change the password of user ftpuser.

Prerequisites
l l The new password of user ftpuser is available. You have logged in to the server as user root by using the SSH.

Procedure
Step 1 Check whether the M2000 is started by referring to 6.2 Viewing the Running Status of M2000 Services (SUSE). Stop the M2000 services if they are running. For details on how to stop the M2000, see 6.4 Stopping the M2000 Services (SUSE). Step 2 Check whether the Oracle service is running. For details, see 7.2 Checking Oracle Services. If the Oracle service is already stopped, start the Oracle. For details about how to start the Oracle, see 7.3 Starting Oracle Service. Step 3 Run the following commands to change the password of user ftpuser. $ . /opt/oss/server/svc_profile.sh $ cd /opt/oss/server/rancn/tools/modifytool $ ./modify.sh The following message is displayed:
-----------------------------------------------------------------Welcome to use Modify tool Modify Tool (2.0.0) ----------------------------------------------------------------------------------------------------------------------------------Please select a(n) operator type 1--IP 2--Database password 3--Password of ftpuser R--Return Q--Quit -----------------------------------------------------------------Please make a choice[1-3]:

Step 4 Type 3, and then type the new password of user ftpuser at the following prompt. Type the new password again, and then press Enter.
-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the new ftpuser password: Please Re-enter the password: The system type is: Single The operator type is: Password of ftpuser ------------------------------------------------------------------

Step 5 At the following prompt, enter Y for confirmation.


Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 27

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

Are you sure to continue? Y--Yes. Q--Quit. R--Re-input P--Return pre-step Please make a choice[Y/Q/R/P]:Y ------------------------------------------------------------------

When the system displays the following information, you can infer that the change is successful.
-----------------------------------------------------------------modify OS ftpuser success svc_cfgtool modpass ftp success -----------------------------------------------------------------Process imap.iors success Process imap.iors.* success -----------------------------------------------------------------Operator compelete! ------------------------------------------------------------------

Step 6 After the operation is complete, select Q to exit. Step 7 For details on how to restart the M2000 service, refer to 6.3 Starting the M2000 Server (SUSE). ----End

5.5 Changing the Password of User oracle


This describes how to change the password of user oracle when you log in to the M2000 database as user root. For an HA system, the password of user oracle on the two nodes must be consistent. Therefore, you need to change the password of user oracle on the active and standby nodes respectively to ensure the password consistency.

Prerequisites
l l The new password of the operating system user oracle is available. You have logged in to the server as user root.

Context
The password can contain 8 to 30 characters, including digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and special characters @%-=_.]{}. To improve password security, you are advised to use the following password policies: l l l l l The password contains at least one uppercase letter. The password contains at least one lowercase letter. The password contains at least one digit. The password contains at least one special character. The password does not contain the user name.
NOTE

The password must also meet the requirements of the operating system. For details about the password policies of the operating system, see the DVD-ROM delivered with the operating system.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

28

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

Procedure
Step 1 Run the following command to change the password of user Oracle: # passwd oracle
Changing password for oracle.

New password:new password Reenter New Password:new password


Password changed.

----End

5.6 Changing the Password of User DB


This section describes how to change the passwords of user DB.

Prerequisites
l l The new password of user DB is available. You have logged in to the server as user root by using the SSH.

Procedure
Step 1 Check whether the M2000 is started by referring to 6.2 Viewing the Running Status of M2000 Services (SUSE). If any M2000 service is running, stop it by referring to 6.4 Stopping the M2000 Services (SUSE). Step 2 Check whether the Oracle is started by referring to 7.2 Checking Oracle Services. If any Oracle service stops, start it by referring to 7.3 Starting Oracle Service. Step 3 Perform the following operations to change the password of user system: 1. Run the modify script. $ . /opt/oss/server/svc_profile.sh $ cd /opt/oss/server/rancn/tools/modifytool $ ./modify.sh Choose 2--Database password after the following message is displayed:
-----------------------------------------------------------------Welcome to use Modify tool Modify Tool (2.0.0) ----------------------------------------------------------------------------------------------------------------------------------Please select a(n) operator type 1--IP 2--Database password 3--Password of ftpuser R--Return Q--Quit -----------------------------------------------------------------Please make a choice[1-3]:

2.

Based on the displayed messages, enter the name of the Oracle database server and the old and new passwords of user system. Press Enter.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29

Issue Draft A (2012-02-27)

M2000 Administrator Guide (x3850, SUSE10)

5 Managing M2000 Users

-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the database server name[default ossdb]: Please input the old database superuser's password: Please input the new database superuser's password: Please Re-enter the password:
NOTE

l Press Enter to use the default value prompted by the system. l Enter p or P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. l Enter q or Q to exit the modify script. l You need to enter the new password of user system twice.

3.

Type Y and press Enter after the following messages are displayed:
Are you sure to continue? Y--Yes. Q--Quit. R--Re-input P--Return pre-step Please make a choice[Y/Q/R/P]: Y
NOTE

l Enter Q to exit the script without performing any operations. l Enter R to return to the previous step to reconfigure relevant parameters. l Enter P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. l Modifying the password of user system by running the modify script takes about 12 minutes.

4.

The password is successfully changed if the following message is displayed:


-----------------------------------------------------------------Operator compelete!

5.

Enter q to exit the modify script if the function menu is displayed again.

Step 4 Start the M2000 service, see 6.3 Starting the M2000 Server (SUSE). ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

30

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Managing the M2000 Processes and Services

About This Chapter


This describes how to manage the M2000 processes so that the processes and services on the M2000 server can function properly. 6.1 Introduction to M2000 Processes and Services When the M2000 is running, the M2000 server automatically starts the processes related to the M2000 system. Each process provides different services and functions. In the ATAE cluster system, the master node starts all the M2000 processes, the slave nodes start some processes, whereas the standby node does not run any M2000 process. 6.2 Viewing the Running Status of M2000 Services (SUSE) This describes how to view the status of M2000 services on the M2000 server. This operation requires only few system resources and does not affect system performance. 6.3 Starting the M2000 Server (SUSE) After you run the start_svc command, all the M2000 services are started. If an M2000 service is already started, the system does not handle the service. Actually, the system starts only the inactive services. 6.4 Stopping the M2000 Services (SUSE) This describes how to stop the M2000 services. After the M2000 services are stopped, the M2000 processes are stopped. In this situation, NE performance data and alarm data cannot be processed. After the services are resumed, the M2000 updates the data with the NEs and processes the data.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

31

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

6.1 Introduction to M2000 Processes and Services


When the M2000 is running, the M2000 server automatically starts the processes related to the M2000 system. Each process provides different services and functions. In the ATAE cluster system, the master node starts all the M2000 processes, the slave nodes start some processes, whereas the standby node does not run any M2000 process.

6.1.1 3rdTool_agent Process


This section describes the 3rdToolService service and dependent services. The 3rdTool_agent process provides the 3rdToolService service. The 3rdToolService service provides an interface for the third-party tools to access the data center. Required services: ScriptServer

6.1.2 adn_agent Process


This section describes the services and functions provided by the adn_agent process. The adn_agent process provides the ADNService service. The ADNService service supports the NodeB plug-and-play function. It provides various functions for newly constructed NodeBs, such as remote automatic activation and automatic fault detection. This helps engineers quickly deploy NodeBs. In the ATAE cluster system, the adn_agent process is deployed on the master node. You can disable the service when it is not required. Required services: none

6.1.3 adss_agent Process


This section describes the services and functions provided by the adss_agent process. The adss_agent process provides the AdvancedSwitchService service. The AdvancedSwitchService service authenticates the MOI resources to enhance the security of the operations on the NEs, and deepen the security level hiberarchy. In the ATAE cluster system, the adss_agent process is deployed on the master node. During the operation of the M2000, ensure that this service is running properly. Required services: none

6.1.4 antenna_agent Process


This section describes the services and functions provided by the antenna_agent process. The antenna_agent process provides the AntennaTune service. The AntennaTune service provides the functions of managing NodeB antennas and locating the faults related to GBSS antennas.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 32

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Required service: EAMService.

6.1.5 ce_agent Process


This section describes the services and functions provided by the ce_agent process. The ce_agent process provides the ConfigExport service. The ConfigExport service provides a transparent channel which enables the northbound NMS to directly obtain configuration data and set NE configurations from the GBSS. If this function is required, you must ensure that the service runs normally. Required services: none.

6.1.6 cmdc_agent Process


This section describes the CmDcService service and dependent services. CmDcService is provided by the cmdc_agent process. The cmdc_agent process provides the CmDcService service. The CmDcService service provides the functions such as data access interface, synchronization management, and session management. In the ATAE cluster system, you can distribute this process to different slave nodes. Required services: TopoAdapterService

6.1.7 cmengine_agent Process


This section describes the services and functions provided by the cmengine_agent process. The cmserver_agent process provides the CMEngine service. CMEngine manages the configuration of the network manager. Configuration management is independent of NEs or managed objects. In the ATAE cluster system, you can deploy this process on different slave nodes. When the M2000 is running, ensure that this service functions properly. Required services: TopoAdapterService.

6.1.8 cmeserver_agent Process


This section describes the services and functions provided by the cmeserver_agent process. The cmeserver_agent process provides the CmeServer service. The cmeserver_agent service provides the function of quickly configuring NEs. In the ATAE cluster system, you can deploy this process on the master node and several slave nodes. You can disable the service when it is not required. Required service: TopoAdapterService.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 33

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

6.1.9 cmexp_agent Process


This section describes the service and functions provided by the cmexp_agent process. The cmexp_agent process provides the CMExport service. The CMExport service provides the functions of exporting configuration files and exporting the configuration database. Through the CMExport service, you can set the NE whose configuration data is to be exported, set the save path and file format of the exported data, and export the NE configuration data by using the Management Information Tree (MIT). In the ATAE cluster system, this process is deployed on the primary node. To enable the functions of exporting configuration files and exporting the northbound database, you need to ensure that this service is running normally. Dependent service: LicenseService.

6.1.10 cmserver_agent Process


This section describes the services and functions provided by the process cmserver_agent. The cmserver_agent process provides the CMServer service. CMserver configures the managed objects of the network manager. Configuration management is independent of NEs or managed objects. The CMServer provides channels for issuing MML commands and helps to receive the supplementary messages reported automatically by NEs. The CMServer provides the function of managing object groups and enables the M2000 to automatically and remotely commission the NodeB upgrade. In the ATAE cluster system, you can distribute the cmserver_agent process to different slave nodes. When the M2000 is running, ensure that this service functions properly. Required services: TopoAdapterService

6.1.11 corba_agent Process


This section describes the services and functions provided by the corba_agent process. The corba_agent process provides the CorbaService service. The CorbaService provides the NBI on which the TMF 814 CORBA protocol runs. Required services: LicenseService, LogService, SecurityService.

6.1.12 cpm_agent Process


This section describes the services and functions provided by the cpm_agent process. The cpm_agent process provides the CPMService service, that is, the pool configuration management service. The Pool configuration management service provides users with the following functions:
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 34

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

l l l l l l l l

Creating a pool Checking pool alarms Measuring the performance of a pool Monitoring the load of a pool in real time Displaying the pool topology Setting pool parameters Checking the NE data in a pool Checking the MSC Server or MSCe of a specific user

In the ATAE cluster system, you can distribute this process to different slave nodes. Required services: none

6.1.13 dam Process


This section describes the services and functions provided by the dam process. This process provides the function of creating SNMP equipment. Required services: None.

6.1.14 datacollectorsvr Process


This section describes the services and functions provided by the datacollectorsvr process. The Datacollector is mainly used for collecting the complete and correct fault data in case of NE failure and helps to locate faults quickly Required services: None.

6.1.15 DCServer Process


This section describes the services and functions provided by the DCServer process. This process provides the function of NE software management and disaster recovery management. The detailed functions are NE software upgrade, patch installation, data backup and recovery for disaster recovery, and plug-andplay automatic upgrade of case-shaped equipment. Required services: None.

6.1.16 devdoc_agent Process


This section describes the DevDocService service provided by the devdoc_agent process. The devdoc_agent process provides the DevDocService service. The DevDocService service enables you to manage device files. Required services: none

6.1.17 dsXXXX agent Process


This section describes the services and functions provided by the dsXXXX_agent process. The dsXXXX_agent process provides the DesktopServiceXXXX service.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 35

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Some typical process names are ds0101_agent and ds0102_agent. The corresponding service names are DesktopService0101 and DesktopService0102. dsXXXX_agent is a multi-instance process and XXXX refers to the process number. The DesktopServiceXXXX service presents and operates data on several types of clients such as the Java GUI client and the Web client. In the ATAE cluster system, you can deploy this process on the master node and several slave nodes. On the master node, some typical process names are ds0101_agent and ds0102_agent. On the first slave node, some typical process names are ds0201_agent and ds0202_agent. On the second slave node, some typical process names are ds0301_agent and ds0302_agent. You can infer the other process names similarly. You can log in to the client only when the DesktopServiceXXXX service is running properly. During the operation of the M2000, ensure that this service is running properly. Required service: none.

6.1.18 eam_agent Process


This section describes the services and functions provided by the eam_agent process. The eam_agent process provides the EAMService, TopoAdapterService, and TopoService services. The EAMService service provides the function of NE access management and maintains a globally complete NE list. The EAMService service does not depend on any other services. The TopoAdapterService service provides the mediation for earlier versions so that the users who use the earlier versions can use the topology function. The TopoAdapterService service depends on the EAMService, TopoService, LogService, and SecurityService services. The TopoService service can maintain the relation between the devices in the subnet, create and delete subnets, nodes, and topology node, and move nodes among subnets. The TopoService service depends on the EAMService services.

6.1.19 Eml_PerfSvr Process


This section describes the services and functions provided by the Eml_PerfSvr process. This process provides the transfer-domain performance management function. Required services: None.

6.1.20 Eml_PubSvr Process


This section describes the services and functions provided by the Eml_PubSvr process. This process provides the function of inter-NE management on transferdomain NEs and reports. Required services: None.

6.1.21 fars_agent Process


This section describes the service and function provided by the fars_agent process. The fars_agent process provides the FarsService.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 36

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The FarsService provides the function of tracing data collection, data analysis, and data collection management. In the ATAE cluster system, this process is deployed on the primary node. To enable the tracing function, you need to ensure that the FarsService is running normally during the operation of the M2000. Dependent service: none.

6.1.22 fmmedXXXX_agent Process


This section describes the services and functions provided by the fmmedXXXX_agent process. The fmmedXXXX_agent process provides the FMMediationServiceXXXX service. fmmedXXXX_agent is a multi-instance process, where XXXX is the instance number. Generally, the processes are named fmmed0101_agent and fmmed0102_agent and related services are named FMMediationService0101 and FMMediationService0102. FMMediationServicexxxx receives alarms reported by NEs that comply with different protocols. In the ATAE cluster system system, this process can be deployed on the master and slave servers. On the master server, the process names are fmmed0101_agent and fmmed0102_agent. On the first slave server, the process names are fmmed0201_agent and fmmed0202_agent. On the second slave server, the process names are fmmed0301_agent and fmmed0302_agent. The same rule applies to the other slave servers. During the operation of the M2000, ensure that this service is running properly. Independent service: none.

6.1.23 fmnotify_agent Process


This section describes the services and functions provided by the fmnotify_agent process. The fmnotify_agent process provides the FMNotify service. FMNotify forwards the alarm data from FaultManager to the network management system (NMS) by Alarm Streaming Interface. In the ATAE cluster system, you can distribute this process to different slave nodes. Disable FMNotify when the real-time alarm forwarding function is not required. Required services: LicenseService.

6.1.24 FMPreServiceXXXX_agent Process


This section describes the services and functions provided by the FMPreServiceXXXX_agent process. The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service. The FMPreServiceXXXX_agent process is a multi-instance process. XXXX refers to the process number. The FMPreServiceXXXX service provides the function of prehandling faults. In the ATAE cluster system, you can deploy the FMPreServiceXXXX_agent process on the master node and several slave nodes. You can also deploy multiple FMPreServiceXXXX_agent
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 37

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

processes on one node. For example, you can deploy the FMPreService0101_agent, FMPreService0102_agent, and FMPreService0103_agent processes on the master node for providing the FMPreService0101, FMPreService0102, and FMPreService0103 services separately. You can also deploy the FMPreService0201_agent, FMPreService0202_agent, and FMPreService0203_agent processes on a slave node for providing the FMPreService0201, FMPreService0202, and FMPreService0203 services separately. Required service: none.

6.1.25 fnlicense_agent Process


This section describes the services and functions provided by the fnlicense_agent process. The fnlicense_agent process provides the FNLicenseService service. The FNLicenseService provides the fix network management function of managing the license authorization information about EMS. The number of purchased licenses determines the number of available resources and whether the user can use a specific functional component. Required services: LicenseService.

6.1.26 gem_agent Process


This section describes the services and functions provided by the gem_agent process. The gem_agent process provides GEMService. This service receives energy consumption summaries reported by devices, and displays statistics and analysis on the energy consumption of devices. Required services: None.

6.1.27 glmssyn_agent Process


This section describes the services and functions provided by the glmssyn_agent process. The glmssyn_agent process provides the GLMSSynService service. The GLMSSynService periodically obtains the information about QChat cluster communication changes from the Group and List Management Server (GLMS) and then applies the information to CBSCs. In the ATAE cluster system, you can deploy this process on different slave nodes. You can stop this process if the QChat cluster communication is not required. Required services: none.

6.1.28 ifms_agent Process


This section describes the service and functions provided by the ifms_agent process. The ifms_agent process provides the FaultService. The FaultService collects alarm data from NEs and saves the data, thus providing the functions of querying, dumping, and analyzing the fault data. In the ATAE cluster system, this process can be deployed on different slave nodes. You can disable the service when fault management is not required.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 38

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Required service: none.

6.1.29 InventoryDM Process


This section describes the services and functions provided by the InventoryDM process. This process provides the inventory data management function, such as physical resource management, cable management, and customer management. Required services: eam_agent,ifms_agent.

6.1.30 ipm_agent Process


This section describes the services and functions provided by the ipm_agent process. The ipm_agent process provides the IPMService service. The IPMService service enables you to manage an IP network. To use the IP network management function, ensure that the IPMService service is running correctly during the operation of the M2000. Required services: LicenseService.

6.1.31 irp_agent Process


This section describes the functions provided by the irp_agent process.

EPIRP
The EPIRP is subject to the entry point object. The entry point object is the first object that the NMS (Manager) accesses when the NMS interacts with the M2000 (Agent). The Agent provides a reference of an entry point object to the Manager, and the Manager obtains the reference of this entry point object in some way, for example, from the stored file. If the interface for northbound network management is not required, disable the EPIRP. Basic IRP: None.

NotificationIRP
NotificationIRP is used for subscribing to notifications and encapsulating notification subscription. If the function of subscription through the interface of northbound network management is not required, disable the NotificationIRP. Basic IRP: EPIRP.

CSIRP
CSIRP provides an interface for link monitoring. The link monitoring enables you to supervise the status of links between the Manager and the Agent. In this way, the potential exceptions can be detected at the first time. If the function of monitoring through the interface of northbound network management is not required, disable the CSIRP. Basic IRP: EPIRP, and NotificationIRP.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 39

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

KernelCMIRP
KernelCMIRP provides an interface for public configuration management. The public configuration management uses KernelCMIRP to carry out some common tasks during the configuration, such as sending configuration objects, or adding, removing and modifying notifications. If the function of public configuration management through the interface of northbound network management is not required, disable the kernelCMIRP. Basic IRP: EPIRP, and NotificationIRP.

BasicCMIRP
BasicCMIRP controls the configuration management. BasicCMIRP is used for querying, modifying, adding, or removing network resource objects. If the function of configuration management through the interface of northband network management is not enabled, disable the BasicCMIRP. Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, and KernelCMIRP.

AlarmIRP
AlarmIRP is used for managing fault data. If the function of fault data management through the interface of northbound network management is not required, disable the AlarmIRP. Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, KernelCMIRP, and BasicCMIRP.

Required Services
The required service is the LicenseService.

6.1.32 itm_agent Process


This section describes the ItmService service and the dependent services by the itm_agent process. The itm_agent process provides the ItmService service. The ItmService service provides the function of integrated task management. Required services: LicenseService

6.1.33 lic_agent Process


This chapter describes the services and functions provided by the process lic_agent. The lic_agent process provides the LicenseService service. LicenseService provides a service interface to validate the license of the current version. Ensure that this service works properly during the M2000 operation. Required services: none

6.1.34 log_agent Process


This section describes the services and functions provided by the log_agent process.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 40

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The log_agent process provides LogService and ForwardingService. LogService records system-related operations in logs, and provides operation logs for other services or clients to query. By using LogService, you can also set and query the parameters for dumping system logs. ForwardingService forwards the M2000 system logs to a third-party Syslog server according to standard protocols. Required services: None.

6.1.35 maintain_agent Process


This topic describes the function of the MaintenanceService service, which is provided by the maintain_agent process. The maintain_agent process provides the MaintenanceService service. The MaintenanceService service enables the periodic backup of the important system configuration files, database data, and real-time data of MOs. In the ATAE cluster system, you can distribute this process to different slave nodes. During the M2000 operation, ensure that the maintain_agent process is operational. Required services: none

6.1.36 manager_agent Process


This section describes the services and functions provided by the manager_agent process. The manager_agent process provides the SystemService service. SystemService enables you to query the M2000 version information such as the version of the operating system, software version of the client, software version of the server, client software version matching the server software, and client upgrade information. Ensure that this service works properly during the M2000 operation. Required services: none

6.1.37 mc Process
This section describes the services and functions provided by the mc process. This process provides the basic NE distribution service. Required services: None.

6.1.38 medXXXX_agent Process


This section describes the services and functions provided by the medXXXX_agent process. The medXXXX_agent process provides the MediationServiceXXXX service. The medXXXX_agent is a multi-instance process, and XXXX refers to the instance number. When the M2000 is running, the system dynamically generates new processes and services based on NE types and NE quantity. Some typical process names are med0101_agent, med0102_agent,
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 41

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

and med0103_agent, and the names of the corresponding services are MediationService0101, MediationService0102, and MediationService0103. The MediationServiceXXXX service creates, deletes, and obtains the NE engines mirrored to the network devices from the M2000 system and also manages the related event interceptors. NEs of different types communicate with the M2000 system by using the corresponding NE engines through various network management protocols. In addition, the MediationServiceXXXX service can export performance result files on the basis of NEs. In the ATAE cluster system, you can deploy this process on the master node and slave nodes. On the master or the first slave node, some typical process names are med0101_agent, med0102_agent, and med0103_agent. On the second slave node, some typical process names are med0201_agent, med0202_agent, and med0203_agent. On the third slave node, some typical process names are med0301_agent, med0302_agent, and med0303_agent. You can infer the other process names similarly. During the operation of the M2000, ensure that this service is running properly. Dependent services: none

6.1.39 ncc0X01_agent Process


This section describes the services and functions provided by the ncc0X01_agent process. The ncc0X01_agent process provides the NCCService0X01 service. ncc0X01_agent is a multi-instance process, where 0X01 is the instance number. Generally, the process is named ncc0101_agent and the related service is named NCCService0101. NCCService0X01 forwards NE data and controls NE connections. In the ATAE cluster system system, this process can be deployed on the master server and the slave servers. The process names are ncc0101_agent, ncc0201_agent, ncc0301_agent and so on. During the operation of the M2000, ensure that this service is running properly. Independent service: none.

6.1.40 necomm_agent Process


This section describes the services and functions provided by the necomm_agent process. The necomm_agent process provides the CommonLicService service and SSLManageService service. The CommonLicService service manages the information about NE license files, such as invalidity, export, and adjustment information. The SSLManageService service manages the SSL connections between the M2000 and NEs. It also manages the SSL certificates used by the SSL connections. The SSLManageService service depends on CommonLicService service.

6.1.41 nelicense_agent Process


This section describes the services and functions provided by the nelicense_agent process. The nelicense_agent process provides the NeLicenseService service.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 42

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The NeLicenseService service manages NodeB licenses and implements the sharing of a license between the NEs of the same type. Required services: LogService.

6.1.42 nemgr_ptn Process


This section describes the services and functions provided by the nemgr_ptn process. This process provides the function of managing Metro Ethernet PTN frame-shaped and caseshaped NEs. Required services: None.

6.1.43 nemgr_rtn Process


This section describes the services and functions provided by the nemgr_rtn process. This process provides the function of managing RTN series equipment. Required services: None.

6.1.44 neproxy Process


This section describes the services and functions provided by the neproxy process. Data Collector NE Proxy Process Required services: None.

6.1.45 neuser_agent Process


This section describes the NeUserService service. NeUserService is provided by the neuser_agent process. The neuser_agent process provides the NeUserService service. The NeUserService service enables you to manage NE users. When the M2000 and NEs are connected properly, you can manage NE users through the M2000. For example, you can authenticate the login of NE users, deliver command rights and command group rights, and customize command groups. Required services: none

6.1.46 ngnffs_agent Process


This section describes the NGNFullFillService service and dependent services. The ngnffs_agent process provides the NGNFullFillService. The NGNFullFillService service provides functions of managing management domains and provisioning subscriber numbers. Required services: none

6.1.47 ngnni112_agent Process


This section describes the services and functions provided by the ngnni112_agent process.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 43

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The ngnni112_agent process provides the NGNNI112Service service. The NGNNI112Service provides the NBI for the subscriber line test system. Required services: NGNTestManageService.

6.1.48 ngnnis_agent Process


This section describes the NGNNIService service and dependent services. The ngnnis_agent process provides the NGNNIService. The NGNNIService service provides functions of the north interface operation management. Required services: none

6.1.49 ngntestmanage_agent Process


This section describes the services and functions provided by the ngntestmanage_agent process. The ngntestmanage_agent process provides the NGNTestManageService service. The NGNTestManageService provides the fix access network test management function. Required services: none.

6.1.50 nhcservice_agent Process


This section describes the services and functions provided by the nhcservice_agent process. The nhcservice_agent process provides the NHCService service. The NHCService service provides the NE health check function. If you plan to perform a heath check task, you must ensure this service is running properly. Required service: ItmService and EAMService.

6.1.51 nicservice_agent Process


This section describes the services and functions provided by the nicservice_agent process. The nicservice_agent process provides the NICService service. The NICService service provides the network information collecting function. The nicservice_agent process is available only after you have installed the network information collecting components. If you plan to perform a network information collecting task, you must ensure this service is running properly. Required service: ItmService and EAMService.

6.1.52 nimserver_agent Process


This section describes the NIMServer service and the dependent service. NIMServer is provided by the nimserver_agent process. The nimserver_agent process provides the NIMServer service.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 44

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The NIMServer service only enables you to centralize the real-time monitoring of alarms, performance, and configuration status of some WRAN configuration objects. It also only provides the functions to some WRAN configuration objectssuch as alarm statistics, query of basic configuration information, query of configuration link constitution and basic configuration information, and query of adjacent cells and channel assignment. Required services: none

6.1.53 nms_mml_agent Process


This section describes the services and functions provided by the process nms_mml_agent. The nms_mml_agent process provides the NMSMMLServer service. That is, the NMS issues MML commands through the northbound MML transmission interface to managed NEs. If the northbound MML transmission interface is used when the M2000 is running, ensure that the NMSMMLServer is running correctly. When the northbound MML transmission interface is not used, the NMSMMLServer is not disruptive to other services. Required services: LogService.

6.1.54 partition_agent Process


This section describes the services and functions provided by the partition_agent process. The partition_agent process provides the PartitionService service. The PartitionService service divides managed objects into various partitions. Each partition is managed by its own process. In the presence of a large quantity of objects, the partitions are managed by various processes on different servers to balance the load. Ensure that this service works properly during the M2000 operation. Required services: none.

6.1.55 pm_agent Process


This section describes the services and functions provided by the process pm_agent. The pm_agent process provides the PMService service. PMService monitors performance management on all NEs. The performance management is independent of NEs or objects. Stop PMService if the performance management function is not required. Required services: none.

6.1.56 PMDataSynchronizer Process


This section describes the services and functions provided by the PMDataSynchronizer process. This process provides the function of importing data in text files. Required services: None.

6.1.57 pmengine0X01_agent Process


This section describes the services and functions provided by the pmengine0X01_agent process.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 45

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The pmengine0X01_agent process provides the PMEngine0X01 service. The pmengine0X01_agent process is a multi-instance process. 0X01 indicates the number of a process instance. The corresponding service of the pmengine0101_agent process is PMEngine0101. This service provides the functions of querying and managing the ATAE cluster system performance. In the ATAE cluster system, you can deploy this process on master node and different slave nodes. Some typical process names are pmengine0101_agent, pmengine0201_agent, and pmengine0301_agent. You can infer the other process names similarly. When the M2000 is running, ensure that this service functions properly. Required services: None.

6.1.58 pmexp_agent Process


This section describes the services and functions provided by the process pmexp_agent. The pmexp_agent process provides the PMExport service. PMExport exports performance data of a measurement unit from the database. PMExport is independent of NEs or managed objects. In the ATAE cluster system, you can distribute this process to different slave nodes. Stop PMExport when the function of exporting performance results is not required. Required services: LicenseService.

6.1.59 pmmon_agent Process


This section describes the services and functions provided by the process pmmon_agent. The pmmon_agent process provides the PMMonService service. PMMonService monitors key NE counters and displays the value about these counters in figures and tables. Required services: PMService

6.1.60 PMSDm Process


This section describes the services and functions provided by the PMSDm process. This process provides the collector management function. Required services: None.

6.1.61 porttrunk_agent Process


This section describes the services and functions provided by the porttrunk_agent process. The porttrunk_agent process provides the PortTrunkingService service. By using the PortTrunkingService service, the M2000 server can communicate with the M2000 client through a specified port. You need not configure multiple ports on the firewall for communication.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 46

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Required services: none

6.1.62 PQMDm Process


This section describes the services and functions provided by the PQMDm process. This process provides the function of grouping performance monitoring and display. Required services: None.

6.1.63 proxy_agent Process


This section describes the services and functions provided by the proxy_agent process. The proxy_agent process provides the Proxyserver service. Proxyserver enables the M2000 client to connect to NEs through the proxy server and to run applications of the NEs on the LMT . Stop Proxyserver when the proxy function is not required. Required services: none.

6.1.64 PRSAssistantService_agent Process


This section describes the services and functions provided by the PRSAssistantService_agent process. The PRSAssistantService_agent process provides the PRSAssistantService service. The PRSAssistantService service provides the function of generating reports in .html, .csv or .xls format. It also provides the function of transferring result files by email or through the FTP. After restarting the PRSAssistantService service, you need to restart the PRSReportService service. In the ATAE cluster system, you can distribute this process to different slave nodes. If you need to run the PRS module, the PRSReportService service cannot be stopped. Required services: none

6.1.65 prsdc_agent Process


This section describes the services and functions provided by the prsdc_agent process. The prsdc_agent process provides the PRSDcService service. The PRSDcService service provides the function of obtaining configuration data files and performance data files on schedule. In the ATAE cluster system, the prsdc_agent process can be deployed on slave nodes. Keep the service running during the operation of the PRS module. Required service: none.

6.1.66 prsfs_agent Process


This section describes the services and functions provided by the prsfs_agent process.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 47

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The prsfs_agent process provides the PRSFsService service. That is, it provides the service for importing report data. The PRSFsService service provides the function of parsing configuration data files and performance data files on schedule. In the ATAE cluster system, the prsfs_agent process can be deployed on slave nodes. Keep the service running during the operation of the PRS module. Required service: LicenseService.

6.1.67 prsreport_agent Process


This section describes the services and functions provided by the prsreport_agent process. The prsreport_agent process provides the PRSReportService service. The PRSReportService service provides the function of querying the reports of the PRS module. In the ATAE cluster system, you can distribute this process to different slave nodes. If you need to run the PRS module, the PRSReportService service cannot be stopped. Required services: LicenseService and ItmService.

6.1.68 prssum_agent Process


This section describes the services and functions provided by the prssum_agent process. The prssum_agent process provides the PRSSumService service. The PRSSumService service provides the function of summarizing the data of the PRS (Performance Report Suite) module. It is responsible for retrieving data in a specified order and scheduling the data. In the ATAE cluster system, you can distribute this process to different slave nodes. If you need to run the PRS module, the PRSSumService service cannot be stopped. Required services: LicenseService.

6.1.69 rn_agent Process


This section describes the services and functions provided by the rn_agent process. The rn_agent process provides the RNService service. The RNService service provides the user with the function of sending notifications by email or short message. Required service: none.

6.1.70 RouterMgrDm Process


This section describes the services and functions provided by the RouterMgrDm process. This process provides the function of managing Quidway routers. Required services: None.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 48

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

6.1.71 ScriptModuleService_agent Process


This section describes the services and functions provided by the ScriptModuleService_agent process. The ScriptModuleService_agent process provides the ScriptModuleService service. The ScriptModuleService service provides the function of managing applications. Required services: ItmService

6.1.72 scriptserver_agent Process


This section describes the services and functions provided by the process scriptserver_agent. The scriptserver_agent process provides the ScriptService service. ScriptService provide script timing and NEs access from script. Ensure that this service works properly during the M2000 operation. Required services: ItmService and SecurityService.

6.1.73 SecurityMgrDm Process


This section describes the services and functions provided by the SecurityMgrDm process. This process provides the function of managing FW/USG, SIG, and SVN series security equipment. Required services: None.

6.1.74 sm_agent Process


This section describes the services and functions provided by the process sm_agent. The sm_agent process provides the SecurityService service. SecurityService controls the access of all sensitive resources in the M2000. Only authorized users can gain access to sensitive resources. Ensure that this service works properly during the M2000 operation. Required services: EAMService and LicenseService

6.1.75 snm_agent Process


This section describes the SNMService service and dependent services. The snm_agent process provides the SNMService. The SNMService service provides signaling network management, including topology management, port monitoring, and resource management. Required services: TopoService and EAMService.

6.1.76 snmp_agent Process


This section describes the SnmpAgent service and the dependent services. The SnmpAgent service is provided by the snmp_agent process.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 49

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The snmp_agent process provides the SnmpAgent service, that is, the northbound interface service complying with the SNMP protocol. The SnmpAgent service enables the upper-level NMS to obtain the information on the M2000 such as alarm data, through the SNMP protocol. Required services: LogService and LicenseService.

6.1.77 son_agent Process


This section describes the services and functions provided by the son_agent process. The son_agent process provides the SONService service. The SONService service provides a series functions for automatically managing networks, such as automatically detecting, configurating, and optimizing NEs. The DHCP module provides the function of automatically detecting the eNodeB, BWA, pBTS3701, NodeB, GSM Pico, PICO BTS, and TGW. The Easy Deployment System (EDS) module provides the function of automatically creating an LTE site. The Auto Neighbor Relation (ANR) module provides the functions of automatically detecting the neighboring cells of the LTE, querying neighboring cell parameters across cells, and modifying neighboring cell parameters. In the ATAE cluster system, the son_agent process is deployed on the master node. If the functions for automatically managing networks are not required, this service can be stopped. Required service: none

6.1.78 sso_agent Process


This section describes the services and functions provided by the sso_agent process. The sso_agent process provides SSO service. SSO service provides the function of centralized account management and authorization. Required services: none.

6.1.79 swm_agent Process


This section describes the services and functions provided by the swm_agent process. The swm_agent process provides the SWMService service. The SWMService manages the versions, configuration data, NE logs, and other files of some NEs. It also provides the download, upload, activation, and rollback functions. Ensure that this service works properly during the M2000 operation. Required services: none

6.1.80 threshold_agent Process


This topic describes the function of the ThresholdService service provided by the threshold_agent process and the service that the threshold_agent process depends on. The threshold_agent process provides the ThresholdService service.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 50

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

The ThresholdService service provides the threshold management function. For example, this service allows you to add, generate, and change a threshold. In addition, this service can generate threshold alarms. During the M2000 operation, ensure that the threshold_agent process is operational. Required services: PMService.

6.1.81 toolkit Process


This section describes the services and functions provided by the toolkit process. This process provides the service of upgrading boardlevel transmission equipment. Required services: None.

6.1.82 trapdispatcher Process


This section describes the services and functions provided by the trapdispatcher process. The trapdispatcher process provides the trapdispatcher service. The trapdispatcher service controls the forwarding of the Snmp Trap messages that are reported by NEs monitored by the M2000. The trapdispatcher service forwards the Snmp Trap messages that are reported to port 162 by each NE to the Mediation service of each NE. When the M2000 is running, ensure that the trapdispatcher process works properly. Required services: PartitionService

6.1.83 TXTNBIDm Process


This section describes the services and functions provided by the TXTNBIDm process. This process provides the NBI function. It is used to transmit performance data in the text format through FTP. Required services: None.

6.1.84 uap_agent Process


This section describes the services and functions provided by the uap_agent process. The uap_agent process provides the UAPService service. The UAPService service provides the Sock5 agent function on the M2000 server. Thus, when users cannot access the BAM server (make sure that the M2000 server normally connects to the BAM), the M2000 client can be started through the agent. The uap_agent process also provides the function of authenticating user operations to meet the requirement of authority and domain based management on the M2000. Required service: none.

6.1.85 uflight_dispatcher Process


This section describes the services and functions provided by the uflight_dispatcher process. Dispatcher the web request of UFlight.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 51

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Required services: Apache.

6.1.86 umgupdsvr_agent Process


This section describes the services and functions provided by the umgupdsvr_agent process. The umgupdsvr_agent process provides the UMGUpgradeService service. UMGUpgradeService provides the UMG upgrade function. Required service: none.

6.1.87 UniteUitlDM Process


This section describes the services and functions provided by the UniteUitlDM process. This process provides the basic functions, such as importing and exporting scripts, managing NE time, synchronizing NEs, and managing NE objects, of the inter-domain universal NMS. Required services: None.

6.1.88 xftpXX01_agent Process


This section describes the services and functions provided by the xftpXX01_agent process. The xftpXX01_agent process provides the XFTPServiceXX01 service. Through the XFTPServiceXX01 service, the M2000 actively uploads exported files through the northbound interface to the FTP server on the NMS side. You can upload the files exported through the northbound interface to the FTP server on the NMS side using the XFTPServiceXX01 service. The XFTPServiceXX01 service can export various types of files, for example: l l l l l l l l NBI FM NBI CM NBI Inventory NBI PM CME NBI License Management NBI server backup NBI log

Through the M2000 client, you can set the FTP server on the NMS side. In the ATAE cluster system, you can deploy this process on the master node and different slave nodes. Some typical process names are xftp0101_agent, xftp0201_agent, and xftp0301_agent. You can infer the other process names similarly. When the M2000 is running, ensure that the xftpXX01_agent process works properly. Required services: none

6.1.89 Trace Server Services and Processes


The section describes the function of Trace Server services and processes
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 52

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Each Trace Server process maps a Trace Server service. Table 6-1 describes Trace Server services and processes. Table 6-1 Trace Server services and processes Service Name Monitor Process Name Monitor Platform HP Description Monitors the Trace Server software. The Monitor service must be started. Dependent service: None. TS.Subscr iber TS.Subscr iber HP Subscribes to signaling and periodically deletes subscribed files. The TS.Subscriber service runs on a separate process. In addition, the service is started automatically by scripts and does not need to be started manually. Dependent service: Monitor. TS.Collec tor TS.Collec tor HP Collects and filters data and events. The TS.Collector service runs on a separate process. In addition, the service is started automatically by scripts and does not need to be started manually. Dependent service: Monitor. EBCStatis tic EBCStatis tic HP Calculates counters based on events for the Long Term Evolution (LTE) network. This service runs on an independent process and starts automatically by scripts. Dependent service: Monitor. TSService ts_agent ATAE Collects LTE tracing data and filters events. The TSService service runs on a separate process. In addition, the service is started automatically by scripts and does not need to be started manually. In the ATAE cluster system, this process is deployed on the Trace Server slave node. Dependent service: None. EBCStatis tic ebc_agent ATAE Calculates counters based on events for the Long Term Evolution (LTE) network. This service runs on an independent process and starts automatically by scripts. Dependent service: None.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

53

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

6.1.90 Processes and Services Related to Each Northbound Interface


This section describes the processes and services related to each northbound interface. Table 6-2 describes the relations between northbound interfaces and their corresponding processes and services. Table 6-2 Relations between northbound interfaces and their corresponding processes and services Process irp_agent Service IRPService Northbound Interface l CORBA configuration interface l CORBA alarm interface l CORBA security interface l CORBA performance interface ifms_agent pmexp_agent FaultService PMExport Northbound alarm file interface Northbound performance file interface (measurement unitbased) Northbound performance file interface (NE-based) Northbound SNMP interface Northbound alarm streaming interface Northbound MML interface Northbound inventory file interface l Northbound configuration file interface l Database interface

medXXXX_agent snmp_agent fmnotify_agent nms_mml_agent cmserver_agent cmexp_agent

MediationServiceXXXX SnmpAgent FMNotify NMSMMLServer CMServer CMExport

6.1.91 Checking the Status of the M2000 Processes


This section describes how to check the status of the M2000 processes. When the M2000 processes are not running normally, you need to locate faults and log in to the server to rectify the faults in time. In the ATAE cluster system, the client can monitor the master node and all slave nodes simultaneously.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

54

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Prerequisites
l l You have logged in to the M2000 client. You have the relevant operation rights.

Context
Checking the states of the M2000 processes on the M2000 client requires only a few system resources and does not affect system performance.

Procedure
Step 1 Choose Monitor > System Monitor > Browser. The System Monitor Browser window is displayed. Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on the M2000 server. See Figure 6-1. Figure 6-1 Process Monitor tab page

Step 3 Optional: Click Save AS to save the monitoring data as a file.


NOTE

l The monitoring information can be saved in the format of TXT, HTML, CSV, or XML. The default format is XML. l Two types of encoding formats are supported: GBK and UTF-8. The default encoding format is GBK. You are recommended to use the default encoding format if the saved file does not need to support multiple languages; otherwise, UTF-8 is recommended.

----End

6.2 Viewing the Running Status of M2000 Services (SUSE)


This describes how to view the status of M2000 services on the M2000 server. This operation requires only few system resources and does not affect system performance.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 55

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Prerequisites
You have Logged in to the M2000 server as user ossuser.

Procedure
Step 1 Run the following commands: ~> cd /opt/oss/server ~> . ./svc_profile.sh ~> svc_adm -cmd status
Host: DEFAULTSYSAGENT SystemConfigurator: running Service Agent: cmserver_agent [1 service(s)] pid: 3160 CMServer [running ] Service Agent: devdoc_agent [1 service(s)] pid: 3138 DevDocService [running ] Service Agent: em_agent [1 service(s)] pid: 3126 EventService [running ]

Service Agent: fmnotify_agent [1 service(s)] pid: 3146 FMNotify [running ] Service Agent: ifms_agent [1 service(s)] pid: 3162 FaultService [running Service Agent: irp_agent [1 service(s)] pid: 3150 IRPService [running Service Agent: log_agent [1 service(s)] pid: 3125 LogService [running ] ] ]

Service Agent: manager_agent [2 service(s)] pid: 3134 DataMgrService [running ] SystemService [running ] Service Agent: med1_agent [1 service(s)] pid: 3140 MediationService1 [running Service Agent: med4_agent [1 service(s)] pid: 3172 MediationService4 [running Service Agent: med_agent [1 service(s)] pid: 3132 MediationService [running Service Agent: mo_agent [4 service(s)] pid: 3136 LockService [running MOProxyService [running MOService [running RelationService [running ] ] ] ] ] ] ]

Service Agent: monitor_agent [1 service(s)] pid: 3128 MonitorService [running ] Service Agent: neuser_agent [1 service(s)] pid: 3164 NeUserService [running ] Service Agent: notify_agent [1 service(s)] pid: 3142 RemoteNotifyService [running ] Service Agent: partition_agent [1 service(s)] pid: 3154 PartitionService [running ]

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

56

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

Service Agent: pm_agent [1 service(s)] pid: 3144 PMService [running ] Service Agent: pmexp_agent [1 service(s)] pid: 3166 PMExport [running ] Service Agent: pmmon_agent [1 service(s)] pid: 3148 PMMonService [running ] Service Agent: porttrunk_agent [1 service(s)] pid: 3158 PortTrunkingService [running ] Service Agent: proxy_agent [1 service(s)] pid: 3170 ProxyServer [running ] Service Agent: sac_agent [2 service(s)] pid: 3130 LicenseService [running ScheduleService [running Service Agent: sm_agent [1 service(s)] pid: 3156 SecurityService [running Service Agent: swm_agent [1 service(s)] pid: 3152 SWMService [running Service Agent: tm_agent [1 service(s)] pid: 3168 TopoService [running ] ] ] ] ]

[All Services: 30 ] [Running : 30 ] [Not Running : 0 ]


NOTE

The M2000 system generates processes and services dynamically during the operation. Accordingly, the number of processes and services changes dynamically.

----End

6.3 Starting the M2000 Server (SUSE)


After you run the start_svc command, all the M2000 services are started. If an M2000 service is already started, the system does not handle the service. Actually, the system starts only the inactive services.

Prerequisites
You have logged in to the server as user ossuser.

Procedure
Step 1 Run the following commands: ~> cd /opt/oss/server ~> . ./svc_profile.sh ~> start_svc
NOTE

l Before starting the M2000 server, ensure that the Oracle is started. l The time required for starting M2000 services is related to the actual environment. Generally, starting services takes 15 to 20 minutes.

----End
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 57

M2000 Administrator Guide (x3850, SUSE10)

6 Managing the M2000 Processes and Services

6.4 Stopping the M2000 Services (SUSE)


This describes how to stop the M2000 services. After the M2000 services are stopped, the M2000 processes are stopped. In this situation, NE performance data and alarm data cannot be processed. After the services are resumed, the M2000 updates the data with the NEs and processes the data.

Prerequisites
You have logged in to the server as user ossuser.

Procedure
Step 1 Run the following commands to stop the M2000 services: ~> cd /opt/oss/server ~> . ./svc_profile.sh ~> stop_svc
NOTE

The time required for stopping M2000 services is related to the actual environment. Generally, stopping services takes 15 to 30 minutes.

Step 2 Run the following command to check whether there is any output. If no system output is displayed, you can infer that M2000 services are stopped. ~> svc_ps Step 3 If some services are still running, run the following command to forcibly stop them: ~> kill_svc Step 4 Run the following command to stop the M2000 daemon: ~> stop_daem Step 5 Run the following command to check whether there is any output. If no system output is displayed, you can infer that the M2000 daemon is stopped. ~> daem_ps Step 6 If the daemon process is still running, run the following command to forcibly stop it: ~> kill_daem ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

58

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

7
About This Chapter

Managing M2000 Database

This chapter describes how to manage the M2000 database. This chapter also describes the concepts of the M2000 database and procedures on how to view the database status, start or stop the database, and check the database space. 7.1 Introduction to the M2000 Database (Oracle, ATAE) The M2000 databases consist of the Oracle database and the M2000 server database. This chapter describes only the M2000 server database. On the basis of the Oracle database, the M2000 creates the OSSDB database. After the installation of the M2000 server application software, the size of the M2000 database is fixed. You must operate the database by using Oracle commands. 7.2 Checking Oracle Services After installing the M2000 software or in the daily maintenance, you need to check the status of Oracle services. 7.3 Starting Oracle Service This section describes how to start the Oracle service. 7.4 Stopping Oracle Service This section describes how to stop the Oracle service. 7.5 Checking Database Space This describes how to use Oracle commands to view the database status, overall size of data files, and size of remaining space. This operation requires few system resources and does not affect system operation.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

59

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

7.1 Introduction to the M2000 Database (Oracle, ATAE)


The M2000 databases consist of the Oracle database and the M2000 server database. This chapter describes only the M2000 server database. On the basis of the Oracle database, the M2000 creates the OSSDB database. After the installation of the M2000 server application software, the size of the M2000 database is fixed. You must operate the database by using Oracle commands.

7.1.1 omcdb
The omcdb is used to store the configuration data, security data, and internal data of the M2000. The omcdb database must exist in the M2000 system. The omcdb requires a disk space of more than 1,000 MB. Table 7-1 describes the name and function of each table in the omcdb. Table 7-1 Names and functions of tables in the omcdb database Table Name Tables with moi_ as the prefix Tables with mos_ver_ as the prefix Tables with nbmmlNe_ as the prefix Tables with sm_ as the prefix Tables with softx3000_ as the prefix Views with gv_view_cmcyw_ as the prefix Views with view_cmcyw_ as the prefix tbl_AllNeInfo Processes with proc_sm_ as the prefix Processes with sm_ as the prefix tbl_Resource Function Records the information about MO examples. Records the information about versions. Records the information about the format of messages transferred between the M2000 and the NEs. Records the information about service data. Records dual-homing relationship. Records service Database Central (DC) data.

Records basic service data.

Records information about NEs. Records the processes of service data. Records the processes of service AMG data. Records NE resource data.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

60

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table Name Tables with ums_ as the prefix Tables with ne_ as the prefix Tables with omc_ as the prefix Tables with rel_ as the prefix tbl_ADAllNeList tbl_ADNeStatus tbl_IPExg tbl_OmcSslOption tbl_nelicBaseInfo tbl_nelicTask tbl_nelicTaskEnv tbl_test_task_property tbl_test_local_path tbl_test_other_path tbl_test_log_result tbl_test_ping_report tbl_test_audit_result tbl_test_nblink_result tbl_test_ping_address tbl_SubareaInfo tbl_SubareaRes session_SessionEntity session_SessionMoc session_SessionOpInfo

Function Record the information about error codes. Records the information about NE models. Records the data about network management. Records the associations between MOs. Records the information about the NodeBs to be commissioned. Records the information about the statuses of the NodeBs to be commissioned. Records the IP configuration information about the NAT translation table. Records the SSL connection policy of the OMC for NEs. Records the basic information about NEs. Records the information about operation tasks. Records the information flow interacted between the M2000 server and client. Records the properties of the IPQoS test task. Records the intra-office test path. Records the inter-office test path. Records the test task logs. Records the signaling parameters on the bearer network. Records the audit results of calling and called parties on the bearer network. Records the audit result of the call completion rate on the bearer network. Records information about address pairs sent by the host. Partition information table, recording the information about each node. Partition resource table, recording the resources of each node. Records information about operated NEs during a session. Records information about operated MOCs during a session. Records information about user operations during a session.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

61

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table Name Other tables

Function Records other configuration data of the M2000.

7.1.2 logdb
The logdb is used to store log management data. The logdb database must exist in the M2000 system. The logdb requires more than 500 MB disk space. Table 7-2 lists the names and functions of the tables in the logdb. Table 7-2 Names and functions of tables in the logdb database Table Name tbl_Audit tbl_SysLog tbl_SysLogResultDef tbl_SysLogStaticInfo Other tables Function Records the logs of user operations. Records the logs of system operations. Records the result information about system logs. Records the static information about system logs. Records the information about other logs.

7.1.3 smdb
The smdb is used to store security management data. The smdb database must exist in the M2000 system. Table 7-3 lists the names and functions of the tables in the smdb. Table 7-3 Names and functions of tables in the smdb database Table Name tbl_AccessTable tbl_AccessViewNodeRelTable tbl_AccessViewNodeTable tbl_IDTable tbl_SMAccessPolicyItem tbl_SMGroup
Issue Draft A (2012-02-27)

Function Records the binding relations between user groups and privileges. Records the relations between the privilege display nodes. Records the privilege display nodes. Records the reclaimed IDs. Records the privilege statistics for binding user groups. Records the basic information about user groups.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 62

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table Name tbl_SMGroupUserMap tbl_SMLoginRec tbl_SMNEUser tbl_SMPrivateGroupUserMap tbl_SMSecurityPolicy tbl_SMTerm tbl_SMUser tbl_SMUserHistoryRec tbl_SMUserNEUserMap tbl_SMUserTerminalMap tbl_SecurityObjectTable tbl_SessionTable tbl_StaticTypeRelationTable tbl_StaticTypeTable tbl_StaticTypeViewTable Other tables

Function Records the binding relations between user groups and users. Stores the history records on user login. Records the basic information about NE users. Records the binding relations between private groups and users. Records the security policy. Records the basic information about terminals. Records the basic information about users. Records history user passwords. Records the binding relations between users and NE users. Records the binding relations between users and terminals. Records security objects. Records session information. Records the relations between privileges. Records the static security information about object types, privileges, and operations. Records the static security information. Records the information about internal implementation.

7.1.4 topodb
The topodb is used to store topology management data. The topodb database must exist in the M2000 system. The topodb requires a disk space of more than 550 MB. Table 7-4 lists the names and functions of the tables in the topodb. Table 7-4 Names and functions of the tables in the topodb database Table Name TSLink TSNode
Issue Draft A (2012-02-27)

Function Records the information on topology links. Records the information on topology NEs.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 63

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table Name TSView TSTempLoc TSTempPos Other tables

Function Records the information on topology views. Records the temporary table that stores the longitude and latitude coordinates of the e-map. Records the temporary table that stores the x-axis and y-axis coordinates of common physical topology. Records the information about internal implementation.

7.1.5 fmdb
The fmdb is used to store the alarm data of the M2000 and the managed NEs. The fmdb database must exist in the M2000 system. The fmdb stores the NE data and the M2000 alarm data. A disk space of more than 3,700 MB is required for the storage. Table 7-5 lists the names and functions of tables in the fmdb. Table 7-5 Tables of the fmdb database and the corresponding functions Table Name tbl_alm_log tbl_event_log Other tables Function Records alarm logs. Records event logs. Record the internal processing data of alarms.

NOTE

The system automatically divides the tbl_alm_log and tbl_event_log tables according to the size of alarms and events. For example, the fmdb database may contain multiple alarm log tables such as tbl_alm_log_1 and tbl_alm_log_2.

7.1.6 pmdb
The pmdb is used to store the NE performance measurement data. The pmdb database must exist in the M2000 system. If the remaining space of the pmdb database is insufficient, the system generates an alarm. After the storage period of the performance measurement data expires, the most recent data overwrites the earliest data on a daily basis. If the data is saved for less than the preset days old but the pmdb is fully occupied, you must change the number of days till the data can be stored. Otherwise, the pmdb cannot process any performance data. Change the number of saving days before the remaining space of the pmdb is insufficient.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 64

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

To calculate the number of days till when the data can be stored, perform the following steps: Observe the usage of the pmdb when the M2000 runs for half a month. Calculate the space of the pmdb used in a day. Calculate the number of days that the pmdb lasts. The pmdb consists of the following types of tables: l l Template Tables Function Subsets and Period Tables

Template Tables
Template tables record measurement information. Table 7-6 lists the name and function of the table. Table 7-6 Template tables in the pmdb and their functions Table Name tbl_SyncInfo Function Records the supplementary collection queues of performance results.

Function Subsets and Period Tables


The pmdb database stores the tables of measurement results categorized by function subsets and periods. Table 7-7 lists the name and function of the table. Table 7-7 Function subset tables and period tables in the pmdb and the corresponding functions Table Name tbl_Result_XXX_Y Function Records periodic results. In the table name, XXX is the ID of the function subset and Y is the period index between 0 and 4.

7.1.7 swmdb
The swmdb is used to store the file information about the software management module and the configuration data of NE versions. The swmdb database must exist in the M2000 system. The swmdb stores the files managed by the software management module and the NE version configuration data. A disk of more than 3,000 MB is required for storage. Table 7-8 lists the name and function of each table. Table 7-8 lists the names and functions of tables in the swmdb.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

65

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table 7-8 Names and functions of tables in the swmdb database Table Name tbl_FTPFileSet tbl_VersionRelation tbl_NELogTable Function Records the files managed by the software management module. Records the information about version relations. Records the NE operation logs.

7.1.8 pmcomdb
The pmcomdb is used for storing the static performance measurement data of NEs. The pmcomdb database must exist in the M2000 system. The space of the pmcomdb must be greater than 400 MB. If the remaining space of the pmcomdb is insufficient, the system generates an alarm. The pmcomdb consists of the following types of tables: l l l Counter tables Template Tables Function Subsets and Period Tables

Counter tables
Compared with the data in other types of tables, the data in these tables is stable. Table 7-9 lists the name and function of each table. Table 7-9 Counter information tables in the pmcomdb and the corresponding functions Table Name systbl_NeType systbl_FunctionSet systbl_FunctionSubSet systbl_Counters systbl_Counter_Unit systbl_AllCounterCategory systbl_ComputeCounters Function Records all possible NE types in M2000. Records the function sets of all NEs. Records the measurement units of all function sets. Records all measurement counters. Records the units of all counters. Records the service features of each version. Records only the counters involved in calculation.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

66

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Template Tables
Template tables contain several tables that record measurement information. Table 7-10 lists the name and function of each table. Table 7-10 Template information tables in the pmcomdb and the corresponding functions Table Name tbl_ObjectInstance tbl_MeasurementPeriod tbl_MeasurementCounter tbl_MeasurementSuspendInfo tbl_CounterCategory tbl_CounterLevel tbl_FeatureStatus Function Records measurement objects. Records measurement periods. Records measurement counters. Records the information on suspended tasks. Records the status of each service feature. Records the status of each service counter. Records the status of all the service features on the M2000 operating environment.

Function Subsets and Period Tables


The measurement results are saved according to the function subset and period. Table 7-11 lists the name and function of each subset and table. Table 7-11 Function subsets and period tables in the pmcomdb and their functions Table Name tbl_MeasObject_XXX_Y Function In the table name, XXX refers to the function subset ID and Y refers to the period index that ranges from 0 to 4. By comparing the tbl_MeasObject_XXX_Y with the result table named tbl_Result_XXX_Y, you can check the loss status and integrity of the results. Each time when the measured object changes, a message is recorded in the list.

7.1.9 itfndb
The itfndb is used to store the northbound configuration data, performance tasks, and performance threshold data. The itfndb database must exist in the M2000 system. The itfndb is optional. It requires a disk space of at least 200 MB. Table 7-12 lists the name and function of each table.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 67

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table 7-12 Names and functions of tables in the itfndb database Table Name tbl_JGeneralInfo tbl_JMoInstance tbl_JStatusRecord tbl_JMeasurementCategory tbl_JSchedule tbl_RegM2KObject tbl_MGeneralInfo tbl_MMoInstance tbl_MMeasurementCategory tbl_MThresholdPackElemen tbl_MAlarmRecord tbl_MStatusRecord Other tables Function Records the general information about tasks. Records the instances of tasks. Records the Status of tasks. Records the measurement categories of tasks. Records the task scheduling. Records the registered M2000 objects. Records the general information about thresholds. Records the instances of thresholds. Records the measurement categories of thresholds. Records the details of thresholds. Records the alarm records of thresholds. Records the status of thresholds. Records the information about northbound implementation.

7.1.10 farsdb
The farsdb is used to store the signaling data of all the NEs managed by the M2000. The farsdb requires at least 10 GB data space and 3 GB log space. The farsdb consists of the following types of tables: l l l Static configuration data table Task table Task data table

Table 7-13 describes the name and function of each table in the farsdb. Table 7-13 Names and functions of tables in the farsdb database Table Name tbl_ProcessorInfo tbl_Field tbl_TaskInfo tbl_TaskNE
Issue Draft A (2012-02-27)

Function Static service configuration table Static field configuration table Dynamic task record table Table recording the tasks reported to NEs
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 68

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table Name Message type name_task ID

Function Task data table created dynamically, which records the signaling data of the message type corresponding to a task

7.1.11 osstempdb
The osstempdb is used to store the buffer data required for internal implementation of the DesktopServiceXXXX service. The osstempdb database must exist in the M2000 system. The osstempdb requires more than 500 MB disk space. Table 7-14 lists the name and function of each table in the osstempdb. Table 7-14 Names and functions of tables in the osstempdb database Table Name tbl_instance name_subsystem name_function name Function Stores the buffer data required for internal implementation of the DesktopServiceXXXX service.

7.1.12 eamdb
The eamdb is used to store the data of network management objects, such as NEs, subnets, and links. The eamdb database must exist in the M2000 system. The eamdb requires more than 500 MB disk space. Table 7-15 lists the name and function of each table in the eamdb. Table 7-15 Names and functions of tables in the eamdb database Table Name tbl_sn tbl_ne tbl_nefeature tbl_link tbl_idresource tbl_sntype tbl_netype tbl_linktype tbl_sync
Issue Draft A (2012-02-27)

Function Subnet information table NE information table NE feature table Link information table NMS object identification management table Subnet type table NE type table Link type table Data synchronization table
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 69

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Table Name tbl_nerelation tbl_maintenanceinfo tbl_locationinfo tbl_negroup tbl_negroupclass tbl_negroup2ne tbl_negrouptype tbl_devsnmppara tbl_dftsnmppara tbl_autodiscfilter tbl_autodischistory tbl_eamschedule tbl_autodiscresult tbl_SubareaInfo tbl_SubareaRes Other tables

Function NE relation table Maintenance personnel information table Device maintenance information table NE group information table NE group mode table NE group and NE relation table NE group type table SNMP device parameter table Default SNMP parameter table Auto-search IP filter table Auto-search history record table Scheduled-search parameter table Auto-search result table Refers to the partition information table, which records the information about each node. Refers to the partition resource table, which records the resources of each node. Record the internal processing data

7.2 Checking Oracle Services


After installing the M2000 software or in the daily maintenance, you need to check the status of Oracle services.

Prerequisites
You have logged in to the server as user root in Secure Shell (SSH) mode. .

Procedure
Step 1 Run the following command to check whether the database service is started: # ps -ef |grep ora |grep -v usb-storage |grep -v hald-addon-storage |grep -v grep If the following information is displayed, the Oracle service is not running. Starting the Oracle database by referring to How Do I Start the Oracle Services.
oracle 17330 17196 ocssd.bin 0 Feb15 ? 00:00:00 /opt/oracle/oradb/home/bin/

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

70

M2000 Administrator Guide (x3850, SUSE10)


oracle 17471 17336 diskmon.bin -d -f 0 Feb15 ?

7 Managing M2000 Database


00:00:00 /opt/oracle/oradb/home/bin/

If the system output contains at least the following seven processes, it indicates that the database service and the monitor are started. If no output is displayed or only some of the following seven processes are displayed, it indicates that the database service is not started. For details about how to start the database, see How Do I Start the Oracle Services. l ora_pmon_ossdb l ora_dbw0_ossdb l ora_lgwr_ossdb l ora_ckpt_ossdb l ora_smon_ossdb l ora_arc0_ossdb l /opt/oracle/oradb/home/bin/tnslsnr LISTENER -inherit
oracle 7742 7603 ocssd.bin oracle 7878 7753 diskmon.bin -d -f oracle 11728 1 oracle 11730 1 oracle 11734 1 oracle 11736 1 oracle 11738 1 oracle 11740 1 oracle 11742 1 oracle 11744 1 oracle 11746 1 oracle 11748 1 oracle 11750 1 oracle 11752 1 oracle 14178 1 LISTENER -inherit oracle 15427 1 oracle 15429 1 oracle 15433 1 oracle 15435 1 oracle 15437 1 oracle 15439 1 oracle 15441 1 oracle 15443 1 oracle 15445 1 oracle 15447 1 oracle 15449 1 oracle 15451 1 oracle 15453 1 oracle 15455 1 oracle 15457 1 oracle 15459 1 oracle 15461 1 oracle 15464 1 oracle 15468 1 oracle 15470 1 oracle 15472 1 oracle 15474 1 oracle 15476 1 oracle 15478 1 oracle 15480 1 oracle 15482 1 oracle 15484 1 oracle 15486 1 oracle 15488 1 oracle 15490 1 oracle 15492 1 0 15:17 ? 0 15:17 ? 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 15:27 15:27 15:27 15:27 15:27 15:27 15:27 15:27 15:27 15:27 15:27 15:27 15:40 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 15:47 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00:00:00 /opt/oracle/oradb/home/bin/ 00:00:00 /opt/oracle/oradb/home/bin/ 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:01 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 asm_pmon_+ASM asm_vktm_+ASM asm_diag_+ASM asm_psp0_+ASM asm_dia0_+ASM asm_mman_+ASM asm_dbw0_+ASM asm_lgwr_+ASM asm_ckpt_+ASM asm_smon_+ASM asm_rbal_+ASM asm_gmon_+ASM /opt/oracle/oradb/home/bin/tnslsnr ora_pmon_ossdb ora_vktm_ossdb ora_diag_ossdb ora_dbrm_ossdb ora_psp0_ossdb ora_dia0_ossdb ora_mman_ossdb ora_dbw0_ossdb ora_dbw1_ossdb ora_dbw2_ossdb ora_dbw3_ossdb ora_dbw4_ossdb ora_dbw5_ossdb ora_dbw6_ossdb ora_dbw7_ossdb ora_dbw8_ossdb ora_dbw9_ossdb ora_dbwa_ossdb ora_dbwb_ossdb ora_dbwc_ossdb ora_dbwd_ossdb ora_dbwe_ossdb ora_dbwf_ossdb ora_dbwg_ossdb ora_dbwh_ossdb ora_dbwi_ossdb ora_dbwj_ossdb ora_lgwr_ossdb ora_ckpt_ossdb ora_smon_ossdb ora_reco_ossdb

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

71

M2000 Administrator Guide (x3850, SUSE10)


oracle 15494 1 0 15:47 ? oracle 15496 1 0 15:47 ? oracle 15498 1 0 15:47 ? oracle 15500 1 0 15:47 ? (LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) oracle 15502 1 0 15:47 ? oracle 15504 1 0 15:47 ? oracle 15506 1 0 15:47 ? oracle 15508 1 0 15:47 ? oracle 15524 1 0 15:47 ? oracle 15526 1 0 15:47 ? (LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) oracle 15541 1 2 15:47 ? oracle 15543 1 3 15:47 ? oracle 15545 1 3 15:47 ? oracle 15547 1 3 15:47 ? oracle 15549 1 2 15:47 ? oracle 15551 1 3 15:47 ? oracle 15553 1 3 15:47 ? oracle 15555 1 3 15:47 ? oracle 15557 1 2 15:47 ? oracle 15559 1 3 15:47 ? oracle 15561 1 3 15:47 ? oracle 15563 1 3 15:47 ? oracle 15565 1 2 15:47 ? oracle 15567 1 3 15:47 ? oracle 15569 1 3 15:47 ? oracle 15571 1 3 15:47 ? oracle 15579 1 4 15:47 ? oracle 15581 1 0 15:47 ? oracle 15583 1 0 15:47 ? oracle 15585 1 0 15:47 ? oracle 15587 1 0 15:47 ? oracle 15589 1 0 15:47 ? oracle 15591 1 0 15:47 ? (LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) oracle 15593 1 0 15:47 ? (LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) oracle 15595 1 0 15:47 ? oracle 15597 1 0 15:47 ? (LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) oracle 15602 1 0 15:47 ? oracle 15609 1 0 15:47 ? oracle 15653 1 0 15:47 ? oracle 15655 1 0 15:47 ? 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:01 00:00:01 00:00:01 00:00:00 00:00:01 00:00:01 00:00:01 00:00:00 00:00:01 00:00:01 00:00:01 00:00:00 00:00:01 00:00:01 00:00:01 00:00:01 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00

7 Managing M2000 Database


ora_rbal_ossdb ora_asmb_ossdb ora_mmon_ossdb oracle+ASM_asmb_ossdb (DESCRIPTION= ora_mmnl_ossdb ora_d000_ossdb ora_s000_ossdb ora_mark_ossdb ora_o000_ossdb oracle+ASM_o000_ossdb (DESCRIPTION= ora_p000_ossdb ora_p001_ossdb ora_p002_ossdb ora_p003_ossdb ora_p004_ossdb ora_p005_ossdb ora_p006_ossdb ora_p007_ossdb ora_p008_ossdb ora_p009_ossdb ora_p010_ossdb ora_p011_ossdb ora_p012_ossdb ora_p013_ossdb ora_p014_ossdb ora_p015_ossdb ora_arc0_ossdb ora_arc1_ossdb ora_arc2_ossdb ora_arc3_ossdb ora_o001_ossdb ora_o002_ossdb oracle+ASM_o001_ossdb (DESCRIPTION=

00:00:00 oracle+ASM_o002_ossdb (DESCRIPTION= 00:00:00 ora_o003_ossdb 00:00:00 oracle+ASM_o003_ossdb (DESCRIPTION= 00:00:00 00:00:00 00:00:00 00:00:00 ora_fbda_ossdb ora_qmnc_ossdb ora_q000_ossdb ora_q001_ossdb

----End

7.3 Starting Oracle Service


This section describes how to start the Oracle service.

Prerequisites
You have logged in to the server as user oracle in Secure Shell (SSH) mode.

Procedure
Step 1 Start the Oracle services. 1. Run the following command to start the ASM instance. > ORACLE_SID=+ASM > sqlplus / as SYSDBA
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 72

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

SQL> startup If the following information is displayed, the ASM instance has been started. Otherwise, the ASM instance is not started. In this case, contact Huawei technical support.
ASM instance started Total System Global Area 392511488 bytes Fixed Size 2159992 bytes Variable Size 365185672 bytes ASM Cache 25165824 bytes ASM diskgroups mounted

SQL> exit 2. Run the following command to start the ORACLE instance. > . ./.bash_profile > sqlplus / as SYSDBA SQL> startup If the following information is displayed, the ORACLE instance has been started. Otherwise, the ORACLE instance is not started. In this case, contact Huawei technical support.
ORACLE instance started. Total System Global Area 2.5254E+10 bytes Fixed Size 2183712 bytes Variable Size 2467098080 bytes Database Buffers 2.2750E+10 bytes Redo Buffers 34705408 bytes Database mounted. Database opened.

SQL> exit Step 2 Run the following commands to start the monitor: > lsnrctl start
The command completed successfully

If the previous information is displayed, the monitor is successfully started. ----End

7.4 Stopping Oracle Service


This section describes how to stop the Oracle service.

Prerequisites
l l You have logged in to the server as user oracle in Secure Shell (SSH) mode. M2000 services have been stopped. For details, see 6.4 Stopping the M2000 Services (SUSE).

Procedure
Step 1 Stop the monitor. 1. Run the following command to check the status of the monitor: > lsnrctl status
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 73

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

When the following information is displayed, the monitor is in running status:


Service "+ASM" has 1 instance(s). Instance "+ASM", status READY, has 1 handler(s) for this service... Service "+ASM_XPT" has 1 instance(s). Instance "+ASM", status READY, has 1 handler(s) for this service... Service "ossdb" has 1 instance(s). Instance "ossdb", status READY, has 1 handler(s) for this service... Service "ossdbXDB" has 1 instance(s). Instance "ossdb", status READY, has 1 handler(s) for this service... Service "ossdb_XPT" has 1 instance(s). Instance "ossdb", status READY, has 1 handler(s) for this service... The command completed successfully

2.

Run the following command to stop the monitor: > lsnrctl stop When the following information is displayed, the monitor is successfully stopped.
The command completed successfully

Step 2 Stop Oracle services: 1. Run the following command to stop the ORACLE instance. > sqlplus / as SYSDBA SQL> shutdown immediate If the following information is displayed, the ORACLE instance has been disabled. Otherwise, the ORACLE instance is not stopped. In this case, contact Huawei technical support.
Database closed. Database dismounted. ORACLE instance shut down.

SQL> exit 2. Run the following command to stop the ASM instance. > ORACLE_SID=+ASM > sqlplus / as SYSDBA SQL> shutdown immediate If the following information is displayed, the ASM instance has been disabled. Otherwise, the ASM instance is not stopped. In this case, contact Huawei technical support.
ASM diskgroups dismounted ASM instance shutdown

SQL> exit ----End

7.5 Checking Database Space


This describes how to use Oracle commands to view the database status, overall size of data files, and size of remaining space. This operation requires few system resources and does not affect system operation.

Prerequisites
You have logged in to the server as user oracle in Secure Shell (SSH) mode.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 74

M2000 Administrator Guide (x3850, SUSE10)

7 Managing M2000 Database

Procedure
Step 1 Run the following commands to view the overall size of database files: > sqlplus / as SYSDBA SQL> select tablespace_name, sum(bytes)/1024/1024 Total_Size_M from dba_data_files group by tablespace_name;
TABLESPACE_NAME TOTAL_SIZE_M ------------------------------------------------------------ -----------LOGDB_TBS 3072 OSSTEMPDB_TBS 2048 PMCOMDB_TBS 5120 SYSAUX 3072 UNDOTBS1 20480 EAMDB_TBS 2048 FARSDB_TBS 8192 SWMDB_TBS 12288 OMCDB_TBS 76800 SYSTEM 3072 ITFNDB_TBS 3072 TABLESPACE_NAME TOTAL_SIZE_M ------------------------------------------------------------ -----------PMDB_TBS 153600 FMDB_TBS 8192 SMDB_TBS 2048 TOPODB_TBS 2048 15 rows selected.

Step 2 Run the following command to view the size of the remaining space: SQL> select TABLESPACE_NAME, sum(bytes)/1024/1024 as free_size_M from dba_free_space group by tablespace_name ;
TABLESPACE_NAME FREE_SIZE_M ------------------------------------------------------------ ----------LOGDB_TBS 3069.6875 OSSTEMPDB_TBS 2047 PMCOMDB_TBS 5107.625 SYSAUX 2877.4375 UNDOTBS1 20158 EAMDB_TBS 2038.625 FARSDB_TBS 8190.5 SWMDB_TBS 12279.625 OMCDB_TBS 76654.875 SYSTEM 2741.75 ITFNDB_TBS 3068.375 TABLESPACE_NAME FREE_SIZE_M ------------------------------------------------------------ ----------PMDB_TBS 153599 FMDB_TBS 8180.5625 SMDB_TBS 2038.1875 TOPODB_TBS 2045.0625 15 rows selected.

----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

75

M2000 Administrator Guide (x3850, SUSE10)

8 Managing Disk Array and Hardware

Managing Disk Array and Hardware

About This Chapter


This describes how to manage the disks and hardwares on the M2000 server. 8.1 Viewing the CPU and Memory Usage of the M2000 Server (SUSE) This describes how to view the CPU and memory usage of the M2000 server. You can view information about the CPU usage, memory capacity, and free memory. If you find that the CPU or memory usage is abnormal, you can log in to the server and handle the problem in time. 8.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands This describes how to view the disk usage of the M2000 server by running the SUSE commands. This operation requires few system resources and does not affect the system operation. 8.3 Clearing the Disk Space of the M2000 Server (SUSE) This describes how to clear the disk space of the M2000 server. Before clearing the disk space, ensure that the files to be deleted are not required for future operations. Deleting a useful file by mistake may lead to a system operation error.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

76

M2000 Administrator Guide (x3850, SUSE10)

8 Managing Disk Array and Hardware

8.1 Viewing the CPU and Memory Usage of the M2000 Server (SUSE)
This describes how to view the CPU and memory usage of the M2000 server. You can view information about the CPU usage, memory capacity, and free memory. If you find that the CPU or memory usage is abnormal, you can log in to the server and handle the problem in time.

Prerequisites
l l You have logged in to the M2000 client. You are authorized with the relevant operation rights.

Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Server Monitor tab. The performance of the M2000 server is displayed, as shown in Figure 8-1. Figure 8-1 Server Monitor

NOTE

In the CPU Usage (%) column and the Memory Usage (%) column, the green icon indicates that the CPU usage or memory usage of the corresponding server is normal; the red icon indicates that the CPU usage or memory usage of the corresponding server is abnormal. In the case that you have set the server monitoring threshold for an item, the icon corresponding to the item changes from green to red when the value of the item reaches the threshold.

Step 3 (Optional) Click Save AS to save the monitoring data in a file. The file can be in any of the following four formats: TXT, HTML, XML, and CSV. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

77

M2000 Administrator Guide (x3850, SUSE10)

8 Managing Disk Array and Hardware

8.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands
This describes how to view the disk usage of the M2000 server by running the SUSE commands. This operation requires few system resources and does not affect the system operation.

Prerequisites
You have logged in to the M2000 server as user root.

Procedure
Step 1 Run the following query command: # df -k Step 2 View the disk usage. Generally, the disk usage is less than 80%, which indicates that the output Use% is less than 80%. If the disk usage is excessive, you need to clear the disk space. ----End

8.3 Clearing the Disk Space of the M2000 Server (SUSE)


This describes how to clear the disk space of the M2000 server. Before clearing the disk space, ensure that the files to be deleted are not required for future operations. Deleting a useful file by mistake may lead to a system operation error.

Context
During the routine operation and maintenance, back up and clear the following files to release more disk space: l l l l l Files storing the information about NEs and the M2000 server Software upgrade package and decompressed files Trace logs Backup files Temporary files created during the system operation

CAUTION
You can delete files when the server is running. Before deleting files, run the ls -l command to check the date when the files are generated. Do not delete the files generated on the current day.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

78

M2000 Administrator Guide (x3850, SUSE10)

8 Managing Disk Array and Hardware

Procedure
Step 1 Export the files that store the information about NEs and the M2000 server, and back up the files to a tape. l Files generated during automatic alarm dump Alarm dump files are stored in the /opt/oss/server/var/ThresholdExport/FM directory. l User log files User log dump files are stored in the /opt/oss/server/var/userlogs directory. l Core files generated by the system Core files refer to the files in the /opt/oss/server/var/logs/ directory. l Trace history files Trace history files are stored in the /opt/oss/server/var/logs/tracebak/ directory. Step 2 Delete the software update package and the decompressed files. After the software is successfully upgraded, you can delete the original upgrade package and the decompressed files. The upgrade package and decompressed files are stored in the folder named after the upgrade patch in the /export/home directory.

CAUTION
Generally, the decompressed upgrade files are stored in the /export/home directory. The folder name of the upgrade files is created according to the upgrade patch name. Sometimes, the folder is created in the /export/home/bak directory. Step 3 Delete trace Logs. Modify the value of tracebackupnum in the tracemonitor_svc_ex.xml file to reduce the number of trace backup files. Edit the tracemonitor_svc_ex.xml file in the /opt/oss/server/etc/conf/ directory to set the trace log monitor period, size limit, and number of backup files. The content of tracemonitor_svc_ex.xml is as follows:
<?xml version="1.0" encoding="utf-8"?> <tracemonitor name="tracemonitor" mount="/imap/common/tracemonitor"> <!-- CCB-ITEM checktracetime indicates that how long trace file will be checked! Min value is 300 seconds! --> <param name="checktracetime">300</param> <!-- CCB-ITEM tracebackupnum indicates the max number of reserved trace file! --> <param name="tracebackupnum">50</param> </tracemonitor>

In checktracetime, you can set the trace log monitor period. The system checks the trace file at the regular interval of 300s. In tracebackupnum, you can set the number of backup trace files for each process in the /opt/oss/server/var/logs/tracebak directory. For a process, if the number of backup trace files in the tracebak directory exceeds the preset value, the system automatically deletes the earliest trace files. Step 4 Clear the backup files. l After the upgrade, delete the backup files for the upgrade or copy them to a tape.
Issue Draft A (2012-02-27) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 79

M2000 Administrator Guide (x3850, SUSE10)

8 Managing Disk Array and Hardware

l Periodically back up all the files in the /export/home/backup/omc directory to tapes. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

80

M2000 Administrator Guide (x3850, SUSE10)

9 Managing License

9
About This Chapter

Managing License

This describes how to query and replace the license file on the M2000 server through the M2000 client. 9.1 Querying the M2000 License This topic describes how to query the license file on the M2000 server through the M2000 client. 9.2 Updating the M2000 License This topic describes how to replace the M2000 license file on the M2000 server through the client.

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

81

M2000 Administrator Guide (x3850, SUSE10)

9 Managing License

9.1 Querying the M2000 License


This topic describes how to query the license file on the M2000 server through the M2000 client.

Procedure
Step 1 Choose License > OSS License Management > License Information. Step 2 In the License Information dialog box, query the license information about resources and functions on the Resource Control Item and Function Control Item tabs. ----End

9.2 Updating the M2000 License


This topic describes how to replace the M2000 license file on the M2000 server through the client.

Context
l l l The version of the license that you applied for must be the same as the version of the M2000. Before the licenses expire, the M2000 displays a warning periodically. The valid time for the license that is uniformly used in M2000 contains two fields: Expiry (Days) and End Time. If both the fields exist, the value of Expiry(Days) is valid.

Procedure
Step 1 Choose License > OSS License Management > License Information. Step 2 In the License Information dialog box, click Update License. Step 3 In the Open dialog box, select the new license file(*.dat or *.txt license file), and then click Open. Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then click OK. ----End

Issue Draft A (2012-02-27)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

82

You might also like