GENEX Mobile Manager Administrator Guide (HP) (V100R002C00 - 04) (PDF) - en

GENEX Mobile Manager
V100R002C00
Administrator Guide (HP)

Issue
04
Date
2013-08-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior 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 a 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 04 (2013-08-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

About This Document
About This Document

Scope
The system components of GENEX Mobile Manager (M2 for short) include M2 client software,
M2 Server software, SAU software, eSAU software, and Agent Server software when the HP
PC servers are used. This document is intended for M2 administrators and provides the concepts
and operation procedures of the M2 system administration tasks which are based on the SUSE
Linux Enterprise Server 10 operating system, Oracle 11g database, and the GaussDB database.
The M2 system includes the M2 Server software, SAU software, eSAU software, and Agent
Server software. This document also provides some routine and emergency maintenance
procedures, commands, tools, and troubleshooting methods.
Product Version
The following table lists the product versions involved in this document.
Product Name
Version
V100R002C00
Operating system
SUSE Linux Enterprise Server 10
Database
M2 Server: Oracle 11g.1.0.7

Agent Server: GaussDB
Intended Audience
This document is intended for:
l
System engineers
Network operators
Issue 04 (2013-08-30)

ii

About This Document
Change History
04 (2013-08-30)
This is the fourth commercial release for V100R002C00.
Compared with Issue 03 (2013-05-30), this issue includes the following changes.
Section
Change Description
11.2.3 Backing Up SAU System Dynamic

Data
Modified the procedure.
11.2.4 Restoring SAU System Dynamic

Data
11.2.5 Backing Up eSAU System Dynamic
Data
11.2.6 Restoring eSAU System Dynamic
Data
SUSE Linux Users and Rights
Modified the content description.
GaussDB Users and Rights

9.2.1 Agent Server System Database
11.1.4 Agent Server Backup Schemes
Changing the Password of User gaussdba
Changing the Password of the GaussDB

Database User
6.2.5 Monitoring Agent Server Database
Status
9.2.2 Checking GaussDB Database
Running Status
9.2.3 Starting GaussDB
9.2.4 Stopping GaussDB
11.2.7 Backing Up Agent Server System
Dynamic Data
11.2.8 Restoring Agent Server System
Dynamic Data
Status
13.5 How Do I Start M2 System Services?
13.6 How Do I Stop M2 System Services?
Issue 04 (2013-08-30)

iii

About This Document
Section
Change Description
13.1 How Do I Log In to the M2 Server in

SSH Mode by Using PuTTY?
13.2 How Do I Use FileZilla to Transfer
Files?
Entire document
Changed the PostgreSQL database to the

GaussDB database.
03 (2013-05-30)
This is the third commercial release for V100R002C00.
Section
Change Description
4.3 Updating the License
02 (2013-03-30)
This is the second commercial release for V100R002C00.
Section
Change Description
3.1 Changing the Host Name and IP

Address of the M2 Server

(One-Click)
(One-Click)
1.2 Powering Off the Server (DL580)
2.1 Changing the Time Zone of the Server

2.2 Changing the Date and Time of the
Server
3.1 Changing the Host Name and IP
Address of the M2 Server
Issue 04 (2013-08-30)

iv

About This Document
Section
Change Description
11.2.2 Restoring M2 System Dynamic Data

(One-Click)
(One-Click)
01 (2013-01-30)
This is the first commercial release for V100R002C00.
Compared with Draft A (2012-11-20), this issue includes the following changes.
Section
Change Description
5.2 Configuring FTP Transfer

Oracle Users and Rights
5.2.1 Introduction to FTP Transmission
Policy
Changing the Password of the GaussDB
Database User
8.2.2 Checking Agent Server Service

Status
9.1.2 Checking Oracle Database Running
Status
Running Status
Status
Optimized the content description.

5.1.5 Managing M2 Users
Added.
5.1.6 Managing Agent Server Users

6 Monitoring the M2 System
7 Managing Logs
Issue 04 (2013-08-30)


About This Document
Section
Change Description
Modifying FTP Security Transfer

Configurations
Deleted.
Entire document
Optimized the content description.
Draft A (2012-11-20)
This is a draft for V100R002C00.
Organization
1 Powering On and Powering Off the Server
This chapter describes how to power on and power off M2 server when the HP DL580 server
acts as M2 server.
2 Configuring Time
This chapter describes how to configure the time zone, date, and time of the server.
3 Configuring Server Parameters
This chapter describes how to change the host name of the server, add or delete the server's
routes, and set the IP address of the M2 server.
4 Managing License
You have permission for the M2 only after obtaining a license. The license file controls the
resources and functions of the M2.
5 Setting M2 System Security
This chapter describes how to manage M2 system users and how to configure FTP transfer for
M2 server.
This chapter describes how to monitor the M2 system. You can learn the status of the services,
processes, hard disks, and databases on the M2 system services, component information of the
M2 system services, and operation logs on the client through M2 system monitoring.
7 Managing Logs
This section describes how to manage the operation logs, system logs, and security logs of the
M2.
8 Managing Processes and Services
This chapter describes how to manage the system processes and services of M2, SAU, eSAU,
and Agent Server.
9 Managing Databases
Issue 04 (2013-08-30)

vi

About This Document
This chapter describes how to manage the M2 databases. It also describes the procedures for
checking the database status of M2 and Agent Server.
10 Managing Files and Disks
This chapter describes how to manage the file system and disks of the server.
11 Backing Up and Restoring Data
This chapter describes how to back up and restore M2 system dynamic data.
12 Routine System Maintenance
This chapter describes the system routine maintenance which is a type of preventive
maintenance. Routine maintenance is classified into daily maintenance, weekly maintenance,
and monthly maintenance. Specified items and guidelines are provided and you can add or delete
the items as required.
13 FAQs
This section describes the common frequently asked questions (FAQs) about the M2 and the
corresponding solutions.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated 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.
Issue 04 (2013-08-30)

vii

About This Document
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.
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.
{ 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
Issue 04 (2013-08-30)

viii

About This Document
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 04 (2013-08-30)
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.

ix

Contents
Contents
About This Document.....................................................................................................................ii
1 Powering On and Powering Off the Server.............................................................................1
1.1 Powering On the Server (DL580)...................................................................................................................................2
1.2 Powering Off the Server (DL580)..................................................................................................................................2
2 Configuring Time..........................................................................................................................4
2.1 Changing the Time Zone of the Server..........................................................................................................................5
2.2 Changing the Date and Time of the Server....................................................................................................................6
2.3 Changing the Date, Time, and Time Zone of the Client................................................................................................7
2.4 Checking DST................................................................................................................................................................8
2.4.1 DST..............................................................................................................................................................................8
2.4.2 Querying the DST Rules of a Time Zone....................................................................................................................9
3 Configuring Server Parameters................................................................................................11

3.1 Changing the Host Name and IP Address of the M2 Server........................................................................................12
3.2 Adding or Deleting Routes of the Server.....................................................................................................................14
4 Managing License........................................................................................................................15
4.1 Viewing the Current License in the System.................................................................................................................16
4.2 Obtaining the ESN........................................................................................................................................................17
4.3 Updating the License....................................................................................................................................................17
5 Setting M2 System Security.......................................................................................................19

5.1 Managing Users............................................................................................................................................................20
5.1.1 Managing SUSE Linux Users of the M2...................................................................................................................20
5.1.2 Managing SUSE Linux Users of the Agent Server...................................................................................................28
5.1.3 Managing Oracle Database Users..............................................................................................................................30
5.1.4 Managing GaussDB Database Users.........................................................................................................................34
5.1.5 Managing M2 Users..................................................................................................................................................36
5.1.6 Managing Agent Server Users...................................................................................................................................37
5.1.7 Changing the Password of Default User Administrator for the Remote Management Port...................................37
5.2 Configuring FTP Transfer............................................................................................................................................38
5.2.1 Introduction to FTP Transmission Policy..................................................................................................................38
6 Monitoring the M2 System........................................................................................................40

Issue 04 (2013-08-30)


Contents
6.1 Setting the Monitoring Parameters...............................................................................................................................41

6.1.1 Setting the Parameters for Monitoring the M2 Server..............................................................................................41
6.1.2 Setting the Parameters for Monitoring the Disk Usage of the M2 Server.................................................................42
6.1.3 Setting the Parameters for Monitoring the Service Status of the M2 Server.............................................................43
6.1.4 Setting the Parameters for Monitoring the Database Usage of the M2 Server..........................................................43
6.2 Monitoring the Status of the M2 Server.......................................................................................................................44
6.2.1 Monitoring the Service Status of the M2 Server.......................................................................................................44
6.2.2 Monitoring the Database Status of the M2 Server....................................................................................................45
6.2.3 Monitoring Agent Server Service Status...................................................................................................................45
6.2.4 Monitoring Agent Server Process Status...................................................................................................................46
6.2.5 Monitoring Agent Server Database Status................................................................................................................46
6.2.6 Monitoring the Disk Status of the M2 Server............................................................................................................47
6.2.7 Monitoring the Resource Status of the M2 Server....................................................................................................47
6.2.8 Viewing the Component Information of the M2 Server............................................................................................47
6.2.9 Refreshing the Monitoring Information....................................................................................................................48
6.2.10 Saving the Monitoring Information.........................................................................................................................48
6.3 Interface Reference for System Monitoring.................................................................................................................48
6.3.1 Parameters for Setting the Monitoring Thresholds of the M2 Server.......................................................................49
6.3.2 Parameters for Setting the Hard Disk Monitoring Thresholds of the M2 Server......................................................50
6.3.3 Parameters for Setting the Database Monitoring Thresholds of the M2 Server........................................................52
6.3.4 Parameters for Setting the Service Monitoring Thresholds of the M2 Server..........................................................54
6.3.5 Parameters for Monitoring the Service Status of the M2 Server...............................................................................55
6.3.6 Parameters for Monitoring the Hard Disk Status of the M2 Server..........................................................................56
6.3.7 Parameters for Monitoring the Database Status of the M2 Server............................................................................57
6.3.8 Parameters for Monitoring the Status of the M2 Server............................................................................................58
6.3.9 Parameters for Viewing the Information About M2 Server Components.................................................................59
7 Managing Logs.............................................................................................................................60
7.1 Log Types.....................................................................................................................................................................61
7.1.1 The M2 Operation Logs............................................................................................................................................61
7.1.2 The M2 System Logs.................................................................................................................................................62
7.1.3 The M2 Security Logs...............................................................................................................................................63
7.1.4 eSAU Service Logs...................................................................................................................................................64
7.1.5 SAU Service Logs.....................................................................................................................................................65
7.1.6 Agent Server Service Logs........................................................................................................................................65
7.2 Managing M2 Server Logs...........................................................................................................................................65
7.2.1 Checking the M2 Operation Logs.............................................................................................................................65
7.2.2 Collecting Statistics on the M2 Operation Logs........................................................................................................67
7.2.3 Checking the M2 System Logs..................................................................................................................................68
7.2.4 Collecting Statistics on the M2 System Logs............................................................................................................70
7.2.5 Checking the M2 Security Logs................................................................................................................................71
7.2.6 Collecting Statistics on the M2 Security Logs..........................................................................................................73
Issue 04 (2013-08-30)

xi

Contents
7.2.7 Checking eSAU Service Logs...................................................................................................................................73

7.2.8 Checking SAU Service Logs.....................................................................................................................................74
7.2.9 Checking Agent Server Service Logs........................................................................................................................74
7.3 Setting Log Templates..................................................................................................................................................75
7.4 Setting an M2 Log Forwarding Server.........................................................................................................................76
7.5 Managing Log Data......................................................................................................................................................77
7.5.1 Setting M2 Log Dump...............................................................................................................................................77
7.5.2 Setting M2 Log Export..............................................................................................................................................78
7.6 Reference of the Log Management GUI......................................................................................................................79
7.6.1 Security Log List.......................................................................................................................................................79
7.6.2 Parameters for Checking Operation Logs ................................................................................................................85
7.6.3 Parameters for Collecting Statistics on Operation Logs............................................................................................88
7.6.4 Parameters for Checking System Logs......................................................................................................................90
7.6.5 Parameters for Collecting Statistics on System Logs................................................................................................92
7.6.6 Parameters for Checking Security Logs....................................................................................................................94
7.6.7 Parameters for Collecting Statistics on Security Logs..............................................................................................96
7.6.8 Parameters for Setting a Log Forwarding Server......................................................................................................99
7.6.9 Parameters for Setting M2 Log Timing Dump........................................................................................................100
7.6.10 Parameters for Setting M2 Log Timing Export.....................................................................................................104
8 Managing Processes and Services..........................................................................................107

8.1 Managing M2 Processes and Services........................................................................................................................108
8.1.1 M2 Server Services and Processes..........................................................................................................................108
8.1.2 Checking M2 Server Service Status........................................................................................................................110
8.1.3 Starting M2 Server Services....................................................................................................................................111
8.1.4 Stopping M2 Server Services..................................................................................................................................112
8.1.5 SAU Services and Processes...................................................................................................................................113
8.1.6 Checking SAU Service Status.................................................................................................................................113
8.1.7 Starting SAU Services.............................................................................................................................................114
8.1.8 Stopping SAU Services...........................................................................................................................................115
8.1.9 eSAU Services and Processes..................................................................................................................................115
8.1.10 Checking eSAU Service Status.............................................................................................................................116
8.1.11 Starting eSAU Services.........................................................................................................................................116
8.1.12 Stopping eSAU Services.......................................................................................................................................117
8.2 Managing the Agent Server Processe and Service.....................................................................................................118
8.2.1 Agent Server Services and Processes......................................................................................................................118
8.2.2 Checking Agent Server Service Status....................................................................................................................118
8.2.3 Starting the Agent Server Service...........................................................................................................................119
8.2.4 Stopping the Agent Server Service..........................................................................................................................119
9 Managing Databases.................................................................................................................121
9.1 Managing Oracle Databases.......................................................................................................................................122
9.1.1 M2 System Databases..............................................................................................................................................122
Issue 04 (2013-08-30)

xii

Contents
9.1.2 Checking Oracle Database Running Status.............................................................................................................122

9.1.3 Staring Oracle..........................................................................................................................................................123
9.1.4 Stopping Oracle.......................................................................................................................................................124
9.2 Managing GaussDB Database....................................................................................................................................125
9.2.1 Agent Server System Database................................................................................................................................125
9.2.2 Checking GaussDB Database Running Status........................................................................................................126
9.2.3 Starting GaussDB....................................................................................................................................................126
9.2.4 Stopping GaussDB..................................................................................................................................................126
10 Managing Files and Disks.....................................................................................................128

10.1 Clearing Up the Disk Space for the Server...............................................................................................................129
10.2 Clearing Up the Disk Space for the Client...............................................................................................................134
11 Backing Up and Restoring Data...........................................................................................136

11.1 Backup Schemes.......................................................................................................................................................137
11.1.1 M2 Backup Schemes.............................................................................................................................................137
11.1.2 SAU Backup Schemes...........................................................................................................................................138
11.1.3 eSAU Backup Schemes.........................................................................................................................................139
11.1.4 Agent Server Backup Schemes..............................................................................................................................139
11.2 Backing Up and Restoring the M2 System..............................................................................................................140
11.2.1 Backing Up M2 System Dynamic Data................................................................................................................140
11.2.2 Restoring M2 System Dynamic Data....................................................................................................................142
11.2.3 Backing Up SAU System Dynamic Data..............................................................................................................144
11.2.4 Restoring SAU System Dynamic Data..................................................................................................................145
11.2.5 Backing Up eSAU System Dynamic Data............................................................................................................146
11.2.6 Restoring eSAU System Dynamic Data................................................................................................................147
11.2.7 Backing Up Agent Server System Dynamic Data.................................................................................................148
11.2.8 Restoring Agent Server System Dynamic Data....................................................................................................149
12 Routine System Maintenance...............................................................................................151

12.1 Routine Maintenance Items......................................................................................................................................152
12.2 Daily Maintenance....................................................................................................................................................153
12.2.1 Viewing the CPU Usage of the Server..................................................................................................................153
12.2.2 Checking the Core Files of M2..............................................................................................................................154
12.2.3 Checking the Core Files of SAU...........................................................................................................................155
12.2.4 Checking the Core Files of eSAU.........................................................................................................................155
12.2.5 Checking SUSE Linux Error Logs........................................................................................................................156
12.2.6 Checking M2 Logs................................................................................................................................................156
12.2.7 Checking SAU Logs..............................................................................................................................................157
12.2.8 Checking eSAU Logs............................................................................................................................................157
12.2.9 Checking Agent Server Logs.................................................................................................................................158
12.2.10 Checking M2 Service Status................................................................................................................................158
12.2.11 Checking SAU Service Status.............................................................................................................................159
Issue 04 (2013-08-30)

xiii

Contents
12.2.12 Checking eSAU Service Status...........................................................................................................................160

12.2.13 Checking Agent Server Service Status................................................................................................................161
12.2.14 Checking Oracle Database Status........................................................................................................................161
12.2.15 Checking GaussDB Database Status...................................................................................................................162
12.3 Weekly Maintenance Items......................................................................................................................................163
12.3.1 Viewing the Hard Disk Usage of the Server.........................................................................................................163
12.3.2 Checking the Server Time.....................................................................................................................................164
12.3.3 Cleaning Up the Disk Space of the Server............................................................................................................164
12.3.4 Cleaning Up the Disk Space of the Client.............................................................................................................170
12.4 Monthly Maintenance Items.....................................................................................................................................170
12.4.1 Checking and Setting M2 Server User Rights.......................................................................................................171
12.4.2 Checking the Power Supply of the Server.............................................................................................................171
12.4.3 Checking the M2 System License.........................................................................................................................171
13 FAQs...........................................................................................................................................173
13.1 How Do I Log In to the M2 Server in SSH Mode by Using PuTTY? ....................................................................174
13.2 How Do I Use FileZilla to Transfer Files?...............................................................................................................177
13.3 How Do I Start M2 System Services? (One-Click)..................................................................................................179
13.4 How Do I Stop M2 System Services? (One-Click)..................................................................................................180
13.5 How Do I Start M2 System Services?......................................................................................................................181
13.6 How Do I Stop M2 System Services?......................................................................................................................183
Issue 04 (2013-08-30)

xiv

Powering On and Powering Off the Server
About This Chapter

This chapter describes how to power on and power off M2 server when the HP DL580 server
acts as M2 server.
1.1 Powering On the Server (DL580)
This section describes how to power on the M2 server when the HP DL580 is used.
This section describes how to power off the M2 server when the DL580 is used.
Issue 04 (2013-08-30)


1.1 Powering On the Server (DL580)

This section describes how to power on the M2 server when the HP DL580 is used.
Procedure
Step 1 Power on the keyboard, video, and mouse (KVM) connected to the server.
The KVM is an operation and maintenance console that is used to control multiple PCs and
servers through a keyboard, a monitor, and a mouse.
Step 2 Turn on the power switch of the server to start it, as shown in Figure 1-1.
Figure 1-1 Power switch of the DL580 server
Step 3 After the server is started, check the status of database services by referring to 9.1.2 Checking
Oracle Database Running Status and check the status of M2 services by referring to 8.1.2
Checking M2 Server Service Status.
Start the corresponding services by referring to 8.1.3 Starting M2 Server Services, 8.1.7
Starting SAU Services, 8.1.11 Starting eSAU Services, 8.2.3 Starting the Agent Server
Service, 9.1.3 Staring Oracle, and 9.2.3 Starting GaussDB if database services and M2
services are not started.
----End

This section describes how to power off the M2 server when the DL580 is used.
Context
Before powering off the server, you need to stop the M2 services and then stop the database
software.
Issue 04 (2013-08-30)


Procedure
Step 1 Stop M2 system services.
You can check whether the M2 one-click installation packge
M2V100R002C00SPC400OneKeyInstall_pkg.tar or one-click script svc_stop.sh is available
in the /export/home/m2install directory by running ls /export/home/m2install.
l Stop M2 system services by referring to 13.4 How Do I Stop M2 System Services? (OneClick) if at least one of the above is available.
l Stop M2 system services by referring to 13.6 How Do I Stop M2 System Services? if neither
of them is available.
Step 2 Stop Oracle services. For detailed operations, see 9.1.4 Stopping Oracle.
Step 3 Log in to the server as user root, and then run the following commands to power off the server:
# sync; sync; sync; sync; sync; sync
# shutdown -h now
Step 4 Turn off the power switches of other devices and the cabinet as required.
----End
Issue 04 (2013-08-30)


2 Configuring Time
Configuring Time
About This Chapter

This chapter describes how to configure the time zone, date, and time of the server.
The accuracy of the server time is dependent on the time zone of the SUSE Linux operating
system. You need to change the time zone of the server when the time zone of the server is
inconsistent with the local time zone.
2.2 Changing the Date and Time of the Server
This section describes how to change the date and time of the server. The server time is closely
related to system operations such as scheduled task processing and database information
dumping. Therefore, you must ensure that the server time is correct so that the system runs
properly.
2.3 Changing the Date, Time, and Time Zone of the Client
This section describes how to change the date, time, and time zone of the M2 client that is based
on the Windows operating system. You can change the date, time, and time zone of the M2 client
by changing the date, time, and time zone of the Windows operating system.
2.4 Checking DST
This section describes how to view the daylight saving time (DST) rules.
Issue 04 (2013-08-30)


2 Configuring Time

The accuracy of the server time is dependent on the time zone of the SUSE Linux operating
system. You need to change the time zone of the server when the time zone of the server is
inconsistent with the local time zone.
Context
l
If you need to change both the time zone and the time, you must first change the time zone.
This section describes how to modify the time zone of the M2 server based on the actual
requirements. Changing the time zone of the server results in the reset or invalidation of
all timers that depend on the operating system. Therefore, you need to stop the M2 and
Oracle services so that the reset or invalidation of timers does not result in function failure
and data error.
Procedure
Step 1 Log in to the server as user root, and then run the following command in the command terminal
window to query the time zone of the server.
# grep TIMEZONE /etc/sysconfig/clock
If ...
Then ...
The time zone of the server is correct End.

The time zone of the server is
incorrect
Perform Step 2.

window to open the YaST Control Center window.
# yast2
Step 5 In the left pane of the YaST Control Center window, click system, and then click Date and
Time in the right pane.
Issue 04 (2013-08-30)


2 Configuring Time
Step 6 According to the description in Time Zone and Clock Settings, change the values of Region
and Time Zone to the actual values.
Step 7 Click Accept.
Step 8 Start Oracle services. For detailed operations, see 9.1.3 Staring Oracle.
Step 9 Start M2 system services.
M2V100R002C00SPC400OneKeyInstall_pkg.tar or one-click script svc_start.sh is
available in the /export/home/m2install directory by running ls /export/home/m2install.
l Start M2 system services by referring to 13.3 How Do I Start M2 System Services? (OneClick) if at least one of the above is available.
l Start M2 system services by referring to 13.5 How Do I Start M2 System Services? if
neither of them is available.
----End
2.2 Changing the Date and Time of the Server

This section describes how to change the date and time of the server. The server time is closely
related to system operations such as scheduled task processing and database information
dumping. Therefore, you must ensure that the server time is correct so that the system runs
properly.
Context
l
If you need to change both the time zone and the time, you must first change the time zone.
This section describes how to modify the time zone of the M2 server based on the actual
requirements. Changing the time zone of the server results in the reset or invalidation of
all timers that depend on the operating system. Therefore, you need to stop the M2 and
Oracle services so that the reset or invalidation of timers does not result in function failure
and data error.
You must ensure that the time of the server is within the validity period of the server
software license so that all services can be normally started.
Procedure
window to query the date and time of the server:
# date
If ...
Then ...
The date and time of the server are correct
End.
The date and time of the server are incorrect
Perform Step 2.
Issue 04 (2013-08-30)


2 Configuring Time

window to change the date and time of the server.
# date mmddHHMMYYYY.SS
NOTE
Wherein:
l mm indicates month.
l dd indicates date.
l HH indicates hour.
l MM indicates minute.
l YYYY indicates year.
l SS indicates second.
Step 5 Run the date command again to query the date and time of the server. If the query results show
that the date and time of the server is incorrect, perform Step 4 again to change the date and
time.
Step 6 Start Oracle services. For detailed operations, see 9.1.3 Staring Oracle.
----End
2.3 Changing the Date, Time, and Time Zone of the Client
This section describes how to change the date, time, and time zone of the M2 client that is based
on the Windows operating system. You can change the date, time, and time zone of the M2 client
by changing the date, time, and time zone of the Windows operating system.
Issue 04 (2013-08-30)


2 Configuring Time
Context
This section describes how to change the date, time and time zone of the Windows XP operating
system.
Procedure
Step 1 Open the Control Panel window, and then double-click Date and Time.
Step 2 In the Date and Time Properties dialog box, change the date, time and time zone of the client
by referring to Table 2-1.
Table 2-1 Changing date and time
Item
Operation
Time
Click the Date & Time tab, and then set hour, minute, or second in the
Time area.
Date
Click the Date & Time tab, and then set date in the Date area.
Time zone
Click the Time Zone tab. Then, select the local time zone from the dropdown list.
Step 3 Click OK.

----End
2.4 Checking DST

This section describes how to view the daylight saving time (DST) rules.
2.4.1 DST
This section describes Daylight Saving Time (DST) and the impact DST has on the M2.
Concept
DST is short for Daylight Saving Time and is one hour earlier than the standard time. For
example, in eastern United States, ten o'clock in the morning in the standard time system is
eleven o'clock in the morning in the DST system.
Impact of DST on the M2

l
The local time of the operating system is automatically increased by one hour when DST
is applied. DST does not affect the system clock. Therefore, the M2 timer is not affected
after DST is applied. The logs and traces of the M2, however, uses the local time. As a
result, one hour of logs and traces are missing.
In normal cases, the local time of the operating system automatically decreases by one hour
when DST is disabled in the M2. This does not affect the storage and switchover of time
because DST does not affect the system clock. The files generated on the modules of the
Issue 04 (2013-08-30)


2 Configuring Time
M2 are named by time stamps. When DST is terminated, the files generated later may cover
the existing files.
2.4.2 Querying the DST Rules of a Time Zone

This section describes how to query the Daylight Saving Time (DST) rules of a time zone. The
DST rules may be adjusted according to the requirements of the local government. Before setting
DST, you need to query the corresponding DST rules based on the time zone name so that the
DST rules defined in the time zone name are consistent with the actual situation.
Context
The SUSE Linux operating system supports two time zone formats: Greenwich Mean Time
(GMT) and time zone name. GMT support time difference but does not support DST. The time
zone name specifies the time difference and DST rules. For the countries or regions that do not
use DST, you are advised to use the GMT format. For the countries or regions that use DST,
you must use the time zone name format.
Procedure
Step 1 Log in to the server as user root.
Step 2 Run the following command to query the DST rules of a time zone in a specific year:
# zdump -v Time zone | grep Specified year
l if DST rules exist, they are displayed as four lines in the command result; if no DST rule
exists, DST is not used.
l The format of the command result is as follows:
Time zone name UTC = Local time/DST isdst=0/1
l The UTC is the same as the GMT.
l isdst=0 indicates that DST is not applied, and isdst=1 indicates that DST is applied.
NOTE
l If you do not specify the year in | grep , the command result shows the DST rules of the time zone in all
years.
l In a particular time zone, DST may start or end on a fixed date. Alternatively, DST may start or end on a
day of week XX of month XX every year. That is, DST starts or ends on a fixed week but not on a fixed
date. For example, at Alaska in the United States, DST starts on the Sunday of the second week of March
every year and ends on the Sunday of the first week of November every year.
l You can run the zdump command to view the DST of the time zone in the last year, current year, and next
year and then deduce the universal DST jumping rule according to the command results.
----End
Example
l
Run the following command to query the DST rules in the Asia/Beijing time zone in 2007:
# zdump -v Asia/Beijing|grep 2007
No information is displayed.
The preceding information indicates that no DST rule exists for the PRC time zone in 2007.
Issue 04 (2013-08-30)


2 Configuring Time
Run the following command to query the DST rules in the US/Alaska time zone in 2007:
# zdump -v US/Alaska|grep 2007
The following or similar information is displayed:
US/Alaska
isdst=0
US/Alaska
isdst=1
US/Alaska
isdst=1
US/Alaska
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
Sun Nov
4 10:00:00 2007 UTC = Sun Nov
4 01:59:59 2007 AKDT

4 01:00:00 2007 AKST isdst=0
The first and second lines of the command result indicate that the time changes from
Mar 11 02:00:00 2007 to Mar 11 03:00:00 2007 and DST starts.
The third and fourth lines of the command result indicate that the time changes from
Nov 4 02:00:00 2007 to Nov 4 01:00:00 and DST ends.
Issue 04 (2013-08-30)

10

Configuring Server Parameters
About This Chapter

This chapter describes how to change the host name of the server, add or delete the server's
routes, and set the IP address of the M2 server.
3.1 Changing the Host Name and IP Address of the M2 Server
This section describes how to change the IP address and host name of the M2 server as required.
3.2 Adding or Deleting Routes of the Server
This section describes how to add or delete routes of the server. By adding or deleting routes on
the server, you can set up or delete the routes from the local network to the target networks.
Issue 04 (2013-08-30)

11

3.1 Changing the Host Name and IP Address of the M2

Server
This section describes how to change the IP address and host name of the M2 server as required.
Procedure
Step 3 Log in to the server as user root and run the following commands.
# . /opt/Nastar/svc_profile.sh
# cd /opt/Nastar/tools/tools_ip
# ./ChangeIP.sh
Step 4 When the system displays the following information, set the host name, private IP address, subnet
mask, and gateway of the server as required:
**********************************************************
*
*
*
Configure System Parameters for PC server
*
*
*
**********************************************************
Please input host name [Default:nassvr,Q:quit]:
Please input IP address [Default:10.141.132.232,Q:quit]:
Please input net masks [Default:255.255.255.0,Q:quit]:
Please input default route [Default:10.141.132.1,Q:quit]:
Step 5 When the system displays the following information, type Y and press Enter:
Are you sure to continue?[Y/N]
When the system displays the following information, the private IP address of the server is
changed successfully:
CfgOracleFile.......Success
ChgProductIP........Success
ChgEsauCFG........Success
DeleteLoadCFG.......Success
Change IP is completed
Please reboot machine
Step 6 Run the following commands to change the private IP address of the server recorded in the
eSAU configuration file:
# cd /opt/esau/script/modifyesau
Issue 04 (2013-08-30)

12

# sh modifyLocalIP.sh /opt/esau Old private IP address of the server new private IP address
of the server
Step 7 Run the following commands to change the private IP address of the server recorded in the
SAU configuration file:
# cd /opt/PSSAU/script/modify
# sh modifyLocalIP.sh /opt/PSSAU Old private IP address of the server new private IP
address of the server
Step 8 Run the following commands to change the public IP address of Agent Server:
NOTE
You are advised not to change the public IP address. Changing the IP address will affect the deployed M2
Agent that accesses Agent Server using the old IP address.
# cd /opt/Nastar/tomcat/script/modify
# sh modifyLocalIP.sh New public IP address of the server
Step 9 Run the following commands to restart the server:
# sync; sync; sync; sync; sync; sync
# shutdown -r now
Step 10 Perform the following substeps 10 minutes after the server is started to check that M2 system
services are running.
1.
Check that M2 services are running. For detailed operations, see 12.2.10 Checking M2
Service Status.
Restart M2 services if M2 services are not running. For detailed operations, see 8.1.4
Stopping M2 Server Services and 8.1.3 Starting M2 Server Services.
2.
Check that eSAU services are running. For detailed operations, see 12.2.12 Checking
eSAU Service Status.
Restart eSAU services if eSAU services are not running. For detailed operations, see 8.1.12
Stopping eSAU Services and 8.1.11 Starting eSAU Services.
3.
Check that SAU services are running. For detailed operations, see 12.2.11 Checking SAU
Service Status.
Restart SAU services if SAU services are not running. For detailed operations, see 8.1.8
Stopping SAU Services and 8.1.7 Starting SAU Services.
4.
Check that GaussDB services are running. For detailed operations, see 12.2.15 Checking
GaussDB Database Status.
Restart GaussDB services if GaussDB services are not running. For detailed operations,
see 9.2.4 Stopping GaussDB and 9.2.3 Starting GaussDB.
5.
Check that Agent Server services are running. For detailed operations, see 12.2.13
Checking Agent Server Service Status.
Restart Agent Server services if Agent Server services are not running. For detailed
operations, see 8.2.4 Stopping the Agent Server Service and 8.2.3 Starting the Agent
Server Service.
----End
Issue 04 (2013-08-30)

13

Follow-up Procedure
You must change the IP address of the server where you want to log in when you log in to the
M2 client again.
3.2 Adding or Deleting Routes of the Server

This section describes how to add or delete routes of the server. By adding or deleting routes on
the server, you can set up or delete the routes from the local network to the target networks.
Prerequisites
You have logged in to the server as user root.
Procedure
l
View, add, and delete routes by referring to Table 3-1.

Table 3-1 Adding, deleting, and viewing a route
Operation
Command
Example
Viewing a
route
# netstat -r
Adding a
route
# route [-v] [-A family] add [-net|host] target [netmask Nm] [gw Gw]
[metric N] [mss M] [window W] [irtt
I] [reject] [mod] [dyn] [reinstate]
[[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 Gw] [netmask Nm]
[metric N] [[dev] If]
# route del -net

192.168.2.128 netmask
255.255.255.128
Automaticall
y adding a
route for the
server each
time the
server is
restarted
l # vi /etc/init.d/boot.route
Write the following

information into the /etc/init.d/
boot.route file:
Write one or multiple route add

[-net|-host] target [netmask
Nm] [gw Gw] [metric N] [mss M]
[window W] [irtt I] [reject] [mod]
[dyn] [reinstate] [[dev] If]
commands in the file.
route add -net 192.168.2.129

netmask 255.255.255.128 gw
192.168.2.130
l Run the following command for

the setting to take effect:
# chmod +x /etc/init.d/
boot.route
# chkconfig boot.route on
----End
Issue 04 (2013-08-30)

14

4 Managing License
Managing License
About This Chapter

You have permission for the M2 only after obtaining a license. The license file controls the
resources and functions of the M2.
4.1 Viewing the Current License in the System
This section describes how to view the current license of the M2.
4.2 Obtaining the ESN
This section describes how to obtain the ESN of the M2 system when the current license is about
to expire. The ESN is used for you to apply for a license.
This section describes how to import a license file when the existing license of the M2 is about
to expire.
Issue 04 (2013-08-30)

15

4 Managing License
4.1 Viewing the Current License in the System

This section describes how to view the current license of the M2.
Prerequisites
l
M2 services are running properly.
You have logged in to the M2 client.
The license has been imported.
Context
Table 4-1 describes the detailed information of the license.
Table 4-1 License information
Item
Attribute
Description
Example
Resource
Control
Product
Name of the product managed

by the license
Resource
Name of the resource

managed by the license
M2 Agent License(Pro)
Capacity
Quantity of the resource

allowed in the license
1000
Consumption
Consumed quantity of the

resource
200
Overflow Time
Expiry date of the license
2012-12-31
Product
Name of the product managed

by the license
Function
Name of a function managed

by the license
UMTS Basic Function

V100R002 or later version
Support or Not
Whether the license allows

users to use the function
support
Function
Control
Procedure
Step 1 In the main menu, choose Help > License Management > License Information.
Step 2 On the Resource Control Item and Function Control Item tab pages of the License
Information dialog box, check the resource and function control information of the license.
----End
Issue 04 (2013-08-30)

16

4 Managing License
4.2 Obtaining the ESN

This section describes how to obtain the ESN of the M2 system when the current license is about
to expire. The ESN is used for you to apply for a license.
Prerequisites
You have successfully installed the operating system of M2 server.
Context
The ESN is necessary for you to prepare the license file, and therefore you must obtain the ESN
in advance.
Procedure
Step 2 Run the following command to check the ESN information.
# ifconfig
Information similar to the following is displayed:
eth0
Link encap:Ethernet
HWaddr 00:0C:29:A3:95:1C
inet addr:10.141.132.232 Bcast:10.141.132.255 Mask:255.255.255.0

inet6 addr: fe80::20c:29ff:fea3:951c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74928795 errors:0 dropped:0 overruns:0 frame:0
TX packets:33718898 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45001321224 (42916.6 Mb) TX bytes:22258980186 (21227.8 Mb)
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
RX packets:222080086 errors:0 dropped:0 overruns:0 frame:0
TX packets:222080086 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:43084623898 (41088.6 Mb) TX bytes:43084623898 (41088.6 Mb)
In the displayed information, 00:0C:29:A3:95:1C is the ESN of the M2 system.

----End

This section describes how to import a license file when the existing license of the M2 is about
to expire.
Prerequisites
l
Issue 04 (2013-08-30)
M2 services are running properly.

17

4 Managing License
You have obtained a new license.
Context
The services provided with M2 are license-controlled. You need to update the license on the
client to use the corresponding resources or functions.
Procedure
Step 2 In the displayed License Information dialog box, click the Function Control Item tab.
Step 3 Click Update License.
Step 4 Select the license file.
Step 5 Click Open.
Step 6 In the displayed License Comparison Result window, click OK.
Step 7 Click Close.
Step 8 Log in to the M2 client again for the license to take effect.
Step 9 Assign M2 Agent licenses. For detailed operations, see Operation and Maintenance > GENEX
Mobile Manager Operator Guide > Preparing for M2 Agent Analysis > Managing M2
Agent Licenses > Assigning M2 Agent Licenses in GENEX Mobile Manager Product
Documentation.
----End
Issue 04 (2013-08-30)

18

Setting M2 System Security
About This Chapter

This chapter describes how to manage M2 system users and how to configure FTP transfer for
M2 server.
5.1 Managing Users
This section describes how to manage user accounts and rights during M2 operations. The users
include SUSE Linux OS users, Oracle database users, and GaussDB database users.
The traditional plaintext FTP mode or the SSL/SSH-based FTP encryption mode can be used
for transferring data between the FTP client and server. By default, the File Transfer Protocol
over SSL (FTPS) mode is used.
Issue 04 (2013-08-30)

19

5.1 Managing Users

This section describes how to manage user accounts and rights during M2 operations. The users
include SUSE Linux OS users, Oracle database users, and GaussDB database users.
5.1.1 Managing SUSE Linux Users of the M2

This describes how to manage SUSE Linux users during M2 operations. The users include
root, omcuser, ftpuser, and oracle. They are created when the Linux operating system is
installed. You can change the passwords of these users according to the actual situation. You
can also create and manage new user accounts as required.

This section provides information about SUSE Linux users involved in the operation of the
M2 system, such as the user name, usage, rights, user group, used shell, and home directory.
Besides the default user root, users oracle, omcuser, and ftpuser are created in the SUSE Linux
operating system.
For details about the SUSE Linux user accounts, see Table 5-1.
Table 5-1 SUSE Linux users
Issue 04 (2013-08-30)
User
Name
Function
Initial
Passwor
d
Rights
User
Group
Shel
l
Res
oluti
on
Prog
ram
Di
rec
tor
y
root
As the default user

account in the
system, user root is
authorized to
control all
resources, create
other user accounts,
assign the rights to
other users, and
perform all system
operations.
Changem
e_123
User root has the

highest rights in the
system.
other, bin,
sys, adm,
uucp, mail,
tty, lp,
nuucp,
daemon,
and
user.root
/
sbin/
sh
/
roo
t
User root is
authorized to
install and uninstall
the M2 system
server applications
and to start and
stop the M2 system
services.

20

User
Name
Function
Initial
Passwor
d
Rights
User
Group
Shel
l
Res
oluti
on
Prog
ram
Di
rec
tor
y
oracle
As the administrator
of the database
software, user
oracle is responsible
for the operation
and maintenance of
the database
software.
Changem
e_123
User oracle is
authorized to
perform all
operations on the
database.
dba,
oinstall,
and
omcuser
/bin/
bash
/
opt
/
ora
cle
Changem
e_123
User omcuser is
authorized to
perform routine
operation and
maintenance and
access the
database.
root, sys,
omcsysm,
dba,
oinstall,
and disk
/bin/
bash
/
ex
por
t/
ho
me
/
om
c
Normally, during
the installation of
the Oracle, user
oracle is
automatically
created in the M2
system and you
need not create user
oracle manually.
omcus
er
As the operator of
the M2 system, user
omcuser is
responsible for
operating and
maintaining the M2
system, such as
querying system
status, backing up
and restoring the
system.
Normally, during
the installation of
the SUSE Linux
operating system,
user omcuser is
automatically
created in the
system, and you
omcuser manually.
Issue 04 (2013-08-30)
User omcuser
cannot install and
uninstall the M2
system server
applications.

21

User
Name
Function
Initial
Passwor
d
Rights
User
Group
Shel
l
Res
oluti
on
Prog
ram
Di
rec
tor
y
ftpuser
User ftpuser is
responsible for data
collection.
Changem
e_123
User ftpuser is
authorized to
transmit data.
dialout,
video, and
omcuser
/bin/
bash
/
ex
por
t/
ho
me
/
sys
m
Normally, during
the installation of
the SUSE Linux
operating system,
user ftpuser is
automatically
created in the
system, and thus
you need not create
user ftpuser
manually.
Changing the Password of User root

This section describes how to change the password of user root.
Prerequisites
l
The old password of user root is available.
The new password of user root is available.
Context
NOTE
The password can contain 8 to 30 characters, including digits 0 to 9, lowercase letters a to z, uppercase
letters A to Z, and special characters @%-=_.]{}. To improve password security, you are advised to use
the following password policies:
l
The password contains at least one uppercase letter.
The password contains at least one lowercase letter.
The password contains at least one digit.
The password contains at least one special character.
The password does not contain the user name.
The password must also meet the requirements of the operating system. For details about the password
policies of the operating system, see the DVD-ROM delivered with the operating system.
Issue 04 (2013-08-30)

22

Procedure
Step 1 Log in to the server as user root, and then type the old password of user root.
Step 2 Run the following command to change the password of user root:
# passwd root
New Password:new password
Reenter New Password:new password
If Password changed or Changed successfully is displayed, the password is
changed successfully.
----End
Changing the Password of User omcuser

This section describes how to change the password of user omcuser.
Prerequisites
l
The old password of user omcuser is available.
The new password of user omcuser is available.
Context
NOTE
l
Procedure
Step 1 Log in to the server as user root, and then run the following commands to change the password
of user omcuser.
# passwd omcuser
----End
Issue 04 (2013-08-30)

23

Changing the Password of User ftpuser

This section describes how to change the password of user ftpuser when you log in to the server
as user root.
Prerequisites
l
The old password of user ftpuser is available.
The new password of user ftpuser is available.
Context
NOTE
l
Procedure
Step 1 Run the following commands to stop M2 services:
1.
Check that the M2 services are running properly. For detailed operations, see 8.1.2
Checking M2 Server Service Status.
2.
Stop M2 services. For detailed operations, see 8.1.4 Stopping M2 Server Services.
NOTE
Currently, the M2 Server are co-deployed with the Agent Server. The Tomcat server provided with M2
services is used in Agent Server services. The Agent Server services are stopped when the M2 services are
stopped.
Step 2 Perform the following substeps to stop eSAU services:

1.
Check that the eSAU services are running properly. For detailed operations, see 8.1.10
Checking eSAU Service Status.
2.
Stop eSAU services. For detailed operations, see 8.1.12 Stopping eSAU Services.
Step 3 Perform the following substeps to stop SAU services:

1.
Check that the SAU services are running properly. For detailed operations, see 8.1.6
Checking SAU Service Status.
2.
Stop SAU services. For detailed operations, see 8.1.8 Stopping SAU Services.
Step 4 Log in to the server as user root, and run the following command to change the password of
user ftpuser:
# passwd ftpuser
New password: New password
Issue 04 (2013-08-30)

24

Reenter new password: New password

When Password changed or Changed successfully is displayed, the password is
Step 5 Run the following commands to modify the configuration items related to the ftpuser password
of eSAU.
# cd /opt/esau
# . ./svc_profile.sh
# cd /opt/esau/script/modifyesau
# sh modifyLocalPasswd.sh /opt/esau Old password New password ftpuser
Step 6 Run the following commands to modify the configuration items related to the ftpuser password
of SAU.
# cd /opt/PSSAU
# cd /opt/PSSAU/script/modify
# sh modifyLocalPasswd.sh /opt/PSSAU Old password New passwordftpuser
Step 7 Start M2 services. For detailed operations, see 8.1.3 Starting M2 Server Services.
NOTE
Agent Server services are started when M2 services are started.
Step 8 Start eSAU services. For detailed operations, see 8.1.11 Starting eSAU Services.
Step 9 Start SAU services. For detailed operations, see 8.1.7 Starting SAU Services.
----End
Changing the Password of User oracle

This section describes how to change the password of user oracle.
Prerequisites
l
The old password of user oracle is available.
The new password of user oracle is available.
Issue 04 (2013-08-30)

25

Context
NOTE
l
Procedure
of user oracle.
# passwd oracle
----End
Creating SUSE Linux Users

This section describes how to create SUSE Linux users. You can create other SUSE Linux users
as required.
Context
l
This section describes how to create user test1. User test1 with user ID 123 belongs to the
staff user group. The main directory /home1 is automatically created. The template files
are saved in the /etc/skel directory. This user account adopts the B shell program.
The template files are used to ensure a unified operating environment.
Procedure
Step 1 Log in to the server as user root, and then run the following command to create user test1.
# useradd -d /home1 -g staff -m -k /etc/skel -u 123 -s /bin/bash test1
Issue 04 (2013-08-30)

26

NOTE
l -d /home1: indicates that the main directory is home1. Change /home1 to the actual main directory
when you create other users.
l -g staff: indicates that the user belongs to the staff group. Change staff to the actual group when you
create other users.
l -m: indicates that the system creates this directory automatically if the main directory does not exist.
l -k /etc/skel: copies the template files in a specified directory to the main directory. Common template
files include .profile and .cshrc files. If the main directory already exists, ensure that the user who
create the main directory and the users that are in the same user group as the user who create the main
directory have the read, write, and operation permissions of the directory.
l -u 123: indicates that the user ID is 123. One user has a unique ID. Replace the ID with the actual user
ID when you create other users.
l -s /bin/bash: indicates that the user uses B Shell. Change B Shell to the actual shell.
Step 2 Run the following command to set the password for the new user account:
NOTE
l The password contains at least one uppercase letter.
l The password contains at least one lowercase letter.
l The password contains at least one digit.
l The password contains at least one special character.
l The password does not contain the user name.
# passwd test1
----End
Deleting SUSE Linux Users

This section describes how to delete SUSE Linux users. You can delete the SUSE users that are
not required. User root cannot be deleted.
Procedure
Step 1 Log in to the server as user root, and then run the following command to delete SUSE Linux
users:
# userdel -r User name
After the previous command is executed, run the following command. If su: user name
of the deleted user does not exist is displayed, deleting the user account
succeeds.
Issue 04 (2013-08-30)

27

# su - Name of the user to be deleted
CAUTION
You cannot delete a login user by running the userdel command.
----End
5.1.2 Managing SUSE Linux Users of the Agent Server

Agent Server and sM2 Server are co-deployed in the current version. The management of users
root and omcuser is the same while the management of user gaussdba of Agent Server is
different from that of the M2.

This section provides information such as user name, function, user group, used shell, home
directory, and rights about the SUSE Linux users involved in the operation of the Agent
Server system.
For details about the SUSE Linux user accounts, see Table 5-2.
Table 5-2 SUSE Linux users
Issue 04 (2013-08-30)
User
Name
Function
Initial
Passwor
d
Rights
User
Group
Shell
Resol
ution
Progr
am
Di
rec
tor
y
root
As the default user

account in the system,
user root is
authorized to control
all resources, create
other user accounts,
assign the rights to
other users, and
perform all system
operations.
Change
me_123
User root has the

highest rights in the
system.
other,
bin, sys,
adm,
uucp,
mail,
tty, lp,
nuucp,
daemon
,
user.roo
t
/sbin/
sh
/
roo
t
User root is
authorized to install
and uninstall the
M2 system server
applications and to
start and stop the
M2 system
services.

28

User
Name
Function
Initial
Passwor
d
Rights
User
Group
Shell
Resol
ution
Progr
am
Di
rec
tor
y
omcus
er
As the operator of the

M2 system, user
omcuser is
responsible for
operating and
maintaining the M2
system, such as
querying system
status, backing up and
restoring the system.
Change
me_123
User omcuser is
authorized to
perform routine
operation and
maintenance and
access the
database.
root,
sys,
omcsys
m, dba,
oinstall,
disk
/bin/
bash
/
ex
por
t/
ho
me
/
om
c
As an operating
omcsys
system user, this
m
user is authorized
to start, access, and
perform the routine
operation and
maintenance on the
GaussDB database.
/bin/
bash
/
ho
me
/
ga
uss
db
a
User omcuser
cannot install and
uninstall the M2
system server
applications.
Normally, during the

installation of the
SUSE Linux
operating system,
user omcuser is
automatically created
in the system, and you
omcuser manually.
gaussd
ba
GaussDB
administrator account
of the Agent Server
database software.
User gaussdba is
responsible for the
routine operation and
maintenance of the
GaussDB database
software.
Users set
the
password
as
required
when
installing
the server
software.
Normally user
gaussdba is
automatically created
in the system when
the GaussDB is
installed, and
therefore you do not
need to create
gaussdba manually.
Changing the Password of User gaussdba

This section describes how to change the password of user gaussdba.
Issue 04 (2013-08-30)

29

Prerequisites
l
The old password of user gaussdba is available.
The new password of user gaussdba is available.
Context
NOTE
l
Procedure
of user gaussdba.
# passwd gaussdba
----End
5.1.3 Managing Oracle Database Users

This section describes the Oracle users and rights for M2 database and the procedure for changing
the password.
Oracle Users and Rights

This section describes the Oracle users used by the M2 and the related rights. To operate the
Oracle database on the M2 Server, you must use the Oracle user accounts.
Only the Oracle user is authorized to use the Oracle database. After the Oracle database is
installed, the system provides the default user accounts, namely, SYS and SYSTEM.
For details about the Oracle user accounts, see Table 5-3.
Issue 04 (2013-08-30)

30

Table 5-3 Oracle users

User Name
Initial Password
User Description
SYS
Changeme_123
User sys has the highest rights.
SYSTEM
Changeme_123
User system has the highest rights.
SYSMAN
sysman
This user is created inside the Oracle

database. It has expired or has been locked.
WMSYS
wmsys

MGMT_VIE
W
mgmt_view

ORACLE_D
CM
oracle_dcm

TSMSYS
tsmsys

DBSNMP
dbsnmp

OUTLN
outln

DIP
dip

ALARMDB
Changeme_123
This is a product data user.
IMAPEAMD
B
Changeme_123
IMAPLOGD
B
Changeme_123
IMAPSMDB
Changeme_123
IMAPTEMP
DB
Changeme_123
IMAPTMDB
Changeme_123
IMAP_DB
Changeme_123
naspa
Changeme_123
User naspa is used to access the Oracle

database of the M2 system.
Changing Passwords for Oracle Database Users

This section describes how to change passwords for Oracle database users.
Issue 04 (2013-08-30)

31

Prerequisites
l
The old password of Oracle users is available.
The new password of Oracle users is available.
Context
CAUTION
You cannot change the password of a single database user. This function changes the password
of the Oracle administrator and the passwords of the table space users of the databases in the
M2.
A user password of the Oracle database can contain only Arabic numerals, case-insensitive
letters, and _. The valid password length contains 8 to 30 characters. To improve password
security, the password must:
l
Start with a letter.
Contain one or more letters.
Contain one or more Arabic numerals.
The password must also meet the requirements for the Oracle database. For details about the
password policies of the Oracle database, see the DVD-ROM delivered with the Oracle database.
Procedure
Step 1 Stop the eSAU services.
1.
Log in to the server as user omcuser.
2.
Run the following command to stop the eSAU services:

~> cd /opt/esau
~> . ./svc_profile.sh
~> esau_stop
3.
Run the following command to check whether the eSAU services are stopped:
~> esau_ps
l If the information similar to the following is displayed, eSAU service processes are
stopped. Perform Step 2.1.
Monitor............................not running
eSAU...............................not running
SysMonitor.........................not running
[All Services: 3 ] [Running: 0 ] [Not Running: 3 ]
l If the displayed information is not consistent with the preceding information or no

information is displayed, eSAU service processes are not stopped completely. Perform
Step 1.4.
4.
Run the following command to forcibly stop the eSAU services:

~> esau_kill
Issue 04 (2013-08-30)

32

Step 2 Stop the M2 services.

1.
2.
Run the following command to stop the M2 services:

~> cd /opt/Nastar
~> stop_svc
3.
Run the following command to check whether the M2 services are stopped:
~> svc_ps
l If no command output is displayed, the M2 services have been stopped. Go to Step
2.5.
l If there is any command output, the M2 services do not stop. Go to Step 2.4.
4.
Run the following command to forcibly stop the M2 services:

~> kill_svc
5.
Run the following command to stop the M2 daemon process:

~> stop_daem
6.
Run the following command to check whether the M2 daemon process is stopped:
~> daem_ps
If no command output is displayed, the M2 daemon process has been stopped. Go to Step
2.8.
If there is any command output, the M2 service does not stop. Go to Step 2.7.
7.
Run the following command to forcibly stop the M2 daemon process:

~> kill_daem
8.
Run the following command to check whether the TAO process is stopped:
~> ps ef|grep 9999|grep v grep
If no command output is displayed, the TAO process has been stopped. Go to Step 3.1.
If there is any command output, the TAO process does not stop. Go to Step 2.9.
9.
Run the following command to forcibly stop the TAO process:

~> stop_tao_services
Step 3 Change passwords for the Oracle database users.

1.
Run the following command to switch to the directory where the script is stored:
~> cd /opt/Nastar/tools/config
2.
Run the following command to modify the script of changing passwords for Oracle database
users:
~> ./modify.sh
------------------------------------------------------------------
Issue 04 (2013-08-30)

33


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]:
------------------------------------------------------------------
3.
Type 3 and press Enter.
4.
Type a password as prompted and confirm it.

The following message is displayed:
Are you sure to continue?
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]:
5.
Type Y and press Enter.

After password change, the following message is displayed:
-----------------------------------------------------------------Operator complete!
------------------------------------------------------------------
6.
Exit the script as prompted.
Step 4 Restart the M2 services.

~> cd /opt/Nastar
~> start_svc
Step 5 Restart the eSAU service.
1.
2.
Run the following commands to restart the eSAU service:

~> cd /opt/esau
~> esau_start
----End
5.1.4 Managing GaussDB Database Users

This section describes the GaussDB database users and rights for Agent Server and the procedure
for changing the password of the GaussDB database users.
Issue 04 (2013-08-30)

34

GaussDB Users and Rights

This section describes the GaussDB users involved in the operation of the Agent Server database
and the rights of these users. User accounts must be available if you want to perform operations
on the GaussDB database of Agent Server.
Only a GaussDB user is authorized to use the GaussDB database. During the process of installing
the server software, the system prompts you to type user names and passwords of user
gaussdba and mmagents. The initial passwords are the same.
Table 5-4 GaussDB user
User
Name
Initial Password
User Description
gaussdba
Users set the password as

required when installing the
server software.
gaussdba is the administrator of the

GaussDB database.
mmagents
Users set the password as

required when installing the
server software.
mmagents is used for Agent Server to

access the GaussDB database.
Changing the Password of the GaussDB Database User

This section describes how to change the password of GaussDB database users.
Prerequisites
l
The old password of the GaussDB database user is available.
The new password of the GaussDB database user is available.
Context
NOTE
l
Procedure
Step 1 Stop the Tomcat service.
Issue 04 (2013-08-30)

35

1.
2.
Run the following commands to stop the Tomcat service processes:

~> cd /opt/Nastar
~> cd tomcat
~> . service.sh stop
service stopping...
service stopped successful.
If the displayed information is consistent with the preceding information, Tomcat services
are stopped.
Step 2 Change the password of the GaussDB database user.
1.
2.
Run the following commands to change the password for logging in to the GaussDB
database.
~> cd /opt/Nastar
~> cd /opt/Nastar/tomcat/script/modify
~> . GaussDB_Password.sh
Please enter the password for gaussdba:
Please enter the old password for the role mmagents:
New Password:
Reenter New Password:
Type the password of the operating system user gaussdba, and the old and new passwords
of user mmagents as prompted.
----End
5.1.5 Managing M2 Users

This section describes how to manage M2 users. You can manage the accounts and rights of
these users and monitor the sessions and operations of these users. This helps ensure system
security.
Prerequisites
You have obtained the account and password of the M2 system administrator.
Procedure
l
For details about how to manage M2 users, see the section Operation and Maintenance
> Security Management > Configuration and Management of User Securityin the
GENEX Mobile Manager Product Documentation.
----End
Issue 04 (2013-08-30)

36

5.1.6 Managing Agent Server Users

This section describes how to manage Agent Server users. You can manage the accounts and
rights of these users and monitor the sessions and operations of these users. This helps ensure
system security.
Prerequisites
You have obtained the account and password of the Agent Server administrator.
Procedure
l
For details about how to manage Agent Server users, see the section Operation and
Maintenance > Security Management > Configuration and Management of User
Securityin the GENEX Mobile Manager Product Documentation.
----End
5.1.7 Changing the Password of Default User Administrator for the

Remote Management Port
This section describes how to change the password of default user Administrator by logging
into the management window at the remote management port.
Prerequisites
l
You have obtained the IP address of the existing remote management port.
You have obtained the old password of user Administrator for the remote management
port.
You have planned the new password of user Administrator for the remote management
port.
Context
CAUTION
The password of user Administrator for the remote management port must adhere to the
following rules:
l
The password does not contain the user name. It contains 8 to 30 characters, including digits
0 through 9, lowercase letters a through z, uppercase letters A through Z, and the following
special characters: @ % - = _ . ] {}.
Issue 04 (2013-08-30)

37

Procedure
Step 1 Enter https://IP address of the remote management port in the address box of the web browser,
and press Enter. The page for logging into the remote management port is displayed.
TIP
If the system displays There is a problem with this website's security

certificate, click Continue to this website (not recommended).
Step 2 Enter the name and password of user Administrator, and click Log In. The management
window at the remote management port is displayed.
Step 3 In the navigation tree, choose Administration > User Administration
Step 4 In the User Administration area, select Administrator in the Local Users list.
Step 5 Click Edit.
Step 6 In User Name and Login Name, enter Administrator. In Password and Password Confirm,
enter the new password of user Administrator.
Step 7 Click Update User to validate the new password of user Administrator.
Step 8 Click Sign Out to exit the remote management port.
----End

for transferring data between the FTP client and server. By default, the File Transfer Protocol
over SSL (FTPS) mode is used.
5.2.1 Introduction to FTP Transmission Policy

This section describes basic concepts of FTP transmission policies and FTP policies of the
M2 server.
Basic Concepts
The FTP client and the FTP server communicate with each other on the basis of security protocols
to ensure data confidentiality and integrity. Security protocols consist of Secure Shell (SSH),
SSH File Transfer Protocol (SFTP), Security Socket Layer (SSL), and FTP Over SSL (FTPS),
as described in Table 5-5.
Table 5-5 Basic Concepts
Issue 04 (2013-08-30)
Concept
Description
SSH
The SSH protocol is usually used to replace the Telnet protocol that is
traditional and insecure. It supports the setup of an encrypted tunnel between
the SSH client and the SSH server. After setting up a TCP connection, the client
and server can transmit data through the encrypted tunnel.
38

Concept
Description
SFTP
As a secure FTP protocol developed from the SSH protocol, the SFTP protocol
is used to transfer files in encryption mode.
SSL
The SSL protocol is used to protect all application protocols based on the TCP
or other transfer protocols.
The SSL protocol is mainly used to identify communication entities and
provides a secure channel for data confidentiality and integrity. The SSL
protocol meets the following basic security requirements: data confidentiality,
data integrity, and entity identification.
FTPS
As a secure FTP protocol developed from the SSL protocol, the FTPS protocol
is used to encrypt data during FTP login connection and data transmission.
Overview of the FTP Transmission Policy

for transferring data between the FTP client and server. By default, the FTPS mode is used.
FTP Policies of the M2 Server

The M2 system only involves the FTP transfer between the SAU and eSAU. By default, the
FTPS mode is used, as shown in Figure 5-1.
Figure 5-1 Encrypted FTP transmission modes
Issue 04 (2013-08-30)

39

Monitoring the M2 System
About This Chapter

This chapter describes how to monitor the M2 system. You can learn the status of the services,
processes, hard disks, and databases on the M2 system services, component information of the
M2 system services, and operation logs on the client through M2 system monitoring.
6.1 Setting the Monitoring Parameters
You can set parameters for the server monitoring, hard disk monitoring, database monitoring,
and service monitoring. When a threshold is reached, the M2 generates an alarm.
6.2 Monitoring the Status of the M2 Server
By monitoring the running status and resource status of the M2, you can understand the health
condition of the M2 and handle the exceptions of the M2 hardware and software in time.
6.3 Interface Reference for System Monitoring
This topic describes the parameters displayed on system monitoring GUIs.
Issue 04 (2013-08-30)

40

6.1 Setting the Monitoring Parameters

You can set parameters for the server monitoring, hard disk monitoring, database monitoring,
and service monitoring. When a threshold is reached, the M2 generates an alarm.
6.1.1 Setting the Parameters for Monitoring the M2 Server

You can set the server monitoring parameters to monitor the performance of the M2 server,
including the CPU usage and memory usage. This helps you to find and handle performance
exceptions in time, ensuring that the M2 server runs effectively. When the CPU usage or memory
usage reaches the specified threshold, the M2 client receives an alarm. You can also determine
whether to display pop-up messages on the client. After you enable this function, the M2 client
displays a pop-up message, prompting you of the high CPU or memory usage on the server.
Context
l
The parameter Server status refresh interval indicates the sampling interval. That is, the
CPU and memory usage is sampled at the specified interval.
CPU overload indicates that the CPU usage is larger than the threshold for alarm generation.
If the CPU usage sampled each time is larger than the threshold for alarm generation, it
means that the CPU is continuously overloaded. In this case, the number of continuous
CPU overload times is equal to that of continuous sampling times.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu.
Step 2 In the System Monitor Settings dialog box, click the Server Monitor tab.
Step 3 Set the parameters.
Step 4 Click OK.
----End
Result
l
When the number of sampling times with overloading reaches the specified value, a high
CPU usage alarm is generated. If the CPU usage sampled at a time is smaller than the
threshold for alarm clearance, the high CPU usage alarm is cleared.
When the memory usage is larger than the threshold for alarm generation, a high memory
usage alarm is generated. When the memory usage is smaller than the threshold for alarm
clearance, the high memory usage alarm is cleared.
When a high usage alarm is generated, the round icon in the CPU Usage or Memory
Usage column turns red on the Server Monitor tab page in the System Monitor
Browser window. If you enable the function of displaying pop-up messages, you can
receive performance exception messages on the status bar of the client.
Issue 04 (2013-08-30)

41

6.1.2 Setting the Parameters for Monitoring the Disk Usage of the
M2 Server
You can set the disk monitoring parameters to monitor the disk usage of the M2 server. This
helps you to find and handle insufficiency of the disk space in time, thereby preventing service
exceptions. When the disk usage reaches the specified threshold, the M2 client receives a high
disk usage alarm. You can also determine whether to display pop-up messages on the client.
After you enable this function, the M2 client displays a pop-up message, prompting you of a
disk exception.
Procedure
Step 2 In the System Monitor Settings dialog box, click the Hard Disk Monitor tab.
Step 3 On the Hard Disk Monitor tab page, set Hard disk status refresh interval and the thresholds
for alarm generation and clearance.
To set the thresholds, specify default values shared by all disks under Default value setting.
Then, you can specify other values in Advanced settings for a specific disk. The detailed
procedure is as follows:
1.
Click + before Default value setting, and then set the thresholds for generating and clearing
alarms of different severities. The threshold specified for generating alarms of a low
severity must be smaller than that for generating alarms of a high severity.
2.
Expand Advanced settings, and then click + before the server name. You can view that
all disks use the default thresholds. To specify other values for a disk, click + before the
disk name, and then click the cell after the name. In the drop-down list, select Customize
value. In the text box, enter the thresholds for generating and clearing alarms of different
severities. If you do not want to receive alarms of a disk, select Disable alarm
generation.
Step 4 Optional: Expand Advanced setting until the disk name is displayed. In the Enable Bubble
column, select Enable or Disable.
Step 5 After the setting, click OK.
----End
Result
l
When the hard disk space usage reaches the threshold set for generating alarms of a certain
severity, a corresponding alarm is generated. When the usage reaches the preset threshold
for a higher severity, an alarm of the higher severity is generated and the existing alarm is
automatically cleared. When the usage is lower than a threshold for clearing alarms of a
severity, the alarm of this severity is cleared.
When a high disk usage alarm is generated, the round icon in the Status column turns red
on the Hard Disk Monitor tab page in the System Monitor Browser window. If you
enable the function of displaying pop-up messages, the message The hard disk partition
is abnormal is displayed on the status bar of the client.
Issue 04 (2013-08-30)

42

6.1.3 Setting the Parameters for Monitoring the Service Status of the
M2 Server
You can set the interval of refreshing the service status and determine whether to display popup messages. If you enable the function of displaying pop-up messages, the M2 prompts service
changes and refreshes the service status at the specified refresh interval.
Procedure
Step 2 In the System Monitor Settings dialog box, click the Service Monitor tab.
Step 3 On the Service Monitor tab page, set Service status refresh interval and determine whether
to display pop-up messages.
Step 4 Click OK.
----End
Result
l
On the Service Monitor tab page in the System Monitor Browser window, information
is refreshed at the specified interval.
When the tooltip function of some services is enabled, a status indicator is displayed on the
status bar in the lower-right corner of the GUI. When all the services for which the tooltip
function is enabled are running, the status indicator is displayed green. When one or
multiple such services are stopped, the status indicator is displayed red and a pop-up
message is displayed.
6.1.4 Setting the Parameters for Monitoring the Database Usage of

the M2 Server
You can set the database monitoring parameters to monitor the M2 database usage. This helps
you to find and handle insufficiency of the database space in time, thereby preventing service
exceptions. When the database usage of the M2 server reaches the lower threshold, the M2
receives a high database usage alarm.
Procedure
Step 2 In the System Monitor Settings dialog box, click the Database Monitor tab.
Step 3 On the Database Monitor tab page, set Database status refresh interval and the thresholds
for alarm generation.
To set the thresholds, specify default values shared by all databases under Default value
setting. Then, you can specify other values in Advanced settings for a specific database. The
detailed procedure is as follows:
Issue 04 (2013-08-30)

43

1.
Click + before Default value setting, and then set the thresholds for generating alarms of
different severities. The threshold specified for generating alarms of a low severity must
be smaller than that for generating alarms of a high severity.
2.
Expand Advanced settings, and then click + before the server name and database instance
name. You can view that all databases use the default thresholds. To specify other values
for a database, click + before the database name, and then click the cell after the name. In
the drop-down list, select Customize value. In the text box, enter the thresholds for
generating alarms of different severities. If you do not want to monitor the usage of a
database, select Disabled Monitoring.
Step 4 After the setting, click OK.

----End
Result
l
When the database usage of the M2 server reaches the threshold for alarm generation, the
M2 generates an alarm. When the usage is smaller than the threshold, the corresponding
clearance alarm is generated.
When the condition for generating a high database usage alarm is met, the round icon in
the Status column turns red on the Database Monitor tab page in the System Monitor
Browser window.
6.2 Monitoring the Status of the M2 Server

By monitoring the running status and resource status of the M2, you can understand the health
condition of the M2 and handle the exceptions of the M2 hardware and software in time.
6.2.1 Monitoring the Service Status of the M2 Server

By viewing the information such as the service names and service status, you can monitor the
service status of the M2. This helps you to understand the running status of the M2 server. Thus,
you can identify and handle exceptions in time, ensuring efficient running of the M2 server.
Context
If a service is stopped or abnormal, its status icon is displayed in red.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu.
Step 2 In the mainSystem Monitor Browser window, click the Service Monitor tab.
Step 3 On the Service Monitor tab page, right-click an service and choose Details.
NOTE
You can also double-click a service to access the Service Details dialog box.
Step 4 In the displayed Service Details dialog box, view the service details and dependencies between
services.
----End
Issue 04 (2013-08-30)

44

6.2.2 Monitoring the Database Status of the M2 Server

By using this function, you can view the information such as the database name, server name,
and database status. The information helps you to understand the running status of the M2 server.
Thus, you can identify and handle exceptions in time, ensuring efficient running of the M2 server.
Context
If the database space is insufficient, contact Huawei technical support engineers to determine
an expansion solution.
Procedure
Step 2 In the mainSystem Monitor Browser window, click the Database Monitor tab.
NOTE
The database monitoring parameters vary according to different databases. For the Oracle database, the
available parameters for database monitoring include Database Name, Total Data Space, Free Data
Space, Total Data Space Usage, Table Space Usage, and Status.
Step 3 On the Database Monitor tab page, view the database status of the M2 server.
Whether Status of a database is Normal depends on the preset alarm threshold. When the
database usage exceeds the threshold, Status changes to Abnormal.
----End
6.2.3 Monitoring Agent Server Service Status

This section describes how to monitor the service status of Agent Server to know its running
status by checking Tomcat service status.
Procedure
Step 1 Log in to the server as user omcuser.
NOTE
l If you have logged in to the server as another user, you can run the su - omcuser command in the
command terminal window to switch to user omcuser.
l If you are required to type a password after the su - omcuser command runs, type the password of user
omcuser.
Step 2 Run the following commands to check the Tomcat service:

~> cd /opt/Nastar
~> cd tomcat
~> . service.sh status
If the following information is displayed, the Tomcat service is started successfully.
Issue 04 (2013-08-30)

45

service is running.
----End
6.2.4 Monitoring Agent Server Process Status

This section describes how to check and monitor Agent Server process status to know Agent
Server running status.
Procedure
Step 2 Run the following commands to check Agent Server process status:
~> cd /opt/Nastar/tomcat/script
~> sh ams_ps.sh
The CPU usage and memory usage of the current Agent Server process are 0.0% and 0.9%
respectively if the information similar to the following is displayed:
%CPU
0.0
%MEM
0.9
NAME
tomcat
Step 3 Press Ctrl+C to exit Agent Server process checking.

----End
6.2.5 Monitoring Agent Server Database Status

This section describes how to check and monitor Agent Server database status to know Agent
Server running status.
Procedure
Step 1 Log in to the server as user gaussdba (The home directory is /home/gaussdba).
NOTE
l If you have logged in to the server as any other user, run su - gaussdba to switch to gaussdba.
l Enter the password of user gaussdba if required when you run the su - gaussdba command.
Step 2 Run the following command to check whether GaussDB database services are started:
~> gs_ctl query
If the information similar to the following is displayed, GaussDB database services are started.
Otherwise, GaussDB database services are not started.
Ha state:
LOCAL_ROLE
STATIC_CONNECTIONS
DB_STATE
DETAIL_INFORMATION
:
:
:
:
Normal
0
Normal
Normal
----End
Issue 04 (2013-08-30)

46

6.2.6 Monitoring the Disk Status of the M2 Server

By using this function, you can view the information such as the total disk capacity and disk
usage to understand the disk status of the M2 server. Thus, you can identify and handle exceptions
in time, ensuring efficient running of the M2 server. If the disk usage is too high, you need to
clear or expand the disk.
Procedure
Step 2 In the mainSystem Monitor Browser window, click the Hard Disk Monitor tab.
Step 3 On the Hard Disk Monitor tab page, view the disk status of the server.
Whether Status of an item is Normal depends on the preset threshold for alarm generation.
When the usage of the item exceeds the threshold, Status changes to Abnormal.
----End
6.2.7 Monitoring the Resource Status of the M2 Server

By using this function, you can view the system resource usage of the M2 server that you have
logged in to. Thus, you can identify and handle exceptions in time, ensuring efficient running
of the M2 server.
Procedure
Step 2 In the mainSystem Monitor Browser window, click the Server Monitor tab.
Step 3 On the Server Monitor tab page, view the status of the M2 server.
----End
6.2.8 Viewing the Component Information of the M2 Server

You can view the information about the components installed on the M2 server that you have
logged in to, including the names, version numbers, and functions of the components.
Procedure
Step 2 In the mainSystem Monitor Browser window, click the Component Information tab.
Step 3 On the Component Information tab page, view the information about all installed components.
----End
Issue 04 (2013-08-30)

47

6.2.9 Refreshing the Monitoring Information

The monitoring information on the M2 client is automatically refreshed based on the specified
monitoring interval. If you want to refresh the monitoring information immediately, you can
click Refresh on each monitor tab page.
Context
l
Only the current tab page is refreshed.
After you switch to another monitor tab, the monitoring information on this tab page is
refreshed immediately.
Procedure
Step 2 In the mainSystem Monitor Browser window, click the tab corresponding to the monitoring
information to be refreshed.
Step 3 Click Refresh.
----End
6.2.10 Saving the Monitoring Information

To facilitate future analysis of the information monitored at certain time, you can save the
monitoring information.
Procedure
Step 2 In the mainSystem Monitor Browser window, click the tab corresponding to 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. The default
format is XML.
l Two types of encoding formats are supported: ANSI - Latin 1 and UTF-8. The default encoding format
is ANSI - Latin 1. You are recommended to use the default encoding format if the saved file does not
need to support multiple languages; otherwise, UTF-8 is recommended.
Step 3 In the Save dialog box, select a path, enter a file name, and click Save.
----End
6.3 Interface Reference for System Monitoring

This topic describes the parameters displayed on system monitoring GUIs.
Issue 04 (2013-08-30)

48

6.3.1 Parameters for Setting the Monitoring Thresholds of the M2

Server
This topic describes the parameters of CPU monitoring and memory monitoring. When setting
the CPU monitoring and memory monitoring thresholds of the server, you need to set these
parameters.
Parameters
Parameter
Server
Monitor
Parameter
Settings
Number of
consecutive
CPU overloads
(10-400)
Description
Setting
Description:
Value:
l If the CPU usage sampled each

time is larger than the alarm
generation threshold, it means
that the CPU is consecutively
overloaded. When the number
of consecutive 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 alarm
clearance threshold, the high
CPU usage alarm is cleared.
Server
Monitor
Threshold
Settings
Issue 04 (2013-08-30)
Server status
refresh interval
(2-60 seconds)
Description:
Value:
Refresh interval of server

monitoring, that is, the CPU usage
is sampled every x seconds.
Value range: 2-60
CPU usage (%)
Description:
Value:
Set Alarm Generation

Threshold and Alarm Clearance
Threshold for the CPU usage
alarm and determine whether to
enable the pop-up prompt.
Value range of usage:

1-99. Default value:
90.

Default value: 15
Value range of offset:

70.
49

Parameter
Memory usage
(%)
Description
Setting
Set Alarm Generation

Threshold and Alarm Clearance
Threshold for the memory usage
alarm.
Value:
l If the memory usage is larger

than Alarm Generation
Threshold of Memory used
rate, the M2 generates a high
memory usage alarm.
Value range of offset:

85.
Value range of usage:

95.
l If the memory usage is smaller

than Alarm Clearance
Threshold of Memory used
rate, the M2 generates a
clearance alarm, prompting
that the high memory usage
alarm is cleared.
l After you enable the pop-up
prompt, if the status is
abnormal, a pop-up prompt is
displayed.
6.3.2 Parameters for Setting the Hard Disk Monitoring Thresholds

of the M2 Server
This topic describes the parameters of hard disk monitoring. When setting the hard disk
monitoring thresholds of the server, you need to set these parameters.
Parameters
Parameter
Disk
Monitor
Parameter
Settings
Issue 04 (2013-08-30)
Hard disk
status refresh
interval
(60-3600
seconds)
Description
Setting
Description:
Value:
Refresh interval of hard disk Value range: 60-3600

monitoring.
Default value: 60

50

Parameter
Disk
Monitor
Threshold
Settings
Default value
setting (%)
Description
Setting
Description:
Setting method:
Default thresholds for

generating and clearing a
high hard disk usage alarm of
the M2 server.
Click + to expand Default

value setting. Set the default
thresholds for generating and
clearing high hard disk usage
alarms in different severities.
l When the hard disk usage

is larger than Alarm
Generation Threshold
of an alarm severity, the
M2 generates a high hard
disk usage alarm of this
severity.
Issue 04 (2013-08-30)
Value:
Value range: 1-99
Default value of Alarm
Generation Threshold:
l warning: 60

is smaller than Alarm
Clearance Threshold of
an alarm severity, the
M2 clears the high hard
severity.
l Minor: 70
l After you enable the popup prompt, if the hard

disk status is abnormal, a
pop-up prompt is
displayed.
l warning: 55

l Major: 80
l critical: 90
Default value of Alarm
Clearance Threshold:
l Minor: 65
l Major: 75
l critical: 85
51

Parameter
Advanced
settings (%)
Description
Setting
Description:
Setting method:
User-defined thresholds for

generating and clearing a
high hard disk usage alarm of
the M2 server. You can set
thresholds for individual
disks.
1. Click + before Advanced

settings to expand the
nodes.

is larger than Alarm
Generation Threshold
of an alarm severity, the
M2 generates a high hard
severity.
is smaller than Alarm
Clearance Threshold of
an alarm severity, the
M2 clears the high hard
severity.
l After you enable the popup prompt, if the hard
disk status is abnormal, a
pop-up prompt is
displayed.
2. Click + before the server

name to expand nodes.
3. Click + before a disk
partition name to expand
nodes. In the drop-down
list after the disk partition
name, select a threshold
setting mode.
Value:
l If you select Default
value, the M2 uses the
threshold specified in
Default value setting.
l If you select Customize
value, the M2 uses
customized thresholds of
alarms. The value range
is 1-99.
l If you select Disable
alarm generation,
theM2 doesn't report
alarms of the disk
partition.
6.3.3 Parameters for Setting the Database Monitoring Thresholds

of the M2 Server
This topic describes the parameters of database monitoring. When setting the database
monitoring thresholds of the server, you need to set these parameters.
Parameters
Parameter
Database
Monitor
Parameter
Settings
Issue 04 (2013-08-30)
Database status
refresh interval
(300-3600
seconds)
Description
Setting
Description:
Value:
Interval of database
refreshing.
Value range: 300-3600

Default value: 300
52

Parameter
Database
Monitor
Threshold
Settings
Default value
setting (%)
Description
Setting
Description:
Setting method:
Default threshold for

generating a high database
usage alarm of the M2
server.
Click + to expand Default

value setting. Set the
default threshold for
generating high database
usage alarms in different
severities.
l When the database usage

is larger than
Threshold of an alarm
severity, the M2
generates a high
database usage alarm of
this severity.
is smaller than
severity, the M2 clears
the high database usage
alarm of this severity.
Issue 04 (2013-08-30)

Value:
Value range: 1-100
Default value:
l warning: 85
l Minor: 90
l Major: 95
l critical: 98
53

Parameter
Advanced
settings (%)
Description
Setting
Description:
Setting method:
User-defined threshold for

generating a high database
usage alarm of the M2
server. You can set
thresholds for individual
databases.
1. Click + before
Advanced settings to
expand nodes.

is larger than
severity, the M2
generates a high
database usage alarm of
this severity.
is smaller than
severity, the M2 clears
the high database usage
alarm of this severity.
2. Click + before the server

name to expand nodes.
3. Click + before the
database instance name
to expand nodes.
4. Click + before a
database name to expand
nodes. In the drop-down
list after the database
name, select a threshold
setting mode.
Value:
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.
6.3.4 Parameters for Setting the Service Monitoring Thresholds of

the M2 Server
This topic describes the parameters of service monitoring. When setting the service monitoring
of the server, you need to set these parameters.
Issue 04 (2013-08-30)

54

Parameters
Parameter
Services Monitor
Parameter Settings
Service status refresh

interval (60-3600
seconds)
Description
Setting
Description:
Value:
Interval of service
refreshing.
Value range:
60-3600
Default value: 60
Service Monitor
Screen Tip Settings
Default Group
Description:
Setting method:
Set whether to
display the service
status at the lower
right corner of the
M2 system monitor
Select a service from

the Service Name
drop-down list.
Select Enable or
Disable in the
corresponding Popup drop-down list.
client by using
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.
6.3.5 Parameters for Monitoring the Service Status of the M2 Server

This topic describes the parameters in the query results on the Service Monitor tab. When
monitoring the service status of the M2 server, you need to set these parameters.
Parameters
Parameter
Description
Service Name
Description:
Name of a service.
Process Name
Description:
Name of a process.
Issue 04 (2013-08-30)

55

Parameter
Description
Description
Description:
Description of functions, interfaces, and other information of
a service.
Status
Description:
Status of a service.
Startup Mode
Description:
Service startup mode: Automatic, Manual, or Disabled. The
Disabled mode is available only for stopped services.
Auto Restart Times
Description:
The system monitor automatically restarts the service when
the service stops abnormally. This parameter indicates the
times for automatically restarting the service.
The number of restart times is cleared when the M2 is
restarted.
NOTE
l The service automatically restarts when Startup Mode of the
service is set to Automatic.
l By default, this menu item is hidden. You can press Ctrl+Alt
+R to display it.
Description:
Start Time
Time when a service is started.

Server Name
Description:
Name of a server.
6.3.6 Parameters for Monitoring the Hard Disk Status of the M2

Server
This topic describes the parameters in the query results on the Hard Disk Monitor tab. When
monitoring the hard disk status of the M2 server, you need to set these parameters.
Parameters
Parameter
Description
File System
Description:
Hard disk partitions and their paths.
Total Size (MB)
Description:
Total size of a specified partition. It equals to the sum of Used
Size and Free Size.
Issue 04 (2013-08-30)

56

Parameter
Description
Used Size (MB)
Description:
Size of the used space of a specified partition.
Free Size (MB)
Description:
Size of the remaining space of a specified partition.
Usage (%)
Description:
Usage of a specified partition.
Status
Description:
State of a specified partition: Normal or Abnormal. If the
hard disk usage is equal to or larger than the threshold, the
state is Abnormal.
6.3.7 Parameters for Monitoring the Database Status of the M2

Server
This topic describes the parameters of the query result displayed in the Database Monitor tab.
When monitoring the database status of the M2 server, you need to set these parameters.
Parameters for Oracle

Parameter
Description
Database Name
Description:
Name of the database on the M2 server.
Total Data Space (MB)
Description:
Total size of the data space in a database.
Free Data Space (MB)
Description:
Size of the remaining data space in a database.
Total Data Space Usage (%)
Description:
Rate of the used data space and the total data space in
a database.
Issue 04 (2013-08-30)

57

Parameter
Description
Table Space Usage (%)
Description:
Rate of the used table space and the total table space
in a database.
NOTE
The Oracle database occupies the table space in a greedy
manner. The high-water mark determines the used and
unused blocks in a segment. The high-water mark increases
after data is added, but does not decrease after data is deleted.
The M2 calculates the Oracle data usage by monitoring the
high-water mark. Therefore, the Oracle data usage monitored
by the M2 does not decrease after data deletion.
Status
Description:
Database state: Normal or Abnormal. If the database
usage is equal to or larger than the threshold, the state
is Abnormal.
6.3.8 Parameters for Monitoring the Status of the M2 Server

This topic describes the parameters in the query results on the Server Monitor tab. When
monitoring the status of the M2 server status, you need to set these parameters.
Parameters
Parameter
Description
Server Name
Description:
Name of the M2 server.
Server Status
Description:
State of the M2 server: Active or Standby.
OS
Description:
Operating system of the server.
Total Physical Memory (MB)
Description:
Total capacity of the physical memory on the server.
Free Physical Memory (MB)
Description:
Remaining capacity of the physical memory on the
server.
Total Swap Memory(MB)
Description:
Total virtual memory space of the M2 server when the
server runs the Solaris or Linux OS.
Issue 04 (2013-08-30)

58

Parameter
Description
Free Swap Memory(MB)
Description:
Remaining virtual memory space of the M2 server when
the server runs the Solaris or Linux OS.
CPU Usage (%)
Description:
Usage of the CPU.
Memory Usage (%)
Description:
Usage of the memory, including the physical memory
and virtual memory.
6.3.9 Parameters for Viewing the Information About M2 Server

Components
This topic describes the parameters on the Component Information tab page. When viewing
the information about M2 server components, you can see these parameters.
Parameters
Parameter
Description
Component
Description:
Component name of the M2 server.
Version
Description:
Component version of the M2 server.
Description
Description:
Component description of the M2 server.
Issue 04 (2013-08-30)

59

7 Managing Logs
Managing Logs
About This Chapter

This section describes how to manage the operation logs, system logs, and security logs of the
M2.
7.1 Log Types
The M2 has operation logs, system logs, security logs. These logs record different log
information.
7.2 Managing M2 Server Logs
This section describes how to check and collects statistics about operation logs, system logs,
and security logs to learn about users' operations on M2 server, the running status of M2 server,
and security-related operations.
7.3 Setting Log Templates
By setting log templates, you can save the specific query and statistical conditions in log
templates. This helps you to query and collect statistics on logs conveniently.
7.4 Setting an M2 Log Forwarding Server
You can set an M2 log forwarding server to forward the M2 logs to a third-party server.
7.5 Managing Log Data
By dumping logs, you can periodically or manually clear the log information that is not required,
preventing the log information from occupying many resources. By exporting logs to files, you
can view logs and identify faults.
7.6 Reference of the Log Management GUI
This topic provides the reference information of the log management GUI.
Issue 04 (2013-08-30)

60

7 Managing Logs
7.1 Log Types

The M2 has operation logs, system logs, security logs. These logs record different log
information.
7.1.1 The M2 Operation Logs

This topic describes the information such as the meaning, path, and parameters of the M2
operation logs. By querying the M2 operation logs, the maintenance personnel can view the user
operation information that the M2 records. In addition, by collecting statistics on the M2
operation logs, the maintenance personnel can count the number of statistics items based on the
statistical conditions.
Description
The operation log records the operations that are performed on the M2 client but do not affect
the M2 security, such as creating views, acknowledging alarms, and clearing alarms.
Path
Operation logs are stored in the database. You can query them through the client. The entry for
querying operation logs through the client is Security > Log Management > Query Operation
Logs.
You can dump operation logs from the database to a file. The entry for dumping operation logs
is Maintenance > Task Management.In the Task Type navigation tree, choose Database
Capacity Management > Operation Log Dump, The default dump paths are /opt/Nastar/var/
ThresholdExport/Log.
After the operation logs are dumped, the M2 generates the associated folder and log file:
l
Folder: In the dump path, the M2 generates a folder named the date of the dump operation.
The format of the name is YYMMDD.
Log file: The following two files are generated in the folder: YYMMDDHHMMSSoperation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-logdateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix number.extension saved the information about the dumped logs.
NOTE
Operation logs can be dumped to a .csv, xml, txt, or html file, and the file can be compressed to a .zip
package.
Parameters
Parameter Name Parameter Meaning
Operation Name
Issue 04 (2013-08-30)
Name of an operation that the user performs on the M2.

61

7 Managing Logs

Risk Level
Levels of risks caused by the operations that are performed on the M2:
Warning, Minor, and Risk.
Operation User
M2 user.
User Type
Type of the user who performs an operation.
Start Time
Time when an operation starts. It is accurate to second.
End Time
Time when an operation ends. It is accurate to second.
Operation Category Type of an operation.

Operation Terminal IP address of the host where an operation is performed.
Operation Object
Object that an operation is performed on.
Operation Result
Result of an operation: successful, failed, partially successful, ongoing

and canceled.
Details
Other useful information about an operation.
7.1.2 The M2 System Logs

This topic describes the information such as the meaning, path, and parameters of the M2 system
logs. By querying the M2 system logs, the maintenance personnel can view the system operation
information that the M2 records. In addition, the maintenance personnel can collect statistics on
the M2 system logs based on the log severity or source.
Description
The system log records the tasks that are performed on the M2 server and affect the running of
the M2. These tasks are triggered on the M2 client, such as starting and executing scheduled
tasks, or triggered on the M2 server, such as starting and stopping the M2 service.
Path
System logs are stored in the database. You can query them through the client. The entry for
querying system logs through the client is Security > Log Management > Query System
Logs.
You can dump system logs from the database to a file. The entry for dumping system logs is
Maintenance > Task Management.In the Task Type navigation tree,choose Database
Capacity Management > System Log Dump The default dump paths are /opt/Nastar/var/
After the system logs are dumped, the M2 generates the associated folder and log file:
Issue 04 (2013-08-30)

62

7 Managing Logs
Log file: The following two files are generated in the folder: YYMMDDHHMMSS-systemlog-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThresholdnumber.extension. The file with the suffix _info.xml saves the configuration information
of the dumped logs, and the file with the suffix -number.extension saves the information
about the dumped logs.
NOTE
System logs can be dumped to a .csv, xml, txt, or html file, and the file can be compressed to a .zip
package.
Parameters
Level
Levels of risks caused by the operations performed on the M2: Warning,

Minor, and Risk.
Source
Module where the M2 performs an operation.
Time
Time when an operation is performed. It is accurate to second.
Basic Information Basic operation information.

Operation Result
Result of an operation: successful, failed or unknown.
Details
7.1.3 The M2 Security Logs

This topic describes the information such as the meaning, path, and parameters of the M2 security
logs. By querying the M2 security logs, the maintenance personnel can view security information
that the M2 records. In addition, by collecting statistics on the M2 security logs, the maintenance
personnel can count the number of statistics items based on the statistical conditions.
Description
Security logs record the security operations that the user performs in the M2, for example, login,
logout, and unlocking.
Path
Security logs are stored in the database. You can query them through the client. The entry for
querying security logs through the client is Security > Log Management > Query Security
Logs.
You can also dump security logs from the database to a file. The entry for dumping security logs
is Maintenance > Task Management.In the Task Type navigation tree,choose Database
Issue 04 (2013-08-30)

63

7 Managing Logs
Capacity Management > Security Log Dump, The default dump paths are /opt/Nastar/var/
After the security logs are dumped, the M2 generates the associated folder and log file:
l
Log file: The following two files are generated in the folder: YYMMDDHHMMSSsecurity-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-logdateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix number.extension saves the information about the dumped logs.
NOTE
Security logs can be dumped to a .csv, xml, txt, or html file, and the file can be compressed to a .zip
package.
Parameters
Security Event
Event that is related to M2 security.
Risk Level
Levels of risks caused by the operations that are performed on the M2:
Operation User
M2 user.
User Type
Type of an M2 user.
Operation Time
Time when an operation is performed. It is accurate to second.
Operation Terminal IP address of the host where an operation is performed.

Operation Object
Object that an operation is performed on.
Operation Result
Result of an operation: successful, failed or partially successful.
Details
7.1.4 eSAU Service Logs

This section describes the information such as the meaning of eSAU service logs and the save
path. The operation and maintenance (OM) personnel locate and analyze problems by checking
eSAU service logs.
Description
eSAU service logs record eSAU's processing information about Counter data.
Issue 04 (2013-08-30)

64

7 Managing Logs
Path
eSAU service logs are server logs and the save path is /opt/esau/var/logs.
7.1.5 SAU Service Logs

This section describes the information such as the meaning of SAU service logs and the save
path. The operation and maintenance (OM) personnel locate and analyze problems by checking
SAU service logs.
Description
SAU service logs record SAU's processing information about raw MCHR data.
Path
SAU service logs are server logs and the save path is /opt/PSSAU/var/logs.
7.1.6 Agent Server Service Logs

This section describes the information such as the meaning of Agent Server service logs and the
save path. The operation and maintenance (OM) personnel locate and analyze problems by
checking Agent Server service logs.
Description
Agent Server service logs consist of two parts: the log information recorded by Tomcat and that
recorded by Agent Server. Their log files are catalina.out and AMS.log. Agent Server service
logs record the procedures of the agent or M2 client connecting to Agent Server, for example,
registration request sent by the agent, file uploading, and configuration information delivery.
Path
Agent Server service logs are saved in /opt/Nastar/tomcat/logs.
7.2 Managing M2 Server Logs

This section describes how to check and collects statistics about operation logs, system logs,
and security logs to learn about users' operations on M2 server, the running status of M2 server,
and security-related operations.
7.2.1 Checking the M2 Operation Logs

You can check the M2 operation logs to know the operation records of the M2.
Context
l
Issue 04 (2013-08-30)
If you query the operation logs based on the operation users, only the names of the users
that have performed operations are displayed in Available Operation User in the Select
Operation User dialog box.
65

7 Managing Logs
By default, users that not in SMManagers groups can query the operation logs of
themselves only. To query the operation logs of all users, set isQueryAll in the
logsvc.xml file on the M2 server to 0, run the following command to import the parameters
in the file to the database, and restart the M2 service for the setting to take effect.
# cd /opt/Nastar
# SettingTool -cmd import -file /opt/Nastar/etc/conf/logsvc.xml
# svc_adm -cmd reload -type sac
# stop_svc
# start_svc
The query result is generated based on the existing data in the database. If the database is
empty, there is no matching query result.
If a value in the Operation User column in the log query result is an invalid user, the system
may have been attacked.
Procedure
Step 1 Choose Security > Log Management > Query Operation Logs from the main menu.
Step 2 In the Filter dialog box, set the filtering conditions, and then click OK.
NOTE
l You can also click Cancel in the Filter dialog box, and then query logs in the Query Operation
Logs window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then
click Open to use an existing template to query logs. If no template exists on the M2, see 7.3 Setting
Log Templates to create a template.
l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs.
l Click Choose at the lower left corner in the Filter dialog box. In the Select Operation Name dialog
box, you can view the operations that can be monitored.
Step 3 Right-click in the query window and perform the following operations.
Operation Name
Operation Method
Details
Right-click a log in the window and choose Details, or double-click

the log.
NOTE
The Log Details dialog box displays the time, risk level, or results of the
operation that generates the log.
Save All Records
1. Right-click a log in the window and choose Save All Records.

2. In the Save dialog box, select the path to save records, and then
click Save.
NOTE
The log records can only be exported as TXT, HTML, CSV, PDF or XLS files.
The default file format is XLS file.
Issue 04 (2013-08-30)

66

7 Managing Logs
Operation Name
Operation Method
Save Selected
Records
1. Select one or more logs in the window, right-click, and then choose
Save Selected Records from the shortcut menu.
click Save.
NOTE
Save Specified
Records
1. Right-click a log in the window and choose Save Specified

Records.
2. In the Save Specified Record dialog box, set the start row and end
row of logs and the name of the file to be saved, and then click
OK.
NOTE
on the right of File
In the Save Specified Records dialog box, click
name. In the Save dialog box, select the path for saving the records. The log
records can only be exported as TXT, HTML, CSV, PDF or XLS files. The
default file format is XLS file.
Print All Records
1. Right-click a log in the window and choose Print All Records.

2. In the Print dialog box, set the print parameters, and then click
Print.
Print Selected
Records
Print Selected Records from the shortcut menu.
Print.
Print Specified
Records
1. Right-click a log in the window and choose Print Specified

Records.
2. In the Print Specified Records dialog box, set the start row and
end row, and then click OK.
Print.
----End
7.2.2 Collecting Statistics on the M2 Operation Logs

You can know the operation status by collecting statistics and analyzing the M2 operation logs.
For example, you can collect statistics about the frequently performed operations within a period.
Issue 04 (2013-08-30)

67

7 Managing Logs
Context
The statistical result is generated based on the existing data in the database. If the database is
empty, there is no matching statistical result.
Procedure
Step 1 Choose Security > Log Management > Operation Log Statistics from the main menu.
Step 2 In the Filter window, set the statistical items and statistical conditions, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Operation Log Statistics window in the
following ways:
l Click Template, and then select Open. Select a template from the template list, and then click Open
to use an existing template to collect statistics on operation logs. If no template exists on the M2, see
7.3 Setting Log Templates to create a template.
l Click Filter. Set Statistical Items and Filter Criteria in the Filter window, and then click OK to
collect statistics on operation logs.
----End
Result
In the Operation Log Statistics window, the statistical result is displayed.
Perform the following operations as required:
l
Click Print to print the statistical result.
Click Save As to save the statistical result.
7.2.3 Checking the M2 System Logs

You can check the M2 system logs to know the important events that occur when the M2 is
running.
Context
l
By default, the users in only the Administrators group can query the system logs.
The query result is generated based on the existing data in the database. If the database is empty,
there is no matching query result.
Procedure
Step 1 Choose Security > Log Management > Query System Logs from the main menu.
Issue 04 (2013-08-30)

68

7 Managing Logs
NOTE
You can also click Cancel in the Filter dialog box, and then query logs in the Query System Logs window
in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to query logs. If no template exists on the M2, see 7.3 Setting Log
Templates to create a template.
Operation Name
Operation Method
Details

the log.
NOTE
Save All Records

click Save.
NOTE
Save Selected
Records
click Save.
NOTE
Save Specified
Records

Records.
OK.
NOTE
Print All Records

Print.
Issue 04 (2013-08-30)

69

7 Managing Logs
Operation Name
Operation Method
Print Selected
Records
Print.
Print Specified
Records

Records.
Print.
----End
7.2.4 Collecting Statistics on the M2 System Logs

You can know the system status by collecting statistics and analyzing the M2 system log. For
example, you can know the type of the services that raise the most alarms.
Context
Procedure
Step 1 Choose Security > Log Management > System Log Statistics from the main menu.
Step 2 In the Filter window, set the statistical condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the System Log Statistics window in the following
ways:
to use an existing template to collect statistics on system logs. If no template exists on the M2, see 7.3
Setting Log Templates to create a template.
l Click Filter. Set the statistical condition in the Filter window, and then click OK to collect statistics
on system logs.
----End
Result
In the System Log Statistics window, the statistical result is displayed.
l
Issue 04 (2013-08-30)

70

7 Managing Logs
7.2.5 Checking the M2 Security Logs

You can check the M2 security logs to know the M2 security operations of the M2.
Context
l
If you query the security logs based on the operation users, only the names of the users that
have performed operations are displayed in Available Operation User in the Select
Operation User dialog box.
By default, the users in only the SMManagers group can query the security logs.
If a value in the Operation User column in the log query result is an invalid user, the system
may have been attacked.
The query result is generated based on the existing data in the database. If the database is empty,
there is no matching query result.
Procedure
Step 1 Choose Security > Log Management > Query Security Logs from the main menu.
NOTE
l You can also click Cancel in the Filter dialog box, and then query logs in the Query Security Logs
window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then
click Open to use an existing template to query logs.
If no template exists on the M2, see 7.3 Setting Log Templates to create a template.
l Click Choose at the lower left corner in the Filter dialog box. In the Select Security Event dialog box,
you can view the operations that can be monitored.
Operation Name
Operation Method
Details

the log.
NOTE
Issue 04 (2013-08-30)

71

7 Managing Logs
Operation Name
Operation Method
Save All Records

click Save.
NOTE
Save Selected
Records
click Save.
NOTE
Save Specified
Records

Records.
OK.
NOTE
Print All Records

Print.
Print Selected
Records
Print.
Print Specified
Records

Records.
Print.
----End
Issue 04 (2013-08-30)

72

7 Managing Logs
7.2.6 Collecting Statistics on the M2 Security Logs

You can know the security operations by collecting statistics and analyzing the M2 security logs.
For example, you can know the period during which maximum number of security operations
are performed and the operations that are performed most frequently.
Context
Procedure
Step 1 Choose Security > Log Management > Security Log Statistics from the main menu.
Step 2 In the Filter window, set the statistical items and filtering conditions, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Security Log Statistics window in the following
ways:
to use an existing template to collect statistics on security logs. If no template exists on the M2, see
7.3 Setting Log Templates to create a template.
l Click Filter. Set Items and Filter Criteria in the Filter window, and then click OK to collect statistics
on security logs.
----End
Result
In the Security Log Statistics window, the statistical result is displayed.
l
7.2.7 Checking eSAU Service Logs

This section describes how to check eSAU service logs.
Procedure
Step 2 Run the following commands to check whether there are errors in the /opt/esau/var/logs
directory.
~> cd /opt/esau/var/logs
~> grep ERROR*
l Collect corresponding log files if you can identify which processes are abnormal onsite. If
this occurs, contact Huawei technical support engineers.
Issue 04 (2013-08-30)

73

7 Managing Logs
l Otherwise, perform Step 3.

Step 3 Optional: Run the following commands to compress the log files. Then contact Huawei
technical support engineers.
~> cd /opt/esau/var
~> tar -zcvf error.tar.gz logs
----End
7.2.8 Checking SAU Service Logs

This section describes how to check SAU service logs.
Procedure
Step 2 Run the following commands to check whether there are errors in the /opt/Nastar/var/logs
directory.
~> cd /opt/PSSAU/var/logs
~> grep ERROR*
~> cd /opt/PSSAU/var
Step 4 Run the following commands to check the error logs upon BS script execution.
~> cd /opt/PSSAU/var/output/log
~> grep ERROR*
l Collect corresponding log files if you can identify the processes with errors at the site. If this
occurs, contact Huawei technical support engineers.
l Otherwise, perform Step 3 again to pack the log files. Then contact Huawei technical support
engineers.
----End
7.2.9 Checking Agent Server Service Logs

This section describes how to check Agent Server service logs to know the important events that
occur when Agent Server is running.
Issue 04 (2013-08-30)

74

7 Managing Logs
Context
l
Agent Server records the information generated when it interacts with the agent to locate
the problems that occur during the interaction. The information includes: the registration
request sent by the agent, authorization, file uploading, and configuration information
downloading.
Agent Server records the information generated when it interacts with M2 Client to locate
the problems that occur during the interaction. The information includes: the configuration
information of the agent, and version and license information.
Procedure
Step 2 Run the following command to navigate to the save path where Agent Server service logs are
saved.
~> cd /opt/Nastar/tomcat/logs
Step 3 Run the following command to check the log information recorded by Agent Server.
~> tail -f AMS.log
NOTE
You can navigate to /opt/Nastar/tomcat/logs using FTP tools to download the log and then analyze it.
Step 4 Run the following command to check the log information recorded by Tomcat.
~> tail -f catalina.out
NOTE
You can navigate to /opt/Nastar/tomcat/logs using FTP tools to download the log and then analyze it.
----End
7.3 Setting Log Templates

By setting log templates, you can save the specific query and statistical conditions in log
templates. This helps you to query and collect statistics on logs conveniently.
Context
The operations for setting the log query and statistic collection templates are similar. The
following is an example of setting the log query template.
Procedure
Step 1 Choose Security > Log Management > Query Operation Logs from the main menu.
Step 2 In the Filter dialog box, click Cancel.
Step 3 You can perform the following operations in the Query Operation Logs window.
Issue 04 (2013-08-30)

75

7 Managing Logs
Task
Operation
Create a template
1. Choose Template Filter > New.

2. In the Enter Template Name dialog box, enter the template name,
and then click OK.
3. In the Filter dialog box, set the filtering conditions of template
parameters, and then click OK.
Modify a template
If there is already a log query template or a log statistics template on

the M2, you can do as follows to modify the template:
1. Choose Template Filter > Open. Select a template in the Open
dialog box, and then click Open.
2. In the Query Operation Logs window, click Filter.
3. In the Filter dialog box, modify the query conditions in the log
template, and then click OK.
4. In the Query Operation Logs window, choose Template Filter >
Save.
Save As
You can do as follows to save and modify a log query or statistics

template:
1. Choose Template Filter > Save As.
2. In the Enter Template Name dialog box, enter the template name,
and then click OK.
Delete a template
If there is already a log query template or a log statistics template on

the M2, you can do as follows to delete the template:
Delete the operations in the template.
1. Choose Template Filter > Delete.
2. In the Delete dialog box, select the specified template, click
Delete.
3. In the Confirm dialog box, click Yes.
----End
7.4 Setting an M2 Log Forwarding Server

You can set an M2 log forwarding server to forward the M2 logs to a third-party server.
Context
The log forwarding server forwards only security logs, operation logs, and system logs.
Issue 04 (2013-08-30)

76

7 Managing Logs
Procedure
Step 1 Choose System > Transmit Log from the main menu.
Step 2 You can perform the following operations in the Log Forwarding Server window.
Task
Operation
Add
In the Create Log Forwarding Server dialog box, set the server that receives
the logs. See 7.6.8 Parameters for Setting a Log Forwarding Server.
NOTE
l To enable the log forwarding function, select Yes from the Enable drop-down list.
l The IP address cannot be set to a loopback address.
l String Filter does not support wildcards.
l The switchover between the primary and secondary servers is supported when the
value of Protocol is TCP. When the primary sever fails, the secondary server takes
over the service and receives the logs. When the primary server is recovered, the
service is switched back to the primary server.
l You can set a maximum of five servers to receive logs.
Modify
In the Log Forwarding Servers dialog box, select a server record, and then
click Modify. In the displayed Modify Log Forwarding Server dialog box,
set the server information of logs.
Delete
In the Log Forwarding Servers dialog box, select a server record, and then
click Delete.
Refresh
After another user updates the information about the log forwarding server,
you can click Refresh to obtain the updated information.
Cancel
To exit the Log Forwarding Server dialog box.
----End
7.5 Managing Log Data

By dumping logs, you can periodically or manually clear the log information that is not required,
preventing the log information from occupying many resources. By exporting logs to files, you
can view logs and identify faults.
7.5.1 Setting M2 Log Dump

By setting M2 log dump, you can periodically or instantly dump security logs, operation logs,
and system logs of the M2. The dumped logs are saved in files and deleted from the database.
This prevents database space insufficiency.
Issue 04 (2013-08-30)

77

7 Managing Logs
Context
Each of the types Operation Log Dump, Security Log Dump and System Log Dump has a
default system task that is provided by the M2. You are not allowed to delete this system task,
but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu.
Step 2 In the Task Type navigation tree, expand the Database Capacity Management node, choose
Operation Log Dump, Security Log Dump or System Log Dump.
Step 3 Double-click the task in the task list.
NOTE
In the task list, right-click the log dump task and choose Run Immediately. The log dump task is performed
instantly.
Step 4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and
Extended Parameters tabs. For the parameter descriptions, see 7.6.9 Parameters for Setting
M2 Log Timing Dump.
Step 5 Click OK.
----End
7.5.2 Setting M2 Log Export

By setting M2 log export, you can periodically or instantly export security logs, operation logs,
and system logs of the M2. The exported logs are saved in files. Thus, they cannot be deleted
from the database.
Context
Each of the types Operation Log Export, Security Log Export and System Log Export has
a default system task that is provided by the M2. You are not allowed to delete the system task,
but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu.
Step 2 In the Task Type navigation tree, expand the File Interface node, choose Operation Log
Export, Security Log Export or System Log Export.
Step 3 Double-click the task in the task list.
NOTE
To perform the operations such as executing an export task instantly, suspending an task, and setting timing
suspending and resuming, right-click the log export task in the right area and choose the corresponding
menus.
Step 4 In the Attribute dialog box, set the parameters on the Common Parameters and Extended
Parameters tabs. For the parameter descriptions, see 7.6.10 Parameters for Setting M2 Log
Timing Export.
Issue 04 (2013-08-30)

78

7 Managing Logs
NOTE
The format of the export files of logs is CSV or XML.
Step 5 Click OK.

----End
7.6 Reference of the Log Management GUI

This topic provides the reference information of the log management GUI.
7.6.1 Security Log List

M2 security logs record security operations that the user performs on the M2. You can find out
insecure operations performed on the M2 by periodically browsing M2 security logs. Browsing
M2 security logs also improves M2 security.
Security log list

Security Event
Risk
Level
Description
User Management
Minor
To implement the function of managing users on the

M2.
Grant user access
Minor
To implement the function of assigning rights to

users on the M2.
Reset Password
Risk
To change the current password. The change takes

effect at the next login.
User Group Management
Minor
To implement the function of managing user groups

on the M2.
Grant usergroup access
Minor
To implement the function of assigning rights to user

groups on the M2.
Force Users to Exit
Risk
To force the user to log out of the M2 if necessary

to ensure network security.
CAUTION
After forcible logout, the user needs to log in to the M2
again.
Issue 04 (2013-08-30)
Edit Security Policy
Risk
To set the password policy and account policy.
Monitor Users
Minor
To monitor user sessions recorded by the M2.

Viewing user operations helps the maintenance
personnel to ensure that the M2 runs normally.
Unlock Users
Minor
To unlock the locked user account.
Security rights
management
Minor
To implement the function of managing security

rights by category on the M2.

79

Issue 04 (2013-08-30)
7 Managing Logs
Security Event
Risk
Level
Description
Object Set Management
Minor
To implement the function of managing object e sets

on the M2.
Operation Set
Management
Minor
To implement the function of managing operation

sets on the M2.
Query Security Logs
Minor
To query security logs.
Security Log template

setting
Minor
To customize the template for querying security

logs. The maintenance personnel can use this
template to conveniently query the same type of
security logs.
Check access
Minor
To implement the function of checking rights on the

M2.
Check combined access
Minor
To implement the function of checking combined

rights on the M2.
Query static information
Minor
To query the static information about the M2.
Log in to the server
Minor
To log in to the M2 server.
Log out the server
Risk
To log out of the M2 server.
Get All Login Session
Minor
To view sessions of all online users of the M2.
Get user login sessions
Minor
To view sessions of M2 online users except

administrators.
Get system mode
Minor
To view the system mode on the M2.
Get session mode
Minor
To view the session mode on the M2.
Get domain information
Minor
To view the domain information on the M2.
Get security object
Minor
To view M2 security objects such as users, user

groups, and objects.
Get access by SO
Minor
To implement the function of inheriting rights by

security object on the M2.
Query domain by SO
Minor
To implement the function of querying domains by

security object on the M2.
Query compressed SO
Minor
To implement the function of querying compressed

security objects on the M2.
Get usergroup
Minor
To implement the function of querying user groups

on the M2.
Get usergroup
information
Minor
To implement the function of querying the

information about user groups on the M2.

80

Issue 04 (2013-08-30)
7 Managing Logs
Security Event
Risk
Level
Description
Get all users
Minor
To implement the function of querying all users on

the M2.
Get access by group
Minor
To inherit rights of the user group. On the M2, a user

can inherit the rights of the user group that the user
belongs to.
Get account information
Minor
To implement the function of querying all user

information on the M2.
Get all usergroup
Minor
To implement the function of querying all user

group information on the M2.
Get users
Minor
To implement the function of querying any users on

the M2.
Get access by user
Minor
To inherit rights of other users on the M2.
Get user name by id
Minor
To obtain a user name by ID on the M2.
Get user id by name
Minor
To obtain an ID by user name on the M2.
NB login
Minor
To access the M2 by using an external user account.
Change password
Risk
To change a user password according to the network

maintenance requirement.
Revert password
Risk
To revert a user password according to the network

maintenance requirement.
Unlock terminal
Minor
To unlock the locked terminal.
Modify user group

description
Minor
To modify the user group description according to

the network maintenance requirement. This helps
the maintenance personnel to quickly understand the
category that the user group belongs to.
Modify user group name
Minor
To modify the user group name according to the

network maintenance requirement. After the
modification, users with the same properties are
merged into the modified user group.
Create user group
Minor
To create a user group. A user group includes users

with similar properties. Creating a user group with
custom permissions achieves the user management
in a centralized manner.
Delete user group
Minor
To delete unnecessary M2 user groups to ensure

security of the network and M2.
Grant rights
Minor
To assign rights to users and user groups according

to the network maintenance requirement. This
facilitates network management.

81

7 Managing Logs
Security Event
Risk
Level
Description
Cancel rights
Minor
To delete rights of users or user groups for M2

applications and devices.
Paste rights
Minor
To implement the function of assigning rights to

other users through rights paste on the M2.
Query access policy
Minor
To implement the function of querying the right

policy on the M2.
Bind user
Minor
To bind operation sets and object sets to a user.
Unbind user
Minor
Unbind objects from a user.
Bind user group
Minor
To bind operation sets and object sets to a user

group.
Unbind user group
Minor
Unbind objects from a user group.
Create user
Minor
To create users according to the network

maintenance requirement and assign different
permissions to users for the purpose of convenient
network management.
Delete user
Risk
To delete unnecessary user accounts for the purpose

of network security. Misoperations and damages
may be caused when invalid users use the disclosed
accounts to log in.
CAUTION
After deleting a user account, you cannot use it to log in
to the M2 except that you have created the same user
account again.
Issue 04 (2013-08-30)
Modify user description
Minor
To implement the function of modifying the user

description on the M2.
Modify user login

duration
Minor
To implement the function of changing the user

login time segment on the M2.
Modify account validity
Minor
To implement the function of modifying accounts

on the M2.
Modify user attribute
Minor
To implement the function of modifying user

attributes on the M2.
Modify account LogOut

Policy
Minor
To implement the function of modifying the account

logout policy (if a user does not perform operations
in a long period, the user is logged out automatically)
on the M2.
Modify password expiry

date
Minor
To implement the function of changing the password

expiry date on the M2.

82

Issue 04 (2013-08-30)
7 Managing Logs
Security Event
Risk
Level
Description
Set user ACLs
Minor
To allow the user to access the M2 by using the

specified IP addresses or IP address segments.
Set security policies
Minor
To set security policies according to the network

maintenance requirement. This ensures that the
M2 runs securely and normally.
Query child domain
Minor
To implement the function of querying child

domains on the M2.
Change user password

valid days
Minor
To implement the function of changing the user

password validity period on the M2.
Modify user password

status
Minor
To implement the function of modifying user

password status on the M2.
Add system ACL
Minor
To add IP addresses or IP address segments to the

system ACL. Users are allowed to access the M2 by
using the specified IP addresses or IP address
segments.
Modify system ACL
Risk
To change IP addresses or IP address segments in

the system ACL. Users are allowed to access the
M2 by using the specified IP addresses or IP address
segments.
Delete system ACL
Minor
To delete IP addresses or IP address segments from

the system ACL.
Create object set
Minor
To plan and create a object set. After you assign the

object set to a user or user group, the user or user
group has the permissions to perform operations on
the objects included in the object set. This helps
assign and manage M2 user permissions in a
centralized manner.
Modify object set name
Minor
To modify a object set name according to the

network maintenance requirement. Objects with the
same properties are merged into the modified object
set.
Modify object set

description
Minor
To modified the object set description according to

the network maintenance requirement. Objects with
the same properties are merged into the modified
object set.
Add object set member
Minor
To add objects to the specified object set according

to the network maintenance requirement.
Delete object set member
Risk
To delete objects from the specified object set

according to the network maintenance requirement.

83

Issue 04 (2013-08-30)
7 Managing Logs
Security Event
Risk
Level
Description
Delete object set
Risk
To delete unnecessary object sets in time.
Bind object set to object

set
Minor
To bind a object set to another object set according

to the network maintenance requirement. The user
does not need to reconfigure properties for object
sets with the same properties.
Unbind object set to

object set
Minor
To unbind a object set from another object set

Create operation set
Minor
To create an operation set. After you assign the

operation set to a user or user group, the user or user
group has the permissions to perform the operations
included in the operation set. This helps assign and
manage M2 user permissions in a centralized
manner.
Modify operation set

name
Minor
To modified an operation set name according to the

network maintenance requirement. Operations with
the same properties are merged into the modified
operation set.
Modify operation set

description
Minor
To modified the operation set description according

to the network maintenance requirement.
Operations with the same properties are merged into
the modified operation set.
Add operation set

member
Minor
To add operations to the specified operation set

Delete operation set

member
Risk
To delete operations from the specified operation set

Delete operation set
Risk
To delete unnecessary operation sets in time.
Bind operation set to

operation set
Minor
To bind an operation set to another operation set

The user does not need to reconfigure properties for
operation sets with the same properties.
Unbind operation set to

operation set
Minor
To unbind an operation set from another operation

set according to the network maintenance
requirement.
Add subresource access

to user group
Minor
To assign a user group the permission to access

subresources.
Delete subresource
access from user group
Minor
To revoke the permission to access subresources

from a user group.
Add subresource access

to user
Minor
To assign a user the permission to access

subresources.

84

7 Managing Logs
Security Event
Risk
Level
Description
Delete subresource
access from user
Minor
To revoke the permission to access subresources

from a user.
Security User
Management
Minor

users on the M2.
Security User Group

Management
Minor

user groups on the M2.
Security Object Set

Management
Minor

object sets on the M2.
Security Operation Set

Management
Minor

operation sets on the M2.
7.6.2 Parameters for Checking Operation Logs

This topic describes the parameters in the Filter dialog box. When checking operation logs, you
can refer to this topic to set the filtering conditions.
Parameters
Parame
ter
Description
Settings
Operatio
n User
Description:
Setting method:
To select operation users for

querying their operation
logs.
In the Filter dialog box, click

. From the Select
Operation User dialog box, select one or more
items.
NOTE
By default, all users' operation logs will be queried.
Operatio
n
Termina
l
Issue 04 (2013-08-30)
Description:
To select operation
terminals. Queried
operation records are
displayed by operation
terminal.
Setting method:
. From the Select
Operation Terminal dialog box, select one or
more items.

85

7 Managing Logs
Parame
ter
Description
Settings
Operatio
n Result
Description:
Value:
To query logs by operation

result.
l Successful means that the operation is complete

and all results are returned.
l Failed means that the operation fails.
l Partially successful means that the operation is
complete and part of operation results are
returned.
l Ongoing means that the operation is being
carried out but results are not yet returned.
l Canceled means that the operation is canceled.
Setting method:
In the Filter dialog box, select one or more items
from the Operation Result group box.
Risk
Level
Description:
Value:
To query logs by risk level.
Warning, Minor, and Risk

Setting method:
In the Filter dialog box, select one or more items
from the Risk Level group box.
Time
Range
Description:
Setting method:
To set the time range within

which the operations
generated can be queried. If
the time range is not set, all
logs generated at any time
are queried.
In the Filter dialog box, select From and To check

box on the left side, and then enter the date and time
NOTE
From means the start time,
and To means the end time.
Example: Set the time range to 02/08/2009

00:00:00-02/09/2009 00:00:00.
directly in the text box, or click

and set the time
in the Date/Time Selection dialog box.
Example:
NOTE
To set the time format, choose File > Preferences from
the main menu, expand Region Settings, and then choose
the Time node. Set Time Format in the area on the right.
When you set the M2 time to DST, the DST check box
is selected automatically.
Issue 04 (2013-08-30)

86

7 Managing Logs
Parame
ter
Description
Settings
Detail
informat
ion
contains
Description:
Setting method:
In the Query Operation

Logs window, you can set
whether to display the
Details column of
operation logs.
In the Filter dialog box, select the Detail

information contains check box, and then enter
the fields to be contained in Details in the text box
that is on the right of the check box.
In Detail information
contains, enter the
information to be displayed
in the Details column. The
M2 filters operation logs
based on the information
provided in Detail
information contains.
Operatio
n Name
Description:
Operatio
n Object
Description:
User
Type
Description:
Start
Time
Description:
End
Time
Description:
Operatio
n
Categor
y
Description:
Details
Description:
To query logs by operation.

object.
Setting method:
corresponding to Operation Name. In the Select
Operation Name dialog box, select one or more
items.
Setting method:
corresponding to Operation Object. In the Select
Operation Object dialog box, select one or more
items.
-
User type of the user that

performs an operation.
-
Start time of an operation.

-
End time of an operation.

-
Category to which an
operation belongs.
-
Details about an operation.

NOTE
The Added by DS log records
in the details is unreliable.
Issue 04 (2013-08-30)

87

7 Managing Logs
7.6.3 Parameters for Collecting Statistics on Operation Logs

This topic describes the parameters in the Filter dialog box. When collecting statistics on
operation logs, you can refer to this topic to set the statistical conditions.
Statistical items
Parameter
Description
Settings
Row
Statistica
l Item
Description:
Value:
To set the row heading of

the statistical result table.
The parameter values include (None),

Operation User, User Type, Operation
Name, Operation Category, Operation
Terminal, Operation Result, and
Operation Object.
Statistica
l Item
Description:
Value:
To set the row heading of

This parameter is the subitem of the preceding
parameter Statistical
Item.
The parameter values include (None),

Operation Object.
Description:
Value:
To set the column heading

of the statistical result
table.
The parameter values include (Count),

Operation Object.
Description:
Value:
To preview the style of the

statistical result table.
Colu
mn
Statistica
l Item
Example
Issue 04 (2013-08-30)
NOTE
You can set at most one of both Statistical
Item in Row to (None). The statistical results are
grouped by Statistical Item.

88

7 Managing Logs
Filter Criteria
Parameter
Description
Settings
Operation
User
Description:
Setting method:
To collect statistics by user.
Click
. In the Select Operation User
dialog box, select one or more items.
NOTE
By default, statistics on all users' operation logs
will be collected.
Operation
Terminal
Description:
Operation
Result
Description:
Value:
To collect statistics by
operation result.
l Successful means that the operation is

being carried out and all results are
returned.
To collect statistics by IP
address of the terminal.
Setting method:
Click
. In the Select Operation
Terminal dialog box, select one or more
items.

l Partially successful means that the
operation is complete but part of
operation results are returned.
l Ongoing means that the operation is
being carried out but results are not yet
returned.
l Canceled means that the operation is
canceled.
Setting method:
From the Operation Result group box,
select one or more items.
Risk Level
Description:
Value:
operation level.
Warning, Minor, and Risk

Setting method:
From the Risk Level group box, select one
or more items.
Issue 04 (2013-08-30)

89

7 Managing Logs
Parameter
Description
Settings
Time
Range
Description:
Setting method:
To collect statistics by time

range.
Select From and To check boxes on the left

side, and then enter the date and time directly
From means the start time, and

To means the end time.
in the text box, or click

and set the time
Example:
00:00:00-02/09/2009 00:00:00.
NOTE
To set the time format, choose File >
Preferences from the main menu, expand
Region Settings, and then choose the Time node.
Set Time Format in the area on the right.
Detail
information
contains
Description:
Setting method:
In the Operation Log

Statistics window, you can set
whether to display the Details
column of operation logs.
Select the Detail information contains

check box, and then enter the fields to be
contained in Details in the text box that is on
the right of the check box.
contains, enter the information
to be displayed in the Details
column. The M2 filters
operation logs based on the
information provided in Detail
Operation
Name
Description:
Operation
Object
Description:
operation.
operation object.
Setting method:
Click
corresponding to
Operation. In the Select Operation Name
Setting method:
Click
corresponding to
Operation Object. In the Select Operation
Object dialog box, select one or more items.
7.6.4 Parameters for Checking System Logs

This topic describes the parameters in the Filter dialog box. When checking system logs, you
Issue 04 (2013-08-30)

90

7 Managing Logs
Parameters
Parameter
Description
Settings
Source
Description:
Setting method:
To select the source of system

logs for query.

. In the Select Source dialog
box, select one or more items.
NOTE
By default, all sources' system logs
will be queried.
Level
Description:
Value:
To query logs by log level.

Setting method:
In the Filter dialog box, select
one or more items from the
Level group box.
Operation Result
Description:
Value:
To query logs by log operation

result.
Failed, Successful, and

Unknown.
Setting method:
one or more items from the
Operation Result group box.
Time Range
Description:
Setting method:
To query logs by time range. If

the time range is not set, all logs
generated at any time are
queried.

From and To check box on the
left side, and then enter the date
and time directly in the text box,
NOTE
From means the start time, and To
means the end time.
and set the time in

or click
the Date/Time Selection dialog
box.
Example:
Example: Set the time range to
02/08/2009
00:00:00-02/09/2009 00:00:00.
NOTE
To set the time format, choose File
> Preferences from the main
menu, expand Region Settings, and
then choose the Time node. Set
Time Format in the area on the
right.
When you set the M2 time to DST,
the DST check box is selected
automatically.
Issue 04 (2013-08-30)

91

7 Managing Logs
Parameter
Description
Settings
Detail information
contains
Description:
Setting method:
In the Query System Logs

window, you can set whether to
display the Details column of
system logs.

the Detail information
contains check box, and then
enter the fields to be contained in
Details in the text box that is on
In Detail information contains,

enter the information to be
displayed in the Details column.
The M2 filters system logs based
on the information provided in
Detail information contains.
Time
Description:
Time for executing a system

operation.
Basic Information
Description:
Basic information about a system

operation.
Details
Description:
Details about a system operation.

NOTE
The Added by DS log records in the
details is unreliable.
7.6.5 Parameters for Collecting Statistics on System Logs

This topic describes the parameters in the Filter dialog box. When collecting statistics on system
logs, you can refer to this topic to set the statistical conditions.
Statistical items
Parameter
Description
Settings
Row
Statistical
Item
Description:
Value:
To set the row heading of the

The parameter values include

(None), Level, and Source.
Statistical
Item
Description:
Value:
To set the column heading of the


(Count), Level, and Source.
Description:
Value:

Colum
n
Example
Issue 04 (2013-08-30)

92

7 Managing Logs
Filter Criteria
Param
eter
Description
Settings
Source
Description:
Setting method:
To collect statistics by source.
Click
. In the Select Source dialog box,
select one or more items.
NOTE
By default, statistics on all sources' system logs
will be collected.
Level
Description:
Value:
To collect statistics by log level.

Setting method:
From the Level group box, select one or more
items.
Operati
on
Result
Description:
Value:
To query logs by log operation

result.
Failed, Successful, and Unknown.

Setting method:
From the Operation Result group box, select
one or more items.
Time
Range
Description:
Setting method:
To collect statistics by time range.

If the time range is not set, all logs
generated at any time are queried.
Select From and To check box on the left

side, and then enter the date and time directly

in the text box, or click

and set the time
Example:
00:00:00-02/09/2009 00:00:00.
NOTE
Preferences from the main menu, expand Region
Settings, and then choose the Time node. Set
Time Format in the area on the right.
Issue 04 (2013-08-30)

93

7 Managing Logs
Param
eter
Description
Settings
Detail
informa
tion
contains
Description:
Setting method:
In the System Log Statistics

system logs.

contained in Details in the text box that is on
In Detail information contains,

enter the information to be
displayed in the Details column.
The M2 filters system logs based
on the information provided in
Detail information contains.
7.6.6 Parameters for Checking Security Logs

This topic describes the parameters in the Filter dialog box. When checking security logs, you
Parameters
Parameter
Description
Settings
Operation
User
Description:
Setting method:
Operation
Terminal
Description:
Operation
Result
Description:
Value:

result.

complete and all results are returned.
To query logs by user.
To query logs by IP address

of the terminal.

. In the
Select Operation User dialog box, select one
or more items.
Setting method:
. In the
Select Operation Terminal dialog box, select
one or more items.

l Partially successful means that the
operation is complete and part of operation
results are returned.
Setting method:
In the Filter dialog box, select one or more
items from the Operation Result group box.
Issue 04 (2013-08-30)

94

7 Managing Logs
Parameter
Description
Settings
Risk Level
Description:
Value:
To query logs by risk level.

Setting method:
In the Filter dialog box, select one or more
items from the Risk Level group box.
Time Range
Description:
Setting method:
To query logs by time range.

If the time range is not set, all
logs generated at any time
are queried.
In the Filter dialog box, select From and To

check box on the left side, and then enter the
date and time directly in the text box, or click
From means the start time,

and To means the end time.
and set the time in the Date/Time

Selection dialog box.
Example:
00:00:00-02/09/2009 00:00:00.
NOTE
To set the time format, choose File > Preferences
from the main menu, expand Region Settings, and
then choose the Time node. Set Time Format in
the area on the right.
Detail
information
contains
Description:
Setting method:
In the Query Security

Logs window, you can set
whether to display the
Details column of security
logs.
In the Filter dialog box, select the Detail

information contains check box, and then
enter the fields to be contained in Details in
the text box that is on the right of the check
box.
contains, enter the
information to be displayed
in the Details column. The
M2 filters security logs
based on the information
provided in Detail
Security
Event
Issue 04 (2013-08-30)
Description:
Setting method:
To query logs by security

event.

corresponding to Security
Event. In the Select Security Event dialog
box, select one or more items.

95

7 Managing Logs
Parameter
Description
Settings
Operation
Object
Description:
Setting method:
To query data by operation

object.
Description:
User Type
corresponding to Operation
Object. In the Select Operation Object
User type of the user that

performs a security event.
Operation
Time
Description:
Details
Description:
Time for executing a

security event.
-
Details about a security

event.
7.6.7 Parameters for Collecting Statistics on Security Logs

This topic describes the parameters in the Filter dialog box. When collecting statistics on security
logs, you can refer to this topic to set the statistical conditions.
Statistical items
Issue 04 (2013-08-30)
Parameter
Description
Settings
Row
Description:
Value:


(None), Operation User, User
Type, Security Event, Operation
Terminal, Operation Result,
Operation Object, and Risk
Level.
Statistica
l Item

96

7 Managing Logs
Parameter
Statistica
l Item
Description
Settings
Description:
Value:

statistical result table. This
parameter is the sub-item of the
preceding parameter Statistical
Item.

(None), Operation User, User
Level.
NOTE
You can set at most one of both
Statistical Item in Row to (None). The
statistical results are grouped by
Statistical Item.
Column
Statistica
l Item
Example
Description:
Value:
To set the column heading of


(Count), Operation User, User
Level.
Description:
Value:

Filter Criteria
Issue 04 (2013-08-30)
Parameter
Description
Settings
Operation
User
Description:
Setting method:
Operation
Terminal
Description:
To collect statistics by user.
To collect statistics by IP
address of the terminal.
Click
. In the Select Operation User
Setting method:
Click
. In the Select Operation
Terminal dialog box, select one or more
items.

97

7 Managing Logs
Parameter
Description
Settings
Operation
Result
Description:
Value:
To collect statistics by operation

result.

complete and all results are returned.
l Partially successful means the
operation is complete, and some
operation results are returned.
Setting method:
In the Result area, select one or more
items.
Risk Level
Description:
Value:
To collect statistics by risk level.

Setting method:
From the Risk Level group box, select
one or more items.
Time Range
Description:
Setting method:
To collect statistics by time

range. If the time range is not
specified, all logs generated at
any time are queried.
Select From and To check box on the left

side, and then enter the date and time

directly in the text box, or click

and
set the time in the Date/Time Selection
dialog box.
Example:
Example: Set the time range to
02/08/2009 00:00:00-02/09/2009
00:00:00.
NOTE
Preferences from the main menu, expand
Region Settings, and then choose the Time
node. Set Time Format in the area on the
right.
Detail
information
contains
Description:
Setting method:
In the Security Log Statistics

security logs.

contained in Details in the text box that is
on the right of the check box.
contains, enter the information
to be displayed in the Details
column. The M2 filters security
logs based on the information
provided in Detail information
contains.
Issue 04 (2013-08-30)

98

7 Managing Logs
Parameter
Description
Settings
Security
Event
Description:
Setting method:
Operation
Object
Description:
To collect statistics by security

event.
To collect statistics by operation

object.
Click
corresponding to
Security Event. In the Select Security
Event dialog box, select one or more
items.
Setting method:
Click
corresponding to
Operation Object. In the Select
Operation Object dialog box, select one
or more items.
7.6.8 Parameters for Setting a Log Forwarding Server

This topic describes the parameters for setting a log forwarding server. When setting a log
forwarding server, you can refer to this topic to perform setting.
Parameters
Parameter
Description
Settings
Master Server
IP Address
Description:
Master Server
Port
Description:
Value:
Port number of the primary server

that receives forwarded logs.
Value range: 1-65535.
Standby Server
IP Address
Description:
Standby Server
Port
Description:
Value:
Port number of the secondary

server that receives forwarded logs.
Value range: 1-65535.
Protocol
Description:
Value:
Protocol for log forwarding.
Value range: TCP or UDP.
Description:
Value:
Whether to enable the server to

receive forwarded logs.
Value range: Yes or No.
Enable
Issue 04 (2013-08-30)
IP address of the primary server.

The server receives the logs
forwarded by the M2.
IP address of the secondary server

that receives forwarded logs.

99

7 Managing Logs
Parameter
Description
Settings
Syslog Level
Level of the logs to be forwarded.
Value range: Emergency, Alert,

Critical, Error, Warning, Notice,
Informational, and Debug.
NOTE
The mapping between the M2 log level
and the Syslog level is: risk-critical,
minor-warning, warning-notice. If you
need to forward the M2 log of the Risk
level, click
on the right, and select
Critical in the Syslog Level Selection
dialog box.
String Filter
Description:
Value:
A log is forwarded only when the

log contains the specified string.
Value range: 0-50

Unit: character
Default: None
Remark
Description:
Value:
Remarks on the log forwarding

server.
Value range: 0-255

Unit: character
Default: None
State
Description:
State of the connection between the

M2 and the third-party Syslog
server. The state can be Connect,
Disconnect, or Unkonwn. If the
Enable parameter for the server is
set to No, the connection between
the M2 and the third-party Syslog
server is in the Unkonwn state.
When the Enable parameter for the
server is set to Yes, the Connect
state indicates that the M2 can
properly communicate with the
third-party Syslog server, and the
Disconnect state indicates that the
M2 fails to communicate with the
third-party Syslog server.
7.6.9 Parameters for Setting M2 Log Timing Dump

This topic describes the parameters for setting M2 log timing dump in the centralized task
management. When you set log timing dump, you can refer to this topic to perform setting.
Issue 04 (2013-08-30)

100

7 Managing Logs
Common Parameters
Table 7-1 Parameters Applicable for both One-time and Periodic Tasks
Parameter
Description
Settings
Task name
Description:
Value:
Refers to the name of a timing task.
l A maximum of 64 bytes.
l Unique and not null.
l Case sensitive.
Execution
type
Description:
Value:
l One-time: If you select this

option, the system runs the
created task once at the defined
time point.
l One-time
l Periodic: If you select this

created task periodically.
Start time
l Periodic
NOTE
The execution type cannot be configured
again after the task is created.
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 immediately, the Start
time parameter is invalid. The task is
performed immediately after the related
settings are complete.
During the DST, if you select DST, the

specified time uses the DST standard.
NOTE
At other time except DST, the option
DST is unavailable.
Task type
Description:
Refers to the type of a timing task.
Issue 04 (2013-08-30)

101

7 Managing Logs
Table 7-2 Parameters Only Applicable for Periodic Tasks

Parameter
Description
Settings
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. Second is not supported.
The supported units of Period vary
according to the task type.
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
The execution interval cannot be
configured again after a dump task is
created.
Execution
Times
Description:
Value:
This parameter indicates the times

that a periodic task is executed.
0 - 65535
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
l 0 indicates that the number of times
for executing periodic tasks is not
restricted.
l The execution times cannot be
configured again after the task is
created.
Description:
Value:
End time of a periodic task.
Later than Start time, and earlier than

01/18/2038 11:14:07.
NOTE
periodic task.
NOTE
The end time cannot be configured again
after the task is created.

NOTE
DST is unavailable.
Issue 04 (2013-08-30)

102

7 Managing Logs
Extended Parameters
Table 7-3 Extended Parameters
Parameter
Description
Setting
Compress
file after
export
Description:
Value:
This parameter is used to set whether compress files

after dumping. If yes, export files will be
compressed to a .zip file. After compression, the
source files are deleted.
Yes or No
File type
Description:
Value:
This parameters indicates the format of the dump

files of logs.
Value range: CSV,

XML, TXT or HTML.
Description:
Value:
This parameter indicates that dump log files are

saved to the specified path on the server.
Value: a specified path
Storage
period in
database
(days)
Description:
Value:
When a dump task is executed, the logs older than

this period are dumped.
Value range: 1-180.
Export File
Managemen
t
Description:
Value:
l Hold files for XX days: In the dump directory,

the log files older than this period are deleted.
l The value range of

Hold files for XX
days is 1-180.
File path
l Hold max. XX files: In the dump directory, if

the number of log files exceeds the value of this
parameter, the M2 deletes the oldest dump files
until the number of log files in this directory
becomes less than the value of this parameter.
l Hold max. XX MB file data: In the dump
directory, if the total size of log files exceeds the
value of this parameter, the M2 deletes the
oldest dump files until the total size of log files
in this directory becomes less than the value of
this parameter.
Rule: It is not
recommended to
change the default file
path. If you need to
specify a new file path,
ensure that the user
imapuser has
permission to read and
write the target folder
under this path.
Default value: 30.
Default value: 15.

Hold max. XX files
is 200-2000.
Default value: 1000.
Hold max. XX MB
file data is
200-4096.
Issue 04 (2013-08-30)

103

7 Managing Logs
7.6.10 Parameters for Setting M2 Log Timing Export

This topic describes the parameters for setting M2 log timing export in the centralized task
management. When you set log timing export, you can refer to this topic to perform setting.
Common Parameters
Table 7-4 Parameters Applicable for both One-time and Periodic Tasks
Parameter
Description
Settings
Task name
Description:
Value:
Refers to the name of a timing task.
l A maximum of 64 bytes.
l Unique and not null.
l Case sensitive.
Execution
type
Description:
Value:
l One-time: If you select this

created task once at the defined
time point.
l One-time
l Periodic: If you select this

created task periodically.
Start time
l Periodic
NOTE
The execution type cannot be configured
again after the task is created.
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 immediately, the Start
time parameter is invalid. The task is
performed immediately after the related
settings are complete.

NOTE
DST is unavailable.
Task type
Description:
Refers to the type of a timing task.
Issue 04 (2013-08-30)

104

7 Managing Logs
Table 7-5 Parameters Only Applicable for Periodic Tasks

Parameter
Description
Settings
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. Second is not supported.
The supported units of Period vary
according to the task type.
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
The execution interval cannot be
configured again after a dump task is
created.
Execution
Times
Description:
Value:
This parameter indicates the times

that a periodic task is executed.
0 - 65535
NOTE
periodic task.
End time
NOTE
l 0 indicates that the number of times
for executing periodic tasks is not
restricted.
l The execution times cannot be
configured again after the task is
created.
Description:
Value:
End time of a periodic task.
Later than Start time, and earlier than

01/18/2038 11:14:07.
NOTE
periodic task.
NOTE
The end time cannot be configured again
after the task is created.

NOTE
DST is unavailable.
Issue 04 (2013-08-30)

105

7 Managing Logs
Extended Parameters
Table 7-6 Extended Parameters
Parameter
Description
Setting
Compress
file after
export
Description:
Value:
This parameter is used to set whether compress

export files. If yes, export files will be
compressed to a .zip file. After compression, the
source files are deleted.
Yes or No
Export File
Type
Description:
Value:
This parameters indicates the format of the

export files of logs.
Value range: CSV, XML,

TXT or HTML.
File path
Description:
Value:
This parameter indicates that export log files are

saved to the specified path on the server.
Value: a specified path
Description:
Value:
l Hold files for XX days: In the export

directory, the log files older than this period
are deleted.

Hold files for XX
days is 1-180.
Export File
Managemen
t
l Hold max. XX files: In the export directory,

if the number of log files exceeds the value
of this parameter, the M2 deletes the oldest
export files until the number of log files in
this directory becomes less than the value of
this parameter.
l Hold max. XX MB file data: In the export
directory, if the total size of log files exceeds
the value of this parameter, the M2 deletes
the oldest export files until the total size of
log files in this directory becomes less than
the value of this parameter.
Issue 04 (2013-08-30)

Rule: It is not
recommended to change
the default file path. If you
need to specify a new file
path, ensure that the user
imapuser has permission to
read and write the target
folder under this path.
Default value: 15.

Hold max. XX files is
200-2000.
Hold max. XX MB file
data is 200-4096.
106

Managing Processes and Services
About This Chapter

This chapter describes how to manage the system processes and services of M2, SAU, eSAU,
and Agent Server.
8.1 Managing M2 Processes and Services
This section describes how to manage M2 processes to ensure that M2 processes and services
are running properly.
8.2 Managing the Agent Server Processe and Service
This section describes how to manage Agent Server processes to ensure that Agent Server
processes and services are running properly.
Issue 04 (2013-08-30)

107

8.1 Managing M2 Processes and Services

This section describes how to manage M2 processes to ensure that M2 processes and services
are running properly.
8.1.1 M2 Server Services and Processes

This section describes the M2 Server processes and services of the M2 system. When the M2
system is running properly, the M2 server starts the processes related to the M2 Server. Each
process provides distinct services and functions.
Table 8-1 lists the services and functions provided by the running processes related to the M2
Server when the M2 system is running properly.
Table 8-1 Services and functions provided by the running processes related to the M2 Server
Service
Process
Name
Description
DesktopS
ervice010
1
ds0101_age
nt
l The DesktopService0101 service can display and operate

data on several types of clients. The multiple desktop services
that are deployed can share the access pressure of multiple
clients on the server.
l You must start this service.
l Required services: none.
EAMServ
ice
eam_agent
l The EAMService service provides the function of NE access

management and maintains a globally complete NE list.
l The process is independent and can be started as required.
l Ruired services: none.
EmfGnlD
evDm
EmfGnlDev
Dm
l The EmfGnlDevDm service provides the function of

managing common devices of third-party NEs.
ItmServic
e
itm_agent
l The ItmService service provides the function of centralized

task management.
LicenseSe
rvice
lic_agent
l The LicenseService service provides a service interface that

is used to check the validity of the license file of the current
version.
l You must start this service. Once it starts, you must not stop
it.
Issue 04 (2013-08-30)

108

Service
Process
Name
Description
LogServic
e
log_agent
l The LogService service records the system-related

information in files. You can query the system operation logs
on the client.
Forwardin
gService
l The ForwardingService service reads the log information in

the format of syslog from the database and forwards the log
information to a third-party Syslog server in the format of
RFC3164 UDP or RFC3195 TCP.
l You can start this service as required.
SystemSe
rvice
manager_ag
ent
l The SystemService service enables you to query the M2

version information such as the version of the operating
system, software version of the client, software version of the
server, and client upgrade information.
it.
Maintena
nceServic
e
maintain_ag
ent
l The MaintenanceService service enables the periodic

backup of the important system configuration files, database
data, and real-time data of MOs. In the ATAE cluster system,
you can distribute this process to different slave nodes.
it.
Mediation
Service01
01
med_agent
l The MediationService0101 service creates, deletes, and

obtains the NE engines mirrored to the network devices from
the M2 system and also manages the related event
interceptors. The NEs using various network management
protocols can communicate with the M2 system by using the
corresponding NE engines.
it.
l Required service: PartitionService.
Common
LicServic
e
SSLMana
geService
necomm_ag
ent
l The CommonLicService service manages the information

about NE license files, such as invalidity, export, and
adjustment information.
l The SSLManageService service manages the SSL
connections between the M2000 and NEs. It also manages the
SSL certificates used by the SSL connections.
l The SSLManageService service depends on
CommonLicService service.
Issue 04 (2013-08-30)

109

Service
Process
Name
Description
CAServic
e
CAService_
agent
l The CAService service provides the function of handling user

complaints.
PartitionS
ervice
partition_ag
ent
l The PartitionService service divides the managed objects

into different partitions. All the partitions are managed by
different processes. The processes are deployed on different
servers so that the load is balanced when there are large
number of managed objects.
it.
PortTrunk
ingServic
e
porttrunk_a
gent
l The PortTrunkingService service can converge all the

service ports of the M2 to enable all them to be presented as
a single port to the firewall. You can configure the port so the
firewall port can be configured easily.
l When using a fixed port to traverse the firewall, ensure that
the service mapping to this port is started, and the service
cannot be stopped.
SecurityS
ervice
sm_agent
l The SecurityService service controls the access rights to all

sensitive resources in the element management system
(EMS). Only authorized users can access these resources. The
service controls the access of resources by controlling the user
operation rights.
it.
l Required services: LogService and LicenseService.
8.1.2 Checking M2 Server Service Status

This section describes how to check the status of M2 Server services. This operation requires
few system resources and does not affect system operation.
Procedure
Step 1 Log in to the server as user omcuser and navigate to the installation directory of the M2 server
software (the default installation directory is /opt/Nastar).
~> cd /opt/Nastar
Issue 04 (2013-08-30)

110

NOTE
omcuser.
Step 2 Run the following commands to view M2 Server service status:

~> svc_adm -cmd status
The command output similar to the following information is displayed:
l In the command output, if the service status is Running, the service is running properly.
l In the command output, if the service status is Not Running, the service is not started.
l In the command output, if the service status is No License, the service is not registered.
NOTE
The M2 may dynamically generate processes and services when it is running. The number of processes
and services queried each time may be different.
----End
8.1.3 Starting M2 Server Services

This section describes how to run the start_svc command to start all the M2 services. The system
does not process the M2 services that are already started but starts only the M2 services that are
not running.
Prerequisites
The Oracle database services are running normally. For details on how to start the Oracle
database service, see 9.1.2 Checking Oracle Database Running Status.
Procedure
Step 1 Log in to the server as user omcuser, and then run the following command to navigate to the
installation directory of the M2 server software (the default installation directory of the M2
server software is /opt/Nastar):
~> cd /opt/Nastar
NOTE
l If you are required to type a password after the su - omcuser command is run, type the password of
user omcuser.
Step 2 Run the following commands to start the M2 services:

Issue 04 (2013-08-30)

111

~> start_svc
Step 3 Run the following commands to start the Tomcat service:
~> cd tomcat
~> ./service.sh start
Step 4 Check whether all M2 services are started. For detailed operations, see 12.2.10 Checking M2
Service Status.
----End
8.1.4 Stopping M2 Server Services

This section describes how to use commands to stop M2 Server services.
Procedure
~> cd /opt/Nastar
NOTE
user omcuser.
Step 2 Run the following commands to stop the M2 Server services.

~> stop_svc
Step 3 Run the following command to check whether the service processes are stopped:
~> svc_ps
l If no command result is displayed, the service processes are stopped.
l If any command result is displayed, run the kill_svc command to forcibly stop the running
service processes.
Step 4 Run the following command to stop the daemon process:
~> stop_daem
Step 5 Run the following command to check whether the daemon process is stopped:
~> daem_ps
l If no command result is displayed, the daemon process is stopped.
l If any command result is displayed, run the kill_daem command to forcibly stop the daemon.
Step 6 Run the following command to check whether the TAO process is stopped:
Issue 04 (2013-08-30)

112

~> ps -ef |grep 9999 |grep -v grep

l If no command result is displayed, the TAO process is stopped.
l If any command result is displayed, run the stop_tao_services command to forcibly stop the
TAO process.
----End
8.1.5 SAU Services and Processes

This section describes the functions provided by SAU services and processes.
When the server is running properly, the processes related to the SAU software start and stop
according to the SAU services. Each process corresponds to a unique service and provides
different functions. Table 8-2 describes SAU services and processes.
Table 8-2 SAU services and processes
Service
Process
Name
Description
Monitor
sf_monitor
l Interception process, which monitors the running status

of SAU processes.
l Service must be started.
l Required service: none.
PSau.Controll
er
sf_env
l Service process, which allows users to upload data to

the eSAU.
l This service must be started.
l Required service: Monitor.
SysMonitor0
sf_env
l Interception process, which monitors the status of the

SAU.
PSau.Calculat
or1
sf_env
l Service process, which converts the data source format

to MCounter format.
PSau.Collecto
r0
sf_env
l Service process, which allows users to collect raw data.

8.1.6 Checking SAU Service Status

This section describes how to check the status of SAU services.
Issue 04 (2013-08-30)

113

Procedure
Step 2 Run the following commands to check SAU services:
~> cd /opt/PSSAU
~> ps_query
When the following or similar information is displayed, SAU services are running.
Service Agent: PSau.Calculator [1 service(s)] pid: 24663
PSau.Calculator
[running]
Service Agent: PSau.Collector [1 service(s)] pid: 24692
PSau.Collector
[running]
Service Agent: PSau.Controller [1 service(s)] pid: 24556
PSau.Controller
[running]
Service Agent: SysMonitor [1 service(s)] pid: 24589
SysMonitor
[running]
[All Services: 4 ] [Running: 4] [Not Running: 0 ]
l In the displayed information, if the state of the service is Running, you can infer that the
service operate properly.
l In the displayed information, if the state of the service is Not Running, you can infer that
the service is abnormal.
l At the end of the displayed information, if the value of Not Running is 0, you can infer that
all the SAU services operate properly. Otherwise, some SAU services have not been started.
----End
8.1.7 Starting SAU Services

This section describes how to start SAU services.
Prerequisites
Oracle database services are started. For details about the running status of Oracle database
services, see 9.1.2 Checking Oracle Database Running Status.
Procedure
Step 2 Run the following commands to start SAU services:
~> cd /opt/PSSAU
~> ps_start
Step 3 Check whether all SAU services are started. For detailed operations, see 12.2.11 Checking SAU
Service Status.
----End
Issue 04 (2013-08-30)

114

8.1.8 Stopping SAU Services

This section describes how to stop the SAU services.
Context
NOTE
Check that no preprocessing tasks are running before you stop SAU services. Otherwise, preprocessing
result might be incorrect.
Procedure
Step 2 Run the following commands to stop the SAU services:
~> cd /opt/PSSAU
~> ps_stop
Step 3 Run the following command to ensure that all SAU services have stopped:
~> ps_query
l If no command output is displayed, the SAU services have stopped.
l If any command output is displayed, run the ps_kill command to forcibly stop the services.
----End
8.1.9 eSAU Services and Processes

This section describes the functions provided by the eSAU services and processes.
When the server is running properly, the processes related to the eSAU software start and stop
according to the eSAU services. Each process corresponds to a unique service and provides
different functions. Table 8-3 describes the eSAU services.
Table 8-3 eSAU services and processes
Service
Process
Name
Description
Monitor
sf_monitor
l Interception process. It provides the function of monitoring

the status of eSAU processes.
l Required service: none.
Issue 04 (2013-08-30)

115

Service
Process
Name
Description
eSAU
sf_env
l Service process. It provides services of querying multidimension data, and collecting Counter data and saving it
to the database.
SysMonitor
SysMonitor
l Interception process. It provides the function of monitoring

the eSAU system.
8.1.10 Checking eSAU Service Status

This section describes how to check the status of eSAU services.
Procedure
Step 2 Run the following commands to view eSAU service status:
~> cd /opt/esau
~> esau_ps
When the following or similar information is displayed, eSAU services are running.
Monitor...........................running
eSAU...........................running
SysMonitor.....................running
[All Services: 3] [Running: 3] [Not Running: 0 ]
l In the displayed information, if the state of the service is Running, you can infer that the
service operate properly.
l In the displayed information, if the state of the service is Not Running, you can infer that
the service is abnormal.
l At the end of the displayed information, if the value of Not Running is 0, you can infer that
all the eSAU services operate properly. Otherwise, some eSAU services have not been
started.
----End
8.1.11 Starting eSAU Services

This section describes how to start eSAU services.
Issue 04 (2013-08-30)

116

Prerequisites
Oracle services are started. For details about the running status of Oracle services, see 9.1.2
Checking Oracle Database Running Status.
Procedure
Step 2 Run the following commands to start eSAU services:
~> cd /opt/esau
~> esau_start
Step 3 Check whether all eSAU services are started. For detailed operations, see 12.2.12 Checking
eSAU Service Status.
----End
8.1.12 Stopping eSAU Services

This section describes how to stop the eSAU services.
Context
NOTE
Before stopping the eSAU services, ensure that no data aggregation task is running. Otherwise, an exception
may occur during the task execution, which causes the data exception.
Procedure
Step 2 Run the following commands to stop the eSAU services:
~> cd /opt/esau
~> esau_stop
Step 3 Run the following command to ensure that all eSAU services have stopped:
~> esau_ps
eSAU...............................not running
l If the value of Running is 0, eSAU services are stopped.

Issue 04 (2013-08-30)

117

l If the value of Running is not 0, run esau_kill to forcibly stop eSAU services.
----End
8.2 Managing the Agent Server Processe and Service

This section describes how to manage Agent Server processes to ensure that Agent Server
processes and services are running properly.
8.2.1 Agent Server Services and Processes

This section describes the functions provided by the Agent Server services and processes.
When the server is running properly, the processes related to the Agent Server software start
and stop according to the Agent Server services. Each process corresponds to a unique service
and provides different functions. Table 8-4 describes the Agent Server services.
Table 8-4 Agent Server services and processes
Service
Process Name
Description
Tomcat
tomcat
Web server that Agent Server relies on. HTTPS

services are provided to the agent and Client after the
tomcat service is started.
This service must be started.
Required service: none.
8.2.2 Checking Agent Server Service Status

This section describes how to check the status of Agent Server services. Check the service status
on the Agent Server consumes occupies few system resources and does not affect the system
running.
Procedure
NOTE
omcuser.
Step 2 Run the following commands to check the Tomcat service:

~> cd /opt/Nastar
~> cd tomcat
Issue 04 (2013-08-30)

118


If the following information is displayed, the Tomcat service is started successfully.
service is running.
----End
8.2.3 Starting the Agent Server Service

This section describes how to start Agent Server service.
Procedure
~> cd /opt/Nastar
NOTE
user omcuser.
Step 2 Run the following commands to start the Tomcat service:

~> cd /opt/Nastar/tomcat
~> . service.sh start
When the following or similar information is displayed, Tomcat service is running.
service starting...
service startup successful.
----End
8.2.4 Stopping the Agent Server Service

This section describes how to stop the Agent Server service.
Procedure
~> cd /opt/Nastar
Issue 04 (2013-08-30)

119

NOTE
user omcuser.
Step 2 Run the following commands to stop the Tomcat service:

When the following or similar information is displayed, Tomcat service is stopped.
service stopping...
----End
Issue 04 (2013-08-30)

120

Managing Databases
About This Chapter

This chapter describes how to manage the M2 databases. It also describes the procedures for
checking the database status of M2 and Agent Server.
9.1 Managing Oracle Databases
This section describes how to manage the Oracle database of M2. It also describes the procedures
for checking the database status.
9.2 Managing GaussDB Database
This section describes how to manage the GaussDB database of Agent Server. It also describes
the procedures for checking the database status.
Issue 04 (2013-08-30)

121

9.1 Managing Oracle Databases

This section describes how to manage the Oracle database of M2. It also describes the procedures
for checking the database status.
9.1.1 M2 System Databases

The system database of M2 is Oracle.
Table 9-1 describes the M2 databases.
Table 9-1 M2 system database
Database
Function
imap_db schema
Stores system related data. The database requires at least 1000 MB

data space.
imapeamdb schema
Stores the data about NE access management. The database requires

at least 500 MB data space.
imaplogdb schema
Stores system log data. The database requires at least 500 MB data
space.
imapsmdb schema
Stores security management data. The database requires at least 400

MB data space.
9.1.2 Checking Oracle Database Running Status

This section describes how to check Oracle database running status.
Prerequisites
You have installed the Oracle database system.
Procedure
Step 2 Run the following command to check whether Oracle database services are started:
# ps -fu oracle
UID PID PPID
Oracle 5141 1
....
Oracle 5157 1
...
Oracle 5165 1
Oracle 5167 1
Oracle 5169 1
...
Issue 04 (2013-08-30)
C STIME TTY TIME CMD

0 21:36 ? 00:00:00 ora_pmon_imapdb
0 21:36 ? 00:00:00 ora_dbw0_imapdb
0 21:36 ? 00:00:00 ora_lgwr_imapdb
0 21:36 ? 00:00:00 ora_ckpt_imapdb
0 21:36 ? 00:00:00 ora_smon_imapdb

122

Oracle 5197 1 0 21:36 ? 00:00:00 ora_arc0_imapdb

...
/opt/oracle/oradb/home/bin/tnslsnr LISTENER -inherit
l If the command result contains at least the following six processes, Oracle database services
and listening services are running normally.
ora_pmon_ imapdb
ora_dbw0_ imapdb
ora_lgwr_ imapdb
ora_ckpt_ imapdb
ora_smon_ imapdb
/opt/oracle/oradb/home/bin/tnslsnr
l If no command output is displayed, Oracle database services are not started properly. Start
database services by referring to 9.1.3 Staring Oracle.
----End
9.1.3 Staring Oracle

This section describes how to start Oracle database services.
Procedure
Step 1 Check whether Oracle database services are started. For detailed operations, see 9.1.2 Checking
Oracle Database Running Status.
Skip the following steps if Oracle database services are started; if not, perform the following
steps to start the services.
Step 2 Log in to the server as user oracle.
If you log in to the server as another user, you can run the su - oracle command to switch to
user oracle.
Step 3 Run the following commands to start the Oracle database service.
~> sqlplus / as sysdba
SQL> startup
l If the following or similar information is displayed, the database is started properly.
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.
l If the following information is displayed, the database has started.

ORA-01081: cannot start already-running ORACLE - shut it down first
Step 4 Run the following command to exit the SQL.

SQL> exit
Step 5 Run the following command to start the database listener:
Issue 04 (2013-08-30)

123

~> lsnrctl start

l If the command result contains the following information, the database listener is started
successfully.
The command completed successfully
l If the command result contains the following information, the database listener has started.
Listener using listener name LISTENER has already been started
Step 6 Run the following command to exit the user oracle.

~> exit
----End
9.1.4 Stopping Oracle

This section describes how to stop Oracle database services.
Context
CAUTION
Check that M2 services and eSAU services are stopped before you stop Oracle database services.
Procedure
Step 1 Check that M2 services are stopped.
1.
Check M2 service status. For detailed operations, see 8.1.2 Checking M2 Server Service
Status.
2.
If M2 services are running, stop M2 services. For detailed operations, see 8.1.4 Stopping
M2 Server Services.
Step 2 Check that eSAU services are stopped.

1.
Check eSAU service status. For detailed operations, see 8.1.10 Checking eSAU Service
Status.
2.
If eSAU services are running, stop eSAU services. For detailed operations, see 8.1.12
Stopping eSAU Services.
Step 3 Run the following commands to stop the database listener:

# su - oracle
~> lsnrctl stop
l If information similar to the following is displayed, the database listener is stopped.
The command completed successfully
l If information similar to the following is displayed, the database listener has been stopped
before you run this command.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=nassvr)(PORT=1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
Issue 04 (2013-08-30)

124

TNS-00511: No listener
Linux Error: 111: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 2: No such file or directory
Step 4 Run the following commands to stop the database services:

~> sqlplus / as sysdba
SQL> shutdown immediate
l If the following information is displayed, the database is stopped.
Database closed.
Database dismounted.
ORACLE instance shut down.
l If the following information is displayed, the database has been stopped before you run this
command.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
l If the following information is displayed, the database is also stopped.

ORA-01012: not logged on
Step 5 Run the following command to exit the SQL.

SQL> exit
Step 6 Run the following command to exit user oracle.
~> exit
----End
9.2 Managing GaussDB Database

This section describes how to manage the GaussDB database of Agent Server. It also describes
the procedures for checking the database status.
9.2.1 Agent Server System Database

The system database of Agent Server is GaussDB.
Table 9-2 describes the Agent Server database.
Table 9-2 Agent Server system database
Issue 04 (2013-08-30)
Database
Function
GaussDB
It is the database of Agent Server and is used to save configuration

data.

125

9.2.2 Checking GaussDB Database Running Status

This section describes how to check GaussDB database status.
Prerequisites
You have installed the GaussDB database system.
Procedure
NOTE
Step 2 Run the following command to check whether GaussDB database services are started:
~> gs_ctl query
Ha state:
LOCAL_ROLE
STATIC_CONNECTIONS
DB_STATE
DETAIL_INFORMATION
:
:
:
:
Normal
0
Normal
Normal
----End
9.2.3 Starting GaussDB

This section describes how to start GaussDB database services.
Procedure
NOTE
Step 2 Run the following command to start GaussDB database services:

~> gs_ctl start -l db.log -D /opt/gaussdb/data
server starting.... done
server started
----End
9.2.4 Stopping GaussDB

This section describes how to stop GaussDB database services.
Issue 04 (2013-08-30)

126

Procedure
NOTE
Step 2 Run the following command to stop GaussDB database services:

~> gs_ctl stop -m fast
If the information similar to the following is displayed, GaussDB database services are stopped.
waiting for server to shut down.... done
server stopped
----End
Issue 04 (2013-08-30)

127

10
Managing Files and Disks
About This Chapter

This chapter describes how to manage the file system and disks of the server.
10.1 Clearing Up the Disk Space for the Server
Before clearing up the disk, you need to ensure that the files you want to delete are not required
for future operations. Deleting useful files by mistake may lead to improper system running.
10.2 Clearing Up the Disk Space for the Client
This section describes how to clear up the disk space for M2 so that more free disk space is
available.
Issue 04 (2013-08-30)

128

10.1 Clearing Up the Disk Space for the Server

Context
During the routine operation and maintenance, back up and delete the following files:
l
Files containing the information about the M2 server
Software upgrade packages and decompressed files
Trace logs
Temporary files created during system operation
CAUTION
You can delete files when the server is running. Before deleting files, run the ls -l command to
check the time when the files were generated. Do not delete the files generated on the current
day.
Procedure
Step 1 Export the files containing the information about the M2 server and back up the files to a local
hard disk.
The following files are included:
l User log files
User log dump files are saved in the /opt/Nastar/var/userlogs/ directory.
l Core files generated by the system
Core files are saved in the /opt/Nastar/var/logs, /opt/esau/var/logs, and /opt/PSSAU/var/
logs directories.
l History trace files
Historical trace files are saved in the /opt/Nastar/var/logs/tracebak, /opt/esau/var/logs/
backup, and /opt/PSSAU/var/logs/backup directories.
Step 2 Delete M2 software upgrade packages and decompressed files.
After the software is successfully upgraded, you can delete the original upgrade packages and
the decompressed files. The upgrade packages and decompressed files are stored in a directory
that is named after the upgrade patch in the /export/home/M2update directory.
Step 3 Perform the following substeps to delete the trace logs of M2 services.
1.
Run the following command to edit the tracemonitor_svc_ex.xml file:

# vi /opt/Nastar/etc/conf/tracemonitor_svc_ex.xml
Issue 04 (2013-08-30)

129

2.
Press i to start editing.
3.
Change the value of tracebackupnum in the tracemonitor_svc_ex.xml file to decrease

trace backup files.
Edit the tracemonitor_svc_ex.xml file in the /opt/Nastar/etc/conf/ directory to set the
trace log monitoring period, size limit, and number of backup files. /opt/Nastar is the default
installation directory of the M2 server software.
You can change the value of checktracetime to set the period for monitoring the trace log.
You can change the value of tracebackupnum to set the number of backup trace files for
each process in the /opt/Nastar/var/logs/tracebak directory. The system checks the trace
file every 300 seconds. If the number of trace files corresponding to one process in the
tracebak directory exceeds the preset value, the system deletes the earliest trace files in
sequence.
The content of the tracemonitor_svc_ex.xml file 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>
4.
Press Esc after the change is complete. Run the command :wq! and press Enter to save
the change and exit the vi editor.
Step 4 Perform the following substeps to delete the trace logs and processed files of eSAU:
1.
Run the following command to edit the configuration file:

# vi /opt/esau/etc/FileManagerConfig.xml
2.
3.
Modify the saveDays attribute of the following configuration items in the file to reduce the
time for backing up trace logs and saving the processed files.
In the preceding example, files in /opt/esau/data/eSAUSucceed are successfully processed
and those in /opt/esau/data/eSAUFailed fail to be processed. The system checks the
corresponding directories every 300 seconds. saveDays is the storage duration (days). If
the value exceeds the threshold, the system deletes the earliest trace files in sequence.
<Para path="/opt/esau/data/eSAUSucceed" saveDays="0.5" dirCheckISecs="300"
scriptRoot=""/>
<Para path="/opt/esau/data/eSAUFailed" saveDays="30" dirCheckISecs="300"
scriptRoot=""/>
<Para path="/opt/esau/var/logs/backup " saveDays="30" dirCheckISecs="300"
scriptRoot=""/>
4.
5.
Run the following commands to restart eSAU services for the setting to take effect.
Issue 04 (2013-08-30)
a.
b.
Start eSAU services. For detailed operations, see 8.1.11 Starting eSAU Services.
130

Step 5 Perform the following substeps to delete the trace logs and processed files of SAU:
1.
Run the following command to modify the /opt/PSSAU/etc/platform/log_cfg.xml file.

# vi /opt/PSSAU/etc/platform/log_cfg.xml
2.
3.
Change the value of <MaxCount>10</MaxCount> to reduce the number of history logs

you want to dump.
The content of the log_cfg.xml file is as follows: You can change the value of
<MaxCount>10</MaxCount> to set the number of history logs of each type you want to
dump in the /opt/PSSAU/var/logs/backup directory. If the value is reduced, the system
deletes the earliest trace files in sequence.
<?xml version="1.0" encoding="UTF-8"?>
<LogSys>

<MaxSize>30</MaxSize>

<MaxCount>10</MaxCount>


<SynchronousLog>true</SynchronousLog>
</LogSys>
4.
5.
Perform the following substeps to modify the /opt/PSSAU/etc/FileManagerConfig.xml

file.
# vi /opt/PSSAU/etc/FileManagerConfig.xml
6.
7.
If you modify the saveDays configuration item under , the system scans
the files in the directory. If the value exceeds the threshold, the system deletes the earliest
trace files in sequence.
Modify only the configuration items in bold in the following displayed information:

<FileManagerConfig>
<FileDelInfo delaySecs="100" intervalSecs="300">

<Para path="/opt/PSSAU/var/output/filepath" saveDays="1"
rmSubDir="0" dirCheckISecs="300"/>
<Para path="/opt/PSSAU/var/data/M2_MCHR" saveDays="90" rmSubDir="1"
dirCheckISecs="300"/>
<Para path="/opt/PSSAU/var/data/MCounter" saveDays="1" rmSubDir="1"
<Para path="/opt/PSSAU/var/data/ReduceMCounter" saveDays="1"
<Para path="/opt/PSSAU/var/output/ftpdir" saveDays="1"
<Para path="/opt/PSSAU/var/output/reduceDir" saveDays="1"
<Para path="/opt/PSSAU/var/data/EDR" saveDays="1" rmSubDir="1"
Issue 04 (2013-08-30)

131


<Para path="/opt/PSSAU/var/data/PCRF/master" saveDays="3"
<Para path="/opt/PSSAU/var/data/PCRF/cu" saveDays="0.125"
<Para path="/opt/PSSAU/var/output/db/PCRF_QUOTA_INDEX"
saveDays="0.125" rmSubDir="1" dirCheckISecs="300"/>
<Para path="/opt/PSSAU/var/output/db/PCRF_SUBSCRIBER_INDEX"
<Para path="/opt/PSSAU/var/output/logupload" saveDays="0.125"
<Para path="/opt/PSSAU/var/logs" saveDays="10" rmSubDir="0"
<Para path="/opt/PSSAU/var/output/log" saveDays="10"
<Para path="/opt/PSSAU/var/operation" saveDays="10"
<Para path="/var/logs" saveDays="10" rmSubDir="1"

<FilePathGrp name="COUNTER" maxSpace="50" cleanupPercent="50"
> 
<Para path="/opt/PSSAU/var/data/MCounter" saveDays="1"
<Para path="/opt/PSSAU/var/data/ReduceMCounter"
saveDays="1" rmSubDir="1" dirCheckISecs="300"/>
<Para path="/opt/PSSAU/var/output/reduceDir"
</FilePathGrp>
<FilePathGrp name="FTP" maxSpace="10" cleanupPercent="50" > <!-maxSpace:Gb-->
<Para path="/opt/PSSAU/var/data/EDR" dirCheckISecs="300"/
>
<Para path="/opt/PSSAU/var/data/PCRF/master"
<Para path="/opt/PSSAU/var/data/PCRF/cu/download"
<Para path="/opt/PSSAU/var/data/PCRF/cu/SUBSCRIBER"
<Para path="/opt/PSSAU/var/data/PCRF/cu/SUBQUOTA"
<Para path="/opt/PSSAU/var/data/PCRF/cu/QUOTA"
<Para path="/opt/PSSAU/var/output/db/
PCRF_SUBSCRIBER_INDEX" dirCheckISecs="300"/>
<Para path="/opt/PSSAU/var/output/logupload"
</FilePathGrp>
<FilePathGrp name="LOG" maxSpace="30" cleanupPercent="50" > <!-maxSpace:Gb-->
<Para path="/opt/PSSAU/var/logs" dirCheckISecs="300"/
>
<Para path="/opt/PSSAU/var/output/log"
<Para path="/opt/PSSAU/var/operation"
<Para path="/var/logs" dirCheckISecs="300"/>
</FilePathGrp>
</FileDelInfo>

Issue 04 (2013-08-30)

132


<DiskMonitorInfo delaySecs="100" intervalSecs="3600">
<Disk name="/export/home/" alarmSizePercent="75"
deleteSizePercent="90">
<Para path="sysm/PSSAU/var/output"/>
<Para path="sysm/PSSAU/var/data/MCounter"/>
<Para path="sysm/PSSAU/var/data/ReduceMCounter"/>
<Para path="sysm/PSSAU/var/data/EDR"/>
<Para path="sysm/PSSAU/var/data/PCRF"/>
<Para path="sysm/PSSAU/var/operation"/>
<Para path="sysm/PSSAU/var/logs"/>
</Disk>
<Disk name="/" alarmSizePercent="75" deleteSizePercent="90">
<Para path="var/logs"/>
</Disk>
</DiskMonitorInfo>
</FileManagerConfig>
8.
9.
Perform the following substeps to restart SAU services for the setting to take effect.
a.
b.
Start SAU services. For detailed operations, see 8.1.7 Starting SAU Services.
Step 6 Perform the following substeps to delete the useless files.
CAUTION
Before clearing up disk space, check that the files you want to delete are no longer required.
Deleting useful files by mistake might cause abnormal system running.
1.
Log in to the server as user root.
2.
Delete the core files of M2, SAU and eSAU.

The three types of core files are saved in the following directories respectively: /opt/Nastar/
var/logs, /opt/PSSAU/var/logs, and opt/esau/var/logs.
l Delete the core files one week earlier.
l For the core files within one week, contact Huawei technical support engineers.
Delete the core files that the Huawei technical support engineers confirm useless.
3.
Delete all files in the /var/tmp directory after you stop M2 services.
l Stop M2 services. For detailed operations, see 8.1.4 Stopping M2 Server Services.
l Restart M2 services. For detailed operations, see 8.1.3 Starting M2 Server Services.
4.
Delete the log files in /opt/Nastar/var/logs, /opt/PSSAU/var/logs, and opt/esau/var/

logs.
Step 7 Delete the historical data that has been processed by the M2 service process.
1.

Run su - omcuser to switch to user omcuser if you have logged in to the server as other
users:
2.
Run the following command to navigate to the /opt/Nastar/var/data/nastarm directory.

~> cd /opt/Nastar/var/data/nastarm
Issue 04 (2013-08-30)

133

3.
Delete all files in survey_bak, survey_missingformater, and survey_invalid_bak.
4.
Delete all files in registerReport_bak.
5.
Delete all files in statusReport_bak.
Step 8 Delete the trace logs of Agent Server.

1.

users.
2.
Run the following command to navigate to the /opt/Nastar/tomcat/logs directory.

3.
Optional: If you need to locate the problems, back up the files in the directory.
4.
Run the following command to delete all files in the directory.

~> rm rf *
5.
Restart the Tomcat service.

a.
Run the following commands to stop the Tomcat service.

~> cd /opt/Nastar/
b.
Run the following commands to restart the Tomcat service:

~> cd /opt/Nastar/
----End
10.2 Clearing Up the Disk Space for the Client

available.
Prerequisites
You have installed the client software.
Context
l
You are advised not to delete the files generated on the current day.
You are advised not to delete files when the client is running.
Before you delete a file, check that it can be deleted. Deleting useful files by mistake may
lead to system operation errors.
Issue 04 (2013-08-30)

134

Procedure
Step 1 Delete historical trace logs.
NOTE
Clearing up disk space tasks involves deleting historical trace logs on the client.
The historical trace logs are saved in the Installation directory of the client software\client
\tracefile directory.
----End
Issue 04 (2013-08-30)

135

11
Backing Up and Restoring Data
About This Chapter

This chapter describes how to back up and restore M2 system dynamic data.
11.1 Backup Schemes
This section describes the backup schemes for M2, SAU, eSAU, and Agent Server.
11.2 Backing Up and Restoring the M2 System
This section describes how to back up and restore M2 system dynamic data.
Issue 04 (2013-08-30)

136

11.1 Backup Schemes

This section describes the backup schemes for M2, SAU, eSAU, and Agent Server.
11.1.1 M2 Backup Schemes

This section describes the M2 system backup based on aspects such as backup scenarios and
backup file naming rules.
Backup of M2 Dynamic Data

Dynamic data backup of the M2 system involves backing up the imapdb database and the
dynamic data generated when the M2 server software is running.
Table 11-1 describes the backup contents, backup modes, and storage media of the dynamic
data backup.
Table 11-1 Dynamic data backup
Item
Content
Backup
contents
l Database imapdb
Backup
mode
Periodic backup: Set any day in a week to perform full backup. After the
periodic backup is activated, the system performs a round of full backup every
week. When a new round of full backup is performed, all the backup files of
the previous round are deleted automatically.
Storage
medium
Hard disk
Directory of
backup files
/export/home/backup/omc (This item does not need to be created manually.)
l M2 system files: files in the /export/home/omc/var and /export/home/

sysm directories
After the backup is performed, the backup contents are automatically packaged as a backup file.
Rules for Naming Backup Files of Dynamic Data

The backup files of dynamic data are named in the following format: allYYYYMMDDhhmmss.tar.
Example:
The file name all-20040601042002.tar refers to a full backup file generated on 01.06.04 at
04:20:02.
Issue 04 (2013-08-30)

137

NOTE
After the system performs backup, the latest backup information is recorded in the /export/home/
backup/omc/backupstate.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 data backup, the all-YYYYMMDDhhmmss folder is generated in the /export/home/
backup/omc directory for storing backup files. When the data backup is complete, the folder is
compressed into the all-YYYYMMDDhhmmss.tar file, and the all-YYYYMMDDhhmmss folder is
automatically deleted.
11.1.2 SAU Backup Schemes

This section describes the SAU system backup based on aspects such as backup scenarios and
Backup of SAU Dynamic Data

Dynamic data backup of the SAU system involves the backup of the dynamic data and
configuration files generated when the SAU software is running.
data backup.
Item
Content
Backup
contents
SAU system files: files in the /opt/PSSAU/var and /opt/PSSAU/etc directories
Backup
mode
Manual backup
Storage
medium
Hard disk
Directory of
backup files
/export/home/backup/pssau (You need to create this directory manually.)

Example:
04:20:02.
Issue 04 (2013-08-30)

138

11.1.3 eSAU Backup Schemes

This section describes the eSAU system backup based on aspects such as backup scenarios and
Backup of eSAU Dynamic Data

Dynamic data backup of the eSAU system involves the backup of the dynamic data and
configuration files generated when the eSAU software is running.
data backup.
Item
Content
Backup
contents
eSAU system files: files in the /opt/esau/var and /opt/esau/etc directories
Backup
mode
Manual backup
Storage
medium
Hard disk
Directory of
backup files
/export/home/backup/esau

Example:
04:20:02.
11.1.4 Agent Server Backup Schemes

This section describes the Agent Server system backup based on aspects such as backup
scenarios and backup file naming rules.
Backup of Agent Server Dynamic Data

Dynamic data backup of the Agent Server system involves the backup of the dynamic data and
configuration files generated when the Agent Server software is running.
data backup.
Issue 04 (2013-08-30)

139


Item
Content
Backup
contents
l Agent Server database
Backup
mode
Manual backup
Storage
medium
Hard disk
Directory of
backup files
l Dada backup path: /export/home/gaussdb/backup
l Agent Server configuration information
l Agent Server configuration information path: /export/home/agents/

backup (You need to create this directory manually.)

Database dynamic data backup files are named as follows: ams-YYYYMMDDhhmmss.bak.
Agent Server service dynamic data backup files are named as follows: agentServerYYYYMMDDhhmmss.tar.
For example:
The file name ams-20040601042002.bak indicates a full backup file generated at 04:20:02 on
1st June, 2004.
The file name agentServer-20040601042002.tar indicates a full backup file generated at
04:20:02 on 1st June, 2004.
11.2 Backing Up and Restoring the M2 System

This section describes how to back up and restore M2 system dynamic data.
11.2.1 Backing Up M2 System Dynamic Data

This section describes how to back up M2 system dynamic data.
Prerequisites
l
You are authorized to back up M2 system dynamic data.
The hard disk where you want to back up the dynamic data has sufficient free space.
Issue 04 (2013-08-30)

140

Context
Generally, M2 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 when
the system is running.
Procedure
Step 1 Choose Maintenance > Task Management.
The Task Management window is displayed.
Step 2 Choose Task Type > Backup > Server Backup, and then double-click the Server Backup
node in the navigation tree in the left.
The Attribute dialog box is displayed, as shown in Figure 11-1.
Figure 11-1 Periodic backup (1)
Step 3 Click the Common Parameters tab, and then set Task Name and Start Time.
Step 4 Click the Extended Parameters tab, and then set Backup Medium, as shown in Figure 11-2.
Issue 04 (2013-08-30)

141

Figure 11-2 Periodic backup (2)
Step 5 Click OK to save the settings.

After you apply the settings, the system periodically backs up data.
NOTE
Currently, M2 supports backup using only hard disks. When you use a hard disk as the backup medium,
log in to M2 server and check whether the all-YYYYMMDDhhmmss.tar file is available in /export/home/
backup/omc/.
----End
11.2.2 Restoring M2 System Dynamic Data

This section describes how to restore M2 system dynamic data.
Prerequisites
l
You have logged in to the server as user root.
The backup files for restoring the M2 dynamic data are obtained.
The M2 is running properly or the static data restoration is complete.
Context
Based on the latest full backup files of the M2, you can restore the M2 system data. After you
perform the restoration operation, all the contents in the backup file package are restored.
Issue 04 (2013-08-30)

142

CAUTION
M2 services are stopped if you perform dynamic data restore operations. M2 server cannot
process the data reported by the agent during this period.
Procedure
Step 1 Run the following commands to copy the backup files to a hard disk if the backup files are stored
on a tape. Skip this step and go to Step 3 if the backup files are stored on a hard disk.
# cd /
# tar xvf /dev/st0
If the following message is displayed during the execution of the commands, ignore the message.
tar: Removing the initial "/" from member names
CAUTION
The decompressed file is stored in the same path as the compressed one. The save path of the
decompressed file is irrelevant to the path where you perform the decompression operation.
Step 3 Restart the Oracle database.
For details about how to stop and start Oracle services, see 9.1.4 Stopping Oracle and 9.1.3
Staring Oracle respectively.
Step 4 Log in to the server as user omcuser to restore M2 system dynamic data.
1.
Decompress the backup file that contains the dynamic data you want to restore.
~> cd /export/home/backup/omc/
~> tar xvf /export/home/backup/omc/name of the dynamic data backup file -C /
For example, before restoring the full dynamic data backup file generated on 18:06:22
2008-01-30, you need to decompress the relevant package.
~> tar xvf /export/home/backup/omc/all-20080130180622.tar -C /
Issue 04 (2013-08-30)

143


NOTE
You need to decompress the relevant package regardless of whether the file to be restored is a full
backup file or an incremental backup file.
2.
Navigate to the save path of the decompressed file.

~> cd /export/home/backup/omc/name of the dynamic data backup file
For example:
~> cd /export/home/backup/omc/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:dbpasswd]:
NOTE
You can type q or Q to stop running 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

Step 6 Delete the decompressed backup files after the data restoration.
~> cd /export/home/backup/omc
~> rm -rf Backup package decompression directory
For example:
~> rm -rf all-20080130180622
----End
11.2.3 Backing Up SAU System Dynamic Data

This section describes how to back up SAU system dynamic data.
Prerequisites
l
Issue 04 (2013-08-30)
You are authorized to back up SAU system dynamic data.

144

Hard disk space is sufficient.
Dynamic data is fully backed up.
Dynamic data backup has no restriction on backup time. The backup can be performed
when the system is running.
Context
Procedure
Step 2 Run the following commands to back up dynamic data to the specified directory.
# cd /opt/PSSAU/script/admin
# sh backupdata.sh
NOTE
The backup data is saved in the following specified directory: /export/home/backup/pssau.
If the dd-YYYYMMDDhhmmss.tar file is generated in the current /export/home/backup/

pssau directory after the commands are executed, the SAU system dynamic data backup
succeeds. Otherwise, the backup fails.
----End
11.2.4 Restoring SAU System Dynamic Data

This section describes how to restore SAU system dynamic data.
Prerequisites
l
The backup files for restoring the SAU dynamic data are obtained.
The M2 server is running properly or the static data restoration is complete.
Context
Based on the latest full backup files of the SAU, you can restore the SAU system data. After
you perform the restoration operation, all the contents in the backup file package are restored.
Stop SAU services when you restore the dynamic data.
Procedure
Step 2 Perform the following substeps to stop SAU services:
1.
Check that the SAU services are running properly. For detailed operations, see 8.1.6
Checking SAU Service Status.
2.
Step 3 Run the following commands to restore the dynamic data.

Issue 04 (2013-08-30)

145

1.

# cd /opt/PSSAU/script/admin
# sh restoredata.sh
The following information is displayed:
Please input restore package path and name:
2.
Enter the save path of the dynamic data, and press Enter.
For example, enter the following if the path of the backup package is /export/home/
backup/pssau:
/export/home/backup/pssau
3.
Enter the file name of the dynamic data, and press Enter.
For example, enter the following if the name of the backup package is ddYYYYMMDDhhmmss.tar:
dd-YYYYMMDDhhmmss.tar
Step 4 Start SAU services. For detailed operations, see 8.1.7 Starting SAU Services.
----End
11.2.5 Backing Up eSAU System Dynamic Data

This section describes how to back up eSAU system dynamic data.
Prerequisites
l
You are authorized to back up eSAU system dynamic data.
Hard disk space is sufficient
Context
Procedure
Step 2 Run the following commands to back up dynamic data to the specified directory.
# cd /opt/esau/script/admin
# sh backupdata.sh
NOTE
The backup data is saved in the following fixed directory: /export/home/backup/esau
Issue 04 (2013-08-30)

146

If the dd-YYYYMMDDhhmmss.tar file is generated in the current /export/home/backup/

esau directory after the commands are executed, the eSAU system dynamic data backup
succeeds. Otherwise, the backup fails.
----End
11.2.6 Restoring eSAU System Dynamic Data

This section describes how to restore eSAU system dynamic data.
Prerequisites
l
The backup files for restoring the eSAU dynamic data are obtained.
The M2 is running properly or the static data restoration is complete.
Context
Based on the latest full backup files of the eSAU, you can restore the eSAU system data. After
you perform the restoration operation, all the contents in the backup file package are restored.
Stop eSAU services when you restore the dynamic data.
Procedure
Step 2 Perform the following substeps to stop eSAU services:
1.
Check that the eSAU services are running properly. For detailed operations, see 8.1.10
Checking eSAU Service Status.
2.
Step 3 Run the following commands to restore dynamic data.

1.

# cd /opt/esau/script/admin
# sh restoredata.sh
Please input restore package path and name:
2.
Enter the save path of the dynamic data, and press Enter.
For example, enter the following if the path of the backup package is /export/home/
backup/esau:
/export/home/backup/esau
3.
Enter the file name of the dynamic data, and press Enter.
For example, enter the following if the name of the backup package is ddYYYYMMDDhhmmss.tar:
dd-YYYYMMDDhhmmss.tar
Issue 04 (2013-08-30)

147

Step 4 Start eSAU services. For detailed operations, see 8.1.11 Starting eSAU Services.
----End
11.2.7 Backing Up Agent Server System Dynamic Data

This section describes how to back up Agent Server system dynamic data.
Prerequisites
l
You are authorized to back up Agent Server system dynamic data.
Hard disk space is sufficient.
Context
Procedure
Step 1 Use PuTTY to log in to the server in SSH mode as user root
Step 2 Run the following commands to created the backup directories /export/home/gaussdb/
backup and /export/home/agents/backup.
# mkdir -p /export/home/agents/backup
# mkdir -p /export/home/gaussdb/backup
Step 3 Run the following commands to modify the owner of /export/home/gaussdb to gaussdba and
the group to omcsysm.
# chown -R gaussdba.omcsysm /export/home/gaussdb
Step 4 Run the following commands to modify the owner of /export/home/agents to omcuser and the
group to omcsysm.
# chown -R omcuser.omcsysm /export/home/agents
Step 5 Run the su - gaussdba command to switch to user gaussdba.
Step 6 Run the following commands to back up Agent Server system database:
~> cd /export/home/gaussdb/backup
~> tar -C /opt/gaussdb -cf /export/home/gaussdb/backup/ams-`date "+%Y%m%d%H%M%
s"`.tar data
If the ams-YYYYMMDDhhmmss.tar file is generated in the current /export/home/gaussdb/
backup directory after the commands are executed, the Agent Server database backup succeeds.
Otherwise, the backup fails.
Step 7 Run the su - omcuser command to switch to user omcuser.
Step 8 Run the following commands to back up Agent Server system dynamic data:
~> cd /export/home/agents/backup
Issue 04 (2013-08-30)

148

~> tar -C /opt/Nastar/webapps/AMS/WEB-INF -cf agentServer-`date "+%Y%m%d%H%M

%s"`.tar classes
If the agentServer-YYYYMMDDhhmmss.tar file is generated in the current /export/home/
agents/backup directory after the commands are executed, the Agent Server system dynamic
data backup succeeds. Otherwise, the backup fails.
----End
11.2.8 Restoring Agent Server System Dynamic Data

This section describes how to restore Agent Server system dynamic data.
Prerequisites
l
The backup files for restoring the Agent Server dynamic data are obtained.
The M2 server is running properly or the static data restoration is complete.
The GaussDB database has been initialized.
Context
Based on the latest full backup files of the Agent Server, you can restore the Agent Server system
data. After you perform the restoration operation, all the contents in the backup file package are
restored.
Stop Agent Server service when you restore the dynamic data.
Procedure
Step 1 Perform the following substeps to stop Agent Server service:
1.
Check that the Agent Server service is running properly. For detailed operations, see 8.2.2
Checking Agent Server Service Status.
2.
Stop Agent Server service. For detailed operations, see 8.2.4 Stopping the Agent Server
Service.

Step 3 Run the following commands to restore the Agent Server system database:
# su - gaussdba -c "gs_ctl stop -m fast"
# cd /export/home/gaussdb/backup
# mv /opt/gaussdb/data /opt/gaussdb/data.bak
# tar xf ams-YYYYMMDDhhmmss.tar -C /opt/gaussdb
# su - gaussdba -c "gs_ctl start"
ams-YYYYMMDDhhmmss.bak is the name of the file you want to restore.
The restoration succeeds if there is no error after you execute the commands and exit the
command-line interface.
Issue 04 (2013-08-30)

149

Step 5 Run the following command to restore the Agent Server configuration data:
~> cd /export/home/agents/backup
~> tar -xvf agentServer-YYYYMMDDhhmmss.tar -C /opt/Nastar/webapps/
agentServer-YYYYMMDDhhmmss.tar is the name of the file you want to restore.
Step 6 Start Agent Server service. For detailed operations, see 8.2.3 Starting the Agent Server
Service.
----End
Issue 04 (2013-08-30)

150

12
Routine System Maintenance
About This Chapter

This chapter describes the system routine maintenance which is a type of preventive
maintenance. Routine maintenance is classified into daily maintenance, weekly maintenance,
and monthly maintenance. Specified items and guidelines are provided and you can add or delete
the items as required.
12.1 Routine Maintenance Items
This section provides maintenance item lists for your reference during the daily, weekly, and
monthly maintenance of the M2 system.
12.2 Daily Maintenance
This section describes the daily system maintenance operations, which helps you learn the
running status and trend of the system so as to improve the troubleshooting efficiency. Daily
maintenance and operation (OM) involves viewing resource status of the server, process status,
logs, and so on.
12.3 Weekly Maintenance Items
This section describes weekly maintenance operations, which helps you identify exceptions such
as function failure and performance decrease and provides guidance for you to take actions
accordingly. You can also back up data during weekly maintenance to avoid data loss. Weekly
maintenance operations also involve checking the disk usage of the server, checking server time,
and clearing up disks of the server and client.
12.4 Monthly Maintenance Items
Monthly maintenance helps the system operate securely, stably, and reliably in a long term.
Monthly maintenance involves checking and setting user rights of M2 server, checking power
supply of the server, and checking M2 system licenses.
Issue 04 (2013-08-30)

151

12.1 Routine Maintenance Items

This section provides maintenance item lists for your reference during the daily, weekly, and
monthly maintenance of the M2 system.
Table 12-1 lists the recommended maintenance items of the M2 system. You can add or delete
maintenance items as required.
Table 12-1 List of maintenance items
Issue 04 (2013-08-30)
Routine Maintenance Maintenan

Task
ce Period
Reference
Checking the CPU usage

of the server
The CPU usage should be lower than 80%. If tasks

are running longer than normal and the CPU usage
always exceeds 80%, exceptions or management
capability risks may exist.
Daily
Checking the core files

of M2
In the /opt/Nastar/var/logs/ directory, no file

whose name starts with "core" is available.

of SAU
In the /opt/PSSAU/var/logs/ directory, no file

whose name starts with "core" is available.

of eSAU
In the /opt/esau/var/logs/ directory, no file whose

name starts with "core" is available.
Checking SUSE Linux

error logs
No error log is generated.
Checking M2 logs
Logs of certain processes are collected for fault

location.
Checking SAU logs

location.
Checking eSAU logs

location.
Checking Agent Server

logs

location.
Checking M2 service
status
All services are running properly. There is no item

whose status is "not running".
Checking SAU service

status

Checking eSAU service

status

Checking the service

status of the Agent
Server database


152

Routine Maintenance Maintenan

Task
ce Period
Reference
Checking the status of

the Oracle database
The Oracle database is running properly and its

usage is less than 90%.
Checking GaussDB
database status
The GaussDB database is running properly and its

usage is less than 90%.
Checking the hard disk

usage of the server
Weekly
The usage of each disk is less than 90%.
Checking the server time
The time of the M2 server is correct.
Cleaning up disks on the

server
Back up the information that is required for further

operations. Then, clean up the disk to free up
storage space.
Cleaning up disks on the

client
Back up the information that is required for further

operations. Then, clean up the disk to free up
storage space.
Checking and setting

M2 system user rights
Monthly
Permission is correctly granted to related users.
Checking the power

supply of the server
The power supply is normal.
Checking the M2 system

license
The license is within the valid period and no

message indicating the expiration of the license is
displayed.
12.2 Daily Maintenance

This section describes the daily system maintenance operations, which helps you learn the
running status and trend of the system so as to improve the troubleshooting efficiency. Daily
maintenance and operation (OM) involves viewing resource status of the server, process status,
logs, and so on.
12.2.1 Viewing the CPU Usage of the Server

This section describes how to check whether the CPU usage is within the specified range.
Prerequisites
l
You are authorized to view the CPU usage.
Context
Normally, the CPU usage should be less than 80%.
Issue 04 (2013-08-30)

153

Procedure
l
View the CPU usage on the client.

1.
Choose System > System Monitor > Browser.
2.
On theServer Monitor tab page of the System Monitor Browser window, view
Usage(%).
Log in to the server to view CPU usage.

1.
2.
Run the following command to view the CPU usage.

# top
In the displayed information, CPU usage is normal if the values in the %CPU column
do not exceed 80. Otherwise, contact Huawei technical support engineers.
top - 16:28:29 up 9 days, 5:50, 13 users, load average: 0.09, 0.07,
0.23
Tasks: 629 total,
1 running, 627 sleeping,
0 stopped,
1 zombie
Cpu(s): 1.0%us, 0.7%sy, 0.0%ni, 98.3%id, 0.0%wa, 0.0%hi, 0.0%si,
0.0%st
Mem:
16039M total,
15834M used,
205M free,
225M buffers
Swap:
8189M total,
1310M used,
6878M free,
12945M cached
PID
16702
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
USER
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
root
PR
15
16
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
34
RT
NI
0
0
0
19
0
19
0
19
0
19
0
19
0
19
0
19
0
19
0
19
0
19
0
19
0
19
0
VIRT RES
5916 1524
800 292
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
SHR
792
244
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
S %CPU %MEM
R
5 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
S
0 0.0
TIME+
0:00.08
0:26.06
0:02.02
0:00.13
0:00.04
0:00.16
0:00.04
0:00.18
0:00.04
0:00.08
0:00.83
0:00.26
0:00.07
0:00.15
0:00.02
0:00.08
0:00.04
0:00.09
0:01.20
0:00.10
0:00.02
0:00.12
0:00.06
0:00.05
0:00.04
0:00.06
0:00.87
COMMAND
top
init
migration/0
ksoftirqd/0
migration/1
ksoftirqd/1
migration/2
ksoftirqd/2
migration/3
ksoftirqd/3
migration/4
ksoftirqd/4
migration/5
ksoftirqd/5
migration/6
ksoftirqd/6
migration/7
ksoftirqd/7
migration/8
ksoftirqd/8
migration/9
ksoftirqd/9
migration/10
ksoftirqd/10
migration/11
ksoftirqd/11
migration/12
----End
12.2.2 Checking the Core Files of M2

This section describes how to check the core files in the /opt/Nastar/var/logs directory.
Issue 04 (2013-08-30)

154

Procedure
l If you have logged in to the server as another user, you can run the su - omcuser command
in the command terminal window to switch to user omcuser.
l If you are required to type a password after the su - omcuser command is executed, type the
password of user omcuser.
Step 2 Run the following command to navigate to the /opt/Nastar/var/logs directory.
~> cd /opt/Nastar/var/logs
Step 3 Run the following command to check whether there is any file whose name starts with "core"
in this directory.
~> ls -ltr core*
l Delete the files whose names start with "core" and that are generated one week ago or earlier.
l If there are core files generated within one week in the directory, contact Huawei technical
support engineers.
----End
12.2.3 Checking the Core Files of SAU

This section describes how to check the core files in the /opt/PSSAU/var/logs directory.
Procedure
Step 2 Run the following command to navigate to the /opt/PSSAU/var/logs directory.
in this directory.
~> ls -ltr core*
support engineers.
----End
12.2.4 Checking the Core Files of eSAU

This section describes how to check the core files in the /opt/esau/var/logs directory.
Procedure
Issue 04 (2013-08-30)

155

Step 2 Run the following command to navigate to the /opt/esau/var/logs directory.

in this directory.
~> ls -ltr core*
support engineers.
----End
12.2.5 Checking SUSE Linux Error Logs

This section describes how to view the SUSE Linux error logs to determine the status of the
system. Viewing the SUSE Linux logs requires few system resources and does not affect the
system operation.
Procedure
Step 2 Run the following command to check whether the files contain error information:
# more /var/log/messages
In normal cases, the logs do not contain the err or failed messages.
Step 3 Run the following command to check whether the logs in the memory contain error information.
# dmesg
----End
12.2.6 Checking M2 Logs

This section describes how to check M2 logs to check where there are errors.
Procedure
directory.
~> cd /opt/Nastar/var/logs
~> grep ERROR*
Issue 04 (2013-08-30)

156

Step 3 Optional: Run the following commands to pack M2 log files. Then contact Huawei technical
support engineers.
~> cd /opt/Nastar/var
~> tar zcvf error.tar.gz logs
----End
12.2.7 Checking SAU Logs

This section describes how to check SAU logs to check where there are errors.
Procedure
directory.
~> grep ERROR*
~> cd /opt/PSSAU/var
Step 4 Run the following commands to check the error logs upon BS script execution.
~> cd /opt/PSSAU/var/output/log
~> grep ERROR*
l Otherwise, perform Step 3 again to pack the log files. Then contact Huawei technical support
engineers.
----End
12.2.8 Checking eSAU Logs

This section describes how to check eSAU logs to check that there is no error.
Procedure
Issue 04 (2013-08-30)

157

Step 2 Run the following commands to check whether there are errors in the /opt/esau/var/logs
directory.
~> grep ERROR*
~> cd /opt/esau/var
----End
12.2.9 Checking Agent Server Logs

This section describes how to check Agent Server logs to check where there are errors.
Procedure
Step 2 Run the following commands to check whether there are errors in the /opt/Nastar/tomcat/
logs directory.
~> grep ERROR*
Step 3 Optional: Run the following commands to pack the log files. Then contact Huawei technical
support engineers.
~> tar zcvf err.tar.gz logs
----End
12.2.10 Checking M2 Service Status

This section describes how to check the service status of each M2 process to see whether it is
running properly.
Prerequisites
l
Issue 04 (2013-08-30)
You have logged in to the M2.

158

You have the permission to check service status.
Check the service status on the client.
Procedure
1.
2.
On the Service Monitor tab page of the System Monitor Browser window, check
the service status of the server.
If a service is abnormal, the icon for this service is displayed in red.
In the System Monitor Browser window, right-click any area. In the displayed
shortcut menu, select Refresh to refresh the current window.
Check the service status by running commands.

1.

NOTE
l If you have logged in to the server as another user, you can run the su - omcuser command
in the command terminal window to switch to user omcuser.
l If you are required to type a password after the su - omcuser command runs, type the
password of user omcuser.
2.
Run the following command to navigate to the M2 server software installation

directory. (The default installation directory is /opt/Nastar.)
~> cd /opt/Nastar
3.
Run the following commands to check M2 service status:

The command output similar to the following information is displayed:
In the command output, if the service status is Running, the service is running
properly.
In the command output, if the service status is Not Running, the service is not
started.
In the command output, if the service status is No License, the service is not
registered.
NOTE
The M2 may dynamically generate processes and services when it is running. The number of
processes and services queried each time may be different.
----End
12.2.11 Checking SAU Service Status

This section describes how to check SAU service status to see whether it is running properly.
Issue 04 (2013-08-30)

159

Procedure
Step 2 Run the following commands to check SAU services:
~> cd /opt/PSSAU
~> ps_query
When the following or similar information is displayed, SAU services are running.
Service Agent: PSau.Calculator [1 service(s)] pid: 24663
PSau.Calculator
[running]
Service Agent: PSau.Collector [1 service(s)] pid: 24692
PSau.Collector
[running]
Service Agent: PSau.Controller [1 service(s)] pid: 24556
PSau.Controller
[running]
Service Agent: SysMonitor [1 service(s)] pid: 24589
SysMonitor
[running]
[All Services: 4 ] [Running: 4] [Not Running: 0 ]
NOTE
l In the displayed information, if the state of the service is Running, the service operate properly.
l In the displayed information, if the state of the service is Not Running, the service is abnormal.
l At the end of the displayed information, if the value of Not Running is 0, all the SAU services operate
properly. Otherwise, some SAU services have not started.
----End
12.2.12 Checking eSAU Service Status

This section describes how to check eSAU service status to see whether it is running properly.
Procedure
Step 2 Run the following commands to view eSAU service status:
~> cd /opt/esau
~> esau_ps
When the following or similar information is displayed, eSAU services are running.
Monitor...........................running
eSAU...........................running
SysMonitor.....................running
[All Services: 3] [Running: 3] [Not Running: 0 ]
Issue 04 (2013-08-30)

160

NOTE
l In the displayed information, if the state of the service is Running, you can infer that the service operate
properly.
l In the displayed information, if the state of the service is Not Running, you can infer that the service
is abnormal.
l At the end of the displayed information, if the value of Not Running is 0, you can infer that all the
eSAU services operate properly. Otherwise, some eSAU services have not been started.
----End
12.2.13 Checking Agent Server Service Status

This section describes how to check Agent Server service status to see whether it is running
properly.
Procedure
Step 2 Run the following commands to check Agent Server service status:
~> cd /opt/Nastar
~> cd tomcat
service is running.
l In the displayed information, if the state of the service is running, the service operate
properly.
l In the displayed information, if the state of the service is not running, the service is abnormal.
----End
12.2.14 Checking Oracle Database Status

This section describes how to check Oracle database status.
Prerequisites
l
You are authorized to check the status of the Oracle database.
If the database usage exceeds the preset threshold, the icon of this item is displayed in red.
You can right-click in the System Monitor Browser window and choose Refresh from
the shortcut menu to refresh the current window.
Context
Issue 04 (2013-08-30)

161

Procedure
l
Check Oracle database status on M2 client.

1.
2.
On the Database Monitor tab page of the System Monitor Browser window, check
the usage of the Oracle database.
Check Oracle database status of the M2 using commands.

1.
2.
Run the following command to check whether Oracle database services are started:
# ps -fu oracle
UID PID PPID C STIME TTY TIME CMD
Oracle 5141 1 0 21:36 ? 00:00:00 ora_pmon_imapdb
....
Oracle 5157 1 0 21:36 ? 00:00:00 ora_dbw0_imapdb
...
Oracle 5165 1 0 21:36 ? 00:00:00 ora_lgwr_imapdb
Oracle 5167 1 0 21:36 ? 00:00:00 ora_ckpt_imapdb
Oracle 5169 1 0 21:36 ? 00:00:00 ora_smon_imapdb
...
Oracle 5197 1 0 21:36 ? 00:00:00 ora_arc0_imapdb
...
/opt/oracle/oradb/home/bin/tnslsnr LISTENER -inherit
If the command result contains at least the following six processes, Oracle database
services and listening services are running normally.
ora_pmon_ imapdb
ora_dbw0_ imapdb
ora_lgwr_ imapdb
ora_ckpt_ imapdb
ora_smon_ imapdb
/opt/oracle/oradb/home/bin/tnslsnr
If no command output is displayed, Oracle database services are not started
properly. Start database services by referring to 9.1.3 Staring Oracle.
----End
12.2.15 Checking GaussDB Database Status

This section describes how to check GaussDB database status. GaussDB is the database software
of Agent Server.
Prerequisites
You have started the Agent Server service. To check whether Agent Server service are started,
see 8.2.2 Checking Agent Server Service Status.
Procedure
Step 1 Log in to the server as user gaussdba.
Issue 04 (2013-08-30)

162

l If you have logged in to the server as another user, you can run the su - gaussdba command
in the command terminal window to switch to user gaussdba.
l If you are required to type a password after the su - gaussdba command runs, type the
password of user gaussdba.
Step 2 Run the following command to navigate to the home directory:
~> cd ~
Step 3 Run the following command to check GaussDB database status.
~> gs_ctl query
Ha state:
LOCAL_ROLE
STATIC_CONNECTIONS
DB_STATE
DETAIL_INFORMATION
:
:
:
:
Normal
0
Normal
Normal
----End
12.3 Weekly Maintenance Items

This section describes weekly maintenance operations, which helps you identify exceptions such
as function failure and performance decrease and provides guidance for you to take actions
accordingly. You can also back up data during weekly maintenance to avoid data loss. Weekly
maintenance operations also involve checking the disk usage of the server, checking server time,
and clearing up disks of the server and client.
12.3.1 Viewing the Hard Disk Usage of the Server

This section describes how to check the disk usage and delete expired log files, temporary files,
and other files that are no longer in use. This operation requires few system resources and does
not affect system performance.
Prerequisites
l
You are authorized to check the disk usage of the server.
In normal cases, the usage of each disk partition should be lower than 80%.
The space available on each disk partition must be sufficient to back up the M2.
View the hard disk usage of the server on the client.
Context
Procedure
1.
Issue 04 (2013-08-30)

163

2.
l
In the System Monitor Browser window, click the Hard Disk Monitor tab to view
the disk usage of the server.
View the hard disk usage by running commands.

1.
Log in to the server as user root and run the following command to view the hard disk
usage.
# df -k
2.
View the hard disk usage.

In normal cases, the hard disk usage is lower than 80%, and the value of Use% is
smaller than 80%.
View the disk partition with the largest available space. The available space must
be sufficient to back up the M2.
If the disk space is insufficient, clean up the disk space by referring to 10.1
Clearing Up the Disk Space for the Server.
----End
12.3.2 Checking the Server Time

This section describes how to check the time of the server to ensure that the server time is the
same as the actual time.
Procedure
Step 1 Log in to the server as user root, and then run the following command to check the time of the
server.
# date
The server time is displayed, for example:
Wed Aug 29 14:57:51 CST 2012
Step 2 Change the server time by referring to 2.2 Changing the Date and Time of the Server if it is
incorrect.
----End
12.3.3 Cleaning Up the Disk Space of the Server

Context
During the routine operation and maintenance, back up and delete the following files:
l
Files containing the information about the M2 server
Software upgrade packages and decompressed files
Trace logs
Temporary files created during system operation
Issue 04 (2013-08-30)

164

CAUTION
You can delete files when the server is running. Before deleting files, run the ls -l command to
check the time when the files were generated. Do not delete the files generated on the current
day.
Procedure
Step 1 Export the files containing the information about the M2 server and back up the files to a local
hard disk.
The following files are included:
l User log files
User log dump files are saved in the /opt/Nastar/var/userlogs/ directory.
l Core files generated by the system
Core files are saved in the /opt/Nastar/var/logs, /opt/esau/var/logs, and /opt/PSSAU/var/
logs directories.
l History trace files
Historical trace files are saved in the /opt/Nastar/var/logs/tracebak, /opt/esau/var/logs/
backup, and /opt/PSSAU/var/logs/backup directories.
Step 2 Delete M2 software upgrade packages and decompressed files.
After the software is successfully upgraded, you can delete the original upgrade packages and
the decompressed files. The upgrade packages and decompressed files are stored in a directory
that is named after the upgrade patch in the /export/home/M2update directory.
Step 3 Perform the following substeps to delete the trace logs of M2 services.
1.
Run the following command to edit the tracemonitor_svc_ex.xml file:

# vi /opt/Nastar/etc/conf/tracemonitor_svc_ex.xml
2.
3.
Change the value of tracebackupnum in the tracemonitor_svc_ex.xml file to decrease

trace backup files.
Edit the tracemonitor_svc_ex.xml file in the /opt/Nastar/etc/conf/ directory to set the
trace log monitoring period, size limit, and number of backup files. /opt/Nastar is the default
installation directory of the M2 server software.
You can change the value of checktracetime to set the period for monitoring the trace log.
You can change the value of tracebackupnum to set the number of backup trace files for
each process in the /opt/Nastar/var/logs/tracebak directory. The system checks the trace
file every 300 seconds. If the number of trace files corresponding to one process in the
tracebak directory exceeds the preset value, the system deletes the earliest trace files in
sequence.
The content of the tracemonitor_svc_ex.xml file is as follows:
<?xml version="1.0" encoding="iso-8859-1"?>
<tracemonitor name="tracemonitor" mount="/imap/tracemonitor">
Issue 04 (2013-08-30)

165



<param name="checktracetime">300</param>

<param name="tracebackupnum">50</param>
</tracemonitor>
4.
Step 4 Perform the following substeps to delete the trace logs and processed files of eSAU:
1.
Run the following command to edit the configuration file:

# vi /opt/esau/etc/FileManagerConfig.xml
2.
3.
Modify the saveDays attribute of the following configuration items in the file to reduce the
time for backing up trace logs and saving the processed files.
In the preceding example, files in /opt/esau/data/eSAUSucceed are successfully processed
and those in /opt/esau/data/eSAUFailed fail to be processed. The system checks the
corresponding directories every 300 seconds. saveDays is the storage duration (days). If
the value exceeds the threshold, the system deletes the earliest trace files in sequence.
<Para path="/opt/esau/data/eSAUSucceed" saveDays="0.5" dirCheckISecs="300"
scriptRoot=""/>
<Para path="/opt/esau/data/eSAUFailed" saveDays="30" dirCheckISecs="300"
scriptRoot=""/>
<Para path="/opt/esau/var/logs/backup " saveDays="30" dirCheckISecs="300"
scriptRoot=""/>
4.
5.
Run the following commands to restart eSAU services for the setting to take effect.
a.
b.
Start eSAU services. For detailed operations, see 8.1.11 Starting eSAU Services.
Step 5 Perform the following substeps to delete the trace logs and processed files of SAU:
1.
Run the following command to modify the /opt/PSSAU/etc/platform/log_cfg.xml file.

# vi /opt/PSSAU/etc/platform/log_cfg.xml
2.
3.
Change the value of <MaxCount>10</MaxCount> to reduce the number of history logs

you want to dump.
The content of the log_cfg.xml file is as follows: You can change the value of
<MaxCount>10</MaxCount> to set the number of history logs of each type you want to
dump in the /opt/PSSAU/var/logs/backup directory. If the value is reduced, the system
deletes the earliest trace files in sequence.
<LogSys>

<MaxSize>30</MaxSize>

<MaxCount>10</MaxCount>

<SynchronousLog>true</SynchronousLog>
</LogSys>
4.
5.
Perform the following substeps to modify the /opt/PSSAU/etc/FileManagerConfig.xml

file.
# vi /opt/PSSAU/etc/FileManagerConfig.xml
6.
7.
If you modify the saveDays configuration item under , the system scans
the files in the directory. If the value exceeds the threshold, the system deletes the earliest
trace files in sequence.
Modify only the configuration items in bold in the following displayed information:

<FileManagerConfig>
<FileDelInfo delaySecs="100" intervalSecs="300">

<Para path="/opt/PSSAU/var/data/M2_MCHR" saveDays="90" rmSubDir="1"
<Para path="/opt/PSSAU/var/data/MCounter" saveDays="1" rmSubDir="1"
<Para path="/opt/PSSAU/var/data/ReduceMCounter" saveDays="1"
<Para path="/opt/PSSAU/var/output/reduceDir" saveDays="1"
<Para path="/opt/PSSAU/var/data/EDR" saveDays="1" rmSubDir="1"
<Para path="/opt/PSSAU/var/data/PCRF/master" saveDays="3"
<Para path="/opt/PSSAU/var/data/PCRF/cu" saveDays="0.125"
<Para path="/opt/PSSAU/var/output/db/PCRF_SUBSCRIBER_INDEX"
<Para path="/opt/PSSAU/var/output/logupload" saveDays="0.125"
<Para path="/opt/PSSAU/var/logs" saveDays="10" rmSubDir="0"
<Para path="/opt/PSSAU/var/output/log" saveDays="10"
<Para path="/opt/PSSAU/var/operation" saveDays="10"
<Para path="/var/logs" saveDays="10" rmSubDir="1"

<FilePathGrp name="COUNTER" maxSpace="50" cleanupPercent="50"
> 
Issue 04 (2013-08-30)

167


<Para path="/opt/PSSAU/var/data/MCounter" saveDays="1"
<Para path="/opt/PSSAU/var/data/ReduceMCounter"
<Para path="/opt/PSSAU/var/output/reduceDir"
</FilePathGrp>
<FilePathGrp name="FTP" maxSpace="10" cleanupPercent="50" > <!-maxSpace:Gb-->
<Para path="/opt/PSSAU/var/data/EDR" dirCheckISecs="300"/
>
<Para path="/opt/PSSAU/var/data/PCRF/master"
<Para path="/opt/PSSAU/var/data/PCRF/cu/download"
<Para path="/opt/PSSAU/var/data/PCRF/cu/SUBSCRIBER"
<Para path="/opt/PSSAU/var/data/PCRF/cu/SUBQUOTA"
<Para path="/opt/PSSAU/var/data/PCRF/cu/QUOTA"
<Para path="/opt/PSSAU/var/output/db/
PCRF_SUBSCRIBER_INDEX" dirCheckISecs="300"/>
<Para path="/opt/PSSAU/var/output/logupload"
</FilePathGrp>
<FilePathGrp name="LOG" maxSpace="30" cleanupPercent="50" > <!-maxSpace:Gb-->
<Para path="/opt/PSSAU/var/logs" dirCheckISecs="300"/
>
<Para path="/opt/PSSAU/var/output/log"
<Para path="/opt/PSSAU/var/operation"
<Para path="/var/logs" dirCheckISecs="300"/>
</FilePathGrp>
</FileDelInfo>

<DiskMonitorInfo delaySecs="100" intervalSecs="3600">
<Disk name="/export/home/" alarmSizePercent="75"
deleteSizePercent="90">
<Para path="sysm/PSSAU/var/output"/>
<Para path="sysm/PSSAU/var/data/MCounter"/>
<Para path="sysm/PSSAU/var/data/ReduceMCounter"/>
<Para path="sysm/PSSAU/var/data/EDR"/>
<Para path="sysm/PSSAU/var/data/PCRF"/>
<Para path="sysm/PSSAU/var/operation"/>
<Para path="sysm/PSSAU/var/logs"/>
</Disk>
<Disk name="/" alarmSizePercent="75" deleteSizePercent="90">
<Para path="var/logs"/>
</Disk>
</DiskMonitorInfo>
</FileManagerConfig>
8.
9.
Perform the following substeps to restart SAU services for the setting to take effect.
Issue 04 (2013-08-30)
a.
b.
Start SAU services. For detailed operations, see 8.1.7 Starting SAU Services.
168

Step 6 Perform the following substeps to delete the useless files.
CAUTION
Before clearing up disk space, check that the files you want to delete are no longer required.
Deleting useful files by mistake might cause abnormal system running.
1.
2.
Delete the core files of M2, SAU and eSAU.

The three types of core files are saved in the following directories respectively: /opt/Nastar/
var/logs, /opt/PSSAU/var/logs, and opt/esau/var/logs.
l Delete the core files one week earlier.
l For the core files within one week, contact Huawei technical support engineers.
Delete the core files that the Huawei technical support engineers confirm useless.
3.
Delete all files in the /var/tmp directory after you stop M2 services.
l Stop M2 services. For detailed operations, see 8.1.4 Stopping M2 Server Services.
l Restart M2 services. For detailed operations, see 8.1.3 Starting M2 Server Services.
4.
Delete the log files in /opt/Nastar/var/logs, /opt/PSSAU/var/logs, and opt/esau/var/

logs.
Step 7 Delete the historical data that has been processed by the M2 service process.
1.

users:
2.
Run the following command to navigate to the /opt/Nastar/var/data/nastarm directory.

~> cd /opt/Nastar/var/data/nastarm
3.
Delete all files in survey_bak, survey_missingformater, and survey_invalid_bak.
4.
Delete all files in registerReport_bak.
5.
Delete all files in statusReport_bak.
Step 8 Delete the trace logs of Agent Server.

1.

users.
2.
Run the following command to navigate to the /opt/Nastar/tomcat/logs directory.

3.
Optional: If you need to locate the problems, back up the files in the directory.
4.
Run the following command to delete all files in the directory.

~> rm rf *
5.
Restart the Tomcat service.

a.
Issue 04 (2013-08-30)
Run the following commands to stop the Tomcat service.

169

~> cd /opt/Nastar/
b.
Run the following commands to restart the Tomcat service:

~> cd /opt/Nastar/
----End
12.3.4 Cleaning Up the Disk Space of the Client

available.
Prerequisites
You have installed the client software.
Context
l
You are advised not to delete the files generated on the current day.
You are advised not to delete files when the client is running.
Before you delete a file, check that it can be deleted. Deleting useful files by mistake may
lead to system operation errors.
Procedure
Step 1 Delete historical trace logs.
NOTE
Clearing up disk space tasks involves deleting historical trace logs on the client.
The historical trace logs are saved in the Installation directory of the client software\client
\tracefile directory.
----End
12.4 Monthly Maintenance Items

Monthly maintenance helps the system operate securely, stably, and reliably in a long term.
Monthly maintenance involves checking and setting user rights of M2 server, checking power
supply of the server, and checking M2 system licenses.
Issue 04 (2013-08-30)

170

12.4.1 Checking and Setting M2 Server User Rights

This section describes how to regularly set the M2 user rights to ensure the security of the M2
system.
Procedure
Step 1 Log in to the M2 client as user admin.
Step 2 Choose Security > Security Management.
Step 3 Set the rights of M2 users in the Security Management window.
Adhere to the following principles when you set user rights:
l Delete expired user accounts in time.
l Classify users into different user groups based on user rights, and then assign rights to user
groups instead of users. This minimizes the impact on the performance of the M2 system.
----End
12.4.2 Checking the Power Supply of the Server

This section describes how to check the power supply of the server.
Procedure
Step 1 Check the power supply indicators on the server and the monitor.
In normal cases, all power supply indicators are on and green and all fault indicators are off.
Step 2 To view the power supply failure information recorded in the recent logs by the SUSE Linux
operating system, run the following commands:
# more /var/log/messages
# more /var/log/warn
In normal cases, the logs do not contain any power supply failure information.
Step 3 Check that the power supply of the server works properly.
In normal cases, all the indicators of the external power supply are on and green, and all the fault
indicators are off.
----End
12.4.3 Checking the M2 System License

This section describes how to check the M2 system license to ensure that M2 system services
are running within the valid period.
Prerequisites
l
You have installed the license in the M2 system.
Issue 04 (2013-08-30)

171

Context
A message is displayed one week before the license expires.
Procedure
Step 2 The expiry time of the M2 license is displayed in the first row of the Resource Control Item
table in the License Information dialog box, as shown in Figure 12-1.
Figure 12-1 License information
----End
Issue 04 (2013-08-30)

172

13 FAQs
13
FAQs
About This Chapter

This section describes the common frequently asked questions (FAQs) about the M2 and the
corresponding solutions.
13.1 How Do I Log In to the M2 Server in SSH Mode by Using PuTTY?
This section describes how to log in to the server in SSH mode by using the PuTTY tool.
13.2 How Do I Use FileZilla to Transfer Files?
The M2 supports SFTP transfer by default as SFTP transfer improves the security of file transfer.
FileZilla is a dedicated file transfer tool that supports both SFTP transfer and resumable
download. You are advised to use FileZilla to transfer files.
13.3 How Do I Start M2 System Services? (One-Click)
This section describes how to start M2 system services using the one-click script. After running
the commands to start M2 services, all M2 services are started. The system ignores the M2
processes that are already started and starts only the inactive services.
13.4 How Do I Stop M2 System Services? (One-Click)
This section describes how to stop M2 system services using the one-click script. After running
the commands to stop M2 services, all M2 services are stopped.
This section describers how to start M2 system services. After running the commands to start
M2 system services, all M2 services are started. The system ignores the M2 processes that are
already started and starts only the inactive services.
This section describers how to stop M2 system services. After running the commands to stop
M2 system services, all M2 services are stopped.
Issue 04 (2013-08-30)

173

13 FAQs
13.1 How Do I Log In to the M2 Server in SSH Mode by

Using PuTTY?
This section describes how to log in to the server in SSH mode by using the PuTTY tool.
Prerequisites
l
You have contacted Huawei technical support engineers to obtain PuTTY at http://
support.huawei.com.
Path for Huawei technical support to download the software at http://
support.huawei.com: Software Center > Controlled Tool > Core Network Line >
Wireless OSS > iManager M2000-II > Public Tools.
The PC communicates with the server properly.
Context
CAUTION
After operating system hardening is performed, if you fail to log in to the server as user root in
password authentication mode using SSH, you can log in to the server as a user other than
root, for example, user omcuser, in SSH mode. Then, run the su - root command to switch to
user root.
Procedure
Step 1 Decompress PuTTY.zip. In the decompressed folder, double-click putty.exe. A dialog box is
displayed, as shown in Figure 13-1.
Issue 04 (2013-08-30)

174

13 FAQs
Figure 13-1 PuTTY Configuration
Step 2 Optional: To record operation logs, choose Session > Logging from the left navigation tree,
select Log all session output in the Session logging area, and set the save path of the operation
logs in the Log file name area, as shown in Figure 13-2.
Issue 04 (2013-08-30)

175

13 FAQs
Figure 13-2 Logging
Step 3 Choose Session in the left pane, select SSH in the right pane, enter server IP address in Host
Name (or IP Address), and then click Open to log in to the server, as shown in Figure 13-3.
When PuTTY is started for the first time, the PuTTY Security Alert dialog may be displayed.
Click Yes to continue.
Issue 04 (2013-08-30)

176

13 FAQs
Figure 13-3 Session
Step 4 Type the user name and password for the server to log in to the server as prompted.
login as: root
root@10.148.63.155's password:
Last login: Wed Dec 21 14:04:49 2011 from 192.168.128.100
You are trying to access a restricted zone. Only Authorized Users allowed.
----End
13.2 How Do I Use FileZilla to Transfer Files?

The M2 supports SFTP transfer by default as SFTP transfer improves the security of file transfer.
FileZilla is a dedicated file transfer tool that supports both SFTP transfer and resumable
download. You are advised to use FileZilla to transfer files.
Prerequisites
l
You have obtained the IP address of the destination server.
The communication between the PC and the destination server is normal.
You have obtained the file to be uploaded to the server and have saved the file to the PC.
You have contacted Huawei technical support engineers to obtain FileZilla.zip at http://
support.huawei.com and decompressed it to the PC.
Issue 04 (2013-08-30)

177

13 FAQs
Path for Huawei technical support to download the software at http://

support.huawei.com: Software Center > Controlled Tool > Core Network Line >
Wireless OSS > iManager M2000-II > Public Tools.
l
You have obtained the user password of the destination server.
Procedure
Step 1 Double-click filezilla.exe to start the tool.
Step 2 In the upper left area of the FileZilla window, click
Step 3 In the lower left area of the Site Manager dialog box, click New Site.
Step 4 On the General tab page, set site parameters according to Table 13-1.
Table 13-1 Parameters in the Site Manager dialog box
Parameter
Description
Host
Enter the IP address of the destination server.
Port
22
Port 22 is the default port for SFTP transfer.
Server type
SFTP
Logon type
Normal
User
Enter the user name and password of the destination server. The user has
permission to access the destination directory.
Password
NOTE
l If the user uploads or downloads files, the user must also have the permission to
upload from or download to the destination directory.
l If you cannot connect to the server through SFTP as user root using the FileZilla
after operating system security hardening is performed. To connect to the server
through SFTP, you can use a user account other than root, for example, omcuser.
Step 5 Click Connect.

NOTE
l You can ignore the dialog box displayed during the connection. Click OK in the dialog box.
l After the connection is successful, the Remote Site area displays directory information on the remote
server.
Step 6 In the Remote site area, set the destination directory on the server. For example, /opt.
After you set the directory, the Remote site area displays all files stored in this directory.
Step 7 In the Local site area, set the source directory on the PC. For example, D:\FILE.
After you set the directory, the Local site area displays all files stored in this directory.
Step 8 Perform the following operations as required.
Issue 04 (2013-08-30)

178

13 FAQs
Purpose
Operation
Upload files
In the Local site area, right-click the file to be uploaded and choose
Upload from the shortcut menu.
Download files
In the Remote site area, right-click the file to be downloaded and choose
Download from the shortcut menu.
TIP
If the upload or download fails, click the Failed transfers tab in the lower left area of the FileZilla window.
Then right-click the file that fails to be transferred and choose Reset and requeue selected files from the
shortcut menu to resume the file transfer.
----End
13.3 How Do I Start M2 System Services? (One-Click)

This section describes how to start M2 system services using the one-click script. After running
the commands to start M2 services, all M2 services are started. The system ignores the M2
processes that are already started and starts only the inactive services.
Question
How do I start M2 system services using the one-click script?
Answer
NOTE

M2V100R002C00SPC400OneKeyInstall_pkg.tar or one-click script svc_start.sh is available in the /
export/home/m2install directory by running ls /export/home/m2install.
l
Perform the following steps to start M2 system services if at least one of the above is available.
Start M2 system services by referring to 13.5 How Do I Start M2 System Services? if neither of
them is available.
Step 1 Optional: Log in to the server as user root. Then, run the following commands to decompress
one-click installation packge:
# cd /export/home/m2install
# tar -xvf M2V100R002C00SPC400OneKeyInstall_pkg.tar
Step 2 Check that the Oracle database services are started properly.
1.
Check Oracle database service status. For detailed operations, see 9.1.2 Checking Oracle
Database Running Status.
2.
Start Oracle database services if they are not normally started. For detailed operations, see
9.1.3 Staring Oracle.

Issue 04 (2013-08-30)

179

13 FAQs
Step 4 Run the following commands to start M2 system services:

~> cd /export/home/m2install
~> sh svc_start.sh
Start services:
PSSAU
.......... [OK]
eSAU
.......... [OK]
M2Server
.......... [OK]
l If the preceding information is displayed, M2 system services are started successfully.

l Otherwise, M2 system services fail to be started. If this occurs, perform Step 4 again. If you
fail to start M2 system services several times, contact Huawei technical support engineers.
----End
13.4 How Do I Stop M2 System Services? (One-Click)

This section describes how to stop M2 system services using the one-click script. After running
the commands to stop M2 services, all M2 services are stopped.
Question
How do I stop M2 system services using the one-click script?
Answer
NOTE

M2V100R002C00SPC400OneKeyInstall_pkg.tar or one-click script svc_stop.sh is available in the /
l
Perform the following steps to stop M2 system services if at least one of the above is available.
Stop M2 system services by referring to 13.6 How Do I Stop M2 System Services? if neither of
them is available.
Step 1 Optional: Log in to the server as user root. Then, run the following commands to decompress
one-click installation packge:
# cd /export/home/m2install
# tar -xvf M2V100R002C00SPC400OneKeyInstall_pkg.tar
Step 3 Run the following commands to stop M2 system services:
~> cd /export/home/m2install
~> sh svc_stop.sh
When the following information is displayed, type yes.
Warning : you are going to stop all products' services
Are you going to continue [yes/no]: yes
Issue 04 (2013-08-30)

180

13 FAQs
If the following information is displayed, all the services are stopped. Otherwise, perform Step
4 to forcibly stop services.
PSSAU
.......... [OK]
eSAU
.......... [OK]
M2Server .......... [OK]
Step 4 Perform the following step to forcibly stop M2 services if you fail to stop the services in Step
3. Otherwise, skip this step.
1.
Run the following commands to forcibly stop the SAU process:

~> cd /opt/PSSAU
~> . svc_profile.sh
~> ps_kill
2.
Run the following commands to forcibly stop the eSAU process:

~> cd /opt/esau
~> . svc_profile.sh
~> esau_kill
3.
Run the following commands to forcibly stop the M2 daemon process:

~> cd /opt/Nastar
~> . svc_profile.sh
~> kill_daem
4.
l If no command output is displayed, the TAO process has been stopped.
l If there is any command output, the TAO process has not been stopped. If this occurs,
run the following command to forcibly stop the TAO process:
~> kill 9 Process ID
Process ID in the preceding command indicates the process ID in the second column
of the command output.
----End

This section describers how to start M2 system services. After running the commands to start
M2 system services, all M2 services are started. The system ignores the M2 processes that are
already started and starts only the inactive services.
Question
How do I start M2 system services?
Issue 04 (2013-08-30)

181

13 FAQs
Answer
NOTE

M2V100R002C00SPC400OneKeyInstall_pkg.tar or one-click script svc_start.sh is available in the /
l
Start M2 system services by referring to 13.3 How Do I Start M2 System Services? (One-Click)
if at least one of the above is available.
Perform the following steps to start M2 system services if neither of them is available.
Step 1 Start M2 services.

1.
Log in to the server as user omcuser, and then run the following command to navigate to
the installation directory of the M2 server software (the default installation directory of the
M2 server software is /opt/Nastar):
~> cd /opt/Nastar
2.
Run the following commands to start the M2 services:

~> start_svc
3.
Run the following command to check whether all M2 services are stared.
Check the value of the parameter Not Running: If the parameter value is 0, all services
are normally started. Otherwise, some M2 services are not started.
Step 2 Start eSAU services.

1.
2.
Run the following commands to start eSAU services:

~> cd /opt/esau
~> esau_start
3.
Run the following command to check whether all eSAU services are stared.
~> esau_ps
are normally started. Otherwise, some eSAU services are not started.
Step 3 Start SAU services.

1.
2.
Run the following commands to start SAU services:

~> cd /opt/PSSAU
~> ps_start
3.
Issue 04 (2013-08-30)
Run the following command to check whether all SAU services are stared.
182

13 FAQs
~> ps_query
are normally started. Otherwise, some SAU services are not started.
Step 4 Start Agent Server service.
1.
~> cd /opt/Nastar
2.
Run the following commands to start the Tomcat service:

When the following or similar information is displayed, Tomcat service is running.
service starting...
service startup successful.
Step 5 Start GaussDB database services.

1.
Log in to the server as user gaussdba.

Run the following command to switch to user gaussdba if you have logged in to the server
as other users:
~> su - gaussdba
2.
Run the following command to start GaussDB database services:

~> gs_ctl start -l db.log -D /opt/gaussdb/data
If the information similar to the following is displayed, GaussDB database services are
started.
server starting.... done
server started
----End

This section describers how to stop M2 system services. After running the commands to stop
M2 system services, all M2 services are stopped.
Question
How do I stop M2 system services?
Issue 04 (2013-08-30)

183

13 FAQs
Answer
NOTE

M2V100R002C00SPC400OneKeyInstall_pkg.tar or one-click script svc_stop.sh is available in the /
l
Stop M2 system services by referring to 13.4 How Do I Stop M2 System Services? (One-Click) if
at least one of the above is available.
Perform the following steps to stop M2 system services if neither of them is available.
Step 1 Stop M2 services.

1.
~> cd /opt/Nastar
2.
Run the following commands to stop the M2 Server services.

~> stop_svc
3.
Run the following command to check whether the service processes are stopped:
~> svc_ps
l If no command result is displayed, the service processes are stopped.
l If any command result is displayed, run the kill_svc command to forcibly stop the
running service processes.
4.
Run the following command to stop the daemon process:

~> stop_daem
5.
Run the following command to check whether the daemon process is stopped:
~> daem_ps
l If no command result is displayed, the daemon process is stopped.
l If any command result is displayed, run the kill_daem command to forcibly stop the
daemon.
6.
l If no command result is displayed, the TAO process is stopped.
l If any command result is displayed, run the stop_tao_services command to forcibly
stop the TAO process.
Step 2 Stop eSAU services.

1.
2.
Run the following commands to stop the eSAU services:

~> cd /opt/esau
Issue 04 (2013-08-30)

184

13 FAQs
~> esau_stop
3.
Run the following command to ensure that all eSAU services have stopped:
~> esau_ps
eSAU...............................not running
l If the value of Running is 0, eSAU services are stopped.

l If the value of Running is not 0, run esau_kill to forcibly stop eSAU services.
Step 3 Stop SAU services.
1.
2.
Run the following commands to stop the SAU services:

~> cd /opt/PSSAU
~> ps_stop
3.
Run the following command to ensure that all SAU services have stopped:
~> ps_query
l If no command output is displayed, the SAU services have stopped.
l If any command output is displayed, run the ps_kill command to forcibly stop the
services.
Step 4 Stop Agent Server service.

1.
~> cd /opt/Nastar
2.
Run the following commands to stop the Tomcat service:

When the following or similar information is displayed, Tomcat service is stopped.
service stopping...
Step 5 Stop GaussDB database services.

1.
Log in to the server as user gaussdba.

Run the following command to switch to user gaussdba if you have logged in to the server
as other users:
Issue 04 (2013-08-30)

185

13 FAQs
~> su - gaussdba
2.
Run the following command to stop GaussDB database services:

~> gs_ctl stop -m fast
If the information similar to the following is displayed, GaussDB database services are
stopped.
waiting for server to shut down.... done
server stopped
----End
Issue 04 (2013-08-30)

186

GENEX Mobile Manager Administrator Guide (HP) (V100R002C00 - 04) (PDF) - en

Încărcat de

Informații document

Titlu original

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

GENEX Mobile Manager Administrator Guide (HP) (V100R002C00 - 04) (PDF) - en

Încărcat de

Drepturi de autor:

Formate disponibile

GENEX Mobile Manager

Administrator Guide (HP)

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential