Book 06 M2000 Overview & Basic Operations 116p

Edited by Foxit Reader
Copyright(C) by Foxit Corporation,2005-2009

For Evaluation Only.
thong thuong
UMTS PS Routine Operation and

Maintenance Training
Book 6
M2000 Overview & Basic Operations
iManager M2000V2
System Overview and
Basic Operations
www.huawei.com
Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.
Contents
1. iManager M2000V2 System Overview ...3
2. Network Monitoring and fault management........................53
3. Topology Management ........99
4. Security Management ..115
5. Performance Management ..151
6. Software Management...193
7. Configuration Management ...210
Page1
References
M2000 Product Description
M2000 Operator Guide
M2000 help
Page2
iManager M2000V2
System Overview
www.huawei.com
Objectives
Upon completion of this course, you will be able to:

Understand the related concept about M2000
Master the M2000 system architecture
Understand the M2000 system networking
Page4
System overview
The iManager M2000 Mobile Element Management System is a centralized

mobile network management platform developed by Huawei Technologies Co.,
Ltd.
The M2000 can perform centralized management on mobile NEs provided by

Huawei, including NEs in the following network:
UMTS, GSM, CDMA, WiMAX
IP
Page5
Network Position
In Telecommunication Management Network (TMN), the M2000

is located in the Element Management-layer (EM-layer).
Network
Management
Layer
Element
Management
Layer
NMS
Other EMS
M2000
NE
Other EMS
NE
NE
NE
Page6
Interfaces
NMS
Northbound interface
FILE
SNMP
CORBA
ASC
iManager M2000
Inner/Southbound interface
NE
NE
NE
Page7

Management Ability
Network Elements managed by M2000V2 can be UMTS/GSM/CDMA/WiMAX

equipments and IP devices.
UMTS NEs: Node B, RNC;
GBSS NEs: BTS, BSC, PCU;
CN NEs: MSC, MSC Server, MGW, HLR, SGSN, GGSN, CG, SIWF, SG;
CDMA NEs: MSC, MSC Serve, MGW, PDSN, HLR, BSC, BTS, RAC, RAU,
GLMS, l PoC server, TSC;
WiMAX NEs: WiMAX BS, ASN-GW, AAA Server;
IMS NEs: IMSOMU, MRF;
IP Networking Devices: Router, Switch series, Firewall series, IPsec Gateway;
Page8
Product Feature
Providing the network management solution for wireless system

M2000 and LMT together provide two-level operation and maintenance

solution.
M2000 provides various interfaces to NMS, so as to realize the grade

management for network.
Centralized O&M function

Support centralized Topology, Configuration, Performance, Fault, Log,

Security Management, etc.
Page9

Product Feature
Flexible networking structure

M2000 communicates with NE following the standard TCP/IP protocol.
Reasonable system structure

Adopting advanced modular architecture, With the Common Object Request

Broker Architecture (CORBA) design,M2000 has favorable smoothly
expansion capacity.
With open system architecture, it is flexible to access NE.
Page10
Network Topology
Itf-N
M2000 Server
Remote terminal
NMS
Client
Alarm Box
Alarm Box
IP over Ethernet,
E1,DDN and X.25
Client 1
Client 1
Client 2
IP Bearing
Network
BSC
LMT
MGW
Area 1
MGW
MSC
Area 2
HLR
LMT
BTS
Page11

Physical Structure
The M2000 hardware includes:

Servers
Clients
Alarm box
Other networking devices
Using a dial-up server, you can operate and maintain the M2000 system through
the Public Switched Telephone Network (PSTN).
Page12
Physical Structure
The M2000 client uses a PC, An M2000 system can have multiple clients.
M2000 system server configuration

Single server system

HA system
M2000 system with one server.
M2000 system with two servers, which work in active/standby mode.
Multi-Server Load-Sharing (SLS) system

M2000 system with multiple servers, which can be in either master/slave

or master/slave/standby mode.
Page13

Physical Structure
Single-Server System
dieu khien
Page14
Physical Structure
HA System
Using the Sun Cluster application, the M2000 makes active and standby
servers in the same local network constitute an HA system.
Page15

Physical Structure
SLS System
Page16
Software Structure
The M2000 system works in client/server mode.
The M2000 software includes:
client software
server software
NE mediation software
su dan xep
qua lai
The software is mutually independent. The client software runs on the client,
and the server software and mediation software run on the server.
Page17
Software Structure
NMS
Northbound interface
M2000 server
Sybase
Server
CORBA
software
Client
software
Solaris
CORBA
NE mediation
software 1
NE mediation
software 2
NE 1
NE 2
NE mediation
software n
NE n
Page18
Server Software
The M2000 server software consists of many function modules.
Through the CORBA software bus, these modules communicate with each other
and with the M2000 client software.
Page19

Module function
NMS interface module (NBI)

Provides the northbound interface for the NMS.
Software management module (SWM)

Querying the software version
Downloading software patches
Activating/Deactivating the software
Fault management module (FM)

Collecting alarms
Querying alarms
Processing alarms
Page20
Module function
Security management module (SEM)

Managing user authorities
Managing user groups
Topology management module (TM)

Managing topology objects
Managing the topology view
System management module (SYM)

Managing the system license
Installing and uninstalling the software
Managing scheduled system tasks
Page21
Module function
Configuration management module (CM)

Querying the configuration data
Configuring NEs
Displaying NE and link reports
Performance management module (PM)

Collecting the NE performance data
Monitoring the performance in real time
Generating the threshold alarm
Page22
Module function
Log management module (LM)

System logs, Operation logs, Security logs, NE operation logs, NE security

logs
Network monitoring (NM)

Provides a graphic interface for integrated monitoring and displays the

following items for the specified objects in real time:
Alarm status, Configuration status, KPI
Signaling trace module (ST)

Traces signaling at various interfaces of the NE.
Page23
Module function
Device panel module (DP)

Resource monitoring module (RM)

Querying the status of NE devices and Operating on the devices
Monitors the NE resources, such as the CPU usage of the NE.
Sub-Area management module (SAM)

Provides CORBA interfaces for the PM, CM, SWM and performance result
export tool.
Mediation module
Provides interfaces for the mediation software of various NEs.
Page24
M2000 Client Software
The M2000 client software provides the graphic user interface (GUI) for
operating and maintaining the managed NEs.
Each module of the M2000 server software, except the mediation common
module and the NMS interface module, corresponds to a module on GUI.
Page25
NE Mediation Software
The M2000 mediation module software consists of a series of mediation

software.
Each piece of mediation software corresponds to one or more NE versions.
The mediation software provides the interface files and mediation files the NE
needs to access the M2000 system.
Page26
Typical Configuration
The M2000 server may be:

Sun Netra 240
Sun Fire V890
Sun Fire E4900
The selection of the computer for an M2000 server depends on the number
of NEs in the network. In the following situations, a Sun Netra 240 server is
required to be the administration console:

Sun Fire E4900 single-server system

HA system
SLS system
Page27
Single-Server System
Sun Netra 240
Sun Fire V890
Sun Fire E4900
CPU
2 CPU/
1.5 GHz
2CPU
/1.5GHz
4CPU
/1.5 GHz
8CPU
/1.5 GHz
4CPU
/1.5 GHz
8CPU
/1.5 GHz
12CPU
/1.5 GHz
Memory
4GB
8GB
16GB
32GB
16GB
32GB
32GB
Hard disk
2*146GB
6*146GB
2*146GB
Disk array
none
1 6140
(A 6140 disk array consists
of sixteen 146GB hard
disks.)
1 6140
disks.)
accessories
DVD/Ethernet adapter/DATA72 tape drive/English documentation
OS
Solaris 10
Database
Sybase 15.0.2
Application
M2000 Server application software
Page28
HA System
Sun Fire V890
Sun Fire E4900
CPU
2CPU
/1.5GHz
4CPU
/1.5 GHz
8CPU
/1.5 GHz
4CPU
/1.5 GHz
8CPU
/1.5 GHz
12CPU
/1.5 GHz
Memory
8GB
16GB
32GB
16GB
32GB
32GB
Hard disk
6*146GB
2*146GB
2 6140
disks.)
2 6140
disks.)
Disk array
accessories
OS
Solaris 10
Database
Sybase 15.0.2
Application
Cluster Management Software SC and M2000 Server application software
Page29
SLS System
Sun Netra 240
Sun Fire V890
Sun Fire E4900
CPU
2 CPU/
1.5 GHz
8CPU
/1.5 GHz
8CPU
/1.5 GHz
Memory
4GB
32GB
32GB
Hard disk
2*146GB
6*146GB
2*146GB
Disk array
none
1 6140
disks.)
1 6140
disks.)
accessories
OS
Solaris 10
Database
Sybase 15.0.2
Application
Disk Management Software VCS and M2000 Server application software
Page30
Operating Scenario
Single Server System
Page31
Operating Scenario
HA system
Page32
Operating Scenario
SLS system
Page33
SUN Netra 240
Front view
Page34
SUN Netra 240
Back view
Page35
SUN Fire V890
Front view
Page36
SUN Fire V890
Back view
Page37
SUN Fire E4900

Front view
Page38
SUN Fire E4900

Back view
Page39
SUN S3310/3320
Contains 5 to 12 hard disks
Be applied to V890 single/dual host, Netra 240 dual host
Page40
SUN S3310/3320
Front view
Page41
SUN S3310/3320
Back view
Page42
SUN S6140
Contains 16 hard disks maximum
Be applied to V890 or E4900 single/dual host
Page43
SUN S6140
Back view
Page44
Server application scene
No.
Management Capacity
Server type
18 equivalent NEs
Sun Netra 240 (2 CPUs)
50 equivalent NEs
Sun Fire V890 (2 CPUs)
90 equivalent NEs
110 equivalent NEs
170 equivalent NEs
Sun Fire E4900 (4 CPUs)
200 equivalent NEs
Sun Fire E4900 (8 CPUs)
Page45
Number of equivalent NEs for each NEs
Page46
Bandwidth requirements for managing the CN NEs
Page47
Single Server networking

Netra 240
M2000 Client
M2000 Server (Netra240)
SC
bge0
bge1
OM LAN Switch B
O&M IP DCN
IP Bearing Network
OM LAN Switch A
Page48
Single Server networking

V890
M2000 Client
M2000 Server
V890
StorEdge3320
rsc
ce0
ce2
OM LAN Switch B
O&M IP DCN
IP Bearing Network
OM LAN Switch A
Page49
HA networking
Netra240
3320B
3320A
M2000 Client
LAN Switch C
sc
sc
bge3
bge2
Netra240
(Administration)
sc
bge0
bge1
bge0
bge1
bge0
bge1
OM LAN Switch B
O&M IP DCN
IP Bearing Network
OM LAN Switch A
Page50
HA networking
V890
3320B
3320A
M2000 Client
LAN Switch C
rsc
rsc
bge2
bge3
Netra240
(Administration)
sc
ce0
ce2
ce0
ce2
bge0
bge1
OM LAN Switch B
O&M IP DCN
IP Bearing Network
OM LAN Switch A
Page51
HA networking
E4900
6140
M2000 Client
LAN Switch C
sc0
sc1
sc0
sc1
bge2
bge3
Netra240
(Administration)
sc
ce0
ce2
ce0
ce2
bge0
bge1
OM LAN Switch B
O&M IP DCN
IP Bearing Network
OM LAN Switch A
Page52
Network Monitoring and

Fault Management
www.huawei.com
Objectives

Master how to perform the network monitoring
Master how to perform fault management
Page54
Alarm Classification
Fault Alarm
It has the occurrence time and clearance time
Event Alarm
It has the occurrence time but no clearance time
Page55
Alarm Levels
Critical
Major
The Quality of Service (QoS) of the device or resource decreases greatly.

Proper measures must be taken to recover the service.
Minor
The device or resource may be no longer available. The fault must be

removed immediately.
The QoS of the device or resource decreases slightly. Proper measures

must be taken or further observation need to be done to avoid more severe
faults.
Warning
The QoS of the device or resource may be affected. Proper measures must
be taken.
Page56
Alarm Collection
All the alarms of the NEs are reported actively to the M2000.
The alarms of most NEs are reported through port 6001.
Page57
Alarm Storage
There are four tables in the alarm database (fmdb) to store the
alarms:
Table of current faulty alarms: tbl_cur_alm
Table of History faulty alarms: tbl_his_alm
Event alarm table: tbl_event
Mask alarm table: tbl_mask_alm
Page58
Alarm Storage
R6 version only support alarm Auto displace.
NE
Alarm Correlation
Fault alarm
abandon
Event alarm
fmdb
tbl_cur_alm
tbl_his_alm
tbl_event
AcknowIedged & Cleared
file
Auto
displace
file
Page59
tbl_mask_alm
Processing Mechanism of Overflow

If the alarm service is running, it checks whether the alarm tables
reaches their upper limit every 83 seconds (default value).
Table tbl_cur_alm can hold a maximum of 100,000 alarms.
Table tbl_his_alm can hold a maximum of 2,000,000 alarms.
Table tbl_event can hold a maximum of 2,000,000 alarms.
Table tbl_mask_alm can hold a maximum of 200,000 alarms.
Page60
Processing Mechanism of Overflow

When surpass the upper limit

Table tbl_cur_alm displaces 10,000 alarms forcibly to history table. It

displaces the earliest cleared and unacknowledged alarms in priority
according to the occurrence time of the alarms . If the alarms are less
than 10,000, it then displaces the earliest un-cleared and
unacknowledged alarms.
Table tbl_his_alm displaces the earliest 20% of the alarms to files

according to the occurrence time of the alarms and deletes them from the
table.
Table tbl_event displaces the earliest 20% of the alarms to files

according to the occurrence time of the alarms and deletes them from the
table.
Table tbl_mask_alm does not displace the alarms to the files. It deletes
the earliest 100,000 alarms from the table directly.
Page61
Alarm Show
Components which can only receive fault alarms:

Alarm Board, Speaker, Topology
Components which can receive both fault and event alarms

Alarm Box
Speaker
Topo
Alarm Board
Alarm Box
Alarm message
Page62
Browse, Query and Statistics of Alarm
Browse the latest 1000

alarms in real time
Statistics
Query
fmdb
tbl_cur_alm
tbl_his_alm
tbl_event
tbl_mask_alm
Page63
Fault Alarm Browsing
Page64
Event Alarm Browsing
Page65
Alarm Querying
Page66
Alarm Querying
Page67
Alarm Synchronization
Includes Auto and Manual alarm synchronization

Auto alarm synchronization

All the alarms are auto synchronized when the NE is reconnected.
All the alarms are auto synchronized when the UMTS NE is created, All
the active alarms are auto synchronized when the G/C NE is created.
Manual alarm synchronization

Only the active alarms, which are uncleared fault alarms, will be
synchronized.
Page68
Manually synchronize alarm
Page69
Locating Alarms
Use the function to locate the NE that raises the alarm by the
alarm record.
Page70
Manually Clearing Alarm

Manually clear the alarms that cannot be recovered automatically

or that are confirmed to be cleared.
Page71
Alarm Statistics
Page72
Alarm Statistics result
Page73
Setting Alarm Real-Time Monitoring
Page74
Setting Alarm Filter
Alarm Filter
M2000
NE
Discard
Page75
Setting Alarm Filter
Page76
Setting Auto Acknowledgement
Page77
Setting Alarm Level Redefinition
Page78
Setting Alarm Remote Notification

Email
Transmitted through smtp Server.
SMS
Transmitted through wireless Modem. The wireless modem can be

connected to the M2000 Server or the 2000 Client.
Transmitted through short message center.
Email
SMS
Alarm messages
Page79
Setting Alarm Remote Notification
Page80
Alarm Correlation
Aim
To reduce the redundant alarms.
Correlative alarms
Correlative alarms are alarms that have correlations between one another.
One is the root alarm that raises other alarms.
A fault may result in multiple alarms, the non-root alarms do not help in the
fault location or analysis.
Page81
Alarm Correlation
Intermittent Alarms
If the interval between two clearance times of an alarm is less than set period of
the cleared alarm, the alarm is an intermittent alarm.
Repeat Events
If the reporting times of an event is more than the set times in the set period, the
event is a repeat event.
Simple/Advanced Correlation
the correlation of the intermittent alarms or repeat events is considered as simple

correlation alarms.
the correlation of the other alarms is considered as advanced correlation alarms.
Page82
Alarm Correlation
Understand the alarm interval T

Fault alarm
Recover
Generate
0
Event alarm
t
T
T
Page83
Principles of Correlation
Two conditions
Alarm interval T
Unit: second
If the alarm interval is less than or equivalent to T, the first alarm will enter the fault
alarm current table or event alarm table. And the subsequent alarms whose alarm
intervals are less than or equivalent to T will be saved to mask table or abandoned
directly according to the correlation rules.
High frequency alarm threshold N

Unit: times
If the system receives certain alarms (alarm intervals T and number of alarms
N ) of the NE continuously, the system will generate high frequency alarms whose
Equipment Serial Number is 0 and alarm level is higher. For fault alarms, if the
subsequent alarm interval of the alarms are more than T, the high frequency alarm
will clear.
Page84
Examples
The correlation configuration of the MSCe is as follows:

The fault alarm whose alarm level is Major is E1/T1 Loss of Signal (ID=1101)
The interval of the alarm is 10s.
The times of high frequency alarm is 10.
The alarms meeting the correlation are saved to the mask table.
t2
t1
1
10 11
12
13
t
T1
T2
T3
T4
T5
T6
T7
T8
T9
T10
Page85
T11
T12
T13
Examples
Suppose T1 to T12 <=10s, T13 > 10 s, the M2000 will generate a E1/T1
Loss of Signal alarm for MSCe at t1. The alarm level is Critical and the
alarm will clear at t2.
The first alarm is saved to fault alarm current table and the 2-12 alarms
are saved to alarm mask table.
Page86
Adding Simple Correlation Rules
Page87
Adding Advanced Correlation Rules
Page88
Alarm Setting of NE
The following three functions is delivered to the NE

Alarm shielding
If the alarms are shielded at the NE, they will not be reported to the LMT
and M2000.
Alarm level redefinition

Support NEs with NBMML interfaces only.
Support NEs with NBMML interfaces only.
User defined alarm

Includes alarm definition and alarm binding.
Page89
Shielding an NE Alarm
Shield the alarms that you are not required.
Page90
Redefining the Level of NE Alarm
To redefine the severity level of an NE alarm.
Page91
Setting Monitoring Parameters

Set thresholds for the performance monitoring, hard disk monitoring, database
monitoring, and service monitoring. When the threshold is reached, the M2000
raises an alarm.
Page92
Monitoring Performance Status

To view the information on the operating system, memory usage, and CPU
usage of the M2000.
Page93
Monitoring Hard Disk Status

To view the total space and usage of the hard disk.
Page94
Monitoring Database Status

To monitor the status of the M2000 server database to view the information such as
the database name, server name, and database status.
Page95
Monitoring Service Status

To monitor the status of the M2000 server services to view the information such
as the service name and service status.
Page96
Monitoring Process Status

To monitor the status of the M2000 server processes to view the information such
as the process name, process ID, and number of threads.
Page97
Monitoring NE Status
To monitor the status of the connection between M2000 server
and NEs.
Page98
Topology Management
www.huawei.com
Objectives
Master how to perform the topology management
Page100
Topology interface
Page101
Basic Knowledge of Topology
Topology Management Function

Topology management is used to construct and manage the entire network

topology and helps you know the networking and operational status of the
devices in real time.
Objects in a Topology
Topology objects refer to the elements in a network. Each element managed

by the network management system is called an object.
Page102
An object can be a subnet, an NE, a group NE, or a link.
Subnet
NE
a large network can be divided into several smaller networks based on a

specific rule (for example, by region) for the convenience of network
management. In topology, these smaller networks are called subnets.
NEs are used to identify concrete entity devices, such as MGW and HLR.
NEs can be grouped into physical NEs and virtual NEs.
Group NE
In a telecommunication network, some NEs are interdependent. A group

NE is an NE that has the characteristics of both NE and subnet.
Page103
Link
Links refer to the links between NEs that are mapped in the topology,
including physical links and virtual links.
A physical link indicates that there is physical connection between two

physical NEs. Currently the M2000 supports six types of links: M3UA,
H248, BICCSCTPLNK, DATALINK, MTP3, and MTP3B.
M3UA, H248 and BICCSCTPLNK links are created by the system

automatically. DATALINK, MTP3 and MTP3B links are created manually.
You can delete only physical links that are manually created.
A virtual link refers to the logic link between two NEs (including physical
NEs and virtual NEs), and you can set up a virtual link manually.
Page104
Creating a Physical Subnet

Choose Topology > Main Topology.
Right-click in the topology view
Page105
Creating NEs
choose New > Create Topo Object
Page106
Moving an NE into a Group NE

Right-click the group NE and select Property from the shortcut menu and Click the
Object Selection tab.
Page107
Allowing Reconnection to an NE
When an NE is disconnected with the M2000 server, you can specify whether
the server automatically connects the NE.
There are two connection states:

Enable Connection
When the communication between an NE and the M2000 is

disconnected, the M2000 attempts to reconnect the NE. By default, the
connection state of a newly added NE is Enable Connection.
Disable Connection.
When the communication between an NE and the M2000 is

disconnected, the M2000 does not attempt to reconnect the NE.
Page108
Disable Connect NE
Disconnection icon
Disabling connection icon
Choose Topology > Main Topology.
Select an NE and right-click.
Page109
Manually Reconnecting an NE
We can reconnect an NE manually when the NE is disconnected from the M2000
server.
On the physical topology view,
select an NE with the Disconnected icon.
Right-click the NE, and select Reconnect.
Page110
Adjusting the Topology View
Continueda
At;hhajgahghag
Create link
Print
Topology
overview
Search NE
Show legend and filter
Show alarm browse region
Select the layout mode
Page111
View/Modify a physical link

Method 1:
On the physical topology view, double-click a physical link or a physical link

set. In the displayed information box, right-click a link and choose Query Link
Information on the shortcut menu.
Click Filter.
Method 2
Choose Configuration > Link Browser.
Page112
Setting Alarm Display

when an alarm is raised on an NE, the color of the NE on the topology view is
changed to the color indicating the highest alarm severity level in the
corresponding status, thus you can know the alarm information in time.
Page113
Displaying the Alarm Pop-Up Pane

Right-click in the topology view and choose Show Alarm Balloon.
Page114
Security Management
www.huawei.com
Objectives
Master how to perform security management
Page116
Security management interface
Page117
Overview
Centralized User Management
User account
NE user: The NE users operate and maintain NEs through the LMT.
OM user: OM users operate and maintain the entire network or specified

NEs through the M2000.
Centralized Management Mode

For category A NEs, you can grant relevant rights to an OM user and the OM
user becomes an NE user, In this way, you can perform uniform
management of user accounts on the entire network.
For category B/C NEs, you need to create an OM user on the M2000 and
NE user on the NEs, and then manually establish and maintain the
association between the OM user and NEs.
Page118
Overview
User monitoring and control
The function of user monitoring provided by the M2000 enables you to

monitor the operation and session of a user, and to query the operation
log.
For category A NEs, you can monitor the operation and session of a user
on the M2000 and on the LMT at the same time.
User Authority
The user authority consists of the user, operation, and NE.
Authority Item
network management application authority
network device authority
Page119
Overview
Allocation Mechanism
the M2000 provides the allocation mechanism at user group and user
levels.
The user authority contains the authority of the user group that the user
belongs and the authority of the user.
Page120
NE User
NE uses can log in to NEs through the LMT and operate and maintain NEs.
Type of NE Users
local NE users
The account, password, and authority of a local NE user are
managed by NEs. The creation and modification of a local NE user
are performed through the LMT of NEs.
non-local NE users
The account, password, and authority of a non-local NE user are
managed by the M2000.The creation and modification of a non-local
NE user are performed through the M2000.
Page121
NE User
User Management of Category A NEs

Category A NEs support local and non-local NE users. If an OM user is

granted with the MML authority of category A NEs, the OM user becomes
a non-local user of the NEs.
User Management of Category B/C NEs

Category B/C NEs support only local NE users.
Page122
Setting the M2000 Security Policy

Setting the Password Policy
to set the parameters such as password valid days, length of a password

and number of letters in a password.
Setting the Account Policy

to set the maximum login attempts and auto unlock time.
Setting the System Policy

to set the number of the sessions that are supported by the M2000.
Page123
Setting the M2000 Security Policy

Choose Security > Security Policy.
Page124
Setting Single-User Mode

The M2000 runs in multi-user mode by default. When you perform maintenance
on the M2000 server, for security purposes, you can set the M2000 to singleuser mode.
Page125
Setting the System ACL

Set the Access Control List (ACL) to allow the users to log in to the M2000
through the clients of only the specific IP addresses or network segment.
Page126
Customizing NE type Command Group

To define a common command group according to actual requirements.
Choose Security > NE User Management.
Select an NE type node from the navigation tree. Right-click and choose
Customize Command Group.
Page127
Customizing NE type Command Group
Page128
Customizing NE Command Group
To customize an NE command group when the command group provided by NEs

cannot meet the requirements for the authority set by users.
Choose Security > NE User Management
Select a specific NE node under the NE type node from the navigation tree.
Right-click the node and choose Add Command Group.
Page129
Customizing NE Command Group
Page130
Setting Authority Rules for NE Types

To set an authority rule by granting the authorization of the MML command group
of a specified NE type to an OM user or a user group.
Issue the authority rule to the specified NEs so that the OM user or user group
owns the MML command authorization of the NEs.
Once the authority rule is created successfully, the OM user or user group owns
the MML command authorization of all the new NEs of the same NE type.
Page131
Setting Authority Rules for NE Types
Page132
Issuing Authority Rules for NE Types

To issue authority rules for NE types. After you apply the authority rules on the
NEs that are of the corresponding types, the OM user obtains the MML
authorities of the NEs.
Page133
Synchronizing NE Security Data

To synchronize the NE security data.
Page134
Creating an OM User Group

By creating an OM user group, you can manage the OM user accounts in groups
and grant related rights to the members of the group.
Page135
New Device Access Rights

New device access rights consist of NEs and operations.
Newly-added NEs will inherit the new device rights automatically. This realizes autoauthorization.
New device access rights are configured in one user group.
Page136
Creating an OM User Account

Create the OM user accounts in the M2000 so that multiple OM users can
operate and manage the M2000.
Page137
Synchronize OM user data

To synchronize the OM user data. The synchronization of OM user data
synchronizes the data on the M2000 with that of the associated NE.
Page138
Querying Authorization
Query the authorization of the NEs and the M2000 rights in the M2000.
Page139
Comparing the OM User Rights

Compare the rights of two users in the M2000.
Page140
Creating an NE User
Before you create a user of category B/C NEs, you need to create an NE local user
on NE side.
Create a user of category A NEs

Create an OM user on the M2000 side.
Assign the authority of the MML commands to an OM user.
Page141
Creating an NE User
Page142
Changing Password of an NE User

Change the password of the category A NE user.
For a category A NE, the corresponding OM user becomes an NE user after

you grant the user the related NE authority.
Page143
Monitoring OM Users
Monitor the OM user sessions and operations, to prevent illegal user operations.
Page144
Monitoring NE User
This function supports only A NEs.
Page145
Setting Status of non-default NE User
The non-default users are the local NE users except user admin and guest.
The status of the non-default NE user includes two types:

Manageable, it indicates that the NE can be managed.
Whether inhibit login, it indicates that the login is inhibited.
Page146
Setting Status of non-default NE User
Page147
Forcing User to Exit

Forcing an OM User to Exit from the M2000
Page148
Forcing User to Exit

Forcing an NE User to Exit from the LMT
Page149
Unlocking an OM User
If the number of the times that a user enters an incorrect password reaches the
number of the preset login attempts, the user is locked.
Page150
Performance Management
www.huawei.com
Objectives
Master the concept related to Performance Management
Master how to perform Performance Management
Page152
Three Elements of Measurement

Counter
Performance measurement counter is a basic unit for the performance

measurement. It defines what to measure.
Counter categories
The default counters, also called system counters, are defined by NEs,
include:
common counters
extended counters.
user-defined counters, are defined on the M2000 client.
Page153

Counter Classification
Original Counter
Default Counter
It is also call the Common Counter, KPI Counter;
It contains some important counters of the NE, and is in the state of
measuring by default. Users can not deactivate its measurement.
Extended Counter
It is not in the state of measuring by default and users need to activate it
to be the measuring state. Users can also deactivate it.
User-Defined Counter
As the original counter can not satisfy the customers needs, the user-defined
counter can be applied.
Page154

User-Defined Counter
After the first installation, there is no User-Defined counter;
Perform arithmetic operation on the original counter (+ - * /);
It is not delivered to the NE, Its result is not saved in the database, it only
has temporal calculation during queries;
The original counter used in user-defined counters must be activated

manually;
Page155

Object
A measurement object can be the physical concept of boards or subracks, or

the logical concepts of cells. It define whose counters to measure.
Classification of Objects
Class-1 Object
Class-2 Object
Class-3 Object
Page156

Class-1 Object
Important objects of NEs. They are in the measuring state by default and
users can not deactivate them.
Class-2 Object
Not in measuring state by default. Users have to activate it to measure.

Users can also deactivate it.
Class-3 Object
It is added manually by users in the performance object setting window.

Users have to activate it to measure. Users can add, modify, delete,
activate and deactivate this type of objects.
Page157

Period
A measurement period refers to the interval for NEs to report

performance measurement results. It define how to measure.
The measurement periods vary according to the measurement

objects.
The following measurement periods are available:

5 minutes, 15minutes, 30 minutes, 60 minutes, or 24 hours.
Page158
Querying Objects and counters
Page159
Querying Objects and counters
Period
Counter
Object
Page160
Managing Class 3 Object

For the type 3 object, you must select objects and enter required parameters for the
client to collect the counter information.
Page161
Managing Class 3 Object
Page162
Adding a User-Defined Counter

According to the existing measurement counters, to define a user-required
measurement counter by using the arithmetic.
Page163
Adding a User-Defined Counter
Page164
Setting Performance Measurement

To set measurement objects and counters and add the measurement range.
Page165
Managing Measurement States

To view the measurement state and the corresponding quantity of all NE
measurement units of a certain NE type.
Page166
Synchronizing Measurement Results

To obtain the missing measurement results by synchronizing measurement
results.
Page167
Subscribing to Measurement Results

To help query measurement results, you can subscribe to measurement results
by object and counter.
Page168
Subscribing to Measurement Results
Page169
Querying Missing Results

During the M2000 running, measurement results may be missing due to many
reasons, such as the disconnection of NEs from the M2000 within a period of time. If
measurement results are lost, you can synchronize the measurement results to
obtain the missing results.
Page170
Querying Missing Results
Page171
Checking Integrity of Results

This task consists of two sub-tasks: monitoring the integrity of current results and
querying the integrity of historical results.
Monitoring the integrity of measurement results refers to checking the integrity of

measurement results in a measurement period before the current time.
Integrity of measurement results is associated with the number of results to be

reported, number of results reported, and the ratio of the two numbers.
Page172
Checking Integrity of Results
Page173
Querying Performance Results
Two query modes

by template
by new conditions
Page174
Querying by template
Page175
Querying by new conditions
Page176
Query Results by Busy Hour

The busy hour refers to the hour when the counter value is the greatest.
The period for collecting statistics of busy hour is set to 60 minutes.
We can not perform busy hour query of the day, can perform busy hour query only
when busy hour counters of the select NE type exist. Busy hour counters are
defined by NEs.
We cannot query the missing results by this query mode.
Page177
Query Results by Busy Hour
Page178
Displaying Performance Results

Measurement results can be displayed in a table or a line or bar chart.
Page179
Printing Performance Results
Page180
Managing Result Query Templates
Page181
Performance Counter Thresholds
The performance threshold is used to monitor the actual measurement result of

the performance counter. When the value of the measurement result exceeds
that set by the user, the system generates an alarm.
The threshold value of the performance counter can be the threshold value of a
specific performance counter or the threshold value of the combined
performance counters.
Page182
Setting Simple Counter Threshold

Simple threshold is a threshold defined for a single counter.
Page183
Threshold Alarm
Page184
Setting Combined Counter Threshold

Combined threshold indicates setting the threshold value for the counters after
logic or arithmetic operations.
Page185
Activate/Deactivate Counter Threshold

Suspend a threshold when it is not used temporarily, and then activate it if required.
Page186
Starting Performance Monitoring
Monitor the specified object types and instances in real time and display the
monitoring results in data tables and figures.
This section shows how to start the real-time performance monitoring, which
consists of creating, viewing, and starting a monitoring task, synchronizing the
monitoring data, and setting the monitoring threshold.
Page187
Viewing Monitoring Task Information
Page188
Creating a Monitoring Task
Page189
Starting a Monitoring Task
Page190
Synchronizing Monitoring Data
Page191
Setting Monitoring Thresholds
Page192
Software Management
www.huawei.com
Objectives
Know Basic Knowledge of Software Management
Managing Software and Files
Upgrading NE Software and Patches
Querying Version Information on Software Installed on the Server
Page194
NE Software
NE software refers to the software version that matches the current NE.
Some NEs, such as MGW, NodeB, SGSN, and TGW, provide an active and a
standby storage area. Therefore, these NEs can store at least two software
versions. The active area stores a software version and a mapping hot patch. In
other words, the software a patch is activated and is operational. The standby
area stores the software that is not activated.
Page195
Software Patch
There are two kinds of NE software patches: hot patches and cold patches.
Loading cold patches need reboot NEs. Loading hot patches need not reboot
NEs.
In the M2000 system, cold patches are managed as special software version
with the NE software.
Software hot patches are identified with patch IDs, which are numbered from
1. IDs of the patches for the same software release reflect their release time,
that is, the larger the value of an ID is, the later it is released. A released
patch must contain contents of all patches released previously.
Page196
Software and Patch States

The state of a software patch can be idle, inactive, active, or running.
Page197
Software Management File Types

The M2000 manages different files for NEs, such as software version package,
patches, configuration data, license, and voice files. The managed files vary
according to the NE types.
Different NE types map different managed files. For details, for MSC Server, only
Patch can be managed and for MGW, Version, patch, license, data, voice can be
managed.
Page198
Software Management Procedure

In the whole process, the M2000 server is the default file server. Through the GUI,
operation and management commands are sent to the file server and then sent
to NEs. Upon receiving the commands, the NEs determine whether to execute
the commands and give a feedback to the file server. Then, the file server sends
the received information to the client and the information is displayed through the
GUI.
Page199
Viewing File Information

Step 1 Choose Software > Browser or click The Software Browser window is
displayed.
Step 2 Select an NE type to be viewed on the navigation tree on the Server tab
page.
Step 3 In the right pane, click the related tab to view the file information.
Page200
Viewing File Information
(1) Navigation tree Lists NE types.

(2) Tab Includes immediate tasks and file transfer tasks.
(3) Content window Lists software version, patches, license, and data of NEs saved on the
server. The M2000 support different file types for different NEs. For details. Lists software,
patches, and data of NEs saved on the server.
(4) Content window Lists details of operation tasks.
(5) Operation bar Arranges provided operation buttons.
Page201
Transferring Files from Client to Server

If the file to be transferred is not a voice resource file, perform the following steps:
1. Choose Software > File Transfer Wizard. The Select General Parameters
dialog box is displayed.
2. In Direction, select From GUI To Server.
3. In Server Path, select the file to be transferred.
4. Click Next. The Select Data File dialog box is displayed.
5. Select the file to be uploaded. You can select multiple files.
6. Click Finish.
Page202
Setting Parameters for Transferring Files

Step 1 Choose Software > FTP Setting to open the FTP Parameter Setting
dialog box.
Alternatively, you can choose System > Preferences to open the System
Setting dialog box.
Step 2 Choose FTP mode, FTP optional function, and network timeout.
The FTP modes consist of FTP and SFTP.
The FTP optional function consists of breakpoint, compress, and passive

mode. If you do not select Passive Mode, the default mode is active mode.
Page203
Parameters for Setting Parameters

Files Transferring
of
File transfer mode:

FTP
Basic FTP mode.
SFTP
Transfer mode based on the SSH protocol. SFTP uses a mature public key
mechanism or private key mechanism to encrypt data packets in the network.
In this case, data communication between two ends can be performed in an
encrypted channel.
Optional functions of file transfer
Page204
Parameters of Setting Parameters of Files Transferring

Optional functions of file transfer
Breakpoint
During file transfers between clients and servers, if destination files exist, the
system prompts users to select resumable downloading or overwriting. If you
select resumable downloading, files are transferred from the size of
destination files.
Compress
Passive
The client actively requests for connection. The server listens and determines
whether to establish FTP connection.
Page205
Upgrading NE Software and Patches

To Upgrade the Software and the patches of the NE, we need to do the operation
including the following steps ( MGW ):
Downloading the MGW Software Patch
Loading the MGW Software Patch
Activating the MGW Software Patch
Confirming the MGW Software Patch
Use NE Upgrade Wizard to do this operation
Page206
Upgrading MGW Software and Patches

Use NE Upgrade Wizard to do this operation
Page207
Querying Version Information on Software

On the M2000 client, you can query the version information about the software
installed on the server. :
The OMC version information, which includes the version numbers of the
software and patch installed on the OMC server.
The version information about the adaptation layer, which refers to the
version number of the adaptation layer connected to the NEs.
The ENM version information, which refers to the version number of the
components used for the NE maintenance.
The version information of the northbound Corba interface.
Page208
Querying Version Information on Software

Step 1 Choose the Software > Browser menu item.
Open the Software Browser.
Step 2 Select the Server tab. Run the operations according to your
requirements.
Page209
Configuration
Management
www.huawei.com
MIT
Management Information Tree (MIT) is used to check the configuration
information of NEs.
We can browse the configuration data of the NE but cannot edit the configuration
data through the MIT.
The MIT is read-only and cannot be modified.
Page211
MML Commands
The MML command is called the Man Machine Language.
It is the main mode of NE operation and maintenance. To facilitate NE

maintenance, the M2000 provides the MML command client. Through this client,
you can deliver MML commands to NEs and query the execution results.
Page212
Inventory Management
Inventory management refers to the centralized and effective management of the
physical asset information and key logical configuration about the entire network
devices.
In M2000, you can query, synchronize, modify, import, or export the asset
information and configuration information of the NEs.
Page213
Viewing NE MIT Information
Page214
Viewing NE other Resource

Viewing NE Resource Reports
Viewing NE Link Reports
Viewing NE Statistics Reports
Viewing NE Reports
Page215
Configuration Synchronization
The M2000 has not saved all the configuration data of the NE.
Synchronization Mode
Automatic synchronization
Timing synchronization
Support the UMTS NE
Support all the NEs
Manual synchronization
Support all the NEs
Page216
Manually Synchronizing
Page217
Manually Exporting
Manually exports configuration data of physical NEs and save the required
configuration data to a specified path.
Page218
Managing Inventory Data

Querying Inventory Data
Page219

Adding Inventory Data
Page220

Exporting Inventory Data
Page221
Viewing NE Resource States
Page222
Monitoring NE Resource States
Page223
Core Basic Navigation Configuration
Page224
Executing an MML Command

An MML command is used to perform operation and maintenance on NEs.
Page225
Viewing Follow-Up Reports

Only one prompt can be displayed in the MML Command window. When more
than one messages are returned after the M2000 delivers an MML command to
an NE, you can query them by using this function.
Page226
Setting the Attributes
Page227
Starting the LMT

The local maintenance terminal (LMT) is the local O&M system of an NE. If an
NE cannot be connected directly owing to the configuration of the firewall, you
can use the LMT to connect the NE.
Page228

Book 06 M2000 Overview & Basic Operations 116p

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Book 06 M2000 Overview & Basic Operations 116p

Hochgeladen von

Copyright:

Verfügbare Formate

Edited by Foxit Reader

Copyright(C) by Foxit Corporation,2005-2009

UMTS PS Routine Operation and

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

Understand the related concept about M2000

Master the M2000 system architecture

Understand the M2000 system networking

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

The iManager M2000 Mobile Element Management System is a centralized

The M2000 can perform centralized management on mobile NEs provided by

UMTS, GSM, CDMA, WiMAX

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

In Telecommunication Management Network (TMN), the M2000

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Edited by Foxit Reader

Network Elements managed by M2000V2 can be UMTS/GSM/CDMA/WiMAX

UMTS NEs: Node B, RNC;

GBSS NEs: BTS, BSC, PCU;

WiMAX NEs: WiMAX BS, ASN-GW, AAA Server;

IMS NEs: IMSOMU, MRF;

IP Networking Devices: Router, Switch series, Firewall series, IPsec Gateway;

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Providing the network management solution for wireless system

M2000 and LMT together provide two-level operation and maintenance

M2000 provides various interfaces to NMS, so as to realize the grade

Centralized O&M function

Support centralized Topology, Configuration, Performance, Fault, Log,

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Edited by Foxit Reader

Flexible networking structure

M2000 communicates with NE following the standard TCP/IP protocol.

Reasonable system structure

Adopting advanced modular architecture, With the Common Object Request

With open system architecture, it is flexible to access NE.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Edited by Foxit Reader

The M2000 hardware includes:

Other networking devices

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

M2000 system server configuration

Single server system

M2000 system with one server.

M2000 system with two servers, which work in active/standby mode.

Multi-Server Load-Sharing (SLS) system

M2000 system with multiple servers, which can be in either master/slave

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Edited by Foxit Reader

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Edited by Foxit Reader

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

The M2000 system works in client/server mode.

The M2000 software includes:

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Edited by Foxit Reader