M2000 Administrator Guide-3850&3650-SUSE10-V200R012_06

M2000V200R012

Administrator Guide (x3850&x3650,SUSE10)

Issue 06

Date 2013-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 a 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 06 (2013-07-30) 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 X5and IBM x3650 M3 servers and based on the SUSE Linux operating system and the Oracledatabase. In addition, this document provides concepts related to M2000 system managementtasks and the detailed operation procedures, M2000 system routine maintenance, M2000processes and service , and descriptions of frequently used commands and tools. This documentapplies to the core network IMS field and the enterprise wireless solution.

Product VersionProduct versions corresponding to this document are as follows:

Product Name Product Version

M2000 V200R012C00&V200R012C01

Intended AudienceThis document is intended for network management engineers.

Change History

06 (2013-07-30)This issue is the sixth release of V200R012C00 and fourth release of V200R012C01. Comparedwith issue 05 (2012-12-30), this issue incorporates the changes listed in the following table.

Change Description

1 Routine Maintenance Items Descriptions are changed.

10.4 Viewing Hardware Status on theIMM

New

M2000Administrator Guide (x3850&x3650, SUSE10) About This Document


ii

05 (2012-12-30)This issue is the fifth release of V200R012C00 and third release of V200R012C01. Comparedwith issue 04 (2012-09-20), this issue incorporates the changes listed in the following table.

Change Description

4.3 Setting the M2000 Server as anIntermediate-Layer NTP Server

Descriptions are changed.

6 Managing M2000 Users Descriptions are changed.

13.5 How Do I Handle the Shortage ofDisk Space on the M2000 Server (SUSE)

New

04 (2012-09-20)This issue is the fourth release of V200R012C00 and second release of V200R012C01.Compared with issue 03 (2012-07-20), this issue incorporates the changes listed in the followingtable.

Change Description

4 Configuring the NTP Service Descriptions are changed.

3 Configuring the Parameters of theM2000 Server

Descriptions are changed.

03 (2012-07-20)This issue is the third release of V200R012C00 and first release of V200R012C01. Comparedwith issue 02 (2012-06-20), this issue incorporates the changes listed in the following table.

Change Description

3.2 Changing the Host Name of the Server New

13 FAQ New

02 (2012-06-20)This issue is the second official release. Compared with issue 01 (2012-04-20), this issueincorporates the changes listed in the following table.

Change Description

3.3 Changing the IP Address of the IMM New

5 Changing the Time Zone and Time on theM2000 Server (SUSE)

New



iii

Change Description

12 Backing Up and Restoring the M2000System (SUSE)

New

01 (2012-04-20)This issue is the first official release. Compared with issue Draft A (2012-02-27), this issue doesnot incorporate any changes.

Draft A (2012-02-27)This issue is a draft.

Organization1 Routine Maintenance Items

This section describes the recommended maintenance items of the M2000 system.

2 Powering On/Off the System

This section describes how to power on and power off the M2000 system when IBM x3850X5 or IBM x3650 M3 acts as the M2000 server.

3 Configuring the Parameters of the M2000 Server

This section describes how to configure 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 Changing the Time Zone and Time on the M2000 Server (SUSE)

This section describes how to set the time zone and the time on the server.

6 Managing M2000 Users

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

7 Managing M2000 and NE Logs

This section describes how to manage the operation logs, system logs, and security logs of theM2000 and NEs. You can also manage the operating system logs. By querying or collectingstatistics on logs, engineers can trace user behaviors. This facilitates system diagnosis andmaintenance.

8 Managing the M2000 Processes and Services

This section describes how to manage the M2000 processes so that the processes and serviceson the M2000 server can function properly. The enterprise wireless network solution does notsupport northbound functions and therefore there is no northbound process.

9 Managing M2000 Database



iv

This section describes how to manage the M2000 database. This first describes the concepts ofthe M2000 database including database type and status. Then describes how to view the databasestatus, start or stop the database, and check the database space.

10 Managing Disks and Hardware

This section describes how to manage the disks and hardware on the M2000 server.

11 Managing License

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

12 Backing Up and Restoring the M2000 System (SUSE)

This section describes how to back up and restore the M2000 system.

13 FAQ

This section describes some FAQs and their solutions.

ConventionsSymbol Conventions

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

Symbol Description

Indicates a hazard with a high level or medium level of riskwhich, if not avoided, could result in death or serious injury.

Indicates a hazard with a low level of risk which, if notavoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.

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

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.



v


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.


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.



vi

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.



vii

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

3 Configuring the Parameters of the M2000 Server...................................................................93.1 Changing the IP Address of the M2000 Server............................................................................................................103.2 Changing the Host Name of the Server........................................................................................................................123.3 Changing the IP Address of the IMM..........................................................................................................................14

4 Configuring the NTP Service....................................................................................................164.1 Methods for Configuring the NTP Service on the M2000 Server................................................................................174.2 Setting the M2000 Server as the NTP Client...............................................................................................................184.3 Setting the M2000 Server as an Intermediate-Layer NTP Server................................................................................214.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE).......................................................244.5 Configuring the NTP Service of the M2000 Client......................................................................................................24

5 Changing the Time Zone and Time on the M2000 Server (SUSE).....................................285.1 Introduction to the DST................................................................................................................................................295.2 Changing the Time Zone and Time of the M2000 Server (Non-DST, SUSE).............................................................295.3 Changing the Time Zone and Time of the M2000 Server (DST, SUSE).....................................................................31

6 Managing M2000 Users..............................................................................................................356.1 User Type.....................................................................................................................................................................366.2 Changing the Password of User root (SUSE)...............................................................................................................396.3 Changing the Password of User ossuser (SUSE).........................................................................................................396.4 Changing the Password of User ftpuser.......................................................................................................................406.5 Changing the Password of User oracle.........................................................................................................................426.6 Changing the Password of User in the Oracle Database..............................................................................................436.7 Changing the Password of the IMM User....................................................................................................................44

7 Managing M2000 and NE Logs.................................................................................................477.1 Overview of Log Management.....................................................................................................................................487.1.1 Log Management Function........................................................................................................................................48

M2000Administrator Guide (x3850&x3650, SUSE10) Contents


viii

7.1.2 Log Types..................................................................................................................................................................487.1.3 Log Templates...........................................................................................................................................................587.1.4 Procedure for Reporting NE Logs.............................................................................................................................587.1.5 Technical Specifications of Log Management..........................................................................................................627.2 Synchronizing NE Logs................................................................................................................................................627.3 Importing NE Logs.......................................................................................................................................................657.4 Managing the M2000 Operation Logs..........................................................................................................................667.4.1 Querying the M2000 Operation Logs........................................................................................................................667.4.2 Collecting Statistics on the M2000 Operation Logs..................................................................................................697.5 Managing the M2000 System Logs..............................................................................................................................707.5.1 Querying the M2000 System Logs............................................................................................................................707.5.2 Collecting Statistics on the M2000 System Logs......................................................................................................727.6 Managing the M2000 Security Logs............................................................................................................................737.6.1 Querying the M2000 Security Logs..........................................................................................................................747.6.2 Collecting Statistics on the M2000 Security Logs....................................................................................................767.7 Managing NE Operation Logs......................................................................................................................................777.7.1 Querying NE Operation Logs....................................................................................................................................777.7.2 Collecting Statistics on NE Operation Logs..............................................................................................................787.8 Managing NE Secrity Logs..........................................................................................................................................797.8.1 Querying NE Security Logs......................................................................................................................................807.8.2 Collecting Statistics on NE Security Logs................................................................................................................807.9 Browsing the NE Syslog Run Logs..............................................................................................................................827.10 Querying MML Logs..................................................................................................................................................827.11 Managing Log Data....................................................................................................................................................847.11.1 Setting M2000 Log Dumping..................................................................................................................................847.11.2 Setting M2000 Log Export......................................................................................................................................857.11.3 Setting NE Log Export............................................................................................................................................867.12 Setting M2000 Log Templates...................................................................................................................................877.13 References for Log Management Interfaces...............................................................................................................887.13.1 Interface Description: Log Management.................................................................................................................887.13.2 Parameters for Querying Operation Logs ...............................................................................................................897.13.3 Parameters for Collecting Statistics on Operation Logs..........................................................................................917.13.4 Parameters for Querying System Logs....................................................................................................................947.13.5 Parameters for Collecting Statistics on System Logs..............................................................................................967.13.6 Parameters for Querying Security Logs..................................................................................................................987.13.7 Parameters for Collecting Statistics on Security Logs..........................................................................................1007.13.8 Parameters for Querying NE Operation Logs.......................................................................................................1037.13.9 Parameters for Statistics on NE Operation Logs...................................................................................................1047.13.10 Parameters for Querying NE Security Logs........................................................................................................1067.13.11 Parameters for Statistics on NE Security Log.....................................................................................................1077.13.12 Parameters for Setting M2000 Log Timing Export.............................................................................................1107.13.13 Parameters for Setting M2000 Log Timing Dump..............................................................................................112



ix

7.13.14 Parameters for the Export of NE Logs................................................................................................................1157.13.15 Parameters for Querying NE Syslog Run Logs...................................................................................................116

8 Managing the M2000 Processes and Services......................................................................1198.1 Introduction to M2000 Processes and Services..........................................................................................................1208.1.1 3rdTool_agent Process............................................................................................................................................1208.1.2 ActiveMQ Process...................................................................................................................................................1208.1.3 adn_agent Process....................................................................................................................................................1208.1.4 adss_agent Process..................................................................................................................................................1208.1.5 antenna_agent Process.............................................................................................................................................1208.1.6 ce_agent Process......................................................................................................................................................1218.1.7 cmdc_agent Process.................................................................................................................................................1218.1.8 cmengine_agent Process..........................................................................................................................................1218.1.9 cmeserver_agent Process.........................................................................................................................................1218.1.10 cmexp_agent Process.............................................................................................................................................1218.1.11 cmserver_agent Process.........................................................................................................................................1228.1.12 corba_agent Process..............................................................................................................................................1228.1.13 cpm_agent Process................................................................................................................................................1228.1.14 devdoc_agent Process............................................................................................................................................1238.1.15 DrlDm Process.......................................................................................................................................................1238.1.16 dsXXXX agent Process...........................................................................................................................................1238.1.17 eam_agent Process.................................................................................................................................................1238.1.18 fars_agent Process.................................................................................................................................................1248.1.19 fmmedXXXX_agent Process..................................................................................................................................1248.1.20 fmnotify_agent Process.........................................................................................................................................1248.1.21 FMPreServiceXXXX_agent Process......................................................................................................................1248.1.22 fnlicense_agent Process.........................................................................................................................................1258.1.23 gem_agent Process................................................................................................................................................1258.1.24 glmssyn_agent Process..........................................................................................................................................1258.1.25 ifms_agent Process................................................................................................................................................1258.1.26 ipm_agent Process.................................................................................................................................................1268.1.27 irp_agent Process...................................................................................................................................................1268.1.28 itm_agent Process..................................................................................................................................................1278.1.29 lic_agent Process...................................................................................................................................................1278.1.30 log_agent Process..................................................................................................................................................1278.1.31 maintain_agent Process.........................................................................................................................................1288.1.32 manager_agent Process..........................................................................................................................................1288.1.33 medXXXX_agent Process.......................................................................................................................................1288.1.34 ncc0X01_agent Process.........................................................................................................................................1298.1.35 necomm_agent Process..........................................................................................................................................1298.1.36 nelicense_agent Process........................................................................................................................................1298.1.37 neuser_agent Process.............................................................................................................................................1298.1.38 ngnffs_agent Process.............................................................................................................................................130



x

8.1.39 ngnni112_agent Process........................................................................................................................................1308.1.40 ngnnis_agent Process.............................................................................................................................................1308.1.41 ngntestmanage_agent Process...............................................................................................................................1308.1.42 nhcservice_agent Process......................................................................................................................................1308.1.43 nicservice_agent Process.......................................................................................................................................1308.1.44 nimserver_agent Process.......................................................................................................................................1318.1.45 nms_mml_agent Process.......................................................................................................................................1318.1.46 partition_agent Process..........................................................................................................................................1318.1.47 pm_agent Process..................................................................................................................................................1318.1.48 pmengine0X01_agent Process...............................................................................................................................1328.1.49 pmexp_agent Process............................................................................................................................................1328.1.50 pmmon_agent Process...........................................................................................................................................1328.1.51 porttrunk_agent Process........................................................................................................................................1328.1.52 proxy_agent Process..............................................................................................................................................1338.1.53 PRSAssistantService_agent Process......................................................................................................................1338.1.54 prsdc_agent Process...............................................................................................................................................1338.1.55 prsfs_agent Process................................................................................................................................................1338.1.56 prsreport_agent Process.........................................................................................................................................1348.1.57 prssum_agent Process............................................................................................................................................1348.1.58 rn_agent Process....................................................................................................................................................1348.1.59 ScriptModuleService_agent Process.....................................................................................................................1348.1.60 scriptserver_agent Process.....................................................................................................................................1348.1.61 sm_agent Process...................................................................................................................................................1358.1.62 snm_agent Process.................................................................................................................................................1358.1.63 snmp_agent Process...............................................................................................................................................1358.1.64 sso_agent Process..................................................................................................................................................1358.1.65 swm_agent Process................................................................................................................................................1358.1.66 SyslogCollectorDM Process..................................................................................................................................1368.1.67 threshold_agent Process........................................................................................................................................1368.1.68 trapdispatcher Process...........................................................................................................................................1368.1.69 uap_agent Process..................................................................................................................................................1368.1.70 xftpXX01_agent Process........................................................................................................................................1378.1.71 xmlagent Process...................................................................................................................................................1378.1.72 Trace Server Services and Processes.....................................................................................................................1378.1.73 Processes and Services Related to Each Northbound Interface.............................................................................1388.1.74 Processes Used by RTN, Router, Switch, Firewall, and SVN..............................................................................1398.2 Viewing the Running Status of M2000 Services (SUSE)..........................................................................................1418.3 Starting the M2000 Services (SUSE).........................................................................................................................1428.4 Stopping the M2000 Services (SUSE).......................................................................................................................142

9 Managing M2000 Database......................................................................................................1449.1 Introduction to the M2000 Database (Oracle)............................................................................................................1459.1.1 cmedb.......................................................................................................................................................................145



xi

9.1.2 eamdb.......................................................................................................................................................................1459.1.3 farsdb.......................................................................................................................................................................1469.1.4 fmdb.........................................................................................................................................................................1479.1.5 itfndb........................................................................................................................................................................1479.1.6 logdb........................................................................................................................................................................1489.1.7 omcdb......................................................................................................................................................................1489.1.8 osstempdb................................................................................................................................................................1509.1.9 pmcomdb.................................................................................................................................................................1519.1.10 pmdb......................................................................................................................................................................1539.1.11 smdb.......................................................................................................................................................................1539.1.12 swmdb....................................................................................................................................................................1549.1.13 topodb....................................................................................................................................................................1559.2 Checking Oracle Services...........................................................................................................................................1559.3 Starting Oracle Service...............................................................................................................................................1579.4 Stopping Oracle Service.............................................................................................................................................1599.5 Checking Database Space...........................................................................................................................................160

10 Managing Disks and Hardware............................................................................................16210.1 Viewing the CPU and Memory Usage of the M2000 Server...................................................................................16310.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands.......................................................16410.3 Clearing the Disk Space of the M2000 Server (SUSE)............................................................................................16410.4 Viewing Hardware Status on the IMM.....................................................................................................................166

11 Managing License....................................................................................................................16811.1 Querying the M2000 License...................................................................................................................................16911.2 Updating the M2000 License...................................................................................................................................169

12 Backing Up and Restoring the M2000 System (SUSE).....................................................17112.1 Introduction to the M2000 Backup and Restore Solution (SUSE)...........................................................................17212.2 Backing Up and Restoring the M2000 Dynamic Data (SUSE)................................................................................17312.2.1 Periodically Backing Up M2000 Dynamic Data (SUSE).....................................................................................17312.2.2 Manually Backing Up M2000 Dynamic Data (SUSE).........................................................................................17512.2.3 Restoring the M2000 Dynamic Data (SUSE)........................................................................................................176

13 FAQ............................................................................................................................................17913.1 How Do I Solve the Problem That the IMM Remote Window Does Not Respond?...............................................18013.2 How Do I Set Internet Explorer on the PC?.............................................................................................................18013.3 How Do I Handle the Problem of Certificate Error or Untrusted Website Displayed in the Web Browser (IMM)?..........................................................................................................................................................................................18113.4 How Do I Set on the IMM Operation Interface to Change Two Cursors to One Cursor?.......................................18613.5 How Do I Handle the Shortage of Disk Space on the M2000 Server (SUSE).........................................................186



xii

1 Routine Maintenance Items

This section describes the recommended maintenance items of the M2000 system.

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 8.2 Viewing the Running Status ofM2000 Services (SUSE)

Daily

2 9.2 Checking Oracle Services Daily

3 9.5 Checking Database Space Monthly

4 10.1 Viewing the CPU and MemoryUsage of the M2000 Server

Daily

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

Weekly

6 11.1 Querying the M2000 License Monthly

7 10.4 Viewing Hardware Status on theIMM

Daily

M2000Administrator Guide (x3850&x3650, SUSE10) 1 Routine Maintenance Items


1

2 Powering On/Off the System

About This Chapter

This section describes how to power on and power off the M2000 system when IBM x3850X5 or IBM x3650 M3 acts as the M2000 server.

2.1 Powering on the System SecurelyThis section describes how to power on the M2000 hardware devices and related cautions whenthe IBM x3850 X5 or IBM x3650 M3 is used as the M2000 server.

2.2 Powering off the System SecurelyThis section describes how to power off the M2000 hardware devices and related cautions whenthe IBM x3850 X5 or IBM x3650 M3 is used as the M2000 server.

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


2

2.1 Powering on the System SecurelyThis section describes how to power on the M2000 hardware devices and related cautions whenthe IBM x3850 X5 or IBM x3650 M3 is used as the M2000 server.

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.

l Before M2000 delivery, the HTTPS protocol is selected for you to log in to the server byusing the Integrated Management Module (IMM); if you attempt to select HTTP for login,the protocol will be automatically converted to HTTPS. To log in to the server accordingto HTTP, ensure that ports 80 and 443 have been opened on the IMM and the local PC. Tolog in to the server according to HTTPS, ensure that port 443 has been opened on the IMMand the local PC.

ContextThe 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 remote management network port of the Integrated

Management Module (IMM). IP address, user name and password of the IMM networkport vary according to the actual live network planning.

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 panel of the x3850 server.



3

Figure 2-1 Operation panel of the x3850 server

Power switch/Power indicator

Figure 2-2 shows the operation panel of the x3650 server.

Figure 2-2 Operation panel of the x3650 server

2. Check the power indicator status of the server after the system is powered on, and

steady green indicates the server is running properly.l Power on the system using IMM.

1. Set Internet Explorer on the PC by referring to 13.2 How Do I Set Internet Exploreron the PC?.

2. 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 cable.

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

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.



4

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 empty.3. Type http://192.168.70.125 or https://192.168.70.125 in the address bar of the

Internet Explorer.Then press Enter to access the IMM login window.– Before M2000 delivery, the HTTPS protocol is selected for you to log in to the

server by using the Integrated Management Module (IMM); if you attempt to selectHTTP for login, the protocol will be automatically converted to HTTPS. To login to the server according to HTTP, ensure that ports 80 and 443 have been openedon the IMM and the local PC. To log in to the server according to HTTPS, ensurethat port 443 has been opened on the IMM and the local PC.

– 192.168.70.125 is an example and must be replaced by the actual IP address of theIMM.

– If the web browser displays certificate error or untrusted website, install certificatesfor the web browser by referring to 13.3 How Do I Handle the Problem ofCertificate Error or Untrusted Website Displayed in the Web Browser(IMM)?.

4. Type the user name USERID and password of IMM. Changeme_123 is the defaultpassword and needs to be replaced with the actual password. Click Login to accessthe window for setting the idle disconnection duration.

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

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

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



5

Figure 2-3 Startup page

----End

2.2 Powering off the System SecurelyThis section describes how to power off the M2000 hardware devices and related cautions whenthe IBM x3850 X5 or IBM x3650 M3 is used 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 8.2 Viewing the Running Status of M2000Services (SUSE). Stop the M2000 services if they are running. For how to stop the M2000services, see 8.4 Stopping the M2000 Services (SUSE).

Step 2 Disable the database interception and database services.



6

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 2 instance(s). Instance "ossdb", status UNKNOWN, has 1 handler(s) for this service... 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

SQL> shutdown immediate

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

SQL> exit

4. Run the following command to exit user oracle.

> exit



7

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-4 Operator information pane

Step 4 Power off other devices and the cabinet.

----End



8

3 Configuring the Parameters of the M2000Server

About This Chapter

This section describes how to configure the parameters of the M2000 server.

3.1 Changing the IP Address of the M2000 ServerThis section describes how to change the IP address of the M2000 server to ensure that the IPaddress of the server meets the requirements.

3.2 Changing the Host Name of the ServerThis section describes how to change the host name of the M2000 server based on siterequirements.

3.3 Changing the IP Address of the IMMThis section describes how to change the IP address of the integrated management module(IMM) on the M2000.

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


9

3.1 Changing the IP Address of the M2000 ServerThis section describes how to change the IP address of the M2000 server to ensure that the IPaddress of the server meets the requirements.

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

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 theM2000 server leads to the disconnection between the M2000 server and theNEs. When you change the IP addresses of the M2000 servers, update the IP address of theM2000 server in the NE database concurrently.

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

This part takes changing the old IP address 10.10.10.10 to the new IP address 192.168.8.12 asan example.

$ ping 192.168.8.12

l If the new IP address can be pinged, the new IP address is occupied and you need to use othernew IP address.

l If the new IP address cannot be pinged, the new IP address is idle and you can use this IPaddress.

Step 3 Check whether the M2000 is started by referring to 8.2 Viewing the Running Status of M2000Services (SUSE). Stop the M2000 services if they are running. For how to stop the M2000, see8.4 Stopping the M2000 Services (SUSE).

Step 4 Check whether the Oracle is started by referring to 9.2 Checking Oracle Services. If the Oracleis not started, start it by referring to 9.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



10

$ ./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 ftpuser4--HostnameR--ReturnQ--Quit------------------------------------------------------------------Please make a choice[1-4]:

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]: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[default 10.121.71.1]: Please input the new router[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 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 in sequence. If you

do not need to change a certain IP address, press Enter to proceed with the next step.l Type p/P to return to the function menu of the modify.sh script. Then, you are prompted to

perform operations such as changing the IP address and user password.l You can type q/Q to exit the modify.sh script.l When the system prompts you to type the previous IP addresses, type f/F to finish typing IP

addresses and proceed with the next step.

4. When the following information is displayed, type Y and press Enter.Are you sure to continue? Y--Yes. Q--Quit. R--Re-input P--Return pre-step Please make a choice[Y/Q/R/P]: Y

NOTE

l You can type Q to exit the script without performing any operations.l You can type R to return to the previous step to reconfigure relevant parameters.l You can type P to return to the function menu of the modify.sh script. Then, you are prompted

to perform operations such as changing the IP address and user password.l Running the modify.sh script to change the server IP addresses takes about three minutes. Please

wait.

5. When the following information is displayed, the change is successful.------------------------------------------------------------------ Operation complete!



11

If the system output contains failed, the change fails. Contact Huawei technical support.

Step 6 Run the following commands to restart the server:


$ shutdown -r now

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 in SSH mode, and check the statusof the Oracle and M2000 services.

NOTE

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

l For how to view the Oracle service, see 9.2 Checking Oracle Services.l For how to check the status of the M2000 services, see 8.2 Viewing the Running Status of

M2000 Services (SUSE).

----End

3.2 Changing the Host Name of the ServerThis section describes how to change the host name of the M2000 server based on siterequirements.

PrerequisitesYou have logged in to the M2000 server as user root.

Procedure

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

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

For details, see How Do I Stop M2000 Services.

Step 2 Check whether the Oracle is started by referring to 9.2 Checking Oracle Services. If the Oracleis not started, start it by referring to 9.3 Starting Oracle Service.

Step 3 Run the modify.sh script.



$ ./modify.sh

Step 4 Type 4 and press Enter.------------------------------------------------------------------ Welcome to use Modify tool Modify Tool (2.0.0)------------------------------------------------------------------



12

------------------------------------------------------------------Please select a(n) operator type1--IP2--Database password3--Password of ftpuser4--HostnameR--ReturnQ--Quit------------------------------------------------------------------Please make a choice[1-4]:

Step 5 Press Enter and change the host name as prompted.------------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools ------------------------------------------------------------------Please input the old hostname[default ossserver02]:Please input the new hostname:ossserver03

****************SUMMARY******************** OPTYPE: HOSTNAME ******************************************* OLDHOSTNAME: ossserver02 NEWHOSTNAME: ossserver03

NOTE

l Press Enter to use the default value in the system output.

l Type p/P to return to the function menu of the modify.sh script. Then, you are prompted to performoperations such as changing the hostname.

l You can type q/Q to exit the modify.sh script.

l A host name is composed of digits, lower- and upper-case letters, and hyphen (-). The new host namemust comply with the following requirements:

l The host name contains a maximum of 24 characters.

l The host name must starts with a letter.

l The end character of the host name cannot be a hyphen (-).

l The host name cannot contain two consecutive hyphens (-).

Step 6 When the following information is displayed, type Y and 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]:

NOTE

l You can type Q to exit the script without performing any operations.

l You can type R to return to the previous step to reconfigure relevant parameters.

l You can type P to return to the function menu of the modify.sh script. Then, you are prompted toperform operations such as changing the hostname.

Step 7 When the following information is displayed, the change is successful.------------------------------------------------------------------ Operation complete!

If the system output contains failed, the change fails. Contact Huawei technical support.


# sync; sync; sync; sync; sync; sync



13

# shutdown -r now

----End

3.3 Changing the IP Address of the IMMThis section describes how to change the IP address of the integrated management module(IMM) on the M2000.

Prerequisitesl You have obtained the IP address plan and have confirmed that the IP address of the IMM

must be changed. For details, see Planning Device Host Name and IP Address.l The network interface on the PC has been connected to the IMM network interface on the

server using network cable.l The communication between the PC and the IMM is normal.l The Dynamic Host Configuration Protocol (DHCP) service has been disabled on the PC.

Procedure

Step 1 Set Internet Explorer on the PC by referring to 13.2 How Do I Set Internet Explorer on thePC?.

Step 2 Set the IP address of the PC to be on the same network segment (192.168.70.xx for example) asthe IP address of the system management network interface on the M2000 server.

For example, set the network adapter of the PC as follows:

l Set IP address to 192.168.70.35.l Set Subnet mask to 255.255.255.0.l Leave Default gateway, Preferred DNS server, and Alternate DNS server empty.

Step 3 Type http://192.168.70.125 in the address bar of the Internet Explorer. Then, press Enter toaccess the IMM login window. If the web browser displays certificate error or untrusted website,install certificates for the web browser by referring to 13.3 How Do I Handle the Problem ofCertificate Error or Untrusted Website Displayed in the Web Browser (IMM)?.

Step 4 Type the initial user name USERID and the actual password. Click Login to access the windowfor setting the idle disconnection duration.

Step 5 Click Continue to access the IMM home page.

Step 6 In the navigation tree, choose System > IMM Control > Network Interface.

Step 7 The current IP addresses are displayed in the right pane. Enter the new IP address, subnet mask,and gateway in IPV4, as shown in Figure 3-1.



14

Figure 3-1 Changing the IP address of the IMM

Step 8 Click Save.

Step 9 In the navigation tree, choose System > IMM Control > Restart IMM to enter the window forrestarting the IMM.

Step 10 Click Restart to restart the IMM to make the new IP address take effect.

NOTERestarting the IMM takes about 2 to 5 minutes. After the IMM restarts, open the web browser again if youneed to log in to the IMM.

----End



15

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

CAUTIONIf you do not need to configure the NTP service on the M2000 server at the site, skip this section.

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 section describes how to check the running status of the NTP service on the M2000 server.

4.5 Configuring the NTP Service of the M2000 ClientThis section describes how to set the M2000 client as the NTP client and synchronize time withthe M2000 server by using the NTP tool delivered with the Windows operating system.

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


16

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

CAUTIONl Policy 1 is recommended. That is, set the M2000 server and NEs as NTP clients.l When the M2000 manages billing system NEs such as the iGWB and CG, you must set the

M2000 server and NEs as NTP clients. If you set the M2000 as an intermediate NTP server,the M2000 server time has an offset, which may lead to severe faults on the network.

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

Higher security ofthe timesynchronizationnetwork becausethe M2000 serverserves as an NTPclient andsynchronizes timeof 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.



17

Method

Reliability Security SystemResource Usage

Cost

Set theM2000server asanintermediate-layerNTPserver.

l The M2000serverperformsfrequentoperations,such asmaintenance,upgrade, andbackup. Whenthe M2000server is usedas anintermediateNTP server,the systemreliability isrelatively low.

l When M2000server is set asanintermediateNTP server,the M2000server time hasan offset,which maylead toinconsistencybetween NEtime and thehighest layerNTP server.

Lower security ofthe timesynchronizationnetwork becausetimesynchronizationservice is affectedwhen the M2000server becomesfaulty.

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.

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 is set correct.l The IP address of the NTP server has been obtained.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 SSH mode.



18

ProcedureStep 1 Run the following command to check the time zone of the server:

$ grep TIMEZONE /etc/sysconfig/clock

If the server time zone is incorrect, correct it by referring to 5.3 Changing the Time Zone andTime of the M2000 Server (DST, SUSE) or 5.2 Changing the Time Zone and Time of theM2000 Server (Non-DST, SUSE).




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

For details, see 9.2 Checking Oracle Services.2. Stop Oracle services.

For details, see How Do I Stop the Oracle Services.

Step 4 Run the following command to synchronize the clock time with the upper-level server.

$ /usr/sbin/ntpdate IP address of the NTP server

NOTEIf the system displays the following information while executing the preceding commands, the NTP servicehas started.ntpdate[518]:the NTP socket is in use, exitingIn this situation, proceed to complete the follow-up steps.

Step 5 Run the following command to open the yast interface:

$ yast

Step 6 On the YaST Control Center interface, use ↑ and ↓ to select Network Services.

Step 7 On the YaST Control Center interface, use Tab, ↑, and ↓ to select NTP Configuration, andpress Enter.

Step 8 Use Tab, ↑, and ↓ to select During Boot on Automatically Start NTP Daemon. PressEnter for confirmation. If During Boot is selected, skip this step.

NOTE

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

Step 9 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 test the NTP configuration, as shown in Figure4-1.

NOTEDo not use the numeric keypad on the GUI of the operating system.

l If the following information is displayed, it indicates that the entered IP address isunavailable. In such a case, you need to check whether the IP address of the NTP server is



19

correct and whether network communication is normal. After troubleshooting, perform thisstep again.Server is unreachable or does not respond properly.

l If the following information is displayed, it indicates that the entered IP address is available.Server is reachable and responds properly.

Figure 4-1 Configuring the NTP client

Step 10 Use the Tab key to select Advanced Configuration, and press Enter.

Step 11 Use the Tab key to select Undisciplined Local Clock (LOCAL). Then use the Tab to selectDelete and press Enter.

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

Step 13 Use Tab to select Finish for completing the configuration of the NTP server.

Step 14 Use Tab to select Quit to exit the system.

Step 15 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

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

If the status is incorrect, the NTP service does not function properly. When this occurs, contactHuawei technical support.

Step 16 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.

----End



20

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 is set correct.l You have logged in to the server as user root in SSH mode.

Context

l The upper-layer time server of the M2000 server requires that the NTP be used. The serverrunning Windows uses the SNTP protocol. Therefore, it cannot be used as the upper-layertime server for the M2000 server.

l When an M2000 server is configured as an intermediate NTP server, the M2000 serversynchronizes time from the upper-layer clock source before providing the NTP service forNEs. If the M2000 server fails to synchronize time from the upper-layer time source, theM2000 server provides the NTP service for NEs using the M2000 server time. TheM2000 server time has an offset. If the M2000 server cannot synchronize the time fromthe upper-layer clock source for a long time, the offset may be large, which may causenetwork faults.

l When the M2000 manages billing system NEs such as the iGWB and CG, you must set theM2000 server and NEs as NTP clients. If you set the M2000 as an intermediate NTP server,the M2000 server time has an offset, which may lead to severe faults on the network.

l When you set the M2000 server as the intermediate NTP server, the specifications are asfollows:

– The number of NEs of concurrent NTP time synchronization is 500. Specifically, theintermediate NTP server can provide time synchronization for 500 NEs concurrently.When the number of NEs requiring time synchronization is greater than 500,synchronize the NE time at an interval of 30s in batches.

– The maximum number of NEs of which the time can be synchronized using theintermediate NTP server is consistent with the M2000 management capability.

Procedure

Step 1 Run the following command to check the time zone of the server:$ grep TIMEZONE /etc/sysconfig/clock

If the server time zone is incorrect, correct it by referring to 5.3 Changing the Time Zone andTime of the M2000 Server (DST, SUSE) or 5.2 Changing the Time Zone and Time of theM2000 Server (Non-DST, SUSE).



21







Step 4 Run the following commands to back up the ntp.conf configuration file:

$ rcntp stop

If the following information is displayed, ignore it and continue to run the following commands:Shutting down network time protocol daemon (NTPD) doneumount: /var/lib/ntp/proc: not mounted

$ cd /etc

$ cp -p ntp.conf bak.ntp.conf

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 Switch to the YaST Control Center window, and configure the M2000 server as anintermediate-layer NTP server.1. Run the following command to switch to the YaST Control Center window:

$ yast2. 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 NTP

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

Daemon, and press Enter. If During Boot is selected, skip this step.NOTE

If the Warning dialog box is displayed, press Tab and choose Continue. 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 press Enter.6. Use the Tab key to select Undisciplined Local Clock (LOCAL). Then use the Tab to

select Delete and press Enter.7. In the displayed prompt dialog box, use the Tab key to select Yes, and press Enter.8. Use the Tab key to select Add, and press Enter.9. Use the Tab key to select Server, and press Enter. If Server is selected, skip this step.10. Use the Tab key to select Next, and press Enter.11. Use the Tab key to select Address, and enter the IP address of the top-level NTP server in

Address.



22

NOTEDo not use the numeric keypad on the GUI of the operating system.

12. Use the Tab key to select Test to check whether the entered IP address is available.l If the following message is displayed, it indicates that the entered IP address is

unavailable. In such a case, you need to check whether the IP address of the NTP serveris correct and whether network communication is normal. After troubleshooting,perform this step again.Server is unreachable or does not respond properly.

l If the following message is displayed, it indicates that the entered IP address is available.Server is reachable and responds properly.

13. Use the Tab key to select Use for Initial Synchronization, and 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 press Enter.

NOTE

If there are multiple NTP servers, repeat Step 6.8 through Step 6.15 to set the IP addresses of otherNTP servers.

16. Press Tab to choose Finish, and press Enter.17. Press Tab to choose Quit, and press Enter.


$ /usr/sbin/ntpq -p


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 precedinginformation 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 8 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.



23

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

----End

Follow-up Procedure

After the M2000 server is set as an intermediate NTP server, set the NEs as NTP clients. Fordetails about how set an NE as an NTP client, see the user guide of the corresponding NE type.

4.4 Checking the Running Status of the NTP Service on theM2000 Server (SUSE)

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

PrerequisitesYou have logged in to the server as user root.

Procedure


$ /usr/sbin/ntpq -p


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


----End

4.5 Configuring the NTP Service of the M2000 ClientThis section describes how to set the M2000 client as the NTP client and synchronize time withthe M2000 server by using the NTP tool delivered with the Windows operating system.



24

Prerequisitesl You have logged in to the Windows OS as a user of the user group Administrators, and

the system is running properly.l The connection between the M2000 client and the server is normal.l The clock source of the server is operational.

Context

CAUTIONl The configuration procedure is applicable to the Windows 7, Windows 2003, Windows 2008,

Windows XP Professional, and Windows Vista Business operating systems.l If the NTP service does not need to be configured at a site, skip this section and proceed with

the following operations.l If the NTP service needs to be configured at a site, but the upper-layer NTP server is not

available and the NTP service is not configured on M2000 server during the commissioning,skip this section and proceed with the following operations without configuring the NTPservice on the client.

Procedure

Step 1 Set the M2000 client as the NTP client.1. Open the Registry Editor window.

l For Windows 2003 or Windows XP Professional, choose Start > Run. In the displayedRun window, enter the regedit command and press Enter. The Registry Editorwindow is displayed.

l For Windows 2008, Windows 7, or Windows Vista Business, click Start, then enterthe regedit command and press Enter in the search box. The Registry Editor windowis displayed.

2. Modify the registry.

In the registry, change the value of LocalNTP under HKEY_LOCAL_MACHINE >SYSTEM > CurrentControlSet > Services > W32Time > Parameters to 0. By default,the value is 0. If the LocalNTP parameter does not exist, you can infer that the value canbe ignored and the registry does not need to be modified.

NOTE

For the Windows 2003 and Windows 2008 operating systems, in the registry, change the value ofEnable under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services >W32Time > TimeProviders > NtpServer to 0.

Step 2 Specify the M2000 server as the NTP server.



25

If... Then...

The M2000 clientruns on theWindows 2003 orWindows XP OS

1. Choose Start > Run. Type cmd and press Enter.2. In the displayed window, run the following command:

c:\>net time /setsntp:M2000 server IP addressNOTEl M2000 Server IP Address: indicates the logical IP address of M2000 in a

single-server system; the logical IP address of the active and standbyservers in an HA system.

l The result of the net time command is saved in the Windows registry.Therefore, after the Windows OS is restarted, the parameters set throughthe net time command still take effect.

l To cancel the setting, run the net time /setsntp command.

The M2000 clientruns on theWindows 2008 ,Windows 7Professional OS, orWindows VistaBusiness OS

1. Click Start, enter cmd in the search box, Right-click the foundcmd icon and choose Run as administrator from the shortcut menu.

2. In the displayed window, run the following command:c:\>net start w32timec:\>w32tm /config /manualpeerlist:M2000 server IP address /syncfromflags:manual /reliable:yes /updateNOTEl M2000 Server IP Address: indicates the logical IP address of M2000 in a

single-server system; the logical IP address of the active and standbyservers in an HA system.

l The result of the w32tm command is saved in the Windows registry.Therefore, after the Windows OS is restarted, the parameters set throughthe w32tm command still take effect.

l To cancel the setting, run the following commands:

net stop w32timew32tm /unregisterIf the error code 0x80070005 is displayed after running the w32tm /unregister command, contact Huawei technical support.

Step 3 Restart the Windows Time service.1. Run the following command to open the Services window.

c:\>services.msc2. Find the Windows Time service and restart it in the Services window.

Step 4 Check the specified NTP server.



26

If... Then...

The M2000 clientruns on theWindows 2003 orWindows XP OS

1. Choose Start > Run. Type cmd and press Enter.2. In the displayed window, run the following command:

c:\>net time /querysntpNOTE

If the host name or IP address of the PC is specified as the host name or IPaddress of the NTP server through /setsntp, the NTP server time is regardedas the standard time of the PC.

The M2000 clientruns on theWindows 2008 ,Windows 7Professional OS, orWindows VistaBusiness OS

1. Click Start, enter cmd in the search box, Right-click the foundcmd icon and choose Run as administrator from the shortcut menu.

2. In the displayed window, run the following command:c:\>w32tm /query /peersNOTE

If the host name or IP address of the PC is specified as the host name or IPaddress of the NTP server through /manualpeerlist, the NTP server time isregarded as the standard time of the PC.

Step 5 Run the following command to manually synchronize time:

c:\>w32tm /resync

Step 6 Run the following command to check the running status of the SNTP service:

c:\>w32tm /stripchart /computer:M2000 server IP address /dataonly

NOTE

M2000 Server IP Address: indicates the logical IP address of M2000 in a single-server system; the logicalIP address of the active and standby servers in an HA system.

The system displays the local time of the client and the deviation between the local time and thetime on the NTP server.

Tracking 10.71.15.98 [10.71.15.98].The current time is 2009-6-22 10:05:09 (local time).10:05:09, +04.9881239s10:05:11, +04.9814570s10:05:13, +04.9740897s10:05:15, +04.9589559s10:05:17, +04.9449507s...

The first line of the system output shows the local time of the client. The next line shows thetime deviation between the client and the NTP server. + indicates that the client time is later thanthe server time. - indicates that the client time is earlier than the server time. You can exit theactive window by pressing Ctrl+C.

----End



27

5 Changing the Time Zone and Time on theM2000 Server (SUSE)

About This Chapter

This section describes how to set the time zone and the time on the server.

5.1 Introduction to the DSTThis section describes the daylight saving time (DST) and the DST impact on the M2000 system.

5.2 Changing the Time Zone and Time of the M2000 Server (Non-DST, SUSE)This section describes how to change the time zone and the time of the M2000 server.

5.3 Changing the Time Zone and Time of the M2000 Server (DST, SUSE)This section describes how to change the time zone and the time of the M2000 server when thesystem uses daylight saving time (DST).

M2000Administrator Guide (x3850&x3650, SUSE10)

5 Changing the Time Zone and Time on the M2000 Server(SUSE)


28

5.1 Introduction to the DSTThis section describes the daylight saving time (DST) and the DST impact on the M2000 system.

IntroductionDST means Daylight Saving Time. The DST is one hour earlier than the standard time. Forexample, during the DST, 10:00 am in US east standard time is 11:00 am in US east DST.

Impact on the M2000 Systeml When the DST starts, generally one hour is automatically added to the local time of the

operating system. This change does not affect the system clock of the M2000. TheM2000 log management and trace management use the local time. Therefore, one-hourrecords are missing in logs or trace files.

l When the DST ends, generally one hour is automatically deducted from the local time ofthe operating system. This change does not affect the system clock and time storage andexchange are not affected. This change, however, affects the time display. During theoperation of the M2000, some modules in the M2000 generate some files whose names areidentified by time stamps. When the DST ends, files that are generated later overwrite theearlier ones.

NOTE

l The local time is the time displayed on the computer. It varies according to the time zone.

l The system clock indicates the Greenwich Mean Time (GMT). The NTP synchronization uses theGMT, which does not affect the local time. The DST does not affect the NTP service.

5.2 Changing the Time Zone and Time of the M2000 Server(Non-DST, SUSE)

This section describes how to change the time zone and the time of the M2000 server.

PrerequisitesYou have logged in to the M2000 server as user root in SSH mode.

ContextThe SUSE operating system supports two time zone formats: Greenwich Mean Time (GMT)and time zone code.

l The GMT format stipulates only time offset rather than DST rules. The GMT format isrecommended for countries or regions that do not use DST.The time and time zone are changed with reference to GMT. The time zone of a region tothe east of the GMT region is represented by GMT+N, indicating that the time of the regionis N hours ahead of the GMT. The time zone of a region to the west of the GMT region isrepresented by GMT-N, indicating that the time of the region is N hours behind the GMT.For example, GMT+8 indicates that the time of the region is eight hours earlier than theGMT, and GMT-8 indicates that the time of the region is eight hours later than the GMT.The GMT time zone format in a Solaris operating system, however, is the reverse of the




29

common GMT time zone format. Specifically, GMT+N indicates that the time of the regionis N hours behind the GMT, and GMT-N indicates that the time of the region is N hoursahead of the GMT.

l The time zone code format stipulates both time offset and DST rules. The time zone codeformat must be used in countries and regions that use DST. Otherwise, the operating systemdoes not support automatic DST transitions.

l If you need to modify both the time zone and the time, modify the time zone first.

Precautions

You can change the time zone on the M2000 server according to the actual requirements.Changing the server time zone directly results in change of the time at the bottom layer of theLinux operating system. Consequently, all the timers that depend on the operating system arereset or stop functioning properly. You must stop the M2000 and Oracle services in advance toavoid a service failure caused by the malfunctioning of timers. During the period, theperformance data and alarm data of the managed NEs cannot be handled in time. After theM2000 and Oracle services are restored, the M2000 starts the automatic synchronizationfunction and collects and handles the missing performance data and alarm data from managedNEs.

Procedure

Step 1 Check the server time zone.


If the time zone of the server is correct, perform Step 8.

If the server time zone is incorrect, perform the following steps to correct it.

Step 2 If the M2000 services are running, stop them. If the M2000 software has not been installed, skipthis step.

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.


Step 3 If the Oracle services are running, stop them.

1. Check the status of the Oracle services.

For details, see 9.2 Checking Oracle Services.

2. Stop Oracle services.


Step 4 Run the yast command to change the time zone of the M2000 server in YaST ControlCenter.

Step 5 Press Tab and the arrow keys to select system in the left part of YaST Control Center andselect Date and Time in the right part, and press Enter.




30

Step 6 Check whether the Region and Time Zone are correct according to the instructions in TimeZone and Clock Settings. If the two parameters are not set correctly, press Tab and the arrowkeys to select the correct time zone. Press Tab to select Accept. Then, press Enter.

Step 7 Run the following command to check the time zone of the server:


If the time zone of the server is incorrect, repeat Step 4 through Step 6 to change it.

Step 8 Check system date and time.

$ date

If system date and time are incorrect, perform the following steps:

Step 9 Set the system date and time.

$ date mmddHHMMYYYY.SS

NOTE

l mm indicates a month.l dd indicates a day.l HH indicates an hour.l MM indicates a minute.l YYYY indicates a year.l SS indicates a second.

For example, to set system date and time to 2005-11-17 16:30:43, run the following command:$ date 111716302005.43Mon Nov 17 16:30:43 CST 2005

NOTE

In the date -u mmddHHMMYYYY.SS command, mmddHHMMYYYY.SS is the Greenwich Mean Time(GMT) but not the local time.

Step 10 Run the following command to restart the server.


$ shutdown -r now

After the operating system restarts, the Oracle service will automatically restart. If the M2000software has been installed, the M2000 services will also automatically restart after the operatingsystem restarts.

----End

5.3 Changing the Time Zone and Time of the M2000 Server(DST, SUSE)

This section describes how to change the time zone and the time of the M2000 server when thesystem uses daylight saving time (DST).

PrerequisitesYou have logged in to the M2000 server as user root in SSH mode.




31

Context

The SUSE operating system supports two time zone formats: Greenwich Mean Time (GMT)and time zone code.

l The GMT format stipulates only time offset rather than DST rules. The GMT format isrecommended for countries or regions that do not use DST.

The time and time zone are changed with reference to GMT. The time zone of a region tothe east of the GMT region is represented by GMT+N, indicating that the time of the regionis N hours ahead of the GMT. The time zone of a region to the west of the GMT region isrepresented by GMT-N, indicating that the time of the region is N hours behind the GMT.For example, GMT+8 indicates that the time of the region is eight hours earlier than theGMT, and GMT-8 indicates that the time of the region is eight hours later than the GMT.The GMT time zone format in a Solaris operating system, however, is the reverse of thecommon GMT time zone format. Specifically, GMT+N indicates that the time of the regionis N hours behind the GMT, and GMT-N indicates that the time of the region is N hoursahead of the GMT.

l The time zone code format stipulates both time offset and DST rules. The time zone codeformat must be used in countries and regions that use DST. Otherwise, the operating systemdoes not support automatic DST transitions.

l If you need to modify both the time zone and the time, modify the time zone first.

Precautions

You can change the time zone on the M2000 server according to the actual requirements.Changing the server time zone directly results in change of the time at the bottom layer of theLinux operating system. Consequently, all the timers that depend on the operating system arereset or stop functioning properly. You must stop the M2000 and Oracle services in advance toavoid a service failure caused by the malfunctioning of timers. During the period, theperformance data and alarm data of the managed NEs cannot be handled in time. After theM2000 and Oracle services are restored, the M2000 starts the automatic synchronizationfunction and collects and handles the missing performance data and alarm data from managedNEs.

Procedure

Step 1 Query the local time zone name.

For details, see How Do I Query a Time Zone Name (SUSE).

Step 2 Run the following command to view the DST rules of the time zone in a specified year:

$ zdump -v time zone name | grep specified year

l If DST is not used, the system displays no information. If DST is used, the system displaysthe following information for describing the DST rules:

l The information is in the following format:Time zone name UTC time = Local time/DST isdst=0/1

l The UTC time is the GMT.

l isdst=0 non-DST period. isdst=1 indicates DST period.




32

NOTE

l If you do not add | grep specified year to the previous command, the system displays the DST rulesof the time zone in all years.

l The DST rules of a time zone stipulate the day, week, and month when DST starts and ends in eachyear. This indicates that the week when DST starts is fixed and that the date when DST starts is flexible.For example, the DST of Alaska, United States time zone starts from the second Sunday of March andends on the first Sunday of November in each year.

l You can run the zdump command to query the DST rules in the three successive years, that is, the lastyear, this year, and the next year. Based on the system output, you can infer the universal DST changerules.



If the time zone of the server is correct, perform Step 8.

If the time zone of the server is incorrect, perform the following steps to change it:

Step 4 If the M2000 services are running, stop them. If the M2000 software has not been installed, skipthis step.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.





Step 6 Perform the following operations to configure the DST:1. Run the yast command to change the time zone of the M2000 server in YaST Control

Center.2. Use the Tab key and arrow keys to select system in the left pane of YaST Control

Center and select Date and Time in the right pane. Then, press Enter.3. According to the description in Time Zone and Clock Settings, check whether the values

of Region and Time Zone are consistent with the actual situation. If the values areinconsistent with the actual situation, use the Tab key and arrow keys to correct the timezone. Then use the Tab key to select Accept and press Enter.

4. In the displayed window, use the Tab key to select Quit to exit the YaST.



If the time zone of the server is incorrect, repeat Step 6 to change it.

Step 8 Check system date and time.

$ date




33

If system date and time are incorrect, perform the following steps:

Step 9 Set the system date and time.

$ date mmddHHMMYYYY.SS

NOTE

l mm indicates a month.

l dd indicates a day.

l HH indicates an hour.

l MM indicates a minute.

l YYYY indicates a year.

l SS indicates a second.

For example, to set system date and time to 2005-11-17 16:30:43, run the following command:$ date 111716302005.43Mon Nov 17 16:30:43 CST 2005

NOTE

In the date -u mmddHHMMYYYY.SS command, mmddHHMMYYYY.SS is the Greenwich Mean Time(GMT) but not the local time.



$ shutdown -r now

After the operating system restarts, the Oracle service will automatically restart. If the M2000software has been installed, the M2000 services will also automatically restart after the operatingsystem restarts.

----End

Examplel Run the following command to view the DST rules of the PRC time zone in 2007:

$ zdump -v PRC|grep 2007If no command output is displayed, the PRC time zone in 2007 does not use DST.

l Run the following command to view the rule of the US/Alaska time zone in 2007:$ zdump -v US/Alaska|grep 2007The system displays information similar to the following:US/Alaska Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST isdst=0US/Alaska Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT isdst=1US/Alaska Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT isdst=1US/Alaska Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 AKST isdst=0

– The information in the first row and the second row indicates that DST starts after Mar11 02:00:00 2007 changes to Mar 11 03:00:00 2007.

– The information in the third row and the fourth row indicates that DST ends after Nov4 02:00:00 2007 changes to Nov 4 01:00:00.




34

6 Managing M2000 Users

About This Chapter

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

6.1 User TypeThis section describes information about OS users and DB users involved in the operation ofthe M2000. OS users include user root, ossuser, ftpuser, and oracle. DB users include usersystem and sys.

6.2 Changing the Password of User root (SUSE)This describes how to change the password of user root.

6.3 Changing the Password of User ossuser (SUSE)This section describes how to change the password of user ossuser when you log in to the systemas user root. In the M2000 HA system, the password of user ossuser on the two nodes must beconsistent. Therefore, you must change the password of user ossuser on the active and standbynodes separately to ensure the password consistency.

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

6.5 Changing the Password of User oracleThis section describes how to change the password of user oracle when you log in to theM2000 database as user root. For the M2000 HA system, the password of user oracle on thetwo nodes must be consistent. Therefore, you must change the password of user oracle on theactive and standby nodes separately to ensure the password consistency.

6.6 Changing the Password of User in the Oracle DatabaseThis section describes how to change the passwords of user in the Oracle database.

6.7 Changing the Password of the IMM UserThis section describes how to change the password of the IMM user USERID on the M2000.

M2000Administrator Guide (x3850&x3650, SUSE10) 6 Managing M2000 Users


35

6.1 User TypeThis section describes information about OS users and DB users involved in the operation ofthe M2000. OS users include user root, ossuser, ftpuser, and oracle. DB users include usersystem and sys.

Table 6-1 and Table 6-2 describe OS users and DB users for the M2000.

Table 6-1 OS users

UserName

Default Password Usage Authority UserGroup

ShellResolutionProgram

Directory

root Changeme_123 Userroot isthedefaultuser ofthesystem. Userroot isauthorized tocontrolallresources,createotheruseraccounts,assignauthority tootherusers,andperform allsystemoperations.

User roothas thehighestauthority ofthe system.User root isauthorizedto installanduninstallM2000serverapplications.

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

/bin/bash

/root



36

UserName



Directory

ossuser Changeme_123 Userossuser isresponsiblefor theoperation andmaintenanceof theM2000.

Userossuser isauthorizedto accessthedatabaseandperformoperationandmaintenance.Userossuser isnot allowedto install oruninstallM2000serverapplications.

root,sys,ossgroup,dba,andoinstall

/bin/bash

/export/home/ossuser

oracle Changeme_123 Useroracleis usedtoinstalltheOracledatabase.Useroracleiscreatedbeforethedatabase isinstalled.

User oracleisauthorizedto accessthedatabaseandperformoperationsover theOracledatabase.

oinstall,dba,andossgroup

/bin/bash

/opt/oracle



37

UserName



Directory

ftpuser Changeme_123 ftpuser is auser touploadfiles totheserveranddownloadfilesfromtheserver.

Userftpuser isauthorizedto performsoftwaremanagement and filetransfer forNEs.

ossgroup,dialout,video

/bin/bash

/export/home/sysm

Table 6-2 DB users

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 theadministrator of theOracle database. User sysis responsible for themanagement andoperation of the Oraclesystem, and is used torestore the Oracledatabase applications.



38

6.2 Changing the Password of User root (SUSE)This describes how to change the password of user root.

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

ContextThe password contains 8 to 127 characters, including digits from 0 to 9, uppercase and lowercaseletters, and special characters. To improve password security, you must set the password byobserving the following rules: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: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?

and spacesl The last 12 history passwords cannot be used.

NOTE

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

l The number of times adjacent codes are used should not be greater than 4 for the ASCII codescorresponding to the characters in a password. You are advised not to use adjacent letters and digits ina password.

Procedure

Step 1 Log in as user root, and enter the old password of user root.

Step 2 Run the following command to change the password:

# passwd root

Changing password for root.

New password:new password

Reenter New Password:new password

Password changed.

----End

6.3 Changing the Password of User ossuser (SUSE)This section describes how to change the password of user ossuser when you log in to the systemas user root. In the M2000 HA system, the password of user ossuser on the two nodes must beconsistent. Therefore, you must change the password of user ossuser on the active and standbynodes separately to ensure the password consistency.



39

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

ContextThe password contains 8 to 127 characters, including digits from 0 to 9, uppercase and lowercaseletters, and special characters. To improve password security, you must set the password byobserving the following rules: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: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?

and spacesl The last 12 history passwords cannot be used.

NOTE



ProcedureStep 1 Run the following command to change the password:

# passwd ossuser

Changing password for ossuser.


Reenter New Password:new password

Password changed.

----End

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

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:



40

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.

Procedure

Step 1 Check whether the M2000 is started by referring to 8.2 Viewing the Running Status of M2000Services (SUSE). Stop the M2000 services if they are running. For details on how to stop theM2000, see 8.4 Stopping the M2000 Services (SUSE).

Step 2 Check whether the Oracle service is running. For details, see 9.2 Checking Oracle Services. Ifthe Oracle service is already stopped, start the Oracle. For details about how to start the Oracle,see 9.3 Starting Oracle Service.

Step 3 Run the following commands to change the password of user ftpuser.



$ ./modify.sh

The following message is displayed:

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

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 ftp user's password: Please Re-enter the password:

Step 5 At the following prompt, enter Y for confirmation.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------------------------------------------------------------------



41

When the system displays the following information, you can infer that the change is successful.

------------------------------------------------------------------ Operation complete!

Step 6 For details on how to restart the M2000 service, refer to 8.3 Starting the M2000 Services(SUSE).

----End

6.5 Changing the Password of User oracleThis section describes how to change the password of user oracle when you log in to theM2000 database as user root. For the M2000 HA system, the password of user oracle on thetwo nodes must be consistent. Therefore, you must change the password of user oracle on theactive and standby nodes separately 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 contains 8 to 127 characters, including digits from 0 to 9, uppercase and lowercaseletters, and special characters. To improve password security, you must set the password byobserving the following rules:

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: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?and spaces

l The last 12 history passwords cannot be used.

NOTE



Procedure

Step 1 Run the following command to change the password of user oracle:

# passwd oracle

Changing password for oracle.


Reenter New Password: new password



42

Password changed.

----End

6.6 Changing the Password of User in the Oracle DatabaseThis section describes how to change the passwords of user in the Oracle database.

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

ContextThe passwords of the system user, sys user and product data users are the same. After thepassword of the system is changed, the passwords of the sys user and product data users will bechanged accordingly.

To improve password security, you are advised to use the following password policies:l The password contains 8 to 30 characters.l The password must contain a combination consisting of the following:

– The password contains at least one uppercase letter.– The password contains at least one lowercase letter.– The password contains at least one digit.– The password contains at least one of the following special characters: ~ ! # $ % ^ & *

( ) - _ + | [ { } ] ; : , < . > ?– The password can't contain the following special characters: ` @ = ' " \ / and the space

l The password must be different from the user name or the user name in reverse order.

Procedure

Step 1 Check whether the M2000 is started by referring to 8.2 Viewing the Running Status of M2000Services (SUSE). If any M2000 service is running, stop it by referring to 8.4 Stopping theM2000 Services (SUSE).

Step 2 Check whether the Oracle is started by referring to 9.2 Checking Oracle Services. If any Oracleservice stops, start it by referring to 9.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:

------------------------------------------------------------------ Welcome to use Modify tool Modify Tool (2.0.0)



43

------------------------------------------------------------------------------------------------------------------------------------Please select a(n) operator type1--IP2--Database password3--Password of ftpuserR--ReturnQ--Quit------------------------------------------------------------------Please make a choice[1-3]:

2. Based on the displayed messages, enter the old and new passwords of user system. PressEnter.------------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools ------------------------------------------------------------------Please input the old database superuser's password: Please input the new database superuser's password: Please Re-enter the password:

NOTE

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 1 to 2 minutes.

4. The password is successfully changed if the following message is displayed:------------------------------------------------------------------ Operation complete!

Step 4 Start the M2000 service, see 8.3 Starting the M2000 Services (SUSE).

----End

6.7 Changing the Password of the IMM UserThis section describes how to change the password of the IMM user USERID on the M2000.

Prerequisitesl The PC network interface is connected to the network interface for IMM management using

network cable.

l The network used by the PC to communicate with the IMM functions properly.



44

l The Dynamic Host Configuration Protocol (DHCP) service is disabled on the PC.

ProcedureStep 1 Set Internet Explorer on the PC by referring to 13.2 How Do I Set Internet Explorer on the

PC?.

Step 2 Set the IP address of the PC to be on the same network segment (192.168.70.xx for example) asthe IP address of the system management network interface on the M2000 server.

For example, set the network adapter of the PC as follows:

l Set IP address to 192.168.70.35.l Set Subnet mask to 255.255.255.0.l Leave Default gateway, Preferred DNS server, and Alternate DNS server empty.

Step 3 Type http://192.168.70.125 in the address bar of the Internet Explorer. Then, press Enter toaccess the IMM login window. If the web browser displays certificate error or untrusted website,install certificates for the web browser by referring to 13.3 How Do I Handle the Problem ofCertificate Error or Untrusted Website Displayed in the Web Browser (IMM)?.

Step 4 Type the initial user name USERID and password (Changeme_123 is the default password andneeds to be replaced with the actual password). Click Login to access the window for settingthe idle disconnection duration.

Step 5 Click Continue to access the IMM home page.

Step 6 In the navigation tree, choose System > IMM Control > Login Profiles.IMM users are displayed in Login Profiles of the window on the right side.

Step 7 Click user USERID to open the window, as shown in Figure 6-1.

Figure 6-1 Window for changing the password of IMM user USERID



45

Step 8 Enter the planned password of existing network in the Password and Confirm password textboxes.

NOTETo enhance account security, you are advised to use the following password policies:

l The password contains eight to fifteen characters.

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 as following: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ?

l The password must be different from the user name or the user name in reverse order.

l The last 5 history passwords cannot be used.

Step 9 Choose Supervisor in Authority Level.

Step 10 Click Save.

Step 11 Click OK in the displayed dialog box. The password of user USERID has been changedsuccessfully.

----End



46

7 Managing M2000 and NE Logs

About This Chapter

This section describes how to manage the operation logs, system logs, and security logs of theM2000 and NEs. You can also manage the operating system logs. By querying or collectingstatistics on logs, engineers can trace user behaviors. This facilitates system diagnosis andmaintenance.

M2000Administrator Guide (x3850&x3650, SUSE10) 7 Managing M2000 and NE Logs


47

7.1 Overview of Log ManagementBefore performing the operations related to log management, you need to be familiar with thebasic information, functions, and technical specifications of logs. The basic log knowledge helpsyou understand the contents of log management.

7.1.1 Log Management FunctionIn log management, the system, security, and operation logs that are generated during M2000running are recorded. You can query logs to understand the M2000 running status, systemsecurity status, or specific user operation. In addition, you can save log results to a file or printthe log results for future browse.

M2000 log management includes the functions such as querying logs, managing log templates,saving logs, and printing logs.

7.1.2 Log TypesThis section describes operation logs, system logs, security logs, and operating system logs ofM2000 and NEs. Each types of logs record different log information.

The M2000 Operation LogsM2000 operation logs record the user operations on the M2000 client, helping rectify faults.

DescriptionThe operation log records the operations that are performed on the M2000 client but do not affectthe M2000 security, such as creating NEs, creating views, acknowledging alarms, and clearingalarms.

PathOperation logs are stored in the database. You can query them through the client. The entry forquerying operation logs through the client is System > Log Management > Query OperationLogs.

You can dump operation logs from the database to a file. The entry for dumping operation logsis Maintenance > Task Management. In the Task Type navigation tree, choose DatabaseCapacity Management > Operation Log Dump. The default dump paths are /opt/oss/server/var/ThresholdExport/Log in Solaris and SUSE Linux.

After the operation logs are dumped, the M2000 generates the associated folder and log file:l Folder: In the dump path, the M2000 generates a folder named the date of the dump

operation. The format of the name is YYMMDD.l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-

operation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-log-dateThreshold-number.extension. The file with the suffix _info.xml saves theconfiguration information of the dumped logs, and the file with the suffix -number.extension saved the information about the dumped logs.



48

NOTE

l Operation logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can becompressed to a .zip package.

l To avoid insufficient space in the database, you can enable log dump to dump the M2000operation logs periodically or immediately. The logs that are dumped will be deleted from thedatabase.

Parameters

Parameter Name Parameter Meaning

Operation Name Name of an operation that the user performs on the M2000.

Risk Level Levels of risks caused by the operations that are performed on theM2000: Warning, Minor, and Risk.

Operation User OM user.

User Type Type of the user who performs an operation.

Operation Time Time when an operation is performed. It is accurate to second.

Operation Category Type of an operation.

Operation Terminal IP address of the host where an operation is performed.

Operation Object Object that an operation is performed on.

Operation Result Result of an operation: successful, failed, partially successful.

Details Other useful information about an operation.

The M2000 System LogsM2000 system logs record the operating information about the M2000, helping detect faults andensuring that the M2000 runs properly.

DescriptionThe system log records the tasks that are performed on the M2000 server and affect the runningof the M2000. These tasks are triggered on the M2000 client, such as starting and executingscheduled tasks, or triggered on the M2000 server, such as starting and stopping the M2000service.

PathSystem logs are stored in the database. You can query them through the client. The entry forquerying system logs through the client is System > Log Management > Query SystemLogs.



49

You can dump system logs from the database to a file. The entry for dumping system logs isMaintenance > Task Management. In the Task Type navigation tree,choose DatabaseCapacity Management > System Log Dump. The default dump paths are /opt/oss/server/var/ThresholdExport/Log in Solaris and SUSE Linux.

After the system logs are dumped, the M2000 generates the associated folder and log file:

l Folder: In the dump path, the M2000 generates a folder named the date of the dumpoperation. The format of the name is YYMMDD.

l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-system-log-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThreshold-number.extension. The file with the suffix _info.xml saves the configuration informationof the dumped logs, and the file with the suffix -number.extension saves the informationabout the dumped logs.

NOTE

l System logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be compressedto a .zip package.

l To avoid insufficient space of the database, you can set the M2000 system log dump to dumpthe M2000 system logs periodically or immediately. The dump logs are saved as files and deletedfrom the database.

Parameters


Level Levels of risks caused by the operations performed on the M2000:Warning, Minor, and Risk.

Source Module where the M2000 performs an operation.

Time Time when an operation is performed. It is accurate to second.

Basic Information Basic operation information.

Operation Result Result of an operation: successful, failed or unknown.


The M2000 Security Logs

M2000 security logs record the security-affected operations on the M2000 client, ensuring thatthe M2000 runs properly.

Description

Security logs record the security operations that the user performs in the M2000, for example,login, logout, and unlocking.



50

Path

Security logs are stored in the database. You can query them through the client. The entry forquerying security logs through the client is System > Log Management > Query SecurityLogs.

You can also dump security logs from the database to a file. The entry for dumping security logsis Maintenance > Task Management. In the Task Type navigation tree, choose DatabaseCapacity Management > Security Log Dump. The default dump paths are /opt/oss/server/var/ThresholdExport/Log in Solaris and SUSE Linux.

After the security logs are dumped, the M2000 generates the associated folder and log file:

l Folder: In the dump path, the M2000 generates a folder named the date of the dumpoperation. The format of the name is YYMMDD.

l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-security-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-log-dateThreshold-number.extension. The file with the suffix _info.xml saves theconfiguration information of the dumped logs, and the file with the suffix -number.extension saves the information about the dumped logs.

NOTE

l System logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be compressedto a .zip package.

l To avoid insufficient space of the database, you can set the M2000 security log dump to dumpthe M2000 security logs periodically or immediately. The dump logs are saved as files and deletedfrom the database.

Parameters


Security Event Event that is related to M2000 security.

Risk Level Levels of risks caused by the operations that are performed on theM2000: Warning, Minor, and Risk.

Operation User OM user.

User Type Type of an M2000 user.

Operation Time Time when an operation is performed. It is accurate to second.

Operation Terminal IP address of the host where an operation is performed.

Operation Object Object that an operation is performed on.

Operation Result Result of an operation: successful, failed or partially successful.




51

NE Operation LogsBy browsing NE operation logs, you can know the operations performed by a user at a certaintime. The operation information is used for future reference.

DescriptionNE operation logs record important operations performed by NE users, which provides operationinformation for future reference.

PathNE operation logs are generated and saved on the NEs. After being synchronized to theM2000, the logs are saved in the database. For details about how to synchronize operation logs,see 7.2 Synchronizing NE Logs. You can choose System > Log Management > Query NEOperation Logs on the client to query the operation logs.

Parameters


User Name of the user for performing theoperation.

User Type Domain attributes of the user correspondingto an NE operation log. The attributes containEMS, Local, and EMSOP.

Terminal An operation terminal identified by an IPaddress.

Start Time Start time of the operation. The format isconsistent with Setting the Time Format ofthe Client and Setting the Date Format of theClient in the region settings, for example,YYYY-MM-DD HH:MM:SS.

End Time End time of the operation. The format isconsistent with Setting the Time Format ofthe Client and Setting the Date Format of theClient in the region settings, for example,YYYY-MM-DD HH:MM:SS.

Result Whether the operation is successful or fails.

MML MML commands for performing operationson an NE.



52


Rollback MML Rollback MML displays the MMLcommands before Operation, which helpsusers to compare the operations before andafter data modification.For example, in an NE operation log, if theOperation column displays MOD GCELL:IDTYPE=BYID, CELLID=0,NEWCELLNAME="gcell2", theRollback MML column displays MODGCELL: IDTYPE=BYID, CELLID=0,NEWCELLNAME="gcell3", you can inferthat MOD GCELL: IDTYPE=BYID,CELLID=0, NEWCELLNAME="gcell2"is performed after MOD GCELL:IDTYPE=BYID, CELLID=0,NEWCELLNAME="gcell3".If the value of Rollback MML is null, youcan infer that the Rollback MML function isnot supported currently. Currently, the NEsthat support the Rollback MML function arethe BSC6900 GSM, BSC6910 GSM,BSC6910 GU and the BSC6900 GU. Thefollowing prerequisites must be met:l The current operations refer to the setting

and modification operations that supportthe rollback. That is, the MOD and SETcommands.

l The configuration authority switch on theNE is set to ON. The quick configurationmode is disabled.NOTE

By default, the configuration authority switchand the quick configuration mode on the NEare disabled. You can run the SETCMCTRLSW: CTRLSW=ON; command toenable the configuration authority switchthrough the M2000 or the LMT. You can runthe SET QUICKCFG: MODE=OFF;command to disable the quick configurationmode.

Information Details of the operation.

NE Type Type of the NE corresponding to theoperation.

NE Name Name of the NE corresponding to theoperation.



53

NE Security Logs

By browsing NE security logs periodically, you can find security vulnerabilities of the NEs andtake proper measures to ensure the security of the NEs.

Description

NE security logs record events related to NE security, such as logging in to the LMT, modifyingthe NE user rights, and adding NE users, which helps monitor the operating status of NEs.

Path

NE security logs are generated and saved on the NEs. After being synchronized to the M2000,the logs are saved in the database. For details about how to synchronize the security logs, see7.2 Synchronizing NE Logs. You can choose System > Log Management > Query NESecurity Logs on the client to query the security logs.

Parameters


User Name of the NE user that carries out a specificoperation

User Type Domain attribute of the user, such as EMS,Local, and EMSOP.

Terminal IP address of the terminal on which theoperation is performed

Security Level Class of a security event to be queried, suchas urgent, important, and subordinate.

Creation Time Time when the security event occurs

Result Whether the operation is successful or fails

Security Event Details of the security event

Message Details of the operation

NE Type Type of the NE

NE Name Name of the NE

SUSE Linux Operating System Logs

This section describes the information about the logs of the SUSE Linux operating system (SUSElogs for short), including log content, log path, and log format. By viewing SUSE logs,maintenance personnel can learn about the running status of the SUSE Linux operating systemin time. Querying SUSE logs requires few system resources and does not affect systemperformance.



54

Log Content

SUSE logs records boot messages during the startup of the SUSE Linux operating system, andother status messages during system running.

Log Path

SUSE logs are recorded in the messages file in /var/log.

Log Format

SUSE logs are recorded in the following format:Date and time of events Host name Event description

Log Check

Generally, the messages file does not contain error information such as error, Error, failed andFailed. If the file has any error information, contact technical support personnel for assistance.

MML Logs

MML log management helps query MML command issue, which facilitates fault identificationand improves maintenance efficiency.

Description

The M2000 logs the MML commands issued to NEs and results returned by the NEs, and savethe MML commands and results to the database.

Path

After being issued to NEs, MML commands are saved in the M2000 database. You can chooseSystem > Log Management > MML Log Management on the client to query the MML logs.

Parameters


Operated NE Refers to the NE involved in the execution ofan MML command.

Module Refers to the module that generates MMLlogs.

User Refers to the user who runs MML commands.

Terminal Refers to an operation terminal running MMLcommands. The terminal is identified with anIP address.

Start Time Refers to the time when the execution ofMML commands begins.



55


End Time Refers to the time when the execution ofMML commands ends.

MML Command Refers to the MML command to be executed.

Result Refers to the command result. The commandresult can be either of the following types:l Success: indicates that the MML

command is successfully executed.l Failure: indicates that the MML command

cannot be executed.

System Tool Logs

This section describes the contents, paths, and formats of the system tool logs. With the systemtool logs, security administrators can audit users' operations on a scheduled basis. This helps toidentify unauthorized user operations.

Log Content

The system tool logs consist of the M2000 application system log, OSS Self-Maintenance Unitsystem log (OSMU), operating system (OS) background tool log, and FTP log.

Log Pathl The M2000 application system log and OS background tool log are saved in the

localmessages file in the /var/log path.

l The FTP log is saved in the vsftpd.log file in the /var/log path.

l The OSMU system log is saved in the Operation.log file in the /export/home/omc_control path.

localmessages Log Format

The localmessages log format is as follows:

Date and time Host name User name: Command name;Result;Details

vsftpd.log Log Format

The vsftpd.log log format is as follows:

Date and time [Thread ID] [Login user] Operation object: Login IP, Operation result

Operation.log Log Format

The Operation.log log format is as follows:

Date and time [Login user, Login IP] Details



56

Log Dump

The system automatically dumps a log file that exceeds 20 MB, and a maximum of 10 log filescan be dumped at a time.

l The log dump path is the same as its save path.

l A dumped log file is named in the following format: source log file name-YYYYMMDD.number.

For example, localmessages-20120423.0.

The M2000 NE Syslog Run Log

NE syslog run logs record running information of NEs. The M2000 obtains NE syslog run logsfrom all managed NEs. You can browse the NE syslog run logs on the M2000 without queryingthem on each NE.

Description

NE syslog run logs record running information of NEs managed by the M2000.

Path

NE syslog run logs are stored on NEs. You can choose System > Log Management > NE SyslogRun Log on the M2000 client to query NE syslog run logs encapsulated by using the syslogprotocol.

The local path to NE syslog run logs is /opt/oss/server/var/devlogs (on Solaris and SUSELinux). An NE syslog run log file is named in YYYYMMDDHHMMSS.File name extensionformat, where the value of File name extension is txt or zip. By default, an NE syslog run logfile stores a maximum of 20,000 logs.

Parameters

Parameter Description

NE Name Name of an NE managed by the M2000.

IP Address IP address of an NE managed by the M2000.

Digest Digest of an NE syslog run log.

Details Details of an NE syslog run log.

Module Name Module corresponding to an NE syslog runlog.

Level NE syslog run log level. Log levels includethe Emergency, Alert, Critical, Error,Warning, Notice, Informational, andDebug levels.

Sending Time Time when an NE syslog run log is reported.



57

7.1.3 Log TemplatesTo facilitate log query and log statistics, the M2000 system provides the template managementfunction. That means that you can save commonly used querying or statistical items to a templatefor future use.

Log templates are categorized into querying templates and statistical templates.l You can save all the querying or statistical settings of a specific type of logs into a template.

You can click Template Filter and choose Open to query the predefined query or statisticstemplate in the template list.

l The contents of the templates are saved in the database of the server, and they are availableonly to their creators.

l Each type of log template created by a user must have a unique name.l The name of a template contains a maximum of 40 characters, and special characters, such

as ` ~ ! @ # $ % ^ & * ( ) " : ; ? , | { } [ ] < > , are not allowed.l The system does not support automatic template refreshing. This means that if a user logs

in to client A and modifies/deletes template A, template A remains unaltered when the userlogs in to client B. You can close the template first, then open it again, and the systemrefreshes the information of the template.

7.1.4 Procedure for Reporting NE LogsNE logs must be centrally reported to the M2000 client for synchronization. NE logs can bereported using a transfer server or without a transfer server.

NE logs record important events occurred on each NE. After filtering criteria are set, the requiredlog information is recorded and reported to the relevant software management server. Then, NElogs are centrally reported to the M2000 client for synchronizing NE logs.

When an NE of a certain type supports the FTP server, you can set the NE to a transfer serverfor file transfer. In this case, the NE functions as the FTP server and the M2000 server functionsas the FTP client.

For security purposes, a firewall is generally deployed between the M2000 and NEs. Only thebasic maintenance channel is retained on the firewall. The port of the maintenance channel isdefined by the company and is unlikely to be attacked. For the port used by the FTP service,however, the possibility of being attacked is higher. In this case, you can set a transfer serverand open only the FTP port of the transfer server on the firewall to reduce the possibility of beingattacked.

Based on whether a transfer server is used for reporting NE logs, the procedures for reportingNE logs are classified as follows:l Figure 7-1 shows the procedure for reporting NE logs using a transfer server.



58

Figure 7-1 Procedure for reporting NE logs using a transfer server

SMServer obtains the information about synchronizing time

SMServer sends the generated log file command to the NE

SMServer obtains the FTP user name and password

SMServer creates a save path for log files

SMServer sends the uploading commands of log files to the NE

SMServer reports the whole progress to the GUI

The NE reports progress of the generated log file to the SMServer

The NE uploads the log files to the FTP server

The NE reports the uploading progresss of the log files to SMServer


SMServer downloads the log files from the FTP server

SMServer resolves the log files to records

SMServer saves the records to the database


End



59

The procedure shown in Figure 7-1 is described as follows:

1. The software management server obtains synchronization time information, writesthe information into the database, and issues commands for generating log files toNEs.

2. NEs generate log files.3. The software management server issues commands for uploading log files to NEs.

After receiving the commands, NEs upload log files to the transfer server.4. Save original log files.5. Check whether the NEs mapped to the log files obtained from the transfer server have

been subscribed to.6. The software management server parses the log files of the subscribed NEs and saves

the parsing result in the database.l Figure 7-2 shows the procedure for reporting NE logs without a transfer server.



60

Figure 7-2 Procedure for reporting NE logs without a transfer server

SMServer obtains the information about synchronizing time

SMServer sends the generated log file command to the NE

SMServer sends the uploading commands of log files to the NE


The NE reports progress of the generated log file to the SMServer

The NE uploads the log files to SMServer

The NE reports the uploading progresss of the log files to SMServer


SMServer downloads the log files from the FTP server

SMServer resolves the log files to records

SMServer saves the records to the database


End

The procedure shown in Figure 7-2 is described as follows:

1. The software management server obtains synchronization time information, writesthe information into the database, and issues commands for generating log files toNEs.

2. NEs generate log files.



61

3. The software management server issues commands for uploading log files to NEs.After receiving the commands, the NEs upload log files to the software managementserver.

4. Save original log files.5. Check whether the NEs mapped to the obtained log files have been subscribed to.6. The software management server parses the log files of the subscribed NEs and saves

the parsing result in the database.

7.1.5 Technical Specifications of Log ManagementThis section describes the technical specifications related to the log management function.

Function Category Specification Item Value

Logs Maximum number of logs Microcomputer: 200,000Mainframe : 1,000,000

Log Storage Days of log storage M2000 logs: 90NE logs: 90

NOTE

How Do I Learn the Technical Specifications for Certain Functions? shows the categories of M2000 servers.

7.2 Synchronizing NE LogsThis section describes how to synchronize the operation logs and security logs on the M2000server with those on NEs. This helps you obtain the latest logs from NEs.

Prerequisitesl You have logged in to the M2000 client.l The NEs whose logs need to be synchronized are not virtual NEs and they must be

connected to the M2000 properly.

Context

For details about NEs that support log synchronization, see NEs Supporting LogSynchronization.

The original log files of all NEs will be saved. When synchronizing logs of subscribed NEs, theM2000 parses the original log files and saves the parsing result into the database. Whensynchronizing logs of NEs that have not been subscribed to, the M2000 does not save the originallog files into the database. You can view these log files by importing them. For details, see 7.3Importing NE Logs.

Procedurel Manually synchronize NE logs by using NE operation logs as an example.



62

Two operation entries are available for manually synchronizing NE logs. You need toperform different steps based on the entries.

Operation Entry Step

Topology view 1. Choose Topology > Main Topology. The MainTopology window is displayed.

2. In the topology view, right-click an NE whose logs are to besynchronized and choose Synchronize NE Operation &Security Logs from the shortcut menu.

The information about the synchronization task is displayed onthe Immediate Task tab page after you click the NE tab in theSoftware Browser window.

Log management 1. Choose System > Log Management > Query NEOperation Logs.

2. In the Query NE Operation Logs dialog box, clickSynchronize.

3. In the displayed Synchronize NE Logs window, click

. The Select NE dialog box is displayed.4. Select NEs whose logs are to be synchronized from the left

Available NEs area to the right Selected NEs area. You canselect a maximum of 10 NEs for synchronization at a time.

The information about the synchronization task is displayed onthe Immediate Task tab page after you click the NE tab in theSoftware Browser window.

l Set scheduled synchronization for NE logs.1. Choose Maintenance > Task Management.2. In the navigation tree in the left pane of the Task Management window, choose the

NE Log Synchronization node.3. In the task list in the Task Management window, double-click the NE Log

Synchronization task.4. In the Attribute dialog box, modify common parameters. For details about the

parameters, see Parameters for Scheduled Task Properties.5. Click OK.

l Subscribe to NEs.

Two operation entries are available for subscribing to NEs. You need to perform differentsteps based on the entries.



63

Operation Entry Step

Log management 1. Choose System > Log Management > Query NEOperation Logs.

2. In the Query NE Operation Logs dialog box, clickSubscribe.

3. Subscribe to NEs by referring to Subscription Type.

Task management 1. Choose Maintenance > Task Management.2. In the navigation tree in the left pane of the Task

Management window, choose the NE LogSynchronization node.

3. In the task list in the Task Management window, double-click the NE Log Synchronization task.

4. In the Attribute dialog box, click the ExtendedParameters tab.

5. Subscribe to NEs by referring to Subscription Type.

Subscription Type

– Subscribing to NEs by NEClick By NE.

1. Click . The Select NE dialog box is displayed.2. Select one or more NEs from the navigation tree in the left pane.

3. You can click to add the selected NEs to the effective area in the rightpane. You can click to add all NEs from the navigation tree in the leftpane to the effective area in the right pane.

NOTE

l You can click to delete the selected NEs from the effective area in the right

pane. You can click to delete all NEs from the effective area in the rightpane.

l You can click or to expand or collapse the nodes in the navigation tree.

l You can click and enter NE names in Name to filter NEs in the navigation tree.

4. Click OK.– Subscribing to NEs by NE type

Click By NE Type.

1. Click . The Select NE Type dialog box is displayed.2. Select one or more NE types from the navigation tree in the left pane.

3. You can click to add the selected NE types to the effective area in theright pane. You can click to add all NE types from the navigation tree inthe left pane to the effective area in the right pane.



64

NOTE

You can click to delete the selected NEs from the effective area in the right pane.

You can click to delete all NEs from the effective area in the right pane.

4. Click OK.– Subscribing to NEs on the entire network

Select All NEs. The system then subscribes to all existing NEs on the network.

CAUTIONIf you select this subscription type, the system overhead will increase significantly.Therefore, narrow down the subscription range as required.

----End

7.3 Importing NE LogsYou can view NE operation and security logs by importing original NE log files.

Context

CAUTIONIf the active and standby servers in a remote HA system are switched over before original NElog files are imported, original NE log files saved before the switchover cannot be imported. Ifthe active and standby servers are switched over then switched back, original NE log files savedbefore the switchover can be imported.

Procedure

Step 1 Choose System > Log Management > Query NE Operation Logs or System > LogManagement > Query NE Security Logs.

Step 2 In the displayed window for querying logs, click Import.

Step 3 In the Import NE Logs dialog box, set Time Range and NEs.1. Set Time Range.

Select From and To, type the date and time in the text boxes, or click and set time inthe Date/Time Selection dialog box.

For example, set the time range to 2011-11-10 00:00:00 2011-11-11 00:00:00.2. Set NEs.

a. Click . The Select NE dialog box is displayed.



65

b. Select one or more NEs from the navigation tree in the left pane.

c. You can click to add the selected NEs to the effective area in the right pane.You can click to add all NEs from the navigation tree in the left pane to theeffective area in the right pane.

NOTE

l You can click to delete the selected NEs from the effective area in the right pane.

You can click to delete all NEs from the effective area in the right pane.

l You can click or to expand or collapse the nodes in the navigation tree.

l You can click and enter NE names in Name to filter NEs in the navigation tree.

d. Click OK.

Step 4 Click OK to view the NE log import task in Immediate Task of the log query window.NOTE

l The database capacity size is limited. You are advised to import log data by specifying a time range asrequired to avoid significant increase of system overhead.

l When the database capacity reaches a threshold, the system displays a message stating that the NE logdata fails to be imported.

l Only one user can import NE log data within a time segment.l If NE log data is being imported, do not synchronize NE logs until the import is complete. Otherwise,

the selected data to be imported may be deleted because of the limited database capacity.

----End

7.4 Managing the M2000 Operation LogsYou can query and collect statistics on operation logs of the M2000 to understand the operationstatus of the M2000.

7.4.1 Querying the M2000 Operation LogsYou can query the M2000 operation logs to know the operation records of the M2000.

Contextl When you query operation logs by user name, only names of the users that have performed

operations are displayed under Available Operation User in the Select Operation Userdialog box.

l Operation log query scopes vary according to user.– Users in the Administrators group can query operation logs of all users.– Users in the SMManagers group who have the Query Operation Logs right can query

operation logs of all users.– Common users who do not belong to the Administrators or SMManagers group and

who have the Query Operation Logs right can query only their own operation logs.To query operation logs of all users, set isQueryAll in the logsvc.xml file on theM2000 server to 0, run the following command as user ossuser to import the parametersin the file to the database, and restart the M2000 service for the setting to take effect.(Assume that the following command is run in the Solaris operating system).



66

$ cd /opt/oss/server

$ . ./svc_profile.sh

$ SettingTool -cmd import -file /opt/oss/server/etc/conf/logsvc.xml

$ svc_adm -cmd reload

$ stop_svc

$ start_svc

l The statistical result is generated based on the existing data in the database. If the databaseis empty, there is no statistical result.

l If a value in the Operation User column in the log query result is an invalid user, the systemmay have been attacked.

Procedure

Step 1 Choose System > Log Management > Query Operation Logs .

Step 2 In the Filter dialog box, set the filtering conditions, and then click OK.

NOTE

l You can also click Cancel in the Filter dialog box, and then query logs in the Query OperationLogs window in the following ways:

l Click Template Filter, and then select Open. Select a template from the template list, and thenclick Open to use an existing template to query logs. If no template exists on the M2000, see 7.12Setting M2000 Log Templates to create a template.

l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs.

l In the Filter dialog box, click Choose in Operation Name, and view the operations that can bemonitored in the Select Operation Name dialog box. The Log out the server operation is notmonitored. Click Choose in Operation Object, and view the operation objects that can be monitoredin the Select Operation Object dialog box.

Step 3 Right-click in the query window and perform the following operations.

Operation Name Operation Method

Details Right-click a log in the window and choose Details, or double-clickthe log.NOTE

The Log Details dialog box displays the time, risk level, or results of theoperation that generates the log.

Save All Records 1. Right-click a log in the window and choose Save All Records.2. In the Save dialog box, select the path to save records, and then

click Save.NOTEl Log records can be saved in TXT, HTML, CSV, PDF, XLSX or XLS format.

The default file format is XLS.

l For .txt files, code formats ISO-8859-1 and UTF-8 are supported. Thedefault encoding format is ISO-8859-1. You are recommended to use thedefault encoding format if the saved file does not need to support multiplelanguages; otherwise, UTF-8 is recommended.



67


Save SelectedRecords

1. Select one or more logs in the window, right-click, and then chooseSave Selected Records from the shortcut menu.

2. In the Save dialog box, select the path to save records, and thenclick Save.

NOTEl Log records can be saved in TXT, HTML, CSV, PDF, XLSX or XLS format.



Save SpecifiedRecords

1. Right-click a log in the window and choose Save SpecifiedRecords.

2. In the Save Specified Record dialog box, set the start row and endrow of logs and the name of the file to be saved, and then clickOK.

NOTE

l In the Save Specified Records dialog box, click on the right of Filename. In the Save dialog box, select the path for saving the records. Logrecords can be saved in TXT, HTML, CSV, PDF, XLSX or XLS format.The default file format is XLS.


Print All Records 1. Right-click a log in the window and choose Print All Records.2. In the Print dialog box, set the print parameters, and then click

Print.

Print SelectedRecords

1. Select one or more logs in the window, right-click, and then choosePrint Selected Records from the shortcut menu.

2. In the Print dialog box, set the print parameters, and then clickPrint.

Print SpecifiedRecords

1. Right-click a log in the window and choose Print SpecifiedRecords.

2. In the Print Specified Records dialog box, set the start row andend row, and then click OK.


----End



68

7.4.2 Collecting Statistics on the M2000 Operation LogsYou can know the operation status by collecting statistics and analyzing the M2000 operationlogs. For example, you can collect statistics about the frequently performed operations within aperiod.

ContextThe statistical result is generated based on the existing data in the database. If the database isempty, there is no statistical result.

Procedure

Step 1 Choose System > Log Management > Operation Log Statistics.

Step 2 In the Filter window, set the statistical items and statistical conditions, and then click OK.

NOTE

You can also click Cancel, and then collect statistics in the Operation Log Statistics window in thefollowing ways:

l Click Template, and then select Open. Select a template from the template list, and then click Opento use an existing template to collect statistics on operation logs. If no template exists on the M2000,see 7.12 Setting M2000 Log Templates to create a template.

l Click Filter. Set Statistical Items and Filter Criteria in the Filter window, and then click OK tocollect statistics on operation logs.

----End

ResultIn the Operation Log Statistics window, the statistical result is displayed.

The display mode of statistic results varies according to the settings on the Statistical Items tabpage in the Filter dialog box. The display mode of statistic results varies according to the settingson the Statistical Items tab page. Table 7-1 describes the settings and display mode of theStatistical Items tab page.

Table 7-1 Settings and display mode of the Statistical Items tab page

Row 1 Row 2 Column Display Mode

Do not set it to(None).


Set it to (Count). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row

1, and Row 1 is displayed byRow 2 in a collapsed tree.


Set it to (None) Set it to (Count). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row

1 or Row 2.

Set it to (None). Do not set it to(None).

Set it to (Count).



69




Do not set it to(Count).

The statistic result is displayed asfollows:l Row is displayed by

Column.l Column is displayed by Row



Set it to (None). Do not set it to(Count).



1 or Row 2.



Note: Row 1 and Row 2 are two statistical items in Statistical Row. Column is a statisticalitem in Statistical Column.

In the Operation Log Statistics window, perform the following steps:l Click Print to print the statistical result.l Click Save As to save the statistical result.

7.5 Managing the M2000 System LogsYou can query and collect statistics on system logs of the M2000 to understand the runningstatus of the M2000.

7.5.1 Querying the M2000 System LogsYou can query the M2000 system logs to know the important events that occur when theM2000 is running.


Procedure

Step 1 Choose System > Log Management > Query System Logs.




70

NOTE

You can also click Cancel in the Filter dialog box, and then query logs in the Query System Logs windowin the following ways:

l Click Template Filter, and then select Open. Select a template from the template list, and then clickOpen to use an existing template to query logs. If no template exists on the M2000, see 7.12 SettingM2000 Log Templates to create a template.


















71





NOTE




Print.








----End

7.5.2 Collecting Statistics on the M2000 System LogsYou can know the system status by collecting statistics and analyzing the M2000 system log.For example, you can know the type of the services that raise the most alarms.

Context

The statistical result is generated based on the existing data in the database. If the database isempty, there is no statistical result.

Procedure

Step 1 Choose System > Log Management > System Log Statistics.



72

Step 2 In the Filter window, set the statistical condition, and then click OK.

NOTE

You can also click Cancel, and then collect statistics in the System Log Statistics window in the followingways:

l Click Template, and then select Open. Select a template from the template list, and then click Opento use an existing template to collect statistics on system logs. If no template exists on the M2000, see7.12 Setting M2000 Log Templates to create a template.

l Click Filter. Set the statistical condition in the Filter window, and then click OK to collect statisticson system logs.

----End

ResultIn the System Log Statistics window, the statistical result is displayed.



Row Column Display Mode

Set it to Level. Set it to (Count). The statistic result is displayed as follows:l Row is displayed by Value.l Column is displayed by Level or

Source.

Set it to Source. Set it to (Count).

Set it to Level. Set it to Source. The statistic result is displayed as follows:l Row is displayed by Source.l Column is displayed by Level.

Set it to Source. Set it to Level. The statistic result is displayed as follows:l Row is displayed by Level.l Column is displayed by Source.

Note: Row is a statistical item in the Statistical Row group box, and Column is a statisticalitem in the Statistical Column group box.

In the System Log Statistics window, perform the following steps:l Click Print to print the statistical result.l Click Save As to save the statistical result.

7.6 Managing the M2000 Security LogsYou can query and collect statistics on security logs of the M2000 to understand the securityoperation status of the M2000.



73

7.6.1 Querying the M2000 Security LogsYou can query the M2000 security logs to know the M2000 security operations of the M2000.

Contextl The statistical result is generated based on the existing data in the database. If the database

is empty, there is no statistical result.

l If a value in the Operation User column in the log query result is an invalid user, the systemmay have been attacked.

Procedure

Step 1 Choose System > Log Management > Query Security Logs.


NOTE

l You can also click Cancel in the Filter dialog box, and then query logs in the Query Security Logswindow in the following ways:

l Click Template Filter, and then select Open. Select a template from the template list, and thenclick Open to use an existing template to query logs.

If no template exists on the M2000, see 7.12 Setting M2000 Log Templates to create a template.


l In the Filter dialog box, click Choose in Security Event, and view the operations that can be monitoredin the Select Security Event dialog box. The Log out the server operation is not monitored. ClickChoose in Operation Object, and view the operation objects that can be monitored in the SelectOperation Object dialog box.











74











NOTE




Print.








----End



75

7.6.2 Collecting Statistics on the M2000 Security LogsYou can know the security operations by collecting statistics and analyzing the M2000 securitylogs. For example, you can know the period during which maximum number of securityoperations are performed and the operations that are performed most frequently.


Procedure

Step 1 Choose System > Log Management > Security Log Statistics.

Step 2 In the Filter window, set the statistical items and filtering conditions, and then click OK.

NOTE

You can also click Cancel, and then collect statistics in the Security Log Statistics window in the followingways:

l Click Template, and then select Open. Select a template from the template list, and then click Opento use an existing template to collect statistics on security logs. If no template exists on the M2000, see7.12 Setting M2000 Log Templates to create a template.

l Click Filter. Set Items and Filter Criteria in the Filter window, and then click OK to collect statisticson security logs.

----End

ResultIn the Security Log Statistics window, the statistical result is displayed.






Set it to (Count). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row



Set it to (None) Set it to (Count). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row

1 or Row 2.


Set it to (Count).



76









Set it to (None). Do not set it to(Count).



1 or Row 2.




In the Security Log Statistics window, perform the following steps:l Click Print to print the statistical result.l Click Save As to save the statistical result.

7.7 Managing NE Operation LogsYou can query and collect statistics on operation logs of the NE to understand the operationstatus of the NE.

7.7.1 Querying NE Operation LogsYou can query NE operation logs to know the operation records of the NE.

ContextThe statistics result is generated based on the existing data in the database and sorted by time(Greenwich Mean Time). If the database is empty, no statistics result is displayed accordingly.

Procedure

Step 1 Choose System > Log Management > Query NE Operation Logs.

Step 2 In the Filter Criteria window, set the filter conditions, and then click OK.



77

NOTEYou can also click Cancel, and then query logs in the Query NE Operation Logs window in the followingways:

l Click Template, and then select Open. Select a template from the template list, and then click Opento use an existing template to query logs.

l Click Filter. Set the query conditions in the Filter Criteria window, and click OK to query logs.

----End

7.7.2 Collecting Statistics on NE Operation LogsYou can know the operation status of an NE by collecting statistics and analyzing the operationlog. For example, you can know the period during which maximum number of operations areperformed, and the period during which operations are performed most frequently.

ContextThe statistics result is generated based on the existing data in the database and sorted by time(Greenwich Mean Time). If the database is empty, no statistics result is displayed accordingly.

Procedure

Step 1 Choose System > Log Management > NE Operation Log Statistics .

Step 2 In the Filter Criteria window, set statistical items and filter criteria, and then click OK.

NOTEYou can also click Cancel, and then collect statistics in the NE Operation Log Statistics window in thefollowing ways:

l Click Template, and then select Open. Select a template from the template list, and then click Opento use an existing template to collect statistics on operation logs.

l Click Statistics. Set Statistics Items and Filter Criteria in the Filter Criteria window, and then clickOK to collect statistics on operation logs.

----End

ResultIn the NE Operation Log Statistics window, the statistical result is displayed.




78





Set it to (None). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row



Set it to (None) Set it to (None). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row

1 or Row 2.


Set it to (None).











1 or Row 2.




In the NE Operation Log Statistics window, the statistical result is displayed.

Perform the following operations as required:l Click Print to print the statistical result.l Click Save to save the statistical result.

7.8 Managing NE Secrity LogsYou can query and collect statistics on security logs of the NE to understand the securityoperation status of the NE.



79

7.8.1 Querying NE Security LogsThis section describes how to query NE security logs. You can query NE security logs to knowthe security operations performed on NEs.

Context

The statistics result is generated based on the existing data in the database and sorted by time(Greenwich Mean Time). If the database is empty, no statistics result is displayed accordingly.

Procedure

Step 1 Choose System > Log Management > Query NE Security Logs.

Step 2 In the Filter Criteria window, set filter criteria and click OK.

CBTS security logs are synchronized to the M2000 together with CBSC security logs. You canenter BTS ID in Information Filter to query CBTS security logs when setting filter criteria.

NOTEAlternatively, you can click Cancel and query logs in the Query NE Security Log window using eitherof the following methods:

l Click Template, and choose Open. Select a template from the template list and click Open to use theexisting template to filter logs.

l Click Filter and set filter criteria in the Filter Criteria dialog box. Then, click OK.

----End

7.8.2 Collecting Statistics on NE Security LogsYou can know the security operations of an NE by collecting statistics and analyzing the securitylog. For example, you can know the period during which maximum number of securityoperations are performed, and the period during which operations are performed most frequently.

Context

The statistics result is generated based on the existing data in the database and sorted by time(Greenwich Mean Time). If the database is empty, no statistics result is displayed accordingly.

Procedure

Step 1 Choose System > Log Management > NE Security Log Statistics.

Step 2 In the Filter Criteria window, set statistical items and filter condition, and then click OK.

NOTEYou can also click Cancel, and then collect statistics in the NE Security Log Statistics window in thefollowing ways:

l Click Template, and then select Open. Select a template from the template list, and then click Opento use an existing template to collect statistics on security logs.

l Click Statistics. Set Statistics Items and Filter Criteria in the Filter Criteria window, and then clickOK to collect statistics on security logs.

----End



80

Result

In the NE Security Log Statistics window, the statistical result is displayed.






Set it to (None). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row



Set it to (None) Set it to (None). The statistic result is displayed asfollows:l Row is displayed by Value.l Column is displayed by Row

1 or Row 2.


Set it to (None).











1 or Row 2.




In the NE Security Log Statistics window, the statistical result is displayed.

Perform the following operations as required.

l Click Print to print the statistical result.

l Click Save to save the statistical result.



81

7.9 Browsing the NE Syslog Run LogsAfter the IP address and port of an M2000 server are configured on network elements (NEs),the NEs automatically upload Syslog run logs to the M2000. Then you can browse Syslog runlogs of NEs managed by the M2000 on the M2000, instead of browsing the logs on the NEsindividually.

Prerequisitesl The IP address and port of an M2000 server have been configured on NEs. For configuration

details, see product documentation for the NEs.l The SyslogCollectorDM service has been started. By default, the SyslogCollectorDM

service is not started. For details about how to start the SyslogCollectorDM service, seeHow Do I Start the Services that Are Disabled by Default in the M2000 AdministratorGuide.

Procedure

Step 1 Choose System > Log Management > NE Syslog Run Log .

Step 2 In the DRL File List navigation tree, double-click an NE Syslog run log file, such as20120530170812. In the right pane, click a record to view log details.

NOTE

l The files in the device run log (DRL) file list are listed by time.

l You can enter the file name in the text box above the DRL File List navigation tree to filter the DRLfiles. Only numbers from 0 to 9 are allowed. Then, the matched files are displayed in the DRL FileList navigation tree.

Step 3 Click Condition. In the Filter Criteria dialog box that is displayed, set the filter criteria forfiltering out NE syslog run logs.

Step 4 Click Query to query NE syslog run logs.

----End

7.10 Querying MML LogsThe MML log records all NE-related MML command operations and results returned by theNEs, and save the MML commands and results to the database.

Prerequisitesl You have logged in to the M2000 client.l You are authorized to perform the related operations. For example, you are authorized to

query and delete an MML log.

ContextThe MML logs are saved in the M2000 database omcdb, which contains a maximum of 100,000log records. If the number of records exceeds 100,000, the first log records are replaced with thelatest records.



82

NOTE

MML logs are recorded when you use the following functions.

l CBSS Enhanced Configuration

l WiMAX Enhanced Configuration

l MSC Pool

l CDMA Pool

l SGSN Pool

l SingleSDB

l CSCF Pool

l MME Pool

Procedure

Step 1 Choose System > Log Management > MML Log Management.

Step 2 In the Query MML Log dialog box, set the conditions for querying the MML log.

1. In the Operated NE field, click . In the Operated NE Select dialog box, select an NEwhose MML log you want to query.

l You can select an NE in Available NEs, and click to move the NE toSelected NEs.

l You can hold down Shift or Ctrl to select multiple NEs.

l You can click to move all the NEs from Available NEs to SelectedNEs.

l You can click or to remove the NEs from Selected NEs.

NOTE

You can query MML logs based on one or more of the following filtering criteria: NE name, MMLcommand head, module name, subscriber name, and date.

2. In the Time Range group box, set the start time and end time of running the MMLcommand.

3. Click Advanced. The system displays the other parameters related to the MML log query,including MML Command, Module, User, and Terminal.

4. In the fields of the previous parameters, click one by one. In the displayed dialog box,set these parameters.If you do not set these parameters, the system queries all the MML logs by default.

Step 3 Click OK.In the MML Log Management window, the system displays the information about all thequeried MML logs. For the contents and description of each MML log, see Table 1.


Operated NE Refers to the NE involved in the execution ofan MML command.

Module Refers to the module that generates MMLlogs.



83


User Refers to the user who runs MML commands.

Terminal Refers to an operation terminal running MMLcommands. The terminal is identified with anIP address.

Start Time Refers to the time when the execution ofMML commands begins.

End Time Refers to the time when the execution ofMML commands ends.

MML Command Refers to the MML command to be executed.

Result Refers to the command result. The commandresult can be either of the following types:l Success: indicates that the MML

command is successfully executed.l Failure: indicates that the MML command

cannot be executed.

Step 4 Select a record and double-click it. Alternatively, right-click a record, and then chooseDetails. In the displayed MML Log Detail Info dialog box, view the details of the MML log.

l The detailed information that you can query includes the information listed in Table 1 andthe MML Report.

l You can query the information about other MML logs by clicking Previous or Next.

Step 5 Optional: Perform the following operations as required.

l In the MML Log Management window, click Delete to delete the logs that are not required.

l In the MML Log Management window, click Refresh to refresh the queried result.

l In the MML Log Management window, click Print to print the queried result.

l In the MML Log Management window, click Save As to save the queried result to a localdisk.

----End

7.11 Managing Log DataBy dumping logs, you can periodically or manually clear the log information that is not required,preventing the log information from occupying many resources. By exporting logs to files, youcan view logs and identify faults.

7.11.1 Setting M2000 Log DumpingBy setting M2000 log dump, you can periodically or instantly dump security logs, operationlogs, and system logs of the M2000. The dumped logs are saved in files and deleted from thedatabase. This prevents database space insufficiency.



84

Prerequisites

You have logged in as a user in Administrators.

Context

Each of the types Operation Log Dump, Security Log Dump and System Log Dump has adefault system task that is provided by the M2000. You are not allowed to delete this systemtask, but you can modify its setting. In addition, you cannot create new tasks of these three types.

Procedure

Step 1 Choose Maintenance > Task Management.

Step 2 In the Task Type navigation tree, expand the Database Capacity Management node, chooseOperation Log Dump,Security Log Dump or System Log Dump.

Step 3 Double-click the task in the task list.

NOTE

In the task list, right-click the log dump task and choose Run Immediately. The log dump task is performedinstantly.

Step 4 In the displayed Attribute dialog box, set the parameters on the Common Parameters andExtended Parameters tabs.

Step 5 Click OK.

NOTE

The time displayed in the M2000 log record is the start time of an operation. If the start time of the operationis within the time range for dumping logs, but the operation is not complete when the time for dumpinglogs is reached, this log record is not dumped to the log file.

----End

Result

You can view the M2000 log file in File path on the Extended Parameters tab page.

7.11.2 Setting M2000 Log ExportBy setting M2000 log export, you can periodically or instantly export security logs, operationlogs, and system logs of the M2000. The exported logs are saved in files. Thus, they cannot bedeleted from the database.

Prerequisites

You have logged in as a user in Administrators.

Context

Each of the types Operation Log Export, Security Log Export and System Log Export hasa default system task that is provided by the M2000. You are not allowed to delete the systemtask, but you can modify its setting. In addition, you cannot create new tasks of these three types.



85

Procedure


Step 2 In the Task Type navigation tree, choose File Interface > Operation Log Export,FileInterface > Security Log Export or File Interface > System Log Export.


NOTE

To perform the operations such as executing an export task instantly, suspending an task, and setting timingsuspending and resuming, right-click the log export task in the right area and choose the correspondingmenus.

Step 4 In the Attribute dialog box, set the parameters on the Common Parameters and ExtendedParameters tabs. For the parameter descriptions, see 7.13.12 Parameters for Setting M2000Log Timing Export.

NOTEThe format of the export files of logs is CSV or XML or TXT or HTML.

Step 5 Click OK.

NOTE

The time displayed in the M2000 log record is the start time of an operation. If the start time of the operationis within the time range for exporting logs, but the operation is not complete when the time for exportinglogs is reached, this log record is not exported to the log file.

----End

ResultYou can view the M2000 log file in File path on the Extended Parameters tab page.

7.11.3 Setting NE Log ExportBy setting NE log export, you can periodically or instantly export security logs and operationlogs of the NE. The exported logs are saved in files. Thus, they cannot be deleted from thedatabase.

Procedure


Step 2 In the Task Type navigation tree, choose File Interface > NE Operation Log Export or FileInterface > NE Security Log Export.


NOTE

The log export task is suspended by default.To perform the operations such as executing an export task instantly, suspending an task, and setting timingsuspending and resuming, right-click the log export task in the right area and choose the correspondingmenus.

Step 4 In the Attribute dialog box, set the parameters on the Common Parameters and ExtendedParameters tabs. For the parameter descriptions, see 7.13.14 Parameters for the Export ofNE Logs.



86

NOTEThe format of the export files of logs is CSV or TXT.

Step 5 Click OK.

----End

7.12 Setting M2000 Log TemplatesBy setting M2000 log templates, you can save the specific query and statistical conditions in logtemplates. This helps you to query and collect statistics on logs conveniently.

Context

l Choose System > Log Management > Query Operation Logs, System > LogManagement > Query System Logs, System > Log Management > Query SecurityLogs, System > Log Management > Operation Log Statistics, System > LogManagement > System Log Statistics, System > Log Management > Security LogStatistics . Click Template Filter to set the template.

l The operations for setting the log query and statistic collection templates are similar. Thefollowing is an example of setting the log query template.

Procedure

Step 1 Choose System > Log Management > Query Operation Logs.

Step 2 In the Filter dialog box, click Cancel.

Step 3 You can perform the following operations in the Query Operation Logs window.

Task Operation

Create a template 1. Choose Template Filter > New.2. In the Enter Template Name dialog box, enter the template name,

and then click OK.3. In the Filter dialog box, set the filtering conditions of template

parameters, and then click OK.

Modify a template If there is already a log query template or a log statistics template onthe M2000, you can do as follows to modify the template:1. Choose Template Filter > Open. Select a template in the Open

dialog box, and then click Open.2. In the Query Operation Logs window, click Filter.3. In the Filter dialog box, modify the query conditions in the log

template, and then click OK.4. In the Query Operation Logs window, choose Template Filter >

Save.



87

Task Operation

Save As You can do as follows to save and modify a log query or statisticstemplate:

1. Choose Template Filter > Save As.2. In the Enter Template Name dialog box, enter the template name,

and then click OK.

Delete a template If there is already a log query template or a log statistics template onthe M2000, you can do as follows to delete the template:

Delete the operations in the template.1. Choose Template Filter > Delete.2. In the displayed Delete dialog box, select the specified template.3. Click Delete.4. In the Confirm dialog box, click Yes.5. In the Delete dialog box, click Close.

----End

7.13 References for Log Management InterfacesThis part describes reference information and the interface of log management. The contents inthis part consist of the log management interface and parameters involved in the process ofquerying and taking statistics of NE logs, system logs, operation logs, and security logs. Thishelps you perform the operations related to log management.

7.13.1 Interface Description: Log ManagementThis part describes the log management interface. You can have an understanding of each parton the log management interface and their functions.

For details about the interfaces for log query or log statistics collection, refer to Figure 7-3.After the filter conditions are set, the results of log query or log statistics collection are displayedin the log window. You can save or print the results by clicking the buttons on the interface.



88

Figure 7-3 Log management interface

7.13.2 Parameters for Querying Operation LogsThis topic describes the parameters in the Query Operation Logs window and the Filter dialogbox. When querying operation logs or set the filter criteria for operation logs, you can refer tothis topic to set the filter criteria.

ParametersParameter Description Settings

Operation User Description:To select operation users forquerying their operation logs.

Setting method:In the Filter dialog box, click

. From the Select OperationUser dialog box, select anoperation user to be queried.NOTE

By default, all users' operation logswill be queried.

Operation Terminal Description:To select operation terminals.Queried operation records aredisplayed by operation terminal.


. From the Select OperationTerminal dialog box, select oneor more items.NOTE

By default, the operation logs for allusers are queried.



89

Parameter Description Settings

Operation Result Description:To query logs by operation result.

Value:l Successful means that the

operation is complete and allresults are returned.

l Failed means that theoperation fails.

l Partially successful meansthat the operation is completeand part of operation resultsare returned.

Setting method:In the Filter dialog box, selectone or more items from theOperation Result group box.

Risk Level Description:To query logs by risk level.

Value:Value range: Warning, Minor,and RiskSetting method:In the Filter dialog box, selectone or more items from the RiskLevel group box.

Time Range Description:To set the time range withinwhich the operations generatedcan be queried. If the time rangeis not set, all logs generated at anytime are queried.

Setting method:In the Filter dialog box, selectFrom and To check box on theleft side, and then enter the dateand time directly in the text box,

or click and set the time inthe Select Time dialog box.Example:Example: Set the time range to02/08/200900:00:00-02/09/2009 00:00:00.

Detail informationcontains

Description:In the Query Operation Logswindow, you can set whether todisplay the Details column ofoperation logs.In Detail information contains,enter the information to bedisplayed in the Details column.The M2000 filters operation logsbased on the informationprovided in Detail informationcontains.

Setting method:In the Filter dialog box, selectthe Detail informationcontains check box, and thenenter the fields to be contained inDetails in the text box that is onthe right of the check box.



90


Operation Name Description:To query logs by operation.


correspondingto Operation Name. In theSelect Operation Name dialogbox, select one or more items.

Operation Object Description:To query logs by operationobject.


correspondingto Operation Object. In theSelect Operation Object dialogbox, select one or more items.

User Type Description:User type of the user thatperforms an operation, includingsystem administrator and localuser.

-

Operation Time Description:Time when the operation isperformed.

-

Operation Category Description:Category to which an operationbelongs.

-

Details Description:Details about an operation.

-

7.13.3 Parameters for Collecting Statistics on Operation LogsThis topic describes the parameters in the Filter dialog box. When collecting statistics onoperation logs, you can refer to this topic to set the statistical conditions.



91

Statistical items


Row Statistical Item Description:To set the row heading ofthe statistical result table.

Value:The parameter valuesinclude None, OperationUser, User Type,Operation Name,Operation Category,Operation Terminal,Operation Result, andOperation Object.

Statistical Item Description:To set the row heading ofthe statistical result table.This parameter is the sub-item of the precedingparameter StatisticalItem.

Value:The parameter valuesinclude None, OperationUser, User Type,Operation Name,Operation Category,Operation Terminal,Operation Result, andOperation Object.NOTE

You can set at most one ofboth Statistical Item inRow to None. Thestatistical results aregrouped by StatisticalItem.

Column Statistical Item Description:To set the column headingof the statistical resulttable.

Value:The parameter valuesinclude Count,Operation User, UserType, Operation Name,Operation Category,Operation Terminal,Operation Result, andOperation Object.

Example Description:To preview the style ofthe statistical result table.

-



92

Filter CriteriaParameter Description Settings

Operation User Description:To collect statistics by user.

Setting method:

Click . In the SelectOperation User dialog box,select one or more items.NOTE

By default, statistics on all users'operation logs will be collected.

Operation Terminal Description:To select operation terminals.Operation log statistics arecollected by operation terminal.

Setting method:

Click . In the SelectOperation Terminal dialogbox, select one or more items.

Operation Result Description:To collect statistics by operationresult.


operation is being carried outand all results are returned.


l Partially successful meansthat the operation is completebut part of operation resultsare returned.

Setting method:From the Operation Resultgroup box, select one or moreitems.

Risk Level Description:To collect statistics by operationlevel.

Value:Warning, Minor, and RiskSetting method:From the Risk Level group box,select one or more items.

Time Range Description:To collect statistics by timerange.

Setting method:Select From and To check boxeson the left side, and then enter thedate and time directly in the text

box, or click and set the timein the Select Time dialog box.Example:Example: Set the time range to02/08/200900:00:00-02/09/2009 00:00:00.



93



Description:In the Operation Log Statisticswindow, you can set whether todisplay the Details column ofoperation logs.In Detail information contains,enter the information to bedisplayed in the Details column.The M2000 filters operation logsbased on the informationprovided in Detail informationcontains.

Setting method:Select the Detail informationcontains check box, and thenenter the fields to be contained inDetails in the text box that is onthe right of the check box.

Operation Name Description:To collect statistics by operation.

Setting method:

Click corresponding to Operation. Inthe Select Operation Namedialog box, select one or moreitems.

Operation Object Description:To collect statistics by operationobject.

Setting method:

Click corresponding to OperationObject. In the Select OperationObject dialog box, select one ormore items.

7.13.4 Parameters for Querying System LogsThis topic describes the parameters in the Query System Logs window and the Filter dialogbox. When querying system logs or set the filter criteria for system logs, you can refer to thistopic to set the filter criteria.


Source Description:To select the source of systemlogs for query.


. In the Select Source dialogbox, select one or more items.NOTE

By default, all sources' system logswill be queried.



94


Level Description:To query logs by log level.

Value:Warning, Minor, and Risk.Setting method:In the Filter dialog box, selectone or more items from theLevel group box.

Operation Result Description:To query logs by log operationresult.




l Unknown means that anoperation result is unknown.If the value of OperationResult in the Query SystemLogs window is Unknown,identify the cause of theunknown operation resultbased on Basic Informationand Details.


Time Range Description:To query logs by time range. Ifthe time range is not set, all logsgenerated at any time arequeried.


or click and set the time inthe Select Time dialog box.Example:Example: Set the time range to02/08/200900:00:00-02/09/2009 00:00:00.NOTE

To set the time format, chooseSystem > Preferences, expandRegion Settings, and then choosethe Time node. Set Time Format inthe area on the right.



95



Description:In the Query System Logswindow, you can set whether todisplay the Details column ofsystem logs.In Detail information contains,enter the information to bedisplayed in the Details column.The M2000 filters system logsbased on the informationprovided in Detail informationcontains.

Setting method:In the Filter dialog box, selectthe Detail informationcontains check box, and thenenter the fields to be contained inDetails in the text box that is onthe right of the check box.

Time Description:Time for executing a systemoperation.

-

Basic Information Description:Basic information about a systemoperation.

-

Details Description:Details about a system operation.

-

7.13.5 Parameters for Collecting Statistics on System LogsThis topic describes the parameters in the Filter dialog box. When collecting statistics on systemlogs, you can refer to this topic to set the statistical conditions.

Statistical items


Row Statistical Item Description:To set the row heading ofthe statistical resulttable.

Value:The parameter valuesinclude None,Level, andSource.

Column Statistical Item Description:To set the columnheading of the statisticalresult table.

Value:The parameter valuesinclude Count, Level,and Source.

Example Description:To preview the style ofthe statistical resulttable.

-



96


Source Description:To collect statistics by source.

Setting method:

Click . In the Select Sourcedialog box, select one or moreitems.NOTE

By default, statistics on all sources'system logs will be collected.

Level Description:To collect statistics by log level.

Value:Warning, Minor, and Risk.Setting method:From the Level group box, selectone or more items.

Operation Result Description:To query logs by log operationresult.




l Unknown means that anoperation result is unknown.If the value of OperationResult in the Query SystemLogs window is Unknown,identify the cause of theunknown operation resultbased on Basic Informationand Details.

Setting method:From the Operation Resultgroup box, select one or moreitems.



97


Time Range Description:To collect statistics by timerange. If the time range is not set,all logs generated at any time arequeried.

Setting method:Select From and To check boxon the left side, and then enter thedate and time directly in the text

box, or click and set the timein the Select Time dialog box.Example:Example: Set the time range to02/08/200900:00:00-02/09/2009 00:00:00.NOTE

To set the time format, chooseSystem > Preferences, expandRegion Settings, and then choosethe Time node. Set Time Format inthe area on the right.


Description:In the System Log Statisticswindow, you can set whether todisplay the Details column ofsystem logs.In Detail information contains,enter the information to bedisplayed in the Details column.The M2000 filters system logsbased on the informationprovided in Detail informationcontains.


7.13.6 Parameters for Querying Security LogsThis topic describes the parameters in the Query Security Logs window and the Filter dialogbox. When querying security logs or set the filter criteria for security logs, you can refer to thistopic to set the filter criteria.


Operation User Description:To query logs by user.


. In the Select OperationUser dialog box, select one ormore items.



98


Operation Terminal Description:To query logs by IP address of theterminal.


. In the Select OperationTerminal dialog box, select oneor more items.

Operation Result Description:To query logs by operation result.




l Partially successful meansthat the operation is completeand part of operation resultsare returned.


Risk Level Description:To query logs by risk level.

Value:Warning, Minor, and Risk.Setting method:In the Filter dialog box, selectone or more items from the RiskLevel group box.

Time Range Description:To query logs by time range. Ifthe time range is not set, all logsgenerated at any time are queried.


or click and set the time in theSelect Time dialog box.Example:Example: Set the time range to02/08/2009 00:00:00-02/09/200900:00:00.



99



Description:In the Query Security Logswindow, you can set whether todisplay the Details column ofsecurity logs.In Detail information contains,enter the information to bedisplayed in the Details column.The M2000 filters security logsbased on the informationprovided in Detail informationcontains.

Setting method:In the Filter dialog box, select theDetail information containscheck box, and then enter thefields to be contained in Detailsin the text box that is on the rightof the check box.

Security Event Description:To query logs by security event.


correspondingto Security Event. In the SelectSecurity Event dialog box, selectone or more items.

Operation Object Description:To query data by operationobject.


correspondingto Operation Object. In theSelect Operation Object dialogbox, select one or more items.

User Type Description:User type of the user thatperforms a security event,including system administratorand local user.

-

Operation Time Description:Time for executing a securityevent.

-

Details Description:Details about a security event.

-

7.13.7 Parameters for Collecting Statistics on Security LogsThis topic describes the parameters in the Filter dialog box. When collecting statistics on securitylogs, you can refer to this topic to set the statistical conditions.



100

Statistical items


Row Statistical Item Description:To set the row heading ofthe statistical result table.

Value:The parameter valuesinclude None, OperationUser, User Type,Security Event,Operation Terminal,Operation Result,Operation Object, andRisk Level.

Statistical Item Description:To set the row heading ofthe statistical result table.This parameter is the sub-item of the precedingparameter StatisticalItem.

Value:The parameter valuesinclude None, OperationUser, User Type,Security Event,Operation Terminal,Operation Result,Operation Object, andRisk Level.NOTE

You can set at most one ofboth Statistical Item inRow to None. Thestatistical results aregrouped by StatisticalItem.

Column Statistical Item Description:To set the column headingof the statistical resulttable.

Value:The parameter valuesinclude Count,Operation User, UserType, Security Event,Operation Terminal,Operation Result,Operation Object, andRisk Level.NOTE

If the value of Row is set toOperation User or UserType, the value ofColumn cannot be set toOperation User or UserType.

Example Description:To preview the style of thestatistical result table.

Value:-



101


Operation User Description:To collect statistics by user.

Setting method:

Click . In the SelectOperation User dialog box,select one or more items.

Operation Terminal Description:To collect statistics by IP addressof the terminal.

Setting method:

Click . In the SelectOperation Terminal dialog box,select one or more items.

Operation Result Description:To collect statistics by operationresult.




l Partially successful meansthe operation is complete, andsome operation results arereturned.

Setting method:In the Result area, select one ormore items.

Risk Level Description:To collect statistics by risk level.

Value:Warning, Minor, and Risk.Setting method:From the Risk Level group box,select one or more items.

Time Range Description:To collect statistics by timerange. If the time range is notspecified, all logs generated atany time are queried.

Setting method:Select From and To check box onthe left side, and then enter thedate and time directly in the text

box, or click and set the timein the Select Time dialog box.Example:Example: Set the time range to02/08/2009 00:00:00-02/09/200900:00:00.



102



Description:In the Security Log Statisticswindow, you can set whether todisplay the Details column ofsecurity logs.In Detail information contains,enter the information to bedisplayed in the Details column.The M2000 filters security logsbased on the informationprovided in Detail informationcontains.


Security Event Description:To collect statistics by securityevent.

Setting method:

Click corresponding to SecurityEvent. In the Select SecurityEvent dialog box, select one ormore items.

Operation Object Description:To collect statistics by operationobject.

Setting method:

Click corresponding to OperationObject. In the Select OperationObject dialog box, select one ormore items.

7.13.8 Parameters for Querying NE Operation LogsThis describes the parameters in the Filter Criteria dialog box when you query NE operationlogs.

Table 7-6 describes the parameters for querying NE operation logs.

Table 7-6 Parameters for querying NE operation logs

QueryCondition

Description Setting

User Query NE operation logs by user. Click , and then select one ormultiple items from the Select Userdialog box.

Terminal Query NE operation logs by terminal. Click , and then select one ormultiple items from the SelectTerminal dialog box.



103

QueryCondition

Description Setting

User Type Query NE operation logs by user type.The user type can be Local, EMS, orEMSOP.

Select one or multiple items from theUser Type area.

Result Query NE operation logs by operationresult.The result can be Succeeded orFailed.

Select one or multiple items from theResult area.

MML Query NE operation logs by MMLcommand.

Enter the MML command to befiltered out in the text box in theMML area.NOTE

The filtering of MML commandssupports the accurate search. You need toenter a part of an MML command, andthen the system queried the NE operationlogs containing the entered MMLcommand.

Time Range Query NE operation logs by timerange.From indicates the start time, andTo indicates the end time.

Select From and To, and enter thedate and time in the text box.Alternatively, click . In the Date/Time Selection dialog box, set thedate and the time.For example, set the time range to2002-02-09 00:00:00 2003-02-0900:00:00.

NE Name Query NE operation logs by NE. Click Select corresponding to NEName, and then select one or multipleitems from the Select NE dialog box.

7.13.9 Parameters for Statistics on NE Operation LogsThis section describes the statistical items in the Filter Criteria dialog box. You can refer tothis section when setting items for collecting statistics about NE operation logs.

Statistical ItemsName Description Settings

Statistic Row Description:To set the row heading of thestatistical result table.

Value:You must select one or two statisticalitems. The statistical results aresorted by statistical item.



104

Name Description Settings

StatisticalColumn

Description:To set the column heading of thestatistical result table.

Value:Statistical item under Statisticalcolumn must be set.

StatisticalItem

Description:To set the row heading and columnheading of the statistical result table.

Value:l User: Name of a user that

performs the operation.l Result: result of an operation,

including succeeded and failed.l NE: name of the NE on which an

operation is performed.l NE Type: type of the NE on

which an operation is performed.l Terminal: identified with an IP

address.l User Type: identifies the domain

attributes of a user in the NEoperation log, including EMS,Local, and EMSOP.

Example Description:To preview the style of the statisticalresult table.

Value:-

Filter conditionsFilterCondition

Description Settings

User To collect statistics by user. Click , and then select one or moreitems from the User Select dialogbox.

Terminal To collect statistics by terminal. Click , and then select one or moreitems from the Terminal Selectdialog box.

User Type To collect statistics by user type.User types include Local, EMS, andEMSOP.

Select one or more items from theUser Type area.

Result To collect statistics by result. Select one or more items from theResult area.



105

FilterCondition

Description Settings

MML To collect statistics by the keyword ofMML filtering conditions.

Enter the keyword (such as LST VER)of a filtering condition in the MMLarea.NOTE

The filtering of MML commandssupports the accurate search. You need toenter a part of an MML command, andthen the system queried the NE operationlogs containing the entered MMLcommand.

Time Range To collect statistics by time range.From indicates the start time, andTo indicates the end time.

Select From and To, and then enterthe date and time in the text box.Alternatively, click , and then setthe date and the time in the Date/TimeSelection dialog box.For example, set the time range to2002-02-09 00:00:00 2003-02-0900:00:00.

NE Name To collect statistics by NE. Click Choose corresponding to NEName. Select one or more items fromthe NE Name: Choose dialog box.

7.13.10 Parameters for Querying NE Security LogsThis section describes the parameters for querying NE security logs.

Table 7-7 describes the parameters for querying NE security logs.

Table 7-7 Parameters for querying NE security logs

QueryCriterion

Description Setting

User Queries NE security logs by user. Click and select one or more itemsin the User Select dialog box.

Terminal Queries NE security logs by terminal. Click and select one or more itemsin the Terminal Select dialog box.

User Type Queries NE security logs by user type.User types are Local, EMS, andEMSOP.

Select one or more items in the UserType area.



106

QueryCriterion

Description Setting

Result Queries NE security logs by operationresult.Operation results are Succeeded andFailed.

Select one or more items in theResult area.

SecurityLevels

Queries NE security logs by securityevent level.Security event levels are Urgent,Important, and Subordinate.

Select one or more items in theSecurity Levels area.

InformationFilter

Filters information based on theentered content in the Informationfield and displays NE security logsthat meet the criterion.

OptionalFor CBSCs, use either of thefollowing methods:l Type BTS ID to query all logs

containing BTS ID in CBSCsecurity logs.

l Type BTS ID=100 to querysecurity logs of BTS ID=100.

For other NEs, type the content set inthe Information field to filter logsthat meet the criterion.

Time Range Queries NE security logs by timerange.From indicates the start time and Toindicates the end time.

Select From and To, type the date andtime in the text boxes, or click andset time in the Date/Time Selectiondialog box.For example, set the time range to2002-02-09 00:00:00 2003-02-0900:00:00.

NEs Queries NE security logs by NE. Click Choose corresponding to NEand select one or more items in theNEs Select dialog box.

7.13.11 Parameters for Statistics on NE Security LogThis part describes the items set in the Filter Criteria dialog box. Refer to this part when youset items for collecting statistics on NE security logs.



107

Statistical ItemsName Description Settings

Statistic Row Description:To set the row heading of thestatistical result table.

Value:You must select one or twostatistical items. The statisticalresults are sorted by statisticalitem.

Statistic Column Description:To set the column heading of thestatistical result table.

Value:The Statistic Item parameterunder Statistic Column ismandatory.

Statistic Item Description:To set the row heading andcolumn heading of the statisticalresult table.

Value:l User: Name of a user that

performs the operation.l Result: result of an

operation, includingsucceeded and failed.

l NE: name of the NE onwhich an operation isperformed.

l NE Type: type of the NE onwhich an operation isperformed.

l Terminal: identified with anIP address.

l User Type: identifies thedomain attributes of a user inthe NE operation log,including EMS, Local, andEMSOP.

l Security Level: securitylevel of the logs, includingUrgent, Important, andSubordinate.

Example Description:Preview the style of thestatistical result table.

Value:-



108

Filter conditionsFilterCondition

Description Setting

User To collects statistics by user Click . Select one or more itemsfrom the User Select dialog box.

Terminal Collects statistics by terminal Click . Select one or more itemsfrom the Terminal Select dialog box.

User Types Queries by user typeThe user type falls into the Local, theEMS, and the EMSOP categories.

Select one or more items from theUser Types group box.

Result Collects statistics by operationresults.The results are either Succeeded orFailed.

Select one or more items from theResult group box.

SecurityLevels

Collects statistics by security levelThe security levels are Urgent,Important, and Subordinate.

Select one or more items from theSecurity Levels group box.

InformationFilter

Filters information based on theentered content in the Informationfield and displays NE security logsthat meet the criterion.

OptionalFor CBSCs, use either of thefollowing methods:l Type BTS ID to query all logs

containing BTS ID in CBSCsecurity logs.

l Type BTS ID=100 to querysecurity logs of BTS ID=100.

For other NEs, type the content set inthe Information field to filter logsthat meet the criterion.

Time Range Collecting statistics by time rangeFrom indicates the start time, whileTo indicates the end time.

Select From and To, and enter thedate and time in the text box.Alternatively, click . In the Date/Time Selection dialog box, set thedate and the time.For instance, set the time range to2002-02-09 00:00:00 2003-02-0900:00:00.



109

FilterCondition

Description Setting

NEs Collecting statistics by NE Click Choose at the lower part ofNEs. Select one or more items fromthe NEs Select dialog box.NOTE

The NEs Select dialog box displays theNEs that are in connection state on thetopology view and has data stored in thedatabase.

7.13.12 Parameters for Setting M2000 Log Timing ExportThis topic describes the parameters for setting M2000 log timing export in the centralized taskmanagement. When you set log timing export, you can refer to this topic to perform setting.

Parameters

Table 7-8 Common Parameters for Periodic Tasks


Task name Description:Refers to the name of a timing task.

Value:l A maximum of 64 bytes.l Unique and not null.l Case sensitive.

Executiontype

Description:l One-time: If you select this

option, the system runs thecreated task once at the definedtime point.

l Periodic: If you select thisoption, the system runs thecreated task periodically.

Value:l One-timel Periodic

Start time Description:This parameter sets the time forstarting a task.

Value:The start time should be later than thetime displayed on the server.

Task type Description:Refers to the type of a timing task.

-



110


Executioninterval

Description:Interval between periodic tasks. Ithas two enlistments: duration andunit.

Value:l The period can be represented in

either of the following units:minutes, hours, days, weeks,months. Second is not supported.The supported units of Period varyaccording to the task type.

l The value range for period shouldbe as follows: Minute (1 - 366 x 24x 60), Hour (1 - 366 x 24), Day (1- 366), Week (1 - 52), Month (1 -12).

NOTEThe execution interval cannot beconfigured again after a dump task iscreated.

Executiontimes

Description:This parameter indicates the timesthat a periodic task is executed.NOTE

This parameter is displayed in theAttribute dialog box only after youset it when creating and copying aperiodic task.

Value:0 - 65535.NOTE

0 indicates that the number of times forexecuting periodic tasks is not restricted.

End time Description:End time of a periodic task.NOTE


Value:Later than Start time, and earlier than01/18/2038 11:14:07.

Table 7-9 Extended Parameters

Parameter Description Setting

Compressfile afterexport

Description:This parameter is used to set whether compressexport files. If yes, export files will be compressedto a .zip file. After compression, the source files aredeleted.

Value:Value range: Yes or NoDefault value: Yes

Export FileType

Description:This parameters indicates the format of the exportfiles of logs.

Value:Value range: CSV,XML, TXT or HTML.



111


File path Description:Path for storing log files on the M2000 server.

Value:Value: a specified pathRule: It is notrecommended tochange the default filepath. If you need tospecify a new file path,ensure that the userossuser has permissionto read and write thetarget folder under thispath.

Export FileManagement

Description:Hold files for XX days: If the retention period ofthe export file exported to a specified folderexceeds this period, the file is deleted.

Value:Value range: 1-180Default value: 15

Description:Hold max. XX files: If the number of export filesexported to the specified folder is greater than thisvalue, the M2000 deletes the oldest export filesuntil the number of files in this folder becomes lessthan the value of this parameter.


Description:Hold max. XX MB file data: If the total size of theexport files in the specified folder is greater thanthis value, the M2000 deletes the oldest export filesuntil the number of files in this folder becomes lessthan the value of this parameter.


7.13.13 Parameters for Setting M2000 Log Timing DumpThis topic describes the parameters for setting M2000 log timing dump in the centralized taskmanagement. When you set log timing dump, you can refer to this topic to perform setting.



112

Parameters

Table 7-10 Common Parameters for Periodic Tasks


Task name Description:Refers to the name of a timing task.

Value:l A maximum of 64 bytes.l Unique and not null.l Case sensitive.

Executiontype

Description:l One-time: If you select this

option, the system runs thecreated task once at the definedtime point.

l Periodic: If you select thisoption, the system runs thecreated task periodically.

Value:l One-timel Periodic

Start time Description:This parameter sets the time forstarting a task.

Value:The start time should be later than thetime displayed on the server.

Task type Description:Refers to the type of a timing task.

-

Executioninterval

Description:Interval between periodic tasks. Ithas two enlistments: duration andunit.

Value:l The period can be represented in

either of the following units:minutes, hours, days, weeks,months. Second is not supported.The supported units of Period varyaccording to the task type.

l The value range for period shouldbe as follows: Minute (1 - 366 x 24x 60), Hour (1 - 366 x 24), Day (1- 366), Week (1 - 52), Month (1 -12).

NOTEThe execution interval cannot beconfigured again after a dump task iscreated.

Executiontimes

Description:This parameter indicates the timesthat a periodic task is executed.NOTE


Value:0 - 65535.NOTE

0 indicates that the number of times forexecuting periodic tasks is not restricted.



113


End time Description:End time of a periodic task.NOTE


Value:Later than Start time, and earlier than01/18/2038 11:14:07.

Table 7-11 Extended Parameters


Compressfile afterexport

Description:This parameter is used to set whether compress filesafter dumping. If yes, export files will becompressed to a .zip file. After compression, thesource files are deleted.

Value:Value range: Yes or NoDefault value: Yes

File type Description:This parameters indicates the format of the dumpfiles of logs.

Value:Value range: CSV,XML, TXT or HTML.

File path Description:File path indicates the path of the dump file. Thedump file is stored on the M2000 server.

Value:You can select thefolder for saving thedumped files in Filepath.The default file path onthe M2000 server is /opt/oss/server/var/ThresholdExport/Log.Rule: It is notrecommended tochange the default filepath. If you need tospecify a new file path,ensure that the userossuser has permissionto read and write thetarget folder under thispath.

Storageperiod indatabase(days)

Description:When a dump task is executed, the logs older thanthis period are dumped.




114


Dump FileManagement

Description:Hold files for XX days: If the retention period ofthe dump file in a specified folder exceeds thisperiod, the file is deleted.


Description:Hold max. XX files: If the number of dump filesin the specified folder is greater than this value, theM2000 deletes the oldest dump files until thenumber of files in this folder becomes less than thevalue of this parameter.


Description:Hold max. XX MB file data: If the total size of thedump files in the specified folder is greater than thisvalue, the M2000 deletes the oldest dump files untilthe number of files in this folder becomes less thanthe value of this parameter.


7.13.14 Parameters for the Export of NE LogsThis section describes the parameters for exporting NE logs and can be taken as reference duringthe parameter modification.

Table 7-12 lists the extended parameters.

Table 7-12 Descriptions of extended parameters

Parameter Value Range Description

File Format You can select .txt or .csv. Exports the operation logs to a .txtfile or .csv file.

File Path Default value: No change.The default path is: /opt/oss/server/var/fileint/nelogs/.

Saves NE logs.



115

Parameter Value Range Description

File Size Unit: MBDefault value: 1024

Refers to the threshold of thespace for dumping log files.During the export of log files, ifthe size of the files existing in thespecified path exceeds the presetthreshold, the earliest files arereplaced.NOTE

When setting the threshold of dumpspace, the size of the partition that thepath for saving log files belongs tomust be taken into account. Thethreshold cannot exceed the size ofthe partition.

File Hold Days Unit: dayDefault value: 3

Refers to the number of the dayswithin which the dump files can besaved. After these days, the filesare automatically deleted.

File Sum Number of filesDefault value: 1000

Refers to the maximum number offiles in the dump space. During theexport of log files, if the numberof the files existing in the specifiedpath exceeds the preset threshold,the earliest files are replaced.

7.13.15 Parameters for Querying NE Syslog Run LogsThis topic describes the parameters in the NE Syslog Run Log window and the FitterCriteria dialog box. You must set these parameters to query NE syslog run logs and set filtercriteria for NE syslog run log query.

Button DescriptionButton Description

Condition Displays the Fitter Criteria dialog box for setting filter criteria.

Query Queries required NE syslog run logs.

Refresh Synchronizes the latest log data on the server to the client.



116

Parameters for Setting Filter CriteriaParameter Description Setting

NE Name Description:Name of an NE whose syslog runlogs are to be queried.

Setting method:Select NE Name and enter an NEname in the text box.NOTE

Wildcard characters are supported.The asterisk (*) indicates a characterstring, and the question mark (?)indicates a single character except thesingle quotation mark ('), percent (%),and caret (^).

IP Address Description:IP address of an NE whose syslogrun logs are to be queried.

Setting method:Select IP Address and enter an IPaddress in the text box.NOTE

Wildcard characters are supported.The asterisk (*) indicates a characterstring.

Digest Description:Log digest to be queried.

Setting method:Select Digest and enter a log digestin the text box.NOTE


Details Description:Log details to be queried.

Setting method:Select Details and enter log detailsin the text box.NOTE


Module Name Description:Name of a module whose NEsyslog run logs are to be queried.

Setting method:Select Module Name and select amodule name from the drop-downlist box.



117


Level Description:Level of logs to be queried.

Value:Comparison operators for loglevels are listed as follows:l =l >l >=l <l <=Log levels are listed in descendingorder as follows:l Emergencyl Alertl Criticall Errorl Warningl Noticel Informationall DebugSetting method:Select Level, select a comparisonoperator from the first drop-downlist box, and select a log level fromthe second drop-down list box.

Sending Time Description:Time segment in which NE syslogrun logs are reported. If the timesegment is not set, all logsgenerated at any time are queried.

Setting method:l Select From or To and enter a

time in the text box.l Select From or To, move the

pointer in the text box, andclick or to adjust thevalue of the pointer position.

l Select From or To, click ,and set a time in the SelectTime dialog box.



118

8 Managing the M2000 Processes and Services

About This Chapter

This section describes how to manage the M2000 processes so that the processes and serviceson the M2000 server can function properly. The enterprise wireless network solution does notsupport northbound functions and therefore there is no northbound process.

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

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

8.3 Starting the M2000 Services (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.

8.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&x3650, SUSE10) 8 Managing the M2000 Processes and Services


119

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

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

8.1.2 ActiveMQ ProcessThis section describes the services and functions provided by the ActiveMQ process.

The ActiveMQ process provides the ActiveMQ service.

The ActiveMQ service provides the northbound interface that supports Java Messaging Service(JMS) notifications.

Dependent service: none

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

You can disable the service when it is not required.

Required services: none

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


8.1.5 antenna_agent ProcessThis section describes the services and functions provided by the antenna_agent process.



120

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.

Required service: EAMService.

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

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

Required services: TopoAdapterService

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

When the M2000 is running, ensure that this service functions properly.

Required services: TopoAdapterService.

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

You can disable the service when it is not required.

Required service: TopoAdapterService.

8.1.10 cmexp_agent ProcessThis section describes the service and functions provided by the cmexp_agent process.



121

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

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.

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


Required services: TopoAdapterService

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

8.1.13 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:

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 topology



122

l Setting pool parametersl Checking the NE data in a pooll Checking the MSC Server or MSCe of a specific user


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


8.1.15 DrlDm ProcessThis section describes the services and functions provided by the DrlDm process.

The DrlDm process provides the DrlDm service.

The DrlDm service provides the NE running log components.


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

The dsXXXX_agent process provides the DesktopServiceXXXX service.

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.

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.

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



123

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.

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

The fars_agent process provides the FarsService.

The FarsService provides the function of tracing data collection, data analysis, and datacollection management.

To enable the tracing function, you need to ensure that the FarsService is running normallyduring the operation of the M2000.

Dependent service: none.

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

During the operation of the M2000, ensure that this service is running properly.

Independent service: trapdispatcher.

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

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

The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service.



124

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


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


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

Required services: None.

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

You can stop this process if the QChat cluster communication is not required.


8.1.25 ifms_agent ProcessThis section describes the service and functions provided by the ifms_agent process.

The ifms_agent process provides the FaultService.



125

The FaultService collects alarm data from NEs and saves the data, thus providing the functionsof querying, dumping, and analyzing the fault data.

You can disable the service when fault management is not required.


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


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

KernelCMIRPKernelCMIRP provides an interface for public configuration management.



126

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.

BasicCMIRP

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

AlarmIRP

AlarmIRP 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 Services

The required service is the LicenseService.

8.1.28 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

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


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

The log_agent process provides LogService and ForwardingService.



127

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.

Required services: None.

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


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



8.1.33 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,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.


Dependent services: none



128

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

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

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

The nelicense_agent process provides the NeLicenseService service.

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

Required services: LogService.

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




129

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


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

The ngnni112_agent process provides the NGNNI112Service service.

The NGNNI112Service provides the NBI for the subscriber line test system.

Required services: NGNTestManageService.

8.1.40 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 northbound interface operationmanagement.


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


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

8.1.43 nicservice_agent ProcessThis section describes the services and functions provided by the nicservice_agent process.

The nicservice_agent process provides the NICService service.



130

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.

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

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.


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

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



8.1.47 pm_agent ProcessThis section describes the services and functions provided by the process pm_agent.

The pm_agent process provides the PMService service.



131

PMService monitors performance management on all NEs. The performance management isindependent of NEs or objects. Stop PMService if the performance management function is notrequired.


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

The pmengine0X01_agent process provides the PMEngine0X01 service.

The pmengine0X01_agent process 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 performance results, diagnosing missing results,and importing neighboring cell data in the ATAE cluster system system.

In the ATAE cluster system system, you can deploy this process on the master node and differentslave nodes. The typical process names are pmengine0101_agent, pmengine0201_agent,pmengine0301_agent, and so on.


Required services: PMService

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


8.1.50 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

8.1.51 porttrunk_agent ProcessThis section describes the services and functions provided by the porttrunk_agent process.

The porttrunk_agent process provides the PortTrunkingService service.

The PortTrunkingService provides the network proxy function.



132

Through the network proxy function, some tools that cannot connect to NEs can access NEs.You do not need to configure multiple ports on the firewall for communication.

Configure the ACL for the PortTrunkingService service to restrict the NEs that can be accessed.


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


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


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

Keep the service running during the operation of the PRS module.


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

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.



133

Keep the service running during the operation of the PRS module.

Required service: LicenseService.

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

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


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


8.1.59 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

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



134


Required services: ItmService and SecurityService.

8.1.61 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

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

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

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.

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


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



135



8.1.66 SyslogCollectorDM ProcessThis section describes the services and functions provided by the SyslogCollectorDM process.

The SyslogCollectorDM process provides the SyslogCollectorDM service.

The SyslogCollectorDM service provides data collection and file management functions for NErunning logs.


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

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.

8.1.68 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

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




136

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

When the M2000 is running, ensure that the xftpXX01_agent process works properly.


8.1.71 xmlagent ProcessThis section describes the services and functions provided by the xmlagent process.

The xmlagent process provides the XMLAgent service.

The XMLAgent service provides the northbound interface that is based on the Simple ObjectAccess Protocol (SOAP).


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

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

Table 8-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.



137

ServiceName

ProcessName

Platform Description

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.

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

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



138

Table 8-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

8.1.74 Processes Used by RTN, Router, Switch, Firewall, and SVNThis section describes the processes used by NEs such as radio transmission node (RTN), router,switch, firewall, and SSL VPN (SVN).

Table 8-3 lists these processes used by NEs such as RTN, router, switch, firewall, and SVN.The processes listed in Table 8-3 are available only after the related NE components are installed.

Table 8-3 Processes used by RTN, router, switch, firewall, and SVN

Process Name Dependentprocesses Description

dam None This process provides the function of creatingSNMP equipment.



139


datacollectorsvr NoneThis process is mainly used for collecting thecomplete and correct fault data in case of NEfailure and helps to locate faults quickly

DCServer None

This process provides the function of NEsoftware management and disaster recoverymanagement. The detailed functions are NEsoftware upgrade, patch installation, databackup and recovery for disaster recovery, andplug-andplay automatic upgrade of case-shapedequipment.

Eml_PerfSvr None This process provides the transfer-domainperformance management function.

Eml_PubSvr NoneThis process provides the function of inter-NEmanagement on transferdomain NEs andreports.

InventoryDM eam_agent andifms_agent

This process provides the inventory datamanagement function, such as physical resourcemanagement, cable management, and customermanagement.

mc None This process provides the basic NE distributionservice.

nemgr_ptn NoneThis process provides the function of managingMetro Ethernet PTN frame-shaped andcaseshaped NEs.

nemgr_rtn None This process provides the function of managingRTN series equipment.

neproxy None Data Collector NE Proxy Process.

PMDataSynchronizer None This process provides the function of importing

data in text files.

PMSDm None This process provides the collector managementfunction.

PQMDm None This process provides the function of groupingperformance monitoring and display.

RouterMgrDm None This process provides the function of managingQuidway routers.

SecurityMgrDm NoneThis process provides the function of managingFW/USG, SIG, and SVN series securityequipment.

toolkit None This process provides the service of upgradingboardlevel transmission equipment.



140


TXTNBIDm NoneThis process provides the NBI function. It isused to transmit performance data in the textformat through FTP.

UFlight_Dis-patcher Apache Dispatcher the web request of UFlight.

UniteUitlDM None

This process provides the basic functions, suchas importing and exporting scripts, managingNE time, synchronizing NEs, and managing NEobjects, of the inter-domain universal NMS.

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

Procedure

Step 1 Log in to the M2000 server as user ossuser.

If the current user is not user ossuser, you can run the following command to switch to userossuser:

~> su - ossuser

Step 2 Run the following commands:

~> cd /opt/oss/server

~> . ./svc_profile.sh

~> svc_adm -cmd status

Host: 10.141.147.234

Service Agent: 3rdTool_agent [1 service(s)] pid: 8773 3rdToolService [running ]

Service Agent: DrlDm [1 service(s)] pid: 8725 DrlDm [running ]

Service Agent: ScriptModuleService_agent [1 service(s)] pid: 11173 ScriptModuleService [running ]

...

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

Normally, the following information is displayed at the end of the system output:

[Running : 51 ] [Not Running : 0 ]l If the value of Not Running : is 0, all the M2000 services are running.

l If the value of Running : is 0, all the M2000 services are stopped.



141

NOTE

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

Step 3 (Optional) If the user was switched to user ossuser in the first step, run the following commandto exit user ossuser:

~> exit

----End

8.3 Starting the M2000 Services (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.

Procedure

Step 1 log in to the server as user ossuser.


~> su - ossuser

Step 2 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, startingservices takes 15 to 20 minutes.


~> exit

----End

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



142

Procedure

Step 1 log in to the server as user ossuser.


~> su - ossuser

Step 2 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 2 minutes.

Step 3 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 4 If some services are still running, run the following command to forcibly stop them:

~> kill_svc

Step 5 Run the following command to stop the M2000 daemon:

~> stop_daem

Step 6 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 7 If the daemon process is still running, run the following command to forcibly stop it:

~> kill_daem


~> exit

----End



143

9 Managing M2000 Database

About This Chapter

This section describes how to manage the M2000 database. This first describes the concepts ofthe M2000 database including database type and status. Then describes how to view the databasestatus, start or stop the database, and check the database space.

9.1 Introduction to the M2000 Database (Oracle)The M2000 databases consist of the Oracle system database and the M2000 server database.This chapter describes only the M2000 server database. On the basis of the Oracle database, theM2000 creates the OSSDB database. After installing the M2000 server application software,the size of the M2000 database is fixed. You can use the oracle commands to perform operationsfor the database.

9.2 Checking Oracle ServicesThis section describes how to check the status of the database services before installing theM2000 to ensure that the database services are running properly.

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

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

9.5 Checking Database SpaceThis section describes how to use Oracle commands to view the database status, overall size ofdata files, and size of remaining space. This operation requires few system resources and doesnot affect system operation.

M2000Administrator Guide (x3850&x3650, SUSE10) 9 Managing M2000 Database


144

9.1 Introduction to the M2000 Database (Oracle)The M2000 databases consist of the Oracle system database and the M2000 server database.This chapter describes only the M2000 server database. On the basis of the Oracle database, theM2000 creates the OSSDB database. After installing the M2000 server application software,the size of the M2000 database is fixed. You can use the oracle commands to perform operationsfor the database.

9.1.1 cmedbThe cmedb is used to store the NE configuration data on the CME, including the configurationdata in the current and planned data areas.

The cmedb requires at least 8 GB data space.

Table 9-1 lists the names and functions of the tables in the cmedb.

Table 9-1 Names and functions of tables in the cmedb database

Table Name Function

Table with the t_c_ prefix Stores NE data in the current data area.

Table with the t_p_ prefix Stores NE data in the planned data area.

Table with the t_ prefix Supports table of the tool type to store NE data.

Other tables Records internal data on the CME.

9.1.2 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 at least 2 GB disk space.

Table 9-2 lists the name and function of each table in the eamdb.

Table 9-2 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.



145

Table Name Function

tbl_sntype Subnet type table.

tbl_netype NE type table.

tbl_linktype Link type table.

tbl_sync Data synchronization table.

tbl_nerelation NE relationship 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 relationship 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 partition information table recording the node information.

tbl_SubareaRes partition resource table recording the resource information ofeach node.

Other tables Record the internal processing data.

9.1.3 farsdbThe farsdb is used to store the signaling message data of all the NEs managed by the M2000.

The farsdb requires at least 12 GB space.

The farsdb consists of the following types of tables:

l Static configuration data table

l Task table

l Task data table

Table 9-3 lists the name and function of each table in the farsdb.



146

Table 9-3 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.

Message type name_taskID

Dynamically created task data table, which records the signalingdata of the message type corresponding to a task.

9.1.4 fmdbThe fmdb is used to store the alarm logs and event logs of the M2000 and NEs.

The fmdb requires at least 8 GB disk space.

Table 9-4 lists the names and functions of tables in the fmdb.

Table 9-4 Tables of the fmdb database and their functions

Table Name Function

tbl_alm_log Records alarm logs.

tbl_event_log Records event logs.

Other tables Record related information about the alarmprocessing internal implementation.

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.

9.1.5 itfndbThe itfndb is used to store the northbound configuration data, performance tasks, andperformance threshold data.

The itfndb is optional to create the M2000 database. It requires at least 3 GB disk space. Table9-5 lists the name and function of each table in the itfndb.

Table 9-5 Names and functions of tables in the itfndb database

Table Name Function

tbl_JGeneralInfo Records the general information about tasks.



147

Table Name Function

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_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 northbound internalimplementation.

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

The logdb requires at least 3 GB disk space.

Table 9-6 lists the names and functions of the tables in the logdb.

Table 9-6 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.

9.1.7 omcdbThe omcdb is used to store the M2000configuration data and related data for internalimplementation.

The omcdb requires at least 75 GB disk space.



148

Table 9-7 describes the name and function of each table in the omcdb.

Table 9-7 Names and functions of tables in the omcdb database

Table Name Function

Tables with moi_ as theprefix

Records the information about MO instances.

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.

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

Tables with rel_ as theprefix

Records the relationship 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.



149

Table Name Function

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.

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.

Other tables Records other configuration data of the M2000.

9.1.8 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 at least 2 GB disk space.

Table 9-8 lists the name and function of each table in the osstempdb.

Table 9-8 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.



150

9.1.9 pmcomdbThe pmcomdb is used for storing the static performance measurement data of NEs. Thepmcomdb database must exist in the M2000 system.

The pmcomdb requires at least 5 GB disk space.

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 tablesl Template Information Tablesl Function Subsets and Period Tablesl Other tables

Counter tablesThe counter tables contain multiple tables to save stable information. Table 9-9 lists the nameand function of each table in the pmcomdb.

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

Table Name Function

systbl_NeType Records all possible NE types that can bemanaged by theM2000.

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.

Template Information TablesTemplate tables contain several tables that record measurement-related information. Table9-10 lists the name and function of each table.

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

Table Name Function

tbl_ObjectInstance Records measurement objects.



151

Table Name Function

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

Table 9-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.

Other Tables

Table 9-12 Other tables in the pmcomdb and their functions

Table Name Function

tbl_UscdbFePmPlugino Records the related information of FE PMPlug-in (such as FE type names, FE interfaceIDs, the status of FE installation anduninstallation).



152

9.1.10 pmdbThe pmdb is used to store the NE performance architecture table or NE performancemeasurement data. The pmdb database must exist in the M2000 system.

The pmdb requires at least 150 GB disk space.

After the storage period of the performance measurement data expires, the system deletes theearliest data on a daily basis.

If the pmdb database is already insufficient before the preset storage period, you must reset thestorage period. Otherwise, the pmdb database cannot process any performance data. Change thestorage period before the remaining space of the pmdb is insufficient.

To calculate the storage period, perform the following steps: After the M2000 runs for half amonth, observe the used space of the pmdb and calculate the pmdb space used every day. Thencalculate the number of days that the whole pmdb database can last for, which is also the storageperiod to be set.

The pmdb consists of the following types of tables:

l Template Tablesl Function Subsets and Period Tables

Template Information TablesTemplate tables record measurement-related information. Table 9-13 lists the name and functionof the table.

Table 9-13 Template information 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 9-14 lists the name and function of the table.

Table 9-14 Function subset tables and period tables in the pmdb and the corresponding functions

Table Name Function

tbl_Result_XXX_Y XXX is the ID of the function subset and Y is theperiod index ranging between 0 and 4.

9.1.11 smdbThe smdb is used to store security management data. The smdb database must exist in theM2000 system.



153

The smdb requires at least 2 GB disk space. Table 9-15 lists the names and functions of tablesin the smdb.

Table 9-15 Names and functions of tables in the smdb database

Table Name Function

tbl_AccessViewNodeRelTable Records the relationship between the privilegedisplay nodes.

tbl_AccessViewNodeTable Records the privilege display nodes.

tbl_IDTable Records the reclaimed IDs.

tbl_SMAccessPolicyItem Records the privilege strategies for binding usergroups.

tbl_SMGroup Records the basic information about user groups.

tbl_SMGroupUserMap Records the binding relationship 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 relationship between privategroups and users.

tbl_SMSecurityPolicy Records the security policy.

tbl_SMUser Records the basic information about users.

tbl_SMUserHistoryRec Records history user passwords.

tbl_SMUserNEUserMap Records the binding relationship between usersand NE users.

tbl_SecurityObjectTable Records security objects.

tbl_SessionTable Records session information.

tbl_StaticTypeRelationTable Records the dependency between privileges.

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

tbl_StaticTypeViewTable Records the display information about staticsecurity information.

Other tables Records the information about internalimplementation.

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



154

A disk of more than 12 GB is required for storage. Table 9-16 lists the names and functions oftables in the swmdb.

Table 9-16 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 relationship.

tbl_NELogTable Records the NE operation logs.

Other tables Records the relationship information about internalimplementation.

9.1.13 topodbThe topodb is used to store topology management data. The topodb database must exist in theM2000 system.

The topodb requires at least 2 GB disk space.

Table 9-17 lists the names and functions of the tables in the topodb.

Table 9-17 Tables of the topodb database and their functions

Table Name Function

TSLink Records the information on topology links.

TSNode Records the information on topology NEs.

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.

9.2 Checking Oracle ServicesThis section describes how to check the status of the database services before installing theM2000 to ensure that the database services are running properly.

PrerequisitesYou have logged in to the server as user root in SSH mode.



155

.

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.binoracle 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_ossdb



156

oracle 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_ossdboracle 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

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



157

ProcedureStep 1 Log in to the server as user root in SSH mode.

Step 2 Run the following command to switch to user oracle:

$ su - oracle

Step 3 Start the Oracle services.

1. Run the following command to start the ASM instance.> ORACLE_SID=+ASM> sqlplus / as SYSDBASQL> 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> startup

NOTE

There must be a space between the two points . . in the . ./.bash_profile.

If 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 4 Run the following commands to start the monitor:

> lsnrctl start


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

Step 5 Run the following command to exit from user oracle:

> exit

----End



158

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

Prerequisitesl M2000 services have been stopped. For details, see 8.4 Stopping the M2000 Services

(SUSE).

ProcedureStep 1 Log in to the server as user root in SSH mode.

Step 2 Run the following command to switch to user oracle:

$ su - oracle

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

> lsnrctl status

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 4 Stop Oracle services:

1. Run the following command to stop the ORACLE instance.> sqlplus / as SYSDBASQL> shutdown immediateIf 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



159

> sqlplus / as SYSDBASQL> shutdown immediateIf 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 shutdownSQL> exit

Step 5 Run the following command to exit from user oracle:

> exit

----End

9.5 Checking Database SpaceThis section describes how to use Oracle commands to view the database status, overall size ofdata files, and size of remaining space. This operation requires few system resources and doesnot affect system operation.

PrerequisitesThe database services are running properly.

Procedure

Step 1 Log in to the server as user oracle in SSH mode.

If the current user is not user oracle, you can run the following command to switch to useroracle:

> su - oracle

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

> sqlplus / as SYSDBA

SQL> select tablespace_name, sum(bytes)/1024/1024 Total_Size_M from dba_data_filesgroup by tablespace_name;TABLESPACE_NAME TOTAL_SIZE_M------------------------------------------------------------ ------------LOGDB_TBS 3072OSSTEMPDB_TBS 2048PMCOMDB_TBS 5120CMEDB_TBS 8192SYSAUX 3072UNDOTBS1 20480EAMDB_TBS 2048FARSDB_TBS 12288SWMDB_TBS 12288OMCDB_TBS 76800SYSTEM 3072

TABLESPACE_NAME TOTAL_SIZE_M------------------------------------------------------------ ------------ITFNDB_TBS 3072PMDB_TBS 153600FMDB_TBS 8192



160

SMDB_TBS 2048TOPODB_TBS 2048

16 rows selected.

Step 3 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 3071OSSTEMPDB_TBS 2047PMCOMDB_TBS 5119CMEDB_TBS 8191SYSAUX 2865.875UNDOTBS1 20190.125EAMDB_TBS 2047FARSDB_TBS 12287SWMDB_TBS 12287OMCDB_TBS 76799SYSTEM 2749.8125

TABLESPACE_NAME FREE_SIZE_M------------------------------------------------------------ -----------ITFNDB_TBS 3071PMDB_TBS 153599FMDB_TBS 8191SMDB_TBS 2047TOPODB_TBS 2047

16 rows selected.

SQL> exit

Step 4 (Optional) If the user was switched to user oracle in the first step, run the following commandto exit user oracle:

> exit

----End



161

10 Managing Disks and Hardware

About This Chapter

This section describes how to manage the disks and hardware on the M2000 server.

10.1 Viewing the CPU and Memory Usage of the M2000 ServerThis 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.

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

10.3 Clearing the Disk Space of the M2000 Server (SUSE)This section describes how to clear the disk space of the M2000 server. Before clearing the diskspace, ensure that the files to be deleted are not required for future operations. Deleting files bymistake may lead to system operation errors.

10.4 Viewing Hardware Status on the IMMThis section describes how to view hardware status on the IMM.

M2000Administrator Guide (x3850&x3650, SUSE10) 10 Managing Disks and Hardware


162

10.1 Viewing the CPU and Memory Usage of the M2000Server

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 10-1.

Figure 10-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



163

10.2 Viewing the Disk Usage of the M2000 Server byRunning SUSE Commands

This describes how to view the disk usage of the M2000 server by running the SUSE commands.This operation requires few system resources and does not affect the system operation.

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

10.3 Clearing the Disk Space of the M2000 Server (SUSE)This section describes how to clear the disk space of the M2000 server. Before clearing the diskspace, ensure that the files to be deleted are not required for future operations. Deleting files bymistake may lead to system operation errors.

ContextDuring routine operation and maintenance, back up and delete the following files to free up diskspace:

l Files storing information about NEs and the M2000 server

l Software package and decompressed files

l Trace logs

l Backup files

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.



164

Procedure

Step 1 Export the files that store information about NEs and the M2000 server and back up the files toa hard disk.l Files generated during automatic alarm dump

These files are stored in /opt/oss/server/var/ThresholdExport/FM.l User logs

These files are stored in /opt/oss/server/var/userlogs.l Core files generated by the system

These files are stored in /opt/oss/server/var/logs/.l Historical trace files

These files are stored in /opt/oss/server/var/logs/tracebak/.

Step 2 Delete the software package and decompressed files.

After the software is successfully upgraded, you can delete the software package anddecompressed files. The upgrade package and decompressed files are stored in the folder namedafter the upgrade patch in /export/home.

CAUTIONGenerally, the folder is created in /export/home. Sometimes, the folder is created in /export/home/bak.

Step 3 Delete trace logs.

Modify the value of tracebackupnum in the tracemonitor_svc_ex.xml file to reduce thenumber of backup trace files.

The tracemonitor_svc_ex.xml file in /opt/oss/server/etc/conf/ specifies the trace logmonitoring period, file length, and number of backup trace 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 period for monitoring trace logs. In the preceding example,the system checks the trace logs every 300 seconds. In tracebackupnum, you can set the numberof backup trace files for each process in /opt/oss/server/var/logs/tracebak. For a process, if thenumber of backup trace files in the tracebak directory exceeds the preset value, the systemautomatically deletes the earliest trace files.

Step 4 Clear the backup files.l Delete the backup files for an upgrade after the upgrade completes successfully.l Periodically delete unnecessary files from the /export/home/backup/omc database backup

directory.



165

NOTEFor details about the commands, see M2000 Command Reference.

----End

10.4 Viewing Hardware Status on the IMMThis section describes how to view hardware status on the IMM.

Prerequisitesl The server is powered on and the operating system has been started.l The communication between the PC and the IMM is normal.

Procedure

Step 1 Open Internet Explorer, type http://IMM IP address, and press Enter. The IMM login page isdisplayed. If the web browser displays certificate error or untrusted website, install certificatesfor the web browser by referring to 13.3 How Do I Handle the Problem of Certificate Erroror Untrusted Website Displayed in the Web Browser (IMM)?.

Step 2 Enter the initial user name USERID, the actual password, and click Login. The page for settingthe inactive session timeout value is displayed.

Step 3 Click Continue. The IMM home page is displayed.

Step 4 In the navigation tree, choose System > Monitors > System Status.

Step 5 View the System Health Summary column in the right pane.

During operating system running, if the status shown in Figure 10-2 is displayed, the hardwareis in the normal state. Otherwise, contact Huawei technical support.

Figure 10-2 System Health Summary

Step 6 In the navigation tree, choose System > Monitors > Virtual Light Path.

Step 7 View the Virtual Light Path column in the right pane and check whether alarms occur on thelight path diagnostics panel of the server.



166

For the 3850 server, if the status of parts Heartbeat and Power in Table 10-1 is displayed, andcolumns Color and Status of other parts are displayed as Not Applicable and Off, the status ofLED indicators for each part of the server is normal. Otherwise, the status of a part is abnormal.Contact Huawei technical support.

Table 10-1 Status of certain parts (x3850)

Name Color Status

Power Green On

Heartbeat Green Blink

For the 3650 server, if the status of parts BMC Heartbeat and Power in Table 10-2 is displayed,and columns Color and Status of other parts are displayed as Not Applicable and Off, the statusof LED indicators for each part of the server is normal. Otherwise, the status of a part is abnormal.Contact Huawei technical support.

Table 10-2 Status of certain parts (x3650)

Name Color Status

BMC Heartbeat Green Blink

Power Green On

----End



167

11 Managing License

About This Chapter

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

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

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

M2000Administrator Guide (x3850&x3650, SUSE10) 11 Managing License


168

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

Contextl When the period between the current day and Overflow Time of the License is less than

or equal to 30 days, the system displays a dialog box after a user logs in, prompting theuser to update the License. In addition, the system reminds the user of a License updateevery 12 hours.

l If a user does not apply a new License after the License expires, the M2000 sends theALM-297 The OSS License Expired indicating that the License has expired. In addition,the client periodically displays an expiration notification dialog box. Table 11-1 describesthe frequency of displaying the expiration notification dialog box on the client.

Table 11-1 Frequency of displaying the License expiration notification dialog box

Duration After Expiration Frequency of Display

Less than or equal to 30 days Once every 6 minutes

More than 30 days and less than or equal to 60days

Once every 3 minutes

More than 60 days Once every 1.5 minutes

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

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

Procedure

Step 1 Choose License > OSS License Management > License Information.



169

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



170

12 Backing Up and Restoring the M2000System (SUSE)

About This Chapter

This section describes how to back up and restore the M2000 system.

12.1 Introduction to the M2000 Backup and Restore Solution (SUSE)M2000 system data backup is the process of storing data on the M2000 server to a storagemedium when the M2000 system is running properly. M2000 system data restoration is theprocess of rolling back the M2000 system to a normal historical running state using backup datawhen the M2000 system cannot run properly due to data damage.

12.2 Backing Up and Restoring the M2000 Dynamic Data (SUSE)This section describes how to back up and restore M2000 dynamic data.

M2000Administrator Guide (x3850&x3650, SUSE10) 12 Backing Up and Restoring the M2000 System (SUSE)


171

12.1 Introduction to the M2000 Backup and Restore Solution(SUSE)

M2000 system data backup is the process of storing data on the M2000 server to a storagemedium when the M2000 system is running properly. M2000 system data restoration is theprocess of rolling back the M2000 system to a normal historical running state using backup datawhen the M2000 system cannot run properly due to data damage.

IBM PC servers support only dynamic data backup. Dynamic data refers to the data aboutM2000 dynamic services.

Dynamic Data Backup

Table 12-1 describes the backup contents, backup modes, and storage media in dynamic databackup.

Table 12-1 Introduction to dynamic data backup

Item Content

Backupcontents

l Database OSSDBl The M2000 system files:

– Files in the /export/home/omc/var and /export/home/sysmdirectories.

– Files in the /opt/oss, opt/OSSENGR, and opt/OSSJRE directories.– Files in the /opt/oracle/oradb/home/dbs/orapwossdb directory.

Backupmode

Periodicbackup

Performs a full backup at a specified time every 7 days. Afterperiodic backup is activated, the dynamic data is backed uponce every day. When a new periodic backup is performed, allthe backup files in the backup directory are deletedautomatically.

Manualbackup

Full backup: backs up all the dynamic data. When a new fullbackup is performed, all the backup files in the backupdirectory are deleted automatically.Incremental backup: Currently, the Oracle database does notsupport incremental backup. Therefore, do not performoperations related to incremental backup.

Storagedevice

Hard disk

Save path ofbackup files

/export/home/backup/omc

After the backup is performed, the backup contents are automatically packaged as a backup file.



172

Rules for Naming Dynamic Data Backup FilesWhen backing up the dynamic data, name the backup files in the following format: all-YYYYMMDDhhmmss.tar.

For example:

The file name all-20110601042002.tar refers to a full backup file generated on June 1, 2011 at04:20:02.

NOTE

l The latest backup information, including the generation time and backup file name, is recorded inthe /export/home/backup/omc/backup.log file.

l During the backup, the all-YYYYMMDDhhmmss folder is generated under the /export/home/backup/omc directory for storing backup files. When the backup is complete, the folder iscompressed into the all-YYYYMMDDhhmmss.tar file, and the all-YYYYMMDDhhmmss folder isautomatically deleted.

12.2 Backing Up and Restoring the M2000 Dynamic Data(SUSE)

This section describes how to back up and restore M2000 dynamic data.

12.2.1 Periodically Backing Up M2000 Dynamic Data (SUSE)This section describes how to periodically back up the M2000 dynamic data.

Prerequisitesl You have logged in to the M2000 client as a member of Administrators user group.l A hard disk has sufficient free space if you plan to back up data on the hard disk.

ContextGenerally, M2000 dynamic data is backed up periodically. The periodic backup of the dynamicdata is performed in full backup mode.

Dynamic data backup has no restriction on backup time. The backup can be performed duringthe system operation. The time required for backing up M2000 dynamic data is related to theactual environment. Generally, it takes about 2.5 hours to 3 hours to back up the dynamic data.

Do not change the storage medium on the System Backup tab page of the M2000 client.Currently, the IBM PC server supports only hard disk.

NOTE

Do not suspend a periodic backup task. Because the latest data fails to be restored after data is lost due toan accident such as the power-off of the server.

Procedure

Step 1 In the main window, choose Maintenance > Task Management.The Task Management dialog box is displayed.



173

Step 2 Double—click Task Type > Backup > Server Backup node. The Attribute dialog box forserver periodic backup is displayed, as shown in Figure 12-1.

Figure 12-1 Periodic backup

Step 3 Click Common Parameters and set Task Name and Start Time.

Step 4 Click Extended Parameters and set the backup period, as shown in Figure 12-2.Select a backup period from the Backup Period (days) drop-down list. The backup period canbe set to 1 to 7.



174

Figure 12-2 Periodic backup

Step 5 Click OK.

The system performs periodic backup automatically.

----End

12.2.2 Manually Backing Up M2000 Dynamic Data (SUSE)This section describes how to manually back up the M2000 dynamic data.

Prerequisitesl You are authorized to perform relevant operations.l A hard disk has sufficient free space if you plan to back up data on the hard disk.

ContextManual backup is a supplement of the periodic backup and is used in special or emergencysituations such as the failure of the M2000 system.

Dynamic data backup has no restriction on backup time. The backup can be performed duringthe system operation. The time required for backing up dynamic data is related to the actualenvironment. Generally, it takes about 2.5 hours to 3 hours to back up the dynamic data.

Do not change the storage medium on the System Backup tab page of the M2000 client.Currently, the IBM PC server supports only hard disk.



175

Procedure

Step 1 In the main window, choose Maintenance > Backup Management > System Backup. TheSystem Backup dialog box is displayed.

Figure 12-3 Manual backup

Step 2 On the System Backup dialog box shown in Figure 12-3, click Full Backup.

----End

12.2.3 Restoring the M2000 Dynamic Data (SUSE)This section describes how to restore the M2000 dynamic data.

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

l You have obtained the backup files for restoring the M2000 dynamic data.

l The M2000 is running properly.

Context

Based on the latest full backup files of the M2000, you can restore the M2000 system data. Afteryou perform the restoration operation, all the contents in the backup file package are restored.If certain data processed after the backup start time, such as the NE performance data or alarmdata, is not packed in the backup file package, the M2000 starts the automatic synchronizationfunction to obtain and process the data.

l During the restoration of dynamic data, the M2000 services stop automatically and do notprocess performance data or alarm data of NEs.

l After you change the IP address of the server or the password of the database user, thedynamic data backed up before the IP address or the database user password is changedcannot be restored.



176

Procedure

Step 1 Check the running status of M2000 services. To check the running status of M2000 services,see 8.2 Viewing the Running Status of M2000 Services (SUSE).If M2000 services are stopped, execute Step 2. Otherwise, stop M2000 services and then executeStep 2. To stop M2000 services, see 8.4 Stopping the M2000 Services (SUSE).

Step 2 Restart the Oracle.

To stop the Oracle, see How Do I Stop the Oracle Services. To start the Oracle, see How Do IStart the Oracle Services.

Step 3 Restore the M2000 data.1. Decompress the backup file that stores the to-be-restored dynamic data.

# cd /export/home/backup/omc

# tar xf backup file that stores dynamic data

For example, if you need to restore the full backup file generated on 18:06:22 2008-01-30,decompress the relevant package.

# tar xf all-20080130180622.tar

NOTE

You can decompress the related decompressed package to restore the backup files that stores dynamicdata.

2. Navigate to the path after the decompression.

# cd name of the backup file that stores dynamic data

For example:

# cd all-200801301806223. Run the following script to restore dynamic data:

# ./restore.sh4. If the following information is displayed, type the password of database user sys.

Note: Enter q/Q to exit this tool.Please input the super user's password of database[default:********]:

NOTE

You can type q or Q to quit the script.

5. If the following information is displayed, type 1 to start restoring dynamic data.

Please make a choice[1-2]:After the restoration is complete, the system displays Operation succeeds.

NOTE

The time required for restoring M2000 dynamic data is related to the actual environment. Generally,it takes about 3 hours to 4 hours to restore the dynamic data. Wait with patience.

Step 4 Run the following command to restart the M2000 services:

# . /opt/oss/server/svc_profile.sh

# cd /opt/oss/server/rancn/tools/common



177

# ./commonop.sh -ostartsvc

l If the following information is displayed, the M2000 service is started.Operation succeeds

l If the following information is displayed, the M2000 service fails to be started. In such acase, contact M2000 for assistance.Performing Start OSS services failed

NOTE

Starting the M2000 service takes a long time. Wait with patience.

Step 5 Run the following command to check whether all the M2000 services are started:

# . /opt/oss/server/svc_profile.sh

# svc_adm -cmd status

Check the value after Not Running : in the last line. If the value is 0, all the M2000 servicesare started.

In this case, the data restoration is complete.

Step 6 Delete the backup file after the data restoration is complete.

# cd /export/home/backup/omc

# rm -rf directory for storing the decompressed backup files

For example:

# rm -rf all-20080130180622

----End



178

13 FAQ

About This Chapter

This section describes some FAQs and their solutions.

13.1 How Do I Solve the Problem That the IMM Remote Window Does Not Respond?

13.2 How Do I Set Internet Explorer on the PC?

13.3 How Do I Handle the Problem of Certificate Error or Untrusted Website Displayed in theWeb Browser (IMM)?

13.4 How Do I Set on the IMM Operation Interface to Change Two Cursors to One Cursor?

13.5 How Do I Handle the Shortage of Disk Space on the M2000 Server (SUSE)

M2000Administrator Guide (x3850&x3650, SUSE10) 13 FAQ


179

13.1 How Do I Solve the Problem That the IMM RemoteWindow Does Not Respond?

QuestionWhat do I do if the IMM remote window does not respond when I use the IMM to manageservers?

Answer1. Restart the IMM. For details, see 7 in Configuring IMM Parameters.2. Log in to the IMM again.

13.2 How Do I Set Internet Explorer on the PC?

QuestionHow do I set Internet Explorer on the PC?

NOTE

l The settings on Internet Explorer 8.0 are provided. The following steps can serve as a reference if youuse the Internet Explorer of another version, though the setting options may be different.

l Internet Explorer is the recommended web browser.

Answer1. Open the Internet Explorer. Choose Tools > Internet Options to open the Internet

Options window.2. Click Security. In the Security tab page, click Custom level to open the Security Settings

- Internet Zone dialog box.3. In the Settings area, perform the following:

l Set the options under ActiveX controls and plug-ins as follows:– Set Automatic prompting for ActiveX controls to Enable.– Set Initialize and script ActiveX controls not marked as safe for scripting to

Prompt.– Set Download unsigned ActiveX controls to Prompt.

l Set Automatic prompting for file downloads under Downloads to Enable.4. Click OK to save your settings.5. Click OK to exit the Internet Options window.



180

13.3 How Do I Handle the Problem of Certificate Error orUntrusted Website Displayed in the Web Browser (IMM)?

Questionl When Internet Explorer is used to log in to the IMM, the web browser displays an error

message similar to Figure 13-1.l When Firefox is used to log in to the IMM, the web browser displays an error message

similar to Figure 13-2.

Figure 13-1 Certificate error message



181

Figure 13-2 Connection error message

Answer

Step 1 Log in to the PC as a user that is in the Administrators user group.

If Internet Explorer 8 runs on Windows 7, when you log in to the PC as a user that is in theAdministrators user group, you need to start Internet Explorer 8 as user administrator.Otherwise, you cannot set Internet Explorer.

Perform the following steps to start Internet Explorer 8.0 on Windows 7 as useradministrator:

1. Choose Start > Internet Explorer.2. In the displayed shortcut menu, choose Run as administrator.3. In the displayed dialog box, click Yes.

Step 2 Perform operations according to the browser type.

Browser Type Operation

Internet Explorer Perform Step 3 through Step 16.

Firefox Go to Step 17.

Step 3 View the certificate.1. When Internet Explorer displays the security certificate message shown in Figure 13-3,

click Continue to this website (not recommended).



182

Figure 13-3 Security certificate

2. Click Certificate Error, as shown in Figure 13-4.

Figure 13-4 Certificate error

3. In the displayed dialog box, click View Certificate.

Step 4 In the displayed root certificate dialog box shown in Figure 13-5, click Install Certificate.



183

Figure 13-5 Installing the root certificate

Step 5 In the displayed Certificate Import Wizard dialog box, click Next.

Step 6 As shown in Figure 13-6, select Place all certificates in the following store, click Browse,select Trusted Root Certification Authorities, and click OK.



184

Figure 13-6 Setting the certificate store

Step 7 Click Next.

Step 8 After confirming the certificate import information, click Finish.

Step 9 When the system displays the Security Warning dialog box asking you whether to install thecertificate, click Yes. If this dialog box is not displayed, skip this step.

Step 10 In the displayed dialog box indicating that the import is successful, click OK.

Step 11 Click OK. The Certificate dialog box is closed.

Step 12 On the menu bar of Internet Explorer, choose Tools > Internet Options.

Step 13 In the displayed Internet Options dialog box, click Advanced.

Step 14 In the Settings area, clear Warn about certificate address mismatch under Security.

Step 15 Click OK. The Internet Options dialog box is closed.

Step 16 Restart Internet Explorer and log in to the IMM again.

Step 17 If the web browser displays a message shown in Figure 13-7, click Add Exception.



185

Figure 13-7 Connection error message

Step 18 In the displayed dialog box, click Confirm Security Exception.

----End

13.4 How Do I Set on the IMM Operation Interface toChange Two Cursors to One Cursor?

QuestionHow do I set on the IMM operation interface to change two cursors to one cursor?

Answer1. In the Video Viewer window, choose Tools > Single Cursor.

NOTEPress F12 to quit single-cursor mode.

13.5 How Do I Handle the Shortage of Disk Space on theM2000 Server (SUSE)

QuestionYou can use any of the following methods to check the server disk space:



186

l View the message output area at the bottom of the M2000 client. If the disk partition usagereaches the threshold, you need to clear the disk space immediately.

l View the disk partition usage in the Hard Disk Monitoring window on the M2000 client.l Run the df -k command to check the disk partition usage.

How do I do when the server disk space is insufficient?

Solutionl If the system notifies you of the high disk space usage of the partition where the /data

directory is located, do not delete or transfer any files. In this case, contact Huawei technicalsupport engineers for assistance.

l If the system notifies you of the high disk space usage of the /export/home partition, see10.3 Clearing the Disk Space of the M2000 Server (SUSE) to troubleshoot.

l If the system notifies you of the high disk space usage of the root partition / or /opt, performas follows:

1. Use PuTTY to log in to the M2000 server in SSH mode as user ossuser.2. Run the following command to switch to user root.

> su - rootPassword: Password of root

3. Run the following command to collect related information:$ du -ak / | sort -nr > /tmp/du.out

4. Transfer the du.out file from the server to the PC by using the FileZilla tool.For details about how to use the FileZilla tool, see How Do I Use FileZilla to TransferFiles?. The configuration information required for transferring the files is as follows:– User and password: ossuser user and its password– Directory of files on the server: /tmp

5. Send the collection results to Huawei technical support engineers.



187

Documents

M2000 Administrator Guide-3850&3650-SUSE10-V200R012_06