Professional Documents
Culture Documents
Operator Guide
Contents
Contents
1 About This Guide ......................................................................................................................1-1
1.1 Purpose..........................................................................................................................................................1-2
1.2 Intended Users...............................................................................................................................................1-2
1.3 Organization..................................................................................................................................................1-2
1.4 Reference ......................................................................................................................................................1-3
3 NE Connection............................................................................................................................3-1
3.1 Connecting NEs to the M2000 ......................................................................................................................3-2
3.2 Monitoring Connection Status of NEs ..........................................................................................................3-2
3.2.1 Introduction to Connection Status of NEs............................................................................................3-2
3.2.2 Monitoring NE Status in the Topology View .......................................................................................3-3
3.2.3 Monitoring NE Status through the System Monitor Browser ..............................................................3-3
Issue 02 (2006-10-31)
M2000
Operator Guide
ii
Issue 02 (2006-10-31)
M2000
Operator Guide
Contents
Issue 02 (2006-10-31)
iii
M2000
Operator Guide
iv
Issue 02 (2006-10-31)
M2000
Operator Guide
Contents
7 Configuration Management.....................................................................................................7-1
7.1 Querying NE Configuration ..........................................................................................................................7-2
7.1.1 Configuration Types.............................................................................................................................7-2
7.1.2 Querying NE Configuration.................................................................................................................7-2
7.1.3 Querying the Basic NE Configuration .................................................................................................7-3
7.2 Synchronizing NE Configuration..................................................................................................................7-4
7.2.1 Synchronizing NE Configuration Manually ........................................................................................7-4
7.2.2 Synchronizing NE Configuration Automatically .................................................................................7-5
7.2.3 Synchronizing NE Configuration Periodically ....................................................................................7-6
7.3 Exporting NE Configuration .........................................................................................................................7-6
7.3.1 Exporting NE Configuration Manually................................................................................................7-6
7.3.2 Exporting NE Confiugration Periodically............................................................................................7-7
7.4 Saving NE Configuration to a File ................................................................................................................7-8
7.5 Setting NE Type Privilege Rules...................................................................................................................7-9
7.6 Applying NE Type Privilege Rules .............................................................................................................7-10
7.7 Managing NE Users .................................................................................................................................... 7-11
7.7.1 Overview of NE Users ....................................................................................................................... 7-11
7.7.2 Principles for NE User Authorization ................................................................................................ 7-11
7.7.3 Creating NE Users ............................................................................................................................. 7-11
7.7.4 Modifying Privileges for NE Users....................................................................................................7-12
7.7.5 Deleting NE User Accounts ...............................................................................................................7-14
7.8 Monitoring Operations of M2000 Users and NE Users ..............................................................................7-15
7.8.1 Overview of User Logs and NE Logs ................................................................................................7-15
7.8.2 Synchronizing NE Logs .....................................................................................................................7-15
7.8.3 Querying NE Logs .............................................................................................................................7-17
7.8.4 Monitoring NE User Login on LMTs ................................................................................................7-18
7.8.5 Monitoring Operations and Sessions of NE Users.............................................................................7-19
7.9 Management of Enhanced Maintenance for NEs ........................................................................................7-19
7.9.1 Overview............................................................................................................................................7-19
7.9.2 Upgrading Enhanced Maintenance for NEs.......................................................................................7-20
Issue 02 (2006-10-31)
M2000
Operator Guide
9 Backup Managemnet.................................................................................................................9-1
vi
Issue 02 (2006-10-31)
M2000
Operator Guide
Contents
10 Troubleshooting .....................................................................................................................10-1
10.1 Client Login Failures.................................................................................................................................10-2
10.1.1 Prompt "Login failed. Confirm that your user name and password are case sensitive and correct."
....................................................................................................................................................................10-2
10.1.2 Prompt "Invalid user account." ........................................................................................................10-2
10.1.3 Prompt "Invalid login duration."......................................................................................................10-2
10.1.4 Prompt Message "Invalid password." ..............................................................................................10-3
10.1.5 Prompt Message "The password has expired. Please change your password! " ..............................10-3
10.1.6 Prompt Message "Maintenance Mode."...........................................................................................10-3
10.1.7 Prompt Message "The User Has Reached the Maximum Login Attempts. The User Account Has
Been Locked, and It Can Be Unlocked in 1 Minute.".................................................................................10-4
10.1.8 Prompt Message "The Server Doesnt Exist or Service Is Not Running.".......................................10-4
10.1.9 Prompt Message "Exceed Maximum Sessions." ing........................................................................10-5
10.1.10 Prompt Message "Loading Module Failed, System Will Exit." .....................................................10-5
10.1.11 Prompt Message "Failed to Log in to the Server after the Auto Client Upgrade or Running
Exception"...................................................................................................................................................10-5
10.2 Client Running Faults................................................................................................................................10-6
10.2.1 Abortion of the M2000 Client..........................................................................................................10-6
10.2.2 Failure to Run the M2000 Client .....................................................................................................10-6
10.2.3 Abnormal Display of M2000 Client Interface..................................................................................10-7
10.2.4 The Bulb on the GUI Is On and Off Intermittently ..........................................................................10-7
10.3 Topology Management Faults ...................................................................................................................10-8
10.3.1 Failure to Refresh the Topology View..............................................................................................10-8
10.3.2 Failure to Discover NodeBs Automatically .....................................................................................10-9
10.3.3 Conflicted Names for the Created Topology Objects.......................................................................10-9
10.4 Alarm Management Faults ........................................................................................................................10-9
10.4.1 Time Delay of Alarm Message Real-Time Printing .........................................................................10-9
10.4.2 Failure to Receive Alarm Emails in Real-Time .............................................................................10-10
10.4.3 Failure to Receive Alarm SMSs in Real-Time ...............................................................................10-10
10.4.4 Unknown NE Names During the Alarm Query .............................................................................10-10
Issue 02 (2006-10-31)
vii
M2000
Operator Guide
Figures
Figure 2-1 M2000 client interface (Physical Topology window) ......................................................................2-3
Figure 2-2 Output Window tab in the System Setting dialog box ..................................................................2-4
Figure 2-3 Terminal tab in the System Setting dialog box ...............................................................................2-5
Figure 2-4 Customize Toolbar dialog box ........................................................................................................2-6
Figure 3-1 Monitoring the NE statuses through the system monitor browser ....................................................3-4
Figure 4-1 An example of CSV templates..........................................................................................................4-5
Figure 4-2 Create NE dialog box ......................................................................................................................4-7
Figure 4-3 Progress of creating physical NEs ....................................................................................................4-8
Figure 4-4 Creating physical NEs in batches ................................................................................................... 4-11
Figure 4-5 Creating physical subnets ...............................................................................................................4-15
Figure 4-6 NE Property dialog box.................................................................................................................4-18
Figure 4-7 Modify Physical Subnet dialog box..............................................................................................4-20
Figure 5-1 Process by which a fault alarm changes to a history fault alarm ......................................................5-5
Figure 5-2 Procedure for processing M2000 alarms ..........................................................................................5-6
Figure 5-3 Querying current fault alarms ...........................................................................................................5-8
Figure 5-4 Browsing alarms ............................................................................................................................. 5-11
Figure 5-5 Alarm details...................................................................................................................................5-13
Figure 5-6 Selecting the columns to be displayed in the alarm list ..................................................................5-15
Figure 5-7 Alarm statistics table.......................................................................................................................5-16
Figure 5-8 Alarm statistics pie chart.................................................................................................................5-17
Figure 5-9 Setting conditions for auto acknowledgement ................................................................................5-19
Figure 5-10 Auto displacement ........................................................................................................................5-22
Figure 5-11 Manual displacement ....................................................................................................................5-23
Figure 5-12 Redefining the alarm severity (level)............................................................................................5-26
Figure 5-13 Setting correlation for intermittent fault alarms............................................................................5-28
Figure 5-14 Modifying the alarm knowledge...................................................................................................5-31
viii
Issue 02 (2006-10-31)
M2000
Operator Guide
Figures
Issue 02 (2006-10-31)
ix
M2000
Operator Guide
Issue 02 (2006-10-31)
M2000
Operator Guide
Tables
Tables
Table 3-1 Icons indicating NE connection status................................................................................................3-2
Table 4-1 Descriptions of two link types ............................................................................................................4-4
Table 6-1 Exporting the monitoring data ..........................................................................................................6-44
Table 8-1 File servers available for the NEs.......................................................................................................8-4
Table 9-1 NE backup data...................................................................................................................................9-2
Issue 02 (2006-10-31)
xi
M2000
Operator Guide
Description
1.1 Purpose
1.3 Organization
1.4 Reference
Issue 02 (2006-10-31)
1-1
M2000
Operator Guide
1.1 Purpose
This guide describes how to operate and maintain the network equipment. It includes the
following content:
!
Network engineers
Shift operators
1.3 Organization
This guide consists of the following chapters:
1-2
1 "About This Guide" introduces the purpose, intended users, and organization of this
guide.
2 "Introduction to M2000" describes the procedures for logging in to the M2000 client
and setting the client.
3 "NE Connection" describes the types of NEs the M2000 system manages, relevant
operation tasks, and the procedures for connecting types of network equipment.
8 "NE Software and License Management" describes the operation tasks and procedures
related to NE software and license management.
9 "Backup Managemnet" describes the operation tasks and procedures related to server
data backup and NE data backup.
10 "Troubleshooting" describes the handling suggestions for common faults that may
occur during operations on the client.
Issue 02 (2006-10-31)
M2000
Operator Guide
1.4 Reference
When you read this guide, see M2000 Online Help for more information.
Issue 02 (2006-10-31)
1-3
M2000
Operator Guide
2 Introduction to M2000
Introduction to M2000
Description
Issue 02 (2006-10-31)
2-1
M2000
Operator Guide
2 Introduction to M2000
The M2000 server runs on the Unix platform. The server processes and stores NE data.
The M2000 clients run on the Windows platform. The clients provide friendly graphical
interfaces for operations and maintenance on the NEs.
Prerequisites
Before logging in to the M2000 client, ensure that:
!
The software versions of the M2000 client and the M2000 server match.
Procedure
To log in to the M2000 client, perform the following steps:
Step 1 Choose Start > Programs > iManager M2000 Client > M2000 Client to start the M2000
client.
You can configure the path for the menu iManager M2000 Client > M2000 Client in Start >
Programs when you install the client software. The default path is iManager M2000 Client.
Step 2 In the displayed User Login dialog box, enter the server IP address to log in to the M2000
client.
2-2
Issue 02 (2006-10-31)
M2000
Operator Guide
2 Introduction to M2000
If User Login does not list the information about the specified server, click
Information dialog box is displayed.
. The Server
In this dialog box, set the server information, such as the server IP and sever port.
----End
Auto displacement
Issue 02 (2006-10-31)
2-3
M2000
Operator Guide
2 Introduction to M2000
Prerequisites
Before setting the properties of the system, ensure that you have logged in to the M2000
client.
Procedure
To set the properties of the M2000 client, perform the following steps:
Step 1 Choose System > System Setting.
The System Setting dialog box is displayed, as shown in Figure 2-2.
Figure 2-2 Output Window tab in the System Setting dialog box
Step 2 In the Output Window tab, set parameters such as Maximum Output Lines.
Step 3 Click the Terminal tab in the System Setting dialog box, as shown in Figure 2-3.
2-4
Issue 02 (2006-10-31)
M2000
Operator Guide
2 Introduction to M2000
Step 4 Set the period for Automatically locked or turn off the option.
Step 5 Click OK.
----End
Prerequisites
Before customizing the toolbar, ensure that you have logged in to the M2000 client.
Procedure
To customize the toolbar, perform the following steps:
Issue 02 (2006-10-31)
2-5
M2000
Operator Guide
2 Introduction to M2000
2-6
Issue 02 (2006-10-31)
M2000
Operator Guide
3 NE Connection
NE Connection
Description
Issue 02 (2006-10-31)
3-1
M2000
Operator Guide
3 NE Connection
Debug the NEs and ensure that they work well before you connect them to the M2000 system.
Meaning
Description
Synchronization
processing
Connection
down
NE not match
The O&M path between the NE and the M2000 works well.
You cannot, however, operate or maintain the NE through the
M2000 because the NE is not installed with the right version of
the mediation package.
3-2
Forbid Connect
Unknown type
FourStates
Issue 02 (2006-10-31)
M2000
Operator Guide
3 NE Connection
Prerequisites
Before monitoring the status of an NE, ensure that you have logged in to the M2000 client.
Procedure
To monitor the status of an NE in the topology view, perform the following steps:
Step 1 Click the Tree tab on the left of the topology view.
Step 2 Select the subnet with the NE.
Step 3 Select the NE.
The NE status is shown in the topology view on the right of the topology view. Here are two
examples,
----End
Prerequisites
Before monitoring NE status through the system monitor browser, ensure that you have
logged in to the M2000 client.
Issue 02 (2006-10-31)
3-3
M2000
Operator Guide
3 NE Connection
Procedure
To monitor NE status through the system monitor browser, perform the following steps:
Step 1 Choose Tools > System Monitor > Monitor Browser.
The System Monitor Browser dialog box is displayed.
Step 2 Click the NE Monitor tab.
The status of each NE is displayed, as shown in Figure 3-1.
Figure 3-1 Monitoring the NE statuses through the system monitor browser
3-4
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Topology Management
Description
Describes how to delete the NEs and the group NEs in the
topology view.
Issue 02 (2006-10-31)
4-1
M2000
Operator Guide
4 Topology Management
The navigation tree on the left shows all the involved topology objects, such as NEs,
subnets, and the hierarchical architecture between these objects.
The topology view on the right shows all the topology objects in the current network and
the location-related relationship between these objects.
The system synchronizes the navigation tree and the topology view automatically.
Examples
The displayed window after you log in the M2000 client is a topology view.
Physical NE
Physical NEs are the communication devices that can be managed by the M2000.
Virtual NE
The third-party communication equipment in the entire communication network. The
M2000 cannot manage the equipment. Virtual NEs help complete the structure of the
communication network.
In the topology view, the physical NE and virtual NE are distinguished by different icon
colors. For example, the physical NE HLR is displayed as
the virtual NE HLR is displayed as
The equipment type corresponds to the NE type. The NE types are identified by different icons. You can
view the icons by clicking the Legend tab in the left of the window.
Examples
Some examples of NEs are as follows:
4-2
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
!
Huawei BTS3812A sets up a physical connection with the M2000; thus it is a physical
NE.
The M2000 itself is a special NE. The M2000 is displayed as OMC in the topology view.
4.1.3 Subnets
Meaning
To manage NEs more efficiently, the huge M2000 network can be divided into several smaller
networks based on certain principles, such as by region. These smaller networks are called
subnets in the topology.
Examples
An example of subnets is as follows:
If the M2000 can manage all the NEs in the provinces A, B and C, these NEs can be divided
into three subnets by region (herein province).
The three subnets can also be divided into smaller subnets by city or county. In other words, a
subnet can be nested in another subnet.
Examples
Some examples of group NEs are as follows:
!
4.1.5 Links
Meaning
The topology view uses links to identify the physical or logical connections between the
communication equipment. There are two types of links, physical and virtual, as shown in
Table 4-1.
Issue 02 (2006-10-31)
4-3
M2000
Operator Guide
4 Topology Management
Description
Physical
link
MTP3B
DATALINK
H248
BICCSCTP
M3UA
Virtual
link
Virtual links can only be created manually. You can modify or delete virtual
links.
Examples
Some examples of the links are as follows:
!
The links between physical MGW and virtual MSC Server are physical links created by
the manually.
The links between virtual MSC Server and virtual HLR are virtual links created
manually.
Examples
Some examples of topology objects are as follows:
4-4
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Issue 02 (2006-10-31)
4-5
M2000
Operator Guide
4 Topology Management
Example 2: BSC
[BSC]
Name =
Vendor =
Physical Location =
District =
IP address =
Description =
Username =
Password =
Pos X =
Pos Y =
Position =
Coordination =
For the parameters of the INI templates, see M2000 Online Help.
Prerequisites
Before creating a physical NE, ensure that:
!
You have obtained the NE information, such as the NE name, IP address, NE version,
and district information.
Procedure
To create a physical NE in the topology view, perform the following steps:
Step 1 Right-click in the topology view, and select Create NE on the displayed menu.
The Create NE dialog box is displayed, as shown in Figure 4-2.
4-6
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Step 2 Select the physical NE category in the Select Category drop-down list.
Step 3 Select the NE type in the Select NE Type drop-down list.
Step 4 Click Next.
Step 5 Select the district.
Enter the information such as the NE name and IP address.
Step 6 Click Finish.
The prompt dialog box Create NE displays the progress of the NE creation.
For example, the progress of creating the BSC NE is as shown in Figure 4-3.
Issue 02 (2006-10-31)
4-7
M2000
Operator Guide
4 Topology Management
The icon for this NE is displayed in the topology view while the system displays the
. The progress bar closes automatically after 100% is displayed.
synchronization progress
You can operate and maintain the NE through the M2000 client.
----End
Prerequisites
Before creating a virtual NE, ensure that:
!
You have obtained the information about the NE, such as the NE name, IP address, and
district information.
Procedure
To create a virtual NE in the topology view, perform the following steps:
Step 1 Right-click in the topology view, and select Create NE on the displayed menu.
The Create NE dialog box is displayed, as shown in Figure 4-2.
4-8
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Prerequisites
Before creating an NE batch file in the CSV format, ensure that:
!
You have obtained the information about the NE Type, IP address, NE version and
district.
Procedure
To create an NE batch file in the CSV format, perform the following steps:
Step 1 Choose Configuration > Exports NE Attributes Template > CSV File Format to view
Export NE Info template (CSV file format) dialog box.
Step 2 Click
Step 3 Open the template file, and enter the information of each NE, such as the NE type, NE name,
NE version, and district.
Obtaining the NE type from the drop-down list in the Create NE dialog box is recommended. For
details, see part 4.2.1 "Creating Physical NEs."
Issue 02 (2006-10-31)
4-9
M2000
Operator Guide
4 Topology Management
Prerequisites
You have obtained the NE information such as the NE Type, IP address, NE version and
district.
Procedure
To create an NE batch file in the INI format, perform the following steps:
Step 1 Choose Configuration > Exports NE Attributes Template > INI File Format to view
Export NE Info template (INI file format) dialog box.
Step 2 Select the NE type. Click
Step 3 Open the template file, and enter the information of each NE, such the NE type, NE name, NE
version and district.
Obtaining the NE type from the drop-down list in the Create NE dialog box is recommended. For
details, see part 4.2.1 "Creating Physical NEs."
4-10
This task applies to creating physical NEs in WCDMA networks when the script file is in
the CSV format.
This task applies to creating all NEs except virtual NEs when the script file is in the INI
format.
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Prerequisites
Before creating physical NEs in batches, ensure that:
!
The NE batch script files are created. For details, see part 4.2.3 "Creating NE Batch
Script Files in CSV Format" and part 4.2.4 "Creating NE Batch Script Files in INI
Format"
Procedure
To create multiple physical NEs in batches, perform the following steps:
Step 1 Right-click in the topology view, and select Create Physical NEs in batch on the displayed
menu.
The Create Physical NEs in batch dialog box is displayed, as shown in Figure 4-4.
Figure 4-4 Creating physical NEs in batches
Step 2 Click
Issue 02 (2006-10-31)
4-11
M2000
Operator Guide
4 Topology Management
----End
Prerequisites
Before deleting a physical NE, ensure that:
!
Procedure
To delete a physical NE from the topology view, perform the following steps:
Step 1 Select a physical NE in the topology view.
Step 2 Right-click the NE, and select Delete on the displayed menu.
Step 3 Click Yes in the displayed Confirm dialog box.
The deletion progress is displayed in percentage. When 100% is displayed, the physical links
of the physical NE are deleted automatically.
----End
Prerequisites
Before deleting a virtual NE, ensure that:
!
4-12
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
!
Procedure
To delete a virtual NE from the topology view, perform the following steps:
Step 1 Select the virtual NE in the topology view.
Step 2 Right-click the NE, and select Delete on the displayed menu.
Step 3 Click Yes in the displayed Confirm dialog box to delete the virtual NE.
If the virtual NE contains sub-NEs, the sub-NEs are displayed in the upper physical topology after you
delete the virtual NE.
----End
Prerequisites
Before deleting a group NE from the physical topology, ensure that:
!
Procedure
To delete the group NE, perform the following steps:
Step 1 Select the group NE to be deleted in the topological view.
Step 2 Right-click the group NE, and select Delete on the displayed menu.
Step 3 Click Yes in the Confirm prompt dialog box to delete the group NE from the current view.
If the group NE contains other NEs, it exists as a virtual NE. In this case, the icon becomes a virtual
icon.
----End
Issue 02 (2006-10-31)
4-13
M2000
Operator Guide
4 Topology Management
Prerequisites
Before creating a subnet in the physical topology, ensure that:
!
The topological view and the network architecture are well planned.
Procedure
4-14
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
----End
Prerequisites
Before deleting a subnet, ensure that:
!
Procedure
To delete a subnet from the topology view, perform the following steps:
Step 1 Select the subnet in the topology view.
Issue 02 (2006-10-31)
4-15
M2000
Operator Guide
4 Topology Management
Step 2 Right-click the subnet, and select Delete on the displayed menu.
The Confirm dialog box is displayed.
Step 3 Click Yes in the Confirm prompt dialog box.
NEs and subnets under this subnet, if any, are displayed in the upper physical topology after you delete
this subnet.
----End
Prerequisites
Before creating a physical link in the topology view, ensure that:
!
The topology view and the network architecture are well planned.
Procedure
To create a physical link, perform the following steps:
Step 1 Right-click in the topology view, and select Create Link on the displayed menu.
The Create Link dialog box is displayed.
Step 2 Select the link type in the Create Link dialog box.
Step 3 Click
In the End A MO and End Z MO areas, select the configuration for the two ends of the link.
Click
4-16
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
The prompt dialog box Create Link displays the progress of the link creation. After the
creation, a link is displayed between the two NEs.
----End
Prerequisites
Before creating a virtual link in the topology view, ensure that:
!
The topology view and the network architecture are well planned.
Procedure
To create a virtual link, perform the following steps:
Step 1 Right-click in the topology view, and select Create Virtual Link on the displayed menu.
The Create Virtual Link dialog box is displayed.
Step 2 Enter the name of the virtual link.
Step 3 Select the NEs in the end A and end Z of the link.
Step 4 Click OK.
After the creation, a link is displayed between the two NEs.
----End
Issue 02 (2006-10-31)
4-17
M2000
Operator Guide
4 Topology Management
Prerequisites
Before moving an NE to a group NE, ensure that:
!
Procedure
To move an NE to a group NE, perform the following steps:
Step 1 Select the target group NE in the topology view.
Step 2 Right-click the NE, and select Property on the displayed menu.
The NE Property dialog box is displayed, as shown in Figure 4-6.
Figure 4-6 NE Property dialog box
4-18
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
----End
Prerequisites
Before moving an NE to another subnet, ensure that:
!
Procedure
To move an NE to another subnet, perform the following steps:
Step 1 Select the target subnet in the topology view.
Step 2 Right-click the NE, and select Modify on the displayed menu.
The Modify Physical Subnet dialog box is displayed, as shown in Figure 4-7.
Issue 02 (2006-10-31)
4-19
M2000
Operator Guide
4 Topology Management
This operation changes only the location of the NE in the topology view. The actual geographical
location and physical connections of the NE is not concerned.
4-20
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Prerequisites
Before moving an NE in the same subnet, ensure that:
!
Procedure
To move an NE in the same subnet, perform the following steps:
Step 1 Select the NE in the topology view.
Step 2 Drag it to the required location.
Step 3 Click
in the toolbar in the middle part to save the new location of the NE.
----End
Prerequisites
Before filtering NEs, ensure that you have logged in to the M2000 client.
Procedure
To filter NEs in the topology view, perform the following steps:
Step 1 Click the Filter tab in the left pane of the topology view.
Step 2 Select the objects to be displayed in the navigation tree.
The objects that are not selected are not displayed in the topology view.
----End
Issue 02 (2006-10-31)
4-21
M2000
Operator Guide
4 Topology Management
You can customize the counter items as prompt information as required. The counter items are
classified into three types by NE, Link and District.
Prerequisites
Before customizing topology tips, ensure that you have logged in to the M2000 client.
Procedure
To customize topology tips, perform the following steps:
Step 1 Choose Tools > Customize Topology Tips.
The Customize Topology Tips dialog box is displayed.
The system displays the counter item (activated or to be set) of the first NE in the navigation
tree by default.
Step 2 Select a counter in the navigation tree.
Step 3 Set the counter item in the right of the dialog box.
Step 4 Click OK or Apply.
----End
You can only switch the background maps of the topology views.
The background of the topology view is Empty map by default. In other words, the topology view
has no background maps.
The file format that can serve as the background map of the topology view in the M2000
includes: GIF, IVL, JPEG, JPG, MIF, and SHP.
Prerequisites
Before setting the background map of the topology view, ensure that:
4-22
Issue 02 (2006-10-31)
M2000
Operator Guide
4 Topology Management
Procedure
To switch electronic maps in the M2000 client, perform the following steps:
Step 1 Right-click in the topology view, and select Set BackGround on the displayed menu.
The Set BackGround dialog box is displayed.
Step 2 Click Select, and select the electronic map file.
Step 3 Click OK.
After that, the electronic map selected becomes the background of the topology view.
----End
Issue 02 (2006-10-31)
4-23
M2000
Operator Guide
5 Alarm Management
Alarm Management
Description
Issue 02 (2006-10-31)
5-1
M2000
Operator Guide
5 Alarm Management
5-2
Title
Description
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
By alarm handling and clearance: history fault alarms and shielded alarms
Fault alarms, such as a board fault alarm, are generated when faults occur to hardware
devices or exceptions occur to key functions. Fault alarms are more severe than event
alarms. Fault alarms can be cleared.
Event alarms, such as a congestion alarm, are occasionally generated during the
equipment operation. The event alarms indicate only the equipment status at a certain
point of time. The system generates some event alarms periodically. Event alarms do not
need manual handling.
History fault alarms refer to the cleared and acknowledged fault alarms.
Shielded alarms are generated during a short period of time. The alarms matching the
correlation rules set on the M2000 client are shielded alarms, and they are stored in the
M2000 shielding library. Shielded alarms can only be fault or event alarms.
Critical alarms, such as the power circuit fault alarm or the output clock fault alarm,
affect the whole system operation. Critical alarms require immediate handling.
Major alarms, such as alarms about disconnected fibers or physical line faults, occur
only to boards or lines. If not handled timely, these alarms may affect the services.
Minor alarms, such as the alarm for bit errors in some physical lines, refer to common
status alarms that indicate the working status of boards or lines.
Warning alarms indicate status changes or events which do not affect the system
performance or subscriber services, but may interest the operator. Some warning alarms
prompt when the equipment returns to normality.
Issue 02 (2006-10-31)
5-3
M2000
Operator Guide
5 Alarm Management
!
For an acknowledged and cleared alarm, the M2000 moves the alarm from the current fault
alarm library to the history fault alarm library. Accordingly, the alarm changes to a history
fault alarm.
For an unacknowledged or uncleared alarm, the alarm remains in the current fault alarm
library as a current fault alarm.
Figure 5-1 shows how a current fault alarm changes to a history fault alarm.
5-4
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Figure 5-1 Process by which a fault alarm changes to a history fault alarm
Event Alarms
Event alarms can be in two statuses: acknowledged and unacknowledged. They do not change
to other alarms.
Issue 02 (2006-10-31)
5-5
M2000
Operator Guide
5 Alarm Management
After receiving alarms from an NE or the M2000 itself, the M2000 shields the alarms,
redefines the alarm severity levels, or correlates the alarms before saving the alarms in the
alarm library.
You can query the alarm information and acknowledge the alarms on the M2000 client.
5-6
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Step 3 The M2000 checks if the alarm matches the correlation rules set on the M2000. If the alarm
matches the correlation rules, the M2000 drops it into the shielded alarm library or discard it.
Step 4 The M2000 saves alarms other than shielded or discarded alarms to the fault or event alarm
library based on the alarm content.
----End
Event alarms
Shielded alarms
The change of the NE status may lead to a change in the alarm category. For details, see part
5.2.3 "Relationship Between Alarm Categories and Alarm Statuses."
Prerequisites
Before querying and browsing current fault alarms, ensure that you have logged in to the
M2000 client.
Issue 02 (2006-10-31)
5-7
M2000
Operator Guide
5 Alarm Management
Procedure
To query current fault alarms, perform the following steps:
Step 1 Choose Fault > Query > Current Fault Alarm. The Alarm Browse, Query and Statistics
dialog box is displayed, as shown in Figure 5-3.
Figure 5-3 Querying current fault alarms
Step 2 Click Current Fault Alarm Query n tab. Two methods are available for querying the current
alarms. The number n is represented by 1, 2, 3, and so on, indicating that you can perform
multiple queries.
!
Method 1: Set the query conditions in the upper half of the Current Fault Alarm Query
1 window, and then click Query.
For example, select an NE to query the fault alarms related to the NE. Select an alarm
severity (level) to query the fault alarms of this severity (level). Set a start time to query
the fault alarms generated after this time point.
By default, the system displays all the fault alarms stored in the current M2000 alarm
library.
Method 2: Select Template in the navigation tree on the left, and then double-click a
template.
This template contains query conditions.
----End
5-8
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before querying event alarms, ensure that you have logged in to the M2000 client.
Procedure
To query event alarms, perform the following steps:
Step 1 Choose Fault > Query > Event Alarm.
The Alarm Browse, Query and Statistics dialog box is displayed.
Step 2 Click Event Fault Alarm Query tab. Two methods are available for querying the event
alarms. For details, see part 5.4.1 "Querying Current Fault Alarms."
----End
Prerequisites
Before querying history fault alarms, ensure that you have logged in to the M2000 client.
Procedure
To query history fault alarms, perform the following steps:
Step 1 Choose Fault > Query > History Fault Alarm.
The Alarm Browse, Query and Statistics dialog box is displayed.
Step 2 Click the History Fault Alarm Query tab. Two methods are available for querying the
history fault alarms. For details, see part 5.4.1 "Querying Current Fault Alarms."
Issue 02 (2006-10-31)
5-9
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before querying shielded alarms, ensure that you have logged in to the M2000 client.
Procedure
To query shielded alarms, perform the following steps:
Step 1 Choose Fault > Query > Shielded Alarm.
The Alarm Browse, Query and Statistics dialog box is displayed.
Step 2 Click the Shielded Alarm Query tab. Two methods are available for querying the shielded
alarms. For details, see part 5.4.1 "Querying Current Fault Alarms."
----End
Prerequisites
Before browsing real-time fault alarms, ensure that you have logged in to the M2000 client.
Procedure
To browse real-time fault alarms, perform the following steps:
Step 1 Choose Fault > Current Fault Alarm Browser.
The Alarm Browse, Query and Statistics dialog box is displayed.
Step 2 Click the Current Fault Alarm Browse tab. Two methods are available for browsing
real-time fault alarms, as shown in Figure 5-4.
5-10
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Step 3 Click Current Fault Alarm Browse tab. Two methods are available for browsing the current
alarms.
!
Method 1: Set the query conditions in the upper half of the Current Fault Alarm Query
1 window, and then click Query.
For example, select an NE to query the fault alarms related to the NE. Select an alarm
severity (level) to query the fault alarms of this severity (level). Set a start time to query
the fault alarms generated after this time point.
By default, the system displays all the fault alarms stored in the current M2000 alarm
library.
Method 2: Select Template in the navigation tree on the left, and then double-click a
template.
This template contains query conditions.
----End
Issue 02 (2006-10-31)
5-11
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before browsing real-time event alarms, ensure that you have logged in to the M2000 client.
Procedure
To browse real-time event alarms, perform the following steps:
Step 1 Choose Fault > Event Alarm Browser.
The Alarm Browse, Query and Statistics dialog box is displayed.
Step 2 Click the Event Alarm Browse tab. Two methods are available for browsing real-time event
alarms. For details, see part 5.4.5 Browsing Real-Time Fault Alarms."
----End
Prerequisites
Before querying the explanation of an alarm, ensure that:
!
The Alarm Browse, Query and Statistics dialog box is displayed with a list of alarms.
Procedure
To query the explanation of an alarm, perform the following steps:
Step 1 In Alarm Browse, Query and Statistics, select an alarm to query the alarm details.
Step 2 Double-click the alarm.
The Alarm Details dialog box is displayed, as shown in Figure 5-5.
5-12
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before querying alarms correlated to an alarm, ensure that:
!
The Alarm Browse, Query and Statistics dialog box is displayed with a list of alarms.
Procedure
To query alarms correlated to an alarm, perform the following steps:
Step 1 In Alarm Browse, Query and Statistics, select an alarm to query the alarm details.
Issue 02 (2006-10-31)
5-13
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before setting the alarm list, ensure that:
!
Procedure
To set the alarm list, perform the following steps:
Step 1 In Alarm Browse, Query and Statistics, right-click the alarm list and select Configure
Columns.
The Configure Columns dialog box is displayed, as shown in Figure 5-6.
Step 2 Select the columns to be displayed, and then click OK.
5-14
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
----End
Prerequisites
Before collecting instant alarm statistics, ensure that you have logged in to the M2000 client.
Procedure
To collect instant alarm statistics, perform the following steps:
Step 1 Choose Fault > Statistics > Alarm Statistics.
The Alarm Browse, Query and Statistics dialog box is displayed.
Step 2 Click the Statistics 1 tab.
Step 3 Select statistics items in Statistic Item.
Issue 02 (2006-10-31)
5-15
M2000
Operator Guide
5 Alarm Management
For example, select Alarm Level and Alarm Type. Click Statistic, and the alarm data is
displayed in a statistics table, as shown in Figure 5-7.
Figure 5-7 Alarm statistics table
5-16
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
----End
Prerequisites
Before collecting real-time alarm statistics, ensure that you have logged in to the M2000
client.
Procedure
To collect real-time alarm statistics, perform the following steps:
Step 1 Choose Fault > Statistics > Real-Time Statistics.
The Real-Time Statistics dialog box is displayed. The system refreshes the displayed data
automatically.
Issue 02 (2006-10-31)
5-17
M2000
Operator Guide
5 Alarm Management
Step 2 Drag the scroll bar on the right to view all the alarm statistics.
----End
Prerequisites
Before acknowledging an alarm manually, ensure that:
!
The Alarm Browse, Query and Statistics dialog box is displayed with a list of alarms.
Procedure
To acknowledge an alarm manually, perform the following steps:
Step 1 In Alarm Browse, Query and Statistics, select an unacknowledged alarm.
Step 2 Right-click the alarm and select Acknowledge.
The Confirm dialog box is displayed.
Step 3 Click Yes.
The alarm is displayed Acknowledged in the alarm list.
After acknowledgement, the cleared alarms are saved in the history alarm database and disappear from
the current interface.
----End
5-18
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before the system acknowledges alarms automatically, ensure that you have logged in to the
M2000 client.
Procedure
To set conditions for the system to acknowledge alarms automatically, perform the following
steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed.
Step 2 Set the conditions for auto acknowledgement, as shown in Figure 5-9.
Figure 5-9 Setting conditions for auto acknowledgement
Issue 02 (2006-10-31)
5-19
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before unacknowledging an alarm, ensure that:
!
The Alarm Browse, Query and Statistics dialog box is displayed with a list of alarms.
Procedure
To unacknowledge an alarm, perform the following steps:
Step 1 In Alarm Browse, Query and Statistics, select an acknowledged alarm.
Step 2 Right-click the alarm and select Unacknowledge.
The Confirm dialog box is displayed.
Step 3 Click Yes.
The alarm is displayed Unacknowledged in the alarm list.
----End
Prerequisites
Before creating a user defined alarm, ensure that you have logged in to the M2000 client.
5-20
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Procedure
To create a user defined alarm, perform the following steps:
Step 1 Choose Fault > NE Alarm Settings.
The NE Alarm Settings dialog box is displayed.
Step 2 Click the User Defined Alarm tab and then the Alarm Definition tab. Click Add.
The Add User Defined Alarm dialog box is displayed.
Step 3 Select the NE type, alarm severity (level), and alarm type. Enter the alarm name and alarm ID,
and click OK.
Step 4 In Alarm Definition, click Apply.
Step 5 Click the Alarm Binding tab.
The Add Alarm Binding dialog box is displayed
Step 6 Select the NE on the left of the dialog box and the new alarm on the right of the dialog box.
Under Bound Setting, set parameters such as Cabinet, Subrack, Slot and Port for this alarm.
Click OK.
Step 7 In Alarm Binding, click Apply.
----End
Prerequisites
Before displacing event alarms, ensure that you have logged in to the M2000 client.
Procedure
To displace event alarms, perform the following steps:
Step 1 Choose Fault > Alarm Displace.
The Alarm Displace dialog box is displayed.
Step 2 The event alarms can be displaced in two ways: auto displacement and manual displacement.
Issue 02 (2006-10-31)
5-21
M2000
Operator Guide
5 Alarm Management
!
Click the Auto Displace tab. Set Alarm category to Event alarm, select the file type,
set the displace conditions, and then click Start, as shown in Figure 5-10.
Manual displacement.
Click the Manual Displace tab. Set Alarm category to Event alarm, select the file type, set
the displace path, and then click Start, as shown in Figure 5-11.
5-22
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
The alarms in the database are deleted after the system displaces the alarms automatically.
When displacing the alarms manually, you can select the Keep alarm data in database after
displace to save the alarm records in the alarm database.
----End
Issue 02 (2006-10-31)
5-23
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before displacing history fault alarms, ensure that you have logged in to the M2000 client.
Procedure
To displace history fault alarms, perform the following steps:
Step 1 Choose Fault > Alarm Displace.
The Alarm Displace dialog box is displayed,
Step 2 History fault alarms can be displaced in two ways: auto displacement and manual
displacement.
!
Auto displacement.
Click the Auto Displace tab. Set Alarm category to History fault alarm, select the file
type, set the displace conditions, and then click Set.
Manual displacement.
Click the Manual Displace tab. Set Alarm category to History fault alarm, select the
file type, set the displace path, and then click Start.
Prerequisites
Before synchronizing alarms manually, ensure that:
5-24
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Procedure
To synchronize alarms manually, perform the following steps:
Step 1 In the Alarm Browse, Query and Statistics dialog box, select the alarm to synchronize.
To synchronize more alarms, press the Ctrl or Shift key to select the alarms.
Step 2 Right-click the selected alarm(s), and select Alarm Synchronize or NE Alarm Synchronize.
Step 3 Click Yes after the Confirm dialog box is displayed.
----End
Prerequisites
Before synchronizing alarms automatically, ensure that you have logged in to the M2000
client.
Procedure
The system performs the synchronization automatically. No manual setting or operation is
necessary.
Issue 02 (2006-10-31)
5-25
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before redefining the alarm severity (level), ensure that you have logged in to the M2000
client.
Procedure
To redefine the alarm severity (level), perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed.
Step 2 Click the Level Redefine tab, and then click Add.
The alarms of all the NEs are displayed on the left of the dialog box, as shown in Figure 5-12.
Figure 5-12 Redefining the alarm severity (level)
Step 3 Select an alarm or press Shift to select multiple alarms in the left pane, or press the Shift key
to select multiple alarms. Select an alarm severity (level) from the drop-down list on the right
of the dialog box.
Step 4 Repeat step 3 to redefine the alarm severities for other alarms.
Step 5 Click OK.
5-26
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
The left part of the dialog box displays the alarms with the redefined alarm severities.
To modify the redefined alarm severity, click Modify, and then perform Step 3 to set a new severity.
To remove the redefined alarm severity, click Delete.
----End
Custom correlation
Prerequisites
Before setting the correlation rules for repeated fault alarms, ensure that you have logged in to
the M2000 client.
Procedure
To set correlation rules for fault alarms, perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed.
Step 2 Click the Correlation tab.
Step 3 Select Activate under Activate or deactivate alarm correlation, and then click Set.
Issue 02 (2006-10-31)
5-27
M2000
Operator Guide
5 Alarm Management
Set the intermittence fault correlation only when the correlation attribute is enabled.
If you select Shield, only the first alarm is displayed when intermittence faults are
generated. The subsequent intermittence fault alarms are saved in the shielded alarm
database.
You can view the alarms in the shielded alarm database by clicking the Correlative Alarms tab in the
Alarm Details window. For details, see 5.4.8 "Querying Correlated Alarms."
If you select Abandon, the system deletes the alarms when intermittence faults are
generated.
Step 6 Select the NE type and the alarm name set Interval (seconds) and Times of intermittence.
Click Add.
Take setting the correlation for the MSC Server alarm Module Level Reset as an example.
The Module Level Reset alarm is generated and cleared 3 times within 10 seconds, as shown
in Figure 5-13.
Figure 5-13 Setting correlation for intermittent fault alarms
----End
5-28
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before setting correlation rules for repeated event alarms, ensure that you have logged in to
the M2000 client.
Procedure
To set correlation rules for event alarms, perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed.
Step 2 Click the Correlation tab.
Step 3 Select Activate under Activate or deactivate alarm correlation, and click Set.
Set the intermittence fault correlation only when the correlation attribute is enabled.
If you select Shield, only the first event alarm is displayed. The subsequent repeat event
alarms are saved in the shielded alarm database.
You can view the alarms in the shielded alarm database by clicking the Correlative Alarms tab in the
Alarm Details window. For details, see 5.4.8 "Querying Correlated Alarms." .
If you select Abandon, the system deletes the alarms when repeat event faults are
generated.
Step 6 Select the NE type and the alarm name set Interval (seconds) and Times of intermittence.
Click Add.
----End
Issue 02 (2006-10-31)
5-29
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before modifying the knowledge of alarms directly, ensure that you have logged in to the
M2000 client.
Procedure
To modify the knowledge of the alarms directly, perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed.
Step 2 Click the Knowledge and Explanation tab.
Step 3 Select the alarm to add or modify on the left of the dialog box, and enter or modify the
knowledge of this alarm in Knowledge on the right of the dialog box, as shown in Figure
5-14.
Step 4 Repeat step 3 to modify the knowledge of more alarms.
Step 5 Click Modify Knowledge.
The knowledge of this alarm is modified.
5-30
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
----End
Prerequisites
Before modifying the alarm knowledge through the file, ensure that you have logged in to the
M2000 client.
Procedure
To modify the alarm knowledge through a file, perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed.
Step 2 Click the Knowledge and Explanation tab.
Step 3 Click Export Knowledge.
Issue 02 (2006-10-31)
5-31
M2000
Operator Guide
5 Alarm Management
In the displayed dialog box, select the path and enter the name for the file with the exported
alarm knowledge.
Step 4 Modify the content in the Explain field in the knowledge file, and save the file.
Step 5 Click Import Knowledge to import this XML file into the alarm knowledge library.
----End
Prerequisites
Before setting the alarm board display, ensure that you have logged in to the M2000 client.
Procedure
To set the alarm board display, perform the following steps:
Step 1 Choose Fault > Local Terminal Settings.
The Local Terminal Settings dialog box is displayed.
Step 2 Click the Alarm Board tab.
Step 3 Set Alarm board windows setting, and set whether to display the number of the alarms.
For example, set the alarm board on top of all the other windows, and show the number of the
unacknowledged and uncleared alarms, and the number of acknowledged and uncleared
alarms.
Step 4 Click OK.
5-32
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
----End
Prerequisites
Before setting the alarm sounds, ensure that:
!
Procedure
To set the alarm sounds, perform the following steps:
Step 1 Choose Fault > Local Terminal Settings.
The Local Terminal Settings dialog box is displayed.
Step 2 Click the Sound and Color tab, as shown in Figure 5-15.
Step 3 Select the alarm sound files for alarms of various severities.
Step 4 Click OK.
Issue 02 (2006-10-31)
5-33
M2000
Operator Guide
5 Alarm Management
----End
Prerequisites
Before starting or stopping the alarm sound, ensure that you have logged in to the M2000
client.
Procedure
To start or stop the alarm sound for alarms of one alarm severity level, perform the following
steps:
Step 1 Choose Fault > Local Terminal Settings.
The Local Terminal Settings dialog box is displayed.
Step 2 Click the Sound and Color tab, as shown in Figure 5-15.
Step 3 Click the speaker icon behind each alarm severity level to start or stop the alarm sound.
5-34
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
----End
To start or stop the alarm sounds for alarms of all the alarm severity levels, perform the
following steps:
Step 1 Choose Fault > Alarm Board.
The Alarm Board dialog box is displayed.
Step 2 Click Sound to start or stop the alarm sound for all the alarm severity levels, as shown in
Figure 5-16.
Step 3 Close Alarm Board.
Figure 5-16 Setting the alarm board
----End
Prerequisites
Before setting the alarm colors, ensure that you have logged in to the M2000 client.
Procedure
To set the alarm colors, perform the following steps:
Step 1 Choose Fault > Local Terminal Settings.
Issue 02 (2006-10-31)
5-35
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before starting or stopping the alarm flash, ensure that you have logged in to the M2000
client.
Procedure
To start or stop the alarm flash, perform the following steps:
Step 1 Choose Fault > Alarm Board.
The Alarm Board dialog box is displayed.
Step 2 Click Flash to start or stop the alarm indicators for all the alarm severities, as shown in Figure
5-16.
Step 3 Close Alarm Board.
----End
5-36
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
The alarm box does not emit any audio or visual alarm for the alarms that are not selected.
By default, all alarms are delivered to the alarm box.
Prerequisites
Before setting the alarm box filter, ensure that:
!
The alarm box is connected properly with the M2000 client, and both of them are
running.
Procedure
To set the alarm box filter, perform the following steps:
Step 1 Choose Fault > Local Terminal Settings.
The Local Terminal Settings dialog box is displayed.
Step 2 Click the Alarm Box tab.
Step 3 Select Enable alarm box on the current client.
Step 4 Select the NEs and the alarm severities.
Alarms of the selected NEs and alarm severities are delivered to the alarm box, as shown in
Figure 5-17.
Step 5 Click OK.
Issue 02 (2006-10-31)
5-37
M2000
Operator Guide
5 Alarm Management
----End
Prerequisites
Before stopping alarm sounds, ensure that:
!
The alarm box is connected properly with the M2000 client, and both of them are
running.
Procedure
Choose Fault > Alarm Box > Stop Alarm Box Sound.
5-38
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before stopping the alarm box, ensure that:
!
The alarm box is connected properly with the M2000 client, and both of them are
running.
Procedure
To stop the alarm box, perform the following steps:
Step 1 Choose Fault > Alarm Box > Stop Alarm Box, and the alarm box is stopped. The Stop
Alarm Box is marked with a .
Step 2 If you select Stop Alarm Box again, the alarm box starts running again.
----End
Prerequisites
Before resetting the alarm box, ensure that:
!
The alarm box is connected properly with the M2000 client, and both of them are
running.
Procedure
Choose Fault > Alarm Box > Reset Alarm Box.
Issue 02 (2006-10-31)
5-39
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before setting the alarm notification by SMS, ensure that:
!
The wireless modem is connected properly to the M2000 client, and they are working
properly.
Procedure
To set the alarm notification by SMS, perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed, as shown in Figure 5-18.
Figure 5-18 Setting the remote alarm notification by SMS
5-40
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Prerequisites
Before setting the alarm notification by PhoneNo. or PagerNo., ensure that:
!
The telephone or pager is connected to the M2000 client through the modem, and the
connection is working properly.
Procedure
To set the alarm notification over PhoneNo.or PagerNo., perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed, as shown in Figure 5-18
Step 2 In the Remote Notify tab, click Parameter Settings.
The Remote notify detail setting dialog box is displayed.
Step 3 Click the Phone pager tab, and select Activate. Select values for Serial port and Sent point.
Step 4 Enter the test phone number or pager number, and then click Test.
Issue 02 (2006-10-31)
5-41
M2000
Operator Guide
5 Alarm Management
If the mobile phone or pager can receive the alarm notification, the displayed Test dialog box
prompts "The operation is successful ". If not, the system prompts "The operation failed.
After the test succeeds, click OK to return to the Remote notify detail setting dialog box
Step 5 Click OK to return to the Fault Service Settings dialog box.
Enter the user name and mobile phone or pager number. Select the alarm to be remote
notified.
Step 6 Click Add.
The settings are displayed in the lower part of the Remote Notify tab.
----End
Prerequisites
Before setting the alarm notification by email, ensure that:
!
The SMTP server is connected to the M2000 system and tested normal.
Procedure
To set the alarm notification by email, perform the following steps:
Step 1 Choose Fault > Fault Service Settings.
The Fault Service Settings dialog box is displayed, as shown in Figure 5-18.
Step 2 In the Remote Notify tab, click Parameter Settings.
The Remote notify detail setting dialog box is displayed.
Step 3 Click the Email tab, select Activate, and set the SMTP server.
Step 4 Enter the test Email address for receiving the alarms, and then click Test.
If the Email address can receive the alarm notification, the displayed Test dialog box prompts
"The operation is successful". If not, the system prompts "The operation failed.
After the test succeeds, click OK to return to the Remote notify detail setting dialog box
Step 5 Click OK to return to the Fault Service Settings dialog box.
5-42
Issue 02 (2006-10-31)
M2000
Operator Guide
5 Alarm Management
Enter the user name and Email address. Select the alarm to be remote notified.
Step 6 Click Add.
The setting information is displayed in the lower part of the Remote Notify tab.
----End
Issue 02 (2006-10-31)
5-43
M2000
Operator Guide
6 Performance Management
Performance Management
Description
6.7 Synchronizing
Performance Data
Issue 02 (2006-10-31)
6-1
M2000
Operator Guide
6 Performance Management
6-2
Title
Description
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Counters defined on the M2000 client, that is, user defined counters.
Common Counter
Common counters refer to key default 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.
You cannot add, modify, or delete KPIs.
Extended Counter
Extended counters are also default counters defined for an NE. The NE reports results of all
the extended counters to the M2000. The M2000 saves the results to the performance database
based on the settings on the M2000 client.
During the M2000 operation, you can select or clear extended counters.
!
When you select an extended counter, the measurement results of the extended counter
are saved to the M2000 performance database for future queries.
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.
The measurement results of the user-defined counters are not stored in the M2000 database.
When you query these results, the M2000 calculates the results through the set formula and
then displays the results through the client.
Issue 02 (2006-10-31)
6-3
M2000
Operator Guide
6 Performance Management
Function subset/
Measurement unit
Measurement
counter
Measurement
counter
Function subset/
Measurement unit
Measurement
counter
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.
Class 1 Object
Class 1 objects are not to be selected. Class 1 objects are not displayed in the Object Setting
dialog box. NEs automatically report the measurement results of default counters of class 1
objects to the M2000.
Class 2 Object
You must select class 2 objects before you start a performance measurement. The M2000
delivers the selected objects to the NE, and the NE reports the results of measurement
counters of these objects to the M2000.
By default, no class 2 objects are selected, and no results are reported.
You can select class 2 objects, such as a board in the SGSN system, in the Object Setting
dialog box.
Class 3 Object
You must enter class 3 objects for performance measurement. The M2000 delivers the entered
objects to the NE, and the NE reports the results of measurement counters of these objects to
the M2000.
6-4
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
You can enter class 3 objects, such as the IMSI number of the SGSN, in the Object Setting
dialog box.
Issue 02 (2006-10-31)
6-5
M2000
Operator Guide
6 Performance Management
Measurement
counter
Measurement
object
NE
Measurement
period
Collect
performance
data
Unselected
Analyze mediation
Discard
Save data
Query result
Calculate userdefined counter
Performance
database
M2000
client
Exceed
threshold?
Yes
Generate alarm
M2000 server
When a measurement period ends, the counters of an NE, both common counters and
specified extended counters, start to be measured. The NE collects the measurement results,
that is, the performance data, and reports the results to the M2000. After the mediation layer
in the M2000 server analyzes the received results, the performance server saves the results to
the performance database.
The M2000 controls the number of the received performance results. An alarm is generated
when the M2000 detects that more than the specified number of results are received.
File interface
The NE saves the measurement results of all the KPIs and extended counters into a file.
When a measurement period ends, the NE uploads the file generated for this period to
the M2000. The M2000 mediation layer analyzes the file and collects the results for each
6-6
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
counter. For the extended counter that is not selected, the M2000 discards the results
instead of saving them into the performance database.
!
Task interface
The M2000 delivers to the NE the information required for performance measurement,
for example, the information regarding objects, counters, and measurement periods.
Based on the received information, the NE creates performance measurement tasks and
measures each counter. When the measurement period ends, the NE reports the collected
results to the M2000. The M2000 analyzes the results and saves them to the performance
database.
Operations involved in the performance management are the same for these two different
interfaces.
Common counters
Extended counters
User-defined counters
For the class 1 objects, the performance results are displayed immediately after your
query.
For the class 2 or class 3 objects, you must select or enter the measurement objects. The
performance results are displayed after the set measurement period ends.
Issue 02 (2006-10-31)
6-7
M2000
Operator Guide
6 Performance Management
!
Prerequisites
Before querying results of periodic performance measurements, ensure that:
!
The performance results of the required measurement objects are reported to the M2000.
Procedure
To query results of periodic performance measurements, perform the following steps on the
M2000 client:
To set new conditions, perform the following steps:
Step 1 Choose Performance > Query Result.
The Query Result window is displayed.
Step 2 click New Query.
The Query dialog box is displayed.
Step 3 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
Step 4 Select measurement objects in the Object Selection tab, select measurement counters in the
Counter Selection tab, and set the measurement period and time in the Other Setting tab.
Step 5 Click Query.
The queried results are displayed on the screen. If the screen prompts "All counts to query are
unavailable now.", infer that these counters are extended counters. Select the extended
counters manually. In this case, perform steps 6 to 7.
Step 6 In the prompt dialog box, click Counter Setting.
The Counter Setting dialog box is displayed.
Step 7 Select the extended counters. Click OK.
When the screen switches to the Query Result window, perform steps 2 through 7 to continue
the query.
----End
To use query condition templates, perform the following steps.
Step 1 Choose Performance > Query Result.
The Query Result window is displayed.
Step 2 Select a query template in the navigation tree on the left.
6-8
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Step 3 Right-click the template and select Query. Select the time.
The queried results are displayed on the screen.
----End
Examples
For example, to set query conditions to measure the CPU usage of SGSN_REAL, perform the
following steps:
Step 1 Choose Performance > Query Result.
The Query Result window is displayed.
Step 2 Click New Query.
The Query dialog box is displayed.
Step 3 In the navigation tree on the left, select the SGSN_MML NE, the System load measurement
measurement set, and then the System load PM measurement unit.
Step 4 On the right of the dialog box, select all objects of SGSN_REAL, as shown in Figure 6-3.
Figure 6-3 Selecting the measurement unit and objects
Step 5 Click the Counter Selection tab. Select the counters to be measured, as shown in Figure 6-4.
Issue 02 (2006-10-31)
6-9
M2000
Operator Guide
6 Performance Management
These measurement counters are extended counters, which are selected manually. The selected
measurement counters are displayed normally under Counter Selection, and the rest counters are
grayed.
Step 6 Click the Other Setting tab. Select All under Default for Time and set Query Period to 30
minutes. Use the default values for other settings, as shown in Figure 6-5. Click Query.
6-10
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
----End
Prerequisites
Before querying results of real-time performance measurements, ensure that:
!
The performance results of the required measurement objects are reported to the M2000.
Procedure
To query the results of real-time performance measurements, perform the following steps on
the M2000 client:
To set new conditions, perform the following steps:
Step 1 Choose Performance > Query Result.
Issue 02 (2006-10-31)
6-11
M2000
Operator Guide
6 Performance Management
Examples
For example, to measure the CPU usage of SGSN_REAL in real time, perform the following
steps:
Step 1 Choose Performance > Query Result.
The Query Result window is displayed.
Step 2 Click Real Query.
The Real-Time Query dialog box is displayed.
Step 3 In the navigation tree on the left, select the SGSN_REAL NE, the System load
measurement measurement set, and then the System load PM measurement unit.
Step 4 On the right of the dialog box, select all the objects of SGSN_REAL.
Step 5 Click the Counter Selection tab. Select the counters to be measured.
6-12
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Step 6 Click the Other Setting tab. Select All under Default for Time and set Query Period to 5
minutes. Use the default values for other settings, and click Query.
Step 7 If the system prompts No result for the specified condition found, click Measurement in
the prompt dialog box.
The Real-Time Measure Management window is displayed.
----End
Prerequisites
Before setting query condition templates, ensure that:
!
The performance results of the required measurement objects are reported to the M2000.
Procedure
To set query condition templates, perform the following steps on the M2000 client:
Step 1 Choose Performance > Query Result.
The Query Result window is displayed.
!
Issue 02 (2006-10-31)
6-13
M2000
Operator Guide
6 Performance Management
Prerequisites
Before applying query condition templates, ensure that:
6-14
The performance results of the required measurement objects are reported to the M2000.
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Procedure
To apply query templates, perform the following steps on the M2000 client:
Step 1 Choose Performance > Query Result.
The Query Result window is displayed.
Step 2 Set a query template.
For details, see part 6.3.4 "Setting Query Condition Templates."
Step 3 Select a query template in the navigation tree on the left.
Step 4 Right-click and select Query. Set the time segment for querying results.
The queried performance measurement results are listed on the screen.
----End
Prerequisites
Before saving performance measurement results to files, ensure that:
!
The performance results of the required measurement objects are reported to the M2000.
Procedure
To save performance measurement results to files, perform the following steps on the M2000
client:
Step 1 Query performance measurement results.
For details, see part 6.3.2 "Querying Results of Periodic Performance Measurements" or part
6.3.3 "Querying Results of Real-Time Performance Measurements."
Step 2 When the results are displayed, click Save to save them as a file in the defined format.
----End
Issue 02 (2006-10-31)
6-15
M2000
Operator Guide
6 Performance Management
Prerequisites
Before saving performance measurement results to files automatically, ensure that:
!
The performance results of the required measurement objects are reported to the M2000.
Procedure
The process for saving performance measurement results automatically starts immediately
after M2000 services are started. According to the settings of the pmexport.cfg configuration
file, the queried measurement results are saved to the specified folder on the server.
!
PATH=/export/home/omc/var/fileint/pm/
files
DELAY=60
an integer multiple of 5.
SAVEDAYS=3
days.
To save performance measurement results to files automatically, perform the following steps
on the M2000 client:
Step 1 Log in to the server through FTP.
Step 2 Download the file in the /export/home/omc/var/fileint/pm/ folder to the client in the ASCII
mode.
Step 3 To modify the configuration file, contact the administrator, who has the privileges of the root
account.
----End
6-16
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before browsing files storing performance measurement results, ensure that:
!
Procedure
To browse files storing performance measurement results, perform either of the following
operations:
!
Use Notepad or other relevant software to open the TXT file to browse the performance
results.
Use Microsoft Internet Exploror or other relevant software to open the HTML file to
browse the performance results.
Use EXCEL or any other relevant software to open the CSV or XLS file to browse the
performance results.
Issue 02 (2006-10-31)
6-17
M2000
Operator Guide
6 Performance Management
Prerequisites
Before synchronizing performance data manually, ensure that:
!
Procedure
To synchronize performance data manually, perform the following steps on the M2000 client:
Step 1 Choose Performance > Measure Management.
The Measure Management window is displayed.
For real-time performance measurements, choose Performance > Real-Time Measure Management.
The Real-Time Measure Management window is displayed.
Step 2 Select an NE, a measurement set, a measurement unit and then an NE, as shown in Figure 6-7.
Figure 6-7 Synchronizing performance measurement results manually
6-18
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
After you perform this operation, the synchronization request is put into the M2000 system
queue. The system processes the request queue periodically, every 5 minutes or 15 minutes,
and obtains performance results as requested. If the request queue includes many
synchronization requests involving long time segments or many counters, the system requires
some time to complete data synchronization.
The period for the system to process the queue depends on the NE type. For different NE type, the
periods are different.
----End
Prerequisites
Before synchronizing performance data automatically, ensure that:
!
Procedure
The system automatically checks the consistency of measurement counters, objects, and
measurement results between the NEs and the M2000. No manual settings or operations are
necessary.
!
If the M2000 detects that the objects and counters on an NE are different, the M2000
delivers a command and requires the NE to modify the measurement information.
If the M2000 detects that the measurement results on an NE are different, it delivers a
command and requires the NE to report the measurement results.
Issue 02 (2006-10-31)
6-19
M2000
Operator Guide
6 Performance Management
Prerequisites
Before subscribing to performance measurement results, ensure that:
!
Procedure
To subscribe to performance measurement results, perform the following steps on the M2000
client:
If the measurement period is more than 30 minutes, perform the following steps.
Step 1 Choose Performance > Measure Management.
The Measure Management window is displayed.
Step 2 In the navigation tree on the left, select an NE type, a measurement set, a measurement unit
and then an NE.
Step 3 Click Subscribe.
The Subscribe Result dialog box is displayed, as shown in Figure 6-8.
Figure 6-8 Subscribing measurement results
----End
6-20
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
The M2000 displays a maximum of five tabs about the subscribed performance measurement results.
----End
Issue 02 (2006-10-31)
6-21
M2000
Operator Guide
6 Performance Management
Prerequisites
Before checking reliability of performance measurement results, ensure that:
!
Procedure
To check reliability of performance measurement results, perform the following steps on the
M2000 client:
Step 1 Choose Performance > Measure Management.
The Measure Management window is displayed.
Step 2 In the navigation tree on the left, select an NE type, a measurement set, a measurement unit
and then an NE.
Step 3 Click Reliability.
The Please Select Time Segment is displayed, as shown in Figure 6-10.
Figure 6-10 Please select time segment dialog box
6-22
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before collecting back the missing performance measurement results, ensure that:
!
Procedure
To collect back the missing results, perform the following steps on the M2000 client:
Step 1 Choose Performance > Measure Management.
The Measure Management window is displayed.
If you choose Performance > Real-Time Measure Management, the Real-Time Measure
Management window is displayed.
Step 2 In the navigation tree on the left, select an NE type, a measurement set, a measurement unit
and then an NE.
Step 3 Click LostResult.
The Please select time segment dialog box is displayed, as shown in Figure 6-10.
Step 4 Enter the time segment. Click OK.
A Message box is displayed to list the missing data, if any.
Step 5 Click Close.
Step 6 Click Synchornize in the Measure Management or Real-Time Measure Management
window.
The measurement results on the NE are manually synchronized to the M2000 performance
database.
Issue 02 (2006-10-31)
6-23
M2000
Operator Guide
6 Performance Management
----End
Prerequisites
Before suspending the collection of performance measurement results, ensure that:
!
Procedure
To suspend the collection of performance measurement results, perform the following steps
on the M2000 client:
Step 1 Choose Performance > Measure Management.
The Measure Management window is displayed.
Step 2 In the navigation tree on the left, select an NE type, a measurement set, a measurement unit
and then an NE.
Step 3 Click Suspend.
The Confirm dialog box is displayed.
Step 4 Click OK.
The collection of the measurement results is suspended. In the Measure Management
window, accordingly, the status of the relevant measurement counters changes from
Measuring to Suspended.
----End
6-24
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before starting the measurement of extended performance counters, ensure that:
!
Procedure
To start the measurement of extended performance counters, perform the following steps on
the M2000 client:
If the measurement period is more than 30 minutes, perform the following steps
Step 1 Choose Performance > Counter Setting.
The Counter Setting dialog box is displayed, as shown in Figure 6-11.
Issue 02 (2006-10-31)
6-25
M2000
Operator Guide
6 Performance Management
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
Step 3 On the right of the dialog box, select the measurement period and the extended counters,
Click OK.
----End
If the measurement period is 5 minutes or 15 minutes, perform the following steps.
Step 1 Choose Performance > Real-Time Counter Setting.
The Real-Time Counter Setting dialog box is displayed.
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
Step 3 On the right of the dialog box, select the measurement period and the extended counters.
Click OK.
----End
6-26
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before stopping the measurement of extended performance counters, ensure that:
!
Procedure
To stop the measurement of extended performance counters, perform the following steps on
the M2000 client:
If the measurement period is more than 30 minutes, perform the following steps.
Step 1 Choose Performance > Counter Setting.
The Counter Setting dialog box is displayed, as shown in Figure 6-11.
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
Step 3 Clear the extended counters for which you want to stop the measurement. Click OK.
----End
If the measurement period is 5 minutes or 15 minutes, perform the following steps.
Step 1 Choose Performance > Real-Time Counter Setting.
The Real-Time Counter Setting dialog box is displayed.
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
Step 3 Clear the extended counters for which you want to stop the measurement. Click OK.
----End
Issue 02 (2006-10-31)
6-27
M2000
Operator Guide
6 Performance Management
Prerequisites
Before adding measurement objects, ensure that:
!
Procedure
To add measurement objects, perform the following steps on the M2000 client:
Step 1 Choose Performance > Object Setting.
The Object Setting dialog box is displayed.
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
!
Step 3 The class 2 objects involved in the measurement unit are displayed on the right of the dialog
box, as shown in Figure 6-12. The displayed class 2 objects are selectable. Select the objects
you want to measure. Click OK.
Figure 6-12 Selecting measurement objects
Step 4 To add class 3 objects, right-click on the right of the Object Setting dialog box, and select
Add.
6-28
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
If the Add menu is not highlighted on the displayed menu, infer that you cannot add user-defined class 3
objects in this measurement unit.
Step 5 In the displayed Set Object Properties dialog box, enter the new object properties.
Step 6 Click OK to close the dialog box.
Step 7 Click OK in the Object Setting dialog box.
----End
Prerequisites
Before deleting measurement objects, ensure that:
!
Procedure
To delete measurement objects, perform the following steps on the M2000 client:
Step 1 Choose Performance > Object Setting.
The Object Setting dialog box is displayed.
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
!
Step 3 The class 2 objects involved in the measurement unit are displayed on the right of the dialog
box, as shown in Figure 6-12. The displayed class 2 objects can be cleared. Clear the objects
you do not want to measure. Click OK.
Step 4 To delete class 3 objects, right-click on the right of the Object Setting dialog box and select
Delete.
The Confirm dialog box is displayed.
If the Delete menu is not highlighted on the displayed menu, infer that this measurement unit does not
involve class 3 objects.
Issue 02 (2006-10-31)
6-29
M2000
Operator Guide
6 Performance Management
----End
Prerequisites
Before setting a threshold for collecting performance measurement results, ensure that you
have logged in to the M2000 client.
Procedure
To set a threshold for collecting performance measurement results, perform the following
steps on the M2000 client:
Step 1 Choose Performance > Threshold Setting.
The Threshold Setting dialog box is displayed.
Step 2 In the navigation tree on the left, select an NE, measurement set, and then a measurement
unit.
Step 3 Click Add at the bottom right corner.
The Add Threshold dialog box is displayed, as shown in Figure 6-13.
6-30
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Figure 6-13 Adding an alarm threshold for collecting performance measurement results
Step 4 Select objects, counters, and the direction. Set the status to Activated. Enter the threshold
value for triggering the alarm.
The parameters Value and Hysteresis together define whether to trigger an alarm.
For example,
!
In the Increasing direction, an alarm of a certain severity is triggered when the number
of measurement results reaches Value + Hysteresis.
In the Decreasing direction, the alarm is stopped when the number reaches Value
Hysteresis.
Issue 02 (2006-10-31)
6-31
M2000
Operator Guide
6 Performance Management
After an NE reports measurement results, the M2000 calculates user defined counters through
the arithmetic operation based on the defined conditions.
The counters used for calculating the user defined counter must belong to the same
measurement set.
Prerequisites
Before creating user defined counters, ensure that you have logged in to the M2000 client.
Procedure
To create user defined counters, perform the following steps on the M2000 client:
Step 1 Choose Performance > Customer Counter Management.
The Customer Counter Management dialog box is displayed.
Step 2 In the navigation tree on the left, select an NE, a measurement set, and then a measurement
unit.
Step 3 Click Add.
The Add User Defined Counter dialog box is displayed, as shown in Figure 6-14.
Figure 6-14 Creating user defined counters
Step 4 Enter the user defined name, select the meansurement counter and operator, and type the
calculation formula.
6-32
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before modifying user defined coudnters, ensure that you have logged in to the M2000 client.
Procedure
To modify user defined coudnters, perform the following steps on the M2000 client:
Step 1 Choose Performance > Customer Counter Management.
The Customer Counter Management dialog box is displayed.
Step 2 Select a user defined counter on the right of the dialog box. Click Modify.
The Modify User Defined Counter dialog box is displayed.
Step 3 Modify the information of the counter, and click Modify.
----End
Issue 02 (2006-10-31)
6-33
M2000
Operator Guide
6 Performance Management
Prerequisites
Before creating performance monitoring tasks, ensure that you have logged in to the M2000
client.
Procedure
To create performance monitoring tasks, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Click the NE View or Region View tab on the left of the Performance Monitor window.
Step 3 Select an object to monitor in the navigation tree.
Step 4 Right-click and select Start Monitor > User Defined.
The Monitor Parameters Setting dialog box is displayed, as shown in Figure 6-15.
6-34
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Issue 02 (2006-10-31)
6-35
M2000
Operator Guide
6 Performance Management
----End
You can start a maximum of eight monitoring tasks on the same client.
Prerequisites
Before starting performance monitoring, ensure that:
!
Procedure
To start performance monitoring, perform the following steps on the M2000 client:
6-36
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before filtering monitoring results, ensure that:
!
Procedure
To filter monitoring results, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Select an object to monitor in the navigation tree.
For details, see part 6.13.2 "Creating Performance Monitoring Tasks."
Step 3 Open the monitoring chart of a monitoring task.
For details, see part 6.13.3 "Starting Performance Monitoring."
Step 4 Right-click the Table Data tab and select Filter Setting.
The Filter Setting dialog box is displayed, as shown in Figure 6-17.
Issue 02 (2006-10-31)
6-37
M2000
Operator Guide
6 Performance Management
Prerequisites
Before setting monitoring thresholds, ensure that:
6-38
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Procedure
To set monitoring thresholds, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Select an object to monitor in the navigation tree.
For details, see part 6.13.2 "Creating Performance Monitoring Tasks."
Step 3 Open the monitoring chart of a monitoring task.
For details, see part 6.13.3 "Starting Performance Monitoring."
Step 4 In the Table Data tab, right-click and select Threshold Setting.
The Threshold Setting dialog box is displayed, as shown in Figure 6-18.
Figure 6-18 Setting a threshold
Step 5 Select a monitoring counter. Set the upper and/or lower limit and the show style.
Step 6 Click OK.
----End
Issue 02 (2006-10-31)
6-39
M2000
Operator Guide
6 Performance Management
Prerequisites
Before exporting data from the current monitoring table, ensure that:
!
Procedure
To export data from the current monitoring table, perform the following steps on the M2000
client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Select an object to monitor in the navigation tree.
For details, see part 6.13.2 "Creating Performance Monitoring Tasks."
Step 3 Open the monitoring chart of a monitoring task.
For details, see part 6.13.3 "Starting Performance Monitoring."
Step 4 In the Table Data tab, right-click and select Export Data.
The Save dialog box is displayed.
Step 5 Enter a file name. Specify the path for saving the file. Click OK.
----End
Counter compare charts: show changes of multiple counters of one monitored object.
Object compare charts: show changes of one counter of multiple monitored objects.
6-40
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before viewing the current monitoring chart, ensure that:
!
Procedure
To view the current monitoring chart, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Select an object to monitor in the navigation tree.
For details, see part 6.13.2 "Creating Performance Monitoring Tasks."
Step 3 Open the monitoring chart of a monitoring task.
For details, see part 6.13.3 "Starting Performance Monitoring."
Step 4 Select a monitoring result record in the Table Data tab.
Step 5 Right-click and select Show Monitor Chart.
The Monitor Information Setting dialog box is displayed, as shown in Figure 6-19.
Figure 6-19 Setting parameters for the monitoring chart
Issue 02 (2006-10-31)
6-41
M2000
Operator Guide
6 Performance Management
Prerequisites
Before viewing the trend chart, ensure that:
!
Procedure
To view the trend chart, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Select an object to monitor in the navigation tree.
For details, see part 6.13.2 "Creating Performance Monitoring Tasks."
Step 3 Open the monitoring chart of a monitoring task.
For details, see part 6.13.3 "Starting Performance Monitoring."
Step 4 In the Table Data tab, right-click and select Show Trend Chart.
TheTrend Chart Parameter Setting dialog box is displayed, as shown in Figure 6-20.
6-42
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before setting attributes for the monitoring chart, ensure that:
!
Procedure
To set attributes for the monitoring chart, perform the following steps on the M2000 client:
Step 1 In the monitoring task tab in the Performance Monitor window, select a monitoring chart
tab.
Step 2 Right-click in the chart area and select Properties.
The Property Setting dialog box is displayed, as shown in Figure 6-21.
Issue 02 (2006-10-31)
6-43
M2000
Operator Guide
6 Performance Management
File Format
File
Photo
6-44
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Prerequisites
Before exporting monitoring results, ensure that:
!
Procedure
To export monitoring results, perform the following steps on the M2000 client:
Step 1 In the monitoring task tab in the Performance Monitor window, select a monitoring chart
tab.
Step 2 Right-click in the chart area and select Export Data.
The Save dialog box is displayed.
Step 3 Enter a file name. Specify a path for saving the file and the file format as well.
Step 4 Click OK to export the monitoring data.
----End
Issue 02 (2006-10-31)
6-45
M2000
Operator Guide
6 Performance Management
Prerequisites
Before adding monitoring thresholds, ensure that:
!
Procedure
To add monitoring thresholds, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Click the Monitor Task tab on the left of the window.
Step 3 Select a monitoring task in the navigation tree.
Step 4 Right-click the monitoring task and select Monitor Threshold Setting.
The Monitor Threshold Management dialog box is displayed, as shown in Figure 6-22.
The Threshold List area displays all thresholds set for the monitoring task.
6-46
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Step 5 In the navigation tree in the Threshold Info area, select the object to monitor.
Step 6 Set rules for monitoring thresholds for the object.
Step 7 Click Add.
The added monitoring thresholds are displayed in the Threshold List area. The system
refreshes the Threshold List area on all the other clients.
----End
Prerequisites
Before modifying monitoring thresholds, ensure that:
Issue 02 (2006-10-31)
6-47
M2000
Operator Guide
6 Performance Management
!
Procedure
To modify monitoring thresholds, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
The Performance Monitor window is displayed.
Step 2 Click the Monitor Task tab on the left of the window.
Step 3 Select a monitoring task in the navigation tree.
Step 4 Right-click the monitoring task and select Monitor Threshold Setting.
The Monitor Threshold Management dialog box is displayed, as shown in Figure 6-22.
The Threshold List area displays all thresholds set for the monitoring task.
Step 5 Select a set monitoring threshold.
Step 6 In the Threshold Info area, reset monitoring threshold parameters.
Step 7 Click Modify.
The modified monitoring thresholds are displayed in the Threshold List area. The system
automatically refreshes the Threshold List area on all the other clients.
----End
Prerequisites
Before deleting monitoring thresholds, ensure that:
!
Procedure
To delete monitoring thresholds, perform the following steps on the M2000 client:
Step 1 Choose Performance > Performance Monitor.
6-48
Issue 02 (2006-10-31)
M2000
Operator Guide
6 Performance Management
Issue 02 (2006-10-31)
6-49
M2000
Operator Guide
7 Configuration Management
Configuration Management
Description
7.1 Querying NE
Configuration
7.2 Synchronizing NE
Configuration
7.3 Exporting NE
Configuration
Issue 02 (2006-10-31)
7-1
M2000
Operator Guide
7 Configuration Management
Physical information, such as the information about the cabinets, subracks, and boards
configured for an NE
Logical information, the information irrelevant to the physical NE structure, such as the
IP address, cell number, and route number
Prerequisites
Before querying the NE configuration through the MIT browser, ensure that:
!
Procedure
To query the NE configuration through the MIT browser, perform the following steps on the
M2000 client:
Step 1 Choose Configuration > MIT Browser.
The MIT Browser window is displayed.
Step 2 Select the NE to be queried in the navigation tree on the left.
The NE configuration is displayed in the window on the right. The NE becomes an
expandable node.
Step 3 Click
All the configuration types available for the NE are displayed in the navigation tree, as shown
in Figure 7-1.
7-2
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before querying the basic NE configuration, ensure that you have logged in to the M2000
client.
Procedure
To query the basic NE configuration, perform the following steps on the M2000 client:
Issue 02 (2006-10-31)
7-3
M2000
Operator Guide
7 Configuration Management
----End
7-4
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before synchronizing NE configuration manually, ensure that:
!
The NE is connected to the M2000, and the relevant mediation layer is installed.
Procedure
To synchronize NE configuration manually, perform the following steps on the M2000 client:
Step 1 Select one or more physical NEs in the topology view.
Step 2 Right-click and select Synchronize NE configuration or Synchronize NE configuration in
batch.
The synchronization progress is displayed on the top left corner of the NE icon, as shown in
Figure 7-3
Figure 7-3 Synchronization progress
When 100% is displayed, the synchronization is complete and the progress percentage bar exits.
----End
Prerequisites
Before synchronizing NE configuration automatically, ensure that the NE is properly
connected to the M2000.
Procedure
The system performs the automatic synchronization. No manual operations are required.
Issue 02 (2006-10-31)
7-5
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before synchronizing NE configuration periodically, ensure that:
!
Procedure
To synchronize the NE configuration periodically, perform the following steps on the M2000
client:
Step 1 Choose Configuration > Task Management.
The Task Management window is displayed.
Step 2 Click Add.
The Add Task dialog box is displayed.
Step 3 Enter the task name and description.
Step 4 Set Task Type to Scheduled Synchronization.
Step 5 Set the execution type, time, and period.
Step 6 Select the NE on which the scheduled synchronization is to be performed.
Step 7 Click OK.
----End
7-6
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before exporting NE confiugration manually, ensure that the NE is properly connected to the
M2000.
Procedure
To export NE confiugration manually, perform the following steps on the M2000 client:
Step 1 Choose Configuration > MIT Browser.
The MIT Browser window is displayed.
Step 2 Unfold the navigation tree. Select a physical NE to export the configuration.
Step 3 Right-click and select Export.
The Export Configuration Data dialog box is displayed.
Step 4 Enter a file name and a path for saving the file.
Step 5 Select a file type.
Step 6 Click Export.
----End
Prerequisites
Before exporting NE confiugration periodically, ensure that the NE is properly connected to
the M2000.
Procedure
To export NE confiugration periodically, perform the following steps on the M2000 client:
Step 1 Choose Configuration > Task Management.
The Task Management window is displayed.
Step 2 Click Add.
The Add Task dialog box is displayed.
Issue 02 (2006-10-31)
7-7
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before saving NE configuration to a file, ensure that you have logged in to the M2000 client.
Procedure
To save NE configuration to a file, perform the following steps on the M2000 client:
Step 1 Choose Configuration > NE Report.
The NE Selection-NE Report dialog box is displayed.
Step 2 Select the NE for which you want to query the configuration. Click OK.
The Operation Result dialog box is displayed, as shown in Figure 7-4.
7-8
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
The NodeBs of the same type may have different privileges based on the hosting RNC.
Prerequisites
Before setting NE type privilege rules, ensure that the NE is properly connected to the
M2000.
Issue 02 (2006-10-31)
7-9
M2000
Operator Guide
7 Configuration Management
Procedure
To set NE type privilege rules, perform the following steps on the M2000 client:
Step 1 Choose System > Security Management.
The Security Management dialog box is displayed.
Step 2 Select an NE type in the navigation tree.
Step 3 Click Setting Rule.
Step 4 The Setting Rule dialog box is displayed.
Step 5 Select users and command groups.
Step 6 Click OK.
----End
Prerequisites
Before applying NE type privilege rules, ensure that the NE communicates the M2000 well.
Procedure
To apply NE type privilege rules, perform the following steps on the M2000 client:
Step 1 Choose System > Security Management.
The Security Management window is displayed.
Step 2 Select an NE in the navigation tree.
If the target NE is not displayed in the navigation tree, right-click the NE node and select Refresh to
refresh the navigation manually.
7-10
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
M2000 users
To log in to the M2000, you must have an M2000 user account and the corresponding
password. M2000 user accounts are endowed with different operation privileges such as
security management, alarm management , and performance management. The M2000
administrator authorizes privileges to the other M2000 user accounts. The privilege
authorization is not described in this manual.
NE users
NE users are special M2000 user accounts. When an M2000 user is bound to an NE and
authorized with command privileges, the M2000 user becomes a user of that NE. The
information about the user is delivered to the NE. The NE user has the privileges to
execute the MML commands of the NE on the M2000 and LMT. In addition, the NE user
can start the LMT directly on the M2000. The NE users are authorized to execute
different commands.
Prerequisites
Before creating NE user accounts, ensure that:
!
Issue 02 (2006-10-31)
7-11
M2000
Operator Guide
7 Configuration Management
Procedure
To creat NE user accounts, perform the following steps on the M2000 client:
Step 1 Choose System > Security Management.
The Security Management window is displayed.
Step 2 Select an M2000 user in the User in the navigation tree.
Step 3 Right-click and select Bind NE.
The Bind NE dialog box is displayed.
Step 4 Select the NE you want to bind the user account, and select command groups, as shown in
Figure 7-5.
Figure 7-5 Selectting an NE and command groups for the created NE user account
7-12
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before modifying privileges for NE users, ensure that:
!
You are authorized to modify the MML commands bound to the NE user.
Procedure
To modify privileges for NE users, perform the following steps on the M2000 client:
Step 1 Choose System > Security Management.
The Security Management window is displayed.
Step 2 Under the NE node in the navigation tree, select the NE bound with the NE user you want to
modify, and then select the NE user, as shown in Figure 7-6.
Figure 7-6 Selecting an NE user
If the target NE is not displayed in the navigation tree, right-click the NE node in the topology view ,
select Refresh to refresh the navigation manually.
Step 3 On the right of the Security Management window, click the Command Group tab. Click
Bind Command Group.
The Bind Command Group dialog box is displayed, as shown in Figure 7-7.
Issue 02 (2006-10-31)
7-13
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before deleting an NE user account, ensure that:
!
Procedure
To delete NE user accounts, perform the following steps on the M2000 client:
Step 1 Choose System > Security Management.
7-14
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
If the target NE is not displayed in the navigation tree, right-click the NE node in the topology view ,
select Refresh to refresh the navigation manually.
The M2000 supports browsing user and NE logs, and monitors login of M2000 and NE users.
Manual synchronization: The M2000 starts extracting NE logs from NEs after receiving
a manual synchronization command.
Prerequisites
Before synchronizing NE logs, ensure that:
!
Issue 02 (2006-10-31)
7-15
M2000
Operator Guide
7 Configuration Management
!
7-16
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Step 2 Turn on the Enable the NE log synchronizing check box, set the time for automatic
synchronization, and click Set.
During the auto-synchronization process, much bandwidth and CPU resources are consumed. To avoid
the influence to user routine operation, Huawei recommends you to perform this task in the morning.
----End
Prerequisites
Before querying NE logs, ensure that:
!
Procedure
To query NE logs, perform the following steps on the M2000 client:
Issue 02 (2006-10-31)
7-17
M2000
Operator Guide
7 Configuration Management
Step 1 Choose System > Log Management > Log Query and Statistic.
The Log Management window is displayed.
Step 2 In the navigation tree on the left, select the nodes Log Query > NE Log.
Step 3 Set query conditions on the right of the window, as shown in Figure 7-10.
Figure 7-10 Querying NE logs
7-18
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before monitoring NE user login on LMTs, ensure that:
!
Procedure
No manual operations are required.
Prerequisites
Before monitoring operations and sessions of NE users, ensure that:
!
Procedure
To monitor operations and sessions of NE users, perform the following steps on the M2000
client:
Step 1 Choose System > User Monitor.
The User Monitor dialog box is displayed.
Step 2 Click the Location Maintenance Monitor tab.
Step 3 Select an NE in the physical topology tree on the left.
Step 4 Click Monitor.
The monitoring of the status, sessions, and operations of the users of the NE starts.
----End
Issue 02 (2006-10-31)
7-19
M2000
Operator Guide
7 Configuration Management
!
Device management
Trace management
Monitoring management
Prerequisites
Before upgrading the enhanced maintenance for NEs, ensure that:
!
Both the M2000 server and the client are installed with meditative NE software.
Procedure
To upgrade the enhanced maintenance for NEs, perform the following steps:
Step 1 Select a physical NE in 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 takes some time. Do you
really need to upgrade?"
Step 3 Click Yes.
If no upgrade files exist in the local, go to step 5).
Step 4 The Confirm dialog box is displayed, prompting The upgrade file exists. Do you want to
redownload the upgrade file?
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.
Step 5 Select the installation directory. Note that the directory must be the installation directory of
the current client.
Step 6 Click Next to install the upgrade file.
Step 7 Click Finish.
After the upgrade file is installed successfully, restart the M2000.
7-20
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Choose a menu item under the Enhanced NE Maintenance. The function is performed if the version of
common components for the enhanced NE maintenance on the M2000 client is consistent with that on
the server. Otherwise, perform the following steps:
!
If the version on the client is earlier than that on the server, the system prompts you to upgrade the
common component for the enhanced NE maintenance on the client. Click Yes to upgrade. Click No
to perform the maintenance forcibly.
If the version on the client is later than that on the server, the system prompts you to install the
corresponding enhanced NE maintenance version on the server, or uninstall the common component
for the enhanced NE maintenance on the client to restart the enhanced NE maintenance upgrade.
----End
Issue 02 (2006-10-31)
7-21
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before activating the NE device panel, ensure that:
!
Both the M2000 server and the client are installed with meditative NE software.
Procedure
To activate the NE device panel, perform the following steps:
Step 1 Select a physical NE in the topology view or from the navigation tree.
Step 2 Right-click the NE and choose Enhanced NE Maintenance > Equipment Management
from the shortcut menu.
You can manage the NE device in the displayed Device Panel dialog box, as shown in Figure
7-12.
Figure 7-12 Device panel
----End
7-22
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
!
Monitor the NE device and service status through graphics or data in real time.
Prerequisites
Before activating the NE monitoring panel, ensure that:
!
Both the M2000 server and the client are installed with meditative NE software.
Procedure
To activate the NE monitoring panel, perform the following steps:
Step 1 Select an NE in the topology view or from the navigation tree.
Step 2 Right-click the NE, and choose Enhanced NE Maintenance > Monitoring Management
from the shortcut menu.
You can monitor the NE in the displayed Monitor Panel window, as shown in Figure 7-13.
Figure 7-13 Monitor Panel
----End
Issue 02 (2006-10-31)
7-23
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before activating the NE trace panel, ensure that:
!
Both the M2000 server and the client are installed with meditative NE software.
Procedure
To activate the NE trace panel, perform the following steps:
Step 1 Select an NE in the topology view or from the navigation tree.
Step 2 Right-click the NE, and choose Enhanced NE Maintenance > Tracing Management from
the shortcut menu.
You can perform the trace management in the displayed Trace Panel dialog box, as shown in
Figure 7-14.
7-24
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
----End
Prerequisites
Before viewing the MML Command window, ensure that:
!
Issue 02 (2006-10-31)
7-25
M2000
Operator Guide
7 Configuration Management
!
Procedure
To view the MML Command window, perform the following steps on the M2000 client:
Step 1 Choose Configuration > MML Command.
The MML Command window is displayed.
Step 2 Select an NE and the NE version in the navigation tree on the left.
The MML command navigation tree and the command entry box are displayed, as shown in
Figure 7-15.
Figure 7-15 MML Command window
The system upgrades the NE version automatically if the NE version is not upgraded. After the upgrade,
query the MML commands of the NE.
----End
7-26
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before executing one MML command, ensure that:
!
Procedure
To execute one MML command, perform the following steps on the M2000 client:
Step 1 In the navigation tree , the upper left part of the MML Command window , select a NE with
version.
Step 2 In the MML command navigation tree, the bottom left part of the MML Command window,
select the node of an MML command you want to execute.
Step 3 Double-click the command node.
The command is displayed in the Command Input box in the bottom left part of the MML
Command window, as shown in Figure 7-15.
Step 4 Enter the parameters of the command.
The mandatory parameters are red.
Step 5 Click
on the right of the Command Input box or press F9 to execute the command.
The results for the executed command are displayed in the Command Maintenance tab in
the right part of the MML Command window.
When executing the same MML command on multiple NEs, the system delivers the command to the
NEs one after another. The NEs, however, must be of the same type and version.
For some MML commands, more than one message is returned after you execute the command. The
Command Maintenance tab, however, displays only the first message. To view the following
messages, choose Configuration > Follow-up Report Browser. The Follow-up Report
Browser window is displayed to show the following messages.
----End
Issue 02 (2006-10-31)
7-27
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before setting the MML command script, ensure that:
!
Procedure
To set the MML command script, perform the following steps on the M2000 client:
Step 1 Click the Command Maintenance tab on the right of the MML Command window.
Step 2 Right-click in the blank area of the tab, and select MML Client Setting.
The MML Client Setting dialog box is displayed, as shown in Figure 7-16.
Figure 7-16 Selecting the script mode
Step 3 Turn on the Script Mode check box in the Operation Mode Option area. Click OK.
Step 4 Enter an MML command in the MML Command window.
You can enter multiple MML commands here. The entered commands are added to the
command list.
Step 5 Click
7-28
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before executing multiple MML commands, ensure that:
!
Procedure
To execute multiple MML commands, perform the following steps on the M2000 client:
Step 1 Choose Configuration > Script Command.
The Script Command window is displayed.
Step 2 Click Create.
The Create Task dialog box is displayed, as shown in Figure 7-17.
Figure 7-17 Create Task dialog box
Issue 02 (2006-10-31)
7-29
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before executing MML commands periodically, ensure that:
!
Procedure
To execute MML commands periodically, perform the following steps on the M2000 client:
Step 1 Choose Configuration > Script Command.
The Script Command window is displayed.
Step 2 Click Create.
The Create Task dialog box is displayed, as shown in Figure 7-17.
Step 3 Enter a task name, and select a script file.
Step 4 Turn on the Periodic Task option. Set Start Time, Period, and Repeat Times. Click OK.
----End
7-30
Issue 02 (2006-10-31)
M2000
Operator Guide
7 Configuration Management
Prerequisites
Before saving MML command results, ensure that:
!
Procedure
To save MML command results, perform the following steps on the M2000 client:
Step 1 Select an NE and an NE version in the MML Command window.
The M2000 GUI displays the MML Command tree and the Command Input box.
Step 2 Right-click the Command Maintenance tab in the MML Command window, and select
Report Redirection.
Step 3 In the displayed Save dialog box, enter a name for the file to save the MML command result.
Step 4 Execute an MML command.
The command result is displayed in the Common Maintenance tab and saved to the file.
Step 5 To stop the saving of the command result, right-click in the Command Maintenance tab, and
select Cancel Redirection.
To save the result of the last MML command to a file, right-click in the Common Maintenance tab, and
select Save As.
----End
Issue 02 (2006-10-31)
7-31
M2000
Operator Guide
Description
Issue 02 (2006-10-31)
8-1
M2000
Operator Guide
Prerequisites
Before checking NE software packages on the M2000, ensure that you have logged in to the
M2000 client.
Procedure
To check NE software packages on the M2000, perform the following steps on the M2000
client:
Step 1 Choose Software > Browser.
The Software Browser dialog box is displayed.
Step 2 Click the Server tab. Select an NE type in the navigation tree.
Step 3 Select the VERSION node to view the information about all software versions and patches of
the NE type, as shown in Figure 8-1.
8-2
Issue 02 (2006-10-31)
M2000
Operator Guide
----End
Prerequisites
Before checking the running NE software, ensure that:
!
Procedure
To check the running NE software, perform the following steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 Click the NE tab. Select an NE in the navigation tree.
Issue 02 (2006-10-31)
8-3
M2000
Operator Guide
Step 3 Select the VERSION node to view the information about the software version and patches of
the NE.
----End
File Server
NodeB
RNC or M2000
RNC
RNC or M2000
CG
SGSN
GGSN
SGSN or M2000
MSCServer
MGW
HLR
IWF
8-4
Issue 02 (2006-10-31)
M2000
Operator Guide
Prerequisites
Before setting the NE file server, ensure that you have logged in to the M2000 client.
Procedure
To set the NE file server, perform the following steps on the M2000 client:
Step 1 Choose System > File Server Setting.
The File Server Setting dialog box is displayed.
Step 2 Select an NE in the navigation tree.
Step 3 In the File Server Name column on the right of the dialog box, select a file server for the NE,
as shown in Figure 8-2.
Figure 8-2 Setting the file server
Issue 02 (2006-10-31)
8-5
M2000
Operator Guide
No
Fall back software
version
End
Prerequisites
Before copying the NE software to the M2000 client, ensure that you have logged in to the
Windows operating system.
Procedure
To copy the NE software to the M2000 client, perform the following steps on the M2000
client:
8-6
Issue 02 (2006-10-31)
M2000
Operator Guide
Step 1 Insert the NE software CD into the CD-ROM of the M2000 client.
Step 2 Copy the data from the CD to the disk on the computer.
----End
Prerequisites
Before uploading the NE software from the M2000 client to the M2000 server, ensure that
you have logged in to the M2000 client.
Procedure
To upload the NE software from the M2000 client to the M2000 server, perform the following
steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 Click the Server tab. Select the NE for which you want to upload the software.
Step 3 Select the VERSION node and then a software version.
Step 4 Right-click and select Upload Patch File to Current Folder > From Local.
The Upload File to Server dialog box is displayed.
Step 5 Select the path of the local NE software file in the left pane. Click
the right pane.
Issue 02 (2006-10-31)
8-7
M2000
Operator Guide
Files must be transferred between the client and the NEs through a file server.
Prerequisites
Before downloading the NE software to a board of an NE, ensure that:
!
Procedure
To download the NE software to a board of an NE, perform the following steps on the M2000
client:
Step 1 Choose Software > File Transfer Wizard.
The File Transfer Wizard dialog box is displayed, as shown in Figure 8-4.
8-8
Issue 02 (2006-10-31)
M2000
Operator Guide
Step 2 Select the file location, file type, and NE type. Click Next.
Step 3 Select the file to be transferred, and click Next.
Step 4 Select NE as the destination. Click Next.
Step 5 Confirm the transfer settings. Click Transfer.
The Download Software Parameters Selection dialog box is displayed, as shown in Figure
8-5.
Issue 02 (2006-10-31)
8-9
M2000
Operator Guide
Step 6 Select the board to which the software is downloaded. Click OK.
Step 7 Click Exit in the File Transfer Wizard dialog box.
----End
Prerequisites
Before operating the NE software, ensure that:
!
8-10
Issue 02 (2006-10-31)
M2000
Operator Guide
Procedure
To operate the NE software, perform the following steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 Click the NE tab. Select an NE.
Step 3 Select the VERSION node, and then a software version.
Step 4 Right-click and select one of the following menu items:
The NE resets automatically after you activate the NE software. Be cautious with the Activate
operation.
!
After you select one of the above menu items, the M2000 creates a software management task.
Choose Software > Browser to view the task in the Software Browser window.
----End
Prerequisites
Before downloading NE software patches to a board of an NE, ensure that:
!
Issue 02 (2006-10-31)
8-11
M2000
Operator Guide
Procedure
For details, see part 8.3.4 "Downloading the NE Software to a Board of an NE."
Confirm: to confirm the patches so that the activated patch serves as the current default
patch and the patch is still valid upon a system restart.
Confirm the patches after the patches work properly for a while after being activated.
Prerequisites
Before operating patches, ensure that:
!
Procedure
To operate patches, perform the following steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 Click the NE tab. Select an NE. Select the VERSION node and then a patch version.
Step 3 Right-click and click one of the following menu items:
8-12
Issue 02 (2006-10-31)
M2000
Operator Guide
The NE resets automatically after you activate the NE software. Be cautious with the Activate
operation.
!
After you select one of the above menu items, the M2000 creates a software management task.
Choose Software > Browser to view the task in the Software Browser window.
----End
Prerequisites
Before monitoring the software upgrade progress, ensure that:
!
Procedure
To monitor the software upgrade progress, perform the following steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 The progress percentages of various tasks are listed in a table in the lower part of the
Software Browser window.
Step 3 Right-click and select Set to filter the information displayed in the window.
To view the details of a particular line, right-click and select Show Detail.
----End
Issue 02 (2006-10-31)
8-13
M2000
Operator Guide
Prerequisites
Before falling back the software version, ensure that:
!
Procedure
To fall back the software version, perform the following steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 Click the NE tab. Select the NE version that is used before the upgrade.
Step 3 Right-click and select Load to load the NE software.
The NE resets automatically after you activate the NE software. Be cautious with the Activate
operation.
Step 4 Right-click and select Activate to activate the NE software.
----End
8-14
Upgrade the software of one NodeB first. After verifying the software upgrade, install
and verify the patches, and then upgrade the other NodeBs in batches.
Issue 02 (2006-10-31)
M2000
Operator Guide
Upgrade all the NodeBs in batches. Divide them into groups and then upgrade the
NodeBs in each group in batches.
To simplify the verification test after the upgrade, divide the NodeBs by region. The
number of NodeBs in one group depends on the batch processing capability of the
M2000. By default, the M2000 supports batch upgrade of 30 NodeBs at a time.
Prerequisites
Before upgrading one NodeB, ensure that:
!
The upgrade software and patches of the NodeB are uploaded to the M2000 server.
Procedure
To upgrade one NodeB, perform the following steps on the M2000 client:
Step 1 Choose Software > Browser.
The Software Browser window is displayed.
Step 2 Click the NE tab. Select NodeB.
Step 3 Right-click and select Upgrade.
The NodeB Upgrade step 1 of 2 dialog box is displayed, as shown in Figure 8-6.
Issue 02 (2006-10-31)
8-15
M2000
Operator Guide
8-16
Issue 02 (2006-10-31)
M2000
Operator Guide
Step 5 Select Upgrade Bootrom and Software or Upgrade Patch, and select the relevant
operations.
Click OK.
The Confirm dialog box is displayed.
Step 6 Click OK.
The system upgrades the NodeB software or patches.
----End
Prerequisites
Before upgrading multiple NodeBs, ensure that:
!
The upgrade software and patches of the NodeBs are uploaded to the M2000 server.
Procedure
For details, see part 8.4.2 "Upgrading One NodeB." Ensure to select multiple NodeBs in the
NodeB Upgrade step 2 of 2 dialog box.
Issue 02 (2006-10-31)
8-17
M2000
Operator Guide
Prerequisites
Before checking the license allocated to NodeBs, ensure that:
!
Procedure
To check the license allocated to NodeBs, perform the following steps on the M2000 client:
Step 1 Choose Software > License Manager.
The License Browser window is displayed, as shown in Figure 8-8.
Figure 8-8 Browsing the license of the current NodeB
Step 2 Select an RNC node in the file structure tree on the left.
The table on the right displays the license of all the NodeBs hosted in this RAN.
8-18
Issue 02 (2006-10-31)
M2000
Operator Guide
----End
Prerequisites
Before modifying the license allocated to NodeBs, ensure that:
!
The Equipment Serial Number (ESN) is obtained from the corresponding NodeB.
The sum of the license allocated to all the NodeBs hosted in the RNC does not exceed
the license control information.
Procedure
To modify the license allocated to NodeBs, perform the following steps on the M2000 client:
Step 1 Choose Software > License Manager.
The License Browser window is displayed.
Step 2 Select an RNC node in the file structure tree on the left.
The table in the upper part of the window displays the RAN license.
Step 3 Select a license record.
The table in the lower part of the window lists the license allocated to all the NodeBs hosted
in the RAN concerned.
Step 4 Select a NodeB license record. Right-click and select Modify, or double-click the NodeB
license record.
The Modify dialog box is displayed.
Reset the parameters.
Step 5 Click OK.
Step 6 Make the modified license effective.
For details, see 8.5.4 "Allocating the RAN License."
----End
Issue 02 (2006-10-31)
8-19
M2000
Operator Guide
Prerequisites
Before allocating the RAN license, ensure that:
!
Procedure
To allocate the RAN license, perform the following steps on the M2000 client:
Step 1 Choose Software > License Manager.
The License Browser window is displayed.
Step 2 Select an RNC node in the file structure tree on the left.
The table in the upper part of the window displays the RAN license.
Step 3 Select a license record.
The lower part of the window lists the license allocated to all the NodeBs hosted in the RAN
concerned.
Step 4 Select a NodeB with the license modified. Right-click and select Distribute All.
The Confirm dialog box is displayed.
Step 5 Click OK.
The modified license information is allocated to all the NodeBs.
----End
8-20
Issue 02 (2006-10-31)
M2000
Operator Guide
Prerequisites
Before synchronizing the license allocated to NodeBs, ensure that:
!
Procedure
To synchronize the license allocated to NodeBs, perform the following steps on the M2000
client:
Step 1 Choose Software > License Manager.
The License Browser window is displayed.
Step 2 Select an RNC node in the file structure tree on the left.
The table in the right upper part of the window displays the RAN license.
Step 3 Select a license record.
The table in the lower part of the window lists the license allocated to all the NodeBs hosted
in the RAN concerned.
Step 4 Select a NodeB with the license modified. Right-click and select Synchronize License to
synchronize the NodeB license.
----End
Prerequisites
Before deleting the RAN license, ensure that:
!
Issue 02 (2006-10-31)
8-21
M2000
Operator Guide
Procedure
To delete the RAN license, perform the following steps on the M2000 client:
Step 1 Choose Software > License Manager.
The License Browser window is displayed.
Step 2 Select an RNC node in the file structure tree on the left.
The table in the right upper part of the window displays the RAN license.
Step 3 Select a license record. Right-click and select Delete.
The license is deleted.
----End
8.5.7 Uploading the License from the Client to the Folder on the
Server
Description
Upload the license from the M2000 client to a folder on the M2000 server and wait for
allocation.
Prerequisites
Before uploading the license from the client to a folder on the server, ensure that:
!
Procedure
To upload the license from the client to a folder on the server, perform the following steps on
the M2000 client:
Step 1 Choose Software > License Manager.
The License Browser window is displayed.
Step 2 Select an RNC node in the file structure tree on the left. Right-click the RNC node and select
Upload > From Client.
The Upload File(s) to Server dialog box is displayed.
8-22
Issue 02 (2006-10-31)
M2000
Operator Guide
Step 3 Select the file(s) or folder(s) to be uploaded on the left, and click
list on the right. Click
the left list.
Issue 02 (2006-10-31)
8-23
M2000
Operator Guide
9 Backup Managemnet
Backup Managemnet
Description
Issue 02 (2006-10-31)
9-1
M2000
Operator Guide
9 Backup Managemnet
Backup File
Description
NodeB
Data configuration
Engineering parameters
Operation logs
Device archives
Board logs
RTWP data
Configuration data
System data
User data
Performance tasks
User-defined performance
options
Performance templates
Tracing tasks
License
SGSN license
System description
Environment configuration
Configuration data
Performance task
configuration
SGSN
MGW
9-2
Issue 02 (2006-10-31)
M2000
Operator Guide
9 Backup Managemnet
NE Type
Backup File
Description
User-defined performance
counters
Alarm configuration
modification
Alarm synchronization
number
Data management
configuration
User data
Configuration data
Alarm logs
Operation logs
Performance statistics
User data
RNC
Configuration data
MSC
Server
Configuration data
CG
Configuration data
CG configuration data
HLR
Configuration data
IWF
Configuration data
GGSN
Issue 02 (2006-10-31)
9-3
M2000
Operator Guide
9 Backup Managemnet
Periodic backup: The M2000 backs up the NE data periodically through the periodic
backup task, which backs up the data about all the NEs.
Manual backup: Manual backup is also called immediate backup. In other words, you
can back up the NE data manually at any time.
Prerequisites
Before backing up NE data periodically, ensure that:
!
Procedure
To back up NE data periodically, perform the following steps on the M2000 client:
Step 1 Choose Tool > System Backup > Periodic Backup Setting.
The Periodic Backup dialog box is displayed, as shown in Figure 9-1.
9-4
Issue 02 (2006-10-31)
M2000
Operator Guide
9 Backup Managemnet
The periodic backup tasks are activated only after you turn on the Enable NE Periodic Backup check
box.
Step 4 Click
Step 5 Set the period for executing the periodical backup task.
The system executes the backup task at the specified time periodically.
Step 6 Click OK.
----End
Prerequisites
Before backing up NE data manually, ensure that:
Issue 02 (2006-10-31)
9-5
M2000
Operator Guide
9 Backup Managemnet
!
Procedure
To back up NE data manually, perform the following steps on the M2000 client:
Step 1 Choose Tool > System Backup > Backup Management.
The Backup Management dialog box is displayed.
Step 2 Click the NE Backup List tab.
Step 3 Select an NE in the navigation tree to back up the NE data.
Press Ctrl to select multiple NEs at a time. To select all the NEs, select the root node.
Prerequisites
Before browsing the NE backup progress, ensure that:
!
Procedure
To browse the NE backup progress, choose Tool > System Backup > Backup Management.
The progress of the backup task is displayed in the lower part of the Backup Management
dialog box.
9-6
Issue 02 (2006-10-31)
M2000
Operator Guide
9 Backup Managemnet
Prerequisites
Before checking NE backup files, ensure that:
!
Procedure
To check NE backup files, perform the following steps on the M2000 client:
Step 1 Choose Tool > System Backup > Backup Management.
The Backup Management dialog box is displayed.
Step 2 Click the NE Backup List tab.
Step 3 Unfold the the navigation tree, and select an NE.
All the backup files of the NE data are listed in the right part of the tab.
Click Refresh to refresh the backup file list. Choose Tool > System Backup > Backup Management,
and the Backup Management dialog box is displayed
----End
Prerequisites
Before restoring the NE data, ensure that:
!
Issue 02 (2006-10-31)
9-7
M2000
Operator Guide
9 Backup Managemnet
!
Procedure
To restore the NE data, perform the following steps on the M2000 client:
Step 1 Choose Tool > System Backup > Backup Management.
The Backup Management window is displayed.
Step 2 Click the NE Backup List tab.
Step 3 Select an NE in the navigation tree.
The backup files of the NE data are listed in NE Backup List.
Press Ctrl to select multiple NEs at a time. To select all the NEs, click the root node.
9-8
Issue 02 (2006-10-31)
M2000
Operator Guide
10 Troubleshooting
10
Troubleshooting
Description
Issue 02 (2006-10-31)
10-1
M2000
Operator Guide
10 Troubleshooting
Possible Causes
The possible causes include:
!
The user account is already deleted because the user account has not been used for login
for more than six months.
Handling Suggestions
Handle this fault in either of the following ways:
!
Relog in to the M2000 client with the correct user name and password.
Possible Causes
The possible causes include:
!
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.
10-2
Issue 02 (2006-10-31)
M2000
Operator Guide
10 Troubleshooting
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.
Possible Causes
The password is incorrect.
Handling Suggestions
Relog in to the M2000 client with the correct user name and the 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.
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.
Issue 02 (2006-10-31)
10-3
M2000
Operator Guide
10 Troubleshooting
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.
Possible Causes
The possible causes include:
!
Handling Suggestions
Handle the fault in either of the following ways:
!
10-4
Contact the M2000 administrator to check the operating status of the server.
Issue 02 (2006-10-31)
M2000
Operator Guide
10 Troubleshooting
Possible Causes
The number of users logging in to the M2000 system reaches the limit.
Handling Suggestions
Wait until a user exits the system.
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 .
Possible Causes
The possible causes include:
!
The client and server versions do not belong to the same version series.
Issue 02 (2006-10-31)
The client version and the server version belong to the same version series, for example,
C02B022.
10-5
M2000
Operator Guide
10 Troubleshooting
!
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. For details, see the
M2000 Software Installation Manual or M2000 HA System Software Installation Manual.
Possible Causes
The possible causes include:
!
Handling Suggestions
Handle the fault in either of the following ways:
!
Do not change the time of the current M2000 client during the M2000 operation. Exit the
M2000 client before you change the time.
Possible Causes
The possible causes include:
!
10-6
Issue 02 (2006-10-31)
M2000
Operator Guide
10 Troubleshooting
Handling Suggestions
Handle the fault in either of the following ways:
!
Possible Causes
The configuration file is incorrect.
Handling Suggestions
Uninstall the existing M2000 client, and install a new one.
Possible Causes
The M2000 uses the event mechanism of CORBA to check whether the communication
between the M2000 client and the M2000 server is functioning well. 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:
Issue 02 (2006-10-31)
10-7
M2000
Operator Guide
10 Troubleshooting
!
Handling Suggestions
!
If you set dual client IP addresses, change the settings on the client as follows.
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.
!
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, see the M2000 Installation Manual or M2000 HA System Installation Manual.
10-8
Issue 02 (2006-10-31)
M2000
Operator Guide
10 Troubleshooting
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.
Possible Causes
The causes include:
!
You do not have the privilege to create objects with the same name.
Handling Suggestions
Change the object name and recreate the topology object.
Possible Causes
The printer prints the alarm messages when the records fill one whole page or five minutes
after the printer receives the alarms.
Issue 02 (2006-10-31)
10-9
M2000
Operator Guide
10 Troubleshooting
Handling Suggestions
This is normal. No operation is necessary.
Possible Causes
The phone number is incorrect. The phone number must begin with the country code, for
example, 861361234***1, where 86 is the country code of the Peoples 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
Enter the correct phone number in Remote notify detail settings.
Possible Causes
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.
Handling Suggestions
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.
Possible Causes
The NE reporting the alarm has been deleted from the M2000.
10-10
Issue 02 (2006-10-31)
M2000
Operator Guide
10 Troubleshooting
Handling Suggestions
No operation is required.
To avoid such faults, delete the NE data after you delete an NE.
Issue 02 (2006-10-31)
10-11