Professional Documents
Culture Documents
Issue 1.0
Date 2009-06-20
INTERNAL OPEN
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please
feel free to contact our local office or company headquarters.
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Author
Name Li Yongsheng Date 2008-05-10
Introduction
This document gives a general introduction of the functions provided by the Huawei M2000
V200R008 for WiMAX. It aims to help readers better understand M2000 functions and
features.
The table below lists the main chapters of this document.
Chapter
1 Overview
2 Basic Functions
0Supported NE Types
AAA ASN-GW BS M2000
√
Optional Functions
Revision Record
Version Revision Date Author Approved by
Description
1.00 First release 2008-05-30 Li Yongsheng Xiao Yong
Table of Contents
1 Overview ................................................................................................................................... 7
2 Basic Functions......................................................................................................................... 8
2.1 Fault Management (WOFD-010000)...........................................................................................................8
2.2 Configuration Management (WOFD-020000) ...........................................................................................18
2.3 Performance Management(WOFD-030000)..............................................................................................21
2.4 Security Management(WOFD-040000).....................................................................................................26
2.5 Log Management (WOFD-050000) ..........................................................................................................28
2.6 Topology Management(WOFD-060000)...................................................................................................31
2.7 System Management (WOFD-070000) .....................................................................................................33
2.8 System Reliability(WOFD-080000)..........................................................................................................40
Tables
1 Overview
As a brief list of the functions provided by the Huawei M2000 V200R008, the document is
intended as a general introduction to M2000 V200R008 functions, aiming to help readers to
better understand M2000 functions and features.
The network elements (NEs) in this document refer to the network equipment managed by
M2000. M2000 can manage WiMAX NEs, IP devices, DNS, DHCP and other devices.
The M2000 can manage the following WiMAX NEs:
l Base station: BS
l Access gateway: ASN-GW
l Authentication server: AAA
M2000 can manage the following IP devices:
l LAN switches of S series
− S8500: S8505, S8512
− S5624P: S5624P
− S5500: S5516
− S3500: S3526, S3526FM[FS], S3526E, S3526E-FM, S3526E-FS, S3526C-24[12FS],
S3526C-24[12FM], S3526C, S3552G, S3552P, S3528G, S3528P
− S3000: S3026, S3026FM[FS], S3026E, S3026E-FM, S3026E-FS, S3050, S3026C,
S3026C-24[12FS], S3026C-24[12FM], S3026G, S3026T, S3026G-SI, S3026C-SI,
S3026S-SI
− S2000: S2403F, S2403H, S2403H-EI
− S2000B: S2016B
l Routers of NE08 series and AR28/AR46 series
− NE08: NE08, NE08E
− NE16: NE16, NE16E
− NE40: NE40-2, NE40-4, NE40-8, NE40-E
− NE80: NE80
l Firewalls of Eudemon series
− Eudemon200: Eudemon200
− Eudemon500: Eudemon500
− Eudemon1000: Eudemon1000
In Chapter 2 of this document, the IP devices in the table of supported NE types include all
the above IP devices.
Other devices of M2000 management consist of:
l Domain Name Server: DNS
l Dynamic Host Configuration Protocol Server: DHCP server
2 Basic Functions
The real-time alarm browse function displays alarm information in the alarm browse window
in real time. User can customize the displayed alarms according to filter conditions. Multiple
browse windows can be opened at the same time, each with a different condition group. Only
the alarms that meet certain conditions are displayed in the browse window.
The conditions to be set are:
l Alarm severity
l Alarm type
l Alarm name
l Acknowledgement status
l Clearance status
l Occurred Time segment
l Cleared Time segment
Supported NE Types
Also M2000 supports to display the number of the highest severity un-cleared alarms on the
icon of this NE in the topology. It is configurable.
Supported NE Types
The alarm detailed information browse function enables user to view the detailed alarm
information about a selected alarm in the Alarm Browse window. The detailed information
includes recovery suggestion, location information, and other information of the alarm in the
knowledge database.
Supported NE Types
√ √ √ √
sorting the NEs according to the NE types and sorting the alarms according to the alarm types,
alarm categories, and alarm severity.
At the same time, users can query the existing alarm shielding records according to alarm ID,
NE name and alarm severity.
M2000 supports alarm shield for BSC6000 according to the objects, supported objects are:
cell and BTS.
The conditions to be set in adding an alarm shielding record are: object and alarm name.
Also, users can query the existing alarm shielding records according to the objects.
Supported NE Types
AAA ASN-GW BS M2000
√ √ √ √
Supported NE Types
The alarm remark function enables user to add remarks on an alarm. The remark information
includes history operations performed on an alarm, operators, operation time, and remarks to
facilitate other users' analysis. An alarm supports a maximum of 4,096-byte remark
information.
Supported NE Types
DHCP DNS
√ √
Supported NE type:
IP devices
√
IP devices
√
M2000 conducts centralized collection of network measurement data and stores the data in the
database.
The measurement counters are categorized into the following types:
l Default counters: are collected and stored by default by the system. User can configure
the measured objects.
l Extended counters: are configured by users. User can configure an extended counter
based on the measured object and counter.
By default, the default counters and extended counters are collected every 30 minutes. User
can also collect the performance data based on either of the following periods:
l 5 minutes
l 15 minutes
l 60 minutes
l 1,440 minutes
BS only supports the period of 30 minutes.
Some performance measurement counters can be suspended and resumed by measured units.
The suspended measurement counter does not report the performance data within the
suspended period.
Supported NE Types
Supported NE Types
AAA ASN-GW BS M2000
√ √ √
The performance alarm function enables user to specify alarm thresholds for the measurement
counters. When a counter value exceeds the threshold, a performance alarm is generated.
The supported functions consist of threshold definition and threshold management.
Threshold definition
l Set multiple alarm thresholds to the same counter. The threshold can be set in different
dimensions, such as objects, time periods, cycled, and trends. That is, different
thresholds can be set to a counter of different objects, time periods, cycles, and trends.
l Set the threshold of the customized counters.
l Support portfolio thresholds, namely, the triggering condition of generating and
recovering the threshold alarms is a conditional expression. The expression can contain
multiple counters. The supported operation rule includes +, -, *, /, AND, OR, =, !=, >=, >,
<, (,), and {mean}. The {mean} is used to define the constant.
l Support the dynamic change of alarm severity. If the same alarm of the same severity is
continuously generated for several times, the severity of the alarm can be raised. User
can set the alarm-generating times.
l Support users to set the alarm-generating times that meet the alarm-triggering
requirements.
l Support users to set the alarm-clearing times that meet the alarm-restoring requirements.
l Support the threshold of cell groups. The system determines the threshold condition after
summarizing the counters of all the cells in a cell group. Performance threshold alarms
are generated if the results meet the conditions of triggering threshold alarms.
l Support the dynamic changes of alarm levels. When an alarm of the same level is
continuously generated for several times, user can increase the level of this alarm. User
can set the times for alarm generation.
l Alarms are generated when the number of times that the threshold meets the alarm
triggering condition reaches a certain value. User can set the value.
l After alarms are generated, these alarms are recovered when the number of times that the
monitoring results of performance counters continuously do not meet alarm conditions
reaches a certain value. User can set the value.
Threshold management:
l Support threshold query: User can filter the thresholds according to the threshold names,
NEs, periods, triggering time, and threshold directions. User can also combination
multiple conditions to query.
l Support threshold operations in batches: The operations include activation operations in
batches and suspension operations in batches.
l Support the suspension of NE thresholds in the automatic and manual manner.
Supported NE Types
AAA ASN-GW BS M2000
√ √ √
The query on missing performance measurement data function queries the missing data of a
period for a measurement unit. User can use this function to determine the integrity of the
reported data.
Supported NE Types
AAA ASN-GW BS M2000
√ √ √
Supported NE Types
Type Description
Operation log Records all of the operations performed by users. The recorded
information is as follows:
l User name
l Terminal
l Operation time
l Operation object
l Operation name
l Operation result
Running log Records the running status of the system.
Type Description
Security log Records the events that have impacts on the system security. In
the security log, the following types of events are recorded:
l Account management event
l Account login event
l System event (Events that have impacts on the system
security and security log when user restart the system or
power off the system)
l Resource access event (Attempts to access the objects for
which user have no authority)
Supported NE Types
Supported NE Types
User can configure the exported contents, which comprise the following items:
l Root node: name and ID of topology type
l Link: name, link type, ID of the source device, and ID of the destination device
l Device: name, device type, ID address, vector coordinate, or latitude and longitude
vectors
l Sub-network: name, sub-network type, vector coordinate, or latitude and longitude
vectors
The topology object searching and locating function enables user to search for and locate
specified topology objects.
The search supports multiple dimensions, including object name and property. Property refers
to IP address, version number, supplier, and location information.
Fuzzy search by name or property is supported.
Supported NE Types
l CPU
l Memory
l Disk array
l Network port
l Battery
l Environment
When the hardware is faulty, the system generates alarms.
Enhancement
Support the collection of M2000 performance statistics data. After M2000 is started, it
automatically collects the performance statistics data. The detailed counters are as follows:
l Average load of the processor on the server
l Peak load of the processor on the server
l Average utilization of the memory on the server
l Peak utilization of the memory on the server
l Average utilization of disk partitions on the server
l Peak utilization of disk partitions on the server
l Average utilization of the database
l Peak utilization of the database
User can query M2000 performance statistics data according to the time segments. The query
results are displayed in tables.
Supported NE Types
AAA ASN-GW BS M2000
√
M2000 server and its managed NEs synchronize network time through the NTP/SNTP
protocols.
Benefits
This function ensures the time synchronization of the whole network elements including
M2000.
Description:
When the NTP server offered by a customer can not communicate with the NEs managed by
M2000, M2000 server can act as the NTP server of the intermediate layer. That is, M2000
server obtains reference time from the NTP server of upper layer and offers synchronization
signals to the NEs managed by M2000. In this way, the system keeps time consistency
between the managed NEs and the time source.
If an M2000 server serves as a secondary time source, customer should offer the NTP server
and the time source.
Supported NE Types
AAA ASN-GW BS M2000
√ √ √
The system supports backup and restoration of the system data. In the case of a system failure,
user can restore the backup data so that the system status is restored to the latest status.
The data that can be backed up is: system application software data, operating system data,
database software data, and other data.
The backup mediums are tapes and hard disks.
M2000 supports auto-backup and manual backup. The backup time and interval are
configurable.
In addition, M2000 also supports the full backup and the incremental backup.
Supported NE Types
AAA ASN-GW BS M2000
√
3 Optional Functions
M2000 provides the alarm CORBA interface that is compatible with the 3GPP R6
specifications.
Benefits
The OSS system can connect to M2000 through the alarm CORBA interface so that the
alarms of the whole network are handled in a centralized way and maintenance costs are
reduced.
Description
The alarm IRPs are alarm interfaces that are defined in the 3GPP specifications which
implement the CORBA solution defined in the 3GPP specifications.
The alarm CORBA interface implements all the required functions that are defined in the
3GPP specifications. It provides the following functions:
l Querying alarm lists, acknowledged alarms, unacknowledged alarms, and clearing
alarms through the alarm CORBA interface
l Sending in real time new alarms and notifications of alarm status changes through the
standard notification service
l Supporting the filter conditions that are defined in the 3GPP specifications
Supported NE Types
security CORBA interface provides open security interconnection mechanisms by using the
form of the CORBA interface.
The security CORBA interface provides the following functions:
l Querying all users
l Querying detailed user information
l Querying all user groups
l Creating users
l Deleting users
l Changing user passwords
l Modifying user validity
l Modify user attributes, including allowed user login period and user description.
l Allocating users to user groups
Supported NE Types
AAA ASN-GW BS M2000
√
l Supporting the parameters that are set through M2000 clients, including the export task
name, alarm name, alarm type, alarm level, task begin time, execution period, and file
format.
l Supporting the configuration of number of fields, field sequence, field names of the
alarm information in the export files.
Dependency:
The function of automatically uploading files depends on the function described in
WOFD-210200.
Supported NE Types
♦ Sequence types of counters in result files. The counters can be sorted by counter
name or by counter ID.
♦ Time modes of results. The time modes consist of NE time and server time of the
NMS.
♦ Whether time zones and DST information are included
l Exporting measurement results based on time segments.
l Setting the execution time for deleting expired export files.
l Supporting two modes for exporting supplementary data. The two modes are as follows:
exporting all data to rewrite original files; keeping the original file unchanged and
exporting supplementary data to another file
l Exporting result files according to the NEs or NE groups
l Supporting the export of performance data result files of M2000 itself.
Dependency
The function of automatically uploading files depends on the function described in
WOFD-210200.
Supported NE Types
The parameters can be set through M2000 clients: export task name, begin time of export
tasks, execution period of export tasks, involved NEs, and file formats.
Dependency
The function of automatically uploading files depends on the function described in
WOFD-210200.
Supported NE Types
When the software is downloaded to the standby area of NE, the current version is not
covered. The downloading progress is initiatively reported by the NE.
l Software activation
The active and standby areas are automatically switched.
l Software version query
l Downloads of the patches and data from the EMS to the NEs
The BS supports the following functions:
l Bulk NEs upgrade
l Software downloading from EMS to NE
When the software is downloaded to the standby area, the current version is not covered.
The downloading progress is initiatively reported by the NE.
l Software activation
The active and standby areas are automatically switched.
l Software version query.
Supported NE Types
AAA ASN-GW BS M2000
√ √
If M2000 sends alarms through emails, M2000 requires a specified mail server. Operator can
set the mail server to be connected and the communications parameters of emails on the
interface of M2000 clients.
Supported NE Types
AAA ASN-GW BS M2000
√ √ √ √
3.7 HA System(WOFD-130000)
WOFD-130100: Local HA System
Overview
M2000 provides complete local dual-node redundancy. The dual-node protection method is
used for the server node, disk array, network interface, and Ethernet switch so that all existing
single-node faults can be worked around.
Benefits
l Providing enhanced system maintenance
l Decreasing or eliminating system downtime caused by software or hardware faults
l Switching over active and standby servers automatically when faults occur
l Reducing the impact on services
Description
M2000 local HA system is comprised of two Sun servers. The Sun Cluster is used to manage
the servers. When M2000 HA system operates, one server is in the active state and the other
sever is in the standby state. When the active server is faulty or is not operational, the standby
server switches over automatically to work as the active server and ensures the smooth
operation of services. In this way, a secure and reliable network management system is
ensured.
Generally, all M2000 services at the application layer work on the active server to provide
services. The standby server monitors the operational status of the active server in real time
through heartbeat lines. When the active server does not work properly, M2000 system
switches over all the resources on the active server to the standby server so that M2000
system works properly.
The common application scenarios are as follows:
l When the active server is faulty and the standby server automatically takes over services
on the active server
When the standby server finds the faults on the active server through heartbeat lines, the
standby server takes over the resources on disk arrays, start the server of the Sybase
software, and start the processes of M2000 services to take over the entire network and to
provide services. The faults on the active server can be interrupted services or damaged
CPU.
l When user initiate the switchover between the active node and the standby node
manually
In some scenarios, user can perform the switchover between the active node and the
standby node manually to reduce the offline time of the server. For example, upgrade the
patches in the operating system of M2000 server; upgrade the server of the Sybase
software; data changes are not involved when the application programs of M2000 server
are upgraded.
l When the check for routine operation and maintenance is performed
When user check the operating conditions of the server node periodically, such as the
power-on and power-off of the server node, the CPU of the server node, and the network
operational status, user can make use of the switchover between the active node and the
standby node to reduce the possibility of service interruption and to improve the
reliability of the system.
The HA system provides the following functions:
l Redundancy
♦ By default, the disk array redundancy policy of RAID5+1 is provided to ensure the
reliability of data.
♦ Dual-plane networking design can be used to work around the single
point-of-failure at the network layer and to reduce the switchover between server
nodes because of the single point-of-failure.
l Automatic switchover
♦ When any of the following faults occurs in the active server, the active server
switches over to the standby server automatically:
n The CPU is faulty.
n The memory is faulty.
n The connection to disk arrays fails.
n Main boards are faulty.
n The communication between the network adapter of the active server and the
LAN switch is disrupted.
♦ When any of the following software faults occurs in the active server, the active
server switches over to the standby server automatically:
n The operating system of the active server does not work properly.
n The server of the database does not work properly.
n Non-repairable faults occur on the application programs of M2000 sever.
♦ When any of the following faults occurs on the network, the switchover between
the active and standby servers does not happen and the services on the active
server are not disrupted because M2000 HA system adopts the dual-plane
networking solution:
n A single network port or network cable is disconnected.
n A single heartbeat line is disconnected.
n A single Ethernet switch is faulty.
n A single disk array is faulty.
l Consistency
The same software and hardware configuration is adopted on the active server and the
standby server. In addition, disk arrays and databases are shared between the active
server and the standby server. In this case, when the switchover is performed between the
active server and the standby server, the consistency of data is ensured.
l Convenient management and maintenance
The Sun Cluster and Veritas Volume manager are adopted in M2000 HA system to
implement the features of the HA system and the management maintenance function of
the volume manager. Encapsulating scripts can implement the switchover between the
active server and the standby server.
For the Sun HA system, the maintenance of each component and module can be
performed through the Administrative Console.
Supported NE Types
3.8 Platform(WOFD-210000)
WOFD-210200 Automatically Uploading Files
Overview
M2000 can use FTP protocols to automatically upload the northbound configuration files,
inventory files, performance files, and alarm files to the specified FTP server.
Benefit
This function reduces the NMS development workload and reduces operators' costs on
developing the NMS.
l M2000 sets up and manages the transmission connection.
l Under the HA or server load sharing networking mode, the switchover between the
active node and the standby node does not affect the uploading of NMS files. Therefore,
the NMS need not care about the switchover between the active node and the standby
node.
Description
The service of automatic file uploading provides the following functions:
l Configuring the uploaded information about the server
On the client, user can choose to upload the northbound CM/FM/PM exported files and
set the address, directory, user name, and password of the server. M2000 creates a
directory on the server according to the setting.
l Supporting the file transmission in single connection or multi-connection mode
The types of northbound exported files comprises the configuration files, performance
files, and alarm files. M2000 can upload the files of each type to one server (single
connection) or multiple servers (multi-connection). By default, the single connection
mode is used. User can configure the uploading mode.
l Creating a directory on the uploading server
User can set the directory of the server to which the northbound files are uploaded. If the
directory does not exist, M2000 creates it according to the setting. M2000 creates the
same directory on the server according to the directory of M2000 northbound exported
files.
l Managing file transmission
On M2000 client, user can browse files to be transmitted and files failing to be
transmitted. In addition, user can delete files to be transmitted.
For the files failing to be transmitted, user can re-upload them according to the parameter
configuration:
User can configure the valid duration for re-uploading the files. By default, the duration
is 24 hours. The system gives up re-uploading the files that expire the valid duration.
By default, the system re-uploads the files for three times. The system records the files
that are re-uploaded more than three times to logs. User can modify the times or cancel
the limitation on the times. After user cancel the limitation on times, the system
determines the files according to the valid time of the re-uploaded files.
User can configure the time interval of re-uploading. The default time interval is one hour.
Supported NE Types