Professional Documents
Culture Documents
www.huawei.com
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
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
Page 3
Page 4
Type the user name and password in the corresponding fields. Type the IP address of the M2000 server.
Page 5
Information display
Status bar
Page 6
Note: Logging out off the M2000 client does not mean the applications running on the M2000 client are terminated.
Page 7
Exiting
To exit the M2000 client, choose System Exit.
Note: Exiting the M2000 client means the applications running on the M2000 client are terminated.
Page 8
Page 9
Page 10
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
Page 11
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
Page 12
Page 13
Page 14
Page 15
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
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
Page 17
Set background
Page 18
Page 19
Page 20
Monitoring NEs
Monitor the NE status.
Page 21
Page 22
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
Page 23
Page 24
Page 25
Page 26
Page 27
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.
Page 28
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
Page 29
the user performs on the M2000, including logout, login, log dumping, and device log synchronization.
System log
NE System log
Security log
such as fault management, performance management, topology management, and resource management
NE operation log
such as logging in to the LMT, modifying the NE user rights, and adding NE users
Operation log
Types of logs
NE security log
Page 30
Page 31
Querying Logs
Page 32
Logs Statistics
Page 33
Page 34
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
Page 35
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.
Page 36
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 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.
Alarm type
Page 37
Page 38
Page 39
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
Page 40
Performance Management
Measurement is a process during which the value of an attribute for an NE
> 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
Page 42
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.
Page 43
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.
Page 44
Measurement Settings
Page 45
Setting Measurement
Refences Counter
Select site
Active Counter
Page 46
Page 47
Page 48
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
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
Page 50
Upload Software
Software software browser in computer/notebook client Transfer from Client to NM Select software folder
Page 51
Upgrading NE software
Software software browser Select software in M2000 List client Transfer from NM to NE
Page 52
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
Page 53
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.
Page 54
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.
Page 55
Page 56
Page 57
Page 58