00389527-Operation Guide (V200R012 - 02, IMS)

iManager N2000 UMS Network Management System
V200R012
Operation Guide
Issue
02
Date
2008-05-31
Part Number
00389527
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.


Operation Guide
Contents
Contents
About This Document.....................................................................................................................1
1 Getting Started............................................................................................................................1-1
1.1 Logging In to the N2000 UMS.......................................................................................................................1-3
1.2 Changing the Current User Password.............................................................................................................1-3
1.3 Getting to Know the Client GUI.....................................................................................................................1-4
1.3.1 GUI.........................................................................................................................................................1-4
1.3.2 Menu Bar................................................................................................................................................1-5
1.3.3 Toolbar...................................................................................................................................................1-5
1.3.4 Main Window.........................................................................................................................................1-8
1.3.5 Status Bar...............................................................................................................................................1-8
1.3.6 Shortcut Conventions on the Client GUI...............................................................................................1-8
1.3.7 Shortcut Keys.........................................................................................................................................1-9
1.4 Setting Automatic Login...............................................................................................................................1-10
1.5 Changing the Login Server...........................................................................................................................1-11
1.6 Setting Client Display...................................................................................................................................1-11
1.6.1 Setting the Window Title.....................................................................................................................1-12
1.6.2 Setting the Output Information............................................................................................................1-12
1.6.3 Setting Topology Display Style...........................................................................................................1-12
1.6.4 Setting Topology Features...................................................................................................................1-13
1.6.5 Setting Alarm Colors............................................................................................................................1-14
1.6.6 Setting Alarm Local Display Properties...............................................................................................1-15
1.7 Customizing the Client Time Format............................................................................................................1-15
1.7.1 Setting the Time Format.......................................................................................................................1-15
1.7.2 Setting the Date Format........................................................................................................................1-16
1.8 Locking the Client.........................................................................................................................................1-17
1.8.1 Locking the Client Automatically........................................................................................................1-17
1.8.2 Locking the Client Manually................................................................................................................1-18
1.9 Unlocking the Client.....................................................................................................................................1-18
1.10 Querying Information on Client Components.............................................................................................1-18
1.11 Querying License Information....................................................................................................................1-18
1.12 Setting the Browser Path.............................................................................................................................1-19
1.13 Logging Out of the Current Session............................................................................................................1-19
1.14 Exiting from the Client................................................................................................................................1-19
Issue 02 (2008-05-31)

Contents

Operation Guide
2 Topology Management.............................................................................................................2-1
2.1 Getting to Know Topology Management........................................................................................................2-3
2.1.1 Topology Management Interface...........................................................................................................2-3
2.1.2 Topology Management Terms...............................................................................................................2-3
2.1.3 Topology Legend...................................................................................................................................2-5
2.2 Process of Construct the Network Topology..................................................................................................2-7
2.3 Setting the Topology Background...................................................................................................................2-7
2.4 Setting Up a Physical Submap........................................................................................................................2-8
2.4.1 Designing a Topology............................................................................................................................2-9
2.4.2 Creating a Submap.................................................................................................................................2-9
2.4.3 Adding Devices....................................................................................................................................2-10
2.4.4 Creating a Link.....................................................................................................................................2-11
2.5 Adding Devices.............................................................................................................................................2-12
2.5.1 Adding a Device...................................................................................................................................2-12
2.5.2 Adding Devices in Batch......................................................................................................................2-14
2.5.3 Adding Devices Periodically................................................................................................................2-16
2.5.4 Setting Device Maintenance Information ............................................................................................2-17
2.5.5 Setting the Maintenance Personnel Information..................................................................................2-18
2.6 Topological Link Management ....................................................................................................................2-19
2.6.1 Classification of Topological Links.....................................................................................................2-20
2.6.2 Status Legends of the Topological Link..............................................................................................2-22
2.6.3 Displaying Topological Links..............................................................................................................2-23
2.6.4 Hiding Topological Links....................................................................................................................2-24
2.6.5 Querying Attributes of a Topological Link..........................................................................................2-25
2.6.6 Modifying Basic Attributes of a Topological Link..............................................................................2-26
2.6.7 Refreshing Topological Links..............................................................................................................2-26
2.6.8 Synchronizing Topological Links from the ATCA Devices................................................................2-27
2.6.9 Aggregating Multiple Links.................................................................................................................2-28
2.6.10 Expanding Aggregated Links.............................................................................................................2-28
2.6.11 Adding a Virtual Topological Link....................................................................................................2-28
2.6.12 Deleting a Virtual Topological Link..................................................................................................2-30
2.7 Adjusting the Network Topology..................................................................................................................2-30
2.7.1 Modifying the Submap Attributes........................................................................................................2-31
2.7.2 Deleting a Submap...............................................................................................................................2-31
2.7.3 Moving an Object.................................................................................................................................2-32
2.7.4 Copying an Object................................................................................................................................2-33
2.7.5 Deleting Objects in Batch....................................................................................................................2-33
2.7.6 Modifying the Device Attributes..........................................................................................................2-34
2.7.7 Deleting a Device.................................................................................................................................2-34
2.8 Refreshing the Topology View.....................................................................................................................2-35
2.9 Example of Setting Up a Network Topology................................................................................................2-35
2.10 Viewing the Topology Information.............................................................................................................2-36
ii

Issue 02 (2008-05-31)

Operation Guide
Contents
2.10.1 Modes of Viewing the Topology.......................................................................................................2-37

2.10.2 Setting the Filter Display....................................................................................................................2-38
2.10.3 Searching Topology Objects..............................................................................................................2-38
2.10.4 Viewing the Submap Information......................................................................................................2-40
2.10.5 Viewing the Device Information........................................................................................................2-40
2.10.6 Viewing the Link Information............................................................................................................2-41
2.10.7 Displaying Device Statistics Information..........................................................................................2-41
2.10.8 Setting the Layout of the Topology View..........................................................................................2-41
2.10.9 Viewing the Aerial View....................................................................................................................2-42
2.10.10 Adjusting the Topology View..........................................................................................................2-42
2.10.11 Setting the Full Screen Display........................................................................................................2-43
2.10.12 Printing the Topology View.............................................................................................................2-43
2.10.13 Returning to the Parent Topology View..........................................................................................2-44
2.10.14 Expanding or Collapsing Child Objects...........................................................................................2-44
2.10.15 Arranging Topology Objects............................................................................................................2-45
2.11 Setting a View.............................................................................................................................................2-45
2.11.1 Setting a View....................................................................................................................................2-46
2.11.2 Displaying the Navigation Tree.........................................................................................................2-46
2.11.3 Moving a View...................................................................................................................................2-46
2.11.4 Creating a Custom View....................................................................................................................2-47
2.11.5 Setting the Startup Submap................................................................................................................2-48
2.11.6 Locking a View..................................................................................................................................2-49
3 Alarm Management...................................................................................................................3-1
3.1 Getting to Know Alarm Management.............................................................................................................3-3
3.1.1 Alarm Management Interface.................................................................................................................3-3
3.1.2 Alarm Severities.....................................................................................................................................3-4
3.1.3 Alarm Status...........................................................................................................................................3-4
3.1.4 Alarm Types...........................................................................................................................................3-5
3.1.5 Alarm Reporting Procedure...................................................................................................................3-5
3.2 Managing the Alarm Template.......................................................................................................................3-7
3.2.1 Alarm Templates....................................................................................................................................3-7
3.2.2 Exporting or Importing an Alarm Template..........................................................................................3-7
3.2.3 Creating an Alarm or Event Browse Template......................................................................................3-8
3.2.4 Creating the Alarm Statistics Template...............................................................................................3-10
3.2.5 Setting the Startup Template................................................................................................................3-11
3.2.6 Saving an Alarm Template As a New One..........................................................................................3-12
3.3 Monitoring Network Alarms.........................................................................................................................3-13
3.3.1 Monitoring Alarms Through the Topology View................................................................................3-13
3.3.2 Monitoring Alarms Through the Alarm Panel.....................................................................................3-14
3.3.3 Locating an Alarm................................................................................................................................3-15
3.3.4 Collecting Statistics on Alarms............................................................................................................3-16
3.4 Browsing Alarms...........................................................................................................................................3-17
Issue 02 (2008-05-31)

iii
Contents

Operation Guide
3.4.1 Browsing Current Alarms....................................................................................................................3-17
3.4.2 Browsing History Alarms.....................................................................................................................3-19
3.4.3 Browsing Events..................................................................................................................................3-21
3.4.4 Browsing Correlative Alarms or Events..............................................................................................3-22
3.4.5 Example of Browsing the N2000 UMS Alarms...................................................................................3-23
3.4.6 Example of Browsing Performance Threshold Alarms.......................................................................3-23
3.4.7 Example of Browsing Environment Alarms........................................................................................3-24
3.5 Handling an Alarm........................................................................................................................................3-24

3.5.1 Fault Handling Procedure.....................................................................................................................3-25
3.5.2 Browsing Current Alarms....................................................................................................................3-27
3.5.3 Viewing the Alarm Details...................................................................................................................3-29
3.5.4 Acknowledging an Alarm....................................................................................................................3-30
3.5.5 Locating an Alarm................................................................................................................................3-31
3.5.6 Querying Device Maintenance Information.........................................................................................3-32
3.5.7 Clearing Alarms...................................................................................................................................3-33
3.5.8 Recording Alarm Maintenance Experiences........................................................................................3-34
3.5.9 Example of Alarm Handling................................................................................................................3-35
3.6 Setting the Alarm or Event Auto Processing................................................................................................3-36
3.6.1 Alarm Auto Processing........................................................................................................................3-37
3.6.2 Setting the Alarm Auto Acknowledgement.........................................................................................3-37
3.6.3 Setting Alarm Auto Synchronization...................................................................................................3-38
3.6.4 Redefining Alarms or Events...............................................................................................................3-39
3.6.5 Setting mask of the NE Alarms or Events............................................................................................3-40
3.6.6 Setting mask of the N2000 UMS Alarms or Events............................................................................3-41
3.6.7 Setting Postprocessing for Alarms or Events.......................................................................................3-42
3.7 Setting the Alarm Correlation Rule...............................................................................................................3-43
3.7.1 Correlation Rules..................................................................................................................................3-44
3.7.2 Setting the Alarm or Event Correlation Analysis.................................................................................3-44
3.7.3 Setting the Alarm or Event Frequency Analysis..................................................................................3-46
3.7.4 Setting the Intermittent Alarms or Repeat Events Analysis.................................................................3-47
3.7.5 Setting the Acknowledged and Uncleared Alarm Time Analysis........................................................3-48
3.7.6 Example of the Alarm or Event Correlation Analysis.........................................................................3-49
3.7.7 Example of Alarm or Event Frequency Analysis.................................................................................3-50
3.7.8 Example of the Intermittent Alarm or Repeat Event Analysis.............................................................3-51
3.7.9 Example of the Acknowledged and Uncleared Alarm Time Analysis................................................3-52
3.8 Setting Alarm Notification............................................................................................................................3-52
3.8.1 Alarm Notification Methods................................................................................................................3-53
3.8.2 Setting the Alarm Panel Style..............................................................................................................3-53
3.8.3 Setting the Alarm Box..........................................................................................................................3-54
3.8.4 Setting Alarm Sounds...........................................................................................................................3-55
3.8.5 Setting Alarm Colors............................................................................................................................3-56
3.8.6 Setting the Threshold for Uncleared Alarms........................................................................................3-57
iv

Issue 02 (2008-05-31)

Operation Guide
Contents
3.8.7 Setting the Client to Be Displayed on Top When an Alarm Is Received............................................3-57

3.9 Setting the Alarm Remote Notification.........................................................................................................3-58
3.9.1 Setting Communication Parameters for Alarm Remote Notification..................................................3-58
3.9.2 Setting the Notification Delay..............................................................................................................3-59
3.9.3 Setting a Remote Notification Rule.....................................................................................................3-59
3.10 Dumping Alarms or Events.........................................................................................................................3-60
3.10.1 Setting Auto Dump of Alarms...........................................................................................................3-60
3.10.2 Setting Auto Dump of Events............................................................................................................3-61
3.10.3 Dumping Alarms Manually................................................................................................................3-62
3.10.4 Dumping Events Manually.................................................................................................................3-63
3.11 Managing the Alarm Panel..........................................................................................................................3-64
3.11.1 Alarm Panel........................................................................................................................................3-65
3.11.2 Displaying the Alarm Panel...............................................................................................................3-65
3.11.3 Setting the Alarm Panel Style............................................................................................................3-66
3.12 Managing the Alarm Box............................................................................................................................3-67
3.12.1 Setting the Alarm Box........................................................................................................................3-67
3.12.2 Stopping the Alarm Sound.................................................................................................................3-68
3.12.3 Synchronizing the Alarm Box Data...................................................................................................3-69
4 Performance Management........................................................................................................4-1
4.1 Overview of the Performance Measurement...................................................................................................4-2
4.1.1 Basic Concepts.......................................................................................................................................4-2
4.1.2 Device Type Definition..........................................................................................................................4-5
4.1.3 Performance Measurement Principle of IMS Devices...........................................................................4-5
4.1.4 GUI of the Performance Measurement..................................................................................................4-6
4.2 Managing Performance Measurement Tasks..................................................................................................4-7
4.2.1 Task State...............................................................................................................................................4-8
4.2.2 Querying Performance Measurement Tasks..........................................................................................4-8
4.2.3 Querying the Measuring Object of the Performance Measurement Task..............................................4-9
4.3 Querying the Performance Data......................................................................................................................4-9
4.3.1 Querying the Performance Data by Time Segment..............................................................................4-10
4.3.2 Querying the Performance Data by User-Defined Condition..............................................................4-10
4.3.3 Querying the Maximum and Minimum Performance Values..............................................................4-12
4.3.4 Saving the Performance Data to a File.................................................................................................4-13
4.3.5 Printing the Performance Measurement Data......................................................................................4-14
4.4 Monitoring the Device Performance.............................................................................................................4-15
4.4.1 Flowchart for Monitoring the Device Performance.............................................................................4-16
4.4.2 Creating a Performance Threshold Template.......................................................................................4-16
4.4.3 Creating a Performance Threshold Record..........................................................................................4-19
4.5 Measuring the Performance Data..................................................................................................................4-21
4.5.1 Time Distribution Measurement..........................................................................................................4-21
4.5.2 Time Distribution Comparison Measurement......................................................................................4-23
4.5.3 Saving the Measurement Results to a File...........................................................................................4-24
Issue 02 (2008-05-31)

Contents

Operation Guide
4.5.4 Printing the Measurement Result.........................................................................................................4-24
4.6 Dumping the Performance Data....................................................................................................................4-25

4.6.1 Configuring the Default Condition for Automatically Dumping Performance Data...........................4-26
4.6.2 Configuring the User-Defined Condition for Automatically Dumping Performance Data.................4-27
4.6.3 Dumping Performance Data Immediately............................................................................................4-28
4.6.4 Configuring the Overflow Dump Condition for Performance Data.....................................................4-29
4.7 Configuring the Performance Northbound Interface.....................................................................................4-29
5 FAQ...............................................................................................................................................5-1
5.1 Topology Management................................................................................................................................... 5-2
5.1.1 Why Is the Aerial View Unclear or Exceptional?..................................................................................5-2
5.1.2 Why Do Devices Vanish After the Topology View Is Refreshed?........................................................5-2
5.1.3 Why Does the Resolution Change of OS Cause Client Display Exception?.........................................5-3
5.1.4 Why Aren't the New Objects Displayed in the Topology View?.......................................................... 5-3
5.1.5 The Northbound Interface Dialog Box Cannot Be Displayed............................................................... 5-4
5.1.6 Why Are the Objects in the Topology View Overlapped?.................................................................... 5-4
5.1.7 Why Is the Location of an Object Changed?......................................................................................... 5-4
5.1.8 Why Are Some Menu Items Gray and Unavailable?.............................................................................5-5
5.1.9 Why Are the Devices in the Physical Path Fewer than Those Found by Auto Discovery?...................5-5
5.2 Fault Management...........................................................................................................................................5-5
5.2.1 Why Does the Fault Service Fail to Start?.............................................................................................5-6
5.2.2 Why Are the Alarm Statistics Displayed on the Alarm Panel Incorrect?..............................................5-6
5.2.3 Why Cannot the Alarm Email Be Received?.........................................................................................5-7
5.2.4 Why Cannot Alarms Be Viewed on the N2000 UMS Client?...............................................................5-7
5.2.5 Why Are Cleared Alarms Displayed as Uncleared?..............................................................................5-7
5.2.6 Why Cannot Alarm/Event Postprocessing Be Executed?......................................................................5-8
A Acronyms and Abbreviations................................................................................................A-1

Index.................................................................................................................................................i-1
vi

Issue 02 (2008-05-31)

Operation Guide
Figures
Figures
Figure 1-1 Client GUI..........................................................................................................................................1-5
Figure 2-1 Main Interface for topology management..........................................................................................2-3
Figure 3-1 Alarm management interface..............................................................................................................3-3
Figure 3-2 Alarm status switching model............................................................................................................3-5
Figure 3-3 Alarm reporting procedure.................................................................................................................3-6
Figure 3-4 Fault handling procedure..................................................................................................................3-26
Figure 3-5 Alarm panel......................................................................................................................................3-65
Figure 4-1 Principle diagram of IMS device performance measurement............................................................4-6
Figure 4-2 GUI of the performance measurement...............................................................................................4-7
Figure 4-3 Flowchart for monitoring the device performance...........................................................................4-16
Issue 02 (2008-05-31)

vii

Operation Guide
Tables
Tables
Table 1-1 Tool button list (system/fault)..............................................................................................................1-5
Table 1-2 Tool button list (topology)...................................................................................................................1-6
Table 1-3 Shortcut keys........................................................................................................................................1-9
Table 2-1 Alarm status......................................................................................................................................... 2-5
Table 2-2 Running status......................................................................................................................................2-6
Table 2-3 Submap types.......................................................................................................................................2-6
Table 2-4 Node types............................................................................................................................................2-6
Table 2-5 Status legends of the topological link................................................................................................2-22
Table 3-1 Alarm severities................................................................................................................................... 3-4
Table 3-2 Fault handling procedure....................................................................................................................3-27
Table 3-3 Alarm auto processing policies..........................................................................................................3-37
Table 4-1 Measurement task state description..................................................................................................... 4-8
Issue 02 (2008-05-31)

ix

Operation Guide
About This Document
About This Document

Purpose
This document describes the operations that an operator can perform on the N2000 UMS.
Related Versions
The following table lists the product version related to this document.
Product Name
Version
N2000 UMS
V200R012
Intended Audience
The intended audiences of this document are:
l
Network monitoring engineers
System maintenance engineers
Organization
This document consists of the following chapters and is organized as follows.
Issue 02 (2008-05-31)
Chapter
Description
1 Getting Started
This section describes the graphical user interface

(GUI) of the N2000 UMS client, and how to log in to
or log out of the N2000 UMS through a client.
2 Topology Management
This section describes how to set up a topological

view, monitor device status, and manage the
topological view.
3 Alarm Management
This section describes how to configure an alarm

template, monitor device alarms, and process alarms.


Operation Guide
About This Document
Chapter
Description
4 Performance Management
This section describes the principles, functions, and

methods of performance measurement.
5 FAQ
This section describes the frequently asked questions

(FAQs) and troubleshooting methods.
A Acronyms and Abbreviations
This section lists the acronyms and abbreviations

used in this document.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol
Description
Indicates a hazard with a high level of risk which, if not
avoided, will result in death or serious injury.
DANGER
WARNING
CAUTION
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could cause equipment damage, data loss, and
performance degradation, or unexpected results.
NOTE
Provides additional information to emphasize or

supplement important points of the main text.
TIP
Indicates a tip that may help you solve a problem or save

you time.
General Conventions
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in boldface. For

example, log in as user root.
Italic
Book titles are in italics.
Courier New
Terminal display is in Courier New.

Issue 02 (2008-05-31)

Operation Guide
About This Document
Command Conventions
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italic.
[]
Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... }
Alternative items are grouped in braces and separated by

vertical bars. One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
GUI Conventions
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles are in

boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Keyboard Operation
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.
Mouse Operation
Issue 02 (2008-05-31)
Action
Description
Click
Select and release the primary mouse button without moving the pointer.


Operation Guide
About This Document
Action
Description
Double-click
Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag
Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2008-05-31)

Second release. The updates are as follows:
The links in the document are optimized.
Updates in Issue 01 (2008-01-05)

Initial commercial release.

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
Getting Started
About This Chapter

This section describes the client GUI of the N2000 UMS and the basic operations on the client.
1.1 Logging In to the N2000 UMS
To perform operations on the client, you must log in to the N2000 UMS first. This section
describes how to start a client on the Windows OS to log in to the N2000 UMS.
1.2 Changing the Current User Password
You can change the password of the current user. The new password takes effect on the next
login.
1.3 Getting to Know the Client GUI
Knowing the client GUI facilitates your operations on the client and saves time.
1.4 Setting Automatic Login
After you set automatic login, you need not enter the user name and password when you log in
to the N2000 UMS next time. When you start the client, you log in to the N2000 UMS. This
function applies to the users who use fixed clients to log in to the N2000 UMS frequently.
1.5 Changing the Login Server
By switching the login server, you can log in to another N2000 UMS server without exiting from
the current client.
1.6 Setting Client Display
You can customize the display effect and features of the N2000 UMS client as required.
1.7 Customizing the Client Time Format
You can customize the time format as required.
1.8 Locking the Client
When no operations are performed on the client, you can lock the client to prevent illegal
operations.
1.9 Unlocking the Client
When the client is locked, you can unlock it.
1.10 Querying Information on Client Components
This section describes how to query the information on the N2000 UMS client components.
Issue 02 (2008-05-31)

1-1
1 Getting Started

Operation Guide
1.11 Querying License Information

You can know the license usage by querying the license information.
1.12 Setting the Browser Path
Describe how to enable the performance browser on a client.
1.13 Logging Out of the Current Session
When you need to switch the login user, you can log out of the current session and then log in
to the N2000 UMS server as another user on the current client.
1.14 Exiting from the Client
When you do not need to operate the N2000 UMS, you can exit from and close the N2000
UMS client to ensure the N2000 UMS security.
1-2

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
1.1 Logging In to the N2000 UMS

To perform operations on the client, you must log in to the N2000 UMS first. This section
describes how to start a client on the Windows OS to log in to the N2000 UMS.
Prerequisite
On the Windows OS, the N2000 UMS client is installed.
Context
By default, the N2000 UMS administrator is admin, and the password is admin. When the
admin user logs in to the N2000 UMS for the first time, the user must change the password.
Procedure
Step 1 Choose Start > Programs > iManager N2000 > N2000 Client, or double-click
Step 2 Click ... next to Server Name.

Step 3 In the Server Setting dialog box, add, modify, or delete a server.
NOTE
Specify the following information about a server:

l
IP Address: The IP address of the server.
Port: The port number of the server. Adopt the default setting.
Mode: The security mode. You can select SSL or Common.
Server Name: The name of the server.
Step 4 In the Login dialog box, enter the user name and password, and select the N2000 UMS server.
Step 5 Click Login.
----End
Result
You log in to the N2000 UMS server. The main topology window of the N2000 UMS client is
displayed by default. The status bar displays the login user name, the login time, the login mode,
and the name and IP address of the N2000 UMS server.
1.2 Changing the Current User Password

You can change the password of the current user. The new password takes effect on the next
login.
Procedure
Step 1 Choose File > Change Password.
Issue 02 (2008-05-31)

1-3

Operation Guide
1 Getting Started
Step 2 In the Change Password dialog box, set Current Password, New Password, and Confirm
Password.
Step 3 Click OK.
----End
1.3 Getting to Know the Client GUI

Knowing the client GUI facilitates your operations on the client and saves time.
1.3.1 GUI
This section describes the graphic user interface (GUI) The N2000 UMS client.
1.3.2 Menu Bar
The menu bar is located under the window title of the client interface, providing menus of main
functions.
1.3.3 Toolbar
The toolbar is located under the menu bar on the client interface, providing the icons for common
operations and the minimized alarm panel.
1.3.4 Main Window
In the main window, the navigation tree is displayed in the left pane, and the topological view
in the right pane. This facilitates the object searching and locating.
1.3.5 Status Bar
The status bar is located at the bottom of the client GUI for status display and real-time refresh.
1.3.6 Shortcut Conventions on the Client GUI
The N2000 UMS client provides shortcuts for some operations. You can perform these
operations quickly by the shortcuts.
1.3.7 Shortcut Keys
The N2000 UMS client provides various shortcut keys. You can perform operations quickly by
using these shortcut keys.
1.3.1 GUI
This section describes the graphic user interface (GUI) The N2000 UMS client.
The client can run on the Windows OS.
Figure 1-1 shows the GUI of the N2000 UMS client.
1-4

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
Figure 1-1 Client GUI
1.3.2 Menu Bar

The menu bar is located under the window title of the client interface, providing menus of main
functions.
The menus are organized according to functions on the menu bar, such as File, View, Fault,
Performance, Edit, System, Window, and Help. The application window displays dynamic
menus so that you can perform any operation as required. The menu status varies with the login
user authority. This ensures the security control.
1.3.3 Toolbar
The toolbar is located under the menu bar on the client interface, providing the icons for common
operations and the minimized alarm panel.
Common tool buttons are displayed as icons on the left part of the toolbar, as listed in Table
1-1 and Table 1-2. The minimized alarm panel is displayed on the right part of the toolbar. This
helps you to monitor the current alarms in real time.
Table 1-1 Tool button list (system/fault)
Category
System
Issue 02 (2008-05-31)
Icon
Name
Description
Exit
Enables you to exit the N2000 UMS.
Lock System
Enables you to lock the terminal. After

locking the terminal, you need to re-enter the
login password to unlock it.

1-5

Operation Guide
1 Getting Started
Category
Icon
Fault
Name
Description
Log Out
Enables you to log out of the N2000 UMS.
Topology
Browser
Enables you to view the main interface of

topology management.
NMS User
Management

browsing real-time alarms.
Browse
Current Alarm

security management.
Stop the
Current Alarm
Sound
Enables you to stop the current sound of the

alarm panel.
Show Alarm
Panel
Enables you to view the alarm panel and the

details of all the alarms.
Critical alarms
Enables you to view the number of uncleared

critical alarms, the number of
unacknowledged critical alarms, and the
total number of critical alarms.
Major alarms

major alarms, the number of
unacknowledged major alarms, and the total
number of major alarms.
Minor alarms

minor alarms, the number of
unacknowledged minor alarms, and the total
number of minor alarms.
Warnings

warnings, the number of unacknowledged
warnings, and the total number of warnings.
New events
Enables you to view the number of new

events.
Table 1-2 Tool button list (topology)

Category
Topology
1-6
Icon
Name
Description
Up
Enables you to switch the current submap to

the parent map to display the topology of the
parent map.
Zoom out
Enables you to zoom out the current view to

80% of the original size.

Issue 02 (2008-05-31)

Operation Guide
Category
Issue 02 (2008-05-31)
Icon
1 Getting Started
Name
Description
Zoom in
Enables you to zoom in the current view to

1.2 times of the original size.
Zoom in
Partially
Enables you to zoom in the selected area.
Restore
Enables you to restore the original size of

the view.
Fit Window
Enables you to set the entire view to fit the

display window.
View Move
Enables you to adjust the position of the

view in the display window.
Object
Attributes
Enables you to view the attributes of

topological objects.
Search
Enables you to search for and locate devices,

boards, and ports by name in the topological
view.
Topology
Navigator
Enables you to view and hide the topology

navigation tree.
View
Navigator
Enables you to set whether to display the

view navigation tree on the panel of the
device navigation tree.
Filter Tree
and Legend
Enables you to filter the display categories

in the topological view.
Aerial
View
Enables you to browse the entire topological

view, and locate the area displayed in the
topological view.
Save the
Location of
the Current
Submap
Icons
Enables you to save the position of a submap

icon to the database after you move the
submap icon in the topological view.
Save the
Location of
All the
Current
Submap
Icons
Enables you to save the position of all

submap icons to the database after you move
the submap icons in the topological view.
Refresh
View
Enables you to refresh the topological data

and topological view.
Lock View
Enables you to lock all the topological

objects so that the objects cannot be moved.

1-7

Operation Guide
1 Getting Started
1.3.4 Main Window

In the main window, the navigation tree is displayed in the left pane, and the topological view
in the right pane. This facilitates the object searching and locating.
All the windows for fault management, performance measurement, and system management are
displayed as tab pages for convenient switchover. All views are displayed in sub-window mode.
1.3.5 Status Bar

The status bar is located at the bottom of the client GUI for status display and real-time refresh.
The following information is displayed on the status bar:
l
Login user: The name of the current login user.
Connection duration: The duration of the connection between the current client and the
server.
Login mode: The login mode which the server adopts. The options are single user mode
and multi-user mode.
Login server: The name and IP address of the server that the current client logs in.
Prompt: The result of the current operation.
Logo: The logo of Huawei Technologies Co., Ltd.
1.3.6 Shortcut Conventions on the Client GUI

For Menu
For any menu followed by an asterisk * (* represents a letter or number), you can press Alt+*
instead of choosing the menu.
For Drop-Down Menu

For any drop-down menu followed by an asterisk * and when the menu is expanded, you can
press * instead of choosing the menu.
For Button
1-8
For any button followed by an asterisk * (* represents a letter or number), you can press
Alt+* instead of clicking the button.
When a dialog box is open and the focus is on a button, this button is the default button. If
the focus is not on any button, OK is the default button.
When the focus is on a button, you can press Enter or space bar instead of clicking the
button.
If the focus is on a button that does not respond when you press Enter, then the effect is
the same when you press Enter or when you click the default button.
Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
For Drop-Down List

When the focus is on a drop-down list, you can press the down arrow key to expand the dropdown list. You can press the Up, Down arrow keys to switch between options in a drop-down
list, and press Enter to select the current option.
For Option Button

If the focus is on an option button, you can press the space bar to select the option button.
For Check Box

If the focus is on a check box, you can press the space bar to select or clear the check box.
For Navigation Tree

When the focus is on the navigation tree, you can move the Down arrow key or Up arrow key
to switch between the nodes in the tree. You can expand or collapse a node that contains child
nodes.
Switching Between Controls

When there are multiple controls in a window, dialog box, or tab, you can press Tab to switch
from one control to another, and press Shift+Tab to switch to the previous control.
Sorting of a List Box

In a list box, if a column heading contains the icon
, it indicates that you can click the field
of the column heading to sort the fields in the column. The icon
order and the icon
indicates sorting in ascending
indicates sorting in descending order.
Shortcuts
1.3.7 Shortcut Keys

The N2000 UMS client provides various shortcut keys. You can perform operations quickly by
using these shortcut keys.
Table 1-3 lists the shortcut keys provided by the N2000 UMS client.
Table 1-3 Shortcut keys
Issue 02 (2008-05-31)
Shortcut keys
Operation
F1
Open the Help
Esc
Close a dialog box
Ctrl+F
Find devices (the operation is valid in the topology

window)
1-9

Operation Guide
1 Getting Started
Shortcut keys
Operation
Ctrl+X
Cut a topology object (the operation is valid in the

topology window)
Ctrl+C
Copy a topology object (the operation is valid in the

topology window)
Ctrl+V
Paste a topology object (the operation is valid in the

topology window)
Ctrl+A
Select all the devices (the operation is valid in the

topology window)
F9
Refresh the view (the operation is valid in the topology

window)
Ctrl+Y
Set the device layout for the topology view (the

operation is valid in the topology window)
Ctrl+B
Set the background of a submap (the operation is valid

in the topology window)
F6
Return to the upper-level submap (the operation is

valid in the topology window)
F7
Return to the top submap (the operation is valid in the

topology window)
Ctrl+Tab
Switch between windows
Ctrl+Alt+U
Unlock a terminal
Alt+X
Exit from the client
Alt+O
End the current session
1.4 Setting Automatic Login

After you set automatic login, you need not enter the user name and password when you log in
to the N2000 UMS next time. When you start the client, you log in to the N2000 UMS. This
function applies to the users who use fixed clients to log in to the N2000 UMS frequently.
Context
If a client is set to automatic login, no dialog box is displayed during login.
Procedure
Step 1 Choose File > Preferences.
Step 2 In the Preferences dialog box, click the Automatic Login tab.
Step 3 Select Log in automatically. Set User Name and Password.
1-10

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
NOTE
If select Full-screen display after login, the client is displayed in full screen mode after login.
Step 4 Click OK.

----End
1.5 Changing the Login Server

By switching the login server, you can log in to another N2000 UMS server without exiting from
the current client.
Procedure
Step 1 Choose File > Change Login Server.
Step 2 In the Change Login Server dialog box, select the server you want to access, and then click
OK.
Step 3 In the Change Login User dialog box, enter User Name and Password, and then click OK.
----End
1.6 Setting Client Display

You can customize the display effect and features of the N2000 UMS client as required.
1.6.1 Setting the Window Title
You can set the title of a window.
1.6.2 Setting the Output Information
The N2000 UMS client provides an output window in the bottom of the client. This window
displays the prompts and responses that can affect the N2000 UMS or other clients. For example,
the initialization information upon a system start. The maintenance users can use this function.
1.6.3 Setting Topology Display Style
This section describes how to set the topology display style on the N2000 UMS client.
1.6.4 Setting Topology Features
You can set the topology features to define the alarms, flash effect of the status icons, and flash
effect of the node icons in the topology view.
1.6.5 Setting Alarm Colors
You can set the alarm colors displayed on the client.
1.6.6 Setting Alarm Local Display Properties
Issue 02 (2008-05-31)

1-11

Operation Guide
1 Getting Started
You can set the alarm local display properties to define the alarm display mode and effect on
the N2000 UMS client.
1.6.1 Setting the Window Title

You can set the title of a window.
Procedure
Step 2 In the Preferences dialog box, click the Main Frame Title tab.
Step 3 In Main Frame Title, enter the title you want to display.
Step 4 Click OK.
----End
Result
The title that you set is displayed. (You do not need to restart the client.)
1.6.2 Setting the Output Information

The N2000 UMS client provides an output window in the bottom of the client. This window
displays the prompts and responses that can affect the N2000 UMS or other clients. For example,
the initialization information upon a system start. The maintenance users can use this function.
Procedure
Step 2 In the Preferences dialog box, click the Output Window tab.
Step 3 In Output Window, set Maximum Output Lines for the output information. Select
Automatically scroll to the new message and Automatic dump as required.
Step 4 Click OK.
----End
1.6.3 Setting Topology Display Style

This section describes how to set the topology display style on the N2000 UMS client.
1-12

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
Procedure
Step 2 In the Preferences dialog box, click the Node Effect tab.
Step 3 In Node Icon, set the node icons in the topology view.
Step 4 In Node Border Color, set the border colors of the nodes in the topology view.
Step 5 In Node Label, set the node labels used in the topology view.
Step 6 In Link Line, set the width and display mode of the combined line in the topology view.
Step 7 In View Show Type Setting, set the number of the views that can be displayed.
Step 8 Click OK.
----End
1.6.4 Setting Topology Features

You can set the topology features to define the alarms, flash effect of the status icons, and flash
effect of the node icons in the topology view.
Procedure
Step 2 In the Preferences dialog box, click the View Effects tab.
Issue 02 (2008-05-31)

1-13

Operation Guide
1 Getting Started
Step 3 In Display Settings, set the alarm status displayed in the topology view.
Step 4 In Status Icon Blinking Effect, set the alarms that use flash icons in the topology view.
Step 5 In Node Icon Blinking Effect, set the nodes that use flash effect in the topology view.
Step 6 Click OK.
----End

Prerequisite
You must be an NMS user with the Fault Watcher authority or higher.
Procedure
Step 2 In the Preferences dialog box, click the Color tab.
Step 3 Set the colors for Critical Alarm, Major Alarm, Minor Alarm, and Warning as required.
Step 4 Click OK.
----End
1-14

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
1.6.6 Setting Alarm Local Display Properties

You can set the alarm local display properties to define the alarm display mode and effect on
the N2000 UMS client.
Procedure
Step 2 In the Preferences dialog box, click the Local Fault Settings tab.
Step 3 In the Local Fault Settings tab, set the alarm display mode and effect on the N2000 UMS as
required.
Step 4 Click OK.

----End
1.7 Customizing the Client Time Format

You can customize the time format as required.
1.7.1 Setting the Time Format
You can set the time format on the client as required.
1.7.2 Setting the Date Format
You can set the date format on the client as required.
1.7.1 Setting the Time Format

You can set the time format on the client as required.
Issue 02 (2008-05-31)

1-15

Operation Guide
1 Getting Started
Context
l
The format is displayed in the Time Setting text box in real time.
You need to restart the client to have the settings take effect after you change the time
format.
Procedure
Step 2 In the Preferences dialog box, click the Time tab.
Step 3 In the Time Settings group box, set the time format.
Step 4 Click OK.
Step 5 In the prompt, click OK.
----End
1.7.2 Setting the Date Format

You can set the date format on the client as required.
Context
l
The format is displayed in the Date Sample text box in real time.
You need to restart the client to have the settings take effect after you change the client
date format.
Procedure
Step 2 In the Preferences dialog box, click the Date tab.
1-16

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
Step 3 In the Date Settings group box, set the date format.
NOTE
Date separator: It can be "/", "-", or ".". The default is "/".
Date format: It can be "yyyy/MM/dd", "dd/MM/yyyy", and "MM/dd/yyyy". The default is "dd/MM/yyyy".
The date format after set is displayed in the Appearance Example.
Step 4 Click OK.

Step 5 In the prompt, click OK.
----End
1.8 Locking the Client

When no operations are performed on the client, you can lock the client to prevent illegal
operations.
1.8.1 Locking the Client Automatically
You can set the client to lock automatically when no operations are performed in a period, to
prevent illegal operations on the client.
1.8.2 Locking the Client Manually
When the client is not in use, you can lock the client manually to prevent illegal operations.
1.8.1 Locking the Client Automatically

You can set the client to lock automatically when no operations are performed in a period, to
prevent illegal operations on the client.
Procedure
Step 2 In the Preferences dialog box, click the Locking Interval tab.
Step 3 Select Automatically locked. In the minutes later, this client will be automatically locked
text box, enter the time to enable the lock time.
NOTE
Locking time ranges from 1 to 35000 minutes.
Clear the Automatically Locked check box to cancel client auto locking.
Step 4 Click OK.

----End
Issue 02 (2008-05-31)

1-17

Operation Guide
1 Getting Started
Result
If you set auto locking and do not perform any operations in the preset interval, the client is
locked automatically.
1.8.2 Locking the Client Manually

When the client is not in use, you can lock the client manually to prevent illegal operations.
Procedure
Choose File > Lock System.
----End
1.9 Unlocking the Client

When the client is locked, you can unlock it.
Prerequisite
The client is locked.
Procedure
Step 1 Press Ctrl+Alt+U.
Step 2 In the Unlock dialog box, enter the user password. Click OK.
NOTE
You can unlock the client using the admin account and password.
----End
Result
If the password is correct, the client is unlocked, and you can perform operations on it.
1.10 Querying Information on Client Components

This section describes how to query the information on the N2000 UMS client components.
Procedure
Step 1 Choose Help > About.
Step 2 In the About window, click the Component tab to view the information on the client
components.
----End
1.11 Querying License Information

You can know the license usage by querying the license information.
1-18

Issue 02 (2008-05-31)

Operation Guide
1 Getting Started
Context
When the N2000 UMS needs expansion or the license is to expire, apply for the license files
from Huawei Technologies Co., Ltd..
Procedure
Step 1 Choose Help > About.
Step 2 In the About dialog box, click the License tab to view the
license information.
----End
1.12 Setting the Browser Path

Describe how to enable the performance browser on a client.
Procedure
Step 1 Choose File > Preferences. In the Preferences dialog box, click the Browser Path tab.
Step 2 Click Browse. In the Open dialog box, select a file.
Step 3 Click OK.
----End
1.13 Logging Out of the Current Session

When you need to switch the login user, you can log out of the current session and then log in
to the N2000 UMS server as another user on the current client.
Procedure
Step 1 Choose File > Logout.
Step 2 In the Confirm dialog box, click OK.
----End
Result
After logout, the Login dialog box is displayed. You can log in to the N2000 UMS as another
user.
1.14 Exiting from the Client

When you do not need to operate the N2000 UMS, you can exit from and close the N2000
UMS client to ensure the N2000 UMS security.
Issue 02 (2008-05-31)

1-19

Operation Guide
1 Getting Started
Context
The N2000 UMS works in client/server mode. Exiting from the client does not affect the running
of the N2000 UMS server.
Procedure
Step 1 Choose File > Exit.
Step 2 In the Confirm dialog box, click OK.
----End
1-20

Issue 02 (2008-05-31)

Operation Guide
Topology Management
About This Chapter

This section describes how to create a topology view and monitor device status, both of which
help you easily manage the topology view.
2.1 Getting to Know Topology Management
Before you perform the topology management tasks, you need to know the basic knowledge
such as topology management functions, topology objects, and topology icons. This helps you
to set up the network topology.
2.2 Process of Construct the Network Topology
This section describes the recommended process of constructing the network topology.
2.3 Setting the Topology Background
You can set the geographical background for different submaps. You can know the geographical
position of a device from the background.
2.4 Setting Up a Physical Submap
In the N2000 UMS, you can set up physical submaps properly, and then allocate the devices that
are adjacent in position or similar in attribute to the same submap. Therefore, you can manage
the devices easily.
2.5 Adding Devices
After a physical submap is created, new devices need to be added to the N2000 UMS for network
expansion.
2.6 Topological Link Management
The N2000 UMS supports the automatic creation of the management topological links and
signaling topological links between ATCA devices, and the display of the management and
interworking relations between the devices.
2.7 Adjusting the Network Topology
When the network structure is changed, for example, when the position of a device or the status
of a link is changed, you need to adjust the topology view in the N2000 UMS.
2.8 Refreshing the Topology View
You can view the latest network topology status by refreshing the topology view according to
the latest topology data.
Issue 02 (2008-05-31)

2-1

Operation Guide
2.9 Example of Setting Up a Network Topology

This section provides an example on how to set up a network topology in the N2000 UMS.
2.10 Viewing the Topology Information
You can view the topology view in various modes to know the entire structure of the topology.
You can view the details of the topology objects, including the submap, device, and link.
2.11 Setting a View
The N2000 UMS provides multiple modes to set the view, including displaying the view
navigation tree, creating a custom view, and setting the startup submap. You can set the view to
manage the network topology conveniently.
2-2

Issue 02 (2008-05-31)

Operation Guide
2.1 Getting to Know Topology Management

Before you perform the topology management tasks, you need to know the basic knowledge
such as topology management functions, topology objects, and topology icons. This helps you
to set up the network topology.
2.1.1 Topology Management Interface
2.1.2 Topology Management Terms
2.1.3 Topology Legend
Different icons are used to represent objects such as the submap, node, and link, as well as the
status of the objects.
2.1.1 Topology Management Interface

Figure 2-1 shows the main interface for N2000 UMS topology management.
Figure 2-1 Main Interface for topology management
2.1.2 Topology Management Terms

The following lists the terms used in the topology management.
Topological Object
A topological object in the topological view maps a physical or logical entity in the network. A
topological object can be a submap, a device, or a link between devices.
Issue 02 (2008-05-31)

2-3

Operation Guide
Submap
On the N2000 UMS, you can divide a large network into several smaller networks by a certain
rule, such as by geographical area. This facilitates device management. Such small networks are
called submaps and are displayed as submap icons in the topological view.
Rack
A rack is a special kind of submap. A rack can contain several frames.
Device
A device can be classified into the physical device and the virtual device.
A physical device is used to mark a specific device. According to the protocol type, devices can
be divided into SNMP devices, MML devices, and XML devices.
A virtual device has some features of a device, but may not correspond to a specific device.
Link
A link is a map of the physical connection between two devices in the topology. The N2000
UMS links consist of virtual links and service links. A virtual link identifies the logical
connection between two managed objects. A service link identifies the physical connection
between two managed objects.
In the topological view, links are drawn according to the following rules:
l
Only one link is drawn between two devices no matter how many actual links occur between
the two devices in the same submap. You can double click the link for details.
If one link occurs between two devices in different submaps, a link is drawn between these
two submap icons in the topological view. If you want to query the details, right click the
topology node, and then select the Show Link Info tab.
If one link occurs between two low level devices of two submaps, a link is drawn between
the two submaps.
Topological View
On the N2000 UMS, the topological view includes the physical view and user-defined view.
The physical view is generated when the N2000 UMS is installed. In the physical view, the
topological structure is divided according to the geographic area or other rules. For a device or
a submap, several copies may exist in the physical view at a time.
The user-defined view is customized by users. You can select the desired device objects from
the physical view or other views, and create a view to reorganize the selected objects. Each user
can create up to five user-defined views.
Topological view is a map of managed communications network on the N2000 UMS. The
managed devices and links are displayed in the form of a tree and a diagram on the client
interface. In the topological view, you can perform configuration operations, alarm operations,
and performance operations.
In the N2000 UMS topological view, the navigation tree is displayed in the left pane, displaying
all topological objects (devices and submaps) and their levels. All the objects and the related
location of the current submap are displayed in the topological view in the right pane.
2-4

Issue 02 (2008-05-31)

Operation Guide
Running Status
The N2000 UMS queries device status and configuration data at intervals, and displays the status
in the topological view.
The running status can be:
l
Normal
Unknown
Offline/Separation
Alarm Status
The N2000 UMS displays the trap data that is reported by the faulty devices in the topological
view.
The alarms can be:
l
Critical alarm
Major alarm
Minor alarm
Warning
Locking View
If an object is locked, it means that:
l
In the topological view, you cannot move the object.
The object cannot be deployed automatically.
2.1.3 Topology Legend

Different icons are used to represent objects such as the submap, node, and link, as well as the
status of the objects.
For the submap, node, and link, the icons at the top left corner are used to represent their alarm
status, as shown in Table 2-1.
Table 2-1 Alarm status
Icon
Status
Uncleared critical alarm
Uncleared major alarm
Uncleared minor alarm
Uncleared warning
Unacknowledged critical alarm
Issue 02 (2008-05-31)

2-5

Operation Guide
Icon
Status
Unacknowledged major alarm
Unacknowledged minor alarm
Unacknowledged warning
For the submap, node, and link, different colors are used to represent their running status, as
shown in Table 2-2.
Table 2-2 Running status
Icon
Status
Normal
Unknown
Offline/Blocked
For the submap, different icons are used to represent the types of the submap, as shown in Table
2-3.
Table 2-3 Submap types
Icon
Type
Common Submap
For the node, different icons are used to represent the types of the node, as shown in Table
2-4.
Table 2-4 Node types
Icon
Type
3rd-Party-ICMP
3rd-Party-SNMP
3rd-Party-Router
3rd-Party-Switch
Dummy-Device
2-6

Issue 02 (2008-05-31)

Operation Guide
Icon
Type
Local NMS
Sun Workstation
Virtual node
Microsoft Windows
2.2 Process of Construct the Network Topology

This section describes the recommended process of constructing the network topology.
Proc
edur
e
Operation
Description
2.3 Setting the Topology

Background
Sets the background with the location information for

different Submap. Through the location information
contained in the background, you can know the
geographical location where the device is.
2.4 Setting Up a Physical

Submap
Constructs the physical Submap and puts the devices

with close geographical location and similar attributes
into the next Submap, to help the user manage.
2.5 Adding Devices
Adds these new devices to the topology view of the

N2000 UMS when new devices needed to be added in
case of expansion of the network.
2.7 Adjusting the

Network Topology
Adjusts the topology view in the N2000 UMS when the

structure of the network changes (for example, the
location or connection status of the device changes).
2.3 Setting the Topology Background

You can set the geographical background for different submaps. You can know the geographical
position of a device from the background.
Prerequisite
You must be an NMS user with the Topo Watcher authority or higher.
Context
l
Issue 02 (2008-05-31)
The background file supports the JPG and GIF formats. The background image must be
provided by Huawei Technologies Co., Ltd..
2-7

Operation Guide
l
The background image is saved on the local client. If the image file does not exist on the
client, the corresponding submap has no background.
Procedure
Step 1 Choose View > Set Background.
Step 2 In the Set Background dialog box, in the submap list, select the submap that you want to modify.
Click Select Background.
Step 3 In the Open dialog box, set the background image file, and then click Open.
Step 4 In the Set Background dialog box, click OK.
The selected image is set to the background of the submap.
----End
2.4 Setting Up a Physical Submap

In the N2000 UMS, you can set up physical submaps properly, and then allocate the devices that
are adjacent in position or similar in attribute to the same submap. Therefore, you can manage
the devices easily.
2.4.1 Designing a Topology
Before deploying devices in the topology view, you need to design the division method of the
submap. The physical topology should present the topology structure of the actual
communication network and help the routine maintenance.
2.4.2 Creating a Submap
In the N2000 UMS, a large network can be divided into several smaller networks according to
a specific rule (such as the geographical location) for the management purposes. In the topology,
2-8

Issue 02 (2008-05-31)

Operation Guide
such smaller networks are called submaps. This operation enables you to create submaps in the
topology view.
2.4.3 Adding Devices
New devices need to be added to the submap after the submap is created.
2.4.4 Creating a Link
A link is the mapping of a connection between devices. You can create a link in the topology
view.
2.4.1 Designing a Topology

Before deploying devices in the topology view, you need to design the division method of the
submap. The physical topology should present the topology structure of the actual
communication network and help the routine maintenance.
The topology management window consists of a navigation tree on the left and a topology view
on the right. The navigation tree displays all the topology objects and their hierarchical relations
in a tree, and the topology view displays all the topology objects and their positions on the
submap in a view.
When designing a topology, pay attention to the following points:
l
The hierarchies of the submap cannot exceed five. Too many hierarchies may make the
operations inconvenient.
Devices in each submap cannot exceed 300. If there are too many devices, the devices may
be overlapped, and this makes the device query difficult.
You can divide submaps in the following ways:

l
By region: the regions where the devices are located.
By device type: the types of the devices.
By IP segment: the IP addresses of the devices.
By owner: the owners of the devices.
2.4.2 Creating a Submap

In the N2000 UMS, a large network can be divided into several smaller networks according to
a specific rule (such as the geographical location) for the management purposes. In the topology,
such smaller networks are called submaps. This operation enables you to create submaps in the
topology view.
Prerequisite
You must be an NMS user with the Topo Operator authority or higher.
Context
l
The submap name cannot be null.
Typically, a submap cannot contain more than 20 submaps.
Procedure
Step 1 Choose File > New > Submap.
Issue 02 (2008-05-31)

2-9

Operation Guide
Step 2 In the Submap navigation tree, select the type of the submap that you want to add.
Step 3 Click the Properties tab. In Name, enter the name of the submap.
Step 4 Click
next to Parent Path. In the Choose Path to Parent Submap dialog box, set the path
of the new submap.
The path of the new submap is displayed in Path.
Step 5 Click
to set.
next to Background. In the Open dialog box, select the background file that you want
Step 6 Click
next to Position. Move the cursor on to the topology view, and then click the position
where you want to locate the new submap.
The coordinates for the submap are displayed in Position.
Step 7 Click the Select Object tab. Click
submap.
or
on the tab to select the object contained in
Step 8 In Remarks, enter the description for the new submap.

Step 9 In the Add Object dialog box, click OK.
----End
2.4.3 Adding Devices

New devices need to be added to the submap after the submap is created.
Devices of specified NE addresses or in a certain network segment can be added to the
submap automatically or manually. For details, see Adding Devices.
2-10

Issue 02 (2008-05-31)

Operation Guide
2.4.4 Creating a Link

A link is the mapping of a connection between devices. You can create a link in the topology
view.
Prerequisite
Context
l
You cannot create a link across views.
You cannot create a link between an object and its child object.
You cannot create a loop link, that is, a link cannot be created between an object and the
link itself or its duplicated node.
Procedure
Step 1 Choose File > New > Link.
Step 2 On the left of the Add Object dialog box, select the type of the link to be added.
Step 3 In Link Name, enter the link name.

Step 4 Click
next to Left Object and Right Object respectively, and then select the nodes from
the topology view or the navigation tree.
The paths of the two selected nodes are displayed in Left Object and Right Object.
next to Left Port and Right Port respectively. In the Select Port dialog
Step 5 Optional: Click
box, select the left and right ports of the link.
Issue 02 (2008-05-31)

2-11

Operation Guide
NOTE
Only when the left and right objects are not submaps, the left and right ports can be set.
Step 6 Set the line type, line width, and line direction of the link.
Step 7 In the Remarks text box, enter the description for the link.
Step 8 Click OK.
----End
2.5 Adding Devices

After a physical submap is created, new devices need to be added to the N2000 UMS for network
expansion.
2.5.1 Adding a Device
You can manage a device through the N2000 UMS only after it is added to the N2000 UMS.
This operation applies to the users who deploy new devices.
2.5.2 Adding Devices in Batch
By auto discovery, the N2000 UMS can search a specified IP network segment or a specified
device type and automatically add the found device to the topological view.
2.5.3 Adding Devices Periodically
When you set the time discovery policy, the N2000 UMS searches the specific IP network
segment and device type at the specific intervals based on the settings and adds the found devices
to the topology view.
2.5.4 Setting Device Maintenance Information
Device maintenance information consists of the device location information and maintenance
personnel information. In case a fault occurs in a device, you can contact the maintenance
personnel in time to handle the fault.
2.5.5 Setting the Maintenance Personnel Information
You can manage the maintenance personnel information. For example, you can add, modify, or
delete the maintenance personnel information.
2.5.1 Adding a Device

You can manage a device through the N2000 UMS only after it is added to the N2000 UMS.
This operation applies to the users who deploy new devices.
Prerequisite
Context
NOTE
2-12
When a device is added, mass data is loaded from the device, and this process takes a certain period (the
default timeout period is 180 seconds). During this period, the GUI does not respond to any other operations.
If the new device is not displayed in the topology view in a long period, refresh the view to check whether
the device is successfully added.

Issue 02 (2008-05-31)

Operation Guide
Procedure
Step 1 Choose File > New > Device.
Step 2 On the left of the Add Object dialog box, select the type of the device to be added.
Step 3 In the IP Address text box, enter the IP address.

Step 4 In the Device Name text box, enter the device name.
Step 5 Optional: In the Device Alias text box, enter the device alias.
Step 6 Click
next to Parent Path. In the Choose Path to Parent Submap dialog box, set the path
for the new device. The path of the new device is displayed in Path. Click OK.
Step 7 Click
next to Maintenance Info. In the Device Maintenance Info dialog box, set the
maintenance information on the device.
Step 8 Set the corresponding parameters according to the added device type.
next to Position. Move the cursor on to the topology view, and then click the position
Step 9 Click
you want locate the new device.
The coordinate of the clicked position is displayed in Position.
next to Time Zone and DST. In the Time Zone drop-down list, select the time zone
Step 10 Click
for the device.
NOTE
The time zone and DST for the N2000 UMS server are not set.
The DST is only set for the devices supporting the DST.
Issue 02 (2008-05-31)

2-13

Operation Guide
Step 11 Select DST. In the DST Rule drop-down list, select the time rule.
Step 12 In the DST Offset drop-down list, set the offset time, start time, and end time. Click OK.
NOTE
The DST is only set for the devices supporting the DST. Step 10 to Step 12 are operations for setting the
DST.
The offset time is calculated in hours and minutes. The value ranges from one minute to 23 hours and 59
minutes (11439 minutes). The DST span is from one month to 11 months.
Step 13 In the Remarks text box, enter the descriptions of the new device.
Step 14 Click OK.
----End
2.5.2 Adding Devices in Batch

By auto discovery, the N2000 UMS can search a specified IP network segment or a specified
device type and automatically add the found device to the topological view.
Prerequisite
Context
l
Auto discovery supports the SNMP and ICMP devices.
Only one client can use the auto discovery function at a time.
Auto discovery does not search existing devices. The More Information dialog box
indicates that these devices already exist.
Procedure
Step 1 Choose File > Auto discovery.
2-14

Issue 02 (2008-05-31)

Operation Guide
Step 2 In the Auto Discovery dialog box, in Device Type, select the device type.
Step 3 In Ping Times, select the times to ping the device.
Step 4 In Timeout(s), select the timeout period for the ping operation.
Step 5 In Layers, select the number of layers you want to search.
Step 6 Click Default SNMP Parameter. In the Set Default SNMP Parameters dialog box, select the
SNMP parameters template used for adapting the searched devices.
NOTE
By default, the SNMP default parameter template is used to adapt the searched devices.
Step 7 Select Name Device By IP. Then the name of a found device is its IP address.
Step 8 Click
next to Physical Path. In the Choose Path to Parent Submap dialog box, select the
target submap of the searched devices. The path of the target submap is displayed in Path. Click
OK.
Step 9 Click Add. In the IP Address Range dialog box, set the start IP address, end IP address, and
subnet mask of the searched device, and then click OK. A new IP address range is added to the
IP Address Range table.
The record lists the start IP addresses, end IP address, and subnet mask of the IP network segment
to be searched. If you want to select the IP address range to search the devices, select Enable.
Step 10 Click Filter to mask the IP addresses of the devices that you do not want to search.
Step 11 Click Next.
----End
Issue 02 (2008-05-31)

2-15

Operation Guide
2.5.3 Adding Devices Periodically

When you set the time discovery policy, the N2000 UMS searches the specific IP network
segment and device type at the specific intervals based on the settings and adds the found devices
to the topology view.
Prerequisite
You must be the NMS user admin.
Context
l
Only the admin user can set the time discovery policy.
The time discovery supports the SNMP and ICMP devices.
If you clear Enable time discovery, click OK, and save only the preset parameters, the
N2000 UMS does not perform the time discovery.
Procedure
Step 1 Choose File > Time Discovery.
Step 2 In the Time Discovery dialog box, in Device Type, select the device type.
Step 3 In Ping Times, select the times to ping the device.
Step 4 In Timeout(s), select the timeout for the ping operation.
Step 5 Click Default SNMP Parameters. In the Set Default SNMP Parameters dialog box, select
the SNMP parameters template used for adapting the searched devices.
2-16

Issue 02 (2008-05-31)

Operation Guide
Step 6 Select Name Device By IP. Then the name of the found device is its IP address.
Step 7 Click
next to Physical Path. In the Choose Path to Parent Submap dialog box, select the
target submap of the searched devices. The path of the target submap is displayed in Path. Click
OK.
Step 8 Click Add. In the IP Address Range dialog box, set the start IP address, end IP address, and
subnet mask of the found device, and then lick OK. A new IP address range is added to the IP
Address Range table.
NOTE
The record lists the start IP addresses, end IP address, and subnet mask of the IP network segment to be searched.
If you want to select the IP address range to search the devices, select Enable.
Step 9 Click Filter to mask the IP addresses of the devices that you do not want to search.
Step 10 In the Time Discovery dialog box, select Enable time discovery.
Step 11 Click OK to save the settings. The N2000 UMS searches the specific IP network segment and
device type at the specific intervals based on the settings.
----End
2.5.4 Setting Device Maintenance Information

Device maintenance information consists of the device location information and maintenance
personnel information. In case a fault occurs in a device, you can contact the maintenance
personnel in time to handle the fault.
Prerequisite
You must be an NMS user with the Topo Maintainer authority or higher.
Procedure
Step 1 Choose System > Device Maintenance Info.
Step 2 In the Device Maintenance Info window, click Display.
Issue 02 (2008-05-31)

2-17

Operation Guide
Step 3 In the dialog box, set the following information:

l
Location Info
In the Location Info group box, set the device location information.
Personnel Info
In the Personnel Info group box, select a maintenance person.
NOTE
If you want to add multiple maintenance persons for the device, click Personnel Info at the bottom. In
the Device Personnel Info dialog box, set the maintenance persons.
Step 4 Click OK.

----End
2.5.5 Setting the Maintenance Personnel Information

You can manage the maintenance personnel information. For example, you can add, modify, or
delete the maintenance personnel information.
Prerequisite
Context
You are not recommended to name a maintenance person All.
Procedure
Step 1 Choose System > Maintenance Personnel Information.
2-18

Issue 02 (2008-05-31)

Operation Guide
Step 2 In the Set Maintenance Personnel Information window, do as follows:

l
Add the maintenance personnel information.

Click Add. In the lower area, set the fields. Click OK. The new maintenance personnel
information is then displayed in the list.
Modify the maintenance personnel information.

In the list, double-click a record to modify the information. Then click Apply. The
information in the list is then updated.
Delete the maintenance personnel information.

In the list, select a record, and then click Delete. In the displayed dialog box, click Yes.
----End
2.6 Topological Link Management

The N2000 UMS supports the automatic creation of the management topological links and
signaling topological links between ATCA devices, and the display of the management and
interworking relations between the devices.
2.6.1 Classification of Topological Links
Topological links are classified into IMS management topological links, IMS Diameter
topological links, IMS SIP topological links, and virtual topological links.
2.6.2 Status Legends of the Topological Link
This section describes the status legends of the topological link.
2.6.3 Displaying Topological Links
This operation enables you to view the topological links in the topological view that you are
concerned about, including IMS management topological links, IMS Diameter topological links,
IMS SIP topological links, and virtual topological links. This facilitates the link status query and
monitoring.
Issue 02 (2008-05-31)

2-19

Operation Guide
2.6.4 Hiding Topological Links

This operation enables you to hide the topological links in the topological view that you are not
IMS SIP topological links, and virtual topological links.
2.6.5 Querying Attributes of a Topological Link
This operation enables you to query the link name, link type, line type, and port information of
a topological link, the Diameter signaling link data of an IMS Diameter topological link, or the
BGCF route data of an IMS SIP topological link in the topological view.
2.6.6 Modifying Basic Attributes of a Topological Link
This operation enables you to modify the basic attributes of a topological link, including link
name, link type, line width, and line direction, and supports remarks information about the
device.
2.6.7 Refreshing Topological Links
N2000 UMS supports the refreshing of topological links. The link alarm and status of devices
at both ends of the links drive the automatic refreshing of the links in real time. In addition, the
N2000 UMS provides the periodic polling mechanism to refresh the link status and link data in
the early morning of each day. You can also refresh the topological links manually to obtain the
latest link status at any time.
2.6.8 Synchronizing Topological Links from the ATCA Devices
This operation enables you to synchronize the link status and link data of topological links
(between the OMU and its managed ATCA devices or between the managed ATCA devices)
from the OMU to the N2000 UMS.
2.6.9 Aggregating Multiple Links
This operation enables you to aggregate excessive links between devices into one link when the
excessive links in the topological view prevents you from querying the key links.
2.6.10 Expanding Aggregated Links
This operation enables you to expand an aggregated link to multiple links when you need to
query the status and details of each link between two devices in the topological view.
2.6.11 Adding a Virtual Topological Link
This operation enables you to add a virtual topological link between two managed objects to
identify their logical connection relation.
2.6.12 Deleting a Virtual Topological Link
This operation enables you to delete a virtual topological link between two managed objects.
2.6.1 Classification of Topological Links

Topological links are classified into IMS management topological links, IMS Diameter
topological links, IMS SIP topological links, and virtual topological links.
This section describes the classification of the topological links based on the service types.
2.6.1.1 IMS Management Topological Link
The IMS management topological link indicates the management relation between the OMU
and the ATCA devices. After the ATCA devices are added, the N2000 UMS automatically adds
the management link between the OMU and the ATCA devices.
2.6.1.2 IMS Diameter Topological Link
The IMS Diameter topological link indicates the Diameter signaling link between the ATCA
devices, for example, between the CSC3300 and the RM9000, AIM6300, iCG9815, or
2-20

Issue 02 (2008-05-31)

Operation Guide
HSS9820, between the HSS9820 and the ATS9900, between the ATS9900 and the iCG9815,
and between the AIM6300 and the RM9000.
2.6.1.3 IMS SIP Topological Link
The IMS SIP topological link indicates the route (SIP link) between the CSC3300 devices in the
local domain or between the CSC3300 device in the local domain and the CSC3300 device in
another IMS domain.
2.6.1.4 Virtual Topological Link
The virtual topological link identifies the logical connection relation between two managed
objects, such as between two devices, between a submap and a device, and between two submaps.
The virtual topological link has only one state, that is, the normal state (green). In addition, this
state cannot be refreshed. A virtual topological link must be set up or deleted manually.
IMS Management Topological Link

The IMS management topological link indicates the management relation between the OMU
and the ATCA devices. After the ATCA devices are added, the N2000 UMS automatically adds
the management link between the OMU and the ATCA devices.
If the OMU or ATCA device node is moved to another submap, the N2000 UMS displays the
management topological link between the moved device node and the original submap. If there
are multiple IMS management topological links, the multiple links are displayed as an
aggregated link by default.
The IMS management topological link is shown in a dotted line. Generally, the IMS management
topological link is always in the normal state (green). When the devices at the both ends of the
link go offline, the IMS management topological link is refreshed to the unknown state (blue).
IMS Diameter Topological Link

The IMS Diameter topological link indicates the Diameter signaling link between the ATCA
devices, for example, between the CSC3300 and the RM9000, AIM6300, iCG9815, or
HSS9820, between the HSS9820 and the ATS9900, between the ATS9900 and the iCG9815,
and between the AIM6300 and the RM9000.
After the ATCA devices are added, the N2000 UMS synchronizes the Diameter signaling link
data, analyzes the devices at the both ends of the link based on the link data, and sets up the
topological link between the devices.
l
When there are multiple links between two ATCA devices, the multiple links are displayed
as an aggregated link on the N2000 UMS. The alarm status of the aggregated link depends
on the alarm with the highest priority of the aggregated link.
When both devices are configured with the link data to the peer end, the N2000 UMS sets
up only one IMS Diameter topological link.
When the device at either end is configured with the link data to the peer end, the N2000
UMS also sets up one IMS Diameter topological link. If the link that is set up cannot
function properly, the ATCA devices report an alarm, and the link is in faulty state.
The status of the IMS Diameter topological link is triggered by a link alarm.
If the devices at the both ends of the IMS Diameter topological link are offline, the link is
refreshed to the unknown state (blue); if an alarm is generated for the IMS Diameter topological
link, the link is refreshed to the faulty state (red).
Issue 02 (2008-05-31)

2-21

Operation Guide
IMS SIP Topological Link

The IMS SIP topological link indicates the route (SIP link) between the CSC3300 devices in the
local domain or between the CSC3300 device in the local domain and the CSC3300 device in
another IMS domain.
After the ATCA devices are added, the N2000 UMS synchronizes the route data from the
CSC3300 device, analyzes the CSC3300 device at the peer end based on the route data, and sets
up the IMS SIP topological link between the CSC3300 devices.
l
When a CSC3300 device at either end is configured with the route data, the N2000 UMS
sets up one IMS SIP topological link.
When the CSC3300 devices at the both ends are configured with the route data, the N2000
UMS sets up two IMS SIP topological links that are displayed as an aggregated link on the
N2000 UMS.
The IMS SIP topological link is shown in a dotted line. Generally, the IMS SIP topological link
is always in the normal state (green). When the devices at the both ends of the link go offline,
the IMS SIP topological link is refreshed to the unknown state (blue).
Virtual Topological Link

The virtual topological link identifies the logical connection relation between two managed
objects, such as between two devices, between a submap and a device, and between two submaps.
The virtual topological link has only one state, that is, the normal state (green). In addition, this
state cannot be refreshed. A virtual topological link must be set up or deleted manually.
When the current topological link type cannot meet the requirement, or the topological link
cannot be displayed because the service is not implemented in the planning stage of the network
operating, you can add the virtual topological link to identify the logical connection relation
between the devices.
2.6.2 Status Legends of the Topological Link

This section describes the status legends of the topological link.
Table 2-5 describes the status legends of the topological link.
NOTE
Table 2-5 describes only the colors of the links in the different states and the corresponding default line
type. You can set the line type of a topological link according to requirements. For details, see 2.6.6
Modifying Basic Attributes of a Topological Link.
Table 2-5 Status legends of the topological link

Legend
Status
Line Type
IMS management topological link

Normal
By default, the link is shown in a

dotted line.
Unknown

dotted line.
IMS Diameter topological link

2-22

Issue 02 (2008-05-31)

Operation Guide
Legend
Status
Line Type
Normal
By default, the link is shown in a solid

line.
Faulty

line.
Unknown

line.
Normal

dotted line.
Unknown

dotted line.
Normal

line.
IMS SIP topological link
Virtual topological link
2.6.3 Displaying Topological Links

This operation enables you to view the topological links in the topological view that you are
IMS SIP topological links, and virtual topological links. This facilitates the link status query and
monitoring.
Procedure
Step 1 Click the Filter tab in the Main Topology tabbed page.
NOTE
By default, the Filter tab is displayed in the Main Topology tabbed page. If the Filter tab is not displayed,
choose View > Display > Filter Tree and Legend from the main menu.
Step 2 Unfold the Link Type node, and select the link type to be displayed, as shown in the following
figure.
Issue 02 (2008-05-31)

2-23

Operation Guide
----End
2.6.4 Hiding Topological Links

This operation enables you to hide the topological links in the topological view that you are not
IMS SIP topological links, and virtual topological links.
Procedure
Step 1 Click the Filter tab in the Main Topology tabbed page.
NOTE
By default, the Filter tab is displayed in the Main Topology tabbed page. If the Filter tab is not displayed,
choose View > Display > Filter Tree and Legend from the main menu.
Step 2 Unfold the Link Type node, and deselect the link type to be hidden, as shown in the following
figure.
2-24

Issue 02 (2008-05-31)

Operation Guide
----End
2.6.5 Querying Attributes of a Topological Link

This operation enables you to query the link name, link type, line type, and port information of
a topological link, the Diameter signaling link data of an IMS Diameter topological link, or the
BGCF route data of an IMS SIP topological link in the topological view.
Procedure
Step 1 Select a topological link from the topological view. Right-click, and choose Object
Attributes.
Step 2 In the dialog box that appears, query the basic attributes, port information, and extended
attributes, as shown in the following figure.
Issue 02 (2008-05-31)

2-25

Operation Guide
Step 3 Click OK.

----End
2.6.6 Modifying Basic Attributes of a Topological Link

This operation enables you to modify the basic attributes of a topological link, including link
name, link type, line width, and line direction, and supports remarks information about the
device.
Procedure
Step 1 Select a topological link from the topological view. Right-click, and choose Object
Attributes.
Step 2 In the dialog box that appears, click the Property tab.
Step 3 In the Link Name text box, modify the link name; in the Line Type, Line Width, and Line
Direction drop-down lists, select the corresponding values; in the Remarks text box, input the
remarks.
Step 4 Click OK.
----End
2.6.7 Refreshing Topological Links

N2000 UMS supports the refreshing of topological links. The link alarm and status of devices
at both ends of the links drive the automatic refreshing of the links in real time. In addition, the
N2000 UMS provides the periodic polling mechanism to refresh the link status and link data in
2-26

Issue 02 (2008-05-31)

Operation Guide
the early morning of each day. You can also refresh the topological links manually to obtain the
latest link status at any time.
2.6.7.1 Refreshing a Single/an Aggregated Topological Link Manually
This operation enables you to refresh a single/an aggregated topological link manually to obtain
the latest link status.
Refreshing a Single/an Aggregated Topological Link Manually

This operation enables you to refresh a single/an aggregated topological link manually to obtain
the latest link status.
Context
N2000 UMS supports the manually refreshing of a topological link. It also supports the
automatically refreshing of the topological link. The link alarm and status of devices at both
ends of the link drive the system to automatically refresh the link status in real time. In addition,
the N2000 UMS provides the periodic polling mechanism to refresh the link status and link data
at wee hours of each day.
Procedure
Select a topological link from the topological view. Right-click, and chooseRefresh Link
Status.
CAUTION
l
You can manually refresh only the IMS Diameter topological links.
You can manually refresh only the aggregated links of the IMS Diameter topological links.
Only the IMS Diameter topological links are refreshed.
----End
2.6.8 Synchronizing Topological Links from the ATCA Devices

This operation enables you to synchronize the link status and link data of topological links
(between the OMU and its managed ATCA devices or between the managed ATCA devices)
from the OMU to the N2000 UMS.
Procedure
Step 1 Select an ATCA device node from the topological view. Right-click, and choose Synchronize
NE Data > Synchronize Link .
Issue 02 (2008-05-31)

2-27

Operation Guide
CAUTION
l
If you select the OMU device node, the link data and link status of all topological links
between the OMU and its managed ATCA devices and all topological links between the
managed devices are synchronized.
If you select a managed ATCA device node, the topological link data and link status of the
selected ATCA device is synchronized.
Step 2 In the prompt box that appears, click OK.

----End
2.6.9 Aggregating Multiple Links

This operation enables you to aggregate excessive links between devices into one link when the
excessive links in the topological view prevents you from querying the key links.
Procedure
Select one link from the excessive links between two devices in the topological view. Rightclick, and choose Collapse, or click on the topological link.
----End
Result
The multiple links between the two devices are aggregated to one link.
2.6.10 Expanding Aggregated Links

This operation enables you to expand an aggregated link to multiple links when you need to
query the status and details of each link between two devices in the topological view.
Procedure
Select an aggregated link from the topological view. Right-click, and choose Expand, or click
on the topological link.
----End
Result
The aggregated link is expanded to multiple single links.
2.6.11 Adding a Virtual Topological Link

This operation enables you to add a virtual topological link between two managed objects to
identify their logical connection relation.
2-28

Issue 02 (2008-05-31)

Operation Guide
Procedure
Step 1 Choose File > New > Link from the main menu, or in the topological view, right-click, and
choose New > Link.
Step 2 In the dialog box that appears, input the name of the virtual topological link in the Link
Name text box.
Step 3 Click
on the right of the Left Object text box, move the cursor of the mouse to the topological
view, and select the object on which the virtual link needs to be created.
on the right of the Right Object text box, move the cursor of the mouse to the
Step 4 Click
topological view, and select the object on which the virtual link needs to be created.
next to the Left Port text box. In the dialog box that appears, select the left port of the
Step 5 Click
virtual topological link.
NOTE
Skip this step if the left port of the virtual topological link is not required.
Step 6 Click
next to the Right Port text box. In the dialog box that appears, select the right port of
the virtual topological link.
NOTE
Skip this step if the right port of the virtual topological link is not required.
Step 7 Set the line type, width, and direction, as shown in the following figure.
NOTE
Skip this step if you use the default values of the line type, width, and direction.
Step 8 Click OK.

Issue 02 (2008-05-31)

2-29

Operation Guide
Step 9 In the prompt box that appears, click OK.

----End
2.6.12 Deleting a Virtual Topological Link

This operation enables you to delete a virtual topological link between two managed objects.
Procedure
Step 1 Select a virtual topological link to be deleted from the topological view. Right-click, and
chooseObject Attributes.
Step 2 In the dialog box that appears, select the virtual topological link to be deleted from the Link tab,
as shown in the following figure.
Step 3 Click Delete.

Step 4 In the dialog box that appears, click Yes.
Step 5 Click OK to close the Object Attributes dialog box.
----End
2.7 Adjusting the Network Topology

When the network structure is changed, for example, when the position of a device or the status
of a link is changed, you need to adjust the topology view in the N2000 UMS.
2-30

Issue 02 (2008-05-31)

Operation Guide
2.7.1 Modifying the Submap Attributes

You can modify the attributes such as the name, icon size, icon style, and description of a
submap in the topology.
2.7.2 Deleting a Submap
When you adjust the network topology structure, you can delete the submaps that are no longer
needed from the topology.
2.7.3 Moving an Object
In the current view, you can move a device or a submap to another submap.
2.7.4 Copying an Object
You can copy a device node from one submap to another.
2.7.5 Deleting Objects in Batch
You can perform this operation to delete multiple devices, submaps, or links in the topology
navigation tree or the topology view.
2.7.6 Modifying the Device Attributes
You can modify the attributes such as the device name, node alias, icon size, icon style, and
description of a device in the topology view.
2.7.7 Deleting a Device
When a device needs to be removed from the network, you need to delete it from the topology
view.
2.7.1 Modifying the Submap Attributes

You can modify the attributes such as the name, icon size, icon style, and description of a
submap in the topology.
Prerequisite
Procedure
Step 1 Select a submap from the navigation tree or the topology view.
NOTE
To select multiple submaps at a time, press and hold Ctrl or Shift in the navigation tree, or press and hold
Shift in the topology view, and then select submaps.
Step 2 Choose File > Object Attributes.

Step 3 In the Object Attributes dialog box, on the Submap tab, select a record from the attributes list.
The details of the record are displayed in the parameter configuration window.
Step 4 Modify the attributes, such as the submap name, icon size, icon style, and description.
Step 5 Click OK.
----End
2.7.2 Deleting a Submap

When you adjust the network topology structure, you can delete the submaps that are no longer
needed from the topology.
Issue 02 (2008-05-31)

2-31

Operation Guide
Prerequisite
Context
When a submap is deleted, the links related to the submap are also deleted.
Procedure
NOTE
To select multiple submaps, press and hold Ctrl or Shift in the navigation tree, or press and hold Shift in the
topology view, and then select submaps.
Step 2 Choose File > Delete > Delete From This Submap.
NOTE
You can also press Delete after selecting the submap in the topology view.
Step 3 In the Confirm dialog box, click Yes.

The submap is deleted, and the corresponding icon is deleted from the topology view.
The objects in the non-empty submap are expanded in the path of the submap.
Step 4 In the Delete Object Results dialog box, click Close.
----End
2.7.3 Moving an Object

In the current view, you can move a device or a submap to another submap.
Prerequisite
Context
l
When you cut and paste an object, the object is copied to the destination submap and deleted
from the source submap.
You cannot paste the same device or submap to a submap.
You cannot copy a submap, but you can cut and paste it.
Procedure
Step 1 In the topology view, switch to the source submap of the object you want to copy. Click the
object.
Step 2 Choose Eidt > Cut to copy the object to the clipboard.
Step 3 Switch to the destination submap. Choose Edit > Paste to paste the object in the submap.
----End
2-32

Issue 02 (2008-05-31)

Operation Guide
2.7.4 Copying an Object

You can copy a device node from one submap to another.
Prerequisite
Context
l
You cannot paste the same device or submap to the destination submap.
You can press and hold Shift to select two or more objects. You can copy and paste multiple
objects at a time.
You cannot copy a submap, but you can cut and paste it.
Procedure
Step 1 In the topology view, go to the source submap of the object that you want to copy. Click the
object.
Step 2 Choose Edit > Copy to copy the object to the clipboard.
Step 3 Go to the destination submap. Choose Edit > Paste to paste the object in the submap.
----End
2.7.5 Deleting Objects in Batch

You can perform this operation to delete multiple devices, submaps, or links in the topology
navigation tree or the topology view.
Prerequisite
Context
You cannot delete the non-empty submaps.
Procedure
Step 1 In the topology view or the navigation tree, select the topology object you want to delete.
NOTE
To choose multiple devices or submaps, press and hold Ctrl or Shift in the navigation tree, or press and
hold Shift in the topology view.
To choose multiple links, press and hold Shift in the topology view.
Step 2 Choose File > Delete > Delete from This Submap or press Delete.
Issue 02 (2008-05-31)

2-33

Operation Guide
If the operation is successful, the devices, submaps, and their links are deleted from the
navigation tree and the topology view.
----End
2.7.6 Modifying the Device Attributes

You can modify the attributes such as the device name, node alias, icon size, icon style, and
description of a device in the topology view.
Prerequisite
Procedure
Step 1 Select a device from the navigation tree or the topology view.
NOTE
To select multiple devices, press and hold Ctrl or Shift in the navigation tree, or press and hold Shift in the
topology view, and then select devices.
Step 2 Choose File > Object Attributes or right-click an object and choose Object Attributes .
Step 3 In the Object Attributes dialog box, on the Node tab, in the node property list, select a record.
The details of the record are displayed in the parameter configuration window.
Step 4 Modify Name, Node Alias, Icon Size or Icon Style, Remarks.
Step 5 Click OK.
----End
2.7.7 Deleting a Device

When a device needs to be removed from the network, you need to delete it from the topology
view.
Prerequisite
Context
l
If all the nodes of the device are deleted, the device is deleted.
If a node is deleted, the links related to the node are also deleted.
Procedure
Step 1 Select a node from the navigation tree or the topology view.
NOTE
To select multiple nodes, press and hold Ctrl or Shift in the navigation tree, or press Shift in the topology view,
and then select the nodes.
Step 2 Choose File > Delete > Delete from This Submap.
2-34

Issue 02 (2008-05-31)

Operation Guide
NOTE
You can also press Delete after selecting the device in the topology view.

----End
2.8 Refreshing the Topology View

You can view the latest network topology status by refreshing the topology view according to
the latest topology data.
Procedure
Choose View > Refresh View or click
on the toolbar.
----End
2.9 Example of Setting Up a Network Topology

This section provides an example on how to set up a network topology in the N2000 UMS.
Background
Suppose your office needs to add some devices because of the fast growing of service. You need
to add these devices to the N2000 UMS network topology so that you can manage these devices
through the N2000 UMS.
Operations
To add the new devices to the N2000 UMS network topology, do as follows:
1.
Create a submap.
(1) Right-click the topology view and choose New > Submap.
(2) In the Submap navigation tree, select the type of the submap.
(3) Click the Properties tab. In the dialog box, set the basic properties of the submap.
(4) Click the Select Object tab and click
the submap.
or
to select the object contained in
(5) Click OK.

2.
Create a device.
(1) Double-click the submap created in Step 1.
(2) Right-click the submap and choose New > Device.
(3) In the Add Object dialog box, set the IP address, device name, path of the parent
submap, maintenance information, and position.
(4) Click OK. The created device is displayed in the current view.
Issue 02 (2008-05-31)

2-35

Operation Guide
(5) Repeat Step 2 to Step 4 to create other devices.

3.
Adjust the device position.

(1) Select a device from the topology view, and then drag the device.
(2) On the topology toolbar, click
4.
to save the device position.
Create a link.
(1) Right-click the topology view and choose New > Link.
(2) In the Add Object dialog box, set the link name, left and right objects, left and right
ports, line type, line width, and line direction.
(3) Click OK.
5.
Create a custom view.

(1) Choose File > New > View.
(2) In the Create View dialog box, click the General tab.
(3) On the General tab, set the name and background.
(4) Click Select Object. In the topology view or topology navigation tree, right-click an
object and choose Select. Click Finish.
(5) In the Create View dialog box, click OK.
2.10 Viewing the Topology Information

You can view the topology view in various modes to know the entire structure of the topology.
You can view the details of the topology objects, including the submap, device, and link.
2.10.1 Modes of Viewing the Topology
on the right. You can view the topology through the navigation tree or the topology view.
2.10.2 Setting the Filter Display
The topology view displays objects such as submaps, links, and device nodes. When multiple
objects are displayed in the topology view, the topology view looks crowded. You can set the
filter display and reserve only the objects that you are concerned about in the topology view.
2.10.3 Searching Topology Objects
This operation enables you to find a topology object such as the device, board, submap, or port
quickly.
2.10.4 Viewing the Submap Information
You can view the details of a submap, including the submap name, icon style, icon size, alarm
status, coordinates, and remarks.
2.10.5 Viewing the Device Information
You can view the details such as the device name, icon size, and maintenance information of a
device.
2.10.6 Viewing the Link Information
You can view the details such as the basic properties, port information, and extended properties
of a link.
2.10.7 Displaying Device Statistics Information
2-36

Issue 02 (2008-05-31)

Operation Guide
You can know the device type and quantity in the current submap by displaying device statistics
information.
2.10.8 Setting the Layout of the Topology View
You can set the layout of the topology view to arrange the topology objects based on the settings.
2.10.9 Viewing the Aerial View
If the topology window displays only a part of the topology view, you can use the aerial view
to browse the entire view or locate the display area of the topology window.
2.10.10 Adjusting the Topology View
You can adjust the topology view as required, including zooming out, zooming in, zooming in
partially, fitting window, restoring, and displaying the view in full screen mode.
2.10.11 Setting the Full Screen Display
If you set the full screen mode, you can view the topology view in full screen mode.
2.10.12 Printing the Topology View
You can print the topology view. You can preview the topology view before printing or print
the view directly.
2.10.13 Returning to the Parent Topology View
This operation allows you to switch between the parent and child submaps to browse all the
paths of the topology view.
2.10.14 Expanding or Collapsing Child Objects
You can expand or collapse the child topology objects in the navigation tree to view the topology
conveniently.
2.10.15 Arranging Topology Objects
You can tile or cascade the nodes of the device navigation tree. You can also sort them in
ascending or descending order.
2.10.1 Modes of Viewing the Topology

on the right. You can view the topology through the navigation tree or the topology view.
l
Through navigation tree:

The navigation tree displays the network hierarchy in a tree structure.
Through topology view:

The objects at a specific hierarchy are displayed in different coordinations in the
background map. You can view the object layout directly.
Issue 02 (2008-05-31)
In filter mode: Customize the filter tree template. When you view Filter Tree and
Legend, select the template to view the topology in filter mode.
In aerial view mode: View the entire current view, and locate the area of the topology
window to be displayed.
In setting layout mode: Select a layout mode provided by the N2000 UMS. The
submaps and nodes are arranged automatically.
In zoom mode: You can zoom out, zoom in, zoom in partially, fit window, restore the
view, and display the view in full screen mode.
In traversing mode: You can switch between each parent view and child view to know
the current topology structure and all the paths of the topology view better.
2-37

Operation Guide
2.10.2 Setting the Filter Display

The topology view displays objects such as submaps, links, and device nodes. When multiple
objects are displayed in the topology view, the topology view looks crowded. You can set the
filter display and reserve only the objects that you are concerned about in the topology view.
Prerequisite
Context
l
When the N2000 UMS is started, the filter condition is empty by default. All the topology
objects are displayed.
When you deselect a filter condition, the objects matching the condition are not displayed.
Procedure
Step 1 Choose View > Display > Filter Tree and Legend or click
on the toolbar.
The Filter/Legend panel is displayed on the right of the topology view.

Step 2 On the Filter/Legend panel, click the Filter tab.
Step 3 Click Filter Tree and select Switch. In the Switch Filter Tree dialog box, select the filter tree
template. Click Open.
Step 4 Click Other Conditions. Set Device Name, Link Name, or Submap Name.
Step 5 Click Filter. Only the topology objects that meet Other Conditions are displayed in the topology
view.
Step 6 Choose View > Display > Filter Tree and Legend again to close the Filter Tree and
Legend panel.
----End
2.10.3 Searching Topology Objects

This operation enables you to find a topology object such as the device, board, submap, or port
quickly.
2-38

Issue 02 (2008-05-31)

Operation Guide
Context
l
This operation applies to all the submaps in the topology view, not limited within the current
submaps.
You must have the right of object management.
If the keyword for search is the device name, dynamic fuzzy search is used. That is, when
you enter the search content, the result is displayed dynamically.
Links cannot be searched.
Procedure
Step 1 Choose Edit > Search or click
Step 2 In the Search dialog box, in Type, select the search type.
Step 3 In Mode, select the search mode.
Step 4 In Keyword, enter the keyword for search.
NOTE
Match whole word only and Match case are not selected by default.
Issue 02 (2008-05-31)

2-39

Operation Guide
Step 5 Click Search.

All the found records are displayed in Search Result.
Step 6 Select a record from the search result list, and then click Locate. You can also double-click a
record.
The object is located in the topology view and the navigation tree.
----End
2.10.4 Viewing the Submap Information

You can view the details of a submap, including the submap name, icon style, icon size, alarm
status, coordinates, and remarks.
Procedure
Step 2 Open the Object Attributes dialog box of the submap:
l
Choose File > Object Attributes.
Right-click a submap in the navigation tree or topology view and choose Object
Attributes.
Step 3 In the Object Attributes dialog box, on the Submap tab, in the Submap attributes list, select a
record to view the details of the submap.
NOTE
Press and hold shift to select multiple submaps for viewing.
----End
2.10.5 Viewing the Device Information

You can view the details such as the device name, icon size, and maintenance information of a
device.
Procedure
Step 1 Select a device in the topology view.
Step 2 Use either of the following methods to open the Object Attributes dialog box:
l
Right-click a device in the topology navigation tree or topology view and choose Object
Attributes .
Step 3 In the Object Attributes dialog box, on the Node tab, in the device attributes list, select a record
to view the detailed information on the device.
NOTE
If you want to select multiple devices at a time, in the device navigation tree, press and hold Ctrl or Shift, and
then select devices. You can also press and hold Shift in the topology view, and then select devices.
----End
2-40

Issue 02 (2008-05-31)

Operation Guide
2.10.6 Viewing the Link Information

You can view the details such as the basic properties, port information, and extended properties
of a link.
Procedure
Step 1 Select a link from the topology view.
Step 2 Open the Object Attributes dialog box of the link.
l
Right-click a link in the topology view and choose Object Attributes.
Step 3 In the Object Attributes dialog box, on the Link tab, select a record from the link attributes
list.
NOTE
Press and hold shift to select multiple links for viewing.
Step 4 Click the Property tab to view the link name, link type, and link status.
Step 5 Click the Port Info tab to view the information on the left and right ports of the link.
Step 6 Click the Extend Property tab to view the information on the extended properties.
----End
2.10.7 Displaying Device Statistics Information

You can know the device type and quantity in the current submap by displaying device statistics
information.
Procedure
Step 1 Choose View > Display > Device Statistics .
Step 2 Switch the submap or view. In the Device Statistics window, view the device type and quantity.
----End
2.10.8 Setting the Layout of the Topology View

You can set the layout of the topology view to arrange the topology objects based on the settings.
Issue 02 (2008-05-31)

2-41

Operation Guide
Procedure
Step 1 Choose View > Layout.
Step 2 In the Layout dialog box, in the Type drop-down list, select the layout type.
l
Select Spring. In the Layout dialog box, click OK.
Select Uniform Length. In the Layout dialog box, click OK.
Select Tree. In the Layout dialog box, click OK. In the Please Select Root Node dialog
box, set the root node.
Select Star. In the Offset text box, enter the distance between nodes. In the Layout dialog
box, click OK. In the Please Select Root Node dialog box, set the root node.
Select Ring. In the Offset text box, enter the distance between nodes. In the Layout dialog
box, click OK.
Select Grid. In the Width and Height text boxes, enter the width and height between nodes.
In the Layout dialog box, click OK.

----End
2.10.9 Viewing the Aerial View

If the topology window displays only a part of the topology view, you can use the aerial view
to browse the entire view or locate the display area of the topology window.
Procedure
Step 1 Choose View > Display > Aerial View or click
on the toolbar.
Step 2 In the Aerial View window, browse the full topology view.
Step 3 In the Aerial View window, drag the rectangle frame to change the display area of the current
topology view.
----End
2.10.10 Adjusting the Topology View

You can adjust the topology view as required, including zooming out, zooming in, zooming in
partially, fitting window, restoring, and displaying the view in full screen mode.
Context
You can adjust the topology view to one tenth of or ten times the original one in size.
Procedure
l
Choose View > Zoom > Zoom out or click
on the toolbar.
The current view is adjusted to eighty percent of the original one in size.
l
2-42
Choose View > Zoom > Zoom in or click
on the toolbar.

Issue 02 (2008-05-31)

Operation Guide
The current view is adjusted to 1.2 times the original one in size.
l
Choose View > Zoom > Zoom in Partially or click

on the toolbar. In the view, press
and hold the left mouse button and move the cursor to select a region.
The selected region is magnified.
Choose View > Zoom > Fit Window or click
on the toolbar.
The view is restored to the normal size.

l
Choose View > Zoom > Restore or click
on the toolbar.
The whole view is adjusted to a proper size.

l
Choose View > Full Screen Mode.

NOTE
When the topology view is displayed in full screen mode, you can do as follows to exit the full screen
mode:
1. Press Esc or right-click the topology view and choose Exit from Full Screen.
2. In the Input Password dialog box, enter the login password.
----End
2.10.11 Setting the Full Screen Display

If you set the full screen mode, you can view the topology view in full screen mode.
Prerequisite
Context
l
After the view is displayed in full screen mode, you can press Esc to exit the full screen
mode. You need to enter your password or the admin user name and password.
If Full Screen Mode is set, Full Screen Mode has the highest priority, and other functions
such as Popup Client on Alarm Reception are invalid.
Procedure
Step 1 Choose View > Full Screen Mode.
The topology is displayed in full screen mode.
Step 2 If you want to exit the full screen mode, right-click the view and choose Exit from full
screen .
Step 3 In the Input Password dialog box, enter the user name and password.
Step 4 Click OK.
----End
2.10.12 Printing the Topology View

You can print the topology view. You can preview the topology view before printing or print
the view directly.
Issue 02 (2008-05-31)

2-43

Operation Guide
Procedure
Step 1 Choose File > Print Preview.
Step 2 In the Print Preview dialog box, click Previous or Next to browse the topology view page by
page.
Step 3 Click Print. In the Print dialog box, set the parameters for print. Then click Print.
----End
2.10.13 Returning to the Parent Topology View

This operation allows you to switch between the parent and child submaps to browse all the
paths of the topology view.
Procedure
Step 1 In the topology view, double-click submap.
The topology view switches to the selected submap and displays the topology structure of the
submap.
Step 2 Choose View > Up or click
on the toolbar to switch to the parent submap.
The topology view switches to the parent submap of the current submap and displays the
topology structure of this parent submap.
----End
2.10.14 Expanding or Collapsing Child Objects

You can expand or collapse the child topology objects in the navigation tree to view the topology
conveniently.
Procedure
l
In Device Navigator, select a collapsed submap and click
on the toolbar.
Devices in the current submap are displayed.

l
Click
on the toolbar.
Devices in each submap are displayed.

l
In Device Navigator, select an expanded submap and click
on the toolbar.
Devices in the current submap are hidden.

l
Click
on the toolbar.
Devices in each submap are hidden.

----End
2-44

Issue 02 (2008-05-31)

Operation Guide
2.10.15 Arranging Topology Objects

You can tile or cascade the nodes of the device navigation tree. You can also sort them in
ascending or descending order.
Procedure
l
On the toolbar, click
. The device nodes are tiled.
. The device nodes are cascaded.
. The device nodes are sorted in ascending order.
NOTE
Click
again. The device nodes are arranged in the original order.
. The device nodes are sorted in descending order.
NOTE
Click
again. The device nodes are arranged in the original order.
----End
2.11 Setting a View

2.11.1 Setting a View
2.11.2 Displaying the Navigation Tree
According to the structure of the topology view, the navigation tree can be grouped into view
navigation tree and device navigation tree. You can set whether to display the view navigation
tree on the Device Navigator panel. The view navigation tree is displayed by default.
2.11.3 Moving a View
You can move a topology view by clicking the button and dragging the mouse.
2.11.4 Creating a Custom View
A physical view may contain many objects. It is difficult to find a specific object. If you are
concerned about only some devices and links, you can create a view to display the objects you
are concerned about.
2.11.5 Setting the Startup Submap
You can set the startup submap of the N2000 UMS.
2.11.6 Locking a View
You can lock a view. After a view is locked, all its topology nodes and the icons of the
submap can no longer be moved.
Issue 02 (2008-05-31)

2-45

Operation Guide


Procedure
Step 1 Choose View > Display > View Navigator. The view navigation tree is displayed on the Device
Navigator panel.
Step 2 Choose View > View Navigator again. The view navigation tree is not displayed on the Device
Navigator panel.
NOTE
Click
on the toolbar to open or close View Navigator.
----End

2-46

Issue 02 (2008-05-31)

Operation Guide
Procedure
Step 1 On the toolbar, click
Step 2 When the pointer turns hand-shaped, drag the mouse to the position as required.
Step 3 Click the right button of the mouse or press Esc to perform other operations.
NOTE
When the pointer is hand-shaped, you can only move the topology view.
----End

Prerequisite
Context
l
You can create up to five views.
When the selected two devices are connected with a link, the link is added to the Selected
Links table.
Custom views are user-based. Users can view only their own custom views.
Procedure
Step 1 Choose File > New > View.
Issue 02 (2008-05-31)

2-47

Operation Guide
Step 2 In the Create View dialog box, click the General tab.
Step 3 In Name, enter the view name.
next to Background text box. In the Open dialog box, set the background of the
Step 4 Click
custom view.
Step 5 Click Select Objects, and then move the cursor to the navigation tree or the topology view.
Right-click a device or a link and choose Select .
The selected submap, device, or link is displayed in the Select Object dialog box.
Step 6 In the Select Object dialog box, click Finish.
Step 7 In the Create View dialog box, on the Selected Nodes and Selected Links tabs, view the object
selected in the custom view.
Step 8 In the Create View dialog box, click OK.
----End
Result
Choose View > Display > View Navigator. The new view is displayed under Custom in the
navigation tree.

2-48

Issue 02 (2008-05-31)

Operation Guide
Prerequisite
Context
Setting the startup submap enables you to set the submap displayed when the N2000 UMS is
started.
Procedure
Step 1 Choose View > Set Startup Submap.
Step 2 In the Set Start Submap dialog box, set the startup Submap.
Step 3 Click OK.
----End
Result
The current view is set to the startup submap. It will be displayed when you log in to the N2000
UMS next time.

Prerequisite
Context
After a view is locked, the coordinates of an object can no longer be changed in the topology
view.
Procedure
Step 1 Choose View > Display > View Navigator.
Step 2 In View Navigator, double-click a view node to access the view.
Step 3 Choose View > Lock View, or click
on the toolbar to lock the view.
----End
Issue 02 (2008-05-31)

2-49

Operation Guide
3 Alarm Management
Alarm Management
About This Chapter

Alarm management is an important task for ensuring the proper running of the network and
devices. Alarm management involves monitoring network alarms, handling alarms, setting alarm
auto processing policies, and dumping alarm data.
3.1 Getting to Know Alarm Management
Alarm management involves many concepts, such as alarm status, alarm type, and alarm
correlation. Before you perform operations on alarms, you need to know the basic knowledge
on alarms.
3.2 Managing the Alarm Template
This section describes the concept of the alarm template and the operations on the alarm template.
You can perform the alarm browse and statistics operations through the alarm template.
3.3 Monitoring Network Alarms
In the N2000 UMS, you can monitor alarms through the topology view and the alarm panel.
You can also monitor the alarm status in the network by alarm browse and alarm statistics.
3.4 Browsing Alarms
The N2000 UMS supports alarm browse. You can set various browse conditions and browse
templates to quickly locate the alarms you are concerned about.
3.5 Handling an Alarm
When an alarm is raised, you need to take actions to handle it. You need to remove the network
fault or the device fault to recover the network or device to its normal state.
3.6 Setting the Alarm or Event Auto Processing
You do not need to handle all the alarms manually. You can set an auto processing policy to
enable the N2000 UMS to process the alarms that match the preset conditions. This helps to
improve the work efficiency.
3.7 Setting the Alarm Correlation Rule
You can filter some unnecessary alarms or modify the alarm severities to improve alarm
processing efficiency by setting alarm correlation rules. The N2000 UMS provides the
correlation analysis, alarm or event frequency analysis, intermittent alarm or repeat event
analysis, and acknowledged and uncleared alarm time analysis.
3.8 Setting Alarm Notification
Issue 02 (2008-05-31)

3-1
3 Alarm Management

Operation Guide
The N2000 UMS provides various methods of alarm notification, such as the alarm panel, alarm
box, email, and SMS. You can customize these methods to obtain the latest alarm information.
3.9 Setting the Alarm Remote Notification
By alarm remote notification, the N2000 UMS can notify the remote maintenance personnel of
a fault in time. You can set various filter conditions to send the notification of only the alarms
that you are concerned about. The alarms that are cleared within the preset delay interval are not
notified because they have no impact on the system. You can set the delay interval.
3.10 Dumping Alarms or Events
To ensure that the N2000 UMS works stably and effectively and that the database space is
sufficient, the alarms or events need to be dumped when the amount of the alarms or events
reaches a specified value. Alarm or event dump supports auto dump and manual dump.
3.11 Managing the Alarm Panel
The alarm panel monitors the alarms in the entire network in real time and displays statistics of
the alarms by alarm severity and status. The numbers of the uncleared alarms and
unacknowledged alarms of different severities are displayed on the alarm panel. When a new
alarm is reported, the statistics change accordingly.
3.12 Managing the Alarm Box
The common alarm box of the Huawei Technologies Co., Ltd. provides audio-visual alarms.
You can set the conditions for filtering alarms to the alarm box.
3-2

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
3.1 Getting to Know Alarm Management

Alarm management involves many concepts, such as alarm status, alarm type, and alarm
correlation. Before you perform operations on alarms, you need to know the basic knowledge
on alarms.
3.1.1 Alarm Management Interface
This section describes the main interface of the alarm management.
3.1.2 Alarm Severities
The alarm severity indicates the seriousness and the importance of an alarm. In the descending
order of severities, the N2000 UMS alarms can be classified into the following types: Critical,
Major, Minor, and Warning.
3.1.3 Alarm Status
An alarm can be acknowledged and cleared. There are four types of alarm status:
Ack&Uncleared, Ack&Uncleared, Unack&Uncleared, and Ack&Cleared.
3.1.4 Alarm Types
Based on the functionality, alarms can be classified into ten types.
3.1.5 Alarm Reporting Procedure
The alarm reporting procedure refers to the handling procedure between the fault occurrence
and alarm notification.
3.1.1 Alarm Management Interface

This section describes the main interface of the alarm management.
Figure 3-1 shows the main interface of the alarm management.
Figure 3-1 Alarm management interface
Issue 02 (2008-05-31)

3-3

Operation Guide
3 Alarm Management
In Figure 3-1, the upper pane displays Current Alarms, providing the alarm severity, alarm
name, and alarm sources. The lower left pane displays Alarm Details, providing the details of
the selected alarm. The lower right pane displays Handling Suggestion, providing the cause
and handling suggestions for the selected alarm.
3.1.2 Alarm Severities

The alarm severity indicates the seriousness and the importance of an alarm. In the descending
order of severities, the N2000 UMS alarms can be classified into the following types: Critical,
Major, Minor, and Warning.
Table 3-1 lists the alarm severities.
Table 3-1 Alarm severities
Alarm Severity
Description
Critical
A critical alarm indicates that a service affecting fault has

occurred and an immediate corrective action is required.
Major
A major alarm indicates that a service affecting fault has occurred

and an urgent corrective action is required.
Minor
A minor alarm indicates the existence of a non-service affecting

fault and that a corrective action should be taken in order to
prevent a more serious fault.
Warning
A warning alarm indicates the detection of a potential or

impending service affecting fault, before any significant effects
have been felt.
3.1.3 Alarm Status

An alarm can be acknowledged and cleared. There are four types of alarm status:
Ack&Uncleared, Ack&Uncleared, Unack&Uncleared, and Ack&Cleared.
1.
Conditions for switching alarm status

The switching of the alarm status is triggered by certain conditions. The following describes
the conditions for switching alarm status.
l
Acknowledge an alarm.
If an alarm is acknowledged, it is processed. By the alarm acknowledgement status, you
can identify whether an alarm is processed and then take proper measures.
Clear an alarm.
When the condition that causes a fault alarm is removed, the device recovers to its
normal state, and the device reports a cleared alarm to the N2000 UMS. The source
alarm is cleared. You can also clear an alarm manually.
2.
Alarm status
There are four types of alarm status: Ack&Uncleared, Ack&Uncleared,
Unack&Uncleared, and Ack&Cleared.
Figure 3-2 shows the alarm status switching model.
3-4

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Figure 3-2 Alarm status switching model
NOTE
The alarms in the Ack&Cleared state are called history alarms. The alarms in the other states are called
current alarms.
3.1.4 Alarm Types

Based on the functionality, alarms can be classified into ten types.
Alarm Type
Description
Power supply alarm
An alarm about the power supply.
Environment alarm
An alarm about the environment of the equipment room.
Signaling alarm
An alarm about the signaling system.
Relay alarm
An alarm about the relay system.
Hardware alarm
An alarm about a board device.
Software alarm
An alarm about software.
Running alarm
An alarm about system running.
Communication alarm
An alarm about the communication system.
Quality of service alarm
An alarm about QoS.
Processing error alarm
Alarms about other exceptions that are not described here.
3.1.5 Alarm Reporting Procedure

The alarm reporting procedure refers to the handling procedure between the fault occurrence
and alarm notification.
Flow Chart
Figure 3-3 shows the alarm reporting procedure.
Issue 02 (2008-05-31)

3-5

Operation Guide
3 Alarm Management
Figure 3-3 Alarm reporting procedure
Procedure
1.
Report NE alarms.
When an alarm is raised from an NE, the NE reports the alarm to the N2000 UMS through
MML or SNMP.
2.
Mask alarms.
The N2000 UMS discards the masked alarms based on the preset conditions.
3.
Redefine alarms.
The N2000 UMS redefines the alarms based on the preset conditions. Alarm redefinition
involves the redefinition of the alarm name, type, and severity.
4.
Analyze alarm correlations.

The N2000 UMS analyzes the alarm correlations based on the correlation rules.
5.
Save alarm information.

The N2000 UMS records the processed alarm into the alarm database.
6.
3-6
Send alarm notification.

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
The N2000 UMS sends an alarm notification based on the preset conditions.
7.
Perform postprocessing of alarms.

The N2000 UMS runs the specified operation commands to handle the specific alarms.
3.2 Managing the Alarm Template

This section describes the concept of the alarm template and the operations on the alarm template.
You can perform the alarm browse and statistics operations through the alarm template.
3.2.1 Alarm Templates
An alarm template consists of the alarm browse conditions or alarm statistical conditions. You
can set typical alarm browse conditions or statistical conditions to templates to avoid repetitively
filter condition setting. You can use the alarm templates to quickly browse alarms or collect
statistics on alarms.
3.2.2 Exporting or Importing an Alarm Template
You can export an alarm template so that you can directly import the template when you use it
next time. Therefore, the template becomes portable.
3.2.3 Creating an Alarm or Event Browse Template
Alarm or event browse conditions are complicated. To prevent setting conditions repeatedly,
you can save the preset conditions as a template. You can use the template to browse the alarms
or events conveniently.
3.2.4 Creating the Alarm Statistics Template
Alarm statistical conditions are complicated. To prevent setting conditions repeatedly, you can
save the preset conditions as a template. When an alarm statistics template is set, you can doubleclick the template to collect statistics on the alarms.
3.2.5 Setting the Startup Template
You can set the startup template for the Current Alarms, History Alarms, Events, or Alarm
Statistics window. After you select a menu, the window displays the alarms, events, or alarm
statistics information according to the settings of the startup template.
3.2.6 Saving an Alarm Template As a New One
You can save an alarm template as a new one.
3.2.1 Alarm Templates

An alarm template consists of the alarm browse conditions or alarm statistical conditions. You
can set typical alarm browse conditions or statistical conditions to templates to avoid repetitively
filter condition setting. You can use the alarm templates to quickly browse alarms or collect
statistics on alarms.
Alarm templates contain the current alarm browse template, history alarm browse template,
event browse template, and alarm statistics template.
Click Filter by Template in the alarm browse window or click Statistics by Template in the
alarm statistics window to set the template.
3.2.2 Exporting or Importing an Alarm Template

You can export an alarm template so that you can directly import the template when you use it
next time. Therefore, the template becomes portable.
Issue 02 (2008-05-31)

3-7

Operation Guide
3 Alarm Management
Prerequisite
You must be an NMS user with the Fault Operator authority or higher.
Context
l
The default alarm template cannot be exported.
For security purposes, the exported template does not contain the resource condition you
choose, that is, it does not contain the specific device information.
Procedure
Step 1 Choose Fault > Import/Export Template.
Step 2 In the Import/Export template dialog box, export or import the alarm template.
l
Export the template to a file.

1.
Choose Export to file.
2.
Click
next to the File name text box. In the Save dialog box, set the destination
path and file name. Click Save.
3.
Click OK.
4.
In the Information dialog box, click OK.
Import the template from a file.

1.
Choose Import from file.
2.
Click
next to the File name text box. In the Open dialog box, choose the template
file, and then click Open.
3.
Click OK.
4.
In the Information dialog box, click OK.
----End
3.2.3 Creating an Alarm or Event Browse Template

Alarm or event browse conditions are complicated. To prevent setting conditions repeatedly,
you can save the preset conditions as a template. You can use the template to browse the alarms
or events conveniently.
Prerequisite
3-8

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Context
l
For each template type, up to 50 templates can be created.
The Save button of the default template is disabled. In other words, the default template
cannot be modified.
A template name cannot exceed 30 characters, and it cannot contain the special characters
such as: ~ ` ! @ # $ % ^ * ( ) { } | \ /.
Procedure
Step 1 In the alarm or event browse window, click Filter by Template, and then choose New .
Step 2 In the New Template dialog box, specify a template name. Click OK.
Step 3 In the New Template dialog box, on the Basic Settings and Alarm Source tabs, set the filter
conditions, and then click Save.
NOTE
On the Basic Settings tab, in the Severity, Acknowledge Status, Clear Status, or Type group box, you
need to select at least one parameter. On the Alarm Source tab, you need to select at least one object or
type. Otherwise, the N2000 UMS prompts that a certain parameter is not selected.
The history alarm browse template does not contain the Ack Status or Clear Status parameter. The event
browse template does not contain the Ack Status, Clear Status, Cleared Time, or Duration parameter.
The GUI is similar to the following figure.
Issue 02 (2008-05-31)

3-9

Operation Guide
3 Alarm Management
Step 4 In the Confirm dialog box, click Yes or No.

----End
3.2.4 Creating the Alarm Statistics Template

Alarm statistical conditions are complicated. To prevent setting conditions repeatedly, you can
save the preset conditions as a template. When an alarm statistics template is set, you can doubleclick the template to collect statistics on the alarms.
Context
l
For each template type, up to 50 templates can be created.
A template name cannot exceed 30 characters, and it cannot contain the special characters
such as: ~ ` ! @ # $ % ^ * ( ) { } | \ /.
Usability is an index used to indicate the availability of a resource (such as a device) in a

period. The calculation formula is as follows:
Usability = (Statistical time range Total alarm duration) / Statistical time range.
The total alarm duration (Time Length) does not contain the repeated duration. For
example, if alarm A lasts three minutes, alarm B lasts two minutes, and the two alarms
overlap for one minute, the total alarm duration is four minutes.
3-10
When time is taken as the row name, the statistics range is specified as follows:
When statistics is collected by month, the statistics time range does not exceed one year.
When statistics is collected by day, the statistics time range does not exceed 90 days.
When statistics is collected by hour, the statistics time range does not exceed 240 hours.
When statistics is collected by time (five minutes), the statistics time range does not
exceed 24 hours.
Issue 02 (2008-05-31)

Operation Guide
l
3 Alarm Management
The parameters for statistics conditions are correlated. If you set a parameter to a specific
value, another parameter may cannot be set or cannot be set to a specific value. For example,
if you set Row heading to month, Anytime and Since cannot be set.
Procedure
Step 1 In the Alarm Statistics window, click Statistic by Template, and then select New.
Step 3 In the New Template dialog box, configure appropriate settings, and then click Save. In the
New Template dialog box, on the Basic Settings and Alarm Source tabs, set the filter
conditions, and then click Save.
Step 4 In the Confirm dialog box, click Yes. In the Confirm dialog box, click Yes or No.
----End
3.2.5 Setting the Startup Template

You can set the startup template for the Current Alarms, History Alarms, Events, or Alarm
Statistics window. After you select a menu, the window displays the alarms, events, or alarm
statistics information according to the settings of the startup template.
Prerequisite
Issue 02 (2008-05-31)

3-11

Operation Guide
3 Alarm Management
Procedure
Step 1 In the Current Alarms, History Alarms, Events, or Alarm Statistics window, click Filter by
Template, and then choose Open .
NOTE
In the Alarm Statistics window, click Statistics by Template.
Step 2 In the Open dialog box, select a template that you want to set to the startup template. Click Set
Startup Template.
When you set the startup template for a window, and then choose the corresponding menu to
access the window, the alarm or event information is displayed according to the settings of the
template.
----End
3.2.6 Saving an Alarm Template As a New One

You can save an alarm template as a new one.
Context
You can save an alarm template as a new one no matter whether it is modified or not.
Procedure
Step 1 In the Current Alarms, History Alarms, Events, or Alarm Statistics window, click Filter by
Template, and then select Open .
3-12

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
NOTE
In the Alarm Statistics window, click Statistics by Template.
Click Filter (In the Alarm Statistics window, click Statistical Condition) to modify the filter conditions
in the current alarm template.
Step 2 In the Save As dialog box, set the template name, and then click OK.
----End
3.3 Monitoring Network Alarms

In the N2000 UMS, you can monitor alarms through the topology view and the alarm panel.
You can also monitor the alarm status in the network by alarm browse and alarm statistics.
3.3.1 Monitoring Alarms Through the Topology View
In the topology view, you can check the status of a device icon to know if an alarm is raised by
this device. You can also browse the alarm details through the topology view.
3.3.2 Monitoring Alarms Through the Alarm Panel
You can monitor alarms through the alarm panel to obtain a brief understanding of the current
alarms.
3.3.3 Locating an Alarm
By locating an alarm, you can find the topology object that raises the alarm. The position of the
object is focused in the topology view.
3.3.4 Collecting Statistics on Alarms
The N2000 UMS enables you to collect statistics on alarms by condition. You can use an existing
alarm statistics template or create a template to collect statistics on alarms.
3.3.1 Monitoring Alarms Through the Topology View

In the topology view, you can check the status of a device icon to know if an alarm is raised by
this device. You can also browse the alarm details through the topology view.
Prerequisite
Procedure
Step 1 In the topology view or the navigation tree, right-click the device that raises an alarm and choose
Browse Alarm.
Issue 02 (2008-05-31)

3-13

Operation Guide
3 Alarm Management
Step 2 On the Current Alarms tab, view the information on the current alarm of the device.
----End
3.3.2 Monitoring Alarms Through the Alarm Panel

You can monitor alarms through the alarm panel to obtain a brief understanding of the current
alarms.
Prerequisite
Procedure
l
Monitor alarms through the thumbnail of the alarm panel.

The thumbnail of the alarm panel consists of four color blocks and an event indicator at the
upper right corner of the client. Each color block represents an alarm severity. The number
on a color block represents the number of the current alarms of the specific severity in the
N2000 UMS. When a new alarm occurs, the corresponding color block blinks to prompt
you. You can check the thumbnail of the alarm panel for new alarms, alarm severities,
current alarm statistics, and new events.
button that is at the upper right corner of the client, the
If you move the cursor to the
number of the new events is displayed. When a new event occurs, this button turns red and
blinks to prompt you. Click this button. Then an event browse window is displayed.
Monitor alarms through the alarm panel.

on the toolbar to display the alarm panel.
Choose Fault > Show Alarm Panel , or click
You can add a current alarm browse template or an event browse template to the alarm
panel. The alarm panel displays alarms information based on the template.
3-14

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Open an alarm or event browse window through the alarm panel.

When you monitor alarms through the alarm panel and you want to know the alarm details,
you can double-click an alarm or event template on the alarm panel to open the
corresponding alarm or event template window. Then you can query the alarm details.
When the alarm panel is displayed as a thumbnail, you can click a color block on it to view
the details on the alarms of a specific severity.
----End

Prerequisite
Context
l
All the alarm browse windows provide the access of locating alarms.
After you locate an alarm, the object that raises the alarm is focused in the topology view.
You can locate the objects in the topology tree or on the panel.
If the object that raises the alarm is deleted, the Locating to Topo Object menu is disabled.
Procedure
In the alarm browse window, right-click an alarm and choose Locating to Topo Object.
After the alarm is located, the object that raises the alarm is focused in the topology view.
----End
Issue 02 (2008-05-31)

3-15

Operation Guide
3 Alarm Management
3.3.4 Collecting Statistics on Alarms

The N2000 UMS enables you to collect statistics on alarms by condition. You can use an existing
alarm statistics template or create a template to collect statistics on alarms.
Prerequisite
Procedure
Step 1 Choose Fault > Alarm Statistics.
Step 2 In the Statistical Condition dialog box, set the statistical conditions. Click OK.
NOTE
If you set the startup template for alarm statistics on the local client and choose Fault > Alarm Statistical, the
statistical result obtained by the startup template is displayed. If you do not set the startup template for alarm
statistics and choose Fault > Alarm Statistical , the Statistical Condition dialog box is displayed.
Step 3 In the alarm statistics window, check the statistical result.
3-16
Click the Alarm Statistics tab. The alarm information collected based on the row and
column headings are displayed.
Click the Alarm Average Ack Time tab. The mean alarm acknowledgement time collected
based on the row and column headings is displayed.
Click the Alarm Average Cleared Time tab. The mean alarm clearance time collected
based on the row and column headings is displayed.

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 4 According to the buttons at the bottom of the Alarm Statistics window, you can perform the
following operations:
l
Click Statistics by Template to create, open, or save an alarm statistical template.
Click Statistical Condition to set the statistical condition.
Click Refresh to collect statistics on alarms again based on the current statistical condition.
Click Print to print the statistical result in a specified medium.
Click Save As to save the statistical result as a file.
----End
3.4 Browsing Alarms

The N2000 UMS supports alarm browse. You can set various browse conditions and browse
templates to quickly locate the alarms you are concerned about.
3.4.1 Browsing Current Alarms
This section describes how to browse current alarms.
3.4.2 Browsing History Alarms
This section describes how to browse history alarms.
3.4.3 Browsing Events
You can browse events based on the preset conditions or a template.
3.4.4 Browsing Correlative Alarms or Events
This section describes how to browse correlative alarms or events.
3.4.5 Example of Browsing the N2000 UMS Alarms
This section provides an example on how to create a template to browse the N2000 UMS alarms.
3.4.6 Example of Browsing Performance Threshold Alarms
This section provides an example on how to create a template to browse performance threshold
alarms and how to use this template to monitor performance threshold alarms.
3.4.7 Example of Browsing Environment Alarms
This section provides an example on how to create a template to browse environment alarms
and how to use the template to monitor environment alarms.

Issue 02 (2008-05-31)

3-17

Operation Guide
3 Alarm Management
Prerequisite
To perform the browse operation, you must be an NM user with the "Fault Maintainer" authority
or higher. To perform the acknowledgement or clearance operation, you must be an NM user
with the "Fault Operator" authority or higher.
Procedure
Step 1 Choose Fault > Browse Current Alarm.
Step 2 In the Filter dialog box, set the filter conditions. Click OK.
NOTE
If the startup template for browsing the current alarms is set, the Filter dialog box is not displayed. The alarms
that meet the filter conditions are displayed.
Step 3 In the query result table, click a column heading to sort the results.
NOTE
If you click Alarm Source or Alarm Source Type, the NEs are grouped by NE ID. If you click a different
field, the alarm records are sorted in alphabetical order.
If you click , the fields are sorted in ascending order. If you click , the fields are sorted in descending
order. Switch between and to switch between the ascending and descending orders.
Step 4 In the query result table, right-click an alarm and do as follows:
3-18
Choose Select All to select all the records in the query result table.
Choose Correlative Alarms to query correlative alarms.
Choose Remark to set the remarks on the alarm.
Choose Maintenance Experience to set the maintenance experience.

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Choose Mask. In the Confirm dialog box, click OK to mask the selected alarm.
Choose Acknowledge to acknowledge the alarm.
If the alarm is unacknowledged and uncleared, the alarm status becomes

Ack&Uncleared.
If the alarm is unacknowledged and cleared, it is moved to the history alarm database.
Choose Clear to clear the alarm if it is not cleared.

Unack&Cleared.
If the alarm is acknowledged and uncleared, it is moved to the history alarm database.
Choose Locating to Topo Object to locate the topology object that raises the alarm.
Step 5 Optional: Choose Display latest alarms to query new alarms in real time.
Step 6 In the query result table, choose an alarm, and do as follows:
l
Click Filter by Template to create, open, or save a browse template.
Click Filter to set filter conditions to query current alarms.
Click Refresh to query current alarms again based on the current filter condition.
Click Acknowledge to acknowledge the alarm if it is unacknowledged.
Click Clear to clear the alarm if it is not cleared.
Click Print to print the alarm information.
Click Save As to save the alarm information as a file.
----End
3.4.2 Browsing History Alarms

This section describes how to browse history alarms.
Prerequisite
Context
You can use a preset template or set a new template to browse history alarms.
Issue 02 (2008-05-31)

3-19

Operation Guide
3 Alarm Management
Procedure
Step 1 Choose Fault > Browse History Alarm.
Step 2 In the Filter dialog box, set the filter conditions. Then click OK.
NOTE
If the startup template for browsing history alarms is set, the Filter dialog box is not displayed, but the alarms
that match the startup template conditions are displayed.
NOTE
3-20
Choose Correlation Alarms to query correlative alarms.
Choose Remark to set remarks for the alarm.
Choose Maintenance Experience to set the maintenance experience for the alarm.
Choose Mask. In the Confirm dialog box, click Yes to mask the alarm.
Choose Dump to dump the alarm to a file.

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 5 Click the buttons in the lower part of the browse window:
l
Click Filter by Template to create, open, or save a template.
Click Filter, and then set the filter conditions to query alarms.
Click Refresh to query alarms again based on the current filter conditions.
Click Print to set and print alarm information.
Click Save As to save the current alarm information to a file.
----End
3.4.3 Browsing Events

You can browse events based on the preset conditions or a template.
Prerequisite
Context
You can use a preset template or set a new template to browse events.
Procedure
Step 1 Choose Fault > Browse Event.
Step 2 In the Filter dialog box, set the conditions. Then click OK.
NOTE
If the startup template for browsing events is set, the Filter dialog box is not displayed, and the events that match
the startup template conditions are displayed.
Step 3 Optional: In the query result table, click a column heading to sort the result.
Issue 02 (2008-05-31)

3-21

Operation Guide
3 Alarm Management
NOTE
If you click Event Source or Event Source Type, the NEs are grouped by NE ID. If you click a different
field, the event records are sorted in alphabetical order.
Step 4 Optional: In the query result table, right-click an event and do as follows:
l
Choose Correlative Events to query correlative events.
Choose Remark to set the remarks for the event.
Choose Maintenance Experience to set the maintenance experience for the event.
Choose Mask. In the Confirm dialog box, click Yes to mask the event.
Choose Dump to dump the event to a file.
Choose Locating to Topo Object to locate the topology object that raises the event.
Step 5 Optional: Select Display latest events to view new events in real time.
Step 6 Optional: Click the buttons in the lower part of the browse window:
l
Click Filter by Template to create, open, or save a template.
Click Filter, and then set the filter conditions to query events.
Click Refresh to query events again based on the current filter conditions.
Click Print to set and print event information.
Click Save As to save the current event information as a file.
----End
3.4.4 Browsing Correlative Alarms or Events

This section describes how to browse correlative alarms or events.
Prerequisite
Context
In the alarm correlation analysis, the alarms or events whose correlation actions are set to
mask are called correlative alarms or correlative events.
3-22

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Procedure
Step 1 Choose Fault > Browse History Alarm, Fault > Browse Current Alarm , or Fault > Browse
Event.
Step 2 In the alarm or event list, right-click an alarm or an event and choose Correlative Alarms or
Correlative Events .
The Correlative Alarms or Correlative Events dialog box is displayed. The dialog box displays
the correlative alarms or correlative events of the selected alarm or event.
----End
3.4.5 Example of Browsing the N2000 UMS Alarms

This section provides an example on how to create a template to browse the N2000 UMS alarms.
Prerequisite
Procedure
Step 2 In the alarm browse window, click Filter by Template and choose New .
Step 4 In the New Template dialog box, set the filter conditions. On the Alarm Source tab, select By
type. In the Type navigation tree, select NMS, and then click Save.
In the alarm browse window, the N2000 UMS alarms are displayed according to the new
template.
----End
3.4.6 Example of Browsing Performance Threshold Alarms

This section provides an example on how to create a template to browse performance threshold
alarms and how to use this template to monitor performance threshold alarms.
Prerequisite
Procedure
Step 2 In the alarm browse window, click Filter by Template and choose New .
Issue 02 (2008-05-31)

3-23

Operation Guide
3 Alarm Management
Step 4 In the New Template dialog box, set the filter conditions. In the Type field, select all the options
except Power Supply and Environment. Click Save.
In the alarm browse window, the performance threshold alarms are displayed according to the
new template.
----End
3.4.7 Example of Browsing Environment Alarms

This section provides an example on how to create a template to browse environment alarms
and how to use the template to monitor environment alarms.
Prerequisite
Procedure
Step 2 On the alarm browse window, click Filter by Template and choose New .
Step 4 In the New Template dialog box, select Power Supply and Environment for Type. Click
Save.
In the alarm browse window, the environment alarms are displayed according to the new
template.
----End
3.5 Handling an Alarm

When an alarm is raised, you need to take actions to handle it. You need to remove the network
fault or the device fault to recover the network or device to its normal state.
3.5.1 Fault Handling Procedure
The procedure for fault handling consists of three phases: information collection, fault location,
and fault removal. After receiving an alarm, you need to collect fault information, analyze fault
causes, locate the fault, remove the fault, and restore the system.
3.5.3 Viewing the Alarm Details
You can view the alarm details to know the alarm information. You can then take actions based
on the information.
3.5.4 Acknowledging an Alarm
3-24

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
The function of alarm acknowledgement provides a method to identify whether an alarm is being
handled. By alarm acknowledgement, you can identify the alarms that are not handled so that
you can handle these alarms in time.
3.5.6 Querying Device Maintenance Information
You can query device maintenance information to obtain the information on the device location
and the maintenance personnel. You can then notify the maintenance personnel if a device is
faulty.
3.5.7 Clearing Alarms
Alarms may be missing due to some faults. For example, when the N2000 UMS fails to
communicate with the device, the clearance alarms reported by the device may be missing. In
such a case, if the device does not support alarm check, these alarms are not cleared. For
maintenance purposes, the N2000 UMS allows you to clear the alarms manually.
3.5.8 Recording Alarm Maintenance Experiences
You can record the alarm maintenance experiences. When a similar alarm is raised, you can
refer to the alarm maintenance experiences so that the alarm can be cleared in time.
3.5.9 Example of Alarm Handling
This section provides an example on how to handle the alarm of insufficient disk space. It shows
the procedure and method for handling alarms. It helps you to know the basic procedure and
operations of alarm handling.
3.5.1 Fault Handling Procedure

The procedure for fault handling consists of three phases: information collection, fault location,
and fault removal. After receiving an alarm, you need to collect fault information, analyze fault
causes, locate the fault, remove the fault, and restore the system.
Flow Chart
Figure 3-4 shows the fault handling procedure.
Issue 02 (2008-05-31)

3-25

Operation Guide
3 Alarm Management
Figure 3-4 Fault handling procedure
3-26

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Procedure
The fault handling procedure, as shown in Figure 3-4, is described inTable 3-2.
Table 3-2 Fault handling procedure
Step
Operation
Description
Receive an alarm
After you receive an alarm, start the alarm handling

procedure. To ensure that the operators can receive
notifications in time when a fault occurs, you need to set
alarm notification methods on the N2000 UMS.
View the alarm details
This is where you start. View the alarm details, including

the alarm location information, alarm help, and alarm
maintenance experience.
Acknowledge the
alarm
To avoid others handling the same alarm, you need to

acknowledge it. When you acknowledge an alarm, it
indicates that the alarm is being processed.
Collect fault
information
By locating an alarm, you can query the fault information

and analyze the causes of the fault.
Analyze the causes of

the alarm
Analyze the causes of the fault according to the fault

information.
Work out the fault

handling scheme
Work out the fault handling scheme according to the alarm

details, device manuals, network status, and maintenance
experience.
Carry out the fault

handling scheme
Carry out the fault handling scheme to remove the fault.
Clear the alarm
When the fault is removed, the alarm is cleared, and the

N2000 UMS receives the cleared alarm.
Check the handling

results
After the fault is removed, check the handling results.
10
Record the
maintenance
experience
After you complete the fault handling, record the

maintenance experience.

Prerequisite
To perform the browse operation, you must be an NM user with the "Fault Maintainer" authority
or higher. To perform the acknowledgement or clearance operation, you must be an NM user
with the "Fault Operator" authority or higher.
Issue 02 (2008-05-31)

3-27

Operation Guide
3 Alarm Management
Procedure
NOTE
NOTE

l
Choose Correlative Alarms to query correlative alarms.
Choose Remark to set the remarks on the alarm.
Choose Maintenance Experience to set the maintenance experience.
Choose Mask. In the Confirm dialog box, click OK to mask the selected alarm.
Choose Acknowledge to acknowledge the alarm.
l
3-28

Ack&Uncleared.
If the alarm is unacknowledged and cleared, it is moved to the history alarm database.
Choose Clear to clear the alarm if it is not cleared.

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management

Unack&Cleared.
If the alarm is acknowledged and uncleared, it is moved to the history alarm database.
Step 5 Optional: Choose Display latest alarms to query new alarms in real time.
Step 6 In the query result table, choose an alarm, and do as follows:
l
Click Filter by Template to create, open, or save a browse template.
Click Filter to set filter conditions to query current alarms.
Click Refresh to query current alarms again based on the current filter condition.
Click Acknowledge to acknowledge the alarm if it is unacknowledged.
Click Clear to clear the alarm if it is not cleared.
Click Print to print the alarm information.
Click Save As to save the alarm information as a file.
----End
3.5.3 Viewing the Alarm Details

You can view the alarm details to know the alarm information. You can then take actions based
on the information.
Prerequisite
Procedure
In the alarm browse window, select an alarm.
----End
Result
The alarm details are displayed at the lower left part of the alarm list. The alarm handling
suggestions are displayed at the lower right part of the alarm list.
Issue 02 (2008-05-31)

3-29

Operation Guide
3 Alarm Management
3.5.4 Acknowledging an Alarm

The function of alarm acknowledgement provides a method to identify whether an alarm is being
handled. By alarm acknowledgement, you can identify the alarms that are not handled so that
you can handle these alarms in time.
Prerequisite
Procedure
NOTE
Step 3 In the Current Alarm window, right-click an alarm and choose Acknowledge.
3-30

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 4 In the Acknowledge Alarms dialog box, click Yes.

----End
Result
l
A progress bar indicates the progress if you acknowledge two or more alarms at a time.
When the N2000 UMS receives the command for acknowledging the alarm, the alarm status
becomes Ack. The N2000 UMS records when the alarm is acknowledged and who performs
this task. It also refreshes the information in all the windows on the client and updates the
data of the alarm panel and alarm box.
If an alarm is acknowledged and cleared, it is dumped to the history database.

Prerequisite
Context
l
All the alarm browse windows provide the access of locating alarms.
After you locate an alarm, the object that raises the alarm is focused in the topology view.
You can locate the objects in the topology tree or on the panel.
If the object that raises the alarm is deleted, the Locating to Topo Object menu is disabled.
Procedure
In the alarm browse window, right-click an alarm and choose Locating to Topo Object.
Issue 02 (2008-05-31)

3-31

Operation Guide
3 Alarm Management
After the alarm is located, the object that raises the alarm is focused in the topology view.
----End
3.5.6 Querying Device Maintenance Information

You can query device maintenance information to obtain the information on the device location
and the maintenance personnel. You can then notify the maintenance personnel if a device is
faulty.
Prerequisite
Procedure
Step 1 In the alarm browse window, right-click an alarm and choose Locating to Topo Object.
The topology object that raises the alarm is focused.
Step 2 Choose System > Device Maintenance Info.
Step 3 In the Device Maintenance Info window, double-click the records in the maintenance
information list or click Display to view the device maintenance information.
NOTE
If you do not select any device in the topology view and choose System > Device Maintenance Info, the
maintenance information on all the devices is displayed.
3-32

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
----End
3.5.7 Clearing Alarms

Alarms may be missing due to some faults. For example, when the N2000 UMS fails to
communicate with the device, the clearance alarms reported by the device may be missing. In
such a case, if the device does not support alarm check, these alarms are not cleared. For
maintenance purposes, the N2000 UMS allows you to clear the alarms manually.
Prerequisite
Context
You cannot roll back the operation of clearing an alarm.
Procedure
Step 2 In the Current Alarms window, right-click an alarm and choose Clear .
Issue 02 (2008-05-31)

3-33

Operation Guide
3 Alarm Management
Step 3 In the Clear Alarms dialog box, click Yes.

----End
Result
l
A progress bar indicates the progress if you acknowledge two or more alarms at a time.
The N2000 UMS changes the status of an alarm to Cleared. The N2000 UMS records when
the alarm is cleared and who performs this task. It also refreshes the information in all the
windows on the client and updates the data of the alarm panel and alarm box.
If an alarm is acknowledged and cleared, it is dumped to the history database.
3.5.8 Recording Alarm Maintenance Experiences

You can record the alarm maintenance experiences. When a similar alarm is raised, you can
refer to the alarm maintenance experiences so that the alarm can be cleared in time.
Prerequisite
Procedure
Step 1 Choose Fault > Settings > Maintenance Experience .
Step 2 In the Alarm/Event navigation tree, select an alarm, and then click Edit.
3-34

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 3 In the Edit dialog box, enter the experience of handling this alarm.
NOTE
The alarm experience cannot exceed 250 characters.
Step 4 Click OK.

----End
3.5.9 Example of Alarm Handling

This section provides an example on how to handle the alarm of insufficient disk space. It shows
the procedure and method for handling alarms. It helps you to know the basic procedure and
operations of alarm handling.
Background
The N2000 UMS reports an alarm of insufficient disk space.
Operation Guide
Based on the 3.5.1 Fault Handling Procedure, do as follows:
1.
Receive the alarm notification.

On the client, choose Fault > Browse Current Alarm to open the current alarm window.
An uncleared hard disk alarm of the N2000 UMS is found. The alarm indicates that the
N2000 UMS server has insufficient disk space.
2.
View the alarm details.

Select this alarm record, and then browse the details and handling suggestions of the alarm
at the bottom of the browse window.
3.
Issue 02 (2008-05-31)
Acknowledge the alarm

3-35

Operation Guide
3 Alarm Management
To avoid others handling the same alarm, you need to acknowledge it. When you
acknowledge the alarm, it indicates that the alarm is being processed. Right-click the alarm
and choose Acknowledg.
4.
Work out the alarm handling method.

According to the troubleshooting tips, maintenance experience, and operation status of the
N2000 UMS, you can delete the redundant files and back up the dump data on another disk
to solve the problem of insufficient disk space.
5.
Remove the relevant fault.

Delete the redundant files of the N2000 UMS. Back up the dump files from
$N2000ROOT/server/dump to other disk. Then delete the source dump data. The N2000
UMS server then obtains more available disk space.
6.
Check the handling results.

On the client, choose Fault > Browse Current Alarm to open the current alarm window.
The status of the alarm is changed from uncleared to cleared.
7.
Record the alarm maintenance experience.

On the client, choose Fault > Settings > Maintenance Experience. In the navigation tree,
select NMS Server Database Data Space Alarm, click Edit. In the Edit dialog box, record
the maintenance experience for future reference.
3.6 Setting the Alarm or Event Auto Processing

You do not need to handle all the alarms manually. You can set an auto processing policy to
enable the N2000 UMS to process the alarms that match the preset conditions. This helps to
improve the work efficiency.
3.6.1 Alarm Auto Processing
You can set the alarm auto processing policies to enable the N2000 UMS to automatically process
multiple alarms that it receives. Alarm auto processing policies reduce the workload.
3.6.2 Setting the Alarm Auto Acknowledgement
The N2000 UMS can acknowledge the cleared alarms immediately or periodically. Therefore,
you do not need to acknowledge the cleared alarms manually.
3.6.3 Setting Alarm Auto Synchronization
You can set alarm auto synchronization. After the N2000 UMS resumes the communication
with a device or is restarted, the N2000 UMS automatically synchronizes the alarms with those
on the device. This helps keep alarm data consistency between the N2000 UMS and devices.
3.6.4 Redefining Alarms or Events
Each type of devices has its own alarms or events. You can redefine the names, function types,
and severities of the alarms or events. The new settings take effect when a new alarm or a new
event is raised.
3.6.5 Setting mask of the NE Alarms or Events
During the device maintenance, test, or deployment, the device may report numerous alarms. In
this case, you can set the alarm mask conditions to mask the alarms or events that meet the
conditions. The mask alarms are not displayed or saved.
3.6.6 Setting mask of the N2000 UMS Alarms or Events
You can set the mask conditions of the N2000 UMS alarms or events to mask the alarms or
events that meet the conditions.
3-36

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
3.6.7 Setting Postprocessing for Alarms or Events

You can configure the alarm or event postprocessing policy of the N2000 UMS. When an alarm
or an event is raised, the N2000 UMS runs the specific operation command automatically.
3.6.1 Alarm Auto Processing

You can set the alarm auto processing policies to enable the N2000 UMS to automatically process
multiple alarms that it receives. Alarm auto processing policies reduce the workload.
Table 3-3 lists the alarm auto processing policies.
Table 3-3 Alarm auto processing policies
Alarm Auto
Processing
Policies
Description
Alarm auto
synchronization
When the network connection fails or the N2000 UMS restarts, the
alarms on the N2000 UMS may be different from those on the devices.
The N2000 UMS then automatically synchronizes the alarms with
those on the devices.
Alarm auto
acknowledgement
After the related faults are removed, you do not need to manually
acknowledge the cleared alarms. You can set the auto
acknowledgement conditions so that the N2000 UMS can
automatically acknowledge alarms that meet the conditions.
Alarm redefinition
You can redefine the alarm name, function type and severity on the
N2000 UMS. The N2000 UMS then displays the redefined alarm based
on your settings.
Alarm mask
If you are not concerned about some alarms, you can set the N2000
UMS to mask them. For example, when the equipment is under
maintenance or test, mass alarms are raised. Such alarms can be
masked.
Alarm
postprocessing
You can set the alarm postprocessing policy. The N2000 UMS can
then process the alarms that match the preset conditions based on the
policy.
3.6.2 Setting the Alarm Auto Acknowledgement

The N2000 UMS can acknowledge the cleared alarms immediately or periodically. Therefore,
you do not need to acknowledge the cleared alarms manually.
Prerequisite
Context
l
Issue 02 (2008-05-31)
The auto acknowledgement applies to only the cleared alarms.

3-37

Operation Guide
3 Alarm Management
l
The time acknowledgement starts at 01:00 every day.
Procedure
Step 1 Choose Fault > Settings > Auto Acknowledgement and Synchronization .
Step 2 In the Auto Acknowledgement and Synchronization dialog box, set the auto
acknowledgement.
l
Set the immediate acknowledgement.

Select Acknowledge Immediately After an Alarm Is Cleared and specify the alarm
severity.
Set the time acknowledgement.

Select Acknowledge in * Days After an Alarm Is Cleared and specify the time and the
alarm severity.
NOTE
The immediate acknowledgement applies to only the alarms that are cleared after the immediate
acknowledgement configuration, but it does not apply to those alarms that are cleared before the configuration.
Step 3 Click OK.

----End
Result
The alarms that match the preset conditions are automatically acknowledged. The user who
acknowledges the alarms is recorded as NMS.
3.6.3 Setting Alarm Auto Synchronization

You can set alarm auto synchronization. After the N2000 UMS resumes the communication
with a device or is restarted, the N2000 UMS automatically synchronizes the alarms with those
on the device. This helps keep alarm data consistency between the N2000 UMS and devices.
3-38

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Prerequisite
Context
Because alarm synchronization may have a big impact on the N2000 UMS, only alarms are
synchronized, and events are not.
Procedure
Step 1 Choose Fault > Settings > Auto Acknowledgement and Synchronization .
Step 2 In the Auto Acknowledgement and Synchronization dialog box, in the Auto
Acknowledgement and Synchronization group box, set the alarm synchronization parameters.
l
Enable synchronize all alarms when the NMS is started indicates that the N2000 UMS
automatically synchronizes the alarms with those on all the devices when it is started.
Enable synchronize the alarms when the communication is resumed between the NMS
and the devices indicates that the N2000 UMS automatically synchronizes the alarms with
those on a specific device when it resumes the communication with the device.
Step 3 Click OK.

----End
3.6.4 Redefining Alarms or Events

Each type of devices has its own alarms or events. You can redefine the names, function types,
and severities of the alarms or events. The new settings take effect when a new alarm or a new
event is raised.
Prerequisite
Issue 02 (2008-05-31)

3-39

Operation Guide
3 Alarm Management
Procedure
Step 1 Choose Fault > Settings > Redefine Alarm/Event .
Step 2 In the Redefine Alarm/Event window, click New. A new alarm or event redefinition record is
displayed.
Step 3 Set the redefinition record.

1.
Set whether to enable this redefinition record.
2.
In Alarm/Event, click
event for redefinition.
3.
In Device, click
4.
In Alarm/Event Name, rename the redefined alarm or event.
. In the Select Alarm/Event dialog box, select the alarm or
. In the Select Device dialog box, select a device.
NOTE
Alarm/Event Name and Type are related to Device. You can set Alarm/Event Name and Type only
when you select all the devices in Device. By default, all the devices in Device are selected.
5.
In Type, in the drop-down list, select a type for the redefined alarm or event.
6.
In Severity, in the drop-down list, select a severity for the redefined alarm or event.
NOTE
You can also modify an existing alarm or event redefinition record by performing the previous steps.
If a field is displayed in white
, it indicates that the filed can be modified. If a field is displayed in gray
, it indicates that the field cannot be modified. If the Enable field is displayed in purple
that the record is modified but not applied. If the Enable field is displayed in green
record is new and not applied.
, it indicates
, it indicates that the
Step 4 Click Apply.

----End
3.6.5 Setting mask of the NE Alarms or Events

During the device maintenance, test, or deployment, the device may report numerous alarms. In
this case, you can set the alarm mask conditions to mask the alarms or events that meet the
conditions. The mask alarms are not displayed or saved.
Prerequisite
3-40

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Context
Alarms are masked based on their original properties (the properties before redefinition).
Therefore, if you set the redefinition and mask for an alarm, the mask settings take effect before
the redefinition settings take effect.
Procedure
Step 1 Choose Fault > Settings > NE Alarm/Event Mask.
Step 2 In the NE Alarm/Event Mask window, click New. An alarm or event mask record is created.
Step 3 Set the alarm or event mask record.

1.
Select whether to enable the alarm or event mask record.
2.
In Mask Condition, click

condition.
3.
Set Start Time, End Time, Alarm Duration, and Remarks.
. In the Mask Condition dialog box, specify the mask
NOTE
You can also modify an existing alarm or event mask record by performing the previous steps.
, it indicates
----End
3.6.6 Setting mask of the N2000 UMS Alarms or Events

You can set the mask conditions of the N2000 UMS alarms or events to mask the alarms or
events that meet the conditions.
Prerequisite
Procedure
Step 1 Choose Fault > Settings > NMS Alarm/Event Mask.
Step 2 In the NMS Alarm/Event Mask window, select the check box in the mask field of an alarm or
event.
Issue 02 (2008-05-31)

3-41

Operation Guide
3 Alarm Management
NOTE
If the mask field of an alarm or event is displayed in purple

but not yet applied.
, it indicates that the alarm or event is modified
Step 3 Click Apply.

----End
3.6.7 Setting Postprocessing for Alarms or Events

You can configure the alarm or event postprocessing policy of the N2000 UMS. When an alarm
or an event is raised, the N2000 UMS runs the specific operation command automatically.
Prerequisite
Procedure
Step 1 Choose Fault > Settings > Alarm/Event Post Actions .
Step 2 In the Alarm/Event Post Actions window, click New. A new alarm or event postprocessing
record is displayed.
Step 3 Set the postprocessing record.
3-42
1.
Set whether to enable this postprocessing record.
2.
. In the Postprocessing Condition dialog box,

In Postprocessing Condition, click
set the alarm or event for postprocessing.
3.
Set Start Time, End Time, Postprocessing Action Settings, and Remarks.
Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
NOTE
l
l
You can also modify an existing alarm or event postprocessing record by performing the previous steps.
If the Enable field of the current rule is displayed in purple
but not yet applied. If the Enable field is displayed in green
created but not yet applied.
, this indicates that the current rule is modified

, this indicates that the current rule is newly
Step 4 Click Apply.

----End
3.7 Setting the Alarm Correlation Rule

You can filter some unnecessary alarms or modify the alarm severities to improve alarm
processing efficiency by setting alarm correlation rules. The N2000 UMS provides the
correlation analysis, alarm or event frequency analysis, intermittent alarm or repeat event
analysis, and acknowledged and uncleared alarm time analysis.
3.7.1 Correlation Rules
This section describes the rules of the correlation analysis and helps you to configure the
correlation rules in the N2000 UMS properly.
3.7.2 Setting the Alarm or Event Correlation Analysis
The objective of the correlation analysis is to analyze the reported alarms based on rules and to
modify the alarm severities or mask the alarms.
3.7.3 Setting the Alarm or Event Frequency Analysis
After you set the alarm or event frequency analysis, the N2000 UMS analyzes the frequency of
alarms or events. When the number of alarms or events exceeds the preset threshold, the N2000
UMS handles the alarms or events according to the preset handling actions.
3.7.4 Setting the Intermittent Alarms or Repeat Events Analysis
You can set the intermittent alarm or repeat event analysis. The N2000 UMS can then discard
the alarms or events that match the conditions or modify the severities of these alarms or events.
3.7.5 Setting the Acknowledged and Uncleared Alarm Time Analysis
By the acknowledged and uncleared alarm time analysis, you can modify the severity of an alarm
that is acknowledged but not cleared in a long period. This helps handle such alarms in time.
3.7.6 Example of the Alarm or Event Correlation Analysis
This section provides two examples of the correlation analysis to help you understand the
correlation analysis better.
3.7.7 Example of Alarm or Event Frequency Analysis
This section describes an example of the alarm or event frequency analysis so that you can
understand the alarm or event frequency analysis better.
3.7.8 Example of the Intermittent Alarm or Repeat Event Analysis
This section provides an example of the intermittent alarms or repeat event analyses to help you
understand the intermittent alarm or repeat event analysis better.
3.7.9 Example of the Acknowledged and Uncleared Alarm Time Analysis
This section describes an example of the acknowledged and uncleared alarm time analysis to
help you understand the acknowledged and uncleared alarm time analysis better.
Issue 02 (2008-05-31)

3-43

Operation Guide
3 Alarm Management
3.7.1 Correlation Rules

This section describes the rules of the correlation analysis and helps you to configure the
correlation rules in the N2000 UMS properly.
Correlative Alarms or Events

Correlative alarms or events are the alarms or events that have correlations between one another.
One is the root alarm or root event that causes other alarms or events.
A fault or a situation may result in multiple alarms or events. The correlative Alarms or events
do not help in the fault location or analysis. To solve this problem, you can set a condition based
on the alarm or event features, such as the alarm raised time or physical location, to reduce the
severities of the alarms or events that match the condition or mask them directly.
Alarm or Event Frequency Analysis

The same alarms raised during a period of time may have correlations with each other. In an
alarm or event frequency analysis, if the number of the same alarms raised during a period of
time reaches a specific value, the alarms are considered to be correlated.
By the alarm or event frequency analysis, you can set a specific threshold. When the number of
the same alarms raised during a period of time exceeds the threshold, the alarms are considered
to be correlated. The N2000 UMS performs the preset operations.
Intermittent Alarms and Repeat Events

When the interval between two reports on the clearance of an alarm is shorter than the specified
report period, this alarm is defined as an intermittent alarm.
When the interval of reporting an event is shorter than specified report period, this event is
defined as a repeat event.
A fault or a situation may result in the reporting of multiple repetitive alarms or events. Such
alarms or events are redundant. You can set a condition to determine the alarms or events that
match the condition as intermittent alarms or repeat events. You can then reduce the severities
of such alarms or events or mask them directly.
Acknowledged and Uncleared Alarm Time Analysis

For the alarms that are acknowledged but uncleared for a long time, you can raise the alarm
severity by the acknowledged and uncleared alarm time analysis. This helps the maintenance
personnel pay attention to the alarm and handle it in time.
3.7.2 Setting the Alarm or Event Correlation Analysis

The objective of the correlation analysis is to analyze the reported alarms based on rules and to
modify the alarm severities or mask the alarms.
Prerequisite
3-44

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Context
l
The correlation analysis settings take effect in a specified period. The effective period
depends on the server time.
A correlation condition and an action must be set.
The correlation conditions are different between the correlation analysis of a single alarm
or event and that of two alarms or events. The correlation properties of the correlation
analysis of a single alarm or event are based on a specific device and a specific time range.
The correlation properties of the correlation analysis of two alarms or events are based on
the alarm sources and time range between the two alarms or events.
Procedure
Step 1 Choose Fault > Settings > Correlation Rule .
Step 2 In the Correlation Rule window, on the Correlation Analysis tab, click New. A new alarm or
event correlation analysis rule is displayed.
Step 3 Set the alarm or event correlation analysis rule.

l
Set the correlation analysis rule of a single alarm or event.

1.
Set whether to enable the alarm or event correlation analysis rule.
2.
In Correlative Alarm/Event1, click

. In the Select Alarm/Event dialog box,
select an alarm or an event for the correlation analysis.
3.
Set Priority, Start Time, End Time, Condition, and Action.
Set the correlation analysis rule of two alarms or events.

1.
Set whether to enable the alarm or event correlation analysis rule.
2.
. In the Select Alarm/Event dialog box,

In Correlative Alarm/Event1, click
select an alarm or an event for correlation analysis. Follow the same procedure to set
Correlative Alarm/Event2.
3.
Set Priority, Start Time, End Time, Condition, and Action.
NOTE
You can also modify an existing alarm or event correlation analysis rule by performing the previous steps.
, it indicates
Step 4 Click Apply.

----End
Issue 02 (2008-05-31)

3-45

Operation Guide
3 Alarm Management
3.7.3 Setting the Alarm or Event Frequency Analysis

After you set the alarm or event frequency analysis, the N2000 UMS analyzes the frequency of
alarms or events. When the number of alarms or events exceeds the preset threshold, the N2000
UMS handles the alarms or events according to the preset handling actions.
Prerequisite
Procedure
Step 2 In the Correlation Rule window, on the Alarm/Event Frequency Analysis tab, click New. A
rule of the alarm or event frequency analysis is created.
Step 3 Set the rule of the alarm or event frequency analysis.
3-46
1.
Select whether to enable the rule.
2.
event.
3.
In Triggering Condition, click

. In the Set Correlation Handling Policy and
Condition dialog box, specify the triggering condition and the handling policy.
. In the Select Alarm/Event dialog box, select an alarm or

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
NOTE
If the handling policy is set to generate N2000 UMS alarms, an avalanche alarm is raised when the triggering
condition is met.
You can also modify an existing rule of the alarm or event frequency analysis by performing the previous
steps.


Step 4 Click Apply.

----End
3.7.4 Setting the Intermittent Alarms or Repeat Events Analysis

You can set the intermittent alarm or repeat event analysis. The N2000 UMS can then discard
the alarms or events that match the conditions or modify the severities of these alarms or events.
Prerequisite
Procedure
Step 2 In the Correlation Rule window, on the Intermittent Alarms/Repeat Events Analysis tab,
click New. A new intermittent alarm or repeat event analysis rule is displayed.
Step 3 Set the intermittent alarm or repeat event analysis rule.

1.
Set whether to enable the intermittent alarm or repeat event analysis rule.
2.
. In the Select Alarm/Event dialog box, select an intermittent
alarm or a repeat event for analysis.
3.

Condition dialog box, select a triggering condition and set a handling policy.
Issue 02 (2008-05-31)

3-47

Operation Guide
3 Alarm Management
NOTE
You can also modify an existing intermittent alarm or repeat event analysis rule by performing the previous
steps.

Step 4 Click Apply.

----End
3.7.5 Setting the Acknowledged and Uncleared Alarm Time

Analysis
By the acknowledged and uncleared alarm time analysis, you can modify the severity of an alarm
that is acknowledged but not cleared in a long period. This helps handle such alarms in time.
Prerequisite
Procedure
Step 2 In the Correlation Rule window, on the Acknowledged and Uncleared Alarm Time
Analysis tab, click New. A rule of the acknowledged and uncleared alarm time analysis is
created.
Step 3 Set the rule of the acknowledged and uncleared alarm time analysis.
3-48
1.
2.
In Alarm, click
3.

Condition dialog box, set the triggering condition and the handling policy.
. In the Select Alarm/Event dialog box, select an alarm.

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
NOTE
You can also modify an existing rule of the acknowledged and uncleared alarm time analysis by performing
the previous steps.

Step 4 Click Apply.

----End
3.7.6 Example of the Alarm or Event Correlation Analysis

This section provides two examples of the correlation analysis to help you understand the
correlation analysis better.
Example of the Correlation Analysis of a Single Alarm

Background
During the period from 5:00 to 23:00 on September 5th, 2005, NE Z raises mass critical alarms
M during upgrade. These critical alarms do not need to be concerned. Therefore, you can
mask alarms M by setting the correlation analysis of a single alarm.
Operation Guide
1.
Open the Correlation Analysis window.

Choose Fault > Settings > Correlation Rule. In the Correlation Rule window, click the
Correlation Analysis tab.
2.
Create a record of alarm or event correlation analysis and set the related parameters.
Click New and set the parameters according to the following table.
Issue 02 (2008-05-31)
Parameter
Operation
Enable
Select the check box.
Correlative Alarm/Event 1
Set it to the major alarm M.
Correlative Alarm/Event 2
You do not need to set it.
Priority
Keep the default value.
Start Time
Set it to 05/09/2007 05:00:00.
End Time
Set it to 05/09/2007 23:00:00.
Condition
Set it to NE Equal Z.

3-49

Operation Guide
3 Alarm Management
Parameter
Operation
Action
Set it to Mask.
Example of the Correlation Analysis of Two Alarms

Background
When a link to an NE is faulty, the NE raises alarm M regularly. At the same time, mass similar
link fault alarms N are raised by this NE or other NEs because of this faulty link. Therefore, the
root cause of fault alarm N is fault alarm M. In correlation analysis, you only need to analyze
and handle alarm M but do not need to analyze alarm N. You can mask alarm N that is raised
after alarm M by setting correlative rules.
Operation Guide
1.
Open the Correlation analysis window.

Alarm/Event Frequency Analysis tab.
2.
Create a record of correlation analysis and set the related parameters.

Parameter
Operation
Enable
Correlative Alarm/Event
1
Set it to alarm M.
Correlative Alarm/Event
2
Set it to alarm N.
Priority
Start Time
End Time
Condition
Set it to Generated Time Range Later than.
Action
For alarm N, set Action to Mask. For alarm M, you do not

need to set Action.
3.7.7 Example of Alarm or Event Frequency Analysis

This section describes an example of the alarm or event frequency analysis so that you can
understand the alarm or event frequency analysis better.
Background
If the major alarm M is reported five times in an hour, the service availability is considered to
be greatly decreased. You need to remove the fault to recover the service availability. To handle
the alarm in time, you can set rules of the alarm or event frequency analysis. Set the triggering
3-50

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
condition to In 1 hours 0 minutes, the number of raised alarms is greater than 5. Set the
handling policy to Change the alarm severity to Critical.
Operation Guide
1.
Open the Alarm/Event Frequency Analysis window.

Alarm/Event Frequency Analysis tab.
2.
Create a record of the alarm or event frequency analysis and set the related parameters.
Click New. Set the parameters according to the following table.
Parameter
Operation
Enable
Alarm/Event
Triggering Condition
Set it to In 1 hours 0 minutes, the number of raised alarms

is greater than 5.
Handling Policy
Set it to Change the alarm severity to Critical.
3.7.8 Example of the Intermittent Alarm or Repeat Event Analysis

This section provides an example of the intermittent alarms or repeat event analyses to help you
understand the intermittent alarm or repeat event analysis better.
Background
If you constantly receive the minor alarm M in a short period of time, it indicates that a device
or service constantly switches between the normal and abnormal status. To deal with the
situation, you can set the intermittent alarm or repeat event analysis. If alarm M is reported and
cleared five times in 10 seconds, change the alarm severity to Major.
Operation Guide
1.
To open the Intermittent Alarm/Repeat Event Analysis window,

Choose Fault > Settings > Correlation Rule . In the Correlation Rule window, click the
Intermittent Alarm/Repeat Event Analysis tab.
2.
Create a record of the intermittent alarm or repeat event analysis and set the related
parameters.
Parameter
Settings
Enable
Alarm/Event
Set it to the minor alarm M.
Triggering
Condition
Set Triggering Condition and Handling Policy to If, in 10

seconds, the alarm is repeated 5 times, change the alarm severity
to Critical.
Handling Policy
Issue 02 (2008-05-31)

3-51

Operation Guide
3 Alarm Management
3.7.9 Example of the Acknowledged and Uncleared Alarm Time

Analysis
This section describes an example of the acknowledged and uncleared alarm time analysis to
help you understand the acknowledged and uncleared alarm time analysis better.
Background
Experience shows that a major alarm M can be cleared 30 minutes after certain measures are
taken. If alarm M is not cleared 30 minutes after you take certain measures, you need to set the
acknowledged and uncleared alarm time analysis to change the alarm severity to critical so that
the alarm can be processed in time.
Operation Guide
1.
Open the Acknowledged and Uncleared Alarm Time Analysis window.

Choose Fault > Settings > Correlation Rule . In the Correlation Rule window, click the
Acknowledged and Uncleared Alarm Time Analysis tab.
2.
Create a record of the acknowledged and uncleared alarm time analysis and set the related
parameters.
Click New. Set the parameters according to the following table.
Parameter
Operation
Enable
Alarm
Triggering Condition
Set Triggering Condition and Handling Policy to If

an acknowledged alarm cannot be cleared in 30
minutes, change the alarm severity to Critical.
Handling Policy
3.8 Setting Alarm Notification

The N2000 UMS provides various methods of alarm notification, such as the alarm panel, alarm
box, email, and SMS. You can customize these methods to obtain the latest alarm information.
3.8.1 Alarm Notification Methods
The N2000 UMS provides various notification methods for you to obtain the alarm information.
3.8.2 Setting the Alarm Panel Style
You can set the style of the alarm panel.
3.8.3 Setting the Alarm Box
This section describes how to set the audio-visual indication and communication parameters of
the alarm box. The alarm box is a device that notifies you of alarms in audio-visual mode.
3.8.4 Setting Alarm Sounds
You can set the alarm sounds for different severities of alarms. When the N2000 UMS receives
an alarm, it plays the sound corresponding to the severity of the alarm to notify you of the alarm.
3-52

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
3.8.6 Setting the Threshold for Uncleared Alarms

After you set the threshold for uncleared alarms, the N2000 UMS prompts you to handle the
alarms when the number of the uncleared alarms reaches the preset threshold.
3.8.7 Setting the Client to Be Displayed on Top When an Alarm Is Received
You can set the N2000 UMS client to be displayed on top when an alarm is received. This helps
you know the alarm information in time.
3.8.1 Alarm Notification Methods

The N2000 UMS provides various notification methods for you to obtain the alarm information.
Alarm
Notification
Method
Description
Alarm panel
The alarm panel is a panel on the client. It displays the status of the
current N2000 UMS alarm data through different color blocks and
statistical data. You can monitor the alarms in the network through
this panel to know the alarm severities and the statistical data.
Topology view
The topology view is a view that shows the device layout on the client.
The colors and status of the device icons in the view indicate the alarm
status of the devices. You can observe the icons to know whether an
alarm occurs in a device and the severity and status of the alarm.
Alarm box
The alarm box is a device that notifies you of alarms in audio-visual

mode. To use the alarm box, connect it to the N2000 UMS server and
set the parameters. You can know new alarms and their severities
through the alarm box.
Sound box
The sound box plays sounds to inform you of the current alarm status.
To use the sound box, connect it to the N2000 UMS client and set the
parameters. You can know new alarms and their severities through the
sound box.
Remote notification
by email or SMS
You can set a mail server, wireless modem, or SMS gateway for
remote notification. The N2000 UMS notifies the maintenance
personnel of alarms by email or SMS.
Alarm browse
window
You can set alarm browse conditions to browse current alarms, history
alarms, and events.

Prerequisite
Context
The settings are effective for only the current client.
Issue 02 (2008-05-31)

3-53

Operation Guide
3 Alarm Management
Procedure
Step 3 On the Local Fault Settings tab, set the display mode of the alarm panel.
NOTE
Display alarm panel at startup: The alarm panel is displayed when the client is started.
Display the alarm panel when a new alarm is reported: The client displays the alarm panel automatically
when receiving a new alarm.
Step 4 Click OK.

----End

Prerequisite
Procedure
Step 1 Choose Fault > Alarm Box.
Step 2 On the Audio-Visual Indication tab, set the severities of the alarms of which you want to notify
users through the alarm box.
3-54

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 3 Click the Communications Parameters tab. Set the serial port and the baud rate.
NOTE
Set the serial port and the baud rate as required. Otherwise, the alarm box fails to work properly.
Step 4 Click OK.

----End
3.8.4 Setting Alarm Sounds

You can set the alarm sounds for different severities of alarms. When the N2000 UMS receives
an alarm, it plays the sound corresponding to the severity of the alarm to notify you of the alarm.
Prerequisite
l
When modifying the alarm sound settings, you need to stop the current alarm sound,
because you need to initialize the sound.
The alarm sound settings are effective for the only local client.
You can click Restore Defaults to restore the alarm sound to the default values.
Context
Issue 02 (2008-05-31)

3-55

Operation Guide
3 Alarm Management
l
Do not stop the sounds of all severities, because you may miss some critical or major alarms
and delay the alarm handling.
Sound playing policy: If the alarm severity corresponding to the current alarm sound is
higher than that of the new one, no action needs to be taken. If the current alarm severity
is lower than or equal to the new alarm severity, stop the current alarm sound and play the
new alarm sound.
When an alarm sound is reset, the sound is not played again according to the alarm statistics
but played when a new alarm is received.
Procedure
Step 2 In the Preferences dialog box, click the Sound tab.
Step 3 On the Sound tab, set the parameters for the sound corresponding to the related alarm severity.
NOTE
If you set the playing duration to -1, the alarm sound will last until you stop the sound or clear the alarm.
To set alarm sounds by alarm name, click Advanced. In the Advanced dialog box, on the Set by Name tab,
select alarms, select an audio file, and set the playing duration. Then click OK.
Step 4 In the Preferences dialog box, click OK.

----End

Prerequisite
Procedure
Step 2 In the Preferences dialog box, click the Color tab.
3-56

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 3 Set the colors for Critical Alarm, Major Alarm, Minor Alarm, and Warning as required.
Step 4 Click OK.
----End
3.8.6 Setting the Threshold for Uncleared Alarms

After you set the threshold for uncleared alarms, the N2000 UMS prompts you to handle the
alarms when the number of the uncleared alarms reaches the preset threshold.
Prerequisite
Procedure
Step 2 In the Preferences dialog box, on the Local Fault Settings tab, set the threshold for uncleared
alarms.
NOTE
When the number of the uncleared alarms reaches this threshold, the N2000 UMS prompts you to handle the
alarms.
Step 3 Click OK.

----End
3.8.7 Setting the Client to Be Displayed on Top When an Alarm Is

Received
You can set the N2000 UMS client to be displayed on top when an alarm is received. This helps
you know the alarm information in time.
Prerequisite
Procedure
Step 3 On the Local Fault Settings tab, select The Client Is on Top When a New Alarm Is
Reported and specify the alarm severity.
Issue 02 (2008-05-31)

3-57
3 Alarm Management

Operation Guide
Step 4 Click OK.

----End
Result
After you complete the settings, when the new alarms of the specified severity are raised, the
client is displayed on top automatically.
3.9 Setting the Alarm Remote Notification

By alarm remote notification, the N2000 UMS can notify the remote maintenance personnel of
a fault in time. You can set various filter conditions to send the notification of only the alarms
that you are concerned about. The alarms that are cleared within the preset delay interval are not
notified because they have no impact on the system. You can set the delay interval.
3.9.1 Setting Communication Parameters for Alarm Remote Notification
After you set the communication parameters for alarm remote notification, the N2000 UMS can
then notify the maintenance personnel of alarms by email or SMS remotely.
3.9.2 Setting the Notification Delay
You can avoid the insignificant alarm notifications by setting the notification delay.
3.9.3 Setting a Remote Notification Rule
After you set an alarm remote notification rule, when an alarm that match the rule is raised, the
N2000 UMS notifies the maintenance personnel of the alarm information by email or SMS so
that the alarm can be handled in time.
3.9.1 Setting Communication Parameters for Alarm Remote

Notification
After you set the communication parameters for alarm remote notification, the N2000 UMS can
then notify the maintenance personnel of alarms by email or SMS remotely.
Prerequisite
Context
The communication parameters are global. Therefore, it applies to all alarm remote notification
rules. You do not need to set the communication parameters for each remote notification rule.
Procedure
Step 1 Choose Fault > Settings > Remote Notification .
3-58

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 2 In the Remote Notification window, click Communication Settings.

Step 3 In the Communication Settings dialog box, click the Email tab. Set the email communication
parameters.
Step 4 In the Communication Settings dialog box, click the SMS tab. Set the SMS communication
parameters.
Step 5 Click OK.
----End
3.9.2 Setting the Notification Delay

You can avoid the insignificant alarm notifications by setting the notification delay.
Prerequisite
Context
l
The notification delay settings are universal. They are effective to all the rules for the alarm
remote notification. Therefore, you do not need to set the notification delay for each remote
notification rule.
If an alarm is cleared immediately after it is raised, a remote notification of the alarm is

unnecessary because the alarm is cleared and the fault is removed. Therefore, you need to
set the notification delay so that you are not remotely notified of the alarm immediately
after the alarm is raised. The N2000 UMS delays the remote notification for a while. If the
alarm is not cleared in this period of time, the N2000 UMS sends a remote notification of
the alarm. In this way, the efficiency of the alarm remote notification is improved.
Procedure
Step 2 In the Remote Notification window, click Delay Settings.
Step 3 In the Delay Settings dialog box, set the notification delay.
----End
3.9.3 Setting a Remote Notification Rule

After you set an alarm remote notification rule, when an alarm that match the rule is raised, the
N2000 UMS notifies the maintenance personnel of the alarm information by email or SMS so
that the alarm can be handled in time.
Prerequisite
Context
To enable the remote notification, configure the communication parameters as follows:
Issue 02 (2008-05-31)

3-59

Operation Guide
3 Alarm Management
Procedure
Step 2 In the Remote Notification window, click New. A rule of the alarm remote notification is
created.
Step 3 Set the rule of the alarm remote notification.

1.
2.
In Remote Notification Condition, click

dialog box, select an alarm.
3.
Set Email, Mobile Phone, Time Zone, Enable Alarm Clearance Notification, and
Remarks.
. In the Remote Notification Condition
NOTE
You can also modify an existing alarm notification rule by performing the previous steps.
You must set either Email or Mobile Phone. You can also set both of them.

not yet applied. If the Enable field is displayed in green
but not yet applied.
, this indicates that the rule is modified but

, this indicates that the rule is newly created
Step 4 Click Apply.

----End
3.10 Dumping Alarms or Events

To ensure that the N2000 UMS works stably and effectively and that the database space is
sufficient, the alarms or events need to be dumped when the amount of the alarms or events
reaches a specified value. Alarm or event dump supports auto dump and manual dump.
3.10.1 Setting Auto Dump of Alarms
After you set alarm auto dump, the history alarms on the N2000 UMS are saved to a specified
file.
3.10.2 Setting Auto Dump of Events
After you set event auto dump, the events on the N2000 UMS are saved to a specified file.
3.10.3 Dumping Alarms Manually
You can dump the history alarms to a specific file manually.
3.10.4 Dumping Events Manually
You can dump the events to a specific file manually.
3.10.1 Setting Auto Dump of Alarms

After you set alarm auto dump, the history alarms on the N2000 UMS are saved to a specified
file.
3-60

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Prerequisite
Context
l
Auto dump applies to only history alarms.
After dump, the source data is deleted from the database immediately.
By default, the N2000 UMS can store a maximum of 50,000 current alarms, 1,000,0000
history alarms, and 120,000 event alarms. You can modify the maximum number of the
history alarms to the maximum of 2,000,000.
By default, auto periodic dump starts between 1:00 and 2:00 in the morning; auto overflow
dump starts automatically in 10 minutes after the number of alarms reaches the maximum.
Procedure
Step 1 Choose System > Database > Dump Settings.
Step 2 In the Dump Settings dialog box, in the Dump Settings navigation tree, select Alarm Data.
Step 3 Set the parameters for alarm dump.

Step 4 Click OK.
----End
3.10.2 Setting Auto Dump of Events

After you set event auto dump, the events on the N2000 UMS are saved to a specified file.
Issue 02 (2008-05-31)

3-61

Operation Guide
3 Alarm Management
Prerequisite
Context
Procedure
Step 1 Choose System > Database > Dump Settings.
Step 2 In the Dump Settings dialog box, in the Dump Settings navigation tree, select Event Data.
Step 3 Set the parameters for event dump.

Step 4 Click OK.
----End
3.10.3 Dumping Alarms Manually

You can dump the history alarms to a specific file manually.
Prerequisite
Context
3-62

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Procedure
Step 1 Choose System > Database > Dump Manually.
Step 2 In the Manual Dump dialog box, in the Manual Dump navigation tree, select Alarm Data.
Step 3 Specify the file path and the file format.

NOTE
The file path and the file format cannot be set here. They are synchronized with the alarm data settings. You
can modify them only by setting the corresponding items in System > Database > Dump Manually.
Step 4 Specify the start time and end time of the alarms.
NOTE
If the start time and end time are not specified, all the history alarms in the database are dumped.
Step 5 Click Query to query the alarms that meet the dump conditions.
Step 6 Click Dump. In the Confirm dialog box, click Yes.
----End
3.10.4 Dumping Events Manually

You can dump the events to a specific file manually.
Prerequisite
Context
Issue 02 (2008-05-31)

3-63

Operation Guide
3 Alarm Management
Procedure
Step 1 Choose System > Database > Dump Manually.
Step 2 In the Manual Dump dialog box, in the Manual Dump navigation tree, select Event Data.
Step 3 Specify the file path and the file format.

NOTE
The dumped file path and the file format cannot be set here. They are synchronized with the alarm data settings.
You can modify them only by setting the corresponding items in System > Database > Dump Settings.
Step 4 Specify the start time and end time of the events.
NOTE
If the start time and end time are not specified, all the events in the database are dumped.
Step 5 Click Query to query the events that meet the dump conditions.
Step 6 Click Dump. In the Confirm dialog box, click Yes.
----End
3.11 Managing the Alarm Panel

The alarm panel monitors the alarms in the entire network in real time and displays statistics of
the alarms by alarm severity and status. The numbers of the uncleared alarms and
unacknowledged alarms of different severities are displayed on the alarm panel. When a new
alarm is reported, the statistics change accordingly.
3.11.1 Alarm Panel
The alarm panel uses different colors to identify different severities of alarms. This helps you
to know the alarms better.
3-64

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
3.11.2 Displaying the Alarm Panel

The thumbnail of the alarm panel is displayed as four color blocks and an event indicator at the
upper right corner of the client. You can also display the complete alarm panel.
3.11.1 Alarm Panel

The alarm panel uses different colors to identify different severities of alarms. This helps you
to know the alarms better.
The thumbnail of the alarm panel is displayed at the upper right corner of the client. Figure
3-5 shows the complete alarm panel.
Figure 3-5 Alarm panel
NOTE
The alarm panel displays only alarm information by default. Event information is displayed only after the event
template is added to the alarm panel.
l
The four colors on the alarm panel represent the four alarm severities: Critical, Major,
Minor, and Warning. The numbers on the color blocks indicate the numbers of the alarms
or events that meet the conditions on the template.
The alarm panel displays the alarm statistical information in real time. When a new alarm
is reported, the corresponding color block blinks one minute and the sound box plays the
alarm sound. At the same time, the statistical information on the alarm panel is refreshed
in real time.
You can add the alarm template to the alarm panel. The alarm panel displays the alarm
statistical information according to the alarm template. By default, the alarm panel is bound
with the All Current Alarms template that displays all the current alarms. When the alarm
panel is displayed as a thumbnail, the displayed alarm statistical information is the statistical
information that meets the conditions specified in the All Current Alarms template. All
templates except The All Current Alarms template can be deleted from the alarm panel.
You can add the event template to the alarm panel. The alarm panel displays the event
statistical information according to the event template.
3.11.2 Displaying the Alarm Panel

The thumbnail of the alarm panel is displayed as four color blocks and an event indicator at the
upper right corner of the client. You can also display the complete alarm panel.
Prerequisite
Issue 02 (2008-05-31)

3-65

Operation Guide
3 Alarm Management
Context
To display the complete alarm panel by default, choose File > Preferences . In the
Preferences dialog box, click the Local Fault Setting tab, and then select Display alarm panel
at startup.
Procedure
Choose Fault > Show Alarm Panel, or click
on the toolbar.
----End

Prerequisite
Context
The settings are effective for only the current client.
Procedure
Step 3 On the Local Fault Settings tab, set the display mode of the alarm panel.
3-66

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
NOTE
Display alarm panel at startup: The alarm panel is displayed when the client is started.
Display the alarm panel when a new alarm is reported: The client displays the alarm panel automatically
when receiving a new alarm.
Step 4 Click OK.

----End
3.12 Managing the Alarm Box

The common alarm box of the Huawei Technologies Co., Ltd. provides audio-visual alarms.
You can set the conditions for filtering alarms to the alarm box.
3.12.2 Stopping the Alarm Sound
You can use this function to stop the alarm box sound.
3.12.3 Synchronizing the Alarm Box Data
You can use this function to send the alarm data from the N2000 UMS to the alarm box so that
the alarm box can correctly indicate the current alarm status.

Prerequisite
Procedure
Step 2 On the Audio-Visual Indication tab, set the severities of the alarms of which you want to notify
users through the alarm box.
Issue 02 (2008-05-31)

3-67

Operation Guide
3 Alarm Management
Step 3 Click the Communications Parameters tab. Set the serial port and the baud rate.
NOTE
Set the serial port and the baud rate as required. Otherwise, the alarm box fails to work properly.
Step 4 Click OK.

----End
3.12.2 Stopping the Alarm Sound

You can use this function to stop the alarm box sound.
Prerequisite
Procedure
Step 2 In the Alarm Box dialog box, on the Audio-Visual Indication tab, click Stop Current Alarm
Sound.
3-68

Issue 02 (2008-05-31)

Operation Guide
3 Alarm Management
Step 3 Click OK.

If the alarm box is playing a sound, the alarm sound stops.
----End
3.12.3 Synchronizing the Alarm Box Data

You can use this function to send the alarm data from the N2000 UMS to the alarm box so that
the alarm box can correctly indicate the current alarm status.
Prerequisite
Procedure
Choose Fault > Synchronize Alarm Box Data.
----End
Issue 02 (2008-05-31)

3-69

Operation Guide
Performance Management
About This Chapter

This section describes how to create a performance statistics task, how to monitor the device
performance, and how to manage the performance data.
4.1 Overview of the Performance Measurement
This section describes the basic concepts and principle of the performance measurement.
4.2 Managing Performance Measurement Tasks
This section describes the probable state that a task can experience and how to manage
performance measurement tasks.
4.3 Querying the Performance Data
This section describes how to query, save, and print the performance data, and search for the
maximum or minimum value.
4.4 Monitoring the Device Performance
This section describes the detailed process for monitoring the device performance using an
example for monitoring the AMG traffic, how to set the performance threshold template and
threshold records, and how to query the performance threshold alarms.
4.5 Measuring the Performance Data
This section describes the measurement types of the performance data supported by the N2000
UMS, how to carry out the time distribution measurement, time distribution comparison
measurement, global traffic measurement, and how to save and print measurement result. The
measurement result can be displayed in multiple figures to provide uses with the device running
status and data reference for optimizing the network.
4.6 Dumping the Performance Data
This section describes how to dump the performance data.
4.7 Configuring the Performance Northbound Interface
This operation enables you to configure the parameters of the performance northbound interface,
generate a northbound interface file with the collected performance data periodically, and send
the file to the upper NMS and the third party NMS.
Issue 02 (2008-05-31)

4-1

Operation Guide
4.1 Overview of the Performance Measurement

This section describes the basic concepts and principle of the performance measurement.
The N2000 UMS provides the performance measurement. The performance measurement
enables you to:
l
Collect the performance data of the whole network
Query the measurement result on the graphic user interface (GUI)
4.1.1 Basic Concepts

This section describes basic concepts of the performance measurement, measuring object,
measuring entity, measuring unit, and measuring time.
4.1.2 Device Type Definition
This section describes the types of devices managed by the N2000 UMS.
4.1.3 Performance Measurement Principle of IMS Devices
This section describes the performance measurement principle and diagram of IMS devices.
4.1.4 GUI of the Performance Measurement
This section describes the structure and display information about the N2000 UMS performance
measurement GUI.
4.1.1 Basic Concepts

This section describes basic concepts of the performance measurement, measuring object,
measuring entity, measuring unit, and measuring time.
Performance Measurement
Performance measurement refers to various measurement activities on the device, including the
traffic measurement, the measurement on system resources, signaling, ports, and interior
operation status. Performance measurement provides reliable data reference for network
measurement, networking plan and operation management.
Measuring Object
It is a physical or logical entity, or a combination of various entities to be measured, such as a
trunk circuit group, common control component, or destination. For the SNMP device, a port or
board can be an object.
Measuring Entity
It is also called measurement item. It is a specific parameter (for example, the traffic, call
attempts, and average occupied time) for which the data must be collected during the
measurement.
Measuring Unit
It is a specific measurement category, such as the measurement of the incoming traffic, outgoing traffic, and internal traffic. In performance measurement, the measuring unit specifies
what to be measured. Each measuring unit consists of one or more measuring entities.
4-2

Issue 02 (2008-05-31)

Operation Guide
Measuring Time
The measuring time specifies when to measure the entity. The measuring time contains start
date, end date, polling period, repeat period, and time segments. You can set it from four aspects,
such as date range, repeat period, time segment and polling period.
NOTE
The set time of all the timers related to the performance measurement on the N2000 UMS server is not the
DST time on the device.
Restrictions
Description
Date Range
The date range specifies the start date and the end date of a measurement
task. The task starts the measurement at the specified start date and stops it
at the specified end date.
Repeat Period
The repeat period specifies the frequency of measurement, such as daily,

weekly and monthly.
l
Daily: The measurement is carried out everyday.
Weekly: The measurement is carried out on a specific day or days in a

week.
Monthly: The measurement is carried out on specific days in a month.
By default, the repeat period is daily. The date range and the repeat period
of performance measurement specify on which days the measurement is
carried out.
Time
Segments
The time segments specifies in which time segment of the day the
measurement is carried out. The measurement mode of each measurement
day is the same. You can divide each day into three time segments at most,
without overlaps with one another. The default time segment is [00:00,
23:59], which represents collecting data for 24 hours.
To re-divide the time segments, delete the default time segment first, and
then specify the start time and end time for each time segment. For example,
you can specify a measurement task to run during a certain segment on each
Saturday and Sunday, such as [9:00, 11:00), [13:00, 16:00), and [20:00,
21:00). Here 9.00 represents a closed time segment, 11.00 represents an
open time segment.
Each time segment starts at a specified time (precise to minute). The
measurement lasts for several consecutive periods. Within the defined time
segments, the tasks run based on the polling period. The different time
segments cannot be overlapped.
Issue 02 (2008-05-31)

4-3

Operation Guide
Restrictions
Description
Polling Period
The polling period is interval at which the performance data is output, that
is, how often the performance data is output.
Such as 5 minutes, 15 minutes, 30 minutes, 1 hour or 1 day. By default, it
is 15 minutes. In the time segments, the system measures data based on a
specific polling period, and then outputs the results.
The polling period cannot be greater than the shortest time length in three
time segments of a day.
Polling period determines how often in each time segment the system output
the measurement result.
For example, you set time attributes of a task as follows:
l
Start Date: 2005-01-01
End Date: 2005-02-01
Repeat Period: weekly
Selected date: Saturday and Sunday
Time segments: 09:00-12:00
Polling period: 30 minutes
After the preceding settings, the system measures data every 30 minutes
during [09:00, 12:00) every Saturday and Sunday from 2005-01-01 to
2005-02-01. That is, the system collects measurement data at 09:30, 10:00,
10:30, 11:00, and 11:30.
Entity Threshold
The threshold is a pre-set standard for measuring entity, including upper limit and lower limit.
If the entity value is more than the upper limit or less than the lower limit during the measurement
period, an alarm will be raised for that threshold. The upper limit and lower limit can be set
according to the actual conditions. Not all entities have the threshold attribute.
Object Type
It refers to the different methods used for describing restrictions. Generally, each restriction can
have several object types for selection. For example, for the restriction of Which incoming
users to be measured, the incoming user can be described by external code, such as dialed
number set + telephone number, or by internal code, such as module number + user type + user
logical number. But you can select only one method of them.
Measurement Type
It is the combination of a specific entity and object, such as Trunk Group Traffic and Outgoing
Call Attempts.
Measurement Task
Measurement task is a description of a specific traffic measurement task, containing four
attributes, such as object, index, time and output. Object attribute decides which to be measured.
4-4

Issue 02 (2008-05-31)

Operation Guide
Index attribute decides what to be measured. Time attribute decides when to measure the
performance data. Output attribute decides how to output the measurement result.
4.1.2 Device Type Definition

This section describes the types of devices managed by the N2000 UMS.
SNMP Device
The SNMP device supports the SNMP protocol. The SNMP device can be defined in
management information base (MIB), such as UA5000(PVMV1). The N2000 UMS can manage
the SNMP devices, by reading and writing the managed objects in the MIB.
MML Device
The MML device supports the MML protocol, providing MML interfaces to the N2000 UMS,
such as SoftX3000, iGWB, and MRS6100. The N2000 UMS can manage and maintain the MML
device using MML commands.
IMS Device
IMS Device refers to a device that works in the IMS network, including IP Centrex, ATCA
device, MSOFTX3000, UMG8900_IMS, and MRS6200. Where, MSOFTX3000 and
UMG8900_IMS are MML devices. IP Centrex, ATCA device, and MRS6200 are SNMP
devices.
For IMS devices, only the ATCA device supports the performance measurement function of the
N2000 UMS.
4.1.3 Performance Measurement Principle of IMS Devices

This section describes the performance measurement principle and diagram of IMS devices.
Measurement Principle
The N2000 UMS realizes the performance measurement of the whole network through the
performance measurement tasks on the BAM of IMS devices.
1.
For collecting performance measurement, N2000 UMS server has to synchronize the task
present on the device.
2.
The IMS device sends the result file containing the performance data to the N2000 UMS
and when the file is generated.
3.
The N2000 UMS saves the data in the database.

NOTE
If you have defined the performance threshold alarm, and the performance index exceeds the limit, the threshold
alarm is reported.
Principle Diagram
Figure 4-1 shows the performance measurement principle of IMS devices.
Issue 02 (2008-05-31)

4-5

Operation Guide
Figure 4-1 Principle diagram of IMS device performance measurement
4.1.4 GUI of the Performance Measurement

This section describes the structure and display information about the N2000 UMS performance
measurement GUI.
The performance measurement involves the GUIs of Task Management, Data Analysis,
Configure Data Dump, and Data Integrity. The navigation tree is in the left pane and the
topological view is in the right pane. This section uses the GUI of the Task Management as an
example. The device types and task relations are displayed in the left pane. The Task State,
Task Name, Device Name, Polling Period, Collect Data, and Measuring Unit are listed in
the right pane.
Figure 4-2 shows the GUI of the performance measurement.
4-6

Issue 02 (2008-05-31)

Operation Guide
Figure 4-2 GUI of the performance measurement
4.2 Managing Performance Measurement Tasks

This section describes the probable state that a task can experience and how to manage
performance measurement tasks.
Managing performance measurement tasks consists of the following operations:
l
Querying performance measurement tasks
Suspending a performance measurement task
Deleting a performance measurement task
Synchronizing a performance measurement task
Modifying a performance measurement task
4.2.1 Task State

This section describes the different states of performance measurement task.
4.2.2 Querying Performance Measurement Tasks
This operation enables you to view all the task information on the device including the task
name, device type, measuring unit, measuring entity, polling period, time segment, time zone,
and repeated period.
4.2.3 Querying the Measuring Object of the Performance Measurement Task
This operation enables you to query the measuring object of the performance measurement task
and search for measuring objects.
Issue 02 (2008-05-31)

4-7

Operation Guide
4.2.1 Task State

This section describes the different states of performance measurement task.
In the life cycle, a measurement task might go through a series of states.
Table 4-1 shows the details about task states.
Table 4-1 Measurement task state description
State
Description
Not started
It indicates that the task is created. The current device time is earlier than the
start time of a task. That is, the task is not started.
Running
It indicates that the current device time is between the start time and the end
time of a task, and the task is not suspended. That is, the task is running.
Suspended
It indicates that the task is inactive. In this case, the task outputs no result.
The suspended task can be activated again.
Terminated
It indicates that the current device time is later than or equal to the end time
of a task. That is, the task is complete.
4.2.2 Querying Performance Measurement Tasks

This operation enables you to view all the task information on the device including the task
name, device type, measuring unit, measuring entity, polling period, time segment, time zone,
and repeated period.
Prerequisite
l
The device communicates with the N2000 UMS normally.
There are performance tasks on the N2000 UMS.
Procedure
Step 1 Choose Performance > Task Management from the main menu to open the Task
Management window.
Step 2 On the Task Management navigation tree, select a task node; or double-click a record from the
task list in the right pane.
Step 3 View the basic information about the performance task on the Basic Info tab.
NOTE
By default, the system displays the Basic Info. tab.
----End
4-8

Issue 02 (2008-05-31)

Operation Guide
4.2.3 Querying the Measuring Object of the Performance

Measurement Task
This operation enables you to query the measuring object of the performance measurement task
and search for measuring objects.
Prerequisite
l
The device communicates with the N2000 UMS normally.
Procedure
Management window.
Step 2 On the Task Management... navigation tree, select a task node; or double-click a record from
the task list in the right pane.
Step 3 In the window that appears, click the Measuring Object tab to view the measuring object
information about the measurement task. It displays information on the device name, object type,
and measuring object.
NOTE
If you want to fast locate a measuring object, you can input the object name in the Measuring Object text box,
and click Search to fast locate the measuring object.
----End
4.3 Querying the Performance Data

This section describes how to query, save, and print the performance data, and search for the
maximum or minimum value.
NOTE
You cannot query the performance data collected by the SNMP large-capacity performance measurement
task (also called batch collection task) on the GUI of the N2000 UMS. The collected performance data is
exported to an NBI file that is provided to the upper NMS or a third-party NMS for analysis.
4.3.1 Querying the Performance Data by Time Segment

This operation enables you to query the performance data of the measurement task by time
segment.
4.3.2 Querying the Performance Data by User-Defined Condition
This operation enables you to query the performance data of the measurement task by userdefined condition.
4.3.3 Querying the Maximum and Minimum Performance Values
This operation enables you to find the maximum value or minimum value of the queried
performance data.
4.3.4 Saving the Performance Data to a File
This operation enables you to save the queried performance data. The data can be saved in the
html, text, or excel format.
4.3.5 Printing the Performance Measurement Data
Issue 02 (2008-05-31)

4-9

Operation Guide
This operation enables you to print the performance measurement data.
4.3.1 Querying the Performance Data by Time Segment

This operation enables you to query the performance data of the measurement task by time
segment.
Prerequisite
Context
The performance data collected by the SNMP large-capacity performance measurement task
(batch collection task) cannot be queried on the GUI of the N2000 UMS. The collected
performance data is exported to an NBI file that is provided to the upper NMS or a third-party
NMS for analysis.
Procedure
Step 1 Choose Performance > Task Management from the main menu to display the Task
Management window.
Step 3 In the window that appears, click the Data Info. tab. From the Condition drop-down list, select
the desired time segment. The user-defined option is described in the next section.
Step 4 Query the performance data in the result list.
----End
4.3.2 Querying the Performance Data by User-Defined Condition

This operation enables you to query the performance data of the measurement task by userdefined condition.
Prerequisite
Context
Up to three time segments can be set in a day, such as [10:00, 14:00), [14:00, 18:00), and [18:00,
22:00). The start time is closed interval and the end time is open interval. The end time of the
previous segment can be repeated with the start time of the later one. Each segment cannot be
overlapped, such as [10:00, 14:00), [13:00, 18:00).
Procedure
Step 1 Choose Performance > Task Management... from the main menu to open the Task
Management window.
4-10

Issue 02 (2008-05-31)

Operation Guide
Step 3 In the window that appears, click the Data Info. tab. From the Condition drop-down list, select
User Defined.
In the dialog box that appears, the system displays the Time tab.
Step 4 Configure Query Time Range and Time Segments, as shown in the following figure.
Step 5 Click the Measuring Entity tab, and configure the measuring entities and their logical type, as
shown in the following figure.
Step 6 Click the Measuring Object tab, and select the measuring object, as shown in the following
figure.
Issue 02 (2008-05-31)

4-11

Operation Guide
NOTE
The system selects all the measuring objects by default. You can also click User-defined Measuring Objects
and Select Obj... to select the desired measuring objects in the dialog box that appears. Click OK.
Step 7 Click OK to view the performance data in the Task Management window.
----End
4.3.3 Querying the Maximum and Minimum Performance Values

This operation enables you to find the maximum value or minimum value of the queried
performance data.
Prerequisite
You have queried the original performance data in the specified time segment or in the userdefined condition.
Procedure
Management window.
Step 2 On the Task Management navigation tree, select a task node; or double-click a record in the
right pane.
Step 3 In the window that appears, click the Data Info. tab. Select the filtering criteria from the
Condition drop-down list, and query the measurement data.
Step 4 In the performance data result list, select a record, right-click, and choose Peak Search.
Step 5 In the dialog box that appears, select Object, Entity, and Search Type.
4-12

Issue 02 (2008-05-31)

Operation Guide
Step 6 Click Search to display the result, as shown in the following figure.
NOTE
Select a record from the result list in the preceding figure, and click Go to to locate the performance data of the
result. Click Next. Only if there is one record in the list, the Next button displays as Search.
Step 7 Click Close.

----End
4.3.4 Saving the Performance Data to a File

This operation enables you to save the queried performance data. The data can be saved in the
html, text, or excel format.
Prerequisite
You have queried the performance data to be saved.
Context
You can save all the queried performance data or the performance data displayed in the current
window.
Issue 02 (2008-05-31)

4-13

Operation Guide
Procedure
Management window.
right pane.
Step 3 In the dialog box that appears, click the Data Info. tab. Select the filtering criteria from the
Condition drop-down list, and view the measurement data.
Step 4 In the Performance Data Management window, click Save to open the Save dialog box.
Step 5 Select the data type to Screen Data or All Data.
Step 6 Click OK.
Step 7 In the dialog box that appears, locate a saving path, input a file name, and select a file type.
Step 8 Click Save.
----End
4.3.5 Printing the Performance Measurement Data

This operation enables you to print the performance measurement data.
Prerequisite
l
The printer is setup on the computer.
You have queried the performance data.
Context
You can print all the performance data or the performance data displayed in the current window.
Procedure
Management window.
right pane.
Step 3 In the dialog box that appears, click the Data Info. tab. Select the filtering criteria from the
Condition drop-down list, and view the measurement data.
Step 4 On the performance data querying interface, click Print to open the Print dialog box.
Step 5 Select the data type to Screen Data or All Data, and click OK.
Step 6 In the dialog box that appears, click Print.
Step 7 In the dialog box that appears, set the printing condition.
Step 8 Click OK.
----End
4-14

Issue 02 (2008-05-31)

Operation Guide
4.4 Monitoring the Device Performance

This section describes the detailed process for monitoring the device performance using an
example for monitoring the AMG traffic, how to set the performance threshold template and
threshold records, and how to query the performance threshold alarms.
With the function, you can set the performance alarm threshold to monitor the device
performance for maintenance. When the performance data does not fall within the threshold, an
alarm is generated.
NOTE
The SNMP large-capacity performance measurement task does not support threshold operations. That
is, you cannot receive threshold alarms by configuring a performance threshold. In addition, the IMS
does not support the threshold operations.
The performance alarm threshold is meaningful only when the performance measurement task exists.
The performance threshold alarm falls into four levels:

l
Critical alarm
Major alarm
Minor alarm
Warning
In the performance threshold template, you can set the lower limit and upper limit for these four
alarm levels. These limits are totally independent. If the message reported by a performance
measurement task meets several alarm levels, the system reports alarms of each level.
Assume that the measuring unit is lower than 100% for the CPU Occupancy.
l
If the CPU occupancy is 75%85%, a minor alarm is generated.
If it is 85%95%, a major alarm is generated.
If it is 95%100%, a critical alarm is generated.
If the measurement result is 95%, the system reports a critical alarm and a major alarm.
If the measurement result is 85%, the system reports a major alarm and a minor alarm.
Under the following conditions, a cleared alarm is generated for the performance threshold
alarm.
l
Deleting a performance threshold template
Deleting a performance threshold record
Deleting a performance measurement task
Deleting the device which generates the alarm
The measurement index does not meet the alarm threshold
4.4.1 Flowchart for Monitoring the Device Performance

This section describes how to monitor the device performance.
4.4.2 Creating a Performance Threshold Template
This operation enables you to create a performance threshold template for the specified
measuring unit of the specified device type.
Issue 02 (2008-05-31)

4-15

Operation Guide
4.4.3 Creating a Performance Threshold Record

This operation enables you to create performance threshold records of the specified device, task,
and measuring object according to the selected performance threshold template.
4.4.1 Flowchart for Monitoring the Device Performance

This section describes how to monitor the device performance.
When performance tasks of the related measuring units exist, the flow of monitoring device
performance is as follows:
1.
Set a threshold template for the measuring entity of the specified device type. In this case,
the alarm level and alarm generation condition of the measuring unit can be defined.
2.
Set a threshold record for measurement tasks and measuring objects of a specific device of
a certain type according to the threshold template.
3.
During the data collection, the N2000 UMS checks the performance data with alarm
thresholds.
l
If the performance data exceeds the threshold, an alarm is generated.
When the performance data recovers, a recovery alarm is generated.
Flowchart
Figure 4-3 shows the flowchart for monitoring the device performance.
Figure 4-3 Flowchart for monitoring the device performance
4.4.2 Creating a Performance Threshold Template

This operation enables you to create a performance threshold template for the specified
measuring unit of the specified device type.
4-16

Issue 02 (2008-05-31)

Operation Guide
Context
l
The threshold template name cannot be repeated with other template names.
For the advanced configuration, you can set 1-3 time segments in a day, such as [10:00,
14:00], [14:01, 18:00], and [18:01, 22:00]. All the time segments are closed interval. The
end time of the previous segment cannot be repeated with the start time of the later one.
Each segment cannot be overlapped, such as [10:00, 14:00], [13:00, 18:00].
For the advanced configuration, if you select the Compare with previous check box (the
options are Hour, Day, Week, and Month), the performance data collected this time is
compared with that collected in the last period. An alarm is generated when the difference
reaches the threshold. For example, if you set Compare with previous to Hour, it indicates
that the performance data collected this time is compared with that collected before one
hour. The threshold alarm is generated when the difference reaches the threshold.
Procedure
Step 1 Choose Performance > Configure > Threshold Template... from the main menu to display
the Threshold Template Management window.
Step 2 Select Device Type and Measuring Unit, and click Create in the lower right corner; or rightclick the threshold template list, and choose Create Template. The Create Template dialog
box appears.
Step 3 In the Template Name text box, input the name of the performance template.
Step 4 From the Measuring Unit drop-down list, select the desired measuring unit.
Step 5 From the Alarm Level drop-down list, select the alarm level of the threshold template.
Step 6 Click the Simple or Advanced check box.
l
Issue 02 (2008-05-31)
The simple configuration is described as follows:

1.
Click the Simple check box.
2.
Select the desired Measuring Entity, and set the lower or upper threshold, as shown
in the following figure. The upper threshold must be larger than the lower threshold.

4-17

Operation Guide
NOTE
An alarm is generated when the performance data is lower or higher than the threshold.
3.
l
4-18
Click Detail Expression to view the detailed information about the template
expression.
The advanced configuration is described as follows:

1.
Click the Advanced check box.
2.
Click the time segment tab, and set the start time and end time.
3.
Click A, select Measuring Entity and Operator, and select or input Entity/Value.
Other threshold conditions can be set similarly.
4.
Double-click an Alias Name record, click a condition button, and double-click other
Alias Name records to add the template expression. The following figure shows the
complete configuration.

Issue 02 (2008-05-31)

Operation Guide
NOTE
You can also select the Compare with previous check box, and select the desired period from the
drop-down list.
5.
Click Detail Expression to view the detailed information about the template
expression.
Step 7 Click OK.

----End
4.4.3 Creating a Performance Threshold Record

This operation enables you to create performance threshold records of the specified device, task,
and measuring object according to the selected performance threshold template.
Prerequisite
l
A performance measurement task is created for the selected measuring unit.
A performance threshold template is created for the measuring unit.
Issue 02 (2008-05-31)

4-19

Operation Guide
You have not created any performance threshold record for the current performance task,
performance threshold template, and the selected measuring object.
Once you create the threshold record, a threshold alarm is generated when the threshold
condition is met.
After the device or task of the measuring unit is deleted, the performance threshold record
is deleted.
After the performance threshold template is deleted, the performance threshold record is
deleted.
A measuring object can create multiple threshold records by using different threshold
templates.
A task, measuring object, or threshold template cannot create multiple threshold records.
Context
Procedure
Step 1 Choose performance > Task Management... from the main menu to display the Task
Management window.
Step 2 On the task management navigation tree, select a task node, or double-click a record in the right
pane.
Step 3 In the window that appears, click the Threshold Info. tab, and click Create in the lower right
corner; or right-click the threshold record list, and choose Create Threshold . The Create
Threshold dialog box appears.
Step 4 In the Threshold Name text box, input the record name.
Step 5 In the Template Name drop-down list, select the performance threshold template of the
measuring unit.
Step 6 Click Select Object... to select at least one measuring object in the dialog box that appears, and
click OK to return to the Create Threshold dialog box, as shown in the following figure.
Step 7 Click OK.

----End
4-20

Issue 02 (2008-05-31)

Operation Guide
4.5 Measuring the Performance Data

This section describes the measurement types of the performance data supported by the N2000
UMS, how to carry out the time distribution measurement, time distribution comparison
measurement, global traffic measurement, and how to save and print measurement result. The
measurement result can be displayed in multiple figures to provide uses with the device running
status and data reference for optimizing the network.
NOTE
The SNMP large-capacity performance measurement task cannot measure the performance data.
4.5.1 Time Distribution Measurement

This operation enables you to measure one or more measuring entities of a measuring object
according to different periods within the set time range. You can also measure one measuring
entity of one or more measuring objects according to different periods within the set time range.
The measurement result can be displayed in a table, a diagram, or a curve.
4.5.2 Time Distribution Comparison Measurement
The time distribution comparison measurement enables you to compare the performance data
of one measuring unit in different time segments. The measurement result can be displayed in
a table, a bar chart, or a curve.
4.5.3 Saving the Measurement Results to a File
This operation enables you to save the measurement results of the performance data. The data
can be saved in the html, text, or excel format.
4.5.4 Printing the Measurement Result
This operation enables you to print the measurement result of the performance data.
4.5.1 Time Distribution Measurement

This operation enables you to measure one or more measuring entities of a measuring object
according to different periods within the set time range. You can also measure one measuring
entity of one or more measuring objects according to different periods within the set time range.
The measurement result can be displayed in a table, a diagram, or a curve.
Prerequisite
l
You have created a performance measurement task and the task has collected performance
data.
Context
When Period is Week, Month, and Year, you can click SetTime to set up to three time
segments. Up to three time segments can be set in a day, such as [10:00, 14:00), [14:00, 18:00),
and [18:00, 22:00). The start time is closed interval and the end time is open interval. The end
time of the previous segment can be repeated with the start time of the later one. Each segment
cannot be overlapped, such as [10:00, 14:00), [13:00, 18:00).
NOTE
The SNMP large-capacity performance measurement task (batch collection task) does not support the time
distribution measurement.
Issue 02 (2008-05-31)

4-21

Operation Guide
Procedure
Step 1 Choose Performance > Data Analysis > Time Distribution Analysis... from the main menu
to open the Time Distribution Analysis window. In the upper area of the window, the
parameters are displayed, as shown in the following figure.
Step 2 In the Device Type drop-down list, select the desired device type.
Step 3 Click Select Device to select a device.
Step 4 In the Measuring Unit drop-down list, select the desired measuring unit.
Step 5 In the Analysis Type drop-down list, select the analysis type, such as Single Measuring
Object and Multiple Measuring Object.
NOTE
When you select many devices, Analysis Type is Multiple Measuring Object.
Step 6 In the Time Range area, click the Period drop-down list, and select a task period.
Step 7 Click ... next to Start Time and specify the start time in the dialog box that appears; or select
the Latest option and set a time range related to the current system time.
Step 8 Click Measuring Object. In the dialog box that appears, select the desired measuring object,
and click OK.
Step 9 Click Measuring Entity. In the dialog box that appears, select the measuring entity, and click
OK.
Step 10 Click the Formula column, and set the related operator, such as SUM, AVG, MIN, and MAX.
Step 11 Click Query or Apply to display the result, as shown in the following figure.
----End
4-22

Issue 02 (2008-05-31)

Operation Guide
4.5.2 Time Distribution Comparison Measurement

The time distribution comparison measurement enables you to compare the performance data
of one measuring unit in different time segments. The measurement result can be displayed in
a table, a bar chart, or a curve.
Prerequisite
You have created a performance measurement task and the task has collected performance data.
Context
l
You must set at least two different Start Time.
When Period is Week, Month, and Year, you can click SetTime to set up to three time
segments. Up to three time segments can be set in a day, such as [10:00, 14:00), [14:00,
18:00), and [18:00, 22:00). The start time is closed interval and the end time is open interval.
The end time of the previous segment can be repeated with the start time of the later one.
Each segment cannot be overlapped, such as [10:00, 14:00), [13:00, 18:00).
NOTE
The SNMP large-capacity performance measurement task (batch collection task) does not support the time
distribution comparison measurement.
Procedure
Step 1 Choose Performance > Data Analysis > Compare Time Analysis... from the main menu to
open the Compare Time Analysis window. In the upper area of the window, the parameters
are displayed, as shown in the following figure.
Step 2 In the Device Type drop-down list, select the desired device type.
Step 3 In the Device Name drop-down list, select the desired device.
Step 4 In the Measuring Unit drop-down list, select the desired measuring unit.
Step 5 In the Analysis Type drop-down list, select the desired analysis type.
Step 6 In the Time Range area, select a period for comparison, and set two different start times. The
start time cannot be later than the current time.
l
Click + to add a time record.
Select a time record, click - to remove it.
Step 7 Click Measuring Object. In the dialog box that appears, select the desired measuring object.
Step 8 Click Measuring Entity. In the dialog box that appears, select the measuring entity.
Step 9 Click the Formula column, and set the related operator, such as SUM, AVG, MIN, and MAX.
Step 10 Click Query to display the result, as shown in the following figure.
Issue 02 (2008-05-31)

4-23

Operation Guide
----End
4.5.3 Saving the Measurement Results to a File

This operation enables you to save the measurement results of the performance data. The data
can be saved in the html, text, or excel format.
Prerequisite
You have queried the performance data to be saved.
Context
If the display type of the measurement report is Table and the report is saved as a HTML file,
the different parameters in the measurement report are saved as a table. If the display type of
the measurement report is Multiple Bar or Curve and the report is saved as a HTML file, the
different parameters in the measurement report are saved as a figure.
Procedure
Step 1 Query the performance measurement data in the Time Distribution Analysis, Compare Time
Analysis, and Global Traffic Flow Analysis windows.
Step 2 In the Performance Data Management window, click Save to open the Save dialog box.
Step 3 In the dialog box that appears, locate a saving path, input a file name, and select a file type.
Step 4 Click Save.
----End
4.5.4 Printing the Measurement Result

This operation enables you to print the measurement result of the performance data.
Prerequisite
4-24
You have queried the performance data.
The printer is connected to the current server.

Issue 02 (2008-05-31)

Operation Guide
Procedure
Step 1 Query the performance measurement data in the Time Distribution Analysis, Compare Time
Analysis, and Global Traffic Flow Analysis windows.
Step 2 On the performance data querying interface, click Print to open the Print dialog box.
Step 3 Set the print conditions.
l
The measurement result is a table format: The pages to be printed are selected in the preview
window.
The measurement result is not a table format: Set the print conditions after you select a
view range of the print or preview.
Step 4 Click Print. In the dialog box that appears, set the printing condition, and click OK.
----End
4.6 Dumping the Performance Data

This section describes how to dump the performance data.
There are two ways to dump the performance data:
l
Automatic dumping
Immediate dumping (Manual dumping)
There are two modes for dumping the performance data automatically:
l
Periodic dumping
The performance data is dumped periodically according to the set time. The performance
data is dumped to the local disk from the database.
Overflow dumping
When the database capacity for saving the performance data exceeds the set threshold (The
threshold is configured in the $N2000ROOT/server/conf/DataAdminDm.cfg, and the
default value is 80%), the performance measurement system dumps the overflow data. The
system dumps part or all the performance data (the percentage is configured in the
$N2000ROOT/server/conf/DataAdminDm.cfg, and the default value is 20%) to the local
disk from the database.
The immediate dumping indicates that the performance data that is generated earlier than the
specified time is dumped.
4.6.1 Configuring the Default Condition for Automatically Dumping Performance Data
This operation enables you to configure the default condition, such as default period and data
saving path, for automatically dumping the performance data.
4.6.2 Configuring the User-Defined Condition for Automatically Dumping Performance Data
This operation enables you to configure the user-defined condition for automatically dumping
performance data.
4.6.3 Dumping Performance Data Immediately
This operation enables you to dump performance data immediately.
4.6.4 Configuring the Overflow Dump Condition for Performance Data
Issue 02 (2008-05-31)

4-25

Operation Guide
This operation enables you to configure the overflow dump condition for performance data.
When the performance data in the database exceeds the set threshold for saving the performance
data, the performance measurement system dumps the overflow data.
4.6.1 Configuring the Default Condition for Automatically

Dumping Performance Data
This operation enables you to configure the default condition, such as default period and data
saving path, for automatically dumping the performance data.
Context
l
By default, all the MUs that are not configured with the user-defined condition use the
default condition for dumping the performance data. That is, the default dump condition is
valid only for the performance data collected by a new performance measurement task.
The performance measurement system dumps the performance data according to the set
time restriction at 00:00 every day.
You can configure the time for automatically dumping the performance data in the
configuration file. The time is regarded as the automatic dump time.
Procedure
Step 1 Choose Performance > Data Dump > Auto Dump... from the main menu.
Step 2 In the dialog box that appears, click the Default Configuration tab.
Step 3 Configure the default dump condition, as shown in the following figure.
NOTE
If you do not select the Save Data check box, the performance data is deleted from the database directly
without being saved.
Step 4 Click OK.

----End
4-26

Issue 02 (2008-05-31)

Operation Guide
4.6.2 Configuring the User-Defined Condition for Automatically

Dumping Performance Data
This operation enables you to configure the user-defined condition for automatically dumping
performance data.
Prerequisite
The device is added to the N2000 UMS and the performance measurement task is created for
the MU of the device.
Context
The configured user-defined dump condition is valid for all the MUs that have created
performance measurement tasks. The performance measurement system periodically dumps the
performance data according to the configured conditions.
Procedure
Step 1 Choose Performance > Data Dump > Auto Dump... from the main menu.
By default, the Customized Configuration tab is displayed.
Step 2 On the MU Template tree, select a template.
Step 3 Configure the user-defined dump condition, as shown in the following figure.
NOTE
If you want to change the dump condition, click Reset to fast reset the user-defined condition to the
default value.
Step 4 Click OK.

----End
Issue 02 (2008-05-31)

4-27

Operation Guide
4.6.3 Dumping Performance Data Immediately

This operation enables you to dump performance data immediately.
Prerequisite
The device is added to the N2000 UMS and the performance measurement task is created for
the MU of the device.
Procedure
Step 1 Choose Performance > Data Dump > Prompt Dump... from the main menu.
Step 2 Select a device type from the Device Type drop-down list.
Step 3 Select a template from the Measuring Unit drop-down list.
Step 4 Click
next to the End Data text box, and set from which date (00:00 of the day) all the
collected data is dumped.
Step 5 Select or clear the Save Data check box, as shown in the following figure.
NOTE
Step 6 Click Start.

Step 7 In the prompt dialog box that appears, click Close.
----End
4-28

Issue 02 (2008-05-31)

Operation Guide
4.6.4 Configuring the Overflow Dump Condition for Performance

Data
This operation enables you to configure the overflow dump condition for performance data.
When the performance data in the database exceeds the set threshold for saving the performance
data, the performance measurement system dumps the overflow data.
Context
You can configure the overflow dump condition by modifying DataAdminDm.cfg in
$N2000ROOT\server\conf. The earliest saved data is dumped each time.
NOTE
$N2000ROOT indicates the installation path of the N2000 UMS on the server. The following uses the
path format on Windows as an example. The path format on Solaris is $N2000ROOT/server/conf.
After modifying the parameters in the configuration file, you need to restart the SysMonitor and data
maintenance process to make the configuration file task effect.
Procedure
Step 1 Open the $N2000ROOT\server\conf\DataAdminDm.cfg file.
Step 2 Set the parameters as follows.
l
Overflow_Dump_Theshhold: The threshold value for saving performance data when the data
overflows. By default, it is 80%.
Overflow_Dump_Percent: The data dumped from the data when the data overflows. By
default, it is 20%.
DumpTimerInterval: The time interval for dumping performance data. By default, it is 6

(unit: hour).
Step 3 Save the modified file DataAdminDm.cfg.

----End
4.7 Configuring the Performance Northbound Interface

This operation enables you to configure the parameters of the performance northbound interface,
generate a northbound interface file with the collected performance data periodically, and send
the file to the upper NMS and the third party NMS.
Context
For the selected measuring units, you need to determine whether the performance data collection
tasks are created. If not, the performance data cannot be collected.
You can query, configure, and modify the northbound interface parameters in the ipms.cfg, and
ipms_NB_Default.cfg files in the $N2000ROOT\server\conf directory. You can query or
configure the following parameters:
l
Issue 02 (2008-05-31)
GENERATION_TIMER_TIME: The generation time of the file. You can query this
parameter in the ipms.cfg configuration file. The format is HHMMSS. For example,
220000 indicates that the northbound interface file is generated at 22:00:00 everyday.
4-29

Operation Guide
NBINTERFACE_TIMER_INTERVAL_MINS: The interval to create the northbound

interface file. You can query this parameter in the ipms_NB_Default.cfg configuration
file. The unit is minute. This parameter must be a multiple of 5. The minimum value for
this parameter is 5 and the maximum value is 1440. If this parameter is set to 240, it indicates
that a northbound interface file is generated every 240 minutes.
OLD_FILE_DELETION_DAYS_LIMIT: The maximum saving period of old files. You

can query this parameter in the ipms_NB_Default.cfg configuration file. The unit is day.
The file that exceeds the limit is deleted. For example, 22 indicates that the data of the latest
22 days is saved.
DELETION_TIMER_TIME: The time at which the file is deleted. You can query this
parameter in the ipms_NB_Default.cfg configuration file. The format is HHMMSS. For
example, 230000 indicates that the overdue northbound interface file is deleted at 23:00:00
everyday.
BASE_DIR_PATH: The base path of saving the northbound interface file. You can query
this parameter in the ipms.cfg configuration file. For example, D:\imap\nbinterface. If
you do not set this parameter, the northbound interface file is saved in $N2000ROOT
\nbinterface by default. A directory is named by the date, such as \imap\nbinterface
\20051026.
NBINTERFACE_FILE_TIME_OPTION: The time configuration format used in the

northbound interface files. You can query this parameter in the ipms.cfg configuration file.
If the parameter value is 1, it represents UTC time. Any value other than 1 represents the
NMS time. The default value is the NMS time.
CUSTOMER_ID : This parameter specifies the customer that is currently supported. You
can query this parameter in the ipms.cfg configuration file. For all MU based NBI, the
CUSTOMER_ID is Default.
NBFILE_ADD_MOID: This parameter is used to add a unique ID to each measuring

object in the northbound interface file. This parameter is used to distinguish the measuring
objects with the same name. If this parameter is set to 1 ,MOID field is added to the
northbound interface file, else it is not added. You can query this parameter in the
ipms.cfg configuration file.
FORMAT_FILE: This specifies the XML file from which the format of the northbound
interface file must be read. For example, NB_Default_Format.xml. You can query this
parameter in the ipms_NB_Default.cfg configuration file.
NB_DLL_FILE: The specific DLL file that needs to be loaded for NBI of the specific
customer. You can query this parameter in the ipms.cfg configuration file.
If the performance northbound interface is configured, the system generates the northbound
interface file every 60 minutes by default and saves the data of the latest 5 days. You can modify
the parameters by configuring the related configuration file. After modifying the configuration
file, you must restart the performance measurement daemon.
4-30

Issue 02 (2008-05-31)

Operation Guide
CAUTION
You can set the time related to the performance measurement on the N2000 UMS server, such
as time for generating the file (GENERATION_TIMER_TIME) and the time for deleting the
file (DELETION_TIMER_TIME). The time is not the daylight saving time (DST).
When setting NBINTERFACE_TIMER_INTERVAL_MINS, it is recommended that this
parameter is set greater than or equal to the maximum collection period of the performance data.
Otherwise, the generated northbound interface file may be null.
For the detailed configuration of the performance northbound interface, see the related user guide
of the performance northbound interface.
Procedure
Step 1 Choose Performance > Configure > NorthBound Interface... from the main menu to display
the NorthBound Interface Management dialog box.
Step 2 From the Device Type drop-down list, select the desired device type. In the Version drop-down
list, select the related version to display all the measuring units.
Step 3 Select a measuring unit, right-click, and choose Enable Send Data.
Step 4 In the dialog box that appears, click OK to return to the NorthBound Interface
Management dialog box.
Step 5 Click Refresh.
Step 6 Click Close.
----End
Result
The N2000 UMS generates a northbound interface file of the measured performance data in the
specified path periodically.
Issue 02 (2008-05-31)

4-31

Operation Guide
5 FAQ
FAQ
About This Chapter

This section describes the possible problems that occur when you maintain the N2000 UMS.
5.1 Topology Management
This section describes the solutions to the exceptions that occur in the operations on the topology
view.
5.2 Fault Management
This section describes the solutions to the problems about alarm remote notification and alarm
query.
Issue 02 (2008-05-31)

5-1

Operation Guide
5 FAQ
5.1 Topology Management

This section describes the solutions to the exceptions that occur in the operations on the topology
view.
5.1.1 Why Is the Aerial View Unclear or Exceptional?
5.1.2 Why Do Devices Vanish After the Topology View Is Refreshed?
5.1.3 Why Does the Resolution Change of OS Cause Client Display Exception?
5.1.4 Why Aren't the New Objects Displayed in the Topology View?
5.1.5 The Northbound Interface Dialog Box Cannot Be Displayed
5.1.6 Why Are the Objects in the Topology View Overlapped?
5.1.7 Why Is the Location of an Object Changed?
5.1.8 Why Are Some Menu Items Gray and Unavailable?
5.1.9 Why Are the Devices in the Physical Path Fewer than Those Found by Auto Discovery?
5.1.1 Why Is the Aerial View Unclear or Exceptional?

Description
The aerial view is unclear or exceptional.
Analysis
The aerial view is a minified topology view. Therefore, some nodes in the view may be invisible.
The cause is that the topology view is magnified by a large factor after layout.
Solution
Close the aerial view, and then open it again.
5.1.2 Why Do Devices Vanish After the Topology View Is

Refreshed?
Description
Some device displayed in the topology view cannot be found after the topology view is refreshed.
Analysis
A possible cause is the right changes. The device nodes displayed in the topology view are the
devices that you have rights to access upon login. If some other administrators change your rights
at the time, the topology view is not refreshed automatically.
5-2

Issue 02 (2008-05-31)

Operation Guide
5 FAQ
Solution
1.
To manage the device, you need to apply for the right from the administrator.
2.
After refreshing the topology view manually, you can see the latest authorized device.
5.1.3 Why Does the Resolution Change of OS Cause Client Display

Exception?
Description
When the resolution of the operating system is 800 x 600, start the client, and the client GUI
displays normally. If the resolution, however, is changed to 1024 x 768, when you drag the scroll
bar, only three quarters of the interface is displayed accordingly.
Analysis
The resolution change of the operating system causes the exception of the client GUI display.
Solution
Restart the N2000 UMS client after you change the resolution.
5.1.4 Why Aren't the New Objects Displayed in the Topology View?
Description
The new topology objects, such as devices or submaps, are not displayed in the topology view.
Analysis
There are two possible causes:
l
You add the objects through the service on the server. The data is not synchronized to the
client.
When a device type or a submap type is filtered from the filter tree in the topology view,
the devices or submaps of this type are not displayed. Therefore, if you want the topology
view to display the topology object, select the corresponding type in the filter tree.
1.
The topology view can be automatically refreshed some time after the device is added
(depending on the communication status). If the topology view is not refreshed for a long
time, it indicates that the network status may be unstable and the data packets are lost. Click
Solution
on the toolbar to refresh the topology view.

2.
Issue 02 (2008-05-31)
If the type of the device or the submap is filtered from the filter tree, choose View >
Display > Filter Tree and Legend . In the filter tree on the Filter tab, select the
corresponding device or submap type.

5-3

Operation Guide
5 FAQ
5.1.5 The Northbound Interface Dialog Box Cannot Be Displayed

Description
The Northbound Interface dialog box cannot be displayed.
Analysis
A possible cause is that the service program of the northbound interface is not started.
Solution
Start the northbound interface service through the system monitor client. For the details on the
name of the northbound interface service, see the N2000 UMS Administrator Guide.
5.1.6 Why Are the Objects in the Topology View Overlapped?

Description
When there are multiple topology objects in the topology view, their names may be overlapped
or cannot be seen clearly.
Solution
You can use the following methods to solve the problem:
l
Create different submaps and add the topology objects to them. Choose File > New >
Submap.
Arrange the layout of topology view so that the topology view displays the topology objects
regularly. Choose View > Layout.
Create the filter tree templates so that each filter tree displays only the topology objects of
the specified type. Choose View > Display > Filter Tree and Legend.
5.1.7 Why Is the Location of an Object Changed?

Description
If the new location of a topology object is saved and the view is locked, the location of the
topology object changes after a re-login.
Analysis
The location of the topology object is changed by other users that have the rights to manage the
topology object.
Solution
Grant the management rights only to the proper users that are qualified for managing the topology
object. For example, grant the rights to manage Device A only to the user and the administrator.
Then other users cannot see Device A in the topology view or change the location of Device A.
5-4

Issue 02 (2008-05-31)

Operation Guide
5 FAQ
5.1.8 Why Are Some Menu Items Gray and Unavailable?

Description
After login, you find that part of the menu items are gray and unavailable on the client.
Analysis
l
The current login user has no operation rights to the menu items.
The menu items are not supported in the current window. For example, Edit > Move to
is gray and unavailable if no corresponding topology object is selected in the topology view.
You can apply for the operation right to the administrator.
Learn the functions and operation conditions of the menu items and perform the operations
when the conditions are satisfied.
Solution
5.1.9 Why Are the Devices in the Physical Path Fewer than Those
Found by Auto Discovery?
Description
In auto discovery, the found devices listed in the dialog box are more than those in the physical
path.
Analysis
Before the auto discovery, the devices that use the NE addresses have been created in other
physical path of the topology view. So the devices are not found in the physical path.
Solution
Check if these devices have been created.
Choose Edit > Search to display the Search dialog box. Choose Device in Type, choose NE
Address in Mode. Enter the NE address in decimal mode, such as 10.10.10.10. In this way, you
can query the new device at an NE address.
5.2 Fault Management

This section describes the solutions to the problems about alarm remote notification and alarm
query.
5.2.1 Why Does the Fault Service Fail to Start?
5.2.2 Why Are the Alarm Statistics Displayed on the Alarm Panel Incorrect?
5.2.3 Why Cannot the Alarm Email Be Received?
5.2.4 Why Cannot Alarms Be Viewed on the N2000 UMS Client?
5.2.5 Why Are Cleared Alarms Displayed as Uncleared?
Issue 02 (2008-05-31)

5-5

Operation Guide
5 FAQ
5.2.6 Why Cannot Alarm/Event Postprocessing Be Executed?
5.2.1 Why Does the Fault Service Fail to Start?

Description
Through the System Monitor Client, you find that the fault service fails to start.
Analysis
To receive the trap reported by the device, the fault service monitors Port 162. If the port is used
by other processes, the fault service fails to start.
Solution
Check if Port 162 is used by other processes with the netstat a command. If it is used by other
processes, you need to stop these processes and restart the fault service.
$ netstat -a | grep 162
.....*.162 ..................Idle
5.2.2 Why Are the Alarm Statistics Displayed on the Alarm Panel
Incorrect?
Description
The statistics on alarms displayed on the alarm panel do not comply with the actual situation.
Analysis
l
The current alarms are acknowledged or cleared and changed into history alarms
automatically. If the alarm statistics on the alarm panel are refreshed before some of the
current alarms are changed into history alarms, the data on the alarm panel may be incorrect.
When deleting resources, you need to change the corresponding alarms to the history
alarms, notify the client to delete the alarm. Also, you have to decide whether to notify the
client to refresh the data on the alarm panel according to InformReqPanelFlag in the
emffault.cfg file. Suppose that the client first receives the refresh notification, and refreshes
the alarm panel accordingly before receiving the notification of deleting the device alarm
from the server. Then this leads to the fact that the data of alarms displayed on the alarm
panel are less than the actual numbers.
In deleting a resource, there may be still alarms reported by the resource. This is because
the alarm was generated before the deletion of the resource, but the alarm arrives later than
you delete the resource. Then such alarm is not stored in the history alarm database.
Therefore, if you refresh the alarm panel after deleting a resource, the numbers displayed
on the alarm panel are less than the actual numbers.
Solution
In the Current Alarms window, clear the Display Latest Alarms check box and click the
Refresh button.
5-6

Issue 02 (2008-05-31)

Operation Guide
5 FAQ
5.2.3 Why Cannot the Alarm Email Be Received?

Description
You have set the remote notification properties on GUI, and specified the email address, SMTP
server, sending address, user name, and password. You cannot, however, receive the email sent
from the remote notification service.
Analysis
Check if The Server Requires Account Authentication in Remote Notification is selected.
When the authentication is not required by the mail server, an error occurs if you select the check
box.
Solution
Clear the check box next to The Server Requires Account Authentication in Remote
Notification.
NOTE
In setting the remote notification, you have to ensure the accuracy of the email address, SMTP server,
sending address, user name, and the password. Besides, you also need to make sure whether the mail server
requires account authentication or not.
5.2.4 Why Cannot Alarms Be Viewed on the N2000 UMS Client?

Description
Some alarms reported by the devices are not displayed on the client.
Analysis
The fault management module supports alarm masking. These alarms probably have been
masked.
Solution
Choose Fault > Settings > NE Alarm/Event Mask to delete the conditions that lead to the
problem.
5.2.5 Why Are Cleared Alarms Displayed as Uncleared?

Description
Display the current alarm query window, and some of the newly reported alarms that meet the
query conditions are also displayed in this window. The cleared alarms reported by the device
are still displayed as uncleared in the current window.
Analysis
l
Issue 02 (2008-05-31)
The network transmission process cannot ensure the correct sequence of reporting and
clearing alarms. Therefore, when the interval is too short between reporting the alarm and
5-7

Operation Guide
5 FAQ
clearing the alarm, the notification for clearing the alarm reaches the NMS before the alarm
itself. This leads to the loss of the cleared alarm in the statistics on the alarm panel.
l
The network transmission process cannot ensure the correct sequences of reporting and
clearing alarms. If you query an alarm before clearing it, then the notification for clearing
the alarm may reach the NMS before the queried results because the of the network
transmission reasons. Thus the cleared alarm is still displayed as uncleared.
Solution
In the Current Alarms window, clear the Display Latest Alarms check box and click
Refresh.
5.2.6 Why Cannot Alarm/Event Postprocessing Be Executed?

Description
When you set the alarm/event postprocessing policy, if you enter the special characters such as
% & @ or ^ in the process name, then alarm/event postprocessing may fail.
Analysis
In different OSs, special characters have different meanings in file names. The status of a process
is also related to an OS.
Solution
The postprocessing process name is user-defined. Avoid using the said characters in the name.
5-8

Issue 02 (2008-05-31)

Operation Guide
Acronyms and Abbreviations
3G
3rd Generation
3GPP
3rd Generation Partnership Project
A
ACB
Access Control Block
ACL
Access Control List
ADSL
Asymmetric Digital Subscriber Line
AMG
Access Media Gateway
AN
Access Network
ARP
Address Resolution Protocol
AS
Application Server
ASN.1
abstract syntax notation one
ATCA
Advanced Telecom Computing Architecture
ATM
Asynchronous Transfer Mode
ATS
Advanced Telephony Server
B
BAM
Background Administration Module
BAS
Broadband Access Server
BCC
Block Check Character
BRA
Basic Rate Access
C
Issue 02 (2008-05-31)

A-1

Operation Guide
CAR
Committed Access Rate
CBR
Constant Bit Rate
CC
Conference Call
CDE
Common Desktop Environment
CG
Charging Gateway
CN
Core Network
CNM
Client Network Management
CRC
Cyclic Redundancy Check; Cyclic Redundancy Code
CSC
Call Session Control Server
D
DD
Database Description
DHCP
Dynamic Host Configuration Protocol
DMM
Distributed Message Manager
DMS
Datacom Management System
DNS
Domain Name Server
DSL
Digital Subscriber Line
E
EAU
Ethernet Access Unit
EC
Echo Cancellation
EMF
Element Management Framework
EML
Element Management Layer
EMS
Element Management System
ETS
European Telecommunication Standard
ETSI
European Telecommunications Standards Institute
A-2
FAX
Facsimile
FE
Fast Ethernet
FR
Frame Relay
FTP
File Transfer Protocol

Issue 02 (2008-05-31)

Operation Guide
G
GGSN
Gateway GPRS Support Node
GMSC
Gateway Mobile Switching Centre
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communication
GSN
GPRS Support Nod
GUI
Graphic User Interface
H
HDLC
High-level Data Link Control; High-speed Digital Link Channel
HLR
Home Location Register
HSS
Home Subscriber Server
Issue 02 (2008-05-31)
IAD
Integrated Access Device
IADMS
Integrated Access Device Management System
iCG
IMS Charging Gateway IMS
ICMP
Internet Control Message Protocol
ID
Identification/Identity
IEEE
Institute of Electrical and Electronics Engineers
IFMI
IP Forward Module Card
IGMP
Internet Group Management Protocol
IMA
Inverse Multiplexing on ATM
IMS
IP Multimedia Subsystem
IMT-2000
International Mobile Telecommunication 2000
IN
Intelligent Network
IP
Internet Protocol
IPoA
IP over ATM
ISDN
Integrated Services Digital Network
ISO
International Organization for Standardization
ITC
Independent Transmit Clock

A-3

Operation Guide
ITU
International Telecommunications Union
Iu
Iu Interface
L
LAN
Local Area Network
LE
Local Exchange
LL
Logical Link
LLC
Link Layer Control
LMT
Local Maintenance Terminal
M
M2000
iManager M2000
MA
Multi-service Access
MAC
Media Access Control
MG
Media Gateway
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MIB
Management Information Base
MML
Human-Machine Language
MODEM
MOdulator-DEModulator
MRP
Media Resource Processing Unit
MRS
Media Resource Server
MSC
Mobile-services Switching Centre, Mobile Switching Centre
MTBF
Mean Time Between Failures
MTC
MPEG Transcoder
MTTR
Mean Time To Repair
A-4
NAT
Network Address Translation
NGN
Next Generation Network
NML
Network Management Layer
NMS
Network Management System

Issue 02 (2008-05-31)

Operation Guide
NN
Network Node
NNI
Network Node Interface
O
OAM
Operation, Administration and Maintenance
OMU
Operation & Maintenance Unit
O&M,OM
Operations & Maintenance
OMC
Operations & Maintenance Centre
OSS
Operation Support System
OSTA
Open Standards Telecom Architecture
P
PC
Personal Computer
PDU
Packet Data Unit; Protocol Data Unit
POTS
Plain Old Telephone Service
PPP
Peer-Peer Protocol
PPPoE
PPP Over Ethernet
PRA
Primary Rate Adaptation
PSTN
Public Switched Telephone Network
PVC
Permanent Virtual Connection
PVC
Permanent Virtual Channel
PVP
Permanent Virtual Path
Q
QoS
Quality of Service
Issue 02 (2008-05-31)
RAM
Radio Access Bearer
RAS
Remote Access Server
RM
Resource Manager
RNC
Radio Network Controller
RSTP
Rapid Spanning Tree Protocol

A-5

Operation Guide
RTCP
Real Time Control Protocol
RTP
Real-time Transport Protocol
S
SAP
Service Access Point
SAPI
Service Access Point Identification
SCH
Synchronization Channel
SCP
Service Control Point
SGSN
Serving GPRS Support Node
SMC
Short Message Center
SMS
Short Message Service
SQL
Structured Query Language
SDH
Synchronous Digital Hierarchy
SIP
Session Initiation Protocol
SML
Service Management Layer
SMTP
Simple Mail Transfer Protocol
SNMP
Simple Network Management Protocol
Softswitch
Softswitch
T
TC
Transcoder
TCAP
Transaction Capability Application Part
TCP
Transfer Control Protocol
TDM
Time Division Multiplex
TDT
Technical Development Team
TOS
Type of Service
TMN
Telecommunications Management Network
TMSI
Temporary Mobile Subscriber Identity
TTL
Time to Live
TUP
Telephone User Part (SS7)
A-6

Issue 02 (2008-05-31)

Operation Guide
UE
User Equipment
UDP
User Datagram Protocol
UI
User Interface
UMG
Universal Media Gateway
UMSC
Universal Mobile Switching Centre
UMTS
Universal Mobile Telecommunication Services
UNI
User Network Interface
UTC
Coordinated Universal Time
V
VC
Virtual Channel
VCI
Virtual Channel Identifier
VLAN
Virtual Local Area Network
VLR
Visit Location Register
VMSC
Visit Mobile Switching Centre
VPI
Virtual Path Identifier
VPN
Virtual Private Network
W
WAP
Wireless Application Protocol
X
XML
Issue 02 (2008-05-31)
Extensible Mark-up Language

A-7

Operation Guide
Index
Index
A
adding device
in batch, 2-14
periodically, 2-16
alarm
acknowledging, 3-30
alarm auto processing, 3-37
alarm reporting procedure, 3-5
alarm status, 3-4
auto acknowledgement, 3-37
auto synchronization, 3-38
clearing, 3-33
notification methods, 3-53
panel, 3-65
redefine, 3-39
setting alarm color, 1-14, 3-56
setting alarm local display properties, 1-15
setting alarm sound, 3-55
severity, 3-4
type, 3-5
view alarm detail, 3-29
alarm auto processing
setting NMS alarm/event mask, 3-41
alarm box
setting, 3-54, 3-67
stopping the alarm sound, 3-68
synchronizing, 3-69
alarm panel
displaying, 3-65
setting the alarm panel style, 3-53, 3-66
alarm remote notification
add a remote notification rule, 3-59
setting parameters for, 3-58
alarm template
creating alarm statistics template, 3-10
creating alarm/event browse template, 3-8
alarms/events
mask, 3-40
postprocess, 3-42
auto dump
alarm data, 3-60
event data, 3-61
Issue 02 (2008-05-31)
B
basic attribute of a topological link
modifying, 2-26
browsing
current alarm, 3-18, 3-27
event, 3-21
history alarms, 3-19
C
changing current user password, 1-3
changing login server, 1-11
classification of topological links, 2-20
client
automatic lock, 1-17
manual lock, 1-18
unlock, 1-18
client GUI
set date format, 1-16
set main window title, 1-12
set output information, 1-12
set time format, 1-15
shortcut conventions, 1-8
collect alarm statistics manually, 3-16
configuring
performance northbound interface, 4-29
D
device
adding, 2-12
deleting, 2-34
modifying, 2-34
setting maintenance information, 2-17
viewing information of, 2-40
device type definition, 4-5
display client on top, 3-57
dual home topological link
displaying, 2-23
dumping performance data
default condition for automatic dump, 4-26
immediate dump, 4-28

i-1

Operation Guide
Index
overflow dump condition, 4-29

user-defined condition for automatic dump, 4-27
E
example
alarm handle, 3-35
browsing environment alarm, 3-24
browsing performance threshold alarm, 3-23
browsing the N2000 UMS alarms, 3-23
setting up network topology, 2-35
exit, 1-19
F
flow
monitoring device performance, 4-16
I
IMS Diameter topological link
displaying, 2-23
hiding, 2-24
IMS management topological link
displaying, 2-23
hiding, 2-24
IMS SIP topological link
displaying, 2-23
hiding, 2-24
L
license
query license information, 1-19
link
creating, 2-11
link type
IMS Diameter topological link, 2-21
IMS management topological link, 2-21
IMS SIP topological link, 2-22
virtual topological link, 2-22
log
log out, 1-19
set automatic login, 1-10
M
managing performance measurement tasks, 4-7
manual dump
alarms, 3-62
events, 3-63
master/slave gateway registry topological link
displaying, 2-23
mode of viewing topology, 2-37
monitoring alarm
through the alarm panel, 3-14
through the topology view, 3-13
monitoring device performance, 4-15
i-2
N
N2000 UMS client
menu bar, 1-5
status bar, 1-8
P
performance data
dumping, 4-25
performance measurement
concept, 4-2
GUI, 4-6
time distribution comparison measurement, 4-23
time distribution measurement, 4-21
performance measurement principles
IMS Devices, 4-5
performance measurement task
managing, 4-7
querying basic information about a task, 4-8
querying measuring objects, 4-9
performance threshold record
creating, 4-19
performance threshold template
creating, 4-16
printing
performance data, 4-14
performance measurement result, 4-24
Process
Construct the network topology, 2-7
Q
querying device maintenance information, 3-32
querying performance data
basic time segment, 4-10
user-defined condition, 4-10
querying the maximum and minimum performance
values, 4-12
R
Record alarm maintenance experiences, 3-34
refreshing
single/aggregated topological link, 2-27
S
saving
performance data, 4-13
performance measurement result, 4-24
set auto display of message on alarms, 3-57
setting alarm/event correlation rule
acknowledged and uncleared time analysis, 3-48
correlation analysis, 3-44
frequency analysis, 3-46
intermittent alarm and repeat event analysis, 3-47

Issue 02 (2008-05-31)

Operation Guide
Index
submap
creating, 2-9
deleting, 2-32
modifying, 2-31
synchronizing topological links from the ATCA
devices, 2-27
T
topological link
aggregating, 2-28
displaying, 2-23
expanding, 2-28
hiding, 2-24
querying, 2-25
topology
design, 2-9
icons, 2-5
searching topology object, 2-38
set the topology background, 2-7
topology view
adjust, 2-42
filter display, 2-38
print, 2-44
refresh, 2-35
setting display effect, 1-13
setting feature, 1-13
setting layout, 2-42
V
view
aerial, 2-42
creating custom view, 2-47
link information, 2-41
move, 2-46
returning to the parent topology view, 2-44
submap information, 2-40
virtual topological link
adding, 2-28
deleting, 2-30
displaying, 2-23
hiding, 2-24
Issue 02 (2008-05-31)

i-3

00389527-Operation Guide (V200R012 - 02, IMS)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

00389527-Operation Guide (V200R012 - 02, IMS)

Uploaded by

Copyright:

Available Formats

iManager N2000 UMS Network Management System

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

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

Trademarks and Permissions

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

2.10.1 Modes of Viewing the Topology.......................................................................................................2-37

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

3.5 Handling an Alarm........................................................................................................................................3-24

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

3.8.7 Setting the Client to Be Displayed on Top When an Alarm Is Received............................................3-57

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

4.6 Dumping the Performance Data....................................................................................................................4-25

A Acronyms and Abbreviations................................................................................................A-1

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

About This Document

About This Document

Network monitoring engineers

System maintenance engineers

This section describes the graphical user interface

This section describes how to set up a topological

This section describes how to configure an alarm

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

About This Document

This section describes the principles, functions, and

This section describes the frequently asked questions

A Acronyms and Abbreviations

This section lists the acronyms and abbreviations

Indicates a hazard with a medium or low level of risk which,

Provides additional information to emphasize or

Indicates a tip that may help you solve a problem or save

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in boldface. For

Book titles are in italics.

Terminal display is in Courier New.

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System

About This Document

The keywords of a command line are in boldface.

Command arguments are in italic.

Items (keywords or arguments) in square brackets [ ] are

Alternative items are grouped in braces and separated by

Optional alternative items are grouped in square brackets

Alternative items are grouped in braces and separated by

Buttons, menus, parameters, tabs, window, and dialog titles are in

Huawei Proprietary and Confidential

iManager N2000 UMS Network Management System