NView NNM Operation Guide (V5 - 41)

www.raisecom.
com
NView NNM
Operation Guide
(V5_41)
Raisecom Technology Co., Ltd. provides customers with comprehensive technical support and services. For any
assistance, please contact our local office or company headquarters.
Website: http://www.raisecom.com
Tel: 8610-82883305
Fax: 8610-82883056
Email: export@raisecom.com
Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China
Postal code: 100085
-----------------------------------------------------------------------------------------------------------------------------------------
Notice
Copyright © 2012
Raisecom
All rights reserved.
No part of this publication may be excerpted, reproduced, translated or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in Writing from Raisecom
Technology Co., Ltd.
is the trademark of Raisecom Technology Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Raisecom
NView NNM Operation Guide Preface
Preface
Objectives
This document describes functions, interface descriptions and related configurations
supported by NView NNM, including network topology management, device discovery and
polling, device configuration, alarm event management, customer management, system
security management, system maintenance, data dump, and configuration procedures. In
addition, you can learn terms and abbreviations involved in this document.
This document helps you systematically master interface operations and function
configurations of NView NNM.
Versions
The following table lists the product versions related to this document.
Product name Version

NView NNM V5
Conventions
Symbol conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
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.
Raisecom Technology Co., Ltd. i

Raisecom
Symbol Description
Provides additional information to emphasize or
supplement important points of the main text.
Indicates a tip that may help you solve a problem or save

time.
General conventions
Convention Description
Times New Normal paragraphs are in Times New Roman.
Roman
Arial Paragraphs in Warning, Caution, Notes, and Tip are in
Arial.
Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Lucida Console Terminal display is in Lucida Console.
Boldface The keywords of a command line are in boldface.
GUI conventions
Convention Description
Boldface Buttons, menus, parameters, tabs, windows, 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+C
means the two 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.
Raisecom Technology Co., Ltd. ii

Raisecom
Mouse operation
Action Description
Click Select and release the primary mouse button without

moving the pointer.
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Change history
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Issue 41 (2012-10-26)
Second commercial release
Add the following contents:
 Add section 7.2 Alarm synchronization task management.
 Add section 8.5.8 CNU.
 NE property and inventory management support "area" property.
 Alarm SMS forwarding supports CDMA SMS modem.
 IP address and system file detection of NMS server
 Add section 12.6 Querying system logs.
Modify the following contents:
 Modify configuration view and parameters about the alarm SMS forwarding.
 Modify known mistakes.
Issue 40 (2012-06-01)
Initial commercial release
Raisecom Technology Co., Ltd. iii

Raisecom
NView NNM Operation Guide Contents
Contents
1 System overview ........................................................................................................................... 1

1.1 Overview .......................................................................................................................................................... 1
1.2 Functions and features ...................................................................................................................................... 2
1.2.1 Outstanding architecture ......................................................................................................................... 2
1.2.2 Strong topology management function ................................................................................................... 2
1.2.3 Perfect fault management function ......................................................................................................... 3
1.2.4 Uniform resource management function ................................................................................................. 4
1.2.5 Flexible security control strategy ............................................................................................................ 4
2 Quick start ...................................................................................................................................... 5

2.1 System operations ............................................................................................................................................ 5
2.1.1 Starting NView NNM ............................................................................................................................. 5
2.1.2 Checking NView NNM operating status ................................................................................................. 8
2.1.3 Starting the NMS Client .......................................................................................................................... 8
2.1.4 Changing user ....................................................................................................................................... 11
2.1.5 Locking system ..................................................................................................................................... 12
2.1.6 Auto-logout ........................................................................................................................................... 13
2.1.7 Changing password ............................................................................................................................... 14
2.1.8 Managing license information............................................................................................................... 15
2.1.9 Checking database ................................................................................................................................ 17
2.1.10 Viewing software version and authorization information ................................................................... 17
2.2 Stopping the system ....................................................................................................................................... 19
2.2.1 Exiting NMS Client .............................................................................................................................. 20
2.2.2 Stopping all services ............................................................................................................................. 20
2.2.3 Stopping NMS server ............................................................................................................................ 20
2.3 NMS Client interface description ................................................................................................................... 20
2.3.1 NMS Client interface composition ........................................................................................................ 20
2.3.2 Common interface elements description ............................................................................................... 24
2.3.3 Common list function............................................................................................................................ 25
2.3.4 Common shortcut .................................................................................................................................. 25
2.3.5 Window management ............................................................................................................................ 26
2.4 System menu description ............................................................................................................................... 29
2.4.1 System ................................................................................................................................................... 29
Raisecom Technology Co., Ltd. iv

Raisecom
2.4.2 Topology ............................................................................................................................................... 29

2.4.3 Alarm .................................................................................................................................................... 29
2.4.4 Performance .......................................................................................................................................... 30
2.4.5 Inventory ............................................................................................................................................... 31
2.4.6 EMS config ........................................................................................................................................... 31
2.4.7 Template ................................................................................................................................................ 31
2.4.8 Customer ............................................................................................................................................... 32
2.4.9 Report.................................................................................................................................................... 32
2.4.10 Security ............................................................................................................................................... 32
2.4.11 Log ...................................................................................................................................................... 33
2.4.12 Service ................................................................................................................................................ 33
2.4.13 Data center .......................................................................................................................................... 33
2.4.14 Windows ............................................................................................................................................. 34
2.4.15 Tools .................................................................................................................................................... 34
2.4.16 Help ..................................................................................................................................................... 34
2.5 Common query interface ................................................................................................................................ 35
2.5.1 General interface description ................................................................................................................ 35
2.5.2 Common query panel ............................................................................................................................ 35
2.5.3 Common query and modify component ................................................................................................ 37
2.5.4 Query template ...................................................................................................................................... 40
2.5.5 Executing query operation .................................................................................................................... 40
2.5.6 Customizing query results ..................................................................................................................... 41
3 System monitoring ...................................................................................................................... 42

3.1 Overview ........................................................................................................................................................ 42
3.1.1 NView NNM system monitoring .......................................................................................................... 42
3.1.2 Functions and features .......................................................................................................................... 43
3.1.3 Technical principles .............................................................................................................................. 44
3.1.4 Installation deployment ......................................................................................................................... 45
3.2 Services .......................................................................................................................................................... 46
3.2.1 NView NNM platform service .............................................................................................................. 46
3.2.2 Database service .................................................................................................................................... 46
3.2.3 Data center service ................................................................................................................................ 46
3.2.4 CORBA northbound interface service................................................................................................... 46
3.2.5 Performance monitoring service ........................................................................................................... 47
3.2.6 Synchronization center .......................................................................................................................... 47
3.2.7 Operating status of services .................................................................................................................. 47
3.2.8 Staring modes of services ..................................................................................................................... 48
3.3 NMS Control settings ..................................................................................................................................... 48
3.3.1 Starting/stopping NMS Control ............................................................................................................ 48
3.3.2 Starting/stopping all network management services ............................................................................. 50
3.3.3 Configuring refreshing cycle for services ............................................................................................. 51
Raisecom Technology Co., Ltd. v

Raisecom
3.3.4 Setting service alarm threshold ............................................................................................................. 52

3.3.5 Locking NMS Control .......................................................................................................................... 53
3.3.6 Showing operation log .......................................................................................................................... 55
3.3.7 North interface configuration ................................................................................................................ 56
3.4 Service management ...................................................................................................................................... 57
3.4.1 Showing service status .......................................................................................................................... 57
3.4.2 Starting/stopping services ..................................................................................................................... 59
3.4.3 Detecting service dependency ............................................................................................................... 59
3.4.4 Setting service startup mode ................................................................................................................. 60
3.5 Hard disk management ................................................................................................................................... 61
3.5.1 Showing hard disk information ............................................................................................................. 61
3.5.2 Refreshing hard disk information .......................................................................................................... 62
3.6 Database management .................................................................................................................................... 62
3.6.1 Showing database space usage .............................................................................................................. 62
3.6.2 Database expansion ............................................................................................................................... 63
3.6.3 Showing database connection ............................................................................................................... 64
3.7 Server monitoring........................................................................................................................................... 66
3.7.1 Showing server information .................................................................................................................. 66
3.7.2 Refreshing system resource information ............................................................................................... 67
3.8 Viewing component information .................................................................................................................... 67
3.9 License management ...................................................................................................................................... 68
3.9.1 Showing License ................................................................................................................................... 68
3.9.2 Updating License .................................................................................................................................. 69
4 Network topology management ............................................................................................... 70

4.1 Basic concepts ................................................................................................................................................ 70
4.1.1 Main view of topology .......................................................................................................................... 70
4.1.2 Topology tree ........................................................................................................................................ 71
4.1.3 Topology graph ..................................................................................................................................... 72
4.1.4 Subnets .................................................................................................................................................. 72
4.1.5 Gateway NE subnets ............................................................................................................................. 72
4.1.6 NEs........................................................................................................................................................ 73
4.1.7 Pre-configured NEs ............................................................................................................................... 73
4.1.8 Virtual NEs............................................................................................................................................ 73
4.1.9 Network management NEs ................................................................................................................... 73
4.1.10 Representation of topology ................................................................................................................. 74
4.1.11 Topology symbol ................................................................................................................................. 76
4.1.12 Customized view ................................................................................................................................. 76
4.1.13 Service view ........................................................................................................................................ 76
4.1.14 Topology graphic symbol .................................................................................................................... 76
4.1.15 Topology layout .................................................................................................................................. 76
4.2 Topology management process ...................................................................................................................... 77
Raisecom Technology Co., Ltd. vi

Raisecom
4.3 Creating topology subnets .............................................................................................................................. 77

4.3.1 Dividing subnet structure ...................................................................................................................... 77
4.3.2 Creating subnets .................................................................................................................................... 78
4.4 Creating NEs .................................................................................................................................................. 79
4.4.1 Batch auto-discovery of NEs ................................................................................................................ 79
4.4.2 Creating single NEs .............................................................................................................................. 80
4.4.3 Copying NE .......................................................................................................................................... 84
4.4.4 Adding cluster device ............................................................................................................................ 85
4.5 Synchronizing NE data................................................................................................................................... 86
4.5.1 Synchronizing NE data ......................................................................................................................... 86
4.5.2 Synchronizing NE pre-configuration data............................................................................................. 86
4.6 Creating link ................................................................................................................................................... 87
4.6.1 Creating physical link ........................................................................................................................... 87
4.6.2 Creating logical link .............................................................................................................................. 89
4.7 Creating symbol ............................................................................................................................................. 90
4.8 Configuring common information of topology object ................................................................................... 90
4.8.1 Configuring NE name ........................................................................................................................... 91
4.8.2 Configuring NE SNMP management parameters ................................................................................. 91
4.8.3 Configuring NE offline detection .......................................................................................................... 92
4.8.4 Configuring project information ........................................................................................................... 92
4.8.5 Configuring expansion properties ......................................................................................................... 92
4.8.6 Configuring the contact information of maintenance staff .................................................................... 93
4.8.7 Configuring link information ................................................................................................................ 93
4.8.8 Configuring symbol information ........................................................................................................... 93
4.9 Deleting topology object ................................................................................................................................ 94
4.9.1 Deleting subnet ..................................................................................................................................... 94
4.9.2 Deleting NEs ......................................................................................................................................... 94
4.9.3 Deleting links ........................................................................................................................................ 95
4.10 Common operations of topology management ............................................................................................. 96
4.10.1 Searching subnet and NEs ................................................................................................................... 96
4.10.2 Refreshing the entire network topology .............................................................................................. 98
4.10.3 Adjusting topology layout ................................................................................................................... 98
4.10.4 Moving subnets and NEs .................................................................................................................. 100
4.10.5 Locking/Unlocking topology view ................................................................................................... 101
4.10.6 Locking/Unlocking the coordinates of topology object .................................................................... 102
4.10.7 Subnet expansion in the same layer .................................................................................................. 102
4.10.8 Viewing related resources ................................................................................................................. 103
4.10.9 Configuring display layout ................................................................................................................ 103
4.10.10 Configuring topology setting .......................................................................................................... 106
4.10.11 Configuring link display aggregation .............................................................................................. 107
4.10.12 Device offline rate statistics ............................................................................................................ 108
4.10.13 Common button in topology toll bar ............................................................................................... 109
Raisecom Technology Co., Ltd. vii

Raisecom
4.10.14 Selecting multiple topology objects ................................................................................................ 110

4.10.15 Configuring background picture ..................................................................................................... 110
4.10.16 Common view operations ............................................................................................................... 112
4.10.17 Configuring view zoom .................................................................................................................. 113
4.11 Configuring customized view..................................................................................................................... 115
4.11.1 Adding customized view ................................................................................................................... 115
4.11.2 Adding topology objects in customized view .................................................................................... 116
4.11.3 Viewing customized view ................................................................................................................. 117
4.11.4 Modifying customized view properties ............................................................................................. 117
4.11.5 Viewing customized view properties................................................................................................. 118
4.11.6 Querying customized view ................................................................................................................ 120
4.12 Viewing topology list ................................................................................................................................. 122
4.12.1 Viewing subnet list ............................................................................................................................ 122
4.12.2 Viewing NE list ................................................................................................................................. 123
4.12.3 Viewing link list ................................................................................................................................ 123
5 Device discovery and polling ................................................................................................. 125

5.1 Overview ...................................................................................................................................................... 125
5.2 Functions and features .................................................................................................................................. 126
5.3 Technical principle ....................................................................................................................................... 126
5.4 Basic conceptions ......................................................................................................................................... 127
5.5 Interface description ..................................................................................................................................... 128
5.5.1 Startup interface .................................................................................................................................. 128
5.5.2 Protocol template ................................................................................................................................ 128
5.5.3 Scan filter ............................................................................................................................................ 132
5.5.4 Scan task ............................................................................................................................................. 135
5.5.5 Scan report .......................................................................................................................................... 138
5.5.6 Device poll .......................................................................................................................................... 141
5.5.7 Polling configuration........................................................................................................................... 141
5.5.8 Polling report ...................................................................................................................................... 143
5.5.9 Polling load ......................................................................................................................................... 144
5.6 Scenarios and operation steps....................................................................................................................... 146
5.6.1 Restriction conditions ......................................................................................................................... 146
5.6.2 Starting/Stopping device scan and poll function ................................................................................. 147
5.6.3 Device scan ......................................................................................................................................... 147
5.6.4 Device poll .......................................................................................................................................... 152
6 Device configuration management........................................................................................ 157

6.1 Overview ...................................................................................................................................................... 157
6.2 Commonly-used management tools ............................................................................................................. 158
6.2.1 MIB browser ....................................................................................................................................... 158
6.2.2 Telnet tools .......................................................................................................................................... 159
6.2.3 3Ping Tools collection ......................................................................................................................... 159
Raisecom Technology Co., Ltd. viii

Raisecom
6.3 Configuration management using NE management module ........................................................................ 161

6.3.1 Prerequisites of using NE management module.................................................................................. 161
6.3.2 Launching NE management module in the topology .......................................................................... 161
6.3.3 Viewing card status in the card list...................................................................................................... 162
6.3.4 Viewing card status in topology view ................................................................................................. 163
6.3.5 Managing devices from other vendors using general device management module ............................ 163
6.3.6 Configuring component by EMS ........................................................................................................ 164
6.4 Device batch configuration .......................................................................................................................... 164
6.4.1 Version ................................................................................................................................................ 164
6.4.2 Adding batch configuration task ......................................................................................................... 166
6.4.3 Modifying batch configuration tasks .................................................................................................. 170
6.4.4 Viewing task details ............................................................................................................................ 171
6.4.5 Enabling batch configuration tasks ..................................................................................................... 173
6.4.6 Disabling batch configuration tasks .................................................................................................... 173
6.5 Batch executing commands script ................................................................................................................ 173
6.5.1 Overview ............................................................................................................................................. 173
6.5.2 Batch executing commands script ....................................................................................................... 173
6.6 OLP route module ........................................................................................................................................ 176
6.6.1 Overview of module............................................................................................................................ 176
6.6.2 Function features ................................................................................................................................. 176
6.6.3 Startup of module ................................................................................................................................ 177
6.6.4 Interface style ...................................................................................................................................... 178
6.6.5 Function of module ............................................................................................................................. 180
6.6.6 Create new route ................................................................................................................................. 180
6.6.7 Open route view .................................................................................................................................. 180
6.6.8 Appoint relative card for route ............................................................................................................ 181
6.6.9 Edit route information ......................................................................................................................... 184
6.6.10 Delete route ....................................................................................................................................... 186
6.6.11 View route information ..................................................................................................................... 186
6.6.12 Cards list ........................................................................................................................................... 189
6.7 Device Syslog management ......................................................................................................................... 190
6.7.1 Receiving Syslog ................................................................................................................................ 190
6.7.2 Querying Syslog.................................................................................................................................. 190
7 Alarm event management........................................................................................................ 192

7.1 Overview ...................................................................................................................................................... 192
7.1.1 Alarm status ........................................................................................................................................ 193
7.1.2 Operation status .................................................................................................................................. 193
7.1.3 Alarm synchronization ........................................................................................................................ 193
7.1.4 Current alarm ...................................................................................................................................... 194
7.1.5 Historical alarm ................................................................................................................................... 194
7.1.6 Alarm filtering ..................................................................................................................................... 194
Raisecom Technology Co., Ltd. ix

Raisecom
7.1.7 Alarm compressing ............................................................................................................................. 194

7.1.8 Alarm reversal ..................................................................................................................................... 194
7.1.9 Alarm live period ................................................................................................................................ 194
7.1.10 Alarm levels ...................................................................................................................................... 195
7.1.11 Content of alarm event ...................................................................................................................... 195
7.1.12 Alarm auto-synchronization .............................................................................................................. 196
7.2 Alarm synchronization task management ..................................................................................................... 197
7.2.1 Functions and features ........................................................................................................................ 197
7.2.2 Checking operating status of alarm synchronization center services .................................................. 198
7.2.3 Configuration procedures .................................................................................................................... 198
7.2.4 Configuring global parameters for alarm synchronization .................................................................. 199
7.2.5 Configuring alarm synchronization tasks ............................................................................................ 201
7.2.6 Performing alarm synchronization manually ...................................................................................... 207
7.2.7 Viewing NE alarm synchronization status .......................................................................................... 208
7.3 Current alarm monitoring ............................................................................................................................. 209
7.3.1 Prerequisites to receive alarms correctly ............................................................................................. 209
7.3.2 Grouped alarm monitoring .................................................................................................................. 210
7.3.3 Customized alarm grouped monitoring rules ...................................................................................... 215
7.3.4 Viewing alarm properties .................................................................................................................... 218
7.3.5 Querying current alarms ...................................................................................................................... 219
7.3.6 Configuring alarm order ...................................................................................................................... 220
7.3.7 Setting alert sound for alarms ............................................................................................................. 223
7.3.8 Acknowledging current alarm ............................................................................................................. 224
7.3.9 Confirming alarm cancellation ............................................................................................................ 225
7.3.10 Clearngi a current alarm .................................................................................................................... 225
7.4 Topology alarm monitoring .......................................................................................................................... 228
7.4.1 Displaying an alarm in the topology view .......................................................................................... 228
7.4.2 Locating an alarm in the topology ...................................................................................................... 228
7.4.3 Locating alarm device ......................................................................................................................... 228
7.4.4 Viewing node alarm ............................................................................................................................ 228
7.5 Device alarm monitoring .............................................................................................................................. 229
7.5.1 Displaying a device alarm ................................................................................................................... 229
7.5.2 Device alarm operation ....................................................................................................................... 230
7.6 Alarm list query ............................................................................................................................................ 230
7.6.1 Customizing query conditions............................................................................................................. 231
7.7 Current alarm filter ....................................................................................................................................... 234
7.7.1 Alarm filter rules ................................................................................................................................. 235
7.7.2 Deploying alarm type filter rules ........................................................................................................ 236
7.7.3 Deploying device filter rules ............................................................................................................... 237
7.7.4 Deploying chassis filter rules .............................................................................................................. 238
7.7.5 Deploying card filter rules .................................................................................................................. 239
7.7.6 Deploying port filter rules ................................................................................................................... 240
Raisecom Technology Co., Ltd. x

Raisecom
7.7.7 Deploying alarm level filter rules ....................................................................................................... 241

7.7.8 Deploying alarm time segment filter rules .......................................................................................... 242
7.7.9 Deploying filter rules quickly ............................................................................................................. 244
7.7.10 Searching filter rules ......................................................................................................................... 244
7.8 Alarm reversal .............................................................................................................................................. 246
7.8.1 Alarm reversal mode ........................................................................................................................... 246
7.8.2 Configuring alarm reversal ................................................................................................................. 247
7.8.3 Configuring alarm reversal mode in batch .......................................................................................... 248
7.9 Trap notification ........................................................................................................................................... 249
7.9.1 Setting SMS trap notification service.................................................................................................. 249
7.9.2 Setting E-mail trap notification service ............................................................................................... 250
7.9.3 Setting trap notification rules .............................................................................................................. 250
7.10 Historical alarm management ..................................................................................................................... 252
7.10.1 Querying historical alarms ................................................................................................................ 252
7.10.2 Deleting historical alarms ................................................................................................................. 252
7.11 Trap definition management ....................................................................................................................... 253
7.11.1 Querying Trap definition ................................................................................................................... 253
7.11.2 Redefining alarm level ...................................................................................................................... 253
7.11.3 Deleting trap definition ..................................................................................................................... 254
7.12 Troubleshooting knowledge management .................................................................................................. 254
7.12.1 Troubleshooting knowledge management ......................................................................................... 254
7.12.2 Troubleshooting knowledge input ..................................................................................................... 255
7.12.3 Querying troubleshooting knowledge ............................................................................................... 257
7.13 Alarm Statistics .......................................................................................................................................... 258
7.13.1 Current alarm statistics...................................................................................................................... 259
7.13.2 Historical alarm statistics .................................................................................................................. 259
8 Inventory management ............................................................................................................ 261

8.1 Overview ...................................................................................................................................................... 261
8.1.1 Function features ................................................................................................................................. 262
8.1.2 Collect inventory information by automation ..................................................................................... 262
8.1.3 Collect inventory information by manual inputting ............................................................................ 262
8.1.4 Inventory information statistics ........................................................................................................... 262
8.2 Main interface of inventory information ...................................................................................................... 263
8.3 Inventory information classification ............................................................................................................ 264
8.3.1 Physical inventory ............................................................................................................................... 264
8.3.2 Directory ............................................................................................................................................. 264
8.4 Inventory information collection .................................................................................................................. 264
8.4.1 Collect by automation ......................................................................................................................... 264
8.4.2 Input by manual .................................................................................................................................. 265
8.4.3 Synchronize inventory information ..................................................................................................... 265
8.5 Physical inventory management ................................................................................................................... 266
Raisecom Technology Co., Ltd. xi

Raisecom
8.5.1 Rack .................................................................................................................................................... 266

8.5.2 NEs...................................................................................................................................................... 267
8.5.3 Chassis ................................................................................................................................................ 270
8.5.4 Slots .................................................................................................................................................... 272
8.5.5 Cards ................................................................................................................................................... 273
8.5.6 Remote devices ................................................................................................................................... 275
8.5.7 ONU .................................................................................................................................................... 277
8.5.8 CNU .................................................................................................................................................... 279
8.5.9 Ports .................................................................................................................................................... 281
8.6 Inventory types ............................................................................................................................................. 283
8.7 Address book management........................................................................................................................... 284
8.8 Exporting inventory information .................................................................................................................. 285
8.9 Inventory information statistics .................................................................................................................... 286
8.9.1 Device type statistics ........................................................................................................................... 286
8.9.2 Card type statistics .............................................................................................................................. 286
8.9.3 Slot idle rate statistics ......................................................................................................................... 287
9 Customer management ............................................................................................................ 289

9.1 Overview ...................................................................................................................................................... 289
9.1.1 Brief introduction of functions ............................................................................................................ 289
9.1.2 Related definitions .............................................................................................................................. 289
9.2 Customer lists ............................................................................................................................................... 290
9.2.1 Inputting customer information........................................................................................................... 290
9.2.2 Importting customer information ........................................................................................................ 291
9.2.3 Exporting customer information ......................................................................................................... 293
9.3 Attaching network resources to customers ................................................................................................... 293
9.3.1 Attachinging network resources to customers ..................................................................................... 293
9.3.2 Viewing customer alarm information .................................................................................................. 296
10 System security management ............................................................................................... 298

10.1 Overview .................................................................................................................................................... 298
10.1.1 Users ................................................................................................................................................. 299
10.1.2 User group ......................................................................................................................................... 300
10.1.3 Operation authority ........................................................................................................................... 301
10.1.4 Operator set ....................................................................................................................................... 301
10.1.5 Management domain ......................................................................................................................... 301
10.1.6 Decentralized hierarchy, decentralized authority and decentralized domain .................................... 302
10.1.7 Access control ................................................................................................................................... 302
10.1.8 Security policy .................................................................................................................................. 303
10.1.9 Log policy ......................................................................................................................................... 303
10.1.10 Security management deployment process ..................................................................................... 303
10.2 User management ....................................................................................................................................... 303
10.2.1 Default user ....................................................................................................................................... 303
Raisecom Technology Co., Ltd. xii

Raisecom
10.2.2 Creating users.................................................................................................................................... 304

10.2.3 Modifying users ................................................................................................................................ 311
10.2.4 Deleting users.................................................................................................................................... 312
10.2.5 Resetting password ........................................................................................................................... 312
10.2.6 Unlocking account ............................................................................................................................ 313
10.3 User group management ............................................................................................................................. 313
10.3.1 Default user group ............................................................................................................................. 313
10.3.2 Creating user groups ......................................................................................................................... 315
10.3.3 Modifying user groups ...................................................................................................................... 319
10.3.4 Deleting user groups ......................................................................................................................... 320
10.4 Operator set management ........................................................................................................................... 320
10.4.1 Default operator set ........................................................................................................................... 320
10.4.2 Creating operator set ......................................................................................................................... 321
10.4.3 Modifying operator set ...................................................................................................................... 324
10.4.4 Deleting operator set ......................................................................................................................... 325
10.5 Access control list management ................................................................................................................. 325
10.5.1 Creating access control list ............................................................................................................... 325
10.5.2 Modifying access control list ............................................................................................................ 327
10.5.3 Deleting access control list ............................................................................................................... 328
10.6 Security policy management ...................................................................................................................... 328
10.6.1 Password policy management ........................................................................................................... 328
10.6.2 Account policy management ............................................................................................................. 330
10.7 Monitoring user operation .......................................................................................................................... 332
10.8 Online user management ............................................................................................................................ 333
10.8.1 Monitoring online users .................................................................................................................... 334
10.8.2 Forcing user offline ........................................................................................................................... 334
10.9 User login modes........................................................................................................................................ 335
10.10 Log strategy management ........................................................................................................................ 335
11 System service management ................................................................................................. 337

11.1 Overview .................................................................................................................................................... 337
11.2 System service management....................................................................................................................... 337
11.2.1 Starting/Stopping system service ...................................................................................................... 337
11.2.2 Editing system service properties ...................................................................................................... 338
11.3 Schedule service management .................................................................................................................... 339
11.3.1 Starting/Stopping schedule service ................................................................................................... 339
11.3.2 Editing schedule service .................................................................................................................... 340
11.4 Tracing service operation status ................................................................................................................. 341
11.5 Common services descriptions ................................................................................................................... 342
11.5.1 SNMP trap receiving service ............................................................................................................. 342
11.5.2 Trap storm defending service ............................................................................................................ 344
11.5.3 Alarm mail relay service ................................................................................................................... 344
Raisecom Technology Co., Ltd. xiii

Raisecom
11.5.4 Alarm SMS relay service................................................................................................................... 347

11.5.5 Trap forwarding service .................................................................................................................... 350
11.5.6 Alarm forwarding service .................................................................................................................. 352
11.5.7 Batch configuration service ............................................................................................................... 354
11.5.8 Link auto detect service..................................................................................................................... 354
11.5.9 Syslog receiving service .................................................................................................................... 355
11.5.10 Current alarm auto-clearing service ................................................................................................ 355
11.5.11 Resource synchronization service ................................................................................................... 356
11.5.12 Syslog auto-clear service ................................................................................................................. 357
11.5.13 Database backup service ................................................................................................................. 359
11.5.14 Database auto-repairing service ...................................................................................................... 362
11.5.15 MAC link discovery service ............................................................................................................ 362
12 System maintenance ............................................................................................................... 364

12.1 Overview .................................................................................................................................................... 364
12.2 Backing up database ................................................................................................................................... 364
12.3 Recovering database ................................................................................................................................... 365
12.4 Maintaining database.................................................................................................................................. 367
12.5 System debug information ......................................................................................................................... 367
12.6 Querying system logs ................................................................................................................................. 369
12.6.1 Entering log management view ......................................................................................................... 369
12.6.2 System log types ............................................................................................................................... 370
12.6.3 Descriptions of log information ........................................................................................................ 371
13 Data Dump ............................................................................................................................... 375

13.1 Overview .................................................................................................................................................... 375
13.2 Automatic dump ......................................................................................................................................... 376
13.2.1 Configuration interface ..................................................................................................................... 376
13.2.2 Procedures of automatic dump .......................................................................................................... 377
13.2.3 Scenarios ........................................................................................................................................... 378
13.2.4 Configuring overflow dump .............................................................................................................. 380
13.2.5 Configuring periodical dump ............................................................................................................ 381
13.2.6 Configuring dump file ....................................................................................................................... 383
13.2.7 Configuring FTP upload ................................................................................................................... 384
13.3 Manual dump ............................................................................................................................................. 385
13.3.1 Configuration interface ..................................................................................................................... 386
13.3.2 Procedures of manual dump .............................................................................................................. 386
13.3.3 Scenarios ........................................................................................................................................... 387
13.3.4 Configuring dump time range ........................................................................................................... 388
13.3.5 Dumping file by manual ................................................................................................................... 389
13.3.6 Manual dump FTP upload ................................................................................................................. 389
13.4 Checking dump conditions ......................................................................................................................... 389
13.4.1 Checking dump file ........................................................................................................................... 389
Raisecom Technology Co., Ltd. xiv

Raisecom
13.4.2 Viewing dump log ............................................................................................................................. 391
14 Appendix .................................................................................................................................. 393

14.1 Operation authority comparison table ........................................................................................................ 393
14.1.1 Network management application and system menu authority comparison table............................. 393
14.1.2 Network management application and topology management authority comparison table .............. 401
14.1.3 Device operation authority and network element management function comparison table .............. 402
14.1.4 Operation authority dependence relationship comparison table ....................................................... 403
14.2 Terms .......................................................................................................................................................... 409
14.3 Abbreviations ............................................................................................................................................. 410
Raisecom Technology Co., Ltd. xv

Raisecom
NView NNM Operation Guide 1 System overview
1 System overview
This chapter is a brief description of the structure and function of NView NNM integrated
network node management system, including the following sections:
 Overview
 Functions and features
1.1 Overview
NView NNM (Network Node Management System, NView NNM for short) is a new
generation of integrated network node management system based on SNMP protocol
developed by Raisecom Technology Co. Ltd. NView NNM system aims at access network
and emphasizes on centralized configuration and fault detection of all-series network
manageable devices of Raisecom. The current release of NView NNM system completely
presents the following functions:
 Topology management: NView NNM system displays network topology in graphics. It
organizes and manages all types of network device nodes and the links connecting nodes.
Network deployment can be completed both manually and automatically.
 Configuration management: Configuration management over Raisecom all-series
network manageable devices is achieved with NView series EMS (Element Management
System) running on the uniform network management platform provided by NView
NNM system. NView NNM also provides a batch configuration component and database
management function that helps reduce the workload generated by network maintenance.
Then it realizes device configuration and software management efficiently.
 Alarm management: NView NNM system can collect and manage alarm information
from network devices under management and provide functions like query, filtration,
statistics forwarding, alert sound prompt, and etc.
 Performance management: Information of CPU usage, interface performance, data flow
and bandwidth usage can be monitored by real-time performance monitoring module and
can be presented in the form of lists or graphics on the NView NNM system.
 Resource management: The resource management function of NView NNM system
manages network resources information, including information of devices, chassis, cards,
ports and the relationship between resources and customers in a centralized style.
 Customer management: NView NNM system helps network administrator keep the
information of all network access customer. By attaching device, card or port resources
1
Raisecom Technology Co., Ltd.
Raisecom
to customers, it is convenient for network administrators to find the customers affected

by the fault from the customer information recorded in alarm information.
 Security management: NView NNM system allows several administrators to log in the
system at the same time and controls the access of clients by creating "Access Control
List"; "System Automatic Lockup" function will lock up the current client if there is not
any operation on client over setting time; "Client Automatic Logoff" function, the system
logs current customer by automation if there is not any operation on client over setting
time; "Illegal Login Authentication" function will lock up the customer if log on system
by wrong username and password over system setting times. NView NNM employs
multi-authority multi-domain security control strategy and keeps detailed system/device
operation logs, which facilitate operation authority control.
 Service management: The application service management frame provided by NView
NNM manages pre-defined system services, like Trap Receiving Service, Alarm Storm
Defending Service, Alarm Mail Relay Service, and etc.
 System monitoring: NView NNM system monitoring function can automatically manage
NView NNM function components service, such as network management platform
service, performance monitoring service, northbound interface service and etc. System
Monitoring can monitor the operating status of these services and support to restart the
service and report alarm and record log when the services are abnormal.
1.2 Functions and features

1.2.1 Outstanding architecture
 NView NNM supports all SNMP versions, including SNMP V1, V2c and V3.
 CORBA-based and TMF814 criterion conformed northbound interface is provided to
enable integration to higher-level integrated network management system.
 NView NNM supports multiple clients to access at the same time, access control and
other safe functions, which is in accordance with operation and maintenance working
features.
 The system supports internationalization/localization settings. Chinese version and
English version are provided.
 The system supports NView NNM system monitoring function and makes sure various
NView NNM services are operating normally.
1.2.2 Strong topology management function

 Manual topology layout. You can create all types of topology nodes and links using the
topology components provided by NView NNM to structure a logical topology view
caters for self-management need.
 Automatic topology layout. Device detection function of NNM supports detecting
managed device in assigned network segment or IP segment. You can add manageable
device by this function. Structuring network topology and greatly increase system
deployment efficiently.
 Real-time device offline detection. NView NNM system monitors the offline status of
devices on different levels and with different grades using the device offline detection
service. The offline status of devices is notified by alarms.
 In support of topology tree nodes and topology figure nodes to take real-time linkage
selection.
2
Raisecom
 Quick search and localization of node. You can search and locate a node under
management quickly using the name or IP address of it.
 Real-time alarm status mapping. The system will highlight alarming node in different
colors to demonstrate the highest alarm level the node is suffering. Detailed information
of the alarm can be examined conveniently and quickly.
 Various automatic layout patterns, such as tree layout, star layout, grid layout, and etc.
 Network topology browsing navigation function. The system provides you with network
topology browsing navigation function along with graphic operations on network
topology like zoom, recover, pre-view, and etc.
 Shortcut operation pattern. The system provides shortcuts for operations like subnet
unfold, nodes move, copy, and etc.
1.2.3 Perfect fault management function

 Uniform alarm receiving and resolving. All alarms from Raisecom devices and other
standard alarms can be resolved.
 Leading processing capability of alarm throughput: a maximum of 100 pieces per second.
 Function of monitoring current network fault in groups. Realizing emphasis monitoring
on key-customer and key devices.
 Alarm synchronization function. Based on current alarms of the device, NView NNM
can automatically analyze and deal with alarms, ensuring alarms on the NView NNM
and on the device consistent.
 Alarm synchronization task management function. With this function, NView NNM can
perform alarm synchronization periodically.
 Exact fault locating function. A one-step operation in the alarm list completes a fast
locating to a faulted topology node or a direct locating to a related card or port on the
device panel.
 Customer information relating function. For the alarm from resources attached to
customers, customer information will be directly included in the alarm information.
 Alarm information compression function. NView NNM compresses the number of
pieces of alarm information displayed in an alarm list by counting and listing the updated
status instead of listing alarms of the same type and from a same node.
 Fault self-recovery alarm function. NView NNM system will automatically search for
corresponding alarm information after it receives a fault recovery event, and modify the
status of the corresponding alarm event to "Recovered".
 Alarm live period calculation function. By calculating the time difference between the
start time of the alarm (the time when the alarm is reported for the first time) and the end
time of the alarm (the time when the alarm is automatically restored or cleared), you can
easily get the fault clearance time of the system.
 Alarm filtering function. Alarm filtering strategy can be set up for different alarm types
and/or for alarms from different location (devices, chassis, cards or ports). At the same
time, alarm storm defending service is applicable to effectively prevent alarm storm from
happening.
 Alarm reversal function for ports without opening service. Alarm reversal is used to
avoid generating the related alarm information and alarm interference.
 Strong alarm query function. Query can be conducted using one or several terms among
alarm type, alarm time period, alarm object status, and alarm resource.
 Alarm alert sound notification function. Different levels of alarms will be notified by
different customized alert sounds.
3
Raisecom
 Alarm auto-forwarding function. Administrator can be notified with alarm events

instantly via e-mail or mobile phone short message.
 Fault removal experience management function. You can write down fault description
and the operations took for removing the fault in the system during the fault removal
process and establish a fault removal knowledge base for future reference for the
removal of similar faults.
 Alarm statistics function, you can take statistics of the current alarm or history alarm in
different level and from different NE.
1.2.4 Uniform resource management function

 Uniform Resources Collection Interface. Resource information contains information of
chassis, cards, ports, and etc., from all Raisecom broadband access devices (e.g. media
converter, interface converter, PDH multiplexer) can be collected. For devices from other
venders, NView NNM obtains the interface information via standard MIB (RFC1213).
 Customer Information Management Function. By attaching network resources to
customers, NView NNM can query and collect resource usage statistics conveniently.
 Alarm Relating Function. Customer information will be automatically included in alarm
information when alarm occurs on the resources that have been attached to the customer.
 Resource-based Statistics Analysis Function. Statistic information, like device type
statistic, card type statistic and idle slot statistic, are calculated to describe network
device distribution status.
1.2.5 Flexible security control strategy

 Multi-Level, Multi-Authority and Multi-Domain Security Control Strategy. The system
supports differentiate administrative authorization based on device. Tailored to practical
need of network management, the strategy grants different level of authority over
different network devices to different customers.
 Customized Management Domain. The network management tasks for network
administrators can be proportioned according to device functions. The strategy can be
applied to satisfy the internal management policy of an operation and maintenance
department of several people or several dozens of people.
 IP Address-Based "User Access Control List". You cannot log in the system through
hosts with IP addresses which are not in the "User Access Control List". The system can
also configure "Login time" restrict, users out of "Login time" cannot login in.
 "Illegal Login Authentication" function will lock up the customer if log on system by
wrong username and password over system setting times.
 Support "Multi-user login mode" and "Single-user login mode". In "Single user login
mode", only the super administrator can login the system so as to manage system in
upgrade and maintenance.
 System/Device Operation Log. Detailed system operation log and device operation log
facilitate the monitoring and tracing of the working status of network administrator.
4
Raisecom
NView NNM Operation Guide 2 Quick start
2 Quick start
This chapter mainly introduces the common operation to start and login NView NNM and
facilitate you to learn NView NNM usage quickly, including the following sections:
 System operations
 Stopping the system
 NMS Client interface description
 System menu description
 Common query interface
2.1 System operations
 In Windows Server operation system, please take install, upgrade and start
operations and running as "administrator" operating system super administrator
user.
 To use non-"Administrators" group operating system user to install, upgrade, and
start the NMS related procedures, please right-click the executable procedure or
shortcut, select "Run as Administrator" to start the related procedures in shortcut
menu. Otherwise the install, upgrade and NMS platform server start operations
will be abnormal.
 To remotely install, upgrade, and start the operation, the user account to login
operating system must belong to "Administrators" group and "Remote Desktop
Users" group at the same time. Otherwise, the install, upgrade and start
operations may be failed.
2.1.1 Starting NView NNM
Starting NView NNM

Double-click NMS Server shortcut on desktop to start NMS server, as shown in figure below.
It will pop up "Command prompt" (CMD command line) window to perform some automatic
operations, please do not close command prompt window manually.
5
Raisecom
After NView NNM is started, all NMS servers in "Auto-start" mode will be started at the
same time.
Figure 2-1 Starting NMS server
 By default, NView NNM is registered for operating system service "NMSServer",

the startup mode is Automatic; NView NNM can be started automatically when the
operating system is started. NView NNM used database is registered for operating
system service "Nms_database_engine" service by default, the startup mode is
Automatic; NView NNM can also be started automatically when the operating
system is started. You can use the various NView NNM functions only when
database service is started.
 In NView NNM system monitoring functions, NView NNM platform service is
started automatically by default. If modified for manual startup, you needs to login
system monitoring manual start platform service after starting NView NNM, and
then the NMS client can use NMS function normally. After platform service is
started, the corresponding operating system procedure is named as
"InstanceServer.exe", which can be viewed in operating system task manager.
 All NView NNM services support to be configured to start automatically, that is to
start simultaneously with the start of NView NNM. The configuration method is to
login monitoring, right-click the service record, and then click Set Start Mode >
Auto in the shortcut menu to configure the service to start automatically with
NView NNM.
Detecting significant system files automatically

During the startup process, the NView NNM will automatically detect significant system files.
6
Raisecom
 If significant system files are damaged, the NView NNM will prompt failure of the
startup operation. Please contact our technical support staff to manually repair these
damaged files.
 If the significant system files are not damaged, no prompt will be displayed. The startup
operation will continue. After detecting the significant system files, the NView NNM
will automatically detect whether the IP address of the server is modified.
Detecting the IP address of the server automatically

When installing the NView NNM, you need to choose an IP address for the server. This IP
will be recorded in the system file and keeps fixed. The NView NNM provides services
through this IP address.
If this IP address is modified and the IP address recorded in the Network Interface Card (NIC)
does not exist, the NView NNM will prompt you to re-choose an IP address for the server,
during the startup process.
 If the NView NNM detects a modified IP address, the NView NNM will prompt you to
reassign an IP address for the server, as shown in Figure 2-2. You need to assign an IP
address for the NView NNM and the startup operation will be continuously performed.
The assigned IP address will be recorded in the system file and be taken as the IP address
for the NView NNM.
 If the NView NNM does not detect a modified IP address, no prompt will be displayed.
And the startup operation will continue.
Figure 2-2 Reassigning an IP address for the server
 At present, for Operating Mode option, only Mater NNMServer is supported. Do

not select Slave NNMServer.
 The IP address displayed in the IP address drop-down list is the current IP
address of NIC in the server. Select the IP address and click OK to apply
configuration.
 In general, do not click Skip or close the dialog box. Otherwise, the NView NNM
cannot provide services properly.
7
Raisecom
2.1.2 Checking NView NNM operating status

NView NNM provides system monitoring program for monitoring and management to
various functions component services of NView NNM. Monitoring system can be started in
correct order and dependencies in starting the service and it will restart the service and report
alarm and record log when the service is abnormal.
Double-click to perform NMS Control shortcut on the desktop, use the super administrator
user password to login and view various services running status of NView NNM.
The super-administrator user name is "administrator", default password is "raisecom".
2.1.3 Starting the NMS Client
When NView NNM is started, start platform service and then start client program. If
the platform service is auto-start mode (default for auto-start), then it will start
automatically when NView NNM is started. System monitoring program can check
whether the status of platform service is "Run".
When NMS server is started successfully, double-click NMS Client shortcut on the desktop to
start client; when the client starts to connect NMS server, the system will provide two modes
"Choose server start" and "Not choose server start".
For the first running, the super administrator user name is "administrator", default
password is "raisecom". Strongly recommended that user modifies the account
password immediately after login so as to ensure system security.
For the first time to run the client, it may prompt that "The client is incomplete, immediate
repair?" Click OK to perform repair operation automatically. After successful repair, it will
prompt that "The client resource files have been created, immediately start the client?" Click
Yes to start the client again.
Starting NMS Client with selecting the server

NMS client is running in "Choose server start" mode by default, double-click NMS Client
shortcut and the program will run to "Choose server" interface, as shown below. Choose
server and then click OK to enter client login interface.
If the server IP address is not listed in the table, please click to enter server name and IP
address. Click to select a server record, click to delete the record.
8
Raisecom
Figure 2-3 Choosing the server
Starting NMS Client without selecting the server

In "Not choose server start" mode, double-click NMS Client shortcut and the program will
run to "Client login interface", as shown below. In this mode, client will use the default server
IP address to login directly.
9
Raisecom
Figure 2-4 Client login interface

Enter correct user name and password. Wait for client to show topology main view and the
client is started successfully.
Configuring modes for connection the server

The specific setting method to start client and connect server mode: select System >
Preference in system main menu to pop up system settings dialog box, as shown below.
Click "Server Settings" in the left side of dialog box, the right side will show server
connection configuration interface. Select "Prompt to choose the server when client starts"
and add corresponding server in server list, click Apply to close the dialog box and complete
the settings.
10
Raisecom
Figure 2-5 System settings dialog box
2.1.4 Changing user

User switching function enables a different user to log in instead of the current user without
restart the system. Click System > Change User on the main menu or click on the
toolbar, the system will switch to security mode. A "Change User" dialog box will pop up.
Enter new user name and password; click OK to verify the identification, change user
operation is successful after successful verification. Click Cancel to cancel this operation and
return to client interface.
11
Raisecom
Figure 2-6 Changing the user
2.1.5 Locking system

"Lock System" function prevents irrelated individual from operating the system during
operation intermission to ensure the confidentiality of system data. The system will switch to
"Security Mode" under which the main interface is hided. The "Lock System" dialog box will
pop up and the system can only be unlocked by the input of correct user information.
Click System > Lock System on the main menu, or click the button on the toolbar, the
system will switch to security mode and a profile validation dialog box will pop up, as shown
in the following figure.
Enter correct password, click OK to verify the identification. The system will return to main
interface after unlocking.
12
Raisecom
Figure 2-7 Locking the system
The system can only be unlocked by entering the correct current user password. The
button Cancel is not applicable when the system is locked.
2.1.6 Auto-logout
In the circumstances that the operator may leave the system for a related long time, to ensure
system security, you can start up the "System Auto-logout" function provided by NView
NNM system. The client will logout automatically if there is no operation, including click of
mouse, moving or mouse and typing from the keyboard, during a specified time period. You
can set to enable/disable the function and the waiting time. By default, the auto-logout
function is disabled and you can enable this function according to their needs.
Click Security > User Management in system menu bar, click user name in the left "Security
Manager Object", the right side will show "Base Info" tab page, as shown below. Uncheck the
"Disable automatic exit", and can configure "Automatically quit waiting time", the default
waiting time is 10 minutes.
13
Raisecom
Figure 2-8 Parameters for auto-logout function
2.1.7 Changing password

Administrator can modify the password after login. Click System > Change Password in the
main menu or click in the toolbar to pop up "Change Password" dialog box, as shown
below.
Figure 2-9 Changing the password

Enter the old password, new password, and confirmation of the new password in turn; click
the OK to start the renewal.
The method above can only modify the password for the current system user. Super
administrator or security administrator user can also change the specified user password
14
Raisecom
through "Reset password" function in security management, see section 10.2.5 Resetting
password for the specific operation.
The password length and complexity are based on security policy control.
2.1.8 Managing license information

In system installation, it will prompt to import legal License file, here just simply select the
License file. When the server is started, the system will check the License file automatically.
Under normal circumstances, it does not need to concern about the License information, but if
the License file is illegal or has been damaged, the system will prompt to import new License
file. You just need to select new License file to import, or else the server will not be started
properly. During system operation, you can update License file through License console
dynamic without restarting the system.
NView NNM supports new version License. The new version is V3, which is not compatible
with older version License.
At present, the License used by the NView NNM should relate to concrete kernel
version or NView NNM version. For example, we do not recommend using V5.4
License for V5.4.1 NView NNM. Different License files may be incompatible.
When installing and upgrading the NView NNM, you need to note the relationship
between the License and the software. We recommend confirming the License
before installing and upgrading the NView NNM
Double-click NMS Control shortcut on the desktop, enter administrator user name and
password to open system monitoring client. Click System monitoring client system menu
Help > License Manager to pop up License management NView network node registration
management console, as shown below. The interface list shows the device node already
registered in the system.
15
Raisecom
Figure 2-10 License console

Click the menu item File > Show License Info to show the content of current License file, as
shown below.
 "License for": License authorized username.
 "Maximum Terminals" is the maximum number to use NMS client for network
management simultaneously.
 "License Type" indicates that License is "Trial version" or "Formal version".
 Expiration Date: the lifetime of License;
 Component License information: control the right of using NMS server components;
 Product Total Units: control the maximum number of registering product units at NMS
server;
 Product license information: control using right of different EMS in NMS server;
 Registered Total Units: the registered nodes number on NMS server.
16
Raisecom
Figure 2-11 License information

Click the menu item File > Update License to pop up file selection dialog box. Select new
License file and click Import to import and validate the new License file.
2.1.9 Checking database

Please make sure that the database is operating properly before starting up the system. The
service will start up as Windows starts up by default. For NView NNM database, please check
whether the "Nms_database_engine" service in Windows services is operating properly.
Please start up the service by using the command "net start Nms_database_engine" in
Windows command prompt or starting it in Windows "Control Panel > Management Tools >
Services" if the service fails to start up with Windows.
2.1.10 Viewing software version and authorization information

NView NNM software version and license information include software version, patching
version and EMS version. The NView NNM version is increased with authorization
mechanism. The functions of authorization mechanism: control using of NView NNM
functionality component; control EMS using integrated in system. The information contains
two parts: software components and device authorization part.
Viewing software version

Click Help > Version Info at the system menu bar of the NMS Client or click shortcut key F2
to pop-up dialog box, which displays detailed software version information, as shown below.
Click Export Excel and the system will save the module and version information in excel file.
17
Raisecom
Figure 2-12 Software version
Viewing authorization information

Click Help > Authorized Info at the system menu bar of the NMS Client or click shortcut
key F3 to pop-up dialog box, which displays detailed software authorization information. The
dialog box is shown as below. The ticked box in "Authorization" row means the selected
module is authorized, the unticked box indicates the module is unauthorized. Click Export
Excel button can save the module and authorization information in excel file.
18
Raisecom
Figure 2-13 "Authorization Info" dialog box_platform
Figure 2-14 Authorization information
2.2 Stopping the system
19
Raisecom
2.2.1 Exiting NMS Client

Please exit the client before stopping NView NNM service. Click System > Exit at system
menu or click in the upper right of client main interface to pop up the dialog box below,
click Yes to exit the client.
Figure 2-15 Exiting the NMS Client
2.2.2 Stopping all services

To stop server, please double click the NMS Control shortcut and use super administrator user
name and password to login, click System > Stop All NNM Services to pop up the following
figure and then click Yes to stop all services.
Figure 2-16 Stopping services
2.2.3 Stopping NMS server

You can only stop "NMS Server" service in operation system service to stop NMS server.
In Windows, click Start > Control panel > Management tool > Services to open service
management interface. Right-click NMSServer and then click Stop.
2.3 NMS Client interface description

2.3.1 NMS Client interface composition
NMS client is the graphical interface of network management. Login the client and show the
main interface, as shown below.
20
Raisecom
Figure 2-17 Client interface
Table 2-1 Interface introduction

1: Systen menu bar 4: Navigation tree area 7: Function area
2: System tool bar 5: Width adjustment bar 8: Function tool bar
3: Form page tab 6: System status bar 9: Function menu bar
System menu bar

System menu bar is for NMS client to initiate a variety of network management functions,
including system menu and submenu.
System tool bar

The system tool bar contains client lock, change user, current alarm counter, view help and
other common functions shortcut buttons, put the mouse arrow on button to display the button
name. The button function is shown as follows.
21
Raisecom
Table 2-2 System tool bar shortcut button

Icon Description
Modify current login user password.
Lock client manually and only enter the login password to unlock.
Change client user.
Configure client system setting.
Show the emergency alarm numbers in current alarm list, click to

open alarm grouping monitoring interface and the list will show
current emergency alarm.
Show the major alarm numbers in current alarm list, click to open
alarm grouping monitoring interface and the list will show current
major alarm.
Show the minor alarm numbers in current alarm list, click to open
minor alarm.
Show the prompt alarm numbers in current alarm list, click to open
prompt alarm.
Show the unknown alarm numbers in current alarm list, click to
open alarm grouping monitoring interface and the list will show
current unknown alarm.
Show the total number of alarms in current alarm list.
Refresh alarm counter.
Configure to enable/disable alarm prompt sound play.
Close all form page tabs and only keep the main interface.
Return to default form layout.
Configure to lock/unlock form layout.
Show NView NNM help.
Show version information.
Show authorization information.
22
Raisecom
Form page tab

Form refers to various client interfaces, click a menu item or enter a network element
management interface to open a form. Click to select the form page tab to switch between
forms.
If the form layout is not locked, click and drag the form page tab to adjust the layout of each
form.
Navigation tree area

The navigation tree area shows the topology tree and classification.
Width adjustment bar

Click and drag the width adjustment bar to change the region size in the form. Click the arrow
in the width adjustment bar to expand/collapse the entire region.
System status bar

System status bar displays the following status information.
Table 2-3 System status bar

Status Description
Login Show client login user name.
information
Connection Show the connection status between client and network
status management server.
Show Red when the server connection fails.
Login mode Show client login mode.
 Multiple-user login mode: NView NNM permits multiple clients
to login simultaneously.
 Single-user login mode: NView NNM only permits one
administrator to login.
NMS Show NMS information
information
Function area
The main function display area in form interface. The graphical interface of each function will
be shown in function area.
For example, the main interface of client shows the topology management function area, that
is the topology area. You can initiate a variety of topology management functions in the
topology.
23
Raisecom
Function tool bar

Each function provided shortcut button tool bar.
Function menu bar

Each function provided menu bar.
2.3.2 Common interface elements description

Common interface elements are shown in the table below.
Table 2-4 Common interface elements

Interface element Instance
Button
Shortcut button
Radio button
Check box
Tab
Textbox
Dorp-down list
box
Menu
Dialog box
Prompt box
24
Raisecom
2.3.3 Common list function

The list display interface is usually divided into multiple pages to display, the common list
functions are shown in the table below.
Interface Description
Show total count of list records.
Configure size page.
Show the page count.
Show page index.

Enter page value and click the Enter key to jump to the
corresponding page.
Show the first page.
Show the previous page.
Show the next page.
Show the last page.
Refresh list records.
2.3.4 Common shortcut

The common shortcut is shown in the table below.
Table 2-5 Common shortcut

Shortcut key Description
Alt + A Close all forms and only show main interface.
Alt + C Pop up system setting interface.
Ctrl + A Check all.
Ctrl + F Pop up topology search interface to search subnet, NE and
symbol.
ESC Exit the pop-up interface.
25
Raisecom
Shortcut key Description

F1 Pop up "Help" interface and show NView NNM help.
F2 Pop up "About" interface and show detailed software version
information.
F3 Pop up "authorization information" interface and show detailed
authorization information.
F9 Change user login password.
F10 Open function menu.
F11 Lock client.
F12 Change client user.
2.3.5 Window management
Window style settings

NView NNM provides tile mode window style; the workspace is filled with current active
windows; you can open multiple windows at the same time, but currently only one is active
window, by default, the network topology window is main window.
"Tile mode" supports to limit the number of windows to start. The specific setting method is
in "Window style" dialog box, click to check "Enable window number limit function", and
then set the number of related enabled windows, the system default value is "5".
Window maximization
The window can be maximized, double-click window tab and the window will fill with the
entire work area. This function is especially suitable for browsing relatively more contents
with smaller window. Double-click the window tab again to return to the original size.
Window re-layout
In NView NNM system, by default, the window layout is locked, you need to unlock layout at
first before the window re-layout. The operation method to unlock: click the main menu bar
Windows > Lock Windows at system main menu, or click in system tool bar. The
window layout can be re-layouted after unlocking: in the window title bar, press the left
mouse button and drag, it will appear a gray rectangle in the interface work area, which
changes its position with the mouse. Release the mouse in a proper position and the window
will be in the new position, as shown below.
26
Raisecom
Figure 2-18 Dragging the window

After re-layout, click the main menu bar Windows > Lock Windows at system main menu or
in system tool bar to lock current layout again. To restore the system default layout, you
can click Windows > Restore Windows at the system main menu or in system tool bar.
Window floating and combination

NView NNM also provides advanced window management function, that is to say, any
window can be popped up in the window of independent dialog box. The specific operation is
when the window layout has not been locked, click in window title bar, the sub-window
will pop up; click to restore the pop-up sub-window to main window.
The pop-up windows can be combined in random, for example to pop up windows in the
same type (current alarm/historical alarm window, etc) and show them in the same dialog box
so as to facilitate the windows classification. The specific operation is to click the left mouse
button in window title bar, drag the window to dialog box and then release the mouse, as
shown in the figure below.
27
Raisecom
Figure 2-19 Window floating
Window floating function is only valid when the window layout has not been locked.
Window lists
The "Window" submenu in system main menu has listed all opened sub-windows, as shown
in the figure below.
Figure 2-20 Window list

Click window menu to activate the corresponding window, which is to display current
window in the work area.
28
Raisecom
2.4 System menu description

System menu can initiate various NView NNM functions. The system menu can be controlled
not only by License file but also user permission, so maybe some system menus cannot be
shown or cannot take operations.
2.4.1 System
Menu Function description
Change password Change current user login password.
Lock system Lock client.
Change user Change client user.
Preference Configure server connection, alarm sound, Telnet NE to
automatically enter user information, system debuf
information and system login mode.
 Dump config: configure automatic dump.
Data dump
 Manual dump: configure manual dump.
Settings xFTP monitor: configure common xFTP server.
Exit Exit client.
2.4.2 Topology
Search node Find subnet, NE and symbol in topology.
Device scan and poll Configure NE automatic find and device poll cycle.
Subnet list Show subnet in topology.
Node list Show NE and symbol in topology.
Link list Show link in topology.
CustomizedCustom Configure Customizedcustomized management view.
management view
2.4.3 Alarm
Grouped alarm Show current alarm according to alarm group.
Current alarm Show current alarm list and manage current alarm.
Historical alarm Show historical alarm list and manage historical alarm.
29
Raisecom

Trap definition Show alarm type list in network management system.
Trap notification Configure e-mail address and mobile terminal numbers to
transmit alarm.
Alarm notification supports e-mail notification and short
message notification. After configuring contact
information, see section 7.9 Trap notification to take
related configuration and performe alarm notification
transmitting function.
Alarm filter rule Configure alarm filter.
Troubleshooting Configure troubleshooting experience.
ALARMSYNMGT Configure alarm synchronization tasks.
Syn global alarm Perform alarm synchronization on all NEs that support
this function.
Settings Configure alarm setting function.
 Alarm list order: configure alarm list order.
 Alarm reverse: configure alarm reverse function.
2.4.4 Performance
Perf monitor Configure performance monitoring progress.
management
Template Configure performance template.
management  Metric template group management: configure template group,
which supports to configure performance metric template and
metric threshold template
 Metric template management: configure metric template and
take customized filter to the required metrics

 Threshold template management: configure threshold template,
which supports to create and configure multi-level threshold to

multiple metrics
Collect task Configure performance collection task.
management
Performance Show historical/real-time performance graph and
Graph performance data.
30
Raisecom
2.4.5 Inventory
Physical Show various resource records of physical inventory and
manage inventory information.
Inventory type Show inventory type.
Address book Configure address book for maintenance staff.
2.4.6 EMS config

Switch Configure switch cluster management.
EoC Configure CBAT and CNU.
Batch configuration Configure batch configuration task.
control console  General command: Configure SNMP parameters, Trap
target address and other general functions in batch for
specified NE.
 Switch command: take batch configuration for specified
switch NE.
Batch configuration Show batch configuration operation result.
logs
Perform command Configure NE to perform command line scripts.
line scripts in batch Enter and import command line scripts and take
command line operation to device in Telnet mode,
supporting to select multiple devices to execute the
same command line in turns and return to command
execution result.
OLP route Configure route for optical line protection device.
EPON/EPON Show EPON link protection view.
protection view
EPON/MAC address Trace MAC address.
trace
EPON/MAC address Rebind ONU MAC address.
re-binding
2.4.7 Template
EoC template Configure CNU device template.
31
Raisecom
2.4.8 Customer
Customer list Configure customer information.
Support to associate NE and customer information so as to
show NE customer and show customer information
influenced by the fault in alarm information.
2.4.9 Report
Current alarm Take current alarm statistics in network management
statistic and subnet.
Historical alarm Take historical alarm statistics in network management
statistic and subnet.
Device type statistic Take various types of devices number statistics in
network management and subnet.
Card type statistic Take various types of cards number statistics in network
management and subnet.
Idle slot statistic Take chassis-based device slot idle rate statistics in
network management and subnet.
Offline device Take NE device offline rate statistics in network
statistic management and subnet.
2.4.10 Security
User management Configure network management client login user.
Support to configure user group, management domain,
operation permission, access control and online user
management etc. security functions.
Online user Show user operation record.
operation
Access control list Configure client to access host IP address control list.
Security strategy Configure network management user security policy.
 Password policy: configure password length, password
combination etc. security policy.
 Account policy: configure user account length, user account
lock etc. security policy.
32
Raisecom

Log strategy Configure to filter system operation log to record, by
default, take a record to all operations.
2.4.11 Log
System event Show NView NNM operation record.
System operation Show user operation record through client.
Device operation Show user operation record to NE device through client.
Login log Show user login client record.
Security manager Show the security management record to add and
log modify network management user.
Syslog Show NE device reported System record.
2.4.12 Service
System service Configure NView NNM alarm receiving and alarm
forwarding services.
Scheduletask Configure NView NNM database auto-backup, auto-
recovery and other timed tasks.
2.4.13 Data center

Software Configure data center NE device/card software management
repository function.
Device Configure to perform upgrade and backup etc. data center
operation function to NE device, show NE device/ card data center
operation record, system software version information.
Task Show the current task working status and complete task in
management data center.
Operation log Show data center log and task operation log.
Backup policy Configure NE device backup policy in data center.
33
Raisecom

Backup Configure NE device/card software backup management
repository function in data center.
Backup log Show data center log and backup task log.
2.4.14 Windows
Boot manager Show client startup information.
Restore windows Configure to restore default client forms style.
Lock windows Lock/unlick client forms layout.
Windows style Configure client form style and the opened forms number
limit.
Close all Close all forms and only keep the main topology view.
Opened forms Show the opened forms name.
name list Each form shows one menu item, click to switch to the
selected form interface.
2.4.15 Tools
ICMP Ping Execute ICMP Ping.
Check the connectivity from NMS server to destination
IP address.
SNMP Ping Execute SNMP Ping.
Check the connectivity from NMS server to destination
IP address SNMP packets.
Web Browser Open built-in Web browser.
2.4.16 Help
Help Show NView NNM help.
Version info Show component version information.
Authorized info Show component authorization information.
34
Raisecom
2.5 Common query interface

For network management system, the information browse and query operations take a big
proportion in common operations, so it is very important to provide a high-efficiency and
convenient information browse, view, query and modify interface.
NView NNM uses the common query and modify interfaces, which have consistent style. In
view, edit property interface, it also use the view and modify interface with same style, here
take inventory list query interface as an example.
2.5.1 General interface description
Parameter description
Generally, the interfaces in client interface have the following features:
 "*": required parameter
 If entering undesirable parameter in the parameter item, it will fail to issue the
configuration and will pop up confirm dialog box and prompt the user parameter is
incorrect.
 In parameter length limit, English and digital character take up 1 character, Chinese
character takes up 2 characters.
 Hover mouse and pop up tooltip to display parameter information.
 Click and to shrink and expand parameter interface
Common button description

 Click Clear to restore interface parameters to the initial value to open interface.
 Click Cancel to exit the current interface.
 Click Save to perform configuration operations.
 Click Reset to restore to the last saved configuration.
2.5.2 Common query panel
The inventory function panel area supports to show query, add, modify, property and
associated customer configuration panels. All these panels can be shown in function
panel area.
Click to open query panel in function panel area, as shown below.
35
Raisecom
Figure 2-21 Query panel
Subpanels
Query panel provides three subpanels: Conditions, Columns and Sort.
 Conditions: in support of choosing query relationship, such as relation of equal to or not
equal to, no query value, "like" relation similar to SQL sentence, "AND" and "OR"
relation among querying attributes. You cannot set query attribute value until select
query relation. According to detailed query attribute, the condition supports fills or select
query attribute value. The queried attribute value is matched accurately, namely, the
queried value is identical to input value (It is not case sensitive.)
 Columns: it is the detailed query attribute in query condition, in support of ticking off
multiple lines, like name, IP address, etc.
 Sort: it is the order of querying result, in support of arranging as "Ascending" or
"Descending" according to attribute. Several ordering condition arranged in accordance
with query conditions: following "Type" order and then following "IP Address" order to
arrange inventory information list. Click the buttons of and to adjust the order.
Value type description box

To set query condition without meeting property value requirement will lead to query failure,
so the query condition value supports automatic verification so as to ensure users not to enter
incorrect query value.
You can click in panel to open the value type description box, when click "value" text
box, the value type description box will automatically show the property value type and
maximum length etc, description information for user reference.
36
Raisecom
For example, click "Located subnet" "Value", the value type description box will show "Type:
character string, the maximum length is 100".
2.5.3 Common query and modify component

To query or edit property, besides enter query value by manual directly, it is also in support of
other four query and modify components.
Tree interface
Tree interface is mainly used to choose device type and subordinated subnet, etc. For example:
click to choose query condition "Type" and "Value" input box, click to pop up tree
interface to choose. You can tick off multiple device types and then click OK, as shown below.
Figure 2-22 Tree interface to choose device type
Table interface
Table interface is mainly used to choose maintenance staff in address book or choose list
record. For example: click to choose query condition "Maintenance staff" and "Value" input
box, click to pop up table interface to choose. You can tick off multiple records and
then click OK, as shown below.
37
Raisecom
Figure 2-23 Table interface to choose maintenance staff
Drop-down list box

Drop-down list box is mainly used to choose fixed options. For example: click to choose
query condition "Online status" and "Value" input box to pop up drop-down list box and then
click to choose a record, as shown below.
38
Raisecom
Figure 2-24 Drop-down list box to choose online status
Date box
Date box is mainly used to set time information. For example: click to choose query condition
"Last Sync time" and "Value" input box to pop up data box, set date and time and then click
OK, as shown below.
39
Raisecom
Figure 2-25 Data box to choose last sync time
2.5.4 Query template

Save the query condition in query template, then you can query the attention information
conveniently. The template supports public and private types:
 Public template is in support of selection and using by all NView NNM users.
 Private template is just for current login user selection and using.
Inventory management supports to set default template, which is open with default query
conditions.
System also save the latest query in a template named "The latest query". Every time you
execute query and exit from main interface of inventory management, system will save
template of "The latest query" by automation.
Currently, only inventory management supports query template function.
2.5.5 Executing query operation

Click Query to execute query operation after setting query conditions. The result will be
shown in arranged order.
Click Reset to restore query condition to initial status. If you uses query template for query,
please click Reset to restore default status of query template.
40
Raisecom
Click Clear to clear all query conditions and properties. Click on the right-top to
shutdown function panel.
2.5.6 Customizing query results

You can set table column displayed in query result. Click on the left-top to pop up
customize column interface, as shown below. Select items by tick off the box and then click
Apply.
Figure 2-26 Customizing query results
41
Raisecom
NView NNM Operation Guide 3 System monitoring
3 System monitoring
This chapter induces the function and operation method of NView NNM system monitoring
function, including the following sections:
 Overview
 Services
 NMS Control settings
 Service management
 Hard disk management
 Database management
 Server monitoring
 Viewing component information
 License management
3.1 Overview
3.1.1 NView NNM system monitoring
NView NNM system monitoring is graphical NView NNM network management system
management and monitoring tool. The system monitoring to NView NNM service
management can ensure the stability of network management system operating; concise
interaction interface improves the ease of network management system to run monitoring
normally; user authentication mechanism meets the security of the operation and maintenance
work.
The main service management functions of system monitoring to NView NNM network
management system:
 Start and stop all network management services
 Start and stop single network management service
 Set service startup mode
 Set northbound interface service IP address and port information
 Manage products License information
42
Raisecom
The main monitoring functions of system monitoring to NView NNM network management
system:
 Monitor service operating status
 Show network management database information
 Show system resource information
 Show network management component version information
System monitoring supports to take a record of user login information, a variety of
management operations and service exception information to network management system
log and supports to send alarm to NView NNM network management system according to
user setting system and database resource alarm threshold.
NView NNM kernel version V5.4 and above supports system monitoring function,
kernel version below V5.4 needs to upgrade by upgrade package so as to use
system monitoring function.
The service management function can take real-time monitoring to the status of NView NNM
Services (Server service, performance service, database service, northbound interface, etc.),
CPU utilization, memory utilization, hard disk utilization information, and provide a unified
start and close entrance to NView NNM services so as to facilitate the centralized
management of services. Moreover, the service management function can also monitor and
manage database space and database connection, physical disk utilization, network
management component version and product License information, etc.
3.1.2 Functions and features

System monitoring has system management function, including service information, database
information, system resource information, component information, operating log functions
and features, as shown below.
43
Raisecom
System
System Hard disk Service Database License Component
resource
function information information information information information
information
Hard disk Database Component

Start/stop License Server
User login space space version
service information information
information information information
Expand
Start all NMS Monitor service Update
database
services operating status License
space
Database
Stop all NMS connection
services information
Monitoring
setting
Northbound
interface
Figure 3-1 System monitoring functions and features

System monitoring has the following features:
 System monitoring server provides message bus service, each network management
service connects message bus through system monitoring server, that is to say, the
communication between system monitoring system and network management service is
achieved through message bus component.
 System monitoring server takes centralized authentication to License and network
management service does not take separate verification any more.
 System monitoring client provides unified startup entrance to each network management
service, which does not show tray and startup window. Startup progress is monitored
unifiedly by system monitoring server.
 NView NNM (including system monitoring service) is system service. Default for
manual startup, after configuring to automatic startup, NView NNM will start
automatically with the startup of server host.
3.1.3 Technical principles

As a separate service, system monitoring system is mainly composed with server and client.
When NView NNM is installed, "network management server" shortcut is NView NNM
(including system monitoring and other services) server; "system monitoring client" shortcut
is system monitoring client.
System monitoring does not support to manage database service start/stop, but
support to monitor the operating status of database service. NView NNM database
service is separately registered as system service in the operating system, so it is the
operating system that manages database service start/stop status according to user
configuration.
44
Raisecom
System monitoring server provides startup function for all NMS services and supports to
perform operation according to user setting in service failure (For example, auto-start service)
and at the same time ensures the dependency and execution order between services.
 If stopping the system service in system monitoring server or NView NNM

database service, you cannot login the system monitoring program.
 By default, NView NNM platform service is started automatically with the startup of
system monitoring service. If need to configure the platform service to manual
startup mode, please select "platform service" line in system monitoring server
"service monitoring" tab and select Set startup mode > Manual in the context
menu to modify the startup mode.
 Currently, when network management server is started, the operating system user
will perform "Logout" operation, NView NNM platform, performance monitoring,
data center and other services will stop and automatically restart, which will lead
to a brief interruption of NView NNM network management system. Please take
operation with caution based on the actual situation.
3.1.4 Installation deployment

NView NNM system monitoring function is installed with NView NNM, V5.4 kernel version
and below can be upgraded to complete system monitoring installation deployment.
Currently, NView NNM is upgraded and installed through network management

system installation program with the upgrade package. After installation is complete,
it will show the following shortcut on the desktop.
Network management server: used to start NView NNM.
System monitoring client: used to start system monitoring client to monitor and
configure startup mode to various services of NView NNM.
Upgrade tool: used to start NView NNM upgrade management tool for backup and
upgrade etc. operations.
Client: used to start NView NNM network management client.
45
Raisecom
3.2 Services
3.2.1 NView NNM platform service
NView NNM platform service is the core service of NView NNM, when the platform service
is started, NMS client can use platform service provided topology, security, alarm, inventory
and NE configuration management and maintenance functions.
3.2.2 Database service

The database service belongs to the system monitoring server located host operating system
service, which is started with the operating system, and you cannot set its startup mode.
3.2.3 Data center service

NView NNM data center service can provide you with a graphical interface of device backup
or upgrade and support the management of transmission file to facilitate the centralized
management and secure storage of files. In addition, the data center supports to check device
files so as to prevent the damage from unmatched device type or wrong version upgrade file.
Data center mainly supports the following functions:
 Backup function: take real-time backup or periodic backup operations to network
element software and configuration data and NView NNM will take a record of the
operation log. The device backup cycle can be set to "monthly", "weekly" and "daily".
The backup function can take a maximum of 10 devices for a group for parallel
operation.
 Upgrade function: upgrade refers to use the files in software library to upgrade NE
software and configuration file of specified NE and card, and NView NNM will take a
record of operation log. Upgrade function support the comparison of two configuration
files and the verification function of file header. The upgrade function can also take a
maximum of 10 devices for a group for parallel operation.
Data center service contains two services. Both services need to be started in using various
functions of data center.
 Data center service: provide to distribute device data and device software scheduling
tasks.
 Data center EMS service: provide to manage and maintain device data and device
software.
3.2.4 CORBA northbound interface service

NView NNM NCIA (North CORBA Interface Agent) north interface supports the butt joint
with OSS (Operation Support System). The operation and maintenance management functions
such as service opening, alarm auto-report, alary sync, service troubleshooting and routine
testing between OSS and NE device have been achieved through NCIA north interface.
NCIA north interface is used between OSS and NView NNM; OSS communicates with
NView NNM through NCIA north interface, as shown below.
46
Raisecom
Figure 3-2 North interface communication

CORBA north interface service consists of three services, which need to start in using
CORBA north interface.
 CORBA north interface service: based on CORBA standard to provide the third party
with alarm, topology, inventory, security, performance and configuration services.
 CORBA north interface naming service: based on CORBA standard to provide the third
party with naming service.
 CORBA north interface notification service: based on CORBA standard to provide the
third party with notification service.
3.2.5 Performance monitoring service

NView NNM performance monitoring service can help managers understand the current and
past network load, flow and other operating conditions, provide basis for network failure
warning, failure removing and network optimization. Performance monitoring service
provides unified network device performance data collection, calculation, summary
statements, report and trend chart display etc. functions.
3.2.6 Synchronization center

The synchronization center is the basis for the NView NNM to perform periodical
synchronization of resources and alarms. The NView NNM cannot synchronize alarm until
the synchronization center is enabled. By periodically synchronizing alarms, the NView NNM
can ensure alarms on a device and on the NView NNM are consistent. If not consistent, the
NView NNM will update alarm records, depending on alarms on the device.
3.2.7 Operating status of services

Service running status refers to an important attribute for you to monitor network
management system related services. The service status can be transformed into each other,
47
Raisecom
for example the start status service will change to stop status after performing stop operation.
System monitoring services contains the following status:
 In service: the service is running.
 Stopped: the service has stopped running.
 Be starting: the service is starting to run.
 Start exception: the service startup is abnormal.
3.2.8 Staring modes of services

System monitoring supporting network management system service is divided into four
startup modes:
 Auto start: the service will be started automatically when system monitoring program is
started. The service will keep start status, even if the service is stopped abnormally, the
system monitoring program is still able to restart network management service and take a
record of logs. The service will stop only when you perform stop operation manually.
 Manual start: the manual start service does not start automatically with the startup of
system monitoring program, which requires you to start the service manually in system
monitoring program.
 No starting: system monitoring program and you cannot start such services directly; you
must change the service mode to "Auto start" or "Manual start" to perform "Start
service" operation.
 External start: such services are started by external program; the system monitoring does
not support to start/stop "External start" service, but support to monitor the operating
status of this type of services. The database services belong to external start mode.
To start/stop system services, you need to start/stop the pre-dependent service of

this service. See section 3.4.3 Detecting service dependency for detailed description
of the dependent service of service.
3.3 NMS Control settings

3.3.1 Starting/stopping NMS Control
When NView NNM network management server is started, you can manage and monitor a
variety of network management services through system monitoring program.
In the situation of not starting NMS Server, to start NMS client, the system will
automatically pop up Error message box that prompts server connection failure.
Click OK to pop up confirm dialog box that prompts whether to re-select the
connected server.
Starting NMS server

Double-click to perform the "Network management server" shortcut on the desktop to start
NView NNM network management server. The shortcut corresponding program is installed in
48
Raisecom
NView NNM program folder with path

"C:\NMS\PLATFORM\NNM5\selfmserver\NMSServer".
To configure "NMS Server" service as "Auto start" in operation system, NView NNM
will started automatically when the server host is turned on.
In NView NNM provided system monitoring function, NView NNM platform service is
default to start automatically. If change to manual start, you need to login system monitoring
to start platform service manually when NView NNM is started and then the NMS client can
use network management function normally.
Starting NMS Control

Double-click to perform the "System monitoring client" shortcut on the desktop to start
system monitoring client and enter system monitoring client login interface, as shown below.
Enter user name and password to login system monitoring and manage various NView NNM
services.
Figure 3-3 Starting the NMS Control

 User Name: user name of NMS Server, the user must belong to "Administrators" user
group
 Password: NView NNM network management server user corresponding password
 Server: system monitoring client connecting server
─ Select through drop-down menu server name;
─ Click in right side to pop up Select Server dialog box and select according to
server name and IP address.
49
Raisecom
Exiting NMS Control

In system monitoring client system menu, select File > Exit to pop up a dialog box; click Yes
to exit system monitoring program.
To exit system monitoring program does not affect the normal operating of NMS
server program and various related services.
Stopping NMS server

When the network management server is started, you can only stop "NMSServer" service
from operating system service to stop the network management server.
Open service management interface in Windows by clicking Control Panel >
Administrative Tools > Services. Right-click to select "NMSServer" service and then click
Stop.
3.3.2 Starting/stopping all network management services

You can start/stop all network management system services through system monitoring and
ensure the sequence of services in the process of start/stop operation.
Starting all network management services

To start all network management services refers to the network management services started
by system monitoring program in the network management server with start status "Stop" and
start mode "Auto start" or "Manual start". Generally, it is used to restart all network
management service with start mode "Auto start" or "Manual start" after performing "Stop all
network management services" operation.
System monitoring server starts the services in accordance with the service priority in
descending order, you can see the service start status in service monitoring interface. When
the service is starting, the service status will be "Be starting".
Select System > Start All NMS Services in system monitoring system menu to start all
network management services.
Stopping all network management services

To stop all network management services refers to stop all network management services with
service status "In service" through system monitoring program in the network management
server computer. Generally, it is only used to stop all network management services rather
than exit the system monitoring program.
System monitoring server stops the services in accordance with the service priority in
ascending order, you can see the service stop status in service monitoring interface. When the
service is stopping, the service status will be "Be stopping".
Select System > Stop All NMS Services in system monitoring system menu to stop all
network management services.
50
Raisecom
3.3.3 Configuring refreshing cycle for services

System monitoring supports to refresh the monitoring information periodically; you can set
polling cycle to monitor reasonably to update monitoring information and reduce system load.
To refresh cycle supports to set the refresh interval of system monitoring resource, service,
database and etc.
System monitoring function can refresh the following monitoring information:
 Database space refresh interval, the default value is 3600 seconds and the value range is
600–99999.
 Data connection progress refresh interval, the default value is 600 seconds and the value
range is 60–99999.
 System resource refresh interval, the default value is 60 seconds and the value range is
10–99999.
 Hard disk refresh interval, the default value is 3600 seconds and the value range is 600–
99999.
 Progress refresh interval, the default value is 60 seconds and the value range is 10–99999.
Select System > Set in system monitoring system menu to pop up a dialog box, click
"Refresh" tab to show the following tab box. Select hard drive, service, database or system
resources located line, click "Refresh interval" value to modify directly. After configuration,
click OK to issue the configuration.
Figure 3-4 Configuring refreshing cycle
The minimum interval to refresh monitoring resources is different, as shown below:

 The minimum interval to refresh database space: 600 seconds
 The minimum interval to refresh data connection service: 60 seconds
 The minimum interval to refresh system resources: 10 seconds
51
Raisecom
 The minimum interval to refresh hard disk drive: 600 seconds

 The minimum interval to refresh service: 10 seconds
3.3.4 Setting service alarm threshold

Set the alarm threshold generated by monitoring information through system monitoring
function so as to know the real-time usage of current system resources.
The alarm threshold is divided into 6 levels: emergency alarm threshold, main alarm threshold,
minor alarm threshold, prompt alarm threshold, unknown alarm, and normal. System
monitoring will send the appropriate level of alarm information according to monitoring
setting once exceeding alarm threshold.
The system monitoring function can set the alarm threshold monitoring information:
 CPU alarm threshold: set CPU utilization alarm threshold, when CPU utilization exceeds
the threshold, the system will send corresponding alarm according to the threshold. The
default value is 80%; the range is 0–100.
 RAM alarm threshold: set RAM utilization alarm threshold, when RAM utilization
exceeds the threshold, the system will send corresponding alarm according to the
threshold. The default value is 95%; the range is 0–100.
 HDD alarm threshold: set HDD utilization alarm threshold, when HDD utilization
exceeds the threshold, the system will send corresponding alarm according to the
threshold. The default value is 90%; the range is 0–100.
 Database space alarm threshold: set database space utilization alarm threshold, when the
proportion of database usage space and distribution space exceeds the threshold, the
system will send corresponding alarm according to the threshold. The default value is
80%; the range is 0–100.
In system monitoring system menu, select System > Set to pop up a dialog box, click
"threshold" tab and pop up the tab box shown in Figure 3-5. Select CPU, RAM, HDD and
database line, click the "threshold" or "alarm level" value and modify directly. After
configuration, click OK to issue the configuration.
52
Raisecom
Figure 3-5 Monitor alarm threshold
3.3.5 Locking NMS Control

Terminal lock supports to set system monitoring client to experience intervals without any
operations, i.e. lock the terminal.
The function to lock system monitoring client is mainly used to retain the current client
interface and make the client in lock status; only to re-enter user name and password can
unlock. There are two modes to lock system monitoring client: manual lock and automatic
lock.
Locking NMS Control manually

Manually lock function supports to set system monitoring client to lock status and go to login
screen. Only to re-enter user name and password can unlock and restore to the client
management interface.
In system monitoring system menu, select File > Lock Terminal to pop up system
monitoring login interface, as shown below.
53
Raisecom
Figure 3-6 login interface of the NMS Control

This interface is different from system monitoring client login interface: cannot select the
server to connect; only can click OK after entering user name and password; the Cancel
cannot be used.
Locking NMS Control automatically

Automatic lock function refers to when the user does not carry out any operation on client
interface for longer than the configured automatic lock time threshold, the system monitoring
client interface will be locked automatically and go to login interface.
In system monitoring system menu, select System > Set to pop up a dialog box. Select "Auto
Lock" and enter time threshold in the textbox and then click OK to issue the configuration.
54
Raisecom
Figure 3-7 Setting auto lock time threshold
To unlock system monitoring client, you cannot change the user name and lock user
A, but enter the password of user A.
3.3.6 Showing operation log

"Operation log" interface in the system monitoring provides client the interface to view and
manage operation record so as to find problem and locate fault later, as shown below, you can
select the log display number in this interface.
55
Raisecom
Figure 3-8 Operation log
Table 3-1 Operation log parameter

Parameter Description
User name User name to execute the operation
Operation device Server IP address
Operation name Operation execution name
Operation time Operation execution time
Operation terminal Operation located terminal
Operation result Operation execution result
In Figure 3-8, you can set the interface displayed log information number directly for you to
view. In addition, when the log changes, you can refresh the interface and update the display
information of system monitoring client.
3.3.7 North interface configuration

North interface function module can configure north interface naming service and notify the
service IP address and port.
In system monitoring client system main menu, select NBI > NCIA to pop up the interface
shown in the following figure, the parameters is shown in the following table.
56
Raisecom
Figure 3-9 Parameters for north interface
Table 3-2 North interface parameters

Name service IP Naming server IP address
Name service port Naming service port No.
NTP service IP Notification server IP address
NTF service port Notification service port No.
To configure north interface notification service and naming service IP and port No.,
north interface naming service, notification service and north interface service need
to be in stop status.
3.4 Service management

3.4.1 Showing service status
"Service information" interface in system monitoring supports to view server service status
information conveniently and intensively. You can start, stop and set service startup mode in
this interface according to their needs, as shown below.
57
Raisecom
Figure 3-10 Service information
Table 3-3 Service information parameters

Service name Service name
Process status Current service status
Startup mode Service startup mode:
 Manual
 Automatic
 Prohibit
CPU used ratio (%) Current service CPU utilization

Used physical Current service RAM utilization, unit: kB
memory (%)
Start time Service startup time
Description Current service description information
Select one or more services in the services list, right-click to select the shortcut menu and
perform the following operations:
 Properties: show service properties.
 Refresh: update various service information, including refresh on conditions and refresh
all the service information.
 Start the service: start the selected unstarted services.
58
Raisecom
 Stop the service: stop the selected started services.

 Set startup mode: set the startup mode of selected service to the corresponding mode,
including automatic, manual and prohibit.
 Force to close: force to close the selected services with service status "Be starting", "Be
stopping", "Start exception" and "Stop exception".
 Task log: show the task log information of the selected services.
3.4.2 Starting/stopping services

NView NNM system monitoring server will take real-time communication with the service
and show the service start/stop status and operation in system monitoring client.
Starting services
Right-click the service and then click Start Process in shortcut menu. The system will start
this service automatically, and the "Service status" will change to "In service" from "Stopped".
If the start of this service needs to depend on other services, you need to start the dependent
services according to the pop-up prompts and then start this service.
Stopping services
Right-click a service and then click Stop Process in shortcut menu. The system will pop up
confirm dialog box, click OK to stop this service, and the "Service status" will change to
"Stopped" from "In service". If other services are depending on the start of this service, the
system will pop up a dialog box to prompt you to stop the dependent services, and then stop
this service.
If the service starts abnormally, i.e. the "Service status" is displayed as "abnormal
stop", you need to collect log and identify the cause of abnormal stop, so the
abnormal stopped service does not start automatically, and you need to perform
manual start.
3.4.3 Detecting service dependency

The dependency of services refers to the service start/stop dependency relationship. Pre-
service refers to this service depending service. Only after the start of pre-service, this service
is available to start; perform dependency detection before the closure of the service, the
detection process is reverse to the service start, only when the pre-service is closed, this
services can be closed.
The dependency detection of services is shown below.
59
Raisecom
Figure 3-11 Procedures for detecting service dependency
3.4.4 Setting service startup mode

Service startup mode contains automatic, manual and prohibited. The system will
automatically detect dependencies between services when the services are started.
If the services are shut down unexpectedly, the system will restart the service. If the
startup fails, it will send alarm.
Configuring auto startup

When set the service to auto startup mode, to start "network management server", if the
service does not start, start this service directly.
In system monitoring client "Process Monitor", right-click the service to start automatically,
select Set Start Model > Automatic in shortcut menu to change the service startup mode to
"Auto".
Configuring manual startup

When set the service to manual startup mode, to start "network management server", if the
service does not start, the service will not start automatically, you need to start the service
manually in system monitoring interface.
60
Raisecom
select Set Start Model > Manual in shortcut menu to change the service startup mode to
"Manual".
Configuring prohibit startup

For prohibit status services, system monitoring client does not provide startup/shutdown
functions. You need to configure to start the service automatically or manually to start a
prohibited service.
select Set Start Model > Ban in shortcut menu to change the service startup mode to
"Prohibit".
3.5 Hard disk management

3.5.1 Showing hard disk information
The interface of "Disk Monitor" in system monitoring supports to view the status information
of server hard disk conveniently and intensively. You can view the current usage of server
hard disk, as shown below.
Figure 3-12 Hard disk information
Table 3-4 Hard disk information parameters

Partition Various hard disk partition information in server
File system File system name of hard disk partition
61
Raisecom
Total space (MB) Total space of hard disk partition
Used space (MB) Used space of hard disk partition
Free space (MB) Free space of hard disk partition
Space usage (%) Space utilization of hard disk partition
Acquisition time Data collection time of hard disk partition, correct to
second
3.5.2 Refreshing hard disk information

Right-click the line of hard disk partition information, and select Refresh to take real-time
collection and management to hard disk partition information of physical server. If the disk
space utilization exceeds the threshold, the system will send alarm; if not exceed the threshold,
refresh the interface.
3.6 Database management

3.6.1 Showing database space usage
The interface of "Database monitor" in system monitoring supports to view the status
information and connection information of database usage conveniently and intensively. You
can refresh the properties, and take expansion operations in this interface according to their
needs, as shown below.
62
Raisecom
Figure 3-13 Database information
Table 3-5 Database information parameters

Database name Database name
Server name Database located server name
IP address Database located server IP address
Data space (MB) Total space of database
Data free space (MB) Free space of database
Database space used ratio (%) Space utilization of database
Acquisition time Collection time of current data information
Description Database description information
Right-click the line of database information and select Refresh to take real-time collection of
database utilization. If the database utilization exceeds the threshold, the system will send
alarm; if not exceed the threshold, refresh the interface.
3.6.2 Database expansion

If the database space exceeds the alarm threshold, the system will report alarm and prompt
you to take database space expansion. After expansion, the system will monitor and calculate
the alarm threshold in accordance with the sum of the size of the original space and expansion
space.
63
Raisecom
Right-click the database record to expand, and click Database Expansion" in shortcut menu
to pop up the following dialog box; fill out the space value to expand and then click OK.
Figure 3-14 Expanding database space
3.6.3 Showing database connection

The interface of Database monitor in system monitoring supports to view the database
connection service, as shown below.
64
Raisecom
Figure 3-15 Database connection service
Table 3-6 Database connection parameters

ID Index value
User Current user, if not root, only show database statement
within limits of authority
Host Access database IP address and port No. to trace error
DB Service connected database name
Command Execution command of current connection:
 Sleep
 Query
 Connect
Time The duration of command

State Database statement status with current connection
Data collection time Current data information collection time
Right-click the line of database service, select Refresh, system monitoring server will take
real-time collection of database information and database connection information as well as
update the interface information.
65
Raisecom
3.7 Server monitoring

3.7.1 Showing server information
The interface of "Server monitor" in system monitoring supports to view the server CPU and
RAM usage status information conveniently and intensively, as shown below. If the RAM
space is insufficient, it will report alarm.
Figure 3-16 Server system resource information
Table 3-7 Server system resource parameters

IP address Server IP address
Server name Server name
CPU total usage (%) The total utilization of current CPU
CPU user usage (%) CPU user utilization
CPU system usage (%) CPU system utilization
CPU idle usage (%) CPU idle rate
Total memory (KB) The total server RAM utilization
Used memory (KB) Used server RAM utilization
Free memory (KB) Free server RAM utilization
Total swap (KB) The total server exchange area utilization
Used swap (KB) Used server exchange area utilization
66
Raisecom
Free swap (KB) Free server exchange area utilization
Acquisition time Current data information collection time
3.7.2 Refreshing system resource information

Right-click the line of server information, select Refresh, system monitoring server will take
real-time collection and management of all physical server information and update the
interface.
3.8 Viewing component information

The interface of "Component Information" in system monitoring supports to view server
component name, version and authorization information conveniently and intensively, as
shown below.
Figure 3-17 Component information
Table 3-8 Component information parameters

Component name Component name
Component version Component version
67
Raisecom
As shown in the above figure, you can set interface display component information numbers
directly for you to view. In addition, when NMS component version is changed, you can
refresh the interface to update the display information in system monitoring client.
3.9 License management

The previous network management service has License authentication mechanism NView
NNM system monitoring will provide service with unified start entrance; the system only take
unified authorization to License authorization when the monitoring server is started and each
service needs not to take License authorization.
3.9.1 Showing License

Select Help > License Manager in system monitoring client system menu to pop up the
following interface.
Figure 3-18 NView network node registration management
Select File > Show > License Info or click in tool bar to pop up the following interface.
68
Raisecom
Figure 3-19 Showing License information

This interface can show user name, the maximum terminals, License type, expiration data,
component License information and product type corresponding registered nodes numbers.
3.9.2 Updating License

If the product License information needs to be replaced, you need to update License
information. Select File > Update License in the menu or click in tool bar to pop up the
Import License dialog box, select the location of License file to import.
69
Raisecom
NView NNM Operation Guide 4 Network topology management
4 Network topology management
This chapter introduces the concepts and management configuration operations of network
topology. Network topology management is a core component of NMS, which shows the
distribution and running status of network resources in a global point of view. In NView
NNM system, network topology is also the launching point of various system applications,
including the following sections:
 Basic concepts
 Topology management process
 Creating topology subnets
 Creating NEs
 Synchronizing NE data
 Creating link
 Creating symbol
 Configuring common information of topology object
 Deleting topology object
 Common operations of topology management
 Configuring customized view
 Viewing topology list
4.1 Basic concepts

Network topology contains subnet, symbols, NEs, links and other topological objects, which
shows the distribution and running status of network resources. NView NNM network
topology also supports to launch various applications. To grasp the basic concepts of topology
management contributes to perform topology management functions.
4.1.1 Main view of topology

In NView NNM, "topology" is the main interface of all subnets and NEs, which can achieve
the network management network subnet, symbols, NEs, and link topology management
functions. Login NMS client and open the main view interface of "topology" at first.
Topology interface layout is shown in the following figure.
70
Raisecom
 The left side shows topological objects and hierarchical relationships between them in
the form of topology tree.
 The middle part shows all topology objects on current subnet and the connection
relationship between them in the form of topology graph.
 The right side shows topology objects properties information in the form of property or
graphic symbol panel.
 The bottom part shows subnet or NE alarm information in the form of list.
Figure 4-1 Main view of topology
The alarm panel is default to display, properties and graphic symbol panel is default
not to display. In topology function menu, click System > Display > Bottom > Alarm,
System > Display > Right > Property or System > Display > Right > Legend to
open/close the corresponding panel.
4.1.2 Topology tree

Topology tree refers to show subnet, NEs and symbols in the network management topology
in the form of tree with subnet first and NE later. Topology tree and topology graph are linked
with each other, to select topology objects on topology tree, and also select the objects on
topology graph at the same time.
The topology tree supports order, expand/shrink, and quickly query functions, as shown below.
Table 4-1 Topology tree function button

Icon Description
Ascend/Descend in number and letter orders.
71
Raisecom
Expand/shrink topology tree.
Enter keyword to find the topology object names in

topology tree.
□
+ Expand the topology objects in topology tree.
□
一 Shrink the topology objects in topology tree.
Each node in topology tree is composed of icon, text and color. Different icons are used to
distinguish subnet, NE, remote card, chassis and other topology objects and support to display
name, device name or IP address etc. text information. The color of icon shows the current
highest alarm level, black indicates the offline status of topology object.
4.1.3 Topology graph

The topology graph shows the contents of some a subnet, including various nodes and the
links between nodes. The top of topology graph is the topology operation toolbars and menus;
the bottom part supports to show current alarm list; the right side is properties and graphic
symbol, which lists the selected node properties information and graphic symbol description.
Each node in topology graph is composed of icon, text and color. Different icons are used to
distinguish subnet, NE, remote card, chassis and other topology objects and support to display
name, host name or IP address etc. text information. The color of icon shows the current
highest alarm level, black indicates the offline status of topology object.
4.1.4 Subnets
Subnet is the logical division of the network topology structure in network management
system, which is helpful to show the topology of NEs clearly in network management system.
The internal structure of subnet contains subnet, NE, symbols, links and other topology
objects.
Subnet supports security control; you can plan subnet security policy to control the view,
configure, browse and operate permissions.
Double-click the subnet icon to view the subnet.
4.1.5 Gateway NE subnets

The gateway NE subnet refers to the subnet with remote/central office structure features. The
gateway NE subnet contains device NEs and the NE related other remote device NEs, chassis
or subnet.
To create device NE with central office/remote structure features (For example iTN2100,
EPON etc.), the system will create gateway NE subnet automatically, double-click gateway
NE subnet node to view gateway NE subnet.
The gateway NE subnet supports topology expansion function in the same layer to view the
following topology structure.
72
Raisecom
For gateway NE subnet of EPON OLT devices, each PON port can automatically
create one "PON network" subnet and "PON network" can automatically create
optical splitter and ONU NE.
4.1.6 NEs
The network device is managed as Network Element (NE) in the network. Link connection
can be established between the NEs to represent the actual device connection relationship.
The network device alarm can be shown on NE to prompt the operation and maintenance staff
to view. The NE will show black offline status when the communication between network
device and network management is interrupted.
NE supports security control; you can plan NE security policy to control the view, configure,
browse and operate permissions.
Double-click NE topology icon to enter network manager function interface. The NE subnet
supports topology expansion function in the same layer to view the following topology
structure.
4.1.7 Pre-configured NEs

The pre-configured NE is a special kind of NE; network management NE configuration is
only saved in the database, but not issued to the actual device. The configuration will be
issued to actual network device when switch pre-configured NE to non-pre-configured NE.
The role of pre-configuration is to take service configuration without devices so as to issue
configuration quickly in device connection. To batch services opening or batch devices
upgrade will save a lot of configuration time, improve the configuration efficiency. In addition,
pre-configuration can test the configuration correctness in order to reduce configuration errors
without device connection.
You can start the pre-configuration function of NView NNM management software in the
early building of the network and take pre-configuration to the nonexistent NE.
4.1.8 Virtual NEs

Virtual NE refers to the NE cannot be managed by NView NNM.
Currently it only supports to create virtual OLT NE, apply to access Raisecom ONU to OLT
from other companies and manage ONU NE through NView NNM.
4.1.9 Network management NEs

Network management NE is the network management server NE in NMS, which is created by
NMS automatically; the default name is the "Computer name" of server host, and network
management NE does not support to remove. Network management NE can show network
management server alarm so that you can monitor the operating situation of network
management system.
In distributed deployment of performance management component, the system will create
network management NE respectively to network management server and performance server.
73
Raisecom
4.1.10 Representation of topology

Each node in the topology graph is composed of four parts:
 Icon: the icon is specified when creating the node.
 Text: beneath the icon, supporting to display name, device name or IP address.
 Color: for subnet and device, there are five kinds of colors to show alarm status. The
colors are consistent to system alarm colors for easy recognition.
─ For subnet, the color shows the nodes color with highest-level alarm status in all
nodes of the subnet.
─ For NE device, the color shows the highest-level alarm event corresponding color in
all current alarm events of NE device.
─ The topology node without alarm will show green and black indicates the device is
offline.
 Decoration: above the topology node. Different decoration indicates different status, for
example alarm confirmation status, offline status, management status, and etc.
The kernel version V 5.4 provides topology graphic symbol, which describes the
graph and status of all topology objects. Click topology function menu System >
Display > Right > Legend to open the graphic symbol panel, and support to show
the corresponding graphic symbol according to selected topology objects.
Network management system shows topology object in different ways, as shown below.
Table 4-2 Topology object instance

Node type Color Instance
Subnet Different subnet alarm status corresponds to
different color, the normal status is green
Gateway Different subnet alarm status corresponds to

NE different color, the normal status is green
subnet
NE Different device alarm status corresponds to

different color, the normal status is green
Symbol No change of color
The decoration instance is shown as below.
74
Raisecom
Table 4-3 Node decoration instance

Decoration Signification
The device or card node is not in the management domain.
Operation is not applicable to the node.
Ping is unsuccessful on this device.
The chassis or card corresponds to the node is lost.
The device corresponding to the node is a member device in the

cluster.
The device corresponding to the node is the master device of the
cluster.
Unacknowledged current alarm exists on the device or card
corresponding to this node.
Alarm filter rule has been set up on the device corresponding to the
node.
Performance data collection task has been deployed on the
corresponding node.
The device corresponding to the node has been attached to customer
information.
The node is performing "synchronization", NMS is synchronizing
device resource information.
The node performs "synchronization" unsuccessfully; NMS cannot
synchronize device resource information.
Pre-config node. (Only iPN2100 is in support of pre-config now, so
this icon is only available to iPN2100 device.)
The node is performing "Configuration Synchronization", NMS is
synchronizing device configuration information (it is only available
to pre-configured iPN2100 device node now).
The node performs "Configuration Synchronization"
unsuccessfully; NMS cannot synchronize device configuration
information (it is only available to pre-configured iPN2100 device
node now).
Alarm bubble indicates that there is unacknowledged alarm on the
node.
 Color: the highest-level current alarm, and display the corresponding
color according to the alarm level.
 Number: the number of unacknowledged highest-level alarms.
 Letter: alarm level C, M, m, W indicate Critical alarm, Major alarm,
Minor alarm and Warn alarm respectively.

 +: indicates that besides the highest-level alarm, there are still other
levels of alarm has not been confirmed.
75
Raisecom
4.1.11 Topology symbol

Topology symbol is schematic symbol, which cannot be managed by NView NNM, but can
show network structure better.
4.1.12 Customized view

Customized view is the special view defined by the login user. You add subnet, NE or symbol
and other topology objects to customized view for centralized monitoring.
Customized view can display various status information of NE alarm and can also modify the
topology object properties and initiate a variety of NE management functions.
 Topology objects in customized view only can be added by right-click the topology
object and then click Add to Custom View.
 To remove topology objects in customized view only affects the customized view,
but not remove the corresponding topology objects in network management.
 Topology objects in customized view do not involve in the report forms and
inventory statistics.
4.1.13 Service view

Service view is NView NNM provided NE service topology view. For example, EPON
protection view is a service view. This view shows the protection topology structure between
OLT and ONU, supporting to display the topology of OLT Ethernet ring, ONU Type-D
protection.
Currently, service view only contains EPON protection view.
4.1.14 Topology graphic symbol

The topology nodes on topology view are shown as various icons, NView NNM system has
classified these icons and created graphic symbol. To add a node, select the node classify and
specific type in classify and create node, then the node will associate with the device type icon
of corresponding device and show the corresponding icon on topology. You can view the icon
and description in graphic symbol.
4.1.15 Topology layout

When displaying the objects on a topology view, you can adjust the topology layout to
arrange the topology object's position reasonably or arrange them to present their position
information. NView NNM system introduces the following two layout patterns into the
topology view management:
 Customized layout: You can prescribe positions for symbols and save the self-defined
layout. The layout will keep unchanged until the next layout saving operation.
 Automatic layout: The system provides you with some layouts, like bus layout, tree
layout, random layout, and etc. The layout will self-adapt to the current situation of the
view (the number of symbols, the links that connect the symbols, the viewable area, and
etc.). The automatic layout function will introduces some algorithms to arrange symbols
onto reasonable position. After saving the layout, the topology position will net change
until next time to save layout.
76
Raisecom
4.2 Topology management process

To plan topology network, in addition to considering the topology relationship of NEs and the
actual position, you still need to consider subnet and the number of NE in subnet so as to view
and manage. The topology management often needs to take configuration according to the
following process:
Subnet NE Link
Create subnet Create NE Create link
(Optional) Delete Configure link

Configure NE data
subnet information
Modify NE (Optional) Delete

information link
Configure offline
detection
(Optional) Delete
NE
Figure 4-2 Topology management process
4.3 Creating topology subnets

4.3.1 Dividing subnet structure
To deploy NE in topology, you need to design subnet division structure. Network
management topology shall not only reflect actual communication network topology structure,
but also facilitate operation staff to take daily maintenance and operation.
 For easy operation, it is recommended that there are 7 subnet layers at most in the
internal subnet.
 For easy browsing, it is recommended that the number of NE and symbols in each subnet
is 500 at most.
 For convenient and secure maintenance and management, it is recommended to divide
subnet structure according to some certain rules. For example, to divided subnet in
accordance with the following ways:
─ Divide from the geographic location of device
─ Divide from the device provided service
77
Raisecom
─ Divide from the device type

─ Divide from the device IP address
─ Divide from the device maintenance staff
4.3.2 Creating subnets

Please perform the following operations to create subnet.
Step 1 Create subnet.
 In topology main view, customized view or subnet topology, right click the blank space
and click Add > Add Subnet in shortcut menu, the mouse will change to "+" status.
 Click the space to place subnet icon to pop up a dialog box, as shown below.
 Click Save to issue the configuration.
 After the subnet is added, it will pop up a dialog box, asking Continue to add? Click Yes
to create subnet again. Otherwise click No.
Figure 4-3 Adding subnet
Table 4-4 Adding subnet parameters

Parameter Value Description
Symbol 100 characters at most Configure subnet name.
name
Remark 100 characters at most Configure subnet description.
78
Raisecom

Display Click the left subnet Configure subnet type.
name type tree to select
topology type.
4.4 Creating NEs

4.4.1 Batch auto-discovery of NEs
NView NNM device auto-discovery function supports the auto-discovery of NE device in
network segment. For not need to specify the NE device type, it is usually applied to the auto-
discovery of multiple NEs in network.
Step 1 Configure scan task.
 Click system menu Topology > Device Scan and Poll to enter device discovery and
polling interface.
 In the left function navigation tree, click Device Scan > Scan Task, click Add, the
configuration parameters are shown in the following table.
 Click OK to create scan task.
Table 4-5 Configuration parameters description

 Range IP
IPv4 Configure auto-discovery mode and range.
 Subnet IP
 Single IP Different mode needs to configure different
value.
 IP range: configure beginning/ending IP address.
 Subnet range: configure IP subnet and subnet
mask.
 Single IP: configure IP address.
IP count – Calculate IP numbers to scan automatically.

Status Enable Configure to start scan task or not.
Select start in batch auto-discovery.
Specified – Configure auto-discovery NE subnet to add.
subnet
Click to select the created subnet.
Protocol – Configure protocol template to use in auto-
template discovery.
Click to select protocol template. The
protocol template contains protocol type,
version and community parameters used in
auto-discovery.
79
Raisecom
Step 2 Start scan task to perform batch auto-discovery of NEs.

 In scan task interface, click Scan to enter scan report interface.
 The scan is complete until the progress reaches 100%.
 Batch auto-discovery of NEs is complete after scanning, the auto-discovery NE will be
added to network management topology.
The device auto-discovery function also supports periodic auto-discovery, protocol

template, scanning filter functions; see section 5.6.3 Device scan for the detailed
function description and operation methods.
4.4.2 Creating single NEs

Please perform the following operations to create single NE.
Step 1 Create single NE.
and click Add > Add Device in shortcut menu, the mouse will change to "+" status.
To add NE topology objects, you can initiate Create topology object function
according to the following operations.
 In topology toolbar, click and click Add device in shortcut menu.
 In Topology function menu, click Edit > Add > Add device in shortcut menu.
 Click the space to place NE icon to pop up a dialog box, the parameters are shown as
below. "*" indicated the required parameter. To create single NE, you need to fill with
"NE name", "IP address" and "NE model" at least.
 Click Save to issue the configuration and create single NE.
 After the operation is complete, it will pop up a dialog box, asking Continue to add?
Click Yes to create NE again. Otherwise click No.

Base info
Net name Created subnet Configure NE located subnet.
Click parameter text box and then
click to select NE located
subnet.
By default, select the subnet to initiate
Add NE operation.
NE name 100 characters at Configure NE name.
most NE name is customized name to NE.
80
Raisecom

IP address Dotted decimal IP Configure NE IP address.
address After IP address is configured, click
Verify NE type, if the NE type
verification is successful, configure
device model automatically, othervise,
select device model manually.
Type NView NNM Configure NE device model.
supported device In the left device type tree, click to
model select device type.
 Unspecified
Purpose Configure NE purpose.
 Common user access
 Major account access NE purpose is user's classification to
 Community NE purpose for the easy management
aggregation of NE.
 Central office
aggregation
 Relay transmission
Supplier 100 characters at Configure NE supplier information.

most
Serial NO. 100 characters at Configure NE serial No. information.
most
Remark 100 characters at Configure NE remark information.
most
Management information
Read 32 characters at Configure NE SNMP read
community most community.
The read community of device and
NE must be the same for normal
network management.
Write 32 characters at Configure NE SNMP read/write
community most community.
The read/write community of device
and NE must be the same for normal
network management.
Retry 1–5 Configure retry times for NE offline
Unit: times detection.
NView NNM judges that the NE is
offline over retry times.
Timeout 1–30 Configure NE SNMP overtime.
(Sec) Unit: second NView NNM judges that the SNMP
management operation fails over
overtime.
81
Raisecom

SNMP port 1–65535 Configure NE SNMP destination
communication port.
SNMP destination port and the device
actually used SNMP Rx port must be
the same for normal network
management.
By default, use 161 port and not
change.
 SNMP V1
SNMP Configure NE SNMP protocol
 SNMP V2c
version version.
 SNMP V3
The device needs to configure SNMP
V3 parameters with SNMP V3
protocol for normal network
management.
SNMP V3 – Configure SNMP V3 parameters.
parameters Click parameter text box and then
(Only click toconfigure the following
display parameters:
when SNMP  User name: Device SNMP V3 username
version is  Security level: device SNMP security
"SNMP
authorization mode, supporting
V3")
"noAuth,noPriv", "Auth,noPriv" and
"Auth,Priv".
 Authorization protocol: device
authorization type, supporting MD5 and

SHA.
 Authorization password: SNMP
authorization secret key.

 Privacy protocol: device encryption type,
supporting DES and AES.

 Privacy password: SNMP encryption
secret key.
Offline detecting
 Checked
Offline Configure to enable/disable NE
 Unchecked
detecting offline detection.
Checked indicates to enable NE
offline detection, NView NNM can
detect whether the NE is offline
automatically according to polling
cycle.
 ICMP Ping
Polling Configure detection mmmode for
 SNMP Ping
protocol offline detection.
82
Raisecom

 30s
Polling Configure offline detection cycle.
 60s
interval When the polling interval is reached,
 5min
 15min NView NNM will take offline
 30min detection automatically; check
 60min whether the device is offline and
generate offline alarm to the offline
device.
You can configure a smaller polling
interval for important device, but
more NE with the same polling
interval will lead to offline detection
delay. See Chapter 5 Device discovery
and polling for detailed configuration
and description.
Project information
Area name 100 characters at Configure information about the area
most wherethe NE is.
Project 100 characters at Configure NE subordinated project
most information.
Room 100 characters at Configure NE subordinated
most machineroom information.
Shelf – Configure NE subordinated rack
information.
Click parameters text box, select the
created rack indrop-down list (Rack
information can be added/deleted in
physical inventory).
Integrator 100 characters at Configure NE contractor information.
most
Maintenance person
Maintenance – Configure NE contact.
person Click parameters text box and then
click to select the contact.
(Contact information can be
added/deleted in inventory address
book).
TEL – Configure acconding to the selected
telephone information automatically.
Address – Configure acconding to the selected
address information automatically.
83
Raisecom
 For devices supporting pre-configuration function, such as to create iTN2100 and

Gazelle RP300H NEs, it will show "pre-configuration" parameters. Check "pre-
configuration" to create iTN2100 pre-configuration NE. See iTN2100 Network
Element Management Manual for the specific instructions.
 To create ONU NE, the configuration parameters include ONU registration
information and other parameters; see EPON Network Management Manual for
the specific description.
4.4.3 Copying NE
To copy a NE with the same properties from the present NE can simplify the operation to
create NE.
Step 1 Copy NE.
 In topology main view or subnet topology, right click the NE icon to copy; click Edit >
Copy to in the shortcut menu to pop up Select subnet dialog box.
 Select Copy NE located subnet, click Save to enter Select subnet interface
automatically, the mouse will change to "+" status.
 Click the space to place NE icon to pop up Add device dialog box, the parameters are
the same to parameters to create subnet.
 Configure NE IP address and can also change other parameters information.
 Click Save to issue the configuration and copy NE.
 After the operation is complete, it will pop up Confirm dialog box "Continue to add?",
click Yes to copy NE again, click No to close the dialog box.
 For devices supporting pre-configuration function, such as to copy iTN2100 and

Gazelle RP300H pre-configuration NEs by Edit > Copy to, the created NE is still
pre-configuration NE and cannot copy the pre-configuration data in pre-
configuration NE.
 For devices supporting pre-configuration function, such as iTN2100 and Gazelle
RP300H pre-configuration NEs, if not perform Cancel pre-configuration
operation, you can copy and create NE with pre-configuration data. Right click NE
icon, click Copy NE to copy and create pre-configuration NE. The created NE will
also carry the pre-configuration data has been completed in the original NE.
 For ONU NE or splitter, use Edit > Copt to to copy, please select PON network as
the NE located subnet to copy and create.
Copying pre-configuration NE with pre-configuration data

For devices supporting pre-configuration function, such as iTN2100 and Gazelle RP300H
pre-configuration NE can take pre-configuration operation, configure to save the data in
database and not issue to actual device. You can copy and create a pre-configuration NE
according to the following steps; however, different to common NE copy, the copied and
created NE can carry the original pre-configuration data.
84
Raisecom
Only the operation without switching pre-configuration status, i.e. not to issue pre-
configuration data to actual device can copy and create pre-configuration NE with
pre-configuration data.
Step 1 Copy pre-configuration NE with pre-configuration data.
 In topology main view or subnet topology, right click the NE icon to copy; click Copy
NE in the shortcut menu to pop up Select subnet dialog box.
 Select Copy NE located subnet, click Save to enter Select subnet interface
automatically, the mouse will change to "+" status.
 Click the space to place NE icon to pop up Add device dialog box, the parameters are
the same to parameters to create subnet.
 Configure NE IP address and can also change other parameters information.
 Click Save to issue the configuration and copy NE.
click Yes to copy NE again, click No to close the dialog box.
4.4.4 Adding cluster device

There are such type of devices, the device itself has not Ethernet management port, the SNMP
management is to entrust itself to other device or host with Ethernet management port through
in-band network management or other network management channel (For example serial port
management channel). At this time, the management IP address of this type of device is the
same to the IP address of entrusted management device. Then the entrust device and entrusted
device are called as one cluster; the entrust device is cluster member device and entrusted
device is cluster master device.
In order to ensure the efficiency of the system, the NE IP address is generally different, so to
add the device with repeat IP address, the client will prompt "IP address already exists, please
reenter!". However, the added cluster device IP address is the same, so you need to change
parameters in client system configuration file System.properties to start add cluster device
function. Use Wordpad to open System.properties and find cluster.enable parameters, the
default property is false, change it to true and save, then restart client to add cluster device
with the same IP address. The System.properties file is stored in the path
C:\NMS\NView\NNM5\client\config.
To add such type of device, create directly managed device or host node in topology at first
(cluster master device), then create entrust management device node (cluster member device).
To fill in the node property, you need to enter IP address same to entrusted device. At this time,
the system will prompt that "The IP address you entered already exists, the device will be
added to the cluster as a member device, continue?", Select "Yes" to add cluster member
device. The cluster member device node will show the icon and cluster master device
node will show device icon for distinction.
To add switch cluster device, please use EMS Config > Switch > Cluster MGT to add; for
the detailed process, please see switch device NE management manual.
After starting the function to add cluster device, you can modify device IP address to
add the device to a cluster or remove from some cluster. To modify the device IP, the
system will check whether the IP address is existed, if yes, it will prompt you to add
85
Raisecom
this device to cluster with specified IP device as main device, if choose "Yes", the
device will become cluster member, it will show member icon on the node, cluster
master device will show master device icon for distinction.
To modify a cluster member device IP address so as to make it different from cluster
master device, the device will leave the cluster. Similarly, to modify a cluster member
device IP address to make it the same to the other cluster master device IP, this
member will be switched from one cluster to the other cluster.
4.5 Synchronizing NE data

4.5.1 Synchronizing NE data
When the NE is created, NView NNM will perform NE syncs operation automatically, the NE
will synchronize device, card, and port resource data. If the device is changed or you need to
synchronize the NE data manually, please perform sync NE data operation at first.
Step 1 Synchronize NE data.
 In topology main view or subnet topology, right click the NE icon to sync and then click
Resource Synchronization in shortcut menu.
 Pop up confirmation box to prompt that "The synchronization command has been sent",
click OK.
 Above the NE icon, it will show , which indicates in the process of synchronization.
 When disappears, the operation to sync NE data is complete.
For gateway NE subnet, double-click or click shortcut Expand to view sync status
icon.
4.5.2 Synchronizing NE pre-configuration data

For devices supporting pre-configuration function, such as iTN2100 and Gazelle RP300H
pre-configuration NE supports to synchronize the device configuration data to database as the
configuration data of pre-configuration NE.
Step 1 Synchronize NE pre-configuration data.
 In topology main view or subnet topology, right click the pre-configuration NE icon to
sync and then click Configuration Synchronization in shortcut menu.
 Pop up dialog box to prompt that "Take resource sync before configuration sync?", click
Yes to perform resource sync and then take pre-configuration data sync. Click No not to
perform resource sync but take pre-configuration data sync directly.
 Pop up confirmation box to prompt that "The synchronization command has been sent",
click OK.
 Above the NE icon, it will show , which indicates in the process of synchronization.
 When disappears, the operation to sync NE pre-configuration data is complete.
86
Raisecom
It is recommanded that you perform resource sync first and pre-configuration data
sync later.
4.6 Creating link

Link can better show the connections between NEs.
4.6.1 Creating physical link

Create physical link.
 In topology main view or subnet topology, click to select the link source device NE,
press Ctrl and click to select the link destination end device NE.
 Select two NEs, release Ctrl key, right-click on one network element icon and then click
Add Link in the shortcut menu to pop up Add Link dialog box, the parameters is shown
below.
To create link, you can also click topology function menu Edit > Add > Add Link, and
then select source node in topology and hold the left mouse button and drag it to the
destination end node, pop up Add Link interface for configuration.
 Click Save to issue the configuration and create link.
 After the operation is complete, it will pop up Confirm dialog box "Continue to
add?", click Yes and then click source node and drag it to destination end node to
create link again, click No to close the Add Link dialog box.

Base info
Link name 254 characters Configure link name.
at most Link name is the customized
name to the link..
 Common link
Type Configure physical link type.

In the left link type tree, click to
select link type.
Source resource – Show link source end NE type.
type
Source resource ID – Show link source end NE name.
Source resource – Configure link source port.
name Click parameter text box and then
click to select device/card
port.
87
Raisecom

Destination – Show link destination end NE
resource type type.
Destination – Show link destination end NE
resource ID name.
Destination – Configure link destination port.
resource name Click parameter text box and then
click to select device/card
port.
 One-way
Direction Configure link transmission
 Two-way direction.
Attenuation (dB) – Configure link attenuation value.
Length (m) – Configure link physical length
value.
 Yes
Is protected Configure whether the link is
 No protect link.
 Unsupport
Active status Configure link active status.
 Activated
 Inactivated
Remark 200 characters Configure link remark

at most information.
Maintenance person
Maintenance – Configure link contact.
person Click parameters text box and
then click to select the
contact. (Contact information can
be added/deleted in inventory
address book).
TEL – Configure acconding to the
selected telephone information
automatically.
Address – Configure acconding to the
selected address information
automatically.
 It can only create logical link between subnet and NE or subnet and subnet.
 When the NEs on both ends of the link are not in the same subnet, the link will
show as link from NE to the other subnet.
 Please select the port with the same speed as source/destination port on both
ends of link, and each port can only belong to one link; you cannot select the port
which has already created link.
88
Raisecom
 To select source/destination port, the created link used port cannot to be select,
that is to say, each port in the same network management can only create one link.
 To create link, you can also click topology function menu Edit > Add > Add link,
and then click to select source end node in topology and hold the left mouse
button and drag it to the destination end node, pop up Add Link interface for
configuration.
4.6.2 Creating logical link

Step 1 Create logical link.
 In topology main view or subnet topology, click to select the link source device NE,
press Ctrl and click to select the link destination end device NE.
 Select two NEs, release Ctrl, right-click on one NE icon and then click Add Link in the
shortcut menu to pop up Add Link dialog box, the parameters is shown below.
 Click Save to issue the configuration and create link.
click Yes create link again, click No to close the Add Link dialog box.

Base info
A – Show link source end node.
Z – Show link destination end node.
Link name 254 characters at Configure link name.
most
Remark 100 chracters at Show link descriptions.
most
Link type Logical link Configure logical link type.
In the left link type tree, click to select
"Logical link".
Link info
 One-way
Direction Configure link transmission direction.
 Two-way
1
Width Configure link display width.
2
3
4
5
 Solid
Style Configure link display style.
 Dash
 Chain
 Dot
 Zigzag
 Broken

89
Raisecom

 Parallel
Shape Configure link tdisplay shape.
 Straight
 Inflection point
 Perpendicular
 Curving
 Denticle
 crosswise to device
 Longitudinal to
device
 to set goes against
 to set at bottom
 to set at left
 to set at right
4.7 Creating symbol

The symbol can show the buildings and users in actual environment in topology reasonably.
Step 1 Create symbol.
and then click Add symbol in the shortcut menu, the mouse will change to "+" status.
 Click the space to place symbol icon to pop up Add symbol dialog box, the parameters
is shown in the following table.
 Click Save to issue the configuration and copy symbol.
click Yes to copy symbol again, click No to close the dialog box.

Base info
Symbol 100 characters Configure symbol name.
name at most
Remark 100 characters Configure symbol description.
at most
Display – Configure symbol type.
name In the left symbol type tree, click to select
"Symbol link".
4.8 Configuring common information of topology object

Most information of subnet, NE, link and symbol can be configured in creation, and also
modified after creation. The properties parameters are consistent to the information in creation,
90
Raisecom
and the properties not allowed to modify will not appear in the modify interface. This section
mainly introduces how to configure the common information of topology object.
Topological object information is only stored in the network management system for
topology management, and not issued to the actual physical device, so the
information cannot be viewed on actual device through command line.
4.8.1 Configuring NE name

The NE name is the NView NNM NE configuration name. The NE name can be displayed in
the topology view through topology setting function after configuration.
Step 1 Configure NE name.
 Right-click the NE icon and click Edit > Edit Properties in shortcut menu to open the NE
properties edit interface.
 Click NE name parameters text box, enter NE name, 100 characters at most.
 Pop up prompt confirmation box to display "Edit successfully", click OK to complete the
configuration.
4.8.2 Configuring NE SNMP management parameters

When the device SNMP management parameters configuration is changed, for example,
modify the device community parameters, you need to configure NE SNMP management
parameters for normal network management.
 Please confirm the device SNMP parameters before configuring NE SNMP

management parameters; the error correction of NE SNMP management
parameters will not take normal network management.
 To modify NE SNMP management parameters will not change the SNMP
management parameters on actual device. If you need to modify the SNMP
management parameters on actual device, please use the configuration function
provided in device NE management.
Step 1 Configure NE SNMP community parameters.
 Right-click the NE icon and click Edit > Edit Properties in shortcut menu to open the
NE properties edit interface.
 Click read/write community parameters text box to configure NE SNMP community
parameters.
 Pop up prompt confirmation box to display "Edit successfully", click OK to complete
the configuration.
Step 2 Configure NE SNMP timeout parameters, mainly used to the situation that the device needs
longer time to process SNMP packets.
 Click timeout parameters text box to configure NE timeout parameters.
91
Raisecom

the configuration.
4.8.3 Configuring NE offline detection

When the device needs to change the polling interval of offline detection, please configure the
NE offline detection parameters.
 Click polling interval parameters text box to configure NE offline detection polling
parameters.
the configuration.
4.8.4 Configuring project information

When you need to take a record of NE project information in NView NNM, please configure
project information parameters.
 Click project, room, rack and contractor parameters text box to configure NE project
information.
the configuration.
4.8.5 Configuring expansion properties

When you need to take a record of some expansion information of NE in NView NNM, for
example VLAN information, office oriented port, uplink circuit information and etc., please
configure expansion properties.
 Click network management VLAN, user VLAN, outer VLAN ID, office oriented switch,
office oriented port and uplink circuit parameters text box to configure NE expansion
properties information.
the configuration.
92
Raisecom
4.8.6 Configuring the contact information of maintenance staff

When you need to take a record of the contact information of maintenance staff in NView
NNM, please configure the contact information of maintenance staff.
Step 1 Create contact information of maintenance staff.
 In system menu, click Inventory > Address Book to open address book interface.
 Click in tool bar to open Add Panel interface and fill in the related contact
information. To ensure data consistency, the job number and name of address book are
not allowed to repeat.
 After filling in the information, click Add to pop up message confirmation box, click
OK to complete the add operation. The newly added address book will be displayed in
Newly Added Data Labels page.
 Right-click the shortcut to select Refresh > Refresh All; the added address book
information will be transferred to the query results tab page.
Step 2 Configure contact information of NE maintenance staff.
 Click "Maintenance staff" parameters text box and then click to pop up the
information list of maintenance staff in address book.
 Click to select the maintenance staff records and then click OK to fill in the contact
telephone and address of maintenance staff automatically.
the configuration.
4.8.7 Configuring link information

When you need to take a record of link name, link features or needs to modify link port,
please configure link information.
Step 1 Configure link information.
 Right-click the link and click Edit > Edit Properties in shortcut menu to open the link
properties edit interface.
 Click link name, link source/destination port names, speed multiples, attenuation,
whether to protect and other parameters to configure link information.
the configuration.
4.8.8 Configuring symbol information

When you need to take a record of symbol node name and description in NView NNM, please
configure symbol information.
Step 1 Configure symbol information.
 Right-click the topology symbol and then click Edit > Edit Properties in shortcut menu
to open the symbol properties edit interface.
93
Raisecom
 Click node name or description to configure symbol information.

the configuration.
4.9 Deleting topology object

The NE, subnet and other topology objects can be deleted only when they do not need to take
NView NNM management.
When the topology objects are deleted, the associated resources, alarm data, will
also be deleted; the deleted data cannot be recovered, please use with caution
according to the actual situation.
4.9.1 Deleting subnet

The subnet can be deleted when the subnet and NE do not need to take NView NNM
management.
When the subnet is deleted, all topology objects and topology objects associated
resources, alarm data in the subnet will also be deleted; the deleted data cannot be
recovered, please use with caution according to the actual situation.
Step 1 Delete subnet.
 Right-click the subnet and click Delete in the shortcut menu to pop up confirmation
dialog box, as shown below.
Figure 4-4 Confirming to delete a subnet

 Click Yes to delete; click No not to delete.
 Pop up prompt confirmation box to display "Delete successfully", click OK to complete
the configuration.
4.9.2 Deleting NEs

The NE or gateway NE subnet can be deleted when they do not need to take NView NNM
management.
94
Raisecom
When the NE or gateway NE subnet is deleted, the associated link, port resources
will also be deleted. If the deleted NE is managed directly by NMS and other devices
take management through this NE, then all device chassis, card and port information
taken management through this NE will be deleted. The deleted devices cannot take
management through NMS.
Step 1 Delete NE.
 Right-click the NE and click Delete in the shortcut menu to pop up confirmation dialog
box, as shown below.
Figure 4-5 Confirming to delete a NE

the configuration.
You can select the following modes to delete multiple NEs:

 Press on Ctrl and click to select multiple NEs.
 Press and hold the left mouse button and drag to select multiple NEs.
 Press on shortcut keys Ctrl + A to select all the NEs in the current subnet.
4.9.3 Deleting links

When the link no longer needs NView NNM management, please delete the link.
Step 1 Delete link.
 Right-click the link and click Delete in the shortcut menu to pop up confirmation dialog
box, as shown below.
Figure 4-6 Confirming to delete a link

95
Raisecom

the configuration.
4.10 Common operations of topology management

4.10.1 Searching subnet and NEs
The complex network environment will make a large number of subnets and NEs exist in
topology and the search in relatively troublesome. Therefore, you can use search function to
find NE quickly.
You can search NE through two ways:
 Search in topology tree
 Search in topology graph
Searching subnet and NEs in topology tree
Enter NE display information in the network topology tree at the left side
of NView NNM main interface, click icon to start the search. The searched destination
NE will show in the drop-down node of network topology.
In the topology menu bar, click System/Topology Settings to configure topology

node display name as "Name, "Host name" or "IP address". You need to search in
topology tree according to the current configuration display information. For example:
to configure "IP address", you need to enter IP address to search.
Searching subnets and NEs in topology graph

In the topology graph menu bar of NView NNM main interface, click System > Search or
click icon in the toolbar to pop up the following interface, the parameters description is
shown in the table below.
96
Raisecom
Figure 4-7 Searching subnets and NEs in topology graph (1)

Parameters Value Description
 Name
Search Select find category.
 Device name
category
 IP address
Search Name or Enter the content of specified find

content dotted decimal category.
IP address
 Perfect match
Condition Perfect match indicates the find contect
 Contain
match and enter content are exactly the same.
Contain indicates the find contect and
enter content are partly the same.
After entering the parameters, click Find next to locate network node location in topology
graph. Click Detail to show the detailed information of NE node, as shown below. Right-click
a piece of detailed information and click Topological Orientation in the shortcut menu, or
double-click a piece of detailed information to locate and find topology object quickly in
topology graph.
97
Raisecom
Figure 4-8 Searching subnets and NEs in topology graph (2)
4.10.2 Refreshing the entire network topology

To refresh the entire network topology will help you to grasp the real-time NE information;
the function entrance and operation are shown in the following table:
Table 4-11 Function entrance description

Function entrance Operation
Topology menu bar System > Refresh entire network Click
topology
Topology tool bar icon Click
Pop up the following Confirm dialog box, and click Yes to refresh the interface.
Figure 4-9 Refreshing the entire network topology
4.10.3 Adjusting topology layout

You can adjust the topology objects layout in topology. To adjust the layout manually, click
and press on the left mouse button to drag the topology object to specified location; or click
in topology tool bar to delay to drag the button, and then click topology object and drag
mouse to select the specified location, release the left mouse to adjust the topology object
location.
98
Raisecom
The topology view management adopts the following two layouts; when the layout is saved,
the topology object location will not change until next time to save.
 Customized layout: to use customized layout, the operator will drag topology object to
define the specific layout location.
 Automatic layout: to use automatic layout, the system will provide some layout modes,
such as bus layout, tree layout, random layout and etc. These layout modes will place the
symbol to reasonable location automatically according to current view situations
(number of symbols, the connection situation between symbols and the visual area size
of the view).
NView NNM provides the following automatic layout modes.
 Tree layout: to show topology layout in the form of tree according to link connection
relationship, the root node and leaf node of tree are layouted from top to bottom.
 Left tree layout: to show topology layout in the form of tree according to link connection
relationship, the root node and leaf node of tree are layouted from left to right.
 Grid layout: the nodes are layouted in the same interval.
 Star layout: to show topology layout in the form of star according to link connection
relationship.
 Symmetrical layout: to show topology layout according to link connection relationship,
the angle between the links is same.
 Bus layout: nodes are layouted in the same interval with the shape of bus connection.
The EPON device PON network structure can be shown in tree layout automatically.
To use the system provided automatic layout function, you can select the automatic layout
mode through the following entrance

Topology menu bar Layout Click
Shortcut menu bar Modify Layout Right click the blank space in topology
After modification, you need to save the current topology layout. It will show the current
layout to open topology next time; the function entrance and operations are shown as below.

Topology menu bar Layout > Save Click
Layout
Shortcut menu bar Save Layout Right click the blank space in
topology
99
Raisecom
4.10.4 Moving subnets and NEs

All the NEs discovered through "Device discovery and polling" function are displayed in
network topology; you can use the move function to move one NE or subnet to other subnet.
The function entrance and operations are shown as below.

Shortcut menu bar Edit > Move to Right click subnet or NE
Topology tool bar icon Select and click subnet or NE
Pop up the following dialog box, select to move to destination subnet, click Save to complete
the operation.
100
Raisecom
Figure 4-10 Moving subnets and NEs
Gateway NE needs to be moved together with NE subnet, i.e. you can only move
gateway NE subnet to change gateway NE located topology subnet.
4.10.5 Locking/Unlocking topology view

You can lock the current view to retain the current view layout. When the view is locked, you
cannot drag to modify the location of current view layout and subnet layout, but can select the
layout mode.
You can unlock the locked view by unlock function. The function entrance and operations to
lock/unlock view are shown as below.

Lock function entrance Unlock function entrance Operation
Topology menu bar Edit > Topology menu bar Edit > Click
Lock View Unlock View

Topology tool bar icon
101
Raisecom
When the topology view is locked and all NView NNM users login the client, the
topology view will be in lock status until unlock the view.
4.10.6 Locking/Unlocking the coordinates of topology object

You can lock the coordinates of topology object to retain the current location of subnet or NE.
When the coordinates are locked, it will show the lock icon and you cannot drag to change the
location.
You can unlock the locked coordinates by unlock function. The function entrance and
operations to lock/unlock coordinates are shown as below.

Lock function entrance Unlock function entrance Operation
Node right-click shortcut Node right-click shortcut Click in the
menu Lock Coordinates menu Unlock Coordinates shortcut menu
When the coordinates of one topology object are locked and all NView NNM users
login the client, the topology object will be in lock status until unlock the view.
4.10.7 Subnet expansion in the same layer

In the network topology, you can double-click to enter the subnet, so the other subnets or NE
in the same layer with this subnet will not be shown, which affects the entire effect. NView
NNM provides same layer subnet expansion function.
Through this function, subnet used border and the NE are shown in the current topology. The
expanded subnet can also be shrinked and recover to the original display interface. The
expand/shrink function entrance and operations are shown as below.

Expand function Shrink function Operation
entrance entrance
Shortcut menu Shortcut menu Shrink Right click subnet in
Expand topology.
Shortcut menu Shortcut menu Shrink Right click subnet in
Expand topology.
Gateway NE subnet expansion in the same layer is shown as below.
102
Raisecom
Only the subnet with NE supports the subnet expansion function in the same layer,
the empty subnet does not support this function.
4.10.8 Viewing related resources

View NE related resources, including:
 Chassis list
 Central office card list
 Remote device list
 Port list
The function entrance and operations to view NE related resources are shown as below:

Shortcut menu Related resources Right click NE in topology
Shortcut menu Related resources Right click NE in topology
Topology tool bar icon Click NE in topology
When selecting the view object of this NE, it will jump to Physical Inventory interface to
show the detailed information of this inventory.
4.10.9 Configuring display layout

You can configure the topology display layout in topology to open the alarm, properties,
graphic symbol panel.
Alarm panel
The alarm panel can show NView NNM current alarm in paging, 2000 pieces at most. Same
to the function of "Current alarm query", alarm panel supports alarm confirmation, clearance,
troubleshooting experience configuration, topology location and view alarm properties etc.
functions and can configure alarm and topology linkage, show the latest alarm and lock alarm
as well as support alarm sequencing.
In topology function menu, click System > Display > Bottom > Alarm to open/close alarm
panel. The alarm panel supports three function options:
103
Raisecom
 Selected linkage: click topology object in topology graph/tree to show topology object
alarm.
 Show the latest report:
─ Checked, the newly generated alarm record will be on the top of alarm panel.
─ Unchecked, the newly generated alarms will not be on the top of alarm list.
 Lock: Checked, the alarm list will be locked, and newly generated alarm will not enter
alarm list.
The topology tool bar provides alarm panel open/close shortcut buttons and you can
click in topology tool bar to open/close alarm panel.
Right-click an alarm record in alarm panel and select various configuration function of current
alarm in shortcut menu. The functions of these menus are the same to the functions in
"Current alarm query". See Chapter 7 Alarm event management.
The records in alarm panel support order function, including order in accordance with some
alarm property and order in accordance with multiple alarm properties.
 Order in accordance with some alarm property: click alarm list header to order alarm
records in ascending according to the list property; click again, order the alarm record in
descending; click another time, cancel the order.
 Order in accordance with multiple alarm properties: click one alarm list header to order,
press on Ctrl to click the other list header, it will show the order condition ID; the alarm
records will be ordered in accordance with multiple conditions. As shown below, click
"Alarm level" for twice, the alarm records will be ordered from emergency alarm to
prompt alarm according to alarm level; then press on Ctrl and click "the first time report
time" for twice, the alarm records will be ordered from new to old according to "the first
time report time" on the basis of ordering in accordance with alarm level.
 Custom order conditions: click the left top of alarm record to open custom table list
and custom order conditions dialog box.
─ Select alarm property to show in custom table list.
─ Custom to order in ascending/descending according to alarm property in custom
order conditions.
104
Raisecom
Figure 4-11 Ordering alarms according to multiple alarm properties
The upward triangle in table header indicates ascending order, downward triangle
indicates descending order. The numbers indicate the order of sort conditions, that is
to say, order in accordance with Condition 1 at first, and then order in accordance
with Condition 2.
Properties panel
The properties panel is used to display the properties information of topology object and the
information in the properties panel can only be viewed but not modified.
In topology function menu, click System > Display > Right > Properties or click
and select "Properties" to open or close properties panel. In topology graph or topology tree,
click to select topology object, it will show the properties information of topology object in
properties panel.
Graphic symbol panel

The graphic symbol panel contains all the graphic symbols of topology object.
In topology function menu, click System > Display > Right > Graphic Symbol, or click
and select "Graphic symbol" to open or close graphic symbol panel. In topology graph
or topology tree, click to select topology object, it will show the graphic symbol of topology
object in properties panel. The graphic symbol can be divided into the following categories.
 Status: show the subsidiary small icon of the topology node; the subsidiary small icon is
shown on the top of topology object to distinguish topology object status.
 Alarm: show emergency, major, minor, prompt and unknown alarm levels corresponding
colors.
 Device: show the graphic symbols of all devices in topology graph and topology tree;
click to select the device and at the same time select the graphic symbols corresponding
graphs.
 Subnet: show the graphic symbols of all subnets in topology graph and topology tree;
click to select the subnet and at the same time select the graphic symbols corresponding
graphs.
105
Raisecom
 Symbol: show the graphic symbols of all symbols in topology graph and topology tree;
click to select the symbol and at the same time select the graphic symbols corresponding
graphs.
 Link: show the graphic symbols of all links in topology graph; click to select the link and
at the same time select the graphic symbols corresponding graphs.
4.10.10 Configuring topology setting

In the menu bar at the top of topology graph, click System > Topology Set to pop up the
following dialog box, the parameters are shown as below.
Figure 4-12 Configuring topology setting

 Name
Node Select the node display name in
 Host name
display topology.
 IP address
name
Name Default value is 15, Configure the name display length
length the maximum value is below node.
255 The name will be shown in
multiple lines over this length.
 Checked: show link name
Show link Configure whether to show link
 Unchecked
name name.
 Name
Link Select link display name in
 Display name
display topology.
 Link name
name This option can be configured
when "Show link name" is in
"Checked" status.
 Checked
Show alarm Configure whether to show
 Unchecked emergency.
106
Raisecom

 Checked
Alarm Configure whether the emergency
 Unchecked
blinking alarm is flickering.
This option can be configured

when "Show alarm" is in
"Checked" status. And only the
emergency alarm is flickering
according to this configuration,
other levels of alarms are not in
support of the flickering.
4.10.11 Configuring link display aggregation

In the actual complex networking application, sometimes two devices need to connect a
number of links, which will be more chaos in topology graph. To show network topology
clearly to customers, NView NNM provides link aggregation function.
Select one link between two devices and double-click it, all links in these two devices will
aggregate to one and the aggregation symbol and number of aggregation links will be shown
on the link, as shown below.
107
Raisecom
Figure 4-13 Configuring link display aggregation
4.10.12 Device offline rate statistics

You can open the view interface by the following two modes to view the offline device
statistics in some subnet.
In system main menu, select Report > Offline Device Statistic to open device offline
statistics interface.
The tool bar will show the time to perform statistics operation, and the list will show the
offline statistics of selected subnet and the included each subnet. Select a subnet in the subnet
list of tool bar, click Statistic to perform statistics analysis operation.
The device offline rate statistics interface is shown as below. It will show the statistics result
after the statistics, "Offline rate" list uses different colors to show the range: 0%–50% green,
50%–80% orange, 80%–100% red. Click Graph in the tool bar to show statistics result in the
form of pie chart.
108
Raisecom
Figure 4-14 Device offline rate statistics
4.10.13 Common button in topology toll bar

To introduce topology operation, besides right-click shortcut menu, the topology interface
provides function menu and tool bar button. The configuration operation to right click
shortcut menu, function menu and tool bar button are the same; the common buttons in
topology tool bar is shown as below.
According to whether to select the record or whether to select multiple records, the
operation has some limits and the limited operation menu and button will be grey,
indicating unable to take the corresponding operations. For example, if not to select
records, you will not perform modify, query and other operations.
Table 4-20 Function entrance of common configuration operations

Configuration Right key shortcut Function menu Tool bar
operation menu button
Show properties Show Properties –
information.
Search topology Search System/Search
object.
Add topology Add Edit/Add
object.
Modify topology Edit/Edit Edit/Edit
object properties. Properties Properties
Delete topology Delete Edit/Delete
object.
109
Raisecom
4.10.14 Selecting multiple topology objects

In topology graph, to select multiple topology objects can delete or move topology object in
batch; you can select multiple topology objects in accordance with the following methods.
 Press and hold the left mouse button and drag to select multiple topology objects.
 Press Ctrl key and click to select multiple topology objects.
4.10.15 Configuring background picture

You can modify subnet corresponding topology view background according to the following
steps:
Step 1 Open the subnet corresponding topology view and right click the blank space of topology view
or the subnet icon on configuration background picture, and then click Set Background in the
shortcut menu to pop up modify dialog box, the configuration operation is shown as below.
Step 2 After setting, click Confirm to complete the operation and then the background of topology
view will change to the selected bd.
Step 3 (Optional) click Reset to restore the background picture to initial status.
110
Raisecom
Figure 4-15 Setting background picture
Table 4-21 Set background picture operation

Operation Description
Select subnet. Checked: need to set background picture subnet.
Set background. Click to select background picture, supporting
GIF, JPG, PNG and JPEG forms.
Set txture picture. Click to select watermark picture, supporting
GIF, JPG, PNG and JPEG forms.
Set background color. Click to select background color.
Gradient color Click to select gradient color. After checked, the
background color and gradient color will appear
gradient display effect.
Preview Preview background picture setting.
NView NNM provided default background picture is stored in the path:

\NMS\PLATFORM\NNM5\client\resource\symbols\background.
111
Raisecom
4.10.16 Common view operations

Enter into topology browser, double-click subnet node to show the subnet node corresponding
topology view in current browser. At the same time, topology browser provides view
navigation operation so that you can go forward or backward to browse these subnets.
To open topology browser, the tool bar on the top of topology browser will provide the
common buttons of navigation operation, as shown below.
Table 4-22 Common view operations

Button Name Description
Return to the Perform this operation and topology browser
toppest level will show toppest level subnet topology view.
subnet The operation is unavailable if the current
subnet is toppest level subnet.
Higher level Perform this operation and topology browser
subnet will show the higher level subnet topology view
of current subnet. The operation is unavailable
if the current subnet is toppest level subnet.
Retreat Perform this operation and topology browser
will show the last time browsed subnet
topology view.
Advance This operation is valid only performing
"Retreat" operation. Perform this operation and
topology browser will show the next subnet
topology view of current subnet in browse
records.
Refresh the Perform this operation, reload topology data
entire network and refresh to show topology structure.
topology
Default to Click this button and click mouse to select
select topology objectin topology view.
Move view Click this button and press on the mouse and
drag in topology view.
Delay to move Click this button and then click and press on the
left mouse button to drag subnet or NE in
topology view; you can select the location to
place at first and then release the left mouse
button.
Topology Click and support the following function
output menus:
 Topology output: support to export the entire
topology graph, select export area, only export the
area cover primitive, export topology graph
according to topology node location line and row.
 Print preview: show print preview
 Print: select printer and print topology graph.
112
Raisecom

Related Click and support the following resource
resource menus:
 Chassis list
 Centrol office card list
 Remote device list
 Port list
Full screen Click to show full screen topology view and

browse/Exit click again toexit the full screen browse.
full screen
Thumbnail Click to show topology thumbnail
4.10.17 Configuring view zoom

In topology browser, the system provides view zoom operation to amplify or shrink current
topology view for you to browse. Open topology browser, the operation methods can be
achieved through tool bar.
Viewing zoom button

Zoom operation button is located in the tool bar on top of topology browser, as shown below.
Table 4-23 Topology view zoom buttons

Zoom in Amplify topology object distance.
Zoom out Shrink topology object distance.
Zoom Select this button, click mouse and drag to select the
selection area to amplify distance in topology, the selected
area will be the displayed central position.
Click to exit area aoom status.
Magnifier Select this button and the mouse will change to
magnifier status in topology for easy to view.
Click to exit magnifier status.
Zoom Click and support the following zoom menus:
setting  Restore to original ratio: restore the default distance of
topology object.
 For window: show topology graph according to the size
of window.
To select "magnifier" function, right click to pop up shortcut menu and configure the display
shape and zoom scale of magnifier, as shown below.
113
Raisecom
Table 4-24 Magnifier display setting

Classification Value Description
 Ellipse
Shape Configure the display shape of magnifier.
 Round
 Rectangle
 Square
 Large
Zoom Configure the zoom scale of magnifier.
 Default
scale
 Small
Thumbnail
Click button in toolbar on top of topology browser to pop up "Thumbnail" window. In
"Thumbnail" window, you can click to drag the position of viewing frame to browse different
areas, as shown below.
Figure 4-16 Thumbnail

To select "Thumbnail" function, right click the thumbnail to pop up shortcut menu to
configure the displaying setting of thumbnail, as shown below.
Table 4-25 Thumbnail display setting

 Fill none side
Fill mode Configure thumbnail display fill pattern, i.e. configure the view
 Fill one side thumbnail display pattern in small window.
 Fill both side
For example: "Unilateral fill" is to show the entire view in small
window, other spare parts are shown in black.
114
Raisecom

 50 ms
Update Configure thumbnail update display time interval; the thumbnail
 500 ms
interval will update the display automatically in reaching the configured
 1000 ms
interval.
 Checked
View Configure whether to label the parts except the current topology
 Unchecked
mask view in gray.
 Checked
View Configure whether the current topology view in topology to display
 Unchecked
border border.
 Checked
Show title Configure whether to show thumbnail title.
 Unchecked
4.11 Configuring customized view

NView NNM system defaulted view name is "topology", in this view it shows the various
NEs, subnets, and the link relationship between them. If there are a large number of NEs or
subnets, and the link relationship is relatively complex, then the view will not be presented
clearly. At this point, you can define new view in the network management system. The
operations in customized view are the same to the operations in topology main view, and are
subject to your security access control.
Each user can create their own customized views, login with the appropriate user account and
only to view and manage their own created customized views. In NView NNM main menu,
click Topology > Custom View Management and pop up Custom View Management
interface. You can perform Add, Delete, Properties, Query, Modify and Refresh operations in
this interface.
4.11.1 Adding customized view

In Custom View Management interface, select Operator > Add in menu bar or in tool
bar, it will show "Add" properties box on the left side of the interface, as shown below. After
configuration, click Add to add customized view.
115
Raisecom
Figure 4-17 Adding customized view

Main view name Entire network view Select main view name.
View name Character string, the Enter view name.
maximum length is 50
View remark Character string, the Enter view description.
maximum length is 512
4.11.2 Adding topology objects in customized view

After creating customized view, you can add subnets, NEs and other topology objects in the
view. The Add, Delete and Adjust layout topology management operations in customized
view can only affect the customized view, but not affect topology main view; Except the
Delete operation, the topology management operations in main view will also not affect
customized view.
Step 1 In the topology main view, right-click the subnet or NE, click Add to Custom View in
shortcut menu to open customized view management interface.
116
Raisecom
Step 2 Click customized view record to add in customized view management interface, and then click
OK.
Step 3 After successful add, it will prompt "The operation is successful", click OK.
Step 4 Click the topology function menu System > Refresh the entire network topology to refresh
the topology in customized view.
There are the following characteristics to add customized view.

 To add subnet: only add the subnet itself, not add the topology objects in subnet.
 To add NE: not shown in accordance with the original subnet and NE topology
level. For example: add a subnet at first, and then add the NE in subnet, the NE
and subnet are shown in the same topology level in customized view.
4.11.3 Viewing customized view

Create customized view and add subnet and NE. And then open to view customized view.
Step 1 Click Topology > Custom View Management in NView NNM system menu to open the
customized view list.
Step 2 Right-click a customized record, click Open Custom View in shortcut menu to open
customized view interface. You can open to view multiple different customized interfaces.
Step 3 Click the topology function menu System > Refresh the entire network topology to refresh
the topology in customized view.
4.11.4 Modifying customized view properties

In Custom View Management interface, select a record and click Operator > Modify in
menu bar or click in toolbar, it will show "Modify" properties box on the left side of the
interface, as shown below.
117
Raisecom
The parameters description in Modify interface is the same to the parameters

description in Add operation interface.
4.11.5 Viewing customized view properties

In Custom View Management interface, select a record and click Operator > Property in
menu bar or click in toolbar, it will show "Properties" properties box on the left side of
the interface, as shown below.
118
Raisecom

ID – Show customized view ID, generated
by system automatically in creation.
Main view Character string, Show customized view name.
name the maximum
length is 50
View name – Show customized view name.
View – Show customized view description.
remark
User ID – Show user ID to add this customized
view.
119
Raisecom
4.11.6 Querying customized view
Query conditions
In Custom View Management interface, select Operator > Query in menu bar or click
in tool bar, it will show "Query" properties box on the left side of the interface, select
"Condition" label, as shown below.

ID – Select view ID query condition and
parameter value.
Main view – Select main view name query
name condition and parameter value.
View name – Select view name query condition
and parameter value.
View remark – Select view remark query
condition and parameter value.
 And
Condition Select condition matching
 Or
selection principle.
120
Raisecom
Click Query to take find operation.
Customizing query column

In the left "Query" properties box, select "Custom query column" label, the input keyword is
shown as below. Then click Apply to complete the customization.
Customizing order conditions

In the left "Query" properties box, select "Custom order conditions" label to query the records
order. You can click properties ascending/descending to reorder the records. Then click Apply
to complete the customization.
This function supports to configure multiple order conditions, and to take multiple ordering
according to the upper/lower sequence of conditions, i.e. order in accordance with the first
condition, and then order in accordance with the second condition to the same results in the
first ordering. Click to select the name of query condition, click or to adjust the
display order of query conditions.
121
Raisecom
4.12 Viewing topology list

4.12.1 Viewing subnet list
In the system main menu, select Topology > Subnet List to open the main view of topology
subnet list, as shown below. The interface will show all or part of subnet information in
network topology in the form of list. You can set the query condition to query, and take
topology locate, modify, delete and export list etc. management operations.
122
Raisecom
Figure 4-18 Topology subnet list
4.12.2 Viewing NE list

In the system main menu, select Topology > Node List to open the main view of topology
node list, as shown below. The interface will show all or part of device nodes and symbol
nodes information in network topology in the form of list. You can set the query condition to
query, and take topology locate, modify, delete and export list etc. management operations.
Figure 4-19 Topology node list
4.12.3 Viewing link list

In the system main menu, select Topology > Link List to open the main view of topology
link list, as shown below. The interface will show all links information in network topology in
123
Raisecom
the form of list. You can set the query condition to query, and take modify, delete and export
list etc. management operations.
Figure 4-20 Topological link list
124
Raisecom
NView NNM Operation Guide 5 Device discovery and polling
5 Device discovery and polling
This chapter introduces how to use NView NNM provided device discovery and polling
function and the common operations, including the following sections:
 Overview
 Functions and features
 Technical principle
 Basic conceptions
 Interface description
 Scenarios and operation steps
5.1 Overview
Device Scan and Poll function of NView NNM system is a sub-module in the five
configuration management of TMN network management functions (fault management,
configuration management, performance management, security and charge management).
Device Scan and Poll is based on SNMP protocol, adopting polling method to monitor device
and collect related information and data from network. It is in support of reporting Trap
information by device. Agent in device keeps on collecting data and record the data into MIB,
NView NNM system get the data via MIB and receive Trap reported from device for the
important device information, then it can ensure device under monitor status.
Device Scan is mainly used at the first stage of network building for carriers. It is used to
detect the manageable devices in assigned network segment or IP segment. You can quickly
add manageable device through this function to improve network building efficient. This
function is in support of execution in period for detecting new devices in assigned network
segment or IP segment.
Device Poll is mainly used in the normal operation period of NMS, to detect the managed
device is online or not, send offline alarm for the offline devices and notify network
administrator. Polling is a kind of asynchronous mechanism; the disadvantage is it cannot
confirm real-time information, especially real-time alarm. Trap cannot take the place of
polling since it will expend resource and influences on both itself and NMS. The setting of
polling period is very important: too small period leads big communication and affects
processing capacity of NMS; too big period may cause difficult in monitor important network
condition. Unreasonable polling period will affect the using of NMS and even monitor result
during operation.
125
Raisecom
NView NNM system hammers at providing powerful operation function to carrier. Device
Scan and Poll function aims to the features of build up device network management in
operation fast and customize polling period for monitor according to real situation, with the
purpose of improving monitor efficient and reduce operation cost: SNMP and other protocol
are in template for operating work in batch; Device Scan by task to realize periodical schedule
and operation; Device Poll in groups to convenient customized monitor operation works for
client; recording the result of Device Scan and Poll in details and generates log and report to
satisfy reliability of work.
5.2 Functions and features

As function modules of NView NNM system, Device Scan and Poll function provides below
function features:
 Device Scan
─ SNMP V1/V2c/V3 and ICMP protocol template function;
─ Adopting multiple protocol template for Device Scan;
─ Control Device Scan range according to device type, IPv4 address filter;
─ In support of adding the discovered device into subnet by automation according to
IPv4 address;
─ In support of automatic synchronize with new device type after discovering new
device;
─ Executing Device Scan function immediately or periodically;
─ Display scanning progress and details in real-time;
─ Device Scan task management function;
─ Device Scan scanning report function;
─ Device Scan result log in details.
 Device Poll
─ Polling in accordance with protocol template;
─ Dense polling in minimal granularity of 30 seconds;
─ Time slice polling every 5 minutes;
─ Device Poll in groups;
─ Calculate polling load by automation;
─ Detailed polling report.
5.3 Technical principle

The devices in network automatic discovered by NM system are usually communicating by
standard protocol, like SNMP, ICMP, etc. or private protocol. The result is depended on
protocol used by device. Different protocol in support will get different results.
NView NNM automatic discovery function is in support of scanning device by multiple
protocols via template protocol. It simplified the configuration process of automatic discover
protocol for network maintenance staff and guarantee the accuracy of Device Scan result
through scanned by multiple protocols.
126
Raisecom
SNMP (Simple Network Management Protocol) is based on UPD. SNMP has become an
international general standard. Device Poll and trap mechanism introduced in RFC1157 has
been widely used as SNMP realization method.
Complying with SNMP technic and combining with the actual condition in operation working,
NView NNM Device Poll function realizes polling in groups and time slice algorithm.
Polling in groups classifies devices by customize according to the attentions, the polling
groups perform Device Poll by system schedule. Two classes of polling groups: dense polling
with granularity of 30 seconds, which is used to poll key devices, but it will take lots of NM
system resources; the other class is polling group with granularity of 5 minutes, which adopts
time slice algorithm, available to common devices.
Time slice algorithm is to classify NE devices in polling group by time dimensionality. When
system launches polling, the NE devices in polling group do not start polling at the same time
but polling in accordance with time slice. The time slices are mutually independent in
microcosmic but forming as a whole in macrocosmic. This mechanism ensures the reliability
of Device Poll and meanwhile provides accordance for NView NNM system calculates the
actual polling load. Maintenance staff controls polling load by adjusting polling group
according to polling load. Then it accomplishes monitor on key devices and guarantee stable
and high-efficient of NMS.
5.4 Basic conceptions

 Device Scan: scanning the manageable devices in assigned IP segment;
 Device Poll: polling the devices in NView NNM system in period;
 Protocol template: the SNMP v1/v2c/v3 or ICMP protocol parameter template used for
scanning devices by Device Scan and Poll function;
 Scanning filter: do not scan the assigned IP address or device types;
 Scanning task: task of scanning assigned IP segment according to the parameters set in
protocol template, immediate execution or periodic execution;
 Scanning service setting: set the global parameters used by Device Scan, such as
scanning period, whether add the new discovered device into NM system;
 Scanning report: to display the scanning progress and device information;
 Log: record the related result in "System Event Management" and "System Operation
Log" for query;
 Polling configuration: start/stop NM system polling, distribute NE devices in different
polling period groups;
 Polling grouping: classify devices with identical polling period in groups;
 Polling report: to view device information and polling details of each polling groups;
 Polling load: the ratio of actual polling time and polling interval, displaying in graphic
interface according to polling groups;
 Offline devices: the ratio of offline devices and device total in polling group, displaying
in graphic interface according to polling groups.
127
Raisecom
5.5 Interface description

5.5.1 Startup interface
Click Topology > Device Scan and Poll to open interface of Device Scan and Poll. The left
of interface is function tree; the right of interface is related function interface of selected
function tree. By default, the interface displays protocol template interface, as figure shows
below. The function tree can be divided into two categories: device scan and device poll, each
has their own function items.
Figure 5-1 Main view of device scan and poll
5.5.2 Protocol template

The protocol used for Device Scan scanning is configured by protocol template.
After device detection and added into NMS, the NMS will record device detection protocol
and configuration parameters, and take the protocol and parameter to perform polling
operation.
The parameters configured by manual can help you add device by manual for
executing device adding and polling.
Click Device Scan > Protocol Template in function tree, the right side will open interface of
protocol template that display all configured protocol templates, as figure shows below. By
default, system provides SNMPv2c template that adopts SNMPv2c protocol. The template
can neither be deleted nor edited. You can add, edit and delete protocol template by the
buttons at bottom of interface or through right-key menu.
128
Raisecom
Figure 5-2 Protocol template
Adding protocol template

Click Add or select Add from right-key menu to add protocol template, as figure shows
below. After finish configuring protocol template, you click OK to finish adding; click
Cancel to cancel adding.
129
Raisecom
Figure 5-3 Protocol template configuration

By default, protocol configuration interface displays configuration interface of SNMPv2c.
Configuration interface of SNMPv1 is identical to this one. The configuration parameters in
the interface will display in protocol template list:
 Template name: compulsory, user defined the name of template.
 Discovery protocol: compulsory, choose protocol type for Device Scan. ICMP protocol
parameters cannot be configured if choose "SNMP Protocol"; SNMP Parameters cannot
be configured if choose "ICMP Protocol".
 SNMP protocol version: compulsory, choose SNMP version.
 SNMP parameters: SNMP parameter will display according to the selected version.
Interface of SNMPv1 and v2c shows in the above figure; interface of SNMPv3
parameters shows as in the following figure. The detailed parameters descriptions please
refer to SNMP V1/V2c protocol parameters and SNMP V3 protocol parameters.
130
Raisecom
Figure 5-4 SNMP V3 parameters

 ICMP parameters: compulsory when choose "ICMP Protocol" in "Discovery Protocol"
panel. ICMP parameters including: overtime (1-7 seconds), default is 3s; tautology times
(1-5), by default is 1.
ICMP protocol is usually used to detect and poll devices from other vendors.
Raisecom devices usually apply SNMP protocol for device detection and polling.
Editing protocol template

Click Edit or select Edit from right-key menu to open interface of "Protocol Configuration".
The interface is identical to the one open by clicking Add. After modifying template content,
click OK to finish modification; click Cancel to cancel modification.
131
Raisecom
Deleting protocol template

Choose aprotocol template from protocol template interface, click Delete or select Delete
from right-key menu to open prompt dialog box, as figure shows below. Click Yes to delete
user configured protocol template, click No to cancel deletion.
Figure 5-5 Deleting protocol template
5.5.3 Scan filter

Scanning filter is used when Device Scan executes scanning; the IP address or device types do
not need to scan will not be scanned. You can configure scanning filter according to IP
address and device types and then reduce scanning range and improve scanning efficiency.
Click Device Scan > Scan Filter in the function tree to open scanning filter interface on the
right side. The interface display all configured filter conditions according to device type filter
and IPv4 filter list, as shown in the following figure. You can add and delete filter condition
by the right-key menu or buttons at the bottom.
132
Raisecom
Figure 5-6 Scan filter view
Adding scan filter based on device type

Click Add or select Add from right-key menu to open interface of Filtration Device Type, as
figure shows below. The interface shows device type and device model in the form of tree,
click to select check boxes to select the device type and device model to filter. After selecting
the device type to filter, click OK to complete the operation and click Cancel to cancel the
operation.
133
Raisecom
Figure 5-7 Adding scan filter based on device type
Deleting scan filter based on device type

After selecting a device type to filter, click Delete or select Delete from the right-key menu to
open prompt dialog box, as figure shows below. Click Yes to delete and click No not to delete.
Adding scan filter based on IP address

Click Add or select Add from right-key menu to open interface of Filtration IP, as figure
shows below. The interface is used to add IPv4. Fill in filter IP address and click OK to
complete the operation and click Cancel to cancel operation.
134
Raisecom
Figure 5-8 Adding scan filter based on IP address
Deleting scan filter based on IP address

After selecting an IP address to filter, click Delete or select Delete from the right-key menu to
open prompt dialog box, as figure shows below. Click Yes to delete and click No not to delete.
5.5.4 Scan task

Scan Task is in support of periodically execution and immediate execution. By setting
scanning range and enable/disable the scanning range to confirm range of Device Scan; by
setting scanning service to perform periodically or immediate scanning and in support of
adding the discovered device into NView NNM system. More than one scanning range can be
configured, then you can decide the whole scanning range by enable Scan Task, namely "Scan
Task" will scan all of the enabled "Scan Range".
Figure 5-9 Scan task view

 Click Add or select Add from the right-key menu to open interface of Scan Range
Config. The interface is used to add IPv4 address range:
135
Raisecom
Figure 5-10 IPv4 scan range configuration
The IPv4 "Subnet Range" in scan range supports auto-calculate subnet mask
according to input "IP Address" by default.
Scan range configuration has following parameters:
 Scan Range: compulsory, to select IP programming way for scanning range and filling IP
range or subnet range or single IP. Scanning range supports up to 65 000 IP.
 IP Count: system automatically calculates in accordance with scanning range.
 Enable status: compulsory, enable by default, indicating the scanning range is enabled
when starting scanning service; the scanning range will not be used if choose disable
here.
 Specified Subnet: compulsory, the subnet when device is added into network topology
after discovered device, choosing Network Topology by default.
 Protocol Template: compulsory, click the button to open "Protocol Template"
interface for adding protocol template. The interface shows as below. The upper side of
interface display the optional protocol templates list, the down side of interface displays
the selected protocol templates list. By default, SNMPv2c template is selected. You can
click Add or Move Out to configure protocol template needed. Then click OK to finish
configuration.
136
Raisecom
Figure 5-11 Scan task_Selecting protocol templates

After configuring scanning range, click OK to finish add and click Cancel to cancel adding
operation. You can click Move Up or Move Down to adjust order of protocol template, and
system follows template order to scan when detecting device.
 Click Edit or select Edit from the right-key menu to open interface of "Scanning Range
Configuration". The interface is identical to the one open by clicking Add. You modify
the scanning range and then clicks OK to finish modification or click Cancel to cancel
modification.
 Select a scanning task from the interface and click Delete or select Delete from the right-
key menu to open prompt dialog box, as figure shows below. Click Yes to delete user
configured protocol template or click No to cancel deletion.
 Scanning service setting at the down side of scanning task interface supports starting
periodically or immediate execution of enabled scanning task, as figure shows below.
Click Edit in scanning service setting panel to modify periodically enable task by user
defined; click Save to save setting after modification or click Scan to start execution of
scanning task.
Figure 5-12 Scan service setting

Detailed configuration of the interface:
 Scanning device IP total: system automatically calculated in accordance with all of the
enabled scanning range.
137
Raisecom
 Manage on discovered device: enable by default, adding the discovered device into
NView NNM system. If disable this item, the discovered device will just be recorded in
scanning result.
 Number of concurrent (1-10): it is 5 by default, and up to 10. The number of scanning
process will be started when performing device detection scanning. The bigger the
concurrent number is, the more resources of PC were occupied.
 Cycle: you can set period for periodically scanning task by "Daily", "Weekly" and
"Monthly".
 Date: set detailed date in period.
 Time: set starting time of scanning task.
 Status: set periodically executing scanning task enable/disable.
A prompt dialog box as figure shows below will open when starting scanning.
Figure 5-13 Processing the scan task
5.5.5 Scan report

Scanning report displays the detailed information and scanning progress of scanning task, and
display the result in "Report Details", as figure shows below. The report details is in support
of filter displaying according to "Result Status" and also supports taxis by clicking fields
name of report details.
138
Raisecom
Figure 5-14 Scan report

In polling report interface, the upper side is "Scan Result" and the down side is "Report
Details".
Scan result
Scan result displays the total number of scanned IP, the number of scanned IP, the begin time
and the end time after finish scanning. Meanwhile, the result displays the scanning progress
by a progress bar. Click the button Stop to stop current scanning task; click Scan to start
configured scanning task.
Report details
The report details interface displays scanning result in list. Click the check box, the report
details supports filtering according to four kinds of "Result Status": "New Discovery",
"TimeOut", "Filtration Device" and "Network Exists". Cancel the selection of check box, and
the corresponding result status will not be displayed in report details.
The four result status of report details:
 New Discovery: the device is discovered by scanning procedure for the first time.
 TimeOut: device scan overtime.
 Filtration Device: the device belongs to "Scan Filter".
 Network Exists: the device is managed by NView NNM system.
Fields of list in report details:
 Network Management: tick it off means direct adding the discovered device into NView
NNM system; no tick it off means the device has not been added into NView NNM
system.
 IP address: display device IP address.
 Scan Status: result of device scan.
139
Raisecom
 Scan Protocol: the device is discovered by this protocol.

 Protocol Version: display protocol version.
 Device Name: display device name.
 Device Type: display device type.
 Start time: display the starting time of device performing scanning task.
If you did not tick off "Manage on discovered device" in scanning task configuration, when
there is new device discovered by scanning, you has to tick of "Network Management" check
box if wants to add the new device into NView NNM system. Then click the button Add To
Network or select Add To Network from the right-key menu, as shown in the following
figure. System pops up a dialog box to prompt Adding device to NMS successfully, then click
OK.
Figure 5-15 Manually adding the device to the NView NNM

The Search in report details interface supports customized query conditions after finishing
scanning. Click the button to open customized query interface, as figure shows below:
140
Raisecom
Figure 5-16 Customizing query conditions
5.5.6 Device poll

Device poll is to classify NE devices in groups according to the polling interval. Polling of the
different groups: set by "Polling Configuration"; display polling result by "Polling Report";
analyze and configure polling group load by "Polling Load".
5.5.7 Polling configuration

Polling configuration is in support of configuring running status of polling groups and devices
in groups. Click Device Poll > Poll Config > 30 Minutes in function tree, the right side will
open polling group configuration interface with polling interval of 30 minutes. The interface
displays all devices in the polling group, as figure shows below. Device list of polling
configuration groups is in supports of filter the displayed polling device list by customized
query conditions, supporting export polling report to Excel file by selecting Export (Excel)
from the right-key menu.
Configuring running status of polling in any group will affect the polling status of whole
NView NNM system. Polling configuration is in support of configuring NView NNM system
polling status by click buttons of Start or Stop.
141
Raisecom
Figure 5-17 Poll configuration
The devices added by auto-discovery belongs to "30 Minutes" group by default,

polling status is "Running" by default.
You can adjust Device Poll groups in polling configuration interface. Different polling groups
have different polling period.
 Right-click a device record to open a right-key menu, as figure shows below:
142
Raisecom
Figure 5-18 Poll configuration_adjusting device poll groups

 Choose related polling group according to the device needs polling interval. Click the
group name in the shortcut menu to adjust device to corresponding polling group.
Devices in group of "No Polling" will not perform polling, but NMS still receive trap
from devices in this group.
5.5.8 Polling report

Polling report list displays the Device Poll condition in different polling groups. Click Device
Poll > Poll Report > 30 Minutes in the function tree, the right side will open a polling report
interface with polling interval of 30 minutes. The interface displays all devices polling
condition belong to this polling group, as figure shows below. The polling report can be
exported to Excel file by selecting Export (Excel) from the right-key menu.
143
Raisecom
Figure 5-19 Poll report_30 minutes
5.5.9 Polling load

Polling load performs polling load analysis for 30s, 60s and 5 minutes commonly used polling
groups after NView NMM system starts polling. Generally speaking, polling interval over 5
minutes will not affect the NMS. Adjusting the device from big polling load group to big
polling cycle group and effectively lower the polling load. Click Device Poll > Poll Load > 5
Minutes in the function tree, the right side open a polling load interface with interval of 5
minutes. The interface provides Poll Load Meter Panel and Dynamic Graph of Device
Offline Rate to show polling load condition, as figure shows below:
144
Raisecom
Figure 5-20 Poll load
By adopting Time slice algorithm, poll load in 5 minutes display all loads polled by
device in the 5 minutes but not only polling the devices in a 5 minute polling group. If
poll load in 5 minutes is too big, you can adjust the 5 minute polling group to group of
bigger polling period and reduce poll load.
Poll load meter panel

The Poll load meter panel displays condition of polling load:
 0%–80% of the panel is green, indicating the polling device number in this group is
proper; polling load is "light load".
 80%–100% of the panel is yellow, indicating the polling device number in this group is
nearly saturation; polling load is "heavy load". NView NNM system generates "Heavy
load alarm", the alarm level is "Prompt".
 100%–120% of the panel is red, indicating the polling device number in this group is not
proper; polling load is "overload". NView NNM system generates "Overload alarm", the
alarm level is "Critical".
When device poll is over load, it still performs poll to all devices, but the start time of
next poll will be delayed, namely the polling interval becomes larger. You can confirm
detailed polling cost time of polling group through actual polling time recorded in
polling report and then adjust poll group.
Detail of poll load

The detail of poll load displays details of current group:
 Start: Start Device Poll or not.
145
Raisecom
 Poll Cycle: polling period of the group.

 The last begin of polling time: the starting time of system performs last scheduling on
this group.
 The last end of polling time: the ending time of system performs last scheduling on this
group.
 The actual begin time of last polling: the starting time of system performs polling on this
group.
 The actual end time of last polling: the ending time of system performs polling on this
group.
 The cost time of last polling: the time cost by last polling, unit in second.
 The load of device last polling: load ratio of last time group polling
 The begin time of next polling: the starting time of system performs next time schedule
on this group.
 Description: description of details.
Dynamic graph of device offline rate

Dynamic graph of device offline rate displays device offline ratio in polling group:
 Green: device online rate
 Red: device offline rate
Detail of device offline

The detail of device offline rate displays details of current group:
 Device number of last polling: the device total in this group at last polling.
 Online devices of last polling: the online device number in this group at last polling.
 Offline devices of last polling: the offline device number in this group at last polling.
 Offline ratio of last polling: the device offline ratio in this group at last polling.
5.6 Scenarios and operation steps

This chapter introduces the operation steps of Device Scan and Poll function. Please read this
chapter before operating Device Scan and Poll function modules.
5.6.1 Restriction conditions

Confirm the following restriction conditions before using Device Scan and Poll function:
 NView NNM system is in order;
 Subnet configuration is correct;
 Configuration parameters of Device Scan and Poll are correct, see section 5.6.3 Device
scan and section 5.6.4 Device poll for detailed configuration operation steps;
 "Device Offline detection Service" in system service is enabled.
146
Raisecom
5.6.2 Starting/Stopping device scan and poll function
Starting scan and poll function

 Two methods for starting Device Scan task; please refer to related section for configuring
Device Scan task operation steps.
─ Start immediate scanning: click Topology > Device Scan and Poll and then click
Device Scan > Scan Task on the left Device Scan and Poll function tree; then click
Scan button on the right interface of Scan Service Setting to Start Device Scan;
─ Start period scanning: period scanning task is automatic scheduled by system; see
section 5.6.3 Device scan for detailed operation steps of configuring period scanning.
 By default, Device Poll function is enabled. If it was disabled, you can click the button
Start at each group interface of polling configuration to start it again. See section5.6.3
Device scan for detailed operation steps of configuring period scanning.
Stopping scan and poll function

Stop Device Scan: after executing immediate scanning or periodically scanning, the scanning
progress and report details will display in Device Scan > Scan Report of the function tree,
click Stop to stop Device Scan.
Stop Device Poll will stop the polling function of the whole NView NNM system, you can
click the button Stop in each group interface of polling configuration to realize this operation.
If a certain NE does not need perform polling, please add it to "no polling" group instead of
stop Device Poll. See 5.6.4 Device poll for detailed operation steps of configuring Device Poll.
5.6.3 Device scan

Device Scan is mainly used at the first stage of network building for carriers. It is used to
detect the manageable devices in assigned network segment or IP segment. You can quickly
add manageable device through this function to improve network building efficient. This
function is in support of execution in period for detecting new devices in assigned network
segment or IP segment.
Preparing for device scan

Check if the system is performing scanning in "Scan Report" before executing "Immediate
Scanning". Wait the current scanning stop or click Stop to stop current task if there is
scanning task being executed.
147
Raisecom
Flow chart for device scan
Figure 5-21 Flow Chart of Device Scan
Configuring protocol template

Step 1 Click Topology > Device Scan and Poll to open interface of Device Scan and Poll;
Step 2 Click Device Scan > Protocol Template in the Device Scan and Poll function tree on the left
to open protocol template interface;
Step 3 Click Add to open dialog box of Protocol Configuration;
Step 4 The following parameters need to be configured in protocol configuration dialog box:
 Template name: like SNMPv1 template;
 Discovery protocol: SNMP or ICMP protocol for optional;
 SNMP protocol version: in support of SNMP V1/V2c/V3 versions, the dialog box will
display related protocol parameters after selecting SNMP version;
 SNMP V1/V2c protocol parameters including: port, overtime (second), tautology (times),
read community, write community, as parameters shows in table below;
148
Raisecom
Table 5-1 SNMP V1/V2c protocol parameters

SNMP Description Range Example
V1/V2c
parameters
Port Device SNMP port ID N/A 161
Overtime Time of overtime for Device Scan 1–8s 3
(second)
Retry Times of retry for Device Scan 1–5 1
(times)
Read Agent performs read authorization for N/A public
community NMS
Write Agent performs write authorization for N/A private
community NMS
 SNMP V3 protocol parameters including: port, overtime (second), retry (times),

username, security level, authorization protocol, protocol password, protocol password
confirmation, Privacy password, Privacy password confirmation, shown as table below;
Table 5-2 SNMP V3 protocol parameters

SNMP V3 Description Range Example
parameters
Port Device SNMP port ID N/A 161
Overtime Time of overtime for 1-8s 3
(second) Device Scan
Retry Times of retry for Device 1-5 1
(times) Scan.
Username Submit username for Agent N/A N/A
authorization.
Security Transmit/receive security noAuthNoPriv, authPriv
level level of SNMP message authNoPriv
authorization password and authPriv
encryption and message
content encryption.
Authority Authorize encryption MD5, SHA MD5
protocol protocol for authorizing
password.
Authority Authority password N/A N/A
password
Ppassword Confirm authorization N/A N/A
confirm password.
149
Raisecom
SNMP V3 Description Range Example

parameters
Privacy Protocol for encrypting DES, AES DES
protocol SNMP message contents
Privacy Password for encrypting N/A N/A
password SNMP message contents
Password Confirm password for N/A N/A
confirm encrypting SNMP message
contents.
 ICMP parameters including:

─ Overtime (1–7 seconds), 3s by default;
─ Retry (1–5 times), once by default;
 Click button OK to finish protocol configuration.
Step 5 Choose a protocol template from protocol template list and click Edit to edit scanning range,
click Delete to delete the selected protocol template.
Configuring scanning filter

Step 1 Click Topology > Device Scan and Poll to open Device Scan and Poll interface;
Step 2 Click Device Scan > Scan Filter in the Device Scan and Poll function tree on the left to open
scanning filter interface;
Step 3 Click Add to open dialog box of Filtration Device Type;
Step 4 Select the check box of device type and models from device type tree in Filtration Device
Type dialog box, and click OK;
Step 5 Click Add in Filter IP Address box to open dialog box of Filter IP Setting;
Step 6 Filling IP address to filter in IP address text box in "Filter IP Setting" dialog box and click OK.
Configuring scanning task

Two methods for scanning task: immediate scanning and periodically scanning. After
configuring scanning task, immediate scanning task only executes once. System will execute
scanning in period if configuring periodically scanning task.
Step 2 Click Device Scan > Scan Task in the Device Scan and Poll function tree on the left to open
scanning task interface; it is in support of configure scanning task and scanning service setting;
Step 3 Click Add to add scanning range, the range supports configuration parameters as below.
 Scanning range: supporting IPv4, setting in accordance with IP range, subnet range,
single IP address, shown as table below;
150
Raisecom
Table 5-3 Parameters description for scanning range IPv4

IPv4 Description Range Example
parameters
Range IP IP address segment Comply to 192.168.1.1
range RFC791. 192.168.1.254
Subnet IP IP address and mask, Comply to 192.168.1.0
mask can be calculated RFC791. 255.255.255.0
by automation
Single IP IP address Comply to 192.168.1.1
RFC791.
 Scanning IP number: in support of calculating IP number in the scanning range by

automation;
 Startup status: single selection, in support of enable/disable the scanning range;
 Appoint subnet: click button to select current subnet, in support of adding

discovered device into assigned subnet;
 Using protocol: click button to open dialog box of "Select Protocol", it is in
support of "Add" or "Remove" protocol template. That is to say, it is in support of using
multiple protocol templates to scan when executing Device Scan. Click OK to finish
protocol selection;
 Click OK in "Range Configuration" dialog box to finish configuration of a scanning
range.
Step 4 Choose a scanning range from the range list and click Edit to edit the scanning range, click
Delete to delete the selected range; Scanning service setting supports the below configuration
parameters:
 Scanning IP total: in support of calculate IP total in scanning range by system;
 Manage on discovered device: single selection, in support of management on discovered
device;
 Concurrent number (1-10): 5 by default, configure concurrent executing progress
number according to actual condition;
 Period: in support of scanning by day, by week or by month;
 Date: date in assigned period;
 Time: in support of assigning scanning execution time;
 Management status: enable/disable scanning service.
Step 5 Click Save to save current configuration;
Step 6 Click Scan to start immediate scanning;
Step 7 Click Device Scan > Scan Report in the Device Scan and Poll function tree on the left to
open scanning result interface; the interface supports displaying current scanning graphic
progress and you can also view information of current scanning: scanning IP total, scanned IP
number, start time, as well as end time after finish scanning.
151
Raisecom
The periodically scanning and immediate scanning of Device Scan scanning task are
mutually restricted. When performing periodically scanning, Immediate Scanning
button is unavailable; when performing immediate scanning, periodically scanning
scheduler will cancel current periodically scanning and wait for the next period
schedule.
Viewing scanning result

Scanning result is in support of viewing scanning information, graphic scanning progress and
report details. The report details support displaying list according to "Result Status" and report
details can be exported in Excel file. In "Scanning Result" interface, it is in support of stop
current scanning task and starts the configured scanning task.
Step 2 Click Device Scan > Scan Report in the Device Scan and Poll function tree on the left to
open scanning result interface;
Step 3 The top of interface shows current scanning information and scanning progress, the bottom is
report details;
Step 4 Report details is in support of single selection and multi-selection, displaying by classes of
New, Overtime, Filtration Device. Existed in NMS;
Step 5 Report details list is in support of taxis by click field name, and can export to Excel file by
clicking button Export (Excel).
Confirmation of discovering device

The scanning task can be confirmed by viewing scanning result. Start and stop of Device Poll
scanning are recorded in "System Event Management" log of NView NNM system at the
same time.
5.6.4 Device poll

Device Poll is to classify NE devices in groups according to polling interval. For the polling
of each group: set by "Polling Configuration"; display polling result by "Polling Report";
analyze and configure polling group load by "Polling Load".
Preparing for device poll

You have to make sure the NE devices are assigned to polling groups and the running status of
Device Poll is "Started". You can view running status through "Running Status" in polling
grouping interface. Polling configuration is in support of configuring NView NNM system
polling status by clicking Start or Stop button.
152
Raisecom
Flow chart for device poll
Figure 5-22 Flow Chart of Device Poll
Configuring device poll

Device Poll realizes different polling period by groups:
153
Raisecom
Step 1 Click the groups of Device Poll > Poll Config in Device Scan and Poll function tree, the right
side will display polling configuration related to groups;
Step 2 "Running Status" can configure NView NNM system starts/stops polling, click Start button to
start polling and click Stop to stop polling;
Step 3 Polling device list can display the devices in current group, all of these devices should use the
polling period of this group;
Step 4 Right-click a device in the list, a shortcut menu will display Device Poll groups. Select a group
from the shortcut menu to remove the device into selected group.
Step 5 Press down Ctrl and click to choose devices in different list, right-click the selected device,
the shortcut menu will display device poll group. Click the shortcut menu and choose a group
to batch transfer multiple devices to the selected group.
Viewing polling report

Click the groups of Device Scan > Poll Report in Device Scan and Poll function tree; the
right side will display corresponding polling report of the groups. The interface list shows all
Device Poll condition and detailed information of the polling groups.
Adjusting polling group according to polling load

For the polling group of 30 seconds, 60 seconds and 5 minutes, you can adjust according to
poll load. Usually, to adjust device from high load polling group to bigger polling period
group can reduce polling load. Click the groups of Device Poll > Poll Load in Device Scan
and Poll function tree; the right side will display corresponding polling load of the groups.
The interface list shows all devices polling load condition by "Polling Load Meter panel" and
"Dynamic Device Offline Ratio". You can judge if the polling device number in group is
reasonable by viewing details information of polling load.
Following the below procedure to adjust polling groups in accordance with polling load:
Adjust polling group procedure according to polling load as figure shows below:
154
Raisecom
Figure 5-23 Adjusting Polling Group According to Polling Load

"Last Polling Load" is the ratio of actual polling time and polling interval. Polling load over
high indicates the polling time over period interval of grouping polling, the actual polling time
for NMS perform polling devices in group is too long.
You need to view "Dynamic Device Offline Ratio" graph:
 If the offline ratio in dynamic graph is very low, the grouping polling load is too big, you
need to reduce NE devices in the group and adjust NE devices to the groups with lower
polling load.
 If the offline ratio in dynamic graph is very high, since Device Poll follows rule of
"overtime" and then "tautology" when NE device is offline, the load of polling group
will increase. You have to check offline device and remove the devices (unused devices)
not need to polling to other group.
155
Raisecom
Adjusting polling group according to polling time

Polling time denotes the time for device polling group perform one time of polling operation.
Too much polling time leads the device polling period longer and cause device monitor in low
real-time performance. After you adjust groups in accordance with polling load, you can
adjust polling group according to polling time to meet your polling requirements.
The procedure of this adjustment is similar with adjustment according to polling load, please
following the steps below:
Step 1 Click Device Poll > Poll Report in functional tree and select polling report of a group.
Step 2 View "Poll Time" in details, if the time is bigger than group polling period, the actual polling
time is too long when NMS polling devices in the group.
Step 3 View offline devices in polling report, if there is few offline devices in a group, the polling
load of group is too big, please reduce NE in this group and distribute the devices to group of
bigger polling period.
Step 4 If there are many offline devices in a group, the polling group time becomes long since the
offline of NE devices follows rule of "Overtime" and the "Try again". You need to detect
offline devices and move out the devices that do not perform poll (the device not being used
for example) according to practical condition.
Confirmation of device poll

When Device Poll is enabled, the polling information of NE device can be confirmed by
checking report and load of each polling group.
156
Raisecom
NView NNM Operation Guide 6 Device configuration management
6 Device configuration
management
This chapter introduces how to manage devices using NView NNM configuration
management function, including the following sections:
 Overview
 Commonly-used management tools
 Configuration management using NE management module
 Device batch configuration
 Batch executing commands script
 OLP route module
 Device Syslog management
6.1 Overview
NView NNM system realizes full device configuration management on the basis of NView
series NE management components. It can not only manage all Raisecom self-developed
devices concentratively, but monitor and manage commonly-used switches through general
device management module.
The system has a commonly-used tool collection for operations on devices. You can use tools
in this collection to configure and monitor the device. For example, the performance
management component demonstrates device CPU performance (second performance and
minute performance) in graph, interface performance (RFC-1213, interfaces group data) and
SNMP performance (RFC-1213, SNMP group data).
To satisfy the carriers' demand of upgrading and backing up network device system files or
configuration files timely, to avoid the loss of device configuration information, to improve
the efficiency of batch operation on a great number of devices, NView NNM system provides
a device upgrade/backup management component to complete batch upgrading and backing
up of device core files and configuration files.
To improve the efficiency of configuring a great number of devices at one time, NView NNM
system platform provides a device batch-configuration function.
157
Raisecom
To help carriers monitor the network device operating status, the system provides a device
Syslog log management component. It receives and displays standard Syslog information
reported by devices. Search and export function are available to help you manage Syslog.
Please refer to NView NNM User Manual-Performance Management for deployment

and using method of performance management component.
6.2 Commonly-used management tools

NView NNM provides MIB browser, Telnet and Ping tools that convenient user monitor
device MIB and know device status.
6.2.1 MIB browser

For devices that support SNMP management, system provides MIB browser to perform
standard MIB (RFC-1213) operations including browsing, configuring, and etc.
Right-click a node and then click Tool > MIB Browser > RFC-1213 > System Group. And
then a dialog box is displayed, as shown in Figure 6-1.
You can browse SNMP MIB information, including system information and protocol
information. In addition, you can modify the sysContact, sysName, and sysLocation
information of the MIB.
Figure 6-1 MIB management tools

Click an item on the sub menu, the corresponding configuration dialog box will appear, in
which you can perform browsing and configuring operations. Browse RFC1213 enables you
to view system information of monitored device, protocol information, etc. standard SNMP
MIB information; RMON (Remote Network Monitoring) is a complementarity and extension
of SNMP MIB, browse RMON supports statistic data and performance specification, etc.
information of monitored device MIB.
158
Raisecom
6.2.2 Telnet tools

System provides standard Telnet tools to enable you to manage devices in Telnet manner. You
can select some device node in topology browser, right click the mouse to pop up set up
Tools > Telnet menu and pop up command line window, as shown below.
When the client side is connected with server side, Telnet tools will not be restricted by the
network firewall between client side and server side and the client side can take Telnet
management to device even if it is not in the same network with the device.
Figure 6-2 Telnet tools
6.2.3 3Ping Tools collection
ICMP Ping
The system provides standard ICMP Ping tools. Click Tools > ICMP Ping on the system
main menu, or select a device node on the topology view, right-click on the node icon and
click Tools > ICMP Ping on the shortcut menu, a dialog box is displayed, as shown in the
following figure.
Figure 6-3 ICMP Ping tool

Enter the IP address of the target host in the IP address bar on the top of the dialog box, and
click the button at the bottom to execute ICMP Ping operation. The result of the
operation will be shown below.
159
Raisecom
That who actually executes Ping operation is the server. In distributed installation
environment, the client only launches the operation and browses the result. Server
executes the operation and the result of the operation is the communication status
between the server and the target host.
If you need to launch Ping operation to NE from the client host, right-click the NE icon
in topology and click Tools > Native Ping in the shortcut menu.
SNMP Ping
SNMP Ping tools check whether the SNMP service of the device under management is
operating in order, or whether the SNMP parameters of the device management is valid or not.
Click Tools > SNMP Ping on the system main menu, or select a device node on the topology
view, right-click on the node icon and click Tools > SNMP Ping on the shortcut menu, a
dialog box is displayed, as shown in the following figure.
Figure 6-4 SNMP Ping tools

Enter the SNMP parameters of the target host in the parameter setting area on the top of the
dialog box, and click the button at the bottom to execute ICMP Ping operation. The
result of the operation will be shown beneath the parameter setting area. That who actually
executes SNMP Ping operation is the server. In distributed installation environment, the client
only launches the operation and browses the result. Server executes the operation and the
result of the operation is the SNMP communication status between the server and the target
host.
SNMP Ping also supports SNMP V3. Choose "SNMP V3" from the drop-down box of
SNMP version selection, the related options of SNMP V3 becomes available. Click
the button after you set SNMP V3 to perform SNMP Ping operation.
160
Raisecom
6.3 Configuration management using NE management

module
6.3.1 Prerequisites of using NE management module
To ensure configuration management for device being performed by NE management module,
the prerequisites listed below should be satisfied:
 NView NNM installation program has integrated EMS, you please make sure get correct
license for EMS. (Corresponding EMS module license information will be listed in
system "License" dialog box.)
 You should install element management component of the type of devices correctly into
the NView NNM platform in advance. The version of the element management
component should be compatible to that of the NView NNM system. (All installed
network EMS modules and their versions will be listed in the system "About" dialog
box.)
 After you get License and installed EMS, the system possesses configuration
management function for a type of devices.
Create device node of this type in the system, and make sure that the SNMP parameters of the
device node is consistent with the actual setting. You can create device node in the following
modes.
 Create device manually in network topology management
 Find device automatically in network topology management
6.3.2 Launching NE management module in the topology

Select a device node on the topology view, right-click on the node icon and click the menu
item NE Management to launch the EMS, or double-click the device node on the topology
view or on the topology list to launch the EMS, an interface as is displayed. Configuration
management could be operated in this interface:
161
Raisecom
Figure 6-5 Chassis view
For different model of devices, the system provides different EMS interfaces. For
instructions of operations of NE, please refer to the instructions in the user manual for
the corresponding EMS.
Please note that for chassis that can form multiple-chassis device (e.g. RC002,
RC006), double-click the chassis node in topology to open up the panel of the
corresponding chassis. For single-chassis devices (e.g. OPCOM3500E, switches,
and etc.), double-clicking the device will open up the EMS interface of the device
directly.
6.3.3 Viewing card status in the card list

Click Inventory > Physical on the system main menu to open stock management interface,
click Card or Remote Device to open card list. The card list is in support of searching card
record. Select the record of a card in the card list, right-click on the selected row and click
Card View on the shortcut menu, or click on the toolbar, a dialog box will appear and
configuration management for the selected card can be operated.
162
Raisecom
Figure 6-6 Card configuration

For different models of cards, the system provides different card configuration interface. For
instructions for card configuration operations, please refer to the user manual for the
corresponding EMS.
6.3.4 Viewing card status in topology view

Select a card node in the topology view, right-click on the node and click Card View on the
shortcut menu, a card configuration dialog box will turn up. Configuration management
operations can be conducted in the dialog box, as shown in the above figure. For instructions
for card configuration operations, please refer to the user manual for the corresponding EMS.
6.3.5 Managing devices from other vendors using general device

management module
Auto-discovery process will discover devices that are not produced by Raisecom according to
their device type definition. Even unregistered devices will be detected as long as they support
SNMP management, and will be recognized as "SNMP Device" and added to the topology.
For these devices, there is no customized element management module. NView NNM system
provides a "General Device Management Module" for them.
Select a switch node of a vendor in the topology view, right-click on the node icon and click
NE Management on the shortcut menu, or double-click the device node icon, a device view
interface will be launched. You can view real-time port status, execute operations based on
standard MIB (RFC-1213, RMON), and receive seven kinds of standard alarms (Link Down,
Link Up, Cold Boot, Warm Boot, SNMP authenticating failure, EgpNeighborLoss, Enterprise
Specific) from the device.
163
Raisecom
Figure 6-7 General switch element manager
6.3.6 Configuring component by EMS

NView NNM V5.3 system integrates abundant types of EMS that imbeds its common
functions as components into EMS Config menu of NView NNM system. The EMS Config
menu also provides components of Batch Execute Command-line Script and OLP Route
module.
6.4 Device batch configuration

For a network with a huge number of devices, even simple configuration operation like the
modification of SNMP parameters and Trap target address may become a complicated task.
This is always a headache of access network administrators. NView NNM system solves the
problem with a device batch configuration function. The device batch configuration function
enables administrators to define different configuration tasks and perform the configuration
for a series of devices in batches periodically. This greatly improves the efficiency of
configuration upgrading.
6.4.1 Version
The current batch configuration tasks include:
Table 6-1 Batch configuration tasks

Task Name Task Description Task Parameters
 Read Community: the Read Community
Modify Configure
SNMP SNMP string should be specified when accessing
Parameters parameters, the device via SNMP
 Write Community: the Write Community
including Read-
Write string should be specified when accessing
Community, and the device via SNMP
 Modify Database Only: "Yes", save the
etc. for device
data into database only; "No", configure
the device and save the data into database
164
Raisecom

 Trap Server IP: the specified IP address
Set Trap Configure and
Server IP send end Trap for the network management system to
information, which the device sends Trap.
 Trap Port: the number of the Trap
including Trap
target address, receiving service port on the network
Trap port management host to which the device
number, sends Trap
 Operation Type: "Add": add the Trap
operation type,
and etc., to Server IP to the Trap Server list;
device. "Delete": delete the Trap Server IP from
the Trap Server list.
Reboot Send the Reboot Send Reboot Command: "Yes" means
Device Device reboot the device at once.
command
Set Set NTP/SNTP NTP/SNTP server: assign NTP/SNTP
NTP/SNTP server IP address server IP address, after configuring
Server for iTN2100, successfully, the device will perform
OPCOM3500E time verify by connecting to
and NTP/SNTP server.
OPCOM3500E-
6.
 Time mode: two modes for time: adopting
Set NE Time Set NE time for
iTN2100, current time of NNM server or assign
OPCOM3500E time by manual;
 NE time: set NE time.
and
OPCOM3500E-
6.
Switch command
 Send Keep Alive Message: "Yes", send;
Set Keep Configure Keep
Alive Alive message "No", not send.
 Sending Interval: the interval of sending
Message information,
including Keep Keep Alive to the device can be chosen
Alive message from 5minutes, 15minutes, 30minutes,
sending interval, 1hour, 2hours, 4hours, 6hours, and
and etc., for the 8hours.
device.
Set Admin Set the Admin Admin Status: "Up", the Admin status
Status for status of a port of the port on the device is up;
CPE Port on the device. "Down", the Admin status of the port
on the device is down.
Set Speed and Set port Speed/Duplex: set the rate/duplex
Duplex Mode rate/duplex mode for the port on the device, can
for Port mode for a port be chosen from Auto Negotiation,
on the device. 10M/Half Duplex, 10M/Full Duplex,
100M/Half Duplex, 100M/Full
Duplex, 1000M/Half Duplex,
1000M/Full Duplex
165
Raisecom

 Ingress Bandwidth (kbps): set the ingress
Set Ingress Set the
and Egress Ingress/egress bandwidth (by kbps) for a port on the
Bandwidth bandwidth for a device
 Egress Bandwidth (kbps): set the egress
for Port port on the
device. bandwidth (by kbps) for a port on the
device
Save Save all Save the changed configuration:
Configuration configuration "Yes", save changed configuration
information for information for the device
the device.
 Old Password: enter the old enable
Change Set device
enable enable password for the device
 New Password: enter the new enable
Password password.
password for the device
 Console User: the name of the Console
Change User Set device user
Password password. user on the device
 Old Password: Old Console password on
the device
 New Password: New Console password
on the device
Take "set Trap Server IP" as an example, the following sections will introduce how to deploy
device batch configuration task.
6.4.2 Adding batch configuration task

You can open up the main view of Batch configuration control by clicking EMS Config >
Batch Task Center on the system main menu.
Figure 6-8 Main view of batch task center

The steps to add new task:
166
Raisecom
Step 1 Select an task in Common Commands group or Switch Commands group on the Batch
Tasks list on the left of the Batch Task Center window, right-click on the blank area of the
"Task List" window and click the menu item Add on the shortcut menu, or click the button
Add on the toolbar of the window Task List, or right-click on the selected item on the "Batch
Tasks" list and click Add on the shortcut menu, an Add Task guide dialog window will
appear, as shown in the following figure.
Figure 6-9 Adding task guide_task basic information

The interface requires the following properties to be input:
 Task Type: System supports the following task types by default: Modify SNMP
Parameters, Set Trap Server IP, Reboot Device, Set Keep Alive Message, Set Admin
Status for End Port, Set Speed and Duplex Mode for Port, Set Ingress and Egress
Bandwidth for Port, Save Configuration, Change Privilege Password, and Change User
Password.
 Task Name: Assign a name for the task. For example: Set switch Trap target IP
 Task Status: the initial status of the task: enable or disable
 Execute Mode: You can select from: Manual, Once Only, Monthly, Weekly, and Daily.
The corresponding items on the dialog box will change as the Execute Mode change.
 Execute Time: The time when the task is executed. Considering the operation delay the
FTP server may meet in busy period, the system will adjust the time point for executing
the task according to the situation to avoid network traffic jam. Hence, the time when the
task is executed may not be the time set up before. However, the time difference will not
exceed 30 minutes. For manual execute mode, the time difference will not exceed 5
minutes.
For manually executed tasks, if the task status is "Enable" when the task is added,
the upgrade/backup management background will execute the task immediately.
Manually executed tasks will not be executed periodically. You can execute the task
167
Raisecom
again by modifying task properties or enabling the task. Tasks whose task type is
"Once Only" will not be executed periodically. Different from the tasks with task type
"Manual", you can set up the time point for executing the task. Tasks with task types
"Daily", "Weekly" or "Monthly" will be executed periodically according to the setting.
Step 2 Click Next and enter the next page, as shown below. For different type of task, the parameters
are different.
Figure 6-10 Adding task guide_task parameter setting

Step 3 If the object of the selected task type is device, after filling in all the parameters for the task
type, please click Next to enter the next page, as shown below.
168
Raisecom
Figure 6-11 Adding task guide_selecting task objects

You could select the devices the task will be executed on in this page. To add a device, please
click the button Add and tick the selected devices and click OK. To delete a device, select the
device on the list and click the button Delete. You can copy the device list of an existing task
to the current task by ticking the Select devices of existing task, selecting an item on the
drop-down menu or clicking Search… to select existing task.
The content of this page varies with the type of object of the task. If the object of the
task is device, the list shown on this page will be device list; if the object of the task is
port, the list shown on this page will be port list.
Step 4 When you click Add, a "Select Device" dialog box will appear, as shown below.
169
Raisecom
Figure 6-12 Selecting devices

Query filtering for devices has already been set up. That is, for a specified task, the devices
that support this task are inputted in the "Device Type" item in advance and cannot be
modified. Click Query, system will list all qualified devices beneath the query panel. Tick the
devices to be added to the task, and click OK, system will display all selected devices in the
device list.
If the object of the task is port, when you click Add, a "Select Port" dialog box will pop
up. Forming a port list is the same process as forming a device list.
Step 5 After selecting devices, please click Finish. The system will organize the information that has
been inputted in the add task guide as a complete task record and save it in the database.
Batch configuration tasks whose object resource is device are Modify SNMP
Parameters, Set Trap Target IP, Reboot Device, Set NTP/SNTP Server, Set NE Time,
Set Keep Alive Message, Save Configuration, Change privileged Password, and
Change User Password. Batch configuration tasks whose object resource is port are
Set Admin Status for End Port, Set Speed and Duplex Mode for Port and Set Ingress
and Egress Bandwidth for Port.
6.4.3 Modifying batch configuration tasks

Select the task to be modified on the task list, right-click on the selected task and click
Properties on the shortcut menu, or click on the toolbar, Edit Task Properties
dialog box will pop up:
170
Raisecom
Figure 6-13 Editing task properties

All properties of a task except for task type can be edited in this dialog box. The content of the
Edit Task Properties dialog box is the same as that of the Add Task dialog box.
6.4.4 Viewing task details

Select a task in the task list, the resource information corresponds to the selected task will be
shown in the Task Detail List beneath the Task List, as shown below.
171
Raisecom
Figure 6-14 Task details

Every task detail corresponds to one resource of the task. Every task detail contains the
following information:
 Device Name: The name of the device
 IP Address: The IP address of the device.
 Device Type: The type of the device
 Result: The result of the latest execution. If the task has never been executed, the result
will be "Unexecuted". Other statuses include "Successful" and "Failed".
 Operation: When the execution failed, here shows the description of the cause of failure.
 Execute Time: The time when the task is executed.
Select a row in the "Task Detail List", right-click on the row, the following operations are
available:
 Click Add, an Add Device dialog box will pop up;
 Click Log, a Task Log Management dialog box will pop up. The history running status
information of the device for this task will be displayed here.
 Click Delete, system will delete the device resource
 Click Enable, the system will execute the task again on the selected device.
 Click Export > All Items/Current Page/Selected Items > To Excel File, device
resource information of the task will be exported to Excel file.
 Click Export > All Items/Current Page/Selected Items > To Text File, device resource
information of the task will be exported to Text file.
There are buttons correspond to the right-mouse-button shortcut menu on the toolbar of the
"Task Detail List".
Click the button Show Query on the toolbar of the Task Detail List, the query panel will
open up. Enter query conditions and click Query, only the devices accord with the query
172
Raisecom
conditions will be shown on the task detail list. For instructions of query, see section 2.5
Common query interface.
6.4.5 Enabling batch configuration tasks

To enable a disabled task or execute a manually executed task once more, you can select the
task to be enabled on the task list of the Batch Task Center window, click Enable on the
right-click menu, or click the button Enable on the toolbar of the Task List, the system will
enable the task.
You can modify task properties in Edit Task Properties dialog box. All properties except for
task type can be modified. System will execute the task according to the new parameters and
execute manually executed task immediately as long as the task status is "Enable".
Select a device resource on the Task Detail List, right-click on the record of the device and
click Restart on the shortcut menu, or click Restart button on the toolbar, system will
execute this task again on the selected device.
6.4.6 Disabling batch configuration tasks

To disable an operation task, you can select the task to be disabled on the task list of the
Batch Task Center window, click Disable on the shortcut menu, or click the button Disable
on the toolbar of the Task List, the system will disable the task.
Modify the task status to Disable in the Edit Task Properties dialog box.
6.5 Batch executing commands script

6.5.1 Overview
NView NNM system provides function of batch executing commands script. This module
takes local script at client side as unit, providing application of configuration commands to
multiple devices in turn and also can view execution result on devices.
The batch execution of commands script includes two parts:
 NView server: It is the core of batch executing commands script. For the device, NView
server is the client of Telnet, device is the server of Telnet; for the client, NView server
receives script execution task from client and applies it to device.
 NView client: It is the expression of batch executing commands script at front end,
providing friendly guiding user interface. The application of all script task, viewing of
information, edition of script, etc. functions are all expressed and processed by client.
6.5.2 Batch executing commands script

Script at client side can be executed in turn on multiple devices via Telnet of remote server.
You save the commands script as script of client and for batch executing commands text
options. It is recommended to save command text in format of ".txt".
After you select multiple devices, the script will be executed in turn according to device order.
It connects to one device at first, after the device finishes execution of script, connecting to
the next device and until finish execution in the last device.
173
Raisecom
Click EMS Config > Batch Command Line Script Execution in the main menu to perform
this function. The interface shows as below:
Figure 6-15 Batch executing commands script

The interface includes four parts:
 The top of interface is tool bar, including: Open, Issue Order, Stop, Save, Export and
Clear functions.
 The upper column is area for displaying script content, right-key menu including
functions of Open, Link, Stop and Save.
 The middle of interface is area for displaying execution progress.
 The bottom of interface is area for displaying script execution result, right-key menu
including functions of Export and Clear.
The function of right-key menu of upper and bottom displaying area is identical to toolbar.
Detailed introduction of functions of right-key menu for text area and buttons in tool bar:
 Open: open file selection box to choose client script file. The content of script will be
displayed at upper area of interface.
 The script content will be displayed at upper area of interface when you chooses script
file and open it, as figure shows below:
174
Raisecom
Figure 6-16 Displaying script

 Issue Order: click Issue Order to open device selection interface, as figure shows below.
In support of tick off multiple devices, port ID is not editable, only in support of login
port 23 of Telnet protocol. You need to fill with correct user name and password for
linking.
Figure 6-17 Connection of devices

 You select device to execute script and click OK, the content of script file will be
executed in the devices in turn. The process of execution: after script is executed in one
device, it links to the next device and executing in the new connected device, until it
175
Raisecom
finishes execution in the last device. Suppose choosing two devices now, the script
finishes execution in the first device and then connect to the second one, as below figure
shows:
Figure 6-18 Execution of script

 Stop: to stop the waiting or running task by this function.
 Save: to save the contents in script displaying area in client local file.
 Export: to export script execution result to local, system pop-up a selection box for local
files selection.
 Clear: to clear the content displayed in script execution result area.
 Progress: the progress of script execution in device group. Displaying progress according
to the devices total and number of devices finished execution.
6.6 OLP route module

6.6.1 Overview of module
OLP (Optical Line Protocol) system is an auto-monitor protection system based on all optical
cable link and independent from communication transmission system. When optic fiber
attenuation is increased large enough to degrade communication quality or working fiber is
broken, system can quickly switches working fiber to standby fiber by automation in real-time
and then keep on communication. Thus the synchronization switchover and protection of fiber
line is implemented to improve availability of fiber line and enhance reliability of
communication in system, and guarantee server quality.
6.6.2 Function features

OLP route management module is application software module over NView NNM system,
used to maintain and monitor OLP fiber line auto-switching protection. The simple and direct
176
Raisecom
interface and strong line maintenance function greatly improves the maintenance of OLP
system.
See section 6.6.12 Cards list for detailed information.
6.6.3 Startup of module

Startup NMS client at first, click EMS Config > OLP Route in menu bar to startup this
module, as figure shows below.
Figure 6-19 Main view of OLP route

The left of interface is route tree; the right side is route diagram and information panel. You
can launch OLP functions from right-key menu in route tree.
After adding route, choose one route and double-click or choose Open Route from right-key
menu, then detailed information of the route will display in route information panel, as figure
shows below.
177
Raisecom
Figure 6-20 Detailed route information
6.6.4 Interface style
Figure 6-21 Main view of OLP route management module

Elements and descriptions of OLP route module as below table showing.
178
Raisecom
Table 6-2 Elements in the View

Element Definition
1x2 optical switch
2x2 optical switch
Optical splitter
Protect channel
Working channel
LOS in the channel
1:1 OLP card (select signal for transmission
and receiving, including two 2x2 optical
switch)
1+1 OLP card (concurrent transmission and

select signal for receiving, including one 1x2
optical switch and one optical splitter)
179
Raisecom
6.6.5 Function of module

This chapter describes the detailed functions of OLP route component.
OLP route is made of a pair of optical line protecting card and main/backup fiber connected.
This component takes management of OLP route as a whole. Create, delete and modify is
operated usually by right-click menu in route tree view.
6.6.6 Create new route

Under the route tree, right-click the mouse and select Add Route, the system will create a
new route and display instantly, the default name as "Unnamed", but full name displayed in
the route tree is "Unnamed @ A Card: Not Designated < > Z Card: Not Designated" (the left
part of "@" is the route name, right part is associated card) as shown below. For a newly
created route, if not designating associated card for it, A card and Z card name will be
displayed as "Not Designated".
Figure 6-22 Creating a route
6.6.7 Open route view

Under the route tree, right-click or double-click the route and click Open Route.
You can edit OLP route properties, refresh status, assign relative cards and configure or
manage on the assigned card, etc.
View from performance, the system can manage at most 5 routes at a certain
moment, namely five OLP route management windows are available at the same
time.
180
Raisecom
6.6.8 Appoint relative card for route

In view of route window, you can designate associated card for A or Z. For example, to
designate card A, firstly click Select, then pop-up the window to select designated card,
secondly click Save; if not designated, click Cancel.
After designate cards for OLP route, the system automatically communicates with NE where
card located, to get the latest equipment information, and redraw route topology. While both
ends of cards are designated, the system will refresh cable connection status based on device
information. You can manually click Refresh as required, to obtain the latest state of route
cable and device.
Figure 6-23 Creating a route
Figure 6-24 Refreshing a route

OLP protect mode includes 1:1 mode and 1+1 mode.
181
Raisecom
Figure 6-25 Route status in 1:1 mode

As the different cards offer different card information, so Select will display its own
configuration and describe information, such as OPCOM600-OLP-A view as below. Under
Select window, OLP route parameters are configurable, which refer to the corresponding user
manual.
Figure 6-26 "Card Selection" of OPCOM600-OLP-A
 Even one end of OLP route associate with a card, it is available to designate a
new card,
 If a card has been associated with a OLP route, then this card cannot be
designated again, If necessary, delete its associated OLP route before the new
designation;
 Whether OLP route is consistent with the actual equipment deployment, is
guaranteed by maintenance staffs instead of the component itself.
182
Raisecom
You can set reference optical power for "Primary Service" and "Secondary Service"
respectively, history optical power is set according to the value requires to record, as figure
shows below.
Figure 6-27 Threshold configuration_referring to optical power

Refresh after the setting of Reference Power, a difference (the current optical power minus
reference power value) will display behind current optical power value. If not set reference
power, the difference will not display.
183
Raisecom
Figure 6-28 Threshold configuration_1+1 mode
Figure 6-29 Threshold vonfiguration_1:1 mode
6.6.9 Edit route information

There are two methods to open this window:
 Click Edit Route Info in route window.
 Right-click the selected route and click Edit Route Info.
184
Raisecom
Figure 6-30 Editing route information

Modify related items and click Save. The system will pop up the following dialog.
If examine the effect of the modification, click Refresh button. Click Close to close it.
Theory attenuation calculator

This component provides you with theory attenuation calculator for some standard cables.
Click Theory Attenuation Calculator to open it. Select Type and Cable Length, the system
will automatically calculate the db value.
Figure 6-31 Theory attenuation calculator
Transmission cable technology always in progress, so theory attenuation (attenuation

coefficient) of unit length cable has been changed. In order to adapt to these changes,
185
Raisecom
the components of the cable attenuation coefficient can be customized according to

user's requirements, specific customization technique please contact with Raisecom
technical supporters.
6.6.10 Delete route

In the tree view of route topology, right-click a selected route, click Delete Route then popup
a "Confirm" dialog box. Click Yes to delete the route.
When one OLP route is deleted, the route information in the system will be deleted too,
meanwhile, route-related cable information will also be deleted. Associated cards are not
deleted, but the relation with route is lifted, after that, it can be designate to other route.
Integer route under system monitor carries a lot of user inputting information, be
careful before deleting it.
6.6.11 View route information
View all routes list

Under route tree right-click at random position, select View All Routes, and then it will pop-
up a window as below.
Figure 6-32 Viewing all routes

"View All Routes" lists all routes in the system, you can click Export button, in the format
of TXT or Excel as required.
View all cables list

Under route tree right-click at random position, select View All Cables, and then it will pop-
186
Raisecom
Figure 6-33 Viewing all cables

"View All Cables" lists all cables in the system, you can click Export button, in the format of
TXT or Excel as required.
View card power list

"Card Power List" display detailed information of one OLP Route. Under route tree right-
click at random position, select Card Power List then click on the left, then it will pop-
Figure 6-34 Card power list

Click Export to export card optical power of all pages, current page or selected pages in txt or
Excel format.
187
Raisecom
View current alarm list

"Current Alarm Info" displays alarm information of one OLP. Under route tree right-click
at random position, select Current Alarm Info, and then click on the left, as below.
Figure 6-35 Current alarm list_customized table

Click Export to export card optical power current alarm information of all pages, current
page or selected pages in txt or Excel format.
View route topology graph

Right-click at any place of route tree view, choose item Route Topology Graph and system
pop-up view of "Route Topology" as below showing.
188
Raisecom
Figure 6-36 Route topology

The route topology view presents connection relationship between system NE and OLP route
module. You can click Export to export topology graph in PNG format.
6.6.12 Cards list

The cards supported by OLP route module shows in below table:
Table 6-3 Cards supported by OLP route module

Card Name Chassis Name
OPCOM100-OLP-A RC006
OPCOM600-OLP-AE RC006
OPCOM600-OLP-B(A.00) RC006
OPCOM600-OLP-B(B.00) RC006
OPCOM600-OLP-B(B.10) RC006
OPCOM600-OLP-B5 RC006
OPCOM600-OLP-A OPCOM3500E
OPCOM600-OLP-B(REV.B) OPCOM3500E
OPCOM600-OLP-B5 OPCOM3500E
189
Raisecom
Card Name Chassis Name

OPCOM600-OLP-AE RC006
OPCOM600-OLP-B(B.10) OPCOM3500E
OPCOM600-OLP-AE OPCOM3500E
6.7 Device Syslog management

Syslog is a standard system service that is provided through port 514. Device send Syslog log
in the format of UDP message to specified Syslog server (NMS server), and the server will
report the Syslog log to the database timely. You can query or export Syslog log using Syslog
log management component. The log can be received and resolved if only the Syslog log sent
by the device conform to the Syslog protocol format defined in RFC-3164 criterion.
6.7.1 Receiving Syslog

Configure the IP address and port number of the Syslog receiving server of the device using
device command lines or device element management system. The IP address for Syslog
receiving server must be set to the IP address of the NMS server. The port number must be
514.
Make sure that the Syslog receiving service in NView NNM is operating.
6.7.2 Querying Syslog

Click Log > Syslog on the system main menu, the main view of Device Syslog is displayed.
190
Raisecom
Figure 6-37 Querying device Syslog

Enter the query conditions in the query panel, which can be opened by clicking the button
Show Query, and click , the Syslog information satisfy the query conditions will be listed
beneath the toolbar of the Device Syslog window.
Select a row of record on the Syslog list, and right-click on the record, a shortcut menu will
appear, as shown above. Operations listed on the shortcut menu are:
 Delete, system will delete Syslog information.
 Export to Excel, system will export Syslog information to an Excel file
 Export to Text, system will export Syslog information to a Text file.
191
Raisecom
NView NNM Operation Guide 7 Alarm event management
7 Alarm event management
This chapter mainly introduces the related definition and operation concerning alarm event
and how to manage alarm events using NView NNM system, including the following sections:
 Overview
 Alarm synchronization task management
 Current alarm monitoring
 Topology alarm monitoring
 Device alarm monitoring
 Alarm list query
 Current alarm filter
 Alarm reversal
 Trap notification
 Historical alarm management
 Trap definition management
 Troubleshooting knowledge management
 Alarm Statistics
7.1 Overview
When operating, network device should have a channel to report fault and operating
abnormity to the administrator to help the administrator remove the fault in time and thereby
guarantee the quality of network operating. This process is called "Trap" in SNMP
management. "Trap" has the following characteristics:
 Trap information is sent automatically. The management workstation does not have to
send a request.
 Trap is based on UDP protocol, hence reliability is not guaranteed. That is, in some
circumstances, Trap information may be unable to reach the management workstation.
For the prerequisites for receiving Trap information correctly, please refer to
prerequisites of receiving alarm correctly.
 The Management workstation monitors Trap information at port 162.
In NView NNM system, Trap information is named "Alarm Event". If an alarm event is
received, system will notify the administrator in a striking way, provide detailed information
192
Raisecom
of the alarm event, and locate the alibi of the fault. The system may even provide a resolution
to assist the administrator remove the fault in time and guarantee the smooth operation of the
network.
Knowledge of the following definitions is essential for learning to use NView NNM system to
manage alarm event.
7.1.1 Alarm status

In NView NNM system, every alarm event may be in one of the following two statuses:
 Newly generated: Received alarm event from network device
 Recovered: If the fault occurred on network device disappears or some performance
indexes get back to normal automatically, the Agent will send "Alarm Recovery
Information" via Trap to the system. System will modify the alarm status of the
corresponding alarm event to "Recovered" after receiving the recovery information. By
this time, the fault on the device should have been removed. The recovered alarm
displays in green in the alarm list.
7.1.2 Operation status

For every alarm event, network administrator may execute some operation on it. There are 4
types of operations can be executed on an alarm event, leading to 4 types of operation status:
 Unacknowledged: The network administrator has not executed any operation on the
alarm event.
 Acknowledged: As to newly generated alarms, you can execute an "acknowledge"
operation on a current alarm to modify the status of the alarm to "Acknowledged" if
he/she is aware of the content of the alarm. Please note that the alarm status is
"Acknowledged" does not mean that the corresponding fault has been removed from the
network.
 Cleared: All current alarms can be changed to historical alarms by executing the "clear"
operation on them. The operation status of the alarm will become "Cleared" after the
operation. And "Cleared" alarms will be removed from the current alarm list and listed
on the historical alarm list.
 Filtered: The system provides an alarm filtering scheme, which filters some received
alarms from being displayed on the current alarm list. The operation status of these
alarms is "Filtered". All filtered alarms will not be displayed in the current alarm list, but
be saved as historical alarm directly.
NView NNM adds function of canceling alarm acknowledge, which is in support of change
the "Acknowledged" alarm to "Unacknowledged" status, see section 7.3.9 Confirming alarm
cancellation detailed operation.
7.1.3 Alarm synchronization

With alarm synchronization, the NView NNM can synchronize alarms on a device to the
NView NNM alarm database. It helps improve accuracy of alarm information.
The NView NNM performs alarm synchronization through multiple trigger modes and you
can select one or more on demand.
 Support periodically performing alarm synchronization. You can create multiple alarm
synchronization tasks. The NView NNM performs alarm synchronization periodically in
alarm synchronization task mode.
193
Raisecom
 Support manually performing alarm synchronization.

 Support synchronizing alarms immediately after a NE is added.
 Support synchronizing alarms immediately after offline NEs resume online. Offline NEs
are those that cannot be managed by the NView NNM or NEs that are offnet. In this
mode, except for all NEs at the topology, you can also configure subnets or NEs that do
not need to perform alarm synchronization when they are online.
 Support synchronizing alarms after the NNM server is started. In this mode, except for
all NEs at the topology, you can also configure subnets or NEs that need to perform
alarm synchronization after the NNM server is started.
7.1.4 Current alarm

For NView NNM system, whether an alarm event is a "Current Alarm" or not is decided by
the operation status of the alarm. All alarms that have not been cleared or filtered will be
considered as current alarms. Please note that the "Current" is only related to the status of the
alarm. It has nothing to do with any time period conception. Current alarms are of
considerably high status in network management.
7.1.5 Historical alarm

Apart from "Current Alarm", all alarms are considered as "Historical Alarm". They are alarms
that have been cleared or filtered. Please note that the "Historical" is only related to the
operation status of the alarm. It has nothing to do with any time period conception.
7.1.6 Alarm filtering

NView NNM system provides an alarm filtering scheme, which enables you to set up filter
rules to have alarm of certain types from certain locations do not be received by the network
management system. You can choose whether to save filtered alarms into the database. If you
choose to save filtered alarms into database, these alarms will become historical alarm and
their operation status will be "Filtered".
7.1.7 Alarm compressing

The system provides an "Alarm Compressing" function, which effectively prevents the system
from the pressure from repeated alarms. Repeated alarms are alarms of the same type and
from the same location. For repeated alarms, the system will not consider them as new alarms
but alarms in the same group, and only count the number of the alarms in the group. You can
enable or disable the function in the corresponding parameter configuration part in Trap
receiving service.
7.1.8 Alarm reversal

For ports not open the service, the alarm reversal is used to avoid generating related alarm
information and avoid alarm interference. To configure alarm reversal function to make the
port alarm status opposite with the actual status, i.e. if there is alarm actually, it will not report
alarm; if there is no alarm actually, and it will report alarm.
7.1.9 Alarm live period

The system provides an alarm live period calculation period, which calculates the time
difference of the start time of the alarm (the time when the alarm is reported for the first time)
194
Raisecom
and the end time of the alarm (the time when the alarm is automatically restored or cleared) to
get the fault clearance time of the system.
When a fault recovery event sent from a device is received by the system, the system will
automatically match the recovery event to existing fault alarms. If the corresponding fault
alarm exists, the system will set the statues of the alarm event to "Recovered" automatically.
If the alarm event is on the list of "Current Alarm", the record of the alarm will be transferred
to the list of "Historical Alarm" as the status of the alarm changes.
7.1.10 Alarm levels

For every type of alarm event, NView NNM system marks them with a level to show its
severity. NView NNM provides 5 levels in all, from the most serious to the least serious, they
are:
 Critical Alarm (Critical): The highest level alarm, which will interrupt the
communication. Marked in red:
 Major Alarm (Major): Service continues while the performance declined considerably
and affected the operation. Marked in orange:
 Minor Alarm (Minor): Alarm event occurs but do not affect the operation of the service.
Marked in yellow:
 Warn Alarm (Warn): The service is operating in order. Only an ordinary problem
occurred. Marked in blue:
 Unknown Alarm (Unknown): Alarm events that cannot be recognized. Marked in light
grey:
The level of a type of alarm can be redefined.
7.1.11 Content of alarm event

A complete alarm event generally contains the following 5 parts:
Basic information
Basic information consists of recognizable information resolved by the system, including
 Alarm Level: The critical level of the alarm event. It depends on the level designated to
the type of alarm
 Alarm Name: The name of the type of alarm event.
 Alarm Status: The current status of the alarm event.
 Alarm Operation Status: The status of the alarm after operations have been executed on
them by network administrators
 Name of Alarm Source: The name of the source where the alarm comes from. For alarm
from device, it is the name of the device node; for alarm from card, it is in the format of
"device node name +chassis name+ card name"; for alarm from port, it is in the format
of "device node name + chassis name+ port name".
 Device Type: The type of the alarm source device
 Source Type: The type of the alarm source. It depends on the alarm source type
designated to the type of alarm.
 Service Affection: Whether the alarm affects network service or not. The content
depends on the affection definition designated to the type of alarm.
195
Raisecom
 Location: The physical location of the alarm source (device, card, port).
 IP Address: IP Address of the alarm source device
 Up Count: How many times the alarm event occurs during the time period from the time
it comes up for the first time to the time it recovers by itself or is cleared by administrator.
 First Report Time: The time when the alarm event is reported for the first time.
 Latest Report Time: The time when the alarm event is reported for the last time.
 Recovered Time: The time when the alarm event recovered by itself.
 Alarm live period: The time difference between the first report time and the end time of
the alarm.
 Response Time: The time from the first report to acknowledge or clear.
 Process Time: The time from the first report to alarm recover.
Operation information
Operation information consists of system self-recovery information and administrator
operating information, including:
 Operator: The administrator who acknowledged or cleared the alarm event.
 ACK Time: The time when the administrator acknowledged the alarm event.
 ACK Log: The log information made out by the administrator when he/she
acknowledged the alarm event.
 Cleared Time: The time when the administrator cleared the alarm event.
 Cleared Log: The log information made out by the administrator when he/she cleared the
alarm event.
Customer information
Customer information will be included in the alarm information if the alarm event affected the
customer. Since one alarm event may affect several customers (e.g. an alarm event from an
access port will directly affect all access customers communicate via this port), a list of
information of affected customers will be included in the alarm information.
Troubleshooting
Historical phenomenon and removal strategy of the corresponding alarm type is provided as
the reference for fault removal.
Trap content
Before being resolved, the original content of an alarm event is a group of property
combinations in the format of "key-value".
7.1.12 Alarm auto-synchronization

System provides alarm auto-synchronization function. After the device gets offline and cannot
managed by NMS, the alarms generated and saved in the device will auto-synchronized to
NMS when device network management recover, then it can guarantee device alarm
information in is real and in details.
This function is only available to device that is in support of saving NE alarm (like
OPCOM3500E); it is invalid for the NE that does not save alarm (like RC002).
196
Raisecom
7.2 Alarm synchronization task management

The device adopts the Trap mechanism of SNMP to send alarms to the NView NNM. During
the transmission, if a packet is lost or a link is blocked, the Trap cannot be sent to the NView
NNM. Therefore, the alarm cannot be recovered properly.
Alarm synchronization is used to synchronize alarms on a device to the NView NNM in an
alarm polling synchronization mode. This helps make alarms on the device and on the NView
NNM consistent. In addition, this helps reasonably assign system resources of the NView
NNM.
When performing alarm synchronization, the NView NNM will compare alarms on the device
with alarms on the NView NNM. For any differences, the NView NNM will automatically
analyze and deal with alarms based on alarms on the device. Therefore, the accuracy of alarm
information will be improved.
Alarm synchronization task needs devices to support alarm synchronization. Some devices
only report Trap but cannot save alarms. Therefore, these devices cannot perform alarm
synchronization.
At present, only the iTN2100 family, the OPCOM3500E family and the RC002
support alarm synchronization.
7.2.1 Functions and features

Alarm synchronization task management has the following features:
 Support dealing with differences when performing alarm synchronization.
− When alarms on a device are not recorded in the NView NNM: the NView NNM will
add related alarms based on alarms on the device.
− When alarms on a device are recovered or cleared: if these alarms still exist in the
NView NNM, alarms will be upgraded into recovery status and then enter into
historical alarm database. The NView NNM will automatically generate recovery
alarms.
− The NView NNM judges a specific alarm based on the position (device, chassis or
ports) where the alarm is generated, alarm levels and properties of the alarm, ensuring
the accuracy of alarm information.
 Support periodically performing alarm synchronization.
− Support continuously performing periodical alarm synchronization.
− Support periodically performing alarm synchronization during a specified time range.
− Support performing alarm synchronization every2 hours, 4 hours, 6 hours, or 8 hours.
 Support manually performing alarm synchronization immediately.
 Support configuring the range of alarm synchronization.
− Support performing alarm synchronization on all NEs that support this function at the
NView NNM.
− Support performing synchronization on some subnet or NE.
 Support performing alarm synchronization in specific modes.
− Support synchronizing alarms immediately after offline NEs are online. Offline NEs
refers to NEs that cannot be managed by the NView NNM or NEs that is offnet. In
197
Raisecom
this mode, except for all NEs at the topology, you can also configure subnets or NEs
that do not need to perform alarm synchronization when they are online.
− Support synchronizing alarms when the NNM server is started. In this mode, except
for all NEs at the topology, you can also configure subnets or NEs that need to
perform alarm synchronization after the NNM server is started.
 Support viewing NE synchronization status and execution time of the alarm
synchronization task.
 Provide default alarm synchronization task. By default, the NView NNM performs alarm
synchronization once a day.
 Support configuring alarm synchronization task group, facilitating managing alarm
synchronization tasks.
If the NView NNM uses default alarm synchronization task provided by the system,
the NView NNM will automatically perform alarm synchronization at 00:00 every day.
7.2.2 Checking operating status of alarm synchronization center

services
Alarm synchronization task is based on alarm synchronization center service. Before
configuring alarm synchronization, you need to enable alarm synchronization center services.
By default, the alarm synchronization center services are automatically enabled. If

disabled, the NView NNM cannot perform alarm synchronize tasks periodically.
Step 1 Double-click the on the desktop.

Step 2 Enter the user name and password and then click OK.
Step 3 Check whether the "synchronization center" is started.
Step 4 If the synchronization center is stopped, right-click the record of synchronization center and
then click Start Process.
7.2.3 Configuration procedures

Configuration procedures for periodical alarm synchronization task are shown in Figure 7-1.
198
Raisecom
Figure 7-1 Configuration procedure of alarm synchronization task
The NView NNM perform alarm synchronization task periodically. In addition, the
NView NNM supports manually perform alarm synchronization tasks immediately.
This facilitates synchronizing current alarms on a NE in batch.
For a single NE that supports alarm synchronization, the NView NNM can
synchronize alarms through alarm synchronization task. In addition, the NView NNM
can synchronize alarms in the following modes:
 Right-click a NE at the topology, and then click Device Maintenance > NE alarm
Synchronize.
 In the configuration management interface of a NE, click Alarm Management >
NE Alarm Synchronize.
7.2.4 Configuring global parameters for alarm synchronization

Configuring global parameters for alarm synchronization refers to configuring all alarm
synchronization tasks. In addition, you can configure performing alarm synchronization when
a NE is added, a NE is re-managed by the NView NNM, or the NNM server is started,
199
Raisecom
Step 1 In the system menu bar, click Alarm > ALARMSYNMGT and a window is displayed.
Step 2 Click Sync Parameter Set on the left navigation tree to display global configurations of
alarm synchronization, as shown in Figure 7-2. Table 7-1 lists descriptions about global
parameters.
Step 3 After configuration, click OK to apply new configurations.
Figure 7-2 Global parameters of alarm synchronization
Table 7-1 Description of global parameters

Item Description
Period task schedule  Checked (default): for alarm synchronization tasks that are
enabled, the system performs alarm synchronization periodically.
 Unchecked: do not perform all alarm synchronization tasks.
After the new create NE  Checked (default): when a NE is added to the NView NNM, the
synchronous alarm NView NNM will automatically perform alarm synchronization.
 Unchecked: when a NE is added to the NView NNM, the NView
NNM will not automatically perform alarm synchronization.
200
Raisecom
Item Description
Nets yuan management  Checked: when the NView NNM detects a device is offset or
channel interrupt after offline, if the device is recovered (detected by the NView NNM
restoring synchronuous alarm or the device reports a Trap to the NView NNM), the NView
NNM will automatically perform alarm synchronization.
 Checked: support configuring range for performing alarm
synchronization. When select "all NE", the NView NNM
performs alarm synchronization on all NEs/cards at all subnets.
When selecting "no contain", you can click Detail and select
subnets or devices where alarm synchronization is not performed.
 By default, this option is not checked. If a device is recovered,
the NView NNM does not automatically perform alarm
synchronization.
Network management server  Checked: when the NMS server is started, the NView NNM will
after launch of synchronous automatically perform alarm synchronization.
alarm  Checked: support configuring range for performing alarm
synchronization. When select "all NE", the NView NNM
performs alarm synchronization on all NEs/cards at all subnets.
When selecting "no contain", you can click Detail and select
subnets or devices where alarm synchronization is not performed.
 By default, this option is not checked. If the NMS server is
started, the NView NNM does not automatically perform alarm
synchronization.
7.2.5 Configuring alarm synchronization tasks

By periodically synchronizing alarms on a device, alarm synchronization task ensures
consistent and accurate alarm information on the NView NNM and on the device. The NView
NNM provides a default alarm synchronization task for all devices on the internet,
automatically performing alarm synchronization at 00:00 every day. If necessary, you can
customize the period, time and range for performing alarm synchronization. In addition, you
can add alarm synchronization tasks.
Alarm synchronization task provides task groups. When you click each task group, alarm
synchronization tasks in this group will be displayed. You can either use default task group or
customize a task group to manage alarm synchronization tasks.
Adding alarm synchronization tasks

Step 1 In the system menu bar, click Alarm > ALARMSYNMGT and a window is displayed, as
shown in Figure 7-3. The left is the navigation tree and the right is the configuration area.
When you click a node on the navigation tree, the related configuration contents are displayed
on the right configuration area. Table 7-2 lists descriptions about the configuration view.
201
Raisecom
Figure 7-3 Configuration view
Table 7-2 Descriptions about configuration view

Node on the navigation tree Configuration area and function
Synchronization task Display all alarm synchronization tasks in

a form of list.
Task group Display alarm synchronization tasks in this
group in a form of list.
Task Display detailed information about the
alarm synchronization task. You can
modify parameters about the alarm
Alarm synchro status monitor Display NE synchronization status and
synchronization time of all alarm
synchronization tasks in a form of list.
Sync parameter set Display global parameters about alarm
synchronization. You can modify these
parameters.
Right-click the configuration area and you can query and refresh alarm
 Query: open the query panel and query task records.
202
Raisecom
 Refresh: refresh all task records or refresh task records based on some query
conditions.
Step 2 At the right configuration area, right-click the blank and then click Add Task to display a
window, as shown in Figure 7-4. Table 7-3 lists parameters about alarm synchronization tasks.
Figure 7-4 Adding alarm synchronization tasks
Table 7-3 Parameters about alarm synchronization tasks

Task name – Enter a name for an alarm synchronization task.

Run type  Auto Select an execution mode for the alarm
 Manual synchronization task. By default, the execution mode
is set to auto.
 Ban
 Auto: the NView NNM automatically performs
alarm synchronization tasks periodically.
 Manual: you can manually perform alarm
 Ban: alarm synchronization tasks cannot be
automatically enabled or be manually executed.
203
Raisecom
Task group – Click Select to display Task Group page.

Select a record and then click OK to select a group.
Right-click a record and you can add a task group,
modify the name and description about a task group,
or delete the task group (only when no alarm
synchronization task in contained in the group, will
you be permitted to delete the task group.)
Task remark – Enter descriptions or remarks about an alarm
 Every 2 hours
Task period Select a period for performing the alarm
 Every 4 hours synchtonization.
 Every 6 hours
 Every 8 hours By default, the NView NNM performs alarm
 Everyday synchronization every 2 hours.
Persist  Checked  Checked (default): continuously perform alarm
synchronize synchronization based on task period, after an
 Unchecked alarm synchronization task is started.
 Unchecked: in this mode, you need to configure
the begin time and the end time for an alarm
Begin time – Select the begin time form the dorp-down menu.
You cannot configure the begin time until the Persist
Synchroze is unchecked.
End time – Select the end time form the dorp-down menu.
You cannot configure the end time until the Persist
Synchroze is unchecked.
Immediately  Checked  Checked (default): immediately perform alarm
 Unchecked synchronization after adding an alarm
 Unchecked: do not immediately perform alarm
synchronization after adding an alarm
Step 3 Click Select at the bottom of Task Resource Domain to display Selection Domain view, as
shown in Figure 7-5. On this view, you can select the range for performing alarm
synchronization task by clicking , , , or . After selecting
a resource domain, click OK to apply new configuration.
204
Raisecom
Figure 7-5 Selection domain view
Devices and object sets are classified into three types:

 All object set: refers to all NEs at the NView NNM.
 Subnet device set: refers to all NEs at a subnet.
 Device: refers to a specific NE.
Step 4 Click OK at the Add Task tab page to apply new configurations.
Viewing and modifying alarm synchronization tasks
When modifying an alarm synchronization task, if the alarm synchronization task is

being performed, all modifications cannot take effect until this alarm synchronization
task is performed.
Step 1 In the system menu bar, click Alarm > ALARMSYNMGT.
Step 2 Click a task group node at the navigation tree and then right-click a task record. And then
click Modify Task. Or click a task node at the navigation tree to display a tab page, as shown
in Figure 7-6, On this tab page, you can modify related parameters and resource domain of an
alarm synchronization task (parameters are identical for adding tasks, as shown in Table 7-3).
205
Raisecom
In addition, you can view related information about an alarm synchronization task, as shown
in Table 7-4.
Step 3 After modification, click OK to apply new configurations.
Figure 7-6 Viewing and modifying alarm synchronization tasks
Table 7-4 Related information about alarm synchronization tasks

Parameters Description
Task status Display whether the alarm synchronization task is

started.
Creater Display the user name that is used to add the alarm
Create time Display the time when the alarm synchronization
task is added.
Deleting alarm synchronization tasks

click Del Alarm Syn Task to display a dialog box, asking Delete task?
Step 3 Click Yes to delete the alarm synchronization task.
206
Raisecom
Starting alarm synchronization tasks

After an alarm synchronization task is started, the NView NNM will automatically perform
alarm synchronization based on configured period.
Step 2 Click a task group node at the navigation tree and then right-click an alarm synchronization
task that is stopped. Click Start Task to display a dialog box, saying Start alarm synchro task
success!
Step 3 Click OK to apply new configuration.
On the Alarm Sync Global Config tab page, only when the Period task schedule
option is checked, will the alarm synchronization task be performed. If this option is
unchecked, even the alarm synchronization is enabled; the NView NNM will not
perform alarm synchronization periodically.
Stopping alarm synchronization tasks

An alarm synchronization task will not be re-performed after it is stopped. If an alarm
synchronization task is being performed when it is stopped, the current alarm synchronization
will not be interrupted.
Step 2 Click a task group node at the navigation tree and then right-click an alarm synchronization
task that is started. Click Stop Task to display a dialog box, saying Stop alarm synchro task
success!
Step 3 Click OK to apply new configuration.
When deleting, starting and stopping alarm synchronization tasks in batch, you can
press Ctrl and click multiple records. Or you can click a record and then drag the
mouse to select multiple records.
7.2.6 Performing alarm synchronization manually
Performing alarm synchronization tasks manually

You can immediately perform alarm synchronization by manually performing an alarm
synchronization task. You can specify a device on the Task Resource Domain part.
If some alarm synchronization task is being used to perform alarm synchronization,

you cannot manually perform the alarm synchronization task.
click Run Task.
207
Raisecom
When manually performing an alarm synchronization task, you can press Ctrl and
click multiple records. Or you can click a record and then drag the mouse to select
multiple records.
Performing alarm synchronization on all NEs manually

You can immediately perform alarm synchronization on all NEs by manually performing an
alarm synchronization task on all NEs.
Step 1 In the system menu bar, click Alarm > Syn Global Alarm.
Step 2 A dialog box is displayed, asking Alarm synchronous global net? Click Yes to perform alarm
synchronization on all NEs.
7.2.7 Viewing NE alarm synchronization status

You can view current synchronization status, the begin and end time of alarm synchronization
of NEs in an alarm synchronization task.
Step 2 Click Alarm Synchro Status Monitor at the navigation tree and all NE alarm synchronization
statuses are displayed on the right area. Table 7-5 lists synchronization status information.
Table 7-5 Synchronization status information

Ircnetnode ID Display unique ID for a NE at the NView

NNM.
Friendly_name Display the friendly name of a NE.
Alarm_Syn_Status Display whether alarm synchronization is
performed on the NE.
Alarm_Syn_Trigger mode Display alarm synchronization is performed
by the user or the NView NNM.
Alarm_Res_Syn_Beigin_time Display the begin time for performing alarm
synchronization on a NE.
Alarm_Last_Syn_ time Display the end time for performing alarm
synchronization on a NE.
Remark Display remarks.
208
Raisecom
7.3 Current alarm monitoring

7.3.1 Prerequisites to receive alarms correctly
To make sure that an alarm can be properly received and displayed by NView NNM system,
the following conditions should be satisfied:
 The network device has already been configured with parameters like Trap target IP,
SNMP parameters, and etc.
 All network devices under management and the management workstation on which the
NView NNM system locates are connecting to the network properly. The communication
on the links connecting the devices and workstations is unblocked. (A device on one end
of the link can Ping the device on the other end of the link; UDP protocol
communication is allowed)
 Port 162 on the host where NView NNM system server locates must not be occupied by
other processes. For example, in Win2003 Server operation system, the SNMP Trap
service that will occupy Port 162 is turned on by default. To install NView NNM on this
operation system, please stop the SNMP Trap service at first to release Port 162,
otherwise NView NNM system will not be able to receive alarm event. Please note that
only the host where the NView NNM system server locates should satisfy this condition.
When performing distributed installation, the host where the client is located does not
have to satisfy this condition.
 UDP protocol communication should be allowed in the network. In some circumstances,
all network devices should hide behind a firewall out of security consideration. Please
make sure that Trap can go through the firewall and reach the workstation, otherwise the
system cannot receive the alarm information.
 The agent of network device should set the Trap Server IP Address to the IP address of
the host on which the server of NView NNM system locates, and make sure that the
target port number conforms to the number of the port through which the Trap receiving
service is monitoring in NView NNM system. (Port 162 by default)
 The "SNMP Trap Receiving Service" of the NView NNM system must be turned ON and
running in order, otherwise the system will not be able to receive any traps.
 NView NNM system must have defined the type or alarm event, or even if the alarm
event is received, it will be treated as an unknown alarm.
 Please check whether the type of alarm event has been filtered by the NView NNM
system. Alarm events will not be properly displayed or handled if they are filtered by the
system.
 The host from which the alarm event is coming should have registered the corresponding
port (The port should be shown on device list.), or the system will discard the alarm
information from the port.
 The node of the host from which the alarm event is coming from should be a node in the
management domain of the current administrator, or the alarm information will only be
received, but will not be displayed. This is not a limitation for administrators from the
"admin" group.
If all the conditions above are satisfied, NView NNM system should be able to receive and
resolve alarm information properly. Please note that these conditions are only the necessary
condition of receiving alarms properly. More conditions may be required in some applications.
209
Raisecom
7.3.2 Grouped alarm monitoring

NView NNM system provides current alarm real-time monitoring function. This function
enables display received traps in groups according to assigned conditions and providing count
and location functions according to alarm level. You can open Current Alarm List under
Grouped Alarm by click Alarm > Grouped Alarm in the main menu.
Figure 7-7 "Current alarm list

The grouped alarm list is in support of customized column. Click at top-left of the list to
open customized column dialog box, as shown below. Select the Column Name to display
from the list and click OK to display the customized columns information.
210
Raisecom
Figure 7-8 Customized column-grouped alarm List

At present, NNM system provides monitoring rules classifying in "System-defined alarm" and
"Customized alarm".
 The "System-defined alarm" including alarms reported in the last 1 hour, alarms reported
in the last one day, alarms reported in the last 1 week, alarms reported in the last 1 month,
acknowledged alarms, newly generated alarms and recovered alarm, etc. Administrator
can click the related node in monitor rule tree to view the alarm information in the
corresponding group;
 "Customized alarm" can create alarm monitoring rule in accordance with source
condition, properties, customer influence, such as creating "alarms responding over 1
hour", "alarms processing over 1 hour", "key customer network alarms", etc.
By configure monitoring rule, administrator can pay more attentions on monitoring key
customer and key devices, meanwhile, it is able to supervise the response and process speed
of alarm information and provide direct viewing data for different maintenance service, then
improve SLA of carriers.
The "System-defined alarm" is not in support of edition, but it affects all admin accounts;
"Customized alarm" supports edition function, administrator can adjust the rules according
need and its affecting range is the admin accounts assigned in "Share Policy".
Every monitor page provides alarm information auto-refresh and manual refresh function.
System default refresh interval is 10 seconds , click to modify refresh
interval. The system support minimum refresh interval is 5 seconds.
Operations in alarm list

The alarm information that satisfying condition will be classified and statistic, the following
operations are available in the list:
211
Raisecom
 Acknowledge: Acknowledge the selected alarm/alarms. Please note that the operation is
applicable through the right-click menu only when all the selected alarms are "Newly
generated" alarms.
 Clear Alarm: Clear the current alarms that satisfy a specified condition. Its sub menu
contains the following operation:
─ Clear Selection: Clear selected alarm/alarms.
─ Clear Alarms with Same Type: Clear all alarm/alarms in the list that is of the same
type as the selected alarm.
─ Clear Alarms With Same Location: Clear all alarm/alarms in the list that are from the
same location as the selected alarm
─ Clear All Acknowledged Alarms: Clear all acknowledged current alarms in the list
─ Clear All: Clear all the current alarms in the list
 Troubleshooting: Query the troubleshooting experience knowledge database for related
fault removal experience helps locate cause of fault quickly and efficiently.
 Properties: Detailed information of the selected alarm is shown in the "Properties" dialog
box.
 Locate in Topo: Locate the corresponding node of the selected alarm, and open the card
view or topology view that the selected alarm affects
 Locate in Device: Locate the position on the device pane where the selected alarm comes
from, and open the element management system of the device corresponds to the
selected alarm. The function is applicable to alarms from chassis, card, and port (alarm
resource information is need to complete the localization).
 Filter Setup: You can set up filtering rules directly on the basis of the selected current
alarm, which can make the deployment visual and quick.
You can filter the alarm event of some NE in some time according to the following operations:
Step 1 In alarm period filter rule view, click Add on top of tool bar to pop up Add Filter Rule dialog
box.
Step 2 Select the rule mode to deploy on top of the dialog box: all object or custom object.
212
Raisecom
Figure 7-9 Deploying rule mode

 If select all objects, you can click Next to enter "Step 3"directly.
 If select custom object, you can click to select a classify in the drop-down list box on the
left of the interface, and select filter rule application object in the pop-up interface, then
click Next to enter "Step 3".
─ To select "NE" or "Card", in the pop-up interface, select NView NNM network
element or card record, and then click OK.
─ To select "NE type" or "Card type", in the pop-up interface, select device type and
then click OK.
213
Raisecom
It can only show less than 10 pieces of records in the "Selected alarm source"; if it
exceeds 10 pieces of records, it will pop up Prompt dialog box to prompt error.
Step 3 Pop up filter alarm time setting dialog box, as shown below. Select alarm filter execution time
and then click OK to complete the operation.
Figure 7-10 Selecting filter alarm time setting

 Deploy filter policy quickly
─ Filter with Same Type: Filter all alarms that are of the same type as the selected alarm.
─ Filter with Same Location: Filter all alarms that are from the same location as the
selected alarm.
214
Raisecom
─ Filter with Same Type and Location: Filter all alarms that are of the same type and in
the same location as the selected alarm.
 Export: Export information of all current alarms
─ Export All Items to Excel File: Export all alarms on the current alarm list to an Excel
(.xls) file
─ Export All Items to Text File: Export all alarms on the current alarm list to a Text (.txt)
file
─ Export Selected Items to Excel File: Export all selected alarms on the current alarm
list to an Excel (.xls) file
─ Export Selected Items to Text File: Export all selected alarms on the current alarm list
to a Text (.txt) file.
─ Export the Current Items to Excel file: Export all the alarms on the current alarm list
to Excel (.xls) file.
─ Export the Current Items to Text file: Export all the alarms on the current alarm list to
Text (.xls) file.
Alarm counter
Apart from displaying current alarms in a list on the Alarm Monitor Pane, NView NNM
system has a current alarm counter as is shown below on the system toolbar. The counter
counts receiving alarms on different levels.
Figure 7-11 Alarm Counter

Six colored buttons form the Alarm Counter. Each color except white corresponds to an alarm
level. The figure on the button indicates the number of current alarm records on the
corresponding level. And the figure on the white button is the total number of current alarm
records.
Click a colored button; only current alarms on the corresponding level will be listed on the
Alarm Monitor Pane. Click the white button, all current alarms will be listed.
The figures shown on the alarm counter will not count in repeated alarm, that is,
alarms of a same type and from a same location will be counted in for only once. The
alarm counter in system toolbar statistic all alarms received by NNM system current,
but the alarm counter in grouped alarm monitor toolbar just statistic the alarms in line
with current grouped monitor rule.
7.3.3 Customized alarm grouped monitoring rules

Customized alarm grouped monitoring rules refers to user creating customized alarm group.
An alarm can belong to several grouped monitoring rules, different groups display alarm
according to the grouped monitoring rules. Customized alarm group can provide different
alarm view without influencing the alarm receiving function of network management system.
Detailed setting of this monitoring rule: click the button at the top-left or right-click the
blank area in "Monitor Rule", system will pop-up a right-key menu, choose Add and click the
dialog of "Edit Monitor Rule", as shown below.
215
Raisecom
Figure 7-12 Editing alarm monitoring Rule

One piece of alarm monitoring rule is in support of the comprehensive setting of alarm source,
alarm properties, customer conditions and share policy.
Alarm source conditions

Alarm source conditions refer to you take grouped monitoring according to alarm source. You
can select content of conditions, as shown in the figure above.
You can comprehensively specify the following conditions:
 Alarm source subnet;
 Alarm source device;
 Alarm source device type;
 Alarm source specified location (chassis and board panel);
 Alarm source name contains specified character
Alarm properties
The alarm properties contain the following conditions setting:
 Alarm name contains specified characters;
 Specified alarm type;
 Specified alarm classification, including equipment alarm, service quality alarm, process
failure alarm, etc;
 Alarm level, including critical alarm, major alarm, prompting alarm, etc;
 Alarm acknowledged by specified person, i.e. the alarm confirmed operation user;
 Alarms with specified alarm status, includes new generation, recovery, and confirmation.
You can select the content of conditions, as shown below:
216
Raisecom
Figure 7-13 Alarm properties
Customer conditions
After configuring NEs associated with the customer, customer conditions will specify the
following conditions to set the equipment associated customer:
 Customer name contains specified characters;
 Circuit ID contains specified characters;
 Specify service impact degree alarm, including three conditions of non-impact, service
deterioration and service interruption.
You can select the content of conditions, as shown below:
217
Raisecom
Figure 7-14 Customer conditions
Share policy
By the time of setting customize monitoring rule, administrator can also set "Share Policy",
that is to assign administrator account to operate the monitoring rules.
Figure 7-15 Share policy
7.3.4 Viewing alarm properties

When you use the view alarm properties function, not only basic information of the alarm, but
related device information, card information (only for alarms from card) and customer
information will be displayed to assist you have a comprehensive view of all related
information. To view properties of an alarm, please double-click a record on the alarm list
(current alarm list or historical alarm list), or select a record, right-click on it and click
Properties on the shortcut menu to open the "Properties" dialog box as is shown below.
218
Raisecom
Figure 7-16 Viewing alarm properties

There are several buttons on the left of the dialog box. They correspond to different groups of
information of the alarm. Click a button, the corresponding group of information will be
shown on the dialog box.
7.3.5 Querying current alarms

NView NNM system provides you with a current alarm management interface "Current
Alarm". You can query current alarms via this interface. Click Alarm > Current Alarm on
the system main menu, the "Current Alarm" panel is displayed, as shown below.
Figure 7-17 Current alarm management

You can query current alarms according to query conditions formed by information of alarm
level, alarm name, service affection, and etc. You can also execute operations like
acknowledge, acknowledge cancelling, clearing, locating, and composite by clicking alarm
219
Raisecom
field, etc. via this interface (for example, clicking "First Report Time" to composite the alarms
by the first report time).
The current alarm list is in support of customized column. Click the button at top-left of
the list to open customized column dialog box, as shown below. Select the Column Name to
display from the list and click OK to display the customized columns information.
Figure 7-18 Customized column_current alarm list
The current alarm renewal function on the "Grouped Alarm" panel is not available in
the "Current Alarm" management interface. You can renew current alarm list
manually by clicking the button Refresh on the bottom right.
7.3.6 Configuring alarm order
Shortcut order
The current and historical alarm list supports order function, click list header (properties field,
for example "First time reported time") to order according to the selected line, i.e. order all
records in database and then show in pages. Press on Ctrl and click list header to order the list
and that is to say just order the data in current list according to selected line.
Alarm line order

To order according to multiple properties fields of alarm records, you can use alarm line order
function to configure more complicate order conditions to current and historical alarm list.
After configuring alarm line order function, open "Alarm grouping monitoring", "Current
alarm query" or "Historical alarm management" interface, the alarm will be ordered in
accordance with the configured order conditions. As shown below, through configuring alarm
line order, alarm records will be ordered in accordance with alarm levels from "emergency" to
"Prompt", and then ordered in accordance with the first time reported time from new to old.
220
Raisecom
Figure 7-19 Ordering alarms

Step 1 Click system menu Alarm > Settings > Alarm Options to open configuration interface, as
shown in step 2. This interface can configure current alarm and historical alarm order through
"Current alarm order" and "Historical alarm order" tab pages. In each tab page, "Unselected
line" shows the alarm properties field can be ordered; "Selected line" shows the configured
order conditions.
Step 2 In "Unselected line", click alarm properties field and then click to add the selected
field to "Selected line" as order condition.
Step 3 In "Selected line", click an order condition and then click Upward or Downward to adjust the
priority of order conditions.
Step 4 In "Selected line", click an order condition and then click Ascending or Descending to
configure the sequence.
Step 5 Click OK to complete the configuration.
The current alarm or historical alarm records in open interface cannot be ordered in
configuring alarm line order; they can be ordered according to the configured order
conditions when open "Alarm grouping monitoring", "Current alarm query" or
"Historical alarm management" interfaces again.
221
Raisecom
Figure 7-20 Configuring alarm order
Table 7-6 Alarm line order interface description

Button Function description
Configure to add order conditions.
In "Unselected line", click a alarm property field and then click
this button to add the selected field to "Selected line" as order
condition.
Configure to reduce order conditions.
In "Selected line", click a alarm property field and then click this
button to remove the selected fields from "Unselected line" as
order conditions.
Upward Configure to increase the priority of order conditions.
In "Selected line", click an order condition and then click this
button to increase the priority of order conditions.
Order conditions are set as order priority from top to bottom, i.e.
order in accordance with the order condition with top location,
and then order in accordance with the order condition with
bottom location.
Downward Configure to reduce the priority of order conditions.
button to reduce the priority of order conditions.
Ascending Configure to order the records in ascending.
button to configure ascending order.
222
Raisecom
Button Function description

Descending Configure to order the records in descending.
button to configure descending order.
OK Save alarm order conditions and close configuration interface.
Cancel Not save alarm order conditions and close configuration
interface.
Apply Save alarm order conditions.
7.3.7 Setting alert sound for alarms

A feature of NView NNM system is to inform network administrator of alarm event
immediately by sound. For alarms on different levels, the system will notify the administrator
by different sounds. The alert sound notification can be enable by clicking the button on
the system toolbar.
The alert sound can be customized. You can set up different sounds for different alarm levels
by following the steps below:
Step 1 Select System > Preference on the system main menu, or click the button on the toolbar,
a "System Settings" dialog box will pop up.
Step 2 Click the button Alarm Settings in the "System Settings" dialog box, the page is displayed,
as shown below.
223
Raisecom
Figure 7-21 Alert sound settings

 One alert sound corresponds to one alarm level. Tick an alarm level, the corresponding
alert sound will be played when an alarm on this level is reported to the system. There
will be no sound notification if the corresponding alarm level is not ticked.
 Click the button on the right, you can select sound files in the format of WAV, MIDI,
or AU as the alert sound of the corresponding alarm level. After the selection, by clicking
the button , you can play and try the selected sound file. After all settings, please
click the button Apply to make the settings effective.
7.3.8 Acknowledging current alarm

An acknowledged alarm is an alarm that has been detected by the administrator and for which
the administrator has acknowledged the alarm event, and sent notification to related engineers
to remove the fault. You can acknowledge a current alarm by following the instructions below:
Step 1 Select the alarm/alarms to be acknowledged in the current alarm list, right-click on the
selected records, and click Acknowledge on the shortcut menu, an "Input" dialog box will
appear.
Step 2 You can enter some log information for the acknowledgement, such as fault notification
information and fault remover, and click OK, the system will start to acknowledge the alarm
event.
Step 3 The alarm status of the alarm event will be modified to "Acknowledged" after the operation.
The acknowledged alarms will also be listed in the current alarm list. After the
acknowledgement, the highest level of alarms may change. The system will inform you of the
change by alert sound and stop playing the alert sound if all alarm events in the current alarm
list have been acknowledged.
224
Raisecom
The change of the status of the alarm is synchronous for all clients connecting to the
same server. That is, acknowledging an alarm in the current alarm list of a client, the
status of the alarm in the current alarm list of the client and all clients connecting to
the same server will change to "Acknowledged".
7.3.9 Confirming alarm cancellation

When you need to change acknowledged alarm to status of "Unacknowledged", following the
below steps:
Step 1 Select one or more pieces of alarm events that are acknowledged from current alarm list, and
click Cancel Acknowledge in the shortcut menu to open related dialog box.
Step 2 Click button OK and system starts operation of cancelling acknowledge the alarm.
Step 3 After successful operation, the selected alarm event changes its status to "Unacknowledged".
The alarm will recover to the status before acknowledgement and acknowledge information
become empty. System plays corresponding alert sound after cancelling acknowledge if the
critical level in current alarm list was changed.
7.3.10 Clearngi a current alarm

A cleared alarm is an alarm for which the corresponding fault has been removed or the
administrator has confirmed that the alarm will not affect the service quality of the current
network. You can clear a current alarm by following the instructions below:
Step 1 Select the alarm/alarms to be cleared on the current alarm list, right-click on the selected
records, and choose Clear operation on the sub menu of the shortcut menu; an "Input" dialog
box will pop up for the input of clearing information. The operations available on the sub
menu are:
 Clear Selection: Clear the selected alarm/alarms
 Clear Alarms With Same Type: Clear the alarm/alarms on the current alarm list that are
of the same type as the selected alarm
 Clear Alarms With Same Location: Clear the alarm/alarms on the current alarm list that
are from the same location as the selected alarm
 Clear All Acknowledged Alarms: Cleared all acknowledged alarm on the current alarm
list
 Clear All: Clear all alarm on the current alarm list
Step 2 You can enter clearing log information, like reason for fault removal, method and result for
fault removal, and etc. This information will be recorded in a troubleshooting knowledge
database for further reference. When similar fault happens, you can query the database by
alarm type and location to make fault removal more quickly and efficiently. Click the button
OK after filling in the log information; the system will start to clear the alarms. The cleared
alarms will disappear from the current alarm list, and be transferred to historical alarm list.
The fault removal information shows as below.
225
Raisecom
Figure 7-22 Fault removal

The fault removal information including:
 Removal person: add the current operation ID that removes alarm by automation;
 Fault removal log: optional item. Description log of fault removal;
 Fault reason: compulsory. Click the reason in the drop-down box, you enter fault reason
and click the button to open edit dialog box for fault reason, as shown below:
226
Raisecom
Figure 7-23 Editing fault reason

Step 3 After filling the text box with fault reason, click the button Add to add fault reason. The fault
reason is editable; but the fault reason being used cannot be erased. The system will pop up
prompt, as shown below.
Figure 7-24 Prompt for undeletable fault

 Description: optional. Description information of fault;
 Fault removal method: optional. Description of removing fault.
Click the button OK and system starts clearing alarm. If operating successfully, the selected
alarm events will disappear from current alarm list and be saved in history alarm by
automation.
Step 4 After the clearing, the alert sound will change if the highest level of alarm changes. The
system will inform you of the change by alert sound and stop playing the alert sound, and
topology node alarm status will change as well.
The change of the status of the alarm is synchronous for all clients connecting to the
same server. That is, clearing an alarm in the current alarm list of a client, the status
of this alarm in the current alarm list of the client and all clients connecting to the
same server will change to "Cleared" and the alarm will be moved from current alarm
list to historical alarm list.
227
Raisecom
7.4 Topology alarm monitoring

7.4.1 Displaying an alarm in the topology view
When system received an alarm event from device, the background of the icon of the device
node will turn to the color used to describe the alarm with the highest alarm level on the
device. In addition, a small icon will appear on the top of the icon of the device if there is
any unacknowledged alarm on the device. When the highest alarm level of all devices in a
subnet changes as the alarm status of one device changing, the alarm status of the subnet will
change as well. The change of the alarm status will be reported upwards level by level to the
subnet on the up-most level. Please note that acknowledging and clearing operations will also
affect the highest level alarm status of the topology node and subnet.
7.4.2 Locating an alarm in the topology

The NView NNM system provides a "Locate in Topo" function, by which you can locate the
device in the network from which the alarm event comes from. Select an alarm event on the
current alarm list or historical alarm list, right-click on the selected item, and click Locate in
Topo on the shortcut menu, the topology view of the device or the card will be opened and the
device node from which the alarm event comes from will be selected.
7.4.3 Locating alarm device

Alarm device location is in support of opening the corresponding alarm device NE manager
and locating to the corresponding position on the device panel. Device location function is
effective to the alarms from the equipment box, panel and port (requiring specific failure
source position information for location), otherwise this function is invalid.
NView NNM is in support of power supply alarm, fan alarm and other abundant alarm types
mapping to related NE and locating alarming device direct through "Device Locate" function.
Select an alarm event in the alarm event list (current alarm or historical alarm), right-click and
select Locate in Device in the shortcut menu, the system will automatically open the
corresponding alarm device element manager.
7.4.4 Viewing node alarm

Select a device node on the topology view, right-click on the selected node and click Alarm
Management > Alarm View on the shortcut menu, a "View Events" dialog box is displayed,
as shown below.
228
Raisecom
Figure 7-25 Viewing events

All current alarm events from the selected device node will be displayed in the "Current
Alarm" list. You can acknowledge, cancel acknowledge or clear an alarm on the list.
Click the button Historical Alarm, all historical alarm events of the selected alarm node can
be viewed here.
7.5 Device alarm monitoring

7.5.1 Displaying a device alarm
In the interface of element management system of the device, there is a current alarm list
occupied the lower part of the interface and all current alarm events from the device are listed
there. You can acknowledge and clear an alarm event via the list. The alarm will also be
displayed on the picture of the chassis pane. For example, the card may decorated by icon
to assist the administrator locate the fault.
229
Raisecom
Figure 7-26 Displaying a device alarm

The displaying pattern of alarms from card may be different in different EMS. The interface
shown above is just an example.
7.5.2 Device alarm operation

You can execute the following operations on the current alarm events:
 Acknowledge: Acknowledge selected current alarm event/events
 Alarm clearing: Clear selected alarm; clear alarms of the same type as the selected alarm
or alarm from the same location as the selected alarm; clear all acknowledged alarm;
clear all alarms in the alarm list.
 Set up alarm filter rules: Select an alarm and set up alarm filter rules for the selected
alarm and alarms of the same type or from the same location.
 Export alarm information: Export alarm information in the alarm list to an Excel file or a
Text file.
All the above operations are executed by select the corresponding items on the right-click
menu of the current alarm list.
7.6 Alarm list query

In alarm grouping monitoring, topology alarm monitoring and device alarm monitoring, the
alarms are displayed in the interface in the form of list. Alarm list query function can locate
alarm accurately and quickly.
The alarms list query has the following features:
 The line shown in all list can be used as query condition and the query conditions can be
combined in accordance with "Logical and" or "Logical or" mode.
 Query condition can be customized, default to display the common query conditions.
Different user has different customized condition.
 The lines in list can also be customized, default to display the common lines. Different
user has different customized line.
230
Raisecom
 The query condition panel can be popped up and displayed in form of dialog box, which
can expand the list display region to display more information. The operation method to
pop up query condition panel is click Pop-up button on the right of query panel.
 The query panel can be open/close, which can expand the list display area to display
more information. The operation method to open/close query panel is click Open query
or Close query in tool bar on top of the list.
7.6.1 Customizing query conditions

Alarm list query can take all lines as query condition, and also allow you to customize query
condition. Use this feature, you can retain the most common query condition, and not to
display the unused condition.
Step 1 Click Customize condition on the right side of the query panel to pop up "Customize query
condition" dialog box, as shown below. The dialog box lists all available query lines and lines
description.
Figure 7-27 Customizing query conditions

Step 2 Select the required lines, click OK to close the dialog box. It only retains the selected lines as
query conditions in query panel.
Step 3 (Optional) click Save and OK to open this form again, the selected query conditions will be
retained.
Step 4 (Optional) if restore to the system default settings, click Restore Default.
231
Raisecom
Step 5 (Optional) if to adjust the query conditions order in query panel, you just need to select some
line in list, click or on the left corner of dialog box to adjust the selected line
order in list, then click Save and OK.
Customizing display contents

Alarm list query provides to display line customized function, by which you can only allow
the most commonly used properties and display order to show in list; the commonly unused
properties can be hidden.
Step 1 Click on the left top of list to pop up "Customize table line" form, this dialog box lists all
available display lines and lines description.
Figure 7-28 Customizing display contents

Step 2 Select the required lines, click OK to close the dialog box. It only retains the selected lines in
list.
Step 3 (Optional) click Save and OK to open this form again, the selected lines will be retained.
Step 4 (Optional) if restore to the system default settings, click Restore Default.
Step 5 (Optional) if to adjust the lines order in list, you just need to select some line in list, click
or on the left corner of dialog box to adjust the selected line order in list, then
click Save and OK.
232
Raisecom
The alarm list query supports order function, click list header to order according to the
selected line, default to take database order, i.e. order all records in database and
then show in pages. Press on Ctrl and click list header to order the list and that is to
say just order the data in current list according to selected line.
Saving query conditions

The alarm list query provides "Bookmark" function to save the commonly used query
conditions. You just need to open the corresponding bookmark to take same condition query
but not needs to enter fussy condition.
Step 1 Open query panel in alarm list, click Bookmark on the right operation list.
Figure 7-29 Bookmark in alarm list query panel

Step 2 Click Add to Bookmark to pop up bookmark naming dialog box, enter bookmark name and
click Save to save the bookmark to system.
Step 3 Click Manage Bookmark to delete or rename the saved bookmark.
233
Raisecom
Figure 7-30 Managing a bookmark

Step 4 To use bookmark, you just need to click Bookmark in tool bar in the corresponding general
query component, it will show all the saved bookmarks in the drop-down menu. Select the
required bookmark, the query condition will list in query panel automatically and query the
corresponding result.
Figure 7-31 Selecting a bookmark
7.7 Current alarm filter

NView NNM system provides alarm filtering function by which system is able to filter
current alarm events of one type or from one device, chassis, card or port. Filtered alarms will
not be displayed in the interface. You decide whether saving the filtered alarms as historical
alarms or not.
234
Raisecom
The above filter rules may have "equivalent filter rules". That is, in some
circumstances, defining filter rule for a card is equivalent to defining a rule for the
chassis to which the card belongs. Equivalent filter rules are allowed by the system;
however, to restart the receiving of a filtered alarm, you must find out all equivalent
filter rules and delete them in advance.
7.7.1 Alarm filter rules

NView NNM system provides you with the following alarm filter rules to assist you set up
different filtering conditions:
 Trap Filter: filter alarm events that are of specified types.
 Device Filter: filter alarm events that are of specified types and from specified device.
 Chassis Filter: filter alarm events that are of specified types and from specified chassis.
 Card Filter: filter alarm events that are of specified types and from specified card.
 Port Filter: filter alarm events that are of specified types and from specified port.
 Alarm Level Filter: filter alarm events that are of specified alarm level.
 Alarm time segment filter rule: filter alarm events with specified alarm time segment.
Click Alarm > Alarm Filter Rule on the system main menu, an "Alarm Filter Rule"
window will turn up.
Figure 7-32 Alarm filter rules

Click the left filter rule to switch between various alarm filter rules. The right side will show
the alarm rule created filter rule. Alarm rule interface description is shown as below.
 Name: name of device type, alarm type or alarm source
 Description: the name represented object description
 Enable: checked indicates that the filter rule is valid; only when the filter rule is enabled,
the system can filter the alarm event complying with filter rule.
235
Raisecom
 Saved to history database: whether to save the alarm events complying with the filter
rule or not. If select this option, the system will save them as historical alarm once
receiving alarm events complying with the filter rule, or the system will discard these
alarm events.
 Delete: delete the selected alarm filter rule. "Alarm level" filter rule does not support
delete function.
There are two options in the bottom of the filter rules add interface, their features are
as follows:
 Enable filter rule: whether the added filter rule is valid, checked by default,
indicates take alarm filter according to this rule after adding. If not check this
option, the rule will be invalid.
 Auto-clear (saved to history database): whether to save the filtered alarms to
history database, not check by default, indicates to discard the filtered alarms
directly. If check this option, the filtered alarms will not be shown in current alarm,
but only saved to history alarms database.
7.7.2 Deploying alarm type filter rules

You can filter all alarm events of one certain alarm type by following the instructions below:
Step 1 Click the button Add on the toolbar of the "Trap Filter" page, an "Add Filter Rule" dialog
box will pop up.
Step 2 Tick the alarm types to be filtered in the "Add Filter Rule" dialog box. Click the button OK
after selection to start the "Add Filter Rule" operation. Corresponding record of the operation
will be displayed on the "Alarm Filter Rule" window.
236
Raisecom
Figure 7-33 Adding filter rules
Step 3 If a filter rule is no longer in need, you can click the button on the same row of the filter
rule to delete it. You can also disable a filter rule by modifying the enable status of the filter
rule.
After modifying the enable status of a filter rule, please click the button Save on the
toolbar to save the settings, otherwise the modification will not be processed.
7.7.3 Deploying device filter rules

You can filter the alarm events that are of a specified type and from a specified device by
following the instructions below:
Step 1 Click the button Add on the toolbar of the "Device Filter" page; an "Add Filter Rule" dialog
box will pop up.
Step 2 The upper half of the dialog box is a device list. You can search for a device or several devices
by query, and tick their "Select" checkboxes. After the selection of devices, please select the
alarm types to be filtered on the alarm type list beneath the device list. By default, all alarm
types will be filtered. Uncheck the checkbox for "All Alarm Types", and the alarm types that
are supported by the selected devices will be listed. Please see the figure below:
237
Raisecom
Figure 7-34 Adding device filter rule

Step 3 After all selection, please click OK to complete the filter rule setup. The corresponding filter
rule will appear in the "Alarm Filter Rule" window.
7.7.4 Deploying chassis filter rules

You can filter the alarm events that are of a specified type and from a specified chassis by
Step 1 Click the button Add on the toolbar of the "Chassis Filter" page; an "Add Filter Rule" dialog
box will pop up.
Step 2 The upper half of the dialog box is a chassis list. You can search for a chassis or several
chassis by query, and tick their "Select" checkboxes. After the selection of chassis, please
select the alarm types to be filtered on the alarm type list beneath the chassis list. By default,
all alarm types will be filtered. Uncheck the checkbox for "All Alarm Types", and the alarm
types that are supported by the selected chassis will be listed. Please see the figure below:
238
Raisecom
Figure 7-35 Adding chassis filter rules

7.7.5 Deploying card filter rules

You can filter the alarm events that are of a specified type and from a specified card by
Step 1 Click the button Add on the toolbar of the "Card Filter" page; an "Add Filter Rule" dialog
box will pop up.
Step 2 The upper half of the dialog box is a card list. You can search for a card or several cards by
query, and tick their "Select" checkboxes. After the selection of card, please select the alarm
types to be filtered on the alarm type list beneath the card list. By default, all alarm types will
be filtered. Uncheck the checkbox for "All Alarm Types", and the alarm types that are
supported by the selected cards will be listed. Please see the figure below:
239
Raisecom
Figure 7-36 Adding card filter rules

7.7.6 Deploying port filter rules

You can filter the alarm events that are of a specified type and from a specified port by
Step 1 Click the button Add on the toolbar of the "Port Filter" page; an "Add Filter Rule" dialog
box will pop up.
Step 2 The upper half of the dialog box is a port list. You can search for a port or several ports by
query, and tick their "Select" checkboxes. After the selection of port, please select the alarm
types to be filtered on the alarm type list beneath the port list. By default, all alarm types will
be filtered. Uncheck the checkbox for "All Alarm Types", and the alarm types that are
supported by the selected ports will be listed. Please see the figure below:
240
Raisecom
Figure 7-37 Adding port filter rules

7.7.7 Deploying alarm level filter rules

You can filter the alarm events that are of a specified level by following operations:
Step 1 In alarm level filter rule view, each alarm level shows one piece of record.
Step 2 In "Enable" field on the right side of records, click checked to enable this level alarm filter; not
check indicates not to filter this level alarm, default not check.
Step 3 In "Saved to history database" field on the right side of records, click checked to save this
level alarm filter directly to history alarm database and not display in current alarm, default to
check; not check indicates to discard the filtered alarm directly.
Step 4 Click Save. The modified configuration will not take effect if not to save; click Refresh to
show the saved filter configuration last time.
241
Raisecom
Figure 7-38 Adding alarm level filter rules
7.7.8 Deploying alarm time segment filter rules

You can filter the alarm event of some NE in some time according to the following operations:
Step 1 In alarm period filter rule view, click Add on top of tool bar to pop up Add Filter Rule dialog
box.
Step 2 Select the rule mode to deploy on top of the dialog box: all object or custom object.
Figure 7-39 Deploying rule mode

 If select all objects, you can click Next to enter "Step 3"directly.
242
Raisecom
 If select custom object, you can click to select a classify in the drop-down list box on the
left of the interface, and select filter policy application object in the pop-up interface,
then click Next to enter "Step 3".
─ To select "NE" or "Card", in the pop-up interface, select NView NNM NE or card
record, and then click OK.
─ To select "NE type" or "Card type", in the pop-up interface, select device type and
then click OK.
Figure 7-40 Selecting filter rule application object
It can only show less than 10 pieces of records in the "Selected alarm source"; if it
exceeds 10 pieces of records, it will pop up Prompt dialog box to prompt error.
Step 3 Pop up filter alarm time setting dialog box, as shown below. Select alarm filter execution time
243
Raisecom
Figure 7-41 Selecting filter alarm time setting
7.7.9 Deploying filter rules quickly

To assist you filtering some alarm events quickly and simply, NView NNM system provides
filter rule quick deployment function. You can perform the function by following the
instructions below:
Select an alarm or alarms on the current alarm list, right-click on the selected items, and click
Filter Setup on the shortcut menu. Four sub menu items are available:.
 Select Filter With Same Level, the alarm filter rule that will filter all alarm events that
are of the same level as the selected alarm will be added to the filter rule.
 Select Filter With Same Type, the alarm filter rule that will filter all alarm events that
are of the same type as the selected alarm will be added to the filter rule.
 Select Filter With Same Location, the alarm filter rule that will filter all alarm events
that are from the same location as the selected alarm will be added to the filter rule.
 Select Filter With Same Type and Location, the alarm filter rule that will filter all
alarm event that are of the same type and on the same location as the selected alarm will
be added to the filter rule.
After the above settings, the newly added filter rule will be displayed in the "Add Filter
Rule" window.
7.7.10 Searching filter rules

NView NNM system searches filter rule using the name of the alarm or alarm source. System
will search for all filter rules of the device type, alarm type, device, chassis, card, and port
whose name contains the keyword.
In practice, you can search filter rules by following the instructions below:
244
Raisecom
Searching in some one filter rule

Open the "Alarm Filter Rule" window, enter the keyword on the toolbar, and click the button
, system will search for records that contain the keyword in their names. Matched records
will be highlighted one by one as you press the button .
Searching in all filter rules

Click the button Search on the toolbar of the "Alarm Filter Rule" window, a "Search Filter
Rules" dialog box will pop up. Enter the keyword and click the button Search on the right,
system will begin to search for the filter rules whose name contain the keyword.
If no filter rule satisfies the search condition, "No filter rules match the condition" will be
shown on the right of the Search button. If filter rules that satisfy the condition exists, they
will be displayed in a list in the "Search Filter Rules" dialog box, and the number of filter
rules that satisfy the search condition will be displayed on the right of the button Search as
"The amount of the filter rules match the condition: x". The "Search Filter Rules" is as
shown below.
You can modify and delete filter rules in this dialog box. Please click the button Apply after
modification to validate the renewal.
245
Raisecom
Figure 7-42 Searching filter rules
7.8 Alarm reversal

For ports not open the service, the alarm reversal is used to avoid generating related alarm
information and avoid alarm interference. To configure alarm reversal function to make the
port alarm status opposite with the actual status, i.e. if there is alarm actually, it will not report
alarm; if there is no alarm actually, and it will report alarm.
7.8.1 Alarm reversal mode

Alarm reversal has three modes: non-reversal mode, automatic recovery mode, manual
recovery mode.
 Non-reversal mode: the normal alarm monitoring status, default for this mode. In this
mode, to configure port alarm reversal enable will not take effect.
 Auto-recovery mode: In this mode, you can only set alarm reversal to current alarm ports.
Set to enable and enter reversal mode, this port will not report alarm. If the current alarm
is end, the system will exit the reversal mode automatically and the port reported alarm
status will recover to the actual alarm status.
 Manual recovery mode: In this mode, regardless of whether the current port has alarm,
you can set alarm reversal to this port. To enable this mode, the port reported alarm
status will be opposite to the actual alarm status. To disable this mode, the port reported
alarm status will be consistent with the actual alarm status.
246
Raisecom
If the NE alarm mode changes, then the ports will check whether the port alarm reversal
setting is legal in accordance with the actual alarm status, if not legal, change to legal status.
For example, set "Manual recovery mode/Port alarm reversal enable" to auto-recovery mode,
but the port has not the highest level alarm, then the alarm reversal function of this port
cannot disable automatically.
Table 7-7 Port alarm reversal configuration

Reversal mode There are highest level There are no highest level
alarms in actually alarms in actually
Non-reversal Enable Disable Enable Disable
mode
Auto-recovery Enable Disable Enable Disable
mode (illegal
configuration)
Manual recovery Enable Disable Enable Disable
mode
 Alarm reversal is set for the physical port.

 By default, the NE is auto-recovery mode; the unused port alarm reversal enables.
 Currently, alarm reversal only supports the transmission line RC002 new version
NMS disk, OPCOM3500E B version.
7.8.2 Configuring alarm reversal

Alarm reversal is mainly configured for port, at the same time, you can configure the NE
alarm reversal mode.
Step 1 Click system main menu Alarm > Settings > Alarm Inverse to pop up alarms reversal batch
configuration interface, select "Reversal configuration" tab.
Step 2 The left side of interface shows NE supporting alarm reversal, click to select a NE and then
click Synchro to make the network management information consistent with device
information.
Step 3 In the right side of the interface, set alarm reversal function to interfaces on device chassis
card, at the same time, configure NE alarm reversal mode.
Step 4 Click Apply to issue the configuration.
247
Raisecom
7.8.3 Configuring alarm reversal mode in batch

To configure alarm reversal mode in batch is easy for you to configure alarm reversal function.
Step 1 Click system main menu Alarm > Settings > Alarm Inverse to pop up alarms reversal batch
configuration interface, select "Reversal configuration" tab.
Step 2 Click Sync to make the network management information consistent with device information.
Step 3 Select one or more lines of NE information, and select reversal mode in "Configure reversal
mode in batch", then click Apply to issue the configuration.
Step 4 (Optional) click Default value to recover all NEs to defaulted reversal mode, i.e. "Auto-
recovery".
Step 5 (Optional) select one line information, in "Reversal mode" list drop-down list box, select a
kind of reversal mode, click Apply to configure the alarm reversal mode of one separate NE.
The method to select multiple records:

 Hold down the left mouse button and drag to select multiple records.
 Press on Ctrl and click to select multiple records.
248
Raisecom
Figure 7-43 Configuring alarm reversal mode in batch
Table 7-8 Configuration parameter description

Parameters Value Function description
 Manual recovery
Configure reversal Configure NE alarm reversal
 Auto-recovery
mode in batch mode in batch.
 Non-reversal
7.9 Trap notification

NView NNM can inform the administrator of the alarm event via E-mail or SMS. This trap
notification function ensures that the administrator will not miss any important network fault
information, even if no one is on watch in the equipment room. You can also have information
from different types of alarm events sent to different administrator by setting up trap
notification rules to ensure efficient network fault management.
7.9.1 Setting SMS trap notification service

To have alarm events notified via SMS, you must make sure in advance that the system is able
to sent short message. However, NView NNM do not have SMS message sending function,
all SMS message sending depends on the GSM (Global System for Mobile Communication)
modem connecting to the host on which the NView NNM system locates. To have alarm
events notified via SMS, the following conditions should be satisfied:
Make sure that the SMS modem is connecting to the host on which the NView NNM system
locates properly. The SMS modem here should be a SMS message sending device that is in
support of AT standard instructions.
249
Raisecom
Make sure that the parameters of the SMS modem are correctly set. After setting up the
connecting parameters for SMS modem, click Service > System Service at the system menu
bar and then start Alarm SMS Relay Service. (For detailed information, see section 11.5.4
Alarm SMS relay service.) If all parameters have been correctly set and the device is at
running status, the trap notification service will be start and the connection between the server
and the SMS modem will be set up. If the connection cannot be set up successfully, please
check the setting of related parameters and the running status of the device before start the
service again.
7.9.2 Setting E-mail trap notification service

To have alarm events be notified by E-mail, you must ensure that NView NNM is able to send
E-mail. However, NView NNM has no E-mail sending function itself. NView NNM system
sends an E-mail by transferring the E-mail to SMTP server, and having the SMTP server send
the E-mail to the E-mail account of the administrator.
NView NNM system provides "Alarm Mail Relay Service" to realize trap auto-notification
via E-mail. See section 11.5.3 Alarm mail relay service for instructions. After setting up all
service parameters correctly, click Service > System Service at the system menu bar and then
start Alarm Mail Relay Service. .
7.9.3 Setting trap notification rules

Setting up a trap notification rule is setting up the receiver and sending channel of the
information from a certain type of alarm event. You can add a trap notification rule by
Step 1 Select Alarm > Trap Notification on the system main menu to open the "Trap Notification"
window.
Step 2 Right-click on the blank area of the "Trap Notification" window, and click Add on the
shortcut menu, an "Add" dialog box will pop up:
Figure 7-44 Adding notification target

Step 3 You can enter target E-mail address or mobile device number in the dialog box. To enable the
trap notification, you should tick the corresponding item "Mail Notify" or "SMS Notify" on
the right. Click the button OK, a record will appear in the list on "Trap Notification" window.
Step 4 After adding a new notification target, an alarm event should be related to the notification
target, or the target cannot receive any information from alarm event. Select the notification
target on the list in the "Trap Notification" window, right-click on the selected item, and click
Edit on the shortcut menu, an "Edit" dialog box will pop up:
250
Raisecom
Figure 7-45 Editing Trap notification

All IP address ranges that have been added will be listed in "Trap Range". If the IP address of
the device from which the new alarm event comes is in these IP address ranges, the
notification of the alarm event will be sent to the target address.
Step 5 Click the button Add on the right of the "Edit" dialog box, a dialog box for adding trap will
pop up:
Figure 7-46 Adding Trap notification conditions

The IP address of the source host from which the alarm event comes from is required in this
dialog box. You can fill in the IP address in one of the following format:
 A full IP address such as 192.168.1.254
251
Raisecom
 IP address with wildcard "*" like 192.168.1.* or 192.*.*.*. When using one "*" to
represent the whole IP address, there will be no limit for the IP address of the source host.
 IP address with separator "/" such as 192.168.1.100/192.168.1.180. This format specifies
a range of IP address.
You can specify an alarm level in this dialog box to indicate the alarm level that you concern
more among the alarms from a certain source.
Step 6 After all settings, click the button OK to save the settings and close the "Add" dialog box. The
newly added record will appear on the trap range list.
You can also edit or delete a trap range record in the "Edit" dialog box.
7.10 Historical alarm management

7.10.1 Querying historical alarms
Click Alarm > Historical Alarm on the system main menu, the "Historical Alarm" window
is displayed, as shown below.
Figure 7-47 Historical alarm management

The "Historical Alarm" window displays all historical alarms in a list and provides powerful
query function by which you can query historical alarms using query conditions combined by
information of alarm level, alarm name, service affection, alarm cost time (alarm restore time)
and etc.. You can also delete, export or locate a query result.
7.10.2 Deleting historical alarms

You can delete historical alarm record/records in the historical alarm list:
 Delete Selection: delete the selected historical alarm event/events
 Delete Query Result: delete all historical alarm events obtained from the current query
operation
252
Raisecom
 Delete All: delete all historical alarm events.

Click one of the three buttons for deleting historical alarm on the toolbar, or select the
corresponding item on the sub menu of Delete on the right-mouse-button shortcut menu of
selected items, you can execute delete operation.
7.11 Trap definition management

7.11.1 Querying Trap definition
Click Alarm > Trap Definition on the system main menu, the "Trap Definition" window is
displayed, as shown below.
Figure 7-48 Trap definition list

The "Trap Definition" window displays all trap definitions in a list and provides query
function. You can set up alarm level, edit, delete, export, and view properties of a selected
item on the list through the right-mouse-button shortcut menu.
7.11.2 Redefining alarm level

You can modify the alarm level of an alarm type in either of the two following operations:
 Select record/records on the trap definition list, right-click on the selected records, and
select an alarm level on the sub menu of Alarm Level. The alarm level of the selected
alarm type/types will be renewed after the operation.
 Select a record on the trap definition list, right-click on the selected record and select
Edit on the shortcut menu, an "Edit" dialog box will pop up:
253
Raisecom
Figure 7-49 Modifying alarm level

Select an alarm level on the drop-down list of the item "Alarm Level", and click the button
OK to save the setting. The alarm level of the selected type of alarm will be renewed after the
operation.
After the modification of the alarm level of a certain type of alarm, the newly-received
alarms of this type will be reported as alarms of the new alarm level. The alarm level
of the alarms that belong to this type or historical alarms level will not be changed.
7.11.3 Deleting trap definition

Select a record/records on the trap definition list, right-click on the selected records; click
Delete on the shortcut menu, a confirm box will pop up. Click Yes; the selected records will
be deleted.
Please be cautious of the deletion operation. A fault operation may lead to alarm
information loss because the fault information from the type of alarm will not be able
to reach the system any more after the deletion. NView NNM network management
system is not in support of you creation alarm type, so the deleted alarm type will not
be recovered.
7.12 Troubleshooting knowledge management

7.12.1 Troubleshooting knowledge management
System provides a troubleshooting knowledge database which collects and manages various
troubleshooting strategies for further reference. The database helps you obtain a suitable
resolution in limited time when a fault occurs and hence greatly improve troubleshooting
254
Raisecom
strategy. The database is empty when the NView NNM system is firstly installed. The
database is built up as the knowledge of troubleshooting being gradually recorded in during
daily fault removal process.
Click Alarm > Troubleshooting in the system main menu, the "Troubleshooting" window
will turn up. Please see the figure below.
Figure 7-50 "Troubleshooting" Window

Troubleshooting information will be displayed on the interface in a list. You can query in the
list using some query conditions, and can add, edit, and delete a record in the list from the
right-click menu of the record. You can also view the properties of a record or export the list
or part of the list to EXCEL or TXT file. Each piece of troubleshooting knowledge may
contain the following information:
 Fault reason: manually enter, the cause of the fault
 Solution: manually enter, the resolution of the fault
 Recording time: the time when this piece of troubleshooting knowledge is being
recorded
 Staff: the person that records the troubleshooting knowledge
 Fault related alarms: an alarm list that records the alarm information related to the fault,
which is built up for further reference
7.12.2 Troubleshooting knowledge input

The NView NNM system provides three troubleshooting knowledge input methods:
Inputting the troubleshooting knowledge when clearing current alarms

When clear a current alarm, a dialog box for the input of alarm clearing log will turn up, and
you can input some troubleshooting knowledge in this dialog box.
255
Raisecom
Figure 7-51 Inputting Clearing Log

The "Fault Reason" and "Solution or Result" input here form a piece of troubleshooting
knowledge. No troubleshooting knowledge will be recorded if the "Fault Reason" and
"Solution or Result" are left blank.
Creating troubleshooting knowledge in the historical alarm list

Cleared alarms will be moved from the current alarm list to the historical alarm list. You can
input troubleshooting information for historical alarms in the historical alarm list. Select a
record or several records of historical alarms in the historical alarm list and click Query
Troubleshooting > Add Troubleshooting on the right-click menu of the selected records, an
"Add Troubleshooting" dialog box will pop up.
256
Raisecom
Figure 7-52 Creating troubleshooting knowledge

Input "Fault Reason" and "Solution" in this dialog box and press OK, a piece of
troubleshooting knowledge will be recorded.
Adding troubleshooting knowledge in the troubleshooting knowledge

management component
Click Alarm > Troubleshooting in the system main menu, the "Troubleshooting" page will
turn up and the troubleshooting knowledge list will be shown on the page. Click Add on the
right-click menu of a record, an "Add Troubleshooting" dialog box as shown above will pop
up. Input the "Fault Reason" and "Solution", select related historical alarms and click OK to
save the input, then a new troubleshooting knowledge will be generated and displayed on the
troubleshooting knowledge list.
7.12.3 Querying troubleshooting knowledge

NView NNM system provides three methods for troubleshooting knowledge query:
Querying related troubleshooting knowledge in alarm property panel

Right-click a record on an alarm list and click Properties on the right-click menu, a
"Properties" window will pop up, and there is a "Troubleshooting" page that displays all
troubleshooting knowledge related to the alarm.
257
Raisecom
Figure 7-53 "Troubleshooting" page in the "properties" dialog box

When the troubleshooting knowledge database is rich, query function is necessary to make the
searching for related troubleshooting knowledge easier. Input the "Key Word" for query, and
click Query, related troubleshooting knowledge will be displayed on the page. The "Key
Word" can be description, solution, and etc.
Querying troubleshooting knowledge in alarm lists

You can query the troubleshooting of an alarm in the following modes:
 In the current alarm list, right-click a piece of information and then click Query
Troubleshooting.
 In the historical alarm list, right-click a piece of information and then click Query
Troubleshooting > With Same Alarm Type.
Querying in the "Troubleshooting" management component

Click Alarm > Troubleshooting in the system main menu, the "Troubleshooting" window
will turn up. Click Show Query, a query panel will appear. Please set up a condition or a
combination of several conditions for query, the system will search for the troubleshooting
knowledge that satisfies the conditions.
7.13 Alarm Statistics

NView NNM system provides an alarm statistics function, which counts the number of alarms
on different criticality levels and helps you collect the information of alarm distribution.
258
Raisecom
7.13.1 Current alarm statistics

The current alarm statistics function provided by the system counts the number of current
alarms on different criticality levels for different NE.
Step 1 Click Report > Current Alarm Statistic on the system main menu. A "Current Alarm
Statistic" window will turn up.
Step 2 Select the target subnet in the "Subnet" drop-down menu, and click Statistic, the system will
give the result of the current alarm statistic calculated based on the information of the selected
subnet.
Figure 7-54 Current alarm statistics

 Click Graph, the displaying pattern of the result will switch between list and histogram.
7.13.2 Historical alarm statistics

The historical alarm statistics function provided by the system counts the number of historical
alarms on different criticality levels for different NE.
Step 1 Click Report > Historical Alarm Statistic on the system main menu. A "Historical Alarm
Statistic" window will turn up.
Step 2 Select the target subnet in the "Subnet" drop-down menu, and click Statistic, the system will
give the result of the current alarm statistic calculated based on the information of the selected
subnet.
259
Raisecom
Figure 7-55 Historical alarm statistics

 Click Graph, the displaying pattern of the result will switch between list and histogram.
260
Raisecom
NView NNM Operation Guide 8 Inventory management
8 Inventory management
This chapter mainly introduces the related definition and operation concerning inventory
management and how to manage inventory using NView NNM system, including the
following sections:
 Overview
 Main interface of inventory information
 Inventory information classification
 Inventory information collection
 Physical inventory management
 Inventory types
 Address book management
 Exporting inventory information
 Inventory information statistics
8.1 Overview
During network management process, the maintenance staffs need to manage inventory
information in order to master network running status and help future network enlargement
and new service project. But the numerous inventory information and classification is very
difficult to manage, and it is hard to locate NE related physical location and logic resource
correctly and quickly when there is fault.
NView NNM system provides inventory management function for network maintenance to
help maintaining staff master physical resource and logic resource inventory information clear
and quickly. The inventory management is mainly used in following conditions:
 At initial stage of network building, automatic collection and manual input can build
association among inventory information to satisfy resource management of inventory
information.
 It is convenient to query and manage inventory information during maintenance working
and satisfy daily management.
 When there is fault in network, searching inventory information can locating physical
device, network topology, logic resource, related customer and maintenance staff contact
information to satisfy quick repair demands for network fault.
261
Raisecom
8.1.1 Function features

Inventory management is in support of below features:
 Physical inventory management, including rack, NE, chassis, slot, local card, remote
device, ONU, CNU and port.
 Directory of maintenance staff, the contact information in directory can be selected and
associated by other inventory information.
 View inventory type.
 Automatic collection of inventory information of NE, chassis, slot, local card, remote
device, ONU, port and VLAN.
 Directory management, the information in directory can be selected by inventory
information to associate inventory information with maintenance staff contacts.
 In support of building association among inventory information.
 Easy to query inventory information.
 Export inventory information record.
Three functions are provided by NView NNM inventory management:
 Collect inventory information by automation or manual inputting
 Manage and maintain inventory information
 Inventory information statistics
8.1.2 Collect inventory information by automation

 During topology deployment, system will automatic collect inventory information from
automatic detection or manual added device.
 When managed device is changed, you can enable synchronization command to keep
system maintained inventory information in line with device current information.
 By device polling function, NMS can execute synchronization command in period to
keep device information in line with system maintained inventory information.
8.1.3 Collect inventory information by manual inputting

 You input inventory information by manual, like rack inventory information, records in
directory.
 Choose rack and information from directory to build association with other inventory
information.
Inventory information management indicates NView NNM provides flexible Query, Modify,
Delete, etc. functions. You can customize query condition, customize content and edit
information displayed in inventory information list.
8.1.4 Inventory information statistics

Inventory information statistics indicates functions of statistic different device types, cards
number and slot vacancy rate according to subnet/area and help to understand distribution of
network devices.
Besides, inventory management module is compact integrated with Topology management,
Alarm management and NE management modules, you can locate topology resource and
262
Raisecom
query device related event (like alarm, associated customer information), etc. very
conveniently.
8.2 Main interface of inventory information

Click Inventory > Physical in system main menu, then double click "NE" in the resource tree
to open inventory management interface of NE device, as figure shows below.
On the left of interface, it is inventory classification tree; on the right, it includes menu,
buttons in tool bar and list to display inventory information. The menu and buttons in this
interface are of identical function with right-key menu items. From left to right, the buttons in
tool bar are: Query, Modify, Attribute, Delete, Refresh, Export, Topology position, NE
management, Alarm management, Resource, Associated customer. The button name will
appear when you move cursor onto the button. Page size function can adjust pages for listing
inventory information.
Figure 8-1 NE inventory management
Though inventory management menu, buttons in tool bar and right-key menu can
execute identical operations, different classification may support different operations.
For example, rack classification has function of add, for you enter information by
manual, but NE, chassis, etc. classification collect information by automation and
does not have function of adding.
263
Raisecom
8.3 Inventory information classification

Inventory management modules are used to manage and maintain the network inventory
information in classification. The inventory information can be divided into physical
inventory and logical inventory. These two big categories can also be divided into many small
categories according to network management work features.
8.3.1 Physical inventory

Physical inventory is the actual existing physical devices in network. For NE and chassis,
NView NNM system is in support of collecting inventory information by automation as well
as synchronizes the physical inventory information. You have to maintain inventory
information of rack (the device cannot connect to NMS) by manual.
Classification of physical inventory:
 Rack: the rack in library, network devices can be put on the rack.
 NE: management object of Agent, with independent management IP address, can be
managed direct or indirect through SNMP protocol.
 Chassis: chassis for modular devices.
 Slot: chassis slot for modular devices.
 Local card: modular device inside chassis.
 Remote device: remote devices (do not include ONU) corresponding to local card, in
NView NNM, all client devices are saved in card format.
 ONU: remote device of EPON.
 CNU: remote device of EoC.
 Port: all service ports provided in device, including Ethernet port, PDH port and SDH
port, etc.
8.3.2 Directory
Inventory management also supports record contacts of maintenance staff and responsible
people in directory; you can associate the contacts with inventory information.
8.4 Inventory information collection

8.4.1 Collect by automation
Automatic collection indicates system collects all inventory information besides project
property, extension property, maintenance staff information, etc. and relationship among the
information by automation. You can associate inventory information with customer
information, or maintain project property, extension property and maintenance staff
information by manual. Now the followed inventory classes can be collected by automation:
NE, Chassis, Slot, Local card, Remote device, ONU and port.
Automatic collection of inventory information does not need user's operation, system can
operate by automation in following conditions:
 After you successfully adding a NE by manual;
264
Raisecom
 Finding a new node during auto-detection process;

 You execute synchronize command for one or several NE through NMS client.
System can startup resource information automatic collection if only one of the above three
condition is satisfied.
NView NNM gets resource information from device via SNMP, so the premise for
automatic collecting inventory information is to set correct SNMP parameter in NView
NNM system and ensure the system can connect and access device. Otherwise,
automatic collection cannot get any resource information.
8.4.2 Input by manual

You have to add and maintain inventory information that cannot be collected by automation.
For example, the input and maintain of inventory for rack and directory requires you' manual
operation. Information manually input by you also can be associated by other inventory.
8.4.3 Synchronize inventory information

For automatic collected inventory information, once the device status is changed (plug in or
pull out card), the information in NView NNM system may become inconsistent with real
device status, then you can "Synchronize" status by manual to collect the current inventory
information, or wait the system to automatic synchronization at the time of performing poll
operation. Following below steps for NE synchronization:
Step 1 Click Inventory > Physical in system main menu.
Step 2 Click "NE" in classification tree to open NE inventory information list.
Step 3 Click button to set query condition and search NE for synchronization.
Step 4 Click and select one inventory information.
Step 5 Click button and select "Synchronize" or click Synchronize in the right-key menu to
open a confirmation dialog box.
Step 6 Click Yes to perform synchronization and open dialog box of "Synchronize command has
been sent".
Step 7 Click OK to finish synchronization.
Synchronization can also be executed in topology besides in inventory management. Select
device node in topology and click Related Resource > Synchronize in the right-key menu to
perform synchronization.
Pay attention to the below situations during system synchronization.

 Since system takes some time to perform synchronization, please wait the
synchronization finished and then view result of synchronization after you
sending synchronization command (Time for synchronization is different
according to network status and device structure, usually it is 5 seconds.)
 During system updating topology, if it cannot find accessory parts (such as sub-
card of chassis) at original place, the card status will set as "does not exist"; if
265
Raisecom
the current found accessory parts is different from actual type, system will
update part type direct.
NE inventory information records the latest synchronization time, synchronization times and
status, it is convenient for administrator to know synchronization of resource information. By
default, you need to click button on the top-left of list and tick off related item in
customized table list to display synchronization times and status.
8.5 Physical inventory management

Physical inventory management includes management information of rack, NE, chassis, slot,
local card, remote device and ONU.
8.5.1 Rack
Adding rack
You can add inventory information for rack on NMS when there is new rack added into
network. NE and Chassis, etc. inventory in rack is in support of rack information to realize
association between rack and included inventories.
Click Inventory > Physical in main menu and click Rack in classification tree to open rack
information interface. Click the button of in tool bar to fill relative information for the
rack, as figure shows below.
Figure 8-2 Adding rack

After filling information, click Add to open dialog box for confirmation and click OK to
finish adding. Choose Refresh > Refresh All in right-key menu, the added rack information
will transfer to query result tab page for displaying.
266
Raisecom
The items with "*" is compulsory options. The rules for filling property display at the
bottom of property description panel, principle and maintenance staff clicks to select
and click button to associate with related information in directory.
Querying rack
You can query assigned racks or all racks. Click Inventory > Physical in main menu and
click Rack in classification tree to open rack information interface. Click the button of
in tool bar to open query panel.
To query all racks, click Clear in query panel and then click Query, the query result tab page
will display information of all racks.
To query assigned racks, set rack information for querying in the query panel and click Query,
the query result tab page will display the rack information meet query conditions.
Choose one piece of record in query result and click to open property panel and view
detailed property information.
Modifying rack
You must update rack information on NMS when the rack information has been modified.
information interface. Click the button of in tool bar to open query panel.
Select rack information for modification and click button in tool bar to open modification
panel. Click Save after modification and system prompt modifying is successful. The query
result tab page will display the modified rack information.
Deleting rack
When move rack out from network, you need to delete related rack information from NMS.
Select rack information to delete and click to open dialog box for confirmation, then click
Yes to finish the deletion. To delete records in batch, you can press Ctrl and click multiple
records. In addition, you can press Shift and click multiple continuous records.
8.5.2 NEs
Querying NEs
You can query assigned NE or all NEs. Click Inventory > Physical in main menu and click
NE in classification tree to open NE information interface. Click the button of in tool bar
to open query panel.
To query all NEs, click Clear in query panel and then click Query, the query result tab page
will display information of all NEs.
267
Raisecom
To query assigned NE, set NE information for querying in the query panel and click Query,
the query result tab page will display the NE information meet query conditions.
Modifying NEs
Modifying SNMP administrative property incorrect will cause NE cannot be managed

in order.
You must update NE information on NMS when the NE information of name, purpose, SNMP
parameters and project property are modified. Click Inventory > Physical in main menu and
click NE in classification tree to open NE information interface. Click the button of in
tool bar to open query panel.
Select NE information for modification and click button in tool bar to open modification
result tab page will display the modified NE information.
For the "Belonged Rack" in NE project property, you can choose a rack added before to
accomplish association.
Deleting NEs
The NE will be deleted from NMS when executing NE deletion in inventory

information, the related node in NE topology will be deleted too and NE cannot be
managed any more. You have to add NE again to recover management.
When deleting inventory information, please view the information of other related
inventory. The selected information and its related accessories data (like chassis
included in NE) will be deleted, but the information of upper layer inventory (like rack
information) will not be deleted.
When deleting NE, system will clear NE related alarm from current alarm list by
automation'.
When move NE out from network, you need to delete related NE information from NMS.
Click Inventory > Physical in main menu and click Rack in classification tree to open NE
Select NE information to delete and click button to open dialog box for confirmation,
click Yes and NMS will confirm the related data to delete at the same time, then click Yes to
execute deletion and No to cancel deletion. To delete records in batch, you can press Ctrl and
click multiple records. In addition, you can press Shift and click multiple continuous records.
Locating NEs in topology

This command can help to locate NE position in inventory information. Click the button of
to choose a record and locating NE in network topology.
268
Raisecom
NE management
NE management helps to manage NE in inventory information. Click the button of to
choose a record and open NE management interface.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from NE.
Filter alarm can filter all alarms of NE or only filter assigned alarm types.
 To view alarm, you can choose an inventory record by right-key and click Alarm >
Show Alarms in shortcut menu to open alarm view window, the current alarm and
history alarm can be viewed.
 To filter all alarms of one NE, you can choose an inventory record by right-key and click
Alarm > Filter Alarm in shortcut menu to open alarm filter window, tick off the alarm
NE and click OK to filter.
 To filter assigned alarm of one NE, you can choose an inventory record by right-key and
click Alarm > Filter Alarm in shortcut menu to open alarm view window, tick off the
alarm NE, cancel selection of "All Alarm Types" and select assigned alarm type then
click OK to filter.
Related resources
Related resource of NE includes the chassis, local card, remote device and port. You can view
related resource of NE through related resource list.
Right-click to choose inventory record for viewing related resource:
 Click Related Resource > Chassis List in the shortcut menu to transfer to chassis
inventory information interface. The interface displays chassis information of NE.
 Choose Related Resource > Card List to transfer to local card information interface.
The interface displays local card information of NE.
 Choose Related Resource > Remote Device List to transfer to remote device
information interface. The interface displays remote device information of NE.
 Choose Related Resource > Port List to transfer to port information interface. The
interface displays port information of NE.
Synchronizing NEs
The NE inventory management is in support of synchronous NEs inventory information. After
the NE changes, the network is in support of acquiring NE inventory information immediately
through synchronous operation.
If you need to synchronize inventory information, right-click to select an inventory record,
click Sync in the shortcut menu, then it will pop up a confirmation box "is synchronizing?",
click Yes to perform the synchronization operation, otherwise click No.
Tools
The NE inventory management is in support of convenient startup NView NNM network
management system by right-click shortcut menu to provide common management tools, such
as "SNMP Ping", " ICMP Ping ", and Telnet etc. See section 6.2 Commonly-used management
tools for the usages of these tools.
269
Raisecom
Attaching customers
NE information is in support of associated with customer information in NView NNM system.
Operation of associated customer is in support of adding inventory resource into customer
resource.
After choosing an inventory record, click the button of to open associated customer
panel. Click the button of to open customer selection interface which display all
customers in all NMS. Tick off the customers to associate and click OK to finish association,
as figure shows below.
Figure 8-3 Attaching customers
Choose one piece of customer information in the panel and click the button of to cancel
association between NE and customer.
Performance graph
NE inventory supports the rapid entrance of performance graph, right-click an inventory
record, click Performance Graph in shortcut menu to open the corresponding performance
graph interface to view real-time and historical performance graph. The performance graph is
provided by NView NNM performance monitoring service, you need to start the performance
monitoring service to view. See NView NNM User Manual (Performance Monitoring Service)
for the usage of performance monitoring service.
8.5.3 Chassis
Querying chassis
You can query assigned chassis or all chassises. Click Inventory > Physical in main menu
and click Chassis in classification tree to open chassis information interface. Click the button
of in tool bar to open query panel.
270
Raisecom
To query all chassis, click Clear in query panel and then click Query, the query result tab
page will display information of all chassises.
To query assigned chassis, set chassis information for querying in the query panel and click
Query, the query result tab page will display the chassis information meet query conditions.
Modifying chassis
You must update chassis information on NMS when the chassis information such as name,
project property, maintenance staff information, etc. has been modified. Click Inventory >
Physical in main menu and click Chassis in classification tree to open chassis information
interface. Click the button of in tool bar to open query panel.
Select chassis information for modification and click button in tool bar to open
modification panel. Click Save after modification and system prompt modifying is successful.
The query result tab page will display the modified chassis information.
For the "Belonged Rack" and "Chassis Serial NO." in chassis project property, you can choose
a rack and the chassis serial No. to accomplish association.
Deleting chassis
 The chassis will be deleted from NMS when executing chassis deletion in
inventory information. You have to add NE again to recover management.
 When deleting inventory information, please view the information of other related
inventory. The selected information and its related accessories data (like chassis
included cards and ports, etc.) will be deleted, but the information of upper layer
inventory (like NE information) will not be deleted.
 When deleting the chassis, system will clear chassis-related alarm from current
alarm list by automation'.
When move chassis out from network, you need to delete related chassis information from
NMS. Click Inventory > Physical in main menu and click Chassis in classification tree to
open chassis information interface. Click the button of in tool bar to open query panel.
Select chassis information to delete and click button to open dialog box for confirmation,
Locating chassis in topology

This command can help to locate chassis position in inventory information. Click the button
of to choose a record and locating chassis in network topology.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from chassis.
Filter alarm can filter all alarms of chassis or only filter assigned alarm types.
271
Raisecom
 To filter all alarms of one chassis, you can choose an inventory record by right-key and
click Alarm > Filter Alarm in shortcut menu to open alarm filter window, tick off the
alarm chassis and click OK to filter.
 To filter assigned alarm of one chassis, you can choose an inventory record by right-key
and click Alarm > Filter Alarm in shortcut menu to open alarm view window, tick off
the alarm chassis, cancel selection of "All Alarm Types" and select assigned alarm type
then click OK to filter.
Related resources
Related resource of chassis includes the local card and remote device. You can view related
resource of chassis through related resource list.
Right-click to choose inventory record for viewing related resource:
 Choose Related Resource > Card List to transfer to local card information interface.
The interface displays local card information of chassis.
 Choose Related Resource > Remote Device List to transfer to remote device
information interface. The interface displays remote device information of chassis.
Performance graph
Chassis inventory supports the rapid entrance of performance graph, right-click an inventory
8.5.4 Slots
Querying slots
You can query assigned slot or all slots. Click Inventory > Physical in main menu and click
Slot in classification tree to open slot information interface. Click the button of in tool
bar to open query panel.
 To query all slots, click Clear in query panel and then click Query, the query result tab
page will display information of all slots.
 To query assigned slot, set slot information for querying in the query panel and click
Query, the query result tab page will display the slot information meet query conditions.
Modifying slots
You must update slot information on NMS when the slot information of name, slot name,
maintenance staff information, etc. has been modified. Click Inventory > Physical in main
272
Raisecom
menu and click Slot in classification tree to open slot information interface. Click the button
Select slot information for modification and click button in tool bar to open modification
result tab page will display the modified slot information.
Supported card type

It is in support of viewing card type supported by slot in inventory management.
To view card type supported by slot, right-click a slot record and open related panel by
selecting Support Card List, and the interface will display card type information supported
by slot.
8.5.5 Cards
Querying cards
You can query assigned card or all of cards. Click Inventory > Physical in main menu and
click Card in classification tree to open card information interface. Click the button of
To query all of cards, click Clear in query panel and then click Query, the query result tab
page will display information of all of cards.
To query assigned card, set card information for querying in the query panel and click Query,
the query result tab page will display the card information meet query conditions.
Modifying cards
You must update card information on NMS when the card information of name, card name,
menu and click Card in classification tree to open slot information interface. Click the button
Select card information for modification and click button in tool bar to open modification
result tab page will display the modified card information.
Deleting cards
 The card will be deleted from NMS when executing card deletion in inventory
information. You have to execute NE synchronization to recover management.
inventory. The selected information and its related port data will be deleted, but
the information of upper layer inventory (like NE and chassis information) will not
be deleted.
273
Raisecom
 When deleting the card, system will clear card-related alarm from current alarm
list by automation. '
When move card out from network, you need to delete related card information from NMS.
Click Inventory > Physical in main menu and click Card in classification tree to open card
Select card information to delete and click button to open dialog box for confirmation,
Locating cards in topology

This command can help to locate card position in inventory information. Right-click to
choose a record and click the button of Locate in Topo to locate card in NE topology.
Configuration management
Configuration management helps to manage card. Click Card View after right-click and
choose an inventory record to open management interface of card. For the "unknown" card
type, system will prompt fail to perform configuration management.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from card.
Filter alarm can filter all alarms of card or only filter assigned alarm types.
 To filter all alarms of one card, you can choose an inventory record by right-key and
click Alarm > Filter Alarm in shortcut menu to open alarm filter window, tick off the
alarm remote device and click OK to filter.
 To filter assigned alarm of one card, you can choose an inventory record by right-key
and click Alarm > Filter Alarm in shortcut menu to open alarm view window, tick off
the alarm card, cancel selection of "All Alarm Types" and select assigned alarm type then
click OK to filter.
Related resources
Related resource of card only includes the port. You can view related resource of card through
related resource list.
Choose Related Resource > Port List to transfer to port information interface. The interface
displays port information of card.
Attaching customers
Card information is in support of associated with customer information in NView NNM
system. Operation of associated customer is in support of adding inventory resource into
customer resource.
274
Raisecom
customers in all NMS. Tick off the customers to associate and click OK to finish association.
association between card and customer.
Performance graph
Card inventory supports the rapid entrance of performance graph, right-click an inventory
8.5.6 Remote devices
Querying remote devices

You can query assigned remote device or all remote devices. Click Inventory > Physical in
main menu and click Port in classification tree to open remote device information interface.
Click the button of in tool bar to open query panel.
To query all remote device s, click Clear in query panel and then click Query, the query
result tab page will display information of all remote device s.
To query assigned remote device, set remote device information for querying in the query
panel and click Query, the query result tab page will display the remote device information
meet query conditions.
Modifying remote devices

You must update remote device information on NMS when the remote device information of
name, device name, maintenance staff information, etc. has been modified. Click Inventory >
Physical in main menu and click Remote Device in classification tree to open remote device
Select remote device information for modification and click button in tool bar to open
The query result tab page will display the modified remote device information.
Deleting remote devices
 The remote device will be deleted from NMS when executing remote device
deletion in inventory information. You have to execute NE synchronization to
recover management.
275
Raisecom
be deleted.
 When deleting the remote device, system will clear remote device-related alarm
from current alarm list by automation.
'When move remote device out from network, you need to delete related remote device
information from NMS. Click Inventory > Physical in main menu and double-click Remote
Device in classification tree to open remote device information interface. Click the button of
Select remote device information to delete and click button to open dialog box for
confirmation, click Yes and NMS will confirm the related data to delete at the same time, then
click Yes to execute deletion and No to cancel deletion. To delete records in batch, you can
press Ctrl and click multiple records. In addition, you can press Shift and click multiple
continuous records.
locating remote devices in topology

This command can help to locate remote device position in inventory information. Right-click
to choose a record and click the button of Locate in Topo to locate remote device in NE
topology.
Configuration management helps to manage remote device. Click Card View after right-click
and choose an inventory record to open management interface of remote device. For the
"unknown" device type, system will prompt fail to perform configuration management.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from remote
device. Filter alarm can filter all alarms of remote device or only filter assigned alarm types.
To view alarm, you can choose an inventory record by right-key and click Alarm > Show
Alarms in shortcut menu to open alarm view window, the current alarm and history alarm can
be viewed.
To filter all alarms of one remote device, you can choose an inventory record by right-key and
click Alarm > Filter Alarm in shortcut menu to open alarm filter window, tick off the alarm
remote device and click OK to filter.
To filter assigned alarm of one remote device, you can choose an inventory record by right-
key and click Alarm > Filter Alarm in shortcut menu to open alarm view window, tick off
the alarm remote device, cancel selection of "All Alarm Types" and select assigned alarm type
then click OK to filter.
Related resources
Related resource of remote device only includes the port. You can view related resource of
remote device through related resource list.
Choose Related Resource > Port List to transfer to remote device information interface. The
interface displays remote device information of remote device.
276
Raisecom
Attaching customers
Remote device information is in support of associated with customer information in NView
NNM system. Operation of associated customer is in support of adding inventory resource
into customer resource.
association between remote device and customer.
8.5.7 ONU
Querying ONUs
You can query assigned ONU or all ONU. Click Inventory > Physical in main menu and
click ONU in classification tree to open ONU information interface. Click the button of
To query all ONUs, click Clear in query panel and then click Query, the query result tab
page will display information of all ONUs.
To query assigned ONU, set ONU information for querying in the query panel and click
Query, the query result tab page will display the ONU information meet query conditions.
Modifying ONUs
You must update ONU information on NMS when the ONU information of name,
menu and click ONU in classification tree to open ONU information interface. Click the
button of in tool bar to open query panel.
Select ONU information for modification and click button in tool bar to open
The query result tab page will display the modified ONU information.
Deleting ONUs
 The ONU and its configuration data will be deleted from NMS when executing
ONU deletion in inventory information. The deleted ONU cannot take network
management, you have to configure ONU again and add it to NMS to recover
management.
be deleted.
277
Raisecom
 When deleting the ONU, system will clear ONU-related alarm from current alarm
list by automation.'
When move ONU out from network, you need to delete related ONU information from NMS.
Click Inventory > Physical in main menu and click ONU in classification tree to open ONU
Select ONU information to delete and click button to open dialog box for confirmation,
Locating ONUs in topology

This command can help to locate ONU position in inventory information. Right-click to
choose a record and click the button of Locate in Topo to locate ONU in related OLT NE
topology.
NE management
Configuration management helps to manage ONU. Click Device View after right-click and
choose an inventory record to open management interface of ONU.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from ONU.
Filter alarm can filter all alarms of ONU or only filter assigned alarm types.
To view alarm, you can choose an inventory record by right-key and click Alarm > Show
Alarms in shortcut menu to open alarm view window, the current alarm and history alarm can
be viewed.
To filter all alarms of one ONU, you can choose an inventory record by right-key and click
Alarm > Filter Alarm in shortcut menu to open alarm filter window, tick off the alarm ONU
and click OK to filter.
To filter assigned alarm of one ONU, you can choose an inventory record by right-key and
click Alarm > Filter Alarm in shortcut menu to open alarm view window, tick off the
alarm ONU, cancel selection of "All Alarm Types" and select assigned alarm type then click
OK to filter.
Related resources
Related resource of ONU only includes the port. You can view related resource of ONU
through related resource list.
Choose Related Resource > Port List to transfer to port information interface. The interface
displays port information of ONU.
Synchronizing ONUs
The ONU inventory management is in support of synchronous ONU inventory information.
After the ONU changes, the network is in support of acquiring ONU inventory information
immediately through synchronous operation.
278
Raisecom
If you need to synchronize inventory information, right-click to select an inventory record,

click Sync in the shortcut menu, then it will pop up a confirmation box "is synchronizing?",
click Yes to perform the synchronization operation, otherwise click No.
Tools
The ONU inventory management is in support of convenient startup NView NNM network
management system by right-click shortcut menu to provide common management tools, such
as "SNMP Ping", "ICMP Ping", and Telnet etc. See section 6.2 Commonly-used management
tools for the usages of these tools.
Attaching customers
ONU information is in support of associated with customer information in NView NNM
customer resource.
association between ONU and customer.
Performance graph
Remote inventory supports the rapid entrance of performance graph, right-click an inventory
8.5.8 CNU
Querying CNU
You can query all CNUs or a specified CNU. At the system menu bar, click Inventory >
Physical to display a window. On the left navigation tree, click CNU to display CNU
inventory information view. Click at the tool bar to display a query panel.
 If you query all CNUs, click Clear and then click Query. And then all CNU records are
displayed.
 If you query a specified CNU, enter required CNU information and click Query. The
required CNU records are displayed.
Select a record from the query results and then click to display a property panel, where
you can view detailed property information.
Modifying CNU
When the name and information of maintenance personnel are changed, you need to upgrade
CNU information at the NView NNM. Click Inventory > Physical to display a window. On
279
Raisecom
the left navigation tree, click CNU to display CNU inventory information view. Click at
the tool bar to display a query panel, where you can query upgraded CNUs.
Click a CNU record that needs to be modified, and then click at the tool bar to display a
modification panel. After modification, click Save to apply new configurations. A dialog box
is displayed, saying The modify operation is successful! The modified CNU information will
be displayed on the query result tab page.
Deleting CNU
When deleting a CNU from the inventory, you will delete the CNU from the NView
NNM. Meanwhile, you delete configuration data of the CNU. The deleted CNU cannot
be managed by the NView NNM. To re-manage a CNU, you need to re-configure the
CNU and add it to the NView NNM.
When deleting inventory information about a CNU, you need to view other related
inventory information. If you confirm the operation, all related information about the
CUN and its ports will be deleted. However, the parent inventory information
(information about the NE or the chassis) of the selected CUN cannot be deleted.
When a CNU is deleted, all alarms that are related to this CNU will be deleted from
the current alarm list.
In a real case, when a CNU is removed from the NView NNM, you need to delete related
CNU information from the NView NNM. Click Inventory > Physical to display a window.
On the left navigation tree, click CNU to display CNU inventory information view. Click
at the tool bar to display a query panel, where you can query CNUs that need to be deleted.
Click a CNU record that needs to be deleted, and then click at the tool bar. A dialog box
is displayed, asking The selected records will be deleted permanently! Continue? Click Yes
and the same dialog box will be displayed again. Click Yes to delete the CNU record. Click
No to cancel the operation.
To delete records in batch, you can press Ctrl and click multiple records. In addition, you can
press Shift and click multiple continuous records.
Locating CNU in topology

When needing to the position of CNU CBAT in the topology, right-click a record and then
click Locate in Topo.
When needing to manage CNU in the inventory, right-click a record and then click Device
View.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from CNU.
You can filter all alarms of CNU or only filter assigned alarm types.
To view alarm, you need to right-click an inventory record and click Alarm > Show Alarms
to display a View Event window. And then you can view current and history alarms.
280
Raisecom
To filter all alarms of one CNU, you need to right-click an inventory record and click Alarm >
Filter Alarm to display an Add Filter Rule window, Tick off the alarm CNU and click OK.
To filter assigned alarm of one CNU, you need to right-click an inventory record and click
Alarm > Filter Alarm to display an Add Filter Rule window. Tick off the alarm CNU, cancel
selection of "All Alarm Types" and select assigned alarm type. And then click OK.
Related resources
Related resources of CNU only include ports. You can view related resources of CNU through
port list.
Right-click an inventory record, and then click Related Resource > Port List to display a
window, where you can view port information of the CNU.
Synchronizing CNU inventory information

The CNU inventory management is in support of synchronizing CNU inventory information.
After the CNU is changed, the NView NNM acquires CNU inventory information
immediately through synchronous operation.
If you need to synchronize inventory information, right-click an inventory record, click Sync
to display a dialog box, asking Is synchronizing? Click Yes to perform the synchronization
operation. Otherwise click No.
Tools
The CNU inventory management provides NView NNM tools through right-click shortcut
menu, such as "SNMP Ping", "ICMP Ping", and Telnet. For detailed information about the
usage method, see sectin 6.2 Commonly-used management tools.
Attaching customers
CNU inventory information is in support of attaching with customer information in NView
NNM. Operation of attaching customer is in support of adding inventory resource into
customer resource.
After choosing an inventory record, click to display Attach panel. Click the to
display Customer Select view where all customers in NView NNM are displayed. Tick off the
customers to attach and click OK.
Choose a piece of customer information in the panel and click to cancel attachement
between CNU and customer.
8.5.9 Ports
According to service and port form, the ports in inventory management include Ethernet port,
PDH electrical port, PDH optical port, SDH port, V35 port, PCM voice port, VoIP port, serial
port, EPON port and other ports. This section takes Ethernet port as an example since the
management functions of all classes are identical.
281
Raisecom
Querying ports
You can query assigned port or all ports. Click Inventory > Physical in main menu and click
Port in classification tree to open port information interface. Click the button of in tool
To query all ports, click Clear in query panel and then click Query, the query result tab page
will display information of all ports.
To query assigned port, set port information for querying in the query panel and click Query,
the query result tab page will display the port information meet query conditions.
Modifying ports
You must update port information on NMS when the port information of name, maintenance
staff information, etc. has been modified. Click Inventory > Physical in main menu and click
Port in classification tree to open port information interface. Click the button of in tool
Select slot information for modification and click button in tool bar to open modification
result tab page will display the modified port information.
Locating ports in topology

This command can help to locate Ethernet port card position in inventory information. Right-
click to choose a record and click the button of Locate in Topo to locate Ethernet port card in
NE topology.
Alarm management
You can view alarm information and filter alarm when there is alarm generated from Ethernet
port. Filter alarm can filter all alarms of Ethernet port or only filter assigned alarm types.
To filter all alarms of one Ethernet port, you can choose an inventory record by right-key and
click Alarm > Filter Alarm in shortcut menu to open alarm filter window, tick off the alarm
Ethernet port and click OK to filter.
To filter assigned alarm of one Ethernet port, you can choose an inventory record by right-key
and click Alarm > Filter Alarm in shortcut menu to open alarm view window, tick off the
alarm Ethernet port, cancel selection of "All Alarm Types" and select assigned alarm type then
click OK to filter.
Attaching customers
Port information is in support of associated with customer information in NView NNM
customer resource.
282
Raisecom
association between port and customer.
Performance graph
Port inventory supports the rapid entrance of performance graph, right-click an inventory
8.6 Inventory types

NView NNM manages the NE and chassis, etc. resources in network according to inventory
types. The inventory types are denoted as system OID. You can view related system OID and
description of inventory type. If system OID of device is inconsistent with resource type in
NNM system, please contact with our technical support staffs. After modifying or deleting
inventory type, the resource cannot be managed normally, so inventory type is only in support
of property view and query.
Click Inventory > Inventory Type to open interface of inventory type. On the left of
interface is the inventory type tree, on the right, it displays type list of NE types by default.
Figure 8-4 Inventory types

Click the classes in inventory type tree to view type of different types.
You can query assigned NE or all NEs. Click Inventory > Inventory Type in main menu and
click NE Type in classification tree to open NE information interface. Click the button of
283
Raisecom
 To query all NEs, click Clear in query panel and then click Query, the query result tab
page will display information of all NEs.
 To query assigned NE, set NE information for querying in the query panel and click
Query, the query result tab page will display the NE information meet query conditions.
8.7 Address book management

You can write contact information of responsible person and maintenance staff into address
book for associating with inventory information.
Adding address book

Write the contact information (name and telephone, etc.) of maintenance staff into address
book, and then you can choose related record in address book when writing or modifying
other inventory information. It is convenient for you to view contact information of
maintenance staff on NMS.
Click Inventory > Address Book to display address book interface. Click the button of
in tool bar to open panel and write related contact information.
Figure 8-5 Adding address book

ID and name of address book cannot be repeated in order to make sure the consistence of data.
Click Add to open confirmation box after filling the data and click OK to finish adding. The
new address book item will display in new data tab. Right-click and choose Refresh >
Refresh All to transfer address book information to query result tab page for displaying.
284
Raisecom
The items with "*" is compulsory options. The rules for filling property display at the
bottom of property description panel.
Querying address book

You can query assigned address book or all directories. Click Inventory > Physical to open
address book information interface. Click the button of in tool bar to open query panel.
To query all directories, click Clear in query panel and then click Query, the query result tab
page will display information of all directories.
To query assigned address book, set address book information for querying in the query panel
and click Query, the query result tab page will display the address book information meet
query conditions.
Modifying address book

You must update address book information on NMS when the contact information of address
book has been modified. Click Inventory > Physical to open address book interface. Click
the button of in tool bar to open query panel.
Select address book record for modification and click button in tool bar to open
The query result tab page will display the modified address book information.
Deleting address book

When the contact information in address book is out of use, you need to delete related
information from NMS. Click Inventory > Physical to open address book information
interface. Click the button of in tool bar to open query panel.
Select address book records to delete and click in tool bar to pop up confirm dialog box.
Click Yes to execute deletion. To delete records in batch, you can press Ctrl and click
multiple records. In addition, you can press Shift and click multiple continuous records.
8.8 Exporting inventory information

Inventory information can be exported and saved as Excel or Text file. Exporting types
include export all, export current page and export selected items.
Click the button of in tool bar to open query panel and query the information for
exporting.
 To export all pages from query result: click Export > All > To Excel and then choose
path for saving, the selected information will be saved to Excel file.
 To export current page from query result: click Export > Current Page > To Excel and
then choose path for saving, the selected information will be saved to Excel file.
285
Raisecom
 To export selected items from query result: choose the items to export and click Export >
Selected Item > To Excel and then choose path for saving, the selected information will
be saved to Excel file.
After the "successful operation" prompt box, click OK to finish operation. The steps for
export and save information in Text file is the same as above.
8.9 Inventory information statistics

Statistic of inventory information includes device type statistics, card type statistics and slot
vacancy ratio statistics.
8.9.1 Device type statistics

System provides device types statistic function to statistic device type amount in each subnet.
Step 1 Click Report > Device Type Statistic in system main menu to open related analysis window.
Step 2 Click at the tool bar to display a Subnet Selector window. Select a subnet node and click
OK. and then click the button of Statistic Analysis in tool bar. System starts to statistic device
types in subnet and gives out statistic result.
Figure 8-6 Statistics of device types

 Click the button of Graph in tool bar to switch displaying mode between Table List and
Histogram.
8.9.2 Card type statistics

System provides card types statistic function to statistic card type amount in each subnet.
Step 1 Click Report > Card Type Statistic in system main menu to open related analysis window.
OK. and then click Statistic in tool bar. System starts to statistic card types in subnet and
gives out statistic result.
286
Raisecom
Figure 8-7 Statistics of card types

 Click the button of Graph in tool bar to switch displaying mode between Table List and
Histogram.
8.9.3 Slot idle rate statistics

System provides slot idle rate statistic function to statistic slot idle rate of chassis in network.
You can efficient know the slot occupation of chassis and provide important reference for
programming staff when buying new card or enlarging network scale.
Step 1 Click Report > Idle Slot Statistic in system main menu to open related analyze window.
OK. And then click Statistic in tool bar. System starts to statistic slot idle rate in subnet and
gives out statistic result.
The statistic result will display after analysis. In row "idle rate", different colors indicate the
range; it is green for 0%–50%, orange for 50%–80%, red for 80%–100%. Click the button of
Graph in tool bar to display statistic result in pie graph.
Slots idle rate statistics need to abide by the following principles:

 The device itself has no slots, if the device has remote device and the remote
device has not slots, then this device will not participate in slot idle rate statistics.
 The device itself has no slots, if the device has remote device and the remote
device also has' slots, then the device nodes "slots number", "idle slots number",
and "idle rate (%)" will show as "—". The slot information of the remote device will
not be included in its local device slots statistics.
 The subnet "slots number", "idle slots number", "idle rate (%)" are always
displayed as "—".
287
Raisecom
Figure 8-8 Statistics of slot vacancy ratio
288
Raisecom
NView NNM Operation Guide 9 Customer management
9 Customer management
This chapter mainly introduces the related definition and operation concerning network
customers and how to manage information of network customers using NView NNM system,
 Overview
 Customer lists
 Attaching network resources to customers
9.1 Overview
9.1.1 Brief introduction of functions
For carriers that provide customers with access services, a key criterion to evaluate their
customer service quality is how they predict or evaluate service affections on customers
directly by exact fault analysis and localization, and remove the faults correctly and in time to
ensure high service quality accordingly. To satisfy the requirements of customer service
quality, NView NNM system provides customer management function to manage detailed
information of end customers and attach network resources to customers according to their
factual access devices. This helps the administrators locate the customer from which the fault
report comes and remove the fault quickly. As a result, service quality of carriers improves.
To improve the efficiency of customer data input, NView NNM customer management
component provides a data import function apart from the traditional manual data input
function. The system is able to import Excel file in a specified format and validate the content
of the file. Besides, the data export function provided by the system helps you backup and
keep important data.
9.1.2 Related definitions

 Customer: an entity (a person or a machine) that utilizes the service or infrastructure
provided by carrier. In NView NNM system, a custom can be a community, a building, a
company, a governmental department, or a person, and etc.
 Attach: establish binding relationship between network resources and customers. In
NView NNM system, you can attach device, card or port resources to customers. A card
or port can be attached to several customers, while several cards or ports can be related
to one customer.
289
Raisecom
 Detach: delete the relationship between network resources and customers
9.2 Customer lists

Click Customer > Customer List on the system main menu to open "Customer List"
interface.
There are three parts on the main view of "Customer List" window: query panel, customer
list, and customer properties pane. The query panel can be opened by clicking the button
Open Query; while the customer properties pane can be opened by clicking the button Open
Properties Pane.
 Query panel: You can set up query condition here. Only customer records that satisfy the
query condition will be displayed on the customer list after the query.
 Customer list: Display the information of registered customers in a list. The content of
the list is related to the query condition in the query panel. The system will display all
customer information in pages by default.
 Properties panel: Select a record in the customer list, detailed information of the
customer and resources attached to it will be displayed on the properties pane. You can
input and edit customer information in the properties pane. Double-click customer
information to open the properties panel. Properties panel contains the "customer
property" and "customer resources" two tabs.
Figure 9-1 Customer List
9.2.1 Inputting customer information

Click the button Open Properties Pane on the toolbar of the "Customer List" window, the
properties pane will turn up beneath the custom list. Click the Customer Properties to turn
up the "Customer Properties" page:
290
Raisecom
Figure 9-2 Customer information manual input

Click the button Add on the properties pane after editing customer properties, if the operation
fails, the system will inform you of the fault, if the operation succeeds, and the newly-added
customer information will be directly displayed in the customer list.
Only "Customer Name" is compulsory among all customer properties. You cannot use a
customer name that has already been used in the system. If this happens, the system will pop
up a prompt box.
9.2.2 Importting customer information

Customer information can be imported from Excel file. The steps are as below:
Step 1 Click Import Excel to open import interface, as shown below. The imported file must meet
the "help" requirements.
Figure 9-3 Selecting the import file
You can perform Excel export operation firstly by exporting Excel file edition and
adding customer information, and then perform the import operation so as to avoid
the field name error which will cause incorrect import customer information.
Step 2 Click Browse to select the Excel file to import, then click OK to open the import file content
inspection interface, as shown below.
291
Raisecom
Figure 9-4 File content inspection

Step 3 Click Check, NView NNM will check the contents of import file automatically and display
the results. If finding problems, the system will pop-up message box, as shown below.
Figure 9-5 File inspection results
For the same customer name import record, you need to update the records
according to the corresponding clients' names. If there is the same client name in
customer information or do not need to update the original customer information,
please modify the client name corresponding to the records in the import file firstly,
and then perform the import operation.
Step 4 Click Import to pop-up confirmation dialog box "it will perform customer information import
operation, whether to continue?", click Yes to perform the import operation.
292
Raisecom
Step 5 After finishing, the system will pop-up confirmation dialog box "operation is successful,
whether to import other data files?". Click No to return client list interface, click Yes to return
import files selection interface.
9.2.3 Exporting customer information

Customer information can be exported and saved in the format of Excel, Text file. The export
can be divided into export all, export the current page and export the options.
 If you need to export all the customer information, click Export > All Items > To Excel
in the customer lists menu, and then choose save path, all the customer information will
be saved to an Excel file.
 If you need to export the current customer information page, click Export > Current
Page > To Excel in the customer lists menu, and then choose save path, the customer
information in current page will be saved to an Excel file.
 If you need to export specified customer information, click to select a piece of customer
information or press Ctrl-click to select multiple customer information, click Export >
Selected Items > To Excel in the customer lists menu, and then choose save path to save
the selected customer information to an Excel file.
The system will pop-up successful prompt dialog box after successful export, click "Confirm"
to complete the export operation. The operations of exporting customer information and
saving it as Text file are similar to the above steps, for example, click Export > Selected
Items > To Text in the customer lists menu, you can export it as Text file.
9.3 Attaching network resources to customers

The alarm information generated by attaching network resources to customers contains
associated customer information, which makes it easy to get customer information with
network failure influence.
9.3.1 Attachinging network resources to customers

Click the button Open Properties Pane on the toolbar of the "Customer List" window, the
properties pane will turn up beneath the customer list. Select a customer on the customer list,
the "Customer Resource" page on the properties pane will become usable, information of
network resources that have been associated to the customer will be shown on the "Customer
Resource" page.
Establishing association
Open the "Customer Resource" page on the properties pane (only applicable after selecting a
customer on the customer list), a list of information of existing customers will appear on the
page, right-click on the list, a shortcut menu as is displayed, as shown below.
293
Raisecom
Figure 9-6 Attaching resources in the customer list on "customer resource" page
You can establish association between devices and customers, cards and customers, or ports
and customers. Click one of Add Device, Add Card and Add Port on the right-click menu,
the corresponding "Select Resource" dialog box will pop up. You can select resources and
associate them to the selected customer.
294
Raisecom
Figure 9-7 Attaching resources to a customer
Locating in topology
"Customer Resources" is in support of topology location operation, and you can quickly
locate the network topology position of customer resource. Select a record in the page of
"Customer Resources" tab, and then click Locate in Topo in the shortcut menu, as shown
below. NView NNM will locate on the topology and select the resource automatically.
Figure 9-8 Locating to topology
Detaching network resources

Select a customer on the customer list and open the "Customer Resource" page on the
properties pane. Select one or several records on the customer resource list, right-click on the
selected records and click Detach on the shortcut menu, the system will delete the
relationship between the customer and the selected resources. The detachment will renew the
records on the customer resource list.
295
Raisecom
Figure 9-9 Detaching resources from customer

Similarly, you can detach the resources from a customer on the properties pane on one of the
resource management window.
9.3.2 Viewing customer alarm information

Customer alarms are alarm information from the network resources (device, card or port) that
have been attached to the customer. Customer alarm information is only available when there
are network resources attached to the customer, these resources have sent alarm information
to network management system and the system has correctly received the information.
Viewing customer-related alarm information

Select the customer to be examined in the customer list, right-click on the selected record and
click View Event on the shortcut menu, or click the button View Event on the toolbar of
"Customer List" window, a "View Events" window for the selected customer will pop up.
You can view current alarms and historical alarms from resources attached to the customer in
this window.
Viewing customer information in alarm properties pane

If the device, card or port has already been attached to a customer, when it reports alarms, the
name of the customer to whom it is attached will be included in the properties of the alarm
event. As a result, you can view related customer information on alarm properties panel, as
shown below.
296
Raisecom
Figure 9-10 Viewing customer information in alarm properties pane
297
Raisecom
NView NNM Operation Guide 10 System security management
10 System security management
This chapter mainly introduces conceptions concerning system security and how to configure
security control policy in NView NNM system to guarantee secure operation of the system,
 Overview
 User management
 User group management
 Operator set management
 Access control list management
 Security policy management
 Monitoring user operation
 Online user management
 User login modes
 Log strategy management
10.1 Overview
NView NNM security management refers to make sure that only the authenticated you can
enter the system and execute authorized network management operations so as to ensure that
the network and network devices, system and network management information are not used
by illegal or unauthorized you or exposed to other dangers.
NView NNM system adopts the concept of "centralized monitoring and decentralized
authority domain management" and realizes "different administrators have different
authorities to different management domains".
 NView NNM centralized monitoring function can record the NMS or device operations
and operation results of all users to logs, the administrator can track and check the users
operation by the logs so as to monitor the network system.
 NView NNM decentralized authority domain management function can divide the users
to different levels and to user group as well as divide the network resource into different
administrative domains by NE as a unit in order to achieve different users with different
operation authorities to different network resources.
298
Raisecom
Compared with previous kernel versions, NView NNM V5.4 and later have different
security management. After the NView NNM is upgraded, the user (NView NNM
account) and user group operation authorities (including NView NNM operation and
device configuration operation authorities) may be changed.
After upgrading the kernel version to V5.4 and later, you need to verify that the
formerly-configured user authority is correct. If not, you need to contact the NView
NNM administrator to modify or re-assign user authorities.
 In topology view, click Security > User Management to display a window. You
can view operation authorities or operation set of the user or user group. In
addition, you can view detailed authority assignment.
 You can view detailed user authorities in the NMS Client. For example, you can
log in to the NMS Client and then view topology or alarms. In addition, you can
configure devices in the NMS Client.
In order to ensure the security of the network management system information, prevent others
illegally authorized users' login, the administrator can set IP network segment or IP address to
access network management system for users. You can only login the network management
system in the certain network segment, which increase the system security. In addition, you
can configure a time range for users to access the NView NNM. Beyond the time range, users
cannot log in to the system.
NView NNM supports to set user login system password rule, for example the following
configuration.
 The minimum password length. Password length for a newly-created user should not be
shorter than the minimum password length..
 Set the number of minimum difference in the character between the old and new
password to modify.
 Set the minimum number of characters and other restriction rules of password composed
units so as to prevent user password from cracking.
NView NNM security management can monitor user operation and view the all user
information and their operation to login NView NNM system, help administrator trace event
source, improve the administrator self-discipline and prevent the illegal operation from
legitimate users.
The system security management configuration operation can be performed only

when "administrator" users or users in "Security administrator group" and "Sub-
domain security administrator group" login the system.
10.1.1 Users
User refers to the entity that has specific operation authority to some management domain and
has certain access control authority to network management system. The operation authority
and the management domain for a user is the union set of authority/domain of assigned user
group and the user. The security function structure is shown as below.
299
Raisecom
User
group
Attach
to
Operatio Subject to access

Manageme n Operation Own control constraint
nt domain authority
User NView NNM
Figure 10-1 User security function structure

NView NNM can divide users into three levels and the authorities are as follows:
 Super administrator: have full operation authorities and management domains; super
administrator can create users or user groups and can assign all operation authorities and
management domains to users or user groups.
 Security administrator/sub-domain security administrator: have security management
operator set, some or all management domains; the administrator can create users or user
groups, the assigned management domain and operation authority can only be the subset
of their own authority; the administrator management to user is a hierarchy relationship,
i.e. A can manage B, B can manage C, then A can also manage C.
 Ordinary user: cannot create users; the resources and operation authority can only be
specified by superior administrator.
In addition to the system default super administrator user "administrator", the users
cannot take security management even if they belong to "Administrators" user group.
Only "administrator" and users in "Security administrator group" and "Subdomain
security administrator group" have security management authority.
10.1.2 User group

User group refers to the group with the same management domain and operation authority.
The function structure is shown as below.
Figure 10-2 User group function structure

NView NNM divides user group into the following classifies:
 Administrators (Super administrators group): set of super administrators
300
Raisecom
 Security administrators group/Sub-domain security administrators group: set of security

administrators
 Ordinary users group" set of ordinary users
Each user can belong to multiple user group (has multiple user group management domain
and operation authority), but cannot belong to security administrators group and sub-domain
security administrators group simultaneously.
10.1.3 Operation authority

Operation authority is divided into two types: network management applications and device
operation. The menu and button without authority is grey and cannot be clicked to use; the
operation does not meet the authority will pop up prompt and cannot be operated.
 Network management applications operation authority refers to system menu, right-click
shortcut menu and the operation authority of various buttons in network management
client.
 Device operation authority refers to the authority to take NE management to NE device
in user or user group management domain, including resource sync, modify and view
device configuration.
The common operation authority of network management application is shown in authority
comparison table.
10.1.4 Operator set

The operator set is the partition to all operation authority set; you can select some specified
operation to divide an operator set according to their own management mode and habits.
NView NNM provides some default operator sets; you can also create by themselves. The
operator set can be divided into "Network management application" and "Network device"
according to the using object, which are corresponding to NMS client operation and NE
management operation respectively.
The user's operation authority can contain multiple operator sets; the actual operation
authority is the union set of all operation authorizes of these operator sets. To modify operator
set will affect the operation authority of all users or user groups using this operator set.
10.1.5 Management domain

Management domain takes subnet, NE, chassis (mainly refers to RC002 chassis), or remote
device as the granularity, is the user operation objects resource set. In this way, the network
resources can be effectively divided. NView NNM security management supports to take
decentralized domain management in accordance with management domain or subnet.
Management domain configuration uses the following classifies for you to select.
 Object universal set: contains all subnets and NEs in NView NNM, i.e. can manage all
network devices in NView NNM.
 Subnet device set: can select to manage the subnet and NE in NView NNM. You can
manage subnet and all subordinated subnets and device with the management authority
of subnet device set management domain, including assigning the created and follow-up
added subnets and devices in management domain.
 Device: contains NE, chassis (mainly refers to RC002 chassis), or remote device, i.e. can
select to manage all NE devices in NView NNM. Device management domain is used to
assign user device operation authority and view device located subnet hierarchy.
301
Raisecom
 For EPON device, OLT and ONU can be added to the management domain as
stand-alone NE and make the management granularity of network management
more refined; OLT subnet (including OLT PON port subnet and all accessed ONU
devices) and PON port subnet (including ONU port accessed all PON device) can
also be added to the management domain as a subnet for unified management.
 For symbol nodes in the topology, they indicate detailed topology information
without any real configuration functions. Therefore, you cannot control symbol
nodes in the management domain. You can view all symbol nodes in the topology.
10.1.6 Decentralized hierarchy, decentralized authority and

decentralized domain
NView NNM achieves decentralized hierarchy, decentralized authority and decentralized
domain security management.
 User level can control and distinguish security management from other network
management application function. Security management can continue to divide into the
sub-domain level security administrators for more levels of management.
 User authority can control the management authority of network management system
and NE device. User group and operator set can take authority planning easily and can
also individually assign user authority for fine adjustment.
 User management domain can divide management range. Subnet devices set and devices
set can divide management range easily.
The allocation combination between network management application, management domain,
operator set and operation authority is shown as below.
Table 10-1 Allocation authority combination

Network management Operator set and operation authority
application/management domain
Network management application Network management application operation authority
Network management application operator set
Full set of objects Assign device operator set to all subnets and NEs of
network management
Subnet devices set Assign device operator set to subnet (including the devices
in subnet)
Device Assign separate device operation authority to NE device
10.1.7 Access control

By setting the system ACL (Access Control List), only the IP address, network segment or IP
address range in the list can login NView NNM system. Reasonable allocation of ACL can
effectively prevent the system from malicious attacks and protect the system security. The
access control can also be used to add, modify and delete access lists.
302
Raisecom
10.1.8 Security policy

Security policy refers to user account and password setting policy to login NView NNM
system. Security policy controls the user accounts and password setting format and rule, for
example, can configure the length of user account, user lock, the length of password, the
number of minimum difference in characters between the old and new passwords and the
ascending/descending order of numbers or letters.
10.1.9 Log policy

You can set the logging strategy with security management authority, specify user actions
need to log all operations to show the form of a tree, you can select or search operation log
policy settings. Default all operations log.
10.1.10 Security management deployment process

For NView NNM system, please deploy security management according to the following
process:
Step 1 Plan management level to determine security management and ordinary user roles.
Step 2 Plan management authorities to determine the management authorities for different users.
Step 3 Plan management domains to divide network resources into several management domains
according to specific situations.
Step 4 Create user, set password and access security policy.
Step 5 Create user group: create several user groups according to the actual needs of network
management, and then assign authorities to user groups. The authorities of user groups contain:
 Assign users: these users will have user group management domains and authorities.
 Assign user group management domains.
 Assign network management application authority and device operator set or operation
authority in management domain.
Step 6 Security management deployment will take effect when the user logins.
Step 7 (Optional) adjust user management domains and authorities to meet the specific security
requirements.
If the user group security management policy has been changed and users in this
user group have already logged in the system through some client, the system must
allow the user to log in again in order to ensure the update to take effect.
10.2 User management

10.2.1 Default user
NView NNM provides "administrator" default user, the default password is "raisecom". This
user authority is highest, i.e. the super administrator user.
303
Raisecom
The user has the following characteristics:

 This user has all operations, configurations and security management authorities of
NView NNM.
 This user belongs to "Administrators" and "Security administrators group".
Administrator user group has all network management applications authorities in
addition to security management; the security administrators group has safety
management authority.
 This user does not support to modify or delete the authority, only supports to modify the
user full name and description.
 This user can configure "access control list" to restrict the login IP.
Use "administrator" default user to login NView NNM, the administrator can create users in
line with the needs according to the specific circumstances of network management authority.
10.2.2 Creating users

It needs the following steps to create a user:
Step 1 Click Security > User Management in system menu bar to open the main application view of
user management, as shown below.
Step 2 Create a new user. Right-click "user" in the left tree list, and then click New User in right-
click menu to display a Create user dialog box
After displaying the user management view, and selecting Security Manager Object >
User, click on the left top of the view to display a dialog box. Select user list
properties in the dialog box.
Step 3 In Create user dialog box, click "Base Info" to show the interface below. This interface can
be used to configure user name, password and other information.
304
Raisecom
Figure 10-3 Basic information about the user

User name Set by "Security Input user name.
policy"
User full mane – Input user full name.
Description – Input user description.
Password Set by "Security Input user password.
policy"
Confirm Set by "Security Input user password again
password policy"
 Checked
User must change Select whether to change
 Unchecked
password at next password at next login
login
 Checked
User cannot Select whether to change
 Unchecked
change password password
 Checked
Account Select whether to suspend the
 Unchecked
suspended account
305
Raisecom

Maximum 1–180 Input the maximum password
password age age days
days "No restriction" indicates not to
restrict the password age days
Step 4 Click Advanced to configure the advanced properties for user. After the configuration is
complete, click OK.

Maximum 0–255 or "no restriction" Configure the numbers to
number of use this user account for
online parallel login.
In the same client host, one
user account can only login
one client process.
Automatically 10–600, unit: minute, or Input the auto-exit time for
quit waiting select "Stop auto-exit" user without operations.
time
Start time Select to start time Select the time segment
limit segment restriction: restriction for this user to
 Start date start login system
 End date
 Daily start time
 Daily end time
 Weekly start time
Step 5 Click "Details" to show the interface below. The contact information of user can be configured
in this interface.
306
Raisecom
Figure 10-4 Detailed information about the user

Department – Input user department
information.
TEL – Input user telephone.
FAX – Input user fax.
E-mail E-mail address Input user email.
should contain "@"
Postcode – Input postcode.
Address – Input user address.
Step 6 Click "Owner Group" to show the interface below. The user subordinated user group can be
configured in this interface.
307
Raisecom
Figure 10-5 Owner group information

Click Add in the lower right corner and select user subordinated user group in the pop-up
dialog box. Click OK to complete the configuration.
One user can belong to multiple groups, but cannot belong to "Security
administrators group" and "Sub-domain security administrators group" simultaneously.
Step 7 (Optional) click Copy permissions from the user to pop up user list, check one or more the
created user records, and then click OK to copy the management domain and operation
authority of selected users.
Click Copy permissions from the user to copy the permissions, the selected
management domain and operation permission will be cleared automatically, and
then copy management domain and operation permission.
Step 8 Click "Management domain" to show the interface below. The user managed resource can be
308
Raisecom
Figure 10-6 Management domain

Click Selection in the lower right corner to select management domain in the popup dialog
box.
Step 9 Click "Operator Privilege" to show the interface below. The user operator privilege can be
309
Raisecom
Figure 10-7 Operator privilege

Click Selection in the lower right corner to pop up Select operator privilege dialog box.
Then click OK to complete the operation.
After adding an operator set in "Select operator privilege" dialog box, if users need to
add constantly, they need to select "Authorization object" (for example click "NMS
application") again and then select operator set to add.
Step 10 Click "Access control" to show the interface below. The access control operator privilege can
be configured in this interface, click Apply to save the configuration.
310
Raisecom
Figure 10-8 Access control
 By default, "All access control list will be used" is selected. It means the user
account is controlled by all created access control lists.
 Select "assigned access control list will be used" and then select specified access
control list. The user account is controlled by the selected access control lists.
 In addition, you can click Set access control list to configure a new access
control list. For detailed configuration descriptions, see section 10.5 Access
control list management.
10.2.3 Modifying users

This operation can modify the properties of non-super administrator users, such as user's full
name, subordinated group, management domain, operation authority, and access control
information. Please follow the steps below.
When user subordinated group, management domain and operation authority

properties are modified, if the modified member is logging in client, the client will
prompt that "Your authority has been changed, please login again and click OK to
exit!" at this time, the user cannot continue the operation but click OK to close client.
After login again, the properties of modified user will take effect.
Step 1 Click Security > User Management in system main menu to open "user management" tab
page.
Step 2 In the left "Security management object", click "user" node, it will show all the current users
in the form of list. Double-click the user located line to modify the properties information of
user in the displayed interface. The modify interface is same to the add interface.
311
Raisecom
Step 3 When the ordinary properties and access control are modified, click Apply to complete the
modification. When the management domain and operation authority are modified, click OK.
 In the left "Security management object" tree, you can also click user name to
modify in "user" node, it will show the properties information of user to modify in
the right interface.
 To modify the management domain and operation authority of user, the grey part
authorities are the authorities of user subordinated user groups, which can only be
modified by modifying user group.
 Sub-domain security administrators can only modify the users created by
themselves, but cannot modify the users created by other management domain
users.
10.2.4 Deleting users

This operation can delete the undesired users and save resources.
The steps to delete user group:
Step 1 Click Security > User Management in system main menu to open "user management" tab
page.
in the form of list. Select the users to delete, click the Delete in the lower left corner, and then
click Yes in the pop-up Confirm dialog box.
Figure 10-9 Double-click the user located line to modify the properties information of user in the
displayed interface. The modify interface is the same to the add interface.
10.2.5 Resetting password

When the user forgets the password, the super administrator, security management domain or
sub-domain security administrator (sub-domain security administrator can only reset
passwords for sub-domain security administrator and common users created by the sub-
domain security administrator.') needs to reset the password; the reset operation does not need
to input old password. The password of super administrator cannot be reset, if the password of
super administrator is forgotten, please contact Raisecom technical support staff.
Step 1 Click Security > User Management in system main menu to open " user management" tab
page.
in the form of list. Select the users to modify the password, click the Set password in the
lower left corner to pop up Set password dialog box, input new password and click OK.
It is default to check "User must modify the password in next login" in Set password
dialog box, which indicates the user with password reset must modify password in
login. In this case, when the user logs in client, it will prompt that "the system requires
you to modify the password, or the system will exit." Click Yes to pop up Modify
password dialog box, input old password and new password and then click OK to
modify the password and login client.
312
Raisecom
10.2.6 Unlocking account

When the number of errors of user's password exceeds the configuration number in account
policy, the user account will be locked and user cannot login the client until reaching the aut0-
unlock time. If the lock rule in account policy is "Permanently locked", the administrator
needs to unlock manually.
page.
in the form of list.
Step 3 The "Lock status" of locked user account is displayed as "Permanently locked" or "Limited
locked" (Limited locked refers to unlock automatically in reaching auto-unlock time). Click to
select the locked user account records, click Unlock in the lower left corner to pop up "Unlock
successfully" dialog box, which indicates the user has already unlocked.
 To login client, if the password is wrong, it will prompt the times to input error
password, the user will be locked after reaching the number of errors in account
policy; even if the correct password is entered, it will also prompt the user has
been locked.
 The system will only show the created users by sub-domain security administrator
when sub-domain security administrator clicks "user" node.
10.3 User group management

10.3.1 Default user group
NView NNM provides three default user groups for system monitoring, maintenance, and
security management. Generally, it needs to create ordinary according to the actual usage
situation of network management to assign NE and subnet management domain range and
specific operation authority so as to achieve hierarchical, decentralized authority and
decentralized domain management.
 "Administrators" user group: users in this user group have the highest user authority, i.e.
the super-administrator user group.
 "Security administrator group": users in this user group have the highest security
management authority and can manage all the management domains as well as create
sub-domain security administrator group.
 "Sub-domain security administrator group": users in the user group have security
management authority and can view security management logs. The specific differences
are as follows:
─ The "security administrator group" can manage all the management domains, while
"sub-domain security administrator group" can only take security management in
sub-domain.
─ "Sub-domain security administrator group" has not set access control list, log policy
and security policy authorities.
313
Raisecom
In addition to the system default super administrator user "administrator", if a user

belongs to the "Administrators" user group but does not belong to the "Security
administrators group/sub-domain security administrator group", the user cannot take
security management. Each user can belong to multiple user groups, but cannot
belong to security administrator group and sub-domain security administrator group
simultaneously. Only the "administrator" users and users in security administrator
group/sub-domain security administrator group have security management authority.
The default user group does not support the delete operation, and the management domain and
operation authority are also somewhat different. User group and the union set of user
management domain and operation authority constitute the specific user authority. The
specific user group comparison is as follows.
Table 10-5 User group comparison table

User group Member Management Operation authority Can create user or not
domain
Administ Except Default to Except Except
rators "adminis manage "administrator" "administrator"
trator" "objects user, default users, default cannot
users, universal set", support "NMS create user
support i.e. all the application
to objects in operation universal
add/dele NMS, not set" and "Device
te support to operation universal
modify set", i.e. all
operation
authorities in NMS
(excluding security
management
authority), not
support to modify
Security Support Default to Default to support Can create Sub-
administr to manage all operation domain security
ator add/dele "objects authority of administrator user
group te universal set", "Security and ordinary user.
i.e. all the management", not
objects in support to modify
NMS, not
support to
modify
314
Raisecom
User group Member Management Operation authority Can create user or not
domain
Sub- Support Default no Default to support Can create Sub-
domain to management all operation domain security
security add/dele domain, support authority of administrator user
administr te to modify "Security and ordinary use; the
ator management", not created user
group support to modify management domain
is the subset or
universal set of Sub-
domain security
administrator
management domain
Ordinary Support Support to Support to assign Cannot create user
user to configure operation authority
group add/dele management in creation and
te domain in support to modify
creation and
support to
modify
10.3.2 Creating user groups

Please create one user group according to the following steps:
Step 1 In the main application view of user management, click Security Manager Object > User
Group in the left side to show the interface below.
After selecting Security Manager Object > User Group in the left tree list, click
on the left top corner of right interface and select user group list properties in the pop-
up dialog box.
315
Raisecom
Step 2 Click Create user group in the lower right corner if the interface, or right-click "User group"
in the left tree list and then click Create user group in the shortcut menu; in the pop-up
Create user group dialog box, select "Base info" to show the interface below to configure
user group name, full name and description information.

User group name Not null Input user group name.
User group full name – Input user group full name.
Type – Ordinary user group.
Description – Input user group description.
Step 3 In Create user group dialog box, click "Member" to show the interface below.
316
Raisecom
Click Add and select users belonging to this user group in pop-up dialog box, and then click
OK.
Step 4 (Optional) click Copy permissions from the user group to pop up ordinary user group list,
check one or more the created user group records, and then click OK to copy the management
domain and operation authority of selected user groups.
Click Copy permissions from the user to copy the permissions, the selected
management domain and operation permission will be cleared automatically, then
copy management domain and operation permission.
Step 5 In Create user group dialog box, click "Domain" to show the interface below. Click
Selection and select the user group operable management domain in the pop-up dialog box
317
Raisecom
Step 6 In Create user group dialog box, click "Operator privilege" to show the interface below.
318
Raisecom
Click Selection and select the user group available operator privilege in the pop-up dialog box,
and then click OK.
After adding an operator privilege in "Select operator privilege" dialog box, if users
need to add constantly, they need to select "Authorization object" and then select
operator privilege to add.
10.3.3 Modifying user groups

The system default "Administrator" and "Security administrator group" user group can only
modify the description. "Sub-domain security administrator group" can also modify
management domain so as to divide multi-level management. The customized created
ordinary user group can modify the name, description, management domain and operation
authority.
When user group user is modified, if the modified member is logging in client, the
client will prompt that "Your authority has been changed, please login again and click
OK to exit!" at this time, the user cannot continue the operation but click OK to close
client. After login again, the properties of modified user will take effect.
page.
319
Raisecom
Step 2 In "User group" on left "Security management object", click a user group, it will show user
group properties to modify in the right side of interface. The modify interface is same to the
add interface.
Step 3 When the ordinary properties are modified, click Apply to complete the modification. When
the management domain and operation authority are modified, click OK.
10.3.4 Deleting user groups

When the user group is deleted, the user "Subordinated user group" will also delete this user
group and delete the user group authority.
The steps to delete user group:
Step 1 Click Security > User Management in system main menu to open the main application
interface of user management.
Step 2 Click Security Manager Object > User Group to select a line of records from user group list,
click Delete in the lower right corner, in the pop-up Confirm dialog box, click Yes to
complete the operation.
10.4 Operator set management

Operator ser is a set of operation authorities. You can assign multiple operation authorities for
users through the operator set.
10.4.1 Default operator set

By default, the system provides six operator sets, which belong to "NMS application" and
"Network device" respectively and basically meet the operation authority division to device
configuration and NMS application. You can create customized operator set according to their
needs for detailed authority division.
Table 10-7 System default operator set description

Type Name Description
NMS Platform Contain all NView NNM operation
application maintenance authorities, including to view, modify and
staff operator set delete (Except security management
operation authority).
The system menu without authorities are
grey and unavailable.
Platform Contain all NView NNM operation
superintendent authorities, only can view alarm, resource
operator set and performance etc, network
management information.
The system menu without authorities are
grey and unavailable.
320
Raisecom
Type Name Description

NMS Contain all NView NNM operation
application authorities (Except security management
operation operation authority).
universal set
Network Device Contain the authorities to configure sync,
device maintenance view configuration, modify configuration,
staff operator set pre-configure management and batch
configure management.
For example: can enter NE management
interface to modify the configuration.
Device Only have authority to view NE device
superintendent configuration.
operator set For example: can enter NE management
interface to view the configuration.
Device Contain all operation authorities of NE
operation device.
universal set
10.4.2 Creating operator set

In order to facilitate user management, you can create operator set according to their needs.
The steps are as follows:
Step 1 In user management main application view, click the left Security Manager Object >
Operator Set to show the following interface.
321
Raisecom
Select Security Manager Object > Operator Set in the left tree list, click in the
left top corner of right interface, the select the operator set list displayed properties in
the pop-up dialog box.
Step 2 Click Create Operator in the lower right corner of the interface, in the pop-up Create
Operator dialog box, select "basic info" to show the following interface and configure the
type, name and description information.
322
Raisecom

Type NMS Select operator set type.
application
Network
device
Name Not null Input operator set name.
Description – Input operator set description information.
Step 3 (Optional) click Copy Operator to pop up the corresponding operator list according to the
operator type, check one or more operator records and then click OK to copy the selected
operator members.
Step 4 In Create operator dialog box, click "Member" to show the following interface.
323
Raisecom
Click Selection and select the operations belonging to this operator set in the pop-up dialog
box, then click OK.
10.4.3 Modifying operator set

Customized operator set supports to be modified; user can modify operator set and all user
authorities with this operator set.
When the operator is modified, if the modified operator user is logging in client, the
client will prompt that "Your authority has been changed, please login again and click
OK to exit!" at this time, the user cannot continue the operation but click OK to close
client. After login again, the modified operator set will take effect.
page.
Step 2 In the left "Operator set" of "Security management object", click an operator set to show the
basic information and member properties of operator set to modify. The properties in modify
interface are the same to the properties in add interface.
Step 3 After the basic information is modified, click Apply. To modify member properties, in the
Selection dialog box, click OK to complete the modification.
324
Raisecom
10.4.4 Deleting operator set

Please select the divided operator set not needed according to the following steps. By default,
the operator set does not support the delete operation.
Step 1 Click Security > User Management in system main menu to open the main application view
of user management.
Step 2 Click the left Security Manager Object > Operator Set and select a line of record in
operator list, click Delete in the lower right corner of interface, in the pop-up Confirm dialog
box, click Yes to complete the operation.
10.5 Access control list management

10.5.1 Creating access control list
You can create access control list according to their needs. The steps are as follows:
Step 1 In system menu bar, click Security > Access Control List to pop up the following dialog box.
Step 2 Click Add in the bottom of interface, in the pop-up interface, you can configure IP address or
network segment access control list and the access control list of IP address range.
 The interface to configure IP address or network segment access control list is shown as
below.
325
Raisecom
Figure 10-10 Add an IP address

IP address or For example: Input single IP address or
network Single IP address: network segment.
segment 10.10.10.10
Network segment:
10.10.10.16/255.255.255.0
Description – Input access list description
information.
 The interface to configure access control list of IP address range is shown as below.
326
Raisecom
Figure 10-11 Configuring IP address range
Figure 10-12 Configuration parameter description

Begin IP For example: Input begin IP address.
address Begin IP address:
10.0.0.1
End IP For example: Input end IP address.
address End IP address:
10.0.0.254
Description – Input access list description
information.
10.5.2 Modifying access control list
You cannot modify, delete the system default existed access control list 0.0.0.0–
255.255.255.255.
Please modify access control list according the following steps:
Step 1 In system menu bar, click Security > Access Control List to select the access control list to
modify in the pop-up dialog box.
Step 2 Select a record and click Modify to pop up Modify access control system interface to modify
access control information.
327
Raisecom
10.5.3 Deleting access control list

Please delete the added access control list not needed according to the following steps:
Step 1 In system menu bar, click Security > Access Control List to select the access control list to
delete in the pop-up dialog box.
Step 2 Select a record and click Delete to pop up Confirm dialog box, click Yes to complete the
operation.
10.6 Security policy management

NView NNM security policy management contains: password policy management and
account policy management.
10.6.1 Password policy management

Through password policy management, administrator can set the user password length,
character rules to prevent password cracking and improve security.
To modify or reset the password will be restricted by password policy, and it will pop up the
corresponding error prompt when the password is not in line with the policy.
Click Security > Security Strategy in system menu, in the pop-up dialog box, select
"Password policy" tab, the parameter description is shown in the table below; when the
configuration is complete, click OK.

Minimum user 6–16 Configure the minimum
password Default value: 6 password length restriction for
length non "administrator" user.
Minimum 6–16 Configure the minimum
admin Default value: 6 password length restriction for
password "administrator" user.
length
Maximum 6–16 Configure the maximum
password Default value: 15 password length restriction for
length all users.
Mdinimum 3–16 Configure the number of
differences Default value: 3 different characters between
between new new password and old
and old password.
password
characters
 0: not to set the minimum
Minimum day Configure the time interval to
of password password age days modify password; user cannot
 1–999
kept modify password within this
Default value: 1 interval.
328
Raisecom

 0:not to set the minimum
Minimum Configure the minimum
number of number of letters number of letters in password.
 1–16
characters in
password Default value: 0
number of number of capital letters number of capital letters in
 1–16
uppercase password.
characters in Default value: 0
password
number of number of lowercase number of lowercase letters in
lowercase letters password.
 1–16
characters in
password Default value: 0
The shortes Configure the minimum
length of the number of digitals number of digitals in
 1–16
password password.
Default value: 0
number of number of special number of special characters in
special characters password. The special
 1–16
characters in characters contain @, #, %, *,
password Default value: 0 &, +, - and blank space.
 No requirement (default)
The maximum Configure whether the user
 Cannot contain the
same characters name and password can be the
between user complete user name same or partly the same.
 Cannot contain the
name and
password connection characters
numbers in user name
The number of 1–16 Configure the number of
connection Default value: 2 characters cannot be the same
characters not in user name and password.
in user name Only when the maximum
number of connection
characters in user name and
password selects "Cannot
contain the number of
connection characters in user
name", the parameter can be
configured.
329
Raisecom

 Checked: Use password
Can't contail Configure whether the
the word from dictionary to check password can use vocabulary
 Unchecked (default): not
password in password dictionary.
dictionary use password dictionary
to check The system provides a
password dictionary, which
stores the common weak
password; check this
parameter to check whether
the password is in the
dictionary, if yes, it will pop
up error prompt in password
configuration.
 Checked: cannot be user
Can't be reverse Configure whether the
order of user name descending password can be user name
 Unchecked (default): No
name descending.
restriction
For example, user name is
ABC123, check this
parameter, the password
cannot be 321CBA.
 Checked: cannot have
Can't have four Configure whether the
or more four or more consecutive password can have four or
repeated repeating characters more consecutive repeating
characters characters.
restriction
For example: check this
cannot contain AAAA.
 Checked: cannot be the
Can't be Configure whether the
increasing or numbers or digitals password can be the numbers
decreaing ascending or descending or digitals ascending or
number or letter descending.
sequence restriction
For example: check this
cannot be ABCDEF.
10.6.2 Account policy management

Through account policy management, administrator can set the user name length and lock
rules to improve security.
To create user is restricted by user name length, and error password is restricted by lock rule,
and at the same time provide password expiration warning configuration.
Click Security > Security Strategy in system menu, in the pop-up dialog box, select
"Account policy" tab, the parameter description is shown in the table below; when the
configuration is complete, click OK.
330
Raisecom

User name 1–32 Configure the minimum length
mini length Default value: 6 of user name.
 Checked: permanently
Permanently Configure whether to lock user
locked locked when the times to account permanently when it
input password reach reaches specified times.
specified times
 Unchecked (Default): the
password will unlock

automatically according
to "Auto-unlock time"
when it reaches specified
times
Auto-unlock 1–1440 Configure auto-unlock time. The
time (minute) Default value: 1, unit: user account will be locked
minute when the times to input
password reach the specified
times, wait for this time, the
account will unlock
automatically and then user can
login again.
This parameter can be
configured only when the
"Permanently locked" is
unchecked.
ALocak 1–99 Configure the times of wrong
automatically Default value: 4 password to lock user account.
after a few User account will unlock
times automatically in reaching auto-
froming unlock time when the
entering the "Permanently locked" is
wrong unchecked. When the
number "Permanently locked" is
checked, super administrator or
security administrator will
unlock manually.
331
Raisecom

Password 1–30 Configure the days to prompt
expiration Default value: 1 that user password is expired in
warning days advance.
The expiration days of user
password are configured by "the
longest remaining days of
password" in user general
properties; click Security >
User Management in system
menu and select user name in
security management objects to
view the general properties.
The warning prompt can be
popped up only when the user
has logged in client.
 Checked: super
Admin will Configure whether super
never be administrator user will be administrator user
locked restricted by lock rule "administrator" is restricted by
when the password is lock rule.
wrong
 Unchecked (default):
super administrator user

will not be restricted by
lock rule
10.7 Monitoring user operation

Super administrator or security administrator can monitor the login users' operations. Open
"Online user operation" interface, the system begins to update the interface list to show all
users' operations and take a record of logs. When the "Online user operation" interface is close,
the operation record list in this interface will be cleared automatically, but the recorded logs
cannot be cleared.
In the system menu bar, click Security > Online User Operation to show the following
interface:
332
Raisecom

Operation user Show operation user name.
Operation name Show operation classify and name.
Operation UE Show operation terminal IP address.
Operation object Show user operation object.
Operation time Show operation time, correct to second.
Operation result Show operation result.
 Successful
 Failed
Description Show operation description.
 On the top of display interface, you can set the page size, i.e. the number of user
operations.
 You can click to view the real-time information of user operations.
 Click in the left top corner of the interface, select online user operation
displayed properties in the pop-up dialog box.
10.8 Online user management

Online user management contains online user monitoring and force user offline functions.
333
Raisecom
10.8.1 Monitoring online users

You can view the current system login user information through online user monitoring
function.
 Click Refresh to view real-time online user information

 Only Super administrators can view the current online user information.
The steps to view the current online user information:
Step 1 In the system menu bar, click Security > User Management, in the right side security
management object tree, click "Online users".
Step 2 The right side interface can show the detailed information of current login users.

User name Show the current login user name.
User type Show the current login user type.
IP address Show the current user login system IP address.
Login time Show the current user login system time, correct to second.
Host name Show the current user login system located host name.
Description Show description.
Select Security Manager Object > Online User in the left tree list, click in the
left top corner of right side interface, you can select online users list displayed
properties in the pop-up dialog box.
10.8.2 Forcing user offline

To force the user to exit login client, the super administrator can force the currently logged
user offline.
The steps to force user offline:
Step 1 In the system menu bar, click Security > User Management, in the right side security
management object tree, click "Online users".
Step 2 In the right side current login user interface, select the force offline users located line, click
Force user to exit in the lower right corner.
Step 3 In the pop-up Confirm dialog box, put forward the reason, and then click OK to complete the
operation.
334
Raisecom
10.9 User login modes

Super administrator user "administrator" can configure NMS user login mode.
 Multi-user login mode: NView NNM default login mode, run multiple clients login for
network management. NView NNM will recover to multi-user login mode automatically
in each time restart.
 Single-user login mode: only allow the super administrator user to user client login, other
users can not login in the mode (It will prompt that "Currently, the system login mode is
single-user login mode, only the super administrator user can login the system!"). The
single-user login mode is generally used in upgrade and maintenance so as to avoid the
incorrect operation from multi-user login.
Step 1 In NMS main menu bar, click System > Preference to open the system setting interface.
Step 2 In the left side of the interface, click "System login mode", the right side will show the
currently used login mode.
Step 3 Click to select the login mode and then click Apply to perform the configuration.
Step 4 To change "Multi-user login mode" to "Single-user login mode", it will pop up confirmation
prompt "This operation will make currently logged all online users except administrator user
force quit!", click Yes to pop up the prompt "When this operation takes effect, only one
administrator use logins to this service and hope to change to multi-user login mode when the
operation is complete!", click Yes to perform the operation. At this time, if there are other
users to login client, the client interface will prompt that "Super administrator user has set the
NMS login mode as single-user login mode, click OK to exit!", click OK, the system will exit
client automatically and cannot login again.
Regardless of any configuration, restart NView NNM, the user login mode will always
be configured as "Multi-user login mode" automatically.
If the single-user login mode is configured, only the super-administrator can log in to
the system. The super-administrator exit from the current client and re-log in to the
system through another client. Only one super-administrator can log in to the system
simultaneously.
10.10 Log strategy management

NView NNM log strategy is default to take a record of all user operations, which does not
need to configure generally. The steps to set user operation log strategy:
Step 1 In NMS main menu bar, click Security > Log Strategy to pop up the following interface.
335
Raisecom
Figure 10-13 Log strategy management
Step 2 In the text box on top of the interface, input the operation name to record logs, and click
to search. After the search is complete, check this operation, click OK.
After the log strategy is modified, restart the server.
336
Raisecom
NView NNM Operation Guide 11 System service management
11 System service management
This chapter mainly introduces how to manage system service and schedule service, and how
to use system events to trace the operation status of service, including the following sections:
 Overview
 System service management
 Schedule service management
 Tracing service operation status
 Common services descriptions
11.1 Overview
NView NNM provides a frame for application service management to manage various
application services. NView NNM system defines two types of application services:
 System Service: Services that will be provided from the startup of the service to the
closedown of the system.
 Schedule Service: The principle of the service is to execute a command by a frequency
(daily, a day in a week, time of a day in a month) in a specified time period.
11.2 System service management

11.2.1 Starting/Stopping system service
To start or stop system service, please follow the instructions below:
Step 1 Click Service > System Service on the system menu bar, "System Service" window with
system service list is displayed.
337
Raisecom
Figure 11-1 System service

Right-click a service and then click Start or Stop.
Step 2 After starting or stopping a specified service, the running status of the service will be modified
accordingly. If any fault occurs, the system will inform the user of it.
Step 3 Select a service, right-click on the selected record, and select View Log on the shortcut menu,
the "System Events" window with system event list will open up. The results of start/stop
system service operations will be displayed on the system event list.
11.2.2 Editing system service properties

To edit system service properties, please follow the instructions below:
Step 1 Click Service > System Service on the system menu bar to open the "System Service"
window.
Step 2 Select system service in the system service list. If the status of the selected service is
"Running", please stop the service firstly.
Step 3 Right-click on the selected records, and click Edit on the shortcut menu, an "Edit" dialog box
will pop up:
338
Raisecom
Figure 11-2 Editing system service properties

Step 4 Edit the properties in the dialog box and click Apply to save the modifications. You can click
the button Close to close the dialog box directly.
If the selected service requires advanced parameters to be set up, the button
Advance… will be usable. Click the button and the "Setup Parameters" dialog box
will pop up.
11.3 Schedule service management

11.3.1 Starting/Stopping schedule service
To start or stop schedule service, please follow the instructions below:
Step 1 Click Service > Schedule Service on the system menu bar, the "Schedule Service" window
with schedule service list will turn up:
339
Raisecom
Figure 11-3 Schedule Service

Step 2 Select a service on the schedule service list, right-click on the selected record. Click the button
Start to start a "Stopped" service; or click the button Stop to stop a "Running" service.
Step 3 After starting or stopping a specified service, the running status of the service will be modified
accordingly. If any fault occurs, the system will inform the user of it.
Step 4 Select a service, right-click on the selected record, and select View Log on the shortcut menu,
the "System Events" window with system event list will open up. The results of start/stop
schedule service operations will be displayed on the system event list.
11.3.2 Editing schedule service

To edit properties of a schedule service, please follow the instructions below:
Step 1 Click Service > Schedule Service on the system menu bar to open the "Schedule Service"
window.
Step 2 Select a service in the schedule service list. If the status of the selected service is "Running",
please stop the service firstly.
Step 3 Right-click on the selected records, and click Edit on the shortcut menu, an "Edit" dialog box
will pop up:
340
Raisecom
Figure 11-4 Editing schedule service properties

Step 4 Edit the properties in the dialog box and click Apply to save the modifications. You can click
the button Close to close the dialog box directly.
11.4 Tracing service operation status

NView NNM system provides a "System Event Management" component to record operation
events of the system, including the startup and stop of system service/schedule service, the
running status of services, and the schedule of the services. You can trace the operation status
of a service by viewing the system event list. The source, report time and description of
services are also displayed on the system event list.
Step 1 Click Log > System Event at the system menu bar to display a window, as shown in Figure
11-5.
Step 2 Right-click a record and click Property to display a dialog box, where you can view detailed
information about an event.
Step 3 Click at the tool bar of to display a Query panel, where you can set some conditions for
querying system events.
For detailed descriptions about log information, see section 12.6 Querying system logs. For
detailed description of query panel, see section 2.5 Common query interface.
341
Raisecom
Figure 11-5 System Event
11.5 Common services descriptions

11.5.1 SNMP trap receiving service
The SNMP trap receiving service is responsible for receiving SNMP trap message. Alarm
events from network devices can only be received properly when the SNMP trap receiving
service is enabled.
You can set up advanced parameters for this service in the "Setup Parameters" dialog box.
Step 1 Click Service > System Service to display a window.
Step 2 Right-click a SNMP Trap Receiving Service record and then click Edit to display a window.
Step 3 Click Advanced… and a "Setup Parameters" dialog box is displayed.
342
Raisecom
Figure 11-6 Parameters for SNMP Trap Receiving Service

The following parameter of the service can be edited in the "Setup Parameters" dialog box:
 Trap Port: The system will receive Trap at the port specified by the user. The system uses
Port 162 by default. Please note that the specified port should be identical with the trap-
transmitting target port of the device.
 Filter Recovery Alarms: Tick this item to filter recovery alarms, all recovery alarms will
not be displayed anymore on the current alarm list. The recovery alarms will enter
history alarms database directly and do not affect the recovery alarm receiving function.
 Compress Repeated Alarms as one piece of alarm record, the "occur times" increase 1:
Repeated alarms are alarms of the same type and from the same location. Tick this item,
the system will only count the repeated alarm as an existing one and increase the
counting; uncheck it, the repeated alarm will be reported as a new alarm.
 Discard Unidentified Alarms: The system will resolve alarms of unregistered types or
from unregistered devices as unknown alarms. If this function is selected, the system will
filter all unknown alarms.
 Auto Clear Recovered Alarm: When system receives alarm recovery information, it will
change the alarm status of the fault to "Recovered". Select the "Auto Clear Recovered
Alarm" item, recovered alarm will become historical alarm automatically and its
operation status will become "Cleared". If this item is not selected, "Recovered" alarm
will be displayed in the current alarm list and the alarm information can only be cleared
manually. The alarm will be listed in historical alarm list after the manual clearing.
 Discover the device where the unknown traps coming from: If the function is enabled,
when an unknown alarm is reported from an unregistered node, the system will start a
node auto-discovery process. The process will recognize the device type of the node,
acquire its resource information and automatically creates a node in the topology. This is
an indirect way of node auto-discovery. This item is disabled by default, once enable it,
the discovered node will be added into "unregistered device" subnet.
343
Raisecom
11.5.2 Trap storm defending service

The trap storm defending service defends the system against challenges from trap storm to
some extent. Numbers for received alarms every 2 minutes should not exceed the maximum
alarm number. (For example, 200 pieces. The received alarms refer to all alarms received by
the NView NNM regardless of alarm type and alarm source.) After the service is started, if
numbers for received alarms during 2 minutes exceed the maximum alarm number, the
NView NNM will not receive alarms until the next 2 minutes.
Step 2 Right-click a Trap Storm Defending Service record and then click Edit to display a window.
Figure 11-7 Parameters for Trap Storm Defending Service

The following parameter of the service can be edited in the "Setup Parameters" dialog box:
 Interval: by default, it is fixed to 2 minutes.
 Max alarm count: the maximum number for received alarms every 2 minutes. It is
recommended to set the value smaller than 1200.
11.5.3 Alarm mail relay service

The alarm mail relay service transfers an alarm event to a specified mail sending server and
informs the user of the alarm event by e-mail. For details of this service, please refer to the
content of alarm event management. Please note that the service can only go into effect when
the related information of the server sending e-mails has been correctly set up.
In this service, you can only configure parameters for sending e-mails. If you use E-
mail to forward alarms, you need to configure e-mail address, alarm level and alarm
source. For detailed information, see section 7.9 Trap notification.
344
Raisecom
Step 2 Right-click a Alarm Mail Relay Service record and then click Edit to display a window.
Step 3 Click Advanced… and a "Setup Parameters" dialog box is displayed. The E-mail address,
account and password are used to connect the SMTP server for sending E-mails.
345
Raisecom
Figure 11-8 Parameters for Alarm Mail Relay Service_SMTP server tab page
Figure 11-9 Parameters for Alarm Mail Relay Service_mail content tab page
The dialog box has two pages:
 "SMTP Server" page: You set up parameters for SMTP mail sending server.
 "Mail Content" page: You can define templates for mail content using the keywords
provided by the system.
346
Raisecom
The "SMTP Server" page requires the following parameters to be set up:
 SMTP Server: the domain name or IP address of the SMTP server
 Port: Port for SMTP service on the SMTP server. Port 25 by default.
 Validate account when sending mail: Tick this item, the password of the mail account
will be required and the system will validate the account before sending the mail.
 Account: The complete user account information on SMTP server.
 User name: user name of administrator on SMTP server.
 Password: The password the administrator used on the SMTP server is required if the
user choose to "Validate account when sending mail".
 Please click the button Test Connection to check whether all the settings are valid. If the
test fails, please modify the input information for the above parameters until the test
succeeds.
You can customize the content of the mails on the "Mail Content" page. NView NNM system
provides the users with some keywords. All keywords are bracketed in point brackets and will
be converted to corresponding alarm content in the mail. You can insert a keyword to the
content of mail by selecting a keyword on the drop-down list of keywords and clicking the
button Insert.
11.5.4 Alarm SMS relay service

The alarm SMS relay service transfers an alarm event to a specified SMS sending device and
informs you of the alarm event by sending a SMS message to the SMS modem. For details of
this service, please refer to the content of alarm event management. Please note that the
service can only come into effect when the connection by which the SMS message will be
sent is valid.
In this service, you can only configure parameters for sending shor messages. If you
use short messages to forward alarms, you need to configure the mobile number,
alarm level and alarm source. For detailed information, see section 7.9 Trap
notification.
Click the button Advanced… and the "Setup Parameters" dialog box will pop up.
Step 2 Right-click an Alarm SMS Relay Service record and then click Edit to display a window.
347
Raisecom
Figure 11-10 Parameters for Alarm SMS Relay Service- GSM mode
Figure 11-11 Parameters for Alarm SMS Relay Service-CDMA mode

The dialog box has two pages:
 "Serial Port" page: The serial port parameters for the connection to the SMS modem.
Please note that the SMS modem connects to the host on which the server locates. As a
result, these parameters are parameters of the host on which the server locates, not those
of the host on which the client locates.
348
Raisecom
 "Short Message Content" page: You can define templates for short message content using
the keywords provided by the system. Its function is identical to the one of Mail Content
of Alarm Mail Relay Service.
On the Serial Port tab page, SMS modems are classified into Global System For Mobile
Communication (GSM) modem and Code Division Multiple Access (CDMA) modem.
─ Parameters for serial port should be configured based on the SMS modem type.
Parameters for devices connected by the serial port should be identical.
─ The length for the short message contents is restricted in 70 Chinese characters or 140
English characters.
─ If the format is set to Text, you cannot create a Chinese short message. To create a
Chinese short message, set the format to PDU or Unicode.
Table 11-1 Parameters for the serial port

SMS  GSM Select a SMS modem that is used to

modem  CDMA forward alarm short messages.
Format  Text Select a format for the alarm short

 PDU messages.
 Text: only support English alarm
 Unicode
short message can be sent.
 PDU: adopt GSM modem and
support both Chinese and English
alarm short messages.
 Unicode: adopt CDMA modem
and support both Chinese and
English alarm short messages.
Contry By default, it is set Enter the country code.
code to 86, refering to
China.
Serial port By default, it is set Enter the serial port used to connect
to COM1. the SMS modem.
Baud rate  9600 (GSM) Select a baud rate for the serial port.
 115200 (CDMA)
Parity  None (default) Select a parity for the serial port.
 Odd
 Even
 Mark
 Space
349
Raisecom
Data bits  5 Select a data bit for the serial port.

 6
 7
 8 (default)
Stop bits  1 (default) Select a stop bit for the serial port.
 1.5
 2
11.5.5 Trap forwarding service

NView NNM provides Trap PDU alarm forwarding service over SNMP. This service
transmits alarm information to Trap and reports to specified Trap server. You can order alarm
contents included in Trap and Trap target address, port according to actual need.
Step 2 Right-click a Trap forwarding Service record and then click Edit to display a window.
350
Raisecom
Figure 11-12 Parameters for Trap Target IP Setting
Figure 11-13 Parameters for Trap Message Setting

The dialog box contains two pages:
351
Raisecom
 Trap Target IP: allow you adding, modifying and deleting Trap server address and port.
 Trap Message: allow you setting message transmitting format and contents.
The following parameters can be set in "Trap Target IP" page:
 Target IP: the IP address of target Trap server.
 Target Port: the port of target Trap server receiving Trap packets (0-65535).
"Trap Packet" page provides an entire alarm attribution, OID, type list and edit tool based on
"Keyword". You can edit the transmitting format and contents according to need. The system
will find the right OID according to keyword of the alarm attribution and form OID-Value
format during transmission, thus an entire Trap packet can be transmitted to specified Trap
server.
11.5.6 Alarm forwarding service

NView NNM system provides alarm forwarding service based on Socket. The service send
the alarm information (filtered) in XML format to the receiver by providing alarm real-time
forwarding service on a Socket port. To receive alarm information through this service, please
set up an alarm receiving client following related specifications.
Step 2 Right-click an Alarm forwarding Service record and then click Edit to display a window.
352
Raisecom
Figure 11-14 Parameters for Base Info Setting
Figure 11-15 Alarm relay content configurations

The "Setup Parameters" dialog box has two pages:
353
Raisecom
 "Base Info. Setting" page: Information of service port, service parameters and client
access control, and etc. can be set up.
 "Alarm Relay Content" page: You can set up the format and content of the information
to be sent.
On the "Base Info Setting" page, the following parameters can be specified:
 Service Port: The port the service monitors. Please note that the port number ranges from
1024 to 65535 and the port must not be occupied by other service. Otherwise, the service
may fail to get started.
 Alarm Relay Max Client: The maximal number of alarm receiving clients allowed.
 Alarm Relay Timeout (second): After an alarm relay, if the client does not reply within
this specified time period, the system will regard the operation as failed.
 Alarm Relay Retry: If the alarm relay fails, the service will retry for specified times. If
there is still no response from the client, the system will regard the connection to the
client as ineffective and cut the connection to the client to save system resources.
 Client Access Control List: Only clients on the list are allowed to connect to the service.
You can edit the list using the buttons on the left.
The "Alarm Relay Content" page provides a text editing area and editing tools based on
"keywords". You can edit the format and content of the alarm relay information in the editing
area using the XML format and keywords provided by the system. The keywords correspond
to certain property information in the alarm information to be sent and the information sent is
a piece of text information in a specified format. All keywords supported by the system are
displayed on the drop-down list of "Key Word", you can select and insert them into the text.
For the details in the development of alarm receiving client (e.g. communication protocol,
message format, etc.), please refer to related guide manual.
In fact, the service is an integration of NView NSIA (Socket northbound interface)

function into NView NNM system. All developed NView NSIA clients are able to
connect to NView NNM alarm transmit service. The communication protocol and
message format are forward compatible.
11.5.7 Batch configuration service

The batch configuration service has the server call the configuration commands module
periodically to configure a number of devices at one time periodically. No parameter setting is
required for the service at this stage.
11.5.8 Link auto detect service

This service responses on start/stop link auto-discovery function based on RNDP (Raisecom
Neighbour Discover Protocol, used for switch cluster management over Raisecom private
protocol) or LLDP (Link Layer Discovery Protocol, used for network device announce its ID
and performance in local sub-net over IEEE802.1ab). This service can discover link among
devices that enable RNDP or LLDP protocol periodically.
Step 2 Right-click a Link Auto Detect Service record and then click Edit to display a window.
354
Raisecom
Figure 11-16 LLDP Link Discover configurations

You can set below information in the above dialog box:
 Protocol: to configure link auto-discovery protocol, RNDP or LLDP for options.
 Cycle (hour): to configure executing period for link auto-discovery, by default, it
executes every 24 hours.
11.5.9 Syslog receiving service

The Syslog receiving service receives standard Syslog information, which needs to use
UDP514 port. Only when the server enables and UDP514 port can communicate normally,
standard Syslog information can be received correctly. No parameter setting is required for
the service at this stage.

11.5.10 Current alarm auto-clearing service

In some applications, current alarms accumulate to a huge amount every day. Without proper
maintenance, a large number of new-come current alarms will influence the performance of
the NView NNM system. The current alarm auto-clearing service will leave the current alarms
received within a period of time on the current alarm list and move the current alarms
received out of the time period to the historical alarm list. The number of the alarms on the
current alarm list will be kept within a limit.
Step 2 Right-click a Current Alarm Auto-Clearing Service record and then click Edit to display a
window.
355
Raisecom
You can
Figure 11-17 Parameters for Current Alarm Auto-clearing Service

The following parameters can be set up in the above dialog box:
 Alarm Keeping Period (Hour): The system provides 7 levels from 1 hour to 72 hours for
choice. The default setting is 72 hours.
 Execute Interval (Second): The time interval by which the system checks the number of
current alarms in the current alarm list. The default value is 300 seconds.
11.5.11 Resource synchronization service

The resource synchronization service is provided in form of timing task, to responsible for the
synchronization of the device configuration information and the resources and topology data
in the database, and keeps the information in the database being consistent to the information
of the devices. Working with the offline device detection service, the resource synchronization
service realizes resource periodical synchronization with the cycle of the offline detection
service. Please note that if the offline device detection service is stopped, the resource
synchronization service will not be able to realize device resources periodical and automatic
synchronization. The operating status of the offline device detection service will not affect the
manual resource synchronization function.
Step 1 Click Service > Schedule Service to display a window.
Step 2 Right-click a Resource Synchronization Service record and then click Edit to display a
window.
356
Raisecom
Figure 11-18 Parameters for Resource Synchronization Service

You can set up the following function in the dialog box:
Report alarms when resource changes: When this function is enabled, if the system detects a
resource change, like newly-found, loss and model change, NView NNM will automatically
generate a piece of alarm information to describe the change. Generally, the device will
automatically report its changes via traps. This function is specially designed of the occasions
that there is no realistic Trap mechanism (e.g. No trap target has been specified for the device).
In these circumstances, if changes happen on the device, the system will generate alarms to
inform the administrator of them.
11.5.12 Syslog auto-clear service

The Syslog log auto-clear service clears Syslog log data periodically and on schedule, and
decides whether to save the cleared Syslog log data to the host where the server locates or to a
specified FTP server.
Step 2 Right-click a Syslog Auto-Clear Service record and then click Edit to display a window.
357
Raisecom
Figure 11-19 Parameters for Syslog Data Auto-clear Service

You can edit the following parameters in the dialog box:
 Clear: clear data several months ago from network management system, which cannot be
recovered.
 Save Cleared Data: You can choose to save or not to save the data to be cleared. If the
"Save Cleared Data" item is ticked, then the other six parameters for saving the data on
the dialog box are editable. If the "Save Cleared Data" is not ticked, then the data will
not be saved.
 Save Directory: The default saving directory is "syslog". You can specify a directory and
the system will save the cleared data in this directory after modification.
─ If you have not specified the parameter "FTP Server", the "Save Directory" should be
an absolute path (e.g. D:/backup/syslog). If you have not specified the parameter
"Save Directory" also, the cleared data will be saved to the sub directory
"/server/syslog" under the installing directory of the server.
─ If you have specified the parameter "FTP Server", the "Save Directory" should be a
relative directory under the root directory of the FTP server (e.g. syslog). The system
will upload the cleared data to the sub directory "/syslog" under the root directory of
the FTP server via FTP protocol. If you have not specified a "Save Directory", the
system will upload the cleared data to the root directory of the FTP server directly.
 File Name: The prefix of the database file generated after the clearing. The format of the
name of the generated file is: File Name+"_"+Date and Time+".sql". For example:
syslog_2007-01-17 08.44.36.sql
 FTP Server: The IP address of the FTP server. The system will save the cleared data to
the FTP server with the specified IP address. If the "FTP Server" has not been specified,
the system will save the cleared data on the host on which the server locates.
 Port: The number of the port that corresponds to the FTP server. In general, port for FTP
server is Port 21.
358
Raisecom
 Login: "Anonymous Login" or "Standard Login". No User name and password are
required when log in anonymously.
 User: A valid user account that can log on the FTP server for "Standard Login".
 Password: A valid password for logging on the FTP server for "Standard Login".
11.5.13 Database backup service

The database backup service backs up the whole database periodically. You can specify the
calling cycle of the service and the patterns of backup. Two backup patterns are currently
available:
 Local file backup: The system backs up the data automatically under a specified file
directory on the host on which the server locates.
 Remote FTP backup: The system backs up the data automatically under a specified
directory on a specified FTP server.
Step 2 Right-click a Database Backup Service record and then click Edit to display a window.
Figure 11-20 Parameters for Database Backup Service

There are three pages in the dialog box: "Base Config", "Backup Config", and "Restore
Config". You can edit the following parameters on the "Base Config" page:
359
Raisecom
Basic configurations
 Save Directory: The default saving directory is "GeneralBack". You can specify a
directory and the system will back up the database file in this directory after modification.
The parameter has different meanings for different backup patterns.
─ Local file backup: If you have not specified the parameter FTP Server, the "Save
Directory" could be an absolute path (e.g. D:/backup/GeneralBack), or a relative path
like "$Installation path/server". If you have not specified the parameter "Save
Directory", the backup of the database file will be saved to the sub directory
"/server/GeneralBack" under the installing directory of the server.
─ If you have specified the parameter "FTP Server", the "Save Directory" should be a
relative directory under the root directory of the FTP server (e.g. GeneralBack). The
system will upload the backup of the database file to the sub directory
"/GeneralBack" under the root directory of the FTP server via FTP protocol. If you
have not specified a "Save Directory", the system will upload the backup to the root
directory of the FTP server directly.
 File Name: The prefix of the database file generated after the backup. The format of the
name of the generated file is: File Name +"_"+NNM Version+"_"+Date and Time+".sql".
For example: nnm5_5.3_2010-07-01 16.36.09.sql.zip.
 FTP Server: The IP address of the FTP server. The system will save the backup of the
database file to the FTP server with the specified IP address. If the "FTP Server" has not
been specified, the system will save the backup file on the host on which the server
locates. If the "FTP Server" has been specified, the system will save the backup file on
the FTP server.
 FTP Port: The number of the port that corresponds to the FTP server, port 21 by default.
 Login: "Anonymous Login" or "Standard Login". No User name and password are
required when log in anonymously.
 User: A valid user account that can log on the FTP server for "Standard Login".
 Password: A valid password for logging on the FTP server for "Standard Login".
Database backup/recovery
The database backup and restoration are realized by backup and restoration commands of the
database management system. As a result, the system needs the paths of the backup or
restoration tools and command parameters. The parameters that are required in the backup and
restoration process are:
360
Raisecom
Figure 11-21 "Backup Config" Page
Figure 11-22 "Restore Config" Page

The content of the above two dialog boxes are similar. The meanings of the parameters are
described as follows:
 Database: choose the database system under use. The database of Mysql, version 5.1.43
is presently supported.
 Backup/Restore tool path: a default path is provided by the system.
361
Raisecom
 Backup/Restore command: the commands for backup or restoration are different when
choose different database. A default command is provided by the system, and it is able to
satisfy most of the requirements. Please do not modify the commands unless there is
special requirement.
11.5.14 Database auto-repairing service

The database auto-repairing service is a schedule service that executes database repairing
command periodically. The service ensures the intactness and effectiveness of the database by
repairing damaged database table. The system will generate logs and save them to the folder
for logs on the server for each time of repair. No parameter setting is required at this stage for
the database auto-repairing service.
11.5.15 MAC link discovery service

This service is provided in a form of scheduled service. It is designed for tracing MAC
address of EPON NE management. By tracing MAC address, you can view the MAC address
record of a user device connected to the switch. And the maintenance personnel can
conveniently find the MAC address of the user device.
At the system menu bar, click Service > Schedule Service to display a window.
Right click a MAC Link Discovery and then click Edit to display a dialog box. Table 11-2
lists parameters of MAC link discovery service.
Table 11-2 Parameters of MAC link discovery service

Start mode  Manual Configure the mode for starting the
 Auto service.
 Manual: after starting the NMS Server,
you need to manually start this service.
 Auto: when the NMS Server is started,
this service is automatically started.

Cycle  Daily Configure the cycle when the service
 Weekly is performed.
 Monthly
Date  When the cycle is set to weekly, the Configure the date when the service
device can perform services at any day of is performed.
a week.
 When the cycle is set to monthly, the
device can perform services at any day of
a month.
Time – Configure the time when the service
is performed.
It is recommended to select a time
when fewer servies are performed,
for example, 3:00 am.
362
Raisecom
 The MAC link trace cannot be performed until a minimum of one MAC link
discovery service is performed.
 For performing MAC link trace, you must start the NView NNM data center
components and MAC link discovery service. By starting the NView NNM data
center server and configuring MAC link discovery service, NView NNM will collect
MAC addresses of user devices and save them to the database. By querying the
MAC link trace information in the database, you can view the connection
situations of user devices.
363
Raisecom
NView NNM Operation Guide 12 System maintenance
12 System maintenance
This chapter mainly introduces how to maintain the system using tools and services provided
by the system, how to maintain the database, and how to isolate and remove faults using
debug information, including the following sections:
 Overview
 Backing up database
 Recovering database
 Maintaining database
 System debug information
 Querying system logs
12.1 Overview
For an information management system, the security of data is essential. NView NNM system
provides a serial of services to guarantee the safety of the database. NView NNM system
provides database auto-backup service to back up database data periodically and on schedule,
database recovery tool to recover system data to a historical status, and several database
maintenance tools to keep the capacity of the database on a stable level.
Faults are unavoidable during system operating process. The key of system maintenance is
isolating and removing faults effectively and efficiently when faults occur. NView NNM
system's self-contained debug information export function ensures that the information of all
faults that occurs during the system operating process will be exported to log files. Technical
support engineers can locate and remove faults by these log files.
12.2 Backing up database

NView NNM system provides a "Database Backup Service" to back up the whole database
periodically and on schedule.
364
Raisecom
The backup service provided by the system is a backup of the whole database.
Currently, backup of the data in a single module, such as inventory data backup and
topology data backup, is not supported.
12.3 Recovering database

NView NNM system provides a database recovery tool to recover the database to a historical
backup status. The database recovery tool is an executable program with file name
"DBRetore.exe" and is located in the directory "$system installation directory/server". The
tool is executed by command line. To use this tool from a remote client, you have to log on
the host where the server locates and execute the program.
Before recovering the database, please make sure that the following conditions are satisfied:
 The program on server has been stopped.
 The system version of the database to be backed up conforms to the version of the
current system.
If the above conditions cannot be satisfied, the database recovery will not operate properly. To
recover the database, please follow the following steps:
Step 1 Under command mode, enter the directory "$system installation directory/server" and execute
the "DBRetore.exe" program. The system will require the user name and password for logging
on NNM5 client to validate the user profile. Press down "Enter" after inputting the user name
and the password.
Figure 12-1 Validating the Logon

Step 2 The system will require you to input the path of the directory where the backup file (ZIP
format) locates. Input the local directory of the file following the prompt (For remote FTP
backup, you have to download the backup file to local host), and press Enter.
365
Raisecom
Figure 12-2 Inputting the absolute path of the directory where the backup file locates
Step 3 The system will require the name of the backup file (ZIP format). Input the file name
following the prompt and press Enter.
Figure 12-3 Inputting the name of the backup file

Step 4 The system will start the database recovery. The time the recovery takes depends on the
amount of data. The system will inform you of a successful backup.
366
Raisecom
Figure 12-4 restoring the system

Step 5 Restart the server after a successful backup, the database will be recovered to the status of a
historical backup. If the system cannot complete the database recovery due to abnormities that
occur during the recovery process, system will restore the database to the status before the
recovery automatically.
12.4 Maintaining database

Long-time operating of the system will increase the data amount in the database, which will
affect the efficiency of the system. Some data, like log information, Syslog, and historical
alarm information, are generally useful within half a year and data of these types from half a
year before have little reference value. To prevent useless data from affecting the efficiency
and stability of the system, NView NNM system provides the following database maintenance
services:
 Current Alarm Auto-Clearing service: Automatically clear the current alarms received
out of the specified time period on schedule, and move the cleared records to the
historical alarm list.
 Syslog Log Auto-Clear Service: Automatically clear the Syslog data out of the specified
time period on schedule.
Click Service > Schedule Service on the system menu bar, the "Schedule Service" window
will turn up, and all the properties on the above services can be viewed on this window.
12.5 System debug information

NView NNM system has a complete debug information output mechanism. Information
generated during the operating process including fault information will be outputted to log
files. When faults occur, these log files will help technical support engineers locate the fault
and solve the problem.
There are three debug output levels:
367
Raisecom
 Maximal: All debug information will be outputted to log files. The level provides
comprehensive debug information for removing faults but will reduce the operating
efficiency of the system.
 Normal: Only error information will be outputted to log files. This level cannot provide
comprehensive debug information, but can ensure the operation efficiency of the system.
 Minimal: Only information of fatal errors will be outputted to log files. The output
information may be too little for debugging, but it will be affect the efficiency of the
system.
The default output level is "Normal". If system fault occurs, the "Maximal" level is
recommended. You can repeat the operation with fault until the fault occurs again, copy the
log files and send them to technical support staff for log analysis and fault removal. All log
files will be in the folders under the path "$system installation directory/server/logs" and
"$system installation directory/client/logs:
To modify the output level, please follow the steps below:
 Select System > Preference on the system menu bar to open up the "System Settings"
window.
 Open up "Debug Settings" page by clicking the button Debug Settings on the left.
 Select an output level on the drop-down list.
The "Maximal" output level is only recommended when fault occurs in the system
operating process, for the output of great amount of debug information will
considerably influence the operating efficiency of the system. "Normal" and "Minimal"
levels are recommended in normal operation. When output level is modified, the
modification will take effect after system restart.
368
Raisecom
Figure 12-5 Modifying the debug output level for the System
12.6 Querying system logs

Operations are recorded in the system log. By querying the system log, you can confirm
operations, the user who perform the operations, the begin time and the end time of an
operation.
The system log provides a commonly-used query panel. Click at the tool bar of the Log
Manager view to display a query panel. For detailed information about the query channel, see
section 2.5 Common query interface.
12.6.1 Entering log management view

At the system menu bar, click Log > Syslog to display a window. Log types are displayed on
the left side of the window. Click a log type and related log records are displayed on the right
area, as shown in Figure 12-6.
369
Raisecom
Figure 12-6 Log management view
12.6.2 System log types

System logs are classified into the following types:
 System event: record configuration operations performed on the NView NNM, such as
resource synchronization, various services. The services refers to service and scheduled
tasks that you can configure by clicking Service > System Service or clicking Service >
Schedule Service.
 System operation: record management operations that are performed by users through
the NView NNM, system operations are classified into add, modification, and deletion
operations, mainly including:
− Topology management
− Alarm management (fault management)
− Performance management
− Inventory management
− Template management
− Customer management
− Report management (statistics)
− Data center
− Data dump
− Tool operations (for example, using ICMP/SNMP Ping and Telnet)
370
Raisecom
Operation names of a system operation log contain information about all

management operations. You can query each management operation by setting the
operation name condition to LIKE and then entering an operation type.
 Device operation: record operations on a device performed by the EMS of the device.
 Login log: record information of the user logging in to the NMS client.
 Security manager log: record operations of the security management function of the
NView NNM. You can configure these operations by clicking Security at the system
menu bar. Only users in the security administrator group and sub-domain administrator
group can perform operations provided by the security management function.
 Syslog: record Syslog sent by a device. The NView NNM can be used as a Syslog server
to receive Syslog sent by the device. The receiving and analysis of the Syslog must
comply with the Syslog protocol format defined by RFC3164.
 To receive Syslog, you need to start the Syslog Receiving Service and use the
UDP 514 port. Only when the Syslog Receiving Service is started and the UDP
514 port works properly, will the NView NNM can properly receive standard Syslog
information from devices in the network.
 At the system menu bar, click Service > System Service to display a window.
 Right-click the Syslog Receiving Service record and then click Start to start the
service. By default, the service is stopped.
12.6.3 Descriptions of log information
System events
Table 12-1 System event log

Field Description
Event source Display the system service name or resource synchronization operations related
to the event.
Event type Display the event type, including notify, warning and error,
 Notify: notification information, indicating the operation is normal.
 Warning: an error occurs without influencing service operation. Or status for
a service monitor is close to the threshold.
 Error: a critical error occurs and service operation cannot be properly
performed.
Occurrence time Display the time when an system event occurs.
Description Describe a specified operation and its result.
371
Raisecom
System operations
Table 12-2 System operation log

Field Description
Operation user Display the user who perform the system operation.
Operation name Display the operation type and detailed operation.
Operation UE Display the IP address of the host where the NMS
Client is installed for peforming this operation.
Operation object Display the operation object.
Operation time Display the time when the operation is performed.
Operation result Display whether the operation is successfully
performed.
Description Describe detaled information about the operation.
Device operations
Table 12-3 Device operation log

Field Description
Operation user Display the user who perform the system operation.
Operation object Display the IP address for a device where the
operation is performed.
Operator result Display whether the operation is successfully
performed.
Login log
Table 12-4 Login log

Field Description
User name Display the user name.
372
Raisecom
Field Description
IP address Display the IP address of the host through which the

user logs in to the NMS Client.
Host name Display the computer name.
Login time Display the time when the user logs in to the NMS
Client.
Logout time Display the time when the user exits the NMS
Client.
Login result Display whether the user successfully logs in to the
NMS Client.
Description Describes detailed information about the the login
log.
Security manager log
Table 12-5 Security manager log

Field Description
Operation user Display the user who perform this operation.

Operation name Display the security management operation type and
detailed operation.
Operation object Display the operation object.
Operation result Display whether the operation is successfully
performed.
Syslog
Table 12-6 Syslog

Field Description
Facility Display the device that sends the Syslog.

Level Display the severity level of the Syslog.
373
Raisecom
Field Description
Time stamp Display the time when an event described by the

Syslog occurs.
This time refers to the time stamp generated by the
device.
Message Display the event content described by the Syslog.
The field information of the Syslog is decapsulated from the Syslog packets sent by
the device. For detailed valuing specifications, see RFC3164.
374
Raisecom
NView NNM Operation Guide 13 Data Dump
13 Data Dump
This chapter introduces how to dump system log, historical alarm, performance data by data
dump function and ensure performance of NView NNM database, including the following
sections:
 Overview
 Automatic dump
 Manual dump
 Checking dump conditions
13.1 Overview
The log, history alarm and performance data are important data for maintenance. Maintenance
staff can view maintaining record, history alarm information, device performance according
to these data. But with time going, the data amount become larger and larger and may lower
down NMS database performance, so NView NNM provides data dump function to solve this
problem.
Data dump function supports transferring log, history alarm and performance data out from
database to generate readable files and delete the same data from database. Then the NMS
database is ensured to run with high efficiency. Data dump function is in support of below
features:
 Automatic dump is in support of overflow dump and periodic dump.
 Automatic dump is in support of batch configuration.
 Manual dump is in support of immediate execution according to time range.
 In support of generating alarm information according to the capacity warning threshold.
 The dump data can be saved as csv or txt file, supporting automatic compression.
 In support of automatic delete dump data from database.
 The dump data file supports setting expire time, system automatic delete expired files.
 The dump data can be uploaded to FTP
Data dump function supports automatic dump and manual dump. Automatic dump is well
arranged and executed periodically, satisfying daily maintenance for NMS data dump; manual
dump is instance and executed immediately, satisfying customized dump requirement.
375
Raisecom
Data dump function provides default automatic dump configuration according to the common
condition in maintenance. After successfully installing NView NNM, system performs data
dump in accordance with default configuration. Maintenance staff can configure data dump
according to practical condition.
13.2 Automatic dump

Automatic dump is in support of overflow dump and periodic dump.
 Overflow dump is to configure dump according to data amount (amount of data).
 Periodic dump is to configure dump according to time range.
The two dump modes achieve independent monitor in system. System detects any mode
satisfies dump condition and will follow the configuration to transfer and save data.
You can configure the two modes at the same time or only take one mode of them. It is
suggested to enable and configures overflow dump function all the time, then it can avoid data
overflow and make sure NMS runs in order. For the large amount data like performance data,
it is suggested to configure periodic dump to ensure efficiency of database.
13.2.1 Configuration interface

Click System > Data Dump > Dump Config in NView NNM system menu to open data
dump configuration interface. The left interface is navigation tree; the right is the functional
configuration items.
376
Raisecom
Figure 13-1 Configuring data dump

The navigation tree displays the groups (like log, alarm, performance, etc.) and objects in
groups (like system log, history alarm, NE type, etc.). Click the object in group, the left of
interface will display related configuration items.
The groups in navigation tree and class-2 group in performance group (day, week,
month, year) also have related configuration items. The items are used for batch
configuration of objects in group (for example the different type logs, different types
NE performance data, etc.).
13.2.2 Procedures of automatic dump

The procedure for automatic dump shows as below figure. The two modes of periodic dump
and overflow dump achieve independent monitor in system. System detects any mode
satisfies dump condition and will follow the configuration to transfer and save data.
377
Raisecom
Figure 13-2 Procedure of automatic dump
13.2.3 Scenarios
Configuring single object

Data dump provides dump configuration for each object by default, which basically satisfies
dump requirement of NMS. You can click object in navigation tree (such as the system log,
history alarm, NE type, etc.) and then configure the object in the interface. Click OK after
configuration to shut down configuration interface.
During configuration of automatic dump, system will check the validity of data and
make sure you input valid data.
Configuring batch dump
You choose groups in navigation tree or class-2 group in performance group (day,
week, month, and year) for dump batch configuration items, the result will be applied
to all objects in the group and the earlier dump configuration will be replaced.
Dump batch configuration can configure all objects in group conveniently. You can configure
single object in group after batch configuration, system will dump according to the latest
configuration result.
Batch dump configuration shows as below figure. It indicates "Batch Configuration" interface
on the top of dump configuration item.
378
Raisecom
Figure 13-3 Batch dump configuration

Click OK after dump batch configuration to open dialog box as below figure to prompt you
operate on dump data type. Click to save configuration and shut down configuration interface,
click No to return configuration interface without saving.
Figure 13-4 Confirming batch configuration

Click Apply to open confirmation dialog for batch configuration. Click to save configuration
and shut down configuration interface, click No to return configuration interface without
saving.
379
Raisecom
13.2.4 Configuring overflow dump

Overflow dump means system dump data when data amount over the maximal capacity.
Following data generation time from old to new, overflow dump takes data out from database
and save into files, then delete the data from database. The procedure shows as below figure.
Figure 13-5 Procedure of overflow dump

Configuration interface of overflow dump:
380
Raisecom
Figure 13-6 Configuring overflow dump

Overflow dump is in support of below configuration:
 Enable overflow dump: tick off by default, denoting enable overflow dump function.
Click the box to cancel selection and stop this function. System prompts in red and the
configuration content become unconfigurable since it is suggested to enable overflow
function.
Figure 13-7 Prompt of canceling selection

 The maximum storage capacity (items): by default is 10000000 items, indicating the
system performs data dump when data over 10000000 items in database. You can input a
number or click the button of to adjust amount. Value range is 10000000–50000000.
 Capacity warning threshold (%): by default is 95%, indicating system generates trap
when data reach 95% of max. capacity and notify you. You can input a number or click
the button of to adjust amount. Value range is 80%–99%.
Capacity warning threshold is invalid when overflow dump is disabled. System will
neither perform overflow dump nor generate alarm.
 Dump percentage (%): by default is 10%, indicating system dump 10% of the max.
saving capacity. You can input a number or click the button of to adjust amount.
Value range is 1%–50%.
13.2.5 Configuring periodical dump

Periodic dump means system dump data when data amount over "data saving time" (day).
This function become effective immediately after configuration, system judge data saving
time at first, if it is overtime, system judges dump period and dump all data overtime if
reaching dump period.
381
Raisecom
Figure 13-8 Procedure of periodical dump

Configuration interface of periodic dump:
382
Raisecom
Figure 13-9 Configuring periodical dump

Periodic dump is in support of below configuration:
 Enable periodic dump: tick off by default, indicating enable periodic dump function.
Click it to cancel selection, the dump period and data saving time both become
unconfigurable.
 Dump period: by default is 1 day, indicating perform dump period is 1 day, namely dump
once every day. The first dump will be executed immediately after enable periodic dump.
You can input a number or click the button of to adjust amount. Value range is 1–90.
 Data saving time: by default is 7 days, indicating perform dump for data over 7 days.
You can input a number or click the button of to adjust amount. Value range is 7–
360.
13.2.6 Configuring dump file

You can configure data saving file type and relative or absolute path in database. In support of
configuration file overtime, system delete overtime dump files by automation.
The configuration interface for dump files:
Figure 13-10 Configuring dump file

Overflow dump is in support of below configuration:
 File type: by default is "CSV (separated by comma) (.csv)", also supports TXT format.
Dump file divides a dump file into several files by automation and save them in a
compressed zip file. The several files adopt 3-digit number to arrange order. Thus a
single dump file will not be oversize and save disk space.
 File path: by default is "/datadump/xxx/xxxx", indicating relative path to save file. It is in
support of relative path and absolute path. The root content for relative path is
"/NMS/PLATFORM/NNM5/server". Saving path for log, history alarm and performance
data are saved in different folders according to user's configuration items. For example:
configure system log saving path as "/datadump/log/syslog", installation disk symbol for
383
Raisecom
NView NNM system is "C:", then saving path for dump file is
"C:/NMS/PLATFORM/NNM5/server/datadump/log/syslog", at the same time of data
dump, system automatically creates the secondary folder of the path as dump file for
dump classification. File path can be recovered to default dump path by clicking the
button of Default.
 Delete dump file by automation: it is not tick off by default, indicating does not enable
automatic deletion function for expired dump file. Tick off the box means enable the
function. It is suggested to enable this function since expiry files become more and more
will take up more and more saving space.
 File expired time: by default is 90 days, indicating the dump files over 90 days will be
deleted by automation. You can input a number or click the button of to adjust
amount. Value range is 90–180.
13.2.7 Configuring FTP upload

Dump file FTP upload refers to upload files meeting dump conditions to FTP and save, which
supports to delete the uploaded FTP local files.
FTP upload configuration interface is shown as below.
Figure 13-11 Configuring FTP upload

FTP upload supports the following configuration:
 Delete local file or not: default not to check, indicates disable to automatically delete the
uploaded FTP local dump file. Checked indicates enable. It is recommended to enable
this function for the number of local files is increasing and occupies storage space
constantly.
 Setting: Click to pop up xFTP monitor interface, you can click Add to
set FTP server information.
384
Raisecom
Figure 13-12 Adding FTP server information

─ Type: select xFTP type as FTP;
─ IP address: input FTP server address;
─ Port No.: input FTP used port No., default for 21;
─ Anonymous login: checked indicates anonymous login to the FTP server, default for
unchecked;
─ User name: input the user name to login FTP server;
─ Password: input the password to login FTP server;
─ Root directory: input root directory to upload dump file to FTP server.
After filling out the parameters, click Test to test whether the added information is correct; if
the information is wrong, it will pop up Error prompt; if the information is correct, it will
show the added FTP information on xFTP monitor interface.
You can select FTP information to use, click OK to show corresponding information about
"FTP IP address", "FTP port", "user name" and "root directory" in the interface.
 FTP IP address: IP address of FTP server;
 FTP port: port No. of FTP server;
 User name: user name to login FTP server;
 Root directory: root directory to upload dump file to FTP server.
13.3 Manual dump

Manual dump is in support of data dump by time. You can set time range and file type, then
system performs data dump in the time range. After configuring manual dump, click the
385
Raisecom
button of Dump to execute immediately. Do not dump if the "Record Number" is 0 in time
range.
13.3.1 Configuration interface

Click System > Data Dump > Manual Dump in system menu of NView NNM to open
interface of manual dump configuration. The left is navigation tree; the right is functional
item for data dump.
Figure 13-13 Configuring manual dump
13.3.2 Procedures of manual dump

Procedure of manual dump:
386
Raisecom
Figure 13-14 Procedure of manual dump
13.3.3 Scenarios
Manual dump is not in support of delete expired file by automation; you have to delete by
manual. The dump file type and path by manual is consistent with automatic dump and it
cannot be modified.
After you configuring time range, click Query to view data number in time range, then click
the button of Dump to perform manual dump immediately. The button Dump is unavailable
if the "Record Number" is 0 in time range.
When data amount in selected time range over 1000,000 items, system prompts it will cost
long time and take up large space, you need to confirm continue or not.
Figure 13-15 Confirming manual dump

Click Yes to enable manual dump and open prompt box. Click No to return back to manual
dump configuration interface. The result will record in dump log after manual dump.
387
Raisecom
Figure 13-16 Prompt of enabling manual dump
13.3.4 Configuring dump time range

Dump time range function is to perform data dump for data in time range.
Configuration interface of dump time range:
Figure 13-17 Range of dump time

Dump time range is in support of below configuration:
 Start time: by default is tick off and set as current time. Cancel selection means do not
set start time, then all data before ending time will dumped. It is in support of set detailed
start time if tick it off. Click the drop-down box to open time selection interface, in
support of selecting date and time.
Figure 13-18 Selecting time

 End time: by default is tick off and set as current time. Cancel selection means do not set
end time, then all data after start time will dumped. It is in support of set detailed end
time if tick it off. Click the drop-down box to open time selection interface, in support of
selecting date and time.
388
Raisecom
Neither tick off start time nor end time means dump all data of the dump object.
 Records: after configuring dump time range, click Query to count data items by
automation. Do not perform dump if "Records" is 0.
13.3.5 Dumping file by manual

Dump file type by manual is consistent with configuration of automatic dump, it cannot be
modified.
Interface for configuring dump file by manual:
Figure 13-19 Configuring dump file manually
13.3.6 Manual dump FTP upload

FTP upload configuration refers to dump file will be upload to FTP server through FTP
upload after performing dump. Manual FTP dump supports to delete the local dump file
automatically.
The manual dump FTP upload configuration interface is shown as below.
Figure 13-20 Manual dump FTP upload
13.4 Checking dump conditions

After execution of data dump, system generates dump file and detailed dump log. You can
check the file and view log to confirm dump condition.
13.4.1 Checking dump file

By searching dump file and open view to check dump file. The dump files are saved in fixed
file name and format under folder of file path.
389
Raisecom
Searching dump file

The dump files are saved under file path configured in automatic dump. Open the folder, the
dump file is saved in zip format and named as "syslog_save time_dump
mode_number.extension name".
Figure 13-21 Dump files inside compression package

Rules for file name format:
 Alias of dump data: the English name of data.
 Save time: format of time is "year month day minute hour second".
 Dump mode: overflow dump, periodic dump, or manual dump. Overflow dump is
denoted as "fd", periodic dump is denoted as "pd", manual dump is denoted as "md".
 Number: to avoid single dump file over size, system numbers the dump data file,
numbering in range of 001–999.
 Extension name: format of dump file, CSV or TXT file.
Viewing dump files

Double-click the file to browse it. The file records all information of dump data.
390
Raisecom
Figure 13-22 Viewing system log dump file in CSV format
Figure 13-23 Viewing system log dump file in TXT format
13.4.2 Viewing dump log

At the system menu bar, click Log > Syslog to display a window. Query system operation log
by "Dump" in "Operation" and then you can view all dump logs. The log records the result of
data dump and dump amount, etc. information in details.
391
Raisecom
Figure 13-24 Viewing dump log
392
Raisecom
NView NNM Operation Guide 14 Appendix
14 Appendix
14.1 Operation authority comparison table

Network management application contains system menu, toolbar button, and right-click
shortcut menu, double-click operation, etc. This chapter introduces the common network
management application operation and authority comparison table.
Network management system provides system defaulted operator set, which can
basically meet the requirements of authority division. To distribute separate operation
authority is only used to fine adjustment of user authority.
14.1.1 Network management application and system menu

authority comparison table
If there is no special instructions in operation authority:

 Use "," to show multiple authorities need to be distributed
 Use project list to show multiple paratactic authorities, i.e. to separately distribute
one authority to achieve one function authority distribution, also to distribute
multiple authorities to achieve multiple functions authorities.
The operation authority is generally divided into View, Add, Modify and Delete. You
can only click the menu to open corresponding interface to view; for Add, Modify and
Delete functions, you need to distribute corresponding operation authority.
System
Operation authority Menu item Function description
– Modify Modify the current user login
password password.
– System Lock client.
lock
– Switch user Switch client user.
393
Raisecom

System Preference Configure server connection, alarm
management/System sound, Telnet NE auto-input user
parameters setting information, system debug
information and system login mode.
 Dump setting: configure auto-dump.
Data dump
 Manual dump: Configure manual dump.
Set xFTP monitor: configure commonly
used xFTP server.
– Exit Exit client.
Topology
Topology/Search Search node Search subnet, NE and symbol
in topology.
Topology Device Configure NE auto-discovery
management/Device discovery and device polling cycle.
discovery and polling and polling
Topology Subnet list Show subnets in topology.
management/Topology
browse Node list Show NEs and symbols in
topology.
Link list Show links in topology
Topology Customized Configure customized
management/Customized view management view.
view management management
Alarm
Failure management/Alarm Alarm grouping Show current alarm list
view monitoring according to alarm
group.
Current alarm Show current alarm list
query and manage current
alarm.
Historical alarm Show historical alarm
management list and manage
historical alarm.
394
Raisecom

Failure management/Alarm Alarm type Show alarm type list in
type management management network management
system.
Failure management/Alarm Alarm Configure alarm
notification management notification notification email
management address and mobile
number.
Alarm notification
supports email
notification and EMS
notification.
Failure management/View Alarm filter Configure customized
alarm filter policy, Failure policy management view.
management/Configure alarm
filter policy
Failure Troubleshooting Configure
management/Troubleshooting experience troubleshooting
experience experience.
 Failure management/Alarm list Setting Configure alarm setting
order function.
 Failure management/Reversal
 Alarm list order: configure
alarm list order.
 Alarm reversal: configure
alarm reversal function.
To separately distribute "Failure management/Alarm view" authority, you can view

current/historical alarm, and also can view alarm grouping monitoring, but cannot
confirm and clear the alarm.
 To deal with current alarm, please distribute "Failure management/Alarm view",
"Failure management/Current alarm management" and "Failure
management/Alarm grouping monitoring" at the same time.
 To deal with current alarm, please distribute "Failure management/Alarm view"
and "Failure management/Historical alarm management" at the same time.
Performance
Performance Performance Configure performance
management/Performance monitoring monitoring progress.
monitoring progress progress
browse browse
395
Raisecom

 Performance Template Configure performance
management/Show indicator management template.
template group
 Indicator template group
 Performance
management/Show indicator management: configure template

template group, which support to configure
 Performance performance indicator template
management/Show threshold and indicator threshold template.
 Indicator template management:
template
configure indicator template to
take customized filter to required
indicators.
 Threshold template management:
configure threshold template,

which supports to create and
configure multi-level threshold to
multiple thresholds.
Performance Collection Configure performance
management/Show task collection task.
collection task management
Performance Performance Show historical/real-time
management/Performance graph performance graph and
graph browse performance data.
To manage performance template and collection task, you need to distribute

corresponding Add, Modify, Delete and Start/Stop collection task authority.
Inventory
Inventory management Menu item Function description
operation authority
 Show rack list Physical Show various resource records of
 Show NE list inventory physical inventory and manage
 Show chassis list
inventory information.
 Show slot list
 Show slot supporting
card list
 Show central office card
list
 Show remote device list
 Show ONU list
 Show port list
 Show NE type
Inventory Show inventory type.
 Show chassis type
type
 Show central office card
type
 Show port type
396
Raisecom
Inventory management Menu item Function description

operation authority
Show address book Address Show maintenance staff address
book book.
Configuration
Configure&Batch Switch Configure switch
configure/Switch cluster cluster management.
management
Configure&Batch CBAT Show CBAT.
configure/EoC/CBAT query query
Configure&Batch CBAT Configure CBAT
configure/EoC/CBATmanagement management management.
Configure&Batch CNU query Show CNU.

configure/EoC/CNU query
Configure&Batch CNU Configure CNU
configure/EoC/CNU management management management.
Configure&Batch configure/ Batch Configure batch

Batch configure console configure configuration task.
console  General command: Batch
configure SNMP
parameters, Trap target
address to specified NE.
 Switch command: Batch
configure specified
switch NE.
Configure&Batch configure/ Batch Show batch
Batch configure log configure configuration
log operation result
record.
397
Raisecom

Configure&Batch configure/ Batch Configure to execute
Batch configure executive executive command line script
command line script command to NE.
line script Input or export
command line script
and execute command
line operation to
device by Telnet
mode, supporting to
select multiple
devices to execute the
same command line in
turn and return to
command execution
result.
Configure&Batch configure/OLP OLP route Configure optical line
route protection device
route.
Configure&Batch EPON Show EPON link
configure/EPON/EPON protection protection protection view.
view view
Configure&Batch MAC Execute MAC address
configure/EPON/EPON MAC address trace.
address trace trace
Configure&Batch MAC ONU MAC address
configure/EPON/MAC address address rebind.
rebind rebind
Template
Service template/EoC EoC Configure CNU device
service template template template.
management
398
Raisecom
Customer
Customer Customer Configure customer
management/Associatestomer list information.
management/Associate
customermanagementdevices
to execute the same command
line by turns and return to
command execution customer
To associate NE to customer information, you need to distribute "Customer

management/Associatestomer management/Associate
customermanagementdevices to execute the same command line by turns and return
to command execution customer" authority.
Report form
Statistics Current Current alarm statistics in NMS or
analysis/Alarm alarm subnet.
related statistics statistics
Historical Historical alarm statistics in NMS or
alarm subnet.
statistics
Statistics Device Various types of devices number
analysis/Resource type statistics in NMS or subnet.
related statistics statistics
Card type Various types of cards number
statistics statistics in NMS or subnet.
Slot idle Chassis-based device slot idle rate
rate statistics in NMS or subnet.
statistics
Statistics Device NE device offline rate statistics in
analysis/Device offline NMS or subnet.
offline rate statistics rate
statistics
Security
Security management related menu and function authority are distributed by "Security
administrators group" and "Sub-domain security administrators group" user group, users in
399
Raisecom
these two user groups will obtain security management authority. Not take authority
distribution to separate security management operation.
Log
Log management/System Query Show NView NNM operation
event management system records.
event
Log management/System Query Show user executing operation
operation log system records by client.
management operation
Log management/Device Query Show user executing NE device
operation log device operation records by client.
management operation
Log management/User Query login Show user login client records.
login log management log
Log management/Syslog Query Show NE device reported
management Syslog Syslog records.
Service
Only users in "Administrators" user group have service management authority.
Data center
Data Software Configure data center NE
center/Software library device/card software management
library management management function.
Data center/Device Device Configure to upgrade and backup
operation operation NE device in data center, show NE
device/card data center operation
records, system software version,
etc.
Data center/Task Task Show the current task working
management management status and complete task in data
center.
Data center/Backup Backup Configure data center NE device
policy policy backup policy.
Data center/Backup Backup Configure data center NE
library management library device/card software backup
management management function.
400
Raisecom

Data center/Data Backup log Show data center log, operation and
center log backup log.
management
Forms
All users have forms related authority
Tool
Tool management/ICMP ICMP Execute ICMP Ping.

Ping Ping Check the connectivity from
NMS server to target IP address.
Tool management/SNMP SNMP Execute SNMP Ping.
Ping Ping Check SNMP packets
connectivity from NMS server
to target IP address.
Tool management/Web Web Open built-in Web browser.
Browser Browser
Help
All users have help-related authority
14.1.2 Network management application and topology management

authority comparison table
The "Topology browse" authority in topology management is a basic authority;

various operations in topology management need this authority.
Operation authority Shortcut Function description
button/right-click
shortcut menu
– Expand, shrink Expand/shrink gateway NE subnet in
current view
Tool management/Lock, Lock coordinate, Lock/unlock gateway NE subnet and NE
unlock unlock node position in view.
coordinate
401
Raisecom
Operation authority Shortcut Function description

button/right-click
shortcut menu
Tool management/Edit Edit/Edit Edit device properties.
properties properties
Tool management/Copy to Edit/Copy to Copy gateway NE subnet and NE node
with the same type.
Configure node IP address.
Tool management/Move to Edit/Move to Move gateway NE subnet located subnet.
Tool management/Delete NE Delete Delete the device gateway NE subnet and
NE node.
Tool management/Topology Show properties Show device properties.
browse
Tool management/Set Set background Configure gateway NE subnet background
background image image image.
Tool management/Add to Add to Add gateway NE subnet and NE node to
customized view customized view customized view.
14.1.3 Device operation authority and network element

management function comparison table
The device operation authority only applies to a single NE device. Please assign the
user's network management application authorities, and then assign device operation
authorities.
 To view smaller management domain (such as to view one or several NE devices)
configuration information, it is recommended to assign network management
application "Platform guard operation table:, and assign "NE management/View
configuration" and "NE management/Configuration Sync" operation authorities to
each device.
 To manage smaller management domain (such as to view one or several NE
devices) configuration information, it is recommended to assign network
management application "Platform guard operation table:, and assign "NE
management/View configuration", "NE management/Modify configuration" and
"NE management/Configuration Sync" operation authorities to each device.
 "NE management/Pre-configuration management" only applies to the devices
such as the iTN2100 to support pre-configuration function.
NE management operation Function description
authority
View configuration Execute NE management, open NE configuration
interface, only view various configuration
information.
402
Raisecom
NE management operation Function description

authority
Configuration sync Execute resource sync function, sync the current
device information.
Modify configuration Execute NE management, open NE configuration
interface, modify various configuration
information.
This authority needs to be used with "View
configuration" authority.
Pre-configuration Execute pre-configuration functions, such as pre-
management configuration sync and pre-configuration issue.
14.1.4 Operation authority dependence relationship comparison

table
The dependence relationship between authorizes mainly contains Add, Modify, Delete
management authorities and view the dependence relationship between authorities.
The management authority is generally depended on view authority, i.e. the Add, Modify
Delete management operations need view authority.
To know authority dependence table can avoid the operation failure in authority refining for
not assigning dependence authority. It can ensure the dependence relationship to use system
provided operator set for authority division.
Network device authority dependence relationship

Depended operation
Classification Operation authority
authority
Device operation
Modify configuration. View configuration.
authority
Network management application authority dependence relationship

Classification Operation authority Depended operation authority
Add rack. Show rack list.
Add contact. Show book address.
Inventory Modify rack properties Show rack list.

management Modify NE properties Show NE list
Modify chassis properties Show chassis list
Modify slot properties Show slot list
403
Raisecom

Modify central office
Show central office card list
card properties
Modify remote device
Show remote device list
properties
Modify ONU properties Show ONU list
Modify port properties Show port list
Modify contact
Show book address
information
Delete rack Show rack list
Delete NE Show NE list
Delete chassis Show chassis list
Delete slot Show slot list
Delete central office card Show central office card list
Delete remote device Show remote device list
Delete ONU Show ONU list
Delete port Show port list
Delete contact Show book address
Topology browse or show NE
Resource sync
list
Current alarm
Show alarm
management
Historical alarm
Show alarm
management
Alarm type management –
Show alarm filter policy –
Alarm notification
–
Fault management
management Troubleshooting
–
experience management
Alarm grouping
Show alarm
monitoring
Alarm list order –
Alarm reversal –
Configure alarm filter
Show alarm filter policy
policy
404
Raisecom

System event
–
management
System operation log
–
management
Log
Device operation log
management –
management
User login log
–
management
Syslog management –
Add device Topology browse
Add link Topology browse
Add subnet Topology browse
Add symbol Topology browse
Search Topology browse
Edit properties –
Delete NE Topology browse
Copy to Topology browse
Move to Topology browse
Customized view
Topology browse
Topology management
management Add to customized view Topology browse
Open customized view Topology browse
Lock Topology browse
Unlock Topology browse
Lock view Topology browse
Unlock view Topology browse
Set background image Topology browse
Topology browse –
Topology locate Topology browse
Device discovery and
–
polling
Performance Performance monitoring –
management progress browse
405
Raisecom

Show indicator template –
group list
Add indicator template Show indicator template
group group list
Modify indicator Show indicator template
template group group list
Delete indicator template Show indicator template
group group list
Show indicator template
–
list
Add indicator template Show indicator template list
Modify indicator
Show indicator template list
template
Delete indicator template Show indicator template list
Show threshold template
–
list
Add threshold template Show threshold template list
Modify threshold
Show threshold template list
template
Delete threshold template Show threshold template list
Show collection task list –
Add collection task Show collection task list
Modify collection task Show collection task list
Delete collection task Show collection task list
Start collection task Show collection task list
Stop collection task Show collection task list
Performance image
–
browse
Device offline rate
–
statistics
Statistics
Alarm related statistics –
analysis
Resource related
–
statistics
NE Configuration sync –
management Show configuration –
406
Raisecom

Modify configuration Show configuration
Pre-configuration
–
management
Software library
–
management
Task management –
Backup policy –
Data center Backup library
–
management
Data center log
–
management
Device operation –
Customer information
Customer –
management
management
Associated customer –
System System parameters
–
management setting
User management –
Reset password –
User group management –
Force user to exit –
Security policy edit –
Monitor user –
Security
management Unlock user –
Manage security
–
authority
Operator set management –
Security log management –
Set log policy –
Access control list –
ICMP Ping –
Tool SNMP Ping –

management Trace Route –
MAC Trace –
407
Raisecom

Web Browser –
Telnet –
Native Ping –
Show system service –
Edit system service –
Start system service –
Stop system service –
Service
Show timing service –
Edit timing service –
Start timing service –
Stop timing service –
EoC –
CBAT query –
CBAT management –
CNU query –
CNU management –
Switch cluster
–
management
OLP route –
Configuration
&Batch Batch configuration
–
configuration console
Batch configuration log –
Batch execute command
–
line script
EPON –
EPON MAC address
–
trace
EPON protection view –
MAC address rebind –
Service EoC service template
–
template management
408
Raisecom
14.2 Terms
A
Alarm The reported information when device or network management
system detects failure.
C
Customer Customer uses device provided service; the customer information
can associate with NE, alarm and can only be stored in network
management system.
E
Equivalent NE Each NE device can be converted to equivalent NE according to
the equivalent coefficient so as to calculate network
management system management capacity.
I
Inventory Various resources in network management system.
N
Network Network device takes management in network management
Element system as network element
NMS Monitor Auxiliary program of network management system, which can
manage various service programs in network management
system and monitor network management system operating
status.
Node General terms of subnet, NE and symbols in network
management system.
P
Performance Network management system collects and shows device flow,
Monitor packet loss and other performance data.
R
Resource Management objects in network management system, including
device, chassis, card, port and etc.
S
Subnet Subnet refers to the logical division of network topology
structure in network management system, which can help show
NE topology structure clearly in network management system.
The subnet interior can contain subnet, NE, symbol, and link etc
topology nodes.
Symbol Symbol is schematic topology node, which cannot take network
management, but give better display to network structure.
Synchronizatio Network management system updates device resource or alarm
n information in database by synchronization function to make
network management system correspondence with device.
409
Raisecom
T
Topology Graphical network structure in network management system,
which can show networking situation, subnet/NE alarm and
online status intuitionally.
U
User Network management system client user; the collection of user
and user group management domain and operation permission
confirms network management function used by user.
14.3 Abbreviations
A
AES Advanced Encryption Standard
C
CPU Central Processing Unit
D
DES Data Encryption Standard
E
EPON Ethernet Passive Optical Network
F
FPGA Field-Programmable Gate Array
FTP File Transfer Protocol
G
GUI Graphical User Interface
I
ICMP Internet Control Message Protocol
IP Internet Protocol
410
Raisecom
LLDP Link Layer Discovery Protocol
M
MD5 Message-Digest Algorithm 5
MIB Management Information Base
N
NCIA North CORBA Interface Agent
NNM Network Node Management
NSIA North Socket Interface Agent
O
OID Object Identifier
OLP Optical Line Protection
ONU Optical Network Unit
P
PCM Pulse Code Modulation
PDH Plesiochronous Digital Hierarchy
PDU Protocol Data Unit
PM Performance Monitoring
Q
QoS Quality of Service
R
RMON Remote Network Monitoring
RNDP Raisecom Neighbour Discover Protocol
S
SDH Synchronous Digital Hierarchy
SHA Secure Hash Algorithm
SLA Service Level Agreement
411
Raisecom
SMTP Simple Mail Transfer Protocol

SNMP Simple Network Management Protocol
U
UDP User Datagram Protocol
V
VLAN Virtual Local Area Network
VoIP Voice over IP
X
XML Extensible Mark-up Language
412
Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China.
Postal code: 100085 Tel: +86-10-82883305
Fax: 8610-82883056 http://www.raisecom.com Email: export@raisecom.com

NView NNM Operation Guide (V5 - 41)

Uploaded by

Copyright:

Available Formats

You might also like

NView NNM Operation Guide (V5 - 41)

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

NView NNM Operation Guide (V5 - 41)

Uploaded by

Copyright:

Available Formats

www.raisecom.

is the trademark of Raisecom Technology Co., Ltd.

Product name Version

Raisecom Technology Co., Ltd. i

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

Raisecom Technology Co., Ltd. ii

Click Select and release the primary mouse button without

Raisecom Technology Co., Ltd. iii

1 System overview ........................................................................................................................... 1

2 Quick start ...................................................................................................................................... 5

Raisecom Technology Co., Ltd. iv

2.4.2 Topology ............................................................................................................................................... 29

3 System monitoring ...................................................................................................................... 42

Raisecom Technology Co., Ltd. v

3.3.4 Setting service alarm threshold ............................................................................................................. 52

4 Network topology management ............................................................................................... 70

Raisecom Technology Co., Ltd. vi

4.3 Creating topology subnets .............................................................................................................................. 77

Raisecom Technology Co., Ltd. vii

4.10.14 Selecting multiple topology objects ................................................................................................ 110

5 Device discovery and polling ................................................................................................. 125

6 Device configuration management........................................................................................ 157

Raisecom Technology Co., Ltd. viii

6.3 Configuration management using NE management module ........................................................................ 161

7 Alarm event management........................................................................................................ 192

Raisecom Technology Co., Ltd. ix

7.1.7 Alarm compressing ............................................................................................................................. 194

Raisecom Technology Co., Ltd. x

7.7.7 Deploying alarm level filter rules ....................................................................................................... 241

8 Inventory management ............................................................................................................ 261

Raisecom Technology Co., Ltd. xi

8.5.1 Rack .................................................................................................................................................... 266

9 Customer management ............................................................................................................ 289

10 System security management ............................................................................................... 298

Raisecom Technology Co., Ltd. xii

10.2.2 Creating users.................................................................................................................................... 304

11 System service management ................................................................................................. 337

Raisecom Technology Co., Ltd. xiii

11.5.4 Alarm SMS relay service................................................................................................................... 347

12 System maintenance ............................................................................................................... 364

13 Data Dump ............................................................................................................................... 375

Raisecom Technology Co., Ltd. xiv

13.4.2 Viewing dump log ............................................................................................................................. 391

14 Appendix .................................................................................................................................. 393

Raisecom Technology Co., Ltd. xv

to customers, it is convenient for network administrators to find the customers affected

1.2 Functions and features

1.2.2 Strong topology management function

1.2.3 Perfect fault management function

 Alarm auto-forwarding function. Administrator can be notified with alarm events

1.2.4 Uniform resource management function

1.2.5 Flexible security control strategy

2.1 System operations

2.1.1 Starting NView NNM

Starting NView NNM

Figure 2-1 Starting NMS server

 By default, NView NNM is registered for operating system service "NMSServer",

Detecting significant system files automatically