Documente Academic
Documente Profesional
Documente Cultură
V200R006
Operator Guide
Issue 04
Date 2008-05-20
Part Number 00366248
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are the property 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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Contents
3 Topology Management.............................................................................................................3-1
3.1 Basic Knowledge of Topology........................................................................................................................3-3
3.1.1 Topology Management Function...........................................................................................................3-3
3.1.2 Objects in a Topology............................................................................................................................3-3
3.2 Constructing a Physical Subnet.......................................................................................................................3-4
3.2.1 Designing the Physical Topology..........................................................................................................3-5
3.2.2 Setting the Topology Background..........................................................................................................3-5
3.2.3 Creating a Physical Subnet.....................................................................................................................3-6
3.2.4 Creating Physical NEs............................................................................................................................3-7
3.2.5 Creating a Virtual NE.............................................................................................................................3-7
3.2.6 Creating an IP Device............................................................................................................................3-7
3.2.7 Creating a Physical Link........................................................................................................................3-8
3.2.8 Creating a Virtual Link..........................................................................................................................3-9
3.2.9 Creating Physical Links in Batches......................................................................................................3-10
3.2.10 Setting an NE as a Transfer Server....................................................................................................3-11
3.3 Creating Physical NEs...................................................................................................................................3-12
3.3.1 NE Types..............................................................................................................................................3-12
4 Security Management................................................................................................................4-1
4.1 Basic Knowledge of Security Management....................................................................................................4-3
4.1.1 Centralized User Management...............................................................................................................4-3
4.1.2 User Authority........................................................................................................................................4-4
4.1.3 NE User..................................................................................................................................................4-5
4.1.4 Northbound User....................................................................................................................................4-5
4.1.5 Introduction to the FTPS........................................................................................................................4-6
4.2 Refreshing the Security Management Interface..............................................................................................4-6
4.3 Configuring the M2000...................................................................................................................................4-6
4.3.1 Setting the M2000 Security Policy.........................................................................................................4-7
4.3.2 Setting Single-User Mode......................................................................................................................4-9
4.3.3 Setting the System ACL.........................................................................................................................4-9
4.3.4 Setting FTPS Parameters......................................................................................................................4-10
4.4 Customizing MML Authority.......................................................................................................................4-10
4.4.1 Customizing an NE Type Command Group........................................................................................4-11
4.4.2 Customizing an NE Command Group.................................................................................................4-12
4.4.3 Setting Authority Rules for NE Types.................................................................................................4-13
4.4.4 Issuing Authority Rules for NE Types.................................................................................................4-14
4.4.5 Synchronizing NE Security Data.........................................................................................................4-16
4.5 Creating OM Users........................................................................................................................................4-16
4.5.1 Process for Creating OM Users............................................................................................................4-17
4.5.2 Creating an OM User Group................................................................................................................4-19
4.5.3 Set the Managed Domain for an OM User Group...............................................................................4-19
4.5.4 Assigning Operation Rights to an OM User Group.............................................................................4-19
4.5.5 Assigning Rights of New NEs to an OM User Group.........................................................................4-20
4.5.6 Granting MML Authority to an OM User Group................................................................................4-21
4.5.7 Creating an OM User Account.............................................................................................................4-22
5 Log Management........................................................................................................................5-1
5.1 Basic Knowledge of Log Management...........................................................................................................5-2
5.1.1 Log Types...............................................................................................................................................5-2
5.1.2 Log Templates........................................................................................................................................5-2
5.1.3 Procedure for Reporting NE Logs..........................................................................................................5-3
5.2 Synchronizing NE Logs..................................................................................................................................5-7
5.3 Querying Logs.................................................................................................................................................5-7
5.3.1 Creating a Log Query Template.............................................................................................................5-8
5.3.2 Querying Operation Logs.......................................................................................................................5-8
5.3.3 Querying System Logs...........................................................................................................................5-9
5.3.4 Querying Security Logs.......................................................................................................................5-10
5.3.5 Querying NE Operation Logs..............................................................................................................5-11
5.3.6 Querying Security Logs of the NEs.....................................................................................................5-12
5.3.7 Saving Log Query Results....................................................................................................................5-13
5.3.8 Printing Log Query Results..................................................................................................................5-14
5.4 Taking Statistics of Logs...............................................................................................................................5-14
5.4.1 Creating a Log Statistical Template.....................................................................................................5-15
5.4.2 Collecting Statistics on Operation Logs...............................................................................................5-15
5.4.3 Collecting Statistics on System Logs...................................................................................................5-16
5.4.4 Collecting Statistics on Security Logs.................................................................................................5-17
5.4.5 Taking Statistics of an NE Log............................................................................................................5-17
5.5 Managing Log Templates..............................................................................................................................5-18
5.5.1 Creating Log Templates.......................................................................................................................5-19
5.5.2 Modifying Log Template Condition....................................................................................................5-20
5.5.3 Deleting Log Template.........................................................................................................................5-21
5.6 References for Log Management Interfaces.................................................................................................5-21
5.6.1 Interface Description: Log Management..............................................................................................5-23
6 Performance Management........................................................................................................6-1
6.1 Basic Knowledge of Performance Management.............................................................................................6-3
6.1.1 Performance Measurement Counters.....................................................................................................6-3
6.1.2 Performance Measurement Objects........................................................................................................6-4
6.1.3 Measurement Function Sets and Subsets...............................................................................................6-5
6.1.4 Performance Measurement Periods........................................................................................................6-5
6.1.5 Performance Measurement Results........................................................................................................6-6
6.1.6 Performance Counter Thresholds...........................................................................................................6-6
6.1.7 Performance Measurement States..........................................................................................................6-7
6.1.8 Performance Measurement Procedure....................................................................................................6-7
6.2 Monitoring NE Performances.........................................................................................................................6-9
6.2.1 Setting a Performance Measurement Range for an NE........................................................................6-10
6.2.2 Managing Class 3 Object.....................................................................................................................6-11
6.2.3 Synchronizing NE Measurement Results.............................................................................................6-13
6.2.4 Subscribing to NE Measurement Results.............................................................................................6-13
6.2.5 Querying the Reliability of Measurement Results...............................................................................6-14
6.2.6 Querying Missing Measurement Results.............................................................................................6-14
6.2.7 Checking the Integrity of NE Results .................................................................................................6-15
6.2.8 Managing NE Measurement States......................................................................................................6-17
6.3 Querying Performance Measurement Results...............................................................................................6-18
6.3.1 Querying Results by Templates...........................................................................................................6-19
6.3.2 Querying Results by New Conditions..................................................................................................6-20
6.3.3 Query Results by Busy Hour................................................................................................................6-21
6.3.4 Re-querying Results.............................................................................................................................6-21
6.3.5 Setting Result Query Conditions..........................................................................................................6-22
8 Software Management..............................................................................................................8-1
8.1 Basic Knowledge of Software Management...................................................................................................8-2
8.1.1 NE Software...........................................................................................................................................8-2
8.1.2 Software Patch........................................................................................................................................8-2
8.1.3 Patch States............................................................................................................................................8-3
8.1.4 Software Management File Types..........................................................................................................8-4
8.1.5 RAN License..........................................................................................................................................8-6
8.1.6 Software Management Procedure..........................................................................................................8-7
8.2 Managing Software and Files..........................................................................................................................8-8
8.2.1 Viewing File Information on the Server................................................................................................8-9
8.2.2 Viewing File Information on an NE.......................................................................................................8-9
8.2.3 Transferring Files from the Server to the Client....................................................................................8-9
8.2.4 Transferring Files from the Server to an NE........................................................................................8-10
8.2.5 Transferring Files from the Client to the Server..................................................................................8-11
8.2.6 Transferring Files from an NE to the Server........................................................................................8-12
8.2.7 Managing Task List..............................................................................................................................8-13
8.2.8 Setting Parameters of File Transferring...............................................................................................8-15
8.2.9 Managing Voice Files.......................................................................................................................... 8-15
8.3 Upgrading NE Software and Patches............................................................................................................8-19
8.3.1 Managing a Scheduled Upgrade.......................................................................................................... 8-20
8.3.2 Upgrading the RNC Software and Patch..............................................................................................8-23
8.3.3 Upgrading the SGSN Software and Patch............................................................................................8-29
8.3.4 Upgrading the GGSN Software and Patch...........................................................................................8-35
8.3.5 Upgrading the MSC Server Software Patch.........................................................................................8-41
8.3.6 Upgrading the MGW Software and Patch............................................................................................8-46
8.3.7 Upgrading the AG Software and Patch................................................................................................8-47
8.3.8 Upgrading the ICS Software................................................................................................................8-53
8.3.9 Upgrading the NodeB Software and Patch.......................................................................................... 8-54
8.3.10 Upgrading the BSC Software and Patch............................................................................................8-55
8.3.11 Upgrading the BTS Software.............................................................................................................8-61
8.3.12 Upgrading the ASN-GW Software and Patch....................................................................................8-66
8.3.13 Monitoring the Procedure of Software Upgrade................................................................................8-72
8.4 Managing NE Licenses................................................................................................................................. 8-72
8.4.1 Managing RAN Licenses.....................................................................................................................8-73
8.4.2 Managing Licenses Between NEs........................................................................................................8-80
8.5 Querying Version Information on Software Installed on the Server.............................................................8-92
8.6 Reference for Software Management Interfaces...........................................................................................8-94
8.6.1 Interface Description: Software Browser.............................................................................................8-94
8.6.2 Interface Description: NE Licenses Management................................................................................8-96
8.6.3 Parameters for RNC Patch.................................................................................................................8-100
8.6.4 Parameters for Other NE Software and Patch....................................................................................8-101
9 Configuration Management.....................................................................................................9-1
9.1 Basic Knowledge of Configuration Management...........................................................................................9-3
9.1.1 Management Information Tree (MIT)....................................................................................................9-3
9.1.2 MML Commands...................................................................................................................................9-3
9.1.3 NE Resource States................................................................................................................................9-4
9.1.4 CBSS Device Panel................................................................................................................................9-5
9.2 Configuring NEs by MML Commands...........................................................................................................9-8
9.2.1 Executing an MML Command...............................................................................................................9-9
9.2.2 Viewing the Result of an MML Command............................................................................................9-9
9.2.3 Viewing Follow-Up Reports................................................................................................................9-10
9.2.4 Setting the Attributes of the "MML Command" Interface...................................................................9-11
9.2.5 Setting Report Redirection...................................................................................................................9-11
9.2.6 Setting Report Scroll Display...............................................................................................................9-12
9.2.7 Clearing History Commands................................................................................................................9-12
9.2.8 Saving the Result of an MML Command............................................................................................9-13
9.3 Viewing NE Configuration Information.......................................................................................................9-13
9.3.1 Viewing NE MIT Information.............................................................................................................9-14
9.3.2 Viewing NE Resource Reports............................................................................................................9-15
9.3.3 Viewing NE Link Reports....................................................................................................................9-15
9.3.4 Viewing NE Statistics Reports.............................................................................................................9-16
9.3.5 Viewing NE Reports............................................................................................................................9-16
9.4 Handling NE Configuration Data..................................................................................................................9-17
9.4.1 Manually Synchronizing NE Configuration Data................................................................................9-17
9.4.2 Manually Exporting NE Configuration Data.......................................................................................9-19
9.4.3 Importing the Configuration Files of PCU...........................................................................................9-20
9.4.4 Exporting the Configuration Files of PCU...........................................................................................9-20
9.5 Managing Inventory Data..............................................................................................................................9-21
9.5.1 Adding Inventory Data.........................................................................................................................9-22
9.5.2 Querying Inventory Data......................................................................................................................9-22
9.5.3 Importing Inventory Data.....................................................................................................................9-23
9.5.4 Modifying Inventory Data....................................................................................................................9-24
9.5.5 Manually Synchronizing Inventory Data.............................................................................................9-24
9.5.6 Manually Exporting Inventory Data....................................................................................................9-25
9.6 Viewing NE Resource Information...............................................................................................................9-26
9.6.1 Viewing NE Resource States...............................................................................................................9-26
10 Data Management..................................................................................................................10-1
10.1 Basic Knowledge of Data Management......................................................................................................10-2
10.1.1 NM Backup Data................................................................................................................................10-2
10.1.2 NE Backup Data.................................................................................................................................10-3
10.1.3 NM Log Data..................................................................................................................................... 10-3
10.2 NE Backup Data..........................................................................................................................................10-4
10.2.1 Manual NE Backup Data....................................................................................................................10-4
10.2.2 Viewing NE Backup File................................................................................................................... 10-5
10.2.3 Restoring NE Data............................................................................................................................. 10-5
10.3 NM Backup Data.........................................................................................................................................10-6
15 NE Commissioning................................................................................................................15-1
15.1 Managing NodeB Commissioning Tasks....................................................................................................15-2
15.1.1 NodeB Commissioning Items............................................................................................................ 15-2
15.1.2 Creating NodeB Commissioning Tasks.............................................................................................15-3
15.1.3 Viewing NodeB Commissioning Tasks.............................................................................................15-4
15.1.4 Modifying NodeB Commissioning Tasks..........................................................................................15-5
15.1.5 Deleting NodeB Commissioning Tasks.............................................................................................15-6
15.1.6 Starting/Stopping NodeB Commissioning Tasks...............................................................................15-6
15.2 Viewing the NodeB Commissioning Report...............................................................................................15-7
15.3 Reuploading the NodeB Configuration File................................................................................................15-7
15.4 Reference to the NE Commissioning Interface...........................................................................................15-8
15.4.1 Interface Description: Viewing NodeB Commissioning Tasks.........................................................15-8
17 FAQ...........................................................................................................................................17-1
17.1 Why Cannot I Log In to the Client?............................................................................................................17-3
17.1.1 Prompt "Login failed. Confirm that your user name and password are case sensitive and correct."
.......................................................................................................................................................................17-3
17.1.2 Prompt "Invalid user account." .........................................................................................................17-4
17.1.3 Prompt "Invalid login duration."........................................................................................................17-4
17.1.4 Prompt "Invalid password." ..............................................................................................................17-5
17.1.5 Prompt "The password has expired. Please change your password!"................................................17-5
17.1.6 Prompt "Maintenance Mode." ...........................................................................................................17-5
17.1.7 Prompt "The User Has Reached the Maximum Login Attempts. The User Account Has Been Locked,
and It Can Be Unlocked in 1 Minute."..........................................................................................................17-6
17.1.8 Prompt "The Server Doesn't Exist or Service Is Not Running."........................................................17-6
17.1.9 Prompt "Exceed Maximum Sessions."...............................................................................................17-7
17.1.10 Prompt "Loading Module Failed, System Will Exit."......................................................................17-7
17.1.11 Prompt "Failed to Log in to the Server after the Auto Client Upgrade or Running Exception"
.......................................................................................................................................................................17-7
17.2 Why Does the Client Abort?.......................................................................................................................17-8
17.3 Why Can't the Client Work?.......................................................................................................................17-8
17.4 Why Is the Client Interface Abnormal?......................................................................................................17-9
17.5 Why Is the Connection Between Client and Server Discontinuous?..........................................................17-9
17.6 Why Can't a Topology View Be Refreshed?............................................................................................17-10
17.7 Why Does the Automatic NodeB Search Fail?.........................................................................................17-11
17.8 Why Is the Name of a New Topology Object a Repeat One?...................................................................17-11
17.9 Why Does a Real-Time Print Delay?........................................................................................................17-11
17.10 Why Can't Alarm Notifications by SMS Be Received?..........................................................................17-12
17.11 How to select or unselect multiple nodes?..............................................................................................17-12
Index.................................................................................................................................................i-1
Figures
Tables
Purpose
This guide describes how to operate and maintain the network equipment.
Related Versions
The following table lists the product versions related to this document.
M2000 V200R006
Intended Audience
The intended audiences of this document are:
l Network administrator
l Shift operator
Update History
04(2008-05-20)
Fourth formal release.
Compared with V200R006 03(2008-03-15), the following content is modified.
Context Description
03(2008-03-15)
Third formal release.
Compared with V200R006 02(2008-01-08), the following content is modified.
Context Description
02(2008-01-08)
Second formal release.
Compared with V200R006 01(2007-10-17), the following content is modified.
Context Description
Topology Management Add the contents related to IMS, C02 and WiMAX.
Software Management Add the contents related to IMS, C02 and WiMAX.
01(2007-10-17)
This is the first formal release.
Organization
1 Getting Started
You can know the operation GUI of the M2000 client, how to log in to, log out of, lock, and
unlock the client, how to set the broadcasting message, and how to modify the user password
and customize the display style of the client.
2 Network Monitoring
On the M2000 client, you can monitor the alarms on the network, real-time NE performances,
the RAN network, and operational status of the NM system. In this way, you can detect network
faults in time and then perform the related operations.
3 Topology Management
Topology management offers the function of constructing and managing the topology structure
of the whole network to display the networking situation and running status of the equipment.
You can query and monitor the entire network operation in real time through the topology view.
4 Security Management
This describes how to guarantee the security of the M2000. The M2000 security management
manages the user and the user's rights. Through the security management, the security of the
M2000 is guaranteed.
5 Log Management
Log management involves the management of user logs, NE logs, and system logs. This function
enables you to query logs and collect statistics of logs, thus helps monitoring and analyzing
operational status of the system and troubleshooting.
6 Performance Management
Through the performance measurement, you can measure and observe the security, the running
status and the signaling connection status of the equipment, also you can measure and observe
the utilization of the user and system resources. This function provides reliable data support for
the measurement, designing and operation management of the communication
network.M2000The M2000 can measure the performance of multiple NEs. When an NE is
successfully set up and communicates normally with the M2000, the NE automatically reports
the measurement results of key performance counters to M2000 for data query and analysis
based on a certain period.
The M2000 provides the function of performance report management. You can set the query
conditions of system reports and custom reports on the GUI. The M2000 can display the queried
performance report on the report query interface. By analyzing the report data, you can obtain
the information about the performance of each NE. You can also manage KPIs, such as create,
modify, and delete KPIs on the KPI management interface.
8 Software Management
9 Configuration Management
The M2000 provides the NE centralized management function. On the M2000 client, you can
run the MML command or start the LMT of an NE to configure the NE. The NEs of class B and
class C do not support the configuration of MML commands.
10 Data Management
M2000The M2000 provides the function of managing NE data and NM data. The management
of NM data includes manually or periodically backing up NM data, viewing NM backup files.
The management of NE data includes manually or periodically backing up NE data, viewing
NE backup files, and restoring NE data. The M2000 also provides the function of collecting NM
log files.
11 Dual-Homing and LN Domain Management
This part describes the basic functions provided by dual-homing and local network domain
management.
12 MSC Pool Management
The 3GPP 23.236 defines the concept of the MSC Pool. That is, by using the Iu-Flex technology,
one RNC can share multiple MSC servers. Based on a specified load balancing algorithm, the
user services are distributed to different MSC Servers and the services of one user are managed
by the same MSC Server. Thus the MSC server resources can be shared. You can configure,
monitor, and maintain the MSC Pool on the M2000 client.
13 CDMA Pool Management
This describes the CDMA pool, which is comprised of multiple MSCes. The CBSC of the access
network connects to all MSCes in the pool. If the network is deployed as a CDMA pool, user
services are distributed to MSCes on the basis of the capacity proportion of each MSCe. In this
way, you can balance the traffic of MSCe in the pool in different regions on weekdays or
weekends. Therefore, operators calculate the device investment on the basis of the maximum
traffic of the city rather than that of each region. This helps operators to optimize network
capacity and reduce the investment. You can configure data, monitor the performance, and
maintain the CDMA pool network through the M2000 client.
14 Integrated Task Management
The M2000 provides the function of integrated management of scheduled tasks. Thus, you can
browse information such as the task status and the progress. You can also create, modify, and
delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and
save task result files to the client.
15 NE Commissioning
The NE commissioning refers to the process that the M2000 automatically commissions the
selected NEs. The NE commissioning includes the following items: automatically detecting and
configuring the devices, automatically checking the performance of new base station, and
automatically generating the commissioning report. You can monitor the commissioning process
on the M2000 client and determine the network performance by analyzing the generated
commissioning report. Currently, only the NodeB commissioning can be performed.
16 NE Maintenance Enhanced Management
The M2000 provides the enhanced maintenance management for some NEs to facilitate servicing
these NEs. The NE enhanced maintenance management involves device management, trace
management, monitoring management, and real-time performance monitoring. You can start
this function only after the related components are upgraded on the client.
17 FAQ
This part describes the typical faults of the M2000 client, analyzes the possible causes, and
provides the solution.
Conventions
1. Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol Description
TIP Indicates a tip that may help you solve a problem or save your
time.
2. General Conventions
Convention Description
3. Command Conventions
Convention Description
Convention Description
4. GUI Conventions
Convention Description
> Multi-level menus are in boldface and separated by the ">" signs.
For example,choose File > Create > Folder .
5. Keyboard Operation
Convention Description
Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the two
keys should be pressed in turn.
6. Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the
pointer.
Double-click Press the primary mouse button twice continuously and quickly
without moving the pointer.
Drag Press and hold the primary mouse button and move the pointer
to a certain position.
1 Getting Started
You can know the operation GUI of the M2000 client, how to log in to, log out of, lock, and
unlock the client, how to set the broadcasting message, and how to modify the user password
and customize the display style of the client.
the LMT proxy, through which you can connect the LMT to the NEs. This function is applicable
when you start the LMT through the M2000 rather than starting the LMT manually.
1.10 Setting the LMT Prompt
You can determine whether to display a dialog box, which prompts the M2000 user when NE
user logs in or exits the NE LMT.
1.11 Sending Broadcasting Messages
This section describes how to send broadcast messages from the client.
1.12 Viewing NM License Information
You can view information about all function control items in the licence control items configured
in the M2000 server.
1.13 Viewing NE Partitioning
This topic descirbes how to view the NE partitioning. If the M2000 server applies the multi-
server load-sharing system, different NEs can be managed by different service partitions. On
the client, you can view different NE partitioning.
1.14 Downloading NE Mediation Data to the M2000 Client
When the NE version on the client is inconsistent with that on the server, you can manually
download the NE mediation file to the M2000 client to reach the consistency. The dynamic NE
upgrade refers to upgrading dynamically the NE configuration files on the M2000 Client. When
detecting that the NE version changes, the M2000 server obtains the new version configuration
files from the NE. You can upgrade manually these files on the M2000 Client.
1.15 Managing the Exported Files in the Server
In the File Browser window, you can view the information that are exported from the server
according to the path to the exported file.
1.16 Managing User-Defined Object Groups
You can group objects of the same type into an object group. In this way, you can perform the
same operation on all the objects in this object group. The M2000 allows you to create, view,
and modify the information about a user-defined object group.
1.17 Reference for M2000 Client Interfaces
This describes the M2000 client interface and related parameters, which helps you perform the
related operations on the client.
Prerequisite
Before login, ensure that the M2000 client and server are connected normally, and the server
works correctly.
Context
l Except the Administrator, if you have not logged in to M2000 for more than 30 days, your
user account becomes invalid automatically. Before you can use the account again, the
account need be set to valid by a user who has the Administrator rights.
l If you do not log in during the preset period after the previous login, the M2000 disables
or delete the user account.
l If a new user account has not logged in to the M2000 server, M2000 does not delete or
invalidate it.
Procedure
Step 1 Start the M2000 client from the start menu.
Step 3 In the Server List dialog box, configure the M2000 server.
1. Click Add.
2. In the Add Server Information dialog box, enter the host name and IP address of the
server.
NOTE
1. The current client checks whether another client is being upgraded. If a client is being
upgraded, the login is not allowed.
2. Initialize the communication connection between the client and the server.
3. Check whether the daemon service is running properly.
4. Obtain the copyright notice on the server and display the contents.
5. Check whether the client version is consistent with the server version. It the two versions
are inconsistent, display the inconsistent messages or prompt the user to upgrade.
6. Invoke the login interface on the server. Check whether the user account and password are
correct.
7. Check whether the user password expires according to the security policy. If the password
expires, it must be changed for a successful login.
8. Check whether the login is within the allowable time period according to the security policy.
9. After the user account passes the authentication, the client loads each software module.
l If the user name and the password are correct, the Loading dialog box is displayed, indicating
the loading progress.
l If the user name or password is wrong, the Information dialog box is displayed, saying Login
failed. Please enter the correct user name and password.”
l If the password is to expire in the specified days, the system prompts you to change the
password before the expiration date.
l If the license is to expire in the specified days, the system notifies you of the expiration date.
----End
Related References
1.17.3 Parameters for Logging In to the M2000 Server
Context
l To ensure security, when you do not need to perform any operations on the client, you can
log out the user account or exit the M2000 client.
l This operation does not end the client program. After logout, the Login dialog box is
displayed. You can enter the proper information in the dialog box to log in to the M2000
again.
Procedure
Step 1 Choose System > Logout.
----End
Context
l To ensure security, when you do not need to do any operations on the client, exit the
M2000 client or log out the user account. If you do not need to do any operations for a
while, you can 1.5.2 Locking Client Manuallyor 1.5.1 Locking the Client
Automatically.
l This operation will end the client program. If you want to do some operations on the client,
restart the M2000 client.
Procedure
Step 1 Choose System > Exit.
Step 2 In the Confirmation dialog box, click OK.
----End
Context
After the M2000 server is upgraded, you can perform this operation to check whether the version
of the client match that of the server. If the versions do not match, you can upgrade the client.
Procedure
Step 1 Choose Help > Check For Upgrades to check whether the client version matches the server
version.
l When the versions match, the system prompts that the client version matches the server
version and the client does not need to be upgraded. Click OK.
l When the version do not match, the system prompts that the versions do not match and the
client needs to be upgraded, and it asks you whether to start the upgrade immediately. Click
OK to continue with the next step.
Step 2 In the Update Wizard: Update Applications window, click Continue. The upgrade progress
is displayed.
Step 3 In the Update Wizard: Update Applications window, click Finish.
----End
Procedure
Step 1 Choose System > Preferences.
Step 2 In the System Setting dialog box, in the navigation tree on the left, select Upgrade. In the
Time Interval drop-down list, select the interval for update checking.
----End
Context
NOTE
l You can check whether the versions on the client and the server are consistent. For details, refer to
1.1.4 Checking Whether the Client Need Upgrade.
l The client can be correctly upgraded only when the software version of the server has the same version
sequence with and greater than that of the client. The same version sequence means that in the
software versions, that is, product name+VxxxRxxxCxxBxxy[SPxx], the numbers after B are the
same.
Only when the software version of the client is of the same version sequence as that of the server
and the software version of the server is later than the client version, the client can be correctly
updated. The software version is in the format of Name of the product + VxxxRxxxCxxBxxy
[SPxx]. For instance, if the software version of the server is V200R005C01B066SP01, the
software version of the client can be updated only when it is of the V200R005C01B066.
According to the flag in the version response, the client determines whether the upgrade tool is
required.
Procedure
Step 1 Start the client. Select the server and then click Login.
NOTE
The M2000 automatically compares the versions of the client and server. If the versions are not consistent,
the system displays a dialog box, prompting you to upgrade the client.
The client exits and the Upgrade Wizard dialog box is displayed.
The client downloads the client programs from the corresponding directories on the server.
----End
Context
l When using the default password policy, the user password cannot be less than six
characters.
l The password of Admin cannot be less than eight characters.
l To ensure the security of the M2000, you are recommended to change the user password
periodically.
Procedure
Step 1 Choose Security > Change Password.
Step 2 In the Change Password dialog box, in the Old Password text box, enter the password of the
login user.
Step 3 In the Change Password dialog box, in the New Password text box, enter the new password.
Step 4 In the Change Password dialog box, in the Confirm Password text box, enter the new password
again.
Step 5 Click OK.
----End
For Menu
For any menu followed by the asterisk * (* represents a letter or a number), you can press Alt
+* to choose the root menu and press * to choose a sub-menu.
For Button
l For any button followed by the asterisk * (* represents a letter or a number), you can press
Alt+* instead of clicking the button.
l When a dialog box is open and a dot square is on a button, this button is the default button.
If the dot square is not on any button, OK is the default button.
l If you click Apply in a window, the settings in the window take effect and the window is
not closed. You can continue with other operations.
l If you click OK in a window, the settings in the window take effect and the window is
closed.
l When a dot square is on a button, you can press Enter or space bar instead of clicking the
button.
l When the button that gets the dot square does not support the Enter operation and you
press Enter, the default button in that dialog box is clicked.
Restore down (when the service window in the public window Ctrl+F5
is maximized)
Maximize the window (when the service window in the public Ctrl+F10
window is restored)
NOTE
The public window area refers to the area below the toolbar on the M2000 client.
Procedure
Step 1 Choose System > Preferences.
Step 2 From the navigation tree on the left of the System Setting window, select Output Window,
and then set relevant parameters.
NOTE
l Right-click in the output pane and choose Save As to save the output information as an *.txt file.
l Right-click in the output pane and choose Clear to clear all the displayed output information.
l Right-click in the output pane and choose Select All, and then right-click again and choose Copy to copy
all the displayed output information to the clipboard.
l Right-click in the output window and choose Auto Scroll. The output information is set to scroll
automatically. Right-click in the output window again and choose Auto Scroll, the auto scroll is cancelled.
l Right-click in the output window and choose Parameter Setting. The Output Window pane is displayed
in the System Setting window.
l Right-click in the output window and choose Find. Enter the keywords in the Find what dialog box.
----End
Related References
1.17.5 Parameters for Output GUI Information
Context
The settings take effect only after you log in to the M2000 client again.
Procedure
Step 1 Choose System > Preferences.
Step 3 In Alarm Status, select the alarm status you want to display.
Step 4 Select the alarm status for which you want to adjust the display sequence. Click Up or Down to
adjust the display sequence in the topology view.
----End
Procedure
Step 1 Choose System > Customize Toolbar.
Step 2 In the Customize Toolbar dialog box, deselect the checkboxed under Toolbar Groups, for
example, System or Fault as desired.
l The new dialog box consists of two sections: Usable Tools and Customize Tools. All the buttons in
Customize Tools are displayed on the toolbar, and the buttons in Usable Tools are not displayed on the
toolbar.
l Click Advanced again. The new dialog box is hidden.
l Click Reset to restore the toolbar so that you can reset it.
Step 4 In the Toolbar Buttons dialog box, set the buttons you want to display on the toolbar.
l In the Usable Tools group box, select the buttons you want to display. Click to
move the buttons to Customize Tools.
l In the Customize Tools group box, select the buttons you do not want to display. Click
to move the buttons to Usable Tools.
----End
Related References
1.17.4 Tool Buttons
Prerequisite
You have logged in to the M2000 client.
Context
NOTE
The executable file triggered by the customizing menu is a program outside the M2000 and this program
is owned by the client.
Procedure
Step 1 Choose Custom Menu > Menu Setting, the Custom Menu Setting window is displayed.
Step 2 Under the Custom Menu node, right-click Add Menu Group.
Step 3 In the displayed Menu Attribute Modifying dialog box, enter the name of the menu group.
NOTE
Step 4 Right-click the menu group node,and then choose Add Menu from the shortcut menu.
Step 5 In the displayed Menu Attribute Modifying dialog box, set the menu information.
1. In Menu Name,enter the menu name.
2. In File Path, click . In the displayed Open dialog box, select the executable file to
be triggered.
3. If you need to enter the parameters for the executable file to be triggered, enter these
parameters in the Parameters field.
For example, according to the LMT configuration, the startup parameter of the LMT is -u
"username" -p "password" -o "NE name" -pip "proxyip" -nip "neip" -closeall
"true" -t "bamid". You can enter the startup parameters in the Parameters field. After
you customize the menu, you can log in to the LMT of the NE through the custom menu.
NOTE
Step 7 Click OK, and then the Custom Menu Setting dialog box is closed.
----End
Postrequisite
Choose the related menu below the Custom Menu . Start the executable file that is set on the
M2000 client.
Context
l After you set the time format, you need to log in to the server again for the settings to take
effect.
l You can preview the time format in Appearance Example.
Procedure
Step 1 Choose System > Preferences.
Step 2 From the navigation tree on the left of the System Setting window, expand the Region
Setting node and select Time.
Step 3 In the Time Settings group box, set the time format.
NOTE
The time format is displayed in Appearance Example.
----End
Related References
1.17.7 Parameters for Setting the Time Style
Context
The settings take effect after you log in to the client again.
Procedure
Step 1 Choose System > Preferences.
----End
Context
l The settings take effect after you log in to the client again.
l You can preview the new date format in Appearance Example.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the navigation tree on the left of the System Setting window, expand the Region Setting
node and select Date.
Step 3 In the Date Settings group box, set the date format.
NOTE
l Date Separator: symbol to separate the date. There are three symbols for you to select: "/", "-", and ".". The
default is "-".
l Date Format: display format of the date. It can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/yyyy".
The default is "yyyy/MM/dd".
l The date display effect that you set is displayed in Appearance Example.
----End
Context
l The settings take effect after you log in to the client again.
l Modifications to the region number settings may adjust the number display and sequence
effect. The display effect is displayed in the Positive number text box and Negative
number text box.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the Region Settings dialog box, click the Number tab, and set Digits of Decimal
Fraction, Number Separator, and Start with 0.
NOTE
l Digits of Decimal Fraction: digits of decimal fraction. The default is two digits, and the value ranges from
0 to 3, 2 by default.
l Number Separator: whether to use the comma (,) to group the integer part of numbers. The default is blank
space. You can choose the blank space or comma ",".
l Start with 0: whether to add 0 before the decimal point. The default is to add a 0.
----End
Context
The setting has effects on the display mode of performance measurement results. The
performance measurement data is automatically displayed according to the defined metrology.
Procedure
Step 1 Choose System > Metrology Setting.
The Metrology Setting dialog box is displayed.
Step 2 Select IMP or MET.
Step 3 Click OK to save the setting.
Click Cancel to cancel the setting.
NOTE
After the modification, the setting takes effect on the client only.
----End
Context
Common option settings are bound to the client. In other words, the parameters set on the same
client apply to all its users.
Procedure
Step 1 Choose Performance > Preference to view the System Setting dialog box.
Step 2 Set the parameters.
Step 3 Click Apply or OK.
----End
Related References
1.17.8 Parameters for Setting Common Options for Performance Management
1.17.2 Interface Description: Common Options for Performance Management
When you do not need to perform any operations on the M2000 client, you can lock the client
manually to prevent illegal operations.
Procedure
Step 1 Choose System > Preferences.
Step 2 From the navigation tree on the left of the System Setting window, select Locking Interval.
Step 3 Select Automatically locked check box. In the minutes later, this client will be automatically
locked. text box, enter the lock time.
NOTE
l Clear Automatically locked check box. The function of auto lock is disabled.
l minutes later, this client will be automatically locked.: Set the time to start the auto lock. The value ranges
from 1 minute to 35000 minutes. The default is 3 minutes.
----End
Procedure
You can lock the client in two ways:
l Choose System > Lock Terminal.
----End
Context
l If you unlock your own account, the M2000 becomes operable after it is unlocked.
l If your user account is in the Administrators user group and you unlock a user account of
someone else, that account is logged out after it is unlocked.
Procedure
Step 1 When the client is locked, press Ctrl+Alt+U .
Step 2 In the Unlock dialog box, enter the user name and the password, and then click OK.
----End
Prerequisite
l You are the admin user.
l No admin users have logged in to other clients.
Context
l Single-user mode: applicable for maintenance. Only one user is allowed to log in and to
establish the session.
l Mulit-user mode: applicable for normal operation. Multiple users are allowed to log in to
the system at the same time.
Procedure
Step 1 Choose System > Preferences. The System Setting dialog box is displayed.
Step 2 In the navigation tree, select the System Login Mode node. Choose the system running mode
in the right pane.
Step 4 Enter the delay time for mode switching. Enter the delay time for mode switching in the Set
Switch Delay dialog box.
CAUTION
The single-user mode allows only one user to log in and to establish the session. Therefore, after
the change of the running mode, the current client is still active, while other online clients that
are not authorized to change the mode are forced to exit. You need to set the switch delay time
based on actual situations so that clients have time for preparations.
The system counts down the mode switching and informs other online clients.
----End
Context
l You can use the sound file of the M2000 or others.
l Only the sound files of the Wav type in the PCM format are supported. The Microsoft
ADPCM type is not supported.
l You can set the delay time of the alarm sound in $iManagerM2000Client\style\defaultstyle
\conf\sf\ConnectionConfig.properties on the M2000 client. The unit of the delay time is
second. If the connection between the client and the network is not recovered within the
preset delay time, the sound box plays the corresponding alarm sound.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the System Setting dialog box, from the navigation tree on the left, select Disconnection
Sound.
Step 3 In the Disconnection Sound group box, choose Enable, and then click . In the Open dialog
box, select a sound file, and then click Open.
----End
Context
l The following NEs support this function: RNC, NodeB, SGSN, GGSN80, MSC Server,
MGW, HLR, CG, IWF, SG7000, IP Clock Serve, AG, and TGW. After the M2000 is
installed with the mediation layer of the related NE, you can set the LMT proxy for this
NE.
l For NodeB, the M2000 automatically starts the LMT proxy. You are not allowed to change
the LMT proxy setting. For other NEs that support the LMT proxy, the M2000 does not
start the LMT proxy by default. You, however, can start or stop the LMT proxy.
l The parameters that you set are saved on the server in real time and overwrite the previous
setting. When other users log in to the client, the client automatically reads and uses the
setting saved on the server.
l If a user changes the setting, the changed setting is stored on the server. It takes effect to
the clients that log in later rather than those who have logged in.
Procedure
Step 1 Choose System > Preferences to open the System Setting dialog box.
Step 2 Click Proxy Service Setting in the left navigation tree on the System Setting dialog box.
Step 3 Select the types of NE maintenance stations on the Proxy Service Setting tab page. When these
NE maintenance stations are started, the M2000 proxy enables them to connect to the NEs.
----End
Procedure
Step 1 Choose System > LMT Prompt Setting. The LMT Prompt Setting dialog box is displayed.
Step 2 Select or deselect the check box Prompt when LMT user login or logout.
----End
Context
l Broadcast messages are only sent to the clients that log in to the server normally.
l A client can receive the broadcast messages sent by itself. A prompt is given in the output
window.
Procedure
Step 1 Choose System > Broadcast Message.
Step 2 In the Broadcast Message dialog box, in the Message entry box, enter the message content.
NOTE
l The system automatically adds line feeds according to the length of broadcast messages.
----End
Context
The license keys are divided into resource keys and function keys. For the resource keys, the
system controls the number of the items, such as the frequency of the CBSC. For the function
keys, the system controls if the function can be performed by the user. Only authorized users
can use the function keys.
Procedure
Step 1 Choose Help > About.
The About dialog box is displayed.
----End
Related References
1.17.6 Parameters for Viewing NM License Information
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Select Configuration > Query NE SubArea, the Query NE Subarea window is displayed.
----End
Related References
1.17.9 Parameters for the NE Partitioning Information
Context
The macro file provides the collection of all commands defined by NEs. From this file, you can
know what commands are supported by the version and the meaning of each parameter.
Procedure
Step 1 Choose Help > Online Update to view a progress bar through which the client queries the new
version file from the server.
Step 2 If new version files exist, the server displays the Update Available dialog box to show the NE
type and version number of the files and prompts you to upgrade them.
NOTE
Step 3 In Update Available, click Yes to upgrade the files. Click No to cancel the upgrade.
A percentage is displayed in the upgrade progression bar to show the upgrade progression.
----End
Procedure
Step 1 Choose Maintenance > File Browser. The File Browser window is displayed.
You can view the exported timing tasks in the server in the File Browser window.
Step 2 In the File Browser window, view the exported results according to the name of the exported
file.
----End
By default, the types of the NEs and object groups that support this function are: MSC Server
(MSCServer NE Group, Office Group), and RNC (RNC NE Group, Cell Group). You can add
or delete the types of NEs and object groups by modifying the configuration file on the server.
Related Tasks
1.16.2 Adding a User-Defined Object Group
1.16.3 Modifying a User-Defined Object Group
1.16.4 Viewing User-Defined Object Groups
Related References
1.17.10 Parameters for User-Defined Object Groups
Prerequisite
l You have logged in to the M2000 client.
l You are authorized with the relevant operation privileges.
Procedure
Step 1 Choose Performance > Object Set Management . The Object Set Management window is
displayed.
Step 3 Select the type of the object group to be created, set the attributes, and then click Next.
For detailed information about the parameters, refer to 1.17.10 Parameters for User-Defined
Object Groups.
Step 4 Select the object scope and create type, and then click Next.
NOTE
If the type of the object group is NE group, the corresponding scope of the object group can only be
Network.
By Manual 1. In Objects, select the objects to be added to the object group. Click
to add them to Selected Objects.
2. Click Next and modify the name and remarks of the object group.
AUTO Select the attribute of the object group in the drop-down list.
----End
Related Concepts
1.16.1 User-Defined Object Groups
Related References
1.17.10 Parameters for User-Defined Object Groups
Prerequisite
l You have logged in to the M2000 client.
l You are authorized with the relevant operation privileges.
l A user-defined object group is available.
Procedure
Step 1 Choose Performance > Object Set Management . The Object Set Management window is
displayed.
Step 2 In the navigation tree, select the node of the object group to be modified. In the right pane, select
the object group to be modified.
Step 3 Click Modify, or right-click the object group and choose Modify on the shortcut menu.
CAUTION
An object group whose create type is AUTO cannot be modified manually.
Step 4 Perform the related operations based on the type of the user-defined object group.
For detailed information about the parameters, refer to 1.17.10 Parameters for User-Defined
Object Groups.
Step 5 Click Finish.
Step 6 In the displayed dialog box that shows the operation result, click OK.
----End
Related Concepts
1.16.1 User-Defined Object Groups
Related References
1.17.10 Parameters for User-Defined Object Groups
Prerequisite
l You have logged in to the M2000 client.
l A user-defined object group is available.
Procedure
Step 1 Choose Performance > Object Set Management . The Object Set Management window is
displayed.
Step 2 In the navigation tree, select the Network node. In the right pane, view the information about
the user-defined object group, such as name, NE type, object group type, scope, creator, and
create type.
NOTE
l Select a user-defined object group in the right pane and click Information. Then you can view the
details of its objects.
l Select a user-defined object group in the right pane and click Delete to delete it. Alternatively, you can
right-click it and choose Delete on the shortcut menu.
----End
Related Concepts
1.16.1 User-Defined Object Groups
Related References
1.17.10 Parameters for User-Defined Object Groups
This topic describes the related parameters in the Query NE Subarea dialog box. You can refer
to the these parameters when you check the NE partitioning information.
1.17.10 Parameters for User-Defined Object Groups
This describes the parameters related to user-defined object groups. You can refer to this part
when adding or modifying user-defined object groups.
Overview
Figure 1-2 shows the GUI after you log in to the system. For details of Figure 1-2, see Table
1-1.
(1) System output The system output window displays the information
window such as the system operation logs and the system
alarms. The time displayed is the time of the client.
The log, fault, and security information is provided by
the server. Therefore, the displayed time is the time of
the server.
(2) Menu bar The menu bar shows the main menu of the system.
(3) Status bar The status bar displays the current status information
of the system, such as the current user and the IP
address of the connected server.
(4) Toolbar The toolbar shows the shortcut icons for key operation
tasks.
Menu Bar
The menu bar shows the main menu of the system. It is designed according to the main functions
of the M2000 to facilitate your operation.
Table 1-2 describes the main menus on the interface and corresponding functions.
Help Help provides the online help of the M2000 client. The menu
options are Help > Help Topics, Help > Check For
Upgrades, Help > About, and Help > Online Update.
Resource Management The menu is displayed after you install the resource
management tool on the client.
The M2000 resource management tool provides the function
of allocating interprovincial circuit resources of softswitch
tandem, thus satisfying the operation and maintenance
requirements of carriers. The resource management tool
includes Standard Data Management , Real Data
Manager and Task Manager .
Toolbar
The toolbar of the M2000 client provides access to some common operations. You can rapidly
open the corresponding windows or perform the corresponding operations by clicking the icons.
The M2000 also allows you to customize the buttons on the toolbar.
l System management tool buttons
Table 1-3 shows the icons and functions of system management tool buttons.
Status Bar
The status bar is located at the bottom of the interface. It displays the status information of the
system, such as the current user and the IP address of the connected server. The status information
is updated in real time.
l Connection status: displays the status of the connection to the server. When the server is
disconnected, the indicator blinks and the system displays a prompt box showing that the
server being connected. shows the indicator.
l Logo: the logo of Huawei Technologies Co., Ltd., that is, .
Organization Tree
Figure 1-3 shows the tab of organization tree.
Status Table
Figure 1-4 shows the tab of status table.
Time Parameter
Figure 1-5 shows the tab of time parameter.
Others
Figure 1-6 shows the tab of others.
Related Tasks
1.4.8 Setting Common Options for Performance Management
Parameters
Name Description Settings
Related Tasks
1.1.1 Logging In to theM2000 Server
Exit Description:
To exit the M2000.
Logout Description:
To log out the current user.
Zoom In Description:
To zoom in on the topology objects. You can
click this icon eight times effectively based on
the default object size.
Magnifier Description:
To magnify the topology objects in the selected
rectangle area to adjust the view to the perfect
size. You can zoom in four times based on the
default size.
Print Description:
To set the print properties to print the topology
view.
Preview Description:
To preview the print result of the topology view.
You can also print by using this icon.
Overview Description:
To display the overview. You can have a full
view of the topology structure through the
overview.
Search Description:
To search topology objects. It supports the
wildcard character *, and the characters entered
for the search must be less than 65 characters,
and cannot be less than 0.
Refresh Description:
To refresh the topology view, and obtain the
latest data from the M2000 server.
Legend/Filter/ Description:
Attribute The Legend/Filter/Attribute pane is displayed
on the right.
Related Tasks
1.4.3 Setting the Toolbar
Parameters
Name Description Settings
Related Tasks
1.4.1 Setting Output Information
Parameters
Parameter Description
Message For the resource keys, the number of the authorized resources
are displayed.
Related Tasks
1.12 Viewing NM License Information
Parameters
Name Description Settings
NOTE
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC, and MRF do not support multi-zone management
and the DST.
Related Tasks
1.4.5.1 Setting the Time Format of the Client
Parameter Description
Parameter Value Description
Orga Organization Object type, In the organization style of the object type,
nizat Function subset right-click an object type in the
ion organization tree and choose View the
tree Function Subset. In this situation, the
organization tree are organized by function
subsets and only the function subsets of the
object type are displayed. In the
organization style of the function subset,
right-click function subsets in the
organization tree and choose Filter with
Object Type,In this situation, only the
function subsets that map the object type are
displayed. After you deselect the options,
all the function subsets are displayed.
Switchable Yes, No -
Statu Default status All, Set, Measuring, Measurement status table displays the
s Error, Suspended, measurement statuses you have selected.
table Not set
Time Default time Integers from 1 to 336 Includes integrity query, specific query,
para range missing result, and synchronize result.
mete
r Result - Defaults from 00:00 to 23:59.
segment
Default 5 minutes, 15 -
measurement minutes, 30 minutes,
period 60 minutes, 24 hours
Related Tasks
1.4.8 Setting Common Options for Performance Management
Parameter Description
Parameter Description
Parameter Description
Related Tasks
1.13 Viewing NE Partitioning
Parameter Description
Parameter Description
Object Group Scope Network Indicates that the objects are selected
from the entire network
Parameter Description
Parameter Description
Related Concepts
1.16.1 User-Defined Object Groups
Related Tasks
1.16.2 Adding a User-Defined Object Group
1.16.3 Modifying a User-Defined Object Group
1.16.4 Viewing User-Defined Object Groups
2 Network Monitoring
On the M2000 client, you can monitor the alarms on the network, real-time NE performances,
the RAN network, and operational status of the NM system. In this way, you can detect network
faults in time and then perform the related operations.
Huawei. On the M2000 client, you can monitor the operational status of the NM system, such
as the status information about the memory, CPU, hard disks, database, processes, and services.
In addition, you can set the alarm threshold of the server.
2.8 Reference for Network Monitoring Interfaces
This describes the parameters used on the network monitoring interface, such as alarm
monitoring, performance monitoring, RAN network monitoring, and NM system monitoring.
l Alarm display
Alarm display involves alarm board output and alarm query.
– Alarm board output
The alarm board collects statistics on the alarms of the managed objects by alarm levels
and states with templates. Working as the monitoring panel, it provides the fault status
of the entire system. For the description of the alarm board, see 2.3.2.2 Introduction
to the Alarm Board.
– Alarm query
Alarm query is to query the current fault alarms, history fault alarms, event alarms,
filtered fault alarms, and filtered event alarms. The M2000 can display fault alarms and
event alarms in a window by different alarm status.
l Alarm statistics
The M2000 can collect statistics on fault alarms and event alarms according to the preset
statistical conditions. The statistical conditions include alarm name, alarm level, alarm type,
alarm raised time, and alarm status, and can be combinations of these items.
Alarm Acknowledgement
The M2000 supports manual and automatic acknowledgement of alarms.
Alarm Synchronization
The M2000 supports alarm synchronization with NEs. Through a client, you can manually
synchronize the alarms between the M2000 and an NE.
Alarm Redefinition
You can change the alarm levels displayed on the client and highlight the required alarms by
redefinition.
The M2000 supports the level redefinition of the alarms on the NEs. You can reset an alarm
level by alarm name.
The M2000 supports alarm correlation analysis. It also supports correlation analysis between
multiple NEs.
Alarm Levels
The alarm levels are described as follows:
l Critical
The device or resource may be no longer available. The fault must be removed immediately.
l Major
The Quality of Service(QoS) of the device or resource decreases greatly. Proper measures
must be taken to recover the service.
l Minor
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.
l Warning
The QoS of the device or resource may be affected. Proper measures must be taken.
1. Alarm status
l The status of an event alarm involves: unacknowledged and acknowledged.
l The status of a fault alarm involves: unacknowledged and uncleared, acknowledged and
uncleared, unacknowledged and cleared, and acknowledged and cleared.
2. Condition for changing alarm status
A certain condition triggers the change of the alarm status.
l Clear an alarm
When the condition that causes a fault alarm is removed, the device recovers to its
normal state, the device reports a cleared alarm to the M2000. The source alarm are
cleared. You can also clear an alarm manually.
l Acknowledge an alarm
If an alarm is acknowledged, it is processed.
You can unacknowledge an acknowledged alarm.
3. Alarm status conversion
Figure 2-1 shows the model of the fault alarm status conversion.
NOTE
The acknowledged and cleared alarms are history alarms. The fault alarms in other status are current
alarms. That is, the unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and
cleared fault alarms are current alarms.
Table 2-2 gives two examples to help you understand the differences between fault alarms and
event alarms.
Power system alarm A power system alarm is raised by the power supply.
Signaling system alarm A signaling system alarm is an alarm about the signaling
system, such as No. 7 signaling.
Trunk system alarm A trunk system alarm is an alarm about the trunk system,
such as E1, STM-1 optical or electrical relay.
Running system alarm A running system alarm is an alarm about the M2000
running.
Name Description
Processing error alarm Processing error alarms are alarms about other
exceptions that are not described here.
Flow Chart
Figure 2-2 shows the alarm reporting procedure.
Flow Description
The following is the description of the flow in Figure 2-2.
1. Reporting a alarm
When a device raises an alarm, it sends the alarm to the M2000 by the Man-Machine
Language(MML) protocol or Simple Network Management Protocol(SNMP).
2. Masking alarms
The M2000 masks alarms based on the mask condition set by users. The alarms that match
the condition are masked.
3. Redefining the alarm level
The M2000 redefines the alarm levels based on the redefinition conditions set by users.
4. Analyzing alarm correlation
The M2000 analyzes the alarm correlation based on the correlation rule and shield the
repetitive or non-root alarms.
5. Saving alarms
After processing, the M2000 writes the alarms into the alarm database.
6. Notifying the user of alarms
The M2000 sends the alarm notifications to users based on the alarm notification rules set
by users.
The alarm auto-triggering script is a kind of the shell script, and thus is provided by the user.
Correct script files are also guaranteed by the user. The M2000 does not provide functions such
as editing and proofreading for the script files.
NOTE
shell script: indicates the program that is edited using the programing language UNIX shell. The shell script
can be used to execute the complicated tasks, which cannot be executed using the command of the UNIX
system itself.
Context
You can make this settings in the following windows:
l Current Fault Alarms
l Event Alarms
l Masked Fault Alarms
l Masked Event Alarms
l History Fault Alarms
l Browse Current Fault Alarms by Status
l Browse Current Event Alarms by Status
Procedure
Step 1 Open the 2.2.7 Querying Alarms window.
The Configure Columns dialog box is displayed. Available column and Selected column
respectively list all the available and selected columns.
Step 3 Click an icon and perform the corresponding operation as show in the table below.
Icon Description
Step 4 In Selected column, select a column and then click Up or Down to adjust the display sequence.
Step 5 Choose Effective for the current window and new window of the same type or Effective for
the current pane only.
Effective for the current window and This setting is effective for the alarm windows
new windows of the same type of the same type.
Effective for the current pane only This setting is effective only for the current
alarm window.
----End
Related References
2.8.10 Parameters for Setting Columns in an Alarm Interface
Prerequisite
l You have logged in to the M2000 client.
l Uncleared fault alarms exist.
Context
l The M2000 supports automatic alarm synchronization.
l The AHR does not support automatic, periodic, and automatic synchronization of alarms.
Procedure
Step 1 In the result window after you open 2.2.7.1 Querying Current Fault Alarms or 2.2.7.6
Displaying Fault Alarms by Status, right-click the fault alarms to be synchronized.
Step 2 From the shortcut menu, select Synchronize.
----End
Related References
2.8.15 Parameters for Selecting Alarm Objects
Context
The topology location is applicable to only one alarm. If multiple alarms are chosen, even if they
are raised by the same network element, the Topology Location item is disabled.
Procedure
l In the window for browsing the alarm query or statistical result, right-click an alarm record
and choose Topology Location.
The cursor is located to the NE that raises the alarm.
l In the lower window of the topology view, right-click an alarm and choose Topology
Location .
The cursor is located to the NE that raises the alarm.
----End
Context
A cleared alarm exists with a fault alarm. When a device is faulty, a fault alarm is reported to
the M2000 server. After the fault is rectified, the cleared alarm is sent to the M2000 server,
notifying that the alarm is cleared.
After a fault alarm is acknowledged and cleared, it becomes a history alarm. The system dumps
the alarm in the history fault alarm database for future reference.
The following NEs do not support this function: HLR36, PCU35, PCU33, PCU6000, tMSC,
iMSC, rMSC, MSC, BSC, GT800BSC, BTS, and AHR.
Procedure
Step 1 In the 2.2.7.1 Querying Current Fault Alarms or 2.2.7.6 Displaying Fault Alarms by
Status window, right-click the alarm to be cleared.
A cleared alarm cannot be cleared again.
Step 2 Select Clear from the from the shortcut menu. Change the state of the alarm to cleared.
----End
Procedure
Step 1 Choose Topology > Main Topology.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
Context
The M2000 monitors all the alarms by default.
Procedure
Step 1 Choose Monitor > Alarm Real-time Monitor.
----End
Related References
2.8.11 Parameters for Monitoring Alarms in Real Time
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
2.8.14 Parameters for Selecting NE for Query
Procedure
Step 1 Choose Monitor > Current Fault Alarms, or click on the toolbar.
Step 2 In the Filter dialog box, set the alarm query conditions.
Step 3 Click OK. The query result is displayed in the browse window.
NOTE
l Click Save As to save the query result in a file. The format of the file can be *.txt, *.html, or *.csv. The
default is *.csv.
l Click Print. In the Print dialog box, set the print parameters and then print the query result.
Step 5 Optional: Right-click an alarm in the browse window and choose Synchronize .
The alarm data on the M2000 keep consistent with that on the NE.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 9 Optional: Choose one or more alarms in the browse window, right-click and then choose Send
Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail
address or SMS number. Click OK.
NOTE
l You can select up to 10 alarms for remote notification. Otherwise, Send Notification is disabled.
l In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000
server.
Step 10 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 11 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 12 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
2.8.15 Parameters for Selecting Alarm Objects
2.8.16 Parameters for Selecting Alarm Name
Procedure
Step 1 Choose Monitor > History Fault Alarms .
Step 2 In the Filter dialog box, set the alarm query conditions.
Step 3 Click OK. The query result is displayed in the browse window.
NOTE
l Click Save As to save the query result in a file. The format of the file can be *.txt, *.html, or *.csv. The
default is *.csv.
l Click Print. In the Print dialog box, set the print parameters and then print the query result.
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 7 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 8 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 9 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
Procedure
Step 2 In the Filter dialog box, set the alarm query conditions.
Step 3 Click OK. The query result is displayed in the browse window.
NOTE
l Click Save As to save the query result in a file. The format of the file can be *.txt, *.html, or *.csv. The
default is *.csv.
l Click Print. In the Print dialog box, set the print parameters and then print the query result.
Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose Send
Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail
address or SMS number. Click OK.
NOTE
l You can select up to 10 alarms for remote notification. Otherwise, Send Notification is disabled.
l In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000
server.
Step 9 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 10 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 11 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
2.8.15 Parameters for Selecting Alarm Objects
Context
The masked alarm is the alarm that is masked by the alarm correlation rules. It includes masked
fault alarms and masked event alarms.
Procedure
Step 1 Choose Monitor > Masked Fault Alarms.
Step 2 In the Filter dialog box, set the alarm query conditions.
Step 3 Click OK. The query result is displayed in the browse window.
NOTE
l Click Save As to save the query result in a file. The format of the file can be *.txt, *.html, or *.csv. The
default is *.csv.
l Click Print. In the Print dialog box, set the print parameters and then print the query result.
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 7 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 8 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 9 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
Context
The masked alarm is the alarm that is masked by the alarm correlation rules. It includes masked
fault alarms and masked event alarms.
Procedure
Step 1 Choose Monitor > Masked Event Alarms.
Step 2 In the Filter dialog box, set the alarm query conditions.
Step 3 Click OK. The query result is displayed in the browse window.
NOTE
l Click Save As to save the query result in a file. The format of the file can be *.txt, *.html, or *.csv. The
default is *.csv.
l Click Print. In the Print dialog box, set the print parameters and then print the query result.
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 7 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 8 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 9 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
Context
NOTE
Up to 1000 fault alarms of each state can be displayed.
Procedure
Step 1 Choose Monitor > Browse Current Fault Alarms By Status , or click on the toolbar.
Step 2 In the Filter dialog box, set the parameters for the fault alarm display. Click OK.
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Send
Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail
address or SMS number. Click OK.
NOTE
l You can select up to 10 alarms for remote notification. Otherwise, Send Notification is disabled.
l In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000
server.
Step 8 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 9 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 10 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
Step 11 Optional: Click the number buttons 1, 2, 3, and 4 to open or close the panes corresponding to
the numbers.
----End
Context
NOTE
Up to 1000 event alarms of each state can be displayed.
Procedure
Step 1 Choose Monitor > Browse Event Alarms By Status.
Step 2 In the Filter dialog box, set the parameters for the event alarm display. Click OK.
Step 4 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 5 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Send
Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail
address or SMS number. Click OK.
NOTE
l You can select up to 10 alarms for remote notification. Otherwise, Send Notification is disabled.
l In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000
server.
Step 8 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 9 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 10 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Context
l The number of autoloading templates cannot exceed 5.
l In the template navigation tree, the default icon of a template is , the icon of a default
template is , and the icon of an autoloading template is . For the template that is default
and autoloading, the icon is .
Procedure
Step 1 In the alarm query window, click Template, choose New.
Step 2 In the Enter The Template Name dialog box, set the template name. Click Set default
template or Set auto load template as required, and then click OK.
Step 3 In the Filter dialog box, set the alarm query conditions.
----End
Related References
2.8.13 Parameters for Setting Alarm Statistics
Context
The M2000 supports up to 400,000 statistical results. Because the count of the statistical results
is the permutation result of all the statistical items and the statistical results with 0 are not
displayed on the client, the displayed statistical results are less than the total statistical results.
Procedure
Step 1 Choose Monitor > Fault Alarm Statistics.
Step 2 In the Statistic Filter dialog box, set the fault alarm statistical conditions, and then click OK.
NOTE
The statistical results are displayed on the Table and Pie tabs.
l Table: The results are listed in a table.
l Pie: Different statistic items are displayed in different pie charts. Click the tab of an item name to view its
pie chart.
Step 3 Optional: In the statistical result window, click Save As to save the result in a file.
NOTE
l Click the Table tab. The file can be saved in the *.txt, *.html, or *.csv format.
NOTE
When a CSV file contains more than 256 lines, it cannot be opened by Excel. Use a text editing tool such
as UltraEdit or notepad to open the file.
l Click the Pie tab. The file is saved in the *.jpg format.
Step 4 Optional: In the statistical result window, click the Table tab. Click Print to print the statistical
result.
----End
Related References
2.8.16 Parameters for Selecting Alarm Name
Context
The M2000 supports up to 400,000 statistical results. Because the count of the statistical results
is the permutation result of all the statistical items and the statistical results with 0 are not
displayed on the client, the displayed statistical results are less than the total statistical results.
Procedure
Step 1 ChooseMonitor > Event Alarm Statistics.
Step 2 In the Statistic Filter dialog box, set the event alarm statistical conditions, and then click OK.
NOTE
The statistical results are displayed on the Table and Pie tabs.
l Table: The results are listed in a table.
l Pie: Different statistic items are displayed in different pie charts. Click the tab of an item name to view its
pie chart.
Step 3 Optional: In the statistical result window, click Save As to save the result in a file.
NOTE
l Click the Table tab. The file can be saved in the *.txt, *.html, or *.csv format.
NOTE
When a CSV file contains more than 256 lines, it cannot be opened by Excel. Use a text editing tool such
as UltraEdit or notepad to open the file.
l Click the Pie tab. The file is saved in the *.jpg format.
Step 4 Optional: In the statistical result window, click the Table tab. Click Print to print the statistical
result.
----End
Context
l The number of autoloading templates cannot exceed 5.
l In the template navigation tree, the default icon of a template is , the icon of a default
template is , and the icon of an autoloading template is . For the template that is default
and autoloading, the icon is .
l The M2000 supports up to 400,000 statistical results. Because the count of the statistical
results is the permutation result of all the statistical items and the statistical results with 0
are not displayed on the client, the displayed statistical results are less than the total
statistical results.
Procedure
Step 1 Choose Monitor > Fault Alarm Statistics or Monitor > Event Alarm Statistics.
Step 2 In the Statistic Filter window, click Cancel.
Step 3 In the statistic window, click Template, and then select New.
Step 4 In the Enter The Template Name dialog box, enter the template name. Select Set Default
Template or Set auto load template as required, and then click OK.
Step 5 In the Statistic Filter dialog box, set the alarm statistical conditions, and then click OK.
Step 6 In the Confirmation dialog box, click Yes.
----End
Prerequisite
The Alarm Browse, Query and Statistics window is open and the results of the alarm query
or statistics are displayed.
Context
l You can save all or selected alarm information in the Current Fault Alarms tab, the Event
Alarms tab, the History Fault Alarms, the Masked Fault Alarms tab, and the Masked
Event Alarms tab.
l You can save only selected alarm information in the Browse Current Fault Alarms by
Status tab and the Browse Current Event Alarms by Status tab.
l You can save the statistic results of all alarm records.
Procedure
Step 1 In the 2.2.7 Querying Alarms or 2.2.8 Collecting Alarm Statistics window, open the Save
dialog box.
Selected alarm records Right-click the alarm information to be saved and choose Save
Selected Record(s) on the shortcut menu.
NOTE
You can press Ctrl or Shift to select multiple alarm records at the same time.
Step 3 Specify the file name. The name can comprise letters, numbers, and characters. The file name,
however, cannot contain the following characters: * " ? / | < >
The Saving ... dialog box is displayed. This dialog box indicates the saving progress.
----End
Prerequisite
The alarm query or statistics interface is open and displays the required alarm information.
Context
l You can print all or selected alarm information in the Current Fault Alarms tab, the Event
Alarms tab, the History Fault Alarms tab, the Masked Fault Alarms tab, and the Masked
Event Alarms tab.
l You can print the statistic results of all alarm records.
Procedure
Step 1 In the 2.2.7 Querying Alarms or 2.2.8 Collecting Alarm Statistics window, open the Print
dialog box.
Selected alarm records Right-click the alarm information to be printed and choose Print
Selected Record(s) on the shortcut menu.
NOTE
You can press Ctrl or Shift to select multiple alarm records at the same time.
Step 2 On the General tab, specify the printing service, scope, and copies.
TIP
If you select Print To File on the General tab, the Print To File dialog box is displayed. Specify the file
name and path in the dialog box, and then click OK to save the alarm information to a specific file.
Step 3 On the Page Setup tab, specify the paper attributes, such as the size, source, orientation, and
margins.
Step 4 On the Appearance tab, specify the printing attributes, such as the color appearance, quality,
sides, and job attributes.
The Printing... dialog box is displayed. This dialog box indicates the saving progress.
----End
To remove alarm-related faults, you find causes of the alarms and then clear the causes to ensure
the proper operation of the system. To remove alarm-related faults, you many need relevant
personnel to assist you.
2.2.11.6 Clearing Alarms
You can manually clear the alarms that cannot be cleared automatically or the alarms that have
been acknowledged. After a fault alarm is cleared, the M2000 considers that the fault that causes
the alarm is removed.
2.2.11.7 Recording Alarm Handling Experience
You can record the alarm handling experience in the knowledge base. When a similar alarm
occurs, you can refer to the experience in the database to handle it.
2.2.11.8 Exporting Maintenance Experience
When you record the alarm maintenance experience in a server, you can export the information
from the alarm knowledge base to back up or synchronize the information to another server.
2.2.11.9 Importing Maintenance Experience
You can import the alarm maintenance experience from a server to the alarm knowledge base,
to back up or synchronize the information to another server.
2.2.11.10 Example: Alarm Handling
This section provides an example on how to handle the issue of insufficient disk space. It
describes the procedure and method for handling alarms. You can know the basic procedure and
operation of alarm handling from this example.
Flow Chart
Figure 2-3 shows the fault handling procedure.
Procedure
The fault handling procedure, as shown in Figure 2-3, is described inTable 2-4.
1 Receive an alarm After you receive an alarm, start the alarm handling
procedure. To ensure that the operators can receive
notifications in time when a fault occurs, you need to set
alarm notification methods on the M2000.
2 View the alarm details This is where you start. View the alarm details, including
the alarm location information, alarm help, and alarm
maintenance experience.
3 Acknowledge the To avoid others handling the same alarm, you need to
alarm acknowledge it. When you acknowledge an alarm, it
indicates that the alarm is being processed.
4 Collect fault By locating an alarm, you can query the fault information
information and analyze the causes of the fault.
5 Analyze the causes of Analyze the causes of the fault according to the fault
the alarm information.
6 Work out the fault Work out the fault handling scheme according to the alarm
handling scheme details, device manuals, network status, and maintenance
experience.
7 Carry out the fault Carry out the fault handling scheme to remove the fault.
handling scheme
8 Clear the alarm When the fault is removed, the alarm is cleared, and the
M2000 receives the cleared alarm.
9 Check the handling After the fault is removed, check the handling results.
results
10 Record the After you complete the fault handling, record the
maintenance maintenance experience.
experience
Procedure
Step 1 Choose Monitor > Current Fault Alarms, or click on the toolbar.
Step 2 In the Filter dialog box, set the alarm query conditions.
Step 3 Click OK. The query result is displayed in the browse window.
NOTE
l Click Save As to save the query result in a file. The format of the file can be *.txt, *.html, or *.csv. The
default is *.csv.
l Click Print. In the Print dialog box, set the print parameters and then print the query result.
Step 5 Optional: Right-click an alarm in the browse window and choose Synchronize .
The alarm data on the M2000 keep consistent with that on the NE.
Step 6 Optional: Choose one or more alarms in the browse window, right-click and then choose
Configure Columns. In the Configure Columns dialog box, select the columns to be displayed
in the browse window and the area where the column settings take effect. Click OK.
The alarms are displayed according to your settings.
Step 7 Optional: Choose one or more alarms in the browse window, right-click and then choose Mix
Sorting. In the Mix Sorting dialog box, set the keywords, and then select Ascending or
Descending. Click OK.
The alarms are displayed according to the keywords you set.
Step 8 Optional: Choose one or more alarms in the browse window, right-click and then choose
Display Time Mode > Server Time or Display Time Mode > NE Time.
The alarms are displayed according to the time mode you set.
Step 9 Optional: Choose one or more alarms in the browse window, right-click and then choose Send
Notification > Email or Send Notification > SMS. In the displayed dialog box, set the E-mail
address or SMS number. Click OK.
NOTE
l You can select up to 10 alarms for remote notification. Otherwise, Send Notification is disabled.
l In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time of the M2000
server.
Step 10 Optional: Right-click an alarm in the browse window and choose Topology Location .
The cursor is located to the NE that raises the alarm.
Step 11 Optional: Right-click an alarm in the browse window and choose Details , or double-click the
alarm.
In the displayed dialog box, you can view the name, location, and level of the alarm.
Step 12 Optional: Right-click an alarm in the browse window and choose Masked Alarm .
l In the displayed dialog box, you can click Previous to view the masked alarm of the
previous alarm.
l In the displayed dialog box, you can click Next to view the masked alarm of the next alarm.
In the displayed dialog box, you can view the masked alarm of the alarm.
----End
Related References
2.8.12 Parameters for Setting Alarm Query/Browse
2.8.15 Parameters for Selecting Alarm Objects
2.8.16 Parameters for Selecting Alarm Name
Procedure
Step 1 In the window for browsing alarm query result, double-click an alarm or right-click an alarm
and choose Detail Information.
Step 2 In the Detail Information window, click Modify below the Alarm Experience text box. Enter
the alarm maintenance experience. Then Click Add or Modify below the Alarm Memo text
box. Enter the remarks. Then click Close.
----End
Related References
2.8.20 Parameters for Viewing Alarm Details
Acknowledging Alarms
Alarm acknowledgement allows you to check if an alarm has been handled. You can easily
distinguish between the alarms you have handled and those you have not handled. You can then
take proper measures to handle them.
Procedure
Step 1 In the window for browsing the alarm query result, right-click an alarm and choose
Acknowledge .
NOTE
If the alarm you click is acknowledged, Acknowledge in the shortcut menu is disabled, and Unacknowledge
is enabled.
After an alarm is acknowledged, you can click Unacknowledge to recover the alarm state to unacknowledged.
----End
Prerequisite
You have obtained alarm-related information. For details, refer to 2.2.11.3 Viewing Alarm
Details.
Context
l For fault alarms, you need to remove related alarms based on the causes of the alarms.
When multiple fault alarms exist at the same time, you need to determine the priority of
these alarms according to the alarm severity and the operational status of the current
network.
l For event alarms, you need only to inform the occurrence of the alarms and does not need
to remove the faults.
Procedure
Step 1 Check the online help of an alarm to know alarm explanation and treatment suggestions.
You can select the Alarm Details tab in the Alarm Details dialog box. Click More
information to view the online help associated with the alarm.
You can choose the Knowledge and Explanation tab in the Alarm Details dialog box to view
the information in the Knowledge frame.
Step 3 Contact relevant personnel to remove alarm-related faults according to treatment suggestions
and recorded fault treatment experience.
----End
Postrequisite
After fault alarms are removed, the system automatically sets the state of the alarm to be
Cleared.
Clearing Alarms
You can manually clear the alarms that cannot be cleared automatically or the alarms that have
been acknowledged. After a fault alarm is cleared, the M2000 considers that the fault that causes
the alarm is removed.
Context
l One cleared alarm corresponds to one fault alarm. When the device is faulty, the fault alarm
is reported to the M2000. After the fault is removed, the device sends the notification to
the M2000, and the fault alarm is cleared automatically.
l The acknowledged and cleared fault alarms are history fault alarms. They are saved in the
database of the history fault alarm for further query.
Procedure
Step 1 In the window for browsing the alarm query result, right-click a fault alarm and choose Clear
.
NOTE
If you right-click the fault alarm that has been cleared, the Clear menu is disabled.
----End
Context
The initial knowledge base is empty.
Procedure
Step 1 ChooseMonitor > Settings > Explain and Experience.
Step 2 In the Search by name text box, enter the key word of an alarm name.
In the Alarm names navigation tree, alarm names with the key word are listed.
Step 3 In the Alarm names navigation tree, choose an alarm name, ClickModify.
NOTE
You can choose one or more options from Group by NE Type, Group by Alarm Type, Group by Alarm
Level, and Group by Category. This helps you to locate an alarm name more quickly in the navigation tree.
Step 4 In the Modify Experience group box, enter the alarm handling experience.
Step 5 Click OK.
----End
Related References
2.8.17 Parameters for the Alarm Explanation and Maintenance Experience
Context
Do not modify the knowledge base file on the disk manually.
Procedure
Step 1 ChooseMonitor > Settings > Explain and Experience.
Step 2 In the Explain and Experience window, in the Search by name text box, enter the keywords
of the alarm name.
The Alarm names navigation tree displays the alarm names that contain the keywords.
Step 3 From the Alarm names navigation tree, select the name of the alarm whose maintenance
experience you want to export, and then click Import.
You can also select one or more from the Group by NE type, Group by alarm type, Group
by alarm level, and Group by category to sort the alarms. In the Alarm names navigation tree,
select the name of the alarm whose maintenance experience you want to export.
Step 4 In the Export Experience dialog box, select the path of the target file, and then select Export
All or Export by NE Type. Click Export.
NOTE
The maintenance experience is saved in the XML or CSV file in the specified path.
----End
Context
Do not modify the knowledge base file on the disk manually.
Procedure
Step 1 ChooseMonitor > Settings > Explain and Experience.
Step 2 In the Explain and Experience window, in the Search by name text box, enter the keywords
of the alarm name.
The Alarm names navigation tree displays the alarm names that contain the keywords.
Step 3 From the Alarm names navigation tree, select the names of the alarms to be imported to the
explanation and experience database. Click Import.
You can also select one or more of Group by NE type, Group by alarm type, Group by alarm
level, and Group by category to sort the alarms. From the Alarm names navigation tree, select
the names of the alarms to be imported to the explanation and experience database.
Step 4 In the Import Experience dialog box, select the target file, and then select Add or Update.
Click Import.
NOTE
Only the files in the XML format can be imported to the explanation and experience database.
----End
Background
Administrator A finds that the M2000 reports a new alarm.
Operation Guide
Based on the Alarm Handling Procedure, administrator A has taken the following actions:
1. Receive the alarm notification.
On the client, choose Monitor > Current Fault Alarms to browse the alarm list. An
uncleared alarm with Identity(ID) 34 is found. The M2000 server has insufficient disk
space.
2. View the alarm details.
Double-click this alarm to view its details.
3. Acknowledge the alarm.
The results indicate that the fault is removed. Now, the alarm can be acknowledged. In the
alarm list, right-click this alarm and choose Acknowledge . In the Configuration dialog
box, click OK.
4. Work out the alarm handling method.
According to the fault management tips, maintenance experience, and the running status
of the M2000, administrator A decides to delete the redundant files and back up the exported
data on other disks.
5. Remove the relevant fault.
Delete the redundant files of the M2000. Back up the export files to other disks. Then delete
the exported data from the source disk. The M2000 server then has more available disk
space.
6. Check the handling results.
On the client, choose Monitor > Current Fault Alarms to browse the alarm list. The
status of the alarm is changed from uncleared to cleared.
7. Record the alarm handling experience.
On the client, choose Monitor > Settings > Explain and Experience. In the Explain and
Experience tab. Search for the alarm and edit its maintenance experience.
Procedure
Step 1 Choose System > Preferences.
Step 2 Expand Alarm Local Terminal Settings , and then select New Fault/Event Alarms.
Step 3 In the New Fault/Event Alarms group box, click Display on top or Display at the bottom.
Step 4 Click OK.
The new fault/event alarm is displayed at the beginning or end of the alarm list.
----End
If you are not concerned about some alarms, you can set the M2000 to filter them. For
example, when the equipment is under maintenance or test, mass alarms are raised. Such
alarms can be filtered.
2. Alarm auto acknowledgement
After the related faults are removed, you do not have to manually acknowledge the cleared
alarms. You can set the auto acknowledgement condition so that the M2000 can
acknowledge alarms based on the condition automatically.
3. Alarm level redefinition
You can redefine the alarm levels on the M2000 according to the actual requirements.
l Alarm browser
The alarm browser is a window on the client. You can browse alarms in real time by using
the browser.
The M2000 also enables you to query specified alarms, such as event alarms, history alarms,
or current alarms.
l Topology view
The topology view is a view that shows the device distribution on the client. The device
icons in the view show the alarm status through their colors and status. You can observe
the icons to know whether an alarm occurs to a device and the level and status of the alarm.
l Alarm speaker
The alarm speaker notifies users of the current alarm by playing a sound. To use the alarm
speaker, connect it to the M2000 server or client and set the parameters. You can know
new alarms and their levels by using the alarm speaker.
l Alarm board
The alarm board is a board on the client. It displays the alarm status through flashing
indicators and statistics. You can monitor the alarms in the network through this board to
know alarm level and related statistics.
l Alarm box
An alarm box is a hardware that prompts alarms in audio and video mode. An alarm box
consists of an amplifier and four indicators. It connects to the M2000 client by a serial port
cable. When an alarm is raised, the corresponding indicator is lighted and an alarm sound
is played.
l Alarm remote notification
You can set a mail server or wireless modem for remote notification. The M2000 notifies
the maintenance personnel of alarms by email or SMS.
Alarm Board
The minimized icon of the alarm board is displayed on the right of the toolbar. See Figure
2-4.
Choose Monitor > Display Alarm Board, or in the M2000 client GUI, click to open the
alarm board, as shown in Figure 2-5.
l The four color indicators on the alarm board represent critical, major, monitor, and warning
alarms. The numbers under the indicators are the counts of alarms.
l The alarm board is a window that runs on the client and displays the alarm statistics in real
time. If a new alarm is raised, the relative indicator flashes and the alarm sound is played.
The alarm statistics on the alarm board is refreshed in real time.
l Both the alarm box and alarm board notify users of new alarms in audio and visual mode.
The alarm box is hardware. It cannot display the alarm statistics. You can set the condition
to filter the alarms sent to the alarm box on the client. Compared with the alarm box, the
alarm board is a window on the client. You can click Add at the bottom of the Alarm
Board dialog box to bind the fault template and event template with the alarm board. You
cannot set the filter conditions for it. It can display the alarm statistics based on the alarm
status and levels according to templates in real time.
Procedure
Step 2 In the Alarm Board dialog box, click Option. Set auto display for the alarm board or auto flash
for the alarm lamp.
Step 4 In the Add dialog box, select the event template or the current fault template. Then click Add.
NOTE
l If no fault template or event template is created, click New Event Template or New Fault Template to
create a template.
l To delete the event template, in the Event Alarms window, click Template, and then click Delete. In the
Delete dialog box, select the template that you want to delete, and then click Delete.
l To delete the current fault template, in the Current Fault Alarms window, click Template, and then click
Delete . In the Delete dialog box, select the template that you want to delete, and then click Delete.
The alarm information on the bound template is added on the alarm board.
----End
Context
NOTE
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC, and MRF do not support this function.
Procedure
Step 1 Choose Monitor > Alarm Box Manager.
Step 2 In the Alarm Box Settings dialog box, configure the audio and visual settings and
communication parameters for the alarm box.
----End
Related References
2.8.31 Parameters for Setting the Alarm Box
Context
l You can use the sound file of the M2000 or others.
l Only the sound files of the Wav type in the PCM format are supported. The Microsoft
ADPCM type is not supported.
l By default, the sound files of the four alarm levels are located in style/defaultstyle/conf/
alarmclient/ in the M2000 client installation folder. The file names are Critical.wav,
Major.wav, Minor.wav and Warning.wav.
l To recover the alarm sound to the default settings, click the Sound tab and click Default.
In the Preference dialog box, click Default to restore the alarm sound to the default.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the System Setting dialog box, from the navigation tree on the left, select Sound.
1. In the Sound group box, click the path of the sound file, and then . In the Sound
Configuration dialog box, select a sound file, and then click OK.
2. In Sound Time(S), enter the play duration of the sound. Click on the right to
listen to the sound.
NOTE
l The play duration is from 0 to 600, and the unit is second. 0 indicates that the play time is unlimited.
l If the alarm indicator on the alarm board is set to flash when a new alarm is raised, when a new alarm
is raised, the alarm indicator that corresponds to the level of this alarm flashes for the preset duration.
If alarms of different levels are raised, only the alarm indicator that corresponds to the highest alarm
level flashes.
l If the duration of the alarm sound of an alarm level is set to 0, when an alarm of this level is raised,
the alarm indicator keeps flashing until the alarm is cleared.
----End
Context
l After you complete the settings, the alarm icon in the topology view, the alarm record you
query, and the alarm indicator on the alarm board are shown in the specified color.
l To recover the default color, click the Sound and Color tab and then click Default. Click
Default in the System Setting dialog box to restore the alarm color to the default.
Procedure
Step 1 ChooseSystem > Preferences.
Step 2 In the System Setting dialog box, from the navigation tree on the left, select Color.
Step 3 In the Color group box, double-click the button next to an alarm level to select the alarm color.
----End
Context
l The unacknowledged event alarm is highlighted when the interval between the local time
on the client and the alarm raised time exceeds the threshold of the alarm highlight.
l The unacknowledged and uncleared fault alarm is highlighted when the interval between
the local time on the client and the alarm raised time exceeds the threshold of the alarm
highlight.
l The time on the client should synchronize with the time on the server. Otherwise, the time
an alarm is highlighted differs from the highlight time you set. For example, if the highlight
time you set is 5 minutes. But the time on the client is 5 minutes ahead of the time on the
server. Then, the alarm is highlighted on the client immediately when it is raised.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the System Setting dialog box, in the navigation tree on the left, expand the Alarm Local
Terminal Settings node, and then select Highlight.
Step 3 In the Highlight group box, set the time for the alarms of a level.
NOTE
Time range: 0-1000000, Unit: minute. 0 indicates that the alarm is not highlighted.
----End
Context
l A user can set more than one remote notification mode.
l A user can add at most fifty remote notification rules for alarms. Attempts to add more than
fifty cause error messages.
l In the Email or SMS, the alarm occurrence time and the alarm clearance time are the time
of the M2000 server.
Procedure
Step 1 Choose Monitor > Settings > Remote Notification .
Step 2 In the Remote Notify tab click Add, and then choose Fault Notification .
Step 3 In the Add Remote Notify Rule dialog box set Level, Type, and Alarm Source. Click Next.
Step 4 Click the Alarm Source tab. On the Alarm Source tab, set the alarm source. Click Next.
Step 5 In the Add Remote Notify Rule dialog box set the notification time. Click Next.
Step 6 In the Add Remote Notify Rule dialog box set the email address or SMS number. Select
Enable.
Step 7 Click Finish.
----End
Related References
2.8.16 Parameters for Selecting Alarm Name
2.8.32 Parameters for Setting Alarm Remote Notification Rules
Context
Only the users that have the right of Setting Remote notification parameters can perform this
task
Procedure
Step 1 Choose Monitor > Settings > Remote Notification .
Step 2 On the lower left of the Remote Notify window, click Communication Settings.
Step 3 In the Notify Device Communication Settings dialog box, click Add.
NOTE
l In the Notify Device Communication Settings dialog box, select a row and click Modify. In the Modify
Notify Device Communication Settings dialog box, modify the setting name and communication
parameters.
l In the Notify Device Communication Settings dialog box, select a row and click <Delete to delete the
settings.
Step 4 In the Add Notify Device Communication Settings dialog box, enter the device name. Select
the sending device. Click Next.
NOTE
l There are three types of devices that can send alarm notification: Email, ETC CDMA Modem, and SMS
Gateway(SMS Center). The method of email sends notifications by emails. The other methods send
notifications by SMS.
l When you set ETC CDMA Modem, pay attention to the following points:
l If the sending address is the server, the modem must be correctly installed on the server. In this case,
the clients that log in to the server can send short messages for alarm remote notification.
l If the sending address is the client, only the clients that are installed with the modem can send remote
alarm notification.
l If the sending address is the client, the corresponding serial port of the client is always in use until the
M2000 client is exited.
l If the sending address is the server, the corresponding serial port of the server is always in use until the
M2000 server is exited.
Step 5 In the Add Notify Device Communication Settings dialog box, set the parameters. Select
Enable.
NOTE
For details on the parameters, see 2.8.33 Parameters for Setting Notification by Email, 2.8.35 Parameters
for Setting Notification by Modem, or 2.8.37 Parameters for Setting Notification by SMS Gateway.
Step 6 Optional: Click Advanced. In the Notify Device Communication Settings dialog box, set the
format of the sending content. Click OK.
NOTE
For details on the parameters, see 2.8.34 Parameters for Advanced Settings of Notification by Email, 2.8.36
Parameters for Advanced Settings of Notification by Modem, or 2.8.38 Parameters for Advanced Settings
of Notification by SMS Gateway.
Step 7 In the Notify Device Communication Settings dialog box, click Add.
Step 8 In the Notify Device Communication Settings dialog box, click Close.
----End
Related References
2.8.33 Parameters for Setting Notification by Email
2.8.34 Parameters for Advanced Settings of Notification by Email
2.8.35 Parameters for Setting Notification by Modem
2.8.36 Parameters for Advanced Settings of Notification by Modem
2.8.37 Parameters for Setting Notification by SMS Gateway
2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway
The modification on the alarm screening rule refers to modifying the screen condition, time
mode, screening rule, validation date, expiration date, and remark based on the previous alarm
screening rule.
2.3.4.3 Deleting Alarm Filter Rules
If an alarm filter rule is no longer applicable, delete it.
Related References
2.8.19 Parameters for Setting Alarm Filter Conditions
Context
l If both alarm redefinition and alarm filter are set for an alarm, the alarm is filtered first and
then redefined. Therefore, alarm filter is based on the original attributes (the attributes
before redefinition) of the alarms.
l The M2000 discards the alarms that are masked by the alarm mask rules and does not save
the alarms to the alarm database.
Procedure
Step 1 Choose Monitor > Settings > Alarm Filter Rule .
Step 2 On the Alarm Filter Rule tab, click Add. Choose New Alarm Filter Rule or New Event Filter
Rule.
Step 3 In the Add Alarm Filter Rule dialog box, set the filter parameters.
Step 4 Click OK.
----End
Context
l If both alarm redefinition and alarm filter are set for an alarm, the alarm is filtered first and
then redefined. Therefore, alarm filter is based on the original attributes (the attributes
before redefinition) of the alarms.
l The M2000 discards the alarms that are masked by the alarm mask rules and does not save
the alarms to the alarm database.
Procedure
Step 1 ChooseMonitor > Settings > Alarm Filter Rule .
Step 2 On the Alarm Filter Rule tab, change the alarm filter rules.
NOTE
l The fields displayed in white can be changed. The fields displayed in cannot be changed. The fields
displayed in are already changed but are not used.
l You can also select a relevant alarm filter rule, and then click Detail. In the Detail Information dialog box,
change the alarm filter rules.
----End
Procedure
Step 1 Choose Monitor > Settings > Alarm Filter Rule .
Step 2 On the Alarm Filter Rule tab, select the alarm filter rule you want to delete. Click Delete.
Step 3 In the Confirmation dialog box, click Yes.
----End
Procedure
Step 1 ChooseMonitor > Settings > Auto Acknowledge Rule .
Step 2 In the Auto Acknowledgement Rule dialog box, set the parameters of auto acknowledgement.
Step 3 Click OK.
After auto acknowledgement is enabled, the M2000 acknowledges the fault alarms that match
the preset conditions.
----End
Related References
2.8.18 Parameters for Acknowledging Alarms Automatically
Modify the content of the alarm level redefinition rule, including the alarm source, redefined
level, and memo.
2.3.6.3 Deleting Redefinition Records
You can recover the alarm level defined by the device manufacturer by deleting the alarm level
redefinition record.
Related References
2.8.23 Parameters for Redefining NMS Alarm Level
2.8.25 Parameters for Alarm Level Redefinition
Context
l The results of query, browse and statistics are displayed based on the alarm levels that are
redefined.
l Redefinition is to change the alarm level on the M2000 server, rather than to change alarm
explanations given by the device manufacturer.
Procedure
Step 1 Choose Monitor > Settings > Level Redefine .
Step 2 Click Add. In the Add level Redefine Setting dialog box, set the parameters for the alarm level
redefinition.
1. Click next to Alarm Name. In the Select Alarm Name dialog box, select the alarm
whose level you want to redefine. Click OK.
2. In the Redefine Level drop-down list, select the level for the alarm after redefinition.
3. In the Memo text box, set the remarks as required.
4. Select or clear the Enable check box as required.
5. In the Alarm Source tab, click Select. In the Select object window , select the objects that
raise alarms. By default, all the objects are selected.
When the objects in Alarm Source report the alarms that are set in Alarm Name, the alarm
level are redefined.
----End
Procedure
Step 1 ChooseMonitor > Settings > Level Redefine .
Step 2 In the Level Redefine window, change the alarm level redefinition rules.
NOTE
l The fields displayed in white can be changed. The fields displayed in cannot be changed. The fields
displayed in are already changed but are not used.
l You can also select a relevant alarm level redefinition rule, and then click Detail. In the Detail
Information dialog box, change the alarm level redefinition rules.
----End
Procedure
Step 1 Choose Monitor > Settings > Level Redefine .
Step 2 In the Level Redefine window, select the alarm level redefinition rules you want to delete.
NOTE
You can choose more than one record by Shift and Ctrl.
----End
rule. When the intermittent alarms reach the preset limit, the M2000 filters or discards them
based on the correlation rule. The system can then work in a stable state.
2.3.7.4 Adding Advanced Correlation Rules of Alarms
Through setting the advanced correlation rules of alarms, you can filter the alarms that match
the rules or redefine the alarm levels. Therefore, you can reduce the unnecessary alarms or ignore
the non-root alarms so that you can handle the major alarms and solve problems quickly.
2.3.7.5 Modifying Simple Correlation Rules for Alarms
This section describes how to modify the existing simple correlation rules for alarms.
2.3.7.6 Modifying Advanced Correlation Rules for Alarms
This section describes how to modify the existing advanced correlation rules for alarms.
2.3.7.7 Example of Using Simple Correlation Rules of Alarms
This section gives an example of using the simple correlation rules of intermittent alarms to
describe how to set a simple correlation rule for alarms.
2.3.7.8 Example of Using Advanced Correlation Rules of a Single Alarm
This section describes how to set the advanced correlation rules for a single alarm by giving an
example.
2.3.7.9 Example of Using Advanced Correlation Rules of Two Alarms
This section describes how to set the advanced correlation rules for two alarms by giving an
example.
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. To solve this problem, you can set a condition based on the alarm features, such as the
alarm raised time or physical location to shield the alarms that do not match the condition or
reduce the levels of insignificant alarms.
Simple/Advanced Correlation
In the M2000, the correlation of the intermittent alarms or repeat events is considered as simple
correlation alarms, and the correlation of the other alarms is considered as advanced correlation
alarms.
Example 1:
The priority of an alarm advanced correlation rule is 1000000000. The priority of another alarm
advanced correlation rule is 1000000. When an alarm meets both rules, the system performs the
first alarm correlation rule first, and then the second correlation rule.
Example 2:
The priority of an alarm advanced correlation rule is 1000000000. The priority of another alarm
advanced correlation rule is also 1000000000. When an alarm meets both rules, the system takes
the analysis actions based on the sequence in which the two rules are added to the correlation
analysis module.
Context
l If the clearance interval of the same alarm is less than the preset interval, the alarm is
intermittent.
l The alarm correlation takes effects only when alarm intervals and repetitions matches what
you set.
l The M2000 discards or save the alarms that are shielded by the correlation rules to the
shield database. You can query the shielded alarms in the shield database.
Procedure
Step 1 Choose Monitor > Settings > Simple Correlation .
Step 3 In the Add Simple Correlation Properties dialog box, set the parameters for correlation rules.
1. Click Choose. In the Select Alarm Name dialog box, select the alarms on which you want
to analyze the correlation, and then click OK.
2. Set Interval and Intermittence/Repeat Times.
----End
Related References
2.8.39 Parameters for Setting Simple Correlation Rules
Context
The M2000 redefine the alarm level or save the alarms that are shielded by the correlation rules
to the shield database. You can query the shielded alarms in the shield database.
Procedure
Step 1 Choose Monitor > Settings > Advanced Correlation .
Step 3 In the Add Advanced Correlation Rule dialog box, set the parameters for correlation rules.
1. Set the correlation conditions: Click Add next to the Correlation Condition group box.
Set Alarm Instance A, Alarm Instance B, Property, Condition, and Value.
2. Set the correlation action: Click New next to the Correlation Action group box. Set Alarm
Instance, Action, and Value.
3. Set Priority, Memo, and Enable.
----End
Related References
2.8.40 Parameters for Setting Advanced Correlation Rules
Procedure
Step 1 ChooseMonitor > Settings > Simple Correlation .
Step 2 In the Simple Correlation window, you can modify the correlation rules in the following ways:
l Click the field of an alarm correlation rule, and then modify it. Then click Apply.
NOTE
l The fields displayed in white can be changed. The fields displayed in cannot be changed. The
fields displayed in are already changed but are not used.
l Select a relevant alarm correlation rule, and then click Detail. In the Detail Simple
Correlation Properties dialog box, modify the correlation rule. Then click OK.
----End
Procedure
Step 1 ChooseMonitor > Settings > Advanced Correlation .
Step 2 In the Advanced Correlation window, you can modify the correlation rules in the following
ways:
l Click the field of an alarm correlation rule, and then modify it. Then click Apply.
NOTE
l The fields displayed in white can be changed. The fields displayed in cannot be changed. The
fields displayed in are already changed but are not used.
l You can use this method to modify the correlation rules for multiple alarms.
l Select a relevant alarm correlation rule, and then click Detail. In the Modify Advanced
Correlation Rule dialog box, modify the correlation rule. Then click OK.
----End
Background
The M2000 receive mass fault alarms that are raised and cleared periodically. These alarms are
reduced after the intermittent alarm correlation rules are set.
Operation Guide
To set correlation rules for intermittent alarms, do as follows:
1. Choose Monitor > Settings > Simple Correlation .
2. In the Simple Correlation window, click Add.
3. In the Add Simple Correlation Properities dialog box, set the correlation rule parameters.
(1) Click Choose. In the Select Alarm Name dialog box, select the alarms that need
correlation analysis, and then click OK.
(2) Set Interval to 3, which indicates that the interval between the clearance of two
intermittent alarms is three seconds.
(3) Set Intermittence / Repeat Times to 5.
(4) Set Action to discarding.
(5) Select Enable.
4. Click OK.
Background
During the period from 5:00 to 23:00 on September 5th, 2005, the NE Z raises mass critical
alarms M during upgrade. These critical alarms do not need be concerned. Therefore, the
administrator redefines all the critical alarms M raised during upgrade to warning alarms, so that
the alarms M are not concerned.
In this example, the administrator redefines the critical alarms M that are raised during the period
from 5:00 to 23:00 on September 5th, 2005.
NOTE
l This correlation analysis is to obtain the root alarms M, and it does not conflict with the correlation analysis
of repeat event alarms or intermittent fault alarms. Therefore, the priority value of this correlation analysis
can be lower than that (which is 1000000000) of repeat event alarms or intermittent fault alarms. In this
example, the priority is set to 1000000.
l When you customize Correlation Condition, you can perform correlation analysis only when all the
conditions are met. Therefore, do not add indeterminate correlation conditions to a custom correlation rule
record. In addition, mass custom correlation analysis may increase the system load. Do not add too many
conditions of custom correlation rule analysis.
Operation Guide
To set a single custom alarm instance, do as follows:
1. Choose Monitor > Settings > Advanced Correlation .
2. In the Advanced Correlation window, click Add.
3. Set the condition for that the alarms M are generated by NE Z.
(1) Click Add next to Correlation Condition.
(2) Set the new correlation condition records. In the Alarm Instance A column, select
Create Alarm Instance. In the displayed Select Alarm Name dialog box, select the
alarm name M, and then click OK. In the Property column, select NE. In the
Condition column, select Equal. Click Value. In the displayed Select Alarm
Name dialog box, click NE Z, click OK.
4. Set the raised time of the alarms M later than 5:00, on September 5th, 2005.
(1) Click Add next to Correlation Condition.
(2) Set the new correlation condition records. In the Alarm Instance A column, select
the alarm name M. In the Property column, select Occurrence Time. In the
Condition column, select Greater than. Click the Value column. In the Select
time dialog box, set the time to 05-09-2005 05:00:00, click OK.
5. Set the raised time of the alarms M earlier than 23:00, on September 5th, 2005.
(1) Click Add next to Correlation Condition.
(2) Set the new correlation condition records. In the Alarm Instance Acolumn, select the
alarm name M. In the Propertycolumn, select Occurrence Time. IN the
Condition column, select Less than. Double-click the Value column. In the Select
time dialog box, set the time to 05-09-2005 23:00:00, click OK.
6. Set the actions of redefining the alarms M.
(1) Click Add next to Correlation Action.
(2) Set the new correlation condition records. In the Alarm Instancecolumn, select the
alarm name M. In the Action column, select Level Redefine. In the Value column,
select Warring.
7. Set Priority to 1000000.
8. Select Enable.
9. In the Add Advanced Correlation Rule dialog box, click OK.
Background
In the actual application, the link of an NE is faulty, and the NE reports the fault alarm M
periodically. In addition, due to the faulty link, this NE or other NEs may raise mass link fault
alarms N. The fault alarm M is the root alarm of the alarm N. Therefore, in the actual analysis,
the administrator can analyze the alarm causes and handling methods by analyzing the alarm M,
and you do not need to analyze the alarm N. The administrator can filter all the alarms N that
are raised after the alarm M by adding correlation rule records.
In this example, the alarm M must be raised before the alarm N. Therefore, the administrator
only need to compare the raised times of the two alarms to determine whether the alarm N meets
the filter conditions.
NOTE
When you customize Correlation Condition, you can perform correlation analysis only when all the conditions
are met. Therefore, do not add indeterminate correlation conditions to a custom correlation rule record. In
addition, mass custom correlation analysis may increase the system load. Do not add too many conditions of
custom correlation rule analysis.
Operation Guide
To set two custom alarm instances, do as follows:
1. Choose Monitor > Settings > Advanced Correlation .
2. In the Advanced Correlation window, click Add.
3. Set the comparison conditions for the alarm M and alarm N.
In this instance, the alarm is raised before the alarm N, that is, the raised time of the alarm
M is earlier than that of the alarm N.
Prerequisite
You have logged in to the M2000 client.
Context
CAUTION
l You need to manually send the script files to be triggered to the M2000 server.
l You can create a maximum of 100 auto-triggering tasks.
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed.
Step 2 Click New, or right-click the task list and choose New from the shortcut menu.
TIP
You may also select an existing auto-triggering task, and by modifying the task information, you can create
an auto-triggering task.
Step 3 In the displayed New Task dialog box, set the basic attributes of the task.
1. In the Task Name field, enter the name of the task.
2. Set the time range and Period.
You may set the time using any of the following three ways:
l Directly enter the time.
l Click or to adjust the time.
CAUTION
The script to be executed is triggered by the server only when the alarm occurs in the
specified time range, and in Period, the date is set to Tuesday.
3. Choose the task running mode from the Run-time Type drop-down list.
4. In the Script File dialog box, enter the absolute path and the name of the script file on the
server.
For example, /export/home/trigger.sh.
NOTE
l Based on demands, in the Run-time Param field, you can reset some of the parameters in the script
file.
l In the Remark field, you may enter task description related information.
For details about relevant parameters, see 2.8.41 Parameters for the Basic Attributes of Auto-
Triggering Tasks.
Step 4 Click the Trigger Condition tab, and then click Add.
NOTE
Step 5 Set the NE alarm of the auto-running script file triggered by the server.
CAUTION
If the triggering conditions that are set are incorrect, for example, if the selected NE does not
exist on the actual network, a dialog box indicating error is displayed. At the same time, on the
Trigger Condition tab page, the Message field displays the message explaining the detailed
reasons why the triggering conditions fail to be created. In this case, you need to click Delete to
delete the triggering condition and perform Step 4 through Step 6 to set another triggering
condition.
----End
Postrequisite
You may choose Query > Query Record in the Triggering Script window. Then, you can
check the running results of the auto-triggering task, For example, the specific time for the
triggering task.
Related References
2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks
2.8.42 Parameters for Auto-Triggering Conditions
2.8.43 Parameters for Adding the Alarm Conditions of the Auto-Triggering Script
Prerequisite
l You have logged in to the M2000 client.
l The auto-triggering task exists.
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed.
Step 2 In the task list, choose the task record whose attribute you need to query.
You may either click Refresh or right-click the task list and choose <Refresh to obtain the latest
information about the task. In usual cases, the client refreshes the displayed information about
the task in real time.
Step 3 Double-click the task record. Alternatively, right-click the it and choose Attribute from the
shortcut menu or click Attribute.
The system displays the Attribute dialog box.
Step 4 You can check the detailed information about the auto-triggering task.
l Basic Attribute tab page: displays the basic attribute of the auto-triggering task. For
parameter-related description, refer to 2.8.41 Parameters for the Basic Attributes of Auto-
Triggering Tasks.
l Trigger Attribute tab page: displays the trigger attribute of the auto-triggering task. For
parameter-related description, refer to 2.8.42 Parameters for Auto-Triggering
Conditions.
NOTE
Based on demands, you can modify the auto-triggering task related information, click OK. he modified
auto-triggering tasks are displayed in the task list of the Triggering Script dialog box.
----End
Related References
2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks
2.8.42 Parameters for Auto-Triggering Conditions
2.8.43 Parameters for Adding the Alarm Conditions of the Auto-Triggering Script
Prerequisite
l You have logged in to the M2000 client.
l The auto-triggering task exists.
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed.
Step 2 Choose Query > Query Task, or right-click the task list and choose Query Task from the
shortcut menu.
The Query Task dialog box is displayed.
Step 3 Select the check boxes before the related parameters, and then set the querying conditions.
By selecting multiple check boxes, you can set multiple querying conditions. For parameter-
related description, refer to 2.8.44 Parameters for Searching Auto-Triggering Tasks.
The auto-triggering task that meets the requirements of the querying conditions is displayed in
the task list of the Triggering Script dialog box.
----End
Related References
2.8.44 Parameters for Searching Auto-Triggering Tasks
Prerequisite
l You have logged in to the M2000 client.
l The auto-triggering task exists.
Procedure
Step 1 Choose Maintenance > Trigged Script. The Triggering Script window is displayed.
Step 2 ClickQuery > Query Record. Alternatively, right-click it and choose Query Record from the
shortcut menu.
The Query Record dialog box is displayed.
Step 3 Select the check boxes before the related parameters, and then set the querying conditions.
By selecting multiple check boxes, you can set multiple querying conditions. For parameter-
related description, refer to 2.8.45 Parameters for Searching Auto-Triggering Records.
Step 4 Click Query.
The triggering records are displayed in the Query Result list.
NOTE
----End
Related References
2.8.45 Parameters for Searching Auto-Triggering Records
You can shield the alarms that you are not required. Thus, you can prevent the NE from reporting
the alarms that must be shielded. In this case, invalid alarm information is reduced, the system
stress is decreased, and the efficiency of the system is improved.
2.4.2 Querying the Shielding of an NE Alarm
You can query the shielding of an NE alarm that has been sent to the NE.
2.4.3 Modifying the Shielding of an NE Alarm
By using this function, you can modify the alarm shielding that is sent to but does not reach the
NE. For the shielding of an NE alarm that does not reach the NE, you need to click Apply to
make the setting take effect. For the setting that does not reach the NE, the modification has no
effect on the NE.
2.4.4 Redefining the Level of an NE Alarm
The M2000 enables you to redefine the severity level of an NE alarm. By using this function,
you can downgrade the severity level of an alarm that has minimal impact on the system. You
can also upgrade the severity level of a major fault alarm.
2.4.5 Querying the Redefinition of an NE Alarm Level
You can query an applied alarm level redefinition record with this function.
2.4.6 Modifying the Setting of NE Alarm Level Redefinition
This describes how to modify an alarm level redefinition record.
2.4.7 Defining an NE Alarm
A newly defined alarm is identified by NE type and alarm ID. Its alarm name, alarm severity
level, and alarm type can be different with that on the NE side. The M2000 supports the function
of environment monitoring. You can define a new NE alarm, bind it to a port of a cabinet, frame,
or slot of an NE, and then externally mount an environment monitoring device on the port. In
this case, when the device detects environment exceptions, a real-time alarm is generated on the
NE and reported to the M2000. In this way, it can quickly and automatically obtain the exception
conditions and guarantee the normal operation.
2.4.8 Binding a User-Defined Alarm
This describes how to define the corresponding relations between the user-defined alarms and
the signal input ports. When a signal received through a port meets the alarm triggering
conditions, the NE reports an alarm to the M2000, and the alarm is bound with a customized
name and ID.
Prerequisite
l You have logged in to the M2000 client.
l You are familiar with the meaning of each alarm.
l You are authorized to perform the related operation.
Context
The following NEs do not support this function: IWF, SG7000, HLR36, PCU35, PCU33,
PCU6000, tMSC, iMSC, MSC, BSC, GT800BSC, BTS, and AHR.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
The alarm shielding record to be added is listed on the Alarm Binding tab page. Each
record is marked on the left.
NOTE
The alarm shielding setting is saved on only the M2000. You must click Apply to apply it on the
NE.
6. Click Apply.
The alarm shielding setting is applied on the NE. The symbol disappears. An
information box is displayed, indicating whether the operation succeeds or fails.
The Shielded Flag in the Add Alarm Shielding dialog box is not configurable. The default
setting is Yes.
----End
Related References
2.8.22 Parameters for Shielding an NE Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are familiar with the meaning of each alarm.
l You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Perform the following operations based on the actual requirement.
Delete from the shortcut menu. You can also delete the alarm shielding records in batches
by using the Ctrl or the Shift key.
3. Click , and select the NE with this alarm filter in the displayed topology tree. Or you
can also enter directly the NE name.
4. Enter the start alarm ID and the end alarm ID to specify the query range.
5. Enter the maximum number of returned records.
6. Select the alarm level in the Alarm Level tree.
7. Click OK.
The queried alarm shielding record is displayed as a list on the Alarm Shielding tab page.
----End
Related References
2.8.14 Parameters for Selecting NE for Query
2.8.21 Parameters for Querying the Shielding of an NE Alarm
Prerequisite
l You have logged in to the M2000 client.
l Relevant NEs are properly connected to the M2000.
l You are authorized to perform the related operation.
l The related NEs operate properly.
l At least one alarm shielding record exists.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 In the list of the NE Alarm Shielding tab under Alarm Shielding, select an alarm shielding
record.
Step 3 Click Modify, or right-click the object group and select Modify from the shortcut menu.
Step 4 Refer to 2.8.22 Parameters for Shielding an NE Alarm to reset the alarm shielding.
You can modify the Shielded Flag only when modifying the applied alarm shielding. The default
setting is Yes.
The user-defined alarms to be modified are listed. The alarm record is marked with on the
left.
CAUTION
l After you modify an alarm shielding record, click Apply to submit this new record to the
NE.
l To modify an applied record, ensure that this record exists. For details, see 2.4.2 Querying
the Shielding of an NE Alarm.
The modified user-defined alarms are applied to the NE. An information box is displayed,
indicating whether the operation is successful.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are familiar with the meaning of each alarm severity level.
l You are authorized to perform the related operation.
Context
The following NEs do not support this function: SG7000, HLR36, PCU35, PCU33, PCU6000,
tMSC, iMSC, MSC, BSC, GT800BSC, BTS, IP Clock Server, and AHR.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Level Redefinition tab, and click Add. The Add Alarm Level Redefinition
dialog box is displayed.
Step 3 Select an NE from the Select NE tree. You can also type the keyword in Search by Name to
search for the NE.
Step 4 Select an NE from the Select Alarm tree. You can also type the keyword in Search by Name
to search for the NE.
Step 5 Select an alarm severity level from the Redefined Level drop-down list.
The alarm level redefinition record to be added is listed on the Alarm Binding tab page. Each
record is marked on the left.
NOTE
After that, you must click Apply to add the new record to the NE.
The alarm level redefinition is applied on the NE and the symbol disappears. An information
box is displayed, indicating whether the operation succeeds or fails.
----End
Related References
2.8.24 Parameters for Redefining/Modifying the Level of an NE Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Level Redefinition tab, and click Query. The Query Alarm Level
Redefinition dialog box is displayed.
Step 3 Click , and select the NE with this alarm level redefinition in the displayed topology tree.
Alternatively, you can also enter directly the NE name.
Step 4 Enter the start alarm ID and the end alarm ID to specify the query range.
----End
Related References
2.8.14 Parameters for Selecting NE for Query
2.8.26 Parameters for Querying the Redefinition of an NE Alarm Level
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
l At least one alarm level redefinition record exists.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 In the list on the Alarm Level Redefinition tab page, select an alarm redefinition record.
Step 3 Click Modify. Alternatively, right-click and select Modify from the shortcut menu. The Add
Alarm Level Redefinition dialog box is displayed.
Step 4 Refer to 2.4.4 Redefining the Level of an NE Alarm to reset the alarm level redefinition.
Step 5 Click OK.
CAUTION
l After you modify an alarm level redefinition record, click Apply to submit this new record
to the NE.
l Before modifying an applied record, ensure that this record exists. For details, see 2.4.5
Querying the Redefinition of an NE Alarm Level.
----End
Related References
2.8.24 Parameters for Redefining/Modifying the Level of an NE Alarm
of environment monitoring. You can define a new NE alarm, bind it to a port of a cabinet, frame,
or slot of an NE, and then externally mount an environment monitoring device on the port. In
this case, when the device detects environment exceptions, a real-time alarm is generated on the
NE and reported to the M2000. In this way, it can quickly and automatically obtain the exception
conditions and guarantee the normal operation.
Context
The NEs that support this function are NodeB, MSC Server, MGW, and BSC6000.
2.4.7.1 Querying a User-Defined Alarm
This describes how to query a user-defined alarm. The attributes of user-defined alarms are
stored in the M2000 database. You can query the related information in the database. The
attributes of a user-defined alarm are NE type, alarm ID, alarm name, alarm severity level, and
alarm type.
2.4.7.2 Adding a User-Defined Alarm
This describes how to add a user-defined alarm as required.
2.4.7.3 Modifying a User-Defined Alarm
This describes how to modify a user-defined alarm.
Related References
2.8.27 Parameters for User-Defined Alarms
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Definition tab in the User Defined Alarm dialog box.
Step 3 Click Query. The Query User Defined Alarm dialog box is displayed.
Step 4 Enter the name and ID of the user-defined alarm to be queried.
Step 5 Select the NE type and alarm severity level.
----End
Related References
2.8.14 Parameters for Selecting NE for Query
2.8.28 Parameters for Querying a User-Defined Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Definition tab in the User Defined Alarm dialog box.
Step 3 Click Add.
The Add User Defined Alarm dialog box is displayed.
Step 4 Set the parameters related to user-defined alarms.
Step 5 Click OK.
The alarm bindings to be added are listed on the Alarm Definition tab page. Each record is
marked .
NOTE
For the NodeB, user-defined alarms are not issued to the NE. For the MSCe and MGW, if you have selected
the specific NE when adding or modifying user-defined alarms, the user-defined alarms are issued to the
selected NE after you click Apply.
The icon disappears. An information box is displayed, indicating whether the operation
succeeds or fails.
----End
Related References
2.8.27 Parameters for User-Defined Alarms
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
Context
CAUTION
The ID and NE type of a user-defined alarm cannot be modified.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Definition tab in the User Defined Alarm dialog box.
Step 4 Click Modify. Alternatively, right-click the object group and choose Modify from the shortcut
menu.
Step 5 Rename the user-defined alarm in the Alarm Name field in the Modify User Defined Alarm
dialog box, if required.
Step 6 Select the alarm severity level in the Alarm Level field, if required.
The alarm bindings to be added are listed on the Alarm Definition tab page. Each record is
marked .
NOTE
After a user-defined alarm is modified, you need to click Apply to make the modification take effect.
The modified user-defined alarms are applied to the NE. An information box is displayed,
indicating whether the operation succeeds or fails.
----End
Related References
2.8.27 Parameters for User-Defined Alarms
Context
The NEs that support this function are NodeB, MSC Server, MGW, and BSC6000.
2.4.8.1 Querying the Binding of a User-Defined Alarm
This describes how to query the binding of a user-defined alarm. The binding of a user-defined
alarm is stored on the related NE rather than in the M2000 database. You can query an existing
binding of a user-defined alarm on an NE.
2.4.8.2 Adding the Binding of a User-Defined Alarm
This describes how to add the binding of a user-defined alarm as required.
2.4.8.3 Modifying the Binding of a User-Defined Alarm
This describes how to modify the binding of a user-defined alarm.
2.4.8.4 Canceling the Binding of a User-Defined Alarm
This describes how to cancel the binding of a user-defined alarm, that is, cancel the binding of
a user-defined alarm set on the M2000 and not issued to the related NE. This operation does not
affect the NE operation.
Related References
2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Binding tab on the User Defined Alarm in the NE Alarm Settings window.
Step 3 On the Alarm Binding tab page, click Query. The Query Alarm Binding dialog box is
displayed.
Step 4 In the Query Alarm Binding dialog box, click behind NE Name.
Step 5 In the displayed navigation tree, select the NE that the alarm binding to be queried belongs to.
Step 6 Type a cabinet number in Cabinet, subrack number in Subrack, slot number in Slot, and port
number in Port.
Step 7 Click OK.
The queried alarm binding is displayed on the Alarm Binding tab page in the NE Alarm
Setting window.
----End
Related References
2.8.14 Parameters for Selecting NE for Query
2.8.29 Parameters for Querying the Binding of a User-Defined Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Binding tab in the User Defined Alarm dialog box.
Step 4 In the left Select NE navigation tree, select an NE. Alternatively, enter the NE name in the
Search by Name field.
Select Group by NE Type. Then, the Select NE navigation tree displays the NEs by NE type.
Step 5 In the left Select Alarm navigation tree, select an alarm. Alternatively, enter the alarm name in
the Search by Name field.
Select Group by Alarm Type, Group by Alarm Level, and Group by Category. Then, the
Select Alarm tree displays the alarms by alarm type and alarm severity level.
The alarm bindings to be added are listed on the Alarm Binding tab page. Each record is marked
.
CAUTION
After adding alarm bindings, you must click Apply to make the settings take effect on the NE.
The user-defined alarm is bound to the NE and the icon before the related record disappears.
An information box is displayed, indicating whether the operation succeeds or fails.
----End
Related References
2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
l At least one user-defined alarm binding record is available.
Context
After the binding of an MSCe alarm is applied, it cannot be modified.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Binding tab in the User Defined Alarm dialog box.
Step 4 Click Modify. Alternatively, right-click the binding and choose Modify from the shortcut menu.
The Modify Alarm Binding dialog box is displayed.
Step 5 In the Modify Alarm Binding dialog box, modify the binding parameters. For detailed
description of the parameters, refer to 2.8.30 Parameters for Adding/Modifying the Binding
of a User-Defined Alarm.
Step 6 Click OK.
The alarm bindings to be added are listed on the Alarm Binding tab page. Each record is marked
.
CAUTION
After adding alarm bindings, you must click Apply to make the settings take effect on the NE.
----End
Related References
2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the related operation.
l At least one user-defined alarm binding record is available.
Procedure
Step 1 Choose Monitor > Settings > NE Alarm Setting . The NE Alarm Settings window is
displayed.
Step 2 Click the Alarm Binding tab in the User Defined Alarm dialog box.
Step 3 In the list on the Alarm Binding tab page, select one user-defined alarm binding record.
Step 4 Click Undo. Alternatively, right-click the record and choose Undo from the shortcut menu.
----End
Context
The NEs that support this function are NodeB, MSC Server, MGW, and BSC6000.
NOTE
You can monitor the performance of NEs only after purchasing the license of the monitoring function.
Related References
2.8.5 Interface Description: Performance Monitor
For the detailed meaning and the calculation method of the performance counters, refer to
Performance Counter Information in NE Reference Information of the online help. For
details about how to download the NE reference information, refer to 1.14 Downloading NE
Mediation Data to the M2000 Client.
Function
Function Set Monitoring Counter
Subset
Function
Function Set Monitoring Counter
Subset
Seizure traffic
Connection traffic
Answer traffic
Seizure traffic
Connection traffic
Answer traffic
Answer traffic
Seizure traffic
Connection traffic
Answer traffic
BHCA value
Function
Function Set Monitoring Counter
Subset
Congestion times
Congestion duration
Overload times
Overload duration
Connection traffic
Answer traffic
Seizure ratio
Connected ratio
Answered ratio
Answer traffic
Seizure traffic
Connection traffic
Answer traffic
Function
Function Set Monitoring Counter
Subset
Answered ratio
Seizure traffic
Connection traffic
Answer traffic
Unavailable times
Unavailable duration
Link traffic
Congestion times
Congestion duration
Unavailable times
Unavailable duration
Link traffic
Congestion times
Function
Function Set Monitoring Counter
Subset
Congestion duration
Unavailable times
Unavailable duration
Link traffic
Alert Rate
HO due to UL Quality
HO due to DL Quality
Network Availability
Maximum FR-Traffic
Maximum HR-Traffic
Incoming HO
Incoming HO Success Rate
Monitor
Outgoing HO
Outgoing HO Success Rate
Monitor
SS7 Link
Link Monitor SS7 Signaling Link Receiving and Sending Rate
Monitor
Gn Uplink in MB
Gn Downlink in MB
Gi Uplink in MB
Gi Downlink in MB
Table 2-11 SGSN performance monitoring counter on the FTP MML interface
Function Set Function Monitoring Counter
Subset
Alert rate
iMSC Office iMSC Office Bidirectional Trunk Incoming Call Seized Traffic
Traffic Traffic
Monitor Measurement Bidirectional Trunk Outgoing Call Seized Traffic
Seizure traffic
iMSC Trunk iMSC Trunk Bidirectional Trunk Incoming Call Answered Traffic
Traffic Traffic
Monitor Measurement Bidirectional Trunk Outgoing Call Answered Traffic
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed.
Step 2 Select the Monitor Task tab on the left of the window.
If the monitored task is unavailable on the navigation tree, you can right-click System Task or
User-Defined Task and choose Refresh to refresh the navigation tree.
Step 3 Right-click the task in the navigation tree choose select View Task. The View Task dialog box
is displayed.
In the dialog box, you can view the detailed information of the task.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l A monitoring task consists of system task, Tip task, and user-defined task.
l The HLR, iMSC, MSC Server, BSC32, BSC6000, PCU, RNC, SGSN, GGSN80, and MSC
Pool support this function. The BSC6000 supports the monitoring period of one minute.
l The naming rule for the monitoring task tab page is NE name-Monitoring type. For example,
RNC32-RNC.
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed.
Step 2 You can choose an NE from the NE View tab page or choose an object group from the Object
Set tab page to create a monitoring task.
NE view 1. Click the NE view tab on the left part of the interface.
2. Select the NE in the navigation tree. You can press Ctrl or Shift to
select multiple NEs or cells of the same NE type.
3. Perform Step 3.
Object set 1. Click the ObjectGroup tab on the left part of the interface.
2. Select the object group in the navigation tree. For details, refer to 1.16
Managing User-Defined Object Groups.
3. Perform Step 3.
You can perform either of the following operations to open the Monitor Parameter Setting
window.
l Press and hold the left mouse button to drag the selected NE to the right part of the interface.
l Right-click multiple objects and choose Start Monitor > User-defined.
If you need to use the default settings, choose Start Monitor > Default.
Click Save as Default. The system automatically saves the current setting as the default one.
The setting takes effect when you set the parameters for the same object next time.
----End
Prerequisite
l You have logged in to the M2000 client.
Context
l You can simultaneously start a maximum of eight monitoring tasks on one client. If eight
monitoring tasks that have been started exist, new task fails to be started.
l For each monitoring task, a maximum of 2000 monitoring result records can be displayed
on the GUI.
l All the created tasks are displayed in the navigation tree.
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed.
Step 2 Select the Monitor Task tab on the left of the window.
----End
Prerequisite
A monitoring task is started.
Context
If the time segment is longer, the data synchronization task lasts longer.
Procedure
Step 1 Right-click and select Show Monitor Chart in the Table Data tab.
Step 2 In Monitor Information Setting, select the icon, monitoring object and monitoring counter.
Step 4 Right-click the compare chart and select Synchronize. The Select a Time Segment dialog box
is displayed.
----End
Context
This operation only supports the MSC Server and the RNC.
Procedure
Step 1 Select Performance > Monitor Threshold Management to view Monitor Threshold
Management.
The Threshold List displays all thresholds set for the monitoring task.
Operation Procedure
Add monitoring thresholds. 1. In the navigation tree in the Threshold Info, select an
object to monitor.
2. Set monitoring threshold parameters for the object.
3. Click Add. The added monitoring thresholds are
displayed in the Threshold List. The system refreshes
the Threshold List area on all the other clients.
Operation Procedure
Delete monitoring thresholds. 1. Select the set monitoring thresholds. Press Shift or
Ctrl to select multiple monitoring thresholds at a time.
2. Click Delete.
3. Click Yes in Confirm. After a monitoring threshold is
deleted, the system automatically refreshes the
Threshold List area on all the other clients.
----End
Related References
2.8.50 Parameters for Setting Real-Time Monitoring Thresholds
Context
The set filtering rules apply only to the selected monitoring counters.
Procedure
Step 1 Select Performance > Monitor Threshold Management to view Monitor Threshold
Management.
Step 2 Select a monitoring task in the navigation tree.
The Threshold List displays all thresholds set for the monitoring task.
Step 3 Select a set monitoring threshold.
Step 4 Click Filter Rules. The Set Rules for Monitoring Thresholds dialog box is displayed.
Step 5 Set the date and time.
Step 6 Click Set.
The displayed dialog box shows the operation results.
Step 7 Click OK to close the prompt box.
----End
Related References
2.8.51 Parameters for Setting Rules for Monitoring Thresholds
System Task
A system task is a task configured by the system when you install the M2000. You cannot modify
or change the system task. Table 2-17 shows the detailed information about a system task.
ALL-NET CPU SEIZURE RATIO Performs the performance monitoring of the CPU
usage ratio on the entire network.
ALL-NET BICC LINK Performs the performance monitoring of the BICC link
on the entire network.
ALL-NET H248 LINK Performs the performance monitoring of the H248 link
on the entire network.
Tip Task
A Tip task is a monitoring task customized in Topology Prompt Customizing. It can monitor
the specified NE, link, and area.
NOTE
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed.
Step 2 Click the NE view tab on the left part of the interface.
Step 3 In the navigation tree, select one or more objects to be monitored. Then right-click the node and
choose <Add task to Monitor Panel on the displayed shortcut menu to view the Monitor
Parameter Setting dialog box.
You can press and hold the Ctrl key to select multiple object nodes of the same type.
Step 4 Set Monitor Object Layer, Detail Data Object Layer, Monitor Type, and Monitor
Counter.
Step 5 Click OK. The Dashboard Monitor tab page is displayed.
l In this window, you can simultaneously monitor multiple counter comparison figures or
object comparison figures. In addition, you can view on real-time basis the performance data
reported by NEs on the list locating under each figure.
l You can click Set to set Monitor chart total, Total per page, and Cycle Period(second).
l You can refresh the screen according to the specified Cycle Period by clicking Cycle. Also,
you can click PageUp or PageDown to manually refresh the screen.
----End
Context
The monitoring of entities can be displayed through charts and data tables. Charts include
monitoring charts and tendency charts.
Monitoring charts fall into the following three categories:
l Counter compare charts: show changes of multiple counters of one monitored object.
l Object compare charts: show changes of one counter of multiple monitored objects.
l Detail charts: show changes of various counters and objects in multiple separate charts.
You can set a color for a curve of the monitoring chart to enhance the visual effect of the chart.
2.5.3.9 Showing Scales in a Monitoring Chart
The tick table is used to show the data of a time point in the active monitoring chart. Only the
compare chart and tendency chart support this function.
Context
l The logical relationship between filtering conditions for object monitoring and filtering
conditions for counter monitoring is "AND".
l You can set zero, one, or more filtering conditions. The relationship between multiple
counter filtering conditions can be "OR" or "AND".
Procedure
Step 1 In Performance Monitor, select Table Data.
Step 2 In Table Data, right-click and selectFilter Setting. The Filter Setting dialog box is displayed.
Set filtering conditions for the counter monitoring in the tables directly. Add or delete counter
filtering conditions by clicking the + or -.
----End
Related References
2.8.48 Parameters for Setting Filtering Conditions for a Monitoring Table
Context
This task sets the data display in the table when the value of a counter is greater than the upper
threshold or smaller than the lower threshold.
Procedure
Step 1 In Performance Monitor, select Table Data.
Step 2 In Table Data, right-click and select Threshold Setting. The Threshold Setting dialog box is
displayed.
Step 3 Select a monitored counter, and set the display format of the upper and lower limit.
Click Reset Default. You can cancel the settings through the restoring defaults function. The
data in the table is displayed in the default format.
----End
Related References
2.8.53 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Table
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart.
Step 2 Perform the following operations to zoom in or out the monitor chart or the tendency chart:
----End
Context
l The curve in the counter compare chart indicates the names of the monitored counters. The
curve in the object compare chart consists of names of the monitored objects.
l When you put the mouse on a sampling point, the system displays the time and value of
the data for this point.
l When counters in multiple units are displayed in one compare chart, single x coordinate
and multiple y coordinates are used.
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart.
Step 2 Right-click and select Properties. The Property Setting dialog box is displayed.
----End
Related References
2.8.49 Parameters for Setting Properties for a Monitoring Chart
Procedure
Step 1 In Performance Monitor, select Monitor Chart.
Step 2 Right-click the detail chart and select Threshold Setting. The Detail Chart Threshold
Setting dialog box is displayed.
Step 3 Select a counter and set thresholds for the counter.
Step 4 Click OK.
Two threshold lines are drawn in the detail chart according to the upper and lower thresholds.
When the value of a monitored counter is greater than the upper threshold or smaller than the
lower threshold, the column is regarded as a grained column.
----End
Related References
2.8.52 Parameters for Setting Thresholds for Displaying Counters in a Monitoring Chart
Context
l The format of a background picture can only be GIF, JPG, or PNG.
l The background picture is displayed, by default, in the same size as that of the compare
chart area.
l The background picture cannot be removed. You can set the background color or set a new
background picture to cover the applied background picture.
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart.
Step 2 Right-click the chart and select Background > picture . The Open dialog box is displayed.
Step 3 Select a background picture.
Step 4 Click Open to apply the selected background picture.
----End
Procedure
Step 1 In Performance Monitor, selectMonitor Chart or Trend Chart.
Step 2 Right-click the chart and choose Background > Color . The Background Setting dialog box
is displayed.
Step 3 Set the background color.
Step 4 ClickOK to make the set background color effective. Click Reset to restore the default
background color.
----End
Related References
2.8.47 Parameters for Setting a Background Color for a Monitoring Chart
Procedure
Step 1 In Performance Monitor, selectMonitor Chart or Trend Chart.
Step 2 Right-click the chart and choose Line color settings. The Line Color Settings dialog box is
displayed.
Step 3 Set the color.
Step 4 ClickOK.
----End
Procedure
Step 1 InPerformance Monitor, selectMonitor Chart or Trend Chart.
Step 2 Right-click the chart and select Tick Table.
The tick table is displayed in the monitoring chart.
If the displayed monitoring chart already includes the tick table, perform this operation to hide
the tick table.
----End
Procedure
Step 1 Choose Monitor > Performance Monitor, the Performance Monitor window is displayed.
Step 2 Select the Monitor Task tab on the left of the window.
Step 3 Starting a monitoring task.
For details, refer to 2.5.2.3 Starting a Monitoring Task.
Step 4 Right-click and select Show Monitor Chart in the Table Data tab. The Monitor Information
Setting dialog box is displayed.
Step 5 Select the icon, monitoring object, and monitoring counter.
The system supports the compare display of multiple counters of the same object, or the compare
display of the same counter of multiple objects.
Step 6 Click OK. The Monitor Chart tab page is displayed.
The compare chart and detail chart of the started monitoring task are displayed.
Step 7 In the compare or detail chart, right-click and select Trend Analysis to view the Trend Chart
Parameter Setting dialog box.
Step 8 Set parameters for the trend chart.
Step 9 Click OK.
In the Monitor Task tab, click the Trend Chart tab to see the trend chart.
Click the Table Data tab. Right-click and select Show Trend Chart to see the trend chart. You
can also see the trend chart through the Trend Chart tab.
In the Trend Chart tab, right-click and select Exceptional Value Background for exceptional
values. The exceptional values are displayed in background color. In other words, when the
value for a time point is greater than the upper value or smaller than the lower value, the counter
value is highlighted in a background color.
In the Trend Chart tab, right-click and select Modify Diff Values to reset the upper and lower
values. The trend chart is refreshed automatically after you modify the upper and lower values.
----End
Related References
2.8.46 Parameters for Analyzing the Trend of a Monitoring Counter
Context
Two types of counters currently support this function, that is , the connected rate and the answer
rate.
Procedure
Step 1 Choose Monitor > Performance Monitor. The Performance Monitor window is displayed.
Step 2 Click the Monitor Task tab on the left of the window.
Step 3 Start a monitoring task.
Step 4 Select a monitoring record in Table Data.
Step 5 Right-click and select Show Monitor Chart to view the Monitor Information Setting.
Step 6 Select the icon, monitoring object, and monitoring counter.
Step 7 Click OK. The Monitor Chart tab is displayed.
The compare chart and detail chart of the started monitoring task are displayed.
Step 8 Perform the following operations to view the data analysis dialog box:
l Right-click on the compare chart. Select the counters to be scanned.
l Select a counter column in the detail counter chart. Right-click the counter and select Data
Scanning.
The list displays related counter records in the Analysis Table dialog box.
Select a counter record in the Analysis Table tab. Right-click and select Analysis Chart. Data
is displayed in pie or column charts in the Analysis Chart tab.
l The pie chart displays the counter data in a prompt box. The pie chart displays a maximum
of 20 counters. When the number of counters exceeds 20, the pie chart displays the first 20
counters sorted by counter value in the descending order.
l In the Analysis Chart tab, select Analysis Counter to set that the counter data is displayed
in the chart.
l In the Analysis Chart tab, click the Color cell behind the Analysis Counter check box to
set the color of the counter to be displayed in the chart.
l After you switch to another object, the relevant tables and charts are updated automatically.
----End
Procedure
Step 1 In Performance Monitor, select Monitor Chart or Trend Chart.
Step 2 Save the monitoring chart as a figure or a file.
Save as a figure. 1. Right-click the chart and select Save as. The Save dialog box is
displayed.
2. Save the chart as a photo. You can save charts only in .JPG format.
3. Click OK.
Save as a file. 1. Right-click the chart and select Export Data. The Save dialog box is
displayed.
2. Save the chart to a file. You can save the data exported from the chart to
a file in .TXT, .XLS, .CSV, or HTML format.
3. Click OK.
----End
Procedure
Step 1 In Performance Monitor, select Table Data.
Step 2 Right-click and select Export Data. The Save dialog box is displayed.
Step 3 Save the monitoring data.
You can save the data in the current data table into a file of either the HTML, TXT, CSV, or
XLS format.
Step 4 Click OK.
----End
Procedure
Step 1 In Performance Monitor, selectMonitor Chart or Trend Chart.
Step 2 Right-click the chart and select Print.
Step 3 Print the chart.
----End
By monitoring the configuration status of the three WRAN objects, that is, RNC, NodeB, and
cell, you can view the status information of the monitored object group. This helps you find out
and handle abnormal status.
2.6.1.4 RNC Monitoring Counters
You can view the monitoring counters and superstandard classic counters of an RNC monitoring
object. When creating an object group, you need set the upper and lower thresholds of monitoring
counters. The superstandard classic counters indicate the counter values exceeding set upper and
lower thresholds.
2.6.1.5 Cell Monitoring Counters
You can view the monitoring counters and superstandard classic counters of a cell monitoring
object. When creating an object group, you need set the upper and lower thresholds of monitoring
counters. The superstandard classic counters indicate the counter values exceeding set upper and
lower thresholds.
Monitored Group
You can group objects of the same type such as RNC, NodeB, and cell. An object group can be
monitored in real time by the M2000 only after being activated.
By using a monitored group, you can easily check the service information and monitor the
monitored group in real time.
Related Tasks
2.6.2 Managing Monitored Object Groups
Related References
2.8.6 Interface Description: Management of Monitored Object Groups
To better monitor these three kinds of objects, you can group the objects of the same type
together.
NOTE
Services depend on the monitored objects. You can view objects to check the monitored services, or locate
objects by monitored services.
l The RNC configuration status is on or off. Whether the RNC is disconnected from the
server is the key of M2000 monitoring.
l The NodeB configuration status is on or off. Whether the NodeB is disconnected from the
server is the key of M2000 monitoring.
l The configuration status of a cell can be blocked, deactivated, and disabled. When a cell is
in the inactive state, the cell cannot provide services. When a cell is in the blocked state,
the users accessing to the cell are not affected. When a cell is in the disabled state, users
cannot access the cell.
Related Tasks
2.6.3.4 Checking Detailed Information of Configuration Status
Related References
2.8.65 Parameters for Configuration Status
RRC Connection Setup Success Rate The number of successful RRC connections/
(service) the number of RRC connection set up
requests received by the RNC x 100%
NOTE
The number of RRC setup requests refers to the
number of requests for initiating services.
AMR RAB Assignment Success Rate The number of 'AMR RB setup complete'
messages received by the RNC from the UE
and the RAB assignment responses sent by
the RNC to the CN/the number of AMR RAB
assignment requests received by the RNC
from the CN x 100%
Video Call RAB Assignment Success Rate The number of 'VP RB setup complete'
messages received by the RNC from the UE
and the RAB assignment responses sent by
the RNC to the CN/the number of VP RAB
assignment requests received by the RNC
from the CN x 100%
CounterName Definition
Soft Handover Success Rate The number of Active Set Update Complete
messages received by the RNC/the number of
Active Set Update messages sent by the RNC
Inter-Freq Hard Handover Success Rate The number of physical link reconfiguration
messages received by the RNC/the number of
physical link reconfiguration messages sent
by the RNC
Related Tasks
2.6.5.1 Checking Values of RNC Monitoring Counters
counters. The superstandard classic counters indicate the counter values exceeding set upper and
lower thresholds.
Table 2-19 describes the monitoring counters of a cell monitoring object. You can view the
superstandard classic counters of a cell object group in the monitoring list.
RRC Connection Setup Success Rate The number of successful RRC connections/
(service) the number of RRC connection set up
requests received by the RNC x 100%
NOTE
The number of RRC setup requests refers to the
number of requests for initiating services.
AMR RAB Assignment Success Rate The number of 'AMR RB setup complete'
messages received by the RNC from the UE
and the RAB assignment responses sent by
the RNC to the CN/the number of AMR RAB
assignment requests received by the RNC
from the CN x 100%
Video Call RAB Assignment Success Rate The number of 'VP RB setup complete'
messages received by the RNC from the UE
and the RAB assignment responses sent by
the RNC to the CN/the number of VP RAB
assignment requests received by the RNC
from the CN x 100%
CounterName Definition
Inter-Freq Hard Handover Success Rate The number of physical link reconfiguration
messages received by the RNC/the number of
physical link reconfiguration messages sent
by the RNC
Related Tasks
2.6.5.5 Checking the Values of Cell Monitoring Counters
For a created object group, you can modify the name, monitoring objects, and monitoring
services.
2.6.2.4 Modifying Names of Object Groups
You can modify the names of the created object groups.
2.6.2.5 Copying Monitored Object Groups
You can copy an object group to create another one with the same monitoring objects and
services.
2.6.2.6 Suspending Monitored Object Groups
This describes how to suspend monitored groups. You can suspend a monitored group that need
not be monitored temporarily. The service status of a suspended object group is not monitored
by the M2000.
2.6.2.7 Activating Monitored Object Groups
This describes how to activate monitored object groups. You can activate a suspended object
group so that the M2000 can monitor its service status.
2.6.2.8 Deleting Monitored Object Groups
You can delete the unwanted monitored object groups to save the resources.
2.6.2.9 Checking Exceptions of Monitored Object Groups
Stopping the configuration or performance service or deleting the object may cause that the
system fails to monitor the monitored object groups. The M2000 can analyze the exceptions and
you can view the causes on the client.
Related Concepts
2.6.1.1 Monitored Group
Related References
2.8.6 Interface Description: Management of Monitored Object Groups
Prerequisite
You are authorized to monitor an object group.
Context
The objects in an object group should satisfy the following conditions:
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
Step 2 Click Add. The Object Group Type dialog box is displayed.
Step 3 Enter the name of the object group and choose the type.
Step 5 Select the services to be monitored, such as alarm, configuration status, performance KPI, and
cell status.
Step 6 Click Next. The Object List dialog box is displayed. Select the monitoring objects of the object
group.
----End
Prerequisite
l You have operation authorities of a object group.
l At least one monitoring object group is available.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
----End
Prerequisite
l You have operation authorities of a object group.
l At least one monitoring object group is available.
Context
Users including the admin can modify only the object group created by themselves.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
Step 2 Select an object group. Click Modify or right-click it and choose Modify on the shortcut menu.
The Object Group Type dialog box is displayed.
----End
Prerequisite
l You have operation authorities of a object group.
l At least one monitoring object group is available.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
Step 2 Select an object group. Click Rename or right-click it and choose Rename on the shortcut menu.
The Rename Object Group dialog box is displayed.
----End
Prerequisite
l You have operation authorities of a object group.
l At least one monitoring object group is available.
Context
You can copy the object group created by yourself or by other users. You can copy an object
group successfully only when you have operation authorities of all objects in the object group.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
Step 2 Select an object group. Click Copy or right-click it and choose Copy on the shortcut menu. The
Copy Object Group dialog box is displayed.
Step 3 Name the object group.
Step 4 Click OK.
----End
Prerequisite
l You have the right to operate the related object groups.
l At least one monitored object group exists.
Context
l A common user can suspend only the self-created object group.
l The user admin can suspend all the object groups in a system.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Group Management window
is displayed.
Step 2 Select one or more object groups and click Suspend. Alternatively, right-click the objects and
choose Suspend from the shortcut menu. The Confirm dialog box is displayed.
Step 3 Click Yes.
----End
Prerequisite
l You have the right to operate the related object groups.
Context
NOTE
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Group Management window
is displayed.
Step 2 Select one or more object groups and click Activate. Alternatively, right-click one or more object
groups and choose Activate from the shortcut menu.
----End
Prerequisite
l You have operation authorities of a object group.
l At least one monitoring object group is available.
Context
l Normal users can delete only the object groups that are created by themselves.
l The user admin can delete all the object groups.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
Step 2 Select an object group. Click Delete or right-click it and choose Delete on the shortcut menu.
The Confirm dialog box is displayed.
Step 3 Click Yes.
----End
Prerequisite
Exceptional object groups exist.
Procedure
Step 1 Choose Monitor > Object Groups Management . The Object Groups Management dialog
box is displayed.
Step 2 In the object list, select a monitoring object.
Step 3 Click Exception Cause or right-click it and choose Exception Cause on the shortcut menu.
The Exception Cause dialog box is displayed.
TIP
In the RAN Network Monitor window, you can also click to query the abnormal information of the
current object group.
----End
Context
NOTE
You can monitor object groups only after purchasing the license of the RAN network monitoring function.
blocking and unblocking are two states of a cell. A blocked cell can be unblocked while an
unblocked cell can be blocked.
Prerequisite
l You are authorized to perform the RAN network monitoring function.
l The activated monitoring object group is available.
Context
The object group supporting the RAN network monitoring function consists of the RNC, NodeB,
and cell.
Procedure
Choose Monitor > RAN Network Monitor. The RAN Network Monitor is displayed.
You can view the service information of the activated object group in the browse area.
----End
Related References
2.8.8 Interface Description: Monitoring Panel
Prerequisite
l You are authorized to perform RAN network monitoring.
l The monitoring object to be queried is already created.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 Right-click a blank space of the monitoring panel and select Search from the displayed shortcut
menu.
Step 3 In the Search dialog box, enter the related information of an object to be searched.
The information to be entered includes the object name, object type, search scope, and search
style.
TIP
Step 4 Click Search. The Search Result panel displays the result.
TIP
By double clicking a piece of result, you can find that it is associated with a specific monitoring object.
----End
Related References
2.8.69 Parameters for Searching for Objects
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one activated object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
----End
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one activated monitored object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
----End
Related Concepts
2.6.1.3 Configuration Status of Monitored Objects
Related References
2.8.65 Parameters for Configuration Status
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one activated RNC or cell object group is available, which has one or more
exceptional performance counters.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC or Cell monitored object group.
Step 3 From the object tree at the bottom left, select a monitored object.
----End
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one activated RNC object group is available, which has one or more performance
monitoring items.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
----End
Blocking/Unblocking Cells
blocking and unblocking are two states of a cell. A blocked cell can be unblocked while an
unblocked cell can be blocked.
Prerequisite
l The current user is authorized to perform RAN network monitoring.
l The activated cell object group is available. The number of blocked or unblocked cells
cannot be null.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select a cell monitoring object group.
Step 3 Click the configuration status pane.
The icons of locking and unlocking are illustrated at the right side of the pane.
Step 4 In the sell list, select a cell object.
Step 5 Right-click and select Unblock or block.
----End
Context
NOTE
You can check the information of the monitored objects only after purchasing the license of the RAN
network monitoring function.
You can view the basic configuration information on the Iu/Iur of the RNC.
2.6.4.4 Checking the Information on Specified Links of the Iu/Iur Interface
You can view the alarm information on a specified link of the Iu/Iur interface of RNC.
2.6.4.5 Checking the Information on the Iub Interface of the RNC
You can view the information such as the link and port on the Iub interface of the RNC.
2.6.4.6 Checking the Information on Specified Links of the Iub Interface
You can view the alarm information on a specified link of the Iub interface of RNC.
2.6.4.7 Checking the Information on Basic NodeB Configuration
You can view the basic configuration information of the NodeB, such as object name, NE type,
and IP address.
2.6.4.8 Checking the Information on Basic Cell Configuration
You can view the information on basic cell configuration, such as cell name, cell ID, and PSCH
power.
2.6.4.9 Checking the Information on CCH Configuration
This task is performed to check the basic information on the public channel configuration of
cells, such as cell name, cell ID, and maximum transmit power.
2.6.4.10 Checking the Information on Neighbors
The task is performed to check the information on the neighboring relation between cells.
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one RNC monitored object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select an RNC monitored object .
Step 4 View the basic configuration information on the Attribute tab page.
For descriptions of the parameters for basic RNC configuration, refer to 2.8.63 Parameters for
Checking the Information on Basic NodeB Configuration.
----End
Related References
2.8.56 Parameters for Checking the Information on Basic RNC Configuration
Prerequisite
l You are authorized to perform the RAN network monitoring.
l At least one RNC monitored object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitored object group.
Step 3 From the object tree at the bottom left, select an RNC monitored object.
Step 4 Click Distributing NodeBs and Cells to view the related information.
For descriptions of the distribution of NodeBs and Cells, refer to 2.8.62 Parameters for
Checking the Distribution of NodeB and Cells on the RNC.
----End
Related References
2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one RNC monitoring object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitored object group.
Step 3 From the object tree at the bottom left, select an RNC monitored object group.
Step 4 Click Iu/Iur Interface. Select a signaling point from Destination Signaling Point.
Step 5 Click Attribute and view the basic configuration information on Iu/Iur.
For details of Iu/Iur attribute parameters, refer to 2.8.57 Parameters for Checking the
Information on the Iu/Iur of the RNC.
----End
Related References
2.8.57 Parameters for Checking the Information on the Iu/Iur of the RNC
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one RNC monitoring object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select an RNC monitored object group.
Step 4 Click Iu/Iur Interface, and select a signaling point from Destination Signaling Point.
----End
Related References
2.8.58 Parameters for Checking the Information on Specified Links of the Iu/Iur Interface
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one RNC monitoring object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select an RNC monitored object group.
Step 4 Click the Iub Interface tab to view the basic configuration information.
----End
Related References
2.8.59 Parameters for Checking the Information on the Iub Interface of the RNC
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one RNC monitoring object group is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select an RNC monitored object group.
Step 4 Click Iub Interface to view the information on the RNC object group.
For descriptions of Iub Interface parameters, refer to 2.8.60 Parameters for Checking the
Information on Specified Links of the Iub Interface.
----End
Related References
2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one activated NodeB monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select a NodeB monitored object group.
Step 4 Click the Attribute tab to view the information on basic NodeB configuration.
For descriptions of the parameters for the NodeB, refer to 2.8.63 Parameters for Checking the
Information on Basic NodeB Configuration.
----End
Related References
2.8.63 Parameters for Checking the Information on Basic NodeB Configuration
Prerequisite
l You are authorized to perform the RAN network monitoring.
l At least one cell monitored object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select a cell monitored object group.
Step 3 From the object tree at the bottom left, select a cell monitored object.
Step 4 Click the Attribute tab to view the basic configuration information.
For descriptions of parameters, refer to 2.8.64 Parameters for Checking the Information on
Basic Cell Configuration.
----End
Related References
2.8.64 Parameters for Checking the Information on Basic Cell Configuration
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one active cell object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 Select an active cell object group on the monitoring panel.
Step 3 Select an active cell object in the object tree to the lower left.
Step 4 Click the Public Channel Configuration tab to view the basic configuration information of the
common channel of the cell object.
For descriptions of parameters, refer to 2.8.66 Parameters for Checking the Information on
CCH Configuration.
----End
Related References
2.8.66 Parameters for Checking the Information on CCH Configuration
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one active cell object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 Select an active cell object in the object tree to the lower left.
Step 4 Click Neighboring Relation to view the neighboring relation of the cell object.
For details of parameters about the neighboring relation between cells, refer to 2.8.67
Parameters for Checking the Information on Neighbors.
----End
Related References
2.8.67 Parameters for Checking the Information on Neighbors
Context
NOTE
You can check the status of the monitored objects only after purchasing the license of the RAN network
monitoring function.
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one active RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select an RNC object .
Step 4 Click KPI Counter to check the KPI of the RNC object group.
For details of KPI Counter parameters, refer to 2.8.55 Parameters for Checking Values of
RNC Monitoring Counters.
----End
Related References
2.8.55 Parameters for Checking Values of RNC Monitoring Counters
2.6.1.4 RNC Monitoring Counters
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one active RNC object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 Select an active RNC object in the object tree to the lower left.
Step 4 Click E1T1 Status to check the E1/T1 status of the RNC object group.
For descriptions of parameters, refer to 2.8.61 Parameters for Checking the E1/T1 Status of
the RNC.
----End
Related References
2.8.61 Parameters for Checking the E1/T1 Status of the RNC
Checking the Current Alarm Information on Specified Links of the Iu/Iur Interface
This task is performed to check the current alarm information on specified links of the Iu/Iur
interface.
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one active RNC object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 Select an active RNC object group on the monitoring panel.
Step 3 Select an active RNC object in the object tree to the lower left.
Step 4 Click Iu/Iur Interface and select a link.
Step 5 Click Current Alarm to check the alarm information on the current link.
For details of alarm parameters about the current links of the Iu/Iur interface, refer to 2.8.60
Parameters for Checking the Information on Specified Links of the Iub Interface.
----End
Checking the Current Alarm Information on Specified Links of the Iub Interface
This task is performed to check the current alarm information on specified links of the Iub
interface.
Prerequisite
l You are authorized to perform the RAN network monitoring.
l At least one active RNC object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 Select an active RNC object group on the monitoring panel.
Step 3 Select an active RNC object in the object tree to the lower left.
Step 4 Click Iub Interface and select a link.
Step 5 Click Current Alarm to check the alarm information on the current link.
For details of alarm parameters about the current links of the Iub interface, refer to 2.8.60
Parameters for Checking the Information on Specified Links of the Iub Interface.
----End
Prerequisite
l You are authorized to perform the RAN network monitoring.
l At least one cell monitored object is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select a cell monitoring object.
Step 4 Click KPI Counter to view the detailed information of KPI counters.
For descriptions of the parameters, refer to 2.8.68 Parameters for Checking the Values of Cell
Monitoring Counters.
----End
Related References
2.8.68 Parameters for Checking the Values of Cell Monitoring Counters
2.6.1.5 Cell Monitoring Counters
Prerequisite
l You are authorized to perform the RAN network monitoring.
l At least one cell monitored object is available.
Procedure
Step 1 Click Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree at the bottom left, select a cell monitored object.
Step 4 Click Current Alarm to view the alarm statistics of the cell.
For descriptions of parameters, refer to 2.8.60 Parameters for Checking the Information on
Specified Links of the Iub Interface.
----End
Context
NOTE
You can summarize the alarms of monitored groups only after purchasing the license of the RAN network
monitoring function.
Prerequisite
l You are authorized to perform RAN network monitoring.
l At least one activated RNC monitoring object group are available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 Select an RNC object from the object tree to the lower left.
Step 4 Click Alarm Statistics.
Step 5 In Statistic Style, select Statistic by Level.
For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/
NodeB.
Step 6 Set a time type for statistics.
Two time types are available. You can set one as required.
l Server Time: is used to measure the current alarms of the RNC
l NE Time: is the actual time of the RNC and is used to measure the current alarms
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitoring object group.
Step 3 Select an RNC object from the object tree to the lower left.
Step 4 Click Alarm Statistics.
Step 5 In Statistic Style, select Statistic by ID.
For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/
NodeB.
Step 6 Set a time type for statistics.
Two time types are available. You can set one as required.
l Server Time: is used to measure RNC alarms
l NE Time: is the actual time of the RNC and is used to measure RNC alarms
If you do not set start time, use the default system setting.
Step 8 Click Statistic.
On the lower panel, you can view the alarms calculated according to alarm IDs.
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitoring object group.
Step 3 Select an RNC object from the object tree to the lower left.
Step 4 Click Alarm Statistics.
Step 5 In Statistic Style, select Statistic by TopN of NodeB.
For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/
NodeB.
Step 6 In TopN, set a number.
Step 7 Set a time type for statistics.
Two time types are available. You can set one as required.
l Server Time: is used to measure the first n alarms of the RNC
l NE Time: is the actual time of the RNC and is used to measure the first n alarms
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 Select an RNC object from the object tree to the lower left.
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select an RNC monitoring object group.
Step 3 From the object tree in the left lower part, select an RNC object.
Step 4 Click Alarm Statistics.
Step 5 In Statistic Style, select Statistic by TopN of SAAL.
For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/
NodeB.
Step 6 In TopN, set a number.
Step 7 Set a time type for statistics.
Two time types are available. You can set one as required.
l Server Time: is used to measure the first n alarms of the RNC
l NE Time: is the actual time of the RNC and is used to measure the first n alarms of the RNC
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated RNC monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated NodeB monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 2 On the monitoring panel, select a NodeB monitoring object group.
Step 3 From the object tree in the left lower part, select a NodeB object.
Step 4 Click Alarm Statistics.
Step 5 In Statistic Style, select Statistic by Level.
For descriptions of parameters, refer to 2.8.54 Parameters for Summarizing Alarms of RNC/
NodeB.
Step 6 In TopN, set a number.
Step 7 Set a time type for statistics.
Two time types are available. You can set one as required.
l Server Time: is used to measure the current alarms of the NodeB
l NE Time: is the actual time of the NodeB and is used to measure the current alarms
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
Prerequisite
l You are authorized to perform RAN network monitoring.
l The activated NodeB monitoring object group is available.
Procedure
Step 1 Choose Monitor > RAN Network Monitor. The RAN Network Monitor window is displayed.
Step 3 From the object tree in the left lower part, select an NodeB object.
----End
Related References
2.8.54 Parameters for Summarizing Alarms of RNC/NodeB
You can set the parameters for the M2000 performance monitoring to specify the threshold of
the CPU usage, memory usage, and refresh period of the performance monitoring. When the
CPU usage and memory usage reach the thresholds, the M2000 raises corresponding alarms,
and the corresponding icon on the Performance Monitor tab is displayed in red.
2.7.1.3 Setting the Parameters for the M2000 Hard Disk Monitoring
You can set the parameters for the M2000 hard disk monitoring to specify the threshold of the
hard disk usage and the refresh period of the hard disk monitoring. When the M2000 hard disk
usage reaches the threshold, the M2000 raises an alarm, and the corresponding icon on the Hard
Disk Monitor tab is displayed in red.
2.7.1.4 Setting the Parameters for the M2000 Database Monitoring
You can set the parameters for the M2000 database monitoring to specify the threshold of the
database usage and the refresh period of the database monitoring. When the M2000 database
usage reaches the threshold, the M2000 raises an alarm, and the corresponding icon on the
Database Monitor tab is displayed in red.
2.7.1.5 Setting the Parameters for the M2000 Service Monitoring
By setting services, you can monitor parameters, specify the displayed prompts of the service
monitoring, and refresh the interval. After the displayed monitoring information is set and when
the service is changed, the corresponding prompts are displayed. At the same time, the service
is updated according to the specified interval. You can set the parameters for the M2000 service
monitoring to specify the service refresh interval. When the service refresh interval reaches the
threshold, the M2000 refreshes the monitored services.
Related References
2.8.70 Parameters for Setting Thresholds of the M2000 Server
Procedure
Step 1 Choose Monitor > System Monitor > Settings .
Step 2 In the System Monitor Settings window, click the Performance Monitor tab to set the property
values.
----End
Related References
2.8.70 Parameters for Setting Thresholds of the M2000 Server
Procedure
Step 1 Choose Monitor > System Monitor > Settings .
Step 2 In the System Monitor Settings window, click the Hard Disk Monitor tab to set the property
values.
Step 3 Click OK.
----End
Related References
2.8.70 Parameters for Setting Thresholds of the M2000 Server
Procedure
Step 1 Choose Monitor > System Monitor > Settings .
Step 2 In the System Monitor Settings window, click the Database Monitor tab to set the property
values.
Step 3 Click OK.
----End
Related References
2.8.70 Parameters for Setting Thresholds of the M2000 Server
Procedure
Step 1 Choose Monitor > System Monitor > Settings .
Step 2 In the System Monitor Settings window, click the Service Monitor tab to set the property
values.
----End
Context
l If you set a threshold of the performance and an item reaches the threshold, the icon of the
item is displayed in red.
l Right-click in the System Monitor Browser window and choose Refresh to refresh the
window.
Procedure
Step 1 Choose Monitor > System Monitor > Browser .
Step 2 In the System Monitor Browser window, click the Performance Monitor tab to view the server
performance.
----End
Related References
2.8.71 Parameters for Monitoring Performance of the M2000 Server
Context
l If you set a threshold of the hard disk and an item reaches the threshold, the icon of the
item is displayed in red.
l Right-click in the System Monitor Browser window and choose Refresh to refresh the
window.
Procedure
Step 1 Choose Monitor > System Monitor > Browser .
Step 2 In the System Monitor Browser window, click the Hard Disk Monitor tab to view the status
of the server hard disk.
Step 3 Optional: Click Save As.
The monitoring data is saved in the local disk.
----End
Related References
2.8.72 Parameters for Monitoring Hard Disk of the M2000 Server
Context
l If you set a threshold of the database and then an item reaches the threshold, the icon of
the item is displayed in red.
l Right-click in the System Monitor Browser window and choose Refresh to refresh the
window.
l When the database space is insufficient, you can expand the space. The M2000, however,
only supports the extension of the Sybase database at present.
Procedure
Step 1 Choose Monitor > System Monitor > Browser .
Step 2 In the System Monitor Browser window, click the Database Monitor tab to view the status
of the server database.
NOTE
The M2000 server runs in Solaris or SuSE Linux. Solaris uses Sybase, and SuSE Linux uses DB2. The status
of the databases that you monitor varies with the database type.
----End
Related References
2.8.73 Parameters for Monitoring Database of the M2000 Server
Context
l If a service is abnormal, its icon is displayed in red.
l Right-click in the System Monitor Browser window and choose Refresh to refresh the
window.
Procedure
Step 1 Choose Monitor > System Monitor > Browser .
Step 2 In the System Monitor Browser window, click the Service Monitor tab to view the services
on the server.
----End
Related References
2.8.74 Parameters for Monitoring Services of the M2000 Server
Context
l Only the running processes are displayed in the monitoring content.
l Right-click in the System Monitor Browser window and choose Refresh to refresh the
window.
Procedure
Step 1 Choose Monitor > System Monitor > Browser .
Step 2 In the System Monitor Browser window, click the Process Monitor tab to view the server
processes.
----End
Related References
2.8.75 Parameters for Monitoring Process of the M2000 Server
This describes the parameters in the Query User Defined Alarm dialog box. It provides a
reference for future query.
2.8.29 Parameters for Querying the Binding of a User-Defined Alarm
This describes the parameters in the Query Alarm Binding dialog box. It provides a reference
for future query.
2.8.30 Parameters for Adding/Modifying the Binding of a User-Defined Alarm
This describes the parameters binding a user-defined alarm. When adding or modifying the
binding of a user-defined alarm, you can perform the related settings by referring to the parameter
descriptions.
2.8.31 Parameters for Setting the Alarm Box
This section describes the parameters in the Alarm Box Settings dialog box. You can refer to
these parameters when you set the alarm box.
2.8.32 Parameters for Setting Alarm Remote Notification Rules
This section describes the parameters for setting the remote notification rules. You can refer to
this section when you set alarm remote notification rules.
2.8.33 Parameters for Setting Notification by Email
This section describes the parameters in the Add Notify Device Communication Settings
dialog box. You can refer to these parameters when you set the remote notification by Email.
2.8.34 Parameters for Advanced Settings of Notification by Email
This section describes the parameters in the Communication Settings dialog box. You can refer
to these parameters when you set advanced parameters of alarm notification by Email.
2.8.35 Parameters for Setting Notification by Modem
This section describes the parameters in the Add Notify Device Communication Settings
dialog box. You can refer to these parameters when you set the remote notification by modem.
2.8.36 Parameters for Advanced Settings of Notification by Modem
This section describes the parameters in the Notify Device Communication Settings dialog
box. You can refer to these parameters when you set the advanced parameters of notification by
modem.
2.8.37 Parameters for Setting Notification by SMS Gateway
This section describes the parameters in the Add Notify Device Communication Settings
dialog box. You can refer to these parameters when you set the alarm notification by SMS
gateway.
2.8.38 Parameters for Advanced Settings of Notification by SMS Gateway
This section describes the parameters in the Notify Device Communication Settings dialog
box. You can refer to these parameters when you set the advance parameters for notification by
SMS gateway.
2.8.39 Parameters for Setting Simple Correlation Rules
This section describes the parameters in the Add Simple Correlation Rule dialog box. You can
refer to these parameters when you set or modify the simple correlation rules of alarms.
2.8.40 Parameters for Setting Advanced Correlation Rules
This section describes the parameters in the Add Advanced Correlation Rule dialog box. You
can refer to these parameters when you set or modify the advanced correlation rules of alarms.
2.8.41 Parameters for the Basic Attributes of Auto-Triggering Tasks
This describes the related parameters on the Basic Attribute tab page in the Attribute dialog
box. You can refer to these parameters when you set auto-triggering basic attributes.
This part describes the parameters about the information on the Iub interface in the RNC object
group.
2.8.60 Parameters for Checking the Information on Specified Links of the Iub Interface
This part describes the basic parameters about the information on specified links of the Iub
interface in the RNC object group.
2.8.61 Parameters for Checking the E1/T1 Status of the RNC
This part describes the parameters about the E1T1 status of the RNC.
2.8.62 Parameters for Checking the Distribution of NodeB and Cells on the RNC
This part describes the parameters about the distribution of NodeB and cells on the RNC.
2.8.63 Parameters for Checking the Information on Basic NodeB Configuration
This part describes the parameters about the information on basic configuration of the NodeB
object group.
2.8.64 Parameters for Checking the Information on Basic Cell Configuration
This describes the parameters for checking the information on basic cell configuration.
2.8.65 Parameters for Configuration Status
This part describes the parameters related with the configuration status of the RNC, NodeB and
cell.
2.8.66 Parameters for Checking the Information on CCH Configuration
This part describes the parameters related to the basic configuration of the common channel in
a cell.
2.8.67 Parameters for Checking the Information on Neighbors
This describes the parameters for checking the information on neighbors.Three types of
neighboring cells are available: Intra-frequency neighboring cell, inter-frequency neighboring
cell, and GSM neighboring cell.
2.8.68 Parameters for Checking the Values of Cell Monitoring Counters
This part describes the parameters related to cell monitoring counters.
2.8.69 Parameters for Searching for Objects
In case that many monitored objects exist, you can search the related monitored objects by using
the fuzzy search method. Then you can locate the object quickly.
2.8.70 Parameters for Setting Thresholds of the M2000 Server
This section describes the parameters of system monitor settings. You can refer to these
parameters when you set the server thresholds.
2.8.71 Parameters for Monitoring Performance of the M2000 Server
This section describes the parameters of the query result displayed in the Performance
Monitor tab.
2.8.72 Parameters for Monitoring Hard Disk of the M2000 Server
This section describes the parameters of the query result displayed in the Hard Disk Monitor
tab.
2.8.73 Parameters for Monitoring Database of the M2000 Server
This section describes the parameters of the query result displayed in the Database Monitor
tab.
2.8.74 Parameters for Monitoring Services of the M2000 Server
This section describes the parameters of the query result displayed in the Service Monitor tab.
2.8.75 Parameters for Monitoring Process of the M2000 Server
This section describes the parameters of the query result displayed in the Process Monitor tab.
Highlighting Alarms
You can specify the time after which an alarm is regarded as a long-period alarm if it is not
handled. A long-period alarm is highlighted on the interface, as shown in Figure 2-7.
Alarm Board
You can customize the settings of the alarm board, as shown in Figure 2-10.
Alarm Box
You can specify the filtering conditions of the alarm box. Thus, only those wanted alarms are
sent to the alarm box and displayed through sounds or visions. Figure 2-11 shows the alarm box
settings.
Correlation Analysis
l After you set the alarm correlation rules, the M2000 abandons or shields the alarms that
satisfy the conditions. Figure 2-13 shows the interface.
l After you set advanced alarm correlation rules, the system can shield the alarms that satisfy
the conditions or re-define the alarm severity. In this case, you can focus on the main alarms
to quickly locate and solve the problems. Figure 2-14 shows the interface.
Automatic Acknowledgement
The automatic acknowledgement interface provides the function of delaying and immediate auto
acknowledging of unacknowledged fault alarms and event alarms. After you activate the auto
acknowledge function, the system automatically acknowledge an event or fault alarm that meets
the conditions. Figure 2-16 shows the interface.
Table 2-20 Description of the tabs i the NE Alarm Settings dialog box
Tab Description
User Defined Alarm The User Defined Alarm tab consists of Alarm Definition and
Alarm Binding. You can self-define a new alarm and bind it to
a port of a cabinet, subrack, or slot of an NE. You can also self-
define the binding relationship. For details, refer toManaging
User-Defined Tasks.
Alarm shielding In the Alarm Shielding tab, you can set shielding attribute for
unwanted or wanted alarms to shield or release the shielding.
Then you can forbid NEs reporting shielded alarms or allow
NEs reporting alarms not shielded.
Alarm Level Redefinition In the Alarm Level Redefinition tab, you can change the
severity of alarms based on the actual effect on the system. For
example, you can degrade the severity level of relatively
unimportant alarms or upgrade the severity of relatively
important alarms.
Alarm Query
The alarm query interface consists of the event alarm query tab, the history fault alarm tab, the
current fault alarm query, the shielded fault alarm query, the shielded event alarm query, the
browse current fault alarms by status tab, and the browse event alarms by status tab. After setting
the conditions, you can view the detailed information in the window. Figure 2-20 shows the
interface.
(1) Navigation tree: shows the NEs, object sets, and monitoring tasks in a tree.
(3) Counter result display area: displays the counter result of the selected time by counter or
object.
(4) Object name display area: displays the short names and full names of the objects. Short
names are automatically assigned by the system, for example, SO1. Full names are the actual
names of the objects, for example, RNC_64.
(5) Monitoring chart: select multiple counters of an object or the same counter of multiple
objects to compare the monitoring result. The compare result is shown in a line chart.
(6) Counter results: displays the counter results in the compare chart separately in a bar chart.
(7) Zooming button: to zoom in, zoom out, or restore the compare chart.
(8) Trend figure: displays the performance monitoring results in a trend chart.
Related Tasks
2.5 Monitoring NEs in Real Time
l (1) Object group list: lists all the object groups and their related information, such as creator,
name, type, and status.
l (2) Detailed information: lists the detailed information of the object groups. The
information are about function type and monitoring object.
– Function Type shows the monitored services of object groups.
– Monitoring Object lists all of the monitored objects of the object group.
l (3) Function key: includes Add, Modify, and Delete.
Related Concepts
2.6.1.1 Monitored Group
Related Tasks
2.6.2 Managing Monitored Object Groups
l (1) RAN network monitoring area: shows all of the object groups that are activated. One
panel represents an object group. For details about the implication of panel legend, refer to
the description column on the right part of this window.
l (2) Detailed service information: shows the information of services. These services are
depend on object type. The monitored services vary with types of the objects.
Related Tasks
2.6.3.1 Browsing Monitoring Panel
Performance You can check the basic information about current login server, such as
Monitor Server Name, Server Status, OS, Free Physical Memory(KB), Total
Physical Memory(KB), Free Swap Memory(KB), Total Swap Memory
(KB), CPU Usage Rate(%) and Memory Usage(%).
Hard Disk You can check the information about the hard disk of current login server,
Monitoring such as Server Name, Server Status, OS, Partition(Mounted Path), Total
Size(KB), Used Size(KB), Free Size(KB), Used Rate(%), and Status.
Database You can check the information about the database of current login server,
Monitor such as DataBase Name, Server Name, OS, Total Data Space(KB), Used
Space(KB), Free Space(KB), Used Rate(%), Total Log Space(KB), Free
Log Space(KB), and Status.
Service You can check the information about running services of current login server,
Monitor such as Agent Name, Service, Service Description, Status, Auto Restart
Count, Service Start Time, and Server Name.
Process You can check the information about service proxy of current login server,
Monitor such as Agent Name, Process ID, Handle Number, CPU Usage Rate
(%), Memory Usage(KB), DB Connection Number, and Thread
Number.
NE Monitor You can check the information about all NEs, such as NE Name, NE Type,
Alarm Status, and Connection Status.
Serial Number The network serial number of an alarm. It is the keyword of an alarm
record and uniquely identifies an alarm.
l Intermittent alarm .
Parameter Description
Link Type The type of a link in the network. Each link type corresponds to a unique
link.
The following link types are available:
l BICCSCTPLINK
l DataLink
l H248Link
l M3UALink
l MTP3BLink
l MTP3Link
Equipment Alarm The serial number of an alarm device. In the same device, a unique alarm
Serial Number can be defined according to the serial number.
Category The category available in the network, including fault alarms and event
alarms. Both fault alarms and event alarms are used to notify users of
exceptional situations. Fault alarms indicate that you need to take
measures to handle the fault.
Type The type of an alarm in the network, such as power system, trunk system,
and OMC.The name of an alarm in the network, through which it is
possible to quickly locate the basic information of the alarm. For
example, if it is a database threshold alarm, users can know that the alarm
is generated from the database by its name.
Clearance Type The clearance type of an alarm, such as, normal clearance, manual
clearance, and configuration clearance.
Parameter Description
Object Instance The name of the object that generates an alarm. If the object is available
Type on the topology view, the related object name is displayed. Otherwise,
the NE name is displayed.
Operation Impact Shows whether the alarm has impact on the services. The value can be
Flag Yes,No, or Unknown.
Additional The additional information about an alarm, for example, the alarm
Information causes.
Location The information is used to quickly locate the reason why an alarm is
Information generated, and analyze the way of handling alarms. When an alarm is
reported, the system automatically fills in the location information
which operators have configured for each NE. If operators do not
configure the location information for an NE, the system replaces it with
the information configured in Explanation and Knowledge Database.
Related Tasks
2.2.1 Setting Columns in an Alarm Interface
Base Settings
Name Description Settings
Related Tasks
2.2.6 Setting Alarm Real-Time Monitoring
Basic Settings
Name Description Operation
Advanced Settings
The Ne District tab in the Advanced dialog box displays the NEs based on districts. You can
select the NEs on which you want to query or browse. The Ne District information is added to
the query or browsing result. The NEs that are queried or browsed are the intersection of the
NEs set on the Ne District and Alarm Source tab pages.
You can set the query mode on the Browse Setting tab page of Advanced dialog box. You can
select Browse all alarms, Browse debug alarms. or Browse normal alarms.
The following is the description of the parameters on the Default tab page of the Advanced
dialog box.
Related Tasks
2.2.5 Monitoring Alarms Through the Topology View
2.2.7 Querying Alarms
2.2.7.1 Querying Current Fault Alarms
2.2.7.3 Querying Event Alarms
2.2.7.2 Querying History Fault Alarms
2.2.7.4 Querying the Masked Fault Alarms
2.2.7.5 Querying the Masked Event Alarms
Statistical Items
Name Description Operation
Basic Settings
Name Description Operation
Advanced Settings
The Ne District tab in the Advanced dialog box displays the NEs based on districts. You can
select the NEs on which you want to collect statistics. The Ne District information is added to
the statistical result. The NEs on which the statistics is collected is the intersection of the NEs
set on the Ne District and Alarm Source tab pages.
You can set the query mode on the Browse Setting tab page of Advanced dialog box. You can
select Browse all alarms, Browse debug alarms. or Browse normal alarms.
The following is the description of the parameters on the Default tab page of the Advanced
dialog box.
Related Tasks
2.2.8 Collecting Alarm Statistics
Parameter Description
Parameter Description
Search by Name Searching NEs by the NE name. It supports fuzzy search. You
can enter keyword of the NE name to search the NE.
Parameter Description
Group by NE Type If you select the option, the NEs in the Select NE navigation
tree are displayed by NE type.
Related Tasks
2.2.7 Querying Alarms
2.4.2 Querying the Shielding of an NE Alarm
2.4.5 Querying the Redefinition of an NE Alarm Level
2.4.7.1 Querying a User-Defined Alarm
2.4.8.1 Querying the Binding of a User-Defined Alarm
Parameters
Name Description Settings
Related Tasks
2.2.2 Manually Synchronizing NE Alarms
2.2.7.1 Querying Current Fault Alarms
2.2.7.3 Querying Event Alarms
Alarm Names
Name Description Settings
Related Tasks
2.2.8.1 Collecting Statistics on Fault Alarms
2.2.7.1 Querying Current Fault Alarms
2.2.6 Setting Alarm Real-Time Monitoring
Parameters
Name Description Settings
Related Tasks
2.2.11.7 Recording Alarm Handling Experience
Parameters
Name Description Settings
Related Tasks
2.3.5 Setting Alarm Auto Acknowledgement
Related Tasks
2.3.4 Setting Alarm Filter Rules
Parameters
Name Description
Name Description:
Name of an alarm in the network. The basic information of the alarm
can be quickly located by alarm name. For example, if it is a database
threshold alarm, you can know that the alarm is raised from the
database based on its name.
Level Description:
Alarm levels, including critical, major, minor, and warning.
Clearance Description:
Clearance status of a fault alarm or event alarm, such as Unclear.
Acknowledgement Description:
Acknowledgement status of a fault alarm or event alarm, such as
Unacknowledged.
Acknowledgement Description:
Time Time when an event alarm or a fault alarm is acknowledged.
Identifier Description:
Identifies the status of Alarm comment. If an alarm is reported, the
status is displayed as Have comment. Otherwise, the field is blank.
Name Description
NE Type Description:
Type of an NE in the network. Each NE type corresponds to a unique
NE.
Category Description:
Categories of alarms in the network, including fault alarms and event
alarms.
Type Description:
Source of an alarm in the network, such as Power System, Trunk
System, or Internal.
Additional Description:
Information Additional information on an alarm.
Name Description
MO Object The managed object that raises an alarm, such as the board name.
Related Tasks
2.2.11.3 Viewing Alarm Details
Group by NE Type None If you select this item, in the Root tree, the NEs
are displayed in groups based on NE types.
NE Name None
Name of an NE. Click and select
the NE in the displayed dialog box.
Start Alarm ID l For NodeB NEs, the value The start alarm ID for the alarm
ranges from 1 to 32000 filter.
and from 65334 to 65534.
l For non-NodeB NEs, the
value ranges from 1 to
32000.
End Alarm ID l For NodeB NEs, the value The end alarm ID for the alarm
ranges from 1 to 32000 filter.
and from 65334 to 65534.
l For non-NodeB NEs, the
value ranges from 1 to
32000.
Maximum Record Numeric type. Ranges from The maximum count of the returned
Count 1 to 1000. The default value records.
is 1000.
Related Tasks
2.4.2 Querying the Shielding of an NE Alarm
Group by Alarm Type None If you select this item, in the Select
Alarm navigation tree, the NEs are
displayed in groups based on NE types.
The alarm types include power system,
environment system, and signaling
system.
Group by Alarm Level None If you select this item, in the Select
Alarm navigation tree, the NEs are
displayed in groups based on alarm
levels. Alarm severity levels are:
Critical, Major, Minor, and Warning.
Group by Alarm Category None If you select this item, in the Select
Alarm navigation tree, the NEs are
displayed in groups based on alarm
types. The alarms can be classified into
two types: fault alarm and event alarm.
Group by Alarm Type None If you select this item, in the Select
Alarm navigation tree, the NEs are
displayed in groups based on NE types.
The alarm types include power system,
environment system, and signaling
system.
Group by Alarm Level None If you select this item, in the Select
Alarm navigation tree, the NEs are
displayed in groups based on alarm
levels. Alarm severity levels are:
Critical, Major, Minor, and Warning.
Group by Alarm Category None If you select this item, in the Select
Alarm navigation tree, the NEs are
displayed in groups based on alarm
types. The alarms can be classified into
two types: fault alarm and event alarm.
Related Tasks
2.4.1 Shielding an NE Alarm
Parameters
Name Description Settings
Related Tasks
2.3.6 Setting Redefinition of Alarm Level
Parameter Description
Parameter Description
Search by Name In Search by Name, enter the alarm name you want to
query.
Fuzzy search is supported.
Redefined Level You can choose a new alarm level from the drop-down list
under this field.
Original alarm severities are not included in the drop-down
list.
Related Tasks
2.4.4 Redefining the Level of an NE Alarm
2.4.6 Modifying the Setting of NE Alarm Level Redefinition
Parameters
Name Description
ID Description:
Name of the redefined alarm.
Enable Description:
Whether to enable the alarm redefinition rules.
Name Description
Category Description:
Alarm category.
Memo Description:
Remarks of the alarm redefinition rule.
Related Tasks
2.3.6 Setting Redefinition of Alarm Level
Parameters
Parameter Value Range Description
NE Name None.
Name of an NE. Click and select the
NE in the displayed dialog box.
Start Alarm ID Numeral. The start alarm ID for the alarm level
Value range: 1 to 32000. redefinition.
End Alarm ID Numeral. The end alarm ID for the alarm level
Value range: 1 to 32000. redefinition.
Alarm Level l Critical You can select more than one alarm
l Major levels. If you do not select any alarm,
alarms of all these levels are queried.
l Minor
l Warning
Related Tasks
2.4.5 Querying the Redefinition of an NE Alarm Level
Parameter Description
Parameter Value Range Description
NE Type NE type and NE For the NodeB, you can select only an
NE type. For the MSCe and MGW,
you can select either an NE type or an
NE.
Level The following four severity You can select only one severity level.
levels are listed in the drop-
down list:
l Critical
l Major
l Minor
l Warning
Types Environment system or the The parameter is set by default and the
OMC. setting cannot be modified.
l If NE Type is set to an NE
type other than OMC, this
option is Environment
System.
l If NE Type is set to OMC,
this option is OMC.
Related Tasks
2.4.7 Defining an NE Alarm
2.4.7.2 Adding a User-Defined Alarm
Parameter Description
Parameter Value Range Description
Level l Critical You can choose more than one items. If you do not
l Major select any alarm level, all alarms will be queried.
l Minor
l Warning
Related Tasks
2.4.7.1 Querying a User-Defined Alarm
Parameter Description
Parameter Value Range Description
NE Name None
Name of an NE. Click and select the NE in
the displayed dialog box.
Cabinet Enumerated Type Refers to the number of the cabinet to which the
l For NodeB, the NE alarm is to be bound.
value range is 0-1.
l For MSCe, the
value range is 0-4.
l For DBS3800, the
value range is 0-1.
l For MSC Server,
the value range is
0-1.
Slot Numeric type. Ranges Applicable only to the NodeB and DBS3800.
from 0 to 255. Refers to the number of the slot to which the NE
alarm is to be bound.
Port Numeric type. Refers to the number of the port to which the NE
l For NodeB, the alarm is to be bound.
value range is
0-255.
l For MSCe, the
value range is 0-5.
l For DBS3800, the
value range is
0-255.
l For MSC Server,
the value range is
0-5.
Related Tasks
2.4.8.1 Querying the Binding of a User-Defined Alarm
Parameter Description
Parameter Value Range Description
Cabinet Enumerated Type Refers to the number of the cabinet to which the
l For NodeB, the value NE alarm is to be bound.
range is 0-1.
l For MSCe, the value
range is 0-4.
l For DBS3800, the
value range is 0-1.
l For MSC Server, the
value range is 0-4.
Subrack Numeric type. Ranges Applicable only to the NodeB. Refers to the
from 0 to 255. number of the subrack to which the NE alarm is
to be bound.
Slot Numeric type. Ranges Applicable only to the NodeB. Refers to the
from 0 to 255. number of the slot to which the NE alarm is to
be bound.
Port Numeric type. Refers to the number of the port to which the NE
l For NodeB, the value alarm is to be bound.
range is 0-255.
l For MSCe, the value
range is 0-5.
l For DBS3800, the
value range is 0-255.
l For MSC Server, the
value range is 0-5.
Port Type Select the value from the Type of the signal received by the port which is
drop-down list. to be bound to the NE alarm, such as Bool and
Value.
Alarm Voltage Select the value from the This parameter is applicable only when Port
drop-down list. Type is Bool. Two types are available, that
is,High and Low.
Upper Numeric type. The value This parameter is applicable only when Port
Threshold range depends on the Type is Value. It indicates the upper limit for
NE. generating alarms. An alarm is reported to the
M2000 when signals received by the port reaches
this value.
Lower Numeric type. The value This parameter is applicable only when Port
Threshold range depends on the Type is Value. An alarm is restored on the
NE. M2000 when signals received by the port are
smaller than this value.
Port Switch Default value, such as The default setting is Open. After you delete an
Open and Close. alarm binding, Port Switch is Close. Open
indicates that user-defined alarm binding is takes
effect. Close indicates that alarms are not bound.
Related Tasks
2.4.8 Binding a User-Defined Alarm
2.4.8.2 Adding the Binding of a User-Defined Alarm
2.4.8.3 Modifying the Binding of a User-Defined Alarm
Parameters
Name Description Settings
Related Tasks
2.3.2.4 Setting the Alarm Box
Base Settings
Name Description Settings
Alarm Names
Name Description Settings
Notification Time
Name Description Settings
Notification Methods
Name Description Settings
Related Tasks
2.2.6 Setting Alarm Real-Time Monitoring
Parameters
Name Description Settings
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
Parameters
Name Description Settings
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
Parameters
Name Description Settings
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
Advance Parameters
Name Description Settings
0 Description:
Unknown.
1 Description:
International number.
Code Description
2 Description:
Home number. Area or special numbers cannot be contained.
3 Description:
Network special number.
4 Description:
Subscriber number.
5 Description:
Letter or number.
6 Description:
Abbreviated number.
7 Description:
Reserved.
0 Description:
Unknown. If TON is equal to 5, then NPI is equal to 0.
1 Description:
Integrated Services Digital Network(ISDN) or telephone number
coding scheme (E164 or E163). This code applies to any Service Center
(SC), Mobile Switching Center(MSC), or Mobile Station(MS).
2 Description:
Reserved.
3 Description:
Data coding scheme (121).
4 Description:
Telegraph coding scheme.
5-7 Description:
Reserved.
8 Description:
Home coding scheme.
9 Description:
Private coding scheme.
Code Description
10 Description:
ERMES coding scheme (ETSI DE/PS 3 01-3).
11-15 Description:
Reserved.
Related Tasks
2.3.3.2 Setting Alarm Remote Notification Parameters
Parameters
Name Description Settings
Related Tasks
2.3.7.3 Adding Simple Correlation Rules of Alarms
Parameters
Name Description Settings
Related Tasks
2.3.7.4 Adding Advanced Correlation Rules of Alarms
Parameter Description
NOTE
Start Date Year range: 1970 to 2038. Indicates the time range when the
script is triggered.
Start Time 24 hours
Only when the alarm occurs in the
End Date Year range: 1970 to 2038. defined time range, and in the
defined Triggering Day, for
End Time 24 hours
Triggering Day The following four severity example, Tuesday, the script to be
levels are listed in the drop- executed is triggered by the server.
down list:
l Everyday
l Mon
l Tuesday
l Wed
l Thursday
l Fri
l Sat
l Sun
Run-time Type Selected from the drop-down Run-time type refers to the way the
list. server runs the script.
l bash represents Bourne Again
shell.
l sh represents Bourne shell.
l csh represents C shell.
l zsh represents Z shell.
l ksh represents Korn shell.
l tcsh represents TC shell.
Script file A maximum of 255 characters. Involves the absolute path and the
name of the script file on the
M2000 server. For example, /
export/home/trigger.sh.
Related Tasks
2.3.8.1 Creating Auto-Triggering Tasks
2.3.8.2 Viewing the Attributes of Auto-Triggering Tasks
Parameter Description
Parameter Description
Ne Name The name of the NE whose alarm triggers the script execution.
Related Tasks
2.3.8.1 Creating Auto-Triggering Tasks
2.3.8.2 Viewing the Attributes of Auto-Triggering Tasks
Parameter Description
NOTE
Parameter Description
Search by Name This parameter is used to search for the NE or the NE alarm
that triggers the script. The querying conditions support
fuzzy search whatever case the name is. The querying
conditions do not support wildcard.
Group by NE Type If you select this item, in the Select NE navigation tree, the
NEs are displayed in groups based on NE types.
Parameter Description
Group by Alarm Type If you select this item, In the Select Alarm navigation tree,
the alarms are divided based on the alarm type. The alarm
types include the power supply system, the environment
system, and the signaling system.
Group by Alarm Level If you select this item, in the Select Alarm navigation tree,
the alarms are displayed in groups based on the alarm levels.
The alarm levels are critical, major, minor and warning.
Group by Category If you select this item, in the Select Alarm navigation tree,
the alarms are displayed in groups based on the alarm
categories. The alarms are categorized into fault alarms and
event alarms.
Related Tasks
2.3.8.1 Creating Auto-Triggering Tasks
2.3.8.2 Viewing the Attributes of Auto-Triggering Tasks
Parameter Description
Parameter Value Range Description
Task Name l The task name has a The name of the task that is
maximum of 20 characters. automatically triggered.
l The allowed characters
include Chinese characters,
English letters, numbers
and any other special
characters rather than ` ~ !
@#$%^&;*()+-={}
[]\\|;':,.?/<>\"
l The task name is unique and
cannot be null.
l The task name is case
sensitive.
Start Date Year range: 1970 to 2038. The period that is set in the auto-
triggering task.
End Date Year range: 1970 to 2038.
Run-time Type You may choose a type from Run-time type refers to the way the
the drop-down list. server runs the script.
l bash represents Bourne Again
shell.
l sh represents Bourne shell.
l csh represents C shell.
l zsh represents Z shell.
l ksh represents Korn shell.
l tcsh represents TC shell.
Related Tasks
2.3.8.3 Searching Auto-Triggering Tasks
Parameter Description
Parameter Description
Related Tasks
2.3.8.4 Searching Auto-Triggering Records
Parameters
Parameter Value Range Description
Upper Warp 0.000 - 100.000 Upper value set against the history value.
(%)
Lower Warp 0.000 - 100.000 Lower value set against the history value.
(%)
Related Tasks
2.5.4.1 Analyzing the Trend of a Monitoring Counter
Parameters
Parameter Operation
HSB Select a sample color or select a color by setting the HSB value.
Related Tasks
2.5.3.7 Setting a Background Color for a Monitoring Chart
Parameters
Parameter Description
Hide the filtered data To hide the data that satisfies the filtering conditions.
Show the filtered data To show the data that satisfies the filtering conditions.
Parameter Description
Related Tasks
2.5.3.1 Setting Filtering Conditions for a Monitoring Table
Parameters
Parameter Description
Time range Specifies the start and end time of the monitoring time segment
for the monitoring chart.
Part/Full Lost Data Status l Normal: Only time points in the normal monitoring status are
shown in the curve in the chart.
l Part Lost: Time points with missing data are shown in the
curve in a special color.
l Full Lost: Time points with lost data are shown in the curve
in a special color.
Related Tasks
2.5.3.4 Setting Properties for a Monitoring Chart
Parameters
Parameter Value Range Description
Related Tasks
2.5.2.5 Setting Real-Time Monitoring Thresholds
Parameters
Parameter Description
Related Tasks
2.5.2.6 Setting Rules for Monitoring Thresholds
Parameters
Parameter Value Range Description
Related Tasks
2.5.3.5 Setting Thresholds for Displaying Counters in a Monitoring Chart
Parameters
Parameter Value range Description
Related Tasks
2.5.3.2 Setting Thresholds for Displaying Counters in a Monitoring Table
Time Style l Server Time: Alarm statistics are made according the time on the
server.
l NE Time: Alarm statistics are made according the time on a specific
NE.
Alarm Level Alarms are categorized into four levels: critical, major,
minor and warning.
Alarm ID ID of an alarm
Parameter Description
Related Tasks
2.6.6.1 Summarizing RNC Alarms by Alarm Severity
2.6.6.2 Summarizing RNC Alarms by Alarm ID
2.6.6.3 Summarizing RNC Alarms by NodeB
2.6.6.4 Summarizing RNC Alarms by Cell
2.6.6.5 Summarizing RNC Alarms by SAAL Link
2.6.6.6 Summarizing RNC Alarms by E1/T1 Link
2.6.6.7 Summarizing NodeB Alarms by Alarm Severity
2.6.6.8 Summarizing NodeB Alarms by Alarm ID
Table 2-27 Parameters about the information on basic configuration of the RNC object group
Property Name Property Value
Related Tasks
2.6.5.1 Checking Values of RNC Monitoring Counters
Table 2-28 Parameters about the information on basic configuration of object groups
Parameter Description
IP IP address of the object. The IP address varies with the object tree
on the left.
neVersion NE version of the object. The NE version varies with the object
tree on the left.
className NE class name of the object. The NE class name varies with the
object tree on the left.
RNCID The RNC ID uniquely identifies an RNC node within the scope of
the PLMN.
Related Tasks
2.6.4.1 Checking the Information on Basis RNC Configuration
Parameter Description
Index Index of the destination signalling point. The range of the index is
from 0 to 37 and the step length is 1.
Parameter Description
Related Tasks
2.6.4.3 Checking the Information on the Iu/Iur of the RNC
Table 2-30 lists the parameters about the information on specified links of the Iu/Iur interface
in the RNC.
Table 2-30 Parameters about the information on specified links of the Iu/Iur interface
Parameter Description
Index Index of the destination signalling point. The range of the index is
from 0 to 37 and the step length is 1.
Related Tasks
2.6.4.4 Checking the Information on Specified Links of the Iu/Iur Interface
Table 2-31 lists the parameters about the information on the Iub interface in the RNC object
group.
Related Tasks
2.6.4.5 Checking the Information on the Iub Interface of the RNC
Serial Number Serial number of the alarm. The serial number is the keyword of
alarm records. Based on the serial number, you can determine a
unique alarm.
Alarm ID Alarm ID
MO Object MO object name. When the object is a real NE, the MO object is
consistent with the NE name. When the object is a virtual NE, the
MO object is the NE type of the object.
Alarm Name Alarm name that enables you to quickly locate the details about
alarms. Take the alarm name Database Threshold Alarm as an
example. Based on this name, you can locate the details about the
alarm.
Type Source of the alarms in the network such as Power System, Trunk
System, and Inside Element Management.
Level Alarm levels that consist of four levels: critical alarm, major alarm,
minor alarm, and warning.
Occurrence Time Time when an alarm occurs. Occurrence time can be server time
or network element time.
Related Tasks
2.6.4.6 Checking the Information on Specified Links of the Iub Interface
Frame No Number of the frame in which the board with the E1T1 interface is
located
Valid range of the parameter: 1 or 3 to 17
Slot No Number of the slot that the board with the E1T1 interface is located
in
Valid range of the parameter: 0 or 15
Use Status Use status that has two states: Unused and Used
Related Tasks
2.6.5.2 Checking the E1/T1 Status of the RNC
Table 2-34 Parameters about the distribution of NodeB and cells on the RNC
Parameter Description
Number of NodeB with Zero Total number of NodeB with zero cell in the current object
Cell group
Number of NodeB with One Total number of NodeB with one cell in the current object
Cell group
Number of NodeB with Two Total number of NodeB with two cells in the current object
Cells group
Number of NodeB with Three Total number of NodeB with three cells in the current
Cells object group
Number of NodeB with More Total number of NodeB with more than three cells in the
than Three Cells current object group
Related Tasks
2.6.4.2 Checking the Distribution of NodeB and Cells on the RNC
Table 2-35 lists the parameters about the information on basic configuration of the NodeB object
group.
Table 2-35 Parameters about the information on basic configuration of object groups
IP IP address of the object. The IP address varies with the object tree on
the left.
neVersion NE version of the object. The NE version varies with the object tree on
the left.
className NE class name of the object. The NE class name varies with the object
tree on the left.
Sub System No Identifies the subsystem of the WSPUb where the NodeB is located.
Related Tasks
2.6.4.7 Checking the Information on Basic NodeB Configuration
MAXTXPOWER Maximum transmit power of a cell. This parameter indicates the sum
of the maximum transmit power over the downlink channels in a cell.
The value depends on network planning.
l Value range: 0 to 500.
l Physical value range: 0 to 50, with a step of 0.1.
UARFCNUPLINK Uplink frequency number. Its value range depends on the frequency
selected.
TCELL Difference between the cell system frequency number (SFN) and the
NodeB frequency number (BFN).
SUPSSDT Indicates whether the cell supports Site Selection Diversity TPC
(SSDT).
LOCELL Identifier of the local cell, which maps to the logical cell.
RAC Identifies the routing area in the LAI, The fixed length is one byte. It
is mainly used in PS services.
CLOSEDLOOPTI Identifies whether the cell supports the closed loop timing adjustment
MEADJUSTMODE mode.
Related Tasks
2.6.4.8 Checking the Information on Basic Cell Configuration
Parameters Related to the Configuration Status of the RNC and the NodeB
Parameter Description
Related Concepts
2.6.1.3 Configuration Status of Monitored Objects
Related Tasks
2.6.3.4 Checking Detailed Information of Configuration Status
For details of the parameters related to the basic configuration of the common channel in a cell,
refer to Table 2-37.
Table 2-37 Parameters related to the basic configuration of the common channel in a cell
Parameter Description
PSCHPower Indicates the offset of the PSCH transmit power from the
PCPICH transmit power in a cell
l Value range (in dBs): -350 to 150
l Physical value range: -35 to 15, with a step of 0.1.
SSCHPower Indicates the offset of the SSCH transmit power from the
PCPICH transmit power in a cell
l Value range (in dBs): -350 to 150
l Physical value range: -35 to 15, with a step of 0.1
Related Tasks
2.6.4.9 Checking the Information on CCH Configuration
READSFNIND Indicate whether to read the System Frame Number (SFN) of the
neighboring cell.
The value range is as follows:
l NOT_READ: not read
l READ: read
CELLINDIVIDAL Indicates the offset of the cell CPICH measurement. This parameter is
OFFSET used in handover decisions and its value depends on network planning.
It is used to move the cell edges in handover algorithm. Configure this
parameter based on the actual situation in network planning. For 1A/
1C/1D events, the triggering chance is in positive correlation with the
value of this parameter. For 1B/1F events, the triggering chance is in
negative correlation with the value of this parameter.
The value range is as follows: -20 to 20, with the unit as dB.
Parameter Description
CELLSFORBIDD Indicates whether the addition of the cell into the active set affects the
EN1A relative threshold of the event 1A.
l NOT_AFFECT: The addition does not affect the relative threshold
of the event 1A.
l AFFECT: The addition affects the relative threshold of the event 1A.
The value range is as follows:
l NOT_AFFECT: not affect.
l AFFECT: affect.
N
CELLSFORBIDD Indicates whether the addition of the cell into the active set affects the
EN1B relative threshold of the event 1B.
l NOT_AFFECT: The addition does not affect the relative threshold
of the event 1B.
l AFFECT: The addition affects the relative threshold of the event 1B.
The value range is as follows:
l NOT_AFFECT: not affect.
l AFFECT: affect.
QOFFSET1SN Indicates load level offset 1 between connection mode center and
neighboring cells. This parameter is used for the cell offset of CPICH
RSCP measurement value in cell selection and re-selection. This
parameter is used for changing the cell border. In cell selection or re-
selection, this parameter is in negative correlation with the probability
of selecting inter-RAT neighboring cells.
The value range is as follows: Value range (in dBs): -50 to 50. The
recommended value of this parameter is 0.
QOFFSET2SN Indicates load level offset 2 between connection mode center and
neighboring cells. This parameter is used for the cell offset of CPICH
Ec/No measurement value in cell selection and re-selection. This
parameter is used for changing the cell border. In cell selection or re-
selection, this parameter is in negative correlation with the probability
of selecting inter-RAT neighboring cells.
The value range is as follows: Value range (in dBs): -50 to 50. The
recommended value of this parameter is 0.
TPENALTYHCSR Indicates the hierarchical cell re-selection penalty timer. The larger the
ESELEC parameter is, the smaller the probability of selecting neighboring cells.
l The value range is as follows: D0, D10, D20, D30, D40, 50, D60
l Physical value range (in seconds): 0, 10, 20, 30, 40, 50, 60.
Parameter Description
Parameter Description
Related Tasks
2.6.4.10 Checking the Information on Neighbors
Related Tasks
2.6.5.5 Checking the Values of Cell Monitoring Counters
Parameter Description
Search Keyword Keywords of the object. It can include letter, number and
underline. The value range is 1-256 characters.
Search Scope You can search in all the object groups or in a specified
object group.
Search Style The options are available. You can search by the object
name.
Search Result Research the result list. The node names and pathes are
displayed.
Related Tasks
2.6.3.2 Searching for Objects
Performance
Name Description Settings
Hard Disk
Name Description Settings
Database
Name Description Settings
Services
Name Description Settings
Related Tasks
2.7.1 Setting Monitoring Parameters
2.7.1.2 Setting the Parameters for the M2000 Performance Monitoring
2.7.1.3 Setting the Parameters for the M2000 Hard Disk Monitoring
2.7.1.4 Setting the Parameters for the M2000 Database Monitoring
Parameters
Name Description
OS Description:
Operating system of the server.
Name Description
Related Tasks
2.7.2 Monitoring the M2000 Performance Status
Parameters
Name Description
OS Description:
Operating system of the server.
Name Description
Status Description:
Current status of a specific partition, including normal and
abnormal. If the usage exceeds the maximum, the system
displays Abnormal.
Related Tasks
2.7.3 Monitoring the M2000 Hard Disk Status
Parameters
Name Description
OS Description:
Operating system in the server.
Name Description
Status Description:
Database status, including normal and abnormal. If the
database usage exceeds the threshold, the system
displays Abnormal.
Related Tasks
2.7.4 Monitoring the M2000 Database Status
Parameters
Name Description
Status Description:
The status of a service.
Related Tasks
2.7.5 Monitoring the M2000 Service Status
Parameters
Name Description
Process ID Description:
ID of a process.
NOTE
If the M2000 uses the DB2 database, the client does not display DB Connection Number.
Related Tasks
2.7.6 Monitoring the M2000 Process Status
3 Topology Management
Topology management offers the function of constructing and managing the topology structure
of the whole network to display the networking situation and running status of the equipment.
You can query and monitor the entire network operation in real time through the topology view.
You can adjust the topology view as required. For example, you can expand or hide the topology
navigation tree, switch the current subnet, display the topology view in full screen, zoom in or
out of the view, and customize the topology tips.
3.8 Printing a Topology View
Using the print function, you can print the topology view to paper.
3.9 Reference for Topology Management Interfaces
This part describers the topology management interfaces and relevant parameters, which helps
you perform the operation related to topology management.
The left of the logical topology is a navigation tree and the right is a topology view. The
navigation tree displays the hierarchies between the topology objects, and the topology view
displays the positions of the topology objects.
Context
Only the image files in the formats of *.gif or *.jpg can be imported, and the file size cannot
exceed 1MB.
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 Right-click in the topology view and choose Set Background or select Topology > Set
Background.
Step 3 In the Set Background dialog box, select a subview (also known as subnet) in the table, then
click Select Background.
Step 4 In the Select Map File dialog box, select an image, then click Open.
NOTE
To remove the background, select empty.gif in the Select Map File dialog box and then click Open.
----End
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 In the Current Viewdrop-down list, select a view where you want to create a physical subnet,
such asPhysical View.
Step 3 Choose one of the following method to start to create the physical subnet:
l In navigation tree of the topology, choose New > Create Physical Subnet .
l Right-click in the topology view and choose New > Create Physical Subnet .
Step 4 Click the Basic Attribute tab. Set the name, coordinate, background, and memo.
Step 5 Click the Objects Selection tab. In the Available Objects list, select a NE or a subnet, click
to add the selected object to the Selected Objects list. Thus the object is added to
the subnet being created.
NOTE
In the Selected Objects list, click . The object added to the subnet being created can be moved back
to the Available Objects list.
----End
Related References
3.9.3 Parameters for Setting a Physical Subnet
3.3.1 NE Types
The Huawei mobile network devices managed by the M2000 are categorized according to the
home network, service function, and management functions supported by NEs.
3.3.2 Basic NE Information
This part describes the basic NE information. You are required to acquire the basic NE
information before creating NEs, modifying NEs, and querying NE reports.
3.3.3 Creating a Physical NE
This task describes the procedure for creating a physical NE on the topology view. After the NE
is created, the M2000 obtains the configuration data of the NE by synchronizing the NE.
3.3.4 Creating Multiple Physical NEs
To reduce the maintenance workload, the M2000 provides the function of creating physical NEs
in batches. You can create multiple physical NEs on the topology at the same time.
Procedure
Step 1 In the physical navigation tree or physical view, right-click the subnet where you want to create
an NE, and then choose New > Create Topo Object .
Step 2 Select a specified virtual NE from the navigation tree of the Create Topo Object dialog box.
Step 3 In the right part of the Create Topo Object dialog box, enter the name, coordinates, and memo.
----End
Prerequisite
l The network communications between the M2000 and an IP device are functioning well.
l The parameters used for connecting the M2000 is set on the IP device.
Context
IP device includes SNMP, routers, and switches. After the IP device is successfully created, the
M2000 system automatically obtains related alarms from the IP device if the IP device incurs
faults.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 OIn the physical topology navigation tree or on the topology view, right-click the subnet of the
NE to be created and choose New > Create Topo Object on the shortcut menu.
Step 3 Select a mapping NE node under the Single Create node from the navigation tree in the left part
of the Create Topo Object dialog box.
Step 4 Configure information about the IP device in the Create Topo Object dialog box.
For details of the parameters, refer to 3.9.4 Parameters for Creating an IP Device.
TIP
When the SNMP is created, you can right-click the parameter panel of the SNMP template and choose
Save to save the modification performed in the parameter template, or click Save As to save the current
parameter information about the SNMP as a template.
You can view the progress of creating the IP device in the displayed Create NE Progress dialog
box. You can click Detail in the Create NE Progress dialog box to view the detailed information
about creating an IP device. A dialog box is displayed to show the progress of creating the IP
device.
NOTE
If the communications between the M2000 and an IP device are not functioning well, a status icon is
displayed at the top left corner of the created IP device on the topology. The icon indicates that the NE is
located in the disconnected state.
----End
Related References
3.9.4 Parameters for Creating an IP Device
Prerequisite
l You have logged in to the M2000 client successfully.
l The topology view and network levels are already planned.
Context
l Currently the M2000 supports six types of links: M3UA, H248, BICCSCTPLNK,
DATALINK, MTP3, and MTP3B. M3UA, H248and BICCSCTPLNK links can be
automatically created by the system. DATALINK, MTP3 and MTP3B links must be
manually created.
l Only physical links that are manually created can be deleted.
l The physical links are named automatically by the system. To change the name of a physical
link, see 3.6.6 Viewing/Modifying a Physical Link.
l The supported NE type varies with the link type. For details, refer to 3.9.5 Parameters for
a Physical Link.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 Right-click the subnet node in the physical topology navigation tree or the physical topology
view, and select New > Create Topo Object.
Step 3 Select a specific link type from the navigation tree of the Create topo objects dialog box.
l Select a specific link type from the Link node under the Single Create node.
l Select the Link node under the Bulk Create node. Click Add in the right part of the window.
For details of parameters about link information, refer to 3.9.5 Parameters for a Physical
Link.
TIP
The system displays the Create Link prompt box. The progress of creating the link is shown.
After the link is created successfully, a link is displayed between two NEs.
NOTE
After a physical link is set up, you can only modify its name.
----End
Related References
3.9.5 Parameters for a Physical Link
Context
l The two NEs at the both ends of a virtual link are called left node and right node. You can
only select an NE as the right or left node. If you select a subnet or a link as the right or
left node, the selection is invalid, and you need to select the node again.
l When there is more than one virtual link between two NEs, a virtual link set is set up.
l Double-click the link set. A table is displayed, listing the links in the set.
Procedure
Step 1 In the physical navigation tree or physical view, right-click the subnet where you want to create
a link, and then choose New > Create Topo Object .
Step 2 Select the Virtual Link node under the Single Create node from the navigation tree of the
Create Topo Object dialog box.
Step 3 In the right part of the Create Topo Object dialog box, enter the name, type, and left node and
right node of the virtual link.
Step 4 Click OK.
----End
Related References
3.9.6 Parameters for Setting a Virtual Link
Prerequisite
l You have logged in to the M2000 client successfully.
l The topology view and network levels are already planned.
Context
l Some physical links can be set up automatically through a program. For the other physical
links that cannot be set up through the program, you can set them up manually.
l The physical links are named automatically by the system. To change the name of a physical
link, see 3.6.6 Viewing/Modifying a Physical Link.
l This operation supports the MGW and the MSC Server.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 Right-click the subnet node in the physical topology navigation tree or the physical topology
view, and select New > Create Topo Object.
Step 3 Select the Link node under Bulk Create from the navigation tree of the Create topo objects
dialog box.
Step 4 Click Add in the right part of the Create topo objects dialog box.
Step 5 To know how to configure link information in Add a link, refer to 3.9.5 Parameters for a
Physical Link.
TIP
NOTE
After a physical link is set up, you can only modify its name.
----End
Context
l The system sets the NEs that can serve as an FTP server for file transfer M2000 server and
an NE.
l If an NE chooses another NE or the M2000 server as its transfer server, the file transfer
process can be stopped. If the NE chooses itself as the transfer server, the file transfer
process cannot be stopped.
l The M2000 provides the function of setting FTP servers in batches to save the maintenance
effort. You set multiple NEs as FTP servers concurrently.
l The typical setting is to use the RNC as the relay server for transferring NodeB data.
Procedure
Step 1 Choose Software > File Server Setting. The File Server Setting dialog box is displayed.
Step 2 Select the type of the target NE from the navigation tree of the dialog box. All the NEs of this
type are listed in the right pane.
NOTE
click Refresh to refresh the NE information in the list at the right of the File Server Setting dialog box.
You can use Shift or Ctrl to select multiple NEs. Then right-click them and choose Set to set
NEs in batches.
Step 4 Click the File Server Name column. Select an NE to act as the file server for transferring files.
The File Server IP box displays the IP address of the file server that you have set.
NOTE
If you click Refresh, the Confirm dialog box is displayed. Click No to cancel the previous setting for the
file server.
----End
3.3.1 NE Types
The Huawei mobile network devices managed by the M2000 are categorized according to the
home network, service function, and management functions supported by NEs.
3.3.2 Basic NE Information
This part describes the basic NE information. You are required to acquire the basic NE
information before creating NEs, modifying NEs, and querying NE reports.
3.3.3 Creating a Physical NE
This task describes the procedure for creating a physical NE on the topology view. After the NE
is created, the M2000 obtains the configuration data of the NE by synchronizing the NE.
3.3.4 Creating Multiple Physical NEs
To reduce the maintenance workload, the M2000 provides the function of creating physical NEs
in batches. You can create multiple physical NEs on the topology at the same time.
3.3.1 NE Types
The Huawei mobile network devices managed by the M2000 are categorized according to the
home network, service function, and management functions supported by NEs.
WCDMA l MGW
network l SGSN
l RNC
l HLR
l SIWF
l CG
l MSCServer
l NodeB
l IMSOMU
l CSCF
l HSS
l ATS
l RM
l CCF
l DOPRA
l SBC
l MRF
l AG
l AHR
l ICS(IP Clock Server)
Core network l CG
l GGSN80
l HA
l HLR
l MGW
l MSC Server
l rMSCSvr
l SGSN
l tMSCSvr
l AAA
l CHLR
l CMSC
l MSCe
l POC
l CHLR9820
l PDSN
l IMSOMU
l CSCF
l HSS
l ATS
l RM
l CCF
l DOPRA
l SBC
l MRF
l AG
l AHR
Class A NE l HLR9820
l NodeB
l SGSN
l GGSN
l CG
l MSC Server
l MGW
l RNC
l CHLR9820
l MSCe
l IMSOMU
l CSCF
l HSS
l ATS
l RM
l CCF
l DOPRA
l SBC
l MRF
l ASN-GW
l BWA
l AG
l AHR
l ICS(IP Clock Server)
Class B NE l BSC
l BTS
l MSC
l PCU
l HLR36
l GT800 BSC
l iMSC
l rMSC
l tMSC
Class C NE l CHLR9820
l GLMS
l RAC
l TSC
l RAU
l POC
l CT800 GLMS
l CBTS
l CBSC
l SG7000
l MSCe
l PDSN
l CMGW
l HA
To know the basic NE information, refer to Table 3-4. The NE report contains all the NE
information except Username, Password, Confirm Password, and Coordinates.
Name Name of the NE, which must be entered when you create an NE.
District District of the NE. For the users outside China, import the files
of their own district information.
Subarea Indicates the subareas where the NEs are located. The candidate
NEs subareas are determined by the server side.
Position Click the value behind Position, and the mouse changes to +. In
the physical topological view, click where the NE is created to
display the X and Y coordinates values of the NE.
Prerequisite
l You have logged in to the M2000 client.
l The mediation applications of accessed NEs are successfully installed.
l You have obtained the basic information about NEs, such as NE name, IP address of NEs,
NE version, and district of NEs.
l The physical NE communicates properly with the M2000 server.
Context
l After the RNC is created, it serves as a subnet or an NE. You can use 3.3.4.1 Automatically
Searching for NodeBs to view all the NodeBs belonging to the RNC on the physical
topology view and the navigation tree.
l After the IMSOMU is created, it can be both a sub-network and an NE. By referring to
3.3.4.2 Automatically Searching the Sub-NEs of the IMSOMU, you can display all the
sub-NEs of the IMSOMU on the topology view and the navigation tree.
l After the ASN-GW is created, it serves as a subnet or an NE. You can create a BWA under
the ASN-GW subnet.
l After the MGW is created, you can use 3.6.2.1 Moving an NE into a Group NE to add it
to the MSC Server. This addition does not change the user authority of the MGW.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 In the physical topology navigation tre or on the physical view, right-click the subnet of the NE
to be created and choose New > Create Topo Object on the shortcut menu.
Step 3 From the navigation tree in the Create topo objects dialog box, select a specific NE node
mapping the NE node under Single Create.
NOTE
l The RNC, MSC Server, ASN-GW, and BSC are group objects. These NEs can manage the subnets. In
addition, these NEs can manage the NodeB, MGW,and BTS.
l The NodeB can be created under only the virtual RNC in batches.
l The physical BTS cannot be manually created. If a BSC is controlled by a BTS, the BTS is automatically
created when you synchronize the BSC.
l The sub-NEs of the IMSOMU are the CSCF, HSS, ATS, RM, CCF, and DOPRA. These sub-NEs
cannot be created manually. After creating the IMSOMU, you can deliver the automatic search
command. The searched NEs are displayed on the physical topology view.
For RNCs, you need set the NE partitions where the NodeBs are located. The NE partitions that can be
selected are determined by the server.
For information about NEs that need configuring, refer to 3.9.9 Parameters for Creating an
NE.
Step 5 Click OK.
The displayed Create NE Progress dialog box shows the NE creation progress. You can click
Detail in the Create NE Progress dialog box to view the detailed information about creating a
physical NE. After an NE is created, the NE is displayed in the physical topology navigation
tree and in the topology view.
Step 6 Click Close. Then, the Create NE Progress dialog box is closed.
----End
Result
After the physical NE is created successfully, the system automatically synchronizes the
configuration information on the NE.
Related References
3.9.9 Parameters for Creating an NE
To reduce the maintenance workload, M2000 provides the function of creating physical NEs in
batches. You can create multiple physical NEs on the topology view at the same time.
3.3.4.8 Description of the .ini Template Format Used by the Batch NE Creation Script
The M2000 provides a standard template for the script files for creating NEs in batches. You
need only export the template, and then enter the information of the NEs to be created. Two
formats of templates are available: INI and CSV. This part describes the template in .ini format
to facilitate the creation of NEs in batches through script files.
3.3.4.9 Description of the .csv Template Format Used by the Batch NE Creation Script
Templates for creating physical NEs in batches are the standard templates provided by the
M2000 client. You need to only export the template and then enter the information of the NEs
to be created. Two formats of templates are available: INI and CSV. This part describes the
template in .csv format to facilitate the creation of NEs in batches through script files.
Prerequisite
l You have logged in to the M2000 client.
l The RNCs are well connected to the M2000 server.
Context
NodeBs can be reparented. Therefore, the NodeBs that need to be deleted are deleted
automatically when they are found automatically. Instead, they are displayed as disconnected.
In this case, you need to determine whether the disconnected NodeBs need to be deleted. For
information about how to delete NodeBs, refer to 3.6.9 Deleting a Virtual NE.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 From the topology navigation tree or the topology view, right-click an RNC and choose Search
NodeB on the shortcut menu.
If the RNCs are disconnected from the M2000 server, Search NodeB turns gray.
NOTE
For RNCs in multi-server load-sharing system, you also need to select the subarea where the NodeB is
located.
----End
Result
In the system output part of the Main Topology window, the system automatically synchronizes
the information about the NodeBs managed by a specific RNC, such as the total number of
NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number of NEs
whose names are duplicate, and the number of NodeBs whose IP addresses are duplicated.
Prerequisite
If an IMSOMU is connected, this task enables you to automatically detect the sub-NEs of the
IMSOMU on the physical topology view or from the navigation tree. These sub-NEs are the
CSCF, HSS, ATS, RM, CCF, and DOPRA.
Procedure
Step 1 From the navigation tree or on the physical topology view, select an IMSOMU.
Step 2 Right-click the pane and choose Search IMSOMU NE from the shortcut menu.
----End
Result
The searched IMSOMU sub-NEs are displayed on the physical topology view.
Context
l Two formats of templates are available for creating NEs in batches: .ini and .csv.
l To create NEs in batches successfully, you need to configure the .ini or .csv file correctly.
Procedure
Step 1 Choose Configuration > Exports NE Attributes Template > INI File Format.
Step 2 Select an NE type, and then click to select a path for saving the template.
Step 3 Enter a name for saving the .ini file, and then click Save to return to Export NE Info template
(INI file format) dialog box.
Step 4 Click Confirm to export the .ini file template for creating NEs in batches.
A prompt is displayed to show that the template is exported successfully.
Step 5 Click OK to close the Message prompt box.
----End
Related Tasks
3.3.4.5 Editing a Script for Batch Creating NEs (in .ini Format)
Related References
3.3.4.8 Description of the .ini Template Format Used by the Batch NE Creation Script
3.9.8 Parameters for Exporting an NE Information Template (in .ini Format)
Context
l Two formats of templates are available for creating NEs in batches: .ini and .csv.
l To create NEs in batches successfully, you need to configure the .ini or .csv file correctly.
NOTE
The script file in .csv format can be used to create physical NEs in batches. It cannot be used to create
group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS. For other NEs, the
configuration file on the client determines whether they are supported. You can obtain the information
through the bulkCreateNe.txt file in the client installation directory client\style\defaultstyle\conf
\omccm.
Procedure
Step 1 Choose Configuration > Exports NE Attributes Template > CSV File Format.
Step 3 Enter a name for saving the .csv file, and then click Save to return to Export NE Info template
(CSV file format) dialog box.
Step 4 Click Confirm to export the .csv file template for creating NEs in batch.
----End
Related Tasks
3.3.4.6 Editing a Script for Batch Creating NEs (in .csv Format)
Related References
3.3.4.9 Description of the .csv Template Format Used by the Batch NE Creation Script
Prerequisite
l You have obtained the NE type, NE IP address, and district area.
l You have exported the NE information template through 3.3.4.3 Exporting an NE
Information Template (in .ini Format).
Context
l For information about the value range of each NE parameter when you singly create
physical NEs, refer to 3.9.9 Parameters for Creating an NE and 3.9.4 Parameters for
Creating an IP Device.
l To determine whether an NE supports bulk creation, you can compare the NETYPE in the
file entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrl-
bycondition.csv is located in \client\style\defaultstyle\conf\omccommon in the
installation path of the client. This file contains NENAME and NETYPE. The file
bulkCreateNe.txt is installed in \client\style\defaultstyle\conf\omccm in the installation
path of the client. This file contains the NETYPE of the NEs that support batch creation.
l Group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS can only
be created in batches using the INI template.
Procedure
Step 1 Use Notepad delivered with the operating system to open the NE information template.
Step 2 Enter the NE name, NE version, and district.
----End
Related Tasks
3.3.4.3 Exporting an NE Information Template (in .ini Format)
Related References
3.3.4.8 Description of the .ini Template Format Used by the Batch NE Creation Script
Prerequisite
l You have obtained the NE information such as NE type, NE IP address, NE version, and
home administration region.
l You have exported the NE information template according to 3.3.4.4 Exporting an NE
Information Template (in .csv Format).
Context
l For information about the value range of each NE parameter when you singly create
physical NEs, refer to 3.9.9 Parameters for Creating an NE.
l The script file in .csv format can be used to create physical NEs in batches. It cannot be
used to create RNCs in batches.
l To determine whether an NE supportes bulk creation, you can compare NETYPE in the
entrancectrl-bycondition.csv and bulkCreateNe.txt files. The entrancectrl-
bycondition.csv file is saved in \client\style\defaultstyle\conf\omccommon under the
client installation directory. This file contains NENAME and NETYPE. The
bulkCreateNe.txt file in \client\style\defaultstyle\conf\omccm under the client
installation directory. This files contains the NETYPE of the NEs that support bulk
creation.
l As the separator of columns, commas are not allowed in each cell of the .csv file.
TIP
It is recommended that you use the Microsoft Excel to edit .csv files.
Procedure
Step 1 Open the exported NE information template.
Step 2 Enter the NE information such as NE type, NE name, NE version, and home administration
region.
----End
Related Tasks
3.3.4.4 Exporting an NE Information Template (in .csv Format)
Related References
3.3.4.9 Description of the .csv Template Format Used by the Batch NE Creation Script
Prerequisite
l You have logged in to the M2000 client.
l The mediation software of the NE to be created is successfully installed.
l The script in .csv or .ini format used for creating NEs in batches is available.
Context
To determine whether an NE supports bulk creation, you can compare the NETYPE in the file
entrancectrl-bycondition.csv and the file bulkCreateNe.txt. The file entrancectrl-
bycondition.csv is located in \client\style\defaultstyle\conf\omccommon in the installation
path of the client. This file contains NENAME and NETYPE. The file bulkCreateNe.txt is
installed in \client\style\defaultstyle\conf\omccm in the installation path of the client. This file
contains the NETYPE of the NEs that support batch creation.
NOTE
Procedure
Step 1 Choose Topology > Main Topology.The Main Topology window is displayed.
Step 2 In the physical topology navigation tree or on the physical view, right-click the subnet of the
NE to be created and choose New > Create Topo Object on the shortcut menu.
CAUTION
If the type of the new NE is NodeB, a virtual or physical RNC is selected as the subnet where
the new NE is located.
If the type of the new NE is BWA, a virtual or physical ASN-GW is selected as the subnet where
the new NE is located.
Step 3 Select the NE node under the Bulk Create node from the navigation tree of the Create topo
objects dialog box.
Step 4 In the right part, click and select the NE configuration script file.
Step 5 Click Verify to check the configuration of the script file. For errors, modify them according to
3.3.4.6 Editing a Script for Batch Creating NEs (in .csv Format) or 3.3.4.5 Editing a Script
for Batch Creating NEs (in .ini Format).
Step 7 Click Close. Then, the Create NE Progress dialog box is closed.
----End
Result
After creating a physical NE successfully, the system performs NE synchronization
automatically to obtain configuration data from this NE. If synchronized successfully, the NE
is displayed in the specified position on the topology view and is in the Being Synchronized
state, as shown by the icon . If the network connection between M2000 and this physical NE
is abnormal, the NE can also be displayed in the designated position on the topology view, but
the NE is in the disconnection state, as shown by the icon .
Related References
3.9.10 Parameters for Batch Creating Physical NEs
Description of the .ini Template Format Used by the Batch NE Creation Script
The M2000 provides a standard template for the script files for creating NEs in batches. You
need only export the template, and then enter the information of the NEs to be created. Two
formats of templates are available: INI and CSV. This part describes the template in .ini format
to facilitate the creation of NEs in batches through script files.
Format Description
The templates in INI format apply to create all types of NEs in batches except virtual NEs.
Use the notepad to edit the templates in the INI format. Different from the CSV templates, the
INI templates apply to different parameter groups. The system can create NEs in batches only
when you conform to the value range of parameters for each NE. For details about the value
range of parameters for each NE, refer to 3.9.9 Parameters for Creating an NE and 3.9.4
Parameters for Creating an IP Device. For details about the basic configuration information
of each NE, refer to 3.3.2 Basic NE Information.
CAUTION
If several NEs of the same category are created, you need to provide the associated parameter
groups. The ID of NE types should be duplicate. For instance, when several RNCs are created,
the [RNC] at the beginning of the configuration information should be duplicate to identify the
NE type for each RNC in the .ini template. Do not configure the information on several RNCs
under one [RNC].
Related Tasks
3.3.4.3 Exporting an NE Information Template (in .ini Format)
3.3.4.5 Editing a Script for Batch Creating NEs (in .ini Format)
Description of the .csv Template Format Used by the Batch NE Creation Script
Templates for creating physical NEs in batches are the standard templates provided by the
M2000 client. You need to only export the template and then enter the information of the NEs
to be created. Two formats of templates are available: INI and CSV. This part describes the
template in .csv format to facilitate the creation of NEs in batches through script files.
NOTE
The script file in .csv format can be used to create physical NEs in batches. It cannot be used to create
group NEs such as RAC, RNC, BSC, GT800BSC, BSC6000, CBSC, and IMS. For other NEs, the
configuration file on the client determines whether they are supported. You can obtain the information
through the bulkCreateNe.txt file in the client installation directory client\style\defaultstyle\conf
\omccm.
Use the Microsoft Excel to edit the templates in the CSV format. All the NEs apply to the same
parameter group, as shown in Figure 3-1.
The system can create NEs in batches only when you conform to the value range of parameters
for each NE. For details about the value range of parameters for each NE, refer to 3.9.9
Parameters for Creating an NE. For details about the basic configuration information of each
NE, refer to 3.3.2 Basic NE Information.
Related Tasks
3.3.4.4 Exporting an NE Information Template (in .csv Format)
3.3.4.6 Editing a Script for Batch Creating NEs (in .csv Format)
Procedure
Step 1 Choose Configuration > SNMP Template Management to open the Template
Management dialog box.
Step 2 Select the template type to be created from the Protocol Version navigation tree and click
Add.
Step 3 Configure parameters in the displayed Template Parameter. For details of configuring
parameters, refer to 3.9.15 Parameters for SNMP Parameter Templates.
Step 4 Click OK or Apply.
The added parameter template is displayed in the right window of the Template Parameter
Management dialog box.
----End
Related References
3.9.15 Parameters for SNMP Parameter Templates
Prerequisite
The SNMP parameter templates are already created.
Procedure
Step 1 Choose Configuration > SNMP Template Management to open the Template
Management dialog box.
Step 2 Select the template types to be modified from the Protocol Version navigation tree and select
the parameter templates to be modified on the right of the window.
Step 3 Double-click the parameter templates or click Modify to open the Template Parameter dialog
box.
Step 4 Modify parameters in Template Parameter. For details about modifying parameters, refer to
3.9.15 Parameters for SNMP Parameter Templates.
Step 5 Click OK.
The latest parameter template is displayed in the right window of the Template Parameter
Management.
----End
Related References
3.9.15 Parameters for SNMP Parameter Templates
Prerequisite
The SNMP parameter templates are already created.
Procedure
Step 1 Choose Configuration > SNMP Template Management to open the Template
Management dialog box.
Step 2 Select the template type to be deleted from the Protocol Version navigation tree and select the
parameter templates to be deleted on the right of the window.
----End
Context
l You can right-click an NE in the system monitor and browse window, and then choose
Topology Location to view the topology view of the NE.
l You can right-click in the system monitor and browse window, and then choose Refresh
to refresh the current window.
Procedure
Step 1 Choose Monitor > System Monitor > Browser .
Step 2 In the System Monitor Browser window, click the NE Monitor tab to view the NEs that are
managed by the M2000.
Step 3 Optional: Click Filter. Select NE Type and Alarm Status.
The information on the NEs that match the filter conditions are displayed in the table.
Step 4 Optional: Click Save As.
The monitoring data is saved to the local disk.
----End
Related References
3.9.11 Parameters for Monitoring the Status of an NE
Context
There are two NE reconnection states:
l 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.
l Disable Connection: When the communication between an NE and the M2000 is
disconnected, the M2000 does not attempt to reconnect the NE.
The set connection state is maintained even after you restarts the system.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 In the navigation tree or on the topology view, select an NE and set a reconnection state.
Enable connect NE The connection is enabled between the M2000 server and an NE. When
disconnected, the NE automatically reconnect the M2000 server. At the
same time, the disabling connection icon disappears. If the connection
succeeds, the disconnection icon disappears.
NOTE
The menu displayed after you right-click an NE varies with the change of the reconnection status. If you
right-click an NE in the Enable Connection state, the displayed menu shows the Disable connect NE
option. If you right-click an NE in the Disable Connection state, the displayed menu shows the Enable
connect NE option.
----End
Context
NodeBs may be in the disconnected state because they are deleted or reparented. Therefore, you
need to determine the reason why the NodeBs are disconnected before performing the related
operation such as deleting, reconnecting, and waiting for the NodeBs to be reparented.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 On the physical topology view, select an NE with the Disconnected icon .
----End
Context
l In the Search Content text box, enter the key words. The wildcard * and fuzzy search are
supported.
l In the Search Content text box, no blank space is allowed between two key words.
l In the Search Results list, click a record. The object related to the record is located in the
topology view.
Procedure
Step 1 Choose Topology > Main Topology.
l Search sublayer: If you select this item, you can search the path and the subpath specified in Search
Scope.
l Case sensitive: If this check box is selected, it is case sensitive in the search operation.
l Match whole word only: If this check box is selected, only the results that exactly meet the conditions are
to be displayed.
the NodeB. Group NEs refer to NEs which can also act as subnets, such as RNC, ASN-GW and
MSC Server.
Prerequisite
l You have logged in to the M2000 client.
l The NE to be moved is located in the same subnet as the group NE.
Context
This operation supports the MGW, NodeB, BWA, ASN-GW, RNC and MSC Server.
Moving an NE into a group NE changes only the dependency relationship on the topology view,
and has no effect on the actual situation.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 On the topology view, select the group NE that the NE is to be moved into.
Step 3 Right-click the group NE and select Property from the shortcut menu. The NE Property dialog
box is displayed.
Step 5 Select the NE to be moved into the group NE in the Available Objects list. Click .
Then the NE is added to the Selected Objects list.
TIP
----End
Prerequisite
You have logged in to the M2000 client.
Context
This operation supports all network equipment.
Moving an NE into another subnet changes only the dependency relationship on the topology
view and has no effect on the actual situation.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
The NE and the subnet are located in different level of network hierarchy Go to Step 3.
on the navigation tree.
The NE and the subnet are located in the same level of network hierarchy Go to Step 4.
on the navigation tree.
4. Select the NE to be moved into the NE group in the Available Objects list. Click
. Then the NE is added to the Selected Objects list.
5. If the subnet is located in the third or higher network level, repeat operation a to operation
d till the NE is moved to the same network level with the subnet.
l If the NE is located in the second network level under the Physical Root node while the
subnet to be moved into is located in the first network level, perform the following steps:
1. In the topology view, select the subnet of the NE to be moved out.
2. Right-click the subnet and select Modify from the shortcut menu. The Modify Physical
Subnet dialog box is displayed.
3. Click the Object Selection tab.
4. Select the NE to be moved out of the NE group in the Selected Objects list. Click
. Then the NE is added to the Available Objects list.
5. If the subnet is located in the third or higher network level, repeat operation a to operation
d till the NE is moved to the same network level with the subnet.
l If both the NE and the subnet are located in the second or higher level of the Physical
Root node, perform the previous steps till the NE is located in the same network level with
the subnet to be moved into.
----End
Prerequisite
l You have logged in to the M2000 client.
l The NE is created.
Context
This operation supports all network equipment.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 Select an NE on the topology view.
Step 3 Drag the NE to the target location.
Step 4 Click the icon on the toolbar to save the new location.
----End
Related References
3.9.16 Parameters for Moving a NodeB
3.9.2 Interface Description: Moving a NodeB
Prerequisite
l You have logged in to the M2000 client.
l You have the right to operate the related NEs.
Context
Figure 3-3 shows the process for moving a NodeB in the same RNC.
The process for moving a NodeB to another RNC shown in Figure 3-3 is as follows:
1. The RNC sends a command about deleting the NodeB to the M2000.
2. The M2000 closes the connection with the NodeB (hereinafter referred to as A).
3. After the NodeB is re-parented, the RNC sends a command about creating a NodeB to the
M2000.
4. The M2000 searches for the NE with the same NodeBID.
If an NE with the same NodeBID is found, you can infer that the created NodeB is the re-
parented one. Then the system updates the information about the existing NodeB with the
created NodeB. If no such a NodeB is found, the M2000 automatically searches for NodeBs
and creates a new NodeB (hereinafter referred to as A'). Then you can specify the binding
relation through the NodeB re-parenting tool. At the same time, the system deletes A'.
5. After the re-parenting, the state of A changes to connected.
Procedure
Step 1 Double-click omcNodebmove.bat under M2000 client installation directory\client\bin to view
the Login dialog box.
by default, the M2000 client is installed in the path C:\iManagerM2000Client.
Step 2 Enter the user name, password, and IP address of the M2000 server. Then, click OK.
Step 3 Select the related NodeBs in the NodeB Re-parent navigation trees. Then, click Add Bind(s).
l After being bound, the NodeB turns blue in color and the node name is added binded.
l A binding record is added to the result table. You can select one or more binding records and
click Remove Bind(s) to remove the binding relation.
l You can repeat Step 3 to specify multiple binding relations for bulk re-parenting.
A' is the logical representation of A. The IP address, belonged RNC, and sometimes the configuration
information of A' are changed after the re-parenting. You need to synchronize the information about A
with the information about A'. Then after the synchronization, the system deletes the logical NE A'.
----End
Result
After the NodeB is moved in the same RNC, the progress bar in the NodeB Re-parent dialog
box displays 100%. You can view the result in Operation Result.
Related References
3.9.16 Parameters for Moving a NodeB
3.9.2 Interface Description: Moving a NodeB
Prerequisite
l You have logged in to the M2000 client.
l You have the right to operate the related NEs.
Context
Figure 3-4 shows the process for moving a NodeB to another RNC.
The process for moving a NodeB to another RNC shown in Figure 3-4 is as follows:
1. The RNC sends a command about deleting the NodeB to the M2000.
2. The M2000 closes the connection with the NodeB (hereinafter referred to as A).
3. After the NodeB is re-parented, the RNC to which the NodeB is moved sends a command
about creating a NodeB to the M2000.
4. The M2000 automatically searches for the NodeB and then creates a new NodeB
(hereinafter referred to as A').
After A is re-parented, it is displayed as A' and its state changes to disconnected. A' is
automatically found by the M2000 and regarded as a new NE.
CAUTION
The IP addresses of NEs of the same type must be unique on the M2000. Therefore, the IP
address of a NodeB must be changed after it is moved to another RNC. The conflict caused
by identical IP addresses may result in the failure to create a new NodeB, and the System
Output Window may display error. In this case, you need to manually change the IP
address of the NodeB and then enable the M2000 to automatically search for the NodeB.
5. The user specifies the binding relation between A and A' by using the NodeB re-parenting
tool.
The system automatically updates the information about A, that is, NodeBID and the
relation with the RNC, with the information about A', and then deletes A'.
NOTE
A' is the logical representation of A. The IP address, belonged RNC, and sometimes the configuration
information of A' are changed after the re-parenting. You need to synchronize the information about
A with the information about A'. Then after the synchronization, the system deletes the logical NE
A'.
6. After the re-parenting, the state of A changes to connected.
Procedure
Step 1 Double-click omcNodebmove.bat under M2000 client installation directory\client\bin to view
the Login dialog box.
by default, the M2000 client is installed in the path C:\iManagerM2000Client.
Step 2 Enter the user name, password, and IP address of the M2000 server. Then, click OK.
Step 3 Select the related NodeBs in the NodeB Re-parent navigation trees. Then, click Add Bind(s).
l After being bound, the NodeB turns blue in color and the node name is added binded.
l A binding record is added to the result table. You can select one or more binding records and
click Remove Bind(s) to remove the binding relation.
l You can repeat Step 3 to specify multiple binding relations for bulk re-parenting.
----End
Result
After the NodeB is moved to another RNC, the progress bar in the NodeB Re-parent dialog
box displays 100%. You can view the result in Operation Result.
Related References
3.9.16 Parameters for Moving a NodeB
3.9.2 Interface Description: Moving a NodeB
Context
CAUTION
l Do not modify the coordinate of the ROOT node in the physical topology.
l The size of the background picture must be less than 1 MB.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 In the physical topology navigation tree or on the physical topology view, select the subnet to
be modified. Right-click the subnet and choose Modify to view the Modify Physical Subnet
dialog box.
Step 3 Select the corresponding tab and then view and modify the basic attributes of the subnet.
Tab Operation
Basic Attribute View and set the name, coordinate, background, and remarks.
Object Selection Deselected objects are listed in the left part of the tab and selected objects
are listed in the right part of the tab. To set objects included in a subnet,
click or .
----End
Related References
3.9.12 Parameters for Viewing/Modifying the Basic Attributes of a Subnet
Context
l If you have modified the IP address of the NE, the system automatically reconnects the NE
through the new IP address.
l To save the NE location information, drag the NE to the specified location and then click
on the topology toolbar.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 Right-click an NE on the navigation tree or topology view, and choose Property from the
shortcut menu, then you can view or modify the information.
CAUTION
The information on a physical BTS cannot be modified.
----End
Procedure
Step 1 Select a physical link.
1. Open the Link Browser window by using either of the following ways:
Method Operation
2. Select one or more NEs in the End A NE and End Z NE fields respectively.
l If you do not select NEs for either end, this function displays the information about all
the available physical links.
l If you select NEs for only one end, this function displays the information about all the
available physical links with the ends as the specified NEs.
3. Click Query.
The links that satisfy the conditions are shown in the list.
----End
Related References
3.9.5 Parameters for a Physical Link
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 On the physical topology view, double-click a virtual link or a virtual link set. You can also
right-click and choose Display on the shortcut menu.
Step 3 Check the information about the virtual link in the displayed information box.
Step 4 Right-click a virtual link and choose Modify on the shortcut-menu. The Modify Virtual
Link dialog box is displayed.
NOTE
For a signal virtual link, you can right-click it directly on the topology view and choose Modify. The
Modify Virtual Link dialog box is displayed.
Step 5 In the Modify Virtual Link table, modify the virtual link attributes.
CAUTION
l You can modify the name and remarks of a virtual link.
l After a virtual link is created, three attributes, that is type, End A NEs, and End Z NEs cannot
be modified.
----End
Related References
3.9.6 Parameters for Setting a Virtual Link
Context
l The root nodes in the navigation tree cannot be deleted.
l When a subnet is deleted, the elements in the subnet are not deleted. They are moved to
the upper subnet. The IMSOMU is an exception. When deleting an IMSOMU, you must
perform association deletion to delete all the subnets belonging to the IMSOMU.
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 In the navigation tree or topology view, right-click a subnet and choose Delete .
Step 3 In the Confirm dialog box, click Yes.
----End
Context
You can delete the virtual NE in the physical view, or electronic view. You cannot delete the
virtual NE in the custom view. This section describes how to delete the virtual NE in the physical
view. In the custom topology, you cannot delete a virtual NE.
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 In the navigation tree or the view, right-click a virtual NE and choose Delete.
Step 3 Click Yes.
----End
Context
The CSCF, HSS, ATS, RM, CCF and DOPRA do not support batch deletion.
CAUTION
Do not perform the batch deletion when a subnet is selected.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 Press Ctrl to select multiple physical NEs from the physical topology navigation tree or the
physical topology view.
Step 3 Right-click the selected NEs, and then choose Delete NEs in batch.
Step 4 In the displayed Confirm dialog box, click Yes.
The Delete NE prompt box is displayed, showing the deleting progress and operation results.
----End
Result
The system deletes the information related to the NEs in the database.
Context
CAUTION
Do not remove the physical links that the are automatically set up by the system. The physical
links are automatically refreshed according to the connection status between NEs.
Procedure
Step 1 Choose Configuration > Link Browser to view the Link Browser window.
Step 2 Set conditions for querying the links you want to remove.
Step 4 Right-click the Delete option or click Delete in the dialog box.
----End
Related References
3.9.5 Parameters for a Physical Link
Context
l A physical link is the physical connection between two physical NEs, and it is displayed
in the physical view automatically. The automatically created physical links cannot be
deleted.
l When a virtual link is deleted, the corresponding physical link is not deleted.
l You can delete the virtual link in the physical view, electronic view, or machine view. You
cannot delete the virtual link in the custom view. This section describes how to delete the
virtual link in the physical view.
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 In the physical view, right-click a link and choose Delete.
Step 3 Click Yes.
----End
Related References
3.9.6 Parameters for Setting a Virtual Link
Procedure
Step 1 Choose Topology > Main Topology.
----End
After you set alarm display on the topology view, 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.
3.7.3 Switching the Current Subnet
On the topology view, you can switch the current subnet view to the desired one.
3.7.4 Display the filtered topology view
When there are excessive objects, the topology view may appear crowded. You can set the filter
conditions to filter the objects in the view by type.
3.7.5 Zooming In/Out on a Topology View
You can adjust the topology view as desired, including zooming out, zooming in, magnifying,
fitting the view to the contents, and displaying the view in full screen.
3.7.6 View the topology aerial view
When the topology view is larger than 1024 x 768 pixels, only a part of the view is displayed in
the topology window. You can use the aerial view to browse the entire view and locate the area
to be displayed.
3.7.7 Laying Out Topology Objects Automatically
If there are multiple objects in the topology view in disorder, you can lay out the objects
automatically.
3.7.8 Expand or Collapse Child Objects
You can expand or collapse the topology objects in the navigation tree so that you can view the
objects conveniently.
3.7.9 Sorting Topology Objects
You can sort the topology objects in the navigation tree in the ascending or descending order.
3.7.10 Displaying the Alarm Pop-Up Pane
You can set the display of the alarm pop-up pane. When an alarm is raised, the number of the
alarms of the highest level is displayed in the pop-up pane on the upper left of the NE.
3.7.11 Customizing Topology Tips
The topology tip refers to the information displayed when the cursor stays on an object for a few
seconds on the topology view. You can select counters for setting the tips. The counters can be
sorted in two ways: by NE, and by link.
3.7.12 Setting a Subnet Displayed When the Topology View is Started
You can specify the default subnet view that is displayed when the topology view is started. If
view is manually set, the default startup subnet view is the root subnet view.
3.7.13 Enabling the Electronic Map
The electronic map supports the map files in .mif or .mid format. This view can directly display
the actual locations of the NEs in all areas.
Context
l or is located between the physical topology navigation tree and physical topology view.
l If both the topology view and topology navigation tree are displayed, you can click to
hide the topology navigation tree. Then the topology view extends to the area of the
topology navigation tree.
l If the topology navigation tree is not displayed, you can click to display the navigation
tree.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
----End
Context
You can customize the display of the following alarm states:
l Uncleared Fault Alarm
l Unacknowledged & Cleared Fault Alarm
l Unacknowledged & Uncleared Fault Alarm
l Unacknowledged Fault Alarm
l Acknowledged & Uncleared Fault Alarm
Uncleared fault alarms represent unacknowledged and uncleared fault alarms, and
unacknowledged and uncleared fault alarms. Unacknowledged fault alarms represent
unacknowledged and uncleared fault alarms, and unacknowledged and cleared fault alarms. To
know the meaning of each alarm state, refer to 2.1.3 Alarm Status.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the System Setting dialog box, select the Topology Status Display node.
Step 3 In Alarm status, select the status of the alarms that you want to display on the topology view.
Click Up or Down to adjust the display priority.
Step 4 Click OK.
----End
Context
You can switch the current subnet both on the navigation tree and the topology view. The
procedures are the same.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 On the navigation tree or the topology view, click a desired subnet to switch a current subnet to
the subnet.
----End
Context
l When the M2000 is started, the default filter condition is null, that is, the topology objects
in all types are displayed.
l When you filter the parent nodes in the navigation tree, indicates partially selected, and
indicates all selected.
Procedure
Step 1 Choose Topology > Main Topology.
----End
Related References
3.9.13 Parameters for Setting Topology Filter Display
Procedure
l On the topology toolbar, click to zoom in on the topology view.
l On the topology toolbar, click . Click in the topology view and drag a rectangle. The
elements in the rectangle are magnified.
l On the topology toolbar, click to reset the size of the topology view.
l On the topology toolbar, click to display all the elements in the topology window.
NOTE
When you click this button, the size of the topology elements may change, but the coordinates and shapes
do not change.
----End
Context
The resolution is determined by the screen size of the client, and is not always 1024 x 768 pixels.
Procedure
Step 1 Choose Topology > Main Topology.
----End
Context
l There are four layout modes: table, tree, star, and ring. You can select the mode according
to the actual requirements.
l If you select part of the topology objects, only the selected objects are laid out.
l If you do not select any object, all the objects in the topology view are laid out.
l Layout of a link or a link set refers to the layout of the NEs at the both end of the link.
l When you lay out topology objects, the M2000 places the figure corresponding to each
topology objects in the cell of a table. The row spacing and column spacing respectively
correspond to the height and width of the cell. The display effects of the figures are the
same.
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 In the topology view, select the topology objects for layout, and then click .
----End
Procedure
l On the toolbar, click to expand all the topology objects in the navigation tree.
l On the toolbar, click to collapse all the topology objects in the navigation tree.
l In the navigation tree, select one or multiple subnets. On the toolbar, click to expand
the selected subnets.
l In the navigation tree, select one or multiple subnets. On the toolbar, click to collapse
the selected subnets.
----End
Procedure
l On the toolbar, click . The topology objects in the navigation tree are sorted in the
ascending alphabetic order.
l On the toolbar, click . The topology objects in the navigation tree are sorted in the
descending alphabetic order.
NOTE
The topology objects are displayed by the order of subnets, NEs, links and link sets. The local NM is
displayed on the top either in the ascending or descending order.
----End
Procedure
Step 1 Choose Topology > Main Topology.
Step 2 Right-click in the topology view and choose Show Alarm Balloon.
When an alarm is raised, the number of the alarms of the highest level is displayed in the pop-
up pane on the upper left of the NE.
----End
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose System > Customize Topology Tips to view the Customize Topology Tips dialog
box.
By default, the system displays the configurable and activated counters of the first NE in the
navigation tree.
Step 2 Under the ToolTip node of the navigation tree, select an object on which a topology tip is
required. Then set the counter item in the right part of the dialog box.
----End
Prerequisite
You have logged in to the M2000 client.
Context
CAUTION
The setting takes effect the client is restarted.
Procedure
Step 1 Right-click the subnet on the topology view and choose Set to My Topology on the displayed
shortcut menu.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l If the electronic map is required, contact technical support engineers.
l The electronic map can help you color the districts, thus showing or hiding the names of
districts. Each district is marked with a unique color.
l You can double-click a province name to open the detailed map of the province.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 On the tool bar of the Main Topology window, select Electronic View from the Current
View drop-down list.. The electronic view is displayed.
Step 3 You can right-click and select Show District Name.
The names of districts are displayed in the electronic map view.
----End
Context
You can directly print the topology view by clicking Print in the Print Preview dialog box and
setting print attributes.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
----End
Related References
3.9.14 Parameters for Printing a Topology View
As shown in Figure 3-5, the Main Topology interface comprises three parts: physical topology
navigation, topology tool bar, physical topology view.
(1) Physical topology Displays the hierarchy of the objects on the topology
navigation view. You can locate the objects on the topology view
through the navigation tree.
(2) Topology toolbar The shortcut icon on the topology tool bar can be used
to perform operations easily and quickly on the
physical topology. For the description of the shortcut
menu, refer to Shortcut Menu in the Topology
View.
(3) Physical topology Displays all the devices managed by the M2000 in a
view map.
Topology Legend
On the topology view, the M2000 uses different icons to identify the objects such as subnet, NE,
group NE, and link.
Icon Description
Common subnet
Icon Description
Root
Custom view
Logical view
Core Net
Access Net
OMC
NOTE
On the topology view, different icons are used to
identify different NEs. To know the legend of each
NE and its meaning, refer to the Legend tab page on
the topology navigation tree.
BICCSCTPLINK
BICCSCTPLINK set
MTP3Link
MTP3Link set
Virtual link
Link set
NE State
l Connection State
On the physical topology, the connection states of the NEs are indicated by the NE icon
and the state icon. The state icon is located at the upper left of the NE icon. Multiple state
icons can be combined to indicate that the NE is in multiple states at the same time. For
details of NE connection states, refer to Table 3-7.
l Alarm State
If an physical NE raises an alarm, the color of the NE icon on the physical topology view
changes to show the alarm status of the NE. If an NE raises multiple fault alarms at the
same time, the color of the NE icon maps to the top alarm severity. In addition, an alarm
balloon appears beside the NE icon. The alarm balloon shows the severity ID and amount
of alarms.
To know how to set the icon color of each alarm severity, refer to 2.3.2.6 Setting the Alarm
Color. To set whether to display the alarm balloon on the topology view through the
shortcut menu, refer to Shortcut Menu in the Topology View.
Table 3-8 lists the samples of integrated alarm states.
In the physical topology view, the NEs are connected in a hierarchical way. When a fault
alarm occurs on the sub-NE of an NE, the following icons are displayed to indicate the
alarms. If there are several fault alarms occuring on a sub-NE at the same time, the NE icon
indicating the severest alarm is displayed.
To know how to set the icon color of each alarm severity, refer to 2.3.2.6 Setting the Alarm
Color.
Table 3-9lists the samples of alarm states.
NOTE
When multiple alarms are reported to the server from the NEs, the alarm statistical result on the NE
tip will be different from the real-time statistical result for a while.
Select
When you move the view, you click to
select the objects in the view.
Query Current l physical NE Query the current fault alarm of the NE.
Fault Alarm l physical link For details, see2.2.7.1 Querying
Current Fault Alarms.
Query Event l physical NE Query the event alarm of the NE. For
Alarm l physical link details, see2.2.7.3 Querying Event
Alarms.
Query History l physical NE Query the history fault alarm of the NE.
Fault Alarm l physical link For details, see2.2.7.2 Querying History
Fault Alarms.
Panels Service physical NE Start the panels service. The menu items
Management are displayed only after the mediation
software of the NE is installed on both the
M2000 server and client.
l Device Panel
l Monitor Panel
l Trace Panel
Set as Startup Subnet Set the subnet that is displayed when the
Subnet client is started.
Query link physical link View the link information. For details,
Information see3.6.6 Viewing/Modifying a Physical
Link.
The NodeB re-parenting tool is divided into four parts: navigation pane, search box, NE attribute
area, and re-parenting result table, as shown in Figure 3-6. Table 3-12 describes the four parts
shown in Figure 3-6.
SN Parameter Description
SN Parameter Description
Related Tasks
3.6.3 Moving a NodeB
3.6.3.1 Moving a NodeB in the Same RNC
3.6.3.2 Moving a NodeB to Another RNC
Basic Attribute
Name Description Settings
Objects Selection
Name Description Settings
Related Tasks
3.2.3 Creating a Physical Subnet
District Selected from the drop- District indicates the district of the NE.
down list For the users outside China, import the
files of their own district information.
District is unique and can not be null.
Subarea Selected from the drop- Indicates the subareas where the NEs
down list are located. The candidate NE subareas
are determined by the server side.
Template Name Selected from the drop- Indicates the parameter template of the
down list SNMP to be loaded.
Get Community String of characters Indicates the community name when the
Value range: 1-100 NMS sends the Get Community
request. Only when the community
This parameter cannot be name is the same as that recognized by
null. the NE, the Get Community can be
performed. The community name
works as password.
The supported SNMP versions are
SNMPV1 and SNMPV2c.
Set Community String of characters Indicates the community name when the
Value range: 1-100 NMS sends the Set Community request.
Only when the community name is
This parameter cannot be same as that recognized by the NE, the
null. Set Community can be performed. The
community name works as password.
The supported SNMP versions are
SNMPV1 and SNMPV2c.
Timeout Value range: 1-5 Indicates the waiting period after the
NMS sends operation requests to NEs.
The supported SNMP versions are
SNMPV1, SNMPV2c, and SNMPV3.
Devise User Name l Value range: 1-100 Indicates the user name in the security
l Numbers, English letters, model. The SNMPV3 provides the user-
and English underline _ based security model. Each user has
are allowed. their own private keys and authorization
keys.
The supported SNMP version is
SNMPV3.
Encrypt Protocol Select from drop-down list. Used to set private keys for users. If
encryption is not necessary, this
parameter can be NONE.
The supported SNMP version is
SNMPV3.
District Selected from the drop- Indicates the district of the NE.
down list For users outside China, import the files
of their own district information.
Equipment type Selected from the drop- Indicates the equipment type of the IP
down list device.
This parameter cannot be null.
Version Selected from the drop- Indicates the version of the IP device.
down list This parameter cannot be null.
Related Tasks
3.2.6 Creating an IP Device
Parameters
Parameter ID Description
Link Type Type of physical links. At present, the M2000 supports six
types of physical links: MTP3, MTP3B, DATALINK, M3UA,
H248, and BICCSCTP.
DATALINK, MTP3 and MTP3B links can only be created
manually. They support the following types of NEs:
l If one end of a MTP3 or MTP3B link is a physical MGW,
the other end of the link can be a physical MSC Server or
MSCe, or a virtual RNC or MSC Server.
l MTP3 and MTP3B links can be created between a physical
SGSN and a physical MSCe.
l DATALINK links can only be created between a physical
CG and a physical GGSN80 or SGSN.
M3UA, H248, and BICCSCTP links are automatically created
by the system. They support the following types of NEs:
l One end of a H248 or M3UA link can only be a physical
MGW, the other end of the link can be a physical MSC
Server or MSCe.
l BICCSCTP links can only be created between physical
MSC Servers.
Related Tasks
3.2.7 Creating a Physical Link
3.6.6 Viewing/Modifying a Physical Link
Parameters
Name Description Settings
Related Tasks
3.2.8 Creating a Virtual Link
3.6.7 Viewing/Modifying a Virtual Link
3.6.12 Deleting a Virtual Link
Parameters
Name Description Settings
Parameters
Parameter Description
All Ne Types NE types of the information export template, consisting of NEs in access
network series and core network series.
Save file to
Path for saving .ini files. You can directly enter a path or click and
select a path in the displayed Save dialog box.
Generate Select this option. You can enter information in the Comment Info pane.
comment The entered information is recorded in the exported .ini file.
information
Comment Info You can enter information only when the option Generate comment
information is selected.
Related Tasks
3.3.4.3 Exporting an NE Information Template (in .ini Format)
Parameter description
Parameter Value Range Description
District Selected from the drop-down Indicates the district of the NE.
list. For users outside China, import the files
of their own district information.
Subarea Selected from the drop-down Indicates the subareas where the NEs are
list. located. The candidate NE subareas are
determined by the server side.
NodebSubare Selected from the drop-down Indicates the subareas where the NodeBs
a list. that are managed by one RNC are
located.
Related Tasks
3.3.3 Creating a Physical NE
Parameters
Parameter Description
Stop creating in case of The system creates NEs one by one according to the sequence of
errors NE information in the CSV or INI file. If you select this option,
the system stops creating the following NEs when it fails to create
one. If not, the system displays a prompt when failed to create one
NE and continues to create the following NEs.
Script verify The script verify information such as verification progress and
information result is generated during the verification of the NE information
in the script file.
Related Tasks
3.3.4.7 Batch Creating Physical NEs
Parameters
Parameter Description
Connection Status State of the connections between the M2000 and NEs,
as described in NE State.
Related Tasks
3.5.1 Monitoring NE Status
Parameters
Parameter Value range Description
Related Tasks
3.6.4 Viewing/Modifying the Basic Attributes of a Subnet
Parameters
Name Description
Background Description:
To filter the background. Set whether to display the backgrounds of
the current view.
Subnet Description:
To filter the subnet. Set whether to display all the subnets in the
current view.
NE Description:
To filter the NE. Set whether to display all the NEs in the current
view.
Link Description:
To filter the link. Set whether to display all the links in the current
view.
Related Tasks
3.7.4 Display the filtered topology view
Parameters
Tab Parameter Description
General Print Service In this box, you can set the printer properties and
select to print a document to file. Name,
Status, Type and Info respectively refer to the
name, status, type and the information of the
selected printer. If it permits, you can click
Properties to set the printer properties. Print
To File shows that you can print a document to
a file.
Related Tasks
3.8 Printing a Topology View
Parameter Description
Parameter Value Range Description Supported
Parameter
Templates
Related Tasks
3.4.2 Modifying SNMP Parameter Templates
3.4.1 Creating SNMP Parameter Templates
Parameter Description
Parameter Description
Related Tasks
3.6.3 Moving a NodeB
3.6.3.1 Moving a NodeB in the Same RNC
3.6.3.2 Moving a NodeB to Another RNC
4 Security Management
This describes how to guarantee the security of the M2000. The M2000 security management
manages the user and the user's rights. Through the security management, the security of the
M2000 is guaranteed.
This describes how to delete an OM user group. You can delete an unwanted OM user group
based on the requirements to save the system resource. The deletion of an OM user group
indicates that only the authority of the OM user for the associated command groups is deleted.
After the deletion, the OM user still exists without belonging to any user group.
4.8 Deleting an OM User
This describes how to delete an OM user. Based on the requirements, you can delete an unneeded
OM user to save the system resource. If an OM user already has the binding relationship with
an NE, the user bound to the NE is also deleted when you delete an OM user. In this way, the
information on the OM user is removed from the M2000.
4.9 Querying Authorization
You can query the authorization of the NEs and the M2000 rights in the M2000.
4.10 Comparing the OM User Rights
You can compare the rights of two users in the M2000.
4.11 Managing NE Users
This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain
NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can
maintain and operate NEs through NE users.
4.12 Managing Northbound Users
For the M2000, northbound users refer to those access the M2000 through northbound interfaces.
On the M2000 client, you can manage northbound users, operators, and their relations.
4.13 Monitoring OM Users
This describes how to monitor an OM user. The M2000 offers the user-monitoring function to
monitor users' login and operations. This prevents illegal users from attacking the system.
4.14 Reference for Security Management Interfaces
This part describes the security management interface and the parameters, which can help you
perform the related operations.
an OM user account
A user account is the identification for OM. On M2000 networks, the user account consists of
the OM user account and NE user account.
l The NE users operate and maintain NEs through the LMT. This describes OM users.
l OM users operate and maintain the entire network or specified NEs through the M2000.
The user authority consists of the user, operation, and NE. That is, the user authority defines the
operations that users perform. When you assign authority to OM users, consider that the
operation is performed through the M2000 client or the MML commands.
Authority Item
According to whether NEs are involved in the operations, the M2000 authority is categorized
into network management application authority and network device authority. The network
management application authority does not involve the operations related to the devices on the
M2000, such as creating a user and viewing user logs. The network device authority involves
the operations related to the devices on the M2000, such as viewing NE operation logs and
downloading NE software.
According to the functions, NEs divide the MML commands into several command groups. You
can customize command groups according to actual requirements. You can grant the authority
of the MML command group to a specified user. In this way, the user can run all the commands
in the command group.
Allocation Mechanism
To simplify the allocation of user authority, 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.
You can grant the authority of several MML command groups of specified NE types to an OM
user or OM user group. In this way, you can create an authority rule. After the authority rule is
created, you can distribute the rule to specific NEs. In this way, the OM user or OM user group
have the authority to the MML commands of the NEs. If the authority rule is successfully created,
the OM user or OM user group automatically have the authority to the MML commands of new
NEs of this NE type.
Related Tasks
4.5.4 Assigning Operation Rights to an OM User Group
4.5.10 Assigning Operation Rights to an OM User
4.6.3.2 Modifying the Operation Rights of an OM User
4.6.2.2 Modifying the Operation Rights of an OM User Group
Related References
4.14.9 Parameters for the Operation Authority of an OM User or an OM User Group
4.1.3 NE User
This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain
NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can
maintain and operate NEs through NE users. The NE user can also troubleshoot NEs at the near
end of NEs.
Type of NE Users
NE users consist of local NE users and non-local NE users.
l 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. NEs provide several
default local users.
l 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.
The user information are independent from each other. The system cannot synchronize the information
about the two accounts. You need to manually synchronize the information about the NE user on the
M2000 and the local user in the NEs.
Prerequisite
l You have logged in to the M2000 client.
l You have the relevant operation authorization.
Procedure
Step 1 Choose Security and select an option to enter the related security management interface.
Step 2 Click the shortcut icon at the upper part of the navigation tree to obtain the latest information.
----End
You can set the Access Control List(ACL) to allow the users to log in to the M2000through the
clients of only the specific IP addresses or network segment.
4.3.4 Setting FTPS Parameters
This describes how to set the FTPS parameters.
Related References
4.14.15 Parameters for the System Security Policy
Context
l The password dictionary is a password set of characters or strings. In the password
dictionary file, each row contains only one character or string. The suffix of each password
dictionary file is dic. The file is in $iManagerM2000Client/etc/conf/pwddic/ on the
M2000 server.
l The number of the password dictionary files are not limited in the M2000, but the total
rows in all the password dictionary files cannot exceed 5000.
Procedure
Step 1 Choose Security > Security Policy.
----End
Related References
4.14.15 Parameters for the System Security Policy
Context
l When you log in to the M2000, if the failed login times exceed the value defined in Max.
Login Attempts, the account is locked to prevent attacks from illegal users to the
M2000.
l When your account is locked, the user who has the unlock right can unlock your account.
You can also wait for the M2000 to unlock your account automatically. The unlock time
is defined in the account policy.
Procedure
Step 1 Choose Security > Security Policy.
Step 3 In the right pane, set the policies such as the maximum login attempts and auto unlock time.
----End
Related References
4.14.15 Parameters for the System Security Policy
Context
l The number of sessions is the number of the connections between the M2000 client and
the M2000 server.
l The value defined in Maximum Sessions does not exceed the license threshold of the
M2000. If the number of current sessions exceeds the value defined in Maximum
Sessions but does not exceed the license threshold of the M2000, the admin can still log
in to the M2000.
Procedure
Step 1 Choose Security > Security Policy.
Step 3 In the right pane, set the maximum number of the sessions that are supported by the M2000.
----End
Related References
4.14.15 Parameters for the System Security Policy
Context
CAUTION
l Only the admin user and the members of the Administrators group can set single-user mode.
l Only the admin can log in to the M2000 through a client and all the other users are forced to
log out after the M2000 is switched from multiuser mode to single-user mode. Please switch
to multiuser mode after you complete the operations in single-user mode.
Procedure
Step 1 Choose System > Preferences.
Step 2 In the navigation tree on the left, select System Login Mode.
Step 3 In the System Login Mode group box, select Single user mode.
----End
Context
To set the system ACL, you must have the Edit Security Policy right.
Procedure
Step 1 Choose Security > Access Control List.
Step 2 In the Access Control List window, specify the IP addresses of the clients that can log in to the
M2000 server.
l Click Add. In the New System Access Control Item dialog box, enter the IP address or
network segment and description. Click OK.
l Select the IP addresses or network segment that need to be modified, and then click
Modify. In Modify System Access Control Item, modify relevant information, and then
click OK.
l Select the IP addresses or network segment that need to be deleted, and then click Delete.
In the Confirm dialog box, click Yes.
Step 3 In the Access Control List window, click Close.
----End
Prerequisite
l The M2000 system is operational.
l NEs support the FTPS function.
l The FTPS client is connected to the FTPS server.
Procedure
Step 1 Choose Software > FTPS Parameters Setting .
The FTPS Parameters Setting dialog box is displayed.
Step 2 Set Encrypted Mode, Supported State, Transmission Mode, Firewall Traversal
Supported, Progress Interval (seconds), Command Port, Data Port, Transmission Size
(bytes), Min. Port, and Max. Port.
For detailed parameter description, refer to 4.14.16 Parameters for FTPS Parameter.
CAUTION
The settings of the parameters except Command Port and Data Port are applicable to only the
M2000 that serves as the FTPS client.
----End
Related Concepts
4.1.5 Introduction to the FTPS
Related References
4.14.16 Parameters for FTPS Parameter
actual requirements. You can grant the authority to the MML commands of command groups
to a specified user. In this way, the user can run all the commands in the command group.
Related Tasks
4.5.6 Granting MML Authority to an OM User Group
4.5.13 Grant MML authority to an OM user
4.6.3.4 Modifying the MML Authority to an OM User
4.6.2.4 Modifying the MML Authority to An OM User Group
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed.
Step 2 Select an NE type node from the navigation tree. Right-click and choose Customize Command
Group. You can also click Customize Command Group in the right pane.
Step 3 In the displayed Customize Command Group dialog box, click Add.
Step 4 Set the information about the command group in the Add Command Group dialog box.
1. Choose the name of the new command group in the Name drop-down list.
Value range: M_0 to M_14.
2. Enter the description of the command group in Description.
3. Choose the command to be added to the command group from the Command navigation
tree.
Step 5 Click OK.
The new command group is displayed in the Customize Command Group window.
Step 6 Click Close to close the Customize Command Group dialog box.
----End
Result
New NEs of a certain type automatically have the authority to the custom command group.
Postrequisite
You can also issue the NE type command group to a specific NE, and then the NE obtains the
authority to the custom command group. The detailed procedures are as follows:
1. Set the authority rules of NE type. For details, refer to 4.4.3 Setting Authority Rules for
NE Types.
2. Issue authority rules to a specific NE. For details, refer to 4.4.4 Issuing Authority Rules
for NE Types.
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed.
Step 2 You can use either of the following three methods to customize an NE command group.
Method one 1. Select a specific NE node under the NE type node from the
navigation tree. Right-click the node and choose Add Command
Group. You can also click Add on the Command Group tab
page in the right pane.
2. Choose the name of the new command group in Name. Enter the
description of the command in Description.
3. Choose the command to be added to the command group from the
Command navigation tree.
4. Click OK.
Method two 1. For details about customizing an NE type command group, refer
to 4.4.1 Customizing an NE Type Command Group.
2. For details about creating authority rules of NE type, refer to 4.4.3
Setting Authority Rules for NE Types.
3. Issue the authority rule to the specific NE so that the NE owns the
customized command group authority of the NE type. For details,
refer to 4.4.4 Issuing Authority Rules for NE Types.
Step 3 You can issue the authority to the custom command group to a specific user.
For details, refer to 4.5.13 Grant MML authority to an OM user.
----End
Related References
4.14.14 Parameters for Customizing an NE Command Group
Prerequisite
The NEs are available before the authority rule of the NE type is created.
Procedure
l Start the setting from the NE User Management window.
1. Choose Security > NE User Management. The NE User Management window is
displayed.
2. Select the NE type node on the navigation tree. Right-click the node and select Setting
Rule , or click Setting Rule in the right window.
3. In the displayed Setting Rule dialog box, select the user and the corresponding
command group. Click OK.
The change in the NE type does not affect the existing NEs. You can manually modify
the authorization through 4.4.4 Issuing Authority Rules for NE Types.
l Start the setting from the Security Management window.
1. Choose Security > Security Management . The Security Management window is
displayed.
2. Select the user or user group node on the navigation tree. Right-click the node and
select Setting Rule, or click Setting Rule in the Rules tab at the right window.
3. In the displayed Setting Rule dialog box, select the NE type, the corresponding
command group, and the user or user group . Click OK.
The change in the NE type does not affect the existing NEs. You can manually modify
the authorization through 4.4.4 Issuing Authority Rules for NE Types.
----End
Related References
4.14.5 Interface Description: Authority Rules for NE Type
Prerequisite
l You have logged in to the M2000 client.
l The authority rules for NE types are already created.
Procedure
Step 1 Choose Security > NE User Management. The NE User Management window is displayed.
Step 2 Issue the authority rules for NE types to specific NEs.
Issue all the set authority rules for this Mode one:
type. 1. Select the NE type node whose authority rules
are to be issued from the navigation tree.
Right-click the node and choose Apply
Rule or click Apply Rule in the right pane.
2. In the displayed Confirm dialog box, click
Yes.
3. Choose the NEs whose authority rules are to
be loaded in the Apply Rule dialog box and
click Start.
4. Click Close to close the Apply Ruledialog
box.
Mode two:
1. Choose the NE types whose authority rules
are to be loaded from the navigation tree.
Right-click and choose Load Rule or click
the Binded NE tab and choose Load Rule.
2. In the displayed Confirm dialog box, click
Yes.
Issue some of the set authority rules for 1. Choose the NE types whose authority rules
this type. are to be issued from the navigation tree.
Choose the authority rules to be issued in the
right pane. Click Apply Rule.
2. In the displayed Confirm dialog box, click
Yes.
3. Choose the NEs whose authority rules are to
be loaded in the Apply Rule dialog box and
click Start.
4. Click Close to close the Apply Ruledialog
box.
NOTE
You can use Ctrl or Shift key to selectively issue the
authority rules.
l After the authority rules are applied to the selected NEs, the custom command groups set in
the rules are added to the command groups preset for the NE. In addition, the added command
groups are named in the same format as that of the command group parameters.
l After the authority rules are applied to an NE, you can modify the added command groups.
The modification, however, does not affect the authority rules.
----End
Result
After the NE type authority rule applies to the NEs created for this NE type, the original NE
MML command authority of the OM user is invalid. In this case, the MML command authority
of the user is the NE type authority rule.
Context
The security data includes the following information: name, password, password policy, system
mode, account policy, password validity period, login duration, binding IP address, system
policy, inactive user policy (hibernate, delete), and user group information.
Procedure
Step 1 Choose Security > NE User Management. The NE User Management window is displayed.
Step 2 Right-click the NE to be synchronized under the NE node in the navigation tree and choose
Synchronize Security Data from the shortcut menu. Then the security data on the M2000 is
synchronized with the NE.
----End
4 Assigning rights of new NEs to Distribute the rights for the new
an OM user group equipment to the user group to
benefit the users by managing the
new equipment.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, right-
click the User Group node and choose New User Group.
Step 3 In the Add User Group dialog box, on the Detail tab, set Name and Description.You can also
click Add to select the user you want to add to the user group, and then click Copy Rights From
User Group to copy operation rights from other user groups.
Step 4 Optional: If you want to set the managed domain for the user group, in the New User Group
dialog box, click the Domain tab. Set the objects that are managed by the user group.
Step 5 Optional: If you want to set operation rights for the user group, in the New User Group dialog
box, click the Operation Rights tab. Set operation rights for the user group.
Step 6 Optional: If you want to set new NE rights for the user group, in the New User Group dialog
box, click the New Device Rights tab. Set new NE rights for the user group.
Step 7 Click OK.
----End
Related References
4.14.8 Parameters for Adding an OM User Group
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node, Select the user group you want to set.
Step 3 In the pane on the right, click the Domain tab.
Step 4 On the Domain tab, click Add.
Step 5 In the navigation tree of the Add Domain dialog box, select the managed objects for the user
group, and then click OK.
----End
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The
Administrators group has all the operation rights. You cannot change the rights of this group.
You can change the rights of the Guests and Operators.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node, Select the user group you want to set.
Step 3 From the pane on the right, click the Operation Rights tab.
Step 4 On the Operation Rights tab, click Add.
Step 5 In the Add Operation Rights dialog box, select the device type and corresponding rights. Click
OK.
NOTE
If the type of the selected operation right is Network Device, you can do as follows:
l You need to add the device to the managed domain of the user group before you set the operation rights to
the device.
l Select the device in the left navigation tree, and select the operation rights to the device in the list on the
right to add the operation rights.
l In the left navigation tree, right-click an NE or an object of an unknown type and choose Copy Rights. Then
in the right navigation tree, right-click another NE or another object of an unknown type and choose Paste
Rights to paste the rights of an NE or an object of an unknown type to another NE or another object of an
unknown type.
l In the left navigation tree, right-click an NE and choose Copy Rights to. In the Copy Rights to Devices of
the Same Type dialog box, select the device where you want to paste the rights, and then click OK. The
rights of an NE are copied to other NEs of the same type.
----End
Related Concepts
4.1.2 User Authority
Related References
4.14.9 Parameters for the Operation Authority of an OM User or an OM User Group
Context
The Administrators user group has all the rights. You cannot change rights of this group.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node, Select the user group you want to set.
Step 3 In the pane on the right, click the New Device Rights tab.
Step 5 In the Add New Device Rights dialog box, select relevant rights, and then click OK.
----End
Prerequisite
l You are authorized with the relevant privileges.
l NEs communicate normally with the M2000.
l NEs support binding.
l You are familiar with the policy of authority assignment of the M2000.
Context
To reduce work effort, you can set the rule for NE type authority to grant the authority of some
MML commands of the specific NE types to an OM user or group. If the authority rule is
successfully created, the OM user or OM user group automatically have the authority to the
MML commands of all new NEs of this NE type.
NOTE
l When you assign MML command authority to OM user groups, the M2000 does not display the defined
rules of NE type authority. The MML command authority of a user group is the union of the NE MML
command authority and NE type authority rule.
l After you assign NE MML command authority to an OM user group and then issue NE type authority
rule to this NE, the NE MML command authority is invalid. In this case, the MML command authority
of the user group is the NE type authority rule.
For details about how to set and issue NE type authority rules, refer to 4.4.3 Setting Authority
Rules for NE Types and 4.4.4 Issuing Authority Rules for NE Types.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose a specific user group in the User Group node from the navigation tree. Click the Binded
NE tab in the right pane.
Step 4 In the Bind NE dialog box, choose a user group, an NE type, and a command group. Click
OK or Apply to assign the MML authority to an OM user group.
l Click OK to save the settings and close the dialog box.
l Click Apply to save the setting, but the dialog box is not closed. You can continue to assign
the MML authority to other user groups.
----End
Related Concepts
4.1.2 User Authority
Related Tasks
4.4 Customizing MML Authority
Related References
4.14.10 Parameters for the MML Authority to an OM User Group or an OM User
4.14.4 Interface Description: MML Authority Information of an OM User
Context
l When the default account policy is used, the user name must contain from 6 to 32 characters.
l You can modify the minimum length of the user name by setting the account policy.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, right-click
the User node and choose New User.
Step 3 In the New User dialog box, on the Detail tab, set Name, Description, and Password.
Step 4 Optional: If you want to add the user to a user group, in the New User dialog box, click the
User Groups tab. Select the user group to which you want to add the user.
Step 5 Optional: If you want to set the managed domain for the user, in the New User dialog box, click
the Domain tab. Set the objects that are managed by the user.
Step 6 Optional: If you want to set operation rights for the user, in the New User dialog box, click the
Operation Rights tab. Set operation rights for the user.
Step 7 Optional: If you want to set the ACL for the user, in the New User dialog box, click the Access
Control List tab. Set the ACL for the user.
Step 8 Click OK.
----End
Related References
4.14.13 Parameters for Creating an OM User Account
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Select a user under the User node on the navigation tree. Right-click the node and select
Synchronize User Data, or click Synchronize User Data in the NE tab.
NOTE
If the selected user does not have the NEs to which they are bound, the NEs cannot be synchronized.
Step 3 Select the NEs to be synchronized in the Synchronize User Data dialog box. Click Start to
synchronize the OM user data with that of the NEs.
The Synchronize User Data dialog box displays the progress of synchronizing OM user data
to the NEs.
Step 4 Click Close. The Synchronize User Data dialog box is closed.
----End
Context
You cannot add the Administrator user to a user group.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node. Select the user you want to set.
Step 3 In the pane on the right, click the User Groups tab.
Step 5 In the Add User Group dialog box, select the user group to which you want to add the user.
Click OK.
----End
Context
l You cannot set the operation rights of the admin user.
l When you set the operation rights for a user, the M2000 does not display the rights of the
user group to which the user belongs. The final rights of the user are the combination of
rights assigned to the user and the user group to which the user belongs.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node. Select the user you want to set.
Step 3 From the pane on the right, click the Operation Rights tab.
Step 4 On the Operation Rights tab, click Add.
Step 5 In the Add Operation Rights dialog box, select the type of operation rights and the
corresponding rights. Click OK.
NOTE
Step 6 Optional: Select Show access from user group. The operation rights of the user group are
displayed in gray in the operation rights list.
----End
Related Concepts
4.1.2 User Authority
Related References
4.14.9 Parameters for the Operation Authority of an OM User or an OM User Group
Context
l You cannot set the managed domain for the admin user.
l When you set the management domain for a user, the M2000 does not display the
management domain of the user group to which the user belongs. The final management
domain of the user is the union of the assigned management domain and the management
domain of the user group to which the user belongs.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node. Select the user you want to set.
Step 5 In the navigation tree of the Add Domain dialog box, select the managed objects, and then click
OK.
----End
Context
l To set the user ACL, you must have the User Management right.
l The system ACL allows all the OM users to log in to the M2000 through the clients of only
the specific IP addresses or network segment. The user ACL is a subset of the system ACL.
The user ACL is effective for only the current user.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node. Select the user you want to set.
Step 3 In the pane on the right, click the Access Control List tab.
----End
Prerequisite
l You have logged in to the M2000 client.
l Relevant NEs are properly connected to the M2000.
Context
To reduce work effort, you can set the rule for NE type authority to grant the authority of some
MML commands of the specific NE types to an OM user or group. If the authority rule is
successfully created, the OM user or OM user group automatically have the authority to the
MML commands of all new NEs of this NE type.
NOTE
l When you assign MML command authority to OM users, the M2000 does not display the defined rules
of NE type authority. The MML command authority of a user is the union of the NE MML command
authority and NE type authority rule.
l After you assign NE MML command authority to an OM user group and then issue NE type authority
rule to this NE, the NE MML command authority is invalid. In this case, the MML command authority
of the user is the NE type authority rule.
For details about how to set and issue NE type authority rules, refer to 4.4.3 Setting Authority
Rules for NE Types and 4.4.4 Issuing Authority Rules for NE Types.
Procedure
l Start the setting from the Security Management window.
1. Choose Security > Security Management . The Security Management window is
displayed.
2. Choose a user in the User node from the navigation tree. Right-click the user and
choose Bind NE. You can also click Bind NE on the NE tab page in the right pane.
3. In the displayed Bind NE dialog box, choose the command group to be assigned and
NEs.
4. Click OK to assign the MML authority to an OM user.
l Start the setting from the NE User Management window.
1. Choose Security > NE User Management. The NE User Management window is
displayed.
2. Open the Bind Command Group window.
You can choose either of the following two methods:
– Select a specific NE node from the navigation tree. Right-click the node and choose
Bind Command Group. You can also click Bind Command Group on the NE
tab page in the right pane.
– Select an NE user node from the navigation tree. Right-click the node and choose
Bind Command Group. You can also click Bind Command Group on the
Command Group tab page in the right pane.
3. In the displayed Bind Command Group dialog box, choose the command group to
be assigned and OM user.
4. Click OK to assign the MML authority to an OM user.
----End
Postrequisite
After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs.
You can choose Security > NE User Management and choose the NE user that maps to the
OM user from the navigation tree. Click the Command Group tab to view the information about
the assigned MML commands.
Related Concepts
4.1.2 User Authority
Related Tasks
4.4 Customizing MML Authority
Related References
4.14.10 Parameters for the MML Authority to an OM User Group or an OM User
4.14.4 Interface Description: MML Authority Information of an OM User
to which the OM user belongs, management domain, operation rights, access control list, MML
command authorization of the managed NEs, and the authorization rule.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Select an OM user node under the User node on the navigation tree. Check the information about
the OM user in each tab of the right window.
l The Detail tab: displays the fundamental information about the OM user, such as user name,
login time, and time for modifying the password.
l The User Groups tab: displays the user group to which the OM user belongs.
l The Domain tab: displays the managed objects of the OM user.
l The Operation Rights tab: displays the operation rights of the OM user.
l The Access Control List tab: displays the IP addresses on the client from which the OM
user can log in to the M2000.
l The Bind NE tab: displays the MML command authorization that the OM user owns.
l The Rules tab: displays the authorization rule of the NE type set by the OM user.
----End
Related References
4.14.11 Parameters for the Information of an OM User
Prerequisite
l You have logged in to the M2000 client.
l You have the management authorization of the user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The
Administrators have all the authorities. You are not allowed to modify the management domain
of this user. You can modify the management domain of Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose a specific user group whose management domain is to be modified under the User
Group node from the navigation tree. Click Domain in the right pane.
The objects managed by a user group are listed as a navigation tree on the Domain tab page.
----End
Prerequisite
l You have logged in to the M2000 client.
l You have the management authorization of the user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators.
Administrators have all the rights. You cannot modify the operation rights of this user group.
You can, however, modify the operation rights of Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Select the user group for the adjustment under the User Group in the navigation tree. Click
Operation Rights at the right window.
In the Operation Rights tab, the operation rights owned by the user group are listed in table.
Add the operation rights. 1. Click Add or right-click and choose Add.
2. In the displayed Add Operation Rights
window, select the type of the operation rights
and the corresponding rights.
3. Click OK.
Delete the operation rights. 1. In the list of the operation rights, select the
unnecessary operation rights. Then, click
Delete, or right-click the list and select
Delete.
2. Click Yes in the displayed Confirm dialog
box.
----End
Related Concepts
4.1.2 User Authority
Related References
4.14.9 Parameters for the Operation Authority of an OM User or an OM User Group
Prerequisite
l You have logged in to the M2000 client.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The
Administrators group has all the operation rights. You cannot change the rights of this group.
You can change the rights of the Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose a specific user group to whom the authority to new devices is to be modified under the
User Group node from the navigation tree. Click New Device Rights in the right pane.
The authority to new devices in the user group is displayed in table format on the New Device
Rights tab page.
Add authority to new devices 1. Click Add or right-click and choose Add.
2. In the displayed Add New Device Rights
dialog box, choose the authority to be added.
3. Click OK.
Delete authority to new devices 1. Choose the authority to be deleted from the
New Device Rights list.
2. Click Delete or right-click and choose
Delete.
3. In the displayed Confirm dialog box, click
Yes.
----End
Prerequisite
l You have the management authorization of the user group.
l NEs communicate normally with the M2000.
l NEs support binding.
l You are familiar with the policy of authority assignment of the M2000.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose the specific user group to whom the MML authority is to be modified from the User
Group node in the navigation tree, right-click the user group and choose Bind NE from the
shortcut menu. You can also click Bind NE on the Bind NE tab page.
Step 3 In the displayed Bind NE dialog box, choose the NE type and command group.
----End
Related Concepts
4.1.2 User Authority
Related Tasks
4.4 Customizing MML Authority
Related References
4.14.10 Parameters for the MML Authority to an OM User Group or an OM User
4.14.4 Interface Description: MML Authority Information of an OM User
Prerequisite
l You have logged in to the M2000 client.
l You have the authority to manager users.
Context
User admin has all the authority. You are not allowed to change the authority of this user.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose a specific user in the User node from the navigation tree. Click the User Groups tab in
the right pane.
Step 3 Adjust the user group to which the OM user belongs according to actual requirements.
Delete the OM user from a user group. 1. Choose a user group that needs not be bound to
the OM user from the list, and click Delete.
Alternatively, right-click it and choose Delete
on the shortcut menu.
2. In the displayed Confirm dialog box, click
Yes.
Add the OM user to a user group. 1. Click Add or right-click and choose Add.
2. Choose a user group in the displayed Add User
Group dialog box.
3. Click OK.
----End
Prerequisite
l You have logged in to the M2000 client.
l You have the authority to manager users.
Context
User admin have all the authority. You are not allowed to change the operation authority of this
user.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose the specific user under the User node from the navigation tree. Click the Operation
Rights tab in the right pane.
l The operation rights that an OM user directly obtains is listed on the Operation Rights tab
page in table format.
l Select Show access from user group. The operation rights of the user group are displayed in
the operation rights list.
Step 3 Adjust the operation rights of an OM user
Add the operation rights. 1. Click Add or right-click and choose Add.
2. In the displayed Add Operation Rights
window, select the type of the operation rights
and the corresponding rights.
3. Click OK.
Delete the operation rights. 1. In the list of the operation rights, select the
unnecessary operation rights. Then, click
Delete, or right-click the list and select
Delete.
2. Click Yes in the displayed Confirm dialog
box.
----End
Related Concepts
4.1.2 User Authority
Related References
4.14.9 Parameters for the Operation Authority of an OM User or an OM User Group
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node. Select the user you want to set.
Step 3 In the pane on the right, click the Access Control List tab.
----End
Prerequisite
l You have the authority to manager users.
l NEs communicate normally with the M2000.
l NEs support binding.
l You are familiar with the policy of authority assignment of the M2000.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Choose the specific user to whom the MML authority is to be modified from the User node in
the navigation tree, right-click the user and choose Bind NE from the shortcut menu. You can
also click Bind NE on the Bind NE tab page.
Step 3 In the displayed Bind NE dialog box, choose the NE type and command group.
----End
Related Concepts
4.1.2 User Authority
Related Tasks
4.4 Customizing MML Authority
Related References
4.14.10 Parameters for the MML Authority to an OM User Group or an OM User
4.14.4 Interface Description: MML Authority Information of an OM User
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, in the Security Management navigation tree, expand
the User node. Select the user whose information you want to modify. Click the Detail tab from
the pane on the right.
Step 3 On the Detail tab, modify the parameters in Description, Enable/Disable user account, and
Valid time.
Step 4 Click Apply.
----End
Related References
4.14.11 Parameters for the Information of an OM User
Context
l The minimum length of the user password can be set in the password policy. For the
description of setting password policy, see 4.3.1.1 Setting the Password Policy. By
default, the length of the common user's password is 7. The value ranges from 7 to 16. The
length of the admin's password ranges from 8 to 16.
l The user admin can reset the password of any user. The users in the Administrators group
can reset the passwords of the users that are in other groups. If the users that are not in the
Administrators group have the Reset Password right, they can reset the passwords of the
users that are not in the Administrators group. If the users that are not in the Administrators
group do not have the Reset Password right, they can reset only their own passwords.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window in the Security Management navigation tree, expand
the User node. Right-click the user whose password you want to reset, and then select Reset
Password.
NOTE
You can choose Security > Change Password to modify the password of the current login user.
Step 3 In the Reset Password dialog box, set New Password and Confirm Password, and then click
OK.
Step 4 In the Confirm dialog box, click OK.
----End
Context
NOTE
If an user in the OM user group has logged in to the server, the user group cannot be deleted.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Click the User Group node on the navigation tree. Delete a user group using the following two
methods:
l Right-click a user group under User Group and choose Delete.
l Choose the user group to be deleted in the right pane, and then click Delete or right-click the
user group and choose Delete to delete the user group.
Step 3 In the displayed Confirmation dialog box, click Yes to delete the selected OM user.
After the deletion, the users on the M2000 can be regrouped and have new authority.
----End
Context
NOTE
The admin users and active users are not allowed to be deleted.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed.
Step 2 Remove an OM user
You can choose either of the following two methods:
l Click a specific user under the User node in the navigation tree, right-click the user, and then
choose Delete.
l Choose the User node in the navigation tree. Choose the OM user to be deleted in the right
pane and click Delete or right-click the user and choose Delete.
----End
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management window, click on the top of the Security Management
navigation tree.
Step 3 In the Authorization Details dialog box, in the Topology Root navigation tree, select the name
of a device . Then select rights from the rights navigation tree.
The table on the right of the Authorization Details dialog box displays the users and user groups
to which the right is assigned.
----End
Procedure
Step 1 In the Security Management window, click on the top of the Security Management
navigation tree.
Step 2 In the Select User for Compare dialog box, select two users.
Step 3 Click OK.
The comparison result is displayed in the Compare User Rights Result dialog box.
----End
Context
For difference between users of category A and category B/C NEs, refer to 4.1.3 NE User.
4.11.1 Creating an NE User
This describes how to operate and maintain NEs when they are disconnected from the M2000
or M2000. You can create an NE user, and then log in to the LMT as the NE user. In this way,
you can operate and maintain NEs.
Prerequisite
Before you create a user of category B/C NEs, you need to create an NE local user on NE side.
Context
For difference between users of category A and category B/C NEs, refer to 4.1.3 NE User.
Procedure
l Create a user of category A NEs
1. Create an OM user on the M2000 side.
For details, see 4.5.7 Creating an OM User Account.
2. Assign the authority of the MML commands to an OM user
For details, see 4.5.13 Grant MML authority to an OM user.
l Create a user of category B/C NEs
1. Choose Security > NE User Management, the NE User Management window is
displayed.
2. Select a specific category B/C NE node from the navigation tree, and then right-click
the node and choose New NE User from the shortcut menu. Or you can click New
NE User in the right pane. You can also right-click on the right pane and choose New
NE User.
3. Set user information in the displayed New NE User dialog box.
NOTE
The information about the new NE user and NE local user is separate from each other. The
system cannot synchronize the information about the two user accounts. You need to manually
synchronize the information about the NE user on the M2000 and the local user in the NEs.
4. Click OK.
----End
Related Concepts
4.1.3 NE User
Related References
4.14.2 Interface Description: NE User Management Interface
4.14.12 Parameters for NE User
Context
NOTE
If you delete a category A NE user, the binding relationship between an OM user and NE is deleted. The
OM user exists.
For difference between category A and category B/C NEs, refer to 4.1.3 NE User.
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed.
Step 2 Delete an NE user.
----End
Context
For detailed description of category A NE users and category B/C NE users, refer to 4.1.3 NE
User. For detailed description of category A/B/C NEs, refer to 3.3.1 NE Types.
Procedure
l 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. Therefore, you can modify a category NE user by changing
the password of the corresponding OM user password. For details, see 4.6.5 Modifying
the Password of an OM User .
l Change the password of the category B/C NE user.
1. Choose Security > NE User Management.
2. In the NE User Management window, in the NE User Management navigation tree,
expand the NE type node. Click the NE user whose password you want to change, and
then choose Change Password .
3. In the Change Password dialog box, select Effect Range. Enter the value of Old
Password. Set New Password and Confirm Password.
NOTE
l When Modify the NMS password only is selected for Effect Range, Old Password is input
by the system automatically.
l If you select Modify the NMS password only, it indicates to modify only the password that the
NE user uses to log in to the M2000.
4. Click OK.
5. In the Confirm dialog box, click OK.
----End
Context
For differences between users of category A and category B/C NEs, refer to 4.1.3 NE User.
Procedure
Step 1 Choose Security > NE Login Management, the NE Login Management window is displayed.
Step 2 Choose the OM user to be associated with the NE user from the navigation tree, right click the
user and choose Associate NE User. Or you can click Associate NE User in the right pane.
You can also right-click on the right pane and choose Associate NE User.
Step 3 Choose the NEs to be associated with the OM user from the navigation tree. Choose the NE user
to be associated in the table in the right pane. Click Set Association.
l All category B/C NEs on the M2000 are displayed in the navigation tree in the dialog box.
The selected NE users are displayed in the table in the right pane.
l For the same NE, one OM user can bind only one NE user.
l One OM user can be bound to a maximum of 255 NE users.
----End
Related References
4.14.3 Interface Description: NE Login Management Interface
Prerequisite
The OM user associates with the category B/C NE user.
Context
For difference between users of category A and category B/C NEs, refer to 4.1.3 NE User.
Procedure
Step 1 Choose Security > NE Login Management, the NE Login Management window is displayed.
Step 2 Choose the OM user whose association is to be deleted from the navigation tree. Choose one or
more associated NE users in the right pane.
Step 3 Click Delete Association, or right-click the menu and choose Delete Association .
----End
Related References
4.14.3 Interface Description: NE Login Management Interface
Related Concepts
4.1.4 Northbound User
Related References
4.14.17 Parameters for Northbound User
Prerequisite
l The M2000 system is operational.
l The logged-in user is authorized to create a northbound user and the operator that the created
northbound user belongs to exists. If the information about the operator that the user belongs
to does not exist, refer to 4.12.4 Adding the Operator.
Procedure
Step 1 Choose Security > NMS.
The NMS User Management window is displayed.
Step 2 Click Add. In the displayed Add NMS User dialog box, set User Name, Password, and
Operator Info.
For detailed parameter description, refer to 4.14.17 Parameters for Northbound User.
----End
Related Concepts
4.1.4 Northbound User
Related References
4.14.17 Parameters for Northbound User
Prerequisite
l The M2000 system is operational.
l The logged-in user is authorized to modify the information on a northbound user.
l The northbound user whose password need be changed already exists.
Procedure
Step 1 Choose Security > NMS.
The NMS User Management window is displayed.
Step 2 To change the password of a northbound user, you can use either of the following methods:
Method II 1. Select a line of user information from the list on the right part
of the window, and then double-click the line or click
Attribute.
2. In the displayed Attribute dialog box, select Change
Password.
3. Enter a new password of the northbound user in the New
Password and Confirm Password fields.
----End
Related Concepts
4.1.4 Northbound User
Related References
4.14.17 Parameters for Northbound User
Prerequisite
l The M2000 system is operational.
l The logged-in user is authorized to delete northbound users.
l The northbound user to be deleted exists.
Procedure
Step 1 Choose Security > NMS.
The NMS User Management window is displayed.
Step 2 To delete a northbound user, you can use either of the following methods:
Method I Select the node to be deleted under NMS User. Right-click the
node and choose Delete from the shortcut menu.
Method II Select a line of user information from the list on the right part of
the window, and then click Delete.
----End
Related Concepts
4.1.4 Northbound User
Related References
4.14.17 Parameters for Northbound User
Prerequisite
l The M2000 system is operational.
l The login user is authorized to add a new operator.
Procedure
Step 1 Choose Security > NMS.
The NMS User Management window is displayed.
Step 5 Set the parameters Operator, Operator Index, MCC, MNC, and Operator Type.
For detailed parameter description, refer to 4.14.18 Parameters for Operator.
----End
Related References
4.14.18 Parameters for Operator
Prerequisite
l The M2000 system is operational.
Procedure
Step 1 Choose Security > NMS.
Step 2 Click Add in the displayed NMS User Management dialog box.
Step 3 Click the icon in the displayed Add NMS User dialog box.
Step 4 In the Operator List dialog box, select the operator to be deleted, and then click Delete.
Step 5 In the displayed Confirm dialog box, click Yes.
NOTE
If NMS users are associated with the operator to be deleted, the Prompt dialog box is displayed, informing
you that the operator cannot be deleted. Thus, to delete the operator, you must delete the NMS users
associated with the operator and then perform the previous operations.
----End
Related References
4.14.18 Parameters for Operator
User operation logs falls into two categories: NM user operation logs and NE user operation
logs.
NM user operation logs records the information on the operations performed on the M2000 by
OM users.
NE user operation logs records the information on the operations performed by NE users.
A user session records the following information: login time, user group to which the user
belongs, the terminal to which the user logs in, and the current status. You get to know what
users have logged in to the system by monitoring the user session information. To ensure the
security of the system, you can also force some users to exit from the system.
Context
l The session is the connection between the M2000 client and the M2000 server.
l If a monitored user performs operations, the information in the operation monitoring list is
updated in real time.
l After the M2000 server is restarted or the network is recovered after interruption, you need
to click Refresh to refresh the session monitoring list.
Procedure
Step 1 Choose Security > User Monitor.
The Session Monitoring area box in the User Monitoring window displays the session
information about users. The information contains the user name, session status, login time,
login terminal, and user group to which the user belongs.
NOTE
When the machine of the client uses multiple network cards, the value of Login Terminal can be randomly
selected from the IP addresses.
----End
Related Concepts
4.13.1 User Operation Logs
4.13.2 User Sessions
Related References
4.14.6 Interface Description: Viewing Operations of OM Users on the M2000
Context
l This function supports only A NEs. B/C NEs are not supported.
l Only the users logging in to the LMTs (the LMT started through the M2000 and the
independently started LMT) are monitored. For the virtual NEs, the maintenance and
monitoring function is not provided.
l If a monitored user performs operations, the information in the operation monitoring list is
updated in real time.
l After the M2000 server is restarted or the network is recovered after interruption, you need
to click Refresh to refresh the session monitoring list.
Procedure
Step 1 Choose Security > User Monitor. The User Monitor window is displayed.
Step 2 Select the Local Maintenance Monitor tab, and then click Subscribe.
Step 3 In the displayed Subscribed NE List, select the NEs for the monitoring. Click OK.
NOTE
After you subscribe the NEs, the sessions and operations of the user on the LMT are displayed in the Local
Maintenance Monitor tab.
----End
Related Concepts
4.13.1 User Operation Logs
4.13.2 User Sessions
Related References
4.14.7 Interface Description: Viewing Operations of NE Users
Prerequisite
l The user has the relevant operation rights.
l The M2000 is connected to the LMT normally.
Procedure
Step 1 Click Security > Local Users Setting. The Local Users Setting window is displayed.
Step 2 Select an NE type under the NE Type node. All the NEs of this type are displayed at the right
window.
You can select multiple NEs in the list. Right-click the list, select an option in the shortcut menu, and then
the NEs are processed in batches.
----End
Context
l The system forces a user to exit only from the specific client in the session monitoring table.
If the user has logged in to the M2000 from multiple clients (if possible), you need to repeat
the operation to force the user to exit from all the clients.
l You cannot force your own user account to exit from the M2000.
Procedure
Step 1 Choose Security > User Monitor.
Step 2 From the session monitoring table, select a user name, and then click Force User to Exit.
----End
Procedure
Step 1 Choose Security > User Monitor, the User Monitor window is displayed.
Step 2 Click the Local Maintenance Monitor tab, and then choose the NE user in the NE session list.
Step 3 Click Force User to Exit or right-click and choose Force User to Exit from the shortcut menu.
----End
Prerequisite
Only the users who have the right to unlock the user can perform this operation.
Context
You can set the maximum login attempts and auto unlock time in the account policy.
Procedure
Step 1 Choose Security > Security Management .
Step 2 In the Security Management dialog box, expand the User root node. Right-click the user you
want to unlock, and then choose Unlock User.
----End
Procedure
Step 1 Choose Security > Security Policy. The Security Settings dialog box is displayed.
Step 2 Click the Account Policy node in the navigation tree. Then, enter the number of attempts in the
Maximum Login Attempts field and the automatic unlocking time in the Automatic Unlock
TIme (Minute) field.
By default:
l the value of Maximum Login Attempts is three.
l The value of Automatic Unlock TIme (Minute) is 30 minutes.
----End
the authority to an OM user and an OM user group. The M2000 consists of three default user
groups and one default user. The default user groups are Administrators, Guests, and
Operators. The default user is admin. The Administrators user group and user admin have
all the authorities.
Select User/User Group node from the navigation tree. The list of OM users or OM user groups
is displayed in the right pane. Select the specific user or user group node. The relevant
information such as the management domain and operation authority of a user or a user group
is displayed in the right pane. For details, refer to Figure 4-1.
(1) Root node.If you select this node, the right window displays the list
of NE types.
(2) Choose the node and view the NE type list in the right pane. NE type
node
No. Description
Related Concepts
4.1.3 NE User
Related Tasks
4.11.1 Creating an NE User
Related Tasks
4.11.4 Associating OM User with NE User
4.11.5 Disassociating OM User with NE User
Related Concepts
4.1.2 User Authority
Related Tasks
4.5.6 Granting MML Authority to an OM User Group
4.5.13 Grant MML authority to an OM user
4.6.3.4 Modifying the MML Authority to an OM User
4.6.2.4 Modifying the MML Authority to An OM User Group
dialog box. After you choose a user record in the User dialog box, the Command Group dialog
box displays the information about the command group associated with the user.
Related Tasks
4.4.3 Setting Authority Rules for NE Types
Related Concepts
4.13.1 User Operation Logs
4.13.2 User Sessions
Related Tasks
4.13.3 Viewing Operation of OM Users on the M2000
Related Concepts
4.13.1 User Operation Logs
4.13.2 User Sessions
Related Tasks
4.13.4 Viewing Operation of NE Users
Parameter Description
Name Description Operation
Related Tasks
4.5.2 Creating an OM User Group
Parameter Description
Parameter Description
Related Concepts
4.1.2 User Authority
Related Tasks
4.5.4 Assigning Operation Rights to an OM User Group
4.5.10 Assigning Operation Rights to an OM User
4.6.3.2 Modifying the Operation Rights of an OM User
4.6.2.2 Modifying the Operation Rights of an OM User Group
Parameter Description
Parameter Description
NE NE Type NE Type
NE IP IP address of an NE.
Related Concepts
4.1.2 User Authority
Related Tasks
4.5.6 Granting MML Authority to an OM User Group
Parameter Description
Parameter Description
Valid Time Time that the user can log in to. For example,
00:00:00-23:59:59 Thursday, Friday, Sunday
indicates that user login is permitted from
00:00:00 to 23:59:59 on each Thursday, Friday,
and Saturday.
Time Authorized to Change Password Time within which you can modify the user
account and password.
Password Expiry Time Time when the user account and password
expires.
User must change password next login l No: Do not change the password when the user
logs in next time.
l Yes: Change the password when the user logs
in next time.
Parameter Description
User can not change password l Yes: User cannot change the password through
the M2000 client.
l No: User can change the password through the
M2000 client.
Maximum password valid days Valid day for password: The system password is
valid within 180 days.
Recent Successful Login Time The latest time when the user successfully logs in
to the M2000
Recent Date for Changing Password The recent date when the user changes the
password
Login Status The M2000 login status comprises Not Login and
Login.
Related Tasks
4.6.4 Modifying the Information of an OM User
4.6.1 Viewing the Details of an OM User
Related Concepts
4.1.3 NE User
Related Tasks
4.11.1 Creating an NE User
Parameters
Name Description Settings
Related Tasks
4.5.7 Creating an OM User Account
Parameter Description
Parameter Value Range Description
Name Select the name from the drop- Refers to the name of the group.
down list. The name of a custom command
group is in M_digit format..
Related Tasks
4.4.2 Customizing an NE Command Group
Parameters
Name Description Settings
Related Tasks
4.3.1 Setting the M2000 Security Policy
4.3.1.1 Setting the Password Policy
4.3.1.2 Setting the Account Policy
4.3.1.3 Setting the System Policy
Parameter Description
CAUTION
The settings of Command Port and Data Port modify only the FTP port number when the
M2000 acts as the FTP client.
The settings of the parameters for FTP transfer strategy, except Command Port and Data
Port, are applicable only when the M2000 serves as the FTP client and the NE acts as the relay
server.
Related Concepts
4.1.5 Introduction to the FTPS
Related Tasks
4.3.4 Setting FTPS Parameters
Parameter Description
Parameter Value Range Description
User name A user name consists of a string The value of this parameter is
of 1 to 60 characters. If a unique and cannot be null. In
special character is included, it addition, the first character of a
can only an underscore. user name cannot be a numeral
or an underline.
Operator name Select from the drop-down list Name of the operator that the
northbound user belongs to.
If the name of the required
operator does not exist in the
drop-down list, click to
open the Operator List dialog
box. Then add the required
operator. For details of
parameter description, refer to
4.14.18 Parameters for
Operator.
Operator index By default, this parameter is set Unique index of the operator
by the system. that the northbound user
belongs to. You need set the
parameter when adding
information about an operator.
For details of parameter
description, refer to 4.14.18
Parameters for Operator.
Operator type By default, this parameter is set Type of the operator that the
by the system. northbound user belongs to,
indicating whether the operator
is host or partner. You need set
the parameter when adding
information about an operator.
For details of parameter
description, refer to 4.14.18
Parameters for Operator.
Related Concepts
4.1.4 Northbound User
Related Tasks
4.12 Managing Northbound Users
4.12.1 Creating a Northbound User
4.12.2 Modifying a Northbound User Password
4.12.3 Deleting a Northbound User
Parameter Description
Parameter Value Range Description
Related Tasks
4.12.4 Adding the Operator
4.12.5 Deleting the Operator
5 Log Management
Log management involves the management of user logs, NE logs, and system logs. This function
enables you to query logs and collect statistics of logs, thus helps monitoring and analyzing
operational status of the system and troubleshooting.
Log templates are categorized into querying templates and statistical templates.
l You can save all the querying or statistical settings of a specific type of logs into a template.
You can click Template Filter and choose Open to query the predefined query or statistics
template in the template list.
l The contents of the templates are saved in the database of the server, and they are available
only to their creators.
l Each type of log template created by a user must have a unique name.
l The name of a template contains a maximum of 40 characters, and special characters, such
as `~!@#$%^&*()|<>?,;':"[]{}, are not allowed.
l The system does not support automatic template refreshing. This means that if a user logs
in to client A and modifies/deletes template A, template A remains unaltered when the user
logs in to client B. You can close the template first, then open it again, and the system
refreshes the information of the template.
Figure 5-1 Process for reporting NE logs through the FTP server
3. The software management server reports the whole progress to the GUI for the first
time.
4. The software management server obtains the user name and password through the
FTP server and create a path for saving the created log files on the FTP server.
5. The software management server sends the uploading commands of log files to NEs.
After the NEs receive the commands, the NEs upload the log files to the FTP server
and report the uploading progress of the log files to the software management server.
6. The software management server reports the whole progress to the GUI for the second
time.
7. The software management server downloads the log files from the FTP server and
then reports the whole progress to the GUI for the third time.
8. The software management server resolves the log files to records and save the records
to the database.
9. The software management server reports the whole progress to the GUI for the fourth
time.
l Figure 5-2 shows the process for reporting NE logs rather other through the FTP server.
Figure 5-2 Process for reporting NE logs rather than through the FTP server
7. The software management server reports the whole progress to the GUI for the third
time.
Prerequisite
l You have logged in to the M2000 client.
l The NEs must not be virtual NEs and they must be connected to the M2000.
Context
Class B and class C NEs do not support NE log synchronization.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.
Step 2 On the topology view of the system, right-click the NE and select Synchronize NE Operation
and Security Logs on the shortcut menu.
The Software Browser window displays the information on the synchronizing task.
----End
The task is performed to set conditions for querying required operation logs, security logs, NE
logs, or system logs, and to save query results as files.
5.3.8 Printing Log Query Results
The task is performed to print query results of operation logs, security logs, NE logs, or system
logs.
Context
The log query templates consist of operation log query template, system log query template, and
security log query template. The procedures for creating these templates are similar. This section
takes how to create an operation log query template as an example.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs .
Step 3 In the Query Operation Log window, click Template Filter and select New.
Step 4 In the Enter The Template Name dialog box, define the name of the template, and then click
OK.
Step 5 In the Filter Condition window, set query conditions, and then click OK.
NOTE
If you want to modify the current query template, you can click Filter in the Query Operation Log window.
In the Filter Condition window, modify the query conditions in the template, and then click OK. Click
Template Filter, and then select Save to save the modified template, or select Save As to save the modified
template as a new one.
----End
Context
l If the query conditions are not set, all operation logs are queried.
l If you have no right to query operation logs, you can only query your own operation logs.
l If you want to print the query result, you need to install a printer.
l The query result is based on the existing data of the database. If the database is empty, the
query result is also empty.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs .
Step 2 In the Filter Condition window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query Operation Log window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to query logs.
l Click Filter. Set the query conditions and click OK to query logs.
l After selecting a record, press Shift and click another record so that you can select all the records
between the two records.
l After selecting a record, press Ctrl and click other records so that you can select multiple incontinuous
records.
----End
Related References
5.6.2 Parameters for Operation Log Details
5.6.14 Parameters for Querying Operation Logs
Context
l If the query conditions are not set, all system logs are queried.
l If you want to print the query result, you need to install a printer.
l The query result is based on the existing data of the database. If the database is empty, the
query result is also empty.
Procedure
Step 1 Choose System > Log Management > Query System Logs .
Step 2 In the Filter Condition window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query System Log window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to query logs.
l Click Filter. Set the query conditions and click OK to query logs.
l After selecting a record, press Shift and click another record so that you can select all the records
between the two records.
l After selecting a record, press Ctrl and click other records so that you can select multiple incontinuous
records.
----End
Related References
5.6.3 Parameters for System Log Details
5.6.15 Parameters for Querying System Logs
Context
l If the query conditions are not set, all security logs are queried.
l If you have no right to query security logs, you can only query your own security logs.
l If you want to print the query result, you need to install a printer.
l The query result is based on the existing data of the database. If the database is empty, the
query result is also empty.
Procedure
Step 1 Choose System > Log Management > Query Security Logs .
Step 2 In the Filter Condition window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query Security Log window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to query logs.
l Click Filter. Set the query conditions and click OK to query logs.
In the Query Security Log window, the query result is displayed.
l After selecting a record, press Shift and click another record so that you can select all the records
between the two records.
l After selecting a record, press Ctrl and click other records so that you can select multiple incontinuous
records.
----End
Related References
5.6.4 Parameters for Security Log Details
5.6.16 Parameters for Querying Security Logs
Context
l If no query condition is specified, all operation logs are queried by default.
l If you have no authority to query operation logs of other NEs, you can query only your
own operation logs.
l If you need print the query results, install the printer first.
l The displayed query results are not updated in real time. In this case, you need click Refresh
Filter.
l The query results are based on the existing data in the database. If no data is generated or
exported, no related information is displayed.
NOTE
Procedure
Step 1 Choose System > Log Management > Query NE Operation Log.
Step 2 In the Filter Condition dialog box, set the filtering conditions.
NOTE
You can click Cancel and use either of the following methods to filter the query in NE operation log
query.
l Click Template. Choose Open. Select a template in the list and click Open to use the existing template
to filter the query.
l Click Filter. Set the query conditions and click OK.
For descriptions of the related parameters, refer to 5.6.17 Parameters for Querying NE
Operation Logs.
In the NE operation log query dialog box, you can perform the following operations:
l Click Refresh to refresh the query results.
----End
Related References
5.6.5 Parameters for NE Operation Log Information
5.6.17 Parameters for Querying NE Operation Logs
5.6.17 Parameters for Querying NE Operation Logs
Context
l If no query condition is specified, all security logs are queried by default.
l If you have no authority to query security logs of other NEs, you can query only your own
security logs.
l If you need print the query results, install the printer first.
l The displayed query results are not updated in real time. In this case, you need click Refresh
Filter.
l The query results are based on the existing data in the database. If no data is generated or
exported, no related information is displayed.
NOTE
Procedure
Step 1 Choose System > Log Management > Query NE Security Log.
Step 2 In the Filter Condition dialog box, set the filtering conditions.
NOTE
You can click Cancel and use either of the following methods to filter the query in NE security log
query.
l Click Template. Choose Open. Select a template in the list and click Open to use the existing template
to filter the query.
l Click Filter. Set the query conditions and click OK.
For descriptions of the related parameters, refer to 5.6.18 Parameters for Querying NE
Security Logs.
Step 3 Click OK.
You can view the query results in NE security log query. For descriptions of the parameters
related to operation logs, refer to 5.6.6 Parameters for NE Security Log Information.
NOTE
In the NE security log query dialog box, you can perform the following operations:
l Click Refresh to refresh the query results.
l Click Print to print the query results.
l Click Save As to save the query results to the local computer.
----End
Related References
5.6.6 Parameters for NE Security Log Information
5.6.18 Parameters for Querying NE Security Logs
5.6.18 Parameters for Querying NE Security Logs
Prerequisite
The required NE log, operation log, security log, or system log is queried.
Context
l By default, the files are saved in the installation directory. The first log record in the log
file corresponds to the first record of the queried result, and the last log record corresponds
to the last result record.
Procedure
Step 1 In the log query window, click Save As.
Step 2 In the displayed Save dialog box, enter the name of the log file and select the file type.
Step 3 Click Save.
The displayed Save dialog box shows the saving progress. You can click Cancel to cancel the
operation.
----End
Prerequisite
The required NE log, operation log, security log, or system log is queried.
Procedure
Step 1 In the log query window, click Print.
Step 2 In the displayed Print dialog box, set the related parameters and then click Print.
For descriptions of related parameters, refer to 3.9.14 Parameters for Printing a Topology
View.
----End
Context
When you collect statistics on logs, you need to set statistical conditions. Statistical conditions
can be set by creating a statistical template or setting statistical conditions in real time.
Procedure
Step 1 Choose System > Log Management > Statistic Operation Logs.
Step 3 In the Statistic Operation Log window, click Template Filter and select New.
Step 4 In the Enter The Template Name dialog box, define the name of the template, and then click
OK.
Step 5 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
If you want to modify the current statistics template, you can click Statistic Filter in the Statistic Operation
Log window. In the Filter Condition window, modify the statistical conditions in the template, and then click
OK. Click Template Filter, and then select Save to save the modifications, or select Save As to save the
modified template as a new one.
----End
Context
l If a statistical item has no options, this statistical item is invalid.
l If you want to print the statistical result, you need to install a printer.
l The statistical result is based on the existing data of the database. If the database is empty,
the statistical result is also empty.
Procedure
Step 1 Choose System > Log Management > Statistic Operation Logs.
Step 2 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Statistic Operation Log window in the following
ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to collect statistics on operation logs.
l Click Statistic Filter. Set Statistic Items and Filter Condition, and then click OK to collect statistics on
operation logs.
In the Statistic Operation Log window, the statistical result is displayed.
----End
Related References
5.6.7 Parameters for Operation Log Statistics
Context
l If a statistical item has no options, this statistical item is invalid.
l If you want to print the statistical result, you need to install a printer.
l The statistical result is based on the existing data of the database. If the database is empty,
the statistical result is also empty.
Procedure
Step 1 Choose System > Log Management > Statistic System Logs .
Step 2 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Statistic System Log window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to collect statistics on system logs.
l Click Statistic Filter. Set Statistic Items and Filter Condition, and then click OK to collect statistics on
system logs.
In the Statistic System Log window, the statistical result is displayed.
l In the Statistic System Log window, click Save As to save the statistical result.
----End
Related References
5.6.9 Parameters for System Log Statistics
Context
l If a statistical item has no options, this statistical item is invalid.
l If you want to print the statistical result, you need to install a printer.
l The statistical result is based on the existing data of the database. If the database is empty,
the statistical result is also empty.
Procedure
Step 1 Choose System > Log Management > Statistic Security Logs.
Step 2 In the Filter Condition window, set Statistic Items and Filter Condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Statistic Security Log window in the following
ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to collect statistics on security logs.
l Click Statistic Filter. Set Statistic Items and Filter Condition, and then click OK to collect statistics on
security logs.
In the Statistic Security Log window, the statistical result is displayed.
----End
Related References
5.6.8 Parameters for Security Log Statistics
Context
l If a statistical item has no options, this statistical item is invalid.
l If you need print the query results, install the printer first.
l The statistical result is based on the existing data of the database. If no data is generated or
exported, no related information is displayed.
l This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC
Server, MGW, HLR9820, CG, PCU, BSC6000, IP Clock Server, and AG.
Procedure
Step 1 Choose System > Log Management and select the logs to collect the statistics.
Step 2 In the Filter Condition dialog box, set Statistical Items and Filter Condition.
NOTE
You can click Cancel and use either of the following methods to filter the statistics of NE logs.
l Click Template. Choose Open. Select a template in the list and click Open to use the existing template
to collect statistics of NE logs..
l Click Statistic Filter. Set Statistical Items and Filter Condition, and then click OK to collect statistics
of NE logs.
For information about statistical items of NE operation logs and security logs, refer to 5.6.10
Parameters for Statistics of an NE Operation Log and 5.6.12 Parameters for Statistics of
an NE Security Log respectively. For descriptions of filtering conditions, refer to 5.6.11
Parameters for Filter Condition of NE Operation Log Statistics and 5.6.13 Parameters for
Filter Condition of NE Security Log Statistics.
Step 3 Click OK.
Then you can view the statistical results in the log statistics window.
NOTE
In the log statistics dialog box, you can perform the following operations:
l Click Print to print the statistical results.
l Click Save As to save the statistical results to the local computer.
----End
Related References
5.6.10 Parameters for Statistics of an NE Operation Log
5.6.11 Parameters for Filter Condition of NE Operation Log Statistics
5.6.12 Parameters for Statistics of an NE Security Log
5.6.13 Parameters for Filter Condition of NE Security Log Statistics
Related Concepts
5.1.2 Log Templates
Prerequisite
l You have logged in to the M2000 client.
l You have the privilege for log management.
Context
You need to set conditions for log query and log statistics collect before you perform these
operations. Two ways are available for setting conditions for log query or log statistics collection.
They are creating query or statistics template, and setting query or statistics conditions in real
time.
The templates of the following logs are created in the same way:
l Operation logs
l System logs
l Security logs
l NE operation logs
l NE security logs
Procedure
Step 1 Choose System > Log Management.
Step 2 In the displayed Filter Condition dialog box, click Cancel.
Step 3 Click Template Filter, and then select New from the drop-down list.
Step 4 Enter the name of the template. Click OK.
l The template name contains a maximum of 40 characters and cannot contain the following
characters: `~!@#$%^&*()\":;?,|{}[]<>, or '
l For each user, the template name for each type of logs must be unique .
Step 5 In the displayed Filter Condition condition, set filter conditions for log query or log statistics
collection.
Different type of logs have different filter conditions. You can set filter conditions based on
actual requirements.
Step 6 Click OK.
----End
Result
The results of log query or log statistics collection are displayed in the log window. The system
displays the new log templates in the following ways:
l Click Template Filter in the log window. The list displays the name of the new log
template.
l Click Template Filter in the log window. Select Open from the drop-down list. The name
of the new log template is displayed in the list.
Related Concepts
5.1.2 Log Templates
Prerequisite
l You have logged in to the M2000 client.
l You have the privilege for log management.
Context
You can modify the following logs by using the same method:
l Operation logs
l System logs
l Security logs
l NE operation logs
l NE security logs
Procedure
Step 1 Choose System > Log Management and select the log whose template is to be modified.
Step 2 In the displayed Filter Condition dialog box, click Cancel.
Step 3 Click Template Filter, and then select Open from the drop-down list.
Step 4 In the displayed Open dialog box, select the log template to be modified. Click Open.
The results of log query or log statistics collection are displayed in the log window.
Step 5 Click Filter.
Step 6 In the displayed Filter Condition dialog box, modify the filter conditions of log query or log
statistics collection. Then, click OK.
Step 7 Click Template Filter, and then select Save As from the drop-down list.
----End
Prerequisite
l You have logged in to the M2000 client.
l You have the privilege for log management.
Context
You can delete the following logs by using the same method:
l Operation log
l System log
l Security log
l NE operation log
l NE security log
Procedure
Step 1 Choose System > Log Management and select the log whose template is to be deleted.
Step 2 In the displayed Filter Condition dialog box, click Cancel.
Step 3 Click Template Filter, and then select Delete from the drop-down list.
Step 4 In the displayed Delete dialog box, select the log template to be deleted. Click Delete.
Step 5 In the Confirmation dialog box, click Yes.
The template deleted is also removed from the template list in the Delete dialog box.
Step 6 Click Cancel. The Delete dialog box is closed.
----End
The interfaces for the query or statistics collection of different types of logs are similar. For
details about the interfaces for log query or log statistics collection, refer to Figure 5-3. After
the filter conditions are set, the results of log query or log statistics collection are displayed in
the log window. You can save or print the results by clicking the buttons on the interface.
Parameters
Name Description
Operation Description:
Name of user operations, such as add, delete, and browse.
User Description:
Name of the user who performs the operation.
Name Description
Category Description:
To identify different types of operations, such as log, topology, and
remote notification.
Terminal Description:
To identify clients in IP addresses.
Result Description:
To indicate whether the operation is successful, including
Succeeded, Failed, Canceled, Partly succeeded, and
Uncompleted.
Partly succeeded means the operation is complete, and some
operation results are returned. Uncompleted means the operation is
being carried out, the result is not returned.
Details Description:
Details of operation logs.
Related Tasks
5.3.2 Querying Operation Logs
Parameters
Name Description
Level Description:
There are three levels for system logs: Error, Warning, and Info.
Name Description
Source Description:
The log IDs of the subsystems of the M2000 are alarm management,
system management, and security management.
Time Description:
The date and time when the system log is recorded. The format is
consistent with that in region settings, such as YYYY-MM-DD
hh:mm:ss.
Basic Description:
Information The basic information of system logs. For example: start service.
Details Description:
Details of system logs.
Related Tasks
5.3.3 Querying System Logs
Parameters
Name Description
User Description:
Name of the user who performs the operation.
Name Description
Terminal Description:
To identify clients in IP addresses.
NOTE
During the initialization of the M2000 server installation, the terminal IP
address corresponding to the operations performed by using scripts or
commands is 1.1.1.1 displayed in security logs.
Result Description:
To indicate whether the operation is successful, including
Succeeded, Failed, Canceled, Partly succeeded, and Ongoing.
Partly succeeded means the operation is complete, and some
operation results are returned. Uncompleted means the operation is
being carried out, the result is not returned.
Details Description:
Details of security logs.
Related Tasks
5.3.4 Querying Security Logs
User Type Domain attribute of the user, such as EMS, Local, and EMSOP
Parameter Description
Related Tasks
5.3.5 Querying NE Operation Logs
For details of the parameters related to NE security logs, refer to Table 5-2.
Parameter Description
User Type Domain attribute of the user, such as EMS, Local, and EMSOP.
Related Tasks
5.3.6 Querying Security Logs of the NEs
Statistical items
Name Description Settings
Filter condition
Name Description Settings
Related Tasks
5.4.2 Collecting Statistics on Operation Logs
Statistical items
Name Description Settings
Filter condition
Name Description Settings
Related Tasks
5.4.4 Collecting Statistics on Security Logs
Statistical items
Name Description Settings
Filter condition
Name Description Settings
Related Tasks
5.4.3 Collecting Statistics on System Logs
Parameter Description
Parameter Description
Result Result of the operation. There are two types: succeeded and failed.
User Type Identifies the domain attribute of the user in the NE operation log,
including EMS, Local and SMSOP.
Related Tasks
5.4.5 Taking Statistics of an NE Log
Parameter Description
Filter Description Setting
Condition
User Types Collects statistics by user type Select one or more items from the
The user type falls into the Local, the User Type group box.
EMS, and the EMSOP categories.
Time Range Collects statistics by time range Select From and To, and enter the
From indicates the start time, while date and time in the text box.
To indicates the end time. Alternatively, click . In the Date/
Time Selection dialog box, set the
date and the time.
For instance, set the time range to
2002-02-09 00:00:00 2003-02-09
00:00:00.
Related Tasks
5.4.5 Taking Statistics of an NE Log
Parameter Description
Parameter Description
Result Result of the operation. There are two types: succeeded and failed.
User Type Identifies the domain attribute of the user in the NE security log,
including EMS, Local and EMSOP.
Security Level Specifies the level of security events to query. There are three
types: critical, major, and minor.
Related Tasks
5.4.5 Taking Statistics of an NE Log
Parameter Description
Filter Description Setting
Condition
User Types Queries by user type Select one or more items from the
The user type falls into the Local, the User Types group box.
EMS, and the EMSOP categories.
Result Collects statistics by operation Select one or more items from the
results. Result group box.
The results are either Succeeded or
Failed.
Security Collects statistics by security level Select one or more items from the
Levels The security levels are Urgent, Security Levels group box.
Important, and Subordinate.
Time Range Collecting statistics by time range Select From and To, and enter the
From indicates the start time, while date and time in the text box.
To indicates the end time. Alternatively, click . In the Date/
Time Selection dialog box, set the
date and the time.
For instance, set the time range to
2002-02-09 00:00:00 2003-02-09
00:00:00.
Related Tasks
5.4.5 Taking Statistics of an NE Log
Parameters
Name Description Settings
Related Tasks
5.3.2 Querying Operation Logs
Parameters
Name Description Settings
Related Tasks
5.3.3 Querying System Logs
Parameters
Name Description Settings
Related Tasks
5.3.4 Querying Security Logs
For details of the parameters related to querying NE operation logs, refer to Table 5-3.
User Types Queries by user type Select one or more items from the
The user type falls into the Local, the User Types group box.
EMS, and the EMSOP categories.
Result Queries by operation results. Select one or more items from the
The results are either Succeeded or Result group box.
Failed.
Time Range Queries by time range Select From and To, and enter the
From indicates the start time, while date and time in the text box.
To indicates the end time. Alternatively, click . In the Date/
Time Selection dialog box, set the
date and the time.
For instance, set the time range to
2002-02-09 00:00:00 2003-02-09
00:00:00.
Related Tasks
5.3.5 Querying NE Operation Logs
5.3.5 Querying NE Operation Logs
For details of the parameters related to querying NE security logs, refer to Table 5-4.
User Types Queries by user type Select one or more items from the
The user type falls into the Local, the User Types group box.
EMS, and the EMSOP categories.
Result Queries by operation results. Select one or more items from the
The results are either Succeeded or Result group box.
Failed.
Security Collects statistics by security level Select one or more items from the
Levels The security levels are Urgent, Security Levels group box.
Important, and Subordinate.
Time Range Collecting statistics by time range Select From and To, and enter the
From indicates the start time, while date and time in the text box.
To indicates the end time. Alternatively, click . In the Date/
Time Selection dialog box, set the
date and the time.
For instance, set the time range to
2002-02-09 00:00:00 2003-02-09
00:00:00.
Related Tasks
5.3.6 Querying Security Logs of the NEs
5.3.6 Querying Security Logs of the NEs
6 Performance Management
Through the performance measurement, you can measure and observe the security, the running
status and the signaling connection status of the equipment, also you can measure and observe
the utilization of the user and system resources. This function provides reliable data support for
the measurement, designing and operation management of the communication
network.M2000The M2000 can measure the performance of multiple NEs. When an NE is
successfully set up and communicates normally with the M2000, the NE automatically reports
the measurement results of key performance counters to M2000 for data query and analysis
based on a certain period.
Context
IMSOMU, CCF, SBC, MRF, IWF, IP Clock Server, and AHR do not support performance
management.
6.1 Basic Knowledge of Performance Management
This topic describes the basic knowledge of performance management. Before you perform the
related operations, you need know some basic knowledge about the performance, such as
measurement counters, measurement objects, function sets and function subsets, measurement
periods, counter thresholds, measurement status and measurement processes.
6.2 Monitoring NE Performances
You can set NE performance measurement range and query performance measurement results.
In addition, you can synchronize and subscribe to NE measurement results, query missing
measurement results, and manage NE measurement states.
6.3 Querying Performance Measurement Results
This task is performed to query performance measurement results. Two query modes, that is, by
template and by new conditions, are available.
6.4 Managing Measurement Objects
Through measurement object management, you can search for counters and objects. You can
also export and import measurement settings information.
6.5 Managing User-Defined Counters
The user-defined counter management involves two types of counters: system counters and user-
defined counters. The system counter is obtained when the system performs the arithmetic
operation on the original counters in the system by default. It is attached to the system. When
the M2000 is running, you can perform a arithmetic operation on the original system counters
to obtain a new measurement counter. The counter generated in this way is called the user-
defined counter. The user-defined counters apply only to the periodic measurement results. A
user-defined counter is measured only when all the original counters contained in the formula
are measured. If an original counter is not measured, the user-defined counter cannot be
measured.
6.6 Managing Counter Thresholds
During different periodic measurement, the M2000 provides the counter value threshold alarm
to automatically monitor key performance counters and currently measured extension counters.
You can set the alarm threshold of every periodic measurement based on actual situations
including setting the simple alarm threshold for a single counter and for the combined counters
after logic or arithmetic operations.
6.7 Collecting Neighbor Cell Optimization Data
The M2000 provides the function of collecting neighbor cell optimization data. Through the
M2000 client, you can issue MML commands to inform a cell of sending system messages to
the mobile phones within the cell, performing neighbor cell measurement tasks, and reporting
the measurement results to the M2000. According to the measurement results of the related
frequencies, the M2000 determines the frequencies of the cells that can serve as the neighbor
cell. In this way, the users can switch to a suitable neighbor cell if the performance of the original
cell is degraded. Thus, the normal usage is not affected. This function is used to find the list of
appropriate neighbor cells during creation, optimize the neighbor relations of existing networks,
and evaluate the optimal location of a micro cell.
6.8 Reference for Performance Management Interfaces
This part describes the following interfaces of performance management: query result interface,
measure management interface, threshold management interface, customer counter interface,
and Performance Monitor interface.
Category
Based on the source, measurement counters fall into the following two categories:
l The default counters, also called system counters, are defined by NEs. The NE periodically
reports the measurement results of all default performance counters to the M2000. The
default performance counters consist of common counters and extended counters.
Common Counter
Common counters refer to the key counters defined for an NE. The NE periodically reports the
measurement results of all these counters to the M2000, and the M2000 saves the results to the
performance database for future queries.
Extended Counter
Extended counters are also counters defined for an NE. The NE reports the results of the selected
extended counters to the M2000.The M2000 determines whether to save the result to the
M2000 performance database based on the user selection.
During the operation of the M2000, you can select or deselet the extended counters.
l When you select an extended counter, the measurement results of the extended counter are
saved to the M2000 performance database for future queries.
l When you clear an extended counter, the M2000 does not save the measurement results of
the extended counter to the performance database.
User-Defined Counter
User-defined counters refer to those defined on the M2000 client. The system defines the user
defined counters by adding, subtracting, multiplying, and dividing the system default counters
(both common counters and extended counters).
You can add, modify, or delete the user-defined counter during the M2000 operation.
User-defined counters can be measured and can also be nested to create other user-defined
counters.
l For the first type, you do not need to specify manually the measurement object. The system
measures all objects of a certain type by default. The NE reports all the obtained
measurement results of all objects of this type to the M2000. Therefore, you do not need
to add these objects manually to the measurement range. You can choose not to measure
them.
l For the second type, you need to specify the measurement object. After you add this type
of measurement objects manually to the measurement range, the NE notifies the M2000 of
the addition, and the M2000 displays these objects in the Measurement Object Management
window.
l For the third type, you need to enter the specific characteristics of the object, because the
measurement is based on these characteristics.M2000The M2000 adds this type of objects
and notifies the NE, and the NE reports the corresponding measurement results to the
M2000. The object of the third type is displayed by icon on the M2000 client interface.
These counters are divided into three levels, as shown in Figure 6-1.
l Level 1 is the function set. A function set consists of function subsets related to a certain
system function. Function sets are also called measurement sets.
l Level 2 is the function subset. A function subset consists of measurement counters related
to a certain system function. Function subsets are also called measurement units.
l Level 3 is the measurement counter.
There is a certain correspondence between the measurement object and the measurement
counter. To make it more specific, different measurement objects have different measurement
counters. One measurement counter applies only to one type of measurement object.
Measurement counters are classified into different measurement function sets. One measurement
function set is divided into multiple measurement units. One measurement unit corresponds to
one type of measurement objects. One measure object can correspond to multiple measurement
units. These measurement units can belong to different measurement function sets.
A measurement period refers to the interval for NEs to report performance measurement results.
NEs report measurement results to the M2000 periodically. The M2000 analyzes the results and
then saves the results to the database for future queries. 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.
from this Monday should be the 10 Mondays in the last 10 weeks. Currently the workday and
non-workday sequence is adopted, that is, the empirical value is calculated from the result values
of the same time point in the last 10 workdays.
To monitor performance counters, you can set thresholds for counters to monitor changes of the
counters. A relevant threshold alarm is generated when the offset of a counter value exceeds the
threshold for three times consecutively. The generated threshold alarm is cleared when the offset
of the counter value remains below the threshold for three consecutive times.
You can monitor in real time counter thresholds. Then you can set counters, threshold sizes, and
triggered threshold alarm levels during the threshold management.
Context
l When you set to measure user-defined counters, the related original counters instead of
nested user-defined counters are set to be measured.
l When you cancel the measurement of user-defined counters, the measurement of the user-
defined counter instead of the related original counters are canceled.
l If a user-defined counter is being measured, the invoked original counter cannot be
canceled.
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
Step 3 Select a function set and subset in the Measurement Settings tab. Check the objects and counters
to be measured.
NOTE
When you set measurement objects, All Measurement Object and Selected Ne Measurement Object
dynamically collect the statistics of objects that are set to measure.
Fuzzy search is supported. You can enter a character, letter, or number in the Filter Search text box. Then,
the system filters out the object types and function subsets that do not contain the typed string. In this way,
you can easily located the object type or function subset.
If you select All when setting measurement objects, then all the objects of the NE are selected. If the NE
has no object, then the system automatically issues measurement tasks when adding performance objects.
In this way, new performance objects can be measured automatically.
----End
Related Concepts
6.1.1 Performance Measurement Counters
6.1.2 Performance Measurement Objects
Procedure
Step 1 Choose Performance > Measure Management to view the Measure Management window,
----End
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
Step 4 Right-click in the measurement object list and choose Edit Object on the shortcut menu.
Step 5 Click Export Editing Template or right-click the list and choose Export Editing Template
on the shortcut menu. The Save dialog box is displayed.
Step 6 Select the save path and enter the file name.
By default, the file name is the name of the current type 3 object.
----End
Context
The file must conform to a certain format. You can edit the template by using the exported
objects.
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
Step 4 Right-click in the measurement object list and choose Edit Object on the shortcut menu.
Step 5 Click Import Objects or right-click the list and choose Import Objects to open the Open
dialog box.
----End
Context
CSCF, HSS, ATS, RM and DOPRA do not support this function.
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
Step 2 Right-click a node on the navigation tree and choose Synchronize Result, or click the icon
----End
Related References
6.8.11 Parameters for Synchronizing NE Measurement Results
Context
Each GUI can open one result subscription window. You can subscribe to the measurement
results of only one NE and one function subsets in each subscription window.
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
Step 2 On the navigation tree, right-click a node and choose Subscribe Result from the shortcut menu,
Step 3 Set the parameters in the Measurement Period and Range areas.
NOTE
You can set the performance measurement results of multiple NEs, multiple periods, and one function
subset of the same NE type at a time.
----End
Procedure
Step 1 Choose Performance > Query Result, or click to view the Query Result window.
Step 2 Right-click the measurement result table and choose Reliability on the shortcut menu.
Then you can view the reliability in the displayed dialog box. Click Yes to the view the detailed
information.
----End
Related References
6.8.8 Parameters for Querying the Reliability of Measurement Results
Procedure
l Customize query conditions to query missing measurement results.
shortcut menu. Or you can click the icon to open the Query Missing Result
dialog box.
3. Set the parameters.
The default end time is the current time. The default start time is the result of
subtracting the missing result time range in the preference setting from the current
time.
4. Click OK.
If missing measurement result exists in the time segment, the missing results are listed
in the displayed dialog box. The first column displays the object information, and the
second displays the time segment.
l Query missing measurement results based on the template.
1. Choose Performance > Query Result, or click . The Query Result window is
displayed.
2. Double-click a template in the navigation tree.
3. Click Lost Result. Alternatively, right-click in the right pane and choose Lost
Result from the shortcut menu. The Query Missing Result dialog box is displayed.
4. You can query the missing measurement results by using any of the following
methods:
– Query the missing results by using one of the following methods: In function
subset list, select the function subset to be queried and then press the enter key.
– In function subset list, double-click the function subset to be queried.
– In function subset list, select the function subset to be queried and click Query.
Alternatively, right-click the function subset and choose Query from the shortcut
menu.
– If the measurement results of this function subset are missing, the right pane in the
Query Missing Result dialog box displayed the object information and related time
segment.
– If the measurement results of this function subset are not missing, the system displays
a dialog box showing that the results are not missing.
----End
Related References
6.8.7 Parameters for Querying Missing Measurement Results
Context
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. The number of results to be reported refers
to the number of valid measurement objects in a measurement period. Valid measurement objects
refer to the NE objects that are to be measured and not suspended.
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
Step 2 Click , and select Integrity Monitor to view the Condition setting for integrity
monitor dialog box.
Step 3 Select the measurement period, NE, and function subset.
A maximum of 5 measurement periods, 10 NEs, and 10 function subsets are allowed.
Step 4 Click OK.
l The Integrity Monitor dialog box is displayed. Each tab shows the result of monitoring the
integrity of one period.
l The tab is named in the format: Measurement period (start time of the period). For example,
if the current time is 15:24, the tab name is 5 Minutes (15:15-15:20), 15 Minutes
(15:00-15:15). The monitoring results are updated dynamically with the time. The tab for
period of 5 minutes changes its name to 5 Minutes (15:20-15:25) when the current time is
15:30.
----End
Postrequisite
In the monitoring results, the intersecting cell of the NE column and function subset row is an
available cell. Other cells are sum cells. You can click the available cell to activate the dimmed
button, where
l Each available cell records the number of performance results that are actually reported,
the number of performance results that should be reported, and the ratio of the previous
two numbers for the corresponding function subset.
l The sum cell under each NE records the number of performance results that are actually
reported, the number of performance results that should be reported, and the ratio of the
previous two numbers for all the corresponding function subset.
l The sum cell of each function subset records the number of performance results that are
actually reported, the number of performance results that should be reported, and the ratio
of the previous two numbers for all the NEs of the corresponding function subset.
l The sum cell at the right corner records the total number of sum cells of all NEs, that is,
the sum of the sum cells of all function subsets.
You can select a cell in the Integrity Monitor window and perform Synchronize Result and
Query Result.
Context
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. The number of results to be reported refers
to the number of valid measurement objects in a measurement period. Valid measurement objects
refer to the NE objects that you have set to measure and are not suspended.
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
Step 2 Click , and select Integrity Query to view the Condition setting for Integrity Query
dialog box.
----End
Postrequisite
You can select a cell in the Integrity Query window and perform Synchronize Result , Query
Result, and Query Missing Result.
Related Concepts
6.1.7 Performance Measurement States
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
Step 2 Choose an NE type on the navigation tree. Then you can view the measurement states in
Measurement Status in the right pane.
----End
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
Step 3 Right-click the measurement status table and choose Export Status on the shortcut menu.
Step 4 Select the save path and file type. Enter the file name.
The file can be in TXT, HTML, CSV, or XLS format.
----End
You can query on the M2000 client all the measurement results reported after the NE is created.
Before querying the results, set the query conditions, including the concerned counters and
objects and the time segment.
6.3.3 Query Results by Busy Hour
The M2000 enables you to query performance measurement results by busy hour.
6.3.4 Re-querying Results
After you re-query or query in real time the results, you can reset query conditions and then re-
query results.
6.3.5 Setting Result Query Conditions
You can set result query conditions to query measurement results. The conditions include the
measurement function set/subset, object range, counter range, time range, measurement period,
sequence mode, and filter condition.
6.3.6 Displaying Performance Measurement Results
Measurement results can be displayed in a table or a line or bar chart. You can set the counter
color and the background color for performance result charts to enhance the visual effect.
6.3.7 Saving Performance Measurement Results
You save the performance measurement results to a file.
6.3.8 Printing Performance Measurement Results
You can print the queried measurement results.
6.3.9 Managing Result Query Templates
The condition template provides a group of condition parameters used for querying measurement
results. It saves the common used data. The templates comprises the system default template
and user-defined template. You cannot modify the query conditions set on the system template.
You also cannot delete the system template. You can create, modify, query, and copy the defined
template. In addition, you can set a directory for the defined template.
Related Concepts
6.1.5 Performance Measurement Results
Related References
6.8.1 Interface Description: Query Result
Procedure
Step 2 In the template tree on the left part of Query Result, select a template.
Step 3 Right-click the template and choose Query Result > Default from the shortcut menu.
Alternatively, double-click the selected template.
The query results are displayed on a new tab page. The tabs are name in the format of Template
Name(Current Time). For example, all(25/12/2007 17:16).
Select Default . Then the selected Date range when you create the template is the date range
for querying the measurement results. You can change the date range for querying measurement
results as required. For details, refer to Table 6-1.
Menu Description
This week To query the measurement results of this week for some counters
under the selected objects based on the query template.
Last week To query the measurement results of last week for some counters
under the selected objects based on the query template.
All time To query all the measurement results for some counters under the
selected objects based on the query template.
For example, the measurement results of some counters under an
object can be stored in the database for 30 days. After you select
this option, you can view all the measurement results for the
selected counter in the 30 days.
Specific After you set Start Time and End Time, the system queries the
measurement results for some counters under the selected object
at the specific time based on the query template.
----End
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query, or select the Custom node or a template under this node and right-click to
select New Query to display Query Result window.
Step 3 On the Object Settings, Counter Settings, and Other Settings tab pages, set the query
conditions for the measurement results.
----End
Context
l The busy hour refers to the hour when the counter value is the greatest.
l The period for collecting statistics of busy hour is set to 60 minutes. If the NE does not
support 60-minute period, the results are summarized every 30 minutes. If the NE support
neither 60-minute period nor 30-minute period, the 15-minute period is adopted. If the 15-
minute period is not supported, the statistics are not collected.
l You can not perform busy hour query of the day.
l You can perform busy hour query only when busy hour counters of the select NE type exist.
Busy hour counters are defined by NEs.
l You cannot query the missing results by this query mode.
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query. Alternatively, right-click a directory in the navigation tree and choose New
Query from the shortcut menu. The New Query dialog box is displayed.
Step 3 Select a function subset on the navigation tree in the left pane.
Step 4 Select the measurement object on the Object Settings tab and measurement counters in the
Counter Settings tab.
Step 5 On the Other Settings tab, select Busy Time under Time Mode.
When multiple busy hour counters exist in the same function subset, you can select only one
busy hour counter to query results.
Step 6 Click Query.
The queried measurement results are displayed in the Query Result window in the form of
tables, line charts, and histograms.
----End
Prerequisite
You have queried the results for once.
Procedure
Step 1 In Query Result, click Condition.
In the displayed Condition Information window, objects and counters are already set in the
previous time. You need not reset the objects and counters. You need reset query conditions in
Other Setting. The objects and counters can be reset.
----End
Procedure
Step 2 Click New Query. Alternatively, right-click a directory on the navigation tree and choose New
Query to open the Query Result dialog box.
Step 3 Select a measurement function subset on the navigation tree in the left part of the window.
----End
Related Concepts
6.1.3 Measurement Function Sets and Subsets
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query, or select the Custom node or a template under this node and right-click to
select New Query to display the Query Result.
Step 3 Select a node in the navigation tree in the left of the window.
----End
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query. Alternatively, right-click a directory in the navigation tree and choose New
Query from the shortcut menu. The New Query dialog box is displayed.
Step 3 Select a node in the navigation tree in the left part of the window.
NOTE
l M2000Note that the counter selection for different function subsets has restrictions. You can select
counters for a maximum of N function subsets, where N is smaller than 3.
l The number of selected counters that are already set to be measured cannot exceed 128. The system
prompts users of the number of selected counters.
l On the M2000, the number of user-defined counters that can be selected is limited. The number of
user-defined counters that can be selected is smaller than 50.
l The counters that are not set to be measured display in grey. The system will not respond to the query
of these counters.
l You can query measurement results of user-defined counters.
l Provide the function of querying by name. You can type the name of a counter to be queried. The
system displays the mapping counter.
l The system displays the mapping object. The system can display the counters of All, Set, and No
Set.
----End
Related Concepts
6.1.6 Performance Counter Thresholds
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query, or select theCustom node or a template under this node and right-click to
select New Query to display Query Result.
Step 3 Select a node in the navigation tree in the left part of the window.
Step 4 Set the time range and mode of the query in Other Settings.
----End
Related References
6.8.6 Parameters for Setting the Conditions for Filtering Result
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query, or select theCustom node or a template under this node and right-click to
select New Query to display the Query Result.
Step 3 Select a node in the navigation tree in the left part of the window.
----End
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 Click New Query, or select the Custom node or a template under this node and right-click to
select New Query to display Query Result.
Step 3 Select a node in the navigation tree in the left part of the window.
Step 4 Set the sequence mode in the Sort box in Other Settings.
l The sorting has five priorities. They are the major, minor, third, fourth and fifth respectively
from high to low.
l The sequence can be organized in an ascending order or a descending order.
l When you set different keywords for various sorting priorities, the M2000 sorts and displays
the queried measurement results according to the keyword priority.
l You are not allowed to set two or more same key words for sequencing.
l The key words used for sequencing must have precedence over those not for sequencing.
----End
Related References
6.8.9 Parameters for Setting the Mode of Sorting Displayed Results
Context
l You can set a maximum of 200 filter conditions.
l The logical operators between multiple filter conditions define the logical relationship. If
the counter value of a is greater than 3 and the counter value of b is greater than 2, or counter
value of c is smaller than 1, the results are displayed. Therefore, the logical relation is a >
3 and b > 2 or c < 1 none.
NOTE
The logical operator of the filter conditions must be none. The parameters before the logical operator
is allowed to be none.
Procedure
Operation Procedure
Add an filter condition. Select the counter filter condition and click Add.
Modify an filter condition. 1. Select an existing filter condition in the list and click
Modify.
2. Click Yes in the displayed Confirm dialog box.
Delete a filter condition. 1. Select an existing filter condition in the list and click
Delete.
2. Click Yes in the displayed Confirm dialog box.
----End
Related References
6.8.6 Parameters for Setting the Conditions for Filtering Result
When the M2000 displays the performance results in a line chart or bar chart, you can set the
background color of the chart.
Prerequisite
The existing measurement results are displayed on the Query Result tab of the Query Result
window.
Context
l Measurement results can be displayed in a table, a line chart, or a bar chart. The system
takes the table form by default.
l When the results are displayed in a table, you can print measurement results and save job
results into a file.
l You can right-click the table heading and choose More to open the Customize dialog
box, where you can customize the column.
Procedure
Under View Type, click Table.
----End
Postrequisite
l Click Measure, you can query the measurement status of the objects and the counters.
l Click Lost Result, you can query the missing measurement results.
Prerequisite
The existing measurement results are displayed in the Query Result window.
Context
l Measurement results can be displayed in a table, a line chart, or a bar chart. The system
takes the table form by default.
l In a line chart, the vertical coordinate represents the measurement counter values, and the
horizontal coordinates represents the measurement time. You can choose to display the line
chart according to By Object or By Counter.
– Select By Object, and the line chart displays the value change of multiple counters of
one object.
– Select By Counter, and the line chart displays the value change of the same counter of
multiple objects.
Procedure
Step 1 Under View Type, click Line Chart.
You can print measurement result and save job results into a file.
Step 2 You can choose to display the line chart according to By Object or By Counter.
Click to zoom out the chart, and click to zoom in the chart.
----End
Prerequisite
The existing measurement results are displayed in the Query Result window.
Context
l Measurement results can be displayed in a table, a line, or bar chart. The system takes the
table form by default.
l In a bar chart, the vertical coordinate represents the measurement value, and the horizontal
coordinate represents the measurement object or measurement counter. You can choose to
display the chart by object or by counter.
l The measurement counters are displayed in different colors and icons.
Procedure
Step 1 Under View Type, click Bar Chart.
You can print measurement results and save job results into a file.
Step 2 You can choose to display the bar chart according to By Object or By Counter.
By Object 1. In the Select Object drop list, select one or multiple measurement objects.
2. In the Select Counter drop list, select one or multiple measurement
counters.
By Counter 1. In the Select Counter drop list, select one or multiple measurement
counters.
2. In the Select Object drop list, select one or multiple measurement objects.
----End
Procedure
Step 1 Right-click Background Color in result tab to display the Background Setting dialog box.
Step 2 Select a color.
Step 3 Click OK.
----End
Related References
6.8.10 Parameters for Setting a Background Color for a Measurement Results Chart
Prerequisite
The performance measurement results are found.
Procedure
In the Query Result window, save the results through the shortcut menu or by clicking Save.
l The performance query results in tables can be saved as an .xls, .csv., .html., or .txt file.
l The performance query result in line charts or bar charts can be saved as a .jpg file.
To save the measurement results through the shortcut menu, perform the following steps:
l When the results are displayed in tables, right-click and choose Export Selected Rows or
Export All from the shortcut menu.
l When the results are displayed in line charts or bar charts, right-click and choose Save.
----End
Procedure
----End
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 From the template tree, select a template.
Step 3 Right-click and select New Query to view the Query Result dialog box. Set conditions for
querying measurement results.
NOTE
The template name is composed of up to 64 characters, including numerals, spaces, English letters, Chinese
characters and some special characters such as ! { } [ ] ( ) , . ; _
Step 6 Select a sub-directory in the directory tree in Save As to store this new template.
NOTE
The added template can only be stored under directories of the custom directory (including the custom
directory).
Step 7 Click OK to save this template. Click Cancel to cancel the added query template.
----End
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 In the template tree, select the template you want to modify.
Step 3 Right-click and select Attribute to display the Template Attributedialog box.
----End
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
Step 2 In the template tree, select the template you want to query.
Step 3 Right-click and select Attribute. The Template Attribute dialog box is displayed.
Step 4 Select Object Settings to view the selected objects on the template. Select Counter Settings to
view the selected counters on the template. Select Other Settings to view the time and sort
information on the template.
----End
Context
The default template can be copied to the Custom directory as a custom template. The custom
template can only be copied/pasted under the Custom directory.
Procedure
Step 1 Choose Performance > Query Result, or click . The Query Result window is displayed.
----End
Procedure
Step 2 Outspread the navigation tree, and select a directory node under the Template > Custom node.
Step 3 Right-click the object and select the corresponding menu option. You can create, delete, and
rename the sub-directory.
Operation Procedure
Create a sub-directory 1. Right-click and select Create directory, Enter a name for the
sub-directory.
2. Right-click and select Enter, or click the button.
Rename a sub-directory 1. Right-click and select Rename, Enter a name for the sub-
directory.
2. Press or click Enter.
NOTE
l The template name is composed of up to 64 characters, including numerals, spaces, English letters,
and some special characters " ! { } [ ] ( ) , . ; _ "
l If this sub-directory contains query templates, the templates are deleted together with this sub-directory.
----End
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
NOTE
You can enter the keyword of the object name in the Filter Search field to quickly find the object type.
----End
Related Concepts
6.1.4 Performance Measurement Periods
6.1.2 Performance Measurement Objects
6.1.2 Performance Measurement Objects
Related References
6.8.16 Parameters for Measurement States of Measurement Objects and Counters
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
You can enter the keyword of the function subset name in the Filter Search field to quickly find the function
subset.
----End
Related Concepts
6.1.6 Performance Counter Thresholds
Related References
6.8.16 Parameters for Measurement States of Measurement Objects and Counters
Context
You can edit the exported xml files, and then import them.
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
Step 3 Right-click the table on the right of the Measurement Object field and choose Import to view
the Open dialog box.
----End
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
Step 4 Right-click the table and choose Export to open the Save dialog box.
Step 5 Set the save path and enter the file name.
----End
Context
l You can import the measurement settings of counters and the objects named All. If you set
the All object to be measured, the system measures all the measurement objects of the object
type.
l For the import of user-defined counters, the system create the counters automatically if no
such counter exists.
l The imported file is in XML format.
Procedure
Step 1 Choose Performance > Measure Management > measurement Status , or click to view
the Measure Management window.
----End
Context
l Exported information includes measurement setting information of objects and counters.
l When exporting user-defined counters, you need to export the user-defined counter,
formula nesting the user-defined counter, and other information. Information of the original
counter is not exported.
l The exported file is in XML format.
l You can click All or Set in the Others tab of the Preference dialog box. Select All to export
all the measurement settings of the selected node. Select Set to export the information of
the set objects or counters.
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
----End
Procedure
Step 1 Choose Performance > Measure Management > measurement Settings to view the Measure
----End
Procedure
Step 1 Choose Performance > Measure Management > measurement Status or click . The
Measure Management window is displayed.
Step 2 Perform the related operations based on the actual requirement.
To... Perform
1. On the Measurement Status tab page, select an object whose measurement task needs
suspending.
2. Right-click the object and choose Suspend Measurement on the shortcut menu.
3. In the Prompt dialog box, click OK.
Step 4 Perform the following steps:
1. In the navigation tree, select a function subset or its counter object.
2. Right-click it and choose Suspend Measurement on the shortcut menu. The Suspend
dialog box is displayed.
3. In the Period field, set the period for executing the measurement task. In the Range field,
set the NEs and counter objects of the measurement task.
4. Click OK.
Step 5 Perform the following steps:
1. On the Management Status tab page, select an object whose measurement task needs
activating.
2. Right-click the object and choose Active Measurement on the shortcut menu.
3. In the Prompt dialog box, click OK.
Step 6 Perform the following steps:
1. In the navigation tree, select a function subset or its counter object.
2. Right-click it and choose Active Measurement . The Active dialog box is displayed.
3. In the Period filed, set the period for executing the measurement task. In the Range field,
set the NEs and counter objects of the measurement task.
4. Click OK.
----End
Related References
6.8.4 Interface Description: User-defined Counter Management
Prerequisite
You have logged in to the M2000 client.
Context
All network devices support this operation.
l You can set user-defined counters for different measurement function sets instead of object
types.
l User-defined counters supports nested setting. That means that a user-defined counter
formula can contain user-defined counters. A maximum of three layers are allowed.
l Recursive setting is not supported. The location function helps you locate the counter by
searching for keyword of the counter name.
l After the creation of a user defined counter, this counter is displayed in the table in the
User-defined Counter Management window.
l You can create user defined counters in batch by 6.5.3 Importing a User-Defined
Counter.
l This window does not close after you create a user defined counter successfully. When
creation failed, the system displays a corresponding prompt.
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click to view the User-
Defined Counter Management window.
Step 3 Click ADD. The ADD User-Defined Counter dialog box is displayed.
Step 5 Select the function set and function subset of the user-defined counter in Function Set and
Function Subset drop-down list.
NOTE
The function set and function subset of the user-defined counter depends on the selected values in the drop-
down list rather than the function set and function subset of the selected counter format.
The specific operations are as follows: Double-click a counter in Available Counter List. You
can add the counter to Formula Information. Click an operation symbol in the right part of the
table. You can also add the operation symbol to Formula Information. To compile a calculation
formula, combine the counter with the operation symbol by using an operation rule.
Step 7 Select the unit for the user-defined counter in the Unit drop-down box.
----End
Related References
6.8.5 Parameters for Adding/Modifying a User-Defined Counter
Prerequisite
You have logged in to the M2000 client.
Context
All network devices support this operation.
l The user-defined counters and all the related original counters must belong to the same
measurement function set.
l You can open the Modify User-Defined Counter dialog box by double-clicking the user-
defined counter you want to modify.
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click to view the User-
Defined Counter Management window.
To switch to the Measurement Settings tab in the Measure Management window, right-click the counter
information and choose Measurement Settings on the shortcut menu.
Step 3 Right-click the counter and choose Modify on the shortcut menu, or click Modify, to view the
Modify User-Defined Counter dialog box.
----End
Related References
6.8.5 Parameters for Adding/Modifying a User-Defined Counter
Context
l The .XML file to be imported is obtained through the export of user-defined counters to
an .XML File.
l By importing and exporting user-defined counter information, you can copy the user-
defined counter easily among multiple M2000 systems.
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click to view the User-
Defined Counter Management window.
Step 2 Click Import. In the displayed Open dialog box, select an XML file.
An .XML file may contain information about multiple user defined counters. If the user-defined
counter in the file has the same name and belongs to the same measurement object with an
existing counter in the system, the system does not import this file and displays a corresponding
prompt at the same time.
----End
Context
l The information about multiple user defined counters under different measurement units
can be saved in the same file.
l Press Shift or Ctrl to select multiple user-defined counters.
l The user-defined counter information can only be saved as the XML file.
l By importing and exporting user-defined counter information, you can copy the user-
defined counter easily among multiple M2000 systems.
Procedure
Step 1 Choose Performance > User-defined Counter Management, or click to view the User-
Defined Counter Management window.
Step 2 Select the user-defined counters for which you want to export the information.
Step 3 Click Export or right-click the counter and choose Export on the shortcut menu. The Save
dialog box is displayed.
----End
Context
For customized counters, the function of alarm threshold settings is not provided.
6.6.1 Setting a Simple Counter Threshold
Simple threshold is a threshold defined for a single counter. You can set a simple threshold for
all the objects under a measurement unit. You can also set a simple threshold for some objects
of a specific NE under a certain measurement unit. When the measurement counter value exceeds
the threshold, a threshold alarm is generated.
6.6.2 Setting a Combined Counter Threshold
Combined threshold indicates setting the threshold value for the counters after logic or arithmetic
operations. You can set a combined threshold for all the objects under a measurement unit. You
can also set a combined threshold for some objects of a specific NE under a certain measurement
unit. When the measurement counter values meet the alarm triggering condition for successive
periods, a threshold alarm is generated. When the measurement counter values meet the alarm
clearance condition for successive periods, the threshold alarm is cleared automatically.
6.6.3 Modifying a Counter Threshold
After adding a threshold, you can modify the set simple threshold based on the actual situation.
When modifying a threshold, you are not allowed to modify the threshold type.
6.6.4 Modifying a Combined Counter Threshold
This topic describes how to modify the threshold for a combined counter. You can modify the
threshold for a combined counter based on demands. The system, however, does not allow the
modification of the threshold type.
6.6.5 Activating/Deactivating a Counter Threshold
You can suspend a threshold when it is not used temporarily, and then activate it if required.
Related Concepts
6.1.6 Performance Counter Thresholds
Related References
6.8.3 Interface Description: Threshold Management
Context
l According to the four alarm levels, you can set four levels of simple thresholds for one
counter.
l If the triggered alarm is not cleared, the same alarm will not be generated again for the
same counter . When the system generates an higher level alarm, the lower level alarm will
be cleared automatically.
l On the M2000, the number of simple thresholds and combined thresholds that can be
created is limited. The sum of simple thresholds and combined thresholds must be equal
to or smaller than 30.
Procedure
----End
Related Concepts
6.1.6 Performance Counter Thresholds
6.1.6 Performance Counter Thresholds
6.1.6 Performance Counter Thresholds
Related References
6.8.12 Parameters for Setting a Simple Counter Threshold
6.8.12 Parameters for Setting a Simple Counter Threshold
6.8.12 Parameters for Setting a Simple Counter Threshold
can also set a combined threshold for some objects of a specific NE under a certain measurement
unit. When the measurement counter values meet the alarm triggering condition for successive
periods, a threshold alarm is generated. When the measurement counter values meet the alarm
clearance condition for successive periods, the threshold alarm is cleared automatically.
Context
On the M2000, the number of simple thresholds and combined thresholds that can be created is
limited. The sum of simple thresholds and combined thresholds must be equal to or smaller than
30.
Procedure
Step 4 In the Add Threshold dialog box, select Combined under Threshold Type.
Step 5 Under Combined Condition, set Alarm Level, Triggering, and Recovering.
Step 6 Under Advanced Setting, set the times of the conditions for triggering alarms and recovering
alarms, that is, if the times for which triggering or recovering conditions are fulfilled reach this
value, alarms are triggered or cleared.
By default, the times of the conditions for triggering alarms and recovering alarms are both one.
Step 7 Optional: Under Advanced Setting, you can set whether to raise the alarm severity if the times
for which alarms of the same severity are generated reach the specified value.
----End
Context
l According to the four alarm levels, you can set four levels of simple thresholds for one
counter.
l If the triggered alarm is not cleared, the same alarm will not be generated again for the
same counter . When the system generates an higher level alarm, the lower level alarm will
be cleared automatically.
Procedure
Step 4 Click Modify or right-click and choose Modify to display the Modify Threshold dialog box.
----End
Related Concepts
6.1.6 Performance Counter Thresholds
6.1.6 Performance Counter Thresholds
6.1.6 Performance Counter Thresholds
Related References
6.8.12 Parameters for Setting a Simple Counter Threshold
6.8.12 Parameters for Setting a Simple Counter Threshold
6.8.12 Parameters for Setting a Simple Counter Threshold
Procedure
Step 1 Select Performance > Threshold Management or click , and then the Threshold
Management window is displayed.
If you select Show all Threshold Information, all threshold records will be listed in the table. If this option
is not selected, the threshold record of the selected node is listed.
----End
Procedure
----End
Context
Currently, only the BSC6000 supports this function.
6.7.1 Creating a Data Collection Task
This describes how to create a data collection task. you can create a data collection task to test
certain frequency points. Then, according to the test result, you can determine the frequency
points of the cells that can serve as the neighbor cells.
Prerequisite
l You have logged in to the M2000 client.
l The NE is properly connected to the M2000.
Context
The state of a data collection task can be Started, Measuring, or Suspended. The respective
icons are , , and .
Procedure
Step 1 Choose Performance > Neighbour Cell Optimization Data Collection. The Neighbour Cell
Optimize dialog box is displayed.
Step 2 Click Add. The Add Measure Task dialog box is displayed.
Step 3 Set the related parameters.
For descriptions of the parameters, refer to 6.8.17 Parameters for Creating/Modifying the
Data Collection Task.
Step 4 Click OK.
For the first time a data collection task is created on the client, you are prompted to select the
path for saving the task information. In this case, all the subsequent data collection tasks created
on the client are saved in the .xls file in the selected path. The .xls file contains the following
information: task ID, task name, NE type, NE name, start time, end time, actual end time,
measure period, measure step, the selected cell list, the selected frequency list, and result
message.
----End
Postrequisite
After a data collection task is created, you need to select the counters related to neighbor cell
optimization on the Measure Setting tab page in the Measure Management dialog box. In this
way, the periodic measurement task is started on the NE and thus the related data of neighbor
cell optimization can be collected.
When you close the Neighbor Cell Optimization dialog box, the system asks you whether to
stop the task if certain data collection tasks are in the Measuring state. Click Yes, and then the
system issues a command to the NE to stop all the Measuring tasks and close the dialog box.
After the dialog box is closed, the information on all the tasks created on the client are invalid.
Related Tasks
6.2.4 Subscribing to NE Measurement Results
Related References
6.8.17 Parameters for Creating/Modifying the Data Collection Task
Prerequisite
l You have logged in to the M2000 client.
l The NE is properly connected to the M2000.
l At least one neighbor cell optimization data collection task is available.
Context
You can modify only the tasks in the Started or Suspended state. For a data collection task in
the Measuring state, you can suspend and then modify it. For details, see 6.7.4 Stopping a Data
Collection Task.
Procedure
Step 1 On the Neighbor Cell Optimize tab page, select a data collection task from the Measure
Task navigation tree.
Step 2 Click Modify. The Modify Measure Task dialog box is displayed.
l For descriptions of the parameters, refer to 6.8.17 Parameters for Creating/Modifying the
Data Collection Task.
Step 4 Click OK.
----End
Related References
6.8.17 Parameters for Creating/Modifying the Data Collection Task
Prerequisite
l You have logged in to the M2000 client.
l The NE is properly connected to the M2000.
l At least one neighbor cell optimization data collection task is available.
Context
You can delete only the tasks in the Suspended state. For a task in the Measuring state, you
can suspend and then delete it. For details, see 6.7.4 Stopping a Data Collection Task.
Procedure
Step 1 On the Neighbor Cell Optimize tab page, select a data collection task from the Measure
Task navigation tree.
Step 2 Click Delete.
Step 3 In the Confirmation dialog box, click Yes.
You can remove the task only from the client. The related information is still available in the .xls
file that saves the information about data collection tasks.
----End
Prerequisite
l You have logged in to the M2000 client.
l The NE is properly connected to the M2000.
l At least one neighbor cell optimization data collection task is available.
Context
If the data collection task to be deleted is in the Measuring state, you can stop and then delete
it..
Procedure
Step 1 On the Neighbour Cell Optimize tab page, select a Measuring data collection task from the
Measure Task navigation tree.
----End
Prerequisite
l You have logged in to the M2000 client.
l The NE is properly connected to the M2000.
l At least one neighbor cell optimization data collection task is available.
Context
For detailed description of the status of a data collection task, refer to 6.7.1 Creating a Data
Collection Task.
Procedure
Step 1 On the Neighbour Cell Optimize tab page, select a Measuring data collection task from the
Measure Task navigation tree.
----End
Prerequisite
l You have logged in to the M2000 client.
l The NE is properly connected to the M2000.
l At least one neighbor cell optimization data collection task is available.
l No measurement task is being performed on the NE.
Context
The software parameters cannot be set for the data collection tasks in the Measuring state.
Procedure
Step 1 On the Neighbour Cell Optimize tab page, select a Started or Suspended task from the
Measure Task navigation tree.
The NE of the selected task should not be performing a measurement task. If a measurement
task is being performed, the soft parameters fail to be modified for the selected task.
Step 2 Click Setting Soft Parameter. The Setting Soft Parameter dialog box is displayed.
Step 3 Set the parameters.
For descriptions of the parameters, refer to 6.8.18 Parameters for Soft Parameter of the Data
Collection Task.
Step 4 Click OK.
----End
Related References
6.8.18 Parameters for Soft Parameter of the Data Collection Task
Related Concepts
6.1.5 Performance Measurement Results
Related Tasks
6.3 Querying Performance Measurement Results
Related Concepts
6.1.6 Performance Counter Thresholds
Related Tasks
6.6 Managing Counter Thresholds
Related Tasks
6.5 Managing User-Defined Counters
Parameter Description
parameter Value Range Description
CounterName 100 characters at most. Cannot The name of a user defined counter is
be null. used to defined this counter. A
meaningful name is recommended.
Triggering/ 255 characters at most. Cannot Formula for the user defined counter.
Recovering be null.
Conditions
Related Tasks
6.5.1 Adding a User-Defined Counter
6.5.2 Modifying a User-Defined Counter
Parameters
Parameter Value range Description
Counter name All measurement counters of the Select in the drop-down list the
selected measurement object name of the counter for which the
filter condition is to be set.
Compare operator ">",">=","=","<" and "<=" For comparing the actual value and
the compare value of the
measurement counter. Compare
Value -999999999.99 to
999999999.99
Logical operator AND, OR and None The logical relationship between the
set filter conditions. none indicates
that the filter condition is the last
logical condition.
Related Tasks
6.3.5.7 Setting the Conditions for Filtering Result Counters
Parameters
Parameter Value range Description
Start Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 The start time for querying
(yyyy=current year+10) the missing results.
Default value: current time-12hours
End Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 The end time for querying
(yyyy=current year+10) the missing results.
Default value: current time
Related Tasks
6.2.6 Querying Missing Measurement Results
Parameters
Parameter Value range Description
Start Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 The start time for querying
(yyyy=current year+10) the measurement result
Default value: current time-12hours reliability.
End Date Time 2000-01-01-00:00 to yyyy-12-31-23:59 The end time for querying
(yyyy=current year+10) the measurement result
Default value: current time reliability.
Related Tasks
6.2.5 Querying the Reliability of Measurement Results
Parameters
Parameter Value range Description
Related Tasks
6.3.5.6 Setting the Mode of Sorting Displayed Results
Parameters
Parameter Operation
HSB Select a sample color or select a color by setting the HSB value.
Related Tasks
6.3.6.4 Setting the Background Color of a Chart
Parameters
Parameter Value range Description
Related Tasks
6.2.3 Synchronizing NE Measurement Results
Object List Enumeration. You can set a simple threshold for all
Including all the measurement objects and for one or more objects.
objects under this On the M2000, the number of objects in
measurement unit. the threshold setting is limited. The
number of objects that can be selected is
smaller than 800.
Time 00:00 to 23:59 Both the start time and the end time,
indicating in which time segment of a
day this performance threshold setting is
valid.
Measure Period 5 Minutes,15 Minutes,30 This means to set the threshold for which
Minutes,60 Minutesand24 of the 5-Minute, 15-Minute, 30-minute,
Hours. 60-minute and 24-hour periodic
measurements.
Related Concepts
6.1.6 Performance Counter Thresholds
6.1.6 Performance Counter Thresholds
6.1.6 Performance Counter Thresholds
Related Tasks
6.6.1 Setting a Simple Counter Threshold
6.6.3 Modifying a Counter Threshold
6.6.1 Setting a Simple Counter Threshold
6.6.3 Modifying a Counter Threshold
6.6.1 Setting a Simple Counter Threshold
6.6.3 Modifying a Counter Threshold
Parameter Description
Parameter Value Range Description
Object List Enumeration. The combined threshold can be set for all
indicates all the measurement objects. You can also set the combined
objects under this threshold for one or multiple objects.
measurement unit. On the M2000, the number of objects in
the threshold setting is limited. The
number of objects that can be selected is
smaller than 800.
Time 00:00 to 23:59 Both the start time and the end time,
indicating in which time segment of a
day this performance threshold setting is
valid.
Advanced Number You can set the times for which the
Setting l Indicates the times for which triggering conditions or the recovering
the triggering conditions are conditions are fulfilled. You can also
fulfilled, and the value raise the alarm severity when the times
ranges from 1 to 10 for which alarms of the same severity are
inclusive. generated reach a certain value.
l Indicates the times for which
the recovering conditions
are fulfilled, and the value
ranges from 1 to 10
inclusive.
l Indicates the times for which
alarms of the same severity
are generated, and the value
ranges from 2 to 10
inclusive. When multiple
threshold alarms of the same
severity are generated, the
alarm severity will be raised.
Parameter Description
Parameter Value Range Description
Filter by Counter You can select All, Default Search for the counters by counter
Type Counter, Extended type and list the counters in Optional
Counter, or User-defined counter list.
Counter.
Parameters
Parameter Value range Description
Date Range All, Specific, Today, Yesterday, The time range for querying the
This Week and Last Week measurement results.
l All: To query all the
measurement results.
l Specific: To query the
measurement results for the
specified time segment. You can
set the Start Time and the End
Time.
Related Tasks
6.3.5.4 Specifying the Time Range of Results
Parameter Description
Parameter Description
Parameter Description
NOTE
l If you select All, then all the added measurement objects will be measured automatically.
l On a 3G network the number of neighbor objects must be equal to or smaller than 900, and the number
of cell objects must be equal to or smaller than 900. On a 2G network the total number of neighbor
objects and cell objects must be equal to or smaller than 700.
Related Tasks
6.4.1 Querying Measurement Objects
6.4.2 Querying Measurement Counters
Parameter Description
parameter Description
parameter Description
Cell The Selected Cell The cells selected in the data collection task.
Parameter List You can click Set to view the Select Cell dialog box
Setting and select the related cells.
NOTE
For the same NE, the number of measured cells at the same
time cannot exceed 50.
parameter Description
Related Tasks
6.7.1 Creating a Data Collection Task
6.7.2 Modifying a Data Collection Task
Parameter Description
parameter Value Range Description
ASSThres An integer from 0 Used to optimize neighbor cells. When the level of
to 63. the neighbor cell is greater than this value, the
relevant traffic statistical counter adds 1.
NOTE
l Level refers to the strength of the received or transmitted signal. It is generally used in power control
and handover algorithm.
l ASSThres and RSSThres evaluate the reasonableness of the neighbor cell. According to the actual
requirements, you can modify the two values to adjust the evaluation standard.
l ADJINLVThres1 to ADJINLVThres7 evaluates the CIR distribution of neighbor cells and serving cells
and the ratio among each segment. This parameter in combination with frequency configuration
analysis indicates the severity level of each frequency interference, and thus can be used to adjust the
C/I distribution segment of neighbor cells and serving cells.
Carrier-to-interference ratio distribution refers to the distribution of the power of the carrier signals
and the power of the interference signals, that is, C/I distribution.
Related Tasks
6.7.6 Setting the Soft Parameter of a Data Collection Task
The M2000 provides the function of performance report management. You can set the query
conditions of system reports and custom reports on the GUI. The M2000 can display the queried
performance report on the report query interface. By analyzing the report data, you can obtain
the information about the performance of each NE. You can also manage KPIs, such as create,
modify, and delete KPIs on the KPI management interface.
Context
The IWF, IP Clock Server, and AHR do not support the function of performance report.
7.1 Basic Knowledge of Performance Report Management
The M2000 can summarize the performance counter data of single NEs and generate
performance reports.
7.2 Managing Performance Reports
The performance report template can be a system performance report template or a custom
performance report template. In the performance management window on the GUI, you can
select a performance report template, set the query conditions to generate the required
performance report, and then save the required query settings to a new report template. This
facilitates later queries. In addition, you can set report relations, filter, save, and print reports,
and set the display mode.
7.3 Managing KPIs
Key performance indicators (KPIs) are categorized into system KPIs and custom KPIs. The
M2000 enables you to manage KPIs, such as browse and filter KPIs, and set display conditions.
You can also set custom KPIs based on your requirement. Custom KPIs are defined on the basis
of system KPIs and the defined KPIs. They are used for setting custom reports.
7.4 MSC Server Performance Reports
The MSC Server performance report group is used to query the traffic and some services of the
MSC Server. This report group includes MSC basic traffic report, MSC Mobility management
report, CPU load report, office direction traffic report, signaling link report, and trunk group
report in a specified period.
7.5 MSC POOL Report Group
Pool report group summarizes the measurement results of the counters on each MSC server
within an MSC Pool in a specified period. After the measurement range is specified on the
M2000, the NEs report the measurement results to M2000 with the interval of 30 minutes. By
querying a Pool report, you can obtain the traffic, number of users, and services, which can serve
as reference for routine maintenance.
7.6 CDMA Pool Report Group
This describes the CDMA pool report. The pool report group summarizes the measurement
results of the counters of each MSCe within a CDMA pool in a specified period. After the
measurement range is specified through the M2000, the NEs report the measurement results
with the interval of 60 minutes. By querying the pool report, you can obtain the traffic, number
of users, and services, which can serve as reference for routine maintenance and network
adjustment.
7.7 RNC Performance Reports
The RNC performance report group is used to query RNC traffic and some services in a specified
period. This report group includes RNC report and cell report group. The RNC report includes
coverage Report, accessibility report, retainability report, mobility report, service integrity
report, availability report, and traffic report. The RNC report includes coverage report,
accessibility report, retainability report, mobility report, service integrity report, availability
report, and traffic report.
7.8 PCU Performance Reports
The PCU performance reports consist of data throughput report, transmission report,
accessibility report, availability report, and retainability report.
7.9 Reference for Performance Report Management Interfaces
This describes the performance report management interfaces and the related parameters. You
can obtain the information about the functions and thus perform the related operations.
This describes how to set a condition template for querying performance reports. You can save
the related query rules as a query condition template. This facilitates future queries.
7.2.3 Filtering the Contents of a Performance Report
This describes how to set filter conditions during the report data check. The report data that
meets the filter conditions is displayed. And the report data that does not meet the filter conditions
is shielded.
7.2.4 Setting the Display of a Performance Report Based on Conditions
This describes how to set the display of a performance report based on conditions. The counter
data that meets the condition is highlighted in the foreground color and background color.
7.2.5 Displaying a Performance Report in a Sequence Chart
This describes how to display a performance report in a sequence chart. You can choose to
display the counters of one object or the same counter of different objects in a sequence chart.
This facilitates query and comparison.
7.2.6 Displaying a Performance Report in a Comparison Chart
This describes how to display a performance report in a comparison chart. The system can display
multiple objects and counters at one time point in the same comparison chart. This facilitates
query and comparison.
7.2.7 Setting a Related Report
This describes how to set a related report. The M2000 enables you to set related reports for
performance reports of the same object type. In this way, when you query the related reports,
the query conditions are consistent with those of the original reports. You can also modify the
settings.
7.2.8 Viewing the Attributes of a Performance Report Template
This describes how to view the attributes of a performance report template to obtain the
information about the report, such as report name, report type, object type, creator, creation time,
and modification time. The M2000 provides the function of viewing the attributes of a
performance report.
7.2.9 Saving a Performance Report
This describes how to save a performance report. The M2000 client enables you to save required
information in a certain format when you are querying the report data. This facilitates query and
browsing.
7.2.10 Printing a Performance Report
This describes how to print a performance report. The M2000 client enables you to print required
information in a certain format when you are querying the report data.
7.2.11 Managing a Custom Performance Report Template
This describes how to manage the M2000 custom performance report template. This function
is used in case that the provided performance report templates cannot meet your requirement.
On the M2000 client, you can save a performance report as a report template so that it can be
repeatedly used to query performance data. This function allows you to create custom, modify,
and delete performance report templates and set the sub-reports of a custom performance.
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l The performance data of a certain time period exists in the database.
l You are authorized to browse reports.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance
Report dialog box.
Step 2 In the navigation tree, double-click a report template. Alternatively, right-click the report
template and choose Query from the shortcut menu. The Report Condition Setting dialog
box is displayed.
Step 3 Set Time Dimension, Data Selection, Time Segment Selection, Object Dimension, and
Object Range.
NOTE
l If condition templates are available, you can select one from the Select Template drop-down list.
l For information on saving the query conditions that are set this time as the template, see 7.2.2 Setting
a Template for Querying Performance Reports.
The query results are displayed on multiple tab pages. The names of level 1 tabs are consistent with those
of the report templates, that is, the nodes in the navigation tree. The names of level 2 tabs are consistent
with those of the sub-reports. If a report has only one sub-report, only the tab of this report is displayed. A
maximum of five reports can be displayed at the same time. Select a tab, right-click it and select Close
to close a primary tab.
----End
Postrequisite
You can filter, display based on conditions, correlation query, save, and print the generated
performance reports.
Related References
7.9.2 Parameters for Setting Conditions for Querying Performance Reports
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to manage reports.
Context
You can create a new query template in the Set report conditions window, modify the existing
template, or delete the template that is no longer used.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance
Report dialog box.
Step 2 In the navigation tree, double-click the report template to be operated. Alternatively, right-click
the report template and choose Query from the shortcut menu. The Report Condition
Setting dialog box is displayed.
Step 3 You can create a condition template, modify the properties of a condition template, or delete a
condition template.
l To create a condition template, perform the following steps:
1. Set each parameter in the dialog box.
See 7.9.2 Parameters for Setting Conditions for Querying Performance Reports
for details.
2. Click Save Template. The Please enter a template name dialog box is displayed.
3. Enter a template name that is different from existing names. Click OK.
l To modify the attributes of a condition template, perform the following steps:
1. In the Select template drop list of the Set report conditions dialog box, select a
template name.
2. After re-setting each property value, click Save template.
3. Click OK. The properties of the template are modified.
l To delete a condition template, perform the following steps:
1. In the Select template drop list of the Set report conditions dialog box, select a
template name.
2. Click Delete template.
3. In the displayed Confirm dialog box, click Ok. The template is deleted.
----End
Related References
7.9.2 Parameters for Setting Conditions for Querying Performance Reports
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to browse reports.
Context
The configuration of filtering conditions has two levels:
l The first level relates to the configuration of query conditions. For details, refer to 7.2.1
Generating a Performance Report.
l The second level relates to the configuration of filtering conditions for generated
performance reports.
Procedure
Step 1 In the Performance Report window, select a tab.
Step 2 Right-click the report data or the blank area and choose Filter from the shortcut menu. The
Filter Condition dialog box is displayed.
If you need to set TopN or BottomN reports, click TopN to view the TopN dialog box.
NOTE
You can set filtering conditions only for a report that uses the common style.
----End
Postrequisite
For the performance report whose filtering conditions are already set, you can right-click the list
area, and then select Cancel Filter from the shortcut menu to cancel the set filtering conditions.
Related References
7.9.3 Parameters for Setting Filter Conditions for Performance Reports
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to browse reports.
Context
You can set the display format of one or multiple counters in a report. The settings do not take
effect after the report is closed. You can also set the display format through KPI management.
The settings in this way apply to all reports. That is, when you use the report template that
contains the defined KPIs to generate reports, the counters are displayed in the format that you
have configured. For details, refer to 7.3 Managing KPIs.
Procedure
Step 1 In the Performance Report window, select a tab.
Step 2 Right-click the report data or the blank area and choose Format Setting from the shortcut menu.
The Format Setting dialog box is displayed.
l You can set a maximum of three display modes for one report.
l For the counter data that meets multiple conditions, the format of the first numbered condition
applies.
l If you need to delete a format setting, select a condition in the Delete format setting dialog
box after clicking Delete. Click OK to delete it.
l To modify a condition format, you can modify the parameters in the drop-down lists of
Counter, Condition, Foreground, and Background.
----End
Result
In the counter field, the counter values are displayed in the defined foreground and background
colors. After the report is closed, the setting expires.
Related Tasks
7.3.3 Setting the Display of a KPI Based on Conditions
Related References
7.9.4 Parameters for Setting the Condition Display of the KPIs
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to browse reports.
Context
l The series chart by object is used to compare the change tendency in a certain time period
of different counters of the same object when they are querying report data. The horizontal
coordinate of the generated series chart displays the time of each query. The vertical
coordinate displays the counter values. The legend differentiates counters in different
colors.
l The series chart by counter is used to compare the change tendency in a certain time period
of the same counters of different objects when they are querying report data. The horizontal
coordinate of the generated series chart displays the time of each query. The vertical
coordinate displays the counter values. The legend differentiates objects in different colors.
Procedure
Step 1 In the Performance Report window, select a tab.
Step 4 Select the series chart by object or by counter according to your requirements.
If... Operation
Display a sequence chart by object 1. In the Select Object drop list, select an object.
2. In the Select Counter drop list, select one or
multiple counters.
If... Operation
Display a sequence chart by counter 1. In the Select Counter drop list, select a counter.
2. In the Select Object drop list, select one or multiple
objects.
l The legend of the series chart is displayed by default. Right-click the series chart and select
Legend to hide it.
l The default background color is white. If you want to set the background color, right-click
the series chart and select Background Color. After setting the background color, click
OK and the setting completes.
l To modify the value range of the y-axis, you can right-click in the sequence chart and choose
Axis Value Range Setting from the shortcut menu. Then, you can set the value range in the
displayed Axis Value Range Setting dialog box.
If you select Auto Axis, the value range of the y-axis is automatically adjusted on the basis
of all selected counters. If you clear Auto Axis, you can set the value range of the y-axis.
In the Series Charttab, the same counter of different objects or different counters of the same
object are displayed in different colors. You can save or print the comparison chart.
----End
Related References
7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance
Reports
7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison
Chart of Performance Reports
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to browse reports.
Context
The comparison chart by object and the one by counter are both used to compare the differences
of one or multiple counters of multiple objects at a certain time period when the counters are
querying the counter data. The differences of the two comparison charts are as follows:
l The comparison chart by objects: Objects are used as the reference points to compare
counters. For comparison charts by object, objects are used as the reference points to
compare counters. The horizontal coordinate of the generated comparison chart displays
the names of the selected objects. The vertical coordinate displays the selected counter
values. The legend differentiates counters in different colors.
l The comparison chart by counters: Counters are used as the reference points to compare
objects. For comparison chart by counter, counters are used as the reference points to
compare objects. The horizontal coordinate of the generated comparison chart displays the
names of the selected counters. The vertical coordinate displays the selected counter values.
The legend differentiates objects in different colors.
Procedure
Step 1 The legend differentiates the selected objects in color. In the Performance Report window,
choose a report tab.
Step 2 Click Show chart.
Step 3 Select the Comparison chart tab.
Step 4 Set Select Time.
You can select the time from the drop-down list, or click or to select previous or next
time point relative to the current time.
Step 5 Choose an object-oriented or index-oriented comparison chart according to your requirements.
If... Then...
Display a comparison chart by object 1. In the Select Object list box, select one or
multiple objects.
2. In the Select Counter list box, select one or
multiple counters.
Display a comparison chart by counter 1. In the Select Counter list box, select one or
multiple counters.
2. In the Select Object list box, select one or
multiple objects.
l The legend of the comparison chart is displayed by default. Right-click the series chart and
select Legend to hide the legend.
l The default background color is white. If you want to set the background color, right-click
the comparison chart and select Background Color. After setting the background color,
click OK and the setting completes.
l To display the value of each counter on the comparison chart, you can right-click in the
comparison chart and choose Value Label from the shortcut menu.
l If you need to display results in a pie chart, you can right-click the comparison chart and
choose Pie Chart from the shortcut menu. If you need to display the results in the bar chart,
you can right-click the comparison chart and choose Bar Chart
By default, the results are displayed in a bar chart.
On the Comparison Chart tab page, relevant counters of different objects are displayed in
different colors. You can save or print the comparison chart.
----End
Related References
7.9.5 Parameters for Setting the Sequence Chart and the Comparison Chart of Performance
Reports
7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison
Chart of Performance Reports
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to manage reports.
Context
For performance reports of the same object type, you can set relation for them if they are
associated in the service. This facilitates the query of related reports and improves the query
efficiency.
Procedure
Step 1 In the Performance Report window, select a report in the navigation tree.
Step 2 Right-click the report and choose Relate Report from the shortcut menu. The Relate Report
dialog box is displayed.
Step 3 Create or delete a relation as required.
l To set the relation, perform the following steps:
1. Select the reports that need to be related to this report.
2. Click OK.
l To delete the relation, perform the following steps:
1. Clear the report that is related to this report.
2. Click OK.
----End
Postrequisite
After you create a report relation, you can view the relation by performing the following steps:
1. In the report tab, right-click the data or the blank area, and then choose Relation Query
> *** from the shortcut menu.
*** stands for the report that is related to this report.
2. In the displayed Report Condition Setting dialog box, set Object Rangeand then click
Query.
If the query condition is different from that of the original one, you can modify the query
condition and then query.
When setting query conditions for related reports, you can modify the level of the
summarized objects. You can also upgrade the level of Object Dimension, for example,
from Cell to Cell Group. You can also downgrade the level of Object Dimension, for
example, from Cell Group to Cell.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to browse reports.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance
Report dialog box.
Step 2 In the navigation tree, right-click the report template of which you plan to view the attributes
and choose View Property from the shortcut menu. The Report Property dialog box is
displayed.
The report attributes consist of basic information and other information. Basic information refers
to report name, report type, and object type. Other information refers to creator, creation time,
and modification time.
----End
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to browse reports.
Context
The performance report data can be saved in the format of data chart or image.
l Save a report in the format of data chart. The .xls, .csv, .html, .txt formats are allowed.
NOTE
If a report has multiple sub-reports, for the .xls format, only one file is generated with each sub-report
corresponds to a tab. By default, the file is named after the report. For the .txt, .csv, or .html format,
one file is generated for each sub-report. By default, the files are named after the sub-reports.
If the data table is displayed on the basis of conditions, the file in .xls format saves the display format.
That is, the counter data is displayed in the background color and foreground color that you have set.
l Save a report in the format of image. That is, save the report displayed in the series chart
or comparison chart. The .jpg file format is allowed.
Procedure
l Print the performance report data in the format of data chart.
1. In the Performance Report window, select a tab.
2. Right-click in the table area, and then select Save from the shortcut menu.
– You can click Save > Save Table to save the table.
– You can choose Save > Save All to save the table and the figure.
3. In the Save dialog box, set the path, name, and type of the file.
4. Click Save.
l Save the performance report data in the format of image.
1. In the Performance Report window, select a tab.
2. Click Show chart.
3. Select an image format, namely, the Series chart tab or the Comparison chart tab.
4. Right-click the chart area, and then select Save.
– You can click Save > Save Chart to save the chart.
– You can choose Save > Save All to save the table and the figure.
5. In the Save dialog box, set the path, name, and type of the file.
6. Click Save.
----End
Prerequisite
l You have logged in to the M2000 client.
l The required performance report has been generated.
l You are authorized to browse reports.
Context
You can print a performance report as a data table or an image.
l To print a performance report in the format of data table, you need to print it when it is
displayed in tabular format.
NOTE
If a report has multiple sub-reports, the data of only one sub-report can be reported each time. The
printed file is named in the format of report name-sub-report name.
l To print a performance report as an image, you need to print it when it is displayed in a
series chart or comparison chart. The .jpg file format is allowed.
Procedure
l Print the performance report data in the format of data chart.
1. In the Performance Report window, select a tab.
2. Right-click the chart area, and then select Print.
3. In the Print dialog box, click Print after setting the properties.
You can save the report data as files in different formats and then print it. The format can
be .xls, .csv, .html, or .txt. For details, refer to 7.2.9 Saving a Performance Report.
If the data table is displayed on the basis of conditions, the file in .xls format saves the
display format. That is, the counter data is displayed in the background color and foreground
color that you have set. If you print an .xls file, the data in the printed report is displayed
as shown in the .xls file.
l Print the performance report data in the format of image.
1. In the Performance Report window, select a tab.
2. Click Show chart.
3. Select an image format, namely, the Series chart tab or the Comparison chart tab.
4. Right-click the chart area, and then select Print.
5. In the Print dialog box, click Print after setting the properties.
----End
This describes how to delete a custom performance report template to release more system
resources.
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You are authorized to manage reports.
Context
l A report consists of one to five sub-reports. A custom report enables you to customize the
attributes of the sub-reports.
l If a sub-report of a report is a comparison report, then the other sub-reports must be
comparison reports.
l Four styles are available for a sub-report. These four styles can be classified into common
report style, cross report style, and comparison report style. In the cross report style, the
counters are fixed and the values are determined by both time and object. In the comparison
report style, the values of a specified counter of the same object are compared by time.
l The sub-reports of a report can use different styles. A sub-report, however, can use only
one style.
l For a sub-report using the common style, a maximum of 15 counters are allowed.
l You can customize TopN and BottomN reports. The value of N is configurable. For details,
refer to 7.2.3 Filtering the Contents of a Performance Report.
l You can select KPIs and custom KPIs.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance
Report dialog box.
3. Click Add Sub-report and then create a sub-reports for this report.
For details, refer to 7.2.11.2 Setting Sub-Reports of a Custom Performance Report
Template.
4. Select the counters to be added to the sub-report in Available Counter List, and drag them
to the corresponding sub-report areas.
l You can press Ctrl or Shift to select multiple counters.
l You can double-click a counter to add it to the sub-report list on right. Alternatively,
you can right-click the counter and choose Add to Table from the shortcut menu.
l You can enter a keyword in Filter Search to quickly find the required counter.
l For a selected counter in a sub-report, you can right-click the column of the counter and
choose Delete Counter from the shortcut menu.
l For a cross report, you can select only one counter. If more than one counter is selected
in the navigation tree, only the first counter can be dragged to the corresponding area.
When one counter is available in the sub-report, the added counter replaces the existing
one.
l For a common report, you can select the function subset and drag it to the corresponding
sub-report area. Then, all the counters under the function subset are added to the area.
l If no sub-report is defined in Add Report Template, the Define Sub-report dialog
box is displayed when you double-click a counter or drag a counter to the sub-report
area. This dialog box prompts you to create a sub-report.
l If no counter is selected in a new sub-report, the system prompts you to select counters
when you perform Step 3.5.
l In the sub-report area, you can right-click the area and choose Filter Condition from
the shortcut menu to set the filtering conditions for the sub-report.
l In the sub-report area, you can right-click the area and choose TopN from the shortcut
menu. In the displayed Filter Condition dialog box, you can set the TopN or BottomN
filtering conditions for the sub-report.
5. Click OK or Apply.
l If you click OK, the Create Report Template dialog box is closed and the settings
take effect.
l If you click OK, the Create Report Template dialog box is not closed and the settings
take effect.
l If you click Cancel, the settings are not saved.
Step 4 Create a report template by duplicating an existing template and then modifying the attributes.
1. In the navigation tree, right-click a report type and choose Copy Report from the shortcut
menu.
You can duplicate system report templates and custom report templates.
2. Locate the duplicated report template, right-click it , and then choose Modify Report from
the shortcut menu.
For details, refer to 7.2.11.3 Modifying a Custom Performance Report Template.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l The Add Report Template or Modify Report Template dialog box is active.
l You are authorized to manage reports.
Context
l You can set one to five sub-reports for a report.
l If a sub-report of a report is a comparison report, then the other sub-reports must be
comparison reports.
l Four styles are available for a sub-report. These four styles can be classified into common
report style, cross report style, and comparison report style. In the cross report style, the
counters are fixed and the values are determined by both time and object. In the comparison
report style, the values of a specified counter of the same object are compared by time.
l The sub-reports of a report can use different styles. A sub-report, however, can use only
one style.
l For a sub-report using the common style, a maximum of 15 counters are allowed.
l You can customize TopN and BottomN reports. The value of N is configurable. For details,
refer to 7.2.3 Filtering the Contents of a Performance Report.
Procedure
Step 1 Perform the following operations based on the actual requirement.
If... Then...
Step 2 To add a sub-report for a custom performance report, perform the following steps:
1. In the Add Report Template or Modify Report Template window, click Add Sub-
report. The Define Sub-report dialog box is displayed.
Alternatively, you can right-click in the counter list and choose Add Sub-report from the
shortcut menu.
2. Set Sub-report Name and select the style for the sub-report.
l If no sub-report exists, four styles can be selected in Choose Sub-report Type. They
are one comparison report style and three non-comparison report styles.
l If a comparison report is created, then only the comparison report style is available in
Choose Sub-report Type.
l If a non-comparison report is created, then the three non-comparison report style are
available in Choose Sub-report Type.
l You can view the detailed description of the selected report style in Description.
3. Click OK to close the Define Sub-report dialog box.
Step 3 To modify a sub-report for a custom performance report, perform the following steps:
1. In the Add Report Template or Modify Report Template dialog box, select the tab of
the sub-report that you plan to modify.
2. Click Modify Sub-report. The Define Sub-report dialog box is displayed.
Alternatively, you can right-click in the counter list and choose Modify Sub-report from
the shortcut menu.
3. Set the related parameters again.
4. Click OK to close the Define Sub-report dialog box.
Step 4 To delete a sub-report for a custom performance report, perform the following steps:
1. In the Add Report Template or Modify Report Template dialog box, select the tab of
the sub-report that you plan to delete.
2. Click Delete Sub-report.
Alternatively, you can right-click the counter list and choose Delete Sub-report from the
shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You are authorized to manage reports.
Context
The Object Type parameter of a custom report cannot be modified.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance
Report dialog box.
Step 2 In the navigation tree, right-click a custom report template and choose Modify Report from the
shortcut menu. The Modify Report Template dialog box is displayed.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You are authorized to manage reports.
Procedure
Step 1 Click Report > Performance Report > Report Management to view the Performance
Report dialog box.
Step 2 In the navigation tree, right-click a report type and choose Delete Report from the shortcut
menu.
Step 3 In the displayed Confirm dialog box, click Yes.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You are authorized to browse KPIs.
Context
For system KPIs, you can only view the related information. For custom KPIs, you can modify
or delete them by choosing Modify or Delete from the shortcut menu.
Procedure
Step 1 Click Report > Performance Report > KPI Management to view the KPI Management
dialog box.
Step 2 In the navigation tree, select the NE type or object type of which you plan to view the KPIs.
l If you select an NE type, you can view all the KPIs of this NE type in the counter list, including
system KPIs and custom KPIs.
l If you select an object type, you can view all the KPIs of this object type in the counter list,
including system KPIs and custom KPIs.
l In the counter list, select a KPI, and then you can view the corresponding counter formula
in Counter Formula. The formulas of only medium counters and custom KPIs rather than
original KPIs can be displayed. For description of medium counters, refer to 7.3.4 Managing
Custom KPIs.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You have performed 7.3.1 Viewing KPIs.
l You are authorized to browse KPIs.
Procedure
In the KPI Management window, enter the keywords of the counter names in Filter Counters
by Name.
– The keywords are case insensitive.
– All the counter names that contain the keywords are displayed in the counter list area.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You have performed 7.3.1 Viewing KPIs.
l You are authorized to browse KPIs.
Context
After you set the display mode for a KPI in the KPI Managementwindow, the counter is
displayed in the defined mode if the performance report contains this counter. You can also
modify the conditions in the Performance Report window. For details, refer to 7.2.4 Setting
the Display of a Performance Report Based on Conditions.
Procedure
Step 1 In the counter list in the KPI Management window, select a KPI.
Step 2 Right-click the counter and choose Format Setting from the shortcut menu. The Format
Setting dialog box is displayed.
Step 3 Set Condition, Foreground, and Background.
If the selected KPI meets the conditions, the corresponding values are displayed in the defined
foreground and background colors. For detailed parameter description, refer to 7.9.4
Parameters for Setting the Condition Display of the KPIs.
l If you need to add a format setting, click Add, and then set parameters in Condition,
Foreground, and Background.
NOTE
You can set a maximum of three display modes for one KPI.
l If you need to delete a format setting, select a condition in the Delete format setting dialog
box after clicking Delete. Click OK to delete it.
l To modify a condition format, you can modify the parameters in the drop-down lists of
Condition, Foreground, and Background.
----End
Related Tasks
7.2.4 Setting the Display of a Performance Report Based on Conditions
Related References
7.9.4 Parameters for Setting the Condition Display of the KPIs
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l You are authorized to manage KPIs.
Context
For the KPIs that can be defined for multiple objects, the data is summarized and calculated on
the basis of one object type. For example, the counter data of RNCs and cells can be calculated
on the basis of RNC. The counter data of different function subsets can be calculated on the
basis of the same object type. For example, the data of in-office and out-office counters belong
to different function subsets, but they are both office direction objects.
Procedure
Step 1 Click Report > Performance Report > KPI Management to view the KPI Management
dialog box.
If... Operation
Step 4 To create custom KPIs by object type, perform the following steps:
1. In the navigation tree, select the object type or function subset to which you plan to add
custom KPIs.
2. Click Add. The Add Counter dialog box is displayed.
Alternatively, you can right-click in the counter list and choose Add from the shortcut
menu.
3. Set Counter Name, Counter Unit, Data Type, Function Subset,and Formula
Information.
l Object Type cannot be modified.
l For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs.
l When setting formula Information, you can manually enter a counter name or double-
click a counter in the counter list.
l In Filter Counters by Name, you can enter the keyword of the counter. Then, the
system displays only the KPIs that match the keywords.
l You can select Counter Type to distinguish system counters and custom counters.
4. Click OK or Apply.
l If you click OK, the Add Counter dialog box is closed and the settings take effect.
l If you click Apply, the Add Counter dialog box is not closed and the settings take
effect.
l If you click OK, the Add Counter dialog box is closed and the settings do not take
effect.
----End
Prerequisite
l You have logged in to the M2000 client.
l The DS and the RS run properly.
l A custom KPI is available.
l You are authorized to manage KPIs.
Context
You are not allowed to modify the object type and function subset.
Procedure
Step 1 Click Report > Performance Report > KPI Management to view the KPI Management
dialog box.
Step 2 In the navigation tree, select the NE type or object type of which you plan to modify the custom
KPIs.
Step 3 In the counter list, select the custom KPI and click Modify. Alternatively, right-click the counter
and choose Modify from the shortcut menu. The Modify Counter dialog box is displayed.
Step 4 Set Counter Name, Counter Unit, Data Type, and Formula Information.
For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs.
Step 5 Click OK or Apply.
l If you click OK, the Modify Counter dialog box is closed and the settings take effect.
l If you click Apply, the Modify Counter dialog box is not closed and the settings take effect.
l If you click OK, the Modify Counter dialog box is closed and the settings do not take effect.
----End
Postrequisite
You can delete a custom KPI that is not required.
1. In the navigation tree of the KPI Management window, select the NE type or object type
of which you plan to delete the custom KPIs.
2. In the counter list, select the KPI and click Delete. Alternatively, right-click the counter
and choose Delete from the shortcut menu.
3. In the displayed Confirm dialog box, click Yes.
Objects
MSCs.
Counters
Counter Meaning
Counter Meaning
Counter Meaning
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
Handover Intra MSC HO Success Rate Rate of intra MSC handover success
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
BICC SCTP Link Number of message send Number of sent message packages
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
H248 SCTP Link Number of Message Sent Number of sent message packages
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCs.
Counters
Counter Meaning
Link Sent SIFSIO Octets Number of sent SIP and SIO octets
Link Received SIFSIO Octets Number of received SIP and SIO octets
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
For details about how to specify the measurement range of NEs, refer to 6.2.1 Setting a
Performance Measurement Range for an NE.
The incoming traffic of Pool report is used to query the Pool incoming traffic in a specified
period.
7.5.4 PoolOutTerCall Report
The PoolOutTerCall report is used to query the Pool outgoing traffic in a specified period.
7.5.5 MobileOfficeInTfc Report
The MobileOfficeInTfc report is used to query the mobile incoming traffic in a specified period.
7.5.6 MobileOfficeOutTfc Report
The MobileOfficeOutTfc report is used to query the mobile outgoing traffic in a specified period.
7.5.7 VLRSubscriber Report
The VLRSubscriber report is used to query the number of VLR subscribers in a specified period.
7.5.8 MeasurementForSMS Report
The MeasurementForSMS report is used to query the SMS services in a Pool in a specified
period.
7.5.9 MeasurementForMTC Report
The MeasurementForMTC report is used to query the MTC connections in a specified period.
7.5.10 MeasurementForLOCUp Report
The MeasurementForLOCUp report is used to query the location updates in a POOL in a
specified period.
7.5.11 Pool Cell Handover Report
The MSC Pool cell handover report is used to query the handovers in MSCs in a period of time.
7.5.12 Traffic Measurement For LAI Report
The traffic measurement for LAI report is used to query the traffics of the specified location area
in a period of time.
7.5.13 GSM Call Drop Report
The GSM call drop report is used to query the GSM call drops in an MSC Pool in a period of
time.
7.5.14 UMTS Call Drop Report
The WCDMA call drop report is used to query the WCDMA call drops in an MSC Pool in a
period of time.
7.5.15 Traffic Measurement of BSCOFI Assignment Report
The traffic measurement of BSC office assignment report is used to query the assignments of
specified BSC offices in an MSC Pool in a period of time.
7.5.16 Traffic Measurement of RNCOFI Assignment Report
The traffic measurement of RNC office assignment report is used to query the assignments of
specified RNC offices in an MSC Pool in a period of time.
7.5.17 Destcode Traffic Report
The destination code traffic report is used to query the traffics of specified destination codes in
an MSC Pool in a period of time.
Objects
MSC Servers.
Counters
Counter Function Set and Function Subset
ANSWER RATIO
CONNECTED RATIO
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
Counter Function Set and Function Subset
Local Traffic of a CALL ATTEMPT TIMES l Function set: Total Traffic of the
Pool Report Office
ALERTING TIMES Function subset: Internal Call
ANSWER TIMES l Function set: Bearer Traffic
Function subset: Trunk Office
SEIZURE TRAFFIC Direction Incoming Office Traffic
ANSWER TRAFFIC
ANSWER RATIO
CONNECTED RATIO
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
ANSWER TRAFFIC
CONNECTED RATIO
ANSWER RATIO
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
Counter Function Set and Function Subset
ANSWER TRAFFIC
CONNECTED RATIO
ANSWER RATIO
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
Counter Function Set and Function Subset
SEIZURE TRAFFIC
ALERTING TRAFFIC
ANSWER TRAFFIC
INSTALLED CIRCUIT
NUM
CONNECTED RATIO
ANSWER RATIO
AVERAGE SEIZURE
TRAFFIC PER LINE
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
SEIZURE TRAFFIC
ALERTING TRAFFIC
ANSWER TRAFFIC
INSTALLED CIRCUIT
NUM
CONNECTED RATIO
ANSWER RATIO
SEIZURE RATIO
AVERAGE SEIZURE
TRAFFIC PER LINE
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
VLR SUBSCRIBER OF
IMSI_ATTACH
VLR SUBSCRIBER OF
LOCAL
VLR SUBSCRIBER OF
ROAMING
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
Counter Function Set and Function Subset
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
Measurement For MTC SUCC RATE PAGING Function set: Call Processing
MTC Report Function subset: Traffic Measurement
MTC SUCC RATE PAGING
For MTC SUCC Rate
RESP
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
NUMBER OF IMSI
DETACH
NUMBER OF IMSI
ATTACH
NUMBER OF LOCATION
UPDATE INTRA_VLR
REQUIRE
SUCCESS NO OF
LOCATION UPDATE
INTRA_VLR REQUIRE
NUMBER OF LOCATION
UPDATE INTER_VLR
REQUIRE
SUCCESS NO OF
LOCATION UPDATE
INTER_VLR REQUIRE
SUCCESS NO OF
NATIONAL ROAMING
USER REGISTRATION
SUCCESS NO OF
INTERNATIONAL
ROAMING USER
REGISTRATION
SUCCESS RATE OF
LOCATION UPDATE
REQUEST
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
Pool Cell Handover REQUEST INTER MSC BASIC Function set: MSC Basic
Report HO IN Services
Function subset: Measurement
REQUEST INTER MSC BASIC
For MSC HO
HO OUT
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
UPDATE LOCATION
REQUEST TIMES (LAI)
MO CONNECT TRAFFIC
(LAI)
MO RESPONSE TRAFFIC
(LAI)
MT CONNECT TRAFFIC
(LAI)
MT RESPONSE TRAFFIC
(LAI)
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
GSM Call Drop Report 2G CALL DROP RATE Function set: Call Processing
CONNECT Function subset: GSM Call Drop
2G CALL DROP RATE
MO CONNECT
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
UMTS Call Drop Report 3G CALL DROP RATE Function set: Call Processing
CONNECT
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
TRAFFIC ASSIGN
SUCCESS RATE
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSC Servers.
Counters
DESTCODE ANSWER
TIMES
DESTCODE SEIZURE
TRAFFIC
DESTCODE CONNECTED
TRAFFIC
DESTCODE ANSWER
TRAFFIC
DESTCODE CONNECTED
RATIO
DESTCODE ANSWER
RATIO
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
of users, and services, which can serve as reference for routine maintenance and network
adjustment.
For details about how to specify the measurement range of NEs, refer to 6.2.1 Setting a
Performance Measurement Range for an NE.
This describes the measurement of short message report. The measurement for SMS report is
used to query the SMS services in a CDMA pool in a specified period.
7.6.9 Measurement of Paging Report
This describes the measurement of paging report. The paging measurement report is used to
query successful paging in a CDMA pool in a specified period.
7.6.10 Measurement of Location Update Report
This describes the measurement of location update report. The location update measurement
report is used to query the location updates in a CDMA pool in a specified period.
7.6.11 Traffic Measurement of Assignment Report
This describes the traffic measurement of assignment report, which is used to query the
assignments of specified offices in a CDMA pool in a period.
7.6.12 Measurement of Dest Code Report
This describes the measurement of dest code report. The destination code traffic report is used
to query the traffics of specified destination codes in a CDMA Pool in a period of time.
Objects
MSCe NE
Counters
Total Traffic of the Office Pool All Answer Times l Function set: Global Traffic
Within Pool Report Measurement
Pool All Call Attempt Function subset: Incoming
Times Traffic Measurement,
Pool All Alerting Originating Traffic
Times Measurement
l Function set: Bearer Traffic
Pool All Answer Measurement
Traffic Function subset: Outgoing
Office Measurement Based on
Pool All Seizure
Office Direction
Traffic
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Local Traffic Within Pool Pool Local Call l Function set: Global Traffic
Report Attempt Times Measurement
Function subset: Intra-office
Pool Local Alerting Traffic Measurement
Times
l Function set: Bearer Traffic
Pool Local Answer Measurement
Times Function subset: Outgoing
Office Measurement Based on
Pool Local Seizure Office Direction
Traffic
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Pool Incoming Traffic Pool Incoming Seizure l Function set: Global Traffic
Report Times Measurement
Function subset: Incoming
Pool Incoming Alerting Traffic Measurement
Times
l Function set: Bearer Traffic
Pool Incoming Answer Measurement
Times Function subset: Outgoing
Office Measurement Based on
Pool Incoming Seizure Office Direction
Pool Incoming Alerting
Pool Incoming
Connected Ratio
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Counter Function Set and Function
Subset
Pool Outgoing Traffic Report Pool Outgoing Seizure l Function set: Global Traffic
Times Measurement
Function subset: Outgoing
Pool Outgoing Alerting Traffic Measurement
Times
l Function set: Bearer Traffic
Pool Outgoing Answer Measurement
Times Function subset: Outgoing
Office Measurement Based on
Pool Outgoing Seizure Office Direction
Pool Outgoing Alerting
Pool Outgoing
Connected Ratio
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Counter Function Set and Function
Subset
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Pool Cell Handover Request Inter MSC Basic Function set: MSC Basic Service Traffic
Report HO In Measurement
Function subset: Inter-office Handoff
Request Inter MSC Basic
Measurement
HO Out
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
MOCs Connected
MOC Answered
MOC Connected
Traffic
MOC Answered
Traffic
MTCs Attempted
MTCs Connected
MTCs Answered
MTC Connected
Traffic
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Counter Function Set and Function
Subset
MT Short Message
Submission Attempts
Successful MT Short
Message Submissions
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Counter Function Set and Function
Subset
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Counter Function Set and Function Subset
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
MOC TCH
Assignment Retries
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
MSCe NE
Counters
Seized Traffic
Call Connection
Traffic
Answered Traffic
Destination Code
Connected Ratio
Destination Code
Answer Ratio
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Coverage Report
The coverage report is used to evaluate the consumption of network resources due to soft
handover in one RNC.
Objects
RNCs.
Counters
Counter RNC Counter/Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Accessibility Report
The accessibility report is used to evaluate the ability of a user to obtain the requested service
from the system.
Objects
RNCs.
Counters
Counter Formula
Counter Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Retainability Report
The retainability report is used to evaluate the ability of a user to retain its requested service for
the desired duration once connected.
Objects
RNCs.
Counters
Counter Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Mobility Report
The mobility report is used to evaluate the handover service success ratio in one RNC.
Objects
RNCs.
Counters
Counter Formula
Counter Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Traffic Report
The traffic report is used to evaluate the equivalent traffic of all CS services in one RNC, the
UL throughput of all PS services in one RNC, the DL throughput of all PS services in one RNC,
the average DL traffic of the HSDPA service at busy hour in each cell, the total traffic volume
of the HSDPA service in certain time in each cell, the average UL traffic of the HSUPA service
at busy hour in each cell, and the total traffic volume of the HSUPA service in certain time in
each cell.
Objects
RNCs.
Counters
Counter Formula
PS UL Throughput VS.PSLoad.ULThruput.RNC +
VS.PSLoad.MaxULThruput.RNC
PS DL Throughput VS.PSLoad.DLThruput.RNC +
VS.PSLoad.MaxDLThruput.RNC
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Accessibility Report
The accessibility report is used to evaluate the ability of a user to obtain the requested service
from the system.
Objects
Cells.
Counters
Counter Formula
Counter Formula
Counter Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Retainability Report
The retainability report is used to evaluate the ability of a user to retain its requested service for
the desired duration once connected.
Objects
Cells.
Counters
Counter Formula
Counter Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Mobility Report
The mobility report is used to evaluate the handover service success ratio in each cell.
Objects
Cells.
Counters
Counter Formula
Counter Formula
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Traffic Report
The traffic report is used to evaluate the equivalent traffic of all CS services in one RNC, the
UL throughput of all PS services in one RNC, the DL throughput of all PS services in one RNC,
the average DL traffic of the HSDPA service at busy hour in each cell, the total traffic volume
of the HSDPA service in certain time in each cell, the average UL traffic of the HSUPA service
at busy hour in each cell, and the total traffic volume of the HSUPA service in certain time in
each cell.
Objects
Cells.
Counters
Counter Formula
PS UL Throughput VS.PSLoad.ULThruput.RNC +
VS.PSLoad.MaxULThruput.RNC
PS DL Throughput VS.PSLoad.DLThruput.RNC +
VS.PSLoad.MaxDLThruput.RNC
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Objects
RNCs and cells
Counters
Counter Formula
VS.RRC.FailConnEstab.Cell [VS.RRC.AttConnEstab.Cell]-
[RRC.SuccConnEstab.sum]
VS.RRC.AttConnEstab.Cell VS.RRC.AttConnEstab.Cell
VS.RRC.Rej.RL.Fail VS.RRC.Rej.RL.Fail
VS.RRC.Rej.AAL2.Fail VS.RRC.Rej.AAL2.Fail
VS.RRC.Rej.Power.Cong VS.RRC.Rej.Power.Cong
VS.RRC.Rej.UL.CE.Cong VS.RRC.Rej.UL.CE.Cong
VS.RRC.Rej.DL.CE.Cong VS.RRC.Rej.DL.CE.Cong
VS.RRC.Rej.Code.Cong VS.RRC.Rej.Code.Cong
VS.RRC.Rej.Other.Cong [RRC.FailConnEstab.Cong]-
[VS.RRC.Rej.Power.Cong]-
[VS.RRC.Rej.Code.Cong]-
[VS.RRC.Rej.UL.CE.Cong]-
[VS.RRC.Rej.DL.CE.Cong]
RRC.FailConnEstab.NoReply RRC.FailConnEstab.NoReply
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Objects
RNCs and cells.
Counters
Counter Formula
VS.CS.Call.Drop.Cell [VS.RAB.Loss.CS.RF]+[VS.RAB.Loss.CS.Abnorm]
VS.RAB.Loss.CS [VS.RAB.Loss.CS.RF]+[VS.RAB.Loss.CS.Abnorm]
+[VS.RAB.Loss.CS.Norm]
Counter Formula
VS.RAB.RelReqCS.OM VS.RAB.RelReqCS.OM
VS.RAB.RelReqCS.RABPreempt VS.RAB.RelReqCS.RABPreempt
VS.RAB.RelReqCS.UTRANgen VS.RAB.RelReqCS.UTRANgen
VS.RAB.Loss.CS.RF.RLCRst VS.RAB.Loss.CS.RF.RLCRst
VS.RAB.Loss.CS.RF.ULSync VS.RAB.Loss.CS.RF.ULSync
VS.RAB.Loss.CS.RF.UuNoReply VS.RAB.Loss.CS.RF.UuNoReply
VS.RAB.Loss.CS.RF.Oth VS.RAB.Loss.CS.RF.Oth
VS.RAB.Loss.CS.Aal2Loss VS.RAB.Loss.CS.Aal2Loss
VS.Call.Drop.CS.Other [VS.RAB.Loss.CS.Abnorm]-
[VS.RAB.RelReqCS.OM]-
[VS.RAB.RelReqCS.UTRANgen]-
[VS.RAB.RelReqCS.RABPreempt]-
[VS.RAB.Loss.CS.Aal2Loss]
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Objects
RNCs and cells.
Counters
Counter Formula
VS.PS.Call.Drop.Cell [VS.RAB.Loss.PS.RF]+[VS.RAB.Loss.PS.Abnorm]
VS.RAB.Loss.PS [VS.RAB.Loss.PS.RF]+[VS.RAB.Loss.PS.Abnorm]
+[VS.RAB.Loss.PS.Norm]
VS.RAB.RelReqPS.OM VS.RAB.RelReqPS.OM
VS.RAB.RelReqPS.RABPreempt VS.RAB.RelReqPS.RABPreempt
VS.RAB.RelReqPS.UTRANgen VS.RAB.RelReqPS.UTRANgen
VS.RAB.Loss.PS.RF.RLCRst VS.RAB.Loss.PS.RF.RLCRst
VS.RAB.Loss.PS.RF.ULSync VS.RAB.Loss.PS.RF.ULSync
Counter Formula
VS.RAB.Loss.PS.RF.UuNoReply VS.RAB.Loss.PS.RF.UuNoReply
VS.RAB.Loss.PS.RF.Oth VS.RAB.Loss.PS.RF.Oth
VS.RAB.Loss.PS.GTPULoss VS.RAB.Loss.PS.GTPULoss
VS.Call.Drop.PS.Other [VS.RAB.Loss.PS.Abnorm]-
[VS.RAB.RelReqPS.OM]-
[VS.RAB.RelReqPS.UTRANgen]-
[VS.RAB.RelReqPS.RABPreempt]-
[VS.RAB.Loss.PS.GTPULoss]
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Objects
RNCs and cells.
Counters
Counter Formula
VS.RAB.FailEstabCS.Cell [VS.RAB.AttEstabCS.Conv]+
[VS.RAB.AttEstabCS.Str]-
[VS.RAB.SuccEstabCS.Conv]-
[VS.RAB.SuccEstabCS.Str]
VS.RAB.AttEstabCS.Cell [VS.RAB.AttEstabCS.Conv]+
[VS.RAB.AttEstabCS.Str]
VS.RAB.FailEstabCS.TNL VS.RAB.FailEstabCS.TNL
VS.RAB.FailEstCS.Relo VS.RAB.FailEstCS.Relo
VS.RAB.FailEstCS.RIPFail VS.RAB.FailEstCS.RIPFail
VS.RAB.FailEstCs.Power.Cong VS.RAB.FailEstCs.Power.Cong
VS.RAB.FailEstCs.ULCE.Cong VS.RAB.FailEstCs.ULCE.Cong
VS.RAB.FailEstCs.DLCE.Cong VS.RAB.FailEstCs.DLCE.Cong
VS.RAB.FailEstCs.Code.Cong VS.RAB.FailEstCs.Code.Cong
VS.RAB.FailEstCs.IUB.Band VS.RAB.FailEstCs.IUB.Band
Counter Formula
VS.RAB.FailEstabCS.Unsp.Other [VS.RAB.FailEstCS.Unsp]-
[VS.RAB.FailEstCs.Power.Cong]-
[VS.RAB.FailEstCs.Code.Cong]-
[VS.RAB.FailEstCs.ULCE.Cong]-
[VS.RAB.FailEstCs.DLCE.Cong]-
[VS.RAB.FailEstCs.IUB.Band]
VS.RAB.FailEstabCS.RNL.Other [VS.RAB.FailEstabCS.RNL]-
[VS.RAB.FailEstCS.Relo]-
[VS.RAB.FailEstCS.RIPFail]-
[VS.RAB.FailEstCS.Unsp]
VS.RAB.FailEstabCS.Other.Cell ([VS.RAB.AttEstabCS.Conv]+
[VS.RAB.AttEstabCS.Str]-
[VS.RAB.SuccEstabCS.Conv]-
[VS.RAB.SuccEstabCS.Str])-
[VS.RAB.FailEstabCS.RNL]-
[VS.RAB.FailEstabCS.TNL]
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
Objects
RNCs and cells.
Counters
Counter Formula
VS.RAB.FailEstabPS.Cell ([VS.RAB.AttEstabPS.Conv]+
[VS.RAB.AttEstabPS.Str]+
[VS.RAB.AttEstabPS.Inter]+
[VS.RAB.AttEstabPS.Bkg])-
([VS.RAB.SuccEstabPS.Conv]+
[VS.RAB.SuccEstabPS.Str]+
[VS.RAB.SuccEstabPS.Inter]+
[VS.RAB.SuccEstabPS.Bkg])
VS.RAB.AttEstabPS.Cell [VS.RAB.AttEstabPS.Conv]+
[VS.RAB.AttEstabPS.Str]+
[VS.RAB.AttEstabPS.Inter]+
[VS.RAB.AttEstabPS.Bkg]
Counter Formula
VS.RAB.FailEstPS.TNL VS.RAB.FailEstPS.TNL
VS.RAB.FailEstPS.RIPFail VS.RAB.FailEstPS.RIPFail
VS.RAB.FailEstPS.Par VS.RAB.FailEstPS.Par
VS.RAB.FailEstPS.Relo VS.RAB.FailEstPS.Relo
VS.RAB.FailEstPs.Power.Cong VS.RAB.FailEstPs.Power.Cong
VS.RAB.FailEstPs.Code.Cong VS.RAB.FailEstPs.Code.Cong
VS.RAB.FailEstPs.ULCE.Cong VS.RAB.FailEstPs.ULCE.Cong
VS.RAB.FailEstPs.DLCE.Cong VS.RAB.FailEstPs.DLCE.Cong
VS.RAB.FailEstPs.IUB.Band VS.RAB.FailEstPs.IUB.Band
VS.RAB.FailEstabPS.Unsp.Other [VS.RAB.FailEstPS.Unsp]-
[VS.RAB.FailEstPs.Power.Cong]-
[VS.RAB.FailEstPs.Code.Cong]-
[VS.RAB.FailEstPs.ULCE.Cong]-
[VS.RAB.FailEstPs.DLCE.Cong]-
[VS.RAB.FailEstPs.IUB.Band]
VS.RAB.FlEstPS.RNL.Other [VS.RAB.FailEstPS.RNL]-
[VS.RAB.FailEstPS.RIPFail]-
[VS.RAB.FailEstPS.Par]-[VS.RAB.FailEstPS.Relo]-
[VS.RAB.FailEstPS.Unsp]
VS.RAB.FailEstabPS.Other.Cell (([VS.RAB.AttEstabPS.Conv]+
[VS.RAB.AttEstabPS.Str]+
[VS.RAB.AttEstabPS.Inter]+
[VS.RAB.AttEstabPS.Bkg])-
([VS.RAB.SuccEstabPS.Conv]+
[VS.RAB.SuccEstabPS.Str]+
[VS.RAB.SuccEstabPS.Inter]+
[VS.RAB.SuccEstabPS.Bkg]))-
[VS.RAB.FailEstPS.TNL]-
[VS.RAB.FailEstPS.RNL]
NOTE
For detailed description of the performance counters, refer to NE Reference Information in Online
Help.
The data throughput report is used to collect statistics on the data throughput of the PCU in a
period of time.
7.8.2 Transmission Report
The transmission report is used to collect statistics on the transmission performance of the PCU
in a period of time.
7.8.3 Accessibility Report
The accessibility report is used to collect statistics on the accessibility of the PCU in a period of
time.
7.8.4 Availability Report
The availability report is used to collect statistics on the resource utilization of the PCU in a
period of time.
7.8.5 Retainability Report
The retainability report is used to collect statistics on the retainability of the PCU in a period of
time.
Objects
PCUs.
Counters
Counter Meaning
Uplink RLC Payload (kbits) (Number of uplink RLC data blocks using CS1*23+Number
of uplink RLC data blocks using CS2*34+Number of uplink
RLC data blocks using CS3*40+Number of uplink RLC
data blocks using CS4*54)*8/1024
Downlink RLC Payload (Number of downlink RLC data blocks using CS1*23
(kbits) +Number of downlink RLC data blocks using CS2*34
+Number of downlink RLC data blocks using CS3*40
+Number of downlink RLC data blocks using CS4*54)
*8/1024
Uplink EDGPRS RLC (Number of uplink EGPRS RLC data blocks using
Payload (kbits) MCS1*22+Number of uplink EGPRS RLC data blocks
using MCS2*28+Number of uplink EGPRS RLC data
blocks using MCS3*37+Number of uplink EGPRS RLC
data blocks using MCS4*44+Number of uplink EGPRS
RLC data blocks using MCS5*56+Number of uplink
EGPRS RLC data blocks using MCS6*74+Number of
uplink EGPRS RLC data blocks using MCS7*56+Number
of uplink EGPRS RLC data blocks using MCS8*68
+Number of uplink EGPRS RLC data blocks using
MCS9*74)*8/1024
Counter Meaning
Downlink EDGPRS RLC (Number of downlink EGPRS RLC data blocks using
Payload (kbits) MCS1*22+Number of downlink EGPRS RLC data blocks
using MCS2*28+Number of downlink EGPRS RLC data
blocks using MCS3*37+Number of downlink EGPRS RLC
data blocks using MCS4*44+Number of downlink EGPRS
RLC data blocks using MCS5*56+Number of downlink
EGPRS RLC data blocks using MCS6*74+Number of
downlink EGPRS RLC data blocks using MCS7*56
+Number of downlink EGPRS RLC data blocks using
MCS8*68+Number of downlink EGPRS RLC data blocks
using MCS9*74)*8/1024
Packet Data Rate on Air ((Uplink RLC payload (kbits)+Uplink EDGPRS RLC
Interface (UL/DL) payload (kbits)) /(Downlink RLC payload (kbits)
+Downlink EDGPRS RLC payload (kbits)))*100
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
PCUs.
Counters
Counter Meaning
Retransmission Rate of RLC (1-(Retransmission rate of RLC uplink data block using CS1
Uplink Data Block (%) (%)+Retransmission rate of RLC uplink data block using
CS2 (%)+Retransmission rate of RLC uplink data block
using CS3 (%) +Retransmission rate of RLC uplink data
block using CS4 (%))/Total number of uplink RLC data
blocks)*100
Retransmission Rate of RLC (1-(Retransmission rate of RLC downlink data block using
Downlink Data Block (%) CS1 (%)+Retransmission rate of RLC downlink data block
using CS2 (%)+Retransmission rate of RLC downlink data
block using CS3 (%)+Retransmission rate of RLC downlink
data block using CS4 (%))/Total number of downlink RLC
data blocks)*100
Retransmission Rate of Uplink (1-(Retransmission rate of uplink EGPRS RLC data block
EGPRS RLC Data Block (%) using MCS1 (%)+Retransmission rate of uplink EGPRS
RLC data block using MCS2 (%)+Retransmission rate of
uplink EGPRS RLC data block using MCS3 (%)
+Retransmission rate of uplink EGPRS RLC data block
using MCS4 (%)+Retransmission rate of uplink EGPRS
RLC data block using MCS5 (%)+Retransmission rate of
uplink EGPRS RLC data block using MCS6 (%)
+Retransmission rate of uplink EGPRS RLC data block
using MCS7 (%)+Retransmission rate of uplink EGPRS
RLC data block using MCS8 (%)+Retransmission rate of
uplink EGPRS RLC data block using MCS9 (%))/Total
number of uplink EGPRS RLC data blocks)*100
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
PCUs.
Counters
Counter Meaning
Uplink GPRS TBF Congestion (Number of uplink TBF establishment failures due to no
Rate (%) channel)/Number of uplink TBF establishment
attempts*100
Uplink GPRS TBF Congestion (Number of uplink EGPRS TBF establishment failures due
Rate (%) to no channel )/Number of uplink EGPRS TBF
establishment attempts*100
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
PCUs.
Counters
Counter Meaning
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
Objects
PCUs.
Counters
Counter Meaning
Uplink GPRS TBF Drop Rate (Number of uplink TBF abnormal release due to N3101
(%) overflow (MS no response)+Number of uplink TBF
abnormal release due to N3103 overflow (MS no response))/
Number of successful uplink TBF establishment*100
Downlink GPRS TBF Drop Number of downlink TBF abnormal release due to N3105
Rate (%) overflow/Number of successful downlink TBF
establishment*100
Uplink EGPRS TBF Drop (Number of uplink EGPRS TBF abnormal release due to
Rate (%) N3101 overflow (MS no response)+Number of uplink
EGPRS TBF abnormal release due to N3103 overflow (MS
no response))/Number of successful uplink EGPRS TBF
establishment*100
Downlink EGPRS TBF Drop Number of downlink EGPRS TBF abnormal release due to
Rate (%) N3105 overflow/Number of successful downlink EGPRS
TBF establishment*100
NOTE
To obtain the information about the previous counters, use the following methods:
l For system counters, refer to NE Reference Information in Online Help.
l For custom counters, you can find the corresponding expressions in the KPI Management window,
and then read the description of each system counter in NE Reference Information in Online
Help.
This part describes the parameters on the Series Chart tab page and the Comparison Chart
tab page.
7.9.6 Parameters for Setting the Background Color of the Sequence Chart and the Comparison
Chart of Performance Reports
This describes the parameters for setting the background color of the sequence chart and the
comparison chart of performance reports.
7.9.7 Parameters for Creating or Modifying a Custom Performance Report Template
This describes the parameters in the Add Report Template and Modify Report Template
dialog boxes.
7.9.8 Parameters for Creating or Modifying a Sub-Report
This describes the parameters in the Define Sub-report dialog box.
7.9.9 Parameters for KPIs
This describes the parameters in the Add Counter and Modify Counter dialog boxes.
(1) Navigation tree: You can select the NE type or object type of a KPI.
(2) Counter list area. This area displays the information about all the KPIs of the selected NE type or object
type. For descriptions of the parameters, refer to 7.9.9 Parameters for KPIs.
(3) Counter formula area. This area displays the information about the formula of the selected custom KPI. No
information is displayed if the selected counters are original counters.
(4) Buttons. You can add, modify, or delete custom KPIs, and close the active window by using the buttons.
(5) Keyword input area. After you enter a keyword in this area, all the counters containing the keyword are
displayed in the counter list area.
Parameter Description
Parameter Value Range Description
MSCServer NE,
and MTP3B Link
l Trunk Group
Report: Whole
Network,
MSCServer NE,
Office, and Trunk
Group
Relative Date (Offset from a previous Set a relative date as the query
date to now): date.
l Non-comparison report: Start, NOTE
End, and Unit The duration varies with the type of
performance data. Therefore, the
l Comparison report: Date 1, Date query time is determined by the
2, and Unit duration. The data duration that
exceeds the preset value cannot be
The Start/Date 1 date and End/Date queried.
2 date are the offsets compared with
the date of the day. For example, if
Date 1 is set to 2, Date 2 is set to 1, you
can infer that the query time is from
two days before to one day before.
Start/Date 1 must be greater or the
same as End/Date 2.
Unit can be Day, Week, or Month.
Time Segment All Time Segment Time segment for querying the
Selection report data.
Object Range All objects on the entire network. Query objects of the report data.
In Display Mode, you can select by
Lever or by Group to view the
objects. You can also enter the
keywords in Filter Search and then
view the matched objects in the
navigation tree.
For example, if Time Dimension is set to Hour, Data Selection is set to Today, and Time
Segment Selection is set to All Time Segment, then the sum data of each object and each hour
of the day is displayed in a row in the report.
Related Tasks
7.2.2 Setting a Template for Querying Performance Reports
7.2.1 Generating a Performance Report
Parameter Description
Parameter Value Range Description
Comparison Column Select from the drop-down list This parameter is used to set
filtering conditions.
Comparison Symbol Select from the drop-down list This parameter is used to
The values vary based on the compare Comparison
Comparison Column. Column and Value.
NOTE
This parameter cannot be
configured before you set
Comparison Column.
Relation Select from the drop-down list. This parameter is used to set the
The value can be or, and, and relations between filtering
none. conditions.
If no filtering condition is
added, the Relation in the
filtering condition is
unavailable.
NOTE
Yo can select a counter in Comparison Column, select TopN or BottomN in Comparison Symbol to set
the TopN or BottomN report. The value of N is configurable.
If the TopN or BottomN filtering conditions is defined, other filtering conditions cannot be added. If
filtering conditions excluding TopN and BottomN conditions are set, then you are informed that the defined
filtering conditions are cleared after you select the TopN or BottomN filtering conditions.
Related Tasks
7.2.3 Filtering the Contents of a Performance Report
Parameter Description
Parameter Value Range Description
Counter You can select a counter from the Name of the counter for which you
drop-down list in the performance plan to set the display mode based
report. on conditions.
In KPI management, this
parameter stands for the name of
the selected counter. It cannot be
re-selected.
Condition Select from the drop-down list. Comparison relation between the
The value can be :>, >=, =, !=, counter and counter value in the
<, <=, or between. condition setting.
NOTE
The counter value must be a
numerical value or null.
Foreground Set the color mode, sample, HSB, Color of the font. The default
or RGB. setting is black.
You can select a color from the
drop-down list. Alternatively, you
can click and select a color
in the displayed Color dialog box.
Background Set the color mode, sample, HSB, Color of the background. The
or RGB. default setting is white.
You can select a color from the
drop-down list. Alternatively, you
can click and select a color
in the displayed Color dialog box.
Related Tasks
7.2.4 Setting the Display of a Performance Report Based on Conditions
7.3.3 Setting the Display of a KPI Based on Conditions
Parameter Description
Parameter Description
Parameter Description
NOTE
To know how to set the background color, refer to 7.9.6 Parameters for Setting the Background Color
of the Sequence Chart and the Comparison Chart of Performance Reports.
Related Tasks
7.2.5 Displaying a Performance Report in a Sequence Chart
7.2.6 Displaying a Performance Report in a Comparison Chart
Parameters
Parameter Operation
HSB Select a sample color or select a color by setting the HSB value.
Related Tasks
7.2.5 Displaying a Performance Report in a Sequence Chart
7.2.6 Displaying a Performance Report in a Comparison Chart
Parameter Description
Parameter Description
To create or modify the attributes of a sub-report, refer to 7.9.8 Parameters for Creating or
Modifying a Sub-Report.
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Filter Counters by Name Indicates that the counter list displays only the counters
containing the keyword.
8 Software Management
Context
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support software
management.
8.1 Basic Knowledge of Software Management
This part describes the basic knowledge about software management, including NE software,
patches, file types for software management, directory structure of the software on the server,
and the processes for managing NodeB licenses and NE software.
8.2 Managing Software and Files
The management of software and files realizes the integrated management of software ,
configuration data, and file information for NEs.
8.3 Upgrading NE Software and Patches
You can upgrade NE software and patches. You can download, synchronize, load, activate,
confirm, deactivate, and delete the NE software and patches. The supported NEs include RNC,
NodeB, MSC Server, MGW, SGSN, GGSN, BSC, BTS, and ASN-GW.
8.4 Managing NE Licenses
This describes how to manage NE licenses by delivering the license files or license control
information from the M2000 to NEs. The function of NE license management consists of the
upload, download, activation, or assignment of the RAN system license and the license sharing
management between the NEs.
8.5 Querying Version Information on Software Installed on the Server
This describes how to query the version information about the OMC, adaptation layer, ENM,
and northbound Corba interface installed on the server through the M2000 client.
8.6 Reference for Software Management Interfaces
This part describes the software management interface and the related parameters.
8.1.1 NE Software
NE software refers to the current software versions of an NE.
8.1.2 Software Patch
This part describes software patches.
8.1.3 Patch States
This describes the states and state transition between software patches.
8.1.4 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 with the NE type.
8.1.5 RAN License
A license is provided by the supplier to the operator for the use of a product. It defines the
usability range and the validity period of the product. Through license authorization and the
purchase of the specific license, the operator can flexibly select phase-specific network functions
and capacity. The RAN system consists of an RNC and all the NodeBs under the RNC. The
RAN system has multiple license files. At one point in time, however, only one license file is
in the active state. The M2000 assigns the license values.
8.1.6 Software Management Procedure
This part describes the flow chart and networking system of software management.
8.1.1 NE Software
NE software refers to the current software versions of an NE.
Some NEs provide the main/backup software storage areas, such as MGW, NodeB, and
SGSN. Thus it can store at least two software versions at the same time. The main area stores a
software version and a hot patch of this version, namely, the activated and running software and
patch of the NE. The backup area stores the deactivated software.
The software upgrade procedure includes loading, activating, and synchronizing the software.
No state transition occurs during an upgrade process.
Different NE types map different managed files. For details, refer to Table 8-1.
BWA Versions
BTS Versions
The server saves the files of each NE. The NEs save their own files. The software management
can manage the files on both the server and the NEs at the same time. The Software
Management window of the Client provides the file structure tree. The Server tab displays the
files on the server. The tree is consistent with the structure of the /export/home/sysm/ftproot
folder on the server. The file structure of NodeB is different from other NEs, as shown in Figure
8-2 and Figure 8-3
The NE tab displays the files on each physical NE. The file structure of NodeB is different from
other NEs, see Figure 8-4 and Figure 8-5.
NOTE
A separate NodeB, that is, a NodeB not controlled by any RNC, cannot be managed on the basis of licenses.
The following part describes the information on RAN licenses.
l The RAN licenses are assigned by the M2000 and controlled by NodeBs. The result of
license assignment is delivered by the M2000 to NodeBs.
l You can assign licenses between NodeBs. The total number of license files, however,
cannot exceed. In addition, the assignment of license files between the RAN systems is not
allowed.
l The ESN, which is formed and encrypted by MCC+MNC+RNCID, binds license files to
a RAN system.
l By default, the NodeB does not use the control items of a license to restrict system resources.
The control items of a license function only after the license file is installed on the
M2000 and the result of license assignment is delivered to NodeBs.
l License synchronization between the M2000 and the NodeBs is performed on time. Thus,
the result of NodeB license assignment is sent to the M2000 on time.
l The M2000 database stores the result of license assignment after encryption check and the
cyclic redundancy check (CRC) processing.
In the event of data damage or corruption, the M2000 stops the license synchronization
check and does not spread the damaged or corrupted data.
l The NodeB automatically stores the result of license assignment, which is delivered by the
M2000.
If the maintenance links between the M2000 and the NodeB are disrupted, the NodeB can
provide the services based on the stored license configuration.
In the whole process, the M2000 server is the default file server, refer to 3.2.10 Setting an NE
as a Transfer 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.
The networking structure of software management is shown in Figure 8-7.
In Figure 8-7, M2000 server performs centralized management on the software, configuration
data and other files of each NE. The server is connected with M2000 client and NEs. Files can
be transferred between the server and the clients or NEs. The FTP protocol is used for transferring
files.
Procedure
----End
Procedure
----End
Procedure
Step 1 Choose Software > File Transfer Wizard.
The Select General Parameters dialog box is displayed.
Step 2 Select From Server To GUI under Direction.
Step 4 Perform the related operation according to the type of the file to be transferred.
Version, patch, upgrade software 1. Click Finish. The NE Selection dialog box is
package, upgrade patch package, and displayed.
backup voice 2. Select an NE.
3. Click OK.
NOTE
The NodeB downloads the relevant files according the
configuration file.
In the Software Management window, you can view the progress information in the list of
FTP Task.
----End
Prerequisite
l The related files are available on the server.
l The NEs and the server are properly connected.
Context
Please refer to 8.1.4 Software Management File Types.
Procedure
Step 1 Choose Software > File Transfer Wizard.
The Select General Parameters dialog box is displayed.
----End
Prerequisite
The connection between the client and the M2000 server is normal.
Procedure
l 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.
The supported file types vary based on the NEs. For details, refer to 8.1.4 Software
Management File Types.
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.
In the Software Browser window, you can view the progress information in the FTP
Task list.
l If the file to be transferred is a voice resource file, perform the following steps:
You can press Ctrl to select multiple voice files and click Operation Mode to set the operation
modes in batches. You can choose to overwrite, back up, or forgive the file.
l Over Write: overwrites the same file.
l Back Up: saves the file on the server and backs up the voice file that is transferred.
l Forgive: saves the file on the server and does not transfer the new file.
11. Click Finish.
In the Software Browser window, you can view the progress information in the FTP
Task list.
----End
Prerequisite
l The related files exist on the NE.
l The NEs and the server are properly connected.
Procedure
l 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 NE To Server.
3. In NE Path, select the file to be transferred.
The supported file types vary based on the NEs. For details, refer to 8.1.4 Software
Management File Types.
4. Click Finish.
In the Software Browser window, you can view the progress information in the
Immediate Task list.
l If the file to be transferred is a voice resource file, perform the following steps:
You can press Ctrl to select multiple voice files and click Operation Mode to set the operation
modes in batches.You can choose to overwrite, back up, or forgive the file.
l Over Write: overwrites the same file.
l Back Up: saves the file on the server and backs up the voice file that is transferred.
l Forgive: saves the file on the server and does not transfer the new file.
NOTE
To view the backup voice files on the server, perform the following steps:
1. In the left pane of the Software Browser window, select the MGW under NM Server.
2. Select Bak Tone
8. Click OK.
In the Software Browser window, you can view the progress in the Immediate
Task list.
----End
Prerequisite
The task list is not null.
Context
The Software Browser window contains the immediate task list and the file transfer task list.
The License Browser window contains the license task list and the file transfer task list. The
task lists on different interfaces display the tasks to be run after the corresponding interface is
displayed. The following part describes the tasks recorded by each task list:
l The immediate task list records the task of upgrading NEs and the task of transferring files
between the NEs and the server.
l The file transfer task list records all the tasks of transferring files between the M2000 client
and the server. In the Software Browser window, the file transfer tasks consist of the tasks
of uploading and downloading NE software versions, patches, and data. In the License
Browse window, the file transfer tasks consist of the tasks of uploading and downloading
license lists.
l The list of license tasks mainly records the tasks related to the license, for example,
synchronizing the network license and setting the NE sharing mode.
Procedure
Step 1 Choose the corresponding menu based on the task type to be managed.
l Immediate task: Choose Software > Browser or click on the toolbar to open the
Software Browser window.
l File transfer task: Choose Software > Browser, or click the shortcut icon , or choose
Software > License Management.
l License task: Choose Software > License Management to open the License Browser
window.
Step 2 Manage the task list.
List of immediate tasks Click the Immediate Task tab, right-click a task on the tab page,
and then choose the following menu items to perform related
operations the task:
l Setting: filters and displays the tasks according to the status or
the NEs.
l Stop Task: stops the selected tasks that are being run.
l Restart: runs the selected tasks again.
l Show Detail: displays the detailed information about the selected
tasks.
l Refresh: refreshes the task list.
File transfer task list Click the FTP Task tab, right-click a task on the tab page, and then
choose the following menu items to perform related operations on
the task:
l Stop Task: stops the selected tasks that are being run.
l Restart: runs the selected tasks again.
l Show Detail: displays the detailed information about the selected
tasks.
l Delete Task: deletes the selected tasks.
License task list Click the License Task tab, right-click a task on the tab page, and
then choose the following menu items to perform related operations
on the task:
l Job Setting: filters and displays the tasks according to the task
status or the NEs.
l Show Detail: displays the detailed information about the selected
tasks.
l Refresh: refreshes the task list.
----End
Procedure
Step 1 Choose Software > FTP Setting.
The FTP Setting dialog box is displayed.
Step 2 Select the transfer mode, optional functions, and expire time.
l The transfer mode can be FTP or SFTP
l The optional functions include breakpoint, compress, and passive mode.If passive mode is
not selected, active mode is selected by default.
l The expire time ranges from 5 to 3600 seconds.
For detailed description of the parameters, refer to 8.6.8 Parameters for Setting Parameters
of Files Transferring.
Step 3 Click OK.
----End
Related References
8.6.8 Parameters for Setting Parameters of Files Transferring
take effect immediately. To play the voice, you must load the file to the VPU board. This function
enables you to check whether all the voice files are consistent and whether the voice files on the
MGW OMU board match to those on each VPU board.
8.2.9.3 Synchronizing a Voice File
This describes how to synchronize a voice file on the active OMU to the standby OMU. In this
way, the voice file on the standby OMU can be complete. Thus, in case that the active OMU is
faulty, you can start the standby OMU to ensure the normal operation of the MGW.
Prerequisite
l You have successfully logged in to the M2000 client.
l The MGW is properly connected to the M2000 server.
l The required voice file is available on the active OMU of the MGW.
Context
l Voice files can be classified into voice package files and dynamic voice files.
l Voice package files are categorized into broadband voice package files and narrowband
voice package files. A broadband voice package files can be named only tonefile_wb.arj
and a narrowband voice package file can be named only tonefile.arj. A single MGW can
have ony one broadband voice package file and one narrowband voice package file.
l Dynamic voice files are categorized into broadband dynamic voice files and narrowband
dynamic voice files. The extension of a broadband dynamic voice files is .wbv and the
extension of a narrowband voice file is .spf. A single MGW can have multiple dynamic
voice files.
Procedure
Step 1 Determine the type of the voice file to be loaded.
CAUTION
During the operation, the asynchronous voice is deleted. Therefore, you must ensure that the
loading process is not interrupted. Otherwise, the asynchronous voice is lost.
1. Choose Software > Browser or click on the toolbar. The Software Browser window
is displayed.
2. In the NE tab, select an MGW in the file structure tree.
3. In the Tone tab, click Load. The Tone files Loading Wizard-Boards Separating dialog
box is displayed.
4. Select an active board. Click Query ATone.
5. Delete the asynchronous announcement.
NOTE
1. Choose Software > Browser or click on the toolbar. The Software Browser window
is displayed.
2. In the NE tab, select an MGW in the file structure tree.
3. In the Tone tab, click Load. The Tone files Loading Wizard-Boards Separating dialog
box is displayed.
4. Select an active board. Click Next. The Tone files Loading Wizard-Tone Files
Loading dialog box is displayed.
5. In the Tone files Loading Wizard-Tone Files Loading dialog box, click the Tone File
Load Information tab.
6. Select the dynamic voice file to be loaded in the file structure tree. Click Load. Then you
can view the loading progress and status in the Tone File Load Information tab.
7. After the loading is complete, click Next. The Tone files Loading Wizard-Boards
Activating dialog box is displayed.
8. Click Finish. Then the voice file is completely loaded.
----End
Prerequisite
l You have successfully logged in to the M2000 client.
l The MGW and its active MSC server are properly connected to the M2000 server.
Context
l Each voice file contains the voice ID, though which the MSC server identifies the voice
file. You can check whether the voice IDs stored on the MSC server match to those
contained in the voice files on the MGW.
l THe MGW centrally manages the voice files through the M2000. You can check whether
the voice files on the M2000 server match to those stored on the MSG OMU board.
l On the MGW, you must load the voice files from the OMU board to the VPU board to
make the files effective. You can check whether the voice files on each VPU board match.
Procedure
Step 1 Choose Software > Browser or click on the toolbar. The Software Browser window is
displayed.
Step 2 In the NE tab, select an MGW from the file structure tree.
Step 3 In the Tone tab, click Check. The Confirm dialog box is displayed.
Step 4 Click Yes. The Tone File Check dialog box is displayed.
----End
Prerequisite
l You have successfully logged in to the M2000 client.
l The MGW is properly connected to the M2000 server.
Context
l After you load a voice file to the MGW, it is loaded to only the active OMU. Therefore,
you must perform this operation to synchronize the voice file to the standby OMU.
l After you delete a voice file, the voice files on both the active OMU and the standby OMU
are deleted. Therefore, you do not need to perform the synchronization.
Procedure
Step 1 Choose Software > Browser or click on the toolbar. The Software Browser window is
displayed.
Step 2 In the NE tab, select an MGW in the file structure tree.
Step 3 In the Tone tab, click Synchronize.
You can check the synchronization progress in the Immediate Task tab.
----End
Context
l You can upgrade the M2000 NE software and patches only after purchasing the license of
the software management function.
l The system displays the dialog box that needs confirming with an audible alert when you
upload or activate the NE software and patches.
8.3.1 Managing a Scheduled Upgrade
To upgrade software of the NodeB, BSC and BTS. The M2000 provides the function of plan
upgrade tasks. You can check, import, or export plan upgrade tasks.
8.3.2 Upgrading the RNC Software and Patch
This task describes how to upgrade the RNC software and patches.
8.3.3 Upgrading the SGSN Software and Patch
This task describes how to upgrade the SGSN software and patches.
8.3.4 Upgrading the GGSN Software and Patch
This task describes how to upgrade the GGSN software and patches.
8.3.5 Upgrading the MSC Server Software Patch
This task describes how to upgrade the patches of the MSC Server.
8.3.6 Upgrading the MGW Software and Patch
By creating an upgrade task, you can easily upgrade the software of one or multiple MGWs or
patches.
8.3.7 Upgrading the AG Software and Patch
This task describes how to upgrade the AG software and patches.
8.3.8 Upgrading the ICS Software
The M2000 provides the NodeB upgrade wizard. You can easily upgrade the software of one or
multiple ICSs.
8.3.9 Upgrading the NodeB Software and Patch
By creating an upgrade task, you can easily upgrade the software and patches of one or multiple
NodeBs.
8.3.10 Upgrading the BSC Software and Patch
This task describes how to upgrade the BSC software and patches.
8.3.11 Upgrading the BTS Software
This describes how to upgrade the BTS software.
8.3.12 Upgrading the ASN-GW Software and Patch
This task describes how to upgrade the ASN-GW software and patches.
8.3.13 Monitoring the Procedure of Software Upgrade
Monitor the NE upgrade process, which includes loading, activating, and synchronizing the NE
software, and loading, activating, deactivating, confirming, and uninstalling the NE patches.
Procedure
----End
Postrequisite
Please refer to 8.2.7 Managing Task List about the operations in the task list.
Context
l The current import data overwrites the previously imported data.
l Please refer to 8.3.1.4 File Format of a Scheduled Upgrade.
l Click Template, you can obtain the template of plan upgrade task.
Procedure
Step 1 Choose Software > Plan Upgrade Task.
Step 3 Select the excel files to be imported, or type the name and path of the excel files to be imported.
----End
Prerequisite
Data exists in the table in Plan Upgrade Tasks.
Context
The format of a plan upgrade task can be the Excel or the CSV format.
Procedure
Step 1 Choose Software > Plan Upgrade Task.
----End
A NodeB supports two kinds of scheduled upgrade tasks, that is, scheduled download and
scheduled activation.
Scheduled Download
To know the format of a scheduled download template, refer to Table 8-2.
Item Content
Scheduled Activation
To know the format of a scheduled activation template, refer to Table 8-3.
Item Content
Item Content
NOTE
The NE to be upgraded must be the NodeB and exist on the topology view.
l Vxxx (version) indicates a single product or a product series. Thus, a product may have
multiple versions. Each version has a general development plan and can be further
categorized into multiple releases.
l Rxxx (release) indicates a feature version that provides a series of product features. A series
of feature products may have its own feature version or may be indicated through special
letters or numbers added to a feature version.
l Cxx indicates a specific sub-version of features delivered to customers.
l Bxxy (build) indicates the build versions during the developing process.
l SPxx (Service Pack) indicates the version of a patch.
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the RNC is already set.
l The RNC communicates properly with the M2000.
l The software versions of the RNC are downloaded to the RNC successfully.
Procedure
If no software version under the corresponding NE can be loaded, you can download files to the
NE by using the server.
Step 4 Click Load. Perform the related operation according to the type of the loading.
Initial loading In the displayed Upgrade dialog box, click OK and then perform Step
5.
For initial loading, the Upgrade dialog box is displayed, showing the
upgrade progress. During the upgrade, the system downloads
configuration files and NE online help to the client to confirm the
parameters that need be set by users.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the RNC is already configured.
l The RNC communicates properly with the M2000.
l The applications of the RNC are downloaded to the RNC successfully.
Context
l Each NE can activate only one software version. After a software version is activated
successfully, the original version is automatically set to be deactivate.
l If the selected software version is already activated, the system prompts that the activation
fails.
Procedure
Step 4 Click Activate. Perform the related operation according to the type of the activation.
Initial activation In the displayed Upgrade dialog box, click OK and then perform
Step 5.
For initial activation, the Upgrade dialog box is displayed, showing
the upgrade progress. During the upgrade, the system downloads
configuration files and NE online help to the client to confirm the
parameters that need be set by users.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the RNC is already set.
l The RNC communicates properly with the M2000.
l The software patches of the RNC are downloaded to the RNC successfully.
Procedure
If no software patch under the corresponding NE can be loaded, you can download files to the
NE by using the server.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the RNC is already set.
l The RNC communicates properly with the M2000.
l The applications of the RNC are downloaded to the RNC successfully.
Procedure
----End
Context
Before you activate patches, confirm the patches.
Procedure
Step 2 On the NE tab page, select a RNC from the navigation tree.
----End
Related References
8.6.3 Parameters for RNC Patch
Context
NOTE
Only the patches that are activated but not confirmed can be deactivated. Confirmed patches can be deleted
only by deleting patches.
Procedure
----End
Procedure
----End
On the M2000, you can use the software management function to uninstall a software patch of
a specified software version of the SGSN.
Related References
8.6.4 Parameters for Other NE Software and Patch
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the SGSN is already set.
l The SGSN communicates properly with the M2000.
l The software versions of the SGSN are downloaded to the SGSN successfully.
Procedure
If no software version under the corresponding NE can be loaded, you can download files to the
NE by using the server.
Step 4 Click Load. Perform the related operation according to the type of the loading.
Initial loading In the displayed Upgrade dialog box, click OK and then perform Step
5.
For initial loading, the Upgrade dialog box is displayed, showing the
upgrade progress. During the upgrade, the system downloads
configuration files and NE online help to the client to confirm the
parameters that need be set by users.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the SGSN is already set.
l The SGSN communicates properly with the M2000.
l The applications of the SGSN are downloaded to the SGSN successfully.
Context
l Each NE can activate only one software version. After a software version is activated
successfully, the original version is automatically set to be deactivate.
l If the selected software version is already activated, the system prompts that the activate
operation fails.
Procedure
Initial activation In the displayed Upgrade dialog box, click OK and then perform
Step 5.
For initial activation, the Upgrade dialog box is displayed, showing
the upgrade progress. During the upgrade, the system downloads
configuration files and NE online help to the client to confirm the
parameters that need be set by users.
----End
Procedure
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the SGSN is already configured.
l The SGSN communicates properly with the M2000.
l The software patches of the SGSN are downloaded to the SGSN successfully.
Procedure
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the SGSN is already configured.
l The SGSN communicates properly with the M2000.
l The applications of the SGSN are downloaded to the SGSN successfully.
Procedure
----End
Context
Before you activate patches, confirm the patches.
Procedure
----End
Context
NOTE
Only the patches that are activated but not acknowledged can be deactivated. You can delete acknowledged
patches only by deleting patches.
Procedure
----End
Procedure
----End
On the M2000, you can use the software management function to load the GGSN patches to
each board of the GGSN.
8.3.4.5 Activating the GGSN Software Patch
After patches are loaded to the GGSN, the patches are in the deactivated state. After the activate
command is sent, the GGSN automatically reboots. After the GGSN runs the loaded patches,
the patches are activated.
8.3.4.6 Confirming the GGSN Software Patch
This task is performed to confirm software patch of the software version designated by the
GGSN NE through software management. After the mandatory confirmation, the software patch
automatically take effect upon the restart of the GGSN.
8.3.4.7 Deactivating the GGSN Software Patch
You can use the software management function to deactivate the GGSN patches that are activated
but not acknowledged.
8.3.4.8 Deleting the GGSN Software Patch
On the M2000, you can use the software management function to uninstall a software patch of
a specified software version of the GGSN.
Related References
8.6.4 Parameters for Other NE Software and Patch
l Vxxx (version) indicates a single product or a product series. Thus, a product may have
multiple versions. Each version has a general development plan and can be further
categorized into multiple releases.
l Rxxx (release) indicates a feature version that provides a series of product features. A series
of feature products may have its own feature version or may be indicated through special
letters or numbers added to a feature version.
l Cxx indicates a specific sub-version of features delivered to customers.
l Bxxy (build) indicates the build versions during the developing process.
l SPxx (Service Pack) indicates the version of a patch.
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the GGSN is already set.
l The GGSN communicates properly with the M2000.
l The software versions of the GGSN are downloaded to the GGSN successfully.
Procedure
If no software version under the corresponding NE can be loaded, you can download files to the
NE by using the server.
Step 4 Click Load. Perform the related operation according to the type of the loading.
Initial loading In the displayed Upgrade dialog box, click OK and then perform Step
5.
For initial loading, the Upgrade dialog box is displayed, showing the
upgrade progress. During the upgrade, the system downloads
configuration files and NE online help to the client to confirm the
parameters that need be set by users.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the GGSN is already set.
l The GGSN communicates properly with the M2000.
l The applications of the GGSN are downloaded to the GGSN successfully.
Context
l Each NE can activate only one software version. After a software version is activated
successfully, the original version is automatically set to deactivate.
l If the selected software version is already activated, the system prompts that the activate
operation fails.
Procedure
Step 4 Click Activate. Perform the related operation according to the type of the activation.
Initial activation In the displayed Upgrade dialog box, click OK and then perform
Step 5.
For initial activation, the Upgrade dialog box is displayed, showing
the upgrade progress. During the upgrade, the system downloads
configuration files and NE online help to the client to confirm the
parameters that need be set by users.
----End
Prerequisite
l You have logged in to the M2000 client.
l The relay server of the GGSN is set.
l The GGSN communicates properly with the M2000.
l The software patches of the GGSN are downloaded to the GGSN.
Procedure
Step 5 Set the parameters in the Load Patch Parameters Selection dialog box.
Step 6 Click OK.
You can query the progress of the task in Immediately Task.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the GGSN is already set.
l The GGSN communicates properly with the M2000.
l The applications of the GGSN are downloaded to the GGSN successfully.
Procedure
----End
Context
Confirm the patches before you activate them.
Procedure
----End
Context
NOTE
Only the patches that are activated but not acknowledged can be deactivated. You can delete acknowledged
patches only by deleting patches.
Procedure
----End
Procedure
----End
Context
l Before you perform the patch operation, take care to read the Patch Operation Guide.
l Select a module for each type of boards to perform a patch operation. After the patch
operation is sucessful, perform the same operation for all other modules.
8.3.5.1 MSC Server Software and Patch
This describes the software versions for the MSC server, naming rules for its patches, and
precautions for loading the software.
8.3.5.2 Loading the MSC Server Software Patch
On the M2000, you can use the software management function to load the MSC Server patches
to each board of the MSC Server.
Related References
8.6.4 Parameters for Other NE Software and Patch
l Vxxx (version) indicates a single product or a product series. Thus, a product may have
multiple versions. Each version has a general development plan and can be further
categorized into multiple releases.
l Rxxx (release) indicates a feature version that provides a series of product features. A series
of feature products may have its own feature version or may be indicated through special
letters or numbers added to a feature version.
l Cxx indicates a specific sub-version of features delivered to customers.
l Bxxy (build) indicates the build versions during the developing process.
l SPxx (Service Pack) indicates the version of a patch.
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the MSC Server is already set.
l The MSC Server communicates properly with the M2000.
l The software patches of the MSC Server are downloaded to the MSC Server successfully.
Context
Load patches when the traffic volume is low.
Procedure
Step 2 Select a MSC Server under the navigation tree on the NE tab.
If no software patch under the corresponding NE can be loaded, you can download files to the
NE by using the server.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the MSC Server is already set.
l The MSC Server communicates properly with the M2000.
l The applications of the MSC Server are downloaded to the MSC Server successfully.
Context
l The board type is patch-specific. Boards of the same type are distinguished from each other
by different module IDs.
l To ensure the correctness, first activate the patche of a module, and then activate patches
of all the modules.
Procedure
----End
Context
l Before you activate patches, confirm the patches.
l The active and standby boards need be confirmed separately.
Procedure
----End
Context
l Only the patches that are activated but not acknowledged can be deactivated.
Acknowledged patches can only be deleted rather than deactivated.
l 8.1.3 Patch States describes the state transition of a patch.
Procedure
Step 2 Select an MSC Server from the navigation tree on the NE tab.
----End
Procedure
Step 2 Select a MSC Server under the navigation tree on the NE tab.
----End
Prerequisite
l You have logged in to the M2000 client.
l The relay server of the MGW is configured.
l The connection between the MGW and the M2000 server is normal.
l The software or patch to be upgraded is available on the M2000 server.
Upgrade Procedure
l You can also upgrade the MGW software and patch through a one-step operation. For
details, refer to 8.3.3 Upgrading the SGSN Software and Patch.
l For you deactivate or delete the patch. For details of the patch state transition, refer to 8.1.3
Patch States.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade MGW . The NE Upgrade Wizard
window is displayed.
Step 3 Select one or more MGWs under the All NE navigation tree.
You can select Version to categorize the NEs in the navigation tree.
Step 4 Click or to shift the selected NEs to the list in the right part of the window.
----End
Related References
8.6.4 Parameters for Other NE Software and Patch
You can use the software management function to deactivate the AG patches that are activated
but not acknowledged.
8.3.7.9 Deleting the AG Software Patch
On the M2000, you can use the software management function to uninstall a software patch of
a specified software version of the AG.
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the AG is already set.
l The AG communicates properly with the M2000.
l The software versions of the AG are downloaded to the AG successfully.
Procedure
If no software version under the corresponding NE can be loaded, you can download files to the
NE by using the server.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the AG is already set.
l The AG communicates properly with the M2000.
l The applications of the AG are downloaded to the AG successfully.
Context
l Each NE can active only one software version. After a software version is activated
successfully, the original version is automatically set to be deactivate.
l If the selected software version is already activated, the system prompts that the activate
operation fails.
Procedure
NOTE
If you activate the AG for the first time, the Software dialog box is displayed. You can browse the upgrade
progress. During the upgrade, the system downloads configuration files and NE online help to the client
to confirm the parameters that need be set by users. After the upgrade is complete, click OK to view
Activate Software Parameters Selection.
----End
Procedure
----End
Prerequisite
l You have successfully logged in to the M2000 client.
l The relay server of the AG is configured.
l The AG communicates properly with the M2000.
l The software patches of the AG are successfully downloaded to the AG.
Procedure
If a software patch under the corresponding NE cannot be loaded, you can download the files
to the NE by using the server.
----End
Prerequisite
l You have successfully logged in to the M2000 client.
l The relay server of the AG is configured.
l The AG communicates properly with the M2000.
l The applications of the AG are successfully downloaded to the AG.
Procedure
----End
Context
Before you activate patches, confirm the patches.
Procedure
----End
Context
NOTE
Only the patches that are activated but not acknowledged can be deactivated. You can delete acknowledged
patches only by deleting patches.
Procedure
----End
Procedure
----End
Prerequisite
l The ICS is properly connected to the server.
l You can conveniently upgrade one or more NodeBs.
l The relay server of the ICS is already set.
Context
The software version of the ICS is named in the format of product name + VxxxRxxxCxxBxxy
[SPxx].
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple
versions. Each version has a general development plan and can be further categorized into
multiple releases. Rxxx (release) indicates a feature version that provides a series of product
features. A series of feature products may have its own feature version or may be indicated
through special letters or numbers added to a feature version. Cxx indicates a feature version
under the R-version delivered to customers. Bxxy (Build) indicates the build versions during the
developing process. SPxx (Service Pack) indicates the version of a patch.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade ICS . The NE Upgrade Wizard window
is displayed.
Step 2 Select an upgrade type under Upgrade Type.
Step 3 Select one or more ICSs under the All NE navigation tree.
You can select Version to organize the NEs in the navigation tree.
Step 4 Click or to shift the selected NEs to the list in the right part of the window.
----End
Prerequisite
l You have logged in to the M2000 client.
l The relay server of the NodeB is configured.
l The connection between the M2000 and the NodeB is normal.
l The software or patch to be upgraded is available on the M2000 server.
l Vxxx (version) indicates a single product or a product series. Thus, a product may have
multiple versions. Each version has a general development plan and can be further
categorized into multiple releases.
l Rxxx (release) indicates a feature version that provides a series of product features. A series
of feature products may have its own feature version or may be indicated through special
letters or numbers added to a feature version.
l Cxx indicates a specific sub-version of features delivered to customers.
l Bxxy (build) indicates the build versions during the developing process.
l SPxxxx (Service Pack) indicates the version of a patch.SPCxxx indicates a cold
patch.SPHxxx indicates a hot patch.
NOTE
Before you perform the patch operation, take care to read the Patch Operation Guide.
Upgrade Procedure
l Usually, an RNC hosts tens or hundreds of NodeBs. You can upgrade the software of one
NodeB first. After verifying the software upgrade, install and verify the patches, and then
upgrade other NodeBs in batches. When upgrading all the NodeBs in batches, you can
divide them into groups and then upgrade the NodeBs in each group in batches.
l You can also upgrade the NodeB software and patch through a one-step operation. For
details of the operation, refer to 8.3.3 Upgrading the SGSN Software and Patch. Note
that the NodeB need not be loaded during upgrade.
l For you deactivate or delete the patch. For details of the patch state transition, refer to 8.1.3
Patch States.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade NodeB .
The NE Upgrade Wizard window is displayed.
Step 2 Select an upgrade type under Upgrade Type.
l To upgrade the software, select Upgrade BootRom and software.
l To upgrade the patch, select Upgrade Hot Patch.
TIP
Step 3 Select one or more NodeBs under the All NE navigation tree.
You can select RNC, NodeB Type, or Version to categorize the NEs in the navigation tree.
Step 4 Click or to shift the selected NEs to the list in the right part of the window.
Click or to move the previous NEs back.
Step 5 Click Next.
Step 6 Select a software or patch version under Parameter Setting.
Step 7 Select one or multiple operations in Operation Setting.
NOTE
The upgrade operations vary according to the software types. For details, refer to 8.6.6 Parameters for
Upgrading the NodeB Software.
----End
Related References
8.6.4 Parameters for Other NE Software and Patch
8.6.6 Parameters for Upgrading the NodeB Software
Procedure
Step 2 Select a BSC under the navigation tree on the NE tab page.
Step 5 Select a version that needs to download in Name. Select SOFTWARE in the Software Type
pull-down box.
----End
Prerequisite
l You have logged in to the M2000 client.
l The relay server of the BSC is already set.
l The BSCs communicate properly with the M2000.
Context
If exceptions occur during the upgrade of the BSCs, the system prompts you to exit the upgrade
and allows the rollback to the previous state.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade BSC6000 . The NE Selection is
displayed.
Step 2 In the navigation tree of NEs, choose one or more BSCs to be upgraded.
Step 6 When the progress bar displays 100%, click Next to check the progress before the upgrade.
You can click Fetch Report to obtain a upgrade report. You can also view and store relevant
system information and operation records.
Step 7 When the progress bar displays 100%, click Next to load software and BIOS.
You can click Fetch Report to obtain a upgrade report. You can also view and store relevant
system information and operation records.
Step 8 When the progress bar displays 100%, click Next to perform the upgrade.
You can click Fetch Report to obtain a upgrade report. You can also view and store relevant
system information and operation records.
Step 9 When the progress bar displays 100%, click Next to perform check before the upgrade.
You can click Fetch Report to obtain a upgrade report. You can also view and store relevant
system information and operation records.
Step 10 When the progress bar displays 100%, click Next to submit the upgrade.
The system prompts that when the upgrade is submitted, performing rollback is not allowed.
When the upgrade submission is finished, the system prompts that the user upgrade is finished.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The BSC communicates properly with the M2000.
l The software is downloaded from the M2000 server to the disk of the BSC.
Procedure
If no software patch under the corresponding NE can be loaded, you can download files to the
NE by using the server.
Step 4 Click Load.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The BSC communicates properly with the M2000.
l The applications of the BSC are downloaded to the BSC successfully.
Procedure
----End
Context
Before you activate patches, confirm the patches.
Procedure
----End
Context
NOTE
Only the patches that are activated but not confirmed can be deactivated. Confirmed patches can be deleted
only by deleting patches.
Procedure
----End
Procedure
----End
Procedure
----End
This describes how to upgrade the BTS software by one push. In BTS Upgrade of the M2000
client, you can select the software version and its mapping BTS. Select the uploading and
activation operations simultaneously and issue the commands to the NEs. The M2000 client
displays the progress of task performance. The results are reported to the M2000 after all the
operations are completed by the NEs.
8.3.11.5 Querying the BTS NE Information
This describes how to query the BTS information to familiarize yourself with the name and type
of the BTS that is connected with the M2000. In addition, you can find the BSC to which the
BTS belongs.
8.3.11.6 Querying the Version of BTS Board
This describes how to query the version of the BTS board to learn the version information about
the running BTS boards.
BTS Software
This describes the software versions for the BTS, and precautions for software loading.
Prerequisite
l You have logged in to the M2000 client successfully.
l The BTS communicates properly with the M2000.
l The software of the BTS is downloaded to the BTS successfully.
Procedure
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the BTS is already set.
l The BTS communicates properly with the M2000.
l The applications of the BTS are downloaded to the BTS successfully.
Context
You need to activate the TMU board before activating other boards.
Procedure
----End
activation operations simultaneously and issue the commands to the NEs. The M2000 client
displays the progress of task performance. The results are reported to the M2000 after all the
operations are completed by the NEs.
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the BTS is already set.
l The BTS communicates properly with the M2000.
l The applications of the BTS are downloaded to the BTS successfully.
Procedure
Step 1 Choose Software > NE Upgrade Wizard > Upgrade GBTS . The BTS Upgrade is displayed.
Step 3 Click to add the selected BTS to the valid domain at the right side.
l Click to add all the BTSs to the valid domain at the right side.
l Click to clear up the valid domain if you need to clear all the BTSs in the valid domain
and reselect them.
l Click Export to export the information in the valid domain to the Excel table. Set the saving
path and file name, and then click OK. The system prompts whether this operation succeeds
or not. You can find the Excel table in the path and query relevant information. The table
records the software name, NE name, and NE type of each BTS in the valid domain.
l Click Import if you need to directly import the information from the Excel table to the valid
domain. Find the edited Excel table in the corresponding directory, and then click OK. The
BTS in the Excel table is displayed in the valid domain.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the BTS is already set.
l The BTS communicates properly with the M2000.
l The applications of the BTS are downloaded to the BTS successfully.
Procedure
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the BTS is already set.
l The BTS communicates properly with the M2000.
l The applications of the BTS are downloaded to the BTS successfully.
Procedure
Query the version information about the 1. In the navigation tree of the NE tab page,
running board of one BTS. choose one BTS.
2. Choose the Query Running Version tab
page.
Before you enter the tab page, the system
automatically queries the version
information about the running board of the
chosen BTS. The query information is
displayed as a list.
3. Click Query.
You can manually refresh the displayed
version information.
Query the version information about the 1. In the navigation tree of the NE tab page,
running board of all BTSs under a BSC. choose a BSC node in the NE > BTS node.
2. Choose Query Running Version tab page.
3. In NE navigation tree, choose one or more
BTSs whose version information about the
running board is to be queried.
4. In Board Type navigation tree, choose one
or more board types.
5. Click Query.
The query result is displayed as a list.
----End
After patches are loaded to the ASN-GW, the patches are in the deactivated state. After the
activate command is sent, the ASN-GW automatically reboots. After the ASN-GW runs the
loaded patches, the patches are activated.
8.3.12.6 Confirming the ASN-GW Software Patch
This task is performed to confirm software patch of the software version designated by the ASN-
GW NE through software management. Only after the confirmation, could the software patch
automatically take effect upon the restart of the ASN-GW.
8.3.12.7 Deactivating the ASN-GW Software Patch
You can use the software management function to deactivate the ASN-GW patches that are
activated but not acknowledged.
8.3.12.8 Deleting the ASN-GW Software Patch
On the M2000, you can use the software management function to uninstall a software patch of
a specified software version of the ASN-GW.
Vxxx (version) indicates a single product or a product series. Thus, a product may have multiple
versions. Each version has a general development plan and can be further categorized into
multiple releases. Rxxx (release) indicates a feature version that provides a series of product
features. A series of feature products may have its own feature version or may be indicated
through special letters or numbers added to a feature version. Cxx indicates a specific sub-version
of features delivered to customers. Bxxy (build) indicates the build versions during the
developing process. SPxx (Service Pack) indicates the version of a patch.
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the ASN-GW is already set.
l The ASN-GW communicates properly with the M2000.
l The software versions of the ASN-GW are downloaded to the ASN-GW successfully.
Procedure
If you load the ASN-GW software versions for the first time, the Upgrade dialog box is displayed. You
can browse the upgrade progress. During the upgrade, the system downloads configuration files and NE
online help to the client to confirm the parameters that need be set by users. After the upgrade is complete,
click OK to view Load Software Parameters Selection.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the ASN-GW is already set.
l The ASN-GW communicates properly with the M2000.
l The applications of the ASN-GW are downloaded to the ASN-GW successfully.
Context
l Each NE can active only one software version. After a software version is activated
successfully, the original version is automatically set to be deactivate.
l If the selected software version is already activated, the system prompts that the activate
operation fails.
Procedure
If you activate the ASN-GW for the first time, the Software dialog box is displayed. You can browse the
upgrade progress. During the upgrade, the system downloads configuration files and NE online help to the
client to confirm the parameters that need be set by users. After the upgrade is complete, click OK to view
Activate Software Parameters Selection.
----End
Prerequisite
l You have logged in to the M2000 client.
l The relay server of the ASN-GW is set.
l The ASN-GW communicates properly with the M2000.
l The software patches of the ASN-GW are downloaded to the ASN-GW.
Procedure
Step 5 Set the parameters in the Load Patch Parameters Selection dialog box.
Step 6 Click OK.
You can query the progress of the task in Immediately Task.
----End
Prerequisite
l You have logged in to the M2000 client successfully.
l The relay server of the ASN-GW is already set.
l The ASN-GW communicates properly with the M2000.
l The applications of the ASN-GW are downloaded to the ASN-GW successfully.
Procedure
Step 2 Select a ASN-GW under the navigation tree on the NE tab page.
----End
Context
Before you activate patches, confirm the patches.
Procedure
----End
Context
NOTE
Only the patches that are activated but not acknowledged can be deactivated. You can delete acknowledged
patches only by deleting patches.
Procedure
----End
Procedure
----End
Prerequisite
l You have logged in to the M2000 client.
l The file server of the NE is configured.
l The NE is properly connected to the M2000.
Procedure
----End
Context
CAUTION
You can perform the operations of Manage NE Licenses only after you purchase the license of
the M2000 License Management function.
The license file is delivered to the NEs through the M2000 client. Then, the license file is
activated by the M2000 client or the LMT so that the NEs obtain the function of license
authorization. The M2000 uses this method to manage the license of the RAN system. For
details, refer to 8.4.1 Managing RAN Licenses.
l Management of the network license
The license control information is directly delivered to the NEs through the M2000 client
so that the NEs obtain the function of license authorization. Currently, the M2000 uses this
method to manage the licenses of the BSC6000 and the BSC32. For details, refer to 8.4.2
Managing Licenses Between NEs.
The license sharing between the NEs is implemented through the management of the
network licenses. You can combine multiple NE groups into a license sharing group. When
the traffic flow on an NE reaches the upper limit and the required value of the license control
items exceeds the applied value, you can deliver the license control information through
an M2000 client to the NEs. In this way, the license utilization of the NEs in the entire
sharing group is improved and the investment is reduced.
The license file is delivered to the NEs through the M2000 client. Then, the license file is
activated by the M2000 client or the LMT so that the NEs obtain the function of license
authorization. The M2000 uses this method to manage the license of the RAN system. For details,
refer to 8.4.1 Managing RAN Licenses.
8.4.1 Managing RAN Licenses
This task is performed to manage RAN licenses, for example, to query, upload, download,
activate, delete, and assign RAN licenses and to query the ESN of an RAN system.
8.4.2 Managing Licenses Between NEs
This describes how to implement license sharing between the NEs in the entire group by
classifying multiple NEs into one group and directly issuing the license control information from
the M2000 client. In this way, the license utilization between the NEs in the entire group is
improved and the investment is reduced.
Context
NOTE
You can manage the RAN licenses only after purchasing the license of the license management function.
This task is performed to activate RAN licenses. RAN licenses can be used only after being
activated. RAN licenses are categorized into RNC licenses and licenses assigned on the NodeBs.
The modes for activating two types of licenses are different.
8.4.1.5 Deleting a RAN License
This describes how to delete the inactivated licenses of the RAN.
8.4.1.6 Querying the ESN of the RAN System
The mobile country code (MCC), mobile network code (MNC), and RNC ID are sequenced and
encrypted to form the ESN of an RAN system. The mobile network code is associated with an
operator. When an RAN system is shared by multiple operators, the RAN system may have
multiple ESNs. This describes how to query the ESN of an RAN system.
8.4.1.7 Distributing RAN Licenses
This describes how to assign the RAN licenses uploaded to the M2000 server to each operator
and set usable licenses for each operator.
Related Concepts
8.1.5 RAN License
Related References
8.6.2 Interface Description: NE Licenses Management
Prerequisite
l You have successfully logged in to the M2000 client.
l The M2000 service is running properly.
l You have successfully obtained the ESN from the RAN.
l You have successfully uploaded the RAN licenses from the M2000 client to the M2000
server. In addition, you have distributed licenses to the NodeBs.
Context
l The sum of a parameter of each NodeB under one RNC must be smaller than the defined
value of this parameter in the control information on a license. For example, If
LQW9ULCE01=128 is defined in the license control information, you can infer that the
sum of the parameter UL CE of each NodeB under the RNC cannot exceed 128.
l You can manually change the assignment of NodeB licenses.
Procedure
Based on user requirements, determine the process to query the licenses.
l To query the RNC licenses, perform the following steps:
1. Choose Software > Browser. The Software Browser window is displayed.
2. Click the NE tab. Choose NE > RNC and select an RNC node.
3. In the right part of the window, click the License tab. The license information on the
RNC node is displayed in the list.
NOTE
In case that the RAN is shared, the information about the operator contains Operator,
ESN, and Primary Operator. In case that the RAN is not shared, the information about the
operator contains only ESN.
– The license information consists of LicenseSN, Activated, CreateDate,
EndDate, and Control. For details of these parameters, refer to 8.6.7 Parameters
for License Information of NodeBs Controlled by an RNC.
3. After selecting a license, you can view the details about how this license is assigned to
each NodeB in the detail table. For details of the parameter description, refer to 8.6.7
Parameters for License Information of NodeBs Controlled by an RNC.
NOTE
In the license list, double-click a license. The Detail dialog box is displayed, informing you about
the detailed license information.
----End
Related Concepts
8.1.5 RAN License
Related References
8.6.7 Parameters for License Information of NodeBs Controlled by an RNC
Prerequisite
l You have successfully logged in to the M2000 client.
l The M2000 service is running properly.
l The valid license file is available.
l You have successfully obtained the ESN from the RAN.
Context
l Each RAN system can upload one RNC license and multiple NodeB license resources. At
a time point, the license distributed to only one NodeB can be activated.
l If the RAN system is shared, the RNC can have multiple ESNs because the operator
information is varies. If a license ID matches any ESN of an RNC when you match the
license ID with ESNs of the RNC, you can infer that the license matches the RNC.
Procedure
Based on the user requirements, determine the process of uploading the licenses.
l To upload the RNC licenses, perform the following steps:
1. Choose Software > Browser. The Software Browser window is displayed.
2. Click the Server tab. Under the Server node, select the RNC node.
3. In the right part of the window, click the License tab.
4. Click From Client To Server. In the displayed Select NE-----1/2 dialog box, select an
RNC.
5. Click Next. In the Select Uploading File-----2/2 dialog box, click Add and select the
license file to be uploaded.
6. Click Select to add the license file to the Select Uploading File-----2/2 dialog box.
7. Click Finish. The progress of uploading the license file is displayed in the FTP Task
tab page at the lower part of the Software Browser window.
l To upload licenses distributed to the NodeBs, perform the following steps:
1. Choose Software > License Management. The License Browser window is
displayed.
2. From the file navigation tree on the left part of the License Browser window, select an
RNC node.
3. Right-click the node and choose Upload > From Client. The Select Uploading
File-----1/1 dialog box is displayed.
4. Click Add. The Select dialog box is displayed.
5. Select one or multiple license resources to be uploaded, and then click Select.
TIP
Hold Shift or Ctrl and select multiple license resources at the same time.
6. In the Select Uploading File-----1/1 dialog box, click Finish.
The upload progress is displayed in the FTP Task tab page at the lower part of the
License Browser window. When the progress bar reaches 100%, you can infer that the
license file is uploaded completely.
NOTE
If you need to stop or delete this task when uploading the license file, select this FTP task, right-
click it, and then choose Stop or Delete from the shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l The M2000 service is running properly.
l You successfully obtain the ESN from the RAN.
l The RNC license is already uploaded to the M2000 server.
Procedure
Step 1 Choose Software > Browser. The Software Browser window is displayed.
Step 2 Click the NE tab. Choose NE > RNC and select an RNC node.
Step 3 In the right part of the window, click the License tab, and then click Download From NM.
The progress of downloading the license file is displayed in the Immediately Task tab page at
the lower part of the Software Browser window. If the progress bar shown in the Percent
column reaches 100%, you can infer that the download of the license file is complete.
----End
Prerequisite
l You have logged in to the M2000 client.
l The M2000 service is running properly.
l You have successfully obtained the ESN from the RAN.
l RAN licenses are assigned to the operators.
Context
An RAN system can have multiple license files. At a particular point in time, only one license
file can be in the active state. The M2000 distributes the values of the license.
Procedure
Based on user requirements, determine the process to activate a license.
l To activate an RNC license, perform the following steps:
1. Choose Software > Browser. The Software Browser window is displayed.
2. Click the NE tab. Choose NE > RNC and select an RNC node.
3. In the right part of the window, click the License tab. The license information on the
RNC node is displayed in the list.
4. Select a license and click Activate. The Activate License window is displayed.
5. Select an operator and set the related parameters, and then click OK.
l To activate a NodeB license, perform the following steps:
l If the set parameter value exceeds its thresholds when you distribute the licenses to the
operators, the Message dialog box is displayed, informing you that a parameter value has
exceeded its thresholds. Click OK and tune the parameter value.
l If a parameter value set for a NodeB owned by an operator exceeds the recommended value
range, the Confirmation dialog box is displayed. Click Yes to continue the license delivery
or click No to cancel the license delivery.
----End
Prerequisite
l You have successfully logged in to the M2000 client.
l The M2000 service is running properly.
l The RAN license is uploaded to the M2000 server.
l You have successfully obtained the ESN from the RAN.
Procedure
Based on user requirements, determine the process to delete a license.
l To delete RNC licenses, perform the following steps:
1. Choose Software > Browser. The Software Browser window is displayed.
2. Click the Server tab. Choose Server > RNC and select an RNC node.
3. In the right part of the window, click the
License tab. The license information on the NE is displayed in the list.
4. Click Delete. In the displayed Confirm dialog box, click Yes.
l To delete NodeB licenses, perform the following steps:
1. Choose Software > License Management. The License Browser window is
displayed.
2. From the file navigation tree on the left part of the
License Browser window, select an RNC node. The detailed license list on the right
part of the window displays the licenses of all the NodeBs on the RNC node.
3. Select a license whose Activated is set to False, and then right-click the license and
choose Delete from the shortcut menu.
NOTE
If you attempt to delete an active license, you must activate another license first. In this case, a
license in the activated state automatically changes to the deactivated state. For details about how
to activate a license, refer to 8.4.1.4 Activating a RAN License.
----End
Prerequisite
l You have successfully logged in to the M2000 client.
l The M2000 service is running properly.
l You have successfully obtained the ESN from the RAN.
Procedure
Step 1 Choose Software > License Management. The License Browser window is displayed.
Step 2 From the file navigation tree on the left part of the License Browser window, select an RNC
node.
The ESN column of the operator information list on the right part of the window shows the ESNs
associated with all the operators.
----End
Prerequisite
l You have logged in to the M2000 client.
l The M2000 service is running properly.
l You successfully obtain the ESN from the RAN.
l The valid license file is already uploaded to the M2000 server.
l The RAN system is shared by multiple operators.
Procedure
Step 1 Choose Software > License Management. The License Browser window is displayed.
Step 2 From the file navigation tree on the left part of the License Browser window, select an RNC
node whose license file is already uploaded to the M2000 server.
The detailed license list on the right part of the window displays all the licenses of the RNC
node.
Step 3 Select a license, right-click it, and choose License Distributed to Operator from the shortcut
menu.
The License Distributed to Operator window is displayed.
Step 4 In this window, assign the number of licenses to each operator.
For details about the parameter description, refer to 8.6.9 Parameters for the Operator.
NOTE
l The number of local cells set by the user must be equal to or more than the number of actual cells. If
the number of preset local cells is less than the number of actual cells, the distribution of NodeB license
is doomed to fail.
l By using the MML command, you can query the parameter information of the NodeB. For example,
you can use the MML command to query the number of cells under a NodeB.
l After modifying the distributed License information of a NodeB, you must redistribute the license
information to all the NEs under this RNC for the modification to take effect.
Step 5 In the NE distribution information list box, select an operator tab. All the licenses distributed to
the operator are displayed in the list box.
Step 6 Double-click a piece of NE license distribution record or right-click the information and choose
Modify from the shortcut menu.
The Modify dialog box is displayed.
Step 7 Redistribute the licences of the NodeB for each operator and deliver the licenses from each
operator to the NEs.
----End
Context
CAUTION
l The function of license sharing management between NEs is available only after you
purchase the license of the M2000 NEs License Sharing Management function.
l You can perform the license sharing management operations between the NEs only after you
are authorized to handle licenses. The operation rights of the license belong to the application
rights of the M2000. For details about the setting of operation rights, see 4.5.10 Assigning
Operation Rights to an OM User.
l The BSC6000 and the BSC32 that are managed by the M2000 support the function. The
versions of NEs that support the support are later versions of BSC6000V900R008C01B040,
G3BSC32V300R008C01B015, and later versions of G3BSC32V300R008C01B015.
l The M2000 currently supports only the license sharing between the NEs of the same type.
Table 8-4 describes the concepts related to the function of license sharing between the NEs.
License sharing Multiple NEs are classified into one group and the license resources
group of all the NEs in this group can be shared.
For example, there are two base station controllers, that is, BSC1 and
BSC2. Each of them has 200 license resources. After you combine
them into a license sharing group, you can adjust the license resources
between them. For example, you can assign 300 to BSC1 and 100 to
BSC2 as long as the total amount does not exceed 200 + 200.
Network license A network license refers to the license control information delivered
by the M2000. The control items in the network license are based on
the sharing-enabled control items in the NE local license file in the
license sharing group.
After network licenses are delivered to NEs, the delivered values of
Allocated and Activated are recorded on the M2000 and on the NE
side respectively. If the network licenses are not successfully delivered
to the NEs because of NE disconnection, the Assigned value and the
Activated value are different.
Concept Description
License list A license list lists the shared license control items supported by a
certain NE type. One NE type corresponds to a license list.
Local value Local values refer to the values of the control items in the local license
file on the NEs.
Available Available value refers to the sum of certain control items in the local
license files of all the NEs in a sharing group. It refers to the available
maximum value of a certain license control item in the sharing group.
Assigned The assigned values are the network values that have been assigned
to the NEs and recorded by the M2000.
Activated The activated values are the network values that have been
successfully issued to the NEs and recorded by the NE side.
license information about the sharing group. The license information includes the Available,
Assigned, and Activated values.
8.4.2.6 Deleting a License Sharing Group
This describes how to delete a license sharing group. You can delete the license sharing groups
that are not required, so as to save system resources. After a license sharing group is successfully
deleted, the status of the NEs in the sharing group changes from centralized management to local
management.
8.4.2.7 Viewing the Sharing Group License Information
This describes how to view the license information in the sharing group. By viewing the license
information in the sharing group, you can learn the information on the available license resources
of the sharing group and each NE in the group, and also the informaiton on the allocated and
activated network licenses.
8.4.2.8 Checking the NE License Information
When you adjust license resources between NEs in the license sharing group, the network
licenses on NEs may differ from the network licenses that are actually allocated to the M2000
server because of NE disconnection. By using the function of checking NE license information,
you can check whether the network licenses on NEs are consistent with the network licenses on
the M2000.
8.4.2.9 Adjusting an NE License in a Sharing Group
When the traffic flow on an NE in a license sharing group reaches the upper limitation and the
required value of a license control item exceeds the applied value, you can regulate the license
resources between NEs without applying for NE licenses. In this way, you can improve the usage
of NE licenses in the entire sharing group and reduce the invested money.
Related References
8.6.2 Interface Description: NE Licenses Management
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
Context
The BSC6000 and the BSC32 managed by the M2000 support the license sharing function. One
NE type corresponds to a license list.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Right-click the NE License Sharing Management node and choose Upload License List from
the shortcut menu.
Step 3 Click to select the license list to be uploaded, and select the NE type corresponding to
the license list from the Select NE Type drop-down list.
You can check the uploaded license list. For details, refer to 8.4.2.2 Viewing a License List.
----End
Postrequisite
After the license list is uploaded to the M2000 server, you can create a license sharing group to
adjust the license resources between the NEs. For details, refer to 8.4.2.4 Adding a License
Sharing Group and 8.4.2.9 Adjusting an NE License in a Sharing Group.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to query or handle licenses. The query or operation rights of the license
belong to the application rights of the M2000. For details about the setting of operation
rights, see 4.5.10 Assigning Operation Rights to an OM User.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Right-click the NE License Sharing Management node and choose View NE License List
from the shortcut menu.
Step 3 Select the NE type to be viewed from the NE Type drop-down list.
The Resource List displays the detailed information about the shared control items supported
by the NE local license file. The information consists of the resource name, resource label, and
the maximum and minimum values of the resource.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
Context
The BSC6000 and the BSC32 managed by the M2000 support the license sharing function. One
NE type corresponds to a license list.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Right-click the NE License Sharing Management node and choose Download License List
from the shortcut menu.
Step 3 Click to select a save path for the license list. Select the NE type corresponding to the
license list from the Select NE Type drop-down list.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 From the navigation tree, select the NEs License Sharing Management node. Right-click the
node, and then choose Add Sharing Group from the shortcut menu.
Step 3 In the Add Sharing Group dialog box, set the name and NEs of a sharing group.
For the detailed description of parameters, see 8.6.10 Parameters for Adding/Modifying
License Sharing Groups.
NOTE
When you set an NE in a sharing group, the NE is not displayed in the Local Controled Nes group box if
you are not authorized to operate the NE. For details on how to add an NE to the management domain of
a user, see 4.5.11 Setting the Managed Domain for an OM User.
Originally, the NEs in a sharing group are in the local management status. After you deliver the related
network licenses to the NEs, their management status changes to the centralized management status. For
more information about the status of local management and centralized management, see 8.4.2 Managing
Licenses Between NEs.
----End
Postrequisite
Based on the traffic status of the NEs in a sharing group, you can adjust licenses among NEs to
maximize the usage of NE licenses, thus protecting your investment. For details, see 8.4.2.9
Adjusting an NE License in a Sharing Group.
Related References
8.6.10 Parameters for Adding/Modifying License Sharing Groups
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
l Related NEs are properly connected to the M2000.
Context
For details about the Available, Assigned, and Activated values, refer to 8.4.2 Managing
Licenses Between NEs.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Right-click a license sharing group to be modified in the navigation tree and choose Modify NE
(s) Sharing Mode from the shortcut menu.
For the detailed description of parameters, see 8.6.10 Parameters for Adding/Modifying
License Sharing Groups.
Step 4 Click OK to close the modification dialog box.
----End
Postrequisite
When NEs are removed from the sharing group, the M2000 automatically delivers the command
to switch the status of the NEs to local management. If the NE status is not successfully switched,
the status of NEs automatically switches to local management after 15 days. You can check
whether the corresponding sharing group is successfully modied through the license task list.
For details, see 8.2.7 Managing Task List.
Related References
8.6.10 Parameters for Adding/Modifying License Sharing Groups
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
Context
NOTE
When you delete a license sharing group, you need to remove all the NEs from the sharing group, and then
delete this empty sharing group.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Remove the NEs in the license sharing group.
1. Right-click a sharing group node in the navigation tree and choose Modify NE(s) Sharing
Mode from the shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to query or handle licenses. The query or operation rights of the license
belong to the application rights of the M2000. For details about the setting of operation
rights, see 4.5.10 Assigning Operation Rights to an OM User.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Click a sharing group or an NE node in the navigation tree and view the corresponding license
information on the right part of the window.
l If you click a sharing group node, the right window displays the network license resources
available to the sharing group (Available), the network licenses that are recorded on the
M2000 server and allocated to the NEs (Assigned), and the network licenses that are recorded
on the NE side and successfully delivered to the NEs ( Activated).
l If you click an NE node, the right window displays the values of the sharing control items
in the NE local license file (Local Value), the network licenses that are recorded on the
M2000 server and allocated to the NEs (Assigned), and the network licenses that are recorded
on the NE side and successfully delivered to the NEs ( Activated).
NOTE
After you click a sharing group node in the navigation tree and deliver the network licenses to the NEs in
the right window, the M2000 and the NE side record the delivered values, that is, the Assigned value and
the Activated value. If the network licenses are not successfully delivered to the NEs because of NE
disconnection, the Assigned value and the Activated value are different.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
l Related NEs are properly connected to the M2000.
Context
NOTE
The M2000 provides the automatic check function. In general, the system automatically checks the
consistency of NE licenses at a specific time every day. For details, refer to 14.9 Modifying NE License
Sharing Management. This part describes only the procedure of manual check.
Figure 8-8 shows the system processing flow during the automatic or manual check.
Update the information about NE The M2000 searches for the local NE licenses and the
licenses network licenses, and updates the NE license resources
and the available resources of the license sharing group
in the M2000 database.
Process Description
Checking the license resources of l The system checks whether the network licenses
the sharing group and NEs allocated to NEs by the license sharing group
outnumbers the actual available resource value. If the
allocated network value outnumbers the available
license resources, the system sends an alarm to the
M2000 server, indicating that the number of used
licenses exceeds the limit. Based on the alarm
information, you can handle the problem. For details,
see ALM-515 The amount of used license's resource
exceeds the threshold.
If the local license files on NEs are updated or out of
date, the network license that are assigned to NEs by
the license sharing group may exceed the actual
available resource value.
l The system checks whether the network license on NEs
is consistent with the network license on the server. If
they are inconsistent, the system sends an alarm to the
M2000 server, indicating that the number of NE
licenses changes. Based on the alarm information, you
can handle the problem. For details, see ALM-514
Changes in the usage of NE license resources.
When you adjust license resources between NEs in the
license sharing group, the network licenses on NEs
may differ from the network licenses that are actually
allocated to the M2000 server because of NE
disconnection.
NOTE
When performing an automatic check, the system checks
whether an NE in the license sharing group is disconnected from
the M2000 for over 15 days. If an NE is disconnected for over
15 days, the system automatically removes the NE from the
group.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Check the information about NE licenses.
l From the navigation tree, select the node of the sharing group. Right-click the node, and then
choose Synchronize NE(s) License from the shortcut menu. Then, check for the license
information about all the NEs in the sharing group.
l From the navigation tree, select the node of an NE. Right-click the node, and then choose
Synchronize NE from the shortcut menu. Then, check for the license information about the
NE.
----End
resources between NEs without applying for NE licenses. In this way, you can improve the usage
of NE licenses in the entire sharing group and reduce the invested money.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to handle licenses. License operation rights belong to the application
rights of the M2000. For details about the setting of user operation rights, see 4.5.10
Assigning Operation Rights to an OM User.
l Related NEs are properly connected to the M2000.
Procedure
Step 1 Choose Software > License Management to open the License Browser window.
Step 2 Click in the navigation tree the sharing group node that an NE belongs to. Then, set the
corresponding network license of the NE in the right part of the window.
The values of control items in the network license must be within the specified NE value range
of license control items. If the entered values are not within the specified value range, you cannot
enter the values on a client. You can know the value range of license control items by checking
the license list. For details, see 8.4.2.2 Viewing a License List.
Step 3 Right-click in the blank area in the right child window for allocating network licenses, and then
choose Distribute from the shortcut menu.
l The M2000 delivers network licenses to the corresponding NEs in the sharing group. The
previously mentioned NEs consist of the NEs whose network licenses are not consistent with
those on the M2000 and the NEs whose network licenses need to be reset.
l You can check whether the network license is successfully delived to an NE by checking the
license task list. For details, see 8.2.7 Managing Task List.
l For the detailed description of the License Browser window, see 8.6.2 Interface
Description: NE Licenses Management.
CAUTION
l When the M2000 delivers a network license to an NE, the system checks whether the
allocated network license exceeds the available resource value of the entire sharing group.
If the allocated network license exceeds the available resource value, the system displays a
message, indicating that the resource value has exceeds the upper limit. In this case, you need
to reset the network license.
l When the M2000 delivers a network license to an NE, the delivery fails if the upper limit of
a control item in the delivered network license is less than the resource value that is already
used by the NE or is more than the resource value that is supported by the NE. You can
identify the problem by checking the detailed task information in the license task list.
----End
Result
After the network license is successfully delivered to the NE through an M2000 client, the NE
is in the centralized management status. In this situation, the local license file of the NE is invalid.
Postrequisite
After network licenses are delivered to NEs, the delivered values of Allocated and Activated
are recorded on the M2000 and on the NE side respectively. If the network licenses are not
successfully delivered to the NEs because of NE disconnection, the Assigned value and the
Activated value are different. In general, the system checks the consistency between NE licenses
at a specific time every day. For details, see 14.9 Modifying NE License Sharing
Management. You can manually check whether the Allocated value is consistent with the
Activated value. For details, see 8.4.2.8 Checking the NE License Information.
Prerequisite
The M2000 server normally operates.
Context
On the M2000 client, you can query the version information about the software installed on the
server. The version information includes the following items:
l The OMC version information, which includes the version numbers of the software and
patch installed on the OMC server.
l The version information about the adaptation layer, which refers to the version number of
the adaptation layer connected to the NEs.
l The ENM version information, which refers to the version number of the components used
for the NE maintenance.
l The version information of the northbound Corba interface, which refers to the version
number of the Corba interface used for the communication between the M2000 and the
network management system.
Procedure
Step 1 Choose the Software > Browser menu item or the shortcut icon .
Open the Software Browser.
Step 2 Select the Server tab. Run the operations according to your requirements.
OMC version information In the structure tree of the file, select the
Server > OMC node.
The primary version and the patch version of
the OMC are displayed in the list box at the
right of the Software Browser window. For
details about the parameters, refer to 8.6.11
Parameters for Version Information on
Software Installed.
NOTE
You can edit the function remarks about the patch
version in the Remark list. The edited remarks can
be saved on the server.
You can only view the remarks about the primary
version. Editing the remarks is not allowed.
Version information about the adaptation In the structure tree of the file, select the NE
layer node under the Server > OMC > Mediation
to check the version information about the
adaptation layer.
The version information about the adaptation
layer of each node is displayed in the list at the
right of the Software Browser window. For
details about the parameters, refer to 8.6.11
Parameters for Version Information on
Software Installed.
OMC version information In the structure tree of the file, select the
Server > OMC > ENM > node.
All the version information about the ENM
installed on the server is displayed in the list
at the right of the Software Browser window.
For details about the parameters, refer to
8.6.11 Parameters for Version Information
on Software InstalledAll the version
information about the.
Version information about the northbound In the structure tree of the file, select the
Corba interface Server > OMC > CorbaNBI > node.
northbound Corba interfaces installed on the
server is displayed in the list at the right of the
Software Browser window. For details about
the parameters, refer to 8.6.11 Parameters
for Version Information on Software
Installed.
----End
Related References
8.6.11 Parameters for Version Information on Software Installed
(3) Content window Lists software version, patches, license, and data of
NEs saved on the server. The M2000 supports
different file types for different NEs. For details, refer
to 8.1.4 Software Management File Types.
Lists software, patches, and data of NEs saved on the
server.
Item Description
Item Description
The software browser under the NEtab is the same as that under the Server tab. For details, refer
to the descriptions of the software browser under the Server tab.
1 Child window of the The license sharing group and its NEs are
navigation tree displayed in the navigation tree.
You can right-click the child window of the
navigation tree and choose correponding menu
items from the shortcut menu to perform related
operations on the sharing group and the license
list.
4 Chid window of the All the executed tasks are displayed in the chid
task list window of the task list after you open the License
Browser window.
l The tasks related to licenses, are displayed in
the license task list. The tasks include the
synchronization of network licenses and the
setting of NE sharing modes.
l The file transfer tasks between the M2000 client
and the server are displayed in the file transfer
list.
You can right-click in the child window of the task
list and choose corresponding menu items from
the shortcut menu to perform related operations on
the executed tasks.
1 Child window of the The RAN NEs are displayed in the navigation tree.
navigation tree You can right-click the child window of the
navigation tree and choose correponding menu
items from the shortcut menu to perform related
operations on the licenses in the RAN system.
2 Child window of After you select an RNC node in the chid window
attributes of the navigation tree, the operator information
and license information in the RAN system are
displayed in the child window of attributes. After
you select a license, the license allocation
information on all the NodeBs in the RAN system
is displayed in the table.
3 Chid window of the All the executed tasks are displayed in the chid
task list window of the task list after you open the License
Browser window.
l The operation tasks related to licenses, are
displayed in the license task list. The tasks
include the synchronization of network licenses
and the setting of NE sharing modes.
l The file transfer tasks between the M2000 client
and the server are displayed in the file transfer
list.
You can right-click in the child window of the task
list and choose corresponding menu items from
the shortcut menu to perform related operations on
the executed tasks.
Related Tasks
8.4.1 Managing RAN Licenses
8.4.2 Managing Licenses Between NEs
Related Tasks
8.3.2.6 Confirming the RNC Software Patch
Table 8-11 lists the parameters that are used to upgrade NE software and patches.
Parameter Description
Related Tasks
8.3.3 Upgrading the SGSN Software and Patch
8.3.4 Upgrading the GGSN Software and Patch
8.3.9 Upgrading the NodeB Software and Patch
8.3.6 Upgrading the MGW Software and Patch
8.3.5 Upgrading the MSC Server Software Patch
The backup files of the NE data are saved in the directory M2000 server /export/home/sysm/
ftproot/NE type (such as RNC)/data type/NE FDN.
In the NE Upgrade Wizard dialog box, select the software to be upgraded Then specify the
operation and version number.
For details of the parameters related to the NodeB software upgrade, refer to Table 8-13.
Upgrade Bootrom and Synchronize Version Synchronize the master software with the
Software backup software. That is, the master and
backup software is of the same version.
Upgrade EPLD and Download the EPLD Download the EPLD to the board. Select
CAN a version number from the drop-down list
of Version.
Upgrade Cold Patch Synchronize Version Synchronize the master software with the
backup software. That is, the master and
backup software is of the same version.
Upgrade Hot Patch Download Patch Download the patch to the NodeB. Select
a version number from the drop-down list
of Hot Patch Version.
Related Tasks
8.3.9 Upgrading the NodeB Software and Patch
Table 8-14 and Table 8-15 list the descriptions of the parameters for querying RAN license
information.
Parameter Description
Activated License status True indicates that the license is already activated,
while False indicates that the license is not activated yet.
Parameter Description
NE Name Name of an NE
Parameter Description
Local Cell(0/0) Number of local cells If this parameter is set to Unlimited, the
number of cells is not limited.
HSDPA RRM(0/0) HSDPA service function items If this parameter is set to Unlimited,
the number of HSDPA services is not limited.
PA[44.8dBm] Number of local cells where the maximum trasmit power is smaller
than 44.8 dBm If this parameter is set to Unlimited, the number of
cells is not limited. The quantity of this parameter is not fixed. The
value in the square brackets is also a variable, which is set
according to the actual situation.
Related Concepts
8.1.5 RAN License
Related Tasks
8.4.1.1 Querying the License Information about the RAN
Parameter Description
Parameter Description
Related Tasks
8.2.8 Setting Parameters of File Transferring
Parameter Description
Parameter Description
Name of an operator
Operator The name of an operator comprises 1 to 30 characters. It does
not include underlines.
Parameter Description
Parameter Description
Parameter Description
Parameters
Parameter Description
Parameter Description
Local Controled Nes Indicates the NEs that do not belong to any sharing group but
support the license sharing function.
NOTE
If you are not authorized to operate related NEs, the NEs are not
displayed in the Local Controled Nes group box.
Group Nes Indicates the NEs that have been added to a sharing group.
Related Tasks
8.4.2.4 Adding a License Sharing Group
8.4.2.5 Modifying a License Sharing Group
Parameters
Version Type Parameter Description
Related Tasks
8.5 Querying Version Information on Software Installed on the Server
9 Configuration Management
The M2000 provides the NE centralized management function. On the M2000 client, you can
run the MML command or start the LMT of an NE to configure the NE. The NEs of class B and
class C do not support the configuration of MML commands.
l Through the MIT browser, the system displays the configuration information of required
objects in the form of trees. The configuration information comprises physical information
and logical information.
l You can use the navigation tree on the MIT browser interface to search information and
set conditions for querying the information of configuration objects. Configuration objects
refer to resource types or resource objects.
On the M2000 client, you can send commands to NEs and view the returned message from the
NEs on the MML command window. The MML command window can display only one
message. When more than one message is returned after M2000 delivers an MML command to
NE, you can query the other messages through the Follow-up Reports Browser window.
The M2000 provides the MML command script function. With this function, you can save a
batch of commands for fulfilling some common tasks or special tasks as a script file. To run
these commands, you just need to execute this script file without carrying out the commands
one by one.
Query Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
Information CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU,
CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC,
CEUB, CRSU
Query CPU Usage CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU,
CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC,
CEUB, CRSU
Reset Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU,
CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC,
CEUB, CRSU
Operation Board
Query E1/T1 Status CXIE, CAIE, CSTU, COIE, CBIE, CBPE, CAPE
Start Manual CMUX, CSPU, CRMU, CHAC, CPCU, CUMB, CNET, CMPU,
Switching CEUB, CRSU
Query Clock Status CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CBPU, CPCU, CIWF, CBIE, CLIU, CBPE, CAPE, CUMB,
CLCB, CNET, CEUB, CRSU
Operation Board
Query Alarms CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM,
CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB,
CLCB, CNET, CMPU, CLPC, CEUB, CRSU
Refresh Alarms CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM,
CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB,
CLCB, CNET, CMPU, CLPC, CEUB, CRSU
Query Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
Information CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU,
CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC,
CEUB, CRSU
Query CPU Usage CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU,
CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC,
CEUB, CRSU
Reset Board CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CIWF, CBIE, CPDU, CLIU,
CBPE, CAPE, CBPF, CAPF, CUMB, CLCB, CNET, CMPU, CLPC,
CEUB, CRSU
Operation Board
Query Alarms CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM,
CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB,
CLCB, CNET, CMPU, CLPC, CEUB, CRSU
Refresh Alarms CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CSTU,
CLAP, CHAC, CBPU, CPCU, COIE, CDSI, CHRB, CLPU, CBFM,
CIWF, CBIE, CPDU, CLIU, CBPE, CAPE, CBPF, CAPF, CUMB,
CLCB, CNET, CMPU, CLPC, CEUB, CRSU
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC Server,
MGW, HLR9820, IWF, BSC, BSC6000, IP Clock Server, and AG.
NOTE
The Confirmation dialog box is displayed with an audible alert when you run some of the MML commands.
Context
l In addition to running an MML command at a time, the system can also run MML
commands in batches. When MML commands are run in batches on multiple NEs, the
system distributes the MML commands to the NEs one by one.
l An MML command may have several messages. When the M2000 runs the commands,
the Common Maintenance shows only the first message. You can view the remaining
messages in the Follow-up Reports Browser window. For details, refer to 9.2.3 Viewing
Follow-Up Reports.
Procedure
Step 1 Select Maintenance > MML Command or click to view the MML Command window.
For details, refer to 9.11.1 Interface Description: MML Command.
Step 2 In the NE window, select the NEs for which an MML command is to be carried out.
The active and standby servers can simultaneously distribute the MML commands related to domain and
dual homing.
----End
Procedure
Step 1 Choose Maintenance > MML Command or click the shortcut icon to display the MML
Command window.
Step 3 On the NEs tab, the MML commands are classified by NE type and displayed in a list. Click
the name of the NE on which the MML command is executed.
----End
Postrequisite
The M2000 supports the export and clear-up of messages. To export or clear messages, perform
the following steps:
1. On the Commands or NEs tab page, right-click an MML command.
2. Choose Export All or Clean from the shortcut menu.
NOTE
l Messages of the MML commands whose Status are Completed can be cleared up.
l When MML commands are being delivered, the options Export All and Clean on the shortcut
menu are unavailable.
l Before you clean up the messages, the Confirmation dialog box is displayed, asking you whether
or not to export messages. If you click Yes, the system saves exported messages in the predefined
path. If you click No, the system does not save the messages already reported.
Context
When the Follow-up Reports Browser window is displayed, the system automatically generates
a cache file for follow-up reports. In the information area located on the lower part of the Follow-
up Reports Browser window, a message is displayed, indicating that the user message is saved
in the file. After the Follow-up Reports Browser is closed, the system automatically deletes
the cache file.
Procedure
NOTE
You can perform the following operations on the displayed messages in Follow-up Reports Browser:
l Click Clear or right-click and select Clear Report to clear all the messages displayed in the output
window.
l Click Save or right-click and select Save as to save the displayed output messages.
l Right-click and select Start Scroll to display the messages through automatic scrolling. Right-click
and select Pause Scroll to stop the scrolling display.
l Right-click and select Report Redirection to save the messages in the specified directory. For details,
refer to 9.2.5 Setting Report Redirection.
Right-click and select Cancel Redirection to disable the redirection.
----End
Related References
9.11.2 Interface Description: Follow-Up Reports Browser
Procedure
Step 1 Choose Maintenance > MML Command or click to view the 9.11.1 Interface
Description: MML Command window.
Step 2 Expand the navigation tree and select an NE.
Step 3 Select the Common Maintenance tab. Right-click in the blank and select Parameter Setting
to view the MML Client Setting dialog box.
Step 4 Set the relevant parameters and click OK.
9.11.7 Parameters for Setting the Attributes of the MML Command Interface lists the
descriptions of the parameters for viewing NE backup files.
NOTE
The settings made in the command output window are still valid after the MML command client resets.
----End
Related References
9.11.7 Parameters for Setting the Attributes of the MML Command Interface
Context
l To save the message obtained before the redirection, refer to 9.2.8 Saving the Result of
an MML Command.
l You can set the size of the redirection report when 9.2.4 Setting the Attributes of the
"MML Command" Interface.
Procedure
Step 1 Choose Maintenance > MML Command or click to view the 9.11.1 Interface
Description: MML Command window.
Step 3 Select Common Maintenance tab. Right-click in the blank area and select Report
Redirection to save the output messages as a file. To cancel the redirection, right-click and
select Cancel Redirection.
----End
Context
When carrying out MML commands one by one, you cannot control the scroll display of
Common Maintenance through this operation.
Procedure
Step 3 In the command output window of the MML command client, select Auto Scroll from the
shortcut menu in Command Maintenance.
Then , each MML messages are automatically scroll displayed.
NOTE
l When carrying out MML commands in batches, select Auto Scroll, and the Common Maintenance
starts scroll display of the MML command reports according to the sequence of the MML commands.
l When carrying out MML commands in batches, if you do not select Auto Scroll, the Common
Maintenance displays only the MML command report that is currently issued. To query the report of
other MML commands, select the MML command to be queried in the Carried out Command List
Window, and the corresponding report will be displayed in the Common Maintenance.
----End
Procedure
Step 1 Select Maintenance > MML Command or click and enter MML Command window.
Step 2 Select an NE in the NE window.
Step 3 In the command input window of MML Command Client, right-click and select Clear History
Command to clear the history commands.
This operation only clears the history command records in the command input window. It does
not affect the history command records in the command output window.
----End
Prerequisite
l You have logged in to the M2000 client as an NE user of the NE.
l The MML Command window is displayed.
l The NE user is bound with the relevant command groups.
Procedure
Step 1 Choose Maintenance > MML Command or click to view the 9.11.1 Interface
Description: MML Command window.
Step 2 Select an NE and an NE version in the MML Command window. The M2000 GUI displays
the MML Command Navigation tree and the command input box.
Step 3 Right-click in the Command Maintenance tab in the MML Command window, and select
Report Redirection.
Step 4 In the displayed Save dialog box, enter a name for the file to save the MML command result.
Run MML commands. The command results are displayed in Common Maintenance and
automatically saved to the specified file.
NOTE
l To stop saving of the command result, right-click in the Command Maintenance tab, and select
Cancel Redirection.
l Right-click in the Common Maintenance tab, and select Save as from the shortcut menu. Then you
can save the results displayed in Common Maintenance to the specified file.
----End
Prerequisite
l You have logged in to the M2000 client.
l The connection between the NEs and the M2000 is functioning well.
Procedure
If the number of configuration data records for an NE exceeds 200, the system browses on a page basis.
Step 3 Right-click the NE, resource type, or resource object, and select Search, or press Ctrl+F to view
the Search box.
The search dialog box is displayed and the search function is enabled.
NOTE
The system can display a maximum of the earliest 100 searching results.
Double-click a record. You can find the resource node on the navigation tree. In the list, the
system displays the configuration information of this node.
During search, click Cancel to stop searching. The searching results, however, are displayed in
Search results.
----End
Related Concepts
9.1.1 Management Information Tree (MIT)
9.1.1 Management Information Tree (MIT)
Related References
9.11.3 Interface Description: MIT Browsing
9.11.8 Parameters for Querying NE MIT Information
Procedure
Step 1 Choose Report > NE Resource Report to view the NE Selection - NE Resource Report
dialog box.
In the NE Resource Report window, you can query, save and print reports.
----End
Context
The wizard applies only to the SGSN, MSC Server, and RNC. For the link types matching the
SGSN, MSC Server, and RNC refer to Table 9-4.
Table 9-4 Link types matching the SGSN, MSC Server, and RNC
SGSN Supports MTP3 link reports, MTP3 route reports, MTP3B link
reports, NSVC reports, and MTP3B route reports.
MSC Server Supports MTP3 link reports and MTP3 route reports.
RNC Supports PPP link reports, MLPPP link reports, PPP Group link
reports, IPPATH link reports, and SCTP link reports.
Procedure
Step 1 Choose Report > Link Report Wizard to view the Create NE Link Report Wizard dialog
box.
Step 3 Select one or more NEs in the navigation tree, and click Next.
In the dialog box listing the link reports, you can query, save and print reports.
----End
Procedure
Step 1 Select Report > NE Statistic Report to view the NE Selection - NE Statistic Report dialog
box.
For details, refer to 9.11.10 Parameters for NE Statistics Report.
In the NE Statistic Report window, you can query, save and print reports.
----End
Related References
9.11.10 Parameters for NE Statistics Report
Procedure
Step 1 Select Report > NE Report to view the NE Selection - NE Report dialog box.
In the NE Reports window, you can query, save and print reports. For real RNC, the function of exporting
RNC IP can be performed in the interface.
----End
Prerequisite
l You have logged in to the M2000 client.
l The NE is connected to the M2000, and the relevant mediation layer is installed.
Context
In general, when the configuration data of an NE has changes, the changed data is automatically
synchronized to the M2000 database. Two automatic synchronization types are available: NE-
triggering automatic synchronization and scheduled-triggering automatic synchronization.
The process of NE-triggering automatic synchronization is as follows:
1. After the configuration data of an NE is added, deleted, or modified, the NE automatically
sends the change notification to the Mediation of the M2000.
2. After the Mediation receives the change notification, it converts the notification to an
automatic synchronization event and then sends the event to the configuration server.
3. After the configuration server receives the event, it determines the synchronization range
according to the description in the event. (The range can be a whole NE or a subtree.)
4. The Mediation layer converts the request and synchronization conditions to the command
that can recognized by the NE.
5. The M2000 sends the command to the NE.
6. The NE handles the command filter message and returns the required NE message.
7. The configuration server receives and parsed the message.
8. The M2000 database and the MIT are updated.
Scheduled-triggering automatic synchronization: On the integrated task management interface,
you can enable the configuration data of an NE to be synchronized on a scheduled basis. You
can set the synchronization time and the period. After the settings are made, the server
synchronizes the configuration data on a scheduled basis. All the configuration data of the NE
are synchronized during the scheduled synchronization. For details, refer to 14.4.2 Modifying
the Synchronization of NE Configuration Data. The process of scheduled-triggering
automatic synchronization is as follows:
1. The server periodically executes the task of synchronizing NEs.
2. Configuration modules can obtain configuration data through the following two ways:
l The server delivers the message of LST to check the configuration data of an NE. After
the Mediation parse the message returned by the NE, it returns all the configuration data
to the configuration modules.
l The server asks the NE to upload configuration data by sending an MML command to
the NE. After the NE receives the command, it exports the data file and then upload the
configuration data to a position specified by the M2000 through the FTP. When the
M2000 receives the command indicating that the configuration data is successfully
uploaded, it gets access to the position and obtains and parses the data file. After the
data file is parsed, the configuration data is saved to the M2000 database. This method
can be applicable NEs such as NodeB, RNC, MSCe, and MSoftX.
3. The configuration modules send the new configuration data to the client and update the
MIT.
CAUTION
l For NEs other than new physical NEs, you should refresh the node in the navigation tree
in the MIT Browser window after each synchronization.
l You are not allowed to manually synchronize an NE if the NE is in the Automatic or Periodic
synchronizing state.
l If an automatic synchronization task is being executed when you trigger automatic
synchronization, the task is added to a queue. The task can be executed only after the
previous synchronization task is executed.
Procedure
Step 1 Select one or more physical NEs on the topology view.
Step 2 Right-click the NEs, and then choose Synchronize CM data or Synchronize CM data in
batches on the displayed shortcut menu.
If you plan to stop the synchronization task, you can right-click the NEs and then choose Cancel
Synchronization on the displayed shortcut menu.
The synchronization progress is displayed on the top left corner of the NE icon. When 100% is
displayed, the synchronization is complete and the progress percentage bar disappears.
----End
Prerequisite
An NE is properly connected to the M2000.
Procedure
Step 1 Select Configuration > MIT Browser or click to view the MIT Browser dialog box.
Step 3 Select the nodes Root Node > NE Type, and then select an NE.
Step 4 Right-click the NE, and select Export to view the Export Configuration Data dialog box.
Step 5 Enter a file name, and select a path for saving the file.
----End
Context
l The import lasts for some time. You can view the related information in the system
information area.
l If the configuration files of multiple PCUs are imported, each PCU processes its
configuration file and generates a result file. The M2000 downloads the result files
generated by the PCUs and merges the files into one. In the merged file, the original result
files are separated by the PCU name.
l The file transfer mode of PCUs can only be active mode.
Procedure
Step 1 Choose Configuration > PCU Integrated Configuration > Import.
Step 2 In the Import PCU config file dialog box, click to choose a file to import.
NOTE
If the PCU NEs contained in the configuration files are still connected, the PCU NEs are displayed in the
Import PCU config file dialog box.
Step 3 Select one or more PCU NEs whose configuration files will be imported.
Step 4 Click Upload.
Step 5 In the Choose a file to save result dialog box, click to select a path to save the PCU result
files.
Step 6 The Information dialog box is displayed, prompting that the file uploading is complete.
----End
Context
l The exportation lasts for some time. You can view the related processes in the system
information area.
l If the configuration files of multiple PCUs are exported, the M2000 merges these files into
one. In the merged file, the original configuration files are separated by the PCU name.
l The file transfer mode of PCUs can be active and passive modes. You can set transfer mode
by 8.2.8 Setting Parameters of File Transferring.
Procedure
Step 1 Choose Configuration > PCU Integrated Configuration > Export.
Step 2 In the Export PCU config file dialog box, click to specify a path to save the exported files.
Step 3 Select one or more PCU NEs whose configuration files will be exported.
Step 4 Click Confirm.
In the system output window, you can check whether the exportation of PCU configuration files
is successful.
----End
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC Server,
MGW, HLR9820, PCU35, PCU6000, BSC, BSC6000, BTS, IP Clock Server, and AG.
NOTE
You can manage inventory data only after purchasing the license of the inventory management function.
Related References
9.11.4 Interface Description: Inventory Management
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
Context
You can add inventory data in batches by means of exporting files. For details, refer to 9.5.3
Importing Inventory Data.
NOTE
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is
displayed.
Step 2 In the navigation tree, right-click an MOC node and choose Add on the shortcut menu.
Step 3 Enter the attribute in the displayed Setting dialog box.
Step 4 Click OK.
The displayed Message box shows whether the operation succeeds. If the operation is successful,
the added inventory data is displayed as a sub-node of the MOC node in the navigation tree.
Step 5 Click OK. The Message box is closed.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is
displayed.
Browse Select the related MO in the navigation tree. Then you can
view the detailed inventory information in a table in the right
pane.
----End
Related References
9.11.11 Parameters for Querying Inventory Data
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is
displayed.
Step 2 In the navigation tree, right-click an NE node or the MOC node and choose Import on the
shortcut menu.
Step 3 In the displayed Open dialog box, select the file to be imported and click Open.
Step 4 In the displayed Setting dialog box, select the import mode.
Overwrite the duplicate name during the If the imported data is the same as the key words
import of an existing record, overwrite the existing
data.
Ignore the duplicate name during the If the imported data is the same as the key words
import of an existing record, use the existing data.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
Procedure
Step 1 Choose Configuration > Inventory Management. The Inventory Management window is
displayed.
Step 2 In the navigation tree, right-click an MO and choose Mod on the shortcut menu.
Step 3 Modify the attribute in the displayed Setting dialog box.
Step 4 Click OK.
The displayed Message box shows whether the modification succeeds.
Step 5 Click OK. The Message box is closed.
----End
Context
The M2000 can synchronize the inventory data at predefined time. For details, refer to 14.4.4
Modifying the Synchronization of Inventory Data.
Procedure
Step 1 Choose Configuration > Inventory Management to view the Inventory Management
window.
Step 2 Right-click the blank area in Table of synchronization progress and choose Add on the shortcut
menu.
Step 3 In the displayed Synchronization dialog box, select the NE to synchronize the inventory data.
You can select multiple NEs.
If the synchronization fails, the Message field in Table of synchronization progress shows Failed.
You can right-click the record and choose Fail details on the shortcut menu to view the reason.
----End
Context
An NE is composed of multiple MOCs. An MOC is composed of multiple MOs. For example,
an RNC is composed of boards and antennas. A board is composed of multiple instances such
as board 1 and board 2. In this example, board and antenna are MOCs. Board 1 and board 2 are
MOs.
Procedure
Step 1 Choose Configuration > Inventory Management to view the Inventory Management
window.
Step 2 Right-click an NE or MO in the navigation tree and choose Export on the shortcut menu.
l If you select an NE, the inventory data of all its MOs is exported.
l If you select an MO, the inventory data of this MO is exported.
Step 3 In the displayed Save dialog box, set the file name, save path, and file type.
l If you export the inventory data of all MOs under the NE, File Type is .txt or .xml.
l If you export the inventory data of a specific MO, File Type is .txt or .csv.
If the system fails to export the inventory data of all MOs under the NE, the Message box shows the reason.
----End
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC
SERVER, MGW, HLR9820, IWF, IP Clock Server,and AG.
9.6.1 Viewing NE Resource States
You can set conditions to view NE resource status. If you have only the browse authority, then
you can browse resource status rather than monitor the status.
9.6.2 Monitoring NE Resource States in Real Time
You can monitor the status of the NEs in real time. Only the users with the monitoring privilege
can perform this operation.
Prerequisite
l You have the related authority.
l You have logged in to the M2000 client as an NE user.
l The mediation software of the NE is installed on both the M2000 server and client.
l The NE is properly connected to the M2000.
l The version of the NE enhanced maintenance is upgraded.
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC
SERVER, MGW, HLR9820, IWF, IP Clock Server,and AG.
Procedure
Step 1 Choose Configuration > State Management > State Browser . The State Management dialog
box is displayed.
9.11.9 Parameters for NE Resource Report lists the descriptions of the parameters for viewing
NE backup files.
Step 3 Expand the Resource Type navigation. Select the type of the resource object.
Step 4 Unfold the NE navigation tree, and select the NE to which these resource objects belong.
To stop the query, click Cancel in the progress prompt box. The queried results are not displayed.
----End
Result
The status information about the queried resource objects is listed in the right part of the Status
Browser dialog box. The total number of resource objects that meet the query conditions is
displayed at the left bottom.
Related Concepts
9.1.3 NE Resource States
Related References
9.11.9 Parameters for NE Resource Report
Prerequisite
l You have the related authority.
l The NE is properly connected to the M2000.
Context
This function is supported by the following NEs: RNC, NodeB, SGSN, GGSN80, MSC
SERVER, MGW, HLR9820, IWF, IP Clock Server,and AG.
The resource status monitoring refers to real-time monitoring tasks. They are valid only for the
activated users. After the client restarts, the monitoring settings become invalid. The settings,
however, remain unaffected after you close the Status Management window.
Procedure
Step 1 The State Management dialog box is displayed.
Step 2 Select the State Browser tab to view the resource status.
Step 3 For details, refer to 9.6.1 Viewing NE Resource States. Select one or more records in the list
of queried results.
Step 4 Right-click the selected records, and select Monitor or click Monitor to start a monitoring task.
Step 5 Select the State Monitor tab. Select a resource object under the Resource Type node in the
navigation tree.
The monitoring tasks on the status of this resource object is listed in the right part of the tab.
Step 6 Select one or more resource status records. You can perform the following operations:
Task Operation
Reset Zoom Right-click and select Resume from the shortcut menu to start
the monitoring task. Alternatively, click Resume.
Suspend a measurement task Right-click and select Suspend from the shortcut menu to
stop the monitoring task. Alternatively, click Suspend.
Delete Right-click and select Delete from the shortcut menu to delete
the monitoring task. Alternatively, click Delete.
9.11.6 Parameters for Monitoring NE Resource States in Real Time lists the descriptions of
the parameters for viewing NE backup files.
----End
Related Concepts
9.1.3 NE Resource States
Related References
9.11.6 Parameters for Monitoring NE Resource States in Real Time
9.11.9 Parameters for NE Resource Report
Prerequisite
l Before starting the CME, users must install the CME software of correct version on the
M2000 client.
l The version of the installed CME must be consistent with that of the NE. Otherwise, you
cannot start the CME.
Context
Only RNC and NodeB support starting the CME.
Procedure
On the main interface of the M2000 client, choose Maintenance > WRAN CME to start the
CME client.
----End
Prerequisite
l Before starting the LMT of an NE, ensure that the correct LMT software corresponding to
the NE is installed on the M2000 client.
l The version of the LMT installed on the M2000 must be the same as that installed on the
NE. Otherwise, the LMT cannot be started.
Context
l If you have bound the user to NE, then the system will automatically log in the LMT using
the user ID of the NE User when starting the LMT, otherwise you should manually input
the user name and password.
l Only when the NE type is NodeB, the M2000 server will serve as LMT's proxy if you start
the LMT from the physical topology.
Procedure
Step 1 Choose Topology > Main Topology. The Main Topology dialog box is displayed.
Step 2 On the physical topology view or under the physical topology navigation tree, select the NEs
whose LMTs need to be started.
----End
Prerequisite
The NE is properly connected to the M2000.
Context
This function is supported by only the BWA, IP device, and IPsec Gateway.
Procedure
On the main interface of the M2000 client, right-click an NE that requires the startup of Telnet,
and then choose Start Telnet from the displayed shortcut menu.
----End
Related Concepts
9.1.4 CBSS Device Panel
Related References
9.11.5 Interface Description: Device Panel
Prerequisite
l The login user has relevant rights.
l The CBSS communicates with the M2000 properly.
Context
To check board types, refer to 9.1.4 CBSS Device Panel.
The functions supported by the CBSC are different from those supported by the CBTS. This
section describes how to query CBSC information. The difference between the operations for
querying CBSC information and those for querying CBTS information is detailed in relevant
steps.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Board Information.
The following functions are available to the CBTS:
Step 4 Check the board information in Query Board Information. For details of the parameter
description of board information, refer to 9.11.12 Parameters for Querying the Board
Information.
Step 5 After the query is complete, save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
----End
Related References
9.11.12 Parameters for Querying the Board Information
Refreshing a Panel
After you log in to the device panel, you need to refresh the panel to obtain the latest NE data
so that the status of the panel is consistent with the actual status.
Prerequisite
The CBSS communicates with the M2000 properly.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Select the entire subrack panel. Right-click the panel, and then choose Refresh.
----End
Resetting a Board
This topic describes how to reset a board.
Prerequisite
l The login user has relevant rights.
l The CBSS communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l For the board that is in active/standby mode, such as CMUX/CRMU/CSPU/CPCU/CHAC,
if you want to perform active/standby switchover, manual switchover is recommended. If
you reset the main board where the full backup of active/standby data is performed, the
standby board resets automatically after the standby board becomes the active board.
l Before you reset the resource board, isolate the board. In this case, new services are assigned
to the board so that the impact on the services is reduced.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Reset
Board.
----End
Prerequisite
l The login user has relevant rights.
l The CBSS communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l This operation is performed when the software of the board is upgraded. If you want to
upgrade the CMUX board, reload and upgrade the standby CMUX, and then start manual
switchover to achieve smooth transition.
l The operation is performed to upgrade versions within a specified range. If you want to
upgrade to other versions not specified, contact Huawei technical support engineers.
l Do not perform manual switchover until five minutes have passed after the standby board
is upgraded to the active board. You should not perform manual switchover if the full
backup of the configuration data on the active/standby board is performed.
l When the system works properly, you must maintain the consistency of the loaded programs
between the active board and the standby board.
CAUTION
The operation may have great impact on the system performance. Do not perform the operation
unless otherwise specified.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Start
Manual Switching.
----End
Prerequisite
l The login user has relevant rights.
l The CBSS communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Check the displayed device panel. If a board has alarms, there are alarms in red on the board.
Step 4 Select the board that has alarms. Right-click the board, and then choose Query Alarms.
----End
Prerequisite
l The login user has relevant rights.
l The CBSS communicates with the M2000 properly.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Select a board. Right-click the board, and then choose Refresh Alarms.
The system synchronizes NE alarm information.
----End
Context
The fault bar displays the specific subrack, slot, and board that have faults. When you stop the
mouse pointer on the fault bar, the bar stops moving.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Select the entire rack panel. Right-click the panel, and then choose Show/Hide Fault Bar.
----End
Context
Legends are categorized into alarm legends and alarm status legends.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Select the entire rack panel. Right-click the panel, and then choose Show/Hide Legend.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Board Version Information.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Query
Subsystem Status.
Step 4 Enter the subsystem number in Subsystem No. of Query Subsystem Status, and then click
OK.
l When you point to the Subsystem No. entry box, you can view the value range of Subsystem
No..
l If you do not type the subsystem number, use the default subsystem number, which is zero.
Step 5 Check the information in Query Subsystem Status. For details of the parameter description of
subsystem status, refer to 9.11.13 Parameters for Querying the Subsystem Status.
----End
Related References
9.11.13 Parameters for Querying the Subsystem Status
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Clock Status.
Step 4 Check the information in Query Clock Status. For details of the parameter description of clock
status, refer to 9.11.14 Parameters for Querying the Clock Status.
Step 5 After the query is complete, save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
----End
Related References
9.11.14 Parameters for Querying the Clock Status
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l At present, only CMUX/CBIE supports the No. 1 subsystem information. Other boards
support the No. 0 subsystem.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query CPU
Usage.
Step 4 Type the number of the subsystem in Subsystem No. of Query CPU Usage, and then click
OK.
l When you point to the Subsystem No. entry box, you can view the value range of Subsystem
No..
l If you do not type the subsystem number, use the default subsystem number, which is zero.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query E1/
T1 Status.
Step 4 Enter the E1/T1 number in E1/T1 No. of Query E1/T1 Status, and then click OK.
l When you point to the E1/T1 No. entry box, you can view the value range of E1/T1 No..
l If no E1/T1 number is entered, all the E1/T1s on the board are queried by default.
l The value range of the E1/T1 number varies with the type of an interface board.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l A signaling point can support a maximum of 4,096 circuits.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query A2
Circuit Status.
Step 4 According to Parameters for querying A2 circuit status, enter parameters in Query A2
Circuit Status, and then click OK.
----End
Related References
9.11.15 Parameters for Querying the A2 Circuit Status
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query PCF
Buffer Occupancy.
You can query the PCF buffer occupancy on the CBPU board and the BSC buffer occupancy
on the CPPU board. For details of the parameter description of buffer occupancy, refer to 9.11.16
Parameters for Querying the PCF Buffer Usage.
----End
Related References
9.11.16 Parameters for Querying the PCF Buffer Usage
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l If the FE link is set to Auto-negotiation Enable, you must ensure that the peer port
connected by the port of the link is operational before you query the FE link status for the
first time. Otherwise, the system displays
Link Not Configured
.
l The FE link status information to be queries consists of:
– Link configuration status
– Link status
– Whether the optical port is available
– Actual operational status of the link
– Link rate
– Link duplex mode
– Whether the link is auto-negotiated
– Link loopback mode
– Link traffic mode
– Interface type at the system side
– Verification type
– BURST length
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query FE
Link Status.
Step 4 Enter the FE port number in Port No. of Query FE Link Status, and then click OK.
l When you point to the Port No. entry box, you can view the value range of Port No..
l If no FE port number is entered, you can infer that all the FE links configured by the BAM
at the slot are queried.
The FE link is available only when the link status is Link Activated and the link running status
is In Service.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query IMA
Link Status.
Step 4 Enter the IMA link number in E1 No. of Query IMA Link Status, and then click OK.
l When you point to the E1 No. entry box, you can view the value range of E1 No..
l A type of interface board has a unique value range.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Check the DSP status.
CAUTION
Do not perform the operation when the DSP is loaded.
1. In the displayed device panel, select a board. Right-click the board, and then choose Query
DSP Status.
2. Enter the DSP number in DSP No. of Query DSP Status, and then click OK.
l By default, the CFMR has 8 DSPs, which are numbered from 0 to 7. The CEVC has 16
DSPs, which are numbered from 0 to 15.
l When you point to the DSP No. entry box, you can view the value range of DSP No..
l If no DSP number is typed, you can infer that the status of all the DSPs on the board is
queried.
3. Check the information in Query DSP Status. For details of the parameter description of
DSP status, refer to 9.11.17 Parameters for Querying the DSP Information.
4. Save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
l When you point to the DSP No. entry box, you can view the value range of DSP No..
l If no DSP number is typed, you can infer that the CPU usage of all the DSPs on the
board is queried.
3. Check the information in Query DSP CPU Usage. For details of the parameter description
of the CPU usage of the DSP, refer to 9.11.17 Parameters for Querying the DSP
Information.
4. After the query is complete, save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
----End
Related References
9.11.17 Parameters for Querying the DSP Information
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Query EVC
Timeslot Occupancy.
Step 4 In Query EVC Timeslot Occupancy, enter the DSP number in DSP No. and the DSP timeslot
number in TimeSlot No.. Then click OK.
l When you point to the DSP No. or TimeSlot No. entry box, you can view the value range of
the DSP No. or TimeSlot No..
l Each DSP has 16 timeslots, which are numbered from 0 to 15. The DSP number must be
entered.
l When you do not enter the DSP timeslot number, you can infer that the occupancy of all the
DSP timeslots is queried.
Step 5 Check the information in Query EVC Timeslot Occupancy. For details of the parameter
description of EVC timeslot occupancy, refer to 9.11.18 Parameters for Querying the EVC
Timeslot Occupancy.
Step 6 After the query is complete, save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
----End
Related References
9.11.18 Parameters for Querying the EVC Timeslot Occupancy
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 Check the chip status of the Modem.
1. In the displayed device panel, select a board. Right-click the board, and then choose Query
IWF Modem Chip.
2. Check the information in Query IWF Modem Chip.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select the CIWF board. Right-click the board, and then choose
Query L Interface Channel.
Step 4 Enter the start channel number and the end channel number in Start Channel No and End Channel
No of Query L Interface Channel, and then click OK.
When you point to Start Channel No and End Channel No, you can see the value ranges of Start
Channel No and End Channel No respectively. For details of related parameters, refer to 9.11.19
Parameters for Querying the L Interface Channel.
Step 5 Check the information in Query L Interface Channel.
----End
Related References
9.11.19 Parameters for Querying the L Interface Channel
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l After the isolated board or the main control board is started after being reset, the isolation
status is cancelled automatically.
NOTE
The CPCU is the main control board for the CBPU, the CRMU for the CPPU and the CIWF, and the
CMUX for the CEVC.
l Before you set board isolation, the system prompts you to confirm execution. Usually, the
last resource board, such as CFMR, CEVC, CBPU, and CPPU, cannot be isolated. If you
try to block the last resource board non-forcedly, the system displays a failure notice
suggesting that you select forced isolation.
l If you perform the non-forced isolation for the last available CIWF board under the same
signaling point when you set board isolation, the system will display a failure notice
suggesting that this is last available CIWF board.
l If the CFMR, CEVC, CBPU, and CPPU boards are isolated, new calls are assigned to and
handled on another board of the same type that is not isolated in the same subrack.
l If the CIWF board is isolated, new calls are assigned to and handled on the CIWF board
that is not isolated at the same signaling point.
CAUTION
After a board is isolated, new calls cannot be connected to the board. The calls that are connected
before the isolation, however, are not affected. Do not use the command unless otherwise
specified.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Set Board
Segregate or Cancel Board Segregate.
Step 4 If you choose Set Board Segregate, you need to set related parameters.
1. Select YesNo in Forced Flag of Set Board Segregate, and then click OK.
Forced segregation means that the resource board of the same type requires segregation
even if the board to be segregated is the only available board in the system.
2. In the Confirm dialog box, click OK.
Step 5 Check the information in Set Board Segregate or Cancel Board Segregate.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l If the IMA link is in the block status, you can still perform "Block IMA Link" successfully
without affecting the system.
l If the IMA link is in the unblock status, you can still perform "Unblock IMA Link"
successfully without affecting the system.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device board, select a panel. Right-click the board, and then choose Block IMA
Link or Unblock IMA Link.
Step 4 Enter the E1 number in E1 No. of Block IMA Link or Unblock IMA Link, and then click
OK.
When you point to the E1 No. entry box, you can view the value range of E1 No..
Step 5 In the Confirm dialog box, click OK.
Step 6 Check the information in Block IMA Link or Unblock IMA Link.
Step 7 Save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l The originating signaling point is configured.
l A signaling point can support a maximum of 4,096 circuits.
l After you reset the circuit that is in the block status, the circuit changes to the idle status.
CAUTION
Performing this operation may result in clearing the calls in circuits. Thus, do not perform this
operation unless otherwise specified.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Reset A2
Circuit.
Step 4 According to Table 9-5, enter parameters in Reset A2 Circuit, and then click OK.
Parameter Description
Name
OPC Indicates the originating signaling point code where the A2 circuit is located.
Start Circuit Indicates the start circuit number and the end circuit number.
No. When you point to the Start Circuit No. and End Circuit No. entry boxes,
End Circuit you can view the value range of the two entry boxes respectively.
No. The start circuit number must not be greater than the end circuit number.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
ATM Port Status.
Step 4 Enter the subslot number and the slot number respectively in Sub Slot No. and Slot No. of Query
ATM Port Status, and then click OK.
When you point to the Sub Slot No. and Slot No. entry boxes, you can view the value range of
the two entry boxes respectively.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select the CIWF board. Right-click the board, and then choose
Query GCKP Clock Information.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Satellite Card Information.
Step 4 Check the information in Query Satellite Card Information.
Step 5 Save the query result or close the window.
l Click Save to save the query result as a .txt file.
l Click Close to close the window.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
GCKP Card Information.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Reset
GCKP Card.
----End
Prerequisite
l The login user has relevant rights.
l The CBSC communicates with the M2000 properly.
Context
l To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
l This operation supports the upgrade between specified versions. That is, switchover
commands are used to upgrade some versions. Before the upgrade, you should contact
Huawei technical support engineers and ensure that software is loaded from the BAM.
l During normal operation, ensure that the same programs are loaded on both the active board
and the standby board.
l When service capability decreases, perform this operation if you are certain of clock signal
problems.
l Before the switchover, ensure that the original standby GCKP board is adjusted to use the
same clock source as the original active board does. In addition, ensure that the clock source
works properly.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 Select an NE in the left navigation tree, and then select the rack where the board to be operated
is located.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Start GCKP
Manual Switching.
----End
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
NOTE
l There are two activation modes: automatic and manual. If the board ID for automatic activation is
not selected, the software or data is only loaded but not activated for the BTS.
l The service and maintenance of the BTS are not affected if the software or data is not activated.
l Software activation may result in the reset of corresponding boards and interruption of service. The
activation of configuration data or INI files does not reset the BTS, but changes the configuration of
the BTS according to the configuration of the activation file. The impact on the service varies with
the configuration files.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Download
BTS Software or Data or Activate BTS Software or Data.
1. When you choose Download BTS Software or Data, the Download BTS Software or
Data dialog box is displayed.
a. Enter or select related information in BTS ID, Object Type, Software Type, and ID
of Board To be Auto-activate.
b. Click OK to view the Confirm dialog box.
c. Click OK to upgrade the BTS. For details of the parameters, refer to 9.11.20
Parameters for Downloading the BTS Software or Data.
2. When you choose Download BTS Software or Data, the Download BTS Software or
Data dialog box is displayed.
a. Enter or select related information in BTS ID, Board ID, Object Type, and Software
Type.
b. Click OK to view the Confirm dialog box.
c. Click OK to upgrade the BTS. For details of the parameters, refer to 9.11.20
Parameters for Downloading the BTS Software or Data.
----End
Related References
9.11.20 Parameters for Downloading the BTS Software or Data
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
CAUTION
l Blocking the BTS CPM may cause multiple sector carriers to be deleted and interrupt the
service borne by this CPM. Perform this operation only when necessary.
l Calls cannot be connected in the case of "Delay block" or "Idle block".
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Block BTS
CPM Board or Unblock BTS CPM Board.
1. When you choose Block BTS CPM Board, the Block BTS CPM Board dialog box is
displayed.
a. Enter values in BTS ID and Board ID, and then select Block Type from the drop-
down list.
b. Click OK to view the Confirm dialog box.
c. Click OK to block the board. For details of related parameters, refer to 9.11.21
Parameters for Blocking the BTS CPM Board.
2. When you choose Unblock BTS CPM Board, the Unblock BTS CPM Board dialog box
is displayed.
a. Enter values in BTS ID and Board ID.
b. Click OK to unblock the board. For details of related parameters, refer to 9.11.21
Parameters for Blocking the BTS CPM Board.
----End
Related References
9.11.21 Parameters for Blocking the BTS CPM Board
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
NOTE
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Current Time of BTS.
The Query Current Time of BTS dialog box is displayed.
The local UTC time of the BTS is displayed at the BTS Current Time parameter line.
----End
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Ethernet IP.
The Query Ethernet IP dialog box is displayed. For details of the parameters in the dialog box,
refer to 9.11.22 Parameters for Querying the BTS Ethernet IP.
At the Local O&M IP parameter line, the IP address of the BTS is displayed. At the Reverse
Maintenance Status parameter line, the inverse maintenance status is displayed.
----End
Related References
9.11.22 Parameters for Querying the BTS Ethernet IP
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Query FE
Port Information.
The Query FE Port Information dialog box is displayed. For details of the parameters in the
dialog box, refer to 9.11.23 Parameters for Querying the FE Port Information.
----End
Related References
9.11.23 Parameters for Querying the FE Port Information
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
NOTE
The queried filber length refers to the actual length between the primary rack and the ODU.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a board. Right-click the board, and then choose Query
Fiber Length.
----End
Resetting a BTS
When a BTS works improperly, you can reset the BTS on the device panel. This topic describes
how to reset a BTS.
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
To know the board types that support the operation, refer to 9.1.4 CBSS Device Panel.
CAUTION
Resetting the BTS may affect services. Thus, you should reset the BTS with caution.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
l Choose Configuration > Device Map.
l Right-click an NE node in the physical topology navigation tree or the physical topology
view, and then choose Device Panel from the displayed shortcut menu.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 In the displayed device panel, select a panel. Right-click the panel, and then choose Reset
BTS.
The Reset BTS dialog box is displayed.
Step 4 In the BTS ID entry box, enter the ID of the BTS.
Step 5 Click OK.
The Confirm dialog box is displayed.
Step 6 Click OK to start resetting the BTS.
When you invoke the CORBA interface to reset the board, a dialog box is displayed to show the
result.
l If the board is reset successfully, the system displayed a dialog box to notify you of the
successful result.
l If the board fails to be reset, the system displays specific reasons. The reasons may be that
you click Cancel to disrupt the resetting process or that CORBA fails to be invoked.
----End
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
The maintenance of environment monitoring units is only applicable for the EMUA board.
CAUTION
Resetting the environment monitoring board may affect services. Thus, you should reset the
EMUA with caution.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 On the displayed device panel, right-click the EMUA board and then choose relevant items to
operate and maintain the EMUA.
For details on how to operate and maintain the EMUA, refer to Table 9-6.
Operation Remarks
Query Board Information On the device panel, you can invoke this operation to
check the detailed information on the EMUA.
Operation Remarks
Query EMUA Temperature Range On the device panel, you can invoke this operation to
check the temperature range of the EMUA.
Set EMUA Temperature Range On the device panel, you can invoke this operation to
set the humidity range of the EMUA.
Query EMUA Humidity Range On the device panel, you can invoke this operation to
check the humidity range of the EMUA.
Set EMUA Humidity Range On the device panel, you can invoke this operation to
set the humidity range of the EMUA.
Query EMUA Switch Extended On the device panel, you can invoke this operation to
Port check the switch extended port of the EMUA.
Set EMUA Switch Extended Port On the device panel, you can invoke this operation to
set the switch extended port of the EMUA.
Query EMUA Analog Extended On the device panel, you can invoke this operation to
Port check the analog extended port of the EMUA.
Set EMUA Analog Extended Port On the device panel, you can invoke this operation to
set the analog extended port of the EMUA.
Reset Board When the EMUA works improperly, you can invoke
this operation on the device panel to reset the EMUA.
Query Alarm On the device panel, you can invoke this operation to
check the alarms of the EMUA.
Refresh Alarm On the device panel, you can invoke this operation to
refresh alarms of the EMUA and to obtain the latest
alarm information.
----End
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
The maintenance of power management units is applicable only for the PMU.
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 On the displayed device panel, right-click the PMU panel and then choose relevant items to
operate and maintain the PMU.
For details on how to operate and maintain the PSU, refer to Table 9-7.
Operation Remarks
Query Board Version Information On the device panel, you can invoke this operation
to check the detailed information on the PMU.
Query BTS Power Supply Unit On the device panel, you can invoke this operation
to check the detailed information on the AC/DC
power supply units of the BTS.
Query AC Alarm Threshold On the device panel, you can invoke this operation
to check the mains alarm threshold.
Set BTS AC Alarm Threshold On the device panel, you can invoke this operation
to set the mains alarm threshold.
Query BTS Battery Parameter On the device panel, you can invoke this operation
to check the parameters of BTS storage batteries.
Set BTS Battery Parameter On the device panel, you can invoke this operation
to set the parameters of BTS storage batteries.
Query BTS Environment Temperature On the device panel, you can invoke this operation
Alarm Threshold to check the alarm threshold of environment
temperature.
Set BTS Environment Temperature On the device panel, you can invoke this operation
Alarm Threshold to set the alarm threshold of environment
temperature.
Query BTS Environment Humidity On the device panel, you can invoke this operation
Alarm Threshold to check the alarm threshold of environment
humidity.
Set BTS Environment Humidity Alarm On the device panel, you can invoke this operation
Threshold to set the alarm threshold of environment
humidity.
Operation Remarks
Query the Alarm Information of the On the device panel, you can invoke this operation
PMU Environment Monitoring to check the alarm information on the PMU
Extended Port environment monitoring extended port.
Set the Alarm Information of the PMU On the device panel, you can invoke this operation
Environment Monitoring Extended Port to set the alarm information on the PMU
environment monitoring extended port.
----End
Prerequisite
l The login user has relevant rights.
l You have logged in to the M2000 client.
l NEs communicate with the M2000 properly.
Context
The maintenance of DC power supply units is applicable only for the PSU (DC/DC).
Procedure
Step 1 Open the Device Panel window.
You can use either of the following ways to open the Device Panel window.
Step 2 In the navigation tree, select the rack that the board is located. The device panel is displayed in
the right part of the window.
Step 3 On the displayed device panel, right-click the PSU (DC/DC) and then choose relevant items to
operate and maintain the PSU (DC/DC).
For details on how to operate and maintain the PSU (DC/DC), refer to Table 9-8.
Operation Remarks
Query Power Supply On the device panel, you can invoke this operation to check the
Parameters parameters of power supplies.
Operation Remarks
Query Alarm On the device panel, you can invoke this operation to check the
alarms of the PSU (DC/DC).
Refresh Alarm On the device panel, you can invoke this operation to refresh
the alarms of the PSU (DC/DC) and to obtain the latest alarm
information.
----End
This topic describes the parameters for querying the board information.
9.11.13 Parameters for Querying the Subsystem Status
This topic describes the parameters for querying the subsystem status.
9.11.14 Parameters for Querying the Clock Status
This topic describes the parameters for querying the clock status.
9.11.15 Parameters for Querying the A2 Circuit Status
This topic describes the parameters for querying the A2 circuit status.
9.11.16 Parameters for Querying the PCF Buffer Usage
This topic describes the parameters for querying the PCF buffer usage.
9.11.17 Parameters for Querying the DSP Information
this topic describes the parameters for querying the DSP information.
9.11.18 Parameters for Querying the EVC Timeslot Occupancy
This topic describes the parameters for querying the EVC timeslot occupancy.
9.11.19 Parameters for Querying the L Interface Channel
This topic describes the parameters for querying the L interface channel.
9.11.20 Parameters for Downloading the BTS Software or Data
This topic describes the parameters for downloading the BTS software or data.
9.11.21 Parameters for Blocking the BTS CPM Board
This topic describes the parameters for blocking the BTS CPM board.
9.11.22 Parameters for Querying the BTS Ethernet IP
This topic describes the parameters for querying the BTS Ethernet IP address.
9.11.23 Parameters for Querying the FE Port Information
This topic describes the parameters for querying the FE port information .
(1)NE window. All the NEs that support the delivery of MML commands are displayed on the
topology view according to the topology structure of the NEs.
(2)MML command navigation tree window. The MML command navigation tree of a specific
NE is displayed.
(3)Command output window, which has the Common Maintenance tab, Historical
Commands tab, and Help Information tab. The Common Maintenance tab displays the
delivered commands and command results. The Historical Commands tab lists the executed
commands and their parameter configuration. The Help Information tab displays the help
information of MML commands.
(4)Command display window, which displays the executed commands and their parameter
configuration.
(5)This window displays all the executed MML commands and the number of the executed
commands for each NE.
(6)Command input window, which displays Historical Command, Command Input and
Command Parameter. Historical Command displays the latest 20 historical commands and
the related parameter configuration.
NOTE
For some MML commands, the M2000 may generated multiple reports for one MML command. In this
situation, the Common Maintenance tab displays only the first report. You can view the other reports in
the Follow-Up Report Browser window.
As shown in the above figure, the Follow-Up Reports Browser interface is divided into three
parts.
(1) is an navigation tree where you can select one or more NEs.
(2) is the output window of the messages. When the M2000 receives the follow-up messages returned by the
selected NEs, the prompt information is displayed in the output window of messages and at the right corner of
the client.
(3) displays buffer file name and path of the follow-up reports.
(4) are the operation buttons that you can click to save follow-up reports, clear follow-up reports, and close the
window.
Related Tasks
9.2.3 Viewing Follow-Up Reports
2 Search area You must press Ctrl+F to display this area. For descriptions of
the parameters, refer to 9.11.8 Parameters for Querying NE
MIT Information.
Related Concepts
9.1.1 Management Information Tree (MIT)
Related Tasks
9.3.1 Viewing NE MIT Information
SN Name Description
Related Tasks
9.5 Managing Inventory Data
(1) NE window. The window displays all the NEs of the CBSS in topology according to the topology structure
of the CBSS.
(2) Device panel window. The window displays the status of all the boards on the rack specified by the CBSS.
(3) Fault bar. The fault information on the board is listed and rolled on the fault bar.
(4) Legend window. The window displays the meanings of board colors and icons on the device panel.
Related Concepts
9.1.4 CBSS Device Panel
Related Tasks
9.10 Operating CBSS Device
Specific resource object state The state of a resource object is visible only when it is
started. The states vary depending on the types of the
resource objects. For details, refer to 9.1.3 NE
Resource States.
Related Tasks
9.6.2 Monitoring NE Resource States in Real Time
Table 9-12 Descriptions of the parameters for configuring MML Command Client
Parameter Value range Description
Max Report 100-20000 Maximum lines of the output the screen displays in the
Lines Default value: Common Maintenance tab for an MML command.
When lines of the output messages exceed this value,
the client displays only the output messages reported
recently.
Max Log file 20-50 The size of the reports redirection file.
Size (MB) Default value: When the size of the redirection file reaches this value,
the system creates automatically a new file under the
same directory to save the received messages. The file
is named YYYYMMDD.TXT.
YYYY, MM and DD are respectively the current year,
month and date.
Max Report 1-5 The size of the MML command output messages to be
Buffer Size Default value: displayed in Common Maintenance.
(MB) When the size of the output messages exceeds this
value, the client displays only those generated
recently.
NOTE
When the messages saved in the system nearly accounts for
70% of the Max Report Buffer Size set by the user, a
warning is displayed, prompting you to clear up memories.
If the amount of messages saved in the system already reach
the preset Max Report Buffer Size,the system prompts you
to clear the messages.
Operation l Script Mode l If you select Script mode, the selected commands
Mode l Multiwindow are not delivered to the NE. Instead, they are used
Mode for creating script tasks. If you do not select this
mode, the selected commands are delivered to the
NE.
l If you select Multiwindow Mode, you can open up
to three MML Command windows at the same
time.
If the parameter setting is changed, you need to open
the MML Command window again.
Related Tasks
9.2.4 Setting the Attributes of the "MML Command" Interface
Key words The name should not be null. The characters contained in the name
It is composed of up to 64 of the to be searched.
characters, excluding special
characters such as `, -, !, @, #,
$, %, ^, &, *, +, \, |, ;, ', :,
", , , ., ?, /, and the Chinese dash.
Case sensitive l Selected: case sensitive. The key words entered for searching
l Cleared: case insensitive. an are case sensitive.
Related Concepts
9.1.1 Management Information Tree (MIT)
Related Tasks
9.3.1 Viewing NE MIT Information
Table 9-14 Parameters for querying the resource status of the NEs
Parameter ID Description
Related Concepts
9.1.3 NE Resource States
Related Tasks
9.6.1 Viewing NE Resource States
9.6.2 Monitoring NE Resource States in Real Time
Related Tasks
9.3.4 Viewing NE Statistics Reports
Parameter Description
Parameter Description
Dec
Related Tasks
9.5.2 Querying Inventory Data
For details of the parameters for querying the board information, refer to Table 9-16.
NOTE
Parameter Description
Name
Operational If the operational status is activated, you can infer that the board operates
Status properly. If the operational status is not activated, you can infer that the
board is faulty.
Management If the management status is activated, you can infer that the board can be
Status managed. If the management status is deactivated, you can infer that the
board cannot be managed. After the board is isolated, the management
status of the board is deactivated.
Parameter Description
Name
Related Tasks
9.10.1.1 Querying the Board Information
For details of the parameters for querying the subsystem status, refer to Table 9-17.
NOTE
Parameter Description
Name
Subsystem No. Generally, a board has only the default subsystem number as 0. Currently,
only CMUX and CBIE support the query of the subsystem whose number
is 1.
Operational If the operational status is activated, you can infer that the board operates
Status properly. If the operational status is not activated, you can infer that the
board is faulty.
Management If the management status is activated, you can infer that the board can be
Status managed. If the management status is deactivated, you can infer that the
board cannot be managed. After the board is isolated, the management
status of the board is deactivated.
Parameter Description
Name
Related Tasks
9.10.2.2 Querying the Subsystem Status
NOTE
The displayed parameters after the query vary with board types or NE versions.
CMUX This command can be used to query the current status of the clock reference sources
of the CMUX.
As the main control board, the CMUX provides the 32 MHz/8 kHz clock for the
boards in the subrack. The clock reference source, which serves as the reference
clock of the CMUX, provides the 32 MHz/8 kHz clock. An appropriate clock
reference source can be selected according to the current status of the reference
sources and actual requirements.
The CMUX can select the following clock reference sources:
l Two TDM 8 kHz clock reference sources (E1 line clock) provided by CBIE/
CXIE/CAIE
l One 8 kHz clock reference source (line clock of ATM switch optical port)
provided by the local optical port
l Two SDH 8 kHz clock reference sources provided by the CSTU
l One 8 kHz clock reference source provided by the local crystal oscillator; one 8
kHz clock reference clock provided by the GCKP
CBIE/ The CXIE/CBIE provides two 2 MHz reference clocks through the board panel and
CXIE two 8 kHz clocks through the back board. Using this operation, you can know
whether these clocks are enabled or disabled.
The query result includes the selection situation of the IMA clock source. The result
also includes the status of 32 MHz and 8 kHz clocks exported to the CBIE/CXIE
from the CMUX.
CAIE/ The clock status information that can be queried for the CAIE is the same as that
CBIE/ for the CBIE and the CXIE. The only difference is that the CAIE does not have the
CXIE IMA clock source.
CFMR The purpose of querying the clock status of the CFMR is to check whether the 32
MHz/8 kHz clocks, internal clocks, and RFN clocks work properly.
CEVC/ The purpose of querying the clock status of the CEVC/CLCB is to check whether
CLAP the 32 MHz/8 kHz external clocks work properly.
CSPU The purpose of querying the CSPU is to check whether there is any fault with 8
kHz clock and whether the status of RFN pulses and RFN synchronization
information elements is proper.
CSTU Querying the CSTU involves querying the status of CSTU SDH Clock Source,
Returned SDH8K Clock Source, Returned TDM8K Clock Source, and Returned
Clock Group.
l CSTU SDH Clock Source can be 8 kHz optical port clock, TDM 32 MHz clock,
or SDH 19.44 MHz clock.
l Returned SDH8K Clock Source must be 8 kHz optical port clock.
l Returned TDM8K Clock Source can be OUT_CLK_FMR2M1,
OUT_CLK_FMR2M2, OUT_CLK_FMR2M3, OUT_CLK_FMR2M4,
OUT_CLK_FMR2M5, OUT_CLK_FMR2M6, OUT_CLK_FMR2M7, or
OUT_CLK_FMR2M8.
l Returned Clock Group can be 0 (group 1) or 1 (group 2).
Related Tasks
9.10.2.3 Querying the Clock Status
For details of the parameters for querying A2 circuit status, refer to Table 9-19.
NOTE
Parameter Description
Name
OPC Indicates the originating signaling point code where the A2 circuit is located.
Start Circuit Indicates the start circuit number and the end circuit number.
No. When you point to the Start Circuit No. and End Circuit No. entry boxes,
you can view the value range of the two entry boxes respectively.
End Circuit
No. The start circuit number must not be greater than the end circuit number.
The number of circuits for each operation cannot exceed 256.
Related Tasks
9.10.2.6 Querying the A2 Circuit Status
For details of the parameters for querying PCF or BSC buffer usage, refer to Table 9-20.
NOTE
Parameter Description
Name
Related Tasks
9.10.2.7 Querying the PCF Buffer Usage
For details of the parameters for querying the DSP information, refer to Table 9-21.
NOTE
Parameter Description
Name
DSP Status The DSP status can be queried even if the DSPs are faulty. The DSP status
cannot be queried only when the board cannot communicate with the BAM.
If the DSP functions well, the DSP status is displayed as "working properly".
CPU Usage When DSP resources are not used, the CPU usage of the DSP on the CFMR
is not zero by default. The CPU usage of the DSP on the CEVC is zero by
default. If other value except the default value is queried, you can infer that
services are operational on the DSP.
If the DSP is in the loaded or faulty state, the CPU usage of the DSP cannot
be queried.
Related Tasks
9.10.2.10 Querying the DSP Information
NOTE
Timeslot No. Each DSP has 16 timeslots, which are numbered from 0 to 15.
Related Tasks
9.10.2.11 Querying the EVC Timeslot Occupancy
NOTE
Related Tasks
9.10.2.13 Querying the Modem Information
For details of the parameters for downloading the BTS software or data, refer to Table 9-24.
Related Tasks
9.10.3.1 Downloading/Activating the BTS Software or Data
For details of the parameters for blocking the BTS CPM board, refer to Table 9-25.
Related Tasks
9.10.3.2 Blocking/Unblocking the BTS CPM Board
Related Tasks
9.10.3.4 Querying a BTS Ethernet IP
Related Tasks
9.10.3.5 Querying the FE Port Information
10 Data Management
M2000The M2000 provides the function of managing NE data and NM data. The management
of NM data includes manually or periodically backing up NM data, viewing NM backup files.
The management of NE data includes manually or periodically backing up NE data, viewing
NE backup files, and restoring NE data. The M2000 also provides the function of collecting NM
log files.
Related Tasks
10.2.2 Viewing NE Backup File
Related References
10.5.5 Parameters for NE Backup File
You can back up the NE data in two ways: the periodic backup and the manual backup. When
a backup task is performed, a backup file is generated on the M2000 server, regardless of the
manual or periodic backup.
The maximum number of NE backup files stored on the server is determined by the M2000
configuration file. At present, a maximum of seven backup files can be stored on 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 (for example: RNC)/data type/NE FDN.
NOTE
l For the CG, all M2000 users are considered as the user named M2000.
l Before backing up the CG data, log in to the LMT and authorize the CDR querying or browsing
privilege to the M2000 user of the CG.
Related Tasks
10.3.2 Viewing NM Backup File
Related References
10.5.6 Parameters for NM Backup File
By using this information, you can locate faults. The collected information includes:
l Trace files on the client, for example, Client_DebugTrace.
l Java virtual machine thread stack and lock state in client, for example,
Client_ThreadStackDump.txt
l Trace files on the server, for example, iMAP.root.trace (to store the current trace files)
and imap_stacks.20070206.170237.trace (to store the historical trace files collected
before the NM log files)
l Core files on the server, for example, core.imapsvcd.0.21221.1170824184.stack
l File of alarm NE synchronization number, for example, FMSyncNo
l The pstack file, for example, imap_stacks.20070207.155817.trace.
l Information about the Sybase, for example, SybaseConfig.zip, SybaseVersion.zip, and
SYBLog.20070206.171040.zip.
Related Tasks
10.4 Collecting NM Log File
Related References
10.5.3 Parameters for Collecting NM Logs Parameters
Prerequisite
l You have logged in to the M2000 client.
l The FTP server is configured.
l You are authorized with the relevant privileges.
Context
For manual backup, the backup files are named BAKDATA+current time. For details, refer to
the glossary and acronyms.
The M2000 server acts as the FTP server to connect the client and NEs.
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > System Backup to view the Backup Management dialog box.
l If you select an NE with sub-NEs, for example, if you select RNC, the system prompts you
whether to back up the data of all the sub-NEs. You can also select sub-NEs of this NE to
back up the data.
Step 4 Click Back up.
Click Yes in the displayed Confirm dialog box.
----End
Result
When the backup task starts, you can view the execution progress and the detailed information
in the Task List in the lower part of the Backup Management window.
Prerequisite
l You have logged in to the M2000 client.
l The FTP server is configured.
l You are authorized with the relevant privileges.
l The backed up NE files exist on the server.
Procedure
Step 1 Choose Maintenance > System Backup.
The Backup Management window is displayed.
Step 2 Click the NE Backup List tab.
Step 3 Expand the navigation tree and select an NE.
Click Refresh to refresh the backup file list.
If you select an NE with sub-NEs, for example, if you select RNC, the backup file list displays
only the backup files of the RNC, but not those of the sub-NEs.
If you select a subnet, the backup file list displays the backup files of all the NEs in this subnet.
10.5.5 Parameters for NE Backup File lists the descriptions of the parameters for viewing NE
backup files.
----End
Related Concepts
10.1.1 NM Backup Data
Related References
10.5.5 Parameters for NE Backup File
Prerequisite
l You have logged in to the M2000 client.
l The FTP server is configured.
l You are authorized with the relevant privileges.
l The NE data is backed up on the server.
Context
IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > System Backup to view the Backup Management dialog box.
Step 5 Choose Restore from the shortcut menu or click Restore in the dialog box.
CAUTION
The NE restarts after you perform the restore operations.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized with the relevant privileges.
Procedure
Step 1 Choose Maintenance > System Backup to view the Backup Management dialog box.
----End
Prerequisite
l You have logged in to the M2000 client.
l The FTP server is configured.
l You are authorized with the relevant privileges.
l The backed up NM files exist on the server.
Procedure
Step 1 Choose Maintenance > System Backup.
Open the Backup Management dialog box. For details, refer to 10.5.6 Parameters for NM
Backup File.
----End
Related Concepts
10.1.2 NE Backup Data
Related References
10.5.6 Parameters for NM Backup File
Context
l The progress of the information collection is displayed in the Collection Details box of the
M2000 Log Information Collector window.
l The M2000 diagnostic tool automatically collects diagnostic information from the client
and then from the server.
Procedure
Step 1 Choose Programs > iManager M2000 Client > M2000 Diagnosis Tool.
Open the M2000 Log Collection Tool window.
Step 3 Choose the information to be collected. For details, refer to 10.5.3 Parameters for Collecting
NM Logs Parameters.
l If you want to collect trace files in the client, trace files in the server, core files in the server,
or trace files in the local maintenance station, you should enter Start Time and End Time
to collect the information within the specified time range.
l If you want to collect alarm diagnostic data of the NE, enter the name of the NE whose alarm
diagnostic data you want collect in NE Name.
By default, the collected files are saved in M2000 client installation path\diagnosis\collected
files. The default M2000 installation path is C:\iManagerM2000Client. You can change the
save path of the collected files.
----End
Related Concepts
10.1.3 NM Log Data
Related References
10.5.3 Parameters for Collecting NM Logs Parameters
10.5.4 Parameters for Fields of the Backing Up or Restorage Task List lists the fields in the
backup or restoration task.
Parameter Description
Parameter Description
FTP User name Indicates a valid name that the user already registered to the
M2000.
Cannot be null.
Items Trace files in Collects the trace files from the M2000 client.
selection Local Host
Parameter Description
Trace files in Collects the trace files from the M2000 server.
server
LMT trace files Collects the trace files from the local maintenance terminal
in server (LMT).
Start Time Indicates the start time for collecting trace files and core
files.
End Time Indicates the end time for collecting trace files and core files.
Number of server Collects the number of server threads and state from the
threads and state M2000 server.
Save Save Positions Indicates the directory for the collected diagnostic data.
Positions
Related Concepts
10.1.3 NM Log Data
Related Tasks
10.4 Collecting NM Log File
Field Description
Field Description
Related Concepts
10.1.1 NM Backup Data
Related Tasks
10.2.2 Viewing NE Backup File
Parameter ID Description
Backup Type Type of the backup selected for 10.3.1 Manual NM Backup
Data, which consists of:
l Full backup: backs up all NM data.
l Incremental backup: backs up new and changed NM data
based on the previous backup data.
For details, refer to 10.1.1 NM Backup Data.
Related Concepts
10.1.2 NE Backup Data
Related Tasks
10.3.2 Viewing NM Backup File
This part describes the basic functions provided by dual-homing and local network domain
management.
11.1.1 Dual-Homing
This part describes the basic knowledge of dual-homing. Dual-homing is a disaster tolerance
mechanism to prevent the system breakdown and ensure the reliability of the mobile network.
11.1.2 Local Network Domain
This part describes the basic knowledge on local network, multi-area (MA) network, and area-
based privilege management of multi-area network. The local network domain refers to the areas
that are managed by the local network. Each local network has an automatic PSTN and a
specified number for toll that indicates the range of local network. For the subscribers in the
same local network, they only need to dial up local telephone number. The local network is
further divided into multi-area network and are network. The resources in the multi-area network
can be divided into different domains. The authority granting policy enables the subscribers in
the multi-area network can manage the resources in the local network.
11.1.1 Dual-Homing
This part describes the basic knowledge of dual-homing. Dual-homing is a disaster tolerance
mechanism to prevent the system breakdown and ensure the reliability of the mobile network.
To be specific, the dual-homing is a kind of networking mode where an MGW is homed to two
MSC servers that together function as a dual-homing pair. Usually, the MGW registers only to
the active MSC server. When the active MSC server fails, the MGW registers to the standby
MSC server to guarantee the continuity of communication services. The active and standby
MSCs know the status of each other through heartbeat signals, and ensure data synchronization
through network management system.
When dual-homing is applied on the MSC server, the following three modes are available:
l 1+1 active/standby: indicates that one MSC server serves as an active server, while the
other MSC server is a standby server.
l 1+1 assistant: indicates that each MSC server is not only an active server but a standby
server of the other MSC server.
l N+1 active/standby: indicates that there are N MSC servers that serve as active servers,
while only one MSC server acts as the standby server for those N MSC servers.
All schemes are the same for the MGW, because each MGW is configured with an active MSC
server and a standby MSC server.
The configuration data in the dual-homing system falls into the following categories:
l Data in the database are divided into active dual-homing data and standby dual-homing
data. The active dual-homing data is always valid, but the standby-homing data is valid
only when the active and standby MSC servers work in assistant mode.
l Data in the active and standby MSC servers are the same.
l Data in the active and standby MSC servers are totally different.
that are managed by the local network. Each local network has an automatic PSTN and a
specified number for toll that indicates the range of local network. For the subscribers in the
same local network, they only need to dial up local telephone number. The local network is
further divided into multi-area network and are network. The resources in the multi-area network
can be divided into different domains. The authority granting policy enables the subscribers in
the multi-area network can manage the resources in the local network.
Local Network
Local network is shorted for local telephone network. A local network is a telephony network
within a toll call numbering zone. The local network is composed of local exchange, transit
exchange, inter-office trunk cables, rural toll trunk cables, subscriber lines, and telephone
terminals.
Local network is an extension of local communication network. After the automatic continuity
is applied in the suburban areas, towns, and rural areas, cities and their suburban areas, towns,
and rural areas are combined together into a local network. The local network mode has the
following advantages: be conducive to the development of telephony service, facilitate the
subscribers' usage, improve the efficiency to cost ratio, and enhance the management efficiency.
Local networks generally apply to areas where the toll call numbers are of two or three digit
long. A local network has a mobile switching center (MSC) or more than one if required. If there
is more than one MSC in a local network, the MSCs intercommunicate with each other through
highly efficient direct routes, which form a mesh network.
Multi-Area Network
The multi-area network is a network in which an MSC server controls several local networks
with the bearer part separated from the control part. The MSC server controls all services in the
MA network. In the MA network, equipment of each local network is connected with the local
media gateway (MGW), and a local network intercommunicates with other local networks
through an MGW. A multi-area network has a maximum of 16 local network. Here, a local
network refers to the areas controlled by a virtual MSC server.
Area-based privilege management of multi-area network applies to the scenario where an MSC
server manages multiple areas divided on a logical or physical basis while user management is
still on a local basis.
A domain contains multiple users and a user has the authorities either in a private domain or a
global domain. The following part illustrates the authorities of users belonging to either local or
global domains.
l A user belonging to a global domain has the following authorities:
– Setting the authorities of an object to the authorities of a local or global domain
– Changing the domain of an object that supports the domain
– Deleting an object that supports the domain
l A user belonging to a private domain (such as domain A) has the following authorities:
– Setting the authorities of an object that supports domain A to the authorities in domain
A
– Changing the domain of an object that supports domain A
– Deleting an object that supports domain A
Only the system administrator is authorized to manage domains and to set the domain authorities
of non-administrator users. By default, an unspecified non-administrator user belongs to a global
domain.
Domains and NEs are in many-to-many relations. Thus, a domain may has more than one MSC
server, and an NE may belong to multiple domains.
Prerequisite
l You have the right to manage dual homing.
l You have the right to operate the NEs that are related to dual homing.
l Dual-homing NEs have be created on the M2000.
l Dual-homing parameters have been set on the NEs.
Context
An MGW is homed to a maximum of two MSC servers, and multiple MGWs can be connected
to the same MSC server.
NOTE
Procedure
Step 1 Choose Configuration > Dual Homing. The Dual Homing dialog box is displayed.
Step 2 On the State Monitor tab page and the information pane below it, you can view the dual-homing
information.
l On the State Monitor tab page, you can view the relationship between the MGW and the
MSC server.
l On the State Monitor tab page, select an MSC server. The Basic Information tab page
displays the basic information about the NE, such as the NE name, dual-homing indication,
working mode, and virtual node name.
l On the State Monitor tab page, select a link. The UDP Heartbeat Information, M3UA
Heartbeat Information, VDB Backup Router Information, and Physical Link
Information tab pages display the details about this link.
----End
Prerequisite
l You have the right to manage dual homing.
l You have the right to operate the NEs that are related to dual homing.
l The NE data is updated on the M2000.
Context
NOTE
Generally, a pair of dual-homing NEs can automatically synchronize data between them. The purpose of
checking dual-homing data is to check the consistency of dual-homing data and to ensure that one MSC
server can take over part or all of the data of the other MSC server after a dual-homing switchover.
Procedure
Step 1 Choose Configuration > Dual Homing. The Dual Homing dialog box is displayed.
Step 2 In the Basic information list, select a dual-homing pair to be checked.
Step 3 Click Check, or click on the interface and then choose Check on the shortcut menu.
The system displays the Consistency Check tab page.
Step 4 In the Consistency Check tab page, select the data resource type to be checked. The system
displays the check result in the right pane.
l You can enter the resource type or key word in Search. Then the related resource types are
listed under Search. You can quickly select the resource type to be checked by double-
clicking the type.
l By default, the system displays inconsistent data by red characters on pink background. To
set the colors of characters and background, refer to 11.2.3 Setting the Attributes for Data
Check Interface.
l Click in the navigation tree, and then choose Hide Identical Pages. The system displays
only the tab pages that include inconsistent data. After you re-select a data resource type in
the navigation tree, the system displays all the consistency check results.
l In the tab page, you can save check results, generate MML scripts, and run the scripts. For
details, refer to 11.2.4 Saving the Audit Result of Dual-Homing Data, 11.2.5 Generating
the Script for Adjusting Difference Data, and 11.2.7 Synchronizing the Dual-Homing
Data.
----End
Prerequisite
The data consistency of the dual-homing pair have been checked. For detailed operations, refer
to 11.2.2 Checking the Dual-Homing Data.
Procedure
Set the parameters in the Consistency Check tab page.
Attribute Operation
Show Line Numbers In the Consistency Check tab page, right-click a record and then choose
Show Line Numbers on the shortcut menu.
To cancel the showing of line numbers, perform an inverse operation.
Show Grid Line In the Consistency Check tab page, right-click a record and then choose
Show Grid Line on the shortcut menu.
To cancel the showing of grid, perform an inverse operation.
Set Color... 1. Right-click the data and choose Set Color . The Set Color dialog
box is displayed.
2. Click a color to open the Color Settings dialog box.
3. You can set colors for inconsistent data and overwritten data in either
of the following ways:
l Under Swatches, select the color you want.
l Under HSB, move the sliders to select the specific colors.
l In the RGB, move the sliders to select the specific colors.
4. Click OK.
5. Click OK or Apply.
To use the default color settings, click Default in the Set Color dialog
box. By default, the system uses red characters in pink background to
express inconsistent data and uses green characters in orange
background to express modified data.
----End
Related References
11.4.2 Interface Description: Checking the Dual-Homing Data
Prerequisite
The data consistency of the dual-homing pair have been checked. For detailed operations, refer
to 11.2.2 Checking the Dual-Homing Data.
Procedure
Step 1 In the Consistency Check tab page, click Save Data.
The system displays the Select File Path dialog box.
NOTE
To obtain the latest data, click Refresh in the Consistency Check tab page.
Step 2 Set the storage path, type, and name for the file.
l The file can be saved in either .txt or .csv format.
l By default, the name is in the format of: Name of the active NE (IP)&Name of the standby
NE (IP)_Data_Generation time, and the time is in the format of YYYY-MM-DD HH-MM-
SS. For instance, the default file name is as follows: OM_SX2(173.20.80.128)&OM_SX8
(173.20.80.132)_Data_2007-03-29 11_20_26.
Step 3 Click OK.
The system displays the content of the file in a dialog box with the file name in the title.
NOTE
You can edit the content of the file in the dialog box and save the modified file.
----End
Prerequisite
The data consistency of the dual-homing pair have been checked. For detailed operations, refer
to 11.2.2 Checking the Dual-Homing Data.
Procedure
Step 1 In the Consistency Check tab page, select a record with inconsistent data.
l If the data of the left NE is correct, click it and then choose Overlap To Right on the shortcut
menu.
l If the data of the right NE is correct, right-click it and then choose Overlap To Left on the
shortcut menu.
TIP
l To select multiple records, press Ctrl or Shift. To select all the records, press Ctrl+a.
l To recover the modified data, right-click it and then choose Revert Left, Revert Right, and Revert
All.
In the generated MML script file, each MML command is followed by the name of the NE that executes
this command. For example, MOD SEVNODE: SN="MSOFT_2", IMMT=TDM, IMCT=NOT-
ALLMGW, IMSM=AUTO; {MSC_FF1}, where MSC_FF1 is the name of the NE that executes this
command.
Step 4 Set the storage path, type, and name for the file.
You can edit the content of the file in the dialog box as well as save and run the modified script.
----End
Procedure
Step 1 Choose Configuration > Dual Homing. The Dual Homing dialog box is displayed.
Step 2 In the Basic information list, select a dual-homing pair.
Step 3 Click MML Command, or click in the window and then choose MML Command on the
shortcut menu, to open the MML Command tab page.
Step 4 Deliver an MML command.
1. In the ROOT navigation tree, select an NE.
2. In the MML Command Navigation Tree, select an MML command.
By clicking the Search tab page and using the search function, you can select an MML
command quickly.
3. In the command window, set related parameters.
4. Do as follows to determine whether to select the Send to assistant host check box:
l If you plan to deliver the MML command to both the active and standby MSC servers,
select the Send to assistant host box.
l If you plan to deliver the MML command only to the active server, do not select this
check box.
----End
Postrequisite
The M2000 supports the clear-up of messages. To clear up messages, perform the following
steps:
l Messages of the MML commands whose Status are Completed can be cleared up.
l When MML commands are being delivered, the option Clear Report on the shortcut menu is
unavailable.
Prerequisite
The inconsistency adjustment script has been created. For detailed operations, refer to 11.2.5
Generating the Script for Adjusting Difference Data.
Procedure
Step 1 In the Consistency Check tab page, click Run MML Script. The system displays the Select
File Path dialog box.
TIP
Also, you can synchronize dual-homing data in either of the following ways:
l Run the script after generating an inconsistency adjustment script. For detailed operations, refer to
11.2.5 Generating the Script for Adjusting Difference Data.
l In the Task Management window, create an MML script task by referring to 14.2.1 Creating MML
Command Script.
----End
Procedure
Step 1 Choose Configuration > Domain Management to open the Domain Management window.
Step 2 Right-click the Domain node and choose Create. The Create Domain dialog box is displayed.
Step 3 Enter the name for the new domain in the Please Input Domain Name field.
NOTE
l You can type one to 30 characters in the field mentioned previously. Special characters excluding the
underline are not allowed.
l Select NEs and users from the NE List and User List to bind these them to this local network domain.
----End
Procedure
Step 1 Choose Maintenance > MML Command. The MML Command window is displayed.
Step 2 Select the MSC servers that have the dual-homing relation from the navigation tree. Enter the
command in the Command Input field. For instance, enter ADD ACC.
Step 3 Set Deliver the Standby Server to Yes.
----End
Prerequisite
You have the authority for domain operation.
Procedure
Step 1 Choose Configuration > Domain Management to open the Domain Management window.
Step 3 Select a field in the Domain navigation tree and select User Liston right.
Step 4 Right-click the selected field and select Bind User on the shortcut menu. Alternatively, click
Bind User to view the Bind User dialog box.
NOTE
You can also select a user in User List on right and right-click it to select Bind User on the shortcut menu.
Step 5 In User List, select the user to be bound or deselect a bound user.
----End
Context
The NE to be added or removed is in connection with the M2000.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is
displayed.
Step 2 On the left pane, right-click a domain under the Domain node. Alternatively, right-click a
domain on the NE List. Choose Bind NE or click Bind NE. The Bind NE dialog box is
displayed.
NOTE
If an NE is in disconnected, the NE cannot be bound.
----End
Related References
11.4.3 Interface Description: Managing the Local Network Element Domain
Prerequisite
You have the authority for domain operation.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is
displayed.
Step 2 In the left pane, select the Domain tab. Two methods are available for changing the name of a
domain:
Method Procedure
Method one 1. In the Domain Managementwindow, select a domain under the node
Domain.
2. Right-click it and select Rename... on the shortcut menu. The system
displays the Rename Domain dialog box.
3. Enter the new name of the domain.
4. Click OK.
Method Two 1. In the Domain Management window, select a domain under Domain
List.
2. Right-click the domain and select Rename... on the shortcut menu, or click
Rename.... The system displays the Rename Domain dialog box.
3. Enter the new name of the domain.
4. Click OK.
NOTE
If the NEs in the modified domain are disconnected from the M2000, the NEs are Different after the name
of the domain is changed. After the NEs are connected, you can right-click an NE whose Synchronization
Status is inconsistent from the NE List, and then choose Synchronization to synchronize the modified
domain name to the NE.
----End
Prerequisite
You have the authority for domain operation.
The NEs are in inconsistent status.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is
displayed.
Step 2 In the navigation tree, select the Domain node. Select an NE whose Synchronized State is
Different on the NE List tab.
Step 3 Choose Synchronize or click Synchronize to synchronize the information of local network
domain.
If the NE is connected, the Synchronized State of the NE becomes Accordant. If the an NE is
disconnected, the Synchronized State is still Different.
----End
Prerequisite
You have the authority for domain operation.
The resources in the local network domain are not used by other domains and the NEs in the
domain is correctly connected.
Context
Once the local network domain is deleted, the subscribers in the previous domain become the
subscribers of the global network domain.
Procedure
Step 1 Choose Configuration > Domain Management. The Domain Management window is
displayed.
Step 2 Select the Domain node and use either of the following methods to delete the local network
domain:
Method Step
Method 2 1. Right-click a domain from the Domain List in the Domain Management
window.
2. Choose Delete. Alternatively, click Deleteafter selecting a domain.
3. In the displayed Confirmation dialog box, click Yes to delete the local network
domain.
----End
Adding a Domain
1. Choose Configuration > Domain Management. The Domain Management window is
displayed.
2. Right-click the Domain node and choose Create. The Create Domain dialog box is
displayed.
3. In the Please Input Domain Name field, enter the name of the desired domain. In the NE
List or User List, select NEs or users to bind NEs and users.
4. Click OK to add a domain.
Figure 11-1 Dual Homing window (for 1+1 mutual-aid networking mode)
Figure 11-2 Dual Homing window (for 1+1 active/standby networking mode)
Figure 11-3 Dual Homing window (for N+1 active/standby networking mode)
Result of Dual-Homing Data, 11.2.5 Generating the Script for Adjusting Difference
Data, and 11.2.7 Synchronizing the Dual-Homing Data.
Figure 11-4 shows the consistency check tab page. Table 11-1 describes Figure 11-4.
(1) Navigation tree Displays all the data resource types to be checked.
(2) Searching panel Displays the related data resource types after you
enter a data resource type or the key word in the
Search box. By clicking a type, you can locate it in
the navigation tree.
Related Tasks
11.2.3 Setting the Attributes for Data Check Interface
Figure 11-5 Interface for managing the local network element domain
No. Meaning
Related Tasks
11.3.4 Managing NEs in the Local Network Domain
The 3GPP 23.236 defines the concept of the MSC Pool. That is, by using the Iu-Flex technology,
one RNC can share multiple MSC servers. Based on a specified load balancing algorithm, the
user services are distributed to different MSC Servers and the services of one user are managed
by the same MSC Server. Thus the MSC server resources can be shared. You can configure,
monitor, and maintain the MSC Pool on the M2000 client.
alarms, the MSC Pool configuration interface, and parameters related to Pool configuration or
maintenance operations. In this way, you can perform operations related to MSC Pool
management.
Basic Concepts
For related description of the MSC Pool concepts, see Table 12-1.
Concept Description
MSC Pool Area If one or more RNCs/BSCs belong to an MSC Pool, the
service areas covered by the RNCs/BSCs form an MSC Pool
area, as shown in Figure 12-1.
The subscribers in the pool area are served by the MSCs in
the MSC Pool.
Iu/A-Flex function Refers to the technology used for connecting the RNC/
BSC to multiple MSC servers.
According to the 3GPP 23.236 protocol, the BSC in an MSC
Pool must support the A-flex function. The BSC on the
current network, however, does not support the A-Flex. In
addition, the A-Flex supported by BSCs manufactured by
different vendors is not consistent. Therefore, the MGW is
the agent of A-Flex in the Pool. To solve this problem,
Huawei MGW can be used to act as the A-Flex agent. In this
way, BSCs on the present network can access the MSC Pool
without upgrade.
NNSF Function (NAS node Indicates the node selection function on the non-access
selection function) stratum (NAS). It is used to select an MSC server for an MS/
UE.
3GPP TS The NEs with the Iu/A-Flex 1. On the MSC server and the RNC/
23.236 protocol function are required, such as the BSC, set the MSC server where
RNC, BSC, or MGW. On these users are transferred to the off-load
NEs, you should set the status of status.
the MSC server from which users 2. When an MS/UE registered in the
are to be transferred to off-load. off-load MSC server initiates
NOTE services, the MSC server
l When using this method, the distributes the TMSI that contains
destination MSC server cannot be the Null TMSI to the MS/UE.
specified. The system selects the Meanwhile, the current LAI of the
destination MSC server according MS/UE is designated as local Non-
to the load balancing algorithm.
broadcast LAI.
l After transferring users, you
should restore the MSC server 3. After the MS/UE ends the current
state that is configured on the MSC service, the Non-broadcast LAI
server and the RNC through the prompts the MS/UE to update the
M2000. location.
This is because the Non-broadcast
LAI is different from the LAI
broadcast by the RNC/BSC of the
MS/UE.
4. Upon receiving a location update
message containing null-NRI
from the MS/UE, the RNC/BSC
selects a valid MSC server
according to the proportion of user
capacity of valid MSC servers
(excluding the off-load MSC
server) and routes services to the
selected MSC server.
The selected MSC server registers
the MS/UE and distributes a TMSI
containing its NRI to the MS/UE.
During the registration, the
selected MSC server determines
the original MSC server where the
MS/UE is registered according to
the Non-broadcast LAI carried by
the MS/UE. The server also
obtains user data, that is, IMSI and
unused encryption parameters
from the original MSC server.
5. After transferring users, restore
the state of the MSC server on the
MSC server and the RNC/BSC
through the M2000. For details,
see 12.3.3.9 Setting the
Inter-office E The NEs with the lu/A-Flex 1. On the MSC server and the RNC/
interface function, that is, the MGW, RNC, BSC, set the MSC server from
redirection or BSC,are not required. You only which users are to be transferred to
need to specify a destination MSC the off-load status.
server, and the system 2. When an MS/UE registered in the
automatically routes the off-load MSC server initiates a
distributed users to the specified location update request or service
MSC server. release request, the MSC server
NOTE initiates the location update
This method aims to reduce the request to the destination MSC
dependence on the access network
server based on the redirection
when users are manually transferred.
The operation can be independently message.
performed in the CN by distributing 3. Upon receiving the request, the
the NRI of the destination MSC destination MSC server encrypts
server. This also reduces the
the authentication, obtains the ID,
operations that must be performed on
both the CN and access network. checkimei, and TMSI re-
distribution message from the MS/
UE, and then sends the
information to the originating
MSC server. The originating MSC
server interacts with the MS/UE.
In addition, the destination MSC
server initiates the location update
to the HLR and finally distributes,
by using the TMSI, a TMSI
containing the NRI of the
destination office to the MS/UE.
Thus, the subsequent location
updates or service requests are
directly delivered to the
destination MSC server.
4. After transferring users, restore
the state of the MSC server on the
MSC server and the RNC/BSC
through the M2000.
relevant MSC servers based on the capacity proportion of the MSC servers. In this way, the
utilization of the entire CN resources is improved and the investment is reduced.
In an MSC Pool, one RNC/BSC is connected to multiple MSC servers in the pool. Therefore,
when the MS/UE in the RNC/BSC service area initiates a new service request, the RNC/BSC
needs to select a serving MSC server for the service. For details, see Table 12-3.
The MS/UE initiates a According to the load balancing algorithm, the RNC/BSC selects
service based on the IMSI a valid MSC server for the MS/UE based on the proportion of
or IMEI. subscriber capacity of the MSC servers in the MSC Pool. If an
MS/UE initiates a service using IMSI, the selected MSC server
distributes a TMSI containing the NRI of the MSC to the MS/UE.
As shown in Figure 12-2, if the available capacity of MSC
server1 is 4, the available capacity of MSC server2 is 3, and the
number of MSs/UEs is 7, then the RNC/BSC assigns four MSs
to MSC server1 and three to MSC server2 to ensure the load
balance.
The MS/UE initiates a The RNC/BSC selects the serving MSC server for the MS/UE
service based on the according to the mapping between the NRI and MSC server.
IMSI. NOTE
When the selected MSC server is invalid or no mapping is available
between the NRI and the MSC server, the RNC/BSC uses the load
balancing algorithm and distributes MSC server according to the
proportion of subscriber capacity of the MSC servers. Then, the selected
MSC server assigns a TMSI containing the office NRI to the MS/UE.
The MSC server pages The RNC/BSC temporally saves the mapping between the MSI
the called MS/UE based and the paged MSC server. When the paged MS/UE pages the
on the IMSI. corresponding network based on the IMSI, the RNC/BSC selects
the MSC server according to whether the NRI is available on the
MS/UE.
l If the NRI is available on the MS/UE, the RNC/BSC selects
an MSC server according the mapping between the NRI and
the MSC server.
l If the NRI is unavailable on the MS/UE, the RNC/BSC selects
the MSC server according to the temporally saved mapping
between the IMSI and the MSC server.
NOTE
If the selected MSC server is invalid or the system fails to select the MSC
server according to the mapping, the RNC/BSC selects an MSC server
according to the load balancing algorithm.
CAUTION
l When the RNC/BSC detects that the signaling point of the MSC is inaccessible, the RNC/
BSC considers the MSC to be faulty or invalid.
l The proportions of subscriber capacity of the RNC/BSC to each MSC server needs to be
configured statically on the RNC/BSC.
In addition, the MSC servers can notify the subscriber capacity regularly, and the RNC/
BSC dynamically adjusts the proportion of subscriber capacity of MSC servers according to
the subscriber capacity of each MSC server in the notification. This mode, however, only
applies to the case that all MSC servers in the MSC Pool and BSCs and RNCs in the MSC
Pool area are Huawei equipment. For other modes, the RNC can configure the subscriber
capacity of MSC servers statically.
l The subscriber capacity of an MSC server described previously is the total number of
subscribers of the MSC server (number of licensed subscribers for the MSC server).
However, when an MSC server connects with RNCs or BSCsoutside the MSC Pool, the
subscriber capacity reserved for these RNCs or BSCs needs to be subtracted from total
capacity as for calculation of subscriber capacity of the MSC server.
Prerequisite
l The access network NEs support the Iu/A-Flex function and they are configured on the
basis of network planning.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool node and choose Create MSC Pool from the
shortcut menu.
Step 3 Set the pool information in the displayed Create MSC Pool dialog box.
1. Enter the Pool name in Pool Name.
2. Select the networking type of the Pool on right of the Pool Name box.
3. Select the NEs to be added to the Pool in Optional Nes. Click . Then the
NEs are added to Selected Nes.
l In Selected Nes, you can use Shift or Ctrl to select multiple NEs at the same time.
l You can click to add all the NEs in Optional Nes to Selected Nes.
----End
Postrequisite
1. After a pool is created, you need to perform initial configuration and data check for the
pool to check whether the configurations of the MSC Pool are correct.
For details about how to perform initial configuration for the pool, refer to 12.3 Initial
Configuration of MSC Pool. For details about how to perform data check, refer to 12.5.2.2
Manually Checking MSC Pool Data.
If the configuration data that must be consistent with all NEs in the pool is inconsistent,
you need to synchronize the data on the basis of reference values. For details, refer to
12.5.2.4 Synchronizing MSC Pool Data.
2. After the data are correctly configured, you can start the pool to perform routine operations
and maintenance.
For details about routine operations and maintenance, refer to 12.4 Routine Maintenance
of MSC Pool.
Related References
12.6.4 Parameters for Creating/Modifying MSC Pool
12.6.3 Interface Description: MSC Pool Configuration
12.6.4 Parameters for Creating/Modifying MSC Pool
12.6.3 Interface Description: MSC Pool Configuration
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
The type of the MSC Pool load unbalance alarm is Fault Alarm, and the alarm severity is
Critical. For details, see ALM-1 Load Unbalance Alarm.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, select the MSC Pool whose alarms for load unbalance need to be set.
Right-click the pool and select Property from the shortcut menu.
Step 3 In the navigation tree in the left pane of the Pool Property Settings dialog box, select Alarm
Load Balance Parameters and set the alarm threshold and automatic check period.
See 12.6.16 Parameters for Setting Load Unbalance Alarm for the details of parameters.
Step 4 Click OK.
The Message dialog box is displayed, showing the operation results.
NOTE
If the configuration of alarm parameters fails, the detailed reason for the failure is displayed in the
Message dialog box.
----End
Result
When an alarm for load unbalance is generated, the MSC Pool Management interface displays
the message Pool load balance status:Abnormal in red.
Postrequisite
l You can check detailed information about the Pool load unbalance by querying fault alarms.
For details, refer to 12.4.1.1 Viewing the Current Fault Alarms of MSC Pool.
l When a load unbalance alarm is generated, you can manually transfer MSC server users to
balance the load of each MSC server in the Pool. For details, refer to 12.5.1.3 Manual
Transfer of Users.
Related References
12.6.16 Parameters for Setting Load Unbalance Alarm
Prerequisite
l You have logged in to the M2000 client.
Context
The type of the alarm about inconsistent MSC Pool data is event alarm, and the alarm severity
level is critical. For details, see ALM-2 Data Inconsistency Alarm.
NOTE
You can manually check MSC Pool data. If the inconsistent data has no effect on the MSC Pool service,
you can shield this data. The shielded data will not be checked in future checks. For details, see 12.5.2.3
Setting the Checking Items of MSC Pool Data.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool to mange auto-check tasks, and choose Data
Consistency Check > Automatic Check from the shortcut menu.
Step 3 In the displayed Automatic Check dialog box, click the Check Task tab. In the displayed tab
page, click Add.
----End
Result
If inconsistent data is found, the system reports a critical event alarm.
Postrequisite
If inconsistent data exists, you can perform the following operations:
1. Check the result to get the information about the inconsistent data. For details, see 12.5.2.1
Viewing the Result of Auto-Checking MSC Pool Data.
2. On the Check Result tab page of the Automatic Check dialog box, click Manual
Check to check the data again.
3. Manually synchronize the inconsistent data to ensure consistency. For details, see 12.5.2.4
Synchronizing MSC Pool Data.
Related Tasks
12.5.2 Checking MSC Pool Data
12.5.2.3 Setting the Checking Items of MSC Pool Data
12.5.2.3 Setting the Checking Items of MSC Pool Data
Related References
12.6.9 Parameters for Setting the Auto-Check of MSC Pool
This describes how to set the load balance parameters of the MSC Pool. After setting up an MSC
Pool, you should specify the user capacity of each MSC server in the MSC Pool. In this way,
you can balance user allocation according to the defined user capacity when guiding the RNC/
BSC to access users.
12.3.3.8 Setting the Non-Broadcast LAIs of MSC Pool
This describes how to set the non-broadcast LAIs of the MSC Pool. When the users in the MSC
Pool are transferred, the destination MSC server determines the address of the original MSC
server of the MS/UE on the basis of the non-broadcast LAI and obtains users' information. The
non-broadcast LAI of each MSC server is set during network planning. You can modify the
network settings through the M2000 when the setting is incorrect.
12.3.3.9 Setting the Maintenance State of NEs in MSC Pool
This describes how to manually set the maintenance state of the NEs in the MSC Pool when you
need to segregate the MGW or perform user transfer. The NE maintenance status can be MGW
Segregate Status and CN Node Status.
12.3.3.10 Setting the Operator for MSC Pool
This describes how to set the operator for the MSC Pool. When the access side of the MSC Pool
supports network sharing, you need to set the operator of the MSC Pool.
CAUTION
When the MSC Pool consists of only the access network NEs, the following parameters cannot
be configured on the M2000 client:
l CN ID
l Non-broadcast LAI
l MGW Segregation Status
Non-broadcast LAI Special LAI. The special The functions of the Non-
LAI has the same coding broadcast LAI are as follows:
system as the common LAI. l During user transfer, Non-
LAI indicates the local area broadcast LAI can be used to
identifier. trigger the immediate location
update of an MS/UE after the
current service is complete.
l When the user transfers, the
destination MSC server
determines the address of the
original MSC server that
serves the MS/UE based on the
Non-broadcast LAI. At the
same time, the destination
MSC server obtains the user
information such as the user's
IMSI and the unused
encrypted parameters.
NOTE
Each MSC server in the MSC Pool
has a unique Non-broadcast RAI.
Each MSC server must be able to
identify the Non-broadcast RAIs of
other MSC servers in the same MSC
Pool.
Pool Available Capacity Indicates the actual user After a pool is initially
capacity of the MSC server established, by setting the pool
in the Pool. available capacity of the MSC
The pool available capacity server, you can balance user
is the converted capacity allocation when guiding the
value of the license capacity. NNSF node, that is, MGW,
For example, if an MSC RNC, and BSC, to access users.
server in the pool is
connected to an RNC or
BSCoutside the pool, the
pool available capacity of
the MSC server in the pool
equals the user capacity
provided outside the pool
subtracted from the license
capacity.
NOTE
The user capacity for an RNC
or BSC outside the Pool is
defined during the planning of
the MSC Pool network.
MGW Segregation Status The MGW states are By setting the MGW status to
Normal and Segregate. Segregate, the MGW exits
NOTE smoothly and has no impact on
The MGW refers to the the users' services.
VMGW that acts as an agent of For detailed description of MGW
the Iu-Flex function.
status, refer to 12.6.14
VMGWs are logically Parameters for Setting NE
divided MGWs. State of MSC Pool.
Iu/A-Flex Activated Displays whether the Iu/A- The prerequisite for joining the
Status Flex function is supported by Pool is that the related CN NEs
the NEs within the pool. support the Iu/A-Flex function.
l True: indicates that NEs
within the pool support
the Iu/A-Flex function.
l False: indicates that NEs
within the pool do not
support the Iu/A-Flex
function.
NOTE
Iu/A-Flex function refers to the
function that enables an RNC
or BSC to connect multiple
CNs.
NRI Length The NRI is included in the Only when the length of the NRI
TMSI distributed to the MS/ is set, the NNSF node, that is, the
UE by the MSC server. The MGW, RNC, or BSC, can obtain
NRI length refers to the the NRI information from the
length of the NRI in the TMSI based on the length of the
TMSI. NRI, and thus route the MS to the
As shown in Figure 12-3, related MSC server.
the NRI is located between NOTE
the 23rd bit and the 14th bit l The length of the NRI configured
of the TMSI. The length is for different MSC servers and
adjustable, that is, from 0 to different RNCs or BSCswithin
10 (unit: bit). When the the MSC Pool should be the
same.
length of the NRI is not 0, the
NRI begins with the 23rd bit. l In the event of overlapping pool
When the length of the NRI area, the length of the NRI
configured for each RNC or
is 0, you can infer that the BSCwithin the MSC Pool area
MSC Pool function is not and the length of the NRI for each
supported. MSC server within the MSC Pool
should be equal.
Null NRI A special NRI, which has the When the user transfers, the null
same coding with the NRI is used to instruct the RNC
common NRI. or BSC to select another MSC
server for the MS/UE.
Within the MSC Pool of a single
operator, the Null NRI is unique.
When Multi-Operator Core
Network (MOCN) is supported,
however, different operators
within the MSC Pool have
different Null NRIs. That is, each
CN operator has a unique Null
NRI.
Related Tasks
12.3.3.3 Setting CN ID of an MSC Server
12.3.3.4 Adding the NRI of MSC Pool
12.3.3.5 Setting the Mapping Between NRI and CN ID
12.3.3.8 Setting the Non-Broadcast LAIs of MSC Pool
12.3.3.7 Setting the Load Balancing Parameters of MSC Pool
12.3.3.9 Setting the Maintenance State of NEs in MSC Pool
12.3.3.6 Setting the Null NRI or the Length of NRI
12.3.3.10 Setting the Operator for MSC Pool
Related References
12.6.10 Parameters for Setting CN ID of an MSC Server
12.6.11 Parameters for Setting NRI of an MSC Pool
12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool
12.6.13 Parameters for Setting Load-Balancing of an MSC Pool
12.6.14 Parameters for Setting NE State of MSC Pool
12.6.15 Parameters for Superior Settings
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
When viewing the attributes the MSC Pool, you can select Show the acquired detail list to view
the detailed parameter information. For example, if you select an MSC server record on the
Load Balance Parameter tab page, The detail list displays the capacity information about the
MSC server configured on all the MSC servers, MGWs, and RNCs/BSCs.
NOTE
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool of which you plan to view the attributes, and
choose Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool whose CN ID needs to be redefined, and then
choose Pool Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
Step 3 Click the CN ID tab, and then select from the list the MSC server whose CN ID needs to be set.
Step 4 Double-click the record or click Modify.
The Modify dialog box is displayed.
Step 5 Enter a value in the CN ID field.
For details of the parameters, see 12.6.10 Parameters for Setting CN ID of an MSC Server.
Step 6 Click OK.
Step 7 In the displayed The MML Commands send to NE dialog box, click Send.
The system issues MML commands to all the MSC servers within the pool, and displays the
Send Status and Send Result of the command.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.10 Parameters for Setting CN ID of an MSC Server
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
You should add the NRI of the MSC server through the M2000 when the MSC server in the
MSC Pool increases.
CAUTION
The change of NRI greatly affects network services. It is recommended that you confirm the
change during the network planning and then add the NRI on the M2000 client.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool to which you plan to add the NRI, and choose
Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
CAUTION
The added NRI value cannot be the same as the existed NRI values in the Pool.
See 12.3.3.1 Parameters of MSC Pool Attributes for detailed information on the NRI.
Step 5 Click OK.
Step 6 In the displayed The MML Commands send to NE dialog box, click Send.
The system issues MML commands to all the MSC servers, MGWs, and RNCs/BSCs within
the pool, and displays the Send Status and Send Result of the command.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 7 Click Close to close the The MML Commands send to NE dialog box.
Step 8 Click Close to close the Pool Parameter Settings dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.11 Parameters for Setting NRI of an MSC Pool
change the setting of the mapping relation between the NRI and the CN ID through the
M2000 when faults occur during network planning or NRI planning adjustment.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
The NNSF node refers to the NE node that provides the NNSF function, that is, the MSC server
that is used to select service for an MS/UE. For example, an NNSF node can be an MGW, RNC,
or BSC.
CAUTION
Different Pool networking types have different implications for operations such as modification
and deletion. For details, refer to Table 12-5.
Pool including the CN NEs l Modification: indicates that only the NRI
Modification: configured on a specific MSC server is modified.
l Deletion: indicates that only the NRI configured
on a specific MSC server is deleted.
Pool that contains the NEs only from l Modification: indicates that the NRI of a specific
the access network MSC server, which is configured on all RNCs/
BSCs, is modified.
l Deletion: indicates that the NRI of a specific MSC
server, which is configured of all RNCs/BSCs, is
deleted.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool on which you plan to set the mapping between
NRI and CN ID, and choose Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
Step 3 Click the CN ID-NRI Setting tab, and then select from the list the NRI record that needs to be
set.
CAUTION
The new NRI value should be unique.
For detailed description about the mapping relation between the NRI and the CN ID, refer to
12.3.3.1 Parameters of MSC Pool Attributes.
Step 7 In the displayed The MML Commands send to NE dialog box, click Send.
The system issues MML commands to all the MSC Servers in the local office, and displays the
Send Status and Send Result of the command.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box.
----End
Result
l On the CN ID-NRI Setting tab page, a new record is added to the task list, displaying the
new NRI-related information.
l The former NRI record, that is, in the NE Name column, Unknown ne is displayed.
Postrequisite
After successfully changing the NRI of the MSC server in the local office, you need to select
the changed NRI record in the list, click Synchronize and then Send. Then the changed NRI is
applied to all the other MSC servers, MGWs, and RNCs/BSCs in the MSC Pool.
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.11 Parameters for Setting NRI of an MSC Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
CAUTION
The re-definition of the NRI length may affect the services near the Pool. Re-plan the NRI of
the Pool on the entire network before performing this operation.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, choose the MSC Pool whose NRI length or the Null NRI value needs to
be re-defined, and then right-click Pool Parameter Setting.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
Step 3 Click the Advanced Setting tab. Click Set in the NRI group box.
Step 4 Re-define the NRI length or the Null NRI value in the displayed Modify dialog box.
For detailed information on the NRI length and Null NRI, see 12.3.3.1 Parameters of MSC
Pool Attributes.
Step 7 In the displayed The MML Commands send to NE dialog box, click Send.
The system issues MML commands to all the MSC servers, MGWs, and RNCs/BSCs within
the Pool, and displays the Send Status and Send Result of the command.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.15 Parameters for Superior Settings
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, select the MSC Pool whose parameters for load balance need to be set.
Right-click the pool and select Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
Step 3 Click the Load Balance Parameter tab, and choose the MSC server record whose available
capacity needs to be re-defined.
l You can view the license capacity of each MSC server in the pool on the Load Balance
Parameter tab page. The maximum license capacity cannot be modified.
l If the M2000 fails to collect the data of certain MSC server, the value of the license capacity
is displayed as 0 on the Load Balance Parameter tab page.
l If you select the Show the acquired detail list check box and select a record of the MSC server
on the Load Balance Parameter tab page, The detail list displays the capacity information
about the MS server configured on all the MSC servers, MGWs, and RNCs/BSCs.
l For detailed description of the parameters on the Load Balance Parameter tab page, refer
to 12.6.13 Parameters for Setting Load-Balancing of an MSC Pool.
Step 5 Enter the new available capacity of the MSC server in New Pool Available Capacity.
See 12.3.3.1 Parameters of MSC Pool Attributes for detailed information on the Pool available
capacity.
Step 7 In the displayed The MML Commands send to NE dialog box, click Send.
The system issues MML commands to all the MSC servers, MGWs, and RNCs/BSCs within
the pool, and displays the Send Status and Send Result of the command.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.13 Parameters for Setting Load-Balancing of an MSC Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool whose Non-broadcast LAI needs to be re-
defined, and then choose Pool Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
Step 3 Click the Non-broadcast LAI Setting tab, and select the MSC server record whose non-
broadcast LAI needs to be re-defined.
Step 7 In the displayed The MML Commands send to NE dialog box, click Send.
The system issues MML commands to all the MSC servers within the pool, and displays the
Send Status and Send Result of the command.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.12 Parameters for Setting Non-Broadcast LAI of an MSC Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool to which you plan to set the NE maintenance
state, and choose Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is successfully refreshed, the Pool Parameter Setting dialog
box is displayed.
NOTE
l If the configuration data fails to be refreshed, the Synchronize Pool Parameter Data dialog box
displays the failure details. You can click Parameter Setting to view the Pool Parameter Setting
dialog box.
l If you have not set the operator of the Pool, the Message box is displayed, prompting you to set the
operator flag. In this case, click OK to open the Pool Parameter Setting dialog box. Then, click the
Advanced Setting tab and set the parameters.
Step 3 Click the NE Status Maintenance tab, and choose the NE status in the Choose Status Type
drop box according to the requirements of network maintenance.
Step 4 Choose the NE record that needs to set the status. Double-click the record or click Modify.
Step 5 Choose the NE status according to your requirements in the Set Status drop box.
See 12.6.14 Parameters for Setting NE State of MSC Pool for detailed information about the
meaning of NE status.
Step 7 In the displayed The MML Commands send to NE dialog box, click Send.
For the CN node status, the system issues MML commands to all the MGWs and RNCs/BSCs
within the pool. For the MGW segregate status, the system issues MML commands to all the
MSC servers within the pool. The system also displays Send Status and Send Result of the
MML commands.
NOTE
l When the MML commands are being issued, you can click Stop to stop issuing the MML commands.
l If all MML commands fail to be run, you can click Send to issue the MML commands again. If part
of the MML command are issued, the Send button is unavailable. You can infer that the command
cannot be issued again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Settings dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.14 Parameters for Setting NE State of MSC Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
l CN NEs exists in the MSC Pool.
Context
NOTE
l You can view the information about the access network NEs in the Parameter Setting dialog box only
after you specify the operator of the Pool.
l The M2000 provides this function only when the networking type of the MSC Pool is Access Network
Only or Core&Radio Access Network.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool whose operator needs to be set, and then choose
Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Data dialog box is displayed, showing the refresh progress.
After the pool configuration data is updated, a Message box is displayed, informing you that the
operator identity is not set.
Step 3 In the displayed Message dialog box, click OK.
Step 4 Click the Advanced Setting tab. Click Set in the PLMN group box.
Step 5 In the displayed Modify dialog box, enter a new MCC and MNC.
For description of the related parameters, see 12.6.15 Parameters for Superior Settings.
Step 6 Click OK.
The displayed dialog box shows whether the operation is successful.
Step 7 Click OK to close the dialog box.
----End
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related References
12.6.15 Parameters for Superior Settings
Context
l For details of the operations related to the alarms, such as synchronizing, printing, and
confirming the alarm, refer to 2.2 Monitoring Network Alarms.
l On the Pool Management interface, you can right-click an MSC Pool in the navigation
tree and choose Query Alarm > History Fault Alarm from the shortcut menu to view
the history fault alarms of MSC Pool. For details, refer to 2.2.7.2 Querying History Fault
Alarms.
12.4.1.1 Viewing the Current Fault Alarms of MSC Pool
Fault alarms of MSC Pool refer to the alarms that are raised because of unbalanced loads. You
can set multiple query conditions to quickly locate the unbalanced loads to perform maintenance.
12.4.1.2 Viewing the Event Alarms of MSC Pool
This describes how to view the event alarms of MSC Pool. Event alarms of MSC Pool are mainly
generated because of data inconsistency between MSC servers or MGWs in the MSC Pool. You
can set multiple query conditions to quickly locate the inconsistent data. Thus you can
synchronize them in time to ensure the normal operation of the MSC Pool.
Related References
12.6.2 Interface Description: Viewing MSC Pool Alarms
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
Fault alarms of MSC Pool refer to the alarms raised because of unbalanced loads in MSC Pool.
The alarm type is internal NM. For details, refer to ALM-1 Load Unbalance Alarm.
To view the current fault alarms of specific NEs in the MSC Pool, you can use one of the
following methods:
l Use the alarm query function described in 2.2.7 Querying Alarms.
l View the icon color and alarm balloon of the NE on the M2000 physical topology view or
the Pool topology view.
When an NE generates fault alarms, the color of the NE icon changes to that for the most
severe alarm. In addition, an alarm balloon appears beside the icon. The balloon displays
the alarm severity identity and number of alarms.
Procedure
View the current fault alarms of MSC Pool.
Use one of the following methods to view the Event Alarms window:
Method Procedure
From the Pool Management 1. Choose Maintenance > Pool Management or click
window
on the toolbar. The Pool Management window is
displayed.
2. Right-click an MSC Pool in the navigation tree and
choose Query Alarm > Current Fault Alarm from the
shortcut menu.
From the main window of the 1. Choose Monitor > Current Fault Alarms or click
M2000 client
on the toolbar. The Filter dialog box is displayed.
2. Click the Alarm Source tab to select the MSC Pool
whose alarms need to be checked.
3. On the Base Setting tab page, set the time segment of the
alarm.
4. Click OK.
Method Procedure
For details of the operations related to alarms, such as saving, printing, and viewing alarm details,
refer to 2.2 Monitoring Network Alarms.
----End
Result
In Current Fault Alarms, you can view the details of current fault alarms of MSC Pool.
Related References
12.6.2 Interface Description: Viewing MSC Pool Alarms
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
l Event alarms of MSC Pool are the event alarms raised when data inconsistency is detected
during data auto-check. The alarm type is internal NM. For details, refer to ALM-2 Data
Inconsistency Alarm.
l To view the event alarms of specified NEs in the Pool, you can use the alarm query function
described in 2.2.7 Querying Alarms.
Procedure
View the event alarms of MSC Pool.
Use one of the following methods to view the Event Alarms window:
Method Procedure
From the Pool Management 1. Choose Maintenance > Pool Management or click
window
on the toolbar. The Pool Management window is
displayed.
2. Right-click an MSC Pool in the navigation tree and
choose Query Alarm > Event Alarm from the shortcut
menu.
For details of the operations related to alarms, such as saving, printing, and viewing alarm details,
refer to 2.2 Monitoring Network Alarms.
----End
Result
In Event Alarms, you can view the details of event alarms of MSC Pool .
Related References
12.6.2 Interface Description: Viewing MSC Pool Alarms
Application Scenario
The scenarios of monitoring the load of MSC Pool in real time are as follows:
l After the imbalance alarm is generated, check the Pool load status in real time to obtain the
information about the users on each MSC server and to draw up the user transfer scheme.
l After manually transferring users, monitor the Pool load status to obtain the information
such as progress of user transfer and CPU load of each NE in the Pool.
l Periodic monitoring in routine maintenance
From the real-time monitoring chart, you can monitor the number of users served by the MSC
server, the CPU usage, and the MGW contexts.
12.4.2.2 Real-Time Monitoring Counters of MSC Pool
This describes the real-time monitoring counters shown in the Create a Real-time Load
Monitor Task dialog box. You can refer to this topic when setting real-time monitoring for an
MSC Pool.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
The real-time monitoring chart of the MSC Pool can be a line chart or bar chart. The difference
is as follows:
l Line chart: The vertical coordinate refers to the counter values. The horizontal coordinate
refers to the monitoring time.
l Bar chart: The vertical coordinate refers to the counter values. The horizontal coordinate
refers to the monitored object
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool to be monitored, and choose Real-time
Monitor from the shortcut menu.
Step 3 In the displayed Create a Real-time Load Monitor Task, set the monitoring parameters.
1. Select the monitoring counters.
For details of monitoring counters, see 12.4.2.2 Real-Time Monitoring Counters of MSC
Pool.
2. Select the monitoring period of the counter from the Period drop-down list of the related
monitored object.
The system refreshes the monitoring counters based on the specified period. The monitoring
period can be 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, or 20 minutes.
3. Select the NEs to be monitored from the NE group box.
You can select multiple monitored objects.
Step 4 Click OK.
The load changes of the MSC server are displayed in a line chart. you can also select Histogram
in Chart Type. You can right-click in the real-time monitoring chart and perform the following
operations:
l Save as an image: to save the monitoring chart as an image. The image is in .jpg format.
l Export data: to save the monitoring data to a file. The file is in .csv format. Print:
l Print: to print the current monitoring chart.
l Set NE color:
l to display different NE data by colors.
NOTE
The created tasks are named by Monitor TaskN with N as an integer starting from 1. For example, the
first monitoring task is named Monitor Task, and the second task is named Monitor Task2. You can
change the task names as required.
----End
The real-time monitoring counters are MSC Server Subscriber Quantity, MSC Server CPU
Occupancy Rate, and Number of MGW Contexts. Table 12-6 shows the meanings of these
counters.
MSC Server Total Number of all subscribers on the MSC server, that is, users
Subscriber inside and outside the Pool.
Quantity
Conversation Number of active subscribers on the MSC server, that is,
active subscribers inside and outside the Pool.
Idle Number of idle subscribers on the MSC server, that is, idle
subscribers inside and outside the Pool.
MSC Server CPU Occupancy Transient mean of the CPU usage on all the active CCU/CSU
Rate boards of the MSC server
Number of MGW Contexts Total number of VMGW contexts on the MSC server.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs .
Step 2 In the Filter Condition window, click Choose in the Operation group box.
Step 3 In the displayed Operation Select dialog box, view the operations related to the MSC Pool.
Step 4 Click OK.
Step 5 In the Filter Condition window, set the filtering conditions and then click OK.
The procedures are the same as those describes in 5.3.2 Querying Operation Logs. For details
of other operations related to logs, such as saving and printing query results, refer to 5 Log
Management.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool of the user and choose Subscriber Search from
the shortcut menu.
Step 3 In the displayed Search for subscribers, select the number type of the user to be found.
The number type can be MSISDN or IMSI. The meanings of the number types are as follows:
l MSISDN: indicates the international ISDN of a mobile station. The calling party is the
number that initiates the call attempt in the telephone network.
l IMSI: indicates the identity number of the international mobile subscriber. The IMSI number
is the only identity number for the subscriber in the network.
Step 4 Enter the number of the subscriber that you need to search in the Number field. Set the result
display mode as Basic Information or Full Information.
l If you choose Basic Information, the system displays only the information that you are most
concerned with, such as IMSI, MSISDN, and HLR No..
l If you choose Full Information, the system displays all the information about the subscriber,
for example, the calling number and the called number of the most recent call.
l If the user to be located is not available in this MSC Pool, a dialog box is displayed, informing you
that no related information about this user is found in this MSC Pool.
l If no MSC server is available in the Pool, a dialog box is displayed, informing you that no such MSC
server is found in this Pool.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
NOTE
If both CN NEs and AN NEs are available in the MSC Pool, you can view the relation between the MGW
and RAN.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 Select an MSC Pool in the navigation tree. Right-click it and choose Attribute from the shortcut
menu.
Step 3 In the left navigation tree of the Pool Property Settings dialog box, select Attribute.
Step 4 Click the Relation between MGW and RAN tab and select the view type.
You can view the relation between the MGWs and the RNC in a tree. For details of the view
type, refer to 12.6.6 Parameters for Viewing the Relation Between MGW and RAN.
----End
Related References
12.6.6 Parameters for Viewing the Relation Between MGW and RAN
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Context
NOTE
l Right-click on the topology view of the MSC Pool and choose Pool Maintenance Main Frame. The
Main Frame of the Pool Operation and Maintenance window.
l For details of other shortcut menus, such as alarm balloon tips display and alarm query, refer to the
related contents in 3 Topology Management and 2.2 Monitoring Network Alarms.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, select the MSC Pool whose topology structure you plan to view, and then
choose Topo from the shortcut menu.
Step 3 In the displayed Main Topology window, view the logical networking structure of the MSC
Pool.
NOTE
Double-click the core network icon and access network icon to display the core network
NEs and access network NEs separately in a box. Double-click and
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
l The auto-check task of the MSC Pool is available.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool to mange auto-check tasks, and choose Data
Consistency Check > Automatic Check from the shortcut menu.
Step 3 Click the Check Task tab. Then, you can manage the auto-check task as required.
Browse detailed information about the l In Task Table, you can view the detailed
task information, such as Task Name, Check
Plan, Nes, Data Items, and Task Status.
l In Task Result, you can view the details of the
task execution, such as Task Name, Result,
Acknowledgement, Last Check Time, Nes,
and Data Items.
Modify the information about the task 1. Select the task to be modified in Task Table.
2. Either double-click the task or click Modify.
3. In the displayed Modify an Automatic Check
Task dialog box, modify the information as
required.
4. Click OK.
Delete the auto-check task 1. Select the task to be deleted in Task Table.
2. Click Delete.
3. In the displayed Message dialog box, click
Yes.
Activate the auto-check task 1. In Task Table, choose a task whose Task
Status is Suspended.
2. Right-click Active. Then, the system performs
the task based on the scheduled period.
Suspend the auto-check task 1. In Task Table, choose a task whose Task
Status is Activated.
2. Right-click Suspend. Then, the system does
not perform the auto-check task.
NOTE
When managing the auto-check tasks of multiple Pools, you can click on right of the Pool box to
easily switch between different Pools.
----End
Related References
12.6.9 Parameters for Setting the Auto-Check of MSC Pool
summarize the performance data reported by NEs and get the counter data applicable for the
entire network.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Use either of the following methods to open the Performance Report window.
Method Operation
2
1. Choose Maintenance > Pool Management or click on the toolbar.
2. Select an MSC Pool in the navigation tree and choose Performance Query from
the shortcut menu.
Step 2 Right-click the performance report in the navigation tree and choose Query from the shortcut
menu.
For information about each performance report, refer to 7.5 MSC POOL Report Group.
Step 3 In the displayed Report Condition Setting dialog box, set the query conditions.
1. Select the time dimension in Time dimension.
Then the system summarizes the performance counter results of the query objects based
on the time dimension. For example, if Time dimension is set to Hour, the system
summarizes the performance counter results at a regular interval of one hour.
2. Select the query object in Object dimension.
For Pool performance counters, the object dimensions are LocalSection level, NE level,
and Pool level. The respective meanings are as follows:
l LocalSection level: The system summarizes the data of the same local network of
different NEs in a Pool. For example, call attempts of local network 1(all)=call attempts
of local network 1 (msc1)+call attempts of local network 1(msc2).
l NE level: The system summarizes the data of all objects of one MSC server in a Pool.
For example, call attempts of MSC 1=call attempts of local network 1 (msc1)+call
attempts of local network 2 (msc1)+call attempts of local network 3 (msc1).
l Pool level: The system summarizes data of all the MSC servers in a Pool. For example,
call attempts of a Pool=call attempts of MSC 1+call attempts of MSC 2.
3. Select the query object in Object range.
4. Select the query time in the Date selection and Time segment selection group boxes.
NOTE
For details of the operations related to performance reports, such as filtering reports, setting query templates,
and setting display conditions, refer to 7 Performance Report Management.
----End
In an MSC Pool, one RNC/BSC is connected to multiple MSC servers in the pool. Therefore,
when the MS/UE in the RNC/BSC service area initiates a new service request, the RNC/BSC
needs to select a serving MSC server for the service. For details, see Table 12-7.
The MS/UE initiates a According to the load balancing algorithm, the RNC/BSC selects
service based on the IMSI a valid MSC server for the MS/UE based on the proportion of
or IMEI. subscriber capacity of the MSC servers in the MSC Pool. If an
MS/UE initiates a service using IMSI, the selected MSC server
distributes a TMSI containing the NRI of the MSC to the MS/UE.
As shown in Figure 12-4, if the available capacity of MSC
server1 is 4, the available capacity of MSC server2 is 3, and the
number of MSs/UEs is 7, then the RNC/BSC assigns four MSs
to MSC server1 and three to MSC server2 to ensure the load
balance.
The MS/UE initiates a The RNC/BSC selects the serving MSC server for the MS/UE
service based on the according to the mapping between the NRI and MSC server.
IMSI. NOTE
When the selected MSC server is invalid or no mapping is available
between the NRI and the MSC server, the RNC/BSC uses the load
balancing algorithm and distributes MSC server according to the
proportion of subscriber capacity of the MSC servers. Then, the selected
MSC server assigns a TMSI containing the office NRI to the MS/UE.
The MSC server pages The RNC/BSC temporally saves the mapping between the MSI
the called MS/UE based and the paged MSC server. When the paged MS/UE pages the
on the IMSI. corresponding network based on the IMSI, the RNC/BSC selects
the MSC server according to whether the NRI is available on the
MS/UE.
l If the NRI is available on the MS/UE, the RNC/BSC selects
an MSC server according the mapping between the NRI and
the MSC server.
l If the NRI is unavailable on the MS/UE, the RNC/BSC selects
the MSC server according to the temporally saved mapping
between the IMSI and the MSC server.
NOTE
If the selected MSC server is invalid or the system fails to select the MSC
server according to the mapping, the RNC/BSC selects an MSC server
according to the load balancing algorithm.
CAUTION
l When the RNC/BSC detects that the signaling point of the MSC is inaccessible, the RNC/
BSC considers the MSC to be faulty or invalid.
l The proportions of subscriber capacity of the RNC/BSC to each MSC server needs to be
configured statically on the RNC/BSC.
In addition, the MSC servers can notify the subscriber capacity regularly, and the RNC/
BSC dynamically adjusts the proportion of subscriber capacity of MSC servers according to
the subscriber capacity of each MSC server in the notification. This mode, however, only
applies to the case that all MSC servers in the MSC Pool and BSCs and RNCs in the MSC
Pool area are Huawei equipment. For other modes, the RNC can configure the subscriber
capacity of MSC servers statically.
l The subscriber capacity of an MSC server described previously is the total number of
subscribers of the MSC server (number of licensed subscribers for the MSC server).
However, when an MSC server connects with RNCs or BSCsoutside the MSC Pool, the
subscriber capacity reserved for these RNCs or BSCs needs to be subtracted from total
capacity as for calculation of subscriber capacity of the MSC server.
Transferring all subscribers on the When you update one or more MSC servers in an
MSC to other MSCs MSC Pool, you need to transfer all the users on the
MSC servers to other MSC servers in the MSC Pool
and then upgrade the MSC servers to ensure the
normal operation.
Transferring a certain ratio of l When the loads of an MSC Pool are unbalanced,
subscribers on the MSC to other MSCs you need manually adjust the loads. Manual load
adjustment is common during network
Transferring a certain number of adjustment.
subscribers on the MSC to other MSCs
l After updating an MSC server, you need transfer
some users of other MSC servers to the updated
MSC server.
Transferring the subscribers with l By using this transfer mode, you can provide
specified RNC on the MSC to other special service which is provided on only a
MSCs specified MSC server for users in a specified area.
To achieve this, you need to transfer specified
Transferring the subscribers with users on the RNC or BSC to this MSC server.
specified BSC on the MSC to other
l Before the Pool is split, you must distribute the
MSCs
users to the specified MSC server based on the
relation between the users and the MSC servers.
l Adjust the link between the MSC server and the
RNC or BSC.
Transferring the subscribers with By using transfer mode, you can provide special
specified LAI on the MSC to other service, which is provided on only a specified MSC
MSCs server, for users in a specified area. To achieve this,
you need to transfer specified users on the LAI to
this MSC server.
Transferring the subscribers on the This mode transfers the users subscribed in MSC
MSC to other MSCs server 1 to MSC server 2 for the purpose of network
commissioning.
Related Tasks
12.5.1.3 Manual Transfer of Users
Related References
12.6.7 Parameters for Transferring MSC Pool Users Manually
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the MSC Pool.
l Before transferring users, you can view each NE's load in the current network through the
M2000 load supervision function and choose a proper transfer method.
Context
You can transfer users through 3GPP TS 23.236 protocol and inter-office E interface redirection.
The default transfer scheme is inter-office E interface redirection. For details, refer to 12.1.1
Basic Scheme of MSC Pool.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool to transfer users and choose Load Re-
distribution from the shortcut menu.
The system displays the Load re-distribution-Select a type dialog box.
Step 3 Choose the distribution method according to your requirements, and then click Next.
See 12.5.1.2 Mode for Manual Transfer of Users for detailed information on distribution
methods.
Step 4 Run different operations according to the user distribution methods.
Transferring all subscribers on the MSC 1. Choose the MSC server from which the users
to other MSCs are transferred in the Source NE.
2. In the Destination NE, select a destination
MSC server.
3. Enter the load balancing ratio of the
destination NE in the Load ratio field. Click
Allocate load ratios, and the system
automatically generates the load ratios
according to the remaining capacity of the
destination NE. This ensures the load
balance of each destination NE.
4. Select the user distribution speed in the Re-
distribution speed drop-down list.
NOTE
l If the preset destination NE cannot hold all the
migrated users, the system displays that the the
destination NE has insufficient capacity. In this
case, you need to select the destination NE again.
l The Medium speed is recommended for the Re-
distribution speed.
Transferring the subscribers with 1. Select the RNC in the Candidate RNC list
specified RNC on the MSC to other MSCs box and then click Next.
2. The operation is the same as that whose
transferring method is Re-distribution all
subscribers on the MSC to other MSCs.
Transferring the subscribers with 1. Select the BSC in the Candidate BSC list
specified BSC on the MSC to other MSCs box, and then click Next.
2. The operation is the same as that whose
transferring method is Re-distribution all
subscribers on the MSC to other MSCs.
Transferring the subscribers with 1. Select the LAI in the Candidate LAIs list
specified LAI on the MSC to other MSCs box, and then click Next.
2. The operation is the same as that whose
transferring method is Re-distribution all
subscribers on the MSC to other MSCs.
Transferring the subscribers on the MSC 1. In the Number Type, choose the number
to other MSCs type of the transferred users.
2. In the Source NE, select the MSC server
from which users are transferred.
3. Enter the subscriber number in the Enter the
subscriber number list.
4. In the Destination NE, select a destination
MSC server.
NOTE
l You can choose only one source and destination
MSC server.
l Up to 10 users of specified numbers can be
transferred.
l The Number Type of all the transferred users can
only use IMSI or MSISDN at the same time. The
two cannot be mixed in use.
See 12.6.7 Parameters for Transferring MSC Pool Users Manually for detailed information
on the parameters.
CAUTION
l If an MSC server is operating a transfer task, it cannot serve as a source NE and a destination
NE for the transfer.
l If an MSC server is acting as the destination of a transfer task that is in process, the server
can be specified as the destination of another transfer task.
----End
Postrequisite
You can view the transfer progress in the task list of the Main Interface. For details of the Main
Frame for MSC Pool operation and maintenance, see 12.6.1 Interface Description: Main
Interface of MSC Pool OM.
Related Concepts
12.5.1.2 Mode for Manual Transfer of Users
Related References
12.6.7 Parameters for Transferring MSC Pool Users Manually
the MSC Pool service, you can shield this data. The shielded data is not checked in future
automatic or automatic checks. You can restore the shielded data.
12.5.2.4 Synchronizing MSC Pool Data
In an MSC Pool, certain configuration data must be consistent on all the MSC servers or MGWs.
When the data is inconsistent, you can synchronize the data to ensure the consistency.
Related Tasks
12.3.2 Creating the Task of Auto-Checking MSC Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
l At least one auto-check task is performed.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click an MSC Pool, and choose Data Consistency Check >
Automatic Check from the shortcut menu.
The Automatic Check tab is displayed.
NOTE
You can also view the check results in the area about data consistency in Main Frame. By double-clicking
a record, you can view the Automatic Check tab page.
Step 3 Click the Check Task tab. Select the task to be viewed in Task Table.
In Task Result, you can view the details of the task execution, such as Result, Nes, and Last
Check Time. After you select a record whose Result is Inconsistent or Abnormal, you can
perform the following operations:
Operation Description
Step 4 In Task Result, select a result whose Result is Inconsistent or Abnormal. Click Result
Detail or the Check Result tab.
NOTE
l The Inconsistency Data tree displays the inconsistent data in the check result.
l You can view the detailed check results in the group box beside the Inconsistency Data tree. The
inconsistent data is in red.
l Click Export Result to save the check results containing the inconsistent data to a .csv file.
l You need to manually synchronize the inconsistent data. For details, see 12.5.2.4 Synchronizing MSC
Pool Data.
l If the inconsistent data does not affect the MSC Pool service, you can click Manual Check and then
shield this data. For details, see 12.5.2.3 Setting the Checking Items of MSC Pool Data.
----End
Related Tasks
12.5.2.3 Setting the Checking Items of MSC Pool Data
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, right-click the MSC Pool for which you plan to check the data, and choose
Data Consistency Check > Manual Check&Synchronize Data from the shortcut menu.
The Manual Check dialog box is displayed.
Step 5 Select the data items in the Select Data Item group box.
NOTE
NOTE
l Before checking the data, the M2000 server requests NEs for the data to be checked, thus ensuring the
consistency between the data on the M2000 server and the data on the NEs.
l If the M2000 fails to obtain the NE data, the group box at the bottom of the progress bar displays the
failure details. Then, the system extracts and checks the data cached on the M2000 server.
Step 7 On the Manual Check tab page, view the check result.
l If inconsistent data exists, the Inconsistency Data tree displays the data. The group box
displays the detailed check result and highlights the inconsistent data in red.
l If the data is consistent, the Inconsistency Data tree does not display any data.
l When the system extracts and checks the data cached on the M2000 server, the right bottom
of the Manual Check tab page displays The check data may be not the
latest data..
----End
Postrequisite
l If data inconsistency exists, you need manually synchronize the data. For details, see
12.5.2.4 Synchronizing MSC Pool Data.
l If the inconsistent data does not affect the MSC Pool service, you can shield this data. The
shielded data is not checked in future automatic or automatic checks. For details, see
12.5.2.3 Setting the Checking Items of MSC Pool Data.
Related Tasks
12.5.2.3 Setting the Checking Items of MSC Pool Data
12.5.2.3 Setting the Checking Items of MSC Pool Data
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the MSC Pool.
Procedure
l Shield data checking items.
1. Check the data of the MSC Pool manually. For details, refer to 12.5.2.2 Manually
Checking MSC Pool Data.
2. In the Inconsistency Data tree, right-click the data to be shielded and choose
Shield from the shortcut menu.
– You can press Ctrl or Shift to select multiple records.
– After the data is shielded, the corresponding background color of the NE record
turns grey.
– You can right-click the NE record of the shielded data item and choose Resume
from the shortcut menu to restore the shielded data.
3. Click Close to close the Manual Check dialog box.
l Restore the shielded checking items.
1. Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
2. Right-click the MSC Pool of which the data checking items are shielded and choose
Data Consistency Check > Cancel the Shield Status of Check Item from the
shortcut menu.
3. Select the data and NEs to be restored in Shielded Item.
4. Click OK.
----End
Result
The setting takes effect at the next automatic or manual check.
Related Tasks
12.3.2 Creating the Task of Auto-Checking MSC Pool
12.5.2.2 Manually Checking MSC Pool Data
12.3.2 Creating the Task of Auto-Checking MSC Pool
12.5.2.2 Manually Checking MSC Pool Data
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform the associated operations.
l The configuration data that must be consistent with all the MSC servers and MGWs in the
Pool is inconsistent.
Context
On the basis of data inconsistency, the M2000 generates MML commands to adjust the data.
These commands are issued to the relevant NEs to adjust NE data and achieve data consistency.
NOTE
For certain NE data, the system cannot generate data adjustment command on the M2000. You can view
a message in the right pane of the Manual Check tab page, showing the specific data that is not supported.
In this case, adjust the data through the LMT of the NE.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 In the navigation tree, choose an MSC Pool and check Pool data.
You can check the data by using either of the following methods:
Method Description
Manually Checking MSC Pool Data For details, see 12.5.2.2 Manually
Checking MSC Pool Data.
In the consistency status area of Main Frame, 1. Double-click the record whose
double-click the record whose Result is Result is Inconsistent.
Inconsistent and manually check the data again. 2. In the displayed Automatic Check
dialog box, click Manual Check on
the Check Task tab page.
3. After setting the data check items in
the displayed Manual Check dialog
box, click Start Check.
Step 3 In the Inconsistency Data tree of the Manual Check tab page, select the data to be synchronized.
You can select a data item or a data type.
Step 4 Click Synchronize.
Step 5 Select an NE in Reference NE.
The system uses the data of this NE as the reference of the synchronization.
Step 6 Select the NEs to be synchronized in Destination NE.
Step 7 Click Generate MML.
The right pane on the Manual Check tab page displays the details of the MML commands.
NOTE
l Edit the MML commands in the right pane. Alternatively, click Save MML to save the MML
commands as files for subsequent operations.
l If the data in Destination NE is consistent with that in Reference NE, the right pane displays a message
showing that the data is consistent and displays the specific value.
l If a data item does not support a certain generated MML command, the right pane also displays a
message, showing that the data does not support the MML command. In this case, adjust data through
the LMT of the NE.
l The right pane can display a maximum of 500 lines of MML commands. When the MML commands
have more than 5000 lines, the system displays that the MML commands are excessive. In this case,
you need to click Export MML and manually edit the MML commands. Then, send the script file to
the NE through the M2000. For details, see 14.2.1 Creating MML Command Script.
Step 8 Click Send MML to select the issuing mode, and then issue the MML commands.
NOTE
l When the MML command is being issued, you can click Terminate MML to terminate the command
issuing.
l The execution process of the MML commands is displayed in an MML message in the right pane. In
the MML message, Total Count indicates the number of MML commands to be sent, Success
Count indicates the number of MML commands that are successfully run on the NE, Fail
Count indicates the number of MML commands that fail to be run on the NE, and Unsent
Count indicates the number of MML commands that fail to be sent by the M2000.
l For the MML commands that fail to be issued by the M2000 and those fail to be run on the NE, you
can get the related information by checking the MML messages returned from the NE.
Step 9 Click Backward and repeat Step 3 through Step 8 to synchronize other data.
----End
Postrequisite
Click Export Result on the Manual Check tab page to save the results of the MML commands
to a file.
1 MSC Pool The created MSC Pool and the NEs in the pool are
object area displayed in a navigation tree.
The MSC Pool object area provides a shortcut menu so
that you can perform maintenance operations on the pool,
such as parameter configuration, user migration, and user
search.
SN Name Description
2 Status area for This area periodically refreshes and displays the number
load balancing of all current pool users of the MSC server within the pool,
the capacity load, and the load balance status of the Pool.
The load balance status of the Pool can be Normal,
Exception, or Unchecked.
l Normal: The loads between each MSC server within the
Pool are balanced.
l Exception: The offset between the highest loads the
lowest load of the MSC server within the Pool exceeds
the threshold.
l Unchecked: The number of MSC servers within the
Pool is smaller than 2 and the system cannot identify
the state of the Pool.
3 Status area for Shows the operation results of all the auto-check tasks.
data The status for data consistency is classified into four types:
consistency Unacknowledged, Inconsistent&Acknowledged,
Inconsistent&Unacknowledged, and Consistent. The
respective meanings are as follows:
l Unchecked: indicates that no auto-check task is
available or the auto-check tasks are not executed.
l Inconsistent&Acknowledged: indicates that data
checked between the NEs is inconsistent and that the
checking result is already acknowledged.
l Inconsistent&Unacknowledged: indicates that the data
checked between the NEs is inconsistent and that the
checking result is still unacknowledged.
l Consistent: indicates that the data checked between the
NEs is consistent.
4 Task list This area displays the information about manual user
transfer and data synchronization tasks.
This area provides a shortcut menu so that you can perform
the following operations on the task records:
l Refreshing the task list.
l Viewing the detailed task information.
l Stopping a task.
l Viewing the operation results.
l Deleting a task.
The MSC Pool alarm browse interface composes of current alarm browse interface and event
alarm browse interface. When the viewing conditions are set, detailed information about the
related alarms is displayed in either the Current Fault Alarms or the Event Alarms window.
If you select an alarm from the list, the system displays its detailed information and handling
suggestions. Figure 12-6 shows the interface.
Related Tasks
12.4.1 Viewing the Alarms of MSC Pool
12.4.1.1 Viewing the Current Fault Alarms of MSC Pool
12.4.1.2 Viewing the Event Alarms of MSC Pool
CAUTION
When the MSC Pool manages only the access network, the features of the Pool Parameter
Setting are as follows:
l The CN ID Setting tab and the Non-broadcast LAI Setting tab are not available.
l The NE Status Maintenance tab has no MGW Segregate Status.
l The CN ID-NRI Setting tab has no NE Name field.
l The CN Node Status on the NE Status Maintenance tab does not have the MSCServer
NE field.
When the MSC Pool manages only the CN, there is no PLMN setting function.
CN ID Setting Displays the CN IDs of all MSC servers in the MSC Pool. You can modify
the CN IDs as required.
CN ID-NRI Displays the NRIs of the MSC servers in the MSC Pool. You can add or
Setting modify the NRIs.
l Add: to expand the maximum users that the MSC server can
accommodate.
l Modify: to adapt to he network adjustment.
Tab Description
Non- Displays the Non-broadcast LAIs of the MSC servers in an MSC Pool. You
broadcast LAI can modify the Non-broadcast LAIs as required.
Setting
Load Balance Displays the capacity of MSC servers in an MSC Pool. Provides the function
Parameter of changing the available capacity of MSC servers. In this way, you can plan
the available MSC server capacity within the pool according to the actual
situations. In addition, you can balance user allocation based on the set user
capacity when instructing the RNCs or BSCsto access users. For example,
after an MSC server is expanded, you need modify its available capacity in
the Pool.
NE Status Provides the functions of setting maintenance states of NEs in an MSC Pool,
Maintenance such as MGW segregation state and CN node state.
l MGW states are Normal and Segregate.
l The state of a CN node can be Normal, OffLoad, or Forbidden.
For detailed description of MGW segregation status and CN node status, see
12.6.14 Parameters for Setting NE State of MSC Pool.
Advanced Provides the function of setting the NRI length, Null NRI value, and carrier
Setting of the MSC Pool.
Related Tasks
12.2 Creating MSC Pool Topology on the M2000
12.2 Creating MSC Pool Topology on the M2000
Parameter Description
Parameter Description
Parameter Description
Optional Nes This list in the form of a navigation tree provides the NEs that can be
added to the MSC Pool.
Based on the NEs that are connected to the M2000 and the selected
networking type of the Pool, the system automatically filters the NEs
that can be added to the MSC Pool.
Selected Nes The list in the form of a navigation tree shows the NEs that are already
selected in the MSC Pool.
Related Tasks
12.2 Creating MSC Pool Topology on the M2000
12.2 Creating MSC Pool Topology on the M2000
Parameter Description
Parameter Description
Number of NE Indicates the number of the NEs and the specific NEs
within the MSC Pool. For example, MSC server(2)
MGW(0) RNC(0) BSC(0)indicates that the MSC Pool
contains two MSC servers.
Parameter Description
CN ID and NRI Relation Indicates the mapping relation between each CN ID value
and its corresponding NRI value in the MSC Pool. For
example, 1-1,2-2,2-4 indicates that:
l When CN ID = 1, its corresponding NRI = 1.
l When CN ID = 2, its corresponding NRI = 2 and 4.
NRI Length Indicates the NRI length configured by the NEs within
the MSC Pool.
Parameter Description
Parameter Description
Choose ViewStyle Select the method to view the relation between the MGW
and the RAN.
l Query by MGW: In the Root navigation tree, the
MGW acts as the first node, which shows the RNCs/
BSCs under different MGWs.
l Query by RAN: In the Root navigation tree, the RNC/
BSC acts as the first node which shows the RNCs/
BSCs under an MGW.
Related Tasks
12.4.5 Viewing the Relation Between MGW and RAN
Re-distribution Transfers all uses on one or multiple MSC servers to other MSC servers in
all subscribers the MSC Pool.
on the MSC to
other MSCs
Re-distribution Transfers a certain ratio of users on one or multiple MSC servers to other
a certain ratio of MSC servers in the MSC Pool.
subscribers on
the MSC to
other MSCs
Re-distribution Transfers a certain number of users on one or multiple MSC servers to other
a certain MSC servers in the MSC Pool.
number of
subscribers on
the MSC to
other MSCs
Re-distribution Transfers the specified RNC users on one or multiple MSC servers to other
the subscribers MSC servers in the MSC Pool.
with specified
RNC on the
MSC to other
MSCs
Re-distribution Transfers the specified BSC users on one or multiple MSC servers to other
the subscribers MSC servers in the MSC Pool.
with specified
BSC on the
MSC to other
MSCs
Re-distribution Transfers the specified LAI users on one or multiple MSC servers to other
the subscribers MSC servers in the MSC Pool.
with specified
RNC on the
MSC to other
MSCs
Re-distribution Transfers the users with the specified number on one MSC server to other
the subscribers MSC servers in the MSC Pool.
on the MSC to
other MSCs
Source NE Lists all MSC servers in an MSC Pool. You can select
one or more MSC servers to transfer their users.
Load ratio Defines the load ratio, which is the basis of distributing
the transferred users to the destination NEs.
NOTE
The sum of all the load ratios of destination NEs is 100%.
You can manually enter the load ratio of target NEs or
click Allocate load ratios. Then the system generates
the load ratios based on the idle capacity of the
destination NE and thus ensure the load balance of each
target NE.
Candidate RNC Displays all the RNCs in an MSC Pool. You can select
one or more RNCs to transfer their users from the
source NEs.
This parameter is valid only when the transfer mode is
Re-distribution the subscribers with specified RNC
on the MSC to other MSCs.
Parameter Description
Candidate BSC Displays all the BSCs in an MSC Pool. You can select
one or more BSCs to transfer their users from the
source NEs.
This parameter is valid only when the transfer mode is
Re-distribution the subscribers with specified BSC
on the MSC to other MSCs.
Candidate LAIs Displays all the LAIs in an MSC Pool. You can select
one or more LAIs to transfer their users from the source
NEs.
This parameter is valid only when the transfer mode is
Re-distribution the subscribers with specified LAI
on the MSC to other MSCs.
Related Concepts
12.5.1.2 Mode for Manual Transfer of Users
Related Tasks
12.5.1.3 Manual Transfer of Users
Parameter Description
Parameter Description
Enter the subscriber number Indicates the number of the users to be transferred.
NOTE
You can enter a maximum of 10 subscriber numbers.
Parameter Description
Parameter Description
Parameter Description
Find Used to quickly find the data item to be checked. Supporting case
insensitive search rather than wildcard search.
Enter the data item in the Find text box and click Find Next. The system
automatically selects the first mapping data item in the Data Item
navigation tree. You can click Find Next and Find Prev to select the
data item to be checked.
Data Item Indicates the data items to be checked. The Data Item group box lists all
the data items that are configured on each MSC server or each MGW in
the Pool.
Check Period Indicates the period for the system to regularly check the data of NEs
within the Pool.
The check periods are: Everyday, Every week, Every month, and
Single time. Single time indicates that this auto-check task is performed
only once.
NOTE
If you set the Check Period to Every month and the set Day is not available every
month, for example 31, the system performs the checking task on the last day of
that month by default in the month of fewer than 31 days.
Day Indicates that the system checks the data of the NEs within the Pool in a
specific day of a scheduled week in a month. This parameter is valid only
when Check Period is Every week or Every month.
Check Time Indicates the specific time for the system to check the data of NEs within
the Pool.
NOTE
When Check Period is Single time, the Check Time should be later than the
current time of the system.
Related Tasks
12.3.2 Creating the Task of Auto-Checking MSC Pool
12.4.7 Managing the Task of Auto-Checking MSC Pool
Parameter Description
Parameter Description
Parameter Description
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related Tasks
12.3.3.3 Setting CN ID of an MSC Server
Parameter Description
Parameter Description
Local Office NE Name of the MSC server that is configured with the mapping
between the NIR and the CN ID
NOTE
l If the MSC Pool manages only the access network, this parameter is
not displayed on the client.
l After you modify the NRI of an MSC server, the NE Name column of
the original NRI is displayed as Unknown ne. You need to delete this
record.
NRI The value of NRI corresponding to the MSC server in the pool
Value range: 0 to 1023.
NOTE
The NRI values for different MSC servers within the same Pool should
not be identical.
Parameter Description
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related Tasks
12.3.3.4 Adding the NRI of MSC Pool
12.3.3.5 Setting the Mapping Between NRI and CN ID
Parameter Description
Parameter Description
Local Office NE Name of the MSC server that is configured with Non-
broadcast LAI
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related Tasks
12.3.3.8 Setting the Non-Broadcast LAIs of MSC Pool
Parameter Description
NOTE
When the MSC Pool networking type is access network, the load balancing parameters are CN ID, Pool
Available Capacity, and Consistency. When the MSC Pool networking type is core network only or
core&radio access network, the load balancing parameters are Local Office NE, License Capacity, Pool
Available Capacity, and Consistency.
Parameter Description
Local Office NE Indicates the name of each MSC server in the Pool
This parameter is available only when the MSC Pool
networking type is access network or access
network&core network.
Parameter Description
Pool Available Capacity Indicates the actual user capacity of the MSC server
in the Pool. After the pool is initially established, by
setting the pool available capacity of the MSC server,
you can balance user allocation according to the
defined user capacity when guiding the NNSF node,
that is, MGW, RNC, and BSC, to access users.
The pool available capacity is the converted capacity
value of the license capacity. For example, if an MSC
server in the pool is connected to an RNC/
BSCoutside the pool, the pool available capacity of
the MSC server in the pool equals the user capacity
provided outside the pool subtracted from the license
capacity.
NOTE
l The value of Pool available capacity ranges from 0 to
the license capacity.
l The user capacity for an RNC/BSC outside the Pool is
defined during the planning of the MSC Pool network.
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related Tasks
12.3.3.7 Setting the Load Balancing Parameters of MSC Pool
CAUTION
When an MSC Pool manages only the RAN, the MGW state parameters are not displayed on
the M2000 client.
Parameter Description
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related Tasks
12.3.3.9 Setting the Maintenance State of NEs in MSC Pool
Parameter Description
Parameter Description
NRI The length of NRI Length of the NRI Value range: 1-10
The value of Null NRI Value of the Null NRI Value range: 0-1023.
Parameter Description
Related Concepts
12.3.3.1 Parameters of MSC Pool Attributes
Related Tasks
12.3.3.6 Setting the Null NRI or the Length of NRI
12.3.3.10 Setting the Operator for MSC Pool
Parameter Description
Parameter Description
Threshold of Indicates the threshold value of the load unbalance alarm for the MSC
capacity offset Pool. When the difference between the maximum and minimum load of
the MSC server within the MSC Pool exceeds this threshold value. the
system reports the load unbalance alarm for the MSC Pool. Load of the
MSC server equals the ratio of the number of the current MSC server
subscribers to the total user capacity of the MSC server. Automatic
detection period
Parameter Description
Automatic The system periodically detects the interval of each MSC server load
detection period within the MSC Pool. The check periods are5 minutes, 15 minutes,30
minutes,1 hour,2 hours,6 hours,12 hours, and 24 hours.
Related Tasks
12.3.1 Setting an Alarm for MSC Pool Load Imbalance
This describes the CDMA pool, which is comprised of multiple MSCes. The CBSC of the access
network connects to all MSCes in the pool. If the network is deployed as a CDMA pool, user
services are distributed to MSCes on the basis of the capacity proportion of each MSCe. In this
way, you can balance the traffic of MSCe in the pool in different regions on weekdays or
weekends. Therefore, operators calculate the device investment on the basis of the maximum
traffic of the city rather than that of each region. This helps operators to optimize network
capacity and reduce the investment. You can configure data, monitor the performance, and
maintain the CDMA pool network through the M2000 client.
Background
Owing to the mobility of subscribers, population density, and calling difference, the traffic varies
largely in different regions at different time. In the case of holidays, the communications
networks are heavily loaded in high-traffic regions, which leads to the unstability of devices.
The devices in low-traffic regions, however, are not completely utilized. To deal with the traffic
peak, operators have to provide support for redundant configurations to enhance reliability. This
increases the investment. The CDMA pool solution provided by Huawei is intended for the
previous problem.
Compared with the traditional solution, the pool technology provides the following features:
l Balancing the load between MSCes to improve the resource efficiency of the entire CN
and to reduce the investment on devices
l Providing disaster recovery and backup at MSCe level
When a MSCe in the pool is faulty, the services of the faulty MSCe are handed over to
other MSCes in the pool. Therefore, no services are affected.
l Reducing the location update between the MSCe and the HLR, and lowering the signaling
traffic of the C and D interfaces to improve the capacity of the MSCe.
l Reducing handoffs between different MSCes to improve conversation quality.
l Simplifying the network planning The planning for the CN and AN is separated.
l Reducing the work load incurred by cut over and improving network reliability
Figure 13-1 shows the networking topology of the M2000 in the CDMA pool.
Operation Rights
Monitor load in real time, search for users, If the CDMA pool is in the management
manually check CDMA pool data, view domain of a user, you can perform these
CDMA pool information, and view pool operations.
topology For details about how to set the management
domain of a user, refer to 4.5.11 Setting the
Managed Domain for an OM User.
Create, modify, and delete the CDMA pool, You can perform these operations if you have
configure alarm parameters of the pool, view relevant rights.
the performance of the pool, transfer users, You can create a CDMA pool provided that
manage the automatic check of pool data, you have the application rights of the M2000.
configure pool parameters, and synchronize For operations other than creating CDMA
poll data pool, you need to have network device rights.
For details on the setting of user operation
rights, refer to 4.5.10 Assigning Operation
Rights to an OM User.
NOTE
l After a user is authorized to create, modify, or delete a CDMA pool, the system automatically grants
the view right of the pool to the user. That is, the user can view the pool in the administration domain.
l After a user creates a CDMA pool, the user is automatically authorized to modify, delete, and view the
pool.
l By default, the Guests and Operators user groups own the new equipment rights of the CDMA pool.
For details about the new equipment rights, see 4.6.2.3 Modifying the Authority to the New Devices
in an OM User Group.
l The pool object takes priority over the NEs in the pool on function authorization. That is, if a function
of the pool is authorized but the NEs in the pool are not authorized to perform this function, the function
of the pool can still be performed.
For example, the pool parameter configuration function needs to issue configuration commands to the
NEs in the pool. If a user is authorized to configure the parameters of the pool object rather than issue
commands to the NEs in the pool, the user still can issue configuration commands to the NEs in the
pool by using the pool parameter configuration function.
Each MGW contains two tables, namely, user block table and MSC capacity indicator table. The user block
table is exported from the MSC capacity indicator table by using a specific algorithm. After you configure
or modify the MSC capacity indicator table, the MGW automatically updates the user block table.
For example, the capacity proportion of three MSCes is 1:1:3. The configuration of the user
block table is listed in Table 13-2.
0 to 199 20% 1
Basic Concepts
Table 13-3 describes the basic concepts concerning the CDMA pool.
Concept Description
Concept Description
MSC pool area If one or more CBSCs belong to an MSC pool, the
service areas covered by the CBSCs form an MSC
pool area, as shown in Figure 13-2.
The subscribers in the pool area are served by the
MSCs in the MSC pool.
1. Based on the connection status of the MSCe, the MGW automatically connects to MSCes
that function well and assigns the users to the MSCes on the basis of capacity proportion.
2. The MGW then transfers users according to the user blocks mapping to the MSCe on the
user block table.
Prerequisite
l Relevant NEs support the A-Flex function and are configured on the basis of network
planning.
l Relevant NEs have been connected to the M2000.
l You are authorized to create a CDMA pool.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 In the navigation tree, right-click the CDMA Pool node and choose Create CDMA Pool from
the shortcut menu.
Step 3 Set the pool information in the displayed Create CDMA Pool dialog box.
1. Enter the pool name in Pool Name.
2. Select the networking type of the CDMA pool group box on the right pane of Pool
Name.
NOTE
The supported networking type is Core Network Only, you can select MSCe and MGW.
3. Select the NEs to be added to the Pool in Optional NEs. Click . The NEs
are added to Selected NEs.
l In Optional NEs, you can use the key Shift or Ctrl to select multiple NEs at a time.
l You can click to add all NEs in Optional NEs to Selected NEs.
----End
Postrequisite
1. After a pool is created, you need to perform initial configuration and data check for the
pool to check whether the configurations of the CDMA pool are correct.
For details about how to perform initial configuration for the pool, refer to 13.3 Initial
Configuration of CDMA Pool. For details about how to perform data check, refer to
13.5.2.2 Manually Checking CDMA Pool Data.
If the configuration data that must be consistent with all the NEs in the pool is inconsistent,
you need to synchronize the data on the basis of reference values. For details, refer to
13.5.2.4 Synchronizing CDMA Pool Data.
2. After the data are correctly configured, you can start the pool to perform routine operations
and maintenance.
For details about routine operations and maintenance, refer to 13.4 Routine Maintenance
of CDMA Pool.
Related References
13.6.4 Parameters for Creating/Modifying CDMA Pool
13.6.3 Interface Description: CDMA Pool Configuration
13.6.4 Parameters for Creating/Modifying CDMA Pool
13.6.3 Interface Description: CDMA Pool Configuration
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
The type of the CDMA pool load imbalance alarm is Fault Alarm, and the alarm severity is
Critical.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 In the navigation tree, select the CDMA pool whose alarms for load imbalance need to be set.
Right-click the pool and choose Property from the shortcut menu.
Step 3 In the navigation tree in the left pane of the Pool Properties Settings dialog box, select Alarm
load balance parameters and set the alarm threshold and automatic check period.
For details about the parameters, refer to 13.6.10 Parameters for Setting Load Unbalance
Alarm of CDMA Pool.
If the configuration of alarm parameters fails, the detailed reason for the failure is displayed in the
Message dialog box.
----End
Result
The status of load balance is categorized into three types, namely, normal, exception, and
unchecked. When a load alarm is generated, Pool load balance status:
Exception is highlighted in red in the right pane of the Pool Management dialog box.
Postrequisite
l You can check detailed information about the CDMA pool load imbalance by querying
fault alarms. For details, refer to 13.4.1.1 Viewing the Current Fault Alarms of CDMA
Pool.
l When a load imbalance alarm is generated, you can manually transfer MSCe users to
balance the load of each MSCe in the pool. For details, refer to 13.5.1.2 Transferring
CDMA Pool Users Manually.
Related References
13.6.10 Parameters for Setting Load Unbalance Alarm of CDMA Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
The type of the alarm about inconsistent CDMA pool data is Event Alarm, and the alarm severity
level is critical. For details, see ALM-2 Data Inconsistency Alarm.
NOTE
You can manually check CDMA pool data. If the inconsistent data does not take effect on the CDMA pool
service, you can shield the data. The shielded data is not checked in future operations. For details, refer to
13.5.2.3 Setting the Checking Items of CDMA Pool Data.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 Select a CDMA pool whose tasks are to be check in the navigation tree, and then right-click the
task and choose Data Consistency Check > Automatic Check .
Step 3 In the displayed Automatic Check dialog box, click the Check Task tab and click Add.
For detailed description of the parameters, refer to 13.6.6 Parameters for Setting the Auto-
Check of CDMA Pool.
Step 5 Click OK.
The added automatic check task is displayed on the Check Task tab page.
----End
Result
The system automatically checks the tasks on the basis of the preset conditions. If inconsistency
occurs, a critical event alarm is generated.
Postrequisite
l In such a case, you can view the check results to learn the details about the data consistency.
You can manually synchronize the data to ensure the consistency of the data.
l For details about how to view check results, refer to 13.5.2.1 Viewing the Result of Auto-
Checking CDMA Pool Data. For details about how to manually synchronize data, refer
to 13.5.2.4 Synchronizing CDMA Pool Data.
Related Tasks
13.5.2 Checking CDMA Pool Data
Related References
13.6.6 Parameters for Setting the Auto-Check of CDMA Pool
Pool Available Capacity Indicates the real user capacity of the MSCe in the pool.
The value of available capacity in the pool is calculated
on the basis of license capacity. For example, if a MSCe
in the pool is connected to a CBSC outside the pool, the
value equals the result of subtracting the capacity of the
CBSC outside the pool.
After creating a pool, you need to set the available pool
capacity. When users are connected to the MGW, the
system distributes users according to the available pool
capacity. Thus, the load of each MSCe is balanced.
MGW Node State Indicates the status of the MGW. The status can either
be Normal or Inhibited..
After you set the MGW Inhibited status, the MGW exits
smoothly and has no impact on the user services.
Related Tasks
13.3.3.3 Setting the MSCe Server ID
13.3.3.5 Setting the Maintenance State of NEs in CDMA Pool
Related References
13.6.7 Parameters for Setting MSCe Server ID of CDMA Pool
13.6.8 Parameters for Setting Load Balancing of CDMA Pool
13.6.9 Parameters for Setting NE State of CDMA Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA Pool.
Context
If you need to view the pool parameters, you can choose Show the acquired detail list. The system
displays the detailed information about the pool parameters. For example, select an MSCe record
on the Load Balance Parameter tab page. The detail list displays all the capacity information
about the MSCe configured on the MGW.
NOTE
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Right-click a CDMA Pool in the navigation tree and choose Parameter Setting from the
shortcut menu.
The displayed Synchronize Pool Parameter Configuration Data dialog box displays the
refreshed configuration data. After the pool configuration data is successfully refreshed, the
system displays the Pool Parameter Setting dialog box.
NOTE
If the configuration data fails to be refreshed, the Synchronize Pool Parameter Configuration Data
dialog box displays the failure information. You can click Parameter Setting to enter the Pool Parameter
Setting dialog box.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
CAUTION
The change of MSCe server ID greatly affects network services. You need to set the MSCe
Server ID on the M2000 client after confirming the network planning.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Select the CDMA pool whose properties is to be viewed, right-click the pool and select
Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Configuration Data dialog box is displayed, showing the
progress of updating the configuration data. After the configuration data of the pool is updated,
the Pool Parameter Setting dialog box is displayed.
NOTE
If updating the configuration data fails, the detailed reason for the failure is displayed in the Synchronize
Pool Parameter Configuration Data dialog box. You can click Parameter Setting to display the Pool
Parameter Setting dialog box.
Step 3 Click the MSCe Server ID Setting tab, and choose the MSCe record whose ID needs to be re-
defined.
The value ranges from 0 to 7. The value of the ID cannot be the same as the existing MSCe server ID.
Step 7 Click Send in the displayed The MML Commands send to NE dialog box.
The system issues MML commands to the relevant MSCe NEs. The system also displays Send
Status and Send Result of the MML commands.
NOTE
l When the MML command is being issued, you can click Stop to stop issuing the MML command.
l If all MML commands fail to be issued, you can click Send to issue MML command again. If part of
the MML command cannot be issued, the Send icon is unavailable. You cannot issue the command
again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Setting dialog box.
----End
Related Concepts
13.3.3.1 Parameters of CDMA Pool
Related References
13.6.7 Parameters for Setting MSCe Server ID of CDMA Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 In the navigation tree, select the CDMA pool whose parameters for load balance need to be set.
Right-click the pool and select Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Configuration Data dialog box is displayed, showing the
progress of updating the configuration data. After the configuration data of the pool is updated,
the Pool Parameter Setting dialog box is displayed.
NOTE
If updating the configuration data fails, the detailed reason for the failure is displayed in the Synchronize
Pool Parameter Configuration Data dialog box. You can click Parameter Setting to display the Pool
Parameter Setting dialog box.
Step 3 Click the Load Balance Parameter tab, and choose the MSCe record whose available capacity
needs to be re-defined.
l You can view the maximum capacity of each MSCe in the pool on the Load Balance
Parameter tab page. The maximum capacity cannot be modified.
l If the M2000 fails to collect the data of certain MSCe, the value of the maximum capacity
is displayed as 0 on the Load Balance Parameter tab page.
l If you select the Show the acquired detail list checkbox, the capacity information about the
MSCe configured on the MGW is displayed in The detail list when you click an MSCe
record on the Load Balance Parameter tab page.
l For detailed description of the parameters on the Load Balance Parameter tab page, refer
to 13.6.8 Parameters for Setting Load Balancing of CDMA Pool.
Step 4 Double-click the record or click Modify.
Step 5 Enter the new available capacity of the MSCe in New Pool Available Capacity.
The value of real capacity ranges from 0 to the maximum value. The value of real capacity is
calculated on the basis of license capacity. For example, if an MSCe in the pool is connected to
a CBSC outside the pool, the value equals the result of subtracting the capacity of the CBSC
outside the pool.
Step 7 Click Send in the displayed The MML Commands send to NE dialog box.
The system issues MML commands to all the MSCes. The system also displays Send Status
and Send Result of the command.
NOTE
l When the MML command is being issued, you can click Stop to stop issuing the MML command.
l If all MML commands fail, you can click Send to issue MML command again. If part of the MML
command cannot be issued, the Send icon is unavailable. You cannot issue the command again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Setting dialog box.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Select the CDMA pool whose properties are to be viewed, right-click the pool and select
Parameter Setting from the shortcut menu.
The Synchronize Pool Parameter Configuration Data dialog box is displayed, showing the
progress of updating the configuration data. After the configuration data of the pool is updated,
the Pool Parameter Setting dialog box is displayed.
NOTE
If updating the configuration data fails, the detailed reason for the failure is displayed in the Synchronize
Pool Parameter Configuration Data dialog box. You can click Parameter Setting to display the Pool
Parameter Setting dialog box.
Step 3 Click the MGW Node Management Status tab, and then select the NE records whose state is
to be set.
NOTE
If the system cannot collect the information about an MSCe in the pool, the state of the MSCe on the MGW
Node Management Status tab page is Unknown NE. In this case, you cannot modify the state of the MGW
node.
Step 5 Choose the NE status from the Set Status drop-down list according to your requirements.
For detailed description of the MGW, refer to13.6.9 Parameters for Setting NE State of
CDMA Pool.
Step 7 Click Send in the displayed The MML Commands send to NE dialog box.
The system issues MML commands to the relevant MSCes. The system also displays Send
Status and Send Result of the command.
NOTE
l When the MML command is being issued, you can click Stop to stop issuing the MML command.
l If all MML commands fail, you can click Send to issue MML command again. If part of the MML
command cannot be issued, the Send icon is unavailable. You cannot issue the command again.
Step 8 Click Close to close the The MML Commands send to NE dialog box.
Step 9 Click Close to close the Pool Parameter Setting dialog box.
----End
Related Concepts
13.3.3.1 Parameters of CDMA Pool
Related References
13.6.9 Parameters for Setting NE State of CDMA Pool
users. You should monitor the load in the CDMA pool in real time. Thus the load in the CDMA
pool is balanced after you perform the related operations such as user transference.
13.4.3 Viewing the Operation Logs of CDMA Pool
This describes how to view the operation logs of a CDMA pool. The operation logs of a CDMA
pool records the operations related to the CDMA pool.
13.4.4 Viewing the MSCe Where a Specific User Is Located
This describes how to view the MSCe where a specific user is located. In the CDMA pool, a
CBSC does not map an MSCe. The users under the same CBSC may also be distributed to
different MSCes. The M2000 provides the subscriber search function. By using this function,
you can quickly find the MSCe where a specific user is located.
13.4.5 Displaying CDMA Pool Topology
This describes how to display the CDMA pool topology. The CDMA pool topology is used to
display the logical networking structure of the CDMA pool. You can also expand it to view the
NEs and their connections within the pool.
13.4.6 Managing the Task of Auto-Checking CDMA Pool
This describes how to manage the task of auto-checking CDMA pool. For the existing auto-
checking task of the CDMA pool, you can perform operations such as modification or deletion.
13.4.7 Viewing the CDMA Pool Performance Report
This describes how to view the performance report of a CDMA pool. After a CDMA pool is
created, counters of a single NE, such as mobile office direction traffic, call connection ratio,
and call drop rate, fail to serve as the statistical information about the entire network. By querying
the CDMA pool performance report, you can summarize the performance data reported by NEs
and get the counter data applicable for the entire network.
Context
For details about the operations related to the alarms, such as synchronizing, printing, and
confirming the alarm, refer to the 2 Network Monitoring.
13.4.1.1 Viewing the Current Fault Alarms of CDMA Pool
This describes how to view the current fault alarms of a CDMA pool. The fault alarms of a
CDMA pool refer to the alarms that are generated because of unbalanced loads. You can set
multiple query conditions to quickly locate the unbalanced loads to perform maintenance.
13.4.1.2 Viewing the Event Alarms of CDMA Pool
This describes how to view the event alarms of a CDMA pool. The event alarms of a CDMA
pool are generated mainly because of data inconsistency between the MSCes or the MGWs in
the CDMA pool. You can set multiple query conditions to quickly locate the inconsistent data.
Thus you can synchronize them in time to ensure the normal operation of the CDMA pool.
Related References
13.6.2 Interface Description: Viewing CDMA Pool Alarms
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
The fault alarms of a CDMA pool refer to the generated alarms because of unbalanced loads in
the CDMA pool. The alarm type is internal NM. For details, refer to ALM-1 Load Unbalance
Alarm.
To view the current fault alarms of specific NEs in the CDMA pool, you can use either of the
following methods:
l Use the alarm query function described in 2.2.7 Querying Alarms.
l View the icon color and alarm balloon of the NE on the M2000 physical topology view or
the pool topology view.
When an NE generates fault alarms, the color of the NE icon changes to that for the most
severe alarm. In addition, an alarm balloon is generated beside the icon. The balloon
displays the alarm severity identity and number of alarms.
Procedure
View the current fault alarms of the CDMA pool.
Select one of the following methods to view the Current Fault Alarms window:
Method Operation
From the Pool Management 1. Choose Maintenance > Pool Management or click
window
on the toolbar. The Pool Management interface is
displayed.
2. Right-click a CDMA pool in the navigation tree and
choose Query Alarm > Current Fault Alarm from the
shortcut menu.
From the main window of the 1. Choose Monitor > Current Fault Alarms or click
M2000 client
on the toolbar. The Filter dialog box is displayed.
From the toolbar of the 2. Click the Alarm Source tab to select the CDMA pool
M2000 client whose alarms need to be checked.
3. On the Base Setting tab page, set the time segment of the
alarm.
4. Click OK.
NOTE
You must select Critical in Level and Internal in Type. All alarm
severities and alarm types are selected by default.
For details of the operations related to alarms, such as saving, printing, and viewing alarm details,
refer to 2 Network Monitoring.
----End
Result
In Current Fault Alarms, you can view the details of current fault alarms of CDMA Pool.
Related References
13.6.2 Interface Description: Viewing CDMA Pool Alarms
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
l Event alarms of CDMA pool are the event alarms generated when data inconsistency is
detected during data auto-check. The alarm type is internal NM. For details, refer to ALM-2
Data Inconsistency Alarm.
l To view the event alarms of specified NEs in the CDMA pool, you can use the network
alarm query function described in 2.2.7 Querying Alarms.
Procedure
View the event alarms of CDMA pool.
Select one of the following methods to view the Event Alarms window:
Method Operation
From the Pool Management 1. Choose Maintenance > Pool Management or click
window
on the toolbar. The Pool Management interface is
displayed.
2. Right-click an CDMA Pool in the navigation tree and
choose Query Alarm > Event Alarm from the shortcut
menu.
Method Operation
From the toolbar of the 2. Click the Alarm Source tab to select the CDMA pool
M2000 client whose alarms need to be checked.
3. On the Base Setting tab page, set the time segment of the
alarm.
4. Click OK.
NOTE
You must select Critical in Level and Internal in Type. All alarm
severities and alarm types are selected by default.
For details of the operations related to alarms, such as saving, printing, and viewing alarm details,
refer to 2 Network Monitoring.
----End
Result
In Event Alarms, you can view the details of event alarms of CDMA Pool.
Related References
13.6.2 Interface Description: Viewing CDMA Pool Alarms
Application Scenarios
The function of monitoring the load of CDMA pool in real time is applied in the following
scenarios:
l After an imbalance load alarm is generated, you can view the load of the pool in real time.
Thus you need to learn the status of users on each MSCe and design a transferring plan.
l After users are manually transferred, you can view the load of the pool in real time. Thus
you can monitor the load of NEs in the pool and the progress of user transferring.
l You can perform scheduled monitoring in routine maintenance.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
l Relevant NEs are properly connected to the M2000.
Context
The real-time monitoring chart of the CDMA pool can be a line chart or bar chart. The difference
is as follows:
l Line chart: The vertical coordinate refers to the counter values. The horizontal coordinate
refers to the monitoring time.
l Bar chart: The vertical coordinate refers to the counter values. The horizontal coordinate
refers to the monitored objects.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Right-click the CDMA pool in the navigation tree and select Realtime Monitor from the
shortcut menu.
Step 3 Set the monitoring parameters in the displayed Create a Real-time Load Monitor Task dialog
box.
1. Select monitoring counters.
For details about monitoring counters, see 13.4.2.2 Real-Time Monitoring Counters of
CDMA Pool.
2. From the Period drop-down list of a monitoring counter, select the monitor period of the
counter.
The system periodically refreshes monitoring counters. The monitoring period can be 30
seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, or 20 minutes.
3. In the NE group box, select the NEs to be monitored.
You can select multiple NEs at a time.
Step 4 Click OK.
The system displays the load balancing condition of the MSCe in bar charts or line charts. You
can right-click in the real-time monitoring chart and perform the following operations:
l Save as an image: to save the monitoring chart as an image. The image is in .jpg format.
l Export data: to save the monitoring data to a file. The file is in .csv format.
l Print: to print the current monitoring chart.
l Set NE color: to display different NE data in different colors.
l Line filter: to display the monitoring data of only the selected NEs in the line chart.
NOTE
The created tasks are named Monitor Task Number with the number increasing from 1. For example, the
first monitoring task is named Monitor Task1, and the second task is named Monitor Task2. You can
change the task names as required.
----End
The real-time monitoring counters comprise Subscriber Quantity, CPU Usage, and Number of
MGW Contexts. Table 13-5 describes these counters.
MSCe Subscribers Total number of users Number of all the users on the MSCe,
that is, users inside and outside the
pool.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs .
Step 2 In the Filter Condition window, click Choose in the Operation group box.
Step 3 In the displayed Operation Select dialog box, view the operations related to the CDMA pool.
Step 5 In the Filter Condition window, set the filtering conditions, and then click OK.
The procedures are the same as those described in 5.3.2 Querying Operation Logs. For details
of other operations related to logs, such as saving and printing query results, refer to 5 Log
Management.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Right-click an CDMA Pool in the navigation tree and choose Subscriber Search from the
shortcut menu.
Step 3 Select the number type of the specific user in the displayed Search for subscriber
The number type can be IMSI, MIN, or MDN. The following part describes the meanings of the
number types:
l IMSI: Indicates the identity number of the international mobile subscriber. The IMSI number
is the only identity number for the subscriber in the network.
l MIN: It is short for Mobile Identification Number. The CDMA system in north America uses
the MIN rather than the IMSI to uniquely identify the mobile subscriber.
l MDN: It is short for Mobile Directory Number. The MDN is the number that is required by
a calling user to call a mobile subscriber in the CDMA PLMN. The use of the MDN is similar
to the use of the PSTN in a fixed network.
Step 4 Enter the number of the subscriber that you need to search in the Number field. Choose the
result display mode to Basic Information or Full Information.
l If you choose Basic Information, the system displays only the information that you are most
concerned with, such as IMSI, MDN, and number attributes.
l If you choose Basic Information, the system displays all the information about the subscriber,
for example, the calling number and the called number of the most recent call.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
NOTE
l On the view of the CDMA pool topology, you can right-click Pool Management Main Frame. Then
the Pool Management interface is displayed.
l See 3 Topology Management and 2 Network Monitoring for the details about other shortcut menus
on the pool topology view. The menus include the functions such as setting forewarning pop and
querying NE alarms.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Select the CDMA pool whose topology is to be viewed, right-click the pool and select
Topology from the shortcut menu.
Step 3 Check the logical networking structure of the CDMA pool in the displayed Main Topology
window.
All NEs on a CN of the pool are displayed in a pane, on the bottom of which the
icon is displayed. Double-click the icon, the NEs are displayed as
. Double-click the icon again, the system expands the NEs in the pool.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to access the CDMA pool.
l The auto-checking task of the CDMA pool is available.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management window is displayed.
Step 2 Select a CDMA pool whose tasks are to be managed in the navigation tree, and then right-click
the task and choose Data Consistency Check > Automatic Check.
Step 3 Click the Check Task tab. Then, you can manage the auto-checking task according to your
requirements.
Browse detailed information about the task In the list, you can check detailed information
about the task, such as the task name, the plan
checking, the NE checking, the data checking,
and the task status.
Modify the information about the task 1. In the list, choose the task to be modified.
2. Either double-click the task or click
Modify.
3. In the displayed Modify an Automatic
Check Task dialog box, modify the
information as required.
4. Click OK.
Delete the auto-checking task 1. In the list, choose the task to be deleted.
2. Click Delete.
3. In the displayed Message dialog box, click
Yes.
Activate the auto-checking task 1. In the list, choose a task whose Task
Status is Suspended.
2. Right-click the task and select Active .
Then, the system performs the task based
on the scheduled period.
Suspend the auto-checking task 1. In the list, choose a task whose Task
Status is Activated.
2. Right-click the task and select Suspend .
Then, the system suspends the task.
----End
Related References
13.6.6 Parameters for Setting the Auto-Check of CDMA Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
Step 1 You can perform either of the operations to open the Performance Report interface.
Method Operation
2
1. Choose Maintenance > Pool Management or click on the toolbar.
2. Right-click a CDMA pool in the navigation tree and choose Query Performance
Report from the shortcut menu.
Step 2 Right-click the performance report in the navigation tree and choose Query from the shortcut
menu.
For information about each performance report, refer to 7.6 CDMA Pool Report Group.
Step 3 Set the query conditions in the displayed Set report conditions
1. Select the time dimension in Time dimension.
Then the system summarizes the performance counter results of the query objects based
on the time dimension. For example, if Time dimension is set to 15 Minutes, the system
summarizes the performance counter results at a regular interval of 15 minutes.
2. Select the query object in Object dimension.
For the pool performance counters, the object dimension is the Pool level. That is, all the
data of the MSCe in the pool is summarized to the pool level. For example, call attempts
of a pool equals the call attempts of MSCe1 and the call attempts of MSCe2.
3. Select the query object in Object Range.
4. In the Date Selection and Time Segment Selection group boxes, select proper query time.
Step 4 Click Query.
The query results are displayed in tables.
NOTE
For detail of the operations related to performance reports, such as filtering reports, setting query templates,
and setting display conditions, refer to 7 Performance Report Management.
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Context
Before transferring users, you can view the load of each NE on the current network through the
CDMA pool load monitoring function and choose a proper transfer method.
For details about the scenario description and how to manually transfer users, refer to Table
13-6.
Transferring all subscribers on the When you update one or more MSCes in a CDMA
MSCe to other MSCes pool, you need to transfer all the users on the MSCes
to other MSCes in the CDMA pool and then update
the MSCes to ensure the normal operation.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Select a pool whose users are to be transferred, right-click the pool and select Load
Redistribution from the shortcut menu.
Step 3 Select a transfer type in the displayed Load re-distribution-Select a type dialog box, and then
click Next.
For details, refer to Table 13-6.
Step 4 Perform different operations according to the user distribution methods.
Transfer all subscribers on the MSCe to Choose the MSCe from which the users are
other MSCes transferred in the Source NE.
Transfer a certain number of subscribers 1. Choose the MSCe from which the users are
on the MSCe to other MSCes transferred in Source NE.
2. Set the number of subscribers to be
transferred in subscribers.
----End
Postrequisite
You can monitor the progress of the transferring task through the real-time monitoring function
of the CDMA pool. For details, refer to 13.4.2.1 Setting the Real-Time Monitoring of CDMA
Pool.
Related Tasks
13.3.2 Creating the Task of Auto-Checking CDMA Pool
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
l At least one auto-checking task is performed.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Right-click a CDMA pool in the navigation tree and choose Data Consistency Check >
Automatic Check from the shortcut menu.
The Automatic Check dialog box is displayed.
NOTE
You can also view the check results in the area about data consistency in the Pool Management window.
By double-clicking a record, you can also open the Automatic Check dialog box.
Step 3 Click the Check Result tab to view the check result.
The check result list displays the results of each auto-checking task. After you select a record
whose Result is Inconsistent or Abnormal, you can perform the following operations.
l Acknowledge: Indicates that the check results are processed. This operation applies to only
results that are not acknowledged.
l Unacknowledge: Identifies the acknowledged check results as not acknowledged. This
operation applies to only acknowledged results.
NOTE
----End
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 Select the CDMA pool whose data to be checked, and right-click the pool and choose Data
Consistency Check > Manual Check&Synchronize Data.
The Manual Check dialog box is displayed.
Step 4 Select the NEs whose data needs to be checked in Select NE.
NOTE
Step 5 Select the data items in the Select Data Item area.
NOTE
Before you perform the data check, the M2000 server requests NEs for the data to be checked; thus ensuring
the consistency between the data on the M2000 server and the data on the NEs.
Step 7 Perform the related operations on the basis of the update results.
Succeeded Go to Step 8.
If inconsistent data exists, the data details are displayed in the area under the Select NE area.
l The Inconsistency Data tree displays the data items and key values of the inconsistent data.
The key value uniquely identifies the data item of a record.
l You can view the detailed check results in the box beside the Inconsistency Data tree. The
inconsistent data is highlighted in red.
If the NE data is consistent, the Data Consistency Check dialog box is displayed, showing that
the data is consistent.
----End
Postrequisite
l If data inconsistency exists, you need to manually synchronize the data. For details, refer
to 13.5.2.4 Synchronizing CDMA Pool Data.
l If the inconsistent data has no effect on the CDMA pool service, you can shield this data.
The shielded data is not checked in further checks. For details, refer to 13.5.2.3 Setting the
Checking Items of CDMA Pool Data.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
Procedure
l Shield data checking items. Perform the following steps:
1. Manually check the CDMA pool data. For details, refer to 13.5.2.2 Manually
Checking CDMA Pool Data.
2. In the Inconsistency Data tree, right-click the data to be shielded and choose
Shield from the shortcut menu.
– You can press Ctrl or Shift to select multiple records.
– After the data is shielded, the corresponding background color of the NE record
turns gray.
– You can right-click the NE record of the shielded data item and choose Resume
from the shortcut menu to restore the shielded data.
3. Click Close to close the Manual Check dialog box.
l Restore the shielded checking items.
1. Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management dialog box is displayed.
2. Right-click the CDMA pool whose data checking items are shielded and choose Data
Consistency Check > Cancel the Shield Status of Check Item from the shortcut
menu.
3. Select the data and NEs to be restored in Shielded Item.
4. Click OK.
----End
Result
The settings take effect at the next automatic or manual check.
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to operate the CDMA pool.
l The configuration data that must be consistent on each NE is inconsistent.
Context
On the basis of data inconsistency, the M2000 generates the MML commands to adjust data.
These commands are issued to the relevant NEs to adjust NE data and achieve data consistency.
NOTE
Some NE data cannot generate the adjusting-data command on the M2000. In this case, you can adjust the
data on the LMT.
Procedure
Step 1 Choose Maintenance > Pool Management or click on the toolbar. The Pool
Management interface is displayed.
Step 2 In the navigation tree, choose a CDMA pool and check pool data.
You use either of the following methods to check the data.
Checking Method Description
Manually check the CDMA pool data. For details, refer to13.5.2.2 Manually
Checking CDMA Pool Data.
In the Pool Management dialog box, 1. Double-click the record whose Result is
manually check the record whose Result Inconsistent.
is Inconsistent 2. In the displayed Automatic Check dialog
box, click Manual Check.
3. After setting the data check items in the
displayed Manual Check dialog box, click
Start Check.
Step 3 In the Inconsistency Data tree of the Manual Check dialog box, select the data item or key
value that needs to be synchronized.
l You can edit the MML command on the MML Command tab page, or click Save MML to save the
MML commands to a file for future operations.
l If the key value of the Destination NE is consistent with that of the Reference NE, the MML
Command tab page shows that the data is consistent and displays the relevant key value.
l If a certain key value does not support a certain generated MML command, the MML Command tab
page shows that the key value does not support the MML command. In this case, adjust data through
the LMT of the NEs.
l The MML Command tab page supports a maximum of 500 MML command lines. When the MML
commands exceed 500 lines, the system prompts that the MML commands are excessive. Change the
number of MML commands, and then issue them.
Step 8 Click Send MML to select the issuing mode, and then issue the MML commands.
The Data Synchronization dialog box shows a progress bar to display the synchronization
progress of the MML commands.
NOTE
l When the MML command is issuing, you can click Terminate MML to terminate the command
issuing.
l The operation records are displayed in MML messages on the MML Report tab page.
l On the MML Report tab page, Total Count indicates the total number of MML commands to be issued,
Success Count indicates the number of succeeded MML commands on the NE, Fail Count indicates
the number of failed MML commands on the NE, and Unsend Count indicates the number of unsent
MML commands on the M2000.
Step 10 Click Close to shut down the Data Synchronization dialog box.
Step 11 Repeat Step 3 through Step 8 to synchronize other data.
----End
Postrequisite
Click Export Result to save the results issued by the MML as files.
1 Child window of CDMA pool The created CDMA pool and the NEs in
objects the pool are displayed in a navigation
tree.
The child window of CDMA pool
objects provides a shortcut menu so that
you can perform maintenance
operations on the pool, such as
parameter configuration, user
migration, and user search.
4 Chid window of the task list This child window displays the
information about the data
synchronization tasks in the pool.
This child window provides a shortcut
menu so that you can perform the
following operations on the task
records:
l Refresh the task list.
l View the detailed task information.
l Stop a task.
l View the operation results.
l Delete a task.
an alarm from the list, the system displays its detailed information and handling suggestion.
Figure 13-4 shows the interface.
Related Tasks
13.4.1 Viewing the Alarms of CDMA Pool
13.4.1.1 Viewing the Current Fault Alarms of CDMA Pool
13.4.1.2 Viewing the Event Alarms of CDMA Pool
MSCe Server ID Setting Displays all the MSCe Server IDs in the CDMA
pool.
Provides the function of modifying the MSCe
Server ID. In this way, you can change the MSCe
Server ID value on the MSCe side according to
actual situations when the MSCe Server IDs set on
the MGW and MSCe sides are inconsistent because
of network planning mistakes.
Load Balance Parameter Displays the capacity of MSCes within the CDMA
pool.
Provides the function of changing the available
MSCe pool capacity. In this way, you can plan the
available MSCe capacity within the pool according
to the actual situations. In addition, you can balance
user allocation based on the set user capacity when
booting the MGWs to access users.
For example, if an MSCe within the pool is
connected to a CBSC external to the pool, the actual
user capacity configured by the MSCe within the
pool equals the result subtracting the user capacity
provided by the pool from the maximum user
capacity.
Tab Description
MGW Node Management Status Provides the function of setting the MGW
maintenance status within the CDMA pool.
The MGW states are Normal and Inhibited. If you
set the MGW to the Inhibited status, the MGW exits
smoothly and has no impact on the services of users
within the pool.
Related Tasks
13.2 Creating CDMA Pool
13.2 Creating CDMA Pool
Parameter description
Parameter Description
Parameter Description
Optional NEs The NEs that can be added to the CDMA pool are
displayed in a navigation tree.
Based on the NEs that are connected to the M2000 and
the selected networking type of the pool, the system
automatically filters the NEs that can be added to the
CDMA pool.
Selected NEs The NEs existing in the CDMA pool are displayed in
a navigation tree.
Related Tasks
13.2 Creating CDMA Pool
13.2 Creating CDMA Pool
Parameter description
Parameter Description
Specification Indicates the specific NEs and the number of the NEs
within the CDMA pool. For example, MSC e(2) MGW
(2) indicates that the CDMA pool contains two MSCes
and two MGWs.
Parameter description
Parameter Description
Data Item Indicates the data items to be checked. The Data Item
navigation tree lists all the data items that are configured
on each MSCe or each MGW in the pool.
Check Period Indicates the period for the system to regularly check the
data of NEs within the pool.
The check periods are Everyday,Every week,Every month,
and Single time. Single time indicates that this auto-
checking task is performed only once.
NOTE
If you set the Check Period to Every month and the set Day is
not available every month, for example 31, the system performs
the checking task on the last day of that month by default in the
month of fewer than 31 days.
Day Indicates that the system checks the data of the NEs within
the pool in a specific day of a scheduled week in a month.
NOTE
This parameter is valid only when Check Period is Every week
or Every month.
Check Time Indicates the specific time for the system to check the data
of NEs within the pool.
NOTE
When Check Period is Single time, the Check Time must be later
than the current time of the system.
Related Tasks
13.3.2 Creating the Task of Auto-Checking CDMA Pool
13.4.6 Managing the Task of Auto-Checking CDMA Pool
Parameter description
Parameter Description
MSC server ID Displays the ID of each MSCe within the pool. The
MSC Server ID is the unique identification of the
MSCe within the pool.
The value of the MSC Server ID ranges from 0 to
7.
NOTE
The changes in the MSCe Server ID have great impacts
on network services. Huawei recommends that the ID
be determined by the network planning first and be
modified on the M2000 client.
Related Concepts
13.3.3.1 Parameters of CDMA Pool
Related Tasks
13.3.3.3 Setting the MSCe Server ID
Parameter description
Parameter Description
Local Office NE Displays the names of all the MSCes in the pool.
Parameter Description
Pool Available Capacity Indicates the actual user capacity of the MSCe in
the pool. The actual user capacity is the converted
capacity value of the license capacity. For example,
if an MSCe in the pool is connected to a CBSC
external to the pool, the actual user capacity of the
MSCw in the pool equals the result subtracting the
user capacity provided outside the pool from the
license capacity.
The value of pool available capacity ranges from
the license capacity to 0.
Related Concepts
13.3.3.1 Parameters of CDMA Pool
Parameter description
Parameter Description
MGW Name Displays the names of all the MGWs in the pool.
Related Concepts
13.3.3.1 Parameters of CDMA Pool
Related Tasks
13.3.3.5 Setting the Maintenance State of NEs in CDMA Pool
Parameter description
Parameter Description
Threshold of capacity offset Indicates the threshold of the load unbalance alarm
for the CDMA pool. When the difference between
the maximum and minimum load of the MSC
Server within the CDMA pool exceeds this
threshold, the system reports the load unbalance
alarm of the CDMA pool. Load of the MSCe equals
the ratio of the number of current MSCe subscribers
to the total user capacity of the MSCe.
Automatic detection period The system periodically detects the interval of each
MSCe load within the CDMA pool. The check
periods are 15 minutes, 30 minutes, 1 hour, 2 hours,
6 hours, 12 hours, and 24 hours.
Related Tasks
13.3.1 Setting an Alarm for CDMA Pool Load Imbalance
The M2000 provides the function of integrated management of scheduled tasks. Thus, you can
browse information such as the task status and the progress. You can also create, modify, and
delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and
save task result files to the client.
l Only the RNC and NodeB support CME tasks. CME tasks are available only after you install the CME
software that corresponds to the NE version.
l Network health check tasks are available only after you purchase and install the relevant components.
Database Capacity Management The system periodically deletes the data that reaches the
specified Save Days from the database. The database
capability is maintained in a proper range. Therefore, the
database fault caused by large amount of data is prevented.
By default, the maximum Save Days in the database is 90
days. The set value cannot exceed 90 days.
The following databases can be managed: operation log
database, system log database, security log management,
NE operation log database, NE security log database,
alarm database, and performance database.
File Interface The file export function enables you to periodically export
various data to a specified directory of the server. Using
this function, you can externally save the data. The
exported data is saved in the database.
The exported data consists of performance data,
configuration data, NE operation logs, NE security logs,
inventory data, alarm data, network management
operation logs, network management system logs, and
network management security logs.
Backup The M2000 allows you to save the server data and NE data
as the backup files to a specified directory of the server.
The saved system data and NE data can be used to restore
the system and NEs in the event of data missing or the
abnormality of the system and the NEs. The backup task
consists of regular backup of all NEs in a network and
regular backup of the server.
The data that can be backed up on the M2000 consists of
configuration data and log data. The system files and
operating system cannot be backed up.
Network Health Check This describes how to check the network health. The
network health check checks the status of NE devices and
M2000 itself, the performance of NE devices, and alarm
information. The health check report is displayed in .html
format.
Thus you can find the hidden problems of devices. In this
way, severe accidents are avoided and proper operation of
current devices is ensured.
For details, refer to the online help about network health
check.
System Timing Tasks System timing tasks are the tasks required for the normal
operation of the M2000 system. They consist of the database
capacity management tasks, synchronization tasks, file
interface tasks, the alarm acknowledgement tasks, NE
license sharing management tasks, and backup tasks
(excluding NE backup). For details, see 14.1.2 System
Timing Tasks.
User Timing Tasks User timing tasks are the user-defined tasks that are created
to meet the requirement of network maintenance. They
consist of MML script, NE software timing download,
timing backup of all NEs on a network, HSL script, CME
upload, CME download, dual home management, and
network health check. For details, see 14.1.3 User Timing
Tasks.
The M2000 uses to indicate system timing tasks and uses to indicate the user timing tasks.
NOTE
l Only users in the administrator group can manage and view the system timing tasks. Other users
cannot manage or view the system timing tasks.
l The system timing tasks cannot be copied or deleted. Only some parameters of the system timing
tasks can be modified.
l You cannot suspend or cancel the database capacity management in the system timing tasks, while
you can suspend or cancel synchronization tasks and backup tasks. You can also set the time to
suspend or cancel synchronization and backup tasks.
Database Capacity Performance data For details, see 14.5.7 Modifying the
Management Performance Data Capacity of Performance Database.
File Interface Performance data For details, see 14.6.1 Modifying the Export
export of Performance Data.
Performance Data
Export
NE security log export For details, see 14.6.8 Modifying the Export
NE Security Log of NE Security Log.
Export
Inventory data export For details, see 14.6.9 Modifying the Export
Inventory Data Export of Inventory Data.
Alarm data export For details, see 14.6.2 Modifying the Export
Alarm Data Export of Alarm Data.
Operation log export For details, see 14.6.4 Modifying the Export
Operation Log Export of Operation Log.
System log export For details, see 14.6.5 Modifying the Export
System Log Export of System Log.
Security log export For details, see 14.6.6 Modifying the Export
Security Log Export of Security Log.
Backup Server backup For details, see 14.7 Modifying Data Backup
Server Backup in the M2000.
l You can create, modify, delete, copy, suspend, and restore user timing tasks.
l The M2000 uses to indicate system timing tasks and uses to indicate the user timing
tasks.
l Only the RNC and NodeB support CME tasks. CME tasks are available only after you install the CME
software that corresponds to the NE version.
l Network health check tasks are available only after you purchase and install the relevant components.
Backup NE Backup To store the NE data, you can For details, see 14.2.3
regularly save the NE data as Creating Entire NE Backup.
backup files to a specified
directory on the server. In this
situation, the data loss can be
avoided. If NEs have errors,
you can restore the NEs. You
can select NE types to back up
specified NEs.
Others MML Script You can perform the MML For details, see 14.2.1
script files based on the Creating MML Command
interval or based on the time to Script.
deliver commands in the script
in batch. You need not
manually deliver the
commands one by one.
Dual Home The system checks the data of For details, see 14.2.7
Management dual home pair NE Creating Dual-Home
periodically or on schedule so Management.
that you can determine
whether the data is consistent.
Thus you can ensure that an
MSC server can take over
some or all data on the other
MSC server.
HSL Script By running the preset HSL For details, see 14.2.6
scripts, you can perform the Creating HSL Script.
operations such as modifying
NE parameters and getting
alarm data.
CME CME Upload Setting a specified interval or For details, see 14.2.4
a time to upload user-selected Creating CME Upload.
NE configuration data to the
CME server side. Thus, CME
can configure the latest NE
data. The upload task only
supports the RNC and NodeB.
CME Set a time to deliver the data For details, see 14.2.5
Download configured by CME. Thus, the Creating CME Download.
data takes effect when the data
is delivered to NEs. The
download task only supports
the RNC and NodeB.
Network Health Check The network health check For details, refer to the online
enables you to check the NE help about network health
device, check alarms, check check.
performance, and compare
result files. The network health
check enables you to find the
hidden problems of devices.
Thus, severe accidents are
avoided and proper operation
of current devices is ensured.
For details, refer to the online
help about network health
check.
Task Type According to different task execution periods, the M2000 divides the
execution types of the managed timing tasks into two types: periodic
execution and one-time execution. The execution type of the system
timing tasks is periodic execution. The execution type of the CM
download tasks in user timing tasks is one-time execution. The
execution type of the other user timing tasks can be periodic
execution or one-time execution.
Task start time Indicates start time of periodic tasks and one-time tasks set upon task
creation, including date and time. The start time of tasks should be
later than the current server time.
Period Interval between periodic tasks. It has two enlistment: unit and
duration. The task execution period can be represented by month,
week, day, hour, and minute. Second is not supported. The period
interval range is as follows: 1 to 12 for month, 1 to 52 for week, 1 to
365 for day, 1 to 8760 for hour, and 1 to 525600 for second.
Run Times Indicates execution times of a periodic task. The execution times
range from 0 to 65535. The value 0 indicates no limit.
If the scheduling parameters of the entire network NE backup task are: Execution type =
Periodicity, Start time = 2006-10-21 09:07:28, Execution period = 1 day, and Period
execution times = 0, infer that the system start to carry out the entire network NE backup task
every day on 2006-10-21 09:07:28.
The states of a scheduled task change with different operations. For details, see Figure 14-1.
If a CME task is in the complete state and you terminate the task, the CME task is in the archiving
state.
When a timing task is in the idle, suspended, or complete state and a CME task is in the archiving
state, you can delete the timing task.
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Perform different operations according to different customized requirement.
----End
Related References
14.15.2 Parameters for Setting Filtering Conditions
Prerequisite
l You have logged in to the M2000 client.
l MML script files are already created.
Context
l The MML script task is a user-timing task.
l The task can be performed for an interval or for one time. Execution Period is expressed
in minute, hour, or day.
l The MML script task allows you to create multiple instances. When the number of MML
script instances exceeds the upper limit, creating any more instances fails.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
TIP
Choose Task Type > Other > MML Script in the navigation tree. Double-click the node. The New
Task dialog box is displayed. By default, the system sets Task Type to MML Script.
Step 5 Click . In the displayed Date/Time Selection dialog box, set the start time.
NOTE
Periodic task In Period and Run Times fields, enter the associated information. Then,
perform Step 7.
Step 8 Click . In the displayed Open dialog box, select a script file.
l If the created task is a one-time task, you can select Redirect Result and set the path of
Redirect File to add the task result to the specified redirection file. You can create a non-
existent file. If the redirection file exists, the new messages does not overwrite the original
messages.
l If you set the result redirection of a task, the path of Redirect File cannot be changed after
the task is completely created.
l When creating MML scripts, you must select Select Ne to choose NE objects if the script
file are lack of object information.
Step 9 Set Run Mode.
The MML commands in the script are issued to the NE You select Collateral
concurrently.
The MML commands are issued to the NE in sequence. You select Serial
----End
Related References
14.15.8 Parameters for Creating/Modifying/Copying MML Command Script
Prerequisite
You have logged in to the M2000 client.
Context
l The software download task is a user timing task.
l The task is performed for an interval or for one time. The unit of Period is Day.
l You can download software by NE type. Before downloading the mediation software, you
need to select the NE type.
l The software download task allows you to create multiple instances. When the number of
software download tasks exceeds the upper limit, creating any more tasks fails.
l The M2000 allows you to download the mediation software of one NE to NEs of the same
type at a time.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
TIP
Choose Task Type > Other > NE Software Download in the navigation tree. Double-click the node. The
New Task dialog box is displayed. By default, the system sets Task Type to NE Software Download.
Step 5 Click . In the displayed Date/Time Selection dialog box, set the start time.
NOTE
Periodic task In Period and Run Times fields, enter the associated information. Then,
perform Step 7.
The newly added software download task is displayed in the task list.
----End
Related References
14.15.9 Parameters for Creating/Modifying Software Download
Prerequisite
You have logged in to the M2000 client.
Context
l Large quantity of system resources are used when the system performs NE backup tasks.
Therefore, avoid backing up NE data at busy time.
l The entire NE backup task is a user timing task.
l Two task types are available: period tasks and once tasks. The units of Period is represented
by Day, Week, and Month.
l The entire NE backup task allows you to create multiple instances. When the number of
entire NE backup tasks exceeds the upper limit, creating any more tasks fails.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Chose Task Type > Backup > NE Backup in the navigation tree. Double-click the task. The New Task
dialog box is displayed. By default, the system sets Task Type to NE Backup.
Step 5 Click . In the displayed Date/Time Selection dialog box, set the start time.
NOTE
Periodic task In Period and Run Times fields, enter the associated information. Then,
perform Step 7.
By default, the system selects the entire NE backup.To back up NEs of the specified type, you
need to clear Backup All NE and select the required NE type in the NE tree.
----End
Related References
14.15.10 Parameters for Creating/Modifying/Copying Entire NE Backup
Prerequisite
l You have logged in to the M2000 client successfully.
l The RNC or NodeB exists on the network and the relevant CME software is installed.
Context
l The CME upload is a user timing task.
l The task can be performed for an interval or for one time. Execution Period is represented
in days, weeks, or months.
l The CME upload only supports the RNC and NodeB.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Choose Task Type > CME > CME Upload in the navigation tree. Double-click the node. The New
Task dialog box is displayed. By default, the system sets Task Type to CME Upload.
Step 4 Click Next to set the run time for the task.
Step 5 Click . In the displayed Date/time dialog box, select the start time for the task.
NOTE
Step 6 Perform different operations according to the run type. The run type consists of two types, that
is, once and period.
Period Enter values in Period and Run Times, and then go to Step 7.
Step 7 Click Next, and then select the types of NEs whose configuration data need be uploaded to the
CME server side.
----End
Related References
14.15.11 Parameters for Creating/Modifying/Copying CME Upload
Prerequisite
l You have logged in to the M2000 client.
l The RNC or NodeB exists on the network and the relevant CME software is installed.
Context
l CME download is a user scheduled task.
l The task execution type is once rather than periodic.
l The CME download only supports the RNC and NodeB.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
TIP
Choose Task Type > CME > CME Download in the navigation tree. Double-click the node. The New
Task dialog box is displayed. By default, the system sets Task Type to CME Download.
Step 5 Click . Select required configuration files from the displayed Open dialog box.
Step 6 Click Finished.
You can view the upload progress in the displayed dialog box. The added CME download task
is displayed in the task list.
----End
Related References
14.15.5 Parameters for Setting Common Information for CME Download Tasks
Prerequisite
l You have logged in to the M2000 client.
l The HSL script exists.
Context
l The HSL script task is a user timing task.
l The task can be performed for an interval or for one time. Run Period is represented in
Minute, Hour, Day, Week, or Month.
l The HSL script task allows you to create multiple instances. When the number of HSL
script instances exceeds the upper limit, creating any more instances fails.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Choose Task Type > Other > Script Executor in the navigation tree. Double-click the node. The New
Task dialog box is displayed. By default, the system sets Task Type to Script Executor.
Step 5 Click . In the displayed Date/Time Selection dialog box, set the start time.
NOTE
Periodic task In Period and Run Times fields, enter the associated information. Then,
perform Step 7.
Step 8 Click besides the Main File text box. In the displayed Open dialog box, select the required
script file. This file is the entry file for later script operation.
The entry files are the entry for running the whole script. Other Accessory Files or involved
NEs may be used during the task execution.
Step 9 If the script file invokes other script files or includes operations to NEs, you need to set Accessory
Files or NE Selection.
The main file invokes other script files. Click besides the Accessory Files text box.
Select the required script file in the displayed
Open dialog box, and then perform Step 10.
----End
Related References
14.15.15 Parameters for Creating/Modifying/Copying HSL Script
Prerequisite
l You have logged in to the M2000 client.
l You have the right to manage dual homing.
l You have the right to operate the NEs that are related to dual homing.
Context
l The dual homing management task is a timing task. For details, refer to 11 Dual-Homing
and LN Domain Management.
l A dual homing task can be performed periodically or once. The units of Period is
represented by day, week, and month.
l The dual homing management task allows you to create multiple instances. When the
number of dual homing tasks exceeds the upper limit, creating any more tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
In the navigation tree, choose Task Type > Other > Dual Home Management and double-click the
selected node. The New Task dialog box is displayed. The default Task Type is Dual Home Management.
Step 4 Click Next. Then perform the related operation according to the task type.
Periodic task 1. Click . In the displayed Date/Time Selection dialog box, set the start
time.
2. Set values in Period and Run Times.
NOTE
Step 5 Click Next, and then set the information about the dual homing pair to be checked.
1. Select the dual homing pair from the Dual Homing Pairs drop-down list.
2. Select the data resource type in the Resource Type navigation tree.
You can enter the resource type or key word in Search. Then the related resource types are
listed under Search. You can quickly select the resource type to be checked by double-
clicking the type.
The added dual homing management task is displayed in the task list.
----End
Postrequisite
l You can obtain the information about data consistency by viewing the check result. For
details, refer to 14.14 Downloading Result Files.
l If data inconsistency exists, you need to generate a script to adjust the data difference and
synchronize the data. For details, refer to 11.2.5 Generating the Script for Adjusting
Difference Data and 11.2.7 Synchronizing the Dual-Homing Data.
Related References
14.15.16 Parameters for Creating/Modifying/Copying Dual-Home Management
Prerequisite
l You have logged in to the M2000 client.
l The copying user timing task does not support the batch operation.
Context
l Copying user timing tasks cannot be performed in batches. Therefore, do not select multiple
user timing tasks for copying.
l This function does not support system tasks and single-instance tasks. Multiple-instance
user timing tasks have the following types: MML command script task, software download
tasks, entire NE backup task, and HSL script task.
l The number of instances for user timing task is limited. When existing instances for the
timing task exceed the maximum value, you cannot copy this type of tasks any more.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Select a user timing task that support multiple instances and click Copy. The Copy Task dialog
box is displayed.
If you have requirement for tasks, modify original basic information parameters such as the task
name. For details of modifying the basic parameters, refer to the creation of each type of user
timing task.
If you have requirement for tasks, modify the original time parameters such as the start time.
For details of modifying the time parameter, refer to the creation of each type of user timing
task.
The newly created user timing task is displayed in the task list.
----End
Prerequisite
l You have logged in to the M2000 client.
l The MML command script task is already created.
Context
l You can modify only the following parameters: Task Name, Start Time, Run Period,
Run Times, Script File, and Run Mode.
l You are not allowed to modify the parameters of a complete MML script task. The
Status column shows whether the task is complete.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Other > MML Script in the navigation tree on the left of the window.
Step 3 Select a created MML command script task from the task list.
Step 5 Click Common Parameters or Extended Parameters. Set the parameters by referring to
14.15.4 Parameters for Setting Common Information and 14.15.8 Parameters for Creating/
Modifying/Copying MML Command Script.
NOTE
l The reset value of Start Time must be later than the current server time.
l For the MML command script task whose Run Type is Period, the reset value of Run Times should
be greater than the number of executed times. You can know the times for which the task has been
executed by viewing Executed Times column of the task list.
l If the task is a one-time task you set the result redirection of a task, the path of Redirect File cannot
be changed after the task is completely created.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.15.8 Parameters for Creating/Modifying/Copying MML Command Script
Prerequisite
l You have logged in to the M2000 client successfully.
l The software download task is already created.
Context
For an uncompleted software download task, you can modify the following parameters: Task
Name, Start Time, Period, Run Times, NE Type, Version, and NE.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Other > NE Software Download in the navigation tree on the left of
the window.
Step 3 Select an already created software download task from the task list to the right.
Step 4 Double-click the task or click Attribute. The Attribute dialog box is displayed.
Step 5 Click Common parameters or Extended Parameters. For details of resetting parameters, refer
to 14.15.9 Parameters for Creating/Modifying Software Download.
NOTE
l The reset value of Start Time must be later than the current server time.
l For the software download task whose Run Type is Period, the reset value of Run Times should be
greater than the number of executed times.
NOTE
If the task is running, the modified data takes effect during the next running.
----End
Related References
14.15.9 Parameters for Creating/Modifying Software Download
Prerequisite
l Log in to the M2000 client successfully.
l The entire NE backup task is already created.
Context
For an uncompleted entire NE backup task, you can modify the following parameters: Task
Name, Start Time, Period, Run Times, File Path, Backup All NE, and NE Type.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Backup > NE Backup in the navigation tree on the left of the window.
Step 3 Select an already created entire NE backup task from the task list to the right.
Step 4 Double-click the task or click Attribute. The Attribute dialog box is displayed.
Step 5 Click Common parameters or Extended Parameters. For details of resetting parameters, refer
to 14.15.10 Parameters for Creating/Modifying/Copying Entire NE Backup.
NOTE
l For an entire NE backup task whose Run Type is Period, the reset value of Run Times should be
greater than the number of executed times.
l The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect during the next running.
----End
Related References
14.15.10 Parameters for Creating/Modifying/Copying Entire NE Backup
Prerequisite
l You have logged in to the M2000 client.
l The CME upload task is already created.
Context
l CME upload is a timing task.
l The system supports period tasks and once tasks. The units of Period is represented by day,
week, and month.
l You can modify the following parameters: Task Name, Start Time, Period, Run
Times, All NE Configuration Data, and NE.
l CME upload supports only the RNC and NodeB. This type of task is available only after
you install the relevant CME software.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task TypeCMECMECME Upload in the navigation tree on the left of the window.
Step 3 Select an already created CME upload task from the task list to the right.
Step 5 Click Common parameters or Extended Parameters. For details of resetting parameters, refer
to 14.15.4 Parameters for Setting Common Information and 14.15.11 Parameters for
Creating/Modifying/Copying CME Upload.
NOTE
l For a CME upload task whose Run Type is Period, the reset value of Run Times should be greater
than the number of executed times.
l The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.15.11 Parameters for Creating/Modifying/Copying CME Upload
Prerequisite
l You have logged in to the M2000 client.
l The CME download task is already created.
Context
l CME download supports only the RNC and NodeB. This type of task is available only after
you install the relevant CME software.
l CME download is a user scheduled task. The task execution type is once rather than
periodic.
l You can modify the following parameters: Validate Interval, Preactivate Interval,
Activate Interval, Retry after Failure, Partially Retry, Retry Counts, Retry
Interval, Stop at Error, Rectify at Error, and Upload Files.
l Once a subtask is running, you can modify only Stop at Error or Rectify at Error in
Extended Parameter.
l For finished or archived CME download tasks, the parameters are not allowed to change.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > CME > CME Download in the navigation tree.
Step 3 Select an already created CME download task from the task list to the right.
Step 5 Click Common Parameters or Extended Parameters. Set the parameters by referring to
14.15.5 Parameters for Setting Common Information for CME Download Tasks and
14.15.14 Parameters for Creating/Modifying CME Download.
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
----End
Related References
14.15.5 Parameters for Setting Common Information for CME Download Tasks
14.15.14 Parameters for Creating/Modifying CME Download
Prerequisite
l You have logged in to the M2000 client.
l The HSL script task is already created.
Context
For an uncompleted HSL script task, you can modify the following parameters: NE Selection,
Task Name, Start Time, Period, and Run Times.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Other > Script Executor in the navigation tree on the left of the window.
Step 3 Select an already created HSL script task from the task list to the right.
Step 4 Double-click or click Attribute to view the Attribute dialog box.
Step 5 Click Common Parameters or Extended Parameters. Set the parameters by referring to
14.15.4 Parameters for Setting Common Information and 14.15.15 Parameters for
Creating/Modifying/Copying HSL Script.
NOTE
l For the HSL script task whose Run Type is Period, the reset value of Run Times must be greater than
the executed times.
l The reset value of Start Time must be later than the current server time.
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.15.15 Parameters for Creating/Modifying/Copying HSL Script
Prerequisite
l You have logged in to the M2000 client.
l A dual homing management task is available.
l You have the right to manage dual homing.
l You have the right to operate the NEs that are related to dual homing.
Context
l For the dual homing management tasks that are not completely performed, you can modify
the information such as Task Name, Start Time, Period, Dual Homing Pairs, and the
data resource type of the dual homing pair to be checked.
l For the dual homing management tasks that are completely performed, the related
information cannot be modified.
l For details of dual homing management, refer to 11 Dual-Homing and LN Domain
Management.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Other > Dual Home Management.
Step 3 In the task list, double-click a dual homing management task that is not completely performed.
Alternatively, select the task and click Attribute.
Step 4 Click Common Parameters or Extended Parameters. Set the parameters by referring to
14.15.4 Parameters for Setting Common Information and 14.15.16 Parameters for
Creating/Modifying/Copying Dual-Home Management.
NOTE
l The reset value of Start Time must be later than the current server time.
l For a dual-homing task whose Run Type is Period, the modified Run Times must be greater than the
executed times.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.15.16 Parameters for Creating/Modifying/Copying Dual-Home Management
users in the administrator group can modify the parameters of the task. If a data synchronization
task is complete, you cannot modify the parameters.
Prerequisite
You have logged in to the M2000 client.
Context
l The NE alarm synchronization task is a system timing task and only supports the period
type.
l Only users in the administrator group can modify the task.
l You can modify the following parameters of NE alarm synchronization:Task Name, Start
Time, and Period
Procedure
Step 1 Choose Maintenance > Task Management.The Task Management dialog box is displayed.
Step 2 Choose Task Type > Synchronization > Alarm Synchronization in the navigation tree on
the left of the window.
Step 3 Select an already created NE alarm synchronization task from the task list to the right.
Step 4 Double-click or click Attribute to open the Attribute dialog box.
Step 5 Click Common Parameters. For details of resetting the parameters, refer to 14.15.4
Parameters for Setting Common Information.
NOTE
The reset value of Start Time must be later than the current server time.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l The synchronization of NE configuration data is the system timing task and only supports
the period type.
l Only users in the administrator group can modify the task.
l You can modify only the following parameters: Task Name, Start Time, Period, All NE
Configuration Data, and NE.
l The synchronization of NE configuration data is applicable for the CDMA and GSM NEs
that do not support manual synchronization.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Synchronization > NE Configuration Data Synchronization node in
the navigation tree on the left of the window.
Step 3 Select an already created synchronization task of NE configuration data from the task list to the
right.
Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their
corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common
Information and 14.15.12 Parameters for Modifying the Synchronization of NE
Configuration Data .
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.15.12 Parameters for Modifying the Synchronization of NE Configuration Data
Prerequisite
You have logged in to the M2000 client.
Context
l The synchronization of the NE log is the system timing task and only supports the period
type.
l Only users in the administrator group can modify the task.
l You can modify the following parameters: Task Name, Start Time, and Period.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Synchronization > NE Log Synchronization.
Step 3 Select an already created synchronization task of the NE log from the task list to the right.
Step 5 Click Common Parameters. For details of resetting the parameters, refer to 14.15.4
Parameters for Setting Common Information.
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l Inventory data refers to the physical asset information and major logical configuration
information.
l The synchronization of the inventory data is the system timing task and only supports the
period type.
l Only users in the administrator group can modify the task.
l You can modify the following parameters: Task Name, Start Time, Period, and NE.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Synchronization > Inventory Data
Synchronization.
Step 3 Select an already created synchronization task of the inventory data from the task list to the right.
Step 4 Double-click or click Attribute to view the Attribute dialog box.
Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their
corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common
Information and 14.15.13 Parameters for Modifying the Synchronization of Inventory
Data.
NOTE
The reset value of Start Time must be later than the current server time.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Related References
14.15.13 Parameters for Modifying the Synchronization of Inventory Data
Related References
14.15.18 Parameters for Modifying Database Capacity
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management task for operation logs can
be executed only periodically.
l Only users in the administrator group can modify the task.
l You can modify the following parameters: Task Name, Start Time, File Format,
Compress after Export, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management.The Task Management dialog box is displayed.
Step 2 In the navigation tree, choose Task Type > Database Capacity Management > Operation
Log.
Step 3 From the task list, select one database capacity management task that is already created for
operation logs.
Step 4 Double-click or click Attribute to view the Attribute dialog box.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management task for system logs can be
executed only periodically.
l Only the users belonging to the administrator group have the right to modify the database
capacity management for system logs.
l You can modify only the following parameters: Task Name, Start Time, File Format,
Compress after Export, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Database Capacity Management > System
Logs.
Step 3 From the task list, select one database capacity management task that is already created for
system logs.
Step 4 Double-click or click Attribute to view the Attribute dialog box.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management task for security logs can be
executed only periodically.
l Only the users belonging to the administrator group have the right to modify the database
capacity management for security logs.
l You can modify only the following parameters: Task Name, Start Time, Compress after
Export, File Format, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Database Capacity Management > Security
Log.
Step 3 From the task list, select one database capacity management task that is already created for
security logs.
Step 4 Double-click or click Attribute to view the Attribute dialog box.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management for NE operation logs can be
executed only periodically.
l Only the users belonging to the administrator group have the right to modify the database
capacity management for NE operation logs.
l You can modify only the following parameters: Task Name, Start Time, Compress after
Export, File Format, and Save Days.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Database Capacity Management > NE Operation
Log.
Step 3 From the task list, select one database capacity management task that is already created for NE
operation logs.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management task for NE security logs can
be executed only periodically.
l Only users in the administrator group can modify the task.
l You can modify only the following parameters: Task Name, Start Time, Compress after
Export, File Format, and Save Days.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Database Capacity Management > NE Security
Log.
Step 3 From the task list, select one database capacity management task that is already created for NE
security logs.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management task of alarm data can be
executed only periodically.
l Only users in the administrator group can modify the task.
l You can modify only the following parameters: Task Name, Start Time, Compress after
Export, File Format, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select Task Type > Database Capacity Management > Alarm Data.
Step 3 From the task list, select one database capacity management task that is already created for alarm
data.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
Prerequisite
You have logged in to the M2000 client.
Context
l As a system periodic task, the database capacity management task for performance data
can be executed only periodically.
l Only users in the administrator group can modify the task.
l You can modify only the following parameters: Task Name, Start Time, Compress after
Export, and Save Days.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > Database Capacity Management > Performance
Data.
Step 3 From the task list, select one database capacity management task that is already created for
performance data.
Step 5 Click Common Parameters or Extended Parameters to reset parameters. For details, refer to
14.15.4 Parameters for Setting Common Information and 14.15.18 Parameters for
Modifying Database Capacity.
NOTE
The reset value of Start Time must be later than the current server time.
You can browse the newest task information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
such as performance data, configuration data, and log data. After modifying the export
conditions, you can export data by using the new parameters.
Prerequisite
l You have logged in to the M2000 client.
l The performance data is exported.
Context
l The M2000 enables you to export performance data based on the performance result query
template.
l The task of exporting performance data is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, File Format,
Hold Days, Object, Measurement Period, Export Period, and Delay Time.
l SBC, IMSOMU, CCF and MRF do not support this function.
Procedure
Step 1 Choose Maintenance > Task Management to view the Task Management window.
Step 2 In the navigation tree, choose Task Type > File Interface > Performance Data Export .
Step 3 Select a task from the task list in the right part of the window.
Step 4 Click Attribute. The Attribute dialog box is displayed.
Step 5 Modify the parameter settings.
Common parameter Click the Common Parameter tab and then modify the
parameter settings. For details, refer to 14.15.4 Parameters
for Setting Common Information.
Extended parameter 1. Select the tab which shows the measurement period of the
performance measurement subset to be exported, for
example, 5Minute.
2. An optional step: If you need to export the performance
measurement data based on performance query template,
click the Template tab and then choose one or more query
templates. For a detailed description of the performance
result query template, refer to 6.3.9 Managing Result
Query Templates.
3. On the Function Subset tab page, select the function subset
to be exported. You can select Show Measuring Function
Subsets or Show All Function Subsets to set the
navigation tree organization style. You can enter the
conditions for filtering the search to locate the function
subset.
4. Click to add the selected function subset to
Selected Function Subsets list. You can also click
to remove function subsets from the Selected
Function Subsets list.
5. Set Export Period and Hold Days. For details, refer to
14.15.23 Parameters for Modifying the Export of
Performance Data.
NOTE
l If you export performance data by template, the M2000 enables you to export by period. That is, if the
measurement period of an NE is 30 minutes, the measurement period set in the template is 60 minutes, then
the M2000 summarized the performance data of 30-minute period and export them by 60-minute period.
l After you export performance data by template, the Export Period setting cannot be modified.
----End
Result
Modified parameter values are displayed in the task list.
Related References
14.15.23 Parameters for Modifying the Export of Performance Data
Prerequisite
l You have logged in to the M2000 client.
l The alarm data export task is exported.
Context
l The task of exporting performance data is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, Period, File
Format, Compact, Alarm Level, Type, Category, and Alarm Name.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select Task Type > File Interface > Alarm Data Export.
Step 3 Select a task from the task list in the right part of the window.
Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their
corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common
Information and 14.15.19 Parameters for Modifying the Export of Alarm Data.
----End
Result
Modified parameter values are displayed in the task list.
Related References
14.15.19 Parameters for Modifying the Export of Alarm Data
Prerequisite
l You have logged in to the M2000 client.
l The configuration data is exported.
Context
l The task of exporting performance data is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, Period, All NE
Configuration Data, and Please select an NE.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select Task Type > File Interface > Configuration Data Export.
Step 3 On the right side of the window, select a task from the task list.
Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. For
details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.20
Parameters for Modifying the Export of Configuration Data.
----End
Result
After the modification, the new values are displayed in the task list.
Related References
14.15.20 Parameters for Modifying the Export of Configuration Data
Prerequisite
l You have logged in to the M2000 client.
l The operation log is exported.
Context
l The task of exporting operation logs is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, File Format,
Whether to compress, and File Format.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select Task Type > File Interface > Operation Log Export.
Step 3 On the right side of the window, select a task from the task list.
Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. For
details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.22
Parameters for Modifying the Export of Operation Log.
----End
Result
After the modification, the new values are displayed in the task list.
Related References
14.15.22 Parameters for Modifying the Export of Operation Log
Prerequisite
l You have logged in to the M2000 client.
l The system log is exported.
Context
l The task of exporting system logs is a system-schedule task and only supports the periodic
execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, Period, Whether
to compress, and File Format.
Procedure
Step 1 Choose Maintenance > Task Management. The Integrated Task Management window is
displayed.
Step 2 In the navigation tree, choose Task Type > File Interface > System Log Export.
Step 3 On the right side of the window, select a task from the task list.
Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters.
Step 6 Click OK.
If the parameter modification fails, a prompt is displayed.
----End
Result
After the modification, the new values are displayed in the task list.
Prerequisite
l You have logged in to the M2000 client.
l The operation log is exported.
Context
l The task of exporting security logs is a system-schedule task and only supports the periodic
execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, Period, Whether
to compress, and File Format.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, choose Task Type > File Interface > Security Log Export.
Step 3 On the right side of the window, select a task from the task list.
Step 4 Click Attribute. The Attribute dialog box is displayed.
Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters.
Step 6 Click OK.
If the parameter modification fails, a prompt is displayed.
----End
Result
After the modification, the new values are displayed in the task list.
Prerequisite
l You have logged in to the M2000 client.
l The NE operation log is exported.
Context
l The task of exporting NE operation logs is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, Period, and File
Format.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select Task Type > File Interface > NE Operation Log Export.
Step 3 On the right side of the window, select a task from the task list.
Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. For
details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.21
Parameters for Modifying the Export of NE Log.
----End
Result
After the modification, the new values are displayed in the task list.
Related References
14.15.21 Parameters for Modifying the Export of NE Log
Prerequisite
l You have logged in to the M2000 client.
l The NE security log is exported.
Context
l The task of exporting NE security logs is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify only the following parameters: Task Name, Start Time, Period, and File
Format.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select Task Type > File Interface > NE Security Log Export.
Step 3 On the right side of the window, select a task from the task list.
Step 5 Click the tab Common Parameters or Extended Parameters and set the parameters. For
details, refer to 14.15.4 Parameters for Setting Common Information and 14.15.21
Parameters for Modifying the Export of NE Log.
----End
Result
After the modification, the new values are displayed in the task list.
Related References
14.15.21 Parameters for Modifying the Export of NE Log
Prerequisite
l Log in to the M2000 client successfully.
l The task of exporting performance data is already created.
Context
l The task of exporting inventory data is a system-schedule task and only supports the
periodic execution.
l Only users in the administrator user group can perform this operation.
l You can modify the following parameters: Task Name, Start Time, Period, File Path,
and NE.
l IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC and MRF do not support this
function.
Procedure
Step 1 Choose Maintenance > Task Management to view the Task Management window.
Step 2 Select Task Type > File Interface > Inventory Data Export node in the navigation tree to
the left.
Step 3 Select a task from the task list in the right part of the window.
Step 5 Click the Common Parameters tab or the Extended Parameters tab. Set parameters in their
corresponding pages. For details, refer to 14.15.4 Parameters for Setting Common
Information and 14.15.13 Parameters for Modifying the Synchronization of Inventory
Data.
----End
Result
Modified parameter values are displayed in the task list.
Related References
14.15.13 Parameters for Modifying the Synchronization of Inventory Data
Context
l The M2000 system data backup is a scheduled task. The task only supports the periodic
run type.
l Only users in the administrator user group can perform this operation.
l For the backup of M2000 system data, you can modify the following parameters: Task
Name, Start Time, and Server Full Backup Date.
Procedure
Step 1 Choose Maintenance > Task Management.
Step 2 Under the task navigation tree in the left pane, select Backup.
Step 3 From the task list in the right pane, select the server backup task.
Step 4 Click Attribute.
The Attribute dialog box is displayed.
Step 5 Click the Common Parameters tab or the Extended Parameters tab and set the parameters.
l To know how to set the Common Parameters, refer to 14.15.4 Parameters for Setting
Common Information.
l To know how to set the Extended Parameters, refer to 14.15.25 Parameters for Modifying
Data Backup in the M2000.
Step 6 Click OK.
----End
Result
You can query modified parameter values in the task list.
Related References
14.15.25 Parameters for Modifying Data Backup in the M2000
Prerequisite
l You have logged in to the M2000 client.
l The alarm timing acknowledgement task is created.
Context
NOTE
l The task of alarm timing acknowledgement is a scheduled task of a system. The task supports only
the periodic run type.
l Only users in the administrator user group can modify parameters of an alarm timing
acknowledgement task.
l You can modify only the following parameters: Task Name, Start Time, Period, Alarm Level, and
Alarm Status.
Procedure
Step 1 Choose Maintenance > Task Management.
The Task Management window is displayed.
Step 2 In the navigation tree in the left pane, select Task Type > Other > Alarm
Acknowledgement.
Step 3 From the task list in the right pane, select a created alarm scheduled acknowledgement task.
Step 5 Click the Common Parameters tab or the Extended Parameters tab and set parameters. To
know how to set the parameters, refer to 14.15.17 Parameters for Modifying Alarm Timing
Acknowledgement.
NOTE
The reset start time must be later than the current server time.
You can view the latest information about the task in the task list.
NOTE
If the task is running, the modified data takes effect when the task is restarted.
----End
Related References
14.15.17 Parameters for Modifying Alarm Timing Acknowledgement
Prerequisite
l You have logged in to the M2000 client.
l The NE license sharing management task has been created in the system.
Context
l The NE license sharing management task is a system timing task and can be carried out
periodically.
l Only the users in the Administrators user group can modify the NE license sharing
management task.
When the NE license sharing mangement task is running, the system checks the following items:
l The system checks whether the network licenses allocated to NEs by the license sharing
group outnumbers the actual available resource value. If the allocated network value
outnumbers the available license resources, the system sends an alarm to the M2000 server,
indicating that the number of used licenses exceeds the limit. Based on the alarm
information, you can handle the problem. For details, see ALM-515 The amount of used
license's resource exceeds the threshold.
If the local license files on NEs are updated or out of date, the network license that are
assigned to NEs by the license sharing group may exceed the actual available resource
value.
l The system checks whether the network license on NEs is consistent with the network
license on the server. If they are inconsistent, the system sends an alarm to the M2000
server, indicating that the number of NE licenses changes. Based on the alarm information,
you can handle the problem. For details, see ALM-514 Changes in the usage of NE license
resources.
When you adjust license resources between NEs in the license sharing group, the network
licenses on NEs may differ from the network licenses that are actually allocated to the
M2000 server because of NE disconnection.
l The system checks whether an NE in the license sharing group is disconnected from the
M2000 for over 15 days. If an NE is disconnected for over 15 days, the system automatically
removes the NE from the group.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Other > NE Software Download in the left navigation tree.
Step 3 Select an already created NE license sharing management task from the right task list.
Step 4 Double-click or click Attribute to open the Attribute dialog box.
Step 5 Reset the start time to carry out the task.
NOTE
The reset value of Start Time must be later than the current server time.
If the task is running, the modified data takes effect at the next execution.
----End
You can set an automatic suspend time or an automatic restore time for a scheduled task. In this
situation, the M2000 automatically suspends the task or restores the task.
14.10.6 Browsing CME Subtask
When you create an CME tasks, the system automatically creates multiple subtasks by NE. You
can browse a CME subtask to view the main task name, the creator, the completion progress,
and the result of the subtask.
14.10.7 Setting Period of CME Subtask
By setting a period of a CME subtask, you can better control execution time of each subtask in
the period.
14.10.8 Terminating Descendant Tasks
You can terminate CME downloading sub-tasks.
14.10.9 Rolling Back Descendant Tasks
You can roll back the activated CME download subtasks.
Prerequisite
l You have logged in to the M2000 client.
l At least one timing task exists.
Context
l Each user can delete only the tasks that are created by him. A user in the
Administrators group can delete all the user timing tasks created by any user.
l System tasks cannot be deleted.
l Running tasks cannot be deleted.
l You can delete only an Archived CME download task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 3 Select one or more scheduled tasks in the task list in the right pane.
----End
Result
Then the task is deleted from the task list.
Prerequisite
l You have logged in to the M2000 client.
l At least one idle timing task exists.
Context
The system uses the tasks that are not suspended.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 3 Select one or more tasks in the task list in the right pane.
Step 4 Right-click the task and select Suspend from the shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l At least one suspended scheduled task exists.
Context
Only idle tasks can wait to be used.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 3 Select one or more tasks in the task list in the right pane.
Step 4 Right-click the task and select Restore from the shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l At least one Running timing task exists.
Context
A user in the common user group can cancel only the tasks created by himself. A user in the
Administrators group can cancel all the user timing tasks created by any user.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 3 Select one or more running tasks in the task list in the right pane.
Step 4 Right-click the task and select Cancel from the shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l At least one suspended or idle timing task exists.
Context
l The system suspends an idle task and delay the time for using this task. If the timing task
is not in the Idle state at the specified time, it fails to be suspended.
l In the specified time, the system resume a suspended task and then the task is in the idle
status and wait to be dispatched. If the timing task is not in the Idle state at the specified
time, it fails to be suspended.
l You are not allowed to set auto-suspend or resume a Running timing task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select the task type of which you plan to suspend.
Step 3 From the task list in the right part of the window, select a timing task to be suspended.
Step 4 Right-click the task and choose Timing Suspend/Resume.
Step 5 In the displayed Timing Suspend/Resume dialog box, select Suspend Time or Resume
Time as required.
Step 6 Set the suspend time or resume time.
For details of setting an automatic suspend time or an automatic restore time, refer to 14.15.26
Parameters for Setting Time of Timing Tasks.
----End
Related References
14.15.26 Parameters for Setting Time of Timing Tasks
Prerequisite
l You have logged in to the M2000 client.
l At least one CME subtask exists.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > CME > CME Download in the navigation tree.
Step 3 Select a task from the task list in the right part of the window.
Step 4 Right-click the task and choose Subtask. The Subtask Browsing dialog box is displayed.
For details about the parameter meaning of the subtask browsing, refer to 14.15.27 Parameters
for Browsing CME Subtask.
----End
Related References
14.15.27 Parameters for Browsing CME Subtask
Prerequisite
l You have logged in to the M2000 client.
l At least one CME download subtask is not scheduled.
Context
The operation is performed only for the CME download task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > CME > CME Download in the navigation tree.
Step 3 Select a task from the task list in the right part of the window.
Step 6 Right-click the subtask and choose Phase Time or click the Phase Time button. The Phase
Time Setting dialog box is displayed.
For details about the setting of a period, refer to 14.15.28 Parameters for Setting Period of
CME Subtask.
----End
Related References
14.15.28 Parameters for Setting Period of CME Subtask
Prerequisite
l You have logged in to the M2000 client.
l At least one Running CME download subtask exists.
Context
Only CME download subtasks can be terminated.
CAUTION
The determination of sub-tasks cannot be restored. Once a sub-task is terminated, it cannot be
dispatched and all the related operations such suspending and recovering are inapplicable. Be
cautious when performing this operation.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 3 Select one or more tasks in the task list in the right pane.
Step 4 Right-click the task and select Terminate from the shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l An activated CME download subtask exists. The configuration data takes effect on the NE.
Context
Only the CME download subtasks support the fallback function.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 3 In the task list, select one or multiple activated CME subtasks.
Step 4 Right-click and then select Resume in the displayed shortcut menu.
----End
Prerequisite
l You have logged in to the M2000 client.
l At least one timing task exists.
Context
l Common users, that is, the users not belonging to the administrator group, are allowed to
browse all user tasks rather than system tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Select Task Type in the navigation tree.
l In the task list, all the tasks are displayed.
l If you want to view the common parameters and extended parameters of each task, go to
Step 3
Step 3 Double click a task, or select a task and click Attribute. The Attribute dialog box is displayed.
In the Common Parameter and Extended Parameter tab pages, you can view the task details.
----End
Prerequisite
l You have logged in to the M2000 client.
l At least one timing task exists.
Context
l During the creation of CME tasks, sub-tasks are created, which are executed in different
phases.
l You can browse the execution progress of subtasks of CME tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select the task type of which you plan to check the progress.
l View the task progress in the Progress column at the right.
l To check the progress of the CME subtask, select the task in the list and view the progress
in the Progress column.
----End
Prerequisite
l You have logged in to the M2000 client.
l At least one timing task exists.
Context
l During the creation of CME tasks, sub-tasks are created, which are executed in different
phases.
l You can browse the execution progress of subtasks of CME tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
----End
Prerequisite
l You have logged in to the M2000 client.
l The timing task that is used for downloading the result files exists and it is run for at least
once.
Context
The allowable operations vary depending on the task type, as shown in Table 14-7.
CME and HSL script The task result are saved on the server in logs. The Result Info area
tasks displays only the information about the last task execution. The
result logs are not displayed.
You can download all the result files to the local client. Result files
of multiple tasks can be downloaded concurrently.
MML script task You can download the latest result file to the local client. Result
files of multiple tasks can be downloaded concurrently.
Network health check You can download the result file of the selected task. Result files
task of multiple tasks can be downloaded concurrently.
Dual Home You can view the latest consistency check result on line.
Management tasks
Timing task, NE If a task is performed at least once, you can save the messages in
Software Download the Result Info area to a local path.
task, and NE Backup
task
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 In the navigation tree, select the type of the task that is used to download the result files. Select
the specific tasks in the right pane.
Step 3 Perform the following operations according to the task type.
CME or HSL script task To download the result logs of a download task,
perform the following steps:
1. Select the task whose result logs you plan to
download.
2. Click Save Log. In the displayed Please select a
directory dialog box, set the save path
3. Click OK.
NOTE
The system generates a folder for the log file generated
each time and saves the folder to the specified path.
The result log file is named in the format YYYY-MM-
DD_HH-MM-SS, for example,
2008-04-18_10-27-53.
Network health check task 1. Select the task whose result files you plan to
download.
2. Right-click a task and choose NHC Report on
the shortcut menu.
3. In the displayed NHC Report dialog box, select
the check report based on Report Nameand then
click Save.
NOTE
You can click Open to view the contents of the check
report and decide whether the report needs to be
downloaded.
4. Set the save path in the displayed Please select a
directory dialog box.
5. Click OK.
Dual Home Management tasks Right-click a task and choose Checked Result from
the shortcut menu.
NOTE
If data inconsistency exists, you need to generate a script
to adjust the data difference and synchronize the data. For
details, refer to 11.2.5 Generating the Script for
Adjusting Difference Data and 11.2.7 Synchronizing
the Dual-Homing Data.
----End
(2) Task result information After a task is carried out, the task result is
panel displayed. On the task result information
panel, you can browse the result of the task
last carried out. Only the result of the
currently selected task is displayed on the
task result information panel. If multiple
tasks are selected in the task list, only the
result of the firstly selected task is
displayed.
(3) Button panel The buttons used for carrying out central
task management are available on the
button panel.
(4) Task list You can browse the timing tasks that exist
on the server side and the detailed
information. In the task list, different colors
are used for indicate different states of
tasks: Gray: complete Orange: suspended
Blue: active White: idle The selected color
of the task is darker than the previous color
of the task.
Parameter Description
Parameter Description
User Current User Indicates the user that operates the client.
Name
Other Users Indicates other users except the current user.
State Idle Indicates that the task waits for being performed by the system.
Parameter Description
Archived The archived state is supported only by the CME download task.
After the CME download task is stopped, the task is archived. Only
when the task is in the archived state, the task can be deleted.
Miss Run Indicates that the task misses the previous performed time. If the
Time server is not running properly or the task is suspended before the
execution, the task may miss the previous execution.
Unknown Indicates that the previous execution result in the server is lost
caused by improper service or sudden power cut. Thus, after
recovery, the previous execution result cannot be determined.
Related Tasks
14.1.6 Customizing the Interface for Managing Timing Tasks
Parameter Description
Parameter Value Range Description
Task Type Select from Task Type. Select a task that you
require, such as NE
Backup.
Parameter Description
Parameter Value Range Description
Parameter Description
Parameter Description
Task Name Indicates the name of a task. The Task Name cannot be modified
in this dialog box.
Related Tasks
14.2.5 Creating CME Download
14.3.5 Modifying CME Download
Parameter Description
Parameter Value Range Description
Parameter Description
Parameter Description
Time Setting Start Time You can either enter the time value in this
field, or click to select the date and time
in the Date/Time Selection dialog box.
If the Run Immediately check box is
selected, the task is performed immediately
after you set the parameters.
Parameter Description
Parameter Value Range Description
Script file The script file The script file is a text file recording MML commands for
is in .txt one NE or multiple NEs of the same type. Enter the path
format. The for MML script file in this field or click to select MML
maximum size script file in the Open dialog box.
is 1 MB.
Redirect result None. If the created task is a one-time task, you can select
Redirect Result and set the path of Redirect File to add
the task result to the specified redirection file. You can
create a non-existent file. If the redirection file exists, the
new messages does not overwrite the original messages.
If you set the result redirection of a task, the path of
Redirect File cannot be changed after the task is
completely created.
Select NE None. After you select this option, you can change the NE of the
script command by selecting the NE in the NE tree instead
of modifying the script file. After the NE is reelected, the
original NE information is invalid and all commands are
sent to all the newly selected NEs.
The NE tree displays all the NEs in a physical topology
tree. The function buttons for selecting NEs are as follows:
l : to expand the NE tree.
l : to expand the NE tree.
Run-time Type Collateral or Two modes for issuing MML commands are available:
Serial. l Collateral: indicates that the MML commands are
issued to the NE concurrently.
l Serial: indicates that the MML commands are issued to
the NE in sequence.
Related Tasks
14.2.1 Creating MML Command Script
14.3.1 Modifying MML Command Script
Parameter Description
Parameter Value Range Description
NE Type Select the value from the Indicates all of the NE types available in the
drop-down list. current network.
Edition List None. Indicates the editions of all NEs that can be
downloaded from the server. These NEs are of
the same type. Multiple choices are not allowed.
Related Tasks
14.2.2 Creating Software Download
14.3.2 Modifying Software Download
Parameter Description
Parameter Description
File Path Indicates the path for saving NE data backup files. The saving path is specified
by the system.
Backup All If you select this check box, the system backs up the data of all the NEs
NE available in the current network. By default, the system backs up the data of
all the NEs in the entire network.
NE Type Indicates the NE type that is available in the current network. Multiple choices
are supported. Only if you select the Backup All NE, you can select specified
NEs in the NE Type.
Related Tasks
14.2.3 Creating Entire NE Backup
14.3.3 Modifying Entire NE Backup
Parameter Description
Parameter Description
All NE Select this check box and the system uploads the configuration data of
all RNCs and NodeBs in the current network.
Related Tasks
14.2.4 Creating CME Upload
14.3.4 Modifying CME Upload
Parameter description
Parameter Description
Please Select Select existing NEs in the entire network. Multiple NEs are supported.
NE
Related Tasks
14.4.2 Modifying the Synchronization of NE Configuration Data
Parameter Description
Parameter Description
All NE If you select this option, the system synchronizes the inventory data of all
NEs on the network.
Please Select Indicates all the NEs in the entire network. Multiple NEs are supported.
NE You can select the specific NEs in Please Select NE only after you seselect
All NE.
Related Tasks
14.4.4 Modifying the Synchronization of Inventory Data
Parameter Description
Parameter Value Range Description
Upload files The upload file is Upload a command file from a local client to the
in .xml format. The M2000 server.
upload file cannot be
empty.
Related Tasks
14.2.5 Creating CME Download
14.3.5 Modifying CME Download
Parameter Description
Parameter Value Range Description
Main File The main file is in .hsl The main file is the entry file for the execution
format. The main file has of script files.
a maximum size of 1
MB.
Assistant File The assistant file has a When the script files are being executed, the
maximum size of 1 MB. main file selects from assistant files if the main
file need to invoke other script files.
NE Selection None. You need to select NEs when script files contain
operations on several NEs. Multiple choices are
supported.
Related Tasks
14.2.6 Creating HSL Script
14.3.6 Modifying HSL Script
Parameter Description
Parameter Description Setting
Dual Homing Pairs Indicates the dual-homing Select from the drop-down list.
pairs. For detailed information
about dual homing, refer to 11
Dual-Homing and LN
Domain Management.
Resource Type Indicates the data resource l Select the item in the
type of the dual homing pairs Resource Type navigation
to be checked. tree.
Data resource types vary l Enter the data resource type or
depending on the version of key word in the Search box.
dual-homing pair NE. Then the related resource
types are listed under the
Search box. You can double-
click resource type to be
checked.
Search Use to search for the type of the Enter the data resource type of
data resource to be checked. key word in the Search box.
The search conditions support
case insensitive fuzzy search.
Wildcard search is not
supported.
Related Tasks
14.2.7 Creating Dual-Home Management
14.3.7 Modifying Dual-Home Management
Parameter Description
Parameter Value Range Description
l Minor
l Warning
Alarm State l Unacknowledge Indicates the alarm states. Multiple choices are
and unclear Fault supported.
l Unacknowledge
and clear Fault
Related Tasks
14.8 Modifying Alarm Timing Acknowledgement
Parameter Description
Parameter Value Range Description
Compress File Select the value from When the data in the database expires, the
After Export the drop-down list. system can choose to compress files during
export. You can select either Yes or No in this
field. The system selects Yes by default.
File Format Select the value from The format of the file that saves the exported
the drop-down list. data.
File formats vary with tasks as follows:
l The data files for performance database
capacity management are in .csv format.
l The data files for NE operation and security
log database capacity management are
in .txt or .csv format.
l The data files in database capacity
management for alarms, operation logs,
system logs, and security logs are in .xml
or .csv format.
Exported file None Indicates the path for saving exported data. The
format save file path is specified by the server and
cannot be modified by users.
The default export path for each database
capacity management task is as follows:
l Log database capacity management tasks: /
export/home/omc/var/ThresholdExport/
Log.
l Alarm database capacity management
tasks: /export/home/omc/var/
ThresholdExport/FM.
l Performance database capacity
management tasks: /export/home/omc/
var/ThresholdExport/PM/.
Hold Days Select Common Mode Applicable to only the task of managing the
Setting or Configuration capacity of performance database.
Mode. l Common Mode: Enter the Hold Days in
the Database. The value ranges from 1 to
90. The default value is 30.
l Configuration Mode: Specify a
Configuration File. The system uses the
hold days specified in the configuration file.
Related Tasks
14.5 Modifying Database Capacity
File Type You can choose: Exports to a .csv file or .xml file.
l CSV
l XML
Compress Exported You can select and deselect. l Select the parameter to
File compress the .csv files or .xml
files to a packet and export.
l Deselect the parameter to
export to a .csv file or .xml file.
Export Path Default value. No change. Indicates the save path of the
The default path is: /export/ exported alarm data.
home/omc/var/fileint/fm/.
Alarm Options in the drop-down list. Select the severity level, type, and
Level,Category,Type l Alarm severity levels are: category of the alarm.
Critical, Major, Minor, and
Warning.
l Alarm types are: current
alarm, event alarm, history
alarm, and shielded alarm.
l Alarm categories are: Power
System, Environment
System, Signaling System,
Trunk System, Hardware
System, Software System,
Running System,
Communication System,
QoS, Processing Error, and
Internal.
Alarm Name Options in the drop-down list. Lists the alarms whose data can be
exported currently.
Related Tasks
14.6.2 Modifying the Export of Alarm Data
File Format Selected from the drop-down The format of the file that saves
list. Two formats are available, the exported data.
that is, .xml and .csv.
File Path Default value. No change. Indicates the path to save the
The default path is: /export/ exported configuration data.
home/omc/var/fileint/cm/
autoExport.
Please Select NE NEs in the list. l Click to expand all the sub
nodes.
l Click to collapse all the sub
nodes.
l Click to cascading select.
That is, by selecting a parent
node, all the subnodes under it
are selected.
Related Tasks
14.6.3 Modifying the Export of Configuration Data
File Path Default value. No change. Indicates the path to save the NE
The default path is: /export/ logs.
home/omc/var/fileint/nelogs/.
File Format You can choose TXT or CSV Exports the operation logs to a .txt
format. file or .csv file.
Related Tasks
14.6.7 Modifying the Export of NE Operation Log
14.6.8 Modifying the Export of NE Security Log
Exported File Format You can choose: Exports operation logs to a .csv
l CSV file or .xml file.
l XML
Save File Path Default value. No change. The path to save the exported
The default path is:/export/ operation logs.
home/omc/var/fileint/
***logs/, where *** stands for
the log type.
Related Tasks
14.6.4 Modifying the Export of Operation Log
Measurement Period You can click different Set the measure period of the
measurement period tabs. exported task.
Export Period Options in the drop-down list. Set the execution period of the
exported task. The value is
determined by the NE type.
NOTE
The export period of performance
data must be consistent with the
measure period of performance
data.
Delay Time The value must be multiples of 5 The parameter stands for the
minutes. delay time of running the task.
Value range: 5-1440.
The unit is minute.
Related Tasks
14.6.1 Modifying the Export of Performance Data
Parameter Description
Parameter Description
File Path Indicates the path to save the exported inventory data.
Default value: /export/home/omc/var/fileint/cm/InvtTimerExport.
All NE If you select this option, the system exports the inventory data of all NEs
on the network. This option is selected by default.
Please Select Indicates all the NEs in the entire network. Multiple NEs are supported.
NE You can select the specific NEs in Please Select NE only after you deselect
All NE.
Related Tasks
14.6.9 Modifying the Export of Inventory Data
Server Full Backup Form Monday to Sunday The full backup is executed each week.
Date If you set to Monday, the full backup
is performed each Monday.
File Path Default value. No change. The path to save the backup M2000
The default path is:/export/ system data.
home/backup/omc.
Related Tasks
14.7 Modifying Data Backup in the M2000
Parameter Description
Suspend Time The system suspends an idle task and delay the time for
using this task. If the timing task is not in the Idle state
at the specified time, it fails to be suspended.
You can set the value manually. Alternatively, you can
click and select the time from the time select panel.
The time format is DD/MM/YYYY HH:MM:SS.
l yyyy stands for the year.
l MM stands for the month.
l DD stands for the date.
l HH stands for the hour.
l MM stands for the minute.
l SS stands for the second.
Resume Time In the specified time, the system resume a suspended task
and then the task is in the idle status and wait to be
dispatched. If the timing task is not in the Idle state at the
specified time, it fails to be suspended.
You can set the value manually. Alternatively, you can
click and select the time from the time select panel.
The time format is DD/MM/YYYY HH:MM:SS.
l yyyy stands for the year.
l MM stands for the month.
l DD stands for the date.
l HH stands for the hour.
l MM stands for the minute.
l SS stands for the second.
Related Tasks
14.10.5 Setting Time of Timing Tasks
Parameter Description
Task Name Name of the main task that the subtask belongs to.
Parameter Description
Run Type Execution type of the main task. The type can be Once or
Period.
Verity Period Start time of verity period, which equals to end time of
downloading plus verification interval.
Reactivated Period Start time of peractivated period, which equals to end time of
verity period plus preactivation interval.
Activated Period Start time of activated period, which equals to end time of verity
period plus activation interval.
Parameter Description
Related Tasks
14.10.6 Browsing CME Subtask
Start Time of Download The time for starting the CME subtask download.
You can set the value manually, or select from the time
select panel.
The time format is YYYY-MM-DD HH:MM:SS.
l yyyy stands for the year.
l MM stands for the month.
l DD stands for the date.
l HH stands for the hour.
l MM stands for the minute.
l SS stands for the second.
Verity Period The interval between the end time of the download period
and the start time of the verity period.
Reactivated Period The interval between the end time of the verity period and
the start time of the Preactivate period.
Activated Period The interval between the end time of the Preactivate
period and the start time of the activated period.
Related Tasks
14.10.7 Setting Period of CME Subtask
15 NE Commissioning
The NE commissioning refers to the process that the M2000 automatically commissions the
selected NEs. The NE commissioning includes the following items: automatically detecting and
configuring the devices, automatically checking the performance of new base station, and
automatically generating the commissioning report. You can monitor the commissioning process
on the M2000 client and determine the network performance by analyzing the generated
commissioning report. Currently, only the NodeB commissioning can be performed.
For details about the NodeB commissioning items, refer to Table 15-1.
NodeB Description
Commissioning
Item
ConfigFile Download the configuration file, which is uploaded from the client to
Download the server, to the NodeB.
NodeB Description
Commissioning
Item
BootRom Download Download the BootRom from the server to the NodeB.
BootRom Activate Download the BootRom software, which is saved in the NodeB
standby file partition, to each board and upgrade the BootRom of each
board.
Software Download Download the NodeB software from the server to the NodeB.
The NodeB software is saved in the NodeB standby file partition after
being downloaded. The NodeB software does not take effect
immediately, or does not damage the software that is operating. The
NodeB software takes effect till it is activated.
Software Activate Download the NodeB software, which is saved in the NodeB standby
file partition, to each board so that the software takes effect.
Health Check Check the running status of the devices. The check items include the
configuration status, cells, IPRAN status, and environment.
Prerequisite
l The NodeB is properly connected to the M2000.
l The configuration file of the commissioned NodeB have been generated by the CME.
l The NodeB software and the BootRom has been uploaded to the M2000.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
Step 2 Click Create NodeB Commissioning Project. The Create NodeB Commissioning Project -
Please Select The NodeBs To Be Surveyed dialog box is displayed.
Step 3 Set the Project Name and select the NodeB node for commissioning.
l You can select one or several items of RNC, NodeB Type, and Version to regroup the
NodeBs in the OMC tree according to the rule.
l Enter the name of the NodeB in Search, and the system directly locates it.
l You can select one or multiple NodeBs for the commissioning.
l After creating a commissioning task, you can modify it by adding NodeB objects. For details,
refer to 15.1.4 Modifying NodeB Commissioning Tasks.
l The OMC tree does not display the commissioned NodeBs.
Step 4 Click Next. The Create NodeB Commissioning Project - Configuration Setting dialog box
is displayed.
Step 5 In the Parameter Setting pull-down box, select the version numbers of the BootRom and
NodeB.
The system supports the upload of configuration files by batches. Therefore, all the configuration
files are uploaded to the server if you select the directory of the NodeBConfig folder, regardless of
one or multiple configuration files that you select for the upload.
3. Click Upload Config To Server. The mapping NodeB configuration file is uploaded to
the server.
----End
Prerequisite
The NodeB commissioning tasks are created.
Procedure
Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
You can view the information abou the NodeB commissioning in this window.
– All the tasks that are commissioned are displayed in the Running node of the Projects tab
page. All the tasks that have finished commissioning are displayed in the Finished node.
Select a commissioning task. The information about the NodeBs that are allowed to be
commissioned is displayed in the NodeB list at the right. The information includes NodeB
Name, Current Status, and Percent.
– Click Refresh. The information in the NodeB Commissioning window can be refreshed in
real time.
– You can view the detailed information about the NodeB commissioning in the NodeB Check
Information area. You can also delete all the information about the NodeB commissioning
in the area if you right-click Clean All Messages.
----End
Prerequisite
The created NodeB commissioning tasks are available.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
Step 2 Perform the following operations according to your requirements.
Add the NodeBs as the commissioning 1. In Projects, select a project that needs to add
objects of the commissioning task a NodeB. Right-click and selectAdd NodeBs
To Project.
2. In Create NodeB Commissioning Project -
Please Select The NodeBs To Be
Surveyed, select one or multiple NodeBs.
Click Next.
3. In Create NodeB Commissioning Project -
Configuration Setting, select the operation
items.
For details, refer to 15.1.2 Creating NodeB
Commissioning Tasks.
4. Click Upload new config file.
5. In Choose NodeBs Config Directory, find
the directory of the NodeB configuration file.
6. Click Upload Config To Server. The
mapping NodeB configuration file is
uploaded to the server.
After the file is uploaded, you can view the
commissioning project of the added NodeBs
in Projects of the NodeB Commissioning
window.
Delete the NodeB from the commissioning 1. In Projects, select a project that needs to
task delete the NodeB.
2. In the list of the commissioned NodeB, select
a NodeB. Right-click and select Delete
NodeBs From Project.
----End
Prerequisite
l The NodeB commissioning tasks are created.
l The NodeB commissioning process of the to-be-deleted task is complete.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
Step 2 Under the Finished node of the Projects, select a NodeB commissioning task. Then, right-click
the window and choose Delete Project from the short-cut menu.
Step 3 In the displayed Delete NodeB Commissioning Project dialog box, click Yes.
----End
Prerequisite
The NodeB commissioning tasks are created.
Context
You cannot restart the commissioning tasks that are being commissioned. Similarly, you cannot
stop the commissioning tasks that have been commissioned.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
----End
Prerequisite
The NodeB commissioning tasks are created.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
Step 2 In Projects, select the project whose NodeB check report is required. Then, right-click Get
Project Report.
NOTE
In the list of the commissioned NodeBs, the check report of the NodeB whose Percent is 100% is complete.
Step 3 In Save File, set the saving directory and file name of the report.
----End
Prerequisite
The NodeB commissioning tasks are created.
Procedure
Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning is displayed.
Step 2 In Projects, select a commissioning task. Then, right-click Upload NodeBs Config File
Again.
Step 3 In Create NodeB Commissioning Project - Please Select The NodeBs To Be Surveyed, click
Next. The Create NodeB Commissioning Project - Configuration Setting is displayed.
Step 4 After selecting the operation items, click Upload new config file.
Step 5 In Choose NodeBs Config Directory, find out the directory where the NodeB configuration
file is placed.
The NodeB configuration files are saved in the folders named by its corresponding NodeB. All
the folders that save the NodeB configuration files are saved in a folder of upper layer, such as
NodeBConfig.
NOTE
The system supports the upload of configuration files by batches. Therefore, all the configuration files are
uploaded to the server if you select the directory of the NodeBConfig folder, regardless of one or multiple
configuration files that you select for the upload.
Step 6 Click Upload Config To Server. The mapping NodeB configuration file is uploaded to the
server.
----End
As shown in Figure 15-1, the NodeB Commissioning interface mainly consists of five parts,
namely, engineering list tab, NodeB list tab, the list of the commissioned NodeBs, and the
detailed NodeB commissioning information domain.
Project name Indicates the project name of the created NodeB commissioning
task .
The name is unique and cannot be null.
Value range: 1 to 255 characters
Spaces and special characters, such as ` ~ ! @ # $ % ^ & * ( ) + =
{ } [ ] \\ | ; ' : \" < > , . ? /, are not allowed.
Search After entering the name of the NodeB, you can locate it in the
OMC tree.
RNC Select this option, then each NodeB in the OMC tree is regrouped
according to the RNCs that the NodeBs belong to.
NodeB type Select this option, then each NodeB in the OMC tree is regrouped
according to the sites that the NodeBs belong to.
Version Select this option, and then each NodeB in the OMC tree is
regrouped according to the versions of the NodeBs.
SoftwareVersion Select the version number of the NodeB from the pull-
down box.
Parameter Description
Health check Check the operating status of the entire network. The
checking items include the configuration status, cells,
IPRAN status, and environment.
Parameter Descriptions
Parameter Description
Look In Select the saving path of the configuration files from the pull-
down box.
File Name Indicates thhe name of the fodler where the configuration files
are saved.
The M2000 provides the enhanced maintenance management for some NEs to facilitate servicing
these NEs. The NE enhanced maintenance management involves device management, trace
management, monitoring management, and real-time performance monitoring. You can start
this function only after the related components are upgraded on the client.
Procedure
Step 1 Select a physical NE on the topology view or from the navigation tree.
Step 2 Right-click the NE and select Upgrade Enhanced NE Maintenance from the shortcut menu.
The Confirm dialog box is displayed, prompting The upgrade file exists. Do you
want to redownload the upgrade file?. If no upgrade file exists in the local PC,
the dialog box is not displayed.
The local system can save only three versions of the upgrade file. Click Yes to redownload the upgrade
file. Click No to run the existing upgrade file.
NOTE
Select a function menu item on the Enhance NE Maintenance menu. If the enhanced public component
version of NE maintenance on the M2000 client is consistent with the version on the M2000 server, the
function is performed. If their versions are not consistent, you need to perform the following operations:
l If the client version is earlier than the server version, the system prompts that enhanced public
components of NE maintenance need be upgraded. Click Yes to start the upgrade of the enhanced
public components of NE maintenance; click No to forcibly perform the maintenance.
l If the client version is later than the server version, the system prompts that enhanced versions of NE
maintenance need be installed on the server. You can also uninstall enhanced public components of
NE maintenance and re-upgrade enhanced versions of NE maintenance.
----End
Prerequisite
Start the device panel on the M2000 client to perform the tracking management on the NEs. The
startup of the device panel must satisfy the following three conditions:
l You have logged in to the M2000 client as an NE user of the NE.
l The mediation software of the NE is installed on both the M2000 server and client.
l The NE is properly connected to the M2000.
Prerequisite
Start the trace panel on the M2000 client to perform the tracking management on the NEs. The
startup of the tracking panel must satisfy the following three conditions:
l You have logged in to the M2000 client as an NE user of the NE.
l The mediation software of the NE is installed on both the M2000 server and client.
l The NE is properly connected to the M2000.
Prerequisite
Start the monitor panel on the M2000 client to perform the tracking management on the NEs.
The startup of the monitor panel must satisfy the following three conditions:
l You have logged in to the M2000 client as an NE user of the NE.
l The mediation software of the NE is installed on both the M2000 server and client.
l The NE is properly connected to the M2000.
Prerequisite
Before starting the real-time performance monitoring management, ensure that the following
four conditions are satisfied:
l You have logged in to the M2000 client as an NE user of the NE.
l The mediation software of the NE is installed on both the M2000 server and client.
l The NE is properly connected to the M2000.
l Only devices of RNC or NodeB support this function.
17 FAQ
This part describes the typical faults of the M2000 client, analyzes the possible causes, and
provides the solution.
This part describes the functions of the keys Ctrl and Shift, and how to use the space key to
quickly select and deselect check boxes.
17.1.1 Prompt "Login failed. Confirm that your user name and password are case sensitive and
correct."
This part analyzes the causes of system prompting wrong user name and password and gives the
solution.
17.1.2 Prompt "Invalid user account."
This part analyzes the cause of the prompt "Invalid user account." and gives the solution.
17.1.3 Prompt "Invalid login duration."
This part analyzes the cause of the prompt "Invalid login duration." and gives the solution.
17.1.4 Prompt "Invalid password."
This part analyzes the cause of the prompt "Invalid password." and gives the solution.
17.1.5 Prompt "The password has expired. Please change your password!"
This part analyzes the causes of the prompt "The password has expired. Please change your
password!" and gives the solution.
17.1.6 Prompt "Maintenance Mode."
This part analyzes the causes of the prompt "Maintenance Mode." and gives the solution.
17.1.7 Prompt "The User Has Reached the Maximum Login Attempts. The User Account Has
Been Locked, and It Can Be Unlocked in 1 Minute."
This part analyzes the causes of system prompting user locked and gives the solution.
17.1.8 Prompt "The Server Doesn't Exist or Service Is Not Running."
This part analyzes the cause of the prompt "The Server Doesn't Exist or Service Is Not Running."
and gives the solution.
17.1.9 Prompt "Exceed Maximum Sessions."
This part analyzes the causes of the prompt "Exceed maximum sessions" at the login and gives
the solutions.
17.1.10 Prompt "Loading Module Failed, System Will Exit."
This part analyzes the cause of the prompt "Loading Module Failed, System Will Exit." and
gives the solution.
17.1.11 Prompt "Failed to Log in to the Server after the Auto Client Upgrade or Running
Exception"
This part analyzes the abnormal running of the client after automatic upgrade and gives the
solution.
17.1.1 Prompt "Login failed. Confirm that your user name and
password are case sensitive and correct."
This part analyzes the causes of system prompting wrong user name and password and gives the
solution.
Symptoms
The login to the M2000 client fails. The system prompts Login failed. Confirm that
your user name and password are case sensitive and correct.
Possible Causes
The possible causes include:
l The user account does not exist.
l The user account is deleted because the user account has not been used for login for more
than six months.
Handling Suggestions
1. Relog in to the M2000 client with the correct user name and password.
2. Recreate the user account.
Symptoms
The login to the M2000 client fails. The system prompts Invalid user account.
Possible Causes
The possible causes include:
l The user account is set to Invalid.
l The system automatically sets this user account to Invalid because the user account has
not been used for login for three months.
Handling Suggestions
Contact the M2000 administrator to set the status of the user account to Valid.
Symptoms
The login to the M2000 client fails. The system prompts Invalid login duration.
Possible Causes
The current time is not in the time range of permitting the user account to perform operation.
Handling Suggestions
Contact the M2000 administrator to change the operating time range for this user account.
Symptoms
The login to the M2000 client fails. The system prompts Invalid password.
Possible Causes
The password is incorrect.
Handling Suggestions
Relog in to the M2000 client with the correct user name and the password.
Symptoms
The login to the M2000 client fails. The system prompts Password expired. Please
change your password!.
Possible Causes
The login password of the user account has expired.
Handling Suggestions
Contact the M2000 administrator to reset the password for this user account.
Symptoms
The login to the M2000 client fails. The system prompts Maintenance mode.
Possible Causes
The M2000 system is running in the maintenance mode.
Handling Suggestions
Contact the M2000 administrator to reset the running mode of the M2000 system.
Symptoms
The login to the M2000 client fails. The system prompts The user has reached the
maximum login attempts. The user account has been locked, and it
can be unlocked in 1 minute.
Possible Causes
The password used for the current user account to log in to the system is incorrect, and the
number of attempts to log in has reached the set threshold.
Handling Suggestions
Contact the M2000 administrator to unlock the user account, or wait until the system unlocks
the user account.
Symptoms
The login to the M2000 client fails. The system prompts The server doesn't exist
or service is not running.
Possible Causes
The possible causes include:
Handling Suggestions
1. Use correct server IP address.
2. Check the connection between the client and the server.
Ensure that the client can ping to the server.
For details, refer to the related software installation user guide.
3. Contact the M2000 administrator to check the operational status of the server.
Symptoms
The login to the M2000 client fails. The M2000 prompts Exceed maximum sessions.
Possible Causes
The number of users logging in to the M2000 system reaches the limit.
Handling Suggestions
Wait until a user exits the system.
Symptoms
The login to the M2000 client fails. The M2000 prompts Loading module failed,
system will exit.
Possible Causes
The time on the client is inconsistent with that on the server.
Handling Suggestions
Maintain time consistency between the client and the server.
17.1.11 Prompt "Failed to Log in to the Server after the Auto Client
Upgrade or Running Exception"
This part analyzes the abnormal running of the client after automatic upgrade and gives the
solution.
Symptoms
When you log in to the server from the client, the system prompts for an upgrade. After the
upgrade, you cannot log in to the server, or function exceptions occur after you log in to the
server.
Possible Causes
l The server version and the client version are inconsistent.
During the upgrade, the client version is higher than the server version.
l The client and server versions do not belong to the same version series.
The client upgrade will be smooth if: The client version and the server version belong to
the same version series, for example, C02B022. The server version is higher than the client
version, for example, the server version is C02B022SP01 and the client version is C02B022.
Handling Suggestions
Uninstall the existing client, and install the client with the correct version.
Symptoms
The M2000 client interface closes automatically.
Possible Causes
l You are forced to exit the M2000 client.
The user with the operation privileges, such as the M2000 administrator, can force you to
exit the M2000 client. The M2000 client prompts a message before your exit.
l You change the time of the current M2000 client.
In this case, the M2000 client does not prompt any message before your exit.
l The M2000 conflicts with a third-party program.
In this case, the M2000 client does not prompt any message before your exit.
Handling Suggestions
1. Contact the M2000 administrator for the operation privilege.
2. Do not change the time of the current M2000 client during the M2000 operation. Exit the
M2000 client before you change the time.
3. Close the third-party program that possibly conflicts with the M2000.
Symptoms
The M2000 client fails to start.
Possible Causes
The possible causes include:
l The computer is short of memory.
The M2000 client operation requires a memory of 256 MB. When the system runs short of
memory, the M2000 client prompts out of memory.
l Errors occur when you install the M2000 client.
Handling Suggestions
1. Avoid starting several M2000 clients on the same terminal.
2. Quit other programs irrelevant to the M2000 client on the terminal.
3. Uninstall the existing M2000 client, and install a new one.
Symptoms
Characters displayed on the M2000 client are abnormal.
Possible Causes
The configuration file is incorrect.
Handling Suggestions
1. Uninstall the existing M2000 client applications.
2. Install new applications.
Symptoms
The client cannot receive the event alarms and broadcast messages from the server. On the client,
the bulb at the lower right corner of the GUI is on and off intermittently. See Figure 17-1.
Figure 17-1 The connection fails between the client and the server
Possible Causes
A CORBA event is called in a different way from a common CORBA request. For a common
request, the client initiates a connection and sends the request to the server. The server responds
to the client using the same connection; however, for a CORBA event, when the client initiates
a subscription request, the server sets up a new connection with the client and sends the event
to the client using this new connection. Therefore, such a fault results from the failure in setting
up a connection from the server to the client. The possible causes are as follows:
l You are using dual IP addresses of the client.
The client monitors either of the IP addresses. Therefore, sometimes the client connects to
the server normally, sometimes does not.
l You are using a firewall.
Handling Suggestions
l If you set dual client IP addresses, change the settings on the client as follows.
Open default.xml in \lib\openorb\config, and then find the following information.
<!-- properties controlling the incomming server side. -->
<property name="listenAddress" value="0.0.0.0">
<description>
Address to listen on on multi-homed host. Defaults to 0.0.0.0,
all local addresses.
</description>
</property>
<property name="port" value="53100">
<description>
Port for the iiop transport to listen on. Defaults to 0, any
available port.<p/>
Command line alias Port is available.
</description>
</property>
Change the value of listenAddress to a client IP address that you can ping successfully
from the server. In addition, you can use this IP address to connect to the port 53100 by
Telnet.
l If you use a firewall, change the settings as follows.
On the firewall, open port 53100 from the server to the client IP address. The IP address
and the port must be consistent with those set in the configuration file on the client.
Symptoms
The connection between the client and the server is normal. The topology view, however, cannot
be refreshed in real time.
Possible Causes
Multiple IP addresses are configured for the PC serving as the client.
Handling Suggestions
In this case, specify the IP address for communications before logging in to the M2000 server.
For details, refer to the related software installation user guide.
Symptoms
The system fails to discover NodeBs automatically.
Possible Causes
The names of the NodeBs are invalid. The NodeB name must not contain the following
characters: ~ ! @ # $ % ^ & * ( ) + - = { } [ ] \ \ | ; ' : \ " <
> . ? /. Also the name must not end with a space.
Handling Suggestions
Execute the corresponding commands on the RNC to reset the names of the NodeBs.
Symptoms
When you create a topology object, the system prompts The attribute value name
already exists., but you cannot see the topology object with this name on the topology
view.
Possible Causes
The possible causes include:
l The current topology is not refreshed in real time.
l You do not have the privilege to create objects with the same name.
Handling Suggestions
Change the object name and recreate the topology object.
Symptoms
After you enable the alarm messages real-time print function, the printer cannot print the reported
alarm messages displayed in the browse window.
Possible Causes
The printer prints the alarm messages when the records fill one whole page or five minutes after
the printer receives the alarms.
Handling Suggestions
This is normal. No operation is necessary.
Symptoms
l The alarm SMS received on the mobile phone notifies the alarm generated 10 minutes ago.
l Both an e-mail address and a phone number are set in the Remote notify tab of the Fault
Service Settings dialog box. But only an e-mail is received when an alarm occurs.
Possible Causes
l Failure to receive alarm SMSs in real time: It takes about six seconds for an SMS to reach
the receiver. Therefore, the M2000 can send a maximum of 10 SMSs in one minute. The
delay occurs when too many alarms are generated.
l Failure to receive alarm Emails in real-time: The phone number is incorrect. The phone
number must begin with the country code, for example, 861361234xxx1, where 86 is the
country code of the People's Republic of China (PRC). In some countries or districts,
however, the phone number must not begin with the country code, for example, the Unite
Arab Emirates (UAE).
Handling Suggestions
l Failure to receive alarm SMSs in real-time: In the Remote Notify tab of Fault Service
Settings, select fewer types of alarms to send by SMS. Ensure that only alarms with the
highest priority are sent to the mobile phone through the SMS.
l Failure to receive alarm Emails in real-time: Enter the correct phone number in Remote
notify detail settings.
– You can press Ctrl and select the desired check boxes. The color of the selected check
boxes is deeper, as shown in Figure 17-2. Press the space key, and then the deep colored
check boxes are selected, as shown in Figure 17-3. To deselect the deep colored check
boxes, press the space key again.
– You can also select the check boxes by ticking off the . Then the check boxes change
to . Select the check boxes, as shown in Figure 17-4.
l If the check boxes are not arranged sequentially, as shown in Figure 17-5, then:
You can press Shift, and click the first desired check box and then the last one. Then the
color of all the desired check boxes is deeper, as shown in Figure 17-5. Press the space
key, and then the deep colored check boxes are selected, as shown in Figure 17-6. To
deselect the deep colored check boxes, press the space key again.
18.1 Terms
M2000 glossary.
18.2 Abbreviations
This describes the M2000 abbreviations.
18.1 Terms
M2000 glossary.
FDN
Unique identification of an NE in the topology. For example, 0.4.1.
Numeric Type
At present, four types of data are available, which includes:
l Data: NE configuration and log files.
l License: NE license.
l Software: NE version or patch files.
l Other: Other types of data.
Current Time
Time displayed on the server.
MO
Configuration or resource object managed.
Resource Type
Type of an resource object
LMT
Local Maintenance Terminal is a logical concept. LMT is connected to the external network of
the RNC and provides the user interface for RNC operation and maintenance. In RNC operation
and maintenance subsystem, LMT is the terminal for operating and maintaining the RNC.
18.2 Abbreviations
This describes the M2000 abbreviations.
AL Audit Logger
CM Configure Manager
EM Event Manager
FM Fault Manager
ID Identity
IP Internet Protocol
MA Multi-service Access
MB MegaByte
PM Performance Manager
RM Resource Manager
SM Security Manager
TM Topology Manager
Index
AG, 8-50
H ASN-GW, 8-69
BSC, 8-58
hiding GGSN, 8-38
navigation tree of topology view, 3-51 MSC Server, 8-43
hierarchical, 3-54 RNC, 8-26
history command SGSN, 8-32
clearing, 9-12 local network, 11-3
local network domain, 11-3
I creating, 11-12
deleting, 11-15
importing managing user, 11-12
measurement object data, 6-34 local network resource
PCU configuration file, 9-20 managing, 11-12
plan upgrade task, 8-21 locating alarm, 2-13
scheduled upgrade, 8-21 locking client
type 3 object, 6-12 automatically, 1-18
instance manually, 1-18
area-based privilege configuration, 11-16 log
interface template, 5-2
follow-up message browser, 9-72 type, 5-2
follow-up report browser, 9-72 log query result
log management, 5-23 printing, 5-14
M2000 client interface, 1-29 saving, 5-13
MML command, 9-71 log template
monitoring panel, 2-161 creating, 5-19
performance management common option, 1-36 deleting, 5-21
physical topology, 3-59 modifying condition, 5-20
software browser, 8-94 logging
topology management, 3-59 LMT client, 11-16
inventory data logging in, 1-3
manually exporting, 9-25 logging in to M2000 server
IP device automatically upgrading client software, 1-8
creating, 3-7 logging out, 1-6
L M
level redefinition maintenance experience
adding, 2-49 exporting, 2-35
deleting, 2-50 importing, 2-36
modifying, 2-49 Man Machine Language, 9-3
license information Management Information Tree, 9-3
viewing, 1-22 managing
link exported file, 1-24
deleting virtual link, 3-49 local network resource, 11-12
LMT result query template directory, 6-32
setting prompt, 1-21 user in local network domain, 11-12
starting, 9-29 manually exporting
LMT client inventory data, 9-25
logging, 11-16 NE configuration data, 9-19
loading manually reconnecting NE, 3-34
NE software matrix layout, 3-54
AG, 8-48 measurement counter
ASN-GW, 8-67 querying, 6-34
GGSN, 8-37 measurement object
RNC, 8-24 exporting, 6-35
SGSN, 8-30 importing data, 6-34
NE software patch modifying memo, 6-37
saving
Q alarm data, 2-26
alarm query result, 2-26
querying alarm statistic result, 2-26
alarm details, 2-33 audit result of dual-homing data, 11-7
authorization, 4-38 log query result, 5-13
current alarms, 2-15, 2-31 monitoring chart, 2-103
event alarms, 2-18 monitoring table, 2-103
historical measurement result integrity, 6-17 scanning
history fault alarms, 2-17 correlated monitoring counter value, 2-102
masked event alarms, 2-20 scheduled upgrade
masked fault alarms, 2-19 activation template, 8-22
measurement counter, 6-34 browsing, 8-20
measurement result reliability, 6-14 download template, 8-22
monitoring object, 2-117 exporting, 8-21
NE configuration information, 9-14 file format, 8-22
NE link information, 9-15 importing, 8-21
NE report, 9-16 searching
operation log, 5-8 monitoring object, 2-117
security log, 5-10 searching topology objects, 3-35
system log, 5-9 server backup
querying measurement result modifying, 14-51
by new condition, 6-20 set
by template, 6-19 alarm sound
, 1-20
R disconnect, 1-20
setting
radial tree layout, 3-54 Alarm box, 2-42
re-querying result, 6-21 alarm color, 2-43
real-time performance monitoring, 16-4 alarm highlight, 2-43
recording, alarm handling experience, 2-35 alarm interface column, 2-11
refreshing topology view, 3-50 alarm sound, 2-42
relation, threshold and alarms, 2-138 chart background color, 6-29
remote notification consistency check window, 11-6
rule, 2-44 data check interface, 11-6
removing default subnet view, 3-57
alarm-related fault, 2-33 display effect of topology icons, 1-12
NE software patch file transferring parameter, 8-15
AG, 8-53 filtering result counter condition, 6-25
ASN-GW, 8-71 LMT prompt, 1-21
BSC, 8-60 monitoring chart attribute, 2-98
GGSN, 8-41 monitoring chart background color, 2-100
MSC Server, 8-45 monitoring chart background picture, 2-99
RNC, 8-28 monitoring chart curve color, 2-100
SGSN, 8-35 monitoring chart property, 2-98
reporting NE log procedure, 5-3 monitoring chart threshold, 2-99
result query template monitoring table filtering condition, 2-97
adding, 6-30 monitoring table threshold, 2-97
managing directory, 6-32 monitoring threshold filtering rule, 2-94
modifying, 6-31 monitoring threshold rule, 2-94
resuming NE reconnection, 3-33
timing task, 14-56 NE transfer server, 3-11
rollbacking output information, 1-11
NE software patch performance management common option, 1-17
BSC, 8-61 real-time monitoring threshold, 2-93
remote notification
S parameter, 2-45
running mode of system
zoom in
V monitoring chart, 2-98
zoom out
version, 8-2 monitoring chart, 2-98
viewing
basic attribute
NE, 3-45
subnet, 3-44
basic cell configuration, 2-125
basic NodeB configuration, 2-124
cell alarm, 2-129
cell distribution on RNC, 2-122
cell monitoring counter, 2-128
configuration status, 2-118
detail information of configuration status, 2-118
detailed alarm information, 2-118
electronic map, 3-57
exported file, 1-24
follow-up report, 9-10
function key, 1-22
information on specified link of Iub interface,
2-124
MML command result, 9-9
monitoring counter chart, 2-119
monitoring panel, 2-117
monitoring service, 2-112
NE file information, 8-9
NE link report, 9-15
NE measurement state, 6-18
NE MIT information, 9-14
NE report, 9-16
NE statistic report, 9-16
NE version, 9-16
NM license information, 1-22
NodeB distribution on RNC, 2-122
physical link, 3-46
resource key, 1-22
RNC Iu interface, 2-122
RNC Iub interface, 2-123
RNC Iur interface, 2-122
RNC monitoring counter, 2-127
server file information, 8-9
specified link of Iu interface, 2-123
specified link of Iur interface, 2-123
template condition, 6-31
virtual link, 3-47
viewing topology overview, 3-54
virtual link
creating, 3-9
modifying, 3-47
viewing, 3-47
W
WRAN configured object model, 2-105