M2000 Administrator Guide-3850&3650-SUSE10-V200R012 - 06

M2000
V200R012
Administrator Guide (x3850&x3650,
SUSE10)
Issue 06
Date 2013-07-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior 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 06 (2013-07-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Overview
This document is intended for the M2000 administrator. It is applicable to the IBM x3850 X5
and IBM x3650 M3 servers and based on the SUSE Linux operating system and the Oracle
database. In addition, this document provides concepts related to M2000 system management
tasks and the detailed operation procedures, M2000 system routine maintenance, M2000
processes and service , and descriptions of frequently used commands and tools. This document
applies to the core network IMS field and the enterprise wireless solution.
Product Version
Product versions corresponding to this document are as follows:
Product Name Product Version
M2000 V200R012C00&V200R012C01

Intended Audience
This document is intended for network management engineers.
Change History
06 (2013-07-30)
This issue is the sixth release of V200R012C00 and fourth release of V200R012C01. Compared
with issue 05 (2012-12-30), this issue incorporates the changes listed in the following table.
Change Description
1 Routine Maintenance Items Descriptions are changed.
10.4 Viewing Hardware Status on the
IMM
New

M2000
Administrator Guide (x3850&x3650, SUSE10) About This Document
ii
05 (2012-12-30)
This issue is the fifth release of V200R012C00 and third release of V200R012C01. Compared
Change Description
4.3 Setting the M2000 Server as an
Intermediate-Layer NTP Server
Descriptions are changed.
6 Managing M2000 Users Descriptions are changed.
13.5 How Do I Handle the Shortage of
Disk Space on the M2000 Server (SUSE)
New

04 (2012-09-20)
This issue is the fourth release of V200R012C00 and second release of V200R012C01.
Compared with issue 03 (2012-07-20), this issue incorporates the changes listed in the following
table.
Change Description
4 Configuring the NTP Service Descriptions are changed.
3 Configuring the Parameters of the
M2000 Server
Descriptions are changed.

03 (2012-07-20)
This issue is the third release of V200R012C00 and first release of V200R012C01. Compared
Change Description
3.2 Changing the Host Name of the Server New
13 FAQ New

02 (2012-06-20)
This issue is the second official release. Compared with issue 01 (2012-04-20), this issue
incorporates the changes listed in the following table.
Change Description
3.3 Changing the IP Address of the IMM New
5 Changing the Time Zone and Time on the
M2000 Server (SUSE)
New
M2000
iii
Change Description
12 Backing Up and Restoring the M2000
System (SUSE)
New

01 (2012-04-20)
This issue is the first official release. Compared with issue Draft A (2012-02-27), this issue does
not incorporate any changes.
Draft A (2012-02-27)
This issue is a draft.
Organization
1 Routine Maintenance Items
This section describes the recommended maintenance items of the M2000 system.
2 Powering On/Off the System
This section describes how to power on and power off the M2000 system when IBM x3850
X5 or IBM x3650 M3 acts as the M2000 server.
3 Configuring the Parameters of the M2000 Server
This section describes how to configure the parameters of the M2000 server.
4 Configuring the NTP Service
This section describes how to set the M2000 server as an NTP client or an intermediate-layer
NTP server.
5 Changing the Time Zone and Time on the M2000 Server (SUSE)
This section describes how to set the time zone and the time on the server.
6 Managing M2000 Users
This section describes how to manage OS users and database users of the M2000 system.
7 Managing M2000 and NE Logs
This section describes how to manage the operation logs, system logs, and security logs of the
M2000 and NEs. You can also manage the operating system logs. By querying or collecting
statistics on logs, engineers can trace user behaviors. This facilitates system diagnosis and
maintenance.
8 Managing the M2000 Processes and Services
This section describes how to manage the M2000 processes so that the processes and services
on the M2000 server can function properly. The enterprise wireless network solution does not
support northbound functions and therefore there is no northbound process.
9 Managing M2000 Database
M2000
iv
This section describes how to manage the M2000 database. This first describes the concepts of
the M2000 database including database type and status. Then describes how to view the database
status, start or stop the database, and check the database space.
10 Managing Disks and Hardware
This section describes how to manage the disks and hardware on the M2000 server.
11 Managing License
This section describes how to query and update the license file on the M2000 server through the
M2000 client.
12 Backing Up and Restoring the M2000 System (SUSE)
This section describes how to back up and restore the M2000 system.
13 FAQ
This section describes some FAQs and their solutions.
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.
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.
M2000
v
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.
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.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.

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

Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action 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.
M2000
vii
Contents
About This Document.....................................................................................................................ii
1 Routine Maintenance Items........................................................................................................1
2 Powering On/Off the System......................................................................................................2
2.1 Powering on the System Securely..................................................................................................................................3
2.2 Powering off the System Securely..................................................................................................................................6
3 Configuring the Parameters of the M2000 Server...................................................................9
3.1 Changing the IP Address of the M2000 Server............................................................................................................10
3.2 Changing the Host Name of the Server........................................................................................................................12
3.3 Changing the IP Address of the IMM..........................................................................................................................14
4 Configuring the NTP Service....................................................................................................16
4.1 Methods for Configuring the NTP Service on the M2000 Server................................................................................17
4.2 Setting the M2000 Server as the NTP Client...............................................................................................................18
4.3 Setting the M2000 Server as an Intermediate-Layer NTP Server................................................................................21
4.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE).......................................................24
4.5 Configuring the NTP Service of the M2000 Client......................................................................................................24
5 Changing the Time Zone and Time on the M2000 Server (SUSE).....................................28
5.1 Introduction to the DST................................................................................................................................................29
5.2 Changing the Time Zone and Time of the M2000 Server (Non-DST, SUSE).............................................................29
5.3 Changing the Time Zone and Time of the M2000 Server (DST, SUSE).....................................................................31
6 Managing M2000 Users..............................................................................................................35
6.1 User Type.....................................................................................................................................................................36
6.2 Changing the Password of User root (SUSE)...............................................................................................................39
6.3 Changing the Password of User ossuser (SUSE).........................................................................................................39
6.4 Changing the Password of User ftpuser.......................................................................................................................40
6.5 Changing the Password of User oracle.........................................................................................................................42
6.6 Changing the Password of User in the Oracle Database..............................................................................................43
6.7 Changing the Password of the IMM User....................................................................................................................44
7 Managing M2000 and NE Logs.................................................................................................47
7.1 Overview of Log Management.....................................................................................................................................48
7.1.1 Log Management Function........................................................................................................................................48
M2000
Administrator Guide (x3850&x3650, SUSE10) Contents
viii
7.1.2 Log Types..................................................................................................................................................................48
7.1.3 Log Templates...........................................................................................................................................................58
7.1.4 Procedure for Reporting NE Logs.............................................................................................................................58
7.1.5 Technical Specifications of Log Management..........................................................................................................62
7.2 Synchronizing NE Logs................................................................................................................................................62
7.3 Importing NE Logs.......................................................................................................................................................65
7.4 Managing the M2000 Operation Logs..........................................................................................................................66
7.4.1 Querying the M2000 Operation Logs........................................................................................................................66
7.4.2 Collecting Statistics on the M2000 Operation Logs..................................................................................................69
7.5 Managing the M2000 System Logs..............................................................................................................................70
7.5.1 Querying the M2000 System Logs............................................................................................................................70
7.5.2 Collecting Statistics on the M2000 System Logs......................................................................................................72
7.6 Managing the M2000 Security Logs............................................................................................................................73
7.6.1 Querying the M2000 Security Logs..........................................................................................................................74
7.6.2 Collecting Statistics on the M2000 Security Logs....................................................................................................76
7.7 Managing NE Operation Logs......................................................................................................................................77
7.7.1 Querying NE Operation Logs....................................................................................................................................77
7.7.2 Collecting Statistics on NE Operation Logs..............................................................................................................78
7.8 Managing NE Secrity Logs..........................................................................................................................................79
7.8.1 Querying NE Security Logs......................................................................................................................................80
7.8.2 Collecting Statistics on NE Security Logs................................................................................................................80
7.9 Browsing the NE Syslog Run Logs..............................................................................................................................82
7.10 Querying MML Logs..................................................................................................................................................82
7.11 Managing Log Data....................................................................................................................................................84
7.11.1 Setting M2000 Log Dumping..................................................................................................................................84
7.11.2 Setting M2000 Log Export......................................................................................................................................85
7.11.3 Setting NE Log Export............................................................................................................................................86
7.12 Setting M2000 Log Templates...................................................................................................................................87
7.13 References for Log Management Interfaces...............................................................................................................88
7.13.1 Interface Description: Log Management.................................................................................................................88
7.13.2 Parameters for Querying Operation Logs ...............................................................................................................89
7.13.3 Parameters for Collecting Statistics on Operation Logs..........................................................................................91
7.13.4 Parameters for Querying System Logs....................................................................................................................94
7.13.5 Parameters for Collecting Statistics on System Logs..............................................................................................96
7.13.6 Parameters for Querying Security Logs..................................................................................................................98
7.13.7 Parameters for Collecting Statistics on Security Logs..........................................................................................100
7.13.8 Parameters for Querying NE Operation Logs.......................................................................................................103
7.13.9 Parameters for Statistics on NE Operation Logs...................................................................................................104
7.13.10 Parameters for Querying NE Security Logs........................................................................................................106
7.13.11 Parameters for Statistics on NE Security Log.....................................................................................................107
7.13.12 Parameters for Setting M2000 Log Timing Export.............................................................................................110
7.13.13 Parameters for Setting M2000 Log Timing Dump..............................................................................................112
M2000
ix
7.13.14 Parameters for the Export of NE Logs................................................................................................................115
7.13.15 Parameters for Querying NE Syslog Run Logs...................................................................................................116
8 Managing the M2000 Processes and Services......................................................................119
8.1 Introduction to M2000 Processes and Services..........................................................................................................120
8.1.1 3rdTool_agent Process............................................................................................................................................120
8.1.2 ActiveMQ Process...................................................................................................................................................120
8.1.3 adn_agent Process....................................................................................................................................................120
8.1.4 adss_agent Process..................................................................................................................................................120
8.1.5 antenna_agent Process.............................................................................................................................................120
8.1.6 ce_agent Process......................................................................................................................................................121
8.1.7 cmdc_agent Process.................................................................................................................................................121
8.1.8 cmengine_agent Process..........................................................................................................................................121
8.1.9 cmeserver_agent Process.........................................................................................................................................121
8.1.10 cmexp_agent Process.............................................................................................................................................121
8.1.11 cmserver_agent Process.........................................................................................................................................122
8.1.12 corba_agent Process..............................................................................................................................................122
8.1.13 cpm_agent Process................................................................................................................................................122
8.1.14 devdoc_agent Process............................................................................................................................................123
8.1.15 DrlDm Process.......................................................................................................................................................123
8.1.16 dsXXXX agent Process...........................................................................................................................................123
8.1.17 eam_agent Process.................................................................................................................................................123
8.1.18 fars_agent Process.................................................................................................................................................124
8.1.19 fmmedXXXX_agent Process..................................................................................................................................124
8.1.20 fmnotify_agent Process.........................................................................................................................................124
8.1.21 FMPreServiceXXXX_agent Process......................................................................................................................124
8.1.22 fnlicense_agent Process.........................................................................................................................................125
8.1.23 gem_agent Process................................................................................................................................................125
8.1.24 glmssyn_agent Process..........................................................................................................................................125
8.1.25 ifms_agent Process................................................................................................................................................125
8.1.26 ipm_agent Process.................................................................................................................................................126
8.1.27 irp_agent Process...................................................................................................................................................126
8.1.28 itm_agent Process..................................................................................................................................................127
8.1.29 lic_agent Process...................................................................................................................................................127
8.1.30 log_agent Process..................................................................................................................................................127
8.1.31 maintain_agent Process.........................................................................................................................................128
8.1.32 manager_agent Process..........................................................................................................................................128
8.1.33 medXXXX_agent Process.......................................................................................................................................128
8.1.34 ncc0X01_agent Process.........................................................................................................................................129
8.1.35 necomm_agent Process..........................................................................................................................................129
8.1.36 nelicense_agent Process........................................................................................................................................129
8.1.37 neuser_agent Process.............................................................................................................................................129
8.1.38 ngnffs_agent Process.............................................................................................................................................130
M2000
x
8.1.39 ngnni112_agent Process........................................................................................................................................130
8.1.40 ngnnis_agent Process.............................................................................................................................................130
8.1.41 ngntestmanage_agent Process...............................................................................................................................130
8.1.42 nhcservice_agent Process......................................................................................................................................130
8.1.43 nicservice_agent Process.......................................................................................................................................130
8.1.44 nimserver_agent Process.......................................................................................................................................131
8.1.45 nms_mml_agent Process.......................................................................................................................................131
8.1.46 partition_agent Process..........................................................................................................................................131
8.1.47 pm_agent Process..................................................................................................................................................131
8.1.48 pmengine0X01_agent Process...............................................................................................................................132
8.1.49 pmexp_agent Process............................................................................................................................................132
8.1.50 pmmon_agent Process...........................................................................................................................................132
8.1.51 porttrunk_agent Process........................................................................................................................................132
8.1.52 proxy_agent Process..............................................................................................................................................133
8.1.53 PRSAssistantService_agent Process......................................................................................................................133
8.1.54 prsdc_agent Process...............................................................................................................................................133
8.1.55 prsfs_agent Process................................................................................................................................................133
8.1.56 prsreport_agent Process.........................................................................................................................................134
8.1.57 prssum_agent Process............................................................................................................................................134
8.1.58 rn_agent Process....................................................................................................................................................134
8.1.59 ScriptModuleService_agent Process.....................................................................................................................134
8.1.60 scriptserver_agent Process.....................................................................................................................................134
8.1.61 sm_agent Process...................................................................................................................................................135
8.1.62 snm_agent Process.................................................................................................................................................135
8.1.63 snmp_agent Process...............................................................................................................................................135
8.1.64 sso_agent Process..................................................................................................................................................135
8.1.65 swm_agent Process................................................................................................................................................135
8.1.66 SyslogCollectorDM Process..................................................................................................................................136
8.1.67 threshold_agent Process........................................................................................................................................136
8.1.68 trapdispatcher Process...........................................................................................................................................136
8.1.69 uap_agent Process..................................................................................................................................................136
8.1.70 xftpXX01_agent Process........................................................................................................................................137
8.1.71 xmlagent Process...................................................................................................................................................137
8.1.72 Trace Server Services and Processes.....................................................................................................................137
8.1.73 Processes and Services Related to Each Northbound Interface.............................................................................138
8.1.74 Processes Used by RTN, Router, Switch, Firewall, and SVN..............................................................................139
8.2 Viewing the Running Status of M2000 Services (SUSE)..........................................................................................141
8.3 Starting the M2000 Services (SUSE).........................................................................................................................142
8.4 Stopping the M2000 Services (SUSE).......................................................................................................................142
9 Managing M2000 Database......................................................................................................144
9.1 Introduction to the M2000 Database (Oracle)............................................................................................................145
9.1.1 cmedb.......................................................................................................................................................................145
M2000
xi
9.1.2 eamdb.......................................................................................................................................................................145
9.1.3 farsdb.......................................................................................................................................................................146
9.1.4 fmdb.........................................................................................................................................................................147
9.1.5 itfndb........................................................................................................................................................................147
9.1.6 logdb........................................................................................................................................................................148
9.1.7 omcdb......................................................................................................................................................................148
9.1.8 osstempdb................................................................................................................................................................150
9.1.9 pmcomdb.................................................................................................................................................................151
9.1.10 pmdb......................................................................................................................................................................153
9.1.11 smdb.......................................................................................................................................................................153
9.1.12 swmdb....................................................................................................................................................................154
9.1.13 topodb....................................................................................................................................................................155
9.2 Checking Oracle Services...........................................................................................................................................155
9.3 Starting Oracle Service...............................................................................................................................................157
9.4 Stopping Oracle Service.............................................................................................................................................159
9.5 Checking Database Space...........................................................................................................................................160
10 Managing Disks and Hardware............................................................................................162
10.1 Viewing the CPU and Memory Usage of the M2000 Server...................................................................................163
10.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands.......................................................164
10.3 Clearing the Disk Space of the M2000 Server (SUSE)............................................................................................164
10.4 Viewing Hardware Status on the IMM.....................................................................................................................166
11 Managing License....................................................................................................................168
11.1 Querying the M2000 License...................................................................................................................................169
11.2 Updating the M2000 License...................................................................................................................................169
12 Backing Up and Restoring the M2000 System (SUSE).....................................................171
12.1 Introduction to the M2000 Backup and Restore Solution (SUSE)...........................................................................172
12.2 Backing Up and Restoring the M2000 Dynamic Data (SUSE)................................................................................173
12.2.1 Periodically Backing Up M2000 Dynamic Data (SUSE).....................................................................................173
12.2.2 Manually Backing Up M2000 Dynamic Data (SUSE).........................................................................................175
12.2.3 Restoring the M2000 Dynamic Data (SUSE)........................................................................................................176
13 FAQ............................................................................................................................................179
13.1 How Do I Solve the Problem That the IMM Remote Window Does Not Respond?...............................................180
13.2 How Do I Set Internet Explorer on the PC?.............................................................................................................180
13.3 How Do I Handle the Problem of Certificate Error or Untrusted Website Displayed in the Web Browser (IMM)?
..........................................................................................................................................................................................181
13.4 How Do I Set on the IMM Operation Interface to Change Two Cursors to One Cursor?.......................................186
13.5 How Do I Handle the Shortage of Disk Space on the M2000 Server (SUSE).........................................................186
M2000
xii
1 Routine Maintenance Items
This section describes the recommended maintenance items of the M2000 system.
Table 1-1 lists the recommended maintenance items of the M2000. You can add or delete
maintenance items according to your requirements.
Table 1-1 Maintenance item list
No. Item Frequency
1 8.2 Viewing the Running Status of
M2000 Services (SUSE)
Daily
2 9.2 Checking Oracle Services Daily
3 9.5 Checking Database Space Monthly
4 10.1 Viewing the CPU and Memory
Usage of the M2000 Server
Daily
5 10.2 Viewing the Disk Usage of the
M2000 Server by Running SUSE
Commands
Weekly
6 11.1 Querying the M2000 License Monthly
7 10.4 Viewing Hardware Status on the
IMM
Daily
M2000
Administrator Guide (x3850&x3650, SUSE10) 1 Routine Maintenance Items
1
2 Powering On/Off the System
About This Chapter
This section describes how to power on and power off the M2000 system when IBM x3850
X5 or IBM x3650 M3 acts as the M2000 server.
2.1 Powering on the System Securely
This section describes how to power on the M2000 hardware devices and related cautions when
the IBM x3850 X5 or IBM x3650 M3 is used as the M2000 server.
2.2 Powering off the System Securely
This section describes how to power off the M2000 hardware devices and related cautions when
M2000
Administrator Guide (x3850&x3650, SUSE10) 2 Powering On/Off the System
2
2.1 Powering on the System Securely
This section describes how to power on the M2000 hardware devices and related cautions when
Prerequisites
l The components of the M2000 system are installed in the cabinet. Before you power on
the cabinet, ensure that the power switch of the cabinet power distribution box (PDB) must
be disabled.
l After the cabinet is powered on, the device power switch is connected to the cabinet power
control panel.
l Before M2000 delivery, the HTTPS protocol is selected for you to log in to the server by
using the Integrated Management Module (IMM); if you attempt to select HTTP for login,
the protocol will be automatically converted to HTTPS. To log in to the server according
to HTTP, ensure that ports 80 and 443 have been opened on the IMM and the local PC. To
log in to the server according to HTTPS, ensure that port 443 has been opened on the IMM
and the local PC.
Context
The system can be powered on using either one of the following methods:
l Power on the system using the power switch of the server.
l Power on the system using the remote management network port of the Integrated
Management Module (IMM). IP address, user name and password of the IMM network
port vary according to the actual live network planning.
Procedure
l Power on the system using the power switch of the server.
1. Turn on the power switch of the server to start the server.
Figure 2-1 shows the operation panel of the x3850 server.
M2000
3
Figure 2-1 Operation panel of the x3850 server
Power switch/
Power indicator

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

2. Check the power indicator status of the server after the system is powered on, and
steady green indicates the server is running properly.
l Power on the system using IMM.
1. Set Internet Explorer on the PC by referring to 13.2 How Do I Set Internet Explorer
on the PC?.
2. Connect the PC and the M2000 server through the local area network (LAN) switch.
a. Connect the system management network port on the M2000 server to the
network interface on the LAN switch using straight-through cable.
b. Connect the PC to the network interface on the LAN Switch using straight-
through cable.
c. Set the IP address of the PC on the same network segment (192.168.70.xx for
example) as the IP address of the system management network port on the
M2000 server.
M2000
4
For example, configure the network card of the PC as follows:
Set IP address to 192.168.70.35.
Set Subnet mask to 255.255.255.0.
Leave Default gateway, Preferred DNS server and Alternate DNS
server empty.
3. Type http://192.168.70.125 or https://192.168.70.125 in the address bar of the
Internet Explorer.Then press Enter to access the IMM login window.
Before M2000 delivery, the HTTPS protocol is selected for you to log in to the
server by using the Integrated Management Module (IMM); if you attempt to select
HTTP for login, the protocol will be automatically converted to HTTPS. To log
in to the server according to HTTP, ensure that ports 80 and 443 have been opened
on the IMM and the local PC. To log in to the server according to HTTPS, ensure
that port 443 has been opened on the IMM and the local PC.
192.168.70.125 is an example and must be replaced by the actual IP address of the
IMM.
If the web browser displays certificate error or untrusted website, install certificates
for the web browser by referring to 13.3 How Do I Handle the Problem of
Certificate Error or Untrusted Website Displayed in the Web Browser
(IMM)?.
4. Type the user name USERID and password of IMM. Changeme_123 is the default
password and needs to be replaced with the actual password. Click Login to access
the window for setting the idle disconnection duration.
5. Click Continue to access the IMM home page.
6. In the navigation tree, choose System > Tasks > Remote Control.
7. In the displayed window, select Use the ActiveX Client with Microsoft Internet
Explorer, and click Start Remote Control in Multi-User Mode.
8. In the displayed window, choose Tools > Power > On.
9. In the displayed window, click Yes.
After the system is powered on, a power-on page is displayed, as shown in Figure
2-3.
M2000
5
Figure 2-3 Startup page

----End
2.2 Powering off the System Securely
This section describes how to power off the M2000 hardware devices and related cautions when
Prerequisites
Log in to the server as user root through Security Shell Protocol (SSH).
Context
To securely power off the system, disable the M2000 service, the database interception and
database services, and then the server in order.
Procedure
Step 1 Stop the M2000 service.
Check whether the M2000 is started by referring to 8.2 Viewing the Running Status of M2000
Services (SUSE). Stop the M2000 services if they are running. For how to stop the M2000
services, see 8.4 Stopping the M2000 Services (SUSE).
Step 2 Disable the database interception and database services.
M2000
6
1. Run the following commands to check the status of the database interception.
$ su - oracle
> lsnrctl status
When the following information is displayed, the database interception is in running status:
Service "+ASM" has 1 instance(s).
Instance "+ASM", status READY, has 1 handler(s) for this service...
Service "+ASM_XPT" has 1 instance(s).
Service "ossdb" has 2 instance(s).
Instance "ossdb", status UNKNOWN, has 1 handler(s) for this service...
Instance "ossdb", status READY, has 1 handler(s) for this service...
Service "ossdbXDB" has 1 instance(s).
Service "ossdb_XPT" has 1 instance(s).
The command completed successfully
2. Run the following commands to disable the database interception.
> lsnrctl stop
If the following information has been displayed, the database interception is disabled
successfully. Otherwise, the database interception is not disabled. In this case, contact
Huawei technical support.
3. Run the following command to disable the Oracle database services.
a. Run the following command to stop the ORACLE instance.
> sqlplus / as SYSDBA
SQL> shutdown immediate
If the following information is displayed, the ORACLE instance has been disabled.
Otherwise, the ORACLE instance is not stopped. In this case, contact Huawei
technical support.
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
b. Run the following command to stop the ASM instance.
> ORACLE_SID=+ASM
If the following information is displayed, the ASM instance has been disabled.
Otherwise, the ASM instance is not stopped. In this case, contact Huawei technical
support.
ASM diskgroups dismounted
ASM instance shutdown
SQL> exit
4. Run the following command to exit user oracle.
> exit
M2000
7
Step 3 Run the following commands to disable the server:
$ sync; sync; sync; sync; sync; sync
$ shutdown -h now
It takes about 5 minutes to disable the server. If the power indicator on the operator information
pane turns from steady green to blinking green, the system is disabled. Then, go to Step 4.
Figure 2-4 Operator information pane

Step 4 Power off other devices and the cabinet.
----End
M2000
8
3 Configuring the Parameters of the M2000
Server
About This Chapter
This section describes how to configure the parameters of the M2000 server.
3.1 Changing the IP Address of the M2000 Server
This section describes how to change the IP address of the M2000 server to ensure that the IP
address of the server meets the requirements.
3.2 Changing the Host Name of the Server
This section describes how to change the host name of the M2000 server based on site
requirements.
3.3 Changing the IP Address of the IMM
This section describes how to change the IP address of the integrated management module
(IMM) on the M2000.
M2000
Administrator Guide (x3850&x3650, SUSE10) 3 Configuring the Parameters of the M2000 Server
9
3.1 Changing the IP Address of the M2000 Server
This section describes how to change the IP address of the M2000 server to ensure that the IP
address of the server meets the requirements.
Prerequisites
l The M2000 server application is installed.
l You have logged in to the server as user root in SSH mode.
Context
l When you are changing the IP addresses of the M2000 servers, the performance data and
alarm data of the managed NEs cannot be processed.
l After you change the IP addresses of the servers, the M2000 collects performance data and
alarm data again through automatic synchronization and then processes the data.
l If the IP addresses of the M2000 servers are recorded in the NE database, changing the IP
address of theM2000 server leads to the disconnection between the M2000 server and the
NEs. When you change the IP addresses of the M2000 servers, update the IP address of the
M2000 server in the NE database concurrently.
Procedure
Step 1 Check the IP address of the server.
$ ifconfig -a
If the IP address of the server is incorrect, perform the following steps:
Step 2 Check whether the new IP address is already occupied.
This part takes changing the old IP address 10.10.10.10 to the new IP address 192.168.8.12 as
an example.
$ ping 192.168.8.12
l If the new IP address can be pinged, the new IP address is occupied and you need to use other
new IP address.
l If the new IP address cannot be pinged, the new IP address is idle and you can use this IP
address.
Step 3 Check whether the M2000 is started by referring to 8.2 Viewing the Running Status of M2000
Services (SUSE). Stop the M2000 services if they are running. For how to stop the M2000, see
8.4 Stopping the M2000 Services (SUSE).
Step 4 Check whether the Oracle is started by referring to 9.2 Checking Oracle Services. If the Oracle
is not started, start it by referring to 9.3 Starting Oracle Service.
Step 5 Perform the following operations to change the IP addresses of the M2000 servers.
1. Run the modify.sh script.
$ . /opt/oss/server/svc_profile.sh
$ cd /opt/oss/server/rancn/tools/modifytool
M2000
10
$ ./modify.sh
2. When the main menu is displayed, choose 1--IP.
------------------------------------------------------------------
Welcome to use Modify tool
Modify Tool (2.0.0)
------------------------------------------------------------------
------------------------------------------------------------------
Please select a(n) operator type
1--IP
2--Database password
3--Password of ftpuser
4--Hostname
R--Return
Q--Quit
------------------------------------------------------------------
Please make a choice[1-4]:
3. Change the IP address, subnet mask, and default route according to system outputs.
------------------------------------------------------------------
Note: -- Enter key f/F to finish ip input old-new ip pairs
-- Enter key p/P to return pre-step
-- Enter key q/Q to exit this tools
------------------------------------------------------------------
Please input the old ip[default 10.121.71.138]:
Please input the new ip[default 10.121.71.138]: 10.121.71.181
Please input the old ip[default 10.121.71.182]:
Please input the database superuser's password:
Please input the old mask number[default 255.255.255.0]:
Please input the new mask number[default 255.255.255.0]:
Please input the old router[default 10.121.71.1]:
Please input the new router[default 10.121.71.1]:
NOTE
l If you need to change multiple IP addresses by running the modify.sh script, type all previous
addresses to be changed and their new values here.
l Press Enter to use the default value in the system output.
l The script displays the IP addresses that are already configured in the system in sequence. If you
do not need to change a certain IP address, press Enter to proceed with the next step.
l Type p/P to return to the function menu of the modify.sh script. Then, you are prompted to
perform operations such as changing the IP address and user password.
l You can type q/Q to exit the modify.sh script.
l When the system prompts you to type the previous IP addresses, type f/F to finish typing IP
addresses and proceed with the next step.
4. When the following information is displayed, type Y and press Enter.
Are you sure to continue?
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]: Y
NOTE
l You can type Q to exit the script without performing any operations.
l You can type R to return to the previous step to reconfigure relevant parameters.
l You can type P to return to the function menu of the modify.sh script. Then, you are prompted
to perform operations such as changing the IP address and user password.
l Running the modify.sh script to change the server IP addresses takes about three minutes. Please
wait.
5. When the following information is displayed, the change is successful.
------------------------------------------------------------------
Operation complete!
M2000
11
If the system output contains failed, the change fails. Contact Huawei technical support.
Step 6 Run the following commands to restart the server:
$ shutdown -r now
After the server is restarted, both the Oracle and M2000 services are automatically restarted.
Step 7 Log in to the server by using the new IP address as user root in SSH mode, and check the status
of the Oracle and M2000 services.
NOTE
If the login fails or the Oracle and M2000 services are abnormal after the server is restarted, contact Huawei
technical support.
l For how to view the Oracle service, see 9.2 Checking Oracle Services.
l For how to check the status of the M2000 services, see 8.2 Viewing the Running Status of
M2000 Services (SUSE).
----End
3.2 Changing the Host Name of the Server
This section describes how to change the host name of the M2000 server based on site
requirements.
Prerequisites
You have logged in to the M2000 server as user root.
Procedure
Step 1 If the M2000 services are running, stop them.
1. Check the status of the M2000 services.
For details, see and How Do I Check the Status of the M2000 Services?.
2. Stop M2000 services.
For details, see How Do I Stop M2000 Services.
Step 2 Check whether the Oracle is started by referring to 9.2 Checking Oracle Services. If the Oracle
is not started, start it by referring to 9.3 Starting Oracle Service.
Step 3 Run the modify.sh script.
$ ./modify.sh
Step 4 Type 4 and press Enter.
------------------------------------------------------------------
Modify Tool (2.0.0)
------------------------------------------------------------------
M2000
12
------------------------------------------------------------------
1--IP
4--Hostname
R--Return
Q--Quit
------------------------------------------------------------------
Step 5 Press Enter and change the host name as prompted.
------------------------------------------------------------------
Note: -- Enter key p/P to return pre-step
------------------------------------------------------------------
Please input the old hostname[default ossserver02]:
Please input the new hostname:ossserver03
****************SUMMARY********************
OPTYPE: HOSTNAME
*******************************************
OLDHOSTNAME: ossserver02
NEWHOSTNAME: ossserver03
NOTE
l Press Enter to use the default value in the system output.
l Type p/P to return to the function menu of the modify.sh script. Then, you are prompted to perform
operations such as changing the hostname.
l You can type q/Q to exit the modify.sh script.
l A host name is composed of digits, lower- and upper-case letters, and hyphen (-). The new host name
must comply with the following requirements:
l The host name contains a maximum of 24 characters.
l The host name must starts with a letter.
l The end character of the host name cannot be a hyphen (-).
l The host name cannot contain two consecutive hyphens (-).
Step 6 When the following information is displayed, type Y and press Enter.
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]:
NOTE
l You can type Q to exit the script without performing any operations.
l You can type R to return to the previous step to reconfigure relevant parameters.
l You can type P to return to the function menu of the modify.sh script. Then, you are prompted to
perform operations such as changing the hostname.
Step 7 When the following information is displayed, the change is successful.
------------------------------------------------------------------
Operation complete!
If the system output contains failed, the change fails. Contact Huawei technical support.
# sync; sync; sync; sync; sync; sync
M2000
13
# shutdown -r now
----End
3.3 Changing the IP Address of the IMM
This section describes how to change the IP address of the integrated management module
(IMM) on the M2000.
Prerequisites
l You have obtained the IP address plan and have confirmed that the IP address of the IMM
must be changed. For details, see Planning Device Host Name and IP Address.
l The network interface on the PC has been connected to the IMM network interface on the
server using network cable.
l The communication between the PC and the IMM is normal.
l The Dynamic Host Configuration Protocol (DHCP) service has been disabled on the PC.
Procedure
Step 1 Set Internet Explorer on the PC by referring to 13.2 How Do I Set Internet Explorer on the
PC?.
Step 2 Set the IP address of the PC to be on the same network segment (192.168.70.xx for example) as
the IP address of the system management network interface on the M2000 server.
For example, set the network adapter of the PC as follows:
l Set IP address to 192.168.70.35.
l Set Subnet mask to 255.255.255.0.
l Leave Default gateway, Preferred DNS server, and Alternate DNS server empty.
Step 3 Type http://192.168.70.125 in the address bar of the Internet Explorer. Then, press Enter to
access the IMM login window. If the web browser displays certificate error or untrusted website,
install certificates for the web browser by referring to 13.3 How Do I Handle the Problem of
Certificate Error or Untrusted Website Displayed in the Web Browser (IMM)?.
Step 4 Type the initial user name USERID and the actual password. Click Login to access the window
for setting the idle disconnection duration.
Step 5 Click Continue to access the IMM home page.
Step 6 In the navigation tree, choose System > IMM Control > Network Interface.
Step 7 The current IP addresses are displayed in the right pane. Enter the new IP address, subnet mask,
and gateway in IPV4, as shown in Figure 3-1.
M2000
14
Figure 3-1 Changing the IP address of the IMM

Step 8 Click Save.
Step 9 In the navigation tree, choose System > IMM Control > Restart IMM to enter the window for
restarting the IMM.
Step 10 Click Restart to restart the IMM to make the new IP address take effect.
NOTE
Restarting the IMM takes about 2 to 5 minutes. After the IMM restarts, open the web browser again if you
need to log in to the IMM.
----End
M2000
15
4 Configuring the NTP Service
About This Chapter
This section describes how to set the M2000 server as an NTP client or an intermediate-layer
NTP server.
Context
CAUTION
If you do not need to configure the NTP service on the M2000 server at the site, skip this section.
4.1 Methods for Configuring the NTP Service on the M2000 Server
This section describes the methods for configuring the Network Time Protocol (NTP) service
on the M2000 server.
4.2 Setting the M2000 Server as the NTP Client
This section describes how to set the M2000 server as an NTP client to synchronize time with
an NTP server.
4.3 Setting the M2000 Server as an Intermediate-Layer NTP Server
This section describes how to set the M2000 server as an intermediate-layer NTP server. An
intermediate-layer NTP server synchronizes time with the upper-layer NTP server, and provides
time reference for NTP clients.
4.4 Checking the Running Status of the NTP Service on the M2000 Server (SUSE)
This section describes how to check the running status of the NTP service on the M2000 server.
4.5 Configuring the NTP Service of the M2000 Client
This section describes how to set the M2000 client as the NTP client and synchronize time with
the M2000 server by using the NTP tool delivered with the Windows operating system.
M2000
Administrator Guide (x3850&x3650, SUSE10) 4 Configuring the NTP Service
16
4.1 Methods for Configuring the NTP Service on the
M2000 Server
This section describes the methods for configuring the Network Time Protocol (NTP) service
on the M2000 server.
You can configure the M2000 server as an NTP client or an intermediate-layer NTP server.
Table 4-2 describes the advantages and disadvantages of each method.
Table 4-1 Methods for configuring the NTP service
Method Reference
Set the M2000 server as an NTP client. 4.2 Setting the M2000 Server as the NTP Client
Set the M2000 server as an intermediate-
layer NTP server.
4.3 Setting the M2000 Server as an
Intermediate-Layer NTP Server

CAUTION
l Policy 1 is recommended. That is, set the M2000 server and NEs as NTP clients.
l When the M2000 manages billing system NEs such as the iGWB and CG, you must set the
M2000 server and NEs as NTP clients. If you set the M2000 as an intermediate NTP server,
the M2000 server time has an offset, which may lead to severe faults on the network.
Table 4-2 Advantages and disadvantages of each method
Metho
d
Reliability Security System
Resource Usage
Cost
Set the
M2000
server as
an NTP
client.
Higher reliability
because an
independent
intermediate-
layer NTP server
is deployed.
Higher security of
the time
synchronization
network because
the M2000 server
serves as an NTP
client and
synchronizes time
of the
intermediate-
layer NTP server.
Less system
resources required
because the
M2000 server
synchronizes time
with the upper-
layer NTP server
but does not
provide time
reference for NTP
clients.
Expensive
because you have
to deploy an
independent
intermediate-
layer NTP server.
M2000
17
Metho
d
Reliability Security System
Resource Usage
Cost
Set the
M2000
server as
an
interme
diate-
layer
NTP
server.
l The M2000
server
performs
frequent
operations,
such as
maintenance,
upgrade, and
backup. When
the M2000
server is used
as an
intermediate
NTP server,
the system
reliability is
relatively low.
l When M2000
server is set as
an
intermediate
NTP server,
the M2000
server time has
an offset,
which may
lead to
inconsistency
between NE
time and the
highest layer
NTP server.
Lower security of
the time
synchronization
network because
time
synchronization
service is affected
when the M2000
server becomes
faulty.
More system
resources required
because the
M2000 server
synchronizes time
with the upper-
layer NTP server
and provides time
reference for NTP
clients.
Cost effective
because the
M2000 server also
serves as an
intermediate-
layer NTP server.

4.2 Setting the M2000 Server as the NTP Client
This section describes how to set the M2000 server as an NTP client to synchronize time with
an NTP server.
Prerequisites
l The time zone of the M2000 server is set correct.
l The IP address of the NTP server has been obtained.
l The network between the M2000 server and the NTP server is running properly.
M2000
18
Procedure
Step 1 Run the following command to check the time zone of the server:
$ grep TIMEZONE /etc/sysconfig/clock
If the server time zone is incorrect, correct it by referring to 5.3 Changing the Time Zone and
Time of the M2000 Server (DST, SUSE) or 5.2 Changing the Time Zone and Time of the
M2000 Server (Non-DST, SUSE).
Step 3 If the Oracle services are running, stop them.
1. Check the status of the Oracle services.
For details, see 9.2 Checking Oracle Services.
2. Stop Oracle services.
For details, see How Do I Stop the Oracle Services.
Step 4 Run the following command to synchronize the clock time with the upper-level server.
$ /usr/sbin/ntpdate IP address of the NTP server
NOTE
If the system displays the following information while executing the preceding commands, the NTP service
has started.
ntpdate[518]:the NTP socket is in use, exiting
In this situation, proceed to complete the follow-up steps.
Step 5 Run the following command to open the yast interface:
$ yast
Step 6 On the YaST Control Center interface, use and to select Network Services.
Step 7 On the YaST Control Center interface, use Tab, , and to select NTP Configuration, and
press Enter.
Step 8 Use Tab, , and to select During Boot on Automatically Start NTP Daemon. Press
Enter for confirmation. If During Boot is selected, skip this step.
NOTE
When the Warning dialog box is displayed, use the Tab key to select Continue and press Enter. This
warning does not affect the setting of NTP server.
Step 9 On the NTP Server Configuration interface, use Tab to enter the IP address of the NTP server
in Address. Use the Tab key to select Test to test the NTP configuration, as shown in Figure
4-1.
NOTE
Do not use the numeric keypad on the GUI of the operating system.
l If the following information is displayed, it indicates that the entered IP address is
unavailable. In such a case, you need to check whether the IP address of the NTP server is
M2000
19
correct and whether network communication is normal. After troubleshooting, perform this
step again.
Server is unreachable or does not respond properly.
l If the following information is displayed, it indicates that the entered IP address is available.
Server is reachable and responds properly.
Figure 4-1 Configuring the NTP client

Step 10 Use the Tab key to select Advanced Configuration, and press Enter.
Step 11 Use the Tab key to select Undisciplined Local Clock (LOCAL). Then use the Tab to select
Delete and press Enter.
Step 12 In the displayed prompt dialog box, use the Tab key to select Yes, and press Enter.
Step 13 Use Tab to select Finish for completing the configuration of the NTP server.
Step 14 Use Tab to select Quit to exit the system.
Step 15 Run the following command to check the status of the NTP service on the M2000 server:
$ /usr/sbin/ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*192.168.8.12 .LCL. 1 u 29 64 177 0.240 0.093 1.222

l The value of remote indicates the IP address and status of an NTP server.
In the preceding output, 192.168.8.12 indicates the IP address of the top-layer NTP server,
and * indicates that the top-layer NTP server is in normal state. After the preceding
information is displayed, wait 5 minutes and * is displayed.
l The value of st indicates the layer of an NTP server in the time synchronization network.
In the preceding output, the IP address 192.168.8.12 is on layer 1.
If the status is incorrect, the NTP service does not function properly. When this occurs, contact
Step 16 Run the following command to check the system date and time.
$ date -R
If the system date and time are incorrect, contact Huawei technical support engineers.
----End
M2000
20
4.3 Setting the M2000 Server as an Intermediate-Layer NTP
Server
This section describes how to set the M2000 server as an intermediate-layer NTP server. An
intermediate-layer NTP server synchronizes time with the upper-layer NTP server, and provides
time reference for NTP clients.
Prerequisites
l The top-layer NTP server has been configured, and the IP address of the top-layer NTP
server has been obtained.
l The network between the M2000 server and the NTP server is running properly.
l The time zone of the M2000 server is set correct.
Context
l The upper-layer time server of the M2000 server requires that the NTP be used. The server
running Windows uses the SNTP protocol. Therefore, it cannot be used as the upper-layer
time server for the M2000 server.
l When an M2000 server is configured as an intermediate NTP server, the M2000 server
synchronizes time from the upper-layer clock source before providing the NTP service for
NEs. If the M2000 server fails to synchronize time from the upper-layer time source, the
M2000 server provides the NTP service for NEs using the M2000 server time. The
M2000 server time has an offset. If the M2000 server cannot synchronize the time from
the upper-layer clock source for a long time, the offset may be large, which may cause
network faults.
l When the M2000 manages billing system NEs such as the iGWB and CG, you must set the
M2000 server and NEs as NTP clients. If you set the M2000 as an intermediate NTP server,
the M2000 server time has an offset, which may lead to severe faults on the network.
l When you set the M2000 server as the intermediate NTP server, the specifications are as
follows:
The number of NEs of concurrent NTP time synchronization is 500. Specifically, the
intermediate NTP server can provide time synchronization for 500 NEs concurrently.
When the number of NEs requiring time synchronization is greater than 500,
synchronize the NE time at an interval of 30s in batches.
The maximum number of NEs of which the time can be synchronized using the
intermediate NTP server is consistent with the M2000 management capability.
Procedure
If the server time zone is incorrect, correct it by referring to 5.3 Changing the Time Zone and
Time of the M2000 Server (DST, SUSE) or 5.2 Changing the Time Zone and Time of the
M2000 Server (Non-DST, SUSE).
M2000
21
Step 4 Run the following commands to back up the ntp.conf configuration file:
$ rcntp stop
If the following information is displayed, ignore it and continue to run the following commands:
Shutting down network time protocol daemon (NTPD) done
umount: /var/lib/ntp/proc: not mounted
$ cd /etc
$ cp -p ntp.conf bak.ntp.conf
Step 5 Run the following command to synchronize the clock time with the upper-level server.
$ /usr/sbin/ntpdate IP address of the NTP server
Step 6 Switch to the YaST Control Center window, and configure the M2000 server as an
intermediate-layer NTP server.
1. Run the following command to switch to the YaST Control Center window:
$ yast
2. In the YaST Control Center window, use or to choose Network Services.
3. In the YaST Control Center window, use Tab and or to choose NTP
Configuration, and press Enter.
4. Use Tab and or to choose During Boot under Automatically Start NTP
Daemon, and press Enter. If During Boot is selected, skip this step.
NOTE
If the Warning dialog box is displayed, press Tab and choose Continue. Then, press Enter. This
warning does not affect the settings of the intermediate-layer NTP server.
5. Use the Tab key to select Advanced Configuration, and press Enter.
6. Use the Tab key to select Undisciplined Local Clock (LOCAL). Then use the Tab to
select Delete and press Enter.
7. In the displayed prompt dialog box, use the Tab key to select Yes, and press Enter.
8. Use the Tab key to select Add, and press Enter.
9. Use the Tab key to select Server, and press Enter. If Server is selected, skip this step.
10. Use the Tab key to select Next, and press Enter.
11. Use the Tab key to select Address, and enter the IP address of the top-level NTP server in
Address.
M2000
22
NOTE
Do not use the numeric keypad on the GUI of the operating system.
12. Use the Tab key to select Test to check whether the entered IP address is available.
l If the following message is displayed, it indicates that the entered IP address is
unavailable. In such a case, you need to check whether the IP address of the NTP server
is correct and whether network communication is normal. After troubleshooting,
perform this step again.
Server is unreachable or does not respond properly.
l If the following message is displayed, it indicates that the entered IP address is available.
Server is reachable and responds properly.
13. Use the Tab key to select Use for Initial Synchronization, and press Enter.
14. Use the Tab key to enter prefer in Options.
NOTE
prefer indicates that the time of the NTP server is synchronized preferentially. If there are multiple
NTP servers, you can set only one of them to prefer.
15. Use the Tab key to select OK, and press Enter.
NOTE
If there are multiple NTP servers, repeat Step 6.8 through Step 6.15 to set the IP addresses of other
NTP servers.
16. Press Tab to choose Finish, and press Enter.
17. Press Tab to choose Quit, and press Enter.
$ /usr/sbin/ntpq -p
==============================================================================
*192.168.8.12 .LCL. 1 u 29 64 177 0.240 0.093 1.222

Step 8 Run the following command to check the time synchronization path from the M2000 server to
the top-layer NTP server:
# /usr/sbin/ntptrace
localhost: stratum 6, offset 0.000000, synch distance 0.950193
192.168.8.12: stratum 1, offset 0.000000, synch distance 0.010010, refid 'LCL
The localhost line and the next line indicate the path from the M2000 server (intermediate-layer
NTP server) to the top-layer NTP server. The system can track the entire NTP synchronization
path from the M2000 server (intermediate-layer NTP server) to the top-layer NTP server.
M2000
23
For example, localhost: stratum 6 in the preceding output indicates that the M2000 server is
on layer 6, and 192.168.8.12: stratum 1 indicates that 192.168.8.12 is on layer 1.
Step 9 Run the following command to check the system date and time.
$ date -R
If the system date and time are incorrect, contact Huawei technical support engineers.
----End
Follow-up Procedure
After the M2000 server is set as an intermediate NTP server, set the NEs as NTP clients. For
details about how set an NE as an NTP client, see the user guide of the corresponding NE type.
4.4 Checking the Running Status of the NTP Service on the
M2000 Server (SUSE)
This section describes how to check the running status of the NTP service on the M2000 server.
Prerequisites
You have logged in to the server as user root.
Procedure
$ /usr/sbin/ntpq -p
==============================================================================
*192.168.8.12 .LCL. 1 u 29 64 177 0.240 0.093 1.222

----End
4.5 Configuring the NTP Service of the M2000 Client
This section describes how to set the M2000 client as the NTP client and synchronize time with
the M2000 server by using the NTP tool delivered with the Windows operating system.
M2000
24
Prerequisites
l You have logged in to the Windows OS as a user of the user group Administrators, and
the system is running properly.
l The connection between the M2000 client and the server is normal.
l The clock source of the server is operational.
Context
CAUTION
l The configuration procedure is applicable to the Windows 7, Windows 2003, Windows 2008,
Windows XP Professional, and Windows Vista Business operating systems.
l If the NTP service does not need to be configured at a site, skip this section and proceed with
the following operations.
l If the NTP service needs to be configured at a site, but the upper-layer NTP server is not
available and the NTP service is not configured on M2000 server during the commissioning,
skip this section and proceed with the following operations without configuring the NTP
service on the client.
Procedure
Step 1 Set the M2000 client as the NTP client.
1. Open the Registry Editor window.
l For Windows 2003 or Windows XP Professional, choose Start > Run. In the displayed
Run window, enter the regedit command and press Enter. The Registry Editor
window is displayed.
l For Windows 2008, Windows 7, or Windows Vista Business, click Start, then enter
the regedit command and press Enter in the search box. The Registry Editor window
is displayed.
2. Modify the registry.
In the registry, change the value of LocalNTP under HKEY_LOCAL_MACHINE >
SYSTEM > CurrentControlSet > Services > W32Time > Parameters to 0. By default,
the value is 0. If the LocalNTP parameter does not exist, you can infer that the value can
be ignored and the registry does not need to be modified.
NOTE
For the Windows 2003 and Windows 2008 operating systems, in the registry, change the value of
Enable under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services >
W32Time > TimeProviders > NtpServer to 0.
Step 2 Specify the M2000 server as the NTP server.
M2000
25
If... Then...
The M2000 client
runs on the
Windows 2003 or
Windows XP OS
1. Choose Start > Run. Type cmd and press Enter.
2. In the displayed window, run the following command:
c:\>net time /setsntp:M2000 server IP address
NOTE
l M2000 Server IP Address: indicates the logical IP address of M2000 in a
single-server system; the logical IP address of the active and standby
servers in an HA system.
l The result of the net time command is saved in the Windows registry.
Therefore, after the Windows OS is restarted, the parameters set through
the net time command still take effect.
l To cancel the setting, run the net time /setsntp command.
The M2000 client
runs on the
Windows 2008 ,
Windows 7
Professional OS, or
Windows Vista
Business OS
1. Click Start, enter cmd in the search box, Right-click the found
cmd icon and choose Run as administrator from the shortcut menu.
c:\>net start w32time
c:\>w32tm /config /manualpeerlist:M2000 server IP address /
syncfromflags:manual /reliable:yes /update
NOTE
l M2000 Server IP Address: indicates the logical IP address of M2000 in a
single-server system; the logical IP address of the active and standby
servers in an HA system.
l The result of the w32tm command is saved in the Windows registry.
Therefore, after the Windows OS is restarted, the parameters set through
the w32tm command still take effect.
l To cancel the setting, run the following commands:
net stop w32time
w32tm /unregister
If the error code 0x80070005 is displayed after running the w32tm /
unregister command, contact Huawei technical support.
Step 3 Restart the Windows Time service.
1. Run the following command to open the Services window.
c:\>services.msc
2. Find the Windows Time service and restart it in the Services window.
Step 4 Check the specified NTP server.
M2000
26
If... Then...
The M2000 client
runs on the
Windows 2003 or
Windows XP OS
1. Choose Start > Run. Type cmd and press Enter.
c:\>net time /querysntp
NOTE
If the host name or IP address of the PC is specified as the host name or IP
address of the NTP server through /setsntp, the NTP server time is regarded
as the standard time of the PC.
The M2000 client
runs on the
Windows 2008 ,
Windows 7
Professional OS, or
Windows Vista
Business OS
1. Click Start, enter cmd in the search box, Right-click the found
cmd icon and choose Run as administrator from the shortcut menu.
c:\>w32tm /query /peers
NOTE
If the host name or IP address of the PC is specified as the host name or IP
address of the NTP server through /manualpeerlist, the NTP server time is
regarded as the standard time of the PC.
Step 5 Run the following command to manually synchronize time:
c:\>w32tm /resync
Step 6 Run the following command to check the running status of the SNTP service:
c:\>w32tm /stripchart /computer:M2000 server IP address /dataonly
NOTE
M2000 Server IP Address: indicates the logical IP address of M2000 in a single-server system; the logical
IP address of the active and standby servers in an HA system.
The system displays the local time of the client and the deviation between the local time and the
time on the NTP server.
Tracking 10.71.15.98 [10.71.15.98].
The current time is 2009-6-22 10:05:09 (local time).
10:05:09, +04.9881239s
10:05:11, +04.9814570s
10:05:13, +04.9740897s
10:05:15, +04.9589559s
10:05:17, +04.9449507s
...
The first line of the system output shows the local time of the client. The next line shows the
time deviation between the client and the NTP server. + indicates that the client time is later than
the server time. - indicates that the client time is earlier than the server time. You can exit the
active window by pressing Ctrl+C.
----End
M2000
27
5 Changing the Time Zone and Time on the
M2000 Server (SUSE)
About This Chapter
This section describes how to set the time zone and the time on the server.
5.1 Introduction to the DST
This section describes the daylight saving time (DST) and the DST impact on the M2000 system.
5.2 Changing the Time Zone and Time of the M2000 Server (Non-DST, SUSE)
This section describes how to change the time zone and the time of the M2000 server.
5.3 Changing the Time Zone and Time of the M2000 Server (DST, SUSE)
This section describes how to change the time zone and the time of the M2000 server when the
system uses daylight saving time (DST).
M2000
Administrator Guide (x3850&x3650, SUSE10)
5 Changing the Time Zone and Time on the M2000 Server
(SUSE)
28
5.1 Introduction to the DST
This section describes the daylight saving time (DST) and the DST impact on the M2000 system.
Introduction
DST means Daylight Saving Time. The DST is one hour earlier than the standard time. For
example, during the DST, 10:00 am in US east standard time is 11:00 am in US east DST.
Impact on the M2000 System
l When the DST starts, generally one hour is automatically added to the local time of the
operating system. This change does not affect the system clock of the M2000. The
M2000 log management and trace management use the local time. Therefore, one-hour
records are missing in logs or trace files.
l When the DST ends, generally one hour is automatically deducted from the local time of
the operating system. This change does not affect the system clock and time storage and
exchange are not affected. This change, however, affects the time display. During the
operation of the M2000, some modules in the M2000 generate some files whose names are
identified by time stamps. When the DST ends, files that are generated later overwrite the
earlier ones.
NOTE
l The local time is the time displayed on the computer. It varies according to the time zone.
l The system clock indicates the Greenwich Mean Time (GMT). The NTP synchronization uses the
GMT, which does not affect the local time. The DST does not affect the NTP service.
5.2 Changing the Time Zone and Time of the M2000 Server
(Non-DST, SUSE)
This section describes how to change the time zone and the time of the M2000 server.
Prerequisites
You have logged in to the M2000 server as user root in SSH mode.
Context
The SUSE operating system supports two time zone formats: Greenwich Mean Time (GMT)
and time zone code.
l The GMT format stipulates only time offset rather than DST rules. The GMT format is
recommended for countries or regions that do not use DST.
The time and time zone are changed with reference to GMT. The time zone of a region to
the east of the GMT region is represented by GMT+N, indicating that the time of the region
is N hours ahead of the GMT. The time zone of a region to the west of the GMT region is
represented by GMT-N, indicating that the time of the region is N hours behind the GMT.
For example, GMT+8 indicates that the time of the region is eight hours earlier than the
GMT, and GMT-8 indicates that the time of the region is eight hours later than the GMT.
The GMT time zone format in a Solaris operating system, however, is the reverse of the
M2000
(SUSE)
29
common GMT time zone format. Specifically, GMT+N indicates that the time of the region
is N hours behind the GMT, and GMT-N indicates that the time of the region is N hours
ahead of the GMT.
l The time zone code format stipulates both time offset and DST rules. The time zone code
format must be used in countries and regions that use DST. Otherwise, the operating system
does not support automatic DST transitions.
l If you need to modify both the time zone and the time, modify the time zone first.
Precautions
You can change the time zone on the M2000 server according to the actual requirements.
Changing the server time zone directly results in change of the time at the bottom layer of the
Linux operating system. Consequently, all the timers that depend on the operating system are
reset or stop functioning properly. You must stop the M2000 and Oracle services in advance to
avoid a service failure caused by the malfunctioning of timers. During the period, the
performance data and alarm data of the managed NEs cannot be handled in time. After the
M2000 and Oracle services are restored, the M2000 starts the automatic synchronization
function and collects and handles the missing performance data and alarm data from managed
NEs.
Procedure
Step 1 Check the server time zone.
If the time zone of the server is correct, perform Step 8.
If the server time zone is incorrect, perform the following steps to correct it.
Step 2 If the M2000 services are running, stop them. If the M2000 software has not been installed, skip
this step.
For details, see How Do I Check the Status of the M2000 Services?.
Step 4 Run the yast command to change the time zone of the M2000 server in YaST Control
Center.
Step 5 Press Tab and the arrow keys to select system in the left part of YaST Control Center and
select Date and Time in the right part, and press Enter.
M2000
(SUSE)
30
Step 6 Check whether the Region and Time Zone are correct according to the instructions in Time
Zone and Clock Settings. If the two parameters are not set correctly, press Tab and the arrow
keys to select the correct time zone. Press Tab to select Accept. Then, press Enter.
If the time zone of the server is incorrect, repeat Step 4 through Step 6 to change it.
Step 8 Check system date and time.
$ date
If system date and time are incorrect, perform the following steps:
Step 9 Set the system date and time.
$ date mmddHHMMYYYY.SS
NOTE
l mm indicates a month.
l dd indicates a day.
l HH indicates an hour.
l MM indicates a minute.
l YYYY indicates a year.
l SS indicates a second.
For example, to set system date and time to 2005-11-17 16:30:43, run the following command:
$ date 111716302005.43
Mon Nov 17 16:30:43 CST 2005
NOTE
In the date -u mmddHHMMYYYY.SS command, mmddHHMMYYYY.SS is the Greenwich Mean Time
(GMT) but not the local time.
Step 10 Run the following command to restart the server.
$ shutdown -r now
After the operating system restarts, the Oracle service will automatically restart. If the M2000
software has been installed, the M2000 services will also automatically restart after the operating
system restarts.
----End
5.3 Changing the Time Zone and Time of the M2000 Server
(DST, SUSE)
This section describes how to change the time zone and the time of the M2000 server when the
system uses daylight saving time (DST).
Prerequisites
You have logged in to the M2000 server as user root in SSH mode.
M2000
(SUSE)
31
Context
The SUSE operating system supports two time zone formats: Greenwich Mean Time (GMT)
and time zone code.
l The GMT format stipulates only time offset rather than DST rules. The GMT format is
recommended for countries or regions that do not use DST.
The time and time zone are changed with reference to GMT. The time zone of a region to
the east of the GMT region is represented by GMT+N, indicating that the time of the region
is N hours ahead of the GMT. The time zone of a region to the west of the GMT region is
represented by GMT-N, indicating that the time of the region is N hours behind the GMT.
For example, GMT+8 indicates that the time of the region is eight hours earlier than the
GMT, and GMT-8 indicates that the time of the region is eight hours later than the GMT.
The GMT time zone format in a Solaris operating system, however, is the reverse of the
common GMT time zone format. Specifically, GMT+N indicates that the time of the region
is N hours behind the GMT, and GMT-N indicates that the time of the region is N hours
ahead of the GMT.
l The time zone code format stipulates both time offset and DST rules. The time zone code
format must be used in countries and regions that use DST. Otherwise, the operating system
does not support automatic DST transitions.
l If you need to modify both the time zone and the time, modify the time zone first.
Precautions
You can change the time zone on the M2000 server according to the actual requirements.
Changing the server time zone directly results in change of the time at the bottom layer of the
Linux operating system. Consequently, all the timers that depend on the operating system are
reset or stop functioning properly. You must stop the M2000 and Oracle services in advance to
avoid a service failure caused by the malfunctioning of timers. During the period, the
performance data and alarm data of the managed NEs cannot be handled in time. After the
M2000 and Oracle services are restored, the M2000 starts the automatic synchronization
function and collects and handles the missing performance data and alarm data from managed
NEs.
Procedure
Step 1 Query the local time zone name.
For details, see How Do I Query a Time Zone Name (SUSE).
Step 2 Run the following command to view the DST rules of the time zone in a specified year:
$ zdump -v time zone name | grep specified year
l If DST is not used, the system displays no information. If DST is used, the system displays
the following information for describing the DST rules:
l The information is in the following format:
Time zone name UTC time = Local time/DST isdst=0/1
l The UTC time is the GMT.
l isdst=0 non-DST period. isdst=1 indicates DST period.
M2000
(SUSE)
32
NOTE
l If you do not add | grep specified year to the previous command, the system displays the DST rules
of the time zone in all years.
l The DST rules of a time zone stipulate the day, week, and month when DST starts and ends in each
year. This indicates that the week when DST starts is fixed and that the date when DST starts is flexible.
For example, the DST of Alaska, United States time zone starts from the second Sunday of March and
ends on the first Sunday of November in each year.
l You can run the zdump command to query the DST rules in the three successive years, that is, the last
year, this year, and the next year. Based on the system output, you can infer the universal DST change
rules.
If the time zone of the server is correct, perform Step 8.
If the time zone of the server is incorrect, perform the following steps to change it:
Step 4 If the M2000 services are running, stop them. If the M2000 software has not been installed, skip
this step.
For details, see How Do I Check the Status of the M2000 Services?.
Step 6 Perform the following operations to configure the DST:
1. Run the yast command to change the time zone of the M2000 server in YaST Control
Center.
2. Use the Tab key and arrow keys to select system in the left pane of YaST Control
Center and select Date and Time in the right pane. Then, press Enter.
3. According to the description in Time Zone and Clock Settings, check whether the values
of Region and Time Zone are consistent with the actual situation. If the values are
inconsistent with the actual situation, use the Tab key and arrow keys to correct the time
zone. Then use the Tab key to select Accept and press Enter.
4. In the displayed window, use the Tab key to select Quit to exit the YaST.
If the time zone of the server is incorrect, repeat Step 6 to change it.
Step 8 Check system date and time.
$ date
M2000
(SUSE)
33
If system date and time are incorrect, perform the following steps:
Step 9 Set the system date and time.
$ date mmddHHMMYYYY.SS
NOTE
l mm indicates a month.
l dd indicates a day.
l HH indicates an hour.
l MM indicates a minute.
l YYYY indicates a year.
l SS indicates a second.
For example, to set system date and time to 2005-11-17 16:30:43, run the following command:
$ date 111716302005.43
Mon Nov 17 16:30:43 CST 2005
NOTE
In the date -u mmddHHMMYYYY.SS command, mmddHHMMYYYY.SS is the Greenwich Mean Time
(GMT) but not the local time.
$ shutdown -r now
After the operating system restarts, the Oracle service will automatically restart. If the M2000
software has been installed, the M2000 services will also automatically restart after the operating
system restarts.
----End
Example
l Run the following command to view the DST rules of the PRC time zone in 2007:
$ zdump -v PRC|grep 2007
If no command output is displayed, the PRC time zone in 2007 does not use DST.
l Run the following command to view the rule of the US/Alaska time zone in 2007:
$ zdump -v US/Alaska|grep 2007
The system displays information similar to the following:
US/Alaska Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST
isdst=0
US/Alaska Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT
isdst=1
US/Alaska Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT
isdst=1
US/Alaska Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 AKST
isdst=0
The information in the first row and the second row indicates that DST starts after Mar
11 02:00:00 2007 changes to Mar 11 03:00:00 2007.
The information in the third row and the fourth row indicates that DST ends after Nov
4 02:00:00 2007 changes to Nov 4 01:00:00.
M2000
(SUSE)
34
6 Managing M2000 Users
About This Chapter
This section describes how to manage OS users and database users of the M2000 system.
6.1 User Type
This section describes information about OS users and DB users involved in the operation of
the M2000. OS users include user root, ossuser, ftpuser, and oracle. DB users include user
system and sys.
6.2 Changing the Password of User root (SUSE)
This describes how to change the password of user root.
6.3 Changing the Password of User ossuser (SUSE)
This section describes how to change the password of user ossuser when you log in to the system
as user root. In the M2000 HA system, the password of user ossuser on the two nodes must be
consistent. Therefore, you must change the password of user ossuser on the active and standby
nodes separately to ensure the password consistency.
6.4 Changing the Password of User ftpuser
This section describes how to change the password of user ftpuser.
6.5 Changing the Password of User oracle
This section describes how to change the password of user oracle when you log in to the
M2000 database as user root. For the M2000 HA system, the password of user oracle on the
two nodes must be consistent. Therefore, you must change the password of user oracle on the
active and standby nodes separately to ensure the password consistency.
6.6 Changing the Password of User in the Oracle Database
This section describes how to change the passwords of user in the Oracle database.
6.7 Changing the Password of the IMM User
This section describes how to change the password of the IMM user USERID on the M2000.
M2000
Administrator Guide (x3850&x3650, SUSE10) 6 Managing M2000 Users
35
6.1 User Type
This section describes information about OS users and DB users involved in the operation of
the M2000. OS users include user root, ossuser, ftpuser, and oracle. DB users include user
system and sys.
Table 6-1 and Table 6-2 describe OS users and DB users for the M2000.
Table 6-1 OS users
User
Name
Default Password Usage Authority Use
r
Gro
up
She
ll
Res
olut
ion
Pro
gra
m
Dir
ecto
ry
root Changeme_123 User
root is
the
default
user of
the
system
. User
root is
authori
zed to
control
all
resourc
es,
create
other
user
accoun
ts,
assign
authori
ty to
other
users,
and
perfor
m all
system
operati
ons.
User root
has the
highest
authority of
the system.
User root is
authorized
to install
and
uninstall
M2000
server
application
s.
othe
r,
bin,
sys,
adm
,
uuc
p,
mail
, tty,
lp,
nuu
cp,
dae
mon
, and
user
.root
/bin/
bash
/
root
M2000
36
User
Name
r
Gro
up
She
ll
Res
olut
ion
Pro
gra
m
Dir
ecto
ry
ossuser Changeme_123 User
ossuse
r is
respon
sible
for the
operati
on and
mainte
nance
of the
M2000
.
User
ossuser is
authorized
to access
the
database
and
perform
operation
and
maintenanc
e.
User
ossuser is
not allowed
to install or
uninstall
M2000
server
application
s.
root,
sys,
ossg
roup
,
dba,
and
oins
tall
/bin/
bash
/
exp
ort/
hom
e/
ossu
ser
oracle Changeme_123 User
oracle
is used
to
install
the
Oracle
databa
se.
User
oracle
is
created
before
the
databa
se is
installe
d.
User oracle
is
authorized
to access
the
database
and
perform
operations
over the
Oracle
database.
oins
tall,
dba,
and
ossg
roup
/bin/
bash
/opt/
orac
le
M2000
37
User
Name
r
Gro
up
She
ll
Res
olut
ion
Pro
gra
m
Dir
ecto
ry
ftpuser Changeme_123 ftpuse
r is a
user to
upload
files to
the
server
and
downl
oad
files
from
the
server.
User
ftpuser is
authorized
to perform
software
manageme
nt and file
transfer for
NEs.
ossg
roup
,
dial
out,
vide
o
/bin/
bash
/
exp
ort/
hom
e/
sys
m

Table 6-2 DB users
User Name Default
Passwor
d
Usage Authority
system Changeme
_123
User system is the
administrator of the
Oracle database. User
system is responsible for
the management, upgrade,
and maintenance of the
Oracle database, and is
used to install the M2000
server applications.
User system has the
highest authority of the
database.
sys Changeme
_123
User sys is the
administrator of the
Oracle database. User sys
is responsible for the
management and
operation of the Oracle
system, and is used to
restore the Oracle
database applications.

M2000
38
6.2 Changing the Password of User root (SUSE)
This describes how to change the password of user root.
Prerequisites
l The old password of user root is available.
l The new password of user root is available.
Context
The password contains 8 to 127 characters, including digits from 0 to 9, uppercase and lowercase
letters, and special characters. To improve password security, you must set the password by
observing the following rules:
l The password contains at least one uppercase letter.
l The password contains at least one lowercase letter.
l The password contains at least one digit.
l The password contains at least one special character: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
and spaces
l The last 12 history passwords cannot be used.
NOTE
l 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.
l The number of times adjacent codes are used should not be greater than 4 for the ASCII codes
corresponding to the characters in a password. You are advised not to use adjacent letters and digits in
a password.
Procedure
Step 1 Log in as user root, and enter the old password of user root.
Step 2 Run the following command to change the password:
# passwd root
Changing password for root.
New password:new password
Reenter New Password:new password
Password changed.
----End
6.3 Changing the Password of User ossuser (SUSE)
This section describes how to change the password of user ossuser when you log in to the system
as user root. In the M2000 HA system, the password of user ossuser on the two nodes must be
consistent. Therefore, you must change the password of user ossuser on the active and standby
nodes separately to ensure the password consistency.
M2000
39
Prerequisites
l The new password for ossuser is available.
l You have logged in to the server as user root.
Context
and spaces
NOTE
a password.
Procedure
Step 1 Run the following command to change the password:
# passwd ossuser
Changing password for ossuser.
Reenter New Password:new password
Password changed.
----End
6.4 Changing the Password of User ftpuser
This section describes how to change the password of user ftpuser.
Prerequisites
l The new password of user ftpuser is available.
l You have logged in to the server as user root by using the SSH.
Context
The password can contain 8 to 30 characters, including digits 0 to 9, lowercase letters a to z,
uppercase letters A to Z, and special characters @%-=_.]{}. To improve password security,
you are advised to use the following password policies:
M2000
40
l The password contains at least one special character.
l The password does not contain the user name.
NOTE
The password must also meet the requirements of the operating system. For details about the password
Procedure
Services (SUSE). Stop the M2000 services if they are running. For details on how to stop the
M2000, see 8.4 Stopping the M2000 Services (SUSE).
Step 2 Check whether the Oracle service is running. For details, see 9.2 Checking Oracle Services. If
the Oracle service is already stopped, start the Oracle. For details about how to start the Oracle,
see 9.3 Starting Oracle Service.
Step 3 Run the following commands to change the password of user ftpuser.
$ ./modify.sh
The following message is displayed:
------------------------------------------------------------------
Modify Tool (2.0.0)
------------------------------------------------------------------
------------------------------------------------------------------
1--IP
R--Return
Q--Quit
------------------------------------------------------------------
Step 4 Type 3, and then type the new password of user ftpuser at the following prompt. Type the new
password again, and then press Enter.
------------------------------------------------------------------
------------------------------------------------------------------
Please input the new ftp user's password:
Please Re-enter the password:
Step 5 At the following prompt, enter Y for confirmation.
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]:Y
------------------------------------------------------------------
M2000
41
When the system displays the following information, you can infer that the change is successful.
------------------------------------------------------------------
Operation complete!
Step 6 For details on how to restart the M2000 service, refer to 8.3 Starting the M2000 Services
(SUSE).
----End
6.5 Changing the Password of User oracle
This section describes how to change the password of user oracle when you log in to the
M2000 database as user root. For the M2000 HA system, the password of user oracle on the
two nodes must be consistent. Therefore, you must change the password of user oracle on the
active and standby nodes separately to ensure the password consistency.
Prerequisites
l The new password of the operating system user oracle is available.
Context
and spaces
NOTE
a password.
Procedure
Step 1 Run the following command to change the password of user oracle:
# passwd oracle
Changing password for oracle.
Reenter New Password: new password
M2000
42
Password changed.
----End
6.6 Changing the Password of User in the Oracle Database
This section describes how to change the passwords of user in the Oracle database.
Prerequisites
l The new password of user in the Oracle database is available.
l You have logged in to the server as user root by using the SSH.
Context
The passwords of the system user, sys user and product data users are the same. After the
password of the system is changed, the passwords of the sys user and product data users will be
changed accordingly.
To improve password security, you are advised to use the following password policies:
l The password contains 8 to 30 characters.
l The password must contain a combination consisting of the following:
The password contains at least one uppercase letter.
The password contains at least one lowercase letter.
The password contains at least one digit.
The password contains at least one of the following special characters: ~ ! # $ % ^ & *
( ) - _ + | [ { } ] ; : , < . > ?
The password can't contain the following special characters: ` @ = ' " \ / and the space
l The password must be different from the user name or the user name in reverse order.
Procedure
Services (SUSE). If any M2000 service is running, stop it by referring to 8.4 Stopping the
M2000 Services (SUSE).
Step 2 Check whether the Oracle is started by referring to 9.2 Checking Oracle Services. If any Oracle
service stops, start it by referring to 9.3 Starting Oracle Service.
Step 3 Perform the following operations to change the password of user system:
1. Run the modify script.
$ ./modify.sh
Choose 2--Database password after the following message is displayed:
------------------------------------------------------------------
Modify Tool (2.0.0)
M2000
43
------------------------------------------------------------------
------------------------------------------------------------------
1--IP
R--Return
Q--Quit
------------------------------------------------------------------
2. Based on the displayed messages, enter the old and new passwords of user system. Press
Enter.
------------------------------------------------------------------
------------------------------------------------------------------
Please input the old database superuser's password:
Please input the new database superuser's password:
Please Re-enter the password:
NOTE
l Enter p or P. The system displays the function menu of the modify script, prompting you to
perform operations such as changing the IP address or user password.
l Enter q or Q to exit the modify script.
l You need to enter the new password of user system twice.
3. Type Y and press Enter after the following messages are displayed:
Y--Yes.
Q--Quit.
R--Re-input
P--Return pre-step
Please make a choice[Y/Q/R/P]: Y
NOTE
l Enter Q to exit the script without performing any operations.
l Enter R to return to the previous step to reconfigure relevant parameters.
l Enter P. The system displays the function menu of the modify script, prompting you to perform
operations such as changing the IP address or user password.
l Modifying the password of user system by running the modify script takes about 1 to 2 minutes.
4. The password is successfully changed if the following message is displayed:
------------------------------------------------------------------
Operation complete!
Step 4 Start the M2000 service, see 8.3 Starting the M2000 Services (SUSE).
----End
6.7 Changing the Password of the IMM User
This section describes how to change the password of the IMM user USERID on the M2000.
Prerequisites
l The PC network interface is connected to the network interface for IMM management using
network cable.
l The network used by the PC to communicate with the IMM functions properly.
M2000
44
l The Dynamic Host Configuration Protocol (DHCP) service is disabled on the PC.
Procedure
Step 1 Set Internet Explorer on the PC by referring to 13.2 How Do I Set Internet Explorer on the
PC?.
Step 2 Set the IP address of the PC to be on the same network segment (192.168.70.xx for example) as
the IP address of the system management network interface on the M2000 server.
For example, set the network adapter of the PC as follows:
l Set IP address to 192.168.70.35.
l Set Subnet mask to 255.255.255.0.
l Leave Default gateway, Preferred DNS server, and Alternate DNS server empty.
Step 3 Type http://192.168.70.125 in the address bar of the Internet Explorer. Then, press Enter to
access the IMM login window. If the web browser displays certificate error or untrusted website,
install certificates for the web browser by referring to 13.3 How Do I Handle the Problem of
Certificate Error or Untrusted Website Displayed in the Web Browser (IMM)?.
Step 4 Type the initial user name USERID and password (Changeme_123 is the default password and
needs to be replaced with the actual password). Click Login to access the window for setting
the idle disconnection duration.
Step 5 Click Continue to access the IMM home page.
Step 6 In the navigation tree, choose System > IMM Control > Login Profiles.
IMM users are displayed in Login Profiles of the window on the right side.
Step 7 Click user USERID to open the window, as shown in Figure 6-1.
Figure 6-1 Window for changing the password of IMM user USERID
M2000
45

Step 8 Enter the planned password of existing network in the Password and Confirm password text
boxes.
NOTE
To enhance account security, you are advised to use the following password policies:
l The password contains eight to fifteen characters.
l The password contains at least one special character as following: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ |
[ { } ] ; : ' " , < . > / ?
l The password must be different from the user name or the user name in reverse order.
Step 9 Choose Supervisor in Authority Level.
Step 10 Click Save.
Step 11 Click OK in the displayed dialog box. The password of user USERID has been changed
successfully.
----End
M2000
46
7 Managing M2000 and NE Logs
About This Chapter
This section describes how to manage the operation logs, system logs, and security logs of the
M2000 and NEs. You can also manage the operating system logs. By querying or collecting
statistics on logs, engineers can trace user behaviors. This facilitates system diagnosis and
maintenance.
M2000
Administrator Guide (x3850&x3650, SUSE10) 7 Managing M2000 and NE Logs
47
7.1 Overview of Log Management
Before performing the operations related to log management, you need to be familiar with the
basic information, functions, and technical specifications of logs. The basic log knowledge helps
you understand the contents of log management.
7.1.1 Log Management Function
In log management, the system, security, and operation logs that are generated during M2000
running are recorded. You can query logs to understand the M2000 running status, system
security status, or specific user operation. In addition, you can save log results to a file or print
the log results for future browse.
M2000 log management includes the functions such as querying logs, managing log templates,
saving logs, and printing logs.
7.1.2 Log Types
This section describes operation logs, system logs, security logs, and operating system logs of
M2000 and NEs. Each types of logs record different log information.
The M2000 Operation Logs
M2000 operation logs record the user operations on the M2000 client, helping rectify faults.
Description
The operation log records the operations that are performed on the M2000 client but do not affect
the M2000 security, such as creating NEs, 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 System > 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/oss/
server/var/ThresholdExport/Log in Solaris and SUSE Linux.
After the operation logs are dumped, the M2000 generates the associated folder and log file:
l Folder: In the dump path, the M2000 generates a folder named the date of the dump
operation. The format of the name is YYMMDD.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
operation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-log-
dateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
number.extension saved the information about the dumped logs.
M2000
48
NOTE
l Operation logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be
compressed to a .zip package.
l To avoid insufficient space in the database, you can enable log dump to dump the M2000
operation logs periodically or immediately. The logs that are dumped will be deleted from the
database.
Parameters
Parameter Name Parameter Meaning
Operation Name Name of an operation that the user performs on the M2000.
Risk Level Levels of risks caused by the operations that are performed on the
M2000: Warning, Minor, and Risk.
Operation User OM user.
User Type Type of the user who performs an operation.
Operation Time Time when an operation is performed. It is accurate to second.
Operation Category Type of an operation.
Operation Terminal IP address of the host where an operation is performed.
Operation Object Object that an operation is performed on.
Operation Result Result of an operation: successful, failed, partially successful.
Details Other useful information about an operation.
The M2000 System Logs
M2000 system logs record the operating information about the M2000, helping detect faults and
ensuring that the M2000 runs properly.
Description
The system log records the tasks that are performed on the M2000 server and affect the running
of the M2000. These tasks are triggered on the M2000 client, such as starting and executing
scheduled tasks, or triggered on the M2000 server, such as starting and stopping the M2000
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 System > Log Management > Query System
Logs.
M2000
49
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/oss/server/var/
ThresholdExport/Log in Solaris and SUSE Linux.
After the system logs are dumped, the M2000 generates the associated folder and log file:
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-system-
log-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThreshold-
number.extension. The file with the suffix _info.xml saves the configuration information
of the dumped logs, and the file with the suffix -number.extension saves the information
about the dumped logs.
NOTE
l System logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be compressed
to a .zip package.
l To avoid insufficient space of the database, you can set the M2000 system log dump to dump
the M2000 system logs periodically or immediately. The dump logs are saved as files and deleted
from the database.
Parameters
Level Levels of risks caused by the operations performed on the M2000:
Warning, Minor, and Risk.
Source Module where the M2000 performs an operation.
Time Time when an operation is performed. It is accurate to second.
Basic Information Basic operation information.
Operation Result Result of an operation: successful, failed or unknown.
The M2000 Security Logs
M2000 security logs record the security-affected operations on the M2000 client, ensuring that
the M2000 runs properly.
Description
Security logs record the security operations that the user performs in the M2000, for example,
login, logout, and unlocking.
M2000
50
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 System > 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
Capacity Management > Security Log Dump. The default dump paths are /opt/oss/server/
var/ThresholdExport/Log in Solaris and SUSE Linux.
After the security logs are dumped, the M2000 generates the associated folder and log file:
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
security-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-log-
dateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
number.extension saves the information about the dumped logs.
NOTE
l System logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be compressed
to a .zip package.
l To avoid insufficient space of the database, you can set the M2000 security log dump to dump
the M2000 security logs periodically or immediately. The dump logs are saved as files and deleted
from the database.
Parameters
Security Event Event that is related to M2000 security.
Risk Level Levels of risks caused by the operations that are performed on the
M2000: Warning, Minor, and Risk.
Operation User OM user.
User Type Type of an M2000 user.
Operation Time Time when an operation is performed. It is accurate to second.
Operation Terminal IP address of the host where an operation is performed.
Operation Object Object that an operation is performed on.
Operation Result Result of an operation: successful, failed or partially successful.
M2000
51
NE Operation Logs
By browsing NE operation logs, you can know the operations performed by a user at a certain
time. The operation information is used for future reference.
Description
NE operation logs record important operations performed by NE users, which provides operation
information for future reference.
Path
NE operation logs are generated and saved on the NEs. After being synchronized to the
M2000, the logs are saved in the database. For details about how to synchronize operation logs,
see 7.2 Synchronizing NE Logs. You can choose System > Log Management > Query NE
Operation Logs on the client to query the operation logs.
Parameters
User Name of the user for performing the
operation.
User Type Domain attributes of the user corresponding
to an NE operation log. The attributes contain
EMS, Local, and EMSOP.
Terminal An operation terminal identified by an IP
address.
Start Time Start time of the operation. The format is
consistent with Setting the Time Format of
the Client and Setting the Date Format of the
Client in the region settings, for example,
YYYY-MM-DD HH:MM:SS.
End Time End time of the operation. The format is
consistent with Setting the Time Format of
the Client and Setting the Date Format of the
Client in the region settings, for example,
YYYY-MM-DD HH:MM:SS.
Result Whether the operation is successful or fails.
MML MML commands for performing operations
on an NE.
M2000
52
Rollback MML Rollback MML displays the MML
commands before Operation, which helps
users to compare the operations before and
after data modification.
For example, in an NE operation log, if the
Operation column displays MOD GCELL:
IDTYPE=BYID, CELLID=0,
NEWCELLNAME="gcell2", the
Rollback MML column displays MOD
GCELL: IDTYPE=BYID, CELLID=0,
NEWCELLNAME="gcell3", you can infer
that MOD GCELL: IDTYPE=BYID,
CELLID=0, NEWCELLNAME="gcell2"
is performed after MOD GCELL:
IDTYPE=BYID, CELLID=0,
NEWCELLNAME="gcell3".
If the value of Rollback MML is null, you
can infer that the Rollback MML function is
not supported currently. Currently, the NEs
that support the Rollback MML function are
the BSC6900 GSM, BSC6910 GSM,
BSC6910 GU and the BSC6900 GU. The
following prerequisites must be met:
l The current operations refer to the setting
and modification operations that support
the rollback. That is, the MOD and SET
commands.
l The configuration authority switch on the
NE is set to ON. The quick configuration
mode is disabled.
NOTE
By default, the configuration authority switch
and the quick configuration mode on the NE
are disabled. You can run the SET
CMCTRLSW: CTRLSW=ON; command to
enable the configuration authority switch
through the M2000 or the LMT. You can run
the SET QUICKCFG: MODE=OFF;
command to disable the quick configuration
mode.
Information Details of the operation.
NE Type Type of the NE corresponding to the
operation.
NE Name Name of the NE corresponding to the
operation.

M2000
53
NE Security Logs
By browsing NE security logs periodically, you can find security vulnerabilities of the NEs and
take proper measures to ensure the security of the NEs.
Description
NE security logs record events related to NE security, such as logging in to the LMT, modifying
the NE user rights, and adding NE users, which helps monitor the operating status of NEs.
Path
NE security logs are generated and saved on the NEs. After being synchronized to the M2000,
the logs are saved in the database. For details about how to synchronize the security logs, see
7.2 Synchronizing NE Logs. You can choose System > Log Management > Query NE
Security Logs on the client to query the security logs.
Parameters
User Name of the NE user that carries out a specific
operation
User Type Domain attribute of the user, such as EMS,
Local, and EMSOP.
Terminal IP address of the terminal on which the
operation is performed
Security Level Class of a security event to be queried, such
as urgent, important, and subordinate.
Creation Time Time when the security event occurs
Result Whether the operation is successful or fails
Security Event Details of the security event
Message Details of the operation
NE Type Type of the NE
NE Name Name of the NE

SUSE Linux Operating System Logs
This section describes the information about the logs of the SUSE Linux operating system (SUSE
logs for short), including log content, log path, and log format. By viewing SUSE logs,
maintenance personnel can learn about the running status of the SUSE Linux operating system
in time. Querying SUSE logs requires few system resources and does not affect system
performance.
M2000
54
Log Content
SUSE logs records boot messages during the startup of the SUSE Linux operating system, and
other status messages during system running.
Log Path
SUSE logs are recorded in the messages file in /var/log.
Log Format
SUSE logs are recorded in the following format:
Date and time of events Host name Event description
Log Check
Generally, the messages file does not contain error information such as error, Error, failed and
Failed. If the file has any error information, contact technical support personnel for assistance.
MML Logs
MML log management helps query MML command issue, which facilitates fault identification
and improves maintenance efficiency.
Description
The M2000 logs the MML commands issued to NEs and results returned by the NEs, and save
the MML commands and results to the database.
Path
After being issued to NEs, MML commands are saved in the M2000 database. You can choose
System > Log Management > MML Log Management on the client to query the MML logs.
Parameters
Operated NE Refers to the NE involved in the execution of
an MML command.
Module Refers to the module that generates MML
logs.
User Refers to the user who runs MML commands.
Terminal Refers to an operation terminal running MML
commands. The terminal is identified with an
IP address.
Start Time Refers to the time when the execution of
MML commands begins.
M2000
55
End Time Refers to the time when the execution of
MML commands ends.
MML Command Refers to the MML command to be executed.
Result Refers to the command result. The command
result can be either of the following types:
l Success: indicates that the MML
command is successfully executed.
l Failure: indicates that the MML command
cannot be executed.

System Tool Logs
This section describes the contents, paths, and formats of the system tool logs. With the system
tool logs, security administrators can audit users' operations on a scheduled basis. This helps to
identify unauthorized user operations.
Log Content
The system tool logs consist of the M2000 application system log, OSS Self-Maintenance Unit
system log (OSMU), operating system (OS) background tool log, and FTP log.
Log Path
l The M2000 application system log and OS background tool log are saved in the
localmessages file in the /var/log path.
l The FTP log is saved in the vsftpd.log file in the /var/log path.
l The OSMU system log is saved in the Operation.log file in the /export/home/
omc_control path.
localmessages Log Format
The localmessages log format is as follows:
Date and time Host name User name: Command name;Result;Details
vsftpd.log Log Format
The vsftpd.log log format is as follows:
Date and time [Thread ID] [Login user] Operation object: Login IP, Operation result
Operation.log Log Format
The Operation.log log format is as follows:
Date and time [Login user, Login IP] Details
M2000
56
Log Dump
The system automatically dumps a log file that exceeds 20 MB, and a maximum of 10 log files
can be dumped at a time.
l The log dump path is the same as its save path.
l A dumped log file is named in the following format: source log file name-
YYYYMMDD.number.
For example, localmessages-20120423.0.
The M2000 NE Syslog Run Log
NE syslog run logs record running information of NEs. The M2000 obtains NE syslog run logs
from all managed NEs. You can browse the NE syslog run logs on the M2000 without querying
them on each NE.
Description
NE syslog run logs record running information of NEs managed by the M2000.
Path
NE syslog run logs are stored on NEs. You can choose System > Log Management > NE Syslog
Run Log on the M2000 client to query NE syslog run logs encapsulated by using the syslog
protocol.
The local path to NE syslog run logs is /opt/oss/server/var/devlogs (on Solaris and SUSE
Linux). An NE syslog run log file is named in YYYYMMDDHHMMSS.File name extension
format, where the value of File name extension is txt or zip. By default, an NE syslog run log
file stores a maximum of 20,000 logs.
Parameters
Parameter Description
NE Name Name of an NE managed by the M2000.
IP Address IP address of an NE managed by the M2000.
Digest Digest of an NE syslog run log.
Details Details of an NE syslog run log.
Module Name Module corresponding to an NE syslog run
log.
Level NE syslog run log level. Log levels include
the Emergency, Alert, Critical, Error,
Warning, Notice, Informational, and
Debug levels.
Sending Time Time when an NE syslog run log is reported.

M2000
57
7.1.3 Log Templates
To facilitate log query and log statistics, the M2000 system provides the template management
function. That means that you can save commonly used querying or statistical items to a template
for future use.
Log templates are categorized into querying templates and statistical templates.
l You can save all the querying or statistical settings of a specific type of logs into a template.
You can click Template Filter and choose Open to query the predefined query or statistics
template in the template list.
l The contents of the templates are saved in the database of the server, and they are available
only to their creators.
l Each type of log template created by a user must have a unique name.
l The name of a template contains a maximum of 40 characters, and special characters, such
as ` ~ ! @ # $ % ^ & * ( ) " : ; ? , | { } [ ] < > , are not allowed.
l The system does not support automatic template refreshing. This means that if a user logs
in to client A and modifies/deletes template A, template A remains unaltered when the user
logs in to client B. You can close the template first, then open it again, and the system
refreshes the information of the template.
7.1.4 Procedure for Reporting NE Logs
NE logs must be centrally reported to the M2000 client for synchronization. NE logs can be
reported using a transfer server or without a transfer server.
NE logs record important events occurred on each NE. After filtering criteria are set, the required
log information is recorded and reported to the relevant software management server. Then, NE
logs are centrally reported to the M2000 client for synchronizing NE logs.
When an NE of a certain type supports the FTP server, you can set the NE to a transfer server
for file transfer. In this case, the NE functions as the FTP server and the M2000 server functions
as the FTP client.
For security purposes, a firewall is generally deployed between the M2000 and NEs. Only the
basic maintenance channel is retained on the firewall. The port of the maintenance channel is
defined by the company and is unlikely to be attacked. For the port used by the FTP service,
however, the possibility of being attacked is higher. In this case, you can set a transfer server
and open only the FTP port of the transfer server on the firewall to reduce the possibility of being
attacked.
Based on whether a transfer server is used for reporting NE logs, the procedures for reporting
NE logs are classified as follows:
l Figure 7-1 shows the procedure for reporting NE logs using a transfer server.
M2000
58
Figure 7-1 Procedure for reporting NE logs using a transfer server
SMServer obtains the information
about synchronizing time
SMServer sends the generated log file
command to the NE
SMServer obtains the FTP user name
and password
SMServer creates a save path for log
files
SMServer sends the uploading
commands of log files to the NE
SMServer reports the whole progress
to the GUI
The NE reports progress of the
generated log file to the SMServer
The NE uploads the log files to the
FTP server
The NE reports the uploading
progresss of the log files to SMServer
to the GUI
SMServer downloads the log files from
the FTP server
SMServer resolves the log files to
records
SMServer saves the records to the
database
to the GUI
End

M2000
59
The procedure shown in Figure 7-1 is described as follows:
1. The software management server obtains synchronization time information, writes
the information into the database, and issues commands for generating log files to
NEs.
2. NEs generate log files.
3. The software management server issues commands for uploading log files to NEs.
After receiving the commands, NEs upload log files to the transfer server.
4. Save original log files.
5. Check whether the NEs mapped to the log files obtained from the transfer server have
been subscribed to.
6. The software management server parses the log files of the subscribed NEs and saves
the parsing result in the database.
l Figure 7-2 shows the procedure for reporting NE logs without a transfer server.
M2000
60
Figure 7-2 Procedure for reporting NE logs without a transfer server
SMServer obtains the information
about synchronizing time
SMServer sends the generated log file
command to the NE
SMServer sends the uploading
commands of log files to the NE
to the GUI
The NE reports progress of the
generated log file to the SMServer
The NE uploads the log files to
SMServer
The NE reports the uploading
progresss of the log files to SMServer
to the GUI
SMServer downloads the log files from
the FTP server
SMServer resolves the log files to
records
SMServer saves the records to the
database
to the GUI
End

The procedure shown in Figure 7-2 is described as follows:
1. The software management server obtains synchronization time information, writes
the information into the database, and issues commands for generating log files to
NEs.
2. NEs generate log files.
M2000
61
3. The software management server issues commands for uploading log files to NEs.
After receiving the commands, the NEs upload log files to the software management
server.
4. Save original log files.
5. Check whether the NEs mapped to the obtained log files have been subscribed to.
6. The software management server parses the log files of the subscribed NEs and saves
the parsing result in the database.
7.1.5 Technical Specifications of Log Management
This section describes the technical specifications related to the log management function.
Function Category Specification Item Value
Logs Maximum number of logs Microcomputer: 200,000
Mainframe : 1,000,000
Log Storage Days of log storage M2000 logs: 90
NE logs: 90

NOTE
How Do I Learn the Technical Specifications for Certain Functions? shows the categories of M2000 servers.
7.2 Synchronizing NE Logs
This section describes how to synchronize the operation logs and security logs on the M2000
server with those on NEs. This helps you obtain the latest logs from NEs.
Prerequisites
l You have logged in to the M2000 client.
l The NEs whose logs need to be synchronized are not virtual NEs and they must be
connected to the M2000 properly.
Context
For details about NEs that support log synchronization, see NEs Supporting Log
Synchronization.
The original log files of all NEs will be saved. When synchronizing logs of subscribed NEs, the
M2000 parses the original log files and saves the parsing result into the database. When
synchronizing logs of NEs that have not been subscribed to, the M2000 does not save the original
log files into the database. You can view these log files by importing them. For details, see 7.3
Importing NE Logs.
Procedure
l Manually synchronize NE logs by using NE operation logs as an example.
M2000
62
Two operation entries are available for manually synchronizing NE logs. You need to
perform different steps based on the entries.
Operation Entry Step
Topology view
1. Choose Topology > Main Topology. The Main
Topology window is displayed.
2. In the topology view, right-click an NE whose logs are to be
synchronized and choose Synchronize NE Operation &
Security Logs from the shortcut menu.
The information about the synchronization task is displayed on
the Immediate Task tab page after you click the NE tab in the
Software Browser window.
Log management
1. Choose System > Log Management > Query NE
Operation Logs.
2. In the Query NE Operation Logs dialog box, click
Synchronize.
3. In the displayed Synchronize NE Logs window, click
. The Select NE dialog box is displayed.
4. Select NEs whose logs are to be synchronized from the left
Available NEs area to the right Selected NEs area. You can
select a maximum of 10 NEs for synchronization at a time.
The information about the synchronization task is displayed on
the Immediate Task tab page after you click the NE tab in the
Software Browser window.
l Set scheduled synchronization for NE logs.
1. Choose Maintenance > Task Management.
2. In the navigation tree in the left pane of the Task Management window, choose the
NE Log Synchronization node.
3. In the task list in the Task Management window, double-click the NE Log
Synchronization task.
4. In the Attribute dialog box, modify common parameters. For details about the
parameters, see Parameters for Scheduled Task Properties.
5. Click OK.
l Subscribe to NEs.
Two operation entries are available for subscribing to NEs. You need to perform different
steps based on the entries.
M2000
63
Operation Entry Step
Log management
1. Choose System > Log Management > Query NE
Operation Logs.
2. In the Query NE Operation Logs dialog box, click
Subscribe.
3. Subscribe to NEs by referring to Subscription Type.
Task management
1. Choose Maintenance > Task Management.
2. In the navigation tree in the left pane of the Task
Management window, choose the NE Log
Synchronization node.
3. In the task list in the Task Management window, double-
click the NE Log Synchronization task.
4. In the Attribute dialog box, click the Extended
Parameters tab.
5. Subscribe to NEs by referring to Subscription Type.
Subscription Type
Subscribing to NEs by NE
Click By NE.
1. Click . The Select NE dialog box is displayed.
2. Select one or more NEs from the navigation tree in the left pane.
3. You can click to add the selected NEs to the effective area in the right
pane. You can click to add all NEs from the navigation tree in the left
pane to the effective area in the right pane.
NOTE
l You can click to delete the selected NEs from the effective area in the right
pane. You can click to delete all NEs from the effective area in the right
pane.
l You can click or to expand or collapse the nodes in the navigation tree.
l You can click and enter NE names in Name to filter NEs in the navigation tree.
4. Click OK.
Subscribing to NEs by NE type
Click By NE Type.
1. Click . The Select NE Type dialog box is displayed.
2. Select one or more NE types from the navigation tree in the left pane.
3. You can click to add the selected NE types to the effective area in the
right pane. You can click to add all NE types from the navigation tree in
the left pane to the effective area in the right pane.
M2000
64
NOTE
You can click to delete the selected NEs from the effective area in the right pane.
You can click to delete all NEs from the effective area in the right pane.
4. Click OK.
Subscribing to NEs on the entire network
Select All NEs. The system then subscribes to all existing NEs on the network.
CAUTION
If you select this subscription type, the system overhead will increase significantly.
Therefore, narrow down the subscription range as required.
----End
7.3 Importing NE Logs
You can view NE operation and security logs by importing original NE log files.
Context
CAUTION
If the active and standby servers in a remote HA system are switched over before original NE
log files are imported, original NE log files saved before the switchover cannot be imported. If
the active and standby servers are switched over then switched back, original NE log files saved
before the switchover can be imported.
Procedure
Step 1 Choose System > Log Management > Query NE Operation Logs or System > Log
Management > Query NE Security Logs.
Step 2 In the displayed window for querying logs, click Import.
Step 3 In the Import NE Logs dialog box, set Time Range and NEs.
1. Set Time Range.
Select From and To, type the date and time in the text boxes, or click and set time in
the Date/Time Selection dialog box.
For example, set the time range to 2011-11-10 00:00:00 2011-11-11 00:00:00.
2. Set NEs.
a. Click . The Select NE dialog box is displayed.
M2000
65
b. Select one or more NEs from the navigation tree in the left pane.
c. You can click to add the selected NEs to the effective area in the right pane.
You can click to add all NEs from the navigation tree in the left pane to the
effective area in the right pane.
NOTE
l You can click to delete the selected NEs from the effective area in the right pane.
You can click to delete all NEs from the effective area in the right pane.
l You can click or to expand or collapse the nodes in the navigation tree.
l You can click and enter NE names in Name to filter NEs in the navigation tree.
d. Click OK.
Step 4 Click OK to view the NE log import task in Immediate Task of the log query window.
NOTE
l The database capacity size is limited. You are advised to import log data by specifying a time range as
required to avoid significant increase of system overhead.
l When the database capacity reaches a threshold, the system displays a message stating that the NE log
data fails to be imported.
l Only one user can import NE log data within a time segment.
l If NE log data is being imported, do not synchronize NE logs until the import is complete. Otherwise,
the selected data to be imported may be deleted because of the limited database capacity.
----End
7.4 Managing the M2000 Operation Logs
You can query and collect statistics on operation logs of the M2000 to understand the operation
status of the M2000.
7.4.1 Querying the M2000 Operation Logs
You can query the M2000 operation logs to know the operation records of the M2000.
Context
l When you query operation logs by user name, only names of the users that have performed
operations are displayed under Available Operation User in the Select Operation User
dialog box.
l Operation log query scopes vary according to user.
Users in the Administrators group can query operation logs of all users.
Users in the SMManagers group who have the Query Operation Logs right can query
operation logs of all users.
Common users who do not belong to the Administrators or SMManagers group and
who have the Query Operation Logs right can query only their own operation logs.
To query operation logs of all users, set isQueryAll in the logsvc.xml file on the
M2000 server to 0, run the following command as user ossuser to import the parameters
in the file to the database, and restart the M2000 service for the setting to take effect.
(Assume that the following command is run in the Solaris operating system).
M2000
66
$ cd /opt/oss/server
$ . ./svc_profile.sh
$ SettingTool -cmd import -file /opt/oss/server/etc/conf/logsvc.xml
$ svc_adm -cmd reload
$ stop_svc
$ start_svc
l The statistical result is generated based on the existing data in the database. If the database
is empty, there is no statistical result.
l If a value in the Operation User column in the log query result is an invalid user, the system
may have been attacked.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs .
Step 2 In the Filter dialog box, set the filtering conditions, and then click OK.
NOTE
l You can also click Cancel in the Filter dialog box, and then query logs in the Query 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 M2000, see 7.12
Setting M2000 Log Templates to create a template.
l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs.
l In the Filter dialog box, click Choose in Operation Name, and view the operations that can be
monitored in the Select Operation Name dialog box. The Log out the server operation is not
monitored. Click Choose in Operation Object, and view the operation objects that can be monitored
in the Select Operation Object dialog box.
Step 3 Right-click in the query window and perform the following operations.
Operation Name Operation Method
Details Right-click a log in the window and choose Details, or double-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
l Log records can be saved in TXT, HTML, CSV, PDF, XLSX or XLS format.
The default file format is XLS.
l For .txt files, code formats ISO-8859-1 and UTF-8 are supported. The
default encoding format is ISO-8859-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.
M2000
67
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
l In the Save Specified Records dialog box, click on the right of File
name. In the Save dialog box, select the path for saving the records. Log
records can be saved in TXT, HTML, CSV, PDF, XLSX or XLS format.
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
M2000
68
7.4.2 Collecting Statistics on the M2000 Operation Logs
You can know the operation status by collecting statistics and analyzing the M2000 operation
logs. For example, you can collect statistics about the frequently performed operations within a
period.
Context
The statistical result is generated based on the existing data in the database. If the database is
empty, there is no statistical result.
Procedure
Step 1 Choose System > Log Management > Operation Log Statistics.
Step 2 In the Filter window, set the statistical items and statistical conditions, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Operation Log Statistics window in 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 M2000,
see 7.12 Setting M2000 Log Templates to create a template.
l Click Filter. Set Statistical Items and Filter Criteria in the Filter window, and then click OK to
collect statistics on operation logs.
----End
Result
In the Operation Log Statistics window, the statistical result is displayed.
The display mode of statistic results varies according to the settings on the Statistical Items tab
page in the Filter dialog box. The display mode of statistic results varies according to the settings
on the Statistical Items tab page. Table 7-1 describes the settings and display mode of the
Statistical Items tab page.
Table 7-1 Settings and display mode of the Statistical Items tab page
Row 1 Row 2 Column Display Mode
Do not set it to
(None).
Do not set it to
(None).
Set it to (Count). The statistic result is displayed as
follows:
l Row is displayed by Value.
l Column is displayed by Row
1, and Row 1 is displayed by
Row 2 in a collapsed tree.
Do not set it to
(None).
Set it to (None) Set it to (Count). The statistic result is displayed as
follows:
1 or Row 2.
Set it to (None). Do not set it to
(None).
Set it to (Count).
M2000
69
Do not set it to
(None).
Do not set it to
(None).
Do not set it to
(Count).
The statistic result is displayed as
follows:
l Row is displayed by
Column.
Do not set it to
(None).
(Count).
follows:
Column.
1 or Row 2.
(None).
Do not set it to
(Count).
Note: Row 1 and Row 2 are two statistical items in Statistical Row. Column is a statistical
item in Statistical Column.

In the Operation Log Statistics window, perform the following steps:
l Click Print to print the statistical result.
l Click Save As to save the statistical result.
7.5 Managing the M2000 System Logs
You can query and collect statistics on system logs of the M2000 to understand the running
status of the M2000.
7.5.1 Querying the M2000 System Logs
You can query the M2000 system logs to know the important events that occur when the
M2000 is running.
Context
Procedure
Step 1 Choose System > Log Management > Query System Logs.
M2000
70
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 M2000, see 7.12 Setting
M2000 Log Templates to create a template.
the log.
NOTE
click Save.
NOTE
Save Selected
Records
click Save.
NOTE
M2000
71
Save Specified
Records
Records.
OK.
NOTE
Print.
Print Selected
Records
Print.
Print Specified
Records
Records.
Print.
----End
7.5.2 Collecting Statistics on the M2000 System Logs
You can know the system status by collecting statistics and analyzing the M2000 system log.
For example, you can know the type of the services that raise the most alarms.
Context
Procedure
Step 1 Choose System > Log Management > System Log Statistics.
M2000
72
Step 2 In the Filter window, set the statistical condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the System Log Statistics window in the following
ways:
to use an existing template to collect statistics on system logs. If no template exists on the M2000, see
7.12 Setting M2000 Log Templates to create a template.
l Click Filter. Set the statistical condition in the Filter window, and then click OK to collect statistics
on system logs.
----End
Result
In the System Log Statistics window, the statistical result is displayed.
Row Column Display Mode
Set it to Level. Set it to (Count). The statistic result is displayed as follows:
l Column is displayed by Level or
Source.
Set it to Source. Set it to (Count).
Set it to Level. Set it to Source. The statistic result is displayed as follows:
l Row is displayed by Source.
l Column is displayed by Level.
Set it to Source. Set it to Level. The statistic result is displayed as follows:
l Row is displayed by Level.
l Column is displayed by Source.
Note: Row is a statistical item in the Statistical Row group box, and Column is a statistical
item in the Statistical Column group box.

In the System Log Statistics window, perform the following steps:
7.6 Managing the M2000 Security Logs
You can query and collect statistics on security logs of the M2000 to understand the security
operation status of the M2000.
M2000
73
7.6.1 Querying the M2000 Security Logs
You can query the M2000 security logs to know the M2000 security operations of the M2000.
Context
l The statistical result is generated based on the existing data in the database. If the database
is empty, there is no statistical result.
l If a value in the Operation User column in the log query result is an invalid user, the system
may have been attacked.
Procedure
Step 1 Choose System > Log Management > Query Security Logs.
NOTE
l You can also click Cancel in the Filter dialog box, and then query logs in the Query Security 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 M2000, see 7.12 Setting M2000 Log Templates to create a template.
l In the Filter dialog box, click Choose in Security Event, and view the operations that can be monitored
in the Select Security Event dialog box. The Log out the server operation is not monitored. Click
Choose in Operation Object, and view the operation objects that can be monitored in the Select
Operation Object dialog box.
the log.
NOTE
click Save.
NOTE
M2000
74
Save Selected
Records
click Save.
NOTE
Save Specified
Records
Records.
OK.
NOTE
Print.
Print Selected
Records
Print.
Print Specified
Records
Records.
Print.
----End
M2000
75
7.6.2 Collecting Statistics on the M2000 Security Logs
You can know the security operations by collecting statistics and analyzing the M2000 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 System > Log Management > Security Log Statistics.
Step 2 In the Filter window, set the statistical items and filtering conditions, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Security Log Statistics window in the following
ways:
to use an existing template to collect statistics on security logs. If no template exists on the M2000, see
7.12 Setting M2000 Log Templates to create a template.
l Click Filter. Set Items and Filter Criteria in the Filter window, and then click OK to collect statistics
on security logs.
----End
Result
In the Security Log Statistics window, the statistical result is displayed.
Do not set it to
(None).
Do not set it to
(None).
Set it to (Count). The statistic result is displayed as
follows:
Do not set it to
(None).
Set it to (None) Set it to (Count). The statistic result is displayed as
follows:
1 or Row 2.
(None).
Set it to (Count).
M2000
76
Do not set it to
(None).
Do not set it to
(None).
Do not set it to
(Count).
follows:
Column.
Do not set it to
(None).
(Count).
follows:
Column.
1 or Row 2.
(None).
Do not set it to
(Count).

In the Security Log Statistics window, perform the following steps:
7.7 Managing NE Operation Logs
You can query and collect statistics on operation logs of the NE to understand the operation
status of the NE.
7.7.1 Querying NE Operation Logs
You can query NE operation logs to know the operation records of the NE.
Context
The statistics result is generated based on the existing data in the database and sorted by time
(Greenwich Mean Time). If the database is empty, no statistics result is displayed accordingly.
Procedure
Step 1 Choose System > Log Management > Query NE Operation Logs.
Step 2 In the Filter Criteria window, set the filter conditions, and then click OK.
M2000
77
NOTE
You can also click Cancel, and then query logs in the Query NE Operation Logs window in the following
ways:
to use an existing template to query logs.
l Click Filter. Set the query conditions in the Filter Criteria window, and click OK to query logs.
----End
7.7.2 Collecting Statistics on NE Operation Logs
You can know the operation status of an NE by collecting statistics and analyzing the operation
log. For example, you can know the period during which maximum number of operations are
performed, and the period during which operations are performed most frequently.
Context
Procedure
Step 1 Choose System > Log Management > NE Operation Log Statistics .
Step 2 In the Filter Criteria window, set statistical items and filter criteria, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the NE Operation Log Statistics window in the
following ways:
to use an existing template to collect statistics on operation logs.
l Click Statistics. Set Statistics Items and Filter Criteria in the Filter Criteria window, and then click
OK to collect statistics on operation logs.
----End
Result
In the NE Operation Log Statistics window, the statistical result is displayed.
M2000
78
Do not set it to
(None).
Do not set it to
(None).
Set it to (None). The statistic result is displayed as
follows:
Do not set it to
(None).
Set it to (None) Set it to (None). The statistic result is displayed as
follows:
1 or Row 2.
(None).
Set it to (None).
Do not set it to
(None).
Do not set it to
(None).
Do not set it to
(None).
follows:
Column.
Do not set it to
(None).
(None).
follows:
Column.
1 or Row 2.
(None).
Do not set it to
(None).

In the NE Operation Log Statistics window, the statistical result is displayed.
Perform the following operations as required:
l Click Save to save the statistical result.
7.8 Managing NE Secrity Logs
You can query and collect statistics on security logs of the NE to understand the security
operation status of the NE.
M2000
79
7.8.1 Querying NE Security Logs
This section describes how to query NE security logs. You can query NE security logs to know
the security operations performed on NEs.
Context
Procedure
Step 1 Choose System > Log Management > Query NE Security Logs.
Step 2 In the Filter Criteria window, set filter criteria and click OK.
CBTS security logs are synchronized to the M2000 together with CBSC security logs. You can
enter BTS ID in Information Filter to query CBTS security logs when setting filter criteria.
NOTE
Alternatively, you can click Cancel and query logs in the Query NE Security Log window using either
of the following methods:
l Click Template, and choose Open. Select a template from the template list and click Open to use the
existing template to filter logs.
l Click Filter and set filter criteria in the Filter Criteria dialog box. Then, click OK.
----End
7.8.2 Collecting Statistics on NE Security Logs
You can know the security operations of an NE by collecting statistics and analyzing the security
log. For example, you can know the period during which maximum number of security
operations are performed, and the period during which operations are performed most frequently.
Context
Procedure
Step 1 Choose System > Log Management > NE Security Log Statistics.
Step 2 In the Filter Criteria window, set statistical items and filter condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the NE Security Log Statistics window in the
following ways:
to use an existing template to collect statistics on security logs.
l Click Statistics. Set Statistics Items and Filter Criteria in the Filter Criteria window, and then click
OK to collect statistics on security logs.
----End
M2000
80
Result
In the NE Security Log Statistics window, the statistical result is displayed.
Do not set it to
(None).
Do not set it to
(None).
Set it to (None). The statistic result is displayed as
follows:
Do not set it to
(None).
Set it to (None) Set it to (None). The statistic result is displayed as
follows:
1 or Row 2.
(None).
Set it to (None).
Do not set it to
(None).
Do not set it to
(None).
Do not set it to
(None).
follows:
Column.
Do not set it to
(None).
(None).
follows:
Column.
1 or Row 2.
(None).
Do not set it to
(None).

In the NE Security Log Statistics window, the statistical result is displayed.
Perform the following operations as required.
l Click Save to save the statistical result.
M2000
81
7.9 Browsing the NE Syslog Run Logs
After the IP address and port of an M2000 server are configured on network elements (NEs),
the NEs automatically upload Syslog run logs to the M2000. Then you can browse Syslog run
logs of NEs managed by the M2000 on the M2000, instead of browsing the logs on the NEs
individually.
Prerequisites
l The IP address and port of an M2000 server have been configured on NEs. For configuration
details, see product documentation for the NEs.
l The SyslogCollectorDM service has been started. By default, the SyslogCollectorDM
service is not started. For details about how to start the SyslogCollectorDM service, see
How Do I Start the Services that Are Disabled by Default in the M2000 Administrator
Guide.
Procedure
Step 1 Choose System > Log Management > NE Syslog Run Log .
Step 2 In the DRL File List navigation tree, double-click an NE Syslog run log file, such as
20120530170812. In the right pane, click a record to view log details.
NOTE
l The files in the device run log (DRL) file list are listed by time.
l You can enter the file name in the text box above the DRL File List navigation tree to filter the DRL
files. Only numbers from 0 to 9 are allowed. Then, the matched files are displayed in the DRL File
List navigation tree.
Step 3 Click Condition. In the Filter Criteria dialog box that is displayed, set the filter criteria for
filtering out NE syslog run logs.
Step 4 Click Query to query NE syslog run logs.
----End
7.10 Querying MML Logs
The MML log records all NE-related MML command operations and results returned by the
NEs, and save the MML commands and results to the database.
Prerequisites
l You are authorized to perform the related operations. For example, you are authorized to
query and delete an MML log.
Context
The MML logs are saved in the M2000 database omcdb, which contains a maximum of 100,000
log records. If the number of records exceeds 100,000, the first log records are replaced with the
latest records.
M2000
82
NOTE
MML logs are recorded when you use the following functions.
l CBSS Enhanced Configuration
l WiMAX Enhanced Configuration
l MSC Pool
l CDMA Pool
l SGSN Pool
l SingleSDB
l CSCF Pool
l MME Pool
Procedure
Step 1 Choose System > Log Management > MML Log Management.
Step 2 In the Query MML Log dialog box, set the conditions for querying the MML log.
1. In the Operated NE field, click . In the Operated NE Select dialog box, select an NE
whose MML log you want to query.
l You can select an NE in Available NEs, and click to move the NE to
Selected NEs.
l You can hold down Shift or Ctrl to select multiple NEs.
l You can click to move all the NEs from Available NEs to Selected
NEs.
l You can click or to remove the NEs from Selected NEs.
NOTE
You can query MML logs based on one or more of the following filtering criteria: NE name, MML
command head, module name, subscriber name, and date.
2. In the Time Range group box, set the start time and end time of running the MML
command.
3. Click Advanced. The system displays the other parameters related to the MML log query,
including MML Command, Module, User, and Terminal.
4. In the fields of the previous parameters, click one by one. In the displayed dialog box,
set these parameters.
If you do not set these parameters, the system queries all the MML logs by default.
Step 3 Click OK.
In the MML Log Management window, the system displays the information about all the
queried MML logs. For the contents and description of each MML log, see Table 1.
Operated NE Refers to the NE involved in the execution of
an MML command.
Module Refers to the module that generates MML
logs.
M2000
83
User Refers to the user who runs MML commands.
Terminal Refers to an operation terminal running MML
commands. The terminal is identified with an
IP address.
Start Time Refers to the time when the execution of
MML commands begins.
End Time Refers to the time when the execution of
MML commands ends.
MML Command Refers to the MML command to be executed.
Result Refers to the command result. The command
result can be either of the following types:
l Success: indicates that the MML
command is successfully executed.
l Failure: indicates that the MML command
cannot be executed.

Step 4 Select a record and double-click it. Alternatively, right-click a record, and then choose
Details. In the displayed MML Log Detail Info dialog box, view the details of the MML log.
l The detailed information that you can query includes the information listed in Table 1 and
the MML Report.
l You can query the information about other MML logs by clicking Previous or Next.
Step 5 Optional: Perform the following operations as required.
l In the MML Log Management window, click Delete to delete the logs that are not required.
l In the MML Log Management window, click Refresh to refresh the queried result.
l In the MML Log Management window, click Print to print the queried result.
l In the MML Log Management window, click Save As to save the queried result to a local
disk.
----End
7.11 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.11.1 Setting M2000 Log Dumping
By setting M2000 log dump, you can periodically or instantly dump security logs, operation
logs, and system logs of the M2000. The dumped logs are saved in files and deleted from the
database. This prevents database space insufficiency.
M2000
84
Prerequisites
You have logged in as a user in Administrators.
Context
Each of the types Operation Log Dump, Security Log Dump and System Log Dump has a
default system task that is provided by the M2000. 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.
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.
Step 5 Click OK.
NOTE
The time displayed in the M2000 log record is the start time of an operation. If the start time of the operation
is within the time range for dumping logs, but the operation is not complete when the time for dumping
logs is reached, this log record is not dumped to the log file.
----End
Result
You can view the M2000 log file in File path on the Extended Parameters tab page.
7.11.2 Setting M2000 Log Export
By setting M2000 log export, you can periodically or instantly export security logs, operation
logs, and system logs of the M2000. The exported logs are saved in files. Thus, they cannot be
deleted from the database.
Prerequisites
You have logged in as a user in Administrators.
Context
Each of the types Operation Log Export, Security Log Export and System Log Export has
a default system task that is provided by the M2000. 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.
M2000
85
Procedure
Step 2 In the Task Type navigation tree, choose File Interface > Operation Log Export,File
Interface > Security Log Export or File Interface > System Log Export.
NOTE
To perform the operations such as executing an export task instantly, suspending an task, and setting 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.13.12 Parameters for Setting M2000
Log Timing Export.
NOTE
The format of the export files of logs is CSV or XML or TXT or HTML.
Step 5 Click OK.
NOTE
The time displayed in the M2000 log record is the start time of an operation. If the start time of the operation
is within the time range for exporting logs, but the operation is not complete when the time for exporting
logs is reached, this log record is not exported to the log file.
----End
Result
You can view the M2000 log file in File path on the Extended Parameters tab page.
7.11.3 Setting NE Log Export
By setting NE log export, you can periodically or instantly export security logs and operation
logs of the NE. The exported logs are saved in files. Thus, they cannot be deleted from the
database.
Procedure
Step 2 In the Task Type navigation tree, choose File Interface > NE Operation Log Export or File
Interface > NE Security Log Export.
NOTE
The log export task is suspended by default.
To perform the operations such as executing an export task instantly, suspending an task, and setting 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.13.14 Parameters for the Export of
NE Logs.
M2000
86
NOTE
The format of the export files of logs is CSV or TXT.
Step 5 Click OK.
----End
7.12 Setting M2000 Log Templates
By setting M2000 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
l Choose System > Log Management > Query Operation Logs, System > Log
Management > Query System Logs, System > Log Management > Query Security
Logs, System > Log Management > Operation Log Statistics, System > Log
Management > System Log Statistics, System > Log Management > Security Log
Statistics . Click Template Filter to set the template.
l 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 System > Log Management > Query Operation Logs.
Step 2 In the Filter dialog box, click Cancel.
Step 3 You can perform the following operations in the Query Operation Logs window.
Task Operation
Create a template 1. Choose Template Filter > New.
2. In the Enter Template Name dialog box, enter the template name,
and then click OK.
3. In the Filter dialog box, set the filtering conditions of template
parameters, and then click OK.
Modify a template If there is already a log query template or a log statistics template on
the M2000, you can do as follows to modify the template:
1. Choose Template Filter > Open. Select a template in the Open
dialog box, and then click Open.
2. In the Query Operation Logs window, click Filter.
3. In the Filter dialog box, modify the query conditions in the log
template, and then click OK.
4. In the Query Operation Logs window, choose Template Filter >
Save.
M2000
87
Task Operation
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 M2000, you can do as follows to delete the template:
Delete the operations in the template.
1. Choose Template Filter > Delete.
2. In the displayed Delete dialog box, select the specified template.
3. Click Delete.
4. In the Confirm dialog box, click Yes.
5. In the Delete dialog box, click Close.
----End
7.13 References for Log Management Interfaces
This part describes reference information and the interface of log management. The contents in
this part consist of the log management interface and parameters involved in the process of
querying and taking statistics of NE logs, system logs, operation logs, and security logs. This
helps you perform the operations related to log management.
7.13.1 Interface Description: Log Management
This part describes the log management interface. You can have an understanding of each part
on the log management interface and their functions.
For details about the interfaces for log query or log statistics collection, refer to Figure 7-3.
After the filter conditions are set, the results of log query or log statistics collection are displayed
in the log window. You can save or print the results by clicking the buttons on the interface.
M2000
88
Figure 7-3 Log management interface

7.13.2 Parameters for Querying Operation Logs
This topic describes the parameters in the Query Operation Logs window and the Filter dialog
box. When querying operation logs or set the filter criteria for operation logs, you can refer to
this topic to set the filter criteria.
Parameters
Parameter Description Settings
Operation User Description:
To select operation users for
querying their operation logs.
Setting method:
In the Filter dialog box, click
. From the Select Operation
User dialog box, select an
operation user to be queried.
NOTE
By default, all users' operation logs
will be queried.
Operation Terminal 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.
NOTE
By default, the operation logs for all
users are queried.
M2000
89
Operation Result Description:
To query logs by operation result.
Value:
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.
Setting method:
In the Filter dialog box, select
one or more items from the
Operation Result group box.
Risk Level Description:
To query logs by risk level.
Value:
Value range: Warning, Minor,
and Risk
Setting method:
one or more items from the Risk
Level group box.
Time Range Description:
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.
Setting method:
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 Select Time dialog box.
Example:
Example: Set the time range to
02/08/2009
00:00:00-02/09/2009 00:00:00.
Detail information
contains
Description:
In the Query Operation Logs
window, you can set whether to
display the Details column of
operation logs.
In Detail information contains,
enter the information to be
displayed in the Details column.
The M2000 filters operation logs
based on the information
provided in Detail information
contains.
Setting method:
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.
M2000
90
Operation Name Description:
To query logs by operation.
Setting method:
corresponding
to Operation Name. In the
Select Operation Name dialog
box, select one or more items.
Operation Object Description:
To query logs by operation
object.
Setting method:
corresponding
to Operation Object. In the
Select Operation Object dialog
User Type Description:
User type of the user that
performs an operation, including
system administrator and local
user.
-
Operation Time Description:
Time when the operation is
performed.
-
Operation Category Description:
Category to which an operation
belongs.
-
Details Description:
Details about an operation.
-

7.13.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.
M2000
91
Statistical items
Row Statistical Item Description:
To set the row heading of
the statistical result table.
Value:
The parameter values
include None, Operation
User, User Type,
Operation Name,
Operation Category,
Operation Terminal,
Operation Result, and
Operation Object.
Statistical Item Description:
This parameter is the sub-
item of the preceding
parameter Statistical
Item.
Value:
User, User Type,
Operation Name,
Operation Category,
Operation Terminal,
Operation Object.
NOTE
You can set at most one of
both Statistical Item in
Row to None. The
statistical results are
grouped by Statistical
Item.
Column Statistical Item Description:
To set the column heading
of the statistical result
table.
Value:
include Count,
Operation User, User
Type, Operation Name,
Operation Category,
Operation Terminal,
Operation Object.
Example Description:
To preview the style of
-

M2000
92
Filter Criteria
To collect statistics by user.
Setting method:
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.
To select operation terminals.
Operation log statistics are
collected by operation terminal.
Setting method:
Operation Terminal dialog
To collect statistics by operation
result.
Value:
operation is being carried out
and all results are returned.
operation fails.
but part of operation results
are returned.
Setting method:
From the Operation Result
group box, select one or more
items.
level.
Value:
Warning, Minor, and Risk
Setting method:
From the Risk Level group box,
To collect statistics by time
range.
Setting method:
Select From and To check boxes
on the left side, and then enter the
date and time directly in the text
box, or click and set the time
in the Select Time dialog box.
Example:
02/08/2009
00:00:00-02/09/2009 00:00:00.
M2000
93
Detail information
contains
Description:
In the Operation Log Statistics
operation logs.
The M2000 filters operation logs
contains.
Setting method:
Select the Detail information
Operation Name Description:
To collect statistics by operation.
Setting method:
Click
corresponding to Operation. In
the Select Operation Name
dialog box, select one or more
items.
object.
Setting method:
Click
corresponding to Operation
Object. In the Select Operation
Object dialog box, select one or
more items.

7.13.4 Parameters for Querying System Logs
This topic describes the parameters in the Query System Logs window and the Filter dialog
box. When querying system logs or set the filter criteria for system logs, you can refer to this
topic to set the filter criteria.
Parameters
Source Description:
To select the source of system
logs for query.
Setting method:
. In the Select Source dialog
NOTE
By default, all sources' system logs
will be queried.
M2000
94
Level Description:
To query logs by log level.
Value:
Setting method:
Level group box.
To query logs by log operation
result.
Value:
operation fails.
l Unknown means that an
operation result is unknown.
If the value of Operation
Result in the Query System
Logs window is Unknown,
identify the cause of the
unknown operation result
based on Basic Information
and Details.
Setting method:
To query logs by time range. If
the time range is not set, all logs
generated at any time are
queried.
Setting method:
or click and set the time in
the Select Time dialog box.
Example:
02/08/2009
00:00:00-02/09/2009 00:00:00.
NOTE
To set the time format, choose
System > Preferences, expand
Region Settings, and then choose
the Time node. Set Time Format in
the area on the right.
M2000
95
Detail information
contains
Description:
In the Query System Logs
system logs.
The M2000 filters system logs
contains.
Setting method:
the Detail information
Time Description:
Time for executing a system
operation.
-
Basic Information Description:
Basic information about a system
operation.
-
Details about a system operation.
-

7.13.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
the statistical result
table.
Value:
include None,Level, and
Source.
To set the column
heading of the statistical
result table.
Value:
include Count, Level,
and Source.
To preview the style of
the statistical result
table.
-

M2000
96
Filter Criteria
Source Description:
To collect statistics by source.
Setting method:
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:
To collect statistics by log level.
Value:
Setting method:
From the Level group box, select
one or more items.
To query logs by log operation
result.
Value:
operation fails.
l Unknown means that an
operation result is unknown.
If the value of Operation
Result in the Query System
Logs window is Unknown,
identify the cause of the
unknown operation result
based on Basic Information
and Details.
Setting method:
From the Operation Result
group box, select one or more
items.
M2000
97
range. If the time range is not set,
all logs generated at any time are
queried.
Setting method:
Select From and To check box
on the left side, and then enter the
Example:
02/08/2009
00:00:00-02/09/2009 00:00:00.
NOTE
To set the time format, choose
System > Preferences, expand
Region Settings, and then choose
the Time node. Set Time Format in
the area on the right.
Detail information
contains
Description:
In the System Log Statistics
system logs.
The M2000 filters system logs
contains.
Setting method:

7.13.6 Parameters for Querying Security Logs
This topic describes the parameters in the Query Security Logs window and the Filter dialog
box. When querying security logs or set the filter criteria for security logs, you can refer to this
topic to set the filter criteria.
Parameters
To query logs by user.
Setting method:
. In the Select Operation
User dialog box, select one or
more items.
M2000
98
To query logs by IP address of the
terminal.
Setting method:
. In the Select Operation
Terminal dialog box, select one
or more items.
To query logs by operation result.
Value:
operation fails.
and part of operation results
are returned.
Setting method:
To query logs by risk level.
Value:
Setting method:
one or more items from the Risk
Level group box.
To query logs by time range. If
the time range is not set, all logs
generated at any time are queried.
Setting method:
or click and set the time in the
Select Time dialog box.
Example:
02/08/2009 00:00:00-02/09/2009
00:00:00.
M2000
99
Detail information
contains
Description:
In the Query Security Logs
security logs.
The M2000 filters security logs
contains.
Setting method:
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.
Security Event Description:
To query logs by security event.
Setting method:
corresponding
to Security Event. In the Select
Security Event dialog box, select
one or more items.
To query data by operation
object.
Setting method:
corresponding
to Operation Object. In the
Select Operation Object dialog
User Type Description:
User type of the user that
performs a security event,
including system administrator
and local user.
-
Operation Time Description:
Time for executing a security
event.
-
Details about a security event.
-

7.13.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.
M2000
100
Statistical items
Value:
User, User Type,
Security Event,
Operation Terminal,
Operation Result,
Operation Object, and
Risk Level.
Statistical Item Description:
This parameter is the sub-
item of the preceding
parameter Statistical
Item.
Value:
User, User Type,
Security Event,
Operation Terminal,
Operation Result,
Risk Level.
NOTE
You can set at most one of
both Statistical Item in
Row to None. The
statistical results are
grouped by Statistical
Item.
To set the column heading
of the statistical result
table.
Value:
include Count,
Operation User, User
Type, Security Event,
Operation Terminal,
Operation Result,
Risk Level.
NOTE
If the value of Row is set to
Operation User or User
Type, the value of
Column cannot be set to
Operation User or User
Type.
To preview the style of the
statistical result table.
Value:
-

M2000
101
Filter Criteria
To collect statistics by user.
Setting method:
Operation User dialog box,
To collect statistics by IP address
of the terminal.
Setting method:
Operation Terminal dialog box,
result.
Value:
operation fails.
the operation is complete, and
some operation results are
returned.
Setting method:
In the Result area, select one or
more items.
To collect statistics by risk level.
Value:
Setting method:
From the Risk Level group box,
range. If the time range is not
specified, all logs generated at
any time are queried.
Setting method:
Select From and To check box on
the left side, and then enter the
Example:
02/08/2009 00:00:00-02/09/2009
00:00:00.
M2000
102
Detail information
contains
Description:
In the Security Log Statistics
security logs.
The M2000 filters security logs
contains.
Setting method:
Security Event Description:
To collect statistics by security
event.
Setting method:
Click
corresponding to Security
Event. In the Select Security
Event dialog box, select one or
more items.
object.
Setting method:
Click
corresponding to Operation
Object. In the Select Operation
Object dialog box, select one or
more items.

7.13.8 Parameters for Querying NE Operation Logs
This describes the parameters in the Filter Criteria dialog box when you query NE operation
logs.
Table 7-6 describes the parameters for querying NE operation logs.
Table 7-6 Parameters for querying NE operation logs
Query
Condition
Description Setting
User Query NE operation logs by user.
Click , and then select one or
multiple items from the Select User
dialog box.
Terminal Query NE operation logs by terminal.
Click , and then select one or
multiple items from the Select
Terminal dialog box.
M2000
103
Query
Condition
Description Setting
User Type Query NE operation logs by user type.
The user type can be Local, EMS, or
EMSOP.
Select one or multiple items from the
User Type area.
Result Query NE operation logs by operation
result.
The result can be Succeeded or
Failed.
Select one or multiple items from the
Result area.
MML Query NE operation logs by MML
command.
Enter the MML command to be
filtered out in the text box in the
MML area.
NOTE
The filtering of MML commands
supports the accurate search. You need to
enter a part of an MML command, and
then the system queried the NE operation
logs containing the entered MML
command.
Time Range Query NE operation logs by time
range.
From indicates the start time, and
To indicates the end time.
Select From and To, and enter the
date and time in the text box.
Alternatively, click . In the Date/
Time Selection dialog box, set the
date and the time.
For example, set the time range to
2002-02-09 00:00:00 2003-02-09
00:00:00.
NE Name Query NE operation logs by NE. Click Select corresponding to NE
Name, and then select one or multiple
items from the Select NE dialog box.

7.13.9 Parameters for Statistics on NE Operation Logs
This section describes the statistical items in the Filter Criteria dialog box. You can refer to
this section when setting items for collecting statistics about NE operation logs.
Statistical Items
Name Description Settings
Statistic Row Description:
To set the row heading of the
Value:
You must select one or two statistical
items. The statistical results are
sorted by statistical item.
M2000
104
Statistical
Column
Description:
To set the column heading of the
Value:
Statistical item under Statistical
column must be set.
Statistical
Item
Description:
To set the row heading and column
heading of the statistical result table.
Value:
l User: Name of a user that
performs the operation.
l Result: result of an operation,
including succeeded and failed.
l NE: name of the NE on which an
operation is performed.
l NE Type: type of the NE on
which an operation is performed.
l Terminal: identified with an IP
address.
l User Type: identifies the domain
attributes of a user in the NE
operation log, including EMS,
Local, and EMSOP.
To preview the style of the statistical
result table.
Value:
-

Filter conditions
Filter
Condition
Description Settings
User To collect statistics by user.
Click , and then select one or more
items from the User Select dialog
box.
Terminal To collect statistics by terminal.
Click , and then select one or more
items from the Terminal Select
dialog box.
User Type To collect statistics by user type.
User types include Local, EMS, and
EMSOP.
Select one or more items from the
User Type area.
Result To collect statistics by result. Select one or more items from the
Result area.
M2000
105
Filter
Condition
Description Settings
MML To collect statistics by the keyword of
MML filtering conditions.
Enter the keyword (such as LST VER)
of a filtering condition in the MML
area.
NOTE
The filtering of MML commands
supports the accurate search. You need to
enter a part of an MML command, and
then the system queried the NE operation
logs containing the entered MML
command.
Time Range To collect statistics by time range.
From indicates the start time, and
Select From and To, and then enter
the date and time in the text box.
Alternatively, click , and then set
the date and the time in the Date/Time
Selection dialog box.
2002-02-09 00:00:00 2003-02-09
00:00:00.
NE Name To collect statistics by NE. Click Choose corresponding to NE
Name. Select one or more items from
the NE Name: Choose dialog box.

7.13.10 Parameters for Querying NE Security Logs
This section describes the parameters for querying NE security logs.
Table 7-7 describes the parameters for querying NE security logs.
Table 7-7 Parameters for querying NE security logs
Query
Criterion
Description Setting
User Queries NE security logs by user.
Click and select one or more items
in the User Select dialog box.
Terminal Queries NE security logs by terminal.
Click and select one or more items
in the Terminal Select dialog box.
User Type Queries NE security logs by user type.
User types are Local, EMS, and
EMSOP.
Select one or more items in the User
Type area.
M2000
106
Query
Criterion
Description Setting
Result Queries NE security logs by operation
result.
Operation results are Succeeded and
Failed.
Select one or more items in the
Result area.
Security
Levels
Queries NE security logs by security
event level.
Security event levels are Urgent,
Important, and Subordinate.
Select one or more items in the
Security Levels area.
Information
Filter
Filters information based on the
entered content in the Information
field and displays NE security logs
that meet the criterion.
Optional
For CBSCs, use either of the
following methods:
l Type BTS ID to query all logs
containing BTS ID in CBSC
security logs.
l Type BTS ID=100 to query
security logs of BTS ID=100.
For other NEs, type the content set in
the Information field to filter logs
Time Range Queries NE security logs by time
range.
From indicates the start time and To
indicates the end time.
Select From and To, type the date and
time in the text boxes, or click and
set time in the Date/Time Selection
dialog box.
2002-02-09 00:00:00 2003-02-09
00:00:00.
NEs Queries NE security logs by NE. Click Choose corresponding to NE
and select one or more items in the
NEs Select dialog box.

7.13.11 Parameters for Statistics on NE Security Log
This part describes the items set in the Filter Criteria dialog box. Refer to this part when you
set items for collecting statistics on NE security logs.
M2000
107
Statistical Items
Statistic Row Description:
To set the row heading of the
Value:
You must select one or two
statistical items. The statistical
results are sorted by statistical
item.
Statistic Column Description:
To set the column heading of the
Value:
The Statistic Item parameter
under Statistic Column is
mandatory.
Statistic Item Description:
To set the row heading and
column heading of the statistical
result table.
Value:
l User: Name of a user that
performs the operation.
l Result: result of an
operation, including
succeeded and failed.
l NE: name of the NE on
which an operation is
performed.
l NE Type: type of the NE on
which an operation is
performed.
l Terminal: identified with an
IP address.
l User Type: identifies the
domain attributes of a user in
the NE operation log,
including EMS, Local, and
EMSOP.
l Security Level: security
level of the logs, including
Urgent, Important, and
Subordinate.
Preview the style of the
Value:
-

M2000
108
Filter conditions
Filter
Condition
Description Setting
User To collects statistics by user
Click . Select one or more items
from the User Select dialog box.
Terminal Collects statistics by terminal
Click . Select one or more items
from the Terminal Select dialog box.
User Types Queries by user type
The user type falls into the Local, the
EMS, and the EMSOP categories.
User Types group box.
Result Collects statistics by operation
results.
The results are either Succeeded or
Failed.
Result group box.
Security
Levels
Collects statistics by security level
The security levels are Urgent,
Important, and Subordinate.
Security Levels group box.
Information
Filter
Filters information based on the
entered content in the Information
field and displays NE security logs
Optional
For CBSCs, use either of the
following methods:
l Type BTS ID to query all logs
containing BTS ID in CBSC
security logs.
l Type BTS ID=100 to query
security logs of BTS ID=100.
For other NEs, type the content set in
the Information field to filter logs
Time Range Collecting statistics by time range
From indicates the start time, while
Select From and To, and enter the
date and time in the text box.
Alternatively, click . In the Date/
Time Selection dialog box, set the
date and the time.
For instance, set the time range to
2002-02-09 00:00:00 2003-02-09
00:00:00.
M2000
109
Filter
Condition
Description Setting
NEs Collecting statistics by NE Click Choose at the lower part of
NEs. Select one or more items from
the NEs Select dialog box.
NOTE
The NEs Select dialog box displays the
NEs that are in connection state on the
topology view and has data stored in the
database.

7.13.12 Parameters for Setting M2000 Log Timing Export
This topic describes the parameters for setting M2000 log timing export in the centralized task
management. When you set log timing export, you can refer to this topic to perform setting.
Parameters
Table 7-8 Common Parameters for Periodic Tasks
Task name Description:
Refers to the name of a timing task.
Value:
l A maximum of 64 bytes.
l Unique and not null.
l Case sensitive.
Execution
type
Description:
l One-time: If you select this
option, the system runs the
created task once at the defined
time point.
l Periodic: If you select this
created task periodically.
Value:
l One-time
l Periodic
Start time Description:
This parameter sets the time for
starting a task.
Value:
The start time should be later than the
time displayed on the server.
Task type Description:
Refers to the type of a timing task.
-
M2000
110
Execution
interval
Description:
Interval between periodic tasks. It
has two enlistments: duration and
unit.
Value:
l The period can be represented in
either of the following units:
minutes, hours, days, weeks,
months. Second is not supported.
The supported units of Period 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:
This parameter indicates the times
that a periodic task is executed.
NOTE
This parameter is displayed in the
Attribute dialog box only after you
set it when creating and copying a
periodic task.
Value:
0 - 65535.
NOTE
0 indicates that the number of times for
executing periodic tasks is not restricted.
End time Description:
End time of a periodic task.
NOTE
periodic task.
Value:
Later than Start time, and earlier than
01/18/2038 11:14:07.

Table 7-9 Extended Parameters
Parameter Description Setting
Compress
file after
export
Description:
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.
Value:
Value range: Yes or No
Default value: Yes
Export File
Type
Description:
This parameters indicates the format of the export
files of logs.
Value:
Value range: CSV,
XML, TXT or HTML.
M2000
111
File path Description:
Path for storing log files on the M2000 server.
Value:
Value: a specified path
Rule: It is not
recommended to
change the default file
path. If you need to
specify a new file path,
ensure that the user
ossuser has permission
to read and write the
target folder under this
path.
Export File
Managemen
t
Description:
Hold files for XX days: If the retention period of
the export file exported to a specified folder
exceeds this period, the file is deleted.
Value:
Value range: 1-180
Default value: 15
Description:
Hold max. XX files: If the number of export files
exported to the specified folder is greater than this
value, the M2000 deletes the oldest export files
until the number of files in this folder becomes less
than the value of this parameter.
Value:
Value range: 200-2000
Default value: 1000
Description:
Hold max. XX MB file data: If the total size of the
export files in the specified folder is greater than
this value, the M2000 deletes the oldest export files
until the number of files in this folder becomes less
than the value of this parameter.
Value:
Default value: 1024

7.13.13 Parameters for Setting M2000 Log Timing Dump
This topic describes the parameters for setting M2000 log timing dump in the centralized task
management. When you set log timing dump, you can refer to this topic to perform setting.
M2000
112
Parameters
Table 7-10 Common Parameters for Periodic Tasks
Task name Description:
Refers to the name of a timing task.
Value:
l A maximum of 64 bytes.
l Unique and not null.
l Case sensitive.
Execution
type
Description:
l One-time: If you select this
created task once at the defined
time point.
l Periodic: If you select this
created task periodically.
Value:
l One-time
l Periodic
Start time Description:
This parameter sets the time for
starting a task.
Value:
The start time should be later than the
time displayed on the server.
Task type Description:
Refers to the type of a timing task.
-
Execution
interval
Description:
Interval between periodic tasks. It
has two enlistments: duration and
unit.
Value:
l The period can be represented in
either of the following units:
minutes, hours, days, weeks,
months. Second is not supported.
The supported units of Period 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:
This parameter indicates the times
that a periodic task is executed.
NOTE
periodic task.
Value:
0 - 65535.
NOTE
0 indicates that the number of times for
executing periodic tasks is not restricted.
M2000
113
End time Description:
End time of a periodic task.
NOTE
periodic task.
Value:
Later than Start time, and earlier than
01/18/2038 11:14:07.

Table 7-11 Extended Parameters
Compress
file after
export
Description:
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.
Value:
Value range: Yes or No
Default value: Yes
File type Description:
This parameters indicates the format of the dump
files of logs.
Value:
Value range: CSV,
XML, TXT or HTML.
File path Description:
File path indicates the path of the dump file. The
dump file is stored on the M2000 server.
Value:
You can select the
folder for saving the
dumped files in File
path.
The default file path on
the M2000 server is /
opt/oss/server/var/
ThresholdExport/
Log.
Rule: It is not
recommended to
change the default file
path. If you need to
specify a new file path,
ensure that the user
ossuser has permission
to read and write the
target folder under this
path.
Storage
period in
database
(days)
Description:
When a dump task is executed, the logs older than
this period are dumped.
Value:
Value range: 1-180
Default value: 30
M2000
114
Dump File
Managemen
t
Description:
Hold files for XX days: If the retention period of
the dump file in a specified folder exceeds this
period, the file is deleted.
Value:
Value range: 1-180
Default value: 15
Description:
Hold max. XX files: If the number of dump files
in the specified folder is greater than this value, the
M2000 deletes the oldest dump files until the
number of files in this folder becomes less than the
value of this parameter.
Value:
Default value: 1000
Description:
Hold max. XX MB file data: If the total size of the
dump files in the specified folder is greater than this
value, the M2000 deletes the oldest dump files until
the number of files in this folder becomes less than
the value of this parameter.
Value:
Default value: 1024

7.13.14 Parameters for the Export of NE Logs
This section describes the parameters for exporting NE logs and can be taken as reference during
the parameter modification.
Table 7-12 lists the extended parameters.
Table 7-12 Descriptions of extended parameters
Parameter Value Range Description
File Format You can select .txt or .csv. Exports the operation logs to a .txt
file or .csv file.
File Path Default value: No change.
The default path is: /opt/oss/
server/var/fileint/nelogs/.
Saves NE logs.
M2000
115
Parameter Value Range Description
File Size Unit: MB
Default value: 1024
Refers to the threshold of the
space for dumping log files.
During the export of log files, if
the size of the files existing in the
specified path exceeds the preset
threshold, the earliest files are
replaced.
NOTE
When setting the threshold of dump
space, the size of the partition that the
path for saving log files belongs to
must be taken into account. The
threshold cannot exceed the size of
the partition.
File Hold Days Unit: day
Default value: 3
Refers to the number of the days
within which the dump files can be
saved. After these days, the files
are automatically deleted.
File Sum Number of files
Default value: 1000
Refers to the maximum number of
files in the dump space. During the
export of log files, if the number
of the files existing in the specified
path exceeds the preset threshold,
the earliest files are replaced.

7.13.15 Parameters for Querying NE Syslog Run Logs
This topic describes the parameters in the NE Syslog Run Log window and the Fitter
Criteria dialog box. You must set these parameters to query NE syslog run logs and set filter
criteria for NE syslog run log query.
Button Description
Button Description
Condition Displays the Fitter Criteria dialog box for setting filter criteria.
Query Queries required NE syslog run logs.
Refresh Synchronizes the latest log data on the server to the client.

M2000
116
Parameters for Setting Filter Criteria
NE Name Description:
Name of an NE whose syslog run
logs are to be queried.
Setting method:
Select NE Name and enter an NE
name in the text box.
NOTE
Wildcard characters are supported.
The asterisk (*) indicates a character
string, and the question mark (?)
indicates a single character except the
single quotation mark ('), percent (%),
and caret (^).
IP Address Description:
IP address of an NE whose syslog
run logs are to be queried.
Setting method:
Select IP Address and enter an IP
address in the text box.
NOTE
string.
Digest Description:
Log digest to be queried.
Setting method:
Select Digest and enter a log digest
in the text box.
NOTE
and caret (^).
Log details to be queried.
Setting method:
Select Details and enter log details
in the text box.
NOTE
and caret (^).
Module Name Description:
Name of a module whose NE
syslog run logs are to be queried.
Setting method:
Select Module Name and select a
module name from the drop-down
list box.
M2000
117
Level Description:
Level of logs to be queried.
Value:
Comparison operators for log
levels are listed as follows:
l =
l >
l >=
l <
l <=
Log levels are listed in descending
order as follows:
l Emergency
l Alert
l Critical
l Error
l Warning
l Notice
l Informational
l Debug
Setting method:
Select Level, select a comparison
operator from the first drop-down
list box, and select a log level from
the second drop-down list box.
Sending Time Description:
Time segment in which NE syslog
run logs are reported. If the time
segment is not set, all logs
generated at any time are queried.
Setting method:
l Select From or To and enter a
time in the text box.
l Select From or To, move the
pointer in the text box, and
click or to adjust the
value of the pointer position.
l Select From or To, click ,
and set a time in the Select
Time dialog box.
M2000
118
8 Managing the M2000 Processes and Services
About This Chapter
This section describes how to manage the M2000 processes so that the processes and services
on the M2000 server can function properly. The enterprise wireless network solution does not
support northbound functions and therefore there is no northbound process.
8.1 Introduction to M2000 Processes and Services
When the M2000 is running, the M2000 server automatically starts the processes related to the
M2000 system. Each process provides different services and functions.
8.2 Viewing the Running Status of M2000 Services (SUSE)
This describes how to view the status of M2000 services on the M2000 server. This operation
requires only few system resources and does not affect system performance.
8.3 Starting the M2000 Services (SUSE)
After you run the start_svc command, all the M2000 services are started. If an M2000 service
is already started, the system does not handle the service. Actually, the system starts only the
inactive services.
8.4 Stopping the M2000 Services (SUSE)
This describes how to stop the M2000 services. After the M2000 services are stopped, the
M2000 processes are stopped. In this situation, NE performance data and alarm data cannot be
processed. After the services are resumed, the M2000 updates the data with the NEs and
processes the data.
M2000
Administrator Guide (x3850&x3650, SUSE10) 8 Managing the M2000 Processes and Services
119
8.1 Introduction to M2000 Processes and Services
When the M2000 is running, the M2000 server automatically starts the processes related to the
M2000 system. Each process provides different services and functions.
8.1.1 3rdTool_agent Process
This section describes the 3rdToolService service and dependent services.
The 3rdTool_agent process provides the 3rdToolService service.
The 3rdToolService service provides an interface for the third-party tools to access the data
center.
Required services: ScriptServer
8.1.2 ActiveMQ Process
This section describes the services and functions provided by the ActiveMQ process.
The ActiveMQ process provides the ActiveMQ service.
The ActiveMQ service provides the northbound interface that supports Java Messaging Service
(JMS) notifications.
Dependent service: none
8.1.3 adn_agent Process
This section describes the services and functions provided by the adn_agent process.
The adn_agent process provides the ADNService service.
The ADNService service supports the NodeB plug-and-play function. It provides various
functions for newly constructed NodeBs, such as remote automatic activation and automatic
fault detection. This helps engineers quickly deploy NodeBs.
You can disable the service when it is not required.
Required services: none
8.1.4 adss_agent Process
This section describes the services and functions provided by the adss_agent process.
The adss_agent process provides the AdvancedSwitchService service.
The AdvancedSwitchService service authenticates the MOI resources to enhance the security
of the operations on the NEs, and deepen the security level hiberarchy.
8.1.5 antenna_agent Process
This section describes the services and functions provided by the antenna_agent process.
M2000
120
The antenna_agent process provides the AntennaTune service.
The AntennaTune service provides the functions of managing NodeB antennas and locating the
faults related to GBSS antennas.
Required service: EAMService.
8.1.6 ce_agent Process
This section describes the services and functions provided by the ce_agent process.
The ce_agent process provides the ConfigExport service.
The ConfigExport service provides a transparent channel which enables the northbound NMS
to directly obtain configuration data and set NE configurations from the GBSS.
If this function is required, you must ensure that the service runs normally.
Required services: none.
8.1.7 cmdc_agent Process
This section describes the CmDcService service and dependent services. CmDcService is
provided by the cmdc_agent process.
The cmdc_agent process provides the CmDcService service.
The CmDcService service provides the functions such as data access interface, synchronization
management, and session management.
Required services: TopoAdapterService
8.1.8 cmengine_agent Process
This section describes the services and functions provided by the cmengine_agent process.
The cmserver_agent process provides the CMEngine service.
CMEngine manages the configuration of the network manager. Configuration management is
independent of NEs or managed objects.
When the M2000 is running, ensure that this service functions properly.
Required services: TopoAdapterService.
8.1.9 cmeserver_agent Process
This section describes the services and functions provided by the cmeserver_agent process.
The cmeserver_agent process provides the CmeServer service.
The cmeserver_agent service provides the function of quickly configuring NEs.
You can disable the service when it is not required.
Required service: TopoAdapterService.
8.1.10 cmexp_agent Process
This section describes the service and functions provided by the cmexp_agent process.
M2000
121
The cmexp_agent process provides the CMExport service.
The CMExport service provides the functions of exporting configuration files and exporting the
configuration database.
Through the CMExport service, you can set the NE whose configuration data is to be exported,
set the save path and file format of the exported data, and export the NE configuration data by
using the Management Information Tree (MIT).
To enable the functions of exporting configuration files and exporting the northbound database,
you need to ensure that this service is running normally.
Dependent service: LicenseService.
8.1.11 cmserver_agent Process
This section describes the services and functions provided by the process cmserver_agent.
The cmserver_agent process provides the CMServer service.
CMserver configures the managed objects of the network manager. Configuration management
is independent of NEs or managed objects.
The CMServer provides channels for issuing MML commands and helps to receive the
supplementary messages reported automatically by NEs.
The CMServer provides the function of managing object groups and enables the M2000 to
automatically and remotely commission the NodeB upgrade.
Required services: TopoAdapterService
8.1.12 corba_agent Process
This section describes the services and functions provided by the corba_agent process.
The corba_agent process provides the CorbaService service.
The CorbaService provides the NBI on which the TMF 814 CORBA protocol runs.
Required services: LicenseService, LogService, SecurityService.
8.1.13 cpm_agent Process
This section describes the services and functions provided by the cpm_agent process.
The cpm_agent process provides the CPMService service, that is, the pool configuration
management service.
The Pool configuration management service provides users with the following functions:
l Creating a pool
l Checking pool alarms
l Measuring the performance of a pool
l Monitoring the load of a pool in real time
l Displaying the pool topology
M2000
122
l Setting pool parameters
l Checking the NE data in a pool
l Checking the MSC Server or MSCe of a specific user
8.1.14 devdoc_agent Process
This section describes the DevDocService service provided by the devdoc_agent process.
The devdoc_agent process provides the DevDocService service.
The DevDocService service enables you to manage device files.
8.1.15 DrlDm Process
This section describes the services and functions provided by the DrlDm process.
The DrlDm process provides the DrlDm service.
The DrlDm service provides the NE running log components.
8.1.16 dsXXXX agent Process
This section describes the services and functions provided by the dsXXXX_agent process.
The dsXXXX_agent process provides the DesktopServiceXXXX service.
Some typical process names are ds0101_agent and ds0102_agent. The corresponding service
names are DesktopService0101 and DesktopService0102.
dsXXXX_agent is a multi-instance process and XXXX refers to the process number.
The DesktopServiceXXXX service presents and operates data on several types of clients such as
the Java GUI client and the Web client.
You can log in to the client only when the DesktopServiceXXXX service is running properly.
During the operation of the M2000, ensure that this service is running properly.
Required service: none.
8.1.17 eam_agent Process
This section describes the services and functions provided by the eam_agent process.
The eam_agent process provides the EAMService, TopoAdapterService, and TopoService
services.
The EAMService service provides the function of NE access management and maintains a
globally complete NE list. The EAMService service does not depend on any other services.
The TopoAdapterService service provides the mediation for earlier versions so that the users
who use the earlier versions can use the topology function. The TopoAdapterService service
depends on the EAMService, TopoService, LogService, and SecurityService services.
M2000
123
The TopoService service can maintain the relation between the devices in the subnet, create and
delete subnets, nodes, and topology node, and move nodes among subnets. The TopoService
service depends on the EAMService services.
8.1.18 fars_agent Process
This section describes the service and function provided by the fars_agent process.
The fars_agent process provides the FarsService.
The FarsService provides the function of tracing data collection, data analysis, and data
collection management.
To enable the tracing function, you need to ensure that the FarsService is running normally
during the operation of the M2000.
Dependent service: none.
8.1.19 fmmedXXXX_agent Process
This section describes the services and functions provided by the fmmedXXXX_agent process.
The fmmedXXXX_agent process provides the FMMediationServiceXXXX service.
fmmedXXXX_agent is a multi-instance process, where XXXX is the instance number. Generally,
the processes are named fmmed0101_agent and fmmed0102_agent and related services are
named FMMediationService0101 and FMMediationService0102.
FMMediationServicexxxx receives alarms reported by NEs that comply with different protocols.
In the ATAE cluster system system, this process can be deployed on the master and slave servers.
On the master server, the process names are fmmed0101_agent and fmmed0102_agent. On the
first slave server, the process names are fmmed0201_agent and fmmed0202_agent. On the
second slave server, the process names are fmmed0301_agent and fmmed0302_agent. The same
rule applies to the other slave servers.
Independent service: trapdispatcher.
8.1.20 fmnotify_agent Process
This section describes the services and functions provided by the fmnotify_agent process.
The fmnotify_agent process provides the FMNotify service.
FMNotify forwards the alarm data from FaultManager to the network management system
(NMS) by Alarm Streaming Interface.
Disable FMNotify when the real-time alarm forwarding function is not required.
Required services: LicenseService.
8.1.21 FMPreServiceXXXX_agent Process
This section describes the services and functions provided by the FMPreServiceXXXX_agent
process.
The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service.
M2000
124
The FMPreServiceXXXX_agent process is a multi-instance process. XXXX refers to the process
number.
The FMPreServiceXXXX service provides the function of prehandling faults.
In the ATAE cluster system, you can deploy the FMPreServiceXXXX_agent process on the
master node and several slave nodes. You can also deploy multiple FMPreServiceXXXX_agent
processes on one node. For example, you can deploy the FMPreService0101_agent,
FMPreService0102_agent, and FMPreService0103_agent processes on the master node for
providing the FMPreService0101, FMPreService0102, and FMPreService0103 services
separately. You can also deploy the FMPreService0201_agent, FMPreService0202_agent, and
FMPreService0203_agent processes on a slave node for providing the FMPreService0201,
FMPreService0202, and FMPreService0203 services separately.
8.1.22 fnlicense_agent Process
This section describes the services and functions provided by the fnlicense_agent process.
The fnlicense_agent process provides the FNLicenseService service.
The FNLicenseService provides the fix network management function of managing the license
authorization information about EMS. The number of purchased licenses determines the number
of available resources and whether the user can use a specific functional component.
8.1.23 gem_agent Process
This section describes the services and functions provided by the gem_agent process.
The gem_agent process provides GEMService.
This service receives energy consumption summaries reported by devices, and displays statistics
and analysis on the energy consumption of devices.
Required services: None.
8.1.24 glmssyn_agent Process
This section describes the services and functions provided by the glmssyn_agent process.
The glmssyn_agent process provides the GLMSSynService service.
The GLMSSynService periodically obtains the information about QChat cluster communication
changes from the Group and List Management Server (GLMS) and then applies the information
to CBSCs.
You can stop this process if the QChat cluster communication is not required.
8.1.25 ifms_agent Process
This section describes the service and functions provided by the ifms_agent process.
The ifms_agent process provides the FaultService.
M2000
125
The FaultService collects alarm data from NEs and saves the data, thus providing the functions
of querying, dumping, and analyzing the fault data.
You can disable the service when fault management is not required.
8.1.26 ipm_agent Process
This section describes the services and functions provided by the ipm_agent process.
The ipm_agent process provides the IPMService service.
The IPMService service enables you to manage an IP network.
To use the IP network management function, ensure that the IPMService service is running
correctly during the operation of the M2000.
8.1.27 irp_agent Process
This section describes the functions provided by the irp_agent process.
EPIRP
The EPIRP is subject to the entry point object. The entry point object is the first object that the
NMS (Manager) accesses when the NMS interacts with the M2000 (Agent). The Agent provides
a reference of an entry point object to the Manager, and the Manager obtains the reference of
this entry point object in some way, for example, from the stored file. If the interface for
northbound network management is not required, disable the EPIRP.
Basic IRP: None.
NotificationIRP
NotificationIRP is used for subscribing to notifications and encapsulating notification
subscription. If the function of subscription through the interface of northbound network
management is not required, disable the NotificationIRP.
Basic IRP: EPIRP.
CSIRP
CSIRP provides an interface for link monitoring.
The link monitoring enables you to supervise the status of links between the Manager and the
Agent. In this way, the potential exceptions can be detected at the first time. If the function of
monitoring through the interface of northbound network management is not required, disable
the CSIRP.
Basic IRP: EPIRP, and NotificationIRP.
KernelCMIRP
KernelCMIRP provides an interface for public configuration management.
M2000
126
The public configuration management uses KernelCMIRP to carry out some common tasks
during the configuration, such as sending configuration objects, or adding, removing and
modifying notifications. If the function of public configuration management through the
interface of northbound network management is not required, disable the kernelCMIRP.
Basic IRP: EPIRP, and NotificationIRP.
BasicCMIRP
BasicCMIRP controls the configuration management. BasicCMIRP is used for querying,
modifying, adding, or removing network resource objects. If the function of configuration
management through the interface of northband network management is not enabled, disable
the BasicCMIRP.
Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, and KernelCMIRP.
AlarmIRP
AlarmIRP is used for managing fault data. If the function of fault data management through the
interface of northbound network management is not required, disable the AlarmIRP.
Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, KernelCMIRP, and BasicCMIRP.
Required Services
The required service is the LicenseService.
8.1.28 itm_agent Process
This section describes the ItmService service and the dependent services by the itm_agent
process.
The itm_agent process provides the ItmService service.
The ItmService service provides the function of integrated task management.
Required services: LicenseService
8.1.29 lic_agent Process
This chapter describes the services and functions provided by the process lic_agent.
The lic_agent process provides the LicenseService service.
LicenseService provides a service interface to validate the license of the current version.
Ensure that this service works properly during the M2000 operation.
8.1.30 log_agent Process
This section describes the services and functions provided by the log_agent process.
The log_agent process provides LogService and ForwardingService.
M2000
127
LogService records system-related operations in logs, and provides operation logs for other
services or clients to query. By using LogService, you can also set and query the parameters for
dumping system logs.
ForwardingService forwards the M2000 system logs to a third-party Syslog server according to
standard protocols.
Required services: None.
8.1.31 maintain_agent Process
This topic describes the function of the MaintenanceService service, which is provided by the
maintain_agent process.
The maintain_agent process provides the MaintenanceService service.
The MaintenanceService service enables the periodic backup of the important system
configuration files, database data, and real-time data of MOs.
During the M2000 operation, ensure that the maintain_agent process is operational.
8.1.32 manager_agent Process
This section describes the services and functions provided by the manager_agent process.
The manager_agent process provides the SystemService service.
SystemService enables you to query the M2000 version information such as the version of the
operating system, software version of the client, software version of the server, client software
version matching the server software, and client upgrade information.
8.1.33 medXXXX_agent Process
This section describes the services and functions provided by the medXXXX_agent process.
The medXXXX_agent process provides the MediationServiceXXXX service.
The medXXXX_agent is a multi-instance process, and XXXX refers to the instance number.
When the M2000 is running, the system dynamically generates new processes and services based
on NE types and NE quantity. Some typical process names are med0101_agent, med0102_agent,
and med0103_agent, and the names of the corresponding services are MediationService0101,
MediationService0102, and MediationService0103.
The MediationServiceXXXX service creates, deletes, and obtains the NE engines mirrored to the
network devices from the M2000 system and also manages the related event interceptors. NEs
of different types communicate with the M2000 system by using the corresponding NE engines
through various network management protocols. In addition, the MediationServiceXXXX service
can export performance result files on the basis of NEs.
Dependent services: none
M2000
128
8.1.34 ncc0X01_agent Process
This section describes the services and functions provided by the ncc0X01_agent process.
The ncc0X01_agent process provides the NCCService0X01 service.
ncc0X01_agent is a multi-instance process, where 0X01 is the instance number. Generally, the
process is named ncc0101_agent and the related service is named NCCService0101.
NCCService0X01 forwards NE data and controls NE connections.
In the ATAE cluster system system, this process can be deployed on the master server and the
slave servers. The process names are ncc0101_agent, ncc0201_agent, ncc0301_agent and so on.
Independent service: none.
8.1.35 necomm_agent Process
This section describes the services and functions provided by the necomm_agent process.
The necomm_agent process provides the CommonLicService service and SSLManageService
service.
The CommonLicService service manages the information about NE license files, such as
invalidity, export, and adjustment information.
The SSLManageService service manages the SSL connections between the M2000 and NEs. It
also manages the SSL certificates used by the SSL connections.
The SSLManageService service depends on CommonLicService service.
8.1.36 nelicense_agent Process
This section describes the services and functions provided by the nelicense_agent process.
The nelicense_agent process provides the NeLicenseService service.
The NeLicenseService service manages NodeB licenses and implements the sharing of a license
between the NEs of the same type.
Required services: LogService.
8.1.37 neuser_agent Process
This section describes the NeUserService service. NeUserService is provided by the
neuser_agent process.
The neuser_agent process provides the NeUserService service.
The NeUserService service enables you to manage NE users. When the M2000 and NEs are
connected properly, you can manage NE users through the M2000. For example, you can
authenticate the login of NE users, deliver command rights and command group rights, and
customize command groups.
M2000
129
8.1.38 ngnffs_agent Process
This section describes the NGNFullFillService service and dependent services.
The ngnffs_agent process provides the NGNFullFillService.
The NGNFullFillService service provides functions of managing management domains and
provisioning subscriber numbers.
8.1.39 ngnni112_agent Process
This section describes the services and functions provided by the ngnni112_agent process.
The ngnni112_agent process provides the NGNNI112Service service.
The NGNNI112Service provides the NBI for the subscriber line test system.
Required services: NGNTestManageService.
8.1.40 ngnnis_agent Process
This section describes the NGNNIService service and dependent services.
The ngnnis_agent process provides the NGNNIService.
The NGNNIService service provides functions of the northbound interface operation
management.
8.1.41 ngntestmanage_agent Process
This section describes the services and functions provided by the ngntestmanage_agent process.
The ngntestmanage_agent process provides the NGNTestManageService service.
The NGNTestManageService provides the fix access network test management function.
8.1.42 nhcservice_agent Process
This section describes the services and functions provided by the nhcservice_agent process.
The nhcservice_agent process provides the NHCService service.
The NHCService service provides the NE health check function.
If you plan to perform a heath check task, you must ensure this service is running properly.
Required service: ItmService and EAMService.
8.1.43 nicservice_agent Process
This section describes the services and functions provided by the nicservice_agent process.
The nicservice_agent process provides the NICService service.
M2000
130
The NICService service provides the network information collecting function. The
nicservice_agent process is available only after you have installed the network information
collecting components.
If you plan to perform a network information collecting task, you must ensure this service is
running properly.
Required service: ItmService and EAMService.
8.1.44 nimserver_agent Process
This section describes the NIMServer service and the dependent service. NIMServer is provided
by the nimserver_agent process.
The nimserver_agent process provides the NIMServer service.
The NIMServer service only enables you to centralize the real-time monitoring of alarms,
performance, and configuration status of some WRAN configuration objects. It also only
provides the functions to some WRAN configuration objectssuch as alarm statistics, query of
basic configuration information, query of configuration link constitution and basic configuration
information, and query of adjacent cells and channel assignment.
8.1.45 nms_mml_agent Process
This section describes the services and functions provided by the process nms_mml_agent.
The nms_mml_agent process provides the NMSMMLServer service. That is, the NMS issues
MML commands through the northbound MML transmission interface to managed NEs.
If the northbound MML transmission interface is used when the M2000 is running, ensure that
the NMSMMLServer is running correctly. When the northbound MML transmission interface
is not used, the NMSMMLServer is not disruptive to other services.
Required services: LogService.
8.1.46 partition_agent Process
This section describes the services and functions provided by the partition_agent process.
The partition_agent process provides the PartitionService service.
The PartitionService service divides managed objects into various partitions. Each partition is
managed by its own process. In the presence of a large quantity of objects, the partitions are
managed by various processes on different servers to balance the load.
8.1.47 pm_agent Process
This section describes the services and functions provided by the process pm_agent.
The pm_agent process provides the PMService service.
M2000
131
PMService monitors performance management on all NEs. The performance management is
independent of NEs or objects. Stop PMService if the performance management function is not
required.
8.1.48 pmengine0X01_agent Process
This section describes the services and functions provided by the pmengine0X01_agent process.
The pmengine0X01_agent process provides the PMEngine0X01 service.
The pmengine0X01_agent process a multi-instance process. 0X01 indicates the number of a
process instance. The corresponding service of the pmengine0101_agent process is
PMEngine0101.
This service provides the functions of querying performance results, diagnosing missing results,
and importing neighboring cell data in the ATAE cluster system system.
In the ATAE cluster system system, you can deploy this process on the master node and different
slave nodes. The typical process names are pmengine0101_agent, pmengine0201_agent,
pmengine0301_agent, and so on.
Required services: PMService
8.1.49 pmexp_agent Process
This section describes the services and functions provided by the process pmexp_agent.
The pmexp_agent process provides the PMExport service.
PMExport exports performance data of a measurement unit from the database. PMExport is
independent of NEs or managed objects.
Stop PMExport when the function of exporting performance results is not required.
8.1.50 pmmon_agent Process
This section describes the services and functions provided by the process pmmon_agent.
The pmmon_agent process provides the PMMonService service.
PMMonService monitors key NE counters and displays the value about these counters in figures
and tables.
Required services: PMService
8.1.51 porttrunk_agent Process
This section describes the services and functions provided by the porttrunk_agent process.
The porttrunk_agent process provides the PortTrunkingService service.
The PortTrunkingService provides the network proxy function.
M2000
132
Through the network proxy function, some tools that cannot connect to NEs can access NEs.
You do not need to configure multiple ports on the firewall for communication.
Configure the ACL for the PortTrunkingService service to restrict the NEs that can be accessed.
8.1.52 proxy_agent Process
This section describes the services and functions provided by the proxy_agent process.
The proxy_agent process provides the Proxyserver service.
Proxyserver enables the M2000 client to connect to NEs through the proxy server and to run
applications of the NEs on the LMT .
Stop Proxyserver when the proxy function is not required.
8.1.53 PRSAssistantService_agent Process
This section describes the services and functions provided by the PRSAssistantService_agent
process.
The PRSAssistantService_agent process provides the PRSAssistantService service.
The PRSAssistantService service provides the function of generating reports in .html, .csv or .xls
format. It also provides the function of transferring result files by email or through the FTP.
After restarting the PRSAssistantService service, you need to restart the PRSReportService
service.
If you need to run the PRS module, the PRSReportService service cannot be stopped.
8.1.54 prsdc_agent Process
This section describes the services and functions provided by the prsdc_agent process.
The prsdc_agent process provides the PRSDcService service.
The PRSDcService service provides the function of obtaining configuration data files and
performance data files on schedule.
Keep the service running during the operation of the PRS module.
8.1.55 prsfs_agent Process
This section describes the services and functions provided by the prsfs_agent process.
The prsfs_agent process provides the PRSFsService service. That is, it provides the service for
importing report data.
The PRSFsService service provides the function of parsing configuration data files and
performance data files on schedule.
M2000
133
Keep the service running during the operation of the PRS module.
Required service: LicenseService.
8.1.56 prsreport_agent Process
This section describes the services and functions provided by the prsreport_agent process.
The prsreport_agent process provides the PRSReportService service.
The PRSReportService service provides the function of querying the reports of the PRS module.
If you need to run the PRS module, the PRSReportService service cannot be stopped.
Required services: LicenseService and ItmService.
8.1.57 prssum_agent Process
This section describes the services and functions provided by the prssum_agent process.
The prssum_agent process provides the PRSSumService service.
The PRSSumService service provides the function of summarizing the data of the PRS
(Performance Report Suite) module. It is responsible for retrieving data in a specified order and
scheduling the data.
If you need to run the PRS module, the PRSSumService service cannot be stopped.
8.1.58 rn_agent Process
This section describes the services and functions provided by the rn_agent process.
The rn_agent process provides the RNService service.
The RNService service provides the user with the function of sending notifications by email or
short message.
8.1.59 ScriptModuleService_agent Process
This section describes the services and functions provided by the ScriptModuleService_agent
process.
The ScriptModuleService_agent process provides the ScriptModuleService service.
The ScriptModuleService service provides the function of managing applications.
Required services: ItmService
8.1.60 scriptserver_agent Process
This section describes the services and functions provided by the process scriptserver_agent.
The scriptserver_agent process provides the ScriptService service.
ScriptService provide script timing and NEs access from script.
M2000
134
Required services: ItmService and SecurityService.
8.1.61 sm_agent Process
This section describes the services and functions provided by the process sm_agent.
The sm_agent process provides the SecurityService service.
SecurityService controls the access of all sensitive resources in the M2000. Only authorized
users can gain access to sensitive resources.
Required services: EAMService and LicenseService
8.1.62 snm_agent Process
This section describes the SNMService service and dependent services.
The snm_agent process provides the SNMService.
The SNMService service provides signaling network management, including topology
management, port monitoring, and resource management.
Required services: TopoService and EAMService.
8.1.63 snmp_agent Process
This section describes the SnmpAgent service and the dependent services. The SnmpAgent
service is provided by the snmp_agent process.
The snmp_agent process provides the SnmpAgent service, that is, the northbound interface
service complying with the SNMP protocol.
The SnmpAgent service enables the upper-level NMS to obtain the information on the M2000
such as alarm data, through the SNMP protocol.
Required services: LogService and LicenseService.
8.1.64 sso_agent Process
This section describes the services and functions provided by the sso_agent process.
The sso_agent process provides SSO service.
SSO service provides the function of centralized account management and authorization.
8.1.65 swm_agent Process
This section describes the services and functions provided by the swm_agent process.
The swm_agent process provides the SWMService service.
The SWMService manages the versions, configuration data, NE logs, and other files of some
NEs. It also provides the download, upload, activation, and rollback functions.
M2000
135
8.1.66 SyslogCollectorDM Process
This section describes the services and functions provided by the SyslogCollectorDM process.
The SyslogCollectorDM process provides the SyslogCollectorDM service.
The SyslogCollectorDM service provides data collection and file management functions for NE
running logs.
8.1.67 threshold_agent Process
This topic describes the function of the ThresholdService service provided by the
threshold_agent process and the service that the threshold_agent process depends on.
The threshold_agent process provides the ThresholdService service.
The ThresholdService service provides the threshold management function. For example, this
service allows you to add, generate, and change a threshold. In addition, this service can generate
threshold alarms.
During the M2000 operation, ensure that the threshold_agent process is operational.
Required services: PMService.
8.1.68 trapdispatcher Process
This section describes the services and functions provided by the trapdispatcher process.
The trapdispatcher process provides the trapdispatcher service.
The trapdispatcher service controls the forwarding of the Snmp Trap messages that are reported
by NEs monitored by the M2000. The trapdispatcher service forwards the Snmp Trap messages
that are reported to port 162 by each NE to the Mediation service of each NE.
When the M2000 is running, ensure that the trapdispatcher process works properly.
Required services: PartitionService
8.1.69 uap_agent Process
This section describes the services and functions provided by the uap_agent process.
The uap_agent process provides the UAPService service.
The UAPService service provides the Sock5 agent function on the M2000 server. Thus, when
users cannot access the BAM server (make sure that the M2000 server normally connects to the
BAM), the M2000 client can be started through the agent. The uap_agent process also provides
the function of authenticating user operations to meet the requirement of authority and domain
based management on the M2000.
M2000
136
8.1.70 xftpXX01_agent Process
This section describes the services and functions provided by the xftpXX01_agent process.
The xftpXX01_agent process provides the XFTPServiceXX01 service. Through the
XFTPServiceXX01 service, the M2000 actively uploads exported files through the northbound
interface to the FTP server on the NMS side.
You can upload the files exported through the northbound interface to the FTP server on the
NMS side using the XFTPServiceXX01 service.
The XFTPServiceXX01 service can export various types of files, for example:
l NBI FM
l NBI CM
l NBI Inventory
l NBI PM
l CME NBI
l License Management
l NBI server backup
l NBI log
Through the M2000 client, you can set the FTP server on the NMS side.
When the M2000 is running, ensure that the xftpXX01_agent process works properly.
8.1.71 xmlagent Process
This section describes the services and functions provided by the xmlagent process.
The xmlagent process provides the XMLAgent service.
The XMLAgent service provides the northbound interface that is based on the Simple Object
Access Protocol (SOAP).
8.1.72 Trace Server Services and Processes
The section describes the function of Trace Server services and processes
Each Trace Server process maps a Trace Server service. Table 8-1 describes Trace Server
services and processes.
Table 8-1 Trace Server services and processes
Service
Name
Process
Name
Platform Description
Monitor Monitor HP Monitors the Trace Server software.
The Monitor service must be started.
Dependent service: None.
M2000
137
Service
Name
Process
Name
Platform Description
TS.Subscr
iber
TS.Subscr
iber
HP Subscribes to signaling and periodically deletes
subscribed files.
The TS.Subscriber service runs on a separate
process. In addition, the service is started
automatically by scripts and does not need to be
started manually.
Dependent service: Monitor.
TS.Collec
tor
TS.Collec
tor
HP Collects and filters data and events.
The TS.Collector service runs on a separate
process. In addition, the service is started
automatically by scripts and does not need to be
started manually.
EBCStatis
tic
EBCStatis
tic
HP Calculates counters based on events for the Long
Term Evolution (LTE) network.
This service runs on an independent process and
starts automatically by scripts.
TSService ts_agent ATAE Collects LTE tracing data and filters events.
The TSService service runs on a separate process.
In addition, the service is started automatically by
scripts and does not need to be started manually.
In the ATAE cluster system, this process is
deployed on the Trace Server slave node.
EBCStatis
tic
ebc_agent ATAE Calculates counters based on events for the Long
Term Evolution (LTE) network.
This service runs on an independent process and
starts automatically by scripts.

8.1.73 Processes and Services Related to Each Northbound Interface
This section describes the processes and services related to each northbound interface.
Table 8-2 describes the relations between northbound interfaces and their corresponding
processes and services.
M2000
138
Table 8-2 Relations between northbound interfaces and their corresponding processes and
services
Process Service Northbound Interface
irp_agent IRPService l CORBA configuration
interface
l CORBA alarm interface
l CORBA security interface
l CORBA performance
interface
ifms_agent FaultService Northbound alarm file
interface
pmexp_agent PMExport Northbound performance file
interface (measurement unit-
based)
medXXXX_agent MediationServiceXXXX Northbound performance file
interface (NE-based)
snmp_agent SnmpAgent Northbound SNMP interface
fmnotify_agent FMNotify Northbound alarm streaming
interface
nms_mml_agent NMSMMLServer Northbound MML interface
cmserver_agent CMServer Northbound inventory file
interface
cmexp_agent CMExport l Northbound configuration
file interface
l Database interface

8.1.74 Processes Used by RTN, Router, Switch, Firewall, and SVN
This section describes the processes used by NEs such as radio transmission node (RTN), router,
switch, firewall, and SSL VPN (SVN).
Table 8-3 lists these processes used by NEs such as RTN, router, switch, firewall, and SVN.
The processes listed in Table 8-3 are available only after the related NE components are installed.
Table 8-3 Processes used by RTN, router, switch, firewall, and SVN
Process Name
Dependent
processes
Description
dam None
This process provides the function of creating
SNMP equipment.
M2000
139
Process Name
Dependent
processes
Description
datacollectorsvr None
This process is mainly used for collecting the
complete and correct fault data in case of NE
failure and helps to locate faults quickly
DCServer None
This process provides the function of NE
software management and disaster recovery
management. The detailed functions are NE
software upgrade, patch installation, data
backup and recovery for disaster recovery, and
plug-andplay automatic upgrade of case-shaped
equipment.
Eml_PerfSvr None
This process provides the transfer-domain
performance management function.
Eml_PubSvr None
This process provides the function of inter-NE
management on transferdomain NEs and
reports.
InventoryDM
eam_agent and
ifms_agent
This process provides the inventory data
management function, such as physical resource
management, cable management, and customer
management.
mc None
This process provides the basic NE distribution
service.
nemgr_ptn None
This process provides the function of managing
Metro Ethernet PTN frame-shaped and
caseshaped NEs.
nemgr_rtn None
RTN series equipment.
neproxy None Data Collector NE Proxy Process.
PMDataSynchron
izer
None
This process provides the function of importing
data in text files.
PMSDm None
This process provides the collector management
function.
PQMDm None
This process provides the function of grouping
performance monitoring and display.
RouterMgrDm None
Quidway routers.
SecurityMgrDm None
FW/USG, SIG, and SVN series security
equipment.
toolkit None
This process provides the service of upgrading
boardlevel transmission equipment.
M2000
140
Process Name
Dependent
processes
Description
TXTNBIDm None
This process provides the NBI function. It is
used to transmit performance data in the text
format through FTP.
UFlight_Dis-
patcher
Apache Dispatcher the web request of UFlight.
UniteUitlDM None
This process provides the basic functions, such
as importing and exporting scripts, managing
NE time, synchronizing NEs, and managing NE
objects, of the inter-domain universal NMS.

8.2 Viewing the Running Status of M2000 Services (SUSE)
This describes how to view the status of M2000 services on the M2000 server. This operation
requires only few system resources and does not affect system performance.
Procedure
Step 1 Log in to the M2000 server as user ossuser.
If the current user is not user ossuser, you can run the following command to switch to user
ossuser:
~> su - ossuser
Step 2 Run the following commands:
~> cd /opt/oss/server
~> . ./svc_profile.sh
~> svc_adm -cmd status
Host: 10.141.147.234
Service Agent: 3rdTool_agent [1 service(s)] pid: 8773
3rdToolService [running ]
Service Agent: DrlDm [1 service(s)] pid: 8725
DrlDm [running ]
Service Agent: ScriptModuleService_agent [1 service(s)] pid: 11173
ScriptModuleService [running ]
...
[All Services: 51 ] [Running : 51 ] [Not Running : 0 ]
Normally, the following information is displayed at the end of the system output:
[Running : 51 ] [Not Running : 0 ]
l If the value of Not Running : is 0, all the M2000 services are running.
l If the value of Running : is 0, all the M2000 services are stopped.
M2000
141
NOTE
The M2000 system generates processes and services dynamically during the operation. Accordingly, the
number of processes and services changes dynamically.
Step 3 (Optional) If the user was switched to user ossuser in the first step, run the following command
to exit user ossuser:
~> exit
----End
8.3 Starting the M2000 Services (SUSE)
After you run the start_svc command, all the M2000 services are started. If an M2000 service
is already started, the system does not handle the service. Actually, the system starts only the
inactive services.
Procedure
Step 1 log in to the server as user ossuser.
ossuser:
~> su - ossuser
Step 2 Run the following commands:
~> start_svc
NOTE
l Before starting the M2000 server, ensure that the Oracle is started.
l The time required for starting M2000 services is related to the actual environment. Generally, starting
services takes 15 to 20 minutes.
~> exit
----End
8.4 Stopping the M2000 Services (SUSE)
This describes how to stop the M2000 services. After the M2000 services are stopped, the
M2000 processes are stopped. In this situation, NE performance data and alarm data cannot be
processed. After the services are resumed, the M2000 updates the data with the NEs and
processes the data.
M2000
142
Procedure
Step 1 log in to the server as user ossuser.
ossuser:
~> su - ossuser
Step 2 Run the following commands to stop the M2000 services:
~> stop_svc
NOTE
The time required for stopping M2000 services is related to the actual environment. Generally, stopping
services takes 2 minutes.
Step 3 Run the following command to check whether there is any output. If no system output is
displayed, you can infer that M2000 services are stopped.
~> svc_ps
Step 4 If some services are still running, run the following command to forcibly stop them:
~> kill_svc
Step 5 Run the following command to stop the M2000 daemon:
~> stop_daem
Step 6 Run the following command to check whether there is any output. If no system output is
displayed, you can infer that the M2000 daemon is stopped.
~> daem_ps
Step 7 If the daemon process is still running, run the following command to forcibly stop it:
~> kill_daem
~> exit
----End
M2000
143
9 Managing M2000 Database
About This Chapter
This section describes how to manage the M2000 database. This first describes the concepts of
the M2000 database including database type and status. Then describes how to view the database
status, start or stop the database, and check the database space.
9.1 Introduction to the M2000 Database (Oracle)
The M2000 databases consist of the Oracle system database and the M2000 server database.
This chapter describes only the M2000 server database. On the basis of the Oracle database, the
M2000 creates the OSSDB database. After installing the M2000 server application software,
the size of the M2000 database is fixed. You can use the oracle commands to perform operations
for the database.
9.2 Checking Oracle Services
This section describes how to check the status of the database services before installing the
M2000 to ensure that the database services are running properly.
9.3 Starting Oracle Service
This section describes how to start the Oracle service.
9.4 Stopping Oracle Service
This section describes how to stop the Oracle service.
9.5 Checking Database Space
This section describes how to use Oracle commands to view the database status, overall size of
data files, and size of remaining space. This operation requires few system resources and does
not affect system operation.
M2000
Administrator Guide (x3850&x3650, SUSE10) 9 Managing M2000 Database
144
9.1 Introduction to the M2000 Database (Oracle)
The M2000 databases consist of the Oracle system database and the M2000 server database.
This chapter describes only the M2000 server database. On the basis of the Oracle database, the
M2000 creates the OSSDB database. After installing the M2000 server application software,
the size of the M2000 database is fixed. You can use the oracle commands to perform operations
for the database.
9.1.1 cmedb
The cmedb is used to store the NE configuration data on the CME, including the configuration
data in the current and planned data areas.
The cmedb requires at least 8 GB data space.
Table 9-1 lists the names and functions of the tables in the cmedb.
Table 9-1 Names and functions of tables in the cmedb database
Table Name Function
Table with the t_c_ prefix Stores NE data in the current data area.
Table with the t_p_ prefix Stores NE data in the planned data area.
Table with the t_ prefix Supports table of the tool type to store NE data.
Other tables Records internal data on the CME.

9.1.2 eamdb
The eamdb is used to store the data of network management objects, such as NEs, subnets, and
links. The eamdb database must exist in the M2000 system.
The eamdb requires at least 2 GB disk space.
Table 9-2 lists the name and function of each table in the eamdb.
Table 9-2 Names and functions of tables in the eamdb database
Table Name Function
tbl_sn Subnet information table.
tbl_ne NE information table.
tbl_nefeature NE feature table.
tbl_link Link information table.
tbl_idresource NMS object identification management table.
M2000
145
Table Name Function
tbl_sntype Subnet type table.
tbl_netype NE type table.
tbl_linktype Link type table.
tbl_sync Data synchronization table.
tbl_nerelation NE relationship table.
tbl_maintenanceinfo Maintenance personnel information table.
tbl_locationinfo Device maintenance information table.
tbl_negroup NE group information table.
tbl_negroupclass NE group mode table.
tbl_negroup2ne NE group and NE relationship table.
tbl_negrouptype NE group type table.
tbl_devsnmppara SNMP device parameter table.
tbl_dftsnmppara Default SNMP parameter table.
tbl_autodiscfilter Auto-search IP filter table.
tbl_autodischistory Auto-search history record table.
tbl_eamschedule Scheduled-search parameter table.
tbl_autodiscresult Auto-search result table.
tbl_SubareaInfo partition information table recording the node information.
tbl_SubareaRes partition resource table recording the resource information of
each node.
Other tables Record the internal processing data.

9.1.3 farsdb
The farsdb is used to store the signaling message data of all the NEs managed by the M2000.
The farsdb requires at least 12 GB space.
The farsdb consists of the following types of tables:
l Static configuration data table
l Task table
l Task data table
Table 9-3 lists the name and function of each table in the farsdb.
M2000
146
Table 9-3 Names and functions of tables in the farsdb database
Table Name Function
tbl_ProcessorInfo Static service configuration table.
tbl_Field Static field configuration table.
tbl_TaskInfo Dynamic task record table.
tbl_TaskNE Table recording the tasks reported to NEs.
Message type name_task
ID
Dynamically created task data table, which records the signaling
data of the message type corresponding to a task.

9.1.4 fmdb
The fmdb is used to store the alarm logs and event logs of the M2000 and NEs.
The fmdb requires at least 8 GB disk space.
Table 9-4 lists the names and functions of tables in the fmdb.
Table 9-4 Tables of the fmdb database and their functions
Table Name Function
tbl_alm_log Records alarm logs.
tbl_event_log Records event logs.
Other tables Record related information about the alarm
processing internal implementation.

NOTE
The system automatically divides the tbl_alm_log and tbl_event_log tables according to the size of alarms
and events. For example, the fmdb database may contain multiple alarm log tables such as tbl_alm_log_1
and tbl_alm_log_2.
9.1.5 itfndb
The itfndb is used to store the northbound configuration data, performance tasks, and
performance threshold data.
The itfndb is optional to create the M2000 database. It requires at least 3 GB disk space. Table
9-5 lists the name and function of each table in the itfndb.
Table 9-5 Names and functions of tables in the itfndb database
Table Name Function
tbl_JGeneralInfo Records the general information about tasks.
M2000
147
Table Name Function
tbl_JMoInstance Records the instances of tasks.
tbl_JStatusRecord Records the status of tasks.
tbl_JMeasurementCategory Records the measurement categories of tasks.
tbl_JSchedule Records the task scheduling.
tbl_MGeneralInfo Records the general information about thresholds.
tbl_MMoInstance Records the instances of thresholds.
tbl_MMeasurementCategory Records the measurement categories of thresholds.
tbl_MThresholdPackElemen Records the details of thresholds.
tbl_MAlarmRecord Records the alarm records of thresholds.
tbl_MStatusRecord Records the status of thresholds.
Other tables Records the information about northbound internal
implementation.

9.1.6 logdb
The logdb is used to store log management data. The logdb database must exist in the M2000
system.
The logdb requires at least 3 GB disk space.
Table 9-6 lists the names and functions of the tables in the logdb.
Table 9-6 Names and functions of tables in the logdb database
Table Name Function
tbl_Audit Records the logs of user operations.
tbl_SysLog Records the logs of system operations.
tbl_SysLogResultDef Records the result information about system logs.
tbl_SysLogStaticInfo Records the static information about system logs.
Other tables Records the information about other logs.

9.1.7 omcdb
The omcdb is used to store the M2000configuration data and related data for internal
implementation.
The omcdb requires at least 75 GB disk space.
M2000
148
Table 9-7 describes the name and function of each table in the omcdb.
Table 9-7 Names and functions of tables in the omcdb database
Table Name Function
Tables with moi_ as the
prefix
Records the information about MO instances.
Tables with mos_ver_ as
the prefix
Records the information about versions.
Tables with nbmmlNe_
as the prefix
Records the information about the format of messages transferred
between the M2000 and the NEs.
Tables with sm_ as the
prefix
Records the information about service data.
Tables with softx3000_
as the prefix
Records dual-homing relationship.
Views with
gv_view_cmcyw_ as the
prefix
Records service Database Central (DC) data.
Views with
view_cmcyw_ as the
prefix
Records basic service data.
tbl_AllNeInfo Records information about NEs.
Processes with proc_sm_
as the prefix
Records the processes of service data.
Processes with sm_ as the
prefix
Records the processes of service AMG data.
tbl_Resource Records NE resource data.
Tables with ums_ as the
prefix
Record the information about error codes.
Tables with ne_ as the
prefix
Records the information about NE models.
Tables with omc_ as the
prefix
Records the data about network management system.
Tables with rel_ as the
prefix
Records the relationship between MOs.
tbl_ADAllNeList Records the information about the NodeBs to be commissioned.
tbl_ADNeStatus Records the information about the statuses of the NodeBs to be
commissioned.
tbl_IPExg Records the IP configuration information about the NAT
translation table.
M2000
149
Table Name Function
tbl_OmcSslOption Records the SSL connection policy of the OMC for NEs.
tbl_nelicBaseInfo Records the basic information about NEs.
tbl_nelicTask Records the information about operation tasks.
tbl_nelicTaskEnv Records the information flow interacted between the M2000
server and client.
tbl_test_task_property Records the properties of the IPQoS test task.
tbl_test_local_path Records the intra-office test path.
tbl_test_other_path Records the inter-office test path.
tbl_test_log_result Records the test task logs.
tbl_test_ping_report Records the signaling parameters on the bearer network.
tbl_test_audit_result Records the audit results of calling and called parties on the bearer
network.
tbl_test_nblink_result Records the audit result of the call completion rate on the bearer
network.
tbl_test_ping_address Records information about address pairs sent by the host.
session_SessionEntity Records information about operated NEs during a session.
session_SessionMoc Records information about operated MOCs during a session.
session_SessionOpInfo Records information about user operations during a session.
Other tables Records other configuration data of the M2000.

9.1.8 osstempdb
The osstempdb is used to store the buffer data required for internal implementation of the
DesktopServiceXXXX service. The osstempdb database must exist in the M2000 system.
The osstempdb requires at least 2 GB disk space.
Table 9-8 lists the name and function of each table in the osstempdb.
Table 9-8 Names and functions of tables in the osstempdb database
Table Name Function
tbl_instance
name_subsystem
name_function name
Stores the buffer data required for internal implementation of the
DesktopServiceXXXX service.

M2000
150
9.1.9 pmcomdb
The pmcomdb is used for storing the static performance measurement data of NEs. The
pmcomdb database must exist in the M2000 system.
The pmcomdb requires at least 5 GB disk space.
If the remaining space of the pmcomdb is insufficient, the system generates an alarm.
The pmcomdb consists of the following types of tables:
l Counter tables
l Template Information Tables
l Function Subsets and Period Tables
l Other tables
Counter tables
The counter tables contain multiple tables to save stable information. Table 9-9 lists the name
and function of each table in the pmcomdb.
Table 9-9 Counter information tables in the pmcomdb and the corresponding functions
Table Name Function
systbl_NeType Records all possible NE types that can be
managed by theM2000.
systbl_FunctionSet Records the function sets of all NEs.
systbl_FunctionSubSet Records the measurement units of all
function sets.
systbl_Counters Records all measurement counters.
systbl_Counter_Unit Records the units of all counters.
systbl_AllCounterCategory Records the service features of each
version.
systbl_ComputeCounters Records only the counters involved in
calculation.

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

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

Other Tables
Table 9-12 Other tables in the pmcomdb and their functions
Table Name Function
tbl_UscdbFePmPlugino Records the related information of FE PM
Plug-in (such as FE type names, FE interface
IDs, the status of FE installation and
uninstallation).

M2000
152
9.1.10 pmdb
The pmdb is used to store the NE performance architecture table or NE performance
measurement data. The pmdb database must exist in the M2000 system.
The pmdb requires at least 150 GB disk space.
After the storage period of the performance measurement data expires, the system deletes the
earliest data on a daily basis.
If the pmdb database is already insufficient before the preset storage period, you must reset the
storage period. Otherwise, the pmdb database cannot process any performance data. Change the
storage period before the remaining space of the pmdb is insufficient.
To calculate the storage period, perform the following steps: After the M2000 runs for half a
month, observe the used space of the pmdb and calculate the pmdb space used every day. Then
calculate the number of days that the whole pmdb database can last for, which is also the storage
period to be set.
The pmdb consists of the following types of tables:
l Template Tables
l Function Subsets and Period Tables
Template Information Tables
Template tables record measurement-related information. Table 9-13 lists the name and function
of the table.
Table 9-13 Template information tables in the pmdb and their functions
Table Name Function
tbl_SyncInfo Records the supplementary collection queues of
performance results.

Function Subsets and Period Tables
The pmdb database stores the tables of measurement results categorized by function subsets and
periods. Table 9-14 lists the name and function of the table.
Table 9-14 Function subset tables and period tables in the pmdb and the corresponding functions
Table Name Function
tbl_Result_XXX_Y XXX is the ID of the function subset and Y is the
period index ranging between 0 and 4.

9.1.11 smdb
The smdb is used to store security management data. The smdb database must exist in the
M2000 system.
M2000
153
The smdb requires at least 2 GB disk space. Table 9-15 lists the names and functions of tables
in the smdb.
Table 9-15 Names and functions of tables in the smdb database
Table Name Function
tbl_AccessViewNodeRelTable Records the relationship between the privilege
display nodes.
tbl_AccessViewNodeTable Records the privilege display nodes.
tbl_IDTable Records the reclaimed IDs.
tbl_SMAccessPolicyItem Records the privilege strategies for binding user
groups.
tbl_SMGroup Records the basic information about user groups.
tbl_SMGroupUserMap Records the binding relationship between user
groups and users.
tbl_SMLoginRec Stores the history records on user login.
tbl_SMNEUser Records the basic information about NE users.
tbl_SMPrivateGroupUserMap Records the binding relationship between private
groups and users.
tbl_SMSecurityPolicy Records the security policy.
tbl_SMUser Records the basic information about users.
tbl_SMUserHistoryRec Records history user passwords.
tbl_SMUserNEUserMap Records the binding relationship between users
and NE users.
tbl_SecurityObjectTable Records security objects.
tbl_SessionTable Records session information.
tbl_StaticTypeRelationTable Records the dependency between privileges.
tbl_StaticTypeTable Records the static security information about
security object types, privileges, and operations.
tbl_StaticTypeViewTable Records the display information about static
security information.
Other tables Records the information about internal
implementation.

9.1.12 swmdb
The swmdb is used to store the file information about the software management module and the
configuration data of NE versions. The swmdb database must exist in the M2000 system.
M2000
154
A disk of more than 12 GB is required for storage. Table 9-16 lists the names and functions of
tables in the swmdb.
Table 9-16 Names and functions of tables in the swmdb database
Table Name Function
tbl_FTPFileSet Records the files managed by the software management
module.
tbl_VersionRelation Records the information about version relationship.
tbl_NELogTable Records the NE operation logs.
Other tables Records the relationship information about internal
implementation.

9.1.13 topodb
The topodb is used to store topology management data. The topodb database must exist in the
M2000 system.
The topodb requires at least 2 GB disk space.
Table 9-17 lists the names and functions of the tables in the topodb.
Table 9-17 Tables of the topodb database and their functions
Table Name Function
TSLink Records the information on topology links.
TSNode Records the information on topology NEs.
TSView Records the information on topology views.
TSTempLoc Records the temporary table that stores the longitude and latitude
coordinates of the e-map.
TSTempPos Records the temporary table that stores the x-axis and y-axis
coordinates of common physical topology.
Other tables Records the information about internal implementation.

9.2 Checking Oracle Services
This section describes how to check the status of the database services before installing the
M2000 to ensure that the database services are running properly.
Prerequisites
You have logged in to the server as user root in SSH mode.
M2000
155
.
Procedure
Step 1 Run the following command to check whether the database service is started:
$ ps -ef |grep ora |grep -v usb-storage |grep -v hald-addon-storage |grep -v grep
If the following information is displayed, the Oracle service is not running. Starting the Oracle
database by referring to How Do I Start the Oracle Services.
oracle 17330 17196 0 Feb15 ? 00:00:00 /opt/oracle/oradb/home/bin/
ocssd.bin
oracle 17471 17336 0 Feb15 ? 00:00:00 /opt/oracle/oradb/home/bin/
diskmon.bin -d -f
If the system output contains at least the following seven processes, it indicates that the database
service and the monitor are started. If no output is displayed or only some of the following seven
processes are displayed, it indicates that the database service is not started. For details about
how to start the database, see How Do I Start the Oracle Services.
l ora_pmon_ossdb
l ora_dbw0_ossdb
l ora_lgwr_ossdb
l ora_ckpt_ossdb
l ora_smon_ossdb
l ora_arc0_ossdb
l /opt/oracle/oradb/home/bin/tnslsnr LISTENER -inherit
oracle 7742 7603 0 15:17 ? 00:00:00 /opt/oracle/oradb/home/bin/
ocssd.bin
oracle 7878 7753 0 15:17 ? 00:00:00 /opt/oracle/oradb/home/bin/
diskmon.bin -d -f
oracle 11728 1 0 15:27 ? 00:00:00 asm_pmon_+ASM
oracle 11730 1 0 15:27 ? 00:00:00 asm_vktm_+ASM
oracle 11734 1 0 15:27 ? 00:00:00 asm_diag_+ASM
oracle 11736 1 0 15:27 ? 00:00:00 asm_psp0_+ASM
oracle 11738 1 0 15:27 ? 00:00:00 asm_dia0_+ASM
oracle 11740 1 0 15:27 ? 00:00:00 asm_mman_+ASM
oracle 11742 1 0 15:27 ? 00:00:00 asm_dbw0_+ASM
oracle 11744 1 0 15:27 ? 00:00:00 asm_lgwr_+ASM
oracle 11746 1 0 15:27 ? 00:00:00 asm_ckpt_+ASM
oracle 11748 1 0 15:27 ? 00:00:00 asm_smon_+ASM
oracle 11750 1 0 15:27 ? 00:00:00 asm_rbal_+ASM
oracle 11752 1 0 15:27 ? 00:00:00 asm_gmon_+ASM
oracle 14178 1 0 15:40 ? 00:00:00 /opt/oracle/oradb/home/bin/tnslsnr
LISTENER -inherit
oracle 15427 1 0 15:47 ? 00:00:00 ora_pmon_ossdb
oracle 15429 1 0 15:47 ? 00:00:00 ora_vktm_ossdb
oracle 15433 1 0 15:47 ? 00:00:00 ora_diag_ossdb
oracle 15435 1 0 15:47 ? 00:00:00 ora_dbrm_ossdb
oracle 15437 1 0 15:47 ? 00:00:00 ora_psp0_ossdb
oracle 15439 1 0 15:47 ? 00:00:00 ora_dia0_ossdb
oracle 15441 1 3 15:47 ? 00:00:01 ora_mman_ossdb
oracle 15443 1 0 15:47 ? 00:00:00 ora_dbw0_ossdb
M2000
156
oracle 15464 1 0 15:47 ? 00:00:00 ora_dbwa_ossdb
oracle 15468 1 0 15:47 ? 00:00:00 ora_dbwb_ossdb
oracle 15470 1 0 15:47 ? 00:00:00 ora_dbwc_ossdb
oracle 15472 1 0 15:47 ? 00:00:00 ora_dbwd_ossdb
oracle 15474 1 0 15:47 ? 00:00:00 ora_dbwe_ossdb
oracle 15476 1 0 15:47 ? 00:00:00 ora_dbwf_ossdb
oracle 15478 1 0 15:47 ? 00:00:00 ora_dbwg_ossdb
oracle 15480 1 0 15:47 ? 00:00:00 ora_dbwh_ossdb
oracle 15482 1 0 15:47 ? 00:00:00 ora_dbwi_ossdb
oracle 15484 1 0 15:47 ? 00:00:00 ora_dbwj_ossdb
oracle 15486 1 0 15:47 ? 00:00:00 ora_lgwr_ossdb
oracle 15488 1 0 15:47 ? 00:00:00 ora_ckpt_ossdb
oracle 15490 1 0 15:47 ? 00:00:00 ora_smon_ossdb
oracle 15492 1 0 15:47 ? 00:00:00 ora_reco_ossdb
oracle 15494 1 0 15:47 ? 00:00:00 ora_rbal_ossdb
oracle 15496 1 0 15:47 ? 00:00:00 ora_asmb_ossdb
oracle 15498 1 0 15:47 ? 00:00:00 ora_mmon_ossdb
oracle 15500 1 0 15:47 ? 00:00:00 oracle+ASM_asmb_ossdb (DESCRIPTION=
(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
oracle 15502 1 0 15:47 ? 00:00:00 ora_mmnl_ossdb
oracle 15504 1 0 15:47 ? 00:00:00 ora_d000_ossdb
oracle 15506 1 0 15:47 ? 00:00:00 ora_s000_ossdb
oracle 15508 1 0 15:47 ? 00:00:00 ora_mark_ossdb
oracle 15524 1 0 15:47 ? 00:00:00 ora_o000_ossdb
oracle 15526 1 0 15:47 ? 00:00:00 oracle+ASM_o000_ossdb (DESCRIPTION=
oracle 15541 1 2 15:47 ? 00:00:00 ora_p000_ossdb
oracle 15579 1 4 15:47 ? 00:00:01 ora_arc0_ossdb
oracle 15602 1 0 15:47 ? 00:00:00 ora_fbda_ossdb
oracle 15609 1 0 15:47 ? 00:00:00 ora_qmnc_ossdb
oracle 15653 1 0 15:47 ? 00:00:00 ora_q000_ossdb
oracle 15655 1 0 15:47 ? 00:00:00 ora_q001_ossdb
----End
9.3 Starting Oracle Service
This section describes how to start the Oracle service.
M2000
157
Procedure
Step 1 Log in to the server as user root in SSH mode.
Step 2 Run the following command to switch to user oracle:
$ su - oracle
Step 3 Start the Oracle services.
1. Run the following command to start the ASM instance.
> ORACLE_SID=+ASM
SQL> startup
If the following information is displayed, the ASM instance has been started. Otherwise,
the ASM instance is not started. In this case, contact Huawei technical support.
ASM instance started
Total System Global Area 392511488 bytes
Fixed Size 2159992 bytes
Variable Size 365185672 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL> exit
2. Run the following command to start the ORACLE instance.
> . ./.bash_profile
SQL> startup
NOTE
There must be a space between the two points . . in the . ./.bash_profile.
If the following information is displayed, the ORACLE instance has been started.
Otherwise, the ORACLE instance is not started. In this case, contact Huawei technical
support.
ORACLE instance started.
Total System Global Area 2.5254E+10 bytes
Fixed Size 2183712 bytes
Variable Size 2467098080 bytes
Database Buffers 2.2750E+10 bytes
Redo Buffers 34705408 bytes
Database mounted.
Database opened.
SQL> exit
Step 4 Run the following commands to start the monitor:
> lsnrctl start
If the previous information is displayed, the monitor is successfully started.
Step 5 Run the following command to exit from user oracle:
> exit
----End
M2000
158
9.4 Stopping Oracle Service
This section describes how to stop the Oracle service.
Prerequisites
l M2000 services have been stopped. For details, see 8.4 Stopping the M2000 Services
(SUSE).
Procedure
Step 1 Log in to the server as user root in SSH mode.
Step 2 Run the following command to switch to user oracle:
$ su - oracle
Step 3 Stop the monitor.
1. Run the following command to check the status of the monitor:
> lsnrctl status
When the following information is displayed, the monitor is in running status:
Service "+ASM" has 1 instance(s).
Service "+ASM_XPT" has 1 instance(s).
Service "ossdb" has 1 instance(s).
Service "ossdbXDB" has 1 instance(s).
Service "ossdb_XPT" has 1 instance(s).
2. Run the following command to stop the monitor:
> lsnrctl stop
When the following information is displayed, the monitor is successfully stopped.
Step 4 Stop Oracle services:
1. Run the following command to stop the ORACLE instance.
If the following information is displayed, the ORACLE instance has been disabled.
Otherwise, the ORACLE instance is not stopped. In this case, contact Huawei technical
support.
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
2. Run the following command to stop the ASM instance.
> ORACLE_SID=+ASM
M2000
159
If the following information is displayed, the ASM instance has been disabled. Otherwise,
the ASM instance is not stopped. In this case, contact Huawei technical support.
ASM diskgroups dismounted
ASM instance shutdown
SQL> exit
Step 5 Run the following command to exit from user oracle:
> exit
----End
9.5 Checking Database Space
This section describes how to use Oracle commands to view the database status, overall size of
data files, and size of remaining space. This operation requires few system resources and does
not affect system operation.
Prerequisites
The database services are running properly.
Procedure
Step 1 Log in to the server as user oracle in SSH mode.
If the current user is not user oracle, you can run the following command to switch to user
oracle:
> su - oracle
Step 2 Run the following commands to view the overall size of database files:
SQL> select tablespace_name, sum(bytes)/1024/1024 Total_Size_M from dba_data_files
group by tablespace_name;
TABLESPACE_NAME TOTAL_SIZE_M
------------------------------------------------------------ ------------
LOGDB_TBS 3072
OSSTEMPDB_TBS 2048
PMCOMDB_TBS 5120
CMEDB_TBS 8192
SYSAUX 3072
UNDOTBS1 20480
EAMDB_TBS 2048
FARSDB_TBS 12288
SWMDB_TBS 12288
OMCDB_TBS 76800
SYSTEM 3072
TABLESPACE_NAME TOTAL_SIZE_M
------------------------------------------------------------ ------------
ITFNDB_TBS 3072
PMDB_TBS 153600
FMDB_TBS 8192
M2000
160
SMDB_TBS 2048
TOPODB_TBS 2048
16 rows selected.
Step 3 Run the following command to view the size of the remaining space:
SQL> select TABLESPACE_NAME, sum(bytes)/1024/1024 as free_size_M from
dba_free_space group by tablespace_name ;
TABLESPACE_NAME FREE_SIZE_M
------------------------------------------------------------ -----------
LOGDB_TBS 3071
OSSTEMPDB_TBS 2047
PMCOMDB_TBS 5119
CMEDB_TBS 8191
SYSAUX 2865.875
UNDOTBS1 20190.125
EAMDB_TBS 2047
FARSDB_TBS 12287
SWMDB_TBS 12287
OMCDB_TBS 76799
SYSTEM 2749.8125
TABLESPACE_NAME FREE_SIZE_M
------------------------------------------------------------ -----------
ITFNDB_TBS 3071
PMDB_TBS 153599
FMDB_TBS 8191
SMDB_TBS 2047
TOPODB_TBS 2047
16 rows selected.
SQL> exit
Step 4 (Optional) If the user was switched to user oracle in the first step, run the following command
to exit user oracle:
> exit
----End
M2000
161
10 Managing Disks and Hardware
About This Chapter
This section describes how to manage the disks and hardware on the M2000 server.
10.1 Viewing the CPU and Memory Usage of the M2000 Server
This describes how to view the CPU and memory usage of the M2000 server. You can view
information about the CPU usage, memory capacity, and free memory. If you find that the CPU
or memory usage is abnormal, you can log in to the server and handle the problem in time.
10.2 Viewing the Disk Usage of the M2000 Server by Running SUSE Commands
This describes how to view the disk usage of the M2000 server by running the SUSE commands.
This operation requires few system resources and does not affect the system operation.
10.3 Clearing the Disk Space of the M2000 Server (SUSE)
This section describes how to clear the disk space of the M2000 server. Before clearing the disk
space, ensure that the files to be deleted are not required for future operations. Deleting files by
mistake may lead to system operation errors.
10.4 Viewing Hardware Status on the IMM
This section describes how to view hardware status on the IMM.
M2000
Administrator Guide (x3850&x3650, SUSE10) 10 Managing Disks and Hardware
162
10.1 Viewing the CPU and Memory Usage of the M2000
Server
This describes how to view the CPU and memory usage of the M2000 server. You can view
information about the CPU usage, memory capacity, and free memory. If you find that the CPU
or memory usage is abnormal, you can log in to the server and handle the problem in time.
Prerequisites
l You are authorized with the relevant operation rights.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser
window is displayed.
Step 2 Click the Server Monitor tab. The performance of the M2000 server is displayed, as shown in
Figure 10-1.
Figure 10-1 Server Monitor

NOTE
In the CPU Usage (%) column and the Memory Usage (%) column, the green icon indicates that the CPU
usage or memory usage of the corresponding server is normal; the red icon indicates that the CPU usage
or memory usage of the corresponding server is abnormal. In the case that you have set the server monitoring
threshold for an item, the icon corresponding to the item changes from green to red when the value of the
item reaches the threshold.
Step 3 (Optional) Click Save AS to save the monitoring data in a file.
The file can be in any of the following four formats: TXT, HTML, XML, and CSV.
----End
M2000
163
10.2 Viewing the Disk Usage of the M2000 Server by
Running SUSE Commands
This describes how to view the disk usage of the M2000 server by running the SUSE commands.
This operation requires few system resources and does not affect the system operation.
Prerequisites
You have logged in to the M2000 server as user root.
Procedure
Step 1 Run the following query command:
# df -k
Step 2 View the disk usage.
Generally, the disk usage is less than 80%, which indicates that the output Use% is less than
80%.
If the disk usage is excessive, you need to clear the disk space.
----End
10.3 Clearing the Disk Space of the M2000 Server (SUSE)
This section describes how to clear the disk space of the M2000 server. Before clearing the disk
space, ensure that the files to be deleted are not required for future operations. Deleting files by
mistake may lead to system operation errors.
Context
During routine operation and maintenance, back up and delete the following files to free up disk
space:
l Files storing information about NEs and the M2000 server
l Software package and decompressed files
l Trace logs
l Backup files
CAUTION
You can delete files when the server is running. Before deleting files, run the ls -l command to
check the date when the files are generated. Do not delete the files generated on the current day.
M2000
164
Procedure
Step 1 Export the files that store information about NEs and the M2000 server and back up the files to
a hard disk.
l Files generated during automatic alarm dump
These files are stored in /opt/oss/server/var/ThresholdExport/FM.
l User logs
These files are stored in /opt/oss/server/var/userlogs.
l Core files generated by the system
These files are stored in /opt/oss/server/var/logs/.
l Historical trace files
These files are stored in /opt/oss/server/var/logs/tracebak/.
Step 2 Delete the software package and decompressed files.
After the software is successfully upgraded, you can delete the software package and
decompressed files. The upgrade package and decompressed files are stored in the folder named
after the upgrade patch in /export/home.
CAUTION
Generally, the folder is created in /export/home. Sometimes, the folder is created in /export/
home/bak.
Step 3 Delete trace logs.
Modify the value of tracebackupnum in the tracemonitor_svc_ex.xml file to reduce the
number of backup trace files.
The tracemonitor_svc_ex.xml file in /opt/oss/server/etc/conf/ specifies the trace log
monitoring period, file length, and number of backup trace files.
The content of tracemonitor_svc_ex.xml is as follows:
<?xml version="1.0" encoding="utf-8"?>
<tracemonitor name="tracemonitor" mount="/imap/common/tracemonitor">

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

<param name="tracebackupnum">50</param>
</tracemonitor>
In checktracetime, you can set the period for monitoring trace logs. In the preceding example,
the system checks the trace logs every 300 seconds. In tracebackupnum, you can set the number
of backup trace files for each process in /opt/oss/server/var/logs/tracebak. For a process, if the
number of backup trace files in the tracebak directory exceeds the preset value, the system
automatically deletes the earliest trace files.
Step 4 Clear the backup files.
l Delete the backup files for an upgrade after the upgrade completes successfully.
l Periodically delete unnecessary files from the /export/home/backup/omc database backup
directory.
M2000
165
NOTE
For details about the commands, see M2000 Command Reference.
----End
10.4 Viewing Hardware Status on the IMM
This section describes how to view hardware status on the IMM.
Prerequisites
l The server is powered on and the operating system has been started.
l The communication between the PC and the IMM is normal.
Procedure
Step 1 Open Internet Explorer, type http://IMM IP address, and press Enter. The IMM login page is
displayed. If the web browser displays certificate error or untrusted website, install certificates
for the web browser by referring to 13.3 How Do I Handle the Problem of Certificate Error
or Untrusted Website Displayed in the Web Browser (IMM)?.
Step 2 Enter the initial user name USERID, the actual password, and click Login. The page for setting
the inactive session timeout value is displayed.
Step 3 Click Continue. The IMM home page is displayed.
Step 4 In the navigation tree, choose System > Monitors > System Status.
Step 5 View the System Health Summary column in the right pane.
During operating system running, if the status shown in Figure 10-2 is displayed, the hardware
is in the normal state. Otherwise, contact Huawei technical support.
Figure 10-2 System Health Summary

Step 6 In the navigation tree, choose System > Monitors > Virtual Light Path.
Step 7 View the Virtual Light Path column in the right pane and check whether alarms occur on the
light path diagnostics panel of the server.
M2000
166
For the 3850 server, if the status of parts Heartbeat and Power in Table 10-1 is displayed, and
columns Color and Status of other parts are displayed as Not Applicable and Off, the status of
LED indicators for each part of the server is normal. Otherwise, the status of a part is abnormal.
Contact Huawei technical support.
Table 10-1 Status of certain parts (x3850)
Name Color Status
Power Green On
Heartbeat Green Blink

For the 3650 server, if the status of parts BMC Heartbeat and Power in Table 10-2 is displayed,
and columns Color and Status of other parts are displayed as Not Applicable and Off, the status
of LED indicators for each part of the server is normal. Otherwise, the status of a part is abnormal.
Contact Huawei technical support.
Table 10-2 Status of certain parts (x3650)
Name Color Status
BMC Heartbeat Green Blink
Power Green On
----End
M2000
167
11 Managing License
About This Chapter
This section describes how to query and update the license file on the M2000 server through the
M2000 client.
11.1 Querying the M2000 License
This topic describes how to query the license file on the M2000 server through the M2000 client.
11.2 Updating the M2000 License
This topic describes how to replace the M2000 license file on the M2000 server through the
client.
M2000
Administrator Guide (x3850&x3650, SUSE10) 11 Managing License
168
11.1 Querying the M2000 License
This topic describes how to query the license file on the M2000 server through the M2000 client.
Context
l When the period between the current day and Overflow Time of the License is less than
or equal to 30 days, the system displays a dialog box after a user logs in, prompting the
user to update the License. In addition, the system reminds the user of a License update
every 12 hours.
l If a user does not apply a new License after the License expires, the M2000 sends the
ALM-297 The OSS License Expired indicating that the License has expired. In addition,
the client periodically displays an expiration notification dialog box. Table 11-1 describes
the frequency of displaying the expiration notification dialog box on the client.
Table 11-1 Frequency of displaying the License expiration notification dialog box
Duration After Expiration Frequency of Display
Less than or equal to 30 days Once every 6 minutes
More than 30 days and less than or equal to 60
days
Once every 3 minutes
More than 60 days Once every 1.5 minutes

Procedure
Step 1 Choose License > OSS License Management > License Information.
Step 2 In the License Information dialog box, query the license information about resources and
functions on the Resource Control Item and Function Control Item tabs.
----End
11.2 Updating the M2000 License
This topic describes how to replace the M2000 license file on the M2000 server through the
client.
Context
l The version of the license that you applied for must be the same as the version of the
M2000.
l Before the licenses expire, the M2000 displays a warning periodically.
Procedure
Step 1 Choose License > OSS License Management > License Information.
M2000
169
Step 2 In the License Information dialog box, click Update License.
Step 3 In the Open dialog box, select the new license file(*.dat or *.txt license file), and then click
Open.
Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then click
OK.
----End
M2000
170
12 Backing Up and Restoring the M2000
System (SUSE)
About This Chapter
This section describes how to back up and restore the M2000 system.
12.1 Introduction to the M2000 Backup and Restore Solution (SUSE)
M2000 system data backup is the process of storing data on the M2000 server to a storage
medium when the M2000 system is running properly. M2000 system data restoration is the
process of rolling back the M2000 system to a normal historical running state using backup data
when the M2000 system cannot run properly due to data damage.
12.2 Backing Up and Restoring the M2000 Dynamic Data (SUSE)
This section describes how to back up and restore M2000 dynamic data.
M2000
Administrator Guide (x3850&x3650, SUSE10) 12 Backing Up and Restoring the M2000 System (SUSE)
171
12.1 Introduction to the M2000 Backup and Restore Solution
(SUSE)
M2000 system data backup is the process of storing data on the M2000 server to a storage
medium when the M2000 system is running properly. M2000 system data restoration is the
process of rolling back the M2000 system to a normal historical running state using backup data
when the M2000 system cannot run properly due to data damage.
IBM PC servers support only dynamic data backup. Dynamic data refers to the data about
M2000 dynamic services.
Dynamic Data Backup
Table 12-1 describes the backup contents, backup modes, and storage media in dynamic data
backup.
Table 12-1 Introduction to dynamic data backup
Item Content
Backup
contents
l Database OSSDB
l The M2000 system files:
Files in the /export/home/omc/var and /export/home/sysm
directories.
Files in the /opt/oss, opt/OSSENGR, and opt/OSSJRE directories.
Files in the /opt/oracle/oradb/home/dbs/orapwossdb directory.
Backup
mode
Periodic
backup
Performs a full backup at a specified time every 7 days. After
periodic backup is activated, the dynamic data is backed up
once every day. When a new periodic backup is performed, all
the backup files in the backup directory are deleted
automatically.
Manual
backup
Full backup: backs up all the dynamic data. When a new full
backup is performed, all the backup files in the backup
directory are deleted automatically.
Incremental backup: Currently, the Oracle database does not
support incremental backup. Therefore, do not perform
operations related to incremental backup.
Storage
device
Hard disk
Save path of
backup files
/export/home/backup/omc

After the backup is performed, the backup contents are automatically packaged as a backup file.
M2000
172
Rules for Naming Dynamic Data Backup Files
When backing up the dynamic data, name the backup files in the following format: all-
YYYYMMDDhhmmss.tar.
For example:
The file name all-20110601042002.tar refers to a full backup file generated on June 1, 2011 at
04:20:02.
NOTE
l The latest backup information, including the generation time and backup file name, is recorded in
the /export/home/backup/omc/backup.log file.
l During the backup, the all-YYYYMMDDhhmmss folder is generated under the /export/home/
backup/omc directory for storing backup files. When the backup is complete, the folder is
compressed into the all-YYYYMMDDhhmmss.tar file, and the all-YYYYMMDDhhmmss folder is
automatically deleted.
12.2 Backing Up and Restoring the M2000 Dynamic Data
(SUSE)
This section describes how to back up and restore M2000 dynamic data.
12.2.1 Periodically Backing Up M2000 Dynamic Data (SUSE)
This section describes how to periodically back up the M2000 dynamic data.
Prerequisites
l You have logged in to the M2000 client as a member of Administrators user group.
l A hard disk has sufficient free space if you plan to back up data on the hard disk.
Context
Generally, M2000 dynamic data is backed up periodically. The periodic backup of the dynamic
data is performed in full backup mode.
Dynamic data backup has no restriction on backup time. The backup can be performed during
the system operation. The time required for backing up M2000 dynamic data is related to the
actual environment. Generally, it takes about 2.5 hours to 3 hours to back up the dynamic data.
Do not change the storage medium on the System Backup tab page of the M2000 client.
Currently, the IBM PC server supports only hard disk.
NOTE
Do not suspend a periodic backup task. Because the latest data fails to be restored after data is lost due to
an accident such as the power-off of the server.
Procedure
Step 1 In the main window, choose Maintenance > Task Management.
The Task Management dialog box is displayed.
M2000
173
Step 2 Doubleclick Task Type > Backup > Server Backup node. The Attribute dialog box for
server periodic backup is displayed, as shown in Figure 12-1.
Figure 12-1 Periodic backup

Step 3 Click Common Parameters and set Task Name and Start Time.
Step 4 Click Extended Parameters and set the backup period, as shown in Figure 12-2.
Select a backup period from the Backup Period (days) drop-down list. The backup period can
be set to 1 to 7.
M2000
174
Figure 12-2 Periodic backup

Step 5 Click OK.
The system performs periodic backup automatically.
----End
12.2.2 Manually Backing Up M2000 Dynamic Data (SUSE)
This section describes how to manually back up the M2000 dynamic data.
Prerequisites
l You are authorized to perform relevant operations.
l A hard disk has sufficient free space if you plan to back up data on the hard disk.
Context
Manual backup is a supplement of the periodic backup and is used in special or emergency
situations such as the failure of the M2000 system.
Dynamic data backup has no restriction on backup time. The backup can be performed during
the system operation. The time required for backing up dynamic data is related to the actual
environment. Generally, it takes about 2.5 hours to 3 hours to back up the dynamic data.
Do not change the storage medium on the System Backup tab page of the M2000 client.
Currently, the IBM PC server supports only hard disk.
M2000
175
Procedure
Step 1 In the main window, choose Maintenance > Backup Management > System Backup. The
System Backup dialog box is displayed.
Figure 12-3 Manual backup

Step 2 On the System Backup dialog box shown in Figure 12-3, click Full Backup.
----End
12.2.3 Restoring the M2000 Dynamic Data (SUSE)
This section describes how to restore the M2000 dynamic data.
Prerequisites
l You have obtained the backup files for restoring the M2000 dynamic data.
l The M2000 is running properly.
Context
Based on the latest full backup files of the M2000, you can restore the M2000 system data. After
you perform the restoration operation, all the contents in the backup file package are restored.
If certain data processed after the backup start time, such as the NE performance data or alarm
data, is not packed in the backup file package, the M2000 starts the automatic synchronization
function to obtain and process the data.
l During the restoration of dynamic data, the M2000 services stop automatically and do not
process performance data or alarm data of NEs.
l After you change the IP address of the server or the password of the database user, the
dynamic data backed up before the IP address or the database user password is changed
cannot be restored.
M2000
176
Procedure
Step 1 Check the running status of M2000 services. To check the running status of M2000 services,
see 8.2 Viewing the Running Status of M2000 Services (SUSE).
If M2000 services are stopped, execute Step 2. Otherwise, stop M2000 services and then execute
Step 2. To stop M2000 services, see 8.4 Stopping the M2000 Services (SUSE).
Step 2 Restart the Oracle.
To stop the Oracle, see How Do I Stop the Oracle Services. To start the Oracle, see How Do I
Start the Oracle Services.
Step 3 Restore the M2000 data.
1. Decompress the backup file that stores the to-be-restored dynamic data.
# cd /export/home/backup/omc
# tar xf backup file that stores dynamic data
For example, if you need to restore the full backup file generated on 18:06:22 2008-01-30,
decompress the relevant package.
# tar xf all-20080130180622.tar
NOTE
You can decompress the related decompressed package to restore the backup files that stores dynamic
data.
2. Navigate to the path after the decompression.
# cd name of the backup file that stores dynamic data
For example:
# cd all-20080130180622
3. Run the following script to restore dynamic data:
# ./restore.sh
4. If the following information is displayed, type the password of database user sys.
Note: Enter q/Q to exit this tool.
Please input the super user's password of database[default:********]:
NOTE
You can type q or Q to quit the script.
5. If the following information is displayed, type 1 to start restoring dynamic data.
After the restoration is complete, the system displays Operation succeeds.
NOTE
The time required for restoring M2000 dynamic data is related to the actual environment. Generally,
it takes about 3 hours to 4 hours to restore the dynamic data. Wait with patience.
Step 4 Run the following command to restart the M2000 services:
# . /opt/oss/server/svc_profile.sh
# cd /opt/oss/server/rancn/tools/common
M2000
177
# ./commonop.sh -ostartsvc
l If the following information is displayed, the M2000 service is started.
Operation succeeds
l If the following information is displayed, the M2000 service fails to be started. In such a
case, contact M2000 for assistance.
Performing Start OSS services failed
NOTE
Starting the M2000 service takes a long time. Wait with patience.
Step 5 Run the following command to check whether all the M2000 services are started:
# . /opt/oss/server/svc_profile.sh
# svc_adm -cmd status
Check the value after Not Running : in the last line. If the value is 0, all the M2000 services
are started.
In this case, the data restoration is complete.
Step 6 Delete the backup file after the data restoration is complete.
# cd /export/home/backup/omc
# rm -rf directory for storing the decompressed backup files
For example:
# rm -rf all-20080130180622
----End
M2000
178
13 FAQ
About This Chapter
This section describes some FAQs and their solutions.
13.1 How Do I Solve the Problem That the IMM Remote Window Does Not Respond?
13.2 How Do I Set Internet Explorer on the PC?
13.3 How Do I Handle the Problem of Certificate Error or Untrusted Website Displayed in the
Web Browser (IMM)?
13.4 How Do I Set on the IMM Operation Interface to Change Two Cursors to One Cursor?
13.5 How Do I Handle the Shortage of Disk Space on the M2000 Server (SUSE)
M2000
Administrator Guide (x3850&x3650, SUSE10) 13 FAQ
179
13.1 How Do I Solve the Problem That the IMM Remote
Window Does Not Respond?
Question
What do I do if the IMM remote window does not respond when I use the IMM to manage
servers?
Answer
1. Restart the IMM. For details, see 7 in Configuring IMM Parameters.
2. Log in to the IMM again.
13.2 How Do I Set Internet Explorer on the PC?
Question
How do I set Internet Explorer on the PC?
NOTE
l The settings on Internet Explorer 8.0 are provided. The following steps can serve as a reference if you
use the Internet Explorer of another version, though the setting options may be different.
l Internet Explorer is the recommended web browser.
Answer
1. Open the Internet Explorer. Choose Tools > Internet Options to open the Internet
Options window.
2. Click Security. In the Security tab page, click Custom level to open the Security Settings
- Internet Zone dialog box.
3. In the Settings area, perform the following:
l Set the options under ActiveX controls and plug-ins as follows:
Set Automatic prompting for ActiveX controls to Enable.
Set Initialize and script ActiveX controls not marked as safe for scripting to
Prompt.
Set Download unsigned ActiveX controls to Prompt.
l Set Automatic prompting for file downloads under Downloads to Enable.
4. Click OK to save your settings.
5. Click OK to exit the Internet Options window.
M2000
180
13.3 How Do I Handle the Problem of Certificate Error or
Untrusted Website Displayed in the Web Browser (IMM)?
Question
l When Internet Explorer is used to log in to the IMM, the web browser displays an error
message similar to Figure 13-1.
l When Firefox is used to log in to the IMM, the web browser displays an error message
similar to Figure 13-2.
Figure 13-1 Certificate error message

M2000
181
Figure 13-2 Connection error message

Answer
Step 1 Log in to the PC as a user that is in the Administrators user group.
If Internet Explorer 8 runs on Windows 7, when you log in to the PC as a user that is in the
Administrators user group, you need to start Internet Explorer 8 as user administrator.
Otherwise, you cannot set Internet Explorer.
Perform the following steps to start Internet Explorer 8.0 on Windows 7 as user
administrator:
1. Choose Start > Internet Explorer.
2. In the displayed shortcut menu, choose Run as administrator.
3. In the displayed dialog box, click Yes.
Step 2 Perform operations according to the browser type.
Browser Type Operation
Internet Explorer Perform Step 3 through Step 16.
Firefox Go to Step 17.
Step 3 View the certificate.
1. When Internet Explorer displays the security certificate message shown in Figure 13-3,
click Continue to this website (not recommended).
M2000
182
Figure 13-3 Security certificate

2. Click Certificate Error, as shown in Figure 13-4.
Figure 13-4 Certificate error

3. In the displayed dialog box, click View Certificate.
Step 4 In the displayed root certificate dialog box shown in Figure 13-5, click Install Certificate.
M2000
183
Figure 13-5 Installing the root certificate

Step 5 In the displayed Certificate Import Wizard dialog box, click Next.
Step 6 As shown in Figure 13-6, select Place all certificates in the following store, click Browse,
select Trusted Root Certification Authorities, and click OK.
M2000
184
Figure 13-6 Setting the certificate store

Step 7 Click Next.
Step 8 After confirming the certificate import information, click Finish.
Step 9 When the system displays the Security Warning dialog box asking you whether to install the
certificate, click Yes. If this dialog box is not displayed, skip this step.
Step 10 In the displayed dialog box indicating that the import is successful, click OK.
Step 11 Click OK. The Certificate dialog box is closed.
Step 12 On the menu bar of Internet Explorer, choose Tools > Internet Options.
Step 13 In the displayed Internet Options dialog box, click Advanced.
Step 14 In the Settings area, clear Warn about certificate address mismatch under Security.
Step 15 Click OK. The Internet Options dialog box is closed.
Step 16 Restart Internet Explorer and log in to the IMM again.
Step 17 If the web browser displays a message shown in Figure 13-7, click Add Exception.
M2000
185
Figure 13-7 Connection error message

Step 18 In the displayed dialog box, click Confirm Security Exception.
----End
13.4 How Do I Set on the IMM Operation Interface to
Change Two Cursors to One Cursor?
Question
How do I set on the IMM operation interface to change two cursors to one cursor?
Answer
1. In the Video Viewer window, choose Tools > Single Cursor.
NOTE
Press F12 to quit single-cursor mode.
13.5 How Do I Handle the Shortage of Disk Space on the
M2000 Server (SUSE)
Question
You can use any of the following methods to check the server disk space:
M2000
186
l View the message output area at the bottom of the M2000 client. If the disk partition usage
reaches the threshold, you need to clear the disk space immediately.
l View the disk partition usage in the Hard Disk Monitoring window on the M2000 client.
l Run the df -k command to check the disk partition usage.
How do I do when the server disk space is insufficient?
Solution
l If the system notifies you of the high disk space usage of the partition where the /data
directory is located, do not delete or transfer any files. In this case, contact Huawei technical
support engineers for assistance.
l If the system notifies you of the high disk space usage of the /export/home partition, see
10.3 Clearing the Disk Space of the M2000 Server (SUSE) to troubleshoot.
l If the system notifies you of the high disk space usage of the root partition / or /opt, perform
as follows:
1. Use PuTTY to log in to the M2000 server in SSH mode as user ossuser.
2. Run the following command to switch to user root.
> su - root
Password: Password of root
3. Run the following command to collect related information:
$ du -ak / | sort -nr > /tmp/du.out
4. Transfer the du.out file from the server to the PC by using the FileZilla tool.
For details about how to use the FileZilla tool, see How Do I Use FileZilla to Transfer
Files?. The configuration information required for transferring the files is as follows:
User and password: ossuser user and its password
Directory of files on the server: /tmp
5. Send the collection results to Huawei technical support engineers.
M2000
187

M2000 Administrator Guide-3850&3650-SUSE10-V200R012 - 06

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

M2000 Administrator Guide-3850&3650-SUSE10-V200R012 - 06

Загружено:

Авторское право:

Доступные форматы

M2000

Вам также может понравиться