M2000 Administrator Guide

M2000
V200R010
Administrator Guide (HP, SUSE10)

Issue
03
Date
2010-12-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 03 (2010-12-31)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
M2000
About This Document
About This Document
Purpose
This document is intended for the M2000 administrator. It is applicable to the M2000 singleserver system which use the HP rx2660 or HP rx7640 server and based on the SUSE Linux 10
operating system and the Oracle database. In addition, it provides the concepts related to system
management tasks, the detailed operation procedures, and the guide to routine and emergency
maintenance, and describes the usage of frequently used commands and tools and how to handle
common faults.
Product Version
The following table lists the product version related to this document:
Product Name
Product Version
M2000
V200R010
Intended Audience
The intended audiences of this document are network administrators.
Update History
03 (2010-12-31)
Third formal release.
Compared with 02 (2010-10-30), the following content is modified.
Issue 03 (2010-12-31)

iii
M2000
About This Document
Content
Description
2.5.1 Policies for Configuring the NTP

Service on the M2000 Server
New
2.5.4 Setting the M2000 Server as the

Intermediate-Layer NTP Server (HP)
New
14.3.7 How Should I Configure the

Monitoring Function for the S3000 Series
Disk Arrays
New
02 (2010-10-30)
Second formal release.
Compared with 01 (2010-04-02), the following content is modified.
Content
Description
2.3 Changing the Time Zone on the M2000

Server (SUSE)
Optimized the content descriptions
5.1.1 SUSE User
14.4.4 How Should I Periodically Monitor

the CPU, Memory, and Disk
01 (2010-04-02)
This is the initial field trial release.
Organization
1 Powering On/Off the M2000 System (SUSE)
This describes the procedures for powering on and off the M2000 system when HP rx2660 or
HP rx7640 acts as the M2000 server.
2 Setting the M2000 Time (SUSE)
This describes how to set the M2000 time. To enable the M2000 time to meet the time
requirements, you must synchronize the M2000 time with the time of the other M2000 devices
in the Huawei mobile network.
3 Configuring the Parameters of the M2000 Server (SUSE)
This describes how to set the parameters of the M2000 server.
iv

Issue 03 (2010-12-31)
M2000
About This Document
4 Managing the M2000 Clients

This chapter describes how to manage the M2000 clients. The graphic user interface (GUI) on
the M2000 client supports the O&M for the NEs and enables you to monitor the M2000. You
must manage the M2000 clients to ensure their normal operation.
5 Managing the M2000 Users (HP)
This describes how to manage the M2000 users, which involve Linux users, Oracle users, OM
users, and NE users. You can manage the accounts and authority of these users and monitor the
operation of these users.
6 Managing OSS System
The M2000 provides the OSS management function. By using this function, you can view NE
partitioning, manage the M2000 license, monitor the M2000 server, integrated task management,
check OMC status, collect NM log files.
7 Managing the M2000 Processes and Services (SUSE)
This describes how to manage the M2000 processes so that the processes and services on the
M2000 server can function properly.
8 Managing the M2000 Database (Oracle)
This chapter describes how to manage the M2000 database. This chapter also describes the
concepts of the M2000 database and procedures on how to view the database status, clear, and
back up the database.
9 Managing the M2000 Files and Disks (SUSE)
This describes how to manage the file systems and disks on the M2000 server and client.
10 Backing Up and Restoring the M2000 System (SUSE)
This describes how to back up and restore the M2000 system.
11 Maintaining the M2000 System (SUSE)
This describes how to perform the M2000 routine maintenance and recommends some
maintenance items and procedures.
12 Emergency Maintenance of the M2000 Client
This section provides guidance for emergency maintenance of the M2000 client.
13 Troubleshooting the M2000 (SUSE)
This chapter describes the procedures for troubleshooting the M2000.
14 FAQs (HP)
This chapter describes the FAQs and solutions related to the M2000.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 03 (2010-12-31)

M2000
About This Document
Symbol
Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
vi
Convention
Description
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 by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
Issue 03 (2010-12-31)
M2000
About This Document
Convention
Description
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical 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.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
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 means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 03 (2010-12-31)
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.
vii
M2000
Contents
Contents
About This Document...................................................................................................................iii
1 Powering On/Off the M2000 System (SUSE)........................................................................1-1
1.1 Powering On or Powering Off the M2000 System (rx2660)..........................................................................1-2
1.1.1 Powering On the M2000 System (rx2660)............................................................................................ 1-2
1.1.2 Powering Off the M2000 System (rx2660)............................................................................................1-3
1.2 Powering on or Powering Off the M2000 System (rx7640)...........................................................................1-4
1.2.1 Powering On the M2000 System (rx7640)............................................................................................ 1-4
1.2.2 Powering Off the M2000 System (rx7640)............................................................................................1-7
2 Setting the M2000 Time (SUSE)..............................................................................................2-1

2.1 Time Synchronization Solution for Huawei Mobile Network (SUSE)...........................................................2-2
2.1.1 Introduction to Time Synchronization................................................................................................... 2-2
2.1.2 Introduction to the NTP/SNTP...............................................................................................................2-3
2.1.3 Time Synchronization Modes of Mobile Network (SUSE)...................................................................2-6
2.2 Changing the Date and Time of the M2000 Server (SUSE).........................................................................2-12
2.3 Changing the Time Zone on the M2000 Server (SUSE)..............................................................................2-13
2.4 Modifying the Date, Time, and Time Zone on the M2000 Client................................................................2-14
2.5 Setting the NTP Service for the M2000 (HP)...............................................................................................2-15
2.5.1 Policies for Configuring the NTP Service on the M2000 Server.........................................................2-15
2.5.2 Checking the Time Settings on the M2000 Server (SUSE).................................................................2-16
2.5.3 Setting the M2000 Server as the NTP Client (HP)..............................................................................2-17
2.5.4 Setting the M2000 Server as the Intermediate-Layer NTP Server (HP)..............................................2-18
2.5.5 Checking the Running Status of the NTP Service on the M2000 Server (SUSE)...............................2-21
2.5.6 Setting the NTP Service on the M2000 Client.....................................................................................2-22
2.6 Setting the DST for the M2000 System (SUSE)...........................................................................................2-23
2.6.1 Introduction to the DST........................................................................................................................2-24
2.6.2 Viewing the DST Rules of a Time Zone .............................................................................................2-24
2.6.3 Changing the Time Zone on the M2000 Server (SUSE).....................................................................2-26
3 Configuring the Parameters of the M2000 Server (SUSE)..................................................3-1

3.1 Changing the Host Name of the M2000 Server (SUSE).................................................................................3-2
3.2 Adding or Deleting Routes on the M2000 Server (SUSE)............................................................................. 3-3
3.3 Changing the IP Address of the M2000 Server (SUSE).................................................................................3-4
3.4 Changing the IP Address of the MP Ethernet Port on the rx7640 Server.......................................................3-9
Issue 03 (2010-12-31)

ix
M2000
Contents
3.5 Changing the IP Address of the S3200 Disk Array (Serial Port Mode).......................................................3-13
3.6 Changing the IP Address of the S2600 Disk Array (Serial Port Mode).......................................................3-17
4 Managing the M2000 Clients...................................................................................................4-1

4.1 Managing Files and Disks on M2000 Clients.................................................................................................4-2
4.1.1 Introduction to the M2000 Client File System.......................................................................................4-2
4.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................4-4
4.2 Monitoring the Login Status of the M2000 Clients........................................................................................4-5
4.3 Setting the Number of Clients Accessible on a PC.........................................................................................4-5
4.4 Setting the Time Information on the M2000 Client........................................................................................4-6
4.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client.........................................................4-7
4.4.2 Setting the NTP Service on the M2000 Client.......................................................................................4-7
5 Managing the M2000 Users (HP).............................................................................................5-1

5.1 Types of M2000 Users (SUSE).......................................................................................................................5-2
5.1.1 SUSE User..............................................................................................................................................5-2
5.1.2 OM Users...............................................................................................................................................5-5
5.2 Managing SUSE Users (HP)...........................................................................................................................5-6
5.2.1 Changing the Password of User root......................................................................................................5-7
5.2.2 Changing the Password of User omcuser...............................................................................................5-7
5.2.3 Changing the Password of User ftpuser (SUSE)....................................................................................5-8
5.2.4 Changing the Password of User oracle................................................................................................5-10
5.2.5 Creating a SUSE User (SUSE).............................................................................................................5-10
5.2.6 Deleting SUSE Users (SUSE)..............................................................................................................5-11
5.3 Managing Oracle Users (HP)........................................................................................................................5-12
5.3.1 Introduction to Oracle Users................................................................................................................5-12
5.3.2 Changing the Password of Oracle user system....................................................................................5-12
5.4 Managing OM Users.....................................................................................................................................5-14
6 Managing OSS System..............................................................................................................6-1

6.1 Monitoring the M2000 Server.........................................................................................................................6-3
6.1.1 Refreshing the Monitoring Information.................................................................................................6-4
6.1.2 Viewing the CPU and Memory Usage of the M2000 Server (SUSE)...................................................6-4
6.1.3 Viewing the Disk Usage of the M2000 Server on the M2000 Client (SUSE).......................................6-5
6.1.4 Viewing the Database Usage of the M2000 Server on the Client (SUSE)............................................6-6
6.1.5 Checking the M2000 Services................................................................................................................6-7
6.1.6 Checking the Status of the M2000 Processes.........................................................................................6-8
6.1.7 Viewing the Information about M2000 Server Components.................................................................6-9
6.1.8 Saving the Monitoring Information......................................................................................................6-10
6.1.9 Setting Alarm Thresholds for the M2000............................................................................................6-10
6.2 Querying the System Logs of the M2000.....................................................................................................6-18
6.3 Collecting NM Log Files...............................................................................................................................6-19
6.4 Querying NE Subareas..................................................................................................................................6-21
6.5 Managing the M2000 License.......................................................................................................................6-22
x

Issue 03 (2010-12-31)
M2000
Contents
6.5.1 Querying the M2000 License...............................................................................................................6-22

6.5.2 Updating the M2000 License...............................................................................................................6-22
6.6 Check OMC status........................................................................................................................................6-23
6.7 Managing OSS System Tasks in Centralized Manner..................................................................................6-24
6.7.1 Overview of Integrated Task Management..........................................................................................6-25
6.7.2 Customizing the Interface for Managing Timing Tasks......................................................................6-41
6.7.3 Creating a User Timing Task...............................................................................................................6-42
6.7.4 Modifying a Timing Task....................................................................................................................6-43
6.7.5 Managing Timing Tasks.......................................................................................................................6-44
6.7.6 Viewing Timing Tasks.........................................................................................................................6-47
6.7.7 Downloading Task Execution Tasks....................................................................................................6-49
6.7.8 Downloading Result Files....................................................................................................................6-49
6.7.9 Reference of the OSS Management GUI.............................................................................................6-52
7 Managing the M2000 Processes and Services (SUSE).........................................................7-1

7.1 Introduction to M2000 Processes and Services...............................................................................................7-2
7.1.1 3rdTool_agent Process...........................................................................................................................7-5
7.1.2 adn_agent Process..................................................................................................................................7-5
7.1.3 adss_agent Process.................................................................................................................................7-6
7.1.4 antenna_agent Process............................................................................................................................7-6
7.1.5 ce_agent Process.................................................................................................................................... 7-6
7.1.6 cmdc_agent Process............................................................................................................................... 7-6
7.1.7 cmengine_agent Process........................................................................................................................ 7-7
7.1.8 cmeserver_agent Process........................................................................................................................7-7
7.1.9 cmexp_agent Process............................................................................................................................. 7-7
7.1.10 cmserver_agent Process....................................................................................................................... 7-7
7.1.11 cnnhc_agent Process............................................................................................................................ 7-8
7.1.12 corba_agent Process.............................................................................................................................7-8
7.1.13 cpm_agent Process...............................................................................................................................7-8
7.1.14 devdoc_agent Process.......................................................................................................................... 7-8
7.1.15 dsXXXX agent Process..........................................................................................................................7-8
7.1.16 eam_agent Process............................................................................................................................... 7-9
7.1.17 em agent Process..................................................................................................................................7-9
7.1.18 fars_agent Process................................................................................................................................7-9
7.1.19 fmnotify_agent Process......................................................................................................................7-10
7.1.20 FMPreServiceXXXX_agent Process...................................................................................................7-10
7.1.21 fnlicense_agent Process......................................................................................................................7-10
7.1.22 glmssyn_agent Process.......................................................................................................................7-10
7.1.23 ifms_agent Process.............................................................................................................................7-11
7.1.24 ipm_agent Process..............................................................................................................................7-11
7.1.25 irp_agent Process................................................................................................................................7-11
7.1.26 itm_agent Process...............................................................................................................................7-12
7.1.27 lic_agent Process................................................................................................................................7-12
Issue 03 (2010-12-31)

xi
M2000
Contents
7.1.28 log_agent Process...............................................................................................................................7-13

7.1.29 maintain_agent Process......................................................................................................................7-13
7.1.30 manager_agent Process......................................................................................................................7-13
7.1.31 medXXXX_agent Process...................................................................................................................7-13
7.1.32 necomm_agent Process......................................................................................................................7-14
7.1.33 nelicense_agent Process.....................................................................................................................7-14
7.1.34 neuser_agent Process..........................................................................................................................7-14
7.1.35 ngnffs_agent Process..........................................................................................................................7-14
7.1.36 ngnnis_agent Process.........................................................................................................................7-14
7.1.37 ngnni112_agent Process.....................................................................................................................7-15
7.1.38 ngntestmanage_agent Process............................................................................................................7-15
7.1.39 nhcservice_agent Process...................................................................................................................7-15
7.1.40 nicservice_agent Process....................................................................................................................7-15
7.1.41 nimserver_agent Process....................................................................................................................7-15
7.1.42 nms_mml_agent Process....................................................................................................................7-16
7.1.43 partition_agent Process......................................................................................................................7-16
7.1.44 pm_agent Process...............................................................................................................................7-16
7.1.45 pmexp_agent Process.........................................................................................................................7-16
7.1.46 pmmon_agent Process........................................................................................................................7-17
7.1.47 pmncdXX01_agent Process................................................................................................................7-17
7.1.48 porttrunk_agent Process.....................................................................................................................7-17
7.1.49 proxy_agent Process...........................................................................................................................7-17
7.1.50 PRSAssistantService_agent Process..................................................................................................7-18
7.1.51 prsdc_agent Process...........................................................................................................................7-18
7.1.52 prsfs_agent Process............................................................................................................................7-18
7.1.53 prsreport_agent Process......................................................................................................................7-18
7.1.54 prssum_agent Process........................................................................................................................7-18
7.1.55 rn_agent Process.................................................................................................................................7-19
7.1.56 ScriptModuleService_agent Process..................................................................................................7-19
7.1.57 scriptserver_agent Process.................................................................................................................7-19
7.1.58 sm_agent Process...............................................................................................................................7-19
7.1.59 snmp_agent Process...........................................................................................................................7-20
7.1.60 son_agent Process..............................................................................................................................7-20
7.1.61 sso_agent Process...............................................................................................................................7-20
7.1.62 swm_agent Process............................................................................................................................7-20
7.1.63 threshold_agent Process.....................................................................................................................7-20
7.1.64 uap_agent Process..............................................................................................................................7-21
7.1.65 udpdispatch_agent Process.................................................................................................................7-21
7.1.66 umgupdsvr_agent Process..................................................................................................................7-21
7.1.67 xftpXX01_agent Process.....................................................................................................................7-21
7.1.68 Processes and Services Related to Each Northbound Interface.........................................................7-22
7.1.69 Checking the Status of the M2000 Processes.....................................................................................7-23
xii

Issue 03 (2010-12-31)
M2000
Contents
7.2 Managing the M2000 Services (SUSE)........................................................................................................7-24

7.2.1 Checking the M2000 Services..............................................................................................................7-24
7.2.2 Viewing the Running Status of M2000 Services (SUSE)....................................................................7-25
7.2.3 Starting the M2000 Server (SUSE)......................................................................................................7-27
7.2.4 Stopping the M2000 Services (SUSE).................................................................................................7-27
8 Managing the M2000 Database (Oracle)................................................................................8-1

8.1 Introduction to the M2000 Database (Oracle).................................................................................................8-2
8.1.1 cmedb.....................................................................................................................................................8-2
8.1.2 omcdb.....................................................................................................................................................8-2
8.1.3 omclogdb................................................................................................................................................8-4
8.1.4 omcsmdb................................................................................................................................................8-5
8.1.5 omctmdb.................................................................................................................................................8-6
8.1.6 fmdb.......................................................................................................................................................8-6
8.1.7 pmdb.......................................................................................................................................................8-7
8.1.8 swmdb....................................................................................................................................................8-8
8.1.9 pmcomdb................................................................................................................................................8-8
8.1.10 sumdb.................................................................................................................................................8-10
8.1.11 itfndb..................................................................................................................................................8-14
8.1.12 farsdb..................................................................................................................................................8-14
8.1.13 omctempdb.........................................................................................................................................8-15
8.1.14 omceamdb..........................................................................................................................................8-15
8.2 Viewing the Status of the M2000 Database (Oracle)....................................................................................8-16
8.2.1 Viewing the Database Usage of the M2000 Server on the Client (SUSE)..........................................8-17
8.2.2 Viewing the Database Usage of the M2000 Server Using Oracle Commands....................................8-18
8.3 Clearing M2000 Databases...........................................................................................................................8-19
8.4 Backing Up the M2000 Databases (Oracle)..................................................................................................8-21
9 Managing the M2000 Files and Disks (SUSE)......................................................................9-1

9.1 Managing Files and Disks on M2000 Clients.................................................................................................9-2
9.1.1 Introduction to the M2000 Client File System.......................................................................................9-2
9.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................9-4
9.2 Managing Files and Disks on the M2000 Server (SUSE)...............................................................................9-5
9.2.1 Introduction to the M2000 Server File System (SUSE).........................................................................9-5
9.2.2 Viewing the Disk Usage of the M2000 Server on the M2000 Client (SUSE).....................................9-10
9.2.3 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands...................................9-11
9.2.4 Clearing the Disk Space of the M2000 Server (SUSE).......................................................................9-12
10 Backing Up and Restoring the M2000 System (SUSE)...................................................10-1

10.1 Data Backup and Restore of the M2000 (SUSE)........................................................................................10-2
10.1.1 Backup of M2000 Dynamic Data (SUSE).........................................................................................10-2
10.1.2 Strategies on Backup and Restore of the M2000 System (SUSE).....................................................10-3
10.2 Backing Up and Restoring M2000 Dynamic Data (SUSE)........................................................................10-4
10.2.1 Setting the Storage Device of Backup Data Using Linux Commands...............................................10-4
Issue 03 (2010-12-31)

xiii
M2000
Contents
10.2.2 Setting the Storage Device of Backup Data Through the Client........................................................10-6
10.2.3 Setting the Wait Time for Replacing a Tape......................................................................................10-8
10.2.4 Periodically Backing Up M2000 Dynamic Data (SUSE)..................................................................10-9
10.2.5 Manually Backing Up M2000 Dynamic Data (SUSE)....................................................................10-12
10.2.6 Restoring the M2000 Dynamic Data (SUSE)..................................................................................10-14
11 Maintaining the M2000 System (SUSE).............................................................................11-1

11.1 M2000 Routine Maintenance Items(SUSE10)............................................................................................11-4
11.2 Checking the Configuration of Alarm Timing............................................................................................11-6
11.3 Checking the Configuration of Automatic Log Dump................................................................................11-6
11.4 Checking the Synchronization Time of NE Log.........................................................................................11-8
11.5 Checking the Configuration of the File Server .......................................................................................... 11-8
11.6 Checking the Configuration of System Backup..........................................................................................11-9
11.7 Checking the Configuration of System Monitoring..................................................................................11-10
11.8 Checking the Synchronization Time of NE Configuration.......................................................................11-17
11.9 Checking the Status of Performance Measurement..................................................................................11-18
11.10 Checking the Missing Performance Result.............................................................................................11-18
11.11 Checking the Alarm Reception...............................................................................................................11-19
11.12 Checking the NMS Connection...............................................................................................................11-19
11.13 Checking the Functionality of Alarm Box..............................................................................................11-20
11.14 Checking the Owner of the M2000 File System.....................................................................................11-20
11.15 Checking the Threshold of Network Management Capability................................................................11-21
11.16 Check OMC Alarms/Events....................................................................................................................11-21
11.17 Checking Connections Between the M2000 and NEs............................................................................11-24
11.18 Checking the Status of the M2000 Routes..............................................................................................11-25
11.19 Checking M2000 Logs............................................................................................................................11-25
11.20 Checking SUSE Error Logs....................................................................................................................11-26
11.21 Checking the CPU Usage of the M2000 Server (SUSE)........................................................................11-26
11.22 Checking the Disk Usage of the M2000 Server (SUSE)........................................................................11-27
11.23 Checking M2000 Database Status (SUSE).............................................................................................11-28
11.24 Checking the States of M2000 Services..................................................................................................11-30
11.25 Checking the Core Files on the Server....................................................................................................11-30
11.26 Backing Up the M2000 System (SUSE).................................................................................................11-31
11.27 Querying the M2000 License..................................................................................................................11-31
11.28 Checking the Time of the M2000 Server (SUSE)...................................................................................11-31
11.29 Checking the Power Supply of the M2000 Server..................................................................................11-32
12 Emergency Maintenance of the M2000 Client..................................................................12-1

13 Troubleshooting the M2000 (SUSE)...................................................................................13-1
13.1 Procedure for Troubleshooting the M2000.................................................................................................13-2
13.2 Collecting M2000 Site and Software Information (SUSE).........................................................................13-3
13.2.1 Collecting the M2000 Site Information............................................................................................. 13-3
13.2.2 Collecting the Time of M2000 Fault Occurrence.............................................................................. 13-3
xiv

Issue 03 (2010-12-31)
M2000
Contents
13.2.3 Obtaining the IP Address of the M2000 Server (SUSE)....................................................................13-4

13.2.4 Collecting SUSE Version Information (HP)......................................................................................13-5
13.2.5 Collecting Oracle Version Information (HP).....................................................................................13-5
13.2.6 Obtaining the Version Information About the M2000.......................................................................13-6
14 FAQs (HP)................................................................................................................................ 14-1

14.1 FAQs About the SUSE Operating System (HP).........................................................................................14-2
14.1.1 How to Grant User root with the telnet Authority (HP).....................................................................14-2
14.1.2 How to Grant User root with the FTP Authority (HP).......................................................................14-3
14.1.3 How to Check the Status of the Tape Drive (SUSE).........................................................................14-4
14.1.4 How to Select the Tape Drive (SUSE)...............................................................................................14-4
14.1.5 How to View the Hardware Configuration of the M2000 Server (SUSE).........................................14-6
14.1.6 How to Check the Device Status of the M2000 Server (SUSE)........................................................14-6
14.1.7 How to Query a Time Zone Name (SUSE)........................................................................................14-8
14.1.8 How Should I Start the NTP Service on the M2000 Server (HP)....................................................14-10
14.1.9 How Should I Stop the NTP Service on the M2000 Server (HP)....................................................14-11
14.1.10 How Should I Check the Running Status of the FTP Service on the M2000 Server.....................14-12
14.1.11 How Should I Start the FTP Service on the M2000 Server...........................................................14-12
14.1.12 How Should I Check the Running Status of the SFTP Service on the M2000 Server?.................14-13
14.1.13 How Should I Start the SFTP Service on the M2000 Server?.......................................................14-13
14.2 FAQs About the Oracle (HP)....................................................................................................................14-14
14.2.1 How to Check Whether the Oracle Is Started (HP)..........................................................................14-14
14.2.2 How to Start the Oracle (HP)...........................................................................................................14-15
14.2.3 How to Stop the Oracle (HP)...........................................................................................................14-16
14.3 FAQs About the TCP/IP Network (SUSE)...............................................................................................14-17
14.3.1 How Do I Change the IP Address of the S3200 Disk Array (Command Mode)?...........................14-18
14.3.2 How Do I Change the IP Address of the S2600 Disk Array (Command Mode).............................14-20
14.3.3 How to Connect the Client to the Server with Multiple IP Addresses (SUSE)...............................14-22
14.3.4 How Should I Log In to the Server in SSH Mode?..........................................................................14-23
14.3.5 How Should I Log In to the Server in MP Mode?...........................................................................14-25
14.3.6 How Do I Configure the Monitoring Function of the S2600 Disk Array?......................................14-25
14.3.7 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays....................14-27
14.4 FAQs About the M2000 Server Application (SUSE)...............................................................................14-30
14.4.1 Why the M2000 Services Are Restarted Abnormally (SUSE)........................................................14-31
14.4.2 Why M2000 Services Stop Abnormally..........................................................................................14-32
14.4.3 What Should I Do When I Fail to Stop the M2000 Services...........................................................14-32
14.4.4 How Should I Periodically Monitor the CPU, Memory, and Disk..................................................14-33
14.4.5 How to Change the MP Password of rx2660...................................................................................14-34
14.4.6 How to Change the MP Password of rx7640...................................................................................14-36
14.4.7 How to Use the iLO MP to Check Whether the HP rx2660 Server Is Connected with the Power Supply
.....................................................................................................................................................................14-38
14.4.8 How Should I Add the DVD Option (rx2660).................................................................................14-38
14.4.9 How Should I Add the DVD Option (rx7640).................................................................................14-40
Issue 03 (2010-12-31)

xv
M2000
Figures
Figures
Figure 1-1 Power switch of the HP rx2660 server...............................................................................................1-2
Figure 1-2 Boot Menu interface...........................................................................................................................1-3
Figure 1-3 S2600 disk array.................................................................................................................................1-5
Figure 1-4 S3200 disk array.................................................................................................................................1-6
Figure 1-5 Boot Menu interface...........................................................................................................................1-7
Figure 1-6 Disk array (I)......................................................................................................................................1-9
Figure 1-7 Disk array (II)...................................................................................................................................1-10
Figure 2-1 NTP rationale......................................................................................................................................2-4
Figure 2-2 NTP layered architecture....................................................................................................................2-5
Figure 2-3 Schematic diagram of time synchronization for the RAN device......................................................2-7
Figure 2-4 Directly connecting the RAN and the NTP server.............................................................................2-9
Figure 2-5 Networking of the RAN and the intermediate-layer NTP server.....................................................2-10
Figure 2-6 Directly connecting the RAN and the highest-layer NTP server.....................................................2-11
Figure 2-7 Configuring the NTP client .............................................................................................................2-18
Figure 3-1 Serial ports of the S3X00..................................................................................................................3-13
Figure 3-2 Viewing the port configuration of the controller..............................................................................3-14
Figure 3-3 Port configuration (I)........................................................................................................................3-15
Figure 3-4 Port configuration (II).......................................................................................................................3-15
Figure 3-5 Port configuration (II).......................................................................................................................3-16
Figure 3-6 Port configuration (IV).....................................................................................................................3-16
Figure 3-7 Serial ports provided by the S2600 disk array..................................................................................3-18
Figure 3-8 Successful connection interface........................................................................................................3-19
Figure 3-9 Successful login dialog box..............................................................................................................3-20
Figure 6-1 Server Monitor....................................................................................................................................6-5
Figure 6-2 Hard Disk Monitor..............................................................................................................................6-6
Figure 6-3 Database monitoring...........................................................................................................................6-7
Figure 6-4 Service Monitor tab page....................................................................................................................6-8
Figure 6-5 Process Monitor tab page...................................................................................................................6-9
Figure 6-6 System Monitor Settings dialog box................................................................................................6-11
Figure 6-7 State transition of a scheduled task...................................................................................................6-40
Figure 6-8 Task Management window...............................................................................................................6-53
Figure 7-1 Process Monitor tab page.................................................................................................................7-23
Figure 7-2 Service Monitor tab page..................................................................................................................7-25
Issue 03 (2010-12-31)

xvii
M2000
Figures
Figure 8-1 Database monitoring.........................................................................................................................8-17

Figure 8-2 Periodic backup................................................................................................................................8-22
Figure 8-3 Manual backup.................................................................................................................................8-23
Figure 9-1 Hard Disk Monitor............................................................................................................................9-11
Figure 10-1 Setting the storage device (I)..........................................................................................................10-7
Figure 10-2 Setting the storage device (II).........................................................................................................10-8
Figure 10-3 Periodic backup............................................................................................................................10-10
Figure 10-4 Manual backup.............................................................................................................................10-11
Figure 10-5 Manual backup.............................................................................................................................10-13
Figure 14-1 PuTTY Configuration...................................................................................................................14-24
Figure 14-2 PuTTY Security Alert...................................................................................................................14-24
Figure 14-3 SNMP tab page............................................................................................................................14-29
Figure 14-4 Boot Menu interface....................................................................................................................14-39
Figure 14-5 Boot Menu without the DVD option...........................................................................................14-39
Figure 14-6 Adding a boot option....................................................................................................................14-39
Figure 14-7 Choosing a DVD boot option.......................................................................................................14-40
Figure 14-8 Quitting the addition of a boot option..........................................................................................14-40
Figure 14-9 Boot Menu....................................................................................................................................14-41
Figure 14-10 Boot Menu without the DVD option.........................................................................................14-41
Figure 14-11 Adding a boot option..................................................................................................................14-41
Figure 14-12 Choosing a DVD boot option.....................................................................................................14-42
Figure 14-13 Quitting the addition of a boot option........................................................................................14-42
Figure 14-14 Returning to the main menu.......................................................................................................14-43
Figure 14-15 Boot Menu with the DVD option..............................................................................................14-43
xviii

Issue 03 (2010-12-31)
M2000
Tables
Tables
Table 2-1 Policies for configuring the NTP service...........................................................................................2-16
Table 2-2 Advantages and disadvantages of the two configuration policies......................................................2-16
Table 3-1 Adding or deleting a route....................................................................................................................3-4
Table 3-2 Setting the properties of the serial port................................................................................................3-5
Table 3-3 Setting properties of the serial port....................................................................................................3-14
Table 3-4 Configuration items of the controller port......................................................................................... 3-15
Table 3-5 Setting the properties of a serial port................................................................................................. 3-19
Table 4-1 M2000 client software directory..........................................................................................................4-2
Table 5-1 Linux users...........................................................................................................................................5-3
Table 5-2 Management modes of OM users........................................................................................................5-6
Table 6-1 Server Monitor...................................................................................................................................6-12
Table 6-2 Hard Disk Monitor.............................................................................................................................6-14
Table 6-3 Database Monitor...............................................................................................................................6-16
Table 6-4 Service Monitor..................................................................................................................................6-17
Table 6-5 Parameters for the NE Partitioning Information................................................................................6-21
Table 6-6 Parameters for Selecting Objects for OMC Check............................................................................ 6-24
Table 6-7 Tasks grouped according to the execution period..............................................................................6-26
Table 6-8 Tasks grouped according to the function...........................................................................................6-26
Table 6-9 Tasks grouped according to the feature..............................................................................................6-31
Table 6-10 Description of system scheduled tasks.............................................................................................6-32
Table 6-11 Description of user scheduled tasks.................................................................................................6-34
Table 6-12 Allowable operations for different task types..................................................................................6-50
Table 6-13 Description of the Task Management window................................................................................ 6-53
Table 6-14 Parameters Applicable for both Once and Period Tasks..................................................................6-55
Table 6-15 Parameters Only Applicable for Period Tasks.................................................................................6-56
Table 6-16 Extended parameters of NIC Configuration Data Export tasks...................................................6-58
Table 6-17 Description of extended parameters.................................................................................................6-61
Table 7-1 Relationships between northbound interfaces and their corresponding processes and services........7-22
Table 8-1 Names and functions of tables in the cmedb database.........................................................................8-2
Table 8-2 Names and functions of tables in the omcdb database.........................................................................8-2
Table 8-3 Names and functions of tables in the omclogdb database....................................................................8-4
Table 8-4 Names and functions of tables in the omcsmdb database....................................................................8-5
Table 8-5 Names and functions of tables in the omctmdb database.....................................................................8-6
Issue 03 (2010-12-31)

xix
M2000
Tables
Table 8-6 Tables of the fmdb database and the corresponding functions............................................................8-7
Table 8-7 Template tables in the pmdb and their functions.................................................................................8-7
Table 8-8 Function subset tables and period tables in the pmdb and the corresponding functions.....................8-8
Table 8-9 Names and functions of tables in the swmdb database........................................................................8-8
Table 8-10 Counter information tables in the pmcomdb and the corresponding functions.................................8-9
Table 8-11 Template information tables in the pmcomdb and the corresponding functions...............................8-9
Table 8-12 Function subsets and period tables in the pmcomdb and their functions.........................................8-10
Table 8-13 Name and function of each object type information table in the sumdb..........................................8-10
Table 8-14 Name and function of each system setting information table in the sumdb....................................8-11
Table 8-15 Name and function of each report information table in the sumdb..................................................8-12
Table 8-16 Name and function of each performance result table in the sumdb.................................................8-13
Table 8-17 Names and functions of tables in the itfndb database......................................................................8-14
Table 8-18 Names and functions of tables in the farsdb database......................................................................8-15
Table 8-19 Names and functions of tables in the omctempdb database.............................................................8-15
Table 8-20 Names and functions of tables in the omceamdb database..............................................................8-15
Table 9-1 M2000 client software directory..........................................................................................................9-2
Table 9-2 Directories for storing the M2000 server software..............................................................................9-6
Table 9-3 Disk partitions of the HP rx2660 server...............................................................................................9-9
Table 9-4 Disk partitions of the HP rx7640 server...............................................................................................9-9
Table 9-5 Disk partitions of the S3200 disk array..............................................................................................9-10
Table 9-6 Disk partitions of the S2600 disk array..............................................................................................9-10
Table 10-1 Introduction to dynamic data backup...............................................................................................10-2
Table 10-2 Values of backupMedia..................................................................................................................10-6
Table 11-1 Maintenance item list.......................................................................................................................11-4
Table 11-2 Server Monitor...............................................................................................................................11-11
Table 11-3 Hard Disk Monitor.........................................................................................................................11-13
Table 11-4 Database Monitor...........................................................................................................................11-15
Table 11-5 Service Monitor..............................................................................................................................11-16
Table 11-6 Alarms that need to be handled immediately.................................................................................11-21
Table 11-7 Alarms that need to be handled within one day.............................................................................11-22
Table 11-8 Alarms to be focused on during network expansion......................................................................11-23
Table 11-9 Alarms about malicious operations................................................................................................11-23
Table 11-10 Events that need to be handled immediately................................................................................11-23
Table 11-11 Events that need to be handled within one day............................................................................11-24
Table 11-12 Events that need to be focused on during network expansion.....................................................11-24
Table 14-1 Tape drive status..............................................................................................................................14-4
Table 14-2 Checking the server configuration...................................................................................................14-6
Table 14-3 Commands for checking the device status.......................................................................................14-6
Table 14-4 Example of the matching table between countries and time zone names........................................14-9
xx

Issue 03 (2010-12-31)
M2000
Powering On/Off the M2000 System (SUSE)
About This Chapter

This describes the procedures for powering on and off the M2000 system when HP rx2660 or
HP rx7640 acts as the M2000 server.
1.1 Powering On or Powering Off the M2000 System (rx2660)
You need to follow a specific operation sequence to power on or power off the M2000 system
to guarantee the system security.
1.2 Powering on or Powering Off the M2000 System (rx7640)
Issue 03 (2010-12-31)

1-1
M2000
1.1 Powering On or Powering Off the M2000 System (rx2660)

1.1.1 Powering On the M2000 System (rx2660)
This describes how to power on the M2000 system when the HP rx2660 server acts as the
M2000 server.
1.1.2 Powering Off the M2000 System (rx2660)
This describes how to power off the M2000 system when the HP rx2660 server acts as the
M2000 server.

This describes how to power on the M2000 system when the HP rx2660 server acts as the
M2000 server.
Prerequisite
l
The cabinet is provided with power supply.
The server is provided with power supply through two power cables connected to the back
panel of the server.
The communication between the PC and the iLO 2 MP serial port is normal.
Procedure
Step 1 Press the power switch on the front panel of the HP rx2660 server to start the M2000 system,
as shown in Figure 1-1.
The power indicator turns green from yellow.
Figure 1-1 Power switch of the HP rx2660 server
Step 2 After the server is powered on, run the following command on the PC to set up the connection
between the PC and the iLO 2 MP.
telnet <IP address of the iLO 2 MP>
1-2

Issue 03 (2010-12-31)
M2000
After a successful login, type the user name and password of the iLO 2 MP. The default user
name and password are both Admin.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
Run the CM command. The system switches to the iLO 2 MP command line mode.
[osssvr-mp] MP> CM
Run the RS command to restart the server.
[osssvr-mp] MP:CM> RS
When the system displays the following prompt, press Y.
Type Y to confirm your intention to restart the system: (Y/[N])
Step 3 View the startup of the operating system.

[osssvr-mp] MP:CM> EXIT
[osssvr-mp] MP> CO
After you run the previous commands, waitting for about 5 minutes until the Boot Menu interface
is displayed, as shown in Figure 1-2.
Figure 1-2 Boot Menu interface
----End

M2000 server.
Issue 03 (2010-12-31)

1-3
M2000
Procedure
Step 1 Check whether the M2000 is started by referring to 7.2.2 Viewing the Running Status of M2000
Services (SUSE). Stop the M2000 services if they are running. For details on how to stop the
M2000, see 7.2.4 Stopping the M2000 Services (SUSE).
Step 2 Check whether the Oracle database is started by referring to 14.2.1 How to Check Whether
the Oracle Is Started (HP). Stop the Oracle database.
For details about how to stop the Oracle database, see 14.2.3 How to Stop the Oracle (HP).
Step 3 Log in to the HP rx2660 server as user root and shut it down.
The operating system becomes standby.
# sync; sync; sync; sync; sync; sync
# shutdown -y -g0 -i0
Step 4 Shut down the power supply of the server and the cabinet if required.
----End
1.2 Powering on or Powering Off the M2000 System (rx7640)

This section describes how to power on the M2000 system. After the M2000 server is provided
with power supply, all the parts of the server do not work if the server is not powered on, except
the MP card. To guarantee the normal operation of the server, you need to power on the
M2000 server.
M2000 server.

This section describes how to power on the M2000 system. After the M2000 server is provided
with power supply, all the parts of the server do not work if the server is not powered on, except
the MP card. To guarantee the normal operation of the server, you need to power on the
M2000 server.
Prerequisite
l
The cabinet is powered on.
The server is provided with power supply through four power cables.
The communication between the PC and the iLO 2 MP serial port is normal.
Procedure
Step 1 Power on the disk array.
1-4

Issue 03 (2010-12-31)
M2000
Option
Description
S2600 disk array
Perform Step 1.1.
S3200 disk array or 6140 disk array
Perform Step 1.2.
1.
Insert the two plugs at the rear of the disk array into the socket, as shown in Figure 1-3.
When the hard disk LEDs of all the disk arrays stop blinking, the disk array are started
successfully.
CAUTION
l Each disk array has two plugs. Ensure that both plugs are inserted into the socket.
l The S2600 disk array does not have a power switch. After you insert the plug into the
socket, the S2600 disk array is automatically powered on.
Figure 1-3 S2600 disk array
(Disk array with a controller)
(Hard disk frame of the disk array)
2.
Set the two power switches at the rear of the S3200 disk array to ON, as shown in Figure
1-4.
CAUTION
Each disk array has two power switches and their directions are opposite.
Issue 03 (2010-12-31)

1-5
M2000
Figure 1-4 S3200 disk array
OFF
ON
Step 2 Run the following command on the PC to set up the connection between the PC and the iLO 2
MP.
After a successful login, type the user name and password of the iLO 2 MP. The default user
name and password are both Admin.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
Step 3 Run the CM command. The system switches to the MP command line mode.
[osssvr-mp] MP> CM
NOTE
l The MP commands are not case sensitive.

l You can press Ctrl+B to return to the main menu.
Step 4 Power on the subrack where the server resides.

1.
Run the PC command. The power control menu is displayed.

[osssvr-mp] MP:CM> PC
2.
When the system displays the following prompt, type T:

This command controls power enable to a hardware device.
T - Cabinet
C - Cell
P - IO Chassis
R - Partition
Select Device: T
3.
When the system displays the following prompt, type ON to power on the subrack where
the server resides.
The power state is OFF for Cabinet 0.
In what state do you want the power? (ON/OFF) ON
1-6

Issue 03 (2010-12-31)
M2000
Step 5 Power on the server partitions.

1.

2.
When the system displays the following prompt, type R:

T - Cabinet
C - Cell
P - IO Chassis
R - Partition
Select Device: R
3.
When the system displays the following prompt, type 0 to select the corresponding partition,
and then type ON to power on partition 0.
Part# Name
----- ---0) Partition 0
Select a partition number: 0
The power state is OFF for Partition 0.
In what state do you want the power? (ON/OFF) ON
Step 6 View the startup of the operating system.

[osssvr-mp] MP:CM> X
[osssvr-mp] MP> CO
After you run the previous commands, waitting for about 10 minutes until the Boot Menu
interface is displayed, as shown in Figure 1-5.
----End

M2000 server.
Issue 03 (2010-12-31)

1-7
M2000
Procedure
Step 3 Log in to the HP rx7640 server as user root and shut it down.
Step 4 Run the following command on the PC to set up the connection between the PC and the iLO 2
MP.
After a successful login, type the user name and password of iLO 2 MP. The default user name
and password are both Admin.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
Step 5 Run the CM command and the system switches to the MP command line mode.
[osssvr-mp] MP> CM
NOTE
l The MP commands are not case sensitive.

l You can press Ctrl+B to return to the main menu.
Step 6 Power off the server partitions.

1.

2.
When the system displays the following prompt, enter R:

T - Cabinet
C - Cell
P - IO Chassis
R - Partition
Select Device: R
3.
When the system displays the following prompt, enter 0 to select the corresponding
partition, and then enter OFF to power off partition 0.
Part# Name
----- ---0) Partition 0
Select a partition number: 0
The power state is ON for Partition 0.
In what state do you want the power? (ON/OFF) OFF
Step 7 Power off the subrack where the server resides.

1.
1-8

Issue 03 (2010-12-31)
M2000
2.
When the system displays the following prompt, enter T:

T - Cabinet
C - Cell
P - IO Chassis
R - Partition
Select Device: T
3.
When the system displays the following prompt, enter OFF to power off the subrack where
the server resides.
The power state is ON for Cabinet 0.
In what state do you want the power? (ON/OFF) OFF
Step 8 Power off the power supply of the disk array.

Option
Description
S2600 disk array
Perform Step 8.1 and Step 8.2.
S3200 disk array or 6140 disk array
Perform Step 8.3 and Step 8.4.
1.
Check whether the I/O activities of the disk arrays are stopped.
NOTE
a. Wait for two minutes. If the LED indicators of all the drives and caches stop blinking, you can
infer that the read and write operations of the disk array are stopped.
b. Check the cache LED on the controller and determine whether any data on the cache needs to be
written to the disk.
c. Ensure that the LEDs of all the drive and caches stop blinking.
2.
Remove the two plugs at the rear of the disk array from the socket.
3.
Check whether the I/O activities of the disk arrays are stopped.
a.
Wait for two minutes. If all the LEDs stop blinking, you can infer that all the data is
written into the disk and that the cache does not hold data. See Figure 1-6
.
Figure 1-6 Disk array (I)
Issue 03 (2010-12-31)

1-9
M2000
1
b.
OFF
ON
Ensure that all the LEDs of all the disk drives at the front of the controller stop blinking.
See Figure 1-7.
Figure 1-7 Disk array (II)
4.
Set the two power switches at the rear of the controller to OFF.
NOTE
Each disk array has two power switches and their directions are opposite.
----End
1-10

Issue 03 (2010-12-31)
M2000
Setting the M2000 Time (SUSE)
About This Chapter

This describes how to set the M2000 time. To enable the M2000 time to meet the time
requirements, you must synchronize the M2000 time with the time of the other M2000 devices
in the Huawei mobile network.
2.1 Time Synchronization Solution for Huawei Mobile Network (SUSE)
This describes the time synchronization solution of Huawei. By using the time synchronization
solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei
mobile network equipment.
2.2 Changing the Date and Time of the M2000 Server (SUSE)
This describes how to modify the date and time of the server. The server time is closely associated
with NE data collection, timing task handling, and database information dump. Therefore, you
must set the server time correctly.
2.3 Changing the Time Zone on the M2000 Server (SUSE)
This describes how to change the time zone on the M2000 server. If a server is used as the NTP
server, the time zone setting must be correct. The local time display, the NTP service, and the
DST can function properly only when the time zone of the NTP server is correct. You can change
the time zone on the M2000 server.
2.4 Modifying the Date, Time, and Time Zone on the M2000 Client
This section describes how to modify the date, time, and time zone on the M2000 client running
the Windows operating system. You can modify the date, time, and time zone on the M2000
client by modifying the date, time, and time zone of the Windows.
2.5 Setting the NTP Service for the M2000 (HP)
This describes how to configure the M2000 server as the NTP client or the intermediate-layer
NTP server according to the NTP solution.
2.6 Setting the DST for the M2000 System (SUSE)
This describes how to set DST for the M2000 system if the local area uses DST. If an NE incurs
DST transition, ensure that the M2000 system can handle the data reported by the NE and that
no reported data is missing.
Issue 03 (2010-12-31)

2-1
M2000
2.1 Time Synchronization Solution for Huawei Mobile

Network (SUSE)
This describes the time synchronization solution of Huawei. By using the time synchronization
solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei
mobile network equipment.
2.1.1 Introduction to Time Synchronization
This section describes the purpose and definition of time synchronization, the elements of the
time synchronization solution, and the impact on system performance and other OM features
after the time synchronization solution is implemented.
2.1.2 Introduction to the NTP/SNTP
This introduces the rationale of time synchronization and the layered architecture of the Network
Time Protocol (NTP) and the Simple Network Time Protocol (SNTP).
2.1.3 Time Synchronization Modes of Mobile Network (SUSE)
This describes the modes of time synchronization and how to deploy the time synchronization
network for the M2000 and NE devices in mobile network.
2.1.1 Introduction to Time Synchronization

This section describes the purpose and definition of time synchronization, the elements of the
time synchronization solution, and the impact on system performance and other OM features
after the time synchronization solution is implemented.
Purpose of Time Synchronization

Time synchronization enables you to synchronize time between the M2000 and other NEs.
The networking mode of a mobile network is complex if the mobile network has multiple NEs.
The uniform OM mode of NEs in a mobile network requires the time synchronization between
NEs. This ensures that the M2000 correctly manages the alarms and performance data reported
by the NEs.
Inaccurate time may lead to the following scenarios:
l
If the alarm time is inaccurate, the sequence of generated alarms, the interval between alarm
generation and alarm reporting, and the associations between alarms may be misjudged.
When the M2000 collects the statistics of performance data, the statistics are incorrect
owing to inaccurate time.
Therefore, time synchronization enables the system to automatically adjust the OM time of NEs.
Definition of Time Synchronization

Time synchronization is the synchronization of absolute time. The start time of a signal should
be consistent with the universal coordinated time (UTC).
Time synchronization aims to adjust the time of devices according to the received time.
2-2

Issue 03 (2010-12-31)
M2000
Elements of the Time Synchronization Solution

At least two elements are involved in the time synchronization solution, namely, the method of
time synchronization and the choice of time reference sources.
l
In the architecture of the current time synchronization networking, the common method is
to implement time synchronization according to the Network Time Protocol (NTP) and the
Simple Network Time Protocol (SNTP).
Time reference sources aim to provide the standard reference time for the time
synchronization network. This ensures the accuracy of the time reference in the entire
network. A common time reference source is the GPS satellite.
Impact on System Performance

If time synchronization is implemented in client/server mode described in the NTP protocol, the
message frame between the NTP client and the NTP server is 128 bytes. Therefore, time
synchronization does not affect the performance of network transmission. If a great number of
NTP clients request to connect to the NTP server at the same time, these connections consume
mass resources, such as the CPU and the memory of the NTP server. As a result, the performance
of the NTP server is affected.
Therefore, if you use the NTP protocol to construct a time synchronization network, the number
of NTP nodes under an NTP server should not exceed 300. If the number exceeds 300, the
performance of the NTP server may be affected. The interval for the time synchronization request
of an NTP client should be 30 minutes or longer. In addition, you need to reduce the probability
of concurrent requests.
Impact on OM
The time synchronization feature is vital for the OM of the mobile network. It has the following
impacts on the other features:
l
Ensures the accuracy and consistency of the time on the M2000 and NEs in a mobile
network. Time synchronization plays a key role in timely fault reporting, information
accuracy, and fault correlation analysis in fault management. If the NE time is inaccurate
or inconsistent with the M2000 time, a mistake may be made during the fault identification
and handling.
Has a significant impact on the accuracy of log record, query, display, audit, and analysis.
If the time is inaccurate or the time of NEs in the entire network is not the same, the log
record is incorrect and the log audit is also affected.
Has a significant impact on recording, collecting, and analyzing performance data in

performance management. If the time is inaccurate or the time of NEs in the entire network
is not the same, the time of NE performance data records and the dot time may be inaccurate,
and thus may result in invalid performance data.
Has a significant impact on services such as call tracing and problem locating. If the time
is inaccurate or the time of NEs in the entire network is not the same, the call tracing service
may fail.
2.1.2 Introduction to the NTP/SNTP

This introduces the rationale of time synchronization and the layered architecture of the Network
Time Protocol (NTP) and the Simple Network Time Protocol (SNTP).
Issue 03 (2010-12-31)

2-3
M2000
Rationale of NTP Time Synchronization

NTP is used to synchronize the time between the distributed time server and the client. It defines
the structure, algorithm, entity, and protocols in the process of time synchronization. Based on
the IP and UDP stack protocol in the TCP/IP protocols, NTP can also be used by other protocol
groups. Theoretically, the error is less than one nanosecond.
Figure 2-1 shows the rationale of NTP time synchronization.
Figure 2-1 NTP rationale
Device A and device B communicate through the network. Both devices have their own system
time. To implement the automatic synchronization of system clocks, ensure that:
l
Before you synchronize the system time of device A and device B, the time on device A is
set to 10:00:00 and the time on device B is set to 11:00:00.
Device B is configured as the NTP server. That is, you need synchronize the time on device
A with that on device B.
The unidirectional transmission of data package between device A and device B takes one
second.
To synchronize the time between device A and device B, ensure that the following information
is available:
l
Offset, which is the time difference between device A and device B
Delay, which is the loss during the time synchronization between device A and device B
If the previous information is available, device A can easily calculate the time to be adjusted to
synchronize with device B. The NTP protocol stipulates the method for calculating the values
of the offset and delay between device A and device B.
The time synchronization process is as follows:
2-4
1.
Device A sends an NTP message to device B. The message records the stamp of the leaving
time from device A, which is 10:00:00am (T1).
2.
When the NTP message reaches device B, device B adds its own time stamp, which is
11:00:01am (T2).
Issue 03 (2010-12-31)
M2000
3.
When the NTP message leaves device B, device B adds its own time stamp again, which
is 11:00:02am (T3).
4.
When device A receives the response message, it adds a new time stamp, which is
10:00:03am (T4).
After that, device A can calculate the two parameters using the following method:
l
Delay of a NTP message delivering circle: delay = (T4 - T1) - (T3 - T2).
Offset between device A and device B: offset = [(T2 - T1) + (T3 - T4)]/2.
Then, device A can set the time according to this previous information so that device A is
synchronized with device B.
Rationale of NTP Layered Architecture

From the origin and purpose of the time synchronization mechanism, fewer clock sources
enables more uniform time. If a network has a large scale and is very complex, it is timeconsuming to connect each device to the same time server if the time of each device needs to be
synchronized. In this case, the layered architecture is applied to the NTP model.
Theoretically, the time synchronization network can be classified into 16 levels from 0 to 15, or
more than 16 levels on the basis of accuracy and importance. In practice, the number of levels
does not exceed six.
The device at level 0 is located at the special position of the subnetwork. It provides the reference
clock for time synchronization. On the top of the subnet, the device at level 0 uses UTC time
codes broadcast by the global positioning system (GPS).
The devices in the subnet can play multiple roles. For example, a device on the second layer
may be a client to the first layer and a server for the third layer.
Figure 2-2 NTP layered architecture
As shown in Figure 2-2, the following servers are configured in the NTP layered architecture:
l
Issue 03 (2010-12-31)
Top level NTP server: level 0 NTP server, which provides the synchronization service for
lower level servers (Stratum-1).
2-5
M2000
Medium level NTP server: level 1 and level 2 servers, which acquires time from the upper
level server and provides the time for the lower level servers.
NTP client: acquires time from upper level NTP server but does not provide time service.
A host can acquire time from multiple NTP servers. An NTP server can also provide time for
multiple hosts. Hosts on the same level can exchange time. The NTP protocol supports a
maximum of 15 clients.
NOTE
Port 123 is used by NTP during communication through the User Datagram Protocol (UDP). Ensure that
all the IP links between the nodes are functional.
Comparison of SNTP and NTP

SNTP is a simplified policy for the NTP server and the NTP client. The difference between
SNTP and NTP is that SNTP has disadvantage over the following aspects:
l
Handling errors
Filtering of multiple servers
Choosing among multiple clock sources, that is, acquiring the most accurate clock resource
after using an algorithm to analyze multiple connected NTP servers.
2.1.3 Time Synchronization Modes of Mobile Network (SUSE)

This describes the modes of time synchronization and how to deploy the time synchronization
network for the M2000 and NE devices in mobile network.
Time Synchronization Modes of the M2000

The time synchronization of a mobile network is implemented through the NTP/SNTP protocols.
The M2000 uses the SUSE operating system and supports the NTP features based on the NTPV3
protocol. By setting the parameters in the file /etc/ntp.conf on the SUSE operating system, you
can set the M2000 server as an NTP client in the mobile network. After you specify the IP address
of the NTP server for the login of the M2000 server, the M2000 server can obtain the time
synchronization information from the specified NTP server.
The M2000 client runs on the Windows 2000 Professional or Windows XP operating system.
You need to configure the operating system to support the SNTP client and specify the IP address
of the NTP server. Then, the M2000 client can obtain the time synchronization information from
the specified NTP server.
NOTE
The upper-level time servers of the M2000 server and the administration console require to use the NTP
protocol. The server running the Windows operating system uses the SNTP protocol, and thus it cannot
function as the upper-level time server of the M2000 server and the administration console.
Time Synchronization Modes of NEs
2-6
For an NE with the Back Administrator Module (BAM), the NE time synchronization
follows the master/slave networking mode, that is, the host time synchronizes with the
BAM and the BAM synchronizes with the NTP server.
For an NE without the BAM, the Operate & Maintenance (OM) board needs to support the
NTP protocol so that the NE can synchronize with the NTP server.
Issue 03 (2010-12-31)
M2000
This takes the RAN as an example:

l
Rationale of time synchronization for the RAN device
Figure 2-3 Schematic diagram of time synchronization for the RAN device
The active BAM of the RAN device serves as the NTP client to synchronize the time on
each NE node and each module of the RAN device, as shown in Figure 2-3. After the active
BAM of the RAN device obtains the reference time from the specified NTP server, the
BAM delivers the time to each module of the RAN device and all NodeBs to realize time
synchronization.
l
The RNC BAM synchronizes the time on the upper-layer NTP server.
The RNC has two BAM servers: an active BAM server and a standby BAM server. In the
BAM program of the RNC, an NTP client process automatically starts following the BAM
program and always runs on the active BAM server.
By running MML commands, you can specify the upper-layer NTP server as the active
BAM server of the RNC. Then, the NTP client process running on the active BAM
automatically obtains the time synchronization information from the specified NTP server.
Up to 16 NTP server addresses can be specified for the active BAM. The active BAM of
the RNC can perform the synchronization from the preferred time source. If an NTP time
source does not work properly, the active BAM can use a new NTP time source to ensure
the continuity of the NTP service.
When the BAM of the RNC experiences active and standby switching, the NTP client
process is automatically switched to the new active BAM to ensure the continuity of the
NTP service.
Issue 03 (2010-12-31)

2-7
M2000
Time synchronization for each internal module of the RNC

In addition to running the NTP client to synchronize with the external time sources, the
active BAM of the RNC has an SNTP server module for time synchronization between the
internal modules.
For the RNC, each internal module has an independent process serving as the SNTP client.
The active BAM of the RNC serves as the SNTP server of all the modules.
By running the MML commands, you can configure the SNTP server attributes for the
active BAM of the RNC.
Time synchronization for the standby BAM of the RNC

If the active and standby BAMs are operational, only the active BAM has the SNTP server,
and the SNTP client on the standby BAM is used only to periodically synchronize the time
with the active BAM. That is, when the active and standby BAMs are operational, the time
of the active BAM is regarded as the reference time.
During the time synchronization of the active and standby BAMs, the SNTP client of the
standby BAM requests for time synchronization, the SNTP server of the active BAM
returns a response message. Then, the standby BAM adjusts the time of the applications
and the system based on the response message.
The time synchronization of the active and standby BAMs is performed every five minutes.
Manual setting of the period is not required because the active and standby BAMs work as
a single entity to provide services.
NodeB synchronizes the time on the BAM of the RNC.

The SNTP server of the active BAM provides both the time synchronization service and
the time comparison service for the NodeB. The SNTP server of the active BAM
periodically broadcasts time synchronization messages to the NodeB and receives the
requests for time synchronization from the NodeB.
Each NodeB runs a SNTP process to setup a synchronization request to the active BAM of
the RNC.
Network of NTP Time Synchronization

The NTP time synchronization network determines the reference time for the network and uses
the reference time to specify how device nodes communicate with each other.
This part takes the RAN as an example to describe how to choose the reference time for the NTP
time synchronization network.
l
Using the NTP server specified by the operator

If the established time synchronization network provides the NTP server that can act as the
reference time source, prefer to use the existing NTP server as the time reference source
of the RAN network.
In this case, the M2000 and the BAM server of the RNC need to directly communicate with
the specified NTP server to obtain standard time signals, as shown in Figure 2-4.
2-8

Issue 03 (2010-12-31)
M2000
Figure 2-4 Directly connecting the RAN and the NTP server
The M2000 server and all the RNCs must directly communicate with the specified time
synchronization server. The NTP server that can serve as the reference time may be
deployed in other subnets. Therefore, the communication between the M2000 and the RNC
may involve the policy of traversing the firewall. In such a case, you need to modify the
configuration of the firewall.
l
Deploying the intermediate-layer NTP server

According to the principle of layered NTP, when constructing a RAN network, you can
deploy a dedicated intermediate-layer NTP server in the RAN-OM network to serve as the
time reference for the internal RAN devices. The intermediate-layer NTP server obtains
the reference time from the upper-layer server, synchronizes its own time, and serves as
the NTP server of the RAN network. In such a case, the intermediate-layer NTP server can
receive the request on time synchronization from the internal NE devices in the RAN, such
as the RNC and the M2000, and provides standard time, as shown in Figure 2-5.
Issue 03 (2010-12-31)

2-9
M2000
Figure 2-5 Networking of the RAN and the intermediate-layer NTP server
Deploying the intermediate-layer NTP server can effectively simplify the structure of the
time synchronization network. It can also prevent too many NEs from directly connecting
the highest layer NTP server, thus reducing the risks to the highest layer NTP server. In
addition, if a firewall exists between the highest layer NTP server and the RAN network,
you need not configure the firewall.
You can use the dedicated BITS SYNCLOCK V5 as the NTP intermediate-layer server of
the RAN network. Complying with the NTP V3 protocols, this device can provide two
channels of NTP service units and lock multiple upper-layer NTP servers to realize NTP
priority. It also provides two channels of NTP service output that are mutually backed up.
2-10

Issue 03 (2010-12-31)
M2000
NOTE
The M2000 server uses the Linux operating system where you can configure the M2000 server as
the intermediate-layer NTP server. With regard to that the time synchronization server for the RAN
network plays a special role and requires the independent and stable operating environment, we
recommends that the M2000 server should not act as the intermediate-layer NTP server for the RAN
network.
Obtaining reference time from the GPS

If the upper-layer time synchronization server that can provide the reference time is not
available, you should deploy the highest-layer NTP server, that is, the NTP server providing
the reference time in the RAN-OM network to ensure the time synchronization. The highest
layer NTP server obtains the reference time from the GPS or other satellite systems and
synchronizes time on all the RAN NEs and the M2000. Figure 2-6 shows the networking
of the RAN to the highest-layer NTP server.
Figure 2-6 Directly connecting the RAN and the highest-layer NTP server
You can use the dedicated BITS SYNCLOCK V5 as the highest-layer NTP server in the
RAN network. Complying with the NTP V3 protocols, this device can provide two channels
Issue 03 (2010-12-31)

2-11
M2000
of the satellite access system and two channels of the NTP service units. It also provides
two channels of NTP service output that are mutually backed up.
NOTE
To improve the reliability of the NTP service, use the following methods:
l
Choose two or more NTP servers that serve as the upper-layer NTP server to provide time reference.
When deploying the upper-layer NTP server for NEs and the M2000, ensure that more than two
channels of the NTP service are available.
If the stratum 1 NTP server is deployed, it obtains reference time directly from the GPS satellite. In
such a case, the stratum 1 NTP server should provide two channels of satellite interfaces.
2.2 Changing the Date and Time of the M2000 Server (SUSE)
This describes how to modify the date and time of the server. The server time is closely associated
with NE data collection, timing task handling, and database information dump. Therefore, you
must set the server time correctly.
Prerequisite
You have logged in to the server as user root.
Context
If the M2000 server acts as the NTP server of network devices, you must update the time of
network devices when changing the time of the M2000 server.
NOTE
Changing the time on the servers results in the change of time at the Linux bottom layer. Thus, all
timers depending on the operating system are reset or invalidated. To avoid the function failures
resulting from invalid timers, stop the M2000 and the Oracle services before you change the server
time. During the period, the performance data and alarm data of the managed NEs cannot be handled
in time. After the M2000 and Oracle services are restored, the M2000 starts the automatic
synchronization function and collects and handles the missing performance data and alarm data from
managed NEs.
If you need to modify both the time zone and the time, modify the time zone first.
When modifying server time, ensure that the new server time does not exceed the validity period of
the license used by the software installed on the server. If the new server time exceeds the validity
period, some services may be disabled.
Procedure
Step 1 Check the system date and time.
# date
If the system date and time are incorrect, perform the following steps to modify the date and
time:
2-12

Issue 03 (2010-12-31)
M2000
Step 4 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.
Step 5 Check the system date and time again.

# date
If the system date and time are incorrect, perform Step 4 to modify the date and time again.
Step 6 For details on how to restart the Oracle services, see 14.2.2 How to Start the Oracle (HP).
Step 7 For details on how to restart the M2000 service, refer to 7.2.3 Starting the M2000 Server
(SUSE).
----End
2.3 Changing the Time Zone on the M2000 Server (SUSE)

Prerequisite
Context
l
You can change the time zone on the M2000 server. Changing the server time zone directly
results in change of the time at the bottom layer of the Linux operating system.
Consequently, all the timers that depend on the operating system are reset or stop
functioning properly. You must stop the M2000 and Oracle services in advance to avoid a
service failure caused by the malfunctioning of timers. During the period, the performance
data and alarm data of the managed NEs cannot be handled in time. After the M2000 and
Oracle services are restored, the M2000 starts the automatic synchronization function and
collects and handles the missing performance data and alarm data from managed NEs.
Procedure
Step 1 You have logged in to the M2000 server as user root.
Step 2 Check the server time zone.
# grep TIMEZONE /etc/sysconfig/clock
Issue 03 (2010-12-31)

2-13
M2000
If the server time zone is incorrect, perform the following steps to correct it.
Services (SUSE). Stop the M2000 services if they are running.
For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services
(SUSE).
Step 5 Run the yast command to change the time zone of the M2000 server in YaST Control
Center.
Step 6 Press Tab and the arrow keys to select system in the left part of YaST Control Center and
select Date and Time in the right part, and then press Enter.
Step 7 Check whether the Region and Time Zone are correct according to the instructions in Time
Zone and Clock Settings. If the two parameters are not set correctly, press Tab and the arrow
keys to select the correct time zone. Press Tab to select Accept. Then, press Enter.
Step 8 Run the following command to restart the server.
# /sbin/shutdown -y -g0 -i6
The Oracle and M2000 services automatically start after the operating system is restarted.
----End
2.4 Modifying the Date, Time, and Time Zone on the

M2000 Client
Prerequisite
The Windows operating system is operational.
Procedure
Step 1 Open the Control Panel.
This section takes the Windows XP operating system as an example.
Step 2 Double-click Date and Time.
Step 3 In the Date and Time Properties dialog box, select the items to be modified.
2-14

Issue 03 (2010-12-31)
M2000
Item
Operation
Hour
Set the required hour on the Time tab page.
Minute
Set the required minute on the Time tab page.
Second
Set the required second on the Time tab page.
Time Zone Click the Time Zone tab. On the Time Zone tab page, choose the local time zone
from the drop-down list.
Step 4 Click Apply.
----End
2.5 Setting the NTP Service for the M2000 (HP)

This describes how to configure the M2000 server as the NTP client or the intermediate-layer
NTP server according to the NTP solution.
2.5.1 Policies for Configuring the NTP Service on the M2000 Server
This section describes the policies for configuring the NTP service for the M2000 system.
2.5.2 Checking the Time Settings on the M2000 Server (SUSE)
This describes how to check the time settings of the M2000 server. Before configuring the NTP
service, ensure that the time zone, date, and time are correctly set on the M2000 server.
2.5.3 Setting the M2000 Server as the NTP Client (HP)
This describes how to set the M2000 server as the NTP client and synchronize the time with the
upper-level server.
2.5.4 Setting the M2000 Server as the Intermediate-Layer NTP Server (HP)
This section describes how to set the M2000 server as an intermediate-layer NTP server. An
intermediate-layer NTP server synchronizes time with the upper-layer NTP server, and provides
time reference for NTP clients.
2.5.5 Checking the Running Status of the NTP Service on the M2000 Server (SUSE)
This describes how to check the running status of the NTP service on the M2000 server.
2.5.6 Setting the NTP Service on the M2000 Client
This section describes how to set the M2000 client as the NTP client. This task enables you to
synchronize the client with the NTP server through the NTP service of the Windows operating
system.
2.5.1 Policies for Configuring the NTP Service on the M2000 Server
This section describes the policies for configuring the NTP service for the M2000 system.
The M2000 provides two policies for configuring the NTP service, as shown in Table 2-1. Table
2-2 describes the advantages and disadvantages of each policy.
Issue 03 (2010-12-31)

2-15
M2000
Table 2-1 Policies for configuring the NTP service

Policy
Reference
Set the M2000 server as an NTP client.
2.5.3 Setting the M2000 Server as the NTP

Client (HP)
Set the M2000 server as an intermediatelayer NTP server.
2.5.4 Setting the M2000 Server as the

Intermediate-Layer NTP Server (HP)
Table 2-2 Advantages and disadvantages of the two configuration policies

Policy
Reliability
Security
System
Resource Usage
Cost
Policy
1: set the
M2000
server as
an NTP
client.
An independent
intermediatelayer NTP server
is deployed and
running stably.
The M2000 server

is set as an NTP
client, and
synchronizes time
with the
intermediatelayer NTP server.
This policy
enhances the
security of the
time
synchronization
network.
The M2000 server

synchronizes time
with the upperlayer NTP server,
but does not
provide time
reference for NTP
clients. In
comparison to
policy 2, this
policy requires
less system
resources.
This policy is
expensive
because you have
to deploy an
independent
Policy
2: set the
M2000
server as
an
interme
diatelayer
NTP
server.
The M2000 server

performs
maintenance,
upgrade, and
backup operations
frequently. When
the M2000 server
is set as an
intermediatelayer NTP server,
its service
reliability is
affected.
When the M2000

server becomes
faulty, the NTP
service is affected.
As a result, the
security of the
time
synchronization
network is
reduced.
The M2000 server

synchronizes time
with the upperlayer NTP server,
and provides time
reference for NTP
clients. In
comparison to
policy 1, this
policy requires
more system
resources.
This policy is
economical
because the
M2000 server also
serves as an
2.5.2 Checking the Time Settings on the M2000 Server (SUSE)

This describes how to check the time settings of the M2000 server. Before configuring the NTP
service, ensure that the time zone, date, and time are correctly set on the M2000 server.
2-16

Issue 03 (2010-12-31)
M2000
Procedure
Step 1 Check the time zone on the server. If the time zone is incorrect, adjust the time zone of the
M2000 server by referring to 2.3 Changing the Time Zone on the M2000 Server (SUSE).
Step 2 Check the date and time on the server.
# date
If the date is incorrect or the time of the server is incorrect with a deviation of more than two
minutes, change the date and time by referring to 2.2 Changing the Date and Time of the
M2000 Server (SUSE).
----End
2.5.3 Setting the M2000 Server as the NTP Client (HP)

This describes how to set the M2000 server as the NTP client and synchronize the time with the
upper-level server.
Prerequisite
l
The time zone, date, and time of the M2000 server are set correctly.
You have obtained the IP address of the NTP server.
Procedure
Step 1 Check whether the M2000 services are started by referring to 7.2.2 Viewing the Running Status
of M2000 Services (SUSE). If the M2000 services are running, stop them.
(SUSE).
Step 2 Check whether the Oracle services are started by referring to 14.2.1 How to Check Whether
the Oracle Is Started (HP). If the Oracle services are running, stop them.
For details about how to stop the Oracle services, see 14.2.3 How to Stop the Oracle (HP).
Step 3 Run the following command to open the yast interface:
# yast
Step 4 On the YaST Control Center interface, use and to select Network Services.
Step 5 On the YaST Control Center interface, use Tab, , and to select NTP Configuration, and
then press Enter.
Step 6 Use Tab, , and to select During Boot on Automatically Start NTP Daemon. Press
Enter for confirmation.
NOTE
When the Warning dialog box is displayed, use the Tab key to select Continue and then press Enter.
This warning does not affect the setting of NTP Client.
Step 7 On the NTP Server Configuration interface, use Tab to enter the IP address of the NTP server
in Address. Use Tab to select Test to test the settings of NTP. For details, see Figure 2-7.
Issue 03 (2010-12-31)

2-17
M2000
l When the system displays Server is unreachable or does not respond

properly., you can infer that the setting is not successful.
l When the system displays Server is reachable and responds
properly.,you can infer that the setting is successful.
Figure 2-7 Configuring the NTP client
Step 8 Use Tab to select Finish for completing the configuration of the NTP client.
Step 9 Use Tab to select Quit to exit the system.
Step 10 Run the following command to synchronize the clock time with the upper-level server.
# ntpdate NTP Server IP Address
Step 11 Restart the Oracle services.
For details about how to start the Oracle services, see 14.2.2 How to Start the Oracle (HP).
Step 12 Restart the M2000 services.
For details about how to start the M2000 services, see 7.2.3 Starting the M2000 Server
(SUSE).
Step 13 Run the following command to check the system date and time.
# date
If the system date and time are incorrect, contact Huawei technical support engineers for
assistance.
----End
2.5.4 Setting the M2000 Server as the Intermediate-Layer NTP

Server (HP)
This section describes how to set the M2000 server as an intermediate-layer NTP server. An
intermediate-layer NTP server synchronizes time with the upper-layer NTP server, and provides
time reference for NTP clients.
Prerequisite
2-18
The top-layer NTP server has been configured, and the IP address of the top-layer NTP
server has been obtained.
The time zone, date, and time of the M2000 server are set correctly.
You have logged in to the M2000 server in SSH mode as user root using the PuTTY.
Issue 03 (2010-12-31)
M2000
Context
The NTP server for the M2000 server uses the NTP. A server running on the Windows operating
system uses the SNTP. Therefore, it cannot serve as the NTP server for the M2000 server.
Procedure
Step 1 Check whether the M2000 services are started by referring to 7.2.2 Viewing the Running Status
of M2000 Services (SUSE). If the M2000 services are running, stop them.
(SUSE).
Step 2 Check whether the Oracle services are started by referring to 14.2.1 How to Check Whether
the Oracle Is Started (HP). If the Oracle services are running, stop them.
For details about how to stop the Oracle services, see 14.2.3 How to Stop the Oracle (HP).
Step 3 Run the following commands to back up the ntp.conf file:
# cd /etc
# mv ntp.conf bak.ntp.conf
Step 4 Switch to the YaST Control Center window, and then configure the M2000 server as an
intermediate-layer NTP server.
1.
Run the following command to switch to the YaST Control Center window:
# yast
2.
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 then press Enter.
4.
Use Tab and or to choose During Boot under Automatically Start NTP
Daemon, and then press Enter.
NOTE
If the Warning dialog box is displayed, press Tab to choose Continue, and then press Enter. This
warning does not affect the settings of the intermediate-layer NTP server.
5.
Use the Tab key to select Advanced Configuration, and then press Enter.
6.
Use the Tab key to select Add, and then press Enter.
7.
Use the Tab key to select Server, and then press Enter. If Server is selected, skip this
step.
8.
Use the Tab key to select Next, and then press Enter.
9.
Use the Tab key to select Address, and then enter the IP address of the highest-level NTP
server in Address.
10. Use the Tab key to select Test to check whether the entered IP address is available.
l If the system displays "Server is unreachable or does not respond
properly. ", it indicates that the entered IP address is unavailable. In such a case,
you need to check whether the IP address of the NTP server is correct and whether
network communication is normal. After troubleshooting, perform this step again.
l If the system displays "Server is reachable and responds properly.
", it indicates that the entered IP address is available.
Issue 03 (2010-12-31)

2-19
M2000
11. Use the Tab key to enter prefer in Options.

NOTE
prefer indicates that the time of the NTP server is synchronized preferentially. If there are multiple
NTP servers, you can set only one of them to prefer.
12. Use the Tab key to select OK, and then press Enter.
NOTE
If there are multiple NTP servers, repeat Step 4.5 through Step 4.12 to set the IP addresses of other
NTP servers.
13. Press Tab to choose Finish, and then press Enter.

14. Press Tab to choose Quit, and then press Enter.
Step 5 Run the following commands to modify the ntp.conf file.
# echo "server 127.127.1.0" >>ntp.conf
# echo "fudge 127.127.1.0" >>ntp.conf
# echo "driftfile /var/lib/ntp/drift/ntp.drift" >>ntp.conf
# echo "logfile /var/log/ntp" >>ntp.conf
Step 6 Run the following command to restart the NTP server for the configuration to take effect:
# /etc/init.d/ntp restart
Shutting down network time protocol daemon (NTPD)
Try to get initial date and time via NTP from 192.168.8.12
Starting network time protocol daemon (NTPD)
done
done
done
CAUTION
This process takes about 10 minutes. Please wait 10 minutes, and then proceed to the follow-up
steps.
Step 7 Restart the Oracle services.
For details about how to start the Oracle services, see 14.2.2 How to Start the Oracle (HP).
Step 8 Restart the M2000 services.
For details about how to start the M2000 services, see 7.2.3 Starting the M2000 Server
(SUSE).
Step 9 Run the following command to check the status of the NTP service on the M2000 server:
# /usr/sbin/ntpq -p
remote
refid
st t when poll reach
delay
offset jitter
==============================================================================
*192.168.8.12
.LCL.
1 u
29
64 177
0.240
0.093
1.222
LOCAL(0)
.LOCL.
5 l
26
64 177
0.000
0.000
0.001
l The value of remote indicates the IP address and status of an NTP server.
In the preceding output, 192.168.8.12 indicates the IP address of the top-layer NTP server,
and * indicates that the top-layer NTP server is in normal state.
2-20

Issue 03 (2010-12-31)
M2000
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 10 Run the following command to check the time synchronization path from the M2000 server to
the top-layer NTP server:
# /usr/sbin/ntptrace
localhost: stratum 6, offset 0.000000, synch distance 0.950193
192.168.8.12: stratum 1, offset 0.000000, synch distance 0.010010, refid 'LCL
The localhost line and the next line indicate the path from the M2000 server (intermediate-layer
NTP server) to the top-layer NTP server. The system can track the entire NTP synchronization
path from the M2000 server (intermediate-layer NTP server) to the top-layer NTP server.
For example, localhost: stratum 6 in the preceding output indicates that the M2000 server is
on layer 6, and 192.168.8.12: stratum 1 indicates that 192.168.8.12 is on layer 1.
Step 11 Run the following command to check the system date and time.
# date
If the system date and time are incorrect, contact Huawei technical support engineers for
assistance.
----End
Follow-up Procedure
After the server is set as an intermediate NTP server, set the NEs as NTP clients. For details
about how set an NE as an NTP client, see the user guide of the corresponding NE type.
2.5.5 Checking the Running Status of the NTP Service on the

M2000 Server (SUSE)
This describes how to check the running status of the NTP service on the M2000 server.
Prerequisite
Procedure
Step 1 Run the following command to check the status of NTP:
# ps -ef|grep ntp|grep -v grep
ntp
32038
1 0 21:34 ?
00:00:00 /usr/sbin/ntpd -p
/var/lib/ntp/var/run/ntp/ntpd.pid -u ntp -i /var/lib/ntp
If the command output contains ntpd, you can infer that the NTP service is running on the
M2000 server.
----End
Issue 03 (2010-12-31)

2-21
M2000

system.
Prerequisite
l
You have logged in to the Windows operating system. The Windows operating system is
running properly.
The M2000 client and the M2000 server communicate normally.
The clock source of the server is operational.
Context
When the M2000 client is configured as the NTP client, synchronize the time of the M2000
client with the time of the M2000 server.
The configuration procedure is applicable to the Windows 2000 Professional, Windows 2003,
Windows 2008, Windows XP Professional or Windows Vista Business operating system.
Procedure
Step 1 Configure the M2000 client as the NTP client.
Choose Start > Run. In the displayed Run dialog box, enter regedit to open the Registry
Editor window.
In the registry, choose HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet >
Services > W32Time > Parameters. Then, change the value of the parameter LocalNTP to
0, which is the default value. If the parameter LocalNTP does not exist, it indicates that the
value can be ignored and the registry need not be modified.
NOTE
For the operating systems of Windows 2003 or Windows 2008, In the registry, change the value of
Enable under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services >
W32Time > TimeProviders > NtpServer to 0.
Step 2 Specify the NTP clock source.

Choose Start > Run. Type cmd and press Enter.
In the displayed window, run the following command:
c:\>net time /setsntp: IP Address of M2000 Server
NOTE
1. The result of the net time command is saved in the Windows registry. This setting of the net time takes
effect after Windows restarts.
2. To clear the specification, run the net time /setsntp command.
Step 3 Restart the Windows Time service.

Choose Start > Run. In the displayed Run dialog box, enter services.msc to open the
Services window. Identify the Windows Time service and restart the service.
2-22

Issue 03 (2010-12-31)
M2000
Step 4 Check the NTP server specified by the PC.

c:\>net time /querysntp
NOTE
If the host name and IP address of the PC are specified as the host name and IP address of the NTP server
by /setsntp, the NTP server time is the local time of the PC.
Step 5 Perform operations based on operating systems.

l If the M2000 client runs on Windows 2000 operating system, perform Step Step 6.
l If the M2000 client runs on Windows 2003, Windows 2008, Windows XP or Windows Vista
operating system, perform Step Step 7 through Step Step 8.
Step 6 Run the following command to check the running status of the SNTP:
c:\>w32tm -once -v -test
The system displays the host name of the connected NTP server, deviation between the local
time and the NTP server time, and time cycle of NTP server roll.
Step 7 Run the following command to manually synchronize the time:
c:\>w32tm /resync
c:\>w32tm /stripchart /computer:IP address of the M2000 server /dataonly
The system displays the following information, including the local time of the client and
deviation of the local time from that 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.9881239s
10:05:11, +04.9814570s
10:05:13, +04.9740897s
10:05:15, +04.9589559s
10:05:17, +04.9449507s
...
In the system output, the first column displays the local time of the client, and the second column
displays the deviation between the local time and the server time. + indicates that the client time
is earlier than the server time. - indicates that the client time is later than the server time. You
can press Ctrl+C to exit the browse window.
----End
2.6 Setting the DST for the M2000 System (SUSE)

This describes how to set DST for the M2000 system if the local area uses DST. If an NE incurs
DST transition, ensure that the M2000 system can handle the data reported by the NE and that
no reported data is missing.
2.6.1 Introduction to the DST
This section describes the daylight saving time (DST) and the DST impact on the M2000 system.
2.6.2 Viewing the DST Rules of a Time Zone
This describes how to view the DST rules of a time zone. As the local government may adjust
the DST rules owing to various reasons, you must query the DST rules of the corresponding
Issue 03 (2010-12-31)

2-23
M2000
time zone based on the time zone name before setting DST. This ensures that the DST rules
defined by the time zone name are consistent with the actual DST rules.
2.6.3 Changing the Time Zone on the M2000 Server (SUSE)
2.6.1 Introduction to the DST

This section describes the daylight saving time (DST) and the DST impact on the M2000 system.
Introduction
The DST is one hour earlier than the standard time. For example, during the DST, 10:00 am in
US east standard time is 11:00 am in US east DST.
Impact on the M2000 System

l
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. The
M2000 log management and trace management uses the local time. Therefore, one-hour
records are missing in trace files.
When the DST ends, generally one hour is automatically reduced from the local time of
the operating system. This change does not affect the system clock. Thus, time storage and
exchange are not affected. This change, however, affects the time display. During the
operation of the M2000, some modules in the M2000 generate some files whose names are
identified by time stamps. When the DST ends, files that are generated later overwrite the
earlier ones.
NOTE
The local time is the time displayed on the computer. It varies according to the time zone.
The system clock indicates the GMT. The NTP synchronization uses the GMT, which does not affect
the local time. The DST does not affect the NTP service.
2.6.2 Viewing the DST Rules of a Time Zone

This describes how to view the DST rules of a time zone. As the local government may adjust
the DST rules owing to various reasons, you must query the DST rules of the corresponding
time zone based on the time zone name before setting DST. This ensures that the DST rules
defined by the time zone name are consistent with the actual DST rules.
Prerequisite
Context
On the Linux operating system, two formats are available for the time zone: GMT and time zone
name. The GMT format stipulates only time offset rather than the DST rules. The time zone
name format stipulates the time offset and the DST rules, depending on time zones.
2-24

Issue 03 (2010-12-31)
M2000
The GMT format can be used by the countries and districts that do not use DST. The time zone
name format must be used by the countries and districts that use DST. Otherwise, the operating
system does not support the automatic time system change.
Procedure
Step 1 Query the local time zone name.
For details on how to query time zone names, refer to 14.1.7 How to Query a Time Zone Name
(SUSE).
Step 2 Run the following command to view the rules:
# zdump -v time zone name | grep the specified year
l When the specified year refers to the current year:
If DST is not used, only a line of information is displayed. If DST is used, the five lines
of information is displayed for describing the DST rules.
The format of the displayed information is as follows:
Time zone name
UTC time = local time
isdst=0/1
The UTC time refers to GMT.

isdst=0 stands for being not in the DST period. isdst=1 stands for being in the DST
period.
l When the specified year does not refer to the current year:
If DST is used, the four lines of information is displayed for describing the DST rules. If
the displayed information does not have four lines, you can infer that DST is not used.
The format of the displayed information is as follows:
Time zone name
UTC time = local time
isdst=0/1
The UTC time refers to GMT.

isdst=0 stands for being not in the DST period. isdst=1 stands for being in the DST
period.
NOTE
l If you do not add | grep the specified year to the previous command, the system displays all time zone
rules of the time zone.
l The DST rules stipulate the day, week, and month when the DST starts and ends in each year. This
means that the week when DST is enabled is fixed and that the date when DST is enabled is flexible.
For example, DST in the time zone US/Alaska starts from the second Sunday of March and ends in
the first Sunday of November in each year.
l Use the zdump command to query the DST rules in the three successive years, that is, the last year,
this year, and the next year. Based on the command result, you can infer the universal rules of DST
jump.
----End
Example
l
To query the DST rules used by PRC in 2007, run the following command:
# zdump -v PRC|grep 2007
If the current year is 2007,
the system displays only one piece of echo information that is similar with the following
message:
Issue 03 (2010-12-31)

2-25
M2000

PRC
Mon Sep 17 06:03:55 2007 UTC = Mon Sep 17 14:03:55 2007 CST isdst=0
If the current year is not 2007,

the system does not display echo information.
Therefore, the PRC time zone does not have DST in 2007.
l
To query the DST rules used by US/Alaska in 2007, run the following command:
# zdump -v US/Alaska|grep 2007
If the current year is 2007,
the command results are similar with the following information:
US/Alaska
isdst=1
US/Alaska
isdst=0
US/Alaska
isdst=1
US/Alaska
isdst=1
US/Alaska
isdst=0
Mon Sep 17 06:09:56 2007 UTC = Sun Sep 16 22:09:56 2007 AKDT
Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST
Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT
Sun Nov
4 09:59:59 2007 UTC = Sun Nov
4 01:59:59 2007 AKDT
Sun Nov
4 10:00:00 2007 UTC = Sun Nov
4 01:00:00 2007 AKST
Based on the fact that the first line of the command result contains isdst=1, you
can infer that DST is used in US/Alaska. DST is being used. The local time, that is,
the DST time, is Sep 16 22:09:56 2007. The UTC time is Sep 17
06:09:56 2007.
Based on the information in the second line and the third line, you can infer that DST
starts after Mar 11 02:00:00 2007 is changed to Mar 11 03:00:00
2007.
Based on the information in the fourth line and the fifth line, you can infer that DST
ends after Nov 4 02:00:00 2007 is changed to Nov 4 01:00:00.
If the current year is not 2007,
The system displays the following information:
US/Alaska
isdst=0
US/Alaska
isdst=1
US/Alaska
isdst=1
US/Alaska
isdst=0
Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST
Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT
Sun Nov
4 09:59:59 2007 UTC = Sun Nov
4 01:59:59 2007 AKDT
Sun Nov
4 10:00:00 2007 UTC = Sun Nov
4 01:00:00 2007 AKST
Based on the information in the first line and the second line, you can infer that DST
starts after Mar 11 02:00:00 2007 is changed to Mar 11 03:00:00
2007.
Based on the information in the third line and the fourth line, you can infer that DST
ends after Nov 4 02:00:00 2007 is changed to Nov 4 01:00:00.
2.6.3 Changing the Time Zone on the M2000 Server (SUSE)

Prerequisite
2-26

Issue 03 (2010-12-31)
M2000
Context
l
You can change the time zone on the M2000 server. Changing the server time zone directly
results in change of the time at the bottom layer of the Linux operating system.
Consequently, all the timers that depend on the operating system are reset or stop
functioning properly. You must stop the M2000 and Oracle services in advance to avoid a
service failure caused by the malfunctioning of timers. During the period, the performance
data and alarm data of the managed NEs cannot be handled in time. After the M2000 and
Oracle services are restored, the M2000 starts the automatic synchronization function and
collects and handles the missing performance data and alarm data from managed NEs.
Procedure
Step 1 You have logged in to the M2000 server as user root.
Step 2 Check the server time zone.
# grep TIMEZONE /etc/sysconfig/clock
If the server time zone is incorrect, perform the following steps to correct it.
Services (SUSE). Stop the M2000 services if they are running.
(SUSE).
Step 5 Run the yast command to change the time zone of the M2000 server in YaST Control
Center.
Step 6 Press Tab and the arrow keys to select system in the left part of YaST Control Center and
select Date and Time in the right part, and then press Enter.
Step 7 Check whether the Region and Time Zone are correct according to the instructions in Time
Zone and Clock Settings. If the two parameters are not set correctly, press Tab and the arrow
keys to select the correct time zone. Press Tab to select Accept. Then, press Enter.
Step 8 Run the following command to restart the server.
# /sbin/shutdown -y -g0 -i6
The Oracle and M2000 services automatically start after the operating system is restarted.
----End
Issue 03 (2010-12-31)

2-27
M2000
Configuring the Parameters of the M2000

Server (SUSE)
About This Chapter

This describes how to set the parameters of the M2000 server.
3.1 Changing the Host Name of the M2000 Server (SUSE)
This describes how to change the host name of the M2000 server. During you change the host
name, the M2000 cannot handle the performance data and alarm data of the managed NEs. After
the change, the implements automatic synchronization to collect and handle the missing
performance data and alarm data.
3.2 Adding or Deleting Routes on the M2000 Server (SUSE)
This describes how to add or delete routes on the M2000 server. By adding or deleting routes
on the M2000 server, you can set up or delete the routes from the local network to the target
networks.
3.3 Changing the IP Address of the M2000 Server (SUSE)
This section describes how to change the IP addresses of the M2000 servers to ensure that the
IP addresses of the servers meet the requirements.
3.4 Changing the IP Address of the MP Ethernet Port on the rx7640 Server
This describes how to change the IP address of the MP Ethernet port on the rx7640 server to
ensure that the IP address meets the relevant requirements.
3.5 Changing the IP Address of the S3200 Disk Array (Serial Port Mode)
This section describes how to change the IP address of the S3200 disk array. The disk array is
connected to the server directly through optical fibers. Change of IP addresses does not affect
data read operations on the disk array. Therefore, you are advised to use the factory-delivered
default IP address of the disk array. If the IP address of a disk array needs to be changed, change
the IP address according to the actual requirement.
3.6 Changing the IP Address of the S2600 Disk Array (Serial Port Mode)
This section describes how to change the IP address of an S2600 disk array in serial port mode.
IP address changes of a disk array have no impact on data transfer between the server and the
disk array. You are recommended to keep the default IP addresses. If you have to change the IP
addresses, change them as required. The IP addresses of each S2600 disk array must be changed.
Issue 03 (2010-12-31)

3-1
M2000
3.1 Changing the Host Name of the M2000 Server (SUSE)

This describes how to change the host name of the M2000 server. During you change the host
name, the M2000 cannot handle the performance data and alarm data of the managed NEs. After
the change, the implements automatic synchronization to collect and handle the missing
performance data and alarm data.
Prerequisite
The M2000 server applications are installed.
Procedure
Step 1 Log in as user root. Check the host name of the server.
# hostname
If the host name is incorrect, perform the following steps:
Step 4 Modify the /etc/HOSTNAME file to change the existing host name to a new one.
# vi /etc/HOSTNAME
The related fields in the file are:
host name
The modified content is as follows:

osssvr
Then, press Esc and run the :wq! command to save the modification and exit.
Step 5 Modify the /etc/hosts file to change the existing host name to a new one.
# vi /etc/hosts
The related fields in the file are:
IP address host name host name
The modified content is as follows:

192.168.8.11
osssvr osssvr
Step 6 Switch to user oracle.
# su - oracle
3-2

Issue 03 (2010-12-31)
M2000
Step 7 View the /opt/oracle/oradb/home/network/admin/listener.ora file.

~> vi /opt/oracle/oradb/home/network/admin/listener.ora
l If the file records the host name information, replace the existing host name with a new one.
l If the file does not record the host name information, do not modify the file. Press Esc and
run the :q! command to exit.
Step 8 View the /opt/oracle/oradb/home/network/admin/tnsnames.ora file.
~> vi /opt/oracle/oradb/home/network/admin/tnsnames.ora
l If the file records the host name information, replace the existing host name with a new one.
l If the file does not record the host name information, do not modify the file. Press Esc and
run the :q! command to exit.
Step 9 Switch to user root.
~> su - root
Password: Enter the password of user root.
Step 10 Restart the server.
After the server is restarted, both the Oracle and M2000 services are automatically restarted.
Step 11 Check whether the M2000 service is running. For details, see 7.2.2 Viewing the Running Status
of M2000 Services (SUSE). If the M2000 is not running, start the M2000 service. For details,
see 7.2.3 Starting the M2000 Server (SUSE).
Step 12 Check whether the Oracle service is running. For details, see 14.2.1 How to Check Whether
the Oracle Is Started (HP). If the Oracle is not running, start the Oracle service. For details,
see 14.2.2 How to Start the Oracle (HP).
----End
3.2 Adding or Deleting Routes on the M2000 Server (SUSE)

This describes how to add or delete routes on the M2000 server. By adding or deleting routes
on the M2000 server, you can set up or delete the routes from the local network to the target
networks.
Prerequisite
Procedure
Step 1 Table 3-1 describes how to add, delete, view, or automatically add a M2000 server route.
Issue 03 (2010-12-31)

3-3
M2000
Table 3-1 Adding or deleting a route

Operation
Command
Example
Adding a route
# route add [-net|-host] target

[netmask Nm] [gw Gw] [[dev] If]
# route add -net 192.168.2.128

netmask 255.255.255.128 gw
192.168.2.129
Deleting a
route
# route [-v] [-A family] del [-net|host] target [gw] [netmask] [metric
N] [[dev] If]
# route del -net 192.168.2.128

netmask 255.255.255.128
Viewing a
route
# netstat -r -anv
After each
restart, new
route
information is
automatically
added to the
M2000.
1. Back up the /etc/sysconfig/

network/routes file:
Write the following information

to the /etc/sysconfig/network/
routes file:
# cp /etc/sysconfig/network/
routes /etc/sysconfig/network/
routes.bak
2. Edit the /etc/sysconfig/network/
routes file. Add one or multiple
network segment gateway subnet
mask eth-id-MAC records.
172.16.89.0 147.2.212.58
255.255.255.0 eth-id-00:18:8b:
88:94:5f
Only a record can be added to each

line.
3. Save the file and quit.
NOTE
For a detailed parameter description of the route command, see route Command (SUSE).
----End
3.3 Changing the IP Address of the M2000 Server (SUSE)

This section describes how to change the IP addresses of the M2000 servers to ensure that the
IP addresses of the servers meet the requirements.
Prerequisite
The M2000 server application is installed.
Context
3-4
When you are changing the IP addresses of the M2000 servers, the performance data and
alarm data of the managed NEs cannot be processed.
After you change the IP addresses of the servers, the M2000 collects performance data and
alarm data again through automatic synchronization and then processes the data.
If the IP addresses of the M2000 servers are recorded in the NE database, changing the IP
address of an M2000 server leads to the disconnection between the M2000 server and the
NEs. When changing the IP addresses of the M2000 servers, you need to notify the NE
Issue 03 (2010-12-31)
M2000
maintenance engineers and ask them to modify relevant plans and update the IP addresses
of the M2000 servers recorded in the NE database.
Procedure
Step 1 You have logged in to the server as user root.
Check whether the IP address is
available. If...
Then...
Yes
Log in to the server through the SSH.
No
Log in to the iLO 2 MP serial port on the server

through the HyperTerminal on the PC. For
details, see Step 1.1 through Step 1.7.
1.
Power on the PC terminal and start it.
2.
Choose Start > All Programs (P) > Accessories > Communications >
HyperTerminal.
3.
In the Connection Description dialog box, enter the name of the new connection.
4.
Specify a serial port on the PC to connect with the LOCAL CONSOLE port, for example,
COM1.
5.
Set the properties of the serial port. For details, see Table 3-2. Then, click OK.
Table 3-2 Setting the properties of the serial port
6.
Property
Attribute Value
Bits per second
9600
Data bits
Parity
Null
Stop bits
Flow control
Null
In the HyperTerminal window, enter the default user name Admin and password Admin
of the iLO 2 MP.
NOTE
If the MP prompt for login is not displayed, press Enter several times until the prompt is displayed.
MP login: Admin
MP password: *****
Then, the following message is displayed:

MP>
7.
Issue 03 (2010-12-31)

3-5
M2000
l For the HP rx2660 server, perform the following steps:

a.
Run the following command:

MP> CO
Then, the prompt for login is displayed.
......
Welcome to SUSE Linux Enterprise Server 10 SP1 (ia64) - Kernel
2.6.16.46-0.12-default (console).
osssvr login:
NOTE
If the prompt for login is not displayed, press Enter several times until the prompt is
displayed.
b.
Enter the user name and password of user root. The default user name is root and
the default password is root.
osssvr login: root
Password:
l For the HP rx7640 server, perform the following steps:

a.

MP> CO
b.
When the system displays the following prompt, enter 0:

Partitions available:
#
--0)
Q)
Name
---Partition 0
Quit
Please select partition number: 0
Then, the prompt for login is displayed.

......
Welcome to SUSE Linux Enterprise Server 10 SP1 (ia64) - Kernel
2.6.16.46-0.12-default (console).
osssvr login:
NOTE
If the prompt for login is not displayed, press Enter several times until the prompt is
displayed.
c.
Enter the user name and password of user root. The default user name is root and
the default password is root.
osssvr login: root
Password:
Step 2 Check the IP address of the server.

# ifconfig -a
l For the rx2660 server, in the command result, the IP address of the eth0 network port is the
same as the IP address of the server.
l For the rx7640 server, in the command result, the IP address of the bond0 network port is
the same as the IP address of the server.
3-6

Issue 03 (2010-12-31)
M2000
If the IP address of the server is incorrect, perform the following steps:

Step 3 Check whether the new IP address is already used.
This part takes change the old IP address 192.168.8.11 to the new IP address 10.10.10.10 as an
example.
# ping 10.10.10.10
l If the new IP address can be pinged, you can infer that the new IP address are occupied and
you need to use other new IP address.
l If the new IP address cannot be pinged, you can infer that the new IP address is idle and you
can use the new IP address.
Step 5 Check whether the Oracle is started by referring to 14.2.1 How to Check Whether the Oracle
Is Started (HP). If the Oracle is not started, start it by referring to 14.2.2 How to Start the
Oracle (HP).
Step 6 Perform the following operations to change the IP addresses of the M2000 servers.
1.
Run the modify.sh script.

# . /opt/OMC/svc_profile.sh
# cd /opt/OMC/tools/config
# ./modify.sh
-----------------------------------------------------------------Welcome to use Config tools
Modify Tool (1.1.0)
----------------------------------------------------------------------------------------------------------------------------------Please select a(n) operator type
1--IP
2--Database server name
3--Database password
4--Password of ftpuser
R--Return
Q--Quit
-----------------------------------------------------------------Please make a choice[1-4]:
When the main menu is displayed, choose 1--IP.

2.
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 192.168.8.11]:
Please input the new ip[default 192.168.8.11]: 10.10.10.11
Please input the old ip[default 192.168.8.12]:
-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step
-----------------------------------------------------------------Please input the database superuser's password: emsems
Issue 03 (2010-12-31)

3-7

Please
Please
Please
Please
input
input
input
input
the
the
the
the
old
new
old
new
M2000
mask number[default 255.255.255.0]:

mask number[default 255.255.255.0]:
router ip address[default 192.168.8.1]:
router ip address[default 192.168.8.1]:
NOTE
l If you need to change multiple IP addresses by running the modify.sh script, type all previous
addresses to be changed and their new values here.
l You can press Enter to use the default value in the system output.
l The script displays the IP addresses that are already configured in the system. If you need not
change a certain IP address, press Enter to proceed with the next step.
l You can type p/P to return to the function menu of the modify.sh script. Then, you are prompted
to perform operations such as changing the IP address and changing user password.
l You can type q/Q to exit the modify.sh script.
l When the system prompts you to type the previous IP addresses, type f/F to finish typing IP
addresses and proceed with the next step.
3.
When the system displays the following prompt, type Y, and then press Enter:
Are you sure to continue?
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]: Y
NOTE
l You can type Q to exit the script without performing any operations.
l You can type R to return to the previous step to reconfigure relevant parameters.
l You can type P to return to the function menu of the modify.sh script. Then, you are prompted
to perform operations such as changing the IP address and user password.
l Running the modify.sh script to change the server IP addresses takes about three minutes. Please
wait.
4.
When the system displays the following information, you can infer that the change is
successful.
-----------------------------------------------------------------Operator compelete!
If the system output contains failed, you can infer that the change fails. Contact Huawei
technical support engineers for assistance.
5.
When the system displays the function menu again, type q to exit.
Step 7 Run the following commands to restart the server:

After the server is restarted, both the Oracle and M2000 services are automatically restarted.
Step 8 Log in to the server by using the new IP address as user root, and then check the status of the
Oracle and M2000 services.
3-8

Issue 03 (2010-12-31)
M2000
CAUTION
If the login fails or the Oracle and M2000 services are abnormal after the server is restarted,
contact Huawei for technical support.
l For details about how to view the Oracle service, see 14.2.1 How to Check Whether the
Oracle Is Started (HP).
l For details about how to check the status of the M2000 services, see 7.2.2 Viewing the
Running Status of M2000 Services (SUSE).
----End
Follow-up Procedure
(Optional) If the S2600 disk array is configured and the Trap IP address of the S2600 disk array
is the logical IP address of the service Ethernet port on the server, you need to reconfigure the
monitoring function of the S2600 disk array after changing the IP address of the server. For
details, see 14.3.6 How Do I Configure the Monitoring Function of the S2600 Disk
Array?.
3.4 Changing the IP Address of the MP Ethernet Port on the

rx7640 Server
This describes how to change the IP address of the MP Ethernet port on the rx7640 server to
ensure that the IP address meets the relevant requirements.
Prerequisite
l
The PC communicates with the iL0 2 MP serial port normally.
A new IP address of the MP Ethernet port is planned.
Procedure
Step 1 Run the following command on the PC terminal to establish the connection between the PC and
the MP Ethernet port.
telnet existing IP address of the MP Ethernet port
Step 2 Enter the default user name Admin and password Admin of the iL0 2 MP.
NOTE
If the prompt for login is not displayed, press Enter several times until the prompt is displayed.
MP login: Admin
MP password: *****
If the login is successful, the system displays the following message:

[mp001b78d20747] MP>
NOTE
mp001b78d20747 refers to the MAC address of the iL0 2 MP, which is unique for identifying the iL0
2 MP on the network.
Issue 03 (2010-12-31)

3-9
M2000
Step 3 Switch to the command line mode of the iL0 2 MP.

[mp001b78d20747] MP> CM
NOTE
The MP command is case insensitive. If any error is displayed when you run the command in uppercase,
run the command in lowercase.
Step 4 Navigate to the interface for modifying the MP network parameters.

MP:CM> LC
Step 5 When the system displays the following message, enter 1 to customize the MP network
parameters.
Then, the configuration of the current MP is displayed.
MP Configurable LAN devices:
1 - MP Customer LAN
Enter LAN device to change, or [Q] to Quit:
Step 6 When the system displays the following message, enter Y to confirm that you want to modify
the current network parameters.
Do you want to modify the configuration for the MP LAN? (Y/[N])
Step 7 When the system displays the following message, perform the following operations to prohibit
the DHCP.
Current DHCP Status is: ***
Do you want to modify it? (Y/[N])
If the current DHCP status is Then ...

Enabled
Enter Y to set the DHCP to Disabled.

1. When the system displays the following message, enter
Y to bind the DHCP status.
Toggle DHCP State? (Y/[N])
2. When the system displays the following message, type

Y for confirmation.
New DHCP Status will be: Disabled
Please confirm (Y/[N])
Enter N.
Disabled
Step 8 When the system displays the following message, enter Y to change the IP address of the MP.
Static IP Address is: ***.***.***.***
Step 9 When the system displays the following message, enter the new IP address.
Enter new IP Address :
Step 10 When the system displays the following message, type Y for confirmation.
Step 11 When the system displays the following message, you can configure the host name of the MP.
3-10

Issue 03 (2010-12-31)
M2000
Current MP Network Name is: ***

If the current MP network name
Then ...
Does not meet the actual requirements Enter Y to change the host name of the MP.
1. When the system displays the following
message, enter the new host name of the MP.
Enter new MP Network Name :
2. When the system displays the following

message, type Y for confirmation.
Enter N and do not change the IP address.
Meets the actual requirements
NOTE
The host name of the MP contains a maximum of 64 characters, which consists of a combination of digits,
dashes, underscores, full stops, or spaces.
Step 12 When the system displays the following message, you can configure the subnet mask of the MP.
Static Subnet Mask is: ***.***.***.***
Static Subnet Mask is
Then ...
Not meet the actual requirements Enter Y to change the subnet mask of the MP.
1. When the system displays the following message,
enter the new subnet mask.
Enter new Subnet Mask :

type Y for confirmation.
Meet the actual requirements
Enter N and do not change the subnet mask.
Step 13 When the system displays the following message, you can configure the gateway of the MP.
Static Gateway is: ***.***.***.***
Issue 03 (2010-12-31)

3-11
M2000
Static Gateway is
Then ...
Not meet the actual requirements Enter Y to change the gateway of the MP.
enter the new gateway.
Enter new Gateway :

type Y for confirmation.
Meet the actual requirements
Enter N and do not change the gateway.
Step 14 When the system displays the following message for confirming that the rate of the MP network
interface card is Auto Negotiate, enter N and do not configure the rate.
Current Data Rate is: Auto Negotiate
If the rate of the MP network interface card is not Auto Negotiate, enter Y and then set the
rate of the MP network interface card to auto.
Enter new Data Rate (10M/100M/10MFDX/100MFDX/auto) : auto
New Data Rate will be: Auto Negotiate
Please confirm (Y/[N]) Y
Step 15 Check whether the iL0 2 MP is correctly configured.

MP:CM> LS
Current configuration of MP customer LAN interface
MAC address
: 00:1b:78:d2:07:47
DHCP Status
: Disabled
IP address
: 10.71.10.123
0x0a470a7b
Hostname
: osssvr-mp
Subnet mask
: 255.255.255.0
0xffffff00
Gateway
: 10.71.10.1
0x0a470a01
Status
: UP and RUNNING
Link
: Connected 100Mb Full Duplex
If the configuration items DHCP Status, IP Address, MP Host Name, Subnet

Mask, and Link State are inconsistent with the previous information, go to Step 4 for
reconfiguration.
NOTE
You need not restart the iL0 2 MP to make the new network parameters to take effect after the modification.
Step 16 Exit the iL0 2 MP command line mode.

MP:CM> X
MP>
----End
3-12

Issue 03 (2010-12-31)
M2000
3.5 Changing the IP Address of the S3200 Disk Array (Serial

Port Mode)
This section describes how to change the IP address of the S3200 disk array. The disk array is
connected to the server directly through optical fibers. Change of IP addresses does not affect
data read operations on the disk array. Therefore, you are advised to use the factory-delivered
Context
l
The S3200 disk array has two controllers. Each controller has two Ethernet ports, that is,
if0 and if1. When changing the IP address of a controller, change the IP address of only
Ethernet port if0. The IP address of Ethernet port if1 needs to be reserved for maintenance.
You can change the IP address of a disk array in serial port mode or command mode. The
serial port mode is preferred because it features high success rate in changing IP addresses.
In the case of remote operations, use the command mode. For details, see 14.3.1 How Do
I Change the IP Address of the S3200 Disk Array (Command Mode)?.
Procedure
Step 1 Use the serial port cable to connect the serial port of the controller of the disk array and that of
the PC. Figure 3-1 shows the disk array.
Figure 3-1 Serial ports of the S3X00
NOTE
You must use the serial port cable that is delivered with the disk array rather than the serial port cable of
other devices. The serial port cable delivered with the disk array is designed specifically for the storage
device. If you do not use this serial port, the communication may fail. A DB-9 connector at one end of the
serial port cable is connected to the serial port on the PC. A 6-thread round connector at the other end is
connected to the port of the disk array controller. You need to configure the controller that is connected to
the serial port (Controller A is on the left while controller B is on the right.)
Step 2 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal.
Step 3 In the Connection Description dialog box, enter a name for the new connection.
Step 4 Select the PC serial port used to connect to the disk array, such as COM1.
Issue 03 (2010-12-31)

3-13
M2000
Step 5 Set the properties of the serial port. For details about how to set the properties of a serial port,
see Table 3-3. Then, click OK.
Table 3-3 Setting properties of the serial port
Property
Value
Bits per second
9600/38400
Data bits
Parity
Null
Stop bits
Data stream control
Null
Step 6 Press Ctrl+Break to activate Shell of the serial port.

Step 7 If the following information is displayed in the HyperTerminal window, enter Esc within five
seconds. The Shell Login interface is displayed.
Press within 5 seconds: <S>for Service Interface , <BREAK>for band rate
Step 8 If the following information is displayed, enter the login password infiniti and press Enter to
log in to the disk array and to configure Shell.
Enter password to access shell:
Step 9 Run the following command to check the port configuration of the controller that you have
logged in to.
-> netCfgShow
The system displays the port configuration of the controller, as shown in Figure 3-2.
Figure 3-2 Viewing the port configuration of the controller
3-14

Issue 03 (2010-12-31)
M2000
Table 3-4 shows the main configuration items in Figure 3-2.

Table 3-4 Configuration items of the controller port
Configuration Item
Meaning
IP Address if0
Indicates the IP address of Ethernet port if0

of the controller that you have logged in to.
Subnet Mask if0
Indicates the subnet mask of Ethernet port if0

of the controller.
Gateway IP Address
Indicates the gateway IP address.
l If the port configuration of the controller meets the requirements, you need not perform any
operation.
l If the port configuration of the controller does not meet the requirements, perform the
following operations to change it.
Step 10 Run the following command:
-> netCfgSet
The command result shown in Figure 3-3 is displayed. Press Enter.
Figure 3-3 Port configuration (I)
Step 11 Set the IP address of Ethernet port if0 of the controller.

This takes 192.168.8.39 as an example to describe how to change the IP address of Ethernet port
if0. After typing the new IP address, press Enter, as shown in Figure 3-4.
Figure 3-4 Port configuration (II)
Issue 03 (2010-12-31)

3-15
M2000
NOTE
l If you press Enter directly without entering a new IP address, the IP address is not changed.
l If you need to restore the IP address of Ethernet port if0 to the factory-delivered default setting, enter .
and press Enter.
Step 12 Set the subnet mask of Ethernet port if0 of the controller.
In the displayed information as shown in Figure 3-5, enter a new subnet mask and then press
Enter. If you press Enter directly without entering any data, the subnet mask is not changed. If
you need to restore the subnet mask of Ethernet port if0 to the factory-delivered default setting,
enter . and press Enter.
Figure 3-5 Port configuration (II)
Step 13 The system displays the following information. Press Enter directly without changing the IP
address of Ethernet port if1.
IP Address if1
: 192.168.129.101
Step 14 The system displays the following information. Press Enter directly without changing the subnet
mask of Ethernet port if1.
Subnet Mask if1
: 255.255.255.0
Step 15 The system displays the following information. Press Enter.

Server Host Name

Server IP Address
Step 17 Set the IP address of the gateway.

This takes 192.168.8.39 and 255.255.255.0 respectively as an example to describe how to change
the IP address and subnet mask of Ethernet port if0. Enter 192.168.8.1 as the new gateway IP
address, and then press Enter. See Figure 3-6.
Figure 3-6 Port configuration (IV)
l If you press Enter directly without entering a new gateway IP address, the gateway IP address
is not changed.
l If you need to restore the gateway IP address of Ethernet port if0 to the factory-delivered
default setting, enter . and press Enter.
Network Init Flags
: 0xA0

User Name

3-16

Issue 03 (2010-12-31)
M2000
User Password
Step 21 When the system displays the following information, it indicates that the IP address of the
controller that you have logged in to is successfully changed.
Network Configuration successfully written to NVSRAM.
Step 22 Run the following command to check whether the information about the port of the disk array
is correctly changed.
-> netCfgShow
l If the port information is incorrect, perform the previous steps to change it. Then, perform
Step 23.
l If the port information is correct, perform Step 23.
Step 23 Check whether the new IP address of the controller takes effect.
On the client PC whose IP address is in the same network segment as the new IP address, open
the DOS command window and then run the ping New IP address of the disk array
controller command.
l If you successfully ping the IP address, it indicates that the new IP address takes effect.
l If you fail to ping the IP address, contact Huawei technical support engineers for assistance.
Step 24 Connect the serial port cable to the port of controller B. Perform the previous steps to change
the port IP address of the other controller.
Step 25 Log in to the server as user root.
Step 26 Run the following commands to search for the disk array:
# SMcli -A
# SMcli -d -i
S3200-1 192.168.8.39
192.168.8.40
SMcli completed successfully.
In the system output, if the IP address of the disk array is consistent with the actual IP address,
it indicates that the IP address of the disk array is successfully changed. Otherwise, change the
IP address again.
----End
3.6 Changing the IP Address of the S2600 Disk Array (Serial

Port Mode)
This section describes how to change the IP address of an S2600 disk array in serial port mode.
Context
l
Issue 03 (2010-12-31)
Each S2600 disk array has an active controller and a standby controller. Each controller
has a CLI serial port.
3-17
M2000
You can change the IP address in serial port mode or command mode. The serial port mode
is preferred because it features high success rate in changing IP addresses. In the case of
remote operations, use the command mode. For details, see 14.3.2 How Do I Change the
IP Address of the S2600 Disk Array (Command Mode).
Before changing the IP address, you must familiarize yourself with the default IP address
planning at delivery. Then, determine whether to re-set the IP address according to the
actual requirement.
The IP address mentioned here is only an example. Replace it with the actual IP address.
If you change the IP addresses of disk arrays on different network segments, change the IP
address of the maintenance Ethernet port on the corresponding server to ensure that two
changed IP addresses are on the same network segment.
Procedure
Step 1 Use the serial port cable to connect any serial port on the controller of the disk array and that of
the PC. Figure 3-7 shows the disk array.
Figure 3-7 Serial ports provided by the S2600 disk array
NOTE
l You need to use the serial port cable that is delivered with the disk array. Otherwise, the disk array
may fail to connect to the PC.
l When using the serial port cable to connect a control to the maintenance terminal, you must use the
serial port cable to connect the maintenance terminal first. When disconnecting the controller from the
maintenance terminal, you must remove the serial port cable from the controller first.
l After using the serial port cable to connect a controller to the maintenance terminal, do not enable the
controller and the maintenance terminal at the same time.
l After using the DB9-RJ45 serial port cable to connect a controller and the maintenance terminal, you
need to use the HyperTerminal or any other program provided by the Windows operating system to
log in to the CLI serial port.
Step 2 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal on the
PC.
Step 3 In the Connection Description dialog box, type the name of a new connection.
Step 4 Specify a serial port of the PC terminal to connect the PC terminal to the disk array, for example,
COM1.
Step 5 Set the properties of the serial port by referring to Table 3-5, and then click OK.
3-18

Issue 03 (2010-12-31)
M2000
Table 3-5 Setting the properties of a serial port

Property
Property Value
Bits per second
115200
Data bits
Parity check
None
Stop bits
Flow control
None
Step 6 Press Enter. If the connection is successful, a dialog box is displayed, as shown in Figure
3-8.
Figure 3-8 Successful connection interface
Step 7 In the successful connection interface, type the user name and password. Then the successful
login success dialog box is displayed, as shown in Figure 3-9.
CAUTION
The initial name and password of the administrator is admin and 123456, respectively. To ensure
the system security, you need to change the password after the initial login.
Issue 03 (2010-12-31)

3-19
M2000
Figure 3-9 Successful login dialog box
Step 8 Run the following command to set the IP address of the Ethernet port managed by controller A:
OceanStor:admin> chgctrlip -c a -a new IP address of controller A -s subnet mask -g
gateway
For example, to change the IP address of the Ethernet port that is managed by controller A to
10.71.15.20, run the following command:
OceanStor:admin> chgctrlip -c a -a 10.71.15.20 -s 255.255.255.0 -g 10.71.15.1
When the system displays the following prompt, type y:
OceanStor: admin> chgctrlip -c a -a 10.71.15.20 -s 255.255.255.0
This operation will change your controller's IP configuration. if you want to ch
ange the IP of the controller you logged in, you will log out after you set the
new IP. However, if you change the IP of the peer controller, you needn't log out.
Do you want to continue? y or n: y
Step 9 Run the following command to check whether the IP address is correct:
OceanStor:admin> showctrlip -c a
Controller IP Address
A 10.71.15.20
00:18:82:e2:00:fb
Subnet Mask
255.255.255.0
Gateway
10.71.15.1
MAC Address
Step 10 Run the following command to set the IP address of the Ethernet port managed by controller B:
OceanStor:admin> chgctrlip -c b -a new IP address of controller A -s subnet mask -g
gateway
For example, to change the IP address of the Ethernet port that is managed by controller B to
OceanStor:admin> chgctrlip -c b -a 10.71.15.21 -s 255.255.255.0 -g 10.71.15.1
When the system displays the following prompt, type y:
This operation will change your controller's IP configuration. if you want to ch
ange the IP of the controller you logged in, you will log out after you set the
3-20

Issue 03 (2010-12-31)
M2000
new IP. However, if you change the IP of the peer controller, you needn't log out.
Step 11 Run the following command to check whether the IP address is correct:
OceanStor:admin> showctrlip -c b
Controller
IP Address
B 10.71.15.21
00:18:82:e2:01:57
Subnet Mask
255.255.255.0
Gateway
10.71.15.1
MAC Address
Step 12 Optional: Modify the /etc/hosts file and the /etc/inet/ipnodes file. If there are multiple servers,
perform the following operations on each server:
NOTE
To change the disk array IP address recorded in the /etc/hosts file and the /etc/inet/ipnodes file, you need
not stop the M2000 services and the database services. After the modification, you need not restart the
server either.
1.
Log in to the server as user root.
2.
Perform the following operations on the server to modify the /etc/hosts file and to replace
the existing IP address of the disk array with a new one:
# vi /etc/hosts
After the modification, press Esc, and then run the :wq! command to save the modification
and exit.
3.
Perform the following operations on the server to modify the /etc/inet/ipnodes file:
# vi /etc/inet/ipnodes
l If the file records the existing IP address of the disk array, replace the existing IP address
with the new one. After the modification, press Esc, and then run the :wq command to
save the modification and exit.
l If the file records the new IP address of the disk array, you need not perform any
modification. Press Esc, and then run the :q command to exit.
----End
Follow-up Procedure
During commissioning, you need to configure the monitoring function of the S2600 disk array
after you install and configure the M2000 client application. For details, see section "Configuring
the Monitoring Function of the S2600 Disk Array".
During maintenance, if the monitoring function of the S2600 disk array is configured, you need
to reconfigure this function after changing the IP address of the server. For details, see section
"How to Configuring the Monitoring Function of the S2600 Disk Array" in the corresponding
administrator manual.
Issue 03 (2010-12-31)

3-21
M2000
Managing the M2000 Clients
About This Chapter

This chapter describes how to manage the M2000 clients. The graphic user interface (GUI) on
the M2000 client supports the O&M for the NEs and enables you to monitor the M2000. You
must manage the M2000 clients to ensure their normal operation.
Context
The requirements of the M2000 client for operation rights are as follows:
l
The users who are authorized to install, upgrade, and uninstall the M2000 client are
Windows users. They belong to the user group Administrators.
The users who are responsible for the routine maintenance of the M2000 client must belong
to the user group Users and have the read and write rights of the M2000 client installation
directory.
4.1 Managing Files and Disks on M2000 Clients

This section describes how to manage the file systems and disks on the M2000 clients.
4.2 Monitoring the Login Status of the M2000 Clients
This section describes how to monitor the login status of the M2000 clients (including the
LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds
the preset maximum number of M2000 threads, you must force a user out to establish a new
connection.
4.3 Setting the Number of Clients Accessible on a PC
This section describes how to edit the configuration file on the M2000 client for setting the
number of clients of the same version (excluding the LMTs that gain access to NEs through the
M2000 proxy) that can be started on a PC.
4.4 Setting the Time Information on the M2000 Client
This section describes how to set the time information on the M2000 client.
Issue 03 (2010-12-31)

4-1
M2000

4.1.1 Introduction to the M2000 Client File System
This introduces the M2000 client file system.
4.1.2 Clearing the Disk Space of an M2000 Client
This section describes how to clear the disk space of an M2000 client. Before performing this
operation, ensure that the files to be deleted are not required for future operations. Deleting a
useful file by mistake may lead to a system operation error.

The client software runs on the Windows operating system and is based on the JAVA virtual
machine. The installation package of the M2000 client software includes the JAVA virtual
machine supported by Windows.
Required client disk space (only for reference): F = I + T + (S x N), where I refers to the size of
the initial version, that is, about 300 MB; T refers to the temporary space for saving patches,
which is less than 20 MB; S refers to the size of mediation files, which ranges from 3 MB to 10
MB; N refers to the number of NE versions, which depends on the actual situation.
Table 4-1 describes the parameters specified in the equations.
Table 4-1 M2000 client software directory
Directory
Description
client installation path
Installation path of the M2000 client software.

The default path is C:\iManagerM2000ClientClient.
M2000 client installation path\client
Path for saving client programs.
M2000 client installation path\client\bin
Path for saving executable files.

\Data
Path for saving NE configuration files.

\diagnosis
Path for saving the information that is used for

locating problems.
NOTE
This path appears only after you run the M2000
diagnosis tool.
4-2

\ext_runcfg
Path for saving the configuration files of

integrated components.
M2000 client installation path\client\dtd
Path for saving .dtd files.

\IDAPI32
Path for saving the localWS dynamic link

libraries.

Issue 03 (2010-12-31)
M2000
Issue 03 (2010-12-31)
Directory
Description
M2000 client installation path\client\lib
Path for saving the library files.

\localWs
Path for saving LocalShell that is used to start

the 2G LMT.

\style
Path for saving the configuration files of the

client.

\Templates
Path for saving the mapping between

administrative regions and their IDs.
M2000 client installation path\client\tmp
Path for saving temporary files during the

upgrade.

\tracefile
Path for saving trace files.

\update
Path for saving upgrade files.
M2000 client installation path\client\cbb
Path for saving the CBB files of the M2000

client.

\configuration
Buffer path of the M2000 client. The path

automatically generates when the client is
started.

\features
Path for saving the feature configuration file of

each subsystem of the M2000 client.

\plugins
Path for saving the configuration file of each

subsystem of the M2000 client as plug-ins.
M2000 client installation path\uninstall
Path for saving the uninstallation program.
M2000 client installation path\script
Root path of the iSStar script.

\run
Path for saving the startup parameter

configuration files of the client and components.

4-3
M2000
Directory
Description
M2000 client installation path\cau
Path for saving the Client Auto Upgrade (CAU)

client software and the version, document
abstract, and group information about the
M2000 client.
NOTE
l The CAU client software provides the upgrade
detection mechanism that is based on the
document abstract for comparing the document
abstract of the server with that of the client. If the
document abstracts are not consistent, you need
to upgrade the client.
l Based on the group information, the server
groups and packs all the client documents
deployed on the server so that the client can
download, install, and upgrade these documents.
Based on the group information, the client also
groups and packs all the client files. Therefore,
these files can be compared with those grouped
and packed by the server after being downloaded.
M2000 client installation path\jre
Path for saving the Java virtual machine

delivered with the M2000 client.
M2000 client installation path\lib
Path for saving the dynamic libraries shared

among the M2000 client, remote alarm
notification client, script framework client, and
data management client.
M2000 client installation path\notify
Path of the remote alarm notification tool.
M2000 client installation path

\TrafficReview
Path of the trace review tool.

Context
CAUTION
You can delete the files when the client is running. Do not delete the files generated on that day.
During the routine O&M, back up and clear the following files:
l
4-4
Trace logs
Issue 03 (2010-12-31)
M2000
Temporary files after the running of the M2000 log collector
Delete the trace logs.
Procedure
Delete the history trace logs saved in the directory M2000 client installation path\client
\tracefile. It is recommended that you preserve the trace logs generated in the latest two
weeks.
l
Delete the temporary files generated after the running of the M2000 log collector.
Delete the temporary files that are generated after the running of the M2000 log collector
and are saved in the directory M2000 client installation path\client\diagnosis.
----End
4.2 Monitoring the Login Status of the M2000 Clients

This section describes how to monitor the login status of the M2000 clients (including the
LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds
the preset maximum number of M2000 threads, you must force a user out to establish a new
connection.
Prerequisite
Before monitoring the M2000 clients, ensure that you are authorized to monitor the users.
Procedure
Step 1 Start the M2000 client and log in to the M2000 server.
Step 2 Choose Security > User Session Monitoring. The User Session Monitoring dialog box is
displayed.
Step 3 Click the User Session Monitoring tab to monitor all the terminals connected to the M2000
system.
Pay special attention to information such as login IP address and login time.
Step 4 Click Refresh to refresh the session list. This step is optional.
Step 5 If you need to force a user to exit, select the user, and then click Force User to Log Out.
NOTE
The user of the selected client is forced out. The users of the other clients do not exit.
The current user cannot force itself to exit.
----End
4.3 Setting the Number of Clients Accessible on a PC

This section describes how to edit the configuration file on the M2000 client for setting the
number of clients of the same version (excluding the LMTs that gain access to NEs through the
M2000 proxy) that can be started on a PC.
Issue 03 (2010-12-31)

4-5
M2000
Prerequisite
l
You have logged in to the PC as a user in the user group Users.
The M2000 client is running properly.
Context
Ideally, a maximum of 31 M2000 clients of the same version can be started on a PC. The number
of clients of the same version connected to a PC depends on the configuration of the PC and that
of the server connected to the PC.
In the M2000 client installation directory\client\plugins\com.swimap.omc.common\style
\productstyle\com.swimap.corba\conf\communicate.xml file, the value of corba_portpool
indicates the port range that the client attempts to occupy. The minimum port number is separated
from the maximum number by "-". The client tests the port from the minimum number to the
maximum number. If all the ports are occupied, the system displays an Error message. You can
set the maximum number of clients of the same version started on a PC by modifying the value
of corba_portpool.
Procedure
Step 1 Open the communicate.xml file in the M2000 client installation path\client\plugins
\com.swimap.omc.common\style\productstyle\com.swimap.corba\conf directory.
Step 2 Find the corba_portpool field, and then change the range of the ports as required.
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE COMMINIDATA SYSTEM "commini.dtd">
<COMMINIDATA>
<AREADESC areaname="communicate">
<DESC descname="communicate">
<PARAS>
<PARA name="operation" value="modify"></PARA>
<PARA name="corba_portpool" value="30500-30699"/>
</PARAS>
</DESC>
</AREADESC>
</COMMINIDATA>
NOTE
l The ports after modification cannot exceed the range from 30500 to 30699.
l Ensure that the ports in the modified range on the firewall are enabled when you modify the port range.
l The ports may be used by other applications. Perform the following substeps to check the occupation
of the ports.
1. Choose Start > Run. The Run dialog box is displayed.
2. Type cmd. Then, click OK.
3. In the displayed window, run the netstat -an command to check the occupation of the ports.
----End
4.4 Setting the Time Information on the M2000 Client

This section describes how to set the time information on the M2000 client.
4.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client
4-6

Issue 03 (2010-12-31)
M2000
system.
4.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client
Prerequisite
The Windows operating system is operational.
Procedure
Step 1 Open the Control Panel.
This section takes the Windows XP operating system as an example.
Step 2 Double-click Date and Time.
Step 3 In the Date and Time Properties dialog box, select the items to be modified.
Item
Operation
Hour
Set the required hour on the Time tab page.
Minute
Set the required minute on the Time tab page.
Second
Set the required second on the Time tab page.
Time Zone Click the Time Zone tab. On the Time Zone tab page, choose the local time zone
from the drop-down list.
Step 4 Click Apply.
----End

system.
Issue 03 (2010-12-31)

4-7
M2000
Prerequisite
l
You have logged in to the Windows operating system. The Windows operating system is
running properly.
The M2000 client and the M2000 server communicate normally.
The clock source of the server is operational.
Context
When the M2000 client is configured as the NTP client, synchronize the time of the M2000
client with the time of the M2000 server.
The configuration procedure is applicable to the Windows 2000 Professional, Windows 2003,
Windows 2008, Windows XP Professional or Windows Vista Business operating system.
Procedure
Step 1 Configure the M2000 client as the NTP client.
Choose Start > Run. In the displayed Run dialog box, enter regedit to open the Registry
Editor window.
In the registry, choose HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet >
Services > W32Time > Parameters. Then, change the value of the parameter LocalNTP to
0, which is the default value. If the parameter LocalNTP does not exist, it indicates that the
value can be ignored and the registry need not be modified.
NOTE
For the operating systems of Windows 2003 or Windows 2008, In the registry, change the value of
Enable under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services >
W32Time > TimeProviders > NtpServer to 0.
Step 2 Specify the NTP clock source.

Choose Start > Run. Type cmd and press Enter.
In the displayed window, run the following command:
c:\>net time /setsntp: IP Address of M2000 Server
NOTE
1. The result of the net time command is saved in the Windows registry. This setting of the net time takes
effect after Windows restarts.
2. To clear the specification, run the net time /setsntp command.
Step 3 Restart the Windows Time service.

Choose Start > Run. In the displayed Run dialog box, enter services.msc to open the
Services window. Identify the Windows Time service and restart the service.
Step 4 Check the NTP server specified by the PC.
c:\>net time /querysntp
NOTE
If the host name and IP address of the PC are specified as the host name and IP address of the NTP server
by /setsntp, the NTP server time is the local time of the PC.
4-8

Issue 03 (2010-12-31)
M2000
Step 5 Perform operations based on operating systems.

l If the M2000 client runs on Windows 2000 operating system, perform Step Step 6.
l If the M2000 client runs on Windows 2003, Windows 2008, Windows XP or Windows Vista
operating system, perform Step Step 7 through Step Step 8.
c:\>w32tm -once -v -test
The system displays the host name of the connected NTP server, deviation between the local
time and the NTP server time, and time cycle of NTP server roll.
Step 7 Run the following command to manually synchronize the time:
c:\>w32tm /resync
c:\>w32tm /stripchart /computer:IP address of the M2000 server /dataonly
The system displays the following information, including the local time of the client and
deviation of the local time from that 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.9881239s
10:05:11, +04.9814570s
10:05:13, +04.9740897s
10:05:15, +04.9589559s
10:05:17, +04.9449507s
...
In the system output, the first column displays the local time of the client, and the second column
displays the deviation between the local time and the server time. + indicates that the client time
is earlier than the server time. - indicates that the client time is later than the server time. You
can press Ctrl+C to exit the browse window.
----End
Issue 03 (2010-12-31)

4-9
M2000
Managing the M2000 Users (HP)
About This Chapter

This describes how to manage the M2000 users, which involve Linux users, Oracle users, OM
users, and NE users. You can manage the accounts and authority of these users and monitor the
operation of these users.
5.1 Types of M2000 Users (SUSE)
This describes three types of M2000 users, namely, Linux user, OM user, and NE user.
5.2 Managing SUSE Users (HP)
This describes how to manage SUSE users, which involve user root, omcuser, and ftpuser. These
users are created during the installation. You can change the password of these users according
to the actual situation. In addition, you can create and manage other users according to the actual
situation.
5.3 Managing Oracle Users (HP)
This chapter describes how to manage the Oracle user that is required for the operation of the
M2000. This chapter also describes how to change the password of the Oracle administrator.
5.4 Managing OM Users
OM users operate and maintain the entire network or specified NEs through the M2000. The
M2000 provides the user management function. By using this function, you can manage user
information and user rights. You can also monitor user sessions and operations. This helps to
prevent unauthorized operations and ensure system security.
Issue 03 (2010-12-31)

5-1
M2000
5.1 Types of M2000 Users (SUSE)

This describes three types of M2000 users, namely, Linux user, OM user, and NE user.
5.1.1 SUSE User
This describes information about Linux users involved in the operation of the M2000 server,
such as the user name, usage, authority, user group, used shell, and home directory.
5.1.2 OM Users
In M2000 wireless network, users with the M2000 operation rights are referred to as operation
and maintenance (OM) users. Users that are authorized to perform operations on only NEs are
referred to as local NE users.
5.1.1 SUSE User

This describes information about Linux users involved in the operation of the M2000 server,
such as the user name, usage, authority, user group, used shell, and home directory.
Besides the default user root on the Linux operating system, the system uses the PlatformTools
to create user omcuser, user ftpuser, user oracle and a user group omcsysm.
The default password and user name of each user account are the same.
l
The default password of user root is root.
The default password of user omcuser is omcuser.
The default password of user ftpuser is ftpuser.
The default password of user oracle is oracle.
Table 5-1 describes the Linux users.
5-2

Issue 03 (2010-12-31)
M2000
Table 5-1 Linux users
Issue 03 (2010-12-31)
User
Name
Usage
Authority
User Group
Shell
Resolution
Program
Directory
root
User root is
the default
user of the
system. User
root is
authorized
to control all
resources,
create other
user
accounts,
assign
authority to
other users,
and perform
all system
operations.
User root
has the
highest
authority
of the
system.
Other, bin, sys,

adm, uucp, mail,
tty, lp, nuucp,
daemon, and
user.root
/sbin/sh
User root
is
authorized
to install
and
uninstall
M2000
server
application
s and to
start and
stop
M2000
services.

5-3
M2000
User
Name
Usage
Authority
User Group
Shell
Resolution
Program
Directory
omcuser
User
omcuser is
the operator
of the
M2000.
User
omcuser is
responsible
for the
operation
and
maintenance
of the
M2000
system, such
as system
status
inquiry and
system
backup, and
system
restoration.
User
omcuser is
authorized
to access
the
database
and
perform
operation
and
maintenan
ce.
root, sys,
omcsysm, dba,
oinstall
/bin/bash
/export/home/
omc
User
omcuser is
not
allowed to
install or
uninstall
M2000
server
application
s.
Before
installing the
M2000
applications,
you must
manually
create user
omcuser.
5-4

Issue 03 (2010-12-31)
M2000
User
Name
Usage
Authority
User Group
Shell
Resolution
Program
Directory
ftpuser
User
ftpuser is
used by the
M2000
applications
to perform
software
management
and file
transfer.
User
ftpuser is
authorized
to perform
software
manageme
nt and file
transfer for
NEs.
omcsysm, dialout,
video
/bin/bash
/export/home/
sysm
User
oracle is
authorized
to access
the
database
and
perform
operations
over the
database.
oinstall, dba,
omcsysm
/bin/bash
/opt/oracle
Before
installing the
M2000
applications,
you must
manually
create user
ftpuser.
oracle
User oracle
is used by
the M2000
to install,
start, stop,
and manage
the Oracle
database.
5.1.2 OM Users
In M2000 wireless network, users with the M2000 operation rights are referred to as operation
and maintenance (OM) users. Users that are authorized to perform operations on only NEs are
referred to as local NE users.
Table 5-2 describes the two management modes of OM users. Only users maintaining the
M2000 are managed in mode 1. Users maintaining NEs are managed in mode 1 or mode 2,
depending on the maintained NEs. For details, see NEs Whose Users Are Managed in Mode 1
and NE Whose Users Are Managed in Mode 2.
Issue 03 (2010-12-31)

5-5
M2000
Table 5-2 Management modes of OM users

Managem
ent Mode
Description
Mode 1
In this mode, users are created, authorized, and authenticated on the M2000.
Mode 2
In this mode, users are created on the M2000 and are authorized and
authenticated on the NE. The mechanism for managing users in mode 2 is as
follows:
l Optical transmission NEs
When creating an NE on the M2000, you need to set a user for accessing
the NE, for example, user A. After user A is set, the M2000 delivers the
information about user A to the NE and the NE creates user A on the NE
and authorizes user A based on the level of user rights. By default, the user
are associated the users created on the M2000 and have the same NE
operation rights.
When the user created on the M2000 performs operations on the NE, the
NE authorizes user A. In this mode, the information about the user name,
password, and rights of user A is managed by the NE.
l NEs of other types
Create user A and user B on the M2000, create a user that has the same user
name and password with user B on the NE and authorize user B, and then
associate user A and user B on the M2000.
When user A operates the NE on the M2000, the NE authorizes user B that
is created on both the M2000 and the NE.
In this mode, the information about the user name, password, and rights of
user A is managed by the M2000. The user name and password of user B
are managed by both the M2000 and the NE and must be consistent. The
information about the rights of user B is managed by the NE.
5.2 Managing SUSE Users (HP)

This describes how to manage SUSE users, which involve user root, omcuser, and ftpuser. These
users are created during the installation. You can change the password of these users according
to the actual situation. In addition, you can create and manage other users according to the actual
situation.
5.2.1 Changing the Password of User root
This describes how to change the password of user root.
5.2.2 Changing the Password of User omcuser
This describes how to change the password of user omcuser when you log in to the system as
user root.
5.2.3 Changing the Password of User ftpuser (SUSE)
This describes how to change the password of user ftpuser when you log in to the system as user
root.
5.2.4 Changing the Password of User oracle
5-6

Issue 03 (2010-12-31)
M2000
This describes how to change the password of user oracle when you log in to the M2000 database
as user root.
5.2.5 Creating a SUSE User (SUSE)
This describes how to create a SUSE user as required.
5.2.6 Deleting SUSE Users (SUSE)
This describes how to delete SUSE users. You can manually delete the SUSE users that are not
required.
5.2.1 Changing the Password of User root

This describes how to change the password of user root.
Prerequisite
l
The old password of user root is available.
The new password of user root is available.
Context
NOTE
The provided password must meet the policy of minimum complexity. The password comprises of at least
6 letters or digits, among which one digit or special character is included.
Procedure
Step 1 Log in as user root, and then enter the old password of user root.
Step 2 Change the password.
# passwd root
Changing password for root.
New password:new password

Reenter New Password:new password
Password changed.
----End
5.2.2 Changing the Password of User omcuser

This describes how to change the password of user omcuser when you log in to the system as
user root.
Prerequisite
l
The new password for omcuser is available.
You have logged in to the UNIX as user root.
Issue 03 (2010-12-31)

5-7
M2000
Context
NOTE
Procedure
Step 1 Run the following command to change the password:
# passwd omcuser
Changing password for omcuser.

Password changed.
----End
5.2.3 Changing the Password of User ftpuser (SUSE)

This describes how to change the password of user ftpuser when you log in to the system as user
root.
Prerequisite
l
The new password of user ftpuser is available.
Context
CAUTION
The special characters '"$ cannot be contained in the password of user ftpuser. To improve the
password security, you are advised to use the following policies to set the password:
l The password length ranges from 8 to 30 characters.
l At least one uppercase is contained in the password.
l At least one lowercase is contained in the password.
l At least one digit is contained in the password.
l At least one special character is contained in the password.
l No user name is contained in the password.
Procedure
5-8

Issue 03 (2010-12-31)
M2000
the Oracle Is Started (HP). If the Oracle service is already stopped, start the Oracle.
For details about how to start the Oracle, see 14.2.2 How to Start the Oracle (HP).
Step 3 Run the following commands to change the password of user ftpuser.
# ./modify.sh
The following message is displayed:
Modify Tool (1.1.0)
1--IP
R--Return
Q--Quit
Step 4 Type 4, and then type the new password of user ftpuser at the following prompt. Type the new
password again, and then press Enter.
-----------------------------------------------------------------Please input the new ftpuser password:
Please Re-enter the password:
The system type is: Single
The operator type is: Password of ftpuser
------------------------------------------------------------------
Step 5 At the following prompt, enter Y for confirmation.

Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]: y
----------------------------------------------------------------------------------------------------------------------------------modify OS ftpuser success
svc_cfgtool modpass ftp success
-----------------------------------------------------------------Process imap.iors success
Process imap.iors.* success
------------------------------------------------------------------
Step 6 After the operation is complete, select Q to exit.
Issue 03 (2010-12-31)

5-9
M2000
Step 7 For details on how to restart the M2000 service, refer to 7.2.3 Starting the M2000 Server
(SUSE).
----End
5.2.4 Changing the Password of User oracle

This describes how to change the password of user oracle when you log in to the M2000 database
as user root.
Prerequisite
l
The new password of the operating system user oracle is available.
Context
NOTE
Procedure
Step 1 Run the following command to change the password of user oracle:
# passwd oracle
Changing password for oracle.

Password changed.
----End
5.2.5 Creating a SUSE User (SUSE)

This describes how to create a SUSE user as required.
Prerequisite
Context
This takes creating user omc1 as an example. User omc1 belongs to the omcsysm user group.
The main directory /home1 is automatically created. The template files are located in the /etc/
skel directory. The user ID is 1023, and B shell is applied.
Procedure
Step 1 Run the following command to create a user account:
# useradd -d /home1 -g omcsysm -m -k /etc/skel -u 1023 -s /bin/bash omc1
5-10

Issue 03 (2010-12-31)
M2000
NOTE
l -d /home1: indicates that the main directory is home1. Change /home1 to the actual main directory
when you create other users.
l -m: indicates that if the main directory does not exist, the system creates this directory automatically.
l -k /etc/skel: copies the template files in a specified directory to the main directory. The common
template files include .profile and .cshrc.
The template files are used to ensure a uniform operating environment. If you plan to copy the template
files to the main directory when you run the useradd command, the following requirements should be
met:
l If the main directory exists, run the useradd -m command to create the main directory.
l If the main directory already exists, ensure that the creator and users in this group have the read,
write, and execute rights of the directory.
l -g omcsysm: indicates that this user belongs to the omcsysm user group. When creating other users,
you need to change it to the actual user group.
l -s /bin/bash: indicates that B shell is applied. If another shell is applied, change B shell to the actual
shell.
l -u 1023: indicates that the user ID is 1023. One user maps to a unique ID. Change the ID to actual user
name when you create other users.
Step 2 Run the following command to set the password for the new user:
# passwd omc1
Changing password for omc1.

Password changed.
NOTE
----End
5.2.6 Deleting SUSE Users (SUSE)

This describes how to delete SUSE users. You can manually delete the SUSE users that are not
required.
Prerequisite
Procedure
Step 1 Run the following command to delete a user account and the main directory of the account:
# userdel -r user account
Issue 03 (2010-12-31)

5-11
M2000
CAUTION
If the user has logged in to the system, you cannot run the userdel command to delete this user.
----End
Example
Assume that there is user omc1 in the system. To delete user omc1, run the following command:
# userdel -r omc1
If the following message is displayed, you can infer that no timing task created by the user is
being performed.
no crontab for omc1
5.3 Managing Oracle Users (HP)

This chapter describes how to manage the Oracle user that is required for the operation of the
M2000. This chapter also describes how to change the password of the Oracle administrator.
5.3.1 Introduction to Oracle Users
This introduces the Oracle user accounts used by the M2000 and the mapping authorities.
5.3.2 Changing the Password of Oracle user system
This describes how to change the password of user system used in the Oracle.
5.3.1 Introduction to Oracle Users

This introduces the Oracle user accounts used by the M2000 and the mapping authorities.
To operate the database on the M2000 server, you must use a Oracle user account.
Only Oracle users can operate the Oracle database. After the Oracle is installed, the default user
account of the Oracle is system, which has the highest authority.
The default password of user system is emsems.
5.3.2 Changing the Password of Oracle user system

This describes how to change the password of user system used in the Oracle.
Prerequisite
5-12

Issue 03 (2010-12-31)
M2000
Context
CAUTION
The password of user system in the Oracle can contain only the special characters #_$. $ is not
recommended because $ is the special character of bash. You are advised to use the combination
of 0 to 9, a to z, A to Z, and special characters #_ to set the password of user system.
To improve the password security, you are advised to use the following policies to set the
password:
l The password length ranges from 8 to 30 characters.
l At least one uppercase is contained in the password.
l At least one lowercase is contained in the password.
l At least one digit is contained in the password.
l At least one special character is contained in the password.
l No user name is contained in the password.
Procedure
Services (SUSE). If any M2000 service is running, stop it.
For details about how to stop the M2000 service, see 7.2.4 Stopping the M2000 Services
(SUSE).
the Oracle Is Started (HP). If the Oracle service is already stopped, start the Oracle.
For details about how to start the Oracle, see 14.2.2 How to Start the Oracle (HP).
Step 3 Perform the following steps to change the password of user system in the Oracle:
1.
Run the modify script.

# ./modify.sh
The following message is displayed:
Modify Tool (1.1.0)
1--IP
R--Return
Q--Quit
Issue 03 (2010-12-31)

5-13
M2000
When the main menu is displayed, choose 3--Database password.

2.
Based on the system prompt, enter the name of the Oracle database server and the previous
and new passwords of user system. Press Enter.
-----------------------------------------------------------------Please input the database server name[default ossdb]:
Please input the old database superuser's password:
Please input the new database superuser's password:
Please Re-enter the password:
NOTE
l Enter p/P. The system displays the function menu of the modify script, prompting you to perform
operations such as changing the IP address or user password.
l Enter q/Q to exit the modify script.
l Press Enter. The default values in the system output are used.
l You need to enter the new password of user system twice.
3.
When the system displays the following prompt, enter Y, and then press Enter:
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]: Y
NOTE
l Enter Q to exit the script without performing any operations.

l Enter R to return to the previous step to reconfigure relevant parameters.
l Enter P. The system displays the function menu of the modify script, prompting you to perform
operations such as changing the IP address or user password.
l You need to wait for about 12 minutes if you run the modify script to change the password of
user system.
4.
When the system displays the following information, you can infer that the change is
successful.
If the system output contains failed, you can infer that the change fails. Contact Huawei
5.
When the function menu is displayed again, enter q to exit.
Step 4 Start the M2000 service. For details, see 7.2.3 Starting the M2000 Server (SUSE).
----End
5.4 Managing OM Users

OM users operate and maintain the entire network or specified NEs through the M2000. The
M2000 provides the user management function. By using this function, you can manage user
information and user rights. You can also monitor user sessions and operations. This helps to
prevent unauthorized operations and ensure system security.
5-14

Issue 03 (2010-12-31)
M2000
Managing OM users, see User Management in the M2000 User Management User Guide.
Issue 03 (2010-12-31)

5-15
M2000
Managing OSS System
About This Chapter

The M2000 provides the OSS management function. By using this function, you can view NE
partitioning, manage the M2000 license, monitor the M2000 server, integrated task management,
check OMC status, collect NM log files.
6.1 Monitoring the M2000 Server
You can monitor the status (including the status of the service, process, hard disk and database)
and the component information of the M2000 server as well as logs of the operations performed
on the system monitor client.
6.2 Querying the System Logs of the M2000
This section introduces the M2000 system log. System logs record the operation of the
M2000 system. System logs also record the files and data tables of various types of information,
which can be queried by the M2000 administrator.
6.3 Collecting NM Log Files
When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic
information from the M2000 Server and Client through the FTP protocol. When the M2000
client or server cannot run properly, you can collect all the operational information from the
M2000 client or server to locate faults.
6.4 Querying NE Subareas
This section describes how to query NE subareas. An NE subarea refers to the M2000 server
that manages the NE. If the M2000 server adopts the SLS solution, NEs can be managed by
different servers (subareas). On the M2000 client, you can query different NE subareas.
6.5 Managing the M2000 License
M2000 licenses can restrict the number of manageable devices, and the availability duration of
the M2000. You need to manage the licenses periodically.
6.6 Check OMC status
OMC check is used to check the status of the M2000. This check also exports check reports
in .html format. The OMC check enables you to find the hidden problems of devices. Thus,
severe accidents are avoided and proper operation of current devices is ensured.
6.7 Managing OSS System Tasks in Centralized Manner
The M2000 provides the function of integrated management of scheduled tasks. Thus, you can
browse information such as the task status and the progress. You can also create, modify, and
Issue 03 (2010-12-31)

6-1
M2000
delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and
save task result files to the client.
6-2

Issue 03 (2010-12-31)
M2000
6.1 Monitoring the M2000 Server

You can monitor the status (including the status of the service, process, hard disk and database)
and the component information of the M2000 server as well as logs of the operations performed
on the system monitor client.
Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser
window is displayed.
The system monitor browser consists of the following items:
l
Service Monitor:
Monitors information about services, such as status and start time.
Process Monitor:
Monitors information about processes, such as number of used handles, CPU usage,
memory usage, number of database connections, and number of threads.
Hard Disk Monitor:

Monitors information about the disks in the system, such as total capacity, used space, free
space, usage, and status.
Database Monitor:
Monitors information about the databases in the system, such as status, space, usage, and
log space.
Server Monitor:
Monitors information about the services, such as status, operating system, memory
capacity, CPU usage, and memory usage.
Component Information:
Provides information about server components, such as name, version, and description.
6.1.1 Refreshing the Monitoring Information

To know the latest running status of the M2000 server, you need to refresh the monitoring
information. The M2000 server also periodically refreshes the monitoring information according
to the specified monitoring interval.
6.1.2 Viewing the CPU and Memory Usage of the M2000 Server (SUSE)
This describes how to view the CPU and memory usage of the M2000 server. You can view
information about the CPU usage, memory capacity, and free memory. If you find that the CPU
or memory usage is abnormal, you can log in to the server and handle the problem in time.
6.1.3 Viewing the Disk Usage of the M2000 Server on the M2000 Client (SUSE)
This describes how to view the disk usage of the M2000 server through the system monitor
browser on the M2000 client.
6.1.4 Viewing the Database Usage of the M2000 Server on the Client (SUSE)
This describes how to view the attributes of the database on the M2000 client to know the usage
of the database.
6.1.5 Checking the M2000 Services
This section describes how to check the M2000 services. When the M2000 services are not
running normally, you need to locate faults, and then log in to the server to rectify the faults.
6.1.6 Checking the Status of the M2000 Processes
Issue 03 (2010-12-31)

6-3
M2000
This section describes how to check the status of the M2000 processes. When the M2000
processes are not running normally, you need to locate faults, and then log in to the server to
rectify the faults.
6.1.7 Viewing the Information about M2000 Server Components
This function enables you to view the information of the components installed on the M2000
server that you log in to.
6.1.8 Saving the Monitoring Information
For the convenience of future analysis of the information that is monitored at certain time, you
can save the required monitoring information to the server.
6.1.9 Setting Alarm Thresholds for the M2000
This section describes how to set the alarm thresholds for the M2000. On the M2000 client, you
can set the alarm thresholds to monitor the server status. The monitoring of system status consists
of server monitoring, disk monitoring, databases monitoring, and service monitoring. if the value
of a parameter exceeds the threshold, the system generates the corresponding alarm.
6.1.1 Refreshing the Monitoring Information

To know the latest running status of the M2000 server, you need to refresh the monitoring
information. The M2000 server also periodically refreshes the monitoring information according
to the specified monitoring interval.
Context
l
When you refresh the current tab page, only the information on this tab page is refreshed.
The information on other tab pages is not refreshed.
When you switch tab pages, the information on these tab pages are refreshed immediately.
Therefore, when you switch tab pages, the information is refreshed at the same time.
Procedure
Step 1 Choose Monitor > System Monitor > Browser.
Step 2 In the System Monitor Browser window, click the tab of the monitoring information to be
refreshed.
Step 3 click Refresh.
----End
6.1.2 Viewing the CPU and Memory Usage of the M2000 Server
(SUSE)
This describes how to view the CPU and memory usage of the M2000 server. You can view
information about the CPU usage, memory capacity, and free memory. If you find that the CPU
or memory usage is abnormal, you can log in to the server and handle the problem in time.
Prerequisite
6-4
You have logged in to the M2000 client.
You are authorized with the relevant operation rights.

Issue 03 (2010-12-31)
M2000
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser
Step 2 Click the Server Monitor tab. The performance of the M2000 server is displayed, as shown in
Figure 6-1.
Figure 6-1 Server Monitor
NOTE
In the CPU usage (%) column and the Memory usage (%) column, the green icon indicates that the CPU
usage of the corresponding process is normal; the red icon indicates that the CPU usage of the corresponding
process is abnormal. If the performance monitoring threshold is set, the icon corresponding to a process is
displayed in red when the CPU usage of the process exceeds 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
6.1.3 Viewing the Disk Usage of the M2000 Server on the M2000
Client (SUSE)
Prerequisite
l
Issue 03 (2010-12-31)

6-5
M2000
Context
This operation requires very few system resources and does not affect system operation.
Procedure
Step 2 Click the Hard Disk Monitor tab. The disk usage of the M2000 server is displayed, as shown
in Figure 6-2.
Figure 6-2 Hard Disk Monitor
NOTE
In the Status column, the green icon indicates that the disk usage of the corresponding process is normal;
the red icon indicates that the disk usage of the corresponding process is abnormal. When the disk usage
of a process exceeds the disk usage threshold, the icon corresponding to the process is displayed in red.

----End
6.1.4 Viewing the Database Usage of the M2000 Server on the Client
(SUSE)
of the database.
6-6

Issue 03 (2010-12-31)
M2000
Prerequisite
l
You are authorized to perform relevant operations.
Context
This operation requires few system resources and does not affect system operation.
Procedure
Step 2 Click the Database Monitor tab. The information about the database of the M2000 server is
displayed, as shown in Figure 6-3.
Figure 6-3 Database monitoring
NOTE
In the Status column, the green icon indicates normal and the red icon indicates abnormal. If the database
usage exceeds the preset threshold, the green icon in the relevant column becomes red.
Step 3 (Optional) Click Save to save the monitoring data to a file.

You can save the monitoring data in one of the following formats: .txt, .html, .xml, and .csv.
----End

Issue 03 (2010-12-31)

6-7
M2000
Prerequisite
l
You have the relevant operation rights.
Context
Checking the M2000 services on the M2000 client requires only a few system resources and
does not affect system performance.
Procedure
Step 2 Click the Service Monitor tab to check the M2000 services. See Figure 6-4.
Figure 6-4 Service Monitor tab page
NOTE
In the Status column, the green icon indicates that the corresponding process is normal; the red icon
indicates the corresponding process is abnormal.
Step 3 (Optional) Click Save AS to save the monitoring data as a file.

----End

rectify the faults.
6-8

Issue 03 (2010-12-31)
M2000
Prerequisite
l
Context
Checking the states of the M2000 processes on the M2000 client requires only a few system
resources and does not affect system performance.
Procedure
Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on the
M2000 server. See Figure 6-5.
Figure 6-5 Process Monitor tab page

----End
6.1.7 Viewing the Information about M2000 Server Components

This function enables you to view the information of the components installed on the M2000
server that you log in to.
Procedure
Issue 03 (2010-12-31)

6-9
M2000
Step 2 In the System Monitor Browser window, click the Component Information tab.
Step 3 View the information of all the installed components in Component Information tab.
----End
6.1.8 Saving the Monitoring Information

For the convenience of future analysis of the information that is monitored at certain time, you
can save the required monitoring information to the server.
Procedure
Step 2 In the System Monitor Browser window, click the tab of the monitoring information, and then
click Save As.
NOTE
l The monitoring information can be saved in the format of TXT, HTML, CSV, or XML.
l The default format is XML.
Step 3 In the Save dialog box, select a storage path, enter the file name, and click Save.
----End
6.1.9 Setting Alarm Thresholds for the M2000

This section describes how to set the alarm thresholds for the M2000. On the M2000 client, you
can set the alarm thresholds to monitor the server status. The monitoring of system status consists
of server monitoring, disk monitoring, databases monitoring, and service monitoring. if the value
of a parameter exceeds the threshold, the system generates the corresponding alarm.
Prerequisite
l
Context
On the M2000, you can set the thresholds of certain parameters for the purpose of system
monitoring. When the value of a parameter exceeds the threshold, the relevant record in the
System Monitor Browser window is displayed in red. In addition, the corresponding alarm is
generated.
Procedure
Step 1 In the main window, choose Monitor > System Monitor > Settings. The System Monitor
Settings dialog box is displayed, as show in Figure 6-6.
6-10

Issue 03 (2010-12-31)
M2000
Figure 6-6 System Monitor Settings dialog box
Step 2 Select a monitoring item to set the thresholds.

For details about the parameters for monitoring the server, see Table 6-1.
Issue 03 (2010-12-31)

6-11
M2000
Table 6-1 Server Monitor

Name
Server Monitor
Parameter Settings
CPU sustained
overload times
(10-400 times)
Description
Settings
Description:
Value:
l The number of
consecutive
sampling times is
equal to CPU
sustained
overload times.
The sampling
interval is equal
to Server status
refresh interval.
If the CPU usage
sampled each
time is larger than
the generation
threshold, it
means that the
CPU is
consecutively
overloaded.
When the number
of overload times
reaches the
specified value, a
high CPU usage
alarm is
generated.
Value range: 10-400

Default value: 40
l If the CPU usage

sampled at a time
is smaller than the
clearance
threshold, the
high CPU usage
alarm is cleared.
Server status refresh
interval (2-60
seconds)
6-12
Description:
Value:
Refresh interval for

server monitoring,
that is, the CPU
usage is sampled
every x seconds.
Value range: 2-60

Default value: 15
Issue 03 (2010-12-31)
M2000
Name
Server Monitor
Threshold Settings
CPU usage (%)
Memory usage (%)
Description
Settings
Description:
Value:
Used to set
Threshold for
Alarm Generation,
Threshold for
Alarm Clearance
for the CPU usage
alarm and whether to
enable the bubble.
Value range: 1-99.

Default value: 90.
Used to set
Threshold for
Alarm Generation
and Threshold for
Alarm Clearance
for the memory
usage alarm.
Value:
Offset value range:

1-99. Default value:
70.
Value range: 1-99.

Default value: 95.
Offset value range:
85.
l If the memory
usage is larger
than Threshold
for Alarm
Generation of
Memory used
rate, the M2000
generates a high
memory usage
alarm.
l If the memory
usage is smaller
than Threshold
for Alarm
Clearance of
Memory used
rate, the M2000
generates an
alarm, prompting
that the high
memory usage
alarm is cleared.
l When the
function of
bubble
information is
enabled, if the
server is faulty,
the system
displays a bubble
information.
Issue 03 (2010-12-31)

6-13
M2000
Table 6-2 describes the parameters for monitoring the disks of the server.
Table 6-2 Hard Disk Monitor
Name
Disk Monitor
Parameter Settings
Disk Monitor
Threshold Settings
Hard disk status

refresh interval
(60-3600 seconds)
Default value setting

(%)
Description
Settings
Description:
Value:

hard disk
monitoring.
Value range:
60-3600
Description:
Value:
All default
thresholds of hard
disk usage on the
M2000 server.
Value range: 1-99
l When the hard

disk usage is
larger than
Threshold for
Alarm
Generation of an
alarm severity
level, the M2000
generates a high
hard disk usage
alarm of this
severity level.
l Warning: 60
l When the hard

disk usage is
smaller than
Threshold for
Alarm
Clearance of an
alarm severity
level, the M2000
clears the high
hard disk usage
alarm of this
severity level.
Default value: 60
Default value of
Threshold for
Alarm Generation:
l Minor: 70
l Major: 80
l Critical: 90
Default value of
Threshold for
Alarm Clearance:
l Warning: 55
l Minor: 65
l Major: 75
l Critical: 85
l When the
function of
bubble
information is
enabled, if the
hard disk is
faulty, the system
displays a bubble
information.
6-14

Issue 03 (2010-12-31)
M2000
Name
Advanced Setting
(%)
Description
Settings
Description:
Value:
Thresholds of all the

hard disk usage on
the M2000 server.
l If you select
Default value,
the M2000 uses
the threshold
specified in
Default value
setting.
l When the hard

disk usage is
larger than
Threshold for
Alarm
Generation of an
alarm severity
level, the M2000
generates a high
hard disk usage
alarm of this
severity level.
l When the hard
disk usage is
smaller than
Threshold for
Alarm
Clearance of an
alarm severity
level, the M2000
clears the high
hard disk usage
alarm of this
severity level.
l If you select
Customize
value, the
M2000 uses
customized
thresholds of
alarms. Value
range: 1-99.
l If you select
Disable alarm
generation,
theM2000 doesn't
report alarms of
the disk partition.
l When the
function of
bubble
information is
enabled, if the
hard disk is
faulty, the system
displays a bubble
information.
Table 6-3 describes the parameters for monitoring the database of the server.
Issue 03 (2010-12-31)

6-15
M2000
Table 6-3 Database Monitor

Name
Database Monitor
Parameter Settings
Database status
refresh interval
(300-3600 seconds)
Description
Settings
Description:
Value:
Interval of database
refreshing.
Value range:
300-3600
Default value: 300
Database Monitor
Threshold Settings
Default Value
Setting (%)
Description:
Value:
All default
thresholds of
database usage on the
M2000 server.
Value range: 1-100
l When the
database usage is
larger than
Threshold of an
alarm severity
level, the M2000
generates a high
database usage
alarm of this
severity level.
l Minor: 90
Default value:
l Warning: 85
l Major: 95
l Critical: 98
l When the
database usage is
smaller than
Threshold of an
alarm severity
level, the M2000
clears the high
database usage
alarm of this
severity level.
6-16

Issue 03 (2010-12-31)
M2000
Name
Advanced Setting
(%)
Description
Settings
Description:
Setting method:
Thresholds for the

database usage
alarms of different
severities. You need
to set these
thresholds separately
for each database on
the M2000 server.
Set the following

parameters for each
database:
l When the
database usage is
larger than
Threshold of an
alarm severity
level, the M2000
generates a high
database usage
alarm of this
severity level.
l When the
database usage is
smaller than
Threshold of an
alarm severity
level, the M2000
clears the high
database usage
alarm of this
severity level.
l Default Value:
use default
thresholds for the
database usage
alarms of
different
severities.
l Customize
Value: customize
thresholds for the
database usage
alarms of
different
severities.
Value range:
1-100
Default value:
Warning: 85
Minor: 90
Major: 95
Critical: 98
l Disabled
Monitoring:
Disable the
database
monitoring.
Table 6-4 describes the parameters for monitoring the server services.
Table 6-4 Service Monitor
Name
Services Monitor
Parameter Settings
Service status refresh

interval (60-3600
seconds)
Description
Settings
Description:
Value:
Interval of service
refreshing.
Value range:
60-3600
Default value: 60
Issue 03 (2010-12-31)

6-17
M2000
Name
Service Monitor
Screen Tip Settings
Default Group
Description
Settings
Description:
Setting method:
Set whether to
display the service
status at the lower
right corner of the
M2000 system
Select a service from

the Service Name
drop-down list.
Select enable or
disable in the
corresponding Show
Screen Tips dropdown list.
monitor client by
or
NOTE
l If all the
monitored
services are
running,
displayed.
is
l if a monitored
service is stopped,
is displayed.
l You can doubleclick
or
to
access the Service
Monitor tab.
Step 3 Click OK.

----End
6.2 Querying the System Logs of the M2000

This section introduces the M2000 system log. System logs record the operation of the
M2000 system. System logs also record the files and data tables of various types of information,
which can be queried by the M2000 administrator.
Prerequisite
l
Querying the system logs requires only a few system resources and does not affect the
system operation.
System logs are saved in the following path on the M2000 server by default:
Context
/opt/OMC/var/fileint/syslogs
The save path of the system logs that are periodically exported is as follows:
/opt/OMC/var/ThresholdExport/Log
6-18

Issue 03 (2010-12-31)
M2000
If the log data in the database exceeds a preset threshold, the system exports the log data
to a specific path.
l
The contents of the system logs:

Level: Risk, Minor, Info. System logs can be categorized into three levels in descending
order.
Source: Sources, such as FaultService, ServiceAdmin, and MediationService, are
identified by the logos of the subsystems in the M2000 system.
Time: Identifies the time when a system log is recorded. The date format is "Week/
Month/Day/Time/Timezone/Year", for example, Thu May 4 11:28:47 CST 2006.
Basic information: Provides the basic information on system operation, such as the
information about service startup.
Details: Provides the details on system operation.
Procedure
Step 1 Choose System > Log Management > Query System Logs. The Filter dialog box is displayed.
Step 2 Set the filtering conditions in the Filter dialog box, and then click OK. The Query System
Logs window is displayed.
Step 3 Double-click a record to view the detailed information.
In the displayed Log Details dialog box, the system displays details about a successful operation
or a failed operation.
Step 4 Right-click a record and save the specified system logs as a file.
You can save the system logs in one of the following formats: .txt, .html, .xls, .csv, and .pdf.
----End
6.3 Collecting NM Log Files

When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic
information from the M2000 Server and Client through the FTP protocol. When the M2000
client or server cannot run properly, you can collect all the operational information from the
M2000 client or server to locate faults.
Context
By using this information, you can locate faults. The collected information includes:
l
Trace files on the client, for example, Client_DebugTrace.
Java virtual machine thread stack and lock state in client, for example,
Client_ThreadStackDump.txt
Trace files on the server, for example, iMAP.root.trace (to store the current trace files)
and imap_stacks.20070206.170237.trace (to store the historical trace files collected
before the NM log files)
Core files on the server, for example, core.imapsvcd.0.21221.1170824184.stack
File of alarm NE synchronization number, for example, FMSyncNo
The pstack file, for example, imap_stacks.20070207.155817.trace.
Issue 03 (2010-12-31)

6-19
M2000
Information about the Sybase, for example, SybaseConfig.zip, SybaseVersion.zip, and

SYBLog.20070206.171040.zip.
By default, the collected files are saved in M2000 client\client\diagnosis\collected files. You
can change the save path.
l
The information collection progress is displayed in the Collection Details area of the Log
Information Collector window.
The M2000 diagnostic tool automatically collects diagnostic information from the client
and then from the server.
Procedure
Step 1 Choose Programs > iManager M2000 Client > M2000 Log Information Collector.
The Log Information Collector window is displayed.
Step 2 In the Port Select window, select the M2000 client from which you need to collect information,
and then click OK.
If you have opened multiple M2000 clients concurrently, all the open clients are displayed in a
list in the Port Select window. By performing this step, you can specify the client from which
the diagnostic information is collected.
TIP
By comparing whether the process IDs in the PID column of the list with the progress ID of the target
client, you can determine the client from which you will collect the diagnostic information.
1. Choose Start > Run. The Run dialog box is displayed.
2. Type taskmgr, and then click OK. The Windows Task Manager dialog box is displayed.
3. Click the Processes tab.
4. Choose View > Select Columns. The Select Columns dialog box is displayed.
5. Select the PID (Process Identifiers) check box, and then click OK.
6. Click the Applications tab.
7. Right-click the M2000 client to be viewed, and then choose Go To Process from the shortcut menu.
8. In the Port Select window, select the column where the value of PID is the same as the value displayed
in the PID column.
Step 3 Configure the FTP server.

1.
Enter the IP address of the M2000 server.
2.
Enter the port number.
3.
Enter the FTP user name and password for logging in to the target server.
Step 4 Select the information to be collected. For details, see Parameters for Collecting NM Logs
Parameters.
l To collect the trace files on the client, trace files on the server, core files on the server, or
trace files on the LMT, you need to set Start Time and End Time to collect the information
within the specified time range.
l To collect alarm localization information, you need to enter the name of the NE whose alarm
localization information needs to be collected in NE Name.
Step 5 Set the folder for saving the diagnostic information.
The collected files are saved under M2000 client installation directory\client\diagnosis
\collected files. You can modify the directory for saving collected files.
6-20

Issue 03 (2010-12-31)
M2000
Step 6 Click Collect to collect the diagnostic information.

l If you click Stop when collecting the diagnostic information from a client, do not stop the
progress of collecting information from the client.
l If you click Stop when collecting the diagnostic information from the M2000 server, the
diagnostic information about the server cannot be obtained.
l To view the collected diagnostic information, you can click Browse to navigate the directory
of the collected files.
----End
6.4 Querying NE Subareas

This section describes how to query NE subareas. An NE subarea refers to the M2000 server
that manages the NE. If the M2000 server adopts the SLS solution, NEs can be managed by
different servers (subareas). On the M2000 client, you can query different NE subareas.
Prerequisite
Procedure
Step 1 Choose System > Query NE SubArea to open the Query NE Subarea window.
Step 2 Select a query condition, and then click Query.
You can query NE subareas based on NE subareas or NE names.
l Querying NE subareas based on NE subareas: In the Query Result dialog box, the NE
distributions and NE information such as No, NE Name, NE Version, and Number of NEs
are displayed. In the Statistics dialog box, the subarea information such as IP addresses and
database instance names are displayed.
l Querying NE subareas based on NE names: In the Query Result dialog box, the NE
distributions and NE information such as No, NE Name, NE Version, and Number of NEs
are displayed. In the Statistics dialog box, the subarea information such as IP addresses and
database instance names are displayed.
NOTE
You can click Save to save the query results as a file.
For the detailed parameter description, see Table 6-5.

Table 6-5 Parameters for the NE Partitioning Information
Parameter
Description
Query Condition
Issue 03 (2010-12-31)
NE Subarea
Host name of the NE Partitioning when you

query the specific partitioning information,
you can select names of all partitions or the
name of a specific partition from the dropdown list.
NE Name
Indicates the NE Name.

6-21
M2000
Parameter
Query Result
Description
No.
Indicates the serial number of the NE.
NE Name
Indicates the NE Name.
NE Version
Indicates the version of the NE.
Number of NEs
Indicates the number of the NEs that belong to

the NE Partitioning.
Statistics
Indicates the partitioning information about

the NE, including the IP address and the
instance name of the database.
----End
6.5 Managing the M2000 License

M2000 licenses can restrict the number of manageable devices, and the availability duration of
the M2000. You need to manage the licenses periodically.
6.5.1 Querying the M2000 License
This topic describes how to query the license file on the M2000 server through the M2000 client.
6.5.2 Updating the M2000 License
This topic describes how to replace the M2000 license file on the M2000 server through the
client.
6.5.1 Querying the M2000 License

Procedure
Step 1 Choose License > OMC License Management > License Information.
Step 2 In the License Information dialog box, query the license information about resources and
functions on the Resource control item and Function control item tabs.
----End
6.5.2 Updating the M2000 License

This topic describes how to replace the M2000 license file on the M2000 server through the
client.
Prerequisite
When updating a license, delete the license files that are not in use from the server directories
license and licensebak, and then update the license.
6-22

Issue 03 (2010-12-31)
M2000
Context
l
The type of the license applied for must be consistent with the version type.
Before the licenses expire, the M2000 displays a warning periodically.
The valid time for the license that is uniformly used in M2000 contains two fields: Expiry
(Days) and End Time. If both the fields exist, the value of Expiry(Days) is valid.
Procedure
Step 2 In the License Information dialog box, click Update License.
Step 3 In the Open dialog box, select the new license file(*.dat license file), and then click Open.
Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then click
OK.
----End
6.6 Check OMC status

OMC check is used to check the status of the M2000. This check also exports check reports
in .html format. The OMC check enables you to find the hidden problems of devices. Thus,
severe accidents are avoided and proper operation of current devices is ensured.
Prerequisite
l
You have logged in to the M2000 successfully.
You are authorized to perform associated operations.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New or double-click OMC Check node.
Step 3 In the displayed New Task dialog box, set the basic information of the task.
1.
In the Task Name field, enter the name of the task.
2.
From the Run Type drop-down list, select Once or Period.
Step 4 Click Next.

Step 5 Then, set the start time of the task.
To set the start time of the task, perform the following operations:
l In the Start Time field, enter the start time.
l Click
or
l Click
. In the displayed Date/Time Selection dialog box, set the start time.
to adjust the time.
NOTE
The Start Time must be later than the current system time.
Issue 03 (2010-12-31)

6-23
M2000
Step 6 Perform different operations based on task types.

Task Type
Steps
One-time task Perform Step 7.

Periodic task
l In No. of periods and No. of run times fields, enter the associated
information. Then, perform Step 7.
l In No. of periods and End time fields, enter the associated information.
Then, perform Step 7.
Step 7 Click Next. Then, For details of setting the information about OMC check, refer toTable 6-6.
Table 6-6 Parameters for Selecting Objects for OMC Check
Parameter
Description
Device Check
OMC
NE
OMC
Health Check
Sun Server:Displays the health check items supported by

M2000.
l Operating System
l Sybase
l VERITAS Volume Manager Software
l Sun Cluster
l Host Hardware
l OMC
HP or ATAE Server:Displays the health check items supported
by M2000.
l Operating System
l Oracle
l VERITAS Volume Manager Software
l VCS Cluster
l S3X00 Array
l OMC
Step 8 Click Finish.

The progress bar displays the progress of file upload. After the upload is complete, the new
device check task is displayed on the task list.
----End
6.7 Managing OSS System Tasks in Centralized Manner

The M2000 provides the function of integrated management of scheduled tasks. Thus, you can
browse information such as the task status and the progress. You can also create, modify, and
6-24

Issue 03 (2010-12-31)
M2000
delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and
save task result files to the client.
6.7.1 Overview of Integrated Task Management
The integrated task management integrates the concepts such as types of integrated tasks, task
scheduling parameters, states of timing tasks. The knowledge of integrated task management
helps you perform the operations related to the integrated task management.
6.7.2 Customizing the Interface for Managing Timing Tasks
This describes how to customize the interface for managing timing tasks. The system can display
timing tasks of the specified function type in the navigation tree or display the timing tasks
meeting the condition in the task list.
6.7.3 Creating a User Timing Task
This topic describes how to create a user timing task. Parameter setting varies according to
different tasks.
6.7.4 Modifying a Timing Task
This section describes how to modify the attributes of a user timing task or a system timing task.
6.7.5 Managing Timing Tasks
User timing tasks refer to those timing tasks managed by the user. The user can delete, suspend,
resume, cancel, terminate, and roll back user timing tasks.
6.7.6 Viewing Timing Tasks
Through the M2000 function of viewing timing tasks, you can view the status of all timing tasks
in a centralized manner. This helps you adjust the concerned timing tasks according to actual
conditions.
6.7.7 Downloading Task Execution Tasks
You can download the execution file of NodeB license allocation tasks to a local PC and then
check the specific resource allocation information.
6.7.8 Downloading Result Files
This describes how to download the results of timing tasks. You can save the results of timing
tasks on the server to the local client in .txt format.
6.7.9 Reference of the OSS Management GUI
This part describes the OSS management interfaces and related information such as the
parameters used in the OSS management. This helps you understand the functions of OSS
management easily.
6.7.1 Overview of Integrated Task Management

The integrated task management integrates the concepts such as types of integrated tasks, task
scheduling parameters, states of timing tasks. The knowledge of integrated task management
helps you perform the operations related to the integrated task management.
Types of Centralized Tasks

The M2000 classifies managed scheduled tasks into different types according to the task
execution period, function, and feature.
Issue 03 (2010-12-31)

6-25
M2000
Tasks Grouped According to the Execution Period

According to the execution period, the M2000 classifies managed scheduled tasks into one-time
tasks and periodic tasks. Table 6-7 describes each type of task.
Table 6-7 Tasks grouped according to the execution period
Description
Once
Refers to a task that is performed only once at a

specified time.
Period
Refers to a task that is performed periodically since a

specified time.
Tasks Grouped According to the Function

According to the task function, the M2000 classifies managed scheduled tasks into database
capacity management tasks, file interface tasks, manual dump tasks, overflow dump tasks, NE
Information Collector (NIC) tasks, synchronization tasks, backup tasks, CM report tasks, CME
tasks, NE health check (NHC) tasks, and other tasks. Table 6-8 describes each type of task.
NOTE
The NEs that support CME tasks are the RNC, NodeB, BSC6000, BSC6900 GSM, BSC6900 UMTS and
BSC6900 GU.CME tasks are available only after the CME software corresponding to the NE version is
installed.
Table 6-8 Tasks grouped according to the function

Description
Database Capacity Management
The M2000 periodically deletes the data whose storage

duration reaches the specified Save Days from the
database. Database capacity management tasks ensure
that the database capacity is maintained within a proper
range, thus avoiding database faults caused by insufficient
database capacity.
By default, the maximum Save Days in the database is 90
days. The customized value cannot exceed 90 days.
The data that can be managed by the M2000 consists of
M2000 operation logs, M2000 system logs, M2000
security logs, NE operation logs, NE system logs, NE
security logs, alarm/event logs, and performance data.
6-26

Issue 03 (2010-12-31)
M2000
Description
File Interface
Various types of data is periodically exported to a

specified directory on the server. You can save data
outside the system by using this function. The exported
data is still stored in the database.
The data that can be exported consists of performance
data, configuration data, alarm/event logs, NodeB license
data, NE upgrade logs, NE inventory data, NE operation
logs, NE security logs, NE system logs, M2000 operation
logs, M2000 system logs, and M2000 security logs.
Issue 03 (2010-12-31)

6-27
M2000
Description
NIC
NIC tasks provide the Nastar with the NE data required

for analyzing system performance, querying and verifying
configuration data, scanning uplink frequencies, and
optimizing neighboring cells. NIC tasks are classified into
the following types:
l 2G/3G Neighboring Cell Optimization: These tasks
are used for collecting the information about
neighboring GSM cells for 3G neighboring relation
analysis.
l GSM MR Data Collection: These tasks provide the
performance analysis tool with MR data for network
optimization analysis. These tasks are controlled by
the M2000 license.
l NIC Configuration Data Export: These tasks provide
the Nastar with NE configuration data for NE
configuration data query and verification.
l RTWP Data Collection: These tasks provide the Nastar
with NodeB interference data.
l Daemon NIC Task: These tasks provide the Nastar
with various types of data, such as the interference
data, intra-frequency neighboring cell optimization
data, complaint handling data of the CDMA network,
and the intra-frequency neighboring cell optimization
data and coverage analysis data of the UMTS network.
l Network Logs Collection: These tasks are used for
collecting the CHR logs of WiMAX BTSs and
eNodeBs and neighboring cell relation logs and
interference logs of WiMAX BTSs, thus providing the
Nastar with the data about abnormal call events,
terminal switch events, and base station frequency
interference.
l Basic NE Information Export: These tasks are used for
collecting basic NE information for the Nastar.
l Frequency Scan: These tasks provide the Nastar with
uplink frequency data for uplink interference analysis.
These tasks are controlled by the M2000 license.
l Neighboring Cell Optimization: These tasks provide
the Nastar with neighboring cell optimization data for
neighboring cell analysis. These tasks are controlled
by the M2000 license.
6-28

Issue 03 (2010-12-31)
M2000
Description
Others
Other tasks are classified into the following types:

l MML Script: After an MML script is configured, the
M2000 issues the commands in the script in batches
on a scheduled basis. Therefore, you need not
manually issue the commands one by one.
l NodeB License Timed Distribution: The M2000
performs scheduled tasks for allocates NodeB license
resources at a specified time, thus reducing manual
operations.
l PRS Scheduled Task: You can set PRS scheduled tasks
on the M2000 for the required performance reports.
Then, the M2000 collects performance data and
generates performance reports on a scheduled basis.
l BSC/RNC License Timed Activation: The M2000
performs scheduled tasks for downloading and
activating BSC/RNC license files at a specified time,
thus reducing manual operations.
l OMC Check: The M2000 checks its devices and
generates a check report in .html format on a scheduled
basis. Therefore, hidden problems of devices can be
identified and severe accidents can be avoided.
l RSSI Test: The M2000 collects the RSSI values of
base stations in a scheduled basis. Therefore,
exceptions in the base station radio frequency (RF)
subsystem can be identified in time and voice quality
can be ensured. Performing an RSSI test task
consumes a large number of system resources.
Therefore, you are advised to perform such a task only
for batch test. Currently, only CBTSs support RSSI test
tasks.
l Upgrade Checking: The M2000 checks whether the
services are functioning normally after an NE is
upgraded.
l Dual Home Auto Consistency Management: The
M2000 checks the data of NEs that have the dualhoming relation periodically or on a scheduled basis,
thus enabling you to check NE data consistency and to
ensure that an MSC server can take over some or all
data on the other MSC server in case of a dual-homing
failover.
l Alarm Check: The M2000 analyzes NE alarm trends,
comparisons between alarms, TopN alarm features,
alarm maintenance, and fault alarms and generates
check reports in .html format on a scheduled basis, thus
enabling you to analyze network faults in detail.
l PM Synchronization: The M2000 periodically
synchronizes NE objects to ensure that the
Issue 03 (2010-12-31)

6-29
M2000
Description
performance measurement (PM) objects on the
M2000 are consistent with those on NEs.
l Top Power Test: The M2000 collects the value of the
transmit power on top of the cabinet on a scheduled
basis. Therefore, exceptions in the base station RF
subsystem can be identified in time and voice quality
can be ensured. Performing a top power test task
consumes a large number of system resources.
Therefore, you are advised to perform such a task only
for batch test. Currently, only CBTSs support top
power test tasks.
l NE Software Download: The M2000 instructs an NE
to download the corresponding NE mediation software
from the M2000 server periodically or on a scheduled
basis to ensure that the NE version is delivered to the
NE at the specified time.
l Script Timer Task: By running the preset HSL scripts,
you can perform operations such as modifying NE
parameters and obtaining alarm data.
Synchronization
Certain data may be missing due to causes such as

communication interruption. The synchronization
function enables you to ensure that the data on the
M2000 is consistent with the data on NEs.
l The M2000 obtains the latest data from NEs on a
scheduled basis by performing an NE configuration
data synchronization task, NE log synchronization
task, NE upgrade log synchronization task, NE
inventory data synchronization task, or alarm
scheduled synchronization task.
l Through a maintenance mode synchronization task,
the NE maintenance mode information stored on the
M2000 is delivered to NEs on a scheduled basis.
Backup
The M2000 allows you to save server data and NE data in

backup files to a specified directory on the M2000 server.
The stored server data and NE data can be used for
restoring the system and NEs in case of any data loss or
any exception in the system and NEs.
Backup tasks are classified into the following types:
l NE Backup: The configuration files stored on NEs and
the files that dynamically change during NE operation
can be backed up.
l Server Backup: The dynamic service data of the
M2000 system can be backed up. The operating
system, however, cannot be backed up.
l NE License Backup: Only the currently activated
license files on NEs can be backed up.
6-30

Issue 03 (2010-12-31)
M2000
Description
CM Report
The M2000 periodically exports configuration reports in

files to a specified directory on the M2000 server. You can
use this function to save data outside the system. The
exported data is still stored in the database.
The types of reports that can be exported consist of RAN
report, core network resource report, NE report, NE
statistic report, and NE link report.
CME tasks are classified into the following types:
CME
l CME Upload: The M2000 uploads the selected NE

configuration data to the CME server periodically or
on a scheduled basis to ensure that the CME obtains
the latest NE data for data configuration.
l Cell Parameters Compare: The M2000 compares the
parameters in the current data area with the default
parameters in the CME configuration template and
then exports the comparison results to the default path.
l Cell Consistency Check: The M2000 checks whether
the data in the current data area complies with the
selected check rules. Currently, the rules for checking
unidirectional neighboring cells and cell consistency
are provided.
l Current Area Export: The M2000 exports the required
data from the current data areas through northbound
interfaces, thus facilitating current data area
management.
Pre-alarm Handling Task: The M2000 checks whether the
mediation or the current NE is normal and generates a
report on a scheduled basis.
NHC
Tasks grouped according to the feature

According to the task feature, the M2000 classifies managed scheduled tasks into system
scheduled tasks and user scheduled tasks. Table 6-9 describes each type of task.
Table 6-9 Tasks grouped according to the feature
Issue 03 (2010-12-31)
Description
System Scheduled Task
System scheduled tasks are the tasks required for the normal
operation of the M2000 system. For details about these
tasks, see System Scheduled Tasks.
User Scheduled Task
User scheduled tasks are the tasks customized to meet the

requirements of network maintenance. For details about
these tasks, see User Scheduled Task.

6-31
M2000
System Scheduled Tasks

System scheduled tasks are created during the installation or upgrade of the M2000 system. The
Creator parameter of each system scheduled task is displayed as OMC.
The M2000 uses
tasks.
to identify system scheduled tasks and uses
to identify user scheduled
NOTE
Only users in the administrator group can manage and view system scheduled tasks.
System scheduled tasks cannot be copied. Only some parameters of system scheduled tasks can be
modified. These parameters, however, cannot be deleted.
In the system scheduled tasks, some tasks can be suspended or canceled.
For details about system scheduled tasks, see Table 6-10.

Table 6-10 Description of system scheduled tasks
Task Type
Task Name
Reference
Database Capacity
Management
Alarm/Event Log
Dump
For details, see Parameters for Setting the

Alarm/Event Timing Dump.
Performance Data
For details, see Parameters for Setting

Performance Database Capacity Parameters.
NE Operation Log
For details, see Parameters for a NE Log Dump

Task.
NE Security Log
NE System Log
NM Operation Log
Dump
For details, see Parameters for Setting M2000

Log Timing Dump.
NM System Log
Dump
NM Security Log
Dump
File Interface
6-32
Performance Data
Export
For details, see Parameters for Exporting

Performance Measurement Results.
Configuration Data
Export
For details, see Parameters for Modifying a

Configuration Data Export Task.
NodeB License Data

Export

Common Information About Timing
Tasks.
NE Upgrade Log
Export
For details, see Parameters for Creating/

Modifying/Copying the Export of NE
Upgrade Log.
NE Operation Log
Export
For details, see Parameters for the Export of

NE Logs.

Issue 03 (2010-12-31)
M2000
Task Type
Task Name
Reference
NE System Log
Export
NE Security Log
Export
Inventory Data Export
For details, see Parameters for Modifying the

Export of Inventory Data.
Alarm/Event Log
Export
For details, see Parameters for Setting Alarm/

Event Timing Export.
NM Operation Log
Export
For details, see Parameters for Setting M2000

Log Timing Export.
NM System Log
Export
NM Security Log
Export
Overflow Dump
Alarm Overflow
Dump
For details, see Parameters for Setting Alarm/

Event Overflow Dump.
Event Overflow Dump

Manual Dump
Alarm Manual Dump

Event Manual Dump
NIC
Issue 03 (2010-12-31)
For details, see Parameters for Dumping

Alarms/Events Manually.
NIC Configuration
Data Export
For details, see Parameters for Modifying a

NIC Configuration Data Export Task.
NE Basic Information
Export
For details, see Parameters for Modifying

NE Basic Information Export Task.
Network Logs
Collection
For details, see Parameters for Modifying

Network Log Data Collection Tasks.
Other
PM Object
Synchronization

Tasks.
Synchronization
NE Configuration
Data Synchronization

Synchronization of NE Configuration Data.
NE Log
Synchronization

Tasks.
Inventory Data
Synchronization

Synchronization of Inventory Data.
Alarm
Synchronization

Tasks.

6-33
M2000
Task Type
Backup
Task Name
Reference
Maintenance Mode
Synchronization

Tasks.
NE Upgrade Log
Synchronization

Tasks.
Server Backup
For details, see Parameter Description:

Modifying a Data Backup Task of the M2000.
User Scheduled Task

User scheduled tasks are tasks customized to meet the requirements of network maintenance.
l
You can create, modify, delete, or copy user scheduled tasks.
In the user scheduled tasks, some tasks can be suspended or canceled.
The M2000 uses

scheduled tasks.
to identify system scheduled tasks and uses
to identify user
For details about user scheduled tasks, see Table 6-11.

NOTE
The NEs that support CME tasks are the RNC, NodeB, BSC6000, BSC6900 GSM, BSC6900 UMTS and
BSC6900 GU. CME tasks are available only after the CME software corresponding to the NE version is
installed.
Table 6-11 Description of user scheduled tasks
6-34
Task
Type
Task Name
Description
Reference
Backup
NE Backup
The M2000 saves NE data in

backup files to a specified
directory on the server
periodically or on a scheduled
basis. The backup files are used
for restoring NEs in case of any
data loss or NE exception. You
can back up the data of the NEs
on the entire network, NEs of a
specified type, or specified NEs.
For details, see Parameters

for NE Backup.
NE License
Backup
The activated license files on NEs

are backed up and uploaded to a
specified directory on the
M2000 server on a scheduled
basis. The license files are used
for restoring NEs in case of any
license file loss or NE exception.
None.

Issue 03 (2010-12-31)
M2000
Task
Type
Task Name
Description
Reference
CM
Report
RAN Report
Export
The M2000 periodically exports

configuration reports in files to a
specified directory on the
M2000 server. You can use this
function to save data outside the
system. The exported data is still
stored in the database.

for Creating, Modifying, or
Copying a Configuration
Report Export Task.
These tasks are used for

collecting the information about
neighboring GSM cells for 3G
neighboring relation analysis.
None.
Core Network
Resource
Report Export
NE Report
Export
NE Statistic
Report Export
Link Report
Export
NIC
2G/3G
Neighboring
Cell
Optimization
This task is created on the Nastar.

You only need to view the task
progress on the M2000.
GSM MR Data
Collection
These tasks provide the

performance analysis tool with
MR data for network
optimization analysis. These
tasks are controlled by the
M2000 license.

for Creating a GSM MR
Data Collection Task.
RTWP Data
Collection
These tasks provide the Nastar

with NodeB interference data.
None.

Daemon NIC
Task

with various types of data, such
as the interference data, intrafrequency neighboring cell
optimization data, complaint
handling data of the CDMA
network, and the intra-frequency
neighboring cell optimization
data and coverage analysis data
of the UMTS network.
None.

Issue 03 (2010-12-31)

6-35
M2000
Task
Type
Other
6-36
Task Name
Description
Reference
Frequency
Scan

with uplink frequency data for
uplink interference analysis.
These tasks are controlled by the
M2000 license.

for Creating a Task of
Collecting the Uplink
ARFCN Data.
Neighboring
Cell
Optimization

with neighboring cell
optimization data for
neighboring cell analysis. These
tasks are controlled by the
M2000 license.
For details, see Creating a

Data Collection Task for
Neighbor Cell
Optimization.
MML Script
After an MML script is

configured, the M2000 issues the
commands in the script in batches
on a scheduled basis. Therefore,
you need not manually issue the
commands one by one.

for Creating/Modifying/
Copying MML Command
Script.
NodeB License
Timed
Distribution
The M2000 performs scheduled

tasks for allocates NodeB license
resources at a specified time, thus
reducing manual operations.

Copying Scheduled NodeB
License Allocation Tasks.
PRS Scheduled
Task
You can set PRS scheduled tasks

on the M2000 for the required
performance reports. Then, the
M2000 collects performance data
and generates performance
reports on a scheduled basis.
For details, see Parameter

Description: Creating,
Viewing, or Modifying a
Scheduled Report Task.
BSC/RNC
License Timed
Activation
The M2000 performs scheduled

tasks for downloading and
activating BSC/RNC license files
at a specified time, thus reducing
manual operations.

Copying Scheduled BSC
or RNC License Allocation
Tasks.
OMC Check
The M2000 checks its devices

and generates a check report
in .html format on a scheduled
basis. Therefore, hidden
problems of devices can be
identified and severe accidents
can be avoided.
For details, see 6.6 Check

OMC status.

Issue 03 (2010-12-31)
M2000
Task
Type
Task Name
Description
Reference
RSSI Test
The M2000 collects the RSSI

values of base stations in a
scheduled basis. Therefore,
exceptions in the base station
radio frequency (RF) subsystem
can be identified in time and
voice quality can be ensured.
Performing an RSSI test task
consumes a large number of
system resources. Therefore, you
are advised to perform such a task
only for batch test. Currently,
only CBTSs support RSSI test
tasks.
For details, see

Parameters for Creating/
Modifying/Copying an
RSSI Test Task.
NOTE
The portals of the RSST Test task
are as follows:
l Maintenance > Task
Management.
l Maintenance > RF
Performance Test > RSSI
Test.
Issue 03 (2010-12-31)
Upgrade
Checking
The M2000 checks whether the

services are functioning normally
after an NE is upgraded.

for Creating an NE
Upgrade Verification
Task.
NE Software
Download
NE mediation software is
downloaded from the M2000
server to a specified NE
periodically or on a scheduled
basis to ensure that the NE
version can be delivered to the
NE at the specified time.

Copying Software
Download.
Dual Home
Auto
Consistency
Check
Management
The M2000 checks the data of

NEs that have the dual-homing
relation periodically or on a
scheduled basis. Therefore, you
can ensure that an MSC server
can take over some or all data on
the other MSC server in case of a
dual-homing failover.
For details, see

Modifying/Copying a
Dual-Homing Auto
Consistency Check Task.

6-37
M2000
Task
Type
Task Name
Description
Reference
Alarm Check
The M2000 analyzes NE alarm

trends, comparisons between
alarms, TopN alarm features,
alarm maintenance, and fault
alarms and generates check
reports in .html format on a
scheduled basis, thus enabling
you to analyze network faults in
detail.

for Setting Special Alarm
Check Tasks.
Top Power
Test
The M2000 collects the value of

the transmit power on top of the
cabinet on a scheduled basis.
Therefore, exceptions in the base
station RF subsystem can be
identified in time and voice
quality can be ensured.
Performing a top power test task
consumes a large number of
system resources. Therefore, you
are advised to perform such a task
only for batch test. Currently,
only CBTSs support top power
test tasks.
For details, see

Modifying/Copying a
Task for Testing BTS
Cabinet-Top Power.
NOTE
The portals of the Top Power Test
task are as follows:
l Maintenance > Task
Management.
l Maintenance > RF
Performance Test > Top
Power Test.
CME
6-38
Script Timer
Task
By running the preset HSL

scripts, you can perform
operations such as modifying NE
parameters and obtaining alarm
data.
For details, see Parameter

Description: Script Timing
Task of the iSStar.
CME Upload
You can set a specified interval or

a time to upload user-selected NE
configuration data to the CME
server. Therefore, the CME can
obtain the latest NE data for data
configuration.
For details, see

Modifying/Copying a
CME Upload Task.

Issue 03 (2010-12-31)
M2000
Task
Type
NHC
Task Name
Description
Reference
Cell
Parameters
Compare
The M2000 compares the

parameters in the current data
area with the default parameters
in the CME configuration
template and then exports the
comparison results to a specified
path.
For details, see

Modifying/Copying Cell
Parameters Compare
Task.
Cell
Consistency
Check

data in the current data area
complies with the selected check
rules. Currently, the rules for
checking unidirectional
neighboring cells and cell
consistency are provided.
For details, see

Modifying/Copying Cell
Consistency Check Task.
Current Area
Export
The M2000 exports the data in

the current data area through
northbound interfaces, thus
facilitating the management of
the current data area.
For details, see

Modifying/Copying an
NE Configuration Data
Export Task.
Pre-alarm
Handling Task

mediation or the current NE is
normal and exports a report on a
scheduled basis.
None.
States of a Timing Task

A timing task has four states: idle, running, suspend and finished.
The states of a scheduled task change with different operations. For details, see Figure 6-7.
Issue 03 (2010-12-31)

6-39
M2000
Figure 6-7 State transition of a scheduled task

Start
Creating a timing task
Deleting a timing task
Restore
a timing task
Suspend
a timing task
Idle
Scheduling
Cancel
Running
Finish
Yes
a
ete
Del task
ME
aC
Terminate
a CME task
Terminate
a CME task
D
tim ele
in ting
g
ta
sk
Suspend
Archived
Another
Scheduling?
Scheduling
No
Ter
a C minate
ME
task
Deleting a timing task
Finished
End
State transition of a scheduled task is as follows:

l
A scheduled task is in the idle state after it is initially created.
An idle task is changed to the running state after being scheduled.
An idle task is changed to the suspended state after being suspended.
A running task is changed to the idle state after being cancelled.
A suspended task is changed to the idle state after being resumed.
If a task need not be scheduled after being performed, it is in the finished state. If it needs
to be scheduled again, it returns to the idle state.
When a timing task is in the idle or suspended state, you can delete the user timing task. Users
except admin can delete only the tasks created by themselves. The admin can delete the tasks
created by all users.
Technical Specifications of Integrated Task Management

This section describes the technical specifications related to the integrated task management
function.
6-40

Issue 03 (2010-12-31)
M2000
Function Category
Specification Item
Value
Centralized task
interface
Maximum size of MML task

execution results (unit: MB)
If the size of MML task

execution results exceeds 2 MB,
the results cannot be displayed
on the GUI. Users need to
download the results to the local
terminal through FTP and then
view them.
Centralized task
interface
Maximum size of the script

uploaded for an MML task (unit:
MB)
The maximum size of a script to

be uploaded is 1 MB.
User task
Total number of scheduled NE

backup tasks
50 (The number of NEs that can

be backed up through a task is
unlimited.)
User task
Total number of MML script

configuration tasks (including
dual-homing consistency check
tasks)
50
User task
Maximum number of scheduled

software downloading tasks
50
User task
Maximum number of iSStar

script tasks
500
User task
Maximum number of CME

uploading tasks
50
User task
Maximum number of dualhoming management tasks
50
User task
Maximum number of TMO

configuration import tasks
100
6.7.2 Customizing the Interface for Managing Timing Tasks

This describes how to customize the interface for managing timing tasks. The system can display
timing tasks of the specified function type in the navigation tree or display the timing tasks
meeting the condition in the task list.
Prerequisite
Procedure
Step 1 Choose Maintenance > Task Management.
Step 2 In the Task Management window perform different operations according to different
customized requirement.
Issue 03 (2010-12-31)

6-41
M2000
Customized Requirement
Operation
Customize the navigation tree 1. Right-click in the navigation tree and choose Filter
Type from the shortcut menu. The Filter Type dialog
box is displayed.
2. Select the timing task type to be displayed. By default,
all the timing task types that the current user is authorized
to browse are displayed.
Customize the task list
1. Right-click the task list and select Filter Task. The Filter
Task dialog box is displayed.
2. Set the User Name, Category, Task State, and Last
Run Result as the filtering conditions. For detailed
parameter description, refer to Parameters for Setting
Task Filter Conditions.
Step 3 Click OK.

----End
6.7.3 Creating a User Timing Task

This topic describes how to create a user timing task. Parameter setting varies according to
different tasks.
Prerequisite
You have logged in to the M2000 client successfully.
Context
l
To quickly create a task, you can copy a multi-instance user timing task (in this task, you
can create multiple subtasks) of user and then modify its parameters.
The instance quantity of the timing tasks of a specific type is restricted. If the instance
quantity of the existing timing tasks of a type reaches the maximum, you cannot create or
copy a timing task of this type.
Procedure
Step 2 In the Task Management window, create a user timing task.
You can create a user timing task by using one of the following methods:
l In general, click New.
l To quickly create a task of the specified type, double-click a user timing task in the Task
Type navigation tree.
l To quickly create a multi-instance user timing task whose parameter settings are similar to
those of the specified task, select the specified multi-instance user timing task, and then click
Copy.
6-42

Issue 03 (2010-12-31)
M2000
Step 3 In the New Task or Copy Task dialog box, set the parameters of the created user timing task.
Parameter
Setting
Common
Parameters
1. Set Task Name, Task Type, and Run Type. Do as follows:

l Task Name: Enter the task name in Task Name.
l Task Type: Select the type of the task to be created in the Task
Type navigation tree.
l Run Type: Select Once or Period in the Run Type area.
NOTE
The value of Run Type for part of tasks is fixed to Once or Period because of
their task types.
2. Click Next.
3. Set Start Time and Period Setting. Do as follows:
l Start Time: In the Time Setting area, set Start Time.
l Period Setting: In the Period Setting area, set Execution Interval,
and then select a periodic execution mode, namely, Execution
Times or End time.
NOTE
l For a one-time task, you can select Run At Once to run the task at once after
it's created.
l For a periodic task, you need to set the parameters in the Period Setting area.
Advanced
Parameters
Set advanced parameters according to the task requirements.

The created user timing task is displayed in the task list.
----End
6.7.4 Modifying a Timing Task

This section describes how to modify the attributes of a user timing task or a system timing task.
Prerequisite
You have logged in to the M2000 client successfully.
Context
Timing tasks are classified into System Scheduled Tasks and User Scheduled Task.
Procedure
Step 2 In the Task Management window, modify the attributes of a timing task.
You can modify a timing task by using one of the following methods:
Issue 03 (2010-12-31)

6-43
M2000

NOTE
Parameter modification varies according to the task type.
l Select a task from the task list, and then click Attribute. In the Attribute dialog box, modify
common and extended parameters.
l Double-click a task in the task list. In the displayed Attribute dialog box, modify common
and extended parameters.
----End
6.7.5 Managing Timing Tasks

User timing tasks refer to those timing tasks managed by the user. The user can delete, suspend,
resume, cancel, terminate, and roll back user timing tasks.
Suspending Timing Tasks

To delay the time for scheduling a task, you can suspend some idle timing tasks. After a task is
suspended, it is changed to the suspended state.
Prerequisite
l
At least one idle timing task exists.
Context
The M2000 can execute the tasks that are not suspended only through scheduling.
Procedure
Step 2 In the Task Management window, select Task Type in the navigation tree.
Step 3 Suspend one or more idle tasks with one of the following methods:
l Manual suspending
Select one or more tasks in the task list. Right-click the task and select Suspend. In the
Confirm dialog box, click Yes.
NOTE
If the Suspend menu item is not contained in the shortcut menu of a scheduled task, this task cannot
be suspended.
l Automatic suspending
Select a task in the task list. Right-click the task and select Timely Suspend/Resume. In the
Timely Suspend/Resume dialog box, select Suspend Time and then specify the time. Click
OK.
NOTE
If the Timely Suspend/Resume menu item is not contained in the shortcut menu of a scheduled task,
this task cannot be suspended.
6-44

Issue 03 (2010-12-31)
M2000
For details of setting an automatic suspend time, refer to Parameters for Setting the Timely
Suspend and Resume of a Timing Task.
----End
Resuming Timing Tasks

You can resume a suspended task. After that, the task becomes idle and is ready to be dispatched
by the system.
Prerequisite
l
At least one suspended scheduled task exists.
Context
Only idle tasks can wait to be used.
Procedure
Step 3 Resume the suspended task with one of the following methods:
l Manual resuming
Select one or more tasks in the task list in the right pane. Right-click the task and select
Resume. In the Confirm dialog box, click Yes.
l Automatic resuming
Select a task in the task list in the right pane. Right-click the task and select Timely Suspend/
Resume. In the Timely Suspend/Resume dialog box, select Resume Time and then specify
the time. Click OK.
For details of setting an automatic restore time, refer to Parameters for Setting the Timely
Suspend and Resume of a Timing Task.
----End
Setting Time of Timing Tasks

You can set an automatic suspend time or an automatic restore time for a scheduled task. In this
situation, the M2000 automatically suspends the task or restores the task.
Prerequisite
l
At least one suspended or idle timing task exists.
The system suspends an idle task and delay the time for using this task. If the timing task
is not in the Idle state at the specified time, it fails to be suspended.
Context
Issue 03 (2010-12-31)

6-45
M2000
In the specified time, the system resume a suspended task and then the task is in the idle
status and wait to be dispatched. If the timing task is not in the Idle state at the specified
time, it fails to be suspended.
You are not allowed to set auto-suspend or resume a Running timing task.
Procedure
Step 2 In the navigation tree, select the task type of which you plan to suspend.
Step 3 From the task list in the right part of the window, select a timing task to be suspended.
Step 4 Right-click the task and choose Timing Suspend/Resume.
Step 5 In the displayed Timing Suspend/Resume dialog box, select Suspend Time or Resume
Time as required.
Step 6 Set the suspend time or resume time.
For details of setting an automatic suspend time or an automatic restore time, refer to Parameters
for Setting Time of Timing Tasks.
----End
Cancelling Timing Tasks

You can cancel a running task. The task status is changed to idle after being cancelled.
Prerequisite
l
At least one Running timing task exists.
Context
A user in the common user group can cancel only the tasks created by himself. A admin can
cancel the timing tasks created by all users.
Procedure
Step 3 Select one or more running tasks in the task list in the right pane. Right-click the task and select
Cancel.
NOTE
If the Cancel menu item is not contained in the shortcut menu of a scheduled task, this task cannot be
cancelled.
Step 4 In the Confirm dialog box, click Yes.

Then the status of the task is changed from running to idle.
----End
6-46

Issue 03 (2010-12-31)
M2000
Deleting Timing Tasks

You can delete the tasks created by yourself according to the actual requirements to save system
resources.
Prerequisite
l
At least one timing task exists.
Users can delete only the tasks created by themselves. The admin can delete the tasks
created by all users.
System tasks cannot be deleted.
Running tasks cannot be deleted.
Context
Procedure
Step 3 Select one or more scheduled tasks in the task list in the right pane.
Step 4 Click Delete.
Step 5 In the Confirm dialog box, click Yes.
Then the task is deleted from the task list.
----End
6.7.6 Viewing Timing Tasks

Through the M2000 function of viewing timing tasks, you can view the status of all timing tasks
in a centralized manner. This helps you adjust the concerned timing tasks according to actual
conditions.
Browsing the Information of Timing Tasks

On the M2000, you can browse information about timing tasks such as the task name, user name,
process, and execution result according to your own permissions.
Prerequisite
l
Procedure
Issue 03 (2010-12-31)

6-47
M2000

NOTE
l The task list area on the right displays the information about the tasks that can be viewed by the current
user.
l If you want to view the common parameters and extended parameters of each task, go to Step 3
l Part of periodic tasks support the function of downloading the log file of task execution results from
the server. The downloaded log file is saved to the client. Thus, the user can view the history execution
results of periodic tasks at any time:
1. Select the tasks that support log file download, and then click Save Log.
2. In the Selecting the Logs to Be Saved dialog box, select the log file to be saved, and then click
OK.
3. In the Select Folder dialog box, select the path for saving the log file, and then click Select.
Step 3 Double click a task, or select a task and click Attribute.

The Attribute dialog box is displayed. In the Common Parameter tab and Extended
Parameter tab, you can view the task details.
NOTE
l If State of a task is Finished, you can view the task information only.
l If State of a task is Idle, Suspend, or Running, you can modify the task details in the Attribute dialog
box.
----End
Viewing the Task Execution

You can view the last execution results of a timing task.
Prerequisite
l
During the creation of CME tasks, sub-tasks are created, which are executed in different
phases.
You can browse the execution progress of subtasks of CME tasks.
Context
Procedure
l View the execution conditions in the Prev Execution Result column in the task list in the
right pane.
l You can check the result details in the Result Information area.
----End
Viewing the Task Execution

You can view the last execution results of a timing task.
6-48

Issue 03 (2010-12-31)
M2000
Prerequisite
l
During the creation of CME tasks, sub-tasks are created, which are executed in different
phases.
You can browse the execution progress of subtasks of CME tasks.
Context
Procedure
l View the execution conditions in the Prev Execution Result column in the task list in the
right pane.
l You can check the result details in the Result Information area.
----End
6.7.7 Downloading Task Execution Tasks

You can download the execution file of NodeB license allocation tasks to a local PC and then
check the specific resource allocation information.
Prerequisite
l
NodeB license allocation tasks are available in the system.
Procedure
Step 2 In the navigation tree, choose Task Type > Other > NodeB License Timed Distribution.
Step 3 In the task list on the right, right-click a task, and then choose Download Task File from the
shortcut menu to download the license resource allocation file set in the task to a local PC.
----End
6.7.8 Downloading Result Files

This describes how to download the results of timing tasks. You can save the results of timing
tasks on the server to the local client in .txt format.
Prerequisite
l
The timing task that is used for downloading the result files exists and it is run for at least
once.
Issue 03 (2010-12-31)

6-49
M2000
Context
The allowable operations vary depending on the task type, as shown in Table 6-12.
Table 6-12 Allowable operations for different task types
Task Type
Allowable Operation
iSStar Script Executor

or Pre-alarm Handling
task
The task result are saved on the server in logs. The Result Info area
displays only the information about the last task execution. The
result logs are not displayed.
You can download all the result files to the local client. Result files
of multiple tasks can be downloaded concurrently.
MML Script task
You can download the latest result file to the local client. Result
files of multiple tasks can be downloaded concurrently.
Health Check task
You can download the result file of the selected task. Result files
of multiple tasks can be downloaded concurrently.
Dual Home
Management task
You can view the latest consistency check result on line.
Timing task, NE
Software Download
task, and NE Backup
task
If a task is performed at least once, you can save the messages in

the Result Info area to a local path.
Procedure
Step 2 In the navigation tree, select the type of the task that is used to download the result files. Select
the specific tasks in the right pane.
Step 3 Perform the following operations according to the task type.
6-50

Issue 03 (2010-12-31)
M2000
Task Type
Procedure
iSStar Script Executor or Pre-alarm

Handling task
To download the result logs of a download task,

perform the following steps:
1. Select the task whose result logs you plan to
download.
2. Click Save Log. In the displayed Please select
a directory dialog box, set the save path
3. Click OK.
NOTE
The system generates a folder for the log file
generated each time and saves the folder to the
specified path. The result log file is named in the
format YYYY-MM-DD_HH-MM-SS, for example,
2008-04-18_10-27-53.
MML Script task
To download the result files of a single task, do as

follows:
1. Select the MML script task whose result files
you plan to download.
2. Right-click a task and choose Save MML
Result on the shortcut menu. Alternatively, you
can right-click the Result Info field and choose
Save AS on the shortcut menu.
3. Set the save path in the displayed Save dialog
box, and then click Save.
To download the result files of multiple tasks, do as
follows:
1. Press Ctrl or Shift to select multiple MML script
tasks in the task list.
2. Right-click the tasks and choose Save MML
Result on the shortcut menu.
box, and then click Save. Save the execution
results of multiple MML script tasks to the same
file.
Issue 03 (2010-12-31)

6-51
M2000
Task Type
Procedure
OMC Check or Alarm Check task
1. Select the task whose result files you plan to

download.
2. Right-click a task and choose NHC Report on
the shortcut menu.
3. In the displayed NHC Report dialog box, select
the check report based on Report Name and
then click Save.
NOTE
You can click Open to view the contents of the check
report and decide whether the report needs to be
downloaded.
4. Set the save path in the displayed Please select

a directory dialog box.
5. Click OK.
Dual Home Management task
Right-click a task and choose Checked Result from

the shortcut menu.
NOTE
If data inconsistency exists, you need to generate a script
to adjust the data difference and synchronize the data.
Timing task, NE Software Download

task, and NE Backup task
To download the result information about a

download task, perform the following steps:
1. Select a task whose result information needs to
be downloaded.
2. Right-click in the Result Info area can choose
Save As from the shortcut menu.
box, and then click Save.
----End
6.7.9 Reference of the OSS Management GUI

This part describes the OSS management interfaces and related information such as the
parameters used in the OSS management. This helps you understand the functions of OSS
management easily.
Interface Description: Managing Scheduled Tasks

This section describes the Task Management window and relevant parameters. You can refer
to this part when performing related operations.
After you log in to the server, the Task Management window is displayed, as shown in Figure
6-8. For the description of Figure 6-8, see Table 6-13.
6-52

Issue 03 (2010-12-31)
M2000
Figure 6-8 Task Management window
Table 6-13 Description of the Task Management window
Issue 03 (2010-12-31)
No.
Name
Description
Navigation tree
You can locate the object of a scheduled

task through the navigation tree.
Task result information

panel
After a task is completed, the task result is

displayed on the task result information
panel. You can browse through the result
of the latest task on the panel. Only the
result of the currently selected task is
displayed on the panel. If multiple tasks are
selected in the task list, the result of only
the firstly selected task is displayed.
Button panel
The buttons used for performing central

task management are available on the
button panel.
Task list
You can browse through the scheduled

tasks existing on the server and their
details. In the task list, different colors
indicate different task statuses. Gray:
complete; Orange: suspended; Blue:
active; White: idle. After you select a task
in the list, the color of the task becomes
darker than before.

6-53
M2000
Parameters for Setting Task Filter Conditions

This topic describes the parameters in the Filter Task dialog box. When you set filter conditions
for a task list, you can refer to this topic.
Parameters
Parameter
Description
User
Name
Description:
Current User
Indicates the user that operates the client.

Other Users
Description:
Indicates other users except the current user.
Catego
ry
User Task
Description:
Indicates the task created by users.
System Task
Description:
Indicates the task created by OMC during the system installation
or upgrade.
Task
State
Idle
Description:
Indicates that the task waits for being performed by the system.
Running
Description:
Indicates that the task is being performed by the system.
Suspend
Description:
The task is not ready to be scheduled.
Finished
Description:
Indicates that the task is completed by the system.
Last
Run
Result
Success
Description:
Indicates that the task is successfully carried out.
Processing
Description:
Indicates that the task is being processed by the system.
Partly
Success
Description:
Failed
Description:
Indicates that the task is partly successfully carried out.
Indicates that the task fails to carry out.

Miss Run
Time
6-54
Description:
Indicates that the task misses the previous performed time. If the
server is not running properly or the task is suspended before the
execution, the task may miss the previous execution.

Issue 03 (2010-12-31)
M2000
Parameter
Description
Unknown
Description:
Indicates that the previous execution result in the server is lost
caused by improper service or sudden power cut. Thus, after
recovery, the previous execution result cannot be determined.
Parameters for Setting the Common Information About Timing Tasks

This topic describes the common parameters of all timing tasks. When you create or copy a user
timing task or when you modify a user or system timing task, you can refer to this topic.
Parameters
Table 6-14 Parameters Applicable for both Once and Period Tasks
Parameter
Description
Settings
Task name
Description:
Value:
Refers to the name of a timing task.
l A maximum of 60 characters
l Unique and not null
l Case sensitive
Run type
Description:
Value:
l Once: If you select this option,

the system runs the created task
once at the defined time point.
l Once
l Period
l Period: If you select this option,

the system runs the created task
periodically.
Start time
Description:
Value:
This parameter sets the time for

starting a task.
The start time should be later than the

time displayed on the server.
NOTE
For a one-time timing task, if you have
selected Run At Once, the Start time
parameter is invalid. The task is performed
immediately after the related settings are
complete.
Task type
Description:
Refers to the type of a timing task.
Issue 03 (2010-12-31)

6-55
M2000
Table 6-15 Parameters Only Applicable for Period Tasks

Parameter
Description
Settings
Execution
Interval
(When you
create a user
timing task,
the parameter
is displayed as
Execution
Interval.)
Description:
Value:
Interval between periodic tasks. It

has two enlistments: duration and
unit.
l The period can be represented in

either of the following units:
minutes, hours, days, weeks,
months. The period, however,
cannot be represented in seconds.
The supported units of Period vary
according to the task type.
Execution
Times
Description:
Value:
This parameter indicates the times

that a periodic task is executed.
0 - 65535
l The value range for period should

be as follows: Minute (1 - 366 x 24
x 60), Hour (1 - 366 x 24), Day (1
- 366), Week (1 - 52), Month (1 12).
NOTE
This parameter is displayed in the
Attribute dialog box only after you
set it when creating and copying a
periodic task.
End time
NOTE
0 indicates that the number of times for
executing periodic tasks is not restricted.
Description:
Value:
End time of a periodic task.
Later than Start time, and earlier than

12/31/2038 23:59:59.
NOTE
This parameter is displayed in the
Attribute dialog box only after you
set it when creating and copying a
periodic task.
Parameters for Setting the Timely Suspend and Resume of a Timing Task
This topic describes the parameters of auto-suspend time and auto-resume time for timing tasks.
6-56

Issue 03 (2010-12-31)
M2000
Parameters
Name
Description
Settings
Suspend Time
Description:
Setting method:
At the time specified by the user,

the system suspends the idle
timing task that is not executed to
delay the task dispatch. If the
timing task is not in the idle state
at the specified time, the
suspension fails.
You can set the value manually.

Alternatively, you can click
and select the time from the time
select panel.
The time format is MM/DD/YYYY
HH:MM:SS.
l MM stands for the month.
l DD stands for the date.
l yyyy stands for the year.
l HH stands for the hour.
l MM stands for the minute.
l SS stands for the second.
Resume Time
Description:
Setting method:
At the specified time, the system

resumes a suspended task and
then the task is in the idle state and
wait to be dispatched. If the timing
task is not in the suspended state
at the specified time, the
suspension fails.
For details on how to set the

resume time, refer to the
description of the Suspend Time
parameter.
Parameters for Modifying NE Basic Information Export Task

This section describes the parameters involved in the NE basic information export task. When
modifying an NE basic information export task, you can refer to this part and perform relevant
operations.
Parameter description
The M2000 provides the function of exporting NE basic information. Thus, it can provide data
to the Nastar for performance analysis. You can modify the common parameters and extended
parameters of the task according to the actual requirement.
Issue 03 (2010-12-31)
Parameter
Description
Exported File
Export the file containing NE basic information to

the /export/home/omc/var/fileint/network/
EAMInfo.xml path on the M2000 server.
Export All NE
The NE navigation tree is unavailable. You need not

specify the NEs to be exported. The M2000 exports the
information about all NEs.

6-57
M2000
Parameter
Description
Export By NE Type
After you select a certain NE type from the NE

navigation tree, the M2000 exports the information
about all NEs of this type.
Export By NE
After you select some NEs from the NE navigation

tree, the M2000 exports the information about all
selected NEs.
Parameters for Modifying a NIC Configuration Data Export Task

This section describes the parameters of NIC Configuration Data Export tasks. You can refer
to this part when modifying parameters.
Parameter Description
For details about the extended parameters of NIC Configuration Data Export tasks, see Table
6-16.
Table 6-16 Extended parameters of NIC Configuration Data Export tasks
Parameter
Value Range
Description
Export Path
Default value. No
change.
Refers to the path for saving the exported

configuration data files on the M2000 server.
The default path

is /export/home/
omc/var/fileint/
cm/GExport.
File Save Time
Default value. No
change.
Refers to the storage duration of the exported

configuration data files on the M2000 server.
The default storage

duration is 3 days.
File Need
Compressed
Default value. No
change.
The default value
is Yes.
6-58
Determines whether to decompress the exported

configuration data files before saving them on the
M2000 server.

Issue 03 (2010-12-31)
M2000
Parameter
Value Range
Description
Export NEs
You need to select

NEs in the
navigation tree
according to the
actual
requirement.
l Export All NE:

The M2000 will export the configuration data of
all NEs.
l Export By NE Type:
After you select the required NE type, the
M2000 will export the configuration data of all the
NEs of this type.
l Export By NE:
After you select the required NEs, the M2000 will
export the configuration data of all the selected
NEs.
Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top

Power
This section describes the parameters of a task for testing BTS cabinet-top power. You can refer
to this section when creating or modifying such a task.
NOTE
The portals of the Top Power Test task are as follows:

l Maintenance > Task Management.
l Maintenance > RF Performance Test > Top Power Test.
Parameter
Value Range
Description
Execution
Duration
3-120 minutes
Maximum execution duration of a task
NE
None
Existing NE that supports cabinet-top power

test.
Parameters for Creating/Modifying/Copying an RSSI Test Task

This section describes the parameters of an RSSI test task. You can refer to this section when
creating or modifying an RSSI test task.
NOTE
The portals of the RSST Test task are as follows:

l Maintenance > Task Management.
l Maintenance > RF Performance Test > RSSI Test.
Issue 03 (2010-12-31)

6-59
M2000
Parameter
Value Range
Description
Execution
Duration
3-120 minutes
Maximum execution duration of a task
NE
None
Existing NE that supports RSSI test.
Frequency
0-2047
Frequency to be tested in an RSSI task.
The default value is null,

which indicates that all
frequencies are tested.
Parameters for Creating/Modifying/Copying a Dual-Homing Auto Consistency

Check Task
This section describes the parameters for creating, modifying, or copying a dual-homing auto
consistency check task.
Parameter
Description
Setting
Dual Homing Pairs
Indicates the dual-homing

pairs whose data is to be
checked.
Resource Type
Indicates the data resource

type of the dual-homing pairs
to be checked.
l Select the corresponding item

in the Resource Type
navigation tree.
Data resource types vary

according to the version of the
dual-homing pair NE.
l Type a data resource type or

keyword in Search. Then the
related resource types are
listed in the area under
Search. You can doubleclick a resource type to be
checked.
Is used to search for the type of

the data resource to be
checked. Case-insensitive
search rather than wildcard
search is supported.
Type a data resource type or

keyword in Search.
Search
Parameters for Creating/Modifying/Copying the Export of NE Upgrade Log

This describes the parameters for exporting NE logs and can be taken as reference during the
parameter modification.
Table 6-17 lists the extended parameters.
6-60

Issue 03 (2010-12-31)
M2000
Table 6-17 Description of extended parameters

Parameter
Value Range
Description
Please Select NE
None.
Refers to all the NEs on the entire

network.
Start Time
The start time must meet the

requirement of time format.
All NE upgrade logs within the

time range specified by the start
time and end time are to be
queried.
End Time
The end time must meet the

requirement of time format.
All NE upgrade logs within the

time range specified by the start
time and end time are to be
queried.
File Format
The default file format must be

retained.
Operation logs are exported

to .xml files.
File Path
The default file path must be

retained.
Refers to the path for saving NE

logs.
The default path is /export/

home/omc/var/field/
UpgradeHistory/.
Parameters for Creating/Modifying/Copying a CME Upload Task

This describes the parameters of a CME upload task. When creating or modifying a CME upload
task, you can refer to the parameter description and perform relevant operations.
Parameter
Description
All NE
After you select this option, the system uploads the configuration data
of all the NEs that support CME tasks on the network. The NEs that
support CME tasks are the RNC, NodeB, BSC6000, BSC6900 GSM,
BSC6900 UMTS and BSC6900 GU.
All NodeBs Under

RNC
After you select this option, the system uploads the configuration data
of all the NodeBs under the selected RNCs.
Please Select NE
Indicates the NEs of all the existing RNCs and NodeBs in the entire
network. Multiple NEs are supported. You can select the specific NEs
in Please Select NE only after you clear All NE.
Parameters for Creating/Modifying/Copying Cell Parameters Compare Task

This describes the parameters involved in the CME cell algorithm comparison task. When
creating or modifying a CME cell algorithm comparison task, you can refer to this part and
perform relevant operations.
Issue 03 (2010-12-31)

6-61
M2000
A CME cell algorithm comparison task can be performed to compare the parameters in the
Current area with the default parameters in the CME configuration template and then export the
comparison results to the specified path.
Parameter
Description
Cell Input Mode
Select the NE of a Cell

and the Template
Select the NE of a Cell
After you select this mode, you can

specify the NEs of a cell whose
parameters are to be compared.
Import Cell
After you select this mode, you can

import the list of cells whose
parameters are to be compared.
NE
Select the name of the controller

managing the cell. The M2000
automatically compares the
parameters of all the cells managed by
the selected controller.
Template
Select the template to be compared.

The M2000 automatically compares
the cell parameters with the default
configuration parameters of the
selected template. For example, you
can select Default 2G Cell
Template.
Parameters for Creating/Modifying/Copying Cell Consistency Check Task

This describes the parameters involved in the CME cell consistency check task. When creating
or modifying a CME cell consistency check task, you can refer to this part and perform relevant
operations.
Parameter description
A cell consistency check task can be performed to check that the data in the Current area complies
with the selected check rules.
Parameter
Description
NE
Select the name of the controller managing the cell.

The M2000 automatically compares the parameters of
all the cells managed by the selected controller.
Rule
Select check rules.
Parameters for Creating/Modifying/Copying an NE Configuration Data Export

Task
The CME supports the export of NE configuration data in the current area for the northbound
interface, which facilitates current area management. This section describes the parameters
6-62

Issue 03 (2010-12-31)
M2000
involved in an NE configuration data export task. You can refer to this section when creating or
modifying an NE configuration data export task and setting related parameters on the CME.
Parameters involved in GBSS/WRAN NE data export tasks

Parameter
Description
Select Export Type
Select the data to be exported and its file format. The

following parameter values are optional:
l XML format:
Transport parameters
Radio and transport parameters
Radio parameters
l CSV format:
Radio parameters
Transport parameters
Radio and transport parameters
Select one or multiple controllers that control the cells
whose data is to be exported. If you select All NEs, the
current area data under all GBSS and WRAN
controllers is to be exported.
Select NE
Parameters involved in eNodeB data export tasks

Parameter
Description
Select Export Type
Select the data to be exported and its file format:

XML format:
l Transport parameters
l Radio and transport parameters
l Radio parameters
Issue 03 (2010-12-31)
Select NE
Select one or multiple eNodeBs that control the cells

whose data is to be exported. If you select NE, the data
of all eNodeBs in the current area is to be exported.
Select Export Mode
Select One file including one eNodeB or One file

including multi-eNodeB.

6-63
M2000
Managing the M2000 Processes and Services

(SUSE)
About This Chapter

This describes how to manage the M2000 processes so that the processes and services on the
M2000 server can function properly.
7.1 Introduction to M2000 Processes and Services
When the M2000 is running, the M2000 server automatically starts the processes related to the
M2000 system. Each process provides different services and functions.
7.2 Managing the M2000 Services (SUSE)
This describes how to view, start, and stop M2000 services.
Issue 03 (2010-12-31)

7-1
M2000
7.1 Introduction to M2000 Processes and Services

When the M2000 is running, the M2000 server automatically starts the processes related to the
M2000 system. Each process provides different services and functions.
7.1.1 3rdTool_agent Process
This section describes the 3rdToolService service and dependent services.
7.1.2 adn_agent Process
This section describes the services and functions provided by the adn_agent process.
7.1.3 adss_agent Process
This section describes the services and functions provided by the adss_agent process.
7.1.4 antenna_agent Process
This section describes the services and functions provided by the antenna_agent process.
7.1.5 ce_agent Process
This section describes the services and functions provided by the ce_agent process.
7.1.6 cmdc_agent Process
This section describes the CmDcService service and dependent services. CmDcService is
provided by the cmdc_agent process.
7.1.7 cmengine_agent Process
This section describes the services and functions provided by the cmengine_agent process.
7.1.8 cmeserver_agent Process
This section describes the services and functions provided by the cmeserver_agent process.
7.1.9 cmexp_agent Process
This section describes the service and functions provided by the cmexp_agent process.
7.1.10 cmserver_agent Process
This section describes the services and functions provided by the process cmserver_agent.
7.1.11 cnnhc_agent Process
This section describes the services and functions provided by the cnnhc_agent process.
7.1.12 corba_agent Process
This section describes the services and functions provided by the corba_agent process.
7.1.13 cpm_agent Process
This section describes the services and functions provided by the cpm_agent process.
7.1.14 devdoc_agent Process
This section describes the DevDocService service provided by the devdoc_agent process.
7.1.15 dsXXXX agent Process
This section describes the services and functions provided by the dsXXXX_agent process.
7.1.16 eam_agent Process
This section describes the services and functions provided by the eam_agent process.
7.1.17 em agent Process
This section describes the services and functions provided by the em_agent process.
7.1.18 fars_agent Process
7-2

Issue 03 (2010-12-31)
M2000
This section describes the service and function provided by the fars_agent process.
7.1.19 fmnotify_agent Process
This section describes the services and functions provided by the fmnotify_agent process.
7.1.20 FMPreServiceXXXX_agent Process
This section describes the services and functions provided by the FMPreServiceXXXX_agent
process.
7.1.21 fnlicense_agent Process
This section describes the services and functions provided by the fnlicense_agent process.
7.1.22 glmssyn_agent Process
This section describes the services and functions provided by the glmssyn_agent process.
7.1.23 ifms_agent Process
This section describes the service and functions provided by the ifms_agent process.
7.1.24 ipm_agent Process
This section describes the services and functions provided by the ipm_agent process.
7.1.25 irp_agent Process
This section describes the functions provided by the irp_agent process.
7.1.26 itm_agent Process
This section describes the ItmService service and the dependent services by the itm_agent
process.
7.1.27 lic_agent Process
This chapter describes the services and functions provided by the process lic_agent.
7.1.28 log_agent Process
This section describes the LogService service and dependent services. LogService is provided
by the log_agent process.
7.1.29 maintain_agent Process
This topic describes the function of the MaintenanceService service, which is provided by the
maintain_agent process.
7.1.30 manager_agent Process
This section describes the services and functions provided by the manager_agent process.
7.1.31 medXXXX_agent Process
This section describes the services and functions provided by the medXXXX_agent process.
7.1.32 necomm_agent Process
This section describes the services and functions provided by the necomm_agent process.
7.1.33 nelicense_agent Process
This section describes the services and functions provided by the nelicense_agent process.
7.1.34 neuser_agent Process
This section describes the NeUserService service. NeUserService is provided by the
neuser_agent process.
7.1.35 ngnffs_agent Process
This section describes the NGNFullFillService service and dependent services.
7.1.36 ngnnis_agent Process
This section describes the NGNNIService service and dependent services.
Issue 03 (2010-12-31)

7-3
M2000
7.1.37 ngnni112_agent Process

This section describes the services and functions provided by the ngnni112_agent process.
7.1.38 ngntestmanage_agent Process
This section describes the services and functions provided by the ngntestmanage_agent process.
7.1.39 nhcservice_agent Process
This section describes the services and functions provided by the nhcservice_agent process.
7.1.40 nicservice_agent Process
This section describes the services and functions provided by the nicservice_agent process.
7.1.41 nimserver_agent Process
This section describes the NIMServer service and the dependent service. NIMServer is provided
by the nimserver_agent process.
7.1.42 nms_mml_agent Process
This section describes the services and functions provided by the process nms_mml_agent.
7.1.43 partition_agent Process
This section describes the services and functions provided by the partition_agent process.
7.1.44 pm_agent Process
This section describes the services and functions provided by the process pm_agent.
7.1.45 pmexp_agent Process
This section describes the services and functions provided by the process pmexp_agent.
7.1.46 pmmon_agent Process
This section describes the services and functions provided by the process pmmon_agent.
7.1.47 pmncdXX01_agent Process
This section describes the services and functions provided by the pmncdXX01_agent process.
7.1.48 porttrunk_agent Process
This section describes the services and functions provided by the porttrunk_agent process.
7.1.49 proxy_agent Process
This section describes the services and functions provided by the proxy_agent process.
7.1.50 PRSAssistantService_agent Process
This section describes the services and functions provided by the PRSAssistantService_agent
process.
7.1.51 prsdc_agent Process
This section describes the services and functions provided by the prsdc_agent process.
7.1.52 prsfs_agent Process
This section describes the services and functions provided by the prsfs_agent process.
7.1.53 prsreport_agent Process
This section describes the services and functions provided by the prsreport_agent process.
7.1.54 prssum_agent Process
This section describes the services and functions provided by the prssum_agent process.
7.1.55 rn_agent Process
This section describes the services and functions provided by the rn_agent process.
7.1.56 ScriptModuleService_agent Process
7-4

Issue 03 (2010-12-31)
M2000
This section describes the services and functions provided by the ScriptModuleService_agent
process.
7.1.57 scriptserver_agent Process
This section describes the services and functions provided by the process scriptserver_agent.
7.1.58 sm_agent Process
This section describes the services and functions provided by the process sm_agent.
7.1.59 snmp_agent Process
This section describes the SnmpAgent service and the dependent services. The SnmpAgent
service is provided by the snmp_agent process.
7.1.60 son_agent Process
This section describes the services and functions provided by the son_agent process.
7.1.61 sso_agent Process
This section describes the services and functions provided by the sso_agent process.
7.1.62 swm_agent Process
This section describes the services and functions provided by the swm_agent process.
7.1.63 threshold_agent Process
This topic describes the function of the ThresholdService service provided by the
threshold_agent process and the service that the threshold_agent process depends on.
7.1.64 uap_agent Process
This section describes the services and functions provided by the uap_agent process.
7.1.65 udpdispatch_agent Process
This section describes the services and functions provided by the udpdispatch_agent process.
7.1.66 umgupdsvr_agent Process
This section describes the services and functions provided by the umgupdsvr_agent process.
7.1.67 xftpXX01_agent Process
This section describes the services and functions provided by the xftpXX01_agent process.
7.1.68 Processes and Services Related to Each Northbound Interface
This section describes the processes and services related to each northbound interface.
rectify the faults.
7.1.1 3rdTool_agent Process

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

This section describes the services and functions provided by the adn_agent process.
Issue 03 (2010-12-31)

7-5
M2000
The adn_agent process provides the ADNService service.

The ADNService service supports the NodeB plug-and-play function. It provides various
functions for newly constructed NodeBs, such as remote automatic activation and automatic
fault detection. This helps engineers quickly deploy NodeBs.
You can disable the service when it is not required.
Required services: PartitionService
7.1.3 adss_agent Process

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

This section describes the services and functions provided by the antenna_agent process.
The antenna_agent process provides the AntennaTune service.
The AntennaTune service provides the functions of managing NodeB antennas and locating the
faults related to GBSS antennas.
Required service: EAMService.
7.1.5 ce_agent Process

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

This section describes the CmDcService service and dependent services. CmDcService is
provided by the cmdc_agent process.
The cmdc_agent process provides the CmDcService service.
The CmDcService service provides the functions such as data access interface, synchronization
management, and session management.
Required services: TopoAdapterService
7-6

Issue 03 (2010-12-31)
M2000
7.1.7 cmengine_agent Process

This section describes the services and functions provided by the cmengine_agent process.
The cmserver_agent process provides the CMEngine service.
CMEngine manages the configuration of the network manager. Configuration management is
independent of NEs or managed objects.
When the M2000 is running, ensure that this service functions properly.
Required services: TopoAdapterService.
7.1.8 cmeserver_agent Process

This section describes the services and functions provided by the cmeserver_agent process.
The cmeserver_agent process provides the CmeServer service.
The cmeserver_agent service provides the function of quickly configuring NEs.
You can disable the service when it is not required.
Required service: none.
7.1.9 cmexp_agent Process

This section describes the service and functions provided by the cmexp_agent process.
The cmexp_agent process provides the CMExport service.
The CMExport service provides the functions of exporting configuration files and exporting the
configuration database.
Through the CMExport service, you can set the NE whose configuration data is to be exported,
set the save path and file format of the exported data, and export the NE configuration data by
using the Management Information Tree (MIT).
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.
7.1.10 cmserver_agent Process

This section describes the services and functions provided by the process cmserver_agent.
The cmserver_agent process provides the CMServer service.
CMserver configures the managed objects of the network manager. Configuration management
is independent of NEs or managed objects.
The CMServer provides channels for issuing MML commands and helps to receive the
supplementary messages reported automatically by NEs.
The CMServer provides the function of managing object groups and enables the M2000 to
automatically and remotely commission the NodeB upgrade.
Issue 03 (2010-12-31)

7-7
M2000
Required services: TopoAdapterService
7.1.11 cnnhc_agent Process

This section describes the services and functions provided by the cnnhc_agent process.
The cnnhc_agent process provides the CNNHCService service.
CNNHCService provides the functions of information collection and health check.
7.1.12 corba_agent Process

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

This section describes the services and functions provided by the cpm_agent process.
The cpm_agent process provides the CPMService service, that is, the pool configuration
management service.
The Pool configuration management service provides users with the following functions:
l
Creating a pool
Checking pool alarms
Measuring the performance of a pool
Monitoring the load of a pool in real time
Displaying the pool topology
Setting pool parameters
Checking the NE data in a pool
Checking the MSC Server or MSCe of a specific user
7.1.14 devdoc_agent Process

This section describes the DevDocService service provided by the devdoc_agent process.
The devdoc_agent process provides the DevDocService service.
The DevDocService service enables you to manage device files.
7.1.15 dsXXXX agent Process

This section describes the services and functions provided by the dsXXXX_agent process.
The dsXXXX_agent process provides the DesktopServiceXXXX service.
7-8

Issue 03 (2010-12-31)
M2000
Some typical process names are ds0101_agent and ds0102_agent. The corresponding service
names are DesktopService0101 and DesktopService0102.
dsXXXX_agent is a multi-instance process and XXXX indicates the process number.
The DesktopServiceXXXX service presents and operates data on several types of clients such as
the Java GUI client and the Web client.
You can log in to the client only when the DesktopServiceXXXX service is running properly.
7.1.16 eam_agent Process

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

This section describes the services and functions provided by the em_agent process.
The cmserver_agent process provides EventService.
EventService provides a mechanism for transmitting messages between NMS services, and
between the NMS server and client. It also broadcasts and filters messages.
Required services: None.
7.1.18 fars_agent Process

This 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 data
collection management.
To enable the tracing function, you need to ensure that the FarsService is running normally
during the operation of the M2000.
Dependent service: none.
Issue 03 (2010-12-31)

7-9
M2000
7.1.19 fmnotify_agent Process

This section describes the services and functions provided by the fmnotify_agent process.
The fmnotify_agent process provides the FMNotify service.
FMNotify forwards the alarm data from FaultManager to the network management system
(NMS) by Alarm Streaming Interface.
Disable FMNotify when the real-time alarm forwarding function is not required.
Required services: LicenseService.
7.1.20 FMPreServiceXXXX_agent Process

This section describes the services and functions provided by the FMPreServiceXXXX_agent
process.
The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service.
The FMPreServiceXXXX_agent process is a multi-instance process. XXXX indicates the process
number.
The FMPreServiceXXXX service provides the function of prehandling faults.
In the ATAE cluster system, you can deploy the FMPreServiceXXXX_agent process on the
master node and several slave nodes. You can also deploy multiple FMPreServiceXXXX_agent
processes on one node. For example, you can deploy the FMPreService0101_agent,
FMPreService0102_agent, and FMPreService0103_agent processes on the master node for
providing the FMPreService0101, FMPreService0102, and FMPreService0103 services
separately. You can also deploy the FMPreService0201_agent, FMPreService0202_agent, and
FMPreService0203_agent processes on a slave node for providing the FMPreService0201,
FMPreService0202, and FMPreService0203 services separately.
Required service: FaultService.
7.1.21 fnlicense_agent Process

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

This section describes the services and functions provided by the glmssyn_agent process.
The glmssyn_agent process provides the GLMSSynService service.
The GLMSSynService periodically obtains the information about QChat cluster communication
changes from the Group and List Management Server (GLMS) and then applies the information
to CBSCs.
You can stop this process if the QChat cluster communication is not required.
7-10

Issue 03 (2010-12-31)
M2000
7.1.23 ifms_agent Process

This section describes the service and functions provided by the ifms_agent process.
The ifms_agent process provides the FaultService.
The FaultService collects alarm data from NEs and saves the data, thus providing the functions
of querying, dumping, and analyzing the fault data.
You can disable the service when fault management is not required.
7.1.24 ipm_agent Process

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

This section describes the functions provided by the irp_agent process.
EPIRP
The EPIRP is subject to the entry point object. The entry point object is the first object that the
NMS (Manager) accesses when the NMS interacts with the M2000 (Agent). The Agent provides
a reference of an entry point object to the Manager, and the Manager obtains the reference of
this entry point object in some way, for example, from the stored file. If the interface for
northbound network management is not required, disable the EPIRP.
Basic IRP: None.
NotificationIRP
NotificationIRP is used for subscribing to notifications and encapsulating notification
subscription. If the function of subscription through the interface of northbound network
management is not required, disable the NotificationIRP.
Basic IRP: EPIRP.
CSIRP
CSIRP provides an interface for link monitoring.
The link monitoring enables you to supervise the status of links between the Manager and the
Agent. In this way, the potential exceptions can be detected at the first time. If the function of
Issue 03 (2010-12-31)

7-11
M2000
monitoring through the interface of northbound network management is not required, disable
the CSIRP.
Basic IRP: EPIRP, and NotificationIRP.
KernelCMIRP
KernelCMIRP provides an interface for public configuration management.
The public configuration management uses KernelCMIRP to carry out some common tasks
during the configuration, such as sending configuration objects, or adding, removing and
modifying notifications. If the function of public configuration management through the
interface of northbound network management is not required, disable the kernelCMIRP.
Basic IRP: EPIRP, and NotificationIRP.
BasicCMIRP
BasicCMIRP controls the configuration management. BasicCMIRP is used for querying,
modifying, adding, or removing network resource objects. If the function of configuration
management through the interface of northband network management is not enabled, disable
the BasicCMIRP.
Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, and KernelCMIRP.
AlarmIRP
AlarmIRP is used for managing fault data. If the function of fault data management through the
interface of northbound network management is not required, disable the AlarmIRP.
Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, KernelCMIRP, and BasicCMIRP.
Required Services
The required service is the LicenseService.
7.1.26 itm_agent Process

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

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

Issue 03 (2010-12-31)
M2000
7.1.28 log_agent Process

This section describes the LogService service and dependent services. LogService is provided
by the log_agent process.
The log_agent process provides the LogService service.
The LogService service enables other services to save the system-related operation information
to files. It also enables the client to query log records of the operating system and to set and
query the parameters for dumping system logs.
7.1.29 maintain_agent Process

This topic describes the function of the MaintenanceService service, which is provided by the
maintain_agent process.
The maintain_agent process provides the MaintenanceService service.
The MaintenanceService service enables the periodic backup of the important system
configuration files, database data, and real-time data of MOs.
During the M2000 operation, ensure that the maintain_agent process is operational.
7.1.30 manager_agent Process

This section describes the services and functions provided by the manager_agent process.
The manager_agent process provides the SystemService service.
SystemService enables you to query the M2000 version information such as the version of the
operating system, software version of the client, software version of the server, client software
version matching the server software, and client upgrade information.
7.1.31 medXXXX_agent Process

This section describes the services and functions provided by the medXXXX_agent process.
The medXXXX_agent process provides the MediationServiceXXXX service.
The medXXXX_agent is a multi-instance process, and XXXX refers to the instance number.
When the M2000 is running, the system dynamically generates new processes and services based
on NE types and NE quantity. Some typical process names are med0101_agent, med0102_agent,
and med0103_agent, and the names of the corresponding services are MediationService0101,
MediationService0102, and MediationService0103.
The MediationServiceXXXX service creates, deletes, and obtains the NE engines mirrored to the
network devices from the M2000 system and also manages the related event interceptors. NEs
of different types communicate with the M2000 system by using the corresponding NE engines
through various network management protocols. In addition, the MediationServiceXXXX service
can export performance result files on the basis of NEs.
Issue 03 (2010-12-31)

7-13
M2000
Dependent services: none
7.1.32 necomm_agent Process

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

This 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 license
between the NEs of the same type.
Required services: LogService.
7.1.34 neuser_agent Process

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

This section describes the NGNFullFillService service and dependent services.
The ngnffs_agent process provides the NGNFullFillService.
The NGNFullFillService service provides functions of the management domain and the
subscriber number management.
7.1.36 ngnnis_agent Process

This section describes the NGNNIService service and dependent services.
7-14

Issue 03 (2010-12-31)
M2000
The ngnnis_agent process provides the NGNNIService.

The NGNNIService service provides functions of the north interface operation management.
7.1.37 ngnni112_agent Process

This 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.
7.1.38 ngntestmanage_agent Process

This section describes the services and functions provided by the ngntestmanage_agent process.
The ngntestmanage_agent process provides the NGNTestManageService service.
The NGNTestManageService provides the fix access network test management function.
7.1.39 nhcservice_agent Process

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

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

This section describes the NIMServer service and the dependent service. NIMServer is provided
by the nimserver_agent process.
The nimserver_agent process provides the NIMServer service.
Issue 03 (2010-12-31)

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

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

This section describes the services and functions provided by the partition_agent process.
The partition_agent process provides the PartitionService service.
The PartitionService service divides managed objects into various partitions. Each partition is
managed by its own process. In the presence of a large quantity of objects, the partitions are
managed by various processes on different servers to balance the load.
7.1.44 pm_agent Process

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

This section describes the services and functions provided by the process pmexp_agent.
The pmexp_agent process provides the PMExport service.
PMExport exports performance data of a measurement unit from the database. PMExport is
independent of NEs or managed objects.
Stop PMExport when the function of exporting performance results is not required.
7-16

Issue 03 (2010-12-31)
M2000
7.1.46 pmmon_agent Process

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

This section describes the services and functions provided by the pmncdXX01_agent process.
The pmncdXX01_agent process provides the PMNCDServiceXX01 service.
The pmncdXX01_agent is a multi-instance process and XX01 indicates the instance number.
Generally, the process name is pmncd0101_agent and the name of the corresponding service is
PMNCDService0101.
By default, the system saves the performance data of the neighboring cells of the RNC and BSC
in files. The database does not hold the data. To view the data of the neighboring cells, you need
to import the data from the files to the database and then query the results. The
PMNCDServiceXX01 service imports the performance data of the neighboring cells from the
files to the database.
Required services: PMService.
7.1.48 porttrunk_agent Process

This section describes the services and functions provided by the porttrunk_agent process.
The porttrunk_agent process provides the PortTrunkingService service.
By using the PortTrunkingService service, the M2000 server can communicate with the
M2000 client through a specified port. You need not configure multiple ports on the firewall for
communication.
7.1.49 proxy_agent Process

This section describes the services and functions provided by the proxy_agent process.
The proxy_agent process provides the Proxyserver service.
Proxyserver enables the M2000 client to connect to NEs through the proxy server and to run
applications of the NEs on the LMT .
Stop Proxyserver when the proxy function is not required.
Issue 03 (2010-12-31)

7-17
M2000
7.1.50 PRSAssistantService_agent Process

This section describes the services and functions provided by the PRSAssistantService_agent
process.
The PRSAssistantService_agent process provides the PRSAssistantService service.
The PRSAssistantService service provides the function of generating reports in .html, .csv or .xls
format. It also provides the function of transferring result files by email or through the FTP.
After restarting the PRSAssistantService service, you need to restart the PRSReportService
service.
If you need to run the PRS module, the PRSReportService service cannot be stopped.
7.1.51 prsdc_agent Process

This section describes the services and functions provided by the prsdc_agent process.
The prsdc_agent process provides the PRSDcService service.
The PRSDcService service provides the function of obtaining configuration data files and
performance data files on schedule.
Keep the service running during the operation of the PRS module.
7.1.52 prsfs_agent Process

This 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 for
importing report data.
The PRSFsService service provides the function of parsing configuration data files and
performance data files on schedule.
Keep the service running during the operation of the PRS module.
7.1.53 prsreport_agent Process

This section describes the services and functions provided by the prsreport_agent process.
The prsreport_agent process provides the PRSReportService service.
The PRSReportService service provides the function of querying the reports of the PRS module.
If you need to run the PRS module, the PRSReportService service cannot be stopped.
Required services: LicenseService and ItmService.
7.1.54 prssum_agent Process

This section describes the services and functions provided by the prssum_agent process.
7-18

Issue 03 (2010-12-31)
M2000
The prssum_agent process provides the PRSSumService service.

The PRSSumService service provides the function of summarizing the data of the PRS
(Performance Report Suite) module. It is responsible for retrieving data in a specified order and
scheduling the data.
If you need to run the PRS module, the PRSSumService service cannot be stopped.
Required services: CMServer.
7.1.55 rn_agent Process

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

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

This section describes the services and functions provided by the process scriptserver_agent.
The scriptserver_agent process provides the ScriptService service.
ScriptService provide script timing and NEs access from script.
Required services: ItmService and SecurityService.
7.1.58 sm_agent Process

This section describes the services and functions provided by the process sm_agent.
The sm_agent process provides the SecurityService service.
SecurityService controls the access of all sensitive resources in the M2000. Only authorized
users can gain access to sensitive resources.
Required services: EAMService and LicenseService
Issue 03 (2010-12-31)

7-19
M2000
7.1.59 snmp_agent Process

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

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

This section describes the services and functions provided by the sso_agent process.
The sso_agent process provides SSO service.
SSO service provides the function of centralized account management and authorization.
7.1.62 swm_agent Process

This section describes the services and functions provided by the swm_agent process.
The swm_agent process provides the SWMService service.
The SWMService manages the versions, configuration data, NE logs, and other files of some
NEs. It also provides the download, upload, activation, and rollback functions.
7.1.63 threshold_agent Process

This topic describes the function of the ThresholdService service provided by the
threshold_agent process and the service that the threshold_agent process depends on.
7-20

Issue 03 (2010-12-31)
M2000
The threshold_agent process provides the ThresholdService service.

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

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

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

This section describes the services and functions provided by the umgupdsvr_agent process.
The umgupdsvr_agent process provides the UMGUpgradeService service.
UMGUpgradeService provides the UMG upgrade function.
7.1.67 xftpXX01_agent Process

This section describes the services and functions provided by the xftpXX01_agent process.
The xftpXX01_agent process provides the XFTPServiceXX01 service. Through the
XFTPServiceXX01 service, the M2000 actively uploads exported files through the northbound
interface to the FTP server on the NMS side.
The XFTPServiceXX01 service actively checks the alarms, configurations, performance files
generated by the PMExport service or the pmexp_agent process. Based on the settings of the
Issue 03 (2010-12-31)

7-21
M2000
FTP server on the NMS side, the XFTPService service uploads the northbound alarm files,
configuration files, performance files to the specified FTP server.
The files that can be exported by the XFTPServiceXX01 are as follows:
l
Northbound alarm file
Northbound configuration file
Northbound inventory file
Northbound performance file
CME northbound configuration file
NodeB license file
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.
7.1.68 Processes and Services Related to Each Northbound Interface

This section describes the processes and services related to each northbound interface.
Table 7-1 describes the relationships between northbound interfaces and their corresponding
processes and services.
Table 7-1 Relationships between northbound interfaces and their corresponding processes and
services
Process
Service
Northbound Interface
irp_agent
IRPService
l CORBA configuration
interface
l CORBA alarm interface
l CORBA security interface
l Configuration database
l Performance database
7-22
ifms_agent
FaultService
Northbound alarm file

interface
pmexp_agent
PMExport

interface (measurement unitbased)
medXXXX_agent
MediationServiceXXXX

interface (NE-based)
snmp_agent
SnmpAgent
Northbound SNMP interface
fmnotify_agent
FMNotify
Northbound alarm streaming

interface
nms_mml_agent
NMSMMLServer
Northbound MML interface

Issue 03 (2010-12-31)
M2000
Process
Service
Northbound Interface
cmserver_agent
CMServer
Northbound inventory file

interface
cmexp_agent
CMExport
Northbound configuration file

interface

rectify the faults.
Prerequisite
l
Context
Checking the states of the M2000 processes on the M2000 client requires only a few system
resources and does not affect system performance.
Procedure
Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on the
M2000 server. See Figure 7-1.
Figure 7-1 Process Monitor tab page
Issue 03 (2010-12-31)

7-23
M2000

----End
7.2 Managing the M2000 Services (SUSE)

This describes how to view, start, and stop M2000 services.
7.2.2 Viewing the Running Status of M2000 Services (SUSE)
This describes how to view the status of M2000 services on the M2000 server. This operation
requires only few system resources and does not affect system performance.
7.2.3 Starting the M2000 Server (SUSE)
After you run the start_svc command, all the M2000 services are started. If an M2000 service
is already started, the system does not handle the service. Actually, the system starts only the
inactive services.
7.2.4 Stopping the M2000 Services (SUSE)
This describes how to stop the M2000 services. After the M2000 services are stopped, the
M2000 processes are stopped. In this situation, NE performance data and alarm data cannot be
processed. After the services are resumed, the M2000 updates the data with the NEs and
processes the data.

Prerequisite
l
Context
Checking the M2000 services on the M2000 client requires only a few system resources and
does not affect system performance.
Procedure
Step 2 Click the Service Monitor tab to check the M2000 services. See Figure 7-2.
7-24

Issue 03 (2010-12-31)
M2000
Figure 7-2 Service Monitor tab page
NOTE
In the Status column, the green icon indicates that the corresponding process is normal; the red icon
indicates the corresponding process is abnormal.

----End
7.2.2 Viewing the Running Status of M2000 Services (SUSE)

This describes how to view the status of M2000 services on the M2000 server. This operation
requires only few system resources and does not affect system performance.
Prerequisite
You have Logged in to the M2000 server as user omcuser.
Procedure
Step 1 Switch to the M2000 installation path. The default M2000 installation path is /opt/OMC.
~> cd /opt/OMC
Step 2 Run the following commands:
~> . ./svc_profile.sh
~> svc_adm -cmd status
Host: DEFAULTSYSAGENT
SystemConfigurator: running
Service Agent: cmserver_agent [1 service(s)] pid: 3160
CMServer
[running
]
Issue 03 (2010-12-31)

7-25
M2000
Service Agent: devdoc_agent [1 service(s)] pid: 3138

DevDocService
[running
]
Service Agent: em_agent [1 service(s)] pid: 3126
EventService
[running
Service Agent: fmnotify_agent [1 service(s)] pid: 3146

FMNotify
[running
]
Service Agent: ifms_agent [1 service(s)] pid: 3162
FaultService
[running
Service Agent: irp_agent [1 service(s)] pid: 3150

IRPService
[running
Service Agent: log_agent [1 service(s)] pid: 3125

LogService
[running
Service Agent: manager_agent [2 service(s)] pid: 3134

DataMgrService
[running
]
SystemService
[running
]
Service Agent: med1_agent [1 service(s)] pid: 3140
MediationService1
[running
Service Agent: med4_agent [1 service(s)] pid: 3172

MediationService4
[running
Service Agent: med_agent [1 service(s)] pid: 3132

MediationService
[running
Service Agent: mo_agent [4 service(s)] pid: 3136

LockService
[running
MOProxyService
[running
MOService
[running
RelationService
[running
]
]
]
]
Service Agent: monitor_agent [1 service(s)] pid: 3128

MonitorService
[running
]
Service Agent: neuser_agent [1 service(s)] pid: 3164
NeUserService
[running
]
Service Agent: notify_agent [1 service(s)] pid: 3142
RemoteNotifyService
[running
]
Service Agent: partition_agent [1 service(s)] pid: 3154
PartitionService
[running
]
Service Agent: pm_agent [1 service(s)] pid: 3144
PMService
[running
]
Service Agent: pmexp_agent [1 service(s)] pid: 3166
PMExport
[running
]
Service Agent: pmmon_agent [1 service(s)] pid: 3148
PMMonService
[running
]
Service Agent: porttrunk_agent [1 service(s)] pid: 3158
PortTrunkingService
[running
]
Service Agent: proxy_agent [1 service(s)] pid: 3170
ProxyServer
[running
]
7-26
Service Agent: sac_agent [2 service(s)] pid: 3130

LicenseService
[running
ScheduleService
[running
]
]
Service Agent: sm_agent [1 service(s)] pid: 3156

SecurityService
[running

Issue 03 (2010-12-31)
M2000
Service Agent: swm_agent [1 service(s)] pid: 3152

SWMService
[running
Service Agent: tm_agent [1 service(s)] pid: 3168

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

NOTE
The M2000 system generates processes and services dynamically during the operation. Accordingly, the
number of processes and services changes dynamically.
----End
7.2.3 Starting the M2000 Server (SUSE)

After you run the start_svc command, all the M2000 services are started. If an M2000 service
is already started, the system does not handle the service. Actually, the system starts only the
inactive services.
Prerequisite
You have logged in to the server as user omcuser.
Procedure
Step 1 Change to the installation directory of the M2000 server.
~> cd /opt/OMC
NOTE
/opt/OMC is the default M2000 installation directory.
Step 2 Run the following commands:

NOTE
l Before starting the M2000 server, ensure that the Oracle is started.
l The time required for starting the M2000 services is related to the actual environment. Generally, it
takes about 20 minutes to start the M2000 services.
~> start_svc
----End
7.2.4 Stopping the M2000 Services (SUSE)

This describes how to stop the M2000 services. After the M2000 services are stopped, the
M2000 processes are stopped. In this situation, NE performance data and alarm data cannot be
processed. After the services are resumed, the M2000 updates the data with the NEs and
processes the data.
Prerequisite
You have logged in to the server as user omcuser.
Issue 03 (2010-12-31)

7-27
M2000
Procedure
Step 1 Change to the installation directory of the M2000 server.
~> cd /opt/OMC
NOTE
/opt/OMC is the default M2000 installation directory.
Step 2 Run the following commands to stop the M2000 services:

~> stop_svc
NOTE
The time required for stopping the M2000 services is related to the actual environment. Generally, it takes
about 20 minutes to stop the M2000 services.
Step 3 Run the following command to check whether there is any output. If no system output is
displayed, you can infer that M2000 services are stopped.
~> svc_ps
Step 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 is
displayed, 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
Step 8 Run the ps -ef |grep 9999 |grep -v grep command and check whether any output is displayed.
If some output is displayed, run the stop_tao_services to stop the TAO process.
----End
7-28

Issue 03 (2010-12-31)
M2000
Managing the M2000 Database (Oracle)
About This Chapter

This chapter describes how to manage the M2000 database. This chapter also describes the
concepts of the M2000 database and procedures on how to view the database status, clear, and
back up the database.
8.1 Introduction to the M2000 Database (Oracle)
The M2000 databases consist of the Oracle database and the M2000 server database. This chapter
describes only the M2000 server database. On the basis of the Oracle database, the M2000 creates
the OSSDB database. After the installation of the M2000 server application software, the size
of the M2000 database is fixed. You must operate the database by using Oracle commands.
8.2 Viewing the Status of the M2000 Database (Oracle)
This describes how to view the status of the M2000 database. You can run Oracle commands
on the server to view the status of M2000 databases. Alternatively, you can view the database
states using the system monitor browser.
8.3 Clearing M2000 Databases
This section describes how to dump the data in the M2000 databases. The data includes the
performance data, NE operation logs, NE system logs, NE security logs, alarm/event logs, NM
operation logs, NM system logs, and NM security logs. You can configure an integrated task
for dumping the data in the M2000 databases.
8.4 Backing Up the M2000 Databases (Oracle)
This describes how to back up the M2000 databases. The M2000 databases are categorized into
omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb, pmcomdb, and sumdb.
Issue 03 (2010-12-31)

8-1
M2000
8.1 Introduction to the M2000 Database (Oracle)

The M2000 databases consist of the Oracle database and the M2000 server database. This chapter
describes only the M2000 server database. On the basis of the Oracle database, the M2000 creates
the OSSDB database. After the installation of the M2000 server application software, the size
of the M2000 database is fixed. You must operate the database by using Oracle commands.
8.1.1 cmedb
The cmedb is used to store the NE configuration data on the M2000, including the configuration
data in the current and planned data areas. The cmedb database must exist in the M2000 system.
The cmedb requires at least 10 GB data space.
Table 8-1 lists the names and functions of the tables in the cmedb.
Table 8-1 Names and functions of tables in the cmedb database
Table Name
Function
Utils_TableDef
Records the basic information about the M2000.
Utils_FieldDef
Records the attribute information about the M2000.
Utils_FieldDefIncludeOpaque
Records the attribute information about the opaque.
Utils_ErrMsg
Records the correspondence between the error code and error

description.
8.1.2 omcdb
The omcdb is used to store the configuration data, security data, and internal data of the
M2000. The omcdb database must exist in the M2000 system.
The omcdb requires a disk space of more than 1,000 MB.
Table 8-2 describes the name and function of each table in the omcdb.
Table 8-2 Names and functions of tables in the omcdb database
8-2
Table Name
Function
Tables with moi_ as the

prefix
Records the information about MO examples.
Tables with mos_ver_ as

the prefix
Records the information about versions.
Tables with nbmmlNe_

as the prefix
Records the information about the format of messages transferred

between the M2000 and the NEs.

Issue 03 (2010-12-31)
M2000
Issue 03 (2010-12-31)
Table Name
Function
Tables with sm_ as the

prefix
Records the information about service data.
Tables with softx3000_

as the prefix
Records dual-homing relationship.
Views with
gv_view_cmcyw_ as the
prefix
Records service Database Central (DC) data.
Views with
view_cmcyw_ as the
prefix
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 the

prefix
Records the processes of service AMG data.
tbl_Resource
Records NE resource data.
Tables with ums_ as the

prefix
Record the information about error codes.
Tables with ne_ as the

prefix
Records the information about NE models.
Tables with omc_ as the

prefix
Records the data about network management.
Tables with rel_ as the

prefix
Records the associations between MOs.
tbl_ADAllNeList
Records the information about the NodeBs to be commissioned.
tbl_ADNeStatus
Records the information about the statuses of the NodeBs to be

commissioned.
tbl_AllNeInfo
Records the network management data that are created for

compatibility with previous versions.
tbl_IPExg
Records the IP configuration information about the NAT

translation table.
tbl_OmcSslOption
Records the SSL connection policy of the OMC for NEs.
tbl_nelicBaseInfo
Records the basic information about NEs.
tbl_nelicTask
Records the information about operation tasks.
tbl_nelicTaskEnv
Records the information flow interacted between the M2000

server and client.
tbl_test_task_property
Records the properties of the IPQoS test task.

8-3
M2000
Table Name
Function
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 bearer
network.
tbl_test_nblink_result
Records the audit result of the call completion rate on the bearer
network.
tbl_test_ping_address
Records information about address pairs sent by the host.
tbl_SubareaInfo
Partition information table, recording the information about each

node.
tbl_SubareaRes
Partition resource table, recording the resources of each node.
session_SessionEntity
Records information about operated NEs during a session.
session_SessionMoc
Records information about operated MOCs during a session.
session_SessionOpInfo
Records information about user operations during a session.
Other tables
Records other configuration data of the M2000.
8.1.3 omclogdb
The omclogdb is used to store log management data. The omclogdb database must exist in the
M2000 system.
The omclogdb requires more than 500 MB disk space.
Table 8-3 lists the names and functions of the tables in the omclogdb.
Table 8-3 Names and functions of tables in the omclogdb database
8-4
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.

Issue 03 (2010-12-31)
M2000
8.1.4 omcsmdb
The omcsmdb is used to store security management data. The omcsmdb database must exist in
the M2000 system.
Table 8-4 lists the names and functions of the tables in the omcsmdb.
Table 8-4 Names and functions of tables in the omcsmdb database
Issue 03 (2010-12-31)
Table Name
Function
tbl_AccessTable
Records the binding relations between user

groups and privileges.
tbl_AccessViewNodeRelTable
Records the relations between the privilege

display nodes.
tbl_AccessViewNodeTable
Records the privilege display nodes.
tbl_IDTable
Records the reclaimed IDs.
tbl_SMAccessPolicyItem
Records the privilege statistics for binding user

groups.
tbl_SMGroup
Records the basic information about user groups.
tbl_SMGroupUserMap
Records the binding relations between user

groups and users.
tbl_SMLoginRec
Stores the history records on user login.
tbl_SMNEUser
Records the basic information about NE users.
tbl_SMPrivateGroupUserMap
Records the binding relations between private

groups and users.
tbl_SMSecurityPolicy
Records the security policy.
tbl_SMTerm
Records the basic information about terminals.
tbl_SMUser
Records the basic information about users.
tbl_SMUserHistoryRec
Records history user passwords.
tbl_SMUserNEUserMap
Records the binding relations between users and

NE users.
tbl_SMUserTerminalMap
Records the binding relations between users and

terminals.
tbl_SecurityObjectTable
Records security objects.
tbl_SessionIDTable
Records session IDs.
tbl_StaticTypeRelationTable
Records the relations between privileges.
tbl_StaticTypeTable
Records the static security information about

object types, privileges, and operations.

8-5
M2000
Table Name
Function
tbl_StaticTypeViewTable
Records the static security information.
8.1.5 omctmdb
The cmetmdb is used to store topology management data. The omctmdb database must exist in
the M2000 system.
The omctmdb requires a disk space of more than 550 MB.
Table 8-5 lists the names and functions of the tables in the omctmdb.
Table 8-5 Names and functions of tables in the omctmdb database
Table Name
Function
MOTSConfig
Records the topology configuration values, including the initial

value and the maximum value assigned by ObjID.
MOTSDomain
Records the information on topology domains.
MOTSLink
Records the information on topology links.
MOTSNode
Records the information on topology NEs.
MOTSSubnet
Records the information on topology subnets.
MOTSSubtree
Records the information on the topology tree.
MOTSVSubnet
Records the information on topology logical subnets.
MOTSView
Records the information on topology views.
MOTSViewObj
Records the information on topology view objects.
TSTempLoc
Records the temporary table that stores the longitude and latitude
coordinates of the e-map.
TSTempPos
Records the temporary table that stores the x-axis and y-axis
coordinates of common physical topology.
8.1.6 fmdb
The fmdb is used to store the alarm data of the M2000 and the managed NEs. The fmdb database
must exist in the M2000 system.
The fmdb stores the NE data and the M2000 alarm data. A disk space of more than 3,700 MB
is required for the storage.
Table 8-6 lists the names and functions of tables in the fmdb.
8-6

Issue 03 (2010-12-31)
M2000
Table 8-6 Tables of the fmdb database and the corresponding functions
Table Name
Function
tbl_alm_log
Records alarm logs.
tbl_event_log
Records event logs.
Other tables
Record the internal processing data of alarms.
NOTE
The system automatically divides the tbl_alm_log and tbl_event_log tables according to the size of alarms
and events. For example, the fmdb database may contain multiple alarm log tables such as tbl_alm_log_1
and tbl_alm_log_2.
8.1.7 pmdb
The pmdb is used to store the NE performance measurement data. The pmdb database must exist
in the M2000 system.
If the remaining space of the pmdb database is insufficient, the system generates an alarm.
After the storage period of the performance measurement data expires, the most recent data
overwrites the earliest data on a daily basis.
If the data is saved for less than the preset days old but the pmdb is fully occupied, you must
change the number of days till the data can be stored. Otherwise, the pmdb cannot process any
performance data. Change the number of saving days before the remaining space of the pmdb
is insufficient.
To calculate the number of days till when the data can be stored, perform the following steps:
Observe the usage of the pmdb when the M2000 runs for half a month. Calculate the space of
the pmdb used in a day. Calculate the number of days that the pmdb lasts.
The pmdb consists of the following types of tables:
l
Template Tables
Function Subsets and Period Tables
Template Tables
Template tables record measurement information. Table 8-7 lists the name and function of the
table.
Table 8-7 Template tables in the pmdb and their functions
Issue 03 (2010-12-31)
Table Name
Function
tbl_SyncInfo
Records the supplementary collection queues of

performance results.

8-7
M2000

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

the ID of the function subset and Y is the period index
between 0 and 4.
8.1.8 swmdb
The swmdb is used to store the file information about the software management module and the
configuration data of NE versions. The swmdb database must exist in the M2000 system.
The swmdb stores the files managed by the software management module and the NE version
configuration data. A disk of more than 3,000 MB is required for storage. Table 8-9 lists the
name and function of each table.
Table 8-9 lists the names and functions of tables in the swmdb.
Table 8-9 Names and functions of tables in the swmdb database
Table Name
Function
tbl_FTPFileSet
Records the files managed by the software management

module.
tbl_VersionRelation
Records the information about version relations.
tbl_NELogTable
Records the NE operation logs.
8.1.9 pmcomdb
The pmcomdb is used for storing the static performance measurement data of NEs. The
pmcomdb database must exist in the M2000 system.
The space of the pmcomdb must be greater than 400 MB.
If the remaining space of the pmcomdb is insufficient, the system generates an alarm.
The pmcomdb consists of the following types of tables:
8-8
Counter tables
Template Tables

Issue 03 (2010-12-31)
M2000
Counter tables
Compared with the data in other types of tables, the data in these tables is stable. Table 8-10
lists the name and function of each table.
Table 8-10 Counter information tables in the pmcomdb and the corresponding functions
Table Name
Function
systbl_NeType
Records all possible NE types in M2000.
systbl_FunctionSet
Records the function sets of all NEs.
systbl_FunctionSubSet
Records the measurement units of all

function sets.
systbl_Counters
Records all measurement counters.
systbl_Counter_Unit
Records the units of all counters.
systbl_AllCounterCategory
Records the service features of each

version.
systbl_ComputeCounters
Records only the counters involved in

calculation.
Template Tables
Template tables contain several tables that record measurement information. Table 8-11 lists
the name and function of each table.
Table 8-11 Template information tables in the pmcomdb and the corresponding functions
Issue 03 (2010-12-31)
Table Name
Function
tbl_ObjectInstance
Records measurement objects.
tbl_MeasurementPeriod
Records measurement periods.
tbl_MeasurementCounter
Records measurement counters.
tbl_MeasurementSuspendInfo
Records the information on suspended

tasks.
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 service

features on the M2000 operating
environment.

8-9
M2000

The measurement results are saved according to the function subset and period. Table 8-12 lists
the name and function of each subset and table.
Table 8-12 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 function

subset ID and Y refers to the period index that
ranges from 0 to 4. By comparing the
tbl_MeasObject_XXX_Y with the result
table named tbl_Result_XXX_Y, you can
check the loss status and integrity of the
results.
Each time when the measured object changes,
a message is recorded in the list.
8.1.10 sumdb
The sumdb stores the summarized performance data of NEs for performance reports to use. If
the M2000 system is not configured with the PRS, the sumdb is not available.
The size of the sumdb is equal to one thirds the size of the pmdb, that is, more than 4,500 MB.
The sumdb consists of the following types of tables:
l
Object type information table
System setting information table
Report information table
Performance result table
Object Type Information Table

The object type information table consists of 12 tables, which save a group of relatively stable
information. Table 8-13 lists the name and function of each table.
Table 8-13 Name and function of each object type information table in the sumdb
8-10
Table Name
Function
t_NeType
Records the NE type and manages the

relevant information.
t_PRSObjectType
Records the information about object types

of each class.
t_GroupObjType

of object groups.

Issue 03 (2010-12-31)
M2000
Table Name
Function
t_AttrObjType

of attribute classes.
t_ConfigObjType

of configuration classes.
t_ConfigObjTypeAttr
Records the attribute information about the

configuration object type.
t_CombObjType

of combination classes.
t_PmObjType
Records the relation between the PRS object

type and the performance object type.
t_CombTable
Records the rule information about the

combination table.
t_FSS
Records the information about the extracted

function subsets.
t_Item
Records counter information.
t_ObjTypeAggrRelation
Records the summarization relation between

objects.
System Setting Information Table

The system setting information consists of 15 tables that record information related to system
setting. Table 8-14 lists the name and function of each table.
Table 8-14 Name and function of each system setting information table in the sumdb
Issue 03 (2010-12-31)
Table Name
Function
t_Week
Records the start date of a week.
t_SpecialDate
Records the definition information about

special dates.
t_BusyRule
Records the information about busy-hour

planning.
t_BusyTime
Records the information about busy hours.
t_BusyTimeArith
Records the information about the statistics

on monthly busy hours.
t_DefaultPeriod
Records the information about default

periods.
t_RawPeriod
Records the information about the extraction

period of original results.
8-11
M2000
Table Name
Function
t_DefaultStorage
Records the default storage duration of

results.
t_CustomStorag
Records the storage duration of results.
t_LoadFlag
Records the information about the

summarization and extraction.
t_MaxItemId
Records the IDs of maximum available

counters of NEs.
t_RawHistoryInf
Records the history of extracting original

result tables.
t_RawResultNo
Records the result numbers of original result

tables.
t_SumHistoryInfo
Records the history of extracting

summarization result tables.
t_BusyHistoryInfo
Records the information about busy-hour

summarization result tables.
Report Information Table

The report information table consists of eight tables that record the information about the queried
tables. Table 8-15 lists the name and function of each table.
Table 8-15 Name and function of each report information table in the sumdb
8-12
Table Name
Function
t_Report
Records the information about reports.
t_Sheet
Records the information about the sheets.
t_SheetItem
Records the counters of sheets.
t_SheetFilter
Records filtering information.
t_ItemFormat
Records the counter format information.
t_RelateReport
Records the relation between reports.
t_TemplateInfo
Records the basic information about the

templates.
t_TemplateObjInfo
Records the basic information about the

templates and the objects.

Issue 03 (2010-12-31)
M2000
Performance Result Table

The performance result table consists of multiple tables, which records the performance
measurement results based on the function subset and the measurement period. Table 8-16 lists
the name and function of each table.
fssName, ObjLevel, ConfigObjectTy, and GroupObjectTy indicate the name of a function
subset, the object dimension, the type ID of an object to be configured, and the type ID of an
object group. These parameters can be configured in the configuration file.
Table 8-16 Name and function of each performance result table in the sumdb
Table Name
Function
f_fssName_Raw
Indicates original result serial tables which

record the original results.
If the function subset is not extracted
internally, the administration tool (AT)
automatically names the function subset in
the following format: F _ ID of the function
subset.
Issue 03 (2010-12-31)
f_fssName_ObjLevel_H
Indicates hourly serial tables which records

the result information at hour dimension.
The hourly summarization is based on the
original results.
f_fssName_ObjLevel_D
Indicates daily serial tables which record the

result information at day dimension. The
hourly summarization is based on hourly
summarization.
f_fssName_ObjLevel_W
Indicates daily serial tables which record the

result information at week dimension. The
weekly summarization is based on daily
summarization.
f_fssName_ObjLevel_M
Indicates monthly serial tables which record

the result information at month dimension.
The monthly summarization is based on
weekly summarization.
f_fssName_ObjLevel_WH
Indicates the weekly busy-hour serial tables

which record the weekly busy-hour results.
f_fssName_ObjLevel_MH
Indicates the monthly busy-hour serial tables

which record the monthly busy-hour results.
d_ConfigObjectTy
Records the information about the objects to

be configured.
d_GroupObjectT
Records the information about the type of

object groups.
d_ConfigObjectTyObject
Records the information about object

instances of object groups.

8-13
M2000
8.1.11 itfndb
The itfndb is used to store the northbound configuration data, performance tasks, and
performance threshold data. The itfndb database must exist in the M2000 system.
The itfndb is optional. It requires a disk space of at least 200 MB. Table 8-17 lists the name and
function of each table.
Table 8-17 Names and functions of tables in the itfndb database
Table Name
Function
tbl_JGeneralInfo
Records the general information about tasks.
tbl_JMoInstance
Records the instances of tasks.
tbl_JStatusRecord
Records the Status of tasks.
tbl_JMeasurementCategory
Records the measurement categories of tasks.
tbl_JSchedule
Records the task scheduling.
tbl_RegM2KObject
Records the registered M2000 objects.
tbl_MGeneralInfo
Records the general information about thresholds.
tbl_MMoInstance
Records the instances of thresholds.
tbl_MMeasurementCategory
Records the measurement categories of thresholds.
tbl_MThresholdPackElemen
Records the details of thresholds.
tbl_MAlarmRecord
Records the alarm records of thresholds.
tbl_MStatusRecord
Records the status of thresholds.
Other tables
Records the information about northbound

implementation.
8.1.12 farsdb
The farsdb is used to store the signaling data of all the NEs managed by the M2000. If the
M2000 system is not configured with the tracing function, the farsdb is not available.
The farsdb requires at least 10 GB data space and 3 GB log space.
The farsdb consists of the following types of tables:
l
Static configuration data table
Task table
Task data table
Table 8-18 describes the name and function of each table in the farsdb.
8-14

Issue 03 (2010-12-31)
M2000
Table 8-18 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_task

ID
Task data table created dynamically, which records the signaling

data of the message type corresponding to a task
8.1.13 omctempdb
The omctempdb is used to store the buffer data required for internal implementation of the
DesktopServiceXXXX service. The omctempdb database must exist in the M2000 system.
The omctempdb requires more than 500 MB disk space.
Table 8-19 lists the name and function of each table in the omctempdb.
Table 8-19 Names and functions of tables in the omctempdb database
Table Name
Function
tbl_instance
name_subsystem
name_function name
Stores the buffer data required for internal implementation of the

DesktopServiceXXXX service.
8.1.14 omceamdb
The omceamdb is used to store the data of network management objects, such as NEs, subnets,
and links. The omceamdb database must exist in the M2000 system.
The omceamdb requires more than 500 MB disk space.
Table 8-20 lists the name and function of each table in the omceamdb.
Table 8-20 Names and functions of tables in the omceamdb database
Issue 03 (2010-12-31)
Table Name
Function
tbl_sn
Subnet information table
tbl_ne
NE information table
tbl_nefeature
NE feature table
tbl_link
Link information table

8-15
M2000
Table Name
Function
tbl_idresource
NMS object identification management table
tbl_sntype
Subnet type table
tbl_netype
NE type table
tbl_linktype
Link type table
tbl_sync
Data synchronization table
tbl_nerelation
NE relation table
tbl_maintenanceinfo
Maintenance personnel information table
tbl_locationinfo
Device maintenance information table
tbl_negroup
NE group information table
tbl_negroupclass
NE group mode table
tbl_negroup2ne
NE group and NE relation table
tbl_negrouptype
NE group type table
tbl_devsnmppara
SNMP device parameter table
tbl_dftsnmppara
Default SNMP parameter table
tbl_autodiscfilter
Auto-search IP filter table
tbl_autodischistory
Auto-search history record table
tbl_eamschedule
Scheduled-search parameter table
tbl_autodiscresult
Auto-search result table
8.2 Viewing the Status of the M2000 Database (Oracle)

This describes how to view the status of the M2000 database. You can run Oracle commands
on the server to view the status of M2000 databases. Alternatively, you can view the database
states using the system monitor browser.
8.2.1 Viewing the Database Usage of the M2000 Server on the Client (SUSE)
of the database.
8.2.2 Viewing the Database Usage of the M2000 Server Using Oracle Commands
This describes how to use Oracle commands to view the database status, overall size of data
files, and size of remaining space. This operation requires few system resources and does not
affect system operation.
8-16

Issue 03 (2010-12-31)
M2000
8.2.1 Viewing the Database Usage of the M2000 Server on the Client
(SUSE)
of the database.
Prerequisite
l
Context
This operation requires few system resources and does not affect system operation.
Procedure
Step 2 Click the Database Monitor tab. The information about the database of the M2000 server is
displayed, as shown in Figure 8-1.
Figure 8-1 Database monitoring
NOTE
In the Status column, the green icon indicates normal and the red icon indicates abnormal. If the database
usage exceeds the preset threshold, the green icon in the relevant column becomes red.
Step 3 (Optional) Click Save to save the monitoring data to a file.

----End
Issue 03 (2010-12-31)

8-17
M2000
8.2.2 Viewing the Database Usage of the M2000 Server Using Oracle
Commands
This describes how to use Oracle commands to view the database status, overall size of data
files, and size of remaining space. This operation requires few system resources and does not
affect system operation.
Prerequisite
You have logged in to the server as user oracle.
Procedure
Step 1 Run the following command to view the overall size of database files:
~>sqlplus / as SYSDBA
SQL> select tablespace_name, sum(bytes)/1024/1024 Total_Size_M from dba_data_files
group by tablespace_name;
TABLESPACE_NAME
TOTAL_SIZE_M
------------------------------ -----------PMCOMDB_TBS
1499
CMEDB_TBS
8191
UNDOTBS1
4095
SYSAUX
1599
FARSDB_TBS
12287
OMCEAMDB_TBS
599
SWMDB_TBS
3071
OMCDB_TBS
3071
SYSTEM
1199
PMDB_TBS
46078
ITFNDB_TBS
3071
FMDB_TBS
3071
OMCLOGDB_TBS
1023
OMCSMDB_TBS
1023
OMCTMDB_TBS
1023
OMCTEMPDB_TBS
1799
Step 2 Run the following command to view the size of the remaining space:
SQL> select TABLESPACE_NAME, sum(bytes)/1024/1024 as free_size_M from
dba_free_space group by tablespace_name ;
The unit in the command output is MB.
TABLESPACE_NAME
FREE_SIZE_M
------------------------------ ----------PMCOMDB_TBS
1468.25
CMEDB_TBS
8190.9375
UNDOTBS1
3683.875
SYSAUX
1501.8125
FARSDB_TBS
12286.5625
OMCEAMDB_TBS
592.8125
SWMDB_TBS
3066.0625
OMCDB_TBS
2667.0625
SYSTEM
934.25
PMDB_TBS
46075.5625
ITFNDB_TBS
3068.5625
FMDB_TBS
3059.3125
OMCLOGDB_TBS
1019.5625
OMCSMDB_TBS
1014.3125
OMCTMDB_TBS
1020.75
OMCTEMPDB_TBS
1798.4375
8-18

Issue 03 (2010-12-31)
M2000
16 rows selected.
----End
8.3 Clearing M2000 Databases

This section describes how to dump the data in the M2000 databases. The data includes the
performance data, NE operation logs, NE system logs, NE security logs, alarm/event logs, NM
operation logs, NM system logs, and NM security logs. You can configure an integrated task
for dumping the data in the M2000 databases.
Prerequisite
l
You have logged in to the M2000.
You are authorized to clear the M2000 databases.
Dump conditions can be set according to the following aspects: execution type, execution
time, and file saving format.
After the data is dumped, the following data is saved in the default directory of the
M2000 server and removed from the databases:
Context
The performance data in the pmdb database

The NE operation logs, NE system logs, and the NE security logs in the swmdb database
The alarm and event logs in the fmdb database
The operation logs, system logs, and security logs in the omclogdb database
Procedure
Step 1 Dump the performance data in the pmdb database.
1.
On the GUI of the M2000 client, choose Maintenance > Task Management.
The Task Management window is displayed.
2.
In the left part of the Task Management window, select Performance Data under the
Database Capacity Management node from the Task Type navigation tree.
3.
Select a task in the right part of the Task Management window, and then click
Attribute.
4.
In the Attribute dialog box, set the dump parameters. Then, click OK.
Step 2 Dump the NE operation logs in the swmdb database.

1.
2.
In the left part of the Task Management window, select NE Operation Log under the
node Database Capacity Management from the Task Type navigation tree.
3.
Attribute.
4.
Issue 03 (2010-12-31)

8-19
M2000
Step 3 Dump the NE security logs in the swmdb database.

1.
2.
In the left part of the Task Management window, select NE Security Log under the node
Database Capacity Management from the Task Type navigation tree.
3.
Attribute.
4.
Step 4 Dump the NE system logs in the swmdb database.

1.
2.
In the left part of the Task Management window, select NE System Log under the node
Database Capacity Management from the Task Type navigation tree.
3.
Attribute.
4.
Step 5 Dump the alarm and event logs in the fmdb database.
1.
2.
In the left part of the Task Management window, select Alarm/Event Log Dump under
the node Database Capacity Management from the navigation tree Task Type.
3.
Attribute.
4.
Step 6 Dump the NM operation logs in the omclogdb database.

1.
2.
In the left part of the Task Management window, select NM Operation Log Dump under
the Database Capacity Management node from the Task Type navigation tree.
3.
Attribute.
4.
Step 7 Dump the NM system logs in the omclogdb database.

1.
8-20
2.
In the left part of the Task Management window, select NM System Log Dump under
3.
Attribute.
4.
Issue 03 (2010-12-31)
M2000
Step 8 Dump the NM security logs in the omclogdb database.

1.
2.
In the left part of the Task Management window, select NM Security Log Dump under
3.
Attribute.
4.
----End
8.4 Backing Up the M2000 Databases (Oracle)

This describes how to back up the M2000 databases. The M2000 databases are categorized into
omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb, pmcomdb, and sumdb.
Prerequisite
l
You are authorized to back up the M2000 system.
Context
NOTE
Do not suspend a periodic backup task. Because the latest data fails to be restored after data lost caused by
an accident, for example, the power-off of the server.
Procedure
Step 1 On the main window, choose Maintenance > Task Management.
Step 2 Choose Task Type > Backup > Server Backup in the navigation tree and double-click the
node. The Attribute dialog box of server periodic backup is displayed, as shown in Figure
8-2.
Issue 03 (2010-12-31)

8-21
M2000
Figure 8-2 Periodic backup
Step 3 Click Common Parameters, and set Task Name and Start Time.
NOTE
You do not need to set Extended Parameters.
Step 4 Click OK.

The system performs periodic backup automatically.
Step 5 If data is backed up on a tape and the tape is fully written during the backup, perform Step 6
through Step 7 to replace the tape with a new tape.
Step 6 The system automatically ejects the fully written tape and waits you to replace the tape.
As shown in Figure 8-3, the Information field in the System Backup dialog box displays the
following message:
The current tape is fully written. Please replace it with
another tape as soon as possible.
8-22

Issue 03 (2010-12-31)
M2000
Figure 8-3 Manual backup
Step 7 Insert a new tape into the tape drive.

The Information field in the System Backup dialog box displays the following message:
The tape has been placed in the tape drive. Please resume the
backup operation.
After you insert a new tape, the system continues to back up the M2000 dynamic data.
NOTE
l If you do not replace the fully written tape within the wait time preset in the configuration file, the
Information field in the System Backup dialog box displays the following message:
Tape replacement times out. The data backup fails.
In such a case, you need to insert a tape into the tape drive and performs a new full backup.
l If the newly inserted tape is fully written again, you need to insert another tape for backup. In this way,
change tapes until all the data is backed up.
l After backing up the dynamic data on the tape, run the following command to view the contents of the
tape:
~> . /opt/OMC/svc_profile.sh
~> gtar tfM /dev/st0
----End
Issue 03 (2010-12-31)

8-23
M2000
Managing the M2000 Files and Disks (SUSE)
About This Chapter

This describes how to manage the file systems and disks on the M2000 server and client.
9.2 Managing Files and Disks on the M2000 Server (SUSE)
This describes how to manage the file systems and disks on the M2000 server.
Issue 03 (2010-12-31)

9-1
M2000


The client software runs on the Windows operating system and is based on the JAVA virtual
machine. The installation package of the M2000 client software includes the JAVA virtual
machine supported by Windows.
Required client disk space (only for reference): F = I + T + (S x N), where I refers to the size of
the initial version, that is, about 300 MB; T refers to the temporary space for saving patches,
which is less than 20 MB; S refers to the size of mediation files, which ranges from 3 MB to 10
MB; N refers to the number of NE versions, which depends on the actual situation.
Table 9-1 describes the parameters specified in the equations.
Table 9-1 M2000 client software directory
Directory
Description
client installation path
Installation path of the M2000 client software.

The default path is C:\iManagerM2000ClientClient.
Path for saving client programs.
Path for saving executable files.

\Data
Path for saving NE configuration files.

\diagnosis
Path for saving the information that is used for

locating problems.
NOTE
This path appears only after you run the M2000
diagnosis tool.
9-2

\ext_runcfg
Path for saving the configuration files of

integrated components.
M2000 client installation path\client\dtd
Path for saving .dtd files.

\IDAPI32
Path for saving the localWS dynamic link

libraries.

Issue 03 (2010-12-31)
M2000
Issue 03 (2010-12-31)
Directory
Description
M2000 client installation path\client\lib
Path for saving the library files.

\localWs
Path for saving LocalShell that is used to start

the 2G LMT.

\style
Path for saving the configuration files of the

client.

\Templates
Path for saving the mapping between

administrative regions and their IDs.
M2000 client installation path\client\tmp
Path for saving temporary files during the

upgrade.

\tracefile
Path for saving trace files.

\update
Path for saving upgrade files.
M2000 client installation path\client\cbb
Path for saving the CBB files of the M2000

client.

\configuration
Buffer path of the M2000 client. The path

automatically generates when the client is
started.

\features
Path for saving the feature configuration file of

each subsystem of the M2000 client.

\plugins
Path for saving the configuration file of each

subsystem of the M2000 client as plug-ins.
M2000 client installation path\uninstall
Path for saving the uninstallation program.
M2000 client installation path\script
Root path of the iSStar script.

\run
Path for saving the startup parameter

configuration files of the client and components.

9-3
M2000
Directory
Description
M2000 client installation path\cau
Path for saving the Client Auto Upgrade (CAU)

client software and the version, document
abstract, and group information about the
M2000 client.
NOTE
l The CAU client software provides the upgrade
detection mechanism that is based on the
document abstract for comparing the document
abstract of the server with that of the client. If the
document abstracts are not consistent, you need
to upgrade the client.
l Based on the group information, the server
groups and packs all the client documents
deployed on the server so that the client can
download, install, and upgrade these documents.
Based on the group information, the client also
groups and packs all the client files. Therefore,
these files can be compared with those grouped
and packed by the server after being downloaded.
M2000 client installation path\jre
Path for saving the Java virtual machine

delivered with the M2000 client.
M2000 client installation path\lib
Path for saving the dynamic libraries shared

among the M2000 client, remote alarm
notification client, script framework client, and
data management client.
M2000 client installation path\notify
Path of the remote alarm notification tool.
M2000 client installation path

\TrafficReview
Path of the trace review tool.

Context
CAUTION
You can delete the files when the client is running. Do not delete the files generated on that day.
During the routine O&M, back up and clear the following files:
l
9-4
Trace logs
Issue 03 (2010-12-31)
M2000
Temporary files after the running of the M2000 log collector
Delete the trace logs.
Procedure
Delete the history trace logs saved in the directory M2000 client installation path\client
\tracefile. It is recommended that you preserve the trace logs generated in the latest two
weeks.
l
Delete the temporary files generated after the running of the M2000 log collector.
Delete the temporary files that are generated after the running of the M2000 log collector
and are saved in the directory M2000 client installation path\client\diagnosis.
----End
9.2 Managing Files and Disks on the M2000 Server (SUSE)

This describes how to manage the file systems and disks on the M2000 server.
9.2.1 Introduction to the M2000 Server File System (SUSE)
This describes the structure of the M2000 server files and the planning of disk partition for
various server types.
9.2.2 Viewing the Disk Usage of the M2000 Server on the M2000 Client (SUSE)
9.2.3 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands
This describes how to view the disk usage of the M2000 server by running the SUSE commands.
This operation requires few system resources and does not affect the system operation.
9.2.4 Clearing the Disk Space of the M2000 Server (SUSE)
This describes how to clear the disk space of the M2000 server. Before clearing the disk space,
ensure that the files to be deleted are not required for future operations. Deleting a useful file by
mistake may lead to a system operation error.
9.2.1 Introduction to the M2000 Server File System (SUSE)

This describes the structure of the M2000 server files and the planning of disk partition for
various server types.
The M2000 server software runs on the Linux operating system and rests on the following
software:
l
Oracle database
FTP supporting software
The installation package of the M2000 server software contains the FTP software.
Table 9-2 lists the directories related to the M2000 server software.
Issue 03 (2010-12-31)

9-5
M2000
Table 9-2 Directories for storing the M2000 server software
9-6
Directory
Description
M2000 server installation directory
M2000 server installation directory refers to the

installation directory of the M2000 server software.
By default, the installation directory is /opt/OMC.
M2000 server installation directory/

3rdTools
Refers to the directory for storing the third-party

software.

apache2
Refers to the directory for storing the files related

to the apache httpd.

bin
Refers to the directory for storing executable files.

cau
Refers to the directory for storing the CAU

components.
M2000 client installation path/client
Refers to the directory of the M2000 client that is

deployed on the M2000 server.

component
Refers to the directory for storing the common files

of the core network.

components
Refers to the PRS control directory.

conf
Refers to the directory for storing the configuration

file of universal devices, the configuration file of
engineering documents and the C++ control
program of the HedEx.

data
Refers to the directory for storing the compressed

component files.
M2000 server installation directory/ds
Refers to the directory for storing the files related

to the DesktopService service.

etc
Refers to the directory for storing the system

configuration files and structured query language
(SQL) scripts.

hascript
Refers to the directory for storing the platform

script files.

helper
Refers to the directory for storing the HedEx

program.

init
Refers to the directory for storing the initialization

script file that should be executed during the
M2000 installation.

install
Refers to the directory for storing the script files

used for installing the M2000.
M2000 server installation directory/lib
Refers to the directory for storing library files.

Issue 03 (2010-12-31)
M2000
Issue 03 (2010-12-31)
Directory
Description

lbin
Refers to the directory for storing the system

administration commands.

jre
Refers to the JRE directory shared by the client

components.

med
Refers to the directory for storing the mediationrelated files generated during the operation.

medshare
Refers to the directory for storing the mediation

files.

nhc
Refers to the directory for storing the key static files

required for generating the NHC reports.

nic
Refers to the directory for storing the key static files

required for generating the network information
collecting reports.

plugins
Refers to the directory for storing the dynamic

library files and configuration files related to plugins.

res
Refers to the directory for storing resource files.

resourcemonitor
Refers to the directory for storing the resource

monitoring files.

sacscript
Refers to the directory for storing the script files

provided by the NIC module.

server
Refers to the directory for storing the dynamic

library files related to M2000 alarms.

sso
Refers to the directory for storing the SS0 program

files.

swapfiles
Refers to the temporary switch directory.

tomcat

data of the webpage server.

tools
Refers to the directory in which the common script

tools of the M2000.

var
Refers to the directory for storing the log files,

performance files, and files recording exported
alarms.

uninstall
Refers to the directory for storing the script file used

for uninstalling the M2000.

upgrade
Refers to the directory for storing the upgrade

scripts.

9-7
M2000
Directory
Description

webapps
Refers to the directory for storing the webpage

service files.
/export/home/omc/var
Refers to the directory for storing the M2000

operation data.
/export/home/omc/var/syslog
Refers to the directory for storing system logs.
/export/home/sysm/ftproot/pm
Refers to the directory for storing the traffic

measurement data of each NE, which is reported as
files,.

var/itf_n/FileTransferIRP/PM
Refers to the directory for storing the northbound

CORBA interface performance files.
/export/home/omc/var/fileint/cm

data files that are periodically exported.
/export/home/omc/var/fileint/pm
Refers to the directory for storing the exported

performance result files.
/export/home/sysm/ftproot/NE
name/Software
Refers to the directory for storing the NE version

package.
/export/home/sysm/ftproot/NE
name/Data/NE fdn
Refers to the directory for storing the NE data

backup.
NOTE
l The NE FDN is a code representing an NE sample in
the program.
l The data generated for manual backup is located in
the BAKDATA****** directory. The data
generated for automatic backup is located in the
AUTOBAKDATA****** directory.
9-8
/export/home/omc/var/logs
Refers to the directory for storing the M2000 log

files.
/opt/oracle/oradb/admin/ossdb/
bdump
Refers to the directory for storing the

alert_ossdb.log file, which is the log file of the
Oracle.
/var/log
Refers to the directory for storing the SUSE Linux

log files.
/export/home/backup/omc
Refers to the directory for storing the backup files

of dynamic data.
/export/home/omc/var/etc/conf/
license
Refers to the directory for storing the license file of

the M2000.
/export/home/omc/sso
Refers to the directory for storing the SS0 data files.

Issue 03 (2010-12-31)
M2000
Disk Partitioning of the HP rx2660 Server

In standard configuration, the HP rx2660 server is equipped with four 146 GB hard disks. Table
9-3 describes how to partition the four disks.
Table 9-3 Disk partitions of the HP rx2660 server
Hard
Disk
Partition
Path
Partition
Type
Mountin
g Point
Size (GB)
Description
Four 146
GB hard
disks act
as RAID 1
+0. Only
one hard
disk can
be viewed
in the
operating
system.
dev/cciss/
c0d0p1
FAT
/boot/efi
0.5
Booting partition
17
Data exchange
partition
dev/cciss/
c0d0p2
dev/cciss/
c0d0p3
reiser
32
Root partition
dev/cciss/
c0d0p4
Linux
LVM
None
Remaining
space
Data partition
Disk Partitioning of the HP rx7640 Server

In standard configuration, the HP rx7640 server is equipped with two 146 GB hard disks. Table
9-4 describes how to partition the two disks.
Table 9-4 Disk partitions of the HP rx7640 server
Hard
Disk
No.
Partition
Path
Partition
Type
Mountin
g Point
Size (GB)
Description
/dev/sda1
FAT
/boot/efi
0.5
Booting partition
34
Data exchange
partition
/dev/md0
/dev/md1
reiser
Remaining
space
Root partition
/dev/sdb1
Linux
LVM
/boot/
efibackup
0.5
/boot/efi Mirroring
partition
Used as the mirroring disk for the first hard disk
Table 9-5 and Table 9-6 describes how to partition the disk array.
Issue 03 (2010-12-31)

9-9
M2000
Table 9-5 Disk partitions of the S3200 disk array

Hard Disk
Partition Path
Size (GB)
Description
Seven hard
disks act as
RAID 5.
/dev/sdc
800
Volume name oss_v0
Seven hard
disks act as
RAID 5.
/dev/sdd
800
Volume name oss_v1
Two disks
Act as the hotspare disk
Table 9-6 Disk partitions of the S2600 disk array

Hard Disk
Partition Path
Size (GB)
Description
Ten hard
disks act as
RAID 10.
/dev/sdc
671
Volume name oss_app0
/dev/sdd
671
/dev/sde
671
Two disks
Act as the hotspare disk
9.2.2 Viewing the Disk Usage of the M2000 Server on the M2000
Client (SUSE)
Prerequisite
l
Context
This operation requires very few system resources and does not affect system operation.
Procedure
Step 2 Click the Hard Disk Monitor tab. The disk usage of the M2000 server is displayed, as shown
in Figure 9-1.
9-10

Issue 03 (2010-12-31)
M2000
Figure 9-1 Hard Disk Monitor
NOTE
In the Status column, the green icon indicates that the disk usage of the corresponding process is normal;
the red icon indicates that the disk usage of the corresponding process is abnormal. When the disk usage
of a process exceeds the disk usage threshold, the icon corresponding to the process is displayed in red.

----End
9.2.3 Viewing the Disk Usage of the M2000 Server by Running

SUSE Commands
This describes how to view the disk usage of the M2000 server by running the SUSE commands.
This operation requires few system resources and does not affect the system operation.
Prerequisite
You have logged in to the M2000 server as user root.
Procedure
Step 1 Run the following query command:
# df -k
Step 2 View the disk usage.
Generally, the disk usage is less than 80%, which indicates that the output Use% is less than
80%.
Issue 03 (2010-12-31)

9-11
M2000
If the disk usage is excessive, you need to clear the disk space.
----End
9.2.4 Clearing the Disk Space of the M2000 Server (SUSE)

This describes how to clear the disk space of the M2000 server. Before clearing the disk space,
ensure that the files to be deleted are not required for future operations. Deleting a useful file by
mistake may lead to a system operation error.
Context
During the routine operation and maintenance, back up and clear the following files to release
more disk space:
l
Files storing the information about NEs and the M2000 server
Software upgrade package and decompressed files
Trace logs
Backup files
Temporary files created during the system operation
CAUTION
You can delete files when the server is running. Before deleting files, run the ls -l command to
check the date when the files are generated. Do not delete the files generated on the current day.
Procedure
Step 1 Export the files that store the information about NEs and the M2000 server, and back up the files
to a tape.
The files are as follows:
NOTE
The directories for saving alarm dump files can be set on the client. This provides the default directories.
l Files generated during automatic alarm dump

Event alarm dump files are stored in the /export/home/omc/var/fm/dump/event/ directory.
Fault alarm dump files are stored in the /export/home/omc/var/fm/dump/history/ directory.
l User log files
User log dump files are stored in the /opt/OMC/var/userlogs directory.
l Core files generated by the system
Core files refer to the files in the /export/home/omc/var/logs/ directory.
l Trace history files
Trace history files are stored in the /export/home/omc/var/logs/tracebak/ directory.
Step 2 Delete the software update package and the decompressed files.
9-12

Issue 03 (2010-12-31)
M2000
After the software is successfully upgraded, you can delete the original upgrade package and
the decompressed files. The upgrade package and decompressed files are stored in the folder
named after the upgrade patch in the /export/home directory.
CAUTION
Generally, the decompressed upgrade files are stored in the /export/home directory. The folder
name of the upgrade files is created according to the upgrade patch name. Sometimes, the folder
is created in the /export/home/bak directory.
Step 3 Delete trace Logs.
Modify the value of tracebackupnum in the tracemonitor_svc_ex.xml file to reduce the
number of trace backup files.
Edit the tracemonitor_svc_ex.xml file in the /opt/OMC/etc/conf/ directory to set the trace log
monitor period, size limit, and number of backup files. /opt/OMC is the default installation path
of the M2000 server software.
The content of tracemonitor_svc_ex.xml is as follows:
<?xml version="1.0" encoding="iso-8859-1"?>
<tracemonitor name="tracemonitor" mount="/imap/tracemonitor">

<param name="checktracetime">300</param>

<param name="tracebackupnum">50</param>
</tracemonitor>
In checktracetime, you can set the trace log monitor period. The system checks the trace file at
the regular interval of 300s. In tracebackupnum, you can set the number of backup trace files
for each process in the /opt/OMC/var/logs/tracebak directory. For a process, if the number of
backup trace files in the tracebak directory exceeds the preset value, the system automatically
deletes the earliest trace files.
Step 4 Clear the backup files.
l After the upgrade, delete the backup files for the upgrade or copy them to a tape.
l Periodically back up all the files in the /export/home/backup/omc directory to tapes.
Step 5 Delete the files that are not required.
Before clearing the disk space, ensure that the files to be deleted are not required for future
operations. Deleting a useful file by mistake may lead to a system operation error.
1.
Choose Start > All Programs > iManager M2000 Client > M2000 Log Information
Collector .
2.
In the displayed M2000 Log Information Collector dialog box, select Core files in
server. Set the start time and end time for searching for core files.
3.
Click Collect.
Save the collected core files to the path c:\Program Files\client\diagnosis\collected
files. Path c:\Program Files is the default installation path of the M2000 client software.
Issue 03 (2010-12-31)

9-13
M2000
CAUTION
The M2000 log collection tool collects the stack information from the core files. In addition
to the stack information, the core files also contain other information. Therefore, before
deleting the core files, confirm the deletion with Huawei technical support engineers. The
size of the core files is large, therefore, you need to compress the core files before sending
them.
4.
After confirming all the core files and the stack files with Huawei technical support
engineers, delete the core files and stack files that are not required for future operations.
5.
Stop the Huawei server and delete all the files in the /var/tmp directory. Delete other files
that are not required.
----End
9-14

Issue 03 (2010-12-31)
M2000
10
Backing Up and Restoring the M2000

System (SUSE)
About This Chapter

This describes how to back up and restore the M2000 system.
10.1 Data Backup and Restore of the M2000 (SUSE)
This describes the backup scheme, backup strategy, and restore scenarios of M2000 dynamic
data.
10.2 Backing Up and Restoring M2000 Dynamic Data (SUSE)
This describes how to back up and restore M2000 dynamic data.
Issue 03 (2010-12-31)

10-1
M2000
10.1 Data Backup and Restore of the M2000 (SUSE)

This describes the backup scheme, backup strategy, and restore scenarios of M2000 dynamic
data.
10.1.1 Backup of M2000 Dynamic Data (SUSE)
Dynamic data backup refers to the backup of the M2000 dynamic service data. It is used to
restore the history data when the M2000 is running properly or the static data restoration is
complete.
10.1.2 Strategies on Backup and Restore of the M2000 System (SUSE)
This section describes the backup of the M2000 system, which involves the backup scenarios,
restore scenarios, rules for naming backup files, and rules for naming backup tapes.
10.1.1 Backup of M2000 Dynamic Data (SUSE)

Dynamic data backup refers to the backup of the M2000 dynamic service data. It is used to
restore the history data when the M2000 is running properly or the static data restoration is
complete.
For details about the backup contents, backup modes, and storage media of the dynamic data
backup, see Table 10-1.
Table 10-1 Introduction to dynamic data backup
Item
Content
Backup
contents
l Database OSSDB
Backup
modes
Periodic
backup
Performs a full backup at a specified time every day. After

periodic backup is set, the dynamic data is backed up once
every day. After a new backup is performed, all the backup
files in the backup directory are deleted automatically.
Manual
backup
Full backup: backs up all the dynamic data. When a new full
backup is performed, all the backup files in the backup
directory are deleted automatically.
l The M2000 system files: files in the /export/home/omc/var and /export/

home/sysm directories.
Incremental backup: backs up all the dynamic data. When a

new incremental backup is performed, all the backup files in
the backup directory are deleted automatically. The Oracle
database does not support incremental backup currently.
Therefore, do not perform operations of incremental backup.
Storage
device
l Tape
l Hard disk
l Tape and hard disk
l Veritas: refers to the storage device of the NetBackup server.
10-2

Issue 03 (2010-12-31)
M2000
Item
Content
Directory of
backup files
/export/home/backup/omc
Number of
the tapes
required for
backup
Generally, one 72 GB tape is required for each backup. You can determine the
number of tapes according to the actual situation. If the earlier tapes are no
longer used, you can use earlier tapes for new backup.
After the backup is performed, the backup contents are automatically packaged as a backup file.
10.1.2 Strategies on Backup and Restore of the M2000 System

(SUSE)
This section describes the backup of the M2000 system, which involves the backup scenarios,
restore scenarios, rules for naming backup files, and rules for naming backup tapes.
Typical Scenarios for M2000 Data Backup

Dynamic data backup is applicable to routine maintenance. The Oracle database supports only
full backup.
Typical Scenarios for M2000 Data Restore

If the M2000 is running properly, the dynamic data restore can roll the system back to the status
of earlier days such as the previous week.
Rules for Naming Backup Files of Dynamic Data

When backing up the dynamic data, name the backup files in the following format: allYYYYMMDDhhmmss.tar.
For example:
The file name all-20040601042002.tar refers to a full backup file or an incremental backup file
generated on 01.06.04 at 04:20:02.
NOTE
After the system performs backup, the latest backup information is recorded in the /export/home/
backup/omc/backup.log file. The information contains the date on which the backup file is
generated, directory for storing the backup file, and the file name.
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 is
compressed into the all-YYYYMMDDhhmmss.tar file, and the all-YYYYMMDDhhmmss folder is
automatically deleted.
Rules for Naming the Tapes That Store the Backup Data
The rule for naming a backup tape is as follows: dynamic data backup tape (backup date).
For example, if a tape is labeled dynamic data backup tape (2007-11-28), it indicates that the
dynamic data is backed up on 2007-11-28.
Issue 03 (2010-12-31)

10-3
M2000
10.2 Backing Up and Restoring M2000 Dynamic Data

(SUSE)
This describes how to back up and restore M2000 dynamic data.
10.2.1 Setting the Storage Device of Backup Data Using Linux Commands
This describes how to set the storage device of backup data.
10.2.2 Setting the Storage Device of Backup Data Through the Client
You can set the storage device for backup data through the client.
10.2.3 Setting the Wait Time for Replacing a Tape
You can store the dynamic data on multiple tapes. If the current tape is fully written, the system
automatically ejects the tape and waits you to replace it. By modifying the configuration file,
you can set the wait time.
10.2.4 Periodically Backing Up M2000 Dynamic Data (SUSE)
This describes how to periodically back up the M2000 dynamic data.
10.2.5 Manually Backing Up M2000 Dynamic Data (SUSE)
This describes how to manually back up the M2000 dynamic data.
10.2.6 Restoring the M2000 Dynamic Data (SUSE)
This describes how to restore the M2000 dynamic data.
10.2.1 Setting the Storage Device of Backup Data Using Linux

Commands
This describes how to set the storage device of backup data.
Prerequisite
Log in to the M2000 server as user omcuser.
Context
The files for the dynamic data backup are stored on hard disks. To store the backup files on a
tape, you need to modify the relevant settings in the /export/home/omc/var/etc/conf/
maintainsvc.xml and /opt/OMC/tools/Backup/config/generalbus.cfg file.
You can configure the storage device of backup data when the M2000 is running.
10-4

Issue 03 (2010-12-31)
M2000
CAUTION
l
Do not modify the storage device file when the backup is in progress.
When you perform a full backup, the backup overwrites the backup files that already exist
on the disk.
After you change the current storage device, for example, from a disk to a tape, you must
perform a full backup again. Otherwise, dynamic data may fails to be restored owing to the
loss of certain backup data.
If you set the backup media parameter to tape or all, remove and label the tape after the
backup is complete.
Do not replace the storage device during the backup process.
For data security, back up the dynamic data to a tape.
Procedure
Step 1 Ensure that the M2000 daemon is running.
Run the following commands to check whether the M2000 daemon is running.
~> daem_ps
After running the daem_ps command,
if ...
Then ...
The output exists
You can infer that the M2000 daemon is

running. Proceed with the next step.
No output exists
You can infer that the M2000 daemon is not

running. Run the following command to start
the M2000 daemon:
# start_daem
Step 2 Navigate to the /export/home/omc/var/etc/conf directory, and then run the vi command to view
the maintainsvc.xml file.
~> cd /export/home/omc/var/etc/conf
~> vi maintainsvc.xml
Step 3 Find the line <param name="backupMedia">, and change the disk for the full backup to
the actual storage device.
<module name="all">
?-?<param name="backupMedia">disk</param>
and
<module name="inc">
?-?<param name="backupMedia">disk</param>
Issue 03 (2010-12-31)

10-5
M2000
Table 10-2 lists the values of the backupMedia parameter.

Table 10-2 Values of backupMedia
Storage Media
Value
Hard disks (on the M2000 server)
disk
Tapes
tape
Hard disks and tapes
all
Storage device of the NetBackup server
veritas
NOTE
l If backupMedia is set to veritas, the system automatically packs the backup data and moves the backup
data to a storage device of the NetBackup server. As a result, the M2000 server does not keep any
backup data.
l The storage device of the NetBackup server can be a tape drive, tape library, or disk, which is determined
by the Veritas backup and restore solution.
Step 4 Save the file and quit.

Step 5 To back up dynamic data on a tape, specify the path of the tape drive. Otherwise, go to Step 6.
1.
Navigate to the /opt/OMC/tools/Backup/config directory and open the generalbus.cfg

file by running the vi command.
~> cd /opt/OMC/tools/Backup/config
~> vi generalbus.cfg
2.
Search for the [STEP_TRANSFERTOMEDIA] area, and then set the value of
tapepath_linux to the directory of the tape drive.
[STEP_TRANSFERTOMEDIA]
......
tapepath_linux=/dev/rmt/0
......
NOTE
l This section takes /dev/rmt/0 as an example. Replace /dev/rmt/0 with actual directory of the tape
drive during actual operations.
l If multiple tape drives are installed on the server, select a tape drive by referring to 14.1.4 How
to Select the Tape Drive (SUSE).
3.
Save the file and quit.
Step 6 Load the configuration files of all the processes again.

~> svc_adm -cmd reload
----End
10.2.2 Setting the Storage Device of Backup Data Through the

Client
You can set the storage device for backup data through the client.
10-6

Issue 03 (2010-12-31)
M2000
Prerequisite
l
The M2000 server is running properly.
The connection between the M2000 client and server is normal.
Context
You can set the storage device for backup data when the M2000 is running.
CAUTION
l
Do not modify the configuration files of storage devices when the backup is in process.
When you perform a full backup, the new backup files replace the backup files that already
exist on the disk.
After you change the current storage device, for example, from Disk to Tape, you need to
perform a full backup again. Otherwise, the dynamic data may fail to be recovered due to
the loss of some backup data.
Set the storage device to Tape or Disk and Tape, remove and label the tape when the
backup is complete.
Do not replace the storage device when the backup is in process.
For data security, back up the dynamic data to a tape.
When recovering the static data and restoring the system, use the dynamic data backup files
stored on the tape to recover the latest service data.
Procedure
Step 1 Start the M2000 client and log in to the M2000 server.
Step 2 Click Maintenance > Backup Management > System Backup. The System Backup interface
is displayed, as shown in Figure 10-1.
Figure 10-1 Setting the storage device (I)
Step 3 Click Reset. The Medium Type Setting dialog box is displayed. Set the storage device in the
dialog box, and then click OK, as shown in Figure 10-2.
Issue 03 (2010-12-31)

10-7
M2000
Figure 10-2 Setting the storage device (II)
NOTE
l The parameter veritas refers to the storage device of the NetBackup server.
l If the storage device is set to veritas, the system automatically packs the backup data and moves the
backup data to the storage device of the NetBackup server. After the operation, the M2000 server does
not hold the backup data that is moved to the storage device.
l The storage device of the NetBackup server is determined by the Veritas backup and restore solution.
The storage device is a tape drive, a tape library, or a disk.
Step 4 The Confirm dialog box is displayed, prompting you for a full backup after you modify the
storage device. Click Yes.
Step 5 When the change of storage device is complete, the Message dialog box is displayed. Click
OK.
Step 6 Perform a full backup. For details, see 10.2.5 Manually Backing Up M2000 Dynamic Data
(SUSE).
----End
10.2.3 Setting the Wait Time for Replacing a Tape

You can store the dynamic data on multiple tapes. If the current tape is fully written, the system
automatically ejects the tape and waits you to replace it. By modifying the configuration file,
you can set the wait time.
Prerequisite
Log in to the server as user omcuser through SSH mode.
Context
If multiple tapes are required for data backup, you can modify the relevant contents in the /opt/
OMC/tools/Backup/config/generalbus.cfg file to set the wait time for replacing a tape. By
default, the wait time is set to 120 minutes.
You can configure the wait time for replacing a tape when the M2000 is running.
10-8

Issue 03 (2010-12-31)
M2000
CAUTION
Do not set the wait time for replacing a tape when the backup is in progress.
Procedure
Step 1 Ensure that the M2000 daemon is started.
Run the following commands to check whether the M2000 daemon is started:
~> daem_ps
If...
Then...
There is any output after you run the

daem_ps command
The M2000 daemon is started. Proceed with the

next step.
There is no output after you run the

daem_ps command
The M2000 daemon is not started. Run the

following command to start the daemon:
~> start_daem
Step 2 Navigate to the /opt/OMC/tools/Backup/config directory and open the generalbus.cfg file by
running the vi command.
~> cd /opt/OMC/tools/Backup/config
~> vi generalbus.cfg
Step 3 Search for the [STEP_TRANSFERTOMEDIA] area, and then set the value of
changetape_timeout to the wait time for replacing a tape.
[STEP_TRANSFERTOMEDIA]
......
changetape_timeout=120
......
NOTE
l The value of the changetape_timeout parameter indicates the wait time, which is represented in
minutes.
l The default wait time is 120 minutes.
Step 4 Save the file and quit.

Step 5 Load the configuration files of all the processes again.
~> svc_adm -cmd reload
----End
10.2.4 Periodically Backing Up M2000 Dynamic Data (SUSE)

This describes how to periodically back up the M2000 dynamic data.
Issue 03 (2010-12-31)

10-9
M2000
Prerequisite
l
The tape drive is connected properly. It holds a tape if you plan to back up data on the tape.
A hard disk has sufficient free space if you plan to back up data on the hard disk.
Context
Generally, M2000 dynamic data is backed up periodically. The periodic backup of the dynamic
data is performed in full backup mode.
Dynamic data backup has no restriction on backup time. The backup can be performed during
the system operation. The time required for backing up M2000 dynamic data is related to the
actual environment. Generally, it takes about 2.5 hours to 3 hours to back up the dynamic data.
NOTE
Do not suspend a periodic backup task. Because the latest data fails to be restored after data lost caused by
an accident, for example, the power-off of the server.
Procedure
Step 1 On the main window, choose Maintenance > Task Management.
Step 2 Choose Task Type > Backup > Server Backup in the navigation tree and double-click the
node. The Attribute dialog box of server periodic backup is displayed, as shown in Figure
10-3.
Figure 10-3 Periodic backup
10-10

Issue 03 (2010-12-31)
M2000
Step 3 Click Common Parameters, and set Task Name and Start Time.
NOTE
You do not need to set Extended Parameters.
Step 4 Click OK.

The system performs periodic backup automatically.
following message:

backup operation.
Issue 03 (2010-12-31)

10-11
M2000
NOTE
Information field in the System Backup dialog box displays the following message:
l After backing up the dynamic data on the tape, run the following command to view the contents of the
tape:
~> gtar tfM /dev/st0
----End
10.2.5 Manually Backing Up M2000 Dynamic Data (SUSE)

This describes how to manually back up the M2000 dynamic data.
Prerequisite
l
The tape drive is connected properly. It holds a tape if you plan to back up data on the tape.
A hard disk has sufficient free space if you plan to back up data on the hard disk.
Context
Manual backup is required in special or emergency situations such as the loss of backup tapes
or the failure of the M2000 system.
Dynamic data backup has no restriction on backup time. The backup can be performed during
the system operation. The time required for backing up M2000 dynamic data is related to the
actual environment. Generally, it takes about 2.5 hours to 3 hours to back up the dynamic data.
NOTE
The files for the dynamic data backup are stored on hard disks. If you plan to change the current storage
device, see 10.2.2 Setting the Storage Device of Backup Data Through the Client.
Procedure
Step 1 On the main window, choose Maintenance > Backup Management > System Backup. The
System Backup dialog box is displayed.
10-12

Issue 03 (2010-12-31)
M2000
Step 2 On the System Backup dialog box shown in Figure 10-5, click Full Backup.
following message:
backup operation.
NOTE
Information field in the Backup Management dialog box displays the following message:
l After backing up the dynamic data on the tape, log in to the M2000 server as user omcuser, run the
following command to view the contents of the tape:
~> gtar tf /dev/st0
----End
Issue 03 (2010-12-31)

10-13
M2000
10.2.6 Restoring the M2000 Dynamic Data (SUSE)

This describes how to restore the M2000 dynamic data.
Prerequisite
l
Log in to the M2000 server as user root.
You have obtained the backup files for restoring the M2000 dynamic data.
The M2000 is running properly or the static data restoration is complete.
Context
Based on the latest full backup files of the M2000, you can restore the M2000 system data. After
you 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 alarm
data, is not packed in the backup file package, the M2000 starts the automatic synchronization
function to obtain and handle the data.
l
During the restoration of dynamic data, the M2000 services stop automatically and do not
process performance data or alarm data of NEs.
After you change the IP address of the server or the password of the database user, you
cannot restore the dynamic data to the data that is backuped when the IP address of the
server or the password of the database user is not changed.
Procedure
Step 1 Skip this step and go to Step 3 if the backup files are stored on a hard disk. Copy the backup
files to a hard disk if the backup files are stored on a tape.
# cd /
# tar xf /dev/st0
If the following message is displayed during the execution of the command, ignore the message.
tar: Removing leading '/' from member names
CAUTION
The decompressed file is stored in the same path as the compressed one. It is not related to the
path where you perform the decompression operation.
Step 2 Change the right and owner of the /export/home/backup directory.
# chmod -R 770 /export/home/backup
# chown -R omcuser:omcsysm /export/home/backup
Step 3 Switch to user oracle and restart the Oracle. Then, switch to user root.
To stop the Oarcle, see 14.2.3 How to Stop the Oracle (HP). To start the Oracle, see 14.2.2
How to Start the Oracle (HP).
10-14

Issue 03 (2010-12-31)
M2000
Step 4 Restore the dynamic 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 need to decompress the relevant package regardless of the full backup file that is to be restored.
2.
Navigate to the path after the decompression.

# cd name of the backup file that stores dynamic data
For example:
# cd all-20080130180622
3.
Run the following script to restore dynamic data:

# ./restore.sh
4.
When the system displays the following message, type the password of user sys of the
database.
Note: Enter q/Q to exit this tool.
Please input the supperuser's password of database[default:emsems]:
NOTE
You can type q or Q to quit the script.
5.
When the system displays the following message, 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 5 Run the following command to start the M2000 services:

# cd /opt/OMC/tools/common
# ./commonop.sh -ostartsvc
l If the system displays the following information, you can infer that the M2000 service is
started.
Operation succeeds
l If the system displays the following information, you can infer that the M2000 service fails
to be started. In such a case, contact Huawei technical support engineers for assistance.
Performing Start OMC services failed
Issue 03 (2010-12-31)

10-15
M2000
NOTE
Starting the M2000 service takes a long time. Wait with patience.
Step 6 Ensure that all the M2000 services are started.

# svc_adm -cmd status
Check the value after Not Running : in the last line. If the value is 0, you can infer that all
the M2000 services are started.
In this case, the data restoration is complete.
Step 7 Delete the backup file after the data restoration.
# cd /export/home/backup/omc
# rm -rf directory for storing the decompressed backup files
For example:
# rm -rf all-20080130180622
----End
10-16

Issue 03 (2010-12-31)
M2000
11
Maintaining the M2000 System (SUSE)
About This Chapter

This describes how to perform the M2000 routine maintenance and recommends some
maintenance items and procedures.
11.1 M2000 Routine Maintenance Items(SUSE10)
This section describes the recommended maintenance items of the M2000 system.
11.2 Checking the Configuration of Alarm Timing
This section describes how to check whether the policy on automatic dumping alarm data from
the alarm database is reasonable.
11.3 Checking the Configuration of Automatic Log Dump
This section describes how to check whether the system of automatic dumping alarm data from
the alarm database is satisfactory.
11.4 Checking the Synchronization Time of NE Log
This section describes how to check whether the configuration of synchronization time of the
NE log is correct. The purpose is to avoid the server overload owing to the conflict of time when
you perform tasks on the server.
11.5 Checking the Configuration of the File Server
This section describes how to check whether the configuration of the file server is appropriate.
11.6 Checking the Configuration of System Backup
This section describes how to check whether the periodic backup of the M2000 server and NEs
are started and whether the start time is correct. The purpose is to avoid the server overload
owing to the conflict of time when you perform tasks on the server. This section also describes
how to check whether backup files are generated in the disk.
11.7 Checking the Configuration of System Monitoring
This section describes how to check the configuration of system monitoring.
11.8 Checking the Synchronization Time of NE Configuration
This section describes how to check whether the time for synchronizing NE configuration data
is appropriate. The purpose is to avoid the server overload. The server overload may occur when
the synchronization together with other tasks on the server is performed at the same time.
11.9 Checking the Status of Performance Measurement
Issue 03 (2010-12-31)

11-1
M2000
This section describes how to check the performance measurement state. You must ensure that
all the required measurement counters and measurement objects are in proper status.
11.10 Checking the Missing Performance Result
To ensure that no result is lost, you must check that the missing performance result exists.
11.11 Checking the Alarm Reception
Check the alarm reception and ensure that the M2000 can receive alarms from NEs in real time.
11.12 Checking the NMS Connection
This section describes how to check the NMS connection and to ensure that the NMS connection
is normal.
11.13 Checking the Functionality of Alarm Box
Check the function of generating visual and audible alarms for the alarm box and ensure that
the alarm box can indicate the alarms on the M2000 in real time.
11.14 Checking the Owner of the M2000 File System
This section describes how to check the owner of the M2000 file system. You need to check the
owner of the M2000 file system regularly to ensure proper user operations because some tools
or operations may change the owner of the M2000 file system.
11.15 Checking the Threshold of Network Management Capability
This section describes how to check whether the M2000 management capability exceeds the
threshold. Ensure that the number of equivalent NEs managed by the M2000 does not exceed
the capability limit.
11.16 Check OMC Alarms/Events
This section describes how to check whether the M2000 system is normal. This section also
describes how to check whether the alarms and events of the M2000 are generated.
11.17 Checking Connections Between the M2000 and NEs
This section describes how to check the connections between the M2000 and NEs.
11.18 Checking the Status of the M2000 Routes
This section describes how to check the configuration of the M2000 routes.
11.19 Checking M2000 Logs
M2000 user logs record the details about user operations, such as user name, start time, end time,
and log type. The M2000 system administrators and operators can query user logs.
11.20 Checking SUSE Error Logs
This describes how to check the error logs of the SUSE operating system.
11.21 Checking the CPU Usage of the M2000 Server (SUSE)
This describes how to check whether the CPU usage is in the required range.
11.22 Checking the Disk Usage of the M2000 Server (SUSE)
This describes how to check the disk usage and clear the expired log files, temporary files, and
other files that are no longer in use. This operation requires very few system resources and does
not affect the system operation.
11.23 Checking M2000 Database Status (SUSE)
After installing the Oracle software and patches, you need to check the status of the database to
ensure that the server starts successfully.
11.24 Checking the States of M2000 Services
This section describes how to check the states of M2000 services. This operation requires few
system resources and does not affect system operation.
11-2

Issue 03 (2010-12-31)
M2000
11.25 Checking the Core Files on the Server

This section describes how to check the /export/home/omc/var/logs directory and to ensure
that core files do not exist.
11.26 Backing Up the M2000 System (SUSE)
This describes how to back up the M2000 system. The M2000 backup refers to the backup of
M2000 databases and system files. The M2000 system files refer to those files in the /export/
home/omc/var and /export/home/sysm directories.
11.27 Querying the M2000 License
11.28 Checking the Time of the M2000 Server (SUSE)
This describes how to check the time of the M2000 server.
11.29 Checking the Power Supply of the M2000 Server
This describes how to check the power supply of the M2000 server.
Issue 03 (2010-12-31)

11-3
M2000
11.1 M2000 Routine Maintenance Items(SUSE10)

This section describes the recommended maintenance items of the M2000 system.
Table 11-1 lists the recommended maintenance items of the M2000 system. You can add or
delete maintenance items according to your requirements.
Table 11-1 Maintenance item list
11-4
No.
Item
Freq
uenc
y
Reference
Check the configuration of

alarm timing tasks.
Wee
kly
The time for alarm timing tasks is set

correctly. This prevents the time conflict
with background tasks. The conflict may
result in the CPU overload.

automatic log dump.
Wee
kly
The time for automatic log dump is set

properly. This prevents the time conflict

NE log synchronization
time.
Wee
kly
The time for NE log synchronization is set

correctly. This prevents the time conflict

the file server.
Wee
kly
The file server is configured correctly.

the system backup.
Wee
kly
The time for the automatical and periodical

backup of the M2000 server and NEs is set
correctly. The backup files are generated in
the disks.
Checking the Configuration

of System Monitoring
Wee
kly
The threshold for system monitoring is set

correctly.
Check the setting of NE

configuration
synchronization time.
Wee
kly
The time for NE configuration

synchronization is set properly.
Check the performance

measurement status.
Daily
All measurement counters and measurement

objects are being measured.
Check the loss of

performance results.
Daily
No performance results are lost.
10
Check the status of alarm

reception.
Daily
The alarms reported by NEs are received in

real time.
11
Check the connection status Daily

of the NMS.
The NMS can collect the alarms and

performance data reported by the M2000.

Issue 03 (2010-12-31)
M2000
Issue 03 (2010-12-31)
No.
Item
Freq
uenc
y
Reference
12
Check the status of the alarm

box.
Daily
The alarm box can raise M2000 alarms in

real time.
13
Check whether the

management capability of
the M2000 exceeds the
limit.
Wee
kly
The number of the equivalent NEs managed

by the M2000 does not exceed the
management capability of the M2000.
14
Check OMC alarms.
Daily
No OMC alarms are generated.
15
Check connections between

the M2000 and NEs.
Daily
This monitors the status of NEs and NE

connections and checks the connections
between the M2000 and NEs.
16
Check the status of M2000

routes.
Wee
kly
The corresponding boot files exist in the

directory /etc/rc2.d.
17
Check M2000 logs.
Daily
The system is operational.
18
Check SUSE Linux error

logs.
Daily
No error logs are generated.
19
Check the disk usage of the

M2000 server.
Daily
The disk usage should be smaller than 90%.
20
Check the database status.
Daily
The databases are functional, and the usage

is less than 80%.
21
Check the total number of

processes.
Daily
When the M2000 is running, run the

command to view the processes. The server
displays all the processes that are running.
The message "not running" is not displayed.
22
Check the status of M2000

services.
Daily
All the processes are running properly. The

message "not running" is not displayed.
23
Check the core file of the

server.
Daily
In the /export/home/omc/var/logs
directory, there are no files whose names
start with core.
24
Back up the M2000 system.
Wee
kly
Back up the M2000 database and system

files. View the backup files on the disks and
tapes.
25
Check the time of the

M2000 server.
Wee
kly
The time of the M2000 server is set

correctly.
26
Check the status of the local

disks on the server and the
status of the disks in the disk
array.
Wee
kly
The state of all disks available is online.

The KSTATE column of pl, sd, and v is
ENABLED. The STATE column is
ACTIVE. The usage of all partitions is less
than 80%.

11-5
M2000
No.
Item
Freq
uenc
y
Reference
27
Check the power supply of

the M2000 server.
Mont
hly
The power supply is functional.
28
Check the hardware of the

M2000 server.
Daily
The hardware of the M2000 server is intact.
29
Check the external devices

of the M2000 server.
Mont
hly
For details about how to check the CD-ROM

drive and the tape drive, see the Linux
Online Help.
30
Check the results collected

by the SMC.
Daily
The operating environment of the M2000

server is normal.
For details about the operation and maintenance of NEs, see the M2000 Client Online Help.
11.2 Checking the Configuration of Alarm Timing

This section describes how to check whether the policy on automatic dumping alarm data from
the alarm database is reasonable.
Prerequisite
l
You are authorized to check the configuration of M2000 integrated task management.
Procedure
Step 2 Under the Database Capacity Management node in the Task Type navigation tree in the left
pane, select the Alarm Data node.
You can also double-click the Alarm/Event Log Dump node to open the Attributes window.
Step 3 Select the task in the right pane and click Attribute.
Step 4 In the Attribute window, check the configuration of automatic alarm data dumping.
Step 5 Ensure that the configuration of automatic alarm data dumping is proper.
----End
11.3 Checking the Configuration of Automatic Log Dump

This section describes how to check whether the system of automatic dumping alarm data from
the alarm database is satisfactory.
11-6

Issue 03 (2010-12-31)
M2000
Prerequisite
l
You have logged in to the M2000 .
You are authorized to check the configuration of M2000 integrated task management.
Procedure
Step 2 Check the configuration of automatic log dump of NE operation logs.
1.
Under the Database Capacity Management node in the Task Type navigation tree in the
left pane, select NE Operation Log.
2.
Choose the task in the right pane. Click Attribute.
3.
Check the configuration of auto NE operation log dump in the Attribute window.
4.
Ensure that the configuration is reasonable.
Step 3 Check the configuration of automatic log dump of NE security logs.

1.
left pane, select NE Security Log.
2.
3.
Check the configuration of auto NE security log dump in the Attribute window.
4.
Step 4 Check the configuration of automatic log dump of NE system logs.

1.
left pane, select NE System Log.
2.
3.
Check the configuration of auto NE system log dump in the Attribute window.
4.
Step 5 Check the configuration of automatic log dump of NM operation logs.

1.
left pane, select NM Operation Log Dump.
2.
3.
Check the configuration of auto NM operation log dump in the Attribute window.
4.
Step 6 Check the configuration of automatic log dump of NM system logs.

1.
left pane, select NM System Log Dump.
2.
3.
Check the configuration of auto NM system log dump in the Attribute window.
4.
Step 7 Check the configuration of automatic log dump of NM security logs.

1.
Issue 03 (2010-12-31)
left pane, select NM Security Log Dump.
11-7
M2000
2.
3.
Check the configuration of auto NM security log dump in the Attribute window.
4.
----End
11.4 Checking the Synchronization Time of NE Log

This section describes how to check whether the configuration of synchronization time of the
NE log is correct. The purpose is to avoid the server overload owing to the conflict of time when
you perform tasks on the server.
Prerequisite
l
You are authorized to check the configuration of the M2000 integrated task management.
Context
You need to run the operation only if the NE supporting this function exists.
Procedure
Step 2 Under the Synchronization node in the Task Type navigation tree in the left pane, select NE
Log Synchronization.
Step 3 Select the task in the right pane. Click Attribute.
Step 4 View the configuration of synchronization time of NE log in the Attribute dialog box.
Step 5 Ensure that the configuration is correct.
You are advised to synchronize NE logs when the traffic is not heavy. Generally, this operation
is performed at night when no other tasks are performed.
----End
11.5 Checking the Configuration of the File Server

This section describes how to check whether the configuration of the file server is appropriate.
Prerequisite
l
You are authorized to check the configuration of the M2000 file server.
Procedure
Step 1 Choose Software > File Server Setting.
11-8

Issue 03 (2010-12-31)
M2000
The File Server Setting window is displayed.

Step 2 Select the NE type in the ROOT navigation tree in the left pane.
Step 3 Check the name and IP address of the file server in the right pane.
Step 4 Ensure that the configuration of the file server is appropriate.
----End
11.6 Checking the Configuration of System Backup

This section describes how to check whether the periodic backup of the M2000 server and NEs
are started and whether the start time is correct. The purpose is to avoid the server overload
owing to the conflict of time when you perform tasks on the server. This section also describes
how to check whether backup files are generated in the disk.
Prerequisite
l
You are authorized to check the configuration of the M2000 integration task.
Procedure
Step 2 Check whether the periodic backup of the M2000 server is started and whether the start time is
correct.
1.
Under the Backup node in the Task Type navigation tree in the left pane, select the Server
Backup node.
2.
View Last Run Time and State in the right pane. Ensure that the task is running in the
execution time.
3.
Select the task in the right pane. Click Attribute.
4.
View the configuration of periodic backup time for the M2000 server in the Attribute
dialog box.
5.
Ensure that the configuration is correct.
Step 3 Check whether the periodic backup of the NE is started and whether the start time is appropriate.
1.
Under the Backup node in the Task Type navigation tree in the left pane, select the NE
Backup node.
2.
View Last Run Time and State in the right pane. Ensure that the task is running in the
execution time.
3.
Select the task in the right pane. Click Attribute.
4.
View the configuration of periodic backup time for NEs in the Attribute dialog box.
Ensure that the configuration is correct.
Step 4 Log in to the M2000 server as user omcuser through SSH mode. Check whether backup files
exist in the backup directory of both the M2000 server and NEs.
Issue 03 (2010-12-31)

11-9
M2000
You can specify the backup directory for the M2000 server and NEs based on the attribute
information.
----End
11.7 Checking the Configuration of System Monitoring

This section describes how to check the configuration of system monitoring.
Context
The recommended thresholds of the CPU usage, memory usage, and database usage are 80%.
Procedure
Step 1 Choose Monitor > System Monitor > Settings.
The System Monitor Settings dialog box is displayed.
Step 2 Click the Server Monitor tab to check whether the settings of the CPU usage and memory usage
thresholds are appropriate.
Step 3 Click the Hard Disk Monitor tab to check whether the settings of the disk usage thresholds are
appropriate.
Step 4 Click the Database Monitor tab to check whether the settings of the database usage thresholds
are appropriate.
Step 5 Click the Service Monitor tab to check whether the settings of the service status refresh interval
thresholds are appropriate.
----End
Example
For details about the parameters for monitoring the server, see Table 11-2.
11-10

Issue 03 (2010-12-31)
M2000
Table 11-2 Server Monitor

Name
Server Monitor
Parameter Settings
CPU sustained
overload times
(10-400 times)
Description
Settings
Description:
Value:
l The number of
consecutive
sampling times is
equal to CPU
sustained
overload times.
The sampling
interval is equal
to Server status
refresh interval.
If the CPU usage
sampled each
time is larger than
the generation
threshold, it
means that the
CPU is
consecutively
overloaded.
When the number
of overload times
reaches the
specified value, a
high CPU usage
alarm is
generated.
Value range: 10-400

Default value: 40
l If the CPU usage

sampled at a time
is smaller than the
clearance
threshold, the
high CPU usage
alarm is cleared.
Server status refresh
interval (2-60
seconds)
Issue 03 (2010-12-31)
Description:
Value:

server monitoring,
that is, the CPU
usage is sampled
every x seconds.
Value range: 2-60

Default value: 15
11-11
M2000
Name
Server Monitor
Threshold Settings
CPU usage (%)
Memory usage (%)
Description
Settings
Description:
Value:
Used to set
Threshold for
Alarm Generation,
Threshold for
Alarm Clearance
for the CPU usage
alarm and whether to
enable the bubble.
Value range: 1-99.

Default value: 90.
Used to set
Threshold for
Alarm Generation
and Threshold for
Alarm Clearance
for the memory
usage alarm.
Value:
Offset value range:

70.
Value range: 1-99.

Default value: 95.
Offset value range:
85.
l If the memory
usage is larger
than Threshold
for Alarm
Generation of
Memory used
rate, the M2000
generates a high
memory usage
alarm.
l If the memory
usage is smaller
than Threshold
for Alarm
Clearance of
Memory used
rate, the M2000
generates an
alarm, prompting
that the high
memory usage
alarm is cleared.
l When the
function of
bubble
information is
enabled, if the
server is faulty,
the system
displays a bubble
information.
11-12

Issue 03 (2010-12-31)
M2000
Table 11-3 describes the parameters for monitoring the disks of the server.
Table 11-3 Hard Disk Monitor
Name
Disk Monitor
Parameter Settings
Disk Monitor
Threshold Settings
Hard disk status

refresh interval
(60-3600 seconds)
Default value setting

(%)
Description
Settings
Description:
Value:

hard disk
monitoring.
Value range:
60-3600
Description:
Value:
All default
thresholds of hard
disk usage on the
M2000 server.
Value range: 1-99
l When the hard

disk usage is
larger than
Threshold for
Alarm
Generation of an
alarm severity
level, the M2000
generates a high
hard disk usage
alarm of this
severity level.
l Warning: 60
l When the hard

disk usage is
smaller than
Threshold for
Alarm
Clearance of an
alarm severity
level, the M2000
clears the high
hard disk usage
alarm of this
severity level.
Default value: 60
Default value of
Threshold for
Alarm Generation:
l Minor: 70
l Major: 80
l Critical: 90
Default value of
Threshold for
Alarm Clearance:
l Warning: 55
l Minor: 65
l Major: 75
l Critical: 85
l When the
function of
bubble
information is
enabled, if the
hard disk is
faulty, the system
displays a bubble
information.
Issue 03 (2010-12-31)

11-13
M2000
Name
Advanced Setting
(%)
Description
Settings
Description:
Value:
Thresholds of all the

hard disk usage on
the M2000 server.
l If you select
Default value,
the M2000 uses
the threshold
specified in
Default value
setting.
l When the hard

disk usage is
larger than
Threshold for
Alarm
Generation of an
alarm severity
level, the M2000
generates a high
hard disk usage
alarm of this
severity level.
l When the hard
disk usage is
smaller than
Threshold for
Alarm
Clearance of an
alarm severity
level, the M2000
clears the high
hard disk usage
alarm of this
severity level.
l If you select
Customize
value, the
M2000 uses
customized
thresholds of
alarms. Value
range: 1-99.
l If you select
Disable alarm
generation,
theM2000 doesn't
report alarms of
the disk partition.
l When the
function of
bubble
information is
enabled, if the
hard disk is
faulty, the system
displays a bubble
information.
Table 11-4 describes the parameters for monitoring the database of the server.
11-14

Issue 03 (2010-12-31)
M2000
Table 11-4 Database Monitor

Name
Database Monitor
Parameter Settings
Database status
refresh interval
(300-3600 seconds)
Description
Settings
Description:
Value:
Interval of database
refreshing.
Value range:
300-3600
Default value: 300
Database Monitor
Threshold Settings
Default Value
Setting (%)
Description:
Value:
All default
thresholds of
database usage on the
M2000 server.
Value range: 1-100
l When the
database usage is
larger than
Threshold of an
alarm severity
level, the M2000
generates a high
database usage
alarm of this
severity level.
l Minor: 90
Default value:
l Warning: 85
l Major: 95
l Critical: 98
l When the
database usage is
smaller than
Threshold of an
alarm severity
level, the M2000
clears the high
database usage
alarm of this
severity level.
Issue 03 (2010-12-31)

11-15
M2000
Name
Advanced Setting
(%)
Description
Settings
Description:
Setting method:
Thresholds for the

database usage
alarms of different
severities. You need
to set these
thresholds separately
for each database on
the M2000 server.
Set the following

parameters for each
database:
l When the
database usage is
larger than
Threshold of an
alarm severity
level, the M2000
generates a high
database usage
alarm of this
severity level.
l When the
database usage is
smaller than
Threshold of an
alarm severity
level, the M2000
clears the high
database usage
alarm of this
severity level.
l Default Value:
use default
thresholds for the
database usage
alarms of
different
severities.
l Customize
Value: customize
thresholds for the
database usage
alarms of
different
severities.
Value range:
1-100
Default value:
Warning: 85
Minor: 90
Major: 95
Critical: 98
l Disabled
Monitoring:
Disable the
database
monitoring.
Table 11-5 describes the parameters for monitoring the server services.
Table 11-5 Service Monitor
Name
Services Monitor
Parameter Settings
Service status refresh

interval (60-3600
seconds)
Description
Settings
Description:
Value:
Interval of service
refreshing.
Value range:
60-3600
Default value: 60
11-16

Issue 03 (2010-12-31)
M2000
Name
Service Monitor
Screen Tip Settings
Default Group
Description
Settings
Description:
Setting method:
Set whether to
display the service
status at the lower
right corner of the
M2000 system
Select a service from

the Service Name
drop-down list.
Select enable or
disable in the
corresponding Show
Screen Tips dropdown list.
monitor client by
or
NOTE
l If all the
monitored
services are
running,
displayed.
is
l if a monitored
service is stopped,
is displayed.
l You can doubleclick
or
to
access the Service
Monitor tab.
11.8 Checking the Synchronization Time of NE

Configuration
This section describes how to check whether the time for synchronizing NE configuration data
is appropriate. The purpose is to avoid the server overload. The server overload may occur when
the synchronization together with other tasks on the server is performed at the same time.
Prerequisite
l
You are authorized to check the configuration of the M2000 integrated task management.
Context
You need to run the operation only if the NE supporting this function exists.
Procedure
Step 2 Under the Synchronization node in the Task Type navigation tree in the left pane, select the
NE Configuration Data Synchronization node.
Issue 03 (2010-12-31)

11-17
M2000
Step 3 Select the task in the right pane. Click Attribute.

Step 4 View the setting of the time for synchronizing NE configuration data in the Attribute dialog
box.
Step 5 Ensure that the configuration is correct.
----End
11.9 Checking the Status of Performance Measurement

This section describes how to check the performance measurement state. You must ensure that
all the required measurement counters and measurement objects are in proper status.
Prerequisite
l
You are authorized to perform performance management.
Procedure
Step 1 Choose Performance > Measurement Management.
The Measurement Management window is displayed.
Step 2 Ensure that all the required measurement counters and the measurement objects on the
Measurement Status tab page are in proper status. If there is any exception, contact Huawei
----End
11.10 Checking the Missing Performance Result

To ensure that no result is lost, you must check that the missing performance result exists.
Prerequisite
l
You are authorized to perform performance management.
Procedure
Step 1 Choose Performance > Measurement Management.
Step 2 From the navigation tree of the Measurement Status tab page, right-click a node and then
choose Missing Result from the shortcut menu.
Step 3 In the displayed Query Missing Result dialog box, set the related parameters.
Default end time = Current time. Default start time = Current time - Time range of the missing
results in the preference settings.
Step 4 Click OK.
11-18

Issue 03 (2010-12-31)
M2000
Any measurement result that is missing within the time range is listed in a table in the displayed
dialog box. The first column of the table displays the object information. The second column
displays the corresponding time range.
----End
Follow-up Procedure
If missing measurement results exist, synchronize the results.
1.
Right-click a node in the navigation tree, and then choose Missing Result from the shortcut
menu.
2.
In the Query Missing Result window, select an NE and a function subset whose missing
results you want to query, and then click OK.
3.
In the dialog box of missing results, click Synchronize Result.
4.
In the Prompt dialog box, click OK.

After the synchronization command is issued to the NE, it takes some time for the NE to
report the performance measurement data. You can check whether the data is successfully
reported by viewing whether the missing results disappear.
11.11 Checking the Alarm Reception

Check the alarm reception and ensure that the M2000 can receive alarms from NEs in real time.
Prerequisite
l
You are authorized to perform fault management.
Procedure
Step 1 Choose Monitor > Browse Alarm List.
The Filter window is displayed.
Step 2 Set filter condition, then click OK.
Step 3 Ensure that the M2000 can receive the alarms reported by NEs in real time.
----End
11.12 Checking the NMS Connection

This section describes how to check the NMS connection and to ensure that the NMS connection
is normal.
Procedure
Step 1 Ensure that the NMS can collect the alarms and performance data reported from the M2000 .
----End
Issue 03 (2010-12-31)

11-19
M2000
11.13 Checking the Functionality of Alarm Box

Check the function of generating visual and audible alarms for the alarm box and ensure that
the alarm box can indicate the alarms on the M2000 in real time.
Prerequisite
l
You are authorized to perform fault management.
Procedure
Step 1 Choose Monitor > Alarm Setting > Options.
The Alarm Option window is displayed.
Step 2 View the settings. Ensure that alarms generated from the NEs, which satisfy the conditions, can
be indicated on the alarm box in real time.
----End
11.14 Checking the Owner of the M2000 File System

This section describes how to check the owner of the M2000 file system. You need to check the
owner of the M2000 file system regularly to ensure proper user operations because some tools
or operations may change the owner of the M2000 file system.
Prerequisite
Log in to the M2000 server as user root through SSH mode.
Procedure
Step 1 Run the following commands to check whether the owner of the M2000 file system is correct:
# . /opt/OMC/lbin/checkOSSRight.sh
If the system output contains the information like Error, run the . /tmp/modifyRight.sh
command to resume the owner of the M2000 file system.
Error: The rights of some OSS files are set incorrectly!
You can execute the /tmp/modifyRight.sh script to correct the settings.
If the system output contains the information like OK, you can infer that the owner of the
M2000 file system is correct.
OK: No rights of OSS files are assigned to user root.
----End
11-20

Issue 03 (2010-12-31)
M2000
11.15 Checking the Threshold of Network Management

Capability
This section describes how to check whether the M2000 management capability exceeds the
threshold. Ensure that the number of equivalent NEs managed by the M2000 does not exceed
the capability limit.
Procedure
Step 1 Check whether the M2000 management capability exceeds the threshold. Ensure that the number
of equivalent NEs managed by the M2000 is not beyond the capacity.
For details on how to calculate equivalent NEs and for the description of the M2000 management
capability, refer to the M2000 Product Description.
----End
11.16 Check OMC Alarms/Events

This section describes how to check whether the M2000 system is normal. This section also
describes how to check whether the alarms and events of the M2000 are generated.
Prerequisite
l
You are authorized to query alarms and events.
Procedure
Step 1 Check whether the OMC icon is colored or an alarm is displayed on it in the topology view.
If the system is operational, no alarm is generated. That is, the OMC icon is not colored or no
alarm balloon is displayed.
Step 2 Right-click the OMC icon, and then choose Query Alarm/Event > Alarm List.
The Browse Alarm List window is displayed.
l If the alarms listed in Table 11-6 are generated, handle the alarms immediately.
Table 11-6 Alarms that need to be handled immediately
Issue 03 (2010-12-31)
Alarm Name
Alarm ID
The OMC Service Is Terminated Abnormally
The Disk Usage Is Too High (Critical)
37
Power Failure
101
Fan Failure
102

11-21
M2000
Alarm Name
Alarm ID
CPU Temperature Is Abnormal
103
Hard Disk Failure
104
Disk Array Failure
105
Power or Fan Failure To the Disk Array Cabinet
106
Failure To the Devices in the Disk Array Cabinet
107
A Disk on the Array Is Faulty
108
Memory Failure
110
CPU Failure
112
The Cache for the Array Controller Is Faulty
202
Logical Drive Is Offline
203
Array Reconstruction Error
204
Physical Hard Disk Failed
205
Hard Disk Synchronization Error
206
The Temperature of the Disk Cabinet Is Abnormal
207
Fan Failure In The Disk Cabinet
208
Disk Cabinet Power Failed
209
Array Reconstruction
210
Reconstruct The Virtual Disk
212
Disk Cabinet Failure
214
Disk Physical State Is Changed
215
Host Power Failure
217
Host Power Cable Failure
218
Host Temperature Is Abnormal
219
Host Fan Is Abnormal
220
l If the alarms listed in Table 11-7 are generated, you need to clear them within one day.
Table 11-7 Alarms that need to be handled within one day
11-22
Alarm Name
Alarm ID
NE Mediation Layer Version Unmatched
303

Issue 03 (2010-12-31)
M2000
Alarm Name
Alarm ID
Insufficient Free Space of the Performance

Database
405
License Invalid
501
License Expired
505
License On Trail
506
Server Backup Unsuccessful
512
l During network expansion, multiple alarms listed in Table 11-8 are generated. In such a
case, you can export the alarm statistical files every day and check the information in the
Location Information column in the exported files. If the alarms are generated on the
required NEs, you need clear the alarms.
Table 11-8 Alarms to be focused on during network expansion
Alarm Name
Alarm ID
NE Is Disconnected
301
l If the alarms listed in Table 11-9 are generated many times, you need to locate the user who
has not obtained the M2000 login password and tries to log in to the M2000 to prevent
malicious operations.
Table 11-9 Alarms about malicious operations
Alarm Name
Alarm ID
The Number of Login Attempts Reaches the Maximum
11
Step 3 Right-click the OMC icon, and then choose Query Alarm/Event > Event Logs from the
shortcut menu.
The Query Event Logs window is displayed.
l If the events listed in Table 11-10 occur, you need to handle the events immediately.
Table 11-10 Events that need to be handled immediately
Event Name
Event ID
The Battery for the Array Controller Is Faulty
201
Array Disk Is Offline
213
Disk Logical State Is Changed
216
l If the events listed in Table 11-11 occur, you need to handle them within one day.
Issue 03 (2010-12-31)

11-23
M2000
Table 11-11 Events that need to be handled within one day

Event Name
Event ID
SMC Alarm
1099
l During network expansion, multiple events listed in Table 11-12 occur. In such a case, you
can export the event statistical files every day and check the information in the Location
Information column in the exported files. If the events occur on the required NEs, you need
to handle them.
Table 11-12 Events that need to be focused on during network expansion
Event Name
Event ID
Performance Result Loss
407
----End
Follow-up Procedure
To handle alarms and events, perform the following steps:
1.
In the Browse Alarm List or Query Event Logs window, select a specific alarm or event.
2.
In the Process Advice area, click Click here to show detail Information. Then, you can
obtain the detailed information and troubleshooting suggestions from the displayed alarm
or event online help.
3.
(Optional) When handling alarms, you also need to acknowledge uncleared alarms, and
analyze and acknowledge the alarms that are automatically cleared.
The cleared but not acknowledged alarms are displayed in a different color.
4.
Double-click an alarm or event. The Detail Information dialog box is displayed.
5.
In the Experience area, click Modify. The Experience dialog box is displayed.
6.
In the Modify Experience dialog box, type the information such as the symptom, cause,
and recommended handling advice.
The typed information is saved in the Experience area.
7.
Repeat 1 to 6 to handle each alarm or event.
8.
Ensure that the M2000 system is operational.

No alarms or events occur if the M2000 system is operational.
11.17 Checking Connections Between the M2000 and NEs

This section describes how to check the connections between the M2000 and NEs.
Prerequisite
Before checking connections between the M2000 and NEs, ensure that:
l
11-24

Issue 03 (2010-12-31)
M2000
You are authorized to query the status of NE connections.

NOTE
The connection status of virtual NEs and the OMC (M2000 ) is NA (not applicable).
Procedure
Step 1 Choose System > NE Monitor.
The NE Monitor dialog box is displayed.
You can check the connection status of NEs. There are three connection status: Connected,
Break, and NA.
Step 2 Handle exceptions.
For the Break status, you must obtain and analyze system information in time and solve the
problem.
The NA status is caused by an unmatched NE version. Check the NE version and then install
the adaptation layer. For details, refer to the M2000 Commissioning Guide.
Step 3 Check whether the NEs are connected correctly.
The status of all NEs is Connected.
----End
11.18 Checking the Status of the M2000 Routes

This section describes how to check the configuration of the M2000 routes.
Prerequisite
Procedure
Step 1 Check the configuration of the current route.
# netstat -rnv
----End
11.19 Checking M2000 Logs

M2000 user logs record the details about user operations, such as user name, start time, end time,
and log type. The M2000 system administrators and operators can query user logs.
Prerequisite
l
You are authorized to check M2000 logs.
Issue 03 (2010-12-31)

11-25
M2000
Procedure
Step 1 Choose System > Log Management > Query Operation Logs.
The Query Operation Logs window is displayed. By default, the system opens the Filter
window automatically.
Step 2 Set query conditions in the Filter window and click OK.
User logs can be queried based on users, operations, terminals, time ranges, results, or objects.
The queried results are displayed.
Step 3 Handle abnormal operations.
Handle the abnormal or unfriendly operations. For example, if a user fails to log in to the client
for several times, perform the validity check for the user.
Step 4 Confirm that no error information exists in M2000 logs.
The system works properly. No abnormal or unfriendly operations are performed.
----End
11.20 Checking SUSE Error Logs

This describes how to check the error logs of the SUSE operating system.
Prerequisite
Procedure
Step 1 Open the /var/log/messages file and check the file for errors.
# cd /var/log
# more messages
Generally, the file does not contain err or failed messages.
If you find out any error information, contact Huawei technical support engineers for assistance.
Step 3 Check whether the logs of the SUSE system contain any error information.
The system logs do not contain any error records.
----End
11.21 Checking the CPU Usage of the M2000 Server (SUSE)

This describes how to check whether the CPU usage is in the required range.
11-26

Issue 03 (2010-12-31)
M2000
Prerequisite
l
You are authorized to view the CPU usage.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser.
The System Monitor Browser window is displayed.
Step 2 Check CPU Usage on the Server Monitor tab page in the System Monitor Browser window.
Generally, the CPU usage is smaller than 80%.
If the CPU usage is greater than 80%, perform the following steps:
1.
Check whether a large number of NE alarms are generated within a short period of time.
Find out the causes of the alarms.
2.
Log in as user root to open the M2000 installation directory. The default installation
directory of the M2000 is /opt/OMC.
3.
Check the CPU usage of each process on the server:

# . ./svc_profile.sh
# top
Step 4 Check whether the CPU usage is in the required range.

Generally, the CPU usage is smaller than 80%.
----End
11.22 Checking the Disk Usage of the M2000 Server (SUSE)

This describes how to check the disk usage and clear the expired log files, temporary files, and
other files that are no longer in use. This operation requires very few system resources and does
not affect the system operation.
Prerequisite
Procedure
Step 1 Run the following command:
# df -h
Details about the disk space usage are displayed.
Step 2 View the disk usage.
l Generally, the disk usage is lower than 80%, which means the capacity is lower than 80%.
Issue 03 (2010-12-31)

11-27
M2000
l View the partition with the largest remaining space. The remaining space must be sufficient
to back up the M2000.
Clear the disk space if the disk space is insufficient. For details, see 9.1.2 Clearing the Disk
Space of an M2000 Client and 9.2.4 Clearing the Disk Space of the M2000 Server
(SUSE).
Step 4 Check whether the disk usage is in the required range.
Generally, the disk usage is lower than 80%, which means the capacity is lower than 80%.
----End
11.23 Checking M2000 Database Status (SUSE)

After installing the Oracle software and patches, you need to check the status of the database to
ensure that the server starts successfully.
Prerequisite
Procedure
Step 1 Run the following command to check whether the database server starts.
# ps -ef |grep ora |grep -v usb-storage |grep -v hald-addon-storage |grep -v grep
root
2013
27 0 Sep12 ?
root
3843 3208 0 Sep12 ?
oracle
5466 5450 0 Sep21 pts/0
oracle
5467 5466 0 Sep21 pts/0
oracle
5891
1 0 00:29 ?
oracle
5893
1 0 00:29 ?
oracle
5895
1 0 00:29 ?
oracle
5897
1 0 00:29 ?
oracle
5899
1 0 00:29 ?
oracle
5901
1 0 00:29 ?
oracle
5903
1 0 00:29 ?
oracle
5905
1 0 00:29 ?
oracle
5907
1 0 00:29 ?
oracle
5909
1 0 00:29 ?
oracle
5911
1 0 00:29 ?
oracle
5913
1 0 00:29 ?
oracle
5915
1 0 00:29 ?
oracle
5917
1 0 00:29 ?
oracle
5921
1 0 00:29 ?
oracle
5923
1 0 00:29 ?
oracle
5927
1 0 00:29 ?
oracle
5929
1 0 00:29 ?
oracle
5935
1 0 00:29 ?
oracle
5937
1 0 00:29 ?
oracle
5974
1 0 00:35 ?
home/bin/tnslsnr LISTENER -inherit
oracle
5979
1 0 00:36 ?
00:00:19
00:00:22
00:00:00
00:00:00
00:00:00
00:00:00
00:00:01
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
[usb-storage]
hald-addon-storage
su - oracle
-bash
ora_pmon_ossdb
ora_psp0_ossdb
ora_mman_ossdb
ora_dbw0_ossdb
ora_dbw1_ossdb
ora_dbw2_ossdb
ora_dbw3_ossdb
ora_lgwr_ossdb
ora_ckpt_ossdb
ora_smon_ossdb
ora_reco_ossdb
ora_cjq0_ossdb
ora_mmon_ossdb
ora_mmnl_ossdb
ora_arc0_ossdb
ora_arc1_ossdb
ora_qmnc_ossdb
ora_j000_ossdb
ora_q000_ossdb
ora_q001_ossdb
/opt/oracle/oradb/
00:00:01 oracleossdb (LOCAL=NO)
If the system output contains at least the following seven processes, you can infer that the
database service and the monitor are started. If no output is displayed or the following seven
processes were not all displayed, you can infer that the database service does not start normally.
Perform Step 2 to start the database.
11-28

Issue 03 (2010-12-31)
M2000
l ora_pmon_ossdb
l ora_dbw0_ossdb
l ora_lgwr_ossdb
l ora_ckpt_ossdb
l ora_smon_ossdb
l ora_arc0_ossdb
l /opt/oracle/oradb/home/bin/tnslsnr LISTENER -inherit
Step 2 If the database is not started, run the following commands to start the database server.
# su - oracle
~> sqlplus / as SYSDBA
SQL>startup
ORACLE instance started.
Total System Global Area 1610612736 bytes
Fixed Size
2046264 bytes
Variable Size
385877704 bytes
Database Buffers
1207959552 bytes
Redo Buffers
14729216 bytes
Database mounted.
Database opened.
Run the following command to log out the SQL.

SQL>exit
Run the following command to start the monitor:
~>lsnrctl start
LSNRCTL for Linux IA64: Version 10.2.0.3.0 - Production on 22-SEP-2008 00:35:31
Copyright (c) 1991, 2006, Oracle.
All rights reserved.
Starting /opt/oracle/oradb/home/bin/tnslsnr: please wait...

TNSLSNR for Linux IA64: Version 10.2.0.3.0 - Production
System parameter file is /opt/oracle/oradb/home/network/admin/listener.ora
Log messages written to /opt/oracle/oradb/home/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=osssvr.com)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
-----------------------Alias
LISTENER
Version
Start Date
22-SEP-2008 00:35:31
Uptime
0 days 0 hr. 0 min. 0 sec
Trace Level
off
Security
ON: Local OS Authentication
SNMP
OFF
Listener Parameter File
/opt/oracle/oradb/home/network/admin/listener.ora
Listener Log File
/opt/oracle/oradb/home/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=osssvr.com)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Issue 03 (2010-12-31)

11-29
M2000
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...

The command completed successfully
If the preceding message is displayed, you can infer that the monitor is started.
Perform Step 1 to check the start status of the database. If the database is not started, identify
the cause and reinstall the database.
----End
11.24 Checking the States of M2000 Services

This section describes how to check the states of M2000 services. This operation requires few
system resources and does not affect system operation.
Prerequisite
l
You have the relevant operation privileges.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser.
The System Monitor Browser window is displayed.
Step 2 Click the Service Monitor or Process Monitor tab to monitor the processes running on the
M2000 server.
Step 3 Handle exceptional situations.
In case a process is running improperly or a process is terminated exceptionally, log in to the
M2000 server as user omcuser. Run the command kill -9 pid to forcibly kill the process, where
pid indicates the process No.. The start_svc command is used to start all the M2000 services.
If some sessions are not started, run the command start_svc again. If a certain progress is still
inactive, contact Huawei technical support engineers for assistance.
Step 4 Check whether the M2000 works properly.
The Status of all M2000 services is Running.
----End
11.25 Checking the Core Files on the Server

This section describes how to check the /export/home/omc/var/logs directory and to ensure
that core files do not exist.
Prerequisite
Procedure
Step 1 Go to the /export/home/omc/var/logs directory.
11-30

Issue 03 (2010-12-31)
M2000
~> cd /export/home/omc/var/logs
Step 2 Check the /export/home/omc/var/logs directory and ensure that core files do not exist.
~> ls -ltr core*
The core files are sorted by time. The file at the top is the earliest one. Delete the core files
generated one week earlier. Contact Huawei technical support engineers to deal with the core
files generated within the week.
----End
11.26 Backing Up the M2000 System (SUSE)

This describes how to back up the M2000 system. The M2000 backup refers to the backup of
M2000 databases and system files. The M2000 system files refer to those files in the /export/
home/omc/var and /export/home/sysm directories.
Prerequisite
l
You are authorized to back up the M2000 system.
Procedure
Step 1 Choose Maintenance > Backup Management > System Backup in the main window.
Step 2 On the System Backup dialog box is displayed, click Full Backup.
----End
11.27 Querying the M2000 License

Procedure
Step 2 In the License Information dialog box, query the license information about resources and
functions on the Resource control item and Function control item tabs.
----End
11.28 Checking the Time of the M2000 Server (SUSE)

This describes how to check the time of the M2000 server.
Prerequisite
You have logged in to the M2000 as user omcuser.
Issue 03 (2010-12-31)

11-31
M2000
Procedure
Step 1 Check the time of the M2000 server.
omcuser@osssvr:~ date
The server time is displayed, for example:
Tue Mar 29 00:35:24 MEST 2005
Step 2 If the M2000 server is configured with the NTP service, run the ps -ef |grep ntp command to
check whether the NTP service is started. Verify that the NTP service is started and check the
service status by referring to2.5.5 Checking the Running Status of the NTP Service on the
l Change the server time if it is incorrect or it is not synchronized with the external clock source
through NTP. For details on how to set the server time, see Configuring the Time of the
l If the M2000 is configured with the NTP service and the NTP service is not running properly,
handle the problem according to 2.5 Setting the NTP Service for the M2000 (HP).
Step 4 Ensure that the server time is correct.
----End
11.29 Checking the Power Supply of the M2000 Server

This describes how to check the power supply of the M2000 server.
Prerequisite
The M2000 server is switched on.
Procedure
Step 1 Check power supply indicators of the server and the display.
All power indicators are green. All fault indicators are dim.
Step 2 To view the power failure information recorded in the recent logs of the SUSE operating system,
run the following commands:
# more /var/log/messages
# more /var/log/warn
The system logs do not contain any error records.
Step 3 Check the external power supply.
The external power supply is functional.
Step 4 Ensure that the power supply of the M2000 works normally.
11-32

Issue 03 (2010-12-31)
M2000
All power indicators must be green and all fault indicators must be dim.
----End
Issue 03 (2010-12-31)

11-33
M2000
12
12 Emergency Maintenance of the M2000 Client
Emergency Maintenance of the M2000

Client
This section provides guidance for emergency maintenance of the M2000 client.
If the M2000 client breaks down or a fault occurs in the client, you can restore the client in the
following ways:
l
Reinstall the operating system on the M2000 client.
Reinstall the M2000 system.
Issue 03 (2010-12-31)

12-1
M2000
13
Troubleshooting the M2000 (SUSE)
About This Chapter

This chapter describes the procedures for troubleshooting the M2000.
13.1 Procedure for Troubleshooting the M2000
This describes the procedure for troubleshooting the M2000. The procedure usually consists of
three phases: collecting data, locating faults, and handling faults.
13.2 Collecting M2000 Site and Software Information (SUSE)
This describes how to collect the M2000 site and software information.
Issue 03 (2010-12-31)

13-1
M2000
13.1 Procedure for Troubleshooting the M2000

This describes the procedure for troubleshooting the M2000. The procedure usually consists of
three phases: collecting data, locating faults, and handling faults.
Collecting Data
When a fault occurs, collect the following data:
l
Time and place the fault has occurred
Description of the fault
Measures taken and the results
Version information
IP addresses
Alarm information
Logs
Internal fault locating information
Database deadlock information

NOTE
Logs are categorized into user logs, system logs, and trace files.
Locating Faults
This describes the procedure for locating faults. The collection and analysis of faults help you
know the causes of the faults.
The M2000 system faults are categorized into hardware faults and software faults.
l
Hardware faults
Hardware faults are the faults that occur in the M2000 server, client, or other network
devices. The appearance of the hardware and indicators indicate the hardware faults clearly.
Software faults
Software faults are the faults that occur in the M2000 software, Linux, and Oracle.
Handling Faults
This describes how to handle faults based on different fault causes:
l
Hardware faults
Refer to the manuals delivered with the associated hardware.
Software faults
For details on alarms, refer to the Help of the M2000 Mobile Element Management System.
For details on faults of software installation, refer to the M2000 Software Installation
Guide of the relevant server type.
For details on the client faults, refer to the M2000 Online Help.
For details on the server faults, refer to FAQs About the M2000 Server Application in
FAQs.
13-2

Issue 03 (2010-12-31)
M2000
Linux faults
Refer to the Linux System Administrators Guide.
Oracle faults
Refer to the Oracle System Administrators Guide.
Uncleared faults
For the uncleared faults, collect all the information related to the faults by referring to
Collecting Data and contact Huawei technical support engineers for assistance.
13.2 Collecting M2000 Site and Software Information

(SUSE)
This describes how to collect the M2000 site and software information.
13.2.1 Collecting the M2000 Site Information
This section describes how to collect the M2000 site information.
13.2.2 Collecting the Time of M2000 Fault Occurrence
This section describes how to find out the time when M2000 faults occur.
13.2.3 Obtaining the IP Address of the M2000 Server (SUSE)
This describes how to obtain the IP address of the M2000 server.
13.2.4 Collecting SUSE Version Information (HP)
This describes how to obtain the version information about the SUSE.
13.2.5 Collecting Oracle Version Information (HP)
This describes how to obtain the version information about the Oracle.
13.2.6 Obtaining the Version Information About the M2000
This section describes how to obtain the version information about the M2000.
13.2.1 Collecting the M2000 Site Information

This section describes how to collect the M2000 site information.
Procedure
Step 1 Collect the M2000 site information.
Collect the following site information:
l Site name
l Customer contact details
l Hardware model
l Date and time when a fault occurs
l Fault description
----End
13.2.2 Collecting the Time of M2000 Fault Occurrence

This section describes how to find out the time when M2000 faults occur.
Issue 03 (2010-12-31)

13-3
M2000
Procedure
Step 1 Log in to the server as user omcuser through SSH mode.
NOTE
If you fail to log in as user omcuser, log in as user root.
Step 2 Run the date command to check the time.

----End
Example
-bash-3.00$ date
Thu Jul 28 09:56:39 EDT 2005
13.2.3 Obtaining the IP Address of the M2000 Server (SUSE)

This describes how to obtain the IP address of the M2000 server.
Procedure
l
Run the ifconfig command to obtain the IP address, subnet mask, and MAC address of the
M2000 server.
----End
Example
# ifconfig
13-4
bond0
Link encap:Ethernet HWaddr 00:1A:4B:07:A0:20

inet addr:10.71.15.57 Bcast:10.71.15.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:5103036 errors:0 dropped:0 overruns:0 frame:0
TX packets:686704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1222834170 (1166.1 Mb) TX bytes:60739078 (57.9 Mb)
bond0:1

bond0:2

eth0

inet6 addr: fe80::21a:4bff:fe07:a020/64 Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
Base address:0x1140 Memory:90160000-90180000
eth1

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Issue 03 (2010-12-31)
M2000

Base address:0x1100 Memory:90140000-90160000
eth2

UP BROADCAST RUNNING NOARP SLAVE MULTICAST MTU:1500 Metric:1
RX bytes:166390306 (158.6 Mb) TX bytes:416 (416.0 b)
Base address:0x1040 Memory:c0120000-c0140000
eth3
Link encap:Ethernet HWaddr 00:1A:4B:07:C2:91

inet6 addr: fe80::21a:4bff:fe07:c291/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Base address:0x1000 Memory:c0100000-c0120000
lo
Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
13.2.4 Collecting SUSE Version Information (HP)

This describes how to obtain the version information about the SUSE.
Prerequisite
Procedure
l
Run the cat /etc/SuSE-release command to collect the version information about the SUSE.
----End
Example
# cat /etc/SuSE-release
SUSE Linux Enterprise Server 10 (ia64)
VERSION = 10
PATCHLEVEL = 1
13.2.5 Collecting Oracle Version Information (HP)

This describes how to obtain the version information about the Oracle.
Prerequisite
You have logged in to the server as user oracle.
Issue 03 (2010-12-31)

13-5
M2000
Procedure
Step 1 Run the following command to view the database software and its patch:
oracle@osssvr:~>sqlplus / as SYSDBA
SQL> select * from v$version;
BANNER
---------------------------------------------------------------Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE
10.2.0.4.0
Production
TNS for Linux IA64: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
In the previous output, the version number is 10.2.0.4.0. If 10.2.0.4.0 is not displayed, refer
Installing the Oracle Database and Patches to install the Oracle again.
----End
13.2.6 Obtaining the Version Information About the M2000

This section describes how to obtain the version information about the M2000.
Procedure
Step 1 Log in to the server as user omcuser through SSH mode.
NOTE
Step 2 Run the displayVersion command to obtain the version information about the M2000.
----End
Example
Change to /opt/OMC, which is the default installation path of the M2000 server software. Run
the following commands:
~> cd /opt/OMC
~> displayVersion
------------------------OMC Version-------------------------Product Name:
iManagerM2000
Version:
iManagerM2000V200R009ENGC00SPC805
Release Date:
06/09/09
...
13-6

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
14
FAQs (HP)
About This Chapter

This chapter describes the FAQs and solutions related to the M2000.
14.1 FAQs About the SUSE Operating System (HP)
This describes the FAQs and solutions related to the SUSE operating system.
14.2 FAQs About the Oracle (HP)
This describes the FAQs and solutions related to the Oracle.
14.3 FAQs About the TCP/IP Network (SUSE)
This describes FAQs and solutions related to the TCP/IP network.
14.4 FAQs About the M2000 Server Application (SUSE)
This describes FAQs and solutions related to the M2000 server application.
Issue 03 (2010-12-31)

14-1
M2000
14 FAQs (HP)
14.1 FAQs About the SUSE Operating System (HP)

This describes the FAQs and solutions related to the SUSE operating system.
14.1.1 How to Grant User root with the telnet Authority (HP)
This describes how to grant user root with the telnet authority.
14.1.2 How to Grant User root with the FTP Authority (HP)
This describes how to grant user root with the FTP authority.
14.1.3 How to Check the Status of the Tape Drive (SUSE)
This describes how to check the status of the tape drive.
14.1.4 How to Select the Tape Drive (SUSE)
The types of servers that are not equipped with an internal tape drive are equipped with an
external tape drive. By default, the external tape drive of these server types is /dev/st0. The types
of servers without an external tape drive are equipped with an internal tape drive, By default,
the internal tape drive of these server types is also /dev/st0. If the servers with an internal tape
drive are equipped with an external tape drive, you need to determine on which tape drive should
the backup data be saved?
14.1.5 How to View the Hardware Configuration of the M2000 Server (SUSE)
This describes how to view the hardware configuration of the M2000 server.
14.1.6 How to Check the Device Status of the M2000 Server (SUSE)
This describes the common commands used to check the device status of the M2000 server.
14.1.7 How to Query a Time Zone Name (SUSE)
This describes how to query a time zone name. Before querying the DST rules of a time zone,
you must know the name of the time zone. Based on the time zone name, you can query the
corresponding DST rules.
14.1.8 How Should I Start the NTP Service on the M2000 Server (HP)
This describes how to start the NTP service on the M2000 server to ensure time synchronization.
14.1.9 How Should I Stop the NTP Service on the M2000 Server (HP)
This describes how to stop the NTP service on the M2000 server.
14.1.10 How Should I Check the Running Status of the FTP Service on the M2000 Server
This section describes how to check the running status of the FTP service on the M2000 server.
14.1.11 How Should I Start the FTP Service on the M2000 Server
This section describes how to start the FTP service on the M2000 server.
14.1.12 How Should I Check the Running Status of the SFTP Service on the M2000 Server?
This section describes how to check the running status of the SFTP on the M2000 server.
14.1.13 How Should I Start the SFTP Service on the M2000 Server?
This section describes how to start the SFTP service on the M2000 server.
14.1.1 How to Grant User root with the telnet Authority (HP)
This describes how to grant user root with the telnet authority.
14-2

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
Question
How should I grant user root with the telnet authority?
Answer
By default, the telnet authority of user root is closed. If you plan to use telnet as user root, perform
the following steps to grant the authority:
1.
Log in to the server as user root, and then open the yast window on the console.
2.
Click Network Services in the left-hand section of the window, and then click Network
Services(xinetd) in the right pane of the window. The Network Services Configuration
(xinetd) window is displayed.
3.
Select the telnet /usr/sbin/in.telnetd service and then click Toggle Status(On or Off). The
telnet service is started.
NOTE
l If the Status is on, you can infer that the service is enabled. If the Status is -, you can infer that
the service is installed. If the Status is NI, you can infer that the service is not installed.
l The telnet service in the /usr/lib/mit/sbin/telnetd directory needs only to be installed but not
started. Otherwise, errors occur during the system startup.
l During the startup of the FTP service, if the system prompts you to insert the SUSE CD, insert
the CD and click OK.
4.
Modify and save the /etc/pam.d/login file to grant user root with the telnet authority.
Add # in front of auth required pam_securetty.so to comment out the contents:
#auth
required
pam_securetty.so
14.1.2 How to Grant User root with the FTP Authority (HP)
This describes how to grant user root with the FTP authority.
Question
How should I grant user root with the FTP authority?
Answer
After the operating system is installed, the default setting is that the FTP service is available for
user root. If the FTP service is unavailable to users, log in as user root through the FTP and
perform the following steps:
1.
Log in to the server as user root, and then open the yast window on the console.
2.
Click Network Services in the left-hand section of the window, and then click Network
Services(xinetd) in the right pane of the window. The Network Services Configuration
(xinetd) window is displayed.
3.
Choose ftp /usr/sbin/vsftpd and then click Toggle Status(On or Off) to start the service.
NOTE
l If the Status is on, you can infer that the service is enabled. If the Status is -, you can infer that
the service is installed. If the Status is NI, you can infer that the service is not installed.
l During the startup of the FTP service, if the system prompts you to insert the SUSE CD, insert
the CD and click OK.
Issue 03 (2010-12-31)

14-3
M2000
14 FAQs (HP)
4.
Modify and save the /etc/ftpusers file to grant user root with the FTP authority.
Add # in front of the following contents to comment out the contents:
#root
14.1.3 How to Check the Status of the Tape Drive (SUSE)

This describes how to check the status of the tape drive.
Question
How do I check the status of the server tape drive?
Answer
1.
2.
Run the following command to check the status of the tape drive:
# mt -f /dev/nst0 status
Table 14-1 lists the tape drive status.
Table 14-1 Tape drive status
No.
System Output
Tape Drive Status
drive type = Generic SCSI-2 tape

drive status = 1191182336
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 0 bytes. Density code
0x47 (unknown).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
Indicates that the system

identifies the tape drive and
drive.
/dev/nst0: No medium found
Indicates that no tape is in the

tape drive or the tape is not
identified.
/dev/nst0: No such file or

directory
Indicates that the system cannot

identify the tape drive.
3.
If the system cannot identify the tape drive, check if the tape drive is correctly installed.
4.
If the previous problems are solved, perform 2 to view the status of the tape drive.
14.1.4 How to Select the Tape Drive (SUSE)

The types of servers that are not equipped with an internal tape drive are equipped with an
external tape drive. By default, the external tape drive of these server types is /dev/st0. The types
of servers without an external tape drive are equipped with an internal tape drive, By default,
the internal tape drive of these server types is also /dev/st0. If the servers with an internal tape
drive are equipped with an external tape drive, you need to determine on which tape drive should
the backup data be saved?
14-4

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
Question
If the system has multiple tape drives, which tape drive should be used for storing the backup
data?
Answer
1.
Check for the number of tape drives in the system.

# ls /dev/st
0
0b
0bn
0c
0cb
0cbn
0cn
0h
0hb
0hbn
0hn
0l
0lb
0lbn
0ln
0m
0mb
0mbn
0mn
0n
0u
0ub
0ubn
0un
l If the command output displays only the logical device files that are preceded by 0, you
can infer that only one tape drive is connected.
l If the command output also displays the logical device files that are preceded by 1, you
can infer that two tape drives are connected.
2.
Identify the type of a tape drive.

Based on the number of tape drives obtain from 1, determine the type of each tape drive.
# mt -f Name of the logical device config
Determine the type of the first tape drive.
# mt -f /dev/st0 config
"HP
C7438A", "HP DAT-72", "CFGHPDAT72";
CFGHPDAT72 = 2,0x34,0,0x18659,4,0x47,0x47,0x47,0x47,3,120,420,3600,36000,3600,
3600,17400;
As indicated by the command result, the type of the first tape drive is HP DAT-72G. This
type of tape drive supports the 36 GB or 72 GB tape. This tape drive matches the logical
device /dev/st0.
Determine the type of the second tape drive.
# mt -f /dev/st1 config
"CERTANCEULTRIUM 3", "Certance Ultrium 3", "CFGCERTANCEULTRIUM3";
CFGCERTANCEULTRIUM3 = 2,0x3B,0,0x18619,4,0x40,0x42,0x44,0x44,3,120,3600,2100,
3600,2100,2100,10800;
As indicated by the command result, the type of the second tape drive is Certance
Ultrium 3. This type of tape drive supports the 400 GB or 800 GB tape. This tape drive
matches the logical device /dev/st1.
3.
Check the status of the tape drive.

Insert a tape into the tape drive and check whether the tape drive is operational.
This part takes the logical device of the tape drive, that is, /dev/st0, for example.
# mt -f /dev/st0 status
If the command results are similar to the following information, you can infer that the
inserted tape is functioning well:
HP DAT-72 tape drive:
sense key(0x6)= Unit Attention
file no= 0
block no= 0
residual= 0
retries= 0
If a tape is not inserted or identified correctly, the system displays the following
information:
/dev/st0n: no tape loaded or drive offline
Issue 03 (2010-12-31)

14-5
M2000
14 FAQs (HP)
14.1.5 How to View the Hardware Configuration of the M2000

Server (SUSE)
This describes how to view the hardware configuration of the M2000 server.
Question
How should I view the hardware configuration of the server? How should I check the memory
size of the server?
Answer
To view the hardware configuration, perform the following steps on the server:
1.
2.
Run the commands listed in Table 14-2 to view related items.
Table 14-2 Checking the server configuration

No.
Command
Item
# uname -a
View the server type.
# yast
In yast, click hardware to

view the hardware
configuration.
14.1.6 How to Check the Device Status of the M2000 Server (SUSE)
This describes the common commands used to check the device status of the M2000 server.
Question
Which commands are often used to check the device status?
Answer
Table 14-3 lists the commands often used for checking the device status.
Table 14-3 Commands for checking the device status
14-6
No.
Item
Description
Method
Network
connecti
on and
configura
tion
Check
network
configuration
.
# ifconfig
Check route
information.
# netstat -r

Issue 03 (2010-12-31)
M2000
No.
Item
Description
Method
File
system
and disk
partitions
Check disk
partitions.
# df -k
Check
system error
logs.
# more /var/log/messages
Check for the

version and
patches of the
operating
system.
# uname -a
Check the
SCS port
information.
# cat /proc/scsi/scsi
Check the
tape status.
# mt -f /dev/st0 status
Rewind a
tape to the
beginning.
# mt -f /dev/nst0 rewind
Remove a
tape, that is,
wind a tape to
the initial
position and
then eject the
tape from a
tape drive.
# mt -f /dev/nst0 offline
Erase the
contents on a
tape.
# mt -f /dev/nst0 erase
Issue 03 (2010-12-31)
14 FAQs (HP)
Tape
drive
NOTE
The erase operation is slow and can damage the tape.
Therefore, the operation is not recommended. After the tape
is fully written, new data written to the tape can overwrite
the existing data. You can directly use a new tape without
erasing the tape.
Fast forward
a tape.
# mt -f /dev/nst0 fsf n
Check error
logs of a tape
drive.
# dmesg | grep "nst0"
List
directories.
# tar tvf /dev/nst0

14-7
M2000
14 FAQs (HP)
No.
Item
Description
Method
Write data.
# tar cvf /dev/nst0 filename

NOTE
This command can be used only when the tape is new.
Otherwise, the data to be written will overwrite the existing
data.
Continue to
write data.
# tar rvf /dev/nst0 filename
Retrieve data.
#tar xvf /dev/nst0 filename
14.1.7 How to Query a Time Zone Name (SUSE)

This describes how to query a time zone name. Before querying the DST rules of a time zone,
you must know the name of the time zone. Based on the time zone name, you can query the
corresponding DST rules.
Question
How to query the name of a time zone?
Answer
To query the name of a time zone, perform the following steps:
1.
2.
Obtain the information on the country code of the time zone.

# more /usr/share/zoneinfo/iso3166.tab
A part of the content to be obtained from the file is as follows:
...
BR
CL
CN
...
Brazil
Chile
China
Based on the previous information, you can confirm that the country codes of Brazil, Chile,
and China are BR, CL, and CN respectively.
3.
Based on country codes, obtain the information on time zone names.

# more /usr/share/zoneinfo/zone.tab
l The format of the zone_sun.tab file is country code + longitude and latitude + time
zone name + comments.
l The north latitude and the east longitude are considered to be positive. The south latitude
and the west longitude are considered to be negative.
A part of the content to be obtained from the file is as follows:
...
#country#code
coordinates
TZ
comments
BR
-0351-03225
America/Noronha
Brazil/DeNoronha
Atlantic islands
BR
-0127-04829
America/Belem
Amapa, E Para
BR
-0343-03830
America/Fortaleza
NE Brazil (MA, PI, CE, RN, PB)
14-8

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
BR
-0803-03454
America/Recife
Pernambuco
BR
-0712-04812
America/Araguaina
Tocantins
BR
-0940-03543
America/Maceio
Alagoas, Sergipe
BR
-1259-03831
America/Bahia
Bahia
BR
-2332-04637
America/Sao_Paulo
Brazil/East
S & SE Brazil
(GO, DF, MG, ES, RJ, SP, PR, SC, RS)
BR
-2027-05437
America/Campo_Grande
Mato Grosso do Sul
BR
-1535-05605
America/Cuiaba
Mato Grosso
BR
-0846-06354
America/Porto_Velho
W Para, Rondonia
BR
+0249-06040
America/Boa_Vista
Roraima
BR
-0308-06001
America/Manaus
Brazil/West
E Amazonas
BR
-0640-06952
America/Eirunepe
W Amazonas
BR
-0958-06748
America/Rio_Branco
Brazil/Acre
Acre
CL
-3327-07040
America/Santiago
Chile/Continental
most locations
CL
-2709-10926
Pacific/Easter
Chile/EasterIsland
Easter Island & Sala y Gomez
CN
+3114+12128
Asia/Shanghai
PRC
...
The time zone names of Brazil, Chile, and China are listed in Table 14-4.
Table 14-4 Example of the matching table between countries and time zone names
Coun
try
Brazil
Issue 03 (2010-12-31)
Time Zone
Name
Remarks
America/
Noronha
Brazil/
DeNoronha
Atlantic islands
America/Belem
Amapa, E Para
America/
Fortaleza
NE Brazil (MA, PI, CE, RN, PB)
America/Recife
Pernambuco
America/
Araguaina
Tocantins
America/Maceio
Alagoas, Sergipe
America/Bahia
Bahia
America/
Sao_Paulo
Brazil/East
S & SE Brazil (GO, DF, MG, ES, RJ,

SP, PR, SC, RS)
America/
Campo_Grande
Mato Grosso do Sul
America/Cuiaba
Mato Grosso
America/
Porto_Velho
W Para, Rondonia
America/
Boa_Vista
Roraima
America/Manaus
Brazil/West
E Amazonas
America/
Eirunepe
W Amazonas

14-9
M2000
14 FAQs (HP)
Coun
try
Chile
China
Time Zone
Name
Remarks
America/
Rio_Branco
Brazil/Acre
Acre
America/
Santiago
Chile/
Continental
Most locations
Pacific/Easter
Chile/
EasterIsland
Easter Island & Sala y Gomez
PRC
NOTE
The time zone names of Europe are special. All the European countries are geographically located
in the east Europe, middle Europe, and west Europe. The corresponding time zone names of the east
Europe, middle Europe, and west Europe are EET, MET, and WET respectively.
14.1.8 How Should I Start the NTP Service on the M2000 Server (HP)
This describes how to start the NTP service on the M2000 server to ensure time synchronization.
Question
What should I do to start the NTP service on the M2000 server?
Answer
Perform the following operations to start the NTP service on the server:
1.
2.
Run the following command to check whether the NTP service is running:
# ps -ef | grep ntp | grep -v grep
ntp
32038
1 0 21:34 ?
If the command result contains ntpd, stop the NTP service and then perform 3 through 8
to start it again. For details about how to stop the NTP service, see 14.1.9 How Should I
Stop the NTP Service on the M2000 Server (HP).
If no output exists, you can infer that NTP service on the M2000 server is not running.
Then, you can perform 3 through 8 to start the NTP service.
3.
Check whether the M2000 services are started by referring to 7.2.2 Viewing the Running
Status of M2000 Services (SUSE). If the M2000 services are running, stop them.
(SUSE).
4.
Check whether the Oracle services are started by referring to 14.2.1 How to Check
Whether the Oracle Is Started (HP). If the Oracle services are running, stop them.
For details about how to stop the Oracle services, see 14.2.3 How to Stop the Oracle
(HP).
14-10

Issue 03 (2010-12-31)
M2000
5.
14 FAQs (HP)
Run the following command to start the NTP service.

# service ntp start
6.
Run the following command to check whether the NTP service cloud automatically starts
after system restarts.
# chkconfig ntp
ntp
on
If the value of a ntp is on, you can infer that the NTP service cloud automatically starts
after system restarts. Otherwise, run chkconfig ntp on.
7.
Restart the Oracle services.

For details about how to start the Oracle services, see 14.2.2 How to Start the Oracle
(HP).
8.
Restart the M2000 services.

For details about how to restart the M2000 services, see 7.2.3 Starting the M2000 Server
(SUSE).
14.1.9 How Should I Stop the NTP Service on the M2000 Server (HP)
This describes how to stop the NTP service on the M2000 server.
Question
What should I do to stop the NTP service on the M2000 server?
Answer
Perform the following operations to stop the NTP service on the server:
1.
2.
Run the following command to check whether the NTP service is running:
ntp
32038
1 0 21:34 ?
If ntpd is contained in the system output, you can infer that the NTP service is running on
the M2000 server. Therefore, perform 3 to stop the NTP service.
If no output exists, you can infer that the NTP service on the M2000 server is stopped and
thus you need not perform any operation to stop the NTP service.
3.
If the NTP service is running, run the following command to stop it:
# service ntp stop
NOTE
The NTP service is started automatically whenever the system is restarted.
4.
Run the following command to check whether the NTP service is stopped:
If any output exists, you can infer that the NTP service is not stopped. Therefore, repeat
3.
If no output exists, you can infer that NTP service on the M2000 server is stopped.
Issue 03 (2010-12-31)

14-11
M2000
14 FAQs (HP)
NOTE
Stopping the NTP service takes about 1 minute.
14.1.10 How Should I Check the Running Status of the FTP Service
on the M2000 Server
This section describes how to check the running status of the FTP service on the M2000 server.
Prerequisites
Context
l
You can use the traditional plain text mode or FTPS as the FTP transfer policy.
As an FTP application based on the SSL protocol, the FTPS protocol encrypts data during
FTP login connection and data transmission.
The FTP client is adaptive, and can determine whether to use the encryption mode or the
non-encryption mode of the SSL protocol according to the encryption policy used by the
FTP server.
FTPS can be used between the M2000 and NEs. When FTPS is used, firewall ports 0 to
500 must be open.
1.
Run the following command to check the running status of the FTP service:
Procedure
# ps -ef | grep ftpd | grep -v grep
If the following information is displayed, it indicates that the FTP service on the M2000
server is started. If there is no system output, start the FTP service by referring to 14.1.11
How Should I Start the FTP Service on the M2000 Server.
root 26510 22906
0 19:53:39 pts/1
0:00 /usr/sbin/ftpd
In the system output, the value in the second line refers to the process ID of the FTP service
on the M2000 server.
14.1.11 How Should I Start the FTP Service on the M2000 Server
This section describes how to start the FTP service on the M2000 server.
Prerequisites
Context
14-12
You can use the traditional plain text mode or FTPS as the FTP transfer policy.
As an FTP application based on the SSL protocol, the FTPS protocol encrypts data during
FTP login connection and data transmission.
The FTP client is adaptive, and can determine whether to use the encryption mode or the
non-encryption mode of the SSL protocol according to the encryption policy used by the
FTP server.
Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
FTPS can be used between the M2000 and NEs. When FTPS is used, firewall ports 0 to
500 must be open.
1.
Run the following command to start the FTP service:
Procedure
# /usr/sbin/ftpd &
The system displays the process ID of the FTP service.
2.
Run the following command to check the running status of the FTP service:
# ps -ef | grep ftpd | grep -v grep
root 26510 22906
0 19:53:39 pts/1
0:00 /usr/sbin/ftpd
In the system output, the value in the second line is the process ID of the FTP service on
the M2000 server. This value must be the same as the process ID displayed in step 1.
14.1.12 How Should I Check the Running Status of the SFTP Service
on the M2000 Server?
This section describes how to check the running status of the SFTP on the M2000 server.
Prerequisites
Context
l
SSH FTP (SFTP), is an FTP transfer mode based on the SSH protocol. SFTP uses a mature
public key mechanism or private key mechanism to encrypt the data in the network. This
ensures that the data communication between two ends can be performed in an encrypted
channel.
SFTP is supported between the M2000 server and the M2000 client, and also between the
M2000 and an NMS.
1.
Run the following command to check the running status of the SFTP service:
Procedure
# rcsshd status
Checking for service sshd
running
If running is displayed in the system output, it indicates that the SFTP service on the
M2000 server is started. If unused is displayed in the system output, it indicates that the
SFTP service on the M2000 server is not started. For details about how to start the SFTP
service, see 14.1.13 How Should I Start the SFTP Service on the M2000 Server?.
14.1.13 How Should I Start the SFTP Service on the M2000 Server?
This section describes how to start the SFTP service on the M2000 server.
Issue 03 (2010-12-31)

14-13
M2000
14 FAQs (HP)
Prerequisites
Context
l
SFTP is an FTP transfer mode based on the SSH protocol. SFTP uses a mature public key
mechanism or private key mechanism to encrypt the data in the network. This ensures that
the data communication between two ends can be performed in an encrypted channel.
SFTP is supported between the M2000 server and the M2000 client, and also between the
M2000 and an NMS.
1.
Run the following command to start the SFTP service on the M2000 server:
Procedure
# rcsshd start
2.
Run the following command to check the running status of the SFTP service:
# rcsshd status
running is displayed in the system output. That is, the SFTP service on the M2000 server
is started.
14.2 FAQs About the Oracle (HP)

This describes the FAQs and solutions related to the Oracle.
14.2.1 How to Check Whether the Oracle Is Started (HP)
This describes how to check whether the Oracle is started.
14.2.2 How to Start the Oracle (HP)
This describes how to start the Oracle service.
14.2.3 How to Stop the Oracle (HP)
This describes how to stop the Oracle service.
14.2.1 How to Check Whether the Oracle Is Started (HP)

This describes how to check whether the Oracle is started.
Question
How to check the startup status of the Oracle?
Answer
To check whether the Oracle is started, perform the following steps:
1.
Log in to the Linux system as user root.
2.
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
root
root
oracle
14-14
2013
3843
5466
27
3208
5450
0 Sep12 ?
0 Sep12 ?
0 Sep21 pts/0
00:00:19 [usb-storage]
00:00:22 hald-addon-storage
00:00:00 su - oracle

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
oracle
5467 5466 0 Sep21 pts/0
oracle
5891
1 0 00:29 ?
oracle
5893
1 0 00:29 ?
oracle
5895
1 0 00:29 ?
oracle
5897
1 0 00:29 ?
oracle
5899
1 0 00:29 ?
oracle
5901
1 0 00:29 ?
oracle
5903
1 0 00:29 ?
oracle
5905
1 0 00:29 ?
oracle
5907
1 0 00:29 ?
oracle
5909
1 0 00:29 ?
oracle
5911
1 0 00:29 ?
oracle
5913
1 0 00:29 ?
oracle
5915
1 0 00:29 ?
oracle
5917
1 0 00:29 ?
oracle
5921
1 0 00:29 ?
oracle
5923
1 0 00:29 ?
oracle
5927
1 0 00:29 ?
oracle
5929
1 0 00:29 ?
oracle
5935
1 0 00:29 ?
oracle
5937
1 0 00:29 ?
oracle
5974
1 0 00:35 ?
home/bin/tnslsnr LISTENER -inherit
oracle
5979
1 0 00:36 ?
00:00:00
00:00:00
00:00:00
00:00:01
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
-bash
ora_pmon_ossdb
ora_psp0_ossdb
ora_mman_ossdb
ora_dbw0_ossdb
ora_dbw1_ossdb
ora_dbw2_ossdb
ora_dbw3_ossdb
ora_lgwr_ossdb
ora_ckpt_ossdb
ora_smon_ossdb
ora_reco_ossdb
ora_cjq0_ossdb
ora_mmon_ossdb
ora_mmnl_ossdb
ora_arc0_ossdb
ora_arc1_ossdb
ora_qmnc_ossdb
ora_j000_ossdb
ora_q000_ossdb
ora_q001_ossdb
/opt/oracle/oradb/
00:00:01 oracleossdb (LOCAL=NO)
If the system output contains at least the following seven processes, you can infer that the
database service and the monitor are started. If no output is displayed or the following seven
processes were not all displayed, you can infer that the database service does not start
normally. For details about how to start the database, see 14.2.2 How to Start the Oracle
(HP).
l ora_pmon_ossdb
l ora_dbw0_ossdb
l ora_lgwr_ossdb
l ora_ckpt_ossdb
l ora_smon_ossdb
l ora_arc0_ossdb
l /opt/oracle/oradb/home/bin/tnslsnr LISTENER -inherit
14.2.2 How to Start the Oracle (HP)

This describes how to start the Oracle service.
Question
How to start the Oracle service?
Answer
To start the Oracle service, perform the following steps:
1.
Log in to Linux as user oracle to check whether the Oracle service is started.
2.
Check whether the Oracle is started by referring to 14.2.1 How to Check Whether the
Oracle Is Started (HP).
3.
Run the following command to start the Oracle server:

SQL> startup
Issue 03 (2010-12-31)

14-15
M2000
14 FAQs (HP)
ORACLE instance started.

Total System Global Area 1610612736 bytes
Fixed Size
2046264 bytes
Variable Size
385877704 bytes
Database Buffers
1207959552 bytes
Redo Buffers
14729216 bytes
Database mounted.
Database opened.
If the previous message is displayed, you can infer that the database is started.
4.
Run the following command to exit the SQL:

SQL> exit
5.
Run the following command to start the listener:

~>lsnrctl start
LSNRCTL for Linux IA64: Version 10.2.0.3.0 - Production on 22-SEP-2008
00:35:31
Copyright (c) 1991, 2006, Oracle.
All rights reserved.
Starting /opt/oracle/oradb/home/bin/tnslsnr: please wait...

System parameter file is /opt/oracle/oradb/home/network/admin/listener.ora
Log messages written to /opt/oracle/oradb/home/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=osssvr.com)
(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
-----------------------Alias
LISTENER
Version
TNSLSNR for Linux IA64: Version 10.2.0.3.0 Production
Start Date
22-SEP-2008 00:35:31
Uptime
0 days 0 hr. 0 min. 0 sec
Trace Level
off
Security
ON: Local OS Authentication
SNMP
OFF
Listener Parameter File
/opt/oracle/oradb/home/network/admin/listener.ora
Listener Log File
/opt/oracle/oradb/home/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=osssvr.com)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
If the previous message is displayed, you can infer that the listener is started.
14.2.3 How to Stop the Oracle (HP)

This describes how to stop the Oracle service.
Question
How to stop Oracle service?
Answer
To stop the Oracle service, perform the following steps:
14-16

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
NOTE
Before stopping the Oracle, ensure that the M2000 services are stopped. For details about how to stop the
M2000 services, see 7.2.4 Stopping the M2000 Services (SUSE).
1.
Log in to the server as user oracle.
2.
Stop the monitor.

(1) Check the running status of the monitor.
~> lsnrctl status
When the following message is displayed, you can infer that the monitor is running:
Instance "ossdb", status READY, has 1 handler(s) for this service...
(2) Run the following command to stop the monitor:

~> lsnrctl stop
3.
Run the following command to stop the Oracle database server:

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
If the preceding message is displayed, you can infer that the database is stopped.
NOTE
l Run the ps -ef |grep ora_ |grep -v grep command to check whether the Oracle database is stopped. If
no command result is displayed, run the kill -9 PID of oracle command to forcibly stop the Oracle
process.
l After you stop the Oracle, run the exit to roll back to user root.
l If the M2000 server is installed, the Oracle starts automatically upon a restart of the operating system.
14.3 FAQs About the TCP/IP Network (SUSE)

This describes FAQs and solutions related to the TCP/IP network.
14.3.1 How Do I Change the IP Address of the S3200 Disk Array (Command Mode)?
This section describes how to change the IP address of the S3200 disk array in command mode.
The disk array is connected to the server directly through optical fibers. Changing IP addresses
does not affect data read operations on the disk array. Therefore, you are advised to use the
14.3.2 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)
14.3.3 How to Connect the Client to the Server with Multiple IP Addresses (SUSE)
This describes how to set up the connection between the client and the server using multiple IP
addresses.
14.3.4 How Should I Log In to the Server in SSH Mode?
Issue 03 (2010-12-31)

14-17
M2000
14 FAQs (HP)
This section describes how to log in to the server in SSH mode. After the Linux operating system
is installed, you need to log in to the server in SSH mode with respect to system security. You
can use the PuTTY tool.
14.3.5 How Should I Log In to the Server in MP Mode?
This describes how to log in to the server in MP mode.
14.3.6 How Do I Configure the Monitoring Function of the S2600 Disk Array?
This section describes how to configure the monitoring function of the S2600 disk array.
14.3.7 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays
This section describes how to configure the monitoring function for the S3000 series disk arrays,
such as S3100 and S3200.
14.3.1 How Do I Change the IP Address of the S3200 Disk Array

(Command Mode)?
The disk array is connected to the server directly through optical fibers. Changing IP addresses
does not affect data read operations on the disk array. Therefore, you are advised to use the
Prerequisites
l
The server communicates properly with the S3200 disk array.
Before changing IP addresses, you must familiarize yourself with the default IP address
planning at delivery. Determine whether to reconfigure IP addresses based on the actual
situation.
Background
Procedure
This section takes the following change as an example to describe how to change the IP address
of the disk array.
l
Before the change:

IP address of controller A: 192.168.9.39
IP address of controller B: 192.168.9.40
After the change:

IP address of controller A: 10.10.10.39
IP address of controller B: 10.10.10.40
1.
Set the temporary subnet of the server to enable the server to access the controllers.
# ifconfig eth0:1 192.168.9.100 up
2.
Check whether the temporary subnet is configured properly.

# ping 192.168.9.40
14-18

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
If the system displays the following information, it indicates that the temporary subnet is
configured properly:
PING 192.168.9.40 (192.168.9.40) 56(84) bytes of data.
64 bytes from 192.168.9.40: icmp_seq=1 ttl=64 time=0.326 ms
3.
Change the IP address of controller B.

# SMcli IP address of controller A -c "set controller [b] ethernetPort [1] ipAddress= New
IP address of controller B gatewayIPAddress=New gateway of controller B
subnetMask=New subnet mask of controller B;"
In this case, IP address of controller A is 192.168.9.39, New IP address of controller B is
10.10.10.40, New gateway for controller B is 0.0.0.0, and New subnet mask of Controller
B is 255.255.255.0. Run the following command:
# SMcli 192.168.9.39 -c "set controller [b] ethernetPort [1] ipAddress= 10.10.10.40
gatewayIPAddress=0.0.0.0 subnetMask=255.255.255.0;"
After the command is successfully executed, the IP address of controller B is 10.10.10.40.
4.
Set the temporary subnet of the server again to enable the server to access the controllers.
# ifconfig eth0:2 10.10.10.100 up
5.
Check whether the new IP address of controller B is set successfully.

# ping New IP address of controller B
In this case, run the following command:
# ping 10.10.10.40
6.
Change the IP address of controller A.

# SMcli IP address of controller B -c "set controller [a] ethernetPort [1] ipAddress= New
IP address of controller A gatewayIPAddress=New gateway of controller A
subnetMask=New subnet mask of controller A;"
In this case, IP address of controller B is 10.10.10.40, New IP address of controller A is
10.10.10.39, New gateway for controller A is 0.0.0.0, and New subnet mask of Controller
B is 255.255.255.0. Run the following command:
# SMcli 10.10.10.40 -c "set controller [a] ethernetPort [1] ipAddress= 10.10.10.39
gatewayIPAddress=0.0.0.0 subnetMask=255.255.255.0;"
After the command is successfully executed, the IP address of controller A is 10.10.10.39.
7.
Check whether the new IP address of controller A is set successfully.

# ping New IP address of controller A
In this case, run the following command:
# ping 10.10.10.39
8.
Run the following commands to search for the disk array:

# SMcli -A
# SMcli -d -i
Issue 03 (2010-12-31)

14-19
M2000
14 FAQs (HP)
S3200-1
10.10.10.39
10.10.10.40
SMcli completed successfully.
In the system output, if the IP address of the disk array is consistent with the actual IP
address, it indicates that the IP address of the disk array is successfully changed. Otherwise,
change the IP address again.
14.3.2 How Do I Change the IP Address of the S2600 Disk Array

(Command Mode)
Prerequisites
l
Log in to the server as user root through SSH mode.
The communication between the server and the two management Ethernet ports on the
S2600 disk array is normal.
Each S2600 disk array has an active controller and a standby controller. Each controller
has one management Ethernet port.
Before changing the IP address of the disk array, you must familiarize yourself with the
default IP address planning at delivery. Then, determine whether to reset the IP address
according to the actual requirement.
If you change the IP address of the disk array on different network segments, continue to
change the IP address of the maintenance Ethernet port on the corresponding server to
ensure that the two changed IP addresses are on the same network segment.
1.
Run the following command to log in to controller A of the S2600 disk array in ssh mode:
Contexts
Procedure
# ssh admin@IP address of controller A
CAUTION
The initial user name and password of the administrator are admin and 123456,
respectively. To ensure the system security, you need to change the password after the
initial login.
2.
Run the following command to change the IP address of controller B:

OceanStor: admin> chgctrlip -c b -a new IP address of controller B -s subnet mask
-g gateway
For example, to change the IP address of the management Ethernet port on controller B to
14-20

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
OceanStor: admin> chgctrlip -c b -a 10.71.15.21 -s 255.255.255.0 -g 10.71.15.1

When the system displays the following prompt, type y.
This operation will change your controller's IP configuration. if you want to
ch
ange the IP of the controller you logged in, you will log out after you set
the
new IP. However, if you change the IP of the peer controller, you needn't log
out.
3.
Run the following command to check whether the changed IP address is correct:
OceanStor: admin> showctrlip
Controller
IP Address
A 192.168.8.39
00:18:82:e2:01:57
B 10.71.15.21
00:18:82:e2:00:fb
4.
Subnet Mask
255.255.255.0
Gateway
192.168.8.1
255.255.255.0
10.71.15.1
MAC Address
Run the following command to exit from controller A:

OceanStor: admin> exit
5.
Run the following command to log in to controller B of the S2600 disk array in ssh mode:
# ssh admin@new IP address of controller B
CAUTION
The initial user name and password of the administrator are admin and 123456,
respectively. To ensure the system security, you need to change the password after the
initial login.
6.
Run the following command to change the IP address of controller A:

OceanStor: admin> chgctrlip -c a -a IP address of controller A -s subnet mask -g
gateway
For example, to change the IP address of the management Ethernet port on controller A to
OceanStor: admin> chgctrlip -c a -a 10.71.15.20 -s 255.255.255.0 -g 10.71.15.1
When the system displays the following prompt, type y.
This operation will change your controller's IP configuration. if you want to
ch
ange the IP of the controller you logged in, you will log out after you set
the
new IP. However, if you change the IP of the peer controller, you needn't log
out.
7.
Run the following command to check whether the changed IP address is correct:
OceanStor: admin> showctrlip
Controller
IP Address
A 10.71.15.20
00:18:82:e2:01:57
B 10.71.15.21
00:18:82:e2:00:fb
8.
Subnet Mask
255.255.255.0
Gateway
10.71.15.1
255.255.255.0
10.71.15.1
MAC Address
Run the following command to exit from controller B:

Issue 03 (2010-12-31)

14-21
M2000
14 FAQs (HP)
9.
Modify the /etc/hosts file and the /etc/inet/ipnodes file. If there are multiple servers,
perform the following operations on each server:
NOTE
To change the disk array IP address recorded in the /etc/hosts file and the /etc/inet/ipnodes file, you
need not stop the M2000 services and the database services. After the modification, you need not
restart the server either.
(1) Log in to the server as user root.

(2) Perform the following operations on the server to modify the /etc/hosts file and to
replace the existing IP address of the disk array with a new one:
# vi /etc/hosts
After the modification, press Esc, and then run the :wq! command to save the
modification and exit.
(3) Perform the following operations on the server to modify the /etc/inet/ipnodes file:
# vi /etc/inet/ipnodes
l If the file records the existing IP address of the disk array, replace the existing IP
address with the new one. After the modification, press Esc, and then run
the :wq command to save the modification and exit.
l If the file records the new IP address of the disk array, you need not perform any
modification. Press Esc, and then run the :q command to exit.
10. If the monitoring function of the S2600 disk array is configured, you need to reconfigure
this function after changing the IP address of the server. For details, see Configuring the
Monitoring Function of the S2600 Disk Array.
14.3.3 How to Connect the Client to the Server with Multiple IP

Addresses (SUSE)
This describes how to set up the connection between the client and the server using multiple IP
addresses.
Question
Why cannot the connection between the client and the server be set up?
Answer
Normally, the M2000 server is configured with only one IP address. If the server has multiple
IP addresses, specify one for the M2000 services. Otherwise, the client cannot set up a connection
with the server.
Stop the M2000 services and the Oracle service before you change the IP address of the
M2000 server. No performance data or alarm data is processed during the process of changing
the server IP address. After the M2000 services are resumed, the M2000 collects the performance
data and alarm data through automatic synchronization and processes the data.
To specify an IP address for the M2000 services, perform the following steps on the server:
1.
14-22
Log in to the M2000 server as user root.

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
2.
To check whether the M2000 is running, see 7.2.2 Viewing the Running Status of M2000
Services (SUSE). If the M2000 is running, stop the M2000 services. To stop the M2000
services, see 7.2.4 Stopping the M2000 Services (SUSE).
3.
To check whether the Oracle service is running, see 14.2.1 How to Check Whether the
Oracle Is Started (HP). If the Oracle is running, stop the Oracle service. To stop the Oracle
service, see 14.2.3 How to Stop the Oracle (HP).
4.
Switch back to user root.

# su - root
5.
Edit the /etc/hosts file to ensure that the host name corresponds to one IP address for
connecting clients and NEs.
For example: If the IP addresses of the server are 10.161.10.101 and 10.121.10.102, the IP
address for connecting the clients is 10.161.10.101. In the M2000 server installation
directory/etc/conf/tao.cfg file, the ListenIpAddrs field indicates that the IP address is
10.161.10.101 and the host name is aries. In the /etc/hosts file, add # in front of the IP
address that is not recorded in the tao.cfg. In this example, the IP address that should be
commented off is 10.121.10.102.
#
# Internet host table
#
127.0.0.1
localhost
#10.121.10.102
aries.china
10.161.10.101
aries.china
6.
aries
aries
Run the following commands to restart the server:

# sync; sync; sync; sync; sync; sync;
# /usr/sbin/shutdown -g0 -y -i6
If the M2000 applications are installed, the Oracle service and the M2000 services are
restart automatically after the operating system restarts.
14.3.4 How Should I Log In to the Server in SSH Mode?

This section describes how to log in to the server in SSH mode. After the Linux operating system
is installed, you need to log in to the server in SSH mode with respect to system security. You
can use the PuTTY tool.
Question
How should you log in to the server in SSH mode?
Prerequisites
l
The Linux operating system is already installed.
You have downloaded the PuTTY tool package PuTTY.zip from http://
support.huawei.com to the local PC.
1.
Decompress PuTTY.zip, and then double-click PuTTY.exe. A dialog box is displayed, as

shown in Figure 14-1.
Answer
Issue 03 (2010-12-31)

14-23
M2000
14 FAQs (HP)
Figure 14-1 PuTTY Configuration
2.
In the Host Name (or IP address) field, enter the IP address of the server to be logged in
to.
3.
Select Protocol:SSH.
4.
Select Close window on exit:Only on clean exit.
5.
Click Open.
When you open the window for the first time, the following interface is displayed, click
Yes.
Figure 14-2 PuTTY Security Alert
14-24

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
6.
When the system displays login as:, type a user name and then press Enter.
7.
When the system displays root@10.10.10.1's password:, type the password and
then press Enter.
When the system displays Last login: Wed Oct 31 11:59:36 2007 from
10.10.10.12, you can infer that the login is successful.
14.3.5 How Should I Log In to the Server in MP Mode?

This describes how to log in to the server in MP mode.
Question
If logging in to the server in SSH mode fails, you need to use the MP mode. How should you
operate?
Answer
1.
Ensure that the communication between the PC and the iLO 2 MP serial port is normal.
2.
Run the following command on the PC to set up the connection between the PC and the
iLO 2 MP.
After you log in to the system, enter the user name and password of the iLO 2 MP. Both
the default user name and the password are Admin.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
3.

[mp001b78d20747] MP> CO
NOTE
The MP command is case insensitive. If any error is prompted when you perform the command in
uppercase, perform the command in lowercase.
14.3.6 How Do I Configure the Monitoring Function of the S2600

Disk Array?
This section describes how to configure the monitoring function of the S2600 disk array.
Question
How do I configure the monitoring function of the S2600 disk array?
Answer
Perform the following operations to configure the monitoring function of the S2600 disk array:
1.
Log in to controller A of the S2600 disk array in SSH mode.

# ssh admin@IP address of controller A
Issue 03 (2010-12-31)

14-25
M2000
14 FAQs (HP)
CAUTION
The initial name and password of the administrator user is admin and 123456, respectively.
For security considerations, you are advised to change the password after you log in to the
system for the first time.
2.
Run the following command to check whether the disk array is set with a Trap IP address:
OceanStor: admin> showtrapip
Index
S26000
IP Address
192.168.8.241
Port ID
162
Version
2
l If there is no system output, you can infer that no Trap IP address is set. In this case,
perform 3 to set a Trap IP address.
l If the system output is similar to the previous information, check whether the
configurations in the system output are correct. If they are incorrect, perform 4 to modify
the configurations.
3.
Run the following command to set a Trap IP address of the disk array:
For example, set the Trap IP address of the disk array to 192.168.8.241.
OceanStor:admin> addtrapip -a 192.168.8.241 -v 2 -p 162
NOTE
In the single-server system, you need to set only one Trap IP address.
Repeat 3 if another Trap IP addresses need to set.
4.
Run the following command to change the Trap IP address of the disk array:
For example, change the Trap IP address of the disk array to 10.10.10.10.
OceanStor:admin> chgtrapip -i S26000 -a 10.10.10.10
Run the following command to check whether the Trap IP address is successfully changed:
OceanStor:admin> showtrapip
Index
S26000
5.
IP Address
10.10.10.10
Port ID
162
Version
2
Run the following command to change the system time of the disk array:
For example, change the system time to 2008-12-17/11:05:00.
OceanStor: admin> chgsystime -t 2008-12-17/11:05:00
NOTE
l The system time of the disk array must be the same as that of the connected M2000 server.
l The command chgsystime is used to change the system time. The time ranges from 1970-01-01
00:00:00 to 2069-12-31 23:59:00.
6.
Run the following command to log out of controller A:

7.
8.
Add the IP address of the disk array controller to the SANtricty_config.xml file.
# cd /opt/OMC/resourcemonitor
# vi SANtricty_config.xml
<config>
<src name = "trapsender" ip = "IP address of controller A" port = "23001"
iorstring = ""/>
14-26

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
<src name = "trapsender" ip = "IP address of controller B" port = "23001"

iorstring = ""/>
</config>
If the IP address of the controller is incorrect in the file, replace the existing IP address with
a new IP address. Then, press Esc and run the :wq command to save the modification and
quit.
9.
Run the following command to view the user.xml file:

# vi user.xml
<snmp name = "trap">
<instance name = "san" run = "true" filepath = "SANtricty_config.xml"/>
<instance name = "vcs" run = "true" filepath = "vcs_config.xml"/>
<loginfo name = "debug" run = "false" filepath = "HDMonitor.debug"/>
</snmp>
l If the status of san in the file is true, do not modify the file. Press Esc and run the :q
command to quit.
l Otherwise, change the status of san to true. Then, press Esc and run the :wq command
to save the modification and quit.
10. Run the following commands to restart the ResourceMonitor process:
# ps -ef | grep "ResourceMonitor"
root 10256
884
0 10:57:58 ?
0:55 /opt/OMC/bin/ResourceMonitor cmd start -ipaddr 10.71.15.31 >/dev/null 2>&1
root 20762 26443
0 16:54:48 pts/4
0:00 grep ResourceMonitor
# kill -9 10256
NOTE
In the previous command, replace the ResourceMonitor process ID 10256 with the actual value.
11. Run the following commands to restart the UdpDispatchService service:

NOTE
You need to restart the UdpDispatchService service on only active server.
# svc_adm -cmd restartsvc UdpDispatchService
14.3.7 How Should I Configure the Monitoring Function for the

S3000 Series Disk Arrays
This section describes how to configure the monitoring function for the S3000 series disk arrays,
such as S3100 and S3200.
Question
How should I configure the monitoring function for the S3000 series disk arrays?
Answer
1.
Log in to the server that is to be installed with the OceanStor as user root by using the
WinaXe software.
2.
Install the OceanStor.

NOTE
If the port 162 on the M2000 server is not occupied, the OceanStor is installed on the M2000 server.
Issue 03 (2010-12-31)

14-27
M2000
14 FAQs (HP)
(1) Insert the installation DVD-ROM, namely, Auto Installation DVD2/2 For SLES10
IA64 V1.0, into the DVD-ROM drive of the server.
(2) Run the following command to mount the installation DVD-ROM:
# mount /dev/cdrom /media
(3) Install the SMruntime, SMesm, and SMclient software in sequence.
# cd /media/HWS3000Array/software
# rpm -ivh SMruntime-LINUX64.rpm
# rpm -ivh SMesm-LINUX.rpm
# rpm -ivh SMclient-LINUX.rpm
3.
Add the disk array to be monitored to the OceanStor.

(1) Run the following commands to start the OceanStor management program:
# SMclient
(2) In the Select Addition Method dialog box, select Manual.
(3) Click OK.
(4) In the Add New Storage Array - Manual dialog box, select Out-of-band
management.
Type the IP addresses of the two controllers of the disk array in First Controller and
Second Controller, respectively.
(5) Click Add to add the disk array.
(6) After the disk array is added, click Out-of-band Storage Arrays.
(7) Choose Edit > Configure Alerts.
(8) Click the SNMP tab, as shown in Figure 14-3.
14-28

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
Figure 14-3 SNMP tab page
(9) Type the IP address of the M2000 server in Trap destination.

(10) Click Add.
(11) Wait until the typed IP address is added to the Configured SNMP addresses area in
Figure 14-3, and then click OK.
(12) If the Configure Mail Server dialog box is displayed, click Yes.
4.
Modify the M2000 configuration file to set the monitoring parameters of the OceanStor.
(1) Log in to the M2000 server as user root.
(2) Run the following command to run the environment variables of the M2000:
(3) Run the following commands to run the monitoring script:
# cd /opt/OMC/bin
# ./deployHDMonitor.sh
When the system displays the following prompt, type 2, and then press Enter.
Issue 03 (2010-12-31)

14-29
M2000
14 FAQs (HP)
=============================================================
Please Select the Monitor Type:
1)--Sun Management Center(SMC) Monitor
2)--Sun ST6140/OceanStor S3000 Monitor
Q|q)--Exit
=============================================================
Please make a choice : 2
(4) When the system displays the following prompt, type the IP address of the server
installed with the OceanStor.
Please input the IP of SANtricty server [default:127.0.0.1]: 192.168.1.1
(5) When the system displays the following prompt, type true.
Please set the flag to start SANtricty service [default:false]: true
(6) When the system displays the following prompt, type false.
Please set the flag to start VCS service [default:false]: false
When the system displays Finish to deploy Sun ST6140/OceanStor S3000

Monitor, it indicates that the monitoring parameters of the disk array are set.
NOTE
The configuration takes effect after about 15 minutes.
5.
Check whether the monitoring of the disk array is enabled.

(1) Log in to the server installed with the OceanStor as user root by using the WinaXe
software.
(2) Run the following commands to start the OceanStor management program:
# SMclient
(3) In the displayed dialog box, click Out-of-band Storage Arrays.
(4) Choose Edit > Configure Alerts.
(5) Click the SNMP tab, as shown in Figure 14-3.
(6) In the Configured SNMP addresses area, select the configured IP address, and then
click Validate.
(7) Switch to the fault alarm page of the M2000 client to view the alarm list.
(8) Log in to the M2000 client.
(9) Choose Monitor > Browse Alarm List to view the alarm list.
If the information about the alarm whose ID is 1042 or the location information whose
Description is Alert Test Message is available in the alarm list, it indicates that the
monitoring of the disk array is enabled.
NOTE
Alternatively, you can check whether the monitoring of the disk array is enabled in the following
way:
1. Remove the power supply cable from any disk array to be monitored.
2. Switch to the fault alarm page of the M2000 client to view the alarm list.
If the information about the alarm whose ID is 1042 or the location information whose
Description is Controller tray component failed is available in the alarm list, it indicates that
the monitoring of the disk array is enabled.
14.4 FAQs About the M2000 Server Application (SUSE)

This describes FAQs and solutions related to the M2000 server application.
14.4.1 Why the M2000 Services Are Restarted Abnormally (SUSE)
14-30

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
This describes how to handle the problem of the abnormal restart of the M2000 services.
14.4.2 Why M2000 Services Stop Abnormally
This section describes how to handle the problem of abnormal stop of the M2000 services.
14.4.3 What Should I Do When I Fail to Stop the M2000 Services
This section describes how to handle the failure to stop the M2000 services.
14.4.4 How Should I Periodically Monitor the CPU, Memory, and Disk
The M2000 periodically exports the report of system performance, such as CPU usage, memory
usage, and disk usage. Based on the report, you can analyze the load and performance of the
hardware system.
14.4.5 How to Change the MP Password of rx2660
This describes how to change the MP password of rx2660 to ensure the system security.
14.4.7 How to Use the iLO MP to Check Whether the HP rx2660 Server Is Connected with the
Power Supply
This describes how to use the iLO MP to check whether the HP rx2660 server is connected with
the power supply.
14.4.8 How Should I Add the DVD Option (rx2660)
This describes how to restore the DVD option, which is deleted from Boot Menu, upon the
startup of HP rx2660.
14.4.1 Why the M2000 Services Are Restarted Abnormally (SUSE)

This describes how to handle the problem of the abnormal restart of the M2000 services.
Question
Why does the M2000 services are restarted abnormally?
Answer
The possible causes are as follows:
l
The Oracle database is faulty.
The M2000 system is faulty.
To solve this problem, perform the following steps:

1.
To check whether the M2000 is running, see 7.2.2 Viewing the Running Status of M2000
Services (SUSE). If the M2000 is running, stop the M2000 services. To stop the M2000
services, see 7.2.4 Stopping the M2000 Services (SUSE).
2.
To check whether the Oracle service is running, see 14.2.1 How to Check Whether the
Oracle Is Started (HP). If the Oracle is running, stop the Oracle service. To stop the Oracle
service, see 14.2.3 How to Stop the Oracle (HP).
3.
Restart the Oracle service. For details, see 14.2.2 How to Start the Oracle (HP).
Issue 03 (2010-12-31)

14-31
M2000
14 FAQs (HP)
4.
Restart the M2000 services. For details, see 7.2.3 Starting the M2000 Server (SUSE).
5.
You have logged in to the server as user omcuser, Check system logs.
Check the system log files in /export/home/omc/var/syslog to find out the reason for the
abnormal restart of the M2000 services.
6.
Send the core files to Huawei technical support engineers for assistance.
Check whether files whose names are preceded by core exist in the /export/home/omc/
var/logs directory and send these files to Huawei technical support engineers for assistance.
14.4.2 Why M2000 Services Stop Abnormally

This section describes how to handle the problem of abnormal stop of the M2000 services.
Question
svc_adm -cmd status
When the value of not running in the command result is greater than 0, the service is stopped
abnormally. How to solve this problem?
Answer
The possible causes are as follows:
l
An error occurs during program running.
The startup is stopped manually.
To solve this problem, perform the following steps:

1.
2.
Switch to the installation path of the M2000 . The default installation path of the M2000
is /opt/OMC.
~> cd M2000 installation path
3.
Start M2000 services.

~> start_svc
Do not stop the startup process manually.
4.
If any service is not started, run the following command to start it:
~> svc_adm -cmd restartsvc name of the service that is not started
NOTE
If the service fails to be started, contact Huawei technical support engineers for support.
14.4.3 What Should I Do When I Fail to Stop the M2000 Services

This section describes how to handle the failure to stop the M2000 services.
Question
Why is that the following commands fail to be executed?
14-32

Issue 03 (2010-12-31)
M2000
stop_svc
kill_svc
14 FAQs (HP)
Answer
If the system output is command not found, the possible cause is that you do not run the
environment script before running these commands.
To rectify this fault, perform the following steps:
1.

NOTE
2.
Run the environment script.

For details, see M2000 Command Reference.
14.4.4 How Should I Periodically Monitor the CPU, Memory, and

Disk
The M2000 periodically exports the report of system performance, such as CPU usage, memory
usage, and disk usage. Based on the report, you can analyze the load and performance of the
hardware system.
Prerequisite
Log in to the M2000 server as user omcuser through SSH mode.
Context
The 3-second period is used for sampling the CPU and the memory and the 1-minute period is
used for monitoring disks.
The difference between the monitoring of the clients and the monitoring of the server is that the
monitoring on the client can export the usage of the CPU, memory, and disks only at certain
time. The monitoring on the server, however, can export the periodically sampled usage of the
CPU, memory, and disks.
l
The CPU and the memory performance report file records performance reports in the
following format:
Hostname, Time, CPU Occupancy(%), MEM Occupancy(%),
Physical Memory(MB), Remaining Physical Memory(MB), Swap Memory(MB),
Remaining Swap Memory(MB)
The disk usage report file records disk usage reports in the following format:
Hostname, Time, Partition Name, Total Size(MB),
Used Size(MB), Remaining Size(MB), Used Rate(%), IO Rate(%)
Procedure
Step 1 Switch to the default installation path of the M2000 server software. The default installation
path of the M2000 server software is /opt/OMC.
~> cd /opt/OMC
Step 2 Run the environment variant commands.
Issue 03 (2010-12-31)

14-33
M2000
14 FAQs (HP)
Step 3 Enable the function of exporting reports.
l Enable the function of exporting a performance report.
~> svc_monitor -cmd start -type system
l Enable the function of exporting a disk usage report.
~> svc_monitor -cmd start -type disk
The performance report is saved as a .csv file in M2000 server installation path/var/monitor/
sysinfo. The default file name is sysinfo. The disk usage report is saved as a .csv file in
M2000 server installation path/var/monitor/diskinfo. The default file name is diskinfo.
Step 4 View the exported reports.
l View the performance report.
~> cd M2000 server installation path/var/monitor/sysinfo
~> more Performance report file name
l Check the report about disk usage.
~> cd M2000 server installation path/var/monitor/diskinfo
~> more Disk usage report file name
----End

Question
How to change the MP password of rx2660?
Answer
1.
Run the following command on the PC terminal to establish the connection between the
PC and the iLO 2 MP.
telnet IP address of the iLO 2 MP
After you log in to the system, enter the user name and password of the iLO 2 MP. The
default user name and password is Admin and Admin.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
2.
Run the CM command to switch to the iLO 2 MP command line mode.

MP> CM
3.
Run the UC command to perform user configuration.

MP:CM> UC
4.
At the following prompt, enter C to modify a user configuration:

This command allows you to modify the user configuration.
14-34

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
User Configuration Menu:

L - List current users
N - Add a New user
C - Change a current user
D - Delete a current user
Enter menu item or [Q] to Quit: C
5.
At the following prompt, enter 1 to select Admin.

Current User Configuration:
Login ID
User Name
Access Rights
Enabled
-------------------------------------------------------------------------1 - Admin
Default Admin
C, P, M, U, V
Yes
2 - Oper
Default Operator
C, V
Yes
Select User to modify by number, or [Q] to Quit: 1
6.
At the following prompt, enter P to modify the user password:

Current User Parameters:
L - User Login ID
P - User Password
U - User Name
W - User Workgroup
R - User Access Rights
:
:
:
:
:
Admin
************
Default Admin
Console access, Power control,

MP configuration, User administration,
Virtual Media
- - User Operating Mode
: Multiple
- - User Enabled/Disabled : Enabled
Enter parameter(s) to change, A to modify All, or [Q] to Quit: P
7.
At the following prompt, enter the new user password. The password comprises of 6-24
letters or digits.
For each parameter, enter:
New value, or
<CR> to retain the current value, or
Q to Quit
User Password:
6-24 characters
<CR> to retain current password
8.
At the following prompt, enter the new user password again.

Enter New Password for confirmation:
9.
At the following prompt, enter Y for confirmation.

-> Password will be updated
New User
L * P U W R -
Parameters (* modified values):

User Login ID
: Admin
User Password
: ************
User Name
: Default Admin
User Workgroup
:
User Access Rights
: Console access, Power control,
MP configuration, User administration,
Virtual Media
- - User Operating Mode
: Multiple
- - User Enabled/Disabled : Enabled
Enter Parameter(s) to revise, Y to confirm, or [Q] to Quit: Y
10. Run the following command on the PC terminal to re-establish the connection between the
Issue 03 (2010-12-31)

14-35
M2000
14 FAQs (HP)
After you log in to the system, enter the user name and new password of the iLO 2 MP.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
If you succeed in logging in to the system, you can infer that the password is successfully
changed.

Question
How to change the MP password of rx7640?
Answer
1.
Run the following command on the PC terminal to establish the connection between the
PC and the iLO 2 MP:
After you log in to the system, enter the user name and password of the iLO 2 MP. The
default user name and password is Admin and Admin.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
2.
Run the CM command to switch to the iLO 2 MP command line mode.

MP> CM
3.
Run the SO command to perform configuration.

MP:CM> SO
4.
At the following prompt, enter 2 to modify the user parameters:

1. MP wide parameters
2. User parameters
3. IPMI password
4. OS initiated firmware update permissions
5. Regenerate the ssh server's public key
Which do you wish to modify? ([1]/2/3/4/5) 2
5.
At the following prompt, enter 1 to select Admin.

Current users:
LOGIN
1
2
Admin
Oper
USER NAME
Administrator
Operator
ACCESS
PART.
STATUS
Admin
Operator
1 to 2 to edit, A to add, D to delete, Q to quit : 1
6.
At the following prompt, press Enter.

Current User parameters are:
Login
: Admin
Common Name
: Administrator
Organization
:
Access Level
: Administrator
Mode
: Multiple Use
State
: Enabled
14-36

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
Default Partition :
Enter Login [Admin] :
7.

Enter Common Name [Administrator] :
8.

Enter Organization [] :
9.

Valid Access Levels: Administrator, Operator, Single Partition User
Enter Access Level ([A]/O/S) :
10. At the following prompt, press Enter.

Valid Modes: Single Use, Multiple Use
Enter Mode (S/[M]) :
11. At the following prompt, press Enter.

Valid States: Disabled, Enabled
Enter State (D/[E]) :
12. At the following prompt, enter the new user password. The password comprises of 6-24
letters or digits.
Enter Password [unchanged] :
13. At the following prompt, enter the new user password again.
Re-Enter Password :
14. At the following prompt, enter Y for confirmation.

New User parameters
Login
:
Common Name
:
Organization
:
Access Level
:
Mode
:
State
:
Default Partition :
are:
Admin
Administrator
A
Administrator
Multiple Use
Enabled
Changes do not take affect until the command has finished.

Save changes to user number 1? (Y/[N]) Y
15. At the following prompt, enter Q to quit.

Current users:
LOGIN
1
2
Admin
Oper
USER NAME
Administrator
Operator
ACCESS
PART.
STATUS
Admin
Operator
1 to 2 to edit, A to add, D to delete, Q to quit : Q
16. Run the following command on the PC terminal to re-establish the connection between the
After you log in to the system, enter the user name and new password of the iLO 2 MP.
MP login: Admin
MP password: *****
[osssvr-mp] MP>
If you succeed in logging in to the system, you can infer that the password is successfully
changed.
Issue 03 (2010-12-31)

14-37
M2000
14 FAQs (HP)
14.4.7 How to Use the iLO MP to Check Whether the HP rx2660

Server Is Connected with the Power Supply
This describes how to use the iLO MP to check whether the HP rx2660 server is connected with
the power supply.
Question
How to use the iLO MP to check whether the HP rx2660 server is connected with the power
supply?
Answer
To check whether the HP rx2660 server is connected with the power supply, perform the
following steps:
1.
Log in to the iLO MP through the serial port on the PC or by running the telnet IP address
of the iLO MP command.
After a successful login, type the user name and password of the iLO 2 MP. The default
user name and password are both Admin.
MP login: Admin
MP password: *****
[osssvr] MP>
2.
Run the CM command. The system switches to the MP command line mode.
[osssvr] MP> CM
3.
Check and ensure that the server is powered on.

[osssvr] MP:CM> PS
PS
For System Processor Status see the SS command.
System Power state: OFF
Temperature
: Normal
...
Check the value of System Power state. If its value is OFF. Power on the server
according to the instructions in 1.1 Powering On or Powering Off the M2000 System
(rx2660).
The system returns to the MP prompt.
[osssvr] MP:CM> exit
[osssvr] MP>

Question
If the Internal Bootable DVD option shown in Figure 14-4 is not available on Boot Menu,
how should I add this option?
14-38

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
For details about how to open the system menu, see 1.1.1 Powering On the M2000 System
(rx2660).
Answer
1.
Open Boot Menu, and then choose Boot Configuration, as shown in Figure 14-5.
Figure 14-5 Boot Menu without the DVD option
2.
ChooseAdd Boot Entry, as shown in Figure 14-6.

Figure 14-6 Adding a boot option
Issue 03 (2010-12-31)

14-39
M2000
14 FAQs (HP)
3.
Choose Removable Media Boot [Internal Bootable DVD], as shown in Figure 14-7.
Figure 14-7 Choosing a DVD boot option
4.
When the system displays Enter Description for this entry;, enter Internal
DVD.
5.
When the system displays Enter Load Options or press <Enter> if

none, press Enter.
6.
When the system displays Save changes to NVRAM?[ Y/N]?, type Y. The system
exits, as shown in Figure 14-8.
Figure 14-8 Quitting the addition of a boot option
7.
Press Esc. The system switches to the main menu.

After you successfully add the DVD option, Boot Menu is shown in Figure 14-4.

Question
If the Internal DVD (Upper) Cabinet 0 ... option shown in Figure 14-9 is not available on
Boot Menu, how should I add this option?
14-40

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
Figure 14-9 Boot Menu
For details about how to open the system menu, see 1.2.1 Powering On the M2000 System
(rx7640).
Answer
1.
Open Boot Menu, and then choose Boot Option Maintenance Menu, as shown in Figure
14-10.
Figure 14-10 Boot Menu without the DVD option
2.
ChooseAdd a Boot Option, as shown in Figure 14-11.

Figure 14-11 Adding a boot option
Issue 03 (2010-12-31)

14-41
M2000
14 FAQs (HP)
3.
Choose Removable Media Boot[Acpi(HWP0002,PNPOA03,100)/, as shown in

Figure 14-12.
Figure 14-12 Choosing a DVD boot option
4.
When the system displays Enter New Description;, enter Internal DVD.
5.
When the system displays Enter BootOption Data Type [A-Ascii UUnicode N-No BootOption], type U.
6.
When the system displays Enter Bootoption Data [Data will be stored
as Unicode string]:, type DVD.
7.
When the system displays Save changes to NVRAM [ Y-Yes,N-no], type Y.
8.
On the interface shown in Figure 14-13, click Exit to quit adding the boot option.
Figure 14-13 Quitting the addition of a boot option
9.
14-42
On the interface shown in Figure 14-14, click Exit to exit from Boot Menu.

Issue 03 (2010-12-31)
M2000
14 FAQs (HP)
Figure 14-14 Returning to the main menu
After you successfully add the DVD option, Boot Menu is shown in Figure 14-15.
Figure 14-15 Boot Menu with the DVD option
Issue 03 (2010-12-31)

14-43

M2000 Administrator Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

M2000 Administrator Guide

Încărcat de

Drepturi de autor:

Formate disponibile

M2000

Administrator Guide (HP, SUSE10)

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

2.5.1 Policies for Configuring the NTP

2.5.4 Setting the M2000 Server as the

14.3.7 How Should I Configure the

2.3 Changing the Time Zone on the M2000

Optimized the content descriptions

5.1.1 SUSE User

Optimized the content descriptions

14.4.4 How Should I Periodically Monitor

Optimized the content descriptions

Huawei Proprietary and Confidential

About This Document

4 Managing the M2000 Clients

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

About This Document

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

2 Setting the M2000 Time (SUSE)..............................................................................................2-1

3 Configuring the Parameters of the M2000 Server (SUSE)..................................................3-1

Huawei Proprietary and Confidential

4 Managing the M2000 Clients...................................................................................................4-1

5 Managing the M2000 Users (HP).............................................................................................5-1

6 Managing OSS System..............................................................................................................6-1

Huawei Proprietary and Confidential

6.5.1 Querying the M2000 License...............................................................................................................6-22

7 Managing the M2000 Processes and Services (SUSE).........................................................7-1

Huawei Proprietary and Confidential

7.1.28 log_agent Process...............................................................................................................................7-13

Huawei Proprietary and Confidential

7.2 Managing the M2000 Services (SUSE)........................................................................................................7-24

8 Managing the M2000 Database (Oracle)................................................................................8-1

9 Managing the M2000 Files and Disks (SUSE)......................................................................9-1

10 Backing Up and Restoring the M2000 System (SUSE)...................................................10-1

Huawei Proprietary and Confidential

11 Maintaining the M2000 System (SUSE).............................................................................11-1

12 Emergency Maintenance of the M2000 Client..................................................................12-1