guide m2000 client

Security Level: Internal

Operation and Maintenance of M2000 Client

www.huawei.com

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


All rights reserved

Page 2

Chapter 1 Logging In to the M2000 Client 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


All rights reserved

Page 3

Logging In to the M2000 ClientLogging in to the M2000 server Logging out Exiting Upgrading the software on the client Automatically The diagram on the left lists some basic operations involved in M2000 client login.

Logging In to the M2000


All rights reserved

Page 4

Logging In to the M2000 ServerTo log in to the M2000 server, choose Start M2000 client. All programs iManager M2000 client

Type the user name and password in the corresponding fields. Type the IP address of the M2000 server.


All rights reserved

Page 5

Logging In to the M2000 Server|Main interface of the M2000 client|Menu bar Tool bar

Information display

Status bar


All rights reserved

Page 6

Log Out Off the M2000 ClientTo 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.


All rights reserved

Page 7

ExitingTo exit the M2000 client, choose System Exit.

Note: Exiting the M2000 client means the applications running on the M2000 client are terminated.


All rights reserved

Page 8

Upgrading the Software on the M2000 Client AutomaticallyTo 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.


All rights reserved

Page 9

Upgrading the Software on the M2000 Client AutomaticallyStep 3: In the displayed Update Wizard dialog box, click Continue.


All rights reserved

Page 10



All rights reserved

Page 11

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 performance status of the server > 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


All rights reserved

Page 12

Setting the Server ThresholdStep 1: Set the hard disk threshold.


All rights reserved

Page 13

Setting the Server ThresholdStep 2: Set the database threshold.


All rights reserved

Page 14

Monitoring the Performance Status of the Server


All rights reserved

Page 15



All rights reserved

Page 16

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 > Monitoring NEs > Printing the topology view


All rights reserved

Page 17

Creating Physical SubnetsTo create physical subnets, perform the following steps: Step 1: Right-click the topology view and choose Create Physical Subnet from the shortcut menu. Create physical subnets Create topological objects

Set background


All rights reserved

Page 18

Creating Physical SubnetsStep 2: Set the physical subnet


All rights reserved

Page 19

Creating Physical NEs Create a single physical NE.


All rights reserved

Page 20

Monitoring NEs Monitor the NE status.


All rights reserved

Page 21

Printing the topology view


All rights reserved

Page 22



All rights reserved

Page 23

M2000 Security Management The M2000 security management involves the following operations:

> Configuring the security management > Monitors OM users Sessions


All rights reserved

Page 24

Interface of Security Management


All rights reserved

Page 25

Monitoring Users SessionsMonitor 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

Page 26

Monitoring Users SessionsForce OM users to exit the M2000.


All rights reserved

Page 27

Monitoring Users SessionsUnlocking 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.


All rights reserved

Page 28



All rights reserved

Page 29

M2000 Log Management Types of logsSuch as the service start and stop, and log exporting and deletion Such as fault running errors, NE failures, etc NE configurations activity

the user performs on the M2000, including logout, login, log dumping, and device log synchronization.

System log

NE System log

record the important operations performed by the NE users,

Security logsuch as fault management, performance management, topology management, and resource management

NE operation logsuch as logging in to the LMT, modifying the NE user rights, and adding NE users

Operation log

Types of logs

NE security log


All rights reserved

Page 30

M2000 Log ManagementOperations involved in the M2000 log management are as follows:> Querying logs > logs statistics > Managing log templates


All rights reserved

Page 31

Querying Logs


All rights reserved

Page 32

Logs Statistics


All rights reserved

Page 33

Managing Log Templates


All rights reserved

Page 34



All rights reserved

Page 35

M2000 Fault Management

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 Filtering Severity redefinition Alarm relevance

In this way, the M2000 can perform centralized analysis and processing on the device alarms generated in the current network.


All rights reserved

Page 36

M2000 Fault ManagementAlarm severity

Critical Indicates that the device or the resource cannot be used completely and needs to be restored immediately.

Major

Fault Management

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

Alarms can be related to the following items: Power supply system Environment system Signaling system Hardware system Software system Operating system Service quality Fault handling Internal alarm

Indicates that the quality of the device or the resource may probably be affected.

Alarm category

Event alarmRefers to the notification generated when the system detects the events occurred.

Fault alarmRefers to the notification generated when the system detects the faults occurred.

Alarm type


All rights reserved

Page 37

Operations Involved in the M2000 Fault Management


All rights reserved

Page 38

Subscriber Informations MonitoringMonitor Signaling Trace Collection select subscriber information monitoring


All rights reserved

Page 39



All rights reserved

Page 40

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 nonmeasurement 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.HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 41

Performance Measurement PeriodsThe 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.


All rights reserved

Page 42

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.


All rights reserved

Page 43

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.


All rights reserved

Page 44

Measurement Settings

Open the Measurement Settings window.


All rights reserved

Page 45

Setting Measurement

Refences Counter

Select site

Active Counter


All rights reserved

Page 46

Query Result Measurement


All rights reserved

Page 47

Query Result Measurement


All rights reserved

Page 48



All rights reserved

Page 49

Software Management

The software management involves the following operations: > Upload software > Upgrading NE software > Querying Version Information on Software Installed on the Server


All rights reserved

Page 50

Upload SoftwareSoftware software browser in computer/notebook client Transfer from Client to NM Select software folder


All rights reserved

Page 51

Upgrading NE softwareSoftware software browser Select software in M2000 List client Transfer from NM to NE


All rights reserved

Page 52



All rights reserved

Page 53

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: inccurrent 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.


All rights reserved

Page 54

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.


All rights reserved

Page 55

Data Management ( Backup )


All rights reserved

Page 56

Data Management (restore)


All rights reserved

Page 57

Thank You www.huawei.com


All rights reserved

Page 58

guide m2000 client

Documents

m2000 client chapter

m2000 huawei technologies

m2000 monitoring management

topology management

log management chapter

software management

performance management

rights reserved page