M2000 Administrator Guide (x3850, SUSE10)(V200R012C00_Draft a)(PDF)-En

M2000V200R012C00

Administrator Guide (x3850,SUSE10)

Issue Draft A

Date 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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

i

http://www.huawei.com

mailto:[email protected]

About This Document

OverviewThis document is intended for the M2000 administrator. It is applicable to the IBM x3850 X5server and based on the SUSE Linux operating system and the Oracle database. In addition, itprovides 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 usageof frequently used commands and tools.

Product VersionProduct versions corresponding to this document are as follows:

Product Name Product Version

M2000 V200R012

Intended AudienceThis 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.

Organization1 Routine Maintenance Items

This section describes the recommended maintenance items of the M2000.

2 Powering On/Off the System

M2000Administrator Guide (x3850, SUSE10) About This Document


ii

This describes the procedures for powering on and off the M2000 system when IBM x3850 X5acts 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-layerNTP 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 theM2000 server can function properly.

7 Managing M2000 Database

This chapter describes how to manage the M2000 database. This chapter also describes theconcepts of the M2000 database and procedures on how to view the database status, start or stopthe 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 theM2000 client.

ConventionsSymbol 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 notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.



iii

Symbol Description

Provides additional information to emphasize or supplementimportant points of the main text.

General Conventions

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

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



iv


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare 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 Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.



v

Contents

About This Document.....................................................................................................................ii

1 Routine Maintenance Items........................................................................................................1

2 Powering On/Off the System......................................................................................................22.1 Powering on the System Securely......................................................................................................................32.2 Powering off the System Securely......................................................................................................................5

3 Configuring the Parameters of the M2000 Server...................................................................83.1 Changing the IP Address of the M2000 Server..................................................................................................9

4 Configuring the NTP Service....................................................................................................124.1 Methods for Configuring the NTP Service on the M2000 Server....................................................................134.2 Setting the M2000 Server as the NTP Client...................................................................................................144.3 Setting the M2000 Server as an Intermediate-Layer NTP Server....................................................................164.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE)...........................................18

5 Managing M2000 Users..............................................................................................................205.1 User Type.........................................................................................................................................................215.2 Changing the Password of User root................................................................................................................255.3 Changing the Password of User ossuser...........................................................................................................265.4 Changing the Password of User ftpuser...........................................................................................................275.5 Changing the Password of User oracle.............................................................................................................285.6 Changing the Password of User DB.................................................................................................................29

6 Managing the M2000 Processes and Services........................................................................316.1 Introduction to M2000 Processes and Services................................................................................................32

6.1.1 3rdTool_agent Process............................................................................................................................326.1.2 adn_agent Process....................................................................................................................................326.1.3 adss_agent Process..................................................................................................................................326.1.4 antenna_agent Process.............................................................................................................................326.1.5 ce_agent Process......................................................................................................................................336.1.6 cmdc_agent Process.................................................................................................................................336.1.7 cmengine_agent Process..........................................................................................................................336.1.8 cmeserver_agent Process.........................................................................................................................336.1.9 cmexp_agent Process...............................................................................................................................346.1.10 cmserver_agent Process.........................................................................................................................34

M2000Administrator Guide (x3850, SUSE10) Contents


vi

6.1.11 corba_agent Process..............................................................................................................................346.1.12 cpm_agent Process................................................................................................................................346.1.13 dam Process...........................................................................................................................................356.1.14 datacollectorsvr Process........................................................................................................................356.1.15 DCServer Process..................................................................................................................................356.1.16 devdoc_agent Process............................................................................................................................356.1.17 dsXXXX agent Process...........................................................................................................................356.1.18 eam_agent Process.................................................................................................................................366.1.19 Eml_PerfSvr Process.............................................................................................................................366.1.20 Eml_PubSvr Process..............................................................................................................................366.1.21 fars_agent Process.................................................................................................................................366.1.22 fmmedXXXX_agent Process..................................................................................................................376.1.23 fmnotify_agent Process.........................................................................................................................376.1.24 FMPreServiceXXXX_agent Process......................................................................................................376.1.25 fnlicense_agent Process.........................................................................................................................386.1.26 gem_agent Process................................................................................................................................386.1.27 glmssyn_agent Process..........................................................................................................................386.1.28 ifms_agent Process................................................................................................................................386.1.29 InventoryDM Process............................................................................................................................396.1.30 ipm_agent Process.................................................................................................................................396.1.31 irp_agent Process...................................................................................................................................396.1.32 itm_agent Process..................................................................................................................................406.1.33 lic_agent Process...................................................................................................................................406.1.34 log_agent Process..................................................................................................................................406.1.35 maintain_agent Process.........................................................................................................................416.1.36 manager_agent Process..........................................................................................................................416.1.37 mc Process.............................................................................................................................................416.1.38 medXXXX_agent Process.......................................................................................................................416.1.39 ncc0X01_agent Process.........................................................................................................................426.1.40 necomm_agent Process..........................................................................................................................426.1.41 nelicense_agent Process........................................................................................................................426.1.42 nemgr_ptn Process.................................................................................................................................436.1.43 nemgr_rtn Process.................................................................................................................................436.1.44 neproxy Process.....................................................................................................................................436.1.45 neuser_agent Process.............................................................................................................................436.1.46 ngnffs_agent Process.............................................................................................................................436.1.47 ngnni112_agent Process........................................................................................................................436.1.48 ngnnis_agent Process.............................................................................................................................446.1.49 ngntestmanage_agent Process...............................................................................................................446.1.50 nhcservice_agent Process......................................................................................................................446.1.51 nicservice_agent Process.......................................................................................................................446.1.52 nimserver_agent Process.......................................................................................................................44



vii

6.1.53 nms_mml_agent Process.......................................................................................................................456.1.54 partition_agent Process..........................................................................................................................456.1.55 pm_agent Process..................................................................................................................................456.1.56 PMDataSynchronizer Process...............................................................................................................456.1.57 pmengine0X01_agent Process...............................................................................................................456.1.58 pmexp_agent Process............................................................................................................................466.1.59 pmmon_agent Process...........................................................................................................................466.1.60 PMSDm Process....................................................................................................................................466.1.61 porttrunk_agent Process........................................................................................................................466.1.62 PQMDm Process...................................................................................................................................476.1.63 proxy_agent Process..............................................................................................................................476.1.64 PRSAssistantService_agent Process......................................................................................................476.1.65 prsdc_agent Process...............................................................................................................................476.1.66 prsfs_agent Process................................................................................................................................476.1.67 prsreport_agent Process.........................................................................................................................486.1.68 prssum_agent Process............................................................................................................................486.1.69 rn_agent Process....................................................................................................................................486.1.70 RouterMgrDm Process..........................................................................................................................486.1.71 ScriptModuleService_agent Process.....................................................................................................496.1.72 scriptserver_agent Process.....................................................................................................................496.1.73 SecurityMgrDm Process........................................................................................................................496.1.74 sm_agent Process...................................................................................................................................496.1.75 snm_agent Process.................................................................................................................................496.1.76 snmp_agent Process...............................................................................................................................496.1.77 son_agent Process..................................................................................................................................506.1.78 sso_agent Process..................................................................................................................................506.1.79 swm_agent Process................................................................................................................................506.1.80 threshold_agent Process........................................................................................................................506.1.81 toolkit Process........................................................................................................................................516.1.82 trapdispatcher Process...........................................................................................................................516.1.83 TXTNBIDm Process.............................................................................................................................516.1.84 uap_agent Process..................................................................................................................................516.1.85 uflight_dispatcher Process.....................................................................................................................516.1.86 umgupdsvr_agent Process.....................................................................................................................526.1.87 UniteUitlDM Process............................................................................................................................526.1.88 xftpXX01_agent Process........................................................................................................................526.1.89 Trace Server Services and Processes.....................................................................................................526.1.90 Processes and Services Related to Each Northbound Interface.............................................................546.1.91 Checking the Status of the M2000 Processes........................................................................................54

6.2 Viewing the Running Status of M2000 Services (SUSE)................................................................................556.3 Starting the M2000 Server (SUSE)..................................................................................................................576.4 Stopping the M2000 Services (SUSE).............................................................................................................58



viii

7 Managing M2000 Database........................................................................................................597.1 Introduction to the M2000 Database (Oracle, ATAE).....................................................................................60

7.1.1 omcdb......................................................................................................................................................607.1.2 logdb........................................................................................................................................................627.1.3 smdb.........................................................................................................................................................627.1.4 topodb......................................................................................................................................................637.1.5 fmdb.........................................................................................................................................................647.1.6 pmdb........................................................................................................................................................647.1.7 swmdb......................................................................................................................................................657.1.8 pmcomdb.................................................................................................................................................667.1.9 itfndb........................................................................................................................................................677.1.10 farsdb.....................................................................................................................................................687.1.11 osstempdb..............................................................................................................................................697.1.12 eamdb.....................................................................................................................................................69

7.2 Checking Oracle Services.................................................................................................................................707.3 Starting Oracle Service.....................................................................................................................................727.4 Stopping Oracle Service...................................................................................................................................737.5 Checking Database Space.................................................................................................................................74

8 Managing Disk Array and Hardware......................................................................................768.1 Viewing the CPU and Memory Usage of the M2000 Server (SUSE)..............................................................778.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands...............................................788.3 Clearing the Disk Space of the M2000 Server (SUSE)....................................................................................78

9 Managing License........................................................................................................................819.1 Querying the M2000 License...........................................................................................................................829.2 Updating the M2000 License...........................................................................................................................82



ix

1 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 deletemaintenance items according to your requirements.

Table 1-1 Maintenance item list

No. Item Frequency

1 6.2 Viewing the Running Status ofM2000 Services (SUSE)

Daily

2 7.2 Checking Oracle Services Daily

3 7.5 Checking Database Space Monthly

4 8.1 Viewing the CPU and MemoryUsage of the M2000 Server (SUSE)

Daily

5 8.2 Viewing the Disk Usage of theM2000 Server by Running SUSECommands

Weekly

6 9.1 Querying the M2000 License Monthly

M2000Administrator Guide (x3850, SUSE10) 1 Routine Maintenance Items


1

2 Powering On/Off the System

About This Chapter

This describes the procedures for powering on and off the M2000 system when IBM x3850 X5acts as the M2000 server.

2.1 Powering on the System SecurelyThis section describes how to power on the M2000 server and related cautions.

2.2 Powering off the System SecurelyThis section describes the procedure for powering off the M2000 hardware devices and relatednotes when the IBM x3850 X5 functions as the M2000 server.

M2000Administrator Guide (x3850, SUSE10) 2 Powering On/Off the System


2

2.1 Powering on the System SecurelyThis section describes how to power on the M2000 server and related cautions.

Prerequisitesl 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) mustbe disabled.

l After the cabinet is powered on, the device power switch is connected to the cabinet powercontrol panel.

Context

The system can be powered on using either one of the following methods:

l Power on the system using the power switch of the server.l 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 Nameand IP Address and Planning Users.

Procedurel 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



3

2. Check the power indicator status of the server after power on, and steady greenindicates the server is running properly.

l Power on the system using IMM.1. Connect the PC and the M2000 server through the local area network (LAN) switch.

a. Connect the system management network port on the M2000 server to thenetwork interface on the LAN switch using straight-through cables.

b. Connect the PC to the network interface on the LAN Switch using straight-through cables.

c. Set the IP address of the PC on the same network segment (192.168.70.xx forexample) as the IP address of the system management network port on theM2000 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.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. Type the initial user name USERID and password PASSW0RD. 0 in PASSW0RDis the digit 0, not the letter O. Click Login to access the Welcome page.

4. Click Continue to access the IMM home page.5. In the navigation tree, choose System > Tasks > Remote Control.6. In the displayed window, select the Use the ActiveX Client with Microsoft Internet

Explorer, and then click Start Remote Control in Multi-User Mode.7. In the displayed window, choose Tools > Power > On.8. In the displayed window, click Yes.

After the system is powered on, a power-on page is displayed, as shown in Figure2-2.



4

Figure 2-2 Startup page

----End

2.2 Powering off the System SecurelyThis section describes the procedure for powering off the M2000 hardware devices and relatednotes when the IBM x3850 X5 functions as the M2000 server.

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

ContextTo securely power off the system, disable the M2000 service, the database interception anddatabase 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 M2000Services (SUSE). Stop the M2000 services if they are running. For how to stop the M2000services, see 6.4 Stopping the M2000 Services (SUSE).

If M2000 service is stopped, run the following command to switch to user root:



5

> 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 disabledsuccessfully. Otherwise, the database interception is not disabled. In this case, contactHuawei 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 Huaweitechnical 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


If the following information is displayed, the ASM instance has been disabled.Otherwise, the ASM instance is not stopped. In this case, contact Huawei technicalsupport.ASM diskgroups dismountedASM instance shutdown

SQL> exit

4. Run the following command to exit user oracle.



6

> 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 informationpane 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



7

3 Configuring the Parameters of the M2000Server

About This Chapter

This describes how to set the parameters of the M2000 server.

3.1 Changing the IP Address of the M2000 ServerThis section describes how to change the IP addresses of the M2000 servers to ensure that theIP addresses of the servers meet the requirements.

M2000Administrator Guide (x3850, SUSE10) 3 Configuring the Parameters of the M2000 Server


8

3.1 Changing the IP Address of the M2000 ServerThis section describes how to change the IP addresses of the M2000 servers to ensure that theIP addresses of the servers meet the requirements.

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

Contextl When you are changing the IP addresses of the M2000 servers, the performance data and

alarm data of the managed NEs cannot be processed.l 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.l 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 theNEs. When changing the IP addresses of the M2000 servers, you need to notify the NEmaintenance engineers and ask them to modify relevant plans and update the IP addressesof 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 anexample.

$ ping 192.168.8.12l 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 M2000Services. 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 Oracleis 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



9

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

------------------------------------------------------------------ Welcome to use Modify tool Modify Tool (2.0.0)------------------------------------------------------------------------------------------------------------------------------------Please select a(n) operator type1--IP2--Database password3--Password of ftpuserR--ReturnQ--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.181Please 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 previousaddresses 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 notchange 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 promptedto 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 IPaddresses 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 promptedto 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. Pleasewait.



10

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

If the system output contains failed, you can infer that the change fails. Contact Huaweitechnical 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 theOracle and M2000 services.

NOTE

If the login fails or the Oracle and M2000 services are abnormal after the server is restarted, contact Huaweifor 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



11

4 Configuring the NTP Service

About This Chapter

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

Context

CAUTIONl 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 thissection and proceed to the follow-up sections.

4.1 Methods for Configuring the NTP Service on the M2000 ServerThis section describes the methods for configuring the Network Time Protocol (NTP) serviceon the M2000 server.

4.2 Setting the M2000 Server as the NTP ClientThis section describes how to set the M2000 server as an NTP client to synchronize time withan NTP server.

4.3 Setting the M2000 Server as an Intermediate-Layer NTP ServerThis section describes how to set the M2000 server as an intermediate-layer NTP server. Anintermediate-layer NTP server synchronizes time with the upper-layer NTP server, and providestime 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.

M2000Administrator Guide (x3850, SUSE10) 4 Configuring the NTP Service


12

4.1 Methods for Configuring the NTP Service on theM2000 Server

This section describes the methods for configuring the Network Time Protocol (NTP) serviceon 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 Reference

Set the M2000 server as an NTP client. 4.2 Setting the M2000 Server as the NTP Client

Set the M2000 server as an intermediate-layer NTP server.

4.3 Setting the M2000 Server as anIntermediate-Layer NTP Server

Table 4-2 Advantages and disadvantages of each method

Method

Reliability Security SystemResource Usage

Cost

Set theM2000server asan NTPclient.

Higher reliabilitybecause anindependentintermediate-layer NTP serveris deployedindependently

Higher security ofthe timesynchronizationnetwork becausethe M2000 serverserves as an NTPclient andsynchronizes timewith theintermediate-layer NTP server

Less systemresources requiredbecause theM2000 serversynchronizes timewith the upper-layer NTP serverbut does notprovide timereference for NTPclients

Expensivebecause you haveto deploy anindependentintermediate-layer NTP server

Set theM2000server asanintermediate-layerNTPserver.

Weaker reliabilitybecause theM2000 server alsoperformsmaintenance,upgrade, andbackup operationsfrequently

Timesynchronizationfailed when theM2000 serverbecomes faulty

More systemresources requiredbecause theM2000 serversynchronizes timewith the upper-layer NTP serverand provides timereference for NTPclients

Cost effectivebecause theM2000 server alsoserves as anintermediate-layer NTP server



13

4.2 Setting the M2000 Server as the NTP ClientThis section describes how to set the M2000 server as an NTP client to synchronize time withan NTP server.

Prerequisitesl The time zone of the M2000 server are set correct.l You have obtained the IP address of the NTP server.l The network between the M2000 server and the NTP server is running properly.l 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 toChanging the Time Zone and Time of the M2000 Server (SUSE).

Step 2 If the M2000 services are running, stop them.1. Check the status of the M2000 services.

For details, see How Do I Check the Status of the M2000 Services?.2. Stop M2000 services.

For details, see How to Stop M2000 Services.

Step 3 If the Oracle services are running, stop them.1. Check the status of the Oracle services.

For details, see 7.2 Checking Oracle Services.2. 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, andthen press Enter.

Step 9 Use Tab, ↑, and ↓ to select During Boot on Automatically Start NTP Daemon. PressEnter for confirmation.



14

NOTE

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 serverin Address. Use the Tab key to select Test to check whether the input IP address is valid, asshown 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-layerNTP server is correct and the network connections. Perform this step again after the problemis 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 followinginformation 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 forassistance.

----End



15

4.3 Setting the M2000 Server as an Intermediate-Layer NTPServer

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

Prerequisitesl The top-layer NTP server has been configured, and the IP address of the top-layer NTP

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

ContextThe NTP server for the M2000 server uses the NTP. A server running on the Windows operatingsystem uses the SNTP. Therefore, it cannot serve as the NTP server for the M2000 server.

ProcedureStep 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 toChanging the Time Zone and Time of the M2000 Server (SUSE).

Step 2 If the M2000 services are running, stop them.1. Check the status of the M2000 services.

For details, see How Do I Check the Status of the M2000 Services?.2. Stop M2000 services.

For details, see How to Stop M2000 Services.

Step 3 If the Oracle services are running, stop them.1. Check the status of the Oracle services.

For details, see 7.2 Checking Oracle Services.2. 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:



16

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

# 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 anintermediate-layer NTP server.

1. Run the following command to switch to the YaST Control Center window:

# yast

2. In the YaST Control Center window, use ↑ or ↓ to choose Network Services.

3. In the YaST Control Center window, use Tab and ↑ or ↓ to choose NTPConfiguration, and then press Enter.

4. Use Tab and ↑ or ↓ to choose During Boot under Automatically Start NTPDaemon, and then press Enter.

NOTE

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

5. Use the Tab key to select Advanced Configuration, and then press Enter.

6. Use the Tab key to select Undisciplined Local Clock (LOCAL), and use the Tab to selectDelete, and then press Enter.

7. In the displayed prompt dialog box, use the Tab key to select Yes, and then press Enter.

8. Use the Tab key to select Add, and then press Enter.

9. Use the Tab key to select Server, and then press Enter. If Server is selected, skip thisstep.

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 NTPserver 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 respondproperly. ", 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 whethernetwork 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 multipleNTP servers, you can set only one of them to prefer.

15. Use the Tab key to select OK, and then press Enter.



17

NOTE

If there are multiple NTP servers, repeat Step 7.8 through Step 7.15 to set the IP addresses of otherNTP 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 followinginformation 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 tothe top-layer NTP server:

# /usr/sbin/ntptrace

localhost: stratum 6, offset 0.000000, synch distance 0.950193192.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-layerNTP server) to the top-layer NTP server. The system can track the entire NTP synchronizationpath 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 ison 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 forassistance.

----End

Follow-up ProcedureAfter the server is set as an intermediate NTP server, set the NEs as NTP clients. For detailsabout 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 theM2000 Server (SUSE)

This describes how to check the running status of the NTP service on the M2000 server.



18

PrerequisitesYou 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 theM2000 server.

----End



19

5 Managing M2000 Users

About This Chapter

This describes how to manage OS users and DB users of the M2000 system.

5.1 User TypeThis section describes information about user OS and user DB involved in the operation of theM2000. User OS include user root, ossuser, ftpuser, and oracle. User DB includes usersystem and sys.

5.2 Changing the Password of User rootThis describes how to change the password of user root. In the M2000 HA system, the passwordof user root on the two nodes must be consistent. Thus, you must change the password of userroot on the active and standby nodes separately to ensure the password consistency.

5.3 Changing the Password of User ossuserThis describes how to change the password of user ossuser when you log in to the system asuser root. In the M2000 HA system, the password of user ossuser on the two nodes must beconsistent. Thus, you must change the password of user ossuser on the active and standby nodesseparately to ensure the password consistency.

5.4 Changing the Password of User ftpuserThis section describes how to change the password of user ftpuser.

5.5 Changing the Password of User oracleThis describes how to change the password of user oracle when you log in to the M2000 databaseas 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 nodesrespectively to ensure the password consistency.

5.6 Changing the Password of User DBThis section describes how to change the passwords of user DB.

M2000Administrator Guide (x3850, SUSE10) 5 Managing M2000 Users


20

5.1 User TypeThis section describes information about user OS and user DB involved in the operation of theM2000. User OS include user root, ossuser, ftpuser, and oracle. User DB includes usersystem and sys.

Table 5-1 and Table 5-2 describe user OS and user DB for the M2000.



21

Table 5-1 User OS

User Name Default Password Usage

Authority

UserGroup

ShellResolutionProgram

Directory

User OS root root Userrootis thesuperuserof thesystem.Userrootisauthorizedtocontrol allresources,createotheruseraccounts,assignauthority tootherusers,andperform allsystemoperations.

User roothas thehighestauthorityof thesystem.User rootisauthorized to installanduninstallM2000serverapplications and tostart andstopM2000services.

other,bin,sys,adm,uucp,mail,tty,lp,nuucp,daemon,anduser.root

/bin/bash

/root



22


Authority

UserGroup


Directory

ossuser Changeme_123 Userossuser isresponsiblefortheoperationandmaintenance oftheM2000.

Userossuser isauthorized toaccess thedatabaseandperformoperationandmaintenance.Userossuser isnotallowedto installoruninstallM2000serverapplications.

root,sys,ossgroup,dba,andoinstall

/bin/bash

/export/home/ossuser



23


Authority

UserGroup


Directory

oracle Changeme_123 Useroracle isusedtoinstalltheOracledatabase.Useroracle iscreatedbefore thedatabase isinstalled.

Useroracle isauthorized toaccess thedatabaseandperformoperations over theOracledatabase.

oinstall,dba,andossgroup

/bin/bash

/opt/oracle

ftpuser Changeme_123 ftpuser is ausertoupload filesto theserveranddownloadfilesfromtheserver.

Userftpuser isauthorized toperformsoftwaremanagement andfiletransferfor NEs.

ossgroup,dialout,video

/bin/bash

/export/home/sysm



24

Table 5-2 User DB

User Name DefaultPassword

Usage Authority

system Changeme_123

User system is theadministrator of theOracle database. Usersystem is responsible forthe management, upgrade,and maintenance of theOracle database, and isused to install the M2000server applications.

User system has thehighest authority of thedatabase.

sys Changeme_123

User sys is the super userof the Oracle database.User sys is responsible forthe management andoperation of the Oraclesystem, and is used torestore the Oracledatabase applications.

User sys is the super userof the database.

5.2 Changing the Password of User rootThis describes how to change the password of user root. In the M2000 HA system, the passwordof user root on the two nodes must be consistent. Thus, you must change the password of userroot on the active and standby nodes separately to ensure the password consistency.

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

ContextThe 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 The password contains at least one uppercase letter.l The password contains at least one lowercase letter.l The password contains at least one digit.l The password contains at least one special character.l The password does not contain the user name.

NOTE

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



25

ProcedureStep 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 ossuserThis describes how to change the password of user ossuser when you log in to the system asuser root. In the M2000 HA system, the password of user ossuser on the two nodes must beconsistent. Thus, you must change the password of user ossuser on the active and standby nodesseparately to ensure the password consistency.

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

ContextThe 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 The password contains at least one uppercase letter.l The password contains at least one lowercase letter.l The password contains at least one digit.l The password contains at least one special character.l The password does not contain the user name.

NOTE


ProcedureStep 1 Run the following command to change the password:

# passwd ossuser

Changing password for ossuser.





26

Password changed.

----End

5.4 Changing the Password of User ftpuserThis section describes how to change the password of user ftpuser.

Prerequisitesl The new password of user ftpuser is available.l 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 M2000Services (SUSE). Stop the M2000 services if they are running. For details on how to stop theM2000, 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. Ifthe 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.



$ ./modify.sh

The following message is displayed:


Step 4 Type 3, and then type the new password of user ftpuser at the following prompt. Type the newpassword 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.



27

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 oracleThis describes how to change the password of user oracle when you log in to the M2000 databaseas 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 nodesrespectively to ensure the password consistency.

Prerequisitesl The new password of the operating system user oracle is available.

l 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 The password contains at least one uppercase letter.

l The password contains at least one lowercase letter.

l The password contains at least one digit.

l The password contains at least one special character.

l The password does not contain the user name.

NOTE




28

ProcedureStep 1 Run the following command to change the password of user Oracle:

# passwd oracle

Changing password for oracle.



Password changed.

----End

5.6 Changing the Password of User DBThis section describes how to change the passwords of user DB.

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

ProcedureStep 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 theM2000 Services (SUSE).

Step 2 Check whether the Oracle is started by referring to 7.2 Checking Oracle Services. If any Oracleservice 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.



$ ./modify.sh

Choose 2--Database password after the following message is displayed:


2. Based on the displayed messages, enter the name of the Oracle database server and the oldand new passwords of user system. Press Enter.



29

------------------------------------------------------------------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 toperform 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 performoperations 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



30

6 Managing the M2000 Processes and Services

About This Chapter

This describes how to manage the M2000 processes so that the processes and services on theM2000 server can function properly.

6.1 Introduction to M2000 Processes and ServicesWhen the M2000 is running, the M2000 server automatically starts the processes related to theM2000 system. Each process provides different services and functions. In the ATAE clustersystem, 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 operationrequires 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 serviceis already started, the system does not handle the service. Actually, the system starts only theinactive services.

6.4 Stopping the M2000 Services (SUSE)This describes how to stop the M2000 services. After the M2000 services are stopped, theM2000 processes are stopped. In this situation, NE performance data and alarm data cannot beprocessed. After the services are resumed, the M2000 updates the data with the NEs andprocesses the data.

M2000Administrator Guide (x3850, SUSE10) 6 Managing the M2000 Processes and Services


31

6.1 Introduction to M2000 Processes and ServicesWhen the M2000 is running, the M2000 server automatically starts the processes related to theM2000 system. Each process provides different services and functions. In the ATAE clustersystem, 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 ProcessThis 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 datacenter.

Required services: ScriptServer

6.1.2 adn_agent ProcessThis 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 variousfunctions for newly constructed NodeBs, such as remote automatic activation and automaticfault 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 ProcessThis 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 securityof 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.


6.1.4 antenna_agent ProcessThis 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 thefaults related to GBSS antennas.



32

Required service: EAMService.

6.1.5 ce_agent ProcessThis 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 NMSto 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 ProcessThis section describes the CmDcService service and dependent services. CmDcService isprovided by the cmdc_agent process.

The cmdc_agent process provides the CmDcService service.

The CmDcService service provides the functions such as data access interface, synchronizationmanagement, 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 ProcessThis 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 isindependent 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 ProcessThis 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 slavenodes.

You can disable the service when it is not required.

Required service: TopoAdapterService.



33

6.1.9 cmexp_agent ProcessThis 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 theconfiguration 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 byusing 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 ProcessThis 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 managementis independent of NEs or managed objects.

The CMServer provides channels for issuing MML commands and helps to receive thesupplementary messages reported automatically by NEs.

The CMServer provides the function of managing object groups and enables the M2000 toautomatically and remotely commission the NodeB upgrade.

In the ATAE cluster system, you can distribute the cmserver_agent process to different slavenodes.


Required services: TopoAdapterService

6.1.11 corba_agent ProcessThis 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 ProcessThis section describes the services and functions provided by the cpm_agent process.

The cpm_agent process provides the CPMService service, that is, the pool configurationmanagement service.

The Pool configuration management service provides users with the following functions:



34

l Creating a pooll Checking pool alarmsl Measuring the performance of a pooll Monitoring the load of a pool in real timel Displaying the pool topologyl Setting pool parametersl Checking the NE data in a pooll Checking the MSC Server or MSCe of a specific user



6.1.13 dam ProcessThis 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 ProcessThis 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 ofNE failure and helps to locate faults quickly


6.1.15 DCServer ProcessThis section describes the services and functions provided by the DCServer process.

This process provides the function of NE software management and disaster recoverymanagement. The detailed functions are NE software upgrade, patch installation, data backupand recovery for disaster recovery, and plug-andplay automatic upgrade of case-shapedequipment.


6.1.16 devdoc_agent ProcessThis 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.


6.1.17 dsXXXX agent ProcessThis section describes the services and functions provided by the dsXXXX_agent process.

The dsXXXX_agent process provides the DesktopServiceXXXX service.



35

Some typical process names are ds0101_agent and ds0102_agent. The corresponding servicenames 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 asthe Java GUI client and the Web client.

In the ATAE cluster system, you can deploy this process on the master node and several slavenodes. 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. Onthe second slave node, some typical process names are ds0301_agent and ds0302_agent. Youcan 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 ProcessThis section describes the services and functions provided by the eam_agent process.

The eam_agent process provides the EAMService, TopoAdapterService, and TopoServiceservices.

The EAMService service provides the function of NE access management and maintains aglobally 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 userswho use the earlier versions can use the topology function. The TopoAdapterService servicedepends on the EAMService, TopoService, LogService, and SecurityService services.

The TopoService service can maintain the relation between the devices in the subnet, create anddelete subnets, nodes, and topology node, and move nodes among subnets. The TopoServiceservice depends on the EAMService services.

6.1.19 Eml_PerfSvr ProcessThis section describes the services and functions provided by the Eml_PerfSvr process.

This process provides the transfer-domain performance management function.


6.1.20 Eml_PubSvr ProcessThis 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.


6.1.21 fars_agent ProcessThis section describes the service and function provided by the fars_agent process.

The fars_agent process provides the FarsService.



36

The FarsService provides the function of tracing data collection, data analysis, and datacollection 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 normallyduring the operation of the M2000.

Dependent service: none.

6.1.22 fmmedXXXX_agent ProcessThis 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 arenamed 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 thefirst slave server, the process names are fmmed0201_agent and fmmed0202_agent. On thesecond slave server, the process names are fmmed0301_agent and fmmed0302_agent. The samerule applies to the other slave servers.


Independent service: none.

6.1.23 fmnotify_agent ProcessThis 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.


Disable FMNotify when the real-time alarm forwarding function is not required.

Required services: LicenseService.

6.1.24 FMPreServiceXXXX_agent ProcessThis section describes the services and functions provided by the FMPreServiceXXXX_agentprocess.

The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service.

The FMPreServiceXXXX_agent process is a multi-instance process. XXXX refers to the processnumber.

The FMPreServiceXXXX service provides the function of prehandling faults.

In the ATAE cluster system, you can deploy the FMPreServiceXXXX_agent process on themaster node and several slave nodes. You can also deploy multiple FMPreServiceXXXX_agent



37

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


6.1.25 fnlicense_agent ProcessThis 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 licenseauthorization information about EMS. The number of purchased licenses determines the numberof available resources and whether the user can use a specific functional component.


6.1.26 gem_agent ProcessThis 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 statisticsand analysis on the energy consumption of devices.


6.1.27 glmssyn_agent ProcessThis 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 communicationchanges from the Group and List Management Server (GLMS) and then applies the informationto 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.


6.1.28 ifms_agent ProcessThis 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 functionsof 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.



38


6.1.29 InventoryDM ProcessThis section describes the services and functions provided by the InventoryDM process.

This process provides the inventory data management function, such as physical resourcemanagement, cable management, and customer management.

Required services: eam_agent,ifms_agent.

6.1.30 ipm_agent ProcessThis 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 runningcorrectly during the operation of the M2000.


6.1.31 irp_agent ProcessThis section describes the functions provided by the irp_agent process.

EPIRPThe EPIRP is subject to the entry point object. The entry point object is the first object that theNMS (Manager) accesses when the NMS interacts with the M2000 (Agent). The Agent providesa reference of an entry point object to the Manager, and the Manager obtains the reference ofthis entry point object in some way, for example, from the stored file. If the interface fornorthbound network management is not required, disable the EPIRP.

Basic IRP: None.

NotificationIRPNotificationIRP is used for subscribing to notifications and encapsulating notificationsubscription. If the function of subscription through the interface of northbound networkmanagement is not required, disable the NotificationIRP.

Basic IRP: EPIRP.

CSIRPCSIRP provides an interface for link monitoring.

The link monitoring enables you to supervise the status of links between the Manager and theAgent. In this way, the potential exceptions can be detected at the first time. If the function ofmonitoring through the interface of northbound network management is not required, disablethe CSIRP.

Basic IRP: EPIRP, and NotificationIRP.



39

KernelCMIRPKernelCMIRP provides an interface for public configuration management.

The public configuration management uses KernelCMIRP to carry out some common tasksduring the configuration, such as sending configuration objects, or adding, removing andmodifying notifications. If the function of public configuration management through theinterface of northbound network management is not required, disable the kernelCMIRP.

Basic IRP: EPIRP, and NotificationIRP.

BasicCMIRPBasicCMIRP controls the configuration management. BasicCMIRP is used for querying,modifying, adding, or removing network resource objects. If the function of configurationmanagement through the interface of northband network management is not enabled, disablethe BasicCMIRP.

Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, and KernelCMIRP.

AlarmIRPAlarmIRP is used for managing fault data. If the function of fault data management through theinterface of northbound network management is not required, disable the AlarmIRP.

Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, KernelCMIRP, and BasicCMIRP.

Required ServicesThe required service is the LicenseService.

6.1.32 itm_agent ProcessThis section describes the ItmService service and the dependent services by the itm_agentprocess.

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 ProcessThis 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.


6.1.34 log_agent ProcessThis section describes the services and functions provided by the log_agent process.



40

The log_agent process provides LogService and ForwardingService.

LogService records system-related operations in logs, and provides operation logs for otherservices or clients to query. By using LogService, you can also set and query the parameters fordumping system logs.

ForwardingService forwards the M2000 system logs to a third-party Syslog server according tostandard protocols.


6.1.35 maintain_agent ProcessThis topic describes the function of the MaintenanceService service, which is provided by themaintain_agent process.

The maintain_agent process provides the MaintenanceService service.

The MaintenanceService service enables the periodic backup of the important systemconfiguration files, database data, and real-time data of MOs.


During the M2000 operation, ensure that the maintain_agent process is operational.


6.1.36 manager_agent ProcessThis 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 theoperating system, software version of the client, software version of the server, client softwareversion matching the server software, and client upgrade information.



6.1.37 mc ProcessThis section describes the services and functions provided by the mc process.

This process provides the basic NE distribution service.


6.1.38 medXXXX_agent ProcessThis 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 basedon NE types and NE quantity. Some typical process names are med0101_agent, med0102_agent,



41

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 thenetwork devices from the M2000 system and also manages the related event interceptors. NEsof different types communicate with the M2000 system by using the corresponding NE enginesthrough various network management protocols. In addition, the MediationServiceXXXX servicecan 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 namesare med0201_agent, med0202_agent, and med0203_agent. On the third slave node, some typicalprocess names are med0301_agent, med0302_agent, and med0303_agent. You can infer theother process names similarly.


Dependent services: none

6.1.39 ncc0X01_agent ProcessThis 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, theprocess 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 theslave servers. The process names are ncc0101_agent, ncc0201_agent, ncc0301_agent and so on.


Independent service: none.

6.1.40 necomm_agent ProcessThis section describes the services and functions provided by the necomm_agent process.

The necomm_agent process provides the CommonLicService service and SSLManageServiceservice.

The CommonLicService service manages the information about NE license files, such asinvalidity, export, and adjustment information.

The SSLManageService service manages the SSL connections between the M2000 and NEs. Italso manages the SSL certificates used by the SSL connections.

The SSLManageService service depends on CommonLicService service.

6.1.41 nelicense_agent ProcessThis section describes the services and functions provided by the nelicense_agent process.

The nelicense_agent process provides the NeLicenseService service.



42

The NeLicenseService service manages NodeB licenses and implements the sharing of a licensebetween the NEs of the same type.

Required services: LogService.

6.1.42 nemgr_ptn ProcessThis section describes the services and functions provided by the nemgr_ptn process.

This process provides the function of managing Metro Ethernet PTN frame-shaped andcaseshaped NEs.


6.1.43 nemgr_rtn ProcessThis section describes the services and functions provided by the nemgr_rtn process.

This process provides the function of managing RTN series equipment.


6.1.44 neproxy ProcessThis section describes the services and functions provided by the neproxy process.

Data Collector NE Proxy Process


6.1.45 neuser_agent ProcessThis section describes the NeUserService service. NeUserService is provided by theneuser_agent process.

The neuser_agent process provides the NeUserService service.

The NeUserService service enables you to manage NE users. When the M2000 and NEs areconnected properly, you can manage NE users through the M2000. For example, you canauthenticate the login of NE users, deliver command rights and command group rights, andcustomize command groups.


6.1.46 ngnffs_agent ProcessThis section describes the NGNFullFillService service and dependent services.

The ngnffs_agent process provides the NGNFullFillService.

The NGNFullFillService service provides functions of managing management domains andprovisioning subscriber numbers.


6.1.47 ngnni112_agent ProcessThis section describes the services and functions provided by the ngnni112_agent process.



43

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 ProcessThis 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.


6.1.49 ngntestmanage_agent ProcessThis 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.


6.1.50 nhcservice_agent ProcessThis 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 ProcessThis 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. Thenicservice_agent process is available only after you have installed the network informationcollecting components.

If you plan to perform a network information collecting task, you must ensure this service isrunning properly.

Required service: ItmService and EAMService.

6.1.52 nimserver_agent ProcessThis section describes the NIMServer service and the dependent service. NIMServer is providedby the nimserver_agent process.

The nimserver_agent process provides the NIMServer service.



44

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 onlyprovides the functions to some WRAN configuration objectssuch as alarm statistics, query ofbasic configuration information, query of configuration link constitution and basic configurationinformation, and query of adjacent cells and channel assignment.


6.1.53 nms_mml_agent ProcessThis 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 issuesMML commands through the northbound MML transmission interface to managed NEs.

If the northbound MML transmission interface is used when the M2000 is running, ensure thatthe NMSMMLServer is running correctly. When the northbound MML transmission interfaceis not used, the NMSMMLServer is not disruptive to other services.

Required services: LogService.

6.1.54 partition_agent ProcessThis 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 ismanaged by its own process. In the presence of a large quantity of objects, the partitions aremanaged by various processes on different servers to balance the load.



6.1.55 pm_agent ProcessThis 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 isindependent of NEs or objects. Stop PMService if the performance management function is notrequired.


6.1.56 PMDataSynchronizer ProcessThis section describes the services and functions provided by the PMDataSynchronizer process.

This process provides the function of importing data in text files.


6.1.57 pmengine0X01_agent ProcessThis section describes the services and functions provided by the pmengine0X01_agent process.



45

The pmengine0X01_agent process provides the PMEngine0X01 service.

The pmengine0X01_agent process is a multi-instance process. 0X01 indicates the number of aprocess instance. The corresponding service of the pmengine0101_agent process isPMEngine0101.

This service provides the functions of querying and managing the ATAE cluster systemperformance.

In the ATAE cluster system, you can deploy this process on master node and different slavenodes. Some typical process names are pmengine0101_agent, pmengine0201_agent, andpmengine0301_agent. You can infer the other process names similarly.



6.1.58 pmexp_agent ProcessThis 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 isindependent of NEs or managed objects.


Stop PMExport when the function of exporting performance results is not required.


6.1.59 pmmon_agent ProcessThis 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 figuresand tables.

Required services: PMService

6.1.60 PMSDm ProcessThis section describes the services and functions provided by the PMSDm process.

This process provides the collector management function.


6.1.61 porttrunk_agent ProcessThis 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 theM2000 client through a specified port. You need not configure multiple ports on the firewall forcommunication.



46


6.1.62 PQMDm ProcessThis section describes the services and functions provided by the PQMDm process.

This process provides the function of grouping performance monitoring and display.


6.1.63 proxy_agent ProcessThis 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 runapplications of the NEs on the LMT .

Stop Proxyserver when the proxy function is not required.


6.1.64 PRSAssistantService_agent ProcessThis section describes the services and functions provided by the PRSAssistantService_agentprocess.

The PRSAssistantService_agent process provides the PRSAssistantService service.

The PRSAssistantService service provides the function of generating reports in .html, .csv or .xlsformat. 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 PRSReportServiceservice.


If you need to run the PRS module, the PRSReportService service cannot be stopped.


6.1.65 prsdc_agent ProcessThis 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 andperformance 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.


6.1.66 prsfs_agent ProcessThis section describes the services and functions provided by the prsfs_agent process.



47

The prsfs_agent process provides the PRSFsService service. That is, it provides the service forimporting report data.

The PRSFsService service provides the function of parsing configuration data files andperformance 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 ProcessThis 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.


If you need to run the PRS module, the PRSReportService service cannot be stopped.

Required services: LicenseService and ItmService.

6.1.68 prssum_agent ProcessThis 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 andscheduling the data.


If you need to run the PRS module, the PRSSumService service cannot be stopped.


6.1.69 rn_agent ProcessThis 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 orshort message.


6.1.70 RouterMgrDm ProcessThis section describes the services and functions provided by the RouterMgrDm process.

This process provides the function of managing Quidway routers.




48

6.1.71 ScriptModuleService_agent ProcessThis section describes the services and functions provided by the ScriptModuleService_agentprocess.

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 ProcessThis 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.


Required services: ItmService and SecurityService.

6.1.73 SecurityMgrDm ProcessThis section describes the services and functions provided by the SecurityMgrDm process.

This process provides the function of managing FW/USG, SIG, and SVN series securityequipment.


6.1.74 sm_agent ProcessThis 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 authorizedusers can gain access to sensitive resources.


Required services: EAMService and LicenseService

6.1.75 snm_agent ProcessThis section describes the SNMService service and dependent services.

The snm_agent process provides the SNMService.

The SNMService service provides signaling network management, including topologymanagement, port monitoring, and resource management.

Required services: TopoService and EAMService.

6.1.76 snmp_agent ProcessThis section describes the SnmpAgent service and the dependent services. The SnmpAgentservice is provided by the snmp_agent process.



49

The snmp_agent process provides the SnmpAgent service, that is, the northbound interfaceservice complying with the SNMP protocol.

The SnmpAgent service enables the upper-level NMS to obtain the information on the M2000such as alarm data, through the SNMP protocol.

Required services: LogService and LicenseService.

6.1.77 son_agent ProcessThis 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, suchas automatically detecting, configurating, and optimizing NEs. The DHCP module provides thefunction of automatically detecting the eNodeB, BWA, pBTS3701, NodeB, GSM Pico, PICOBTS, and TGW. The Easy Deployment System (EDS) module provides the function ofautomatically creating an LTE site. The Auto Neighbor Relation (ANR) module provides thefunctions of automatically detecting the neighboring cells of the LTE, querying neighboring cellparameters 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 bestopped.

Required service: none

6.1.78 sso_agent ProcessThis 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.


6.1.79 swm_agent ProcessThis 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 someNEs. It also provides the download, upload, activation, and rollback functions.



6.1.80 threshold_agent ProcessThis topic describes the function of the ThresholdService service provided by thethreshold_agent process and the service that the threshold_agent process depends on.

The threshold_agent process provides the ThresholdService service.



50

The ThresholdService service provides the threshold management function. For example, thisservice allows you to add, generate, and change a threshold. In addition, this service can generatethreshold alarms.

During the M2000 operation, ensure that the threshold_agent process is operational.

Required services: PMService.

6.1.81 toolkit ProcessThis section describes the services and functions provided by the toolkit process.

This process provides the service of upgrading boardlevel transmission equipment.


6.1.82 trapdispatcher ProcessThis 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 reportedby NEs monitored by the M2000. The trapdispatcher service forwards the Snmp Trap messagesthat 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 ProcessThis 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 formatthrough FTP.


6.1.84 uap_agent ProcessThis 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, whenusers cannot access the BAM server (make sure that the M2000 server normally connects to theBAM), the M2000 client can be started through the agent. The uap_agent process also providesthe function of authenticating user operations to meet the requirement of authority and domainbased management on the M2000.


6.1.85 uflight_dispatcher ProcessThis section describes the services and functions provided by the uflight_dispatcher process.

Dispatcher the web request of UFlight.



51

Required services: Apache.

6.1.86 umgupdsvr_agent ProcessThis 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.


6.1.87 UniteUitlDM ProcessThis section describes the services and functions provided by the UniteUitlDM process.

This process provides the basic functions, such as importing and exporting scripts, managingNE time, synchronizing NEs, and managing NE objects, of the inter-domain universal NMS.


6.1.88 xftpXX01_agent ProcessThis section describes the services and functions provided by the xftpXX01_agent process.

The xftpXX01_agent process provides the XFTPServiceXX01 service. Through theXFTPServiceXX01 service, the M2000 actively uploads exported files through the northboundinterface to the FTP server on the NMS side.

You can upload the files exported through the northbound interface to the FTP server on theNMS side using the XFTPServiceXX01 service.

The XFTPServiceXX01 service can export various types of files, for example:

l NBI FMl NBI CMl NBI Inventoryl NBI PMl CME NBIl License Managementl NBI server backupl 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 slavenodes. 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.


6.1.89 Trace Server Services and ProcessesThe section describes the function of Trace Server services and processes



52

Each Trace Server process maps a Trace Server service. Table 6-1 describes Trace Serverservices and processes.

Table 6-1 Trace Server services and processes

ServiceName

ProcessName

Platform Description

Monitor Monitor HP Monitors the Trace Server software.The Monitor service must be started.Dependent service: None.

TS.Subscriber

TS.Subscriber

HP Subscribes to signaling and periodically deletessubscribed files.The TS.Subscriber service runs on a separateprocess. In addition, the service is startedautomatically by scripts and does not need to bestarted manually.Dependent service: Monitor.

TS.Collector

TS.Collector

HP Collects and filters data and events.The TS.Collector service runs on a separateprocess. In addition, the service is startedautomatically by scripts and does not need to bestarted manually.Dependent service: Monitor.

EBCStatistic

EBCStatistic

HP Calculates counters based on events for the LongTerm Evolution (LTE) network.This service runs on an independent process andstarts 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 byscripts and does not need to be started manually.In the ATAE cluster system, this process isdeployed on the Trace Server slave node.Dependent service: None.

EBCStatistic

ebc_agent ATAE Calculates counters based on events for the LongTerm Evolution (LTE) network.This service runs on an independent process andstarts automatically by scripts.Dependent service: None.



53

6.1.90 Processes and Services Related to Each Northbound InterfaceThis section describes the processes and services related to each northbound interface.

Table 6-2 describes the relations between northbound interfaces and their correspondingprocesses and services.

Table 6-2 Relations between northbound interfaces and their corresponding processes andservices

Process Service Northbound Interface

irp_agent IRPService l CORBA configurationinterface

l CORBA alarm interfacel CORBA security interfacel CORBA performance

interface

ifms_agent FaultService Northbound alarm fileinterface

pmexp_agent PMExport Northbound performance fileinterface (measurement unit-based)

medXXXX_agent MediationServiceXXXX Northbound performance fileinterface (NE-based)

snmp_agent SnmpAgent Northbound SNMP interface

fmnotify_agent FMNotify Northbound alarm streaminginterface

nms_mml_agent NMSMMLServer Northbound MML interface

cmserver_agent CMServer Northbound inventory fileinterface

cmexp_agent CMExport l Northbound configurationfile interface

l Database interface

6.1.91 Checking the Status of the M2000 ProcessesThis section describes how to check the status of the M2000 processes. When the M2000processes are not running normally, you need to locate faults and log in to the server to rectifythe faults in time. In the ATAE cluster system, the client can monitor the master node and allslave nodes simultaneously.



54

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

ContextChecking the states of the M2000 processes on the M2000 client requires only a few systemresources and does not affect system performance.

ProcedureStep 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 theM2000 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 defaultformat is XML.

l Two types of encoding formats are supported: GBK and UTF-8. The default encoding format isGBK. You are recommended to use the default encoding format if the saved file does not need tosupport 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 operationrequires only few system resources and does not affect system performance.



55

PrerequisitesYou have Logged in to the M2000 server as user ossuser.

ProcedureStep 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 ]



56

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, thenumber 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 serviceis already started, the system does not handle the service. Actually, the system starts only theinactive services.

PrerequisitesYou have logged in to the server as user ossuser.

ProcedureStep 1 Run the following commands:



~> 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



57

6.4 Stopping the M2000 Services (SUSE)This describes how to stop the M2000 services. After the M2000 services are stopped, theM2000 processes are stopped. In this situation, NE performance data and alarm data cannot beprocessed. After the services are resumed, the M2000 updates the data with the NEs andprocesses the data.

PrerequisitesYou have logged in to the server as user ossuser.

Procedure

Step 1 Run the following commands to stop the M2000 services:



~> stop_svc

NOTE

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

Step 2 Run the following command to check whether there is any output. If no system output isdisplayed, 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 isdisplayed, 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



58

7 Managing M2000 Database

About This Chapter

This chapter describes how to manage the M2000 database. This chapter also describes theconcepts of the M2000 database and procedures on how to view the database status, start or stopthe 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 chapterdescribes only the M2000 server database. On the basis of the Oracle database, the M2000 createsthe OSSDB database. After the installation of the M2000 server application software, the sizeof the M2000 database is fixed. You must operate the database by using Oracle commands.

7.2 Checking Oracle ServicesAfter installing the M2000 software or in the daily maintenance, you need to check the statusof Oracle services.

7.3 Starting Oracle ServiceThis section describes how to start the Oracle service.

7.4 Stopping Oracle ServiceThis section describes how to stop the Oracle service.

7.5 Checking Database SpaceThis describes how to use Oracle commands to view the database status, overall size of datafiles, and size of remaining space. This operation requires few system resources and does notaffect system operation.

M2000Administrator Guide (x3850, SUSE10) 7 Managing M2000 Database


59

7.1 Introduction to the M2000 Database (Oracle, ATAE)The M2000 databases consist of the Oracle database and the M2000 server database. This chapterdescribes only the M2000 server database. On the basis of the Oracle database, the M2000 createsthe OSSDB database. After the installation of the M2000 server application software, the sizeof the M2000 database is fixed. You must operate the database by using Oracle commands.

7.1.1 omcdbThe omcdb is used to store the configuration data, security data, and internal data of theM2000. 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 Function

Tables with moi_ as theprefix

Records the information about MO examples.

Tables with mos_ver_ asthe prefix

Records the information about versions.

Tables with nbmmlNe_as the prefix

Records the information about the format of messages transferredbetween the M2000 and the NEs.

Tables with sm_ as theprefix

Records the information about service data.

Tables with softx3000_as the prefix

Records dual-homing relationship.

Views withgv_view_cmcyw_ as theprefix

Records service Database Central (DC) data.

Views withview_cmcyw_ as theprefix

Records basic service data.

tbl_AllNeInfo Records information about NEs.

Processes with proc_sm_as the prefix

Records the processes of service data.

Processes with sm_ as theprefix

Records the processes of service AMG data.

tbl_Resource Records NE resource data.



60

Table Name Function

Tables with ums_ as theprefix

Record the information about error codes.

Tables with ne_ as theprefix

Records the information about NE models.

Tables with omc_ as theprefix

Records the data about network management.

Tables with rel_ as theprefix

Records the associations between MOs.

tbl_ADAllNeList Records the information about the NodeBs to be commissioned.

tbl_ADNeStatus Records the information about the statuses of the NodeBs to becommissioned.

tbl_IPExg Records the IP configuration information about the NATtranslation table.

tbl_OmcSslOption Records the SSL connection policy of the OMC for NEs.

tbl_nelicBaseInfo Records the basic information about NEs.

tbl_nelicTask Records the information about operation tasks.

tbl_nelicTaskEnv Records the information flow interacted between the M2000server and client.

tbl_test_task_property Records the properties of the IPQoS test task.

tbl_test_local_path Records the intra-office test path.

tbl_test_other_path Records the inter-office test path.

tbl_test_log_result Records the test task logs.

tbl_test_ping_report Records the signaling parameters on the bearer network.

tbl_test_audit_result Records the audit results of calling and called parties on the bearernetwork.

tbl_test_nblink_result Records the audit result of the call completion rate on the bearernetwork.

tbl_test_ping_address Records information about address pairs sent by the host.

tbl_SubareaInfo Partition information table, recording the information about eachnode.

tbl_SubareaRes Partition resource table, recording the resources of each node.

session_SessionEntity Records information about operated NEs during a session.

session_SessionMoc Records information about operated MOCs during a session.

session_SessionOpInfo Records information about user operations during a session.



61

Table Name Function

Other tables Records other configuration data of the M2000.

7.1.2 logdbThe logdb is used to store log management data. The logdb database must exist in the M2000system.

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 Function

tbl_Audit Records the logs of user operations.

tbl_SysLog Records the logs of system operations.

tbl_SysLogResultDef Records the result information about system logs.

tbl_SysLogStaticInfo Records the static information about system logs.

Other tables Records the information about other logs.

7.1.3 smdbThe smdb is used to store security management data. The smdb database must exist in theM2000 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 Function

tbl_AccessTable Records the binding relations between usergroups and privileges.

tbl_AccessViewNodeRelTable Records the relations between the privilegedisplay nodes.

tbl_AccessViewNodeTable Records the privilege display nodes.

tbl_IDTable Records the reclaimed IDs.

tbl_SMAccessPolicyItem Records the privilege statistics for binding usergroups.

tbl_SMGroup Records the basic information about user groups.



62

Table Name Function

tbl_SMGroupUserMap Records the binding relations between usergroups and users.

tbl_SMLoginRec Stores the history records on user login.

tbl_SMNEUser Records the basic information about NE users.

tbl_SMPrivateGroupUserMap Records the binding relations between privategroups and users.

tbl_SMSecurityPolicy Records the security policy.

tbl_SMTerm Records the basic information about terminals.

tbl_SMUser Records the basic information about users.

tbl_SMUserHistoryRec Records history user passwords.

tbl_SMUserNEUserMap Records the binding relations between users andNE users.

tbl_SMUserTerminalMap Records the binding relations between users andterminals.

tbl_SecurityObjectTable Records security objects.

tbl_SessionTable Records session information.

tbl_StaticTypeRelationTable Records the relations between privileges.

tbl_StaticTypeTable Records the static security information aboutobject types, privileges, and operations.

tbl_StaticTypeViewTable Records the static security information.

Other tables Records the information about internalimplementation.

7.1.4 topodbThe topodb is used to store topology management data. The topodb database must exist in theM2000 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 Function

TSLink Records the information on topology links.

TSNode Records the information on topology NEs.



63

Table Name Function

TSView Records the information on topology views.

TSTempLoc Records the temporary table that stores the longitude and latitudecoordinates of the e-map.

TSTempPos Records the temporary table that stores the x-axis and y-axiscoordinates of common physical topology.

Other tables Records the information about internal implementation.

7.1.5 fmdbThe fmdb is used to store the alarm data of the M2000 and the managed NEs. The fmdb databasemust exist in the M2000 system.

The fmdb stores the NE data and the M2000 alarm data. A disk space of more than 3,700 MBis 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 Function

tbl_alm_log Records alarm logs.

tbl_event_log Records event logs.

Other tables 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 alarmsand events. For example, the fmdb database may contain multiple alarm log tables such as tbl_alm_log_1and tbl_alm_log_2.

7.1.6 pmdbThe pmdb is used to store the NE performance measurement data. The pmdb database must existin 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 dataoverwrites 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 mustchange the number of days till the data can be stored. Otherwise, the pmdb cannot process anyperformance data. Change the number of saving days before the remaining space of the pmdbis insufficient.



64

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 ofthe pmdb used in a day. Calculate the number of days that the pmdb lasts.

The pmdb consists of the following types of tables:

l Template Tablesl Function Subsets and Period Tables

Template TablesTemplate tables record measurement information. Table 7-6 lists the name and function of thetable.

Table 7-6 Template tables in the pmdb and their functions

Table Name Function

tbl_SyncInfo Records the supplementary collection queues ofperformance results.

Function Subsets and Period TablesThe pmdb database stores the tables of measurement results categorized by function subsets andperiods. 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 Function

tbl_Result_XXX_Y Records periodic results. In the table name, XXX isthe ID of the function subset and Y is the period indexbetween 0 and 4.

7.1.7 swmdbThe swmdb is used to store the file information about the software management module and theconfiguration 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 versionconfiguration data. A disk of more than 3,000 MB is required for storage. Table 7-8 lists thename and function of each table.

Table 7-8 lists the names and functions of tables in the swmdb.



65

Table 7-8 Names and functions of tables in the swmdb database

Table Name Function

tbl_FTPFileSet Records the files managed by the software managementmodule.

tbl_VersionRelation Records the information about version relations.

tbl_NELogTable Records the NE operation logs.

7.1.8 pmcomdbThe pmcomdb is used for storing the static performance measurement data of NEs. Thepmcomdb 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 Counter tables

l Template Tables

l 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 liststhe name and function of each table.

Table 7-9 Counter information tables in the pmcomdb and the corresponding functions

Table Name Function

systbl_NeType Records all possible NE types in M2000.

systbl_FunctionSet Records the function sets of all NEs.

systbl_FunctionSubSet Records the measurement units of allfunction sets.

systbl_Counters Records all measurement counters.

systbl_Counter_Unit Records the units of all counters.

systbl_AllCounterCategory Records the service features of eachversion.

systbl_ComputeCounters Records only the counters involved incalculation.



66

Template TablesTemplate tables contain several tables that record measurement information. Table 7-10 liststhe name and function of each table.

Table 7-10 Template information tables in the pmcomdb and the corresponding functions

Table Name Function

tbl_ObjectInstance Records measurement objects.

tbl_MeasurementPeriod Records measurement periods.

tbl_MeasurementCounter Records measurement counters.

tbl_MeasurementSuspendInfo Records the information on suspendedtasks.

tbl_CounterCategory Records the status of each service feature.

tbl_CounterLevel Records the status of each service counter.

tbl_FeatureStatus Records the status of all the servicefeatures on the M2000 operatingenvironment.

Function Subsets and Period TablesThe measurement results are saved according to the function subset and period. Table 7-11 liststhe name and function of each subset and table.

Table 7-11 Function subsets and period tables in the pmcomdb and their functions

Table Name Function

tbl_MeasObject_XXX_Y In the table name, XXX refers to the functionsubset ID and Y refers to the period index thatranges from 0 to 4. By comparing thetbl_MeasObject_XXX_Y with the resulttable named tbl_Result_XXX_Y, you cancheck the loss status and integrity of theresults.Each time when the measured object changes,a message is recorded in the list.

7.1.9 itfndbThe itfndb is used to store the northbound configuration data, performance tasks, andperformance 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 andfunction of each table.



67

Table 7-12 Names and functions of tables in the itfndb database

Table Name Function

tbl_JGeneralInfo Records the general information about tasks.

tbl_JMoInstance Records the instances of tasks.

tbl_JStatusRecord Records the Status of tasks.

tbl_JMeasurementCategory Records the measurement categories of tasks.

tbl_JSchedule Records the task scheduling.

tbl_RegM2KObject Records the registered M2000 objects.

tbl_MGeneralInfo Records the general information about thresholds.

tbl_MMoInstance Records the instances of thresholds.

tbl_MMeasurementCategory Records the measurement categories of thresholds.

tbl_MThresholdPackElemen Records the details of thresholds.

tbl_MAlarmRecord Records the alarm records of thresholds.

tbl_MStatusRecord Records the status of thresholds.

Other tables Records the information about northboundimplementation.

7.1.10 farsdbThe 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 Static configuration data table

l Task table

l 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 Function

tbl_ProcessorInfo Static service configuration table

tbl_Field Static field configuration table

tbl_TaskInfo Dynamic task record table

tbl_TaskNE Table recording the tasks reported to NEs



68

Table Name Function

Message type name_taskID

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

7.1.11 osstempdbThe osstempdb is used to store the buffer data required for internal implementation of theDesktopServiceXXXX 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 Function

tbl_instancename_subsystemname_function name

Stores the buffer data required for internal implementation of theDesktopServiceXXXX service.

7.1.12 eamdbThe eamdb is used to store the data of network management objects, such as NEs, subnets, andlinks. 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 Function

tbl_sn Subnet information table

tbl_ne NE information table

tbl_nefeature NE feature table

tbl_link Link information table

tbl_idresource NMS object identification management table

tbl_sntype Subnet type table

tbl_netype NE type table

tbl_linktype Link type table

tbl_sync Data synchronization table



69

Table Name Function

tbl_nerelation NE relation table

tbl_maintenanceinfo Maintenance personnel information table

tbl_locationinfo Device maintenance information table

tbl_negroup NE group information table

tbl_negroupclass NE group mode table

tbl_negroup2ne NE group and NE relation table

tbl_negrouptype NE group type table

tbl_devsnmppara SNMP device parameter table

tbl_dftsnmppara Default SNMP parameter table

tbl_autodiscfilter Auto-search IP filter table

tbl_autodischistory Auto-search history record table

tbl_eamschedule Scheduled-search parameter table

tbl_autodiscresult Auto-search result table

tbl_SubareaInfo Refers to the partition information table, which records theinformation about each node.

tbl_SubareaRes Refers to the partition resource table, which records the resourcesof each node.

Other tables Record the internal processing data

7.2 Checking Oracle ServicesAfter installing the M2000 software or in the daily maintenance, you need to check the statusof Oracle services.

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

.

ProcedureStep 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 Oracledatabase by referring to How Do I Start the Oracle Services.oracle 17330 17196 0 Feb15 ? 00:00:00 /opt/oracle/oradb/home/bin/ocssd.bin



70

oracle 17471 17336 0 Feb15 ? 00:00:00 /opt/oracle/oradb/home/bin/diskmon.bin -d -f

If the system output contains at least the following seven processes, it indicates that the databaseservice and the monitor are started. If no output is displayed or only some of the following sevenprocesses are displayed, it indicates that the database service is not started. For details abouthow to start the database, see How Do I Start the Oracle Services.

l ora_pmon_ossdbl ora_dbw0_ossdbl ora_lgwr_ossdbl ora_ckpt_ossdbl ora_smon_ossdbl ora_arc0_ossdbl /opt/oracle/oradb/home/bin/tnslsnr LISTENER -inheritoracle 7742 7603 0 15:17 ? 00:00:00 /opt/oracle/oradb/home/bin/ocssd.binoracle 7878 7753 0 15:17 ? 00:00:00 /opt/oracle/oradb/home/bin/diskmon.bin -d -foracle 11728 1 0 15:27 ? 00:00:00 asm_pmon_+ASMoracle 11730 1 0 15:27 ? 00:00:00 asm_vktm_+ASMoracle 11734 1 0 15:27 ? 00:00:00 asm_diag_+ASMoracle 11736 1 0 15:27 ? 00:00:00 asm_psp0_+ASMoracle 11738 1 0 15:27 ? 00:00:00 asm_dia0_+ASMoracle 11740 1 0 15:27 ? 00:00:00 asm_mman_+ASMoracle 11742 1 0 15:27 ? 00:00:00 asm_dbw0_+ASMoracle 11744 1 0 15:27 ? 00:00:00 asm_lgwr_+ASMoracle 11746 1 0 15:27 ? 00:00:00 asm_ckpt_+ASMoracle 11748 1 0 15:27 ? 00:00:00 asm_smon_+ASMoracle 11750 1 0 15:27 ? 00:00:00 asm_rbal_+ASMoracle 11752 1 0 15:27 ? 00:00:00 asm_gmon_+ASMoracle 14178 1 0 15:40 ? 00:00:00 /opt/oracle/oradb/home/bin/tnslsnr LISTENER -inheritoracle 15427 1 0 15:47 ? 00:00:00 ora_pmon_ossdboracle 15429 1 0 15:47 ? 00:00:00 ora_vktm_ossdboracle 15433 1 0 15:47 ? 00:00:00 ora_diag_ossdboracle 15435 1 0 15:47 ? 00:00:00 ora_dbrm_ossdboracle 15437 1 0 15:47 ? 00:00:00 ora_psp0_ossdboracle 15439 1 0 15:47 ? 00:00:00 ora_dia0_ossdboracle 15441 1 3 15:47 ? 00:00:01 ora_mman_ossdboracle 15443 1 0 15:47 ? 00:00:00 ora_dbw0_ossdboracle 15445 1 0 15:47 ? 00:00:00 ora_dbw1_ossdboracle 15447 1 0 15:47 ? 00:00:00 ora_dbw2_ossdboracle 15449 1 0 15:47 ? 00:00:00 ora_dbw3_ossdboracle 15451 1 0 15:47 ? 00:00:00 ora_dbw4_ossdboracle 15453 1 0 15:47 ? 00:00:00 ora_dbw5_ossdboracle 15455 1 0 15:47 ? 00:00:00 ora_dbw6_ossdboracle 15457 1 0 15:47 ? 00:00:00 ora_dbw7_ossdboracle 15459 1 0 15:47 ? 00:00:00 ora_dbw8_ossdboracle 15461 1 0 15:47 ? 00:00:00 ora_dbw9_ossdboracle 15464 1 0 15:47 ? 00:00:00 ora_dbwa_ossdboracle 15468 1 0 15:47 ? 00:00:00 ora_dbwb_ossdboracle 15470 1 0 15:47 ? 00:00:00 ora_dbwc_ossdboracle 15472 1 0 15:47 ? 00:00:00 ora_dbwd_ossdboracle 15474 1 0 15:47 ? 00:00:00 ora_dbwe_ossdboracle 15476 1 0 15:47 ? 00:00:00 ora_dbwf_ossdboracle 15478 1 0 15:47 ? 00:00:00 ora_dbwg_ossdboracle 15480 1 0 15:47 ? 00:00:00 ora_dbwh_ossdboracle 15482 1 0 15:47 ? 00:00:00 ora_dbwi_ossdboracle 15484 1 0 15:47 ? 00:00:00 ora_dbwj_ossdboracle 15486 1 0 15:47 ? 00:00:00 ora_lgwr_ossdboracle 15488 1 0 15:47 ? 00:00:00 ora_ckpt_ossdboracle 15490 1 0 15:47 ? 00:00:00 ora_smon_ossdboracle 15492 1 0 15:47 ? 00:00:00 ora_reco_ossdb



71

oracle 15494 1 0 15:47 ? 00:00:00 ora_rbal_ossdboracle 15496 1 0 15:47 ? 00:00:00 ora_asmb_ossdboracle 15498 1 0 15:47 ? 00:00:00 ora_mmon_ossdboracle 15500 1 0 15:47 ? 00:00:00 oracle+ASM_asmb_ossdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))oracle 15502 1 0 15:47 ? 00:00:00 ora_mmnl_ossdboracle 15504 1 0 15:47 ? 00:00:00 ora_d000_ossdboracle 15506 1 0 15:47 ? 00:00:00 ora_s000_ossdboracle 15508 1 0 15:47 ? 00:00:00 ora_mark_ossdboracle 15524 1 0 15:47 ? 00:00:00 ora_o000_ossdboracle 15526 1 0 15:47 ? 00:00:00 oracle+ASM_o000_ossdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))oracle 15541 1 2 15:47 ? 00:00:00 ora_p000_ossdboracle 15543 1 3 15:47 ? 00:00:01 ora_p001_ossdboracle 15545 1 3 15:47 ? 00:00:01 ora_p002_ossdboracle 15547 1 3 15:47 ? 00:00:01 ora_p003_ossdboracle 15549 1 2 15:47 ? 00:00:00 ora_p004_ossdboracle 15551 1 3 15:47 ? 00:00:01 ora_p005_ossdboracle 15553 1 3 15:47 ? 00:00:01 ora_p006_ossdboracle 15555 1 3 15:47 ? 00:00:01 ora_p007_ossdboracle 15557 1 2 15:47 ? 00:00:00 ora_p008_ossdboracle 15559 1 3 15:47 ? 00:00:01 ora_p009_ossdboracle 15561 1 3 15:47 ? 00:00:01 ora_p010_ossdboracle 15563 1 3 15:47 ? 00:00:01 ora_p011_ossdboracle 15565 1 2 15:47 ? 00:00:00 ora_p012_ossdboracle 15567 1 3 15:47 ? 00:00:01 ora_p013_ossdboracle 15569 1 3 15:47 ? 00:00:01 ora_p014_ossdboracle 15571 1 3 15:47 ? 00:00:01 ora_p015_ossdboracle 15579 1 4 15:47 ? 00:00:01 ora_arc0_ossdboracle 15581 1 0 15:47 ? 00:00:00 ora_arc1_ossdboracle 15583 1 0 15:47 ? 00:00:00 ora_arc2_ossdboracle 15585 1 0 15:47 ? 00:00:00 ora_arc3_ossdboracle 15587 1 0 15:47 ? 00:00:00 ora_o001_ossdboracle 15589 1 0 15:47 ? 00:00:00 ora_o002_ossdboracle 15591 1 0 15:47 ? 00:00:00 oracle+ASM_o001_ossdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))oracle 15593 1 0 15:47 ? 00:00:00 oracle+ASM_o002_ossdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))oracle 15595 1 0 15:47 ? 00:00:00 ora_o003_ossdboracle 15597 1 0 15:47 ? 00:00:00 oracle+ASM_o003_ossdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))oracle 15602 1 0 15:47 ? 00:00:00 ora_fbda_ossdboracle 15609 1 0 15:47 ? 00:00:00 ora_qmnc_ossdboracle 15653 1 0 15:47 ? 00:00:00 ora_q000_ossdboracle 15655 1 0 15:47 ? 00:00:00 ora_q001_ossdb

----End

7.3 Starting Oracle ServiceThis section describes how to start the Oracle service.

PrerequisitesYou 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



72

SQL> startupIf 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 bytesFixed Size 2159992 bytesVariable Size 365185672 bytesASM Cache 25165824 bytesASM diskgroups mountedSQL> exit

2. Run the following command to start the ORACLE instance.> . ./.bash_profile> sqlplus / as SYSDBASQL> startupIf the following information is displayed, the ORACLE instance has been started.Otherwise, the ORACLE instance is not started. In this case, contact Huawei technicalsupport.ORACLE instance started.

Total System Global Area 2.5254E+10 bytesFixed Size 2183712 bytesVariable Size 2467098080 bytesDatabase Buffers 2.2750E+10 bytesRedo Buffers 34705408 bytesDatabase mounted.Database opened.SQL> exit

Step 2 Run the following commands to start the monitor:

> lsnrctl start


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

----End

7.4 Stopping Oracle ServiceThis section describes how to stop the Oracle service.

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

(SUSE).

ProcedureStep 1 Stop the monitor.

1. Run the following command to check the status of the monitor:

> lsnrctl status



73

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.


Step 2 Stop Oracle services:

1. Run the following command to stop the ORACLE instance.> sqlplus / as SYSDBA


If the following information is displayed, the ORACLE instance has been disabled.Otherwise, the ORACLE instance is not stopped. In this case, contact Huawei technicalsupport.Database closed.Database dismounted.ORACLE instance shut down.

SQL> exit

2. Run the following command to stop the ASM instance.> ORACLE_SID=+ASM



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 dismountedASM instance shutdown

SQL> exit

----End

7.5 Checking Database SpaceThis describes how to use Oracle commands to view the database status, overall size of datafiles, and size of remaining space. This operation requires few system resources and does notaffect system operation.

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



74

Procedure

Step 1 Run the following commands to view the overall size of database files:


SQL> select tablespace_name, sum(bytes)/1024/1024 Total_Size_M from dba_data_filesgroup by tablespace_name;

TABLESPACE_NAME TOTAL_SIZE_M------------------------------------------------------------ ------------LOGDB_TBS 3072OSSTEMPDB_TBS 2048PMCOMDB_TBS 5120SYSAUX 3072UNDOTBS1 20480EAMDB_TBS 2048FARSDB_TBS 8192SWMDB_TBS 12288OMCDB_TBS 76800SYSTEM 3072ITFNDB_TBS 3072

TABLESPACE_NAME TOTAL_SIZE_M------------------------------------------------------------ ------------PMDB_TBS 153600FMDB_TBS 8192SMDB_TBS 2048TOPODB_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 fromdba_free_space group by tablespace_name ;

TABLESPACE_NAME FREE_SIZE_M------------------------------------------------------------ -----------LOGDB_TBS 3069.6875OSSTEMPDB_TBS 2047PMCOMDB_TBS 5107.625SYSAUX 2877.4375UNDOTBS1 20158EAMDB_TBS 2038.625FARSDB_TBS 8190.5SWMDB_TBS 12279.625OMCDB_TBS 76654.875SYSTEM 2741.75ITFNDB_TBS 3068.375

TABLESPACE_NAME FREE_SIZE_M------------------------------------------------------------ -----------PMDB_TBS 153599FMDB_TBS 8180.5625SMDB_TBS 2038.1875TOPODB_TBS 2045.0625

15 rows selected.

----End



75

8 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 viewinformation about the CPU usage, memory capacity, and free memory. If you find that the CPUor 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 CommandsThis 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 bymistake may lead to a system operation error.

M2000Administrator Guide (x3850, SUSE10) 8 Managing Disk Array and Hardware


76

8.1 Viewing the CPU and Memory Usage of the M2000Server (SUSE)

This describes how to view the CPU and memory usage of the M2000 server. You can viewinformation about the CPU usage, memory capacity, and free memory. If you find that the CPUor memory usage is abnormal, you can log in to the server and handle the problem in time.

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

Procedure

Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browserwindow is displayed.

Step 2 Click the Server Monitor tab. The performance of the M2000 server is displayed, as shown inFigure 8-1.

Figure 8-1 Server Monitor

NOTE

In the CPU Usage (%) column and the Memory Usage (%) column, the green icon indicates that the CPUusage or memory usage of the corresponding server is normal; the red icon indicates that the CPU usageor memory usage of the corresponding server is abnormal. In the case that you have set the server monitoringthreshold for an item, the icon corresponding to the item changes from green to red when the value of theitem 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



77

8.2 Viewing the Disk Usage of the M2000 Server by RunningSUSE 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.

PrerequisitesYou 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 than80%.

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 bymistake may lead to a system operation error.

ContextDuring the routine operation and maintenance, back up and clear the following files to releasemore disk space:

l Files storing the information about NEs and the M2000 server

l Software upgrade package and decompressed files

l Trace logs

l Backup files

l Temporary files created during the system operation

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



78

Procedure

Step 1 Export the files that store the information about NEs and the M2000 server, and back up the filesto a tape.

l Files generated during automatic alarm dumpAlarm dump files are stored in the /opt/oss/server/var/ThresholdExport/FM directory.

l User log filesUser log dump files are stored in the /opt/oss/server/var/userlogs directory.

l Core files generated by the systemCore files refer to the files in the /opt/oss/server/var/logs/ directory.

l Trace history filesTrace 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 andthe decompressed files. The upgrade package and decompressed files are stored in the foldernamed after the upgrade patch in the /export/home directory.

CAUTIONGenerally, the decompressed upgrade files are stored in the /export/home directory. The foldername of the upgrade files is created according to the upgrade patch name. Sometimes, the folderis 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 thenumber of trace backup files.

Edit the tracemonitor_svc_ex.xml file in the /opt/oss/server/etc/conf/ directory to set the tracelog 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"> <param name="checktracetime">300</param> <param name="tracebackupnum">50</param></tracemonitor>In checktracetime, you can set the trace log monitor period. The system checks the trace file atthe regular interval of 300s. In tracebackupnum, you can set the number of backup trace filesfor each process in the /opt/oss/server/var/logs/tracebak directory. For a process, if the numberof backup trace files in the tracebak directory exceeds the preset value, the system automaticallydeletes 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.



79

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

----End



80

9 Managing License

About This Chapter

This describes how to query and replace the license file on the M2000 server through theM2000 client.

9.1 Querying the M2000 LicenseThis topic describes how to query the license file on the M2000 server through the M2000 client.

9.2 Updating the M2000 LicenseThis topic describes how to replace the M2000 license file on the M2000 server through theclient.

M2000Administrator Guide (x3850, SUSE10) 9 Managing License


81

9.1 Querying the M2000 LicenseThis 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 andfunctions on the Resource Control Item and Function Control Item tabs.

----End

9.2 Updating the M2000 LicenseThis topic describes how to replace the M2000 license file on the M2000 server through theclient.

Contextl The version of the license that you applied for must be the same as the version of the

M2000.l Before the licenses expire, the M2000 displays a warning periodically.l 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 clickOpen.

Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then clickOK.

----End

M2000Administrator Guide (x3850, SUSE10) 9 Managing License


82

M2000 Administrator Guide (x3850, SUSE10)(V200R012C00_Draft a)(PDF)-En

Documents

Transcript of M2000 Administrator Guide (x3850, SUSE10)(V200R012C00_Draft a)(PDF)-En