Guide M2000 Client

HSDPAHUAWEI TECHNOLOGIES CO., LTD.
All rights reserved
Developed independently by Huawei Technologies Co., Ltd, the iManager M2000 functions as EMS in the Huawei wireless network solution. The M2000 can access a whole series of products developed by Huawei and perform centralized management on them.
This slide introduces the basic operations of on the M2000 client.
HUAWEI TECHNOLOGIES CO., LTD.
Chapter 2 Network Monitoring
Chapter 3 Topology Management
Chapter 4 Security Management
Chapter 5 Log Management
Chapter 6 Fault Management
Chapter 7 Performance Management
Chapter 8 Software Management
Chapter 9 Data Management
Logging out
Logging In to the M2000
The diagram on the left lists some basic operations involved in M2000 client login.
Logging In to the M2000 Server
To log in to the M2000 server, choose Start All programs iManager M2000 client M2000 client.
Type the user name and password in the corresponding fields.
Type the IP address of the M2000 server.
IP IP M2000 IPIP M2000
M2000 30 M2000
M2000 60 M2000 M2000
M2000
Information display
Menu bar
Status bar
Tool bar
:IP
To log out off the M2000 client, choose System > Logout.
Note: Logging out off the M2000 client does not mean the applications running on the M2000 client are terminated.
M2000
To exit the M2000 client, choose System Exit.
Note: Exiting the M2000 client means the applications running on the M2000 client are terminated.
Upgrading the Software on the M2000 Client Automatically
To upgrade the software on the M2000 client automatically, perform the following steps:
Step 1: Start the M2000 client.
Step 2: Log in to the M2000 server.
After you log in to the M2000 server, the Confirmation dialog box is displayed, click Yes.
VxxxRxxxCxxBxxy[SPxx]B
Upgrading the Software on the M2000 Client Automatically
Step 3: In the displayed Update Wizard dialog box, click Continue.
Overview of the M2000 Network Monitoring
The M2000 network monitoring monitors the operational status of the M2000. For instance, the monitoring management monitors the status of hard disk, database, session, or services. The M2000 monitoring management involves the following operations:
Setting the server threshold
Monitoring the hard disk status of the server
Monitoring the database status of the server
Monitoring the database serving status
Monitoring the process status of the server
:
(%):1 10090
(:2 60 3
(%): M2000 1 100 60 70 80 90
(%): M2000 1 100
():60 3600 60

:“”“”“”“MB”“MB”“MB”“MB”“CPU ”“”
“”“”“”“”“MB”“MB”“MB”“”“”
“”“”“”“MB”“MB”“MB”“”“MB”“MB”“”
“”“”“”“”“”“”“”
“”“ID”“”“CPU ”“KB”“”“”
“”“”“”“”
M2000
Topology Management
The topology management is used for constructing and managing the topology structure of the entire network. In this way, the networking topology and the operational status of the entire network are displayed clearly.
Creating physical subnets
Creating physical NEs
To create physical subnets, perform the following steps:
Step 1: Right-click the topology view and choose Create Physical Subnet from the shortcut menu.
Set background
Create a single physical NE.
RNCMSC ServerASN-GW BSC NodeB MGW BWA BTS
NodeB RNC
BTS BSC BTS BSC BTS
IMSOMU CSCFHSSATSRMCCF DOPRA IMSOMU
Configuring the security management
Monitors OM users Sessions
Monitor the OM Users.
Monitor the operations of OM users who are now in session status.
When the M2000 server restarts or the network is disconnected and restored, click Refresh to refresh the session monitor table.
All rights reserved
Monitoring Users Sessions
Unlocking OM users.
If the times that a user enters wrong password at a time exceeds the maximum attempts, the OM user is locked for a period. Right-click the user and choose Unlock User from the shortcut menu to unlock the user.
such as fault management, performance management, topology management, and resource management
the user performs on the M2000, including logout, login, log dumping, and device log synchronization.
Such as the service start and stop, and log exporting and deletion
NE System log
Such as fault running errors, NE failures, etc NE configurations activity
such as logging in to the LMT, modifying the NE user rights, and adding NE users
record the important operations performed by the NE users,

Operations involved in the M2000 log management are as follows:
Querying logs
logs statistics
Function
The M2000 reports, manages, and analyzes NE alarms in a centralized manner. The M2000 collects NE alarms to the M2000. In addition, the M2000 notifies the maintenance personnel of device alarms by short message or email at the time when the alarm is generated.
Operations:
The following operations and analysis can be performed on NE alarms at the M2000 side.
Manual restore
Severity redefinition
Alarm relevance
In this way, the M2000 can perform centralized analysis and processing on the device alarms generated in the current network.
Event alarm
Refers to the notification generated when the system detects the events occurred.
Fault alarm
Refers to the notification generated when the system detects the faults occurred.
Alarms can be related to the following items:
Power supply system
Critical
Indicates that the device or the resource cannot be used completely and needs to be restored immediately.
Major
Indicates that the quality of the device or the resource is severely damaged. Corrective measures should be taken immediately.
Minor
Indicates that the quality of the device or the resource is slightly affected.
Warning
Indicates that the quality of the device or the resource may probably be affected.

1000
Performance Management
Measurement is a process during which the value of an attribute for an NE entity (including logical entity) in a period is acquired.
Category of performance measurement counters
System counters: a kind of a default counter defined in the NE. System counters are categorized into common counters and extended counters.
- Common counters: By default, the common counters are in the measurement state. The measurement can be cancelled.
- Extended counters: By default, the extended counters are in the non-measurement state. Before performing any measurement on extended counters, you need to activate them first. You can enable or disable the measurement on extended counters.
Custom counters: refers to the counters that are defined on the M2000 client by users. The principle for customizing counters is to perform arithmetic operations on the default counters, including common counters and extended counters, in the system. In this way, custom counters are self-defined.
M2000M2000
M2000M2000M2000 M2000 M2000 M2000

M2000 M2000
All rights reserved
Performance Measurement Periods
The measurement periods vary according to the measurement objects. The following measurement periods are available: 5 minutes, 15 minutes, 30 minutes, 60 minutes, or 24 hours. Note that the measurement whose periods are 5 minutes or 15 minutes are called real-time measurement, or short-period measurement. Only some of the NEs support the real-time measurement.
Caution:
The measurement periods for all the NEs of the same type must be same.
M2000

5 15 30 60
24
Performance Measurement Results and Counter Threshold
Performance measurement results refer to the values of measurement counters of NE measurement objects.
Performance counter threshold can be set in either of the following windows:
Threshold Management window
Performance Monitor window
If the value of a counter exceed this threshold, the threshold alarm is generated.
For the same counter, you can set alarm thresholds for various time phases, or set an alarm threshold for all time periods in each measurement period. These thresholds can be set for all objects of a measurement type, or for one or more objects.
Results of Performance Measurement Statistics
The maximum saving days for the results whose measurement period is 5 minutes or 15 minutes are 7 and represented by the parameter maxRTResultSavingDay.
The maximum saving days for the results whose measurement period is 30 minutes, 60 minutes, or 1 day are 30 and represented by the parameter maxResultSavingDay.
The M2000 checks the results whose period is 30 minutes, 60 minutes, or 1 day on a fixed time 03:25 a.m. each day. This is represented by the parameter capacityControlTime. The M2000 deletes the data saved for over 30 days.
The M2000 checks the results whose period is 5 minutes or 15 minutes on a fixed time 04:35 a.m. each day. This is represented by the parameter capacityControlTime + 70 minutes. The M2000 deletes the data saved for over 7 days.
The parameters described previously are described in the file /export/home/omc/var/etc/conf/pmsvc.xml.
Upload software
Upload Software
Software software browser Transfer from Client to NM Select software folder in computer/notebook client
All rights reserved
Upgrading NE software
Software software browser Select software in M2000 List client Transfer from NM to NE
Overview of Data Management: Backing Up NM Data
You can back up the NM data in two ways: periodic backup and manual backup.
You can back up the NM data through the full backup and the incremental backup. The following gives the difference between the full backup and the incremental backup:
Each time when a full backup is performed, the M2000 removes all the previous files related to full backup and incremental backup on the server and saves one and only the latest compressed full backup file. The file of full backup is named in the following way: all-current time, such as, all-20060106103055.tar.gz.
Each time when an incremental backup is performed, a new backup file is generated. The incremental backup is on the basis of previous backup data that can be a full backup or an incremental backup. The file of an incremental backup is named in the following way: inc-current time, such as, inc-20060106103055.tar.gz.
The NM data to be backed up refers to the data contained the following files:
/export/home/omc/var/
/export/home/sysm/
The backup files of the NM data are saved in the directory of /export/home/backup/omc/ on the M2000 server.
Overview of Data Management: Backing Up NE Data
NE data backup: The data management provided by the M2000 enables you to back up the configuration files of all NEs managed by the M2000 and the files that change dynamically during the operation.
You can back up the NE data in two ways: the periodic backup and the manual backup. The system can generate one backup file after you perform the backup task once.
The maximum number of NE backup files stored on the server is determined by the M2000 configuration file. At present, the M2000 server can store up to seven backup files for each NE. When more than seven backup files are generated for an NE, the M2000 server stores only the latest seven backup files for this NE. Meanwhile, the M2000 server refreshes the backup file list.
The backup files of NE data are saved to the path: M2000 server/export/home/sysm/ftproot/NE type. Take the RNC for example, /data type/NE FDN.

Documents

Guide M2000 Client