Operation and Maintenance of M2000 Huawei

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 V2 functions as EMS in the Huawei wireless network solution. The M2000 V2 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
After learning this course, you will have a basic

knowledge of:
Basic operations on the M2000 client.
Operations related to monitoring management,

topology management, security management, log management, fault management, performance management, software management, data management, and configuration management.
All rights reserved
Page 3
Reference
iManager M2000 System Description iManager M2000 Administrator Guide iManager M2000 Commissioning Guide
All rights reserved
Page 4
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 Chapter 10 Configuration Management
All rights reserved
Page 5
Logging In to the M2000 Client

Logging in to the M2000 server Logging out Exiting Upgrading the software on the client Automatically Other operations The diagram on the left lists some basic operations involved in M2000 client login.
Logging In to the M2000
All rights reserved
Page 6
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.
Note: The initial user name is admin and the password is null. The user password is saved on the M2000 server. Only when the server is initially installed, the password is null.
All rights reserved
Page 7
Logging In to the M2000 Server

|Main interface of the M2000 client|
Menu bar Navigation tree Tool bar
Topology view
Information display
Status bar
All rights reserved
Page 8
Logging Out Off the M2000 Client

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.
All rights reserved
Page 9
Exiting
To 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 10
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.
Prerequisites: The M2000 can be automatically and correctly upgraded only when: The versions of the software on the M2000 client and on the M2000 server are of the same version sequence. The version of the software on the M2000 server is higher than that on the M2000 client.
All rights reserved
Page 11
Upgrading the Software on the M2000 Client Automatically

Step 3: In the displayed Update Wizard dialog box, click Continue.
All rights reserved
Page 12
Other Operations
System Settings Region Settings Proxy Service Setting LMT Prompt Setting Metrology Setting Broadcast Message Change Password
Display/Hide/Customize Toolbar
Lock Terminal
All rights reserved
Page 13
Region Settings
Number tab page Time tab page Date tab page Time Mode tab page
All rights reserved
Page 14
Overview of Other Common Operations

System security settings
Single-user mode: indicates the system status during the maintenance. The single-user mode allows only one user to log in to the client and set up sessions. Multi-user mode: indicates the system status when the system is functional. The multi-user mode allows several users to log in to the client at the same time.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 15

View license information
All rights reserved
Page 16

Download NE match files to the M2000 client
When the version of an NE on the M2000 client is different from that on the M2000 server, download the NE match file to the M2000 client, as shown on the right.
If the files related to the new version of the NE are not available, the system displays a message, indicating that the system cannot perform the upgrade operation.

All rights reserved
Page 18
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 19
Setting the Server Threshold

Step 1: Set the hard disk threshold.
All rights reserved
Page 20
Setting the Server Threshold

Step 2: Set the database threshold.
All rights reserved
Page 21
Monitoring the Performance Status of the Server
All rights reserved
Page 22
Monitoring the Hard Disk Status of the Server
All rights reserved
Page 23
Monitoring the Database Status of the Server
All rights reserved
Page 24
Monitoring the Database Serving Status
All rights reserved
Page 25
Monitoring the Process Status of the Server
All rights reserved
Page 26

All rights reserved
Page 27
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 Managing SNMP parameter template Monitoring NEs
Adjusting the network topology

Adjusting the display of the topology view Printing the topology view
Creating Physical Subnets

To 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 The Create Topo Object option is used to create physical NEs, virtual NEs, IP devices, virtual links, and physical links.
All rights reserved
Page 29
Creating Physical Subnets

Step 2: Set the file server.
The file server is used for the file transfer between the M2000 and the NEs. An NE is used as the file server to set up connections between the M2000 and other NEs. In this way, the problem that the M2000 cannot set up direct connection with other NEs are solved.
Creating Physical NEs

Create a single physical NE.
All rights reserved
Page 31

Create multiple physical NEs.
For instance, the Search NodeB function enables you to find the NodeBs that belong to the RNC on the topology view. Similarly, you can set Search IMSOUT to create multiple physical NEs simultaneously.
All rights reserved
Page 32

NE attributes template
The NE attributes template provides standard formats for information input when NEs are created in batches. The formats consist of INI (editable in notepad) and CSV file formats (editable in Excel). After editing the NE information, enter the NE configuration script file when you create a topological object. The .CSV file format supports the bulk creation of NEs in the WCDMA and WiMAX network.
Export NE attributes template CSCF: call session control function HSS: home subscriber server ATSgeneral telephony application server RM: resource manager CCFcall control function
Note
The .INI file format supports the bulk creation of all NEs except virtual NEs. The virtual NEs cannot be created in batches. The CSCF, HSS, ATS, RM, CCF, and DOPRA cannot be created in batches.
DOPRAdistributed object-oriented programmable realtime architecture


NE attributes template
Example of NE configuration information in .ini format
Example of NE configuration information in .csv format
Template
Monitoring NEs
Monitor the NE status.
All rights reserved
Page 35
Monitoring NEs
Set NE reconnection status.
When the M2000 server is disconnected from NEs, set the M2000 to re-connect NEs. The NE reconnection has two statuses:
Forbidden connection
When the M2000 server is disconnected from an NE, the M2000 will not attempt to connect the NE. Permitted connection
When the M2000 server is disconnected from an NE, the M2000 attempts to reconnect the NE. By default, a new NE is in permitted connection status.
Disconnection icon: Forbidden connection icon: Page 36
All rights reserved
Monitoring NEs
Reconnect NE manually.
All rights reserved
Page 37
Adjusting Network Topology/Adjusting Network Topology Display/Printing Topology View
Zoom in Zoom out Partially zoom in Restore Elements display Print View Search Save
All rights reserved
Page 38

Adjust the NE position.
All rights reserved
Page 39

View or modify the basic attributes of subnets.
All rights reserved
Page 40

Search or modify the physical links.
To search for physical links, double-click a physical link or a physical link set on the topology view. In the displayed dialog box, right-click a link and choose Link Browser.
All rights reserved
Page 41

Delete a subnet.
Delete an NE.
All rights reserved
Page 42

Customize the display of topology alarms.
All rights reserved
Page 43

Set the topology view to start the subnet.
The subnet view refers to that displayed on the client after the topology view is displayed. If you do not plan to set the topology view manually, the default view of the subnet started by the topology view is the root subnet view.
All rights reserved
Page 44

All rights reserved
Page 45
M2000 Security Management

The M2000 security management involves the following operations:
Configuring the security management Managing OM users Managing NE users
Managing OM and NE users

Setting FTPS parameters
All rights reserved
Page 46
Interface of Security Management

Set the NE types to be displayed.
Refresh the security management interface.
All rights reserved
Page 47
Managing OM Users
Add an OM user group.
All rights reserved
Page 48
Managing OM Users
Authorizing OM User Group
Three default user groups are available on the M2000 client. They are Administrators group, Guests group, and Operators group. The Administrators group has the highest privileges. You cannot modify or copy the privileges of the Administrator group. You can, however, authorize the Guests group and the Operators group. Assigning privileges to OM user group Assigning new device rights to OM user group Assigning MML command rights to OM user group
All rights reserved
Page 49
Managing OM Users
Change password Add OM users to OM user group Bind OM user private rights Assign MML command rights to OM users Synchronize OM user data
Note that each NE is assigned with the corresponding MML command rights. When a new NE is added, you need to re-assign the MML command rights for each user in the OM user group.
Page 50
All rights reserved
Managing OM Users
Set rules for NE type rights.
You can set the rules for NE type rights in a template. After setting the template, all the NEs added have the rights inherited from this template.
All rights reserved
Page 51
Managing NE Users
After the OM user is bound with a real NE, you can create at the NE side a user with the same name as the OM user. This user is called NE user. The NE user logs in to the NE through the LMT.
All rights reserved
Page 52
Monitoring OM Users and NE Users

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
Page 53

Monitor the sessions of the OM user on the LMT.
Note that this function is applicable only to NEs in the WCDMA network and supports only the LMT users.
All rights reserved
Page 54

Set the status for a non-default NE user. By setting the status, the non-default NE user's login and operation of the MML commands on the LMT can be controlled. Non-default NE users refer to the NE local users excluding the admin and guest users. The statuses of non-default NE users can be manageable and lock.
All rights reserved
Page 55

Force OM users to exit the M2000.
All rights reserved
Page 56

Force OM users to exit the LMT.
All rights reserved
Page 57

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.
All rights reserved
Page 58

Set to lock an OM user automatically.
All rights reserved
Page 59
Setting FTPS Parameters
Encryption mode: self-adaptation mode, SSL encryption mode, and plain mode. Supported mode: refers to the FTPS connection mode, mainly including active mode and passive mode. Transmission mode: refers to the mode in which the FTPS transfers files. The transmission mode can be in ASCII mode or in text mode.

All rights reserved
Page 61
M2000 Log Management

Types of logs
Records security events occurred in the system, such as logging in to the M2000, modifying rights for OM user group, or adding OM users. Records significant events occurred in the system. Records all the important operations performed by NE users
System log
Security log
Records all the important operations performed by OM users.
NE operation log
Records security events occurred to NEs.
Operation log
Types of logs
NE security log
All rights reserved
Page 62

Notes:
Log template
Saved on the server background, the contents of a template are associated with users. For instance, the templates created by user A can be seen by user A only. The names of log templates that are of the same type and belong to the same user cannot be duplicate. If the names of log templates are duplicate, the system cannot save the template. A maximum of 40 characters are allowed for the name of the template. The following characters are not allowed: `~!@#$%^&*()\":;?,|{} []<>'
Log query template
Log statistics template
The template information node does not support dynamic refresh. If user A logs in to two terminals at the same time and delete or modify template 1 on terminal 1, the deletion or modification cannot be performed on terminal 2 automatically. The manual refresh provided by the system, however, enables you to refresh the template information manually.
All rights reserved
Page 63

Operations involved in the M2000 log management are as follows:
Querying logs Collecting statistics on logs Managing log templates
All rights reserved
Page 64
Querying Logs
Querying operation logs Querying system logs
Querying security logs
Querying NE security logs
Querying NE operation logs Page 65
All rights reserved
Collecting Statistics on Logs

Collecting statistics on operation logs Collecting statistics on system logs Collecting statistics on security logs
Collecting statistics on NE operation logs
Collecting statistics on NE security logs
All rights reserved
Page 66
Managing Log Templates
Saving a template
Modifying a template
All rights reserved
Page 67

All rights reserved
Page 68
M2000 Fault Management
Function
The M2000 reports, manages, and analyzes NE alarms in a centralized manner. The M2000 collects NE alarms to the M2000 and displays different audio and video device alarms for the maintenance personnel. 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 69

Fault Management
Alarm severity
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.
Prompt
Alarms can be related to the following items:

Power supply system Environment system Signaling system Relay system Hardware system Software system Operating system Telecommunications 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
All rights reserved
Page 70

Saving alarms
In the alarm database, four tables are available for saving alarms. The four tables are as follows: tbl_cur_alm: saves currently generated alarms. tbl_his_alm: saves alarms generated in the past. tbl_event: saves the event alarms. tbl_mask_alm: saves the shielded alarms.
All rights reserved
Page 71
Mechanism for Processing Alarm Table Overflow

By default, the alarm service detects whether the number of alarms in the alarm table reaches to the upper threshold every 83 seconds after it is started. The upper threshold for each alarm table is as follows: tbl_cur_alm: 100, 000 tbl_his_alm: 2 million and can be modified through the M2000 client. tbl_event: 200 million and can be modified through the M2000 client. tbl_mask_alm: 200, 000
All rights reserved
Page 72
Mechanism for Processing Alarm Table Overflow

When the alarms recorded in the alarm table exceed the threshold, different alarm tables have different mechanisms to process alarm table overflow.
tbl_cur_alm: sorts the alarms by alarm generation time in sequence and forcibly changes first ten thousand unacknowledged and cleared alarms to the tbl_his_alm. If the alarm table still has the problem of overflow, move the earliest unacknowleged and uncleared alarms to the tbl_his_alm.
tbl_his_alm: sorts the alarms by alarm generation time in sequence and documents the 20 percent of the earliest alarms. Then, the system deletes these earliest alarms automatically.
tbl_event: sorts the alarms by alarm generation time in sequence and documents the 20 percent of the earliest alarms. Then, the system deletes these earliest alarms automatically.
tbl_mask_alm: deletes the earliest 100,000 alarms from the alarm table.
All rights reserved
Page 73
Operations Involved in the M2000 Fault Management

Browsing current fault alarms Browsing event alarms Querying current fault alarms Querying event alarms
Collecting statistics on alarms
Querying history fault alarms
Querying shielded alarms
All rights reserved
Page 74

Browsing current fault alarms Browsing event alarms Setting alarm services
All rights reserved
Page 75

Set alarm services.
Setting remote alarm notification Acknowledging Setting alarms conditions for alarm filtering Redefining alarm severity
Setting alarm correlation analysis Setting parameters of remote alarm notification
All rights reserved
Page 76

All rights reserved
Page 77
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. Page 78
All rights reserved
Performance Measurement Objects

Class 1
Refers to some significant objects of NEs. By default, objects belonging to class 1 are in the measurement state. The measurement on class 1 objects can be cancelled. For instance, the Iu interface of the RNC belongs to class 1.
Class 2
By default, the objects belonging to class 2 are in the non-measurement state. You need to first activate these objects before performing any measurement on them. You can enable or cancel the measurement on these objects. For instance, the neighbors of
the RNC belongs to class 2.
All rights reserved
Page 79
Performance Measurement Objects

Class 3
Refers to those objects created manually by users in the Setting Performance Measurement Object dialog box. You need to first activate these objects before performing any measurement on them. You can add, modify, or delete the Class 3 objects. In addition, you can also enable or cancel any measurement on class 3 objects. For instance, the IMSI number of the SGSN belongs to class 3. The RNC does not have class 3 objects.
All rights reserved
Page 80
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.
All rights reserved
Page 81
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 82
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 83
Measurement Settings
Open the Measurement Settings window.
All rights reserved
Page 84
Setting Measurement
Change of function sets Change of function subset Periods for the selected function subset Two navigation modes Counter ID
Applying the measurement
Objects
Several NEs
All rights reserved
Page 85
Monitoring NE Performance
Querying missing measurement results of NEs Synchronizing measurement results of NEs
Measurement management
All rights reserved
Page 86
Monitoring NE Performance
Monitor the integrity of measurement results of current NEs.
All rights reserved
Page 87
Querying Performance Measurement Results (I)
Query template
Create a query
All rights reserved
Page 88
Querying Performance Measurement Results (II)
Setting an object
Other settings, such as querying the busy-hour results, measurement periods, sorting, and filter conditions
Setting a counter
All rights reserved
Page 89
Managing Measurement Objects
Importing the information about measurement objects Exporting the information about measurement objects HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 90
Managing Measurement Objects

Activate/Suspend measurement tasks.
Suspending measurement tasks Activating measurement tasks
All rights reserved
Page 91
Managing User-Defined Counters
Creating user-defined counters Modifying userdefined counters
Importing user-defined counters

Exporting user-defined counters
All rights reserved
Page 92
Managing Counter Threshold
Setting the counter Modifying the threshold counter threshold
Setting the status of the counter threshold
All rights reserved
Page 93
Monitoring NEs in Real Time
All rights reserved
Page 94

All rights reserved
Page 95
Software Management
The software management involves the following operations:
Managing the software and files

Upgrading NE software and patches Managing RAN Licenses Querying Version Information on Software Installed on the Server
All rights reserved
Page 96
Managing Software and Files
Browsing the file information on the server. The file information includes software, patches, license, data, and others.
All rights reserved
Page 97
Managing Software and Files
Transferring files from the client to the server Transferring files from the server to the client
Transferring files from NEs to the server
Transferring files from the server to NEs
All rights reserved
Page 98
Upgrading NE Software and Patches
The software management function enables you to upgrade the software and patches of the following NEs: RNC NodeB SGSN GGSN MSC server MGW ASN-GW
Note
For details about how to upgrade the RNC, the NodeB, and their corresponding patches, refer to the upgrade guide.
All rights reserved
Page 99

All rights reserved
Page 100
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 101
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 102
Overview of Data Management: NM Log Data
When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic information from the M2000 server and client through the FTP protocol. By using this information, you can locate faults.
The collected information is as follows: Trace files on the client, for example, Client_DebugTrace. Java virtual machine thread stack and lock state of the client, for example, Client_ThreadStackDump.txt. Trace files on the server, for example, iMAP.root.trace (to store the current trace file) imap_stacks.20070206.170237.trace (to store history trace files before the currently collected NM log file). Core files on the server, for example, core.imapsvcd.0.21221.1170824184.stack. NE alarm synchronization number, for example, FMSyncNo. The pstack file, for example, imap_stacks.20070207.155817.trace. Information of the Sybase, for example, SybaseConfig.zip, SybaseVersion.zip, SYBLog.20070206.171040.zip.
All rights reserved
Page 103
Overview of Data Management: NM Log Data

By default, the collected files are saved in M2000 client\iManagerM2000Client\diagnosis\collected files. You can change the save path.
All rights reserved
Page 104
Data Management
Management of server data Management of NE data
All rights reserved
Page 105
Data Management
NE data management
Refreshing NE backup data
Restoring NE backup data up NE
Backing data
All rights reserved
Page 106
Collecting NM Log Files

Step 1
All rights reserved
Page 107
Step 2: Set the FTP server. Enter the IP address of M2000 server. Enter the port number. Enter the FTP user name and password used to log in to the target server.
Step 3: Select information to be collected. If you plan to collect trace files on the client, trace files on the server, core files on the server, or trace files on the local maintenance station, you should enter Start Time and End Time to collect the information within the specified time range. If you plan to collect alarm diagnostic data of the NE, enter the name of the NE whose alarm diagnostic data you want collect in NE Name.
All rights reserved
Page 108
Step 4: Set the folder for saving the diagnostic information.
The collected files are saved under the M2000 client installation directory: \iManagerM2000Client\diagnosis\collected files. You can change the directory for saving collected files.
Step 5: Click Collect to collect the diagnostic information. If you click Stop when the diagnostic tool is collecting information from a client, you are not allowed to stop the progress of collecting information from the client. If you click Stop when the diagnostic tool is collecting information from the M2000 server, you are not allowed to get any diagnostic information about the server.
All rights reserved
Page 109

All rights reserved
Page 110
Configuration Management
The operations involved in the configuration management vary with different products. For details about the operations involved in the configuration management, refer to the iManager M2000 Operator Guide. This part only illustrates how to start the LMT.
All rights reserved
Page 111
Starting the LMT
All rights reserved
Page 112

Operation and Maintenance of M2000 Huawei

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Operation and Maintenance of M2000 Huawei

Caricato da

Copyright:

Formati disponibili

Security Level: Internal

Operation and Maintenance of M2000 Client

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Developed independently by Huawei

the M2000 client.

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

After learning this course, you will have a basic

Operations related to monitoring management,

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Chapter 6 Fault Management

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Logging In to the M2000 Client

Logging In to the M2000

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Logging In to the M2000 Server

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Logging In to the M2000 Server

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Logging Out Off the M2000 Client

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Upgrading the Software on the M2000 Client Automatically

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Upgrading the Software on the M2000 Client Automatically

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Overview of Other Common Operations

Overview of Other Common Operations

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Overview of Other Common Operations

Chapter 6 Fault Management

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Overview of the M2000 Network Monitoring

Monitoring the database serving status

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Setting the Server Threshold

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Setting the Server Threshold

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Monitoring the Performance Status of the Server

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Monitoring the Hard Disk Status of the Server